This type of issue comes when you use **https** instead of **http**. Change the URL to use **http**.

Example: `https://localhost:3000/posts`

Change it to: `http://localhost:3000/posts`

This error comes when the API that we are hitting is running on http and we are trying using https. Information was really useful.

Example: 
Using this https://localhost:8092/customers, when this http://localhost:8092/customers, must be used as API is running on http.

I encountered this error while trying to test the api request on postman. Ensure the the url link specified during the development process is the same url link been used during testing of postman.

example: during development, the url link specified is http://______. Then, during testing on postman make sure that the link is the same http://_____.

API requests from Http:// and Https:// are treated and handled differently.



There is another case when the questioner&#39;s error message appears, and that is when you are sending a https request to a site whose SSL certificate has expired.

In such a case, I think all you can do is make the owner of the endpoint aware, and hope they fix it.


I ran into this while debugging [this question](https://stackoverflow.com/questions/65638680/using-boost-strong-typedef-to-differentiate-arg-types-but-causing-seg-fault/65643014?noredirect=1#comment116069484_65643014).

I trimmed it down all the way to just using [Boost Operators](https://www.boost.org/doc/libs/1_75_0/libs/utility/operators.htm):

 1. **Compiler Explorer [C++17](https://godbolt.org/z/q89brM) [C++20](https://godbolt.org/z/szYx9E)**
    
        #include &lt;boost/operators.hpp&gt;
        
        struct F : boost::totally_ordered1&lt;F, boost::totally_ordered2&lt;F, int&gt;&gt; {
            /*implicit*/ F(int t_) : t(t_) {}
            bool operator==(F const&amp; o) const { return t == o.t; }
            bool operator&lt; (F const&amp; o) const { return t &lt;  o.t; }
          private: int t;
        };
        
        int main() {
            #pragma GCC diagnostic ignored &quot;-Wunused&quot;
            F { 42 } == F{ 42 }; // OKAY
            42 == F{42};         // C++17 OK, C++20 infinite recursion
            F { 42 } == 42;      // C++17 OK, C++20 infinite recursion
        }
    
    This program compiles and runs fine with C++17 (ubsan/asan enabled) in both GCC and Clang.
    
 1. When you change the _implicit_ constructor to `explicit`, the problematic lines obviously **[no longer compile on C++17](https://godbolt.org/z/hq4fve)**

Surprisingly both versions **compile on C++20 ([v1](https://godbolt.org/z/onMzo5) and [v2](https://godbolt.org/z/b1Pav5))**, but they lead to **infinite recursion** (crash or tight loop, depending on optimization level) on the two lines that wouldn&#39;t compile on C++17.

Obviously this kind of silent bug creeping in by upgrading to C++20 is worrisome.

Questions:

 - Is this c++20 behaviour conformant (I expect so)
 - What exactly is interfering? I suspect it might be due to c++20&#39;s new &quot;spaceship operator&quot; support, but don&#39;t understand **how** it changes the behaviour of this code.



C++20 behaviour breaking existing code with equality operator?

I&#39;m trying to evaluate `((x == a and y == b) or (x == b and y == a))` in Python, but it seems a bit verbose. Is there a more elegant way?

Is there a more elegant way to express ((x == a and y == b) or (x == b and y == a))?

The issue was that I was trying to POST to https when that API actually only supports HTTP.
Just leave this as a note for other folks who might run into the same issue.

Any Help can be appreciated

Error: write EPROTO 34557064:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:

<p>The issue was that I was trying to POST to https when that API actually only supports HTTP.
Just leave this as a note for other folks who might run into the same issue.</p>
<p>Any Help can be appreciated</p>


# Preface

**This issue seems to only affect Chrome/V8, and may not be reproducible in Firefox or other browsers**. In summary, the execution time of a function callback increases by an order of magnitude or more if the function is called with a new callback anywhere else. 

## Simplified Proof-of-Concept

Calling `test(callback)` arbitrarily many times works as expected, but once you call `test(differentCallback)`, the execution time of the `test` function increases dramatically no matter what callback is provided (i.e., another call to `test(callback)` would suffer as well). 

**This example was updated to use arguments so as to not be optimized to an empty loop. Callback arguments `a` and `b` are summed and added to `total`, which is logged.** 

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    function test(callback) {
        let start = performance.now(),
            total = 0;

        // add callback result to total
        for (let i = 0; i &lt; 1e6; i++)
            total += callback(i, i + 1);

        console.log(`took ${(performance.now() - start).toFixed(2)}ms | total: ${total}`);
    }

    let callback1 = (a, b) =&gt; a + b,
        callback2 = (a, b) =&gt; a + b;

    console.log(&#39;FIRST CALLBACK: FASTER&#39;);
    for (let i = 1; i &lt; 10; i++)
        test(callback1);

    console.log(&#39;\nNEW CALLBACK: SLOWER&#39;);
    for (let i = 1; i &lt; 10; i++)
        test(callback2);

&lt;!-- end snippet --&gt;

---

## Original post

I am developing a `StateMachine` class ([source][1]) for a library I&#39;m writing and the logic works as expected, but in profiling it, I&#39;ve run into an issue. I noticed that when I ran the profiling snippet (in global scope), it would only take about 8ms to finish, but if I ran it a second time, it would take up to 50ms and eventually balloon as high as 400ms. Typically, running the same named function over and over will cause its execution time to *drop* as the V8 engine optimizes it, but the opposite seems to be happening here. 

I&#39;ve been able to get rid of the problem by wrapping it in a closure, but then I noticed another weird side effect: Calling a different function that relies on the `StateMachine` class would break the performance for all code depending on the class. 

The class is pretty simple - you give it an initial state in the constructor or `init`, and you can update the state with the `update` method, which you pass a callback that accepts `this.state` as an argument (and usually modifies it). `transition` is a method that is used to `update` the state until the `transitionCondition` is no longer met.

Two test functions are provided: `red` and `blue`, **which are identical**, and each will generate a `StateMachine` with an initial state of `{ test: 0 }` and use the `transition` method to `update` the state while `state.test &lt; 1e6`. The end state is `{ test: 1000000 }`.

You can trigger the profile by clicking the red or blue button, which will run `StateMachine.transition` 50 times and log the average time the call took to complete. If you click the red or blue button repeatedly, you will see that it clocks in at less than 10ms without issue - *but*, once you click the *other* button and call the other version of the same function, everything breaks, and the execution time for both functions will increase by about an order of magnitude. 

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    // two identical functions, red() and blue()

    function red() {
      let start = performance.now(),
          stateMachine = new StateMachine({
            test: 0
          });

      stateMachine.transition(
        state =&gt; state.test++, 
        state =&gt; state.test &lt; 1e6
      );

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      else return performance.now() - start;
    }

    function blue() {
      let start = performance.now(),
          stateMachine = new StateMachine({
            test: 0
          });

      stateMachine.transition(
        state =&gt; state.test++, 
        state =&gt; state.test &lt; 1e6
      );

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      else return performance.now() - start;
    }

    // display execution time
    const display = (time) =&gt; document.getElementById(&#39;results&#39;).textContent = `Avg: ${time.toFixed(2)}ms`;

    // handy dandy Array.avg()
    Array.prototype.avg = function() {
      return this.reduce((a,b) =&gt; a+b) / this.length;
    }

    // bindings
    document.getElementById(&#39;red&#39;).addEventListener(&#39;click&#39;, () =&gt; {
      const times = [];
      for (var i = 0; i &lt; 50; i++)
        times.push(red());
        
      display(times.avg());
    }),

    document.getElementById(&#39;blue&#39;).addEventListener(&#39;click&#39;, () =&gt; {
      const times = [];
      for (var i = 0; i &lt; 50; i++)
        times.push(blue());
        
      display(times.avg());
    });

&lt;!-- language: lang-html --&gt;

    &lt;script src=&quot;https://cdn.jsdelivr.net/gh/TeleworkInc/state-machine@bd486a339dca1b3ad3157df20e832ec23c6eb00b/StateMachine.js&quot;&gt;&lt;/script&gt;

    &lt;h2 id=&quot;results&quot;&gt;Waiting...&lt;/h2&gt;
    &lt;button id=&quot;red&quot;&gt;Red Pill&lt;/button&gt;
    &lt;button id=&quot;blue&quot;&gt;Blue Pill&lt;/button&gt;

    &lt;style&gt;
    body{box-sizing:border-box;padding:0 4rem;text-align:center}button,h2,p{width:100%;margin:auto;text-align:center;font-family:-apple-system,BlinkMacSystemFont,&quot;Segoe UI&quot;,Roboto,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;,&quot;Segoe UI Symbol&quot;}button{font-size:1rem;padding:.5rem;width:180px;margin:1rem 0;border-radius:20px;outline:none;}#red{background:rgba(255,0,0,.24)}#blue{background:rgba(0,0,255,.24)}
    &lt;/style&gt;

&lt;!-- end snippet --&gt;

# Updates
### [&lt;strike&gt;Bug Report&lt;/strike&gt; &quot;Feature Request&quot; filed](https://bugs.chromium.org/p/v8/issues/detail?id=10676) (awaiting update) - See @jmrk&#39;s answers below for more details. 

Ultimately, this behavior is unexpected and, IMO, qualifies as a nontrivial bug. The impact for me is significant - on Intel i7-4770 (8) @ 3.900GHz, my execution times in the example above go from an average of 2ms to 45ms (a 20x increase).

As for nontriviality, consider that any *subsequent* calls to `StateMachine.transition`  after the first one will be unnecessarily slow, regardless of scope or location in the code. The fact that SpiderMonkey does not slow down subsequent calls to `transition` signals to me that there is room for improvement for this specific optimization logic in V8.

See below, where subsequent calls to `StateMachine.transition` are slowed:

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    // same source, several times

    // 1
    (function() {
      let start = performance.now(),
        stateMachine = new StateMachine({
          test: 0
        });

      stateMachine.transition(state =&gt; state.test++, state =&gt; state.test &lt; 1e6);

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      console.log(`took ${performance.now() - start}ms`);
    })();


    // 2 
    (function() {
      let start = performance.now(),
        stateMachine = new StateMachine({
          test: 0
        });

      stateMachine.transition(state =&gt; state.test++, state =&gt; state.test &lt; 1e6);

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      console.log(`took ${performance.now() - start}ms`);
    })();

    // 3
    (function() {
      let start = performance.now(),
        stateMachine = new StateMachine({
          test: 0
        });

      stateMachine.transition(state =&gt; state.test++, state =&gt; state.test &lt; 1e6);

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      console.log(`took ${performance.now() - start}ms`);
    })();

&lt;!-- language: lang-html --&gt;

    &lt;script src=&quot;https://cdn.jsdelivr.net/gh/TeleworkInc/state-machine@bd486a339dca1b3ad3157df20e832ec23c6eb00b/StateMachine.js&quot;&gt;&lt;/script&gt;

&lt;!-- end snippet --&gt;

This performance decrease can be avoided by wrapping the code in a *named* closure, where presumably the optimizer knows the callbacks will not change:

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    var test = (function() {
        let start = performance.now(),
            stateMachine = new StateMachine({
                test: 0
            });
      
        stateMachine.transition(state =&gt; state.test++, state =&gt; state.test &lt; 1e6);
      
        if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
        console.log(`took ${performance.now() - start}ms`);
    });

    test();
    test();
    test();

&lt;!-- language: lang-html --&gt;

    &lt;script src=&quot;https://cdn.jsdelivr.net/gh/TeleworkInc/state-machine@bd486a339dca1b3ad3157df20e832ec23c6eb00b/StateMachine.js&quot;&gt;&lt;/script&gt;

&lt;!-- end snippet --&gt;

&lt;h1&gt;Platform Information&lt;/h1&gt;

```none
$ uname -a
Linux workspaces 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$ google-chrome --version
Google Chrome 83.0.4103.116
```


  [1]: https://cdn.jsdelivr.net/gh/TeleworkInc/StateMachine.js@bd486a339dca1b3ad3157df20e832ec23c6eb00b/StateMachine.js
  [2]: https://bugs.chromium.org/p/v8/issues/detail?id=10676

Why is the execution time of this function call changing?

Here is my simple graphql express app

    const express = require(&#39;express&#39;);
    const graphqlHTTP = require(&#39;express-graphql&#39;);
    
    const app = express();
    app.use(
        &#39;/graphql&#39;,
        graphqlHTTP({
          graphiql: true,
        })
      );
    
    app.listen(4000, () =&gt; {
        console.log(&quot;listening for request!&quot;);
    });

I&#39;m getting the following errors when I run it:

     graphqlHTTP({
        ^
    
    TypeError: graphqlHTTP is not a function
        at Object.&lt;anonymous&gt; (D:\PersonalProjects\GraphQL\server\app.js:7:5)
        at Module._compile (internal/modules/cjs/loader.js:1138:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
        at Module.load (internal/modules/cjs/loader.js:986:32)
        at Function.Module._load (internal/modules/cjs/loader.js:879:14)
        at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)  
        at internal/main/run_main_module.js:17:47

How can I fix it? Thanks in advance!

graphqlHTTP is not a function

The documentation page: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replaceAll

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    let string = &quot;:insertx: :insertx: :inserty: :inserty: :insertz: :insertz:&quot;;
    let newstring = string.replaceAll(&quot;:insertx:&quot;, &#39;hello!&#39;);

&lt;!-- end snippet --&gt;

When I run this, I receive `Uncaught TypeError: string.replaceAll is not a function`. Maybe I&#39;m misunderstanding what a prototype is, but the function appears to be a string method that is available for use.

I&#39;m using Chrome.

Javascript .replaceAll() is not a function type error


I&#39;m trying to run very simple code, but I&#39;m getting an error, I didn&#39;t use the create react app!

It looks like my babel.config.js file is being ignored!

This is the structure of my small project:
[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/XovUB.png

My html file

    &lt;!DOCTYPE html&gt;
    &lt;html lang=&quot;en&quot;&gt;
    
    &lt;head&gt;
        &lt;meta charset=&quot;UTF-8&quot;&gt;
        &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1.0&quot;&gt;
        &lt;title&gt;ReactJS&lt;/title&gt;
    &lt;/head&gt;
    
    &lt;body&gt;
        &lt;div id=&quot;app&quot;&gt;&lt;/div&gt;
        &lt;script  src = &#39;bundle.js&#39; &gt;&lt;/script&gt;
    &lt;/body&gt; 
    
    &lt;/html&gt;

My index.js file:

    import React from &#39;react&#39;;
    import { render } from &#39;react-dom&#39;;
    
    render(&lt;h1&gt;Hello World!!&lt;/h1&gt;, document.getElementById(&#39;app&#39;)); 

My package json:

    {
      &quot;name&quot;: &quot;front&quot;,
      &quot;version&quot;: &quot;1.0.0&quot;,
      &quot;main&quot;: &quot;index.js&quot;,
      &quot;license&quot;: &quot;MIT&quot;,
      &quot;scripts&quot;: {
        &quot;dev&quot;: &quot;webpack-dev-server --mode development&quot;,
        &quot;build&quot;: &quot;webpack-dev-server --mode production&quot;
      },
      &quot;dependencies&quot;: {
        &quot;@babel/cli&quot;: &quot;^7.10.5&quot;,
        &quot;@babel/core&quot;: &quot;^7.10.5&quot;,
        &quot;@babel/plugin-proposal-class-properties&quot;: &quot;^7.10.4&quot;,
        &quot;@babel/preset-env&quot;: &quot;^7.10.4&quot;,
        &quot;@babel/preset-react&quot;: &quot;^7.10.4&quot;,
        &quot;react&quot;: &quot;^16.13.1&quot;,
        &quot;react-dom&quot;: &quot;^16.13.1&quot;,
        &quot;webpack&quot;: &quot;^4.43.0&quot;,
        &quot;webpack-cli&quot;: &quot;^3.3.12&quot;,
        &quot;webpack-dev-server&quot;: &quot;^3.11.0&quot;
      },
      &quot;devDependencies&quot;: {
        &quot;@babel/plugin-transform-runtime&quot;: &quot;^7.9.0&quot;,
        &quot;babel-loader&quot;: &quot;^8.1.0&quot;,
        &quot;webpack-dev-server&quot;: &quot;^3.10.3&quot;
      }
    }

My webpack.config.js

    const path = require(&#39;path&#39;);
    
    module.exports = {
        entry: path.resolve(__dirname, &#39;src&#39;, &#39;index.js&#39;),
        output: {
            path: path.resolve(__dirname, &#39;public&#39;),
            filename: &#39;bundle.js&#39;
        },
        devServer: {
            contentBase: path.resolve(__dirname, &#39;public&#39;),
        },
        module: {
            rules: [{
                test: /\.js$/,
                exclude: /node_modules/,
                use: {
                    loader: &#39;babel-loader&#39;,
                }
            }]
        },
    };

And this is my babel.config.js

    module.exports = {
        &quot;presets&quot;: [&quot;@babel/preset-env&quot;, &quot;@babel/preset-react&quot;]
    
    };

Error when

    yarn webpack-dev-server --mode development

    ERROR in ./src/index.js
    Module build failed (from ./node_modules/babel-loader/lib/index.js):
    SyntaxError: /root/treina/front/src/index.js: Support for the experimental syntax &#39;jsx&#39; isn&#39;t currently enabled (4:8):
    
      2 | import { render } from &#39;react-dom&#39;;
      3 | 
    &gt; 4 | render(&lt;h1&gt;Hello World!!&lt;/h1&gt;, document.getElementById(&#39;app&#39;));
        |        ^
    
    Add @babel/preset-react (https://git.io/JfeDR) to the &#39;presets&#39; section of your Babel config to enable transformation.
    If you want to leave it as-is, add @babel/plugin-syntax-jsx (https://git.io/vb4yA) to the &#39;plugins&#39; section to enable parsing.
        at Parser._raise (/root/treina/front/node_modules/@babel/parser/lib/index.js:757:17)
        at Parser.raiseWithData (/root/treina/front/node_modules/@babel/parser/lib/index.js:750:17)
        at Parser.expectOnePlugin (/root/treina/front/node_modules/@babel/parser/lib/index.js:8849:18)
        at Parser.parseExprAtom (/root/treina/front/node_modules/@babel/parser/lib/index.js:10170:22)
        at Parser.parseExprSubscripts (/root/treina/front/node_modules/@babel/parser/lib/index.js:9688:23)
        at Parser.parseMaybeUnary (/root/treina/front/node_modules/@babel/parser/lib/index.js:9668:21)
        at Parser.parseExprOps (/root/treina/front/node_modules/@babel/parser/lib/index.js:9538:23)
        at Parser.parseMaybeConditional (/root/treina/front/node_modules/@babel/parser/lib/index.js:9511:23)
        at Parser.parseMaybeAssign (/root/treina/front/node_modules/@babel/parser/lib/index.js:9466:21)
        at Parser.parseExprListItem (/root/treina/front/node_modules/@babel/parser/lib/index.js:10846:18)
    ℹ ｢wdm｣: Failed to compile.



I&#39;m using yarn and the WSL terminal

Support for the experimental syntax &#39;jsx&#39; isn&#39;t currently enabled

When I call this promise, the output does not match with the sequence of function calls. The `.then` comes before the `.catch`, even though the promise with `.then` was being called after. What is the reason for that?

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    const verifier = (a, b) =&gt;
      new Promise((resolve, reject) =&gt; (a &gt; b ? resolve(true) : reject(false)));

    verifier(3, 4)
      .then((response) =&gt; console.log(&quot;response: &quot;, response))
      .catch((error) =&gt; console.log(&quot;error: &quot;, error));

    verifier(5, 4)
      .then((response) =&gt; console.log(&quot;response: &quot;, response))
      .catch((error) =&gt; console.log(&quot;error: &quot;, error));

&lt;!-- end snippet --&gt;

output
```
node promises.js
response: true
error: false
```

Javascript Promises curiosity

In my typescript project, I am using eslint. The files below are in the root, and I have also subfolders `/dist` and `/src`.

eslintrc.js

```js
module.exports = {
  root: true,
  parser: &#39;@typescript-eslint/parser&#39;,
  parserOptions: {
    tsconfigRootDir: __dirname,
    project: [&#39;./tsconfig.json&#39;],
  },
  rules: {
    strict: &#39;error&#39;,
    semi: [&#39;error&#39;, &#39;always&#39;],
    &#39;no-cond-assign&#39;: [&#39;error&#39;, &#39;always&#39;],
  },
  plugins: [&#39;@typescript-eslint&#39;],
  extends: [
    &#39;eslint:recommended&#39;,
    &#39;plugin:@typescript-eslint/recommended&#39;,
    &#39;plugin:@typescript-eslint/recommended-requiring-type-checking&#39;,
  ],
}
```

tsconfig.json

```json
{
  &quot;compilerOptions&quot;: {
    &quot;outDir&quot;: &quot;dist&quot;,
    &quot;noImplicitAny&quot;: true,
    &quot;moduleResolution&quot;: &quot;Node&quot;,
    &quot;resolveJsonModule&quot;: true,
    &quot;module&quot;: &quot;ES2020&quot;,
    &quot;target&quot;: &quot;ES2020&quot;,
    &quot;lib&quot;: [&quot;ES2020&quot;],
    &quot;allowJs&quot;: false,
    &quot;alwaysStrict&quot;: true
  },
  &quot;include&quot;: [&quot;src&quot;]
}
```

the word `module` on top has a red line with this error

```
Parsing error: &quot;parserOptions.project&quot; has been set for @typescript-eslint/parser.
The file does not match your project config: .eslintrc.js.
The file must be included in at least one of the projects provided. eslint
```

How can I fix this?


How to fix eslintrc The file does not match your project config?

Can see it&#39;s been asked a dozen times but none of the solutions I&#39;ve found have worked for me so far. 

I&#39;ve installed the latest version of Node.js (12.18.3) on my Windows 10 PC and I&#39;m trying to install a package using npm. When I input `npm -v` it comes back with 5.6.0, which to me looks out of date - but when I try and install a package or update npm, I get the following error every time:

    npm WARN npm npm does not support Node.js v12.18.3
    npm WARN npm You should probably upgrade to a newer version of node as we
    npm WARN npm can&#39;t make any promises that npm will work with this version.
    npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
    npm WARN npm You can find the latest version at https://nodejs.org/
    npm ERR! cb.apply is not a function

    npm ERR! A complete log of this run can be found in:

I&#39;ve tried uninstalling Node.js completely, deleting all node_modules folders and restarting my computer after a fresh install, but it&#39;s the same thing each time. I&#39;ve also tried using `npm install -g npm` and `npm install npm@latest -g` but again, I get the same error.

Any solutions here? 

npm does not support Node.js v12.18.3

Error on terminal: `nodemon.ps1` cannot be loaded because running scripts is disabled on this system. For more 
information, see **about_Execution_Policies** at 
[https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.2][1]

I have a solution to fix the issue by this way:  

`1. Open Windows PowerShell with Run as Administrator`  
`2. Run this command: Set-ExecutionPolicy Unrestricted`


That solves the issue, but this way the system shows Security Risk Warning.  
My question: Is there any other way to solve this without security risk? Target is to use `nodemon`.


  [1]: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.2

How to fix error- nodemon.ps1 cannot be loaded because running scripts is disabled on this system, (without security risk)?

I am trying to do the ```docker-compose up``` command in my terminal. First I navigate to the file directory where I find a docker-compose.yaml. Then I write the command. The Server is on Port 80. I get the following error:

```
Traceback (most recent call last):
      File &quot;site-packages/docker/api/client.py&quot;, line 205, in _retrieve_server_version
      File &quot;site-packages/docker/api/daemon.py&quot;, line 181, in version
      File &quot;site-packages/docker/utils/decorators.py&quot;, line 46, in inner
      File &quot;site-packages/docker/api/client.py&quot;, line 228, in _get
      File &quot;site-packages/requests/sessions.py&quot;, line 543, in get
      File &quot;site-packages/requests/sessions.py&quot;, line 530, in request
      File &quot;site-packages/requests/sessions.py&quot;, line 643, in send
      File &quot;site-packages/requests/adapters.py&quot;, line 498, in send
    requests.exceptions.ConnectionError: (&#39;Connection aborted.&#39;, ConnectionRefusedError(61, &#39;Connection refused&#39;))
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File &quot;docker-compose&quot;, line 3, in &lt;module&gt;
      File &quot;compose/cli/main.py&quot;, line 67, in main
      File &quot;compose/cli/main.py&quot;, line 123, in perform_command
      File &quot;compose/cli/command.py&quot;, line 69, in project_from_options
      File &quot;compose/cli/command.py&quot;, line 132, in get_project
      File &quot;compose/cli/docker_client.py&quot;, line 43, in get_client
      File &quot;compose/cli/docker_client.py&quot;, line 170, in docker_client
      File &quot;site-packages/docker/api/client.py&quot;, line 188, in __init__
      File &quot;site-packages/docker/api/client.py&quot;, line 213, in _retrieve_server_version
    docker.errors.DockerException: Error while fetching server API version: (&#39;Connection aborted.&#39;, ConnectionRefusedError(61, &#39;Connection refused&#39;))
    [12728] Failed to execute script docker-compose
```


The first error shows up two times then the second.

Docker-compose up : Error while fetching server API version: (&#39;Connection aborted.&#39;, ConnectionRefusedError(61, &#39;Connection refused&#39;))

It seems like CORS error is well-known issue in the web field. But I tried flutter web for the first time ever and I faced critical error.

The code below worked well in app version when it was running on iOS device, but when i tested the same code on Chrome with web debugging from beta channel, it encountered CORS error.

Other stackoverflow answers explained how to solve the CORS issue with serverside files of their projects. But I have totally no idea what is server thing and how to deal with their answers. The error message from Chrome console was below

[  Access to XMLHttpRequest at &#39;https://kapi.kakao.com/v1/payment/ready&#39; from origin &#39;http://localhost:52700&#39; has been blocked by CORS policy: Response to preflight request doesn&#39;t pass access control check: No &#39;Access-Control-Allow-Origin&#39; header is present on the requested resource.  ]

So, what i want to do is to solve above &#39;Access-Control-Allow-Origin header&#39; issue ONLY WITH DART CODE! Code below is what i&#39;ve tried to solve these issues only with my main.dart.


    onPressed: () async {
          var res =
              await http.post(&#39;https://kapi.kakao.com/v1/payment/ready&#39;, encoding: Encoding.getByName(&#39;utf8&#39;), headers: {
            &#39;Authorization&#39;: &#39;KakaoAK $_ADMIN_KEY&#39;,
            HttpHeaders.authorizationHeader: &#39;KakaoAK $_ADMIN_KEY&#39;,
            &quot;Access-Control-Allow-Origin&quot;: &quot;*&quot;,
            &quot;Access-Control-Allow-Methods&quot;: &quot;POST, GET, OPTIONS, PUT, DELETE, HEAD&quot;,
          }, body: {
            &#39;cid&#39;: &#39;TC0ONETIME&#39;,
            &#39;partner_order_id&#39;: &#39;partner_order_id&#39;,
            &#39;partner_user_id&#39;: &#39;partner_user_id&#39;,
            &#39;item_name&#39;: &#39;cool_beer&#39;,
            &#39;quantity&#39;: &#39;1&#39;,
            &#39;total_amount&#39;: &#39;22222&#39;,
            &#39;vat_amount&#39;: &#39;2222&#39;,
            &#39;tax_free_amount&#39;: &#39;0&#39;,
            &#39;approval_url&#39;: &#39;$_URL/kakaopayment&#39;,
            &#39;fail_url&#39;: &#39;$_URL/kakaopayment&#39;,
            &#39;cancel_url&#39;: &#39;$_URL/kakaopayment&#39;
          });
          Map&lt;String, dynamic&gt; result = json.decode(res.body);
          print(result);
        },


Even though i actually had the header `&quot;Access-Control-Allow-Origin&quot;: &quot;*&quot;` which most other answers recommended, the Chrome console printed same error message. Weird thing is that the same code made successful request in mobileApp version. So I think this is only problem with flutter WEB VERSION.

Hope somebody can figure it out and suggest only-dart code to resolve the issue in my main.dart!! Thank you for reading [:

How to solve flutter web api cors error only with dart code?

I&#39;m doing API with the node and using Mongoose. When I give a `yarn dev` to start my Nodemon, there is an error in Mongo, I have no idea how to solve this. Would anyone have any ideas? (I&#39;m using the MongoDB Atlas database)

Right after the following error.

    yarn run v1.22.5
    $ nodemon src/server.js
    [nodemon] 2.0.7
    [nodemon] to restart at any time, enter `rs`
    [nodemon] watching path(s): *.*
    [nodemon] watching extensions: js,mjs,json
    [nodemon] starting `node src/server.js`
    (node:752) Warning: Accessing non-existent property &#39;MongoError&#39; of module exports inside circular dependency
    (Use `node --trace-warnings ...` to show where the warning was created)
    (node:752) DeprecationWarning: Listening to events on the Db class has been deprecated and will be removed in the next major version.


I&#39;m using the

- Node v14.15.4
- npm 6.14.10

My package.json

    {
      &quot;name&quot;: &quot;backend&quot;,
      &quot;version&quot;: &quot;1.0.0&quot;,
      &quot;main&quot;: &quot;index.js&quot;,
      &quot;license&quot;: &quot;MIT&quot;,
      &quot;scripts&quot;: {
        &quot;dev&quot;: &quot;nodemon src/server.js&quot;
      },
      &quot;dependencies&quot;: {
        &quot;express&quot;: &quot;^4.17.1&quot;,
        &quot;md5&quot;: &quot;^2.3.0&quot;,
        &quot;mongoose&quot;: &quot;^5.11.16&quot;,
        &quot;multer&quot;: &quot;^1.4.2&quot;,
        &quot;yarn&quot;: &quot;^1.22.10&quot;
      },
      &quot;devDependencies&quot;: {
        &quot;nodemon&quot;: &quot;^2.0.7&quot;
      }
    }



Content Type	Original Author	Original Content on Stackoverflow
Question	Ayeen M Khan	View Question on Stackoverflow
Solution 1 - Javascript	Kranthi Kumar	View Answer on Stackoverflow
Solution 2 - Javascript	Sharad	View Answer on Stackoverflow
Solution 3 - Javascript	E.Anthony	View Answer on Stackoverflow
Solution 4 - Javascript	Breandán Dalton	View Answer on Stackoverflow

Error: write EPROTO 34557064:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:

Javascript Problem Overview

Javascript Solutions

Solution 1 - Javascript

Solution 2 - Javascript

Solution 3 - Javascript

Solution 4 - Javascript

Is there a more elegant way to express ((x == a and y == b) or (x == b and y == a))?

C++20 behaviour breaking existing code with equality operator?

Attributions