Not working on OpenELEC 5.01

Pulsar doesn't work anymore after upgrading to OpenELEC 5.01. I'm running v0.4.5 and get script failed errors when trying to start streaming.

Same here. It keeps displaying "You must restat XBMC before using Pulsar".

Confirmed:
Pulsar 0.4.5
OpenELEC 5.01
Raspberry Pi B+
Loop restarting pulsar after first reboot...

Can you provide a debug log ? Can't do nothing without it...

Same problem here. Here is a debug log: http://xbmclogs.com/show.php?id=419172

I am using
Pulsar 0.4.5
OpenELEC 5.01
Without a problem. not running on raspberry pi though

Updated OpenELEC and Pulsar to a new version, still the same problem:
Pulsar 0.4.6
OpenELEC 5.03
Raspberry Pi B+
Kodi Log --> https://gist.github.com/epoxi/fd7ea2703dd1b5fc605c

I updated OpenELEC and Pulsar to a new version:

Pulsar 0.4.6
OpenELEC 5.03

Now Pulsar tells me that XBMC must be restarted, and it doesn't help to reboot the PI.
Brgds
Jonas

Guys, how are you downloading the addon? I hope not from the Github "Download ZIP" on the right.
Use the releases provided at: https://github.com/steeve/plugin.video.pulsar/releases/
That's what your logs tell me

@steeve I'm getting looping errors on the latest 0.4.7 version (openelec 5.0.1). Cannot start Pulsar at all
18:06:01 T:3043266560  NOTICE: Previous line repeats 1 times.
18:06:01 T:3043266560   ERROR: GetDirectory - Error getting plugin://plugin.video.pulsar/
18:06:01 T:3043266560   ERROR: CGUIMediaWindow::GetDirectory(plugin://plugin.video.pulsar/) failed
18:06:04 T:3043266560   ERROR: GetDirectory - Error getting addons://sources/video/
18:06:04 T:3043266560   ERROR: CGUIMediaWindow::GetDirectory(addons://sources/video/) failed
18:06:04 T:3043266560  NOTICE: SpawnThread - fatal error creating thread
18:06:32 T:3043266560  NOTICE: Previous line repeats 2 times.
18:06:32 T:3043266560   ERROR: GetDirectory - Error getting addons://sources/video/
18:06:32 T:3043266560   ERROR: CGUIMediaWindow::GetDirectory(addons://sources/video/) failed
18:06:32 T:3043266560  NOTICE: SpawnThread - fatal error creating thread
18:07:04 T:3043266560  NOTICE: Previous line repeats 1 times.
18:07:04 T:3043266560   ERROR: GetDirectory - Error getting addons://all/
18:07:04 T:3043266560   ERROR: CGUIMediaWindow::GetDirectory(addons://all/) failed
18:07:04 T:3043266560  NOTICE: SpawnThread - fatal error creating thread

Got the latest version v.0.47 automatically downloaded from the repo, and it still says "You must restart XBMC before using Pulsar." Rebooting doesn't help unfortunately.

@steeve, I've now downladed Pulsar from the link you provided (https://github.com/steeve/plugin.video.pulsar/releases/)
The outcome was almost the same. But now it keeps crashing and reloading :(
Upgraded OpenELEC to 5.04
Pulsar 0.4.7
OpenELEC 5.04
Raspberry Pi B+

Hi,
I have also upgraded to OpenELEC 5.04 and Pulsar 0.4.7, still the same message to restart XBMC.
Brgds
Jonas

I Have The Same Issue with Gotham OpenELEC In Mx2 Box..

@steeve - The logs above seem to indicate that the error tends to occur after the get_pulsar_checksum method; the exception might indicate wrong (out of bounds) fd position or argument value (taken from here).
I don't have the issue yet, per se, but I will be testing the addon on an OpenELEC later tonight (finally hooking up my RaspberryPi 2 up).

ok, apparently you guys have a corrupted install.
try this, in OpenELEC shell:
$ rm -rf .kodi/addons/plugin.video.pulsar .kodi/userdata/addon_data/plugin.video.pulsar

And then reinstall Pulsar from the zip at https://github.com/steeve/plugin.video.pulsar/releases/download/v0.4.7/plugin.video.pulsar-0.4.7.zip

Did what you mention, and reinstalled... Pulsar keeps restarting
17:49:46 T:1690297408  NOTICE: [plugin.video.pulsar] pulsard: starting
pulsard
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  main
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  main                          .__
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  main             ______  __ |  |   ___________ _______
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  main             __ |  |  \  |  /  /_  \  __
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  main             |  |> >  |  /  |_ \  / __ |  | /
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  main             |   /|/|/__  >(____  /|
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  main             ||                   /      /
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  main
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  main             Version: 0.4.7 Git: v0.4.7 Go: go1.4
17:49:47 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO  config           Reloading configuration...
17:49:48 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO  main             Addon: plugin.video.pulsar v0.4.7
17:49:48 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO  btservice        Setting Session settings...
17:49:48 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO  btservice        Setting Encryption settings...
17:49:48 T:1690297408  NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO  btservice        Consuming alerts...
17:49:48 T:1690297408  NOTICE: [plugin.video.pulsar] panic: dial tcp
<IP_ADDRESS>:9090: connection refused
17:49:48 T:1690297408  NOTICE: [plugin.video.pulsar]
17:49:48 T:1690297408  NOTICE: [plugin.video.pulsar] goroutine 1 [running]:
17:49:48 T:1690297408  NOTICE: [plugin.video.pulsar] pulsard: starting
pulsard
On Mon, Mar 2, 2015 at 5:36 PM, Steeve Morin<EMAIL_ADDRESS>wrote:

ok, apparently you guys have a corrupted install.
try this, in OpenELEC shell:
$ rm -rf .kodi/addons/plugin.video.pulsar .kodi/userdata/addon_data/plugin.video.pulsar
And then reinstall Pulsar from the zip at
https://github.com/steeve/plugin.video.pulsar/releases/download/v0.4.7/plugin.video.pulsar-0.4.7.zip
—
Reply to this email directly or view it on GitHub
https://github.com/steeve/plugin.video.pulsar/issues/102#issuecomment-76813392
.

--
Atte.-
LC

Yes because you didn't follow the install guide and didn't enable remote
control in Kodi
On Tuesday, March 3, 2015, Lucas Campa<EMAIL_ADDRESS>wrote:

Did what you mention, and reinstalled... Pulsar keeps restarting
17:49:46 T:1690297408 NOTICE: [plugin.video.pulsar] pulsard: starting
pulsard
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main .__
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main ______ __ | | ___________ _______
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main __ | | \ | / /_ \ __
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main | |> > | / |_ \ / __ | | /
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main | /|/|/__ >(____ /|
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main || / /
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main Version: 0.4.7 Git: v0.4.7 Go: go1.4
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO config Reloading configuration...
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO main Addon: plugin.video.pulsar v0.4.7
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO btservice Setting Session settings...
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO btservice Setting Encryption settings...
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO btservice Consuming alerts...
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] panic: dial tcp
<IP_ADDRESS>:9090: connection refused
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar]
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] goroutine 1 [running]:
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] pulsard: starting
pulsard
On Mon, Mar 2, 2015 at 5:36 PM, Steeve Morin<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
wrote:

ok, apparently you guys have a corrupted install.
try this, in OpenELEC shell:
$ rm -rf .kodi/addons/plugin.video.pulsar
.kodi/userdata/addon_data/plugin.video.pulsar
And then reinstall Pulsar from the zip at

https://github.com/steeve/plugin.video.pulsar/releases/download/v0.4.7/plugin.video.pulsar-0.4.7.zip

—
Reply to this email directly or view it on GitHub
<
https://github.com/steeve/plugin.video.pulsar/issues/102#issuecomment-76813392
.

--
Atte.-
LC
—
Reply to this email directly or view it on GitHub
https://github.com/steeve/plugin.video.pulsar/issues/102#issuecomment-77031899
.

--
Steeve Morin
twitter.com/steeve
github.com/steeve
linkd.in/smorin

Clean reinstall, erasing all ./kodi pulsar files.
OpenELEC:~ # rm -rf .kodi/addons/plugin.video.pulsar
.kodi/userdata/addon_data/plugin.video.pulsar
OpenELEC:~ # cd .kodi/addons/plugin.video.pulsar
-sh: cd: can't cd to .kodi/addons/plugin.video.pulsar
OpenELEC:~ # cd .kodi/userdata/addon_data/plugin.video.pulsar
-sh: cd: can't cd to .kodi/userdata/addon_data/plugin.video.pulsar
OpenELEC:~ #

Both remote control options are selected.

Re-Downloaded the pulsar plugin from the provided link. (
https://github.com/steeve/plugin.video.pulsar/releases/download/v0.4.7/plugin.video.pulsar-0.4.7.zip
)

Installed plugin from System --> Settings --> Add-ons --> Install from
zip file (popup indicates "addon enabled")

Reboot system/Kodi

ON REBOOT

Try to exec Pulsar for the first time. A pop-up says "you must reboot
kodi/xbmc"

Reboot system/Kodi

ON SECOND REBOOT

Try to exec Pulsar for the second time. A pop-up says "error: script
failed" then "pulsar daemon restarted"

BUT it worked on a second try :)

A lil' slow on a RBPi B+, but is really neat and functional :D
Thanks Steeve!
On Tue, Mar 3, 2015 at 7:07 PM, Steeve Morin<EMAIL_ADDRESS>wrote:

Yes because you didn't follow the install guide and didn't enable remote
control in Kodi
On Tuesday, March 3, 2015, Lucas Campa<EMAIL_ADDRESS>wrote:

Did what you mention, and reinstalled... Pulsar keeps restarting
17:49:46 T:1690297408 NOTICE: [plugin.video.pulsar] pulsard: starting
pulsard
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main .__
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main ______ __ | | ___________ _______
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main __ | | \ | / /_ \ __
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main | |> > | / |_ \ / __ | | /
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main | /|/|/__ >(____ /|
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main || / /
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO main Version: 0.4.7 Git: v0.4.7 Go: go1.4
17:49:47 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:47
INFO config Reloading configuration...
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO main Addon: plugin.video.pulsar v0.4.7
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO btservice Setting Session settings...
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO btservice Setting Encryption settings...
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] 2015-03-03 20:49:48
INFO btservice Consuming alerts...
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] panic: dial tcp
<IP_ADDRESS>:9090: connection refused
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar]
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] goroutine 1
[running]:
17:49:48 T:1690297408 NOTICE: [plugin.video.pulsar] pulsard: starting
pulsard
On Mon, Mar 2, 2015 at 5:36 PM, Steeve Morin<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
wrote:

ok, apparently you guys have a corrupted install.
try this, in OpenELEC shell:
$ rm -rf .kodi/addons/plugin.video.pulsar
.kodi/userdata/addon_data/plugin.video.pulsar
And then reinstall Pulsar from the zip at

https://github.com/steeve/plugin.video.pulsar/releases/download/v0.4.7/plugin.video.pulsar-0.4.7.zip

—
Reply to this email directly or view it on GitHub
<

https://github.com/steeve/plugin.video.pulsar/issues/102#issuecomment-76813392

.

--
Atte.-
LC
—
Reply to this email directly or view it on GitHub
<
https://github.com/steeve/plugin.video.pulsar/issues/102#issuecomment-77031899
.

--
Steeve Morin
twitter.com/steeve
github.com/steeve
linkd.in/smorin
—
Reply to this email directly or view it on GitHub
https://github.com/steeve/plugin.video.pulsar/issues/102#issuecomment-77046947
.

--
Atte.-
LC

Same here.

Raspberry Pi B
OpenElec 5.0.6
Pulsar plugin: https://github.com/steeve/plugin.video.pulsar/releases/download/v0.4.7/plugin.video.pulsar-0.4.7.zip

Please check out my comment in
https://github.com/steeve/plugin.video.pulsar/issues/118

Hi,
I had to reinstall my PI with a new OpenELEC 5.0.6 for other reasons (the Confluence interface was corrupt), and now Pulsar 0.4.7 works fine.
Brgds
Jonas

May I close this, then ?

Ok for me :-)

Hi, I use Openelec 5.0.3 on Rpi2, I download the repository 1.0.1, but when I want download Pulsar from the repository I always have a fail.

Hi,
What is the solution for the message "you must restart xbmc before using pulsar" in Kodi 15.1 insengrad even after restarting kodi?
I have already uninstall several times include the providers, delete all the related folders, and install again (by the way it works only with install from zip from here), and again and again the same problem.

I've had the same message on Raspberry Pi 2. I tried reinstalling Openelec with beta version, but the same message kept appearing ("you must restart....."). And then I noticed that I downloaded the whole pulsar repository (master), instead a particular version (https://github.com/steeve/plugin.video.pulsar/releases). I uninstalled Pulsar, installed from the new file, and it worked like a charm.

@zorglub76
Thanks man!
Now it's works.


Cleanup dead debug_value_addr in CopyForwarding

After hoisting the destroy of the copy src, debug_value_addr users of the
copy src become dead, this PR cleans them so that MemoryLifetimeVerifier does not
complain later.

@swift-ci test


replace python3-pep8 by python3-pycodestyle on Fedora 32

The package python3-pep8 doesnt exist on Fedora 32 and has been replaced by python3-pycodestyle
From the looks of it, most of the dependencies on this list could be installed by rosdep, I went with the simplest fix to get it working but the longer term solution would be to prune this list and rely on rosdep to install the dependencies.

I don't know why python3-pep8 was required, but the python3-pycodestyle is not an drop-in replacement, because it does not provide the pep8 command. So anything that depends on pep8 will fail.
As far as I can see there is no dependency on pep8 in the ROS2 installation, I would prefer to remove it to keep the list of dependencies as short as possible (as suggested in #847).

My understanding is that pep8 was needed by ament_pep8 that became ament_pycodestyle
https://github.com/ament/ament_lint/pull/217 (that now needs pycodestyle)
I agree with you than this list of dependency should be narrowed down to only the bits necessary to install by hand (and let rosdep handle the rest).
However (removal or replacement) the fix needs to be applied to ROS2 rolling instructions as well

@clalancette friendly ping, do you think we can merge this as is or would you rather remove the line completely and let rosdep handle its installation ?

@clalancette friendly ping, do you think we can merge this as is or would you rather remove the line completely and let rosdep handle its installation ?

I think we should let rosdep handle the installation of as much as possible, so let's just remove most of this and let rosdep do it.

so let's just remove most of this and let rosdep do it.

done in https://github.com/ros2/ros2_documentation/pull/848/commits/a4a022cd9119c8496e3f46a581bd41e3648d95ca


MINOR: Verify startup of zookeeper service in system tests

@ewencp @hachikuji @ijuma
This should make sure ZK service is up before Kafka service attempts to startup.

Tested normal path (ZK starting) and abnormal path (ZK being shut down before wait_until check runs).

Also, AK system tests have succeeded on top of this PR

LGTM


ip-tagging filter: add support for loading tags from file system

Commit Message:
Add support for loading IP tags from filesystem to IP tagging filter.
Any updates to the tags in the file will be watched for envoy via Inotify.
Usage:
   http_filters
     - name: ip.tagging
       typed_config:
         "@type": type.googleapis.com/envoy.extensions.filters.http.ip_tagging.v3.IPTagging
         request_type: BOTH
         path: /path/to/tags.yaml

Only one of ip_tags or path can be specified.
Implements https://github.com/envoyproxy/envoy/issues/2695.
Risk Level: Medium
Testing: Unit Tests
Docs Changes: Done
Release Notes: TODO
Co-authored-by: Ariane van der Steldt<EMAIL_ADDRESS>Signed-off-by: Radha Kumari<EMAIL_ADDRESS>

Like discussed above, we will explore ECDS with filesystem subscription and don't need this PR anymore so closing it. Thank you for all the help and review.


Incoming transaction in transaction history don't make much sense

The Problem

The data in the response doesn't make much sense for an incoming transaction into the OpenBazaar wallet
The response should include the OpenBazaar destination address; currently it has nothing (not sure if this is because the transaction is unconfirmed)
Related to 2, it says 1093136 confirmations, when clearly the transaction is unconfirmed.
Related to (2 & 3), it is an unconfirmed transaction but it says 'CONFIRMED'
The response doesn't say whether funds are incoming or outgoing from the wallet

Data
This is the response I got from the server from a transaction I made to top-up the OpenBazaar wallet:
[
  {
    "Address": "",
    "Confirmations": 1093136,
    "Memo": "",
    "OrderId": "",
    "Status": "CONFIRMED",
    "Thumbnail": "",
    "Timestamp": "2017-03-10T06:19:44Z",
    "Txid": "52b70ab04a5e23d621404ef8e256d4a646a6a9cc34a7aa28df880fa38f4233eb",
    "Value": 631385
  }
]

And at the time of posting, this is the testnet transaction according to Blocktrail:

After a few minutes the response changed:
[
  {
    "Address": "",
    "Confirmations": 1,
    "Memo": "",
    "OrderId": "",
    "Status": "PENDING",
    "Thumbnail": "",
    "Timestamp": "2017-03-10T06:19:44Z",
    "Txid": "52b70ab04a5e23d621404ef8e256d4a646a6a9cc34a7aa28df880fa38f4233eb",
    "Value": 631385
  }
]

Not sure what's going on.
Also not sure why it says PENDING' when it appears as 'confirmed' in the /wallet/balance`

The issue with the address is Mike wanted to show the address it was sent from, the information for which simply doesn't exist. I could maybe have it show the address it was received to, but then again, there can be more than one address (unlikely though). But it would also be hard to get that data.

The current wallet designs only show an address when it's an outgoing payment. This api conforms to that.

the value will be negative if it's outgoing.

All of this would be great in the API docs :)

No @hoffmabc, I prefer to let developers suffer.

@cpacia one of my outgoing transactions still shows a positive value:
[
  {
    "address": "",
    "confirmations": 109,
    "memo": "",
    "orderId": "",
    "status": "CONFIRMED",
    "thumbnail": "",
    "timestamp": "2017-03-10T06:19:44Z",
    "txid": "52b70ab04a5e23d621404ef8e256d4a646a6a9cc34a7aa28df880fa38f4233eb",
    "value": 631385
  },
  {
    "address": "",
    "confirmations": 101,
    "memo": "",
    "orderId": "",
    "status": "CONFIRMED",
    "thumbnail": "",
    "timestamp": "2017-03-10T07:43:31Z",
    "txid": "06f3fa084a1ab573bf9cae438943fd949796c75682fa8c1996d2e2ea3c02a77f",
    "value": 126820
  },
  {
    "address": "mvsbfdCLSpsgaWE61rvpt9i5zv38yu9wDY",
    "confirmations": 0,
    "memo": "",
    "orderId": "",
    "status": "UNCONFIRMED",
    "thumbnail": "",
    "timestamp": "2017-03-11T03:15:45Z",
    "txid": "58d079de37dff09e276c5139685787b4400d0e5cd4b9045183a622be51691405",
    "value": 476905
  }
]

https://www.blocktrail.com/tBTC/tx/58d079de37dff09e276c5139685787b4400d0e5cd4b9045183a622be51691405


ensure ECCVM polynomial commitments are never points at infinity

ECCVM prover/verifier uses a workaround for points at infinity that will not work in the recursive setting. Change composer to never produce points at infinity

This was handled by https://github.com/AztecProtocol/aztec-packages/pull/7709


Do not use fixed dir

issue: https://github.com/project-chip/certification-tool/issues/289
Not tested yet

Unable to get relative path because execution is in backend container. Path needs to be relative to host (rasp)


Automatically nest use statement paths

I read in the book that mod statements like
use a::b;
use a::c;
use a::d::e;
use a::d::f;

Can be reformatted with nested paths like
use a::{
    b, c,
    d::{e, f},
};

What's a consensus about the right way to go?
Is it in the scope of rustfmt to automatically handle this?
If yes, how to configure rustfmt so it does?

merge_imports (https://github.com/rust-lang/rustfmt/blob/master/Configurations.md).

@cynecx Thanks, so merge is the keyword I was missing instead of nest ;)
I read that the default value for this option is false, because the feature is not stabilized yet. See this #3362 for discussion about it.


Save button on aka.ms/trytypespec/azure does nothing in Edge Dev

Clicking the save button in https://aka.ms/trytypespec/azure in Edge Dev 116.0.1923.0 (and for many versions before) does nothing. The address doesn't change, and there's no visual cue of any kind. Seems on the old site it works, since @johanste sent me a URL to saved state and told me how he did it.

Dup of https://github.com/microsoft/typespec/issues/1265


website does not work offline

Hey @samccone—I'm not able to reproduce with the current deployment. We've been iterating quite a bit on the site, and it's possible that you hit us at a time when not everything was set up properly.
If you can reproduce now, can you re-open (and maybe grab one of us to let us debug the repro in person?)

will do

You got this because you were offline and our service worker was borked.
Should be fixed soon.

I believe @gauntface adjusted the build to make sure this doesn't crop up again.


Add Logo and Contract ShieldTokenCoin

Add Logo and Contract ShieldTokenCoin

On which chain it is deployed?

Hello smartchain BEP20
Obter o Outlook para iOShttps://aka.ms/o0ukef

De: MRabenda @.>
Enviado: Thursday, July 13, 2023 8:16:10 AM
Para: MetaMask/contract-metadata @.>
Cc: Roney Veloso Moreira @.>; Author @.>
Assunto: Re: [MetaMask/contract-metadata] Add Logo and Contract ShieldTokenCoin (PR #1206)
On which chain it is deployed?
—
Reply to this email directly, view it on GitHubhttps://github.com/MetaMask/contract-metadata/pull/1206#issuecomment-1634061160, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKMJQQFH2WWWO5DAGSYFHYLXP7KHVANCNFSM6AAAAAA2H3MS7U.
You are receiving this because you authored the thread.Message ID: @.***>

Unfortunately is not supported yet by this repo


Laravel integration failed

my env:
OSX / MAMP / Nginx / project: http://localhost:8888/blog/
I followed with precision  the instructions to integrate the package with Laravel:
(csrf token + service provider + route pointing the tusd server)
Service provider:
$this->app->singleton('tus-server', function ($app) {
    $server = new TusServer();
    $server
        ->setApiPath('/tus') // tus server endpoint.
        ->setUploadDir(storage_path('app/public/uploads')); // uploads dir.

    return $server;
});

Route:
Route::any('/tus/{any?}', function () {

    $response = app('tus-server')->serve();

    return $response->send();

})->where('any', '.*');

when i do a very simple test with axios :
axios.head('http://localhost:8888/blog/tus/').then(console.log).catch(console.log);

it responds with a 404 not found.
in chrome debug console here is the server response:
HTTP/1.1 404 Not Found
Server: nginx/1.13.2
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Powered-By: PHP/7.3.1
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
X-Content-Type-Options: nosniff
Tus-Resumable: 1.0.0
Access-Control-Allow-Origin:
Access-Control-Allow-Methods: GET,POST,PATCH,DELETE,HEAD,OPTIONS
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Content-Length, Upload-Key, Upload-Checksum, Upload-Length, Upload-Offset, Tus-Version, Tus-Resumable, Upload-Metadata
Access-Control-Expose-Headers: Upload-Key, Upload-Checksum, Upload-Length, Upload-Offset, Upload-Metadata, Tus-Version, Tus-Resumable, Tus-Extension, Location
Access-Control-Max-Age: 86400
Cache-Control: no-cache, private
Date: Sat, 20 Apr 2019 09:38:32 GMT
X-Content-Type-Options: nosniff
Tus-Resumable: 1.0.0
Access-Control-Allow-Origin:
Access-Control-Allow-Methods: GET,POST,PATCH,DELETE,HEAD,OPTIONS
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Content-Length, Upload-Key, Upload-Checksum, Upload-Length, Upload-Offset, Tus-Version, Tus-Resumable, Upload-Metadata
Access-Control-Expose-Headers: Upload-Key, Upload-Checksum, Upload-Length, Upload-Offset, Upload-Metadata, Tus-Version, Tus-Resumable, Tus-Extension, Location
Access-Control-Max-Age: 86400
Cache-Control: no-cache, private
Date: Sat, 20 Apr 2019 09:38:32 GMT
Set-Cookie: blog_session=ZZnNuohp7qWgChmhZtl7Rpgi1bxOHUjnP0PYxc6Q; expires=Sat, 20-Apr-2019 11:38:32 GMT; Max-Age=7200; path=/; httponly
Content-Encoding: gzip

... I can see the "Tus-Resumable: 1.0.0" mixed with Nginx server
Is there something i need to set up in Nginx ??
Very confused.
Thank you for your time and effort.
PS: I carefully read the issue #93 but with no help

Is your route supoosed to be http://localhost:8888/tus/ or http://localhost:8888/blog/tus/?

@francoisdop If the resource is not found, the server will respond with the 404 Not Found. Please check tus protocol. You should consider using tus js client instead of manually sending requests.

@alhaji-aki my route is http://localhost:8888/blog/tus/ because i have multiple project serve by MAMP. But I don't think that is an issue as the route works.
@ankitpokhrel I implemented your basic example (verify.php and upload.php)
after some debugging of the file Tus\Client.php, I noticed :

the method setApiPath('tus') doesn't work as in the method create(string $key) $this->apiPath always return the default value '\files'.

So I change this value (in AbstractTus.php) (hard coded) to 'blog\tus' to match my environment.
then in the method sendPatchRequest(int $bytes, int $offset), $this->getUrl() return http://localhost:8888/blog/blog/tus/ (instead of http://localhost:8888/blog/tus).
So I did a temporary str_replace('blog/blog','blog',$this->getUrl().
Every thing works fine until :
$response = $this->getClient()->patch($this->getUrl(), [                 'body' => $data,                 'headers' => $headers,  ]);
where $this->getClient() is a GuzzleClient instance (so I can't investigate further) but it throws the Error :
that the file (the actual image i am trying to upload) is not found in
\Applications\MAMP\_BLOG\storage\app\uploads (which normally  works for 'normal' uploads not using tusd server).
Thanks a lot for your attention

@francoisdop

the method setApiPath('tus') doesn't work as in the method create(string $key) $this->apiPath always return the default value '\files'.

Not sure what you did here, but it doesn't seem possible for create method to return default value for $this->apiPath if it is changed using setApiPath. We will need more info here to figure out what's going on.

Every thing works fine until:...

It can be this is because of the same url issue mentioned above. Will need more info to debug further.

closing due to inactivity, please feel free to comment or create a new issue if you need any further help.


Integrate camel-transform with Apache Camel

Create a branch off Apache Camel to integrate our camel-transform module and prepare a PR for Camel.  Update camel-transform component as necessary to fit Camel component guidelines.

Done:
https://issues.apache.org/jira/browse/CAMEL-8332


fix: add presto-trino demo to ci pipeline

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Enable the presto-trino demo and fix installation issues of prestodb.
https://buildkite.com/risingwavelabs/integration-tests/builds/565 passed
Checklist

[x] I have added necessary unit tests and integration tests

Maybe we can dump then result with --output-format option and validate the query result more detailedly.
https://teradata.github.io/presto/docs/current/installation/cli.html


Annoying flash

Hello,
in dark mode of the toolbar dial, if I press home button there is white flash and it's annoying. You can see it better if you set some backgorund picture... is this possible to fix?
Thanks!

Hi @trinajstica,
I don't think there is anything I can do to improve that, but I'm going to look into it to see what can be done to improve it.

@trinajstica This should be fixed in release 2.5. Please let me know if it looks better to you.

Thank you, it is working as expected. No white flickering! Great work. Thanks. :)

Fixed by e5a39151b15f970e1fb4b7cc863c4d8a3d4d66a7.


Adding a input otp component

Describe the feature
I saw that the react based shadcn/ui (https://ui.shadcn.com/docs/components/input-otp) created a new input otp component. So since I also need this component for my own project i thought I could help out by start creating this component for this library. The component is based on the bits-ui input otp(https://www.bits-ui.com/docs/components/pin-input) component but shares the visuals and functionality of the shadcn/ui input otp component. See photo for example running locally. The full functionality is not done yet and there are some discussions to be had on how to implement some things but a start is always nice
I have already made a basic version in a local environment so if someone can assign me to this feature i can commit the new input otp component for what i have so far so that you guys can correct some things or provide more feedback. This component is highly requested for this package and would be a great addition.
If you need more info please ask.

+1 🤗

Related:

https://github.com/huntabyte/shadcn-svelte/issues/881
https://github.com/huntabyte/shadcn-svelte/issues/995
https://github.com/huntabyte/shadcn-svelte/issues/1027

Ok so we are not basing it on the bits ui for this one? But we are waiting for the same person who created the input otp wrapper/api for the react version to make a svelte variant.

Tbh, I'm not sure.
But, Hunter made a remark that there might be the possibility of making the Bits-UI version as good as the input-otp one.

Pin Input (I think we can make this as good as the input-otp library)

https://github.com/huntabyte/bits-ui/pull/469#issue-2247113476
Guess time will tell the direction this goes in.

Ah ok. I looked at the input-opt multiple frameworks branch and it looked already pretty far along for svelte but who knows how much time it will actually be before it is production ready. I will keep an eye open for a any changes and for now I will be using my own created input-otp component based on the react one.

@VerburgtJimmy if you're ever up for it, please do share your component. 🙂

@huntabyte don't know how far you are with the svelte input-otp implementation but this is what I have and use so far. Still a work in progress but has the same features and foundation as the input-otp package for react.
https://github.com/VerburgtJimmy/svelte-input-otp/tree/main

Here is a small demo video
https://github.com/huntabyte/shadcn-svelte/assets/47350871/e64d7e50-7c66-4c08-835e-7abd70ceb61f

Hey @VerburgtJimmy! Thanks for that! I'll check it out once I get through some of these higher-priority components in the Bits UI rewrite for Svelte 5 first.

Sure take all the time you need! I am developing it further and publishing it on npm as a unstyled component. That component can than be used to create the shadcn variant. And thanks for all the hard work you provide for this community👍🏻

fyi: just deployed the package. For more info see: https://svelte-input-otp.jimmyverburgt.com/

@VerburgtJimmy Awesome job 🚀 ! I was checking the accesibility of your component and I saw some improvements that we can do. I open a PR https://github.com/VerburgtJimmy/svelte-input-otp/pull/2
With this change the copy and paste will work better in mobile, and we wil have a aria-label to set to the control.
Let me know, happy to contribute in any other things 😄

Not to rush anything here, but I'm just curious if the plan is still to add input otp to this awesome library

Hey @VerburgtJimmy! Thanks for that! I'll check it out once I get through some of these higher-priority components in the Bits UI rewrite for Svelte 5 first.

Like mentioned here. The priority for now is on rewriting bits-ui to svelte 5 and then convert this library to svelte 5 as well I guess but @huntabyte can correct me if I am wrong!
For now I guess the only option is to use a different input-otp package and then add shadcn/ui styles to it or if you are familiar with bits-ui you can check out the pin-input component over there: https://www.bits-ui.com/docs/components/pin-input

Added to @next


Try alternative memory layout

Currently it's 24 bytes with a capacity of 22, but a (pointer, len) with cap 14 might be better. Try that.

Not worth the trouble.

Find out if reordering the fields improve performance: https://stackoverflow.com/a/21710033

https://github.com/elliotgoodrich/SSO-23 uses that layout.

That gives 5% worst timings.


What to do when restart robot controller?

@jontje,
If robot controller is restarted ,then the current rws interface will lost its connection with the robot. But how to restore the connection automatically on restart of robot controller?
Thank you

Hi @ScottYang1982,
Can you provide more context about how you use abb_librws?
For example, if your application is polling for data, then it should automatically connect again after the robot controller has been restarted. Assuming the polling is continued during the restart.
However, if you have, for example, set up RWS subscriptions, then they won’t be resumed after the robot controller restart (at least as far as I know). In that case you need to reregister the subscriptions.

I'm going to assume this is no longer a problem for you @ScottYang1982 and close this.
If you still have questions, please post a comment and we can re-open.

I'm going to assume this is no longer a problem for you @ScottYang1982 and close this.
If you still have questions, please post a comment and we can re-open.


All emissive surfaces are rendered invisible if no lights are active

To reproduce:

Play 2 players and have one player extinguish their own candle and the other players candle at the same time.

fixed in #524


External select documentation problem

Description
We are trying to implement interactivity select with the external datasource as described here - https://api.slack.com/reference/block-kit/block-elements#external_select
Our select inside actions:
{
	"blocks": [{
		"type": "actions",
		"elements": [{
			"type": "external_select",
			"action_id": "subprocess",
			"placeholder": {
				"type": "plain_text",
				"text": "Subprocess"
			},
			"min_query_length": 4
		}]
	}]
}

Request for external options:
{
	"type": "block_suggestion",
	"action_id": "subprocess",
	"block_id": "+7x/Z",
	"value": "4367",
	"message": {
		"bot_id": "BNQSQ2ZDK",
		"type": "message",
		"text": "This content can't be displayed.",
		"user": "UNQCZ5C4U",
		"ts": "1570463370.018100",
		"team": "T2V37EATG",
		"blocks": [{
			"type": "actions",
			"block_id": "+7x/Z",
			"elements": [{
				"type": "external_select",
				"action_id": "subprocess",
				"placeholder": {
					"type": "plain_text",
					"text": "Subproess",
					"emoji": true
				},
				"min_query_length": 4
			}]
		}]
	}
}

Our response to POST with code 200 as application/json:
{
	"options": [{
		"text": {
			"type": "plain_text",
			"text": "Scoring"
		},
		"value": "Scoring"
	}, {
		"text": {
			"type": "plain_text",
			"text": "Delivery"
		},
		"value": "Delivery"
	}]
}

After this response we have the error: {ok: false, error: "invalid_response_json"} on Slack client.
What is the correct response format for this method?
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[ ] question
[x] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Unfortunately, we don't provide schemas or Open API specs for the variety of interactive response sequences in the API.. I know this inquiry is a bit dated, but if you're still running into trouble I recommend asking Slack support or the wider community for help with this particular issue: api.slack.com/support


Implement to_xarray method for earthkit.data.readers.csv.CSVReader

Is your feature request related to a problem? Please describe.
Would it be possible to implement the to_xarray method for the CSVReader class?
Describe the solution you'd like
As to_pandas is already implemented, I believe all is needed is this: to_pandas().to_xarray()
Describe alternatives you've considered
No response
Additional context
No response
Organisation
B-Open / CADS-EQC

This issue is fixed now. I added some documentation to: https://earthkit-data.readthedocs.io/en/develop/_api/data/readers/csv/index.html#data.readers.csv.CSVReader ("develop" version only).


Calendar inconsistent after reboot

For now, it might be good to note to archons to check the date before and adjust after a reboot. Command to do so is ticktock

Thanks, if you have time, could you add more detail. LIke what is going wrong, and what would expect instead.
Is this related to configuration settings with respect to time?
I also recall that there are settings governing whats happening when world state is saved before shutdown.

Its a known coffeemud bug. They must not prioritize it. Essentially, when you restart the mud, the date dials back several months or sometimes back to Jan 1 lol.
Its a minor issue the archon who restarts can adjust the date back with ticktock command. What should happen is it saves the date and resumes from the point it shutdown


FAQ update

Update FAQ for all items, including backup but keep in mind that the UX can change for backup. So just talk about fundamentals that may not change.

FAQ updated.


Make accommodations for component-local config

Explicitly declares access to current config as global where necessary, and makes it possible for us to introduce a component-local config that inherits from these global options in future.
Will be a breaking change if folks still use ViewComponent::Base.config to setup their config. Also unsure of how this interacts with gems with engines that depend on ViewComponent, but I'm hoping in the long run it's a step in the right direction for them that'll allow them to have their own ApplicationComponent equivalents that inherit their config from ViewComponent's own defaults.

Will be a breaking change if folks still use ViewComponent::Base.config to setup their config.

Unfortunately for us, it's the first line of the API docs 😬  so I think we'll need to make this change in 4.0 or implement it in a non-breaking fashion. How do you think we should proceed?

It might be possible to rename the ViewComponent::Base.config endpoint to ViewComponent::Base.default_global_config and preserve the existing interface. I suppose since the idea is that ViewComponent::Base's idea of config shouldn't change and should instead be extended internally by gems, that should be fine.
This PR needed a rebase anyway, so I'll try to address that in the process.

I've made it so that ViewComponent::Base.config, Rails.application.config.view_component, and ViewComponent::GlobalConfig are all equivalent. My thoughts are that from here, we should set the pattern for component-local config going forward – that's currently done by #1987, but if that gets held up by other factors it could be done in isolation.
Once we have the structure for component-local config in place, we can start looking at moving config options out of global and into local config one by one. There are a couple of ways we can go about this:

Have the default for an option be sourced from global config at the same endpoint it currently exists at. So for example, Rails.application.config.component.strict_helpers_enabled = true would mean that all descendants of ViewComponent::Base have strict helpers enabled unless they opt out. We would seek to deprecate this in the next major version.
Move options to component-local config in minor versions. This would be preferable in relation to the goal of making sure that engines that consume ViewComponent aren't subject to global config options in a way that would be detrimental for them, and would also mean that for particular minor versions we'd need to advise folks to set this config on, say, ApplicationComponent if they have it.

@boardfish sorry for the delay in reviewing your PR, I was on vacation last week and am just now getting to it!
Having seen this set of changes and #1987, I feel like I'm missing a clear sense of exactly the end state we're hoping to migrate for. What would be helpful for me is something like this:

Option
Old API
New API

test_controller
TBD
TBD

render_monkey_patch_enabled
TBD
TBD

For all of our configuration API. Do you think you could put together that list for us to discuss? I think we need to make sure we agree on the proposed API changes and that they are even feasible to make.

@boardfish I took a first crack at listing them all out. Here they are with my notes:

Setting name
Description
Proposed changes for v4

capture_compatibility_patch_enabled
Enables the experimental capture compatibility patch that makes ViewComponent compatible with forms, capture, and other built-ins. previews. Defaults to false.
None - This setting mokey-patches ActionView::Base, which we can only be done globally

component_parent_class
The parent class from which generated components will inherit. Defaults to nil. If this is falsy, generators will use "ApplicationComponent" if defined, "ViewComponent::Base" otherwise.
Move - This shoule be moved to be under `generate`

config
Returns the value of attribute config.
Move - Currently set on Base, I think this should be stored in the Rails application config, right?

current
Returns the current ViewComponent::Config. This is persisted against this class so that config options remain accessible before the rest of ViewComponent has loaded. Defaults to an instance of ViewComponent::Config with all other documented defaults set.
Move - Currently set on Base, I think this should be stored in the Rails application config, right?

default_preview_layout
A custom default layout used for the previews index page and individual previews. Defaults to nil. If this is falsy, "component_preview" is used.
Move - Currently set on Base, I think this should be stored in the Rails application config, right? I also think we could nest preview-related config under a `preview` key.

generate.*
The subset of configuration options relating to generators.All options under this namespace default to false unless otherwise stated.
Move - Currently set on Base, I think this should be stored in the Rails/Engine application config, right?

instrumentation_enabled
Whether ActiveSupport notifications are enabled. Defaults to false.
Move - Currently set on Base, I think this should be stored in the Rails/Engine application config, right?

preview_controller
The controller used for previewing components. Defaults to ViewComponentsController.
Move - Currently set on Base, I think this should be stored in the Rails application config, right? I also think we could nest preview-related config under a `preview` key.

preview_paths
The locations in which component previews will be looked up. Defaults to ['test/components/previews'] relative to your Rails root.
Move - Currently set on Base, I think this should be stored in the Rails application config, right? I also think we could nest preview-related config under a `preview` key.

preview_route
The entry route for component previews. Defaults to "/rails/view_components".
Move - Currently set on Base, I think this should be stored in the Rails application config, right? I also think we could nest preview-related config under a `preview` key.

render_monkey_patch_enabled
If this is disabled, use #render_component or #render_component_to_string instead. Defaults to true.
Remove (already done in v4 branch)

show_previews
Whether component previews are enabled. Defaults to true in development and test environments.
Move - Currently set on Base, I think this should be stored in the Rails application config, right? I also think we could nest preview-related config under a `preview` key.

show_previews_source
Whether to display source code previews in component previews. Defaults to false.
Move - Currently set on Base, I think this should be stored in the Rails application config, right? I also think we could nest preview-related config under a `preview` key.

test_controller
The controller used for testing components. Can also be configured on a per-test basis using #with_controller_class. Defaults to ApplicationController.
Move - Currently set on Base, I think this should be stored in the Rails application config, right? I also think we could nest preview-related config under a `preview` key.

use_deprecated_instrumentation_name
Whether ActiveSupport Notifications use the private name "!render.view_component" or are made more publicly available via "render.view_component". Will default to false in next major version. Defaults to true.
Remove - This should be done in v4 IMO

view_component_path
The path in which components, their templates, and their sidecars should be stored. Defaults to "app/components".
Modify - Wouldn't we want this to be view_component_paths?

If it's easier, I shared a Google Doc with you we can collaborate on 🤷🏻

@joelhawksley Thanks for putting that together! A cursory look through seems to suggest that's all right, but generate jumps out at me as something that's both global within an app and could be configurable within an engine. I figure we'd handle this in a similar way to component-local config using inheritance. I'll have a more thorough look soon.
On reflection, the implementation of GlobalConfig shouldn't change behaviour right this second, but I could do with understanding how that might need to change depending on whether we're in an engine or not. It might be possible for us to roll that out as opt-in before v4.


changing the PR flow

Hey there,
This is a test comment to be viewed in Slack

All check have passed. Merging with master.

[ ] I don't know what this is @aryansh04


[BUG] Wrong URL for S3 endpoint

Describe the bug
Hi, I am trying to create a profile for s3compliant using the endpoint s3.cern.ch. Instead of looking at the desired URL, it appends this URL to https://s3.cern.amazonaws.com. I run the following command and get the error as shown below.
Command
kanctl create profile s3compliant --access-key $ACCESS_KEY --secret-key $SECRET_KEY --endpoint https://s3.cern.ch/ --bucket mongodb-backup --region cern --namespace default --verbose

Output
secret 's3-secret-cy0fja' created
Failed the 'Validate bucket region specified in profile' check.. ❌
validation failed, deleting secret 's3-secret-cy0fja'
secret 's3-secret-cy0fja' deleted
Error: profile validation failed: failed to get bucket mongodb-backup: GetBucketLocation: RequestError: send request failed
caused by: Get "https://s3.cern.amazonaws.com/mongodb-backup?location=": dial tcp: lookup s3.cern.amazonaws.com on <IP_ADDRESS>:53: no such host
{"File":"pkg/kanctl/kanctl.go","Function":"github.com/kanisterio/kanister/pkg/kanctl.Execute","Line":48,"error":"profile validation failed: failed to get bucket mongodb-backup: GetBucketLocation: RequestError: send request failed\ncaused by: Get \"https://s3.cern.amazonaws.com/mongodb-backup?location=\": dial tcp: lookup s3.cern.amazonaws.com on <IP_ADDRESS>:53: no such host","hostname":"imran-cc.cern.ch","level":"info","msg":"Kanctl failed to execute","time":"2022-08-09T19:57:22.077775142+02:00"}

Could someone please help to fix this issue? Thanks
Best regards
M Imran

@muhammadimranfarooqi thanks for filing the bug. Looks like a bug in the profile validation code where the profile endpoint is not copied to the objectstore config. As a test, can you re-run your command with the --skip-validation flag to see if that works? Meanwhile, will you be interested in submitting a pull request fix? It should be a three-line change. If yes, I can show you where the code is.


Check if removed index items can be removed on write

When removed index items are cleaned, we need to make sure:

to update the index structures (index pages for Btree)
merge pages if possible
updating the index pages in case of BTree might lead to further merges (of index pages)


Why is this deprecated?

What is the reason? Can I maintain it?

when nodejs involes, the owner stops.


How to decrease batch size during testing?

Hello, I get memory error half-way through testing your code. Is there any way to reduce the batch size during testing? This is the error I get:
2020-07-30 05:35:53.904913: W tensorflow/core/common_runtime/bfc_allocator.cc:419] Allocator (GPU_0_bfc) ran out of memory trying to allocate 1.02GiB (rounded to<PHONE_NUMBER>).  Current allocation summary follows.
2020-07-30 05:35:53.905024: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (256):   Total Chunks: 93, Chunks in use: 93. 23.2KiB allocated for chunks. 23.2KiB in use in bin. 7.3KiB client-requested in use in bin.
2020-07-30 05:35:53.905071: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (512):   Total Chunks: 6, Chunks in use: 6. 3.8KiB allocated for chunks. 3.8KiB in use in bin. 3.8KiB client-requested in use in bin.
2020-07-30 05:35:53.905102: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (1024):  Total Chunks: 36, Chunks in use: 36. 46.8KiB allocated for chunks. 46.8KiB in use in bin. 44.2KiB client-requested in use in bin.
2020-07-30 05:35:53.905130: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (2048):  Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2020-07-30 05:35:53.905157: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (4096):  Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2020-07-30 05:35:53.905187: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (8192):  Total Chunks: 1, Chunks in use: 1. 8.0KiB allocated for chunks. 8.0KiB in use in bin. 8.0KiB client-requested in use in bin.
2020-07-30 05:35:53.905220: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (16384):         Total Chunks: 4, Chunks in use: 4. 64.0KiB allocated for chunks. 64.0KiB in use in bin. 64.0KiB client-requested in use in bin.
2020-07-30 05:35:53.905252: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (32768):         Total Chunks: 2, Chunks in use: 2. 92.5KiB allocated for chunks. 92.5KiB in use in bin. 92.5KiB client-requested in use in bin.
2020-07-30 05:35:53.905284: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (65536):         Total Chunks: 7, Chunks in use: 7. 525.0KiB allocated for chunks. 525.0KiB in use in bin. 525.0KiB client-requested in use in bin.
2020-07-30 05:35:53.905317: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (131072):        Total Chunks: 2, Chunks in use: 2. 299.0KiB allocated for chunks. 299.0KiB in use in bin. 225.0KiB client-requested in use in bin.
2020-07-30 05:35:53.905347: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (262144):        Total Chunks: 14, Chunks in use: 13. 4.81MiB allocated for chunks. 4.48MiB in use in bin. 4.47MiB client-requested in use in bin.
2020-07-30 05:35:53.905379: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (524288):        Total Chunks: 2, Chunks in use: 1. 1.15MiB allocated for chunks. 562.5KiB in use in bin. 351.6KiB client-requested in use in bin.
2020-07-30 05:35:53.905410: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (1048576):       Total Chunks: 2, Chunks in use: 0. 2.39MiB allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2020-07-30 05:35:53.905439: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (2097152):       Total Chunks: 1, Chunks in use: 1. 3.43MiB allocated for chunks. 3.43MiB in use in bin. 3.43MiB client-requested in use in bin.
2020-07-30 05:35:53.905469: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (4194304):       Total Chunks: 1, Chunks in use: 1. 6.80MiB allocated for chunks. 6.80MiB in use in bin. 3.43MiB client-requested in use in bin.
2020-07-30 05:35:53.905503: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (8388608):       Total Chunks: 3, Chunks in use: 3. 31.98MiB allocated for chunks. 31.98MiB in use in bin. 26.52MiB client-requested in use in bin.
2020-07-30 05:35:53.905530: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (16777216):      Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2020-07-30 05:35:53.905562: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (33554432):      Total Chunks: 1, Chunks in use: 0. 43.39MiB allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2020-07-30 05:35:53.905589: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (67108864):      Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2020-07-30 05:35:53.905617: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (134217728):     Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2020-07-30 05:35:53.905646: I tensorflow/core/common_runtime/bfc_allocator.cc:869] Bin (268435456):     Total Chunks: 3, Chunks in use: 1. 3.00GiB allocated for chunks. 1.01GiB in use in bin. 1.01GiB client-requested in use in bin.
2020-07-30 05:35:53.905678: I tensorflow/core/common_runtime/bfc_allocator.cc:885] Bin for 1.02GiB was 256.00MiB, Chunk State:
2020-07-30 05:35:53.905719: I tensorflow/core/common_runtime/bfc_allocator.cc:891]   Size: 1019.84MiB | Requested Size: 358.83MiB | in_use: 0 | bin_num: 20, prev:   Size: 1.01GiB | Requested Size: 1.01GiB | in_use: 1 | bin_num: -1
2020-07-30 05:35:53.905750: I tensorflow/core/common_runtime/bfc_allocator.cc:891]   Size: 1.00GiB | Requested Size: 76.55MiB | in_use: 0 | bin_num: 20
2020-07-30 05:35:53.905772: I tensorflow/core/common_runtime/bfc_allocator.cc:898] Next region of size<PHONE_NUMBER>
2020-07-30 05:35:53.905797: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fec12000000 next 168 of size<PHONE_NUMBER>
2020-07-30 05:35:53.905820: I tensorflow/core/common_runtime/bfc_allocator.cc:905] Free  at 0x7fec52677a00 next<PHONE_NUMBER>3709551615 of size<PHONE_NUMBER>
2020-07-30 05:35:53.905841: I tensorflow/core/common_runtime/bfc_allocator.cc:898] Next region of size<PHONE_NUMBER>
2020-07-30 05:35:53.905862: I tensorflow/core/common_runtime/bfc_allocator.cc:905] Free  at 0x7fec98000000 next<PHONE_NUMBER>3709551615 of size<PHONE_NUMBER>
2020-07-30 05:35:53.905883: I tensorflow/core/common_runtime/bfc_allocator.cc:898] Next region of size 67108864
2020-07-30 05:35:53.905906: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed32000000 next 178 of size 10805248
2020-07-30 05:35:53.905927: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed32a4e000 next 169 of size 10805248
2020-07-30 05:35:53.905947: I tensorflow/core/common_runtime/bfc_allocator.cc:905] Free  at 0x7fed3349c000 next<PHONE_NUMBER>3709551615 of size 45498368
2020-07-30 05:35:53.905967: I tensorflow/core/common_runtime/bfc_allocator.cc:898] Next region of size 8388608
2020-07-30 05:35:53.905988: I tensorflow/core/common_runtime/bfc_allocator.cc:905] Free  at 0x7fed46600000 next 167 of size 1254400
2020-07-30 05:35:53.906008: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed46732400 next<PHONE_NUMBER>3709551615 of size 7134208
2020-07-30 05:35:53.906042: I tensorflow/core/common_runtime/bfc_allocator.cc:898] Next region of size 16777216
2020-07-30 05:35:53.906060: I tensorflow/core/common_runtime/bfc_allocator.cc:905] Free  at 0x7fed9c000000 next 171 of size 1254400
2020-07-30 05:35:53.906078: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9c132400 next 182 of size 3601920
2020-07-30 05:35:53.906097: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9c4a1a00 next<PHONE_NUMBER>3709551615 of size 11920896
2020-07-30 05:35:53.906115: I tensorflow/core/common_runtime/bfc_allocator.cc:898] Next region of size 1048576
2020-07-30 05:35:53.906133: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00000 next 1 of size 256
2020-07-30 05:35:53.906153: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00100 next 2 of size 256
2020-07-30 05:35:53.906171: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00200 next 3 of size 256
2020-07-30 05:35:53.906188: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00300 next 4 of size 256
2020-07-30 05:35:53.906207: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00400 next 5 of size 1280
2020-07-30 05:35:53.906225: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00900 next 6 of size 256
2020-07-30 05:35:53.906242: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00a00 next 7 of size 256
2020-07-30 05:35:53.906260: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00b00 next 8 of size 256
2020-07-30 05:35:53.906277: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00c00 next 9 of size 256
2020-07-30 05:35:53.906296: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da00d00 next 10 of size 1280
2020-07-30 05:35:53.906313: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01200 next 11 of size 256
2020-07-30 05:35:53.906331: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01300 next 12 of size 256
2020-07-30 05:35:53.906348: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01400 next 13 of size 256
2020-07-30 05:35:53.906366: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01500 next 14 of size 256
2020-07-30 05:35:53.906382: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01600 next 15 of size 256
2020-07-30 05:35:53.906399: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01700 next 16 of size 256
2020-07-30 05:35:53.906416: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01800 next 17 of size 256
2020-07-30 05:35:53.906434: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01900 next 18 of size 256
2020-07-30 05:35:53.906451: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01a00 next 19 of size 256
2020-07-30 05:35:53.906468: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01b00 next 20 of size 256
2020-07-30 05:35:53.906486: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01c00 next 21 of size 256
2020-07-30 05:35:53.906504: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01d00 next 22 of size 512
2020-07-30 05:35:53.906521: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da01f00 next 23 of size 256
2020-07-30 05:35:53.906539: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02000 next 24 of size 256
2020-07-30 05:35:53.906556: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02100 next 25 of size 256
2020-07-30 05:35:53.906574: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02200 next 26 of size 256
2020-07-30 05:35:53.906591: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02300 next 27 of size 1280
2020-07-30 05:35:53.906609: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02800 next 28 of size 256
2020-07-30 05:35:53.906626: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02900 next 29 of size 256
2020-07-30 05:35:53.906643: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02a00 next 30 of size 256
2020-07-30 05:35:53.906661: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02b00 next 31 of size 256
2020-07-30 05:35:53.906678: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02c00 next 32 of size 256
2020-07-30 05:35:53.906696: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da02d00 next 33 of size 1280
2020-07-30 05:35:53.906713: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03200 next 34 of size 256
2020-07-30 05:35:53.906730: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03300 next 35 of size 256
2020-07-30 05:35:53.906747: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03400 next 36 of size 256
2020-07-30 05:35:53.906765: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03500 next 37 of size 1280
2020-07-30 05:35:53.906782: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03a00 next 38 of size 256
2020-07-30 05:35:53.906800: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03b00 next 39 of size 256
2020-07-30 05:35:53.906817: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03c00 next 40 of size 256
2020-07-30 05:35:53.906834: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03d00 next 41 of size 256
2020-07-30 05:35:53.906852: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03e00 next 42 of size 256
2020-07-30 05:35:53.906869: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da03f00 next 43 of size 256
2020-07-30 05:35:53.906887: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da04000 next 44 of size 1280
2020-07-30 05:35:53.906904: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da04500 next 45 of size 256
2020-07-30 05:35:53.906921: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da04600 next 46 of size 256
2020-07-30 05:35:53.906950: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da04700 next 47 of size 256
2020-07-30 05:35:53.906970: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da04800 next 48 of size 256
2020-07-30 05:35:53.906985: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da04900 next 49 of size 1280
2020-07-30 05:35:53.907000: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da04e00 next 50 of size 256
2020-07-30 05:35:53.907016: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da04f00 next 51 of size 1280
2020-07-30 05:35:53.907033: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da05400 next 52 of size 256
2020-07-30 05:35:53.907050: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da05500 next 53 of size 256
2020-07-30 05:35:53.907078: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da05600 next 54 of size 256
2020-07-30 05:35:53.907095: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da05700 next 55 of size 1280
2020-07-30 05:35:53.907113: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da05c00 next 56 of size 256
2020-07-30 05:35:53.907129: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da05d00 next 57 of size 256
2020-07-30 05:35:53.907175: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da05e00 next 58 of size 256
2020-07-30 05:35:53.907195: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da05f00 next 59 of size 256
2020-07-30 05:35:53.907215: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da06000 next 60 of size 1280
2020-07-30 05:35:53.907232: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da06500 next 61 of size 1280
2020-07-30 05:35:53.907250: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da06a00 next 62 of size 256
2020-07-30 05:35:53.907267: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da06b00 next 63 of size 256
2020-07-30 05:35:53.907286: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da06c00 next 64 of size 1280
2020-07-30 05:35:53.907303: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07100 next 65 of size 256
2020-07-30 05:35:53.907321: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07200 next 66 of size 1280
2020-07-30 05:35:53.907338: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07700 next 67 of size 256
2020-07-30 05:35:53.907356: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07800 next 68 of size 256
2020-07-30 05:35:53.907373: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07900 next 69 of size 256
2020-07-30 05:35:53.907391: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07a00 next 70 of size 256
2020-07-30 05:35:53.907408: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07b00 next 71 of size 256
2020-07-30 05:35:53.907426: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07c00 next 72 of size 256
2020-07-30 05:35:53.907444: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07d00 next 73 of size 256
2020-07-30 05:35:53.907461: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07e00 next 74 of size 256
2020-07-30 05:35:53.907479: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da07f00 next 75 of size 256
2020-07-30 05:35:53.907496: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da08000 next 76 of size 256
2020-07-30 05:35:53.907513: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da08100 next 77 of size 256
2020-07-30 05:35:53.907531: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da08200 next 78 of size 1280
2020-07-30 05:35:53.907548: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da08700 next 79 of size 256
2020-07-30 05:35:53.907566: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da08800 next 80 of size 256
2020-07-30 05:35:53.907584: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da08900 next 81 of size 256
2020-07-30 05:35:53.907601: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da08a00 next 82 of size 256
2020-07-30 05:35:53.907619: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da08b00 next 83 of size 1280
2020-07-30 05:35:53.907636: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da09000 next 84 of size 256
2020-07-30 05:35:53.907654: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da09100 next 85 of size 256
2020-07-30 05:35:53.907671: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da09200 next 86 of size 256
2020-07-30 05:35:53.907689: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da09300 next 87 of size 256
2020-07-30 05:35:53.907707: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da09400 next 88 of size 1280
2020-07-30 05:35:53.907726: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da09900 next 89 of size 76800
2020-07-30 05:35:53.907744: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da1c500 next 90 of size 1792
2020-07-30 05:35:53.907763: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da1cc00 next 91 of size 1280
2020-07-30 05:35:53.907781: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da1d100 next 92 of size 1024
2020-07-30 05:35:53.907799: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da1d500 next 93 of size 360192
2020-07-30 05:35:53.907819: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da75400 next 94 of size 153600
2020-07-30 05:35:53.907836: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9da9ac00 next 95 of size 76800
2020-07-30 05:35:53.907854: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9daad800 next 96 of size 1280
2020-07-30 05:35:53.907873: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9daadd00 next 97 of size 8192
2020-07-30 05:35:53.907890: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9daafd00 next 98 of size 256
2020-07-30 05:35:53.907908: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9daafe00 next 99 of size 32768
2020-07-30 05:35:53.907927: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dab7e00 next 100 of size 512
2020-07-30 05:35:53.907944: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dab8000 next 101 of size 512
2020-07-30 05:35:53.907962: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dab8200 next 102 of size 16384
2020-07-30 05:35:53.907980: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dabc200 next 103 of size 256
2020-07-30 05:35:53.907998: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dabc300 next 104 of size 16384
2020-07-30 05:35:53.908016: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac0300 next 107 of size 256
2020-07-30 05:35:53.908034: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac0400 next 108 of size 1280
2020-07-30 05:35:53.908052: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac0900 next 109 of size 256
2020-07-30 05:35:53.908069: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac0a00 next 110 of size 1792
2020-07-30 05:35:53.908087: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac1100 next 111 of size 768
2020-07-30 05:35:53.908105: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac1400 next 112 of size 256
2020-07-30 05:35:53.908123: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac1500 next 113 of size 1792
2020-07-30 05:35:53.908140: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac1c00 next 114 of size 1280
2020-07-30 05:35:53.908158: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac2100 next 116 of size 16384
2020-07-30 05:35:53.908175: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac6100 next 117 of size 1280
2020-07-30 05:35:53.908193: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac6600 next 118 of size 256
2020-07-30 05:35:53.908210: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac6700 next 119 of size 1792
2020-07-30 05:35:53.908228: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac6e00 next 120 of size 256
2020-07-30 05:35:53.912712: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac6f00 next 121 of size 1280
2020-07-30 05:35:53.912733: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac7400 next 123 of size 1280
2020-07-30 05:35:53.912740: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac7900 next 124 of size 256
2020-07-30 05:35:53.912746: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dac7a00 next 125 of size 76800
2020-07-30 05:35:53.912751: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dada600 next 126 of size 256
2020-07-30 05:35:53.912756: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dada700 next 127 of size 1280
2020-07-30 05:35:53.912762: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9dadac00 next<PHONE_NUMBER>3709551615 of size 152576
2020-07-30 05:35:53.912768: I tensorflow/core/common_runtime/bfc_allocator.cc:898] Next region of size 2097152
2020-07-30 05:35:53.912773: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9de00000 next 106 of size 360192
2020-07-30 05:35:53.912779: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9de57f00 next 115 of size 363776
2020-07-30 05:35:53.912784: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9deb0c00 next 122 of size 360192
2020-07-30 05:35:53.912791: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9df08b00 next 128 of size 76800
2020-07-30 05:35:53.912797: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9df1b700 next 129 of size 360192
2020-07-30 05:35:53.912803: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9df73600 next<PHONE_NUMBER>3709551615 of size 576000
2020-07-30 05:35:53.912809: I tensorflow/core/common_runtime/bfc_allocator.cc:898] Next region of size 4194304
2020-07-30 05:35:53.912814: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fc00000 next 131 of size 76800
2020-07-30 05:35:53.912820: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fc12c00 next 132 of size 1280
2020-07-30 05:35:53.912825: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fc13100 next 133 of size 360192
2020-07-30 05:35:53.912831: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fc6b000 next 134 of size 1280
2020-07-30 05:35:53.912836: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fc6b500 next 135 of size 256
2020-07-30 05:35:53.912842: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fc6b600 next 136 of size 76800
2020-07-30 05:35:53.912847: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fc7e200 next 137 of size 360192
2020-07-30 05:35:53.912852: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fcd6100 next 138 of size 1280
2020-07-30 05:35:53.912856: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fcd6600 next 139 of size 256
2020-07-30 05:35:53.912873: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fcd6700 next 140 of size 76800
2020-07-30 05:35:53.912877: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fce9300 next 141 of size 256
2020-07-30 05:35:53.912900: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fce9400 next 142 of size 256
2020-07-30 05:35:53.912906: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fce9500 next 143 of size 256
2020-07-30 05:35:53.913188: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fce9600 next 144 of size 256
2020-07-30 05:35:53.913196: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fce9700 next 145 of size 768
2020-07-30 05:35:53.913201: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fce9a00 next 146 of size 256
2020-07-30 05:35:53.913205: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fce9b00 next 147 of size 363776
2020-07-30 05:35:53.913210: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fd42800 next 148 of size 256
2020-07-30 05:35:53.913214: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fd42900 next 149 of size 1280
2020-07-30 05:35:53.913218: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fd42e00 next 150 of size 256
2020-07-30 05:35:53.913223: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fd42f00 next 151 of size 768
2020-07-30 05:35:53.913227: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fd43200 next 152 of size 256
2020-07-30 05:35:53.913231: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fd43300 next 153 of size 360192
2020-07-30 05:35:53.913236: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fd9b200 next 154 of size 360192
2020-07-30 05:35:53.913240: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fdf3100 next 155 of size 16384
2020-07-30 05:35:53.913244: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fdf7100 next 156 of size 360192
2020-07-30 05:35:53.913249: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fe4f000 next 157 of size 1280
2020-07-30 05:35:53.913253: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fe4f500 next 158 of size 1280
2020-07-30 05:35:53.913258: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fe4fa00 next 159 of size 256
2020-07-30 05:35:53.913262: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fe4fb00 next 160 of size 360192
2020-07-30 05:35:53.913266: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9fea7a00 next 161 of size 363776
2020-07-30 05:35:53.913271: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9ff00700 next 162 of size 256
2020-07-30 05:35:53.913275: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9ff00800 next 163 of size 256
2020-07-30 05:35:53.913280: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9ff00900 next 164 of size 1280
2020-07-30 05:35:53.913284: I tensorflow/core/common_runtime/bfc_allocator.cc:905] Free  at 0x7fed9ff00e00 next 183 of size 349952
2020-07-30 05:35:53.913289: I tensorflow/core/common_runtime/bfc_allocator.cc:905] InUse at 0x7fed9ff56500 next 170 of size 61952
2020-07-30 05:35:53.913293: I tensorflow/core/common_runtime/bfc_allocator.cc:905] Free  at 0x7fed9ff65700 next<PHONE_NUMBER>3709551615 of size 633088
2020-07-30 05:35:53.913298: I tensorflow/core/common_runtime/bfc_allocator.cc:914]      Summary of in-use Chunks by size:
2020-07-30 05:35:53.913308: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 93 Chunks of size 256 totalling 23.2KiB
2020-07-30 05:35:53.913314: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 3 Chunks of size 512 totalling 1.5KiB
2020-07-30 05:35:53.914050: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 3 Chunks of size 768 totalling 2.2KiB
2020-07-30 05:35:53.914069: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 1024 totalling 1.0KiB
2020-07-30 05:35:53.914089: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 31 Chunks of size 1280 totalling 38.8KiB
2020-07-30 05:35:53.914094: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 4 Chunks of size 1792 totalling 7.0KiB
2020-07-30 05:35:53.914117: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 8192 totalling 8.0KiB
2020-07-30 05:35:53.914123: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 4 Chunks of size 16384 totalling 64.0KiB
2020-07-30 05:35:53.914129: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 32768 totalling 32.0KiB
2020-07-30 05:35:53.914134: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 61952 totalling 60.5KiB
2020-07-30 05:35:53.914140: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 7 Chunks of size 76800 totalling 525.0KiB
2020-07-30 05:35:53.914147: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 152576 totalling 149.0KiB
2020-07-30 05:35:53.914152: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 153600 totalling 150.0KiB
2020-07-30 05:35:53.914159: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 10 Chunks of size 360192 totalling 3.43MiB
2020-07-30 05:35:53.914165: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 3 Chunks of size 363776 totalling 1.04MiB
2020-07-30 05:35:53.914170: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 576000 totalling 562.5KiB
2020-07-30 05:35:53.914175: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 3601920 totalling 3.43MiB
2020-07-30 05:35:53.914180: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 7134208 totalling 6.80MiB
2020-07-30 05:35:53.914185: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 2 Chunks of size 10805248 totalling 20.61MiB
2020-07-30 05:35:53.914203: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size 11920896 totalling 11.37MiB
2020-07-30 05:35:53.914207: I tensorflow/core/common_runtime/bfc_allocator.cc:917] 1 Chunks of size<PHONE_NUMBER> totalling 1.01GiB
2020-07-30 05:35:53.914212: I tensorflow/core/common_runtime/bfc_allocator.cc:921] Sum Total of in-use chunks: 1.05GiB
2020-07-30 05:35:53.914216: I tensorflow/core/common_runtime/bfc_allocator.cc:923] total_region_allocated_bytes_:<PHONE_NUMBER> memory_limit_:<PHONE_NUMBER> available bytes: 0 curr_region_allocation_bytes_:<PHONE_NUMBER>
2020-07-30 05:35:53.914224: I tensorflow/core/common_runtime/bfc_allocator.cc:929] Stats:
Limit:<PHONE_NUMBER>
InUse:<PHONE_NUMBER>
MaxInUse:<PHONE_NUMBER>
NumAllocs:                   26656
MaxAllocSize:<PHONE_NUMBER>

2020-07-30 05:35:53.914241: W tensorflow/core/common_runtime/bfc_allocator.cc:424] *********************************________________________________________________________________*_*
2020-07-30 05:35:53.916244: W tensorflow/core/framework/op_kernel.cc:1651] OP_REQUIRES failed at concat_op.cc:153 : Resource exhausted: OOM when allocating tensor with shape[900436,303] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
 85%|█████████████████████████████████████████████████████████████████████████████████████████████▌                | 377/443 [07:53<01:22,  1.26s/it]
Traceback (most recent call last):
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1365, in _do_call
    return fn(*args)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1350, in _run_fn
    target_list, run_metadata)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1443, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.ResourceExhaustedError: 2 root error(s) found.
  (0) Resource exhausted: OOM when allocating tensor with shape[900436,303] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
         [[{{node layer2/concat}}]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.

         [[ArgMax/_187]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.

  (1) Resource exhausted: OOM when allocating tensor with shape[900436,303] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
         [[{{node layer2/concat}}]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.

0 successful operations.
0 derived errors ignored.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "run.py", line 260, in <module>
    results = sess.run(fetches, feed_dict=feed_dict)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 956, in run
    run_metadata_ptr)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1180, in _run
    feed_dict_tensor, options, run_metadata)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1359, in _do_run
    run_metadata)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1384, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.ResourceExhaustedError: 2 root error(s) found.
  (0) Resource exhausted: OOM when allocating tensor with shape[900436,303] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
         [[node layer2/concat (defined at /home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/framework/ops.py:1748) ]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.

         [[ArgMax/_187]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.

  (1) Resource exhausted: OOM when allocating tensor with shape[900436,303] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
         [[node layer2/concat (defined at /home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/framework/ops.py:1748) ]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.

0 successful operations.
0 derived errors ignored.

Original stack trace for 'layer2/concat':
  File "run.py", line 140, in <module>
    t_is_training)
  File "/home/sarim/PycharmProjects/trajectory_prediction/Point-GNN/models/models.py", line 146, in predict
    **layer_kwargs)
  File "/home/sarim/PycharmProjects/trajectory_prediction/Point-GNN/models/gnn.py", line 352, in apply_regular
    axis=-1)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/util/dispatch.py", line 180, in wrapper
    return target(*args, **kwargs)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/ops/array_ops.py", line 1420, in concat
    return gen_array_ops.concat_v2(values=values, axis=axis, name=name)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/ops/gen_array_ops.py", line 1257, in concat_v2
    "ConcatV2", values=values, axis=axis, name=name)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/framework/op_def_library.py", line 794, in _apply_op_helper
    op_def=op_def)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/framework/ops.py", line 3357, in create_op
    attrs, op_def, compute_device)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/framework/ops.py", line 3426, in _create_op_internal
    op_def=op_def)
  File "/home/sarim/PycharmProjects/trajectory_prediction/venv/lib/python3.7/site-packages/tensorflow_core/python/framework/ops.py", line 1748, in __init__
    self._traceback = tf_stack.extract_stack()

You can change the batch size in *_train_train_config file


Added maintenance5 and 6 extensions

This PR adds the VK_KHR_maintenance5 and VK_KHR_maintenance6 to the cleanup extension list.
English version only

thanks for help keeping this updated


Malformed XML file

im getting this error when trying to execute a command to a remote windows host
panic: Malformed XML file

My code is
package main

import (
	"github.com/masterzen/winrm"
	"os"
)

func main() {
	var (
		user     string = "Administrator"
		password string = "supper-awesome-password"
		host     string = "<IP_ADDRESS>"
		port     int    = 5985
	)

	endpoint := winrm.NewEndpoint(host, port, false, false, nil, nil, nil, 0)
	client, err := winrm.NewClient(endpoint, user, password)
	if err != nil {
		panic(err)
	}
	cmd := "ipconfig /all"
	_, err = client.Run(cmd, os.Stdout, os.Stderr)

	if err != nil {
		panic(err)
	}

	return
}

and my deps are
  Locking in v1.0-alpha3 (2ad3b31) for transitive dep github.com/ChrisTrenkamp/goxpath
  Locking in v0.3.0 (f21a4df) for transitive dep golang.org/x/text
  Locking in v3.2.0 (6b08a5c) for transitive dep github.com/gofrs/uuid
  Locking in master (d196dff) for transitive dep golang.org/x/net
  Using master as constraint for direct dep github.com/masterzen/winrm
  Locking in master (1d17eaf) for direct dep github.com/masterzen/winrm
  Locking in master (4572e39) for transitive dep github.com/masterzen/simplexml
  Locking in master (4a21cbd) for transitive dep github.com/Azure/go-ntlmssp
  Locking in master (a1f597e) for transitive dep golang.org/x/crypto

go version
go version go1.12.1 darwin/amd64

I've tried building https://github.com/masterzen/winrm-cli and running winrm with the same username/password/host and it was a success.
Im not sure if this is a bug or im missing something :(

Hi,
Thanks for the report. I have no idea what could be wrong (except that something doesn't sent back xml).
Since you say that the winrm-cli version is working with the same winrm server, then that means something that we introduced recently has broken something, because winrm-cli uses an older winrm (the library) version.
Would you have time to git bisect the problem and isolate what commit makes it not working?
On the other hand, you can also update winrm-cli dependencies to point the winrm master and check that it works or not.
I'll do my best to perform some tests this week.
Thanks!

thanks for the reply, ill do the bisect and report back.
I've tried digging a bit to see if i can enable debug logs but couldnt find anything (although my golang knowledge sucks).
Is there anything i can do to get some more logs out of it ?

This is starting to look like a PEBCAK :\
If i perform a go get https://github.com/masterzen/winrm and then use a simple script to execute a remote command, it works
If i do a dep init so that golang fetches winrm and other deps and then use the script to execute a remote command, it fails.

Many thanks for the troubleshooting!
You did an awesome job :)
I'll fix that bad dependency tomorrow.

Hi @mhristof ,
Indeed, dep always favor a tag as explained in the documentation:

dep generally prefers semantic versioning-tagged releases to branches (when not given any additional rules). This is a significant shift from the "default branch" model of go get and some other tools. It can result in dep making surprising choices for dependencies for which it could not infer a rule.

You won't get the issue if you use Go 1.11 module system, because the provided go.mod points to a working version of https://github.com/ChrisTrenkamp/goxpath.
Since we can't support every go vendor system (and it would be hard to sync them all), we're using the go module system.
Thank you for doing all the hard work troubleshooting this issue.
I'm going to close this ticket, feel free to reopen if you think there's something we should do in this project to solve the issue.

makes sense, i need to switch to go.mod anyway.
Cheers for the help


(fix)Executor: Experiment status patching in chaosengine

Signed-off-by: Amit Bhatt<EMAIL_ADDRESS>
This PR will help in patching experiment status in chaosengine.

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Checklist

[ ] Does this PR have a corresponding GitHub issue?
[ ] Have you included relevant README for the chaoslib/experiment with details?
[ ] Have you added debug messages where necessary?
[ ] Have you added task comments where necessary?
[ ] Have you tested the changes for possible failure conditions?
[ ] Have you provided the positive & negative test logs for the litmusbook execution?
[ ] Does the litmusbook ensure idempotency of cluster state?, i.e., is cluster restored to original state?
[ ] Have you used non-shell/command modules for Kubernetes tasks?
[ ] Have you (jinja) templatized custom scripts that is run by the litmusbook, if any?
[ ] Have you (jinja) templatized Kubernetes deployment manifests used by the litmusbook, if any?
[ ] Have you reused/created util functions instead of repeating tasks in the litmusbook?
[ ] Do the artifacts follow the appropriate directory structure?
[ ] Have you isolated storage (eg: OpenEBS) specific implementations, checks?
[ ] Have you isolated platform (eg: baremetal kubeadm/openshift/aws/gcloud) specific implementations, checks?
[ ] Are the ansible facts well defined? Is the scope explicitly set for playbook & included utils?
[ ] Have you ensured minimum/careful usage of shell utilities (awk, grep, sed, cut, xargs etc.,)?
[ ] Can the limtusbook be executed both from within & outside a container (configurable paths, no hardcode)?
[ ] Can you suggest the minimal resource requirements for the litmusbook execution?
[ ] Does the litmusbook job artifact carry comments/default options/range for the ENV tunables?
[ ] Has the litmusbooks been linted?

Special notes for your reviewer:

Chaos experiment status patching in chaosengine
user@localhost:~/Desktop/litmus-docs$ kubectl get chaosengine -o yaml
apiVersion: v1
items:
- apiVersion: litmuschaos.io/v1alpha1
  kind: ChaosEngine
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"litmuschaos.io/v1alpha1","kind":"ChaosEngine","metadata":{"annotations":{},"creationTimestamp":"2019-11-25T08:37:03Z","generation":1,"name":"engine-nginx","namespace":"default","resourceVersion":"609119","selfLink":"/apis/litmuschaos.io/v1alpha1/namespaces/default/chaosengines/engine-nginx","uid":"e45308c0-501b-4e8f-93f3-0b048d1ac4ef"},"spec":{"appinfo":{"appkind":"deployment","applabel":"app=nginx","appns":"default"},"chaosServiceAccount":"litmus","experiments":[{"name":"pod-delete","spec":{"components":null}}],"monitoring":true,"schedule":{"concurrencyPolicy":"","excludedDays":"","excludedTimes":"","interval":""}},"status":{"experimentStatuses":[{"instance":"pod-delete-23c9a4","name":"pod-delete","status":"\u003cnil\u003e","verdict":"pass"}]}}
    creationTimestamp: "2019-11-25T08:37:03Z"
    generation: 2
    name: engine-nginx
    namespace: default
    resourceVersion: "609462"
    selfLink: /apis/litmuschaos.io/v1alpha1/namespaces/default/chaosengines/engine-nginx
    uid: e45308c0-501b-4e8f-93f3-0b048d1ac4ef
  spec:
    appinfo:
      appkind: deployment
      applabel: app=nginx
      appns: default
    chaosServiceAccount: litmus
    experiments:
    - name: pod-delete
      spec:
        components: null
    monitoring: true
    schedule:
      concurrencyPolicy: ""
      excludedDays: ""
      excludedTimes: ""
      interval: ""
  status:
    experimentStatuses:
    - instance: pod-delete-23c9a4
      name: pod-delete
      status: <nil>
      verdict: pass
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""


[VS Code] Could not load file or assembly 'System.Runtime.Serialization, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.

Error:
Could not load file or assembly 'System.Runtime.Serialization, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.
Steps to Reproduce:

Install extension for vs code on mac os
Sign in via github
Error appears

Version Data

extensionName
VSLS

extensionVersion
0.2.260

protocolVersion
2.1

applicationName
VSCode

applicationVersion
1.21.0

platformName
MacOS

platformVersion
17.4.0

Hey @Dussed, thanks for reporting this!!  I think you're hitting #112.  Can you try completely shutting down VS Code and then reinstalling the extension to verify that fixes the problem?

Also, could you please take a look at ~/.vscode/extensions/ms-vsliveshare.vsliveshare-0.2.260/dotnet_modules and confirm System.Runtime.Serialization.dll is actually there?

@Dussed - Merging this with #112.  Thanks so much for the feedback so far!


Launcher does not support more OMP threads per core than hyperthreads

Given a launch command with OMP_NUM_THREADS set such as:
OMP_NUM_THREADS=4 geopmlaunch srun -N 1 -n 42 -- geopmbench
the launcher will try to assign cores to ranks assuming 1 OMP thread per hyperthread (mcfly has 44 cores and 2 hyperthreads).  It fails with the message: <geopmpy.launcher> Cores cannot be shared between MPI ranks

Improve the error message to reflect the OMP misconfig.