bv__dry_run function is a required function for each module, but does nothing

In the build system, there are 13 required functions for each module. One of these is bv_<module>_dry_run, which, as far as I can tell, does nothing. I have examined the implementations of this function for every single module we currently have, and each one is identical and looks like this:
function bv_<module>_dry_run
{
    if [[ "$DO_<module>" == "yes" ]] ; then
        echo "Dry run option not set for <module>."
    fi
}

I'm guessing at some point this function did something. build_visit won't let you get away with removing the function from any bv_<module> file. Is this something that should be fixed? Just for code cleanup reasons? Is there a reason it exists as it currently does?

We should remove this.

If/when this is removed, whoever works on it should find the comments at the beginning of build_visit and remove the instructions relating to bv_<module>_dry_run.


Updated Minor Typo

Updated the minor typo requested in below issue:
MicrosoftDocs/azure-docs#25629

@angoyal-msft : Thanks for your contribution! The author, @ronortloff, has been notified to review your proposed change.

Verified the update; merging.
@angoyal-msft Thanks!


COR-2752-add-privacy-manifest-ios

Changes

added privacy manifest

#198  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jsalaber and the rest of your teammates on  Graphite


Fix h3Line test

Thanks to @isaacbrodsky for catching!

Pull Request Test Coverage Report for Build 86

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 100.0%

Totals

Change from base Build 84:
0.0%

Covered Lines:
402

Relevant Lines:
402

💛  - Coveralls


SSR is very agressive!

Trying to upgrade to 9, and I've got some code that talks to window.localStorage that only runs in the browser, but bankai 9 is trying to run this on the server.
I don't need/want to install global/window here since this code will only ever run on the client (it's part of the app wrapper we use) -- are we going to require all code that uses window or document or another browser-only object to properly shim it for node?

This still an issue? Greenkeeper shouldn't have pinged to update to this
one, given it shouldn't be marked as "stable" :(
On Mon, Sep 11, 2017 at 10:54 PM Todd Kennedy<EMAIL_ADDRESS>wrote:

Trying to upgrade to 9, and I've got some code that talks to
window.localStorage that only runs in the browser, but bankai 9 is trying
to run this on the server.
I don't need/want to install global/window here since this code will only
ever run on the client (it's part of the app wrapper we use) -- are we
going to require all code that uses window or document or another
browser-only object to properly shim it for node?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/choojs/bankai/issues/234, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWlenGRF2qxVBsODTT--6EwY7KmTLRLks5shZ3_gaJpZM4PTwbg
.

I stumbled into this as well ;)

The versioning issue should be fixed now. Agree with the sentiment that SSR should be a gentle improvement, not fail loudly if it doesn't work - think new branch should take care of that! :D


How to use multiple Vec from js

Summary
How to use js array Uint8Array as Vec<u8> or [u8] in wasm
file_bufs is here

 wasm.apngEncode(file_bufs);

#[wasm_bindgen (js_name = apngEncode)]
pub fn apng_encode(data: Box<[u8]>) {
    console_log!("{:?}", data);
...

console_log result here
[0, 0, 0]

Ideally, I wanna use multiple files buffer (Uint8Array) as Vec<Vec<u8>>

Thanks for the report! Currently Vec<Vec<u8>> isn't supported so you'll want to take a js_sys::Array and then you can iterate over that, cast objects to Uint8Array, and then use copy_to to extract the contents. Does that work for you?

@alexcrichton
Thank you for it, But I don't know how to cast object to Uint8Array.
Array is contents here. (this is log)
Array { obj: Object { obj: JsValue([Uint8Array, Uint8Array]) } }

iterate val is JsValue(Uint8Array)

In the next release you'll be able to use foo.to_vec() to convert a Uint8Array to a Vec<u8>, so you can do this:
#[wasm_bindgen (js_name = apngEncode)]
pub fn apng_encode(data: Array) {
    let data: Vec<Vec<u8>> = data.values().into_iter().map(|x| {
        x.unwrap_throw().unchecked_ref::<Uint8Array>().to_vec()
    }).collect();

(You'll need to import the wasm_bindgen::JsCast trait in order to use unchecked_ref, be careful, unchecked_ref doesn't do any type checking, so you have to make sure it really is a Uint8Array)

Going the other way around, you can use Uint8Array::from(&foo) to convert a Vec<u8> into a Uint8Array, and you can convert a Vec into an Array by using the standard Rust collect, like this:
let array: Array = data.iter().map(|x| Uint8Array::from(&x)).collect();

@Pauan Thank you this proposal.
That's sounds good! This is exactly the thing I wanted.
When can I use it?


Allow unwrapping scalar Prometheus values

Prometheus returns scalar values as strings in order to support NaN, Inf, and -Inf. Unfortunately, this makes it quite difficult to use the Toolkit's jsonpath support to filter based on these scalar values, as jsonpath2 does not perform comparisons between numbers and numbers formatted as strings.
I would like to use the following tolerance to ensure a metric is within a certain range:
{
    "type": "jsonpath",
    "path"<EMAIL_ADDRESS>> 90)]",
    "count": 1,
    "target": "stdout"
}

In order to do so, I am currently relying on a custom probe script which will fetch the Prometheus metrics and reformat the scalars represented as strings into floating point values. I think this would be useful functionality to have in the Prometheus extension, and it is easier to implement the change here than in jsonpath2.

Im not clearly understanding how to run this experiment. I cloned this repo and inside chaosprometheus dir, I created a experiment.json with the given example. It says - " hypothesis probe must have a tolerance entry". Is there someother way to run this experiment or should I give tolerance myself? if so, how?


Extension does not appear in the UI

Extension version: v0.0.9
Playwright version: 1.18.0
VS Code: 1.63.2
One package.json in the root. Tests are in root/tests folder named with pattern of *.ts
The extension does not appear in the UI. Is there any way to solve this?

Hey! We are currently in the process of rewriting the extension and it should get released in a few weeks. In the meantime you can test the development builds here which should have a lot of bugfixes including this one: https://github.com/microsoft/playwright-vscode/wiki/Installation


Tock Hello World demo

Demonstration of building tock kernel and apps in the OpenTitan repo
This demonstration builds the Rust-based tock kernel, userspace library (libtock-rs) and applications (hello world) via bazel from within the OpenTitan repository.  The tock resources (kernel, library, tooling) are all instantiated as external resources known to bazel.
TL;DR
bazel build -c opt //sw/device/silicon_owner/tock:image //sw/host/opentitantool
opentitantool --interface=cw310 bootstrap bazel-out/k8-opt-ST-2cc462681f62/bin/sw/device/silicon_owner/tock/image.bin

Note: the opt profile is required because the un-optimized rust code won't fit within the bound defined by the linker script.  A fastbuild binary will work, but the linker script needs adjustment.
Current Dependencies Structure
A separate index of tock dependencies is in //third_party/tock.

elf2tab is referenced from my personal github repo.  This is done because currently, elf2tab miscomputes the application entry point, and I've hacked my fork to fix that.
libtock is referenced from its upstream github url.  No changes were necessary.
The tock kernel is referenced from my personal github repo.  Upstream currently has a number of problems that make it unable to boot on the CW310 board.

The ePMP configuration has no idea how the Test or Mask ROM set the initial configuration, and thus clobbers the ePMP.
There's a whole laundry list of modules included at the original developer's whim.
The earlgrey-cw310 crate is a binary crate; we need a library crate so we can instantiate the kernel on our own terrms.

OpenTitan Repo Structure

Tock applications are located in //sw/device/silicon_owner/tock/apps.  Currently, only a hello app is present.
The tock kernel is built by the targets in //sw/device/silicon_owner/tock/kernel.  Currently, it builds the earlgrey-cw310 board from the upstream tock repo.  This needs to change such that we're defining our boards (e.g. earlgrey-{verilator,cw310,es_silicon}) in our repo with the appropriate configuration.
The final image is integrated together by //sw/device/silicon_owner/tock:image.  This probably needs to be a bit more flexible (e.g. .../tock/transport:image, .../tock/security_key_demo:image, etc).

Superseded by https://github.com/lowRISC/opentitan/pull/19439, https://github.com/lowRISC/opentitan/pull/19442, https://github.com/lowRISC/opentitan/pull/19477, https://github.com/lowRISC/opentitan/pull/19478, https://github.com/lowRISC/opentitan/pull/19495.


AppMgr addon service account name change

Signed-off-by: Roke Jung<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/19762

/lgtm


[bug]

Link to minimal reproducible example
web3modal  example is not working
Summary
First i can use it ,when i close this project and then start the npm run laborary   can not work ,many bug ,i can not   use the command npm install,and npm install turbo,npm run watch use it  can not work again
List of related npm package versions
i useweb3modal  4.0

Hi the instructions to run the project is in the README.md file


elasticsearch plugin for dokku-alt?

Is anyone using elasticsearch with dokku-alt? I tried using jedez/dokku-elasticsearch-plugin, but when I restarted my machine I'm getting the following error. Trying to figure out if it's an issue with the plugin or not..
2014/09/27 22:07:27 json: cannot unmarshal array into Go value of type map[string]interface {}

@npow have you managed to sort it out in the end?


Blurry words in ODK-X survey

In the example data loaded into the ODK-X survey app that contains tables data and form data, When the 'Select Examples' table is clicked the new window where the surveys are recorded has a very sharp white background which is not friendly to the eye and makes viewing the words difficult. Attached is a preview. I installed the ODK-X survey app on my phone which runs on android 9.

@kenejane this appears to be a valid issue. If you would like to fix it let us know.

It should be noted that the change should not make any other form look incorrect as it should be a change local to the css styles of this form.

@wbrunette  would love to work on it

@kenejane I have assigned the issue to you

ok @wbrunette . I am on it


Add RTCPFeedback support to PopulateFromSDP

Handles the newly added RTCPFeedback information from pion/sdp

Codecov Report

Merging #1000 into master will increase coverage by 3.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1000      +/-   ##
==========================================
+ Coverage   74.39%   77.45%   +3.06%
==========================================
  Files          66       59       -7
  Lines        5003     4405     -598
==========================================
- Hits         3722     3412     -310
+ Misses        959      714     -245
+ Partials      322      279      -43

Flag
Coverage Δ

#go
77.45% <100%> (+0.77%)
:arrow_up:

#wasm
?

Impacted Files
Coverage Δ

mediaengine.go
95.14% <100%> (+17.08%)
:arrow_up:

sctptransport.go
75.38% <0%> (-3.59%)
:arrow_down:

peerconnection_js.go

datachannel_js_detach.go

iceserver_js.go

js_utils.go

datachannel_js.go

settingengine_js.go

api_js.go

peerconnection.go
73.54% <0%> (+0.35%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Fix TabContainer not setting layout immediately

Fixes #23570
The code I removed is done in _repaint().

Thanks!

Any chance this bugfix will get cherrypicked for 3.4.3 as well?

Cherry-picked for 3.5.

Cherry-picked for 3.4.3.


ci: add Jenkinsfile and shell.nix for builds

This PR consists of two components:

ci/Jenkinsfile.build - CI build for both Linux, MacOS, and Windows
ci/Jenkinsfile.release - Meta-build that combines two above.

The purpose of the release job is to create a single GitHub releas that combines artifacts from all build jobs.
The GitHub release created is in Draft mode and needs to be edited to update description and published.
Here's the result:

Correct one:

https://github.com/status-im/keycard-certify/pull/2


Manifest file should include DPI Aware options

I've made this work using Resource Hacker so I can achieve clean DPI levels on Winfile

Default DPI:

What specifically do you think should be changed?

What specifically do you think should be changed?

I have a huge monitor so I'm using DPI Scaling. I don't like going to Compatibility and setting the DPI levels myself, I think the application should default by itself.
What needs to be changed you ask? Inside the manifest file we should replace application tag with this:
<application xmlns="urn:schemas-microsoft-com:asm.v3">
  <windowsSettings  xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings">
    <ws2:dpiAwareness>PerMonitorV2</ws2:dpiAwareness>
  </windowsSettings>
</application>

This will enable the best DPI scaling Windows 10 has to offer.

Closing this as a duplicate. We can continue the conversation about best next steps in #19 .


Support HTML data

supporting copy & paste html data would be nice. Especially for copying data from Web browsers.

https://support.microsoft.com/en-us/kb/274308
https://msdn.microsoft.com/en-us/library/aa767917(v=vs.85).aspx

For x window, just use a "text/html" intern when copy:
atom = Gdk.Atom.intern("text/html", False)
result = clippy.wait_for_contents(atom)

In the meantime, the jaraco.clipboard supports HTML on MacOS and Windows.

This would be a useful feature - having a way to copy/get an image in the clipboard with Python (or other formats like HTML), using this simple cross-platform clipboard module.
However, the jaraco.clipboard module described above appears to do the job but only supports MacOS and Windows, not other platforms like Linux.


Install to PREFIX/lib by default

As suggested by @rbange, installing into a flat directory hierarchy is not intuitive. This PR aims to fix that. We still need the possibility to install into a flat hierarchy to build the Python package.

Let's restart the build by closing/reopening the issue.


sap.m.IconTabSeparator visible property does not exist

OpenUI5 version: latest
Browser/version (+device/version): chrome 54
Any other tested browsers/devices(OK/FAIL): yes
URL (minimal example if possible): https://sapui5.hana.ondemand.com/explored.html#/sample/sap.m.sample.IconTabSeparator/preview
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
1.
2.
3.
What is the expected result?
It would be great if you have the visible property on IconTabSeparator. If you combine it with sap.m.IconTabFilter in a icontabbar you would like to bind the visible property to sap.m.IconTabFilter ( exist ) and also to IconTabSeparator ( doesn't have ).
What happens instead?
you can not hide IconTabSeparator
Any other information? (attach screenshot if possible)

Makes sense to me. As it is an Element it does not have the visible property by default.
Internal reference:<PHONE_NUMBER>

Hi,
We added IconTabSeparator visible property in the master branch. We'll add it to the SAPUI5 1.44 branch as well.
Best,
Teo


Reverse polygon expandable arrows

Reverse arrows

thanks for the fixes.  i copied and pasted what i needed. you should just go ahead and pull from my branch again and accept all of my changes.


Decrypt failing

I'm just in the process of testing encryption with our backups. I simply added the following to my model file:
  encrypt_with OpenSSL do |encryption|
    encryption.password = 'testing'
    encryption.base64   = true
    encryption.salt     = true
  end

This works perfectly, however when I try and decrypt it the result is:
# backup decrypt --encryptor openssl --base64 --salt --in testing.tar.enc-aa --out testing.tar.aa
Launching: openssl aes-256-cbc -d -base64  -salt -in 'testing.tar.enc-aa' -out 'pharmmd_testing.tar.aa'
enter aes-256-cbc decryption password:
bad decrypt
140192250541728:error:0606506D:digital envelope routines:EVP_DecryptFinal_ex:wrong final block length:evp_enc.c:532:
# backup version
Backup 3.8.0

Please note, I tried running openssl manually too and got the same:
# openssl aes-256-cbc -d -base64  -salt -in 'testing.tar.enc-aa' -out 'pharmmd_testing.tar.aa'
enter aes-256-cbc decryption password:
bad decrypt
139798984115872:error:0606506D:digital envelope routines:EVP_DecryptFinal_ex:wrong final block length:evp_enc.c:532:

What am I not understanding here?
[edit] I use a splitter as well, I am going to try concatenating them together first, maybe it splits after.

Yup, I got the order wrong. Sorry!


I'am not able to access a own private LESS

When I want to look at a own private LES at the<EMAIL_ADDRESS>account on PRO server I get an error message. Refreshing and recalculation is not working.
Showcase buurtbatterij - buurtbatterij en capping - aangepaste business case has number 522.

You have to be signed in as<EMAIL_ADDRESS>to view the LES for<EMAIL_ADDRESS>I could give the LES to your own personal account though. It looks as though you're singed in with that account (you can verify by clicking on "Your account", right next to the "Sign out" button).

It should be fixed now. This is still bug-worthy though. What I saw was the following:

The LES belonged to<EMAIL_ADDRESS>The Market model aswell
The Topology belonged to the orphan user (implying that somebody tried to delete that Topology while it was still used in a LES)

I'll create a follow up issue.

I'll create a follow up issue.

Can this one be closed than @grdw?


Include more info on AWS X-Ray

Description of changes:
Added some information on the limitations of configuring X-Ray in Lambda, which is a common source of questions to X-Ray.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Merging, sorry for the delay!


chore: cleanup empty default values

Use undefined instead of empty collections where applicable. This makes the manifest less verbose and easier on the eyes.

💔 All backports failed

Status
Branch
Result

❌
k8s-21/main
An unhandled error occurred. Please see the logs for details

❌
k8s-20/main
An unhandled error occurred. Please see the logs for details

Manual backport
To create the backport manually run:
backport --pr 694

Questions ?
Please refer to the Backport tool documentation

💚 All backports created successfully

Status
Branch
Result

✅
k8s-21/main

Questions ?
Please refer to the Backport tool documentation

💚 All backports created successfully

Status
Branch
Result

✅
k8s-20/main

Questions ?
Please refer to the Backport tool documentation


Please change whitelist to allow list

Hi - please align whitelist to allow list as part of race-insensitive language work.
Many thanks,

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

ID: a7673988-90bd-d4f7-6b34-12139d25f5e8
Version Independent ID: 93301ddf-7a0c-7286-8e2b-1f9eab9f3f0d
Content: ProcessLauncher.RunToCompletionAsync Method (Windows.System) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.System/ProcessLauncher.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @hickeys
Microsoft Alias: hickeys

Thanks for submitting your feedback and we apologize for the extremely delayed response. I see that updates have not been made since the creation of this Issue, so I went ahead and resolved this doc bug. The changes should be pushed live sometime today, so I will go ahead and close this issue.
Though the Issue will be marked as Closed, we will monitor any replies that come afterwards so treat this like an open Issue. Many thanks!


Declare required development packages

I have trouble linking on Debian 8 and OSX 10.11.
Could you guys write a quick list of dep+vsn in /README.md?
On debian I have this:
error: linking with `cc` failed: exit code: 1
note: "cc" "-Wl,--as-needed" "-m64" "-L" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib" "/home/pete/wefwefwef/chaptrs.git/target/debug/chaptrs.0.o" "-o" "/home/pete/wefwefwef/chaptrs.git/target/debug/chaptrs" "-Wl,--gc-sections" "-pie" "-nodefaultlibs" "-L" "/home/pete/wefwefwef/chaptrs.git/target/debug" "-L" "/home/pete/wefwefwef/chaptrs.git/target/debug/deps" "-L" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-L" "/home/pete/wefwefwef/chaptrs.git/.rust/lib/x86_64-unknown-linux-gnu" "-L" "/home/pete/wefwefwef/chaptrs.git/lib/x86_64-unknown-linux-gnu" "-Wl,-Bstatic" "-Wl,-Bdynamic" "/home/pete/wefwefwef/chaptrs.git/target/debug/deps/libffmpeg-805255d617bd8363.rlib" "/home/pete/wefwefwef/chaptrs.git/target/debug/deps/libffmpeg_sys-fadf153a42f32bb4.rlib" "/home/pete/wefwefwef/chaptrs.git/target/debug/deps/liblibc-540159808ccfa9ab.rlib" "/home/pete/wefwefwef/chaptrs.git/target/debug/deps/libbitflags-eec34728826d9769.rlib" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd-8cf6ce90.rlib" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcollections-8cf6ce90.rlib" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_unicode-8cf6ce90.rlib" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/librand-8cf6ce90.rlib" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc-8cf6ce90.rlib" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc_jemalloc-8cf6ce90.rlib" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/liblibc-8cf6ce90.rlib" "/home/pete/.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-8cf6ce90.rlib" "-l" "avutil" "-l" "avcodec" "-l" "avdevice" "-l" "avformat" "-l" "avfilter" "-l" "avresample" "-l" "swresample" "-l" "swscale" "-l" "dl" "-l" "pthread" "-l" "gcc_s" "-l" "rt" "-l" "pthread" "-l" "c" "-l" "m" "-Wl,-rpath,$ORIGIN/../../../../.multirust/toolchains/nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-Wl,-rpath,/usr/local/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-l" "compiler-rt"
note: /usr/bin/ld: cannot find -lswresample
collect2: error: ld returned 1 exit status

Mainly: does it depend on ffmpeg (from the Ffmpeg project), avconv (because both my platforms ask for libavutil)?
Or: do you know an easy way to install libavutil on debian or osx?
I think I'll test my code using only Travis CI for now :D

We're trying to figure that out, see ongoing discussion here.

sudo apt-get install libavutil-dev
sudo apt-get install libavformat-dev
sudo apt-get install libavfilter-dev
sudo apt-get install libavdevice-dev
sudo apt-get install libclang-dev


Pubsub: Add the option to decouple the DLT from the subscribed pubsub

In what area(s)?

/area runtime
Describe the feature

When subscribing a Dapr app to a Pubsub component, configuring a DLT requires it to be in the same Pubsub "context" as the originally subscribed topic. Usually, this isn't an issue since it covers most of the use cases,
Let's assume the following subscription:
apiVersion: dapr.io/v2alpha1
kind: Subscription
metadata:
  name: example-subscription
spec:
  topic: example-topic
  routes:
    default: /checkout
  pubsubName: example-pubsub
  deadLetterTopic: poison-topic

In this case, the deadLetterTopic - "poison-topic" needs to reside in the "example-pubsub" Pubsub component.
However, in certain cases, it's not possible to create more topics beyond the subscribed topic in the subscribed Pubsub, hence creating the DLT for the Dapr application would not be possible in that case.
Decoupling the DLT from the subscribed Pubsub component enables these use cases, and it also allows more complex use cases where you would want the DLT to be in a different Pubsub cluster/platform.
For example, it would be possible for the subscribed topic to use a Kafka pubsub, while the DLT uses the RabbitMQ pubsub.
In terms of the API for the user, the user should configure the deadLetterPubsub (declaratively or programmatically), which references a Dapr Pubsub component with that name.
If not configured, then the current behavior is preserved.
An example of using this feature when using the external component file (declarative subscription):
apiVersion: dapr.io/v2alpha1
kind: Subscription
metadata:
  name: example-subscription
spec:
  topic: kafka-topic
  routes:
    default: /checkout
  pubsubName: kafka-pubsub
  deadLetterTopic: rabbit-topic
  deadLetterPubsub: rabbit-pubsub

or when programmatically subscribing to a topic (used Python for this example):
@app.route('/dapr/subscribe', methods=['GET'])
def subscribe():
    subscriptions = [
      {
        'pubsubname': 'kafka-pubsub',
        'topic': 'kafka-topic',
        'routes': {
          'default': '/checkout',
        },
        'deadLetterTopic': 'rabbit-topic',
        'deadLetterPubsub': 'rabbit-pubsub',
      }]
    return jsonify(subscriptions)

Release Note

RELEASE NOTE: ADD Decoupling of the DLT from the subscribed pubsub

However, in certain cases, it's not possible to create more topics beyond the subscribed topic in the subscribed Pubsub

Are you able to elaborate on this - why is it not possible to create more topics beyond the subscribed topic?

However, in certain cases, it's not possible to create more topics beyond the subscribed topic in the subscribed Pubsub

Are you able to elaborate on this - why is it not possible to create more topics beyond the subscribed topic?

A possible case is when your application is consuming from another team's (could be a different department, organization, etc...) topic, and the Kafka cluster is not shared between the teams - it's not possible to expect from the other team to create another topic just so that the application would be able to utilize DLT.
In that case, to be able to utilize DLT would require to setup another microservice, which would consume from the aforementioned topic, and produce into a different Kafka cluster's topic (where in that Kafka cluster, it would be easy to also have a DLT setup), and only then, the "application" is able utilize DLT.
Therefore, instead of implementing the solution above, it would be more "correct" for Dapr to be able to use a separate pubsub for the DLT from the subscribed topic's one.


Allow exporting transparency from Standard shader

The HdrpShaderExporter already supports transparency, seems it's an oversight that the StandardExporter doesn't. This PR adds the ability to have transparent surfaces for the Standard shader as well. Additionally, the 4 modes of Standard shader (Opaque, Cutout, Fade, Transparent) are respected on exporting.

Done!

Hi @soraryu, could you please provide me the steps to test this change? That would be awesome, thanks!

create a new project on Standard pipeline
create a material that is transparent (Standard shader with transparency)
create a material that has cutout (Standard shader with cutout)
export without this PR: broken; export with this PR: works


Pull Request for CATiledLayer based zoom

I've been working in a pdf reader based on your amazing work, however it needed a high quality zoom feature, after a little struggling, I found a good way to implement it. So I'm back here to return something back to the community. This is my first time sharing on github so please be kind! :)

Hello Rodrigo.
I've been having a look at your leaves implementation, but whenever i try to scroll the pages in two pages mode. The page flip animation seems to be really slow and jerky on the iOS simulator. Have you or anyone else seen or had this problem?
If i can work out a method to get it to work i'll post it, but im still struggling so any help would be appreciated.
Thanks
Alex

Alex:
Thanks you for the feedback. This is the first time I hear about this problem, it works fine on my simulator and it has not been mentioned by others so far, I have a couple of questions for you so I can have a better idea about it:

Does the animation problem shows up in one and two pages mode or just two pages mode?
Have you tried the original brows leaves version and it works ok in your simulator?
Can you tell me which iOS version are you running?
How are you triggering the turning page animation? By tapping the left and right side, or dragging the page?

I look forward for your feedback!
Rodrigo

Hi.
Thanks for the reply. The animation problem only shows up in two pages mode while dragging the page, its fine if i tap it in two pages mode. I dont get the problem at all in single page mode.
I am currently using iOS 5, however i have tried 4.2 as well and got the same problem.
The original version of leaves works ok in my simulator when it comes to the dragging and animation effect in both one and two page views.
I'll keep working on it, sounds like it might be a problem with my simulator / xcode. I look forward to any feedback from you.
Thanks
Alex

Hi again Rodrigo.
I have since tried this on my iphone and still have the same dragging across problem. I still am not sure on what the problem could be, I have also since tried it using iOS SDK 3.2 and it didnt work on that either.
Regards
Alex

Alex:
Sorry for the delay in the response, I've been away from computers this weekend. I think that the problem could be related to animation, I will try a couple of fixes today and I'll let you know.
Rodrigo

Hi again.
Yeah ok, that would be interesting to see. Also, Ive tried this on device running iOS 3.1 but on this the page turner doesnt seem to work at all as well as the possible animation problem when dragging the page across on other iOS versions, whether it could be related to the animations i dont know.
Thanks a lot for the help.
Alex

Hi Alex,
I am not Rodrigo! Probably you have got the wrong email id.
BTW in IOS5 ibook like page flip has been introduced check it out :)
Thanks and Regards,
Anil
On Mon, Oct 17, 2011 at 4:31 PM, achetwood <
<EMAIL_ADDRESS>
Hi again Rodrigo.
I have since tried this on my iphone and still have the same dragging
across problem. I still am not sure on what the problem could be, I have
also since tried it using iOS SDK 3.2 and it didnt work on that either.
Regards
Alex
--
Reply to this email directly or view it on GitHub:
https://github.com/brow/leaves/pull/16#issuecomment-2427418

Hi.
Ive been working with Rodrigo's version of Leaves, I have managed to get the page turning to work on an iphone running iOS 3.1. However, I have for the moment got rid of the facing pages support because it is still slow and jumpy when dragging the page across. If anyones had any luck with this, any help would be great.
Thanks

Hi achetwood
Have you been able to solve slowness of page dragging? I have the same problem using it in iPad 5.0 simulator and a real iPad with also 5.0.
Thanks


Fix some incorrect links in docs

https://gitea.com/gitea/gitea-docusaurus/actions/runs/661/jobs/0#jobstep-9-39
I noticed that there are many warning logs in building docs.
It is causing 404 in docs.gitea.com now, so we need to fix it.
And there are also some other problems in v1.19 which can not be done in this PR.
ps: Are there any good methods to test this in local?

Some of them should be backported to v1.21. I guess it's no harm to add backport labels since the merge will conflict.


Raising Kernel Key Retention Service variables maxbytes and maxkeys seems to be needed for high load

We rolled out sysbox on 33 Gitlab Runners that all use docker-dind and every day 1-3 runners stopped working with this error:
starting permission container: Error response from daemon: OCI runtime create failed: container_linux.go:392: starting container process caused: process_linux.go:592: container init caused: join session keyring: create session key: disk quota exceeded: unknown (linux_set.go:105:0s)

After the runners reached this error everytime when the runner tried to start a new container resulting in this error a new sysboxfs mount was leaked. A restart of sysboxfs helped and removed all sysboxfs mounts and new containers could be started again.
We did't had this error before using sysbox but it seems that this can happen without sysbox as well and you can find several hints regarding the maxkeys and maxbytes variables.
First we tried raising maxkeys with "sysctl -w kernel/keys/maxkeys=1000000" which is the same value as root_maxkeys but it did not help.
After that we raised maxbytes with "sysctl -w kernel/keys/maxbytes=25000000" which is the same value as root_maxbytes as well and having both optons set helped. We havn't encountered a single error within the last 5 days.
As you can see we increased maxkeys and maxbytes to very high values. Could it be that keys are leaked by sysboxfs? At least sysboxfs mounts are leaked when this error state is reached. Or could it be that the garbace collection (gc_delay) does not run often enough? https://www.kernel.org/doc/html/v5.10/security/keys/core.html

Hi @nudgegoonies, thanks for filing this issue.
For context, Sysbox allocates a session keyring each time a container is started or when the container is entered via exec (e.g., "docker exec ...") . The session keyring is destroyed when the container stops or when the "exec" exits the container. You can verify this by looking at the output of /proc/key-users as you create and destroy containers (i.e., you should see the key allocation count increase when the container starts, and decrease when the container stops). Note that if you are running Docker-in-Docker, inner Docker containers also add to the keyring consumption count.
Now, by default the kernel sets a low limit on the max number of keys that non-root users can have (i.e., 200). The Sysbox installer increases this limit to 20K because, on the assumption that a Sysbox-CE host machine will have ~100 containers, each using 200 keys on average (including keys used  by inner containers).
In your case you are raising the max-keys limit to 1M keys (i.e., 50 times larger than our assumption), which sounds really large.
I don't believe however that Sysbox is leaking the keys, though I can see our test-suite is not checking exhaustively for this (something I will improve).
A couple of questions for you:

How many sysbox containers plus inner containers do you think are running on the host at peak time?

After the sysbox containers are removed, does /proc/key-users report that the keyrings were deallocated?

Thanks!

Thank you very much for your explantation. I checked /proc/key-users and keys and bytes for the it is always increasing reproducible via:

start and exit a container
wait GC time
the value for keys is still increased by one and the value for bytes is increased as well

I will try a master build to see if it is still the case there.

Seems like this is already fixed in the current master!

Hi @nudgegoonies,

the value for keys is still increased by one and the value for bytes is increased as well
...
Seems like this is already fixed in the current master!

mmm ... that's strange, I was under the impression we had fix this over a year ago.
What version of Sysbox where you using when you hit the problem?

The 0.3.0 with the journald and DeadlineExceeded commits cherry picked.

The 0.3.0 with the journald and DeadlineExceeded commits cherry picked.

I see ... thanks.
In general, I would advice against cherry-picking specific changes, because even if the merge goes smoothly, it's possible to break functionality (e.g., the cherry-picked change may depend functionally on a prior change which was not cherry-picked).
Also, we can't support Sysbox versions that are created by cherry-picking specific commits, because the resulting binary is not something we produced or have tested.
Glad you confirmed that things work with top-of-tree though ... sounds like this resolves the issue then.
I am closing the PR, please re-open if you feel the issue is not resolved.
Thanks as always for giving Sysbox a shot in your company's infra!

I adjusted my builds to always use the master. A release always feels better - but we use it for ci - continuous :-)


Cannot query container info from metadata if network is set to "host"

The following command does not work if the container networking is set to "host"
wget http://rancher-metadata/2015-12-19/self/container/create_index

It seems like with "host" networking, only "http://rancher-metadata/2015-12-19/self/host" is available.
I don't know if this is intention or a bug?

Metadata is based on the source IP making the request. With host networking the source is the host itself, and which individual container is making the request is not distinguishable.

Is there any workaround way to get the container metadata from the container itself.


Archive in package code used to create dummy data

@bms63 - in admiral core we include the below in the data.R file, is it necessary to request the same for admiralvaccine?
#' @keywords datasets
#' @family datasets
#' @source
Originally posted by @yangc71 in https://github.com/pharmaverse/admiralvaccine/pull/33#discussion_r1103486396

@pharmaverse/admiralvaccines We should figure out a way to store all the code that was used to create the dummy data for admiralvaccines.  We can a folder called dummy_data to store it and use .Rbuildignore to prevent it from loading into the package

Probably should also create a readme with how to update/create dummy data


Confused by some Random Errors

Hi Mark..
Very Nice Library great work ... but i'm working on Wifi Direct for the first time so i'm not sure how to use your library... can you please create sample projects showing its basic usage and difference between Host and Client...
it is giving me error when i use startNetworkService function to create a host
Failed to create __signaldispalyservice : Error Code: 0
and when i create an instance it gives this error
06-29 17:47:29.377: E/Salut(21732): Failed to use standard port, another will be used instead.
06-29 17:47:29.377: E/Salut(21732): Failed to get a random port, Salut will not work correctly.
06-29 17:47:29.377: E/Salut(21732): Failed to use standard port, another will be used instead.
06-29 17:47:29.377: E/Salut(21732): Failed to get a random port, __childdisplayservice will not work correctly.

I'm looking into this. What device are you testing on?

this is my code for Host Activity I'm Using Samsung galaxy s4 and a asus tablet android version 4.2.2
public class MainActivity extends AppCompatActivity {
public static SalutDataReceiver dataReceiver;
public static SalutServiceData serviceData;
public static Salut network;
@Override
protected void onCreate(Bundle savedInstanceState) {
	super.onCreate(savedInstanceState);
	setContentView(R.layout.activity_main);

	FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
	MainFragment mainFragment = new MainFragment();
	ft.replace(R.id.fMainActivityFragmentPlaceHolder, mainFragment)
			.commit();

	dataReceiver = new SalutDataReceiver(this, new SalutDataCallback() {

		@Override
		public void onDataReceived(Object data) {
			// TODO Auto-generated method stub

		}
	});

	serviceData = new SalutServiceData("_signaldispalyservice", 5062,
			"parent");
	network = new Salut(dataReceiver, serviceData, new SalutCallback() {
		@Override
		public void call() {
			// wiFiFailureDiag.show();
			// OR
			Log.e("Main",
					"Sorry, but this device does not support WiFi Direct.");
		}
	});
	Log.e("Main",
			"Host: "+ network.isRunningAsHost);
}

@Override
protected void onDestroy() {
	super.onDestroy();
	network.unregisterClient(new SalutCallback() {

		@Override
		public void call() {

		}
	});
}

}

I've pushed a new build with some minor bug fixes, so you'll have to update your build.gradle file's compile dependencies to:
    compile 'com.github.markrjr:Salut:v0.4.3'

Also, try using a port greater than 10000.

I'm Using Eclipse ... I've to download it....
Thanks for the update i'll let you know...

Hi Mark Sorry for the inconvenience but this is not working for me..
here is my code and log.... may be i'm missing something..
import com.pantera.fragments.MainFragment;
import com.peak.salut.Salut;
import com.peak.salut.SalutDataReceiver;
import com.peak.salut.SalutServiceData;
import com.peak.salut.Callbacks.SalutCallback;
import com.peak.salut.Callbacks.SalutDataCallback;
import android.os.Bundle;
import android.support.v4.app.FragmentTransaction;
import android.support.v7.app.AppCompatActivity;
import android.util.Log;
public class MainActivity extends AppCompatActivity {
public static SalutDataReceiver dataReceiver;
public static SalutServiceData serviceData;
public static Salut network;
SalutDataCallback callback;
@Override
protected void onCreate(Bundle savedInstanceState) {
	super.onCreate(savedInstanceState);
	setContentView(R.layout.activity_main);

	FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
	MainFragment mainFragment = new MainFragment();
	ft.replace(R.id.fMainActivityFragmentPlaceHolder, mainFragment)
			.commit();
	SalutDataCallback callback = new SalutDataCallback() {

		@Override
		public void onDataReceived(Object data) {
			//Data Is Received

		}
	};
	dataReceiver = new SalutDataReceiver(this, callback);

	serviceData = new SalutServiceData("_signaldispalyservice", 60606,
			"parent");
	network = new Salut(dataReceiver, serviceData, new SalutCallback() {
		@Override
		public void call() {
			// wiFiFailureDiag.show();
			// OR
			Log.e("Main",
					"Sorry, but this device does not support WiFi Direct.");
		}
	});
	Log.e("Main", "Host: " + network.isRunningAsHost);
}

@Override
protected void onDestroy() {
	super.onDestroy();
	network.stopNetworkService(false);
	network.unregisterClient(new SalutCallback() {

		@Override
		public void call() {
			// success
		}
	}, new SalutCallback() {

		@Override
		public void call() {
			// failure

		}
	}, false);
}

}
Its log:
06-29 20:37:52.404: E/Salut(28268): Failed to use standard port, another will be used instead.
06-29 20:37:52.404: E/Salut(28268): Failed to get a random port, Salut will not work correctly.
06-29 20:37:52.404: E/Salut(28268): Failed to use standard port, another will be used instead.
06-29 20:37:52.404: E/Salut(28268): Failed to get a random port, __signaldispalyservice will not work correctly.
06-29 20:37:52.404: E/Main(28268): Host: false
the fragment where i try to start network service in Onclick
import com.pantera.signaldisplay.MainActivity;
import com.pantera.signaldisplay.R;
import com.peak.salut.SalutDevice;
import com.peak.salut.Callbacks.SalutCallback;
import com.peak.salut.Callbacks.SalutDeviceCallback;
import android.os.Bundle;
import android.support.annotation.Nullable;
import android.support.v4.app.Fragment;
import android.util.Log;
import android.view.LayoutInflater;
import android.view.View;
import android.view.View.OnClickListener;
import android.view.ViewGroup;
import android.widget.ImageView;
public class LinkFragment extends Fragment implements OnClickListener {
View view;
ImageView ivFindDevices;

@Override
@Nullable
public View onCreateView(LayoutInflater inflater,
		@Nullable ViewGroup container, @Nullable Bundle savedInstanceState) {
	view = inflater.inflate(R.layout.link_fragment, container, false);
	ivFindDevices = (ImageView) view
			.findViewById(R.id.ivLinkFragment_FindChildDevices);
	ivFindDevices.setOnClickListener(this);

	return view;
}

@Override
public void onClick(View v) {
	MainActivity.network.startNetworkService(new SalutDeviceCallback() {
		@Override
		public void call(SalutDevice device) {
			Log.d("HOST", device.readableName + " has connected!");
		}

	}, new SalutCallback() {

		@Override
		public void call() {
			Log.d("HOST", "Success");
		}
	}, new SalutCallback() {

		@Override
		public void call() {
			Log.d("HOST", "Failure");
		}
	});
	Log.e("Main", "Host: " + MainActivity.network.isRunningAsHost);
}

}
its log:
06-29 20:30:52.291: D/Salut(28268): Starting __signaldispalyservice Transport Protocol __signaldispalyservice._tcp
06-29 20:30:52.313: E/Main(28268): Host: false
06-29 20:30:52.313: V/Salut(28268): Not connected to another device.
06-29 20:30:52.316: D/WifiP2pManager(28268): Ignored { what=139313 when=-8ms target=Handler (android.net.wifi.p2p.WifiP2pManager$Channel$P2pHandler) {4196dd70} }
06-29 20:30:52.320: D/WifiP2pManager(28268): Ignored { what=139313 when=-10ms target=Handler (android.net.wifi.p2p.WifiP2pManager$Channel$P2pHandler) {417a9e08} }
06-29 20:30:52.321: E/Salut(28268): Failed to create __signaldispalyservice : Error Code: 0
06-29 20:30:52.322: D/HOST(28268): Failure
06-29 20:30:52.322: D/WifiP2pManager(28268): Ignored { what=139313 when=-11ms target=Handler (android.net.wifi.p2p.WifiP2pManager$Channel$P2pHandler) {4196dd70} }
06-29 20:30:52.326: D/WifiP2pManager(28268): Ignored { what=139313 when=-12ms target=Handler (android.net.wifi.p2p.WifiP2pManager$Channel$P2pHandler) {417a9e08} }
06-29 20:30:52.327: D/WifiP2pManager(28268): Ignored { what=139313 when=-17ms target=Handler (android.net.wifi.p2p.WifiP2pManager$Channel$P2pHandler) {4182aba0} }
06-29 20:30:52.328: V/Salut(28268): Service discovery request acknowledged.
06-29 20:30:52.332: D/Salut(28268): Service discovery initiated.
when MainActiviy is Destroyed...
06-29 20:29:21.345: D/Salut(28268): Network service is not running.
06-29 20:29:21.400: D/Salut(28268): Attempted to unregister, but not connected to group. The remote service may already have shutdown.
06-29 20:29:21.400: E/Salut(28268): Failed to close one or more sockets. Perhaps they were already closed or null.
06-29 20:29:21.400: E/Salut(28268): Failed to close one or more sockets. Perhaps they were already closed or null?

I've figured it out!
So before I get to the actual issue, a few things. In your code, you recreate the SalutDataCallback. You have one declared for your class and then you declare another in onCreate.
You can also remove the underscore from your service name, I forgot to update the readme, but the framework will put that there for you.
Now on to the issue, so it turns out that you actually need the following in your AndroidManifest.xml.
    <uses-permission android:name="android.permission.INTERNET" />

Turns out that you can't actually open ports on Android without the internet permission.
Thanks for opening that issue, lest we both would have never found out about this. I've updated the readme accordingly.

So For So Good... Thanks The Service is Running but i've another problem..
when i start a networkService like this after initiating the object
network.startNetworkService(new SalutDeviceCallback() {
@Override
public void call(SalutDevice device) {
Log.d("HOST", device.readableName + " has connected!");
}
}, new SalutCallback() {

    @Override
    public void call() {
        Log.d("HOST", "Success");
    }
}, new SalutCallback() {

    @Override
    public void call() {
        Log.d("HOST", "Failure");
    }
});

it says failed to create _signaldisplayservice
06-30 14:20:43.316: D/Salut(11983): Starting _signaldispalyservice Transport Protocol _signaldispalyservice._tcp
06-30 14:20:43.341: E/Main(11983): Host: false
06-30 14:20:43.341: D/WifiP2pManager(11983): Ignored { what=139313 when=-11ms target=Handler (android.net.wifi.p2p.WifiP2pManager$Channel$P2pHandler) {417a0e48} }
06-30 14:20:43.341: E/Salut(11983): Failed to create _signaldispalyservice : Error Code: 0
06-30 14:20:43.341: D/HOST(11983): Failure
06-30 14:20:43.342: D/WifiP2pManager(11983): Ignored { what=139313 when=-8ms target=Handler (android.net.wifi.p2p.WifiP2pManager$Channel$P2pHandler) {417a0e48} }
06-30 14:20:43.344: V/Salut(11983): Service discovery request acknowledged.
06-30 14:20:43.344: D/Salut(11983): Service discovery initiated.
and when i try to discover from another device it only shows the service running not the device
network.discoverNetworkServicesWithTimeout(new SalutCallback() {
@Override
public void call() {
textView.setText("Look at all these devices! "
+ network.foundDevices.toString());
Log.d("",
"Look at all these devices! "
+ network.foundDevices.toString());
}
}, new SalutCallback() {
@Override
public void call() {
textView.setText("Bummer, we didn't find anyone. ");
Log.d("", "Bummer, we didn't find anyone. ");
}
}, 25000);
06-30 14:11:46.493: V/Salut(13843): Not connected to another device.
06-30 14:11:46.498: V/Salut(13843): Service discovery request acknowledged.
06-30 14:11:46.643: D/OpenGLRenderer(13843): Enabling debug mode 0
06-30 14:11:46.648: D/Salut(13843): Service discovery initiated.
06-30 14:11:49.128: D/Salut(13843): Found myparentinstance-1391081894 _signaldispalyservice._tcp.local.
06-30 14:11:49.128: D/Salut(13843): Found parent-1391081894 __signaldispalyservice._tcp.local.
06-30 14:11:49.128: D/Salut(13843): Found whatever-1391081894 __superawesomeservice._tcp.local.
06-30 14:12:11.503: D/(13843): Bummer, we didn't find anyone.
06-30 14:12:11.593: V/Salut(13843): Successfully removed service discovery request.
and please clear one more thing, how to create a host and how to connect the devices to the host?

Can You please make a sample for your library?

Perhaps sometime in the future. For now, however, the readme should definitely suffice as material to answer most of your questions, particularly even the ones you've just asked, and when that fails there is looking at the actual code for the library itself.

I’v meet the similar problem as the following description
10-19 11:09:07.871 7997-7997/ D/WifiP2pManager: Ignored { when=0 what=139313 target=android.net.wifi.p2p.WifiP2pManager$Channel$P2pHandler }

I use the the service discovery via wifi direct to broadcast data to device nearby in circulation mode


Pickle issue due to lambda functions

Traceback (most recent call last):
  File "train.py", line 961, in <module>
    main(args)
  File "train.py", line 941, in main
    trainer.fit(forecaster, datamodule=data_module)
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 608, in fit
    call._call_and_handle_interrupt(
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/site-packages/pytorch_lightning/trainer/call.py", line 36, in _call_and_handle_interrupt
    return trainer.strategy.launcher.launch(trainer_fn, *args, trainer=trainer, **kwargs)
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/site-packages/pytorch_lightning/strategies/launchers/multiprocessing.py", line 113, in launch
    mp.start_processes(
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 189, in start_processes
    process.start()
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/multiprocessing/process.py", line 121, in start
    self._popen = self._Popen(self)
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/multiprocessing/context.py", line 283, in _Popen
    return Popen(process_obj)
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/multiprocessing/popen_fork.py", line 19, in __init__
    self._launch(process_obj)
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 47, in _launch
    reduction.dump(process_obj, fp)
  File "/home/jott2/miniconda3/envs/spacetimeformer/lib/python3.8/multiprocessing/reduction.py", line 60, in dump
    ForkingPickler(file, protocol).dump(obj)
AttributeError: Can't pickle local object 'Embedding.__init__.<locals>.<lambda>'

I'm not able to confirm this, but this is very likely to be a pytorch lightning version control issue. Try v1.6. I had upgrade several times over the course of the project. I thought this was in the requirements.txt but that's apparently missing from the public version. There is one more code update coming with the final version of this paper over the next few weeks, but I don't expect to future-proof this repo to pytorch lightning because there are just too many breaking changes. Probably applies to #64 as well.... these dependencies change fast and you need to use a late 2021 or early 2022 version of everything.

Yeah looks like it was a pytorch lightning version control issue. I was able to get it running with pytorch-lightning==1.9.4 with the following modifications here:
accelerator="gpu",
devices=4,
strategy="ddp",

Looking forward to the updated final version!


lib crash ClassNotFoundException for org.pytorch.PyTorchAndroid

Im having Crash on some pixel devices that prevent me to upload to playstore
Given the details you've provided, it appears that your Android app is encountering an ExceptionInInitializerError and a ClassNotFoundException for org.pytorch.PyTorchAndroid
have u seen this before? tks
at androidx.compose.ui.platform.AndroidComposeView.onAttachedToWindow(Unknown Source:139)

Exception java.lang.ExceptionInInitializerError:
at org.pytorch.LiteModuleLoader.load (LiteModuleLoader.java)
at com.kiltdesign.remove_background.MainActivity$RemoveBgViewModel. (MainActivity.kt)
at com.kiltdesign.remove_background.MainActivity$RemoveBgViewModelFactory.create (MainActivity.kt)
at androidx.lifecycle.ViewModelProvider$Factory.create (ViewModelProvider.kt)
at androidx.lifecycle.ViewModelProvider.get (ViewModelProvider.kt)
at androidx.lifecycle.ViewModelProvider.get (ViewModelProvider.java)
at com.kiltdesign.remove_background.MainActivity.ImageSelectorAndRemoveBg (MainActivity.kt)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt)
at androidx.compose.material3.SurfaceKt$Surface$1.invoke (Surface.kt)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt)
at androidx.compose.runtime.CompositionLocalKt.CompositionLocalProvider (CompositionLocal.kt)
at androidx.compose.material3.SurfaceKt.Surface-T9BRK9s (Surface.kt)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt)
at androidx.compose.runtime.CompositionLocalKt.CompositionLocalProvider (CompositionLocal.kt)
at androidx.compose.material3.TextKt.ProvideTextStyle (Text.kt)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt)
at androidx.compose.runtime.CompositionLocalKt.CompositionLocalProvider (CompositionLocal.kt)
at androidx.compose.material3.MaterialThemeKt.MaterialTheme (MaterialTheme.kt)
at com.kiltdesign.remove_background.ui.theme.ThemeKt.MyApplicationTheme (Theme.kt)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt)
at androidx.compose.ui.platform.ComposeView.Content (ComposeView.android.kt)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt)
at androidx.compose.runtime.CompositionLocalKt.CompositionLocalProvider (CompositionLocal.kt)
at androidx.compose.ui.platform.CompositionLocalsKt.ProvideCommonCompositionLocals (CompositionLocals.kt)
at androidx.compose.ui.platform.AndroidCompositionLocals_androidKt$ProvideAndroidCompositionLocals$3.invoke (AndroidCompositionLocals.android.kt)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt)
at androidx.compose.runtime.CompositionLocalKt.CompositionLocalProvider (CompositionLocal.kt)
at androidx.compose.ui.platform.AndroidCompositionLocals_androidKt.ProvideAndroidCompositionLocals (AndroidCompositionLocals.android.kt)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt)
at androidx.compose.runtime.CompositionLocalKt.CompositionLocalProvider (CompositionLocal.kt)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt)
at androidx.compose.runtime.ActualJvm_jvmKt.invokeComposable (ActualJvm_jvm.kt)
at androidx.compose.runtime.ComposerImpl.doCompose (Composer.kt)
at androidx.compose.runtime.ComposerImpl.composeContent$runtime_release (Composer.kt)
at androidx.compose.runtime.CompositionImpl.composeContent (Composition.kt)
at androidx.compose.runtime.Recomposer.composeInitial$runtime_release (Recomposer.kt)
at androidx.compose.runtime.CompositionImpl.composeInitial (Composition.kt)
at androidx.compose.runtime.CompositionImpl.setContent (Composition.kt)
at androidx.compose.ui.platform.AndroidComposeView.setOnViewTreeOwnersAvailable (AndroidComposeView.android.kt)
at androidx.compose.ui.platform.WrappedComposition.setContent (Wrapper.android.kt)
at androidx.compose.ui.platform.WrappedComposition.onStateChanged (Wrapper.android.kt)
at androidx.lifecycle.LifecycleRegistry$ObserverWithState.dispatchEvent (LifecycleRegistry.kt)
at androidx.lifecycle.LifecycleRegistry.addObserver (LifecycleRegistry.kt)
at androidx.compose.ui.platform.AndroidComposeView.onAttachedToWindow (AndroidComposeView.android.kt)
at android.view.View.dispatchAttachedToWindow (View.java:20753)
at android.view.ViewGroup.dispatchAttachedToWindow (ViewGroup.java:3490)
at android.view.ViewGroup.dispatchAttachedToWindow (ViewGroup.java:3497)
at android.view.ViewGroup.dispatchAttachedToWindow (ViewGroup.java:3497)
at android.view.ViewGroup.dispatchAttachedToWindow (ViewGroup.java:3497)
at android.view.ViewGroup.dispatchAttachedToWindow (ViewGroup.java:3497)
at android.view.ViewRootImpl.performTraversals (ViewRootImpl.java:2630)
at android.view.ViewRootImpl.doTraversal (ViewRootImpl.java:2143)
at android.view.ViewRootImpl$TraversalRunnable.run (ViewRootImpl.java:8665)
at android.view.Choreographer$CallbackRecord.run (Choreographer.java:1037)
at android.view.Choreographer.doCallbacks (Choreographer.java:845)
at android.view.Choreographer.doFrame (Choreographer.java:780)
at android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:1022)
at android.os.Handler.handleCallback (Handler.java:938)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loopOnce (Looper.java:201)
at android.os.Looper.loop (Looper.java:288)
at android.app.ActivityThread.main (ActivityThread.java:7839)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1003)
Caused by java.lang.ClassNotFoundException: org.pytorch.PyTorchAndroid
at java.lang.Runtime.nativeLoad
at java.lang.Runtime.nativeLoad (Runtime.java:1121)
at java.lang.Runtime.loadLibrary0 (Runtime.java:1075)
at java.lang.Runtime.loadLibrary0 (Runtime.java:998)
at java.lang.System.loadLibrary (System.java:1656)
at com.facebook.soloader.nativeloader.NativeLoader.loadLibrary (NativeLoader.java)
at org.pytorch.LiteNativePeer. (LiteNativePeer.java)

Hi bruno, Are you using obfuscation in your app this can related with the pro-guard rules i will investigate it.

I have the same problem. Any updates? @erenalpaslan

I have it when use release build with:
isMinifyEnabled = true
isShrinkResources = true

my full error:
java.lang.ExceptionInInitializerError
at org.pytorch.a.a(Unknown Source:2)
at o2.b.(Unknown Source:86)
at b2.k.d(Unknown Source:277)
at l2.a.k(Unknown Source:28)
at N.c.k(Unknown Source:53)
at A.H0.a(Unknown Source:204)
at A.H0.k(Unknown Source:15)
at N.c.k(Unknown Source:53)
at q2.v.c(Unknown Source:151)
at D.N.a(Unknown Source:98)
at b2.k.c(Unknown Source:216)
at k2.c.j(Unknown Source:36)
at N.c.a(Unknown Source:45)
at N.c.j(Unknown Source:8)
at D.A.a(Unknown Source:160)
at D.A.k(Unknown Source:27)
at N.c.k(Unknown Source:53)
at s.b.a(Unknown Source:182)
at s.b.k(Unknown Source:43)
at N.c.k(Unknown Source:53)
at q2.v.u1(Unknown Source:14)
at F.r.q(Unknown Source:117)
at F.r.k(Unknown Source:10)
at F.y.n(Unknown Source:33)
at F.G0.a(Unknown Source:48)
at F.o.a(Unknown Source:4)
at F.y.o(Unknown Source:8)
at i0.v.h(Unknown Source:29)
at i0.v.g(Unknown Source:119)
at i0.q.m(Unknown Source:180)
at D.D.a(Unknown Source:890)
at D.D.k(Unknown Source:11)
at i0.s.a(Unknown Source:73)
at k0.x.a(Unknown Source:41)
at r.d.a(Unknown Source:50)
at r.d.c(Unknown Source:1033)
at H1.b.w(Unknown Source:59)
at P.A.b(Unknown Source:47)
at k0.n0.a(Unknown Source:154)
at k0.M.h0(Unknown Source:108)
at k0.M.a(Unknown Source:95)
at u.q.a(Unknown Source:110)
at k0.x.a(Unknown Source:41)
at X.H.c(Unknown Source:0)
at k0.C.a(Unknown Source:10)
at X.H.c(Unknown Source:0)
at k0.C.a(Unknown Source:10)
at r.d.a(Unknown Source:50)
at r.d.c(Unknown Source:1033)
at H1.b.w(Unknown Source:59)
at P.A.b(Unknown Source:47)
at k0.n0.a(Unknown Source:154)
at k0.M.h0(Unknown Source:108)
at k0.M.a(Unknown Source:95)
at u.q.a(Unknown Source:110)
at k0.x.a(Unknown Source:41)
at X.H.c(Unknown Source:0)
at k0.C.a(Unknown Source:10)
at X.H.c(Unknown Source:0)
at k0.C.a(Unknown Source:10)
at u.A.c(Unknown Source:96)
at k0.C.a(Unknown Source:10)
at r.d.a(Unknown Source:50)
at r.d.c(Unknown Source:1033)
at H1.b.w(Unknown Source:59)
at P.A.b(Unknown Source:47)
at k0.n0.a(Unknown Source:154)
at k0.M.h0(Unknown Source:108)
at k0.M.a(Unknown Source:95)
at i0.I.a(Unknown Source:38)
at k0.x.a(Unknown Source:41)
at r.d.a(Unknown Source:50)
at r.d.c(Unknown Source:1033)
at H1.b.w(Unknown Source:59)
at P.A.b(Unknown Source:47)
at k0.n0.a(Unknown Source:154)
at k0.M.h0(Unknown Source:108)
at k0.V.c(Unknown Source:16)
at k0.V.l(Unknown Source:17)
at k0.V.i(Unknown Source:58)
at l0.v.onMeasure(Unknown Source:82)
at android.view.View.measure(View.java:26557)
at l0.a.onMeasure(Unknown Source:66)
at android.view.View.measure(View.java:26557)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7022)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
at android.view.View.measure(View.java:26557)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7022)
at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1552)
at android.widget.LinearLayout.measureVertical(LinearLayout.java:842)
at android.widget.LinearLayout.onMeasure(LinearLayout.java:721)
at android.view.View.measure(View.java:26557)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7022)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
at com.android.internal.policy.DecorView.onMeasure(DecorView.java:835)
at android.view.View.measure(View.java:26557)
at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:4142)
at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:2836)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:3113)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2543)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:9465)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1451)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1459)


build(deps): bump the opentelemetry-deps-python group  and up py env in tox.ini

…ories with 36 updates
Bumps the opentelemetry-deps-python group with 36 updates in the /python/src/otel directory:

Package
From
To

opentelemetry-instrumentation-aws-lambda
0.49b1
0.50b0

Bumps the opentelemetry-deps-python group with 35 updates in the /python/src/otel/otel_sdk directory:

Package
From
To

opentelemetry-instrumentation-aws-lambda
0.49b1
0.50b0

Bumps the opentelemetry-deps-python group with 4 updates in the /python/src/otel/tests directory: opentelemetry-instrumentation-aws-lambda, opentelemetry-test-utils, opentelemetry-instrumentation and opentelemetry-semantic-conventions.
Updates opentelemetry-instrumentation-aws-lambda from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-test-utils from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-semantic-conventions from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-botocore from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-sdk from 1.28.1 to 1.29.0

Release notes
Changelog
Commits

Updates opentelemetry-exporter-otlp-proto-http from 1.28.1 to 1.29.0

Release notes
Changelog
Commits

Updates opentelemetry-distro from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-aiohttp-client from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-util-http from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-asgi from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-asyncpg from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-boto from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-boto3sqs from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-celery from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-dbapi from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-django from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-elasticsearch from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-fastapi from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-falcon from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-flask from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-grpc from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-jinja2 from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-mysql from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-psycopg2 from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-pymemcache from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-pymongo from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-pymysql from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-pyramid from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-redis from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-requests from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-sqlalchemy from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-sqlite3 from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-starlette from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-tornado from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-wsgi from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-aws-lambda from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-semantic-conventions from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-botocore from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-sdk from 1.28.1 to 1.29.0

Release notes
Changelog
Commits

Updates opentelemetry-exporter-otlp-proto-http from 1.28.1 to 1.29.0

Release notes
Changelog
Commits

Updates opentelemetry-distro from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-aiohttp-client from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-util-http from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-asgi from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-asyncpg from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-boto from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-boto3sqs from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-celery from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-dbapi from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-django from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-elasticsearch from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-fastapi from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-falcon from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-flask from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-grpc from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-jinja2 from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-mysql from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-psycopg2 from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-pymemcache from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-pymongo from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-pymysql from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-pyramid from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-redis from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-requests from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-sqlalchemy from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-sqlite3 from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-starlette from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-tornado from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-wsgi from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation-aws-lambda from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-test-utils from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-instrumentation from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

Updates opentelemetry-semantic-conventions from 0.49b1 to 0.50b0

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: opentelemetry-instrumentation-aws-lambda dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-test-utils dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-semantic-conventions dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-botocore dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-sdk dependency-type: direct:production update-type: version-update:semver-minor dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-exporter-otlp-proto-http dependency-type: direct:production update-type: version-update:semver-minor dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-distro dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-aiohttp-client dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-util-http dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-asgi dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-asyncpg dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-boto dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-boto3sqs dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-celery dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-dbapi dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-django dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-elasticsearch dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-fastapi dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-falcon dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-flask dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-grpc dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-jinja2 dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-mysql dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-psycopg2 dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-pymemcache dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-pymongo dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-pymysql dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-pyramid dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-redis dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-requests dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-sqlalchemy dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-sqlite3 dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-starlette dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-tornado dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-wsgi dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-aws-lambda dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-semantic-conventions dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-botocore dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-sdk dependency-type: direct:production update-type: version-update:semver-minor dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-exporter-otlp-proto-http dependency-type: direct:production update-type: version-update:semver-minor dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-distro dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-aiohttp-client dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-util-http dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-asgi dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-asyncpg dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-boto dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-boto3sqs dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-celery dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-dbapi dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-django dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-elasticsearch dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-fastapi dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-falcon dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-flask dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-grpc dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-jinja2 dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-mysql dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-psycopg2 dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-pymemcache dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-pymongo dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-pymysql dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-pyramid dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-redis dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-requests dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-sqlalchemy dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-sqlite3 dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-starlette dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-tornado dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-wsgi dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation-aws-lambda dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-test-utils dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-instrumentation dependency-type: direct:production dependency-group: opentelemetry-deps-python
dependency-name: opentelemetry-semantic-conventions dependency-type: direct:production dependency-group: opentelemetry-deps-python ...

@open-telemetry/lambda-extension-maintainers for review/merge.


Django 1.11 is close, some docs cleanup

Coverage remained the same at 95.699% when pulling f03474c4cffab1ff7f3f62f9d257728ce1f6396b on sergei-maertens:develop into 53b2524ff5dc792098569da068ee42d4741f3e4d on bigjason:develop.


Customizable sections of Posts page are being regenerated every push

fixed as of https://github.com/madaley1/nova-blog/commit/d406c665cc782d01e8c555bc1923ce92a6f9e266


Accessing documentation Deploy -> Docker crashes

When accessing https://docs.firezone.dev/deploy/docker/ I get the following error message

Fixed in #1257, just deployed. Thanks for the report!

That was quick, thank you!


[firebase 3.2.x] Android "default FirebaseApp is not initialized"

CLI: 8.6.5
@nativescript/core: 8.6.2
@nativescript/firebase-analytics: 3.2.2
@nativescript/firebase-core: 3.2.2
@nativescript/firebase-crashlytics: 3.2.2
@nativescript/firebase-messaging: 3.2.2
Were there any breaking changes in the latest versions of firebase-core analytics, crashlytics or messaging? After updating from version 3.1.3 to version 3.2.2 or 3.2.0, I get this error on Android devices:
Error: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.myapp.myapp. Make sure to call FirebaseApp.initializeApp(Context) first.
My code, unchanged from the previous version. initializeApp() returns null and the next line throws the exception.
import { firebase } from "@nativescript/firebase-core";
import "@nativescript/firebase-analytics";
import "@nativescript/firebase-crashlytics";
import "@nativescript/firebase-messaging";

export async function initFirebase() {
    const app = await firebase().initializeApp();
    // app is null

    firebase().crashlytics().setCrashlyticsCollectionEnabled(true);
}

Downgrading to version 3.1.3 all works fine.

Hi,
Downgrade the google firebase lib from the firebase-core/platforms/android/build.grale to 3.8 I think.


plotCurve now handles NA in pseudotime column

Running slingshot on large datasets often results in multiple lineages.
Not all cells are part of all lineages, and consequently some cells have an 'NA' for a given lineage as their pseudotime. This would cause an error when plotting the curve.
A simple filtering step solves this problem.

Thanks for your modification!


Add Preliminary for compiling source code

I'm submitting a...
[ ] Bug Fix
[ ] Feature
[ x ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

[ ] Commit Messages follow the Conventional Commits pattern

A feature commit message is prefixed "feat:"
A bugfix commit message is prefixed "fix:"

[ ] Tests for the changes have been added

Description
please describe the changes that you are making
Just modify the readme.md for helping typescripe fresh users
By the way, this PR template is too complex for fresh guys...
for features, please describe how to use the new feature
please include a reference to an existing issue, if applicable
Does this PR introduce a breaking change?
[ ] Yes
[ x ] No

You can just use npm install to get everything ready.
the ts-node will be installed in the local directory at ./node_modules/.bin/ts-node
Related to #31

Oh I see.


docs: Change page header in database/utilities.rst

Description
Change page header to be consistent with the menu in database/utilities.rst
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[x] User guide updated
[ ] Conforms to style guide

Change page header to be consistent with the menu in database/utilities.rst

Why?


Add a stylized depth of field effect

Added a first version with 172a67a.

Tagged for milestone 1 along with #93 - fairly solid already. And soooo shiny!

I'm going to consider this item complete as per milestone 1 going official, tho there's lots more neato stuff coming!


strange mesh refining error

Hello, @tzanio
I'm using a simple mesh refining method in AMR: (mfem v4.6)
Mesh pmesh(mesh_file, 1, 1);

 fec = new H1_FECollection(order, dim);  // order = 1; dim = 3
FiniteElementSpace fespace(&pmesh, fec);
if(refine loop begins)
{
       int neles = pmesh.GetNE();
       Vector errors(neles);
        // some error calculation here .....

       // Refine the elements whose error is larger than a fraction of the
       // maximum element error.
       const double frac = 0.5;
      double max_err = errors.Max();    // max_err is 3.54e-4 for the test
       double threshold = frac * max_err;
       { cout << "Refining ..." << endl; }
       pmesh.RefineByError(errors, threshold);
}

but I keep getting the following strange run-time error:
Verification failed: (GetNE() == 0 || ((Tetrahedron*)elements[0])->GetRefinementFlag() != 0) is false:
--> tetrahedral mesh is not marked for refinement: call Finalize(true)
... in function: virtual void mfem::Mesh::LocalRefinement(const mfem::Array&, int)
... in file: /Users/.../myworks/MFEM/mfem-master/mesh/mesh.cpp:9167
This error literally says that GetRefinementFlag() == 0 ( since pmesh.GetNE() /= 0 can be easily verified), but I can't figure out why this is happening.
Running examples such as ex6 has no issues.
Could anyone offer any help ?
Thanks !
mesh_file is (remove .txt to get .vtk file)
New_MT.vtk.txt

To perform refinement on a tet mesh (based on that error message I assume that), you need to Finalize the mesh first. This will reorder the vertices in each element so the longest is set 0-1, and then set the refinement flag appropriately. If you call mesh.FinalizeTopology() then mesh.Finalize(true) before building the fespace, I think that should resolve your issue.


Onboarding 2fa broken

After creating a New collective and a new organization 2fa is broken "atleast for me it is"  and in order to complete on boarding 2fa code must be verified. I attempted 2fa using Google Authenticator  on android, Authy on android, Authy on Windows 10 X64, Microsoft Authenticator on Android and tried sever different user agents, Firefox, Edge, Google Chrome for some reason none of the User agents will accept any codes from from any of the authenticator apps, not Windows or android versions.
To Reproduce
Steps to reproduce the behavior:

Go to 'settings'
Click on 'security'
Scroll down to '2FA'
clicking on the empty circle does not select authenticator add bubble it simple stays white/transparent
click on Authenticator+ button a pop up appears with a QR code and Manual text code.
enter the manual code into your authenticator app or scan code via auth app and several attems both qr and manual entry Fails with message invalid code.
Expected behavior
after step 5 and 6 above are performed and i have entered the timed 6 digit code from the authenticator app.... my account should sync with code and 2fa should be toggled to active.

Screenshots

Desktop (please complete the following information):

OS:  Windows 10 Home 22H2 OS Build:19045.3448- Windows Feature Experience Pack 1000.19044.1000.0

Browser: firefox Version 117.0.1 (64-bit) / Microsoft Edge Version 117.0.2045.43 (Official build) (64-bit)

Version: 22H2

Smartphone (please complete the following information):

Device: Motorola Edge Plus 5G UW (2022)
OS: Android
Browser: firefox / chrome
Version: 13

Additional context
I even attempted to use the 1password option but could not figure out how to use it in the current configuration

Triage Template (core team only)
This template is for members of the team to triage for prioritisation. For more guidance see https://www.loom.com/share/369ab467fbc64dec848085d38ff57ca0:
P1 high frequency, high impact
P2 low frequency, high impact
P3 high frequency, low impact
P4 low frequency, low impact
Examples of high impact - a problem affects users during an essential process (expenses and payments > onboarding and registration > contributing) with no workaround.
High frequency - >10% of users affected (measured as a proportion of total potential users for this case).

#6262

@Kiloabqq could it be that the date/time on your machine was not set correctly? If your machine's time is too far away from our server's time, 2FA will fail. Have you tried setting up 2FA on different websites (i.e. Google) to see if that works?

yes time is correct and yes on android and windows 2fa for other apps works
fine
On Thu, Sep 28, 2023 at 11:47 PM Benjamin Piouffle @.***>
wrote:

@Kiloabqq https://github.com/Kiloabqq could it be that the date/time on
your machine was not set correctly? If your machine's time is too far away
from our server's time, 2FA will fail. Have you tried setting up 2FA on
different websites (i.e. Google) to see if that works?
—
Reply to this email directly, view it on GitHub
https://github.com/opencollective/opencollective/issues/7017#issuecomment-1740388614,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWWJ6WGRYGBCHQ4QFVS6H2LX4ZVHTANCNFSM6AAAAAA5KWWCZY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Kiloabqq Which 2FA authenticator app are you using?


Spree 2.3

Maybe it would be good to support Spree 2.3?
You can find my try here: https://github.com/novotarq/spree_ajax_add_to_cart/tree/2-3-stable

nice to have it as a gem

Hey guys, this stuff is getting too old and I am no longer up-to-date. Anyone keen to take over?

@joneslee85 I think I could try :)

@novotarq I added you as collbarator


F10 and F11 grayed out in Run menu and these keys do not work

Issue Type: Bug
After installation a few days ago all worked as expected however on shutdown or hibernate the PC attempted a reboot. Visual Studio was running but not running a program. These reboots did not occur if I shutdown Visual studio before shutting down the PC. (This is just background info). The problem I have now is that the F10 and F11 keys don't work the code runs and stops at a breakpoint but I don't get the highlighted line in the code. F5 works and program continues (to next breakpoint). The terminal output does change to a > prompt on stopping at the breakpoints.
Presumably something has changed in config somewhere but I can't see anything obvious that I can change to 'fix' the issue. I guess I can uninstall and reinstall but that would be a rather long winded workaround.

Hi Andre,
Sorry for the slow response. I was debugging powershell code using the
VisualStudio IDE
Roger
On Tue, 8 Jun 2021 at 16:01, Andre Weinand @.***> wrote:

what debugger are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/125744#issuecomment-856845149,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUMZMCZJGQL6ACXHL6CZ4VTTRYWELANCNFSM46J5QUHQ
.

Just a bit more digging. If I start and set a breakpoint at pretty much the
first line of code and run the debugger it stops on the breakpoint. At this
point F10, etc are enabled and I can step through the code. If I press F5
to jump to a breakpoint further down the code then the Terminal window
shows a prompt (rather than my debug log  output) but the F10 key no longer
works (and is grayed out in the Run menu)
Hope this helps.
Roger
On Tue, 8 Jun 2021 at 16:32, Roger Young @.***> wrote:

Hi Andre,
Sorry for the slow response. I was debugging powershell code using the
VisualStudio IDE
Roger
On Tue, 8 Jun 2021 at 16:01, Andre Weinand @.***>
wrote:

what debugger are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/125744#issuecomment-856845149,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUMZMCZJGQL6ACXHL6CZ4VTTRYWELANCNFSM46J5QUHQ
.

I have updated to the most recent PowerShell extension and restarted VisualStudio. No better sadly.

Here is a very simple example of where it goes wrong (for me). The script does pretty much nothing but if I set a breakpoint on the line 14 ($contextFilmStripAlbumPictureBoxMenuStrip = New-Object System.Windows.Forms.ContextMenuStrip) or just step through the code using F10 on stepping onto (F10) to line 14 Visual Studio grays out F10, F11, F5 in the Run menu.
param(
[string]$testDir
)
if (!$testDir) {
"n No picture path was given in start parameter n"
"Usage:n$PSCommandPath [-testDir] full_path_to_image_filen"
break
}
Add-Type -AssemblyName 'System.Windows.Forms'
$debug = $true
$contextFilmStripAlbumPictureBoxMenuStrip = New-Object System.Windows.Forms.ContextMenuStrip
Write-Host 'Hello world'

/extPowershell


nodejs-rolling-router-wercker does not create hello-world repository

The hello-world project is not created to developer's git-hub for the Wercker deployment.

Fixing.

Tested and fixed.


Add tests for nested tuple access

There have been various reports of the same underlying parsing issue with nested tuple access over the last few weeks. https://github.com/rust-lang/rust/pull/77774 in rustc addressed the underlying issue which was then incorporated within rustfmt via #4469
However, would still be good to add some regression test cases for all the reports by adding corresponding files under the tests/target directory (no source files needed for this)
https://github.com/rust-lang/rustfmt/blob/master/Contributing.md#creating-test-cases
For anyone interested in working on this, please add tests for all the reported cases (including those added in issue comments)
#4355
#4410
#4363
https://github.com/rust-lang/rust/issues/76449

Hey @calebcartwright! Can I pick this issue up?

Absolutely @V1shvesh! Let us know if you have any questions

I've setup the project, going through the issues now 👍

@V1shvesh - apologies as there's some additional context here that'll impact the tests. Until recently nested tuple access that didn't have some kind of separator or token before latter items would result in a parser error as they would be parsed as a float.
As such rustfmt has historically put a space before the ident to prevent said parsing error. Since that's no longer the case, we no longer need to conditionally insert that space
https://github.com/rust-lang/rustfmt/blob/2d6a968d52b13b75fc3799f50020a34efd480a28/src/formatting/chains.rs#L203-L207
I think the rustc parser improvements will obviate the need for us to track whether a the tuple fields are nested now as well, if you are interested in working on that and doing a bit more work than the issue description originally covered (though simply removing the conditional space insertion above should suffice for tests)
https://github.com/rust-lang/rustfmt/blob/2d6a968d52b13b75fc3799f50020a34efd480a28/src/formatting/chains.rs#L122

@calebcartwright so far I just tried to read up and get more context on the test cases. Can you clarify if the test cases are still required?

@V1shvesh - Yes, the test cases are absolutely needed and they are the main point of this issue. All you really need to do for test cases is to create files with snippets of code (you can think of these as being like test fixtures), and the linked issues in the description contain the actual snippets you would stick in these files.
For example, one such snippet comes from #4355
fn main() {
    let _ = ((1,),).0.0;
}

As detailed in, https://github.com/rust-lang/rustfmt/blob/master/Contributing.md#creating-test-cases you can just create a file under tests/target/... with that content. That's really all there is to these tests, just a collection of snippets from a few different issues.
What I was referring to in my follow up is that rustfmt will currently add an extra space in there for historical reasons. So without making any changes to rustfmt, it would convert the above snippet this (notice the space before the trailing .0
fn main() {
    let _ = ((1,),).0 .0;
}

This used to be necessary for rustfmt to do so that the emitted formatting didn't cause any parser/compilation, however, it is no longer necessary to do so. As such, in addition to adding the test case files, you'll also want to update the formatting of the TupleField I linked to above to no longer insert that extra space

Hi, rustfmt panicked here.
On Windows it just panicked without providing much context, on my linux box it provided more details, but in the GitHub CI it panicked the same way Windows did.

Thank you for reaching out @jRimbault, but you're reporting a duplicate of several previous issues that have already been fixed (#4355)

Ah sorry, I didn't find this one (I guess because github default to searching only open issues).

I'll work on this!

This issue was fixed by #4570


Fixed the example code for sqlx::test

This pull request fixes the example code for sqlx::test.

Import Row required to use Row::get.
Declare foo to assign the query result.
Add the type parameter for the index.

@kenkoooo if you rebase on main it should fix those CI failures.

Thanks, @abonander! I fixed it.