Just chat.deepseek.com with prompts adapted from this gist.
qX_0 variants, they are actually quite straight-forward so deepseek can come up with a correct result in 1 shot.qX_K it's more complicated, I would say most of the time I need to re-prompt it 4 to 8 more times.q6_K, the code never works until I ask it to only optimize one specific part, while leaving the rest intact (so it does not mess up everything)
I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.
| import argparse | |
| import random | |
| import sys | |
| from transformers import AutoModelForCausalLM, AutoTokenizer, DynamicCache | |
| import torch | |
| parser = argparse.ArgumentParser() | |
| parser.add_argument("question", type=str) | |
| parser.add_argument( |
Instructions to obtain WireGuard details of your NordVPN account. These can be used to setup a WireGuard tunnel on your router to NordVPN.
Source: https://forum.gl-inet.com/t/configure-wireguard-client-to-connect-to-nordvpn-servers/10422/27
If you have any linux machine, use that or install a vm if you don't have one.
Get their official linux app installed. Make sure you have wireguard installed too. And set the used technology to Nordlynx by running nordvpn set technology nordlynx
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
| <html> | |
| <head> | |
| <meta name="mobile-web-app-capable" content="yes" /> | |
| <meta name="apple-touch-fullscreen" content="yes" /> | |
| <meta name="apple-mobile-web-app-title" content="Expo" /> | |
| <meta name="apple-mobile-web-app-capable" content="yes" /> | |
| <meta name="apple-mobile-web-app-status-bar-style" content="default" /> | |
| <link | |
| rel="apple-touch-icon" | |
| sizes="180x180" |
In the new year, I plan on archiving the repositories below. Because I plan on only archiving the repositories, any project that depends on any of these projects will continue to work. However, I will no longer be accepting issues or pull requests and will never tag a new release.
The reality of each of the projects listed below is that I've almost completely ignored issues and pull requests for
If you ever need to modify the proguard rules for the Android-part of your Expo managed workflow, you can achieve this by using a config plugin.
./plugins in the project root folder.withProguardRules.js and my-proguard-rules.pro in the folderplugins array of your app.config.js (or app.json if you're using that instead).NOTE: if you rename your .pro file, don't forget to change the two occurrences of my-proguard-rules in withProguardRules.js as well.
This gist contains lists of modules available in
in AWS Lambda.