🐛 BUG: ✘ [ERROR] fetch failed

Which Cloudflare product(s) does this pertain to?
Wrangler core
What version(s) of the tool(s) are you using?
⛅ wrangler 3.22.1
What version of Node are you using?
bun latest
What operating system are you using?
Mac
Describe the Bug
Uploading 22 new assets...
Skipped uploading 20 existing assets.
Uploaded 100% [22 out of 22]
Removing 22 stale assets...
↗  Done syncing assets
Total Upload: 323.15 KiB / gzip: 75.33 KiB

✘ [ERROR] fetch failed

success sometimes
Please provide a link to a minimal reproduction
https://github.com/willin/sso
Please provide any relevant error logs
--- 2023-12-28T13:50:31.874Z debug
🪵  Writing logs to "/Users/v0/.wrangler/logs/wrangler-2023-12-28_13-50-31_798.log"
---

--- 2023-12-28T13:50:31.874Z log
 ⛅ wrangler 3.22.1
-------------------
---

--- 2023-12-28T13:50:31.877Z log
Running custom build: bun run build
---

--- 2023-12-28T13:50:35.309Z debug
-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/user
---

--- 2023-12-28T13:50:35.309Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:35.309Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:35.309Z debug
-- END CF API REQUEST
---

--- 2023-12-28T13:50:36.659Z debug
-- START CF API RESPONSE: OK 200
---

--- 2023-12-28T13:50:36.659Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:36.659Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:36.659Z debug
-- END CF API RESPONSE
---

--- 2023-12-28T13:50:36.659Z debug
Saving to cache: {"userId":"754c9a86f8f601aef8ea2ac92e0c566d"}
---

--- 2023-12-28T13:50:36.660Z debug
Metrics dispatcher: Dispatching disabled - would have sent {"type":"event","name":"deploy worker script","properties":{"usesTypeScript":false}}.
---

--- 2023-12-28T13:50:36.661Z debug
-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/memberships?page=1
---

--- 2023-12-28T13:50:36.661Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:36.661Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:36.661Z debug
-- END CF API REQUEST
---

--- 2023-12-28T13:50:38.043Z debug
-- START CF API RESPONSE: OK 200
---

--- 2023-12-28T13:50:38.043Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:38.044Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:38.044Z debug
-- END CF API RESPONSE
---

--- 2023-12-28T13:50:38.044Z debug
Saving to cache: {"account":{"id":"96f10109ea482311a0fe5e42d6ea35f7","name":"Willin Wang"}}
---

--- 2023-12-28T13:50:38.045Z debug
-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/accounts/96f10109ea482311a0fe5e42d6ea35f7/workers/standard
---

--- 2023-12-28T13:50:38.045Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:38.045Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:38.045Z debug
-- END CF API REQUEST
---

--- 2023-12-28T13:50:39.256Z debug
-- START CF API RESPONSE: OK 200
---

--- 2023-12-28T13:50:39.256Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:39.256Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:39.256Z debug
-- END CF API RESPONSE
---

--- 2023-12-28T13:50:39.258Z debug
-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/accounts/96f10109ea482311a0fe5e42d6ea35f7/workers/services/v0-sso-web
---

--- 2023-12-28T13:50:39.258Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:39.258Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:39.258Z debug
-- END CF API REQUEST
---

--- 2023-12-28T13:50:40.226Z debug
-- START CF API RESPONSE: OK 200
---

--- 2023-12-28T13:50:40.226Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:40.226Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:40.226Z debug
-- END CF API RESPONSE
---

--- 2023-12-28T13:50:40.273Z debug
-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/accounts/96f10109ea482311a0fe5e42d6ea35f7/storage/kv/namespaces?per_page=100&order=title&direction=asc&page=1
---

--- 2023-12-28T13:50:40.273Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:40.273Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:40.273Z debug
-- END CF API REQUEST
---

--- 2023-12-28T13:50:41.180Z debug
-- START CF API RESPONSE: OK 200
---

--- 2023-12-28T13:50:41.180Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:41.180Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:41.180Z debug
-- END CF API RESPONSE
---

--- 2023-12-28T13:50:41.180Z info
Fetching list of already uploaded assets...
---

--- 2023-12-28T13:50:41.180Z debug
-- START CF API REQUEST: GET https://api.cloudflare.com/client/v4/accounts/96f10109ea482311a0fe5e42d6ea35f7/storage/kv/namespaces/d8e498ec56434e30bbb9227b92c8591e/keys?prefix=
---

--- 2023-12-28T13:50:41.180Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:41.180Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:41.180Z debug
-- END CF API REQUEST
---

--- 2023-12-28T13:50:42.189Z debug
-- START CF API RESPONSE: OK 200
---

--- 2023-12-28T13:50:42.189Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:42.190Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:42.190Z debug
-- END CF API RESPONSE
---

--- 2023-12-28T13:50:42.190Z info
Building list of assets to upload...
---

--- 2023-12-28T13:50:42.192Z info
 = _app/immutable/assets/0.Urg-3lps.79cb11519d.css (already uploaded _app/immutable/assets/0.Urg-3lps.css)
---

--- 2023-12-28T13:50:42.192Z info
 = _app/immutable/assets/_layout.Urg-3lps.79cb11519d.css (already uploaded _app/immutable/assets/_layout.Urg-3lps.css)
---

--- 2023-12-28T13:50:42.192Z info
 + _app/immutable/chunks/4.3EjWPp8f.93da6f503d.js (uploading new version of _app/immutable/chunks/4.3EjWPp8f.js)
---

--- 2023-12-28T13:50:42.193Z info
 + _app/immutable/chunks/AdSlot.GfbsTSk-.043499c3b3.js (uploading new version of _app/immutable/chunks/AdSlot.GfbsTSk-.js)
---

--- 2023-12-28T13:50:42.193Z info
 + _app/immutable/chunks/ChangeLanguage.Pgplb_fD.05c1782c2c.js (uploading new version of _app/immutable/chunks/ChangeLanguage.Pgplb_fD.js)
---

--- 2023-12-28T13:50:42.194Z info
 + _app/immutable/chunks/ChangeTheme.qUWxQpWF.ef77a42669.js (uploading new version of _app/immutable/chunks/ChangeTheme.qUWxQpWF.js)
---

--- 2023-12-28T13:50:42.194Z info
 + _app/immutable/chunks/disclose-version.HxzQiLgO.78a503a26b.js (uploading new version of _app/immutable/chunks/disclose-version.HxzQiLgO.js)
---

--- 2023-12-28T13:50:42.194Z info
 + _app/immutable/chunks/each.wkCjo8iw.02172423c6.js (uploading new version of _app/immutable/chunks/each.wkCjo8iw.js)
---

--- 2023-12-28T13:50:42.194Z info
 + _app/immutable/chunks/formatter.yg7eW7U8.fdd07c5647.js (uploading new version of _app/immutable/chunks/formatter.yg7eW7U8.js)
---

--- 2023-12-28T13:50:42.195Z info
 + _app/immutable/chunks/forms.w0Ey-5xC.2d92be590e.js (uploading new version of _app/immutable/chunks/forms.w0Ey-5xC.js)
---

--- 2023-12-28T13:50:42.195Z info
 + _app/immutable/chunks/i18n.i4f8Tejw.860a012efa.js (uploading new version of _app/immutable/chunks/i18n.i4f8Tejw.js)
---

--- 2023-12-28T13:50:42.195Z info
 + _app/immutable/chunks/index.CX7UizHQ.a9f5a8574f.js (uploading new version of _app/immutable/chunks/index.CX7UizHQ.js)
---

--- 2023-12-28T13:50:42.195Z info
 + _app/immutable/chunks/main-client.qKB2NWHE.a574e37f38.js (uploading new version of _app/immutable/chunks/main-client.qKB2NWHE.js)
---

--- 2023-12-28T13:50:42.196Z info
 + _app/immutable/chunks/navigation.RqVQecrO.6668586398.js (uploading new version of _app/immutable/chunks/navigation.RqVQecrO.js)
---

--- 2023-12-28T13:50:42.196Z info
 = _app/immutable/chunks/parse.RrI1B0B4.b998472783.js (already uploaded _app/immutable/chunks/parse.RrI1B0B4.js)
---

--- 2023-12-28T13:50:42.196Z info
 + _app/immutable/chunks/prefix.SrRpSTWp.a027056998.js (uploading new version of _app/immutable/chunks/prefix.SrRpSTWp.js)
---

--- 2023-12-28T13:50:42.196Z info
 = _app/immutable/chunks/preload-helper.0HuHagjb.b6af99f8f2.js (already uploaded _app/immutable/chunks/preload-helper.0HuHagjb.js)
---

--- 2023-12-28T13:50:42.197Z info
 + _app/immutable/chunks/runtime.p5QmDtc3.f95a48ad81.js (uploading new version of _app/immutable/chunks/runtime.p5QmDtc3.js)
---

--- 2023-12-28T13:50:42.197Z info
 + _app/immutable/chunks/singletons.pXfk2Pxa.8aa1eaf48b.js (uploading new version of _app/immutable/chunks/singletons.pXfk2Pxa.js)
---

--- 2023-12-28T13:50:42.197Z info
 + _app/immutable/chunks/stores.glrQOQQf.6b346e8e48.js (uploading new version of _app/immutable/chunks/stores.glrQOQQf.js)
---

--- 2023-12-28T13:50:42.197Z info
 = _app/immutable/chunks/utils.AWfeOWkL.dfbfe01dc8.js (already uploaded _app/immutable/chunks/utils.AWfeOWkL.js)
---

--- 2023-12-28T13:50:42.198Z info
 + _app/immutable/entry/app.Ig9ywhnQ.5b17b833a3.js (uploading new version of _app/immutable/entry/app.Ig9ywhnQ.js)
---

--- 2023-12-28T13:50:42.198Z info
 + _app/immutable/entry/start.Quggo4KH.62b727162d.js (uploading new version of _app/immutable/entry/start.Quggo4KH.js)
---

--- 2023-12-28T13:50:42.198Z info
 + _app/immutable/nodes/0.ApVu-tCx.0da080e94f.js (uploading new version of _app/immutable/nodes/0.ApVu-tCx.js)
---

--- 2023-12-28T13:50:42.198Z info
 + _app/immutable/nodes/1.lVfikgx8.e5220bfaff.js (uploading new version of _app/immutable/nodes/1.lVfikgx8.js)
---

--- 2023-12-28T13:50:42.198Z info
 + _app/immutable/nodes/10.1TICcykn.f63742dea6.js (uploading new version of _app/immutable/nodes/10.1TICcykn.js)
---

--- 2023-12-28T13:50:42.199Z info
 + _app/immutable/nodes/11.wnQnc6gj.500b85fc9b.js (uploading new version of _app/immutable/nodes/11.wnQnc6gj.js)
---

--- 2023-12-28T13:50:42.199Z info
 + _app/immutable/nodes/12.Og_S9ol9.d475df4275.js (uploading new version of _app/immutable/nodes/12.Og_S9ol9.js)
---

--- 2023-12-28T13:50:42.199Z info
 + _app/immutable/nodes/2.B5xekSKZ.bb9f52d0dc.js (uploading new version of _app/immutable/nodes/2.B5xekSKZ.js)
---

--- 2023-12-28T13:50:42.199Z info
 + _app/immutable/nodes/3.XHqN7vpU.4799f172b0.js (uploading new version of _app/immutable/nodes/3.XHqN7vpU.js)
---

--- 2023-12-28T13:50:42.199Z info
 + _app/immutable/nodes/4.XHqN7vpU.4799f172b0.js (uploading new version of _app/immutable/nodes/4.XHqN7vpU.js)
---

--- 2023-12-28T13:50:42.200Z info
 + _app/immutable/nodes/5.xfisZQ9j.d8eef6b534.js (uploading new version of _app/immutable/nodes/5.xfisZQ9j.js)
---

--- 2023-12-28T13:50:42.200Z info
 + _app/immutable/nodes/6.6u4rCFlg.e859689b23.js (uploading new version of _app/immutable/nodes/6.6u4rCFlg.js)
---

--- 2023-12-28T13:50:42.200Z info
 + _app/immutable/nodes/7.GQeLuhB-.5212226221.js (uploading new version of _app/immutable/nodes/7.GQeLuhB-.js)
---

--- 2023-12-28T13:50:42.200Z info
 + _app/immutable/nodes/8.wN0X1bWS.0c83ed378e.js (uploading new version of _app/immutable/nodes/8.wN0X1bWS.js)
---

--- 2023-12-28T13:50:42.200Z info
 + _app/immutable/nodes/9.o64eAQly.2e1ca54786.js (uploading new version of _app/immutable/nodes/9.o64eAQly.js)
---

--- 2023-12-28T13:50:42.201Z info
 + _app/version.e357d57a18.json (uploading new version of _app/version.json)
---

--- 2023-12-28T13:50:42.201Z info
 = ads.adc1402911.txt (already uploaded ads.txt)
---

--- 2023-12-28T13:50:42.201Z info
 = favicon.f5cfedb270.ico (already uploaded favicon.ico)
---

--- 2023-12-28T13:50:42.201Z info
 = favicon.4783ed1753.png (already uploaded favicon.png)
---

--- 2023-12-28T13:50:42.201Z info
 = logo.e20a1585b5.jpg (already uploaded logo.jpg)
---

--- 2023-12-28T13:50:42.202Z info
 = robots.5e79220c12.txt (already uploaded robots.txt)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/4.C6pFUE5t.ad3cd879a4.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/AdSlot.5TB7Zgn8.a20f533afc.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/ChangeLanguage.SpC8KXXC.a7711f9b85.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/ChangeTheme.pYcYw9dz.4fb60167a9.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/disclose-version.zLMZfvtP.a230433ec1.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/each.tgIEJFsl.ce8609f72c.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/formatter.9qER3qnu.df9f7ec7ce.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/forms.j-0FiBe6.489ee3e097.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/i18n.IGxQKcbs.493d8f6178.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/index.LCUhL13_.4953cb5c41.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/main-client._cmh2Tk8.89c81500dc.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/navigation.VIgaPO7U.6721ad2520.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/prefix.Yu9ncKHI.ca5d6ec3ec.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/runtime.7FXZIIzr.aa4e7e7a57.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/singletons.4WHkhFFv.5a5d420b1f.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/chunks/stores.9J4-cvZW.6feacacfb5.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/entry/app.NRlpBNDP.3942f033e3.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/entry/start.oHMZa3-e.10d7952322.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/0.2wVnOxpu.c0251f1091.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/1.GhqNaE7W.2ea06149ee.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/10.UlTgYKb9.fcf7cfaeb0.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/11.KlmzWsPi.0ad9b6033e.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/12.NgDpGyGH.c2e0f72b11.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/2.ImdCI2OM.ef5b9fbee4.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/3.suRdIy3P.1de05ffde8.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/4.suRdIy3P.1de05ffde8.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/5.Q-pSOaN8.3bf6002768.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/6.vW7x4LNY.91d1fb8e8b.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/7.lCath3J4.f2f130d4bd.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/8.mVV6Yidf.9444bf53de.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/immutable/nodes/9.-do8FVep.0f97ca2b07.js (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
 - _app/version.7fc91bfd55.json (removing as stale)
---

--- 2023-12-28T13:50:42.202Z info
Uploading 32 new assets...
---

--- 2023-12-28T13:50:42.202Z info
Skipped uploading 10 existing assets.
---

--- 2023-12-28T13:50:42.207Z debug
-- START CF API REQUEST: PUT https://api.cloudflare.com/client/v4/accounts/96f10109ea482311a0fe5e42d6ea35f7/storage/kv/namespaces/d8e498ec56434e30bbb9227b92c8591e/bulk
---

--- 2023-12-28T13:50:42.207Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:42.208Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:42.208Z debug
-- END CF API REQUEST
---

--- 2023-12-28T13:50:44.816Z debug
-- START CF API RESPONSE: OK 200
---

--- 2023-12-28T13:50:44.817Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:44.817Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:44.817Z debug
-- END CF API RESPONSE
---

--- 2023-12-28T13:50:44.817Z info
Uploaded 100% [32 out of 32]
---

--- 2023-12-28T13:50:44.817Z info
Removing 32 stale assets...
---

--- 2023-12-28T13:50:44.817Z debug
-- START CF API REQUEST: DELETE https://api.cloudflare.com/client/v4/accounts/96f10109ea482311a0fe5e42d6ea35f7/storage/kv/namespaces/d8e498ec56434e30bbb9227b92c8591e/bulk
---

--- 2023-12-28T13:50:44.817Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:44.817Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:44.817Z debug
-- END CF API REQUEST
---

--- 2023-12-28T13:50:46.256Z debug
-- START CF API RESPONSE: OK 200
---

--- 2023-12-28T13:50:46.256Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:46.256Z debug
RESPONSE: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:46.256Z debug
-- END CF API RESPONSE
---

--- 2023-12-28T13:50:46.256Z log
↗  Done syncing assets
---

--- 2023-12-28T13:50:46.260Z debug
Retrieving cached values for userId from node_modules/.cache/wrangler
---

--- 2023-12-28T13:50:46.274Z log
Total Upload: 323.15 KiB / gzip: 75.32 KiB
---

--- 2023-12-28T13:50:46.275Z debug
-- START CF API REQUEST: PUT https://api.cloudflare.com/client/v4/accounts/96f10109ea482311a0fe5e42d6ea35f7/workers/scripts/v0-sso-web?include_subdomain_availability=true&excludeScript=true
---

--- 2023-12-28T13:50:46.275Z debug
HEADERS: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:46.275Z debug
INIT: omitted; set WRANGLER_LOG_SANITIZE=false to include sanitized data
---

--- 2023-12-28T13:50:46.275Z debug
-- END CF API REQUEST
---

--- 2023-12-28T13:50:46.427Z log

---

--- 2023-12-28T13:50:46.469Z error
✘ [ERROR] fetch failed

---

--- 2023-12-28T13:50:46.469Z log
If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose
---

--- 2023-12-28T13:51:04.022Z debug
Sentry: Capturing exception TypeError: fetch failed
---

It looks like you're running Wrangler in bun? Wrangler doesn't support bun as a runtime—would you be able to try again with node?

Closing due to a lack of response.


Compatibility with React 16

Since React has deprecated PropTypes, are there any plans to upgrade Fluxxor to use the new paradigm?  Would love to continue using it, just getting tons of errors related to PropTypes.
I'd be happy to give it a shot, not sure how successful I'll be.
Thanks!

Hi,
Any ETA on upgrading Fluxxor to be compatible with react 16.We have bunch of applications we need to upgrade and are currently blocked by this issue.

Found a workaround for this while awaiting a fix.
var PropTypes = require('prop-types');
React.PropTypes = PropTypes;

Using the above code in the component or an appropriate level in the architecture enables us to use fluxxor with React 16.


Add vector and matrix utility functions

Utility functions as discussed in:
https://forum.babylonjs.com/t/matrix-vector-color-conversation-and-utilities-cleanup/49818

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15101/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15101/merge/testResults/webgl2playwright/index.html

Hi Sebavan,
the original idea was to add some functions that are not yet in the library, such as Vector2.toVector3, that feel missing because there is already a similar function, such as Vector3.toVector2.
As Deltakosh mentioned in the discussion, for the sake of tree-shaking, we should actually not put more functions in Vector and Matrix, but rather add them to the mentioned utility functions file, so I prepared this MR as a base of discussion.
Actually, personally I got unsure wether it is worth filling this file utility file already with the missing functions while the majority of this functions remains for now in Vector an Matrix classes respectively.
When it is about making the functions pure functions and not part of the classes I can also easily add them somewhere in my project.
What do you think?

Hi Sebavan, the original idea was to add some functions that are not yet in the library, such as Vector2.toVector3, that feel missing because there is already a similar function, such as Vector3.toVector2.
As Deltakosh mentioned in the discussion, for the sake of tree-shaking, we should actually not put more functions in Vector and Matrix, but rather add them to the mentioned utility functions file, so I prepared this MR as a base of discussion.
Actually, personally I got unsure wether it is worth filling this file utility file already with the missing functions while the majority of this functions remains for now in Vector an Matrix classes respectively.
When it is about making the functions pure functions and not part of the classes I can also easily add them somewhere in my project.
What do you think?

I completely agree that new addition should be in this file and this format, but here I am more questioning the general usefulness of those shortcuts and how frequently we would use them to understand if it justifies the extra maintenance and weight in the UMD scenario :-)
@deltakosh @RaananW any thoughts?

Lets keep them in your project for now and reopen if we change our mind then ?


Windows Terminal crashes when emptying settings.json with settings window open

Windows Terminal version
1.14.1962.0
Windows build number
10.0.19043.0
Other Software
N/A
Steps to reproduce

Open Terminal
Open Settings
Open JSON file
In external editor, CTRL+A to select the contents of the settings.json and press delete
Save

Expected Behavior
No crash.
Actual Behavior
Windows Terminal repopulates the settings.json file with defaults and then crashes with:
Unhandled exception at 0x00007FFCE568FB62 (KernelBase.dll) in WindowsTerminal.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x000002CDCB9A0970, 0x000000000000000A).

Which is being triggered from TerminalApp.dll!winrt::TerminalApp::implementation::AppLogic::_ApplyStartupTaskStateChange$_ResumeCoro$1() Line 1004.
Edit: Feedback Hub URL: https://aka.ms/AAhm2q3

Possibly related to #12333.

I'll triage this as a separate bug for now, but cross my fingers and hope that it's the root cause of #12333. dmps loading now......

If need be, I created another feedback at https://aka.ms/AAhmblm since my original didn't appear for over 12-13 hours under My Feedback.

Hmm. Coroutines are weird, but this looks like the error it's trying to report is "The operation attempted to access data outside the valid range..".
Interesting bit of the stack is:
2e (Inline Function) --------`--------     rpcrt4!Ndr64pSendReceive+0x2f [minio\rpc\ndr64\cltcall.cxx @ 184]
2f 000000aa`24d9dab0 00007ffc`e6abc538     rpcrt4!NdrpClientCall3+0x3a4 [minio\rpc\ndr64\cltcall.cxx @ 328]
30 000000aa`24d9de20 00007ffc`e6bcf642     combase!ObjectStublessClient+0x138 [onecore\com\combase\ndr\ndrole\amd64\stblsclt.cxx @ 369]
31 000000aa`24d9e1b0 00007ffc`613f652d     combase!ObjectStubless+0x42 [onecore\com\combase\ndr\ndrole\amd64\stubless.asm @ 176]
32 000000aa`24d9e200 00007ffc`613a8d24     TerminalApp!winrt::impl::consume_Windows_ApplicationModel_IStartupTask<winrt::Windows::ApplicationModel::IStartupTask>::State+0x2d [C:\a\_work\1\s\src\cascadia\TerminalApp\Generated Files\winrt\Windows.ApplicationModel.h @ 1077]
33 000000aa`24d9e240 00007ffc`613a4d71     TerminalApp!winrt::TerminalApp::implementation::AppLogic::_ApplyStartupTaskStateChange$_ResumeCoro$1+0x1c4 [C:\a\_work\1\s\src\cascadia\TerminalApp\AppLogic.cpp @ 1004]
34 (Inline Function) --------`--------     TerminalApp!std::experimental::coroutine_handle<void>::resume+0x9

Kinda looks like
        const auto task = co_await StartupTask::GetAsync(StartupTaskName);

        switch (task.State())
        {

Like, task was null?

Naw, this is in xaml.  MainPage::UpdateSettings -> replaces all the elements of the nav view -> NavigationView::OnMenuItemsSourceCollectionChanged

If I need to look at anything from VS 2022's debugger view for you, let me know. Just be a bit more explicit, since I hardly ever use that.

Nah, I think we can repro this pretty readily. This is probably just more fallout from doing weird stuff to our nav view. Doing this a few times seemed like I would get a friggen wild set of items in the nave view, until eventually the app would crash.

@zadjii-msft Did you need a (mini)dump for this?

Nah, this one's got a consistent repro. Just need someone to take the time to look into it at this point.

see also:

#9273
#10390

This is the SAME THING.
https://github.com/microsoft/terminal/blob/2d66dc44f5abef975bed86af12cb5facb6729a1a/src/cascadia/TerminalSettingsEditor/MainPage.cpp#L152-L157
That ReplaceAll call, causes a XAML exception higher in the stack.
We can't

Clear
RemoveAtEnd in a loop
Just RemoveAtEnd once: nope
Just RemoveAt(0) once: that crashes too.

Hmm.

@chingucoding Okay, I'm way out on a limb here. But I was looking at https://github.com/microsoft/microsoft-ui-xaml/pull/3138, which was the fix for https://github.com/microsoft/microsoft-ui-xaml/issues/2818, and thought you might have an idea here.
TL;DR: we're calling IVector<>::ReplaceAll() on our NavigationView's MenuItems to replace the list when the settings reloads (demonstrated above by just deleting your existing settings, forcing us to generate a fresh set). However, when the list decreases in length[1], it seems like the NavView just crashes.
You think if I somehow converted our std::vector<MUX::Controls::NavigationViewItem> into something that could be used as a MenuItemSource, that I could swap out the entries that way?
[1]: it's not totally clear what triggers the crash, but that seems close enough to the truth.

That's a really interesting one @zadjii-msft and I'm surprised that works. Out of curiosity, is that the fix you want to use? Reading the title of the issue, could this maybe be caused because the new collection is empty? None the less, this is a very interesting bug, thanks for mentioning me.

Is that the fix I want to use? Probably not. Am I willing though? Absolutely.

maybe be caused because the new collection is empty

Through a series of other things that transpire, the new collection actually isn't empty. When we see that the new settings file is empty, we immediately blat in the default settings, then parse that, so the new collection should have Command Prompt, PowerShell, and possibly a couple more profiles at the least.
Seems to me like anytime you remove an element from the nav view's MenuItems, we hit that exception, even if there's plenty of other elements left. Wild, right?

Ah I see, so the collection is not empty. It's really strange that this issue happens to you, I was not able to reproduce this (though I was trying this in C# which does not have a replace). Do I understand this correctly that Clear/Remove/... also doesn't work?

An alternative I could think of would be to not call ReplaceAll on the Menuitems but rather set the MenuItems property on the NavigationView. Maybe that doesn't crash?

Do I understand this correctly that Clear/Remove/... also doesn't work?

Sorry I missed this - yea no variation on Remove seemed to work. I tried Clear, RemoveAtEnd in a loop, just RemoveAtEnding once, just RemoveAt(0) once - all crashes. Wild, I know.


chore(deps): bump guava from 30.0-jre to 32.0.0-jre in /templates/java-app (#1008)

Backport
This will backport the following commits from 2.x to 1.x:

chore(deps): bump guava from 30.0-jre to 32.0.0-jre in /templates/java-app (#1008)

Questions ?
Please refer to the Backport tool documentation

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1078

Questions ?
Please refer to the Backport tool documentation


Windows 10 eval is failing to find disk to install to on Parallels

make parallels/eval-win10x64-enterprise

I verified that the Virtualbox build using the same template file and Autounattend appears to be working.
make virtualbox/eval-win10x64-enterprise

I noticed it had guest_os_type set to win-8.1 while another Packer template I've used with Parallels has win-10, but I would be surprised if that is the root cause of the failure.
I tried upgrading to the latest Packer (1.6.0), but then I was getting warnings about some outdated entries in the JSON file that they don't want/use anymore.
I'm trying out some things to narrow down the issue, but I wasn't sure if somebody had already solved this and I just missed it in an open pull request or somebody's fork.

To fix all the templates quickly I ran these two commands after I had updated to Packer 1.6.0.
for template in *.json; do packer fix $template > fixed-$template; done

for template in fixed*.json; do mv $template ${template/fixed-}; done

While reviewing the git diff it showed that it reordered the elements alphabetically but other than that it only removed the iso_checksum_type so I reset and ran sed -i'' -e '/iso_checksum_type/d' *.json which removes the entire line containing that string from all the templates and then Packer was happy again without having to make a huge diff due to the reordering.

The one downside of the above "fix" is that it appears maybe Packer internally hashes the url+checksum+checksum type and removing checksum_type lead to it downloading the ISO again even though it already had an identical one that used the exact same checksum sitting in the packer_cache directory, so I'll be filing a bug over there.

I had a lot of theories on what could be causing the issue, but it seemed like it might be related to the disk layout that only creates a single partition and didn't leave room for an EFI partition. I believe Parallels defaults to EFI for newer operating systems (in versions of Parallels Desktop >10 at least) while Virtualbox might still assume "legacy" MBR first, but just changing the partition layout didn't fix things.
Eventually I found this in another repo and it fixed the issue I was having with the templates here and Parallels.
      "prlctl": [
        [
          "set",
          "{{.Name}}",
          "--efi-boot",
          "off"
        ]
      ],

Then of course I found several mentions online of using that to fix various attachment/build issues with Parallels + Packer.
https://github.com/joefitzgerald/packer-windows/issues/105#issuecomment-441579558

Thanks a lot for your contribution btw.
As I primarily use vmware and don't have access to the osx platform, I literally have no idea what's going on with the parallels flavors of the templates and thus am forced to fix them blindly. (The original maintainers dropped support of this repo for another one).

I'm torn between the boxcutter templates that have been really useful for quite a while and the chef/bento repo which I think gets more eyes and has a stronger corporate backing plus it gets a lot more testing because their boxes are used to test their software as well.

The bento boxes get built pretty frequently, but the scope is a lot more narrow than these boxes. Signed: bento maintainer.

I personally use a combination this repo for windows boxes (which is why I offered to help maintain this as I use scripts to de-vagrantify these), and then chef-bento for everything else.
The only reason why I don't use chef-bento's Windows templates is because I'm in infosec and having support for the older Windows platforms is pretty important.

@dragon788, instead of using sed, you should consider checking out jq (https://stedolan.github.io/jq/) it's pretty much xslt but for json. Once you get the hang of its "language", doing mass changes on json templates whilst still preserving the order is pretty simple.

I definitely like jq and there is another one that acts more like the AWS JSON filtering, but for this quick removal I didn't need to look up the syntax for sed where I would have for jq, and the ordering issue actually was caused by letting Packer try to fix it which was sad but not surprising because maintaining order is only important to humans looking at diffs, JSON doesn't care.
What would be really slick is a jsondiff tool or something that ignored order as long as items had the same hierarchy. This could be useful for xml/json/yaml/toml maybe.
There is a new one called rq I came across that looks really interesting as well.


[feat] Please use different features to use different code

When I try to compile sp1's verifier into wasm, I get a bunch of the same errors. This error is caused by sp1 relying on the reqwest network library, as the mio crate is under the reqwest crate in output of cargo tree.
error[E0599]: no method named `reregister` found for struct `IoSource<std::net::UdpSocket>` in the current scope
   --> /Users/flyq/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-0.8.11/src/net/udp.rs:631:20
    |
631 |         self.inner.reregister(registry, token, interests)
    |                    ^^^^^^^^^^ method not found in `IoSource<UdpSocket>`
    |
   ::: /Users/flyq/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-0.8.11/src/io_source.rs:62:1
    |
62  | pub struct IoSource<T> {
    | ---------------------- method `reregister` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `reregister`, perhaps you need to implement it
   --> /Users/flyq/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-0.8.11/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

   Compiling typenum v1.17.0
   Compiling serde_json v1.0.116

Refer to rics0, which also relies on the reqwest network library, but the reqwest is only used under the dep:bonsai-sdk feature:
[features]
client = [
  "dep:bincode",
  "dep:bonsai-sdk",
  "dep:bytes",
  "dep:prost",
  "dep:prost-build",
  "dep:protobuf-src",
  "dep:tempfile",
  "std",
]

https://github.com/risc0/risc0/blob/c809f313d9ac84927c5fc683fe12f01c777fecf7/risc0/zkvm/Cargo.toml#L106-L115
So, when I use like this, it can compile to wasm:
risc0-zkvm = { version = "0.21.0", default-features = false, features = ["std"] }

Could you please change the title of your issue to something more descriptive?  Thanks!

I think this issue is gone with your code refactor
let me test it in the night

Same problem

Hi! If you're looking to verify Groth16 and Plonk proofs in wasm, try the no-std sp1-verifier crate. Here's an example of javascript proof verification. If you have more questions about the crate, feel free to comment here.


prisma query not returning all type properties

Describe the bug
prisma queries are omitting fields
I'm trying to query for a user
const user = await ctx.db.query.user({
   where: { email }
});

prisma gives me back a user object but it doesn't have the permissions property on it so it's throwing an error.
Error: Cannot return null for non-nullable field User.permissions.
My mutation expects for a User type to be returned
signin(email: String!, password: String!): User!
and my type looks like the following
type User {
  id: ID!
  name: String!
  email: String!
  password: String!
  resetToken: String
  resetTokenExpiry: String
  store: Store
  permissions: [Permission!]!
}

The object prisma returns to me looks like this
{ id: '5cedfc7602743900070ba914',
  name: 'test ',
  email<EMAIL_ADDRESS>  password: 'lsjfdslfj',
  resetToken: null,
  resetTokenExpiry: null }

Expected behavior
I'd expect prisma to return me an object w/ all the properties described on the User type.

@pantharshit00 Passing the info object actually causes even less properties to be returned on the user object. For example, password field is missing so can't do any validation. I'll look into using prisma client tho.

@pantharshit00 Is there an example of how to set this up?

Ok, I was assuming that you wanted to return the data from the resolver. If you pass the info it guarantees that we are not overfetching.
In order to fetch all the field that you need, you will need to pass a custom info object.
const user = await ctx.db.query.user(
  {
    where: { email }
  },
  `
	{ id name  permission { id } }
`
);

Thanks!


KIT - create architecture documentation with ARC42

[x] General documentation structure in the KIT @SujitMBRDI
[ ] Content @maximilianong

Reference from Kits repo - https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/pull/684


Fix syncronous commands bug

coverage: 98.834% (-0.04%) from 98.877%
when pulling d7dba1f3dec0b2a8b3ca6a5e993c1845499dba23 on jeromekelleher:fix-dexplode-part-bug
into 6e87b272b0cc28c9b6451f1b5b6349cce35644e5 on sgkit-dev:main.

coverage: 98.877%. remained the same
when pulling d7dba1f3dec0b2a8b3ca6a5e993c1845499dba23 on jeromekelleher:fix-dexplode-part-bug
into 6e87b272b0cc28c9b6451f1b5b6349cce35644e5 on sgkit-dev:main.


Added icons to the right-click context menu in file view

Should appear like this...

I'll file a follow-up for additional icons.


"struggling" LaTeX warnings?

Hi - I'm getting into the final editing and formatting stages, and thought I would ask
about a LaTeX warning I've been getting:   Is this anything I should take action
about?  Rerender some figures with different software or ???
The QuatRot*.eps figures are screen shots from a piece of interactive graphics
software, and my iMac grabs them initially as .png, the default software to open
it is Preview, and then I save it as a .pdf, and run ps2pdf to get the .eps (I am
using TeXShop "TeX plus dvi", which needs all .eps graphics).  "convert" will
also do pdf->eps I think, but I have been using ps2pdf.   I have little knowledge
of my options for pdf->eps if I should be using some other application to make
life easier for you at VTeX for these images of mine.   Advice and suggestions
welcome.
Thanks, Andy
...
...
</usr/local/texlive/2017/texmf-dist/fonts/type1/public/fira/FiraSans-Light.pfb>
</usr/local/texlive/2017/texmf-dist/fonts/type1/public/mathabx-type1/matha9.pfb>
</usr/local/texlive/2017/texmf-dist/fonts/type1/public/mathabx-type1/matha7.pfb>
[0<./00CoverImages/Elsevier-Visualizing-More-Quaternions-2.eps>] [1] [2] [3]
[4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15
<./img/480px-CalabiYau5.eps>] [16] [1] [2] [3] [4] [5<./img/Hamilton.eps>]
[6<./img/AJH-on-BroomeBridge.eps>] [7] [8] [9] [10] [11] [12] [13] [14] [15]
[16] [17] [18] [19] [20] [21<./imgKlein/imgA5-1.eps><./imgKlein/imgD6-1.eps>
<./imgKlein/imgTet-1.eps><./imgKlein/imgOcta-1.eps><./imgKlein/imgIco-1.eps>]
[22<./imgKlein/KleinIJKS2.eps><./imgKlein/KleinS2.eps>] [23] [24] [25
<./imgKlein/S2XToxyPlane1.eps><./imgKlein/S2YToxyPlane1.eps>
<./imgKlein/S2ZToxyPlane1.eps><./imgKlein/S23DToxyPlane1.eps>] [26] [27
<./imgDual/cliffRfl.eps><./imgDual/cliffRotWangle.eps>] [28] [29
<./imgKlein/SimpleS3Triple.eps>] [30] [31] [32] [33] [34] [35
<./img2/S1hemiTripleN.eps><./img2/S1hemiTripleEq.eps>
<./img2/S1hemiTripleS.eps><./img2/S1hemiTripleEqBand.eps>] [36] [37] [38
<./img2/S1Density1.eps>] [39] [40<./imgBasics/S2hemispheres.eps>
<./imgBasics/S2vis.eps><./imgBasics/S2proj.eps>] [41<./img2/arctanDx.eps>]
[42] [43<./img2/S2Density1a.eps>] [44<./img2/S2Density1b.eps>
<./img2/S2Density1c.eps>] [45<./img2/out3DShells.eps>] [46] [47
<./img2/QuatRot1.eps>
/Library/TeX/texbin/dvips:  expected to see %%EndBinary at end of data; struggling on
<./img2/QuatRot2.eps>
/Library/TeX/texbin/dvips:  expected to see %%EndBinary at end of data; struggling on
] [48<./img2/QuatRot3.eps>
/Library/TeX/texbin/dvips:  expected to see %%EndBinary at end of data; struggling on
<./img2/QuatRot4.eps>
/Library/TeX/texbin/dvips:  expected to see %%EndBinary at end of data; struggling on
] [49] [50<./imgBF/S3south.eps><./imgBF/S3eqtr.eps><./imgBF/S3Vis.eps>] [51]
[52<./imgKlein/SimpleS3Triple.eps>] [53<./imgKlein/WXYS3Triple.eps>] [54
<./imgKlein/IcosaQuatGroup120-v1.eps>] [55<./imgKlein/S3TripleRandom.eps>]
[56<./imgKlein/fig3DFrmRefVisCh.eps>] [57] [58<./imgBasics/rollingball3D.eps>]
[59] [60<./imgBasics/SpinAction.eps>] [61<./imgBasics/rollingball4D.eps>]
[62] [63] [64] [65] [66<./img2/TheNSpheres.eps>] [67] [68
...
...

Hi,
These "struggling" warnings are from dvips, not LaTeX.
If the pdf output is ok, then you should do nothing.
Alternatively you might want to fix "faulty" EPS files with ps2eps or some similar utility.
Or, a better way,  convert PNG files into EPS with pngtopnm file.png | pnmtops > file.eps.


Eliminate Type-Level Distinction of Static and Dynamic

I think this may be able to be handled at the value level instead. Roughly, here's the idea. We have three kinds of tokens:

Static: read, ignore
Dynamic: deallocate
Neutral: allocate, modify

There's some kind of lattice thing going on (or maybe it's a partial order) where neutral can be merged with either of the other token types, assuming their type. The dynamically and statically would scoped the computation introducing the appropriate token type.
The reason this is appealing to me is that library authors will already have to explicitly deal with tokens somewhat often. However, it turns out there are a number of definable functions that work in a static or dynamic context. I'll need to think about the soundness of this more.

Let's give this a try:
data Mode = Static | Dynamic
data Token :: Type
data Action :: Mode -> Type

action :: Token ->. Action m ->. Action m

-- Dynamic actions
allocate :: Object a =>. Action Dynamic ->. (Action Dynamic, Reference a)
deallocate :: Object a => Reference a ->. Action Dynamic ->. (Action Dynamic, Reference a)

-- Static Actions
read :: Object a => Reference a ->. Action Static ->. (Action Static, a)
ignore :: Reference a ->. Action Static ->. Action Static

-- Scoping Computations
statically_ :: Object a => Reference a ->. (a ->. Action Static ->. Action Static) -> Reference a
dynamically_ :: Object a => Reference a ->. (a ->. Action Dynamic ->. Action Dynamic) -> Reference a

Under this scheme, we can actually nest a static/dynamic computation directly under a computation of the same type. I don't think this introduces unsoundness.
What's cool about this is that I think we can still write functions like map and cons that operate on lists without mentioning tokens in the type signatures. But is it sound?...

I have dynamically_ wrong. It should be:
dynamically_ :: Object a => Reference a ->. (a ->. Action Dynamic ->. (Action Dynamic,a)) ->. Action Static ->. Action Static

It needs to be this way since we want to preserve replace the payload and then immidiately discard the reference. But what about the more simple:
dynamically_ :: Object a => Reference a ->. (a ->. Action Dynamic ->. (Action Dynamic,a)) ->. Reference a

Does this work? To recover the behavior of the one suggested above, one could combine this with read.

Hmmm... The definition of dynamically_ now implies that we can only allocate if we already have a reference in scope. But how do we get the very first reference?

Maybe the top-level continuation-accepting function would be:
run :: (Reference () ->. Unrestricted b) ->. Unrestricted b

The type of this feels a little unnatural though.

Even better would be:
run :: (Action Dynamic ->. (Action Dynamic,Unrestricted a)) ->. Unrestricted a

This is basically like dynamically except that it is missing the reference/payload component. It makes sense that we have to start in a dynamic context. If we started in a static context, there would be nothing to do.

I thought we would need to start in a neutral context?

Starting in a neutral context does not work. Starting with only a Token, there is no way to create a Reference.

Static: read, ignore
Dynamic: deallocate
Neutral: allocate, modify
am i interpreting this incorrectly?

In the type signature for allocate (the one in the code block above has an unintended omission), I changed my mind on that:
allocate :: forall a. Object a
  =>  a
  ->. Action 'Dynamic
  ->. (Action 'Dynamic, Reference a)

If allocate could run in a neutral context, then you could allocate something in a static context and then ignore the reference. This would leak memory.

okay

This was completed in 770ad31bc42c5382f74a71f194f1b5c062e968fe.

Dang. This is not sound. With statically_, we can throw away arbitrary references.

rip happiness

I have reverted back to the old approach with a force push to master. I cannot figure out a way to do this without pushing a static/dynamic distinction to into the types. This is unfortunate because the types could be much pretty. However, I am growing more confident that this somewhat cumbersome system is actually sound.

happiness = fleeting


[Endpoint Bug] - Meshmodel Browser Endpoints Sorting

Current Behavior

For attribute apiVersion in case of components and relationships the endpoint returns null.

For nested attributes, the endpoints does not sorts the result. For example, in case of metadata attribute we are displaying catergory name and model name but the data cannot be sorted. The attribute metadata is sorted correctly.

Expected Behavior

The data should be sorted on every attribute. Most importantly, for the following attributes that we are displaying on the meshmodel browser:
For Components:

Kind
Api Version
Sub category inside Metadata
Model inside Metadata
Registrar (soon to be incorporated)

For Models:

Name
Version
Category Name inside Metadata

For Relationships:

KInd
Api Version
Model inside Metadata

Screenshots/Logs

Environment

Host OS: Mac Linux Windows
Platform: Docker or Kubernetes
Meshery Server Version: stable-v
Meshery Client Version: stable-v

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

The notion that asc and desc are appended without sort= or sortby= seems wrong, @UsmanDev09. This has me scratching my head.

Hmm. https://github.com/meshery/meshery/pull/8466#pullrequestreview-1578948014

You are right :+1:


Don't crash on CIM classes with no superclass

PR Summary
Fix #982 by checking for null on superclass property.
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an x between the square brackets. Please mark anything not applicable to this PR NA.

[x] PR has a meaningful title

[x] Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[ ] User facing documentation needed
[x] Change is not breaking
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed
[x] This PR is ready to merge and is not work in progress

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready

Bergmeister's PR https://github.com/PowerShell/PSScriptAnalyzer/pull/985 addresses same issue, I am agnostic about which one to take. Would be nice to fix though...

One PR build got stuck, which is an AppVeyor problem, therefore I triggered another build.
My PR is still WIP because I also wanted to remove the empty catch block, which then caused test failures, therefore, I think it is OK to take your PR with the minimal changes for fixing the NullReferenceException. I think we should add a test case for the bug that this PR fixes before merging the PR despite the fix being trivial.

I think the error in the AppVeyor WMF4 build could actually due to the recent breaking change with TLS 1.2 here: https://github.com/dotnet/announcements/issues/77

OK, added a test case.

@JamesWTruher @bergmeister can we merge this now?

Sorry, I will review this the next days (I want to test that that the added test would actually fail) but it looks OK otherwise.

Added -ErrorAction Stop - the additional try/catch/should check isn't needed as far as I can see - Pester fails the test because a terminating error occurs.
Changed the test data to be inline, but TBH I don't really think it's an improvement.

@JamesWTruher wondered if [path.io]::combine("testdrive:", ...) would do the right thing on linux. I tried it, and I believe it does, but changed to Join-Path anyway. Also, turns out this rule basically doesn';t work on linux anyway because DscClassCache.Initialize() throws and the rest of the rule doesn't do anything. So I marked the test to be skipped on linux and mac like the others in this file.

@JamesWTruher if you're ok with this please go ahead & merge (FYI the main reason I care about this is that PowerShell Gallery script scanning process hits this exception fairly frequently and I want to cut the noise).

@edyoung Since you have addressed @JamesWTruher and my comment about adding a test, I think it is OK to merge it in since the implementation has already been approved.


Personal/rotodd/enable pretty formatting

Description

Enables clients to request pretty-printed resources using the _pretty parameter as described in the spec
Adds GetIsPretty extension method which pulls the _pretty parameter value from the request query string
Adds indentation to the response if GetIsPretty returns true

Related issues
Addresses [69450].
Testing

Adds new Unit tests to ensure GetIsPretty extension method returns expected values

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: rotodd sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Failed to kill Runner: rpc error: code = Unavailable desc = connection error: desc

I am experiencing some issues which I cannot seem to resolve. I am constantly getting this error message and upon further inspection of logs/gauge.log, I can view the logs however it does not provide a stack trace. I'm hoping someone can shed some light on this matter. I will provide the console output as well as the log output. This is very difficult to debug as there is absolutely no stack trace. I don't see the stack trace in either the console or the log file.
Versions
Python Version: Python 3.7.0
Gauge version: 1.1.7
Commit Hash: 5d86b72
Plugins
flash (0.0.2)
html-report (4.0.12)
python (0.3.14)
reportserver (0.3.0)
screenshot (0.0.1)
spectacle (0.1.4)
xml-report (0.2.3)
Requirements.txt:
Appium-Python-Client==1.0.2
beautifulsoup4==4.9.1
browsermob-proxy==0.8.0
boto3==1.16.14
debugpy==1.2.1
decorator==4.4.2
getgauge==0.3.14
google==3.0.0
gTTs==2.2.1
psutil==5.8.0
python-vlc==3.0.11115
requests==2.24.0
requests-oauthlib==1.3.0
selenium==3.141.0
selenium-page-factory==2.1
tcp-latency==0.0.10
paramiko==2.7.2
fabric==2.6.0
CONSOLE OUTPUT
Executing Command: gauge run --install-plugins --verbose --log-level debug --env "default" --tags "about_page" --dir="." --fail-safe specs
gauge run specs
install-plugins : [true]
log-level : [debug]
tags : [about_page]
Plugin reportserver is already installed.
Parsing started.
Started concepts parsing.
172 specifications parsing completed.
Applying tags filter: about
The following specifications satisfy filter criteria:
specs/projects/web/test/about/about.spec
Parsing completed.
Checking updates...
Downloading https://downloads.gauge.org/plugin/flash?l=python&p=flash,html-report,python,reportserver,screenshot,spectacle,xml-report&o=darwin&a=amd64
Downloading https://downloads.gauge.org/plugin/html-report?l=python&p=flash,html-report,python,reportserver,screenshot,spectacle,xml-report&o=darwin&a=amd64
Downloading https://downloads.gauge.org/plugin/python?l=python&p=flash,html-report,python,reportserver,screenshot,spectacle,xml-report&o=darwin&a=amd64
Downloading https://downloads.gauge.org/plugin/reportserver?l=python&p=flash,html-report,python,reportserver,screenshot,spectacle,xml-report&o=darwin&a=amd64
Downloading https://downloads.gauge.org/plugin/screenshot?l=python&p=flash,html-report,python,reportserver,screenshot,spectacle,xml-report&o=darwin&a=amd64
Downloading https://downloads.gauge.org/plugin/spectacle?l=python&p=flash,html-report,python,reportserver,screenshot,spectacle,xml-report&o=darwin&a=amd64
Downloading https://downloads.gauge.org/plugin/xml-report?l=python&p=flash,html-report,python,reportserver,screenshot,spectacle,xml-report&o=darwin&a=amd64
You are using pip version 10.0.1, however version 21.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Python: 3.7.0
Loading step implementations from /Users/testuser/Development/test/app/step_impl dirs.
Starting grpc server..
Attempting to connect to grpc server at port: 60022
Successfully made the connection with runner with port: 60022
Validation started.
Validation completed.
Successfully made the connection with plugin with port: 60043
Initialising suite data store.
Error occurred while waiting for runner process to finish.
Error : exit status 1
Error Message: transport is closing
Stacktrace:
Error Message: Runner is not Alive
Stacktrace:
Transformed SuiteResult to report structure
Successfully generated html-report to => /Users/testuser/Development/test/app/reports/html-report/index.html
Done generating HTML report using theme from /Users/testuser/.gauge/plugins/html-report/4.0.12/themes/default
Successfully generated xml-report to => /Users/testuser/Development/test/app/reports/xml-report
Origin report directory is ' /Users/testuser/Development/test/app/reports/html-report'
renaming index file to 'report.html'
Archive destination is ' /Users/testuser/Development/test/app/reports/html-report.zip'
removing archive '/Users/testuser/Development/test/app/reports/html-report.zip'
Origin report directory is ' /Users/testuser/Development/test/app/app/reports/html-report'
Archive destination is ' /Users/testuser/Development/test/app/reports/html-report.zip'
baseDir => 'app'
environment => 'default'
reportPath => ''
Could not find 'REPORTSERVER_HOST', setting to default 'http://localhost:8000'.
reportserverurl => 'http://localhost:8000/app/default'
Archive destination is ' /Users/testuser/Development/test/app/reports/html-report.zip'
Archive destination is '/Users/testuser/Development/test/app/reports/html-report.zip'
Could not send the archive from '/Users/testuser/Development/test/app/reports/html-report.zip' to 'http://localhost:8000/app/default'
Post http://localhost:8000/app/default: dial tcp [::1]:8000: connect: connection refused
Sending kill message to Flash plugin.

Archive destination is ' /Users/testuser/Development/test/app/reports/html-report.zip'
removing archive ' /Users/testuser/Development/test/app/reports/html-report.zip'
Origin report directory is ' /Users/testuser/Development/test/app/reports/html-report'
Failed to kill Runner: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:60022: connect: connection refused"
renaming index file to 'index.html'
Specifications: 0 executed 0 passed 0 failed 0 skipped
Scenarios: 0 executed 0 passed 0 failed 0 skipped
Total time taken: 495ms
Terminating Automation Successfully
Terminated Stopwatch: [2021-03-10 | 21:33:06]
Overall Elapsed Time: "0:00:26.988521"
Waiting for logs to generate..
All processes completed
LOG OUTPUT:
10-03-2021 21:32:48.071 [python] [ERROR] You are using pip version 10.0.1, however version 21.0.1 is available.
10-03-2021 21:32:48.071 [python] [ERROR] You should consider upgrading via the 'pip install --upgrade pip' command.
10-03-2021 21:32:48.871 [python] [INFO] Python: 3.7.0
10-03-2021 21:32:48.871 [python] [DEBUG] Loading step implementations from /Users/testuser/Development/test/app/step_impl dirs.
10-03-2021 21:33:03.996 [python] [DEBUG] Starting grpc server..
10-03-2021 21:33:04.002 [Gauge] [DEBUG] Attempting to connect to grpc server at port: 60022
10-03-2021 21:33:04.004 [Gauge] [DEBUG] Successfully made the connection with runner with port: 60022
10-03-2021 21:33:04.004 [Gauge] [DEBUG] Validation started.
10-03-2021 21:33:04.008 [Gauge] [DEBUG] Validation completed.
10-03-2021 21:33:04.010 [Gauge] [DEBUG] Run started
10-03-2021 21:33:04.018 [Gauge] [DEBUG] Starting Html Report plugin
10-03-2021 21:33:04.112 [Gauge] [DEBUG] Attempting to connect to grpc server at port: 60027
10-03-2021 21:33:04.114 [Gauge] [DEBUG] Successfully made the connection with plugin with port: 60027
10-03-2021 21:33:04.115 [Gauge] [DEBUG] Starting Xml Report plugin
10-03-2021 21:33:04.190 [Gauge] [DEBUG] Attempting to connect to grpc server at port: 60032
10-03-2021 21:33:04.197 [Gauge] [DEBUG] Successfully made the connection with plugin with port: 60032
10-03-2021 21:33:04.205 [Gauge] [DEBUG] Starting Flash plugin
10-03-2021 21:33:04.349 [flash] [INFO] [Flash] Starting progress reporting at http://<IP_ADDRESS>:60037
10-03-2021 21:33:04.351 [Gauge] [DEBUG] Attempting to connect to grpc server at port: 60038
10-03-2021 21:33:04.354 [Gauge] [DEBUG] Successfully made the connection with plugin with port: 60038
10-03-2021 21:33:04.356 [Gauge] [DEBUG] Starting Report Server plugin
10-03-2021 21:33:04.428 [Gauge] [DEBUG] Attempting to connect to grpc server at port: 60043
10-03-2021 21:33:04.434 [Gauge] [DEBUG] Successfully made the connection with plugin with port: 60043
10-03-2021 21:33:04.434 [Gauge] [DEBUG] Initialising suite data store.
10-03-2021 21:33:04.479 [python] [CRITICAL] Exception occurred while loading step implementations from file: step_impl/global.py.
10-03-2021 21:33:04.496 [Gauge] [ERROR] Error occurred while waiting for runner process to finish.
Error : exit status 1
10-03-2021 21:33:04.506 [Gauge] [ERROR] Error Message: transport is closing
10-03-2021 21:33:04.506 [Gauge] [ERROR] Stacktrace:
10-03-2021 21:33:04.506 [Gauge] [ERROR] Error Message: Runner is not Alive
10-03-2021 21:33:04.506 [Gauge] [ERROR] Stacktrace:
10-03-2021 21:33:04.507 [html-report] [DEBUG] Transformed SuiteResult to report structure
10-03-2021 21:33:04.660 [html-report] [INFO] Successfully generated html-report to =>/Users/testuser/Development/test/app/reports/html-report/index.html
10-03-2021 21:33:04.660 [html-report] [DEBUG] Done generating HTML report using theme from /Users/armonds/.gauge/plugins/html-report/4.0.12/themes/default
10-03-2021 21:33:04.663 [xml-report] [INFO] Successfully generated xml-report to => /Users/testuser/Development/test/app/reports/xml-report
10-03-2021 21:33:05.670 [reportserver] [DEBUG] Origin report directory is '/Users/testuser/Development/test/app/reports/html-report'
10-03-2021 21:33:05.675 [reportserver] [DEBUG] renaming index file to 'report.html'
10-03-2021 21:33:05.675 [reportserver] [DEBUG] Archive destination is '/Users/testuser/Development/test/app/reports/html-report.zip'
10-03-2021 21:33:05.675 [reportserver] [DEBUG] removing archive '/Users/testuser/Development/test/app/reports/html-report.zip'
10-03-2021 21:33:05.675 [reportserver] [DEBUG] Origin report directory is '/Users/testuser/Development/test/app/reports/html-report'
10-03-2021 21:33:05.676 [reportserver] [DEBUG] Archive destination is '/Users/testuser/Development/test/app/reports/html-report.zip'
10-03-2021 21:33:06.599 [reportserver] [DEBUG] baseDir => 'app'
10-03-2021 21:33:06.599 [reportserver] [DEBUG] environment => 'default'
10-03-2021 21:33:06.599 [reportserver] [DEBUG] reportPath => ''
10-03-2021 21:33:06.599 [reportserver] [DEBUG] Could not find 'REPORTSERVER_HOST', setting to default 'http://localhost:8000'.
10-03-2021 21:33:06.599 [reportserver] [DEBUG] reportserverurl => 'http://localhost:8000/app/default'
10-03-2021 21:33:06.599 [reportserver] [DEBUG] Archive destination is '/Users/testuser/Development/test/app/reports/html-report.zip'
10-03-2021 21:33:06.615 [reportserver] [DEBUG] Archive destination is '/Users/testuser/Development/test/app/reports/html-report.zip'
10-03-2021 21:33:06.615 [reportserver] [INFO] Could not send the archive from '/Users/testuser/Development/test/app/reports/html-report.zip' to 'http://localhost:8000/app/default'
Post http://localhost:8000/app/default: dial tcp [::1]:8000: connect: connection refused
10-03-2021 21:33:06.615 [Gauge] [DEBUG] Sending kill message to Flash plugin.
10-03-2021 21:33:06.615 [Gauge] [DEBUG] Sending kill message to Report Server plugin.
10-03-2021 21:33:06.615 [Gauge] [DEBUG] Sending kill message to Html Report plugin.
10-03-2021 21:33:06.615 [Gauge] [DEBUG] Sending kill message to Xml Report plugin.
10-03-2021 21:33:06.616 [reportserver] [DEBUG] Archive destination is '//Users/testuser/Development/test/app/reports/html-report.zip'
10-03-2021 21:33:06.616 [reportserver] [DEBUG] removing archive '/Users/testuser/Development/test/app/reports/html-report.zip'
10-03-2021 21:33:06.637 [Gauge] [ERROR] Failed to kill Runner: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:60022: connect: connection refused"
10-03-2021 21:33:06.637 [reportserver] [DEBUG] Origin report directory is '/Users/testuser/Development/test/app/reports/html-report'
10-03-2021 21:33:06.637 [reportserver] [DEBUG] renaming index file to 'index.html'
10-03-2021 21:33:06.637 [Gauge] [INFO] Specifications: 0 executed 0 passed 0 failed 0 skipped
10-03-2021 21:33:06.637 [Gauge] [INFO] Scenarios: 0 executed 0 passed 0 failed 0 skipped
10-03-2021 21:33:06.637 [Gauge] [INFO]
Total time taken: 495ms

hi @asarkisian - I notice this line:
[CRITICAL] Exception occurred while loading step implementations from file: step_impl/global.py.

Which tells me that the gauge-python runner is unable to load this file due to some error, and this has caused gauge-python runner to crash. The error could be due to multiple possible reasons (ex either due to a missed requirement, or an unsupported python version).
There is an open issue that talks about improving the error reporting.

@sriv I have tried to use pyenv and downgraded my python ver to 3.8.0 and even lower than that all the way down to 3.7.0. It still doesn't work as expected. Is it possible I can send you a sample project so you can see on your end?

@sriv
I posted in a nother thread but here it is again:
Hi @sriv Absolutely. I removed all confidential content and only put in generic sample tests.
Repo: https://github.com/asarkisian/gauge_test_app
Here is some info on my system:
OS: Mac Catalina 10.15.7
Python3 Ver: 3.9.2
Python3 Path: /usr/bin/python3, /usr/local/bin/python3
Gauge version: 1.1.7
Plugins
html-report (4.0.12)
python (0.3.14)
screenshot (0.0.1)
OUTPUT:
`➜ test_app git:(master) gauge run specs
Python: 3.9.2
Error occurred while waiting for runner process to finish.
Error : exit status 1
Error Message: transport is closing
Stacktrace:
Error Message: Runner is not Alive
Stacktrace:
Successfully generated html-report to => /Users/armondsarkisian/Desktop/test_project/test_app/reports/html-report/index.html
Failed to kill Runner: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:51812: connect: connection refused"`
Log Output:
Screen Shot 2021-03-17 at 8 40 14 AM

@asarkisian - thanks for the sample, it helped troubleshoot.
There are two aspects to this problem:

gauge-python does not log the stacktrace indicating the real cause of the failure, and hence you see a generic and unhelpful error message. This is reported in getgauge/gauge-python#228. I've raised a PR (getgauge/gauge-python#230) to fix this.

when I use the changes included above and run your sample, here's what I see in the gauge.log:

18-03-2021 07:54:10.937 [python] [CRITICAL] Exception occurred while loading step implementations from file: step_impl/global.py.
Traceback (most recent call last):
  File "/home/steam/.local/lib/python3.8/site-packages/getgauge/impl_loader.py", line 65, in _import_file
    m = importlib.import_module(module_name)
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 783, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmp/gauge_test_app/step_impl/global.py", line 25, in <module>
    from framework import Framework
ImportError: cannot import name 'Framework' from 'framework' (/tmp/gauge_test_app/framework/__init__.py)
18-03-2021 07:54:10.939 [Gauge] [ERROR] Error occurred while waiting for runner process to finish.
Error : exit status 1

It seems that the project is unable to load because of an error when importing framework. I am not familiar with your setup, but it looks like some dependencies are missing from requirements.txt and hence not available to your framework. ex:

reporting.py has import vlc, but python-vlc is missing in requirements.txt
requests.py has from requests_oauthlib import OAuth1 but requests-oauthlib is missing in requirements.txt

There could be more, and I am not sure if these dependencies are somehow made available automatically in your environments.
Perhaps, once gauge-python 0.3.15 is out, you can run it and see the error in your system (alternatively, you could install gauge-python from source from https://github.com/getgauge/gauge-python/tree/228_log_impl_error).

Thanks for the update @sriv . I will wait for gauge-python 0.3.15 to be out. In the meantime, I will keep searching for the cause. It's especially difficult when the stack trace is blank

gauge-python 0.3.15 is released - https://github.com/getgauge/gauge-python/releases/tag/v0.3.15
It will take a few hours for the cache to get refreshed and then you can do a gauge install python to get the latest version. In the meanwhile you can download the zip file from the releases page and run gauge install python -f <path_to_zip>


WonderCMS 3.0.7  error permission denied

Using php 7.3.17 and trying to access index.php but error obtained is
 [error] 3717#3717: *32 FastCGI sent in stderr: "PHP message: PHP Warning:  mkdir(): Permission denied in /var/www/localhost/htdocs/wondercms/index.php on line 340PHP message: PHP Fatal error:  Uncaught Exception: Could not create data folder. in /var/www/localhost/htdocs/wondercms/index.php:341
Permssion is set to 0755 on the directory, Anyone else facing this error?

@kkarthik23, just to verify, do all files have the 0644 permissions, including the index.php and all folders 0755?
If the answer is yes, I believe the next solution would be by editing your /etc/init.d/php-fcgi and changing
PHPUSER=php
PHPUSER=nginx
as explained here: https://stackoverflow.com/questions/13101820/nginx-php-fastcgi-unable-to-write-permission-denied-even-using-his-own-permiss

thanks for the quick response
i did follow the above instructions and i tried
$find /var/www/html -type d -exec chmod 755 {} \;
$find /var/www/html -type f -exec chmod 644 {} \;

which should have worked but  still didn't help and then i tried chmod -R 0777  /var/www/html which finally worked this may not be the most secure option but for now it works  hope it helps someone

@kkarthik23 no problem at all 👍
The stackoverflow solution seems better though, setting the correct user for PHP user (and restarting), which would avoid using the 777 permissions.
Would you be willing to try that out so we get more clarity on the issue?

@kkarthik23 no problem at all 👍
The stackoverflow solution seems better though, setting the correct user for PHP user (and restarting), which would avoid using the 777 permissions.
Would you be willing to try that out so we get more clarity on the issue?

Sorry if i was not clear in my previous comment, i did try the stack overflow option and i had to set user and group as nginx as well as the file permissions and finally had to use chmod -R 0777 /var/www/html  to get it to work  i am not using php-fcgi and using php-fpm

@kkarthik23 thanks for the clarification. It does seem odd that you had to set everything to 777, which doesn't seem like the best idea.
Did you have any successful results in setting the permissions only to the index.php or trying to understand what file/folder was actually at fault?

Closing due to inactivity, please feel free to continue commenting or re-open this issue.

Yes sir, i am continuing commenting. I set chmod -R 777 data, on data folder but i got same error 'Uncaught Exception: Could write to data folder'. Then i did  this:  I have  edit function checkFolder at line 339 that frowing error, i add in it  'echo $folder' to
show me what folder is a problem. It show me  'themes' folder. Is it really necessary to write to themes folder??

Oh sorry, its necessary. Due to ability to install new themes. Thank you!

@iicuken most welcome, glad this was solved!


Context menu to toggle fixed width only displays when terminal is in editor area

Testing #133550
When the terminal is in the panel, the context menu to toggle fixed width is not displayed:

The keyboard shortcut Alt-Z works though (sometimes anyway).
Once I move the terminal into the editor area, the context menu command is displayed:

good catch - missed that in the single terminal tab context menu. you'll see it in the tab context menu if you have more than one terminal


Wrong section reference

There is no "Section 7" in the Microsoft Publisher Agreement.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 42d0270d-7734-62c8-8373-bf675b3bfe1e
Version Independent ID: 9aab8950-ada1-8cf9-2d61-7475709655fd
Content: Delete Marketplace Offers - Azure Marketplace
Content Source: articles/marketplace/cloud-partner-portal/manage-offers/cpp-delete-offer.md
Service: marketplace
GitHub Login: @v-miclar
Microsoft Alias: pbutlerm

@Benjiiim Thank you for your query . We will investigate and update the thread further.

#please-close
This is a repeat of issue #27699.

@Benjiiim We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

@v-miclar actually, this is not a duplicate, even if the two issues are similar.

#please-close
It does have a section 7:  "7. WARRANTIES. You represent, warrant and undertake to Microsoft that: "  although termination policies are also mentioned in other sections.

Indeed, there is a section 7, my bad. However, it doesn't seem to be the right and only section to point to regarding termination. Removing "(Section 7) " from the doc might be less confusing from my perspective.

#please-close
Agreed, has been removed.


portuguese language support

language support with #8 in mind, using portuguese as an example

Obrigado, @JarbasAI - this is excellent, thank you for putting this together.
There are some minor style modificiations I'd like to make to this - capitalizations and phrasing and such, however I'm going to merge it first and then make the style changes in WordPress - the integration plugin we have running will then push any edits I make in WordPress back here in GitHub.
Again, a huge thank you for your contribution.


Examples

Adding some examples would be helpful (even without doc)

Hello,
I'm planning to add some examples in the repository.
For now, here is a working example.
import { MediaDevicesShim, VideoRoomBuilder, WebRTCShim } from 'janus-gateway-tsdx'

// Media constraints documentation here:
// https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamConstraints
// https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackConstraints
const MEDIA_CONSTRAINTS = {
  audio: { autoGainControl: true, echoCancellation: true, noiseSuppression: true },
  video: { width: { ideal: 1280 }, height: { ideal: 720 } },
}

let room = new VideoRoomBuilder('wss://webrtc.janus.test/ws', MEDIA_CONSTRAINTS, new MediaDevicesShim(), new WebRTCShim())
      .onLocalVideo(stream => console.log('Local video:', stream))
      .onRemoteVideo(event => console.log('Remote video:', event))
      .onUnpublished((feeId) => console.log('Unpublished:', feeId))
      .onLeaving((feeId) => console.log('Unpublished:', feeId))
      .join(room, user.username)
      .then(room => console.log(room))

Hi, @smyrgeorge Do you have any example for streaming plugin?

Hello @osv, right now i don't have.
For now I just use the VideoRoom plugin.
In the near future maybe I'll write some example.


syz-fuzzer, pkg/repro: fault injection stacks lead to corrupted reports

Fault injection prints lots of stack traces, frequently this leads to corrupted reports. Some we filter out, some are not. This is especially harmful for repro, because sometimes final reports are corrupted even though we try several times.
Perhaps we could run only 1 test process when doing fault injection. But it's unclear what to do with repro because we try 1 process too, but presumably these crashes do not reproduce with 1 process (?).

We don't need this if we do #600


cpp-package OpWrapperGenerator.py exists some bug?

recently i try to use cpp version to write some code
code :
int main(){
    auto x = Symbol::Variable("x");
    auto y = topk(x);
}

but got following error :
Symbol.ComposeKeyword argument name src not found.
Candidate arguments:
	[0]data

i look into "op.h" in "cpp-package/include/mxnet-cpp"
return Operator("topk")
           .SetParam("axis", axis)
           .SetParam("k", k)
           .SetParam("ret_typ", TopkRetTypValues[int(ret_typ)])
           .SetParam("is_ascend", is_ascend)
           .SetInput("src", src)
           .CreateSymbol();

and i modified my code to:
int main(){
   auto x = Symbol::Variable("x");
   auto y= Operator("topk")
           .SetParam("axis", 0)
           .SetParam("k", 1)
           .SetParam("ret_typ", "value")
           .SetParam("is_ascend", false)
           .SetInput("data", x)                                    // change "src" to "data"
           .CreateSymbol("symbol_topk");

}

and it works
it seems "op.h" is generate by  "OpWrapperGenerator.py", but there are some bug existed

@lx75249

@piiswrong To fully fix this bug, it will be a big patch. All ops that forget to set FListInputNames properly suffer from this problem, because the default implementation of FListInputNames is return {"data"}. The basic idea of the patch is to separate parameters from inputs in op arguments. (add_arguments() to add_input(), add_arguments() to add_params()). In this way, we don't need set_num_inputs() and FListInputNames any more. What's your opinon?

its probably better to change src to data in add argument

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!


exit on network failures only

What type of PR is this?

What does this do?

Which issue(s) does this PR fix/relate to?

Related Issue #
Resolves #

Have you included tests for your changes?

Did you document any new/modified feature?

Notes

@dborovcanin please review this one ASAP


file paths for file_drop need to be absolute paths

Here's a sample error message that appears:
ERROR - failed to start cyberreboot-vent-rq-worker-master because: 500 Server Error: Internal Server Error ("create ~/Documents: "~/Documents" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path")
From my logs, rq-worker-master, network-tap-master, and file-drop-master fail to start with the exact same error.


Improve edit forms

Big priority. Right now it's not very pretty. Need more intuitive and easy to use UI/UX, responsiveness etc...

For now, they are in better shape. Still could use little improvements but it is good for now


[Bug]: Searching for partial method names fails

Issue Checklist:

[X] No matching Open Bugs
[X] No matching Closed Bugs
[X] I've read the Contributing Guide
[X] I'm following the Code of Conduct

What happened?
Let's say you forget the exact name of a method, but you know the first part of it.
For example: Session.setTrackingAllowed
You'll end up with no hits that match partially in this case. Perhaps because of an exact match on the TrackingInfo object.

Which Browser(s) were you using?
Chrome
Which Operating System(s) were you using?
macOS
Steps to produce this issue.
Step 1: Type setTracking into the search field
Step 2: Press 'enter' key
Step 3: Observe that the Session class isn't a hit.

This has been resolved in v0.3.0 which is now available at https://sfccdocs.com


fix: node ignores

In Node.js 23, node:sqlite is built-in, but when using require('sqlite') alone, it should refer to the community package. Considering this scenario, all require statements starting with node: should be treated as using Node's built-in modules.
https://nodejs.org/docs/latest/api/sqlite.html

Summary by CodeRabbit

新功能

在配置中添加了对以“node:”开头的内置 Node.js 模块的忽略规则，增强了对 Node 平台的支持。

求发个版本

This solution hides problems, such as the fact that this error is not reported at compile time when require('node:foo').

And, no testcases added.


Expose call to remove Visual Linking on a viewport

The only param the UI is expecting to pass is childVpId.

case class RemoveVisualLinkRequest(childVpId: String) extends MessageBody


Include status.networkAttachments in PrinterColumns

Printing the status.networkAttachments instead of the spec part is more useful as it dumps pod IPs.

nice catch!

lgtm


fonts.fontconfig-penultimate: remove dependency on fontconfig_210

Motivation for this change
Since https://github.com/NixOS/nixpkgs/pull/93562 was merged,
configurations which set fonts.fontconfig.penultimate.enable to true
will fail to build, tripping the assertion:
fontconfig 2.10.x hasn't had a release in years, is vulnerable to CVE-2016-5384
and has only been used for old fontconfig caches.

This rectifies the module, deleting references to fontconfig_210. I just
did the most obvious thing possible to make it build, and didn't really
think properly about the consequences, so I would appreciate some review
on this one from someone who knows the fontconfig stuff a bit better.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

I wonder if we should keep penultimate at all: https://github.com/NixOS/nixpkgs/pull/92571#issuecomment-654909307

I opened https://github.com/NixOS/nixpkgs/pull/95681 removing fontconfig-pentultimate.

Ah, I didn't realise that upstream fontconfig-penultimate hasn't been updated in over 3 years. I guess what you propose makes more sense.


Docker setup for tuya-mqtt

A small contrib to add handy config files to build and run tuya-mqtt within docker a container

I'm going to close this PR for now.  I do plan to add Docker support in the future, but it will be done slightly differently (I think) and, while I may implement a status option for the script in a future version, it will not be done in the same way as what the patches from mbronk do (i.e. it will not be an option) as I just don't agree with the implementation.

Ho, sorry didn't realised that merging this in my fork's master will update this MR. I was not intending to insist on mbronk's MR at all. I should have merge it in a separate branch...
I perfectly understand your opinion about that, but I have to admit that tasmosta's implementation behave like this and is really stable for my use case, and so it seems right/logical to me that tuya-mqtt can behave the same, or at least give an opportunity for users to configure this to behave the same as tasmota.
Anyway you've got the point, I was about to ask you if you still plan to fix the status topic update bug when HA status change is detected. I'm facing lot's off instability with HA/tuya-mqtt integration by this days, and while I didn't really took the time
to troubleshoot the root cause, I did stumble on @mbronk's MR and decided to give it a try.
About the docker support, I'll be interested in your implementation plans. I can not see any big issue with my MR, dispete the lake of documentation :), comments are welcome !

No issue.  I don't really think it's a valid analog to compare Tasmota to tuya-mqtt.  For Tasmota each device maintains it's own unique connection to the broker so you can assume that if the device has an active connection it's online.  For tuya-mqtt that's simply not true, the script could absolutely have a connection to the broker while some devices are offline due to no active connection so the script has to maintain the status of each device.
I'm open to implementing a separate status, based on LWT, for the scripts connection to the broker, but that's largely useless for Home Assistant, which would still depend on the actual device status, not on the scripts connection status.  The goal of the current tuya-mqtt device level status function is to show if the tuya device is online and tuya-mqtt is able to communicate with it, it's not to show if tuya-mqtt has a connection to the broker.
I do have a fix queued up for the current failure to republish online state, it's just a single line, so no big deal, this project has simply taken a backseat lately.
And there's not much different between what I will implement and what you had from a Docker perspective, just some small code changes to look for configs in a specific mounted path when running in Docker, nothing world changing.  I just need to get the time to get these, and the handful of other fixes I have, queued up and pushed.  Hopefully in the next week.


Frontend: Graph Legend Update

Forked repo discussion
Ready for ItJustWorksTM:master ✔

Haven't had the time to review this just yet, will find some time this week hopefully.
could you maybe post some screenshots of the final product?

Haven't had the time to review this just yet, will find some time this week hopefully. could you maybe post some screenshots of the final product?

The changes are mostly regards the ColorLegend component. We create a new G6 graph as legend and display the nodes according to the config.json file.
We also relocate the legend to the top left of the window, and display the legend by default.

I have clean up the code in the layout.ts file. It seems some late changes cause some conflicts to resolve.

We resolve the conflicts and we put the legend and the button of the legend back to the original place. We will change the location of the panel in other branch. The result is shown as follow.

The only thing we are not sure is that the undefined type is called "Unknown" in the legend right now, but it is too long to display. We are suggest to change it to "Unk." for short. What's your opinion about that?

We are suggest to change it to "Unk." for short. What's your opinion about that?

Unk. is not really a common term people use I think, try making it a quesiton mark ?, or even ???; that will visually tell people what happened.

The legend looks good as shown in the pic, if we can change the orange header to a more muted color (with white text) then Im happy to include this change.

Dose this color works for you?

Not bad actually! however I think if the overarching plan is to put the legend in the left card stack it shoudnt have an eye catching header like that, it needs to be a card like the current filter panel. If the legend stays like that im happy with it.

The plan is still to have the side bar, yes.
I think the purple is a bit strange to have since there is no other element that is purple. Maybe, if orange is too flashy, we could go for the light gray that is on the buttons when hovered?
We will most likely need something consistent between panels anyway

Now the background color of legend title is set to gray.

Meant dark gray to match the rest, not light gray :see_no_evil:

Meant dark gray to match the rest, not light gray 🙈
The previous one is bg-gray-500
And bg-gray-300 is even lighter.

bg-gray-700 is more blue-ish to me.

Look here: https://daisyui.com/docs/colors/

Meant dark gray to match the rest, not light gray 🙈

The previous one is bg-gray-500 And bg-gray-300 is even lighter.
bg-gray-700 is more blue-ish to me.

Hey Renyaun, I have used bg-base-200 for the filter panel header. And, that matches perfectly the rest of the elements. I think in the version that you are working with, bg-base-100 is the best color.

We will update the colors slightly in this issue. So, I suggest that we use bg-base-100 for now.

I made the title color consistent with filter panel.

That works for me

Ready for a last review?

Ready for a last review?

Yes, let's go

Thanks!


Clean up logging.

Use logger named after module, a widely followed python convention.

So why do this anyway? One part is convention, but another is allow easier customization of log verbosity. Right now when --debug is used we pull in all kind of events all the way to boto authenticating with AWS. It can really drown out events that we directly generate. Even with this change you'll be able to grep out all asiaq log events and that'll provide a high level overview of when something went awry.

isnt there a way to set the verbosity of boto3? without changing our code base this extensively?

👍 after conflicts are resolved

@pchand-amplify yep, we already do. But we'd still not be following python logging convention. It might solve our immediate problems but if you were to use asiaq as a library you'd really have to work around the logging problems we introduced.

ok. 👍.

+:100: to this


Allow devices to access details of the snapshot running on them

Description
When working with large sets of devices, it's fair to assume that during a migration to a new snapshot that some devices will continue to run the old snapshot for longer than others.
Where the devices are collecting data from sensors and passing it to a central time series database it would be useful if the data could be tagged as originating from a given snapshot.
That would allow HMIs both on the shop-floor and in offices to understand which data was generated by a specific snapshot and where needed highlight data from an old build.

Verified staging -> device


AWS SES SERVICE INTEGRATION

Hi Team,
Is it possible to incorporate AWS SES in django-templated-email.
Note:
I already tried above scenario but i got below errors:
SAXParseException at /url
:1:0: syntax error

Hi, this is outside the scope the project, the project uses Django's built in abstractions for mailer (have a look at django-ses for SES integration).


Refine samples on README.

Codecov Report

Merging #60 (97f3019) into main (9578ffb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #60   +/-   ##
=======================================
  Coverage   75.36%   75.36%
=======================================
  Files          32       32
  Lines        5833     5833
  Branches      270      270
=======================================
  Hits         4396     4396
  Misses       1437     1437

Flag
Coverage Δ

unittests
75.36% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9578ffb...97f3019. Read the comment docs.


docs: clarify why/where proj:epsg is required

It wasn't clear that proj:epsg is required by the Projection Extension, not by the core STAC Spec.

Just needs yarn lint.


typescript: Update all non-major dependencies

This PR contains the following updates:

Package
Type
Update
Change

@types/chai (source)
devDependencies
patch
4.3.17 -> 4.3.19

@types/node (source)
devDependencies
patch
22.5.0 -> 22.5.2

@types/node (source)
dependencies
patch
22.5.0 -> 22.5.2

axios (source)
dependencies
patch
1.7.5 -> 1.7.7

gdata-vaas
dependencies
minor
7.3.1 -> 7.4.0

:warning: Warning
Some dependencies could not be looked up. Check the warning logs for more information.

Release Notes

axios/axios (axios)
v1.7.7
Compare Source
Bug Fixes

fetch: fix stream handling in Safari by fallback to using a stream reader instead of an async iterator; (#6584) (d198085)
http: fixed support for IPv6 literal strings in url (#5731) (364993f)

Contributors to this release

 Rishi556
 Dmitriy Mozgovoy

v1.7.6
Compare Source
Bug Fixes

fetch: fix content length calculation for FormData payload; (#6524) (085f568)
fetch: optimize signals composing logic; (#6582) (df9889b)

Contributors to this release

 Dmitriy Mozgovoy
 Jacques Germishuys
 kuroino721

GDATASoftwareAG/vaas (gdata-vaas)
v7.4.0
Compare Source

Configuration
:date: Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
:warning: Warning: custom changes will be lost.


Can't turn off email notifications

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

Describe the bug*
Emails notifications are still being sent after turning off "Enable email notifications".
Steps to Reproduce

Turn on "Enable email notifications"
1.5. I suppose I left email notifications on for a few days, received some email. Probably not a required step.
Turn off "Enable email notifications"
Create a PO, BO, etc. that will generate a notification.
Still get email!!

Expected behavior
Stop sending email notifications after turning off the setting.
Deployment Method

[ ] Docker
[X] Bare metal

Version Information
Version Information:
InvenTree-Version: 0.9.0 dev
Django Version: 3.2.15
Commit Hash: 0fae2432b
Commit Date: 2022-08-26
Database: mysql
Debug-Mode: True
Deployed using Docker: False
Relevant log output
No response

The user setting is never checked anywhere. Need to add check to the send_bulk function:
https://github.com/inventree/InvenTree/blob/ea60cdc6a8a7eaa5a445148f5067e5c0137c5377/InvenTree/plugin/builtin/integration/core_notifications.py#L73

It is checked a few lines above in get_targets

You're right, it should be being called through that...

Maybe something is wrong with setting the property itself, I mean update the setting value through the api.
I am trying to get email notifications live, and I have a problem with enabling/disabling settings like:
Menu item User settings / Notifications / Enable email notifications: I get 404 for URL: /api/settings/global/NOTIFICATION_METHOD_MAIL/
Menu item Plugin settings / CoreNotificationsPlugin / Enable email notifications: I get 404 for  URL: /api/settings/global/ENABLE_NOTIFICATION_EMAILS/
Bare metal install, always upgraded to recent master branch. (now b306d2a34a60c453aab57197c895ed7a64651f18)

I get similar errors for /api/settings/global/REPORT_INLINE/ and others
I don't see NOTIFICATION_METHOD_MAIL or REPORT_INLINE in the InvenTreeSetting.SETTINGS (Dict of all global settings values)
Shouldn't these be calling user settings instead of global?

Also I don't see these settings in InvenTreeUserSetting
So I think

It's calling the wrong api
Even if calling user settings api, I don't see some of the settings defined there

I'm very new to this project so entirely possible I am missing something

@rkalman thanks for pointing this out, sorry took me so long to get back around to this one. Certainly something is going wrong with the settings page / API there.

I'm not sure that the API bug is the same as what is preventing the email from being turned off, but we'll see


Uncaught (in promise) Error: Permission denied to access object

How to fix?

Browser: Firefox
User Script Manager: Tampermonkey
Web Exporter v1.1.0

Maybe you could try Nightly Build?

The results did not change.


Updating docs

This fixes #2913 :)
The pictures also needs to be changed, is there any source of these images through which it can directly change? Otherwise I will go ahead and photoshop them.

@kira0204 The sources for those images are in the Vision file in the /docs/raw directiory (I presume  - I don't have Vision handy). If you have Visio, an update would be appreciated. If not, we'll have to bug @mhils.

It's  Microsoft Visio, but other than that I agree entirely. :-)

That was actually autocorrect, Microsoft Max. ;)


Move rector code to core

Move the rector stuff from 1x to core

Well moving it will be stupid since it only has rules for the 1.x implementation on dynamic attributes (the $faker->foo to $faker->foo()).
We have to see if we can even build a rector file to migrate from 1.x to 2.x


Update grpc to 1.1.2

Closes #397

@trustin PTAL

Updated

Seems like we had various test failures:
https://travis-ci.org/line/armeria/builds/204105094#L845

Yeah it's because grpc uses guava which we shade. Trying to see whether I'm screwed or not ;)

Think I know how to fix this will try it out tomorrow.

Rebased and tests pass - @trustin PTAL


gnumeric: 1.12.48 -> 1.12.49

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gnumeric is: "The GNOME Office Spreadsheet"
meta.homepage for gnumeric is: "http://projects.gnome.org/gnumeric/"
meta.changelog for gnumeric is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.12.49 with grep in /nix/store/8jwcwhqcy89dhl9qv3wkid3id5qh20rg-gnumeric-1.12.49

directory tree listing: https://gist.github.com/80c6eff36278439378aee2e42489a269

du listing: https://gist.github.com/5e910b4cb399137198c10e674daa49da

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gnumeric

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8jwcwhqcy89dhl9qv3wkid3id5qh20rg-gnumeric-1.12.49 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gnumeric https://github.com/r-ryantm/nixpkgs/archive/ff756c92832a265541798edda1cdf87a6b3643ad.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8jwcwhqcy89dhl9qv3wkid3id5qh20rg-gnumeric-1.12.49
ls -la /nix/store/8jwcwhqcy89dhl9qv3wkid3id5qh20rg-gnumeric-1.12.49/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

gnumeric

Maintainer pings
cc @vcunat for testing.

We have had to disable the "cs" translation of the documentation 😱

... but OK, it seems likely that noone here used it.  (Even I'm using LANG=en_US.UTF-8 for simplicity.)

Yeah, en_GB.UTF-8. Though, I rarely open yelp anyway.
I have seen that error in the past. I thought we did not upgrade itstool to avoid this issue https://github.com/itstool/itstool/issues/22 but apparently we did:
https://github.com/NixOS/nixpkgs/commits/070bfc96b7446e7d2653a1913b9bc4082d529638/pkgs/development/tools/misc/itstool/default.nix