Use the format below to document issues. Use screenshots and/or screen recording when necessary, using a tool like Monosnap.
TODO: write a summary of the issue.
- TODO Describe steps needed to trigger the issue.
Use the format below to document issues. Use screenshots and/or screen recording when necessary, using a tool like Monosnap.
TODO: write a summary of the issue.
| document.querySelectorAll("[name='g-recaptcha-response'], [name='token']").forEach(function(element) { | |
| element.value = 'bad-recaptcha-token'; | |
| }); |
| Index:/src/view/frontend/web/template/shipping-address/address-renderer/default.html | |
| IDEA additional info: | |
| Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP | |
| <+>UTF-8 | |
| =================================================================== | |
| diff --git a/src/view/frontend/web/template/shipping-address/address-renderer/default.html b/src/view/frontend/web/template/shipping-address/address-renderer/default.html | |
| --- a/src/view/frontend/web/template/shipping-address/address-renderer/default.html | |
| +++ b/src/view/frontend/web/template/shipping-address/address-renderer/default.html (date 1709742374536) | |
| @@ -11,6 +11,11 @@ | |
| <div class="shipping-address-item" css="'selected-item' : isSelected() , 'not-selected-item':!isSelected()"> |
For future reference:
I just had to troubleshoot a script that ran so long that it eventually died without any relevant errors ([pid 6048:tid 139809649469184] (104)Connection reset by peer: [client 184.4.89.70:0] FastCGI: comm with server "/var/run/a49982b9-remi-safe-php81.fcgi" aborted: read failed, referer was getting written to the Apache error logs).
Thankfully I was able to reproduce the issue locally. Here are the steps I took in Warden to troubleshoot:
In pub/index.php I added this line: set_time_limit(15); above the $bootstrap->run($app);
cd <PATH TO MAGENTO 2 DIRECTORY>
This document covers how to export Jira tickets to PDF from the on-premise version of Jira. For the cloud version of Jira, you can write a script to download Word versions of each issue (e.g., https://krakencommerce.atlassian.net/si/jira.issueviews:issue-word/DMC-95/DMC-95.doc) and you don't need this approach.
https://krakencommerce.atlassian.net/browse/DMC-1
https://krakencommerce.atlassian.net/browse/DMC-2
| #!/bin/bash | |
| set -euo pipefail | |
| FRONT_URL="${FRONT_URL:-https://app.exampleproject.test/}" | |
| echo "==> [$(date +%H:%M:%S)] waiting on readiness" | |
| ELAPSED_SECONDS=0 | |
| while : ; do | |
| ELAPSED_SECONDS=$(echo ${ELAPSED_SECONDS}+2 | bc) | |
| RESPONSE_CODE=$(curl -sI "${FRONT_URL}" 2>/dev/null | head -n1 | awk '{print $2}') |
This applies to Magento 2.3+.
If you have your crontab configured to run the bin/magento cron:run command using flock, you should either:
flock, since it's technically not necessary as of Magento 2.3.2-o command to flock, as this will prevent the indefinitely running bin/magento queue:consumers:start processes spawned by bin/magento cron:run from holding a lock when they shouldn't be.Before:
See this Github comment thread for any issues or additional context for getting Warden running on Windows with WSL 2.
The instructions below cover how to install Warden on Windows, using WSL 2.
Ubuntu 20.04 program that will have been installed in the step above (If you want to be able to copy/paste, see here. Going forward, this article assumes you will run all commands inside of the Ubuntu terminal| # clear the entire cache | |
| varnishadm "ban req.url ~ /" | |
| # monitor varnish log with multiple patterns | |
| varnishlog | grep 'eqURL\|Age:\|VCL_call\|TTL\|Expires:\|Cache-Control:' | |
| # Use a query with varnishlog to watch requests from a specific IP | |
| varnishlog -q 'ReqHeader:X-User-IP eq "1.2.3.4" or BereqHeader:X-User-IP eq "1.2.3.4"' | |
| # Monitor PURGE requests hitting Varnish |