update user policies to grant full access to buckets

user policies grant permission to buckets, overriding the default private acl of objects created with s3fs.
no longer need usernames to be in multiple sets

Fixed a problem where users must have exactly one policy. If multiple policies apply to a user, whichever one gets created last will have its effect, while previous policies will have been deleted despite Tofu thinking they exist. All policies should be recreated now.


error

[X] Failed at importing tqdm from tdqm: No module named tqdm
Traceback (most recent call last):
File "skiptracer.py", line 16, in
from plugins.haveibeenpwned import HaveIBeenPwwnedGrabber
File "/root/skiptracer/plugins/haveibeenpwned.py", line 14, in
import cfscrape
ImportError: No module named cfscrape
i have both cfscrape and tdqm installed i am running kali linux amd64

Please try the latest version offered. We had some issues in the previous versions with Python2/3
Please ensure you are using python2 to launch ./skiptracer.py


refactor(core): consolidate endowments logic

This is not the major refactoring of core that we were sometimes discussing.
I'm refactoring the endowments bit so that they're more ready to use externally as a toolkit for putting the globals in place.

waiting to merge after release today


Mail for the mail server's FQDN loops back to itself

So after running my Modoboa server for a few days ( and able to send and receive mail - tested between my other email accounts as well as with some app services and things work as expected ) I check the logs just to see what's going on and find them filled with:
Feb 28 11:50:04 modoboa postfix/pickup[7874]: CC44916C7A: uid=0 from=<root>
Feb 28 11:50:04 modoboa postfix/cleanup[8397]: CC44916C7A<EMAIL_ADDRESS>Feb 28 11:50:04 modoboa postfix/qmgr[1998]: CC44916C7A<EMAIL_ADDRESS>size=1920, nrcpt=1 (queue active)
Feb 28 11:50:04 modoboa postfix/smtp[8399]: warning: CC44916C7A: defer service failure
Feb 28 11:50:04 modoboa postfix/smtp[8399]: CC44916C7A<EMAIL_ADDRESS>orig_to=<root>, relay=none, delay=0.06, delays=0.04/0.02/0/0, dsn=4.3.0, status=deferred (bounce or trace service failure)
Feb 28 11:50:04 modoboa postfix/cleanup[8397]: E383A16C7F<EMAIL_ADDRESS>Feb 28 11:50:04 modoboa postfix/bounce[8400]: CC44916C7A: sender non-delivery notification: E383A16C7F
Feb 28 11:50:04 modoboa postfix/qmgr[1998]: E383A16C7F: from=<>, size=3915, nrcpt=1 (queue active)
Feb 28 11:50:04 modoboa postfix/qmgr[1998]: CC44916C7A: status=deferred (bounce failed)
Feb 28 11:50:04 modoboa postfix/smtp[8399]: E383A16C7F<EMAIL_ADDRESS>relay=none, delay=0.01, delays=0/0.01/0/0, dsn=5.4.6, status=bounced (mail for computername.domain.tld loops back to myself)
Feb 28 11:50:04 modoboa postfix/qmgr[1998]: E383A16C7F: status=deferred (bounce failed)

And I do mean filled. Like nonstop. The domain name it's servicing is domain.tld, I don't have anything setup for computername.domain.tld ( where computername is the host of the Modoboa computer so basically this string is the mail server's FQDN ). Do I need to set this up in modoboa? I'm assuming this is some service account issue thing because root@whatever isn't going to be any regular mail account...

This is a beginners question for Postfix users. It is definitely NOT a
question for modoboa.
p@rick

armouredking<EMAIL_ADDRESS>

So after running my Modoboa server for a few days ( and able to send and receive mail - tested between my other email accounts as well as with some app services and things work as expected ) I check the logs just to see what's going on and find them filled with:
Feb 28 11:50:04 modoboa postfix/pickup[7874]: CC44916C7A: uid=0 from=<root>
Feb 28 11:50:04 modoboa postfix/cleanup[8397]: CC44916C7A<EMAIL_ADDRESS>Feb 28 11:50:04 modoboa postfix/qmgr[1998]: CC44916C7A<EMAIL_ADDRESS>size=1920, nrcpt=1 (queue active)
Feb 28 11:50:04 modoboa postfix/smtp[8399]: warning: CC44916C7A: defer service failure
Feb 28 11:50:04 modoboa postfix/smtp[8399]: CC44916C7A<EMAIL_ADDRESS>orig_to=<root>, relay=none, delay=0.06, delays=0.04/0.02/0/0, dsn=4.3.0, status=deferred (bounce or trace service failure)
Feb 28 11:50:04 modoboa postfix/cleanup[8397]: E383A16C7F<EMAIL_ADDRESS>Feb 28 11:50:04 modoboa postfix/bounce[8400]: CC44916C7A: sender non-delivery notification: E383A16C7F
Feb 28 11:50:04 modoboa postfix/qmgr[1998]: E383A16C7F: from=<>, size=3915, nrcpt=1 (queue active)
Feb 28 11:50:04 modoboa postfix/qmgr[1998]: CC44916C7A: status=deferred (bounce failed)
Feb 28 11:50:04 modoboa postfix/smtp[8399]: E383A16C7F<EMAIL_ADDRESS>relay=none, delay=0.01, delays=0/0.01/0/0, dsn=5.4.6, status=bounced (mail for computername.domain.tld loops back to myself)
Feb 28 11:50:04 modoboa postfix/qmgr[1998]: E383A16C7F: status=deferred (bounce failed)

And I do mean filled. Like nonstop. The domain name it's servicing is domain.tld, I don't have anything setup for computername.domain.tld ( where computername is the host of the Modoboa computer so basically this string is the mail server's FQDN ). Do I need to set this up in modoboa? I'm assuming this is some service account issue thing because root@whatever isn't going to be any regular mail account...

Reply to this email directly or view it on GitHub:
https://github.com/tonioo/modoboa/issues/837

--
[*] sys4 AG
https://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

Perhaps you should read my question again. Recall the one I actually asked?

Do I need to set this up in modoboa?

Judging by your answer I will assume that a command line edit in Postfix will suffice and not be overwritten by Modoboa.


complete assignment-2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
create dataframe ; splitting the training and testing dataset ; applying random states, performing preprocessing -- apply KNN-based imputation and robustscaler for numerical varaibles, and apply simple imputation and one-hotencoding for categorical variables ; create model pipeline ; performing cross-validation ; calculating performance metrics
What did you learn from the changes you have made?
python coding to perform the above functions
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
using other preprocessing methods
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Yes, the coding becomes more complicated when more task is to be involved. Overcome by searching on google and trial and error.
How were these changes tested?
result displayed at the interactive window of python in visual studio code.
A reference to a related issue in your repository (if applicable)
Checklist

[V ] I can confirm that my changes are working as intended

You have unfortunately made a pull request to the wrong repo. You shouldn't be making a pull request to UofT-DSI/scaling_to_production, but rather your own forked scaling_to_production repo. Please read the instructions on your onboarding Assignment Submission Guide more carefully.


Add dns_record interface

Add dns_record interface as defined in ISD125.
No charms implementing the relation have been released yet

@simskij @PietroPasotti  , would you mind reviewing this PR?

@gruyaume any feedback from you?


audio:add virtio snd driver

Summary
playback test:
nxplayer
device /dev/audio/pcm0p
playraw /data/test.wav 2 16 44100
stop

record test:
nxrecorder
device /dev/audio/pcm0c
recordraw /data/rec.pcm 2 16 16000
stop

Impact
new feature
Testing

@shipei-xiaomi
Please create a new config or update the existing config to test the driver.

@shipei-xiaomi please create a new pr to enable viritio-snd in one of qemu config and upate the readme file.


Roll Flutter Engine from 673d6b1cb102 to 40b7e6160f78 (1 revision)

https://github.com/flutter/engine/compare/673d6b1cb102...40b7e6160f78
2022-07-13<EMAIL_ADDRESS>Roll Skia from cef14e607db0 to e9effac80ca7 (2 revisions) (flutter/engine#34638)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


A GUI of some sort

As the title says, I think it would be nice to have a GUI for this. Not a super advanced one, but one that you could just open up and configure easily instead of running a command every time.
You might be able to base it off of the MSI gaming app as it would be pretty easy to make something like that in GTK:

It would be fairly difficult to provide anything more than text fields and buttons in a way such that all the functionality is exposed.

I would like something like this.
even if it was a text box to make it slightly easier doing testing on this.
maybe somthing like this? (super simple design)

would there be a way to show what the output might look like as well?  like have a output window on the side as well?

Use the fork, Luke. (and then pull request)

I'd be interested in some sort of basic gui. At the very least, I'm needing a much better understanding of how to use your tool, I'm having a hell of a time making things happen so far.

It seems to me that a GUI would be outside the scope of this project. You know the old unix philosophy "do exactly one thing and do it well".
I think the path of least resistance would be to script out a GUI in Python and Tkinter that just execs the binary to make changes. Probably use PolicyKit to handle the permissions.
Plus if the GUI were a separate project, it could support different backends for different mobos.


qlog output is malformed for packet_sent events when raw_encrypted is not None

Hello!
First, thanks for the community contribution of the qlog library!
I was investigating how qlog would handle events that include raw data and noticed a problem. When raw_encrypted or raw_decrypted are not None in the object to be serialized, the resulting qlog output is corrupt.
I have a fix for this issue and the PR is incoming.
Thanks again for the library!
Will

Fixed by https://github.com/cloudflare/quiche/commit/be23b6fcc3ce3bd595bef91931d248268b1da4c5.


Handle windows newlines

on Windows, you have to change line 76:
pub_pattern = r"modulus:\n\s+00:([a-f0-9\:\s]+?)\npublicExponent: ([0-9]+)"

to add a \r before each \n
pub_pattern = r"modulus:\r\n\s+00:([a-f0-9\:\s]+?)\r\npublicExponent: ([0-9]+)"

There's probably a more pythonic way to include the current os newline character, or maybe a way to tell openssl to use unix newlines.

Replacing '\r' with '' the string which is matched against this pattern should fix that, right? Or convert \r to \n and then reduce multiple \n to a single \n? That would even work if systems use \r instead of \n.

Microsoft Windows does not use bash... If you're trying to use a bash script on Windows, prepare for it to not work.
But you can replace \n to \r?\n in the regex (matches either windows newlines OR sane newlines). Since \r? matches either \r or nothing, it can match \r\n or just \n.

Bash?  I'm using Python.

Oh, sorry. I thought the project said it was a bash script. I guess I missed something right in front of me then...

I'm open to reviewing a pull request for windows support, but I don't have an easy way to develop my own pull request myself (I don't use a Windows system). Closing this for now, but feel free to open a pull request with actual proposed updates!

@diafygi finally!! non-Windows buddies <3


New localization strings (WIP)

I added more localization strings. I need to figure out how to change the separator in the view count from "," to " " (non-breaking space) and make the sub count match the text "subskrybentów". For example, it is supposed to be "50 454", not "50,4 tys. subskrybentów". Can you help me with this?

The view count change you did is wrong. It's supposed to have a comma (it didn't have a space in Polish version, not a comma either, simply view count, like: 12345).

If that's not a problem, I can commit over these changes to fix up some things so they remain proper, and add some stuff that is not in the original code yet to improve localization.

Okay.


Rev engine to pick up FlutterActivity change

https://github.com/flutter/flutter/issues/10072

LGTM


Antiforgery token validation failed. The required antiforgery cookie is not present. iOS Auth. iPad.

Describe the bug
A clear and concise description of what the bug is.
0. Default web app is unable to be signed in / registered from iPad.
Error logs show the following:
2019-09-19 12:12:15.0486|1|INFO|Microsoft.AspNetCore.Hosting.Internal.WebHost|Request starting HTTP/1.1 POST http://localhost_on_IIS:5015/Identity/Account/Login application/x-www-form-urlencoded 270
2019-09-19 12:12:15.0486|1|INFO|Microsoft.AspNetCore.Mvc.RazorPages.Internal.PageActionInvoker|Route matched with {page = "/Account/Login", area = "Identity", action = "", controller = ""}. Executing action /Account/Login
2019-09-19 12:12:15.0486|1|INFO|Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.AutoValidateAntiforgeryTokenAuthorizationFilter|Antiforgery token validation failed. The required antiforgery cookie ".AspNetCore.Antiforgery.pwALLqxivEg" is not present. Microsoft.AspNetCore.Antiforgery.AntiforgeryValidationException: The required antiforgery cookie ".AspNetCore.Antiforgery.pwALLqxivEg" is not present.
at Microsoft.AspNetCore.Antiforgery.Internal.DefaultAntiforgery.ValidateRequestAsync(HttpContext httpContext)
at Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.ValidateAntiforgeryTokenAuthorizationFilter.OnAuthorizationAsync(AuthorizationFilterContext context)
2019-09-19 12:12:15.0486|3|INFO|Microsoft.AspNetCore.Mvc.RazorPages.Internal.PageActionInvoker|Authorization failed for the request at filter 'Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.AutoValidateAntiforgeryTokenAuthorizationFilter'.
2019-09-19 12:12:15.0486|1|INFO|Microsoft.AspNetCore.Mvc.StatusCodeResult|Executing HttpStatusCodeResult, setting HTTP status code 400
2019-09-19 12:12:15.0486|2|INFO|Microsoft.AspNetCore.Mvc.RazorPages.Internal.PageActionInvoker|Executed action /Account/Login in 1.7633ms
2019-09-19 12:12:15.0518|2|INFO|Microsoft.AspNetCore.Hosting.Internal.WebHost|Request finished in 3.3011ms 400
To Reproduce
Steps to reproduce the behavior:

Create default site
scaffold identity framework
spin up either local db or connect to db
register on pc to make sure works
attempt to register on ipad
error is thrown in logs.
ipad screen shows no error. just a white screen.

Expected behavior
A clear and concise description of what you expected to happen.
I expect to be able to login/register via an ipad.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Include the output of dotnet --info
Host (useful for support):
Version: 2.1.12
Commit:  ccea2e606d
.NET Core SDKs installed:
1.1.11 [C:\Program Files\dotnet\sdk]
2.1.500 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 1.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
iPad 12.4.1
tried site in safari and chrome (on iPad)
keys are persisted on disk drive.
repo can be found here --> https://github.com/RA-Work-A/AntiForgeryToken

This is a known bug in Safari right now. Have you tried updating to iOS13?

@blowdart I haven't tried that. Is there a work-around? Our QA team is unable to test since all (sans older iPads) are unable to login?

Try https://github.com/aspnet/AspNetCore/issues/4647
Note that when Chrome changes how it works in January and we update our code to match them Safari will be broken again, but we will have more advice in place before then.

Yea I know, it's confusing. Google unilaterally changed how they implement same site in a way that will cause Safari to treat "None" as, in fact, strict. We'll have code samples in a month or so and updates.

@blowdart Can you take care of updating this issue when the samples are available?

@CribAd , my team and I ended up just upgrading our iOS devices to 13.x.x. This resolved our issue. For now anyway.


Invalid durations in log files

[x] I am using the latest version of PyInstaLive: 3.2.4.
[x] I have installed either Python 2.7.x or 3.5+: YOUR VERSION HERE
[x] I have read the README.
[x] I have read the FAQ.
[x] I have checked all existing issues, none of which could solve my issue.

I am using:

[x] Windows 10
[ ] Windows 8.1
[ ] Windows 8
[ ] Windows 7
[ ] Linux (distribution: )
[ ] macOS (version: )
[ ] Other (device & OS name: )

To report a bug, fill in the information below.
Pardon me not following the bug report layout, but I believe this is more of a general bug than a specific one. If need be, I will still provide files should you require them.
I was downloading the Instagram Livestream of a user earlier and later I noticed that the download duration was wrong and therefore the missing approximation was wrong too.
---------------------------------------------------------------------------
PYINSTALIVE (SCRIPT V3.2.4 - PYTHON V3.8.7) - 05-12-2021 03:41:52 AM
---------------------------------------------------------------------------
Overriding configuration file login with -u and -p arguments.
---------------------------------------------------------------------------
Successfully logged into account: None
---------------------------------------------------------------------------
Getting info for 'twicetagram' successful.
---------------------------------------------------------------------------
Livestream available, starting download.
---------------------------------------------------------------------------
Username    : twicetagram
Viewers     : 48803 watching
Airing time : 0 minutes and 40 seconds
Status      : Active
---------------------------------------------------------------------------
Downloading livestream, press [CTRL+C] to abort.
---------------------------------------------------------------------------
The livestream has been ended by the user.
---------------------------------------------------------------------------
Airtime duration  : 18 minutes and 5 seconds
Download duration : 17 minutes and 26 seconds
Missing (approx.) : 0 minutes and 39 seconds
---------------------------------------------------------------------------
Successfully saved 607 comments.
---------------------------------------------------------------------------
Merging downloaded files into video.
Successfully merged downloaded files into video.
---------------------------------------------------------------------------
There are no available replays.
---------------------------------------------------------------------------

However, the temporary video file came out to be 18:01 in length while the temporary audio was 18:00. I came to realize these lengths are false because the video cuts out earlier than the length because footage is missing. The merged video's duration is true to length at 17:50. However, the log said the download duration was 17:26, but that's not the case here with the merged segments.
Furthermore, I used the method to get the missing segments by using #121 successfully and restored 10 seconds. This brought the original result of PyInstaLive's livestream recording from 17:50 to 18:00 which was more in-line with the temporary file. Additionally, this result is much closer to the logged airtime of 18:05.
This is the case for not only this recording but plenty of others as I came to find out.

This happens when the stream enters the "interrupted" e.g. the livestreamer loses internet connection temporarily or minimizes Instagram app. During these moments no video is being streamed but the total airing time does not account for this and simply measures the elapsed time between the start of the stream and the current time.


feat(order): add magento 2.4.1 driver queries

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Fixes: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Are there API docs for Magento orders in 2.4.1? I found the release notes, but there isn't too much about orders.

@lderrickable https://devdocs.magento.com/guides/v2.4/graphql/queries/customer.html#customerOrders

While I question Magento's architecture decisions in modeling a lot of the order feature, this PR lgtm.
For posterity, I'll say that our query fragments could be greatly simplified if the CreditMemoItem, InvoiceItem, and ShipmentItem didn't have a bundle_options attribute (and therefore would not need a "Bundle" extended version of them; e.g. BundleCreditMemoItem), because that is included in the cart_item attribute already.
Also, it would be nice if InvoiceTotal and OrderTotal extended a common model, but this is not included in the API docs.

@lderrickable yeah the actual fields on a lot of the models are exactly the same, its only the name of the type that is different. Very unfortunate. Also the order model does not take into account multiple shipping or billing addresses.


OS/Arch Exclusions

Implement OS/architecture exclusions

@leucos Wouldn't it be easier to (optionaly) list supported OS - Arch pairs?

Yes indeed !

OK then, PR will come soon. :-)

Awesome !
If we could keep the keys lowercase that would be great.
Good luck !

Awesome !
If we could keep the keys lowercase that would be great.
Good luck !

No problem

@jakubvokoun I released a new version containing your contribution (and gokart is taking advantage of this)
You can binenv update -f binenv && binenv install binenv to play with it if you wish.


This script doesn't create the WIN10 vm.  Standard_A2_v2 is not available in specified location

@cloudcrazie - Can you please share what specific issue you have and may we know which Microsoft document link you used in reference to this issue?
Please share it with us so we can investigate further. Thank you.

I am getting error message saying Win 10 standard A2v2 is not available in West US.
[cid:278f4659-02af-4d2c-981f-4f4e880a6119]

From: Joyce Y<EMAIL_ADDRESS>Sent: Wednesday, April 1, 2020 7:35 PM
To: MicrosoftDocs/microsoft-365-docs<EMAIL_ADDRESS>Cc: cloudcrazie<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/microsoft-365-docs] This script doesn't create the WIN10 vm. Standard_A2_v2 is not available in specified location (#1541)
@cloudcraziehttps://github.com/cloudcrazie - Can you please share what specific issue you have and may we know which Microsoft document link you used in reference to this issue?
Please share it with us so we can investigate further. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/1541#issuecomment-607540929, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AO4DWFBIMBCEHDC655IUV6LRKPFUXANCNFSM4LZQZIHA.

@cloudcrazie - Thank you for submitting feedback.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome, let us know if it is something that can be called out in the docs.
If you don't mind please keep us posted here on the resolution so we can get the applicable information you are discovering back into the docs.


[Coverity CID :203465]Memory - corruptions in /tests/kernel/mem_protect/protection/src/main.c

Static code scan issues seen in File: /tests/kernel/mem_protect/protection/src/main.c
Category: Memory - corruptions
Function: write_text
Component: Tests
CID: 203465
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

Just like #18444, this is a false positive.  The test is deliberately attempting to write to the .text section and verify that the failure gets detected by the memory protection implementation.  Static analysis is correct that this is invalid, but that's the point.

Assign to @aasthagr as I don't know how to manage recording this as a false positive in the tool

I've done it. Just closing it.


NestedContainer.to_container method gets tracked individually per NestedContainer object

Looking into https://github.com/dask/distributed/issues/8958, I've noticed that for each NestedContainer object, its bound to_container method is tracked individually by the GC. This accounts for ~500k of 9MM objects in my workload. It would probably be better to stop tracking these individually.

On top, that is very likely a self referencing cycle so breaking this will benefit GC in more than one way


suggetion to disable the component in mobile

Hello there !!
I'm newbie at Vuejs and your component is being very useful for my project. I saw the prop disabled which I'm using to disable the component but...
What do you think is the best way to use it in case the webapp is on mobile ?

Hello, I'm glad to hear it's helping you!
You can just have a variable in your component that will be true/false depending on a verification and always pass this variable as a prop to vue-affix. You can either check the browser viewport width and assign false if it's lower than 1024 for example, or you can check the header to see the UserAgent that was sent.That will depend on your application needs.
You can find some pre made verifications based on UserAgent on google, while for the width verification you can just if (window.innerWidth < 1024) enabled = false

@eddiemf But in this case there is a trouble with resizing. After initializing the component calculates a wrong position with offset.

Maybe you should re-render it after resizing so it can be mounted again, preferably with a debouncing function. Let me know if that helps, or maybe post a fiddle with the bug so I can dig in and see if anything is wrong.

Try using vue-media-queries


511 - Configuration panel's layer list lines do not align with text boxes - LOW

When the 511 widget is configured in Internet Explorer or Firefox, the gray lines in the background of the listbox do not align with the other elements (e.g. drop-down menus, textboxes, checkboxes, etc.).  The behavior becomes more pronounced with the more layers that are added.

Now tracking this issue devtopia.


fix: fix nomail image in get_mails function

Proposed change

fix nomail image in get_mails function

Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests
[ ] Documentation update
[ ] Adds a new shipper
[ ] Update existing shipper

Additional information

This PR is related to issue: #416

Codecov Report

Merging #469 (cb917fb) into dev (76d8c97) will decrease coverage by 0.07%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##              dev     #469      +/-   ##
==========================================
- Coverage   99.27%   99.20%   -0.08%
==========================================
  Files           6        6
  Lines        1244     1250       +6
==========================================
+ Hits         1235     1240       +5
- Misses          9       10       +1

Impacted Files
Coverage Δ

custom_components/mail_and_packages/helpers.py
99.40% <85.71%> (-0.15%)
:arrow_down:


Boilerplate

Hi @mattcieslak
I'm getting toward putting together a manuscript with outcomes based on QSIPrep processing. Just curious about the state of the boiler plate. Right now it is light on details after FSL Fast on the anatomical side and devoid of processing steps for the DWI (see below for current boilerplate in 0.11.0 with my data). Is there a more expansive description of the details somewhere that I'm not finding?
Preprocessing was performed using QSIPrep 0.11.0, which is based on Nipype 1.5.0 (Gorgolewski et al. (2011); Gorgolewski et al. (2018); RRID:SCR_002502).

Anatomical data preprocessing
A total of 2 T1-weighted (T1w) images were found within the input BIDS dataset. All of them were corrected for intensity non-uniformity (INU) using N4BiasFieldCorrection (Tustison et al. 2010, ANTs 2.3.1). A T1w-reference map was computed after registration of 2 T1w images (after INU-correction) using mri_robust_template (FreeSurfer 6.0.1, Reuter, Rosas, and Fischl 2010). The T1w-reference was then skull-stripped using antsBrainExtraction.sh (ANTs 2.3.1), using OASIS as target template. Spatial normalization to the ICBM 152 Nonlinear Asymmetrical template version 2009c (Fonov et al. 2009, RRID:SCR_008796) was performed through nonlinear registration with antsRegistration (ANTs 2.3.1, RRID:SCR_004757, Avants et al. 2008), using brain-extracted versions of both T1w volume and template. Brain tissue segmentation of cerebrospinal fluid (CSF), white-matter (WM) and gray-matter (GM) was performed on the brain-extracted T1w using FAST (FSL 6.0.3:b862cdd5, RRID:SCR_002823, Zhang, Brady, and Smith 2001).

Diffusion data preprocessing
Several confounding time-series were calculated based on the preprocessed DWI: framewise displacement (FD) using the implementation in Nipype (following the definitions by Power et al. 2014). The head-motion estimates calculated in the correction step were also placed within the corresponding confounds file. Slicewise cross correlation was also calculated. The DWI time-series were resampled to ACPC, generating a preprocessed DWI run in ACPC space.

Many internal operations of QSIPrep use Nilearn 0.6.2 (Abraham et al. 2014, RRID:SCR_001362) and Dipy (Garyfallidis et al. 2014). For more details of the pipeline, see the section corresponding to workflows in QSIPrep’s documentation.

It looks like the boilerplate is pretty empty. Can you tell from the rest of the report whether distortion correction, denoising, unringing or bias correction were run?

Everything ran as expected. I've check across a couple of datasets with both 0.11.0 and 0.8.0 and they're all the same in terms of how much information they give.

Hi @mattcieslak,
I saw you release 0.12.0. Will this potentially fix the issues with the boilerplate?

Hey, sorry for the delay on this. I hope to fill in a bunch of the boilerplate and correct some of the text in the visual reports within the next few weeks.

Sounds good. Grateful for this tool.


Document how our OpenAI REST Client can be used

We have a REST Client for OpenAI (OpenAiRestApi.java)  that users could use manually if they want more control than Langchain4j's model provide.
We should document this

Oh great. It's more a low level for Langchain4j.

Right, but it's completely usable from user code as well .


zero_push 2.5.0

This release adds some features and makes some changes to the default http client.

add a way to configure multiple tokens (ios dev/prod, gcm dev/prod)
add methods for recently added API endpoints
change default encoding scheme to use JSON encoding instead of url-encoded parameters. This is so that number types get preserved as numbers and not stringified.
add backwards compatibility shim.
migrate stubbed responses to WebMock for more flexibility

@adamvduke any thoughts on releasing this?

Changing the default encoding to json instead of form-encoded is a backwards incompatible change, no?
Specifically for the instance we had recently with how the info parameter is encoded, and the workaround was using {info: JSON.dump(info)} ?


Configurable log level/format for gardener-seed-admission-controller

How to categorize this PR?

/area control-plane
/kind enhancement
What this PR does / why we need it:
This PR creates cli parameters --log-level=<debug/info/error> and --log-format=<json/text> in gardener-seed-admission-controller and enables its configuration in botanist package.
There is no dedicated configuration for gardener-seed-admission-controller and this PR does not create one for this purpose only. Thus, log-level and log-format settings of gardenlet are used for gardener-seed-admission-controller too.
Additionally, different log-levels/format could be set by changing the deployment while ignoring the corresponding managed resource during reconciliation.
Which issue(s) this PR fixes:
Part of #5191
Special notes for your reviewer:
Release note:

log-level and log-format of gardener-seed-admission-controller can now be configured.

Can you please check the failing tests?
GSAC errors with
2022-10-13T18:30:25.909228027Z stdout F unknown flag: --log-level


An offset for the downloaded data would be nice

I saw this in another yahoo archiver: if you interrupt the transfer, then next time that you run the script it will continue where you were the last time. This could be easily implemented with a log file where you save the last processed file, ie: a message, an attachment, etc. Then next time you can just go directly were the transfer was interrupted. Since yahoo stores everything in order of creation, this wouldn't be any problem. Just a count variable. My two cents.

Will handle this with #42


Save Trakt Token

Description
Once #61 is done, we can save the token on iOS side. We will need to:

[ ] Save the token
[ ] Update UI based on the Authentication state. (Requires #64)

Hi @c0de-wizard,
I'd like to pick this issue. Please assign it to me.


Helm chart cant transmit the config changes

Describe the bug
The HELM variables not transmitted to the pod
Environment details

Image/version of Ceph CSI driver : Canary and Git version: b2099eb
Helm chart version : ceph-csi-rbd-3.4.0
Kernel version :
Mounter used for mounting PVC (for cephFS its fuse or kernel. for rbd its
krbd or rbd-nbd) : fuse
Kubernetes cluster version : v1.21.2
Ceph cluster version : 14

Steps to reproduce
Steps to reproduce the behavior:
helm install
helm install -f values_csi_cephfs.yaml --namespace "ceph-csi-cephfs" "ceph-csi-cephfs" ceph-csi/ceph-csi-cephfs
Actual results
The mounts is in pending state.
I logged into one of the provisioner container with the following command with troubleshooting purpose:
kubectl exec -i -t -n ceph-csi-cephfs ceph-csi-cephfs-provisioner-74fff76cc6-j62cb --container csi-cephfsplugin -- /bin/bash
I was surprised the following files wasnt updated
/etc/ceph/ceph.conf
/etc/ceph/ceph.client.admin.keyring

After I updated the files manually, the following command successfully mounted the remote share
ceph-fuse -m 10.xx.xx.xx:6789 /mnt/cephfs/application1/ --no-mon-config
Here is my values_csi_cephfs.yaml
---
rbac:
  # Specifies whether RBAC resources should be created
  create: true

serviceAccounts:
  nodeplugin:
    # Specifies whether a ServiceAccount should be created
    create: true
    # The name of the ServiceAccount to use.
    # If not set and create is true, a name is generated using the fullname
    name:
  provisioner:
    # Specifies whether a ServiceAccount should be created
    create: true
    # The name of the ServiceAccount to use.
    # If not set and create is true, a name is generated using the fullname
    name:

# Configuration for the CSI to connect to the cluster
# Ref: https://github.com/ceph/ceph-csi/blob/devel/examples/README.md
# Example:
# csiConfig:
#   - clusterID: "<cluster-id>"
#     monitors:
#       - "<MONValue1>"
#       - "<MONValue2>"
#     cephFS:
#       subvolumeGroup: "csi"
#csiConfig: []

csiConfig:
  - clusterID: "518b8dff-0cfe-4758-8aea-8ccf523bb89f1"
    monitors:
      - "10.xx.xx.yy:3300"
      - "10.xx.xx.zz:3300"
      - "10.xx.xx.xx:3300"
    cephFS:
      subvolumeGroup: "TestVol"

# Set logging level for csi containers.
# Supported values from 0 to 5. 0 for general useful logs,
# 5 for trace level verbosity.
logLevel: 5

nodeplugin:
  name: nodeplugin
  # if you are using ceph-fuse client set this value to OnDelete
  updateStrategy: RollingUpdate

  # set user created priorityclassName for csi plugin pods. default is
  # system-node-critical which is highest priority
  priorityClassName: system-node-critical

  httpMetrics:
    # Metrics only available for cephcsi/cephcsi => 1.2.0
    # Specifies whether http metrics should be exposed
    enabled: true
    # The port of the container to expose the metrics
    containerPort: 8081

    service:
      # Specifies whether a service should be created for the metrics
      enabled: true
      # The port to use for the service
      servicePort: 8080
      type: ClusterIP

      # Annotations for the service
      # Example:
      # annotations:
      #   prometheus.io/scrape: "true"
      #   prometheus.io/port: "9080"
      annotations: {}

      clusterIP: ""

      ## List of IP addresses at which the stats-exporter service is available
      ## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
      ##
      externalIPs: []

      loadBalancerIP: ""
      loadBalancerSourceRanges: []

  profiling:
    enabled: false

  registrar:
    image:
      repository: k8s.gcr.io/sig-storage/csi-node-driver-registrar
      tag: v2.3.0
      pullPolicy: IfNotPresent
    resources: {}

  plugin:
    image:
      repository: quay.io/cephcsi/cephcsi
      tag: canary
      pullPolicy: IfNotPresent
    resources: {}

  nodeSelector: {}

  tolerations: []

  affinity: {}

  # Set to true to enable Ceph Kernel clients
  # on kernel < 4.17 which support quotas
  # forcecephkernelclient: true

  # If true, create & use Pod Security Policy resources
  # https://kubernetes.io/docs/concepts/policy/pod-security-policy/
  podSecurityPolicy:
    enabled: false

provisioner:
  name: provisioner
  replicaCount: 3
  strategy:
    # RollingUpdate strategy replaces old pods with new ones gradually,
    # without incurring downtime.
    type: RollingUpdate
    rollingUpdate:
      # maxUnavailable is the maximum number of pods that can be
      # unavailable during the update process.
      maxUnavailable: 50%
  # Timeout for waiting for creation or deletion of a volume
  timeout: 60s

  # set user created priorityclassName for csi provisioner pods. default is
  # system-cluster-critical which is less priority than system-node-critical
  priorityClassName: system-cluster-critical

  httpMetrics:
    # Metrics only available for cephcsi/cephcsi => 1.2.0
    # Specifies whether http metrics should be exposed
    enabled: true
    # The port of the container to expose the metrics
    containerPort: 8081

    service:
      # Specifies whether a service should be created for the metrics
      enabled: true
      # The port to use for the service
      servicePort: 8080
      type: ClusterIP

      # Annotations for the service
      # Example:
      # annotations:
      #   prometheus.io/scrape: "true"
      #   prometheus.io/port: "9080"
      annotations: {}

      clusterIP: ""

      ## List of IP addresses at which the stats-exporter service is available
      ## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
      ##
      externalIPs: []

      loadBalancerIP: ""
      loadBalancerSourceRanges: []

  profiling:
    enabled: false

  provisioner:
    image:
      repository: k8s.gcr.io/sig-storage/csi-provisioner
      tag: v3.0.0
      pullPolicy: IfNotPresent
    resources: {}

  attacher:
    name: attacher
    enabled: true
    image:
      repository: k8s.gcr.io/sig-storage/csi-attacher
      tag: v3.3.0
      pullPolicy: IfNotPresent
    resources: {}

  resizer:
    name: resizer
    enabled: true
    image:
      repository: k8s.gcr.io/sig-storage/csi-resizer
      tag: v1.3.0
      pullPolicy: IfNotPresent
    resources: {}

  snapshotter:
    image:
      repository: k8s.gcr.io/sig-storage/csi-snapshotter
      tag: v4.2.0
      pullPolicy: IfNotPresent
    resources: {}

  nodeSelector: {}

  tolerations: []

  affinity: {}

  # If true, create & use Pod Security Policy resources
  # https://kubernetes.io/docs/concepts/policy/pod-security-policy/
  podSecurityPolicy:
    enabled: false

topology:
  # Specifies whether topology based provisioning support should
  # be exposed by CSI
  enabled: false
  # domainLabels define which node labels to use as domains
  # for CSI nodeplugins to advertise their domains
  # NOTE: the value here serves as an example and needs to be
  # updated with node labels that define domains of interest
  domainLabels:
    - failure-domain/region
    - failure-domain/zone

storageClass:
  # Specifies whether the Storage class should be created
  create: true
  name: csi-cephfs-sc
  # Annotations for the storage class
  # Example:
  # annotations:
  #   storageclass.kubernetes.io/is-default-class: "true"
  annotations: {}

  # String representing a Ceph cluster to provision storage from.
  # Should be unique across all Ceph clusters in use for provisioning,
  # cannot be greater than 36 bytes in length, and should remain immutable for
  # the lifetime of the StorageClass in use.
  clusterID: 518b8dff-0cfe-4758-8aea-8ccf523bb89f1
  # (required) CephFS filesystem name into which the volume shall be created
  # eg: fsName: myfs
  fsName: cephfs
# 518b8dff-0cfe-4758-8aea-8ccf523bb89f
  # (optional) Ceph pool into which volume data shall be stored
  pool: cephfs_data
  # For eg:
  # pool: "replicapool"
  #  pool: ""
  # (optional) Comma separated string of Ceph-fuse mount options.
  # For eg:
  # fuseMountOptions: debug
  #fuseMountOptions: ""
  # (optional) Comma separated string of Cephfs kernel mount options.
  # Check man mount.ceph for mount options. For eg:
  # kernelMountOptions: readdir_max_bytes=1048576,norbytes
 # kernelMountOptions: ""
  # (optional) The driver can use either ceph-fuse (fuse) or
  # ceph kernelclient (kernel).
  # If omitted, default volume mounter will be used - this is
  # determined by probing for ceph-fuse and mount.ceph
  # mounter: kernel
  mounter: fuse
  # (optional) Prefix to use for naming subvolumes.
  # If omitted, defaults to "csi-vol-".
  # volumeNamePrefix: "foo-bar-"
#  volumeNamePrefix: ""
  # The secrets have to contain user and/or Ceph admin credentials.
  provisionerSecret: csi-cephfs-secret
  # If the Namespaces are not specified, the secrets are assumed to
  # be in the Release namespace.
  provisionerSecretNamespace: ""
  controllerExpandSecret: csi-cephfs-secret
  controllerExpandSecretNamespace: ""
  nodeStageSecret: csi-cephfs-secret
  nodeStageSecretNamespace: ""
  reclaimPolicy: Delete
  allowVolumeExpansion: true
  mountOptions: []
  # Mount Options
  # Example:
  # mountOptions:
  #   - discard

secret:
  # Specifies whether the secret should be created
  create: true
  name: csi-cephfs-secret
  # Key values correspond to a user name and its key, as defined in the
  # ceph cluster. User ID should have required access to the 'pool'
  # specified in the storage class
  adminID: admin
  adminKey: "XXX"
# This is a sample configmap that helps define a Ceph configuration as required
# by the CSI plugins.
# Sample ceph.conf available at
# https://github.com/ceph/ceph/blob/master/src/sample.ceph.conf Detailed
# documentation is available at
# https://docs.ceph.com/en/latest/rados/configuration/ceph-conf/
cephconf: |
  [client.rgw.ceprgw01]
  rgw dns name = objects.dev.xx
  rgw num rados handles = 1
  rgw realm = xx
  rgw thread pool size = 2048
  rgw zone = moi
  rgw zonegroup = poc

  [client.rgw.ceprgw02]
  rgw dns name = objects.dev.xx
  rgw num rados handles = 1
  rgw realm = xx
  rgw thread pool size = 2048
  rgw zone = moi
  rgw zonegroup = poc
  # Please do not change this file directly since it is managed by Ansible and will be overwritten
  [global]
  cluster network = xx.xx.xx.xx/28,yy.yy.yy.yy/28
  fsid = 518b8dff-0cfe-4758-8aea-8ccf523bb89f
  mon host = [v2:1xx.xx.xx.xx:3300,v1:xx.xx.xx.xx:6789],[v2:xx.xx.xx.yy:3300,v1:xx.xx.xx.yy:6789],[v2:xx.xx.xx.zz:3300,v1:xx.xx.xx.zz:6789]
  mon initial members = cemont01,cemont02,cemont03
  mon max pg per osd = 400
  mon osd down out interval = 28800
  mon pg warn max object skew = -1
  osd pool default crush rule = -1
  osd pool default min size = 2
  osd pool default size = 3
  public network = xxx
  rgw dynamic resharding = False
  rocksdb cache size =<PHONE_NUMBER>

  [mds]
  mds cache memory limit =<PHONE_NUMBER>78

  [mds.cepmds01]
  mds standby for rank = 0
  mds standby replay = True

  [mds.cepmds02]
  mds standby for rank = 0
  mds standby replay = True

  [osd]
  bluestore cache autotune = 0
  bluestore cache kv ratio = 0.2
  bluestore cache meta ratio = 0.8
  bluestore cache size ssd = 8G
  bluestore csum type = none
  bluestore extent map shard max size = 200
  bluestore extent map shard min size = 50
  bluestore extent map shard target size = 100
  bluestore min alloc size ssd = 4096
  bluestore rocksdb options = compression=kNoCompression,max_write_buffer_number=32,min_write_buffer_number_to_merge=2,recycle_log_file_num=32,compaction_style=kCompactionStyleLevel,write_buffer_size=67108864,target_file_size_base=67108864,max_background_compactions=31,level0_file_num_compaction_trigger=8,level0_slowdown_writes_trigger=32,level0_stop_writes_trigger=64,max_bytes_for_level_base=536870912,compaction_threads=32,max_bytes_for_level_multiplier=8,flusher_threads=8,compaction_readahead_size=2MB
  ms async max op threads = 10
  ms async op threads = 6
  osd client watch timeout = 15
  osd deep scrub interval = 604800
  osd heartbeat grace = 20
  osd heartbeat interval = 5
  osd memory target =<PHONE_NUMBER>8
  osd op num threads per shard hdd = 8
  osd op num threads per shard ssd = 8
  osd scrub begin hour = 21
  osd scrub end hour = 6
  osd scrub max interval = 604800
  osd scrub min interval = 259200

#########################################################
# Variables for 'internal' use please use with caution! #
#########################################################

# The filename of the provisioner socket
provisionerSocketFile: csi-provisioner.sock
# The filename of the plugin socket
pluginSocketFile: csi.sock
# kubelet working directory,can be set using `--root-dir` when starting kubelet.
kubeletDir: /var/lib/kubelet
# Name of the csi-driver
driverName: cephfs.csi.ceph.com
# Name of the configmap used for state
configMapName: ceph-csi-config
# Key to use in the Configmap if not config.json
# configMapKey:
# Use an externally provided configmap
externallyManagedConfigmap: false

Error in the provision pod if I want to create the PVC. The standard pod restart doesn't help

E1215 11:06:17.457773       1 controller.go:956] error syncing claim "8d8e71bc-9040-4355-a9b1-74d6990262f5": failed to provision volume with StorageClass "csi-cephfs-sc": rpc error: code = Aborted desc = an operation with the given Volume ID pvc-8d8e71bc-9040-4355-a9b1-74d6990262f5 already exists
I1215 11:06:17.457801       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"csi-vol-cephfs", UID:"8d8e71bc-9040-4355-a9b1-74d6990262f5", APIVersion:"v1", ResourceVersion:"34543832", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "csi-cephfs-sc": rpc error: code = Aborted desc = an operation with the given Volume ID pvc-8d8e71bc-9040-4355-a9b1-74d6990262f5 already exists

Expected behavior
pvc creation is working
Logs
If the issue is in PVC creation, deletion, cloning please attach complete logs
of below containers.

10.xx.xx.yy:3300

instead of v2 can you see using 6789 (v1) port helps?

@Madhu-1

It looks the /etc/ceph/ceph.conf contains the default config

[global]
auth_cluster_required = cephx
auth_service_required = cephx
auth_client_required = cephx

# Workaround for http://tracker.ceph.com/issues/23446
fuse_set_user_groups = false

# ceph-fuse which uses libfuse2 by default has write buffer size of 2KiB
# adding 'fuse_big_writes = true' option by default to override this limit
# see https://github.com/ceph/ceph-csi/issues/1928
fuse_big_writes = true

No, If I change the port to 6789 it still not working
I still not understand, if I change the /etc/ceph/ceph.conf to the content in the csi cephfsplugin container  above the fuse-mount is working from the container. (ofc with the addition of the admin keyring)

@tothger i have verified in canary local helm charts its working fine. please use 3.5.0 helm charts as we don't have support for custom ceph.conf in 3.4.0 release
[🎩]mrajanna@fedora ceph-csi $]kubectl get ns
NAME              STATUS   AGE
ceph-csi-cephfs   Active   82s
default           Active   2m7s
kube-node-lease   Active   2m9s
kube-public       Active   2m9s
kube-system       Active   2m9s
[🎩]mrajanna@fedora ceph-csi $]kubectl get po -nceph-csi-cephfs
NAME                                                      READY   STATUS              RESTARTS   AGE
ceph-csi-cephfs-1642755305-nodeplugin-5zn7m               3/3     Running             0          73s
ceph-csi-cephfs-1642755305-provisioner-66fb946f78-4xwp4   0/6     Pending             0          73s
ceph-csi-cephfs-1642755305-provisioner-66fb946f78-kcdlk   0/6     ContainerCreating   0          73s
ceph-csi-cephfs-1642755305-provisioner-66fb946f78-wj6gn   0/6     Pending             0          73s
[🎩]mrajanna@fedora ceph-csi $]kubectl exec -it ceph-csi-cephfs-1642755305-nodeplugin-5zn7m -c csi-cephfsplugin -nceph-csi-cephfs -- sh
sh-4.4# cat /etc/ceph/ceph.conf
[client.rgw.ceprgw01]
rgw dns name = objects.dev.xx
rgw num rados handles = 1
rgw realm = xx
rgw thread pool size = 2048
rgw zone = moi
rgw zonegroup = poc

[client.rgw.ceprgw02]
rgw dns name = objects.dev.xx
rgw num rados handles = 1
rgw realm = xx
rgw thread pool size = 2048
rgw zone = moi
rgw zonegroup = poc
# Please do not change this file directly since it is managed by Ansible and will be overwritten
[global]
cluster network = xx.xx.xx.xx/28,yy.yy.yy.yy/28
fsid = 518b8dff-0cfe-4758-8aea-8ccf523bb89f
mon host = [v2:1xx.xx.xx.xx:3300,v1:xx.xx.xx.xx:6789],[v2:xx.xx.xx.yy:3300,v1:xx.xx.xx.yy:6789],[v2:xx.xx.xx.zz:3300,v1:xx.xx.xx.zz:6789]
mon initial members = cemont01,cemont02,cemont03
mon max pg per osd = 400
mon osd down out interval = 28800
mon pg warn max object skew = -1
osd pool default crush rule = -1
osd pool default min size = 2
osd pool default size = 3
public network = xxx
rgw dynamic resharding = False
rocksdb cache size =<PHONE_NUMBER>

[mds]
mds cache memory limit =<PHONE_NUMBER>78

[mds.cepmds01]
mds standby for rank = 0
mds standby replay = True

[mds.cepmds02]
mds standby for rank = 0
mds standby replay = True

[osd]
bluestore cache autotune = 0
bluestore cache kv ratio = 0.2
bluestore cache meta ratio = 0.8
bluestore cache size ssd = 8G
bluestore csum type = none
bluestore extent map shard max size = 200
bluestore extent map shard min size = 50
bluestore extent map shard target size = 100
bluestore min alloc size ssd = 4096
bluestore rocksdb options = compression=kNoCompression,max_write_buffer_number=32,min_write_buffer_number_to_merge=2,recycle_log_file_num=32,compaction_style=kCompactionStyleLevel,write_buffer_size=67108864,target_file_size_base=67108864,max_background_compactions=31,level0_file_num_compaction_trigger=8,level0_slowdown_writes_trigger=32,level0_stop_writes_trigger=64,max_bytes_for_level_base=536870912,compaction_threads=32,max_bytes_for_level_multiplier=8,flusher_threads=8,compaction_readahead_size=2MB
ms async max op threads = 10
ms async op threads = 6
osd client watch timeout = 15
osd deep scrub interval = 604800
osd heartbeat grace = 20
osd heartbeat interval = 5
osd memory target =<PHONE_NUMBER>8
osd op num threads per shard hdd = 8
osd op num threads per shard ssd = 8
osd scrub begin hour = 21
osd scrub end hour = 6
osd scrub max interval = 604800
osd scrub min interval = 259200
sh-4.4#
sh-4.4#
sh-4.4# exit
exit
[🎩]mrajanna@fedora ceph-csi $]kubectl get cm ceph-cong ^C
[🎩]mrajanna@fedora ceph-csi $]kubectl get cm -nceph-csi-cephfs
NAME               DATA   AGE
ceph-config        2      2m17s
ceph-csi-config    1      2m17s
kube-root-ca.crt   1      2m29s
[🎩]mrajanna@fedora ceph-csi $]kubectl get cm ceph-config -nceph-csi-cephfs -oyaml
apiVersion: v1
data:
  ceph.conf: |
    [client.rgw.ceprgw01]
    rgw dns name = objects.dev.xx
    rgw num rados handles = 1
    rgw realm = xx
    rgw thread pool size = 2048
    rgw zone = moi
    rgw zonegroup = poc

    [client.rgw.ceprgw02]
    rgw dns name = objects.dev.xx
    rgw num rados handles = 1
    rgw realm = xx
    rgw thread pool size = 2048
    rgw zone = moi
    rgw zonegroup = poc
    # Please do not change this file directly since it is managed by Ansible and will be overwritten
    [global]
    cluster network = xx.xx.xx.xx/28,yy.yy.yy.yy/28
    fsid = 518b8dff-0cfe-4758-8aea-8ccf523bb89f
    mon host = [v2:1xx.xx.xx.xx:3300,v1:xx.xx.xx.xx:6789],[v2:xx.xx.xx.yy:3300,v1:xx.xx.xx.yy:6789],[v2:xx.xx.xx.zz:3300,v1:xx.xx.xx.zz:6789]
    mon initial members = cemont01,cemont02,cemont03
    mon max pg per osd = 400
    mon osd down out interval = 28800
    mon pg warn max object skew = -1
    osd pool default crush rule = -1
    osd pool default min size = 2
    osd pool default size = 3
    public network = xxx
    rgw dynamic resharding = False
    rocksdb cache size =<PHONE_NUMBER>

    [mds]
    mds cache memory limit =<PHONE_NUMBER>78

    [mds.cepmds01]
    mds standby for rank = 0
    mds standby replay = True

    [mds.cepmds02]
    mds standby for rank = 0
    mds standby replay = True

    [osd]
    bluestore cache autotune = 0
    bluestore cache kv ratio = 0.2
    bluestore cache meta ratio = 0.8
    bluestore cache size ssd = 8G
    bluestore csum type = none
    bluestore extent map shard max size = 200
    bluestore extent map shard min size = 50
    bluestore extent map shard target size = 100
    bluestore min alloc size ssd = 4096
    bluestore rocksdb options = compression=kNoCompression,max_write_buffer_number=32,min_write_buffer_number_to_merge=2,recycle_log_file_num=32,compaction_style=kCompactionStyleLevel,write_buffer_size=67108864,target_file_size_base=67108864,max_background_compactions=31,level0_file_num_compaction_trigger=8,level0_slowdown_writes_trigger=32,level0_stop_writes_trigger=64,max_bytes_for_level_base=536870912,compaction_threads=32,max_bytes_for_level_multiplier=8,flusher_threads=8,compaction_readahead_size=2MB
    ms async max op threads = 10
    ms async op threads = 6
    osd client watch timeout = 15
    osd deep scrub interval = 604800
    osd heartbeat grace = 20
    osd heartbeat interval = 5
    osd memory target =<PHONE_NUMBER>8
    osd op num threads per shard hdd = 8
    osd op num threads per shard ssd = 8
    osd scrub begin hour = 21
    osd scrub end hour = 6
    osd scrub max interval = 604800
    osd scrub min interval = 259200
  keyring: ""
kind: ConfigMap
metadata:
  annotations:
    meta.helm.sh/release-name: ceph-csi-cephfs-1642755305
    meta.helm.sh/release-namespace: ceph-csi-cephfs
  creationTimestamp: "2022-01-21T08:55:05Z"
  labels:
    app: ceph-csi-cephfs
    app.kubernetes.io/managed-by: Helm
    chart: ceph-csi-cephfs-3-canary
    component: nodeplugin
    heritage: Helm
    release: ceph-csi-cephfs-1642755305
  name: ceph-config
  namespace: ceph-csi-cephfs
  resourceVersion: "525"
  uid: 07bf3299-07aa-4960-a0fa-1de1908c2562


Tried creating a deploy group/policy from scratch and ran into issues

There is an issue with deploys where it can get stuck in a state where it will give the following error.

ClientError: An error occurred (ResourceConflictException) when calling the CreateFunction operation: Function already exist: test-dev
Deleting

Expected Behavior

Actual Behavior

I will be introducing a PR soon with the fix. It will require the "lambda:GetFunction" permission.

Create a profile with the following policies attached:
"iam:PassRole"
"s3:GetObject"
"lambda:CreateFunction"
"iam:GetRole"
"s3:PutObject"
"s3:CreateBucket"
now try zappa deploy dev a couple of times.

Context

I'm trying to figure out minimum amount of policy requirements per zappa commands.
Your Environment

Zappa version used: latest from pip
Operating System and Python version: ubuntu 16.04 and python 2.7.12 on pyenv
Link to your project (optional):
Your zappa_settings.py:
I'm using cookie cutter settings and app.py

What's happening here?

Starting from no permissions and gradually granting more led to an infinite loop situation where I needed to first try getting a function arn. Deleting my s3 zip files and deleting the lambda function had no effect on advanceing the deployer.
I broke some tests on travis inadvertently so I will try updating on the cli side of things and reopen my PR

Oh, okay, great. Thanks!


Mention 254 character limit of InputBox function

To test the character limit, run the following code. Try to paste the string, which is 256 characters long.
Sub InputBoxTest()
    Dim strInput As String
    strInput = InputBox("What?")
    Debug.Print Len(strInput) & " characters"
    Debug.Print strInput
End Sub

256 character string
1:3:5:7:9:12:15:18:21:24:27:30:33:36:39:42:45:48:51:54:57:60:63:66:69:72:75:78:81:84:87:90:93:96:99:103:107:111:115:119:123:127:131:135:139:143:147:151:155:159:163:167:171:175:179:183:187:191:195:199:203:207:211:215:219:223:227:231:235:239:243:247:251:255:

Docs Build status updates of commit e42e45d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/inputbox-function.md
:bulb:Suggestion
View
Details

Language/Reference/User-Interface-Help/inputbox-function.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel


[Documentation FIXED] fixed the wrong upgrade command on "Documentation/InstallOpenSearch/RPM"

Signed-off-by: Aimee Yao<EMAIL_ADDRESS>Description
the Documentation page "Documentation/InstallOpenSearch/RPM" have mistake with commands.
fixed the mistake about rpm.md ,the upgrade command was wrong , but the correct command is rpm -Uvh .
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks for your contribution Aimee! Going to close this one in favor of #628, where the command is also fixed.


[RFE] Support dumping data structures to a separate module

It'd be nice to have a way to dump all types from a schema into a module and then using that module to pull all of the data types for queries. This would simplify creating impl From<query_name::SomeGQLType> for each query's copy of relevant types.
Maybe:
#[derive(GraphQLQuery)]
#[graphql(schema_path = "…", only_types)]
pub struct SchemaTypes;

#[derive(GraphQLQuery)]
#[graphql(schema_path = "…", query_path = "…", types_from = schema_types)]
pub struct SchemaTypes;

Not sure how feasible this is.

Good point about the From impls. Let's think about it. This would be possible for GraphQL enums, scalars and fragments, since those always have the same fields, but I don't think it would work for objects, unions and interfaces because you can select different fields on them in different places in the same query or in different queries.
One small problem I see is that you could have one document (a .graphql file) with a fragment called FullResponse or something equally generic, and then, in another file, another FullResponse fragment - the names would clash.
Since scalars are just type aliases, that would just leave enums to be shared through the whole app, while fragments could be reused by multiple queries in the same document.

The other issue with fragments is when they aren't used as a complete type:
query {
  ...SomeFragment
  anotherField
}

Due to serde(flatten), a From<SomeFragment> wouldn't work here. I'm OK with just handling the types in the full schema though (I'm mainly looking at just enum and scalar). Looking at the spec, fragments aren't even allowed in the schema, so unless schema_path supports only_types as well, we shouldn't need to bother with it.

Having now used fragments, I see that the way the code is generated, dumping fragments to the module space also is wanted. The serde(flatten) bit isn't important for this; each fragment gets its own type.

Good point, I think this is a feature we want if we manage to find a solution to the fragment names clashing problem (nested modules?).

Well, fragments are always going to be in the query side, so how could they clash when sharing a schema namespace?

There has been progress on this. I think we can go a lot further with the CLI codegen and build script workflow that we are going to build. Maybe we can reuse that infrastructure in the derive flow when it is implemented. See issue #134 for some discussion.


[SDK] Add more unit tests for TrainingClient APIs - get_job_pods

What this PR does / why we need it:
New unit test for get_job_pods function
Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Fixes #2161
Checklist:

[ ] Docs included if any changes are user facing

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 35.374%

Files with Coverage Reduction
New Missed Lines
%

pkg/controller.v1/mpi/mpijob_controller.go
6
80.67%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
4374

Relevant Lines:
12365

💛  - Coveralls

/ok-to-test

/rerun-all

Thank you for this great contribution @YosiElias 🎉
/lgtm
/approve


Add option --longmode on to support Windows 32bit hosts

After some investigations in issue boot2docker/windows-installer#65 Allow installation on 32bit Machines! I just added the option --longmode on to make docker-machine working on my 32bit Windows 10 PC to start up the official 64bit boot2docker.iso.

I haven't tested implications with 64bit hosts or other VirtualBox host platforms. But in doubt we could just add the --longmode on flag if the docker-machine binary is windows/386.

Travis failed as VirtualBox 4.3.1 was used. The option --longmode was introduced with v4.3.4 as mentioned in https://www.virtualbox.org/ticket/12458?cversion=0&cnum_hist=10

@StefanScherer Could you squash your two commits and force push. This should by the way re-trigger the documentation build.

@dgageot squashed.

I ran the full IT test on a 64bits machine against virtualbox, without any problem.
As documentation is non existing on --longmode flag in virtualbox documentation ( search for longmode in this doc and have fun), I'm in favor of adding a guard on GOOS/GOARCH as @StefanScherer suggested.
It will make the code less readable, but we are adding a flag for which we dont really know what it does, to all create command regardless of the GOOS/GOARCH.
I am too defensive on this one @docker/machine-maintainers ?

Linking #2071

As documentation is non existing on --longmode flag in virtualbox documentation ( search for longmode in this doc and have fun), I'm in favor of adding a guard on GOOS/GOARCH as @StefanScherer suggested.

Yes, I agree with this.  Given such a guard I'm in favor of the change.

@StefanScherer do you feel like adding the guard ?

@jeanlaurent yes, sure. Just busy with some other Docker on ARM things ;-)

No hurries. Just checking, that the original PR author is still willing to move it forward.

@StefanScherer Any news on adding a guard and doing a rebase? The quicker we merge, the more we get feedback from testing on our machines.

@dgageot I'll have a look at it in the next few days.

LGTM

Just did a manual test with my old DELL Inspiron 530. Works fine:
PS D:\Users\Stefan> .\Dropbox\docker-machine-Windows-i386.exe create -d virtualbox dev
Running pre-create checks...
(dev) Default Boot2Docker ISO is out-of-date, downloading the latest release...
(dev) Latest release for github.com/boot2docker/boot2docker is v1.10.1
(dev) Downloading D:\Users\Stefan\.docker\machine\cache\boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v1.10.1/boot2docker.iso...
(dev) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
Creating machine...
(dev) Copying D:\Users\Stefan\.docker\machine\cache\boot2docker.iso to D:\Users\Stefan\.docker\machine\machines\dev\boot2docker.iso...
(dev) Creating VirtualBox VM...
(dev) Creating SSH key...
(dev) Starting the VM...
(dev) Check network to re-create if needed...
(dev) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: D:\Users\Stefan\Dropbox\docker-machine-Windows-i386.exe env dev

PS D:\Users\Stefan> .\Dropbox\docker-machine-Windows-i386.exe env dev | iex

PS D:\Users\Stefan> docker version
Client:
 Version:      1.10.0
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   590d5108
 Built:        Thu Feb  4 19:55:25 2016
 OS/Arch:      windows/386

Server:
 Version:      1.10.1
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   9e83765
 Built:        Thu Feb 11 20:39:58 2016
 OS/Arch:      linux/amd64

PS D:\Users\Stefan> Get-WmiObject Win32_Processor

Caption           : x64 Family 6 Model 15 Stepping 11
DeviceID          : CPU0
Manufacturer      : GenuineIntel
MaxClockSpeed     : 2400
Name              : Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
SocketDesignation : Socket 775

LGTM

:+1:

it's actually helpful tks u

Anyone can help me ?
i am using windows 2008 r2 to run docker 32 bit machine
Docker is watting ip and i am waitting it more than 2 hours


Inlined input queries (was: display search line instead of link line)

Currently, when you click on a search link (e.g. to GUS), a text box with OK and Cancel appears near the top of the window.  Instead, what about displaying it in place of the link line itself?  Visually, this could be a text box placed after the right-pointing arrowhead and followed by small icons ✅ and ❌ (or whatever icons you prefer).  If you hit ❌ or reload the page, the link line is redisplayed.  This would be more compact and eliminate unnecessary scrolling.

I have been thinking of doing something like this, although there are a couple of usability issues to consider. DocumentWidget has problems with query URLs when back/forward navigating over them. These should be addressed also to make the query UI behave more seamlessly.

I have been thinking of doing something like this, although there are a couple of usability issues to consider. DocumentWidget has problems with query URLs when back/forward navigating over them. These should be addressed also to make the query UI behave more seamlessly.

There is another very much related issue: #375


keyIdentifier deprecation in Chrome 53

New Chrome version started showing this warning in developer tools when cssreloader is active. Not exactly sure what functionality will break when 53 lands, but it would be worth a look and updating the extension.
cssreloader.content.js:24 'KeyboardEvent.keyIdentifier' is deprecated and will be removed in M53, around September 2016. See https://www.chromestatus.com/features/5316065118650368 for more details.

[Duplicate] Duplicate of #16 .
[Fixed] Fixed by Issue #17 .
Can we mark this complete?


Height adjustment

Hoping for help - can't figure out how to adjust the height on this version of ALVR - I am always a few metres below level...

Please try the Room-Setup

Hi mate – yes that’s what I did after a bit of searching….cheers mate!!
From: JackD83<EMAIL_ADDRESS>Sent: 28 February 2020 13:12
To: JackD83/ALVR<EMAIL_ADDRESS>Cc: nk33<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [JackD83/ALVR] Height adjustment (#128)
Please try the Room-Setup https://github.com/JackD83/ALVR/wiki/Room-Setup
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/JackD83/ALVR/issues/128?email_source=notifications&email_token=AGF2UG7N7XE3H6BPBJUVS7DRFEETXA5CNFSM4K5C5VU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENIO47Y#issuecomment-592506495 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGF2UGY5LHOZ2P67O73CGCTRFEETXANCNFSM4K5C5VUQ .  https://github.com/notifications/beacon/AGF2UG3DS24ST6PPHLYN2U3RFEETXA5CNFSM4K5C5VU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENIO47Y.gif

Hi mate,
Also, in Dirt 2, when i centre it i an sitting behind the front seat....so
I have to go back, set it then come forward again to be in the correct
place....is there a setting i can change in your alvr to correct this?
Thanks
Nick
On Fri, 28 Feb 2020, 13:12 JackD83<EMAIL_ADDRESS>wrote:

Please try the Room-Setup
https://github.com/JackD83/ALVR/wiki/Room-Setup
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JackD83/ALVR/issues/128?email_source=notifications&email_token=AGF2UG7N7XE3H6BPBJUVS7DRFEETXA5CNFSM4K5C5VU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENIO47Y#issuecomment-592506495,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGF2UGY5LHOZ2P67O73CGCTRFEETXANCNFSM4K5C5VUQ
.

First, it’s not my alvr, many people contribute to this. Second is no, there is no such option. I have not tried Dirt 2 yet, but project cars 2 has a key to recenter you directly behind the wheel in any direction. I think you need something like this to be able to use wheel and paddles as input


Replace the subidentifier field with a Relationship object

Replace the subidentifier field with a Relationship object
The specification currently uses the road_events.subidentifier field as a foreign key to relate objects.  However, the field does not explicitly describe how linked features are related.  Replacing road_events.subidentifier with a Relation object, like the one used in JSCalendar, will relate road event features and explicitly describe how features are related.
The Relationship object as defined in the JSCalendar Specification.
A Relation object defines the relation to other objects, using a possibly empty set of relation types. The object that defines this relation is the linking object, while the other object is the linked object.
The Relation object has the following properties:

@type: "String" (mandatory)

Specifies the type of this object. This MUST be "Relation".

relation: "String[Boolean]" (optional, default: empty Object)

Describes how the linked object is related to the linking object. The relation is defined as a set of relation types. If empty, the relationship between the two objects is unspecified.  Keys in the set MUST be one of the following values, or specified in the property definition where the Relation object is used, or a value registered in the IANA JSCalendar Enum Registry, or a vendor-specific value:

"first": The linked object is the first in a series the linking object is part of.
"next": The linked object is the next in a series the linking object is part of.
"child": The linked object is a subpart of the linking object.
"parent": The linking object is a subpart of the linked object.

The value for each key in the set MUST be true.
The Relationship object used in the Work Zone Data Specification.
Hierarchical Example

In the example below, the first road event feature ("road_event_id": "1") is the parent of the second, third, and fourth features ("road_event_id": "2", "road_event_id": "3", "road_event_id": "4")
Note the relationship in the first feature ("road_event_id": "1") can be left blank.  The children can point to the parent with the same effect.

{
  "road_event_feed_info": {},
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "road_event_id": "1",
        "relatioship": [{"child":"2"},{"child":"3"},{"child":"4"}]
      },
      "geometry": {
        "type": "LineString",
        "coordinates": []
      }
    },
    {
      "type": "Feature",
      "properties": {
        "road_event_id": "2",
        "relatioship": {"parent":"1"}
      },
        "geometry": {
          "type": "LineString",
          "coordinates": []
      }
    },
    {
      "type": "Feature",
      "properties": {
        "road_event_id": "3",
        "relatioship": {"parent":"1"}
      },
      "geometry": {
        "type": "LineString",
        "coordinates": []
      }
    },
    {
      "type": "Feature",
      "properties": {
        "road_event_id": "4",
        "relatioship": {"parent":"1"}
      },
      "geometry": {
        "type": "LineString",
        "coordinates": []
      }
    }
  ]
}

Sequential Example

The example below shows how to relate and order road event features.
The first road event feature ("road_event_id": "1") begins the sequence and identifies the second feature ("road_event_id": "2") as next in the sequence.
The second feature identifies the first feature ("road_event_id": "1") as the beginning of the sequence and the third feature ("road_event_id": "3") as next in the sequence.
The third feature identifies the first feature ("road_event_id": "1") as the beginning of the sequence and the fourth feature ("road_event_id": "4") as next in the sequence.
The fourth feature identifies the first feature ("road_event_id": "1") as the beginning of the sequence.

{
  "road_event_feed_info": {},
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "road_event_id": "1",
        "relatioship": {"first":"1","next":"2"}
      },
      "geometry": {
        "type": "LineString",
        "coordinates": []
      }
    },
    {
      "type": "Feature",
      "properties": {
        "road_event_id": "2",
        "relatioship":  {"first":"1","next":"3"}
      },
        "geometry": {
          "type": "LineString",
          "coordinates": []
      }
    },
    {
      "type": "Feature",
      "properties": {
        "road_event_id": "3",
        "relatioship":  {"first":"1","next":"4"}
      },
      "geometry": {
        "type": "LineString",
        "coordinates": []
      }
    },
    {
      "type": "Feature",
      "properties": {
        "road_event_id": "4",
        "relatioship":  {"first":"1"}
      },
      "geometry": {
        "type": "LineString",
        "coordinates": []
      }
    }
  ]
}

Added in #118


python311Packages.packageurl-python: 0.14.0 -> 0.15.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.packageurl-python is: Python parser and builder for package URLs
meta.homepage for python311Packages.packageurl-python is: https://github.com/package-url/packageurl-python
meta.changelog for python311Packages.packageurl-python is: https://github.com/package-url/packageurl-python/blob/v0.15.0/CHANGELOG.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.15.0 with grep in /nix/store/d1scr4in3gz10657vjdg4v3724390g6q-python3.11-packageurl-python-0.15.0
found 0.15.0 in filename of file in /nix/store/d1scr4in3gz10657vjdg4v3724390g6q-python3.11-packageurl-python-0.15.0

Rebuild report (if merged into master) (click to expand)

16 total rebuild path(s)

16 package rebuild(s)

First fifty rebuilds by attrpath
appthreat-depscan
checkov
cyclonedx-python
dep-scan
pip-audit
python311Packages.appthreat-vulnerability-db
python311Packages.cyclonedx-python-lib
python311Packages.packageurl-python
python311Packages.scancode-toolkit
python311Packages.tern
python312Packages.appthreat-vulnerability-db
python312Packages.cyclonedx-python-lib
python312Packages.packageurl-python
python312Packages.scancode-toolkit
python312Packages.tern
sbomnix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d1scr4in3gz10657vjdg4v3724390g6q-python3.11-packageurl-python-0.15.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.packageurl-python https://github.com/r-ryantm/nixpkgs/archive/e98e6acb233ed719b623de0b2d643ad01a2ef51b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e98e6acb233ed719b623de0b2d643ad01a2ef51b#python311Packages.packageurl-python

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d1scr4in3gz10657vjdg4v3724390g6q-python3.11-packageurl-python-0.15.0
ls -la /nix/store/d1scr4in3gz10657vjdg4v3724390g6q-python3.11-packageurl-python-0.15.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

32 packages built:

appthreat-depscan
appthreat-depscan.dist
checkov
checkov.dist
cyclonedx-python
cyclonedx-python.dist
dep-scan
dep-scan.dist
pip-audit
pip-audit.dist
python311Packages.appthreat-vulnerability-db
python311Packages.appthreat-vulnerability-db.dist
python311Packages.cyclonedx-python-lib
python311Packages.cyclonedx-python-lib.dist
python311Packages.packageurl-python
python311Packages.packageurl-python.dist
python311Packages.scancode-toolkit
python311Packages.scancode-toolkit.dist
python311Packages.tern
python311Packages.tern.dist
python312Packages.appthreat-vulnerability-db
python312Packages.appthreat-vulnerability-db.dist
python312Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib.dist
python312Packages.packageurl-python
python312Packages.packageurl-python.dist
python312Packages.scancode-toolkit
python312Packages.scancode-toolkit.dist
python312Packages.tern
python312Packages.tern.dist
sbomnix
sbomnix.dist

Maintainer pings
cc @armijnhemel for testing.

Result of nixpkgs-review pr 297776 run on x86_64-linux 1

32 packages built:

appthreat-depscan
appthreat-depscan.dist
checkov
checkov.dist
cyclonedx-python
cyclonedx-python.dist
dep-scan
dep-scan.dist
pip-audit
pip-audit.dist
python311Packages.appthreat-vulnerability-db
python311Packages.appthreat-vulnerability-db.dist
python311Packages.cyclonedx-python-lib
python311Packages.cyclonedx-python-lib.dist
python311Packages.packageurl-python
python311Packages.packageurl-python.dist
python311Packages.scancode-toolkit
python311Packages.scancode-toolkit.dist
python311Packages.tern
python311Packages.tern.dist
python312Packages.appthreat-vulnerability-db
python312Packages.appthreat-vulnerability-db.dist
python312Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib.dist
python312Packages.packageurl-python
python312Packages.packageurl-python.dist
python312Packages.scancode-toolkit
python312Packages.scancode-toolkit.dist
python312Packages.tern
python312Packages.tern.dist
sbomnix
sbomnix.dist


Alexa Guard: TypeError: 'NoneType' object is not subscriptable

Site note (I think not relevant within this issue): The log has an error during setup of component:
2019-07-04 10:28:24 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Error while setting up platform alexa_media
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/alexa_media/alarm_control_panel.py", line 35, in setup_platform
    hass)  \
  File "/config/custom_components/alexa_media/alarm_control_panel.py", line 88, in __init__
    guard_dict = (data['locationDetails']
TypeError: 'NoneType' object is not subscriptable

That is because, alexa guard is not yet available in germany.
Originally posted by @lweberru in https://github.com/keatontaylor/alexa_media_player/issues/242#issuecomment-508400440

Just a heads up, I'm not in Germany and I too am seeing this (I am in the U.S.).

@monsieurlatte Just to check, did you set up Alexa Guard? That is also the cause of the error. There is a PR that should resolve this if you want to check it. #245

Yep I did.  Thanks I’ll have a look at the PR.
On Jul 7, 2019, at 11:07 AM, Alan Tse<EMAIL_ADDRESS>wrote:
@monsieurlatte Just to check, did you set up Alexa Guard? That is also the cause of the error. There is a PR that should resolve this if you want to check it. #245
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@monsieurlatte oh wait, I didn't read your logs fully, that's a different issue. I'm going to move this to a different issue so please respond there.


[stable/rabbitmq] Rabbitmq chart: option to override RABBITMQ_NODENAME env variable

https://github.com/helm/charts/blob/a34b4603f6b61adf8d43edf81cdaad558ea74c00/stable/rabbitmq/templates/statefulset.yaml#L124
Tagging the recent committer: @f84anton
When running single pod for rabbitmq, using pod ip for server name is a bad idea since after every restart we will lose the data. Please give an option to override this value in values file or end of env configuration provide option to override any env from env map in the values.

https://github.com/helm/charts/pull/7807


Added multiple os build

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Multiple OS builds

What is the current behavior? (You can also link to an open issue )

Only Linux

What is the new behavior (if this is a feature change)?

macOS + Linux + Windows

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No

Other information:

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Arguments other than strings and Errors are lost when enhancedLog is called

🐞 Bug report
Description
Arguments other than strings and Errors are lost when enhancedLog is called.
🔬 Minimal Reproduction

Start scully in watch mode
Look at the enable reload on port, which is missing the port number, because it has type number

💻Your Environment
Angular Version:

11.1.5

Scully Version:

1.0.11

Closed by #1206
Thanks @Markus-Ende

Closed by #1206
Thanks @Markus-Ende


Host header field in outbound HTTP requests is wrong in some cases

At least in the cases where we use SO_ORIGINAL_DST to determine the destination IP address, the Host header field is set to the SO_ORIGINAL_DST IP address. Instead the Host header field (and :authority) should not change in these cases. In particular, if there wasn't a Host header field before, none should be added, and if there was a host header field then it should be preserved.
AFAICT, the only time we should change the Host header field is when we manually override the Host in FullyQualifiedAuthority::normalize().
/cc @seanmonstar @hawkw

AFAICT, the only time we should change the Host header field is when we manually override the Host in FullyQualifiedAuthority::normalize().

In fact, I think we shouldn't even change the Host header field in that case, as of now. When we implement TLS then we may need to have a way to do this Host header field override only for the case where we're using the Conduit TLS infrastructure (i.e. Conduit-to-Conduit transport). Otherwise I think we should not touch it.
Also, I say "Host header field" everywhere here, but the same thinking applies to :authority for HTTP/2.

To clarify the exact current behavior:

If an accepted HTTP/1 request has an absolute-form request-target, the authority replaces any Host header that may exist, per RFC7230 Section 5.4.
If the request-target is not in absolute-form, and there is a Host header, it is completely untouched.
If not in absolute-form, and there is no Host header, the Hostwill indeed get set to theSO_ORIGINAL_DST` address, but more as an accident than on purpose.

The reason for the 3rd case is that the request-target (Uri) must be built for telemetry recording, and to pass to hyper's Client. Inside the Client, hyper will automatically set the Host header if one does not exist.

If an accepted HTTP/1 request has an absolute-form request-target, the authority replaces any Host header that may exist, per RFC7230 Section 5.4.

RFC7230 Section 5.4 applies only to HTTP proxies. The Conduit proxy isn't acting as an HTTP proxy, because clients don't connect to it using CONNECT. It is acting as a gateway or a transparent proxy, so the UA and origin server requirements apply to it, not the proxy requirements. From the RFC:

However, an HTTP-to-HTTP gateway that wishes to interoperate with
third-party HTTP servers ought to conform to user agent requirements
on the gateway's inbound connection.

and

An "interception proxy" [RFC3040] (also commonly known
as a "transparent proxy" [RFC1919] or "captive portal") differs from
an HTTP proxy because it is not selected by the client.  Instead, an
interception proxy filters or redirects outgoing TCP port 80 packets
(and occasionally other common port traffic).

The reason for the 3rd case is that the request-target (Uri) must be built for telemetry recording

Consider the two cases:

Host: <IP_ADDRESS>
No Host, SO_ORIGINAL_DST = <IP_ADDRESS>

In the second case where we used SO_ORIGINAL_DST, the original URL was probably not http://<IP_ADDRESS>/.... Much more likely, the original URL was using a hostname.
Consequently, it would be really misleading to mix the telemetry for these two cases. Instead we should bucket the telemetry for these two cases separately.

and to pass to hyper's Client. Inside the Client, hyper will automatically set the Host header if one does not exist.

We need to be able to tell Hyper which authority to use as an override for routing purposes (the FullyQualifiedAuthority) and for telemetry purposes, in a way that doesn't cause it to change the HTTP message.

The Conduit proxy isn't acting as an HTTP proxy, because clients don't connect to it using CONNECT.

Interesting, I hadn't seen the distinction between the different intermediary types! Slight correction here, though, is that the rule in 5.4 isn't about CONNECT requests, but rather the opposite: Say you've stood up a proxy for your PC, and want to fetch to Conduit's website, and your client doesn't know how to tunnel, and just sent this:
GET https://conduit.io/docs HTTP/1.1
Host: www.conduit.io

That's a case where the proxy should replace the Host with Host: conduit.io.

Much more likely, the original URL was using a hostname.

I don't follow. If it was using a hostname, it would be included in the request, wouldn't it?

We need to be able to tell Hyper which authority

That much, at least, is possible! hyper will only set the Host header if one does not already exist. So, if in the proxy we know of a better hostname, we can set it prior to passing to hyper.
However, if we specifically want there to be no host header, hyper doesn't understand that. I've just added a config option to hyper's client to allow disabling automatic host header addition. (In most cases, it's a very useful feature, allowing client.get("https://conduit.io") to set the Host header for you.)

I don't follow. If it was using a hostname, it would be included in the request, wouldn't it?

An HTTP/1.0 request often won't have a Host header.

(In most cases, it's a very useful feature, allowing client.get("https://conduit.io") to set the Host header for you.)

I fully support that behavior of hyper, for those high-level APIs. Really the concern I have here is for transparent proxies, which really want a very low-level interface where the default is for nothing to change unless it is explicitly asked for something to be changed.

Slight correction here, though, is that the rule in 5.4 isn't about CONNECT requests, but rather the opposite: Say you've stood up a proxy for your PC, and want to fetch to Conduit's website, and your client doesn't know how to tunnel, and just sent this:
GET https://conduit.io/docs HTTP/1.1
Host: www.conduit.io

That's a case where the proxy should replace the Host with Host: conduit.io.

That's a case where an HTTP proxy should replace the Host. However, the definition of an HTTP proxy is one in which the client specifically CONNECTs to. Since the client never CONNECTs to Conduit, it isn't an HTTP proxy. therefore, when Conduit receives a GET request like the one you quoted, it shouldn't apply the rule for HTTP proxies rewriting the Host header.

However, the definition of an HTTP proxy is one in which the client specifically CONNECTs to.

Reference?
My understanding of "HTTP Proxies" is that they receive "proxy requests" where the resource is in absolute-form.  The http_proxy env variable does not cause curl to issue CONNECT requests unless the target is HTTPS.  For plaintext, CONNECT is not invoked.
FWIW, I don't think that Conduit should do anything special with HTTP proxy requests, because they're presumably being configured in the context that the destination is a proxy.
For example, imagine I run http_proxy=http://outbound-squid-proxy.corp.example.com curl http://conduit.io, this would result in a request like
GET http://conduit.io/
Host: outbound-squid-proxy.corp.example.com

I think we want to route the request to outbound-squid-proxy.corp.example.com and not conduit.io directly.

Nope, I'm totally wrong about how that curl command would work.  Disregard.
We will have to figure out how to configure proxies, but that can be done later.

However, the definition of an HTTP proxy is one in which the client specifically CONNECTs to. Since the client never CONNECTs to Conduit, it isn't an HTTP proxy. therefore, when Conduit receives a GET request like the one you quoted, it shouldn't apply the rule for HTTP proxies rewriting the Host header.

Reference?

Sorry, I was sloppy. What I meant is better described in the RFC text I quoted above:

An "interception proxy" [RFC3040] (also commonly known
as a "transparent proxy" [RFC1919] or "captive portal") differs from
an HTTP proxy because it is not selected by the client. Instead, an
interception proxy filters or redirects outgoing TCP port 80 packets
(and occasionally other common port traffic).

In our case, the client application is totally unaware of Conduit, so Conduit can't be acting as a HTTP proxy for it. In particular, as you mentioned in the Gitter discussion, the application that Conduit is proxying may be intending to communicate with an HTTP proxy like this:
Application <-> Conduit <-> Proxy

Therefore, we have to be really careful that we don't do "proxy stuff" that the application is expecting that proxy to do.
More generally, it goes back to the transparency idea: Unless we've explicitly chosen for the proxy to do some non-transparent behavior, all the behavior of the proxy should be transparent by default.

We can guess that the request was meant for a proxy if it has an absolute-form target in HTTP/1, but it's only a guess! It's not illegal at all to send an absolute-form target directly to the end server. And for HTTP/2, requests always has the :authority, so we can't really even guess there.

OK, so it's probably the case that we cannot detect proxy configuration transparentlyand it needs to be explicitly configured via the control plane?

OK, so it's probably the case that we cannot detect proxy configuration transparently and it needs to be explicitly configured via the control plane?

I do not know what you're asking here, but I'll guess: We don't provide any way for the user to configure their app to use Conduit as an HTTP proxy, so we can assume that we're not being used as a proxy. If/when that changes, regardless of how that configuration is done, we'll have to revisit. (I think it would be nice to have a configuration option for Conduit that allows the application to use it as a HTTP proxy and avoid the iptables stuff.)

If we really are trying to be transparent in the face of http-proxy requests, we should never route proxy requests through discovery/balancing, instead using the original dst. The only indication that the request is destined for a proxy is the absolute-form resource. And the only knowledge we have of the proxy address is the original dst on the socket...

I don't think we should do this extra complication of trying to detect when we're talking to a proxy. One of the ways where we're intentionally non-transparent is that we do L7 load balancing and different service discovery.

Therefore, we have to be really careful that we don't do "proxy stuff" that the application is expecting that proxy to do.

In particular, in theory the application might be sending hop-by-hop header fields (as noted in the Connection header field) that are intended for its HTTP proxy to consume. It would be very wrong for us to consume the hop-by-hop header fields. In particular, "Both the Proxy-Authenticate and the Proxy-Authorization header fields are hop-by-hop". The application would fail to authenticate to the proxy if we consumed the hop-by-hop header fields:
    Application <-> Conduit <-> Proxy

It would be very wrong for us to consume the hop-by-hop header fields.

So, it'd be useful to know then that we currently do strip off connection headers.
We'd also need to do so if we ever upgrade h1 to h2 internally, as most h1 connection headers are illegal in h2.

So, it'd be useful to know then that we currently do strip off connection headers.

Yeah, I know. That seems wrong to me but I don't know all the consequences of fixing it.

We'd also need to do so if we ever upgrade h1 to h2 internally, as most h1 connection headers are illegal in h2.

Upgrading to HTTP/2 isn't so much about removing hop-by-hop header fields as it is about replacing them with HTTP/2's alternative mechanisms.

I don't think that we can be transparent to HTTP proxies unless CONNECT is used; and I think that, in order to use HTTP proxies, users will have to explicitly provide configuration for this in the controller (i.e. routing).
If the proxy gets an HTTP request, it really doesn't have any reliable way to know whether the request is destined for a proxy or for the end-destination. and soI think we have to strip connection headers, for the sake of not leaking credentials (we definitely have to strip the Connection header -- but i'll argue we need to strip others as well).
Given a configuration like:
http_proxy=http://outbound-squid-proxy.corp.example.com curl http://conduit.io/docs

We'll get a request like:
GET https://conduit.io/docs HTTP/1.1
Host: conduit.io

How are we to know that this shouldn't go directly to the external destination?


change event is raised with old selected value when remove button used

If value is selected and remove button is used than change event is raised but with old value selected.
How to determine that value was actually removed?
Here is an example: https://jsfiddle.net/hedgic/m44fggL1/2/ Try to select value and then remove it. Expected result is to have null in value of ev.detail.value but I'm receiving an old value

The value should be of the item removed. This issue has been raised before though so I'm beginning to think it should just be null... I'll look into it

Is there a flag or any other event to know that value actually was removed, not selected?

The removeItem event is triggered when an item is removed. highlightItem is triggered when a item is selected/highlighted.


Fix webpack 2.2 regression

This PR fixes recent test failures.

Thanks. Yep, the apollo issue was already fixed by me too... seems I forgot to push that one.

You are very welcome.

在 2016年12月18日，17:29，Sebastian Werner<EMAIL_ADDRESS>写道：
Thanks. Yep, the apollo issue was already fixed by me too... seems I forgot to push that one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.