| import { Text, SafeAreaView, StyleSheet } from 'react-native'; | |
| // You can import supported modules from npm | |
| import { Card } from 'react-native-paper'; | |
| // or any files within the Snack | |
| import AssetExample from './components/AssetExample'; | |
| export default function App() { | |
| return ( |
| import { Text, SafeAreaView, StyleSheet } from 'react-native'; | |
| // You can import supported modules from npm | |
| import { Card } from 'react-native-paper'; | |
| // or any files within the Snack | |
| import AssetExample from './components/AssetExample'; | |
| export default function App() { | |
| return ( |
Many tools do not fully remove metadata, but just remove the link with in the metadata table. The data are thus still available in the PDF file itself.
While a lot of people rely on Exiftool to remove metadata, it actually does the same in PDFs. If you remove metadata with exiftool -all= some.pdf, you can always restore the data with exiftool -pdf-update:all= some.pdf.
There are several options to remove PDF metadata safely:
- Remove metadata with exiftool :
exiftool -all= some.pdf - Then remove ununsed objects with qpdf :
qpdf --linearize some.pdf - > some.cleaned.pdf
Many tools do not fully remove metadata, but just remove the link with in the metadata table. The data are thus still available in the PDF file itself.
While a lot of people rely on Exiftool to remove metadata, it actually does the same in PDFs. If you remove metadata with exiftool -all= some.pdf, you can always restore the data with exiftool -pdf-update:all= some.pdf.
There are several options to remove PDF metadata safely:
- Remove metadata with exiftool :
exiftool -all= some.pdf - Then remove ununsed objects with qpdf :
qpdf --linearize some.pdf - > some.cleaned.pdf
https://containers.dev an open spec that extends container definition to also include dev environment configuration including:
- packages
- lifecycle automation
- processes
- IDE configurations
- remote connection
- port forwarding
| while true; do | |
| osascript -e ' | |
| tell application "System Events" | |
| if exists process "Claude" then | |
| tell process "Claude" | |
| if exists button "Allow for This Chat" of group 2 of group 1 of group 1 of group 1 of UI element 2 of group 1 of group 1 of group 1 of group 1 of window "Claude" then | |
| click button "Allow for This Chat" of group 2 of group 1 of group 1 of group 1 of UI element 2 of group 1 of group 1 of group 1 of group 1 of window "Claude" | |
| log "clicked allow button" | |
| end if | |
| end tell |
- local https://github.com/kubernetes-sigs/kind (or just use minikube if it works for you)
- cloud https://cloud.google.com/kubernetes-engine (for PersistentVolume and Ingress, I needed to try the real deal)
- practice environment: https://github.com/arush-sal/cka-practice-environment
| Questions are not from any actual exam!!! | |
| Q: Create a job that calculates pi to 2000 decimal points using the container with the image named perl | |
| and the following commands issued to the container: ["perl", "-Mbignum=bpi", "-wle", "print bpi(2000)"] | |
| Once the job has completed, check the logs to and export the result to pi-result.txt. | |
| Solution: |
| <artifacts_info> | |
| The assistant can create and reference artifacts during conversations. Artifacts are for substantial, self-contained content that users might modify or reuse, displayed in a separate UI window for clarity. | |
| # Good artifacts are... | |
| - Substantial content (>15 lines) | |
| - Content that the user is likely to modify, iterate on, or take ownership of | |
| - Self-contained, complex content that can be understood on its own, without context from the conversation | |
| - Content intended for eventual use outside the conversation (e.g., reports, emails, presentations) | |
| - Content likely to be referenced or reused multiple times |