FEATURE/MEDIUM: userList: generate random secure password

This change previously hard coded password ("insecure-password" in HAProxy config) usage and instead use hashed password("password").
So, on every start up a random password is generated, hashed and then saved to HAProxy conf.
Generated password is stored in memory, while hashed password is saved to HAProxy conf.

This is related to https://github.com/haproxytech/haproxy-consul-connect/issues/12

I dont think hashing the password is needed here. b64 should only output chars compatible with the config file format and hashing doen't add entropy to the generated string.
Overwise LGTM.

If we remove hashing func, then we need to use insecure-password again. From the issue https://github.com/haproxytech/haproxy-consul-connect/issues/12:

One possible simple solution would be to generate a strong crypto-random password for HAProxy on every startup so it's only in-memory in the consul-haproxy process and passed through to HAProxy. I guess the Config is written to disk so I'd suggest using the secure (hashed) password config to pass it through and hashing the random password in consul-haproxy. That way you can have high confidence that the only process able to configure the proxy is same consul-haproxy process that stated it.

My understanding from above is that generated password should be in memory and encrypted password saved to disk. What do you think?

LGTM


Is there an option to get skins from the game files and use them in cs lol manager?

not directly but I guess v can find files from internet
the problem is v need to convert them to a file format named ".fantome" or ".rar" archive which contains a ".wad.client" file
look for the example check out this link
https://drive.google.com/drive/folders/11fr3_4MIewpXalOG2fAhyTQdNVIxOrLR
It contains most of the skins but the problem is they r just unusable files in cs-lol-manager
there r few kinds of files type in these folders which is ".dds" ".SKL" ".SKN" and ".troybin"
so what then how can i use these files or actually let's say how can I convert these to a ".client" file?

All the guides use the obsidian program https://github.com/Crauzer/Obsidian/releases . And they just change the files they took out and change the textures and throw the new files into a new folder and then just throw that folder into cslolmanager and it works as a skin for example https://www.youtube.com/watch?v=yrWBEMLj-R8.

All the guides use the obsidian program https://github.com/Crauzer/Obsidian/releases . And they just change the files they took out and change the textures and throw the new files into a new folder and then just throw that folder into cslolmanager and it works as a skin for example https://www.youtube.com/watch?v=yrWBEMLj-R8.
so u can now use skins files and convert them into wad to use them in cs.lol manager?

not directly but I guess v can find files from internet the problem is v need to convert them to a file format named ".fantome" or ".rar" archive which contains a ".wad.client" file look for the example check out this link https://drive.google.com/drive/folders/11fr3_4MIewpXalOG2fAhyTQdNVIxOrLR It contains most of the skins but the problem is they r just unusable files in cs-lol-manager there r few kinds of files type in these folders which is ".dds" ".SKL" ".SKN" and ".troybin" so what then how can i use these files or actually let's say how can I convert these to a ".client" file?

bro the skins link doesn't contain any files
only names of the champs


更新最新版本以后，登录报错：找不到该用户，请重试

更新最新版本以后，登录报错：找不到该用户，请重试

更新以后会强制让当前用户的登录状态失效。请重启试下
如果还有问题，请按issue的模版提供相应信息，特别是日志记录
Describe the issue
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

**Logs: under ymir-workplace/ymir-data/logs

Error Message: in controller/app/hel-log
Trace stack

Additional context
Add any other context about the problem here.


feat(Templates): Updating Parameters Tab to Grid View to Align with Multi Workflow

Requirement Checklist

[X] The commit message follows our guidelines

Type of Change

[ ] Bug fix
[X] Feature
[ ] Other

Updating parameters tab to new design, aligning with multi workflow to display associated worklfow
Screenshots or Videos (if applicable)

Sorted by Name

Multi workflow (Showing Associated workflows)

After the tab has been moved to review+create and back (validation for the tab triggered)

5 mins - removing unwanted changes


[App Service] az logicapp create, az appservice plan create : Fix #20337 : add support for App Service Plan Logic App SKUs (WS1-3) and auto-creation of plans when creating a Logic App

Description

Allows the creation of App Service Plans with SKUs WS1, WS2, or WS3. These SKUs are used for plans that contain Logic Apps. This fixes #20337
Also changes the behavior of az logicapp create. If neither --plan nor --consumption-plan-location are specified, instead of failing, the command creates a WS1 App Service Plan to house the Logic App
Testing Guide

azdev test --live test_logicapp_commands
History Notes

[App Service] az logicapp create: Autogenerate a WS1 App Service Plan when no value for --plan or --consumption-plan-location is provided
[App Service] az appservice plan create: Allow creating App Service Plans for Logic Apps (SKUs WS1, WS2, and WS3)

This checklist is used to make sure that common guidelines for a pull request are followed.

[X] The PR title and description has followed the guideline in Submitting Pull Requests.

[X] I adhere to the Command Guidelines.

[X] I adhere to the Error Handling Guidelines.

@zhoxing-ms one of the extension loading CI tests here is failing with:
ERROR: Request to https://github.com/Azure/azure-hanaonazure-cli-extension/releases/download/0.6.5/sap_hana-0.6.5-py2.py3-none-any.whl failed with 403
Do you know what's causing this?

@StrawnSC This is a issue related to other extensions. Could you address those conflicts for this PR first?

Hi, Do we have a solution for this issue? i am unable to create a Logic app with sku WS1, there is no argument to pass either sku or a app service plan name. Please suggest

Sorry you're running into an issue here, @Poonamn91.
When I run az appservice plan create -n <plan_name> -g <group_name> --sku WS1 (filling in <plan_name> and <group_name> with the desired name and resource group name), it successfully creates a WS1 app service plan.
Please ensure you're using the latest version of the azure CLI. You can upgrade your CLI version with az upgrade. When  you run az --version, you should see the CLI version shown as 2.34.1

@StrawnSC  thanks for the reply. We are also trying to assign the app service plan to the logic app. But it's not applying the standard sku , it is creating with basic sku. Please suggest the command for logic app to pass the sku ws1.

Hi Team, can someone please suggest a command to create a logic app with Standard Sku, not able to find a argument to pass sku.

@Poonamn91 as per this doc for logic app standard the following are the supported SKUs https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-pricing#standard-pricing  (Ws1, ws2, ws3) & these are supported using CLI as well.


Add builder extension methods

Fixes https://github.com/aspnet/Identity/issues/849
Fixes https://github.com/aspnet/Identity/issues/565

@divega @blowdart

@divega look good?

@divega says :shipit:

27f021ab933a153eb977318e844a74f8497e3b47


AI: Basic scheduling facilities

While this is optional in most cases when the AI is simple, when the size of the simulation increases, pathfinding requests, heatmap generation, state/behavior tree updates etc can become cumbersome and slow the simulation down, requiring a lot of manual labour to determine when/if a particular AI action needs to run.
A scheduling system alleviates some of that work by centralizing work inside of jobs which can be prioritized and changed with frequency, and offset with a phase.

Having a facility like that for this project and future ones, but also to cover often requested topics like optimization is most welcome :)


feat: ASAP-211 Convert auth-frontend to Vite

basic setup
add dist to gitignore
use dist output to upload to auth0 and s3
add preset to auth-frontend to support import.meta

I wanted to look at the build output but this seems to have broken the artifacts created

This error also seems due to your changes

 This error also seems due to your changes

its not


Configure

@derevnjuk , for your review. There are couple of additional minor issues, that I will merge later today, but this contains the full implementation

@derevnjuk , most of the comments for client and cli are addressed.  please review

@gmesserman there's still a few unresolved issues and couple new ones. Also, please format code in the client, HTML and SCSS are readable hardly.


[WIP] 201712 mappings refactor

Coverage decreased (-0.5%) to 86.486% when pulling c08dca414f94ebbebb06f3ea3d53d0b2f916e13f on 201712-mappings-refactor into 66ae48fa89312dfcd506b231ebce7ba62aafefc1 on master.


manage.py get_email is not working

File "/usr/lib/python3.5/ssl.py", line 377, in wrap_socket
_context=self)
File "/usr/lib/python3.5/ssl.py", line 752, in init
self.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 988, in do_handshake
self._sslobj.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 633, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:645)
This is an error I am receiving. I tried with 3 different email ids across multiple service providers.
Any ideas on what I am missing?

I am also getting the same issue.Is there anyone who can help me on this?

Are you using POP or IMAP? With what email service? A google search suggests that the port being used might be wrong. Check your service settings and ensure the correct port is set in your configuration. The default is 993 (IMAP) or 995 (POP) for SSL but that may not be what your service expects.

Thanks for the reply and we have figured out the problem last week itself. Its going to be a issue with Imap folder. Everything is working fine for now.

OK great! @ramdaz does that fix your problem too? If you are using IMAP, ensure that you set the correct folder name in the queue settings. The suggested default is INBOX but it could be a different name depending on your service provider.


⚠ Bofrost.es has degraded performance

In 5a80b52, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1571 ms

Resolved: Bofrost.es performance has improved in b5fd358 after 6 minutes.


Feat: Strong Password Recommendation Feature

What feature?
Strong Password Recommendation Feature
Problem Description
In the registration section of a web application, users are required to set a password. However, many users often choose weak passwords that are easy to guess, such as "password123" or "123456". Weak passwords can lead to security vulnerabilities, making accounts more susceptible to unauthorized access.
To enhance security, it's essential to suggest strong passwords to users who are registering for the first time. A strong password should be complex enough to resist brute force attacks and should include a mix of characters.
Solution
To address this issue, we will implement a strong password recommendation feature in the registration section. This feature will automatically generate and suggest a strong password when a user is registering. The suggested password will follow best practices for password security, including:

A minimum length of 12 characters.
A combination of uppercase and lowercase letters.
Inclusion of numerical digits.
Inclusion of special characters (e.g., !, @, #, $).

Add screenshots

Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue

Hi @driyash9881
The issue is addressed and fixed in #325 so I am closing this issue.

This feature will automatically generate and suggest a strong password when a user is registering. The suggested password will follow best practices for password security

We can implement that. What will be your process? Are you going to use some libraries or is it using some strategy? let me know


Annotation point not displaying correctly with logarithmic

Annotation point y position is not accurate when yaxis is set to logarithmic

@junedchhipa this issue still occurs in the latest version. (v3.35.5)
All points get positioned at the bottom regardless of their 'y' value.
It can be replicated in the annotations demo by setting the y-axis to logarithmic.
https://codepen.io/apexcharts/pen/GXOJXQ


a sentence in stats.norm's docstring seems incorrect

Specifically, norm.pdf(x, loc, scale) is identically equivalent to norm.pdf(y) / scale with y = (x - loc) / scale.  Here,'pdf' should be cdf.

Thanks @clwez this repo is for the website and it's related machinery. Please use the SciPy repo for the content.
https://github.com/scipy/scipy/issues


Automate Version upgrades

Add a periodic workflow to circleci upgrading dependencies, and running them against the current test harness.
Test only dependencies which raiden does not require.
Test each dependency sequentially, dropping any upgrades that would break the tests.

This is the right issue ;)
Within the light client project we looked into dependabot and renovate
Maybe @nephix or @kelsos could give an advice

Related light client issue: https://github.com/raiden-network/light-client/issues/345
So far we tried dependabot but it creates a new pull request for each dependency update, and rebases each PR on merge again, which triggers a lot of CI workflows each time.
So we're looking for a solution as well that batches dependency updates together

You could certainly skip the CI on rebases, no? Separate PRs per dependency doesn't seem like a bad thing either. At least for us that seems like what we're looking for mostly. I'll have a look

Ideal for us would be (@kelsos please correct me if I'm wrong) a single pull request per week with all updated dependencies from that week. That pull request then triggers CI tests and we can quickly do manual tests to see if something broke even though tests succeeded. If everything went well, we simply merge the PR.

Shouldnt your test harness cover the testing? Circle can run tests (even specific once for compatibility checks, if you so want) on PRs submitted by the bot, and all you need to check is if the checks passed. But alas, that's your decision to make, of course.
 There also shouldn't be too many updates per-week (aside from probably the first time it runs).

Nils for the light client the initial checks where too much but yes
afterward it should be easier, especially if you go with live updates.
Initially, I was thinking of batching to avoid spam on the CI but I can see
the merit on having a per-dependency approach. Also, the weekly schedule
makes less sense if you go on a per-dependency approach.
I am not sure if you can currently skip the ci on rebase, but there are
some issues in that regards open for dependabot.
On Wed, Oct 30, 2019 at 1:33 PM Nils Diefenbach<EMAIL_ADDRESS>wrote:

Shouldnt your test harness cover the testing? Circle can run tests (even
specific once for compatibility checks, if you so want) on PRs submitted by
the bot, and all you need to check is if the checks passed. But alas,
that's your decision to make, of course.
 There also shouldn't be too many updates per-week (aside from probably
the first time it runs).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/raiden-network/scenario-player/issues/91?email_source=notifications&email_token=AARKEJF3XSMF2F5UFCXSM6TQRF5KPA5CNFSM4IAXMBSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECT7ULI#issuecomment-547879469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARKEJDV5DWX4JRAG3LYJOLQRF5KPANCNFSM4IAXMBSA
.

Circle can run tests (even specific once for compatibility checks, if you so want) on PRs submitted by the bot, and all you need to check is if the checks passed

It's not a good idea to test all updates in one go (hence me favoring the per-dependency PR approach), since that can make debugging a pain in the ass

I guess CircleCI is pay-as-you-go and some of our tests are also quite heavy. So it's not only a technical question

There also shouldn't be too many updates per-week (aside from probably the first time it runs).

That's true, even though NPM is moving quite quickly. Not sure about the python world

I guess CircleCI is pay-as-you-go and some of our tests are also quite heavy. So it's not only a technical question

Money should be the least of your concerns - especially if that saves you time manually testing a dependency upgrade. Chacnes are pretty good that the CI is cheaper than you.

I am not sure if you can currently skip the ci on rebase, but there are
some issues in that regards open for dependabot.

I'm sure there's a sensible approach to allowing this somehow. But that can be discussed when we get to it.

That's true, even though NPM is moving quite quickly. Not sure about the python world

Ach right, you're silly JS people, I forgot :smiley: you can of course always fine-tune the timeframes. Asides from that, it's probably even more important because of that, to automate away as much as possible of this.

Ach right, you're silly JS people, I forgot smiley you can of course always fine-tune the timeframes.

At heart, I am still an Android/Kotlin person, although I deal more with JS nowadays :P
But yes having an automated way to keep dependencies updated, ensuring that there is no breaking is really a time saver.

you're silly JS people

Compliment taken

This is implemented.

This is implemented.


v<IP_ADDRESS> does not support version 2.0 key files

I've been trying to use the module with a KeePass database secured by a key file with format version 2.0 as recommended by KeePass v2.47. The module fails to connect to the database stating that the composite key is invalid. Switching to format version 1.0 for the key file works.

Hi @ReneSchumacher, thanks for reporting.
Since that new file format is very new in 2.47, my downstream library I'm using for cross-platform (pt.keepasslib) hasn't reached that version yet, so this is currently unsupported.
https://github.com/panteam-net/pt.KeePassLibStd/discussions/8
I'll leave this issue open until a 2.47 .NET standard library is available to upgrade to.

Hey,
that's what I thought. Just wanted to let you know. Switching to 1.0 format is an easy workaround.

@ReneSchumacher if there's an extended period before the new library gets released maybe I'll add a quick check to look for the new format and throw a warning.

This is no longer blocked: https://github.com/panteam-net/pt.KeePassLibStd/discussions/8#discussioncomment-390719
I will try to add the feature in the next couple days.

@ReneSchumacher Keyfile v2 support should be in <IP_ADDRESS>


modules/autopairs: use boolToString instead of toLuaObject

Not that important, but I didn't realize that function existed before

toLuaObject should automatically apply the correct type (which in this case, is a string). Not sure if this change is really necessary. But it is probably a more concise solution.


Postman files missing?

After doing latest scoop update and scoop update postman, I get the following:
Installing 'postman' (6.1.2) [64bit] The remote server returned an error: (404) Not Found. URL https://dl.pstmn.io/download/6.1.2/Postman-win64-6.1.2-full.nupkg#/dl.7z is not valid
Gets the same for a 'scoop install postman' after an uninstall.

Fixed, obsolete


proposal: ignore push events for dependabot branches

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the issue has not already been raised

Issue
When dependabot opens a PR to update a dependency, it runs the whole ci pipeline twice. Once by push and once by pull request event. We could actually save one ci run when we would ignore the dependabot branch in push events.
We could actually configure, that only push events into master, main and next result in a pipeline run.

Will take a look.
Less CI runs would mean less resources/bandwidth wasted and less time waiting.

Exactly. When we e.g. activated license-check it always run twice, clogging the github runners.
Thank you. :)

something like:
on:
  push:
    branches:
     - main
     - master
     - next
    paths-ignore:
      - 'docs/**'
      - '*.md'
  pull_request:
    paths-ignore:
      - 'docs/**'
      - '*.md'

would solve this, not just for Dependabot PRs but for all PRs. Your recent PR to fastify-helmet ran it twice as well: https://github.com/fastify/fastify-helmet/pull/195

@Fdawgs are you using https://github.com/Eomm/massive-wax?

@Fdawgs are you using https://github.com/Eomm/massive-wax?

No, just using a horrible shell script 😂

PR made to all Fastify repos to add this.


[KYUUBI #1944] Upgrade Spark 3.1.3

Why are the changes needed?

close #1944
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Thanks, waiting #1947

Thanks, merging to master


[No ticket] Delete unused action

I noticed this action is only triggered on releases, but we never make releases through Github for this library. It looks like it's only ever been run once: https://github.com/DataBiosphere/terra-common-lib/actions/workflows/publish-release.yml

We still bump the version and publish artifacts to Artifactory, but it's triggered on PRs merging into the main branch via a different action instead of on a Github release being created. That's the same pattern we currently use in CRL - we used to publish Github releases, but don't anymore


Added my pixel

Checklist

[ ] I ran npm test locally and it passed without errors.

[ ] I only edited the _data/pixels.json file.

[ ] I entered the username in the pixels.json that I'm also using to create this pull request.
[ ] I acknowledge that all my contributions will be made under the project's license.

Done :) Thanks you


Benchmark Hummingbird for model compilation

Benchmark Hummingbird: https://github.com/microsoft/hummingbird
We should test on XGBoost & LightGBM, and try out the GPU support, to see if we can get a meaningful inference speedup.

@liangfu any prior knowledge on hummingbird? Do you think we should try it out?


[stable/datadog] fix various whitespace and missing separator issues

Signed-off-by: Joe Hohertz<EMAIL_ADDRESS>@mfpierre
What this PR does / why we need it:
Some recent refactoring of the templates resulted in broken manifests when rendering, with some lines inappropriately joined, or separators missing between different manifest items. The chart is simply broken for some configurations, such as using RBAC. This patch remedies that.
Which issue this PR fixes
No known open issues relating to this.
Special notes for your reviewer:
None
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])

Re-based and re-bumped version.

hi @jhohertz,
The PR #15577 was merged and provide the same fix.

/hold

The other PR seems to do it, thanks, closing this one off.


Create a Forum Post Component.

[ ] Refer to the Figma design.
[ ] Use SVGs for like, comment and social media icons.
[ ] Make it responsive. Use correct breakpoints for media queries.
[ ] Refrain from using fixed widths and heights.
[ ] Use existing components wherever necessary.

I want to work on this

Is the issue open?

Is the issue open?

@inomag 1 dev is already working on it. : )

@inomag 1 dev is already working on it. : )

@Shubham-1105 Please continue with this.

@Shubham-1105 Please continue with this.


Add Options based configuration into CLI and Examples for BlueGiga

[ ] Create a construction-injectable Options object for BlueGiga
[ ] Refactor the CLI service provider builder process to better incorporate the command line (and maybe a json file ... so user can spare the arguments). Use Microsoft.Extensions.Configuration.CommandLine features maybe.

BlueGiga in focus because currently the only one needing configuration
See details in #154

An options object would be useful for BlueZ implementation too. Mainly to specify a specific bluetooth adapter (eg hci0) instead of simply using the first available one. Kind of optional since multiple available bluetooth adapters seems like a bit of a edge case.
Maybe best to open a separate issue to complete if this one is done?

Let us focus on finishing bluez first. We see which delivery beat which and then we adjust :)

I've tested today with BlueGiga on a RaspberryPi with the actual Master-branch - works like a charme!
The BleuGiga-adapter gets recognized on the Pi without any additional installation and is just a SerialPort:
./SharpBrick.PoweredUp.Examples --usebluegiga /dev/ttyACM0
..and it works. Also with two Hubs in parallel (ExampleTwoHubsMotorControl) 😄
Surley I had to remove the dependency on the SharpBrick.PoweredUp.WinRT from SharpBrick.PoweredUp.Examples because WinRT cannot build for linux-arm target. Also instead of net5.0-windows10.0.19041.0 just only use net5.0 in the TargetFramework
for Examples and BleuGigaBLE. And some small changes in BaseExample.cs(comment line 97 which is calling AddWinRTBluetooth() and Program.cs (just for making sure the options are given over to InitHostandDiscoveryasync(); line 82 instead of 80)
publish for Raspberry Pi:
cd GitHub\sharpbrick\powered-up\examples\SharpBrick.PoweredUp.Examples
dotnet publish -r linux-arm -o bin\\linux-arm\\publish --no-self-contained

Why do I mention it here?
Because we need to think about how to separte the different BLE-implementations into different independent Nuget-packages later, so it gets easy to build for differnt platforms. With Bluez-implementation in near future it will be an additional candidat which probably will not compile for windows-target.
So it should be  in mind also here...

Oh that is nice. Create a PR updating the README
second: Yes, I agree. We need to decouple the dependency to the bluetooth stacks in the tools etc. There is a "plugin"-like concept called AssemblyLoadContext which can load assemblies at runtime. With a small generic helper, all the CLI, Examples, TestScript Runner can dynamically load an adapter. The only thing I am not sure is, does it work with the -windows target when called from a command line part. To be tested. In doubt, we can multi-target.

I've tested on a Raspberry Pi 4. I will do another test on a Raspi 3 and also on an Ubuntu 20.0 LTS (PC-based). As soon as I have finished these tests, I will update the README. Shall I go for an own file BlueGigaReadme.md for bringing all the information for BlueGiga centralized or put it into the big README? It's  more a question of wanted style from your side.

That is indeed a good idea. Put it somewhere reasonable in the docs folder and link it from the main readme. That declutters the project start page.


Wrong padding of dropdown menu icons in Editor

Godot version
v3.6 beta3 official
System information
Windows 10, OpenGL ES 3.0 Renderer
Issue description
All icons in dropdown menus in the Editor are having wrong padding.
Here you see the file menu when rightclicking a file in the FileSystem (v3.6 beta3):

In Godot 3.5.3 the icons were still fine:

Steps to reproduce
Open the v3.6 beta3 official Editor and open a menu with icons in it.
Minimal reproduction project
Only the Editor is needed for testing

This appears to be the case since 3.6.beta1. I'll look into bisecting this.

If this was reported in 3.6.beta3 why is the milestone set to 4.x?

If this was reported in 3.6.beta3 why is the milestone set to 4.x?

Fixed.

This was fixed by https://github.com/godotengine/godot/pull/81409


APAAS-3046 Update tool to assist quality assurance of production-like environments

Hi @HartS
Could you update https://github.com/hpcloud/stackato-cluster-tool/blob/master/terraform/amazon-aws/provider-amazon-security-groups.tf instead?


Screening Status doesn't show up in detailed view

For screening a bigger amount of submissions or revisiting the screening status of submissions, it would be helpful to have them as sections in the detailed view too. That would make it way easier for others to run through them and confirm the Out of Remit status.

@arduina I've added the screening status to the status bar as part of #1079


WASM Support

Hey guys!
I was wondering if you are planning on releasing the library for kotlin multiplatform web with WASM as well.
kind regards

No one is actively working on such a thing, but I'd happily accept a PR for it.


Click on play button

man, i think there's no need pull request. the location click in other device might be different. i try your pull request version but not work, it only click random position in outside telegram window.

man, i think there's no need pull request. the location click in other device might be different. i try your pull request version but not work, it only click random position in outside telegram window.

join t.me/chatbutlazy to discuss it


Addition of table of contents in  ReadMe.md

Addition of table of contents allows
Users to access information on readme easily. As they can direct go to the required information

I can help with adding some contents to the project so do assigne me this issue under GSSOC'23

I would like to work on the issue as a contributor of GSSoC23.
Please assign me the issue.


Forgot password | Can't log in | Facebook_loginfacebook_login<PHONE_NUMBER>

Reset your password
Reset your password
How do you want to get the code to reset your password?
Send code via email
c***@*******
Send code via Facebook notification
You're logged in on another app or device. Get a notification with a login code.
Send code via SMS
+526181274840
Send code via SMS
+**********62
Enter password to log in
6181274840
Facebook user
Not you?Continue
English (US)
Español
Português (Brasil)
Français (France)
Italiano
Deutsch
العربية
日本語
हिन्दी
中文(简体)
Sign UpLog InMessengerFacebook LiteVideoPlacesGamesMarketplaceMeta PayMeta StoreMeta QuestMeta AIInstagramThreadsFundraisersServicesVoting Information CenterPrivacy PolicyPrivacy CenterCookie SettingsGroupsAboutCreate adCreate PageDevelopersCareersCookiesAd choicesTermsHelpContact Uploading & Non-UsersSettingsActivity log
Meta © 2024```
``
Reset your password
Reset your password
How do you want to get the code to reset your password?

Send code via email
c***@*******

Send code via Facebook notification
You're logged in on another app or device. Get a notification with a login code.

Send code via SMS
+526181274840

Send code via SMS
+**********62

Enter password to log in

6181274840
Facebook user
Not you?Continue
English (US)
Español
Português (Brasil)
Français (France)
Italiano
Deutsch
العربية
日本語
हिन्दी
中文(简体)
Sign UpLog InMessengerFacebook LiteVideoPlacesGamesMarketplaceMeta PayMeta StoreMeta QuestMeta AIInstagramThreadsFundraisersServicesVoting Information CenterPrivacy PolicyPrivacy CenterCookie SettingsGroupsAboutCreate adCreate PageDevelopersCareersCookiesAd choicesTermsHelpContact Uploading & Non-UsersSettingsActivity log
Meta © 2024

Reset your password
Reset your password
How do you want to get the code to reset your password?
Send code via email
c***@*******
Send code via Facebook notification
You're logged in on another app or device. Get a notification with a login code.
Send code via SMS
+526181274840
Send code via SMS
+**********62
Enter password to log in
6181274840
Facebook user
Not you?Continue
English (US)
Español
Português (Brasil)
Français (France)
Italiano
Deutsch
العربية
日本語
हिन्दी
中文(简体)
Sign UpLog InMessengerFacebook LiteVideoPlacesGamesMarketplaceMeta PayMeta StoreMeta QuestMeta AIInstagramThreadsFundraisersServicesVoting Information CenterPrivacy PolicyPrivacy CenterCookie SettingsGroupsAboutCreate adCreate PageDevelopersCareersCookiesAd choicesTermsHelpContact Uploading & Non-UsersSettingsActivity log
Meta © 2024```
``
Reset your password
Reset your password
How do you want to get the code to reset your password?

Send code via email
c***@*******

Send code via Facebook notification
You're logged in on another app or device. Get a notification with a login code.

Send code via SMS
+526181274840

Send code via SMS
+**********62

Enter password to log in

6181274840
Facebook user
Not you?Continue
English (US)
Español
Português (Brasil)
Français (France)
Italiano
Deutsch
العربية
日本語
हिन्दी
中文(简体)
Sign UpLog InMessengerFacebook LiteVideoPlacesGamesMarketplaceMeta PayMeta StoreMeta QuestMeta AIInstagramThreadsFundraisersServicesVoting Information CenterPrivacy PolicyPrivacy CenterCookie SettingsGroupsAboutCreate adCreate PageDevelopersCareersCookiesAd choicesTermsHelpContact Uploading & Non-UsersSettingsActivity log
Meta © 2024


update pixi packages

I don't think this is the correct fix. It's not maintainable to bump this every time PixiJS does a release. I'm going to fix this by making the @pixi/* packages peerDependencies instead, which is probably what they should've been in the first place.


Raw constructor

Hi, I had a situation in which I needed to run Jimp on over 2000 jpegs. The profiler showed it was spending a lot of time in jpeg encoding/decoding, so I switched to using a C-based jpeg decoder. In order to get things back to Jimp to do further processing, I needed Jimp to be able to accept raw buffers (not jpeg buffers), so I added this constructor.

There's another similar pull request: #203

closing in favor of #514


Strange behavior with defaultValues

I am using version 3.4.4
In my parent component, I am creating a defaultValues object in the constructor. This object is either empty if the user is not logged in or has values if the user is logged in. I tried both with having this object be part of the component state and as a class variable. The values needed to build the defaultValues object are being read from a cookie so its not an async function. In my render function, I have:
<Form  					component={ContactFormFields}  					onSubmit={this.handleSubmit}  					validate={this.handleFormValidation} 					defaultValues={this.defaultValues} 				/>
When the page first loads, the default values do not show up. When I click on one of the text input fields that does have a default value assigned and take the focus away from it, then the default value appears. Any thoughts on whether I am misusing the defaultValues prop or there is something wrong?

Hmm interesting.. I just created this code sandbox and this seems to work fine there. https://codesandbox.io/s/vj781lzrq0

Are you sure you have no console errors?

I don't have any console errors and I am not pulling the default values from an async function so I do it have them available on first render. Let me double check everything by comparing to your code sample and get back to you.

Also try with the latest version 3.5.0

Sorry, this issue was on my side. I was getting default values from a cookie and it indeed was not available on the first render. I am going to instead use setValue. Thanks for your help and this awesome library!


test: Change test case for "In" & "Equals"

In tests/test_validator.py
test_in and test_equals looks likes the same as test_truthy

Well that's a little embarassing. Thanks for the fix.


Storefinder should work without e2econfigurationwebservices

Need to add more info here, but we suspect that maybe the storefinder code is dependent on the walker's special scc module, which we don't want in generic spartacus.

@Xymmer
This issue was covered in #824

no longer needed, closing


Allow integration tests to specify what project to generate assets for

This is great. It will reduce our build times definitely. Thanks :1st_place_medal:


Negative expectation failures should be surfaced during verification

Consider the following app:
Gemfile:
source "https://rubygems.org"
ruby '2.1.5'

gem 'sinatra', git: 'https://github.com/sinatra/sinatra.git', ref: 'b39d72d'
gem 'sentry-raven', '~>0.12.2'
gem 'rspec', '~>3.1.0'
gem 'rack-test', '~>0.6.2'

1.rb:
require 'rubygems'
require 'bundler/setup'

require 'sinatra'
require 'sentry-raven'

Raven.configure(true) do |config|
  config.dsn = '...'
end

use Raven::Rack

get '/' do
  raise 'test exception'
end

ENV['RACK_ENV'] = 'test'

require 'rack/test'

describe 'app' do
  include Rack::Test::Methods

  def app
    @app || Sinatra::Application
  end

  it 'passes errors to Raven' do
    expect(Raven.client).not_to receive(:send)
    # expect(Raven.client).to receive(:send)   # works the same as previous line
    get '/'
  end
end

Additionally, I've added some debug statements:
https://github.com/getsentry/raven-ruby/blob/0.12.3/lib/raven/base.rb#L75:
    def send(evt)
puts 'inside Raven.send'
p client.method(:send).source_location
      client.send(evt)

https://github.com/getsentry/raven-ruby/blob/0.12.3/lib/raven/client.rb#L25:
    def initialize(configuration)
puts 'inside Raven::Client.initialize'
      @configuration = configuration

https://github.com/getsentry/raven-ruby/blob/0.12.3/lib/raven/client.rb#L19:
    def send(event)
puts 'inside Raven::Client#send'
      unless configuration.send_in_current_environment?

Then, when I run the spec:
$ rspec 1.rb
inside Raven::Client.initialize
D, [2015-01-21T13:15:45.492433 #19390] DEBUG -- : ** [Raven] Collecting RuntimeError: test exception
inside Raven.send
["/home/yuri/.gem/ruby/2.1.5/gems/rspec-mocks-3.1.3/lib/rspec/mocks/method_double.rb", 59]
.

Finished in 0.07989 seconds (files took 0.40847 seconds to load)
1 example, 0 failures

But the test should fail. Now if I comment the expectation out:
inside Raven::Client.initialize
D, [2015-01-21T13:16:47.920593 #19406] DEBUG -- : ** [Raven] Collecting RuntimeError: test exception
inside Raven.send
["/home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/client.rb", 26]
inside Raven::Client#send
D, [2015-01-21T13:16:47.933273 #19406] DEBUG -- : ** [Raven] Sending event 39925f25c66832e9c9dcaa47059d0a6f to Sentry
E, [2015-01-21T13:16:48.016546 #19406] ERROR -- : ** [Raven] Unable to record event with remote Sentry server (Raven::Error - Unknown transport scheme '')
E, [2015-01-21T13:16:48.016722 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/client.rb:91:in `transport'
E, [2015-01-21T13:16:48.016761 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/client.rb:45:in `send'
E, [2015-01-21T13:16:48.016798 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/base.rb:78:in `send'
E, [2015-01-21T13:16:48.016835 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/base.rb:116:in `block in capture_exception'
E, [2015-01-21T13:16:48.016871 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/base.rb:143:in `send_or_skip'
E, [2015-01-21T13:16:48.016907 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/base.rb:110:in `capture_exception'
E, [2015-01-21T13:16:48.016943 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/integrations/rack.rb:29:in `capture_exception'
E, [2015-01-21T13:16:48.016978 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/integrations/rack.rb:66:in `rescue in call'
E, [2015-01-21T13:16:48.017013 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/sentry-raven-0.12.3/lib/raven/integrations/rack.rb:60:in `call'
E, [2015-01-21T13:16:48.017060 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'
E, [2015-01-21T13:16:48.017096 #19406] ERROR -- : ** [Raven] /home/yuri/.gem/ruby/2.1.5/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'
E, [2015-01-21T13:16:48.017136 #19406] ERROR -- : ** [Raven] Failed to submit event: RuntimeError: test exception
.

Finished in 0.15771 seconds (files took 0.40316 seconds to load)
1 example, 0 failures

And now consider using mocha:
Gemfile:
...
gem 'rack-test', '~>0.6.2'
gem 'mocha', '~>1.1.0'

1.rb:
require 'rubygems'
...
require 'rack/test'

RSpec.configure do |config|
  config.mock_with :mocha
end

describe 'app' do
  ...
  it 'passes errors to Raven' do
    Raven.client.expects(:send)   # Raven.client.expects(:send).never
    get '/'
  end
end

Then:
$ rspec 1.rb
inside Raven::Client.initialize
D, [2015-01-21T14:04:10.503716 #23500] DEBUG -- : ** [Raven] Collecting RuntimeError: test exception
inside Raven.send
["/home/yuri/.gem/ruby/2.1.5/gems/mocha-1.1.0/lib/mocha/class_method.rb", 62]
.

Finished in 0.08241 seconds (files took 0.45779 seconds to load)
1 example, 0 failures

And with .expects(:send).never:
inside Raven::Client.initialize
D, [2015-01-21T14:05:04.584304 #23556] DEBUG -- : ** [Raven] Collecting RuntimeError: test exception
inside Raven.send
["/home/yuri/.gem/ruby/2.1.5/gems/mocha-1.1.0/lib/mocha/class_method.rb", 62]
F

Failures:

  1) app passes errors to Raven
     Failure/Error: Raven.client.expects(:send).never
     Mocha::ExpectationError:
       not all expectations were satisfied
       unsatisfied expectations:
       - expected never, invoked once: #<Raven::Client:0x7f2315649490>.send(any_parameters)
     # ./1.rb:33:in `block (2 levels) in <top (required)>'

Finished in 0.05607 seconds (files took 0.42729 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./1.rb:32 # app passes errors to Raven

Well, it must be because sinatra was running in development environment and catched all exceptions to show them in a pretty way (show_exceptions settings). In other words, ENV['RACK_ENV'] = 'test' must be before require 'sinatra'.

Yep

I've dug into this a bit to understand why mocha works correctly here while RSpec doesn't and I see what's going on.  When you expect that a message is not received with rspec-mocks, it prepares the object so that if it does receive the message, it will raise an exception immediately at that point of time and halt the example with that failure.  If the exception is rescued (which is what sinatra does when ENV['RACK_ENV'] is not "test"), then the example will pass because the failure that RSpec was triggering was caught and silenced.
In mocha, it also raises the error immediately, but it also has logic in the end-of-example mock verification that fails the example again if a message was received that was specifically expected to not be received.  Thus mocha is immune to intermediaries rescuing the eager error while RSpec is not.
I think this is something we can and should fix -- as you found, users aren't always aware that their web framework is rescuing and silencing errors for them, and in those situations RSpec's behavior can appear baffling.

We can close this because of #884


[ENH] - Consider using OS-specific standards for conda-store data

Feature description
As part of #513, it was suggested to use ~/.conda-store as the default data directory. This was implemented successfully in https://github.com/conda-incubator/conda-store/pull/639.
I am suggesting we stick to well defined standards for this kind of decisions, instead of polluting the home directory with one more dot-folder. Namely:

On Linux, follow XDG Base Directory Specification

On macOS, it seems that CLI apps still follow XDG standards as Linux. GUI stuff drops things in ~/Library. See this SO thread.
On Windows, we should probably use %LOCALAPPDATA% (i.e. non-roaming).

Value and/or benefit
Following well established standards in each Operating System allow us to be better citizens, and navigate better known spaces (e.g. permissions, lack of user profiles in some Windows installations).
A nice side effect, and one of the reasons these standards exist, is to avoid polluting the user profile with dot-directories.
Anything else?
Comes from https://github.com/conda-incubator/conda-store/pull/639#issuecomment-1787555517

ArchWiki list, with links to various issues: https://wiki.archlinux.org/title/XDG_Base_Directory_support

Yeah totally agree we should use system defaults

conda is going to switch to platformdirs (instead of the vendored appdirs), which seems to abstract away all the complicated business:
https://platformdirs.readthedocs.io/en/latest/index.html

Status update: not working on this until other issues in the milestone are resolved.


Song info is broken for some players

Description
Commit e6b8f4f broke some players that use a query command with a format string.
e.g.: deadbeef --nowplaying-tf '%artist% \n %album% \n %title%'
The newline in the format string is not interpreted/printed as was intended.
I have not tested all players that use a query command with format string,
but at least deadbeef, rhythmbox and qmmp are affected.
Neofetch version
git
Screenshot
deadbeef

rhythmbox, qmmp

Rhythmbox can use get_song_dbus, see #1110
A possible solution for the other affected players would be to add back separator to the query commands and then pipe the output to awk.
        "deadbeef"*)    "$(deadbeef --nowplaying-tf '%artist%-@-%album%-@-%title%' |
                           awk -F'-@-' '{print $1"\n"$2"\n"$3}')"
        ;;

And perhaps add a function.
    get_song_query() {
        song="$(eval "${1}" | awk -F'-@-' '{print $1"\n"$2"\n"$3')"
    }

    case "${player/*\/}" in
        ...
        "deadbeef"*)      get_song_query "deadbeef --nowplaying-tf '%artist%-@-%album%-@-%title%'" ;;
        "qmmp"*)          get_song_query "qmmp --nowplaying '%p-@-%a-@-%t'" ;;
        and so on
        ...
    ;;

What do you think @dylanaraps ?

No eval.
I have a laptop again so I'll try and fix this tomorrow.


Icon doesn't render properly when using SVG and fa-icon

Using  SVG to be able to apply RGB color on an Extra Marker icon, it is not rendering properly the icon. As you can see in the image below, the fa-bolt icon is below the marker and there is a red shadow.

That is my code to create the extra marker:
var customIcon = L.ExtraMarkers.icon({
icon: 'fa-bolt',
markerColor: '#3deb47',
shape: 'start',
prefix: 'fa',
svg: true
});
What have I missed?

The only problem I see is that the value for shape should be "star" not
"start".  (but that might just be a typo in the issue...)
On Thu, Aug 6, 2020, 3:28 PM leonardotvd<EMAIL_ADDRESS>wrote:

Using SVG to be able to apply RGB color on a Extra Marker icon, it is not
rendering properly the icon.
[image: GreenStartBoltIcon]
https://user-images.githubusercontent.com/48744269/89588844-997dab80-d898-11ea-8b41-04b75e1cde90.png
That is my code to create the extra marker:
var customIcon = L.ExtraMarkers.icon({
icon: 'fa-bolt',
markerColor: '#3deb47',
shape: 'start',
prefix: 'fa',
svg: true
});
What have I missed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/coryasilva/Leaflet.ExtraMarkers/issues/55, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUMSTCBLFABKSR6A7RN65DR7MVBZANCNFSM4PXBEIIQ
.

Even changing "start" to "star", it is showing wrong. Can you see that red shade behind the start and also the bolt icon under the marker? Is that right?

@leonardotvd Did you ever resolve this issue? (sorry for the 1 year later follow up... life)

Hi, same problem here. Using SVG the icon is not in the correct position.
I have found this workaround. You have to set an extraClass to the marker icon and then you can add a CSS. In my example I used the following options:
L.ExtraMarkers.icon({
extraClasses: 'translate-to-markers',
icon: 'fa-circle',
iconColor: 'white',
markerColor: '#feb96a',
shape: 'circle',
prefix: 'fa',
svg: true
});
and my css:
.translate-to-markers {
transform: translate(11px, -41px);
}

This is was causing the issue for me. Setting icon to true (or to any string at all) made my Marker show up on the map.
https://github.com/coryasilva/Leaflet.ExtraMarkers/blob/c4f5f1e4184194b584ef112a609af7a1f91db172/src/assets/js/leaflet.extra-markers.js#L30C23-L30C23


fix place markers

@andreasviglakis these should be resolution independent SVG icons, they look bad, especially on retina:

sorry about this, changes are pushed @samanpwbb


Randmise some numbers to prevent block

Codecov Report

Merging #1197 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1197   +/-   ##
=======================================
  Coverage   43.65%   43.65%
=======================================
  Files          32       32
  Lines        3569     3569
  Branches      579      579
=======================================
  Hits         1558     1558
  Misses       1869     1869
  Partials      142      142

Impacted Files
Coverage Δ

instabot/bot/bot.py
77.12% <ø> (ø)
:arrow_up:

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 79bcb73...4d74039. Read the comment docs.

Did it help you to prevent from bans or you just suggest that this might help?

Its a suggestion that this might help. I do know that instagram is doing more and more to prevent bots. And with these high numbers its more likely people will get blocked.

@bruvv: As far as i understood you just changed the default values to more "odd" values.
What about using random.randint with a useful range?
For example:
like_delay=random.randint(7,15),
instead of
like_delay=39,
I guess performance is not the limiting factor if we use like 15-20 randint calls in the constructor instead of fixed values. And so each created bot instance is truly individual instead of just all new bot instances are now using an other fixed value. I suggest that this might be even better for instagram to not detected our bots.

@fighterii I have no idea why I didn't do that lol thanks for the headsup

Great. Again, please fix Travis Issues and I'll merge. Thanks!

 It's pretty strict ;)

You can try to use pre-commit
needs to do pip install pre-commit to install the package.
Then pre-commit install and pre-commit run --all to run it on the existing code.
The next commits after pre-commit install have been done (once ever) then it will do it automatically.

Thanks, It started as some simple edits on github itself that, tbh, I didn't even test. Since there is much to be improve I will start doing it locally from now on.

randint and randrange is almost the same:
https://docs.python.org/3/library/random.html#random.randrange

@ohld little help with these last errors? I installed pre-commit, ran it and all works just fine:

But when travis is doing it, it isn't passing the test.

@bruvv:
I think tests are getting more complicated with this change.
For example, if i check the travis build results:
INFO     [instabot_140343133661560]:bot_filter.py:9 Received 4 medias.
INFO     [instabot_140343133661560]:bot_filter.py:20 After filtration 0 medias left.

and the expected result:
>       assert len(medias) == results - expect_filtered
E       assert 0 == (4 - 3)
E        +  where 0 = len([])

because of randomised filter settings the checks sometimes will fail randomly.
I think best practice would be to use the old, default vals in the tests to initiate the bot instances.

@fighterii you are right indeed, I thought it had to do with the image not being found but it looks like some where there is a misscommunication in the build. Do you know how to adjust the build so the numbers get hard coded in it?

@bruvv
I would take a look at tests/test_bot.py
As far as i understand all tests use the TestBot class as BaseClass for their tests. In line 20 the bot is created with:
self.bot = Bot()
I guess the best would be to pass all arguments that you like to randomise here with there old default values, for example:
        self.bot = Bot(
            max_likes_to_like=100,
            min_likes_to_like=20,
        )

Good spot, let's see what travis thinks about it ;)

That did it! Great minds think alike thanks for the spot @fighterii
@ohld save to merge :) ?

merged! thanks!


feat: language select screen

I didn't realize tts could be enabled on other channels. Now the language selection screen is only visible if the broadcaster's language is set to asl or other.


Added RunTLS convenience function

Hi @cmsmith1977,
We discussed this feature before in #85 and opted to not include it (in lieu of adding documentation to the README about how to use negroni as a middleware library rather than starting a server). Please let me know what you think after reviewing that discussion.
Thank you!

Closing due to inactivity, but please feel free to reopen if desired!


v2.1.15 tags not available on registry

Hi,
I see a v2.1.15 release but for some reason I can't pull it?
  Warning  Failed     21s (x3 over 60s)  kubelet            Failed to pull image "ghcr.io/patrikjuvonen/docker-nginx-http3:v2.1.15": rpc error: code = NotFound desc = failed to pull and unpack
 image "ghcr.io/patrikjuvonen/docker-nginx-http3:v2.1.15": no match for platform in manifest: not found

Might be related to x64 builds, since arm64 works
Anyways, thanks again for this great image :)
cdr

Hi, thanks for reporting the issue!
I'll re-run the build, it was stuck for a couple of days. I'll ping you here when it should be available.

@githubcdr Should be fixed now!

It is, thanks man!


Update APIversion for Graph.RBAC Endpoint-getObjectsByObjectID from 1.6-internal to 1.6

Description
This API change is to fix  the following issue https://github.com/Azure/azure-powershell/issues/3407
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@darshanhs90,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

 https://github.com/Azure/azure-sdk-for-ruby/pull/744

 https://github.com/Azure/azure-sdk-for-python/pull/1068

 https://github.com/Azure/azure-sdk-for-node/pull/2130

No modification for Ruby


(chore) improve setting school website

Don’t set protocol if it’s website url is nil

@gazaston fixed!


feat(Footer): rename Pro Membership link

Overview

Global Footer: rename Pro Membership -> Paid Memberships in preparation for Plan Rename.

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: PX-6056
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change
[ ] This PR includes testing instructions tests for the code change
[ ] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions

Don't make me tap the sign.
PR Links and Envs

Repository
PR Link
PR Env

Monolith
Monolith PR
Monolith Env

Portal
Portal Link
Portal Env

Another Repo
Another Link
Another Env

🚀 Styleguide deploy preview ready!https://6390c693f35ef8489c171899--gamut-preview.netlify.appDeploy Logs


NuttX defconfig minor cleanup and improvements

remove all the unnecessary entries disabling NXFONTS
don't exclude procfs entries (enables df and a few other things)
enable tab completion and command line history on newer boards with plenty of memory (f7, h7, imxrt)

Example: df
nsh> df -h
  Filesystem    Size      Used  Available Mounted on
  cromfs        204K      204K         0B /etc
  vfat           14G       95M        14G /fs/microsd
  procfs          0B        0B         0B /proc

Example: tab completion (a tab)
nsh> a
  adc
  adis16448
  ak09916
  adis16477
  adis16497
  attitude_estimator_q
  airspeed_selector
nsh> a

TODO: review possible mavlink nsh issues
@davids5 I vaguely recall you encountered an issue with either tab completion or command line history with nsh over mavlink. What was the problem?

Rebased with the tab completion and history removed (we can try again later).


Fix bug in caching

Caching does not properly account for cached files "owned" by a job that was SIGKILLed, or one that failed on a node that was full enough to the point that even the cache file could not be updated. This PR will handle that issue to the best of Toil's ability. This is not critical to the 3.5 release.

False alarm


:fix MM injected browser not showing on ethers

Description
Fixed an issue where MM injected browser doesn't show up on ethers
Type of change

[ ] Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Associated Issues
For Linear issues: Closes APKT-xxx
For GH issues: closes #3244
Showcase (Optional)
If there is a UI change include the screenshots with before and after state.
If new feature is being introduced, include the link to demo recording.
Checklist

[ ] Code in this PR is covered by automated tests (Unit tests, E2E tests)
[ ] My changes generate no new warnings
[ ] I have reviewed my own code
[ ] I have filled out all required sections
[ ] I have tested my changes on the preview link
[ ] Approver of this PR confirms that the changes are tested on the preview link

please deploy to NPM @svenvoskamp


title: Added blog on nullable types in csharp

Checklist

Please note that in case of below checklist not updated accordingly, the maintainers have the right to immediately close your pull request.

[x] You created a branch from dev branch.
[x] You PR is raised on dev branch and not onmaster.
[x] Blog follows Blog Guidelines.
[x] You have read the Contribution Guidlines before creating this PR.
[x] Checked for any duplicate blog entry.
[x] Checked for all grammatical errors in the blog.
[x] You have not published the blog content anywhere else on the internet on platforms like medium, dev.to etc.
[x] The content is not copy-pasted from anywhere else on the Internet.

Description of change

Added blog on nullable types in csharp.
Author Details for Blog Post Entry

Id - Hemant Manwani

@puneetsingh24 @vyasriday Please review.

@puneetsingh24 @vyasriday Please review.


Improve error messages when creating star-tree indexes

This PR improves the error messages when star-tree or forward index creation end up failing due to integer overflow produced when chunks are too large.

Codecov Report
Attention: Patch coverage is 0% with 13 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (59551e4) to head (0698101).
Report is 885 commits behind head on master.

Files
Patch %
Lines

...cal/startree/v2/builder/BaseSingleTreeBuilder.java
0.00%
12 Missing :warning:

...al/io/writer/impl/BaseChunkForwardIndexWriter.java
0.00%
1 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (0698101). Click for more details.
HEAD has 48 uploads less than BASE

Flag
BASE (59551e4)
HEAD (0698101)

integration
7
2

integration2
3
2

temurin
12
2

java-21
7
2

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13818       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2483       +47
  Lines        133233   137525     +4292
  Branches      20636    21414      +778
=============================================
- Hits          82274        0    -82274
- Misses        44911   137525    +92614
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <0.00%> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <0.00%> (ø)

java-11
?

java-21
0.00% <0.00%> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <0.00%> (-61.75%)
:arrow_down:

skip-bytebuffers-true
0.00% <0.00%> (-27.73%)
:arrow_down:

temurin
0.00% <0.00%> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


add Icon, social graphic and update brand colors for steampipe hub

Updated the docs index and added social graphics/icon for use in steampipe hub

@dboeke Awesome, thanks for your work and the future inclusion on the hub!
There is one question on the icon_url, as the filename doesn't match the svg you uploaded.

Thanks for the update. I merged the PR manually.


Multiple requests going in case of request close

I am using Fresco with OkHttp 2.7.4. By default the image request from the previous activity won't get canceled when we switch to a new activity. This makes the new activity load slower as previous requests are still running. So I am closing the all the image requests in onStop() of my activity based on tag.
The request are getting closed, all good...But the requests are fired again to download the images from the previous activity. It is retrying to download the images again. I have setRetryOnConnectionFailure(false).
Not able to figure out what I am doing wrong. Not sure if Fresco is triggering new requests on cancel. I didn't find any configuration option with Fresco.
Please help. Thank you!

This was posted to StackOverflow (presumably by you) which is the correct place to ask usage questions.


Support AWS CDK v2

It would be great to release a cdk-triggers version that supports CDK v2 so that it could be used in v2 CDK projects.
I would like to use it for writing test assertions in projen CDK v2 projects.
Is there already a strategy to migrate libs like this one to CDK v2? Is it necessary to publish a v1 and a v2 version in parallel during a transition period? Or is it possible to migrate this repository to v2 and stop publishing the v1 version?

I think the most likely path forward would be to upgrade the library directly to support v2, since this is an experimental library, and since that's what we did with cdk-watchful and so far nobody has complained. :)

cdk-triggers has been bumped to v0.1.x to support CDK v2! 🎉

@Chriscbr Thank you very much. I updated my example project to the new version and it works fine.


Policy for inclusion in the flake search

Basically a mirror of https://github.com/NixOS/flake-registry/issues/25, triggered by https://github.com/NixOS/nixos-search/pull/482.
I think the policies should be somewhat similar between the two repos (if not tied together by only indexing flakes in the registry), and moreover I don't think nixos-search is currently ready to include every flake in the universe.

I think the issue the registry faces is not one we have in the search.
In the issue you mentioned it was brought about that the registry is a global namespace and therefore has quite a bit more influence.
Only indexing the registry defeats in my opinion the purpose of the search.
A) the search should make projects more discoverable, that includes small projects that are not yet popular enough to be in the registry.
B) As mentioned in the issue, the registry is not really necessary and just a shorthand for a selected set of packages. I don't see why we should bind us to something "unnecessary"
The registry also has to maintain a certain standard of quality and security as packages in there could be considered "officially approved".
Yet, neither us search people nor the maintainers of the registry have the capacity to QA every flake added (and track it over time).
Options to face this are either putting up extensive rules that narrow the amount of flakes that need to be considered/screened or providing a somewhat neutral index.
Considering the goal to improve discoverability I think we should lean more towards the latter although.
Still we should come up with some rules that filter out flakes with no public benefit (such as completely personal configs, or false flag flakes)
Regarding nixos-search, I think indexing more flakes (within limits) is not too much of an issue since most flakes are relatively small.
There are also efforts to include whole organisations into the search.
I agree however that in the current state flakes are quite disorganized and should be addressed in the current redoing.
These are my first thoughts on this
Let's discuss possible filters below or other options below!

Some points of todays discussion on the topic:
Most indexes allow you to publish your work on your own account. Cargo, for instance is famously indifferent about the packages listed there.
In contrast, we have a whole PR process for this which may be good to prevent spamming but also makes us discuss the same issues over again to the frustration of flake maintainers.
So what are the reasons we reject/block packages?

https://github.com/NixOS/nixos-search/pull/530

incorrect flake definition

https://github.com/NixOS/nixos-search/pull/481:

including may cause more confusion than clarity.
too many options?

https://github.com/NixOS/nixos-search/pull/482:

sparked a discussion in the registry repo https://github.com/NixOS/flake-registry/issues/25
note: we dont have the namespace issue mentioned
not a "nix ecosystem app"

https://github.com/NixOS/nixos-search/pull/510

cryptocurreny wallet
monetary project?

https://github.com/NixOS/nixos-search/pull/533

blockchain tools

Summarized that is:

incorrect flakes, which should be blocked or even removed eventually if the indexed ones break regularly.
"non nix tools" At which point does something become a nix tool then? and wouldnt that definition invalidate half of our existing catalog? most of the ngi-0 packages are not nix tools, their maintainers often dont even use nix
Cryptocurrency
Blockchain projects see an increasing use of nix, and start being interested in a spot in the ecosystem. IOHK, Tweag, Serokell, all are tightly entangles with both Nix and Crypto.
I dont deny certain ideological concerns about crypto but I dont know why we should shut them out entirely, without reason.
In the end these players could even help popularizing nix further which is a win
Regardless we may need to discern "official" from "unofficial" flakes, we should neither endorse or hinder the usage of any particular tool over another.

In my option limits such as requiring the projects to be "non-profit" would make slightly more sense.
Additionally, I think we can do a better job enabling others to spin up their own search for their respective target audience.
Final note: nixos-search is not an advertisement platform, and if it was it did a very bad job.
However even more important is it to clearly state that all these projects are just public repositories that happen to be buildable using nix bun none of them are endorsed OR cherry picked by nixos.
The bar should be: can the package be evaluated (we can't check the build) and is it safe (in the eye of the reviewer).

@ysndr lnbits-legend is not a cryptocurrency wallet. It is middleware like e-commerce plugins for wordpress, for facilitating transactions.

Thanks @MatthewCroughan for correcting me.
Took that from https://legend.lnbits.com/ site which states:

free and open-source lightning wallet

Yeah, it's probably bad that they say that, rather than being more clear. I will try to get that changed to be more representative of what the software actually does in practice. It has only existed for a year, so their descriptions are not 100% accurate.

registry.json X manual.toml:
My concern related to usability. The user expectation when both Index, one with WebUI other with CLI, but one has more things indexed.
 We do not index github:NixOS/nix.
It is another issue, of having two different sources. Forget to add to both, making two PR, convincing two maintainers...
flakes-registry only have the issue of namespace, because they're registering single pkg flake, instead of sub registry list (like NUR). Doing same here would reduce the toml size and hopefully reduce time to process it.

A) the search should make projects more discoverable, that includes small projects.

Agree, for both search and registry. Flakes-registry could be the official version of NUR.

B) As mentioned in the issue, the registry is not really necessary and just a shorthand for a selected set of packages. I don't see why we should bind us to something "unnecessary"

We diminished the importance of usability for so many years that the first joke I learn about nix is about learning curve.
Then we tag usability features as 'unnecessary'.

Filtering by ideology

requiring the projects to be "non-profit"

Paraphrasing:
"I dont deny certain ideological concerns about ~crypto~ X but I dont know why we should shut them out entirely, without reason.
In the end these players could even help popularizing nix further which is a win."

Overall suggestion
Flakes brings decentralization, it is good, but we cannot expect all 'nodes' of this new decentralized schema to have the same quality, like we never know the quality of a npm, docker or pypi before use it.
I think we should blacklist offenders:

Legal issues;
Supply Chain Attacks (Dependency Confusion, Repojacking);
Fail to match some SLA to be defined (i.e. broken for 1h, 1d, 1w, 1m, 1y).

Related: https://discourse.nixos.org/t/call-for-volunteers-curating-official-projects/45382


Issue while backpropagating through sparse_tensor_dense_multiply

I have a simple network defined as follows:
h1 = tf.sparse_tensor_dense_matmul(x, W1)
h2 = tf.matmul(h1, W2)
y = tf.matmul(h2, W3)
loss = tf.nn.l2_loss(y - y_)
train = tf.train.AdamOptimizer(learning_rate=lr).minimize(loss)

where x is a sparseTensor, rest are dense.
Dimensions (shapes) of W1 = [1000,200], W2 = [200,400] and W3 = [ 400, 500].
When I run the following:
sess.run([train], feed_dict={x:X, y_:Y})

where X is sparseTensor of shape [N, 1000] and Y is a tensor of shape [N, 500]
I get an error saying: OOM when allocating tensor with shape[3684773,200].
This is happening while the the the gradient for W is being computed. 3684773 also happens to be the number of non-zero elements in X.
Note:

When I compute gradients using tf.gradients, they work completely
fine.
When I run the same network using dense X and dense multiply( tf.matmul ), it works completely fine.

Please provide details about what platform you are using  (operating system, architecture). Also include your TensorFlow version. Also, did you compile from source or install a binary?  Make sure you also include the exact command if possible to produce  the output included in your test case. If you are unclear what to include  see the issue template displayed in  the Github new issue template.
We ask for this in the issue submission template, because    it is really difficult to help without that information. Thanks!

This issue is automatically closed due to lack of activity. Please re-open if this is still an issue for you. Thanks!


Added support for shifting time forward/backward.

Workflow now allows to shift time forward and backward by passing a pattern as an argument.
Pattern: +|-VALUE[mhdwMy] (minutes, hours, days, weeks, months, years)
Ie. df +30d will shift current time + 30 days; df -4w will subtract 4 weeks from current time.

+1


Release new version?

The code in the repo is different to the code of the latest released version. The last release was a year ago, and changes have been made to the code since then.

0.3.0 was released a while ago.


Add the Azure Boards badge to the README

Add the Azure Boards badge for the board used to track the work for this repository. Fixes AB#40. See the status badge configuration documentation for more information.

/deploy test

/deploy test

/deploy test


Added Discard time and continue button to linux UI

Hi,
After testing your OSX version, just added the Discard Time and Continue button to Linux UI.
Hope it helps.
Regards,
Javi M

Thank you very much for your contribution.
Next release for beta channel is planned to the end of this week. Few weeks later if all is good the new version will be pushed to stable.

Great, I will be using this very next release when launched.
Regards


Task 16,17

Build data table & Text to Excel

@SwapnaThiagarajan
Task16: Changes Verified
Task17: Changes Verified


Pre-receive hook support in Github enterprise

Describe the bug
Pre-receive hook support in Github enterprise
Hi,
is there any option or example where we can use this as a pre-receive hook at Github Enterprise server.
Thanks

Hi @roshvin, and thanks for the question.
I'm not aware of any example at present for using Nosey Parker in a pre-receive hook for GitHub Enterprise Server. (Presumably the use case there is to be able to scan for secrets at push time, and block pushing of commits that contain secrets.)
To make that work, you'd need to script some pieces: in a pre-receive hook, run noseyparker scan on the received content, and then perhaps noseyparker report -f json, followed by some test in the pre-receive hook that would cause it to fail if there were any Nosey Parker findings in the JSON output. I've not written such a thing myself.
One thing you would want to do if you set up a mechanism like this is specify a custom ruleset to only enable rules that have essentially no false positives, as you don't want to spuriously be blocking developer's commits. This mechanism is not well documented, but it involves writing a YAML file with the list of rule IDs that you want to enable, and then invoking noseyparker scan --rules-path YOUR_YAML_FILE --ruleset YOUR_RULESET_NAME.
See here for an example ruleset: https://github.com/praetorian-inc/noseyparker/blob/0cce95910be38058cc0cf00b548a892e3ed5dc35/crates/noseyparker/data/default/builtin/rulesets/default.yml
Let me know if you have questions about this and I will write up more documentation.

Hi @bradlarsen  thanks a lot for the quick help/support.


Chore: Readme and import updates

Thanks for fixing the audioClassification import in the ModelDetailPage.jsx ! I just noticed it is making the staging environment to crash


Bugfix : add fix in finish: and shouldStart:'s method

when the only difference is fragment value between two urls,wo should not treat them as redirect.


Unique request ID with logging interceptor

Currently there is no way to pair the start log entry with the end log entry when using the HTTP logging interceptor.
It would be nice if a random ID would be generated for each request that is logged together with the entry so that you can track which requests that complete.

@ansman you can create a custom logger and pass it to HttpLoggingInterceptor :)

@jbaginski How is the logger supposed to know that two log statements are related?

very good point :) I think you will end up with custom interceptor... I suppose that the id could be the instance id of the request object.

Well, this is a feature request for the HTTP logging interceptor. I understand that I have to roll my own if I want this feature today.

I don't think we’ll implement this. If you’re logging many requests concurrently and manually relating them, you’re going to have a bad time. You’re much better off hooking up Stetho or Charles.


Xavier initialization and ReLu

Hi Davis,
I have seen in the docs that you use the "Xavier initialization" described in http://jmlr.org/proceedings/papers/v9/glorot10a/glorot10a.pdf to set up the network parameters.
However, I saw in some of your examples you use rectified linear units (ReLu) in between the layers . A 2015 paper from Kaiming He (resnet guy) says the Xavier initialization should not be used with ReLu as the network might not be able to converge properly.
The paper I am referring to is here: https://arxiv.org/pdf/1502.01852v1.pdf,  Comparisons with “Xavier” Initialization chapter. The initialization proposed in the paper is actually very similar to Xavier, just adds an extra factor.
What do you think? Should we change the initialisation, or at least overload randomize_parameters  to have both?

Yes, I know about this.  I haven't had any trouble with the existing
initialization.  However, a more general way of initializing layers is also
needed.  So if you want to propose something that's fine with me.  I'll get
around to improving it eventually, but to my mind it's relatively low
priority.

Sure I will open a PR if I ever get the time to do it after I am done with my detection program.


Dimensions support for metrics

Hi,
I am unable to add a dimension for Event hub namespace, say a particular event hub entity for the namespace. Is there a way to achieve this?

In both Datadog and in the Grafana Azure Datasource, ascertaining DocumentDB(CosmosDB) throttled requests, is done by checking the StatusCode dimension that should be returned by the TotalRequests metric of the Microsoft.DocumentDB/databaseAccounts metric namespace.
Again, this is returned by the Grafana datasource, but no metric dimensions are being returned with the azure_metrics_exporter.
Is this yet to be implemented or is this in the current documentation and I have not understood?
    targets:
      - resource: "/resourceGroups/MyResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/MyDatabase"
        metric_namespace: "Microsoft.DocumentDB/databaseAccounts"
        metrics:
        - name: AvailableStorage
        - name: DataUsage
        - name: DocumentCount
        - name: IndexUsage
        - name: MetadataRequests
        - name: ProvisionedThroughput
        - name: ReplicationLatency
        - name: TotalRequests

In both Datadog and in the Grafana Azure Datasource, ascertaining DocumentDB(CosmosDB) throttled requests, is done by checking the StatusCode dimension that should be returned by the TotalRequests metric of the Microsoft.DocumentDB/databaseAccounts metric namespace.
Again, this is returned by the Grafana datasource, but no metric dimensions are being returned with the azure_metrics_exporter.
Is this yet to be implemented or is this in the current documentation and I have not understood?
    targets:
      - resource: "/resourceGroups/MyResourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/MyDatabase"
        metric_namespace: "Microsoft.DocumentDB/databaseAccounts"
        metrics:
        - name: AvailableStorage
        - name: DataUsage
        - name: DocumentCount
        - name: IndexUsage
        - name: MetadataRequests
        - name: ProvisionedThroughput
        - name: ReplicationLatency
        - name: TotalRequests

Since it's been over a year without a response from the dev team, I thought I'd post this here, which you can use as an alternative.
It's too bad, because I kind of liked the way this exporter from RobustPerception does things.
However, this exporter includes the aforementioned dimension support, and more.
https://github.com/webdevops/azure-metrics-exporter

Since it's been over a year without a response from the dev team on PR #93, I thought I'd post this here, which you can use as an alternative.
It's too bad, because I kind of liked the way this exporter from RobustPerception does things.
However, this exporter includes the aforementioned dimension support, and more.
https://github.com/webdevops/azure-metrics-exporter


Misc fixes/refactors

[ ] Add spinner in download
[ ] Remove href to avoid warning issue -> maybe <span ..> with css cursor: pointer
[ ] Bulk download should download pdbs in set of n
[ ] Prevent web to go the top when clicking on links
const noop = React.useCallback((ev: React.FormEvent) => ev.preventDefault(), []);
...
<a href="#" onClick={noop} ... />
[ ] Add hover for i icon instead of title
[ ] Improve design for pocket box (in particular *)
[ ] Add favicon
[ ] PocketMethods.download should be moved to the usecase
[ ] Review REACT_APP_API_URL as it doesn't seem to be working
[ ] Review Google Analytics. They don't seem to work
[ ] Move DSE Api to a different class
[ ] Change name to repository

This page is not under development anymore


Does not check for Android API >= LOLLIPOP

Hi!
Awesome plugin, found the directive extremely useful, so first of all, thank you!
Anyway, I did have to use *ngIf to hide a view with a shadow on phones running android with APIs lower than 21 (LOLLIPOP) since the method View.setElevation() was not added until that update. Think it would be nice if you could add that validation to the directive before it sets the elevation...
To recreate the issue just run any app using the directive on an Android phone running Android 4.4 or lower (API 21 is implemented on Android 5.0)

Good catch, will look into it (feel free to submit a PR tho).
Anyway, I just released a version 2. That'd be awesome if you could give it a try and let me know of any issues.
Thanks

Sorry it took me so long to get back to you!
I'll check out the new version ASAP and if it still has the same error I'll add a validation before applying the shadow to Android views and submit a PR.

Done on #12


Port mapping problem.

even I didn't include ssl object in my mup.json file. that whole build process is still assume I use ssl and redirect all the traffic into 433 port even if listen at 80 only.
here is my config:
{
  // Server authentication info
  "servers": [
    {
      "host": "myhost",
      "username": "myuser",
      "password": "mypassword",
      // or pem file (ssh based authentication)
      //"pem": "~/.ssh/id_rsa"
      "env": {
        "PORT": 3000,
        "NODE_ENV": "production"
      }
    }
  ],

  // Install MongoDB in the server, does not destroy local MongoDB on future setup
  "setupMongo": true,

  // Application name (No spaces)
  "appName": "myapp",

  // Location of app (local directory)
  "app": "../../",

  // Configure environment
  "env": {
    "PORT": 3000,
    "ROOT_URL": "http://myurl.com"
  },

  // Meteor Up checks if the app comes online just after the deployment
  // before mup checks that, it will wait for no. of seconds configured below
  "deployCheckWaitTime": 15,

  // show a progress bar while uploading.
  // Make it false when you deploy using a CI box.
  "enableUploadProgressBar": true
}

when I run this inside my remote server:
root@localhost:/# curl -L http://localhost:3000
curl: (7) Failed to connect to myurl port 443: Connection refused

Do you have force-ssl package installed. Make a visual confirmation in the packages file, since sometime add remove misses something.

in meteor app? no, there is no force-ssl, the apache server is currently serve a wordpress and it's fine without ssl, so I think on apache level, there are no force-ssl installed.

Not sure why it says myurl? Maybe there's a redirect to a url with httpS somewhere?

I double checked the settings, they all are http uri s, I still think it's the app that redirected it self.

Well maybe if you can make a default meteor app to test in its place.

A possibly final thought is that maybe it could be environment variables that are causing that too. If you could view all your environment variables maybe there's something revealing there. That is if a default meteor app is still miss behaving.

@MasterJames  thanks for the help, I think it's docker it self now, when we run mupx and it runs in docker deamon mode, so according to the doc, it will be protected from client access by using ssl. https://docs.docker.com/engine/articles/https/#daemon-modes

@MasterJames  problem solved by change how I locally config the docker setup. @MasterJames thanks for help!


i turn on jitstreamer says connected but doesnt work what do i do

Same situation over here.
I’m pretty sure the server is offline, because the Homepage is also not reachable.

Yep, JitStreamer is down.

When will the jitstreamer reopen?

Same problem… jit not working.

JitStreamer is now a self-hosted program. I have no plans to run another public server. I would recommend buying a cheap Raspberry pi and use Zerotier, SideStore.


Fixes uses of type :str = None to be :Optional[str] = None

Small fix to the typing, wherever :str = None is used the str type needs to be wrapped in Optional as None is not a string. This fixes it for users who run tools like Typeguard.

cheers 🍻  @drcongo


Question: Why is are the inputs/targets split into different batches?

Hi, quick question. Why are the inputs and targets split into different batches here?
https://github.com/alecwangcq/GraSP/blob/master/pruner/GraSP.py#L82
Did you not have the memory to compute the gradients in a single batch?

Hi, sorry for the late reply.
I had memory overflow issue when I compute the gradients in a single batch for tiny-imagnet. So I split the batch into two.
If you have any further questions, feel free to reopen this issue. Thanks!


powerline-shell prints out ansi sequences instead of color

So I installed powerline-shell via the git way, everything seems to be working normally when I hit powerline-shell and it prints out this junk:
powerline-shell --shell bash
\[\e[38;5;250m\]\[\e[48;5;240m\] \u \[\e[48;5;238m\]\[\e[38;5;240m\]\[\e[38;5;250m\]\[\e[48;5;238m\] \h \[\e[48;5;31m\]\[\e[38;5;238m\]\[\e[38;5;15m\]\[\e[48;5;31m\] ~ \[\e[48;5;236m\]\[\e[38;5;31m\]\[\e[38;5;15m\]\[\e[48;5;236m\] \$ \[\e[0m\]\[\e[38;5;236m\]\[\e[0m\] <imyusername>

Powerline works normally on my terminal(s). How can I fix this?

Hi, having the same issues, a few notes:
Using Mac menterey 12.4
Adding in the main function in the __init__ file the line:
sys.stdout.write('\033[93mWarning test\033[0m')

Makes the output be respected as yellow as it should be. So seems a issue with how the strings are build or printed, but could not get to the issue.

But be sure to use correct --shell for the call


Feature: allow to pass kubeconfig as a base64 string

This PR makes it possible to provide --kubeconfig="base64:$KUBE_CONFIG_BASE64" as proposed in the issue #588

Hello Guys, this is my first code in go ever, please be cool, if something is missing, docs, tests, code, whatever.. no big deal, I'll fix it.
thx

Thanks for the pull request. Code for kubectl and client-go lives in Kubernetes/Kubernetes, not in this repo.
Also, since this affects client-go, not just kubectl, overloading the current flag would cause all existing clients/libraries to fail to parse that flag consistently.
The proposed feature has broad enough impact that it should start as a KEP and be accepted before implementing. See https://github.com/kubernetes/enhancements/blob/master/keps/0001-kubernetes-enhancement-proposal-process.md for details
/close


Strange crash on some iPhone models when locking the orientation

Bug
Version 0.28.1 with React Native 0.59.0, no pods:
When launching the camera from a view that has its orientation locked, the application will crash and close without errors on an iPhone XR. It will however work as expected if the orientation is unlocked.
On an iPhone 6, launching the camera from a view with the orientation locked works without any issues.
Both devices run iOS 12.4
Environment info
React native info output:
React Native Environment Info:
System:
OS: macOS 10.14.6
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 24.62 MB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 11.3.0 - ~/.nvm/versions/node/v11.3.0/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v11.3.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
IDEs:
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.9 => 0.59.9
npmGlobalPackages:
react-native-cli: 2.0.1
Library version: x.x.x
Steps To Reproduce

Lock the view with Orientation.lockToLandscape()
Attempt to launch the camera with ImagePicker.launchCamera()
Run the application on a iPhone XR and then on a iPhone 6

Describe what you expected to happen:

I would expect that the application would behave similarly on both devices

I am getting the same error.
Steps:

Lock device orientation. (Potrait Mode)
open camera with ImagePicker.launchCamera() in Landscape mode

Camera app crashes and device goes in landscape mode.


Version 0.4.0 not published on Maven Central

Hi!
The README shows installation instructions for version 0.4.0, but on Maven Central the most recent version is 0.2.3:
https://search.maven.org/artifact/com.mux/mux-sdk-java
Versions missing from Maven Central:

0.4.0
0.3.0

(Thanks for the library, I really appreciate it)

I'm looking into this today.

Version 0.4.0 has now been published to Maven Central -- it may take a bit for the search index to catch up.  @gabrielgatu can you please test again when you've got a minute?

Version 0.4.0 now shows up in the Maven search as well.  Closing this issue, but feel free to re-open it if you have any other concerns.


featureafter creating a materialized view, if other operations fail, roll back

Proposed changes
Issue Number: close #xxx
after create mtmv, if create job failed,need frop mtmv
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run clickbench


Problem: Inconsistent HTTP API docs

Made the title of the asset search section consistent with the example (and consistent with the metadata search title and example).
Added a note that one can use asset?search or asset/?search, and a similar note for the metadata search.

Codecov Report

Merging #2403 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2403   +/-   ##
======================================
  Coverage    86.9%   86.9%
======================================
  Files          38      38
  Lines        2169    2169
======================================
  Hits         1885    1885
  Misses        284     284


Add support for gcs_id to project.yaml

:+1:

:tada: This has been pushed live to https://developers.google.com/web/


Email Client

Describe the solution you'd like
Create a script that can send emails to a CSV list of recipients - Potential to customize names & custom attachments
Additional context
People often have to manually send out emails to people, containing the same information. E.g. invoicing, job applications, etc.
I want to make a script that reads fields like email, first_name, last_name, attachment_dir from a csv file, and automatically send emails from my entered address to the specified recipients.

Great idea. Go for it 👍

can multiple people be assigned to a project
this is my first time trying to contribute

can multiple people be assigned to a project this is my first time trying to contribute

@zyetta is in process


Add podman edition of alpine-lima

Make a "pm" edition for completeness:
LIMA_INSTALL_DOCKER=false

LIMA_INSTALL_PODMAN=true

LIMA_INSTALL_NERDCTL=false
LIMA_INSTALL_CONTAINERD=false
LIMA_INSTALL_BUILDKIT=false

Basically it is with: apk add podman
Allows running podman, but does not start "podman.sock".
You can still run and build, without running the daemons.

Seems to be working:
lima-pm:/home/anders/alpine-lima$ podman run -it busybox
Resolving "busybox" using unqualified-search registries (/etc/containers/registries.conf)
Trying to pull docker.io/library/busybox:latest...
Getting image source signatures
Copying blob 5cc84ad355aa done
Copying config beae173cca done
Writing manifest to image destination
Storing signatures
/ # exit

91M	iso/alpine-lima-pm-3.14.3-x86_64.iso


Deployment Files

This PR adds the deployment files for the CSI driver.

@wlan0 - sounds good, I opened pr #6 which has all of the code changes


Surveyor view: Load My Account data

Loads account data for surveyor My Account page and displays it, with error handling and page loading.

Another thing that's probably out of scope for this particular thing is that we should allow surveyors to change their passwords on this screen.


Modify sudoers on every start

Fix for issue #10
Issue #, if available:
10
Description of changes:
Moved modify_sudoers function call so that it is executed at every start of the container
Why is this change necessary:
On restarts the /etc/sudoers file would be the original one not allowing Greengrass to operate correctly
How was this change tested:
By building the container and running it
Any additional information or context required to review the change:
Checklist:

[ ] Updated the README if applicable

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This can be closed as it is resolved by https://github.com/aws-greengrass/aws-greengrass-docker/pull/14


re-order imports with ruff

I can't merge this because of the branch protection rules.
I think the intention is to only allow merges if the (future) CI passes?

@alexrudd2 that is correct. I will merge this and make you an admin in the interim.


Clean up dnf cache completely on el8

dnf clean all do not clean everything stored in dnf cache.
At least it keeps fastestmirror dnf plugin cache that enabled on AlmaLinux by default.
So I propose to delete dnf cache completely during image build.

@googlebot I signed it!

/ok-to-test

Thanks Andrew!

OMG there is typo in my code:
rm -fr cd /var/cache/dnf/*
of course it should be
rm -fr /var/cache/dnf/*
Sorry for that. Could you fix it?

Lol, sorry I completely missed that. Yeah just send another PR if you would.


ci: remove git credentials after checkout

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
513

Relevant Lines:
513

💛  - Coveralls


Restrict input size

The algorithm expects sentence or several as an input. It cannot handle really long sequences without memory and CPU related issues. If user gives a really long input (let's say more than 100 tokens) algorithm should be able to split to parts or cut off the tail. If the text is splittable into  sentences, it is ok, just process text sentence by sentence, but what if there's no any pucntuation OR dots rarely met in the input body?

It might be better to provide generator interface to iterate over matches in long input.


Should be allowed to start multiple containers with same exposed port on the same host when networking has hostPorts set to "false"

Rancher server version - v1.2.0
Steps to reproduce the problem:
Create a template with network service provider as - "Vxlan-Internal" from - https://github.com/deniseschannon/rancher-catalog and branch vxlantest
Create environment with this template.
Create service with expose ports.
hostPorts for vxlan network is still set to"true" in DB -- #6958.
Set hostPorts for vxlan network to "false" is DB.
Add restart any existing container ( just to trigger the new metadata changes to the vxlan cnontainers)
No exposed port get programmed on the host as expected.
Note - Set up has 2 hosts.
Try to start a service  S1 with exposed port - 7878 and scale 2.
Try to start a service  S2 with same exposed port - 7878 and scale 2.
S2 fails to start because of not able to find host with available port.
Expected Behavior:
Should be allowed to start multiple containers with same exposed port on the same host when networking has hostPorts set to "false"

@deniseschannon My changes for the scheduler have not touched the service port part(nodePort). Not sure i can fix it in 1.4.

Seems very odd to me to change the behavior of the scheduler based off of this backdoor hostPorts=false feature.
Think about the user flow for this:
User specifies the equivalent of -p 80:8080 but we just quietly ignore that in the network provider. To me, the quietly ignoring it part needs to change, not the scheduler. Scheduler should continue to do its job of not allowing duplicate host port consumption. If we want to preen this use case, the cattle API should add validation to not allow public ports.

Confirmed with @ibuildthecloud - he agrees this doesn't need fixed changed. If a container says it is publishing port 80, then that port should be reserved for that host.

@cjellick but if you have hostports set as false, why are we reserving it? you should be able to schedule as many containers to whatever host since the ports aren't actually published.

No, these are separate concerns. The user is requesting that that port be reserved, so it is. The implementation details of network plugin should not impact this. Per @ibuildthecloud, hostPorts=false does not mean that we are completely ignoring host ports. It is an indication to the plugin that it should not manage them (that is not to say that something else isn't managing them).


Can't run the program

when i run the program, it took like a split of a second. Then it said in the command center,
"Process finished with exit code 0" the camera was not turning on, nor the program. What should i do to fix it?

Never mind, the program is running, however, when the camera is on, it auto quits if I press b , as the instruction say, does anyone know y?

Pressing the 'b' key closes the program. and I get this error:

some idea to solve it.
Thanks,

Hi @getvladimir4  try using createBackgroundSubtractorMOG2 instead of BackgroundSubtractorMOG2

Still same error. Any other way to rectify this?