Configure max message size received by mcp client

This allows us to configure the maximum message size that MCP's underlying grpc client can receive. We discovered the following errors during our scaling tests
Error receiving MCP response: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4623689 vs. 4194304)

This change allows MCP client in pilot to receive bigger payloads from the MCP server, if no value provided the default underlying grpc maxMessageSize is taken into account.

@Nino-K: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test e2e-mixer-no_auth-mcp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-mixer-no_auth-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
2ff3216765971fccbcd3cde0420cf2cf8d7b3c6c
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-multicluster-e2e.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
2ff3216765971fccbcd3cde0420cf2cf8d7b3c6c
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
2ff3216765971fccbcd3cde0420cf2cf8d7b3c6c
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
d00374c6241570d8ebf35db02927c6aa1e4318f1
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
2ff3216765971fccbcd3cde0420cf2cf8d7b3c6c
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
2ff3216765971fccbcd3cde0420cf2cf8d7b3c6c
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
2ff3216765971fccbcd3cde0420cf2cf8d7b3c6c
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: nmittler
If they are not already assigned, you can assign the PR to them by writing /assign @nmittler in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [rshriram]
tests/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add new attributes to add ic functionality to existing link

The 'ic-get-from', 'ic-post-to', 'ic-put-to', 'ic-patch-to' and 'ic-delete-from' attributes all require a url parameter. This is fine if you're coding up your own HTML, but in some instances you don't have control over the links that get generated by some packages, such as pagination gems.
For example, a pagination gem such as Kaminari or Will Paginate spits out a bunch of pagination links, so if you're using Intercooler to request the pages, you end up having to hack the pagination generators to put in the correct 'ic-get-from' attributes.
I've coded up a fairly neat solution to this problem which adds the following attributes - 'ic-get', 'ic-post', 'ic-put' and 'ic-delete'. They all work in exactly the same way as the corresponding attributes in the current code, except that they take the url from the href attribute in the link, instead of as a parameter. This means that you can just add the attribute 'ic-get="true"' to an existing link and get the same result as if you'd built the link with the 'ic-get-from' attribute.
This makes it very easy to create Intercooler links from generated pagination links, for example, without needing to modify any of the generating code, as long as it allows you to provide custom attributes for the link.
If anyone thinks this is a worthwhile addition, then I can code up some test cases and submit a pull request.

Hi There,
Have you seen the "ic-enhance" attribute?  It might cover some of these use cases:
http://intercoolerjs.org/attributes/ic-enhance.html

Sorry. I missed the significance of that attribute.
Yes, it does exactly what I need for this issue. I just didn't connect the two together.

Ah, sorry about that.  I wonder if improving the docs would help.
It is a newer feature and a bit more magic than the usual stuff.  :man_shrugging:

For me, I didn't connect the purpose of the 'ic-enhance' to anything in particular. The documentation might be improved by adding some reasons why you would want to use this feature. The pagination generators example is a pretty good use case.


Cleos returning error when using any vector on a table (cdt 1.4.1)

I want to store a vector in my table and I'm aware of the breaking changes eos.cdt 1.3 introduced to std::vector, so I'm now importing the vector library and I am directly using std::vector, as suggested in #133.
#include <eosiolib/eosio.hpp>
#include <vector>

using namespace eosio;

class [[eosio::contract]] hello : public eosio::contract {

public:
  using contract::contract;

  hello(name receiver, name code,  datastream<const char*> ds): contract(receiver, code, ds) {}

  [[eosio::action]]
  void upsert(name user, std::string first_name, std::string last_name, std::string street, std::string city, std::string state) {
    require_auth( user );
    address_index addresses(_code, _code.value);
    auto iterator = addresses.find(user.value);
    if( iterator == addresses.end() )
    {
      addresses.emplace(user, [&]( auto& row ) {
       row.key = user;
       row.first_name = first_name;
       row.last_name = last_name;
       row.street = street;
       row.city = city;
       row.state = state;
      });
    }
    else {
      std::string changes;
      addresses.modify(iterator, user, [&]( auto& row ) {
        row.key = user;
        row.first_name = first_name;
        row.last_name = last_name;
        row.street = street;
        row.city = city;
        row.state = state;
      });
    }
  }
  **[[eosio::action]]
  void testvector(name user, char number) {
    address_index addresses(_self, _code.value);
    auto iterator = addresses.find(user.value);
     addresses.modify(iterator, user, [&]( auto& row ) {
        row.myvector.push_back(number);
      });
  }**
  [[eosio::action]]
  void erase(name user) {
    require_auth(user);
    address_index addresses(_self, _code.value);
    auto iterator = addresses.find(user.value);
    eosio_assert(iterator != addresses.end(), "Record does not exist");
    addresses.erase(iterator);
  }

private:
  struct [[eosio::table]] person {
    name key;
    std::string first_name;
    std::string last_name;
    std::string street;
    std::string city;
    std::string state;
    std::vector<char> myvector;
    uint64_t primary_key() const { return key.value; }
  };
  typedef eosio::multi_index<"people"_n, person> address_index;
};
EOSIO_DISPATCH( hello, (upsert)(erase))

I basically took the example contract from the docs: https://developers.eos.io/eosio-home/docs/data-persistence and added a vector to the person struct and created a testvector action to simply add a number to that vector array.
the contract compiles and is successfully able to modify the vector's content without returning any error(inside the modify lambda).
But cleos get table returns Error 3015013: Unpack data exception, saying:
error 2018-12-22T00:24:04.986 thread-0  http_plugin.cpp:585           handle_exception     ] FC Exception encountered while processing chain.get_table_rows debug 2018-12-22T00:24:04.986 thread-0  http_plugin.cpp:586           handle_exception     ] Exception Details: 3015013 unpack_exception: Unpack data exception Stream unexpectedly ended; unable to unpack field 'myvector' of struct 'person'     {"f":"myvector","p":"person"}     thread-0  abi_serializer.cpp:307 _binary_to_variant
removing the vector from the table makes the rest of the table readable again from cleos. I'm using eosio v1.6.0 rc1.
Please help, this is frustrating, all examples I find using std::vector are for older versions of eoscdt.

Solved. The problem was that you can't change the table definition after deploying the contract for the first time.


Remove version: NetEase.CloudMusic version <IP_ADDRESS>242

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://d1.music.126.net/dmusic/cloudmusicsetup<IP_ADDRESS>242.exe
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 762)


Add handling of oauth2 security definition annotations in PlayReader.

Fix for issue #182

Thanks! included and replaced by #192 which introduces handling of both api key and oauth2 security definition support in play 2.6


ERROR DryRunExecutor :  TypeError: Cannot set properties of undefined (setting 'currentTestId')

Summary
wenn stryker-js is run with config listed below on  this project:
git clone git@github.com:bodote/book-monkey.git
git checkout v0.2

I get this error during DryRunExecution on all tests:
...
08:41:57 (37435) INFO DryRunExecutor Starting initial test run (karma test runner with "perTest" coverage analysis). This may take a while.
08:41:57 (37435) DEBUG DryRunExecutor Using timeout of 300000 ms.
08:41:57 (37435) DEBUG TimeoutDecorator Starting timeout timer (300000 ms) for a test run
08:41:58 (37435) TRACE ChildProcessProxy Chrome Headless 105.0.5195.125 (Mac OS 10.15.7): Executed 0 of 134 SUCCESS (0 secs / 0 secs)

08:41:58 (37435) TRACE ChildProcessProxy Chrome Headless 105.0.5195.125 (Mac OS 10.15.7) FormMessagesComponent should create an array of errormessage that fit to a "title" control  FAILED
	TypeError: Cannot set properties of undefined (setting 'currentTestId')
	    at Object.specStarted (node_modules/@stryker-mutator/karma-runner/dist/src/karma-plugins/test-hooks-middleware-21f23d35-a4c9-4b01-aeff-da9c99c3ffc0.js:5:44)
	    at <Jasmine>
	    at ZoneQueueRunner.jasmine.QueueRunner.ZoneQueueRunner.execute (node_modules/zone.js/fesm2015/zone-testing.js:692:42)
	    at <Jasmine>
Chrome Headless 105.0.5195.125 (Mac OS 10.15.7): Executed 1 of 134 (1 FAILED) (skipped 25) (0 secs / 0.018 secs)

...

Whereas if I replace "src/app/app.component.ts", in the stryker.conf.json by   "src/app/shared/*.ts"
It works without errors.
And althought of cause the ng test for src/app/app.component.ts or for the hole project runs also without any hickups
Stryker config

{
  "$schema"<EMAIL_ADDRESS>  "_comment": "This config was generated using 'stryker init'. Please see the guide for more information: https://stryker-mutator.io/docs/stryker-js/guides/angular",
  "mutate": [
    "src/app/app.component.ts",
    "!src/**/*.spec.ts",
    "!src/test.ts",
    "!src/environments/*.ts",
    "!src/**/*.module.ts",
    "!main.ts",
    "!cypress/**"
  ],
  "testRunner": "karma",
  "karma": {
    "configFile": "karma.conf.js",
    "projectType": "angular-cli",
    "config": {
      "browsers": [
        "ChromeHeadless"
      ]
    }
  },
  "reporters": [
    "progress",
    "clear-text",
    "html"
  ],
  "htmlReporter": { "fileName": "reports/mutation/mutation.app.html" },
  "concurrency": 2,
  "concurrency_comment": "Recommended to use about half of your available cores when running stryker with angular",
  "coverageAnalysis": "perTest",
  "timeoutFactor": 40,
  "checkers": ["typescript"],
  "fileLogLevel": "info",
  "tsconfigFile": "tsconfig.stryker.json",
  "tempDirName": "stryker-tmp",
  "inPlace": true
}

Test runner config

// Karma configuration file, see link for more information
// https://karma-runner.github.io/1.0/config/configuration-file.html

module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine', '@angular-devkit/build-angular'],
    plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
      require('karma-jasmine-html-reporter'),
      require('karma-coverage'),
      require('@angular-devkit/build-angular/plugins/karma')
    ],
    client: {
      jasmine: {
        // you can add configuration options for Jasmine here
        // the possible options are listed at https://jasmine.github.io/api/edge/Configuration.html
        // for example, you can disable the random execution with `random: false`
        // or set a specific seed with `seed: 4321`
      },
      clearContext: false // leave Jasmine Spec Runner output visible in browser
    },
    jasmineHtmlReporter: {
      suppressAll: true // removes the duplicated traces
    },
    coverageReporter: {
      dir: require('path').join(__dirname, './coverage/book-monkey'),
      subdir: '.',
      reporters: [
        { type: 'html' },
        { type: 'text-summary' }
      ]
    },
    reporters: ['progress', 'kjhtml'],
    port: 9876,
    colors: true,
    logLevel: config.LOG_DEBUG,
    autoWatch: true,
    browsers: ['ChromeHeadless'],
    singleRun: false,
    restartOnFileChange: true
  });
};

├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>

├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>

Test runner environment
ng test

karma.conf.json see above
tsconfig.stryker.json:
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./out-tsc/app",
    "types": []
  },
  "include": [
    "src/**/*.ts",
    "src/**/*.d.ts"
  ],
  "exclude": [
    "src/**/*.spec.ts"
  ]
}

Your Environment

software
version(s)

node
v18.10.0

npm
v8.19.2

Operating System
MacOS 12.6

Add stryker.log
see attached
stryker.log

found the reason:
app.component.ts has only a constructor, but no other methods. Nevertheless there is logic in the html-template, so the
app.component.spec.ts indeed contains 2 tests.
As soon as I add any method to app.component.ts, stryker does no longer throw this error

Thanks for opening this issue! Love to have a reproduction repo 😍. I think I know what's going on here.
This was the smoking gun:

Instrumented 1 source file(s) with 0 mutant(s)

So there are 0 mutants. That means the __stryker__ global variable also doesn't get introduced in the source code. The Stryker karma plugin expects the __stryker__ global variable to be there, because it injects this piece of code:
jasmine.getEnv().addReporter({
  specStarted: function (spec) {
    window.__stryker__.currentTestId = spec.id;
  }
});

I think an easy fix is to add this line:
+ window.__stryker__ = window.__stryker__ || {};
  jasmine.getEnv().addReporter({
    specStarted: function (spec) {
      window.__stryker__.currentTestId = spec.id;
    }
  });

As a workaround: As long as there is at least 1 file with 1 mutant, Stryker should work as expected.

For anyone interested in picking this up: https://github.com/stryker-mutator/stryker-js/blob/339a3f248d7a78a66b3b5f6fe170d1926d4d88bc/packages/karma-runner/src/karma-plugins/test-hooks-middleware.ts#L86-L112

I try...

unfortunately the "Integration tests core" show error even before I change something in the code (I forked this project , added git remote add upstream git@github.com:stryker-mutator/stryker-js.git
and run git fetch upstream && git merge upstream/master && git push && npm i to be up to date.)
56 passing (2m)
/Users/bodo.teichmann/dev/learning/myStryker/stryker-js/node_modules/mocha/lib/reporters/base.js:379
  1 failing
/Users/bodo.teichmann/dev/learning/myStryker/stryker-js/node_modules/mocha/lib/reporters/base.js:392
  1) ChildProcessProxy
       should throw an OutOfMemoryError if the process went out-of-memory:

      AssertionError: expected promise to be rejected with 'OutOfMemoryError' but it was rejected with 'Error: Child process [pid 94460] exit…'
      + expected - actual

      -Error: Child process [pid 94460] exited unexpectedly with exit code null (SIGABRT). Last part of stdout and stderr was:
      -	59: 0x1050dc004 v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	60: 0x104ea8b94 node::InternalCallbackScope::Close() [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	61: 0x104ea8fd4 node::InternalMakeCallback(node::Environment*, v8::Local<v8::Object>, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*, node::async_context) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	62: 0x104ec3630 node::AsyncWrap::MakeCallback(v8::Local<v8::Function>, int, v8::Local<v8::Value>*) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	63: 0x1050252bc node::StreamBase::CallJSOnreadMethod(long, v8::Local<v8::ArrayBuffer>, unsigned long, node::StreamBase::StreamBaseJSChecks) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	64: 0x10502553c node::EmitToJSStreamListener::OnStreamRead(long, uv_buf_t const&) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	65: 0x10502b66c node::LibuvStreamWrap::OnUvRead(long, uv_buf_t const*) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	66: 0x10502b35c node::LibuvStreamWrap::ReadStart()::$_1::__invoke(uv_stream_s*, long, uv_buf_t const*) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	67: 0x1075d7004 uv__stream_io [/opt/homebrew/Cellar/libuv/1.44.2/lib/libuv.1.dylib]
      -	68: 0x1075de1e0 uv__io_poll [/opt/homebrew/Cellar/libuv/1.44.2/lib/libuv.1.dylib]
      -	69: 0x1075ce7d0 uv_run [/opt/homebrew/Cellar/libuv/1.44.2/lib/libuv.1.dylib]
      -	70: 0x104ea9878 node::SpinEventLoop(node::Environment*) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	71: 0x104fb37dc node::NodeMainInstance::Run(int*, node::Environment*) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	72: 0x104fb3430 node::NodeMainInstance::Run() [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	73: 0x104f3da10 node::LoadSnapshotDataAndRun(node::SnapshotData const**, node::InitializationResult*) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	74: 0x104f3db00 node::Start(int, char**) [/opt/homebrew/Cellar/node/18.10.0/bin/node]
      -	75: 0x1074e508c
      -
      +OutOfMemoryError
```.
I have MacOS 12.6. with Apple M1 with 16Gbyte RAM

...and the integration tests for the karma-runner also give me an error:
mocha --timeout 18000 --exit "dist/test/integration/**/*.js":
  34 passing (25s)
  1 failing

  1) Infinite loop
       should report a timeout eventually and be able to recover from it:

      AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected

+ 'survived'
- 'timeout'
      + expected - actual

      -survived
      +timeout

      at Module.expectTimeout (file:///Users/bodo.teichmann/dev/learning/myStryker/stryker-js/packages/test-helpers/src/assertions.ts:34:10)
      at Context.<anonymous> (file:///Users/bodo.teichmann/dev/learning/myStryker/stryker-js/packages/karma-runner/test/integration/timeout-on-infinite-loop.it.spec.ts:35:18)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)

but apart from that :
the fix proposed from @nicojs  seems to work.
so I added a line to the unit test to cover this change and  this is the
pull request 3787

Closed with #3787


timestamp is not updated properly

this is tested on Lustre for src and dst. "--preserved" should be enabled in dcmp, but mtime seems to be updated, but last data seems to be still in cache on client and not arrived yet. At the end, mtime seems to re-updated when last data arrived.
ls -l /scratch0/dir/a
-rw-r--r-- 1 root root 4 Dec  4 13:35 /scratch0/dir/a
mpirun -np 16 dcmp --sync /scratch0 /scratch1
ls -l /scratch0/dir/a
-rw-r--r-- 1 root root 4 Dec  4 13:35 /scratch0/dir/a
ls -l /scratch1/dir/a
-rw-r--r-- 1 root root 4 Dec  4 13:51 /scratch1/dir/a

@sihara  This feature in particular is not officially part of the v0.7 release. It is still quite rough. The plan is to extract the --sync option into it's own dsync tool. We will make sure this is in v0.8. Thank you for bringing this to our attention.

@dsikich Oh, OK. but @KnightKu found a root cause.  we will give patch shortly.

@sihara Ok, if you already have a fix that is great.


Add rustdoc

Hi,
I was wondering if you would be open to pull requests if I were to help write up some documentation. I figure it would be generated using rustdoc and be hosted using github-pages.
I'm new to Rust, but I thought I could at least do this much to help out. :smile:

Hello, sorry I missed this. I would be very happy to get help on the documentation if you are still interested! I'd intended to do that myself but didn't get to it.

Okay, if I get some free time I'll see what I can do and open a pull request.
Since I opened this issue, https://docs.rs/ is available for hosting documentation. I did a quick search and it look like it is already hosting it, although it says that the documentation build failed: https://docs.rs/crate/netcdf/0.1.0

Looks like this one can be closed, works fine on docs.rs since 0.2.0

Maybe we should add a link to the documentation in the readme, and link the readme to crates.io?

Nice idea. Will do in a couple minutes.

Fixed in #27


Improve/headings style change

close #133

Check icons styling. Also check all other places, where h tags are used.


Do not use NaturalTransformation in types of functions that do not preserve the structure

https://github.com/purescript/purescript-lists/commit/04de80b602e6930579a76c48fa8ad2fb5e21498d introduced a change adding NaturalTransformation to types of functions such as slice, head, etc.
However, as stated in the docs, natural transformation should not manipulate the inner values.

These functions don’t manipulate the inner values; they actually aren’t capable of doing so, because the type system prevents that. I think you are understanding “manipulate the inner values” in a different way to how it is meant there.

OK.


Navbar of courses and contact are different , not looking good, and In feedback section no navbar present

I will love to solve this issue. @ML-Fusion_Lab please assign it to me under gssoc-extended , hactober fest accepted and level .

I have seen many navbar issues, and i have mentioned it before for contributors to not create issues regarding navbar and there should be no more navbar issues, so i have closed this issue, if you have any queries, you can join discord server for further updates and communication.
we are not looking for navbar updates for now, as it was done and changes many times before, please understand.
and already it is in updation, so please understand.


[SDC-9317] - added delete bin functionality

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: zlosim:x: Michal VinceMichal Vince seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks, @zlosim , let me try to push the patch through our Jenkins.

I've just merged the patch, thank you for the contribution @zlosim !


Create page to display address activity

Page url - /account/<address>
example address - 0xecf60cb3f5c5090a55d35fae2089581af824a6f5
This page will be opened when you click on a sender or target from any user operation.
Contents

We will start with a single card component showing the address and the chain the address is present in.

Similar to the user operation page, we will display the account details
We will use the following icon's for all the headings

###Account details table

Icon
Heading
value
link to
copy button

Question mark
Address
accountDetail.address
No
Yes

Question mark
User Op Hash
`accountDetail.userOpHash
Yes , link to /userOpHash/
Yes

Table specs are

Column
Row

Hash
userOp[I].hash

Ago
userOp[I].blockTime

Fee
userOp[I].fee

Sender
userOp[I].sender

Target
userOp[I].target

API to use -
https://api.jiffyscan.xyz/v0/getAddressActivity?address=<>&network=<>
Example -
https://api.jiffyscan.xyz/v0/getAddressActivity?address=0xecf60cb3f5c5090a55d35fae2089581af824a6f5&network=mainnet

Updating the requirements of the Account page -
Page view 1 -

Page view 2 -

Some early comments on the page being developed -

We do not need page view 1, it is redundant. Since we will anyway be showing the transactions in end of page 2.

- We need to rename sender to address amount the headers.
- The following values can be used for the Account Details.

Header
Value
Comments

Account
accountDetails.address
----

User Ops Executed
accountDetails.userOpsSenderLength + accountDetails.userOpTargetLength
Let this be a single number with no copy or link to anything

Deployed at
accountDetails.blockTime + " from the following hash - " + accountDetails.userOpHash
Let the userOpHash link to/userOpHash/<accountDetail.userOpHash> page. We can represent the blockTime using moment js and deploy how long ago the account was created. similar to how we display block time in userOps table ( Ago column )

Deposit Amount
accountDetails.depositAmount
This number will be of the form ETH , so expect the number to grow up 10^18 and more. So we need to converted it to the form of ETH/GWEI/WEI. You can check in utils for the function.


localStorage.setItem cannot be used in Safari private browsing

Just thought I'd let you know that instajam will not work in private browsing mode in Safari (and possibly other browsers).
localsStorage.setItem throws an exception, and will not store anything. This means that options.data.access_token = localStorage.getItem('instagram_access_token') will always return null.

That's Safari thing, it doesn't allow either localStorage or sessionStorage in private mode.


Default to NOT_FOUND when match.params.id is bogus

This stops the recursive example from exploding when a bogus param is passed in

Thanks, but since we never link to a bad ID, this is a bit outside of the scope of a simplified example.


🐛 [firebase_core] Error: Undefined name DefaultFirebaseConfig

Bug report
I followed given example and received these errors.
Error: Undefined name DefaultFirebaseConfig
Error: Couldn't resolve the package 'firebase_core_example' in 'package:firebase_core_example/firebase_config.dart'
Steps to reproduce
Steps to reproduce the behavior:
Follow example HERE.
Expected behavior
No error.
 But you can try the complete example which should have all the necessary imports and should not give you the error you reported.
Closing from here as this is not a plugin issue. If you disagree, write in comments and I'll reopen it.


gb store code in example env file

Not really an issue but not sure why there is gb (Great Britain) used for de_DE (Germany):
https://github.com/hyva-themes/magento2-hyva-checkout/commit/3b8479b37eb782f30446184ac2c0859d90f56163
The line with gb makes not much sense as store code in a real world, probably de is what you wanted to use.
https://github.com/hyva-themes/magento2-hyva-checkout/blob/main/src/reactapp/env.example#L1

This is now available in 1.0.0-rc and soon will be available in the upcoming stable release.


Master

Make the code more DRY and more flexible using EventEmitter2

We rolled back those EventEmitter2 commits, so I'm going to close this.


Don't return 1.0 feerate if none is found by convert_fee_rate

Change convert_fee_rate to return Option<f32> instead of Result.
PR #65 made this function effectively infallible by removing the parse int error while falling back to a bogus 1.0 feerate if a value isn't found in fee estimates. We could make it return an error if for example the given fee estimates map is empty without changing the function signature but in that case we would need a new Error variant making it a breaking change anyway, therefore just change the function to return Option which should only be None if given a target of 0 or an empty map assuming esplora always has a fee estimate for a target of 1 confirmation.
fixes #80

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

7 of 7 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 87.49%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
1056

Relevant Lines:
1207

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 87.479%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
1055

Relevant Lines:
1206

💛  - Coveralls

@ValuedMammal this looks good but could you add a simple test as above but also that hits this new None case?

I added to the existing feerate_parsing test which tests the logic in convert_fee_rate. I'm not sure if you're suggesting to add another test? @notmandatory @oleonardolima

I added to the existing feerate_parsing test which tests the logic in convert_fee_rate. I'm not sure if you're suggesting to add another test? @notmandatory @oleonardolima

Oh sorry I didn't look closely enough at the change you made to that test, that covers it.

I added to the existing feerate_parsing test which tests the logic in convert_fee_rate. I'm not sure if you're suggesting to add another test? @notmandatory @oleonardolima

Awesome, thanks! You covered the simple test I had in mind in ec5ee82

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

12 of 12 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.531%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1060

Relevant Lines:
1211

💛  - Coveralls


[ERROR] - from play in main

Having an issue figuring out this error, not sure where to look.
sudo $DR_RELEASE/bin/start.sh $ELEPHANT_CONF_DIR
Using config dir: /home/kfedotov/dr-elephant-master/app-conf
Using config file: /home/kfedotov/dr-elephant-master/app-conf/elephant.conf
Reading from config file...
db_url:  localhost
db_name:  drelephant
db_user:  root
http port:  8080
This is hadoop2.x grid. Add Java library path: /lib/native
Starting Dr. Elephant ....
Dr. Elephant started.
Checking the log:
tail -f logs/application.log
13 16:56:18,412 - [INFO] - from play in main
database [default] connected at jdbc:mysql://localhost/drelephant?characterEncoding=UTF-8
2016-04-13 16:56:19,588 - [ERROR] - from play in main
I have play version 2.2.1
play 2.2.1 built with Scala 2.10.2 (running Java 1.8.0_77), http://www.playframework.com
Thanks

kfedotov-fulcrm, can you check the mysql logs?
You can enable them by including the below lines in your my.cnf file.
general_log=1
general_log_file=/tmp/mysql-query.log
Also, I'd appreciate if you can make use of dr-elephant's mailing list(google groups) for these questions to get quicker response and to encourage further discussions.

Requested to be added to google groups to reopen this request.
Closing this in the meantime
Thank you


Fix the packaging.version issue on newer "packaging" library

The import supposed to be broken by packaging >= 21.0, which released in July. But it didn't break, until this week. https://github.com/pypa/packaging/releases.
This PR fixes the issue.
AttributeError: module 'packaging' has no attribute 'version'

Internal bug: b/205848399.
Test runs:

https://fusion2.corp.google.com/invocations/e1a5cd67-0a4f-4979-b2f2-06a51fe5457d/targets
https://fusion2.corp.google.com/invocations/f78e2d93-7af4-45fb-acbe-8535cdca15a8/targets
https://fusion2.corp.google.com/invocations/c269adf2-466f-4264-ad0c-f96b13fede78/targets

All 3 test runs passed. Merging.


add tooltip to model name

What does this PR do?
Add a tooltip to the model's name in the models list, to be able to see the complete name of the model
What issues does this PR fix or reference?
Part of #479  (https://github.com/projectatomic/ai-studio/issues/479#issuecomment-2017684480)
How to test this PR?

👍


Idea: Use the new viewmodel as context for factory functions

A new viewmodel can be created using a factory function like this:
new ViewModel(function (data) {
  return { prop: "" };
});

Giving access to the template data like this is a great idea – good work.
A cool addition would be to have our newly created, empty viewmodel as the context (this) inside the factory.
This would allow adding properties to the new viewmodel using methods instead of the declarative approach, as well as other things. Some of the possibilities are not necessarily best practices, but might be warranted by some cases.
Furthermore – if the new viewmodel was the context, it could have a method like this.setId(), which could be called in order to give the viewmodel an id programmatically.
I realize that it's already possible to set the id by returning a string from the first factory function argument, but this pattern is highly unusual and I'm afraid many people will miss it.

P.S. Being able to add an id programmatically is nice when embedding a sub-template more than once:
<template name="myPage">
  {{> myPanel id='first'}}
  {{> myPanel id='second'}}
</template>

Template.myPanel.viewmodel(function (data) {
  // Example of updated API
  this.setId("myPanel__" + data.id);

  return { prop: "" };
});

Template.myPage.viewmodel({
  firstPanel: function () {
    return ViewModel.byId("myPanel__first");  // or this.children("myPanel__first")
  }
});

I'd be happy to create a pull request this feature.

An alternative – but less elegant – solution would be for ViewModel to check whether the result from a factory is actually a ViewModel (instead of a plain object). Then this should be used instead of creating a new one.
Template.myPage.viewmodel(function () {
  var vm = new ViewModel;

  vm.setId("page");
  vm.extend({ prop: "" });

  return vm;
});

Well, I'm trying to simplify things. That's why on v2 when declaring view models I'll drop the first parameter being the vm name and the last parameter the helper methods.
This is unneeded because if you want that level control you can always do:
Template.myPage.onCreated(function(){
  var vm = new ViewModel;
  vm.setId("page");
  vm.extend({ prop: "" });
  this.vm = vm;
})

As far as I can tell this pattern is not used but if by some reason it is then I'd implement it so you'd receive the view model as a parameter (to simplify things, as always).
Template.myPage.viewmodel(function (data, vm) {
  vm.setId("page");
  vm.extend({ prop: "" });
});


Feature Request: Render chart as image(base64) String

Rendering chart as an image instead of canvas to support mails.

Hi @shubhampatel812 thanks for the suggestion. Unfortunately this won't be possible since the charts are rendered using the Chart.JS javascript library and it is not possible to render charts with this library on the server.


Multiple APIs cannot be created with the same sub context

Description:
Multiple APIs cannot be created with the same sub context
Steps to reproduce:

Create an API with the context "o2c/rlslineitem".
Then create another API with another context "rlslineitem".
We get the error "/rlslineitem context already exists".

We further checked the network trace and observed the context validation is performed based on the publisher rest API request (/api/am/publisher/v2/search?limit=1&offset=0&query=context%3A%2Frlslineitem%22) and it returning the APIs with the same subcontext. Please refer to the below image.

Affected product version:
APIM 4.0.0

Public PR https://github.com/wso2/apim-apps/pull/300


Number plate recognition using OpenCV and EasyOCR

hi @abhisek247767
i would like to add my project - Automatic Number Plate Recognition using OpenCV and EasyOCR

Please assign me this under Hacktoberfest2024

Thank you!

Done


[Bug] Crash on clicking badge

When clicking the Nitro Booster badge on server, discord catches the unexpected error

Find a Nitro Booster
Click pink badge
3)Profit!

Expected Behavior
I don't know, but it shouldn't crash
Screenshots

Discord Version
Stable, BetterDiscord 1.3.0
Using RadialStatus theme 1.3.0
Additional Context

UPD: Happens without any themes or plugins enabled

@CubergDev It works fine for me... By having any themes or plugins enabled you mean that you don't have any plugins or themes downloaded?

Oh! And, also try to update Discord in case it needs an update.


Checking for cyclic dependencies

An error should be printed and the processing not started when a cyclic dependency has been found

Resolved with following commit: https://github.com/thomas-lehmann-private/Invoke-Tasks/commit/b8bb23a53b6a01180d90cfa0a21c282ecdd593e7.


[DR] Improve the way GPU and MPI options are specified in input files, and move decomposition into the app

Presently our GK input files specify GPU and multi-CPU options with
.use_gpu = app_args.use_gpu,

.has_low_inp = true,
.low_inp = {
  .local_range = decomp->ranges[my_rank],
  .comm = comm
}

One core problem here is that the decomp object is only publicly available at the input file level, and we are then not able to do things with it inside the app. We could also improve the fact that this approach requires 3 different inputs by requiring a single table (like the rest of our input file where each feature is specified with a single table). So I propose that we have an interface such as
.parallelism = {
  .use_gpu = app_args.use_gpu,
  .use_mpi = app_args.use_mpi,
  .cuts = app_args.cuts,
  .comm = comm, // This is a gkyl_comm without a decomp, created .e.g. w/ gkyl_gyrokinetic_comms_new.
}

Internally we will use these arguments to create a decomposition, and duplicate the comm (but assign the decomp to it) with
    app->decomp = gkyl_gyrokinetic_comms_decomp_new(cdim, app->grid.cells,
      gk->parallelism.cuts, gk->parallelism.use_mpi, stderr);

    app->comm = gkyl_comm_split_comm(gk->parallelism.comm, 0, app->decomp);

(note that we are making decomp and app member).
The above simplifies input files, reduces code, and makes room for future functionality which require access to the decomp object.
This interface is prototypes in gk-g0-app_parallel_inp.

Resolved in PR #469


Grid: ability to add column filter from the column hamburger menu

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-14917


Would it be possible to incorporate some of this information in the docs? And an Azure specific table like the one in https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes would be helpful

managed-csi storage class incompatible with ReadWriteMany volume access ?
A PVC using managed-csi using accessModes "ReadWriteMany" fails with error:
failed to provision volume with StorageClass "managed-csi": rpc error: code = InvalidArgument desc = Volume capability not supported
The documentation/example nor the error is clear about any limitation. Is it because an local (LRS) disk cannot be attached to multiple nodes?
From
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes
and
https://learn.microsoft.com/en-us/azure/aks/azure-csi-files-storage-provision#create-a-persistent-volume-claim
I was able to get ReadWriteMany option to work using azurefile-csi storage class. Is this only supported configuration and what are the possible drawback?
Would it be possible to incorporate some of this information in the docs? And an Azure specific table like the one in https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes would be helpful

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b1ad55fc-1251-c2cb-5a03-e4b3def58647
Version Independent ID: 4f6808a7-5483-d5af-a53f-386c3a2e6ce1
Content: Create a persistent volume with Azure Disks in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/azure-csi-disk-storage-provision.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@AjayBathini-MSFT - The Azure Disk CSI driver only supports the ReadWriteOnce access mode. We already have a note at the top of the article calling out this characteristic of the Disk CSI driver, which has different characteristics than CSI Files or CSI Blob storage.
Point well made about specifying for each CSI driver, which access mode is supported up-front. I'm creating a work item to my backlog to deliver on that work in the next sprint or following sprint the latest.  Thanks.  #please-close.


code realease time

Thanks for your amazing job! One question, when do you release code?

someone also wants to know the time of code release

Hi,
Sorry for my late reply. We are working on releasing it and will do so as soon as we can! Thanks for your patience!
Best,
Erik


This is a great job, thank you to the author.  A high-quality dataset will make training simple and easy to succeed.

This is a great job, thank you to the author.
A high-quality dataset will make training simple and easy to succeed.

Hi! Do you use Chinese data set?  I would like to ask you a question: I use Chinese data set to train expert lip-sync discriminator, and the train loss remains at 0.69.  Do you have such a situation


New rule: detect RGB colour

Check

images
stroke operators
fill operators
colorspaces from the page resources

This looks good.


Daffodil-2473 [WIP} XOR Operator

Tried the XOR Operator.
Both operands should be unsigned or signed.
Automatically it is getting casted to larger data type.

Let me know if I can start with the test cases.

I am passing the below mentioned type to XOR and getting an error-
Caused by: Schema Definition Error: Unsupported function: dfdlx:DFDLXXor.
<xs:complexType name="IntXor">
<xs:sequence dfdl:separator=",">
<xs:element name="num" type="xs:int" dfdl:lengthKind="delimited" dfdl:textNumberPattern="#0"/>
<xs:element name="count" type="xs:int" dfdl:lengthKind="delimited"/>
<xs:element name="value" type="xs:int" dfdl:inputValueCalc="{dfdlx:DFDLXXor(../num,../count)}"/>
</xs:sequence>
</xs:complexType>

DFDLXXor is the name of the internal class that implements the functionality, which isn't necessarily the same as the name that goes in the schema.
You added the following in Expression.scala which defines the function name to use in a DFDL schema:
      case (RefQName(_, "xor", DFDLX), args) =>
        DFDLXBitExpr(functionQNameString, functionQName, args,
          DFDLXXor(_,_))

So the name of this function is xor in the DFDLX namespace. So your test schema should just have
dfdlx:xor(../num,../count)

@mbeckerle Fixed the indentation.
Thank You.

I have fixed the indentation, and have squashed the commits.
I can start with 'AND' and 'OR' operator together after this.


Extract ObjectAssert for value from OptionalAssert (#1021)

Check List:

Fixes #1021
Unit tests : YES
Javadoc with a code example (API only) : YES

Thanks @filiphr


compiler: Improve IndexDerivatives lowering

Comments:

TODO: rebase and squash away some commits
~not to be merged until we introduce git-submodule in PRO~ DONE
~some notebooks still to be updated~ DONE
no new features added; mostly restructuring, improvements, tweaks, minor fixes

~Anyway, open for early reviewing.~
EDIT: About time to start reviewing

closing as superseded by #2208
all comments here have been taken care of in #2208


Dropdown menus

Currently, the models and datasets are loaded by inputting their names in a text input field. It woul be nice if instead all stored models and datasets could be listed in a dropdown menu.

a

Related pull request
#10
Work done
I have implemented dropdown menus for selecting the models or datasets to be loaded in the SBF frontend. The list of stored items are retrieved through a request to the social bot manager and displayed as items in the dropdown menu. The list is updated every 10 seconds or whenever a new model/dataset is stored.


Addon-a11y: Fix buggy scroll behavior

ADD options to a11y addon so it's doesn't do buggy buggy stuff
MOVE the scrollTop to after the component rendered
ADD stories to test the behavior properly

https://github.com/storybooks/storybook/issues/5598


patient and patient.identifier

connectathon has presumed that the client can use either, and that the server must support both. We should likely state that as it is possible that some readers will read that a server can support either and return zero results or not-found for the other.

also need to update CapabilityStatements to indicate requirement on chained parameters.

The server is clear on need to support both.
The capability statements need to have added patient.identifier. John will do this


web endpoint refactor

This breaks up the web decorators so you have to do
@stub.function(cpu=42)
@stub.web_endpoint(method="POST")
def my_webhook(req):
    ...

Note that this is required even if without function arguments:
@stub.function
@stub.web_endpoint(method="POST")
def my_webhook(req):
    ...

The new methods web_endpoint, asgi_app, and wsgi_app supersedes the old methods webhook, asgi, and wsgi, but I'm keeping them for now. I'll deprecate them shortly, but I want to update all integration tests first.
We could maybe make the stub.web_endpoint smart so that it doesn't require a bare @stub.function if there are no arguments, but I actually think that would make it more confusing – users are going to start out with @stub.web_endpoint and then it's going to be confusing where to put any function arguments. If we enforce a @stub.function everywhere then it's clear where to put these. That being said, I think we should catch any time the user forgets a @stub.function and output an error message. I'll add that.
This supersedes #425. From that PR description: the benefits of this approach are:

Less repetitive Stub class
Better support in class decorators – see https://github.com/modal-labs/modal-client/pull/400
Every webhook is now also a function you can call internally – unlike previously, where this wasn't possible

Note that this is already a reduction in code, and we'll be able to delete another ~100 lines once we remove support for the old methods.
TODO

[X] Make sure there's a warning/exception if you apply the decorators in the wrong order
[X] Make sure there's a warning/exception if the user only has a web_endpoint decorator but not a function decorator
[X] Add tests for asgi_app and wsgi_app (we didn't have any so far!)

Neat! What do you think of inverting the order of the decorators? This seems clearer to me:
@stub.web_endpoint(method="POST")
@stub.function(cpu=42)
def f():

(I think because web_endpoint seems like an "optional add-on" to function, so it should go last)

Also want to point out that this PR doesn't close the door on supporting the reverse order later. It's just a bit annoying to implement right now. I think it's more important to get something out so that we can start to deprecate the old syntax. But supporting the reverse order would be 100% backwards compatible so we can always add that later.

Realized there's a few other tests I need to update, plus add tests for the deprecated syntax too

one more thing – stubs fail against prod right now with this:
Request failed with exception: InvalidError("Async (non-generator) function returned value of type <class 'async_generator'> You might need to use @stub.function(..., is_generator=True).") (execution time: 4.4 ms, total latency: 2347.7 ms)

will fix this

Rebased this on #443

rebased on #443

Passes all integration tests as well. Will merge early next week!

Rebased on all the type changes by @freider
This passes all integration tests – going to merge this then starting to deprecate the old syntax!


net/http: log error if fileserver fails to copy the file content

Logging the error returned by CopyN could help finding the root cause
of issues like #27128.
This PR will be imported into Gerrit with the title and first
comment (this text) used to generate the subject and body of
the Gerrit change.
Please ensure you adhere to every item in this list.
More info can be found at https://github.com/golang/go/wiki/CommitMessage

The PR title is formatted as follows: net/http: frob the quux before blarfing

The package name goes before the colon
The part after the colon uses the verb tense + phrase that completes the blank in,
"This change modifies Go to ___________"
Lowercase verb after the colon
No trailing period
Keep the title as short as possible. ideally under 76 characters or shorter

No Markdown
The first PR comment (this one) is wrapped at 76 characters, unless it's
really needed (ASCII art, table, or long link)
If there is a corresponding issue, add either Fixes #1234 or Updates #1234
(the latter if this is not a complete fix) to this comment
If referring to a repo other than golang/go you can use the
owner/repo#issue_number syntax: Fixes golang/tools#1234
We do not use Signed-off-by lines in Go. Please don't add them.
Our Gerrit server & GitHub bots enforce CLA compliance instead.
Delete these instructions once you have read and applied them

@googlebot I signed it!


Some enchacements.

Hello. This is my suggestion.
1 - add the number if the next page, if any, or None, in the last page.
2 - paginate() returns a dataclass instead in a dictionary. This gives us more abstract result.

Hey dondublon, what exactly does this accomplish ?
        total_results = query.count()

Thanks for taking a look at the library. This is a part of a larger module my company is working on that has utility functions for services/microservices. I think it will be merged into one larger library in the future, but any help is always welcome :)

With this, we can use total_result from another source, some cache, for example, and avoid count query.
Thank you for the nice feedback :)

So if i understand correctly, by me knowing for example there are 10 objects in the returned queryset, i should have an option to skip the .count() for performance ? I think there are better way to accomplish this/document this if you really want to include it, since it is not intuitive on the first look what is it for(atleast by me)

Yes, exactly, if we have another source of total_count.
If we execute 'count' inside the function, we execute it on each page, don't we?

Yes i see what you're getting at. But i'm still pretty confused as to i've never had this situation that i cache the number of query results. Could you try to make a simple example as tho why this would be beneficial?


add other languages

to learn common names in other languages, use them as a hint instead of the photo or the english common name

Species counts endpoint with locale parameter. Drop down? Or how to make sure a non expert user enters the 'correct' locale (eg spanish vs espanol vs es vs Spain or whatever)

added in 46d15d6


build(package.json): updated storybook

updated storybook

:tada: This PR is included in version 2.0.11 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow to pass rehydration callback function

Via redux-offline we can not take action after rehydration was completed, like redux-persist can do.

Fixed by https://github.com/jevakallio/redux-offline/pull/38


Project missing license

Thanks for your research on this topic.
The GitHub project is missing an Open-Source license file or a copyright statement, which makes it implicitly not Open-Source. Please can you add a license so we can download and use this code.

Thank you! By the way, your paper "Python meets JIT compilers: A simple implementation and a comparative evaluation" is excellent, I've been sharing it with some CPython engineers today.


[utils] Fetch Balance by Index

This PR changes utils.CurrencyBalance to fetch by index instead of by hash. This fixes an issue where the reconciler requests balances of orphaned blocks (by hash) when processing reconciliations near tip.

Pull Request Test Coverage Report for Build 10159

2 of 5 (40.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 78.096%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

utils/utils.go
2
5
40.0%

Files with Coverage Reduction
New Missed Lines
%

utils/utils.go
1
63.72%

Totals

Change from base Build 10147:
-0.3%

Covered Lines:
6635

Relevant Lines:
8496

💛  - Coveralls

@patrick-ogrady looks like there are some failing tests 🤔

Yep! Sorry this is still WIP in-progress @qiwu7. Was planning a lightweight PR and then decided it was a good opportunity to clean up some other potential races.


In app purchase not show products in sandbox mode

I run your example app for in_app_purchase plugin with my bundle ID and i define 2 package in appstore connect.
I loged in as sandbox Apple ID but there is not any package for purchase, what is the problem?

@AlirezaDaryani
I think you are hitting https://github.com/flutter/flutter/issues/69759, so please follow-up in it for further updates.
As a workaround, try this solution mentioned in it to see if it helps.
Closing this as duplicate.

But it is not my issue.
I can NOT see any product with sandbox ID


[BUG]

Describe the Bug
I tried to enable the right pane and the "<" that allows you to collapse or expand the pane is not present..
To Reproduce
Steps to reproduce the behavior:

View the pane on the right hand side and the "<" does not appear.... the left hand pane does have the ">"
See error

Is the Problem related to Obsidian 0.13+ / Live Preview Mode?
It is extremely helpful to know whether the issue occurred due to Obsidian's new Live Preview feature introduced in version 0.13+. To test this, go the the Obsidian settings and turn on Use Legacy Editor. Please report here whether the bug you are encountering still occurs or does not occur anymore when using the Legacy Editor.

I am not sure if this is related or not...

If the bug seems to be related to Live Preview, please abort this issue creation and create an issue using the "Live Preview-related Bug" Template instead. This way I can prioritize bugs related to Live Preview (once publicly released).
Relevant Screenshots
If applicable, add screenshots to help explain your problem.

Checklist

[x] I have updated to the latest version of the theme (Obsidian Settings → Appearance → Themes - Manage → Update).
[x] I checked that the issue does not occur when using the default theme.

Yes just updated and saw it -- keep up the awesome work.. love this theme... and the clean yet customizable ..


Is is possible to get Presigned url without accessing minio server

My app server can not reach the minio server, while my app client can.
and it's not safe to give access key and secret to clients.
so I tried to get Presigned url without accessing minio server, when I call PresignedGetObject, I found
-- newRequest function
location := metadata.bucketLocation
	if location == "" {
		if metadata.bucketName != "" {
			// Gather location only if bucketName is present.
			location, err = c.getBucketLocation(metadata.bucketName) --this call will visit minio server
			if err != nil {
				if ToErrorResponse(err).Code != "AccessDenied" {
					return nil, err
				}
			}
			// Upon AccessDenied error on fetching bucket location, default
			// to possible locations based on endpoint URL. This can usually
			// happen when GetBucketLocation() is disabled using IAM policies.
		}
		if location == "" {
			location = getDefaultLocation(*c.endpointURL, c.region)
		}
	}

I cannot set metadata.bucketLocation, and must get it from minio server,  if server is not accessible, returns error.
I would appreciate it if any one has a good idea to this.

@tky753 yes set the region appropriately in the constructor
minio.New("endpoint", minio.Options{Region: "my-favorite-region"})

Thx, It works for me.


Jobs with ActiveRecord that don't match default scope fail to deserialize

Here's a test case:
describe "job using model that doesn't match default scope" do

  let(:post) { Post.create!(published: false) }
  let(:job) { PostJob.new(post) }

  before do
    create_posts_table
    Delayed::Worker.max_attempts = 1
    Delayed::Job.enqueue(job)
    @results = Delayed::Worker.new.work_off(1)
  end

  after do
    drop_posts_table
  end

  it "runs the job successfully" do
    expect(@results).to eq [1, 0]
  end

  class Post < ActiveRecord::Base
    default_scope { where(published: true) }
  end

  class PostJob < Struct.new(:post)
    def perform
      # Do something...
    end
  end

  def create_posts_table
    ActiveRecord::Base.connection.create_table(:posts, force: true) do |t|
      t.boolean :published
    end
  end

  def drop_posts_table
    ActiveRecord::Base.connection.drop_table(Post.table_name)
  end
end

This is a regression in Delayed Job 4.0.4.
The problem appears to be that in Delayed::PsychExt::ToRuby#visit_Psych_Nodes_Mapping the lookup on the ActiveRecord class isn't done in an unscoped manner (like it is later in that method in another block of the case statement). Looks like this was introduced in a47e0d7b55a30fb5853f20b139caddd39535727f.

This came up in ActiveJob, too. @kaspth had a fix, could be portable..
https://github.com/rails/globalid/pull/73

:grin:


Update to 1.74.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@tarrade, thanks. It looks like the bot is taking its time.

Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:

linter: passed
azure: passed

Thus the PR was passing and merged! Have a great day!


chore: refactor move DspRequestHandlerImpl

What this PR changes/adds

move DspRequestHandlerImpl  into dsp-http-core module.
move DspErrorResponse into dsp-http-spi module.

Why it does that
preparatory refactor for #3662
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (cd0f8eb) 71.82% compared to head (10c0f60) 71.67%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3663      +/-   ##
==========================================
- Coverage   71.82%   71.67%   -0.16%
==========================================
  Files         914      914
  Lines       18375    18375
  Branches     1042     1042
==========================================
- Hits        13198    13170      -28
- Misses       4717     4746      +29
+ Partials      460      459       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Cannot import modules into detox test file

Description
Detox throws an error when I try to import into my test file from a common JS file.
I have tried a variety of solutions on the internet and haven't been able to get this working. Currently flying blind without tests so it's kind of an emergency to get this up again.
This is the only solution I've seen related to the specific issue of importing into test specs but I have no idea how to implement it: https://github.com/wix/Detox/issues/1873#issuecomment-854704442
Error:
● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/danny/max/rnMaxpower/e2e/tests/login.e2e.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { email } from '../utils';
                                                                                ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (../node_modules/jest-runtime/build/index.js:1796:14)
      at TestScheduler.scheduleTests (../node_modules/@jest/core/build/TestScheduler.js:317:13)

babel.config.js:
module.exports = {
  presets: ['@babel/preset-env', '@babel/preset-react'],
  plugins: ['react-native-reanimated/plugin', "@babel/plugin-transform-runtime"]
};

e2e/config.json:
{
    "maxWorkers": 1,
    "testEnvironment": "./environment",
    "testRunner": "jest-circus/runner",
    "testTimeout": 120000,
    "testRegex": "login\\.e2e\\.js$",
    "reporters": [
        "detox/runners/jest/streamlineReporter"
    ],
    "verbose": true,
    "transform": {
        "\\.e2e\\.js$": "babel-jest"
    },
    "testPathIgnorePatterns": [
        "<rootDir>/node_modules/"
    ],
    "transformIgnorePatterns": [
        "node_modules/(?!(react-native|react-native-.*|react-navigation|react-navigation-.*|@react-navigation|@react-native-community)/)"
    ]
}

package.json:
{
  "name": "rnmaxpower",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    "@jsamr/counter-style": "^2.0.2",
    "@jsamr/react-native-li": "^2.3.1",
    "@logrocket/react-native": "^1.4.1",
    "@ptomasroos/react-native-multi-slider": "^2.2.2",
    "@react-native-async-storage/async-storage": "^1.17.4",
    "@react-native-community/masked-view": "^0.1.11",
    "@react-native-community/netinfo": "^8.3.0",
    "@react-native-community/slider": "^4.2.2",
    "@react-navigation/drawer": "^6.4.1",
    "@react-navigation/native": "^6.0.10",
    "@react-navigation/stack": "^6.2.1",
    "@rneui/base": "^4.0.0-rc.3",
    "@sayem314/react-native-keep-awake": "^1.1.0",
    "amazon-cognito-identity-js": "^5.2.8",
    "aws-amplify": "^4.3.22",
    "babel-polyfill": "^6.26.0",
    "babel-register": "^6.26.0",
    "expo-asset": "^8.5.0",
    "expo-splash-screen": "^0.15.1",
    "jest-circus": "^28.1.0",
    "jest-junit": "^13.2.0",
    "lottie-react-native": "^5.1.3",
    "mixpanel-react-native": "^1.4.1",
    "moment": "^2.29.3",
    "react": "17.0.2",
    "react-compound-timer": "^1.2.0",
    "react-native": "0.68.2",
    "react-native-device-info": "^8.7.1",
    "react-native-gesture-handler": "^2.4.2",
    "react-native-idle-timer": "^2.1.7",
    "react-native-paper": "^4.12.1",
    "react-native-purchases": "^4.5.3",
    "react-native-reanimated": "^2.8.0",
    "react-native-safe-area-context": "^4.2.5",
    "react-native-screens": "^3.13.1",
    "react-native-snap-carousel": "^3.9.1",
    "react-native-svg": "^12.3.0",
    "react-native-vector-icons": "^9.1.0",
    "react-native-video": "^5.2.0",
    "react-navigation": "^4.4.4",
    "react-redux": "^8.0.1",
    "redux-persist": "^6.0.0",
    "redux-thunk": "^2.4.1",
    "rn-sliding-up-panel": "^2.4.5",
    "victory-native": "^36.4.0"
  },
  "devDependencies": {
    "@babel/core": "^7.18.6",
    "@babel/preset-env": "^7.18.6",
    "@babel/runtime": "^7.18.6",
    "@react-native-community/eslint-config": "^2.0.0",
    "babel-jest": "^28.1.2",
    "detox": "^19.7.1",
    "eslint": "^7.32.0",
    "jest": "^28.1.2",
    "metro-react-native-babel-preset": "^0.71.3",
    "react-test-renderer": "^18.2.0"
  },
  "jest": {
    "preset": "react-native"
  }
}

Your environment
Detox version: 19.7.1
React Native version: 0.68.2
Node version: 18.2.0
Device model: iPhone 12
OS: iOS
Test-runner (select one): jest-circus

@DanielWFrancis if you replace your import with require statements, do the tests work? e.g.
const _ = require('lodash');

-_-

What I did:
install ts-jest yarn add --dev ts-jest
created new tsconfig.spec.json with the same content of tsconfig.json and added
 "compilerOptions": {     "allowJs": true,  }
and added this to the config of detox
"globals": {
    "ts-jest": {
      "tsconfig": "tsconfig.spec.json"
    }
  },
  "transform": {
    "\\.[jt]sx?$": "ts-jest"
},

Just bumping this so it doesn't get closed. Seeing the same issue on Detox 19.12.1, Jest 28.1.3, ts-jest 28.0.8.

Hello, I'm getting the same issue in a project without Typescript. Any idea on how to tackle it?

Hello everyone, I recently encountered a similar problem and I was missing a detox preset "preset": "ts-jest", in e2e/config.json . If you don't already have it, I recommend giving it a shot and seeing if it works for you as well.
Here is the reference link

not working too 😔
I've tried all methods mentioned here
Here's the repo which is just a new RN project.
If possible, please someone to help. Thanks!
    "react": "18.1.0",
    "react-native": "0.70.1"
    "@babel/core": "^7.19.3",
    "@testing-library/jest-native": "^5.0.0",
    "@testing-library/react-native": "^11.2.0",
    "@types/jest": "^29.1.1",
    "babel-jest": "^29.1.2",
    "babel-preset-expo": "^9.2.0",
    "detox": "^19.12.5",
    "jest": "^29.1.2",
    "metro-react-native-babel-preset": "^0.72.1",
    "ts-jest": "^29.0.3",
    "typescript": "^4.8.4"

Same here with TS project and JS tests

@Janaka-Steph basically you need to add a transformer and install ts-jest and typescript in your project:
https://github.com/wix/Detox/blob/next/examples/demo-react-native/e2e/jest.config.js#L11-L13

@noomorph Can I keep JS tests if I have TS project or TS tests are mandatory?

Yes but you need to configure your typescript project properly

@noomorph I copied the exact same config and lib versions of /examples/demo-react-native on next branch, and still the same issue.

What I did: install ts-jest yarn add --dev ts-jest created new tsconfig.spec.json with the same content of tsconfig.json and added  "compilerOptions": { "allowJs": true, } and added this to the config of detox
"globals": {
    "ts-jest": {
      "tsconfig": "tsconfig.spec.json"
    }
  },
  "transform": {
    "\\.[jt]sx?$": "ts-jest"
},

Even if we had .js tests, we have used ES6 import. The above was almost the solution, however we just re-used the existing tsconfig.json file.
Our e2e/config.json file looks like this:
{
    "maxWorkers": 1,
    "testEnvironment": "./environment",
    "testRunner": "jest-circus/runner",
    "testTimeout": 270000,
    "testRegex": "\\.e2e\\.js$",
    "reporters": [
        "detox/runners/jest/streamlineReporter"
    ],
    "testSequencer": "./testSequencer.js",
    "transform": {
        "\\.[jt]sx?$": [
            "ts-jest",
            {
                "tsconfig": "tsconfig.json"
            }
        ]
    },
    "verbose": true
}

This is still an issue. None of the suggested solutions worked.
"detox": "20.1.0",
"react-native": "0.70.2",
"jest": "29.3.1",

@owens-ben I need a reproduction repo. Usually this problem is outside of Detox scope, it is just about configuring Jest transformers.


add newly consented experts

add 3 new experts. Fix an incorrect URL.
This fixes #63

I'm going to merge this as minor change


Removed light mode

For users without dark mode on, they saw a crazy white website. Removed light mode for simplicity.
Before

After

Lgtm. Ty for your help.


[Docs] Translate Introducing Meshery page to Spanish

Current State:
The actual documentation is in english.
Desired State:
I want to translate this page: https://meshery.layer5.io/docs/overview to spanish.

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

Hey @jesuslerma  what do you think?

Hey @jesuslerma
Please assign this to me. Thanks

Done @Drake8710


Simplify new

Let’s treat all methods the same way.
That’ll make it easier to fix #82

@termoshtt anything I need to do about the failed check?


Succeed when an origin is defined, but no acl:origin is set

This makes it so that if no acl:origin is defined in the .acl file,
then no check will be done of the origin.
Fixes https://github.com/solid/node-solid-server/issues/994
To be honest, I'm not entirely certain that this is the correct way of doing this.
I'm unable to find anything about a missing acl:origin in the spec.
But this seems a reasonable way of handling this.
The alternative would be to add acl:origin predicates to all .acl files in NSS.

If this is merged, a unit test in NSS will have to be changed.

Actually, this is not the solution, the root here is my understanding that you shouldn't even trust your own origin, since you may have been fooled into installing a malicious web app. This is codified in
https://github.com/solid/node-solid-server/blob/release/v5.0.0/test/integration/authentication-oidc-test.js#L215-L231
However, we have discussed, and we shouldn't make that assumption. Thus, the solution is that we send in the server's origin in trustedOrigins. Can you look into that, and change the above test, @rubensworks ?

Thus, the solution is that we send in the server's origin in trustedOrigins

Ah, that makes sense! Done in https://github.com/solid/node-solid-server/pull/1012


Mull is not mutating the shared object file

The tool is not mutating the shared object file. Here are the details to replicate the behavior.
Details:
valid_age.h
#ifndef MULL_EXAMPLE_H
#define MULL_EXAMPLE_H

int valid_age(int age);

#endif

valid_age.cpp
#include "valid_age.h"

int valid_age(int age) {
    if (age >= 21) {
        return 1;
    }
    return 0;
}

test_valid_age.cpp
#include "mull_example_lib.h"

int main() {
    int test1 = valid_age(25) == true;
    if (!test1) {
        /// test failed
        return 1;
    }

    int test2 = valid_age(20) == false;
    if (!test2) {
        /// test failed
        return 1;
    }

    /// success
    return 0;
}

Commands
clang++ -fPIC -g0 -Wall '-Wno-error=self-assign-overloaded' -fembed-bitcode -g '-std=c++14' -no-canonical-prefixes -Wno-builtin-macro-redefined -c valid_age.cpp -o _objs/valid_age.pic.o
clang++ -shared -o _objs/libvalid_age.so _objs/valid_age.pic.o -pipe '-fuse-ld=lld' -Wl,-z,relro,-z,now,-z,notext -no-canonical-prefixes -pthread -Wl,--push-state -Wl,-as-needed -ldl -lrt -Wl,--pop-state
clang++ -fPIC -g0 -Wall '-Wno-error=self-assign-overloaded' -fembed-bitcode -g '-std=c++14' -no-canonical-prefixes -Wno-builtin-macro-redefined -c test_valid_age.cpp -o _objs/test_valid_age.pic.o
clang++ -o test_valid_age.out '-Wl,-rpath,./_objs' -L./_objs _objs/test_valid_age.pic.o -lvalid_age -pie -pthread -pipe '-fuse-ld=lld' -Wl,-z,relro,-z,now,-z,notext -no-canonical-prefixes -pthread -Wl,--push-state -Wl,-as-needed -ldl -lrt -Wl,--pop-state
mull-cxx \
    --linker="/usr/local/bin/clang++" \
    --mutators="cxx_all" \
    --linker-flags="-Wl,-rpath,./_objs -L./_objs -Wl,-S -fuse-ld=gold -Wl,-no-as-needed -Wl,-z,relro,-z,now -B/usr/bin -lvalid_age -pthread -lstdc++ -lm" \
    --ide-reporter-show-killed \
    --reporters=IDE\
    --print-options \
    --debug \
    test_valid_age.out

Expected Behavior
The tool should mutate both valid_age.cpp and test_valid_age.cpp.
Current Behavior
The tool is only validating test_valid_age.cpp
[info] Killed mutants (4/6):
/home/mull_issue_code/test_valid_age.cpp:5:17: warning: Killed: Replaced call to a function with 42 [cxx_replace_scalar_call]
    int test1 = valid_age(25) == true;
                ^
/home/mull_issue_code/test_valid_age.cpp:5:31: warning: Killed: Replaced == with != [cxx_eq_to_ne]
    int test1 = valid_age(25) == true;
                              ^
/home/mull_issue_code/test_valid_age.cpp:11:17: warning: Killed: Replaced call to a function with 42 [cxx_replace_scalar_call]
    int test2 = valid_age(20) == false;
                ^
/home/mull_issue_code/test_valid_age.cpp:11:31: warning: Killed: Replaced == with != [cxx_eq_to_ne]
    int test2 = valid_age(20) == false;
                              ^
[info] Survived mutants (2/6):
/home/mull_issue_code/test_valid_age.cpp:5:9: warning: Survived: Replaced 'T a = b' with 'T a = 42' [cxx_init_const]
    int test1 = valid_age(25) == true;
        ^
/home/mull_issue_code/test_valid_age.cpp:11:9: warning: Survived: Replaced 'T a = b' with 'T a = 42' [cxx_init_const]
    int test2 = valid_age(20) == false;
        ^
[info] Mutation score: 66%

Versions
mull-cxx
Mull: LLVM-based mutation testing
https://github.com/mull-project/mull
Version: 0.11.2
Commit: a9a8ed6c
Date: 01 Oct 2021
LLVM: 11.0.1

Hi @AlexDenisov, did you have a chance to look at this issue?

Hi @duthades,
After some thinking, I know what's the problem is!
mull-cxx embeds the information about the mutants into the binary itself. In your case, you get the information both in mutated_objs/libvalid_age.so and in the test_valid_age_mutated.out.
Then, mull-runner extracts the information about the mutants from the executable under test.
This means that if the executable has some mutants, mull-runner will only run those mutants (as it didn't extract the info about mutants from the shared library).
The best solution would be to teach mull-runner to also scan all the dependent shared libraries, but it might be a demanding task performance-wise.
As a workaround, I can suggest looking at this tutorial https://mull.readthedocs.io/en/latest/tutorials/NonStandardTestSuite.html.
You may consider the test suite to be a "non-standard" and call mull-runner this way:
mull-runner -ide-reporter-show-killed mutated_objs/libvalid_age.so -test-program=test_valid_age_mutated.out

This way, it will search for mutants at mutated_objs/libvalid_age.so, but will run test_valid_age_mutated.out as a test suite.
The drawback, is that you cannot get mutants for both test_valid_age_mutated.out and mutated_objs/libvalid_age.so in one run. But, as a workaround to that, you can run the tests twice 😄
This is not ideal, but it should do the job.

Hi @AlexDenisov, This workaround is working on the above example code. I was wondering if there is a timeline to implement a feature to automatically scan the dependent shared files for mutations?
This workaround has made the integration of this tool in our pipeline very complex. Here is the psedocode for integeration:
def mutate(target):
    all_mutations = []
    all_shared_libs = get_all_shared_files_for(target)
    for each_lib in all_shared_libs:
        linker_flags = get_linker_flags(each_lib)
        compiler_flags = get_compiler_flags(each_lib)
        mutate_shared_lib(each_lib, linker_flags, compiler_flags)
        mutated_lib = get_mutated_lib_for(each_lib)
        all_mutations.append(check_mutation_status(mutated_lib, target))
    return all_mutations

Finding linker flags and compiler flags is not always straight forward for dependent shared files (we use bazel for building and testing). This way the runtime is also increases by len(all_shared_lib) times.

Hi @duthades, thank you so much for trying and confirming that the workaround actually works!
I can certainly see the pain with this solution.
I cannot provide an ETA for the proper fix, but this is certainly an important problem to solve - I simply overlooked this user case when I initially implemented it.
I'll see how much effort it'd take and will get back to you soon.

Hi @AlexDenisov, I have noticed one more issue while testing. When I modify valid_age.cpp to use static variable. For example:
#include "valid_age.h"

int valid_age(int age) {
  static int lower_limit = 21;
  if (age >= lower_limit) {
        return 1;
    }
    return 0;
}

When I try to mutate this shared object file using the following commands:
clang++ -fPIC -g0 -Wall '-Wno-error=self-assign-overloaded' -fembed-bitcode -g '-std=c++14' -no-canonical-prefixes -Wno-builtin-macro-redefined -c valid_age.cpp -o _objs/valid_age.pic.o
clang++ -shared -o  _objs/libvalid_age.so _objs/valid_age.pic.o -pipe '-fuse-ld=lld' -Wl,-z,relro,-z,now,-z,notext -no-canonical-prefixes -pthread -Wl,--push-state -Wl,-as-needed -ldl -lrt -Wl,--pop-state
mull-cxx --disable-junk-detection --debug --linker="/usr/local/bin/clang++" --mutators="cxx_all" --linker-flags="-shared -fPIC -pipe -fuse-ld=lld -Wl,-z,relro,-z,now,-z,notext -no-canonical-prefixes -pthread -Wl,--push-state -Wl,-as-needed -ldl -lrt -Wl,--pop-state" --mutate-only -output=_mutated_objs/libvalid_age.so  _objs/libvalid_age.so

Mull throws following error:
...
[info] Link mutated program (threads: 1)
[error] Cannot link program
status: Failed
time: 36ms
exit: 1
command: /usr/local/bin/clang++ -shared -fPIC -pipe -fuse-ld=lld -Wl,-z,relro,-z,now,-z,notext -no-canonical-prefixes -pthread -Wl,--push-state -Wl,-as-needed -ldl -lrt -Wl,--pop-state /tmp/mull-8ef324.o -o _mutated_objs/libvalid_age.so
stdout:
stderr: ld.lld: error: relocation R_X86_64_32S cannot be used against local symbol; recompile with -fPIC
>>> defined in /tmp/mull-8ef324.o
>>> referenced by valid_age.cpp:5
>>>               /tmp/mull-8ef324.o:(cxx_assign_const:/home/mull_issue_code/valid_age.cpp:6:9)

ld.lld: error: relocation R_X86_64_32S cannot be used against local symbol; recompile with -fPIC
>>> defined in /tmp/mull-8ef324.o
>>> referenced by valid_age.cpp:5
>>>               /tmp/mull-8ef324.o:(cxx_assign_const:/home/mull_issue_code/valid_age.cpp:8:5)

ld.lld: error: relocation R_X86_64_32S cannot be used against local symbol; recompile with -fPIC
>>> defined in /tmp/mull-8ef324.o
>>> referenced by valid_age.cpp:5
>>>               /tmp/mull-8ef324.o:(cxx_ge_to_gt:/home/mull_issue_code/valid_age.cpp:5:13)

ld.lld: error: relocation R_X86_64_32S cannot be used against local symbol; recompile with -fPIC
>>> defined in /tmp/mull-8ef324.o
>>> referenced by valid_age.cpp:5
>>>               /tmp/mull-8ef324.o:(cxx_ge_to_lt:/home/mull_issue_code/valid_age.cpp:5:13)

ld.lld: error: relocation R_X86_64_32S cannot be used against local symbol; recompile with -fPIC
>>> defined in /tmp/mull-8ef324.o
>>> referenced by valid_age.cpp:5
>>>               /tmp/mull-8ef324.o:(cxx_init_const:/home/mull_issue_code/valid_age.cpp:6:9)

ld.lld: error: relocation R_X86_64_32S cannot be used against local symbol; recompile with -fPIC
>>> defined in /tmp/mull-8ef324.o
>>> referenced by valid_age.cpp:5
>>>               /tmp/mull-8ef324.o:(cxx_init_const:/home/mull_issue_code/valid_age.cpp:8:5)

ld.lld: error: relocation R_X86_64_32S cannot be used against local symbol; recompile with -fPIC
>>> defined in /tmp/mull-8ef324.o
>>> referenced by valid_age.cpp:5
>>>               /tmp/mull-8ef324.o:(cxx_remove_void_call:/home/mull_issue_code/valid_age.cpp:3:19)

ld.lld: error: relocation R_X86_64_32S cannot be used against local symbol; recompile with -fPIC
>>> defined in /tmp/mull-8ef324.o
>>> referenced by valid_age.cpp:5
>>>               /tmp/mull-8ef324.o:(mull__Z9valid_agei_original)
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

[error] Error messages are treated as fatal errors. Exiting now.

Hi @duthades, thank you so much for trying and confirming that the workaround actually works!
I can certainly see the pain with this solution. I cannot provide an ETA for the proper fix, but this is certainly an important problem to solve - I simply overlooked this user case when I initially implemented it.
I'll see how much effort it'd take and will get back to you soon.

@AlexDenisov did you have any chance to estimate effort? And probably an rough ETA for the fix?

@duthades the issue is that Mull doesn't respect certain compiler flags when lowering bitcode to the machine code.
#929 contains a fix that you can test by installing the "right" version (0.13.0-pr929 in this case).
Let me know if it works for you, then I'll cut the release soon.

Hi @AlexDenisov, I compiled and installed mull with this PR changes for llvm 11. This change did not show mutated shared libs. I used the code and command from this comment - https://github.com/mull-project/mull/issues/903#issue-1031458236 with --lower-bitcode flag and without. Am I missing anything?

@duthades my latest comment only addresses the issue with the -fPIC, the original issue with the missing mutants from shared libs is not yet fixed.
Or did I misunderstand your message?

@AlexDenisov I got it now. I misunderstood your comment earlier. I tried to run the new mull tool using the code with static variable and commands from https://github.com/mull-project/mull/issues/903#issuecomment-972882621. The tool was able to mutate successfully now. :)

@duthades #931 is supposed to fix the original issue. Please, feel free to reopen the issue if the issue is still there.
Regarding the rest (specifically https://github.com/mull-project/mull/issues/903#issuecomment-970325368), we are working on a clang plugin that would allow more seamless build system integration (at least we hope so).


Create schule.txt

@MastercodingR I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host schule.fbs-ffm.de not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Bugfix Jenkinsfile

Submisison Checklist

[ ] Run tests: ./runCmdStanTests.py src/test
[ ] Declare copyright holder and open-source license: see below

Summary:
When the build is not a PR, Jenkins would compare the changes with the same branch resulting in 0 changes. This is because on a merge when comparing current commit with develop, develop already contains the commit.
Jenkins will now use HEAD^1 commit to see what changed since last commit.
Intended Effect:
How to Verify:
Side Effects:
Documentation:
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

You are right, good catch. I'm on it.
Just to double-check, changes should always be compared with develop on downstream_tests right ?

I think so yes. Downstream tests only have the changed submodule reference compared to the develop branch.


initialize engine in async.go

why initialize engine in async.go, when import this package will auto initialize engine instance.Is it better?

Just for a quick start to use, if user wants to try it. We can offer two options, user can choose the inner default engine, or they can create one.

I understand,thank you.


Fix Error in get-logs request LogEvent instance is not JSON serializable

When an user request get-log-events commands returns next error:
TypeError: <moto.logs.models.LogEvent instance> is not JSON serializable
Fixed bug with new list of dictionary attributes from LogEvent Object

@jorgemarcial Great fix! Thanks for this

This is now released as Moto 1.1.24


[Zone Decommission] Add route to get decommission status for particular attribute

https://github.com/opensearch-project/OpenSearch/pull/4261#discussion_r983785299

Completed in #4751


Pass cookies when renewing access token

Is it possible to include cookies in the request when any request (such as access token renewal) is sent? It should be possible by passing { credentials: 'include' } to fetch function, but currently it's not possible to specify extra settings to fetch.

related to #608


Is the flow chart present at https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/plan-conditional-access correct?

Hello
I was going through conditional access documentation (https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/plan-conditional-access) and the decision flowchart present in the page is not making sense to me. Could be that I understand it wrong, but I would expect that if "Access control BLOCK conditions satisfied" is true, then the access token would not be issued. But the flowchart seems to imply the opposite. When result is "No" says the flowchart then token is not issued.
Anyway, I am not yet familiar enough with CA, so this could be a misunderstanding on my side.
Hope someone will have a look into this.
Best,
Celio

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 1e4eb266-d556-29dd-8c22-1b0221a048a7
Version Independent ID: 3b4c4a89-85a8-5948-3ad2-efc7459945c2
Content: Plan an Azure Active Directory Conditional Access deployment - Microsoft Entra
Content Source: articles/active-directory/conditional-access/plan-conditional-access.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @Gargi-Sinha
Microsoft Alias: gasinh

@Celio-Rossy
Thanks for your feedback! We will investigate and update as appropriate.

@Celio-Rossy
I understand your confusion. The flowchart in the documentation you mentioned is a bit confusing. You are correct that if the "Access control BLOCK conditions satisfied" is true, then the access token would not be issued. The flowchart seems to imply the opposite. When the result is "No," it means that the access token is not issued.
In general, Conditional Access policies are evaluated when a user attempts to access a resource. If the conditions of the policy are met, the user is either granted or denied access to the resource. If the user is granted access, an access token is issued. If the user is denied access, no access token is issued.
I hope this helps clarify your understanding of Conditional Access policies. Let me know if you have any further questions.

@YashikaTyagii
Thanks for the follow-up.
I think I understood under what conditions the user would be granted access to the resource (i.e. the access token is issued).
However something still does no add up after your explanation. If the "No" was supposed to mean "the access token is not issued", then the result on "CA policies are in scope of request" condition is incorrect. The flowchart says an access token is issued.
If the "No" and "Yes" do represent the result of the condition described in the diamond shape, then the "No" and "Yes" attached to "Access control BLOCK conditions satisfied" are the opposite of what they should be.

@Celio-Rossy
Yes, you are correct, and it seems document need to be updated. I am going to assign this issue to content author who will update accordingly.
@Gargi-Sinha  kindly take a look at this case.

Tagging @MicrosoftGuyJFlo , our Content Dev for Conditional Access to help with this review. Thanks!

Hi @Gargi-Sinha , has the flow chart been pushed to public space? I still see the old chart when browsing the documention.

Removing diagram at issue until @Gargi-Sinha can republish.


Add new ap-east-1 region

Source: https://aws.amazon.com/blogs/aws/now-open-aws-asia-pacific-hong-kong-region/ .
Example of how we added a region previously: https://github.com/rusoto/rusoto/pull/1248 .

Done!


App does not display any default text on screen when offline, to inform users that the list is empty or out of date.

d3ee702 addresses this issue


kubectl commands need a --config

kubectl commands need a "--config kubeconfig" in order for ReadMe instructions to work.  Readme instructions such as:
./kubectl cluster-health
don't work unless I append --config, such as
./kubectl cluster-health --config./kubeconfig

hey good catch. I think when we wrote these instructions up we had already moved the kubeconfig to the default location of $HOME/.kube/config


Could not delete path

Error:Execution failed for task ':react-native-maps:processReleaseResources'.

java.io.IOException: Could not delete path 'C:\Users**\node_modules\react-native-maps\lib\android\build\generated\source\r\release\android\support'.

I got the same error after changing the react-native's load version from 0.5.4 to 0.4.9 to resolve an issue with a topTouch error, now nothing works, going back to 5.4 where at least I get a compiled version.

Fixed it by running npm start -- --reset-cache (And following the Android Installation guide

@christopherdro can close

I'm having similar error. Can the issue be reopened?
...
:lottie-react-native:generateReleaseBuildConfig FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':lottie-react-native:generateReleaseBuildConfig'.
> java.io.IOException: Could not delete path 'D:\myPATH\myApp\node_modules\lottie-react-native\src\android\build\generated\source\buildConfig\release\com'.

@LuisRizo  Instead of reset cache every time the best way is go to that particular folder and give it full access that one worked for me

npm watchman watch-del-all
its worked for me.
RN version-0.55.2

i was facing the same problem in my project what i did was i deleted the build project in the file explorer and then did 'rebuild' in the android studio and it worked perfectly for me

@AAKIBZ  but it will work for one time next time you have to do same things I did back track on buildToolsVersion it was working but after some time again facing the same issue not getting exactly what happening If any one have better solution please provide .... Thanks in advance

If you want you can change gradle build directory using below script so you can delete all build files at once.
allprojects {
    buildDir = "${rootProject.rootDir}/.build/${project.name}"
}


Is there a way to change the colorscheme after it's been set?

In my vimrc I'll set the colorscheme:
let g:lightline = { 'colorscheme': 'solarized' }

then depending on the light or dark mode of the os the colorscheme may be updated:
let g:lightline = { 'colorscheme': 'PaperColor' }

lightlines colors don't change even when it updates information displayed.
Could you advise or suggest a way to trigger lightline to update its colors?

Please call call lightline#init() and then call lightline#colorscheme().

Thanks, that works!


Docker install fails with error at Composer/SimpleSAML Step

I've found this Dockerfile very useful as an exercise in learning Docker and in the process get my head around simpleSAML.  I started with the Docker image available on the Docker hub which saved a lot of time in debugging my iDP.
I did hit a problem when trying to create my own Dockerfile, and then later discovered that the problem exists here also, so it wasn't just my simpleSAML newbie status.
When running the install the Composer step that performs the simpleSAML install fails now, presumably due to changes in simpleSAML dependencies since this script was created.
Here is the output showing the problem
Step 28 : RUN php composer.phar install
 ---> Running in b2c6110c2f1d
PHP Warning:  Module 'mcrypt' already loaded in Unknown on line 0
PHP Warning:  Module 'mcrypt' already loaded in Unknown on line 0
Running composer as root/super user is highly discouraged as packages, plugins and scripts cannot always be trusted
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested PHP extension ext-pdo_sqlite * is missing from your system. Install or enable PHP's pdo_sqlite extension.

The command '/bin/sh -c php composer.phar install' returned a non-zero code: 2

This may be all that is needed to fix this
Add to Dockerfile before the Composer run
RUN apt-get install -y  php5-sqlite

@paulfreeman much appreciated.
I added this in and it's all good.


chore(memberType): Use GuildMemberManager#resolve instead of Guild#member

Guild#member is getting removed in v13 so replace it with GuildMemberManager#resolve.

@Gawdl3y ?


[BEAM-701] AvroIO.Write: minor doc and test fixes

Document the default codec.
Swap the order of assertEquals in tests to match the expected pattern (expected, actual).

@ravwojdyla take a look? I did not make you do this busywork, but I wanted to get this in before I backport this functionality to Dataflow.
NB: because it's a behavior change, I will be setting the default to uncompressed for Dataflow.

Sorry missed this 👍


A11y view iframe doesn't include scrolling="no"

Just noticed this after somehow triggering something to scroll (just by keyboard navigation) during testing:

The usual solution would be to put scrolling="no" in the iframe (as we should have for basically every iframe pointing to a sim).

Implemented, closing.


I am currently unable to install platformio-ide-terminal on atom

[ x] I have reset Atom to defaults prior to submitting report.
[ x] I have not reset Atom to defaults prior to submitting report.
<I am currently unable to install platformio-ide-terminal on atom because it is showing:

npm ERR! code Z_BUF_ERROR
npm ERR! errno -5
npm ERR! zlib: unexpected end of file
npm ERR!      C:\Users\Dell.atom.apm_logs\2020-10-24T04_38_55_927Z-debug.log>

> atom --version:atom 1.52.0

> apm --version: apm  2.5.2

OS name and version: windows 10
Platformio-ide-terminal version:
Additional Information

Fixed in https://github.com/platformio/platformio-atom-ide-terminal/releases/tag/v2.10.1
Please update platformio-ide-terminal to the latest version.


Add flag to allow bypass of MIDI enabling on sampler

Enabling midi on sampler instance is not always desirable. If you have MIDI chain with MIDI effects, the sampler should receive transformed events and not the original ones.
This preserves backwards compatibility by defaulting to shouldEnableMIDI to true

Absolutely yes! Thank you!