| <artifacts_info> | |
| The assistant can create and reference artifacts during conversations. Artifacts are for substantial, self-contained content that users might modify or reuse, displayed in a separate UI window for clarity. | |
| # Good artifacts are... | |
| - Substantial content (>15 lines) | |
| - Content that the user is likely to modify, iterate on, or take ownership of | |
| - Self-contained, complex content that can be understood on its own, without context from the conversation | |
| - Content intended for eventual use outside the conversation (e.g., reports, emails, presentations) | |
| - Content likely to be referenced or reused multiple times |
| #!/usr/bin/env python3 | |
| # -*- coding: utf-8 -*- | |
| # Copyright (c) Odd Stråbø <[email protected]> | |
| # | |
| import os | |
| from opencv_test import Session, Image, Hash, HASHERS | |
| from gmpy2 import hamdist |
| Disclaimer: The instructions are the collective efforts from a few places online. | |
| Nothing here is my original. But I want to put them together in one place to save people from spending the same time as I did. | |
| First off, bundle. | |
| ================== | |
| 1. cd to the project directory | |
| 2. Start the react-native packager if not started | |
| 3. Download the bundle to the asset folder: | |
| curl "http://localhost:8081/index.android.bundle?platform=android" -o "android/app/src/main/assets/index.android.bundle" |
| for f in *.aud; do echo '#!AMR' | cat - $f > $f.amr; done | |
| for f in *.pic_hd; do mkdir -p convert; cp $f convert/$f.jpg; done |
| <?xml version="1.0" encoding="utf-8"?> | |
| <selector xmlns:android="http://schemas.android.com/apk/res/android"> | |
| <item android:state_enabled="false" | |
| android:color="@color/flat_disabled_text"/> | |
| <item android:color="@color/flat_normal_text"/> | |
| </selector> |
Update: For those interested, here's the version for updating from Android 5.1.0 (LMY47D/LMY47I) to Android 5.1.1 (LMY48B):
https://gist.github.com/eyecatchup/dab5cf7977008e504213
UPDATE `NEXUS 5`
SET `VERSION`='5.0.1', `BUILD`='LRX22C', `RECOVERY`='CUSTOM', `ROOTED`=1
WHERE `VERSION`='5.0' && `BUILD`='LRX21O' && `RECOVERY`='CUSTOM' && `ROOTED`=1
&& `WANNA_KEEP_USERDATA`=1;
| good, 你已经有了一个自己的shadowsocks代理了，现在想要把这个代理公布出去给所有人分享。 | |
| 但是没有两个小时，代理就没法使用了，为什么？因为你需要额外注意以下事项（以下步骤需要比较高的linux技能） | |
| 本文只关注于确保shadowsocks服务还“活着”，如果你希望让其跑得更快，请参考 | |
| https://github.com/clowwindy/shadowsocks/wiki/Optimizing-Shadowsocks | |
| 1、 shadowsocks的timeout设置 | |
| 超时时间越长，连接被保持得也就越长，导致并发的tcp的连接数也就越多。对于公共代理，这个值应该调整得小一些。推荐60秒。 | |
| 2、 检查操作系统的各种限制 | |
| 对于openvz的vps，特别需要检查一下 |
| if 64 - 64: i11iIiiIii | |
| if 65 - 65: O0 / iIii1I11I1II1 % OoooooooOO - i1IIi | |
| if 73 - 73: II111iiii | |
| if 22 - 22: I1IiiI * Oo0Ooo / OoO0O00 . OoOoOO00 . o0oOOo0O0Ooo / I1ii11iIi11i | |
| import os | |
| if 48 - 48: oO0o / OOooOOo / I11i / Ii1I | |
| if 48 - 48: iII111i % IiII + I1Ii111 / ooOoO0o * Ii1I | |
| if 46 - 46: ooOoO0o * I11i - OoooooooOO | |
| if 30 - 30: o0oOOo0O0Ooo - O0 % o0oOOo0O0Ooo - OoooooooOO * O0 * OoooooooOO | |
| if 60 - 60: iIii1I11I1II1 / i1IIi * oO0o - I1ii11iIi11i + o0oOOo0O0Ooo |
Read the blog at http://fokkezb.nl/2013/09/20/url-schemes-for-ios-and-android-2/
