SSL error: unexpected eof while reading (in )

the stream setup only a few minutes ,then the WS will be closed,what's the matter,help pls ,thanks.
DEBUG:root:closing ws connection
WARNING:root:WebSocket connection closed: connection was closed uncleanly ("SSL error: unexpected eof while reading (in )"), code: 1006, clean: False, reason: connection was closed uncleanly ("SSL error: unexpected eof while reading (in )")
root@bot-dev:/home/binance-futures-connector-python/examples/websocket/um_futures# python3 -V
Python 3.8.10
root@bot-dev:/home/binance-futures-connector-python/examples/websocket/um_futures# openssl version
OpenSSL 1.1.1f  31 Mar 2020 (Library: OpenSSL 1.1.1s  1 Nov 2022)

my_client.stop().....


Update README.md with 2FA

emojipacks supports two-factor authentication so the README should reflect that.

As the person who implemented 2FA, this PR pleases me. Thanks @aboutaaron !


GraphQL example is shipping unused code

Version<EMAIL_ADDRESS>binary version: 30a33bde5b1d9f79e0a48491749528da76002e24
Currently, Prisma2 is shipping with unused SDL first code which is not being used. Only index.js file is needed which is using GraphQL Nexus.

Reproduction:

Run prisma init
SQLite > JS > Select both photon and lift > GraphQL Server

Can you please retest this with the new init flow @pantharshit00 and apply the candidate label if it is still the case? Thanks.

I am no longer able to reproduce this.


Add tests for limits

We had a queue backup this morning because the builder would panic whenever a crate had limits set (https://github.com/rust-lang/docs.rs/pull/648, https://docs.rs/releases/queue). This adds tests so that doesn't happen again.
r? @kvrhdn

I should be able to look at this in the next couple of days @jyn514.

Good idea! I added a test for scale and noticed at the same time that it always rounded down. I changed it so now it rounds to the closest integer instead. I was also considering printing a float rounded to 1 decimal place, what do you think?

Yeah, makes sense! Having one digit after the decimal point provides a lot more precision. There is a significant difference between 1 GB and 1,5 GB. But at the same time, I find it difficult to reason about 1,2 hour. So it will be a bit of a trade off 😅

Implemented fractional precision up to 1 decimal point. I also displayed it as an integer if the decimal was 0 (2.0 -> 2).

But overall this looks neat :+1: I love Rust's format!!

Rust is indeed wonderful! Thanks for the review, I think the new precision will be helpful :)


Design logo/icon

If anyone feels creative, it would be nice to have some kind of logo/icon for the project!
The original version is a little - let's say - rudimentary ;)

Along these lines, we can also replace the gif in the readme!

Just updated the gif ✅

I was playing around with SDXL with "magnifying glasses" prompts and found some drafts to be quite interesting:

I really liked the last one.

Apparently SDXL really likes the circle, found it funny that it tried to melt a face, glasses and the magnifying glass with a baseball bat nose :D
Anyway, came up with a hand-drawn version in excalidraw. If anyone feels creative, feel free to iterate on this one or propose another one!

Excalidraw file here:
SemanticFinder.zip

I like the hand drawn one! Feel free to put it wherever you like for now and I might try to iterate on it

I like the new logo but it is hard to see on the pinned extension. It could use a light background (instead of a transparent one) or some other way of popping out.

Agree, will come up with something poppier tonight.

I've tried a few options. Maybe the middle one is best?

Not really sure, but seems to be more recognizable than before.

For now resolved - if anyone has further ideas, I'll reopen.


Hyundai Kona Electric 2019 - CAN Error

Describe the bug
Installed Openpilot on a new Comma Two that arrived yesterday.
Message onscreen is "CAN communication has failure"
How to reproduce or log data
Used a new install or openpilot.
Had followed instructions to get the latest from openpilot.comma.ai
Expected behavior
I think it should connect CAN communication
Device/Version information (please complete the following information):
*Device: [Comma Two]
*Version: [0.7.6-1]
*Car make/model [Hyundai Kona Electric 2019 with LFA and HDA  ]

Can you post a route where this happens? You can see your routes with https://my.comma.ai.

last week i tested kona ev 2019
use comma two
-- release2 can error
-> xx979xx HKG_community ver can error to
-> add elect_ems and hyundaican add kona_ev no error work done..~
https://github.com/xx979xx/openpilot/pull/127

I have a Hyundai Kona Electric 2019 SEL (no SCC) and get similiar results:

Original OP release2- Factory Reset, install openpilot.comma.ai, turn on community features, turn on car. Says: OP not available, buckle seat belt, Device Sensors not detected, CAN error. (fyi - Seat belt buckled) I even added elect_ems and added kona_ev to it but no help
-Installed HKG_community - looks like same fingerprint as original OP but won't detect and turn on OP like Original did. (this may be before the adds crwusiz did)
-In https://my.comma.ai/useradmin the release2 comes up as Hyundai Kona Electric 2019 but the HKG_community comes up as Mock

Sample route: 6d556f411feddcac|2020-06-25--18-50-23--0

I used the HKG_community build after the elect_ems commint @crwusiz talked about above and it still did not detect the car and leave dashcam mode and stayed in Mock.
Sample HKG_community route detected as Mock: 6d556f411feddcac|2020-06-29--04-16-27
Sample release2 route detected as Hyundai Kona EV and tried to engage OP but Seatbelt error, Sensor error, and CAN error: 6d556f411feddcac|2020-06-26--21-57-52

I used the HKG_community build after the elect_ems commint @crwusiz talked about above and it still did not detect the car and leave dashcam mode and stayed in Mock.
Sample HKG_community route detected as Mock: 6d556f411feddcac|2020-06-29--04-16-27
Sample release2 route detected as Hyundai Kona EV and tried to engage OP but Seatbelt error, Sensor error, and CAN error: 6d556f411feddcac|2020-06-26--21-57-52

i think..the reason....is (no SCC) -> radar signal not exist...

@swells-Kona @crwusiz Seems like the Kona EV uses a different message for the gas pedal like the Ioniq. Fixed in 83af35bf95e794f0968fc3a8e18333d96c786172
@davidew98 cars without SCC are currently not supported.

I used the HKG_community build after the elect_ems commint @crwusiz talked about above and it still did not detect the car and leave dashcam mode and stayed in Mock.
Sample HKG_community route detected as Mock: 6d556f411feddcac|2020-06-29--04-16-27
Sample release2 route detected as Hyundai Kona EV and tried to engage OP but Seatbelt error, Sensor error, and CAN error: 6d556f411feddcac|2020-06-26--21-57-52

i think..the reason....is (no SCC) -> radar signal not exist...

this does not explain why release2 detects my car and HKG does not.

@davidew98 This isn’t the place for discussion of community forks. For that discussion, try discord.comma.ai or the issues of the specific repository you’re running code from.


[Bug]: Current value won't populate when editing

What happened?
When using the field in an Edit form:

Selecting a value in the dropdown will correctly save the country code in the DB
After refreshing the page, the country field is back to "Select an option" while other fields correctly show value from DB
Same happen on View page

How to reproduce the bug
in App\Filament\Resources\MyResource:
use Parfaitementweb\FilamentCountryField\Forms\Components\Country;

//
public static function form(Form $form): Form
    {
        return $form
            ->schema([
                Country::make('Nationality')->searchable()->required(),
           ]);
    }

Package Version
2.1.0
PHP Version
8.2.18
Laravel Version
10.45.1
Which operating systems does with happen with?
Windows
Notes
No response

OK I solved my own issue, the field name should be lowercased
Country::make('**n**ationality')->searchable()->required(),


Goto next problem does not go in sequence in certain scenarios

ATTENTION ATTENTION: This is a BUG. Repeat this is a BUG. Do not label this a a feature request so your bot comes and auto closes it because it is not getting votes.
Repeat once again.....this is a BUG not a feature request.
Version: 1.51.1
Commit: e5a624b
Date: 2020-11-10T23:31:29.624Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-53-generic
I have observed a scenario where pressing F8 to go to next problem will take me back the first problem, instead of to the next problem.
The problems in my problems view can be summarized as follows. (number of files and issues within files is irrelevant).
File A
problem 1
problem 2
problem 3
File B
problem 1
problem 2
problem 3
File C
problem 1
problem 2
problem 3
-press F8 to go to problem A1.
-keep pressing F8 until you get to problem B3 (the last problem in a file that has problems in a file before it and problems in a file after it).
-fix the problem and save the file.
-press F8 again....
-it jumps to problem A1.
Expected Behaviour
-it should jump to problem C1.

Reopening the original issue - https://github.com/microsoft/vscode/issues/113257

Reopening the original issue - https://github.com/microsoft/vscode/issues/113257


Can't use LDAP auth when LDAP Server has objectClass attribute in lowercase

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Enable OpenLDAP Auth
Configure to a LDAP Server which the objectClass name is lowercase (objectclass), like below:

objectclass: top
objectclass: person
objectclass: inetOrgPerson
uid: f435
givenname: User

Result:
It doesn't find the inetOrgPerson objectClass and doesn't bind the user correctly.

It enables OpenLDAP Auth, but it can't find any user or group, so I can't add members in any cluster.

Other details that may be helpful:
After some troubleshoot, the problem seems to be in the function isType() in ldap_util.go, that searches for the specific attribute name "objectClass", so in this case will never find it because the name is objectclass (lowercase).
func IsType(search []*ldapv2.EntryAttribute, varType string) bool {
	for _, attrib := range search {
		if attrib.Name == "objectClass" {       <===================== here
			for _, val := range attrib.Values {
				if strings.EqualFold(val, varType) {
					logrus.Debugf("ldap IsType found object of type %s", varType)
					return true
				}
			}
		}
	}
	logrus.Debugf("ldap IsType failed to determine if object is type: %s", varType)
	return false
}

The change I made to solve this was to use the function strings.EqualFold to make it case insensitive:
func IsType(search []*ldapv2.EntryAttribute, varType string) bool {
	for _, attrib := range search {
		if strings.EqualFold(attrib.Name, "objectClass") {
			for _, val := range attrib.Values {
				if strings.EqualFold(val, varType) {
					logrus.Debugf("ldap IsType found object of type %s", varType)
					return true
				}
			}
		}
	}
	logrus.Debugf("ldap IsType failed to determine if object is type: %s", varType)
	return false
}

Also changed this isType implementation to use the new ldap.isType() function changed above so it can also be case insensitive.
After this changes are made, OpenLDAP auth works fine.

I have opened 3 PRs for this case:
rancher/rancher#26778
rancher/rancher#26952
rancher/rancher#26949
The same problem occurs if using others providers for LDAP, like FreeIPA, because the function isType() is common to them.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): Verified on versions 2.2.8, 2.3.5 and 2.4.5.
Installation option (single install/HA): Both single and HA

What LDAP server are you working with?

It's a IBM LDAP Server for z/OS Mainframe.

https://github.com/rancher/rancher/pull/26949

This has been fixed in 2.4, 2.5 and master lines.

Thanks @igorcezar for all the pull requests 😃

It was my pleasure to contribute! Thanks for accept it! 😄
Will this fix be in version 2.4.9?

@igorcezar No guarantees but it should be

I think we should test the fix with all ldap providers, that is Openldap, AD and Freeipa, since the IsType method is common to all

@bmdepesa It's working in v2.4-head and v2.5-head, for both OpenLdap and FreeIPA. 😄


Improvements for block comment

There should be no spaces by default inside the """.
Example: """Comments on a single line."""
If there's a text selection on multiple lines, the """ should be placed on separated lines above and below the selected lines.
Example:
"""
Comments on
multiple lines.
"""

I think that should be the default but it would be even better if you provide a setting to choose whether the starting quotes must be on a line by itself or not.
Example:
"""Comments on
multiple lines.
"""

And the "toggle block comment" should be improved to uncomment the whole block when we executed the command with the cursor anywhere inside the comment or having a selection inside the comment.
See PEP-257.
Practical examples (Django): single line and multiline.

@ppo we will discuss this when working on #10640. Additionally, we plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.
/ cc @luabud This is about how we handle multi-line comments (see #10640).

Thanks for the suggestion! We talked about it with the team and we have unfortunately decided we will not be moving forward with this idea. We think there isn't an enough widespread need for this to warrant the maintenance cost for the feature.


Separate router API into a module

[x] Remove dependency on WebExtension API
[x] Remove tab related functions

Closed by 3a33f2a733807f81ea18dba9b42087aac563aaa9


Run job splitter only on a reasonable amount of events/lumis

Fixes #7988
Changes how secondary tasks/steps create processing jobs. Instead of creating jobs as soon as files are available wmbs_sub_files_available, wait for enough files such that they can meet the job splitting arguments (amount of events or lumis).
In addition to that, check whether the (input) fileset is closed, in this case just proceed with the splitting no matter how many files/events/lumis are available (useful for the very last jobs to be created).
Also fixed a couple of issues with the EventAwareByWork splitting.

Another comment, I've just noticed this is not optimal because it guarantees we will have at least 1 job with a decent splitting, but it could be that for each decent job there will be one very short...
If this change is not enough, then we have to make (much?) more changes to the job splitting algos such that they consider only the lumi sections that are able to completely fill a job, leaving the remainder lumi sections for a future cycle. Still, a whole file has to either be fully splitted or not...

Before I start the real tests, I'd like to hear your thoughts @ericvaandering @ticoann @hufnagel

test this please

That's unfortunate... I've just found we have JobSplitting tests under

WMCore/JobSplitting, for DataStructs
WMCore/WMBS/JobSplitting, and for WMBS structs

working on that...

Tests are looking good and it improves the overall job splitting in 50%, at the very very least.
Reviews are most welcomed at this stage.

@ericvaandering I've just updated this patch and all your comments/concerns should've been taken care of. Thanks!

From my side, it's good to go.
Feel free to review and merge.

@amaltaro , do you still need a review from me ? I skimmed through the code but I don't have time to really go through it. What are the functional changes ?

Dirk, I have updated the PR description (1st comment).

Thanks, this make it clearer to me. Looking at the code, if I have a job splitter that is NOT using the newly added getFilesSortedByLocation method to discover it's input, it would not be affected by these changes, right ?
So for the Tier0, this only changes how we do the PromptReco job splitting ?

That's correct. It changes the behaviour only for LumiBased and EventAware* algos.

@ticoann can you review and merge it? Then we can run further integration tests, though I expect no issues :)


pressing Backspace while in Replace mode does not put back a character that had been replaced

What did you expect to happen?
pressing Backspace while in Replace mode puts back a character that had been replaced
What actually happened?
pressing Backspace while in Replace mode does not put back a character that had been replaced but only a space
Describe your attempts to resolve the issue
No response
Steps to reproduce
Open Emacs
To Insert mode
Type: Hello
To Replace mode
Go to beginning of the line
Type World
Press backspace 5 times
See empty (5 spaces) space, in VIM you get Hello.
System Information
pastebin.com/vy0TcGCf

I acn reproduce this in vanilla Emacs + evil. This is an upstream bug. Please report this upstream. I will keep this open until it is resolved there.


Image Compression not working

I had done below code:
include('../includes/tinify-php-master/lib/Tinify/Exception.php');
include('../includes/tinify-php-master/lib/Tinify/ResultMeta.php');
include('../includes/tinify-php-master/lib/Tinify/Result.php');
include('../includes/tinify-php-master/lib/Tinify/Source.php');
include('../includes/tinify-php-master/lib/Tinify/Client.php');
include('../includes/tinify-php-master/lib/Tinify.php');
\Tinify\setKey("API Key");
$source = \Tinify\fromFile($fromFile);
$source->toFile($uploadPath);
Above code gives me wrong output
The output is not compresses

Hi there!
What output do you get back? The original image or something
else?
Could it be that $fromFile and $uploadPath got mixed up? Would it
be possible for you to share your entire script? (Right now we
don't know what $fromFile and $uploadPath is which makes it a bit
tricky to investigate your issue).
Hope to hear from you soon!
Kind regards,
Simon Wahlstrom
tinify/tinify-php on July 12, 2017 at 11:45am wrote:
I had done below code:
include('../includes/tinify-php-master/lib/Tinify/Exception.php');
include('../includes/tinify-php-master/lib/Tinify/ResultMeta.php');
include('../includes/tinify-php-master/lib/Tinify/Result.php');
include('../includes/tinify-php-master/lib/Tinify/Source.php');
include('../includes/tinify-php-master/lib/Tinify/Client.php');
include('../includes/tinify-php-master/lib/Tinify.php');
\Tinify\setKey("API Key");
$source = \Tinify\fromFile($fromFile);
$source->toFile($uploadPath);
Above code gives me wrong output
The output is not compresses
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
( https://github.com/tinify/tinify-php/issues/16 ), or mute the
thread
( https://github.com/notifications/unsubscribe-auth/AVWuQGP35vMNoiVhkFqyRG9cr_yTvD9oks5sNJWfgaJpZM4OVYW6 )
.


[DOC] Add estimator overview table with capabilities

Reference Issues/PRs
Fixes #1242
What does this implement/fix? Explain your changes.
Add back the estimator overview table from 0.3, but add capabilities of individual estimators to the table.
When this is merged, i'll raise an issue for the sorting by columns / search function that I didn't manage to implement.

The trick is that it should be generated while building the docs, and I don't know if build_tools would be accessible while readthedocs builds. But I agree we should put it in a separate file, maybe create a folder/python script inside docs/ for script that generate content ?

Ok, a quick try on moving the script somewhere else made a mess, I'll keep it that way for now. I opened #1430 for individual estimators, and I'll create the issue for search/sort. So I guess we can close #1242 for now.


Translate guides/accessibility/page-template-considerations.md

Closes #13

@BlueCutOfficial , misclick on a button, it updated your PR with a merge commit.
My bad.


Teach ratbag-command the "ratchet mode switch" special action name

This doesn't effect functionality (since assigning this action to buttons seems to do nothing on the MX Master at present), but the ratbag-command program should at least know the action's name.

the logitech page seems to call this button the "mode shift" button. maybe we should stick with that nomenclature?
http://support.logitech.com/en_nz/article/Configure-the-MX-Master-mouse-with-Logitech-Options?product=a0qi0000006Njj9AAC

I am not a big fan of a simple "mode shift". In the MX Master case, it's rather obvious what it is, but I am not sure everybody who don't own this particular mouse will understand that this is a reserved one for the ratchet feature. Plus on the drawing on the page you linked, the button is called "manual mode switch".
So I'd say if we want to expose it, stick to "ratchet mode switch", as in the PR.

oki, in that case - merged! thanks


Repo sync for protected CLA branch

The pull request is created from main637924859040680312 to main to fix git push error for protected CLA branch

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


some error on bundle

from D:/Ruby23/lib/ruby/gems/2.3.0/gems/bundler-1.17.2/lib/bundler/dsl.rb:47:in eval_gemfile' 	from D:/Ruby23/lib/ruby/gems/2.3.0/gems/bundler-1.17.2/lib/bundler/dsl.rb:12:in evaluate'
from D:/Ruby23/lib/ruby/gems/2.3.0/gems/bundler-1.17.2/lib/bundler/definition.rb:34:in build' 	from D:/Ruby23/lib/ruby/gems/2.3.0/gems/bundler-1.17.2/lib/bundler.rb:135:in definition'
from D:/Ruby23/lib/ruby/gems/2.3.0/gems/bundler-1.17.2/lib/bundler.rb:101:in setup' 	from D:/Ruby23/lib/ruby/gems/2.3.0/gems/bundler-1.17.2/lib/bundler/setup.rb:20:in <top (required)>'
from D:/Ruby23/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require' 	from D:/Ruby23/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require'

This does not seem like the full error, can you please attach the full stack trace and the output of bundle env.

thank you. issue is sloved


The bot answer wrong when the question have "NOT" in the phrase

Example
Which of these country is NOT in Europe?
A. Spain
B. France
C. India
The correct answer is C, but the bot will definitely say A or B.
The bot need to deliver the answer that has the lowest score.

My example is also for the other negatives (don't didn't etc..etc..)

The bot does reverse answer scores if a reverse word is detected. From my experience, HQ uses "NOT", "least", and "NEVER".


Blogpost link 404s

http://madebynathan.com/2011/10/18/git-shortcuts-like-youve-never-seen-before/
It was really hard to find you from old hackernews posts because you changed the paths for your blog!

Thanks for letting me know! I've added a redirect


Update issue template

Additional guidance for what type of details should be included with a bug report.
I've removed the formatting around links as it did not succeed in making the template more readable in the New Issue composer, which is where most people would see this for the first time.

Those of you who have spent more time triaging issues will likely have a better idea of what details people should provide up front.

LGTM. A note about how to enable verbose logging might be useful as well.

@hramos updated the pull request.


Many warnings because Swoosh does not declare Plug as a dependency

Describe the bug
When I include Swoosh in my application and compile dependencies I get a LOT of warnings from Swoosh.
The first couple:
warning: Plug.Builder.__before_compile__/1 defined in application :plug is used by the current application but the current application does not depend on :plug. To fix this, you must do one of:

  1. If :plug is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :plug is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :plug, you may optionally skip this warning by adding [xref: [exclude: [Plug.Builder]]] to your "def project" in mix.exs

  lib/plug/mailbox_preview.ex:2: Plug.Swoosh.MailboxPreview

warning: Plug.Builder.__using__/1 defined in application :plug is used by the current application but the current application does not depend on :plug. To fix this, you must do one of:

  1. If :plug is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :plug is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :plug, you may optionally skip this warning by adding [xref: [exclude: [Plug.Builder]]] to your "def project" in mix.exs

  lib/plug/mailbox_preview.ex:17: Plug.Swoosh.MailboxPreview

This problem should be easily fixed by adding {:plug, "~> 1.1"}, to the mix.exs file in the deps function.
Steps to Reproduce the Bug or Issue
Include swoosh in my dependencies. Compile.
Expected behavior
The app compiles without almost 300 lines of warnings.
Your reproducible example
No response
Screenshots or Videos
No response
Platform
Erlang/OTP 24 [erts-12.3] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:1] [jit]
Elixir 1.13.3 (compiled with Erlang/OTP 24)
Additional context
No response

Observation, which I don't think should eliminate the need to declare plug as a dependency, but I switched to Elixir 1.14.5-otp-25 and recompiled and didn't get any errors.
I still think it would make sense to declare plug as an explicit dependency.

I suspect that you added plug or plug_cowboy at some point then removed it from mix.exs. Hence the deps are not clean. In a clean environment, either:

you have plug or plug_cowboy in deps
or you don't have them in mix.exs and you don't have the deps installed

You won't see the warning.

The problem is not with my deps. Swoosh is clearly dependent on Plug, but does not declare that dependency in its own mix.exs. That should be fixed, whether it is causing a compile problem or not. At least in that way it would let Swoosh control the version of Plug that is used.

It is an optional dependency through plug_cowboy.


Inconsistency between arm64 and x86 containers

In preparing a hands on lesson on MsPASS for the SCOPED workshop in May 2024 I uncovered two inconsistencies in behavior between the arm64 and x86 containers.   One is simply a performance issue that isn't totally surprising.  The second is bigger issue that is causing a job that runs fine on x86  to crash in mysterious and inconsistent ways.
Let me discuss the performance issue first.   The differences in these results are likely partly details of the hardware of the individual machines I ran this test on, but the variation is much larger than seems reasonable.   I ran this workflow in data from 20 large teleseismic events recorded by the Earthscope TA in 2011 made up of 26247 waveforms of about an hour in duration with a 40 sps sample rate.
Here is the simple serial processing loop I ran on that data for the tutorial exercise:
# Assume wf_miniseed contains only the data we want so we request all documents
t0 = time.time()
cursor = db.wf_miniseed.find({})
for doc in cursor:
    d = db.read_data(doc,collection="wf_miniseed")
    d = detrend(d,type='constant')
    d = filter(d,'bandpass',freqmin=0.01,freqmax=2.0)
    d = trim_edges(d)
    db.save_data(d,data_tag="serial_example")
t = time.time()
print("Elapsed time to process=",t-t0)

noting time_edges is little more than a call to WindowData.   The calculations are pretty lightweight so there is a strong possibility that workflow is IO bound, although while running a monitor shows it consumes 100% of one core.  There is a parallel version in tutorial too that replaces the read and write with the distributed versions and does the three processing steps with a bag map operator - the standard way in MsPASS.
I ran this on three desktop machines:  (1) an 8 core linux pc, (2) a mac mini with an M1 chip and 8 cores, and (3) a mac air laptop with an M2 chip set and 8 cores.   All three are reading and writing with and SSD file system.  The parallel job used 4 workers run as processes to avoid the GIL problem.  The surprising (to me anyway) results are these:

Linux box:  serial job: 263 s, parallel job:  138 s
M1 chip (mac mini):   serial job:  995 s, parallel job:  1038 s.
M2 chip (mac air):   serial job:  430 s, parallel job (8 workers):  380 s.

I do not find the M1 versus M2 difference surprising, but the difference between the linux machine and the macs is huge.   I wonder if even though our container sis built for arm64 that something is causing the mac version to run in x86 emulaton mode or something in docker is running x86 and is the throttle here.   That hypothesis could be tested by running this with a compiled version of MsPASS or the arm64 conda package that is in the works.
The (potentially unrelated) issue that running this tutorial workflow has shown is a weird instability of the arm64 version.   I have run the linux version multiple times with no issues.  However, I've never been able to get the same notebook with the same data (as far as I can tell anyway) to completion on either of the macs mentioned above.   I've seen two problems:

In one run MongoDB crashed with no clear record i could make sense of in mongodb's log file.  The only hint was a bunch (probably about 50)  of "Slow query" messages and then the log just ends.
A later part of this notebook does a more extensive processing to compute P wave arrival times and window data around a predicted P wave time.  It also differs in that is used the ensemble model where data are read as "source gathers" and processed together.  That was an intentional lesson for the workshop as that particular case is more efficient to handle that way.   Otherwise the processing sequence is almost the same except it adds a step to compute P wave arrival times and cut down the data to a smaller window around P.  The weird thing is that it crashes in the call to detrend (i.e. I get the window that comes up saying "kernel died") before it even gets to the section that is different.    I can only get the entire notebook to run if I comment out the call to detrend.   (Note I have verified with brutal print statements the the ensemble and all the members that enter detrend are marked live and have no obvious metadata problems created by the normalization steps that this box adds)   If I could recreate the problem with ubuntu I could run the job with a debugger and maybe find this problem, but the debug tools in a notebook do not allow me to step into external python modules.  This is happening somewhere inside detrend.   How can we sort this out?

For the record, this is the code block that is failing on arm64 but not linux:
from obspy.taup import TauPyModel
from mspasspy.db.normalize import ObjectIdMatcher
ttmodel = TauPyModel(model="iasp91")
# The default for this generic normalizer is to use channel and channel_id
# for normalizing - works here because we ran normalize_maeed earlier
channel_normalizer = ObjectIdMatcher(db)
source_otime_tolerance = 5.0   # fudge factor on start time for miniseed time irregularities
source_matcher = OriginTimeMatcher(db,t0offset=300.0,data_time_key="gather_starttime",tolerance=source_otime_tolerance)

# we loaded data with this offset relative to origin time - used below
t0offset=300.0
resampler=ScipyResampler(20.0)
decimator=ScipyDecimator(20.0)
stime=-100.0
etime=500.0

t0 = time.time()
nlive=0
ndead=0
cursor=db.source.find({})
for doc in cursor:
    # construct a waveform query as a time range around the
    # expected start time - similar to earlier
    otime = doc['time']
    ottest = otime + t0offset
    wfquery = {'starttime' : { '$gt' : ottest-source_otime_tolerance, '$lt' : ottest+source_otime_tolerance} }
    wfcursor = db.wf_miniseed.find(wfquery)
    ensemble = db.read_data(wfcursor,
                            collection='wf_miniseed',
                            normalize=[channel_normalizer],
                           )
    # We normalize the ensemble a more efficient way here
    # we just load attributes from doc into the ensemble's Metadata container
    ensemble['gather_starttime'] = ottest   # time reference is like a datum's start time not an origin time
    ensemble = normalize(ensemble,source_matcher)
    ensemble = detrend(ensemble,type="constant")
    ensemble = resample(ensemble,decimator,resampler)
    ensemble = set_PStime(ensemble)
    ensemble = cut_Pwindow(ensemble,stime,etime)
    for i in range(len(ensemble.member)):
        if ensemble.member[i].live:
            nlive += 1
        else:
            ndead += 1
    db.save_data(ensemble,data_tag='preprocessed')
t=time.time()
print("Total processing time=",t-t0)
print("Number of live data saved=",nlive)
print("number of data killed=",ndead)

This is something we should keep a record of, but it should be fine to close it now.


suggestion: a pre-commit hook test for deb-get

If accepted, I'll also commit a fix of the current files.

I like this. It does have implications for contributors' systems and workflows as well as potentially improving quality and consistency so needs a bit of testing and discussion and probably some notes in the contribution guide (which needs updating anyway...).
Even if it is not finally accepted and merged I'm pretty sure I'll be retaining and maybe extending these suggestions locally in this and other projects so thanks again for the incentive to explore another area of git and foss magic.

I like this idea. I wonder if a better place for these checks might be GitHub actions.

I think it is preferable to have these checks done pre-commit as they help keep all forks clean and shiny. I do have concerns though that imposing shellcheck on contributorssystems and workflow might be something better handled in a repository workflow. But then even that simply imposes the installation and use ofshellcheck` on contributors without facilitating that for them, so I end up accepting pre-commit as the place to do this.
The key for me is accompanying guidance for contributors.

Fair enough. I'm all for checks at the IDE level, pre-commit level and the github actions, they each have their function in the workflow.
As for documentation updates, I'll try to get to all that. I'm just a little pre-occupied here with the war efforts in Israel. May take some time.


The right way to load dynamic remote

Hi guys, thanks for the contributions of the module federation work. Recently I've experimented with the dynamic loading of mf, I found this two resources:

https://gist.github.com/ScriptedAlchemy/3a24008ef60adc47fad1af7d3299a063
https://github.com/module-federation/module-federation-examples/tree/master/advanced-api

Since these two examples haven't been updated for a while, I was wondering which is one is the best solution to load dynamic remote? Especially when I use React, thanks.

have you tried something like this:
const RemoteComponent = React.lazy(async () => {   let remoteModule;   try {     remoteModule = await import('@mf/remoteComponent');   } catch (e) {     remoteModule = await import('./fallbackComponent');   }   return remoteModule; });

You can check the official webpack docs.. https://webpack.js.org/concepts/module-federation/#dynamic-remote-containers
and of course for this to work, remote entry file has to be loaded with a script tag in the dom..
and https://github.com/module-federation/module-federation-examples/tree/master/advanced-api example demonstrates the exact same thing..
So I think.. it's reasonably right way to do it.

try catch or suspense fallbacks / error boundaries are the way to go.
You can use the advanced API to load dynamic remotes.
there's utils in this repo for loading remotes and injecting them. they should also work client or server side too
in browser its window.remote in node its global.remote_scope.remote


Copy operation doesn't auto refresh on network drives

Description
Anytime I copy files, or create a folder, I have to hit the reset button. It works ok on the main drives, but on network drives it doesn't work
Steps To Reproduce
No response
Expected behavior
I"d like to see the files copied displayed in the folder.
Files Version
<IP_ADDRESS>
Windows Version
Windows 10 21H2
Relevant Assets/Logs
debug_fulltrust.log
debug.log

Tracked in #5869


[Feature Request] Troubleshooting Guide / how to reset OpenDevin

What problem or use case are you trying to solve?
This bug : https://github.com/OpenDevin/OpenDevin/issues/2837
Describe the UX of the solution you'd like
Something in the Readme to help me reset OpenDevin to a working state
Do you have thoughts on the technical implementation?
Yes this is a script I made but it did not work
#!/bin/bash

set -e

CONTAINERS=$(docker ps -aq --filter "name=opendevin")
VOLUMES=$(docker volume ls -q --filter "name=opendevin")

CONTAINERS_COUNT=$(echo "$CONTAINERS" | wc -w)
VOLUMES_COUNT=$(echo "$VOLUMES" | wc -w)

echo "Found $CONTAINERS_COUNT containers and $VOLUMES_COUNT volumes containing 'opendevin'"

if [ -n "$CONTAINERS" ]; then
  docker rm -f $CONTAINERS
  echo "Removed $CONTAINERS_COUNT containers"
fi

if docker image inspect ghcr.io/opendevin/opendevin:latest &>/dev/null; then
   echo "Image found, removing..."
   docker rmi ghcr.io/opendevin/opendevin:latest
 else
   echo "Image not found, skipping removal"
fi

docker builder prune -af

if [ -n "$VOLUMES" ]; then
  docker volume rm $VOLUMES
  echo "Removed $VOLUMES_COUNT volumes"
fi

echo "Done"

Describe alternatives you've considered
I guess build from source ?
Additional context

This is interesting.
I set my WORKSPACE_BASE to something nonexistent. Instead of OpenDevin erroring out or telling me there is no folder or some sort of warning before creating the folder, it just went ahead and created that folder.
I agree there should be some sort of message or warning of sorts that tells me the workspace I set doesn't really exist and that OpenDevin is creating an empty one. That way at least it's visible somewhere that this occurred. Let me update the issue title to reflect that.


If we have passed the private key, don't copy it implicitly

Fixes #16197

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged. Thanks!


ZConnection.executeSqlWith to use setObject as fallback

Fixes issue inserting with a UUID  column, but i think it should work with other types.
timestamp=2023-01-23T03:20:16.082152Z level=ERROR thread=#zio-fiber-126 message="Error executing SQL due to: Exception in thread "zio-fiber-126" org.postgresql.util.PSQLException: ERROR: column "id" is of type uuid but expression is of type character varying
  Hint: You will need to rewrite or cast the expression.
  Position: 71

Unfortunately, the issue is a blocker for my use case, as i need to bulk insert, so i'll have to drop Sql.values in order to generate insert statements with required casts 😿  @jdegoes Can you please publish a new release once it's merged 🙏

Merged, will cut a new release!


View messed up when displaying alert

When double clicking an alert generated by Cacher in the Server app - the view gets messed up, forcing to quit and restart the server app.
See GIF:

Yes that is an issue with Server.app and there isn't anything I can do to resolve that issue. I suggest creating an email alert to get this data, vs looking at it via the GUI. You can find out how to do this at https://onemoreadmin.wordpress.com

On Jun 20, 2016, at 7:42 AM, Will Wiggins<EMAIL_ADDRESS>wrote:
When double clicking an alert generated by Cacher in the Server app - the view gets messed up, forcing to quit and restart the server app.
See GIF:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Updating Insight contributing page

Out of date Java is a quick fix, other quick fixes can be added, everything else can go on a Trello card for 5.2.2.
https://trello.com/c/XF44F6RN/396-update-build-instructions-contributing-docs

@hflynn:
I will remove the section ant since the command indicated like java build will not work
and for now point to http://www.openmicroscopy.org/site/support/omero5.2-staging/developers/build-system.html
we can rework that section in 5.2.2

Pushed, should be good to merge now.
I wonder if actually, rather than messing about with this for 5.2.2, there is any point in keeping this page longer term? Maybe we just delete it for 5.3 instead.

@hflynn: probably delete it in 5.3
Merging


Adding Free View

We need to update the SQL query to limit the views so its faster and to remove the pagination function.

Thought was we can have an easy to remember folder 'freeview' and manipulate the page any way we want to conform to free users. Also thought it would be overall easier. Fine either way.


Go to next unused

Similar to "Go to Next Problem" (f8, alt/f8) but for unused vars, fields, imports, functions, etc.
It'd help cleaning up the code while still being able to check what each of them are.

You should have your language or linter mark unused code as an error/warning. That ways they show in the problems panel and f8 works
For js/ts, just set noUnusedLocals in your jsconfig or tsconfig


Make it more obvious the project is open source and the code is available on GitHub

We don't seem to be converting website visitors to GitHub repository visitors.

I think one of the first things we can look into is make the GitHub icons more obvious (right now there are small and kinda hidden).

I think we could also modify the intro text a bit to say that webhint is an open-source linting tool and link out from there as well.

I think one of the first things we can look into is make the GitHub icons more obvious

The icons at the top on the right-hand side computes to 15x15px, could probably double their size?
IMO, a link to GitHub in the menu would be nice. Even if only at smaller breakpoints such as when the menu is collapsed on mobile devices:

Good ideas @Malvoz
Do you want to implement them?


blockdust/blockcrack/iconcrack particles not working?

I'm unsure if this is just me being stupid, but I've been trying to make colored particle effects via iconcrack/blockcrack/blockdust. However, when I try to use stained clay to achieve an effect, all I get is White Stained Clay particles from iconcrack, and errors for blockcrack and blockdust.
The commands I've used to test this out are:
- playeffect <player.location.cursor_on.center> 'effect:blockcrack_45215' data:0.3 quantity:10 offset:0,0,0
- playeffect <player.location.cursor_on.center> 'effect:blockdust_45215' data:0.3 quantity:10 offset:0,0,0
- playeffect <player.location.cursor_on.center> 'effect:iconcrack_159,11' data:0.3 quantity:10 offset:0,0,0

45215?
What is that supposed to represent?

It's supposed to be the ID that identifies what particle I want to use. In vanilla MC, blockcrack and blockdust rely on only one number, which is calculated by <item ID> + (<item metadata> * 4096). For example, if I wanted to use stone (ID of 1), I would use 1 as the number to specify that the blockdust/blockcrack particle I want is just stone. However, if I wanted to use diorite, I would use the formula to calculate what number I need to use. Since its metadata is 3, I need to multiply it by 4096, then add it to the ID. This would produce  12289, which is the number I would use to produce blockcrack/blockdust particles that used diorite.

 I exposed the options for that.
It'd be effect:blockcrack_1,3 or 159,11
Dev build 126+ on http://ci.citizensnpcs.co/job/Denizen_Developmental/ has the fix.

It appears to be fixed. I'm hesitant to close this issue in case this sort of problem crops up again (and I'll be honest, I've had more issues with the playeffect command than most other commands), but I'm more than willing to believe that there's nothing else regarding the blockdust, blockcrack, and iconcrack particle effects.
Thank you for helping out!

Okay, nevermind. Either I'm drunk, or iconcrack still doesn't work for some reason. It does the same thing that it did before, it just returned White Stained Clay particles.

But the other two work fine with colors, right?

I believe so, yes. I've tried out both blockdust and blockcrack with various colored blocks.

Lol, uh, build 127+ actually :P there was a typo in the pre-existing code there too

Confirmed that the current build works. Thank you!


How to run finetuning on server without internet connection

I ran the finetuning with lora on my server without internet connection, the following error appears:
Traceback (most recent call last):
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/urllib3/connection.py", line 174, in _new_conn
conn = connection.create_connection(
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/urllib3/util/connection.py", line 72, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/socket.py", line 954, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/urllib3/connectionpool.py", line 703, in urlopen
httplib_response = self._make_request(
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/urllib3/connectionpool.py", line 386, in _make_request
self._validate_conn(conn)
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn
conn.connect()
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/urllib3/connection.py", line 363, in connect
self.sock = conn = self._new_conn()
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/urllib3/connection.py", line 186, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x2afc97e66820>: Failed to establish a new connection: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/requests/adapters.py", line 489, in send
resp = conn.urlopen(
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/urllib3/connectionpool.py", line 787, in urlopen
retries = retries.increment(
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/urllib3/util/retry.py", line 592, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: /api/models/llama_hf/llama-7b-hf (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x2afc97e66820>: Failed to establish a new connection: [Errno -2] Name or service not known'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/fs0/home/liqiang/LMFlow/examples/finetune.py", line 76, in
main()
File "/fs0/home/liqiang/LMFlow/examples/finetune.py", line 72, in main
tuned_model = finetuner.tune(model=model, lm_dataset=lm_dataset)
File "/fs0/home/liqiang/LMFlow/src/lmflow/pipeline/finetuner.py", line 266, in tune
trainer.create_model_card(**kwargs)
File "/fs0/home/liqiang/LMFlow/transformers-main/src/transformers/trainer.py", line 3562, in create_model_card
training_summary = TrainingSummary.from_trainer(
File "/fs0/home/liqiang/LMFlow/transformers-main/src/transformers/modelcard.py", line 610, in from_trainer
return cls(
File "", line 17, in init
File "/fs0/home/liqiang/LMFlow/transformers-main/src/transformers/modelcard.py", line 385, in post_init
info = model_info(self.finetuned_from)
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/huggingface_hub/utils/_validators.py", line 120, in _inner_fn
return fn(*args, **kwargs)
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/huggingface_hub/hf_api.py", line 1623, in model_info
r = requests.get(path, headers=headers, timeout=timeout, params=params)
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/requests/api.py", line 73, in get
return request("get", url, params=params, **kwargs)
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/requests/api.py", line 59, in request
return session.request(method=method, url=url, **kwargs)
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/requests/sessions.py", line 587, in request
resp = self.send(prep, **send_kwargs)
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/requests/sessions.py", line 701, in send
r = adapter.send(request, **kwargs)
File "/fs0/home/liqiang/anaconda3/envs/lmflow/lib/python3.9/site-packages/requests/adapters.py", line 565, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: /api/models/llama_hf/llama-7b-hf (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x2afc97e66820>: Failed to establish a new connection: [Errno -2] Name or service not known'))

Hi,
You may look into the code line 266 in this file.
File "/fs0/home/liqiang/LMFlow/src/lmflow/pipeline/finetuner.py"
Commenting out line 264-266 may help.

Thank you very much, this solved my error.


Web - Email Persistence Issues when Adding Commas after Email in Search Bars

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to the plus sign > New chat > write an email from your contacts > add multiple commas.
Observe that the email remains persistent in the preview.
Write a new email that has never been used before and add multiple commas after it.
Observe that the email is not persistent in the preview; instead, it displays as an invalid email.

Expected Result:
The preview should either display an invalid email for both new emails and contact emails or show both in the preview when multiple commas are added after the email in the search bar.
Actual Result:
The app shows an invalid email when we search for a new email and add multiple dots after it, but the contact email remains persistent in the preview even after adding multiple commas after writing the email found in our contacts.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.37-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/ce0d3a59-3a92-4499-938c-6f94e219a307
https://github.com/Expensify/App/assets/93399543/dc2ea65c-d47b-4f8f-afc7-590e46ee2db1
Expensify/Expensify Issue URL:
Issue reported by: @tewodrosGirmaA
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688639380099079
View all open jobs on GitHub

This is done so that user can search for multiple users like<EMAIL_ADDRESS><EMAIL_ADDRESS>So i don't think this is a bug.

@jeet-dhandha if that answer it should work for both for new email and the email in contact. what are your thought on this?

In new chat we don't have any feature where user can directly start a new chat with comma separated users, it might be more of a feature request.

will be OOO fri-mon and it's 10pm for me now, reassigning

I think this is working as expected because we want the known email to be persistent and for the unknown, since we don't know it, we don't want to assume it.


fix: Bridge Bridge

Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge.

Bridge

(this was actually merged i promise github is just weird)


Fixing signing issues

Fixes: https://github.com/santthosh/aws-es-kibana/issues/27
and [I think]: https://github.com/santthosh/aws-es-kibana/issues/29

Thanks @Amit-A, this has been fixed with PR #23


[BSI][20210511][v2.2] ZIP Processing Resource Exhaustion

Rating: Informational
The JavaScript that is used to process the ZIP archives is vulnerable to a resource exhaustion attack. More specifically,
it is possible to upload a specially crafted ZIP file which leads to an endless loop while decompressing the file.
As the file decompression is done in a separate worker, this does not affect the main process of the log upload browser
tab. Therefore, the implications of this issue are rather low. On the tester’s machine the endless loop resulted in a very
high CPU usage, however, as the main process of the tab is not affected, it can simply be closed to stop the loop.
Due to time restrictions, the cause of this issue has not been further investigated. The issue has been tested in a setup
isolated from the cwa-log-upload application to rule out any possible influence by the application itself. This test showed
that the issue, in fact, stems from the library.
Proof of Concept
The screenshot below shows that the file is struck while decompressing and the processor utilization of the worker
goes up to about 100%:

Below is a hexdump of the offending ZIP file. The file is a partially corrupted ZIP file which contains two files (a and P)
with a size of 34 and 19. It was created during randomly corrupting ZIP files, therefore the corruption does not follow a
specific format.
00000000 50 4b 03 04 14 00 08 00 08 00 00 00 00 00 00 00 |PK..............|
00000010 00 00 00 00 00 00 00 00 00 00 01 00 00 00 61 4a |..............aJ|
00000020 84 82 24 9c 00 10 00 00 ff ff 50 4b 07 08 6f b2 |..$.......PK..o.|
00000030 bf e3 0b 00 00 00 22 00 00 00 50 4b 03 04 14 00 |......"...PK....|
00000040 08 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000050 00 00 00 00 01 00 00 00 62 4a 4c 4a 4e 49 4d 4b |........bJLJNIMK|
00000060 cf 30 30 34 32 36 ff 7f 33 b7 b0 34 00 04 00 00 |.00426..3..4....|
00000070 ff ff 50 4b 07 08 da c9 f3 fc 19 00 00 00 13 00 |..PK............|
00000080 00 00 50 4b 01 02 14 00 14 00 08 00 08 00 00 00 |..PK............|
00000090 00 00 6f b2 bf e3 0b 4c 00 00 22 00 00 00 01 00 |..o....L..".....|
000000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000b0 61 50 4b 01 02 14 00 14 00 08 00 08 00 00 00 00 |aPK.............|
000000c0 00 da c9 f3 fc 19 00 00 00 13 00 00 00 01 00 00 |................|
000000d0 00 00 00 00 00 00 00 00 00 00 00 3a 00 00 00 50 |...........:...P|
000000e0 4b 05 06 00 00 00 00 02 00 02 00 5e 00 00 00 82 |K..........^....|
000000f0 00 00 00 00 00 |.....|
000000f5

@ascheibal / @daniel-eder
Was this problem meanwhile fixed or will it be fixed soon?

Hi @Ein-Tim,
this is probably a won't fix. It is rated only informal, as no issue is given in real live conditions. The exploit was found on local run with none of the security measures applied.
In general DOS caused by endless loops or other exhausts is a well known attack vector on buffered I/O and is a really severe problem for server services - in this case only the client loading such a corrupted zip would be affected and simply closing the current browser window would solve it.
Only few people (the mobile developers) can use the service at all.

@ascheibal
Thanks for your response!
I suggest to consider closing this issue if it won't be addressed.
Enjoy the easter weekend!


Add Kscale2 - a KSP system resize mod from SpaceDock

This is a semi-automated commit on behalf of Paul_Kingtiger

I'll make a clean PR from local


Detect unused dependencies in CI

This requires cargo nightly: cargo +nightly udeps

Done in https://github.com/roc-lang/roc/pull/6635


Add adjustments in release action for stable

What

Add adjustments in release action for stable

If there is input param, flavor will be chosen by parameter (beta/stable)
If that is left empty, then determine the flavor by branch name

Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

I'd also love to see a github action run that tests this (comment out the publishing part of the task but let it upload to the azure blob store and check the blob store contents are correct). Github action syntax is not friendly or very readable and we don't want this failing when we finally do publish
(or even some action runs that are cancelled after the rush-switch is executed)

I'd also love to see a github action run that tests this (comment out the publishing part of the task but let it upload to the azure blob store and check the blob store contents are correct). Github action syntax is not friendly or very readable and we don't want this failing when we finally do publish (or even some action runs that are cancelled after the rush-switch is executed)

Thanks, James, for coming up with a smart way to test, now all cases were tested:
Without parameter, without beta in the name: https://github.com/Azure/communication-ui-library/actions/runs/1866916009
Without parameter, beta in the name: https://github.com/Azure/communication-ui-library/actions/runs/1866928360
Stable parameter, but beta in the name(will choose stable): https://github.com/Azure/communication-ui-library/actions/runs/1866936808
beta parameter, but no beta in the name(choose beta): https://github.com/Azure/communication-ui-library/actions/runs/1866945121


Cannot build host vm with Xcode 13 on macOS, TARGET_OS_LINUX dart flags declared

On Xcode 13 beta 2 (13A5154o) (available at go/xcode) on dart 557c841b50b I wasn't able to build the host Flutter engine.
$ ./flutter/tools/gn --unoptimized && ninja -C out/host_debug_unopt
...
ninja: Entering directory `out/host_debug_unopt'
[1/1] Regenerating ninja files
[4594/5483] LINK ./gen_snapshot
FAILED: gen_snapshot
../../buildtools/mac-x64/clang/bin/clang++ -isysroot /Users/m/Applications/Xcode-13_beta2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.0.sdk -mmacosx-version-min=10.11.0 -rdynamic -arch x86_64 -nostdlib++ -stdlib=libc++ -Wl,-search_paths_first -L. -Wl,-rpath,@loader_path/. <EMAIL_ADDRESS>-Wl,-pie  -Xlinker -rpath -Xlinker @executable_path/Frameworks -o ./gen_snapshot -Wl,-filelist,./gen_snapshot.rsp  -ldl -lpthread -framework CoreFoundation -framework CoreServices
Undefined symbols for architecture x86_64:
  "dart::FLAG_generate_perf_jitdump", referenced from:
      dart::VirtualMemory::Init() in libdart_vm_precompiler.virtual_memory_posix.o
  "dart::FLAG_generate_perf_events_symbols", referenced from:
      dart::VirtualMemory::Init() in libdart_vm_precompiler.virtual_memory_posix.o
ld: symbol(s) not found for architecture x86_64
clang-13: error: linker command failed with exit code 1 (use -v to see invocation)
[4611/5483] CXX obj/third_party/dart/runtime/vm/libdart_vm_jit.object.o
ninja: build stopped: subcommand failed.

(Ran on top of PR https://github.com/flutter/buildroot/pull/475 to pick up macOS 12 SDK.)
@jason-simmons noticed those dart flags should be gated on #if defined(TARGET_OS_LINUX).
https://github.com/dart-lang/sdk/blob/d9f9b4dc96064879a8187b48ed62a7cbc32abc2c/runtime/vm/virtual_memory_posix.cc#L40-L43
The Xcode 12.5 (working) TargetConditionals.h does not define TARGET_OS_LINUX:
    #define TARGET_OS_MAC               1
    #define TARGET_OS_WIN32             0
    #define TARGET_OS_UNIX              0

TargetConditionals-12.h.txt
But Xcode 13 does (as well as TARGET_OS_WINDOWS):
    #define TARGET_OS_MAC               1
    #define TARGET_OS_WIN32             0
    #define TARGET_OS_WINDOWS           0
    #define TARGET_OS_UNIX              0
    #define TARGET_OS_LINUX             0

TargetConditionals-13.h.txt

\cc @zanderso

One option would be to put a Dart-specific prefix on the existing defines, i.e. TARGET_OS_MAC -> DART_TARGET_OS_MAC, etc.
/cc @a-siva @aam @rmacnak-google

Or these kinds of checks can be swapped to check the value instead of whether it's defined, since if it's not defined it would be 0.
#if TARGET_OS_LINUX.

Not sure why the code in sdk/runtime/vm/virtual_memory_posix.cc needs to be guarded around TARGET_OS_LINUX, there is code in os_android.cc that is not guarded like that.

Since the TargetConditionals.h header is updated with new defines, the issue affects all #if defined(TARGET_OS...) checks.

Do you see additional undefined symbols ?

@a-siva If I comment out the DECLARE_FLAGs it then crashes
===== CRASH =====
si_signo=Segmentation fault: 11(11), si_code=1, si_addr=0x100
version=2.14.0-244.0.dev (dev) (Thu Jun 24 12:43:59 2021 -0700) on "macos_x64"
pid=69720, thread=3587, isolate_group=vm-service(0x7fbbee812c00), isolate=vm-service(0x7fbbee817e00)
isolate_instructions=10f9162c0, vm_instructions=10f9162c0
  pc 0x0000000112c824c7 fp 0x000070000319e9a8 Unknown symbol
  pc 0x000000010fc58619 fp 0x000070000319ea50 dart::DartEntry::InvokeCode(dart::Code const&, unsigned long, dart::Array const&, dart::Array const&, dart::Thread*)+0x149
  pc 0x000000010fc5842d fp 0x000070000319eac0 dart::DartEntry::InvokeFunction(dart::Function const&, dart::Array const&, dart::Array const&, unsigned long)+0x14d
  pc 0x000000010fd0d477 fp 0x000070000319eb40 dart::Library::Invoke(dart::String const&, dart::Array const&, dart::Array const&, bool, bool) const+0x307
  pc 0x000000011048f069 fp 0x000070000319ec30 Dart_Invoke+0x639
  pc 0x000000010fbd4beb fp 0x000070000319ec80 dart::bin::DartUtils::PrepareBuiltinLibrary(_Dart_Handle*, _Dart_Handle*, bool, bool)+0x4b

but maybe that's not what you're asking?
I see places this could be a problem if the code was ever rewritten or refactored, like say these conditions were reverted:
https://github.com/dart-lang/sdk/blob/2c6009efafdee8668ab6f5be3919903c3a94a51d/runtime/vm/image_snapshot.cc#L965-L967
or this was refactored to not || defined(TARGET_OS_MACOS):
https://github.com/dart-lang/sdk/blob/82ea8416ed2a22e40c5c67252cb37bebec3a57e8/runtime/bin/snapshot_utils.cc#L352
https://github.com/dart-lang/sdk/search?q=TARGET_OS_LINUX

https://dart-review.googlesource.com/c/sdk/+/205860 has rolled into the engine.

Just tested, seems to be working now.  Thanks @zanderso!


Service 'workspace' failed to build : Build failed

executor failed running [/bin/sh -c set -xe;     apt-get update -yqq &&     pecl channel-update pecl.php.net &&     groupadd -g ${PGID} laradock &&     useradd -l -u ${PUID} -g laradock -m laradock -G docker_env &&     usermod -p "*" laradock -s /bin/bash &&     apt-get install -yqq       apt-utils       libzip-dev zip unzip       php${LARADOCK_PHP_VERSION}-zip       nasm &&       php -m | grep -q 'zip']: exit code: 1

> [  3/107] RUN set -xe;     apt-get update -yqq &&     pecl channel-update pecl.php.net &&     groupadd -g 1000 laradock &&     useradd -l -u 1000 -g laradock -m laradock -G docker_env &&     usermod -p "*" laradock -s /bin/bash &&     apt-get install -yqq       apt-utils       libzip-dev zip unzip       php8.0-zip       nasm &&       php -m | grep -q 'zip':
#6 0.226 + apt-get update -yqq
#6 16.10 + pecl channel-update pecl.php.net
#6 16.21 PHP Warning:  foreach() argument must be of type array|object, null given in /usr/share/php/PEAR/Command.php on line 249
#6 16.21
#6 16.21 Warning: foreach() argument must be of type array|object, null given in Command.php on line 249
#6 16.21
#6 16.21 Warning: foreach() argument must be of type array|object, null given in Command.php on line 249
#6 16.21 PHP Warning:  foreach() argument must be of type array|object, null given in /usr/share/php/PEAR/Command.php on line 249
#6 16.21 PHP Warning:  foreach() argument must be of type array|object, null given in /usr/share/php/PEAR/Command.php on line 249
# ... ...
#6 16.23 Warning: foreach() argument must be of type array|object, null given in PEAR/Command.php on line 249
#6 16.23 PHP Warning:  foreach() argument must be of type array|object, null given in /usr/share/php/PEAR/Command.php on line 249
#6 16.23 PHP Warning:  foreach() argument must be of type array|object, null given in /usr/share/php/PEAR/Command.php on line 249
#6 16.23 PHP Warning:  foreach() argument must be of type array|object, null given in /usr/share/php/PEAR/Command.php on line 249
#6 16.23
#6 16.23 Warning: foreach() argument must be of type array|object, null given in PEAR/Command.php on line 249
#6 16.23
#6 16.23 Warning: foreach() argument must be of type array|object, null given in PEAR/Command.php on line 249
#6 16.23 XML Extension not found

@niuto are you trying to build using PHP 8.0? If so I think this is the same issues as this: https://github.com/laradock/laradock/issues/3133
Change WORKSPACE_BASE_IMAGE_TAG_PREFIX=latest to WORKSPACE_BASE_IMAGE_TAG_PREFIX=20220115 in your .env file
You should be able to build then.

In my case, my disk was full...

@niuto您是否使用 PHP 8.0 制造？如果是这样，我认为这与以下问题相同：#3133
在您的 .env 文件中更改WORKSPACE_BASE_IMAGE_TAG_PREFIX=latest为WORKSPACE_BASE_IMAGE_TAG_PREFIX=20220115
那时你应该能够制造。

yes, think you

Set PHP_VERSION=7.4
//此处默认的php-redis 会获取php8的扩展，后面会有冲突，指定版本就好
apt-get install -yqq php-redis
apt-get install -yqq php${LARADOCK_PHP_VERSION}-redis \

window user account conflict or network issue

The clue for me was "XML Extension not found" -- I needed to install php-xml

The clue for me was "XML Extension not found" -- I needed to install php-xml

work for me. thanks.


feat: adding preprocessor for select functions

Changes:

Adding preprocessor callable parameter to select
Adding preprocessor callable parameter to select_multiple

Issue #3

Codecov Report

Merging #22 (fc1fee5) into master (d79c075) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage   95.93%   96.00%   +0.06%
==========================================
  Files           2        2
  Lines         197      200       +3
  Branches       62       64       +2
==========================================
+ Hits          189      192       +3
  Misses          2        2
  Partials        6        6

Flag
Coverage Δ

unittests
96.00% <100.00%> (+0.06%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

beaupy/beaupy.py
95.42% <100.00%> (+0.07%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Support for Policy description

Support the Description attribute on IAM policies. Resolves https://github.com/99designs/iamy/issues/26; see that issue for more background.

When iamy pull fetches new and existing policies, it writes a top-level Description field to the YAML file if present.
When iamy push creates new policies, it sets the description from the new top-level Description field if present.
When iamy push updates existing policies, the local YAML description is ignored because AWS policy descriptions are immutable.

Note this adds a GetPolicy AWS API call per policy to iamy pull, but not to iamy push. If this is considered too slow a goroutine concurrency pool could be added.

It seems Roles also have a description. I do think we will also want a put these calls in goroutines, this ups the number of API calls significantly

Or alternatively we have a flag to opt-in? e.g iamy pull --with-extra-descriptions

Nice work finishing this 👍


Force constructor inlining when stack-allocating objects

This is an improvement for the heap2stack optimisation pass, which replaces heap allocations by stack allocations when possible. This modification allows the optimiser to know that the parent object of a given field is stack-allocated, which gives it more information to stack-allocate the field itself.
In order to get correct nocapture info in LLVM, which greatly helps the analysis in heap2stack, class constructors in generated code now return void instead of their receiver.

I had to disable a warning on Windows because there is a DEBUG macro in LLVM which conflicts with MSVC headers. That's a really bad name for a macro.

Excellent, thanks!

This can be merged if CI passes.


Merges Master to Live. See commits for details.

OPS Build status updates of commit c9fb149:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit c9fb149:
:clock10: Incremental building: average incremental building time is 12 min(s) 22 sec(s)

OPS Build status updates of commit c9fb149:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docfx.json
:white_check_mark:Succeeded

exchange/docs-conceptual/exchange-server/recipient-filters/filter-properties.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance/New-ActivityAlert.md
:white_check_mark:Succeeded
View (exchange-ps)

skype/skype-ps/skype/New-CsSimpleUrlConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsCallingLineIdentity.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsMeetingConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

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

OPS Build status updates of commit d9ba5cc:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit d9ba5cc:
:clock10: Incremental building: average incremental building time is 12 min(s) 22 sec(s)

OPS Build status updates of commit d9ba5cc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docfx.json
:white_check_mark:Succeeded

exchange/docs-conceptual/exchange-server/recipient-filters/filter-properties.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance/New-ActivityAlert.md
:white_check_mark:Succeeded
View (exchange-ps)

skype/skype-ps/skype/New-CsSimpleUrlConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsCallingLineIdentity.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsMeetingConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

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

OPS Build status updates of commit 35110e1:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit 35110e1:
:clock10: Incremental building: average incremental building time is 12 min(s) 22 sec(s)

OPS Build status updates of commit 35110e1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docfx.json
:white_check_mark:Succeeded

exchange/docs-conceptual/exchange-server/recipient-filters/filter-properties.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance/New-ActivityAlert.md
:white_check_mark:Succeeded
View (exchange-ps)

skype/skype-ps/skype/Grant-CsVoicePolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsSimpleUrlConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsCallingLineIdentity.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsMeetingConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

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


Discussion about how to handle deeply nested dataloader

I have a graphql query that looks like this (simplified)
posts { # Type of [Post]
  body
  viewerHasLiked
  comments { # Type of [Post] (but just has parent_id column or something)
    body
    viewerHasLiked
    replies { # Type of [Post]
      body
      viewerHasLiked
    }
  }
}

I am using Dataloader for the associations and for the viewerHasLiked field. Unfortunately, when this query is run, Dataloader runs the query for viewerHasLiked twice. Once for the post and its comments, and once for the comments' replies. I have been trying to figure out a way to merge this all into one query and it ended up bringing me to Absinthe.Middleware.Dataloader. It looks like, if I understand correctly, before the field is to be resolved, the plugin calls Dataloader.run/1 on the loader in the context. Then when the middleware is called, it checks if batches are still pending (if the Dataloader has finished running?). If there are none pending, it returns the result from Dataloader and if there are still batches, it sets the field's state to :suspended and adds a middleware to that field to call it again, and that is when it returns the result.
The issue is that when Dataloader.run/1 in before_resolution/1 is called, it fetches for all the existing batches (including for viewerHasLiked), but it has only resolved posts and comments so far. I'm not really sure how this would be approached because Dataloader has to load the stuff for comments and replies in order to have the ids to use for loading viewerHasLiked.
It could be some kind of priority system where things with a higher priority (posts, comments, replies) would be resolved first, and then something with a lower priority (viewerHasLiked) would be resolved last. This might require extensive rearchitecting of absinthe because it would have to resolve in multiple passes, depth first, instead of breadth first. I'm not sure though.
We could also have a Dataloader.run/2 that selectively fetches. It could group things together by their object and look at both the schema and what's being requested in the query or mutation. With this information, it could do passes where it tries to resolve as much as possible until it can't anymore and then resolve the fields with Dataloader middleware by looking at what child fields are requested. Here's an example using the query above:

Resolves the root posts
Resolves body
Tries to resolve viewerHasLiked, but it's a Dataloader field so it suspends
Tries to resolve comments, but it's a Dataloader field so it suspends
Now it starts to resolve Dataloader fields. it looks at the query and sees that one of comments's child fields is viewerHasLiked, so it resolves (and fetches from DB) comments first
It does a pass on comments' children. It can resolve body, but not viewerHasLiked.
It tries to resolve replies, but it's a Dataloader field, so it can't. It has nothing more to resolve so it starts on the Dataloader fields
It looks at what the children of replies are, and it sees viewerHasLiked, so it resolves (and fetches) replies first.
Now it can resolve the replies' body
Finally it fetches viewerHasLiked with the ids from every level, running a single query. It can resolve the replies' viewerHasLiked
There's nothing more to resolve at this level so it goes back to the top and resolves posts' viewerHasLiked and then comments' viewerHasLiked

I'm pretty familiar with Dataloader's internals, but not as much with Absinthe's. If someone who knows more about how Absinthe words could provide their input this would be much appreciated.

Thinking about it even more, if we're gonna go the route of walking the whole tree (or walking all of a field's children depth first) ahead of time to know what to wait for and what to fetch now, it might be worth adding the ability to choose between joins or batches, because in a lot of cases, joins might be more efficient.

Hi @Un3qual ,
You should read this topic: https://github.com/absinthe-graphql/absinthe/issues/269 , I believe it will contrast with your intuition. Both approaches have different trade offs.

Here's the thing. What you're asking for isn't strictly speaking impossible, but it's quite hard for two reasons:

Resolvers are opaque to Absinthe. They're a stack of functions that contain and execute arbitrary code, Absinthe cannot easily know that partial resolution of suspended fields will be better than complete resolution of suspended fields. Right now Absinthe has an execution flow. What you would need to do is write a custom Resolution phase module that could utilize Dataloader specific information to adjust how resolution works.

Global query optimizers are very hard.

This is a fine idea at some level, but this is definitely not a bug in Absinthe and is well, well beyond anything that is part of the Absinthe roadmap. It also, strictly speaking, does NOT need to be in Absinthe core. All Absinthe phases are replaceable, and they're replaceable by plugins dynamically too, so you could write your own version of this as a separate package, give it a whirl, and if that pans out we can look at adding it to core.
The Absinthe core team has worked very hard to make Absinthe extendable, precisely so that when people want to try stuff like this, they are not bottlenecked by the core team. I'll be happy to weigh in on the forum post, but the issue tracker we try to reserve for bugs and concrete roadmaped features.


[BUG]: PowerStore Grafana dashboard does not populate correctly

Bug Description
The PowerStore Volume IO Metrics dashboard displays "No data" for all panels in the dashboard
Logs
No relevant logs.  See screeeshots
Screenshots

Additional Environment Information
No response
Steps to Reproduce
Deploy CSI observability module per instructions here: https://dell.github.io/csm-docs/docs/observability/deployment/
Expected Behavior
PowerStore Volume IO Metrics dashboard should display correctly.
CSM Driver(s)
CSM Observability for PowerStore 1.1
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
Kubernetes v1.23.5
Operating System
RHEL 8.5

@DougBernhardt How are you generating traffic at PowerStore? Likw creating volumes, IO etc and how long those test run?

Running test workloads that run for hours.
From: alikdell @.***>
Sent: Friday, April 22, 2022 6:47 AM
To: dell/csm
Cc: Bernhardt, Doug; Mention
Subject: Re: [dell/csm] [BUG]: PowerStore Grafana dashboard does not populate correctly (Issue #279)
[EXTERNAL EMAIL]
@DougBernhardt [github.com]https://urldefense.com/v3/__https:/github.com/DougBernhardt__;!!LpKI!zHrGpAiww5nNVSxa8vMdWcbYDWuupVkN_L1OGx7pesOriU03vMtxNZMX3D2MGZAdRVY$ How are you generating traffic at PowerStore? Like creating volumes, IO etc and how long those test run?

Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https:/github.com/dell/csm/issues/279*issuecomment-1106434891__;Iw!!LpKI!zHrGpAiww5nNVSxa8vMdWcbYDWuupVkN_L1OGx7pesOriU03vMtxNZMX3D2MzHesP8Y$, or unsubscribe [github.com]https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AJNSSESUHKVI3IKUZ7WPN7TVGKGTRANCNFSM5UASNOCA__;!!LpKI!zHrGpAiww5nNVSxa8vMdWcbYDWuupVkN_L1OGx7pesOriU03vMtxNZMX3D2Mf8_2I7M$.
You are receiving this because you were mentioned.Message ID: @.***>
Internal Use - Confidential

And those workloads are run on volumes/filesystem created using PowerStore CSI Driver?

This fix is available using this image dellemc/csm-metrics-powerstore:nightly. The version of the opentelemetry collector we support here  has been verified against these changes. Please continue to use this image otel/opentelemetry-collector:0.42.0.

Thanks.  I verified that charts are populating with values using these images.
From: shaynafinocchiaro @.***>
Sent: Friday, April 29, 2022 11:06 AM
To: dell/csm
Cc: Bernhardt, Doug; Mention
Subject: Re: [dell/csm] [BUG]: PowerStore Grafana dashboard does not populate correctly (Issue #279)
[EXTERNAL EMAIL]
This fix is available using this image dellemc/csm-metrics-powerstore:nightly. The version of the opentelemetry collector we support here [github.com]https://urldefense.com/v3/__https:/github.com/dell/helm-charts/blob/main/charts/karavi-observability/values.yaml*L81__;Iw!!LpKI!iXOf-EFbOvX1YVwkYeHoLHqsq1NWwXdJdXoOEbpcKbzpwfV9IFmMzPPCHljZMEJ4OhIdQBa8UFN-5JDQ8_qJyZ-vxjk$ has been verified against these changes. Please continue to use this image otel/opentelemetry-collector:0.42.0.

Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https:/github.com/dell/csm/issues/279*issuecomment-1113483913__;Iw!!LpKI!iXOf-EFbOvX1YVwkYeHoLHqsq1NWwXdJdXoOEbpcKbzpwfV9IFmMzPPCHljZMEJ4OhIdQBa8UFN-5JDQ8_qJtEgfdEc$, or unsubscribe [github.com]https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AJNSSEWTMWX7QIWBC2XKUILVHQCHDANCNFSM5UASNOCA__;!!LpKI!iXOf-EFbOvX1YVwkYeHoLHqsq1NWwXdJdXoOEbpcKbzpwfV9IFmMzPPCHljZMEJ4OhIdQBa8UFN-5JDQ8_qJPx2bPeQ$.
You are receiving this because you were mentioned.Message ID: @.***>
Internal Use - Confidential

have reviewed this. There are no issues.

Hi Doug, this issue was fixed and is included in the v1.3.0 release. Can you try with the latest image? Thanks.


handle hex inputs

Just noticed that the base branch didn't automatically update to main. Guess I shouldn't stack PR on top of each other, which I'm used to with the rollups repo. I will include the commit in another PR to main


Fix potential vulnerability by bumping sqlite to 5.1.5

Description

Addresses https://github.com/advisories/GHSA-jqv5-7xpx-qj74
Checklist

[ ] For UI or styling changes, I have added a screenshot or gif showing before & after
[x] I have added a changeset

Superseded by #1068


Add IBM Z JCL Expert v 1.1 (API Mediation Layer ZOWE V1)

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you including a repo_url? You need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Does the project meet the guidelines for new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~5 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Build failed because of:
No cached entry, and IBM Z/OS Workload Interaction Navigator (App Framework ZOWE V1) has issues with logo: IBM Z/OS Workload Interaction Navigator.SVG, ENOENT: no such file or directory, open '/opt/build/repo/hosted_logos/IBM Z/OS Workload Interaction Navigator.SVG'
Item IBM Z/OS Workload Interaction Navigator (App Framework ZOWE V1) has no image_data

Build failed because of:
No cached entry, and IBM Z/OS Workload Interaction Navigator (App Framework ZOWE V1) has issues with logo: IBM ZOS Workload Interaction Navigator.svg, ENOENT: no such file or directory, open '/opt/build/repo/hosted_logos/IBM ZOS Workload Interaction Navigator.svg'
Item IBM Z/OS Workload Interaction Navigator (App Framework ZOWE V1) has no image_data

Build failed because of:
No cached entry, and IBM Z/OS Workload Interaction Navigator (App Framework ZOWE V1) has issues with logo: IBM ZOS Workload Interaction Navigator.svg, ENOENT: no such file or directory, open '/opt/build/repo/hosted_logos/IBM ZOS Workload Interaction Navigator.svg'
Item IBM Z/OS Workload Interaction Navigator (App Framework ZOWE V1) has no image_data


Compilation fails on nightly-2019-05-16

Compilation is broken on the latest nightly due to a change in type inference:
   Compiling rustyline v4.0.0
error[E0283]: type annotations required: cannot resolve `std::string::String: std::convert::AsRef<_>`
   --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rustyline-4.0.0/src/lib.rs:627:43
    |
627 |             editor.add_history_entry(line.as_ref());
    |                                           ^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0283`.
error: Could not compile `rustyline`.
warning: build failed, waiting for other jobs to finish...
error: build failed
Exited with code 101

rustc version:
$ rustc --version --verbose
rustc 1.36.0-nightly (7d5aa4332 2019-05-16)
binary: rustc
commit-hash: 7d5aa43325ad7629766b1183011f5bf5b2a1ea26
commit-date: 2019-05-16
host: x86_64-unknown-linux-gnu
release: 1.36.0-nightly
LLVM version: 8.0
$ cargo --version --verbose
cargo 1.36.0-nightly (c4fcfb725 2019-05-15)
release: 1.36.0
commit-hash: c4fcfb725b4be00c72eb9cf30c7d8b095577c280
commit-date: 2019-05-15

Example failed build: https://circleci.com/gh/lopopolo/ferrocarril/78

We need help to make #218 works on stable and nightly.

Should be fixed by release 4.1


How to create fixed pin on the center of map

I want create fixed pin on the center of map like Uber. And what is map drag event?

@matanist
Sorry for this late answer. To achieve what you want, we done that on our application, you have to put your map in a Grid layout, and then add an image on top of it (the image of your pin) at the center of this grid. Then, when you add a pin, use the GeoCoordinates of the mapCenter to add the Pin to the location you pointed out with your image.

So when I move the map, I'm going to have to constantly calculate the midpoint. The map has no scrolling events. The scrolling events of the grid does not work.


Download v.4.7.0 links to file containing Normalize v5.00

The current Tachyons download contains Normalize 5.00. Instead, according to the release notes  it should include Normalize 6.00.
Click on Download on and open the download file. The comments at the top file say
/*! TACHYONS v4.6.1 | http://tachyons.io */
/*! normalize.css v5.0.0  */

While apart from the version number, the Tachyons CSS itselfs looks updated (it contains the f7 class), the file contains rule such as:
html {
  font-family: sans-serif;
}

and
body {
  margin: 0;
}

that are part of Normalize 5.0 but not 6.0.

Yeah, I found the currently packaged version number confusing as well...
/*! TACHYONS v4.6.1 | http://tachyons.io */

This is fixed in the latest 4.7.2 release. This issue can be closed.

I confirm this is fixed.


Focus on activate request

I request an equivalent to the i3/sway option focus_on_window_activation.
I have not found anything of sorts on the wiki nor on other issues.
This would be very nice to have since currently after pressing a link somewhere you have to manually swap to the browser workspace.
Thank you poland

check with 2c714eace5bc903e5e9ef9e2c3048cb65a2ca9b4


ssl  key to small

异常信息：
wechaty-gateway npm package update
npm i<EMAIL_ADDRESS>npm i<EMAIL_ADDRESS>

Error：ssl  key to small
解决方案：
替换wechaty-puppet-service 里面 ca.js 文件里面的ssl证书相关信息，然后即可临时修复，我这里替换的是用2048位加密位数

Thanks for creating this issue and let me know that the 1024 bit key is not working.
I have updated the code with version 0.27.7, please try it and let me know if it works for you.

The problem should have been solved.
Please let me know if there's any problem still exists.


Automated cherry pick of #2980: feature: keystone v3 auth response carry user's displayname/email/mobile

Cherry pick of #2980 on release/2.11.
#2980: feature: keystone v3 auth response carry user's displayname/email/mobile

/lgtm
/approve


Problem with the installation

The examples don't work.
Firstly, I have tried to install the plugin with pip install climetlab-plugin-a6 but
ERROR: Could not find a version that satisfies the requirement climetlab-plugin-a6
ERROR: No matching distribution found for climetlab-plugin-a6

The same trying with other way to spell the name, including the climetlab_climetlab_plugin_a6 in the README.
Finally, I managed to install with pip install climetlab-maelstrom-power-production. The package downgraded my climetlab to 0.5.6 but at least it seems running.

Hi Matteo, thanks for feedback. We will check what happens here.

Thanks for your feedback. It seems the documentation is not up-to-date and that there has been a new release of CliMetLab, and our package is pinned to an older version.


Feature/fix undefined width and height

With this feature/fix you'll be able to set a zero width and height to view images you don't know the exact width and height from.

Thank you!

Available in v1.1.0


UUIDParam not checking structure of input

UUIDParam appears to be passing the String representation directly through to the UUID.fromString method, which does not validate its input.
This allows clients to supply an invalid value which should be rejected.
We can verify the behaviour of UUID.fromString as follows:
UUID originalUuid = UUID.randomUUID();
UUID mutatedUuid = UUID.fromString(originalUuid + "1234");
assertEquals(originalUuid.toString(), mutatedUuid.toString());

I'm a bit confused. The test case that you present never passes for one of two reasons (depending on the random UUID:

Overflow in parsing originalUuid + "1234"
original != validated so assertEquals fails

Sorry for my confusing naming convention there.  I originally copied and pasted without checking that the wording made sense - I have now edited the issue to indicate that the second UUID can be regarded as "mutated".
I only ran the test a couple of times myself, so only witnessed that the original and mutated values were never equal.
I don't think that the possibility of two outcomes detract from the reported issue though.

Ah I may have misunderstood. Is the issue that UUID.fromString does validate the input, but it is too lax? If so, what are your expectations? What are (languages / RFCs / frameworks) you comparing against? Do you have a suggestion in mind?
Additionally, use hardcoded UUIDs in examples instead of random so that I can more easily follow along

My bad.  I could have specified a much simpler mutation and never triggered the overflow.
I'm not sure if there is a preferred approach to validating UUID - perhaps a regular expression would suffice?  Then throw an exception if the input does not match.

perhaps a regular expression would suffice

Maybe, but I'm wary of crafting regular expressions. I would hate for a couple weeks after a release to get a bunch of reports about how valid UUIDs are being rejected. Not saying this isn't the correct approach, but it's something to consider.

Another alternative that I have just come across involves comparing the UUID's toString value against the original input String.

That's interesting. I hadn't thought of that. Could work.

100% agree.
The regular expression approach is a little bit complex, particularly if catering for an edge case (nil/null value).

@StephenSouness @nickbabcock Would it be sufficient to check for the length of the input additionally to using it with UUID#fromString()?
This would solve the problem with the ignored suffixes and it's relatively cheap to check.

Yes that sounds good to me.

Cheap is good.
👍


Allow pipelines from AutoMLSearch to be pickled

fix #1400
The issue arises from pipeline_class(id) returning a make_pipelines.<locals>.GeneratedPipeline object. For objects, pickle only accepts classes defined on a global scale, which GeneratedPipeline did not satisfy since it was defined in the make_pipeline method. I introduced the stand-alone classes GeneratedPipelineBinary, ... in order to make these pipelines pickle-able.
Saving pipeline:

Loading and running pipeline (in a different kernel):

@bchen1116 Oops I see you've updated while I was reviewing so some of the comments might not show up on the files! LMK if anything is confusing :)

@bchen1116 Oops I see you've updated while I was reviewing so some of the comments might not show up on the files! LMK if anything is confusing :)

@angela97lin updated the docs to include info about saving pipelines and about incompatibility with stacked ensembler

@angela97lin updated the docs to include info about saving pipelines and about incompatibility with stacked ensembler


custom tooltip callback receives "undefined" instead of the tooltip model

Expected Behavior
Custom tooltip should render when tooltips.custom is passed a callback function.
Current Behavior
Custom tooltip does not render, the following errors appear in the console:
Uncaught TypeError: Wt.distanceBetweenPoints is not a function
Uncaught TypeError: Cannot read property 'opacity' of undefined
Possible Solution

core.tooltip.js callshelper.distanceBetweenPoints instead of helper.math.distanceBetweenPoints

Regression in core.tooltip.js. The update function passes the tooltip model to the custom tooltip function as options.custom.call(me);, but previous versions expect two params: options.custom.call(me, model)

Steps to Reproduce (for bugs)

Implement a chart using custm tooltips:
https://codepen.io/bjones526/pen/KKwBgzd
Context

Environment

Chart.js version: Latest code from master
Browser name and version: Chrome 79.0.3945.117
Link to your project:

Thanks for the bug report! I just sent a fix https://github.com/chartjs/Chart.js/pull/6962
There have been lots of changes in master, so please let us know if you come across anything else or need any tips on testing it out

To the 2nd point, model was remove. The first parameter Tooltip contains everything now (directly or under options), .


Add initialDuration field

Fix self issue https://github.com/MuhammadUsamaSiddiqui/circular_countdown_timer/issues/15
This logic allows you to add an initial duration.
In this case, the timer will start with initialDuration.

Hi!
I am facing issue in reviewing your pull request because you have committed code on your master branch, instead of creating a new branch. Kindly do the required fixes. I have updated my code therefore now you can make pull request using updated code.

Hi!
I am facing issue in reviewing your pull request because you have committed code on your master branch, instead of creating a new branch. Kindly do the required fixes. I have updated my code therefore now you can make pull request using updated code.

Hi! I have integrated this feature with a little bit fixes in the library. You can find it in the latest version of the library. Thanks for your contribution.


[Bug] Crash when duplicate one object twice

Select an object ctrl+D twice, the editor will crash.

Fixed in Build N#79