talk.tryitonline.net

« first day (568 days earlier) ← previous day next day → last day (1926 days later) »

Οurous

12:17 AM

@Dennis Thanks, mind doing it again?

Dennis

Done.

2 hours later…

Pavel

2:20 AM

@Dennis Can I ask about Q# again? Especially since QC.SE is live now. I have three ideas for handling the C# Driver until the front-end can support multiple files: Stick with a fixed default driver (limited but ok for now), read the driver from a compiler flag (hacky but preferable to no driver customization at all) or just have Q# templates be installed but only allow using Q# from a bash wrapper without adding it as a proper language.

Dennis

Where/how would I install the templates?

Pavel

@Dennis dotnet new -i "Microsoft.Quantum.ProjectTemplates::0.2-*"

Dennis

Is that a global install?

Pavel

This will enable dotnet new console -lang q#

@Dennis Yeah, netcore templates are always global.

Oh, nvm, not global. Per-user.

Dennis

I think just installing the templates will be best until TIO supports it properly.

Pavel

2:25 AM

Dennis

What does dotnet new console -lang Q# -o quantum do?

Do I do that as well, or would that be handled in Bash?

Pavel

Creates an empty Q# project with a C# driver and Q# Operation, in a new directory ./quantum, with the namespace quantum.

You could create one in /opt with a Hello World that can be linked to the current directory

But it's not necessary

The cs-core wrapper has a @/opt/microsoft/home/csharp/csopts.txt in it, what does the @ do?

Dennis

I have no idea.

Pavel

Oh.

Found it? stackoverflow.com/questions/28719148/…

Dennis

I don't think so.

@Pavel I did HOME=/opt/microsoft/home dotnet new -i "Microsoft.Quantum.ProjectTemplates::0.2-*". Could you check if that accomplished something?

ASCII-only

2:41 AM

@Pavel "This meaning of @ is defined by the date utility alone and not by bash."

Pavel

Right. So presumably in this case it means it's defined by the dotnet utility alone.

@Dennis I think it accomplished something, it doesn't seem to work though: tio.run/##S0oszvj/P7WiIL@oRMHD39fVVj@/oEQ/NzO5KL84P61EPyM/…

I think you need to chmod 766 it

(I probably forgot the correct way to permissions)

Dennis

You need cp -r /opt/microsoft/home/. .. Changing HOME means that dotnet will attempt to write to that "home" directory.

@Pavel That's universal write access and rarely what you want.

Pavel

@Dennis That worked better, but it seems you also need dotnet restore for nuget packages

Dennis

That requires making a project first, no?

Pavel

Yes, unfortunatly.

Dennis

2:49 AM

So, dotnet new console -lang Q# -o quantum?

Pavel

Yeah

Capital Q though

(It doesn't really matter, but C# namespaces are generally capitalized)

Dennis

Just copy-pasting what you wrote.

Pavel

I know, I should have realized earlier

Dennis

Everything else in that directory is lowercase, so I'll quantum for consistency.

Pavel

That works

Dennis

2:51 AM

Error: Invalid parameter(s):
-lang Q#
    'Q#' is not a valid value for -lang (language).

Pavel

ಠ_ಠ

More lowercase qs

See, that's what happened when I made that message. The Qs somehow swapped places.

Dennis

Nevermind. Forgot to set HOME.

Pavel

Dennis

Now cd quantum; dotnet restore?

Pavel

Yeah

Dennis

2:56 AM

Done. Did that help?

Pavel

It didn't, not sure why

Does cp -r copy dotfiles?

It might be that the .cache isn't being copied

Hmm, no, not the case.

Ideally, this should run and exit without errors.

@Dennis Does it work if you do dotnet run in /opt/micrsofot/home/quantum locally?

Dennis

3:12 AM

It should work now.

Pavel

It does! Nice.

@Dennis Ok, so the empty project compiles, but it seems to have trouble instantiating a QuantumSimulator object: https://tio.run/##fZBNSwMxEIbv@RXj4mEXNIseLQiioJeitgUP4iHNjt1gNtlmkpYi/e1r6n60SnUOQ96ZyfC8MxdUNo2s4dxBbmufV0o6S/bd56WtMOfAmSxgGYTxoWIoSwvJ6UUC13Dn1Aodl9RXL3fVxxqd8MoaviRWWG/QgwuGNU0TSJkFTDfksRqxQ8VnpUNRxAKfCfqgvjvuYfhzC8Cnqgq63d89rYvjzIgKqRYSB9RPBjHqMNdKgtSCqCP@rrfdgwnycauElVUFjIUyKXkXEV7fQLgFZQcfdrF3OQkmNbiGDnCASrOM36O/WQvlMaqdmCAF7dNsNOzasjZvm78M2BrNkTs8OVUpH@2M/pu6FcaaeJ1upEXew0OawVVMvy4yt8VmED99j5FILDBNHlBrewYv1uniJDnm6As

Pavel

3:30 AM

I can't tell what file it's trying to read

Dennis

3:50 AM

Neither can I. As far as error messages go, The system cannot open the device or file specified. is pretty useless...

Pavel

Does it work if run from /opt/microsoft/home?

I wonder if there's a way to intercept syscalls to see what files it's trying to access

Pavel

4:02 AM

Apparantly there is (strace/ltrace) but they're not on TIO

Downgoat

4:42 AM

@Dennis can you pull VSL

You should also now be able to remove linker step since now it will automatically detect GCC or Clang and use that

6 hours later…

Dennis

11:03 AM

@Pavel Yes, it does. I'll try to figure out what the difference is.

@Pavel The sandbox wouldn't let you use it anyway.

@Downgoat That almost works now. It generates a file with 644 permissions, so I'd have to chmod it.

Pulled and synced VSL.

3 hours later…

Pavel

2:03 PM

@Dennis Alright. I'll try to strace it locally and hope it's not a sandbox issue.

Pavel

2:49 PM

So I tried running strace with creating the simulator and without and the diff is over 2000 lines long ;-;

@Dennis The only file access that done with creating a QuantumSimulator that's not done without creating said simulator is open("/sys/devices/system/cpu", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 32

If that helps

Dennis

It does. Permission denied.

Pavel

Is that fixable?

Dennis

Not without allowing the sandbox access to everything labeled sysfs_t. Not sure if that's a good idea.

I'll see if I can safely allow it when I get back home.

Pavel

Alright

Pavel

3:15 PM

Would it be possible to set permissions for only that directory but keep the contents unreadable? That one call is the entire diff, it's not looking at at any of the files/directories inside /sys/devices/system/cpu