Weirdly formatted text in log with wasm-init

To reproduce:
$ pwd
/home/erlend/rust/wasm-pack
$ mkdir myproject
$ cd myproject/
$ cargo init --lib
     Created library project
$ cd ..
$ cargo run -- init myproject/
    Finished dev [unoptimized + debuginfo] target(s) in 0.09s
     Running `target/debug/wasm-pack init myproject/`

| [1/8] Checking crate configuration...
Ensure that you have "wasm-bindgen" as a dependency in your Cargo.toml file:
[dependencies]
wasm-bindgen = "0.2"

wasm-pack.log
Jul 14 07:43:53.737 ERRO Ensure that you have "wasm-bindgen" as a dependency in your Cargo.toml file:
[dependencies]
wasm-bindgen = "0.2"

There are two problems here: "ERRO" should be "ERROR" and there is some encoding issue with what should be "wasm-bindgen".
I'm on Ubuntu 16.04
Locale, if that matters:
$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US

Thanks for filing! Could you let me know what version of wasm-pack you are using and what command you ran? That will help us track down what the issue is. We are not currently localizing the log so this is almost certainly a bug!

Sure:
$ pwd
/home/erlend/rust/wasm-pack
$ git show
commit b0470b08e008b55b6c0f249888918b114befee8d
Merge: faed391 81e5868
Author: Michael Gattozzi<EMAIL_ADDRESS>Date:   Tue Jun 26 14:37:22 2018 -0400

    Merge pull request #195 from steveklabnik/patch-1

    Fix code example in README

$ mkdir myproject
$ cd myproject/
$ cargo init --lib
     Created library project
$ cd ..
$ cargo run -- init myproject/
   Compiling wasm-pack v0.4.0 (file:///home/erlend/rust/wasm-pack)
    Finished dev [unoptimized + debuginfo] target(s) in 3.25s
     Running `target/debug/wasm-pack init myproject/`

| [1/8] Checking crate configuration...
Ensure that you have "wasm-bindgen" as a dependency in your Cargo.toml file:
[dependencies]
wasm-bindgen = "0.2"

This is the exact sequence as above but with git show included so you can see the exact git commit I'm on. It's the latest master right now.
The weird thing is that it works fine if I run cat wasm-pack.log but it's incorrect if I open it in both Vim and VSCode. It would be good if someone could execute the exact steps above and then open myproject/wasm-pack.log to see if they can reproduce.

oh thanks for the details @Mackiovello ! particularly that cat works fine. i'll be honest, in my testing of it i've only viewed the log with cat so this is almost certainly why i've missed this. yay character encoding!! lolsob

Oh boy character encoding issues! Will try this out soon to see if I can reproduce

Not an encoding issue; those are ECMA-48 SGR codes. [1m is set bold, [2m is set half-brightness, and [0m is reset to default. Raw terminal output is getting dumped into the log file, including the formatting control codes to print "wasm-bindgen" in bold:
Notice the difference between less wasm-pack.log and less -R wasm-pack.log:

The fix is making sure that whatever is doing the logging is treating the log file as a file, rather than as a terminal.

Hi! I've actually been working on this one since last week, after discussing it with Ashley and finding it'd be a good first issue. I meant to write an update post yesterday but it got away from me.
In any case, the simplest solution for this seems to be just removing the encoding before throwing the message to the log. The message gets formatted in manifest.rs at the check_wasm_bindgen function, in the line
Error::crate_config(&format!(         "Ensure that you have \"{}\" as a dependency in your Cargo.toml file:\n[dependencies]\nwasm-bindgen = \"0.2\"",         style("wasm-bindgen").bold().dim()     ))
the same crate that contains style() also has a convenient function-- strip_ansi_codes()-- that removes the format tags from a string.
Currently, I think the issue has to do with where we can address this in the order of events. The error message is formatted in manifest.rs, then thrown to error.rs to form an Error enum before it's passed back up to command.rs, logged using error!, has extra formatted text appended using PBAR.error() and then passed to main.rs to print to the CLI. We still want the formatted message to reach the CLI but it needs to be stripped before being pushed to the log. This is a bit of an issue since it's pushed to the log before it is printed to the CLI. Once it hits the error! macro as well, it steps through a bunch of functions in the slog library which puts further formatting out of our hands until it's finished actually pushing it to log.
I have a few solutions in mind currently, but I haven't implemented them yet since this is my first open source project and I'm not sure how much I'm able to actually adjust in the code, in addition to being unsure how to do certain things in Rust just yet.
The best solution I can think of currently is to have some sort of function that takes the value rather than the reference to the Error enum, takes the message and runs it through strip_ansi_codes(), then passes that to error! to be pushed to log; leaving the original Error enum alone so it can be returned to main and printed to CLI with the formatting still intact. I think implementing a solution like this would be good if we're intending to make style formatting for the CLI format a standard, since it'd future-proof any other formatted messages by running them through the stripping function.
I might be overcomplicating this since it's my first issue, so if anyone knows a simpler method I'm absolutely open to hearing. Otherwise, I am going to continue trying to tackle this with Ashley's help today. :)

Thinking of it we could clone it and strip the ansi codes from the clone only and then pass back the other one like normal. I think that's the easiest solution if it's cloneable (which my guess is that it should be)

we are going to be working towards a fix for this as we approach solving #298. i am going to close this specific issue as we will track progress in the mini RFC


Applying new patches

Hello guys,
We'll use Elastic Beanstalk with ActiveJob, and we found this awesome gem; however, it has some problems with CI (especially Ruby 2.4) and @tawan was not using Elastic Beanstalk anymore. Also, test files depend to real Elastic Beanstalk environment, but I think, we can achieve this problem with using stubbed data.
These are the main reasons why we clone and maintain by our team.
So, if you will apply new patches, please consider to add them to magara/active-elastic-job since we'll some help.
P.S. Thank you for bringing this :gem: to the Ruby ecosystem, @tawan!

@BerkhanBerkdemir did you move that repo to another location? It is a 404 now. Thanks!


Add functions for determining the maximum useful thread count

This could be useful for reducing CPU overhead in Amethyst

I'm not sure I can recommend this as there are other things than the
dispatcher running jobs with the pool. E.g. asset loading
On Mon, Jun 11, 2018, 19:19 Jacob Kiesel<EMAIL_ADDRESS>wrote:

@Xaeroxe https://github.com/Xaeroxe requested your review on:
slide-rs/shred#95 https://github.com/slide-rs/shred/pull/95 Add
functions for determining the maximum useful thread count.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/slide-rs/shred/pull/95#event-1674434604, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AWFFua8AmuI5piCGLkWXDaD0eA7m403Lks5t7qangaJpZM4UjCEo
.

@torkleyy right, which is why Amethyst would add 1 or 2 to the value reported by this API in order to accomodate that.

@torkleyy quick context for the motivation behind this: https://github.com/amethyst/amethyst/issues/780#issuecomment-396281153

I saw that, but I'm still not convinced it makes sense to create a pool with less threads than cores, and I don't think it's the solution to the high CPU usage.

bors r+


Remove version lower bound on zlib host requiement

You shouldn't put a version constraint here on zlib. It's included in the global pinning: https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/9e690262e1bb221e8fc8b370232a0aaf7ef1eb2b/recipe/conda_build_config.yaml#L906-L907
When you rerender the versions are picked from there and included in the .ci_support files. The reason for defining it there is that if there is a zlib 2 with a different ABI, a "migration" can be ran to rebuild all dependent packages in order with the new zlib. You can track current migrations on the status page: https://conda-forge.org/status/#migrations
It could also make sense to add pythia and lhapdf to the global pinning but I'll leave that up to you.

Originally posted by @chrisburr in https://github.com/conda-forge/pythia8-feedstock/pull/39#discussion_r1717462110

When you rerender the versions are picked from there and included in the .ci_support files.

@chrisburr Questions on how https://github.com/conda-forge/conda-forge-pinning-feedstock works:

The recommendation for

https://github.com/conda-forge/pythia8-feedstock/blob/831a47b1760e2a17ea1d64996ae7501c3495385d/recipe/meta.yaml#L36
to remove the lower bound on zlib
diff --git a/recipe/meta.yaml b/recipe/meta.yaml
index 46276a1..3843b19 100644
--- a/recipe/meta.yaml
+++ b/recipe/meta.yaml
@@ -33,7 +33,7 @@ requirements:
     - libxcrypt  # [linux and py<39]
     - pybind11
     - lhapdf >=6.2
-    - zlib >=1.0.0
+    - zlib
   run:
     - python

given https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/9e690262e1bb221e8fc8b370232a0aaf7ef1eb2b/recipe/conda_build_config.yaml#L906-L907 and this is because if the host requirements have zlip listed then the conda-forge-pinning-feedstock will pin it to be zlib==1.0.0?

Given my question https://github.com/conda-forge/pythia8-feedstock/pull/39#discussion_r1717486474 does this mean that is lhapdf got added to https://github.com/conda-forge/conda-forge-pinning-feedstock that to ensure that it didn't pin to the lowest version of lhapdf6 supported by pythia8 (LHAPDF v6.2) that I'd need to add it like

lhapdf:
  - 6.*

which would get interpreted as lhapdf >=6.x in the .ci_support files (which should be fine as the oldest lhapdf on conda-forge is v6.4.0)?

Ah I guess the answer to my questions is "yes" given https://conda-forge.org/docs/maintainer/pinning_deps/


[BUG]: Observability - Improve Grafana dashboard

Bug Description
In Observability Grafana dashboard:

PowerFlex metrics dashboard name is not clear, unlike PowerScale or PowerStore.

It may be helpful to change the topology from 5 to 25+ for items shown to give customers a larger swath of items seen. I usually go in and change it when deployed, but some customers may find that "difficult" shouldn't be much to change
],
"panelHeight": null,
"pluginVersion": "7.0.3",
"rowNumbersEnabled": false,
"rowsPerPage": 5, <-----------------------------------------------------Change to 25 as Default?
"scroll": false,
"scrollHeight": "default",
"searchEnabled": true,
"searchHighlightingEnabled": false,
"showCellBorders": false,
"showHeader": true,
"showRowBorders": true,
"sort": {
"col": 0,
"desc": true
},

Logs
NA
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce

Navigate to Observability Grafana dashboard
Open PowerFlex metrics dashboards
Open Kubernetes Admin Dashboard

Expected Behavior

For PowerFlex metrics dashboards, the title indicates 'PowerFlex'.
For Topology dashboard, the row per page is 25.

CSM Driver(s)
CSI Driver for PowerFlex v2.4
Installation Type
No response
Container Storage Modules Enabled
Observability v1.3
Container Orchestrator
K8s 1.24
Operating System
RHEL 8.6

Resolved.


treewide: prep 2.4.11

Let's cut a patch release to get #445 out the door.

Thanks @tetsuo-cpp! I'll do the tag.


Update runtests.jl to use maxfun  = 500n and rhoend = 1e-6 instead of maxfun = 200n and rhoend = 1e-3

Use maxfun  = 500n and rhoend = 1e-6 instead of maxfun = 200n and rhoend = 1e-3 in the test. Users may use the tests as examples to learn how to set parameters in practice. The original values will render only rough solutions.

I agree with the changes. I have changed another rhoend value in the tests as of ee406df.


请问支持api吗，例如api增删改查一些功能

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
API
🔖 Feature description
请问支持api吗，想通过api接口增删改查一些功能
✔ Solution
请问支持api吗，想通过api接口增删改查一些功能
❓ Alternatives
No response
📝 Additional Context
No response

目前还没有公开的api来做这些事情，尽管它正在计划中。#118
对于未来的问题，请使用翻译，以便每个人都能轻松地帮助你。
(There is no publicly available api to do this yet, although it is being planned. #118
For future questions, please use a translator so that everyone can easily help you.)


"craftar" package throws error on Ubuntu 16.04 when importing

The Python "craftar" package throws error on Ubuntu 16.04 when importing:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.5/dist-packages/craftar/__init__.py", line 9, in <module>
    from craftar._management import *
  File "/usr/local/lib/python3.5/dist-packages/craftar/_management.py", line 8, in <module>
    from craftar._common import _get_object_list, _get_object, _create_object, \
  File "/usr/local/lib/python3.5/dist-packages/craftar/_common.py", line 11, in <module>
    from urllib import urlencode
ImportError: cannot import name 'urlencode'

Steps to reproduce
Prepare a docker container:
docker run -ti --rm ubuntu:16.04 bash

# In the docker container bash
apt-get update
apt-get install -y python3 python3-pip

pip3 install craftar

Start a python interactive shell:
$ python3
Python 3.5.2 (default, Nov 17 2016, 17:05:23)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import craftar
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.5/dist-packages/craftar/__init__.py", line 9, in <module>
    from craftar._management import *
  File "/usr/local/lib/python3.5/dist-packages/craftar/_management.py", line 8, in <module>
    from craftar._common import _get_object_list, _get_object, _create_object, \
  File "/usr/local/lib/python3.5/dist-packages/craftar/_common.py", line 11, in <module>
    from urllib import urlencode
ImportError: cannot import name 'urlencode'
>>>

Closed with #4


Bluetooth: controller: Fix assert in RPA timeout for advertiser

Fix assert in the RPA timeout when no resolving entry exists in the
resolving list, and the advertiser was requested to use a local IRK
to generate it's own address.
Fixes: #18092

@carlescufi backport this?

@carlescufi backport this?

Can you please include this in your Controller Conformance backport PR @cvinayak ?

@wopu-ot @thoh-ot @asmk-ot I will be merging this today since it's a pretty serious bug that we need to backport and deal with as soon as possible. We have developed the fix together with @joerchan and we are quite confident it is correct. If you have additional remarks please let us know and we'll deal with those post-merge.

@carlescufi backport this?

Can you please include this in your Controller Conformance backport PR @cvinayak ?

Does this mean we are not yet sure if this is to be back-ported @carlescufi ?

@carlescufi backport this?

Can you please include this in your Controller Conformance backport PR @cvinayak ?

Does this mean we are not yet sure if this is to be back-ported @carlescufi ?

No, this means we need to backport it, and so it needs to be added to the PR

@carlescufi backport this?

Can you please include this in your Controller Conformance backport PR @cvinayak ?

Does this mean we are not yet sure if this is to be back-ported @carlescufi ?

No, this means we need to backport it, and so it needs to be added to the PR

Then we don't need to label it as back-port.

@carlescufi backport this?

Can you please include this in your Controller Conformance backport PR @cvinayak ?

Does this mean we are not yet sure if this is to be back-ported @carlescufi ?

No, this means we need to backport it, and so it needs to be added to the PR

Then we don't need to label it as back-port.

That's right

@carlescufi backport this?

Can you please include this in your Controller Conformance backport PR @cvinayak ?

Does this mean we are not yet sure if this is to be back-ported @carlescufi ?

No, this means we need to backport it, and so it needs to be added to the PR

Then we don't need to label it as back-port.

That's right

Done. Added to https://github.com/zephyrproject-rtos/zephyr/pull/17720

Backport included in #18122


Override or circumvent?

I need to run a migration (production db) that splits documents. The new inserted document should get the same createdAt field as the original one.
I tried these collection2 settings, but it still uses the current date instead of the old one:
Collection.insert newDoc,
  validate: false
  filter: false
  getAutoValues: false

I'd rather not switch off the timestampable behaviour in my production codebase.
Any other way to switch the behaviour off for a certain query? Thanks!

Sorry there is already a similar issue. Can be closed I guess. Sorry!

I'll close this and give you both a temp solution in the other thread.


[Feature request] Add English in the main package NuGet

Is your feature request related to a problem? Please describe.
The default langage is chinese. Some patern use the default langage of HandyControl, like error in hc:TextBox, hc:PropertyGrid.
Describe the solution you'd like
I think it can be nice to add English langage in the main package NuGet
Describe alternatives you've considered
The current alternative is to install the HandyControl.Lang.En package NuGet
Additional context
Reference : #1131 , #1130

As a non native English speaker (I speak Spanish), I also think English should be the default, as is an industry standard.


Fortnite Download From Cache Only Completes to 28%

Describe the bug
When going through the LAN-Cache, Fortnite only completes to 28%. It doesn't matter which computer in the house I use. Epic Games launcher shows the download rate drop to 0 instantly once it reachs 28% downloaded. Filesystem was XFS on a 6TB HDD.
Additional Details

unRAID Server - Lancache, Lancache-DNS, and Lancache-Prefill in Docker
ZurkeyDurkey
Region : US West Coast

Screenshots
If applicable, add screenshots to help explain your problem.
access.log

Try the latest version v2.0.0, it should include a potential fix for this issue.

I'll definitely try that out.   The steam cache and prefill has been disabled since shortly after that post, so I'll turn it all back on again, update Docker, and test it out.

Let me know how that goes.  I'm going to go ahead and close this for now since I'm 99% sure it will fix your issue.  If it doesn't please feel free to reopen this and we'll look at it again.


Style of export tab doesn't match the rest

Describe the bug
Export tab doesn't have "pane" class
Screenshots
Pane:

No Pane:

Since this export pane is its own component rather than a dynamically rendered component. Will need to make some changes in Editors/exportEditor.js to include that className


Feature(LLMLingua): add examples

Added the ./examples folder, which includes practical applications such as RAG, Online Meeting, CoT, Code, and RAG using LlamaIndex.
Fixed the typo in the README as mentioned in issue #10. Special thanks to @eltociear for pointing this out.
Updated the README to include a dedicated page for LongLLMLingua, along with its motivation.

Additionally, the example notebooks are now supported to be displayed in Google Colab.


doc: tfm: Document how to pass list arguments to the TF-M build system

Document how to pass list arguments to the TF-M build system.
fixes: #53556
Signed-off-by: Joakim Andersson<EMAIL_ADDRESS>

@carlescufi Mind having a look to get this merged in?


Error with Preview 17 query engine distribution

When upgrading to preview17.2 (from 16.2) I am getting
Generating Photon.js to ./node_modules/@prisma/photon
__dirname /usr/src/app/node_modules/@prisma/photon/generator-build
/usr/src/app/node_modules/@prisma/photon/generator-build
2019-11-30T10:13:39.035Z generateClient Copying /usr/src/app/node_modules/prisma2/build/query-engine-debian-openssl-1.1.x to<EMAIL_ADDRESS>Error: Error: Error: ENOENT: no such file or directory, copyfile '/usr/src/app/node_modules/prisma2/build/query-engine-debian-openssl-1.1.x' -><EMAIL_ADDRESS>    at GeneratorProcess.handleResponse (/usr/src/app/node_modules/prisma2/build/index.js:182160:35)
    at LineStream.<anonymous> (/usr/src/app/node_modules/prisma2/build/index.js:182138:26)
    at LineStream.emit (events.js:210:5)
    at LineStream.EventEmitter.emit (domain.js:478:20)
    at addChunk (_stream_readable.js:326:12)
    at readableAddChunk (_stream_readable.js:301:11)
    at LineStream.Readable.push (_stream_readable.js:235:10)
    at LineStream.Transform.push (_stream_transform.js:150:32)
    at LineStream.module.exports.2514.LineStream._pushBuffer (/usr/src/app/node_modules/prisma2/build/index.js:64185:23)
    at LineStream.module.exports.2514.LineStream._transform (/usr/src/app/node_modules/prisma2/build/index.js:64177:10)
error Command failed with exit code 1.

while on preview16.2 it works like a charm
Downloading https://s3-eu-west-1.amazonaws.com/prisma-native/master/b72fd0a786adc77ba6c61d0a9637ff0371e433b0/linux-glibc-libssl1.1.0/prisma.gz to /usr/src/app/node_modules/prisma2/build/query-engine-linux-glibc-libssl1.1.0
Generating Photon.js to /usr/src/app/server/node_modules/@prisma/photon
2019-11-30T10:30:36.553Z generateClient Copying /usr/src/app/node_modules/prisma2/build/query-engine-linux-glibc-libssl1.1.0 to<EMAIL_ADDRESS>Done in 11.60s

Most notable difference: on 16.2 it's loading query-engine-linux-glibc-libssl1.1.0 while on 17.2 it tries to fetch query-engine-debian-openssl-1.1.x.
Both instances are using Heroku/heroku:18 docker image based on Ubuntu 18.4, and are running on Heroku. I hope this helps 🙂

preview017 changed the binary names, see https://github.com/prisma/prisma2/releases/tag/2.0.0-preview017, so the new name is expected. The error you are seeing of course is not.
Where does your project live - /usr/src/app/server/ or /usr/src/app/? Any special ENV variables or config in your schema?
I think I saw a similar issues before, so @pantharshit00 will probably be able to actually help you out next Monday.

prisma2 is required as a peerDependency for @prisma/photon so that we can copy the binaries in the build folder. Can you please make sure that you have prisma2 installed a dependency for this project?

@pantharshit00 I believe I have prisma2 installed - it's a development dependency. Wouldn't I be unable to run prisma generate if it weren't installed?

it's a development dependency.

I think Heroku prunes devDependencies so it might also be removing the binary the need to be copied.
Can you share your DockerFile so that I can try this locally once?

@pantharshit00 I have the exact same setup - same dependencies, same development dependencies - earlier version as I have with the later. I am pretty convinced that is not the problem.
https://github.com/maticzav/emma-cli/blob/master/Dockerfile

I'm seeing an issue that might have a similar cause as this:
$ npx prisma2 generate
Error: Error: Command failed with ENOENT: /home/dan/prisma2/node_modules/prisma2/query-engine-debian-openssl-1.1.x cli --dmmf
spawn /home/dan/prisma2/node_modules/prisma2/query-engine-debian-openssl-1.1.x ENOENT

This is on WSL2 (Ubuntu)

That might very well be a separate issue @djskinner, please create a new issue and include all available information. Thanks.

@pantharshit00 @janpio any luck with the issue?

Sorry I didn't get to it earlier. You need to update your docker setup a bit. You don't require to configure the output now as @prisma/photon package is now in the package.json and yarn workspace will handle it. Right now the output node_modules node_modules but our script is trying to fetch binary from the root node_modules.
I made a small PR fixing this setup: https://github.com/maticzav/emma-cli/pull/219

@maticzav Can this be closed now?

It can.


[Bug]: Mocking getters/setters does not work

Version
29.3.1
Steps to reproduce
I prepared a repository with failing test cases here: https://github.com/meeh0w/jest-mock-repro
Or you can use the example below (it's fairly short). In a nutshell, mocking property accessors will throw an [accessorName] property does not exist error.
Class
// SimpleClass.js
module.exports = class SimpleClass {
  get testGetter() {
    return 'test';
  }
}

Tests
// SimpleClass.test.js
const SimpleClass = require('./SimpleClass.js');

jest.mock('./SimpleClass');

describe('Mocking accessors', () => {
  it('can mock an instance getter', () => {
    const instance = new SimpleClass();
    const mockTestGetter = jest
      .spyOn(instance, 'testGetter', 'get')
      .mockReturnValue('mockedTestGetter');

    expect(mockTestGetter).toHaveBeenCalledTimes(1);
  });
});

Expected behavior
Getters & setters are properly mocked.
Actual behavior
Jest is unable to mock getters and setters.
Additional context
I believe the issue was already fixed in #13145 (I see relevant test cases being added to the repository), but has since regressed in a follow-up PR (#13472), which removed the test cases for property accessors (see the diff here).
Environment
System:
  OS: macOS 13.0
  CPU: (10) arm64 Apple M1 Max
Binaries:
  Node: 16.19.0 - ~/.nvm/versions/node/v16.19.0/bin/node
  Yarn: 1.22.19 - ~/.nvm/versions/node/v16.19.0/bin/yarn
  npm: 8.19.3 - ~/.nvm/versions/node/v16.19.0/bin/npm
npmPackages:
  jest: ^29.3.1 => 29.3.1

I am experiencing the same issue right now with 28.1.1

@giorgosera It was supposed to be fixed by #13145 in 29.1.0, but unfortunately I believe the fix got broken again before the release happened.


Run tests with --throw-deprecations

Similar to https://github.com/GoogleCloudPlatform/google-cloud-node/issues/2839, it would be good for Google Cloud libraries to not use deprecated Node.js APIs. Deprecation messages printed to the console, however, can be easy to miss.
We should run tests with --throw-deprecations to ensure that use of deprecated APIs is caught by tests.
The same deprecation mechanism would work for our own deprecations, e.g. https://github.com/google/google-auth-library-nodejs/pull/402.

Should we run all of our tests with this turned on, or just the system-tests and samples tests?  I ask because we have unit tests that verify the warning behavior for deprecated APIs :)

We have unit tests that verify the warning behavior of all deprecations, including Node.js? Can you point me to how this is done?

I was referring to this:
https://github.com/google/google-auth-library-nodejs/pull/402/files#diff-86629eb1fa03b5146081c8eed046735bR1407
When you run that unit test, it will emit the deprecation warning to the console.

Oh gotcha! In that test could you install a mock on process.emitWarning instead of installing a listener and expecting it to be called?

All of the PRs for this have been submitted.  Just waiting on fix in gax-nodejs to land the stragglers :)


Add post: Round 4 accessibility research findings (Funding mentors)

All looks good except this seems off:

@olioldfield this is now ready for review


handling of array of events not working

I would like to listen to multiple events, specified by an array. but it is not working of any of the events listed, except when i try to emit on all events together.
Please see below for your reference:

var em = require('eventemitter2').EventEmitter2;
undefined
var ser = new em({wildcard: true});
undefined
ser.many(['foo', 'bar', 'bazz'],10, function() { console.log("test 123 fired :" + this.event ); });
EventEmitter {
_events: {},
newListener: false,
_conf: { wildcard: true },
wildcard: true,
listenerTree: { foo: { bar: [Object] } } }
ser.emit('foo');
false
ser.emit(['foo','bar','bazz']);
test 123 fired :foo,bar,bazz
true

What version of EventEmtiter2 are you using? Does it work with older or newer versions?

I'm using 1.0.3. I haven't tried other versions.
On Wed, May 18, 2016 at 2:36 AM, RangerMauve<EMAIL_ADDRESS>wrote:

What version of EventEmtiter2 are you using? Does it work with older or
newer versions?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/asyncly/EventEmitter2/issues/168#issuecomment-219853877

Do you think you could try out pre 1.0? There were a bunch of changes around then that may have changed things around.

Looking through the code, it seems that passing an array isn't the same as subscribing multiple events. It's basically the same as ser.on(["foo", "bar", "baz"].join(ser._conf.delimiter), etc, etc). It seems that many(events, fn), as shown in the docs, doesn't actually exist.

Does this issue relate to the scenario where you need a listener to fire only if multiple events are received?
I.e.
emit('a')
emit('b')
on(['a', 'b'] => do something when both a and b have been received)

waitFor for EventNS also not work...
example: waitFor(['event1', 'event2'])

@gengshenghong The EventNS type is not an array of separate events. It is an event namespace/event path for the wildcard emitter. It could be a string like 'body.menu.click' or an equal array ['body', 'menu', 'click'].

@DigitalBrainJS thanks for your answer. This is not intuitive at all, I had to struggle my way out. Would be cool to either emphasize it somewhere in the doc (like really visible) or change if there's no strong prerequisite for current behavior (I guess there is).


Which TensorFlow and python version did you use ?

In your docker file, it shows
FROM tensorflow/tensorflow:latest-gpu

This question has been answered, please see issue #1
Python version above 3.6 should be ok

I tried tensorflow=2.1.0, but get ValueError: The batch_size argument must not be specified for the given input type. Received input: <action_predict.DataGenerator object at 0x7efd0811a590>, batch_size: 32.


Bug | Deleting your own article

When ?

User signs in
User clicks on an article that's created by themself.
User clicks on delete button icon.

What ?

The backend API returns 411 with the error 'Something went wrong'

Screenshot:

Bonus points:

Ideally, when user clicks on the delete icon, user should be shown confirm dialog before actually deleting the article. A-1 if you can implement it in this ticket. (Optional)

A bit new to Node JS, But want to try to solve some of the backend bug as well, Can you assign it?

Sure

I'd be happy to assist with this if @dhairya-create needs any help or isn't able to come up with a solution. Just let me know!

Setting up the backend is just going into the backed folder and installing the dependencies right?
Or some extra steps are needed?

@dhairya-create - fyi backend setup

#98 closes this


Unexpected behavier when close a file

VSCode Version: macOS 10.12
OS Version: 1.4.9

Steps to Reproduce:

The file list in sidebar is so long that produce a scroll bar.
Close file in editor.
Then focus in sidebar will jump to bottom.

This is as designed, once you close a file in the Open Editors list we will reveal and focus the currently opened file.
If you think this is unexpected please provide a short gif video showing this issue and I will reopen this issue.

Thanks！  @isidorn 😁


apparmor: refactored code

Deleted 438 lines of redundant code.
Ref: #619
Signed-off-by: Rahul Jadhav<EMAIL_ADDRESS>

LGTM


Add supervisors to overlord console.

@gianm could you add a screenshot of this in action in the PR please?

It looks like this:

If you don't have any supervisors then the top section doesn't show up.


Feature request: WorkItemRevisionReplayContext

Hey there!
I would like to not only migrate the current state of a work-item to the new project, but I would like to port over the whole revision history, to get the history in the new system as well, including the state graph, which would be of very much value for me.
Having a look at the code of the Work Item Migration Context, it should not be a big deal to have the following approach in place:

instead of just taking a "snapshot" of the latest revision of the item, recreate it in revision 0 state from the original system
then replay all revisions from the original work item on the target item

You would already have quite much things for this in place. Instead of just simply copying the values from the current work item, just walk through the workItem.Revisions collection and use the Fields property there, to replay the changes on the item on the target system.
Would you see this as being feasible after all?
As mentioned: keeping the state + revision history and thus the state graph intact in the target system would be of immense value for me!
Cheers,
Harald

Hey there,
I just had some hours to spent on the tool and implemented an extension: the work item revision replay context.
The pull request can be found here: https://github.com/nkdAgility/vsts-sync-migration/pull/17
I tested it on my system and it seems to work fine.

On my system, tests are succeeding.
Documentation would need to be updated.
Cheers,
Harald

This is awesome work and I will look at it this weekend... did you add a switch so that users can choose to migrate flat or with revisions? There is a time constraint if one is migrating many work items...

@MrHinsh see the latest pushed commits on the branch
Originally, I had a different pull request for these changes #20
I now merged these changes into the old branch for the feature itself.
So far I have not had any problems with time constraints or the like. I migrated over (with the revisions replay context) around 3500 items, without any problem.

Each save takes around 0.2 seconds, and I often migrate 100k+ work items. That takes around 30 hours with no revisions, with revisions it can be significantly longer...

Well, true. For 100k+ items, it will be quite slow.
Especially, if you take into account the additional calls to the API for fetching the revisions as well.
I do not remember exact times anymore for the 3.5k+ items, but it was "okayish".
And as it was a one-time migration, I do not have to run it again.
Maybe we just add some hint for this to the documentation?

Agreed... We do however now have a lot of duplicate between revision and no-revision...

You mean duplication in code? That is right, as I just copied the old context and did the necessary adaptations for replaying the work item history.
One could try to refactor out a common base class for the work-item-migration-context itself.

My two cents worth... Love the replaying feature but would also liked to have seen this as a switch on the original Work Item Migration Context rather than creating a new context for this specific feature. There is a lot of duplicated code in the master branch now.

I agree with you, i just wanted folks to be able to benefit with what's there now. Can you open a new issue to merge the two features?

Sure, I've opened up a new issue #33.

@hkoestin can you please close this thread.


Improve display of public source/task/files on user profiles

The research data view could also be improved to move the timestamp to be per source/task, not per file.

Closed by #342


Handle failed demotions directly.

Instead of depending on connection monitoring to process cold peers
handle it directly.

Alternative fix for #3234 .

deprecated


tf.keras.models.load_model fails if tf.linalg.band_part is used.

System information

Have I written custom code: yes
OS Platform and Distribution: Arch Linux (5.9.4-arch1-1)
TensorFlow installed from: binary
TensorFlow version: 2.3.1
Python version: 3.8.6
CUDA/cuDNN version: 11.1/8.0.4
GPU model and memory: NVIDIA GeForce GTX 1080 Ti/10.91GiB

Describe the current behavior
tf.keras.models.load_model fails when tf.linalg.band_part is used.
ValueError: Inconsistent values for attr 'Tindex' DT_INT32 vs. DT_INT64 while building NodeDef 'tf_op_layer_MatrixBandPart/MatrixBandPart' using Op<name=MatrixBandPart; signature=input:T, num_lower:Tindex, num_upper:Tindex -> band:T; attr=T:type; attr=Tindex:type,default=DT_INT64,allowed=[DT_INT32, DT_INT64]>

Describe the expected behavior
Model is loaded without error.
Standalone code to reproduce the issue
import tensorflow as tf

x = tf.keras.Input(shape=(3, 3))
y = tf.linalg.band_part(x, -1, 0)  # getting lower triangle part. I need band_part() for making look-ahead-mask on Transformer.
# y = tf.reshape(x, (-1, 9))

model = tf.keras.Model(x, y)
print(model.predict([[[1, 2, 3], [4, 5, 6], [7, 8, 9]],
                     [[9, 8, 7], [6, 5, 4], [3, 2, 1]]]))
model.save('model')

tf.keras.models.load_model('model')

Other info / logs Include any logs or source code that would be helpful to
tensorflow.python.framework.errors_impl.InvalidArgumentError: Inconsistent values for attr 'Tindex' DT_INT32 vs. DT_INT64 while building NodeDef 'tf_op_layer_MatrixBandPart/MatrixBandPart' using Op<name=MatrixBandPart; signature=input:T, num_lower:Tindex, num_upper:Tindex -> band:T; attr=T:type; attr=Tindex:type,default=DT_INT64,allowed=[DT_INT32, DT_INT64]>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "test_band_part.py", line 11, in <module>
    tf.keras.models.load_model('model')
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/saving/save.py", line 187, in load_model
    return saved_model_load.load(filepath, compile, options)
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/saving/saved_model/load.py", line 120, in load
    model = tf_load.load_internal(
  File "/usr/lib/python3.8/site-packages/tensorflow/python/saved_model/load.py", line 632, in load_internal
    loader = loader_cls(object_graph_proto, saved_model_proto, export_dir,
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/saving/saved_model/load.py", line 194, in __init__
    super(KerasObjectLoader, self).__init__(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/tensorflow/python/saved_model/load.py", line 130, in __init__
    self._load_all()
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/saving/saved_model/load.py", line 221, in _load_all
    self._finalize_objects()
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/saving/saved_model/load.py", line 530, in _finalize_objects
    self._reconstruct_all_models()
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/saving/saved_model/load.py", line 548, in _reconstruct_all_models
    self._reconstruct_model(model_id, model, layers)
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/saving/saved_model/load.py", line 588, in _reconstruct_model
    created_layers) = functional_lib.reconstruct_from_config(
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/engine/functional.py", line 1214, in reconstruct_from_config
    process_node(layer, node_data)
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/engine/functional.py", line 1162, in process_node
    output_tensors = layer(input_tensors, **kwargs)
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/engine/base_layer.py", line 925, in __call__
    return self._functional_construction_call(inputs, args, kwargs,
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/engine/base_layer.py", line 1117, in _functional_construction_call
    outputs = call_fn(cast_inputs, *args, **kwargs)
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/engine/base_layer.py", line 3099, in call
    return self._make_op(inputs)
  File "/usr/lib/python3.8/site-packages/tensorflow/python/keras/engine/base_layer.py", line 3121, in _make_op
    c_op = ops._create_c_op(graph, node_def, inputs, control_inputs=[])
  File "/usr/lib/python3.8/site-packages/tensorflow/python/framework/ops.py", line 1815, in _create_c_op
    raise ValueError(str(e))
ValueError: Inconsistent values for attr 'Tindex' DT_INT32 vs. DT_INT64 while building NodeDef 'tf_op_layer_MatrixBandPart/MatrixBandPart' using Op<name=MatrixBandPart; signature=input:T, num_lower:Tindex, num_upper:Tindex -> band:T; attr=T:type; attr=Tindex:type,default=DT_INT64,allowed=[DT_INT32, DT_INT64]>

Same as #42301. I just wrote standalone code.

The issue is resolved in TF 2.4-rc0 version.I have tried in colab with TF 2.4-rc0 and i am not seeing any issue. Please, find the gist here.Please, verify once and close the issue. Thanks!

Thanks. And sorry I forgot to check latest version...


Improve Server Pending Reboot

Currently only holding a boolean for ServerPendingReboot, would like to hold the values from all the location checks to see what is set.

currently the extern template is updated to return this information, we just need to update and handle it.

Have this included in the script now, but would like to see some information to provide why we are seeing it set as server reboot is pending.

Have this included in the script now, but would like to see some information to provide why we are seeing it set as server reboot is pending.


Cross-compiling code using fsevents

Which version of macOS are you using?
Github runner macos-latest (Apparently macOS 12 Monterey based on the documentation.
Please describe the issue that occurred.
In my build I'm cross compiling into various OSes and hardware platforms. I initially used the Ubuntu 12 runner to do the compilation, but that failed on macOS after some dependency introduced the use of fsevents.
I then added macos builders for the two build workflows for darwin/amd64 and darwin/arm64. This fails on darwin/arm64 as well.
Compiling it on my M1 machine works though.
Are you able to reproduce the issue? Please provide steps to reproduce and a code sample if possible.
Try to compile ccmanager to darwin/arm64 from any machine other than an arm mac.
Do you have any hints on how to succeed building the tool with Github actions? Thanks a lot!

You'll have to set up the C compiler/XCode to compile arm64 binaries; it looks like it doesn't have the arm64 version of the libraries?
I'm not really knowledgable on macOS development. This library is essentially unmaintained, and I wouldn't wait for an answer here – you'll probably have better luck on reddit, Slack, or Stack Overflow if you're really stuck.

@dploeger cross compiling (especially to MacOs) CGO code is not trivial. We're not using this library, but if you look at Hugo's release setup:
https://github.com/gohugoio/hugo/blob/master/.circleci/config.yml
You can get a hint.
The short story is; there's no way of doing this (I'm pretty sure about this) with any of the basic GitHub containers.

Ugh. Thanks a lot. I wonder why one of the latest Docker versions started using fsevents as it obviously is deprecated, but Docker golang release management is hell anways. 😄
I guess, I'll just have to wait until Github releases the darwin arm build agents finally (heard the target was end of the year) and upload the arm binary manually until then.
Let me close this issue then.


Change RadzenComponent.Element setter to protected

#857
Changing this setter allows custom components inheriting the RadzenComponent class to reference the html element in @ref tags.

Hi @scottfridwin,
Your change breaks the compilation...

Thanks! Since it was so small, I made the change directly in github and didn't actually compile it. Updated to protected internal which will maintain access to all internal types as well as allow inheritance.


Remove confusing Start from wordPartLeft commands ID : #53497

ping @alexandrudima
(I did not test this change yet, but looking at what I needed to change it seems to be enough - I'll test later today)
Fixes #53497

:+1: Thank you!


All text are clearly visible now

I have solved issue #93
All the texts are clearly visible now
None of the texts are hidden.
These were the previous conditions without changing in dark and lite mode.

This is the current condition.

Thanks for assigning me the issue.
It was great working on this issue.


getSharedPreferences is useless

I couldn't find any way to share preferences between MuzeiArtSource and settingsActivity.
I know there is static getSharedPreferences, but it returns SharedPreferences, and then I couldn't find a way to use them in PreferenceFragment (or PreferenceActivity).
So in all plugins I found on Github, people still do this in MuzeiArtSource:
SharedPreferences prefs = PreferenceManager.getDefaultSharedPreferences(this);
boolean b = prefs.getBoolean("derp", false);

Solutions

Add another EXTRA to the Intent providing preferences name.
Add another static method for getting preference name.

We will then be able to do this in PreferenceFragment:
getPreferenceManager().setSharedPreferencesName("PrefsName");

Sure, we can use muzeiartsource_PrefsName these days, but it's undocumented. So maybe, document it is possible soulution number 3.

Good points; it might be useful to do option 3.

We've decided to remove the shared preferences APIs in Muzei 3.0's new API as Muzei no longer needs to store any specific shared preferences and it is better that you, as the developer, control your own shared preferences as needed.


rename idom to reactpy

closes: #888
Checklist
Please update this checklist as you complete each item:

[ ] Tests have been included for all bug fixes or added functionality.
[ ] The changelog.rst has been updated with any significant changes.
[ ] GitHub Issues which may be closed by this Pull Request have been linked.

There's a number of different png and gif files that will need to be updated to use the ReactPy name before this can go in. I have intentionally left the names of those files unchanged so they can be more easily found by searching for files with IDOM in their names.

I am going to begin work on the new docs based off import paths in this PR

@Archmonger, assuming no other changes are needed, I think we're ready to release 1.0 and execute the rename.

I think I condensed it down to one paragraph:

ReactPy is a library for building user interfaces in Python without Javascript. ReactPy interfaces are made from components which look and behave similarly to this found in ReactJS. Designed with simplicity in mind, ReactPy can be used by those without web development experience while also being powerful enough to grow with your ambitions. It has you covered whether you need to run a full blown application with a standalone server, or simply want try things out in a Jupyter Notebook.

ReactPy is a library for building user interfaces in Python without Javascript. ReactPy interfaces are made from components which look and behave similar to ReactJS. Designed with simplicity in mind, ReactPy can be used by those with minimal web development experience while also being powerful enough to grow with your ambitions.

Last sentence becomes unneeded if we're going for a hyper-minimal summary.

ReactPy has you covered whether you need to run a full blown application with a standalone server, or simply want try things out in a Jupyter Notebook.


[MOB-290] - url schemes for in-app clicked url

itbl:// for internal
action:// for other

This should probably target master, because it changes the in-app behavior that's already in beta.

Merging to master is going to be a major pain. It is pulling in dozens of commits.

The branch has to be rebased before that

OK. I rebased on master.


Fix Issue #141

This little bugfix will fix the Issue #141 , also #64 and #88

Could you please review unit tests?
--- FAIL: TestValidateStruct (0.00s)
	validator_test.go:2689: Expected ValidateStruct({"John"<EMAIL_ADDRESS>"123G#678" '\x14' %!q(*govalidator.Address=&{Street 123456}) [{"Street" "123456"} {"Street" "123456"}]}) to be false, got true
FAIL
FAIL	github.com/asaskevich/govalidator	0.394s

Hello guys!
I forked this package cause owner disappeared. Hope, he will be back, but it would be easier to merge these changes back if he is back
Link to my repo: create issue there and we'll discuss it.


Remote Maintenance Constraints

In GitLab by @jmorris-uk on Jun 14, 2019, 09:34
After DEMO configuration meeting and discussions with Oliver Crofts and Tony Loving, will look into best way forward for including remote maintenance considerations in PROCESS.
Mainly will involve:

Geometry and space allocation
Blanket segmentation and masses
Maintenance time
Costs (maybe)
Building sizes

I have move this to a discussion here https://github.com/ukaea/PROCESS/discussions/3288
for now I will close this issue.


browserHistory doesn't exist in react-router

import { browserHistory, Router, Route, IndexRoute } from 'react-router'

Shows error:
'react-router' does not contain an export named 'browserHistory'.

Here is the code Code
React version: v4

You have to install v3 of react-router. You have the wrong version installed.

Thanks! @timdorr I got it.
this link helped: npm-package@version
npm i @version/react-router-v3

That is not the right version and not a package we maintain. I wouldn't trust that. npm install react-router@3 is the correct way to install.

Is there any page where I can found some alternatives for browserHistory?
Such as:
for redirecting instead of using:
browserHistory.push("/back")

we can use
this.props.history.push("/back")

and pass it through an onClick function in your Component.
etc. etc.

https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/guides/migrating.md

Thanks man! that's awesome
Exactly what I wanted.


Fixes typo

@godrei @kdobmayer @trapacska pls review, merge & release ;)

Actually I'll do that myself ;)


mupdf: 1.19.0 -> 1.20.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/mupdf/versions.
meta.description for mupdf is: "Lightweight PDF, XPS, and E-book viewer and toolkit written in portable C"
meta.homepage for mupdf is: "https://mupdf.com"
meta.changelog for mupdf is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.20.0 with grep in /nix/store/bqy88c9pp0q9l2z2yfgmlps3yzpm71md-mupdf-1.20.0-bin
found 1.20.0 in filename of file in /nix/store/bqy88c9pp0q9l2z2yfgmlps3yzpm71md-mupdf-1.20.0-bin

Rebuild report (if merged into master) (click to expand)

29 total rebuild path(s)

29 package rebuild(s)

First fifty rebuilds by attrpath
arcanPackages.all-wrapped
arcanPackages.arcan
arcanPackages.arcan-wrapped
arcanPackages.durden-wrapped
arcanPackages.pipeworld-wrapped
arcanPackages.prio-wrapped
arcanPackages.xarcan
beamerpresenter
cups-filters
img2pdf
llpp
mcomix
mupdf
ocrmypdf
paperless-ngx
pdfarranger
python310Packages.img2pdf
python310Packages.ocrmypdf
python310Packages.pikepdf
python310Packages.pymupdf
python39Packages.img2pdf
python39Packages.ocrmypdf
python39Packages.pikepdf
python39Packages.pymupdf
sioyek
splix
system-config-printer
termpdfpy
zathura

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bqy88c9pp0q9l2z2yfgmlps3yzpm71md-mupdf-1.20.0-bin \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mupdf https://github.com/r-ryantm/nixpkgs/archive/31d30fecb95b58001e9bb1a132dc66f0c6d7ae2f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bqy88c9pp0q9l2z2yfgmlps3yzpm71md-mupdf-1.20.0-bin
ls -la /nix/store/bqy88c9pp0q9l2z2yfgmlps3yzpm71md-mupdf-1.20.0-bin/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages failed to build:

beamerpresenter
llpp
sioyek
zathura

24 packages built:

arcanPackages.all-wrapped
arcanPackages.arcan
arcanPackages.arcan-wrapped
arcanPackages.durden-wrapped
arcanPackages.pipeworld-wrapped
arcanPackages.prio-wrapped
arcanPackages.xarcan
cups-filters
img2pdf (python310Packages.img2pdf)
mcomix (mcomix3)
mupdf
ocrmypdf (python310Packages.ocrmypdf)
openlpFull
paperless (paperless-ng ,paperless-ngx)
pdfarranger
python310Packages.pikepdf
python310Packages.pymupdf
python39Packages.img2pdf
python39Packages.ocrmypdf
python39Packages.pikepdf
python39Packages.pymupdf
splix
system-config-printer
termpdfpy

Maintainer pings
cc @vrthra @fpletz for testing.

zathura seems affected by this: https://hydra.nixos.org/build/187797909

Opened as https://github.com/NixOS/nixpkgs/issues/187305


Update to plugins API 2.0

As this plugin is getting mentioned as an early plugin, let's make sure it is an actual consumer of the 2.0 API.

Duplicate of #16


Support for basic non-staking transactions

Add full support for basic non-staking transactions

registry.DeregisterEntity https://github.com/oasislabs/oasis-core/blob/master/go/registry/api/api.go#L218-L221
registry.UnfreezeNode https://github.com/oasislabs/oasis-core/blob/master/go/registry/api/api.go#L228-L231

Request and include updated test-vectors

Only test vectors are pending

@kostko @david-yan
This is basically merged and working in the dev branch, however, it would be good to have the corresponding test vectors before closing the issue.
If you think this may take a few more days, I can close this issue and open another one to track test vector integration.

Closing this issue and replacing with https://github.com/ZondaX/ledger-oasis/issues/24


[Feature] Token Encryption (JWE) Support

[ ] I read and understood how to enable logging

Issue / Steps to reproduce the problem
I am using Identity server to implement a centralized authentication/login service for all our internal applications and I need to  encrypt jwt claims (such as authorization information).  System.IdentityModel.Tokens.Jwt 1.5.3 and later versions supports encrypted tokens and I know I can do it myself by implementing custome TokenCreationService and TokenValidator classes
But I don't prefer to maintain those classes while using future versions of IdentityServer and I believe other users may also need to encrypt jwt claims for their projects.
It would be nice that IdentityServer4 has a built-in support for token payload encryption.
Relevant parts of the log file
<log goes here>

What do you want to encrypt? id_tokens or access_tokens? And why?

I want to be able to encrypt both id_tokens and access_tokens. I want to pass claims(userId, authorization ifnormation type of things) in jwt tokens between applications but I don't want clientapp/people who has the token to read my claims, at least I don't want them to read the claims easily.

Did you look into reference tokens?

IMO encrypting id_tokens does not make a lot of sense unless you want to hide information from end user (but the id_token is about the end user in essence).
Encrypting access tokens - can make sense - but requires extra key management - reference tokens seem easier here with same effect.

I don't want to make an extra network call to the identity server for every request to read claims, or call identity server once and store that claims on a distributed cache etc.
Even those claims that I want to encrypt aren't very sensitive information, I don't want to give any information to someone else to understand my business flow, or to have a data privacy risk etc.
On the other hand token encryption is not an idea that comes to my mind. There is already a proposed JWE standart (https://tools.ietf.org/html/rfc7516) for that and it is already implemented at System.IdentityModel.Tokens.Jwt so why not in IdentityServer?
Yes, extra key management is required but I don't think it would be a problem.

@alpersogukpinar Maybe you can create custom claim that extends default JWT claims and put your extra data in it. You can encrypt it, encode to base64 and put it to custom claim on IdentityServer side and extract and decrypt it on other side (API). On other side (API) you will exctract your payload from custom claim, decode it and do whatever you want (as example - you may assign decoded claims to user context). So you no need to change something inside IdentityServer. Just override some services to add some custom logic.
It really simple.
One thing that you should do by yourself - is key management for encryption and decryption on both sides. I think DPAPI is the best choice for this.
P.S. - sorry for my English) I just want to help))

I think this is a fair question, Why JWE is not supported ?
Using encrypted claims is not the right answer.
Can you please let us know if there is a plan to support JWE

It's on our todo list. You can do it easily yourself today by replacing the token creation service.


Encounter the RuntimeError when running train.py

Hello these days I've tried this code many times
But when I run the train.py it always crashed at the beginning
I follow the all instructions in your README.md
So I'm confused if there is anything I need to setting?
I run this command and use the original .yml file without modified
Hope you can help me~ Many thanks
python train.py -c configs/pgp_gatx2_lvm_traversal.yml -r /media/ee904/Data_stored/data/Nuscenes -d /media/ee904/Data_stored/data/Nuscenes/preprocess -o /media/ee904/Data_stored/PGP/results -n 100

I tried to print out the predictions in the trainer.py
and I found there is something strange for the 'pi' value is it normal to display nan value?

Yes I think it's because the value of op_masks
I tried to print  the output of pi but found nan, so I trace back and find if I print op_masks there would be some -inf value pop up so I tried to add one line of code to convert the inf to a big number
What's your opinion for these type of bug?

this is the result if I print the op_masks


EXC_BAD_ACCESS (code=1, address=0x4) in FIRCollectionReference.addDocument(data:)

Description
To my understanding this is a similar issue to https://github.com/firebase/firebase-ios-sdk/issues/13480

The app crashes when I write add ducoment to Firestore
Reproducing the issue
This happens everytime I try to create document using CollectionReference.addDocument
Firebase SDK Version
c570e44f78896bbce0fcd03f5e6539c6b81fd2d5
Xcode Version
Version 16.1 beta (16B5001e)
Installation Method
Swift Package Manager
Firebase Product(s)
Firestore
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

I'm closing my own issue because this issue can be resolved by updating to the latest XCode Beta version.


Use zarr to validate attrs when writing to zarr

[x] Closes #6448
[x] Tests added
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst
~New functions/methods are listed in api.rst~

I think we can just use zarr to validate attributes, so we can support all types allowed by zarr.
Note that I removed the checks on the keys, as I believe we can rely on zarr for that as well. However, there is an issue with mixed types (e.g., attrs={"a": "foo", 1: "foo"}), but I think that needs to be addressed in zarr. See: https://github.com/zarr-developers/zarr-python/issues/1037
cc: @wankoelias @rabernat

All set. Thanks everyone!

Thanks @malmans2


Where to place diffuse color.

Hello.
How to correctly mix diffuse color of planet underneath atmosphere?
I assume, there is something like
vec4 groundDiffuseColor = texture(screenspaceRenderedPlanet, uv);

In my shader.
How to mix them with ground_radiance?

You should replace kGroundAlbedo with groundDiffuseColor in
ground_radiance = kGroundAlbedo * (1.0 / PI) * (
sun_irradiance * GetSunVisibility(point, sun_direction) +
sky_irradiance * GetSkyVisibility(point));
(in demo.glsl). groundDiffuseColor should be an albedo (i.e. fraction of incident light which is reflected, between 0 and 1).


Logged out immediately after logging in

 Issue by typhoon2099
Thursday Apr 05, 2018 at 12:03 GMT
Originally opened as https://github.com/catalogueglobal/datatools-ui/issues/70

I'm still not sure if I've configured Auth0 correctly. I've checked the Auth0 logs and appear to be getting a failed silent auth on the login page, after which I can log in, but I don't get to do anything before I've been logged out by the frontend. Auth0 logs it as a successful logout.
I notice when I'm on the homepage that /api/manager/public/region returns a 404 (message: Unknown error occurred), could this be causing the frontend to panic and kick me out?
Just to note: I'm using the auth0-update-sql branch as I can't get Auth0 to work on the dev branch (hard coded URLs etc).

 Comment by landonreed
Tuesday Nov 13, 2018 at 19:01 GMT

I believe this should be solved with #250 now.

@landonreed  I have still have this issue on master branch.
Failed Silent Auth .

@gelinger777, did you happen to see/follow @karimhm's final comments on https://github.com/ibi-group/datatools-ui/issues/441#issuecomment-497459261

@landonreed  that fixed the issue with logging in, but still I have this

@landonreed  yes, that was the reason. It's fixed. thank u

:tada: This issue has been resolved in version 4.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Validation specific Exception type.

Describe the feature you'd like
When submitting a task/job it would be good to distinguish an python exceptions from Validation from other possible exceptions that can occur during the submission, for example:
try:
    task = device.run(discretized_ahs_program, shots=shots)
except braket.ValidationException as e:
    print(str(e))

which would error if discretized_ahs_program wasn't the correct type of object or shots wasn't an integer, or other failure modes that live deeper inside of AWS software stack that I am not aware of.
How would this feature be used? Please describe.
I would like to be able to safely saving validation errors without having to worry about catching non-validation errors.
Describe alternatives you've considered
I could parse the error message to check if it follows a particular format consistent with a Validation error.

Nvm, I just read the boto3 docs and I think I found the exception that I need.


Cleanup the heartbeat records based on the retention

Signed-off-by: myan<EMAIL_ADDRESS>

/lgtm

/lgtm


CVE-2007-4559 Patch

Patching CVE-2007-4559
Hi, we are security researchers from the Advanced Research Center at Trellix. We have began a campaign to patch a widespread bug named CVE-2007-4559. CVE-2007-4559 is a 15 year old bug in the Python tarfile package. By using extract() or extractall() on a tarfile object without sanitizing input, a maliciously crafted .tar file could perform a directory path traversal attack. We found at least one unsantized extractall() in your codebase and are providing a patch for you via pull request. The patch essentially checks to see if all tarfile members will be extracted safely and throws an exception otherwise. We encourage you to use this patch or your own solution to secure against CVE-2007-4559. Further technical information about the vulnerability can be found in this blog.
If you have further questions you may contact us through this projects lead researcher Kasimir Schulz.

Thank you for letting us know. We are not accepting the pull request, but we did implemented the change ourselves.


Cannot resolve forward reference in type annotations of "p1.my_class.Subclass": name 'MyEnum' is not defined

Please, see https://github.com/sphinx-doc/sphinx/issues/11460 first.
So, after having read that, you should know that someone suggested me to open the same issue here. I don't know if this is related to sphinx-autodoc-typehints, but I'm opening it here in case it's and in case you know a solution or I'd like to tackle the problem.

PR welcome.


⚠ Bofrost.de has degraded performance

In 31477d9, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1509 ms

Resolved: Bofrost.de performance has improved in 607ef89 after 34 minutes.


Fix up form flashing on load if it's already been filled

If you've already filled in the form, then it'll flash on the screen before turning into the "You've already filled in the contributor form." message.
It's because after the query succeeds, loading stops, but setFormFilled is called only moments later in the onSuccess function... I didn't catch it earlier because it was fast before the preview being deployed in Sydney.
This is not a very neat way of doing it, open to other approaches.

Not sure I fully follow this... shouldn't the query loading state got you covered? So this is a workaround to ensure already filled is set first by blocking it with another loading state before unsetting?
Yeah seems a bit hacky (on top of all of that crazy CSV stuff 🙈 )... unfortunately don't have time until probably tomorrow to properly look into this to suggest anything better

I think setting  defaultValue on the form elements should work without needing the hack. Since the form isn't rendered until it is loaded, user should be populated by the time those elements are created

I think the onSuccess runs after queryLoading is set to false, so it causes a render just before onSuccess hides it again.
For the default values: we hide those fields if the user is logged in, they don't modify them, so defaultValue doesn't really work

Does this form show anywhere where the user is not logged in?

Yes, there's an extra page, /contribute if we want to just directly link it to people externally

It might be that I just don't understand react query loading states

Okay, I fixed it up better: no need for an extra state variable, just read it from the data. I also noticed the contributor info was not invalidated after submitting the form, which now mattered as the data was used.

Okay, I fixed it up better: no need for an extra state variable, just read it from the data.

That was literally what I was gonna suggest next but only got time to come on here now 👍  nice refactor on the query key too


TrackBy for arrays

it would be interesting if we could define a field by which we track objects inside array(similar as angular.js or vue.js does it)
This way we could precisely tell which objects were deleted/added to an array when doing a diff

Yeah, that's definitely possible. I'd welcome a PR to do that, or some sort of LCS detection.


de-duplicate CAs added to the CA bundle, returned from .well-known/est/cacerts

If one configures their environment with multiple identity blocks of different types, including the signing cert, the CA pool that is returned from  .well-known/est/cacerts can have duplicate certificates listed. while that's not a big deal, it's not necessary.
It'd be better to de-dupe the certs as they are added to the pool.
Steps to reproduce

run the host it anywhere quickstart
issue curl -sk https://"${ZITI_EDGE_CTRL_ADVERTISED_HOST_PORT}/.well-known/est/cacerts"   | openssl base64 -d   | openssl pkcs7 -inform DER -outform PEM -print_certs -text   | grep -A1 'Serial Number'
observe at least two duplicated certificates by serial number (example output below)

curl -sk https://"${ZITI_EDGE_CTRL_ADVERTISED_HOST_PORT}/.well-known/est/cacerts"   | openssl base64 -d   | openssl pkcs7 -inform DER -outform PEM -print_certs -text   | grep -A1 'Serial Number'
        Serial Number:
            70:6b:12:fb:56:d1:ec:65:26:b7:5b:b0:d7:9b:c4:b0
--
        Serial Number:
            62:24:2b:29:81:12:86:21:92:c3:55:68:96:ec:9b:ec
--
        Serial Number:
            7d:e3:4e:05:90:9b:c3:4f:7a:cf:d5:92:00:03:17:26
--
        Serial Number:
            70:6b:12:fb:56:d1:ec:65:26:b7:5b:b0:d7:9b:c4:b0
--
        Serial Number:
            2a:66:d4:f6:95:36:23:fa:0d:02:dd:f8:17:df:72:88
--
        Serial Number:
            2a:66:d4:f6:95:36:23:fa:0d:02:dd:f8:17:df:72:88

same command, grepping for Subject: instead and sorted/counted:
curl -sk https://"${ZITI_EDGE_CTRL_ADVERTISED_HOST_PORT}/.well-known/est/cacerts"   | openssl base64 -d   | openssl pkcs7 -inform DER -outform PEM -print_certs -text   | grep 'Subject:' | sort | uniq -c
      2         Subject: C=US, L=Charlotte, O=NetFoundry, OU=ADV-DEV, CN=ec2-18-225-8-209.us-east-2.compute.amazonaws.com-intermediate
      1         Subject: C=US, L=Charlotte, O=NetFoundry, OU=ADV-DEV, CN=ip-172-31-45-134 server certificate
      1         Subject: C=US, L=Charlotte, O=NetFoundry, OU=ADV-DEV, CN=ip-172-31-45-134-intermediate
      2         Subject: C=US, L=Charlotte, O=NetFoundry, OU=ADV-DEV, CN=ip-172-31-45-134-signing-intermediate

This may have been fixed or may not be applicable to ziti edge quickstart.
/tmp/tmp.BQWPg2jpCC
❯ nohup ziti edge quickstart --home $PWD &> ./quickstart.log &
[1] 1094882

/tmp/tmp.BQWPg2jpCC
❮ curl -skSf https://<IP_ADDRESS>:1280/.well-known/est/cacerts \
  | base64 -d \
  | openssl pkcs7 -inform DER -outform PEM -print_certs \
  > ./bundle.pem

/tmp/tmp.BQWPg2jpCC
❮ openssl storeutl \
    -certs \
    -noout \
    -text \
    /tmp/cas.pem 2>/dev/null \
| grep -E '(Subject):'

/tmp/tmp.BQWPg2jpCC
❯ openssl storeutl -certs -noout -text ./bundle.pem 2>/dev/null \
| grep -E '(Subject):'
        Subject: C=US, L=Charlotte, O=NetFoundry, OU=ADV-DEV, CN=intermediate-ca
        Subject: C=US, L=Charlotte, O=NetFoundry, OU=ADV-DEV, CN=root-ca

per @andrewpmartinez it is done


Service Instances cascading delete proposal

Service Instances cascading delete proposal
This is the umbrella issue for the Service Instances cascading delete operation.
In this issue, we also track the implementation of this functionality from alpha to GA stage.
Motivation
Currently, during the deprovisioning operation, the default case is to fail the deprovisioning if there are bindings against the instance being deprovisioned.

Problems:

Users expect that deleting a Kubernetes API resource results in the total deletion of resources associated with the API resource
Not going back once deletion timestamp is set

OSB API Spec states:

Platforms MUST delete all Service Bindings for a Service Instance prior to attempting to deprovision the Service Instance. This specification does not specify what a Service Broker is to do if it receives a deprovision request while there are still Service Bindings associated with it.

source: https://github.com/openservicebrokerapi/servicebroker/blob/v2.15/spec.md#deprovisioning
Discussions

https://github.com/kubernetes-sigs/service-catalog/issues/46
Issue created on Nov 22, 2016

remove first the instance then remove the bindings.

https://github.com/kubernetes-sigs/service-catalog/issues/481
F2F meeting in late January, 2017

On a deprovision operation, we decided that the default case is to fail the deprovision if there are bindings against the instance being deprovisioned. A "force" or "cascade" flag can be explicitly set on the call to make all bindings be unbound, and then the deprovision be done.

https://github.com/kubernetes-sigs/service-catalog/issues/820
F2F meeting on May 9, 2017

When a user attempts to delete an instance (ie kubectl delete instance) Catalog will check if any bindings are associated with the instance. If there are, the operation will fail with an error indicating that the instance is in use. The user can repeat the operation with a -force flag. In this case, the instance will be marked as soft deleted. Instances that don't have bindings will be deleted immediate with or without the force flag.

https://github.com/kubernetes-sigs/service-catalog/issues/2229
F2F meeting on Jul 23, 2018

We decided that the object that owns other objects should recursively delete everything that these objects own in case they are deleted.

Action
Description of Scenario
What we do / What will happen

Delete Instance
Has bindings, broker allows it
"Depth First Deletion": Cascade delete the bindings from the Broker. Once all bindings are deleted, delete the instance (blockOwnerDeletion, foreground deletion). Instance status says something like "Deprovision will start after bindings are unbound" instead of "Can't deprovision until all bindings are unbound" (current wording)

Proposed behaviors
Based on the discussions above, there are four proposed options:

Use the kubectl --cascade flag

--cascade=true: If true, cascade the deletion of the resources managed by this resource (e.g. Pods created by a
ReplicationController).  Default true.

Basically, under the hood, the propagationPolicy is applied on a given resource. In case of cascade=true, it is propagationPolicy=foreground. In case of cascade=false, it is propagationPolicy=background. The propagationPolicy is managed by the Kubernetes Garbage Collection.

However, this option cannot be considered because of the expected behavior:
The ownerReference cannot be used because of a problem when a user sets the --cascade=false option. In such case, Kubernetes requires the propagationPolicy=background.

 Implementing the background behavior is not an option in the case of Service Catalog.

Global flag for changing the behavior
Add the disable-cascading-deletion=<true/false> flag for the Service Catalog controller-manager. This flag globally changes the behavior of the controller-manager.

ServiceInstance spec property changes
We can add the deleteBehavior field under the Instance spec. The field has two possible behaviors: forceCascade or failOnBindings. In the former case, deleting an instance force-deletes all Bindings that reference the instance, without confirming with the person who deletes it. In the latter one, the deletion simply fails if there are bindings that reference the instance. *This field will be optional and it will default to failOnBindings.

Always perform cascade deletion
When a user deletes a ServiceInstance, the related ServiceBindings are deleted (execute the unbind call to the broker). When all ServiceBindings are deleted successfully, the ServiceInstance is also deleted (execute the deprovision call to the broker).

Accepted solution
Based on the client feedback and OSB API specification, we know that we want to implement this behavior and to do it safely we decided to go with the 2nd option: Global flag for changing the behavior.

Reasons:

OSB API Spec:

Platforms MUST delete all Service Bindings for a Service Instance prior to attempting to deprovision the Service Instance. This specification does not specify what a Service Broker is to do if it receives a deprovision request while there are still Service Bindings associated with it.

source: https://github.com/openservicebrokerapi/servicebroker/blob/v2.15/spec.md#deprovisioning

If Users expect that deleting a Kubernetes API resource results in the total deletion of resources associated with the API resource then they can set the disable-cascading-deletion flag to true and controller-manager will take care about that.

This solution was accepted and the alpha implementation has already been added in this PR: https://github.com/kubernetes-sigs/service-catalog/pull/2711. Starting from the Service Catalog version 0.3.0, you can enable this option by setting the CascadingDeletion feature gate to true. Users, who do not accept cascading deletion, the controller-manager provides a flag disable-cascading-deletion which blocks the feature even if the cascading deletion is enabled by default (in the future).
ACTION REQUIRED
Going with this behavior is backward compatible. It was implemented as alpha.
We are waiting for your feedback and use-cases if this approach happens to break your flow. It's unacceptable for us, so please let us know.

/remove-lifecycle rotten

ICYMI:
The Cascading binding deletion feature is officially available in 0.3.0 release. The controller manager deletes all Service Bindings for a Service Instance before attempting to deprovision the Service Instance. This option can be enabled by setting the CascadingDeletion feature gate to true (#2711)

/remove-lifecycle rotten
/reopen
/lifecycle frozen

This project is being archived, closing open issues and PRs.
Please see this PR for more information: https://github.com/kubernetes/community/pull/6632


Backlinks don't work in computables when the link is defined in an abstract class

EdgeDB Version: Alpha 5
OS Version: Mac OS 10.15.6

Steps to Reproduce:
Create a schema where a computable link uses a backlink for a link defined in an abstract class
For example the following schema:
abstract type Action{
    required property txid -> str{
        constraint exclusive;
    }
    required property timestamp -> int32;

        required link user -> User;

}

type Post extending Action{
  ...
}

type User {
  ...
  posts := .<user[IS Post];
}

produces the error: InternalServerError: reference to an undefined item default::Post@user in default::User@posts
If I don't include the IS intersect, i.e.:
type User {
  ...
  posts := .<user;
}

I get the following error: SchemaError: cannot get 'name' value: item '3b64a89d-50f4-e418-acaa-c19c327e41d9' is not present in the schema <Schema gen:4106 at 0x7f857a0be820>

Two bugs here:

SDL dependency sorter gets confused about inheritance.
Opaque union types produced by naked backlinks don't get added to the schema properly (I opened #1830).


Python SDK System Datastore Auth AML

Description
This PR is to add the System Datastore Auth method to the Python SDK for AML Credential-less datastores
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml

Based on https://github.com/Azure/azure-sdk-for-python/pull/28879


[Concurrency] Make #isolation macro expansions explicit.

Macro expansions are never considered implicit. They have valid source locations in their macro expansion buffer, they do not cause implicit self capture diagnostics, etc.
This fixes an issue where existing code that iterates over an async sequence in an escaping closure would diagnose a use of implicit self via the #isolation argument to next().
Resolves rdar://122578942

@swift-ci please smoke test

@swift-ci please smoke test


namespace resolution

rebar3 unstable compile will use a compiler in the unstable namespace, but rebar3 unstable eunit will not use a compiler in the unstable namespace even if it exists. i think it probably should. i also think that rebar3 unstable eunit should succeed even if there's no unstable eunit provider, using unstable versions of any of it's dependencies if available

That would entirely break how namespaces work, though. The resolution is always local to the namespace, and if you want another one, the provider has to mention the remote namespace. I.e. unstable eunit needs to depend on {default, compile} as a provider to depend outside of its scope.
The main objective being to give other languages or suite developers a way to completely own a part of their development stack without conflicting with the default stuff.

Right, all you have to do is put the dep as [{unstable, compile}] for the unstable eunit to use it.

right, but i want the opposite. i want to use the default eunit with an unstable compiler which as far as i can tell is impossible

I think that would conflict with the current behaviour, which we intend to keep.


Allow Hygieia UI to see Hygieia Status and Critical Errors

UI option should allow the user to view

collector status, error
api status, errors

somewhat related; internally we have on our backlog to look at exception handling in Hygieia. anticipate more to come on it in 2017.

We currently do this somewhat in the current dashboard. https://github.com/capitalone/Hygieia/pull/1765. More to come on the rest of this.


Updated configs for ci

Fixed scrutinizer sync
Updated labels

Pull Request Test Coverage Report for Build 462917300

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 39.878%

Totals

Change from base Build 446154287:
0.0%

Covered Lines:
262

Relevant Lines:
657

💛  - Coveralls

Pull Request Test Coverage Report for Build 462917300

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 39.878%

Totals

Change from base Build 446154287:
0.0%

Covered Lines:
262

Relevant Lines:
657

💛  - Coveralls

Pull Request Test Coverage Report for Build 462917300

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 39.878%

Totals

Change from base Build 446154287:
0.0%

Covered Lines:
262

Relevant Lines:
657

💛  - Coveralls

Pull Request Test Coverage Report for Build 462917300

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 39.878%

Totals

Change from base Build 446154287:
0.0%

Covered Lines:
262

Relevant Lines:
657

💛  - Coveralls


3-dots button should be in the corner of the screen

Current Implementation
This is obviously one of the most pressing issues with the app right now: the 3-dots menu button isn't in the corner of the screen - there is a slight narrow gap in between the button and the corner of the screen

Suggested Enhancement
put the menu button in the corner - as it is with literally every other Android app
this is a screenshot of the Gmail app:

Expected Benefits
people being able to open the menu without having sniper-like accuracy

Internal Tracking ID: EXPOSUREAPP-3173

Hey @orangebutblue ,
Thank for the feedback. I have added a ticket to the internall Jira that contains your suggestion. The devs will now have a look at it and then decide when and how they implement the change. Status updates will be posted in this issue thread.
Regards,
CH

Corona-Warn-App Open Source Team

I think it depends on the OS. For me, all android apps have it as the cwa – or on the left-hand side, e.g. gmail:

or Telegram:

@shoeffner those are two different things.
This entire region is called the 'top bar'.
Your first image (Gmail) shows the hamburger menu/navigation icon (3 dashes on the left). That's used for sliding in a menu from the left side of the screen.
The bottom picture shows the menu overflow (3 dots on the right), which is part of the action items in the top bar. Icons that don't fit into this bar (because of size restraints) will overflow into the overflow menu. The narrower the screen, the fewer icons can be displayed in the bar - the more will overflow

Hm, the message view also has the dots there,
(see attachment), but I don't know about this overflow menu. Guess my old
phone always has enough vertical space. Thanks for clearing this up!
On Mon, Oct 12, 2020, 21:54 orangebutblue<EMAIL_ADDRESS>wrote:

@shoeffner https://github.com/shoeffner those are two different things.
This entire region is called the 'top bar'.
Your first image (Gmail) shows the hamburger menu/navigation icon (3
dashes on the left). That's used for sliding in a menu from the left side
of the screen.
The bottom picture shows the menu overflow (3 dots on the right), which is
part of the action items in the top bar. Icons that don't fit into this bar
(because of size restraints) will overflow into the overflow menu. The
narrower the screen, the fewer icons can be displayed in the bar - the more
will overflow
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-android/issues/1377#issuecomment-707315375,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOAOD42VECXY26TWIIFKR3SKNNIPANCNFSM4SK423TQ
.


Add Media Central oEmbed provider (#305)

Codecov Report

Merging #357 (d506e2f) into develop (95a5cc0) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop     #357   +/-   ##
========================================
  Coverage    97.91%   97.91%
========================================
  Files           90       90
  Lines         3556     3557    +1
========================================
+ Hits          3482     3483    +1
  Misses          74       74


Only override integrated strategy in Neotest

Currently, Overseer only respects the strategy passed to run, but it should respect the default strategy if it's not integrated.
For example, if I change the default strategy for a project, I expect tests to run with that strategy and not with the overseer one even if I don't pass it to run explicitly.

Consumer should respect the default_strategy now

Works properly. Thanks!


fix: import duplicate components when add routers

Fix: 添加页面时，路由配置文件中重复引入组件的问题

Codecov Report

Merging #947 (45389c2) into release/1.4.1 (9528cb7) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release/1.4.1     #947   +/-   ##
==============================================
  Coverage          57.14%   57.14%
==============================================
  Files                  1        1
  Lines                 70       70
  Branches              18       18
==============================================
  Hits                  40       40
  Misses                30       30

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 9528cb7...45389c2. Read the comment docs.


Making sure that gpr_free is a no-op for NULL input.

I personally don't think this is necessary.  I would consider any implementation of free() that does not ignore NULL to be broken.
That having been said, if Craig has no objection, then I'm okay with it too.

If my understanding is correct, the free function can be user supplied (custom allocators). If this function, over which we have zero control over, does not do this check, grpc will crash badly in some unexpected manner.
Adding this check gives me that warm and fuzzy feeling...

I don't think it's necessary, and I noted that earlier, but I also don't object.

Part of the free contract is that NULL is a valid argument with no value. If that's also part of the free_fn contract, then this could instead be tested in alloc_test.c and leave the library alone instead, right?

I'm not sure how we can test that in alloc_test.c since I can't think of a
way to run these tests after the user of the API has called
gpr_set_allocation_functions.
Now, I'm OK removing this check in gpr_free and having a more precise
documentation for gpr_set_allocation_functions(...).
On Thu, Apr 13, 2017 at 9:52 AM, Vijay Pai<EMAIL_ADDRESS>wrote:

Part of the free contract is that NULL is a valid argument with no value.
If that's also part of the free_fn contract, then this could instead be
tested in alloc_test.c and leave the library alone instead, right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/10633#issuecomment-293958751, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF-P7QVv8PsYys3CgDtCvazI2UNUZxNvks5rvlLigaJpZM4M86wA
.

Please see new diff and let me know if that works for you.

Performance differences noted:
Benchmark                                         cpu_time    real_time
----------------------------------------------  ----------  -----------
BM_MetadataFromStaticMetadataStringsNotIndexed      +11.00       +11.00

Performance differences noted:
Benchmark                                               cpu_time    real_time
----------------------------------------------------  ----------  -----------
BM_CallCreateDestroy<InsecureChannel>                    -199.00      -199.00
BM_CallCreateDestroy<LameChannel>                        -221.00      -221.00
BM_HpackParserParseHeader<IndexedSingleInternedElem>       +6.00        +6.00
BM_IsolatedCall_NoOp                                     -248.00      -248.00
BM_IsolatedCall_Unary                                    -382.00      -382.00
BM_LameChannelCallCreateCpp                              -997.00      -997.00
BM_PollEmptyPollset_SpeedOfLight/1/1000                    +8.00        +8.00


Broken github link

https://github.com/singh_kshitij should be pointing to https://github.com/singhkshitij

Ohh okay.. I dont know how i missed that 👍  Thanks , will fix it !


Geode-4950 + GEODE-4951: Upgrade spotless version and reduce run time.

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[n/a - build] Have you written or updated unit tests to verify your changes?

[n/a] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Getting some strange behavior in gradle when run with the initial compile tasks / ./gradlew --rerun-tasks.

Precheckin railed due to GEODE-4963 but was green otherwise.


The conditioning_only decoder.

What's the mean of conditioning_only decoder? I checked the source code but still not understand the different between conditioning_only and model_only . Has any explanation with them.

The architecture we are using is similar to WaveRNN, in the sense that it has 2 different networks. The conditioning network that runs once for every frame, upsampling the input conditioning features to the sample rate. And the model network that runs once for every sample, combining the output of the conditioning network with the state of the previous samples to generate the next sample in an autoregressive fashion. When benchmarking we report the time for each of these networks, as well as the combined total.

Thanks for your response. I want to know :
The audio quality of conditioning_only decoder.  Which is better, conditioning_only or model_only ?  And which type of decoder in the guide of README.md when the command is "babel-bin/decoder_main  --model_path=wavegru" . How can I get the generate audio for conditioning_only decoder.

Oh, sorry I wasn't clear. Lyra always uses conditioning and model networks. There is no way to generate audio with conditioning only. We only report the complexity of each network separately in the benchmark tool to have a finer grain understanding of the computational complexity of different networks.

I got it. thanks!


test: Fix test_i18n.test_json_error().

The refer_friend endpoint is about to be deprecated, so we
test with invite_users instead, and I tried to make the
dummy value returned by the mocked gettext function a little
more clear.

Automated message from Dropbox CLA bot
@showell, it looks like you've already signed the Dropbox CLA. Thanks!


Install NAVSipCryptoProvider only successfully executed every second time

Describe the issue
Prerequisite: Always started PowerShell "As Administrator".

Start Powershell and execute Install-NAVSipCryptoProviderFromBcContainer -containerName "DoesNotMatter". It will be
executed successfully.
Close the window.
Repeat step 1. An error message will occure.

Full output of scripts
PS C:\Windows\system32> Install-NAVSipCryptoProviderFromBcContainer R-DE-14-17
Copy SIP crypto provider from container R-DE-14-17
Copy from container R-DE-14-17 (C:\Windows\System32\NavSip.dll) to C:\Windows\System32\NavSip.dll
Move-Item : Cannot create a file when that file already exists.
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\1.0.13\Misc\Copy-FileFromNavContainer.ps1:40 char:13
+             Move-Item -Path $tempFile -Destination $localPath -Force
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Windows\System32\NavSip.dll:FileInfo) [Move-Item], IOException
    + FullyQualifiedErrorId : MoveFileInfoItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand

Additional context

It doesn't matter which container I'm using.

BcContainerHelper is version 1.0.13-dev
BcContainerHelper is not running as administrator
Host is Microsoft Windows 10 Enterprise - 1909
Docker Client Version is 19.03.13
Docker Server Version is 19.03.13

BcContainerHelper version doesn't matter, also occured in older versions. Same for Docker.

Shipped in 1.0.15-preview269


Port NUnit based tests to Core CLR

PR for #690
This version keeps NUnit 3.0 as the test framework.
The Core CLR version of FSharp.Core.Unittests now compiles to an exe, and uses NUnitLite as the test runner.
Alternative to #699, which uses xUnit.net

This is really nice!!!!

Yesterday @PatrickMcDonald I updated all of the project jsons to use the latest RC2 version of the .Net framework.  That may!!!! explain the failures.
Kevin

great job @PatrickMcDonald !!

@PatrickMcDonald, @enricosada --- hey guys, I love this PR, the changes look great, although I expect you have both stomped over similar sets of files.  What additional work is needed before I pull this.  Or should I just pull it and fixup the issues?
Kevin

I'll update my pr if you pull this one.
This pr is really good, if this doesnt build and you want to pull in, i'll check this weekend and fix issues.
Is nice yo have nunit runner working in coreclr, i can use that for fsharp suite

There's just the 2 tests failing, both due to Reflection errors I think, but I'm not sure how to fix them.. Upgrading to Core CLR RC2 did not fix.  The choices are to fix or ignore the tests or leave them failing. I'd welcome guidance on how to proceed!

I think you can disable the failing tests and open an issue with details about failure.
For example there are some failing tests with  NO_CI tags.
So pr can be merged and we can fix later.

Okay I am going to try to bring these into the coreclr branch ....
wish me luck :-)

hehe, good luck!

Thank you so much for this, its awesome.

:+1: great!

fab


Add missing translations, remove duplicate ones

Merci!

Merci!

De rien ! ;o)
I use a quick command to compare translation files :
> php artisan h3d:checktranslations plugins/winter/blocks/ en fr

Comparing translations.

Missing EN translations found
+----------------------------------+-------------------------------+
| EN keys missing in FR            | Value                         |
+----------------------------------+-------------------------------+
| missing_en                       | New EN key missing in FR      |
| actions.open_url.missing_deep_en | New EN deep key missing in FR |
+----------------------------------+-------------------------------+

Extras FR translations found
+----------------------------------+------------------------------------+
| Extras FR keys not found in EN   | Value                              |
+----------------------------------+------------------------------------+
| extra_fr                         | Extra FR key no more required      |
| actions.open_media.extra_deep_fr | Extra FR deep key no more required |
+----------------------------------+------------------------------------+

@damsfx feel free to submit that command as a PR to the winter core, maybe as a winter:util subcommand for now

We also have support for programmatically interacting with the localization files now so perhaps we could add support for making the changes directly from the command line as well! 🤯


Fix a couple of performance issues in peak_local_max (improve performance of blob detectors and corner_peaks)

It seems that we can get a large speedup in calls to peak_local_max when the default min_distance=1 is specified. A bottleneck in that function can be the call to ensure_spacing which falls back to the CPU, but we don't need to call that function at all unless min_distance>1 (no coordinates can be excluded if min_distance=1, so it is pointless to call it).
I proposed the same changes upstream in https://github.com/scikit-image/scikit-image/pull/7548. See additional comments and measurements made there.
There should be no change in behavior with this MR, it is purely a performance improvement.

/merge


Split larval ventral sensory clusters and neurons into v and v'

Most recent papers seem to use v and v' rather than calling everything 'ventral'
See FlyPNS paper - FBrf0183734
These can probably be subclasses of the existing 'ventral' terms

might be best to rename original term to 'larval ventral sensory cluster group' - 'ventral sensory cluster' in the literature usually seems to mean just the v cluster.