What is wrong?

Translating. Please wait.(node:78632) UnhandledPromiseRejectionWarning: RequestError: read ETIMEDOUT
at ClientRequest. (/Users/Eugene/node_modules/got/source/request-as-event-emitter.js:178:14)
at Object.onceWrapper (events.js:520:26)
at ClientRequest.emit (events.js:412:35)
at ClientRequest.origin.emit (/Users/Eugene/node_modules/@szmarczak/http-timer/source/index.js:37:11)
at TLSSocket.socketErrorListener (_http_client.js:475:9)
at TLSSocket.emit (events.js:400:28)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(Use node --trace-warnings ... to show where the warning was created)
(node:78632) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:78632) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Thanks for your report. Can you please provide more information about your flow?
1 - The size of your JSON object (number of fields approximately)
2 - Which languages are you translating your JSON object to? (number of languages)
3 - Are you using CLI or functions?

Hi

1237 lines
English to Indonesian
CLI on my MacOS

On 21 Feb 2022, at 15:38, Parvin Eyvazov @.***> wrote:
Thanks for your report. Can you please provide more information about your flow?
1 - The size of your JSON object (number of fields approximately)
2 - Which languages are you translating your JSON object to? (number of languages)
3 - Are you using CLI or functions?
—
Reply to this email directly, view it on GitHub https://github.com/ParvinEyvazov/json-translator/issues/1#issuecomment-1046558208, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBNC5ZWTV4YV34ANDFBCEDU4HTYNANCNFSM5O5NNAFQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

Thank you.
Can you please try the v0.7.0 version? (will be available after 10 hours) I will also mention here when the new release comes.

Sure ))

On 21 Feb 2022, at 15:52, Parvin Eyvazov @.***> wrote:
Thank you.
Can you please try the v0.7.0 version? (will be available after 10 hours) I will also mention here when the new release comes.
—
Reply to this email directly, view it on GitHub https://github.com/ParvinEyvazov/json-translator/issues/1#issuecomment-1046566472, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBNC5ZL2XGG627WC3A46VLU4HVKFANCNFSM5O5NNAFQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

v0.7.0 is available now. Can you please try the same flow?

It has been still working for 2 hours already it it ok for that file?

On 22 Feb 2022, at 03:57, Parvin Eyvazov @.***> wrote:
v0.7.0 is available now. Can you please try the same flow?
—
Reply to this email directly, view it on GitHub https://github.com/ParvinEyvazov/json-translator/issues/1#issuecomment-1047187922, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBNC562L3WMJBQMTHHHOJDU4KKMHANCNFSM5O5NNAFQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

Actually, it is normal for that big file. I translated 700 lines JSON file before, and it took 10 minutes. If there is no error, it will respond.
This package works in async format to make operations fast. That means if there are 5 fields in the object it tries to translate them at the same time. And when sending more than 1000+ requests at the same time to the Google Translate API, response times get longer (Google Translate API makes this latency.). At that time problem occurs on big files. Unfortunately, I can't solve it right now (I don't have much time nowadays) but there can be a way to solve it manually. You can do like this:
Please divide your JSON file into 3 or more pieces, translate them separately and merge it. For example:
You have 1000 lines JSON file (a.json):
Create valid JSON files:
a1.json (from a.json, take 0 to 250 lines)
a2.json (from a.json, take 251 to 500 lines)
a3.json (from a.json, take 501 to 750 lines)
a4.json (from a.json, take 751 to 1000 lines)

And translate them separately. (Don't forget to change the name of the file which will be created each time. Because the new English file name will always be en.json).
Sorry for the problem. I am adding this problem to the roadmap to solve it when I am available.

Thanks
you don't have to say sorry. )) Everything is ok and thanks a lot for your work.

On 22 Feb 2022, at 16:10, Parvin Eyvazov @.***> wrote:
Actually, it is normal for that big file. I translated 700 lines JSON file before, and it took 10 minutes. If there is no error, it will respond.
This package works in async format to make operations fast. That means if there are 5 fields in the object it tries to translate them at the same time. And when sending more than 1000+ requests at the same time to the Google Translate API, response times get longer (Google Translate API makes this latency.). At that time problem occurs on big files. Unfortunately, I can't solve it right now (I don't have much time nowadays) but there can be a way to solve it manually. You can do like this:
Please divide your JSON file into 3 or more pieces, translate them separately and merge it. For example:
You have 1000 lines JSON file (a.json):
Create valid JSON files:
a1.json (from a.json, take 0 to 250 lines)
a2.json (from a.json, take 251 to 500 lines)
a3.json (from a.json, take 501 to 750 lines)
a4.json (from a.json, take 751 to 1000 lines)
And translate them separately. (Don't forget to change the name of the file which will be created each time. Because the new English file name will always be en.json).
Sorry for the problem. I am adding this problem to the roadmap to solve it when I am available.
—
Reply to this email directly, view it on GitHub https://github.com/ParvinEyvazov/json-translator/issues/1#issuecomment-1047527733, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBNC523XDQLFNZIM6VHL3LU4NAIZANCNFSM5O5NNAFQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

just one idea - if you would show the number of lines that is translated already the user can be sure that the process is working and not stuck

On 22 Feb 2022, at 16:10, Parvin Eyvazov @.***> wrote:
Actually, it is normal for that big file. I translated 700 lines JSON file before, and it took 10 minutes. If there is no error, it will respond.
This package works in async format to make operations fast. That means if there are 5 fields in the object it tries to translate them at the same time. And when sending more than 1000+ requests at the same time to the Google Translate API, response times get longer (Google Translate API makes this latency.). At that time problem occurs on big files. Unfortunately, I can't solve it right now (I don't have much time nowadays) but there can be a way to solve it manually. You can do like this:
Please divide your JSON file into 3 or more pieces, translate them separately and merge it. For example:
You have 1000 lines JSON file (a.json):
Create valid JSON files:
a1.json (from a.json, take 0 to 250 lines)
a2.json (from a.json, take 251 to 500 lines)
a3.json (from a.json, take 501 to 750 lines)
a4.json (from a.json, take 751 to 1000 lines)
And translate them separately. (Don't forget to change the name of the file which will be created each time. Because the new English file name will always be en.json).
Sorry for the problem. I am adding this problem to the roadmap to solve it when I am available.
—
Reply to this email directly, view it on GitHub https://github.com/ParvinEyvazov/json-translator/issues/1#issuecomment-1047527733, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBNC523XDQLFNZIM6VHL3LU4NAIZANCNFSM5O5NNAFQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

Great idea. Thank you for the feedback :)

Hi @Aido21 , json-translater now will show the number of lines that are translated already with the 0.8.0 version. Now, it is available to use.
Thank you for your great feedback.

Thanks. I just checked it up
It works pretty fast much faster that i expected but it stuck in line 1650 of my file. And does not translate more
So i see
Translating. Please wait. 1650 of 1724 translated
and no progress more
These lines are
1650: "sections_have_been_sorted": "Sections have been sorted”,
1651: "currently_the_scorm_course_addon_is_deactivate": "Currently the scorm course addon is deactivate",
Cannot understand what is the problem

On 15 Apr 2022, at 08.32, Parvin Eyvazov @.***> wrote:
Hi @Aido21 https://github.com/Aido21 , json-translater now will show the number of lines that are translated already with the 0.8.0 version. Now, it is available to use.
Thank you for your great feedback.
—
Reply to this email directly, view it on GitHub https://github.com/ParvinEyvazov/json-translator/issues/1#issuecomment-1099741454, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBNC55LUUFRS2EEODXCK4TVFC2I3ANCNFSM5O5NNAFQ.
You are receiving this because you were mentioned.

It was after first execution
Now it does not work i just get the different errors about the connection
like this
Translating. Please wait. 1267 of 1724 translated.(node:35328) UnhandledPromiseRejectionWarning: RequestError: socket hang up
at ClientRequest. (/Users/Eugene/node_modules/got/source/request-as-event-emitter.js:178:14)
at Object.onceWrapper (events.js:520:26)
at ClientRequest.emit (events.js:412:35)
at ClientRequest.origin.emit @.***/http-timer/source/index.js:37:11)
at TLSSocket.socketOnEnd (_http_client.js:499:9)
at TLSSocket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1334:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(Use node --trace-warnings ... to show where the warning was created)
(node:35328) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:35328) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
° Translating. Please wait. 1530 of 1724 translated.
It looks like the number of lines is limited

On 15 Apr 2022, at 08.32, Parvin Eyvazov @.***> wrote:
Hi @Aido21 https://github.com/Aido21 , json-translater now will show the number of lines that are translated already with the 0.8.0 version. Now, it is available to use.
Thank you for your great feedback.
—
Reply to this email directly, view it on GitHub https://github.com/ParvinEyvazov/json-translator/issues/1#issuecomment-1099741454, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBNC55LUUFRS2EEODXCK4TVFC2I3ANCNFSM5O5NNAFQ.
You are receiving this because you were mentioned.

The number of lines can be limited by Google Translate API (because of concurrent requests from the same IP address). I will try to find a way to handle these errors. Thank you for the report.
For the current situation, you can try to split your file into 3 different files and translate them one by one and can combine them all until I fix this problem.

Fixed #2 with version 1.0.0
Solution is here


more phase options

Allows separate settings to be used for acceptable phase levels depending on dual-mono vs stereo inputs (relies on information in BEXT CodingHistory). Uses third default option when expected BEXT CodingHistory info is not present.

Will resolve conflicts tomorrow!

Seems to work - lemme know if I didn't catch something broken!


angular2-2.0.0-beta.11 close dialog more than once gives error.

When opening and closing a modal more than once, throws an error of "Error: Task does not support cancellation, or is already canceled." Not sure if this is an angular2 issue or an issue here. It was working on an earlier version before the upgrade.

all good zone.js issue in angular...


[REQUEST] Please add environment variables

After installing using command go install -v github.com/Lu1sDV/wafme0w/cmd/wafme0w@latest, environment variables won't be automatically added.
so only running cat list.txt | wafme0w --concurrency 30 --no-warning --no-generic will give an error wafme0w: command not found

It's most likely a problem with your go installation since it didn't set GOROOT/GOPATH in your shell environment.
Try installing it using this script:
https://github.com/canha/golang-tools-install-script/blob/master/goinstall.sh
Change https://github.com/canha/golang-tools-install-script/blob/master/goinstall.sh#L5 to 1.20 (or grab actual version at https://go.dev/dl/)
It should automatically build it from sources and set correct GOROOT/GOPATH in your shell environment.


Bug when running the code

I have faced this bug when running with train.py , can anyone show me how to fix it?

Have you solved the problem?


Added the some space in 'Contact us' heading and in Contact us form, Incorrect input type in subject field

Thank you for taking the time to file a Bug report.
Describe the bug
The contact page contains several bugs :

'contact us' heading touches the navbar border.
In contact form:

In the subject field, it has 'password' in input type instead of the 'text'.
In the message field, It has only an input field rather than a textarea.
There is no space between the remember me checkbox and the 'send' button.

To Reproduce
Steps to reproduce the behavior:

Go to the website (https://journal-policy-tracker.netlify.app/)
Click on the Contact link in the navbar
Scroll down to the contact form
See an error

Actual behavior
The bugs you can see in the below image:
Screenshots'

Expected behavior

Added some space above the 'contact us' heading.
Change the 'subject' input field with text type instead of the password type.
Added some space in between the remember me checkbox and the 'send' button.
Added the textarea in the 'message' field.

Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome

Smartphone (please complete the following information):

Device:  OnePlus Nord CE
OS:  Android 11
Browser: Chrome
Version [e.g. 22]

Sure, thanks for pointing this out.

Welcome :)
I will make PR for this issue.

Greetings, I have made the PR. kindly review it. Thank you. @padmajabhol

Greetings @padmajabhol, I resolved all the problems and updated the PR. Kindly review it. Thank you

Thanks for the PR @dikshashukla455! We're a bit snowed under with lots of applications and PRs right now, but we'll review this as soon as we get a chance

oh, I lied, Padamaja has already approved - epic!


All icons appearing as empty boxes

Is this package alive? I thought it would be really useful for my app but none of the icons is working.
example: Icon(WeatherIcons.wi_cloudy) or any other icon is not working. All i'm getting is a box kind of looking thing.

I was trying with hot reload, restarting my app completely fixed this. facepalm


Please create a release

the .exe is hard to find

it's in the bin folder?

Sorry for the wait. I created release including the binary.


Make A Person Test Suite Fragile

Describe your problem and how to reproduce it:
The test suite for 'Make A Person' is a little fragile and needs some // Only change... comments.
The below code will fail the test suite even though the object definition is correct because a user changed the code outside of the object definition:
var Person = function(firstAndLast) {
  const names = firstAndLast.split(' ');
  let firstName = names[0];
  let lastName = names[1];
  // Complete the method below and implement the others similarly
  // Getters
  this.getFirstName = function() {
    return firstName;
  };
  this.getLastName = function() {
    return lastName;
  };
  this.getFullName = function() {
    return firstName + " " + lastName;
  };
  // Setters
  this.setFirstName = function(name) {
    firstName = name;
  };
  this.setLastName = function(name) {
    lastName = name;
  }
  this.setFullName = function(name) {
    const names = name.split(' ');
    firstName = names[0];
    lastName = names[1];
  }
};

var bob = new Person('Bob Ross');
bob.getFullName();
bob.setFirstName("Haskell") // This code passes if this line is removed

A fix is to add the // Only change... comments
New starter code:
var Person = function(firstAndLast) {
  // Only change code below this line
  // Complete the method below and implement the others similarly
  this.getFullName = function() {
    return "";
  };
  return firstAndLast;
  // Only change code above this line
};

var bob = new Person('Bob Ross');
bob.getFullName();

Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/intermediate-algorithm-scripting/make-a-person
Tell us about your browser and operating system:

Browser Name: Firefox
Browser Version: 76.0.1 (64-bit)
Operating System: Linux

If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

Good catch!  Rather than restricting what the user can do with bob, what do you think about adding the following code before the tests are run:
if (bob) {
  bob = new Person("Bob Ross");
}

That way they can mess around with the object in their own tests, but it should be ready for the challenge tests.

Agreed, I like this better.
Credit goes to ieahleen on the forums for catching this, I just whipped up the reproducer.

Thanks to @Ieahleen, too then!
I think this should not be too hard to fix, so I'll pop the label on it.


[AutoRelease] t2-network-2022-10-26-16313(Do not merge)

https://github.com/Azure/sdk-release-request/issues/2985
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1031
BuildTargetingString
azure-mgmt-network
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/2985


Prepare for CCM namespace cleanup

Based on #119

Tests passing here means compatible with "older" CCM versions

@jrha ideally this PR also makes in 1.50 release of the build tools

#119 is now merged so needs a rebase?


Add s3a schema

Codecov Report

Merging #80 (cee39c4) into develop (7a51cc4) will decrease coverage by 16.91%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##           develop      #80       +/-   ##
============================================
- Coverage    61.36%   44.45%   -16.92%
============================================
  Files           54       52        -2
  Lines        16966    14438     -2528
============================================
- Hits         10412     6418     -3994
- Misses        6554     8020     +1466

Impacted Files
Coverage Δ

core/src/misc/utils.cc
32.85% <100.00%> (-37.34%)
:arrow_down:

core/include/misc/utils.h
0.00% <0.00%> (-100.00%)
:arrow_down:

core/include/codec/codec_lz4.h
0.00% <0.00%> (-100.00%)
:arrow_down:

core/src/misc/progress_bar.cc
0.00% <0.00%> (-96.78%)
:arrow_down:

core/src/codec/codec_lz4.cc
4.16% <0.00%> (-85.12%)
:arrow_down:

core/src/storage_manager/storage_gcs.cc
1.81% <0.00%> (-75.61%)
:arrow_down:

core/src/storage_manager/storage_azure_blob.cc
0.40% <0.00%> (-74.18%)
:arrow_down:

core/src/codec/codec_filter.cc
28.57% <0.00%> (-71.43%)
:arrow_down:

core/include/storage_manager/storage_buffer.h
0.00% <0.00%> (-71.43%)
:arrow_down:

core/include/storage_manager/storage_azure_blob.h
0.00% <0.00%> (-71.12%)
:arrow_down:

... and 37 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7a51cc4...cee39c4. Read the comment docs.

Codecov Report

Merging #80 (cee39c4) into develop (7a51cc4) will decrease coverage by 16.91%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##           develop      #80       +/-   ##
============================================
- Coverage    61.36%   44.45%   -16.92%
============================================
  Files           54       52        -2
  Lines        16966    14438     -2528
============================================
- Hits         10412     6418     -3994
- Misses        6554     8020     +1466

Impacted Files
Coverage Δ

core/src/misc/utils.cc
32.85% <100.00%> (-37.34%)
:arrow_down:

core/include/misc/utils.h
0.00% <0.00%> (-100.00%)
:arrow_down:

core/include/codec/codec_lz4.h
0.00% <0.00%> (-100.00%)
:arrow_down:

core/src/misc/progress_bar.cc
0.00% <0.00%> (-96.78%)
:arrow_down:

core/src/codec/codec_lz4.cc
4.16% <0.00%> (-85.12%)
:arrow_down:

core/src/storage_manager/storage_gcs.cc
1.81% <0.00%> (-75.61%)
:arrow_down:

core/src/storage_manager/storage_azure_blob.cc
0.40% <0.00%> (-74.18%)
:arrow_down:

core/src/codec/codec_filter.cc
28.57% <0.00%> (-71.43%)
:arrow_down:

core/include/storage_manager/storage_buffer.h
0.00% <0.00%> (-71.43%)
:arrow_down:

core/include/storage_manager/storage_azure_blob.h
0.00% <0.00%> (-71.12%)
:arrow_down:

... and 37 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7a51cc4...cee39c4. Read the comment docs.