chore(markdown): render to light DOM for styling

Related Ticket(s)
Refs #4327.
Refs #4129.
Refs #4104.
Description
Changes <dds-markdown> to:

Render its converted HTML to light DOM instead of in shadow DOM, to allow adaptors to apply their custom styles to the rendered markdown content.
Apply Carbon standard style automatically via carbon-web-components.
Removes attributes for markdown rendering options that seems not supported by markdownToHtml().

For the second one above, enhances markdownToHtml() to allow custom renderer and custom tags.
From the same/similar purpose of the first two above, introduces <dds-content-block-copy> and <dds-content-item-copy>, that extends <dds-markdown> and replaces copy attribute of <dds-content-block> and <dds-content-item>, respectively. <dds-content-block-copy> and <dds-content-item-copy> renders new <dds-content-block-paragraph> and <dds-content-item-paragraph> tags, respectively, to achieve their specific styling needs.
Due to the third one above, <dds-card-cta-markdown> has become the same as <dds-markdown> and thus it's removed.
Also:

Adds expressive theme to the Storybook global style, so carbon-web-components components in there get the expressive theme.
Renames _hasCta private property to _hasCTA in <dds-content-item>, to align to other components.
Makes <dds-pictogram-item> inherit <dds-content-item> so it can better represent its nature, and use <dds-content-item-copy> instead of rendering <dds-markdown> and <dds-content-item-heading> instead of rendering <dds-content-item-heading> by itself.
A change to ensure <dds-image-with-caption> does not render modal unless it's lightbox mode.
Applys a similar change to <dds-content-group>.

Changelog
New

Custom renderer and custom tag support for markdownToHtml().
<dds-content-block-copy>, the markdown copy content of <dds-content-block>.
<dds-content-item-copy>, the markdown copy content of <dds-content-item>.
<dds-content-block-paragraph>, the paragraph content of <dds-content-block>.
<dds-content-item-paragraph>, the paragraph content of <dds-content-item>.

Changed

Changes <dds-markdown> to:

Render its converted HTML to light DOM instead of in shadow DOM, to allow adaptors to apply their custom styles to the rendered markdown content.
Apply Carbon standard style automatically via carbon-web-components.
Removes attributes for markdown rendering options that seems not supported by markdownToHtml().

Makes <dds-pictogram-item> inherit <dds-content-item>.
A change to ensure <dds-image-with-caption> does not render modal unless it's lightbox mode.

Removed

<dds-card-cta-markdown>

Thank you @asudoh ! Can you also update the READMEs for the components using the new custom elements (like dds-content-block-simple), as it is still referencing the old way of setting copy and paragraph.
Also just for my knowledge, wondering if the copy should be a slot instead of directly referencing the sub-component custom elements and setting as attributes for those?

@jeffchew

Can you also update the READMEs for the components using the new custom elements (like dds-content-block-simple), as it is still referencing the old way of setting copy and paragraph.

It's done something like this, but please let me know if there are any missing CodeSandbox changes: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/4351/files#diff-ec211775d10ab010fc9500490855ad3a24ea089b67f6e590d7285b96940d2769

Also just for my knowledge, wondering if the copy should be a slot instead of directly referencing the sub-component custom elements and setting as attributes for those?

If I understand what you said correctly, yes, above CodeSandbox example reflects such change. But please let me know if I'm missing anything. Thanks!

Can you also update the READMEs for the components using the new custom elements (like dds-content-block-simple), as it is still referencing the old way of setting copy and paragraph.

It's done something like this, but please let me know if there are any missing CodeSandbox changes: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/4351/files#diff-ec211775d10ab010fc9500490855ad3a24ea089b67f6e590d7285b96940d2769

Yes, looks like you updated the codesandbox but not the README file: https://ibmdotcom-webcomponents.s3.us-east.cloud-object-storage.appdomain.cloud/deploy-previews/4351/index.html?path=/docs/components-content-block-simple--default

Got it, thank you for clarifying @jeffchew! Updated.

Also just for my knowledge, wondering if the copy should be a slot instead of directly referencing the sub-component custom elements and setting as attributes for those?

If I understand what you said correctly, yes, above CodeSandbox example reflects such change. But please let me know if I'm missing anything. Thanks!

I guess my question is why is it like:
<dds-content-item-copy content="Lorem ipsum *dolor* sit amet"></dds-content-item-copy>

And not:
<dds-content-item-copy>
   Lorem ipsum *dolor* sit amet
</dds-content-item-copy>

Or even:
<dds-content-block-simple>
  <slot slot="heading">Curabitur malesuada varius mi eu posuere</slot>
  <slot slot="copy">Lorem ipsum *dolor* sit amet</slot>
  ...
</dds-content-block-simple>

@jeffchew Good question - If we put the copy content as a child text node, the whitespace in the text node directly affects what's rendered as markdown. Given that, copy property (instead of attribute) is the primary way of <dds-markdown> (and its descendants like <dds-content-item-copy>) as its API to set the markdown content. copy attribute can be used, too, as long as the spacing is right.
BTW <slot> is for shadow DOM to define the slot, instead of for component users to use the slot. We have some wrong usage of <slot>s in that regard (we can search for <slot slot="...">) that needs to be fixed.

@jeffchew Good question - If we put the copy content as a child text node, the whitespace in the text node directly affects what's rendered as markdown. Given that, copy property (instead of attribute) is the primary way of <dds-markdown> (and its descendants like <dds-content-item-copy>) as its API to set the markdown content. copy attribute can be used, too, as long as the spacing is right.
BTW <slot> is for shadow DOM to define the slot, instead of for component users to use the slot. We have some wrong usage of <slot>s in that regard (we can search for <slot slot="...">) that needs to be fixed.

Ok, I'm wondering if we stick with <dds-content-item-copy>, if users have paragraphs of content then having that in an attribute might not work, especially if this is happening in something like a CMS if they configure the content block simple or content group simple as, say, a parsys element in AEM.

Ok, I'm wondering if we stick with <dds-content-item-copy>, if users have paragraphs of content then having that in an attribute might not work, especially if this is happening in something like a CMS if they configure the content block simple or content group simple as, say, a parsys element in AEM.

@jeffchew Wondering if it's about having to put newline character in attribute, or something else. If it's the case, our adaptors can simply HTML-encode newline characters. If not, interested in hearing more details, e.g. I have't been able to find a website that serves as a good summary of AEM parsys.

Ok, I'm wondering if we stick with <dds-content-item-copy>, if users have paragraphs of content then having that in an attribute might not work, especially if this is happening in something like a CMS if they configure the content block simple or content group simple as, say, a parsys element in AEM.

@jeffchew Wondering if it's about having to put newline character in attribute, or something else. If it's the case, our adaptors can simply HTML-encode newline characters. If not, interested in hearing more details, e.g. I have't been able to find a website that serves as a good summary of AEM parsys.

I guess a simpler example would be handlebars, or any CMS template file (AEM uses HTL). The template markup would look something like this:
<dds-content-block-simple>
  <dds-content-block-heading>{{ heading }}</dds-content-block-heading>
  <dds-content-item-copy content="{{ copy }}"></dds-content-item-copy>
  <dds-image slot="media" alt="Image alt text" default-src="{{ image.rendition.large }}">
    <dds-image-item media="(min-width: 672px)" srcset="{{ image.rendition.large }}"></dds-image-item>
    <dds-image-item media="(min-width: 400px)" srcset="{{ image.rendition.medium }}"></dds-image-item>
    <dds-image-item media="(min-width: 320px)" srcset="{{ image.rendition.small }}"></dds-image-item>
  </dds-image>
  <dds-text-cta slot="cta" href="{{ urlLink }}" type="local">{{ urlLabel }}</dds-text-cta>
</dds-content-block-simple>

In this scenario, the CMS will put in whatever copy in the authoring field that would go into <dds-content-item-copy>, which may or may not include spaces or line breaks. We're saying it's up to the CMS to escape those? I think it might be better if we did it as <dds-content-item-copy>{{ copy }}</dds-content-item-copy> then let our markdowndown utility handle whatever gets put in there.

@jeffchew You are right, we basically ask our adaptors to escape LFs in attribute for the particular case. The reason is that putting the contents in as the child node (text node) will cause redundant whitespace that affects how the markup is rendered. If it's possible with the CMS, a better approach is rendering the markup server-side, because by doing so we can avoid all the problems like whitespace and the extra code in client-side to sanitize the rendered markdown.

@jeffchew You are right, we basically ask our adaptors to escape LFs in attribute for the particular case. The reason is that putting the contents in as the child node (text node) will cause redundant whitespace that affects how the markup is rendered. If it's possible with the CMS, a better approach is rendering the markup server-side, because by doing so we can avoid all the problems like whitespace and the extra code in client-side to sanitize the rendered markdown.

I still think that having as an attribute isn't a good idea. We should expect adopters to trim whitespace on their own if it's an issue. If anything, if they pass non-trimmed/non-escaped content into an attribute that's even worse. I think having as content of the element makes more sense, and providing in the copy description that they should trim whitespace to not introduce unwanted rendering issues.

Thank you for your thought @jeffchew - Sent a message offline.

Per discussion with @jeffchew, unsupported content as an attribute and add support for child text node for providing markdown content, with a clear documentation that it's our adaptor's responsibility to take extra care not to put any extra whitespace in/around the markdown content. Thanks @jeffchew for your feedback!


Move the retry to a common util.

There is a couple of ways to do this, but I'm not sure what would work
best.  Either we can group all the exceptions together, or split up the
exceptions by smaller groups.  Such as email_exceptions vs http
exceptions.  This PR does the one big grouping as that seems easier to
manage.  But will be happy to hear of any feedback for the alternative.

Adding cla: yes label, as the PR author is a googler at the time of this PR was created.


isort not honoring setup.cfg

Environment data

VS Code version: 1.34.0
Extension version (available under the Extensions sidebar): 2019.5.17059 (28 May 2019)
OS and version: macOS 10.14.4
Python version: 3.6.7 (miniconda)

Issue
I added
  "editor.codeActionsOnSave": { "source.organizeImports": true }

to my user settings to sort imports with isort. I'm also using black as a code formatter. On multiline imports these two tools format imports very differently, leading to alternating formatting and jumping code from one save to the next as shown in this gif.

I was able to prevent this by configuring isort to use black's formatting by adding
[isort]
multi_line_output = 3
include_trailing_comma = True

to my setup.cfg as indicated in the comments of this black commit.
Now, the file is stable if I repeatedly save it without changes in between. But if I modify the file and then save, the imports briefly flash to isort formatting before reverting to black formatting. So unlike before, the final result is now always black formatting but there's jumping code every time I modify and save.
This seems to suggest that isort is still being run by VS Code with its default settings when the formatOnSave callbacks are triggered. Is there any way to respect the setup.cfg settings in the isort callback?
Additional Info
Related Issue: #2301

Do some more research, I was able to fix this issue by adding
"python.sortImports.args": ["--settings-path=${workspaceFolder}/setup.cfg"]

to my user settings as suggested here. This feels a little bit hacky tough, since other projects not all projects use a setup.cfg file, meaning this setting would have to be added on a per-workspace basis.
Is there a better way to handle this with less manual configuration?

Prescribed Solution

We have the same issue with other formatters, and the solution we've implemented there is to create a temporary file in the same location where the current file exists, and format that. This way the tools will pick correct config file.
Implement same solution for isort (create temp file in same location as current document if it hasn't been saved).

The real cause of this is that the bundled isort (sortImports.py) gets invoked without any directory context. At best, the cwd of isort is /, while it really should be ${workspaceFolder} -- obviously there's no relevant setup.cfg under /. This also explains why "python.sortImports.args": ["--settings-path=...] fixes thing.
Formatter invocations do set cwd properly, so I guess the solution would be to copy their cwd behaviour (maybe extract common parts even?). I hope to get around trying that soon.
@DonJayamanne I get the reasoning behind the autopep8/yapf tmpfile hack, however, isort has worked perfectly as < file.py | isort --diff - for quite a long time. Why the tmpfile dance for isort then, is it still relevant?
On a related note - is there a reason you guys bundle your own isort with the extension? Why not go the way of formatters and have it under the user's control?

I'm facing a related issue. I've configured isort's skip_glob and filter_files in my pyproject.toml such that files under my conda environment directory (site-packages etc.) are skipped by isort, and it works OK. However, as @janosh has indicated, if I modify some file from site-packages and then hit save, then isort gets invoked as
...\python.exe ...\.vscode\...\pythonFiles\sortImports.py ~\AppData\Local\Temp\tmp-334840Hb7lTxuklQV.py --diff --settings-path c:\...\workspace_folder --quiet

and since  ~\AppData\Local\Temp\tmp-334840Hb7lTxuklQV.py does not match my glob pattern, this does not get skipped, and gets processed by isort, ending up modifying the site-packages file which I do not want. Basically since each and every file passed to isort is invoked from the same temp directory, I cannot apply any rules to skip certain files.
I would be great @DonJayamanne if like you mentioned you could generate the temp file in the current directory. Then I wouldn't lose the directory context and apply myskip_glob properly.

Any update on a fix for this?  Its still happening in 1.44.2 and this issue has been open for nearly a year.

The real cause of this is that the bundled isort (sortImports.py) gets invoked without any directory context. At best, the cwd of isort is /, while it really should be ${workspaceFolder} -- obviously there's no relevant setup.cfg under /. This also explains why "python.sortImports.args": ["--settings-path=...] fixes things.

Actually, it seems to occur not only for the bundled isort, but also for the isort manually installed into the python virtual environment of the workspace.
But only when it does the tmpfile shenanigans...
I can reproduce it like this:
workspace settings.json
{
    "python.pythonPath": ".venv\Scripts\python",
    "python.sortImports.path": "${workspaceFolder}\.venv\Scripts\isort",  // needed (https://github.com/microsoft/vscode-python/issues/7042)
}

setup.cfg
[isort]
line_length = 88

main.py
from os import PathLike, environ, fsdecode, fsencode, fspath, getcwd, getenv, getlogin

Case 1: main.py is saved, then right-click menu -> Sort imports
The python extension output shows cmd
> <project_dir>\.venv\Scripts\isort.exe <project_dir>\main.py --diff
and all is fine, as the setup.cfg is respected and the line is shorter than 88 chars.
Case 2: main.py dirty (i.e. unsaved changes), then right-click menu -> Sort imports
The python extension output shows cmd
> <project_dir>\.venv\Scripts\isort.exe <user_dir>\AppData\Local\Temp\tmp-22188OH1xzYhzlS7j.py --diff
now the line gets formatted to
from os import (PathLike, environ, fsdecode, fsencode, fspath, getcwd, getenv,
                getlogin)

following the default line length of 80 chars (i.e. ignoring setup.cfg).
My guess is that when isort is invoked on a file outside of the project root (in this case in the system tmp folder), it does not honor the setup.cfg of the project (although isort itself is installed inside the project).

Also experiencing this with configuration in pyproject.toml.

Can anyone confirm if this issue is solved with https://github.com/microsoft/vscode-python/pull/9128? We went with using isort --diff - as @mikeroll suggested.

This is still an issue even after #9128. I believe this PR was included since 2020.6.88468 and I am having this issue with pyproject.toml

I'm still curious if there's an answer to @mikeroll's question:

On a related note - is there a reason you guys bundle your own isort with the extension? Why not go the way of formatters and have it under the user's control?

For me, this is not yet fixed.
I still need the lines suggested by janosh in my settings.json,
otherwise any isort configs in setup.cfg are ignored (e.g. line_length).
VSCode 1.49.0 insider
Extension 2020.8.105369
Win10
Python 3.8.5
isort 5.4.2


Make MAX_REQUEST_BLOB_SIDECARS and MAX_BLOBS_PER_BLOCK configurable

Problem description
In ethereum/consensus-specs#3817, MAX_BLOBS_PER_BLOCK is moved from preset to config.
This poses a challenge in Lodestar since BlobSidecarsByRootRequest - a fixed length ssz container depends on it but types package has no access to chain.config.

Solution description
I believe this is the only place in the spec has a ssz container for which its definition relies on a variable from config.
We can either make a one time exception and define BlobSidecarsByRootRequest ssz in beacon-node or further refactor to be more future proof if such scenario happens again.
cc. @g11tech
Additional context
No response

to fix your trouble check this solution click
maybe this will solve your problem.


Support for Windows on Arm

Hi,
What is your question?
Linaro is currently working with Microsoft to help develop Windows on Arm ecosystem.
For this task, we would like to be able to use containers to create reproducible builds.
docker x64 binaries are working, thanks to Win 11 x64 emulation.
For technical reasons, we must use process level isolation (hyper-v is not available in our environment).
However, there is no base image matching our host yet (its architecture).
When running  docker:
an error during hcsshim::System::Start: failure in a Windows system call: The container operating system does not match the host operating system. (0xc0370101).
We understand that it's difficult to bring support for this new platform, but is there a way to generate a windows base image ourselves (from an existing system)?
If not, is there a way to bypass this match check, to "force" a container to run?
Thanks,
Pierrick

Hey @pbo-linaro, thanks for this comment. ARM support is not available at the moment, but it's definitely on our roadmap. I can't promise any timelines on this, but it's good to continue to see asks for the feature. Creating new images from the binaries on the existing system is not currently possible either, primarily because it is against the Windows server license terms to repackage and distribute Windows OS binaries.

Thanks for your answer. Beyond licensing issue, is there something technical than can prevent it? The aim is not to redistribute anything, just to build/use an image locally.

For someone aking question "Why process level isolation needs same version of windows?", here is the reason.
To the opposite of Linux, Windows syscall interface is not stable. It can (and will) change between versions. A list is available here: https://j00ru.vexillium.org/syscalls/nt/64/. Thus, the same approach than Linux containerization can't be used.
The only stable interface is Win32 API (that's what wine project is targetting). It is implemented as a list of dll, and I assume this is what must be present in your container.
From there, probably that Windows container runtime is having a translation layer between versions, or simply injecting it's own ntdll library directly in the running container. Who knows?
See a list of windows layers there: https://en.wikipedia.org/wiki/Microsoft_Windows_library_files

IIRC there is a "Windows" image which is a specialized Windows 10/11 Enterprise image, not Windows Server. If Windows Server on ARM is not going to be public, providing Windows Client container base image would still be valuable.

The Windows image is only currently maintained for Windows Server 2019, and has been replaced with the Windows Server image from the Windows Server 2022 release onwards, as the Windows Server and (Client) Windows release cycles have diverged.
Anecdotally, I recall seeing mentioned somewhere that even that "Windows" image was actually a Windows Server build configured to work like (Client) Windows (including IIS connection limits, etc), rather than just a containerised copy of the relevant Windows 10 release. (Assuming I am remembering correctly) This was possible because at the time, Windows Server and Windows 10 were releasing with the same cadence.
Sadly, we haven't heard anything public about Windows Server on ARM since 2017 as far as I know, and Windows Containers is part of the Windows Server development roadmap, so without Windows Server on ARM, we aren't going to see Windows Containers on ARM either. (Although if and when we do get Windows Server on ARM, I expect Windows Containers support to be run-up pretty quickly.)


Big Problem with Lists

basically its when we are dealing with List. check the print bellow. Imagine the we have a Entity called FAQItem and a List<FAQItem> on my widget atributtes.
the .g does not convert it to a List<FAQItem> when reading the json. Resulting an error.
And its not only with List<Entity>, it's with every list.
List<String>, List<Int>...
I have to put manually List.from(map["list_example"]).
or in the case of List<Entity>:

I check the examples but there's no example using those kind of lists
there's a alternative for don't manually edit the .g file?

Responded in here
https://github.com/peiffer-innovations/json_dynamic_widget/issues/260#issuecomment-2148293288
Closing that one


How to use window handle of other application?

I wrote a launcher for my LWJGL game in Rust. Is it possible to pass the window handle via the start arguments to draw the game into my launcher window or would I have to pass every single OpenGL function via JNI?

Please clarify what you mean by "launcher". If you mean a JVM Invocation API client, which loads a JVM process and calls into your main class'es main(String[]) method (so essentially a replacement for the java executable), then you don't have to do anything, als GLFW when called inside your Java application will simply create the window.

I have written a program/launcher in Rust that uses OpenGL to open a window. This launcher starts the java.exe with the appropriate arguments. My question was if I can draw into this window from my program/launcher instead of creating a new window using LWJGL to make the transition a bit smoother?

Is there a particular reason why you create the window in another process and not inside of your Java application?
Regarding sharing window handles: There is a PR in GLFW to allow GLFW to manage external windows/contexts, but it hasn't been finished/integrated yet: https://github.com/glfw/glfw/issues/25

Is there a particular reason why you create the window in another process and not inside of your Java application?
Regarding sharing window handles: There is a PR in GLFW to allow GLFW to manage external windows/contexts, but it hasn't been finished/integrated yet: glfw/glfw#25

The reason is that in the future I want to run not only Java programs but also other applications.

Alright, then it seems this is not a question/issue towards LWJGL but rather towards the windowing/context library used. In LWJGL's case it is GLFW, which as of now, does not have this capability. I don't know about GLUT or SDL even being able to do this.

In the end, this question boils down to: "Can an OS process A render to a window from another process B using OpenGL." And so far the answer to this seems to be "no", at least on Windows. You might want to do more research in that area. Probably first try with simply two native (i.e. Rust or C) processes and try using the window handle of process in process B and make that context/window current and draw to it and swap buffers in process B.


Add Brazilian Portuguese locale

Remove a duplicated entry in the french javascript locale

Not sure if you guys accept translations... But here's the Brazilian Portuguese one, anyway.

Thank you, but I am not currently willing to maintain support for more languages. If I see more desire for this from the community, I will reconsider; closing for now.


Spyder crashes after minimizing to Start bar and reactivating the window (Windows 7)

Description
What steps will reproduce the problem?

Python 3.7.0, Spyder 3.3.1., Windows 7 (6.1.7601 Sp1).
Whenever I minimize the program to the Start bar, then try to reactivate the window, Spyder crashes. I donot have Just In Time debugging on the machine I use, but the problem seems to come from an unknown exception within Spyder.
This has consistently happened to me on Anaconda 3-5.2.0, and after removing Anaconda and reinstalling Spyder from pip3.
Versions

Spyder version: 3.3.1
Python version: 3.7.0
Qt version: 5.9.3
PyQt5 version: 5.9.2
Operating System: Windows 7

Dependencies
pyflakes >=0.6.0  :  2.0.0 (OK)
pycodestyle >=2.3 :  2.4.0 (OK)
pygments >=2.0    :  2.2.0 (OK)
sphinx >=0.6.6    :  1.8.1 (OK)
rope >=0.9.4      :  0.11.0 (OK)
jedi >=0.9.0      :  0.13.0 (OK)
nbconvert >=4.0   :  5.4.0 (OK)
pandas >=0.13.1   :  None (NOK)
numpy >=1.7       :  1.15.2 (OK)
sympy >=0.7.3     :  None (NOK)
cython >=0.21     :  None (NOK)
qtconsole >=4.2.0 :  4.4.1 (OK)
IPython >=4.0     :  7.0.1 (OK)
matplotlib >=2.0.0:  3.0.0 (OK)
pylint >=0.25     :  2.1.1 (OK)

This error will be fixed in our next release (3.3.2). In the meantime, please use Python 3.6 and not 3.7.

Problem persists using pip and python 3.6.6. Which 3.6 should I install so I don't get this error anymore?


Update Consideration.sol

Updated inline documentation readability.

Closing this for now, feel free to reopen with one where linters pass and comment's addressed!


Unable add nano scroll on body element?

I want ro add nano scroll on body element. But as per the docs, the structure should be

then how to add nano scroll on body element?

I don't think that having nanoscroller on body element is supported, the library is meant to be used with div elements. You can of course try to see if it happens to work with body + a div element.


Root View Controller gets changing after navigating from Main ViewController to another controller by push in swift

I have signup view in my application. After signup completes, I have Mainview Controller and I am making that as RootViewController with Slidemenucontroller.
Its working fine, but, after I am navigating from MainViewController to some other viewcontroller by doing push, once I pressed on Slidemenucontroller home button, its showing last pushed viewconroller instead of mainviewcontroller.
Even I set slidemenuviewcontroller with rootviewcontroller as Mainviewcontroller.
And I am using SlideMenuControllerSwift library to show slidemenu in my application.
Here is my code

    // create viewController code...
    let storyboard = UIStoryboard(name: "Main", bundle: nil)

    let mainViewController = storyboard.instantiateViewController(withIdentifier: "MainViewController") as! MainViewController
    let leftViewController = storyboard.instantiateViewController(withIdentifier: "LeftViewController") as! LeftViewController

    let nvc: UINavigationController = UINavigationController(rootViewController: mainViewController)

    let navigationBarAppearace = UINavigationBar.appearance()
    navigationBarAppearace.tintColor = UIColor.white
    navigationBarAppearace.titleTextAttributes = [NSAttributedStringKey.foregroundColor:UIColor.white]

    leftViewController.mainViewController = nvc

    let appDelegate = UIApplication.shared.delegate as! AppDelegate

    let slideMenuController = SlideMenuController(mainViewController:nvc, leftMenuViewController: leftViewController)
    appDelegate.window?.rootViewController = slideMenuController
    // slideMenuController.delegate = self as! SlideMenuControllerDelegate
    appDelegate.window?.makeKeyAndVisible()

How to fix this?

remove leftViewController.mainViewController = nvc line of code and always make root view controller in appDelegate class it may help to solve your problem.


Pixel wide gaps between adjacent UI nodes

Bevy version
main
What you did

use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_startup_system(setup)
        .run();
}

fn setup(mut commands: Commands) {
    let w = 100.3;
    commands.spawn(Camera2dBundle::default());
    commands.spawn(NodeBundle {
        style: Style {
            flex_direction: FlexDirection::Column,
            align_items: AlignItems::Center,
            size: Size::new(Val::Px(963.3333), Val::Percent(100.)),
            ..Default::default()
        },
        background_color: BackgroundColor(Color::WHITE),
        ..Default::default()
    })
    .with_children(|parent| {
        parent.spawn(NodeBundle {
            style: Style {
                justify_content: JustifyContent::Center,
                size: Size::new(Val::Percent(100.), Val::Percent(50.)),
                ..Default::default()
            },
            ..Default::default()
        })
        .with_children(|commands| {
            commands.spawn(
                NodeBundle {
                    style: Style {
                        size: Size::width(Val::Px(w)),
                        ..Default::default()
                    },
                    background_color: BackgroundColor(Color::NAVY),
                    ..Default::default()
                },
            );
            commands.spawn(
                NodeBundle {
                    style: Style {
                        size: Size::width(Val::Px(w)),
                        ..Default::default()
                    },
                    background_color: BackgroundColor(Color::DARK_GRAY),
                    ..Default::default()
                },
            );
        });
        parent.spawn(NodeBundle {
            style: Style {
                justify_content: JustifyContent::Center,
                size: Size::new(Val::Px(w * 2.), Val::Percent(25.)),
                ..Default::default()
            },
            background_color: BackgroundColor(Color::RED),
            ..Default::default()
        });
    });
}

A pixel-wide gap appears between adjacent nodes at certain node sizes.
The same gap appears vertically if you modify the example to reverse the flex-direction.

I think this is probably Taffy related. It seems to round the length of certain nodes but not others.
There are subtle problems with Bevy UI Text that are the same
What I think is happening is that you ask for a width of x pixels for your text with the MeasureFunc, but then Taffy rounds it down a pixel and so the Text no longer fits the width, so the last word of the text gets pushed down to a new line. But the Node itself stays at a height of only one line of text, so the text renderer doesn't draw the second line of text and it just looks there are missing words at the end of sentences with certain text layouts.

Hmm... I feel like the text renderer probably shouldn't count a glyph as fitting if it requires a partial pixel.

I think this is probably Taffy related. It seems to round the length of certain nodes but not others.

Taffy's rouding is pretty simple. It computes the entire layout using floats, and then rounds everything at the end.

I haven't really looked at this deeply yet, so I might be completely off. The scale factor code is all over the place, it might be something there. I'll recreate some of my examples just in Taffy and see what happens.

use taffy::prelude::*;

fn main() {
    for width in [963.3333, 1000.] {
        example(width);
    }
}

fn example(width: f32) {
    let root_style = Style {
        flex_direction: FlexDirection::Column,
        align_items: AlignItems::Center,
        size: Size { width: Dimension::Points(width), height: Dimension::Points(100.) },
        ..Default::default()
    };

    let parent_style = Style {
        flex_direction: FlexDirection::Row,
        justify_content: JustifyContent::Center,
        size: Size { width: Dimension::Percent(1.), height: Dimension::Points(100.) },
        ..Default::default()
    };

    let child_style = Style {
        size: Size { width: Dimension::Points(100.3), height: Dimension::Auto },
        ..Default::default()
    };

    let mut taffy = Taffy::new();
    let children = [
        taffy.new_leaf(child_style).unwrap(),
        taffy.new_leaf(child_style).unwrap(),
    ];
    let parent = taffy.new_with_children(parent_style, &children).unwrap();
    let root = taffy.new_with_children(root_style, &[parent]).unwrap();

    taffy.compute_layout(root, Size::MAX_CONTENT).ok();

    println!("Width = {width}");
    println!("root size: {:#?}", taffy.layout(root).unwrap().size);
    println!("parent size: {:#?}", taffy.layout(parent).unwrap().size);
    for child in children {
        println!("child layout: {:#?}", taffy.layout(child).unwrap());
    }
    println!();

I was able to reproduce in Taffy 0.3.2 as well:
use taffy::prelude::*;

fn main() {
    // First create an instance of Taffy
    let mut taffy = Taffy::new();

    let w = 100.3;

    let w_square = Size {
        width: points(w),
        height: points(w),
    };
    let child_a = taffy
        .new_leaf(Style {
            size: w_square,
            ..Default::default()
        })
        .unwrap();

    let child_b = taffy
        .new_leaf(Style {
            size: w_square,
            ..Default::default()
        })
        .unwrap();

    let root_node = taffy
        .new_with_children(
            Style {
                size: Size {
                    width: points(963.3333),
                    height: points(1000.),
                },
                justify_content: Some(JustifyContent::Center),
                ..Default::default()
            },
            &[child_a, child_b],
        )
        .unwrap();

    taffy.compute_layout(root_node, Size::MAX_CONTENT).unwrap();

    let layout_a = taffy.layout(child_a).unwrap();
    let layout_b = taffy.layout(child_b).unwrap();
    assert_eq!(
        layout_a.location.x + layout_a.size.width,
        layout_b.location.x
    );
}

I can see why this is happening. Unrounded results for @A-Walrus's test:
TREE
└──  FLEX [x: 0    y: 0    width: 963.3333 height: 1000] (3v1)
    ├──  LEAF [x: 381.36664 y: 0    width: 100.3 height: 100.3] (1v1)
    └──  LEAF [x: 481.66663 y: 0    width: 100.3 height: 100.3] (2v1)

child_a's x position is going to get rounded down. child_b's x position is going to get rounded up. It's not immediately obvious to me what the correct solution is though. Especially as I suspect the ideal solution would take into account the devicePixelRatio and round based on the size of physical pixels rather than logical ones, and perhaps even do subpixel rendering.
This quote quite neatly sums up the problem:

We’re trying to meet a bunch of constraints that can’t all be satisfied at the same time (the proof is left as an exercise to the reader, though I may have actually written it out once in a Bugzilla comment):

4 adjacent objects of width/height 25% (for example) starting at one edge of a container should end exactly at the other edge; there should never be an extra pixel in the container and they should never be wrapped due to being a pixel to wide
objects that are logically adjacent should always touch visually; there should never be a pixel gap or a pixel of overlap due to rounding error
objects given the same width should occupy the same number of pixels
object boundaries should always (visually) be aliased to a specific pixel boundary in the display (they should never be blurred)

The one [Mozilla] sacrifices is typically (3), except for borders where we sacrifice (1) by rounding the widths to pixel boundaries much earlier.

(https://johnresig.com/blog/sub-pixel-problems-in-css/)
I tried looking into what browsers do, but there seems to be no easy way to tell because they won't give you programatic access to the values used for rendering (getBoundingClientRect will give you the unrounded floats, and offsetLeft/offsetWidth will give you values Taffy is already computing with the 1 pixel gap even though there isn't actually a 1px gap in the final render).

Yep, I understand now I think, the size of the root node doesn't matter. If you add another node to the example that wraps the two nodes it will be 201 pixels wide, it just depends on how it is aligned as to whether the extra pixel either ends up between or on the side of the two nodes.

This is issue is now fixed in Taffy and can be fixed in Bevy by upgrading to the latest Taffy (v0.3.3). This will require https://github.com/bevyengine/bevy/pull/7485 to be merged either first, or as part of the upgrade. The approach in this branch of disabling the grid feature for the initial upgrade is probably a sensible one.


Notice: Undefined index: unwatch in /vagrant/mediawiki/skins/2018/includes/Skin2018Template.php on line 18

Likely just needs a call to isset

1434a549cac869c9dcb5643c085d5258ff39a45a

1434a549cac869c9dcb5643c085d5258ff39a45a


Incorrect Positioning of InputAdornment on IE 11

On IE 11, the InputAdornment on the end of a  TextField is not positioned properly.  The demo site section looks like this on IE 11:

whereas on chrome:

Tech
Version

Material-UI
1.0.0-beta.44

browser
IE11

The problem might occur between different versions of IE11. I'm closing as it's a duplicate of #10342. Let's keep things together.

That issue was marked as closed. Yet I didn't see it rendered correctly even with the IE version you used. As alexanthony pointed out:

@oliviertassinari Your screenshot shows the password field adornment in the wrong place - it isn't inside the field.


Websockets

I believe websocket support would be quite nice for this library. In a similiar, simple implementation.
Is this something that would be in scope?

For sure! I will finish the request part first tho


[ui] Update grammar in operator removal message

Signed-off-by: Joseph Midura<EMAIL_ADDRESS>Description
This PR fixes #3182
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Looks great, @josephmidura +1
@ramrodo, the Netlify failed build checks are examples of an errant failure. Ideally, we're not invoking a netlify builds when no /docs/* are changed as those builds are unnecessary. And in this case, their failed build checks are preventing the PR from being merged.

It seems there is another bug from Netlify builds. I'll check that this weekend to have all the tests green again.

Re-running Netlify checks...


Fix find xaptum tpm

The guards int eh FindXaptumTPM.cmake that ensure we only find XaptumTPM once were incorrect, meaning Xaptum-TPM would never be properly found! Things were only working because the xaptum-tpm directory was in the default location, I guess.

Coverage remained the same at 96.06% when pulling 3d667709017b5c97b9b63d03806abb1a23ad4c7f on zanebeckwith:fix-find-xaptum-tpm into 978f5a3e368ba25da48b94bfb50fba69c16af4b5 on xaptum:master.


GH-34262: [C++][ORC] Support union type

Rationale for this change
The ORC adapter does not support union type yet.
What changes are included in this PR?
Support union type to both ORC reader and writer.
Are these changes tested?
To be added.
Are there any user-facing changes?
No.

Closes: #34262

@westonpace @wjones127 Could you take a look please?

Does your test cover the read path?  Also, do you want a test with a dense union?

Does your test cover the read path? Also, do you want a test with a dense union?

Yes, I have added a roundtrip test for sparse union type. The read path of dense union will never happen because we always convert orc union to arrow sparse union type. Let me add a test case for batch conversion roundtrip of dense union to make it coverred.


Connect message names with RPC calls

On the control protocol page, we uses message names like "SIGNIN" etc. Now we use RPC calls with different method names.
One possibility would be to state, that "SIGNIN" stands for a rpc call for the "sign_in" method.

I think we should be consistent between message names and method names, that's easier to keep track of (less mental overhead keeping two slightly different designations in your head).

I adjusted the text in #56


Move get_or_create into sysdb

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

Current dependencies on/for this PR:

main

PR #1228

PR #1229

PR #1237

PR #1242   👈

This comment was auto-generated by Graphite.


Change max-pods-test to more general scheduler predicates test.

I'm running out of ideas as for why max-pods are failing. I want to add a test to check if we don't do resource overcommitement as well.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain eikaas.no has exceeded the max emails per hour (31/30 (103%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from github-smtp2-ext3.iad.github.net ([<IP_ADDRESS>]:56024 helo=github-smtp2b-ext-cp1-prd.iad.github.net)
by cpanel30.proisp.no with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.85)
(envelope-from<EMAIL_ADDRESS>id 1ZEfBT-003bYL-Rv
for<EMAIL_ADDRESS>Mon, 13 Jul 2015 16:58:21 +0200
Date: Mon, 13 Jul 2015 07:58:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1436799498;
bh=o5brYhrvsTSGW0pJQF04+sorGZcMACfvI1pvFMOB6Gg=;
h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=QiFvtUI+4cINbxZgxtcV+GlchAIYUncGoIJH1CMG29bx8av5G2hbgbGUnZw0TMDUJ
tRXhoaGarluuZnoQuSZUHyiQrj0ZRQPEYWzN9IrQTUvRa8QFQ8e4JsFpzc1ilzlUX2
7bi+nPThKeQEI2aMFLYATqo+23nhck/XSDAkJy9Q=
From: Kubernetes Bot<EMAIL_ADDRESS>Reply-To: GoogleCloudPlatform/kubernetes<EMAIL_ADDRESS>To: GoogleCloudPlatform/kubernetes<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [kubernetes] Add test that verifies that we don't allow resource
overallocation on Nodes. (#11151)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_55a3d20acc65d_7b5d3fc7092332b8268947d";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: k8s-bot
X-GitHub-Recipient: eikaas
List-ID: GoogleCloudPlatform/kubernetes
<kubernetes.GoogleCloudPlatform.github.com>
List-Archive: https://github.com/GoogleCloudPlatform/kubernetes
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AF9fZ1xQTm8PzYfVvlsM4uIMCpiwDxdqks5oc8mKgaJpZM4FXfsM
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-Spam-Status: No, score=-0.9
X-Spam-Score: -8
X-Spam-Bar: /
X-Ham-Report: Spam detection software, running on the system "cpanel30.proisp.no",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  GCE e2e build/test failed for commit 3af5815ae318c38c6689b07e7c6bcf771c97d50f.
* Build Log
* Test Artifacts
* Internal Jenkins Results
[...]
Content analysis details:   (-0.9 points, 4.0 required)
pts rule name              description

0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: github.com]
-0.0 RCVD_IN_MSPIKE_H4      RBL: Very Good reputation (+4)
[<IP_ADDRESS> listed in wl.mailspike.net]
-0.0 SPF_PASS               SPF: sender matches SPF record
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.0 HTML_MESSAGE           BODY: HTML included in message
1.1 HTML_IMAGE_ONLY_16     BODY: HTML: images with 1200-1600 bytes of words
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
-0.0 RCVD_IN_MSPIKE_WL      Mailspike good senders
X-Spam-Flag: NO
----==_mimepart_55a3d20acc65d_7b5d3fc7092332b8268947d
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
GCE e2e build/test failed for commit 3af5815ae318c38c6689b07e7c6bcf771c97d50f.

Build Log
Test Artifacts
Internal Jenkins Results

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/11151#issuecomment-120957819
----==_mimepart_55a3d20acc65d_7b5d3fc7092332b8268947d
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
GCE e2e build/test failed for commit 3af5815.

Build Log
Test Artifacts
Internal Jenkins Results

—Reply to this email directly or view it on GitHub.

----==_mimepart_55a3d20acc65d_7b5d3fc7092332b8268947d--

Maybe @bprashanth can review this
If he doesn't get to it tomorrow I can take a look

@gmarek it hasn't failed since the race pr went in right? think I only saw a few cluster bringup failures yesterday.

Yes - I wrote this PR yesterday, when this wasn't true yet. It's probably still a valid test, but maybe it's not worth it.

Sure,i'll review today

I feel like we can reuse a single test in a loop to validate cpu, memory and maxpods by just specifying different rcs. The pattern looks strikingly similar, create X pods, then create one, make sure the last on fails. Thoughts?
I also don't think this needs to go in for v1, it is like any other test, so removing the candidate label.

Yup. I agree, given that it's not needed quickly anymore. I'll rewrite max_pods given some time.

PTAL I put those two tests together and added NodeSelector test as well.

@bprashanth PTAL

LGTM sorry for the delay

@k8s-bot test this [contrib/submit-queue: candidate for merging]

@k8s-bot test this please [deflake attempt]

@k8s-bot test this [contrib/submit-queue: candidate for merging]

Automatic merge from SubmitQueue


Graphite db support for string data

Hi Team,
In my application, I am sending alot of data to Graphite database those values are numbers and that is working fine.
Now I want to send some values which are string and not number.
the question is : Does Graphite supports string data? As for as I understand from the documentation it looks like we can push only numerical data there.

Hi @mukeshhope
No, Graphite supports only numerical data.

Hi Deniszh,
Thankyou so much for quick reply


fix: Adjust query prefetching fetch policy to not bypass the cache

The type of this PR is: Bugfix

Description
Adjust query prefetching fetch policy to not bypass the cache.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against ad3df14b747e19f5e3df750de87e5fbf97ce42ba


automatic hyperlink using react-linkify

Added Linkify for announcements & questions for both instructors & students

Clicking on link in announcement navigates directly to link while clicking on link in question opens link in new tab. Is this intended behavior?

Oh yeah, that's something I wanted to ask you guys. Do you think it would be better to open on a new tab? (I think so).


OTP verification system project in Python

Describe the project you want to add with tech stack

I'd add an OTP verification system made in python which would firstly prompt user to sign in using gmail and then would send an OTP to their mail account. It would then prompt the user to type in the otp in the CLI. This way, the verification would be checked.
Expected behavior

User executed the program.
User is prompted to login in their mail in the browser.
When login is completed, the script would send an auto-OTP to their mail.
The user would then have to type in the correct OTP to get verified.

HI @pranjay-poddar @MohitGupta121 @TusharKesarwani please assign me this!


Fix bug where cardback doesnt empty

Fixes #163

Pull Request Test Coverage Report for Build 405

2 of 2 (100.0%) changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 87.603%

Totals

Change from base Build 404:
0.1%

Covered Lines:
2226

Relevant Lines:
2541

💛  - Coveralls


fix(config): use comma instead of semicolon as the default delimiter

To maintain consistency and use the same delimiter as the product-type-import module use a comma
instead of a semicolon to seperate the cells by default. This is also the default delimiter for the
CSV format.
Solves #1

Current coverage is 100% (diff: 100%)

Merging #5 into master will not change coverage

@@           master    #5   diff @@
===================================
  Files           3     3
  Lines         201   201
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits          201   201
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 0490fbc...da7d042

@hisabimbola suggested to add a test to see check if the delimiter falls back to a comma if no argument is given.

@PhilippSpo could you publish to npm?

@Siilwyn semantic-release 😎


Permission issue

"""       2021-10-13T20:55:57,530][INFO ][c.a.o.s.p.PrivilegesEvaluator] [008dac2d5e029914e] No index-level perm match for User [name=admin, backend_roles=[admin], requestedTenant=user] Resolved [aliases=[], allIndices=[], types=[], originalRequested=[], remoteIndices=[]] [Action [indices:data/read/search]] [RolesChecked [own_index]]      """
I am facing this issue, I am mentioning the permissions mentioned in roles.yml file for admin role.

allowed_actions:
- "indices:*"

- "indices:admin/create"

- "indices:admin/resolve/index"

- "indices:monitor/*"

- "indices:admin/*"

- "indices:admin/create"

- "indices:admin/mapping/put"

- "indices:admin/aliases*"

- "indices:data/*"

- "indices:data/write*"

- "indices:admin/mapping/put"

- "indices:data/read*"

- "indices:admin/mappings/fields/get*"

- "indices:data/write/delete*"

- "indices:data/read/search*"

"indices:data/read/msearch*"

- "indices:data/read/suggest*"

- "indices:data/write/index*"

- "indices:data/write/update*"

- "indices:admin/mapping/put"

- "indices:data/write/bulk*"

- "indices:data/read/get*"

- "indices:data/read/mget*"

- "indices:data/read/mget"

- "indices:data/read/msearch"

- "indices:data/read/mtv"

- "indices:admin/aliases/exists*"

- "indices:admin/aliases/get*"

- "indices:data/read/scroll"

- "indices:data/write/bulk"

- "indices:admin/aliases*"

- "indices:data/write/reindex"

static: false

even though there is a permission mentioned for  action "  indices:data/read/search   ", I am getting this error while trying to create an indices. Could you help me with this issue and guide me to the part where I am making a mistake,

I have the same issue after upgrading Opendistro 1.10.2 to 1.13.3
[2021-12-17T09:22:04,249][INFO ][c.a.o.s.p.PrivilegesEvaluator] [h161.company.com] No index-level perm match for User [name=kibanaserver, backend_roles=[], requestedTenant=null] Resolved [aliases=[*], allIndices=[*], types=[*], originalRequested=[*], remoteIndices=[]] [Action [indices:monitor/settings/get]] [RolesChecked [own_index, kibana_server]] [2021-12-17T09:22:04,249][INFO ][c.a.o.s.p.PrivilegesEvaluator] [h161.company.com] No permissions for [indices:monitor/settings/get]
Here is exerpt from my 'internal_users.yml':
kibanaserver:   hash: "$2y$12$K.........."   reserved: true   description: "Kibanaserver user"
Here is an excerpt from my 'roles_mapping.yml':
`kibana_server:
reserved: true
users:

"kibanaserver"
`

Here is an excerpt from my 'roles.yml'
`kibana_server:
cluster_permissions:

"cluster:*"
"indices:*"
indes_permissions:
index_patterns:

"*"
allowed_actions:
"indices_all"
"indices:*"
`

Could you please advise on identifying the issue?

This looks like a question for the security forum: https://discuss.opendistrocommunity.dev/c/security/3

So what was the answer? :\


[4.1] Activities on spells cannot bet set to not expend a spell slot

Also, as pictured, cannot scale with number of uses.

Doesn't seem to be the case. If you have the spell set to Prepared mode and "Consume Spell Slot" is unchecked it will still by used fine, but you will get the warning if you don't have any spellcasting slots at all because scaling is always based on a spell slots.

Doesn't seem to be the case. If you have the spell set to Prepared mode and "Consume Spell Slot" is unchecked it will still by used fine, but you will get the warning if you don't have any spellcasting slots at all because scaling is always based on a spell slots.

I don't think you should get a warning when casting a spell without spell slots if you don't have spell slots at the moment. After all, you don't need to have one. That seems counter-intuitive and likely to trip players up.


Colour of smoke test block in build pipeline does not reflect failed status correctly.

What are you trying to do? Run a build and see the status reflected in the blocks in the pipeline overview
Expected behaviour: If the smoke test failes causing an overall fail status in the pipeline, then the corresponding square in the pipeline should show  failed status
Observed behaviour:

This screenshot is despite the failure of riscv64-temurin_SmokeTests#14 triggered by jdk-evaluation-linux-riscv64-temurin#47 (it's the overview for jdk-evaluation-linux-riscv64-temurin where the screen shot above was visible)
Any other comments:

Related:

https://github.com/adoptium/ci-jenkins-pipelines/issues/234
https://github.com/adoptium/ci-jenkins-pipelines/issues/11

This issue has been frustrating me too! i'm working on a fix


spec: Unclear scope for platform section

In opencontainers/runtime-tools#347, @Mashimiao was reading the platform section as a restriction on platform.os.  Something like:

platform.os may have permissive SHOULD language for valid values, but you can ignore that.  Valid configs MUST be using one of these…

I read the spec.md section as a list of certification tracks:

Runtime-tools will have the following certification tracks: ….  platform.os allows many other values (e.g. android), and valid configs MAY use those (with questionable usefulness), but there is currently no certification track for them.

The spec should probably be updated to make it very clear which of these interpretations is intended.
With the restrictive approach (where platform.os == "android" was illegal), we should be using something like:
* **`os`** (string, REQUIRED) specifies the operating system family of the container configuration's specified [`root`](#root) file system bundle.
  The runtime MUST generate an error if it does not support the specified **`os`**.
  Bundles MUST use `linux`, `solaris`, or `windows`.

With the permissive approach, we should update the spec section to make it clear that it does not restrict platform.os.  And we probably want some notes about what happens in cases where platform.os does not match any of the certification tracks, even if that is “these other configs are possible, but because they have no platform-specific configuration settings, we don't think they are useful enough to be worth a certification track”.

@opencontainers/runtime-spec-maintainers  any comments?

Any thoughts?  I think clarifying the intention here will help with language if we decide to “preview” Windows (and Solaris?) in 1.0.


Some basic problems

Hi Mark, I tested the version you posted in Actions (warp: refactor identity creation)
1_ The first movie (when I enter the command warp-plus-4 and when we exit, the IPs are again broken and
and it connects with IP v6, while it should be connected with v4)
2_ The second movie (sometimes it brings IP v6 first, if there is a problem with the shatel and mci with ipv6 and the config doesn't connect)
3- The third movie (by entering the warp-plus -e command, when we want to change the IP and port, the IP does not change and the IPs of the boiler are connected).
https://github.com/bepass-org/warp-plus/assets/83357422/1b098495-0d6d-4a8e-855f-a8b5ac318d48
https://github.com/bepass-org/warp-plus/assets/83357422/cdf51788-5ab9-4c9a-9b2d-f1c03831d0d9
https://github.com/bepass-org/warp-plus/assets/83357422/7a39c97c-77ca-4e48-8c10-5c55a0e55313

Hi,
Every time you run the command, you need to give the full command. Even after exit, when you run again, you need to give the full command.
The best command I recommend you use is warp-plus --scan --gool

Hi,
Every time you run the command, you need to give the full command. Even after exit, when you run again, you need to give the full command.
The best command I recommend you use is warp-plus --scan --gool

Thanks for your Support ❤


Failing test: history__query_arguments__start_and_end_should_filter_messages_between_those_two_times

When run locally with make test_macOS and make test_iOS:
    ✗ history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, expected to be true, got <false>
    ✗ history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, expected to be false, got <true>
    ✗ history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, expected to have Array<ARTMessage> with count 2, got 0
    ✗ history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, expected to equal <m1>, got <nil> (use beNil() to match nils)
    ✗ history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, expected to equal <m2>, got <nil> (use beNil() to match nils)
    ✗ history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, Result is empty

[19:10:57]: ▸   history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, expected to be true, got <false>
[19:10:57]: ▸   /Users/quintin/code/ably-cocoa/Spec/RestClientChannel.swift:763
[19:10:57]: ▸   ```
[19:10:57]: ▸                     expect(error).to(beNil())
[19:10:57]: ▸                     expect(result.hasNext).to(beTrue())
[19:10:57]: ▸                     expect(result.isLast).to(beFalse())
[19:10:57]: ▸   ```
[19:10:57]: ▸   history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, expected to be false, got <true>
[19:10:57]: ▸   /Users/quintin/code/ably-cocoa/Spec/RestClientChannel.swift:764
[19:10:57]: ▸   ```
[19:10:57]: ▸                     expect(result.hasNext).to(beTrue())
[19:10:57]: ▸                     expect(result.isLast).to(beFalse())
[19:10:57]: ▸                     expect(result.items).to(haveCount(2))
[19:10:57]: ▸   ```
[19:10:57]: ▸   history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, expected to have Array<ARTMessage> with count 2, got 0
[19:10:57]: ▸   /Users/quintin/code/ably-cocoa/Spec/RestClientChannel.swift:765
[19:10:57]: ▸   ```
[19:10:57]: ▸                     expect(result.isLast).to(beFalse())
[19:10:57]: ▸                     expect(result.items).to(haveCount(2))
[19:10:57]: ▸                     let items = result.items.compactMap({ $0.data as? String })
[19:10:57]: ▸   ```
[19:10:57]: ▸   history__query_arguments__start_and_end_should_filter_messages_between_those_two_times, expected to equal <m1>, got <nil> (use beNil() to match nils)
[19:10:57]: ▸   /Users/quintin/code/ably-cocoa/Spec/RestClientChannel.swift:767
[19:10:57]: ▸   ```
[19:10:57]: ▸                     let items = result.items.compactMap({ $0.data as?  The codebase changed drastically since then and all skipped tests were unskipped, see PRs for https://github.com/ably/ably-cocoa/issues/1406 and https://github.com/ably/ably-cocoa/issues/1848
If you encounter frequently failing test again, please create a new issue with a best guess why it might be happening.


ATProto outbound: inReplyTo/object are create activity, not object

eg when a Mastodon post is the object/inReplyTo, the value is something like https://mas.to/users/me/statuses/123/activity, but it should be https://mas.to/users/me/statuses/123. Currently blocking ATP => fediverse interop.

I think 2be1229488a1da360f16d6b24784b65235aacf75 fixes this. Not sure though.


Ask: Publish Releases to Chocolatey

Summary of the new feature/enhancement
I love that the Terminal is now published to the windows store -- congrats on that great step!
To keep applications synced up across multiple machines and to ensure I can recreate machines quickly as needed, I'm a big fan of Chocolatey.
I'd love to be able to run choco install terminal, as I currently can for other terminal applications such as Cmder.

Proposed technical implementation details (optional)
Because a release pipeline already exists and appears to be published in yml (thank you for that, too!) I believe I could submit a pull request to add a release push to Chocolatey as well. I should be able to test locally.
I would be happy to publish this under my chocolatey account, but it seems like an opportunity to help Microsoft publish it in an official way as well.
Let me know if you are open to this idea and I will begin to explore it.

I think alternative paths for install other than the Store are important.
E.g. I couldn't get WinDbg Preview installed the other day as it was needed on an isolated server and needs the Store to install.
The Store is great.  When it's available.  But please make offline installers for tools available too.
Thanks

@pilcherd if you're interested in offline installers, you may wish to add that as a separate GitHub issue. I'd like to scope this purely to publishing to a Chocolatey feed, to ensure it doesn't grow in scope.

I'm going to make #1386 the master issue for alternate distribution mechanisms. Thanks!


Docker + wagtail + nuxt + API html_path

Found a bug? Please fill out the sections below. 👍
Issue Summary
It's a bit hard to explain. But I got the following issue:
When you use docker in combo with wagtail and nuxt I got an show stopper.
A common pattern is that the browser lands on a page ex. /homepage and you lookup in pages/find/?html_path=/homepage wagtail wil then redirect to the correct page.
Now when wagtail does this redirect it return the a full path example localhost
https://github.com/wagtail/wagtail/blob/master/wagtail/api/v2/utils.py#L13
https://github.com/wagtail/wagtail/blob/master/wagtail/api/v2/views.py#L92
But when using docker there are two ways to reach the wagtail container as you have server side rendering and client side rendering.
http:///django:8000 (server side)
http://localhost:8000 (client side)
Steps to Reproduce
start a docker django/wagtail
start a docker nuxt
create a api in wagtail
try to find a page in in api via SSR rendering
like so in nuxt
    asyncData({app, route}) {
      const path = route.path
      console.log(path)
      return app.$axios.$get(`pages/find/?html_path=${path}`)
        .then((res) => {
          return {somedata: res}
        })
    },

No nuxt will find the html_path but wagtail returns a path with the host that nuxt should read again and will fail there.
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Does anybody use Wagtail in combination with Docker and Vue/Nuxtjs that has similar issue and is there a work around?

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (yes / no)

Technical details
python 3.7
django 2.2
wagtail 3.7

@onno-timmerman This is a nice solution! However, won't it interfere with multi-site if anyone tries this solution? As far as I know, for every non-listed site, it will return the default site.
I use a setup exactly like your's except my container host is server instead of django. What I did is, I've created another alias site, with server as host and 8000 in port. It did the trick!


docs(package.json): add funding

$ npm fund
<EMAIL_ADDRESS>└── https://opencollective.com/katex
    └──<EMAIL_ADDRESS>

Codecov Report

Merging #3378 (3da0971) into master (9b7f10f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3378   +/-   ##
=======================================
  Coverage   93.54%   93.54%
=======================================
  Files          88       88
  Lines        6557     6557
  Branches     1513     1513
=======================================
  Hits         6134     6134
  Misses        393      393
  Partials       30       30

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 9b7f10f...3da0971. Read the comment docs.


Device template parameterization

Adding device type parameter to template

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/381


AWS spot instance termination notification marks node as unschedulable and starts draining it

I couldn't find anywhere if this is already implemented, if so, feel free to disregard this and close the issue directly.
It would be great if nodes that are running on spot instances are marked as unschedulable and drained upon a spot instance termination notification. The way to retrieve these notifications is described in this blog post.
The gist of it consists in having a process polling every 5s the URL http://<IP_ADDRESS>/latest/meta-data/spot/termination-time and, when it shows a time in the future, take actions to drain the k8s node.
You only get a 2 minutes heads up but it may allow for a clean shutdown of pods before the instance is terminated.

That would be great indeed, but i can imagine it's not that high up on the feature list yet.
First of all you'd want to prevent pods with a terminationGracePeriodSeconds value over 120 - (poll interval) - (some extra slack?) from being scheduled on spot instances. I guess the primitives are already there but you'd have to write your own scheduler & polling daemonset. :)

@mgilbir @pieterlange Thanks for the inspiration!
I've implemented it with simple shell-scripting. Rough around the edges but it seems to work.
https://github.com/mumoshu/kube-spot-termination-notice-handler
Just run kubectl create -f spot-termination-notice-handler.daemonset.yaml and it should work.

That's really cool! I like the simple implementation. And now that i think about it, i think one could currently set a node selector for pods that have a large terminationGracePeriodSeconds so they don't get scheduled on spot instances. Nice work :)

@mumoshu Wow, love that!
Stream Kitchen is going to need this feature too, but I'm not necessarily sure this repo is the right place for it? It seems like everyone that's using AWS Spot Instances for Kubernetes is going to run that kube-spot-termination-notice-handler or something similar to it as a cluster addon, irrespective of how the Kubernetes cluster got there.


Is there a file that lists the methods of blot?

I see const t = new bt.Turtle();
which leads me to believe this is a js implementation of turtle. OK,  cool. so  I tried some methods like penup() pendown() circle(n)
all of which failed. So I went to read more about the implementation of blots version of turtle, but have yet to find the documentation.
To be more specific, I do mean an online reference, something akin to:
https://docs.python.org/3/library/turtle.html
I did find the turtle implementation in the source code. penup() and pendown() are up(),  down()
I did not see implementations for shapes. Maybe I should write those.
Anyway, I think an online reference would be nice.
Alternatively, if the methods more closely matched the Turtle methods,  you could probably just use the python documentation.

https://blot.hackclub.com/docs

Very good, thanks!

Can you close this?


Fix Fuzz 2460

****************************************************************

libgrpc.so

     VM SIZE                                                             FILE SIZE
 ++++++++++++++ GROWING                                               ++++++++++++++
  +0.0%     +16 [None]                                                   +176  +0.0%

 -------------- SHRINKING                                             --------------
  -0.3%     -48 src/core/ext/filters/client_channel/client_channel.cc     -48  -0.3%
      -1.6%     -46 on_resolver_result_changed_locked                         -46  -1.6%
      -0.7%      -2 [Unmapped]                                                 -2  -0.7%

  -0.0%     -32 TOTAL                                                    +128  +0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE                                                             FILE SIZE
 ++++++++++++++ GROWING                                               ++++++++++++++
  +0.0%     +16 [None]                                                   +176  +0.0%

 -------------- SHRINKING                                             --------------
  -0.3%     -48 src/core/ext/filters/client_channel/client_channel.cc     -48  -0.3%
      -1.6%     -46 on_resolver_result_changed_locked                         -46  -1.6%
      -0.7%      -2 [Unmapped]                                                 -2  -0.7%

  -0.0%     -32 TOTAL                                                    +128  +0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[microbenchmarks] No significant performance differences


feat: bundle package deps as local packages

fix #652
fix #596

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-12-07T01:31:57.081+0000

Duration: 4 min 46 sec

Steps errors
Expand to view the steps failures

Check out from version control

Took 0 min 10 sec . View more details here
Description: [2022-12-07T01:34:57.521Z] The recommended git tool is: NONE
[2022-12-07T01:35:05.365Z] using crede

Check out from version control

Took 0 min 2 sec . View more details here
Description: [2022-12-07T01:35:17.885Z] The recommended git tool is: NONE
[2022-12-07T01:35:17.897Z] using crede

Check out from version control

Took 0 min 2 sec . View more details here
Description: [2022-12-07T01:35:29.722Z] The recommended git tool is: NONE
[2022-12-07T01:35:29.734Z] using crede

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

Closing this in favor of #687


Need to cancel twice in Export to Sheets/Rename player dialog

Open Export to Sheets dialog when not using Sheets
Click Cancel

or

Try to rename a player
Click Cancel right away

In both cases you expect the dialog to close, but validation fires first and prevents the window from closing. We should ignore the blur event in this case and just close the dialog.

Sadly this won't be easy to fix without redoing a lot of validation logic. Seems to be inherent to validating on focusOut. Won't fix for now.


Fix wrong example output of float*Color in classref

Alpha was not correctly multipied.
Use the same # Prints "XXX" format as other examples.

Thanks!

Cherry-picked for 4.1.3.


LootTracker: Loot Drops From Server are in Reverse Order

Describe the bug
When reloading the client the drops that are loaded from prev sessions are in reverse order
To Reproduce

switch loot tracker to individual kill
Kill a mob
kill another mob
restart runelite
open loot tracker and see drops have been reversed

Expected behavior
the loot tracker should always have the same order of drops
Screenshots
Kill Order:
rabbit -> guard -> guard
Loot Tracker before reloading runelite:

Loot Tracker after reloading runelite:

Loot Tracker after killing imp after reload:

Expected:
(top -> bottom)
imp -> guard -> guard -> rabbit
Environment (please complete the following information):

OS: Windows 10
RuneLite version: <IP_ADDRESS>
Launcher version: 1.6.0

https://github.com/runelite/runelite/blob/08fed6dba1771a6ac86dcd99d3964e1be8601d7d/http-service/src/main/java/net/runelite/http/service/loottracker/LootTrackerService.java#L69
i'm not 100% sure but I believe the fix for this would be either:

change the SELECT_LOOT_QUERY from "...ORDER BY TIME DESC" to "...ORDER BY TIME ASC"
or
it's because TIME is uppercase (this depends on if the database used is case-sensitive)

We want the last X entries, so selecting by descending is correct.

oh yes you are corrent, I was thinking of trying to reorder the ones selected. not the entire drops table. mistake on my part.


Add domain on transforms

This adds a domain key to all transforms.
@nden: If this makes sense to you, I'll go ahead and add an implementation in pyasdf (which would just stuff the information in meta.domain until astropy.modeling grows support for this).

I think this is good for now. Thanks.


11TA submission to 11ty.dev Starter Projects

Thanks in advance for considering my 11TA Template System listing on the Starter Project page. 😄

Thank you!

Thank YOU @zachleat for 11ty!! 😃


feat: add search param to list function

A simple non-breaking change that adds the new search param (added in https://github.com/supabase/storage-api/pull/127) to the list function.

@alaister could you update https://supabase.com/docs/reference/javascript/storage-from-list as well please?

Oops, I didn't realised that supabase/storage-api#127 hadn't been merged yet. Since @joshenlim said it worked locally, let's just merge, deploy to staging and test there?

Sounds good to me!


[WIP] Align CSS with VUI

Screenshots
Light mode

Dark mode

CC @eskibars @danielone Still a work in progress, just giving you a head's up. Feedback welcome!

@eskibars @danielone @pwoznic This is ready for review!

Note that the styles have evolved past the point at which the screenshots were taken. To see the latest changes please run this branch locally.

This change is cosmetic so I'm going to merge it. It will be trivial to revert this change if we need to.


KYLIN-4306: Delete data model desc when encountering WriteConflictExc…

…eption
see: https://issues.apache.org/jira/browse/kylin-4306

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@27df350). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #1006   +/-   ##
=========================================
  Coverage          ?   25.51%
  Complexity        ?     6178
=========================================
  Files             ?     1416
  Lines             ?    85972
  Branches          ?    12059
=========================================
  Hits              ?    21934
  Misses            ?    61902
  Partials          ?     2136

Impacted Files
Coverage Δ
Complexity Δ

...apache/kylin/storage/hbase/HBaseResourceStore.java
0% <ø> (ø)
0 <0> (?)

.../apache/kylin/metadata/model/DataModelManager.java
30.43% <0%> (ø)
11 <0> (?)

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 27df350...2cb8bd8. Read the comment docs.


Unable to run the tests

First I clone the project
git clone https://github.com/jhipster/jhipster-vuejs.git
I run
npm install
I can't run test : npm test, I get :
    Default with Maven
      1) "before all" hook
    Default with Gradle
      2) "before all" hook
    noi18n with Maven
      3) "before all" hook
    Elasticsearch and Protractor
      4) "before all" hook

  0 passing (873ms)
  4 failing

  1) VueJS JHipster blueprint
       Default with Maven
         "before all" hook:
     Uncaught Error: ERROR! The generator-jhipster-vuejs blueprint provided is not installed. Please install it using command npm i -g generator-jhipster-vuejs.
      at Environment.error (node_modules/yeoman-environment/lib/environment.js:157:40)
      at module.exports.error (node_modules/generator-jhipster/generators/generator-base.js:2444:18)
      at shelljs.exec (node_modules/generator-jhipster/generators/generator-base-private.js:794:22)
      at /Users/arnaudfreismuth/Documents/Ippon/jhipster-vue/jhipster-vuejs/node_modules/shelljs/src/exec.js:124:9
      at ChildProcess.exithandler (child_process.js:301:5)
      at maybeClose (internal/child_process.js:978:16)
      at Socket.stream.socket.on (internal/child_process.js:395:11)
      at Pipe._handle.close (net.js:616:12)
[...]

npm ERR! code ELIFECYCLE
npm ERR! errno 4
npm ERR<EMAIL_ADDRESS>test:unit: `mocha --timeout 20000 --slow 0 --reporter spec "test/client.spec.js"`
npm ERR! Exit status 4
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:unit script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/arnaudfreismuth/.npm/_logs/2018-12-06T15_49_25_481Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 4
npm ERR<EMAIL_ADDRESS>test: `npm run test:unit -- test/*.spec.js`
npm ERR! Exit status 4
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/arnaudfreismuth/.npm/_logs/2018-12-06T15_49_25_535Z-debug.log

You need to install yo: npm install -g yo
Thanks @sahbi-ktifa !

You need to install yo: npm install -g yo
Thanks @sahbi-ktifa !

It works, great!


json_dumps real value 7.6 as 7.59....96

Behavior:
$ gcc main.c -Iinclude -Llib -ljansson -Wl,-rpath,lib
$ ./a.out
7.5999999999999996
$ ls lib
libjansson.a  libjansson.la  libjansson.so  libjansson.so.4  libjansson.so.4.14.0  pkgconfig
$ ls include/
jansson_config.h  jansson.h
$ cat main.c
#include <jansson.h>

int main()
{
  json_t *j = json_real(7.6);
  printf("%s\n", json_dumps(j, JSON_ENCODE_ANY));
  return 0;
}
$ ldd ./a.out
        linux-vdso.so.1 (0x00007ffd2ff7d000)
        libjansson.so.4 => lib/libjansson.so.4 (0x00007f2f8b45b000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2f8b220000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f2f8b472000)

Steps to reproduce:

download latest release from github: https://github.com/akheron/jansson/releases/tag/v2.14
configure with --prefix="/my/current/path"
make && make install

I first noticed this with the jansson lib installed in ubuntu via apt, so this should exist in 2.13, as well.

This is probably due to the fact to 7.6 not being presentable as a float in binary.
https://en.wikipedia.org/wiki/Floating-point_arithmetic
You can use the call JSON_REAL_PRECISION().
Thereby you force the internal use of the printf() family to round the number and that will "hide" this effect.
I have the same issue. Doesn't everybody when placing prices in json with c-code.
Normale you could als send a price multiplied with a 100 so you send the prices as cents.
But when using this in a API then the other party had to agree to do it like that.
Using JSON_REAL_PRECISION() had the disadvantage that it is for all "real"; so they are all rounded the same way and that is not always desirable.
I've tried to make a change for this. To the real object I added a precision. So with each real stored in json_t you can use  a function that also allows you to set the precision for that specific number.
I've still to test it. But maybe I can get it accepted here as a change

@wqboth you're right :) I hope you'll forgive my ignorance on this one. I had heard about this issue, but had never understood it. I can close this now.

I only made some spelling checks. I'm not a native speaker of English. So sometimes some corrections need to be made.

I will read the information in the url you just gave.
But indeed I do need a very specific formatting for floats. For example the numbers for prices may demand a different precision(variable number of decimals) than weights or other numbers.
This also has the advantage that you have control over binary non presentable numbers like 0.15. Because of the implicit rounding it will nicely be presented as 0.15 and not 0.1499999999....
That is why I created a branche of jansson with a proposition to a solution as you might have seen?

https://github.com/ulfjack/ryu does have somenthing in common.
I can see that this could be a used in printf()?
Or a replacement of printf() in jansson?
But even than I would like to have control over the precision per individual float value.
To put it accurately there are two issues. One is the fact of numbers not being presentable and wanting to have more control over the precision. The fun thing is that when you have control over the precision you "hide"/"solve" the other issue implicitly.

I've opened #680 that changes encoding of reals to output optimal values, i.e. no 7.599999... anymore. There's still a bit of work to do with the tests, but you can already check if it fixes your use case.

This does indeed work for my use case:
$ ./a.out
7.6

Thank you.


Add Silero models for de and es

Hi @maringeo
Please see 2 more models added

Hi @snakers4 , the PR looks good. It is possible to sync this PR past d4fe081f823b6d9096f716135fcacd4a3237cc77 (this commit aims to resolve an external report that the model table in https://tfhub.dev/silero/collections/silero-stt/1 had an extra line that did not render correctly)?

Hi @maringeo I removed this line for better rendering
Please take a look
https://github.com/tensorflow/hub/pull/684/commits/80631cad27adc6fb5443030438e3ee40f4df6785

Hi @snakers4, the models are live on tfhub.dev:

https://tfhub.dev/silero/silero-stt/es/1
https://tfhub.dev/silero/silero-stt/de/1

This PR has been merged in 0a782de8c604e52a8d5531e902d4650ade58287f.


Removed clear button container ID

As part of #319:

Removed ID from ClearButton container element
Updated corresponding unit tests

👍


why partial views for ajax grids

Hello,
just a quick question ?
is it necessary to use partial views for ajax grids ?
or we can just use a normal view ?

Yes you have to use partial views, because otherwise you would be rendering your page inside the grid's container.


Master -> Live

Docs Build status updates of commit 2a289e4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/sf-academy-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 9cd9376:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/sf-academy-events.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Controller and Action Implementation in Autorace Map

UPDATE 1

Created a controller to follow the lines of the automap world

To-do

Implement an action server and action client that use the controller to complete the track

UPDATE 2

Implemented the action files and a launch file to call the action server, action client and controller

@eborghi10 @ernestmc @serraramiro1 @LucasJSch please review

Action Server and Action Client implemented and working
Added comments on Robot Controller file


Metal: Implement fix for non vector4 texture Load/Sample

fixes: #4405
The change modifies stdlib to ensures all metal texture read/sample uses swizzle their vector<T,4> output into the same parent element type of __TextureImpl

Fixes solve the current issue with buffer-swizzle-store.slang for 'metal' target (partially solves #4291)
Added test cases to texture.slang to cover all types

Note: this PR relies upon changes from #4408
(made a separate PR since this PR is very simple despite changing lots of code)


✨ Begin SQL insert with best practice

issue: #64
I just improving code with best practices as I know 😅
Recap

OOP support on our CSV to SQL Insert
Terminal input (like, fileName and destination location name etc)
File handling hooks
Response handler
Fully readable and understandable clean code
String validator
and more.... 🎁

Note: I have written "TODO" which I left for someone else to work on.

@gitdagray I requested you review my code, sir...

@jsvigneshkanna I hope this marge will help us to grow our project. what is your opinion??

I think increased code splitting like this increases the readability of the code and increases testability too

@Klock85 thank you mate


[Dashboard Removal] Migrated Dashboard

This PR removes the migrated dashboard page from the repository.
This is not the old dashboard contained within cartodb. That one will be removed in another PR.

This migrated dashboard page is within lib/assets/javascripts/dashboard and its entry point is dashboard.js.
This dashboard page is not used anymore because of the new dashboard has been put in place. So, it's time to clean it.
The dashboard bundle was compiled with Webpack and its dependencies were defined in:
https://github.com/CartoDB/cartodb/blob/9659826d96d41dca346622188622af806ef6d07b/webpack/v4/entryPoints.js#L22-L27
So, doing an static analysis, we got the dependency files to remove that were detailed in https://github.com/CartoDB/product/issues/289 and removed in this pull request.
The removal is safe because we discarded the files being used in dashboard and other entry points so that we don't remove them causing a failure when building the bundle.
https://github.com/CartoDB/product/issues/289

retest this please

This PR is ready to review 🎉
It'd be great if @javitonino can give it a look just in case I missed something to remove and review the FF removal.
And for the FrontEnd part, I invoke @rjimenezda as we worked on the dashboard migration to give it a look.
cc/ @VictorVelarde

retest this please

🔥🔥🔥🔥?

It is the first stage, but yes, the migrated dashboard is no longer there :)

👏 👏 👏


K8s updating service selectors doesn't update ingress controller

Rancher Versions:
Server: rancher/server:v1.5.0-rc1
kubernetes (if applicable):
1.5.2-rancher1-3
Testing Blue Green Deployments with service selectors:
Yaml:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: webserver-blue
spec:
  replicas: 3
  template:
    metadata:
      labels:
        type: webserver
        color: blue
    spec:
      containers:
        - image: cloudnautique/hello-world:light
          name: webserver-hello
          ports:
            - containerPort: 80
              name: http-server
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: webserver-green
spec:
  replicas: 3
  template:
    metadata:
      labels:
        type: webserver
        color: green
    spec:
      containers:
        - image: cloudnautique/hello-world:dark
          name: webserver-hello
          ports:
            - containerPort: 80
              name: http-server
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: webapp
spec:
  backend:
    serviceName: webserver
    servicePort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: webserver
spec:
  ports:
    - port: 80
      targetPort: 80
      protocol: TCP
      name: http
  selector:
    type: webserver
    color: blue

performing kubectl edit svc webserver and chaging color to green doesn't result in an update to the ingress controller.

We should check if:

change of selector on k8s triggered change of selector on the service in cattle (selector_container field in instance table)
if selector got changed, check if endpoints for the service in cattle got updated to the new ones.
if everything above worked, check if it triggered haproxy reload with new port rules

Selector was updated on the service in Rancher, the bug is that the update wasn't carried via process.data like it happens when you update selector via API, so the update didn't trigger selector evaluation:
https://github.com/rancher/cattle/blob/060bd6b0104a21ea7221ea5ad17d5696fdb26a29/code/iaas/service-discovery/server/src/main/java/io/cattle/platform/servicediscovery/process/SelectorServiceCreatePostListener.java#L75


Don't assume that method bodies produce the correct tuple type already

It's possible that the method body returns a subtype of the return type.
For example, a return value with type ((U32, U32) | (U32, None)) is
legal for a method with return type (U32, (U32 | None)), but it
requires a cast.
071db1051b01b02a1224867c5bdbae3983634231 changed that methods returning a tuple always use a cast as if the method body's value already has the return type. Unfortunately, it doesn't go into detail why. This already caused an issue in #849 and an exception was added if return type and body type are both tuples. I think that assumption doesn't hold: for the above mentioned case, the return type is a tuple, but the body type is an union, and yet the current code continues as if the body produces a tuple.
Fixes #2609, #2808

@Trundle on a roll!

Hi @Trundle,
The changelog - fixed label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do.
Release notes are added by creating a uniquely named file in the .release-notes directory. We suggest you call the file 3723.md to match the number of this pull request.
The basic format of the release notes (using markdown) should be:
## Title

End user description of changes, why it's important,
problems it solves etc.

If a breaking change, make sure to include 1 or more
examples what code would look like prior to this change
and how to update it to work after this change.

Thanks.

Confirmed that #2808 is fixed by this.

Confirmed #2609 is fixed.

I'll hold tomorrow's ponyc release until this has release notes and is merged.
Thanks @Trundle.

@Trundle I think "Fix tuple related compiler segfaults" would be a good release notes title.

I've added release notes.

Thank you for adding the release notes, @SeanTAllen. They contain a slight mistake though: the crash happens in the compiled code, not the compiler itself. Is it worth fixing and if so, how does it work? Should I open a new PR with changes to 0.39.0.md?

@Trundle yeah go ahead and then I'll update the release page as well.


Example Github Page With Video

This looks like a great idea. Can we please see a Github page with an embedded video using this so we can see how it works?

Hi, this project aims to add the possibility to link a video on the markdown using a generated image that looks like a video player.
So you can have a markdown with a video that looks like an embedded one.
Just like this:

Using GitHub Pages you are hosting a static website. In this case, you can directly embed a video from Youtube or any other sources without using video-to-markdown.
Instead, if you just want a link to the video on your website, you can download the generated image from video-to-markdown and use it inside your website.
Let me know if this answers your question.


pythonPackages.pymysql: 0.6.6 -> 0.9.2; move to python-modules.

Motivation for this change
Updating pymysql required by mycli. See https://github.com/NixOS/nixpkgs/pull/44571.
I also moved the package to the new location under //pkgs/development/python-modules/pymysql.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

included in #44571


Add tests for create-staked

As witnessed by @carlhammann here, it would be nice to add tests to the new create-testsnet-data command.
Since this new command is a variation on create-staked I propose to start add a few tests to create-staked, which I will then be able to port over to create-testnet-data very easily.
This will allow us to check that the two commands behave the same and transition smoothly from one to the other.
Both for create-staked and for create-testnet-data, we can check the shape of the genesis.json file, which is related to the values passed to the command's CLI flags. Checking the content of generated files will require a bit of boilerplate, because the content is not entirely stable (so you can't golden check everything), not sure it's worth the effort, but I gotta check if there is some nice general property about each folder.

Done most of it in https://github.com/input-output-hk/cardano-cli/pull/498, but keeping this one open, because the test for create-staked is a bit more complete than the one for create-testnet-data and I want to revisit the latter.


failed to open stream: Permission denied

Out of date ?

I don't have a subscription active, so i cant test. sorry

Closing, working good at the moment.

Having Same Problem, Tried on 2 different versions ubuntu server:
====================================
Starting Collecting the data

216 new lessons and 496 episodes. 5.841s elapsed with 3.25Mb of memory usage.

====================================
Authenticating

Successfull!

====================================
Downloading Lessons

Download started: prevent-spam-with-recaptcha . . . . Saving on lessons folder.
ERROR: Unable to open ./lessons/0216-prevent-spam-with-recaptcha.mp4 using mode r+: fopen(./lessons/0216-prevent-spam-with-recaptcha.mp4): failed to open stream: No such file or directory

@HelKyle check if php5-curl extension is installed.


Converting a JSON to SAV seems to corrupt some characters

One player can't log back in my server. I suspect a character corruption. So I delete the .sav file associated with the player and modified the Level.sav to remove every instance of his GUID in the file. there was only 2. I convert the JSON back to sav using your tool, everything went well. I logged back in my character the world was working, my character was there, however 2 other player had lost their character. One was showing online in the game but has a UUID 0000000.
If you need my sav file to test stuff, I can provide them. I can help you debug stuff. I'm a software dev, but no experience with python. I can probably run the app in debug mode and check stuff. Anyway let me know what I can do to help fix this.

I know when I was converting back and forth with uesave the only thing I was seeing were single byte changes from floating point numbers.

Yeah, I'm trying to compare the correct level.sav.json with the level.sav.json after converting to sav then back to json. But... VSCode don't like files with 1M rows lol

Compare them with code. I ran through the code with python and compared byte by byte. I printed the lines where the bytes were different.

Went back into the file to analyze more stuff, and noticed that I left some stuff related to the players. deleted, those, converted to sav file, and seems to work just fine.