• Joined on 2019-03-28
sb10q opened issue M-Labs/nac3#542 2024-09-12 23:07:12 +08:00
ndarray subscript assignment has to be implemented
sb10q pushed to master at sb10q/cells 2024-09-12 22:53:05 +08:00
12e1d4d4c2 add slider GUI element
d0ed143579 copy top level assignment logic from nac3standalone
c5fe70ec9a cleanup
03d10a1907 cleanup
Compare 4 commits »
sb10q commented on issue M-Labs/nac3#541 2024-09-12 13:00:07 +08:00
globals support in nac3standalone

Also we want to be able to assign to globals, e.g.

def run() -> int32:
    global X
    X  = 34
    return 0

And they should be stored in the data segment and persist across calls…

sb10q opened issue M-Labs/nac3#541 2024-09-12 12:59:14 +08:00
globals support in nac3standalone
sb10q commented on pull request M-Labs/nac3#540 2024-09-12 10:47:58 +08:00
Async RPC support

Can this be handled entirely in nac3artiq and without passing opts all over the place?

sb10q commented on pull request M-Labs/nac3#540 2024-09-12 10:47:13 +08:00
Async RPC support

Actually, processing __artiq_rpc_flags__ doesn't work easily with NAC3, contrary to what I said earlier in the chat, sorry for that mistake. Probably better to process the AST after all.

sb10q commented on pull request M-Labs/nac3#540 2024-09-12 10:45:33 +08:00
Async RPC support

Why remove it? Then you don't know what it is afterwards.

sb10q deleted branch misc-fixes from M-Labs/nac3 2024-09-11 16:00:47 +08:00
sb10q pushed to master at M-Labs/nac3 2024-09-11 16:00:47 +08:00
3e92c491f5 [standalone] Add tests creating ndarrays with tuple dims
7f629f1579 core: fix comment in unify_call
5640a793e2 core: allow np_full to take tuple shapes
Compare 3 commits »
sb10q merged pull request M-Labs/nac3#534 2024-09-11 16:00:45 +08:00
core: Miscellaneous fixes.
sb10q pushed to master at sb10q/cells 2024-09-11 15:30:12 +08:00
dbb88ad79d support multiple cells
sb10q pushed to master at M-Labs/web2019 2024-09-10 18:45:24 +08:00
76bc87ce5c faq: add entries
sb10q pushed to master at M-Labs/it-infra 2024-09-10 17:12:52 +08:00
4a288abe2b nixbld: keep automatic flarum DB migrations
sb10q commented on pull request M-Labs/it-infra#45 2024-09-10 15:50:44 +08:00
Use postfix options for routing mails through tunnel

And why not just set the correct netmask in the first place?

Regarding the routing tables: You complain about strongswan, but you should note that it doesn't mess up the routing tables. Your…

sb10q commented on pull request M-Labs/it-infra#45 2024-09-10 15:45:57 +08:00
Use postfix options for routing mails through tunnel

And to where will you route? I repeat: with a /32 address you cannot reach any other host.

sb10q commented on pull request M-Labs/it-infra#45 2024-09-10 15:41:25 +08:00
Use postfix options for routing mails through tunnel

This IP is to acquire.

What does that mean anyway?

sb10q commented on pull request M-Labs/it-infra#45 2024-09-10 15:40:21 +08:00
Use postfix options for routing mails through tunnel

Also with a /31 the last digits should be .0 and .1, .2 is not going to work.

sb10q commented on pull request M-Labs/it-infra#45 2024-09-10 15:39:34 +08:00
Use postfix options for routing mails through tunnel

If you use /32 then you can't reach any other hosts.

sb10q commented on pull request M-Labs/it-infra#45 2024-09-10 15:37:46 +08:00
Use postfix options for routing mails through tunnel

You need to set up the policy-based routing for the interface choosing part. As has been done before with existing altnet and HKBN connections.

sb10q commented on pull request M-Labs/it-infra#45 2024-09-10 15:36:07 +08:00
Use postfix options for routing mails through tunnel

I think you'd want /31 and then route the default traffic on table 3 through 10.42.0.1 (which would be the VPS)?