Inline settings modal field/submission issues

Description
First of all I really love what you guys are building with Tina, it's a great editing experience and a real win for making interactive content management accessible to non-devs in our team 🎉
However I've run into a few bugs with the inline editing experience, specifically using the Inline Settings modal and nested fields inside Group, Group List and Blocks fields. I would love to use Inline Blocks to their fullest in my current project, but I'm having to fall back to the sidebar and standalone Inline elements for now.
All of these issues are reproducible in the demo linked from the Tina homepage (https://tina-demo-two.vercel.app), and in the tinacms repo's demo projects that use the above elements.

When clicking into a group/group-list/block, the first interaction with any field inside it (e.g. the first keypress inside a focused input/textarea, clicking a toggle) will retrigger the enter animation from the first form page and cause the active field to lose focus.
When clicking into a group/group-list/block, if there is another group/group-list/block nested inside it these items won't respond to clicks and you will not be able to proceed deeper into the form. However, if you click the back button and re-enter the group/group-list/block, the previously inaccessible fields will now work as expected. Furthermore, attempting to interact with any fields inside the newly accessible group/group-list/block will retrigger the enter animation mentioned in point 1 above, except you are returned to the previous page and must perform the 'go-forward-to-go-back' steps again in order to get back to where you were.
Specifically with group-lists (and sometimes groups, see 2nd video below), editing them in any way (either by dragging to reorder, deleting an item, editing any of the fields nested within a group-list item) causes the Form Status field in the toolbar to show Unsaved changes in the background as expected. But if Confirm is clicked without editing any other fields, the status returns to No changes and the changes cannot be saved, even though they can still be seen on the page. If you re-open the inline settings menu the Form Status shows in the background that there are unsaved changes, but this does not persist when closing the settings modal.

None of these issues appear to exist when using the same fields in the sidebar, everything functions seamlessly there. My suspicion is this is caused by stale form state/re-rendering issues related to React Final Form in the inline package, but I haven't been able to diagnose so far when running the tinacms repo demo's locally.
Steps to reproduce

https://user-images.githubusercontent.com/40216869/112761787-cc75da80-8ff4-11eb-9986-52d9ed942f26.mp4

https://user-images.githubusercontent.com/40216869/112761799-da2b6000-8ff4-11eb-9caf-4e82e0de96b6.mp4

https://user-images.githubusercontent.com/40216869/112761806-e3b4c800-8ff4-11eb-8975-fdf2df6036fe.mp4
Expected result

When clicking into a group/group-list/block in the inline settings modal and interacting with a field (e.g. typing into an input, clicking a toggle), the respective field works normally.
When clicking into a group/group-list/block in the inline settings modal and attempting to click into another nested group/group-list/block, it opens the the nested item normally as expected.
When editing group-list items in the inline settings modal, clicking Confirm should update the form status to Unsaved changes in the toolbar and allow the changes to be saved.

Actual result

When clicking into a group/group-list/block in the inline settings modal and interacting with a field (e.g. typing into an input, clicking a toggle), the enter animation is re-triggered and causes the field that was being used to lose focus.
When clicking into a group/group-list/block in the inline settings modal and attempting to click into another nested group/group-list/block, the nested item is unresponsive and you must click back and re-enter the current page to make them accessible.
When editing group-list items in the inline settings modal, clicking Confirm does not update the Form Status to Unsaved changes.

Tinacms Package Versions
(These are from the tina-demo project, however the above issues are also present when using 0.38.0 of tinacms, and 0.37.0 + 0.38.0 of react-tinacms-inline)
"tinacms": "0.37.0"
"react-tinacms-inline": "^0.39.0-alpha.1",

No worries, thanks for responding! :)
Ahh interesting, I was looking at the plugins themselves to see if there was a common pattern that might be causing issues, but that idea sounds plausible if the form itself is handled differently between sidebar and toolbar/modal. I’ll take another look when I get chance tomorrow evening, will update if I find anything 👍

Ough, few hours of my life are gone due to this bug. Hopefully, you will accept the PR and release it soon, it is really annoying.

Ok, I found what causes the second issue, and it is related with FormPortal again. It is because of z-index. When you are in a group field (1 level), the Panel is rendered under the portal element and everything great. But when you go deeper and opens another group (2 level), the second Panel could be added to the portal element before or after the Panel of the level one Panel, and since we have no z-index management, If the second one added before the first one it won't be visible.
So, to fix that I see no other way than to introduce some kind of zIndex management, but it requires more than one line of code that I did so far :) The only idea I have right now is to convert FormPortal to a component that manages the z-Index and provide it to the children via children function, so the child will have to set provided zIndex where needed.

Ahh amazing @c58! Confirmed first PR fixes the rerender issues, nice one on the z-index management too!
Re the 3rd issue, I can still reproduce in the demo-next project and the Tina Tailwind Demo (after fixing the first issue in the source).
It’s very weird - in demo-next, it affects fields in the two InlineGroups on the Nesting page: hero.description, hero.toggle and author.description, but interestingly not the fields inside author.colors. In the tailwind demo, the issues with nav fields in the 3rd video above still persist after updating the source with the wrapperRef fix.
However in both of these examples, if you enable the sidebar and add the same fields to the useForm config, the issue stops (see video of tailwind demo below). This perhaps explains why the InlineGroup on the Info page in demo-next isn’t affected.
This might tally with what @spbyrne mentioned above, that the inline modal only uses a stripped down version of the form? I’ve been having a look at Toolbar.tsx in the inline package to see if it's a subscription issue.
https://user-images.githubusercontent.com/40216869/114303989-b8d47480-9ac8-11eb-97fd-bb7aacdb356d.mp4

Hm, I see. I tried in my project a similar "fields" configuration and it worked fine. I will try to reproduce it in demo-next

Apologies I’ve been on a tight deadline so not had chance to look at this again until now. I’ve done a bit more investigation though and think I know how that 3rd issue is happening, but not yet why.
It seems to be specific to fields that are only registered via the fields prop of the InlineGroup component, and don’t have a corresponding inline field on the page or one in the sidebar. If this is the case, then Toolbar.tsx rerenders when Confirm is clicked, and a new instance of the form is created with pristine and dirty set to true and false respectively, even though the values contain the new changes.
I haven’t yet managed to figure out why Toolbar.tsx rerenders on clicking Confirm in this scenario, but not when a field is also registered inline or in the sidebar.


Standalone player - controle multiple players and more.

Hi,
I'm not got with react and i want tu use the standalone version.
In did a example based on your own: https://jsfiddle.net/onigetoc/0y374z9m/
i see that we can create functions to interact with the player and access the player informations.
Like many others video players do.
Plyr player: https://jsfiddle.net/onigetoc/rLkazct6/
Videojs: https://jsfiddle.net/onigetoc/hq5x1c90/
I would like to use myplayer.playplayer() to target the right player and create multiple players and create a way to manipulate video functions.
In the plyr example i did a console.log() and it return all player functions.
It would be interesting to access all control options and more with the stand alone reak player.
I see that there's already have video control options here, why don't use theme for the stand alone.
https://github.com/CookPete/react-player/blob/b7b2b1c9385826b6bca4ea838bdb8bc214791e07/src/players/Facebook.js
play, pause, seek ect...
sorry for the long text but i really like your player.

myplayer1.internalPlayer.getCurrentTime()

Respect!


after downloading 1 video gets error

Authentication successful.
[+] DOWNLOADING VIDEOs
[+] LOGGED IN TO INSTAGRAM[\green]
[+] MAKING VIDEO
Traceback (most recent call last):
File "/home/gm/Ytmaker/main.py", line 155, in
make_video(files)
File "/home/gm/Ytmaker/main.py", line 118, in make_video
concatenate(clips,f"videos/vid_{VID_NUM}.mp4")
File "/home/gm/Ytmaker/main.py", line 127, in concatenate
clips = [VideoFileClip(c) for c in video_clip_paths]
File "/home/gm/Ytmaker/main.py", line 127, in
clips = [VideoFileClip(c) for c in video_clip_paths]
File "/home/gm/.local/lib/python3.10/site-packages/moviepy/video/io/VideoFileClip.py", line 88, in init
self.reader = FFMPEG_VideoReader(filename, pix_fmt=pix_fmt,
File "/home/gm/.local/lib/python3.10/site-packages/moviepy/video/io/ffmpeg_reader.py", line 35, in init
infos = ffmpeg_parse_infos(filename, print_infos, check_duration,
File "/home/gm/.local/lib/python3.10/site-packages/moviepy/video/io/ffmpeg_reader.py", line 270, in ffmpeg_parse_infos
raise IOError(("MoviePy error: the file %s could not be found!\n"
OSError: MoviePy error: the file intro.mp4 could not be found!
Please check that you entered the correct path.

ok there was missing the intro.mp4 and the "videos" folder and now it works.
if i comment out the intro and the upload section the script still works?


[Fundamentals] Lists not supported with account owned tokens

Summary
Requested via internal chat.

Preview:
https://pedro-2024-12-20-fundamental.cloudflare-docs-7ou.pages.dev/fundamentals/api/get-started/account-owned-tokens/#compatibility-matrix


Use relative urls when the canonical url isn't set

If this merges I'll open a similar pull for version 8.

I'm concerned about putting this in a relatively small release (<IP_ADDRESS>) when it has some far-reaching implications. This could very possibly break lots of sites that use the URL class for generating URLs that they use in APIs (turning them relative when they need to be absolute so that other services can consume them.) Not against the change, I think it's a good one – but I think it should be in 8.0 only going forward.

Alright we can do that

@KorvinSzanto: Did you already include this onto Ver.8?

I have not

I have opened a PR now


Register service only when OCI metric enable flag is set to true

Environment Details

Helidon Version: 2.x/3.x
Helidon MP

Problem Description
For Helidon Metrics to OCI feature, when ocimetrics.enable is not set to true, the OciMetricsSupport service is still registered in the default routing, but not running. It would be more optimal if the service is not registered at all, so that the service won't be loaded from the start.

PR https://github.com/helidon-io/helidon/issues/5946 is the potential fix

PR https://github.com/helidon-io/helidon/pull/6032 has been completed.


[Snyk] Upgrade axios from 1.6.5 to 1.6.8

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade axios from 1.6.5 to 1.6.8.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released 25 days ago, on 2024-03-15.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Information Exposure SNYK-JS-FOLLOWREDIRECTS-6444610
432/1000  Why? Proof of Concept exploit, CVSS 6.5
Proof of Concept

Resource Exhaustion SNYK-JS-JOSE-6419224
432/1000  Why? Proof of Concept exploit, CVSS 6.5
No Known Exploit

Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-JS-TAR-6476909
432/1000  Why? Proof of Concept exploit, CVSS 6.5
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: axios

1.6.8 - 2024-03-15Release notes:
Bug Fixes

AxiosHeaders: fix AxiosHeaders conversion to an object during config merging (#6243) (2656612)
import: use named export for EventEmitter; (7320430)
vulnerability: update follow-redirects to 1.15.6 (#6300) (8786e0f)

Contributors to this release

 Jay
 Dmitriy Mozgovoy
 Mitchell
 Emmanuel
 Lucas Keller
 Aditya Mogili
 Miroslav Petrov

1.6.7 - 2024-01-25Release notes:
Bug Fixes

capture async stack only for rejections with native error objects; (#6203) (1a08f90)

Contributors to this release

 Dmitriy Mozgovoy
 zhoulixiang

1.6.6 - 2024-01-24Release notes:
Bug Fixes

fixed missed dispatchBeforeRedirect argument (#5778) (a1938ff)
wrap errors to improve async stack trace (#5987) (123f354)

Contributors to this release

 Ilya Priven
 Zao Soula

1.6.5 - 2024-01-05Release notes:
Bug Fixes

ci: refactor notify action as a job of publish action; (#6176) (0736f95)
dns: fixed lookup error handling; (#6175) (f4f2b03)

Contributors to this release

 Dmitriy Mozgovoy
 Jay

    from axios GitHub release notes

Commit messages

Package name: axios

ab3f0f9 chore(release): v1.6.8 (#6303)
2656612 fix(AxiosHeaders): fix AxiosHeaders conversion to an object during config merging (#6243)
7320430 fix(import): use named export for EventEmitter;
8786e0f fix(vulnerability): update follow-redirects to 1.15.6 (#6300)
d844227 chore: update and bump deps (#6238)
caa0625 docs: update README responseEncoding types (#6194)
41c4584 docs: Update README.md to point to current axios version in CDN links (#6196)
bf6974f chore(ci): add npm tag action; (#6231)
a52e4d9 chore(release): v1.6.7 (#6204)
2b69888 chore: remove unnecessary check (#6186)
1a08f90 fix: capture async stack only for rejections with native error objects; (#6203)
104aa3f chore(release): v1.6.6 (#6199)
a1938ff fix: fixed missed dispatchBeforeRedirect argument (#5778)
123f354 fix: wrap errors to improve async stack trace (#5987)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

/retest

/retest


[Bug]: MONEY_DEFAULTS_CONVERT env option is not being used

What happened?
According to the config file, I can set MONEY_DEFAULTS_CONVERT in my env file. However this setting has no effect.
I am storing the amount in the db as 100.00
If I use it on a table column like this
        Tables\Columns\TextColumn::make('amount')
          ->currency(),

It outputs $1.00
If I change the shouldConvert option to true
        Tables\Columns\TextColumn::make('amount')
          ->currency(shouldConvert: true),

It outputs $100.00, which is what I want.
However to setting the MONEY_DEFAULTS_CONVERT=true and removing the shouldConvert option
        Tables\Columns\TextColumn::make('amount')
          ->currency(),

It outputs $1.00 instead of $100.00
Can you please apply an update which respects the MONEY_DEFAULTS_CONVERT env variable.
Thanks for this package.
How to reproduce the bug
        Tables\Columns\TextColumn::make('amount')
          ->currency(),

It outputs $1.00 instead of $100.00 even when MONEY_DEFAULTS_CONVERT env variable is set to true.
Package Version
1.9
PHP Version
8.2
Laravel Version
11
Which operating systems does with happen with?
Linux
Notes
No response

added in 1.10.0


fix missing response.Body.Close()

As mentioned in Do docs:
// If the returned error is nil, the Response will contain a non-nil
// Body which the user is expected to close. If the Body is not both
// read to EOF and closed, the Client's underlying RoundTripper
// (typically Transport) may not be able to re-use a persistent TCP
// connection to the server for a subsequent "keep-alive" request.

I also thought of changing from your custom HttpClient interface to the default http.RoundTripper interface. What do you think?

I also thought of changing from your custom HttpClient interface to the default http.RoundTripper interface. What do you think?
@brenol The only reason I'm using a custom HttpClient is so I can mock it. As long as the change you're suggesting doesn't affect the ability to mock responses, I'm fine with it.

Thank you for the contribution!

Released in v0.0.2


Short summary of the issue...

Describe the issue
While DF Architect is enabled, I can no longer bring up the macro edtior
To Reproduce
Steps to reproduce the behavior:

Go to a world
Right click on a macro in your hotbar (if no macro exists create one)
You'll no longer see the edit option in the macro context menu

Expected behavior
I expect to see the edit option in the context menu.
Foundry v9 build 242
DF Architect 3.1.1

I did leave my library modules active otherwise Find the Culprit is a pain to work with. So I guess there is a possibility that it's a weird interaction just between DFA and one of these library modules. After running the Find the Culprit and disabling just this one mod the edit button popped back in as expected

DF Architect is not currently V9 compatible. Please follow the migration process here: FoundryVTT V9 Migration


missing credit

generated2.rule is missing credit:
From the oclHashcat v1.20 changelog:
Type: Feature
File: Rules
Desc: Added generated2.rule, each one cracked a real hash, sorted by occourance. use head -XXXX to make a top XXXX
Cred: EvilMog
I spent 6 months generating that rule

@evilmog Thanks for the head's up. Credit's added. Thanks for all the hardwork you have done.


Zia module not working

Hi ! I am writing terraform code for zia using module but when i am calling the resources using module as i used to do with AWS.   I get errors
Un-successful request with status code : 400
Can anyone please help me sharing code where you have called module. I can refer that and proceed towards success

@atulevertz
Please provide exact error message along with debug logs, resource name you're trying to provision etc.
Set the following environment variables prior to executing Terraform again, and then provide the log output for analysis.
export ZSCALER_SDK_LOG=true
export ZSCALER_SDK_VERBOSE=true
export TF_LOG="TRACE"
export TF_LOG_PATH="terraform.log"

hi @willguibr
i need your urgent help. please provide me sample ZIA-terraform module which can help me refer to write for my environment.
I can see the modules available but how to call those modules are not available at all.
I have worked on AWS terraform and the module i a following with ZIA-TF in AWS-TF , it works in AWS-TF ...
I am calling the module like below:
module "dlps" {
source = "../modules/dlp_dictionary"
api_key  = var.api_key
}
module "dlp_engine_policy" {
source = "../modules/vinci_dlp_engine"
api_key = var.api_key
}

Please contact me via email so we can set up some time to discuss. The question/problem you're stating is unclear and cannot be answered via this issue. Please email at<EMAIL_ADDRESS>Second I am on PST timezone.
William


Allow users to update friend request list on registration form before team formation

Currently players have to contact mods and mods have to manually update the registration. It would be nice if users could update their own friends list after registration submission but before team formation.

I agree. I think we should require "sign in" to the website in order to register. Once you register, you should be taken to a dashboard page, where you can update your registration. This should also serve as a place where you can confirm your registration status.
Finally, it can also be a place where we include any onboarding information that we want to convey to them.  It should also be obvious that they can return to this page to see their current pairings, current league status and update their availability.

Fixed in #280.


App gives false information for devices made after 2020

At the end of 2019 the serials reached ZY
& the new iPhones that were made in 2020 had serials beginning with C1 and now they reached D8 I believe.
If you can update the app to apply this change I’ll be very grateful.
Currently, Serial app correctly detects the device model but it shows iOS 13.0 as the probable version for all 2020 devices which is not correct (also the dates for the week are not correct as they are from 2010).
Thanks again for making this very useful tool.

Serial has been succeeded by Reincubate Lookup, which you can read more about here. It features a brand-new design and tons more information.

Serial has been succeeded by Reincubate Lookup, which you can read more about here. It features a brand-new design and tons more information.


Question : Why I can't find a way without that plugging

Sorry my question is from a newbie on kubernetes and network rules.
I have a managed kubernetes cluster ( gke auto-pilot ) where a pod  A ( that I can "kubectl exec" ) have access to a managed hidden postgres database.
My wish is to access that database from my host by using the pod A as a "bastion/proxy"
With this plugging I simply run kubectl socks5-proxy and my host can now resolve and access the host:port of that hidden postgres using the proxy localhost:1080.
I could not found a way without this plugging, is this normal ?
Thank you

@raphaelauv
Thank you for the issue (I'm very sorry for the late response)
I believe you can use kubectl port-forward to achieve your goal.
Please read this page:
https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/#forward-a-local-port-to-a-port-on-the-pod
As one of other solutions, as you know, you also can use this plugin - he plugin actually creates a SOCKS proxy server Pod in a Kubernetes cluster and forwards a local port (default:1080) to the proxy. So you can access to the hidden pod in the k8s cluster via localhost:1080

I'm closing this but please feel free to open an issue if further discussion is needed


@typecheck pragma

allow enabling and disabling type checks using babel options.
fixes https://github.com/codemix/babel-plugin-typecheck/issues/113

Very nice, thanks!

Would you have any eta on a new npm release? I would rather not publish my own built version.


Issues with inv(Triangular)

Consider
julia> using LazyArrays, ArrayLayouts, LinearAlgebra

julia> A = UpperTriangular(ApplyArray(inv, rand(5, 5)))
5×5 UpperTriangular{Float64, ApplyArray{Float64, 2, typeof(inv), Tuple{Matrix{Float64}}}}:
 2.35135   1.68449   -1.84848   -0.955078  -1.85021
  ⋅       -0.271777  -1.25844    0.94071   -1.27413
  ⋅         ⋅        -0.124992  -1.4524     2.35783
  ⋅         ⋅          ⋅         0.669905  -0.609163
  ⋅         ⋅          ⋅          ⋅         0.840739

julia> inv(A)
inv(5×5 UpperTriangular{Float64, ApplyArray{Float64, 2, typeof(inv), Tuple{Matrix{Float64}}}}):
  0.425287   2.63595  -32.8287   -74.2701    43.1852
 -0.0       -3.67949   37.0457    85.4846   -47.5317
 -0.0       -0.0       -8.00051  -17.3457     9.86934
  0.0        0.0        0.0        1.49275    1.08158
  0.0        0.0        0.0        0.0        1.18943

julia> MemoryLayout(inv(A))
LazyArrays.InvLayout{TriangularLayout{'U', 'N', LazyArrays.LazyLayout}}()

The LazyArrays.InvLayout{TriangularLayout{'U', 'N', LazyArrays.LazyLayout}}() could maybe be TriangularLayout{'L', 'N', LazyArrays.LazyLayout}()? One issue that the current situation causes is e.g.
julia> using BandedMatrices

julia> colsupport(inv(A), 1)
Base.OneTo(5)

which is of course more problematic for infinite matrices.

Actually this might be more on LazyArrays.jl than here since it comes from https://github.com/JuliaArrays/LazyArrays.jl/blob/8fc085dc65af7114b74c774da71a7942ffa2461f/src/linalg/inv.jl#L84


How to use protoc to generate code when the base package contains minus sign ?

Here is the proto file I used -- pkg/apis/workflow/v1alpha1/generated.proto
syntax = 'proto2';

package go-server.com.argo-new.pkg.apis.workflow.v1alpha1;

import "k8s.io/api/core/v1/generated.proto";
import "k8s.io/api/policy/v1beta1/generated.proto";
import "k8s.io/apimachinery/pkg/apis/meta/v1/generated.proto";
import "k8s.io/apimachinery/pkg/runtime/generated.proto";
import "k8s.io/apimachinery/pkg/runtime/schema/generated.proto";

// Package-wide variables from generator "generated".
option go_package = "v1alpha1";

// ArchiveStrategy describes how to archive files/directory when saving artifacts
message ArchiveStrategy {
  optional TarStrategy tar = 1;

  optional NoneStrategy none = 2;
}

When I tried to use protoc -I /usr/local/include -I . -I ./vendor -I /root/go/src -I<EMAIL_ADDRESS>-I<EMAIL_ADDRESS>--include_imports --gogofast_out=plugins=grpc:/root/go/src --grpc-gateway_out=logtostderr=true:/root/go/src --swagger_out=logtostderr=true,fqn_for_swagger_name=true:. pkg/apis/workflow/v1alpha1/generated.proto to compile the proto file, it reminds me pkg/apis/workflow/v1alpha1/generated.proto:6:11: Expected ";".
It's a compile error which means the package name should not contain "-". Are there any methods to use "-" in package name or any workaround ?
Thanks!

The package in the .proto file is a distinctly different concept from the Go package path. In the protobuf language, the syntax for a valid protobuf package are [_a-zA-Z][_a-zA-Z0-9]+([.][_a-zA-Z][_a-zA-Z0-9]+)*.
The go_package option in the .proto file is where you specify the full Go package path. Thus, v1alpha1 is incorrect.
Also, it seems that you are using protoc-gen-gogo, but this repository is for protoc-gen-go, perhaps you should be asking these questions on that project's issue tracker if you're using that plugin?

Our issue tracker is intended to track work that needs to be done. For questions that are better resolved through a series of back-and-forth questions and responses, this is probably best asked on Slack. There's a protobuf channel where similar questions are usually asked.

Thanks


NETOBSERV-412: document architecture

@OlivierCazade that's fine. Let me merge this (other PRs will go on top on this) and then fix it into another PR


Liquid output agent

@cantino There is still documentation and cleanup to do here, but this is the idea I mentioned on Twitter a week or so ago.
This is an agent that will produce a string output, just like the data output agent.  The difference is that it's wide-open to be anything that's a string - a html page, javascript, whatever.  This agent stores the payload of the last event it received into memory, and then passes that payload through liquid templating and renders the output via a URL.  The content and mime type can be configured.
I use Huginn to process data that I check often.  Huginn sends me messages, RSS feeds, etc., but this would allow output in many other forms.
I have a very simple example below.  I set up a liquid output agent that receives names through events, and then produces a javascript page that alerts that name.  I then set up another liquid output agent that produces a HTML page that links to that javascript page.  I can then go to that web page and the last name the first agent receives will show up as an alert.
Thoughts?

@cantino One more example:

Wow, that looks really powerful and flexible, great idea! Without having looked at the code I'd like to note that we should make the options/memory as flexible as possible to allow future extensions (without versioning we always have to support old versions of Agent options). The first idea that comes to my mind is to aggregate a certain number of event or  over a time period to use them all in the liquid template.
The concept looks so simple, yet it allows so many use cases, I am excited 👏

I really like that idea, @dsander, to pass a set of events.  I'll include that.

Next bits of work:

[ ] Tests.  I've been spiking this agent to test that the idea work.  It does, so now it needs the tests.

[ ] Aggregate event option.  Currently it uses the last event payload as the data to pass to liquid, but why not merge?  If I get an event like {a: 'b'} and a second event of {c: 'd'}, then the data passed to Liquid could be {a: 'b', c: 'd'}.

[ ] Last X event option.  Instead of passing a single event, why not pass the last X events?

[ ] Last time period. Instead of passing a single event, why not pass the last events based on a time period?

Very cool!  I'll dig into the code shortly.

[ ] Rename "secrets" to "secret."

[ ] Make the detail view of the agent display a link to the URL that was created.

Slick!

[ ] Mark this agent as not being capable of having receivers.  It only outputs html.

@cantino I'm done with development on this pull request.  Unless there are any other issues, this PR is ready to go!
I know you prefer to have these pull requests squashed and rebased against master.  I can do that, but... could you do it with the Github button?  You might already be doing this; I'm only asking because I've done it myself in my previous pull requests.

@cantino Oh gosh! Wait, one more commit!

[ ] Put an example of how to loop through events in the default "content" block.

This is very important, I think... I want to make it like the Javascript agent, where you get a sample that explains the situation better than any documentation ever could.

Ok @cantino , NOW it is ready to go. :smile: Thanks!

Awesome @darrencauthon!  I'm at a conference this weekend, so it may be a few days before I can review.

I found the time ;)  Awesome work!

All good tips, I'll clean them up over the weekend.  Have a good weekend and conference!

@cantino Ok I think all of the recommended changes have been made, thanks!

Awesome work!


Adding this library on top of XLabs 2.0 breaks the WP project

Adding this library on top of XLabs 2.0 breaks the WP project

Did you added it through nuget? Or did you add code from github?

via Nuget

There is a problem with nuget library right now. It also causes crash on iOS.
I will update it when I'm available.
For now you can clone code from github to your project.

I see. Thanks for your support.


Improve Persona Selector

Improve the Personas Selector in preparation for dynamic personas, and to conform to screen sizes.

[x] removed hardcoded pre-computed tiling options - 9d2857d41e73d423c729f5c7553779a9fafba80f
[x] use a grid layout with snuggle fit
[x] smaller tiles and improved fitting across screens - 1ea8b42e5f84b6f8ef01547cdb1bf9fa44f908c2, 16b25fcc1fb757a062781f1f8b8259c92b25f843
[x] render persona images when present - 9bcdbf8db61a82e31ba59edd8bcf25fb94bc00c4
[x] change highlights from orange to blue
[x] toggleable examples all at once - e2b1c6aff0e90d2c715ddc384d6cade2f3aaf020
[x] improve custom prompt input
[x] improve accessibility

Done. Dramatic improvement.
Before:

After:


Uploading stemcell bosh-openstack-kvm-ubuntu-trusty-go_agent/3262.14 to the cloud. Failed: Unable to connect to the OpenStack Keystone API http://ctl:5000/v3/auth/tokens

I am deploying cloud foundry on openstack keystone v3, trying to upload the bosh stemcell image. But it prints this error message:
Uploading stemcell bosh-openstack-kvm-ubuntu-trusty-go_agent/3262.14 to the cloud. Failed: Unable to connect to the OpenStack Keystone API http://ctl:5000/v3/auth/tokens
getaddrinfo: Name or service not known (SocketError) (00:00:05)
Error 100: Unable to connect to the OpenStack Keystone API http://ctl:5000/v3/auth/tokens
getaddrinfo: Name or service not known (SocketError)
The complete output of the bosh upload stemcell command can be seen here:
http://pastebin.com/bk3jNV0w
I used the same approach mentioned in
https://github.com/cloudfoundry-incubator/bosh-openstack-cpi-release/issues/44
But all I get is the same error as above. Anyone could tell me how to solve this? Thanks!

Dear @kenfting
It seems like the host ctl cannot be resolved from the BOSH Director VM (that's what the error says). Are you running a DevStack? Here is a few things you can try to figure out your networking problem:

Can you access e.g. Horizon from the BOSH Director VM?
Which DNS server are you using inside the VM? Something like dig @<your DNS server IP> ctl should work if this setup is supposed to work
Can you use an IP address instead?

Warm regards
Marco

@voelzmo
Dear Marco,
Thanks very much for your answers. I am not sure whether it is DevStack, the openstack is provided by cloudlab.us. I will check with them. I tried to use IP address and hostname instead right now. but it also didn't work. About your suggestion, the result is ( vm_ip, ip_addresss and hostname replace the relative details):

I am not sure how to access Horizon from Director VM. I used  ssh vcap@vm_ip -i ./bosh.pem to log in Director VM. and used curl http://ip_address:5000/v3, it got:
{"version": {"status": "stable", "updated": "2015-03-30T00:00:00Z", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}], "id": "v3.4", "links": [{"href": "http://ip_addres:5000/v3/", "rel": "self"}]}}

the DNS server inside VM is <IP_ADDRESS>, I used dig @<IP_ADDRESS> ctl and dig @<IP_ADDRESS> hostname, it got:
; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @<IP_ADDRESS> ctl
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62703
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ctl.					IN	A
;; ANSWER SECTION:
hostname. 29 IN	A	130.127.1**.4*
;; Query time: 75 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Fri Sep 23 14:03:35 UTC 2016
;; MSG SIZE  rcvd: 74

If you're not using a custom nameserver, ctl cannot be resolved to your actual OpenStack API endpoint. <IP_ADDRESS> is hosted by google, they have no chance to know where ctl should point to.
Try to use Keystone's IP address as OpenStack endpoint in your deployment manifest and re-deploy your BOSH Director.

Thanks @voelzmo
I used Keystone's IP address and re-deploy. the manifest is:
auth_url: http://130.127..:5000/v3
endpoint_type: publicURL
human_readable_vm_names: false
ignore_server_availability_zone: false
state_timeout:  300
boot_from_volume:  false
use_dhcp:  true
wait_resource_poll_interval:  5
project: admin
domain: default
username: admin
api_key: ea53a4c22**
default_key_name: bosh
default_security_groups: [bosh]
connection_options:
connect_timeout: 360
ssl_verify_peer: false
But it failed. Also I used cat /etc/resolv.conf command and got nameserver 130.127.. as DNS server. It also failed.  Same errors:
Failed: Unable to connect to the OpenStack Keystone API http://130.127..:5000/v3/auth/tokens
getaddrinfo: Name or service not known (SocketError) (00:00:06)
Error 100: Unable to connect to the OpenStack Keystone API http://130.127..:5000/v3/auth/tokens
getaddrinfo: Name or service not known (SocketError)

I'm not sure how you're supposed to connect to the cloudlab.us OpenStack. Is this over some VPN connection? Did you add some nameserver entries manually?

I use ssh to connect the cloudlab.us Openstack controller, and deploy cloud foundry. is there something wrong with it? I tried to use different nameservers in /etc/resolv.conf, but no luck.

@voelzmo
Dear Marco,
I have updated the pulic URL, changed the hostname(ctl) to FQDN and restarted all services. Re-deployed and now the stemcell is uploaded successfully. Thanks all the same.

I'm also trying to deploy CloudFoundry on Openstack Keystone V3 using BOSH and I am getting the same error when trying to upload the stemcell:
18:19:14 | Update stemcell: Uploading stemcell bosh-openstack-kvm-ubuntu-trusty-go_agent/3421.4 to the cloud (00:00:07)
            L Error: CPI error 'Bosh::Clouds::CloudError' with message 'Unable to connect to the OpenStack Keystone API http://*.*.*.*:5000/v3/auth/tokens
getaddrinfo: Name or service not known (SocketError)' in 'create_stemcell' CPI method

18:19:21 | Error: CPI error 'Bosh::Clouds::CloudError' with message 'Unable to connect to the OpenStack Keystone API http://*.*.*.*:5000/v3/auth/tokens
getaddrinfo: Name or service not known (SocketError)' in 'create_stemcell' CPI method

When I log into the bosh director VM, it allows to me to connect to Keystone manually though:
bosh/0:~$ curl *.*.*.*:5000
{"versions": {"values": [{"status": "stable", "updated": "2016-04-04T00:00:00Z", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}], "id": "v3.6", "links": [{"href": "http://.*.*.*:5000/v3/", "rel": "self"}]}, {"status": "stable", "updated": "2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links": [{"href": "http://.*.*.*:5000/v2.0/", "rel": "self"}, {"href": "http://docs.openstack.org/", "type": "text/html", "rel": "describedby"}]}]}}bosh/0:~$

I was even able to obtain an auth token by posting a custom auth request through curl. Anyone have an idea what could be going on here?


Swift compilation should not fail when some but not all source files have changed since last compile

To reproduce:

Create a Swift project with more than one source file, with class A using class B.
Run gradle assemble.
Change the source file for class A but not class B.
Run gradle assemble -> compilation fails due to class B not found.

Probably due to the incremental compile analysis that is done by the Swift compile task (but shouldn't be).

See #44.

This is fixed now.


Document USE and SET NAMES, simplifies SET TIME ZONE

Fixes #1502.
Fixes #1503.
Also covers the change implemented in https://github.com/cockroachdb/cockroach/pull/16459
Based off #1107 to separate concerns, and also because this change applies to 1.1 not 1.0.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/bbcb71c1d6ee75134dd0bae9b62b129c32db9369/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/daf66a1032b60e8da2258a8b124d6408186d41a4/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/30dbeaa70c1b05fcdde3f5363f458ba63b9f8eb7/

Agreed. I'll rebase off release-1.1 when the other PR is merged.
Any suggested ETA on that btw?

I'm reviewing it now. Hopefully we can have feedback to you very soon.

@knz, now that https://github.com/cockroachdb/docs/pull/1107 has landed, you should be free to wrap this one up, right? No rush, just don't want it to get lost.

No problem. Do you want me to also take my changes from #1107 and pick them to apply on top of release-1.1?

Yeah, that'd be great, @knz. Thank you!

Superseded by #1609.


[BUG] CVE-2023-49569 in go-git

go-git in versions before 5.11.0 contains the critical vulnerability  CVE-2023-49569.
It seems that the datadog agent is affected in its latest version 7.50.3.
Is it possible to bump the go-git dependency?

Nevermind, I just saw these changes are already in main. So probably fixed with the next release.


bug: unversioned references from exe-docs to git repo

Describe the bug
For example, in release-0.2 we see https://github.com/kubestellar/kubestellar/blob/a05e6f20bdac2366c3aae8d1f9c915cb25180f87/docs/content/Coding Milestones/PoC2023q1/example1-subs/example1-start-kcp.md?plain=1#L20 , which does a git clone of the repo without specifying a branch --- and nothing later does a git checkout of the release-0.2 branch.
This problem is in several docs in both release branches.
Steps To Reproduce
RTFM
Expected Behavior
An executable thing in a release should invoke stuff in that release.
Additional Context
No response

BTW, I think it would help if these docs included usage of the kubestellar-release command (https://docs.kubestellar.io/main/Coding Milestones/PoC2023q1/commands/#kubestellar-release) to show the release that is actually being used.

fixed in all branches - "-b {{ config.ks_branch }}"


rqt_common_plugins: 0.3.12-0 in 'hydro/distribution.yaml' [bloom]

Increasing version of package(s) in repository rqt_common_plugins to 0.3.12-0:

upstream repository: https://github.com/ros-visualization/rqt_common_plugins.git
release repository: https://github.com/ros-gbp/rqt_common_plugins-release.git
distro file: hydro/distribution.yaml
bloom version: 0.5.20
previous version for package: 0.3.11-0

rqt_action

No changes

rqt_bag
* Added step-by-step playback capability
* Contributors: Aaron Blasdel, sambrose

rqt_bag_plugins

No changes

rqt_common_plugins

No changes

rqt_console

No changes

rqt_dep

No changes

rqt_graph

No changes

rqt_image_view
* Added button to save current image to file
* Contributors: Dirk Thomas

rqt_launch

No changes

rqt_logger_level

No changes

rqt_msg

No changes

rqt_plot

No changes

rqt_publisher

No changes

rqt_py_common

No changes

rqt_py_console

No changes

rqt_reconfigure
* Added refresh button to re-scan reconfigure server list
* Now retains functioning nodes when refreshing
* Contributors: Kei Okada, Scott K Logan

rqt_service_caller

No changes

rqt_shell

No changes

rqt_srv

No changes

rqt_top

No changes

rqt_topic
* Save/Restore of headers added
* Contributors: Aaron Blasdel

rqt_web

No changes

You should also update the doc and source branches now since the latest release is from a different branch.

There isn't a special bloom way to do that or anything, just open a normal pull right?

Yes.


[FEATURE]

Description
Add day night light button for better enhancement .....

Hey, thanks for raising the issue. But as per previous discussion with our maintainers we removed light mode support. So we no longer going to implement this feature.


Update upgrade-distribution-lists.md

@MikePlumleyMSFT  this reflects the deprecation plan for the feature

Learn Build status updates of commit 730050e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/upgrade-distribution-lists.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 81e17f0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/upgrade-distribution-lists.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@MikePlumleyMSFT Please merge this.

@kwekuako

Learn Build status updates of commit d1a3404:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/upgrade-distribution-lists.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 1bd2e6d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/upgrade-distribution-lists.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 0dfbe4b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/upgrade-distribution-lists.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 752003a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/upgrade-distribution-lists.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


PostProcessStageCollection does not export Uniforms in first execution

In Cesium does not run a stage that requires depth textures when depth textures are not supported unit test will fail unless fxaa is enabled. I am lead to believe this it is because of this logic within cesium:
https://github.com/AnalyticalGraphicsInc/cesium/blob/63fbb701e1ba5cbd0ed169ba11b674f1b7853d1d/Source/Scene/PostProcessStageCollection.js#L748-L752
When FXAA is enabled execute will be called within the first render call. However, when disabled .update needs to be called then .execute can be called for activeStages to include the custom stage.
The solution was to enable FXAA for this unit test but there may be something larger happening here.
Referenced in: https://github.com/AnalyticalGraphicsInc/cesium/pull/8057

Turned out FXAA allowed for the test to properly run but wasn't the root cause. Fixed in PR.


   <title>

   <doc import=?  src: "(http://mycompany.okta.com)"
   <p> platformed for function; can we function?
             No!
                #This will be used for testing your solution.
                      def _eq_(self, other):
                            if type(other) is type (self):
                               return self.value=other.value return false

         src str https://learn.microsoft.com/en-us/previous-versions/windows/it-pro
                    /windows-server-2012-R2-and-2012/dn452420(v=ws.11)?WT.mc_id=
                    linkedin
        Type: oauth2
                 Flow: accessCode
                 Authorization URL:
                 Token URL:

   <doc import=?  src: "(http://mycompany.okta.com)"
   <p> platformed for function; can we function?
             No!
                #This will be used for testing your solution.
                      def _eq_(self, other):
                            if type(other) is type (self):
                               return self.value=other.value return false

         src str https://learn.microsoft.com/en-us/previous-versions/windows/it-pro
                    /windows-server-2012-R2-and-2012/dn452420(v=ws.11)?WT.mc_id=
                    linkedin
        Type: oauth2
                 Flow: accessCode
                 Authorization URL:
                 Token URL:


Devel

Hi,
I hope this pull request doesn't get rejected because it's a huge refactor of the original code base to bring this puppet module up to speed with recent puppet changes and influxdb >= 1.x.
I hope these updates will be accepted and will prevent me from creating yet another influxdb puppet module on the forge.
Let me know if you have any questions or concerns.
Kind Regards,
-Cody

Hey Cody and thank you.
Indeed is a big PR, but I agree with you we dont need another influxdb module. I will review the changes and come back to you.

Yeehaw!  Glad to help my friend and thank you for reviewing.  I also hope that this addresses the most if not all of the open issues and pull requests.
I didn't update the CHANGELOG, but I can if you'd like?

Don't worry about the ChangeLog. I need to fully review the code anyway, so while doing that I will update the logs and the metadata files.

Hi there -
I know you are probably really busy but I'm just wondering if you have any questions or concerns about my changes and if they can be merged into master?  I won't hold any hard feelings if you choose not to incorporate my changes in this pull request.

Hi,
sorry for the delay :( As you guessed the main reason is that i didn't have time to fully review it, since its a really big change. Although you made a lot of conceptual changes I like it. For now I will merge the commits , but before releasing it to the forge I want to run more tests. I should have more time end of this week.
thank you again for the great work you did.

I should also say that I'm grateful for you putting this wonderful module together.
You are very welcome and I'm glad to hear that you liked the changes.  Please don't hesitate to reach out if you need me to clarify anything.
To hopefully put your mind at ease in terms of testing I also fixed all the unit and beaker tests and they are on tip top shape and working.  I've deployed this in my production site and it has been running for the past 20 days without issues on both Ubuntu and RedHat based operating systems.   This still doesn't mean there aren't bugs, just haven't seen anyone complain yet and that's usually a good sign.


Cache and revert

This patch provides a autoenv_cache function that can be used to cache variables in .env files when leaving is enabled. These are then reverted in autoenv_leave().

Oooh, this looks useful ^w^, it seems to address some ideas in #19. Before I merge this I wanna get #205 merged, so tests can be added for this behavior

While this is a useful feature for some people, I'm closing this because I think the addition would make the project more complex than what is necessary. There are other softwares that do better unloading and those can be used instead


fix(typing): Relax dict annotations in channels.py

Fixes #3572

mypy fails in https://github.com/vega/altair/actions/runs/10737803168/job/29780043433?pr=3573
mypy passes in https://github.com/vega/altair/actions/runs/10737971560/job/29780584984?pr=3573

Hmm, may move this back to draft.
Wasn't planning to modify the docstrings

Great fix regarding the de-prioritization of Map!

Great fix regarding the de-prioritization of Map!

Thanks for reviewing @binste


Editor Rulers (Part 2 - Pick up configuration setting and render)

Given any rulers present in editor.rulers they will be rendered in the viewport. The color is currently hardcoded and will be fixed in part three of #460
This pull request depends on the work done in #573, so be sure to merge that first.

Looking through the codebase I can see that other features such as rendering indent guides are using activeBuffer. Is that something I should take into account as well?


Help: we have forked the repo and met a problem of "Permission not permitted" on CI/CD

Proposal

We want to start a new project based on Hermes relayer, but a CI/CD permission problem was revealed while we are creating a PR to our forked master branch, and we don't know how to resolve it.
Does the issue happen in CI/CD script or the process we fork it?

Acceptance Criteria

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

@romac good to see you, master, can you give some advice on this issue?

Might be solved like this? https://github.com/informalsystems/hermes/pull/2927

Might be solved like this? #2927

thanks for the reply, let me check.


docs:demo doc example

example for students to use github
daniel
Description
This is a demo of how to add things to github
Type of change

[X] Documentation (update or new)

How Has This Been Tested?
I tested this by running x and the result was that it worked.
Testing Checklist:

[X] Tested in latest Chrome

Checklist:

[X] I have made corresponding changes to the documentation

demo


Update samples and docs for v1

Some of the samples and documentation need to be updated in preparation for v1.

[X] Update migration guide
[ ] Update samples
[ ] Update readme

For anyone pulling in the latest release on nuget, you should refer to the examples on nuget.org: https://www.nuget.org/packages/Blockfrost.Api/latest
The current examples in the README.md will not work.


Fix "Treat Warnings as Errors" Project Setting doing nothing

Fix https://github.com/godotengine/godot/issues/58330.

The setting wasn't being accounted for, at all. I'm not sure the current fix is performant, as I've heard fetching Project Settings is really slow, so it should be cached somewhere? Regardless, it gets the job done.

Wouldn't it make more sense just to remove this option? You can change each warning type to an error individually now, so it's no longer necessary.


ReturnDefaultIfNotRegistered is not respected between scopes

The following code will throw even though IfUnresolved is set to ReturnDefaultIfNotRegistered:
class Program
{
    static void Main(string[] args)
    {
        var container = new Container();

        using (var scope = container.OpenScope())
        {
            var foo = scope.Resolve<Foo>(IfUnresolved.ReturnDefaultIfNotRegistered); // Does not throw
            scope.UseInstance<Foo>(new Foo()); // Do a registration within the scope
        }

        using (var scope = container.OpenScope())
        {
            var foo = scope.Resolve<Foo>(IfUnresolved.ReturnDefaultIfNotRegistered); // Throws
        }
    }
}

Since the registration happened within the first scope, I'd expect the second scope to simple be empty and not throw. Looking at the stack trace, the IfUnresolved parameter seems to get discarded half way through, and the code simply throws instead of checking if it should actually throw.

@rick-palmsens Thanks for finding, will check. The fix PRs are appreciated as well (as you have already looking into the stack trace) ;)

I have fixed the issue in the upcoming v4.8.4 but going forward please use Use instead of UseInstance as the later will be removed in the next major version.


netstandard2 support

Hi. I'm porting a large application I built that uses the UrbanAirship.Portable nuget package to netstandard2.
Currently my app is unable to resolve AirshipBindings.Portable and I suspect that it is because the package is built for PCL and does not support yet netstandard. I tried setting the <AssetTargetFallback>portable-net45+wp8+wpa81+win8+MonoAndroid41+MonoTouch10+Xamarin.iOS10</AssetTargetFallback> in my netstandard csproj file, but it didn't help.
Do you have plans to releasing a new version supporting netstandard?

Hi @rlepinski. I bring good news (I hope) to you.
I took the liberty of cloning this project and ported the UrbanAirship.Portable project to netstandard, fixed the references and then referenced it directly in my project. I was able to get push notifications working on my iOS app, however I couldn't test Messaging Center due to dependencies in my code I need to fix beforehand.
The good news is that the migration is pretty simple and I didn't stumble upon anything in the middle of the road. To understand better how to do it, I suggest reading this post: https://montemagno.com/how-to-convert-a-pcl-library-to-net-standard-and-keep-git-history/
Basically I replaced the whole content for AirshipBindings.Portable.Abstractions.csproj and AirshipBindings.Portable.csproj to
<Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
        <TargetFrameworks>netstandard2.0</TargetFrameworks>
</PropertyGroup>

and referenced AirshipBindings.Portable.Abstractions on the AirshipBindings.Portable project. I also deleted the AssemblyInfo.cs file as it is no longer used for netstandard projects (you can migrate the content there to the .csproj file).
You guys may want to discuss internally if you still want to support PCL profiles for future releases.

Thanks for the info. We are looking into adding it but it may take us a week or so due to other priorities.

Thanks a lot @rlepinski. I'm looking forward to trying out your netstandard package.

@arctouch-oberdanbitencourt https://github.com/urbanairship/xamarin-component/pull/92
It looks ready to go, its just waiting on reviews from my team. Most likely it will be released by the end of the week.

Ah, I should've looked at the open PRs. Outstanding! Thanks for the info.

Hey @arctouch-oberdanbitencourt ,
5.0.2 is now out, which includes a .NET standard 2.0 package on nuget.  Functionally it's pretty much identical to the PCL, so hopefully it should be pretty straightforward. Give it a try, and if you have any feedback don't hesitate to let us know.

Hello @marc-scig I've been working with @arctouch-oberdanbitencourt in this migration and we encountered a while trying to run an iOS application with the new .NET standard 2.0 package:
2018-06-18 17:05:46.588 xxxxxx.iOS.xxxx[25354:1319052] Could not find `AirshipBindings.NETStandard` referenced by assembly `xxxxxxxx, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null`.

With the same references (urbanairship.netstandard nuget and urbanairship.android.core) in Android everything seems to work fine, but not in iOS, the application is unable to find the Bindings for some unknown reason, I've tried to add the respective NuGet packages (urbanairship.netstandard and rbanairship.ios) to the iOS project, but it still fails at runtime, any thoughts on this? (all version 9.0.0)

I am unable to reproduce this at my desk. It could be you have some cruft in your project file left over from building with our SDK pre 9.0. Here are some ideas:

Do a really clean build, i.e. manually remove all bin and obj directories.
Check your .csproj files:

Remove any references to AirshipBindings.NETStandard and AirshipBindings.NETStandard.Abstractions.
For the root and iOS .csproj, make sure your only PackageReferences are to urbanairship.netstandard. For Android, you will also need one or more push providers, e.g. urbanairship.android.fcm.

Remove and re-add the urbanairship nuget packages.

Please let us know if this solves your issue.

@arctouch-fabriciomiranda @arctouch-oberdanbitencourt
Closing this issue. Please re-open if you have further issues.


Cloud init data source: Azure

Is your feature request related to a problem? Please describe.
Our cloud-init support does not include data source from Azure. We are running a fork of linuxkit to have the data sources exposed separately, although we miss the Azure cloud-init support.
Describe the solution you'd like
Support for Azure in the cloud-init data sources
Describe alternatives you've considered

Additional context
See also https://github.com/linuxkit/linuxkit/pull/3585 for an exampl

See: https://github.com/mudler/yip/pull/16 and https://github.com/davidcassany/linuxkit/pull/2

Fixed by https://github.com/mudler/yip/pull/16


support get/set of object content_encoding

We use the content encoding field when storing compressed objects in Riak. This is currently supported in RiakPBC client (https://github.com/nlf/riakpbc), which we are moving from.
I have added the field and raised an issues for this: https://github.com/basho/riak-nodejs-client/issues/69

Hello!
Thanks for your contribution. I have created PR #71 which includes your commit plus another to add unit and integration tests for this feature.

@gonzohunter I'll be releasing 1.4 today with this update.


Question: Firmware verification

When updating a Jade hardware wallet, does the device carry out any sort of signature verification, to ensure the FW build has come from a trusted source, ie Blockstream?

Hi,
If you have a standard Jade unit (eg. as purchased from Blockstream store) then yes, the unit will verify the firmware uploaded during the upgrade process has been signed by Blockstream.  In fact it carries out this check every time it boots the firmware.
This security feature is provided by the esp-idf 'operating system' that underlies the Jade firmware - it is usually referred to as 'secure boot' and you can check the technical details here.
Also, during the upgrade process the unit should display the 'hash' of the data file being uploaded - we intend to also publish a web-page listing the good/valid hashes, although this is still a work-in-progress atm.
NOTE: if you have a 'diy' unit (eg. you have purchased a consumer esp-32 board, like a lilygo t-display or an m5stack unit) and have loaded the firmware yourself, the 'secure boot' feature is not enabled, as you are in full control and are able to load any firmware you desire - eg. one you have modified yourself.  (Of course in that case you are free to enable 'secure boot' such that it only accepts firmware signed by you!)

Closing as inactive.
Please comment/reopen if further clarification is needed.

We could possibly read the fw partition and compute the hash and show the user.
The problem is that a fake/malicious fw pretending to be version X would just discard the hash it computed and instead display the (hard-coded) correct hash for version X - so I'm not sure it gains you much, security-wise.

Thank you very much for your analysis.
You brought up an important point that I hadn't thought of.
It doesn't make sense to show the hash value on the Jade display after the firmware has been updated, because that would possibly lull the user into a false sense of security.


High memory since 0.3

Since updating Ajour to iced 0.3, we have noticed very high memory on especially Windows.

Windows
MacOS

iced 0.3
~195mb
~90mb

iced 0.2
~70mb
~70mb

Here's a picture of Windows running Ajour with both 0.2 and 0.3, both builds built in release mode.

It should be quite easy testable
master runs 0.2 and development runs 0.3.

Can confirm same issue here on windows.
The issue isn't present on Linux, pre /post the 0.3 commit its at ~112mb on my machine.

There's a post in the Zulip about this.  Memory usage has increased noticeably ever since upgrading the wgpu dependency to 0.6, and 0.7 made it even worse.  The glow renderer is fine, so something is up on the wgpu side of things.

@Ssaely Thanks for the heads up on that.
I wish I knew more about profiling on windows to help figure out what's causing this. We have some really cool features dependent on 0.3, but we're hesitant to roll this out when memory usage ships 3x and one of our selling points is performance :P

Probably related to #786.

that's awesome ajour uses iced, didn't know that, absolutely love Ajour so thanks for your team :). On this issue, I tried the fix that helped the #786 example, but it didn't change anything here. Going to try and take a look, was hoping 0.8 would have helped also but it didn't, so it's probably some niche usage of wgpu

created issue: https://github.com/gfx-rs/wgpu/issues/1407

Running the simple "Hello World" example from the Application trait is eating 180 Mb ram on my Win10 ...


Designing test cases for repairability

Hi @martinezmatias ,
I have a doubt about designing test cases. I think I've two options right now:

Use @BeforeAll to process all the input files at once. After that, we just need to analyze the results in each of the test cases. Hence, the heavy processing is done only once.

The other is the usual choice of dividing files into different sets of test cases. This may result in a repetition of the same file as well as the processing of the same file more than once.

It's a tradeoff between testing time and modularity of test cases.
WDYT?

Hi @sedflix
I would say the second one for one reason: In case of debugging on particular test case that option computes only the diffs involved in that case.
WDYT?
Regards
Matias

Yeah. That's a good point too. I will continue with the second approach.
Maybe at some later stage, we should work on the resources taken by coming to make it faster and lighter.


Fix packaging - include README.rst so setup.py works

You can test your setup.py is working with tox, which does a full setup.py install in the test virtualenvs

@MrMinimal64 bump


Feature/mission join action

Hi @houdamzari 👋
In this PR

[ ] I added join missions functionality inside the missions reducer
[ ] Then I called the action from the Missions component

Issue Reference #10
If you have any questions about this PR feel free to ask, Thanks 👍

Status Approved :heavy_check_mark:
Hi @raihan2bd, great job implementing the requirements,
✔ Followed Gitflow.
✔ No linter errors.
✔ Good commit messages.
✔  Added the join missions functionality.
✔ Dispatched the join mission's action.
There is nothing left but to merge it!

Cheers and Happy coding!👏👏👏


Resolve syncing conflicts from repo_sync_working_branch to master

Pull request opened by Docs to resolve syncing conflicts from repo_sync_working_branch to master.

@huypub : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Resolved the merge conflict; merging.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Implementation problems on a Raspberry Pi

Describe the bug
I had posted this on Discourse, not realizing this was the appropriate place for it. I believe the Raspberry Pi is an important platform for the expansion of Monty in the real world, and so deserves some support attention, some time down the road.
Tristan Slominski helped me in my journey but concluded "Decoupling from Habitat utilities within a motor policy seems to have little uncertainty (use scipy instead). However, Monty uses the Habitat simulator for testing. Determining the best approach to testing Monty without the Habitat simulator remains an open question."
My problem:
I’m trying to get Monty setup on a 64 bit Arm Raspberry Pi running Bookworm. In
"conda env create -f environment_arm64.yml" I get "Solving environment: failed
PackagesNotFoundError: The following packages are not available from current channels:
pytorch::torchvision
pytorch::pytorch==1.11.0
pyg::pyg
aihabitat::habitat-sim==0.2.2
mkl[version=‘<2022’]"

Thank you for posting here @rollynoel.
Link to the Disource thread mentioned above: https://thousandbrains.discourse.group/t/implimentation-problems-on-a-raspberry-pi/187


Update licenses in Windows Container build workflows

Updates the licenses in the Daisy workflows to reflect a fork to Mirantis and Docker CE builds.

/lgtm


Initially only load menu screen assets.

Improve loading times by only requiring that the menu screen assets be loaded before showing the menu screen. The rest of the assets required during the game can then be loaded in the background.

Implemented in b16c3ef.


Mysql Flexible Server.Get API doesn't return the PrivateDNSZoneResourceID property after failover

After tested, we found Mysql Flexible Server.Get API doesn't return the PrivateDNSZoneResourceID property after failover. So could you help take a look? Thanks in advance.

please assign this to @SudheeshGH, Sudheesh this is in your charter right?

@Bashar-MSFT , Networking and Security should be assigned to @vivgk

@neil-yechenwei please assign this to @vivgk

Issue still exist

@dollarpo7 , Request to open a support incident on this. The github items are for Doc bugs.

Request to close the PR as the concern here is not a doc bug

#please-close


Proper usage with selective polyfilling?

Is there a good, or preferable setup using preset-modules, along with `preset-env' auto polyfilling? Perhaps all the transforms disabled so the polyfills are also included?

We will move this preset into preset-env soon (either in the next Babel minor release or in the one after), so it will be enough to use @babel/preset-env with the esmodules: true option.

Right - I believe even with all transforms enabled right now preset-env would produce polyfill imports since it isn't aware preset-modules is transforming things.

At the moment i've got them working together but have had to manually exclude any transforms in preset-env. On a tangent it'd be nice to have a leaner polyfill option as well, corejs is thorough, maybe too much so :P

@jquense I couldn't agree more! :)
FWIW I've found myself using polyfill.io's configurator tool and then grabbing the resulting polyfills (with the ?flags=always parameter) and just inlining that. I tend to conditionally load it using <script nomodule>.

its luckily as easy as using a regex since the babel plugins are consistently named https://github.com/4Catalyzer/javascript/blob/esm/packages/babel-preset/esm.js#L25

oh, brilliant haha. One thing potentially worth trying would be to exclude known false positive inclusions of corejs:
exclude: [
  /transform/,
  'es.map',
  'es.set',
  'es.object.assign'
]

We will move this preset into preset-env soon (either in the next Babel minor release or in the one after), so it will be enough to use @babel/preset-env with the esmodules: true option.

Babel 8 is planned to be released in March. Any chance it will be included then? :)

It will! And in case we release 7.9.0 before 8.0.0, it will be already included in 7.9.0.
You can turn on notifications for https://github.com/babel/babel/pull/11083 :wink:

I don't know where to post this, but the Safari 10 polyfill for supporting "nomodule", is this part of this plugin, or do we still need to include that ourselves?


which is branch have 5.0.0.Alpha2 resource code?

I want to read this resource code. Code demo use 5.0.0.Alpha2 version,but I don't know how pull this version code.

You should not use it... Use 4.1.x as 5.0.0* was deprecated and is dead for now.
If you really want to checkout the tag you can use git checkout netty-5.0.0.Alpha2.


Requesting salinity units

Hello,
I am requesting addition of salinity units that are not detected by the UOM server currently. These are coming from our NCBI Biosample work over 20M+ sample records.
The list of units is:
PSU
psu
practical salinity units
dS/M (decisiemens per metre)
uS/cm (microsiemens per centimeter)
% NaCl
PSS-78 (https://salinometry.com/pss-78/)
percent (w/v)
ppt (this is a pseudounit so lower priority, would likely have to be 'NaCl ppt' in the wild)

This project builds directly on UCUM. There are lots of examples. We will not be adding new units, but UCUM allows flexibility with "non-units".

I think that PSU is not in UCUM. It could be represented as a "non-unit" in UCUM with {}, such as {PSU}; our project doesn't yet support {} but we plan to in the future.
"dS/M" won't work because "M" does not mean "metre", but dS/m works
uS/cm works
UCUM supports percent and "NaCl" could be a non-unit: %{NaCl}
I believe PSS-78 could also be a non-unit.
I don't understand "percent (w/v)"
"ppt" means parts-per-trillion? In UCUM this is [pptr]


[epoll set] reset cursor and num events when shutdown epoll set

Maybe a naive approach to fix #32481

cc @drfloob

Hi, thanks for helping on this, but looks like this change did not fix the issue since the test is still failing (You can trigger it using bazel test --test_timeout=10 //src/python/grpcio_tests/tests/unit:_jina_hanging_test.native).

I took the test from a comment in the original issue.
I am not sure I am the best suited to clarify the testing structure.
Also it seems the issue solves no problem. But I still think it can be a good addition to the codebase to reset these to 0. But this is up to you wether you want to keep it.

Sorry for not being clear in my previous comment. While https://github.com/grpc/grpc/pull/33085 does fix the issue captured by this test, we're no longer 100% that this is not just papering over an underlying issue. We will do the legwork of adding this issue to a slightly different test suite that has better debugging instrumentation for this class of issue.
@XuanWang-Amos will take over that.
Again, thank you for the contribution.


Why vpkg can't install pcl

C:\vcpkg>vcpkg install pcl
Computing installation plan...
The following packages will be built and installed:

boost-algorithm[core]:x86-windows -> 1.78.0
boost-asio[core]:x86-windows -> 1.78.0
boost-atomic[core]:x86-windows -> 1.78.0
boost-bimap[core]:x86-windows -> 1.78.0
boost-chrono[core]:x86-windows -> 1.78.0
boost-container[core]:x86-windows -> 1.78.0
boost-context[core]:x86-windows -> 1.78.0
boost-coroutine[core]:x86-windows -> 1.78.0
boost-date-time[core]:x86-windows -> 1.78.0
boost-filesystem[core]:x86-windows -> 1.78.0
boost-foreach[core]:x86-windows -> 1.78.0
boost-graph[core]:x86-windows -> 1.78.0
boost-interprocess[core]:x86-windows -> 1.78.0
boost-iostreams[bzip2,core,lzma,zlib,zstd]:x86-windows -> 1.78.0
boost-lexical-cast[core]:x86-windows -> 1.78.0
boost-math[core]:x86-windows -> 1.78.0
boost-multi-index[core]:x86-windows -> 1.78.0
boost-phoenix[core]:x86-windows -> 1.78.0
boost-property-map[core]:x86-windows -> 1.78.0
boost-property-tree[core]:x86-windows -> 1.78.0
boost-proto[core]:x86-windows -> 1.78.0
boost-ptr-container[core]:x86-windows -> 1.78.0
boost-random[core]:x86-windows -> 1.78.0
boost-range[core]:x86-windows -> 1.78.0
boost-regex[core]:x86-windows -> 1.78.0
boost-serialization[core]:x86-windows -> 1.78.0
boost-sort[core]:x86-windows -> 1.78.0
boost-spirit[core]:x86-windows -> 1.78.0
boost-system[core]:x86-windows -> 1.78.0
boost-thread[core]:x86-windows -> 1.78.0
boost-unordered[core]:x86-windows -> 1.78.0
boost-uuid[core]:x86-windows -> 1.78.0
boost-xpressive[core]:x86-windows -> 1.78.0
pcl[core]:x86-windows -> 1.12.0#3
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x86-windows...
Restored 0 packages from C:\Users\ztx\AppData\Local\vcpkg\archives in 7.274 ms. Use --debug to see more details.
Starting package 1/34: boost-regex:x86-windows
Building package boost-regex[core]:x86-windows...
-- Using cached boostorg-regex-boost-1.78.0.tar.gz.
-- Cleaning sources at C:/vcpkg/buildtrees/boost-regex/src/ost-1.78.0-c212e9f671.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/vcpkg/downloads/boostorg-regex-boost-1.78.0.tar.gz
-- Using source at C:/vcpkg/buildtrees/boost-regex/src/ost-1.78.0-c212e9f671.clean
-- Including C:/vcpkg/ports/boost-regex/b2-options.cmake
CMake Error at installed/x64-windows/share/boost-build/boost-modular-build.cmake:38 (message):
Could not find b2 in C:/vcpkg/installed/x64-windows/tools/boost-build
Call Stack (most recent call first):
ports/boost-regex/portfile.cmake:15 (boost_modular_build)
scripts/ports.cmake:142 (include)

Error: Building package boost-regex:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with git pull and .\vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+boost-regex
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[boost-regex]+Build+errorincluding:
package: boost-regex[core]:x86-windows -> 1.78.0
vcpkg-tool version: 2021-12-09-724cea8b33cbf06c645f5095fa29773697da9761
vcpkg-scripts version: unknown
I installing pcl failed at first time
then, I install pcl with 'keep-going'
at last , 'vcpkg install pcl' again, the above problems arise

Could not find b2 in C:/vcpkg/installed/x64-windows/tools/boost-build

Please remove boost-uninstall then try again.

Also having a similar problem
`-- Using source at C:/Dev/vcpkg/buildtrees/pcl/src/89d532cf08-e771f817a1.clean
-- Found external ninja('1.10.2').
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:158 (message):
Command failed: C:/Dev/vcpkg/downloads/tools/cmake-3.21.1-windows/cmake-3.21.1-windows-i386/bin/cmake.exe --build . --config Release --target install -- -v -j9
Working Directory: C:/Dev/vcpkg/buildtrees/pcl/x64-windows-rel
See logs for more information:
C:\Dev\vcpkg\buildtrees\pcl\install-x64-windows-rel-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:111 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:41 (vcpkg_cmake_build)
ports/pcl/portfile.cmake:82 (vcpkg_cmake_install)
scripts/ports.cmake:145 (include)
Error: Building package pcl:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with git pull and .\vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+pcl
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[pcl]+Build+error
including:
package: pcl[core,visualization,vtk]:x64-windows -> 1.12.0#4
vcpkg-tool version: 2022-02-03-457b0309cefb58fae0dcb2e4c06de9bd7582967f
vcpkg-scripts version: 05c445c1f 2022-02-10 (5 hours ago)
Additionally, attach any relevant sections from the log files above.`

install-x64-windows-rel-out.log

Seems like this is a compiler bug. Check the following issue:
#19561

Yeah, please track #19561 instead.

you should remove alibabaprotect


Remove *.pfx from gitignore

When running crank benchmarks using a local YARP build, crank will respect the gitignores when uploading the files.
Having this .pfx in it means we're not copying the testCert.pfx to the perf machines, breaking some runs (https, h2).

I guess this is related: https://github.com/dotnet/crank/issues/232

Yeah semi-related, but this is an issue on Yarp's side that we're using an ignore for something that was already tracked before.


ink! setup compile problem: dispatcher.rs:186:30

Following steps in ink! tutorial I get following compile problem.
To be sure that it is not due to my macOs setup, I repeated all steps as github-workflow by running ubuntu and got the same compile problem.

Default host: x86_64-unknown-linux-gnu
rustup home:  /home/runner/.rustup
installed toolchains
stable-x86_64-unknown-linux-gnu (default)
nightly-2020-06-01-x86_64-unknown-linux-gnu
nightly-x86_64-unknown-linux-gnu
installed targets for active toolchain
wasm32-unknown-unknown
x86_64-unknown-linux-gnu
active toolchain
stable-x86_64-unknown-linux-gnu (default)
rustc 1.47.0 (18bf6b4f0 2020-10-07)

Compiling ink_core v2.1.0 (https://github.com/paritytech/ink?tag=latest-v2#cca31543)
Compiling ink_lang v2.1.0 (https://github.com/paritytech/ink?tag=latest-v2#cca31543)
error[E0658]: function pointers cannot appear in constant functions
--> /home/runner/.cargo/git/checkouts/ink-1add513eda8f5a89/cca3154/lang/src/dispatcher.rs:186:30
|
186 |               pub const fn new(dispatchable: $dispatchable_fn<Msg, S>) -> Self {
|                                ^^^^^^^^^^^^
...
237 | / impl_dispatcher_for! {
238 | |     /// Dispatcher for storage preserving messages.
239 | |     struct Dispatcher(DispatchableFn);
240 | | }
| |_- in this macro invocation
|
= note: see issue #57563 https://github.com/rust-lang/rust/issues/57563 for more information
= help: add #![feature(const_fn_fn_ptr_basics)] to the crate attributes to enable
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

hi @Maar-io --
afaik ink! 2.1 and Cargo contract 0.6.2 aren't compatible with Substrate v2.0.0
The tutorial is getting updates to match ink! 3.0 (releasing soon) and Substrate v2.0.0
In the meantime, if you're not already I encourage you to ping the Riot channels for more real time QA/updates if you're not already around ( https://substrate.dev/community )
I am closing this issue but feel free to open it up or start another if you have additional issues. thanks!
cc @danforbes

@Maar-io what command are you running when you encounter this error? As Addie mentioned, ink! 3.0 is imminent and will be debuted at Sub0. This tutorial should be updated around that time. Ref https://github.com/substrate-developer-hub/substrate-contracts-workshop/pull/73
cc @Robbepop

Hi Dan,
last command that fails is:
cargo +nightly test

Can you try this? cargo +nightly-2020-06-01 test

@danforbes, you make me happy :) THANKS!!!
I can finally start playing with ink!
@wheresaddie, thanks for help, I will join the Riot


Wiki. Stories universal rendering. Misspelling in instruction

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Repro steps.

Look at screen (dot and hyphen in file name)

Has PR. #7178

Ok, but the wiki page at https://github.com/angular/angular-cli/wiki/stories-universal-rendering still has this issue. Must that be manually edited?

@BurningDog we re-publish the wiki on releases so it should be fixed soon.


Flex-grow-1 not in documentation

flex-grow-1 and flex-shrink-1, and probably a lot more classes are missing from the documentation...

Can i be assigned to this issue


Widgetset compilation every time

Hi,
Since I added your addon to my project, my widgetset gets compiled every single time I build the project. This didnt happened before (and should not happend). Can you take a look at this? Its quite annoying and time consuming.
Im using Vaadin 8.1.6.
Thanks!

Yes, I knew this is happening with the demo application, but I did not know it happens with apps using the add-on. It is weird issue with maven, and I do not yet know why it is happening. My setup with Renderers collection add-on is practically identical, and it works correctly.

Im using other addons and its not happening there. Anything I can do to help troubleshoot, just tell me!

Based on #40  I tried cloning your project and changing GridFastNavigation.gwt.xml to GridFastNavigationWidgetSet.gwt.xml (both the file name and in POM.xml) solves this issue and #40

Yes, I can confirm this. I had totally overlooked that minor detail.

Cool! Glad to help!

Yes, thanks alot for spotting this. I uploaded new version to Directory.

Could you merge your commits on master branch too?
Thanks!

Yes, a moment. That goes to version 1.1.7 for Vaadin 7.

Thanks a lot! Very kind and fast!

Thanks. I would appreciate your rating and feedback in the directory, vaadin.com/directory/component/gridfastnavigation-add-on


feature request: CNI file permissions more restrictive (600)

Expected Behavior

CNI-related CIS Benchmarks include:
1.1.9	Ensure that the Container Network Interface file permissions are set to 600 or more restrictive
1.1.10	Ensure that the Container Network Interface file ownership is set to root:root

Current Behavior

/etc/cni/net.d/10-calico.conflist file permission is 644.
root@master:/root$ ll /etc/cni/net.d/
total 8
drwxr-xr-x. 2 root root   57 Nov 16 05:33 ./
drwxr-xr-x. 3 root root   19 Apr 18  2022 ../
-rw-r--r--  1 root root  657 Mar 13 03:46 10-calico.conflist
-rw-------  1 root root 2712 Mar 13 03:46 calico-kubeconfig

Possible Solution

Steps to Reproduce (for bugs)

curl https://raw.githubusercontent.com/projectcalico/calico/v3.24.5/manifests/calico.yaml -O
kubectl apply -f calico.yaml
ll /etc/cni/net.d/

Context

Your Environment

Calico version: 3.24.5
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes 1.24.8
Operating System and version: Centos 7.8
Link to your project (optional):

After installation, I wonder if it is okay to manually change the above file(/etc/cni/net.d/10-calico.conflist) permissions to 600.

@moonek I don't particularly remember if we had a reason to have the current 644 permissions. It sounds like this is mostly a matter of testing so if you or any other community members would like to help us test out those permissions, let us know!

Looks like our install script maintains the permissions from the binaries packaged in the docker image: https://github.com/projectcalico/calico/blob/master/cni-plugin/pkg/install/install.go#L215
Should just be a matter of changing the permissions as part of the cni-plugin image build here: https://github.com/projectcalico/calico/blob/master/cni-plugin/Makefile#L132-L141

Hello, would this feature be considered for the next release?


[RokuChannelStoreRating] Add Roku Channel Store rating badges

Adding a few badges for the Roku Channel Store, specifically for rating.

I don't know who to tag for review, maybe @chris48s ?

There's no need to tag anyone explicitly. We're rather short staffed, so to speak, and we'll get to it when we can. To be fully transparent though reviews for net-new badges aren't as high on our priority list as some other core/maintenance related work that needs to get done, so it may (potentially) be a while before we get back to you.
Thanks for submitting a PR though, appreciate your willingness to contribute!


nfs-client: added support for arm64

Adding support in nfs-client-provisioner module for arm64 platform.

please check me.
/assign @jsafrane

Hi @snmagn
We are in the middle of migrating the NFS client code into a new home under  https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner. The migration PR is up for review at the moment. https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/pull/2
Thank you for this PR and sorry to have kept you waiting here. Can I circle back with you to raise the PR again in the new repo after the migration is completed?

Hi @kmova
Thank you for your comment.
That project is interesting. I also want to help with this PR.
What kind of process do you need?

As @kmova mentioned, we are in the process of archiving this repo and continuing work in https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner. Please reopen a PR in the new repo once https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/pull/2 has merged. Thanks for your patience! :)
Going to close this PR in order to be able to archive this repo.


Mistakenly recognized 0.7.0+26 as maven incompatible

Snapshot versions in the format of ${last tag}+${number of commits since that tag} would be mistakenly identified as dynamic versions and then declared as maven incompatible
This is too blunt (thanks @Vampire for finding this out)
private boolean isVersionMavenIncompatible(String version) {
    if (version == null) {
        return false;
    }
    if (version.contains("+")) {
        return true;
    }
    if (version.contains("latest")) {
        return !MavenVersionSelectorScheme.isSubstituableLatest(version);
    }
    return false;
}

Expected Behavior
no warning
Current Behavior

Maven publication 'maven' pom metadata warnings (silence with 'suppressPomMetadataWarningsFor(variant)'):

Variant runtimeElements:

contains dependencies that will produce a pom file that cannot be consumed by a Maven client.

kotlin.graphics.build-logic:platform-source:0.7.0+26 declared with a Maven incompatible version notation
These issues indicate information that is lost in the published 'pom' metadata file, which may be an issue if the published library is consumed by an old Gradle version or Apache Maven.
The 'module' metadata file, which is used by Gradle 6+ is not affected.

Context
I was declaring a dependency with the following GAV
kotlin.graphics.build-logic:platform-source:0.7.0+26
Steps to Reproduce
I can provide a repo in a moment, if needed
Your Environment
same as with the build scan
Gradle 7.0 M3

+ is also a valid character in version following the semver specification.
Imho also having .contains("latest") is too blunt.
It should probably be .endsWith(".+") and .startsWith("latest.").

Thanks for reporting this. I agree with @Vampire for the fixes.
That looks like a good candidate for a contributed fix if anyone is interested.

Given the simplicity of the fix, would you still like to have test regarding this?

Yes please, makes sure it never regresses.

I've encountered this issue in the 7.0 release. Can it please be fixed in 7.0.1?

Added to 7.0.1 for consideration. Taking community contribution for this one 😉

Perhaps @elect86 could submit their PR without providing any new tests.

Done

This will not be done for 7.0.1 as this is not a regression from 7.0.
The team has also limited bandwidth to tackle this right now.
Thanks for the initial PR, let's keep the discussion there but as mentioned earlier, it will require tests to be merged.

Since 6.8.3 did not generate warnings for "cannot be consumed by a Maven client", the messages appearing in 7.0 sure looked like a regression to the end user.

Does this fix actually fix these issues where Gradle is barfing on various version numbers with strange characters?
https://github.com/cossacklabs/themis/pull/824
https://github.com/flutter/flutter/issues/75600

No, this PR just fixes a false warning when publishing.
What you link to has nothing to do with Gradle itself, even if the people like to blame Gradle or call it "rot" or whatever. That just shows they cannot read. :-D
The stack trace of the error clearly shows that this happens in com.android. classes, so this seems to be a problem in the Android Gradle plugin and is nothing that could be fixed within Gradle. Instead a report has to be done to Google if there is none yet.

If you point me at the appropriate spot, I will happily harass the relevant Google people.

I'm not an android dev. But this page seems to list known issues of AS and AGP and then also links to how to properly report new bugs: https://developer.android.com/studio/known-issues

Btw. I'm not on the Gradle team like you stated in that flutter issue. I'm just a user, contributor and fellow (https://blog.gradle.org/gradle-fellowship), so I don't do any official statements or similar.

My fault for my imprecise language.  I just meant that someone who actually does some coding on Gradle looked at it.
I certainly wasn't trying to imply anything "official".  My apologies.
Sorry, for accidentally causing you grief.


Remove ambiguous Color math implementations

Objective
The implementations are very ambiguous, and it's easy to make bugs using them, especially Hsla variant. They treat Color as Vec4, which isn't quite right. Color values should be clamped to [0.0,1.0], but there are no checks. It adds/multiplies the first 3 values, regardless of the color's variant (There's no reason why you should multiply 3 values of Hsl at once). Also, I (and maybe some other people) initially thought Color::GREEN * 0.5 would result in semi-transparent green, but it makes it darker instead, so it makes it hard to read. Mul<f32> example (but the same errors apply to every other implementation):
// 2 different representation of one color. If you pass them to a function,
// the function may not handle it correctly, just like this:
let green = Color::GREEN;
let other_green = Color::Hsla {
    hue: 120.0,
    saturation: 100.0,
    lightness: 50.0,
    alpha: 1.0,
};
assert_ne!(green * 0.5, other_green * 0.5);

// as in iter_combinations.rs example
let emissive_green = green * 2.0;
// now emissive_green.g() is 2.0, which is not valid
// hsla fails to convert this value and the left value will be Color::WHITE
assert_ne!(emissive_green.as_hsla().as_rgba(), emissive_green);

Solution
Remove it! It's only used by 1 example (btw it's multiplying ORANGE_RED by 2 making .r() == 2.0, which is a bug, but the renderer somehow handles it).

Values > 1.0 are allowed for linear colours and there is tonemapping code in the shaders that handles mapping HDR values where the colour value is > 1.0 to within 0.0 to 1.0. The bloom PR also specifically benefits from values > 1.0 and it will be common to set emissive values > 1.0 I think, in order for the light to bloom to the surroundings.

Thanks for the context. Closing this out, in favor of a new issue.


server: support engine address

Signed-off-by: disksing<EMAIL_ADDRESS>What problem does this PR solve?
We plan to provide a heterogeneous engine with tikv, which may need to use different addresses to provide kv and raft services. Now kvproto has an optional engine_address to support this (https://github.com/pingcap/kvproto/pull/462).
The corresponding PD modification is mainly updating kvproto.
What is changed and how it works?

update kvproto.
add engine address in the clone option.
update api doc

Check List
Tests

Manual test (add detailed scripts or steps below)
check the output of store API.

Code changes

Has HTTP API interfaces change
Has persistent data change

Related changes

Need to update the documentation

Codecov Report

Merging #1785 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1785      +/-   ##
==========================================
- Coverage   77.42%   77.42%   -0.01%
==========================================
  Files         163      163
  Lines       16432    16433       +1
==========================================
  Hits        12723    12723
- Misses       2665     2666       +1
  Partials     1044     1044

Impacted Files
Coverage Δ

server/cluster.go
84.21% <100%> (-0.26%)
:arrow_down:

server/core/store_option.go
100% <100%> (ø)
:arrow_up:

server/grpc_service.go
57.48% <0%> (-1.31%)
:arrow_down:

client/client.go
68.6% <0%> (-1.3%)
:arrow_down:

server/member/leader.go
77.04% <0%> (-0.52%)
:arrow_down:

server/handler.go
51.38% <0%> (+0.5%)
:arrow_up:

server/region_syncer/client.go
78.94% <0%> (+1.31%)
:arrow_up:

server/tso/tso.go
81.65% <0%> (+2.75%)
:arrow_up:

pkg/mock/mockhbstream/mockhbstream.go
91.89% <0%> (+5.4%)
: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 e6c0609...1521a6c. Read the comment docs.

I don't like the name of engine.

@siddontang What's your suggestion?


add Plaster Template for CmdLets

Overview/Summary
Possible solution for using a Plaster template for scaffolding your Cmdlets.
Adds a Cmdlet file to Private/Public source folder depending on your parameter and adds corresponding test file in Tests folder.
Connected to Issue #15
Feedback Needed.
This PR fixes/adds/changes/removes

Cmdlet.ps1
CmdletTests.ps1
plasterMainfest.xml
README.md

As part of this Pull Request I have

[x] Checked for duplicate Pull Requests
[x] Associated it with relevant issues, for tracking and closure.
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[x] Updated relevant and associated documentation.

Another note: I just realized Plaster still haven't finished updating and still doesn't work 100% in ps 7 according to the plaster github page. We'll see how this turns out.

Agreed I think it might be better suited in the "resources" repo.
Regarding PS 7, the basic tests I have done seams to work fine. But lets see.


Enhanced Rdoc for ::new

I wanted to change the argument from +data+ to +string_or_io+, but that's a code change, not a doc change.   Let me know if that would have been ok.

@kou, ready for review.


Add Android support

Thanks for creating this project!
I'd like to use it in an Android app with Maui. Are you planning to add support for Android?

Yes, it should be possible to be adapted and used from Maui and it sounds like a nice enhancement.

Good news @DVaughan ,
@drasticactions added support for Android (among other platforms) in #30
It will be a breaking change (as it will require a new Nuget package) and it will be probably only released in 1.4.0, but the support is definitely coming soon.

Very nice! Thanks for the heads up @sandrohanea.


Update to add-in introduction

Added statement regarding coolness of add-ins.

@jasonjoh,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/add-ins/index.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

This was just for demonstration purposes, closing pull request without merging.


Remove ScientificTypesBase as dep

What is needed is already imported by MLJModelInterface.

Codecov Report

Merging #12 (4bfb67a) into dev (189fc3c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev       #12   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           24        24
=========================================
  Hits            24        24

Impacted Files
Coverage Δ

src/MLJTSVDInterface.jl
100.00% <ø> (ø)

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 189fc3c...4bfb67a. Read the comment docs.

@pazzo83


Clean up javascript code style

Be more consequent in JS files. It's differences in all files.
Maybe use node-jscs (grunt-jscs) to make it easier to write consistent markup?

Merged in around here: f8f3ce3234ea54e07c340bbd56dcae5fd448ebb7
For the next version of the framework, the plan is to add Sass and JS linters from the start.


Updated yarn.lock

yarn install is modifying yarn.lock.
This commit update those changes, so that yarn install does not cause untracked modifications.

@daveajones Quick win here.


Rrfdim commands

Hello, Can you help me: How the default users on server can delete your dimension - If he write /rftdim safedel  ->  Command is not allowed!

*yours dimension

This is a config option that must be enabled first before this works

I enable this:    B:playersCanDeleteDimensions=true
But it's still the same thing

Enabled on both server and client config?

yes

Can you show me both configs? (client and server)

Server: https://pastebin.com/Q3rSZ0Wr
Client: https://pastebin.com/ADfxM61J

? :)

@McJty ?

I'll get to this eventually. A bit busy right now

I cannot reproduce this and I don't understand why it wouldn't work. Can you try if deleting the dimension works by sending tnt to the dimension with the dimension editor?


IO APIC will never write NMIs

https://github.com/DeanoBurrito/northport/commit/847f221deb5cffe87c53157d00cdb905d1c5880c fixes the problem of accidentally overwriting NMI redirect entries, but now we can never write them at all.
My proposed solution is to just construct the redirect entry manually, and then use IoApic::WriteReg(entryNum, redirect); to skip over the protection logic. This is fine since it's coming from inside of the ioapic init code (where we can try to assume) we know what we're doing.

This is yet to cause any breaking bugs in emulation (acpi is reporting 0 NMIs in both vbox and qemu), so it's of low priority.

Fixed in https://github.com/DeanoBurrito/northport/commit/46d028657cf9b2087431eff62a7ebdf437cbe00f.