Hi everyone,
Bit of a different topic but I was using Rocksmith 2014 and ran into the following error:
rocksmith 2014.exe has stopped working windows 10 Faulting module name: igdumd32.dll
The fix is pretty easy, but somewhat annoying, unplug any external monitors (second, third monitor).
Hi everyone,
I ran into the following error while using the AWS IoT python SDK:
Error in discovery! Type: Error message: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)
It turns out that this was because I was using the wrong root certificate. In the documentation there are five certificates listed:
If you’re using the console to create the certificate and have already downloaded your device cert, public cert and private key you can use Amazon Root CA 1: https://www.amazontrust.com/repository/AmazonRootCA1.pem
As soon as that was added the error was resolved and I was able to move onto the next one. I found most of the info on the AWS forums but let me know if you have any questions: https://forums.aws.amazon.com/thread.jspa?threadID=286871
Hi everyone,
Just a quick post on how to configure wireless info on a raspberry pi. To start with, open the config file:
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
You can then add any number of connections to the file with varying priorities:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=AU
network={
ssid="Mobile Network"
psk="YOUR_PASSWORD"
key_mgmt=WPA-PSK
priority=2
}
network={
ssid="Home Network"
psk="YOUR_PASSWORD"
key_mgmt=WPA-PSK
priority=10
}
Then save the file. Your raspberry pi will now connect to the network with the highest priority first (home network), when that’s not available it will use the network with the lower priority (mobile network).
The official doco is actually pretty good for this use case if you need more info: https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md
Hi everyone,
I ran into the following error while using “fetch as Google” and none of my pages were being indexed correctly:
It took a while to find a solution but after some Googling I found that GoogleBot currently uses Chrome v41. You can download the mini installer of Chromium v41 which will run in parallel with your existing Chrome version: https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Win%2F310958%2Fmini_installer.exe?generation=1420864313749000&alt=media
After downloading Chromium you can just debug normally via the console. In my case, Chrome v41 didn’t like the following command:
document.head.append(script);
If you’re using a front-end framework like ReactJS, AngularJS or Vue you’ll often just need to add babel polyfill:
npm install babel-core --save-dev
Then add this as the first line in your entry point e.g. index.js:
import 'babel-core/polyfill';
It’s important that the polyfill import is added as the first line otherwise anything added before it won’t work.
If you’re getting an error about Headers, you may also need to install the following:
npm install whatwg-fetch --save
Add then add this import just below your babel polyfill:
import 'whatwg-fetch'
Thanks to tomekrudzki on Reddit for the link to Chromium v41: Chrome 41 the key to successful website rendering
Hi everyone,
I ran into the following error while completing an AWS tutorial: https://github.com/aws-samples/aws-serverless-workshops/tree/master/DevOps/2_ContinuousDeliveryPipeline
> uni-api-test@1.0.0 test C:UsersChris-PCsourcereposUniApiuni-api
> echo ‘Error: no test specified’
‘Error: no test specified’
The solution was to add the following line to my package.json file:
Now when running npm test I get the expected test output:
1) Reading Unicorns
errors on missing unicorn data:
AssertionError [ERR_ASSERTION]: 500 == 404
+ expected – actual
-500
+404
at lambda.lambda_handler (testread.spec.js:77:20)
at appread.js:20:10
at Object.get (testread.spec.js:34:33)
at Object.exports.lambda_handler (appread.js:18:13)
at Context. (testread.spec.js:65:16)
npm ERR! Test failed. See above for more details.
Thanks to this link for the answer: https://teamtreehouse.com/community/when-i-run-test-i-am-getting-an-error-that-says-no-test-specified
Hi everyone,
Just testing out .Net Core 2.1 and noticed that all of my JSON properties are being returned in lowercase despite being defined as uppercase. It turns out that this is configurable:
// Change from this
services.AddMvc();
// To this
services
.AddMvc()
.AddJsonOptions(options => options.SerializerSettings.ContractResolver = new DefaultContractResolver());
Check out these links for more info:
https://stackoverflow.com/a/38202543/522859
https://github.com/aspnet/Announcements/issues/194
Hi everyone,
A quick post on a function for parsing hash args when using AWS Congito.
//jsfiddle.net/4eo7836j/embed/
Just in case the fiddle ever disappears:
const parseHashArgs = aURL => {
aURL = aURL || window.location.href;
var vars = {};
var hashes = aURL.slice(aURL.indexOf('#') + 1).split('&');
for (var i = 0; i 1) {
vars[hash[0]] = hash[1];
} else {
vars[hash[0]] = null;
}
}
return vars;
};
document.body.append(parseHashArgs("#id_token=testtokenval&token_type=bearer&expires_in=3600")["id_token"]);
Thanks to this link on Github: https://gist.github.com/miohtama/1570295/289d5a82e65663c9b515c88186a268c6dd1fddb7
Hi everyone,
Just a quick post on installing the AWS Inspector Agent on a Windows EC2 instance.
Open PowerShell and run the following command:
(new-object System.Net.WebClient).DownloadFile('https://inspector-agent.amazonaws.com/windows/installer/latest/AWSAgentInstall.exe','C:UsersAdministratorDesktopAWSAgentInstall.exe')
On your desktop, right click on AWSAgentInstall.exe and select run as administrator. Follow the prompts.
Go to run, and execute services.msc. You should now see the Amazon SSM Agent:
If you go to your amazon console > amazon inspector > assessment targets > Click on your relevant target > Preview Target:
Your agent status should now be healthy.
Thanks to these links for the info:
https://superuser.com/a/330754/124014
https://docs.aws.amazon.com/inspector/latest/userguide/inspector_installing-uninstalling-agents.html#install-windows
Hi everyone,
For a project I’m currently working on I needed a dynamic robots.txt. Because our test environment is public facing we want to keep it from being indexed by Google etc. It took a bit of Googling to find a solution that worked, but in the end it was actually pretty simple.
Here’s the action in one of the API Controllers:
public class UtilitiesController : CustomBaseApiController
{
[Route("Robots.txt")]
[HttpGet]
public HttpResponseMessage GetRobotsFile()
{
var resp = new HttpResponseMessage(HttpStatusCode.OK);
var stringBuilder = new StringBuilder();
if (Helpers.IsProduction())
{
// Allow bots in production
stringBuilder.AppendLine("user-agent: *");
stringBuilder.AppendLine("disallow: ");
}
else
{
// Don't allow bots in non-production environments
stringBuilder.AppendLine("user-agent: *");
stringBuilder.AppendLine("disallow: *");
}
resp.Content = new StringContent(stringBuilder.ToString());
return resp;
}
}
Also need to add the following to your web.config so that the robots.txt file can processed by the routing handler. Without this IIS will attempt to serve it as a static file and will return a 404 when it’s not found:
In production you’ll end up with the following:
user-agent: * disallow:
And any other environments:
user-agent: * disallow: *
Thanks to these answers on stackoverflow for the info:
https://stackoverflow.com/a/52270877/522859
https://stackoverflow.com/a/17037935/522859
Hi everyone,
I’ve been having a bit of an issue with my AWS app going to sleep and taking a long time to handle initial requests.
I’m using .NET with Elastic Beanstalk on a T2 Micro Instance and MSSQL Server Express on RDS. My FrontEnd is a static ReactJS app that sits in S3 behind CloudFront. There’s also a load balancer across the backend.
My frontend was always instant but my initial Api calls were timing out. This ruled out S3 and CloudFront, leaving the following:
After a bit of Googling I came across something that looked fairly promising – MSSQL Server Express has a property called AutoClose set to ‘ON’ by default. AWS appears to correct this as mine was off however it’s worth checking:
-- If set to zero then auto close is off
SELECT DATABASEPROPERTY('mydatabasename','IsAutoShrink')
-- Check all instances at once
SELECT name,is_auto_close_on FROM sys.databases
-- Turn off if on
ALTER DATABASE myDB SET AUTO_CLOSE OFF
In my case the actual problem turned out to be IIS idle timeout. By default IIS automatically times out an application after 20 minutes. In order to disable this create the following ebextension:
commands:
setIdleTimeoutToZero:
cwd: "C:\windows\system32\inetsrv"
command: "appcmd set apppool /apppool.name:DefaultAppPool /.processModel.idleTimeout:0.00:00:00"
If you haven’t done this before, all you need to do is create a folder called .ebextensions under your project directory. Then create a new file called iis-idle-timeout.config and add the yaml to it. If you need more information on iis timing out check out this great blog post: https://notebookheavy.com/2017/06/21/set-iis-idle-timeout-elastic-beanstalk/
Thanks to these sources for the solutions:
Disable auto_close: https://stackoverflow.com/a/1750400/522859
IIS Timeout: https://notebookheavy.com/2017/06/21/set-iis-idle-timeout-elastic-beanstalk/
EBExtension Info: http://notebookheavy.com/2017/05/01/auto-install-newrelic-agent-elastic-beanstalk/
What I Broke - Programming and Web Development 