Settings sync doesn't install any extension.

🐛 Describe the bug
Settings sync doesn't install any extension when it download my settings.
🌴 Visual Studio Code Version : 1.27.2 (VSCode OSS)
🌴 Code Settings Sync Version : 3.1.2
🌴 Operating System : ArchLinux
🌴 Occurs On: Download
🌴 Proxy Enabled: No
🌴 Gist Id: [ ID_HERE ]
📰 To Reproduce
Steps to reproduce the behavior:

Install as a clean install of VSCode
Enter token
Enter Gist ID
Settings Sync download all the files but doesn't install any extensions.

💪 Expected behavior
📺 Console Error Log
[Extension Host] Sync : /usr/lib/electron/electron
CODE SETTINGS SYNC DOWNLOAD SUMMARY
Version: 3.1.2
--------------------
GitHub Token:
GitHub Gist:
GitHub Gist Type: Secret

Restarting Visual Studio Code may be required to apply color and file icon theme.
--------------------
Files Downloaded:
  extensions.json > extensions.json
  keybindings.json > keybindings.json
  settings.json > settings.json
  vsicons.settings.json > vsicons.settings.json

Extensions Ignored:
  No extensions ignored.

Extensions Removed:
  No extensions removed.

Extensions Added:
  No extensions installed.
--------------------
Done.

Gist Id: [ ID_HERE ]

Share your gist ID

I need the GIST ID to check.
Also post the developer console logs

I need the GIST ID to check.
Also post the developer console logs
I have the same problem. This is my gist ID:
gist: d71aa3d4f75329d3b760da1e7ba17c98

I have the same problem.
My GIST ID is:
d71aa3d4f75329d3b760da1e7ba17c98
@shanalikhan

Same issues here on Linux Mint 32bit. No errors, it says "done" after the download, but no extensions are installed even after a restart. Also it doesn't apply settings. Can't share the gist, because some settings might contain sensitive info.

Possibly related to #331? VSCode OSS uses different directory names

Possibly related to #331? VSCode OSS uses different directory names

Possibly related to #331? VSCode OSS uses different directory names

It looks like. I would suggest expanding advanced options so that people could set their paths manually there. Not the best solution, but should be enough for a start. This issue seems to be very old.

Duplicate of #331

i have same issue, what could be the solution ?

Hey just came across the same issue. I can't get the extensions but in the sync history it's history. Tried between widows10 and ubuntu20.04

any updates on this?

yes, here is my output:
--------------------
Done.CODE SETTINGS SYNC DOWNLOAD SUMMARY
Version: 3.4.3
--------------------
GitHub Token: gho_**********
GitHub Gist: eff9d50ce1575e6982272851693bbe1f
GitHub Gist Type: Public

Restarting Visual Studio Code may be required to apply color and file icon theme.
--------------------
Files Downloaded:
  History\-1009c057\entries.json > History\-1009c057\entries.json
  History\-1011f0c7\entries.json > History\-1011f0c7\entries.json
  History\-10183b56\entries.json > History\-10183b56\entries.json
  History\-10ad0c64\entries.json > History\-10ad0c64\entries.json
  History\-1105e8a0\entries.json > History\-1105e8a0\entries.json
  History\-1139db3a\entries.json > History\-1139db3a\entries.json
  History\-11555437\entries.json > History\-11555437\entries.json
  History\-1155c5a\entries.json > History\-1155c5a\entries.json
  History\-11e123f6\entries.json > History\-11e123f6\entries.json
  History\-125460ca\entries.json > History\-125460ca\entries.json
  History\-1257b4a5\entries.json > History\-1257b4a5\entries.json
  History\-1261c1cc\entries.json > History\-1261c1cc\entries.json
  History\-12f0b3d4\entries.json > History\-12f0b3d4\entries.json
  History\-132db9e8\entries.json > History\-132db9e8\entries.json
  History\-132db9e8\zChB.json > History\-132db9e8\zChB.json
  History\-1333653c\entries.json > History\-1333653c\entries.json
  History\-13e70259\entries.json > History\-13e70259\entries.json
  History\-13f1362\entries.json > History\-13f1362\entries.json
  History\-1429995e\entries.json > History\-1429995e\entries.json
  History\-1453e330\entries.json > History\-1453e330\entries.json
  History\-14c989dd\entries.json > History\-14c989dd\entries.json
  History\-1511c851\entries.json > History\-1511c851\entries.json
  History\-1529a264\entries.json > History\-1529a264\entries.json
  History\-1552dc68\entries.json > History\-1552dc68\entries.json
  History\-15a41e13\entries.json > History\-15a41e13\entries.json
  History\-163b2755\entries.json > History\-163b2755\entries.json
  History\-16597ed9\entries.json > History\-16597ed9\entries.json
  History\-16c979bb\entries.json > History\-16c979bb\entries.json
  History\-170e2bce\entries.json > History\-170e2bce\entries.json
  History\-1710c796\entries.json > History\-1710c796\entries.json
  History\-17133afb\entries.json > History\-17133afb\entries.json
  History\-175a9909\entries.json > History\-175a9909\entries.json
  History\-175b0d68\entries.json > History\-175b0d68\entries.json
  History\-175b81c7\entries.json > History\-175b81c7\entries.json
  History\-175c6a85\entries.json > History\-175c6a85\entries.json
  History\-175cdee4\entries.json > History\-175cdee4\entries.json
  History\-176ca5a3\entries.json > History\-176ca5a3\entries.json
  History\-1772b7fe\entries.json > History\-1772b7fe\entries.json
  History\-17b23458\entries.json > History\-17b23458\entries.json
  History\-17e7729b\entries.json > History\-17e7729b\entries.json
  History\-180662b7\2BPV.json > History\-180662b7\2BPV.json
  History\-180662b7\GWMt.json > History\-180662b7\GWMt.json
  History\-180662b7\HFTh.json > History\-180662b7\HFTh.json
  History\-180662b7\JkR9.json > History\-180662b7\JkR9.json
  History\-180662b7\P2Uw.json > History\-180662b7\P2Uw.json
  History\-180662b7\Y5w3.json > History\-180662b7\Y5w3.json
  History\-180662b7\entries.json > History\-180662b7\entries.json
  History\-180662b7\l9Y9.json > History\-180662b7\l9Y9.json
  History\-180662b7\ymmL.json > History\-180662b7\ymmL.json
  History\-188e6d55\entries.json > History\-188e6d55\entries.json
  History\-18a1ce7a\entries.json > History\-18a1ce7a\entries.json
  History\-18a37ecd\entries.json > History\-18a37ecd\entries.json
  History\-18efb2ff\entries.json > History\-18efb2ff\entries.json
  History\-19029f50\entries.json > History\-19029f50\entries.json
  History\-190e1958\entries.json > History\-190e1958\entries.json
  History\-1915b540\entries.json > History\-1915b540\entries.json
  History\-193734f\Agae.json > History\-193734f\Agae.json
  History\-193734f\AvY1.json > History\-193734f\AvY1.json
  History\-193734f\entries.json > History\-193734f\entries.json
  History\-1941ea51\entries.json > History\-1941ea51\entries.json
  History\-1941eb11\entries.json > History\-1941eb11\entries.json
  History\-19531e9b\entries.json > History\-19531e9b\entries.json
  History\-1996e08c\entries.json > History\-1996e08c\entries.json
  History\-19aa179f\entries.json > History\-19aa179f\entries.json
  History\-19ce16c5\entries.json > History\-19ce16c5\entries.json
  History\-19f447c6\entries.json > History\-19f447c6\entries.json
  History\-1a55e565\entries.json > History\-1a55e565\entries.json
  History\-1a87b0bc\entries.json > History\-1a87b0bc\entries.json
  History\-1a9fa265\entries.json > History\-1a9fa265\entries.json
  History\-1ac987d0\entries.json > History\-1ac987d0\entries.json
  History\-1b0d8ebb\entries.json > History\-1b0d8ebb\entries.json
  History\-1b61d658\entries.json > History\-1b61d658\entries.json
  History\-1b863751\entries.json > History\-1b863751\entries.json
  History\-1b9412f4\entries.json > History\-1b9412f4\entries.json
  History\-1babab99\entries.json > History\-1babab99\entries.json
  History\-1bb978e3\entries.json > History\-1bb978e3\entries.json
  History\-1beb944b\entries.json > History\-1beb944b\entries.json
  History\-1bfe64c0\entries.json > History\-1bfe64c0\entries.json
  History\-1c37bb59\entries.json > History\-1c37bb59\entries.json
  History\-1cbfc455\entries.json > History\-1cbfc455\entries.json
  History\-1d309aae\entries.json > History\-1d309aae\entries.json
  History\-1d5c99ec\entries.json > History\-1d5c99ec\entries.json
  History\-1d6d6bae\entries.json > History\-1d6d6bae\entries.json
  History\-1d97cf50\entries.json > History\-1d97cf50\entries.json
  History\-1dc08ff2\entries.json > History\-1dc08ff2\entries.json
  History\-1dd04769\entries.json > History\-1dd04769\entries.json
  History\-1dd316b1\entries.json > History\-1dd316b1\entries.json
  History\-1e2d28ce\3U2H.json > History\-1e2d28ce\3U2H.json
  History\-1e2d28ce\Hlsy.json > History\-1e2d28ce\Hlsy.json
  History\-1e2d28ce\Wgee.json > History\-1e2d28ce\Wgee.json
  History\-1e2d28ce\entries.json > History\-1e2d28ce\entries.json
  History\-1e3320b\entries.json > History\-1e3320b\entries.json
  History\-1e44325f\entries.json > History\-1e44325f\entries.json
  History\-1e8e17fa\entries.json > History\-1e8e17fa\entries.json
  History\-1e919270\entries.json > History\-1e919270\entries.json
  History\-1ec83997\entries.json > History\-1ec83997\entries.json
  History\-1f0e0cca\entries.json > History\-1f0e0cca\entries.json
  History\-1f1bbd39\entries.json > History\-1f1bbd39\entries.json
  History\-1f98d886\entries.json > History\-1f98d886\entries.json
  History\-1fb0ce95\entries.json > History\-1fb0ce95\entries.json
  History\-1fcd8c4f\entries.json > History\-1fcd8c4f\entries.json
  History\-20031f16\entries.json > History\-20031f16\entries.json
  History\-2012e6a4\entries.json > History\-2012e6a4\entries.json
  History\-202255c6\entries.json > History\-202255c6\entries.json
  History\-206086a6\entries.json > History\-206086a6\entries.json
  History\-2063f090\entries.json > History\-2063f090\entries.json
  History\-20724f1c\entries.json > History\-20724f1c\entries.json
  History\-212a6e73\entries.json > History\-212a6e73\entries.json
  History\-213a7020\8oxI.json > History\-213a7020\8oxI.json
  History\-213a7020\PnDY.json > History\-213a7020\PnDY.json
  History\-213a7020\entries.json > History\-213a7020\entries.json
  History\-213a7020\j5Bi.json > History\-213a7020\j5Bi.json
  History\-213a7020\ok2d.json > History\-213a7020\ok2d.json
  History\-213a7020\wOfj.json > History\-213a7020\wOfj.json
  History\-215e2b51\entries.json > History\-215e2b51\entries.json
  History\-21609bc7\entries.json > History\-21609bc7\entries.json
  History\-2218d62d\entries.json > History\-2218d62d\entries.json
  History\-22390eea\entries.json > History\-22390eea\entries.json
  History\-2262cd4f\entries.json > History\-2262cd4f\entries.json
  History\-228ddd23\entries.json > History\-228ddd23\entries.json
  History\-2296f041\entries.json > History\-2296f041\entries.json
  History\-22d0bf1\entries.json > History\-22d0bf1\entries.json
  History\-2303ea30\entries.json > History\-2303ea30\entries.json
  History\-23594326\entries.json > History\-23594326\entries.json
  History\-23a727b6\entries.json > History\-23a727b6\entries.json
  History\-23b2aa52\entries.json > History\-23b2aa52\entries.json
  History\-23dd59f7\entries.json > History\-23dd59f7\entries.json
  History\-23e75a0c\entries.json > History\-23e75a0c\entries.json
  History\-24335068\entries.json > History\-24335068\entries.json
  History\-24454010\entries.json > History\-24454010\entries.json
  History\-24554fef\entries.json > History\-24554fef\entries.json
  History\-24a76055\entries.json > History\-24a76055\entries.json
  History\-24f02f88\entries.json > History\-24f02f88\entries.json
  History\-250f5a83\entries.json > History\-250f5a83\entries.json
  History\-2512c84c\entries.json > History\-2512c84c\entries.json
  History\-2572dc6c\entries.json > History\-2572dc6c\entries.json
  History\-2598be31\entries.json > History\-2598be31\entries.json
  History\-25a07902\entries.json > History\-25a07902\entries.json
  History\-25bb1a1e\entries.json > History\-25bb1a1e\entries.json
  History\-25d75a87\entries.json > History\-25d75a87\entries.json
  History\-25d7cee6\entries.json > History\-25d7cee6\entries.json
  History\-2611a7ff\entries.json > History\-2611a7ff\entries.json
  History\-26321aa7\entries.json > History\-26321aa7\entries.json
  History\-267f7569\entries.json > History\-267f7569\entries.json
  History\-26d400ad\entries.json > History\-26d400ad\entries.json
  History\-26e2cf8d\entries.json > History\-26e2cf8d\entries.json
  History\-271e163e\entries.json > History\-271e163e\entries.json
  History\-272a2083\entries.json > History\-272a2083\entries.json
  History\-273f3a51\entries.json > History\-273f3a51\entries.json
  History\-27849694\entries.json > History\-27849694\entries.json
  History\-278744fc\BkiA.json > History\-278744fc\BkiA.json
  History\-278744fc\QiIT.json > History\-278744fc\QiIT.json
  History\-278744fc\entries.json > History\-278744fc\entries.json
  History\-279b6357\entries.json > History\-279b6357\entries.json
  History\-27bb69cb\entries.json > History\-27bb69cb\entries.json
  History\-27e6eeb4\entries.json > History\-27e6eeb4\entries.json
  History\-28040c9c\entries.json > History\-28040c9c\entries.json
  History\-2820dff0\entries.json > History\-2820dff0\entries.json
  History\-2870780a\entries.json > History\-2870780a\entries.json
  History\-28987bb\entries.json > History\-28987bb\entries.json
  History\-289c00c5\entries.json > History\-289c00c5\entries.json
  History\-29336272\entries.json > History\-29336272\entries.json
  History\-29419941\entries.json > History\-29419941\entries.json
  History\-29574e03\entries.json > History\-29574e03\entries.json
  History\-295d190a\entries.json > History\-295d190a\entries.json
  History\-299054cf\entries.json > History\-299054cf\entries.json
  History\-29dd1554\entries.json > History\-29dd1554\entries.json
  History\-2a216e2a\entries.json > History\-2a216e2a\entries.json
  History\-2a775623\entries.json > History\-2a775623\entries.json
  History\-2a92f678\entries.json > History\-2a92f678\entries.json
  History\-2aa8914a\entries.json > History\-2aa8914a\entries.json
  History\-2acad5d6\7V5X.json > History\-2acad5d6\7V5X.json
  History\-2acad5d6\entries.json > History\-2acad5d6\entries.json
  History\-2b38883c\entries.json > History\-2b38883c\entries.json
  History\-2b4b2146\entries.json > History\-2b4b2146\entries.json
  History\-2b4b95a5\entries.json > History\-2b4b95a5\entries.json
  History\-2b4c0a04\entries.json > History\-2b4c0a04\entries.json
  History\-2b4c7e63\entries.json > History\-2b4c7e63\entries.json
  History\-2b6d8b3a\entries.json > History\-2b6d8b3a\entries.json
  History\-2b7b1450\entries.json > History\-2b7b1450\entries.json
  History\-2bd3d53f\entries.json > History\-2bd3d53f\entries.json
  History\-2be627a7\entries.json > History\-2be627a7\entries.json
  History\-2c00643\entries.json > History\-2c00643\entries.json
  History\-2c1788bb\entries.json > History\-2c1788bb\entries.json
  History\-2c1af451\entries.json > History\-2c1af451\entries.json
  History\-2c726ae2\entries.json > History\-2c726ae2\entries.json
  History\-2c7c4b9f\entries.json > History\-2c7c4b9f\entries.json
  History\-2c7eb0b5\entries.json > History\-2c7eb0b5\entries.json
  History\-2c7f2514\entries.json > History\-2c7f2514\entries.json
  History\-2c7f9973\entries.json > History\-2c7f9973\entries.json
  History\-2cc4ae24\entries.json > History\-2cc4ae24\entries.json
  History\-2cc5a0ac\entries.json > History\-2cc5a0ac\entries.json
  History\-2cc5bf6c\entries.json > History\-2cc5bf6c\entries.json
  History\-2ccffd71\entries.json > History\-2ccffd71\entries.json
  History\-2cd2f377\entries.json > History\-2cd2f377\entries.json
  History\-2cebd866\entries.json > History\-2cebd866\entries.json
  History\-2d4a95a6\entries.json > History\-2d4a95a6\entries.json
  History\-2d6c832f\entries.json > History\-2d6c832f\entries.json
  History\-2d6dd050\entries.json > History\-2d6dd050\entries.json
  History\-2da984d2\6QXX.json > History\-2da984d2\6QXX.json
  History\-2da984d2\entries.json > History\-2da984d2\entries.json
  History\-2ddec60b\entries.json > History\-2ddec60b\entries.json
  History\-2de65146\entries.json > History\-2de65146\entries.json
  History\-2debe86c\entries.json > History\-2debe86c\entries.json
  History\-2e18f00f\entries.json > History\-2e18f00f\entries.json
  History\-2ed7b665\entries.json > History\-2ed7b665\entries.json
  History\-2f15c861\entries.json > History\-2f15c861\entries.json
  History\-2f174609\entries.json > History\-2f174609\entries.json
  History\-2f8c5276\entries.json > History\-2f8c5276\entries.json
  History\-2fac3bb9\entries.json > History\-2fac3bb9\entries.json
  History\-2fb413eb\entries.json > History\-2fb413eb\entries.json
  History\-305e047e\entries.json > History\-305e047e\entries.json
  History\-305eed3c\entries.json > History\-305eed3c\entries.json
  History\-30a5ce31\entries.json > History\-30a5ce31\entries.json
  History\-30afdc28\0AHM.json > History\-30afdc28\0AHM.json
  History\-30afdc28\3kDI.json > History\-30afdc28\3kDI.json
  History\-30afdc28\6gsx.json > History\-30afdc28\6gsx.json
  History\-30afdc28\AnAu.json > History\-30afdc28\AnAu.json
  History\-30afdc28\Eijs.json > History\-30afdc28\Eijs.json
  History\-30afdc28\IdMC.json > History\-30afdc28\IdMC.json
  History\-30afdc28\Iq52.json > History\-30afdc28\Iq52.json
  History\-30afdc28\dNqU.json > History\-30afdc28\dNqU.json
  History\-30afdc28\dXx9.json > History\-30afdc28\dXx9.json
  History\-30afdc28\dwQV.json > History\-30afdc28\dwQV.json
  History\-30afdc28\entries.json > History\-30afdc28\entries.json
  History\-30afdc28\fN5e.json > History\-30afdc28\fN5e.json
  History\-30afdc28\hQZI.json > History\-30afdc28\hQZI.json
  History\-30afdc28\mxgE.json > History\-30afdc28\mxgE.json
  History\-30afdc28\qNvH.json > History\-30afdc28\qNvH.json
  History\-30afdc28\seoU.json > History\-30afdc28\seoU.json
  History\-30afdc28\yMDI.json > History\-30afdc28\yMDI.json
  History\-30afdc28\zOz2.json > History\-30afdc28\zOz2.json
  History\-31009d1f\entries.json > History\-31009d1f\entries.json
  History\-310cf5f9\entries.json > History\-310cf5f9\entries.json
  History\-31666f91\entries.json > History\-31666f91\entries.json
  History\-316fac9e\entries.json > History\-316fac9e\entries.json
  History\-31be5251\entries.json > History\-31be5251\entries.json
  History\-31d8f61f\entries.json > History\-31d8f61f\entries.json
  History\-31f03686\entries.json > History\-31f03686\entries.json
  History\-328cd64a\entries.json > History\-328cd64a\entries.json
  History\-32f590bd\entries.json > History\-32f590bd\entries.json
  History\-330dc963\entries.json > History\-330dc963\entries.json
  History\-334c6895\entries.json > History\-334c6895\entries.json
  History\-33cf974d\entries.json > History\-33cf974d\entries.json
  History\-33e4c605\entries.json > History\-33e4c605\entries.json
  History\-3493553b\entries.json > History\-3493553b\entries.json
  History\-349b0b5c\entries.json > History\-349b0b5c\entries.json
  History\-34ccc08b\entries.json > History\-34ccc08b\entries.json
  History\-3521ffd\entries.json > History\-3521ffd\entries.json
  History\-3535e9c4\entries.json > History\-3535e9c4\entries.json
  History\-3598bcba\entries.json > History\-3598bcba\entries.json
  History\-3599ea23\entries.json > History\-3599ea23\entries.json
  History\-35f35742\entries.json > History\-35f35742\entries.json
  History\-35fb35bc\entries.json > History\-35fb35bc\entries.json
  History\-360e43c8\entries.json > History\-360e43c8\entries.json
  History\-363e3f10\entries.json > History\-363e3f10\entries.json
  History\-366ea3df\entries.json > History\-366ea3df\entries.json
  History\-36dcdd39\entries.json > History\-36dcdd39\entries.json
  History\-3710f375\entries.json > History\-3710f375\entries.json
  History\-37469046\entries.json > History\-37469046\entries.json
  History\-374ddd00\entries.json > History\-374ddd00\entries.json
  History\-37556e1d\entries.json > History\-37556e1d\entries.json
  History\-3777a61f\entries.json > History\-3777a61f\entries.json
  History\-37828d79\entries.json > History\-37828d79\entries.json
  History\-37a21fcb\entries.json > History\-37a21fcb\entries.json
  History\-37b3b7d9\entries.json > History\-37b3b7d9\entries.json
  History\-37feb78b\entries.json > History\-37feb78b\entries.json
  History\-383c5b7b\entries.json > History\-383c5b7b\entries.json
  History\-383f5412\entries.json > History\-383f5412\entries.json
  History\-3869ad66\entries.json > History\-3869ad66\entries.json
  History\-38b2047b\entries.json > History\-38b2047b\entries.json
  History\-3a00ba11\entries.json > History\-3a00ba11\entries.json
  History\-3a18703a\entries.json > History\-3a18703a\entries.json
  History\-3a229040\entries.json > History\-3a229040\entries.json
  History\-3a8e5d76\entries.json > History\-3a8e5d76\entries.json
  History\-3a939050\entries.json > History\-3a939050\entries.json
  History\-3a9404af\entries.json > History\-3a9404af\entries.json
  History\-3aab5ebd\entries.json > History\-3aab5ebd\entries.json
  History\-3aca23b3\entries.json > History\-3aca23b3\entries.json
  History\-3adc67ff\entries.json > History\-3adc67ff\entries.json
  History\-3b52bc35\entries.json > History\-3b52bc35\entries.json
  History\-3b5541ff\entries.json > History\-3b5541ff\entries.json
  History\-3b8a587c\entries.json > History\-3b8a587c\entries.json
  History\-3c3bdb87\entries.json > History\-3c3bdb87\entries.json
  History\-3c3c0cdb\entries.json > History\-3c3c0cdb\entries.json
  History\-3c525b7b\entries.json > History\-3c525b7b\entries.json
  History\-3c830296\entries.json > History\-3c830296\entries.json
  History\-3c8b0fbb\entries.json > History\-3c8b0fbb\entries.json
  History\-3c9b7689\entries.json > History\-3c9b7689\entries.json
  History\-3ca68c09\entries.json > History\-3ca68c09\entries.json
  History\-3d31781f\entries.json > History\-3d31781f\entries.json
  History\-3d68b8b2\6Enb.json > History\-3d68b8b2\6Enb.json
  History\-3d68b8b2\RN6Z.json > History\-3d68b8b2\RN6Z.json
  History\-3d68b8b2\entries.json > History\-3d68b8b2\entries.json
  History\-3d8baade\entries.json > History\-3d8baade\entries.json
  History\-3dba4801\entries.json > History\-3dba4801\entries.json
  History\-3dec6cbf\entries.json > History\-3dec6cbf\entries.json
  History\-3ded9dba\entries.json > History\-3ded9dba\entries.json
  History\-3e4b22cc\entries.json > History\-3e4b22cc\entries.json
  History\-3e7100d1\entries.json > History\-3e7100d1\entries.json

Extensions Ignored:
  No extensions ignored.

Extensions Removed:
  No extensions removed.

Extensions Added:
  No extensions installed.
--------------------

As you can see "no extensions installed"

Same issue, same output as above.
Didn't find anything online and my gist is working on my mac but not on windows.
Any updates?

Same output as above.
Work on mac but not on windows, nothing sync.
Any updates?

Hi there,
Same for me...
Unable to sync my config


Check source code with golint

Currently build script checks the code with gofmt. Adding checks with golint is good for the Walter source.

Fixed with #134


Additional closing trades feature

*Close trades from the furthest trades that are in loss.

Hello!
Thank you for the commit, but I would recommend applying such a change to a separate fork of the EA's code. I don't think that this change will be good for everyone.


IOError from DuckDB when run with Superset

First of all, this is a great project! However, I ran into a minor error on my local machine.
I cloned the project and run it with make docker-run-superset. Everything went well until I visit the dashboard in Superset. Then I got the following error:
Error: (duckdb.IOException) IO Error: Trying to read a database file with version number 51, but we can only read version 43.
The database file was created with an newer version of DuckDB.

The storage of DuckDB is not yet stable; newer versions of DuckDB cannot read old database files and vice versa.
The storage will be stabilized when version 1.0 releases.

For now, we recommend that you load the database file in a supported version of DuckDB, and use the EXPORT DATABASE command followed by IMPORT DATABASE on the current version of DuckDB.

See the storage page for more information: https://duckdb.org/internals/storage
(Background on this error at: http://sqlalche.me/e/13/e3q8)

Definitely a backward incompatibility with DuckDB but I don't know what DuckDB version I should use.

I am attaching a screenshot for reference.

just noticed it is the exactly same as this issue. trying to match duckdb version in superset and dbt-duckdb

Changing DuckDB version solved the issue. Created PR


Can't find package in Atom package installer

Have tried searching for jsdoc and atom-jsdoc.
I'm using Atom version 1.0.5
I want to use this package but don't know how to install it.

No avalible package for this version winth trying install by apm. Please, update package to latest atom build.

I would like this as well unless anyone knows of an alternative plugin?

I'm using https://atom.io/packages/docblockr now.  So far so good.

I Have same problem.


UnconnectedPing missing pingId field

The UnconnectedPing (0x01) packet actually has an extra long at the end indicating the ID of the client. It has also been discovered that the "pingId" in UnconnectedPong (0x1C) is actually the timestamp from UnconnectedPing, not a random ping ID.

Fixed in 2.7.6


Fixed Name collision issue with keyword "Result" when using WKZombie in the same project with Alamofire in it.

This resolves an issue where there is a name collision of keyword "Result" when using WKZombie in the same project with Alamofire in it.
ERROR: "Result' is ambiguous for type lookup in this context" with Alamofire in the same project

Closing this pull request. See #72 for more info.


Simplify tracking params of car-rental widget

This one makes car rental forms that appear aside on some NTK pages pass Tealium requirements.

:+1:


Fails to encode map.keys

Converting object to an encodable object failed: Instance of '_CompactIterable'

print() had handled this without error.

When did you run into this exception? Can you tell me which printers you were using? Also please provide the entire stacktrace/error output.

I've ran into the same issue. Here's what was outputted in vscode:
E/flutter ( 7377): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: Converting object to an encodable object failed: Instance of '_CompactIterable'
E/flutter ( 7377): #0      _JsonStringifier.writeObject  (dart:convert/json.dart:659:7)
E/flutter ( 7377): #1      _JsonStringStringifier.printOn  (dart:convert/json.dart:846:17)
E/flutter ( 7377): #2      _JsonStringStringifier.stringify  (dart:convert/json.dart:831:5)
E/flutter ( 7377): #3      JsonEncoder.convert  (dart:convert/json.dart:260:30)
E/flutter ( 7377): #4      PrettyPrinter.stringifyMessage  (package:logger/src/printers/pretty_printer.dart:184:22)
E/flutter ( 7377): #5      PrettyPrinter.log  (package:logger/src/printers/pretty_printer.dart:94:22)
E/flutter ( 7377): #6      Logger.log  (package:logger/src/logger.dart:115:29)
E/flutter ( 7377): #7      Logger.d  (package:logger/src/logger.dart:80:5)
E/flutter ( 7377): #8      Debug.log
package:grovemobile/Logger.dart:20
E/flutter ( 7377): #9      new ChatMessage
package:grovemobile/models/chatMessage.dart:50
E/flutter ( 7377): #10     ChatMessage.create
package:grovemobile/models/chatMessage.dart:116
E/flutter ( 7377):
E/flutter ( 7377): #11     ChatBloc.mapEventToState
package:grovemobile/…/chat/chat_bloc.dart:50
E/flutter ( 7377):
E/flutter ( 7377): #12     Bloc._bindEventsToStates.
package:bloc/src/bloc.dart:252
E/flutter ( 7377): #13     Stream.asyncExpand.onListen.  (dart:async/stream.dart:579:30)
E/flutter ( 7377): #14     _rootRunUnary  (dart:async/zone.dart:1192:38)
E/flutter ( 7377): #15     _CustomZone.runUnary  (dart:async/zone.dart:1085:19)
E/flutter ( 7377): #16     _CustomZone.runUnaryGuarded  (dart:async/zone.dart:987:7)
E/flutter ( 7377): #17     _BufferingStreamSubscription._sendData  (dart:async/stream_impl.dart:339:11)
E/flutter ( 7377): #18     _DelayedData.perform  (dart:async/stream_impl.dart:594:14)
E/flutter ( 7377): #19     _StreamImplEvents.handleNext  (dart:async/stream_impl.dart:710:11)
E/flutter ( 7377): #20     _PendingEvents.schedule.  (dart:async/stream_impl.dart:670:7)
E/flutter ( 7377): #21     _rootRun  (dart:async/zone.dart:1180:38)
E/flutter ( 7377): #22     _CustomZone.run  (dart:async/zone.dart:1077:19)
E/flutter ( 7377): #23     _CustomZone.runGuarded  (dart:async/zone.dart:979:7)

Ah. That makes sense. Seems you are passing a ChatMessage as a value of a map key to the printer? Then that ChatMessage needs to implement a String toJson() method.

Ah. That makes sense. Seems you are passing a ChatMessage as a value of a map key to the printer? Then that ChatMessage needs to implement a String toJson() method.

How ablout if Class don't have toString method,  print Instance of 'xxxx'  instead of throw Error.

I encountered this same error today with the Camera plugin passing in an array of CameraDescription objects
E/flutter (23935): [ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: Converting object to an encodable object failed: Instance of 'CameraDescription'
E/flutter (23935): #0      _JsonStringifier.writeObject (dart:convert/json.dart:688:7)
E/flutter (23935): #1      _JsonPrettyPrintMixin.writeList (dart:convert/json.dart:793:7)
E/flutter (23935): #2      _JsonStringifier.writeJsonValue (dart:convert/json.dart:718:7)
E/flutter (23935): #3      _JsonStringifier.writeObject (dart:convert/json.dart:679:9)
E/flutter (23935): #4      _JsonStringStringifier.printOn (dart:convert/json.dart:877:17)
E/flutter (23935): #5      _JsonStringStringifier.stringify (dart:convert/json.dart:862:5)
E/flutter (23935): #6      JsonEncoder.convert (dart:convert/json.dart:262:30)
E/flutter (23935): #7      PrettyPrinter.stringifyMessage
package:logger/…/printers/pretty_printer.dart:201
E/flutter (23935): #8      PrettyPrinter.log
package:logger/…/printers/pretty_printer.dart:101
E/flutter (23935): #9      Logger.log
package:logger/src/logger.dart:115
E/flutter (23935): #10     Logger.i
package:logger/src/logger.dart:85

print was able to print it just fine:
I/flutter (23935): [CameraDescription(0, CameraLensDirection.back, 90), CameraDescription(1, CameraLensDirection.front, 270), CameraDescription(2, CameraLensDirection.front, 270), CameraDescription(3, CameraLensDirection.front, 270)]

I have fixed these exceptions with a simple addition of a toEncodable() optional function passed to the JsonEncoder.withIndent()   constructor.
#88


Prep README and Changelog for v0.1.0

The README should include

"Sales pitch" for this extension
Summary of core supported features
Example usage accompanied by a demo video
(as reference) Manim Notebook commands alongside their default shortcut
Roadmap of features for the near future

The Changelog should view v0.1.0 as the "initial release" and list all features that are supported. In a sense, it is the first release under a formal github workflow and the first that is publicly announced.

for "example usage" - it would be nice to at least link this:
https://github.com/3b1b/manim/blob/1139b545f9e766e7282f8cf64e68e225a4f25eb1/manimlib/scene/interactive_scene.py#L469-L539
because it's an essential part for many use-cases

thoughts, where we can also announce it:
discord, reddit which are linked here:
https://github.com/3b1b/manim?tab=readme-ov-file

So we would announce on:

Reddit
Discord to which channel(s)? I see #general, #projects, #beginner-resources, #tips-and-tricks as all valid. Perhaps we can spam multiple channels 😇
Twitter (tag @3blue1brown and @manim_community)
LinkedIn (maybe?)
As a comment on Grant's how-to youtube video

Any other outlets you would consider? @Splines @VladimirFokow what are your twitter handles?

I don't have a Twitter account, but I might post a video on my YouTube channel. However, I'd like such a video to be more than a sales-pitch and to go a bit more in-depth, so this won't happen in the timeframe you have envisioned and I'm not sure if I even have time for that video ;)
I can however create a YouTube post on my channel with a square image advertising the new extension. And on LinkedIn as well. It'd be really nice if you could create such an asset for us to use, e.g. with the VSCode icon in a corner, your cool extension logo in the center and a short title (in the image).
As a further idea: let's file in a PR to 3b1b's manim repo or to his video repo where we add a link to the extension in the Readme.

I think we should also include some images in the Readme. Since to be honest: when installing a new extension, I rarely take a too close look on the Readme. I just scroll through it and if images stand out I will see them first. Users should at least remark the ## notation in our Readme, so maybe we can showcase that in an image (including alt attributes for screen-readers).

I've just seen that on the VSCode Discussions, there exists an Extension Show and Tell category where we could also post upon our first bigger release.

Also make clear which minimal ManimGL version we support.


Type field of Resources changes

From @SoniRathore on October 3, 2018 6:51
Type field to be renamed to "Resource Category" in data import tool, backend and UI.
Make this field optional.
Copied from original issue: Microsoft/Access2Justice#535

@svasylenko Please validate this for us.


[MINOR][PYTHON][TESTS] Move test test_named_arguments_negative to test_arrow_python_udf

What changes were proposed in this pull request?
Move test test_named_arguments_negative to test_arrow_python_udf
Why are the changes needed?
it seems was added in a wrong place, it only runs in Spark Connect, not Spark Classic.
After this PR, it will also be run in Spark Classic
Does this PR introduce any user-facing change?
no, test only
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

merged to master


can not run agent

Please answer these questions before submitting your issue.

Why do you submit this issue?
[x] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

Bug

Which version of SkyWalking, OS and JRE?

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.
use <IP_ADDRESS> or localhost or real ip, bring different errors,not easy to use!!!!!!!!!!!

Requirement or improvement

Please describe about your requirements or improvement suggestions.

First run it locally. No need to worry about ip things. Then read architecture document, you will understand. Don't try to guess, read the documents.


refactor(TextInput): improve height calculations

hey @bvleur - the text input was heavily influenced by this https://github.com/andreypopp/react-textarea-autosize (I made some contributions there as well). I took some fixes from them and noticed they also have minRows & maxRows. With their implementation we potentially can reduce a domAccess in case min & max rows are defined.
I noticed you added new line characters to calculate the height, while these guys calculated the height of one row and multiplied. Do you know if we are missing anything by doing so?

Hey @nikgraf, would be interesting to know what are you missing from react-textarea-autosize not to reuse its code in Belle?

hey @andreypopp, it's actually not too much, but have few features that make the belle version different

allowNewLine (I'm happy to create a PR in case you would be interested to have this in react-textarea-autosize). The downside here is that it introduces some needed complexity and you can't pass value, defaultValue or valueLink down to the textarea, but rather control it.

props like hoverStyle, focusStyle, … (this is very opinionated)

we decided to consistently use onUpdate for belle components (find some details here: https://github.com/nikgraf/belle/issues/58)


Add Cache-Control and Expires HTTP headers in response

Hello,
This is a small patch to add some cache control in configuration.
If you use some caching technologies like varnishd in front of thumbor it could be usefull to add Cache-Control and Expires header to make varnish storing fine the generated image preventing request at thumbor to often.
I add some tests with it but wasn't able to make them working, all the tests ends with :
AssertionError: Async operation timed out after X seconds
Did I missed something ?
Best regards,
--
Damien

Thanks a LOT Damien. We'll integrate asap.
Cheers,
Bernardo Heynemann
On Thu, Dec 29, 2011 at 1:44 PM, Damien Hardy <
<EMAIL_ADDRESS>
wrote:

Hello,
This is a small patch to add some cache control in configuration.
If you use some caching technologies like varnishd in front of thumbor it
could be usefull to add Cache-Control and Expires header to make varnish
storing fine the generated image preventing request at thumbor to often.
I add some tests with it but wasn't able to make them working, all the
tests ends with :
AssertionError: Async operation timed out after X seconds
Did I missed something ?
Best regards,
--
Damien
You can merge this Pull Request by running:
git pull https://github.com/dhardy92/thumbor master
Or you can view, comment on it, or merge it online at:
https://github.com/globocom/thumbor/pull/53
-- Commit Summary --

add optional Cache-Control and Expires HTTP headers in response

-- File Changes --
M tests/test_handlers.py (11)
M thumbor/config.py (1)
M thumbor/handlers/init.py (5)
-- Patch Links --
https://github.com/globocom/thumbor/pull/53.patch
https://github.com/globocom/thumbor/pull/53.diff

Reply to this email directly or view it on GitHub:
https://github.com/globocom/thumbor/pull/53

Implemented this on master.
Thanks a LOT for contributing.


Automated cherry pick of #3555: feature: keystone add service config API and allow config services by API

Cherry pick of #3555 on release/2.12.
#3555: feature: keystone add service config API and allow config services by API

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@020fcae). Click here to learn what that means.
The diff coverage is 2.92%.

@@              Coverage Diff               @@
##             release/2.12   #3556   +/-   ##
==============================================
  Coverage                ?   6.97%
==============================================
  Files                   ?     498
  Lines                   ?   83364
  Branches                ?       0
==============================================
  Hits                    ?    5812
  Misses                  ?   77058
  Partials                ?     494

Flag
Coverage Δ

#aFlag
6.97% <2.92%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/skus_tools.go
0% <ø> (ø)

pkg/keystone/models/services.go
9.47% <0%> (ø)

pkg/keystone/models/passwords.go
12.32% <0%> (ø)

pkg/keystone/tokens/auth.go
0% <0%> (ø)

pkg/keystone/driver/cas/class.go
40% <0%> (ø)

pkg/keystone/models/syncworker.go
0% <0%> (ø)

pkg/keystone/driver/cas/cas.go
0% <0%> (ø)

pkg/keystone/models/configs.go
8.44% <1.76%> (ø)

pkg/keystone/models/identity_provider.go
1.85% <21.42%> (ø)

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 020fcae...38f7cea. Read the comment docs.

/lgtm
/approve


UPDATE: Compass icon

LiveURL: https://orbit-components-updat-compasicon.surge.sh

Path definition is broken, doesn't work for 24x24 viewBox.

Should be fixed


A bug in implements of loading image for docker v1.12.0

These seems a bug in implements of loading image in line 239 of load.go(v1.12.0).
repositoriesFile, err := os.Open(repositoriesPath)
	if err != nil {
		if !os.IsNotExist(err) {
			return err
		}
		return repositoriesFile.Close()
	}
	defer repositoriesFile.Close()

If repositoriesFile doesn't exist, it will go to "return reposigoriesFile.Close()". Since it does not exist, why we close it? And the close will cause an "invalid argument" error.
Besides, does the new version of docker support loading layers? In version 1.8.2, I can load a middle layer if its parents have existed in docker, but now docker seems not support it anymore. According to the implements of v1.12.0, docker does not look up layer's parent in file system first but just check if it exits in the tarball file.

I think that's a bug indeed, but has been there since 1.10.0 (see https://github.com/docker/docker/blob/v1.10.0/image/tarexport/load.go#L164-L171)
Are you interested in opening a pull request?

Besides, does the new version of docker support loading layers? In version 1.8.2, I can load a middle layer if its parents have existed in docker, but now docker seems not support it anymore. According to the implements of v1.12.0, docker does not look up layer's parent in file system first but just check if it exits in the tarball file.

That's due to the content-addressable store; since 1.10, the way layers are "collected" for an image changed. In older versions, the "parent" image chain is walked to collect the image-layers for the image. Since docker 1.10, each image contains a list of image-layers that compose the image; the "parent" chain is no longer used for that, which also means that pulling an image will no longer pull parent images.

Sorry for the late reply  and I will open a pull request later to fix the bug.

@ywk253100
I think in load.go, there are two places have the same problem.
repositoriesFile, err := os.Open(repositoriesPath)
	if err != nil {
		if !os.IsNotExist(err) {
			return err
		}
		return repositoriesFile.Close()
	}

Wish it could be fixed soon.

Besides, does the new version of docker support loading layers? In version 1.8.2, I can load a middle layer if its parents have existed in docker, but now docker seems not support it anymore.

You can't load layers individually but you don't have to have all the layers in tar if docker already has them https://github.com/docker/docker/pull/18727


Support for env file per flavor

fixes #82  #1

This reads all matching .env files regardless of them being used or not, which is not the best, but it allows running multiple builds like:
gradlew assembleDevelopmentDebug assembleProductionRelease


Move privacy acceptance on payment step

Closes #445

What I did

How to test

Checklist

[x] Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests).
[x] Make sure to add/update documentation regarding your changes.
[x] You are NOT deprecating/removing a feature.

@sfiorucci thanks for highlight this improvement

:tada: This PR is included in version 4.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


SUBGRAPH: Prove that 38 and 42 are equivalent

This corresponds to issue "SUBGRAPH: Prove that 38 and 42 are equivalent."

awaiting-review

@ChienYungChi : Can you check and resolve the merge conflicts. In all likelihood, merging the main branch into your PR should fix it.

@ChienYungChi was the PR closing accidental?

Hi, I resolved the conflict and proposed a new PR. I don’t know if the
closing was accidental.
簡勇吉
On Sat, Sep 28, 2024 at 9:52 AM Shrys @.***> wrote:

@ChienYungChi https://github.com/ChienYungChi was the PR closing
accidental?
—
Reply to this email directly, view it on GitHub
https://github.com/teorth/equational_theories/pull/38#issuecomment-2380347036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR3AKL5OJ5GJN4ADTO55VX3ZYYDUBAVCNFSM6AAAAABPAEYIZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQGM2DOMBTGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

You don't need to close a PR when resolving a merge conflict.

OK. I didn’t know that I could resolve that in the same PR, so I created
another one. I didn’t close the old PR myself. Maybe it was automatically
closed.
簡勇吉
On Sat, Sep 28, 2024 at 10:06 AM Shrys @.***> wrote:

You don't need to close a PR when resolving a merge conflict.
—
Reply to this email directly, view it on GitHub
https://github.com/teorth/equational_theories/pull/38#issuecomment-2380354129,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR3AKL4B5QYSEIUNNZP43JLZYYFLNAVCNFSM6AAAAABPAEYIZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQGM2TIMJSHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Maybe the old PR was closed because I discarded a commit in my fork before
creating the new commit. Next time I will just add commits instead of
discarding one ones first.
簡勇吉
On Sat, Sep 28, 2024 at 10:12 AM 簡勇吉 @.***> wrote:

OK. I didn’t know that I could resolve that in the same PR, so I created
another one. I didn’t close the old PR myself. Maybe it was automatically
closed.
簡勇吉
On Sat, Sep 28, 2024 at 10:06 AM Shrys @.***> wrote:

You don't need to close a PR when resolving a merge conflict.
—
Reply to this email directly, view it on GitHub
https://github.com/teorth/equational_theories/pull/38#issuecomment-2380354129,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR3AKL4B5QYSEIUNNZP43JLZYYFLNAVCNFSM6AAAAABPAEYIZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQGM2TIMJSHE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add C# language options Kubernetes AWS and Azure templates

⚠ Don't merge this until https://github.com/pulumi/templates/pull/411 has merged.

This is ready to be merged as soon as we give it the 👍.


More streamlined image tinting

-[UIImage rz_tintedImageWithColor:] exists, but you have to use it first before inserting the image into the string. It should be done automatically if a string with an embedded image also has a textColor set (or maybe use a separate imageColor property).

seconded. should be a separate property to account for cases in which requirements dictate that text and image have different colors.

A BonText that has an image can't also have a string (the properties intentionally clobber each other), so just using textColor shouldn't be a problem.

In the upcoming 4.0 release, images set to "automatic" or "always template" will now be tinted if they are styled with a color.


[ARTEMIS-1477] Removing netty-all dependency from jms-client

The JIRA title and the commit comment both reference the jms-client, but none of the files changed are directly related to the jms-client.  Any chance you could update these to be more accurate?
Can you provide a quick explanation of why the change is necessary?


[QUESTION] Longhorn Web-UI not loading

Question
Hi all,
I cant reach the Longhorn Web-UI.
I followed the Longhorn installation guide via helm: https://longhorn.io/docs/1.2.2/deploy/install/install-with-helm/ (including successfull requirements check). Results:
kubectl get pods -n longhorn-system
NAME                                        READY   STATUS    RESTARTS      AGE
csi-attacher-75588bff58-7mzcw               1/1     Running   0             63m
csi-attacher-75588bff58-dwst8               1/1     Running   0             63m
csi-attacher-75588bff58-nrk58               1/1     Running   0             63m
csi-provisioner-669c8cc698-cmlvc            1/1     Running   0             63m
csi-provisioner-669c8cc698-jxqlb            1/1     Running   0             63m
csi-provisioner-669c8cc698-whbts            1/1     Running   0             63m
csi-resizer-5c88bfd4cf-l5jpw                1/1     Running   0             63m
csi-resizer-5c88bfd4cf-l9x98                1/1     Running   0             63m
csi-resizer-5c88bfd4cf-sskwt                1/1     Running   0             63m
csi-snapshotter-69f8bc8dcf-56n4f            1/1     Running   0             63m
csi-snapshotter-69f8bc8dcf-jlf8g            1/1     Running   0             63m
csi-snapshotter-69f8bc8dcf-l6qlp            1/1     Running   0             63m
engine-image-ei-d4c780c6-hl6lb              1/1     Running   0             63m
engine-image-ei-d4c780c6-kcmml              1/1     Running   0             63m
engine-image-ei-d4c780c6-mbmq9              1/1     Running   0             63m
engine-image-ei-d4c780c6-njbr2              1/1     Running   0             63m
instance-manager-e-16b797ac                 1/1     Running   0             63m
instance-manager-e-54f9de01                 1/1     Running   0             63m
instance-manager-e-d801ac0e                 1/1     Running   0             63m
instance-manager-e-db5ba766                 1/1     Running   0             63m
instance-manager-r-8f204c95                 1/1     Running   0             63m
instance-manager-r-ad74c0c4                 1/1     Running   0             63m
instance-manager-r-c4807df1                 1/1     Running   0             63m
instance-manager-r-cf6a68ab                 1/1     Running   0             63m
longhorn-csi-plugin-7w8ld                   2/2     Running   0             63m
longhorn-csi-plugin-r8q4n                   2/2     Running   0             63m
longhorn-csi-plugin-r9pqr                   2/2     Running   0             63m
longhorn-csi-plugin-v85ck                   2/2     Running   0             63m
longhorn-driver-deployer-75f68555c9-8nw7d   1/1     Running   0             64m
longhorn-iscsi-installation-jd5zb           1/1     Running   0             84m
longhorn-iscsi-installation-qntvs           1/1     Running   0             84m
longhorn-iscsi-installation-svlrk           1/1     Running   0             84m
longhorn-iscsi-installation-wp22l           1/1     Running   0             84m
longhorn-manager-7mlsn                      1/1     Running   1 (63m ago)   64m
longhorn-manager-8gp7k                      1/1     Running   0             64m
longhorn-manager-jppdb                      1/1     Running   1 (63m ago)   64m
longhorn-manager-jzn42                      1/1     Running   1 (63m ago)   64m
longhorn-nfs-installation-2ml5j             1/1     Running   0             80m
longhorn-nfs-installation-6dlnk             1/1     Running   0             80m
longhorn-nfs-installation-96vdd             1/1     Running   0             80m
longhorn-nfs-installation-m7xr5             1/1     Running   0             80m
longhorn-ui-75ccbd4695-ms4tv                1/1     Running   0             64m

Next, I installed a nginx ingress controller, by following the "bare metal" guide on https://kubernetes.github.io/ingress-nginx/deploy/#bare-metal. I added the lines
annotations:
    ingressclass.kubernetes.io/is-default-class: "true"

to the nginx yaml file. Everthing else is original. The file looks as follows:
          secret:
            secretName: ingress-nginx-admission
---
# Source: ingress-nginx/templates/controller-ingressclass.yaml
# We don't support namespaced ingressClass yet
# So a ClusterRole and a ClusterRoleBinding is required
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
  labels:
    helm.sh/chart: ingress-nginx-4.0.6
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 1.0.4
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: controller
  annotations:
    ingressclass.kubernetes.io/is-default-class: "true"
  name: nginx
  namespace: ingress-nginx
spec:
  controller: k8s.io/ingress-nginx
---
# Source: ingress-nginx/templates/admission-webhooks/validating-webhook.yaml
# before changing this value, check the required kubernetes version
# https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#prerequisites
apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingWebhookConfiguration
metadata:
  labels:
    helm.sh/chart: ingress-nginx-4.0.6
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/version: 1.0.4
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/component: admission-webhook
  name: ingress-nginx-admission
webhooks:
  - name: validate.nginx.ingress.kubernetes.io

Next, I followed the Longhorn guide for setting up an longhorn UI ingress https://longhorn.io/docs/1.2.2/deploy/accessing-the-ui/longhorn-ingress/.
With file "auth" containing two entries:
user1:$xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
user2:$xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Results are:
kubectl get ingress --all-namespaces
NAMESPACE         NAME               CLASS   HOSTS   ADDRESS        PORTS   AGE
longhorn-system   longhorn-ingress   nginx   *       "my_host_ip"   80      7m32s

and:
kubectl get svc -n ingress-nginx
NAME                                 TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx-controller             NodePort    <IP_ADDRESS>     <none>        80:31436/TCP,443:30418/TCP   18m
ingress-nginx-controller-admission   ClusterIP   <IP_ADDRESS>   <none>        443/TCP                      18m

Curling the nodeport twice without credentials (second time I get an completly different answer):
curl -v http://my_host_ip:31436/
*   Trying my_host_ip:31436...
* TCP_NODELAY set
* Connected to my_host_ip (my_host_ip) port 31436 (#0)
> GET / HTTP/1.1
> Host: my_host_ip:31436
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 401 Unauthorized
< Date: Thu, 11 Nov 2021 08:45:55 GMT
< Content-Type: text/html
< Content-Length: 172
< Connection: keep-alive
< WWW-Authenticate: Basic realm="Authentication Required"
<

<title>401 Authorization Required</title>

401 Authorization Required

nginx

* Connection #0 to host my_host_ip left intact
user1@host:~/longhorn$ curl -v http://my_host_ip:31436/
*   Trying my_host_ip:31436...
* TCP_NODELAY set
* Connected to my_host_ip (my_host_ip) port 31436 (#0)
> GET / HTTP/1.1
> Host: my_host_ip:31436
> User-Agent: curl/7.68.0
> Accept: */*
>

curling with credentials:
 curl -v http://my_host_ip:31436/ -u user1:xxxxxxxxxxxxxxxxx
*   Trying my_host_ip:31436...
* TCP_NODELAY set
* Connected to my_host_ip:31436 (my_host_ip:31436) port 31436(#0)
* Server auth using Basic with user 'user1'
> GET / HTTP/1.1
> Host: my_host_ip:31436
> Authorization: Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Wed, 10 Nov 2021 13:40:02 GMT
< Content-Type: text/html
< Content-Length: 1025
< Connection: keep-alive
< Last-Modified: Thu, 07 Oct 2021 11:29:55 GMT
< Vary: Accept-Encoding
< ETag: "615eda33-401"
< Cache-Control: max-age=0
< Accept-Ranges: bytes
<
<!DOCTYPE html>

  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">

<link href="./styles.css?fc8ec4140abd497a1b70" rel="stylesheet">

* Connection #0 to host my_host_ip left intact

Entering credentials via my browser (after port forwarding to my local laptop 'ssh -L 31436:localhost:31436 user1@my_host_ip' and then in browser: http://localhost:31436/) will be accepted but the Longhorn Webpage wont be loaded. All I see is the Longhorn symbol on my browser tab.
Any ideas how to fix that?
Thank you in advance.
Environment:

Longhorn version: 1.2.2
Kubernetes version: 1.22.2
Underlying Infrastructure: Baremetal

All I see is the Longhorn symbol on my browser tab.

Could you please provide the screenshot?
You're using the Baremetal, usually, I use the MetalLB in front of it.
But personally, I use NodePort to access the LH when developing.
Could you please check if the NodePort works for you?


Develop Footer with Tailwind CSS

Purpose
Develop the Footer with Tailwind CSS ensuring responsiveness
Goals
Move Antd Components to Tailwind CSS
Approach
N/A
Screenshots

Checklist

[X ] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[ X] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[ X] My code follows the style guidelines of this project
[ X] I have performed a self-review of my own code
[X ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Related PRs
N/A
Test environment
N/A
Learning
N/A

@vishwaikon Rename the file names also. If git is not detecting the change check this out: https://stackoverflow.com/questions/13805750/git-fails-to-detect-renaming

@anjula-sack  Made the changes and updated the PR description. Regards!


DNS resolution errors if DNS changes after daemon has started

I am using a corporate private Maven repository whose domain can only be resolved once connected via VPN. When I use mvnd before I am connected to the VPN it obviously fails. But if I afterwards connect to the VPN, the DNS lookup does still not work and I get the message
[ERROR] Failed to execute goal on project org.apache.sling.feature.cpconverter: Could not resolve dependencies for project org.apache.sling:org.apache.sling.feature.cpconverter:jar:1.1.1-SNAPSHOT: Failed to collect dependencies at org.apache.sling:org.apache.sling.jcr.contentloader:jar:2.4.3-SNAPSHOT: Failed to read artifact descriptor for org.apache.sling:org.apache.sling.jcr.contentloader:jar:2.4.3-SNAPSHOT: Could not transfer artifact org.apache.sling:org.apache.sling.jcr.contentloader:pom:2.4.3-SNAPSHOT from/to nexus (https://repo.int.netcentric.biz/nexus/content/groups/public/): Transfer failed for https://repo.int.netcentric.biz/nexus/content/groups/public/org/apache/sling/org.apache.sling.jcr.contentloader/2.4.3-SNAPSHOT/org.apache.sling.jcr.contentloader-2.4.3-SNAPSHOT.pom: Unknown host repo.int.netcentric.biz -> [Help 1]
If I execute the same Maven command via regular mvn it starts working immediately once I am connected to the VPN.
Seems that either the Java process or some Maven internals still use the old DNS or cache resolutions aggressively.

Probably the system property https://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.html#nct has to be set.

The default is 30 seconds afaik: https://github.com/AdoptOpenJDK/openjdk-jdk11/blob/master/src/java.base/share/classes/sun/net/InetAddressCachePolicy.java#L48

@kwin can you double check that it works if you wait one minute ?
Also, note that networkaddress.cache.ttl is a security property (it has to be set in the [JAVA_HOME]/conf/security/java.security file), but you can try adding -Dsun.net.inetaddr.ttl=5 to the command line, or adding mvnd.jvmArgs=-Dsun.net.inetaddr.ttl=5 to your ~/.m2/mvnd.properties file.

The weird thing is that the DNS resolution was not successful before, therefore sun.net.inetaddr.negative.ttl should be taken into account, but this is already set to 0 by default (never). I will try to do some more tests...

This error is persistent until I restart the mvn daemon. Seems that Maven is doing some kind of caching here. I don't think that Java is to blame here

Do you have the full stack trace to verify which transport is used ? The default http transport uses the org.apache.http.client.HttpClient which can optionally be configured with a custom DnsResolver, but I don't think that's the case.  What's weird is that afaik, transports should not live longer than the maven session, which is tied to the build.

This is the full stack trace when not yet connected to the proper DNS:
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.apache.sling:org.apache.sling.repoinit.parser:pom:1.6.9-SNAPSHOT from/to nexus (https://repo.int.netcentric.biz/nexus/content/groups/public/): transfer failed for https://repo.int.netcentric.biz/nexus/content/groups/public/org/apache/sling/org.apache.sling.repoinit.parser/1.6.9-SNAPSHOT/org.apache.sling.repoinit.parser-1.6.9-SNAPSHOT.pom
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:424)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:229)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:207)
	at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:240)
	... 23 common frames omitted
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.apache.sling:org.apache.sling.repoinit.parser:pom:1.6.9-SNAPSHOT from/to nexus (https://repo.int.netcentric.biz/nexus/content/groups/public/): transfer failed for https://repo.int.netcentric.biz/nexus/content/groups/public/org/apache/sling/org.apache.sling.repoinit.parser/1.6.9-SNAPSHOT/org.apache.sling.repoinit.parser-1.6.9-SNAPSHOT.pom
	at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:52)
	at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:369)
	at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:75)
	at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:628)
	at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:262)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:513)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:401)
	... 26 common frames omitted
Caused by: org.apache.maven.wagon.TransferFailedException: transfer failed for https://repo.int.netcentric.biz/nexus/content/groups/public/org/apache/sling/org.apache.sling.repoinit.parser/1.6.9-SNAPSHOT/org.apache.sling.repoinit.parser-1.6.9-SNAPSHOT.pom
	at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1250)
	at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1140)
	at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:126)
	at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
	at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
	at org.eclipse.aether.transport.wagon.WagonTransporter$GetTaskRunner.run(WagonTransporter.java:546)
	at org.eclipse.aether.transport.wagon.WagonTransporter.execute(WagonTransporter.java:430)
	at org.eclipse.aether.transport.wagon.WagonTransporter.get(WagonTransporter.java:407)
	at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:457)
	at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:364)
	... 31 common frames omitted
Caused by: java.net.UnknownHostException: repo.int.netcentric.biz
	at java.base/java.net.InetAddress$CachedAddresses.get(InetAddress.java:797)
	at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1509)
	at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1368)
	at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1302)
	at org.apache.maven.wagon.providers.http.httpclient.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)
	at org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:112)
	at org.apache.maven.wagon.providers.http.httpclient.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
	at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
	at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
	at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec.execute(RetryExec.java:89)
	at org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.maven.wagon.providers.http.httpclient.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.maven.wagon.providers.http.httpclient.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:1005)
	at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1162)
	... 40 common frames omitted
[ERROR]

the same appears after switching to the right DNS, with standalone mvn it starts working then.

@kwin I doubt it unfortunately.  I'll try to get back to this issue and investigate more...


Problem reading / writing in TCP stream.

I am playing with http2 and wanted to make a simple server to test it out.
I created a TCP server and am reading and parsing http2 bytes which works without a problem.
But then I tried to write response frames while reading TCP stream this resulted in me then reading the frames I written. Basically I cannot read and write into the TCP stream at the same time.
I created a simple example code of this that you can try out that simulates the above problem:
https://github.com/MoMannn/rust-async-std-server-issue-example

I'm not familiar with http2 but this doesn't seem to be an issue with async-std to me because even a blocking version with std networking exhibits the same behavior:
https://gist.github.com/stjepang/aa46961abea8010d1f71b5933ad9ba1f

🤔 Closing this issue here. Was sure this had to do something with async. Thanks for quick response.


[request] Allow populating the linked table of a Reference column on the fly

This one seems kind of useful to me as I have been compelled to backtrack several times while copying-pasting data into a new Grist document.

I have a list of cities with their contries attached in LibreOffice, which I Copy:

I create a new Grist document
I name the default table Cities
I paste the list > OK

Now I want the Country to be a Reference list from another table, Countries. So:

I create a new table Countries
I name the first column Name > OK and the table is currently empty
I go back to the Cities and transform the 2nd column to a Reference, choosing the reference table as Counntries and the displayed column as Name
When I click Apply, the column turns red to show there is an error
Also, the column Name in the table Countries is not populated

I think there should at least be a question asked to the user if he/she wants to add unique values from the column Cities:country to the table Countries.
Otherwise, as it is currently, the process is really tedious:

in LibreOffice I get all unique values in the column Country and copy them
I create the table Countries in Grist
I paste the column Country from LibreOffice in the newly created table Countries in Grist
I go back to LibreOffice and copy the whole table this time
I go back to the Cities table in Grist
I paste the two columns (city and country)
I then transform the Country column into a Reference column

Phew...

Converting a column type allows creating an association between two tables of data, but you are right that there is no option currently to move data around as part of this conversion. I've also run into cases when I'd like some option like it, but usually the need is a bit more involved.
For this example, imagine that for each row contains another column with the country's language (e.g. "French" for the first three rows, and "German" for the next three). Ideally, if the list of unique countries moves to a new table, I'd like languages to move along with it. But then a checkbox isn't enough.
There is actually a way to do what you want (though still not so quick or easy):

Add Widget to Page > Cities [Summarize] > Group By: Country
In Creator Panel > Table > Data for the new summary table, select Detach
This creates a new table of countries: rename it to Countries.
Optionally, remove things you don't need: the count column, the group column (which you'd need to unhide first), and the "Countries" widget from the first page.
Now, transform the Country column into a Reference column.

Thanks for the procedure. Also, I understand your point about the multiple possible choices of Reference columns.
All well thought, I guess this is a fringe need as it mostly happens once: when switching from another source to Grist.


Properly override Shims for int96Rebase [databricks]

Signed-off-by: Raza Jafri<EMAIL_ADDRESS>
Added methods for returning the Rebase conf for different versions of Spark in their proper Shims
No further tests were added

closes #3642

build

build

Failed due to OOM

build


v2rayn: Major Update to 6.21

Closes #XXXX

Relates to #XXXX

[x] I have read the Contributing Guide.

/verify

SEE
https://github.com/ScoopInstaller/Versions/pull/907
https://github.com/ScoopInstaller/Versions/commit/bf961e23365072071fee37bf1c18a6af85ef1d3e

/verify

/verify
The author deleted the 7z package…

/verify
The author deleted the 7z package…


Ignore removed workspace folders in setup-symlinks helper

Summary

It contains 2 fixes:

The symlinks for workspaces created by setup-symlink had an invalid target.
If a workspace does not exist, the helper failed because the symlink could not be read.

Use Cases

In case you do not want your final image to contain a workspace and delete it after build, the helper setup-symlinks would fail. Now, instead of failing, this symlink is just not created.
Checklist

[X] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[X] I have reviewed the styleguide for guidance on my code quality.
[X] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

Hi @c0d1ngm0nk3y, we've done some work that's now on main to fix the tests in this PR. If you could rebase this branch w those changes I'd be happy to get it merged.

Hi @c0d1ngm0nk3y, we've done some work that's now on main to fix the tests in this PR. If you could rebase this branch w those changes I'd be happy to get it merged.

The PR has been rebased


HD-612 Strings: reverse sweep

@ydrain @mariasica @craig-day
Risks
low.  English edits and title improvements

:+1:  on green


Split Package in various target

This will give more control on which part of generated code you want to use:

only Models (no need for Alamofire)
Models + Requests (no need for Alamofire)
Models + Request + Client (required Alamofire)

All of this is usable with or without dynamic library(it will now work with my dependencies that are used in Xcodegen and are imported in multiples frameworks)
This should change nothing at all to most people except the removal of timeline.
This should simplify the migration out of Alamofire because now there is only one part of the code to focus on to remove it.
This should simplify refactoring of a part of the template if needed.
Issue

This force me to remove Timeline feature of Alamofire.

I would love to have some comment from @yonaskolb about this.

This not ready for review yet I found new bugs sorry.


Add stele to the Electron apps public list

https://github.com/electron/apps#readme

Moved to Jira - https://smm.atlassian.net/browse/EXTCH-51


Create Your First App on Cloud Foundry

Group: https://developers.sap.com/group.scp-3-first-app.html
Hi,
Please change "SAP Cloud Platform cockpit" to "SAP BTP cockpit" in the introductory text of the tutorial. The name of the product changed a long time ago.
Regards
Jimmy

Thank you for the feedback.  The text has been updated.


remove kube-register and update config-default

Some updates to the Rackspace scripts that will let us run v0.18.1

generally get things working
use newer rackspace cloud flavor names (https://github.com/GoogleCloudPlatform/kubernetes/pull/8984 can be closed)
update coreos (beta) image id
use NUM_MINIONS instead of RAX_NUM_MINIONS - for the standard validation scripts
I know scp the known_tokens file to the master. Not ideal but works for the moment.

@doublerr +1 I think we should start leveraging the node registration built into k8s going forward.

@kelseyhightower ya, I removed kube-register from the rackspace cloud config in favor of the self registration. It was pretty painless as long as the nodes have the right tokens, etc. Thanks for the making kube-register though, it definitely helped until self registration was a thing.
This patch only touches the Rackspace coreos cloud config.

LGTM.  Thanks for the update!

Oncall: this should be safe to merge as it can't affect our e2es

@doublerr we still seem to need a CLA from you.  Is your rackspace email address associated with your github account?

Removing LGTM until CLA is verified.

@quinton-hoole I'm on the CLA as<EMAIL_ADDRESS>I've just added the email to my profile but not sure if it needs to be primary for your scripts to catch it.

Thanks Ryan.  I manually verified your CLA.  To save hassle and make this automatic in future, please remind Rackspace to follow the instructions that they should have received with their CLA (setting up an appropriate Google Group with members etc).


Oxygen Subsystem: Tygon tubing not rated for pressure

Current behaviour

The 5894K34 1/4" ID Tygon tubing is rated for 5psi max and should not be used at the oxygen inlet pressure nor the intermediate regulated pressure.
It could be used at the patient inhale limb pressure but since these hoses would be easy to mix up, whatever solution used would probably be best applied to all the entire oxygen inlet pathway unless it would be impossible to mix up.

Expected behaviour

Inlet path should be rated for the highest expected hospital supply pressure, at least 50psi
Regulated pathway will probably be between 15 to 45psi depending on our design

How do you know it is wrong

McMaster spec for the tygon tubing. https://www.mcmaster.com/5894K34/

Code pointers
Lives in this doc: https://github.com/RespiraWorks/Ventilator/tree/master/manufacturing/oxygen
Possible solution:

use PU push-to-connect pneumatic fittings and tubing from the oxygen inlet to the regulator and from the regulator to the PSOL. It possible that the PU hose can be used from the PSOL to the inhale limb as well but I'm not sure if we would run into flow constriction problems at the lower pressure of the inlet limb. Any pneumatics people want to chime in here?

Rough calc using an online calculator shows (apologies for the mixed units):

0.2m of 6mm OD, 4mm ID PU tube at 50psi pressure, 60lpm flow (oxygen inlet to reg): 0.7% drop (should be OK)
0.2m of 6mm OD, 4mm ID PU tube at 15psi pressure, 60lpm flow (reg to PSOL, PSOL to inhale): 8% drop (probably not great)
0.2m of 8mm" OD, 5mm ID PU tube at 15psi pressure, 60lpm flow (reg to PSOL, PSOL to inhale): 2.5% drop (better)

Using 8mm OD PU tubing for all, the following part numbers are examples:

8mm OD 5mm ID PU tubing, opaque green: https://www.mcmaster.com/50315K25-50315K321/
Inlet and IR2010 regulator 1/4" NPT to 8mm tubing push connect: https://www.mcmaster.com/5225K715/
IR1010 regulator and PVQ31-xx-01N PSOL 1/8" NPT to 8mm tubing push connect: https://www.mcmaster.com/5225K714/
IBV19M PSOL: 1/8" BSPP to 8mm tubing push connect: https://www.mcmaster.com/5225K507/
SMC PVQ31-xx-01 1/8" BSPT to 8mm tubing push connect: https://www.mcmaster.com/5225K305/

Would love to have a person with pneumatics experience check over this.
Don't forget

[ ] Put the issue in a milestone
[ ] Assign it to one of the projects
[ ] Add appropriate labels
[ ] Mention dependent/blocked issues if any

@tijanim @martukas I tagged this v0.3 hardware because I believe this makes breaks the v0.3 design for use with supplied oxygen, and because it might have an impact on the physical layout.  Feel free to move the tag if appropriate.

@tijanim @martukas I tagged this v0.3 hardware because I believe this makes breaks the v0.3 design for use with supplied oxygen, and because it might have an impact on the physical layout.  Feel free to move the tag if appropriate.

@inceptionev can you confirm to have built a modification with those particular parts and it has fixed the problem?

Can confirm this was built with the 8mm tubing and push-connect fittings in a v0.3 enclosed build and it solves the problem of the tubing popping off the fittings, and provides sufficient flow of >60 lpm.  Note that with this setup, the regulator is still not oxygen-safe (#952), so v0.3 with respect to oxygen is for for control demonstration only.

@yusufcance @canooonn to select the tubing we need to connect the PSOL outlet to the oxygen venturi, we need to check the flow rate.  If we use the 8mm PU tubing, the internal diameter will be 5mm.  For an estimated 150mm of tubing length, what is the required pressure to achieve 120L/min flow rate (you may also need to consider the resistance of the venturi for this, or provide sufficient margin).  Most hospitals have around ~350kpa oxygen outlets, so assume we regulate this down to 200kpa, and we want to achieve > 120L/m at this pressure given the selected tubing and venturi.


Add staker statistics: candidates (Nova) [medium]

Description

Priority: medium

This is part 2 of 3 statistics we would like to have for Nova. For this statistics, we would like to track how many candidated there are.
The 3 parts are:

validators in committee
candidates
total

Afaik, this needs an INX endpoint
Motivation
Improve statistics to accomodate to new IOTA 2.0 features, like staker statistics
Requirements

Open questions (optional)

Are you planning to do it yourself in a pull request?
No.

Implemented in features analytics.


feature: Zone-aware SAML SP metadata

Implemented to the same level as the default IdenityZone's SP metadata generation.
Minus NameIDFormat value populaition and registration-ID specific implementation.

[#187846376]

LGTM


Dev into next

Merges latest Gravity 2.x updates from develop into next.

:tada: This PR is included in version 2.2.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Recursively copying elements from one graph to another

Allows for easy portability of elements (Variables and Ops) from one Tensorflow Graph to another. If called on a top-level root in a dataflow graph, automatically copies all required instances.
Provides an API to retrieve the copied elements in the other graph, using a namespace.
Reference: https://codesachin.wordpress.com/2015/11/20/recursively-copying-elements-from-one-graph-to-another-in-tensorflow/

Just added the code, haven't changed any imports yet. Want to get general feedback before refining the code.

Hi @srjoglekar246, this looks pretty cool, and thanks for going through the work to put this together!
One of the ideas we have been working on is a notion of "Functions" in the GraphDef, which would allow for re-usable components.  See here for the proto definition.
It's not ready yet and still needs some work (we may not do this as a proto in the GraphDef) but the underlying idea would be something that would obviate the need for copying elements around with unique names: you could define a subgraph as a function with inputs and outputs, and then re-use them.  So instead of having multiple versions of the graph stamped out at once, each with unique names, you could have one named function that could be called, ported across graphs, etc.
Do you feel that such a feature would accomplish your higher level goals?

Aah yes. The whole idea was to enable reusability of dataflow-structures across Graph instances. If I am not wrong, your solution would need some careful handling of how sessions 'run' these portable functions. But if implemented right, it could save a lot of memory and accomplish what my code intends.

Yeah, there's some more plumbing in the internal execution of graphs that specially handles functions.
For now, do you mind if we keep this pull request open but on the backburner, at least until we figure out whether functions may be an easier to use abstraction?
(If you really want this checked in somewhere and know lots of others are using this, we've been intending to create a 'contrib' directory or repo where these types of utilities / functions could be placed).

Yeah no problem!
On the other hand, a contrib directory for such scripts would be nice - especially for code that might be useful to a good audience as utilities (instead of being inside the main framework).

Can one of the admins verify this patch?

Ping @vrv

We've considered adding a contrib directory but ownership and bug reports would be hard to manage -- probably needs to be a separate repo.  Adding @martinwicke since I think he's in the process of figuring this out.
There's been more progress over the past few weeks on functions.  I think it's close -- take a look at an example:  https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/framework/function_test.py#L279  and let us know if that would sort of accomplish what you want

@vrv With the experience of opecv-contrib it is hard to maintain a quality level in a contributed repository and grant a decent review time of that PR. One of the best community scaling effort is the Debian developer/maintainer process. We can implement a very light version of this here. Github lowered the entrance cost of new developers trough the fork-PR process but also let proliferation of sparse or short time frame contributions. We can find a way to reward middle and long term valid contributors or contributors groups to maintain some contrib modules in Tensorflow and to review and accept related PR and issue on this targets modules. I don't know what will be the best way to to this with the actual Github managements features for handling process of module Orphaning, contributor/group MIA, new module proposal acceptance and module removal. I think that Wikifing community rules a little bit, using labels, repositories, and submodules the process could be managed in some way.

@vrv A separate repo would be nice, would even let users build a proper codebase for different algorithms implemented in tensorflow. Something like what sklearn is for scipy.
As far as the code goes, it pretty much does what I wanted to achieve, with a better interface for reusable functions across graphs. Is it coming out in the next version? The function class would also enable running of different algorithms within same environment - a nice bonus.

@srjoglekar246, @bhack: we'll try to find something that works for contributions.
As for functions: I'm not entirely sure what the state of it is, but I wanted to solicit early feedback from you since it seems like what you originally were trying to do with this PR.  It's being actively worked on so I'm hoping it will be ready "soon".

I guess once we can define reusable functions, we could do away with initialising ops as "tf.add", instead going for the method used here: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/framework/function_test.py#L99 . My only suggestion would be to make the system smarter with respect to argument types (like adding float types to int types should automatically return a float, assuming shapes are compatible). But I guess it won't be too easy, especially in C++.

I'm afraid that creating a separate repo would lose the focus of the community as a whole.

Sorry for the long silence -- if you're still interested, I'd like to merge this into contrib. Can you move the file to tensorflow/contrib/copy_graph/python/util/copy.py?
Also, can you add a license header and the python3 from future imports, and can you add a test for this?

Can one of the admins verify this patch?

@martinwicke Will get it done by tomorrow. Any particular format/guideline for the unit test to be added?

Just make sure that it tests the functionality you claim your functions provide.

And can you modify the docstrings to match the tensorflow style guide (look at the "writing documentation" howto)?
Thanks!

@martinwicke Could you take a look at the code (especially the BUILD and test files) and tell me if I am on the right track?

@martinwicke Made the changes. Let me know if there's anything more to be modified.

Ping @martinwicke

Can one of the admins verify this patch?

Jenkins, test this please.

I've had some minor comments about python module things, but otherwise looks good.

@martinwicke I made the changes, and fixed the bazel test errors. They all pass now. Have a look.

Thanks!
Jenkins, test this please.

@martinwicke Seems to work. Okay to be pushed in?

Thanks!

Hi @vrv ,
I'm currently writing some high-level library based on tensorflow. I'm relying a lot on copying existing ops to achieve re-usability of data flow structures. So I'm very interested in the "Functions" idea you mentioned here. I'm wondering how this is going on.
Because I recently meet some problems due to not copying op._control_flow_context, which makes gradients through tf.cond failed in copied subgraph. This problem also exists in this contribution.

There's been some work on functions but it's still kind of primitive and I don't know how well it composes with control flow.
We have https://github.com/tensorflow/tensorflow/blob/5a566a7701381a5cf7f70fce397759483764e482/tensorflow/python/framework/function.py which isn't yet public (but until we seal the public interface it's still available to play around with), and it isn't getting that much love / attention unfortunately.  But if it proves useful, let us know and maybe we can at least make it public at some point.

@vrv Thanks for the link. I had a look at functions and unfortunately that's not what I actually want. I can describe my high-level goals here. It's something like theano.clone() (related issues: #5479 #1070), which, in my view, can be seen as operation-level reuse rather than subgraph-level, which enables one to replace inputs of any operations in the graph. I guess this is also what the author of tf.contrib.graph_editor tries to achieve.


Update README.md

numpy 1.24 is not compatible:
module 'numpy' has no attribute 'int'

It might be better to change the code to remove all np.int and np.float, honestly, so newer numpy can work too. I can work on a PR for that.


Test Bug

CircleCI Build Bug Test

@Ndacyayisenga-droid Looks fine! Bug Test completed. CircleCI Verified✅


Improve badges

Fix an incorrect link, use shields.io for all badges for the sake of consistency and a few minor improvements.

Thanks!


Unable to overwrite k3s agent configuration.

Environmental Info:
k3s master is running in my local machine and i am trying to run the k3s agent in edge device but there i dont have root access along with can't write anything to  /etc, /var, /usr/bin directory. So k3s agent not able write the agent configuration to /etc/rancher directory. While running k3s agent it is not able to find out the default configuration.  Is there any way to write the agent configuration into any custom directory instead of /etc/rancher.
K3s Version:

1.26
Node(s) CPU architecture, OS, and Version:

Cluster Configuration:

1 master, 2 agents
Describe the bug:

Not able write the agent configuration to custom directory other than  /etc/rancher directory.
Steps To Reproduce:

Installed K3s on edge device

Expected behavior:

ks3 agent should connect to mster.
Actual behavior:

Additional context / logs:

Is there any way to overwrite the agent configuration into any custom directory instead of /etc/rancher.

No. Can you bind-mount a writable partition to /etc/rancher?


Strip in-workspace devDependencies when pruning

Describe the feature you'd like to request
Hi,
First of all, thanks for this awesome project, it's really powerful!
We're currently using the great turbo prune feature, and we noticed a potential optimization.
Imagine a project app having two "in-workspace" dependencies:

lib-config as a dependency
tooling as a devDependency

Currently, running turbo prune --scope=app will generate a directory out/ with app, lib-config and tooling.
In our case, we run turbo prune in our CI after all packages have been built. Therefore, we don't need the devDependencies in our out/ directory.
Ideally, our pruned out/ directory would contain only app and lib-config, which are the only packages needed at runtime.
Describe the solution you'd like
Having an optional --production flag that would ignore the devDependencies would be great.
Describe alternatives you've considered
I don't think there are any alternatives, except keeping the devDependencies, which is frankly not a big deal. It's just less optimal... But, isn't Turborepo all about optimization? 😉

@joemckenney  care to share your rm-dev-deps.mjs script referenced in issue #1488 ? I'm having the same problem as you, 1GB docker image

@joemckenney care to share your rm-dev-deps.mjs script referenced in issue #1488 ? I'm having the same problem as you, 1GB docker image

Here's a gist https://gist.github.com/joemckenney/fd55f02ab0bf905283423aadeeca80ca
The script uses a package we built called @dopt/wutils - which assumes you use pnpm. It's open source but not published to any registry - you can find it here https://github.com/dopt/odopt/tree/main/packages/%40dopt/wutils and take inspiration from it or copy pieces to recreate the functionality.
The stage that utilized it in our container looked like this:
FROM node:16.9.1-alpine AS pruner
ENV NODE_ENV=production
RUN apk update && apk add jq
WORKDIR /app
COPY --from=builder /app/ .
RUN node scripts/rm-dev-deps.mjs
RUN npx turbo prune --scope="@app/server" --docker
RUN cp ./out/yarn.lock ./out/json
RUN cd out/json; for pkg in `yarn workspaces list --json | jq .location | sed 's/"//g' | tail -n +2 | xargs`; do mv /app/$pkg/dist /app/out/json/$pkg/; done; cd ../../;
RUN rm -rf ./apps ./packages ./node_modules ./scripts yarn.lock
RUN mv ./out/json/* .
RUN rm -rf ./out

Some additional context - this problem was solved by our shift from yarn to pnpm and pnpm's deploy command.

okay, thanks! I stumbled upon pnpm myself in the last hour, that seems the way to go

Tagging core team member to make sure this gets seen since it is a pretty major issue @gsoltis
Annoyingly, pnpm v8 introduced a regression where it broke pnpm deploy so there isn't even a fallback option.
Related pnpm issues:

https://github.com/pnpm/pnpm/issues/6437#issuecomment-1546989143
https://github.com/pnpm/pnpm/issues/6540

A --production flag does seem like a good idea.
cc @chris-olszewski, how hard would this be to do? I got a little lost reading the prune code with the transitive_closure stuff, so I wasn't able to get an easy answer

This is something we do want to add, but a few things need to happen first:

We need to change our package graph to contain what dependency types in the edges. This is a fairly straight forward change, but it will be pretty invasive throughout the codebase.
Come to agreement on flag naming
Once those are done, this feature will just be using the correct package graph in prune.

Faced this today where one of our packages required some devDependencies for building it but turbo prune is pulling them inside production build the way our pipeline is built. We have to write a workaround for this but it would be great if it was natively available.

Just came across this problem when dockerizing my app today. The only decent workaround I could think of is to extract packages that are devDependencies in my apps to a separate repo, publish those to a registry, and install them that way. Definitely not a great workaround in cases where you don't want to publish those.

Facing same issue my workspace has some tooling packages in devDeps and they are getting bundled in image. Some packages like prettier typescript are quite heavy like 22MB

I spent some time struggling with the same issue. I am using pnpm and I tried pnpm deploy, but that messes with the symlinks. If I add the option to inject, then turbo complains.
Till there is a fix, here is a possible workaround -
I'm compiling the build output to a single file (using vercel/ncc - can also be tsup or something similar) and only copying that output to the final layer of my docker image, and I am at a third of the previous size. Be mindful of the pitfalls of this approach and make sure you test all code paths by bundling and running this locally before going to production


Add https/wss support to graphql api webpage

Explain your changes:

Add https/wss support to the graphql api webpage

Explain how you tested your changes:

Run mina daemon
ngrok http 3085
Use the tmp https:// reverse proxy url to visit graphql client page

Checklist:

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

Closes #0000

!ci-build-me


Determine and codify best practices and coding style

Quick question: I know we obviously never want to break the CI build on master, but is it okay to push code that I know will break the build to a dev branch? I currently have some tests that are failing (see #31), and I want to write the fix on the IO dev branch. Is it okay to push the failing tests to the test-refactor branch before I write the fix?
Also, we should see about writing up a quick development best practices and coding style document to codify some of these things. I have Codacy's automated code review service set up to run code style analysis, but I haven't put the Codacy badge on the README because we haven't really worked out what coding style rules we want to follow. I vote tentatively for Effective Scala.

Never mind, the first part of this issue is a moot point, the io-refact dev branch is way stale. I'll just make the fix on master and push the tests later.
I'm leaving this open since we ought to have a discussion regarding dev policy.

This is assigned to @ArcticLight because I'd like his input on it, not because he has to take sole responsibility for it.

The Effective Scala document seems like a reasonable thing. Standards seem like a reasonable thing. Basically, I approve this message and approve of standards. I will need to read up on Effective Scala, but I think it's fine to use.

Cool. I believe Codacy is currently set up to run all the code style checks from Effective Scala, plus a couple of additional checks I've enabled that I think are important. Do note that Codacy only runs code review on Scala code – any Java code in the repo is silently ignored.
If you're signing off on our coding standards being Effective Scala-based, I'll add a note in the readme stating that. If we want to build on Effective Scala and say "we also require x, y, and z", we can do that, as well.

I've added a page on contributing to Pathway to the project wiki. If this seems reasonable to you, I'll add it to a markdown document in the repo itself as well, and put a link in the README.
We may also wish to come up with a Contributor License Agreement (CLA) for Pathway to avoid any legal troubles, but that's probably deserving of its own issue.

I think this is finished.


Updated jwt gem and allow jwt options hash to be used

Here is a group of commits to enhance the tool and clean up a couple of issues.
The main things addressed are:

upgrade to security and bugfix upgrade of JWT gem
allow passing through the options hash that the JWT gem requires in order to verify most claims.

I also pulled in the other pull request that was pending into this group of commits so you only need to do one merge to get both pull requests.
Tests have been added for all changes.
Cheers,
Glenn

cc: @fgehrm

PS - A new release once this is pulled in would be great!  Thx.

@grempe  can't merge your changes :cry:

Closing this pull request.  I'll give you another in a minute that does not contain the final commit (which was a reproduction of the other pull request you pulled in, that's why you could no longer merge.  I thought I was making it easier for you to pull just one, but I guess not.


Clean up stored preferences and create a TestFX test manipulating them

I was just trying to create an TestFX test where I changed the a preference (such as which is the most recent repo), but doing it without breaking my experience as a regular Elegit user. The tests already ignore the user's normal preferences, but adding a preference before Elegit starts is hard. For that matter, the prefs in Elefit are kind of a mess; they're supposed to be associated with a class, but it's somewhat all over the map which class we're using. Clean this up, and generate a TextFX  test that changes a preference before it starts.
The commit where I have the test I started to write is 1852ec9.

I completed this as part of helping the tests to run in parallel. All tests (so long as they call the right initialization code) now store their preferences in a sandbox.


bitwarden-desktop: 2024.4.1 -> 2024.5.0

Diff: https://github.com/bitwarden/clients/compare/desktop-v2024.4.1...desktop-v2024.5.0
Changelog: https://github.com/bitwarden/clients/releases/tag/desktop-v2024.5.0
Description of changes

Things done

Tested copy-paste, vault sync.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

After this I did #319269 to remove the inactive maintainer. Maybe @dotlambda or myself could be added, if you/he/they want to.


is it not possible to insert api key

i am  unable to insert my api key,not even after deleting it and cleaning the cache,it simply doesn't request the api key and neither there's a flag option to use.

@manoelacmn thank you for rising the issue. Now you can enter the api key by using chatgpt-cli -k command.