neuron-explorer
Steering-first neuron explorer for Qwen3.5-4B: push every MLP neuron, keep every rollout, browse the results
翻譯準備中
測試難以測試的支付環節:待授權、Webhook 重試、重複傳送、逾時、退款與冪等性。可預測、離線、無需供應商沙箱。
AI 翻譯
Test the parts of payments that are hard to test: pending mobile-money authorization, webhook retries, duplicate deliveries, timeouts, refunds and idempotency. Deterministic, offline, no provider sand
開發工具TypeScript · HTMLGitHub @dsasante1上線中營運者未確認
試用過了嗎? 點一下就好,不需要登入。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證本地支付基礎設施模擬器,支援 Paystack、Stripe、Flutterwave 與 Kora。只要將既有整合指向 localhost,即可在本機伺服器上重現難以測試的情況:待處理的行動金錢授權、Webhook 重試與重複、逾時、退款、冪等性。行為可預測,且不需供應商沙箱。
AI 翻譯
Local payment-infrastructure emulator for Paystack, Stripe, Flutterwave and Kora. Point an existing integration at localhost and reproduce what's hard to test: pending mobile-money authorization, webhook retries and duplicates, timeouts, refunds, idempotency. Deterministic, and no provider sandbox needed.
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
A local payment infrastructure emulator. Point an existing Paystack, Stripe,
Flutterwave, Kora, Quid Payments, Tingg, WeWire or Wise integration at
localhost and test the parts of payments that are hard to test: pending
transactions, asynchronous mobile-money authorization, duplicate webhooks,
retries, timeouts, refunds, idempotency and flaky networks.
Every adapter is partially implemented, and each one's coverage is
documented honestly — see the table below.
If your production payment integration can hit it, you should be able to
reproduce it locally.檢視完整 README ↗目前無法載入完整 README。請透過原文連結閱讀。 以下為已儲存的摘錄。
A local payment infrastructure emulator. Point an existing Paystack, Stripe,
Flutterwave, Kora, Quid Payments, Tingg, WeWire or Wise integration at
localhost and test the parts of payments that are hard to test: pending
transactions, asynchronous mobile-money authorization, duplicate webhooks,
retries, timeouts, refunds, idempotency and flaky networks.
Every adapter is partially implemented, and each one's coverage is
documented honestly — see the table below.
If your production payment integration can hit it, you should be able to
reproduce it locally.檢視完整 README ↗