Do you read the FAQ?
Yes.
Describe the bug:
Live sass compiler with https://github.com/ritwickdey/vscode-live-sass-compiler make style.css.min file but this file do not auto upload
in sftp.json (accesses are hide, only one file do not upload after save):
{
"name": "name",
"host": "host",
"protocol": "ftp",
"port": 21,
"username": "username",
"password": "password",
"remotePath": "/remotePath/",
"uploadOnSave": true,
"watcher": {
"files": "/style.min.css",
"autoUpload": true
}
}
What i need to do to make auto upload generation file style.min.css?
Related
I need to use two reporters with my Cypress tests: mochawesome to generate html reports, and autoset-status-cypress-testrail-reporter to publish test results to Testrail.
The main tool I could find that would enable me to use multiple reporters is cypress-multi-reporters.
However, If I try to use cypress-multi-reporters with autoset-status-cypress-testrail-reporter, alone or in conjunction with mochawesome as below (in cypress.json), it does not work. It will not print out any errors, but it just will not publish the results to Testrail, and it will not generate the mochawesome reports.
{
"reporterEnabled": "mochawesome, autoset-status-cypress-testrail-reporter",
"mochawesomeReporterOptions": {
"reportDir": "cypress/reports",
"overwrite": false,
"html": true,
"json": false
},
"autosetStatusCypressTestrailReporterReporterOptions": {
"host": "https://xxxxxx/",
"username": "xxxxx",
"password": "xxxx",
"projectId": 1,
"runId": 1234
}
}
Can anyone tell me why the above is not working, or suggest a similar tool that would work with both mochawesome and autoset-status-cypress-testrail-reporter?
Got this to work in the end. The solution was
OPTION 1 - to include only the below in cypress.json:
"reporter": "cypress-multi-reporters",
"reporterOptions": {
"configFile": "reporter-config.json"
}
Then to create a new file called reporter-config.json, and add the config for each reporter in there:
{
"reporterEnabled": "mochawesome, autoset-status-cypress-testrail-reporter",
"mochawesomeReporterOptions": {
"reportDir": "cypress/reports",
"overwrite": false,
"html": true,
"json": false
},
"autosetStatusCypressTestrailReporterReporterOptions": {
"host": "https://xxxxxx/",
"username": "xxxxx",
"password": "xxxx",
"projectId": 1,
"runId": 1234
}
}
OPTION 2 - to have everything inside cypress.json, like so:
"reporter": "cypress-multi-reporters",
"reporterOptions": {
"reporterEnabled": "mochawesome, autoset-status-cypress-testrail-reporter",
"mochawesomeReporterOptions": {
"reportDir": "cypress/reports",
"overwrite": false,
"html": true,
"json": false
},
"autosetStatusCypressTestrailReporterReporterOptions": {
"host": "https://xxxxxx/",
"username": "xxxxx",
"password": "xxxx",
"projectId": 1,
"runId": 1234
}
}
I have worked out how to do it, but is this 'supported', Eshan or pyRevit community?
How to load extension for all existing and new-logins for pyRevit users:
If I:
Get the extensions from the user profile pyRevit 'extensions' folder and copy them to the Program Files pyRevit-Master folder, and then
Add the users extensions.json values to the pyRevit-Master extensions.json, and then
set the "builtin" to "False" and the "default_enabled" to "True", like below?
{
"builtin": "False",
"default_enabled": "True",
"type": "extension",
"rocket_mode_compatible": "False",
"name": "PyRevitPlus",
"description": "Extensions for PyRevit",
"author": "Gui Talarico",
"author_profile": "https://github.com/gtalarico",
"url": "https://github.com/gtalarico/pyrevitplus.git",
"website": "https://github.com/gtalarico/pyrevitplus",
"image": "",
"dependencies": []
},
Cheers!
I've installed ftp-simple on vs-code (I can connect with FileZilla) and
I pressed F1, typed config:
[
{
"name": "dev-server",
"host": "192.168.0.140",
"port": 21,
"type": "ftp",
"username": "user",
"password": "12345",
"path": "/var/www/WebApp",
"autosave": true,
"confirm": true
}
]
Pressed F1 again, remote directory open to workspace..and nothing happens.
I've noticed it does take quite a while, you have to be patient, it will load the remote structure eventually. Once loaded, then save as a Workspace.
When we try to download a file with an extension of .mp4 from Google Photo using Google Drive API, the downloaded file always has different md5 hash value with the md5Checksum field provided by remote metadata.
For example, assume there exists a file name video.mp4 on Google Photo. After we download the file using either one of the following URL:
(v2) https://doc-14-6c-docs.googleusercontent.com/docs/securesc/[SOME_VALUES]?h=[SOME_VALUES]&e=download&gd=true
(v3) https://www.googleapis.com/drive/v3/files/[FILEID]?alt=media
Both methods will download the file correctly on a local machine. The file size is also the same as the fileSize field of remote metadata.
However, the md5 hash value is inconsistent with the md5Checksum field of remote metadata. For example, if we enter $md5sum video.mp4 command, we may got 5cf9fb1bb88dc9bf38d1de5c9180dc4e video.mp4. This is not the hash recorded at remote metadata.
All other files work fine (size and hash are consistent), except for the files with an extension of .mp4. By the way, we use CURL to send a request to Google Drive API to download these files, instead of using any of Google Drive SDK.
Hope someone can help us, thanks!
[Update] more explanation
These files are from our customer's Google Photo. We don't know the exact way to reproduce such situaion. We provide the metadata of one of problematic file for your reference. (we remove some private information.)
{
"kind": "drive#file",
"id": "(REMOVED)",
"etag": "(REMOVED)",
"selfLink": "(REMOVED)",
"webContentLink": "(REMOVED)",
"alternateLink": "(REMOVED)",
"embedLink": "(REMOVED)",
"iconLink": "(REMOVED)",
"thumbnailLink": "(REMOVED)",
"title": "(REMOVED)",
"mimeType": "video/mp4",
"description": "",
"labels": {
"starred": false,
"hidden": false,
"trashed": false,
"restricted": false,
"viewed": false
},
"createdDate": "2016-10-10T11:42:25.000Z",
"modifiedDate": "2016-10-18T23:01:19.000Z",
"modifiedByMeDate": "2016-10-18T23:01:19.000Z",
"markedViewedByMeDate": "1970-01-01T00:00:00.000Z",
"version": "133589",
"parents": [
{
"kind": "drive#parentReference",
"id": "(REMOVED)",
"selfLink": "(REMOVED)",
"parentLink": "(REMOVED)",
"isRoot": false
}
],
"downloadUrl": "(REMOVED)",
"userPermission": {
"kind": "drive#permission",
"etag": "(REMOVED)",
"id": "me",
"selfLink": "(REMOVED)",
"role": "owner",
"type": "user"
},
"originalFilename": "(REMOVED)",
"fileExtension": "mp4",
"md5Checksum": "c5a208198614c34b6fc61186d025df77",
"fileSize": "15284923",
"quotaBytesUsed": "0",
"ownerNames": [
"(REMOVED)"
],
"owners": [
{
"kind": "drive#user",
"displayName": "(REMOVED)",
"picture": {
"url": "(REMOVED)"
},
"isAuthenticatedUser": true,
"permissionId": "(REMOVED)",
"emailAddress": "(REMOVED)"
}
],
"lastModifyingUserName": "(REMOVED)",
"lastModifyingUser": {
"kind": "drive#user",
"displayName": "(REMOVED)",
"picture": {
"url": "(REMOVED)"
},
"isAuthenticatedUser": true,
"permissionId": "(REMOVED)",
"emailAddress": "(REMOVED)"
},
"capabilities": {
"canCopy": true,
"canEdit": true
},
"editable": true,
"copyable": true,
"writersCanShare": true,
"shared": false,
"explicitlyTrashed": false,
"appDataContents": false,
"headRevisionId": "(REMOVED)",
"videoMediaMetadata": {
"width": 720,
"height": 1280,
"durationMillis": "43697"
},
"spaces": [
"photos",
"drive"
]}
As you can see, the md5Checksum field shows c5a208198614c34b6fc61186d025df77 in the metadata. However, the actual md5 hash value equals to 95be52d721e2f5d8d02650b27095d466 instead.
What's the simplest folder structure I can use with Nightwatchjs? It will be used locally and for continuous integration. Currently I can't even get the demo to work. I have six errors:
module.js:469:15
module.js:417:25
bootstrap_node.js:604.10
bootstrap_node.js:394:7
bootstrap_node.js:149:9
bootstrap_node.js:509:3.
I realize this is a beginner question. I've been using Telerik and TestComplete for a few years and now we want to do CI properly so Selenium is the way to go. I'm comfortable with javascript but kind of bad at file path stuff.
What's the simplest folder structure I can use with Nightwatchjs?
The simplest NightwatchJS folder structure is:
To have 2 files (a configuration file and a file which contain you tests):
nightwatch.json
app.js (you can rename it as you want)
Example
1) nightwatch.json
{
"src_folders": [
"app.js"
],
"live_output": false,
"tests_output": "test/tests_output/",
"detailed_output": true,
"selenium": {
"start_process": false,
"host": "hub.browserstack.com",
"port": 80
},
"test_workers": {
"enabled": false,
"workers": "auto"
},
"test_settings": {
"chrome": {
"selenium_port": 80,
"selenium_host": "hub.browserstack.com",
"silent": true,
"desiredCapabilities": {
"os": "Windows",
"os_version": "10",
"browserName": "chrome",
"resolution": "1024x768",
"javascriptEnabled": true,
"acceptSslCerts": true,
"browserstack.video": "true",
"browserstack.debug": "true",
"browserstack.user": "<yourUsername>",
"browserstack.key": "<yourPassword>"
}
}
}
}
2) app.js
module.exports = {
'Does-stackoverflow-works': function (browser) {
browser
.url("http://stackoverflow.com/questions")
.waitForElementPresent('body', 2000, "Display latest Stackoverflow questions")
.end()
}
};
Run
$> nightwatch --env chrome
Output