Regression in main bundle size.

🐞 Bug report
Command (mark with an x)

[x] build

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Description
When I build my app with version 11.0.7, this is the initial bundle:

Initial Chunk Files
Names
Size

polyfills.e360d1535f100e4f0e96.js
polyfills
50.76 kB

runtime.e3a55ec346089bacde1e.js
runtime
4.32 kB

styles.f34419b46f4c8397f83c.css
styles
1.10 kB

main.4b155e348e7d074cc7b0.js
main
1.03 kB

Initial Total
57.20 kB

When I upgrade to 11.2.2, this is the initial bundle:

Initial Chunk Files
Names
Size

main.a68ac17a3ee7b04b27c1.js
main
304.40 kB

polyfills.ab27ff871f3f289a1bbd.js
polyfills
50.76 kB

runtime.6298cce722c648ea2baf.js
runtime
4.14 kB

styles.f34419b46f4c8397f83c.css
styles
1.10 kB

Initial Total
360.40 kB

That is a 359Kb size increase of main.js
🔬 Minimal Reproduction
npx<EMAIL_ADDRESS>new MainBundleIssue

In the new app, update main to:
(async () => {
  const { enableProdMode } = await import('@angular/core');
  const { platformBrowserDynamic } = await import('@angular/platform-browser-dynamic');
  const { AppModule } = await import('./app/app.module');
  const { environment } = await import('./environments/environment');

  if (environment.production) {
    enableProdMode();
  }

  platformBrowserDynamic()
    .bootstrapModule(AppModule)
    .catch((err) => console.error(err));
})();

then build and notice the main bundle size
after that, ng update @angular/cli @angular/core
Build and notice the increased bundle size.

This bootstrapping code was actually never supported. In fact, pre version 11.1, when using @angular/platform-browser-dynamic would cause for it not to be replaced with @angular/platform-browser when using AOT compilation.
The former is used to bootstrap JIT applications.
Before
/*!*********************!*\
  !*** ./src/main.ts ***!
  \*********************/
/*! no static exports found */
/***/ (function(module, exports, __webpack_require__) {

"use strict";

var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
    return new (P || (P = Promise))(function (resolve, reject) {
        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
        step((generator = generator.apply(thisArg, _arguments || [])).next());
    });
};
(() => __awaiter(void 0, void 0, void 0, function* () {
    const { enableProdMode } = yield __webpack_require__.e(/*! import() | angular-core */ "default~angular-core~angular-platform-browser-dynamic~app-app-module").then(__webpack_require__.bind(null, /*! @angular/core */ "fXoL"));
    const { platformBrowserDynamic } = yield Promise.all(/*! import() | angular-platform-browser-dynamic */[__webpack_require__.e("default~angular-core~angular-platform-browser-dynamic~app-app-module"), __webpack_require__.e("default~angular-platform-browser-dynamic~app-app-module"), __webpack_require__.e("angular-platform-browser-dynamic")]).then(__webpack_require__.bind(null, /*! @angular/platform-browser-dynamic */ "a3Wg"));
    const { AppModule } = yield Promise.all(/*! import() | app-app-module */[__webpack_require__.e("default~angular-core~angular-platform-browser-dynamic~app-app-module"), __webpack_require__.e("default~angular-platform-browser-dynamic~app-app-module"), __webpack_require__.e("app-app-module")]).then(__webpack_require__.bind(null, /*! ./app/app.module */ "ZAI4"));
    const { environment } = yield __webpack_require__.e(/*! import() | environments-environment */ "environments-environment").then(__webpack_require__.bind(null, /*! ./environments/environment */ "AytR"));
    if (environment.production) {
        enableProdMode();
    }
    platformBrowserDynamic()
        .bootstrapModule(AppModule)
        .catch((err) => console.error(err));
}))();

/***/ })

In 11,.1, with the new Ivy plugin system, a non dynamic import is added and the bootstrapping code is change to use ``@angular/platform-browser`, so in this case the transformer is doing a better job, but has the side-effect that this import is not dynamic.
After
/*!*********************!*\
  !*** ./src/main.ts ***!
  \*********************/
/*! no exports provided */
/***/ (function(module, __webpack_exports__, __webpack_require__) {

"use strict";
__webpack_require__.r(__webpack_exports__);
/* harmony import */ var _angular_platform_browser__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__(/*! @angular/platform-browser */ "jhN1");

var __awaiter = (undefined && undefined.__awaiter) || function (thisArg, _arguments, P, generator) {
    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
    return new (P || (P = Promise))(function (resolve, reject) {
        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
        step((generator = generator.apply(thisArg, _arguments || [])).next());
    });
};

(() => __awaiter(void 0, void 0, void 0, function* () {
    const { enableProdMode } = yield Promise.resolve(/*! import() */).then(__webpack_require__.bind(null, /*! @angular/core */ "fXoL"));
    const { platformBrowserDynamic } = yield __webpack_require__.e(/*! import() | angular-platform-browser-dynamic */ "angular-platform-browser-dynamic").then(__webpack_require__.bind(null, /*! @angular/platform-browser-dynamic */ "a3Wg"));
    const { AppModule } = yield __webpack_require__.e(/*! import() | app-app-module */ "app-app-module").then(__webpack_require__.bind(null, /*! ./app/app.module */ "ZAI4"));
    const { environment } = yield __webpack_require__.e(/*! import() | environments-environment */ "environments-environment").then(__webpack_require__.bind(null, /*! ./environments/environment */ "AytR"));
    if (environment.production) {
        enableProdMode();
    }
    _angular_platform_browser__WEBPACK_IMPORTED_MODULE_0__["platformBrowser"]()
        .bootstrapModule(AppModule)
        .catch((err) => console.error(err));
}))();

To disable the above behaviour you can do is to replace the @angular/platform-browser-dynamic import manually in your code.
(async () => {
  const { enableProdMode } = await import('@angular/core');
- const { platformBrowserDynamic } = await import('@angular/platform-browser-dynamic');
+ const { platformBrowser } = await import('@angular/platform-browser');
  const { AppModule } = await import('./app/app.module');
  const { environment } = await import('./environments/environment');

  if (environment.production) {
    enableProdMode();
  }

-   platformBrowserDynamic()
+   platformBrowser()
    .bootstrapModule(AppModule)
    .catch((err) => console.error(err));
})();

Using dynamic imports, can cause optimization bailouts which will result in larger bundle sizes. in general I don't think that the above is a common good practice to support as users might user the above pattern without fully understanding the consequences.
Seeing that the above pattern is not recommended and there is a workaround for your problem I think it's best not to take action. To support the above pattern, the transformer code will need to be extended to handle this use-case, which few people would benefit from.

@alan-agius4 The provided code is an example of what happens. It's not coding that is used as-is in production code.
The reasons for having a minimal main bundle:

startup performance
make booting angular code optional (especially in SSG this will come in handy)
More control over how the app is bundled,
Start-up light-weight alternatives to angular in SSG

I think those do outweigh the current optimization bailout. Also, optimization bailout is a tooling artifact, and while important, it should not be leading in how to architect an application.  When tooling matures, it will start picking up on those patterns.
Thanks for explaining the platform vs platformDynamic, the workaround works, and I don't need JIT in most of my apps anyway.
However, I think there needs to be a broader discussion around this. Perhaps this issue isn't the place for that.  Feel free to close this issue when there is a better place to discuss this!

Following our offline convo.
This is also related to why we use FESM's instead of ESM. https://github.com/angular/angular-cli/issues/13635 (When not using FESM there would be a size increase of ~5Kb on an ng new app).
While I do see that the benefit for SSG, there are some cavets, the underlying tooling struggles to optimize when having a lot of files (Webpack and Terser). In the above case the initial size of the application more than doubles in size with an increase of about ~240Kb.
Keep tooling in mind when architecting your application is also important IMHO similarly to when you intend to HMR or SSR, if you do want to successfully use such features you need to keep these in mind when architecting your application. Eventually when tooling does support your desired architecture you can update it.
Currently, I don't see as there is anything actionable from our end since this is a limitation of how underlying tools work and expects the JavaScript input. If you do find that such optimization bailout are acceptable for you, there is nothing which is stopping you from using the above bootstrapping code.  I do however suggest the above to be used with caution a period analysing of your bundle as overtime you might end up retaining a lot of unused code in your chunks.
Cross chunk optimization is something high on our wishlist as well. Feel free to reach out on Slack to discuss this more.


[backport] Skip some Convolution2D tests for older numpy versions

Backport of #8458

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 26ef78e904040b65ba976bb503b9635efb0892f2, target branch v6) failed with status FAILURE.


Does not work microk8s.helm3 plugins install

Microk8s was installed by using snap on ubuntu 18.04.4
# snap install microk8s --classic microk8s (1.18/stable) v1.18.3 from Canonical✓ installed
Then enabled Helm3
# microk8s.enable helm3 Enabling Helm 3 Fetching helm version v3.0.2.   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100 11.5M  100 11.5M    0     0  1692k      0  0:00:06  0:00:06 --:--:-- 2272k Helm 3 is enabled
After that - trying to install diff plugin for helm - no luck
# microk8s.helm3 plugin install https://github.com/databus23/helm-diff --version master Error: Unable to get repository: Cloning into '/home/user/.cache/helm/plugins/https-github.com-databus23-helm-diff'... /usr/lib/git-core/git-remote-https: relocation error: /lib/x86_64-linux-gnu/libnss_dns.so.2: symbol __res_context_search version GLIBC_PRIVATE not defined in file libresolv.so.2 with link time reference : exit status 128
The same problem with other plugin
# microk8s.helm3 plugin install https://github.com/chartmuseum/helm-push Error: Unable to get repository: Cloning into '/home/user/.cache/helm/plugins/https-github.com-chartmuseum-helm-push'... /usr/lib/git-core/git-remote-https: relocation error: /lib/x86_64-linux-gnu/libnss_dns.so.2: symbol __res_context_search version GLIBC_PRIVATE not defined in file libresolv.so.2 with link time reference : exit status 128
No differences if you run installation under root or user
inspection-report-20200602_082429.tar.gz

I have a similar error trying to install helm plugins on Ubuntu 20.04
#sudo microk8s.helm3 --debug plugin install https://github.com/databus23/helm-diff --version master
[debug] cloning https://github.com/databus23/helm-diff to /root/.cache/helm/plugins/https-github.com-databus23-helm-diff Error: Unable to get repository: Cloning into '/root/.cache/helm/plugins/https-github.com-databus23-helm-diff'... /usr/lib/git-core/git-remote-https: symbol lookup error: /usr/lib/git-core/git-remote-https: undefined symbol: curl_global_sslset, version CURL_GNUTLS_3 : exit status 128 helm.go:76: [debug] Unable to get repository: Cloning into '/root/.cache/helm/plugins/https-github.com-databus23-helm-diff'... /usr/lib/git-core/git-remote-https: symbol lookup error: /usr/lib/git-core/git-remote-https: undefined symbol: curl_global_sslset, version CURL_GNUTLS_3 : exit status 128

i got the same error
microk8s helm3 plugin install https://github.com/hayorov/helm-gcs.git

Error: Unable to get repository: Cloning into '/root/.cache/helm/plugins/https-github.com-hayorov-helm-gcs.git'...
/usr/lib/git-core/git-remote-https: symbol lookup error: /usr/lib/git-core/git-remote-https: undefined symbol: curl_global_sslset, version CURL_GNUTLS_3
: exit status 128

@Izopi4a which revision of MicroK8s are you using?

I am not sure if this is the correct way to check for the version
izopi4a@server:~$ microk8s ctr version
Client:
  Version:  v1.3.7
  Revision: 8fba4e9a7d01810a393d5d25a3621dc101981175

Server:
  Version:  v1.3.7
  Revision: 8fba4e9a7d01810a393d5d25a3621dc1019811

// I missed my email sorry for the delay.

I'm having the same problem.
Ubuntu 20.10
Microk8s v1.20.5
$ microk8s.helm3 plugin install https://github.com/salesforce/helm-starter.git
Error: Unable to get repository: Cloning into '/home/stone/.cache/helm/plugins/https-github.com-salesforce-helm-starter.git'...
/usr/lib/git-core/git-remote-https: symbol lookup error: /usr/lib/git-core/git-remote-https: undefined symbol: curl_global_sslset, version CURL_GNUTLS_3
: exit status 128

Still not fixed in the latest microk8s
$ microk8s.helm3 --debug plugin install https://github.com/databus23/helm-diff
[debug] vcs_installer.go:159: cloning https://github.com/databus23/helm-diff to /home/zhuhaow/.cache/helm/plugins/https-github.com-databus23-helm-diff
Error: Unable to get repository: Cloning into '/home/zhuhaow/.cache/helm/plugins/https-github.com-databus23-helm-diff'...
/usr/lib/git-core/git-remote-https: symbol lookup error: /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_pthread_init, version GLIBC_PRIVATE
: exit status 128
helm.go:84: [debug] Unable to get repository: Cloning into '/home/zhuhaow/.cache/helm/plugins/https-github.com-databus23-helm-diff'...
/usr/lib/git-core/git-remote-https: symbol lookup error: /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_pthread_init, version GLIBC_PRIVATE
: exit status 128

$ microk8s version
MicroK8s v1.29.0 revision 6364

I am also getting:
Error: Unable to get repository: Cloning into '/root/.cache/helm/plugins/https-github.com-databus23-helm-diff'...", "/usr/lib/git-core/git-remote-https: symbol lookup error: /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_pthread_init, version GLIBC_PRIVATE


kill() or a simple unbind() method.

Hi there,
in my use case i need to unbind the jQuery.tipsy() plugin or the hover effect who was setted up by tipsy(). The problem is the configuration in tipsy().
Please implement a simple unbind method:
jQuery('selector').tipsyUnbind();
Greets,
Marc

@seekshreyas disabling the tooltip is not the same as removing it. Ideally, tipsy would have something like .tipsy('destroy') that would unbind and remove the tooltip entirely.


initial draft of a Task class

This draft Task class (see #42) is derived from the Cirrus task template: https://github.com/cirrus-geo/cirrus-task-template

I was creating a new task for Cirrus, so I decided to just expand on the Task class here and get a working version.
I've also added a task example in the tests directory that show a basic copy task, now far simpler than having all the previous boilerplate.

As you know I really like this idea. I wish I had more time to review and test out some of my thoughts, but here's a couple high-level comments:

I think the base class here is not Task, but Lambda, and Task should be a subclass of Lambda. Then we'd also have Feeder and Function subclasses. I say that because things like logging, event parsing, and args/cli functions would be common across all of these "lambda" types.
I would look into using the __init_subclass__ method on that base Lambda class to register the handler method as the function lambda_handler within the subclass's module. I might have this totally wrong, but it could be something like this:

    def __init_subclass__(cls, abstract=False, **kwargs):
        super().__init_subclass__(**kwargs)
        if abstract:
            return
        module = cls.__module__
        module.lambda_handler = cls.handler

Good point on having another base class, although I really don't like calling it Lambda though, because this Task would be used for Batch as well.  So not sure what to call the base class, but like the idea of having one and then adding a Feeder class (which also does not need to be a Lambda).

In my mind this was only for use for tasks within a cirrus project, i.e., for things packaged as a lambda. But you're suggesting it could be used for tasks built into docker containers as well? I suppose that makes sense.
Then maybe we want to have a LambdaHandler mixin that does the handler registration, and we could expose both a Task and TaskLambda class? Or perhaps a Lambda class decorator that does the registration?
I don't know what is best here, I just want to make sure it is super easy for a task author to ensure the task class will actually work with the default lambda definition.yml config.

Oh I see, I was wondering what the value was with the registration.   But yeah, you could use the Task class when creating a new Batch task as well, it provides the CLI for local testing and all the wrapping/fetching/parsing/payload return.
We could also change the default generated definition.yml file for new tasks to not use lambda_function.lambda_handler, which as you know I've never cared for.

I suppose cirrus could import the .py file in the component dir to inspect it to see if it has a subclass of the base (whatever we're calling it), an explicit lambda_handler definition, or any other patterns we would consider supporting here. This seems a little more "magic" than I'd normally like, because it comes from a build-time inspection and isn't something you can "see" externally, but advantage over the current just-set-a-default approach is that we could error the build command if no handler is set in the definition.
I guess we also need to know what .py file to import; that could be handled in a similar discovery-with-error process as above.
Though we also have to consider with the lambda-as-batch runner, to make sure whatever is set here is compatible with the patterns it supports. If we are actually modifying the module state on class instantiation to set a well-known lambda_handler value, then we get that compatibility for free.
Also, maybe setting lambda_handler in the module namespace isn't a problem for batch-only applications. So perhaps we don't need different behavior for lambda vs not.

@jkeifer The testing error is also happening in your PR #46 , which is in the transfer tests.  Any idea what could be happening here?

I added some tests, although there are still failing tests from test_transfer unrelated to these additions

Codecov Report

Merging #43 (599e3a2) into main (64f7cd1) will decrease coverage by 0.18%.
The diff coverage is 63.88%.

@@            Coverage Diff             @@
##             main      #43      +/-   ##
==========================================
- Coverage   69.77%   69.59%   -0.19%
==========================================
  Files           5        6       +1
  Lines         622      763     +141
==========================================
+ Hits          434      531      +97
- Misses        188      232      +44

Impacted Files
Coverage Δ

src/cirrus/lib/task.py
63.88% <63.88%> (ø)

src/cirrus/lib/utils.py
67.08% <0.00%> (-0.42%)
:arrow_down:

src/cirrus/lib/process_payload.py
50.42% <0.00%> (-0.21%)
:arrow_down:

src/cirrus/lib/statedb.py
87.00% <0.00%> (-0.07%)
:arrow_down:

src/cirrus/lib/transfer.py
88.23% <0.00%> (+9.41%)
:arrow_up:

Continue to review full report at Codecov.

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

I was trying to fix the tests, started changing from mocking to vcr when I updated all the dev dependencies and the tests all work now.   So ready for review so we can get this merged into main @jkeifer

This work has been replaced by new library stac-task


[Python] Recognizers-text - Add emoji as required dependency

Fixes ISSUE 1740
Description
When running some test methods from a file with a reference to recognizers-text after installing this package directly (i.e, by using the pip install command instead of the build.cmd file), and without having the emoji package installed in your environment, the next error will be prompted:

In order to fix this, it's necessary to add emoji as a requirement in the setup.py file.
Reproduce ISSUE
For reproducing the current ISSUE, follow these steps without the changes performed in this PR:

Ensure that emoji is not installed in your environment
Add a reference to recognizers-text in, for example, test_initialization_number_with_unit_recognizer.py file:

Manually install the recognizers-text package using pip install -e .\libraries\recognizers-text
Run the test methods from the file where you added the reference to recognizers-text package with the command pytest. The next error will be prompted:

Changes made

Add emoji as a requirement in the setup.py file.
Remove emoji from the requirements.txt file.

Testing
Using this PR's changes, follow the next steps:

Add a reference to recognizers-text in, for example, test_initialization_number_with_unit_recognizer.py file
Manually install the recognizers-text package using pip install -e .\libraries\recognizers-text. In this case, you will see that the emoji package is being installed:

Run the test methods from the file where you added the reference to recognizers-text (pytest tests\test_initialization_number_with_unit_recognizer.py). The test successfully pass:

Replaced w/ PR 1750


Cannot unroll identity matrix of more than 2 qubits when coupling_map is set

Information

Qiskit Terra version: 0.14.1
Python version: 3.8
Operating system: both Windows and Linux

What is the current behavior?
The transpile function fails to unroll an UnitaryGate containing an identity matrix of more than 2 qubits when the backend argument is set to be a remote quantum computer or the coupling_map argument is set.
Steps to reproduce the problem
>>> import numpy as np
>>> from qiskit import IBMQ, QuantumCircuit, transpile
>>> from qiskit.extensions import UnitaryGate
>>> provider = IBMQ.load_account()
>>> backend = provider.get_backend('ibmq_london')  # arbitrary backend with at least 3 qubits
>>> circuit = QuantumCircuit(3)
>>> gate = UnitaryGate(np.eye(2 ** 3))
>>> circuit.append(gate, range(3))
<qiskit.circuit.instructionset.InstructionSet object at 0x7ff8b93a60d0>
>>> transpile(circuit, backend=backend)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.8/dist-packages/qiskit/compiler/transpile.py", line 210, in transpile    circuits = parallel_map(_transpile_circuit, list(zip(circuits, transpile_args)))
  File "/usr/local/lib/python3.8/dist-packages/qiskit/tools/parallel.py", line 105, in parallel_map
    return [task(values[0], *task_args, **task_kwargs)]
  File "/usr/local/lib/python3.8/dist-packages/qiskit/compiler/transpile.py", line 306, in _transpile_circuit
    return pass_manager.run(circuit, callback=transpile_config['callback'],
  File "/usr/local/lib/python3.8/dist-packages/qiskit/transpiler/passmanager.py", line 214, in run
    return self._run_single_circuit(circuits, output_name, callback)
  File "/usr/local/lib/python3.8/dist-packages/qiskit/transpiler/passmanager.py", line 277, in _run_single_circuit
    result = running_passmanager.run(circuit, output_name=output_name, callback=callback)
  File "/usr/local/lib/python3.8/dist-packages/qiskit/transpiler/runningpassmanager.py", line 115, in run
    dag = self._do_pass(pass_, dag, passset.options)
  File "/usr/local/lib/python3.8/dist-packages/qiskit/transpiler/runningpassmanager.py", line 145, in _do_pass
    dag = self._run_this_pass(pass_, dag)
  File "/usr/local/lib/python3.8/dist-packages/qiskit/transpiler/runningpassmanager.py", line 157, in _run_this_pass
    new_dag = pass_.run(dag)
  File "/usr/local/lib/python3.8/dist-packages/qiskit/transpiler/passes/basis/unroll_3q_or_more.py", line 54, in run
    decomposition = self.run(decomposition)  # recursively unroll
  File "/usr/local/lib/python3.8/dist-packages/qiskit/transpiler/passes/basis/unroll_3q_or_more.py", line 54, in run
    decomposition = self.run(decomposition)  # recursively unroll
  File "/usr/local/lib/python3.8/dist-packages/qiskit/transpiler/passes/basis/unroll_3q_or_more.py", line 39, in run
    raise QiskitError("Cannot unroll all 3q or more gates. "
qiskit.exceptions.QiskitError: 'Cannot unroll all 3q or more gates. No rule to expand instruction circuit9_dg.'

Notes:

This bug only happens when the backend argument is set to be a remote quantum computer or the coupling_map argument is set to be a coupling map of a remote quantum computer. Calling transpile(circuit, basis_gates=['u1', 'u2', 'u3', 'cx', 'id']) works fine.
This bug only happens when the UnitaryGate contains an identity matrix of more than 2 qubits.

What is the expected behavior?
Successfully transpile the circuit.

Hi I think I'm getting a similar error
QiskitError: "Cannot unroll the circuit to the given basis, ['u0', 'u1', 'u2', 'u3', 'cx', 'x', 'y', 'z', 'h', 's', 't', 'snapshot']. Instruction id not found in equivalence library and no rule found to expand."
when I'm using the qiskit-jku-provider. It occurs when I try to execute the job with backend=jku_backend

Hi I think I'm getting a similar error
QiskitError: "Cannot unroll the circuit to the given basis, ['u0', 'u1', 'u2', 'u3', 'cx', 'x', 'y', 'z', 'h', 's', 't', 'snapshot']. Instruction id not found in equivalence library and no rule found to expand."
when I'm using the qiskit-jku-provider. It occurs when I try to execute the job with backend=jku_backend

Hi @EziOzoani , that error is raised because the circuit being transpiled contains an identity gate, but the backend does not report that it can implement an identity gate ('id' is not in the backend's basis_gates). The transpiler won't remove identity gates (id ) as they're generally left for the backend to decide how to implement (IBMQ backends, for example, have traditionally implemented id gates as an implicit delay, though this behavior will be removed in the future).
One option is to remove the id gates from your circuit before running it, or you can open an issue on the JKU provider suggesting the id gate be implemented. Feel free to reach out on the Qiskit Slack if you have further questions.


Improve Avatar Readme

Need to improve this component on \Avatar\Readme.md
Improvements required :
Update the images in the images in readme of Avatar
Any reference image?
Currently its not displaying image of any component
To fix it just copy paste the code of each component in https://play.tailwindcss.com/ and take screenshot of proper aspect ration, host the image on any free image hosting websites update the link

Any external reference?
You can checkout this one for better understanding.

I want to contribute, please assign it to me

I want to contribute, please assign it to me

Go Ahead

I want to contribute..

@RavindraP04  I updated it , now it is working properly ,I checked it on  https://play.tailwindcss.com/ .You can now merge it to main branch after rechecking from your end . I did it under diversion 2k23.


Hot bug fix

Details of Feature/Bug

Short title
Description
Dependencies (if any)

List of changes

change a
change b

Database migration/schema changes (if any)

List your migrations here...

Self review checklist

[ ] Ran all the tests locally to check that you have not introduced any new regression.
[ ] Followed coding and styling guidelines. Checked for ESLint fixes.
[ ] Checked for any dependencies and updated them.
[ ] Made sure to add the comments where required.
[ ] Added the PR link to the ticket assigned.
[ ] Make sure you have updated (if necessary)-

[ ] Documentation (if any)
[ ] Noted version number
[ ] Added the label in the PR
[ ] Created release notes

Additional info (if any)

Add anything you feel worth mentioning...

This is a redundant PR


Using FlatBuffers

https://google.github.io/flatbuffers/ looks like more simple Procol Buffers alternative. Does it worth to use it instead?

Our existing indexers already use Protobuf in some form or the other, so introducing yet another format needs to have substantial benefit to justify the cost of migration: https://sourcegraph.com/search?q=context:global+repo:github.com/sourcegraph/.%24+file:.%5C.proto%24&patternType=standard&sm=1&groupBy=repo
The main touted benefits of FlatBuffers are:

(De-)Serialization performance: This is good enough with Protobuf. For deserialization, yes you can technically operate on the data directly, but the Sourcegraph backend bits ingesting the data would need non-trivial refactoring (and would likely become less ergonomic to work with) for questionable gain.
Code size: This has not been a problem with Protobuf.


bin/next not found and compiled/arg/index.js not found

I'm using the next.config.js option outpout: 'standalone' and its not copying the following module:
'next/dist/bin/next'
So I added it just to see if I can get it working, but bin/next requires this missing module:
'next/dist/compiled/arg/index.js'
what do I do?
My build is running github actions, if that helps. I'm copying missing modules from my local node modules to the production environment but it keeps going. ../lib/commands is also missing, then ../cli/next-start.

If you are using Next.js, please create an issue in the https://github.com/vercel/next.js repo and provide the steps to reproduce the problem, thanks!


Salt issue

Hey there,
I've got not much time to look up into that problem but i just wanted to let you know - there must be something wrong with storing generated salt or something, because SHA-1 of correctly entered PIN (after defining&confirming correctly, then second app launch) does never match the one entered before on my test device.

I agree, I came across this issue as well. Confirmed the PIN numbers and then upon invoking the lock screen, the confirmed number failed to unlock the app.

@mseroczynski @BlacKCaT27
Hummm I remember a pull request made a while ago, the tests were passing but it seems that a regression is present on the library.
I'll try fixing it in the next revisions, otherwise just fix the Salt in AppLockImpl.java instead of generating a random one.

You should not use line feed symbols in SharedPrefs (maybe this is an issue https://code.google.com/p/android/issues/detail?id=159799), also your salt is too big, there is no reason to use salt length more than 256 bit with the same key length.


Fix: delete multiple entities

Deleting grades removes them from student groups and leaves those student groups invalid.


ppocr INFO: In PP-OCRv3, rec_image_shape parameter defaults to '3, 48, 320', if you are using recognition model with PP-OCRv2 or an older version, please set --rec_image_shape='3,32,320

Please fill in the information below so that we can solve the problem quickly, Thanks !
Describe the bug
While executing 'predict_system.py'  I have set the rec_image_shape parameter as rec_image_shape='3,32,320'. But even after specifying the value for the parameter system is still not able to recognize the value
Informations (please complete the following information):

Inference engine for deployment: CPU (windows)
Why convert to onnx：ONNX is already implemented so to use the additional functionality
Paddle2ONNX Version: paddle2onnx==1.0.6
Email/Wechat/Phone: NA

Screenshots:

Additional context: issue is not only observed for paddle2onnx but also observed for paddle.
The command which I have executed is given below:
python -m predict_system.py --use_gpu=False
--cls_model_dir=./inference/ch_ppocr_mobile_v2.0_cls_infer
--rec_model_dir=./inference/en_PP-OCRv3_rec_infer
--det_model_dir=./inference/en_PP-OCRv3_det_infer
--image_dir=doc/imgs_en/img_12.jpg
--rec_char_dict_path=ppocr/utils/en_dict.txt
--rec_image_shape='3,32,320'
(Note: I have also tried giving the shape in different but the issue  still persists. --rec_image_shape="3,32,320",
--rec_image_shape "3,32,320", --rec_image_shape 3,32,320

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

I am facing same issue, have you solved it ?

I am facing same issue, have you solved it?


Imgur WebException 400 Bad Request

It appears perhaps there is a size limit. I can upload my gif manually to imgur, but it won't finish processing, I just get a blank image, and no error message and it works eventually (I spoke too soon).
My gif is 100MB...

There's a limit. It's supposed to be 10MB for images or 200MB for videos.
https://apidocs.imgur.com/#c85c9dfc-7487-4de2-9ecd-66f727cf3139

The uploader logic was updated for v2.28.
The upload should be more stable.
Imgur limits the upload of gifs to less than 10Mib.


Question:  Copy/Paste To/From Clipboard

Hello
Similar to Electron that has APIs to Copy/Paste and Context Menus, does Tauri have clipboard support?

Not yet, but we'll have it when the new bindings are used, #846
Context menus might take a while though, it needs support on webview/webview or our custom window management, #837

Thanks Lucas@, would you therefore agree that for copy/paste clipboard, I should implement in front-end, like if I use Angular then implement as much as it can there?

Yeah so the only issue I see is that the support on Windows is incomplete: https://github.com/webview/webview/pull/405
Maybe we should ship our own implementation? what do you think @nothingismagick

Well, the thing I think our clipboard should do under all circumstances is have a purging method. I mean, after this whole iOS scandal and the general insecurity of the clipboard, I'd like to have a secure paste pattern that allows the dev to control the paste buffer. I'm thinking of chainable things like paste.toText which sanitizes html, paste.thenPurge which clears the clipboard.

The new WRY system does allow for copy & paste on macos. Closing as resolved

good to know this works! maybe update the home page too since it's still marked as planned

So is the clipboard now supported on all operating systems? Definitely update the home page!!! I almost decided to stop my investigation into using Tauri until I found this issue through Google!

Still not working for me on MacOS, tauri 1.0.0-beta.8

@Janaka-Steph on macOS you need a window menu to support copy/past (and more), did you add one?
If not, here's an example: https://github.com/probablykasper/mr-tagger/blob/master/src-tauri/src/main.rs#L28-L78

@Janaka-Steph on macOS you need a window menu to support copy/past (and more), did you add one?
If not, here's an example: https://github.com/probablykasper/mr-tagger/blob/master/src-tauri/src/main.rs#L28-L78

No I don't have a menu. Why is it related? :/

Well, that's just how things work on macOS (not tauri specific) 🤷


[WIP] Feat/prism

Prototype for Prism object
Overall folder/file structure

comparators: Contains the basic logic to compare different type of results. Comparators can be a function of the result container type, and potentially the evaluators

comparator.py: abstract class
metric_comparator.py: takes a list of Lens objects, extract metric containers and compares metrics across all the Lens objects. Comparisons are done respect to a reference Lens object. Currently the reference is defined by model name, to be changed in the future if necessary. @esherman-credo I simplified the logic, the all vs all comparison produced a lot of results that were probably not going to get used, we can reinstate it if needs be. I have added the possibility to select different operations.

compare.py: this is a type of task that prism can orchestrate. ATM it's only calling metric_comparator, in the future compare.Compare will instantiate the necessary comparators (table, metric, etc...) depending on the existing results containers.

prism.py: the orchestrator, this is the equivalent of Lens but at a higher level. The purpose of Prism is to coordinate the various tasks.  Currently when the user instantiates it, they can pass a dictionary of tasks to perform on the Lens objects. The dictionary is in the format {'task_name:{'parameter':value}}, where parameters are specific to the type of task to perform.

Missing

Docstrings in general
Abstract classes for task objects (like compare.Compare). I haven't created an abstract class for this yet, I am wondering if there is a need for it, or if the variety of the object will be too big for an abstract class to be useful.
Tests

To test the run you can use the following code:

from credoai.lens import Lens
from credoai.artifacts import TabularData, ClassificationModel
from credoai.evaluators import *
from credoai.governance import Governance
import numpy as np

# imports for example data and model training
from credoai.datasets import fetch_creditdefault
from sklearn.ensemble import RandomForestClassifier
from sklearn.model_selection import train_test_split
from xgboost import XGBClassifier

data = fetch_creditdefault()
df = data["data"]
df["target"] = data["target"].astype(int)

# fit model
model1 = RandomForestClassifier(random_state=42)
X = df.drop(columns=["SEX", "target"])
y = df["target"]
sensitive_features = df["SEX"]
(
    X_train,
    X_test,
    y_train,
    y_test,
    sensitive_features_train,
    sensitive_features_test,
) = train_test_split(X, y, sensitive_features, random_state=42)
model1.fit(X_train, y_train)

model2 = XGBClassifier(tree_method='hist', random_state=42, n_estimators=2, enable_categorical=True)
model2.fit(X_train, y_train)

# ## Set up artifacts

credo_RF1 = ClassificationModel(
    'credit_RF1_classifier',
    model1
)

credo_XGB = ClassificationModel(
    'credit_XGB_classifier',
    model2
)

train_data = TabularData(
    name = "UCI-credit-default-train",
    X=X_train,
    y=y_train,
    sensitive_features=sensitive_features_train
)
test_data = TabularData(
    name='UCI-credit-default-test',
    X=X_test,
    y=y_test,
    sensitive_features=sensitive_features_test
)

# pipeline scan be specifed using a sklearn-like style
metrics = ['accuracy_score', 'roc_auc_score']
pipeline = [
    (Performance(metrics)),
    (ModelFairness(metrics)),
]

pipeline2 = [
    (Performance(metrics)),
    (ModelFairness(metrics)),
]

# and added to lens in one fell swoop
lens_rf1 = Lens(
    model=credo_RF1,
    assessment_data=test_data,
    # training_data=train_data,
    pipeline=pipeline
)

lens_xgb = Lens(
    model=credo_XGB,
    assessment_data=test_data,
    # training_data=train_data,
    pipeline=pipeline2
)

from credoai.prism import Prism

prism_test = Prism(
    [lens_rf1, lens_xgb],
    tasks={'compare':{'ref':'credit_RF1_classifier'}}
)

prism_test.execute()

prism_test.get_results()

@IanAtCredo Overall responses to the high level critique:

I feel like the compare.py class is unneeded and can be rolled into Prism. Happy to discuss and be wrong here though.

Initially I was of the same opinion, however I feel we need this kind of objects due to the variety of tasks that Prism will have to handle in the future (not just comparisons). If everything gets put into Prism I feel it will eventually ballon up pretty quickly. I intended for Prism to only handle orchestration logic, including the translation from user input into the tasks to perform.
This is based mostly on feeling at the moment, I would like to create a sampling task following this schema and see how we feel about it at the end.

The way a reference is defined and IDed is not flexible enough. Only works for cross-model comparisons, when really we want cross "context" comparisons. If the same model is run on different samples of data, we may want to compare those.

Agreed,  this was meant as a temporary solution. I think Data/Model/SensitiveFeature define the context ATM, I wonder what is the best way of conveying this information. The simplest is a combo of Model_Name + Data_Name + Feature_Name/Value, this will get ugly pretty fast.
Potential solution: leverage PepelineStep -> Create a context property which is a function of metadata, and which associate a hash to the step. In my mind each step coincides with a context.  All Prism tasks will use hashes for internal referencing (this makes creating DF easier, rather than having to move around Dictionaries).
We can create a couple of Prism methods that can then translate to/from human readable output/input.

The user interface of Prism, which is supposed to simplify everything, instead obfuscates.
Documentation needed for most functions (though easy to follow anyway)

Agreed, I wasn't extremely happy about it either. We can ask the user to pass the actual (task) class, like Compare. So the param tasks in Prism will be something like this:
[
 {
   task: Compare,
   params: {ref: ...}
 },
]

another argument to keep the task objects 😛 . In any case, whether we map user input string to behavior, or we pass tasks directly, a certain amount of knowledge is necessary on user side.
Stylistically this is more similar to what we are currently doing in Lens when we build the pipeline.

Few thoughts:
Why does the user need to specify tasks at all? Or at the level of granularity you are describing? Why not just "here are a few models, either aggregate or compare them". I can buy that if you say "aggregate them", implicitly a list of tasks are created, but should that be the main way the user interacts? Perhaps some super-user will want specific access to the tasks (which we can allow), but that's secondary to the primary user interaction.
Data/Model/SensitiveFeature as context - yeah. I think we may want to define this somewhere. I was originally thinking that a run of Lens is the context. Why do we need to infer the context? Can't we just say "we took a bucket of what you said was one thing and compared it to another." To generalize this to evidence separated from Lens is trickier within your current implementation, but could be done by a list of evidence-lists, rather than inferring separation by IDs.

@IanAtCredo Update:

Formalized the concept of Task
Updated method of passing tasks to Prism, same logic as for passing evaluators to Prism
Updated PipelineStep to create a unique id for each step dependent on Evaluator name, model name, datasets names, sensitive feature.
Update comparator task and metric comparators to leverage the new id to match evidences for comparisons


Fix chart resizing issue (#7297)

Fix #7297

Haven't got much free time these days, could you please help add some basic tests? Or I can try add them 2-3 weeks later (Have some on-call duties these weeks)

We can wait a couple weeks. I'm afraid we're all pretty busy too

It should quite straight forward to add to those tests:
https://github.com/chartjs/Chart.js/blob/00f726b0eaeeaad177ded228a00cb4c4e0c9e529/test/specs/core.controller.tests.js#L306

Due to some strange error I cannot do unit testing on Windows 10 + Chrome, so I just updated original branch and see if CI will help do the unit testing.

It looks like the test is not useful. Chrome and Firefox pass it on master. Running tests on Edge fails with "ResizeObserver is not defined".

I don't have much background about this repo so I just simply copied another test and do some slightly changes, with methods also used in other tests, not sure if this would hit 'ResizeObserver is not definederror. As for the code itself, I didn't change/useResizeObserver's ctor or any property, just modified its callback, so if ResizeObserver` is not defined in Edge, I guess it would be a long-existing issue, rather than introduced by my change.
BTW, as Microsoft is pushing updates to all Windows 10 devices to replace (not side-by-side) their old Edge with Chromium-based Edge, I guess it might need to support new Edge and drop support for old Edge.

@yhvicey no worries! The ResizeObserver issue is not related to this.
I'll dig around a bit more on how to test this specific issue. I would be impossible for you, if you can't run the tests locally.

All my old Edge browsers have been replaced with new Edge already lol
As for the Chrome, I have no idea why it fails with below errors:
Error: 'import' and 'export' may only appear at the top level
ERROR You need to include some adapter that implements __karma__.start method!

Will try on another dev machines later, if I got some free time then.

ok, here is a test that fails on master and succeeds on this pr:
		fit('should restore the original size when parent became invisible', function(done) {
			var chart = acquireChart({
				options: {
					responsive: true,
					maintainAspectRatio: false
				}
			}, {
				canvas: {
					style: ''
				},
				wrapper: {
					style: 'width: 300px; height: 350px; position: relative'
				}
			});

			waitForResize(chart, function() {
				expect(chart).toBeChartOfSize({
					dw: 300, dh: 350,
					rw: 300, rh: 350,
				});

				var original= chart.resize;
				chart.resize = function() {
					fail('resize should not have been called');
				};

				var wrapper = chart.canvas.parentNode;
				wrapper.style.display = 'none';

				setTimeout(function() {
					expect(wrapper.clientWidth).toEqual(0);
					expect(wrapper.clientHeight).toEqual(0);

					expect(chart).toBeChartOfSize({
						dw: 300, dh: 350,
						rw: 300, rh: 350,
					});

					chart.resize = original;

					waitForResize(chart, function() {
						expect(chart).toBeChartOfSize({
							dw: 300, dh: 350,
							rw: 300, rh: 350,
						});

						done();
					});
					wrapper.style.display = 'block';
				}, 200);
			});
		});

the description is exactly same with the test i've added, but the code doesn't looks the same.

Yeah, I started with your test, but it passed in master. So I've modified it quite a bit.

Here's some more info about the ResizeObserver issue: https://github.com/chartjs/Chart.js/issues/7341

Oh, I think I got your meaning. Do you want me to modify the test to make it passable in my PR but failed on master, to make sure it covered the issue?


some corrections related to font size

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main--world-bank--aemsites.hlx.live/
After: https://home-bugs--world-bank--aemsites.hlx.live/

Incorporate these changes. Pls check @thomsebastin


Avoid re-downloading the cookiecutter template if it's already downloaded

Currently, briefcase always re-downloads the cookiecutter template.
Since re-generating an application bundle (for example, running python setup.py ios or python setup.py android) is meant to be a very common thing to do, it would be nice if it tolerate network issues.
My suggestion is that we check if there is a template already downloaded, and if it does, instead of re-cloning it, we'd try updating it (running git pull) and just emit a warning in case updating fails.

Btw, not sure if this will need special handling, but the update shouldn't be tried if one specifies --template.

Resolved by #39


Assignment Manager

Moves everything assignment-related (trail, levels, decisions, etc.) and the clause storage into separate classes.

For the future: it is necessary to decide the fate of trail, level value and other methods and fields that were moved from the Solver (CDCL class) into Assignment manager-class. We could leave the delegating methods/fields in CDCL, how it is currently done for value method (though, this was left only because value method is a part of public interface). Or we could just use assignment.*** (assignment.trail, assignment.decisionLevel, etc) everywhere. Currently, the latter is implemented/used.


ROX-25852: Sensor sends collector runtime config to collector

Description

This is a part of an epic to give users the ability to configure collector runtime features. In a previous PR the collector runtime config was added to the cluster config protobuf definition. This means that it can be set using the PUT cluster service API endpoint, and when that is done the configuration is sent to the correct sensor. This PR makes it such that when sensor receives the cluster configuration, the collector part of it is sent to collector.
There is another PR that makes it so that collector is able to receive the configuration. That PR is still in draft form. https://github.com/stackrox/collector/pull/1810
The version of collector in that PR is used for testing to confirm that sensor is sending the configuration to collector.
User-facing documentation

[ ] CHANGELOG is updated OR update is not needed
[ ] documentation PR is created and is linked above OR is not needed

Testing and quality

[ ] the change is production ready: the change is GA or otherwise the functionality is gated by a feature flag
[ ] CI results are inspected

Automated testing

[ ] added unit tests
[ ] added e2e tests
[ ] added regression tests
[ ] added compatibility tests
[ ] modified existing tests

How I validated my change

Set ROX_COLLECTOR_RUNTIME_CONFIG to true. Deployed ACS using this branch. Set the cluster config with the following script
!/usr/bin/env bash
set -eou pipefail

ROX_ENDPOINT=${1:-localhost:8000}

clusters_json="$(curl --location --silent --request GET "https://${ROX_ENDPOINT}/v1/clusters" -k --header "Authorization: Bearer $ROX_API_TOKEN")"

cluster_id="$(echo "$clusters_json" | jq -r '.clusters[0].id')"

input_file=delete_temp.josn
echo "$clusters_json" > "$input_file"

cluster_put="$(jq -s '.[0].clusters[0].dynamicConfig.collectorConfig = .[1]' "$input_file" collector_config_5.json | jq '.[0].clusters[0]' | jq 'del(.id)')"

curl --location --silent --request PUT "https://${ROX_ENDPOINT}/v1/clusters/$cluster_id" -k --header "Authorization: Bearer $ROX_API_TOKEN" --header "Content-Type: application/json" --data "$cluster_put"

Where collector_config_5.json has the following contents
{
  "processConfig": {
    "enabled": true
  },
  "networkEndpointConfig": {
    "enabled": true,
    "includeListeningEndpointProcesses": true
  },
  "networkConnectionConfig": {
    "enabled": true,
    "aggregateExternal": true
  },
  "namespaceScopeConfig": [
    {
      "feature": {
        "networkConnection": {
          "enabled": true,
          "aggregateExternal": false
        }
      },
      "namespaceSelection": [
        {
          "namespace": "marketing.*",
          "matchType": "REGEX"
        },
        {
          "namespace": "namespace1",
          "matchType": "EXACT"
        }
      ]
    }
  ]
}

This script gets the cluster configuration by calling the API, adds a collector config to it, makes a few other minor changes, and then sets the cluster config using the API endpoint. The collector logs were checked and in each log something like the following was found.
[INFO    2024/09/24 22:19:01] In Receive
[INFO    2024/09/24 22:19:01] Before switch
[INFO    2024/09/24 22:19:01] [runtime-control::Service] Receive: CollectorRuntimeConfig
[INFO    2024/09/24 22:19:01] Before Update
[INFO    2024/09/24 22:19:01] process_enabled= 1

This means that the collectors got the configuration.
The collector pods were then deleted and allowed to come back up using
ks delete pod -l app=collector

The above script was run again and the collector logs where checked again. This was done multiple times and each time the logs confirmed that the config was set using the API, that all collectors received it. Collector also received the config multiple times when it was sent multiple times, without restarting collector.

It is a bit of a mess, but I would like feedback on it. I started out by thinking that I would simply build upon the code that already exists for sending the cluster config to admissioncontrol. I didn't fully understand the code and ended up making some changes to the code I wrote to send the original collection based configuration to collector. How could I move towards leveraging the existing code for sending the configuration to admissioncontrol to send the configuration to collector? According to the logs sensor is sending the configuration to collector, but the version of collector that is supposed to receive the configuration crashes soon after starting up. This is not a result of the configuration being sent to collector.

Closing as the existing networkflows code will be used to send the configuration. The new PR is at https://github.com/stackrox/stackrox/pull/12826


Xamarin and VSMonoDebugger

Hello, it's a known issue that debugging Xamarin app doesn't work when VSMonoDebugger extension is enable. I would like to know if this issue is going to be fixed in the future. Sometime I'm trying to debug a Xamarin app and I forgot to disable the extension and I need to relaunch Visual Studio. It is a little bit annoying. Thank you.

I have tried this very often, but have always failed due to the dependency injection of Visual Studio. Therefore the dependency to Mono.Debugging.VisualStudio.4.9.10-pre is still available.
See Readme in directory Mono.Debugging.VisualStudio.4.9.10-pre

Could you try this with the new extension VSMon Debugger 2022 in Visual Studio 2022? If I have time I could try to port the new Xamarin debugger call to VSMonoDebugger.


Changed type of id of adaptation set to double

Fixes https://github.com/androidx/media/issues/485

Closing (see discussion in https://github.com/androidx/media/issues/485)


VELPITAR - Incorrect county in the job listings on "peviitor.ro"

ENVIRONMENT: production
URL: https://scrapers.peviitor.ro/
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open the url
Type "velpitar" in search field
Press on search button
Click on "Run Scraper" button
Click on "See jobs"
Check the county of the jobs

EXPECTED RESULTS:
In the job listings from "peviitor.ro", for the city "Iași" we expected to see the county "Iași"
ACTUAL RESULTS:
In the job listings from "peviitor.ro" we see the village "Iași" and the county "Brașov"
ATTACHMENTS:

fixed can you retest?

Retested ✅


unsigned

Your extension is unsigned. Today, it is blocked in Firefox 62.0. Can you get it signed?

I don't know what you mean, it's hosted on AMO, which does the signing:
https://addons.mozilla.org/en-US/firefox/addon/resurrect-pages/

(And I'm currently using it, in FF 62.)

You are right. I did have a problem. After updating your extension, it
worked again. An, yours wasn't the only one. It must be a problem with my
profile. Sorry to have bothered you!
Thanks for helping me 😀
Carl
On Wed, 12 Sep 2018, 15:12 arantius<EMAIL_ADDRESS>wrote:

(And I'm currently using it, in FF 62.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/arantius/resurrect-pages/issues/37#issuecomment-420642659,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApM3dwYhIzBYNaRroCxg6ojIo8mZJYZTks5uaQgogaJpZM4Wk8QC
.


@JsonProperty annotation reads wrong class attribute

I tried to use Angular's FormControl and FormGroup inside my models, but strangely json2typescript do not linked the attribute just after the annotation.
For example I have this implementation:
    @JsonProperty("id", String)
    private _id: string = undefined;

    public get id(): string {
        return this._id;
    };
    public set id( id: string) {
        this._id = id;
    };
    private _id$: FormControl = new FormControl('', [
        Validators.required,
        Validators.minLength(8),
        Validators.maxLength(15)
    ]);

so when I call serialize() method on this model, strangely the result will be like this: { id: FormControl ....... }
I created a live stackblitz example to see the issue and it contains also my light modification to avoid this wrong behaviour. See the console for the result.
https://stackblitz.com/edit/angular-8z7dxm

That is very strange and looks like a bug. Thanks for your submission.

Have you figured out if this is really a bug or some other issue?

I think you can safely close this; if you update the json2typescript dependency in the provided stackblitz example to current (1.4.1 at this time), the error is gone.

I think you can safely close this; if you update the json2typescript dependency in the provided stackblitz example to current (1.4.1 at this time), the error is gone.

Thanks for the heads up!


Nacos added appender error

detail see https://github.com/alibaba/nacos/issues/11781

I need more information.  Preferably with reproducible code and config.

@philsttr
https://github.com/ncc0706/spring-boot-logstash.git

The error messages that you have highlighted do not look related to logstash-logback-encoder.
The error messages look related to the appenders defined in naco-logback.xml.
I can reproduce the same error messages without using logstash-logback-encoder by replacing this:
        <appender name="LOGSTASH" class="net.logstash.logback.appender.LogstashTcpSocketAppender">
            <destination>${logstashHost}</destination>
            <encoder charset="UTF-8" class="net.logstash.logback.encoder.LogstashEncoder"/>
        </appender>

with this
        <appender name="LOGSTASH" class="ch.qos.logback.core.ConsoleAppender">
            <encoder>
                <pattern>%m</pattern>
            </encoder>
        </appender>

Since I can reproduce the error messages you see without using logstash-logback-encoder, I do not believe the error messages are caused by logstash-logback-encoder.

You can set debug="true" in your logback-spring.xml to help debug.
<configuration scan="false" debug="true">

Thanks, this is a bug in Nacos.
-Dnacos.logging.default.config.enabled=false


Delta 4 Config

Committing genesis files pushed to S3.
Updated pull_genesis.sh to point to S3 URL.
Funding Faucet, N0, N1, N2, Medha, and bitgo.
Bonding N0, N1, bitgo.
My expectation is bitgo will move over to the more stable Delta.

bors merge

bors try

bors r+

bors r-


Support events not containing an installation

This is the case of ping for instance but also of various web hooks.
Note that in this case, you can't get an installation client:

The injected GitHub client will be the very limited application one (I'm even wondering if I should prevent people from using it)
The GraphQL client cannot be injected.

For anything advanced, you will have to create your own GitHub client with a token.

Documentation to come once @ebullient has approved it works for her use case.

100% on me having to make my own GitHub client, no worries.
Will have a go with this.


Deployment pipeline

On master branch update: deploy to internal dev cluster

@Arthelon please fix the inconsistent name in workflow definition (GCE_ZONE vs GKE_ZONE)

@Arthelon please use the use project in GKE_PROJECT secret to setup the cluster credentials.


remove comments from production minified output

remove comments from production output through terser plugin

using terserOptions for terser plugin
we can remove comments from dev as well? what do you think?

    --comments [filter]         Preserve copyright comments in the output. By
                                default this works like Google Closure, keeping
                                JSDoc-style comments that contain "@license" or
                                "@preserve". You can optionally pass one of the
                                following arguments to this flag:
                                - "all" to keep all comments
                                - a valid JS RegExp like `/foo/` or `/^!/` to
                                keep only matching comments.
                                Note that currently not *all* comments can be
                                kept when compression is on, because of dead
                                code removal or cascading statements into
                                sequences.

Are you disabling this? This is a potential legal issue for Next.js users as you are required to include the licenses somewhere.

@timneutkens This was actually inspired by CRA and, also I see that I can get rid of few KBs from production bundle.
By default, terser-webpack-plugin removes comments except license, preserve, cc_on.
If we need to keep the licensing kinds of stuff, then we can disregard this PR.

@timneutkens do you really need those licensing info? Can we take inspiration from CRA?

I'm going to check this at a later point, as per my concerns I have to verify it.

I'm going to close this PR as the reduction would be minimal compared to the potential legal issues.


Add github workflow to build and upload chipdb

This will build the chipdb for each new commit to the master branch and upload it as a github artifact . Not sure if that is a bit redundant, but at least it runs automatically whenever stuff changes.
An example run of this can be seen in https://github.com/kbeckmann/apicula/actions/runs/193110067
The reason to why I changed ADD to RUN curl.. is so that it gets cached. Docker will download the files every single time the container is built otherwise.

I updated the URL for the GW1NR-9 pinout file, since the old URL returned 0 bytes. I guess this means that it has been updated, which is the reason to why the tools don't work with it anymore with the new file.

Updated the PR with new URLs. Builds GW1NR-9 fine now. Example artifacts: https://github.com/kbeckmann/apicula/actions/runs/193294274

Amazing!


Q: Why doesn't von mises distributions wrap around [-pi, pi]?

I am trying to get a Von Mises probability density function whose mean is set parametrically (The ultimate aim is to build a kernel density estimation).
It seems that scipy's Von Mises pdf does not wrap around [pi, pi] if loc is different from 0. E.g.
import matplotlib.pyplot as plt
from scipy.stats import vonmises
x = np.linspace(-np.pi, np.pi)
mean = 2.  # abritrary mean parameter
y = vonmises(kappa=1., loc=mean).pdf(x)
plt.plot(x, y)

Is this expected? If so, how I can retrieve the pdf that wraps in the expected range [-pi, pi]?
Thanks
cc @ev-br

Looks like this is the same issue or at least related to gh-4598.

A structural solution is needed, likely the rv_circular class discussed at https://github.com/scipy/scipy/issues/4598#issuecomment-206548297

That issue does have some discussion on how to fix your problem manually, can you have a look at that?

You're right, it's a duplicate.
However, I didn't understand the possibles fixes, so I just re-implemented the equation with numpy:
from scipy.special import i0
vonmises = lambda x, mu, kappa: np.exp(kappa*np.cos(x-mu))/(2*np.pi*i0(kappa))

Closing as dup, thanks for looking into it @kingjr


[python-package] LGBMClassifier produces empty trees

Description
While exploring the trees produced by LGBMClassifier, it appears that some trees can have only one leaves.
This behavior seems strange as we would expect at least one split for every trees.
Reproducible example
import numpy as np
from sklearn.datasets import load_digits
from lightgbm import LGBMClassifier
np.random.seed(0)

# data | regression | binary | multi class
data_mult = load_digits(as_frame=True)
# Model
model_mult = LGBMClassifier(**{'verbosity': -1, }).fit(data_mult.data, data_mult.target)

for tree in model_mult._Booster.dump_model()["tree_info"]:
    if tree["num_leaves"] == 1:
        print(f"Tree {tree['tree_index']} has only one {tree['num_leaves']} leaf")

Environment info
LightGBM version or commit hash: 4.0.0
Command(s) you used to install LightGBM
pip install lightgbm

Additional Comments
This bug has been found while working on an issue on the SHAP library.

Thanks for your quick return and explanation.
I did not saw that this issue was already explained. It is a duplicated. closing the issue.


test-branch/execute-job/fork-branch/85aad939-dfcb-417b-bc9f-6378b7abcc8a

PR for testing 564a5979d94499156766a426122303a7e7282f68

padding /canonical/self-hosted-runners/run-workflows 564a5979d94499156766a426122303a7e7282f68 padding


winget install terminal not working

Environment
Windows build number: [run "ver" at a command prompt]
PowerToys version:
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

have you installed Winget? You need to install the package manager first! Below is the link to their latest release on Github
https://github.com/microsoft/winget-cli/releases/tag/v0.1.4331-preview

@Namangarg110 is the issue resolved after installing Winget as @saahmedm mentioned above?

yes

thanks for support

@Namangarg110 is the issue resolved after installing Winget as @saahmedm mentioned above?

yes, thanks for the support

I am able to run "winget install terminal" from the command line but not from powertoys run command

did you run it with greater than key and a space right after?  "> winget install terminal" Can you share a screenshot of the command in PT Run

I am able to run "winget install terminal" from the command line but not from powertoys run command

I think I figured it out, I guess the command line commands will not on Linux not windows :)

did you run it with greater than key and a space right after? "> winget install terminal" Can you share a screenshot of the command in PT Run

someone called out the space issue here: #3212 that we'll fix soon.
but for now you need a space after the >

someone called out the space issue here: #3212 that we'll fix soon.
but for now you need a space after the >

Thanks it worked after giving a space after ">"


app.NewCloudControllerManagerCommand additionalFlags not working as expected

Hi,
Poking around with app.NewCloudControllerManagerCommand I noticed additionalFlags argument does not seems to be working as I would expect, while the flag is parsed it is not show in the usage or help.
When an additional flagSet is passed it is parsed, and can be used however it is not shown in the usage or help of the command.
To reproduce, use the following snippet of code:
package main

import (
	"os"

	"k8s.io/apimachinery/pkg/util/wait"
	cloudprovider "k8s.io/cloud-provider"
	"k8s.io/cloud-provider/app"
	"k8s.io/cloud-provider/app/config"
	"k8s.io/cloud-provider/fake"
	"k8s.io/cloud-provider/options"
	kflag "k8s.io/component-base/cli/flag"
	klog "k8s.io/klog/v2"
)

var myFlag string

func main() {

	additionalFlags := kflag.NamedFlagSets{}
	additionalFlags.FlagSet("myFlagSet").StringVar(&myFlag, "abcd", "defaultValue", "n/a")

	opts, err := options.NewCloudControllerManagerOptions()
	if err != nil {
		klog.Fatalf("Failed to create new cloud controller manager options: %v", err)
	}
	opts.KubeCloudShared.CloudProvider.Name = "myProvider"
	home, _ := os.LookupEnv("HOME")
	opts.Kubeconfig = home + "/.kube/config"

	command := app.NewCloudControllerManagerCommand(
		opts,
		cloudProviderInitializer,
		app.DefaultInitFuncConstructors,
		additionalFlags,
		wait.NeverStop,
	)

	if err := command.Execute(); err != nil {
		klog.Fatalf("Failed to execute cloud controller manager command: %v", err)
	}
}

func cloudProviderInitializer(_ *config.CompletedConfig) cloudprovider.Interface {
	klog.Info("abcd flag value is: ", myFlag)
	return &fake.Cloud{}
}

The flag is not shown in the help with the existing cloud controller manager flags, the following command return no results.
$ go run cmd/test/main.go --help |grep abcd

While the flag has been really bound and parsed and can In fact be used.
$  go run cmd/test/main.go --abcd 123456
I0602 19:23:40.055119   44145 serving.go:348] Generated self-signed cert in-memory
W0602 19:23:40.376430   44145 authentication.go:317] No authentication-kubeconfig provided in order to lookup client-ca-file in configmap/extension-apiserver-authentication in kube-system, so client certificate authentication won't work.
W0602 19:23:40.376466   44145 authentication.go:341] No authentication-kubeconfig provided in order to lookup requestheader-client-ca-file in configmap/extension-apiserver-authentication in kube-system, so request-header client certificate authentication won't work.
W0602 19:23:40.376521   44145 authorization.go:193] No authorization-kubeconfig provided, so SubjectAccessReview of authorization tokens won't work.
I0602 19:23:40.381690   44145 main.go:45] abcd flag value is: 123456

It does feel either a bug or an unimplemented feature, while the additional flags are successfully bound in
https://github.com/kubernetes/cloud-provider/blob/9c22fcdc5eab5b9e62f9bdf5dbca07bcbdf6fab5/app/controllermanager.go#L123
The problem seems to be in the the use namedFlagSets which does not contain the additional flags to print he usage and help sections
https://github.com/kubernetes/cloud-provider/blob/9c22fcdc5eab5b9e62f9bdf5dbca07bcbdf6fab5/app/controllermanager.go#L130
https://github.com/kubernetes/cloud-provider/blob/9c22fcdc5eab5b9e62f9bdf5dbca07bcbdf6fab5/app/controllermanager.go#L135
I wouldn't mind having a closer look and propose a fix if one would be accepted, I just wanted to share and get feedback first to ensure this make sense.
Cheers.

I have created https://github.com/kubernetes/kubernetes/pull/112405 with a fix for this which is awaiting for review, feedback is welcomed.


JSON export bugfixes

I was trying to debug my 3MF exporter using to_json, and found a few bugs that tripped it up. These changes fix those, so that running to_json on a loaded male02.obj file now works. No extra tests added, just a few quick tactical fixes that seem fairly obvious.
Incidentally, to_json in other contexts would normally produce a string, whereas this creates a hash which then needs JSON.generate() calling on it. Maybe something to reconsider down the line, what the "correct" output from to_json should be.

The first one, we don't need the metadata on every child object

Great, thanks, I'll update the code :)

I'll revisit this once #125 is merged, to avoid conflicts.

OK, this is good to go now. 🎉
Could merge before or after #125, I'll whichever goes in second.


test(elixir-sdk): Add Elixir to SDK coverage script

The way the SDK coverage script works is it checks for each function listed in extism.h in the source of each SDK,  since the elixir bindings go through Rust the SDK coverage script won't work. I will try to work on an update at some point.

There should be matching elixir code in this native.ex file https://github.com/extism/extism/blob/main/elixir/lib/extism/native.ex
Does that help?
On Oct 25, 2022, 6:58 PM -0500, zach @.***>, wrote:

The way the SDK coverage script works is it checks for each function listed in extism.h in the source of each SDK, since the elixir bindings go through Rust the SDK coverage script won't work. I will try to work on an update at some point.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Actually, after looking at it again, it will still fail (even with the right path) because those functions are missing the extism_ prefix - we could update the sdk coverage script to check with and without the prefix.

@zshipko - good catch...
It looks like maybe we should combine these files to scan (not sure if that's ok in Elixir):
https://github.com/extism/extism/blob/main/elixir/lib/extism/context.ex
https://github.com/extism/extism/blob/main/elixir/lib/extism/plugin.ex
Since https://github.com/extism/extism/blob/main/elixir/lib/extism/native.ex doesn't actually call the runtime APIs.
If the elixir_nif code was updated to include the extism_ prefixes on the Rust functions, and rebuilt/generated, I think the declaration code would have them. Then the Elixir lib stuff above would need to be updated to call the prefixed functions.

Closing for the time being


Remove unnessary memory copy when doing Bzip2 encoding

Motivation:
We did an unessary memory copy when doing bzip2 encoding.
Modifications:
Remove memory copy and just use a ByteProcessor.
Result:
Less memory copies and so faster.

@Scottmitch PTAL

Cherry-picked into 4.1 (9151739)


Is convert MMSeg Pytorch model to ONNX possible with your container?

Hi I'm trying to follow:
https://mmsegmentation.readthedocs.io/en/latest/useful_tools.html

Is convert MMSeg Pytorch model to ONNX possible with your container? Would it be easy to add into the docker build? I'm not sure how to do it. Cheers, Sam
I am also interested in ONNX to TensorRT.
EDIT: I just discovered this which looks useful https://github.com/open-mmlab/mmdeploy

I usually use the models natively rather than exporting them, so not really high on my priority list. Please feel free to do a PR.

The just published docker images for version 0.30.0 (CPU and CUDA 11.1) have ONNX support built-in and script mmseg_onnx for convenience.


Update Jackson

Update jackson based on latest security vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2019-12086

Coverage remained the same at 74.268% when pulling e35fe01009dad3d63daa1cf9e1bd4bbe4f8355f3 on jackson-update into 2afb57fa8f9c161d5098293a36eb06f054dbb31e on develop.


Suggestion: alias 'send' to 'sendText'

Love the simplicity - Zen style - of this solution. I would like to suggest to create an alias to 'sendText' so to be in line with other libraries - they use 'send' as the default for text messages.
It is a minor request but well, I thought to make this suggestion

And in line with this suggestion, to emit('message') instead of ('text') on Connection line 396 - maybe in a new version because it breaks, again is a bit confusing for who is used to work with websockets.
I can appreciate that the development of this module started a while ago (when probably there were no common-uses) but I don't understand why this module is not on the top-lists around the Internet - maybe people like complicated...

Hello @itpmngt
Thank you for taking your time to open this issue.
We may take the idea of aliasing one step further and make it an abstraction over both sendText and sendBinary. That is: send(aString) calls sendText and send(aBuffer) calls sendBinary. What do you think?
For the event name change, I don't think it's worth breaking other people code without a clear benefit. The current terminology was grabbed from the WebSocket spec itself. This module was designed to be a low-level implementation for WS, that's why I think it's good to keep the names similar to the spec (and not much with other implementations).
The simplicity of this module comes from the fact it implements a subset of the WS spec that I find most useful. But one size does not fit all ;)
Regards

Hello sitegui
Yes, a simple send() fits spot on. Feels great.
And I do understand and agree with the 'breaking code' issue regarding 'text' to 'message'
Going into production next week with this WSS - exciting times

As someone who has deployed this package, I would not install a new version
if it broke my existing implementation.
That's the value of a package like this. The standard is stable. It's great
to know that the design of this package was guided by the terminology of
the standard. Keep it that way! :-)
And thanks. It works great for my blog, readers get instant updates as I
make changes to stories. It's like magic to them (and me actually too).
Dave
On Sun, Jan 10, 2016 at 12:34 PM, Joe Rosa<EMAIL_ADDRESS>wrote:

Hello sitegui
Yes, a simple send() fits spot on. Feels great.
And I do understand and agree with the 'breaking code' issue regarding
'text' to 'message'
Going into production next week with this WSS - exciting times
—
Reply to this email directly or view it on GitHub
https://github.com/sitegui/nodejs-websocket/issues/27#issuecomment-170373269
.

Thank you for the feedback guys, released as minor 1.5.0


Refactor and clean-up POM

Fixed indentation.
I must admit that futzing with Maven POMs remains alchemy to me... really not sure if I've done things correctly. Here's the main issue I tried to fix (successfully?):
Shading seems to run twice. First:
[INFO] --- shade:3.5.3:shade (default) @ anserini ---
[INFO] Including org.apache.lucene:lucene-core:jar:9.9.1 in the shaded jar.
[INFO] Including org.apache.lucene:lucene-codecs:jar:9.9.1 in the shaded jar.
...

And runs again:
[INFO] --- shade:3.5.3:shade (shade-jar-with-dependencies) @ anserini ---
[INFO] Including org.apache.lucene:lucene-core:jar:9.9.1 in the shaded jar.
[INFO] Including org.apache.lucene:lucene-codecs:jar:9.9.1 in the shaded jar.
[INFO] Including org.apache.lucene:lucene-backward-codecs:jar:9.9.1 in the shaded jar.
...

I traced it back to the parent POM that we're inheriting from Spring, which runs shading once already. And we run it again.
Removing the parent fixed the issue, but I had to make other adjustments.
In the current state, we fire up the server from the fatjar itself:
java -cp `ls target/*-fatjar.jar` io.anserini.server.Application --server.port=8081

What alerted me to this issue:
https://repo1.maven.org/maven2/io/anserini/anserini/0.35.0/ - anserini-0.35.0.jar: 2.5 MB
https://repo1.maven.org/maven2/io/anserini/anserini/0.35.1/ - anserini-0.35.1.jar: 379 MB
So... something got mangled in the bloat.


HIVE-27824 : Upgrade ivy to 2.5.2 and htmunit to 2.70.0

What changes were proposed in this pull request?
Upgrade ivy to 2.5.2 and htmunit to 2.70.0
Why are the changes needed?
CVE Fixing
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
Yes
How was this patch tested?
Locally built , relying on precommit.

@devaspatikrishnatri I know there are breaking change in htmlUnit 3, but don't you want to try out to update to the latest one? The 2 is a legacy line

@aturoczy I was trying this so as to upgrade ivy to 2.5.2 , as in last attempt there were some problems discovered as mentioned in https://issues.apache.org/jira/browse/HIVE-27849.I am not sure if this will work , but hoping that upgrading both these dependencies won't cause the replication failures as 2.70.0 has some changes related to parsing xmlattributes,
https://htmlunit.sourceforge.io/changes-report.html#a2.70.0.
But , yes will surely try to upgrade html unit to 3.x line , in a separate PR (hoping this feels reasonable).

@SourabhBadhya @deniskuzZ Could you pls merge it if it is acceptable?

@SourabhBadhya Is this run acceptable ?
http://ci.hive.apache.org/job/hive-flaky-check/778/
The tests seems to be passing..

@devaspatikrishnatri Seems good to me. I will proceed with merging.


Assigning Users or Teams as owners or reviewers should be same component and same experience on all pages

Affected module
UI
Describe the bug
Currently we are using multiple ways of assigning a owner or reviewer . We should use a single
module to add a user/team for owner , reviewer or in future in any other place.
We should be using the ES apis to achieve the experience of adding users or teams or list users or teams.
cc @vivekratnavel
As part of this ticket remove any calls to users or teams via apis to bulkload that list on the UI side

Completed!


Allow empty "egress_cidr_blocks"

what

Allow empty egress_cidr_blocks (no egress rules in default security group)

why

Not mandatory to have an egress rule

references

#90

@adamcrews @brcnblc any chance to get some love on this please? :smiley:

@adamcrews @brcnblc any chance to get some love on this please? :smiley:

/rebuild-readme

/test readme

/test all


Is this library still maintained?

This library is widely used but PRs do not seem to be responded to.
If the library is no longer maintained, it would be best if maintainership could be handed over to someone willing to review, merge, and release changes. This is better than forking, which would require new maven coordinates.
Is anyone using the library willing to do maintenance, and are the current maintainers interested in handing over the organisation to a potential maintainer?

I had the same question around half a year ago (before submitting a number of PR myself, to fill in the gaps in the missing functionality of JsonPath). Things haven't been progressing - until late October '21, then something changed and PR's started being reviewed and approved, and code being updated. I guess it will take some time for maintainers to review and approve (or correct / discard) all accumulated PR's ... :-)

This library is very widely used (I don't think it's an exaggeration to call it a bedrock library - here are the users of the latest release) and as far as I can tell, its maintenance depends on a single maintainer, @kallestenflo, so it's completely understandable that things take time. On the other hand, it is incomplete, has performance problems and bugs, and because it's so widely used these things do need fixing in a timely manner. Of course, the source code is available so anybody can fork and release changes, but I don't think that's a good outcome, especially if the fork ends up with a single maintainer who doesn't have the time to be responsive.
So my question is does anybody want to help and can @kallestenflo delegate some of the maintenance burden so things can move faster?

have anyone stepped in and forked the project?


MWPW-143562 - Add "radio" variant to Tabs block

As an author, I want the ability to recreate complex pricing tables like those that previously were created in Dexter. This PR adds a radio variant to the Tabs block to accomplish this -- essentially allowing for tabs within tabs, with an alternate style applied to the inner block.
As the Dexter version of this price table required a full page refresh when switching between Individual/Business tabs, I believe this variant will allow for a much improved user experience.

Resolves: MWPW-143562
Test URLs:

Before: https://main--milo--adobecom.hlx.page/drafts/ebartholomew/pricing?martech=off
After: https://ebartholomew-MWPW-143562-radio-button-group--milo--adobecom.hlx.page/drafts/ebartholomew/pricing?martech=off

Copying over feedback from comments in the Jira ticket, for added clarity. These have all been implemented.
Height should be 56px instead of 50px.
The font should be Body S Bold instead of font-weight of 700.
The gap between the title and the radio button should be XS instead of S.
The gap between the radio button and the text should be 12px instead of 11px.


Spam modes

Renewed discussion about spam reminded me of some thinking we did in this direction a few months back. In particular, one aspect that's interesting to me is: what exactly is spam, is there a line, is it a coninuum?
One illustrative example is Shiv Integer, a bot that uploads programmatically permuted versions of other models on Thingiverse. In this case the output has only been ~300 models, but you can easily imagine this being 300,000. The bot has a legitimate artistic purpose and technically obeys both CC license terms and site ToS. Is it spam?

Update: in Phase II design, shiv integer can write to /shivinteger all they want


Error: @actions/core/lib/command.js:66

I'm getting an error while running the action, see below logs,
2022-10-13T11:50:16.0152871Z /github-action-runner/install/_work/_actions/estherk0/jenkins-trigger/1.0/node_modules/@actions/core/lib/command.js:66
2022-10-13T11:50:16.0158606Z         .replace(/%/g, '%25')
2022-10-13T11:50:16.0158851Z          ^
2022-10-13T11:50:16.0161264Z
2022-10-13T11:50:16.0163161Z TypeError: (s || "").replace is not a function

you should write your params in this format:
          parameter: |             {               "parm1":"value1"             }

you should write your params in this format:  parameter: | { "parm1":"value1" }

@samithegreen I dont think this is related. This was working earlier but even me too getting the same error which @ChintanPania  mentioned.
@estherk0  any suggestions?

I having the same problem as @sawanverma :

Passing the parameter like this works fine for us ->
          parameter: '{"BRANCH":"test"}'


renovate: do not update etcd on older branches

Since etcd v3.5.5, bash is no longer present on etcd images and we can't upgrade to newer versions as we still use a bash init script to setup clustermesh.

/test

/test


Publish 06/22/2021, 10:30 AM

Docs Build status updates of commit f494e6c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-AntiPhishPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/sharepoint-ps/sharepoint-server/Backup-SPFarm.md
:white_check_mark:Succeeded
View (sharepoint-ps)

teams/teams-ps/teams/New-TeamChannel.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


WebGL build dont see llmTools

Hello,
I am using unity 6, and wile testing latest ChatdollKit I found out that after switching to WebGL build there are errors in:
Assets\ChatdollKit\Scripts\LLM\Gemini\GeminiServiceWebGL.cs
Assets\ChatdollKit\Scripts\LLM\CommandR\CommandRServiceWebGL.cs
Assets\ChatdollKit\Scripts\LLM\Gemini\GeminiServiceWebGL.cs
Assets\ChatdollKit\Scripts\LLM\Claude\ClaudeServiceWebGL.cs
Assets\ChatdollKit\Scripts\LLM\ChatGPT\ChatGPTServiceWebGL.cs
The name 'llmTools' does not exist in the current context. I tried to reimport everything, but it doesnt seem to work. Windows platform works without problems. Maybe any tips or suggestions how to solve it?

Hello again, thank you for quick response.
I just wanted to inform you that v0.8.7 package ChatdollKit_0.8.7.unitypackage does not include these changes.

@kirelisaurimas Thank you for letting me know!
I've just uploaded a new unitypackage that includes both the reported missing changes and all other intended updates.
SocketServer is not supported in WebGL, so you can solve that error by just comment out whole code of SocketServerController as a quick work around. I will handle this in another issue.


Not clear how to inspect Javascript logs/tracebacks

When executing a Javascript cell in a .ipynb, like:
%%js

console.log('hello');

Currently it's not clear where the Javascript logs appear. I tried to look in the Output tab -> Jupyter but don't see anything. On Colab/Chrome, I can open the Javascript console (right click -> Inspect).
This makes debugging .ipynb quite hard. For example, if an error is raised in Javascript, it's not clear how to inspect the stacktrace.

So actually it seems the JS console is available through Help > Toggle Developer Tools.


Bug: TextBoxes with emoji support cause undefined behavior (especially when binding to properties)

Delete they (temporary solution)

Fixed by 006c248 commit


Workflow from Phishing => Phishing.Database => VirusTotal?

See first issue here https://github.com/mitchellkrogza/phishing/issues/395

@spirillen , closing as I will move the issue here on Wednesday.


krane: 2.4.0 → 2.4.6

Description of changes
Update to the latest version: https://github.com/Shopify/krane/releases/tag/v2.4.6
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 170005 run on x86_64-linux 1

1 package built:

krane


fix: pfe-cta arrow wrap issue #679

Resolves Issue #679

Link(s) to demo pages where this element can be viewed:
https://deploy-preview-765--happy-galileo-ea79c4.netlify.com//elements/pfe-cta/demo/

What has changed and why
Summarize files edited as part of this MR along with a brief description of what was changed/why.

Used nobreak space in the template + white-space:nowrap to force the arrow to stick to the last word in the CTA. Then reset the white-space on the link inside the CTA. Firefox understands the box model differently, so there is a browser specific style to limit the width of the CTA so the arrow does not get cut off.

Testing instructions
Be sure to include detailed instructions on how your update can be tested by another developer.
Use the resize box on the pfe-cta demo page (halfway down) to test in various browsers.
- The arrow should always be on the same line as the last word in the cta
- The arrow should stay next to the last word, and not float to the edge of the CTA area

[x] Latest 2 versions of Edge
[x] Internet Explorer 11 (should be useable, not pixel perfect)
[x] Latest 2 versions of Firefox (one on Mac OS, one of Windows OS)
[x] Firefox 60.7.2 (or latest version for Red Hat Enterprise Linux distribution)
[x] Latest 2 versions of Chrome (one on Mac OS, one of Windows OS)
[x] Latest 2 versions of Safari
[x] Galaxy S9 Firefox
[x] iPhone X Safari
[x] iPad Pro Safari
[x] Pixel 3 Chrome

Ready-for-merge Checklist

[x] Expected files: all files in this pull request are related to one feature request or issue (no stragglers)?
[x] Did browser testing pass?
[x] Did you update or add any necessary documentation (README.md, WHY.md, etc.)?
[x] Was this feature demo'd and the design review approved?
[x] Did you update the CHANGELOG.md file with a summary of this update?

The resize updates look great but please add back the demo page layout styles as they are not related to the PR and require discussion and additional consideration.

I opened an issue for current updates needed on the demo page for pfe-cta, I'd love to collaborate on it with you: https://github.com/patternfly/patternfly-elements/issues/775


Repo sync for protected CLA branch

The pull request is created from main637847750764226682 to main to fix git push error for protected CLA branch

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Changed setup() to not be an exclusive system

Description
In the examples of the valence crate, the setup() functions are currently exclusive systems. My reasoning for making these a standard system is twofold:

Exclusive systems can be considered an advanced Bevy topic. I don't think you should be using advanced concepts in examples meant to be an introduction to the way this project/framework is used.
In instances where developers try to use these examples, adding another startup system would result is running the systems sequentially. That leaves performance on the table (albeit only during startup).

Test Plan (or lack thereof)
I've chosen to not include any tests besides the ones already present, because I feel that it's unnecessary. My justification is as follows: Since setup() was the only startup system in these examples (that I'm aware of), the changes are functionally equivalent to anything before. This is because startup systems run before all non-startup systems. See this docs.rs section for some information on startup system scheduling.

FYI, a test plan is not "What tests do I need to write?", think of it as "What should the maintainers do to make sure this change works as expected?"


New maintainer of this project

Hi,
I use this library very often and for my own DCF calculator.
It seems as though this package has been abandoned. Could I request to take it over @ebradyjobory
I'd like to refactor it to normal functions, add testing, add more functions etc.
Thanks

I know it's been awhile since you posted this @MartinDawson, but I just recreated this package refactored into simple javascript functions, modularized it, and split out the tests.   I used the exact same test cases as in this package to verify the functions, but I switched from mocha to jest.
Here is my new repository for anyone interested:  https://github.com/alfreema/finance