Terminated process first.
(首先停止正在執行的OneDrive程序)
taskkill /f /im OneDrive.exe
According to your OS type:
(根據OS版本)
open cmd with administrator permission
(以系統管理員身份執行)
32bit
%SystemRoot%\System32\OneDriveSetup.exe /uninstall
64bit
%SystemRoot%\SysWOW64\OneDriveSetup.exe /uninstall
WebStorm can't resolve alias if project created by vue-cli.
Because vue-cli didn't set up via webpack, the alias can't resolved without webpack config.
To fix this problem, we can specify a webpack config for WebStorm to recognize alias.
[Setting] > [Language & Frameworks] > [JavaScript] > [Webpack]
Here are my references.
[1] https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000556284/comments/360000093780
[2] https://juejin.cn/post/6844903802185891848
[3] https://cli.vuejs.org/guide/webpack.html#inspecting-the-project-s-webpack-config
Updated
In unknown problem, all above action can't fix the resolution issue. But I found some trick: Go to any *.vue file, move to import block, right click on any component then install it. And it will solved. Unbeleible. Amazing.
Updated-2
No need to set webpack config because it always says:
Can't analyse webpack.config.js: coding assistance will ignore module resolution rules in this file.
The rest current setting: node_module was excluded. src was rescouce root.
Rewritre vue.config.js, let it re-index, then it can resolved correctly.
I rewrite
config.resolve.alias
.set('@img', path.resolve(__dirname, 'src/asset/images'))
.set('@common', path.resolve(__dirname, 'src/components/common'))
.set('Source', path.resolve(__dirname, 'src')); toconfig.resolve.alias
.set('_img', path.resolve(__dirname, 'src/asset/images'))
.set('_common', path.resolve(__dirname, 'src/components/common'))
.set('Source', path.resolve(__dirname, 'src')); then re-write backconfig.resolve.alias
.set('@img', path.resolve(__dirname, 'src/asset/images'))
.set('@common', path.resolve(__dirname, 'src/components/common'))
.set('Source', path.resolve(__dirname, 'src'));
Updated-3
[Setting] > [Language & Frameworks] > [JavaScript] > [Webpack]
=> Set as Automatic.
Select node_module folder, right click to popup menu, click "Optimize Imports"
=> it's work!Or, select "src" root, do "Optimize Imports".
=> it's work!Or, select any single *.vue, do "Optimize Imports".
[1] https://youtrack.jetbrains.com/issue/WEB-27933
這有可能是該BAT檔的文件編碼選到UTF-8。
要正確顯示BAT檔，需改成ANSI格式。
可利用Notepad++或以記事本開啟BAT檔後另存新檔時將編碼改選為ANSI
以上
How to TURN ON HPET
[Credit] NavJack27
to enable HPET - bcdedit /set useplatformclock true
to disable HPET - bcdedit /deletevalue useplatformclock串AWS S3 SDK時
要下載一個項目，使用 Signature的下載方式
const getS3SignedDocumentURL = (docName) => {
const url = s3.getSignedUrl('getObject', {
Bucket: <aws-s3-bucket-name>,
Key: <aws-s3-object-key>,
Expires: <url-expiry-time>,
});
return url;
};但會因為檔案預設的 Content-Type 被 Browser 處理(例如txt就直接打開)所以需要指定一個 Content-Disposition兩個方法1.在網址後加上
String url = serverURL+'/'+bucketName+'/'+codedFilename+'?response-content-disposition='+EncodingUtil.urlEncode('attachment; filename=abc.doc','UTF-8')+'&AWSAccessKeyId='+awskey+'&Expires='+Lexpires+'&Signature='+codedsigned;
然後含這串signed的文字給後端去算signed
2.直接在Header裡加上ResponseContentDisposition: 原因是若後端已經拿算好的URI去計算Signed的話，只能靠在呼叫AWS s3 sdk 時加上ResponseContentDisposition
const getS3SignedDocumentURL = (docName) => {
const url = s3.getSignedUrl('getObject', {
Bucket: <aws-s3-bucket-name>,
Key: <aws-s3-object-key>,
Expires: <url-expiry-time>,
ResponseContentDisposition: `attachment; filename="${docName}"`
});
return url;
};
參考資料https://stackoverflow.com/questions/59684182/s3-presigned-url-multiple-content-disposition-headershttps://stackoverflow.com/questions/19046718/aws-s3-force-file-download-using-response-content-disposition
打開bash後，要編寫變數可以寫在 ~/.bash_profile 或 ~/.bashrc。
也許還聽過 /etc/profile
位置不同但效果相同，有想過這些順序和情境到底怎麼使用嗎？
execute /etc/profile
IF ~/.bash_profile exists THEN
execute ~/.bash_profile
ELSE
IF ~/.bash_login exist THEN
execute ~/.bash_login
ELSE
IF ~/.profile exist THEN
execute ~/.profile
END IF
END IF
END IFIF ~/.bash_logout exists THEN
execute ~/.bash_logout
END IFIF ~/.bashrc exists THEN
execute ~/.bashrc
END IF參考文章在此
Execution sequence for .bash_profile, .bashrc, .bash_login, .profile and .bash_logout
https://www.thegeekstuff.com/2008/10/execution-sequence-for-bash_profile-bashrc-bash_login-profile-and-bash_logout/