ASCII/Braille writing support.

Acknowledgement of preliminary instructions

[x] I have read and acknowledged the preliminary instructions.

What idea do you have?
Can you make roblox support braille writing /ascii?
imma be honest, the reason I want this is to use fflags to make my roblox say
"                          No Internet?
⠀⣞⢽⢪⢣⢣⢣⢫⡺⡵⣝⡮⣗⢷⢽⢽⢽⣮⡷⡽⣜⣜⢮⢺⣜⢷⢽⢝⡽⣝
⠸⡸⠜⠕⠕⠁⢁⢇⢏⢽⢺⣪⡳⡝⣎⣏⢯⢞⡿⣟⣷⣳⢯⡷⣽⢽⢯⣳⣫⠇
⠀⠀⢀⢀⢄⢬⢪⡪⡎⣆⡈⠚⠜⠕⠇⠗⠝⢕⢯⢫⣞⣯⣿⣻⡽⣏⢗⣗⠏
⠀⠪⡪⡪⣪⢪⢺⢸⢢⢓⢆⢤⢀⠀⠀⠀⠀⠈⢊⢞⡾⣿⡯⣏⢮⠷⠁
⠀⠀⠀⠈⠊⠆⡃⠕⢕⢇⢇⢇⢇⢇⢏⢎⢎⢆⢄⠀⢑⣽⣿⢝⠲⠉
⠀⠀⠀⠀⠀⡿⠂⠠⠀⡇⢇⠕⢈⣀⠀⠁⠡⠣⡣⡫⣂⣿⠯⢪⠰⠂
⠀⠀⠀⠀⡦⡙⡂⢀⢤⢣⠣⡈⣾⡃⠠⠄⠀⡄⢱⣌⣶⢏⢊⠂
⠀⠀⠀⠀⢝⡲⣜⡮⡏⢎⢌⢂⠙⠢⠐⢀⢘⢵⣽⣿⡿⠁⠁
⠀⠀⠀⠀⠨⣺⡺⡕⡕⡱⡑⡆⡕⡅⡕⡜⡼⢽⡻⠏
⠀⠀⠀⠀⣼⣳⣫⣾⣵⣗⡵⡱⡡⢣⢑⢕⢜⢕⡝
⠀⠀⠀⣴⣿⣾⣿⣿⣿⡿⡽⡑⢌⠪⡢⡣⣣⡟
⠀⠀⠀⡟⡾⣿⢿⢿⢵⣽⣾⣼⣘⢸⢸⣞⡟
⠀⠀⠀⠀⠁⠇⠡⠩⡫⢿⣝⡻⡮⣒⢽⠋⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ "
when I disconnect.

Can you make roblox support braille writing /ascii?

Unless you use a font that supports it then no


DIsappearing data with default retention policy

Hello. I have a few influx instances that simply use the default retention policy , and I am seeing data disappear after I insert more data

select count(value) from prism_latencies where time > now() - 2d
name: prism_latencies

time                    count
1456924319006500360     4.263355e+06

select count(value) from prism_latencies where time > now() - 2d
name: prism_latencies

time                    count
1456924581862548266     3.43473e+06
I'm not seeing anything logged that explains this.

@pbooth This only shows that the number of points inserted in the 48 hours immediately preceding each query is different. A better query for demonstrating that a loss has occurred is to use a fixed date in both queries. So:
select count(value) from prism_latencies where time > '2016-03-03 00:00:00'
That said, @jwilder did fix a point deduplication issue in #5719 which may also be relevant. This fix was delivered in v0.10.2 which was released today.

You can see from the time delta that the two queries were entered in close proximity.
I'll see if I can reproduce in a standalone fashion. This keeps occurring so shouldn't be too difficult.
I do know that my upload method can cause points to be double entered and entered out of order. On related point, when moving Data between DB with SELECT INTO I had repeatedly seen this until I created explicit retention policies.
QN: Is there an upper limit on the number of points in a series?
Sent from my iPhone

On Mar 4, 2016, at 8:33 AM, Jon Seymour<EMAIL_ADDRESS>wrote:
@pbooth This only shows that the number of points inserted in the 48 hours immediately preceding each query is different. A better query for demonstrating that a loss has occurred is to use a fixed date in both queries. So:
select count(value) from prism_latencies where time > '2016-03-03 00:00:00'
That said, @jwilder did fix a point deduplication issue in #5719 which may also be relevant. This fix was delivered in v0.10.2 which was released today.
—
Reply to this email directly or view it on GitHub.

@pbooth The only technical limit on points per series should be the available disk space.
Were you able to come up with a set of steps to reproduce losing data, or is this just a case of double-counted points getting removed by deduplication?


README

README
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

README committed on 8/16.


Added support for Rust HashMaps

Added support to parse Rust HashMaps
Implemented support for typescript

Currently we return a result to std::io::Result instead of our own error type, so I'm mapping an invalid map (one which doesn't contain at least 2 comma separated types) to std::io::ErrorKind::InvalidInput.
I've only implemented maps in typescript. I'm hoping folks with more knowledge in the other languages can implement maps there if possible.

I can help with the Swift side unless someone beats me to it


docs, network binding: The use of CNI plugins

What this PR does / why we need it:
When there is a need to change the pod network namespace, CNI plugins can be used by a network binding.
The part CNI has in creating a network binding is described in a new section named "The Complete Plugin".
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

NONE

change: Answered review comments.

change: Answered review comments.

/approve

Hi @brianmcarey
I think that this PR is a corner case for phased plugin
when lgtm + approve made on draft, undrafting wont trigger the jobs, tide will do that eventually so we are good
but if we want to fix this case we can

@EdDev The PR is lgtm/approved. Please undraft it.


[Feature request] Support for custom Session Tags and Session Name

Feature request
Ability to configure Custom Session Tags and Custom Session Names for STS sessions created by EKS Pod Identities.
Context
Currently it's not possible to configure neither Custom Session Tags^1 nor Custom Session Name^2.
This makes it impossible to implement certain use-cases where I need to configure IAM policies based on custom IDs, rather than supported values of:

eks-cluster-arn
eks-cluster-name
kubernetes-namespace
kubernetes-service-account
kubernetes-pod-name
kubernetes-pod-uid

This also helps with MSK's IAM policy. The MSK server gets angry and de-auths you when your session name changes. So your MSK connection is alive and well for the initial X hours. When pod-identtity-agent assumes a NEW STS role when the old expires, the session name changes, which causes MSK to kick you out. The error you get is about principals changing. The fix is to set AWS_ROLE_SESSION_NAME, which isn't possible w/ pod-identity
https://github.com/aws/aws-msk-iam-auth/issues/104

linking to aws roadmap in case it helps https://github.com/aws/containers-roadmap/issues/2362


Use the latest version of the GOV.UK Accessible autocomplete

Description
This version includes fix for a bug that prevented users from clicking on options in certain circumstances.
https://github.com/alphagov/accessible-autocomplete/releases/tag/v2.0.2
Checklist

[x] Tested against our testing policy (Resolution, Browser & Accessibility)
[x] Follows our coding standards and style guide
[x] CHANGELOG entry

LGTM 👍


Fix prerequisites table

Fix to the prerequisites table because the prerequisites table was displayed as a code block

Thanks, @tksh164 !


Install redis-sentinal package before redis

Pull Request (PR) description
When the redis-sentinal package was installed it could
alter previously applied requested permissions and ownerships
of files.
Ensure that redis-sentinal package is installed before directory
permissions and ownerships are set.

@traylenator do you want to fix the typo (earier -> earlier) in the commit message? Or even copy what I did with the PR title?


Feedback

The goal of this library is to have drawn controls with Cupertino, Fluent and Material support for Android, iOS, macOS, Windows and Linux. The idea is to have high performance pixel perfect controls offering the same rendering and behavior across platforms.
The list of initially supported controls will be the controls included in Xamarin.Forms Visual with the same properties and events: Button, Slider, Entry, etc.
Your feedback is welcome!

@jsuarezruiz Firstly, you are doing a nice work - keep it up. Could you produce a NuGet package so we can test the library? Thanks

I like it! How easy will it be to extend or change the controls compared to the handler/renderer approach?
It would also be nice to get a couple of navigation controls that in combination with the MVU paradigm could be used to implement a flutter-esque SPA architecture that does not use the current XF page concept.  I'm thinking of drawn replacements for NavigationPage, TabPage, Flyout page + new ones that gives emulates modal popups, hero navigations, etc.
As I see it, it is only important to make sure that we can still use high-performance native control abstractions like CollectionViews and CarouselViews, or use native controls that somehow relies on important platform features like accessibility, special keyboards, maps, etc. But there should be no reason why these native abstractions can't live in some new drawn navigational framework.

Hi! The gold standard for cross platform is when you can do the major platforms and web. Uno tackles this with WASM, could these controls be made to work?
Very excited to see drawn controls. Accessibility is obviously the priority, followed by functionality, performance (and style-ability?)

Thank you all for the feedback.
@saint4eva Having a simple way to test is definitely a better way to get feedback. For now, you can sync the repository and try the sample. Later we can generate NuGet packages on GitHub. It will be when progressing more with  https://github.com/dotnet/GraphicsControls/blob/master/STATUS.md
@timahrentlov I have updated the README with an example of how it will be to create a drawn control or modify an existing control.
Will include specific examples of custom controls or an existing control by customizing how to draw any of the layers.
The initial idea is to have all the controls available in Visual Xamarin.Forms:

ActivityIndicator
Button
Check box
DatePicker
Editor
Entry
Frame
Picker
ProgressBar
Slider
Stepper
TimePicker

Later, yes, more possibilities can be added.
As for reaching new platforms, yes, it makes it easier. Using native controls, require a renderer to map each abstract view with a native control. In this case you only need to decide how to render on the platform (Example: Linux can use Cairo, SkiaSharp) and create the renderer for the Canvas used on that platform.
@webprofusion-chrisc These drawn controls are based on System.Graphics. In System.Graphics there are implementations for Blazor (WebGL) https://github.com/dotnet/System.Graphics/tree/5754007eb4d52cf1dc6dbdb25a44d159f97782d8/src/System.Graphics.Blazor
It could be possible.

I really enjoyed the concept because from simple things + your imagination you can build amazing things, and at the same time you don't loose performance. Also I enjoyed the video where you explained step by step the concept and how to build a control you made the task fun, it is very helpful and wish to see more maybe a part 2. I was wondering whether it is possible to access to the Canvas somehow inside an event (example keydown.. or any) in order to maybe redraw a part of shape upon some condition/user interaction, or it is not necessary, other ways to achieve that maybe?

We want this!
This is a great project. There is a huge demand for platform-independent rendering which is always blocked by the history of Xamarin. This library could end up becoming the best option for the majority of XF/Maui developers, allowing them to:

Avoid things looking different on different platforms
Avoid platform-dependent bugs
Depend on a higher quality repo since contributions improve all platforms and there isn't the noise of some UI doesn't work on some platform.
Support further platforms easily e.g. the web

Suggestion: focus on plain manually-styled controls first

Cupertino, Fluent and Material

We would not want any automatic styling: only plain styling unless indicated otherwise by specifying explicit properties. These design systems don't interest us at all, but presumably they are optional things at the periphery of this library? I would highly recommend working getting feedback on the standard controls until they are very polished, before splitting off users who want to use one of these design systems, to avoid similar problems to those above (design-systems look different, design-system-dependent bugs, noise of managing x controls on y design systems...).
[Speculative] How far can this go?
In theory Xamarin.Forms/MAUI View objects render to/are handled by GraphicsControls objects, which then render to native graphics. I wonder if XF/MAUI could then be taken out completely, and we could work directly with GraphicsControls?

@jsuarezruiz Hi, good work!
Neumorphism is a new design style!
Please consider this style as well
Some UI UX with Neumorphic

This is such great work!
I was researching the other day about things like this. I know that MAUI currently has no plan to target web, but this could change so much. A lot of web apps are slow and heavy, but if this could work with WebGPU (which is much faster then WebGL) and Web Assembly, web apps could be running at near native speed. And people can finally stop using Electron just because it aligns the code base for all platforms (except mobile, but THIS does all platforms including mobile, so it's even better in that regard).
So my question is: Could this work with WebGPU and Web Assembly? MAUI and Comet are all trying to provide as much choice as possible (in terms of how controls are rendered), so experimenting on those frameworks may need to consider/implement a lot before seeing any result. So I think it could almost be beneficial to assemble some building blocks from either MAUI or Comet to have a drawn control only framework where it can target any platform including (and also most importantly) web.
Flutter has gained a lot of popularity because of this (among other reasons), but I think this could be something for the .NET ecosystem. And WebGPU running on Web Assembly could be much faster than transpiling to JavaScript (which is what Flutter does I think)

We also need some gestures.

This library should be officially be supported by Microsoft . I know that it is a lot of work but with just 2 contributors ( Javier is one and the other 3 looking at the commits still fall behind so counting as 2) this library is already really good.
I don't think we need design parity perfection (even if it would be welcomed) but the benefits on performance side would make it worth the investment.
For both Android and iOS the way Xamarin/.Net for iOs and Android drawing the controls in the runtime where we are coding (.Net) and not having proxy's to the native one (reference count or worst Java GC) should bring a real boost in performance.

Hello when will you create nuget package?

@kerberosargos By implementing animations and other small pending details. I would say that in the next few weeks the first package will be ready.

@jsuarezruiz Thank you for your effort.

@jsuarezruiz How to add prefix and suffix text for Entry(Material)? Is it possible? Or need to create a new control?

I really like the idea of drawn controls! Hopefully more effort will come here in future.
I am not sure how layouting of controls will be solved. If I want to use this package on native platform and web, I cannot use StackLayout and others as they are part of .NET MAUI right? So if we want this to be independent of MAUI we need to handle layouting as well. Is this also the target of this project?

@listepo Could be possible but not already implemented.
@Martinn2 Yes, at the moment is using the .NET MAUI Layouts, so have some dependencies for now. The initial goal is to have solid, stable, high-performance, easy-to-customize pixel perfect controls. After complete this first milestone (Cupertino, Material and Fluent), other options could come. And using SkiaSharp in Linux, WebGL for the web etc would be an option and the point you indicate should be covered first.

I love this library. My UIs are 99% the same between platforms.
I did something similar for myself a couple of years ago, but it was only for some tasks.
And I really liked that approach.
I don't want to bother with the native UI when I don't need it.
Especially complex shadows. Especially complex elements.
It would also be great to be able to create my complex components. Which sometimes I need to draw from primitives and sometimes I need to use Layouts and it would be nice to have one UI component as a result.
For example:
9path button. As we understand it is made from a Grid divided into 3 rows and 3 collumns.
And as I understand in the current implementation I will really have a Grid and 9 elements.
And I would also like the ability to combine this into one View (or Canvas).
That is when these Grids will only exist in the drawing math of the Skia control. but for the application it will just be one Canvas.
<GraphicsGrid>
    <GraphicsGrid.Rows>
       ...
    </GraphicsGrid.Rows>

   <Rect Grid.Row="1" />
   <Rect Grid.Row="2" />
   <Rect Grid.Row="3" />
   <Button Grid.Row="4"/>

</GraphicsGrid>

I think that such a thing would increase the performance.
And open up the possibility to create your own lists and any other Skia-based components. And that way we can make our answer to Fluiter.

I love this!! It is so often that we need to tweak the UI to get a consistent experience across platforms.

@IvoKrugers Using https://visualstudio.microsoft.com/vs/mac/preview/ you could get to compile etc, although details are still missing to have the same level as in Windows.

There are two main questions I have about this approach:

Accessibility

Extensive performance comparison compared to the native controls (for example compare the time to display a drawn Button to a native Button) on all the platforms (because in the context of cross-platform of at least iOS and Android, it doesn't matter if it works well on iOS if it's bad on Android, or viceversa)

It won't suffice to throw some simple performance comparisons, the difference will be very small with a single control, but it's very different when there's 10 labels, 3 buttons and also using layout controls (Grid, StackLayout, etc.)

There are two main questions I have about this approach:

Accessibility
Extensive performance comparison compared to the native controls (for example compare the time to display a drawn Button to a native Button) on all the platforms (because in the context of cross-platform of at least iOS and Android, it doesn't matter if it works well on iOS if it's bad on Android, or viceversa)

It won't suffice to throw some simple performance comparisons, the difference will be very small with a single control, but it's very different when there's 20 labels, buttons, images, all using layout controls (Grid, StackLayout, etc.), etc. Also, take into account things like alignment (you want text on a Button to be left aligned, etc.) or gradients on different button states.
There's also another thing: With custom drawn controls you don't get the native support for different features. If Apple or Google wants to have some special feature on some controls, they will never be available for these drawn controls or if some it will be possible, it will be complicated to implement it.

All the drawn controls use a native canvas that have a native view as parent. We already map the a11y options related with the screen reader taking advantage of that native part. High contrast colors, for example, would use another totally different implementation, it would rather detect the use of high contrast (today, for example, the change of theme is detected) and adjust colors, etc.
About performance, there are differences depending on the control. In general the difference between loading a page with a single native control or a single drawn one is low. The difference is noticeable with 100 or 1000 controls for example. Loading 100 Material Entries using a Compatibility Custom Renderer vs drawing (the entry using Handler reduces the difference).

At the UI level everything can be adapted in some way. At the behavioral level there are more complex aspects or would require more effort. For that reason, there are also hybrid control implementations. These are controls where the UI is drawn but has parts depending on native. Example: Entry: draw background, icons, etc but when selecting text and allowing copy or paste content, use native.  https://github.com/dotnet/Microsoft.Maui.Graphics.Controls/blob/main/src/GraphicsControls/Handlers/MixedGraphicsControlHandler.cs

At the behavioral level there are more complex aspects or would require more effort. For that reason, there are also hybrid control implementations. These are controls where the UI is drawn but has parts depending on native. Example: Entry: draw background, icons, etc but when selecting text and allowing copy or paste content, use native.

Yes, that's the kind of big challenges I was referring about, which on long term need a lot of maintenance.

it may be time to set up a call with a few of us to show you guys some of the things the fluidsharp library can do and discuss how this might help your efforts

@wouterst79 Sure thing, just write me an email and we can organize a meeting :)

i've sent a mail, and have updated my e-mail on github just in case

@wouterst79 Sent an email with a proposal for a meeting, let me know if that is fine for you :)

Hey Javier, it was nice meeting with you today!
I have summarized the user (developer) benefits of using "FluidSharp" as follows in the past:

A high performance mobile first multi-platform UI layout framework.
Built on top of Skia, just like Chrome and Flutter.
Integrates with Xamarin Forms, Xamarin.Android, Xamarin.iOS, WinFormsCore and more.
Use it as a view, or to draw your whole app (including navigation containers).
Edit and continue support for a better "hot reload" experience.
Full multi-language and RTL support.
Lots of in-built widgets (that are drawn by the framework) - Textbox uses native controls.
Great for both simple, and complex views like grids and search results.
Easy to extend with your own layouts; make any UI that you can imagine!

As discussed, from my perspective, there's definitely advantages of drawing controls instead of relying on the OS:

Much better performance (possible)!
Much richer UI
Better cross-platform parity (and better Windows support)
Faster UI development turn-around
Better UI thread management
Reduces some of the problems of XAML (full "binding" breakpoint support)
Less black-box code
Good migration path for existing C# based applications.

I'll look forward to discussing some of these benefits with the larger product team.

This is such a great project. I do hope this will be the future of MAUI. Drawing the controls is the way to go and would enable such "crazy" things like having a Web version of MAUI using WebAssembly. Skia is already available as a wasm library and at least in theory such a thing would be possible. Kind of hybrid between Blazor and MAUI.
HUGE potential!

We want this!
We are looking for Material style controls in MAUI like xamarin. You are doing a nice work. Keep ir up.

Layout system, we have implement layout system :)

I love this so much! And 'From Figma to AlohaKit UI' is amazing! 🔥🤩
I hope it gets out of Experimental phase soon. 😊

Great work.
Windows is missing for me in the NuGet package


Add debugging support

Adds support for debugging playbooks using the ansibug library. This allows users to launch a debuggable playbook through this extension or attach to an existing playbook process launched by ansibug.
This requires https://github.com/jborean93/ansibug to be installed in the Python environment used by the extension. We need to have a conversation around whether this should be bundled with this extension or whether the user supplies it themselves. We could support both with the bundled version being a fallback. For now it just needs to be manually installed with
python -m pip install ansibug

Fixes: https://github.com/ansible/vscode-ansible/issues/760

I think this PR is ready for a proper review. Please let me know what might be missing or needs to be fixed up so I can get it ready to be merged.

@nitzmahone Considering the upcoming changes in core, please advise if we want to get this in as experimental and rewrite it once core changes get implemented. I do think that there is a lot of interest in playing with this feature.

not a lot of interest ???? use so many jinja template scripts that a debugger would be a lifesaver for me as we all know syntax errors for jinja are the opposite of useful, and ib general I want to know what the output of those script into playbook variables look like, so a ansible playbook debugger is an absolute necessity
and I'm not talking of a python debugger used to debug ansible somehow

Closing as we decided to delay implementing this in extension until ansible-core receives native support for debugging, anyone can try using https://marketplace.visualstudio.com/items?itemName=jborean.ansibug

Big changes coming in 2.18 to the guts of our Jinja integration that make diagnosing template issues easier- we can now track the provenance of all vars, and we've majorly overhauled the bookkeeping we do during templating, so a lot of problems that used to just silently fail are now loudly in your face, with error messages that can show you the entire template stack that was running when the problem occurred. A number of those things are already accessible through Jordan's ansibug VSCode Ansible debugger prototype in currently-released Ansible, and a lot more capabilities will be accessible once the debugger hook support is properly integrated in core.


integrations: Switch BigBlueButton over to SHA256.

This commit switches the BigBlueButton integration
to use SHA256 instead of SHA1 as BigBlueButton supports
it and scalelite does now, too.
This is regarding to #19966
Testing plan:
Tested this with a BigBlueButton server: worked
Tested with Scalelite: did not work
Scalelite has just recently merged this into master.

Merged, after tweaking the commit message to auto-close #19966; thanks for doing this!


xroute import is very inefficient

injecting 16000 routes ate a core 3 cpu for all of the 5 minutes I had it going. We've discussed how to go about improving xroute support in the past, and I've got a better patch for filtering stuff out sooner already, but the core is a better qsort. To this day I don't get the whole "route_stream" idea....

the new code is nlogn and much faster. The problems move over to the resend routines mostly, and we do have issues getting the kernel route table out fast enough.


[Concurrency] Add an environment variable to validate unchecked continuation usage.

When enabled, we track all active unchecked continuations in a global set, and fatal error if one is called twice.
This commit also removes swift_Concurrency_fatalError in favor of exporting swift::fatalError from libswiftCore as SPI so that libswift_Concurrency can use it. This gives us better error messages and crash reporting for fatal errors in libswift_Concurrency.

@kateinoigakukun I saw you added swift_Concurrency_fatalError, will there be any problem with removing that in favor of exporting swift::fatalError as SPI and calling that?

@mikeash As Doug told me in my PR, swift::fatalError is not exported by older swiftCore, so simple linkage against it in Concurrency runtime would break back-deploy, I think.
https://github.com/apple/swift/pull/37084#pullrequestreview-646122992
Unfortunately, this breakage would be happened by concurrencyValidateUncheckedContinuations also.
If we want to add dependencies on newer swiftCore's symbols, we need to guard the use of newly exported symbols like here, or add the impls of those symbols in back-deploy library.
CC: @DougGregor

The fatal error stuff was causing too much trouble and didn't belong here. I've removed that and rebased the rest of the PR on top of main.

@swift-ci please test

I didn't realize this PR was from a branch in the main repo! I rebased and made a new PR based on my own fork here: https://github.com/apple/swift/pull/61076


Separate Requirements from Text

Document Improvement Suggestion:  In general, if we can pull the requirements from the "flavor" text, it will be easier for those implementing to determine what are just best practices (that may not be called out by SHOULD) and what are actual requirements.

#186 does a lot of the work on this


Blazor Server App Short Name Changed in 3.0.0-preview7.19365.7

Getting Started step #3 uses the command dotnet new blazorserverside -o WebApplication1 for .NET Core CLI; however, the short name in this preview version is blazorserver.

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

ID: c07e57dc-526f-9479-4695-de7d8f06eb9a
Version Independent ID: 8226ed72-69b2-3c93-a931-218bd11cf9c8
Content: Get started with ASP.NET Core Blazor
Content Source: aspnetcore/blazor/get-started.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @Just2Sour ... That will be for Pre8. We have it on https://github.com/aspnet/AspNetCore.Docs/pull/13536.


Documentation Question - mount point element ID for web

Hi,
I tried to search both the documents and examples but didn't find answer to below, I hope someone can direct me to the resource.
As per Web documentation, i.e.:
https://dioxuslabs.com/reference/platforms/web.html
Quote:
"Make sure your "mount point" element has an ID of "main" (this can be configured later)"
How can I change that? Or specify a different "id" name for my "div" tag?
Thanks

https://docs.rs/dioxus-web/0.2.1/dioxus_web/fn.launch_cfg.html
https://docs.rs/dioxus-web/0.2.1/dioxus_web/struct.WebConfig.html#method.rootname
sorry I'm on mobile

@rMazeiks - thanks for your help.
I will give it a try and comment back here (and close this ticket if it works).

It worked! I will close this ticket.
I used below for testing:
   dioxus::web::launch_cfg(app, |config| config.rootname("main_app"));


Improve ping

Add that ability to wait for a pong and get the payload.
Add a heartbeat recipe that uses wait_pong() to check/keep the connection alive.
Implement heartbeat in the example client.

Closing this because I merged #58 as the preferred alternative to this PR.


Proposal: Change key 'resource' to 'relation' in hasOne/hasMany object param.

If it's still the case that the optional {resource: 'direct-reports', type: 'employees'} isn't documented (much/well) I want to suggest to rename the resource property of that object to relation. So:
Resource.extend({
  directReports: hasMany({relation: 'direct-reports', type: 'employees'}), // suggested
  // directReports: hasMany({resource: 'direct-reports', type: 'employees'}) // current
});

2 reasons:

Calling it resource is confusing since we're defining Resources all over the place, but that is not what it means in this case.
The related-proxy stores this value as relation. Which is what we end up using internally. meta.relation.

Many times there isn't really a resource (either defined in terms of ember-jsonapi-resources or defined in terms of a JSONAPI url/resource to request) by this name. It is the name of the relationship a Resource has with some other Resource of a certain type. As defined by type.
To illustrate using urls:
http://api.pixelhandler.com/api/v1/supervisors/1/relationships/`resource`
vs
http://api.pixelhandler.com/api/v1/supervisors/1/relationships/`relation`
would make more sense since:
http://api.pixelhandler.com/api/v1/direct-reports does not exist. It is not a resource.
(I'll be happy to do the work for this. Including changes to docs)

@aars yes I agree the relationship link used to fetch the resource uses a relationship name. From the spec, "related resource" is what we're talking about operating on using a "relationship link" see http://jsonapi.org/format/#document-resource-object-relationships
I am in favor with using "relation" for the argument object property with the relationship helper.
I'm also curious if the helpers should be named toMany and toOne instead of hasMany and hasOne the nomenclature here:

http://jsonapi.org/format/#crud-updating-to-many-relationships
http://jsonapi.org/format/#crud-updating-to-one-relationships

We could keep the hasMany and hasOne as aliases as well.

I'd like to add this as a 2.0 item


gis.search() runs forever without any results or errors

Followed the installation and credential generation guide.
GoogleImagesSearch() instantiations runs without errors.
gis.search() with num=10 runs forever without errors or results.
What can be wrong?

Hey @Nika-St! Can you provide an example of a query you're trying to execute that stays running forever?


[BUG] Generate CLI code doesn't work on my machine unless the executable path of Genesis.CLI.dll is surrounded by quotation marks

Starting "Generate CLI Code" results in a "unexpected error occurred" "Code generation failed, process exited with code 1"
If I copy the dotnet command from the log message and run it in Command Prompt I get the error "Specify which project file to use because this 'E:\GameDev\Builderdam Workspace\BuilderDam' contains more than one project file."
If I add quotation marks around the path of the Genesis.CLI.dll the command works and if I change 			SB.Append(GenesisPreferences.GetExecutablePath()); in line 224 and 257  in "GenesisCLIRunner.cs" to
SB.Append("\"" + GenesisPreferences.GetExecutablePath() + "\"");
"Generate CLI Code" works
Unity Version:
Unity 2020.3.27f1
To Reproduce
Steps to reproduce the behavior:

Place the Genesis.CLI folder in a path with a white space
Update the path in the Genesis preferences
execute Tools ->JCMG->Genesis->Generate CLI Code

Expected behavior
Generate code completes and produces no error
Additional context
Win10

Hi @ashwin911 ,
I was able to reproduce this issue with CLI executable paths not being formatted correctly if they had a space in the folder name. I have fixed this in the way you've described along with an additional unrelated bug for a case-sensitive argument for executing a dry run. This has been merged to develop, is in Genesis v2.4.4, and should be available shortly on OpenUPM for installation. Meanwhile I will be shortly updating the Genesis min version for Entitas Redux to this version.
When you have a moment please attempt to repro this and report both, otherwise I will be closing this issue on Monday.


psh: add umount applet

Description

Added umount applet to psh.
Motivation and Context

JIRA: DTR-101
Types of changes

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

How Has This Been Tested?

[ ] Already covered by automatic testing.
[ ] New test added: (add PR link here).
[x] Tested by hand on: armv7a7-imx6ull

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing linter checks and tests passed.
[x] My changes generate no new compilation warnings for any of the targets.

Special treatment

[x] This PR needs additional PRs to work (list the PRs, preferably in merge-order).
https://github.com/phoenix-rtos/libphoenix/pull/224
[ ] I will merge this PR by myself when appropriate.

Had to dismiss the approval due to wrong psh_mount_info() return type.


fyi: ingestor tree parsing

We agreed that in the long term, the ingestor would need to have a way to communicate information up/down the tree in order to make edges and annotations between the elements of each node in the document tree.
However, to get started with an e2e poc, we decided to defer the implementation of the recursive processing model.
Relevant Conversation:
https://github.com/guacsec/guac/pull/39#discussion_r956089252
https://github.com/guacsec/guac/pull/39#issuecomment-1229180454
https://github.com/guacsec/guac/pull/39#issuecomment-1231897400

This issue is no longer required due to the new GraphQL ontology and discussions to move trust to a separate plane (https://github.com/guacsec/guac/issues/75)


Fixed cleanup.sh script according to the requirements, squashed to a single commit.

Signed-off-by: Konstantin Rybalko<EMAIL_ADDRESS>

@rybalko Thank you for posting this new pull-request!
There is no problem with the content of the pull-request itself and this was already approved by two maintainers.
But the code checking tool is running now. After that this pull-request can be merged. I'm going to merge this PR after the tool finishes to check.
Could you wait for a while until this PR is merged?

@rybalko The merge was done now. Thanks for your contribution!


change accessTokenAcceptedVersion to 2 and iss still be https://sts.windows.net/{id}/

I install keycloak-proxy on AKS and then I meet some questions.
{"error": "oidc: JWT claims invalid: invalid claim value: 'iss'. expected=https://login.microsoftonline.com/{id}/v2.0, found=https://sts.windows.net/{id}/."}
I have already change accessTokenAcceptedVersion to 2

but when I get my jwt, it still unchanged

how can I solve this problem, thanks a lot.

@qinmaye Please fill out the issue template, we cannot answer your question effectively if we don't have the information there.


Customize Expiration?

Not really an issue, just a question... is it possible to set a custom expiration on the token, or set it to nil?

Great question.
Yes. After you install the initializer by running:
rails generate devise_jwt_auth:install User auth

You can modify the default settings in the file:
config/initializers/devise_jwt_auth.rb

You have two settings that you can modify. config.refresh_token_lifespan and config.access_token_lifespan. The refresh token is meant to be a long lasting token (maybe 1 to 2 weeks? Maybe more depending one what you're needs are). The access token should be much shorter. Only a few minutes long.
Setting either token's life span to nil will actually cause an error but even if it made your tokens to never expire, this would give someone an authentication token that would never expire and that's probably not ideal. I should probably just set the tokens to expire immediately if someone did this. Something to work on in the future.
Sorry for this confusion with the configuration settings. I need to add this final installation step in the README file. There is a USAGE documentation file but I need to have it print out properly.
I'm going to be making some changes to the library soon so its compatible with Rails 7. A lot of auth libraries that depend on Devise were waiting for Rails 7 support but its available now.


Tests skipped if command nginx not in PATH

Use case:
remote system Debian 7.x
tests executed via ssh using normal user account (it is in sudoers but tests are run without sudo).
nginx is not in PATH because it is in /usr/sbin/.
Altering code to:
 command('/usr/sbin/nginx').exist?
starts to work.
Using sudo work as expected, but I'd like to minimize exposure of the password ( thinking about passwordless sudo account...)
I'm not sure if altering the test suite in such way is suggested solution?

@nvtkaszpir the main target for this test is to check the implementation for chef cookbook, ansible playbook and the puppet manifest. This test ensure the right implementation for the different automation frameworks.
Can you please explain the sudo usecase a bit more?

Yes I know it's for checking if different configuration management tools produce the same output.  That's why I want to use it. I can mix it with current packer provisioning toolset, or add as another service for inspecting existing infra if it conforms the compliance.
The problem is with the way the test is executed - the test assumes that command('nginx') exists for the user which invokes the test, which actually checks if nginx is within PATH for specified account. So for example for root (or user in sudoers using sudo) it will work. Otherwise it will be skipped, because nginx command is not present within PATH env var.
Now how can we execute the test:

copy scripts to the server, and execute it (similar to how serverspec does it) - this is ok if you are creating image which is not used for production yet,
remote execution - using for example ssh - and now things get complicated, depending on the way it is done, especially if remote machine has limited access.

Let say I've got some other servers I'd like to test, and I have set up sudo account on them. To perform the test on those servers I would have to use:
inspec exec test-suite<EMAIL_ADDRESS>--sudo --sudo-password guesswhat
Above is fine if it is used locally, but for example running it from jenkins can result in password leak, if not handled properly.
The things gets even more complicated if I'd like to provide specific persons access to the servers, but in rather limited scope, for example auditors.
Now there are few options, and I wonder which one to choose:

test could be rewritten so that it does not really need sudo (at least for major part of tests)
create new account on remote hosts with passwordless sudo for specific commands (actually this would mean dig through all test suites to see what commands are executed), but still would need specific ssh keys available to jenkins - as a result I could run inspec exec test-suite<EMAIL_ADDRESS>--sudo with empty password
run on privileged account but in a totally separated manner, for example as jenkins build which would output html table with filtered output (to hide any typical jenkins console output)
run something like a separate agent to execute tests (I guess chef does it now?) and produce reports

First solution is really dependent on the way system is configured and prepared (there may be some other issues with different operating systems like custom install paths etc.), but for me looks most reasonable, especially if test suite should be as portable as possible.
Just an open discussion, trying to think how to do the stuff in our setup :)

OK, I think this is out of scope of the project, this is more like a matter to think about when dealing with inspect itself and not this test suite. Closing.


Hw03_bytyquil.py

This is the source code for assignment 3 that draws the image requested.

Rejecting PR because you edited a03_stubs.py instead of creating a new file.


Update README.md

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

nameAdd


Jupyter notebooks fail (regression) - in all environments local/docker-compose/k8s

The jupytyer notebooks are currently failing both locally and in docker compose.
One the user opens up the jupyter web UI the following warnings start flooding the jupyter container's output log, and the python interpreter fails to initialise, meaning the notebooks fail completely
ui_1         | 2020-06-23 11:54:48.669  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8443 (https) with context path ''
ui_1         | 2020-06-23 11:54:48.694  INFO 1 --- [           main] o.o.o.u.u.springboot.EgeriaUIPlatform    : Started EgeriaUIPlatform in 82.697 seconds (JVM running for 88.325)
notebook_1   | [I 11:57:08.201 LabApp] 302 GET / (<IP_ADDRESS>) 1.22ms
notebook_1   | [I 11:57:10.792 LabApp] Build is up to date
notebook_1   | [I 11:57:15.824 LabApp] Writing notebook-signing key to /home/jovyan/.local/share/jupyter/notebook_secret
notebook_1   | [W 11:57:15.826 LabApp] Notebook egeria-server-config.ipynb is not trusted
notebook_1   | [W 11:57:16.371 LabApp] 404 GET /images/coco-pharmaceuticals-systems-omag-server-platforms.png (<IP_ADDRESS>) 53.06ms referer=http://<IP_ADDRESS>:18888/lab?
notebook_1   | [W 11:57:16.373 LabApp] 404 GET /images/coco-pharmaceuticals-systems-metadata-servers.png (<IP_ADDRESS>) 53.98ms referer=http://<IP_ADDRESS>:18888/lab?
notebook_1   | [W 11:57:16.377 LabApp] 404 GET /images/creating-configuration-documents.png (<IP_ADDRESS>) 1.99ms referer=http://<IP_ADDRESS>:18888/lab?
notebook_1   | [W 11:57:16.378 LabApp] 404 GET /images/deploying-configuration-documents.png (<IP_ADDRESS>) 2.86ms referer=http://<IP_ADDRESS>:18888/lab?
notebook_1   | [I 11:57:18.948 LabApp] Kernel started: 23483a1e-d3a2-439d-87d9-1251522eb458
notebook_1   | [I 11:57:19.938 LabApp] Starting buffering for 23483a1e-d3a2-439d-87d9-1251522eb458:a0cdb09a-0018-46c6-a04f-2aa12f4b409e
notebook_1   | [I 11:57:20.043 LabApp] Starting buffering for 23483a1e-d3a2-439d-87d9-1251522eb458:a0cdb09a-0018-46c6-a04f-2aa12f4b409e
notebook_1   | [I 11:57:20.110 LabApp] Starting buffering for 23483a1e-d3a2-439d-87d9-1251522eb458:a0cdb09a-0018-46c6-a04f-2aa12f4b409e
notebook_1   | [I 11:57:20.162 LabApp] Starting buffering for 23483a1e-d3a2-439d-87d9-1251522eb458:a0cdb09a-0018-46c6-a04f-2aa12f4b409e
notebook_1   | [I 11:57:20.235 LabApp] Starting buffering for 23483a1e-d3a2-439d-87d9-1251522eb458:a0cdb09a-0018-46c6-a04f-2aa12f4b409e
notebook_1   | [I 11:57:20.302 LabApp] Starting buffering for 23483a1e-d3a2-439d-87d9-1251522eb458:a0cdb09a-0018-46c6-a04f-2aa12f4b409e
notebook_1   | [I 11:57:20.366 LabApp] Starting buffering for 23483a1e-d3a2-439d-87d9-1251522eb458:a0cdb09a-0018-46c6-a04f-2aa12f4b409e
notebook_1   | [I 11:57:20.430 LabApp] Starting buffering for 23483a1e-d3a2-439d-87d9-1251522eb458:a0cdb09a-0018-46c6-a04f-2aa12f4b409e

There was a jupyter container update 5 days ago, which is a possible cause.
Investigating ....

Near Identical failures across all environments
Sometimes the 'starting' errors don't occur, but in all cases the jupyter kernel fails to initialise

In order to eliminate any files we add to the image (we build a custom image which uses jupyter as the base but adds a python module or two, and the notebooks) I ran:
docker run -p 28888:8888 jupyter/base-notebook:latest

I then did New->Python 3
.. and get the same error.
So the notebook base image is broken.,
Currently we use the tag 'latest' - the last sensibly named image seems to be 'lab-2.1.1' (currently 2.1.3 seems to be latest). Will also check/report to jupyter team

Further investigation - this was actually browser specific (safari, customised). Reverting to defaults and problem does not occur, nor in chrome. Will update if I discover exact reason, but it was only this particular browser....


Connecting with Hasura when getting user session

I'm very excited about this project as it seem to significantly simplify auth flow.
I'm using Google provider and Hasura is my backend (Graphql on top of Postgres). Do I need to use an Adapter to do user operations in my use case? Right now it says in the docs that Adapters are intended for the library authors.
Should I not be using nextauth just yet or I can still make it work somehow?
Thanks for your hard work!

Closed after finding callbacks in the docs.


McMMO Suport Issue

Seems to be a problem turning McMMO support to "true" instead of default "false"
Upon players joining it completely removes the scoreboard after 5 seconds and players are forced to activate with /sb toggle to "ON" when for some reason it's "OFF" to begin with, even though RealScoreboard-Disabled-By-Default: false

Will look into when I have time, thanks

Hi, just checking in. Is there any temporary work around?

Probably no

Hi there. The problem still persists? The code seems fine.

Closing due to inactiviy. Reopen or create new issue if you have still having the same problem.


ValidationError: No updates are to be performed.

I removed auth on my envs via amplify auth remove, amplify pushed, then git pushed to master. Amplify tried to build at that point but is now stuck in the build phase with the error:
2020-07-13T14:28:42.365Z [INFO]: ValidationError: No updates are to be performed.
                                 at Request.extractError (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/query.js:50:29)
                                 at Request.callListeners (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
                                 at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
                                 at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:688:14)
                                 at Request.transition (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
                                 at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
                                 at /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
                                 at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
                                 at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:690:12)
                                 at Request.callListeners (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
2020-07-13T14:28:42.378Z [ERROR]: !!! Build failed
2020-07-13T14:28:42.451Z [ERROR]: !!! Non-Zero Exit Code detected

I deleted my amplify project and created a new one against the same backend role, and the same error occurred 🤔

Hi @devth ,
Can you share your appId and region?

I was able to get past it after fully deleting my project and all ./amplify/* files.
us-west-2 docproject

Hi @devth,
Are you still facing the issue?

No, but only because I deleted my project and started over. I've had to do that several times so far.

Just to understand the steps to reproduce:

Add auth to an amplify project via CLI
Remove auth from the CLI (amplify auth remove)
Push the update to cloud (amplify push)
At this point, the amplify directory should reflect the removal of auth

Push the changes to git (git push)
The push triggers an update in Amplify Console, and the build fails saying there are no updates to be performed?

Are the above steps correct?

Maybe, but I did a lot of other stuff along the way, and also had 2 environments that I added and removed auth from.

Closing as this is not easily reproducible.


model update grippeweb

PR Context

based on mex-assets branch feature/mx-1640-update-grippeweb

Changes

model update grippeweb

all good 🎇 ready to merge


Cleanup zinc-persist tests

To validate this pull request against other sbt modules, please visit this link.


Light theme not changing button colors

windmill-dashboard-react version: 0.4.0
Relevant code or config:
<div className="grid md:grid-cols-3 gap-1">
  <Button title="Edit" size="small" className="!bg-green-100 dark:bg-green-500">
    <MdModeEdit />
  </Button>
  <Button title="Delete" size="small" className="!bg-red-100 dark:bg-red-500">
    <MdDelete />
  </Button>
  <Button
    title="Open marketplace profile"
    size="small"
    className="!bg-blue-100 dark:bg-blue-500"
  >
    <MdOpenInNew />
  </Button>
</div>;

What happened:
I am switching to light theme and the button background colors is still colored purple
Problem description:
light theme does not change button colors

I have the same problem, any solution?

No. Don't have solution.


SHPE public events google calendar

Feature request Motivation
to attract more members to SHPE-UCI wide events, and create more easy access, transparency for anyone, not just our members
Solution
Request SHPE-UCI exec board to make a public google calendar, ask leads to save events here, and embed the html  into a page.  No API required, just that snippet of code from google calendar
Alternatives
Create a whole calendar from scratch which would be more time consuming. https://wics.ics.uci.edu/events/

Any progress on this @Johan-Cuevas?


next release 0.19.15

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Identifying xx encoded archives

Codecov Report

Merging #838 (cbb6f27) into dev (2d82a3e) will increase coverage by 0.26%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #838      +/-   ##
==========================================
+ Coverage   73.65%   73.91%   +0.26%
==========================================
  Files         132      132
  Lines       12429    12526      +97
==========================================
+ Hits         9154     9259     +105
+ Misses       3275     3267       -8

Impacted Files
Coverage Δ

assemblyline/odm/models/tagging.py
99.48% <100.00%> (+<0.01%)
:arrow_up:

assemblyline/odm/models/result.py
92.06% <0.00%> (-5.53%)
:arrow_down:

assemblyline/common/heuristics.py
84.78% <0.00%> (-2.18%)
:arrow_down:

assemblyline/odm/models/service.py
100.00% <0.00%> (ø)

assemblyline/odm/models/service_delta.py
100.00% <0.00%> (ø)

assemblyline/odm/messages/task.py
97.05% <0.00%> (+0.69%)
:arrow_up:

assemblyline/datastore/helper.py
45.00% <0.00%> (+0.95%)
:arrow_up:

assemblyline/filestore/transport/local.py
91.93% <0.00%> (+1.61%)
:arrow_up:

assemblyline/odm/randomizer.py
95.25% <0.00%> (+1.72%)
:arrow_up:

assemblyline/common/backupmanager.py
75.72% <0.00%> (+5.76%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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


track human performance: add keyboard interaction

42860ec8149bb46cd4673943168eddbb7fb0e042

https://github.com/suqi/gym-sandbox/blob/master/test/demo_keyboard.py
Now that we can record keyboard actions of human, and we can use DQfD implementation of TensorForce to train.


Webpack bundle error

commit ID=c60c507
tns 2.3.0
Ubuntu 16.04
npm 3.10.8
cd /tmp
git clone git@github.com:NativeScript/sample-Groceries.git
cd sample-Groceries
tns install
tns install webpack
tns prepare android --bundle

webpack.config.js
var bundler = require("nativescript-dev-webpack");
var path = require("path");

module.exports = bundler.getConfig({
    resolveLoader: {
        root: path.join(__dirname, "node_modules")
    },
    module: {
        loaders: [
            {
                test: /\.html$/,
                loader: "html"
            }
        ]
    }
});

ERROR in ../~/nativescript-angular/element-registry.js
Module not found: Error: Cannot resolve module 'ui/layouts/flexbox-layout' in /tmp/sample-Groceries/node_modules/nativescript-angular
 @ ../~/nativescript-angular/element-registry.js 74:54-90
Executing after-prepare hook from /tmp/sample-Groceries/hooks/after-prepare/nativescript-unit-test-runner.js

flexbox-layout not exists, when I remove this module in nativescript-angular/element-registry.js 74:54-90,  everything works fine.

Are you using nativescript-angular 1.1.2? Try switching to 1.0.1 as 1.1.2 has flexbox layout reference which'll be delivered with NativeScript@Next (2.4) I think.

Hey @naturalfreak indeed flexbox will be available in NativeScript 2.4.0 as @creambyemute  pointed out.
If you want to use it now (along with all the features in the @next version) you can do the following:
tns plugin remove tns-core-modules
tns plugin add tns-core-modules@next


Handle multi-hosts in PulsarAdmin for both sync and async requests.

This PR unifies all request logic for PulsarAdmin in the async path.


Added check against the subweb for the list, added warning to log if …

…not found.
(Apologies for the rash of PR's, I am fairly new to Github. Hopefully this one is correct.)

Hi @lanegoolsby, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Thx lanegoolsby. Good catch and would ask to update the GitHub profile with your full name, so that we can provide you credits in the monthly communications and not just for the GitHub alias. If you have also Twitter tag, would recommend to get that in or any other web site, which you'd like to get to the monthly communications.


folder name not rename for sharee when sharer rename the folder

Describe the bug
When sharer renamed the share folder then the folder name is not renamed for sharee. Due to this, there is also difficult to search for sharee to search the folder by name
Steps to reproduce
Steps to reproduce the behavior:

As marie, create a folder folder1
As marie, share a folder to einstein
As einstein, accept the share
As marie, rename folder folder1 to folder2

Expected behavior
The folder should be renamed
for sharer marie

for sharee einstein

Actual behavior
The folder is not renamed for sharee
for sharer marie

for sharee einstein

The screen shots show folders called folders and folder, but the test description of the steps to reproduce has folder and folder1 - that makes it confusing to understand the issue.
Also, the Actual Behavior section has the text "The response contains resource named folder in the response"
IMO it should say "The response does not contain resource named folder in the response"

The screen shots show folders called folders and folder, but the test description of the steps to reproduce has folder and folder1 - that makes it confusing to understand the issue.
Also, the Actual Behavior section has the text "The response contains resource named folder in the response" IMO it should say "The response does not contain resource named folder in the response"

oh sorry for that mistake. I've updated

AFAIK, the behavior where the resource (accepted share) doesn't get renamed in the sharee side is expected.
CC  @ScharfViktor

Now the issue describes what is known expected behavior. When a sharer renames a resource, a sharee who has already received the resource still sees it with its original name. This is the way "the system" is expected to work. A sharee can also renme a received resource, and the sharee is the only user that sees the changed name.
I think that this issue is supposed to be about searching?

the behavior is expected. same issue https://github.com/owncloud/ocis/issues/6376

Then I will close this here. @nabim777 open another issue that is related to REPORT

Then I will close this here. @nabim777 open another issue that is related to REPORT

Here is related to REPORT https://github.com/owncloud/ocis/issues/7262


API doesn't send "installed_app_status"

In the current version of the API, it doesn't send the "installed_app_status" message on a new connection.
Messages:

Even after restart they are missing:

Yes, see https://github.com/fusion44/blitz_api/commit/4408a6a58cb5e5ac94f8cf41e109bb33df58c39c
Will be fixed once #149 is merged. Until then this must stay disabled, otherwise it makes local development a hassle as it'll constantly ask for root password.

s a quick fix you can always go to https://github.com/cstenglein/blitz_api/blob/beba4332e7f6da1b96af74d8ddc0cd863896ee6c/app/repositories/utils.py#L37 and uncomment the get_app_status calls.


Unable to reply messages - 4K monitor on 15 inch laptop

Since @nevercast and I dont have a 4K its really hard for us to debug that problem. Scaling is one issue that we face and we hope to resolve it by the release 1.5.0 or before if possible...

V1 not supported anymore


User is not able to save secret as "data-volume" in environment overrides

Bug Description
User is not able to save secret as "data-volume" in environment overrides
To Reproduce

Create a complete CI/CD flow
Now go to environment overrides
Try to save a secret of any data type except "Kubernetes External Secret"

Current behaviour
There is no action on save button
Expected behaviour
File should save properly without any issue

Merged


imap   settings do not take effect

Thank you for creating such a great extension!
I want to map <ctrl-j> to esc , so I set it like this, but it doesn't work
{
    "imap": [
        ["<C-j>", "<Esc>"],
    ],
}

The environment to be used is as follows

jupyterlab                3.2.6
jupyterlab-vim            0.14.5
upyterlab-vimrc          0.5.2

Hi @fuchami
thanks for your kind words :)
What browser are you using? For me on firefox it seems to be that the browser eats ctrl-j

@ianhi
I'm using Chrome

I'm having the same issue and I'm using Brave, is there a way around this? Is it possible to use use the control key in remaps?


Fix typos, remove useless sections, and format

@ilyassesalama please merge and please give me merge permissio


Is patched CP required?

https://github.com/F483/picopayments-hub/blob/master/docs/setup.md mentions a patched Counterparty library. Is that still the case? Or is that only for those who want to run the hub (while the client doesn't need to have Counterparty library/server)?
Here I can't see that mentioned, so I thought to ask.

Only the hub requires a patched counterparty-lib and will continue to do so until the micropayment branch is merged into master and becomes part of a release.


Release 0.1.0

Are there blockers for publishing a non-experimental release?
Are there APIs that may change soon?

I agree. There's really no benefit of not bumping to v0.1 now. It makes it easier for projects to receive patches without manual intervention.


Expected empty line after require statement not followed by another require.

title says it all, when using following:
const { Router } = require('express');

any thoughts?

That's just one line - what's the rest of it look like?

only that one line triggers this error. anyways, here's the another part, which does the same thing.
import { Router } from 'express';
const router = Router();

module.exports = router;

Right, it wants a new line after the import or the require.

doh... I'm sorry. My English skills betrayed me. You are right, this issue makes no sense.
Thanks for the clarification!


Failures with Dgraph generated GraphQL schema

I'm going to just post my "sanitized" schema here for reference to what's failing.  To the best of my knowledge it's top level lists - I saw a post claiming to fix this but I tried pulling new ver and it seems I'm still crashing on those types and inputs
So here's the sanitized schema - the schema as generated from Dgraph's backend, and then ariadne-problematic bits commented out.
SANITIZED.schema.graphql.txt
... and here's the target schema (unsanitized - the raw output of Dgraph generated schema, which breaks ariadne-codegen currently)
schema.graphql.txt
queries.graphql.txt
Cheers, and happy bunting.
I'll put in some effort here too, if I can get this test case to pass I'll open a PR
P.S. Here's a oneliner to get that schema from the .../admin GraphQL endpoint using fish:
echo -en (curl 'http://<IP_ADDRESS>:8080/admin' -H 'Accept-Encoding: gzip, deflate, br' -H 'Content-Type: application/json' -H 'Accept: application/json' -H 'Connection: keep-alive' -H 'DNT: 1' -H 'Origin: file://' --data-binary '{"query":"{\n  getGQLSchema {\n    generatedSchema\n  }\n}"}' --compressed|jq .data.getGQLSchema.generatedSchema|sed -e 's/^"//' -e 's/"$//')|sed 's/\\\"/\"/g'

Can you put that failing schema on github gist? We don't need it all in the issue.

yes one sec

Actually it would be perfect if all those code blocks were instead gists with descriptions what they are.

@nargetdev I found what causes problem with your schema. in, and, or, not are keywords in python, so following code is not valid:
class IntFilter(BaseModel):
    ...
    in: Optional[List[Optional[Int]]]
    ...

This issue is already fixed on main and it will be included in next release. With this fix, example from above will look like this:
class IntFilter(BaseModel):
    ...
    in_: Optional[List[Optional[int]]] = Field(alias="in")
    ...

@nargetdev Fix for this problem has just been released, so I'm closing this issue.


Not an issue, but just wanted to say thanks a lot

Rewriting all the objective-c to swift code was great. But even greater than that was using the new APIs(CNContactStore) for getting phonenumbers. Really really appreciate it.

Thank you. I'm glad that you found it useful.


ES5 async/await sourcemap issue

TypeScript Version:  2.2.1
Code
async function bar(): Promise<void> {
    await foo();
    let x = 1;
}

produces
function bar() {
    return __awaiter(this, void 0, void 0, function () {
        var x;
        return __generator(this, function (_a) {
            switch (_a.label) {
                case 0: return [4 /*yield*/, foo()];
                case 1:
                    _a.sent();
                    x = 1;
                    return [2 /*return*/];
            }
        });
    });
}

The sourcemap associates the let x part of the ts with the var x part of the js. This is technically correct, but not very useful in practice. If you set a breakpoint on the let x line in chrome devtools or vscode, it actually sets a breakpoint on the var x line which runs before the await foo line. So it's practically impossible to debug this code with sourcemaps. It would be much more useful if the whole line was just sourcemapped to the x=1 line in the case.

Tracking similar reported issue for VS users: https://developercommunity.visualstudio.com/content/problem/23101/tyepscript-breakpoints-async-issues.html

Any ETA on when this might be fixed? Or is there an older version of TypeScript for Visual Studio 2015 that I can install which doesn't have this issue?

I may have to resort to using a multi-stage compilation using Babel if this bug isn't fixed, which would be very inconvenient. It's been two months, so can you at least give us a status update? Will this be fixed?

@rbuckton can you please take a look.

This is ridiculous, I've been telling our entire team that this bug will be fixed in TypeScript 2.4 and now you've pushed it to 2.5? This bug makes debugging TypeScript with async methods impossible! Please re-evaluate your priorities here.

@ijabit sorry for the frustration this might have caused. fix should be in typescript@next tomorrow, and in<EMAIL_ADDRESS>later this month.

@mhegazy I see now it's in Milestone 2.4.1, and not 2.5 any longer. I'm glad its fixed! Eagerly awaiting TS 2.4.1 :)

I still have breakpoint issues when compiling TS -> ES5. Compiling TS -> ES6 and then using Babel go from ES6 -> ES5 produces the correct source maps. Are you sure this issue is fixed in 2.4.1? I installed the 2.4.1 TypeScript for VS 2015 yesterday and am still seeing sourcemap issues.

Compiling from ES6 to ES5 via Babel might be the problem here, as I doubt
Babel will factor the source-map generated by TS in.
Does your ES6 code work as expected? You can try in Chrome DevTools or VS
Code.
/K
On Thu, Jun 29, 2017 at 1:24 PM ijabit<EMAIL_ADDRESS>wrote:

I still have breakpoint issues when compiling TS -> ES5. Compiling TS ->
ES6 and then using Babel go from ES6 -> ES5 produces the correct source
maps. Are you sure this issue is fixed in 2.4.1? I installed the 2.4.1
TypeScript for VS 2015 yesterday and am still seeing sourcemap issues.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/TypeScript/issues/14506#issuecomment-312093488,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKl96JOYV72_5r_gBJURgR54d5lHu7Sks5sJAgPgaJpZM4MVoea
.

Actually Babel works great, but TS doesn't! As soon as I go from TS -> ES5 directly it screws up the sourcemaps. If I run through Babel it works perfect.

Any news on this issue? I'm still running into this in 2.4.2. Using async/await completely destroys the ability to debug properly... No matter if my target is set to es6, es2015 or es5 the result is the same...breakpoints don't get honored, lines jump between TS and JS etc...

@taicho if you run it through babel that seems to clean up all the TypeScript sourcemaps and fixes stuff.

@ijabit Thanks for the workaround. Anybody have any idea why this is closed? Am I missing something? Not trying to sound testy but I’m starting to think I should rewrite all the async/await in my condenase to go back to standard promise syntax as it’s getting hard to showcase the benefits of async/await when it becomes near impossible to debug. Can we at least reopen this issue so it’s not forgotten about?


Build is not optimized for components

Considering that devs want to use this boilerplate for making components and libraries, using webpack for the final build is not necessary and is making the production file very heavy. The common practice is just to compile the es6 to es5 through babel and let the users use their own bundling preference to bundle the requirements (like react and etc)
I already have the config so if you are okay with the changes I can submit the PR

After considering that this is a webpack-base boilerplate, I decide to keep the build script as it is now.


Fix sync of generated client-go to master

Signed-off-by: Petr Horacek<EMAIL_ADDRESS>
What this PR does / why we need it:
In the current state, we never update the master branch of
kubevirt/client-go repository. Even we try to push there with git push origin master, the push is never applied and exits with:
+git push origin master
Everything up-to-date
The reason for that is, that our chenges are checked out on branch
"master-local" while the aforemenetioned command tries to push from the
checked out master branch.
With this change, we explicitly push from the currently checked-out
branch to master.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

It might be clearer if it said:
git push origin ${TARGET_BRANCH}-local:master

But it seems to make sense! thanks for the patch.

perhaps this works:
/lgtm

Thanks @maya-r. I don't mind changing it if you find it clearer. What about ${TARGET_BRANCH}-local:${TARGET_BRANCH}? My only worry with "master" is that it would be the only place where we call it by the "real" name and not the variable.

sure, whichever works, even the original :-)

All right, tell me what you think

/retest

/lgtm


command twill:capsule is not defined

Hi to all,
i'm trying to install capsule-homepages but I'm unable to complete the process.
I've followed this steps:

Copied the content of Capsule/base repository in app/Twill/Base
Copied  the content of twill-capsule-homepages in app/Capsules/Homepages
run command twill:capsule:install homepages
got this error: There are no commands defined in the "twill:capsule" namespace.

where am I wrong?

Could you please try again. Some steps to take

Delete your Homepages directory.
Comment the Homepage Capsule on your twill.php, if you have it.
Make sure Twill/Capsules directory exists mkdir -p app/Twill/Capsules (bug will be fixed soon)
Then install the capsule with php artisan twill:capsule:install --copy Homepages
Add the Capsule to your twill.php:

<?php

return [
    'capsules' => [
        'list' => [
            [
                'name' => 'Homepages',

                'enabled' => true,
            ],
        ]
    ]
];

Create a dummy route front.home:

Route::get('/', fn() => print('This is the homepage'))->name('front.home');

And I believe it should work.
Thanks for reporting this.
Cheers!

Hi @antonioribeiro ,
Thank you so much. The problem with artisan command it's now resolved, but now I have another error after login in admin area
Route [admin.homepages.landing] not defined
it seems that Laravel does not consider routes and controllers under app / Twill / Capsules / Homepages
I miss some steps with Capsules installation?

Hi @joeyramone76!
Did you get the capsule to work?
I just made a change that Antonio merged with this change, and now there is no need to create a folder (the error has been fixed), and I no longer have the error of the route not being defined. I updated the Readme as well to rework the installation.
Do not hesitate to tell me if you still have a problem!
Cheers ✌🏽


publish library

docs: https://central.sonatype.org/register/central-portal/their docs are confusing but apparentely there are two main ways to publish my library: via maven central portal (https://central.sonatype.org/publish-ea/publish-ea-guide/) and via the legacy OSSRH (https://central.sonatype.org/publish/publish-guide/). Maven central seems to be the recommended one.

some requirements: https://central.sonatype.org/publish/requirements/

jar files
checksums (.md5 and .sha1) for each file
PGP/GPG signature (.asc) for each file
pom file for metadata

example: https://github.com/simpligility/ossrh-demo/tree/master

these docs are quite confusing

I've chosen publishing via maven central portal, but apparently there are four ways to publish this way: Maven, Publisher API, Uploading a bundle and Gradle, but I only consider Maven and uploading a bundle since publisher API teaches how to build a client to send your files, and gradle is not official.

I'll use the Gradle Maven Publish Plugin


⚠ RPC server - Harmony has degraded performance

In eb46748, RPC server - Harmony ($HARMONY_RPC_URL) experienced degraded performance:

HTTP code: 503
Response time: 176 ms

Resolved: RPC server - Harmony performance has improved in 740aa92.


Optional chaining transformation is invalid in some cases

Describe the bug
Maybe this has to do with the recent changes on optional chaining? (This seems to work fine on 1.3.62)
Input code
export class TestClass {
  public anyVariable: any;
  test() {
    const testVariable = this.anyVariable?.property;
    return testVariable;
  }
}

Config
{
  "jsc": {
    "target": "es2017",
    "parser": {
      "syntax": "typescript",
      "decorators": true,
      "dynamicImport": true
    },
    "transform": {
      "decoratorMetadata": true,
      "legacyDecorator": true
    },
    "keepClassNames": true,
    "externalHelpers": true,
    "loose": true,
  },
  "module": {
    "type": "commonjs",
    "strict": true,
    "noInterop": true
  },
  "sourceMaps": true,
  "exclude": [
    "jest.config.ts",
    ".*\\.spec.tsx?$",
    ".*\\.test.tsx?$",
    "./src/jest-setup.ts$",
    "./**/jest-setup.ts$",
    ".*.js$"
  ]
}

Playground link
No response
Expected behavior
Something like:
class r {
    test() {
        let _a;
        let e = (_a = this.anyVariable) === null || _a === void 0 ? void 0 : _a.property.;
        return e;
    }
}`

Actual behavior
class r {
    test() {
        let e = null == this ? void 0 : this.;
        return e;
    }
}

Version
1.3.66
Additional context
No response

I think I found the culprit...
I am using @lingui/swc-plugin and it seems to alter the code :/
I will try to look into that


Sickbeard Module Does Not Display Images

First of all, excellent work on this! It's been just the project to bring my HTPC solution together.
I recently updated to the latest commit, and none of the banners are showing in the Sickbeard module for either the compact or regular view. I did a "Copy Image Location" and it came back with:
http://mydomain:7000/sickbeard/get_banner/95011
That is the correct show ID from within Sickbeard, but when I paste this into a URL bar, I get no image back.
Any troubleshooting steps to take?

MrK, thanks for the quick response!
I just pulled down all of the files from the repo (using the Zip option) and replaced my Maraschino directory, so I should have everything up to date. (I'm using version 491 of Sickbeard as well).
I am getting the shows to populate in the box, it's only the photos that are failing to populate.
The image comes up as .
Going to http://mydomain.com:7000/sickbeard/get_banner/95011 simply returns a blank page.

Is version 491 of Sickbeard the alpha version?
If so then I'm not sure as I didn't write the code for the Sickbeard module myself. Let me know and I'll pass the query on to the developer who did.

The version I'm using of Sickbeard is "alpha build 491", so it sounds like that could be the problem.
Feel free to pass this on, and let them know I'm available to do testing as well.
I'll stick with the compact view for now :-)

I don't think it is going to work for you until they issue another update. To be honest, quite a few people have been having problems with this and I'm thinking of switching back to the older way of handling image. The code is still there.

I love the new updates to the module in general, but it may be best to roll back the image links to the way they were, or maybe provide an option?

Okay, reverted. Can you test and let me know if it works now?

That did the trick, thanks for the quick work!!


Introduce safecast, update golangci-lint, fix bug in max app size

Description
When running a more modern version of golangci-lint the gosec linter complains about possible integer overflows (G115) even for unlikely cases. Instead of turning off the warning I experimented with the safecast package and used that to cast the types.
This changes the type signature of UDI's Unpack() to now return an error.
Type of change
Please tick any that are relevant to this PR and remove any that aren't.

[x] Bugfix (non breaking change which resolve an issue)
[x] Breaking Change (a change which would cause existing functionality to not work as expected)

Submission checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my changes
[x] I have tested and verified my changes on target
[x] My changes are well written and CI is passing
[x] I have squashed my work to relevant commits and rebased on main for linear history
[ ] I have added a "Co-authored-by: x" if several people contributed, either pair programming or by squashing commits from different authors.
[x] I have updated the documentation where relevant (readme, dev.tillitis.se etc.)

Why not update the the github actions for golangci-lint while we are at it:
I think the latest are
actions/checkout@v4
actions/setup-go@v5t
golangci/golangci-lint-action@v6

I agree we should update GH actions. Done, squashed and pushed.

Hi here
I have found out you switched to my lib to cope with integer overflows
Thank you
I found it because your tool is now available on Debian, and a Debian maintainer comes to ask me to support the i386 env
https://github.com/ccoVeille/go-safecast/issues/46
I felt honored to somehow have my lib packaged in Debian. So thank you guys.


Every Host Environment Having Different Ports .

You have declared in confuration.json but here the array format is wrong
it must be CONFIGURATIONS[local].port

Thanks for the pull request


Update README.md

Ferris Bueller, you're my hero.
This has literally been an issue I've been looking for a solution to. Thank you!


POST findings: error suggests wrong values

Issue Type

[x] Bug

Description
When POSTing to findings with the keys title, description, engagement, product, test, reporter, impact, mitigation but not severity, the error suggests choosing an option from the wrong list
the response:
{"findings": {"severity": ["Select valid choice: In Progress, On Hold, Completed"]}}
As far as I can tell, the 'valid choices' should be 'Low, Medium, High' etc.
Steps to Reproduce
post to findings using the api playground or whatever method you'd like
example body:
{
"title": "testing the api",
"description": "foopy",
"engagement": "/api/v1/engagements/1/",
"product": "/api/v1/products/1/",
"test": "/api/v1/tests/1/",
"reporter": "/api/v1/users/1/",
"impact": "fdas",
"mitigation": "asdf"
}

I'd recommend trying out the new v2 API as this is one of the reasons we are moving to the new version. V2 should be in shortly or you can try it out in the dev branch.

Great, wasn't aware of v2.


Magento 2 deploy fails when target shop is not in production mode

Deployer version: 7.0.1
Deployment OS: ubuntu

Deploy fails when the target is not in production mode.
<?php
namespace Deployer;

require_once 'recipe/magento2.php';

/ Config

set('repository', '<url>);
set('http_user', '<user>');
set('shared_files', [
    'app/etc/env.php'
]);
set('static_content_locales', 'en_US nl_NL de_DE');
set('magento_themes', ['Client/default', 'Magento/backend']);

add('shared_files', []);
add('shared_dirs', []);
add('writable_dirs', []);

// Hosts

host('<host>')
    ->set('remote_user', '<user>')
    ->set('port', '<port>')
    ->set('deploy_path', '<path>');

// Tasks

task('build', function () {
    cd('{{release_path}}');
});

after('deploy:failed', 'deploy:unlock');

What's the error you're getting?

Should have added in my OP ;)
task magento:deploy:assets
[<server>]  error  in magento2.php on line 108:
[<server>] run /usr/bin/php /usr/www/users/<user>/application/releases/48/bin/magento setup:static-content:deploy --content-version=1663324713 en_US nl_NL de_DE  -t Client/default -t Magento/backend -j 1
[<server>] err In DeployStaticContentCommand.php line 158:
[<server>] err NOTE: Manual static content deployment is not required in "default" and "de
[<server>] err veloper" modes.
[<server>] err In "default" and "developer" modes static contents are being deployed autom
[<server>] err atically on demand.
[<server>] err If you still want to deploy in these modes, use -f option: 'bin/magento set
[<server>] err up:static-content:deploy -f'
[<server>] err setup:static-content:deploy [-f|--force] [-s|--strategy [STRATEGY]] [-a|--area [AREA]] [--exclude-area [EXCLUDE-AREA]] [-t|--theme [THEME]] [--exclude-theme [EXCLUDE-THEME]] [-l|--language [LANGUAGE]] [--exclude-language [EXCLUDE-LANGUAGE]] [-j|--jobs [JOBS]] [--max-execution-time [MAX-EXECUTION-TIME]] [--symlink-locale] [--content-version CONTENT-VERSION] [--refresh-content-version-only] [--no-javascript] [--no-js-bundle] [--no-css] [--no-less] [--no-images] [--no-fonts] [--no-html] [--no-misc] [--no-html-minify] [--no-parent] [--] [<languages>...]
[<server>] exit code 1 (General error)
task deploy:failed

Just put this in your deploy.php to override the recipe's default magento:deploy:assets job;
desc('Deploys assets');
task('magento:deploy:assets', function () {

    $themesToCompile = '';
    if (count(get('magento_themes')) > 0) {
        foreach (get('magento_themes') as $theme) {
            $themesToCompile .= ' -t ' . $theme;
        }
    }

    run("{{bin/php}} {{release_or_current_path}}/bin/magento setup:static-content:deploy --force --content-version={{content_version}} {{static_content_locales}} $themesToCompile -j {{static_content_jobs}}");
});

(I've added --force in the command)

Thanks @peterjaap, I will try it out. Any idea if this is expected behavior when deploying with deployer? Or is it just my setup?

It is expected behavior that it fails, yes. Usually you shouldn't deploy to a server that runs Magento in non-production mode, but YMMV for special circumstances :)

It is a special circumstance indeed. Thanks, the provided solution works like a charm :)


Are the labels for the buzzer on the PCB backward?

Thank you for this creating and releasing this PCB. The thumb clusters located excellently for my hands. I could not help but add a piezo buzzer for the fun of it and oriented the "+" label of the buzzer with the "+" labeled on the PCB--the right pad. The buzzers made no sound until I reversed the orientation. Is the PCB mislabeled?
Also, the right side does not work with audio enabled and both halves are connected. Does a AUDIO_PIN_ALT need to be defined? Do you think that may be the root cause of my issue?
Thanks again for a great layout and PCB design.
"+" on Buzzer appears to go to the "+" printed on the PCB:

Built with incorrect orientation of buzzer:

ahhh sorry the + is not a label its the conection to die GND-plane ... the buzzer is only working on one side gmk only supports on side :(

I see. Thanks for the explanation.


feat(ingest/snowflake): generate query nodes for snowflake

Other noteworthy changes:

Removed view lineage fallback for views with failed sql parsing
Populated timestamp in Upstream class same as query time

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Lint issues should be fixed by https://github.com/datahub-project/datahub/pull/9976


Fixes/is operator and jsonb

Fix: https://github.com/dropbox/sqlalchemy-stubs/issues/207

please merge! :D

I have a PR up that does something similar:
https://github.com/dropbox/sqlalchemy-stubs/pull/211
It hasn't been merged in a while.

@jhirshman i suppose you mean #202.
Maybe we should fork and upload it to pypi, while dropbox doesn't maintain this package?

@jhirshman i suppose you mean #202.
Maybe we should fork and upload it to pypi, while dropbox doesn't maintain this package?

yes, sorry. I linked to the wrong one.
I agree that forking it might be the right solution here.

If you haven’t already seen, check out the more recent activity on this issue and this issue.
It seems as though we are fortunate enough that Mike has turned his attention to having typing integration with sqla 1.4/2.0.
I mention this as it might change your opinion as to the need to fork the repo.


case sensitivity ignored when sending custom headers through fetch  request

I am using react native 0.23.1 (also tried it using 29) on Mac. during a fetch request react ios, when I send a custom header (eg 'Api-Version' : '0.1' ) the server receives it all in lower case ('api-version':'0.1').The standard of writing a header is using camel case, I don't have control over the server code so the request fails as it is expecting the headers in camel case.When checking the server log found out that all the other non custom headers come as camel case while only the custom headers come as all lowercase.
I tried using different http clients such as frisbee and axios still it was the same.
Doing the same request using a chrome console was successful.
Following is my fetch code
  fetch(Properties.uris.base + Properties.uris.getBusinessDetails.replace("{businessId}",   Properties.appId).replace("{timezone",this.getTimeZone()), {
        method: "GET",
        headers: {
            'Accept': 'application/json',
            'Content-Type': 'application/json',
            'User-Agent': DeviceInfo.getUserAgent(),
            'X-UserId':userDetailsJson.username,
            'X-BusinessId':Properties.appId,
            'X-App-Version': DeviceInfo.getVersion(),
            'Api-Version': Properties.fetchHeaderInformation.apiVersion,
        }})
        .then((response) => response.json())

This isn't a React Native issue because the HTTP spec says that header fields are case insensitive. You should probably file a bug with the API provider.
Note that RN uses the underlying iOS networking libraries. Check out this note in the NSURLRequest docs: "The name of the header field to set. In keeping with the HTTP RFC, HTTP header field names are case-insensitive." (https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSMutableURLRequest_Class/index.html#//apple_ref/occ/instm/NSMutableURLRequest/setValue:forHTTPHeaderField:)

@facebook-github-bot expected

The comment above tells me this is expected behavior. Closing this as we'd like to use the GitHub issue tracker for bugs. If you'd like to change how this feature works please post a feature request on Product Pains so that other people can vote on it.

I did some searching and can see that there was a commit that addressed this: https://github.com/facebook/react-native/commit/7069e4cd3f1228e0508988ecdee2afb3899aedfc
I thought the iOS was doing that but that looks like it isn't the case although the reason is the same.
You could probably monkeypatch that function if necessary.

@ryankask thanks for the heads up. did the patch works like a charm (also had to patch the Fetch module in Network folder for it to work ) 👍


OTAPI v3 - Client Index doesn't get passed into SendBytesEventArgs

Describe the bug
The SendBytes hook doesn't pass the client's index into its arguments
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Platform and patch info

OS: Windows
Assembly and version you are patching: TerrariaServer v<IP_ADDRESS>
Version of OTAPI/git commit: c6bd0df3d04571e3b58172b8f1d930d750b62350
.NET runtime: NET 6

should be passed in 5f9dcbd


"permits", "prohibits", and "requires"

If we don't want omissions of acts as universals and if we assume that directive ICEs can also permit the omission of an act (which seems plausible), it seems to me that there should be a distinction between "permits action" and "permits omission". I guess one could say that  "permits omission" can be reduced to "not requires". But the same argument could be made for "permits" which can analogously be reduced to "not prohibits".

By the way, I was wondering whether the distinction between "some agent may be agent in a process" and "some agent must be agent in a process" (from the definitions) is captured formally by different relations in one of the ontologies downstream.

I now lean towards removing "permits" or defining it in terms of "not prohibits".
See paragraph 24 of https://journals.openedition.org/revus/4173


lineItems format?

Hi, my aim is to create one-time payments as described here and here (I do not want to create each product in Stripe as I have lots of references that are constantly changing)
My StripeCheckout component setup is:
    <StripeCheckout
          ref="elementsRef"
          :pk="pk"
          :lineItems="lineItems"
          :mode="'payment'"
          :successUrl="successUrl"
          :cancelUrl="cancelUrl"
        >
    </StripeCheckout>
    <template slot="checkout-button">
        <button @click="checkout">Shut up and take my money!</button>
    </template>

and in my data I have the following (I'm using Nuxt)
data: function() {
    this.pk = process.env.STRIPE_PK;
    return {
      checkoutDone: false,
      lineItems: [{
        price_data: {
          currency: 'eur',
          product_data: {
            name: 'myProduct',
          },
          unit_amount_decimal: 1500,
        },
        quantity: 1,
      }],
      loading: false,
      successUrl: 'http://localhost:3000',
      cancelUrl: 'http://localhost:3000'
    },
    methods: {
      checkout () {
        this.$refs.checkoutRef.redirectToCheckout();
      }
    }

When I click on the checkout button, I have this error in the console
Invalid stripe.redirectToCheckout parameter: lineItems.0.price_data is not an accepted parameter.
I have been checking the docs and I cannot find out why the lineItems object is rejected. Any hint would be very welcome.
Cheers and thanks for this module!

Hello @Jesus82 the lineItems payload that you are using is the one meant for sessions which is done in the backend. You should check this one, notice that it only has 2 properties, price and quantity. The one you're using, this one. What you can do is create a session in the backend. It will give you a "session id", use that session id here in vue-stripe-checkout, like this one on the documentation.

Hi @jofftiquez, thanks for your reply. My problem is that with that I would like to pass a price to checkout, not a priceID (as described here. The reason is that I don't want to create products in checkout as I sell craft beer and my references are constantly changing.
Is there any possibility of passing the prices without having to create them previously in Stripe? Thanks in advance

If you intend to charge arbitrary amount to your customer you are probably looking for the Charge API. I haven't implemented this in the past but for my understanding this is how it should be:

Capture the "source" (the credit card of the customer) using payment intent.
Pass the amount and the source to your backend to create a new Charge object.

You can also do this using Stripe Elements. May I know what's blocking you?


"Your are running Vue in development mode"

As soon as the paypal extension gets installed / activated, the browser console shows
”Download the Vue Devtools extension for a better development experience: [https://github.com/vuejs/vue-devtools|https://github.com/vuejs/vue-devtools|smart-link]  [cdn:46:38646|https://unpkg.com/@shopware-ag/meteor-admin-sdk/cdn]
You are running Vue in development mode. Make sure to turn on production mode when deploying for production. See more tips at [https://vuejs.org/guide/deployment.html|https://vuejs.org/guide/deployment.html|smart-link] ”

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-38791
[created from NEXT-38791, comment 501808]


Near constant loss

Does someone have managed to get results with this repository?
My loss is near constant, oscillating around 1.50.
I should mention that I have removed the instance segmentation module, but that shouldn't impact the pose estimation module.

Have you solved this? Just curious, I haven't worked with this lib before.

@AroMorin
I had success with the other repository based on Tensorflow, so I stopped trying with this one.

I see. The other libraries usually operate with TF 1.X. The advantage of this library is that it uses Keras, so the interface doesn't change much between TF1.X and TF2.X. Also, it uses MIT License which is permissive. Others typically have restrictive licenses or none at all.

@nscotto can you tell me what other libraries worked for you? Did you measure the accuracy using COCO ?

It's the Tensorflow Personlab repository, roughly the equivalent of this one.
I don't remember the mAP value sorry, they provide pre-trained weights in case you want to try.


Set MAVEN_OPTS for Travis-CI

Travis builds occasionally fail with Java heap space error.
This commit sets higher limits to fix the issue mentioned above.

We actually recommend the following setup: export MAVEN_OPTS="-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m". Have you experienced any issues with this configuration?
Do you think we should enable the tests after we have fixed our flaky tests?

@liorze : thank you for the comment!
I actually copied it from my local environment. That's what I have been using.
(Btw, it looks like to me we aren't exactly consistent with these options. See DEVNOTES vs. README.md)
Regarding the tests: yes, that's what I think.
I see two options:
We either fix all the flakiness and make sure it all fits into reasonable time limits.
Or, we create different test suites, one for smoke testing and another one which contains all the tests we have. (Because some of them aren't exactly "unit" tests, afaik.)

I'll update the DEVNOTES as part of FLUME-2945, thanks.
Re/ tests, I think we have a few more tests to fix, it looks doable. Let's give it a try and go with plan b if it takes to much time to fix.

@liorze : thank you for offering to fix the DEVNOTES. (Although, I'm not sure how this is related to switching to Java 8)
Do you have any other review comments for this change?

It's related because the MaxPermSize option is deprecated in Java 8.
No, LGTM.

I think, if we have MAVEN_OPTS = "..." mvn, then we need to have MAVEN_SKIP_RC = 1.
If we are going to use multiple mvn ... commands, then I think it's easier to set it up in one place. (before_install)
@mpercy : I'm sorry, what do you refer to by "Is this needed for something?"

The caching is to speed up the builds.
Thanks for helping me understand. Maybe add a comment about this for people new to Travis?

I think, if we have MAVEN_OPTS = "..." mvn, then we need to have MAVEN_SKIP_RC = 1.
Why? I don't understand the reason

If we are going to use multiple mvn ... commands, then I think it's easier to set it up in one place.
We aren't doing that yet, right? Would we ever do that?

Personally I like to avoid putting stuff in default locations for build scripts in order to avoid unintended side effects either in other concurrent builds or in future builds. I just don't like to "pollute" the environment. However, I'm guessing Travis uses a Docker image or something like that and wipes out the home dir before each build so you can leave cruft in $HOME and it will never affect future builds. Is that right?

Thanks for helping me understand. Maybe add a comment about this for people new to Travis?

I did not notice huge speedups, so I'm just going to remove it for now.

Why? I don't understand the reason

According to http://stackoverflow.com/a/35755762/5323166 , if there are any defaults (mavenrc, etc.) set in the FS, MAVEN_OPTS env var is ignored.
Afaik, all Travis-CI build environments are "disposable" (the Docker stuff you have mentioned), so it should be fine to "pollute" the environment, but we can go YAGNI and change it later.

I did not notice huge speedups, so I'm just going to remove it for now.

I wasn't asking to remove it, just for a comment to be added to the yaml file, but either way is OK with me.

Thank you, @mpercy
I'm about to commit this


This commit was done by Jose Garibay: includes readme.txt file creati…

…on and readme.txt modification

Jose garibay merge into remote branch


Terrible performance on Android

I ran an example on Google Pixel, which has absolutely no problems in Chrome. WebView is very slow
https://github.com/KevinnZou/compose-webview-multiplatform/assets/126922273/c76df869-4adf-4b72-95dd-2e8cd5a185fc
Version: 1.7.8

The problem seems to be related to this.setLayerType(View.LAYER_TYPE_SOFTWARE, null) added recently https://github.com/KevinnZou/compose-webview-multiplatform/pull/65. With or without this.setLayerType(View.LAYER_TYPE_HARDWARE, null) everything works correctly

@flymedllva Thanks for your help! @xmeaindes In version 1.7.8, I have set the Software Layer as the default solution to address the https://github.com/KevinnZou/compose-webview-multiplatform/issues/64. I will switch to Hardware Layer and release the 1.8.0 today. Sorry for the inconvenience caused.

@xmeaindes It has been fixed in version 1.8.0. Please have a try and let me know if you encounter any problems.