profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/lukaszsamson/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Łukasz Samson lukaszsamson Warsaw, Poland

elixir-lsp/elixir-ls 743

A frontend-independent IDE "smartness" server for Elixir. Implements the "Language Server Protocol" standard and provides debugger support via the "Debug Adapter Protocol"

elixir-lsp/vscode-elixir-ls 330

Elixir language support and debugger for VS Code, powered by ElixirLS.

elixir-lsp/elixir_sense 190

Provides context-aware information for code completion, documentation, go/jump to definition, signature info and more

lukaszsamson/absinthe 0

The GraphQL toolkit for Elixir

lukaszsamson/absinthe_plug 0

Plug support for Absinthe, the GraphQL toolkit for Elixir

lukaszsamson/angular2-qrcode 0

An Angular 2 component that generates a QR Code.

lukaszsamson/chess_net_0x88 0

A simple 0x88 chess engine in C# which I wrote in 2008

lukaszsamson/datetimepicker-css 0

Elm CSS package for DateTimePicker

issue commentpython-poetry/poetry

poetry 1.2.0a1: AttributeError when installing package from secondary repo

@paulmelnikow how to do that? I installed poetry via curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python - and don't see any poetry-core in $HOME/.poetry/

maksbotan

comment created time in 9 hours

issue commentpython-poetry/poetry

poetry 1.2.0a1: AttributeError when installing package from secondary repo

Having the same issue on poetry 1.1.9. One of the packages uses md5 hash. Switching to sha256 in lockfile does not help

  RuntimeError

  Retrieved digest for link my_dep-0.0.2-py3-none-any.whl(md5:somemd5hash) not in poetry.lock metadata ['sha256:somesha256hash']

  at ~/.poetry/lib/poetry/installation/chooser.py:115 in _get_links
      111│ 
      112│         if links and not selected_links:
      113│             raise RuntimeError(
      114│                 "Retrieved digest for link {}({}) not in poetry.lock metadata {}".format(
    → 115│                     link.filename, h, hashes
      116│                 )
      117│             )
      118│ 
      119│         return selected_links
maksbotan

comment created time in 9 hours

issue commentzeromq/libzmq

Assertion failed: input_stopped (src/stream_engine.cpp:443) after setting send/receive high water marks

@scottbrogden-iheartmedia if your issue is indeed related to #3937 then no, 4.3 does not fix it. In our case we disabled heartbeat_ivl and worked it around with custom heartbeats via ordinary zmq messages.

scottbrogden-iheartmedia

comment created time in 3 days

PR opened theDavidCoen/LightningExchanges

Add PrimeBit as they started supporting LN

https://twitter.com/primebit_com/status/1438078966384975872 https://blog.primebit.com/2021/07/27/superfast-low-cost-lightning-network-payments-for-bitcoin-accounts/

+1 -0

0 comment

1 changed file

pr created time in 3 days

push eventlukaszsamson/LightningExchanges

Łukasz Samson

commit sha 37bc3895878299062e76b2b58611df183b220021

Add PrimeBit as they started supporting LN https://twitter.com/primebit_com/status/1438078966384975872 https://blog.primebit.com/2021/07/27/superfast-low-cost-lightning-network-payments-for-bitcoin-accounts/

view details

push time in 3 days

fork lukaszsamson/LightningExchanges

Let's keep track of the exchanges that support Lightning Network

fork in 3 days

issue commentprysmaticlabs/prysm

Validator not able to resume operation after beacon_chain restart

Did you miss any attestation during that 90s?

No

It seems like the validator did connect successfully to the beacon node

If it if fact did reconnect, I'd expect some info level log message confirming that, e.g. Validator activated or Attestation schedule

lukaszsamson

comment created time in 7 days

issue openedprysmaticlabs/prysm

Validator not able to resume operation after beacon_chain restart

<!--💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎

Hellooo! 😄

To help us tend to your issue faster, please search our currently open issues before submitting a new one. Existing issues often contain information about workarounds, resolution, or progress updates.

💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎-->

🐞 Bug Report

Description

We run mainnet validator and beacon chain on the same linux machine. Recently we had to restart beacon_chain (to enable correctly-insert-orphaned-atts and correctly-prune-canonical-atts flags). The validator was left running during the beacon_chain restart. It was not able to resume normal operation and needed manual restart.

Has this worked before in a previous version?

I don't have logs anymore but it happened before on 1.3.x

🔬 Minimal Reproduction

With active validator and synced beacon_chain running on the same machine

  1. stop beacon_chain and wait a bit
  2. start beacon_chain
  3. observe validator logs

🔥 Error

In the logs you can see:

  1. normal operation
  2. beacon chain stop at 11:15:41
  3. validator notices grpc cancellation at 11:15:41
  4. beacon_chain start at 11:15:49
  5. 11:16:03 - 11:17:15 validator retries grpc calls every ~12s
  6. beacon_chain fully synced at 11:17:26
  7. 11:17:26 - 11:18:54 no more retries, validator stuck while beacon_chain is working correctly
  8. validator restart at 11:18:54
  9. situation back to normal

validator log <pre><code> Sep 08 11:15:41 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:15:41" level=error msg="Could not receive blocks from beacon node, could not connect" error="rpc error: code = Canceled desc = Context canceled" prefix=validator Sep 08 11:15:41 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:15:41" level=warning msg="block stream interrupted" error="rpc error: code = Canceled desc = Context canceled: could not connect" prefix=validator Sep 08 11:15:45 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:15:45" level=error msg="Failed to retrieve blocks stream, could not connect" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:4000: connect: connection refused"" prefix=validator Sep 08 11:15:45 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:15:45" level=warning msg="block stream interrupted" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:4000: connect: connection refused": could not connect" prefix=validator Sep 08 11:15:49 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:15:49" level=error msg="Failed to retrieve blocks stream, could not connect" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:4000: connect: connection refused"" prefix=validator Sep 08 11:15:51 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:15:51" level=error msg="Could not check if validators are exited" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:4000: connect: connection refused"" prefix=validator Sep 08 11:15:51 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:15:51" level=warning msg="block stream interrupted" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:4000: connect: connection refused": could not connect" prefix=validator Sep 08 11:15:55 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:15:55" level=error msg="Failed to retrieve blocks stream, could not connect" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:4000: connect: connection refused"" prefix=validator Sep 08 11:15:55 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:15:55" level=warning msg="block stream interrupted" error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:4000: connect: connection refused": could not connect" prefix=validator Sep 08 11:16:03 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:16:03" level=error msg="Could not check if validators are exited" error="rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond" prefix=validator Sep 08 11:16:15 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:16:15" level=error msg="Could not check if validators are exited" error="rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond" prefix=validator Sep 08 11:16:27 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:16:27" level=error msg="Could not check if validators are exited" error="rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond" prefix=validator Sep 08 11:16:39 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:16:39" level=error msg="Could not check if validators are exited" error="rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond" prefix=validator Sep 08 11:16:51 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:16:51" level=error msg="Could not check if validators are exited" error="rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond" prefix=validator Sep 08 11:17:03 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:17:03" level=error msg="Could not check if validators are exited" error="rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond" prefix=validator Sep 08 11:17:15 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:17:15" level=error msg="Could not check if validators are exited" error="rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond" prefix=validator Sep 08 11:18:54 eth2-prod-1a systemd[1]: Stopping Prysm Validator daemon... Sep 08 11:18:54 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:18:54" level=info msg="Got interrupt, shutting down..." prefix=node Sep 08 11:18:54 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:18:54" level=info msg="Context canceled, stopping validator" prefix=validator Sep 08 11:18:54 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:18:54" level=error msg="Could not receive blocks from beacon node, could not connect" error="rpc error: code = Canceled desc = context canceled" prefix=validator Sep 08 11:18:54 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:18:54" level=info msg="Stopping service" prefix=validator Sep 08 11:18:54 eth2-prod-1a prysm.sh[12747]: time="2021-09-08 11:18:54" level=info msg="Stopping Prysm validator" prefix=node Sep 08 11:18:54 eth2-prod-1a systemd[1]: Started Prysm Validator daemon. </code></pre>

beacon_chain log <pre><code> Sep 08 11:15:41 eth2-prod-1a systemd[1]: Current command vanished from the unit file, execution of the command list won't be resumed. Sep 08 11:15:41 eth2-prod-1a systemd[1]: Stopping Prysm Beacon chain daemon... Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=info msg="Got interrupt, shutting down..." prefix=node Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=info msg="Stopping beacon node" prefix=node Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=warning msg="Subscription next failed" error="context canceled" prefix=sync topic="/eth2/b5303f2a/voluntary_exit/ssz_snappy" Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=warning msg="Subscription next failed" error="context canceled" prefix=sync topic="/eth2/b5303f2a/beacon_aggregate_and_proof/ssz_snappy" Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=warning msg="Subscription next failed" error="context canceled" prefix=sync topic="/eth2/b5303f2a/beacon_attestation_28/ssz_snappy" Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=warning msg="Subscription next failed" error="context canceled" prefix=sync topic="/eth2/b5303f2a/beacon_attestation_44/ssz_snappy" Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=warning msg="Subscription next failed" error="context canceled" prefix=sync topic="/eth2/b5303f2a/beacon_attestation_25/ssz_snappy" Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=warning msg="Subscription next failed" error="context canceled" prefix=sync topic="/eth2/b5303f2a/beacon_block/ssz_snappy" Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=warning msg="Subscription next failed" error="context canceled" prefix=sync topic="/eth2/b5303f2a/attester_slashing/ssz_snappy" Sep 08 11:15:41 eth2-prod-1a prysm.sh[12416]: time="2021-09-08 11:15:41" level=warning msg="Subscription next failed" error="context canceled" prefix=sync topic="/eth2/b5303f2a/proposer_slashing/ssz_snappy" Sep 08 11:15:45 eth2-prod-1a systemd[1]: Stopped Prysm Beacon chain daemon. Sep 08 11:15:49 eth2-prod-1a systemd[1]: Started Prysm Beacon chain daemon. Sep 08 11:15:49 eth2-prod-1a systemd[1]: Starting Prysm Beacon chain daemon... Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: Latest Prysm version is v1.4.4. Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: Beacon chain is up to date. Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: Verifying binary integrity. Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: beacon-chain-v1.4.4-linux-amd64: OK Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: gpg: Signature made Wed Sep 1 17:45:16 2021 UTC using RSA key ID F1A5036E Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: gpg: Good signature from "Preston Van Loon preston@prysmaticlabs.com" Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: gpg: WARNING: This key is not certified with a trusted signature! Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: gpg: There is no indication that the signature belongs to the owner. Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: Primary key fingerprint: 0AE0 051D 647B A3C1 A917 AF40 72E3 3E4D F1A5 036E Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: Verified /crypto/eth2/dist/beacon-chain-v1.4.4-linux-amd64 has been signed by Prysmatic Labs. Sep 08 11:15:49 eth2-prod-1a prysm.sh[31919]: Starting Prysm beacon-chain --accept-terms-of-use --http-web3provider=http://10.21.4.17:8545 --fallback-web3provider=http://10.21.4.36:8545 --datadir=/crypto/eth2/datadir --enable-db-backup-webhook --db-backup-output-dir /crypto/eth2/backup/beacon_chain --correctly-insert-orphaned-atts --correctly-prune-canonical-atts Sep 08 11:15:50 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:50" level=warning msg="Running on Ethereum Consensus Mainnet" prefix=flags Sep 08 11:15:50 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:50" level=warning msg="Enabled feature flag" correctly-insert-orphaned-atts="This fixes a bug where orphaned attestations don't get reinserted back to mem pool. This improves validator profitability and overall network health,see issue #9441 for further detail" prefix=flags Sep 08 11:15:50 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:50" level=warning msg="Enabled feature flag" correctly-prune-canonical-atts="This fixes a bug where any block attestations can get incorrectly pruned. This improves validator profitability and overall network health,see issue #9443 for further detail" prefix=flags Sep 08 11:15:50 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:50" level=info msg="Checking DB" database-path="/crypto/eth2/datadir/beaconchaindata" prefix=node Sep 08 11:15:50 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:50" level=info msg="Deposit contract: 0x00000000219ab540356cbb839cbe05303d7705fa" prefix=node Sep 08 11:15:51 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:51" level=info msg="Waiting for state to be initialized" prefix=initial-sync Sep 08 11:15:51 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:51" level=info msg="Starting beacon node" prefix=node version="Prysm/v1.4.4/29d48dfe7eb38959752048aec700f31c3abf7484. Built at: 2021-09-01 16:20:28+00:00" Sep 08 11:15:51 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:51" level=info msg="Starting API middleware" API middleware address="127.0.0.1:3501" prefix=gateway Sep 08 11:15:51 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:51" level=info msg="gRPC server listening on port" address="127.0.0.1:4000" prefix=rpc Sep 08 11:15:51 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:51" level=warning msg="You are using an insecure gRPC server. If you are running your beacon node and validator on the same machines, you can ignore this message. If you want to know how to enable secure connections, see: https://docs.prylabs.network/docs/prysm-usage/secure-grpc" prefix=rpc Sep 08 11:15:51 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:51" level=info msg="Starting gRPC gateway" address="127.0.0.1:3500" prefix=gateway Sep 08 11:15:51 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:51" level=info msg="Connected to eth1 proof-of-work chain" endpoint="http://10.21.4.17:8545" prefix=powchain Sep 08 11:15:51 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:51" level=info msg="Blockchain data already exists in DB, initializing..." prefix=blockchain Sep 08 11:15:52 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:52" level=info msg="Chain genesis time reached" genesisStateRoot=7e76880eb67bbdc86250aa578958e9d0675e64e714337855204fb5abaaf82c2b genesisTime="2020-12-01 12:00:23 +0000 UTC" genesisValidators=21063 prefix=slotutil Sep 08 11:15:56 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:56" level=info msg="Starting initial chain sync..." prefix=initial-sync Sep 08 11:15:56 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:56" level=info msg="Waiting for enough suitable peers before syncing" prefix=initial-sync required=3 suitable=0 Sep 08 11:15:56 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:56" level=info msg="Started discovery v5" ENR="enr:-LK4QG4UoPE3GyaPBflgqc44P7qLY3Cb93xqtZj9Ftl3_DizdsOPUZujhha6IHEYYFj137XZbc8YLqRcSpSJ3f-UPCsBh2F0dG5ldHOIAAAAAAAAAACEZXRoMpC1MD8qAAAAAP__________gmlkgnY0gmlwhAoVBByJc2VjcDI1NmsxoQLqGkwmPVEerESo2LLIy2dEp-cb80LL7g4aa6-ygI-oSIN0Y3CCMsiDdWRwgi7g" prefix=p2p Sep 08 11:15:56 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:56" level=info msg="Node started p2p server" multiAddr="/ip4/10.21.4.28/tcp/13000/p2p/16Uiu2HAmBBWe1TNtAXwF97v726uAd3uzTihnU7R8ZsPGmKoar9my" prefix=p2p Sep 08 11:15:57 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:15:57" level=info msg="New gRPC client connected to beacon node" addr="127.0.0.1:47826" prefix=rpc Sep 08 11:16:02 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:16:02" level=info msg="Processing block batch of size 31 starting from 0x4ca453d6... 2022913/2022978 - estimated time remaining 41s" blocksPerSecond=1.6 peers=11 prefix=initial-sync Sep 08 11:16:56 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:16:56" level=info msg="Peer summary" activePeers=44 inbound=0 outbound=44 prefix=p2p Sep 08 11:16:59 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:16:59" level=info msg="Processing block batch of size 35 starting from 0xdd049b80... 2022944/2022983 - estimated time remaining 22s" blocksPerSecond=1.8 peers=43 prefix=initial-sync Sep 08 11:17:09 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:09" level=info msg="Synced to finalized epoch - now syncing blocks up to current head" headSlot=2022983 prefix=initial-sync syncedSlot=2022978 Sep 08 11:17:10 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:10" level=info msg="Synced new block" block=0x903b00f8... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022979 slotInEpoch=3 Sep 08 11:17:10 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:10" level=info msg="Finished applying state transition" attestations=128 prefix=blockchain Sep 08 11:17:10 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:10" level=info msg="Synced new block" block=0x8f5bdb49... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022980 slotInEpoch=4 Sep 08 11:17:10 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:10" level=info msg="Finished applying state transition" attestations=99 prefix=blockchain Sep 08 11:17:10 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:10" level=info msg="Synced new block" block=0x46eab2cf... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022981 slotInEpoch=5 Sep 08 11:17:10 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:10" level=info msg="Finished applying state transition" attestations=128 prefix=blockchain Sep 08 11:17:11 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:11" level=info msg="Synced new block" block=0x3a1bde44... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022982 slotInEpoch=6 Sep 08 11:17:11 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:11" level=info msg="Finished applying state transition" attestations=128 prefix=blockchain Sep 08 11:17:11 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:11" level=info msg="Synced new block" block=0x5f368542... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022983 slotInEpoch=7 Sep 08 11:17:11 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:11" level=info msg="Finished applying state transition" attestations=128 prefix=blockchain Sep 08 11:17:26 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:26" level=info msg="Synced to head of chain" headSlot=2022985 prefix=initial-sync syncedSlot=2022983 Sep 08 11:17:26 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:26" level=info msg="Synced up to slot 2022983" prefix=initial-sync Sep 08 11:17:31 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:31" level=info msg="Synced new block" block=0xc5643fe9... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022984 slotInEpoch=8 Sep 08 11:17:31 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:31" level=info msg="Finished applying state transition" attestations=79 prefix=blockchain Sep 08 11:17:35 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:35" level=info msg="Synced new block" block=0xe874d40e... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022985 slotInEpoch=9 Sep 08 11:17:35 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:35" level=info msg="Finished applying state transition" attestations=57 prefix=blockchain Sep 08 11:17:35 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:35" level=info msg="Synced new block" block=0x93fcc436... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022986 slotInEpoch=10 Sep 08 11:17:35 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:35" level=info msg="Finished applying state transition" attestations=128 prefix=blockchain Sep 08 11:17:47 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:47" level=info msg="Synced new block" block=0x4f401429... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022987 slotInEpoch=11 Sep 08 11:17:47 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:47" level=info msg="Finished applying state transition" attestations=60 prefix=blockchain Sep 08 11:17:56 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:56" level=info msg="Peer summary" activePeers=46 inbound=0 outbound=46 prefix=p2p Sep 08 11:17:59 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:59" level=info msg="Synced new block" block=0x9a10f50d... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022988 slotInEpoch=12 Sep 08 11:17:59 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:17:59" level=info msg="Finished applying state transition" attestations=128 prefix=blockchain Sep 08 11:18:11 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:11" level=info msg="Synced new block" block=0x28994291... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022989 slotInEpoch=13 Sep 08 11:18:11 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:11" level=info msg="Finished applying state transition" attestations=77 prefix=blockchain Sep 08 11:18:27 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:27" level=info msg="Synced new block" block=0xb8d7e3b7... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022990 slotInEpoch=14 Sep 08 11:18:27 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:27" level=info msg="Finished applying state transition" attestations=128 prefix=blockchain Sep 08 11:18:35 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:35" level=info msg="Synced new block" block=0x98f78550... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022991 slotInEpoch=15 Sep 08 11:18:35 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:35" level=info msg="Finished applying state transition" attestations=128 prefix=blockchain Sep 08 11:18:47 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:47" level=info msg="Synced new block" block=0xb879f167... epoch=63218 finalizedEpoch=63216 finalizedRoot=0xe0ee654b... prefix=blockchain slot=2022992 slotInEpoch=16 Sep 08 11:18:47 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:47" level=info msg="Finished applying state transition" attestations=64 prefix=blockchain Sep 08 11:18:56 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:56" level=info msg="Peer summary" activePeers=43 inbound=0 outbound=43 prefix=p2p Sep 08 11:18:56 eth2-prod-1a prysm.sh[31919]: time="2021-09-08 11:18:56" level=info msg="New gRPC client connected to beacon node" addr="127.0.0.1:47936" prefix=rpc </code></pre>

🌍 Your Environment

Operating System:

<pre> <code> aws linux 2 </code> </pre>

What version of Prysm are you running? (Which release)

<pre> <code> 1.4.4 </code> </pre>

Anything else relevant (validator index / public key)?

created time in 8 days

push eventlukaszsamson/telemetry_metrics_zabbix

Lukasz Samson

commit sha 457792341d865810d7c150f9f4c89cd03b7ba44a

small optimization

view details

Lukasz Samson

commit sha 8c7aae5e68f80235e64983d8daede017fa1cc83c

bump version

view details

push time in 12 days

issue commentelixir-lsp/elixir-ls

Failed to run 'elixir' command. ElixirLS will probably fail to launch.

Can you just move this issue over to that repo please?

I dont't have access in that repo. @axelson?

krainboltgreene

comment created time in 14 days

issue commentelixir-lsp/elixir-ls

Failed to run 'elixir' command. ElixirLS will probably fail to launch.

It's definitely in my .bash_rc and .bash_profile. I suspect this has to do with codespaces itself.

What really matters is wether vscode process has proper PATH environment set.

cat /proc/{vscode pid}/environ | tr '\0' '\n' | grep PATH

Verify that the session that loads vscode loads bash_rc/pash_profile correctly.

krainboltgreene

comment created time in 14 days

pull request commentelixir-lsp/elixir-ls

add additional extensions, clean

@vanjabucic are you still interested in finishing this PR?

vanjabucic

comment created time in 15 days

issue commentelixir-lsp/elixir-ls

Crash when printing into stdout inside of nif load callback

it could be a good idea to add this case to the troubleshooting section.

Sure. A PR would be welcome

kaaboaye

comment created time in 15 days

issue commentelixir-lsp/elixir-ls

Failed to run 'elixir' command. ElixirLS will probably fail to launch.

Please ensure that elixir is in PATH env of vscode process. I guess it's not correctly lading your bash_rc/bash_profile. Use search - there were already similar reports before.

I manually ran /home/codespace/.vscode-remote/extensions/jakebeck…xir-ls-0.8.1/elixir-ls-release/language_server.sh in my terminal and it booted up just fine.

Closing as this confirms that it's not a problem with elixir-ls itself. If you find it's a problem with the vscode extension please open an issue in https://github.com/elixir-lsp/vscode-elixir-ls

krainboltgreene

comment created time in 15 days

issue closedelixir-lsp/elixir-ls

Failed to run 'elixir' command. ElixirLS will probably fail to launch.

Environment

  • Elixir & Erlang versions (elixir --version): Erlang/OTP 24 [erts-12.0.2] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [jit] Elixir 1.12.1 (compiled with Erlang/OTP 24)
  • Operating system: Linux 033d18dbe177 5.4.0-1055-azure #57~18.04.1-Ubuntu SMP Fri Jul 16 19:40:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  • Editor or IDE name (e.g. Emacs/VSCode): VSCode (Codespaces)

Output logs:

[Trace - 9:57:33 AM] Sending request 'initialize - (0)'.
erl_child_setup closed

Crash dump is being written to: erl_crash.dump...done
[Info  - 9:57:35 AM] Connection to server got closed. Server will restart.

Developer Tool logs:

Failed to run 'elixir' command. ElixirLS will probably fail to launch. Logged PATH to Development Console.
[Extension Host] Failed to run 'elixir' command. Current process's PATH: /home/codespace/.vscode-remote/bin/e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
The ElixirLS - blank-application server crashed 5 times in the last 3 minutes. The server will not be restarted.

I manually ran /home/codespace/.vscode-remote/extensions/jakebeck…xir-ls-0.8.1/elixir-ls-release/language_server.sh in my terminal and it booted up just fine.

closed time in 15 days

krainboltgreene

issue closedelixir-lsp/elixir-ls

Fail when building from source

When I run mix compile I get an error saying that not all dependencies are satisfied, and that I should run mix deps.get to get them. This works fine for most of them but then I run into the error provided under the logs header. Rerunning mix compile shows that it failed to get docsh and dialyxir. I'm new to elixir and it's ecosystem, so any and all help with this will be greatly appreciated.

Environment

  • Elixir & Erlang versions (elixir --version): Erlang/OTP 24 [erts-12.0.3] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit] Elixir 1.12.2 (compiled with Erlang/OTP 24)
  • Operating system: openSUSE Tumbleweed
  • Editor or IDE name (e.g. Emacs/VSCode): Doom Emacs
  • Editor Plugin/LSP Client name: N/A

Logs

10:33:03.618 [error] Task #PID<0.199.0> started from :hex_fetcher terminating
** (UndefinedFunctionError) function :ssl.cipher_suites/1 is undefined or private
    (ssl 10.4.2) :ssl.cipher_suites(:openssl)
    (hex 0.20.5) lib/hex/http/ssl.ex:124: Hex.HTTP.SSL.filter_ciphers/1
    (hex 0.20.5) lib/hex/http/ssl.ex:66: Hex.HTTP.SSL.ssl_opts/1
    (hex 0.20.5) lib/hex/http.ex:41: Hex.HTTP.build_http_opts/2
    (hex 0.20.5) lib/hex/http.ex:16: Hex.HTTP.request/5
    (hex 0.20.5) lib/hex/registry/server.ex:306: anonymous fn/3 in Hex.Registry.Server.prefetch_online/2
    (elixir 1.12.2) lib/task/supervised.ex:90: Task.Supervised.invoke_mfa/2
    (elixir 1.12.2) lib/task/supervised.ex:35: Task.Supervised.reply/5
Function: #Function<17.45335590/0 in Hex.Registry.Server.prefetch_online/2>
    Args: []

closed time in 15 days

Pistrie

issue commentelixir-lsp/elixir-ls

Fail when building from source

Note thet this is elixir or hex that is crashing. We run CI on OTP 24 and elixir 12 with no problems. Most likely your erlang setup is incorrect/incomplete. This happens often when using erlang as packaged by Linux distros' maintainers instead of building by asdf/kerl.

Pistrie

comment created time in 15 days

issue closedelixir-lsp/elixir-ls

Crash when printing into stdout inside of nif load callback

When you print something into stdout inside erlang nif initialization callback

https://erlang.org/doc/man/erl_nif.html#initialization int (*load)(ErlNifEnv* caller_env, void** priv_data, ERL_NIF_TERM load_info)

ElixirLs in VScode will hang without any timeout on formatting or pretty much any other action.

image

There will be no output in ElixirLs logs after MIX_TARGET:

However in VScode console there will be a lot of those messages

image

Workaround

Use stderr instead of stdout. In the case of rust it will be eprintln! instead of println!.

Minimal reproduction

https://github.com/kaaboaye/elixir-ls-stdout-when-nif-load-bug-reproduction/blob/main/native/demo/src/lib.rs https://github.com/kaaboaye/elixir-ls-stdout-when-nif-load-bug-reproduction/blob/main/lib/plskillme.ex

Environment

  • Elixir & Erlang versions (elixir --version): Any I think, but tested on Elixir 1.12 OTP 24
  • Operating system: Arch on x86_64 and MacOs on AARM
  • Editor or IDE name (e.g. Emacs/VSCode): VSCode
  • Editor Plugin/LSP Client name: ElixirLS

closed time in 17 days

kaaboaye

issue commentelixir-lsp/elixir-ls

Crash when printing into stdout inside of nif load callback

That's expected as elixir-ls uses stdio for communication with the client. Language Server Protocol (https://microsoft.github.io/language-server-protocol/specifications/specification-current/#implementationConsiderations) states that pipes or sockets can be also used but none of this is currently supported nor planned though a PR would be welcome. For now please ensure that your NIFs do not write to stdout nor read from stdin.

kaaboaye

comment created time in 17 days

pull request commentelixir-lsp/elixir-ls

List all workspace symbols when an empty query comes in

@groig Have you tested it on any decent size project? IIRC this was super slow and that's why I explicitly disabled returning everything.

groig

comment created time in 18 days

issue commenthexpm/hex

mix.deps.update --all downgrades deps even when there are no conflicts

@ericmj I isolated it even further. In fact leaving just 2 deps is enough to reproduce it

{:phoenix, "~> 1.5.0"},
{:plug_cowboy, "~> 2.0"}
lukaszsamson

comment created time in 18 days

push eventlukaszsamson/elixir_deps_downgrade_repro

Lukasz Samson

commit sha cce8dbe8b4a79364c7a6aca15603b69ffcee4074

isolate

view details

push time in 18 days

issue commenthexpm/hex

mix.deps.update --all downgrades deps even when there are no conflicts

I've found a smaller non umbrella repro

  1. clone git@github.com:lukaszsamson/elixir_deps_downgrade_repro.git
  2. mix deps.get
  3. mix deps.update --all
* Updating gradualixir (https://github.com/overminddl1/gradualixir.git - master)
* Updating gradualizer (https://github.com/josefs/Gradualizer.git - master)
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  amqp 1.6.0
  amqp_client 3.8.21
  cowboy 2.9.0
  cowlib 2.11.0
  credentials_obfuscation 2.4.0
  dialyxir 1.1.0
  erlex 0.2.6
  file_system 0.2.10
  gettext 0.18.2
  goldrush 0.1.9
  jason 1.2.2
  jsx 3.1.0
  lager 3.9.2
  meck 0.9.2
  mime 2.0.1
  mock 0.3.7
  phoenix 1.5.12
  phoenix_html 2.14.3
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.1
  plug_crypto 1.2.2
  rabbit_common 3.8.21
  ranch 1.8.0
  recon 2.5.1
  telemetry 0.4.3
Downgraded:
  plug_cowboy 2.5.1 => 2.3.0
* Updating plug_cowboy (Hex package)
  1. mix deps.update plug_cowboy
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  amqp 1.6.0
  amqp_client 3.8.21
  cowboy 2.9.0
  cowboy_telemetry 0.3.1
  cowlib 2.11.0
  credentials_obfuscation 2.4.0
  dialyxir 1.1.0
  erlex 0.2.6
  file_system 0.2.10
  gettext 0.18.2
  goldrush 0.1.9
  jason 1.2.2
  jsx 3.1.0
  lager 3.9.2
  meck 0.9.2
  mime 2.0.1
  mock 0.3.7
  phoenix 1.5.12
  phoenix_html 2.14.3
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.1
  plug_crypto 1.2.2
  rabbit_common 3.8.21
  ranch 1.8.0
  recon 2.5.1
  telemetry 0.4.3
Upgraded:
  plug_cowboy 2.3.0 => 2.5.1
* Updating plug_cowboy (Hex package)

I don't recall seeing it that much in smaller projects though

lukaszsamson

comment created time in 18 days

create barnchlukaszsamson/elixir_deps_downgrade_repro

branch : master

created branch time in 18 days

created repositorylukaszsamson/elixir_deps_downgrade_repro

created time in 18 days

issue commenthexpm/hex

Hang and not helpful warning on mix deps.update --all

You can either update individual dependencies with mix deps.update APP or constarin the version on individual deps until the problem is solved

Of course I can start from scratch or go dep after dep. The point is hex is not making my job easier while it could. Also please note that deps in https://github.com/lukaszsamson/elixir_deps_resolution_bug_repro are already constrained but it still takes a lot of time. At least after constraining it's able to finish at all.

it's better to focus the development time on fixing the resolver so the warning is not needed

If that's going to get fixed soon then I'm Ok with that. However since last week the underlying issue manifested on 3 separate projects in our organisation.

lukaszsamson

comment created time in 18 days

issue commenthexpm/hex

mix.deps.update --all downgrades deps even when there are no conflicts

@ericmj I created a stub project basing on one of our projects that reproduces the issue.

  1. clone git@github.com:lukaszsamson/elixir_deps_resolution_bug_repro.git
  2. mix deps.get (gets deps fine)
  3. mix deps.update --all (why downgrade when upgrading? why it takes so long? all deps' ranges are now quite narrow)
* Updating browser (https://github.com/lukaszsamson/elixir-browser.git - origin/dev)
Resolving Hex dependencies...
The dependency resolver is taking more than 30 seconds. This typically happens when Hex cannot find a suitable set of dependencies that match your requirements. Here are some suggestions:

  1. Do not delete mix.lock. If you want to update some dependencies, do mix deps.update dep1 dep2 dep3

  2. Tighten up your dependency requirements to the latest version. Instead of {:my_dep, ">= 1.0.0"}, try {:my_dep, "~> 3.6"}

Dependency resolution completed:
Unchanged:
  absinthe 1.6.5
  absinthe_plug 1.5.8
  appsignal_plug 2.0.8
  bcrypt_elixir 2.3.0
  certifi 2.6.1
  comeonin 5.3.2
  connection 1.1.0
  corsica 1.1.3
  cowboy 2.9.0
  cowboy_telemetry 0.3.1
  cowlib 2.11.0
  db_connection 2.4.0
  decimal 1.9.0
  decorator 1.4.0
  deferred_config 0.1.1
  dialyxir 1.1.0
  ecto 3.7.1
  ecto_sql 3.7.0
  elixir_make 0.6.2
  erlex 0.2.6
  ex2ms 1.6.1
  ex_aws_s3 2.3.0
  ex_machina 2.7.0
  ex_rated 2.0.1
  excoveralls 0.14.2
  file_system 0.2.10
  gen_stage 1.1.1
  geolix 0.18.0
  gettext 0.18.2
  hackney 1.17.4
  httpoison 1.8.0
  idna 6.1.1
  jason 1.2.2
  meck 0.9.2
  metrics 1.0.1
  mime 1.6.0
  mimerl 1.2.0
  mmdb2_decoder 1.1.0
  mock 0.3.7
  mogrify 0.9.1
  nimble_csv 1.1.0
  nimble_parsec 1.1.0
  parse_trans 3.3.1
  peerage 1.0.3
  phoenix 1.5.12
  phoenix_ecto 4.4.0
  phoenix_html 3.0.0
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.0
  plug_cowboy 2.5.0
  plug_crypto 1.2.2
  poison 4.0.1
  poolboy 1.5.2
  pot 1.0.2
  ranch 1.8.0
  ssl_verify_fun 1.1.6
  stream_data 0.5.0
  telemetry 0.4.0
  unicode_util_compat 0.7.0
Upgraded:
  sweet_xml 0.7.0 => 0.7.1
Downgraded:
  appsignal 2.2.0 => 2.1.5
  appsignal_phoenix 2.0.12 => 2.0.11
  bamboo 1.7.1 => 1.7.0
  ex_aws 2.2.3 => 2.2.2
  postgrex 0.15.10 => 0.15.0
* Updating appsignal_phoenix (Hex package)
* Updating appsignal (Hex package)
* Updating bamboo (Hex package)
* Updating postgrex (Hex package)
* Updating ex_aws (Hex package)
* Updating sweet_xml (Hex package)
  1. mix deps.update postgrex (no conflicts here)
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  absinthe 1.6.5
  absinthe_plug 1.5.8
  appsignal 2.1.5
  appsignal_phoenix 2.0.11
  appsignal_plug 2.0.8
  bamboo 1.7.0
  bcrypt_elixir 2.3.0
  certifi 2.6.1
  comeonin 5.3.2
  connection 1.1.0
  corsica 1.1.3
  cowboy 2.9.0
  cowboy_telemetry 0.3.1
  cowlib 2.11.0
  db_connection 2.4.0
  decimal 1.9.0
  decorator 1.4.0
  deferred_config 0.1.1
  dialyxir 1.1.0
  ecto 3.7.1
  ecto_sql 3.7.0
  elixir_make 0.6.2
  erlex 0.2.6
  ex2ms 1.6.1
  ex_aws 2.2.2
  ex_aws_s3 2.3.0
  ex_machina 2.7.0
  ex_rated 2.0.1
  excoveralls 0.14.2
  file_system 0.2.10
  gen_stage 1.1.1
  geolix 0.18.0
  gettext 0.18.2
  hackney 1.17.4
  httpoison 1.8.0
  idna 6.1.1
  jason 1.2.2
  meck 0.9.2
  metrics 1.0.1
  mime 1.6.0
  mimerl 1.2.0
  mmdb2_decoder 1.1.0
  mock 0.3.7
  mogrify 0.9.1
  nimble_csv 1.1.0
  nimble_parsec 1.1.0
  parse_trans 3.3.1
  peerage 1.0.3
  phoenix 1.5.12
  phoenix_ecto 4.4.0
  phoenix_html 3.0.0
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.0
  plug_cowboy 2.5.0
  plug_crypto 1.2.2
  poison 4.0.1
  poolboy 1.5.2
  pot 1.0.2
  ranch 1.8.0
  ssl_verify_fun 1.1.6
  stream_data 0.5.0
  sweet_xml 0.7.1
  unicode_util_compat 0.7.0
Upgraded:
  postgrex 0.15.0 => 0.15.10
  telemetry 0.4.0 => 0.4.3
* Updating telemetry (Hex package)
* Updating postgrex (Hex package)
  1. mix deps.update appsignal (still no conflicts)
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  absinthe 1.6.5
  absinthe_plug 1.5.8
  appsignal_phoenix 2.0.11
  appsignal_plug 2.0.8
  bamboo 1.7.0
  bcrypt_elixir 2.3.0
  certifi 2.6.1
  comeonin 5.3.2
  connection 1.1.0
  corsica 1.1.3
  cowboy 2.9.0
  cowboy_telemetry 0.3.1
  cowlib 2.11.0
  db_connection 2.4.0
  decimal 1.9.0
  decorator 1.4.0
  deferred_config 0.1.1
  dialyxir 1.1.0
  ecto 3.7.1
  ecto_sql 3.7.0
  elixir_make 0.6.2
  erlex 0.2.6
  ex2ms 1.6.1
  ex_aws 2.2.2
  ex_aws_s3 2.3.0
  ex_machina 2.7.0
  ex_rated 2.0.1
  excoveralls 0.14.2
  file_system 0.2.10
  gen_stage 1.1.1
  geolix 0.18.0
  gettext 0.18.2
  hackney 1.17.4
  httpoison 1.8.0
  idna 6.1.1
  jason 1.2.2
  meck 0.9.2
  metrics 1.0.1
  mime 1.6.0
  mimerl 1.2.0
  mmdb2_decoder 1.1.0
  mock 0.3.7
  mogrify 0.9.1
  nimble_csv 1.1.0
  nimble_parsec 1.1.0
  parse_trans 3.3.1
  peerage 1.0.3
  phoenix 1.5.12
  phoenix_ecto 4.4.0
  phoenix_html 3.0.0
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.0
  plug_cowboy 2.5.0
  plug_crypto 1.2.2
  poison 4.0.1
  poolboy 1.5.2
  postgrex 0.15.10
  pot 1.0.2
  ranch 1.8.0
  ssl_verify_fun 1.1.6
  stream_data 0.5.0
  sweet_xml 0.7.1
  telemetry 0.4.3
  unicode_util_compat 0.7.0
Upgraded:
  appsignal 2.1.5 => 2.2.0
* Updating appsignal (Hex package)
  1. mix deps.update bamboo (why downgrading here? bamboo does not depend on telemetry directly, any other dependancy not changed)
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  absinthe 1.6.5
  absinthe_plug 1.5.8
  appsignal 2.2.0
  appsignal_phoenix 2.0.11
  appsignal_plug 2.0.8
  bcrypt_elixir 2.3.0
  certifi 2.6.1
  comeonin 5.3.2
  connection 1.1.0
  corsica 1.1.3
  cowboy 2.9.0
  cowboy_telemetry 0.3.1
  cowlib 2.11.0
  db_connection 2.4.0
  decimal 1.9.0
  decorator 1.4.0
  deferred_config 0.1.1
  dialyxir 1.1.0
  ecto 3.7.1
  ecto_sql 3.7.0
  elixir_make 0.6.2
  erlex 0.2.6
  ex2ms 1.6.1
  ex_aws 2.2.2
  ex_aws_s3 2.3.0
  ex_machina 2.7.0
  ex_rated 2.0.1
  excoveralls 0.14.2
  file_system 0.2.10
  gen_stage 1.1.1
  geolix 0.18.0
  gettext 0.18.2
  hackney 1.17.4
  httpoison 1.8.0
  idna 6.1.1
  jason 1.2.2
  meck 0.9.2
  metrics 1.0.1
  mime 1.6.0
  mimerl 1.2.0
  mmdb2_decoder 1.1.0
  mock 0.3.7
  mogrify 0.9.1
  nimble_csv 1.1.0
  nimble_parsec 1.1.0
  parse_trans 3.3.1
  peerage 1.0.3
  phoenix 1.5.12
  phoenix_ecto 4.4.0
  phoenix_html 3.0.0
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.0
  plug_cowboy 2.5.0
  plug_crypto 1.2.2
  poison 4.0.1
  poolboy 1.5.2
  postgrex 0.15.10
  pot 1.0.2
  ranch 1.8.0
  ssl_verify_fun 1.1.6
  stream_data 0.5.0
  sweet_xml 0.7.1
  unicode_util_compat 0.7.0
Upgraded:
  bamboo 1.7.0 => 1.7.1
Downgraded:
  telemetry 0.4.3 => 0.4.0
* Updating telemetry (Hex package)
* Updating bamboo (Hex package)
  1. mix deps.update telemetry (no conflicts - downgrade was unnecessary)
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  absinthe 1.6.5
  absinthe_plug 1.5.8
  appsignal 2.2.0
  appsignal_phoenix 2.0.11
  appsignal_plug 2.0.8
  bamboo 1.7.1
  bcrypt_elixir 2.3.0
  certifi 2.6.1
  comeonin 5.3.2
  connection 1.1.0
  corsica 1.1.3
  cowboy 2.9.0
  cowboy_telemetry 0.3.1
  cowlib 2.11.0
  db_connection 2.4.0
  decimal 1.9.0
  decorator 1.4.0
  deferred_config 0.1.1
  dialyxir 1.1.0
  ecto 3.7.1
  ecto_sql 3.7.0
  elixir_make 0.6.2
  erlex 0.2.6
  ex2ms 1.6.1
  ex_aws 2.2.2
  ex_aws_s3 2.3.0
  ex_machina 2.7.0
  ex_rated 2.0.1
  excoveralls 0.14.2
  file_system 0.2.10
  gen_stage 1.1.1
  geolix 0.18.0
  gettext 0.18.2
  hackney 1.17.4
  httpoison 1.8.0
  idna 6.1.1
  jason 1.2.2
  meck 0.9.2
  metrics 1.0.1
  mime 1.6.0
  mimerl 1.2.0
  mmdb2_decoder 1.1.0
  mock 0.3.7
  mogrify 0.9.1
  nimble_csv 1.1.0
  nimble_parsec 1.1.0
  parse_trans 3.3.1
  peerage 1.0.3
  phoenix 1.5.12
  phoenix_ecto 4.4.0
  phoenix_html 3.0.0
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.0
  plug_cowboy 2.5.0
  plug_crypto 1.2.2
  poison 4.0.1
  poolboy 1.5.2
  postgrex 0.15.10
  pot 1.0.2
  ranch 1.8.0
  ssl_verify_fun 1.1.6
  stream_data 0.5.0
  sweet_xml 0.7.1
  unicode_util_compat 0.7.0
Upgraded:
  telemetry 0.4.0 => 0.4.3
* Updating telemetry (Hex package)
  1. mix deps.update ex_aws (no conflicts)
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  absinthe 1.6.5
  absinthe_plug 1.5.8
  appsignal 2.2.0
  appsignal_phoenix 2.0.11
  appsignal_plug 2.0.8
  bamboo 1.7.1
  bcrypt_elixir 2.3.0
  certifi 2.6.1
  comeonin 5.3.2
  connection 1.1.0
  corsica 1.1.3
  cowboy 2.9.0
  cowboy_telemetry 0.3.1
  cowlib 2.11.0
  db_connection 2.4.0
  decimal 1.9.0
  decorator 1.4.0
  deferred_config 0.1.1
  dialyxir 1.1.0
  ecto 3.7.1
  ecto_sql 3.7.0
  elixir_make 0.6.2
  erlex 0.2.6
  ex2ms 1.6.1
  ex_aws_s3 2.3.0
  ex_machina 2.7.0
  ex_rated 2.0.1
  excoveralls 0.14.2
  file_system 0.2.10
  gen_stage 1.1.1
  geolix 0.18.0
  gettext 0.18.2
  hackney 1.17.4
  httpoison 1.8.0
  idna 6.1.1
  jason 1.2.2
  meck 0.9.2
  metrics 1.0.1
  mime 1.6.0
  mimerl 1.2.0
  mmdb2_decoder 1.1.0
  mock 0.3.7
  mogrify 0.9.1
  nimble_csv 1.1.0
  nimble_parsec 1.1.0
  parse_trans 3.3.1
  peerage 1.0.3
  phoenix 1.5.12
  phoenix_ecto 4.4.0
  phoenix_html 3.0.0
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.0
  plug_cowboy 2.5.0
  plug_crypto 1.2.2
  poison 4.0.1
  poolboy 1.5.2
  postgrex 0.15.10
  pot 1.0.2
  ranch 1.8.0
  ssl_verify_fun 1.1.6
  stream_data 0.5.0
  sweet_xml 0.7.1
  telemetry 0.4.3
  unicode_util_compat 0.7.0
Upgraded:
  ex_aws 2.2.2 => 2.2.4
* Updating ex_aws (Hex package)
  1. mix deps.update appsignal_phoenix (why downgrade here?
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  absinthe 1.6.5
  absinthe_plug 1.5.8
  appsignal_phoenix 2.0.11
  appsignal_plug 2.0.8
  bamboo 1.7.1
  bcrypt_elixir 2.3.0
  certifi 2.6.1
  comeonin 5.3.2
  connection 1.1.0
  corsica 1.1.3
  cowboy 2.9.0
  cowboy_telemetry 0.3.1
  cowlib 2.11.0
  db_connection 2.4.0
  decimal 1.9.0
  decorator 1.4.0
  deferred_config 0.1.1
  dialyxir 1.1.0
  ecto 3.7.1
  ecto_sql 3.7.0
  elixir_make 0.6.2
  erlex 0.2.6
  ex2ms 1.6.1
  ex_aws 2.2.4
  ex_aws_s3 2.3.0
  ex_machina 2.7.0
  ex_rated 2.0.1
  excoveralls 0.14.2
  file_system 0.2.10
  gen_stage 1.1.1
  geolix 0.18.0
  gettext 0.18.2
  hackney 1.17.4
  httpoison 1.8.0
  idna 6.1.1
  jason 1.2.2
  meck 0.9.2
  metrics 1.0.1
  mime 1.6.0
  mimerl 1.2.0
  mmdb2_decoder 1.1.0
  mock 0.3.7
  mogrify 0.9.1
  nimble_csv 1.1.0
  nimble_parsec 1.1.0
  parse_trans 3.3.1
  peerage 1.0.3
  phoenix 1.5.12
  phoenix_ecto 4.4.0
  phoenix_html 3.0.0
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.0
  plug_cowboy 2.5.0
  plug_crypto 1.2.2
  poison 4.0.1
  poolboy 1.5.2
  postgrex 0.15.10
  pot 1.0.2
  ranch 1.8.0
  ssl_verify_fun 1.1.6
  stream_data 0.5.0
  sweet_xml 0.7.1
  telemetry 0.4.3
  unicode_util_compat 0.7.0
Downgraded:
  appsignal 2.2.0 => 2.1.5
* Updating appsignal (Hex package)
  1. mix deps.update appsignal (again no conflicts, we now have all deps updated)
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  absinthe 1.6.5
  absinthe_plug 1.5.8
  appsignal_phoenix 2.0.11
  appsignal_plug 2.0.8
  bamboo 1.7.1
  bcrypt_elixir 2.3.0
  certifi 2.6.1
  comeonin 5.3.2
  connection 1.1.0
  corsica 1.1.3
  cowboy 2.9.0
  cowboy_telemetry 0.3.1
  cowlib 2.11.0
  db_connection 2.4.0
  decimal 1.9.0
  decorator 1.4.0
  deferred_config 0.1.1
  dialyxir 1.1.0
  ecto 3.7.1
  ecto_sql 3.7.0
  elixir_make 0.6.2
  erlex 0.2.6
  ex2ms 1.6.1
  ex_aws 2.2.4
  ex_aws_s3 2.3.0
  ex_machina 2.7.0
  ex_rated 2.0.1
  excoveralls 0.14.2
  file_system 0.2.10
  gen_stage 1.1.1
  geolix 0.18.0
  gettext 0.18.2
  hackney 1.17.4
  httpoison 1.8.0
  idna 6.1.1
  jason 1.2.2
  meck 0.9.2
  metrics 1.0.1
  mime 1.6.0
  mimerl 1.2.0
  mmdb2_decoder 1.1.0
  mock 0.3.7
  mogrify 0.9.1
  nimble_csv 1.1.0
  nimble_parsec 1.1.0
  parse_trans 3.3.1
  peerage 1.0.3
  phoenix 1.5.12
  phoenix_ecto 4.4.0
  phoenix_html 3.0.0
  phoenix_live_reload 1.3.3
  phoenix_pubsub 2.0.0
  plug 1.12.0
  plug_cowboy 2.5.0
  plug_crypto 1.2.2
  poison 4.0.1
  poolboy 1.5.2
  postgrex 0.15.10
  pot 1.0.2
  ranch 1.8.0
  ssl_verify_fun 1.1.6
  stream_data 0.5.0
  sweet_xml 0.7.1
  telemetry 0.4.3
  unicode_util_compat 0.7.0
Upgraded:
  appsignal 2.1.5 => 2.2.0
* Updating appsignal (Hex package)
lukaszsamson

comment created time in 18 days

push eventlukaszsamson/elixir_deps_resolution_bug_repro

Lukasz Samson

commit sha ff4ee660e96a4e77347f47dd4c36ae9fa1f616f7

bump

view details

push time in 19 days

push eventlukaszsamson/elixir_lnd_grpc

Lukasz Samson

commit sha 1eb992dc738414cec0a6a6c39e1b3ba746540904

readd version lock

view details

push time in 19 days

push eventlukaszsamson/elixir_lnd_grpc

Lukasz Samson

commit sha bbb6f689ff667d8e36a298839ef9918aeb261f4c

remove overrides

view details

push time in 19 days