00:38 <GitHub150> [smoltcp] dlrobertson opened pull request #59: Implement set_ttl for Tcp and Udp sockets (master...add_ttl) https://git.io/vd16o

00:51 <GitHub123> [smoltcp] dlrobertson commented on pull request #59 c499cf9: This isn't super useful. I'd be okay with backing this out. https://git.io/vd1ie

00:51 <GitHub72> [smoltcp] dlrobertson commented on pull request #59 c499cf9: This isn't ergonomic to have to specify the `ttl` member on initialization. https://git.io/vd16h

00:51 <GitHub125> [smoltcp] dlrobertson commented on pull request #59 c499cf9: This is totally unrelated to the TTL value change. I'm 100% fine with backing this out. https://git.io/vd16j

06:30 <artiq__> force build --props=package=artiq-kc705-phaser artiq-board

06:33 <artiq__> Is there a buildbot available for the phaser environment that works ubuntu?

06:34 <sb0> artiq__, works ubuntu?

06:35 <sb0> the phaser stuff itself runs on the fpga board and is independent of the OS of your computer

06:41 <GitHub198> [smoltcp] whitequark commented on pull request #59 c499cf9: `an explicitly set TTL value`, `IANA recommended` https://git.io/vd1Hf

06:41 <GitHub11> [smoltcp] whitequark commented on pull request #59 c499cf9: `Set the time-to-live (IPv4) or hop limit (IPv6) value used in outgoing packets.` https://git.io/vd1Hv

06:41 <GitHub157> [smoltcp] whitequark commented on pull request #59 c499cf9: Same as above. https://git.io/vd1He

06:41 <GitHub113> [smoltcp] whitequark commented on pull request #59 c499cf9: `The time-to-live (IPv4) or hop limit (IPv6) value used in outgoing packets.` https://git.io/vd19j

06:41 <artiq__> Hi sb0

06:42 <artiq__> Could you please activate a buildbot for phaser environment? Or if there is one active already how can I call it?

06:43 <GitHub1> [smoltcp] whitequark commented on issue #54: @little-dude Sure why not, if it's up to smoltcp's code quality. We can always split it afterwards.... https://git.io/vd1HT

06:46 <whitequark> bb-m-labs: force build --props=package=artiq-kc705-phaser artiq-board

06:46 <bb-m-labs> build forced [ETA 13m39s]

06:46 <bb-m-labs> I'll give a shout when the build finishes

06:48 <GitHub174> [smoltcp] whitequark commented on issue #55: So... why does _smoltcp_ need to support multiple interfaces? It's not only perfectly doable but also IMO more convenient to build routing on *top* of it. That is, packets originating in the OS or destined to the OS are routed according to the OS' routing table, and the rest is handled using raw sockets, which also provide buffering, because it's not really possible to do routing without buffering with

06:52 <artiq__> Thanks bb-m-labs

07:04 <bb-m-labs> build #833 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/833

07:06 <artiq__> force build --props=package=artiq-kc705-phaser artiq-board

07:28 <sb0> artiq__, whitequark just built that package

07:28 <artiq__> I am new to buildbot. I installed buildbot. Can you tell me what commands do I need to make the buildbot program to install on my station the built?

07:28 <sb0> what exactly are you trying to do?

07:29 <artiq__> I want to install phaser environment to be run on kc7 board.

07:29 <sb0> ok, you don't need to install buildbot for that

07:29 <sb0> just follow the instructions here: http://m-labs.hk/artiq/manual-release-3/installing.html

07:32 <mithro> Have you guys used strace with vivado before?

07:33 <artiq__> sb0, So I am assuming that in release 3 I do not need to build from source to install phaser? That is I can install it just using conda?

07:34 <sb0> artiq__, yes

07:34 <sb0> and even when building from source you don't need to install buildbot

07:34 <sb0> there are separate instructions in the manual for building from source

07:36 <artiq__> Great

07:36 <sb0> artiq__, by the way, who's this? what research group are you working in?

07:38 <artiq__> This is Omid from Georgia Tech. We met at UMD :-)

07:41 <artiq__> So if I want to install phaser environment what commands do I need to change?

07:41 <sb0> just nist_qc2 -> phaser

07:41 <artiq__> I am assuming that the first one would be to change $ conda config --add channels http://conda.anaconda.org/m-labs/label/main

07:41 <sb0> no

07:42 <artiq__> OR this one: conda create -n artiq-main artiq-kc705-nist_clock ?

07:43 <sb0> yes

07:46 <artiq__> So that would just become conda create -n artiq-main artiq-kc705-phaser ?

07:46 <sb0> sure

07:46 <sb0> it's just a conda package name, you can look them up on anaconda.org

07:48 <artiq__> great! thanks

08:31 <GitHub122> [smoltcp] whitequark closed issue #56: rustfmt.toml for smoltcp https://git.io/vdiX0

08:31 <GitHub176> [smoltcp] whitequark commented on issue #56: I looked at the diff produced by rustfmt. It is 11937 line long and readability suffers, particularly badly with tests. Thank you for your work but I don't think I'm going to use rustfmt for my projects. https://git.io/vd15e

09:05 <felix_> mithro: iirc vivado tries to detect if its being straced or debugged from some version on and then just prints some error message. iirc clifford had that problem a while ago; not sure how he solved it though

09:07 <mithro> An alternative option is a fuse filesystem which traces file accesses...

09:26 <whitequark> you could just disable hat check

10:05 <GitHub180> [smoltcp] whitequark commented on pull request #57 61737cd: `writer` is a thin pointer so why not https://git.io/vd1NJ

10:05 <GitHub118> [smoltcp] whitequark commented on pull request #57 61737cd: Oh, this also works. Sweet, this is the 1st time I find higher-ranker lifetimes useful, personally. https://git.io/vd1NI

10:05 <GitHub155> [smoltcp] whitequark commented on pull request #57 61737cd: This is an implementation detail so just initialize it with struct initialization syntax. No need for a separate `new` method etc. https://git.io/vd1Nk

10:05 <GitHub26> [smoltcp] whitequark commented on pull request #57 61737cd: I think this can just be `tx_token: DeviceT::TxToken` https://git.io/vd1Nt

10:05 <GitHub165> [smoltcp] whitequark commented on pull request #57 61737cd: You should document the reason for `InterfaceInner`'s existence. https://git.io/vd1Nq

10:06 <GitHub144> [smoltcp] whitequark commented on pull request #57 61737cd: Isn't this condition inverted? I think you can just move it into the `else` branch. https://git.io/vd1Nf

10:06 <GitHub135> [smoltcp] whitequark commented on pull request #57 61737cd: You need to *first* call `f` and *then* record the packet or you'll record junk. https://git.io/vd1NU

10:06 <GitHub129> [smoltcp] whitequark commented on pull request #57 61737cd: You need a mutex because state is mutable. Without a mutex it will always perform the same action on every packet. https://git.io/vd1NT

10:06 <GitHub91> [smoltcp] whitequark commented on pull request #57 61737cd: Why is this necessary? https://git.io/vd1Nm

10:06 <GitHub16> [smoltcp] whitequark commented on pull request #57 61737cd: Is this really needed? I thought it's enough that `Device` is using `'a`. https://git.io/vd1NL

10:06 <GitHub169> [smoltcp] whitequark commented on pull request #57 61737cd: :+1: Pays off already! https://git.io/vd1NY

10:06 <GitHub182> [smoltcp] whitequark commented on issue #57: @phil-opp looks like github has marked a few comments as "outdated" where I didn't intend that, so please expand them all. https://git.io/vd1NO

10:10 <GitHub31> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vd1Nc

10:10 <GitHub31> smoltcp/master bbb54fe whitequark: Fix a (future) syntax error in the net_log macro.

10:13 <travis-ci> m-labs/smoltcp#316 (master - bbb54fe : whitequark): The build passed.

10:13 <travis-ci> Change view : https://github.com/m-labs/smoltcp/compare/096ce02ac4c9...bbb54fe2a2f3

10:13 <travis-ci> Build details : https://travis-ci.org/m-labs/smoltcp/builds/288158903

18:28 <GitHub96> [smoltcp] batonius commented on issue #55: That would mean I have to use an instance of `SocketSet` for each `EthernetInterface`, so sockets bound to 0.0.0.0 gonna be problematic, but I think I can just duplicate them. I'll try to implement this approach and report back with results. https://git.io/vdMn3

18:38 <GitHub109> [smoltcp] whitequark commented on issue #55: Once you figure out a design we might lift it into smoltcp, but right now I feel like it's not the right direction for this project to delve into. https://git.io/vdMcl