fix: angular 13.x error with color not exist in palette

Issue
na
Description
angular 13.x error with color not exist in palette
Additional context

Gravitee.io Automatic Deployment
A prerelease version of this package has been published! 🚀
To use it in your project run the following lines:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

Gravitee.io Automatic Deployment
A prerelease version of this package has been published! 🚀
To use it in your project run the following lines:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:tada: This PR is included in version 2.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


regarding issue in parameter

Why in keras and pytorch shows a diffrent parameter count always.I have made a model in torch and i campare with keras there in less learnable parameter than keras.why??

I believe this is a general question regarding keras vs. pytorch?  If so, please consider using stackoverflow for this.  Thank you!


feat(Tabs): add contentless prop to avoid the render of the HTML markup

🔗 Linked issue
Resolves #1709
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This prop give tha ability to the user to remove the render markup of the content completely. It may be useful in certain cases, where the user is using the @change event, because is changing something else, and using the tab just as a switcher component.
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

I'm wondering if it wouldn't be better to name the prop content (defaults to true) to be used as :content="false". That is what I was planning to do in v3.

I'm wondering if it wouldn't be better to name the prop content (defaults to true) to be used as :content="false". That is what I was planning to do in v3.

That actually makes a lot of sense. I started with the less suffix cause it was an addendum, so more of a feature on top of the default behaviour, but makes sense. Should i change it or you prefer leave it as is until v3?

No you can do it like this in your PR, it will avoid another breaking change 😅

Thanks! 😊


Text-animation

A text animation
The javascript script animates text transition.
Fixed #172
Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added screenshots(if any) that prove my fix is effective or that my feature works

@m4dummies  hey u didn't remove the 3d animation file outside its folder. It's still there. If you have any other animation then create PR with that changing this. or else u can create a PR now fixing this

Oh, i missed it. Thanks for letting me know ill fix it asap.


Simple Method to GZIP Response

Right now there doesn't seem to be a simple way to automatically gzip responses and attach the appropriate content-encoding header. Right now you have to do something like this:
$app->get('/', function(React\Http\Request $request, React\Http\Response $response) use (&$i) {

    $text = gzencode("A generic response with gzip.\n");

    $headers = array('Content-Encoding' => 'gzip',
                     'Content-Type' => 'text/plain',
                     'Content-Length' => strlen($text));

    $response->writeHead(200, $headers);
    $response->end($text);
});

Which works but this gets tedious and I believe its a common enough (and expected) feature that even forcing people to implement an abstraction themselves isn't the best path.

See https://github.com/reactphp/http/issues/48 :+1:


openRC init script for chrooted apache

Hi all.
I try to write init script for chrooted apache and it works but not exactly as I need.
When I start chrooted apache manually:
chroot --userspec=apache /opt/jail/apache/ /usr/local/apache24/bin/httpd -k start
all processes are owned by apache user:
# ps -ef | grep http
apache   111196      1  0 14:41 ?        00:00:00 /usr/local/apache24/bin/httpd -k start
apache<PHONE_NUMBER>96  0 14:41 ?        00:00:00 /usr/local/apache24/bin/httpd -k start
apache<PHONE_NUMBER>96  1 14:41 ?        00:00:00 /usr/local/apache24/bin/httpd -k start
apache<PHONE_NUMBER>96  0 14:41 ?        00:00:00 /usr/local/apache24/bin/httpd -k start
apache<PHONE_NUMBER>96  0 14:41 ?        00:00:00 /usr/local/apache24/bin/httpd -k start

When I use my own openrc init script (based on init script from alpine linux) the apache process is started but the first root process is owned by root:
/etc/init.d/apache2 start
# ps -ef | grep http
root     110679      1  0 14:39 ?        00:00:00 /usr/local/apache24/bin/httpd -k start
apache<PHONE_NUMBER>79  0 14:39 ?        00:00:00 /usr/local/apache24/bin/httpd -k start
apache<PHONE_NUMBER>79  0 14:39 ?        00:00:00 /usr/local/apache24/bin/httpd -k start
apache<PHONE_NUMBER>79  1 14:39 ?        00:00:01 /usr/local/apache24/bin/httpd -k start
apache<PHONE_NUMBER>79  1 14:39 ?        00:00:01 /usr/local/apache24/bin/httpd -k start

Init script in attachment: apache2-jail.txt
Important part of /etc/conf.d/apache2-jail:
CHROOT_DIR="/opt/jail/apache/"
USERSPEC=apache

HTTPD="/usr/local/apache24/bin/httpd"

PIDFILE=/usr/local/apache24/logs/httpd.pid

CONFIGFILE=/opt/usr/local/apache24/conf/vhosts.conf

How to start chrooted apache in the same way when I start it manually? I have in mind - all processes was owned by specified user.

You can use this in openrc scripts to have it launch the command with a specific user/group:
command_user="user:group"

I tried 'command_user' before post. Not helped. The situation is still the same as I described.

please attach your exact init.d & conf.d files

@vapier Everything what you ask is in my first post here:

Init script in attachment: apache2-jail.txt
Important part of /etc/conf.d/apache2-jail:

Related? https://github.com/OpenRC/openrc/pull/517


fix: allow using CRLF and LF

Hi @ctron, thank you for the reminder. I did not have the opportunity to look at this yet, but I blocked some time in my calendar already.
That being said, I think we will need to discuss whether we can merge this PR as-is, but let's use the corresponding issue for that.


Support deletion of KMS Key Aliases - CORE-292

Closes CORE-292
This PR adds functionality to nuke KMS Key Aliases with KMS keys that are being nuked.

This does not change existing cloud-nuke KMS Key filtering functionality
Key aliases will only be nuked if they are attached to a KMS key that is being nuked

TODOs
Read the Gruntwork contribution guidelines.

[x] Update the docs.
[x] Run the relevant tests successfully, including pre-commit checks.
[x] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[x] Include release notes. If this PR is backward incompatible, include a migration guide.
[x] Attention Grunts - if this PR adds support for a new resource, ensure the nuke_sandbox and nuke_phxdevops jobs in .circleci/config.yml have been updated with appropriate exclusions (either directly in the job or via the .circleci/nuke_config.yml file) to prevent nuking IAM roles, groups, resources, etc that are important for the test accounts.

Release Notes (draft)
Added support for deletion of KMS Key Aliases

Build and relevant tests passed
TestListKmsUserKeys
TestRemoveKmsUserKeys


Move angular-cli.json to .angular-cli.json

angular-cli.json is now .angular-cli.json according to wiki
I guess that this is something that can be done through @angular/cli and requires manual change.
I guess that this would be required for both Angular2* and Angular4*

I'm working on it


Highlighted bold text doesn't stick out, but bolded highlighted text does

I'm trying technique called progressive summarization where after I take notes, I go through and bold important parts, and then go back through and highlight the most key parts.
I love how the bold looks in this theme, but you can't really tell when something has been highlighted in a bold section.
Given this markdown:
- **can we ==highlight and bold== from the 'view' mode?**

It ends up looking like:

Compare to:
- ==can we highlight and **bold** from the 'view' mode?==

Which looks like:

I started writing this not knowing that if you bold highlighted text, it looks right. So maybe this is a non issue 😅

This is a very interesting case. I will look into this one later on.


Refactor DnsNameResolver to be able to use different strategies when …

…it comes to creating Channels for queries.
Motivation:
At the moment we reuse the same Channel (and so underyling socket) for all queries. It has show that this can cause problems in some deployments, we should allow to use different strategies.
Modifications:

Refactor code to make it possible to use different strategies when it comes to creating / reusing channels for resolve operations

Result:
More flexible configuration and possible fix for https://github.com/netty/netty/issues/14364

Just to show the idea... This still lacks the possibility to configure the different strategies (at the moment it just creates a new socket per resolve operation). That said it would be easy to expose some enum to allow to configure it via the builder (not sure what the default should be tho).

One sec there is something wrong I need to fix first...

@bryce-anderson @idelpivnitskiy ok this is ready to go now


Can't see the screen

I only see pink lines like in this image. I use a custom tablet that not on the market.
$ scrcpy -b2M -m800

Buraks-MacBook-Pro:~ burak$ scrcpy -b2M -m800
/usr/local/Cellar/scrcpy/1.1_1/share/s...shed. 2.6 MB/s (19334 bytes in 0.007s)
2018-05-05 22:15:48.282 scrcpy[63302:537114] DEBUG: Starting decoder thread
2018-05-05 22:15:48.282 scrcpy[63302:537114] DEBUG: Starting controller thread
2018-05-05 22:15:48.362 scrcpy[63302:537114] INFO: OpenGL shaders: ENABLED
2018-05-05 22:15:48.362 scrcpy[63302:537114] INFO: Created renderer: opengl
2018-05-05 22:15:48.364 scrcpy[63302:537114] INFO: Initial texture: 800x448
2018-05-05 22:15:51.214 scrcpy[63302:537114] DEBUG: Unknown touch device id -1406696192, cannot reset

Does screenrecord works? (see https://github.com/Genymobile/scrcpy/issues/55)


ENTRYPOINT command doesn't work on Docker version 19.03.1

The ENTRYPOINT that ends with && does not work on 19.03.1 version of docker.  I am getting the following warning when building the image:
[Warning] Shell-form ENTRYPOINT and exec-form CMD may have unexpected results
When trying to run the container, I get the following error:
Error response from daemon: container .... encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2) extra info: {"CommandLine":""cmd /S /C C:\BuildTools\Common7\Tools\VsDevCmd.bat \u0026\u0026" powershell.exe -NoLogo -ExecutionPolicy Bypass","WorkingDirectory":"C:\","Environment":...,"EmulateConsole":true,"CreateStdInPipe":true,"CreateStdOutPipe":true,"ConsoleSize":[45,180]}.
When inspecting the image and compairing it to the previously working Docker version, I noticed that ArgsEscaped is missing on the current version image.
    "DockerVersion": "18.09.3",
    "Author": "",
    "Config": {
        "Hostname": "",
        "Domainname": "",
        "User": "",
        "AttachStdin": false,
        "AttachStdout": false,
        "AttachStderr": false,
        "Tty": false,
        "OpenStdin": false,
        "StdinOnce": false,
        "Env": ...,
        "Cmd": [
            "powershell.exe",
            "-NoLogo",
            "-ExecutionPolicy",
            "Bypass"
        ],
        "ArgsEscaped": true,
        "Image": "sha256:...",
        "Volumes": null,
        "WorkingDir": "",
        "Entrypoint": [
            "cmd",
            "/S",
            "/C",
            "C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat &&"
        ],
        "OnBuild": [],
        "Labels": null,
        "Shell": [
            "cmd",
            "/S",
            "/C"
        ]
    },

    "DockerVersion": "19.03.1",
    "Author": "",
    "Config": {
        "Hostname": "",
        "Domainname": "",
        "User": "",
        "AttachStdin": false,
        "AttachStdout": false,
        "AttachStderr": false,
        "Tty": false,
        "OpenStdin": false,
        "StdinOnce": false,
        "Env": ...,
        "Cmd": [
            "powershell.exe",
            "-NoLogo",
            "-ExecutionPolicy",
            "Bypass"
        ],
        "Image": "sha256:...",
        "Volumes": null,
        "WorkingDir": "",
        "Entrypoint": [
            "cmd /S /C C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat &&"
        ],
        "OnBuild": [],
        "Labels": null,
        "Shell": [
            "cmd",
            "/S",
            "/C"
        ]
    },

Is there a workaround for this?

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

ID: b91a4a43-5353-97cf-7532-7644aa3b497f
Version Independent ID: 858d9a5c-72f3-6a85-9270-0a0dd9e0438b
Content: Install Visual Studio Build Tools into a container
Content Source: docs/install/build-tools-container.md
Product: visual-studio-windows
Technology: vs-installation
GitHub Login: @heaths
Microsoft Alias: tglee

@pmartin-brierley Thanks for your question. It looks like you're having an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:
https://social.msdn.microsoft.com/Forums/vstudio
https://www.stackoverflow.com
https://www.reddit.com/r/VisualStudio/
As well, you might also consider using the Report a Problem tool to report the issue.

@WilliamAntonRohm I think the issue is with the documentation, as the Dockerfile example does not work with version 19 of docker.

@pmartin-brierley, while the Dockerfile example no longer works on version 19.03.1, it's because of a regression in Docker for Windows. I linked a bug I opened above, which references another bug I'm tracking.

Got this problem as well, docker 19.03.2. 2 months since first reported - what's the solution? The docker for windows is provided by microsoft via the Server Core for Containers VM installed by Azure... so i don't have much choice in the underlying docker version. Attached ticket is closed so no idea where to go next.
This shouldn't be closed - documentation as followed doesn't produce a working example on microsoft provided infrastructure.

There is currently no workaround with that certain of docker. You'll need to uninstall and install an older version.

Ok - since these instructions don't work for the latest version of docker (which is installed by default by Microsoft themselves in their Azure windows for container image), if there is an image already available that can be used - presumable this? https://hub.docker.com/_/microsoft-dotnet-framework-sdk/ if so, this should be explicitly stated in the documentation.

This is not a problem with the image, but with Docker itself.

A possible workaround is creating a batch file, for example VsDevCmdPowerShell.bat
@echo off
call C:\BuildTools\Common7\Tools\VsDevCmd.bat %*
powershell.exe -NoLogo -ExecutionPolicy Bypass

In the docker file
ADD VsDevCmdPowerShell.bat C:\BuildTools\
ENTRYPOINT C:\BuildTools\VsDevCmdPowerShell.bat

does not work, I have nothing installed in c:\buildtools

I have the exact same problem. C:\BuildTools is empty, which indicates that it failed somewhere before, which is also means that the solution provided by @bfloch wont help in this context.
Would really appreciate a solution here...

Running into the same issue - any solution please? I can't imagine it hasn't worked for anyone since August? I'm on version 19.03.5, entrypoint issue was solved by following hint in https://github.com/moby/moby/issues/39779, but thereafter I get same issue as reported above:
docker: Error response from daemon: container a25f33fe25eb9f652ff8f6803a8e825bdfe84a022ab8679d3444eb04e380f180 encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2)
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail: onecore\vm\compute\management\orchestration\vmhostedcontainer\processmanagement.cpp(173)\vmcomputeagent.exe!00007FF793A1AE77: (caller: 00007FF7939CE4AB) Exception(2) tid(384) 80070002 The system cannot find the file specified.
    CallContext:[\Bridge_ProcessMessage\VmHostedContainer_ExecuteProcess]
 Provider: 00000000-0000-0000-0000-000000000000] extra info: {"CommandLine":"\"cmd /S /C [\\\"C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat\\\", \\\"\u0026\u0026\\\"]\" powershell.exe -NoLogo -ExecutionPolicy Bypass","WorkingDirectory":"C:\\","Environment":{"COMPLUS_NGenProtectedProcess_FeatureEnabled":"0","DOTNET_RUNNING_IN_CONTAINER":"true","DOTNET_USE_POLLING_FILE_WATCHER":"true","NUGET_VERSION":"5.3.1","ROSLYN_COMPILER_LOCATION":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\BuildTools\\MSBuild\\Current\\Bin\\Roslyn"},"CreateStdInPipe":true,"CreateStdOutPipe":true,"CreateStdErrPipe":true,"ConsoleSize":[0,0]}.

I removed ENTRYPOINT and added a combined CMD which appears to be working:
CMD [ "C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat", "&&", "powershell.exe", "-NoLogo", "-ExecutionPolicy", "Bypass" ]

@Simran-B - what's your full docker file please? I am still having issues, the BuildTools folder does not seem to be generated. See my full docker file in posts in:
https://docs.microsoft.com/en-us/visualstudio/install/build-tools-container?view=vs-2019

@rlordcardano It's basically like this:
# escape=`

ARG FROM_IMAGE=mcr.microsoft.com/windows/servercore:ltsc2019
FROM ${FROM_IMAGE}

COPY Install.cmd C:\TEMP\

ADD https://aka.ms/vscollect.exe C:\TEMP\collect.exe

ARG CHANNEL_URL=https://aka.ms/vs/16/release/channel
ADD ${CHANNEL_URL} C:\TEMP\VisualStudio.chman

ARG BUILD_TOOLS_URL=https://aka.ms/vs/16/release/vs_buildtools.exe
ADD ${BUILD_TOOLS_URL} C:\TEMP\vs_buildtools.exe
RUN C:\TEMP\Install.cmd C:\TEMP\vs_buildtools.exe --quiet --wait --norestart --nocache `
    --installPath C:\BuildTools `
    --channelUri C:\TEMP\VisualStudio.chman `
    --installChannelUri C:\TEMP\VisualStudio.chman `
    --add Microsoft.VisualStudio.Workload.VCTools

CMD [ "C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat", "&&", "powershell.exe", "-NoLogo", "-ExecutionPolicy", "Bypass" ]

I'm actually using v15, but I suppose it doesn't make much of a difference. Note that I removed --all (and the --remove arguments), because I found --all to be problematic, i.e. I saw the virtual disk file grow >60GB and ran out of disk space after an hour or so... With just --adding the VCTools workload components I end up with a ~6 GB image. I guess it only installs what is listed as Required in the Dependency type column on https://docs.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-build-tools?view=vs-2019 ?
I use something like docker build -t buildtools2019 -m 8GB . to build the image (docs say at least -m 2GB). Docker Desktop <IP_ADDRESS>, Engine 19.03.5.

I found that modifying the entrypoint syntax fixed this for me:
ENTRYPOINT ["C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat", "&&"]

The hint was the fact that the && was appended to the script string as \u0026\u0026 so this explicitly indicates each Entrypoint argument so it doesn't try and find an executable with name C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat &&

I finally understand this warning:

---> [Warning] Shell-form ENTRYPOINT and exec-form CMD may have unexpected results

Both entries in shell-form (no escaping):
ENTRYPOINT C:\BuildTools\Common7\Tools\VsDevCmd.bat &&
CMD powershell.exe -NoLogo -ExecutionPolicy Bypass

Both entries in exec-form (JSON array, i.e. double-quotes and escaped backslashes):
ENTRYPOINT ["C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat", "&&"]
CMD ["powershell.exe", "-NoLogo", "-ExecutionPolicy", "Bypass"]

If you use the shell-form for the first, but the exec-form for the other, then above warning is raised and running the container results in an error like this:
docker: Error response from daemon: container 46fd… encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2)
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail: onecore\vm\compute\management\orchestration\vmhostedcontainer\processmanagement.cpp(173)\vmcomputeagent.exe!00007FF687EC9D2B: (caller: 00007FF687E7E13A) Exception(2) tid(388) 80070002 The system cannot find the file specified.
    CallContext:[\Bridge_ProcessMessage\VmHostedContainer_ExecuteProcess]
 Provider: 00000000-0000-0000-0000-000000000000] extra info: {"CommandLine":"\"cmd /S /C C:\\BuildTools\\Common7\\Tools\\VsDevCmd.bat \u0026\u0026\" powershell -NoLogo -ExecutionPolicy Bypass","WorkingDirectory":"C:\\","EmulateConsole":true,"CreateStdInPipe":true,"CreateStdOutPipe":true,"ConsoleSize":[30,120]}.

I guess mixing both forms has the effect of && getting Unicode-escaped as \u0026\u0026, which cmd and powershell do not understand. One can try this out with e.g. \u0063\u0061\u006c\u0063 (calc). It results in the "cannot find the file" error.
If you use one of the forms consistently, then it works however! So above examples with both entries in the same form will work. BTW. The file extension .exe can apparently be omitted from powershell.exe just fine.

This is great, thank you.
On Wed, 26 Feb 2020 at 15:11, Simran<EMAIL_ADDRESS>wrote:

I finally understand this warning:
---> [Warning] Shell-form ENTRYPOINT and exec-form CMD may have unexpected
results
Both entries in shell-form (no escaping):
ENTRYPOINT C:\BuildTools\Common7\Tools\VsDevCmd.bat &&
CMD powershell.exe -NoLogo -ExecutionPolicy Bypass
Both entries in exec-form (JSON array, i.e. double-quotes and escaped
backslashes):
ENTRYPOINT ["C:\BuildTools\Common7\Tools\VsDevCmd.bat", "&&"]
CMD ["powershell.exe", "-NoLogo", "-ExecutionPolicy", "Bypass"]
If you use the shell-form for the first, but the exec-form for the other,
then above warning is raised and running the container results in an error
like this:
docker: Error response from daemon: container 46fd… encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2)
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail:  Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail: onecore\vm\compute\management\orchestration\vmhostedcontainer\processmanagement.cpp(173)\vmcomputeagent.exe!00007FF687EC9D2B: (caller: 00007FF687E7E13A) Exception(2) tid(388) 80070002 The system cannot find the file specified.
CallContext:[\Bridge_ProcessMessage\VmHostedContainer_ExecuteProcess]

Provider: 00000000-0000-0000-0000-000000000000] extra info: {"CommandLine":""cmd /S /C C:\BuildTools\Common7\Tools\VsDevCmd.bat \u0026\u0026" powershell -NoLogo -ExecutionPolicy Bypass","WorkingDirectory":"C:\","EmulateConsole":true,"CreateStdInPipe":true,"CreateStdOutPipe":true,"ConsoleSize":[30,120]}.
I guess mixing both forms has the effect of && getting Unicode-escaped as
\u0026\u0026, which cmd and powershell do not understand. One can try
this out with e.g. \u0063\u0061\u006c\u0063 (calc). It results in the
"cannot find the file" error.
If you use one of the forms consistently, then it works however! So above
examples with both entries in the same form will work. BTW. The file
extension .exe can apparently be omitted from powershell.exe just fine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/visualstudio-docs/issues/3713?email_source=notifications&email_token=AAIXS4MYRLRFLXLVMOAHIBTREZTAVA5CNFSM4IIUC4W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENAFHZQ#issuecomment-591418342,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIXS4PCVP4GDY3FA7VDCR3REZTAVANCNFSM4IIUC4WQ
.


Go module only supports binary classification

This is documented, but is quite limiting. How much effort would it take to support this? I might be willing to contribute if there are no resources available to do this.

Hi, see my answer in the discussions thread, the core team does not have the bandwidth to work on this in the near future, but we're happy to review and discuss PRs.


Better error message on amplify init, please.

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
NEW_APP
AWS Region
us-west-2
Amplify Hosting feature
Console
Frontend framework
Next.js
Next.js version
13.4.16
Next.js router
App Router
Describe the bug
Hello.   I'm a first-time user trying to evaluate Amplify for my next project.  I'm carefully following the instructions here:  https://docs.amplify.aws/start/getting-started/setup/q/integration/next/
When I get to the amplify init step, after selecting my AWS profile, the command fails like this:
? Enter a name for the project twerk
The following configuration will be applied:

Project information
| Name: twerk
| Environment: dev
| Default editor: Visual Studio Code
| App type: javascript
| Javascript framework: react
| Source Directory Path: src
| Distribution Directory Path: build
| Build Command: npm run-script build
| Start Command: npm run-script start

? Initialize the project with the above configuration? Yes
Using default provider  awscloudformation
? Select the authentication method you want to use: AWS profile

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Please choose the profile you want to use default
🛑 We are unable to process your request. Please reach out to your support representative.

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: 00c940e9-b1a7-4f4c-a3ee-bbbf26e86c69

Expected behavior
Some error message or log that I can look at to see what is it that failed?
Maybe my key is incorrect or not using the keys from [default] in ~/.aws/credentials (I'm pretty sure it is and those are correct).     Maybe the region is incorrect in my ~/.aws/config?  How would I know?
Reproduction steps
Follow instructions of this tutorial:  https://docs.amplify.aws/start/getting-started/setup/q/integration/next/  up to amplify init step.
Build Settings
I think `init` did not get far enough to generate an amplify.yml.  I don't see one in my project root.

Log output

# Put your logs below this line

2023-08-16T16:41:36.709Z|info : amplify init core
2023-08-16T16:41:36.739Z|info : @aws-amplify/amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-08-16T16:41:53.867Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["default"])
2023-08-16T16:41:53.868Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"us-east-1"}])
2023-08-16T16:41:53.868Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["default"])
2023-08-16T16:41:53.873Z|info : amplify-provider-awscloudformation.amplify-service-permission-check.checkAmplifyServiceIAMPermission.amplifyClient.listApps([])
2023-08-16T16:41:54.230Z|info : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.createApp([{"name":"[***]rk","environmentVariables":{"_LIVE_PACKAGE_UPDATES":"[{\"pkg\":\"@aws-amplify/cli\",\"type\":\"npm\",\"version\":\"latest\"}]"}}])
2023-08-16T16:41:54.709Z|error : We are unable to process your request. Please reach out to your support representative.
ProjectInitFault: We are unable to process your request. Please reach out to your support representative.

Additional information
No response

Hey @littlebee, thank you for reaching out. When creating a new application on the AWS Amplify console, do you observe a similar message?
we can create a new application by clicking on New app -> Build an app

Hey @littlebee, If you are unable to create a application on the AWS Amplify console as well, this seems to be occurring on the account level.
I would suggest reaching out to the AWS Quota increase team. From the following documentation: https://docs.aws.amazon.com/general/latest/gr/amplify.html#service-quotas-amplify
noticed the following banner for new accounts.
New AWS accounts have reduced apps and concurrent jobs quotas. AWS raises these quotas automatically based on your usage.

Closing due to inactivity

same error, noth CLI and UI Console error out

I'm seeing the same issue.

@littlebee were you able to resolve this issue?

No, I was not.
Sent from my iPhone

On Oct 12, 2023, at 6:57 PM, Joe Yu @.***> wrote:

@littlebee were you able to resolve this issue?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

@joeyu23 @joeyu23 were you able to reach out to the quota team as the issue is currently occurring on a account level?
if you have a premium support plan, you can open a support case under the Amplify Console Support with a brief explanation with the error and being unable to create resources.
if you do not have a support plan and see a Basic Support Plan in the AWS support console,
create a new support case under Account and Billing using the following headings:
Service: Account
Category: Other Account Issues
General Question
add a subject line say "Check Account Status - Amplify Console" and describe the issue you are experiencing. Do link the GitHub issue to help track the issue.

@ykethan where is 'Account and Billing' section ? somewhere in Billing and Cost Management ??


[ERROR] No device found with specified name

Wanted to connect my Quest 2 with my Windows 7 PC. But it keeps showing error "No device found with specified name" a few from the ALVR dashboard (v 15.1.0), and followed by a appcrash of vrserver.exe.
From the headset ALVR side, it also shows "The server has disconnected" multiple times.
May I know what is the issue and how can I solve this? Thanks!

Windows 7 support has been dropped since ALVR v12. You need Windows 8 or greater.


Upgrade tusd to version 1.10+

Version 1.10.1 of tusd has been released with some changes. Add support for it.
Thank you.

Hi, thanks for letting us know about the new version. Currently I don't have time to do the upgrade and all the testing. Would you be so kind to submit a pull request with the updated binaries?


fix: calling setIsAdjustingWidth to block other cell events + new min width for sn-table

In order to block click events on the dimension value cells and header cells, we need to know when the column adjuster is being dragged or not. Therefor we add a state in sn-pivot-table, then passing the setter in here and set it to true when you start dragging. If you haven't changed the width, the state is set to false, since there is no way for pivot table to know that you are done dragging, without calling the confirmCallback. Note that there is still a small bug you can get. If you have the min width aldready, then start to drag over the cell and release, you will trigger the cell click handler. This is an extreme corner-case, that will be fixed if we implement drag to select. See both the fix and lastly the remaining bug in the gif

Adding a new min value which is the current one for sn-table. We need to use that value when we have the old header implementation, to fit both buttons. Once we turn on the flag for the new header, we can switch only having one min value (30px)

:tada: This PR is included in version 2.6.1 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Update index.js

Improved JavaScript Code

There is no significant change in this PR. Also removing JSDoc in not a great idea. Closing this.


Kubernetes Deprecation Policy page lists wrong release cadence

In k8s document page: https://kubernetes.io/docs/reference/using-api/deprecation-policy/
Second paragraph below Rule #4b says:
All of this is best illustrated by examples. Imagine a Kubernetes release, version X, which introduces a new API group. A new Kubernetes release is made every approximately 3 months (4 per year).
It should say:
All of this is best illustrated by examples. Imagine a Kubernetes release, version X, which introduces a new API group. A new Kubernetes release is made every approximately 4 months (3 per year).

/kind bug
/retitle Kubernetes Deprecation Policy page lists wrong release cadence
/language en
/help
/priority backlog
/triage accepted
Thanks for the report.

I would like to pick this up
/assign


Add aws-ebs-csi-driver add-on

This commit enables the aws-ebs-csi-driver add-on to enable PVC creation out of the box for new EKS clusters. Beforehand, this add-on needed to be created manually through the aws cli after cluster creation.

This honestly may or may not be a good idea. I've seen some weird, flaky behavior on installation. Sometimes the deployments for the aws-ebs-csi-driver don't always come up correctly and require a couple of restarts.


Q: Sorting between status in wrong order duplicates entities

Ahoy
I want my entities to be dragged between statuses. I enabled
    public bool $sortable = true;
    public bool $sortableBetweenStatuses = true;

as documented.
Now, I am able to move entities between status, all good.
But, if I for example have two entities and two status, one entity per status and move the first entity from status A to status B but move it over the other entity, the Board refreshes with the entity being above and below the old entity in status B.
If I directly move the entity to the end of the column status B I do not have this effect.
I guess this is an issue with ordering vs sorting? I only need the sorting between status, as I do not have an orderable value on my entities. Do I need to add it to make it work? Or could ordering (below/above) be split from sorting between status? If I disabled $sortable it doesn't work alone with $sortableBetweenStatuses.
Thanks a lot

Let me check I will have a look soon. Sorry for the delay

I can't reproduce this. As there is no activity, I will close this. Reopen it if you are still having the issue

I got the same issue in my project, take a look to the below video:
https://user-images.githubusercontent.com/6197875/199604178-e6a8a343-fd70-4555-83b4-264e442de0c2.mp4

@heloufir same problem. How did you get to fix it ?


ci: publish to github package

Signed-off-by: TennyZhuang<EMAIL_ADDRESS>

No idea about how to test it


WARN: Screenshot could not be saved. page.current_path is empty

Using:
capybara-screenshot 1.0.21
Rails 4.2.0
capybara 2.14.3
I get:
WARN: Screenshot could not be saved. `page.current_path` is empty

on CircleCI, but it seems to work fine locally. Is this a known problem?

Hi I have same issue.
Using:
capybara-screenshot 1.0.22
Cucumber 3.1.2
capybara 3.11.1
I get error in my local as well

I had to change both capybara-screenshot and rspec-rails to get it working in Rails 6. See:

https://github.com/szTheory/rspec-rails/commit/dde73abae8b21ac806552fdbd43565fecbe3c181 (fork from rspec-rails v3.8.2)
https://github.com/szTheory/capybara-screenshot/commit/c539e36c1fc60a2544781b891cf61bdcf0c62a12

@mattheworiordan FWIW, I'm seeing this issue while using headless_chrome.
I'm opening a page, filling in some form fields and clicking a button, at which point the spec fails and this message appears.

Yes, i'm getting "WARN: Screenshot could not be saved. page.current_path is empty." with headless_chrome too. i can create screenshots manually with screenshot_and_save_page.

@mattheworiordan FWIW, I'm seeing this issue while using headless_chrome.
I'm opening a page, filling in some form fields and clicking a button, at which point the spec fails and this message appears.

I also have a similar problem while using headless_chrome, the reason was:
config.after(:each, js: true) do
  Capybara.reset!
end

I have replaced it with:
config.retry_callback = proc do |ex|
  Capybara.reset! if ex.metadata[:js]
end

And now everything works as expected :tada:

Thanks for sharing a working solution, @GalenkoEugene!

@GalenkoEugene Can you please specify the file name where you made these changes?

@GalenkoEugene Can you please specify the file name where you made these changes?

@GalenkoEugene Can you please specify the file name where you made these changes?

../spec/support/capybara.rb
inside configuration block...
RSpec.configure do |config|
  config.retry_callback = proc do |ex|
    Capybara.reset! if ex.metadata[:js]
  end
end

Generally, you could put it into any config file. Don't forget to require it in spec_helper.rb

@GalenkoEugene Can you please specify the file name where you made these changes?

../spec/support/capybara.rb
inside configuration block...
RSpec.configure do |config|
  config.retry_callback = proc do |ex|
    Capybara.reset! if ex.metadata[:js]
  end
end

Generally, you could put it into any config file. Don't forget to require it in spec_helper.rb

I'm running the test using bundle exec rspec which gives me the error of:
WARN: Screenshot could not be saved. page.current_path is empty.
also this:
 Failure/Error: expect(page).to have_selector(".name", text: "Take Notes").
I used all above-mentioned solutions, but nothing worked. Can anyone help me with this?

I'm running the test using bundle exec rspec which gives me the error of:
WARN: Screenshot could not be saved. page.current_path is empty.
also this:
 Failure/Error: expect(page).to have_selector(".name", text: "Take Notes").
I used all above-mentioned solutions, but nothing worked. Can anyone help me with this?

Closed but continued here: #277


Internal error: Failed to update peripheral  after memory reads

I am trying to read the contents of the peripheral registers using VS Code.
Unfortunately when I click on a peripheral on XPERIPHERAL section of the debug column I got the following error:
Internal error: Failed to update peripheral BUSCTRL after memory reads
Internal error: Failed to update peripheral PADS_BANK0 after memory reads
Internal error: Failed to update peripheral IO_BANK0 after memory reads
Internal error: Failed to update peripheral BUSCTRL after memory reads
Internal error: Failed to update peripheral DMA after memory reads
Internal error: Failed to update peripheral I2C0 after memory reads

The step-by-step debug works fine instead.
My platformio.ini file is the simplest one:
[env:pico]
platform = raspberrypi
board = pico
framework = arduino

Thanks in advance to everyone.

Hello this repository is refusing updates and fixes because platformio demands money from the raspberry pi foundation which they are unwilling to pay.
Please consider switching to the https://github.com/maxgerhardt/platform-raspberrypi repository for continued use of Pi Pico within PlatformIO


Overcommit Precommit hook: Ktlint runs on unmodified files

I am using Ktlint as a git hook in precommit hook of the Overcommit , the problem i am facing is that Ktlint runs on unmodified files as well, whereas it should only run on modifies files.
Below is my hook configuration in the overcommit.yml file:
Ktlint: problem_on_unmodified_line: report enabled: true description: 'Analyze with Ktlint' required_executable: 'ktlint' install_command: 'brew install ktlint' include: '**/*.kt' flags: []
Any help would be appreciated.

I am not familiar with Overcommit. The git-hook installed by ktlint should look as follows:
#!/bin/sh
# https://github.com/pinterest/ktlint pre-commit hook
git diff --name-only --cached --relative | grep '\.kt[s"]\?$' | xargs ktlint --relative
if [ $? -ne 0 ]; then exit 1; fi

Please execute command above to find out what is happening on your system.

Closed, as no response received in last 23 days.


Select not working when inside Dialog. Throws error when clicked.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behaviour
Should not throw an error
Current Behavior
Throws the following error:
Menu.js:107 Uncaught TypeError: Cannot read property 'focus' of null
at Menu._this.focus (Menu.js:107)
at Object.Menu._this.handleEnter [as onEnter] (Menu.js:122)
at Object.Popover._this.handleEnter (Popover.js:226)
at Object.chainedFunction [as onEnter] (helpers.js:85)
at Object.Grow._this.handleEnter [as onEnter] (Grow.js:86)
at Object.CSSTransition._this.onEnter (CSSTransition.js:217)
at Transition.performEnter (Transition.js:242)
at Transition.updateStatus (Transition.js:215)
at Transition.componentDidMount (Transition.js:157)
at commitLifeCycles (react-dom.development.js:8770)
Steps to Reproduce (for bugs)
Place a Select control within a Dialog and click on the control.

Tech
Version

Material-U I
v1.0.0-beta.24

React
v16.2.0

Cromium
Version 63.0.3239.84 (Official Build) Built on Ubuntu , running on Ubuntu 17.04 (64-bit)

Seems working in this demo: https://codesandbox.io/s/64l1mw00lz

@int13h can you provide an example on something like codesandbox?  We need more information about how you’re configuring the components.  I’ve used a Select within a Dialog and @Chopinsky has also linked a problem-free example.

Closing this issue, as your reproduction steps have not reproduced the issue.  I will happily reopen this if you can provide an alternate set of steps to reproduce the behavior you're experiencing.

I'm not sure what causes it, but I'm facing the same problem, and it is NOT inside a modal or dialog.
It's simply added to my pages and, as soon as I click, it triggers the "Cannot read property 'focus' of null" error.
I'm testing with a "copied/pasted" example from the documentation.

I found out the problem and fixed it.
I was importing it as:
import MenuItem from 'material-ui/Menu'

but the correct way is
import { MenuItem } from 'material-ui/Menu'

Check if that wasn't the same problem for you too, @int13h


Component: Testimonial (Home Page)

Bride Review Component
Desktop:

Mobile:

@jmripper - I think this is what you are working on...


WebWorker Error when running on Android cordova

Hi, I'm getting this error when uploading images from Android device in development mode:
Error: Failed to construct 'Worker': Script at 'http://<IP_ADDRESS>:3000/packages/ostrio_files/worker.min.js' cannot be accessed from origin 'http://localhost:12280'
Its working normally when running on localhost:3000 in web browser.

I tried deploying the web app on the server, then connected the Android app to that server.  And the same error is showing:
Failed to construct 'Worker': Script at 'http://my-root-domain.com/packages/ostrio_files/worker.min.js' cannot be accessed from origin 'http://localhost:12280'.
I also tried setting this on mobile-config.js, but the app still could not access the worker.min.js file:
App.accessRule( "http://my-root-domain.com" );

Is there any way to override this and just get worker.min.js on public folder?

@mking200
Sorry, this was broken in v1.7.0
Please wait for next release. Meanwhile you can use v1.6.10 or set settings.allowWebWorkers to false in .insert() method options

Btw, have tried the App.accessRule('*') and/or meteor build --server http://my-root-domain.com

Yes, have tried all that except for App.accessRule('*')

BTW this was broken by this fix: https://github.com/VeliovGroup/Meteor-Files/issues/188 :)
Do you have an idea how to fit both requirements?

Can we try to have an option to set the link to worker.min.js file manually?
Am thinking of putting this in public folder, since the Android app doesn't seem to have problem with access to public folder.

I'll use inline worker in v1.7.1, so there is will be no need to have a request for worker over the wire

Ok, thanks.  Will just wait for the next update then.

Hi @mking200 ,
Fixed in v1.7.1, pleas update and test on your end


Issues with Bearded Theme - Color Inconsistencies and Inactive Lines

Feedback on Bearded Theme for Neovim
I hope this message finds you well. Firstly, I wanted to express my appreciation for your work on the Bearded Theme for Neovim. It's been a delightful addition to my coding environment, reminiscent of the setup I enjoyed while using VSCode.
As I've transitioned to Neovim and adopted the Bearded Theme, I've encountered a couple of issues that I believe are worth addressing:
Color Differences between Neovim and VSCode
Upon comparing files opened in Neovim with the Bearded Theme and VSCode with the Bearded Theme, I've noticed discrepancies in color representation, particularly in React and .tsx files. Ensuring consistency across different editors is crucial for maintaining a seamless workflow, and resolving these color inconsistencies would greatly enhance user experience.
Indent Guides
The lines that link the beginning and end of brackets, such as parentheses, braces, and square brackets. Similarly, in HTML files, these lines connect the opening and closing tags. While these lines do change color when the cursor is on them in all Neovim themes to indicate where I am in the code, they don't become active as expected. Instead, they remain static, which can lead to confusion and detracts from their utility in code navigation.
I hope this clarification helps in addressing the issues more effectively. Your attention to these matters would greatly contribute to improving the overall usability and aesthetics of the Bearded Theme.
Thank you for your dedication to maintaining and enhancing this excellent theme. I eagerly await your response and any updates you may provide.

Thank you for the feedback!
I will try to fix the inconsistencies between languages.
Although i'm a bit confused when you mentioned the inactive lines for bracket beginnings and endings, could you maybe send an example?
Also, are there any other variants (outside of vivid) you would want added?

I'm referring to the indent lines, like the ones showcased in the image below:

Ideally, when the cursor is placed within a function, the lines indicating the start and end of that function should become active. However, this isn't occurring as expected.

I see what you mean now. do you mind telling me which plugin you use for the indent lines? I probably just need to add support for plugins that add those.

I use Lazyvim distro and I think they use indent-blankline and mini.indentscope to handle it.

Hello! I'm sorry for the kind of wait, but I think I might have sorted out the indent-blankline and indentscope issue, although i'm not entirely sure, so I would appreciate some feedback on it.
When it comes to the consistencies between different syntaxes, I would still need to see if I can do anything.

thanks for the effort. I will check it and give you a feedback.

I have just checked it in some js, ts, jsx, tsx files but I have noticed that unfortuneatly everything is the same as before.


Is this correct?

https://www.zhihu.com/question/283016683/answer/432657498

Sorry, I can't read Mandarin.


Fix ed25519::generate_from_entropy

The implementationw was erroneously trying to create a keypair from the given entropy instead of just the secret key.

Codecov Report

Merging #4 (185b91d) into main (2ddd7e0) will increase coverage by 3.64%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
+ Coverage   64.94%   68.59%   +3.64%
==========================================
  Files           6        6
  Lines         271      277       +6
==========================================
+ Hits          176      190      +14
+ Misses         95       87       -8

Impacted Files
Coverage Δ

src/ed25519/mod.rs
86.41% <100.00%> (+9.08%)
:arrow_up:

src/ecc_compact/mod.rs
74.66% <0.00%> (+2.66%)
: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 2ddd7e0...185b91d. Read the comment docs.


⚠ Bofrost.de has degraded performance

In 2d1debd, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1738 ms

Resolved: Bofrost.de performance has improved in 0ee19b5 after 13 minutes.


Jelly Library Fails to Parse Cross-File Modules

I attempted to implement Example1 from the paper associated with the Jelly library. This involved creating two separate files and importing modules from one file to another. Despite following the documentation's guidelines closely, Jelly is unable to parse the cross-file modules, resulting in an import failure.

Actual Behavior
An error occurs during the parsing process.
Error: Unable to resolve module

I have attempted clearing the npm cache and reinstalling node_modules, but the issue persists.
Node.js version: v20.0.0
NPM version:9.6.4

You set -b . (sets the base directory to .) but analyze files in another directory. Try removing -b . or replacing . by D:\Study\Lab_NPM\try_jelly\test.

I have retried your suggested solutions, but I'm still encountering the same issue as before, unable to resolve it.

I've made multiple attempts, exploring all possible avenues, yet the problem persists.
node ../jelly/lib/main.js -j cg.json -b . D:\Study\Lab_NPM\try_jelly\test
node ../jelly/lib/main.js -j cg.json -b D:\Study\Lab_NPM\try_jelly\test D:\Study\Lab_NPM\try_jelly\test
node ../jelly/lib/main.js -j cg.json -b D:\Study\Lab_NPM\try_jelly\test .
node ../jelly/lib/main.js -j cg.json D:\Study\Lab_NPM\try_jelly\test
node ../jelly/lib/main.js -j cg.json .

jelly -j cg.json -b . D:\Study\Lab_NPM\try_jelly\test
jelly -j cg.json -b D:\Study\Lab_NPM\try_jelly\test D:\Study\Lab_NPM\try_jelly\test
jelly -j cg.json -b D:\Study\Lab_NPM\try_jelly\test .
jelly -j cg.json D:\Study\Lab_NPM\try_jelly\test
jelly -j cg.json .

Additionally, I've provided the structure of my files for a clearer understanding of the setup:
try_jelly
├─ jelly
│  └─ ……
└─ test
   ├─ cg.html
   ├─ cg.json
   ├─ clinet1.js
   ├─ lib1.js
   └─ package.json

It turned out to be an issue with how Linux and Windows handle paths differently. After switching to Linux, everything runs smoothly now. Thanks a lot!

Should be fixed by c197c6b.


iOS: Wrong icons on ShowSuccess and ShowError methods

Please check all of the platforms you are having the issue on
[X] iOS
[] Android
[] UWP
[X] PCL

Please state the issue to the best of your ability below
ShowSuccess() and ShowError() are probably using the wrong icon since 5.1.0. I guess it shows a progress indicator (circle that fills).

Please copy and paste the exception details below.  If you are having a crash and this detail is missing, your issue will be closed without warning.

Just use one of the following lines to see the issue.
UserDialogs.Instance.ShowSuccess ("Test");
UserDialogs.Instance.ShowError ("Test");

a temporary 'fix' is to add the success* and error* images from https://github.com/nicwise/BTProgressHUD/tree/master/BTProgressHUD to your recources folder.

It looks like xamarin changed the way the bundles are brought in at some point.  I have internalized btprogresshud in 6.1 to fix this issue

@aritchie this error already exist in last nuget package : 6.3.1

There isn't much I can do to fix this currently.  Use the workaround listed above.


vite4 env Variables contains "#", build exception

Describe the bug
when i define a varibales like
VITE_APP_KEY=ptest.com,7213421265257#B0sECF3mUC0sECF3m3mUC0sECF
then execute
npm run build
VITE_APP_KEY become ptest.com,7213421265257， and miss '#...'
Reproduction

Steps to reproduce
No response
System Info
System:
    OS: macOS 11.4
    CPU: (6) x64 Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
    Memory: 507.70 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.18.1 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.15 - /usr/local/bin/npm
  Browsers:
    Chrome: 111.0.5563.64
    Safari: 14.1.1

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

You can wrap it with quotes. https://github.com/motdotla/dotenv#comments


Bug | Logout | Localstorage data leak

When ?

User clicks on logout button

What ?

Localstorage should get cleared. At the moment, draft and chat history is present.

Screenshot

can you please check if its fixed I could not reproduce the and the localstorage is cleared. i tried logging out and it got cleared

The issue still persists.
To reproduce it, you need to use the blog chat or Autosave while writing blog.
Because the localstorage inserts happen while using these features.


Create project banners

While navigating on Github (following Romain Lanz work) I spotted that all repositories in the setten-io org has banners.
For example https://github.com/setten-io/adonis-bull-queue has the following banner

I think that a brillant idea and we should do the same for our projects. The idea is to design a simple banner that we will reuse just by updating the package name and description.
Having an image at the top of the project is a lot better than a simple title (H1). It gives a more professional feel.
I guess @im-codebreaker should be the champion of this.
We can start by doing a banner for JS-X-Ray (to discuss the design etc).
package name: @nodesecure/js-x-ray
description: JavaScript & Node.js open-source SAST

JS-X-Ray banner


feat: Implement Run Service

Description

We do not have a sandboxed environment where we can execute code right now.
We can integrate Judge0 into our application to ensure that users are able to execute code on the server.
An instance of Judge0 has been deployed onto AWS, and I have shared the IP address privately with you to prevent abuse of the system right now.
Remember to include the API Key with the Headers X-Auth-User and X-Auth-Token to ensure that you are authorized to make calls to the /submissions path on the sandbox to execute your code.
The Schemas for the inputs and outputs have been added into the team's Miro board, but I have included them below for your convenience:
Request
{
  "source_code": "string",
  "language_id": "71", (for Python)
  "stdin": "string",
  "expected_output": "string", (w.r.t stdout, users need to print their answers ~ Kattis)
  "max_processes_and_or_threads": 1,
  ["cpu_time_limit": 10.0 (in seconds)],
  ["cpu_extra_time": 1.0 (in seconds)],
  ["memory_limit": 12800 (in KB)]
}

[!NOTE]
The [] values represent optional values you may or may not want to set. Defaults have already been set on the server.

Response
{
 "stdout": null, (or string)
  "time": "0.02", [in seconds]
  "memory": 7172, [in KB]
  "stderr": null, (or string)
  "token": uuid,  [used if we are polling]
  "compile_output": null, (or string)
  "message": null, (or string)
  "status": {
    "id": 3,
    "description": "Accepted"
  }
}

Additional information

N/A

Closing this PR as work is continued on #110.


Bug: downloadManifest doesn't actually download any manifests

Expected behaviour
downloadManifests should iterate through all dependencies of the project it was called on, and download the autodoc manifest for that project dependency.
Observed behaviour
the manifest file - if one exists - is not downloaded
Possible cause
in AbstractManifestResolveTask, a filter is put on the stream of dependencies:
                .filter(dep -> dep instanceof DefaultProjectDependency)

which may be the culprit, as autodoc manifests, that are resolved from Maven central, are of type DefaultExternalModuleDependency.
Possible implementation
filter every dependency of every configuration for DefaultExternalModuleDependency, and attempt to resolve it appending the manifest classifier ("manifest") and the manifest dependency type ("json")
\cc @thomasrutger

I can confirm that .filter(dep -> dep instanceof DefaultProjectDependency) indeed filters out the external manifests


Removed importing of unused symbol

I'm getting the following error with Python 3.5:
Could not import extension sensio.sphinx.bestpractice (exception: cannot import name 'upper')
It seems this package/symbol was removed in Python 3.5 or something, but this symbol is actually not used at all in this file.

👍

Thank you @sstok.


Android Map cannot be displayed

Is this a bug report?
Yes

Have you read the Installation Instructions?
YES

Environment
react-native: 0.51.0
react: 16.0.0
react-native-maps: 0.20.1
phone: xiaomi 5s（Real machine Android7.0）、Google Nexus 5X（Simulator Android7.0）

Steps to Reproduce
react-native run-android

Expected Behavior
Map display

Actual Behavior
Map not shown

Reproducible Demo
[https://github.com/react-community/react-native-maps/tree/master/example/examples]
build.gradle
compileSdkVersion 27
buildToolsVersion '27.0.3'

defaultConfig {
    multiDexEnabled true
    applicationId "com.xxxx"
    minSdkVersion 16
    targetSdkVersion 27

}
compile(project(':react-native-maps')) {
    exclude group: 'com.google.android.gms', module: 'play-services-base'
    exclude group: 'com.google.android.gms', module: 'play-services-maps'
}
compile 'com.google.android.gms:play-services-base:10.0.1'
compile 'com.google.android.gms:play-services-maps:10.0.1'

That's an  api key problem

@rborn
AndroidManifest.xml file I have configured.

Try to make an unrestricted key in google console, you have a restricted one for android only now (I think, I cannot read your language 😅)

@rborn ok! Is the SHA-1 value obtained from the .android debug.keystore or is it obtained in my project my-release-key.keystore?

@rborn ok! Is the SHA-1 value obtained from the .android debug.keystore or is it obtained in my project my-release-key.keystore?


Module compiled with Swift 3.0.2 cannot be imported in Swift 3.1

Any news about when newest Realm build is coming for 3.1? Can't compile my code after updating to Xcode 8.3 / Swift 3.1.
Cheers

Had the same problem. Just used the method provided in another post. As I use carthage (which itself downloads the binary by default) just add the --no-use-binaries option to the update command:
carthage update --no-use-binaries
It takes a while .... really a while ... 15 min on a MBP 2015 ;-) but it worked for me and I have the swift 3.1 frameworks now

@Tintenklecks @danieldelouya Or update Carthage to 0.20. Carthage uses pre-built binary only when they were built with the same version of the Swift compiler from 0.20. No longer need to --no-use-binaries :)
https://github.com/Carthage/Carthage/releases/tag/0.20.0

What if I've added the Realm frameworks manually?

@danieldelouya We've released Realm 2.5.0 that is built by Xcode 8.3 https://realm.io/docs/swift/latest/

@kishikawakatsumi Yes thank you! Updated some hours ago and everything works :) Appreciate you guys being quick with these kind of things. Cheers


Provide access loop on iPad2 using es5

I'm using HA 0.90.2
Working normally on MacBook, cell phone and some Fire HD tablet
I've set up Home Panel and it asks to login to HA in order to give it access to its API.
In all the devices I've mentioned it works flawlessly, however, on my iPad 2, when I type in the credentials the hit the login button, the page reloads and returns to the same login page.
I've noticed it uses es5 when trying to login, I've tried to set javascript_version to latest but then it just says 'initializing' and doesn't show anything else.
Nothing on the logs :(

This is a front-end issue and should be posted in https://github.com/home-assistant/home-assistant-polymer.


webhook why once time ?Why cannot alarms be sent all the time in Down state

Is it a duplicate question?
Please search in Issues without filters: https://github.com/louislam/uptime-kuma/issues?q=
Info
Uptime Kuma Version:
Using Docker?: Yes/No
OS:
Browser:
webhook why once time ?Why cannot alarms be sent all the time in Down state

Duplicate of #233


Parameterised expressions for Structs

This PR 'parameterise' Expressions to be able to choose when they can be converted into a StructExpression and when they cannot. This modification allows us to overcome ambiguities with Structs and to adopt the standard Structs syntax:
struct Point{ x: int, y: int }
let p: Point = Point{ x: 1, y: 2 };

It goes on top of PR https://github.com/powdr-labs/powdr/pull/1516 which implements structs, so that one should be reviewed first.

Would it be a lot of work to put this PR first?
It looks quite complicated, but I also don't see a better option.
We want both if a { ... } and if x >= 0 { ... } to work. So the condition should support both Terms and more complex expressions.

We want both if a { ... } and if x >= 0 { ... } to work. So the condition should support both Terms and more complex expressions.

That shouldn't be a problem. The modification, the only thing it doesn't allow in the if, is something like
if X{a:1, b:2}, which is invalid anyway.
Closing this in favor of PR #1627, which includes the modification but not the structs.