This explains how to build mesa from source, and how to use the custom built mesa to run some apps and games, without needing to replace the mesa libraries that your operating system runs on.
Let's assume that you are using an x86_64 system.
| // workaround for https://github.com/cloudflare/workerd/issues/698 | |
| const originalFetch = globalThis.fetch; | |
| globalThis.fetch = async function (...args) { | |
| try { | |
| return await originalFetch.apply(this, args); | |
| } catch (e) { | |
| if (!args[1] || typeof args[1] !== 'object') throw e; | |
| const unimplementedCacheError = | |
| e && typeof e === 'object' && 'message' in e && e.message === "The 'cache' field on 'RequestInitializerDict' is not implemented."; |
| from lib import appsync | |
| def lambda_handler(event, context): | |
| print(event) | |
| input = { | |
| 'name': 'test123', | |
| 'description': 'some cool description' | |
| } |
This explains how to build mesa from source, and how to use the custom built mesa to run some apps and games, without needing to replace the mesa libraries that your operating system runs on.
Let's assume that you are using an x86_64 system.
There is no problem with being a noobie and I do not use the term to sligtht or disparage anyone.
This is a way to setup your permissions for running Plex in Linux. Different folks may use different methods.
The permissions concepts provided here apply to OSX, but the users and groups are controlled and modified differently, so much of this will not work properly. I think the command is dscl, but that could be out of date.
There are many ways to setup your permissions scheme in Linux, this methodology describes a way to do it, not everyone will like it, but it works for me, so whatever.
I have two Github accounts: oanhnn (personal) and superman (for work). I want to use both accounts on same computer (without typing password everytime, when doing git push or pull).
Use ssh keys and define host aliases in ssh config file (each alias for an account).