Discover gists
| SET @database_current = '<production>'; | |
| SET @database_dev = '<development>'; | |
| -- column and datatype comparison | |
| SELECT a.TABLE_NAME, a.COLUMN_NAME, a.DATA_TYPE, a.CHARACTER_MAXIMUM_LENGTH, | |
| b.COLUMN_NAME, b.DATA_TYPE, b.CHARACTER_MAXIMUM_LENGTH | |
| FROM information_schema.COLUMNS a | |
| LEFT JOIN information_schema.COLUMNS b ON b.COLUMN_NAME = a.COLUMN_NAME | |
| AND b.TABLE_NAME = a.TABLE_NAME | |
| AND b.TABLE_SCHEMA = @database_current | |
| WHERE a.TABLE_SCHEMA = @database_dev |
Welcome to the Cinematic Sora Video Prompts tutorial! This guide is meticulously crafted to empower creators, filmmakers, and content enthusiasts to harness the full potential of Sora, an advanced AI-powered video generation tool.
By transforming textual descriptions into dynamic, visually compelling video content, Sora bridges the gap between imagination and reality, enabling the creation of professional-grade cinematic experiences without the need for extensive technical expertise.
http://localhost:49312/updater/{action}?[parameters]
Responses are always in JSONP, responding to the function BoseUpdater.remoteCallback, which has either two or three parameters (depending upon whether token is supplied). The last parameter appears to be a "status code," whilst the penultimate parameter is the data.
With its latest reales qemu added the Venus patches so that virtio-gpu now support venus encapsulation for vulkan. This is one more piece to the puzzle towards full Vulkan support.
An outdated blog post on clollabora described in 2021 how to enable 3D acceleration of Vulkan applications in QEMU through the Venus experimental Vulkan driver for VirtIO-GPU with a local development environment. Following up on the outdated write up, this is how its done today.
Let's start with the brief description of the projects mentioned in the post & extend them:
A collection of links to the excellent "Composing Software" series of medium stories by Eric Elliott.
Edit: I see that each post in the series now has index, previous and next links. However, they don't follow a linear flow through all the articles with some pointing back to previous posts effectively locking you in a loop.
As you may know, there have been a lot of major changes from 1.20.2, to 1.20.5/6 and 1.21; which resulted in some power/action/condition/data types that cannot be re-implemented. This is due to the work-arounds being either too unreliable/too hacky, too much of a pain to maintain in the long run, or just outright impossible to do, therefore, we've decided to remove and re-structure stuff to accommodate for the changes.
(Make sure to check this list for updates, I'll be updating this frequently throughout the development of the 1.21 port!)
The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.
The correct way of creating a private frok by duplicating the repo is documented here.
For this assignment the commands are:
- Create a bare clone of the repository.
(This is temporary and will be removed so just do it wherever.)
git clone --bare [email protected]:usi-systems/easytrace.git