QuickOpen placeholder text in Warlock Contrast is hard to read

The placeholder text in the Warlock Contrast theme is really hard to read. Take a look at the screenshot below.

This is just a nitpick on an otherwise awesome theme!

Ah you're right. That is kinda poop. I'll fix that tomorrow. Thanks. :)

Christmas got in the way. :) Will take a look this evening!

This should be improved in the latest version. Thanks. :)


Stop opening files when drag and drop in explorer

Stop opening files when drag and drop in explorer
When I drag and drop any file to Visual Studio Code's explorer, it automatically opens this file in the editor. Are there any settings to turn off this behavior?
Usually, I work with large and heavy CSV, JSON, etc., so when these files open it can really slow down my computer, also because some extensions like text highlighting automatically try to parse the text, but until it realizes that it is too much content to do his job and shows a warning that it won't continue because of performance issues, it has already slowed down my computer.
Of course, I can just close fast enough the file before this happens, but sometimes the problem still occurs (and anyway it should be possible to disable this feature).

This is a problem of stack overflow. I need this too.

Any update here? I'm also interested in disabling auto open files on drag and drop. I have enough tabs open in my browser I don't need anymore in my editor T.T

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

how‘s it going?

This is also really annoying me.

Thank you, @lramos15!

When should this setting be avalible in our hand? Is it now avalible?

It is already available yes.

It's not working for me though - I have 'Explorer: Auto Open Dropped File' unchecked, but it's still opening dropped files.


Add on hover animation to landing page buttons

I'm having an idea that we can add some sort of animations on the buttons of navbar when we will hover over it. It will glow kinda

@hrshtmlng go for it
But thed added effect must be matched with the theme and it should not look contradictory
An underline effect would be preferable.

can you elaborate about the feature you wanted to include in the website

Yeah sure I was thinking that if I could add glowing color when i hover over it must looks better

@hrshtmlng  Where exactly are you expecting the glow effect because the website already contains glow spots in it.

At the place of Home, Our services, How it works, etc.

Sure you can if it looks good
If it doesn't then simply add underline erfect

Okay so, I'm working on it :)

@hrshtmlng what's the status ?


Error Monitoring

This PR is for setting up error monitoring and performance logging for our project using sentry.io
Updates:
Currently set up sentry and able to receive emails for errors.

Nice work, is there a dashboard where it logs errors too?
Does it capture all errors or only some?
Does it capture execution time?
Thanks! Include screenshots if possible.

Merged in #176


fix(flask.py): ignore flask url_rule and not path

Fixing cases for endpoint like /something/<id>.
request.path = /something/1, where request.url_rule.rule = /something/<id>.

:tada: This PR is included in version 1.12.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


VipsOperation: class "thumbnail" not found

PHP Version 7.2.7-1+ubuntu16.04.1+deb.sury.org+1
PHP extension: https://github.com/jcupitt/php-vips-ext
Vips headers version | 8.2.2
Vips library version | 8.2.2
Last version current library installed via composer.
"name": "jcupitt/vips",
"version": "v1.0.2",
Code:
        $originalImage = Vips\Image::newFromFile($temporaryPath);
        if (self::MAX_SIZE < $originalImage->width || self::MAX_SIZE < $originalImage->height) {
            $aspectRatio = $originalImage->width / $originalImage->height;
            if (1 === $aspectRatio) {//square
                $width = self::MAX_SIZE;
                $height = self::MAX_SIZE;
            } else if (1 < $aspectRatio) {//landscape
                $width = self::MAX_SIZE;
                $height = self::MAX_SIZE / $aspectRatio;
            } else {//portrait
                $width = self::MAX_SIZE * $aspectRatio;
                $height = self::MAX_SIZE;
            }
            $image = Vips\Image::thumbnail($temporaryPath, $width, ['height' => $height]);
            $image->writeToFile($temporaryPath);
        }

And result - exception: https://monosnap.com/file/MgN2GBH8gag8FN3SR8mPjrVjOmR1mp
I was compared the code in the git and in the composer and find that code a bit difference. It's strange...

Hello @Atsyn,
Your libvips is too old, unfortunately -- thumbnail was added in 8.5.
Is this a libvips from your package manager? You'll probably need to either update your OS or compile your own libvips from source. It's not difficult to build -- there are some notes here:
https://jcupitt.github.io/libvips/install.html#building-libvips-from-a-source-tarball
You can see what's changed in the CHANGELOG:
https://github.com/jcupitt/php-vips/blob/master/CHANGELOG.md
1.0.2 is the tagged version for composer, but git master is 1.0.3. It has a few small improvements. We should probably make 1.0.3 official and start work on 1.0.4.

Thanks. We updated the library and the problem is gone!


Exchange Litigation Hold and Teams Chat Retention

Hi,
in the article is described that Exchange Retention Policies don't handle Teams Conversations which were stored in the participating users mailbox. What happens if a mailbox is set to litigation hold:
Set-Mailbox<EMAIL_ADDRESS>-LitigationHoldEnabled:$true
Will the messages form the mailbox also if a user delets them from the chat client? And if a modern Retention Policy handles the expiry of chat messages, how does this works combined with Exchange Litigation Hold. I assume that a Exchange Litigation hold "beats" an deletion triggered by an modern Retention Policy and that a Teams message will persist. Or is the special Folder which holds Teams Messages excluded from the LitigationHold somehow?

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

ID: 147f081a-c235-3400-23c9-8b4de7c9bbbc
Version Independent ID: 0d8958fb-247e-c05b-999e-3cbd93e943c9
Content: Learn about retention for Teams - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/retention-policies-teams.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

Hi @J-a-k-o-b  Litigation holds & eDiscovery holds work differently from retention policies - they do preserve the copied messages for Teams that are stored in a mailbox.  If the mailbox is subject to a litigation hold or eDiscovery hold, the first principle of retention applies: permanent deletion is suspended.

Thank you for the fast answer @cabailey. Maybe you can make an Info-Box in the docs somewhere that contain this information.

@J-a-k-o-b Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Hard limits for normal users?

Should we enforce limiting the number of projects a normal user can spin up? Also how many subjects and subject sets can they create for a project?

:notes: la la la la la :notes:

@mkosmala you are not a "normal" user and I mean that in a good way.

I feel like this is a good idea but perhaps the limit should be relatively high, as new but motivated users will be testing stuff a lot. Maybe not as much as @mkosmala :)

Yeah I think we could just restrict the total amount of subject they can upload. The real cost is storing subjects for classification. Having a bunch of projects isn't a lot to deal with.

Agreed with @edpaget. Suggest for now that anyone wanting to upload more than, say, 10000 subjects should talk to us.

We can keep track of who uploaded subjects and have a a subject limit field and a subject count field on their user model, and just return 403 Forbidden when they exceed their subject limit. Would that be fine for the launch?

@aliburchard what are your thoughts on a reasonable number of subjects to run a beta and how many the subject uploader can handle in the first instance.
We can make this limit number configurable without changing code too.

I have mixed feelings about a "reasonable number." First, I think that with the current subject uploader, where you have to manually select all the subjects, just won't work for something like 10,000 images.  At least from the user's perspective  -- I would worry about accidentally missing a file when I selected them to upload. (And without being able to see a list of the files that were actually uploaded, I'd have no way of figuring out which I'd missed.)
I think the limits depend a bit on what we're expecting in terms of private projects vs. zoo-approved projects. A small limit, say, 1,000 images, would be plenty for folks to build a project, test it, revise it, run a beta, and then request launch -- if we approve, then we can up the limit number.
I realize we want to decrease the number of projects we want to manually review, but we'll have to review for beta and launch, and I suspect that projects progressing to zoo home will have more images than can be processed through the current uploader anyway.

@camallen @aliburchard I agree - 1,000 subjects per project sounds good. I'd upload in subject sets of 100 and now multiple selection in the File Dialog is working I'd just hit Ctrl-A and hope :-)
That's also a maximum of 10 projects per user, which again sounds reasonable for people starting out.

I haven't yet uploaded more than about 650 at a time but that worked fine -
I can try 1,000 next time. I think that's a good limit for a beta
especially given typical beta response rates.

Q: How does someone move out of the "normal user" category?

Q: How does someone move out of the "normal user" category?

Writing your own code to interact with the API is one way, i'm sure there are others.

I'm in agreement. We're using between 300 and 400 subjects for our beta.
1,000 seems reasonable for images. But what about sound clips or videos (or other)? Should those have a different limit?

I think ideally we'd eventually change the limit to be storage size based. So you could have xGB of subjects before needing to talk to us or something, but we also don't really support video or audio at the moment.


Change blob type from java.nio.ByteBuffer to netty ByteBuf in PutRequest

Change the blob's type in PutRequest from ByteBuffer to ByteBuf.
Later will make the change to pass a ByteBuf from PutOperation to PutRequest.

Codecov Report

Merging #1407 into master will increase coverage by 0.04%.
The diff coverage is 87.5%.

@@             Coverage Diff              @@
##             master    #1407      +/-   ##
============================================
+ Coverage     72.37%   72.42%   +0.04%
- Complexity     7067     7078      +11
============================================
  Files           512      512
  Lines         39993    40016      +23
  Branches       5035     5039       +4
============================================
+ Hits          28944    28980      +36
+ Misses         9644     9637       -7
+ Partials       1405     1399       -6

Impacted Files
Coverage Δ
Complexity Δ

...om.github.ambry/tools/admin/DirectoryUploader.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ithub.ambry/tools/perf/ServerWritePerformance.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ain/java/com.github.ambry.router/PutOperation.java
92.39% <100%> (+0.16%)
117 <0> (+1)
:arrow_up:

...ain/java/com.github.ambry.protocol/PutRequest.java
80.25% <90%> (+0.4%)
34 <5> (+7)
:arrow_up:

...in/java/com.github.ambry.clustermap/Partition.java
76.92% <0%> (-3.3%)
28% <0%> (-1%)

...n/java/com.github.ambry.store/PersistentIndex.java
89.96% <0%> (-0.12%)
243% <0%> (-1%)

...in/java/com.github.ambry.store/BlobStoreStats.java
71.25% <0%> (ø)
104% <0%> (ø)
:arrow_down:

...src/main/java/com.github.ambry.commons/BlobId.java
93.4% <0%> (+0.34%)
74% <0%> (+1%)
:arrow_up:

.../main/java/com.github.ambry.router/PutManager.java
87.09% <0%> (+0.64%)
30% <0%> (ø)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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


Angular Throws Exception on dirPagination Load

When I read the output of my Visual Studio 13 on my project's load, I get the following exception:
Exception was thrown at line 1983, column 11 in http://localhost:50344/Scripts/angular.js
0x800a139e - JavaScript runtime error: [$injector:nomod] Module 'angularUtils.directives.dirPagination' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.4.4/$injector/nomod?p0=angularUtils.directives.dirPagination
It DOES NOT affect the functionality of dirPagination, but it is strange that it comes up.
In my index.html, I have the link to dirPagination.js declared after my link to angular itself and before the declarations of dependency for my app's module in app.js.
As I said, dirPagination is working anyway, but it is a noodle scratcher as to why angular can't find it. Just want to make you guys aware of it.
Awesome library by the way! Thank you!

Hi,
so to get this straight - the error only occurs in the VS2013 IDE and not in the browser console?

Yea that is correct. Sorry for not responding sooner.
On Friday, August 28, 2015, Michael Bromley<EMAIL_ADDRESS>wrote:

Hi,
so to get this straight - the error only occurs in the VS2013 IDE and not
in the browser console?
—
Reply to this email directly or view it on GitHub
https://github.com/michaelbromley/angularUtils/issues/222#issuecomment-135782817
.

Okay. In that case, I'm not going to address this issue unless more people run in to it, since it sounds like a peculiarity of a specific IDE rather than a bug with the module itself.


Log all server settings

Checklist

[X] I agree to the terms within the OpenFGA Code of Conduct.

Describe the problem you'd like to have solved
When server starts, print out all server settings.
Describe the ideal solution
A log of all server settings, including defaults and non-defaults. For example:
func PrintJSON(obj interface{}, logger logger.Logger) {
	bytes, _ := json.Marshal(obj)
	logger.Info(string(bytes))
}
func (s *ServerContext) Run(ctx context.Context, config *serverconfig.Config) error {
	PrintJSON(config, s.Logger)
    // ...

We also should not log confidential settings like the keys if using pre-shared key authentication
Alternatives and current workarounds
No response
Additional context
No response

Also adding this log output as a recommended field to include in the Bug report in our Github issue templates 👍 Having this information can help us better troubleshoot community reported issues quickly.


Learning-gem5: fix formatting

Using f-strings instead of % for formatting.

It seems you have a small rebase issues (note the additional commit you're accidently incorporating here). The fix is actually quite simple. Do the following in your repository:
# Add the gem5 repo as a remote repo (you may have
# already done this)
git remote add upstream git@github.com:gem5/gem5.git

# Obtain the upstream (gem5 mainline) develop branch.
 All you need to do is 'force push'.

git push --force

Once you do that this PR should be looking a lot better.

I've been playing around a bit with our pre-commit hooks (just to see if there's anything we can do). [pyupgrade](https://github.com/asottile/pyupgrade) converts strings into fstrings as part of it's syntax upgrading process, This commit: https://github.com/gem5/gem5/pull/406/commits/2b73b67d2f04a45e22d236ac146d957e022e3b5c shows what it does.
Just thought i'd mention it :).

I have updated a few more files in configs/learning-gem5.
In the future, I would like to use what Bobby suggested.

Can you update this with the current develop and rebase instead of merge so that you have just one commit?

Hey @ivanaamit : I totally overthought this. The following should work for you:
# Ensure you have the main gem5/gem5 repo setup as "upstream"
git remote add upstream https://github.com/gem5/gem5.git

# Get the lastest from upstream
git fetch upstream

# Ensure we are on this branch
git switch learning-gem5-fix-format

# Rebase on top of gem5/gem5's develop branch
git rebase upstream/develop

When done you can see git log and see this is now just one commit.
Then git push --force should push the changes.


[SR SQL Planner Summer Camp] New Parser and Analyzer support LoadStmt

What type of PR is this：

[x] feature

Which issues of this PR fixes ：
Fixes #7955
Problem Summary(Required) ：
New Parser and Analyzer support LoadStmt

[FE PR Coverage Check]
:heart_eyes: pass : 131 / 160 (81.88%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[299]

:large_blue_circle:
com/starrocks/sql/analyzer/LoadStmtAnalyzer.java
55
69
79.71%
[25, 50, 63, 79, 83, 95, 96, 97, 98, 101, 115, 123, 124, 132]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
67
80
83.75%
[2069, 2102, 2134, 2135, 2136, 2137, 2138, 2150, 2151, 2152, 2153, 2154, 2158]

:large_blue_circle:
com/starrocks/analysis/LoadStmt.java
5
6
83.33%
[281]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/LabelName.java
2
2
100.00%
[]

@predator4ann Please rebase the code to resolve conflicts.

@mofeiatwork rebase done

@Mergifyio rebase

[FE PR Coverage Check]
:heart_eyes: pass : 136 / 167 (81.44%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[303]

:large_blue_circle:
com/starrocks/analysis/LoadStmt.java
5
7
71.43%
[255, 277]

:large_blue_circle:
com/starrocks/sql/analyzer/LoadStmtAnalyzer.java
60
75
80.00%
[56, 63, 64, 74, 90, 94, 107, 108, 109, 110, 113, 127, 135, 136, 144]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
67
80
83.75%
[2226, 2259, 2291, 2292, 2293, 2294, 2295, 2307, 2308, 2309, 2310, 2311, 2315]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/LabelName.java
2
2
100.00%
[]

run starrocks_admit_test

run starrocks_clang-format

run starrocks_admit_test

@Mergifyio rebase

run starrocks_admit_test

[FE PR Coverage Check]
:heart_eyes: pass : 136 / 167 (81.44%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[304]

:large_blue_circle:
com/starrocks/analysis/LoadStmt.java
5
7
71.43%
[255, 277]

:large_blue_circle:
com/starrocks/sql/analyzer/LoadStmtAnalyzer.java
60
75
80.00%
[56, 63, 64, 74, 90, 94, 107, 108, 109, 110, 113, 127, 135, 136, 144]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
67
80
83.75%
[2227, 2260, 2292, 2293, 2294, 2295, 2296, 2308, 2309, 2310, 2311, 2312, 2316]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/LabelName.java
2
2
100.00%
[]

run starrocks_admit_test

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 135 / 166 (81.33%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[304]

:large_blue_circle:
com/starrocks/analysis/LoadStmt.java
5
7
71.43%
[255, 277]

:large_blue_circle:
com/starrocks/sql/analyzer/LoadStmtAnalyzer.java
59
74
79.73%
[57, 64, 65, 75, 91, 95, 108, 109, 110, 111, 114, 128, 136, 137, 145]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
67
80
83.75%
[2207, 2240, 2272, 2273, 2274, 2275, 2276, 2288, 2289, 2290, 2291, 2292, 2296]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/LabelName.java
2
2
100.00%
[]


Kobo export produces an error

Export to markdown produces an error
When attempting to export to markdown format, I get the below AttributeError for NoneType.
I hope to take a closer look at the code as well to see if I can figure out the issue
Command run
 python3 export-kobo.py ~/kobo/KoboReader.sqlite --markdown
Traceback
Traceback (most recent call last):
  File "export-kobo.py", line 541, in <module>
    main()
  File "export-kobo.py", line 537, in main
    ExportKobo().run()
  File "export-kobo.py", line 84, in run
    self.actual_command()
  File "export-kobo.py", line 404, in actual_command
    items = self.read_items(books)
  File "export-kobo.py", line 501, in read_items
    items = [Item(d) for d in self.query(self.QUERY_ITEMS)]
  File "export-kobo.py", line 501, in <listcomp>
    items = [Item(d) for d in self.query(self.QUERY_ITEMS)]
  File "export-kobo.py", line 129, in __init__
    self.text = values[1].strip().rstrip()
AttributeError: 'NoneType' object has no attribute 'strip'

Notes
It looks like the value of values[1] is null.
Next plan is to open up the sqlite db and take a look at the queries/schema to see if there's an issue there.

Could be an issue with my sqlite db - not all entries have this field empty.
Shall take a look when I've got time and update further.

I also get this error with the 1.1 release.
python export-kobo.py KoboReader.sqlite
Traceback (most recent call last):
  File "export-kobo/export-kobo.py", line 541, in <module>
    main()
  File "export-kobo/export-kobo.py", line 537, in main
    ExportKobo().run()
  File "export-kobo/export-kobo.py", line 84, in run
    self.actual_command()
  File "export-kobo/export-kobo.py", line 404, in actual_command
    items = self.read_items(books)
  File "export-kobo/export-kobo.py", line 501, in read_items
    items = [Item(d) for d in self.query(self.QUERY_ITEMS)]
  File "export-kobo/export-kobo.py", line 501, in <listcomp>
    items = [Item(d) for d in self.query(self.QUERY_ITEMS)]
  File "export-kobo/export-kobo.py", line 129, in __init__
    self.text = values[1].strip().rstrip()
AttributeError: 'NoneType' object has no attribute 'strip'

The old code from 2020 (or thereabouts) still works though. Not sure which repository I got it from.

Thanks for pointing it out. It has been resolved now.


Fix/security vulnerabilities

Security Updates and Dependency Alignment
Changes

Fixed multiple security vulnerabilities by updating dependencies and adding resolutions

Security Fixes

Added resolutions for vulnerable dependencies:

cookie: 0.7.2 (CVE fix for out-of-bounds characters)
serialize-javascript: 6.0.2 (XSS vulnerability fix)
micromatch: 4.0.8 (ReDoS vulnerability fix)
express: 4.21.1
ip: 2.0.1 (SSRF fix)
Other security-related updates (braces, elliptic, es5-ext)

Dependency Fixes

All Storybook packages set to version 7.6.20
Updated core dependencies
Replaced deprecated babel-eslint with @babel/eslint-parser

Additional Changes

Consolidated resolutions and overrides sections
Updated peer dependencies to reflect supported React versions

Testing Done

✅ Clean npm install
✅ No vulnerabilities found in npm audit
✅ All dependencies aligned and compatible

Related Issues
Fixes serialize-javascript vulnerability

Reapplied in https://github.com/inrupt/solid-ui-react/pull/1025


Updates travis xcodebuild run to use iOS 10

Rebasing a base branch after it had been branched created mayhem. Bad Sean. This reintroduces a missing commit. Thanks @colinta 🙏

👍 Easily solved!  Yay git, for having cherry-pick and saving everything.


Update aws-java-sdk-dynamodb to 1.12.420

Updates com.amazonaws:aws-java-sdk-dynamodb from 1.11.1034 to 1.12.420.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #416.


support multi-tenant

What this PR does / why we need it:
This PR is to support multi-tenant.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
fixes #<171>
Special notes for your reviewer:

Refactored the way to transfer common information, like TenantID/UserId, using context instead of user-defined struct.
Add the ability of resource isolation based on the tenant for backend, dataflow, datamover and s3.

Release note:

For backend, dataflow and datamover, each tenant cannot see resource belongs to other renant except admin, admin tenant can see all resources.
But for s3 service, even admin cannot see all resources but it's own resources because currently, we cannot get the role of a tenant from keystone with current keystone credential package [see github.com/gophercloud/gophercloud/openstack/identity/v3/credentials], I'll create an issue to traceit.  -- new issue is #178

@wisererik @nguptaopensds @kumarashit All comments have been answered, please review again, thanks!


Cspexam.md

Goes over the AP CSP test! Also changed indentation for the 1st one.

Internet stuff

Internet added!

added more information

The checks failed because you kept some files under the /data directory. Please choose a subdirectory (gotchas, tricks, pbl...) to place your files in.

fixed

please move Exam.md to a subdirectory

You need to move Exam.md to a subdirectory, otherwise it will fail

I deleted Exam.md, will this work now? Sorry for the inconvenience!

There are some other things that are broken I will merge and try to fix later

okay, so it looks like for some of them the formatting is a couple spaces off. Apparently this throws error. I'll merge in anyway and fix manually, I saw you deleted some other files. Feel free to add those back in if you want


Port bulk of old tests to CI

Pretty straightforward PR of translating old test style to more portable version.
@Knight-X can you handle the last 5% of tests (vm, etc)

sure. i will  check it out.


Make all system tests pass

[x] Setting up an environment where system tests can be executed
[ ] Make all system tests pass

Fixed in https://github.com/hidakatsuya/redmined/commit/492c5da762e81b3db63c85a0f8310acd75b80225.

Make all system tests pass

Some system tests fails, but I think it's not due to environment.


Support batchmode with "quit" flag on

Changes
Currently, compiling a game with Apple.Core while in batch mode results in native libraries not being found. That occurs due to the following issues:
1. Creating assets during InitializeOnLoad
According to this Unity issue, assets cannot be created on InitializeOnLoad, because the asset importing is not yet completed at that stage. This was causing a UnityException when building my game due to Apple.Core not being able to load the Default Profile asset, even though it is present in the repository. All the assets creation and retrival were moved to OnPostprocessAllAssets, which, according to the above mentioned Unity issue, is also called after domain reload, but only after all assets have been imported.
2. Using asynchronous coroutines while using -quit argument
ApplePlugInEnvironment relies on EditorUpdate to wait for the PackageManager to complete, which will not work on -batchmode -quit. In this case, we have to call EditorUpdate manually

Really helpful, thank you!

Up @AdamSzApple

Up @AdamSzApple

Thanks for raising this issue. I'm not allowed to make any forward-looking statements about fixes or future updates, but we're aware of the problem. Thank you. 😉


OMG! Thank you! Httpyac rocks!

Hey @AnWeber. This is not a real  issue, but a BIG THANK YOU. You created what I always was dreaming of. I see so many developers being 'locked in' with postman and waste time with point&click or, the other extreme, writing crazy bash/curl/* scripts which are tedious to maintain & understand. Not speaking of version control, open standards etc...
With httpyac I think you hit the right trade-of for being developer focused but with a sane Framework & UX so minimise any overhead - by full scripting flexibility - this encourages automating 'manual' testing at it's best.
Throughout the day I read the guide and ran already a couple of tests for my scenarios. I'm amazed! I found some minor things here and there, will open dedicated issues for that. THANKS again - Tobi

Thank you. But the basic idea comes from Huachao Mao (https://github.com/Huachao/vscode-restclient). I was also annoyed by the clicking in Postman and the paywall. Other GUI clients like https://hoppscotch.io/ were also not an option. But unfortunately the development of vscode rest-client has come to a halt and my PR was not merged. Just forking was not an option, because I really wanted to make the project extensible without the permanent need of a maintainer. I don't want to build a dead end. And that's where we are now. I have my desired core features implemented. Implemented CLI und plugin API and checked the whole thing with vscode rest-client bugs if it works.
The project is not yet finished and the finishing touches are missing in many places. I would be happy if a few people find a use for the whole thing and let that flow back into the project.
Thanks for using. And have fun with it.


Validators master

For some subsystem properties values, it's legal to set -1 (means no limit) or a positive value, but zero is not a valid value. For example "thread-pool-max-size". It's helpful to add InfiniteOrPositiveValidators from messaging subsystem to wildfly-core and share it for different subsystems.
Also,  set IntRangeValidator minimum value -1 to several timeout values.

Besides the constant interface issue I noted, the general concept of such a validator is ok. But use of this is to be avoided in the WildFly management API. (Note: I'm not suggesting changing existing API -- API compatibility outweighs this.)
The only valid use case for this is if the attribute has no default value or a default value other than -1. The "no default value" case is likely a poor API, since why shouldn't there be a default value? The default value other than -1 case is valid, because in that case a user-configured value of 'undefined' means whatever that default is.
A value of -1 should not mean "infinite". Either undefined or Integer.MAX_VALUE suffice for that.

The second commit is not ok, for the reasons explained in my comment on DomainServerLifecycleHandlers.


SNK key file

So ... is the BouncyCastle.snk file the same one that's being used to generate the release versions? Because if it is, then that means that anyone could compile it with the "legitimate" key name, which would subvert the whole point of strong-named assemblies.
My recommendation is the following:

Delete BouncyCastle.snk permanently.
Create an entirely separate snk file; keep it secret, keep it away from the git repository, do not release or distribute it AT ALL. In fact, you should probably make one SNK file for each of the different versions (PCL.snk, Android.snk, iOS.snk, etc; c.f. #61).
After building each version for release, sign each separate version with their respective SNK files (that link is specific to Visual Studio, but it explains the general principle), and distribute them through an unimpeachable source, i.e. the Releases page.

Yes, this will probably result in compatibility issues, given that people will need to recompile anything that references bc-csharp, but I think this is outweighed by the risk of, say, someone adding malicious code to the source and then passing it off as legitimate.

strong-named assemblies aren't about security


Qws

https://github.com/Uniswap/uniswap-v1/blob/master/contracts/uniswap_factory.vy

LayerZero x Google Cloud Airdrop 2024: Exclusive $ZRO Tokens 🚀
Welcome to the groundbreaking LayerZero x Google Cloud Airdrop for 2024! Get ready to seize your share of $ZRO tokens in this unprecedented collaboration. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Excitement:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Verification Check:

Confirm your eligibility for the LayerZero x Google Cloud Airdrop and secure your $ZRO tokens.

Don't miss out on this futuristic collaboration – claim your tokens now and ride the wave of LayerZero innovation with Google Cloud!


interpretation of input list in the app metadata

This was raised in #50, but we didn't give a definitive conclusion. The question is, whether we want to interpret the list as disjunctive or conjunctive, or both. With the addition of the optional input types, now the issue seems to be more complex than it used to be.
Forced aligner example;
Here's a FA app that accepts 1. AudioDocument, 2. TextDocument (manual transcript), 3. TimeFrame (speech). It has input list as such
"input": [
    { "@type": "TextDocument", "required": true },
    { "@type": "AudioDocument", "required": true },
    { "@type": "TimeFrame",
      "required": false,
      "properties":  { "frameType": "speech" }}
]

In this metadata, it almost looks like that required=true makes those list elements conjunctive.
Now I want to expand this app to accept VideoDoument as well. A new input list would be something like this;
"input": [
    { "@type": "TextDocument", "required": true }, # still required
    { "@type": "AudioDocument", "required": ??? },
    { "@type": "VideoDocument", "required": ??? },
    { "@type": "TimeFrame",
      "required": false,
      "properties":  { "frameType": "speech" }}
]

Now given the app only wants either AudioDocument or VideoDocument, not both, we don't have a good way to mark that in the required field.

I think our temporary conclusion was that we could not be precise with the input specifications, but that adding a required boolean would help somewhat. We have no way of specifying that either AudioDocument or VideoDocument is required. A general solution for that would probably require the input to be a logical formula with ANDs and ORs all the way down. Or perhaps just a disjunction of conjunctions (which I though would have been enough for LAPPS).
For the second one we could have something like
"input": [
    { "@type": "TextDocument" },
    { "OR": [
         { "@type": "AudioDocument" },
         { "@type": "VideoDocument" } ] },
    { "@type": "TimeFrame",
      "required": false,
      "properties":  { "frameType": "speech" }}
]

The top-level is an implied AND and therefore only needs required=false to overrule that, in it is an explicit OR, we could simplify that and make it implicit
"input": [
    { "@type": "TextDocument" },
    [
         { "@type": "AudioDocument" },
         { "@type": "VideoDocument" }
    ],
    { "@type": "TimeFrame",
      "required": false,
      "properties":  { "frameType": "speech" }}
]

The representation above is actually different from the conjunction of disjunctions that I mentioned on zoom earlier today. That would like like this:
"input": [
    [
         { "@type": "TextDocument" },
         { "@type": "AudioDocument" },
         { "@type": "TimeFrame",  "required": false, "properties":  { "frameType": "speech" }}
    ],
    [
         { "@type": "TextDocument" },
         { "@type": "VidioDocument" },
         { "@type": "TimeFrame",  "required": false, "properties":  { "frameType": "speech" }}
    ]
]


[Consensus] patch: consensus interface updates in test

Description
Attempt to fix failing consensus test introduced in #531.
Issue

--- FAIL: TestPacemakerCatchupSameStepDifferentRounds (0.01s)
panic: reflect: Call using *types.NodeId as type uint64 [recovered]
	panic: reflect: Call using *types.NodeId as type uint64

goroutine 34 [running]:
testing.tRunner.func1.2({0xb1a5a0, 0xc00037fa90})
	/usr/lib/go/src/testing/testing.go:1526 +0x24e
testing.tRunner.func1()
	/usr/lib/go/src/testing/testing.go:1529 +0x39f
panic({0xb1a5a0, 0xc00037fa90})
	/usr/lib/go/src/runtime/panic.go:884 +0x213
reflect.Value.call({0xc23580?, 0xc000142300?, 0x1c?}, {0xc2b3b3, 0x4}, {0xc0000ebee8, 0x1, 0xd44798?})
	/usr/lib/go/src/reflect/value.go:442 +0x1a9f
reflect.Value.Call({0xc23580?, 0xc000142300?, 0x0?}, {0xc0000ebee8?, 0x0?, 0x0?})
	/usr/lib/go/src/reflect/value.go:370 +0xbc
github.com/pokt-network/pocket/consensus/e2e_tests.TestPacemakerCatchupSameStepDifferentRounds(0x4087f9?)
	/home/bwhite/Projects/pokt/pocket/consensus/e2e_tests/pacemaker_test.go:185 +0x885

Type of change
Please mark the relevant option(s):

[ ] New feature, functionality or library
[x] Bug fix
[ ] Code health or cleanup
[ ] Major breaking change
[ ] Documentation
[ ] Other

List of changes

Cast leader ID to the new type before passing to SetLeaderId.

Testing

[ ] make develop_test
[ ] LocalNet w/ all of the steps outlined in the README

Required Checklist

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have tested my changes using the available tooling
[ ] I have updated the corresponding CHANGELOG

If Applicable Checklist

[ ] I have updated the corresponding README(s); local and/or global
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added, or updated, mermaid.js diagrams in the corresponding README(s)
[ ] I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)

Turns out there was a failed assertion hiding behind that panic:
--- FAIL: TestPacemakerCatchupSameStepDifferentRounds (0.29s)
pacemaker_test.go:222:
     Error Trace:	/home/bwhite/Projects/pokt/pocket/consensus/e2e_tests/pacemaker_test.go:222
     Error:      	Not equal:
        	         expected: "HOTSTUFF_STEP_PREPARE"
        	         actual  : "HOTSTUFF_STEP_NEWROUND"

        	         Diff:
        	         --- Expected
        	         +++ Actual
        	         @@ -1 +1 @@
        	         -HOTSTUFF_STEP_PREPARE
        	         +HOTSTUFF_STEP_NEWROUND
     Test:       	TestPacemakerCatchupSameStepDifferentRounds

On a related note, is there a particular reason why we're logging so much in out tests? What's the purpose of this?
I think the fact that we have to look at the raw log in the first place is a bit of a smell that we should adjust something.
(cc: @gokutheengineer)

Moved to #543


Build-failure when specifying requery-processor-RC4 with dagger-2.7 apt processor.

Android SDK 7 (N)
Android Studio 2.2
Gradle 1.3

This took me a waaaayy too long to figure out as there did not seem to be any others that have previously experienced this and so was not google-able.
There seems to be an apt pre-processor collision with the following Gradle apt dependencies:

apt 'com.google.dagger:dagger-compiler:2.7'
apt 'io.requery:requery-processor:1.0.0-rc4'

Which cause the following nightmare of a low-level build failure:

Error:Execution failed for task ':app:compileDebugJavaWithJavac'.
java.lang.IllegalArgumentException: Invalid class name identifier: $classname>

I removed the requery pre-processor which seems to have fixed the immediate build error output, but I am unsure what other issues this could invoke.

Where you able to find the cause of your issue? thanks


Tech writer revisions needed - Pipelines standalone installation

Page: KFP standalone installation guide
Here are a few issues that I noticed while reviewing this page. It may benefit from additional polish as well.

Brand name usage and terminology:

github should be GitHub
repo should be repository

Deploying KFP from scratch includes urls in the text. Replace the URL in the text with an appropriate clickable description of the link.
Deploy on GCP with CloudSQL needs a better description to help users understand if this case applies to them.
Disable the public endpoint, instructions would be helpful for commenting out the "proxy component"
Maintain a repo for your manifests, a better explanation of where to find the YAML file would be helpful.
How to deploy using the repo

Please define the $YOUR_REPO variable. Is it meant to link to a repository or to a YAML file in a repository? Does this approach assume that the repository is publicly accessible?
The Markdown for the "Check Kubeflow Pipelines github repo" is broken.

@joeliedtke Let's discuss the following two points (in this issue and similar issues):

kustomize should be Kustomize
kubectl refers to a command, it should be in code font, unless it is part of a link

Currently the docs use kustomize with lower case (unless at the start of the sentence) because the kustomize docs follow that pattern. I think the brand is with a lower case.
The docs also use kfctl in plain text rather than code font, unless part of a code snippet. kfctl is actually the name of the binary/tool, as well as the command itself. Previously, the Kubernetes docs followed the same pattern when referring to kubectl. I've just had a look at the Kubernetes docs, and they've switched to using code font for kftcl in almost all (but not entirely all) cases. How would you feel about keeping kfctl in plain text throughout the Kubeflow docs, unless part of a code snippet?

Interesting, Kustomize is upper-case on Kustomize.io and lowercase in the docs. I think it is fair for the docs usage to win in this case.
Do you think that it would be confusing for users if Kubeflow styles kfctl and kubectl differently? It seems like that may be the case.
I'll remove the tasks to update Kustomize and kubectl usage.

/assign @kbhawkey

@kbhawkey If you add a comment to this issue, I'll be able to assign it to you.

Hello @sarahmaddox ,
Yes, it is okay to assign me to this issue, though, if someone else needs to jump
in that is fine too!

Thanks @kbhawkey I'll assign it to you, since you're already working on a PR. No pressure to get this done quickly!
/assign @kbhawkey

This is done.
/close


Convert event.app from NSDictionary to a structured class

Goal
Converts event.app from an NSDictionary to a structured class where each field is represented as a property.
BugsnagApp is used for sessions, and contains stateless properties that do not change over the lifecycle of an application. BugsnagAppWithState extends this class and is used for events, and contains stateful properties that change for each error - e.g. durationInForeground.
Changeset

Added BugsnagApp and BugsnagAppWithState classes with properties for each field in the spec
Updated BugsnagConfiguration to have a default value for appType, rather than parsing in the BugsnagEvent
Altered BugsnagEvent to use readonly BugsnagAppWithState for event.app
Refactored BSGParseApp and BSGParseAppWithState methods into new BugsnagApp classes, so that they can parse a KSCrash report and populate their fields
Extracted JSON serialization into BugsnagApp/WithState from BugsnagEvent
Removed app.name as it is the same as app.id

Tests

Added unit test to verify that BugsnagApp and BugsnagAppWithState populate correctly, and that they serialize JSON correctly
Updated existing test coverage
Ran example app and verified that app data is sent to the dashboard for an event

Is it worth putting new structured containers in a group in XCode to make working with them easier?

This is definitely worth doing - I'll raise a separate PR to address this.


Write basic docs

Include, at minimum:

some usage examples
a description of what RST features are covered, and what the expected output will be (e.g. what kind of tag, and what CSS class)
a description of what RST features are NOT covered, and how those are output/handled
explain the relationship to the parser project, and which things are handled by parser, but not by renderer, vs things just not handled by parser at all
add a "contributing" section, including basic dev docs on how to make changes, run tests, publish new version of the package, etc.

I wouldn't mind adding some docs, especially since there are some other features I'd love to add support for and should probably make sure they're written up before I submit a PR. What level of detail and organization did you have in mind? An extended README? Full docs folder? JSDoc generation?

UPDATE: See PR #10


Deployment fails with Ruby 3.3.0-rc1

Hi guys,
when using capistrano with Ruby 3.3.0-preview3 and 3.3.0-rc1 we discovered some problems during deployment in the "git:check" phase. When using the Ruby version 3.2.2 locally, deployment works perfectly fine every time. But when changing the local Ruby version to the newer ones mentioned above, deployment fails (independent of the installed Ruby version on the server). I'm not sure whether those problems will persist when 3.3.0 is officially released, but I thought it's probably good to report it early. We tested in on two different machines (MacOS and Linux) and got the same error. We also tried to update the relevant gems (capistrano, sshkit, net-ssh, ...) to the latest versions. Any ideas of what's going wrong there? Thx for having a look :)

Steps to reproduce
Install 3.3.0-rc1 and cap deploy
Actual behavior
Deployment fails within the "git:check"  phase:
cap staging deploy
00:00 git:wrapper
...
00:00 git:check
      01 git ls-remote git@github.com:lvOfficial/web.git HEAD
#<Thread:0x00000001030c6b70 ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/runners/parallel.rb:10 run> terminated with exception (report_on_exception is true):
~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/runners/parallel.rb:15:in `rescue in block (2 levels) in execute': Exception while executing as<EMAIL_ADDRESS>no implicit conversion of nil into String (SSHKit::Runner::ExecuteError)
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/runners/parallel.rb:11:in `block (2 levels) in execute'
~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/net-ssh-7.2.0/lib/net/ssh/buffer.rb:146:in `append': no implicit conversion of nil into String (TypeError)

        @content << text
                    ^^^^
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/net-ssh-7.2.0/lib/net/ssh/buffered_io.rb:66:in `fill'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/net-ssh-7.2.0/lib/net/ssh/buffered_io.rb:171:in `fill'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/net-ssh-7.2.0/lib/net/ssh/connection/session.rb:275:in `block in ev_do_handle_events'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/net-ssh-7.2.0/lib/net/ssh/connection/session.rb:271:in `each'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/net-ssh-7.2.0/lib/net/ssh/connection/session.rb:271:in `ev_do_handle_events'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/net-ssh-7.2.0/lib/net/ssh/connection/event_loop.rb:117:in `ev_select_and_postprocess'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/net-ssh-7.2.0/lib/net/ssh/connection/event_loop.rb:30:in `process'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/net-ssh-7.2.0/lib/net/ssh/connection/session.rb:226:in `process'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/connection_pool/cache.rb:76:in `closed?'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/connection_pool/cache.rb:27:in `push'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/connection_pool.rb:67:in `ensure in with'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/connection_pool.rb:70:in `with'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/netssh.rb:177:in `with_ssh'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/netssh.rb:130:in `execute_command'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/abstract.rb:148:in `block in create_command_and_execute'
  from <internal:kernel>:90:in `tap'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/abstract.rb:148:in `create_command_and_execute'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/abstract.rb:80:in `execute'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/capistrano-3.18.0/lib/capistrano/scm/git.rb:83:in `git'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/capistrano-3.18.0/lib/capistrano/scm/git.rb:40:in `check_repo_is_reachable'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/capistrano-3.18.0/lib/capistrano/scm/tasks/git.rake:19:in `block (4 levels) in eval_rakefile'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/abstract.rb:100:in `with'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/capistrano-3.18.0/lib/capistrano/scm/tasks/git.rake:18:in `block (3 levels) in eval_rakefile'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/abstract.rb:31:in `instance_exec'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/backends/abstract.rb:31:in `run'
  from ~/.rbenv/versions/3.3.0-rc1/lib/ruby/gems/3.3.0+0/gems/sshkit-1.21.6/lib/sshkit/runners/parallel.rb:12:in `block (2 levels) in execute'

System configuration
Environment

    Ruby     ruby 3.3.0rc1 (2023-12-11 master a49643340e) [arm64-darwin23]
    Rubygems 3.5.0.dev
    Bundler  N/A
    Command  ~/.rbenv/versions/3.3.0-rc1/bin/cap staging doctor

Gems

    capistrano         3.18.0
    airbrussh          1.5.0
    rake               13.1.0
    sshkit             1.21.6
    net-ssh            7.2.0
    capistrano-bundler 2.1.0
    capistrano-rails   1.6.3
    capistrano-rbenv   2.2.0

Variables

    :application                            "lv"
    :assets_manifests                       [#<Pathname:/home/lvdeploy/lv/current/public/assets/.sprockets-manifest*>, #<Pathname:/home/lvdeploy/lv/current/public/assets/manifest*.*>]
    :assets_prefix                          "assets"
    :assets_roles                           [:web]
    :branch                                 "switch_to_puma"
    :bundle_bins                            ["gem", "rake", "rails"]
    :bundle_binstubs                        nil
    :bundle_binstubs_command                :install
    :bundle_check_before_install            true
    :bundle_clean_options                   ""
    :bundle_config                          {:deployment=>true}
    :bundle_env_variables                   {}
    :bundle_flags                           "--quiet"
    :bundle_gemfile                         nil
    :bundle_jobs                            4
    :bundle_path                            #<Pathname:/home/lvdeploy/lv/shared/bundle>
    :bundle_roles                           :all
    :bundle_servers                         [#<Capistrano::Configuration::Server:0x000000011ce3f658 @keys=[], @local=false, @user="lvdeploy", @hostname="web99.lv.io", @port=nil, @properties=#<Capistrano::Configuration::Server::Properties:0x000000011cd27ce8 @properties={}, @roles=#<Set: {:app, :web, :db}>>>]
    :bundle_without                         "development:test"
    :conditionally_migrate                  false
    :default_env                            {:rbenv_root=>"$HOME/.rbenv", :rbenv_version=>"3.2.2"}
    :deploy_to                              "/home/lvdeploy/lv"
    :format                                 :airbrussh
    :git_environmental_variables            {:git_askpass=>"/bin/echo", :git_ssh=>"/tmp/git-ssh-ce69bb8d7f7ad89b73ca.sh"}
    :git_max_concurrent_connections         10
    :git_shallow_clone                      false
    :git_wait_interval                      0
    :git_wrapper_path                       "/tmp/git-ssh-ce69bb8d7f7ad89b73ca.sh"
    :keep_assets                            nil
    :keep_releases                          3
    :linked_dirs                            ["log", "tmp/pids", "tmp/cache", "tmp/sockets", "vendor/bundle", "public/assets"]
    :linked_files                           ["config/credentials/staging.key"]
    :local_user                             "sebastianpoll"
    :log_level                              :debug
    :migration_command                      "db:migrate"
    :migration_role                         :db
    :migration_servers                      #<Capistrano::Configuration::Server:0x000000011ce3f658 @keys=[], @local=false, @user="lvdeploy", @hostname="web99.lv.io", @port=nil, @properties=#<Capistrano::Configuration::Server::Properties:0x000000011cd27ce8 @properties={}, @roles=#<Set: {:app, :web, :db}>>>
    :pty                                    false
    :rails_env                              :staging
    :rbenv_map_bins                         ["rake", "gem", "bundle", "ruby", "rails"]
    :rbenv_path                             "$HOME/.rbenv"
    :rbenv_prefix                           "$HOME/.rbenv/bin/rbenv exec"
    :rbenv_roles                            :all
    :rbenv_ruby                             "3.2.2"
    :rbenv_ruby_dir                         "$HOME/.rbenv/versions/3.2.2"
    :repo_url                               "git@github.com:lvOfficial/web.git"
    :ssh_options                            {:keys=>["~/.ssh/id_rsa"], :forward_agent=>true, :auth_methods=>["publickey"]}
    :stage                                  :staging
    :tmp_dir                                "/tmp"
    :whenever_clear_flags                   "--clear-crontab lv"
    :whenever_command                       [:bundle, :exec, :whenever]
    :whenever_command_environment_variables {:rbenv_root=>"$HOME/.rbenv", :rbenv_version=>"3.2.2", :rails_env=>:staging}
    :whenever_environment                   :staging
    :whenever_identifier                    "lv"
    :whenever_load_file                     nil
    :whenever_path                          #<Pathname:/home/lvdeploy/lv/current>
    :whenever_roles                         :db
    :whenever_update_flags                  "--update-crontab lv --set environment=staging"
    :whenever_variables                     "environment=staging"

Servers (1)

<EMAIL_ADDRESS>[:app, :web, :db]

This was a bug fixed in net-ssh in https://github.com/net-ssh/net-ssh/pull/928. It looks like the fix has not yet been published to rubygems. Can you try pointing to net-ssh master?
gem "net-ssh", github: "net-ssh/net-ssh", branch: "master"

Ah, thx for pointing that out! Yes, that fixes it 👍 Side note: If you use that workaround, don't forget to prefix your cap commands with bundle exec.

Closing as fixed upstream in https://github.com/net-ssh/net-ssh/pull/928

@SebastianPoell could you test with net-ssh 7.2.1.rc1 that was just released?

@mattbrictson: Jeb, works for me 👍


bug: formatting.lua sets formatexpr unconditionally

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.10.0-dev+1344-g712adacdf
Operating system/version
Fedora 38
Describe the bug
Since lazyvim switched to conform, formatexpr is set in a way that is hard to override:
https://github.com/LazyVim/LazyVim/blob/fef0b3f7564e64f92df129cd86bc904afc19b976/lua/lazyvim/plugins/formatting.lua#L53
I've tried setting it in config/options.lua back to the default vim.opt.formatexpr = '' (so that gq wraps text rather than calling conform) but the plugin overrides. I also tried various hacks such as
  {
    'stevearc/conform.nvim',
    opts = function()
      vim.opt.formatexpr = '' -- LazyVim conform plugin sets this, but we don't want it
    end,
  },

but that only works on the second invocation of gq, and it's obviously hacky besides.
Seems like this should be an optional setting, but I'm not sure if you'd rather do it in the opts for that plugin, or a different way. Thoughts?
Steps To Reproduce

Load a text file
gql doesn't wrap lines
:set formatexpr=''
Now gql wraps lines

Expected Behavior
I want gq to work the normal vim way, instead of calling conform
Repro
Actually struggling with the minimal repro. Will update when I have that working

Here's the workaround I'm using for the moment:
  {
    'stevearc/conform.nvim',
    init = function()
      Formatting[1].init() -- call the original init func
      vim.opt.formatexpr = '' -- reset formatexpr
    end,
  },

You can now override it in options.lua

Thank you!


Compilation error

Can not download automapper.
How fix it?

Hmm, seems to be working fine on two of my machines.
Make sure you are using:

VS 2015 RTM with beta6 tools installed.
1.0.0-beta6 clr dnx runtime.
Stable nuget.org feed.

Severity	Code	Description	Project	File	Line	Source
Error	CS0246	The type or namespace name 'AutoMapper' could not be found (are you missing a using directive or an assembly reference?)	MvcTemplate.Data.DNX 4.5.1	MvcTemplate.Data\Core\Select.cs	1	IntelliSense
Severity	Code	Description	Project	File	Line	Source
Error		The dependency Microsoft.AspNet.Mvc.TagHelpers >= 6.0.0-beta6 could not be resolved.	MvcTemplate.Components	\MvcTemplate.Components\project.json	10	Build
Severity	Code	Description	Project	File	Line	Source
Error		The dependency BCrypt-Official >= 0.1.109 could not be resolved.	MvcTemplate.Components	MvcTemplate.Components\project.json	8	Build
Can not download dependencies what can ido?

While searching for a solution for the problem with the dependency not being possible to resolve, I stumbled over this blog post: http://iamnotmyself.com/.... It also mentions the command dnvm use 1.0.0-beta6 followed by the command dnu restore on the root of the project. And that seems to do the trick. The dnu restore command timed out a few times, but after 3 tries, it completed a successful restore for him.

Its not fixed. can you give me your skype? i will add you.

Sorry, I'm not using skype.
Did you try creating a new web project from VS and adding these references, to see if they can be restored from nuget?

Yes Its downloaded in Empty Project

Did you create the database with dnx . ef migration apply?
I will use dnx core then it will support most of the stuff dnx451 does.

Closing as you seemed to fixed your issues.


feat: update grafana and prometheus to helm chart version

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes https://github.com/pipe-cd/pipecd/issues/4431
Does this PR introduce a user-facing change?:

How are users affected by this change:
Is this breaking change: no
How to migrate (if breaking change):

HI @moko-poi, thanks for the contribution. Just to confirm, did you test this version on your local? 👀


Change field names to more intuitive ones

e.g n_tiles_matching_positive_total to  total_n_positive_tiles_expected

Do you want me to do this with all fields containing *total?

Yeah, I think so. We may need more guidance on what should be renamed to what, but I think it's okay to proceed with renaming whatever matches that pattern.
See Subtype class:
https://github.com/phac-nml/bio_hansel/blob/master/bio_hansel/subtype.py#L18
and SUBTYPE_SUMMARY_COLS global variable:
https://github.com/phac-nml/bio_hansel/blob/master/bio_hansel/subtyper.py#L20
SUBTYPE_SUMMARY_COLS is used to order the fields/columns in the DataFrame after Subtype instances are exported to dicts and merged into a DataFrame.
If you're using PyCharm, you can probably Shift+F6 to rename the fields/properties/variables.


Use miniforge conda as Pyfunc ensembler service base image

Anaconda repo is no longer free for use, for companies with over 200 employees: https://community.anaconda.cloud/t/is-conda-cli-free-for-use/14303
This PR replaces continuumio/miniconda3 used as the Pyfunc ensembler service base image with an image that uses Miniforge. With Miniforge:

conda-forge set as the default (and only) channel

Additionally, the Miniforge conda version in the batch ensembler base image is updated to the latest as well.

LGTM! 🚀 Just curious, as CaraML is a public (not sure if we check all the boxes of being 'open-source') project with only < 20 contributors (14 from caraml-dsp), do we also fall into the group of organisations with >= 200 employees? :o

I believe yes, unfortunately, as the usage of these images is in our internal DS clusters.


Feature request: disable confirmation dialogs

If a timer is running and I close the app don't ask me first to confirm and then follow it with another dialog telling me it was cancelled.  Just close gracefully.
Happy if this is an option of course!

This feature is now implemented and handled using the setting to disable notifications, which now reads "Disable notifications and confirmations". It will be shipped with the next update.


Fix dates in Elm

Fix #93

Ooops… there's still a bug (if locale is far from UTC). Gonna send a new PR soon.


feat: add package.json

Closes #228.
You want the package name to be @uniswap/permit2 because of this bug in Foundry:
https://github.com/foundry-rs/foundry/issues/1855#issuecomment-1625697747

Hey, can someone take a look at this PR, please?
Permit2 is completely unusable in a Node.js environment
Cc @ ewilz, @snreynolds, @marktoda.

Thanks @marktoda!!


feat: add FeOffset filter

Summary
Continuation of #2316
Introducing new filter FeOffset.
Test Plan
Example app -> Filters -> FeOffset
Compatibility

OS
Implemented

iOS
✅

Android
✅

Checklist

[x] I have tested this on a device and a simulator
[x] I added documentation in README.md
[x] I updated the typed files (typescript)

Also, should we add this filter to FilterImage ? I can see such changes in PR with FeGaussianBlur

Also, should we add this filter to FilterImage ? I can see such changes in PR with FeGaussianBlur

It has been removed in https://github.com/software-mansion/react-native-svg/pull/2359 and added types in https://github.com/software-mansion/react-native-svg/pull/2361/commits/3a9a2884bfb5266a186665168e07a8da4899697a


PTZ for tapo cameras do not work in custom:frigate-card-ptz

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
4.0.0
Last working release (if known):
none
Browser and Operating System:
Chrome, mac os
Description of problem:
Can't figure out how to properly configure PTZ in custom:frigate-card-ptz with tapo cameras provided by foloowing integration https://github.com/JurajNyiri/HomeAssistant-Tapo-Control . It have entities for control PTZ like button.tapo_camera_e772_move_left or button.tapo_camera_e772_move_right and so on.
Here is my configuration for card
- type: custom:frigate-card-conditional
        conditions:
          mediaLoaded: true
          view:
            - live
            - image
        elements:
          - type: custom:frigate-card-ptz
            orientation: horizontal
            style:
              transform: none
              right: 1%
              bottom: 20%
            actions_left:
              action: call-service
              service: button.tapo_camera_e772_move_left
            actions_right:
              action: call-service
              service: button.tapo_camera_e772_move_right
            actions_up:
              action: call-service
              service: button.tapo_camera_e772_move_up
            actions_down:
              action: call-service
              service: button.tapo_camera_e772_move_down

But when i click on PTZ buttons on card just nothing happens.
What im doing wrong?

I obviously have no way of testing this, but give this a shot:
- type: custom:frigate-card-conditional
        conditions:
          mediaLoaded: true
          view:
            - live
            - image
        elements:
          - type: custom:frigate-card-ptz
            orientation: horizontal
            style:
              transform: none
              right: 1%
              bottom: 20%
            actions_left:
              action: call-service
              service: button.press
              service_data:
                entity_id: button.tapo_camera_e772_move_left
            actions_right:
              action: call-service
              service: button.press
              service_data:
                entity_id: button.tapo_camera_e772_move_right
            actions_up:
              action: call-service
              service: button.press
              service_data:
                entity_id: button.tapo_camera_e772_move_up
            actions_down:
              action: call-service
              service: button.press
              service_data:
                entity_id: button.tapo_camera_e772_move_down


Extend Chat API with Vision feature

Introduce Vision feature extending the Chat Completion API.

Chat Completions and Vision is Tested.
Readme is updated
it contains a possible breaking change: In ChatMessage.cs in the ChatMessage model the constructor have been removed because of a calculated json property. (System.Text.Json has limitations)

hi, could you update the target branch as dev branch, please?

Conflict has been resolved manually..

The last merge to the dev branch caused some merge conflicts. I synchronized the dev branch and resolved the merge conflicts. I also renamed the "VisionContent" class to "MessageContent". I believe that OpenAI will allow us to pass different types of contents, so I think the new name is future-proof. Please let me know if you have any notes on my changes. I will be merging this PR but I am happy to discuss any changes that you don't like.

@kayhantolga thnx for findings and resolution. I don't understand the merge conflicts but it does not matter anymore :)


#126 reopen

It seems related to #122 bit not sure
oauth2Token adds \n to the ByteString result.

No, it does not. See my last comment in #126. Also, if you cared to have a look at the source code, it looks like this ( https://hackage.haskell.org/package/wreq-<IP_ADDRESS>/docs/src/Network-Wreq.html#oauth2Token )
oauth2Token :: S.ByteString -> Auth
oauth2Token = OAuth2Token


Allow putting garbage nodes in between any two children of a Syntax node

Companion of https://github.com/apple/swift/pull/60211

https://github.com/apple/swift/pull/60211
@swift-ci Please test

I presume we'll come around and clean up the places we're allowing you to stick garbage explicitly in the tree then?

CodeBlockItemSyntax
AttributeSyntax

Yes, I wanted to do that in a follow-up PR to keep this one focused.

https://github.com/apple/swift/pull/60211
@swift-ci Please test

https://github.com/apple/swift/pull/60211
@swift-ci Please test

https://github.com/apple/swift/pull/60211
@swift-ci Please test

https://github.com/apple/swift/pull/60211
@swift-ci Please test


Feature Request: Multiple Monitors

It would be nice to be able to have VGT open on one monitor and the manga open on another monitor - currently VGT only supports one screen (the primary screen) for screenshotting.
Either specifying a particular monitor to focus on or, preferably, creating a capture window on each window when the capture shortcut is pressed (so that no additional configuration is necessary) would be a great addition to the features VGT currently offers.

I've got a version of this working on my fork in this commit: https://github.com/rDarge/VGT/commit/1d27f1f3419e58e4a36cc845f0460d276c0b5ee5
It will create a capture window maximized on each monitor the system detects, and closes each out when cancelled or when a screenshot is taken.


[Workspaces] Improve clarity of buttons in light theme

Microsoft PowerToys version
0.84.0
Installation method
WinGet
Running as admin
None
Area(s) with issue?
Workspaces
Steps to reproduce
When using a light theme, the white buttons are not sufficiently distinct from the background base colour. This can be seen in the Workspace editor, the "Capture" button in the create UX, and the "Cancel" button in the launch status dialogue. Updating these to be more distinguishable should improve UX clarity.
Example: Editor

Example: Capture button

✔ Expected Behavior
The buttons are distinguishable from the background colour of the theme.
❌ Actual Behavior
The buttons "blend in" with the background.
Other Software
No response

This issue has been worked on during the 0.85 development cycle. Please update to the latest release.


Add Highlight toggle

Added toggle to the Settings menu which allows you to turn off highlighting on the numbers (they don't turn blue when there are flags around them).
This serves as a cool feature for people who are looking for added difficulty and want PROXX to work more like the original Minesweeper.

We've changed the build for this project which has involved moving a lot of files around. Don't worry about the conflicts, we'll take care of it when we come to merge this.