Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Releases: urbit/urbit

411k-6

25 Mar 15:59
9979280

Choose a tag to compare

%base hash (check with +vat %base): 0v3.o67ps.cq1fl.tk52p.jj2dg.d11ug.rlfum.9kpgl.2f08g.eluvl.1lu71

Today ~sarlev-sarsen discovered that some ships were showing their Azimuth ethereum block as being far in the future. This was caused by an Infura incident that briefly routed all HTTP requests to the Optimism blockchain instead of the Ethereum blockchain (https://status.infura.io/incidents/g9vzrcm5cv20). Most ships regrettably listen to Ethereum through an Infura node operated by Tlon, but this incident only lasted 10 minutes so not every ship was hit.

411k-6 fixes the issue for all affected ships.

This release is on ~zod and is propagating across the network.

What's Changed

Full Changelog: 411k-5...411k-6

410k-rc3

06 Mar 15:21
5640099

Choose a tag to compare

410k-rc3 Pre-release
Pre-release

%base hash (check with +vats %base, =verb %.y): 0v1h.uvkp6.s8rfr.72una.v9saj.n3eck.bfioe.iv4q5.t220o.5opp7.rhni9

Description

During pre-release testing of 410k-rc2 a few issues were discovered:

  • Double boot protection had a bug affecting old ships and another one for ships who were migrated to directed messaging.
  • The directed messaging driver would be unnecessarily conservative in using direct routes.
  • The manual migration for directed messaging was not performing enough sanity checks for the peer before executing the migration.

For testing guide, see the release notes for 410k-rc1.

What's Changed

  • eyre: improve test ergonomics slightly by @Fang- in #7081
  • mesa: update /~/boot endpoint to support |mesa peers by @yosoyubik in #7107
  • azimuth-rpc: remove team check on-watch by @yosoyubik in #7101
  • eyre: explicit 401 instead of implicit downgrade by @Fang- in #7076
  • mesa: test migration before sending %ahoy $plea by @yosoyubik in #7108
  • ames: fix ping-bone detection in %boot scry by @pkova in #7110

Full Changelog: 410k-rc2...410k-rc3

410k-rc2

27 Feb 13:08
177dc69

Choose a tag to compare

410k-rc2 Pre-release
Pre-release

%base hash (check with +vat %base, =verb %.y): 0vp.694fn.28f63.t8kk4.f7r4k.qnfkq.ud5dp.vl28c.ph3ab.qg3of.3slrm

Description

During pre-release testing of 410k-rc1 some issues were discovered:

  • Cancelling remote scry threads with backspace was unreliable at best.
  • The %shut group encrypted remote scry namespace was not working.
  • Migrating ships to directed messaging was not possible in all cases.
  • The runtime could exit ungracefully with a crash on ctrl+d when cleaning up DM driver timer handles.
  • The DM driver would leak memory because of an unbounded remote scry cache and an unlimited pending interest table lifetime.

This release candidate fixes all of these issues. We also added stateless Urwasm to the 410 release.

For testing guide, see the release notes for 410k-rc1.

What's Changed

Full Changelog: 410k-rc1...410k-rc2

410k-rc1

14 Feb 15:01
97961f4

Choose a tag to compare

410k-rc1 Pre-release
Pre-release

%base hash (check with +vats %base, =verb %.y): 0v5.tra5n.0ka63.jcmhd.0m1mg.m2trb.c3s7o.m42bk.tkape.gv8ff.or75d

Description

410 is a major release with the following highlighted features:

  • Directed messaging, aimed at improving the reliability especially speed of Ames networking.
  • Double boot protection, aimed at fixing one of the most common failure scenarios of operating a ship.
  • Essential desks, preventing the most common upgrade failure scenario.
  • Lagoon, native matrix math for Urbit.
  • HTTP streaming, exposing the scry namespace to the web with caching in the runtime.
  • Memory usage statistics in arvo, aimed primarily at helping hosting providers monitor their ships.

Breaking changes

There are very few breaking changes in 410, most applications will be compatible with no changes.

  • The http scry url format has changed. Note that this does not affect scrying through js-http-api:
old: https://dinleb-rambep.arvo.network/_~_/cx/===/sys/kelvin
new: https://dinleb-rambep.arvo.network/_~_/===/cx/sys/kelvin 
  • The infamous |hi has a little known optional argument that allows you to send a message with your hi. This message is now of type atom instead of a tape. One byproduct of this is you can send a very large |hi to other ships, not recommended unless you're on directed messaging.
  • Certain generators and threads have been namespaced, such as +keys becoming +jael/keys. The most commonly used generators such as +vats remain unchanged.

Release candidate testing guide

This is a release candidate, do the following on important ships at your own risk

Download the appropriate vere binary for your platform:

curl -O https://bootstrap.urbit.org/vere/edge/v3.2-bc9a063d06/vere-v3.2-bc9a063d06-linux-aarch64
curl -O https://bootstrap.urbit.org/vere/edge/v3.2-bc9a063d06/vere-v3.2-bc9a063d06-linux-x86_64
curl -O https://bootstrap.urbit.org/vere/edge/v3.2-bc9a063d06/vere-v3.2-bc9a063d06-macos-aarch64
curl -O https://bootstrap.urbit.org/vere/edge/v3.2-bc9a063d06/vere-v3.2-bc9a063d06-macos-x86_64

Use the binary to boot from a pill if you want a fakeship:

curl -O https://bootstrap.urbit.org/pills/410k-rc1.pill
chmod +x ./vere-v3.2-b825a6c30b-linux-x86_64
./vere-v3.2-b825a6c30b-linux-x86_64 -F zod -B 410k-rc1.pill

Or download the update from ~marnec-dozzod-marzod if you're on a real ship

|ota ~marnec-dozzod-marzod
:: wait until downloaded
|bump

Directed messaging testing guide

410k-rc1 includes directed messaging, but it is not turned on by default yet. Initially, directed messaging has to be manually enabled on a peer by peer basis. Note that at the current time only the very sparsely populated galaxy ~sud can route directed messaging packets, which means that indirect galaxy routes will not work if you are under another galaxy. This is mainly a problem if the IP of a ship changes or if they're behind a NAT. Watch this space, we will migrate many more galaxies soon.

To migrate a peer to directed messaging, run the following command

|ahoy <the-ship>, =dry %.n

After that is successful, you can try sending a big |hi:

|hi <the-ship> (bex (bex 27))

If you want to switch back to using old ames you can do the following:

|rege <the-ship>, =dry %.n

You can migrate and test out directed messaging on the real network with ~dirmes-dozzod-dozsud.

What's Changed

New Contributors

Full Changelog: 411k-5...410k-rc1

411k-5

15 Nov 15:23
a49d059

Choose a tag to compare

%base hash (check with +vat %base): 0v18.s0keg.k75ag.suu88.ljdqm.br2t9.5f2cp.7l7i6.kvpi4.02bm8.kg9p5

Description

This release fixes three issues:

  1. The fine / eauth fix from 411k-4 caused performance degradation on some ships because of unnecessary allocations.
  2. The same fix had the potential to break galaxy lane caching in cases where the galaxies would restart the runtime.
  3. It was impossible to create a working pill for 411k-4 because of a Gall bug that a recent version of %groups uncovered.

We also include the egg-any mark that is needed for backing up and restoring ship state.

What's Changed

Full Changelog: 411k-4...411k-5

411k-4

05 Nov 16:02
199f084

Choose a tag to compare

%base hash (check with +vat %base): 0v1c.ssksn.igk95.cdp90.cgb71.8hn0b.48ukq.n17va.srq75.tank7.5o04k

Description

This week some longstanding flakiness with eauth was finally tracked down. The issue presented itself as some users hanging for minutes after pressing "Approve" on the eauth login screen. The problem was always transient and fixed itself after doing |hi with the counterparty ship.

The root cause of the problem was improper route management in Ames. In essence we were not timing out direct routes when using the fine remote scry protocol which caused the eauth flow to respond to a potentially stale IP address. This release contains #7082 to fix the issue.

The release also fixes an issue with the -dns-address flow which prevented self-hosted users from requesting a ship.arvo.network domain.

What's Changed

  • ames: expire routes on a timer by @yosoyubik in #7082
  • dbug: fix debug authentication redirect for comet identities by @pkova in #7059

Full Changelog: 411k-3...411k-4

411k-3

05 Jul 16:20
b466dfe

Choose a tag to compare

%base hash (check with +vat %base): 0v15.a5bh7.k4g2m.cla3q.9ko3q.29psk.a81d2.3h8uq.rt7ua.qahqt.j4c48

Description

A few days ago we discovered that the root cause of eAuth being flaky was remote scries failing if the ships had not communicated through Ames before. The bug was caused by incorrect permissions in the Ames %forward-lane scry endpoint. This release contains #7028 to fix the problem.

What's Changed

Full Changelog: 411k-2...411k-3

411k-2

03 Jun 12:09
0364cdd

Choose a tag to compare

%base hash (check with +vat %base): 0v1r.efrfe.6djlo.6k6g1.dlq1d.qdmgo.8nd0k.dbbhu.0oiji.rehs5.35dpv

Description

411k-2 is a minor release to fix a congestion control issue that most commonly happens when Gall applications send a list of %facts in the initial subscription response instead of one large %fact. #6991 fixes this issue.

The release also adds the +commit-event generator to help with marooned ship recovery. This generator takes a path and creates a clay commit event from the path that can be written to unix with .event/jam +commit-event /path/to/clay/file. This event then gets saved to unix into <your-ship>/.urb/put/event.jam and can be injected to a misbehaving ship with <the-ship>/.run -I event.jam.

What's Changed

Full Changelog: 411k-1...411k-2

411k-1

13 May 16:44
dad0bbf

Choose a tag to compare

%base hash (check with +vat %base): 0v1v.7d11h.3r3uv.nf5q5.dmn7e.oh2k5.laq86.hpq3c.qdh77.dqicb.k6s76

Description

411-1 is an intermediate release with bugfixes and features that didn't quite make it to 411.

The highlights of this release include:

  • The verb+ log viewer in the debug dashboard (#6959).
  • A bugfix for a problem where publishers of popular desks would take hours to run |commit.
  • A bugfix for scenarios where Gall agents would receive a breach update before Gall the vane.
  • Type shadows for commonly used types that used to print extremely large outputs in nest-fails.
  • Ames and Gall bugfixes for "ignoring message on closing bone" spam.

This is not a kelvin release and therefore includes no breaking changes.

What's Changed

New Contributors

Full Changelog: 411k...411k-1

411k-1-rc3

03 May 13:35
eca32c4

Choose a tag to compare

411k-1-rc3 Pre-release
Pre-release

Description

During pre-release testing of 411k-1-rc2 it was discovered that Jael was delivering subscription updates to Gall the vane and individual Gall agents in an undefined order. This means that apps such as %phoenix that immediately poke a ship when hearing it breach would often never receive the poke-ack. This release candidate contains #6980 to fix the issue.

What's Changed

  • jael: notify gall the vane before notifying gall agents by @pkova in #6980

Full Changelog: 411k-1-rc2...411k-1-rc3