瀏覽器的 console log 幾種不同呈現方式

瀏覽器在 Debug 常常使用 console.log(),除了 console.log 外,還有沒有更多的參數可以使用呢?

  • console.log():標準的文字
  • console.error():出現紅字錯誤文字 和 錯誤的 X
  • console.warn():出現黃色警告文字 和 警告的 !
  • console.table():可於 console 出現表格
  • 客製化 console.log:(前景綠字、背景黃色、24px 字體大小)
    (() => {
        console.log('%c%s', 'color: green; background: yellow; font-size: 24px;','Success!')
    })();

詳見此篇:Better console.logs

Git 遇到 GnuTLS handshake error 解法

Git 想要 clone Github 的資料,卻遇到下述錯誤:

fatal: unable to access 'https://github.com/tsung/config/': gnutls_handshake() failed: Error in protocol version

錯誤訊息主要是「Error in protocol version、TLS」,遇到這個問題該怎麼解決呢?

閱讀全文〈Git 遇到 GnuTLS handshake error 解法〉

Linux APT 遇到 NO_PUBKEY 的 GPG error 解法

Debian / Ubuntu Linux 若使用外部套件(Apt sources.list 有額外增加),apt update 常常會遇到下述訊息:

由於無法取得它們的公鑰,以下簽章無法進行驗證: NO_PUBKEY 9334A25F8507EFA5

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9334A25F8507EFA5

W: GPG error: http://repo.percona.com/apt stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9334A25F8507EFA5

要怎麼解決呢?

閱讀全文〈Linux APT 遇到 NO_PUBKEY 的 GPG error 解法〉

PHP json_decode 遇到 Control character error 解法

PHP 使用 json_decode() 遇到下述錯誤訊息:(由 json_last_error_msg() 抓到的訊息)

Control character error, possibly incorrectly encoded

要怎麼解決呢?

閱讀全文〈PHP json_decode 遇到 Control character error 解法〉

Python3 遇到 UnicodeEncodeError: ascii codec 錯誤解法

Python3 遇到下述問題:

UnicodeEncodeError: 'ascii' codec can't encode characters in position 0–9: ordinal not in range(128)

此錯誤訊息,要怎麼解決呢?

一般這個都在 Python2 看到,沒想到在 Python3 也會遇到.. @.@a..

閱讀全文〈Python3 遇到 UnicodeEncodeError: ascii codec 錯誤解法〉

FB Graph 登入 API Error 需要確認 redirect_uri 的問題修復 (v2.10)

Facebook 的 API v2.4 於 2017/10/9 就不支援了,需要升級上去,要升級就乾脆升級到最新的 v2.10,但是卻遇到下述錯誤:(使用 PHP SDK:php-graph-sdk)

Graph returned an error: Error validating verification code. Please make sure your redirect_uri is identical to the one you used in the OAuth dialog request,

註:於測試環境都正常,但是上線後卻都無法登入成功

閱讀全文〈FB Graph 登入 API Error 需要確認 redirect_uri 的問題修復 (v2.10)〉

Linux 修正大量 GPG error BADSIG 的問題

Debian / Ubuntu Linux 遇到大量的 GPG error (BADSIG) 要怎麼解決呢?

錯誤訊息如下述:

問題1

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com stable Release: 以下簽名無效: BADSIG A040830F7FAC5991 Google, Inc. Linux Package Signing Key \<[email protected]\>
W: 無法取得 http://dl.google.com/linux/mod-pagespeed/deb/dists/stable/Release,
W: Some index files failed to download. They have been ignored, or old ones used instead.

問題2

W: GPG error: http://dl.google.com stable Release: The following signatures were invalid: BADSIG A040830F7FAC5991 Google, Inc. Linux Package Signing Key \<[email protected]\>
W: GPG error: http://security.ubuntu.com precise-security Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key \<[email protected]\>
W: GPG error: http://extras.ubuntu.com precise Release: The following signatures were invalid: BADSIG 16126D3A3E5C1192 Ubuntu Extras Archive Automatic Signing Key \<[email protected]\>
W: GPG error: http://ppa.launchpad.net precise Release: The following signatures were invalid: BADSIG 531EE72F4C9D234C Launchpad webupd8
W: GPG error: http://in.archive.ubuntu.com precise Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key \<[email protected]\>
W: GPG error: http://in.archive.ubuntu.com precise-updates Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key \<[email protected]\>

閱讀全文〈Linux 修正大量 GPG error BADSIG 的問題〉