The term 'Import-PodeSnapIn' is not recognized when running pode as a windows service with nssm.

Describe the Bug
When I try to run my pode webservice as a windows service with nssm, I get the following error:
Import-PodeSnapIn -Name 'Microsoft.Exchange.Management.PowerShell .
~~~~~~~~~~~~~~~~~
The term 'Import-PodeSnapIn' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.

It works well using pode start.
Steps To Reproduce

Create the server.ps1:

Start-PodeServer -Threads 1 {
    $config = Get-PodeConfig

    Import-PodeSnapIn -Name 'Microsoft.Exchange.Management.PowerShell.SnapIn'

    Add-PodeEndpoint -Address "servername.com" -Port 8666 -Protocol Https -Certificate $config.certificateName
}

Install the server as a service (installService.ps1):

$service = Import-PowerShellDataFile ($PSScriptRoot + "\config\service.psd1")

$exe = (Get-Command powershell.exe).Source
$name = $service.name
$file = $PSScriptRoot + '\server.ps1'
$logFile = $PSScriptRoot + '\logs\server.log'
$arg = "-ExecutionPolicy Bypass -NoProfile -Command `"$($file)`""

nssm install $name $exe $arg
nssm set $name AppStdout $logFile
nssm start $name

See the error in the logfile logs/server.log:

Import-PodeSnapIn -Name 'Microsoft.Exchange.Management.PowerShell .
~~~~~~~~~~~~~~~~~
The term 'Import-PodeSnapIn' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.

Expected Behavior
I would expect the webservice to run without any error, since it works well using pode start in a fresh powershell (without adding any snap-in before).
Platform

OS: Microsoft Windows Server 2016 Standard
Browser: none
Versions:

Pode: 1.8.1
PowerShell: 5.1.14393.3471

Hi @KuenzelIT,
I think I can see why this is happening, Import-PodeSnapIn appears to not be in the FunctionsToExport list.
I can get this fixed; for now you should be able to use Import-Module -Name Pode at the top of your server.ps1, and that should expose the function.

Thanks for the quick response!
I tested it using Import-Module -Name Pode but that does not seem to help. I'm still getting the same error message.

Gah, sometimes it works as a quick fix! 😂
I managed to work it out anyway, and it is because it was missing in the module's FunctionsToExport. The reason pode start works is because the file at that point is invoked within Pode, so it would have seen all functions. The moment you try to invoke the script externally, it relies on the exported functions; causing the error.
I'll get this out as a 1.8.2.

Thank you for the super fast support und fix!

You're welcome! 😄
This has been released in v1.8.2 now


Action handler must not trigger UIKit animations

When UIKit becomes a side-technology, the action handler must not trigger any such animations. Instead, it should be up to the button.

This has been moved to the button in v4.0.


Reference authorizations don't cleanly support tags

What happened?
With the expectation that a reference authorization is for merging commits, we don't currently support tags very well. I propose we bump the predicate to v0.2 and update how we apply its contents.
When the target ref is a tags ref: from -> zero/empty, target -> underlying commit the tag points to
When the target ref is a non-tags ref: from -> previous commit for the ref / zero (if approving for a new ref), target -> underlying Git tree
While refs / tags can point to any Git objects, I think we're safe in that attestations are likely to be used for:
a) branches to move from one commit to another
b) tag refs that point to tag objects that point to commit objects
We could be flexible for what the tag object points to, possibly, but I think on the first, we should expect commits (and therefore use trees for the target in the attestation).
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I don't know if we support lightweight tags today fwiw. I think we expect tag objects at several points for refs/tags in our verification flow.


Vendoring and secondary disk configuration option

My original intent was only to add an option to be able to use a secondary disk, however I was unable to build the projekt due to type inconsistencies caused by packer vendoring. So I followed the packer way of vendoring using Godep and replaced the ssh package as well to be able to build the binary.
The secondary disk config addition is a bit dumb, please advise me if you would like to see this a bit more sophisticated.
Sorry for the gofmt noise in the diffs, I hope it is still readable.

Fixed here https://github.com/watson-platform/packer-builder-softlayer, can you rebase and pull against that repo?

yes, thanks


Fixing Social Media Icons

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!
Providing the issue number/url helps us identify the problem being solved and keep the issues tab clean and tidy

What issue does this fix?
Summarize what this PR fixes:-
The Social Media Icons where not visible when changed to dark mode. This PR fixes that issue.
What issue is it attached to?
Fixes #219
Checklist
(Add an x between the brackets to check the items)

[x ] I have summarize what this PR fixes above
[ x] I have provided the issue ID/URL above
[ x] I have not added Bootstrap or jQuery and used correct styling guide.
[ x] This PR fixes only the issue mentioned above (create separate PRs for separate issues)
[ x] I was the first one to claim the issue or I created the issue

Even in light mode it Social Media icons are jumping...

I can fix those.

This is an older issue and the styles are not consistent with the new mockup. Try creating a new issue if the problem still occurs and resubmit.

This is an older issue and the styles are not consistent with the new mockup. Try creating a new issue if the problem still occurs and resubmit.

Can you tell me where I can find the new mockup?


[Doc] Update Import_and_query.md

missing SQL to use the correct database before inserting.
What type of PR is this：

[ ] Doc

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

Thank you @alberttwong for your contribution.


tcp health check does not need keepalive

making tcp health check be "keepalive" is buggy if backend server crashes quietly

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Wang Xinyong seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

Actually tcp health check should not use "check_keepalive_requests" feature.
The "check_keepalive_requests" should be only used for http protocol.
BTW, original pr https://github.com/alibaba/tengine/pull/321 has a case for testing "check_keepalive_requests" in tcp protocol. But it makes no sense.
Could you sign the  Contributor License Agreement? Then we'll merge this patch.

Thanks, merged!


Travis CI: log length has exceeded the limit of 4 MB

I think they've changed terminal session parameters, log seems to be overflooded by repeating interactive messages (like progress output) even from things like git clone which Travis does on its own.
Example: https://api.travis-ci.org/v3/job/340900769/log.txt
However we still should reduce output of things like apt-get, Android SDK installation and so on.

Closed by #191.


🐛: Email verification status does not change in profile view after verification

Contact Details
No response
What happened?
After successful email verification on the website, email status in the profile page does not change from unverified

Expected behavior
Email status should change to verified
Your Environment
Fedora 38
Steps to Reproduce the Behavior
sign up with a new email address,
verify email address
Relevant log output
No response
Additional Context
Another API call to the backend to fetch user data after verification may solve the problem
Code of Conduct

[X] I agree to follow this project's Code of Conduct

In response to the suggestion in the "Additional Context" section, maybe user data can be included in the payload on successful verification as well?
What do you think about that? @Olatisunkanmi

Thanks, @Olatisunkanmi @tobisupreme
These issues will be looked into.


support marks on element nodes

https://github.com/yjs/y-prosemirror/issues/47

An alternative serialization method might be to just use setAttribute('marks', node.marks) to distinguish between attrs and marks. This would also allow marksto retain its expected properties of being an array (which help with https://github.com/yjs/y-prosemirror/pull/52), and we wouldn't also have to rely onschemato tell if something is amarkorattrs`.


NoMethodError when using summary metric without labels

When I observe a PrometheusExporter::Metric::Summary without passing any label, I get a NoMethodError: undefined method merge' for nil:NilClass` when scraping the metrics
[2018-02-16 09:12:59] ERROR NoMethodError: undefined method `merge' for nil:NilClass
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/metric/summary.rb:57:in `block (2 levels) in metric_text'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/metric/summary.rb:56:in `each'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/metric/summary.rb:56:in `block in metric_text'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/metric/summary.rb:53:in `each'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/metric/summary.rb:53:in `metric_text'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/metric/base.rb:61:in `to_prometheus_text'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/server/collector.rb:55:in `map'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/server/collector.rb:55:in `block in prometheus_metrics_text'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/server/collector.rb:53:in `synchronize'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/server/collector.rb:53:in `prometheus_metrics_text'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/server/web_server.rb:117:in `block in metrics'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/timeout.rb:33:in `catch'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/timeout.rb:33:in `catch'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/server/web_server.rb:116:in `metrics'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/prometheus_exporter-0.1.13/lib/prometheus_exporter/server/web_server.rb:54:in `block in initialize'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/webrick/httpservlet/prochandler.rb:39:in `do_GET'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/webrick/httpservlet/abstract.rb:107:in `service'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run'
        /home/siebert/.rbenv/versions/2.3.1/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread'
::1 - - [16/Feb/2018:09:12:59 CET] "GET /metrics HTTP/1.1" 500 321

When I observe passing labels, everything works fine!

ok should be fixed and released!


Add denoland/deno:bin image

This simplifies the build process, and also users who want to install deno in their own base images. This pattern is also followed by the Docker Buildx: https://hub.docker.com/r/docker/buildx-bin
For now, some additional complexities were added to the ci.yaml (the entire build-ci) stage. But I plan to also propose a simplification in another PR using the Docker Bake Action and Docker Metadata Action, thus allowing we to build everything in a single job.
Plus, some additional changes were made:

Format Dockerfiles to use 2 spaces as indent delimiter
Format ci.yaml with vscode-yaml

This seems like two independent changes:

bin release that just exposes the binary (and other dockerfiles copy from that)

This seems more complicated to me. Creates an additional dependency that didn't exist before. Also worth noting the binary won't work with (vanilla) alpine / some other base images. I think buildx pattern might make more sense when the build is more complex than a single "download via curl" step.

using ARG instead of ENV for deno version

There has been some discussion of this in the past but I don't recall a compelling argument being made (also, there was a competing deno docker image which used that but it was less popular).
Perhaps I am missing something...

bin release that just exposes the binary (and other dockerfiles copy from that)

This seems more complicated to me. Creates an additional dependency that didn't exist before. Also worth noting the binary won't work with (vanilla) alpine / some other base images. I think buildx pattern might make more sense when the build is more complex than a single "download via curl" step.

Indeed, having to call docker build twice is not better than before. But:

You don't have to call it twice if you are just playing with the distros based Dockerfiles (as long as denoland/deno:bin was already pushed to Docker Hub once).

I forgot to add to the PR description this link: https://github.com/docker/buildx/tree/master#from-dockerfile

Regarding not working with vanilla alpine images, that's not something that can be solved at our side, but only in the main project -- perhaps publishing an additional deno binary with the rest of the dependencies statically compiled. What we can do is to document the requirements for an alpine image to use it.

Ultimately, the entire build process can be further optimized by collapsing all the Dockerfiles into a single one -- leveraging docker multi staged builds, and a bit of Bake perhaps. See https://github.com/denoland/deno/pull/11827 as an inspiration. That way, docker will resolve (and build -- leveraging build cache) the dependencies for each target without having to call multiple docker builds.

using ARG instead of ENV for deno version

There has been some discussion of this in the past but I don't recall a compelling argument being made (also, there was a competing deno docker image which used that but it was less popular).

Oh, I just used it in the bin.dockerfile and not in the final image (which still is an ENV). The ARG here is only used to prevent having to hardcode the DENO_VERSION=1.13.2 in multiple stages. At the end, the ARG is converted to an ENV, so there are no breaking changes here.

My recommendation is to publish something on docker hub to play with... That way the community can play with it - and give some feedback. Personally I don't feel qualified/confident in best practices here... and would just go with the simpler solution. 🤷 (Note: I am not a maintainer anymore so not up to me.)
RE the deno PR, similar advice, I suspect they'll be some push back against a new top-level file (let alone several), also - more importantly - deno is already a very complex build matrix (and carefully optimised/cached for performance). My suspicion is a better way could be to create a new repo which includes deno as a submodule and build from that.... In that way you could create version binaries (or daily, similar to how daily deno binaries were built by the community)... this could be a route to something like that being included in mainline deno (as happened with daily deno binaries).

I was also worried about Alpine, but having tested it locally it does seem to work properly since the Alpine image is still based off of frolvlad/alpine-glibc.

Sorry, that was related to the README instruction to include the binary in your own image. I think that may lead to confused users.

in addition to those I'd say I would prefer calling this image scratch instead of bin

If we do that, we could have FROM scratch as last stage (that just copies the binary from the top layer).

in addition to those I'd say I would prefer calling this image scratch instead of bin

If we do that, we could have FROM scratch as last stage (that just copies the binary from the top layer).

Regarding the name of the image, the only example that I found was docker/buildx-bin. The convention about using the base image name as the tag (if base is ubuntu, tag is ubuntu) makes sense, but I don't know at which extent the scratch can be considered a base image. :)

in addition to those I'd say I would prefer calling this image scratch instead of bin

If we do that, we could have FROM scratch as last stage (that just copies the binary from the top layer).

Regarding the name of the image, the only example that I found was docker/buildx-bin. The convention about using the base image name as the tag (if base is ubuntu, tag is ubuntu) makes sense, but I don't know at which extent the scratch can be considered a base image. :)

I think Andy was saying that the bin image should use FROM scratch as the last build stage, but it's already doing that.

I think Andy was saying that the bin image should use FROM scratch as the last build stage, but it's already doing that.

Yes! Oops.

So I thought a bit more about this change over the day; I'm in favor of adding this bare Docker layer and even publish it as a scratch image -- I think it can be pretty useful, makes the other images slightly nicer and makes it so we only have one canonical script to download the artifact. Really the only two blockers for me are:

Removing the dependency on buildx as I don't think it's needed (unless I'm missing something?)
Making the base image for the download stage something more mainstream like Debian or Ubuntu

@wperron Great, I will work on these points.

@wperron Done.

I used alpine to download because downloading is a very straightforward operation so I just wanted to make it as fast as possible. But I do use Ubuntu for everything otherwise here as well. :)
I'm not sure if build-push-action will work without setup-buildx, we would need to trigger a run in the CI.

https://github.com/felipecrs/deno_docker/actions/runs/1164191039
@wperron CI is passing finally. I switch from ubuntu-latest-xl to ubuntu-latest for testing here. Should I switch back to ubuntu-latest-xl? Using a custom runner makes it a bit more difficult for contributors to test their changes, as the CI will not be able to assign a runner in their fork. And I don't know what are the specific needs that ubuntu-latest-xl solves...

https://github.com/felipecrs/deno_docker/actions/runs/1164191039
@wperron CI is passing finally. I switch from ubuntu-latest-xl to ubuntu-latest for testing here. Should I switch back to ubuntu-latest-xl? Using a custom runner makes it a bit more difficult for contributors to test their changes, as the CI will not be able to assign a runner in their fork. And I don't know what are the specific needs that ubuntu-latest-xl solves...

Please do; they run much faster than the regular runner. I agree it's a bit of a bummer when developing on a fork only, but it works as soon as you have a PR open. You can always open PRs as draft in the future, they usually stay unreviewed when in that state.

I just did @wperron.


Change InputManager event handling to _input

Should allow _gui_input to work (#38) and also allow more flexibility in how to handle events.
Related documentation: https://docs.godotengine.org/en/stable/tutorials/inputs/inputevent.html#how-does-it-work

I had to make the same change in my project. What was the reasoning behind making it use _unhandled_input()?


DisplayInformation properties on Android and iOS

GitHub Issue (If applicable): #385
PR Type
What kind of change does this PR introduce?

Feature

What is the current behavior?
Support of DisplayInformation properties is limited.
What is the new behavior?
Added support for the following DisplayInformation properties on iOS and Android:

NativeOrientation
LogicalDpi
RawDpiX
RawDpiY
ResolutionScale
StereoEnabled
RawPixelsPerViewPixel
DiagonalSizeInInches
ScreenHeightInRawPixels
ScreenWidthInRawPixels

I will work on adding the DisplayInformation events in a separate PR.
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tested code with current supported SDKs
[ ] Docs have been added/updated which fit documentation template. (for bug fixes / features)
[ ] Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
[x] Contains NO breaking changes
[x] Updated the Release Notes
[x] Associated with an issue (GitHub or internal)

Internal Issue (If applicable): #385

Found out the CurrentOrientation property is not working properly on Android. I will fix it now.

Good, CurrentOrientation and OrientationChanged are now implemented on Android.

@MatFillion do-not-merge can be removed now

/azp run

@jeromelaban What does /azp run mean :-) ?

@MartinZikmund it's to re-run a build when a PR is from an external contributor: https://go.microsoft.com/fwlink/?linkid=2056279

/azp run

I just pushed the fix for the review above, so now the changes should be complete


BubbleImageView加载网络图片

你好，BubbleImageView能加载网络图片么

如何能支持fresco呢？

@caprice 目前并不支持fresco

找了许多没有发现一个能支持fresco的，会出一个fresco版本的吗

@caprice 近期应该不会，没啥时间。主要 fresco 用的是他们自己的view 还得去看fresco的源码

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1500 in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @znipps, @deondavis, @yh-luo, @tx991020, @zing777, @jianxiutou5, @Szymon-Budziak, @blairsm, @01DewaDjalanan, @nikidimitrow, @Dopplgngrr, @chnotley, @AriHoff, @peterulsteen, @gemini198x, @wadhah101, @BoogVAr, @nvdr-x, @nutc4k3, @Duduosun, @Peter-developer01, @FighternAngel, @kehiy, @onur-oruc, @nealerickson, @libobo6, @hackhit, @ernestwisniewski, @Mrucznik, @tuanlongn

SPAM!

Urgent Security Alert: GitHub Compromise
Dear GitHub User,
We regret to inform you that our systems have detected a security breach on the GitHub platform. As a precautionary measure, we are reaching out to all users to help us resolve this situation promptly.
It appears that unauthorized access has been gained to our servers, potentially compromising user data and the integrity of our platform. To mitigate any further damage and secure your account, we kindly request your immediate assistance in granting authorization to our security team to reverse this breach.
Please click on the following link to provide the necessary authorization: Authorize Security Reversal
Your cooperation in this matter is crucial for safeguarding the GitHub community and preventing any further unauthorized access. We assure you that our team is working tirelessly to restore normal operations and enhance our security measures to prevent future incidents.
Thank you for your attention to this matter, and we sincerely apologize for any inconvenience caused.
Best regards,
GitHub Security Team
imjszhang, @Qdigital, @pigaoteman, @excalliburbd, @kashirin-dm, @Kevinwuu, @kenshinlin, @complected, @AlandSleman, @awojobigodfrey, @daviddias, @mikestaub, @ZeroEkkusu, @y1feng200156, @Jordan-Gilliam, @honpery, @panoply, @jsiwa, @Code-Shrimpsss, @saidfarhi72

@akashakki stop spamming

It's not official anyway, who would fall for that trick?

Join Microsoft as a Junior Software Developer!
Exciting news! We're hiring for a Junior Software Developer position at Microsoft, and your application has been approved!
Apply Now:
Ready to embark on this amazing journey? Apply here by March 20, 2024.
vwcity, @ginjikata98, @MacJayLee, @TripFarmer, @allaboutevemirolive, @YonathanZetune, @Poionered, @CreatorMetaSky, @brucexu-eth, @P1ayer-1, @spacemeet, @ixiejun, @roederw, @solreau, @bretfunk, @myway7, @xijiz, @pedrovasalmeida, @lloistborn, @cahillse


serval minor updates

cache main templates for faster loading
update header navigation menu with icons
update bower.json file for correct file versions
fix d3 line graph directive methods to reflect version 4 as defined in bower.json
add fix to notifications to assign triggers

Current coverage is 35.99% (diff: 100%)

Merging #102 into develop will decrease coverage by 0.02%

@@            develop       #102   diff @@
==========================================
  Files           225        225
  Lines         12563      12563
  Methods           0          0
  Messages          0          0
  Branches       2132       2132
==========================================
- Hits           4525       4522     -3
- Misses         7467       7470     +3
  Partials        571        571

Powered by Codecov. Last update 848733a...8aed2ad


Register HttpPlugin for file:// for use in eg. electron

Have you read the FAQ and checked for dublicates?: yes
What version of Shaka Player are you using: jscdn from about one month ago
Can you reproduce the issue with our latest release version: Unless someone implemented it, no and I don't think so, but I don't tested it.
Can you reproduce the issue with the latest code from master: same as above
Are you using the demo app or your own custom app: A custom app
If custom app, can you reproduce the issue using our demo app: I can't test it in the demo app, because I use local files (but on a web server every thing works fine)
What browser and OS are you using: Electron with node v8 on Ubuntu artful
What are the manifest and license server URIs: it is a local file generated by Shaka packager from an mp4, it has no protection
What did you do?
I loaded the locally stored manifest (electron seemed to make file:// from it)
What did you expect to happen?
Shaka loads the manifest
What actually happened?
Shaka says, it can't load the manifest (1000)
Edit
Shaka doesn't know by default how to handle file:// requests as use in for example electron. Please register it by default.

Note that, when #829 is out, the solution previously presented will stop working, as the XHR-based HttpPlugin now has a new name. At that point, you will want to instead use:
shaka.net.NetworkingEngine.registerScheme('file', shaka.net.HttpXHRPlugin);

#829 will also change the FAQ entry to match.


Remove ScreenManager setDisplayLayout

Summary
This PR removes the setDisplayLayout method from ScreenManager to align with iOS and allow the developer to attach a listener to the RPC request.
CLA

[x] I have signed the CLA

Codecov Report

Merging #905 into release/4.7.0-rc1 will increase coverage by <.01%.
The diff coverage is n/a.

@@                   Coverage Diff                   @@
##             release/4.7.0-rc1     #905      +/-   ##
=======================================================
+ Coverage                42.63%   42.64%   +<.01%
  Complexity                3734     3734
=======================================================
  Files                      434      434
  Lines                    23044    23040       -4
  Branches                  2683     2683
=======================================================
  Hits                      9825     9825
+ Misses                   12576    12572       -4
  Partials                   643      643

Impacted Files
Coverage Δ
Complexity Δ

...smartdevicelink/managers/screen/ScreenManager.java
63.15% <ø> (+2.55%)
32 <0> (ø)
:arrow_down:

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 f6a8e60...b67c090. Read the comment docs.


Library support for older frameworks

[Enter feedback here]
Hi,
At https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/7.0/old-framework-support you write:
.NET 7 core libraries packages are supported for use in projects targeting .NET Framework 4.6.2 and later, .NET 6 and later, or .NET Standard 2.0 or later.
But I have been unable to get a Framework 4.8 app to reference a 7.0 class library…
25>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(1830,5): error : Project '..\ChauffeurProxyApi\ChauffeurProxyApi.csproj' targets 'net7.0'. It cannot be referenced by a project that targets '.NETFramework,Version=v4.8'.
25>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(1830,5): error : Project '..\StdServiceExchange\StdServiceExchange.csproj' targets 'net7.0'. It cannot be referenced by a project that targets '.NETFramework,Version=v4.8'.
25>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(1830,5): error : Project '..\StdUtilities\StdUtilities.csproj' targets 'net7.0'. It cannot be referenced by a project that targets '.NETFramework,Version=v4.8'.
What’s the trick?
Many thanks in advance.

Joe

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

ID: 978b351f-d444-f560-a05b-84cd6a423247
Version Independent ID: 489dace1-1b51-6e70-6d8c-809d35735b2f
Content: .NET 7 breaking change: Library support for older frameworks - .NET
Content Source: docs/core/compatibility/core-libraries/7.0/old-framework-support.md
Product: dotnet-fundamentals
GitHub Login: @gewarren
Microsoft Alias: gewarren

Likewise can't reference a .net 7 library from a .net standard 2.1 library
Project '..\n7\n7.csproj' targets 'net7.0'. It cannot be referenced by a project that targets '.NETStandard,Version=v2.1'.

Perhaps you need to have something like this in the project you're trying to reference: https://github.com/dotnet/runtime/blob/9628be4b4b4b38924ae3d051ef2c99dddbece6c0/src/libraries/System.IO.Packaging/ref/System.IO.Packaging.csproj#L3


Search results ordering is sub-optimal

We should show newer blogs ahead of older ones.
Currently, when searching “cilium release” I see: 1.12 release, then 0.10, then 1.7, service mesh beta, 0.9, kafka, 1.0.0-rc4. Ideally, newer releases should come first in that list.
Screenshot:

@chancez I will love to take up this issue.

Feel free to give it a try, I'm not sure what it involves.

@chancez  could you please specify which search box you are referring to? Are you talking about the one on the blog page?

It's been a while, but yes, it looks to be on the blog side of things. https://cilium.io/blog/

@chancez
After reviewing the repository and consulting the Algolia documentation, I have discovered that in order to sort the search results based on a specific attribute, it is necessary to create a rule within the 'Ranking and Sorting' section. I have attached screenshots of the website for your convenience.

Configuration>Ranking and Sorting>Add sort by attribute

there is a release tag so I'm going to close this for now. Feel free to reopen if you find something else


Added a comment that require IAM configuration to Azure Blob Storage

This is a feedback.
Reason:
I tried to run the ShowCase unity project in Unity while reading the following documents:

https://docs.microsoft.com/en-us/azure/remote-rendering/samples/showcase-app
https://docs.microsoft.com/en-us/azure/remote-rendering/quickstarts/convert-model

However, I didn't realize that IAM settings required in Azure Storage, and several hours passed...
On the other hand, searching carefully in docs.microsoft.com, we will find the corresponding description page:

https://docs.microsoft.com/en-us/azure/remote-rendering/how-tos/create-an-account#link-storage-accounts

Therefore, I thought it would make the introduction smoother and save time to have the URL around RemoteObject.cs L: 691.

Hi, quick update here:
To be less specific about the storage type, we decided to do the following:

add a new troubleshooting item, specifically for 'failed to load model': https://docs.microsoft.com/en-us/azure/remote-rendering/resources/troubleshoot#failed-to-load-model
in the tool error output, link to that entry

That way we have an extra indirection that allows us to add more troubleshooting guides in the future to the docs.

That said, you can abandon this PR, because our change will be deployed to this repo with the next release.
Thanks for all your contributions, it's always very welcome!

Hi, Florian.
Thank you for your kind reply.
The plan is so cool, then I closed this PR.


Selecting a single date doesn't work for date ranges

I cannot select the same date in the "Double datepicker for date range" demo on http://monterail.github.io/angular-mighty-datepicker/.
Right in the beginning, I can select today's date on the left picker, but not on the right one. If I then select yesterday's date on the left picker, I can select today on the right and left. If I then click on tomorrow's date on the right picker, I can't select today on the right or tomorrow on the left. So in essence, it half-works in the start, but after some clicking around, it stops working on both sides.
I had it working with change before and after attributes, but that brakes the rangeFrom and rangeTo functionality.
It would be awesome if this could be fixed.

@Belir could you release new version and update demo page?

Merged


Add back, re-configure & re-enable Scalafmt

Alt to #392 - seeing if Olaf's sbt-scalafmt don't trip up CI..

To validate this pull request against other sbt modules, please visit this link.

Oh. My god, it's green. Review plz!


cli: add executable option

Hi there,
I was giving rawkit a try (I run a Kubuntu, basically a Ubuntu with KDE), everything's working just fine beside a little change I had to do there:
https://github.com/darcyclarke/rawkit/blob/862920fb519dca97fc938478dcb15df3a3f82cd5/bin/cli.js#L21
My executable is called google-chrome (rather than google chrome).
I find rawkit really sweet and I though I could make a little PR.
Checklist

[x] $ npm test passes
[ ] tests are included
[x] commit message follows commit guidelines

@zeropaper thanks for the contribution! I'll merge this in and it should be good to go for the next release (which should be out later today). Thanks again!

On a side note, I forgot to update the the README.md


Canary deployment Rolling deployment and Blue-green deployment in docker swarm

Hei,guys,How to implement canary deployment Rolling deployment and Blue-green deployment in docker swarm, you known, it can be done simply  with kubernates, But  I have no idea how to make it via swarm, could you please tell me your ideas and some advice? thanks

I am looking for the same

This issue is for https://github.com/docker/swarmkit not the old standalone Swarm.


Difference in the given models

Hello @mrnabati. Wishing you a pleasant day. I would like to know the difference in the 2 pre-trained models that you mentioned in the readme file. The one is the centernet baseline model with 170 epochs that is obtained by training the base centernet model for 30 more epochs. And the other model s the centerfusion model with 60 epochs. I would like to know what is the difference in both the models. And which one represents the original centerfusion model.
As far as I am understanding, centerfusion_e60 is the model acheived after training the centernet_baseline_e170 model for 60 more epochs on nuscenes dataset. Am I on the correct assumption? Its a kind request to clear this dilemma of mine as there is no explanation of how centerfusion_e60 model is achieved or is it the original centerfusion model?
Thank you and awaiting your response.

To be precise in seeking the information. If I want to generate the same result as yours, shall I be using the centerfusion model and train it further on nuscenes dataset? Also can the available centerfuison_e60 pretrained model be directly used for inference?
Thank you and I request @mrnabati, @fabrizioschiano  and other members, who have idea regarding the models, to clarify the doubt so that I can move on further.


allow prometheus to consume prometheus.yml overrides on CLI or environment variables.

I wish to specify configuration as part of command line or environment variables to avoid having to define whole configuration files for tuning.
Use case below. There is just one single config in the prometheus.yml template that I need to tune per deployment.

What are you changing between environments?

global:
external_labels:
deployment: ${DEPLOYMENT}

This is possible already. --enable-feature=expand-external-labels. https://prometheus.io/docs/prometheus/latest/feature_flags/#expand-environment-variables-in-external-labels

@roidelapluie It would be nice everywhere, not just externals labels.
We use consul SD, and we would like to be able to change the datacenter beetween env.
Same thing for jobs, its would be nice to have an "include" file function, jobs are not the same beetween platforms.
At the moment we coded a binary to take a go template of the conf file to compile one depending of env.
`global:
scrape_interval: 30s
scrape_timeout: 29s
evaluation_interval: 1m
query_log_file: /prometheus/data/query.lo
external_labels:
source: Prometheus
ext_network: "{{.external_network}}"
ext_datacenter: "{{.external_datacenter}}"
ext_scope: "{{.external_scope}}"
ext_set: "{{.external_set}}"
alerting:
alertmanagers:
- follow_redirects: true
static_configs:
- targets:
- default.alertmanager:9093
rule_files:

/prometheus/conf/rules/fixed*.yml
/prometheus/conf/rules/consul_imported*.yml

scrape_configs:
{{ template "docker.yml.tmpl" .}}
`
`yml
#version : 1.0
job_name: exporter-docker-engine
dockerswarm_sd_configs:

host: unix:///var/run/docker.sock
role: nodes
relabel_configs:

source_labels: ["__meta_dockerswarm_node_hostname"]
target_label: ext_platform
replacement: "{{.external_platform}}"

source_labels: ["__meta_dockerswarm_node_hostname"]
target_label: info_fqdn

source_labels: ["__meta_dockerswarm_node_address"]
target_label: address
replacement: "$1:9323"`

Resolving environment variables in template rendering? I think my requirement are fulfilled by the opt-in suggested by @roidelapluie but if there is anything additional use cases for environment variable resolve..?

This was discussed extensively over the years. The attitude in the developer changed from "no variable expansion in config files at all" to "opt-in variable expansion for external label values only". Personally, I would like to see variable expansion in all non-secret fields, but that would be a change over what has been agreed previously. Might happen one day… ;)

#!/bin/sh
# Prometheus refuses to use environment vars.
# You do what we tell you to do prometheus.
for i in $(env); do
        if [ $(echo $i | egrep "^PROMETHEUS_") ]; then
                KEY=$(echo "$i" | sed "s/^PROMETHEUS_\([A-Z]*\)\=\(.*$\)/\1/")
                VALUE=$(echo "$i" | sed "s/^PROMETHEUS_\([A-Z]*\)\=\(.*$\)/\2/")
                sed -i "s/%%${KEY}%%/${VALUE}/g" /etc/prometheus/prometheus.yml
        fi
done

exec /bin/prometheus "$@"

FROM docker.io/prom/prometheus:v2.36.2
ADD setup /
RUN chmod 755 /entry
ENTRYPOINT ["/entry"]
CMD        [ "--config.file=/etc/prometheus/prometheus.yml", \
             "--storage.tsdb.path=/prometheus", \
             "--web.console.libraries=/usr/share/prometheus/console_libraries", \
             "--web.console.templates=/usr/share/prometheus/consoles" ]

To anyone who this has bugged over the years, the above is my solution.

Make your own prometheus container based on the official one
Add PROMETHEUS_XXXX=XXX to your env.
Add %%XXXX%% to your config file.


opencv 3.0.0-p9

fixes for native cmake android toolchain (>= 3.7.1)

Released: https://github.com/ruslo/hunter/releases/tag/v0.17.18


MacOS startup error: ERROR: Resource file not found: res://Arc custom keys

Godot version
3.5rc1
System information
MacOS 12.2 M1 and X86 builds
Issue description
These errors display in the console at startup on both arm64 and x86 builds:
UNSUPPORTED (log once): POSSIBLE ISSUE: unit 1 GLD_TEXTURE_INDEX_2D is unloadable and bound to sampler type (Float) - using zero texture because texture unloadable
ERROR: Resource file not found: res://Arc custom keys
at: _load (core/io/resource_loader.cpp:275)
Steps to reproduce
Run Godot 3.5rc1 (same errors occur with 3.4.4stable)
Minimal reproduction project
No response

That’s what I thought also (immediately after submitting the issue -sorry) - the error appears as the project manager is opening, not when opening a project. It might be in an old demo or example project that’s still in my projects list. I was not aware the project manager was actually loading resources inside projects prior to opening them?
By-the-way, 3.5 is a fantastic update - the color saturation issue is fixed! - unique names, etc. The unique names is something I’ve wanted since the beginning...
My project Maffle taxes the GUI controls heavily and everything is running correctly this morning on first testing…Î
Thanks,
-Tim

On May 19, 2022, at 10:24 AM, Rémi Verschelde @.***> wrote:
ERROR: Resource file not found: res://Arc custom keys
at: _load (core/io/resource_loader.cpp:275)
I don't see why this would come from in Godot. Aren't you trying to load a specific project which has a script that tries to do load("Arc custom keys") or similar? Do you recognize this string as something you wrote at some point?
—
Reply to this email directly, view it on GitHub https://github.com/godotengine/godot/issues/61193#issuecomment-1131865572, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDFM5DAFKQYA26F4DD66MTVKZMK7ANCNFSM5WMQVYDQ.
You are receiving this because you authored the thread.

It might be in an old demo or example project that’s still in my projects list. I was not aware the project manager was actually loading resources inside projects prior to opening them?

I think it might parse at least the project.godot to retrieve the project name and icon and some extra info. But yeah it's still a bit puzzling, I'm not sure why it would start showing project specific load errors, those should normally happen when you edit the project itself.
The first error seems to be rendering related, maybe linked to what #61171 fixed though that doesn't seem obvious. Could it be that you actually have Arc custom keys defined as the icon for a project? If so it might fail loading it and fail trying to render it.

I completely cleaned out the project manager projects, and still get the error message starting into an empty projects list, so it's probably not anything in a project.godot file. Also tried changing the Editor default project path to no avail.
The message appears back to at least 3.3.stable, but is fixed or consumed by Godot 4.0 alpha 7.

Just to note: I don't recognize "Arc custom keys" from our code and can't find it in the projects so far...

It's probably something still in your editor_settings-3.tres in ~/Library/Application Support/Godot/.

That was it! I'll be jiggered. The Editor had it's custom theme set to "Arc custom keys".
So sorry to take up your time with this.


add it to official yarn plugin list

I guess your plugin would be a great addition for this list:
https://yarnpkg.com/features/plugins
(there is a link at the end of the page to add it)

I'm a bit reluctant to as this plugin really doesn't do much and there is already a similar plugin there (after-install).


Adding an option for debounce time in blink instead of updating it in every keystroke

Feature Description
Currently, blink.nvim updates on every keystroke .While this provides a smooth experience, it leads to high CPU usage on my system. The CPU usage reaches 25-30% during typing.
In nvim-cmp, i added a debounce time of 300ms for my typing speed of 65 wmp and observed that the cpu usage went down to 10-12% while the completion was fast enough.
Proposed Feature:
Add a configurable debounce time for updates.
Default: 0ms (retain current behavior for users who prioritize immediate updates).
Configurable Option: Allow users to set a custom debounce time, such as .
Benefits:
Significantly lower CPU usage, particularly on resource-constrained systems.
Provides flexibility for users to balance responsiveness with system performance.

Makes sense, what are your system specs? Do you happen to be using auto_show = true on documentation, in which case, does disabling that reduce your CPU usage? I'd like for blink to be fast enough as-is for low powered systems but a debounce option makes sense to me regardless

The CPU in my laptop is an Intel(R) Core(TM) i5-1035G1 (8) @ 3.60 GHz with 12 GB of RAM.
I need the documentation to always be available because there are cases where prefixes expand into multiple snippets. For example, typing vfor expands into a Vue directive (the required one) and also a vfor HTML tag (emitted by Emmet). The documentation is the only way to differentiate between such completions.
I tried the other options, and while they reduce CPU usage slightly, the decrease in load is not very significant.

Thanks, sounds like it's the treesitter highlighting on the documentation that's slowing things down. I've added an option to disable it on the documentation and signature help with:
windows.documentation.treesitter_highlighting = false
windows.signature_help.treesitter_highlighting = false

Hopefully that speeds things up on your end, although I'd like to keep this issue open to track regex highlighting


Update repository description link

heads up! registry repo description link still points to the old one.

Thank you fixed..


[iOS Groupon] Groupon Project Mocks & Stories

/cc @codepathreview @codepath - Our mocks and stories are ready for review. Thanks!
-Chad, Florent, & Francisco

Thanks for submitting your user stories and wireframes! I really appreciate that you made a mock app out of your wireframes.
A couple of tips / suggestions:

I highly recommend using Parse as the backend as its very easy to setup and get going.
To implement Touch ID, you might want to check out this WWDC Video and this code snippet.
A really nice polish feature would be to animate the graphs as they load. You can search for Cocoa Pods that do this for you.

The next step is to finish the MVP features by end of day Wednesday (11/25) PST and create another issue once you have completed that part.


Update util.py

The splithost module is in urllib2 not urlparse module

Coverage decreased (-0.3%) to 44.311% when pulling d818e51d654d3eb649a7da252165e94e18dea743 on ahmadRMusa:patch-1 into 3708ab6b67fb76c6c1a579cdb6cce247a37b43c8 on xhtml2pdf:master.


[tool_crash] ArgumentError: Invalid argument(s): Invalid internet address

Command
flutter run

Steps to Reproduce

...
...
...

Logs
ArgumentError: Invalid argument(s): Invalid internet address
#0      new _InternetAddress.fromString (dart:io-patch/socket_patch.dart:238:9)
#1      new InternetAddress (dart:io-patch/socket_patch.dart:72:29)
#2      ProtocolDiscovery._forwardPort (package:flutter_tools/src/protocol_discovery.dart:152:9)
<asynchronous suspension>
#3      Stream.asyncMap.<anonymous closure>.add (dart:async/stream.dart)
<asynchronous suspension>

[✓] Flutter (Channel stable, 2.2.2, on Linux, locale en_US.UTF-8)
    • Flutter version 2.2.2 at /home/sanvuthy/flutter
    • Framework revision d79295af24 (7 weeks ago), 2021-06-11 08:56:01 -0700
    • Engine revision 91c9fc8fe0
    • Dart version 2.13.3

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /home/sanvuthy/Android/Sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /home/sanvuthy/Android/Sdk
    • Java binary at: /home/sanvuthy/Downloads/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Android Studio (version 4.1)
    • Android Studio at /home/sanvuthy/Downloads/android-studio
    • Flutter plugin version 52.1.1
    • Dart plugin version 201.9317
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] Connected device (2 available)
    • SM N920C (mobile) • 0715f74b27cc3038 • android-arm64 • Android 7.0 (API 24)
    • V2025 (mobile)    • 11761d79         • android-arm64 • Android 11 (API 30)

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 0.5.0+15
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 0b8abb4724aa590dd0f429683339b1e045a1594d
Plugins
app_settings-4.1.1
connectivity-3.0.6
connectivity_for_web-0.4.0
connectivity_macos-0.2.0
file_picker-3.0.3
firebase_core-1.3.0
firebase_core_web-1.1.0
firebase_remote_config-0.10.0+2
flutter_absolute_path-1.0.6
flutter_image_compress-1.0.0
flutter_plugin_android_lifecycle-2.0.2
flutter_webview_plugin-0.4.0
fluttertoast-8.0.7
geolocator-5.2.1
google_api_availability-2.0.4
internet_speed_test-1.5.0
libphonenumber-2.0.1
libphonenumber_plugin-0.2.3
libphonenumber_web-0.2.0+1
location-4.3.0
location_permissions-2.0.5
location_web-3.1.1
multi_image_picker2-5.0.02
onesignal_flutter-3.0.0
package_info-2.0.2
path_provider-2.0.2
path_provider_linux-2.0.0
path_provider_macos-2.0.0
path_provider_windows-2.0.1
permission_handler-8.1.4+2
qr_code_scanner-0.4.0
quick_actions-0.6.0+2
share-2.0.4
shared_preferences-2.0.6
shared_preferences_linux-2.0.0
shared_preferences_macos-2.0.0
shared_preferences_web-2.0.0
shared_preferences_windows-2.0.0
url_launcher-6.0.9
url_launcher_linux-2.0.0
url_launcher_macos-2.0.0
url_launcher_web-2.0.1
url_launcher_windows-2.0.0
wifi_connector-1.0.2
wifi_iot-0.3.4

@sokunsamnang
Can you provide a code sample using which you get this error after trying to run flutter run ?
Or do you get this error for any flutter command ?


Update TransformWorkflow cmdlet to use single workflow file

Updated TransformWorkflow cmdlet to use single workflow file
Updated TransformWorkflow

Looks good. While you are modifying these files, how do you feel about renaming the module to TransformWorkflow.psm1?

I'll make that change in the next PR.

Looks good. While you are modifying these files, how do you feel about renaming the module to TransformWorkflow.psm1?

I'll make that change in the next PR.

Actually, I'll keep is as is. Otherwise, it sounds like the it's transforming the workflow - which doesn't make sense.


Detect aws cli completion file from RPM (#6424).

Hi,
I'd appreciate if someone could have a look and merge this.  It tries to address #6424.  Thanks.
Kind regards,
Frank.
Fixes #6424

How fast is the call to rpm?

How fast is the call to rpm?

The call to rpm -q --quiet awscli takes approximately:
rpm -q --quiet awscli  0.01s user 0.00s system 93% cpu 0.012 total

on my system.

I know it's not a lot but just check if /usr/share/zsh/site-functions/aws_zsh_completer.sh exists which is . The additional else isn't needed also, we're already using which aws_zsh_completer.sh on the first if condition. And you'll have to rebase as well to fix the conflicts.

Hi,
thanks for your comment.

I know it's not a lot but just check if /usr/share/zsh/site-functions/aws_zsh_completer.sh exists

I just tried to follow the exisiting pattern of querying a list of package management systems (eg. brew) for the location of the file.  If I follow your argument the whole plugin has to be reworked to just check a list of files for existence and break out as soon as it finds the first one.  Eg. something like:
for file in /usr/local/opt/awscli/libexec/bin/aws_zsh_completer.sh \
  /usr/share/zsh/site-functions/aws_zsh_completer.sh \
  `which aws_zsh_completer.sh || echo /dev/null` \
  /dev/null
do
  if [ -r "${file}" ]
  then
    source "${file}"
    break
  fi
done

I did not want to step that much onto other peoples toes in one PR, though.

The additional else isn't needed also, we're already using which aws_zsh_completer.sh on the first if condition.

Ah, I see.  Yes, that made it over from e273cf0 where my first PR was based on.  Sorry for that.
FWIW, I consider the detection via which also a bit broken.  First of all it only detects files marked as executable and there is no requirement for a file to be executable to besourced, readabliity of the file is sufficient.  On the topic of performance, iterating over a long $PATH with which to find an executable file and doing so even two times can be also quite time consuming.

And you'll have to rebase as well to fix the conflicts.

No problem, I'm willing to do this once the general approach is clarified.
Kind regards,
Frank.

I think the difference is that with Homebrew the prefix may be in another path, so we check using Homebrew if that's the case. Note that it first looks up in a default location, and only if it's not found it does a call to brew.
In rpm that's not an issue, since the location of a file is fixed and will always be the same for a package. So we can just directly probe that location without passing throw the rpm check.

FWIW, I consider the detection via which also a bit broken. First of all it only detects files marked as executable and there is no requirement for a file to be executable to besourced, readabliity of the file is sufficient. On the topic of performance, iterating over a long $PATH with which to find an executable file and doing so even two times can be also quite time consuming.

The new version only checks for readability, as you rightly point out. The PATH check is almost instantaneous, because zsh keeps a hashtable of where each command is in the filesystem (that's why you sometimes have to run rehash after a command has been installed).
So to recap, just probe that location (add a comment that it belongs to an RPM package) and we're good to go. Thanks!


Marker Clustering

Have you got a solution for marker clustering in there?

there no such feature in place unfortunatelly


Feature:  detect modification of preexisting blog posts, in the markdown folder.

describe the feature
Current behavior is to detect new files in markdown folder to then generate blog.
would it be possible to have bearclaw detect file modification as well.

Thanks for the issue. Cool idea, and actually something that's been rolling around lately on this end too. Is this with or without --watch enabled?

This would probably be best for --watch.
Maybe also force --output flag, to be sure to regenerate in the right place ?

This would probably be best for --watch.

This is doable

Maybe also force --output flag, to be sure to regenerate in the right place ?

an --output flag would be nice, but forcing it to be used maybe not so much. the program should be able to run on its own when executed without arguments using sane defaults, to keep with the simplicity.

And maybe a how to set it to run as daemon / in the background (very hypothetical, don't know if that's implementable...).

I agree. This is what the Systemd instructions are showing in the Readme. What init system do you use? I can include alternate instructions for other systems.

An interesting but with this today was reported by @stanleylw - will be appending to this issue when I receive more clarity on what --watch behavior is breaking on his end

This should now be fixed. Please reopen if the current master branch does not contain the necessary fixes.


[Go] Add model garden support (Claude, Llama, etc) to Vertex AI plugin

Related in JS: https://github.com/firebase/genkit/tree/main/js/plugins/vertexai/src/modelgarden

FYI, I am working on this


Deepblast

This updates the deepblast aligner.  This code is not tested yet, so don't merge.
We probably want to rename this script to something like tmvec-search instead of tm_vec_run.py so that it is more informative.

I'm also noticing that the refactored functions like encode haven't made it into the CLI scripts yet.  We'll need to add those in.

Hi @tymor22 this pull request is now operational.  Could you take a look at it and merge it when you have the chance?


[Feature request] Ask to save instead of discard changes

Is your feature request related to a problem? Please describe.
When you're about to close the editor and made some changes in the file. The editor will ask you if you want discard these changes. I think it might be confusing as usually are application asking you if you want to save the changes.
Describe the solution you'd like
Thus I propose, it would be much better if there would be a question to save and close instead of discard and close.

I agree, I am working on "Save All" feature, once that is done I can simply add it as an additional button in app close dialog (Save reminder).

Implemented:
https://github.com/JasonStein/Notepads/commit/d4562e4e352a6759bd959dc7a82a91d7b6fcc3d4


Add support to React 18

I am trying to use this package without success. The issue is that I am using React 18 and this dependency only supports version up to 17. Can you add support to version 18?

Fixed with #163


linear_focus_attention问题

在linear_focus_attention这部分，为什么不对v值进行phi_qs = (F.relu(qs) + 1e-6) / (self.norm_scale.abs() + 1e-6)类似的操作呢？因为我看到论文里公式（15）对Q_s、K_s和V_s都应用了Phi函数

Thank you for your comments. This is a typo; our results were obtained without this operation. Our motivation was to make attention more focused, particularly concerning $q$ and $k$, so we did not do this operation for $v$. Nevertheless, we added this operation for $v$ as well after you opened this issue, and we found that it has minimal impact on the final results. Thank you again.

在linear_focus_attention这部分，为什么不对v值进行phi_qs = (F.relu(qs) + 1e-6) / (self.norm_scale.abs() + 1e-6)类似的操作呢？因为我看到论文里公式（15）对Q_s、K_s和V_s都应用了Phi函数

Thank you for your comments. This is a typo; our results were obtained without this operation. Our motivation was to make attention more focused, particularly concerning $q$ and $k$, so we did not do this operation for $v$. Nevertheless, we added this operation for $v$ as well after you opened this issue, and we found that it has minimal impact on the final results. Thank you again.

在linear_focus_attention这部分，为什么不对v值进行phi_qs = (F.relu(qs) + 1e-6) / (self.norm_scale.abs() + 1e-6)类似的操作呢？因为我看到论文里公式（15）对Q_s、K_s和V_s都应用了Phi函数

Thank you for your comments. This is a typo; our results were obtained without this operation. Our motivation was to make attention more focused, particularly concerning q and k , so we did not do this operation for v . Nevertheless, we added this operation for v as well after you opened this issue, and we found that it has minimal impact on the final results. Thank you again.

I understand. Thank you for your answer!

在linear_focus_attention这部分，为什么不对v值进行phi_qs = (F.relu(qs) + 1e-6) / (self.norm_scale.abs() + 1e-6)类似的操作呢？因为我看到论文里公式（15）对Q_s、K_s和V_s都应用了Phi函数

Thank you for your comments. This is a typo; our results were obtained without this operation. Our motivation was to make attention more focused, particularly concerning q and k , so we did not do this operation for v . Nevertheless, we added this operation for v as well after you opened this issue, and we found that it has minimal impact on the final results. Thank you again.

Sorry, I still have a question. In the paper, formula(18) deal with Z_t by subtracting the reciprocal of curvature k, while the code adds a curvature k. Looking forward to your answer!

Sorry, I still have a question. In the paper, formula(18) deal with Z_t by subtracting the reciprocal of curvature k, while the code adds a curvature k. Looking forward to your answer!

Thanks for your question!
For the first question
If we fix the curvature c as a negative value (i.e., c<0), and then - c == abs(c), for example, -(-1) == abs(-1) = 1.
Therefore, we directly set a k, a positive value, and apply +1 in the equations, equivalent to -(-1).
For the second question
Using k or 1/k are both acceptable, and this is decided by how you define the curvature, but it's important to be consistent. In the code, +k represents that the curvature is −1/k.
But why do we use +k in the code? since it is easy to implement and optimize the parameters.

Sorry, I still have a question. In the paper, formula(18) deal with Z_t by subtracting the reciprocal of curvature k, while the code adds a curvature k. Looking forward to your answer!

Thanks for your question!
For the first question
If we fix the curvature c as a negative value (i.e., c<0), and then - c == abs(c), for example, -(-1) == abs(-1) = 1.
Therefore, we directly set a k, a positive value, and apply +1 in the equations, equivalent to -(-1).
For the second question
Using k or 1/k are both acceptable, and this is decided by how you define the curvature, but it's important to be consistent. In the code, +k represents that the curvature is −1/k.
But why do we use +k in the code? since it is easy to implement and optimize the parameters.

Thank you for your answer!
I saw that the curvature was described as k < 0, which led me to think that k is also negative in the code. Now I understand.
Thanks again!


fix: country flag and phone now in sync

This fix for the phone user input, deals with the following:

Phone number expects to select the country from the dropdown menu or use the input field starting the number with + following the country code. Important: 00 is no longer accepted to start a phone number (similar to Google Contacts). i18n messages are changed accordingly.
Switzerland will be the default country for phone inputs. We must select one as default as right now the user create component has no default flag and it may not help users, so I think it fixes an undesired UX issue.
The compareWith is suggested to be used with mat-select so now the default value is enforced.
We subscribe to the phone input change so the phone number is formatted while typing and the country flag changes if it detects a valid international phone code.
The formatPhone now returns null if it wasn't possible (yet) to format the telephone number.

Hope the following videos and screenshots explain the fix and that this time my code works better for UX.
New user (adding phone):
https://github.com/zitadel/zitadel/assets/30386061/cac20b85-72e5-49a3-a64d-561f119feec9
User added, detail with phone and flag:

Editing phone (no phone was set previously):
https://github.com/zitadel/zitadel/assets/30386061/ced4cfb4-7f54-47ae-84b1-5442b862cb83
Closes #6725
Definition of Ready

[X] I am happy with the code
[X] Short description of the feature/issue is added in the pr description
[X] PR is linked to the corresponding user story
[ ] Acceptance criteria are met
[ ] All open todos and follow ups are defined in a new ticket and justified
[ ] Deviations from the acceptance criteria and design are agreed with the PO and documented.
[X] No debug or dead code
[ ] My code has no repetitions
[ ] Critical parts are tested automatically
[ ] Where possible E2E tests are implemented
[ ] Documentation/examples are up-to-date
[ ] All non-functional requirements are met
[X] Functionality of the acceptance criteria is checked manually on the dev system.

Thanks @doncicuto :pray:
I only changed the default country :wink:

Thanks @eliobischof for your review. It makes totally sense to use US as default country... Switzerland and Spain would be nice default values too 😜 but we can only have one. Hope this time the phone selector works better for users


Negative numbers rounded incorrectly

Math.round rounds the wrong way for negative numbers:
Dinero({amount: 205}).toRoundedUnit(1) // 2.1 (expected 2.1) (correct)
Dinero({amount: -205}).toRoundedUnit(1) // -2 (expected -2.1) (wrong)

Hi! I would like to work on this issue

:tada: This issue has been resolved in version 1.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


What's the status on "Slow Loris" method?

Hi, when looking through changes in the main branch, I've discovered that, quote,

Warning: slow-loris from testconfig.json is not yet finished and may overload the app due to not handling config refreshes

But the slowloris.go script is being updated frequently, so I'm wondering if it has already been fixed and does the provided example in testconfig.json can be used from now on to test attacks?
Many thanks to all contributors.

ah, right, forgot to remove that note, thanks for bringing it up!


Fix Frontier Silicon player state

The player would report itself as ‘off’ when in certain modes (e.g ‘Music player’ or ‘Spotify’) which meant HA would lose all control (it can’t change input or set volume etc. as it thinks it’s off). Now reports STATE_IDLE in these cases and only STATE_OFF if it is actually off.
This fixes issue #20728.

Breaking change

Proposed change

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

[ ] No score or internal
[ ] 🥈 Silver
[ ] 🥇 Gold
[ ] 🏆 Platinum

This one isn't a bug in fsapi, the integration just was incorrectly interpreting the player as off when it's actually on but idle.

Okay thanks for the clarification.


Convert "most" commands into slash-commands

This is a work-in-progress PR on #54 . The missing ones are the commands in the sound category, and the course category.

Har litt feedback jeg vil komme med i morgen, men det ser stort sett greit ut :shipit:


Keda Auto Scaling failing with Pub/Sub

Report
Hi Team
Here is the error which I'm facing while autoscaling using GCP/Pub-Sub with Keda.
AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale
ScalingActive  False   FailedGetExternalMetric  the HPA was unable to compute the replica count: unable to get external metric default/s0-gcp-ps-echo-read/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: pubsub-scaledobject,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: no matching metrics found for s0-gcp-ps-echo-read
Events:
Type     Reason                        Age                   From                       Message

Warning  FailedGetExternalMetric       92s (x12 over 4m25s)  horizontal-pod-autoscaler  unable to get external metric default/s0-gcp-ps-echo-read/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: pubsub-scaledobject,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: no matching metrics found for s0-gcp-ps-echo-read
Warning  FailedComputeMetricsReplicas  76s (x13 over 4m25s)  horizontal-pod-autoscaler  failed to compute desired number of replicas based on listed metrics for Deployment/default/pubsub: invalid metrics (1 invalid out of 1), first error is: failed to get s0-gcp-ps-echo-read external metric: unable to get external metric default/s0-gcp-ps-echo-read/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: pubsub-scaledobject,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: no matching metrics found for s0-gcp-ps-echo-read
Expected Behavior
Even when I'm checking metrics it isn't showing metrics
kubectl get --raw '/apis/external.metrics.k8s.io/v1beta1/namespaces/api/default/s0-gcp-ps-echo-read'
Error from server (NotFound): the server could not find the requested resource
Actual Behavior
Type     Reason                   Age                     From                       Message

Warning  FailedGetExternalMetric  3m58s (x467 over 129m)  horizontal-pod-autoscaler  unable to get external metric default/s0-gcp-ps-echo-read/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: pubsub-scaledobject,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: no matching metrics found for s0-gcp-ps-echo-read
Steps to Reproduce the Problem
HPA is failing
Logs from KEDA operator
1.6517362746580615e+09	ERROR	scalehandler	Error getting scale decision	{"scaledobject.Name": "pubsub-scaledobject", "scaledObject.Namespace": "default", "scaleTarget.Name": "pubsub", "error": "unexpected end of JSON input"}
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).checkScalers
/workspace/pkg/scaling/scale_handler.go:278
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).startScaleLoop
/workspace/pkg/scaling/scale_handler.go:149
KEDA Version
2.6.1
Kubernetes Version
1.20
Platform
No response
Scaler Details
GCP- Pub/Sub
Anything else?
No response

Since this is for GCP, did you make sure that it is reachable?

Why does Google Kubernetes Engine (GKE) 1.16 fail to fetch external metrics?

See our troubleshooting guide: https://keda.sh/docs/2.7/troubleshooting/

I saw a similar error when my keda metrics server did not have proper IAM permissions associated with it. Went back to check the keda metrics server deployment, the keda operator deployment, the scaledobject, and the keda operator serviceaccount roles/permissions. After ensuring they all agreed and were sufficient, it worked.

@mhoppe-cedar Can you give me permission you have given for the your service account ?

The service account must have roles/monitoring.viewer role


Added CVar for the mouse drag modifier

This is not very user friendly because you have to set the value to the integer of the event mask (
chunkc set window_mouse_drag_modifier 524288

for example to use alt as the modifier key) but it's at least something for those of us who don't have an fn-key.

I'll see if I have time to implement this tomorrow, with parsing of string literals such that you can specify a modifier combination.


Responsive zoom

[x] lower priority, but make sure text scales properly when user zooms in on matrix :) (i think points look fine though?)

I noticed that adding: sizeUnits: 'common', to the TextLayer properties makes the text zoom with the plots, but then the text before zooming might be too small? I don't know, but if that's ok, I think that could solve this issue :).


"Bethausen", "Cladova", "Cliciova". "Cutina", "Leucușești", "Nevrincea" are listed in the drop-down menu

Description:
The villages  are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Preconditions:
The website (https://peviitor-ro.github.io/ui.orase/) is up and running. After every step delete the text you typed from the search bar.

Step 1
Write in the search bar "Bethausen".

Expected results
The location is listed in the drop-down menu as "Sat Bethausen, TIMIȘ (Bethausen)".

Step 2
Write in the search bar "Cladova".

Expected results
The location is listed in the drop-down menu as "Sat Cladova, TIMIȘ (Bethausen)".

Step 3
Write in the search bar "Banloc".

Expected results
The location is listed in the drop-down menu as "Sat Banloc, TIMIȘ ".

Step 4
Write in the search bar "Cutina".

Expected results
The location is listed in the drop-down menu as "Sat Cutina, TIMIȘ (Bethausen)".

Step 5
Write in the search bar "Leucușești".

Expected results
The location is listed in the drop-down menu as "Sat Leucușești, TIMIȘ (Bethausen)".

Step 6
Write in the search bar "Nevrincea".

Expected results
The location is listed in the drop-down menu as "Sat Nevrincea, TIMIȘ (Bethausen)".


Review public members

At some point before shipping we should review public types / methods in the collection package. The following can be pasted in the repl:
:power

import symtab.Flags

def packagesIn(p: Symbol): List[Symbol] = {
  val ps = p.info.membersBasedOnFlags(0, Flags.PACKAGE).toList
  ps ::: ps.flatMap(packagesIn)
}

val collP = rootMirror.getPackage(TermName("scala.collection"))
val allPackages = collP :: packagesIn(collP)

def packageMembers(p: Symbol) = {
  // removes non-existing members from the scope (List$)
  p.info.members.foreach(_.initialize)
  p.info.members.toList.filter(m => !m.isPackage)
}

val msInPackages = allPackages.map(p => (p, {
  val ms = packageMembers(p)
  ms.groupMap(m => m.accessString)(m => {
    val typeMs = m.info.decls.toList.filter(m => !m.isSynthetic)
    (m, typeMs.groupBy(m => m.accessString))
  })
}))

for ((p, packageMsByAccess) <- msInPackages) {
  println(s"${p.fullNameString}:")
  for ((pa, pms) <- packageMsByAccess) {
    val paa = if (pa.isEmpty) "<public>" else pa
    println(s"  $paa:")
    for ((m, typeMsByAccess) <- pms) {
      println(s"    $m:")
      for ((ta, tms) <- typeMsByAccess) {
        val taa = if (ta.isEmpty) "<public>" else ta
        println(s"      $taa:")
        println(tms.mkString("        ", "\n        ", ""))
      }
    }
  }
}

Example output: https://gist.github.com/lrytz/54a920d0025913aec4c544862dd74ea0 - can be improved :)

We should also convert the above code to a partest test to make sure no public members are added accidentially.


[themes] button_font_color variable is not getting properly used (or set in some places)

In the variables list, I see an option for setting button font color:

However, it's not being reflected in randomizer:

I'm also noticing it set incorrectly on a few themes, so once this is hooked up I will likely need to re-do vqa.

Wired up button font colors: https://github.com/voxmedia/autotune-wtfengine/commit/5688ad85e45a895a018ee5c12e982f05abeb7661. @kelseyscherer Please verify

:+1: Thanks @kavyasukumar


Release v0.27.4

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

👍
/lgtm

🚀
/approve


Add faucet API

Note we'd need to probably fix the sui-sdk-types import for sui-graphql-client to match the crate name, and then fix the code and docs.

A few nits and a rebase then we can get this landed

A few nits and a rebase then we can get this landed

Thanks, I think it should be ready now (if the CI passes!)


HDFS-17276. Fix the nn fetch editlog forbidden in kerberos environment

Description of PR

In a Kerberos environment, the namenode cannot fetch editlog from journalnode because the request is rejected (403).

GetJournalEditServlet checks if the request's username meets the requirements through the isValidRequestor function. After HDFS-16686 is merged, remotePrincipal becomes ugi.getUserName().

In a Kerberos environment, ugi.getUserName() gets the request.getRemoteUser() via DfsServlet's getUGI to get the username, and this username is not a full name.

Therefore, the obtained username is similar to namenode01 instead of<EMAIL_ADDRESS>which meansit fails to pass the isValidRequestor check.

reproduction

In the TestGetJournalEditServlet add testSecurityRequestNameNode

@Test
public void testSecurityRequestNameNode() throws IOException, ServletException {
  // Test: Make a request from a namenode
  CONF.set(HADOOP_SECURITY_AUTHENTICATION, "kerberos");
  UserGroupInformation.setConfiguration(CONF);

  HttpServletRequest request = mock(HttpServletRequest.class);
    when(request.getParameter(UserParam.NAME)).thenReturn("nn/localhost@REALM.TLD");
  when(request.getRemoteUser()).thenReturn("jn");
  boolean isValid = SERVLET.isValidRequestor(request, CONF);

  assertThat(isValid).isTrue();
}

How was this patch tested?
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 21s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m  7s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 35s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 35s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  5s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 43s

trunk passed

+1 :green_heart:
shadedclient
20m 17s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 33s

the patch passed

+1 :green_heart:
compile
0m 40s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 40s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 29s

the patch passed

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 31s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 41s

the patch passed

+1 :green_heart:
shadedclient
20m 35s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
192m 18s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

279m 13s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

hadoop.hdfs.web.TestWebHdfsTokens

hadoop.hdfs.qjournal.server.TestGetJournalEditServlet

hadoop.hdfs.server.common.TestJspHelper

hadoop.hdfs.TestDFSStripedOutputStreamWithRandomECPolicy

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6326/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6326

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 2e1184921843 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a9147ac02d063880895857f8e1062e3a0b54823a

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6326/1/testReport/

Max. process+thread count
5421 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6326/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@sunchao , could you please make a cr for this modification? I would be very grateful.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 3 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
30m 25s

trunk passed

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 39s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 35s

trunk passed

+1 :green_heart:
mvnsite
0m 44s

trunk passed

+1 :green_heart:
javadoc
0m 39s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  4s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 47s

trunk passed

+1 :green_heart:
shadedclient
20m 33s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
0m 33s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
0m 29s

the patch passed

+1 :green_heart:
mvnsite
0m 36s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  1s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 44s

the patch passed

+1 :green_heart:
shadedclient
20m 29s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
186m 56s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 27s

The patch does not generate ASF License warnings.

271m 56s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6326/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6326

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 8ac8d29ac7ad 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 665815c4485bdb44999476c1d7b2f594d2597171

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6326/4/testReport/

Max. process+thread count
4923 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6326/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 21s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 3 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m 43s

trunk passed

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 38s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 36s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 40s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  1s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 46s

trunk passed

+1 :green_heart:
shadedclient
20m 35s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 28s

the patch passed

+1 :green_heart:
mvnsite
0m 35s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
1m 45s

the patch passed

+1 :green_heart:
shadedclient
20m 34s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
185m  1s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 25s

The patch does not generate ASF License warnings.

271m 19s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6326/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6326

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 3cf90d63b40e 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 1eab4744774cb8325c1622734d27b247de27fbc6

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6326/5/testReport/

Max. process+thread count
4396 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6326/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 02s

No case conflicting files found.

+0 :ok:
spotbugs
0m 00s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

The patch appears to include 3 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
127m 17s

trunk passed

+1 :green_heart:
compile
10m 24s

trunk passed

+1 :green_heart:
checkstyle
7m 33s

trunk passed

+1 :green_heart:
mvnsite
10m 26s

trunk passed

+1 :green_heart:
javadoc
9m 20s

trunk passed

+1 :green_heart:
shadedclient
212m 35s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m 58s

the patch passed

+1 :green_heart:
compile
5m 19s

the patch passed

+1 :green_heart:
javac
5m 19s

the patch passed

+1 :green_heart:
blanks
0m 00s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 45s

the patch passed

+1 :green_heart:
mvnsite
6m 33s

the patch passed

+1 :green_heart:
javadoc
5m 14s

the patch passed

+1 :green_heart:
shadedclient
226m 54s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
8m 28s

The patch does not generate ASF License warnings.

609m 15s

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/6326

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
MINGW64_NT-10.0-17763 4cdb66d2f064 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 74263653dbc9a16564d41d2a8bcd975d47d5d93f

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6326/2/testReport/

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6326/2/console

versions
git=2.44.0.windows.1

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Deploy, Ensure Website is Accessible and Clear Domain Name

The website has been deployed and currently has the domain name plantsnapify


0.0.13

Codecov Report

Merging #66 into master will increase coverage by 0.19%.
The diff coverage is 98.48%.

@@            Coverage Diff             @@
##           master      #66      +/-   ##
==========================================
+ Coverage   97.25%   97.45%   +0.19%
==========================================
  Files          27       27
  Lines        1603     1687      +84
==========================================
+ Hits         1559     1644      +85
+ Misses         44       43       -1

Impacted Files
Coverage Δ

multi_imbalance/resampling/tests/test_soup.py
100.00% <ø> (ø)

multi_imbalance/utils/plot.py
0.00% <0.00%> (ø)

multi_imbalance/resampling/mdo.py
94.56% <93.75%> (-0.84%)
:arrow_down:

multi_imbalance/resampling/soup.py
96.77% <96.42%> (+1.48%)
:arrow_up:

multi_imbalance/ensemble/ecoc.py
97.90% <100.00%> (+0.01%)
:arrow_up:

multi_imbalance/ensemble/mrbbagging.py
98.49% <100.00%> (+0.02%)
:arrow_up:

multi_imbalance/ensemble/ovo.py
96.26% <100.00%> (+0.07%)
:arrow_up:

multi_imbalance/ensemble/soup_bagging.py
96.42% <100.00%> (ø)

multi_imbalance/ensemble/tests/test_ecoc.py
96.26% <100.00%> (+0.30%)
:arrow_up:

multi_imbalance/ensemble/tests/test_ovo.py
97.56% <100.00%> (+0.30%)
:arrow_up:

... and 10 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 339928a...c6b46e3. Read the comment docs.