Add possibility to share a directory other than the working directory with the container

Currently, the only directory shared between the host machine and the container is the directory vagga.yaml resides in (known as /work inside the container). It would be useful to be able to share another directory with the container in the form of volumes. For example, maybe allow a prefix that makes vagga know that the directory is outside the container and in the host machine.
This has a few use cases:

It could help with making vagga cross-platform: applications that create symlinks in directories (such as postgresql in its data directory) can be installed on vagrant machines running on Windows.
It could help with people not wanting to litter the /work directory with artifacts such as logs. This would mean that you wouldn't have to have a logs directory in your repository with a .gitignore with something like this inside:

*
!.gitignore

Not sure if this idea is worth it, but putting it here since this is blocking me from installing postgresql in a vagga container on an Ubuntu virtual machine created by vagrant.

@parhamdoustdar Let me know if I didn't understand this correctly.
Vagga already supports this. What you need to do is:

Add the external volumes your are interested in the global settings:

external-volumes:
  Path:  /path/on/host

In your vagga.yaml create the directory where you want to mount this volume:

- !EnsureDir /Path

Mount the external volume to your directory inside the container:

volumes:
      /Path:   !BindRW /volumes/Path

Ah, yes, I forgot to note my issue with this approach. Thanks for the reminder!
My issue with this is that this means everyone who checks out your project must have a location defined in their global settings. Since as far as I know vagga is going for git clone <url> && vagga run, this adds extra steps.
What I'm proposing is the ability to add a volume in vagga.yaml that will be defined as an external volume, and then will be used, so that everyone wouldn't have to go and define it for themselves.
Am I understanding the issue right, or am I getting things wrong here? i haven't tried the external volumes feature, I have just read about it.

@parhamdoustdar this is a the security measure. The program that is running in vagga can't escape its project dir, or volumes defined in settings.
It's also not entirely clear why would you need that. I.e. you either need  project-specific data (and you can put that in /work) or you have some well-known location like /etc/.X11-unix. There might be some exceptions, for example if you have multiple projects in a company with different vagga files, you might say that every employee must declare volumes: { mycompany: /home/myuser/mycompany } and then any vagga.yaml can use some subfolder of /volumes/mycompany. So you have to set it up once, but not for every project.
For use case defined in the start of this ticket, we could probably allow using !BindRW for subfolders of projectdir/.vagga. Because you have already set up .vagga to handle symlinks and hard links anyway. But to do that we must better define the lifecycle of the volume. Like when they are going to be created and deleted, what if volume is removed from config and added back again, and how they behave then storage-dir is configured.
If you can come up with good spec for the volumes inside the .vagga, it's easy to implement.

@parhamdoustdar What I do is actually more like this: git clone <url> && ./setup_vagga.sh && vagga run
@tailhook I never told you but I actually don't like one limitation that comes with Global Settings.
When I first tried to use external-volumes, I've put paths that look something like this: ${WorkArea}/Folder and it complains that you need to use absolute paths.
In the environment I did that, every developer has different paths to their work area, so I was forced to create a configure script that has to be run by every developer separately every time they make a copy of the project, instead of having 1 general Global Settings(that is copied once) that every developer can use by default.
So, there are some limitations with the current setup, although one can work around them.

@lilianmoraru what is WorkArea? I think we can expand some things in ~/.vagga.yaml like ~ or even environment variables. But we can't allow mount arbitrary directory by default.

I think subdirectories of /work/.vagga are a perfect middleground. I
agree that we need to find a better life cycle for them though. Maybe
just create the directory the first time the build step is encountered
and let the user handle cleaning or removing it using other build steps,
and remove it when _clean --everything is implemented?
On 3/18/2016 8:03 PM, Paul Colomiets wrote:

@lilianmoraru https://github.com/lilianmoraru what is WorkArea? I
think we can expand some things in ~/.vagga.yaml like |~| or even
environment variables. But we can't allow mount arbitrary directory by
default.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/tailhook/vagga/issues/201#issuecomment-198441806

@tailhook It's an environment variable that points to the work area(project) the developer is working on currently. I haven't tested lately but I think even using $HOME won't work.

@lilianmoraru, well, we expand tilde ~ in storage-dir and cache-dir but not in volumes. Certainly we can fix that. But I'm a little bit sceptical about expanding arbitrary environment variables. For example, I'm not sure why adding WorkArea environment variable (to your bashrc or whatever startup script) is easier than adding a line to vagga.yaml.
@parhamdoustdar vagga _clean --everything is just a synonymous to rm -rf .vagga, with proper permissions (just FYI).
(not answering other points, I have to think about temporary/magical/hidden volumes a bit more)

Just another thought: for vagrant it's fine to allow mount everything. So your Vagrantfile and vaggrant-vagga may put default vagga settings with volumes: { host-system: / } or something similar.

Okay, you can take a look at #204

Okay, I think this issue will be exhausted when we implement #204.


MediaElement does not play immedieately when first chunk is loaded.

I am having the issue in playing the audio in my website. When the play button clicked, the song gets loaded correctly, but do no play after first chunk is loaded. It waits till the song loads upto 2.2mb 2.3mb and later on, we could hear the song. I dont know what is the issue. please check the website www.kannadaremix.in  and try to play any song in that website to understand the exact issue i am talking about. Please help me.

I am streaming the songs mp3 with php readfile ().

sounds like an encoding issue of your files. Read http://rigor.com/blog/2016/01/optimizing-mp4-video-for-fast-streaming to see if that helps you

Excellent article, helped me a lot. Problem exists. But minimized.


[HUDI-4781] Allow omit metadata fields for hive sync

Impact
This adds a new config hoodie.datasource.hive_sync.omit_metadata_fields, which default as previous behavoir.
WHen true, this won't create the metadata fields in the hive table, and hide them for end users
**Risk level:  low **
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Yep. Also tested with Athena ans spectrum
On September 6, 2022 1:43:35 AM UTC, Y Ethan Guo @.> wrote:
@. commented on this pull request.

@.*** Have you tested if the Hudi table can be queried with Hive, if the Hudi meta fields are not synced?

@@ -103,6 +103,11 @@ public class HiveSyncConfigHolder {
.key("hoodie.datasource.hive_sync.create_managed_table")
.defaultValue(false)
.withDocumentation("Whether to sync the table as managed table.");

public static final ConfigProperty HIVE_OMIT_METADATA_FIELDS = ConfigProperty

 .key("hoodie.datasource.hive_sync.omit_metadata_fields")

 .defaultValue(false)

 .sinceVersion("0.12.1")

We don't introduce new configs in minor releases.   This should be 0.13.0 which is the next major version.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/hudi/pull/6471#pullrequestreview-1096841811
You are receiving this because you were mentioned.
Message ID: @.***>


adding constraints to rating prompt example form

When I opened the xlsx file, I didn't understood where should I make changes to make it work. I checked the formdef.json file and added a constraint there. Please let me know where I am wrong.

@swaingotnochill the formDef.json file is a processed representation of the XLSX file. Your changes to file will be destroyed when the XLSX form is converted again. You can simply add the constraint column to the survey sheet. See https://docs.odk-x.org/xlsx-converter-reference/#optional-columns

Okay.. that's the confusion I had..Just that the example form is little different compared to other forms.I will make the necessary changes

@swaingotnochill A Pull Request is between two branches, so your changes for the rating prompt are in this Pull Request. Please use a separate branch for each Pull Request.

@wbrunette okay..sorry, it won't happen again.

@swaingotnochill can you resolve the conflicts so we know what is left in the PR, you may have already had other PRs that made this change. I want to make sure we have an understanding of what the code is that is in the PR and with conflicts it might be duplicates.

@wbrunette Sorry, was busy with exams. I will start working on the issues assigned.

@swaingotnochill no worries. Hope your exam went well.

@swaingotnochill this request has conflicts, before we can merge it the conflicts must be resolved

@swaingotnochill this request has conflicts, before we can merge it the conflicts must be resolved


NPE while getting table DDL in Clickhouse when user is readonly

https://user-images.githubusercontent.com/28875055/155171959-94089e38-11df-4f21-87b8-6dec3a7f13b2.mp4

Verified


Cannot use latest version of SwiftLint with SFSymbolsMacro due to conflicting swift syntax versions

Failed to resolve dependencies Dependencies could not be resolved because root depends on 'sfsymbolsmacro' 0.5.2..<1.0.0 and root depends on 'swiftlint' 0.55.1..<1.0.0.
'swiftlint' is incompatible with 'sfsymbolsmacro' because 'sfsymbolsmacro' 0.5.2 depends on 'swift-syntax' 509.1.1..<510.0.0 and no versions of 'sfsymbolsmacro' match the requirement 0.5.3..<1.0.0.
'swiftlint' >= 0.55.1 practically depends on 'swift-syntax' 510.0.2..<511.0.0 because 'swiftlint' 0.55.1 depends on 'swift-syntax' 510.0.2..<511.0.0 and no versions of 'swiftlint' match the requirement 0.55.2..<1.0.0.

Hey @BrentMifsud can you share how to reproduce this? could you provide a repo with a Package.swift or .xcodeproj that I could look at?

Its fairly easy to repro:

make a new Xcode project
add SwiftLint as a dependency
add SFSymbolsMacro as a dependency
Xcode will give you a package resolution error

you can do step 2 and 3 in the opposite order as well to reproduce the problem.
here's a project with the repro:
SwiftSyntaxConflict.zip

The provided project does not include the dependencies that you are using.
But I was able to reproduce by directly depending on the SwiftLint repository which is not recommended
See README.md

[!NOTE]
Consuming the plugins directly from the SwiftLint repository comes
with several drawbacks. To avoid them and reduce the overhead imposed, it's
highly recommended to consume the plugins from the dedicated
SwiftLintPlugins repository,
even though plugins from the SwiftLint repository are also absolutely
functional. If the plugins from SwiftLint are preferred, just use the URL
https://github.com/realm/SwiftLint in the package declarations above.
However, SwiftLintPlugins
facilitates plugin adoption massively. It lists some of the reasons that
drive the plugins as provided by SwiftLint itself very troublesome. Since
the plugin code and the releases are kept in sync, there is no difference
in functionality between the two, but you spare yourself a lot of time and
trouble using the dedicated plugins repository.
This document assumes you're relying on SwiftLintPlugins.

are you using https://github.com/SimplyDanny/SwiftLintPlugins or https://github.com/realm/SwiftLint for your project?
Switching to SwiftLintPlugins everything should work since it's precompiled and does not require a dependency on swift-syntax

Once 600.0.0 is out of prerelease I can update our dependency to match SwiftLint
Let me know if you have any other questions!

Thanks for the heads up. I didn't realize they had a separate plugin package.


Add a flag for pinning s3 client to current region

Fixes #4018 and changes the default behavior to not to pin the s3 client to any region (hence letting it to access buckets in any region).
@electrum can you please review?
@haitaoyao you now need to set this new flag to access your bucket in cn-north-1.

Merged, thanks!


Cannot find module ~/.config/mpv/scripts/rikai-mpv/rikaichamp-backend/extension/background_search_html.js

Hi,
I'm a bit confused about this.
Node complains that Cannot find module ~/.config/mpv/scripts/rikai-mpv/rikaichamp-backend/extension/background_search_html.js
But, there's a background_search_html.ts  file in src but no .js files in what I downloaded.
What do I do?
thanks

This is a duplicate issue

Hello, did these steps help https://github.com/fxmarty/rikai-mpv/issues/3#issuecomment-887492831 ? I tried to edit the README but I agree it is a bit involved just to install, I hope I can find a simpler solution.

Yes, thank you! I couldn't get the script to work though :(
It pops up a little blank window, beside the main mpv window, but nothing appears in it.
I think Qt just doesn't work well on MacOS.

Ah, that's bad to hear :-(
I somewhat expected it to break on MacOS, I explicitly call a function related to X11 (here https://github.com/fxmarty/rikai-mpv/blob/main/subtitles_popup_graphics.py#L120 ), so maybe this is a problem, but I think it should be not too hard to fix. If I gets hands on a MacOS once I will have a look.
Otherwise have you tried Memento https://github.com/ripose-jp/Memento ? I never tried it, but probably it works on MacOS and could fit your need.


Can I view all the schema and tables in one big spreadsheet?

[Enter feedback here]

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

ID: bf2518c0-9184-479d-5f39-755f8a10cddc
Version Independent ID: 9d76fac7-5f54-abbb-d860-fb1723d2149d
Content: Advanced hunting schema reference
Content Source: microsoft-365/security/defender-endpoint/advanced-hunting-schema-reference.md
Product: m365-security
Technology: mde
GitHub Login: @schmurky
Microsoft Alias: maccruz

@xiaoweiwu12701 Thank you for your feedback. As the Advanced hunting data schema changes very often there is no spreadsheet that is available as such to view all schema in one place.
@yogkumgit There are no changes required in the document.
Thanks
Sri

I do have a need to systematically download all the attributes, and its descriptions for documentation purposes. Doing a copy and paste line by line doesn’t seem to efficient.
Would you really consider this in the near future?
From: Sriraman M S @.>
Sent: Thursday, May 13, 2021 8:10 PM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Wu, Xiaowei (CGI Federal) @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Can I view all the schema and tables in one big spreadsheet? (#4962)
EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe.
@xiaoweiwu12701https://github.com/xiaoweiwu12701 Thank you for your feedback. As the Advanced hunting data schema changes very often there is no spreadsheet that is available as such to view all schema in one place.
@yogkumgithttps://github.com/yogkumgit There are no changes required in the document.
Thanks
Sri
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/4962#issuecomment-840906833, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOMPISM54C2XYTYY64BZZMDTNRS5ZANCNFSM44SLZVZA.
Proprietary/confidential information belonging to CGI Federal Inc. or its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for the delivery of this message to such person), or if you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply email.

@msbemba Thank you very much for the contribution and sharing this explanation. @xiaoweiwu12701 we do understand what you saying but in the current scenario scope is limited to this document only.  If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Buttons when disabled have unsightly dark grey backgrounds

Description of the Bug
Take the following three buttons: MDIconButton, MDFlatButton, MDRaisedButton:

In KivyMD 0.104.1 when these buttons are disabled they appear like:

In KivyMD 0.104.2 and the current master, when these buttons are disabled they appear like:

Code and Logs
The following code was used to generate the screenshots.  The widgets in the second column are given md_bg_color_disabled: [0,0,0,0] as a workaround.  Alternative workaround on line 51, if un-commented it will monkey patch BaseButton.md_bg_color_disabled = [0,0,0,0] globally.
from kivy.lang import Builder

from kivymd.app import MDApp
from kivymd.uix.button import BaseButton

KV = '''
MDGridLayout:
    cols: 2
    pos_hint: {'top': 1}
    padding: 50
    spacing: 50
    size_hint: None, None

    MDIconButton:
        icon: "language-python"
        disabled: sw.active

    MDIconButton:
        icon: "language-python"
        disabled: sw.active
        md_bg_color_disabled: [0,0,0,0]

    MDFlatButton:
        text: "MDFlatButton"
        disabled: sw.active

    MDFlatButton:
        text: "MDFlatButton"
        disabled: sw.active
        md_bg_color_disabled: [0,0,0,0]

    MDRaisedButton:
        text: 'MDRaisedButton'
        disabled: sw.active

    MDRaisedButton:
        text: 'MDRaisedButton'
        disabled: sw.active
        md_bg_color_disabled: [0,0,0,0]

    MDLabel:
        text: 'Disabled'

    MDSwitch:
        id: sw
        active: False
'''

class Example(MDApp):
    def build(self):
        #BaseButton.md_bg_color_disabled = [0,0,0,0]
        return Builder.load_string(KV)

Example().run()

Screenshots

Versions

OS: Ubuntu 21.04 and Android 10
Python: 3.9.5 and 3.8.1
Kivy: 2.0.0
KivyMD: 0.104.2 and 9fc99af

Glad you obviously agree that the current inconsistent and overly-dark disabled buttons looks nothing like the subtle light grey backgrounds of the Material Design spec :)
So differences from the Spec to start with:

for icon buttons which have no background to begin with, they should not gain one when disabled (whereas icon buttons are gaining a medium grey circular background)
there are no examples of disabled text buttons without backgrounds in the spec, but it would be inconsistent for them to gain one (whereas flat buttons are gaining a medium grey disabled background)
for buttons which start with a background, they gain a consistent light grey background (whereas raised buttons gain a background so dark it obscures the text of the buttons)

The KivyMD 0.104.1 behaviour is consistent with the Material Design spec (as far as stated); the KivyMD 0.104.2 behaviour is not.

@gbm001 We do not support KivyMD version 0.104.2

Fair enough - which version is supported, and I assume that means it is fixed?
I think the problem is that the disabled_hint_text_color, used to set the md_bg_color_disabled, is set to 0.38 opacity of black in theming.py via _get_disabled_hint_text_color - whereas the correct opacity is 0.38 of the active state plus (where appropriate) colour changes (which would normally be changing to greyscale).

@gbm001 If you know how to fix it - welcome to contributors :)

I think the thing to do is set the md_bg_color_disabled in update_md_bg_color based on a greyscale version of md_bg_color at 38% opacity (or something like that. I will have a play.

After eventually knocking something that works (by calculating the 38% opacity of whatever the
The whole thing is incredibly difficult to sort out because of the nightmarish hierarchy of button classes. For example:
MDFillRoundFlatIconButton (a filled, round class) inherits from
MDRoundFlatIconButton (a non-filled, round class) which inherits from
MDRoundFlatButton (a non-filled, round class) which inherits from
MDFlatButton (a non-filled, no-border class) which inherits from
BaseFlatButton which inherits from
BaseRectangularButton which inherits from
BaseButton (which finally inherits from ButtonBehaviour in Kivy).
That's crazily deep inheritance; it really needs refactoring with mix-in classes or something. I'll have a go at that rather than my hideous hacky 'it works so hey' approach to background colours.

@gbm001 Try it :)

#1139
A first draft of a refactoring...

Should all be fixed now in #1139; this bug can probably be closed?


Fix(eos_validate_state): Ensure graceful handling of command errors from ANTA

Change Summary

Ensure graceful handling of command errors from ANTA
Related Issue(s)
Fixes #4384
Component(s) name
arista.avd.<role-name>
Proposed changes

The ANTA API changed between the initial implementation and ANTA 1.0.0, but we missed updating failed -> errors[] when interacting with AntaCommand subclasses.
How to test

Asking @mtache to test and confirm :)
Checklist
User Checklist

N/A

Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[X] I have updated molecule CI testing accordingly. (check the box if not applicable)

The Exception is re-raised in the except block, and this is not handled gracefully in ANTA as suggested by the function docstring:
2024-08-21 15:59:09,322 p=12088 u=mtache n=anta.tests.hardware.VerifyEnvironmentPower | [ANTA Debug Mode] Exception raised while collecting commands for test VerifyEnvironmentPower (on device campus-leaf3d)
Traceback (most recent call last):
  File "/mnt/lab/projects/avd/ansible_collections/arista/avd/plugins/plugin_utils/eos_validate_state_utils/ansible_eos_device.py", line 140, in _collect
    response = await loop.run_in_executor(None, send_request)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/mtache/.ansible/collections/ansible_collections/arista/eos/plugins/httpapi/eos.py", line 97, in send_request
    results = handle_response(response_data)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/mtache/.ansible/collections/ansible_collections/arista/eos/plugins/httpapi/eos.py", line 190, in handle_response
    raise ConnectionError(error_text, code=error["code"])
ansible.module_utils.connection.ConnectionError: There seem to be no power supplies connected.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/mtache/.local/pipx/venvs/pyavd/lib/python3.12/site-packages/anta/models.py", line 530, in collect
    await self.device.collect_commands(self.instance_commands, collection_id=self.name)
  File "/home/mtache/.local/pipx/venvs/pyavd/lib/python3.12/site-packages/anta/device.py", line 178, in collect_commands
    await asyncio.gather(*(self.collect(command=command, collection_id=collection_id) for command in commands))
  File "/home/mtache/.local/pipx/venvs/pyavd/lib/python3.12/site-packages/anta/device.py", line 165, in collect
    await self._collect(command=command, collection_id=collection_id)
  File "/mnt/lab/projects/avd/ansible_collections/arista/avd/plugins/plugin_utils/eos_validate_state_utils/ansible_eos_device.py", line 156, in _collect
    raise e.__class__(msg) from e
ansible.module_utils.connection.ConnectionError: Command 'show system environment power' failed: There seem to be no power supplies connected.

I am pushing suggested changes, please review. Having an ERROR log allows to have the failure reported in the play.
The long term solution is to use the AsyncEOSDevice implementation in ANTA to benefit from the error handling of the _collect() function maintained there: https://github.com/aristanetworks/anta/blob/main/anta/device.py#L309C15-L309C23

When initially working on this implementation, we agreed that we would NOT fail the play for a device if a command fails, but rather let ANTA handle the exception. Once we get the results from ANTA we "translate" the errored tests into failed tests for the report. Your suggestion changes that behavior (play fails) and I don't think we want to change that for now. @ClausHolbechArista Thoughts?
Like you pointed out we will be using the native AsyncEOSDevice client in the future implementation :)

There are 2 points here:

how to handle an exception related to command collection
should we fail the play in Ansible if that happens

Regarding (1), it needs to be done in the _collect() function as exception handling is dependent on the underlying libraries. We do not have ANTA Exception to raise so the ANTA framework could distinguish errors and do proper handling as this is currently done in AsynEOSDevice._collect().
For (2), I don't have any opinion. I've juste noticed that if you issue an ERROR log using the logger instance, the play reports a failure (but all the tests are still run).

There are 2 points here:

how to handle an exception related to command collection
should we fail the play in Ansible if that happens

Regarding (1), it needs to be done in the _collect() function as exception handling is dependent on the underlying libraries. We do not have ANTA Exception to raise so the ANTA framework could distinguish errors and do proper handling as this is currently done in AsyncEOSDevice._collect().
For (2), I don't have any opinion. I've juste noticed that if you issue an ERROR log using the logger instance, the play reports a failure (but all the tests are still run).

If we want to keep the existing behavior (play doesn't fail), we can either use logger.warning and have a beautiful (or not) Ansible warning message, or we re-raise to ANTA and use ANTA loggers (like we do today). Unless I am missing something I don't see another option if we don't want to fail the play.

So this fix was supposed to address the issue you raised about using the wrong field. It was not supposed to change the way we do error handling. If we wish to change the strategy for error handling it should be done in a refactor or feature PR.

The updates breaks CI because imports from anta must be done inside try/except (welcome to Ansible plugins...). I will try to update it.

@mtache @carl-baillargeon please test this again. Thanks!

So I've changed the log level from error to warning to keep existing behaviour.
@carl-baillargeon, when this will be refactored to use the implementation at https://github.com/aristanetworks/anta/blob/main/anta/device.py#L309, the behaviour will change as the code raises error logs when an error occurs during an eAPI request.
Tested and working.


Please invite me to the Recode-Hive GitHub Community Organization

Name
Harsh Shivhare
Discord Username (if applicable)
250519
Additional Context
No response

Invitation sent to join the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see. You can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/Recode-Hive/people


Can you make a gui version?

Can you make a gui version of gooey?
Hello There, Future Issue Creator!

README: Are you suddenly seeing errors related to Alignment flags when starting Gooey? Upgrade your gooey installation to the latest version (pip install -U gooey) to resolve the errors! See this issue for additional information.

Found a bug? Just a friendly heads up, debugging it requires information from you! Make sure the template below is filled out in its entirety.

[ ] OS
[ ] Python Version
[ ] Gooey Version
[ ] Thorough description of problem

[ ] Expected Behavior
[ ] Actual Behavior

[ ] A minimal code example -- preferably copy/pastable in the issue itself (less time figuring out how to run your code == more time debugging!)
[ ] Screenshot (if visual quirk)
[ ] Anything else you may think will be helpful

Thanks! ^_^

I do not understand your question

Make a GUI builder for Gooey so you use GUI to turn a command line application to a gui application.


Introduce kinesis sink on function

Motivation
Introduce a kinesis sink which can consume messages from pulsar topics and publishes to configured kinesis stream.
Modifications

kinesis sink
e2e test for kinesis on function

Result
User can submit a function for a kinesis sink which can replicate pulsar messages to kinesis stream.
NOTE: it is based on #1902 and #1903

@srkukarni ^^

retest this please

retest this please

however I'm not sure kinesis dependency in broker is a good idea

@srkukarni I can remove it, but dependency scope is only test. also, if we add tests for any Source/Sink implementation available in Pulsar repo, will be helpful part in our test-suits as well.


Thumbnail gif file with crop: :centre always creates 1 scene gif

Describe the bug
Vips::Image.thumbnail("filename.gif[n=-1]", 200, height: 200, crop: :centre)  with animated GIF file saves static file with 1 scene only.
Without crop: :centre it saves animated file correctly
I used file https://i.pinimg.com/originals/96/50/f0/9650f01cd3334952b075f8cf55bedd60.gif for testing
To Reproduce
Steps to reproduce the behavior:
Run ruby script
# frozen_string_literal: true

require "bundler/inline"

gemfile(true) do
  source "https://rubygems.org"

  git_source(:github) { |repo| "https://github.com/#{repo}.git" }

  gem "ruby-vips"
  gem 'down'
end

GLib::logger.level = Logger::DEBUG

tempfile = Down.download("https://i.pinimg.com/originals/96/50/f0/9650f01cd3334952b075f8cf55bedd60.gif")

resized_image = Vips::Image.thumbnail("#{tempfile.path}[n=-1]", 400, height: 400, crop: :centre)
resized_image.write_to_file "/tmp/rabbit-with-crop.gif"
`browse /tmp/rabbit-with-crop.gif`

Expected behavior
File must be animated with all scenes cropped
Additional context
I have libvips 8.13rc1 compiled with cgif

Hi @aglushkov,
vipsthumbnail has logic for shrinking animated images. but not for cropping them. There's an enhancement issue here https://github.com/libvips/libvips/issues/2668


Readme.md landing image updated

Readme.md landing image updated with fresh macOS UI.

Awesome, thanks @ergenekonyigit!


[STORM-3675] Check worker process death using /proc/ directory

What is the purpose of the change
This function can replace a system "ps" command with existence/ownership check on /proc/ directory. In additional, on loaded nodes, ps command can take a few seconds. java.io.File.exists() is expected to be much faster. Note that File watcher does not work on /proc file system and the event based approach was coded/tested and then discarded.
How was the change tested
new test methods in ServerUtilsTest. Also run storm, kill worker and observe log to ensure proper detection

Unit test is failing
classname: org.apache.storm.utils.ServerUtilsTest / testname: testIsAnyProcessPosixProcessPidDirAlive
java.lang.AssertionError: There are 5 failures in test

Fixed the test for JDK11.


Added use_dpi setting to WindowDescriptor

Maybe closes #1118

Can I be removed from this thread

Wow, I wasn't expecting such quick action on my request. This is awesome. Thanks guys.

Can I be removed from this thread

You need to click unsubscribe.

On my machine the new UI from your example is somewhat broken in higher scaling modes, which doesn't make sense. Also I feel like we should call some stuff use_scaling etc instead of use_dpi, but I'm not sure.

Can you post some details and a screenshot?

So in theory, because the UI is all done based on logical pixels, the images should be identical (barring scaling artifacts). However, 100% gives me:

and 125% gives me

where for some reason the left panel stays the same width, and the font doesn't move down.

That is definitely better, although there's still some jank - if you go through this video frame by frame for example you can see a few examples.
https://user-images.githubusercontent.com/36049421/102925674-c28b8b00-448b-11eb-8327-ac6d0f5be1ef.mp4
That being said, it's not super important, because we don't really expect people to be changing window scaling on/off that often ™

Yeah, I'm fine with it stuttering when its being cycled at such a frequency. Given that it requires a full UI redraw on every switch, its not very surprising.

A couple of thoughts. Would system_scale_factor be a better name that true_scale_factor? Would it be simpler to make scale_factor the current scale factor instead of having to check use_dpi every where? This would either be the user selected value, or automatically updated when the system changes. Does it make sense to include the scale factor as part of the window resized event since these are tightly coupled?

Would it be simpler to make scale_factor the current scale factor instead of having to check use_dpi every where? This would either be the user selected value, or automatically updated when the system changes.

I don't exactly understand what you're offering here. Do you mean you want to change Window.scale_factor so it stores 1 when using physical pixels? In such a case, we'd have to store the scaling factor from winit in a seperate variable, effectively caching the result of scale_factor(). I dont think its worth the additional complexity.

Does it make sense to include the scale factor as part of the window resized event since these are tightly coupled?

They aren't tightly coupled. Both are triggered by seperate events, and are handled by diffrent pieces of code.

I think they mean that when scale_factor is ignored, the scale_factor method should return 1.
i.e. the current scale_factor method should be
pub fn scale_factor(&self)->f32{
    if self.use_dpi { 1 } else{ self.scale_factor }
}

and there should be a
pub fn requested_scale_factor(&self)->f32 {self.scale_factor}

This is the current behaviour, thats why I am confused.

Would it be simpler to make scale_factor the current scale factor instead of having to check use_dpi every where? This would either be the user selected value, or automatically updated when the system changes.

I don't exactly understand what you're offering here. Do you mean you want to change Window.scale_factor so it stores 1 when using physical pixels? In such a case, we'd have to store the scaling factor from winit in a seperate variable, effectively caching the result of scale_factor(). I dont think its worth the additional complexity.

Yeah, I guess it might be nice to specify a custom scale factor in addition to disabling the system value. And the scale_factor variable would always hold the current value, with another holding the system scale factor if required. While subjective, to me having scale_factor() perform logic to know what the real current scale factor is more complex than a separate variable recording the current system scale_factor independent of the currently selected scale factor.

Does it make sense to include the scale factor as part of the window resized event since these are tightly coupled?

They aren't tightly coupled. Both are triggered by seperate events, and are handled by diffrent pieces of code.

I was thinking that changes to the scaling factor will effect the resolution reported and from the users perspective it might be better to receive both of these at the same time.

Being able to supply your own "scale_factor" could be useful for testing.

I made a major rework to implement @blunted2night s suggestions and clean everything up.

rebased on master

I made a few tweaks. Feel free to contest any of them:

Removed window.set_physical_resolution(). its a nice shorthand, but i think it over-complicates things. Too much implicit behavior when it comes state changes (could change scale factor or requested resolution). Id prefer to just let people override scale factor to 1.0 then use set_resolution
Moved the scale factor override example logic to its own example. I want to keep the window_settings example simple
Renamed  "true scale factor" cases to "backend scale factor". "true" felt a bit too arbitrary / undefined to me.
Renamed instances of DPI to "scale factor". DPI != scale factor. DPI is a measure of pixel density whereas scale factor is a scale preference.
simplified event handling logic
style tweaks

Sounds good!


Crash with double free when removing lines after appending bbcode

Godot version
v3.4.4.stable.mono.official [419e713a2]
System information
linux 5.17.4-arch1-1
Issue description
This code crashes Godot Mono:
private void BbcodeTest() {
	while(GetLineCount() > 1)
		RemoveLine(0);

	for(int i=0; i<20; ++i) {
		AppendBbcode("[color=red]test[/color]\n");
	}
}

And this doesn't:
private void TextTest() {
	while(GetLineCount() > 1)
		RemoveLine(0);

	for(int i=0; i<20; ++i) {
		Text += "test\n";
	}
}

So it happens only when appending Bbcode.
Steps to reproduce

Remove some lines from RichTextLabel
Append Bbcode

Minimal reproduction project
bbcode_bug.zip

	Managed Stacktrace:
=================================================================
	  at <unknown> <0xffffffff>
	  at Godot.NativeCalls:godot_icall_1_35 <0x000c1>
	  at Godot.RichTextLabel:RemoveLine <0x000bf>
	  at Test:BbcodeTest <0x00097>
	  at Test:_Process <0x000cb>
	  at <Module>:runtime_invoke_void__this___single <0x000cc>
=================================================================```

This it the stacktrace I get after a crash

I can confirm it, it's not Mono related though, it's reproducible with GDScript:
extends RichTextLabel

func _process(delta):
        while get_line_count() > 1:
                remove_line(0)

        for i in range(20):
                append_bbcode("[color=red]test[/color]\n")

This doesn't happen with the same logic in _ready, but doing it in _process means doing it once per frame which is a lot for heavy bbcode operations, so it might have some race condition.
GDScript MRP: bbcode_bug.zip
The crash is reproducible in 3.x (73e6b7c14) with this stacktrace on Linux:
double free or corruption (fasttop)

Thread 1 "godot-3.x" received signal SIGABRT, Aborted.
0x00007ffff7b3404c in __pthread_kill_implementation () from /lib64/libc.so.6

(gdb) bt
#0  0x00007ffff7b3404c in __pthread_kill_implementation () from /lib64/libc.so.6
#1  0x00007ffff7ae72f2 in raise () from /lib64/libc.so.6
#2  0x00007ffff7ad345c in abort () from /lib64/libc.so.6
#3  0x00007ffff7b28a48 in __libc_message () from /lib64/libc.so.6
#4  0x00007ffff7b3ceaa in malloc_printerr () from /lib64/libc.so.6
#5  0x00007ffff7b3e9ba in _int_free () from /lib64/libc.so.6
#6  0x00007ffff7b40f8b in free () from /lib64/libc.so.6
#7  0x00000000048bd428 in Memory::free_static (p_ptr=0x8479f50, p_pad_align=false) at core/os/memory.cpp:168
#8  0x000000000385d776 in memdelete<RichTextLabel::Item> (p_class=0x8479f50) at ./core/os/memory.h:117
#9  0x000000000384d5d4 in RichTextLabel::_remove_item (this=0x847aa10, p_item=0x8479f50, p_line=0, p_subitem_line=0) at scene/gui/rich_text_label.cpp:1715
#10 0x000000000384db0a in RichTextLabel::remove_line (this=0x847aa10, p_line=0) at scene/gui/rich_text_label.cpp:1780
#11 0x0000000002808573 in MethodBind1R<bool, int>::call (this=0x7c9ed30, p_object=0x847aa10, p_args=0x7fffffffb128, p_arg_count=1, r_error=...) at ./core/method_bind.gen.inc:941
#12 0x000000000476e46a in Object::call (this=0x847aa10, p_method=..., p_args=0x7fffffffb128, p_argcount=1, r_error=...) at core/object.cpp:918
#13 0x000000000480cb03 in Variant::call_ptr (this=0x7fffffffb350, p_method=..., p_args=0x7fffffffb128, p_argcount=1, r_ret=0x0, r_error=...) at core/variant_call.cpp:1193
#14 0x0000000001c9b39e in GDScriptFunction::call (this=0x84e25e0, p_instance=0x8203130, p_args=0x7fffffffc498, p_argcount=1, r_err=..., p_state=0x0) at modules/gdscript/gdscript_function.cpp:1050
#15 0x0000000001c49580 in GDScriptInstance::call_multilevel (this=0x8203130, p_method=..., p_args=0x7fffffffc498, p_argcount=1) at modules/gdscript/gdscript.cpp:1211
#16 0x00000000036699da in Node::_notification (this=0x847aa10, p_notification=16) at scene/main/node.cpp:63
#17 0x00000000016d450e in Node::_notificationv (this=0x847aa10, p_notification=16, p_reversed=false) at ./scene/main/node.h:45
#18 0x00000000016d4b39 in CanvasItem::_notificationv (this=0x847aa10, p_notification=16, p_reversed=false) at ./scene/2d/canvas_item.h:163
#19 0x00000000016d51d5 in Control::_notificationv (this=0x847aa10, p_notification=16, p_reversed=false) at ./scene/gui/control.h:47
#20 0x000000000385c889 in RichTextLabel::_notificationv (this=0x847aa10, p_notification=16, p_reversed=false) at scene/gui/rich_text_label.h:38
#21 0x000000000476e587 in Object::notification (this=0x847aa10, p_notification=16, p_reversed=false) at core/object.cpp:927
#22 0x00000000036a1bc3 in SceneTree::_notify_group_pause (this=0x82ec170, p_group=..., p_notification=16) at scene/main/scene_tree.cpp:1057
#23 0x000000000369eef0 in SceneTree::iteration (this=0x82ec170, p_time=0.0166666675) at scene/main/scene_tree.cpp:552
#24 0x00000000016adee1 in Main::iteration () at main/main.cpp:2244
#25 0x0000000001670acb in OS_X11::run (this=0x7fffffffcd50) at platform/x11/os_x11.cpp:3933
#26 0x000000000165ccaf in main (argc=1, argv=0x7fffffffd688) at platform/x11/godot_x11.cpp:55

It doesn't crash in master, so the bug might be fixed there already.
CC @bruvzg

Similar crash: #59935

It's fixed in master by #49060, seem like a fix can be used for 3.x as well (with a minor changes).

Fixed by #60618.


watson interrupt  (feature request)

Let's say I am working on project A from 09:00, and suddenly at 09:30 I receive an unexpected phone call about project B. The phone call lasts until 09:50, and then I resume my work on project A.
Typically after the call at 09:50, I would correct my time tracking by doing something like:
watson stop --at 09:30
watson start --at 09:30 projectB
watson stop
watson start projectA

My feature request is to add a new command, watson interrupt, that would behave like this:
watson interrupt projectB --at 09:30
> Added projectB from 09:30 to now. Restarting projectA.

That's interesting, thanks!

With a recent merge, you should be able to do in a future release.
watson start --at 09:30 projectB
watson start projectA

Would be simple enough to replicate those steps for interrupt using ctx.invoke(), if i'm not mistaken @jmaupetit

With a recent merge, you should be able to do in a future release.
watson start --at 09:30 projectB
watson start projectA

Would be simple enough to replicate those steps for interrupt using ctx.invoke(), if i'm not mistaken @jmaupetit

Do you have visibility on when the next release will come out?


Better search ui

i would love to see more padding on individual elements like a compact mode and a default mode somewhat like raycast being honest it looks pleasing but I like your app's idea more than theirs just because of the ease of use and minimalism

Yeah, I always play around with ideas and I liked spotlight a bit better but I have to admit it is a bit crowded. I will change it soon.

Completely rebuilt the UI in the last version.


Add installation instructions for FreeBSD

Description
Hi. I am packaging SpoofDPI for FreeBSD and it is already available on latest branch of FreeBSD ports tree. So, I think it would be good if you add the installation instructions for FreeBSD too.
Additional context
Users can install this port either with package manager (SpoofDPI does only exist in only latest repository for now) or compiling from source code.

sudo pkg install spoofdpi
cd /usr/ports/net/spoofdpi && sudo make install

Users might want to enable SpoofDPI service by running:
sudo service spoofdpi enable
sudo service spoofdpi start

Users can also specify arguments in their /etc/rc.conf like this below.
spoofdpi_args="-port 8181 -enable-doh -dns-addr <IP_ADDRESS>"

Thanks.

can you please change the name of package to spoof-dpi? also, I've been thinking of move the installation guide to a separate markdown file. So it might take some time to solve this issue.

I will let you know if the documentation part is done, and then you can make a PR or i can do it for you.

In FreeBSD, the use of hyphens in port names is generally discouraged due to several important considerations that relate to naming conventions and technical functionality. Here’s a detailed overview based on recent discussions:
Naming Conventions

Semantic Separation

Hyphens are typically employed to delineate different semantic parts of a port name. For example, in names like py311-, p5-, or rubygem-*, the hyphen serves to separate the version or category from the main part of the name. This helps in organizing ports and understanding their purpose at a glance.

Versioning Clarity

In some cases, such as openjdk21-21.0.4+7.1, hyphens are used to separate the base name from its versioning information. This structured approach allows for easier identification of the port's version and its associated components.
Technical Limitations

Script Execution Issues

Hyphens can complicate script execution. In shell scripts, a hyphen may be interpreted as an option flag, leading to unexpected behavior or errors when executing commands related to the port. This can create additional complexity for users and developers.

Replacement with Underscores

To avoid these complications, it is common practice to replace hyphens with underscores in port names. For instance, the port spoofdpi should be maintained without a hyphen to align with this convention. Existing examples, such as www/tomcat-devel, illustrate this practice effectively.
Conclusion
Given these considerations, it is highly advisable not to use hyphens in port names within the FreeBSD ecosystem. While some exceptions exist, particularly in specific categories like Python ports (e.g., py39-xxx), the general guideline is to prioritize clarity and functionality. By adhering to this convention, developers can help ensure that ports are easily manageable and less prone to execution errors, ultimately enhancing the user experience.

Now you can make a PR to update the docs!


Add param to let you search for legislators in all sessions

See https://github.com/aclu-national/scorecards/issues/65 & https://github.com/aclu-national/scorecards/issues/61

these urls should work
https://elections.api.aclu.org/v2/congress/legislators?session=all
https://elections.api.aclu.org/v2/congress/legislators?include=name&session=all
we could just call get_all_legislators two times, for 115 and 116
otherwise we do some refactoring


After setting navigateToLoginRequestUrl: true still redirecting to home page instead of requested url

Core Library
MSAL.js v1 (@azure/msal or msal)
Core Library Version
1.1.2
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
none
Public or Confidential Client?
Public
Description
When we access our webpage with any direct URL(eg: locahost/home/admin) it'll redirect to microsoft login authentication(login redirect) after successful login it is redirecting to homepage (localhost/home). instead it should redirect to calling URL
MSAL Configuration
auth: {
            clientId: 'clientID',
            authority: 'authority',
            redirectUri: window.location.origin,
            protectedResourceMap: 'protectedResourceMap',
            navigateToLoginRequestUrl: true
        },
        cache: {
            //cacheLocation:'cacheLocation'
            cacheLocation:("localStorage" as CacheLocation),
            storeAuthStateInCookie:isIE
        }

Relevant Code Snippets
No response
Identity Provider
Azure AD / MSA
Source
External (Customer)

https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/929 facing similar issue.

Upgrading version needs lot of changes. Is there a way to fix this in existing "msal": "^1.4.4" @jo-arroyo @sameerag

@asvashrith Unfortunately we only support the latest Angular version as there are too many backward compat issues in the framework. We are only supporting new work and enhancements in<EMAIL_ADDRESS>and other wrappers based on the same.


Introduce create_account kernel section

Tests failing due to - https://github.com/0xPolygonMiden/miden-base/pull/185.  Rebasing will fix tests once merged.
Introduces account creation logic in the kernel.
We identify a new account by checking if the nonce is equal to zero. If the account is new then we enforce the condition that the nonce must be incremented in the transaction, this condition is enforced in the epilogue.  We now apply two permutations of the hashing function to compute the seed digest and as such the work has doubled.  To account for the doubling of work I have reduced the required trailing bits by one.
closes: #87, #84

We could still use the nonce, but then the block producer would need to know the nonce not only for new accounts but also for existing ones. Also, we'd need to change how we compute hash of the account so that we don't leak any other info (i.e., the hash could be computed as hash(nonce, hash(account_id, vault_root, storage_root, code_root)).
We could provide the is_new_account flag as an input to the transaction kernel.

good catch!  I think there may be a third option we can consider here. Set the initial account hash public input to [ZERO; WORD_SIZE] for new accounts.

Since the block producer will need to check account state hash against the account DB anyway, I'm not sure we need to do this check as the part of the transaction kernel. This would simplify the code, but also would mean that the user can update block_ref input without the need to update the Merkle authentication path for the account.

Good point, I will remove the account db lookups.

I think there may be a third option we can consider here. Set the initial account hash public input to [ZERO; WORD_SIZE] for new accounts. What do you think is preferable?

And then the actual account state would be provided non-deterministically (and verified against the ID provided via stack inputs)? I think this would be preferable - though, we should think through potential attack vectors here (I'm not seeing any, but it's also pretty late for me :) )

I think there may be a third option we can consider here. Set the initial account hash public input to [ZERO; WORD_SIZE] for new accounts. What do you think is preferable?

And then the actual account state would be provided non-deterministically (and verified against the ID provided via stack inputs)? I think this would be preferable - though, we should think through potential attack vectors here (I'm not seeing any, but it's also pretty late for me :) )

Yes exactly.  We would have a conditional branch based on the initial account hash.  If the initial account hash is an empty word then we verify the account data satisfies new account requirements - if it is not empty then we apply the checks we currently have in place for existing accounts.  I don't see any attack vectors but I will give it some more thought.


Deprecation Warning in PHP 7.4+ due to Dynamic Property Creation

Hello,
I am currently using the huaweicloud-sdk-php-obs SDK in a PHP 7.4+ environment and encountered a deprecation warning when using the CheckoutStream class.
The exact warning is:
PHP Deprecated: Creation of dynamic property Obs\Internal\Common\CheckoutStream::$stream is deprecated in /home/wp-content/plugins/dreams-huawei-obs-uploader/huaweicloud-sdk-php-obs/Obs/Internal/Common/CheckoutStream.php on line 31
Even though the $stream property is explicitly declared in the CheckoutStream class, the warning is being triggered. I suspect it might be related to how the $stream property is accessed or modified via the StreamDecoratorTrait from the GuzzleHttp\Psr7 package. It could be that the property is being accessed or modified in a way that's deprecated in PHP 7.4+.
Could you please investigate this issue and provide a fix or workaround? This deprecation warning could turn into a breaking change in future versions of PHP, and it's important for us to keep our environment up-to-date with the latest PHP version for security and performance reasons.
Thank you in advance for your time and help!

标题: 在 PHP 7.4+ 中因动态属性创建而出现弃用警告
正文:
您好，
我目前在 PHP 7.4+ 环境中使用 huaweicloud-sdk-php-obs SDK，并在使用 CheckoutStream 类时遇到了一个弃用警告。
准确的警告是：
PHP 已弃用：在 /home/wp-content/plugins/dreams-huawei-obs-uploader/huaweicloud-sdk-php-obs/Obs/Internal/Common/CheckoutStream.php 的第 31 行，创建动态属性 Obs\Internal\Common\CheckoutStream::$stream 已被弃用。
尽管 $stream 属性在 CheckoutStream 类中明确声明了，但是仍然触发了警告。我怀疑这可能与 $stream 属性通过 GuzzleHttp\Psr7 包中的 StreamDecoratorTrait 被访问或修改的方式有关。可能是以一种在 PHP 7.4+ 中已被弃用的方式访问或修改了属性。
您能否请调查此问题并提供解决方案或解决方法？这个弃用警告可能在未来的 PHP 版本中变成一个破坏性的变化，而我们需要保持我们的环境与最新的 PHP 版本同步，以保证安全性和性能。
提前感谢您的时间和帮助！

Hello, could you please provide the version numbers of php and sdk you are using?

Hello, could you please provide the version numbers of php and sdk you are using?
你好，麻烦提供您使用的php和sdk的版本号呢？

你好，我在php8.2.12,sdk3.23中也遇到了

Hello,
I am currently using the huaweicloud-sdk-php-obs SDK in a PHP 7.4+ environment and encountered a deprecation warning when using the CheckoutStream class.
The exact warning is:
PHP Deprecated: Creation of dynamic property Obs\Internal\Common\CheckoutStream::$stream is deprecated in /home/wp-content/plugins/dreams-huawei-obs-uploader/huaweicloud-sdk-php-obs/Obs/Internal/Common/CheckoutStream.php on line 31
Even though the $stream property is explicitly declared in the CheckoutStream class, the warning is being triggered. I suspect it might be related to how the $stream property is accessed or modified via the StreamDecoratorTrait from the GuzzleHttp\Psr7 package. It could be that the property is being accessed or modified in a way that's deprecated in PHP 7.4+.
Could you please investigate this issue and provide a fix or workaround? This deprecation warning could turn into a breaking change in future versions of PHP, and it's important for us to keep our environment up-to-date with the latest PHP version for security and performance reasons.
Thank you in advance for your time and help!
标题: 在 PHP 7.4+ 中因动态属性创建而出现弃用警告
正文:
您好，
我目前在 PHP 7.4+ 环境中使用 huaweicloud-sdk-php-obs SDK，并在使用 CheckoutStream 类时遇到了一个弃用警告。
准确的警告是：
PHP 已弃用：在 /home/wp-content/plugins/dreams-huawei-obs-uploader/huaweicloud-sdk-php-obs/Obs/Internal/Common/CheckoutStream.php 的第 31 行，创建动态属性 Obs\Internal\Common\CheckoutStream::$stream 已被弃用。
尽管 $stream 属性在 CheckoutStream 类中明确声明了，但是仍然触发了警告。我怀疑这可能与 $stream 属性通过 GuzzleHttp\Psr7 包中的 StreamDecoratorTrait 被访问或修改的方式有关。可能是以一种在 PHP 7.4+ 中已被弃用的方式访问或修改了属性。
您能否请调查此问题并提供解决方案或解决方法？这个弃用警告可能在未来的 PHP 版本中变成一个破坏性的变化，而我们需要保持我们的环境与最新的 PHP 版本同步，以保证安全性和性能。
提前感谢您的时间和帮助！
I have encountered the same situation as you. I am using PHP 8.2.13, and the following is my solution:


Switched Seattle_Lidar to blue cmap for clarity

Previously used a greyscale colormap, which was difficult to distinguish from the background:

Now it's clear where the data is:

Also added a colorbar where appropriate:

Probably need to add python-graphviz and graphviz to environment.yml, as they are required for the dask graph plotting.


upstream merge

PR description
This PR merges current hyperledger master branch onto chainsafe master.
Fixed Issue(s)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 16 committers have signed the CLA.:white_check_mark: edwardmack:x: jframe:x: joshuafernandes:x: matkt:x: shemnon:x: mark-terry:x: macfarla:x: abdelhamidbakhta:x: MadelineMurray:x: atoulme:x: RatanRSur:x: pinges:x: anthonybuckle:x: hmijail:x: lucassaldanha:x: faraggiYou have signed the CLA already but the status is still pending? Let us recheck it.

hmm. DCO doesn't like this.
@shemnon Do you envision this will be a problem?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 16 committers have signed the CLA.:white_check_mark: atoulme:white_check_mark: edwardmack:x: mark-terry:x: matkt:x: jframe:x: MadelineMurray:x: shemnon:x: pinges:x: macfarla:x: joshuafernandes:x: faraggi:x: abdelhamidbakhta:x: lucassaldanha:x: RatanRSur:x: hmijail:x: anthonybuckleYou have signed the CLA already but the status is still pending? Let us recheck it.


Fix for division by zero

Fix for division by zero error:

mu = (x - cumDistances[i]) / (cumDistances[i+1] - cumDistances[i])
ZeroDivisionError: division by zero

Thanks


Scroll bar style

Hello, It would be very helpful if you could implement the option to change the color and style of the scroll bar.

Scrollbar customization options:

Scrollbar - allows basic scrollbar customization such as thickness and radius. Should be applied to individual controls.
RawScrollbar - allows full scrollbar customization such as thickness, radius and colors. Should be applied to individual controls.
ScrollbarThemeData - allows almost the same level customization as RawScrollbar, but is configured for all controls.


Flogo Activity Json2xml

Flogo Activity for format conversion from JSON Object into XML using clbanning/mxj Go package.

Notice I need to do some cleanup


Docs app will fail when we go to 1.6

The docs app needs improving to ensure that changes to the "minor" version do not cause a catastrophic failure of the production docs app.

The trick is not to update the
"branchVersion": "^1.5.0-beta.2",

until the CDN is ready

Don't we need a similat issue for 1.7?

Well strictly the information is in the Asana task. But even better we should fix the build process so that this can't happen... i.e. when searching for a viable release to use in the docs we shouldn't bail out if we can't find a version that matches the version being built.

Created a new issue.


please include license files into crates.io archive

I see that licenses are in repo, but not included in sub-crates. ASL 2.0 requires license text to be presented along with sources

@alexcrichton Is there a way to do this with some Cargo.toml options? Or should I just copy the license files into each crate directory?

@BurntSushi package.license-file in Cargo.toml

@BurntSushi but it's only one file, what about second one?

@BurntSushi ah unfortunately I think you'd have to copy them around, I hadn't thought of this...


configure shibboleth auth for quimby

https://uit.stanford.edu/service/shibboleth/sp

https://github.com/apokalipto/devise_saml_authenticatable

I'll do a simple setup as talked about Friday, where the entirety of quimby-stage is just behind shibboleth.

PR 73 closed the code part of this, and shib is set up on sul-quimby-stage.  The new code isn't yet pushed out.

Closing the issue, code will be updated on stage at next general update there.


Latency base routing does not work

Describe the problem
latency base routing was suppose to be added with the following patch:
https://github.com/netbirdio/netbird/pull/1732
Unfortunately I believe the following if statement is wrong, but I am hesitant to open a PR to fix it since it will make the underlying wireguard connection unstable:
https://github.com/netbirdio/netbird/pull/1732/files#diff-67387c2b097eeb87387ab2575884677a2f9ee1c53b9e8674dcfa4936463c23f9R155
There also seems to be a few race conditions that could impact the route analyzes poorly.
In my testing sometimes the slower connection is picked because it was the first to connect. Other times the slower connection is picked because latency for one of the later connected peers is missing.
I will try and add logs, as I collect them.
To Reproduce
Steps to reproduce the behavior:
Fix if statement, set a more reasonable latency forgiveness number such as 0.015 (15 ms) rather than 100ms and watch what happens. You will eventually end up disconnected from all peers
Expected behavior
I expected the best route to be picked, unless it is a route that is only 100ms different as per the the latency base routing patch intended
Are you using NetBird Cloud?
Nope
NetBird version
modified version of 0.27.3
NetBird status -d output:
Peers detail:
 lon1.peers.n.com:
  NetBird IP: <IP_ADDRESS>
  Public key: DdiC7cXVeE409wdJO1bQjFQ8JYP52X+/HO46FtkTQSI=
  Status: Connecting
  -- detail --
  Connection type:
  Direct: false
  ICE candidate (Local/Remote): -/-
  ICE candidate endpoints (Local/Remote): -/-
  Last connection update: 2024-04-29 10:29:36
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/0 B
  Quantum resistance: false
  Routes: -
  Latency: 135.14475ms

 sfo2.peers.n.com:
  NetBird IP: <IP_ADDRESS>
  Public key: S3TburlUFqMPX3PLDlKhQnD/NLxq9B9YCzJ7mAZozh8=
  Status: Connecting
  -- detail --
  Connection type:
  Direct: false
  ICE candidate (Local/Remote): -/-
  ICE candidate endpoints (Local/Remote): -/-
  Last connection update: 2024-04-29 10:29:38
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/0 B
  Quantum resistance: false
  Routes: -
  Latency: 59.2695ms

 iad1.peers.n.com:
  NetBird IP: <IP_ADDRESS>
  Public key: MGJ+hGFni8uJSgVsF5AZI9GJCSEaOfJOUJ9joDxbhBI=
  Status: Connecting
  -- detail --
  Connection type:
  Direct: false
  ICE candidate (Local/Remote): -/-
  ICE candidate endpoints (Local/Remote): -/-
  Last connection update: 2024-04-29 10:29:39
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/0 B
  Quantum resistance: false
  Routes: -
  Latency: 69.943916ms

Daemon version: <IP_ADDRESS>9
CLI version: <IP_ADDRESS>9
Management: Connected to https://netbird.n.com:443
Signal: Connected to https://netbird.n.com:443
Relays:
  [stun:stunvpn-ec2.n.com:3478] is Available
  [turn:stunvpn-ec2.n.com:3478?transport=udp] is Unavailable, reason: allocate: all retransmissions failed for fGXwf/+OxEZN791L
Nameservers:
  [<IP_ADDRESS>:53, <IP_ADDRESS>:53, <IP_ADDRESS>:53] for [n.com, corp.n.com, dev.n.com] is Available
  [<IP_ADDRESS>:53, <IP_ADDRESS>:53, <IP_ADDRESS>:53] for [.] is Available
FQDN: hx7yg952h5-89.peers.n.com
NetBird IP: <IP_ADDRESS>/16
Interface type: Userspace
Quantum resistance: false
Routes: -
Peers count: 0/3 Connected

Additional context
I have explicitly disable turn on my coturn instance to force direct connections

HI @hurricanehrndz, I think you are right. The condition will keep the worse route. I updated the tests and will create a fix soon. As for the 100ms between the routes, I reduced that to 10ms. The idea was to avoid frequently alternating routes if their latency is similar. 10ms should be enough.

There is a race condition if a peer just connected the latency might still be 0 if the route selection happens before the first update. However, this should not be an issue as we will recalculate the routes once we receive a new latency. In the future we might need to reduce the frequency at which the latency is updated as in bigger networks this could cause permanent recalculation and therefore wasted resources.
If you see other race conditions please let me know.

Hello @hurricanehrndz can you share the full masked logs and the output from netbird status -d when all routing peers are connected?

I can try to catch it, it does disconnect quickly

Ok, in that case, can you share logs after 2 reconnections?

@mlsmaycon maybe we should close this issue and I will open a new one specifically scoped ICE candidates going to a disconnect state without recovery

Ok, thanks @hurricanehrndz

@mlsmaycon I found the other bugs that stop this from working on userspace wireguard interfaces, I will open PRs that should be merged before this does

Thanks, @hurricanehrndz;
Please let me know if you have any questions about the bugs you've found before opening the PRs.
BTW, we just merged #1903.

Awesome not a big deal, new release should be avoided till fixes are merged. I did document one of the bugs in the self-hosted channel.

Let me open a new issue


Protocol 244

Protocol 244 fails when entering in that protocol only, when leaving the parameter open it does not search for anything above protocol 223.
::::::::rtl_433 running output::::::::
rtl_433 version v3.18.0_rc2-146-g3edb93059ec branch master at<PHONE_NUMBER>10 inputs file rtl_tcp RTL-SDR with TLS
Use -h for usage help and see https://triq.org/ for documentation.
Trying conf file at "rtl_433.conf"...
Trying conf file at "/root/.config/rtl_433/rtl_433.conf"...
Trying conf file at "/usr/local/etc/rtl_433/rtl_433.conf"...
Trying conf file at "/etc/rtl_433/rtl_433.conf"...
New defaults active, use "-Y classic -s 250k" for the old defaults!
Publishing MQTT data to IPADDRESS port PORT
Publishing device info to MQTT topic "rtl_433[/model][/id][/channel:A]".
Publishing events info to MQTT topic "rtl_433/events".
Publishing states info to MQTT topic "rtl_433/states".
Registered 191 out of 223 device decoding protocols [ 1-4 8 11-12 15-17 19-23 25-26 29-36 38-60 63 67-71 73-100 102-105 108-116 119 121 124-128 130-149 151-161 163-168 170-175 177-197 199 201-215 217-223 ]
Opening file: 244 failed!
INFO:Started

I second this! im trying to use protocol 228 at its not there. How can we get this updated?

That should be available with the new update.

I had to roll that update back. Seems something has changed upstream that might be causing issues...


Add patch for long inchis

Fixes #164
Changes made in this Pull Request:

This patches NAGL to fail if inchis can't be generated.

PR Checklist

[ ] Tests?
[ ] Docs?
[ ] CHANGELOG updated?
[ ] Issue raised/referenced?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.25%. Comparing base (92d3302) to head (8caafc2).

Additional details and impacted files


fix: Fix emulator tests running on Grpc.Net.Client on .NET Core 3.1

We need to document this as something that users will need to do
when using the emulator.

Could we automatically add this in the library when we detect the emulator, or even if we detect an insecure connection and are on .netcore3.1? Else we should document this somewhere.

I prefer documentation over doing this implicitly - it's an application-wide setting which could have unexpected consequences - best to make the code explicit in user-space IMO.


[PoE2] no option to change from divine currency to exalt in price check

there is no option to change from div to exalt currency

Related #29, different enough though that I'm fine keeping as an issue

The specifically described one should be working so will be in next release


make Team explorer pageable

Reticketed from #3704.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Moving from the Pivot milestone to a new Optimize Homepage project.

Done! https://github.com/gratipay/gratipay.com/pull/4481


sort-prop-types fix to account for comments

I know comments on prop types are not in favour here, but for those who do have them, would it be acceptable to support sorting comments together with their prop types? i.e. currently the rule would fix
{
  /** z */
  z: PropTypes.string,
  /** a */
  a: PropTypes.any
}

to
propTypes: {
  /** z */
  a: PropTypes.any,
  /** a */
  z: PropTypes.string
}

How would you determine whether comments attach to the thing before, or the thing after?

Hmm... can you give an example where the comment goes after the thing you're commenting on? I'm having a difficulty coming up with a real use case.
AST-wise, there is a leadingComments property on the node that contains the comment before the node.

propTypes: {
  baz: PropTypes.any,
  foo: PropTypes.any,
  // ^ this is a foo, but the others don't need explanation
  bar: PropTypes.any,
}

Ok. Haven't really seen code like that. But if it's something people would do in your experience (as opposed to putting this is a foo above the foo), then yeah.

However, I’d say the current behavior is a bug, so your plan is probably a strict improvement.
Perhaps a plugin setting, that defaults to “above”, that determines comment attachment?

comments: “above” | “below”

(At plugin level tho, not rule)

Why? Are there other rules that would use it?

Any rule that moves code around :-) I’ve found over time that many rule configs belong instead as settings, and it’s easier to plan ahead.

I'm able to use sourceCode.getCommentsBefore(node) to process comments when attachment is "above". But finding this tricky to implement for the "below" attachment.
propTypes: {
  foo: PropTypes.any,
  // ^ this is a foo, but the others don't need explanation
  bar: PropTypes.any
}

If node is the entire foo property, then the comment will not be available in sourceCode.getCommentsAfter(node) because it's after the comma. So I need to either get down to the token level functions, or try using getCommentsBefore on the property that goes next (in this case, bar).
Also, here
propTypes: {
  foo: PropTypes.any, // <- this is a foo, but the others don't need explanation
  bar: PropTypes.any
}

the comment needs to be attached to foo as well (whether "above" or "below"), but it only differs from the previous example in a new line I think.
I'll continue working on this and see if I can make it work. We could use this rule internally.

Has there been any progress on this? FWIW the sort-keys-fix eslint rule doesn't properly deal with comments after the node either

jsx-sort-props got a fix for this in #3358; perhaps someone could handle it the same way in sort-prop-types? (cc @ROSSROSALES)

@ljharb Thanks for pinging me! I can try and take a look at it. I also noticed in the lib/rules/sort-prop-types.js file, all the invalid test cases are commented out https://github.com/jsx-eslint/eslint-plugin-react/blob/210865e9a74eb04ff339d85957df8f28531f78da/tests/lib/rules/sort-prop-types.js#L489
Currently when running test cases, it passes. However, once I comment them back in, test cases don't pass.
I am going to try and read into the history of the code, but if you had any insight please let me know! :thumbsup:

nah that sounds like it’s probably an oversight. It’d be great to get a PR that uncomments everything passing; and then a second PR that uncomments the rest and fixes the bugs :-)

@ljharb
I think we can close this issue now since #3471 fixes this.


download historical reports for a node from ui (client runs + compliance)

User Story
We recently did some work to add an endpoint for downloading historical reports for a single node (https://github.com/chef/automate/pull/1832). This work is complete on the client runs side of things, and will be getting worked on soon for the compliance nodes (https://github.com/chef/automate/issues/1765).
We'd like to give users a way to download these reports from the ui if possible.
looking for input from ux on this
Definition of Done
A way (button, menu, something) to download historical reports for a node.
Please note this download will respect all currently applied filters.

client runs has API and UI functionality for this; compliance has API but doesn't have it in the ui
need to make a UI card for the compliance part


Make limited functionality branch

Moving jobs from Civis to GCP, use the test branch to run a simpler notebook and write that as HTML.

@angelarafiles-lacityorg: Here's the new branch test.
Specifically, this is the script to run: https://github.com/CityOfLosAngeles/covid19-indicators/blob/test/gcp/run-report.py. I set it so that you have to be in the same directory gcp to run the script successfully, just to keep everything in the gcp folder.  I guess I mean: cd /app/gcp, followed by python run-report.py.

Close via #72


[hotfix][cdc-connector][mysql] Expose row_kind metadata column for mysql cdc source.

We use 'row_kind' name instead of 'op' or 'op_type', the operation type is a concept of database and database only has 'update' type and hasn't 'update_before' and 'update_after' type.

@whhe Could you help review this PR？


Revert classpath ordering of distribution-loaded test framework classes

When running embedded integration tests with test distribution, the junit-platform-launcher jar which is loaded from the gradle distribution is different than the version we usually test against. This version is incompatible with older versions of junit-platform-commons and junit-platform-engine jars pulled in by the corresponding junit jupiter versions.
To resolve this, we reversed the ordering of distribution loaded test framework jars to ensure our versions of these junit-platform-launcher dependencies came first on the classpath. This turned out to break the newest version of junit jupiter, which we do not test against, leading to a regression.
This reverses the order and ignores the embedded tests which break when testing against older versions of junit jupiter.

Fixes #24429

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you.


Implement presence & stats packets

This pr introduces packet 6 (presence) and packet 5 (stats), and sends them at login. There are still a few fields I'm unsure of, but we'll get there lol
Note for hosters: you will get an error saying "unable to recreate image from data" at login if you don't have an avatar server (http://hexis.dienay.net/a/id).

I've changed up the player presence & stats a bit, what do you think?

I am thinking of renaming the presence to Info, because player.Info.Id feels better, but I am not sure if that actually makes sense.

Nothing in the game refers to it as presence, I just named it that because osu! does something similar.
We could rename it to Info, but it's up to you.
Actually, I think the game does call it PlayerInfo aswell

Let's see if I can come up with something..

I think that works.

Do you have a theory on what the Unknown stuff could be?

0 clue
Ghidra sets a local variable equal to it and then seems to do nothing with it so I have 0 idea


add Mozilla Firefox support

Error in firefox:
h3::Error { code: H3_STREAM_CREATION_ERROR, reason: "Stream closed before type received" }

seems like if i comment either of these lines (Client side), it avoid the error: (but streams don't work)
writer.release_lock();
JsFuture::from(stream.close()).await.unwrap();

OR
I can comment out BOTH of these lines in the server, and avoid the error:
session.accept_uni() => ...
session.accept_bi() => ...

so basically streams has some issues.
Datagrams seem to work fine.

@ten3roberts ^^ what do you think? any clues?

I feel that we need an echo test for your sec-http3 webtransport implementation.
I tested my client code in mozilla with a public webtransport echo test and it works great:
https://security-union.github.io/yew-webtransport/

@cybersoulK can you test my echo client against your backend?

To add some valuable information from my testing:
Datagrams work fine. Uni streams Server->Client works perfect.
The issue:
When client sends uni streams to the server. the first several streams are successful. And then there is an error:
my logs:
Success: JsFuture::from(uni_stream) [client.js:1304:17](https://localhost/client.js)

Error: JsFuture::from(uni_stream) failed: JsValue(InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable

error:
) 2 [client.js:1295:17](https://localhost/client.js)
Uncaught (in promise) TypeError: getObject(...) is undefined

so there is something external affecting it.

I feel that we need an echo test for your sec-http3 webtransport implementation.
I tested my client code in mozilla with a public webtransport echo test and it works great:
https://security-union.github.io/yew-webtransport/

@darioalessandro
when i connect the echo server to my backend:
16:34:36.191: Connection lost (JsValue(Object({"closeCode":0,"reason":""})))
16:34:36.188: Sending: "awdawdawdwad" using UnidirectionalStream
16:34:34.191: Sending: "awdawdawdwad" using Datagram
16:34:33.903: Sending: "awdawdawdwad" using Datagram
16:34:33.597: Sending: "awdawdawdwad" using Datagram
16:34:33.129: Sending: "awdawdawdwad" using Datagram
16:34:30.055: Sending: "awdawdawdwad" using BidirectionalStream
16:34:28.508: Sending: "awdawdawdwad" using BidirectionalStream
16:34:27.917: Sending: "awdawdawdwad" using BidirectionalStream


clamtk: wrap with wrapGAppsHook

Description of changes
This patch fixes crashing due to missing icon files with wrapGAppsHook and pass extra makeWrapper arguments through gappsWrapperArgs.
ClamTk is known to crash when the icon files are not presented. As an application that uses the Gtk widget, it expects a bunch of environment variables to get various resources, including icons. This is exactly what wrapGAppsHook is made for.
Fixes #268203
Cc: @chewblacka

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

P.s. Please consider adding yourself as a maintainer for this package. By the looks of it you can do at least as good a job as I can.

Thanks for your encouragement!


Extra propagated Kafka Header converted to byte[] value

Hi! A while ago I posted https://github.com/openzipkin/brave/issues/783 where extra propagated headers with Apache Kafka were not available for use in something like:
    @KafkaListener(topics = "demo-topic2", groupId = "demo-group2")
    public void listen(@Header("corporate_trace_id") String corporateTraceId){ ... }

This was thankfully resolved and proven to work when unpacking Kafka headers; as demonstrated here: https://github.com/timtebeek/sleuth-kafkalistener/blob/master/src/test/java/com/github/timtebeek/sleuth/kafkalistener/TracingKafkaListenerTest.java#L77
However, when adding a web controller before the kafka send (mostly because I'm unsure how else to have Brave adopt my header value in a test), my Kafka header value is suddenly converted to a String containing a list of number, comma separated, that together make up the byte[] that corresponds to my header value. So abc becomes 65,66,67.
Demonstrated here: https://github.com/timtebeek/sleuth-kafkalistener/commit/70f79de5dd9f26c9c65934bb9d8bd56716d34704
Sorry for the possibly confusing test setup; this matches my actual use and demonstrates the issue; I'm unsure how to create a fully minimal test that replicates the same.
Can you have a look and possibly direct me to a workaround/fix?

spring-kafka is a layer above kafka, which brave instruments. At kafka's layer of abstraction, there are only byte array values. So, you would expect to always see byte arrays.
spring-kafka is a variant of spring-messaging which allows users to configure KafkaHeaderMapper which can convert byte arrays to something else. In your demo, this type ends up as DefaultKafkaHeaderMapper (invoked by MessagingMessageConverter.. both in spring-kafka), which has no special handling for the key "corporate_trace_id".
I don't know why that's the case, but in any rate it isn't something the kafka client layer which is the only thing defined in brave can affect. You might want to ask spring-kafka support for more advice.

In case anyone stumbles upon this in the future; It's been fixed in Spring Kafka 2.2:
https://github.com/spring-projects/spring-kafka/commit/214316839b2e309151094301016e7fd66d2c08c4

Just to close this out...
@timtebeek  when you previously set the header yourself...
    public void testHeadersNotStripped() throws Exception {
        String corporateTraceId = UUID.randomUUID().toString();
        Message<String> message = MessageBuilder
                .withPayload("bar")
                .setHeader(KafkaHeaders.TOPIC, Constants.TOPIC2)
                .setHeader(CORPORATE_TRACE_ID, corporateTraceId)
                .build();
        template.send(message);
        await().untilAsserted(() -> assertThat(listener.getMessageTraces().get("bar")).isNotNull());
        TraceDiagnostics traceDiagnostics = listener.getMessageTraces().get("bar");
        assertThat(traceDiagnostics.getCorporateTraceId()).isEqualTo(corporateTraceId);
    }

The template uses a message converter, and a DefaultKafkaHeaderMapper to map the headers. This mapper converts all the headers to JSON; it also adds an additional header spring_json_header_types which is a (JSON) map of header names to header types. On the receiving side, the headers are converted back to their original types. Any headers that don't appear in the name:type map are left as byte[]. Hence the change in behavior you saw. The 2.2 version performs a conversion when it sees the @Header parameter is of type String.

nice loopback on this folks! well done


psi-plus: init at 0.16.572.639

Motivation for this change
Psi+ is a great Jabber client, successor of Psi.
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I get a build error, when compiling this package:
Scanning dependencies of target whiteboarding
[ 24%] Building CXX object src/whiteboarding/CMakeFiles/whiteboarding.dir/moc_wbdlg.cpp.o
In file included from /tmp/nix-build-psi-plus-0.16.572.639.drv-0/psi-plus-snapshots-0.16.572.639-src/src/psiaccount.h:39:0,
                 from /tmp/nix-build-psi-plus-0.16.572.639.drv-0/psi-plus-snapshots-0.16.572.639-src/build/src/whiteboarding/../../../src/whiteboarding/../sxe/sxesession.h:33,
                 from /tmp/nix-build-psi-plus-0.16.572.639.drv-0/psi-plus-snapshots-0.16.572.639-src/build/src/whiteboarding/../../../src/whiteboarding/wbwidget.h:25,
                 from /tmp/nix-build-psi-plus-0.16.572.639.drv-0/psi-plus-snapshots-0.16.572.639-src/build/src/whiteboarding/../../../src/whiteboarding/wbdlg.h:42,
                 from /tmp/nix-build-psi-plus-0.16.572.639.drv-0/psi-plus-snapshots-0.16.572.639-src/build/src/whiteboarding/moc_wbdlg.cpp:9:
/tmp/nix-build-psi-plus-0.16.572.639.drv-0/psi-plus-snapshots-0.16.572.639-src/src/mucjoindlg.h:26:24: fatal error: ui_mucjoin.h: No such file or directory
compilation terminated.
make[2]: *** [src/whiteboarding/CMakeFiles/whiteboarding.dir/build.make:83: src/whiteboarding/CMakeFiles/whiteboarding.dir/moc_wbdlg.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1265: src/whiteboarding/CMakeFiles/whiteboarding.dir/all] Error 2
make: *** [Makefile:128: all] Error 2

It would help if you could post the complete build log. Mine is at https://gist.github.com/orivej/b7e783378bd44f2b5d72271c0a4c9837

@Mic92 Travis build on amd64 has passed, and I have not seen anything like your error while packaging psi-plus, and I have been building and on a multicore server so it is not likely to be an issue with parallelized compilation. Can you give more details? This may have been not the first error in your build log.

@orivej if you rebase it against master:
$ git fetch origin master
$ git rebase --onto c3c69535aa9f18f611950655d2e8ffc82521943d HEAD~3 HEAD

You hopefully get the following build error:
https://dl.thalheim.io/TeqOuLNtYDwsHKxk-ry9FA/build.log

It was an issue with parallel building. It has been fixed upstream, and I updated package version in pull request.

I wonder if this version still crashes when connecting to servers with untrusted certificates…

For me it does not, let me know if you see a crash.

right now Qt 5.8 cannot be built…

#24036 fixes Qt build


Kubeless topic command don't work with custom Kafka

Is this a BUG REPORT or FEATURE REQUEST?:
It's a bug.
What happened:
Scenario:
I have existing Kafka+Zookeeper cluster (installed by this Helm chart) and i configured Kubeless Kafka Trigger to work this cluster. Trigger works as expected when i publish to topic by kafka-topics.sh inside Kafka pod. But when i use command from my PC kubeless topic list --kafka-namespace kafka, i got following error:
websocket.Dial wss://<IP_ADDRESS>:8443/api/v1/namespaces/kafka/pods/kafka-0/exec?command=bash&command=%2Fopt%2Fbitnami%2Fkafka%2Fbin%2Fkafka-topics.sh&command=--zookeeper&command=zookeeper.kafka%3A2181&command=--list&container=broker&stderr=true&stdout=true: bad status

What you expected to happen:
I expect to see list of Kafka topics.
Anything else we need to know?:
Same result for kubeless topic create/delete/publish.
Environment:

Kubernetes version (use kubectl version): Client Version: v1.13.0, Server Version: v1.13.3
Kubeless version (use kubeless version): v1.0.2
Cloud provider or physical cluster: laptop with Windows 10, VirtualBox 6.0, Minikube v0.34.1

My bad, I accidentally submit issue to bad repository :(


Add a timeout in RefreshContainers to avoid hanging connections

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "container_list_timeout" git@github.com:wsong/swarm.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Ping @jlhawn @alexmavr for review

Ping @nishanttotla


Updated widget after click button

How to create a circle button that refreshes the widget content when clicked?  without opening the application.

https://saleksovski.github.io/react-native-android-widget/docs/handling-clicks

Do you plan to implement this library for IOS and Expo dev?

No plans to support iOS for now.
Expo is supported, see the docs https://saleksovski.github.io/react-native-android-widget/docs


Helm-Chart: Increase timeouts of probes of webhook-deployment

Describe the bug:

The liveness- and readinessProbe of the webhook-deployment uses the (default) timeout of 1s. This seems to be too short and the pod gets restarted very often.

NAME                                       READY   STATUS    RESTARTS   AGE   IP
cert-manager-webhook-5677b9b48d-jdz5l      1/1     Running   108        21d   <IP_ADDRESS>

Events:
  Type     Reason     Age                     From             Message
  ----     ------     ----                    ----             -------
  Warning  Unhealthy  47m (x71 over 6h8m)     kubelet, server  Liveness probe failed: Get http://<IP_ADDRESS>:6080/livez: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy  4m25s (x220 over 6h8m)  kubelet, server  Readiness probe failed: Get http://<IP_ADDRESS>:6080/healthz: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

Expected behaviour:
The webhook-pod is only restarted if needed :wink:
Steps to reproduce the bug:
No special steps
Anything else we need to know?:
I can do a PR if desired to increase the timeout.
Environment details::

Kubernetes version (e.g. v1.10.2): 1.18.8
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): bare-metal
cert-manager version (e.g. v0.4.0): 0.16.0
Install method (e.g. helm or static manifests): helm

/kind bug

Hi @ckotzbauer, you should be able to do a PR to extend the helm chart to offer configurable values for the probe timeouts. You can probably crib from another helm chart with similar probe configuration, e.g. haproxy-ingress
That said, 1s is a long time for cluster-internal requests. In my tests this health probe is ~10ms. So you might have something else going on.
NAME                                       READY   STATUS    RESTARTS   AGE
cert-manager-webhook-66976469d7-hhhp8      1/1     Running   0          50d

# time curl -i <IP_ADDRESS>:6080/healthz
HTTP/1.1 200 OK
Date: Sun, 16 Aug 2020 18:02:24 GMT
Content-Length: 0

real    0m0.010s
user    0m0.004s
sys     0m0.004s

Agreed with @whereisaaron here, a PR to allow to modify it is welcome!
Might be worth investigating why it takes a second as this will affect the speed of cert-manager and all deployments.
/help
/priority backlog
/area deploy
/remove-kind bug
/kind feature

Great, thanks @whereisaaron @meyskens for your feedback! I will open a PR for this.


publish kolena document to production s3

Linked issue(s):
What change does this PR introduce and why?
Please check if the PR fulfills these requirements

[ ] Include reference to internal ticket and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Relevant tests for the changes have been added
[ ] Relevant docs have been added / updated

Looks harmless enough! Once we set up DNS for docs.kolena.io to point to S3, let's remove the GitHub pages publishing stuff from this repo in a follow-up.

yes, will do. The switch might cause a brief outage to our docs


Size of PNG too big after resize

Hi,
I've tried to resize PNG image to the smaller size (with resizeToWidth) but the resulting image was extremely big. When I've used image compress tool (ImageOptim) it was able to remove 99% of the image size so there must be too much bloating information in the image.

You should use quality parameter for PNG compression. https://github.com/eventviva/php-image-resize#quality It does not apply compression by default.


Scroll wheel no longer works correctly in OpenConsole

Windows Terminal version
Commit ed27737233714dea77877624d1beeb49e2ccd36e
Windows build number
10.0.19044.1706
Other Software
No response
Steps to reproduce

Checkout commit ed27737233714dea77877624d1beeb49e2ccd36e or later.
Build and run OpenConsole.
Perform a few directory listings or something to get a couple of pages into the buffer.
Use the scroll wheel to scroll back in the buffer.
Use the scroll wheel to scroll forward again.

Expected Behavior
Scrolling should work correctly in both directions.
Actual Behavior
When I attempt to scroll forward, the viewport immediately jumps back to the start of the buffer.
I did a git bisect, and it looks like this problem may have been introduced by commit ed27737233714dea77877624d1beeb49e2ccd36e.
/cc @lhecker

I'll check this out as soon as I can. Quite curious that this happens because I did notice this exact bug while I was developing the PR and fixed it.
It can occur when you aren't careful when extracting the wheel delta, as it's stored as a signed 16-bit integer in the high word of the wParam: https://github.com/microsoft/terminal/blob/4e20a8631cbb5b20defe549a0e75bc7719969bee/src/interactivity/win32/windowproc.cpp#L653
Initially I had replaced all (short) with (til::CoordType) which caused large jumps during scrolling. This appears to be the exact same bug? Scrolling down (e.g. wheel delta int16_t(-3)) gets passed around as a very large but equivalent positive number (uint16_t(65532)). And now with everything as int32_t this doesn't work anymore.

Building 4e20a86 wheel scrolling works as expected:
https://user-images.githubusercontent.com/3933920/172752195-bd0e093e-f26c-470c-821b-4f9f45e303e6.mp4
200 one-line git log entries were used to fill the buffer. Does it need more data in the buffer to trigger the bug?

FYI, I think the issue might be here:
https://github.com/microsoft/terminal/blob/ed27737233714dea77877624d1beeb49e2ccd36e/src/host/scrolling.cpp#L145
We're dividing a short by an unsigned long, which I think is treated as an unsigned division, and that results in a massive positive delta. Previously the ulActualDelta was cast to short here, so it was a signed division.


Cocoon CI is broken due to recent grpc: 3.1.0 release

This also caused cocoon deployment failure:

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8799111100632269761/+/u/auto_submit/stdout
[31mFailed to load "test/requests/update_revert_issues_test.dart":
  ../../.pub-cache/hosted/pub.dev/appengine-0.13.3/lib/src/appengine_internal.dart:292:7: Error: The non-abstract class '_ClientChannelWithClientId' is missing implementations for these members:
   - ClientChannelBase.onConnectionStateChanged
  Try to either
   - provide an implementation,
   - inherit an implementation from a superclass or mixin,
   - mark the class as abstract, or
   - provide a 'noSuchMethod' implementation.

  class _ClientChannelWithClientId implements grpc.ClientChannel {
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
  ../../.pub-cache/hosted/pub.dev/grpc-3.1.0/lib/src/client/channel.dart:118:31: Context: 'ClientChannelBase.onConnectionStateChanged' is defined here.
    Stream<ConnectionState> get onConnectionStateChanged =>
                                ^^^^^^^^^^^^^^^^^^^^^^^^

Created appengine bug: https://github.com/dart-lang/appengine/issues/154 to track.

Upstream fix: https://github.com/dart-lang/appengine/pull/155


CI: Add a GitHub Actions matrix

In order to have a next CI system when Travis CI stops giving out free CI minutes.

<Rack::Timeout::RequestTimeoutError> expected but was
<ArgumentError(<wrong number of arguments (given 2, expected 1)>)
/home/runner/work/rack-timeout/rack-timeout/lib/rack/timeout/core.rb:69:in `initialize'
/home/runner/work/rack-timeout/rack-timeout/vendor/bundle/ruby/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:158:in `new'

This smells like a ruby2_keywords thing. Probably not hard to fix.

<Rack::Timeout::RequestTimeoutError> expected but was
<ArgumentError(<wrong number of arguments (given 2, expected 1)>)
/home/runner/work/rack-timeout/rack-timeout/lib/rack/timeout/core.rb:69:in `initialize'
/home/runner/work/rack-timeout/rack-timeout/vendor/bundle/ruby/3.0.0/gems/rack-2.2.3/lib/rack/builder.rb:158:in `new'

This smells like a ruby2_keywords thing. Probably not hard to fix.

I triaged pull requests backwards and already merged a github-actions PR even though it came later. So sorry :(
The good news is that we have CI working on github actions now!

I created #182 without noticing this PR, sorry. :bow:
@olleolleolle I always appreciate your great contributions!


CD Pipeline - Deploy to Production

User Story - Business Need
This ticket is the final stage to completing our CD Pipeline according to this diagram.

[x] Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)
As VA Notify        <!---   describe the affected user  --->
I want  Continually deploy production-ready code  <!---   describe the need           --->
So that  application upgrades and features are made available to clients as soon as possible, and engineer hours managing this process are significantly reduced   <!---   describe the outcome]       --->
Additional Info and Resources

cd-pipeline.yml already has various stops for QA; This is the final run merge and run through of this pipeline.
Engineering Checklist

[x] Add to the cd-pipeline.yml, after the final check of QA for the prod-deploy environment, a workflow_call to dev_deploy.yml for the prod environment.
[ ] Run through workflow with QA after merging this PR, ensuring all looks correct.

Acceptance Criteria

After QA approval, Github Actions deploys the new version to production and runs the Prod smoke test

QA Considerations

[ ] work with the dev to ensure that the work done in this ticket meets the necessary requirements

Out of Scope

Publishing the drafted release notes is in #1721

Hey team! Please add your planning poker estimate with Zenhub @cris-oddball @EvanParish @k-macmillan @kalbfled @ldraney @MackHalliday @mchlwellman

I've contacted Cris and we will be syncing on this after standup.

Things are looking good, but I would like to continue work on Monday after I figure out my E-Pass stuff today.  This is a high priority because it may expire Monday!
Also, we like to avoid deploying on Fridays. I've passed this by Cris and Kyle. I will wait until Monday morning to sync with Cris before creating a PR.
Here’s what I’ve accomplished on the ticket so far.
I got a working POC.
Here is the PR in demo api of the code I merged.
I also discovered the cd-pipeline wasn't passing the tag to deploy-release.yml, so I included the fix in the above PR and wrote out these notes about the fix.
I’ve also written out some steps for a smooth transition to the new pipeline, and tested it in my POC to make this release.

Epass looking good!  Getting back to this.

Had a sync with Cris and things look good!
We need to make sure in standup the team is okay with an out of cycle release, and to move forward with this process.
Then I'll open a draft PR!


making yes as default when regenerating token

It is simple to press two enters than typing y again. So, making y default would make it faster to generate otp.

merged

And now you have to press enter just once


[Blog] Performance improvements

[x] Little jank in HtmlView
[x] show no results when no post (in search)
[x] highlight search query in posts

Implemented


Reframing the goal of this starter

"docker-java" seems rather general, and the current README doesn't make the goal of this starter really clear.
Is this starter only about configuring a docker java client? In this case, renaming this starter to docker-client-spring-boot-starter could be a better fit.
Currently the starter only provides a single configuration property namespace and uses the client builder to create a couple of beans. Are there other opinions or features that this starter could offer to developers?

I renamed the project name to docker-api. Because both docker-java and docker-client are wrappers of the docker api.

The new name looks fine!
In a previous comment I said this starter should come with at least one compile dependency. Reading the README of this project, I don't see the difference between docker-java and docker-client.
I'm not really familiar with this library, so feel free to close this issue if you think this is the right choice here.

OK!
Both docker-java and docker-client really have many differences. I will add more about docker-java and docker-client so that users can chose the right choose for their projects.