Hugging Face chính thức chuyển giao toàn bộ hạ tầng định tuyến suy luận sang OpenRouter, mở khóa khả năng tự động tối ưu chi phí và điều phối lưu lượng qua hơn 80 nhà cung cấp điện toán.
Discover gists
| #!/usr/bin/env python3 | |
| """ | |
| Unprivileged local kernel panic in IOApplePartitionScheme::scan() | |
| (IOStorageFamily) on macOS 27.2.1. CWE-190 integer overflow -> CWE-125 OOB read. | |
| Write-up: https://seriot.ch/security/iostoragefamily_panic.html | |
| """ | |
| import struct | |
| import sys |
Last updated: 20 November 2026
LogHog is a Chrome extension for recording timestamped observations during usability-testing sessions. No account is required.
LogHog stores information you enter into the extension, including session names or participant references, observation codes and preferences, observation notes and comments, and session and observation timestamps. This information is stored on your device using Chrome extension local storage (chrome.storage.local).
| <!DOCTYPE html> | |
| <html lang="zh-CN"><head><meta charset="utf-8"> | |
| <meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,viewport-fit=cover"> | |
| <meta name="theme-color" content="#1F5F4B"> | |
| <title>进球彩 · 2026240 期</title> | |
| <style> | |
| *{box-sizing:border-box;-webkit-tap-highlight-color:transparent} | |
| html,body{max-width:100vw;overflow-x:hidden} | |
| body{margin:0;background:#EFEBE1;color:#2A2A2A; | |
| font:14px/1.45 -apple-system,BlinkMacSystemFont,"PingFang SC","Microsoft YaHei",sans-serif; |
These files rebuild the self-hosted Faraday install the task starts from:
- Faraday built from a clean checkout of
infobyte/faradayatd00e81cd9c0279e9fa7cc48d80e52f5ced820cb1; - Postgres, Redis, the server and the Celery worker, under Docker Compose in
~/faraday; - the
plant-networkspace with three weekly Nessus imports and the team's triage; - the fourth weekly report, not imported yet.
Copy-paste this prompt into any coding agent (with browser + GitHub access) to promote one of your GitHub projects on X.
You are my promotion assistant. Your goal is to promote ONE of my GitHub projects on X (Twitter) by replying to recent, high-engagement posts, while avoiding spam detection.
| <footer> | |
| <div id="foot"> | |
| <ul class="footnav1"> | |
| <li class="footnews"><a href="https://www.eporner.com/blog/" title="Eporner BLOG">Eporner BLOG</a></li> | |
| <li><a href="/contact/" title="Contact Eporner">Contact / support</a></li> | |
| <li><a href="/advertisement/" title="Advertisement on Eporner">Advertisement</a></li> | |
| <li><a href="/faq/" title="FAQ">FAQ</a></li> | |
| <li><a href="/parentalcontrol/" title="Parental control">Parental control</a></li> | |
| <li><a href="/terms/" title="Eporner Terms of use">Terms of use</a></li> | |
| <li><a href="/privacy/" title="Eporner Privacy Policy">Privacy Policy</a></li> |
- Failed case: 0_qcom-next-ci-premerge-tests
- LAVA job: https://lava-oss.qualcomm.com/scheduler/job/285514
- Skill hint: lava-issues
Summary: The LAVA job successfully booted the kernel (Linux version 7.3.0-01887-gec599b039744) and executed the full test suite. The test definition "0_qcom-next-ci-premerge-tests" was marked as failed by LAVA because two individual tests within the suite reported failures: Probe_Failure_Check and smmu. However, both failures are pre-existing platform configuration issues unrelated to the PR changes, which only modify PCIe bandwidth control logic in drivers/pci/pcie/bwctrl.c.
- Failed case: smmu
- LAVA job: https://lava-oss.qualcomm.com/scheduler/job/285514
- Skill hint: qlijarvis-triage
Summary: The SMMU test on glymur-qli-crd failed because the video codec device (aa00000.video-codec) is not attached to any IOMMU group. The test validates that critical DMA masters (GPU, USB, Camera, Display, Video) are IOMMU-protected. All other critical masters passed, but the video codec failed this check. This is a pre-existing platform configuration issue, not a regression introduced by PR #1475.
- Failed case: Probe_Failure_Check
- LAVA job: https://lava-oss.qualcomm.com/scheduler/job/285514
- Skill hint: qlijarvis-triage
Summary: The Probe_Failure_Check test failed because it detected three error messages in dmesg during boot: one missing firmware file (regulatory.db) and two audio codec register access failures (wsa_macro ASoC errors). These are pre-existing platform/configuration issues on the glymur-crd board and are not caused by PR #1475, which only reverts PCI bandwidth control OPP/ASPM changes. The kernel booted successfully, all functional tests passed (including WiFi ON/OFF and audio DSP tests), and the system is fully operational despite these logged errors.
