求图：沧州.geojson

有没有人已下载沧州.geojson 地图? 能与我和大家分享么。
现在echarts-china-cities-js漏了大沧州。https://github.com/chfw/echarts-china-cities-js/issues/1
谢谢

One-line summary [问题简述]
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:
Browser version [浏览器类型和版本]:
OS Version [操作系统类型和版本]:

Expected behaviour [期望结果]
ECharts option [ECharts配置项]

option = {

}

Other comments [其他信息]

{"type": "FeatureCollection", "features": [{"type":"Feature","properties":{"name":"泊头市"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.652823515625,38.219702375],[116.662081328125,38.2077053046875],[116.71478640625,38.18698753125],[116.741832304688,38.1909841132813],[116.747345,38.1838430000001],[116.74267703125,38.1770839667969],[116.695094023438,38.1460964179688],[116.649176054688,38.1289150214844],[116.61970828125,38.1085707832031],[116.6601965625,38.0934206367188],[116.663746367188,38.0775966621094],[116.643013945313,38.0475722480469],[116.632345,38.0499636054688],[116.622345,38.0477223945313],[116.59435671875,38.0539968085938],[116.583013945313,38.0375722480469],[116.5526184375,38.0443862128907],[116.547345,38.0238430000001],[116.51595828125,38.0171376777344],[116.482345,38.0191408515625],[116.472345,38.0185451484376],[116.46209109375,38.0191555],[116.45255984375,38.0084865546876],[116.3768371875,38.020005109375],[116.337564726563,38.0176638007813],[116.30259890625,37.9785305000001],[116.292120390625,37.9791542792969],[116.272628203125,37.9685622382813],[116.227154570313,37.9545204902344],[116.172174101563,37.9692458320313],[116.161539335938,37.9573464179688],[116.163804960938,37.9193691230469],[116.087345,37.9138430000001],[116.104093046875,37.9391847968751],[116.09142703125,37.9479274726563],[116.07326296875,37.9797585273438],[116.057345,37.9838430000001],[116.049893828125,37.9988283515626],[116.054976835938,38.0092348457032],[116.038585234375,38.0298720527344],[116.068116484375,38.03839378125],[116.050704375,38.0472023750001],[116.047345,38.0638430000001],[116.062808867188,38.0683803535156],[116.100616484375,38.0825868964844],[116.14275515625,38.0782912421875],[116.163487578125,38.1119106269531],[116.212633085938,38.0981703925781],[116.223604765625,38.1113784003907],[116.265455351563,38.1295290351562],[116.281881132813,38.1493056464844],[116.292896757813,38.158452375],[116.2884778125,38.2017848945313],[116.317891875,38.1849379707031],[116.438741484375,38.2016347480469],[116.477652617188,38.1793495917969],[116.497345,38.2138430000001],[116.51298953125,38.2094863105469],[116.528424101563,38.1894863105469],[116.56298953125,38.1981996894531],[116.581954375,38.2096401191406],[116.592428007813,38.2080922675782],[116.652823515625,38.219702375]]]]}},{"type":"Feature","properties":{"name":"沧县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[117.111846953125,38.4813491035156],[117.078619414063,38.4344838691407],[117.103780546875,38.3893862128907],[117.080738554688,38.3695351386719],[117.0980871875,38.3545864082032],[117.119722929688,38.3294753242187],[117.143551054688,38.318843],[117.141944609375,38.298843],[117.142764921875,38.2886403632813],[117.13185671875,38.2487892890625],[117.137345,38.233843],[117.109874296875,38.2148744941407],[117.1178528125,38.1792653632813],[117.14326296875,38.1697585273438],[117.15142703125,38.1609841132813],[117.12142703125,38.1497585273438],[117.086246367188,38.1268471503907],[117.072198515625,38.1299965644531],[117.025382109375,38.1154860664063],[117.017345,38.1038430000001],[117.002623320313,38.0976601386719],[116.992198515625,38.0999965644532],[116.945245390625,38.0854433417969],[116.906246367188,38.1108388496095],[116.8726184375,38.1032997871094],[116.86326296875,38.1397585273438],[116.834620390625,38.1504738593751],[116.80435671875,38.1436891914063],[116.785694609375,38.1707155585938],[116.771890898438,38.1676210761719],[116.747345,38.1838430000001],[116.741832304688,38.1909841132813],[116.71478640625,38.18698753125],[116.662081328125,38.2077053046875],[116.652823515625,38.219702375],[116.592428007813,38.2080922675782],[116.581954375,38.2096401191406],[116.56298953125,38.1981996894531],[116.528424101563,38.1894863105469],[116.51298953125,38.2094863105469],[116.497345,38.2138430000001],[116.49281375,38.2568679023438],[116.461158476563,38.2676552558594],[116.457345,38.313843],[116.461158476563,38.3300307441406],[116.493531523438,38.3476552558594],[116.511383085938,38.4006996894532],[116.537315703125,38.392622296875],[116.572261992188,38.4209242988282],[116.5959778125,38.4042714667969],[116.617345,38.413843],[116.643170195313,38.4096681953125],[116.66177859375,38.3837050605469],[116.733170195313,38.3980178046876],[116.75216921875,38.4100795722656],[116.782345,38.3976784492188],[116.817345,38.4120619941406],[116.837345,38.4038430000001],[116.78154421875,38.3292739082031],[116.783140898438,38.318452375],[116.771549101563,38.299233625],[116.773160429688,38.2883315253907],[116.760611601563,38.2786452460938],[116.783424101563,38.2693080878906],[116.770621367188,38.2367397285157],[116.77220828125,38.2094863105469],[116.821900664063,38.2496474433594],[116.842711210938,38.2465724921876],[116.847345,38.273843],[116.857345,38.273843],[116.857345,38.283843],[116.874215117188,38.2721938300782],[116.8710559375,38.2580861640626],[116.890714140625,38.2497585273438],[116.93267703125,38.2770839667969],[116.944503203125,38.2942116523438],[116.941221953125,38.308843],[116.947496367188,38.3368325019532],[116.93142703125,38.3479274726563],[116.92326296875,38.3597585273438],[116.90088015625,38.3679274726563],[116.867345,38.353843],[116.861690703125,38.358716046875],[116.887345,38.4038430000001],[116.89166140625,38.4946303535157],[116.938619414063,38.4749062324219],[116.96142703125,38.4897585273438],[117.01326296875,38.5079274726563],[117.02142703125,38.5197585273438],[117.05326296875,38.5279274726562],[117.077345,38.543843],[117.08271609375,38.5292153144532],[117.09197390625,38.4984706855469],[117.111846953125,38.4813491035156]]]]}},{"type":"Feature","properties":{"name":"东光县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.877345,37.843843],[116.842843046875,37.8353688789063],[116.815343046875,37.8415334296875],[116.758053007813,37.8155666328125],[116.74326296875,37.7579274726563],[116.697345,37.733843],[116.689869414063,37.7606935859375],[116.655889921875,37.7556728339844],[116.632345,37.7698744941406],[116.605636015625,37.7537624335938],[116.56298953125,37.7794863105469],[116.496954375,37.7907045722657],[116.467345,37.783843],[116.467345,37.813843],[116.47312625,37.8285512519532],[116.471607695313,37.8388430000001],[116.473082304688,37.848843],[116.471519804688,37.8594130683594],[116.496324492188,37.8695644355469],[116.532003203125,37.915786359375],[116.552877226563,37.9667983222657],[116.557345,38.0238430000001],[116.653077421875,38.0298110175782],[116.672061796875,38.0085622382813],[116.682628203125,37.9991237617188],[116.69435671875,37.9859963203125],[116.823961210938,37.9657997871094],[116.8426575,37.949095685547],[116.84146609375,37.9290956855469],[116.8537903125,37.9180849433594],[116.8520325,37.8885817695313],[116.885714140625,37.8671620917969],[116.877345,37.843843]]]]}},{"type":"Feature","properties":{"name":"海兴县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[117.807764921875,38.2392055488281],[117.791519804688,38.1996681953125],[117.783170195313,38.1680178046876],[117.761217070313,38.1595510078126],[117.765675078125,38.1369826484375],[117.735694609375,38.115493390625],[117.705445585938,38.0732900214844],[117.672340117188,38.0798317695313],[117.612349882813,38.0678542304688],[117.581456328125,38.0739589667969],[117.5507434375,38.0519448066406],[117.55341921875,38.0384096503907],[117.541519804688,38.0196681953125],[117.537345,38.003843],[117.522789335938,37.9948732734375],[117.503531523438,37.9376552558594],[117.497345,37.933843],[117.491676054688,37.942055890625],[117.455650664063,37.93397971875],[117.464136992188,37.9718349433594],[117.40142703125,37.9879274726563],[117.39326296875,38.0097585273438],[117.365235625,38.0202455878906],[117.384283476563,38.0494960761719],[117.35142703125,38.0579274726563],[117.340186796875,38.0742116523438],[117.345225859375,38.0966884589844],[117.317345,38.1038430000001],[117.320704375,38.1204836250001],[117.34287234375,38.1316994453125],[117.347345,38.153843],[117.352896757813,38.1582900214844],[117.361793242188,38.1793959785157],[117.373013945313,38.1984828925782],[117.370582304688,38.218001935547],[117.412345,38.2231960273438],[117.491275664063,38.2133791328126],[117.562183867188,38.2294850898438],[117.577486601563,38.2275820136719],[117.60302859375,38.2383449531251],[117.601085234375,38.2539833808594],[117.615538359375,38.2882900214844],[117.719429960938,38.2745729804688],[117.761793242188,38.2582900214844],[117.787345,38.2538430000001],[117.807764921875,38.2392055488281]]]]}},{"type":"Feature","properties":{"name":"河间市"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.451519804688,38.5764479804688],[116.443170195313,38.5580178046875],[116.423394804688,38.543843],[116.443170195313,38.5296681953126],[116.457393828125,38.4927846503907],[116.5132825,38.4817409492188],[116.55088015625,38.5056093574219],[116.561519804688,38.4780178046875],[116.587345,38.473843],[116.5933996875,38.4608486152344],[116.621612578125,38.4770217109376],[116.639620390625,38.453559796875],[116.620523710938,38.4306642890625],[116.617345,38.413843],[116.5959778125,38.4042714667969],[116.572261992188,38.4209242988282],[116.537315703125,38.392622296875],[116.511383085938,38.4006996894532],[116.493531523438,38.3476552558594],[116.461158476563,38.3300307441406],[116.457345,38.313843],[116.44197390625,38.3184706855469],[116.429522734375,38.3598220039063],[116.392345,38.3568337226563],[116.333961210938,38.3615248847656],[116.318668242188,38.3437734199219],[116.192056914063,38.3794008613282],[116.18271609375,38.3584706855469],[116.17197390625,38.3492153144532],[116.162667265625,38.3384157539063],[116.141510039063,38.3401149726563],[116.102535429688,38.3183693671876],[116.017345,38.3338430000001],[116.021881132813,38.3493056464844],[116.032896757813,38.358452375],[116.030069609375,38.3861440253907],[116.043233671875,38.4091213203125],[116.0132434375,38.4221279121094],[116.033365507813,38.4388430000001],[116.021881132813,38.4483803535156],[116.010621367188,38.474349591797],[115.91713015625,38.4910097480469],[115.932808867188,38.5183803535157],[115.937345,38.533843],[115.928819609375,38.5541469550782],[115.957345,38.573843],[115.973975859375,38.5497585273438],[116.00326296875,38.5579274726563],[116.032623320313,38.5806825996094],[116.041998320313,38.56710471875],[116.069581328125,38.5850673652345],[116.102345,38.5777223945312],[116.112345,38.5799636054688],[116.157867460938,38.5697585273438],[116.173585234375,38.5883107734375],[116.169537382813,38.6063637519532],[116.20142703125,38.6197585273438],[116.23326296875,38.6279274726563],[116.24201296875,38.6406020332032],[116.279097929688,38.6647524238282],[116.317672148438,38.6733998847657],[116.34142703125,38.6579274726563],[116.357345,38.653843],[116.380074492188,38.6124318671876],[116.413170195313,38.5996681953125],[116.421519804688,38.5880178046876],[116.451519804688,38.5764479804688]]]]}},{"type":"Feature","properties":{"name":"黄骅市"},"geometry":{"type":"MultiPolygon","coordinates":[[[[117.887345,38.313843],[117.890767851563,38.3260353828125],[117.899537382813,38.3172658515626],[117.887345,38.313843]]],[[[117.887345,38.313843],[117.883985625,38.307202375],[117.857423125,38.293764875],[117.847345,38.273843],[117.839693632813,38.2604201484375],[117.799693632813,38.2754970527344],[117.787345,38.2538430000001],[117.761793242188,38.2582900214844],[117.719429960938,38.2745729804688],[117.615538359375,38.2882900214844],[117.601085234375,38.2539833808594],[117.60302859375,38.2383449531251],[117.577486601563,38.2275820136719],[117.562183867188,38.2294850898438],[117.491275664063,38.2133791328126],[117.412345,38.2231960273438],[117.370582304688,38.218001935547],[117.373013945313,38.1984828925782],[117.361793242188,38.1793959785157],[117.352896757813,38.1582900214844],[117.347345,38.153843],[117.307642851563,38.1603652167969],[117.292027617188,38.1580568671876],[117.242662382813,38.1796291328125],[117.203487578125,38.1738393378906],[117.192095976563,38.2016664863281],[117.15170046875,38.2181996894532],[117.14298953125,38.2294863105469],[117.137345,38.233843],[117.13185671875,38.2487892890625],[117.142764921875,38.2886403632813],[117.141944609375,38.298843],[117.143551054688,38.318843],[117.119722929688,38.3294753242187],[117.0980871875,38.3545864082032],[117.080738554688,38.3695351386719],[117.103780546875,38.3893862128907],[117.078619414063,38.4344838691407],[117.111846953125,38.4813491035156],[117.09197390625,38.4984706855469],[117.08271609375,38.5292153144532],[117.077345,38.543843],[117.08298953125,38.5481996894531],[117.097345,38.583843],[117.11326296875,38.5879274726563],[117.14267703125,38.6070839667969],[117.147345,38.613843],[117.183170195313,38.6180178046876],[117.220518828125,38.6465407539063],[117.231519804688,38.6180178046876],[117.245186796875,38.6082228828126],[117.235875273438,38.561108625],[117.259386015625,38.5564638496094],[117.29279421875,38.5701918769532],[117.302115507813,38.5571865058594],[117.343170195313,38.5680178046875],[117.357345,38.5877956367188],[117.374132109375,38.5643727851562],[117.393170195313,38.5780178046875],[117.40314578125,38.5919350410157],[117.48187625,38.6158522773438],[117.529386015625,38.6064638496094],[117.547345,38.613843],[117.567896757813,38.5954811835938],[117.622061796875,38.4985622382813],[117.642628203125,38.4691237617188],[117.687784453125,38.3981179023438],[117.735714140625,38.3444777656251],[117.828048125,38.3060732246094],[117.860240507813,38.3235683417969],[117.887345,38.313843]]]]}},{"type":"Feature","properties":{"name":"孟村回族自治县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[117.192095976563,38.2016664863281],[117.203487578125,38.1738393378906],[117.242662382813,38.1796291328125],[117.292027617188,38.1580568671876],[117.307642851563,38.1603652167969],[117.347345,38.153843],[117.34287234375,38.1316994453125],[117.320704375,38.1204836250001],[117.317345,38.1038430000001],[117.291519804688,38.1080178046875],[117.248580351563,38.1210622382813],[117.232345,38.1178554511719],[117.219386015625,38.120415265625],[117.1805871875,38.1054506660157],[117.143526640625,38.0470754218751],[117.171724882813,38.0077321601563],[117.187613554688,38.0108718085938],[117.205943632813,37.95054221875],[117.153780546875,37.9402346015625],[117.123170195313,37.9596681953126],[117.061519804688,37.9680178046875],[117.053170195313,37.9796681953125],[117.027345,37.993843],[117.03312625,38.0085512519531],[117.030865507813,38.0238430000001],[117.03314578125,38.0392726875],[117.011529570313,38.06843284375],[117.017345,38.1038430000001],[117.025382109375,38.1154860664063],[117.072198515625,38.1299965644531],[117.086246367188,38.1268471503907],[117.12142703125,38.1497585273438],[117.15142703125,38.1609841132813],[117.14326296875,38.1697585273438],[117.1178528125,38.1792653632813],[117.109874296875,38.2148744941407],[117.137345,38.233843],[117.14298953125,38.2294863105469],[117.15170046875,38.2181996894532],[117.192095976563,38.2016664863281]]]]}},{"type":"Feature","properties":{"name":"南皮县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.747345,38.1838430000001],[116.771890898438,38.1676210761719],[116.785694609375,38.1707155585938],[116.80435671875,38.1436891914063],[116.834620390625,38.1504738593751],[116.86326296875,38.1397585273438],[116.8726184375,38.1032997871094],[116.906246367188,38.1108388496095],[116.945245390625,38.0854433417969],[116.992198515625,38.0999965644532],[117.002623320313,38.0976601386719],[117.017345,38.1038430000001],[117.011529570313,38.06843284375],[117.03314578125,38.0392726875],[117.030865507813,38.0238430000001],[117.03312625,38.0085512519531],[117.027345,37.993843],[116.99791140625,37.9711244941407],[117.02744265625,37.9483315253906],[117.021607695313,37.9088430000001],[117.024561796875,37.888843],[117.0216028125,37.8688088203126],[117.027345,37.8338430000001],[116.96281375,37.8401894355469],[116.957345,37.8338430000001],[116.947345,37.8338430000001],[116.947345,37.843843],[116.937345,37.843843],[116.877345,37.843843],[116.885714140625,37.8671620917969],[116.8520325,37.8885817695313],[116.8537903125,37.9180849433594],[116.84146609375,37.9290956855469],[116.8426575,37.949095685547],[116.823961210938,37.9657997871094],[116.69435671875,37.9859963203125],[116.682628203125,37.9991237617188],[116.672061796875,38.0085622382813],[116.653077421875,38.0298110175782],[116.557345,38.0238430000001],[116.547345,38.0238430000001],[116.5526184375,38.0443862128907],[116.583013945313,38.0375722480469],[116.59435671875,38.0539968085938],[116.622345,38.0477223945313],[116.632345,38.0499636054688],[116.643013945313,38.0475722480469],[116.663746367188,38.0775966621094],[116.6601965625,38.0934206367188],[116.61970828125,38.1085707832031],[116.649176054688,38.1289150214844],[116.695094023438,38.1460964179688],[116.74267703125,38.1770839667969],[116.747345,38.1838430000001]]]]}},{"type":"Feature","properties":{"name":"青县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.8740246875,38.6829872871094],[116.912628203125,38.6781862617188],[116.946763945313,38.6913075996094],[117.030987578125,38.7017836738282],[117.041793242188,38.6882900214844],[117.054156523438,38.6783901191407],[117.048980742188,38.6367787910157],[117.071793242188,38.6082900214844],[117.082896757813,38.5993959785157],[117.091793242188,38.5882900214844],[117.097345,38.583843],[117.08298953125,38.5481996894531],[117.077345,38.543843],[117.05326296875,38.5279274726562],[117.02142703125,38.5197585273438],[117.01326296875,38.5079274726563],[116.96142703125,38.4897585273438],[116.938619414063,38.4749062324219],[116.89166140625,38.4946303535157],[116.887345,38.4038430000001],[116.855797148438,38.4115920234376],[116.837345,38.4038430000001],[116.817345,38.4120619941406],[116.782345,38.3976784492188],[116.75216921875,38.4100795722656],[116.733170195313,38.3980178046876],[116.66177859375,38.3837050605469],[116.643170195313,38.4096681953125],[116.617345,38.413843],[116.620523710938,38.4306642890625],[116.639620390625,38.453559796875],[116.621612578125,38.4770217109376],[116.5933996875,38.4608486152344],[116.587345,38.473843],[116.59197390625,38.4792153144531],[116.6080871875,38.4930995917969],[116.622667265625,38.5100221992188],[116.643961210938,38.5083107734375],[116.667232695313,38.5353224921876],[116.640347929688,38.5584889960938],[116.6627746875,38.5684963203125],[116.661163359375,38.5885195136719],[116.67271609375,38.5984706855469],[116.68197390625,38.6092153144532],[116.72271609375,38.6184706855469],[116.74197390625,38.6292153144531],[116.77752078125,38.6450771308594],[116.7619153125,38.6585195136719],[116.762745390625,38.6688430000001],[116.761944609375,38.6788430000001],[116.762750273438,38.6888808417969],[116.757345,38.7438430000001],[116.864273710938,38.7393386054688],[116.861085234375,38.7137026191407],[116.8740246875,38.6829872871094]]]]}},{"type":"Feature","properties":{"name":"任丘市"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.197345,38.923843],[116.201881132813,38.8783803535156],[116.24302859375,38.8605361152344],[116.241793242188,38.8484194160157],[116.262808867188,38.8393056464844],[116.271881132813,38.8183803535157],[116.334068632813,38.8091176582031],[116.405455351563,38.7781569648438],[116.421881132813,38.7583803535156],[116.427345,38.7538430000001],[116.423985625,38.717202375],[116.361373320313,38.685805890625],[116.357345,38.653843],[116.34142703125,38.6579274726563],[116.317672148438,38.6733998847657],[116.279097929688,38.6647524238282],[116.24201296875,38.6406020332032],[116.23326296875,38.6279274726563],[116.20142703125,38.6197585273438],[116.169537382813,38.6063637519532],[116.173585234375,38.5883107734375],[116.157867460938,38.5697585273438],[116.112345,38.5799636054688],[116.102345,38.5777223945312],[116.069581328125,38.5850673652345],[116.041998320313,38.56710471875],[116.032623320313,38.5806825996094],[116.00326296875,38.5579274726563],[115.973975859375,38.5497585273438],[115.957345,38.573843],[115.95052859375,38.6283864570313],[115.967803984375,38.6422182441407],[115.951695585938,38.6986257148438],[115.953013945313,38.7092031074219],[115.941612578125,38.7285976386719],[115.947345,38.7538430000001],[115.970787382813,38.7598586250001],[116.003082304688,38.8066347480469],[116.033638945313,38.8180690742188],[116.03119265625,38.828989484375],[116.04349734375,38.868696515625],[116.037686796875,38.8946169257813],[116.083814726563,38.9118764472657],[116.110191679688,38.9059633613282],[116.117345,38.933843],[116.155733671875,38.9432729316407],[116.197345,38.923843]]]]}},{"type":"Feature","properties":{"name":"肃宁县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[115.937345,38.533843],[115.932808867188,38.5183803535157],[115.91713015625,38.4910097480469],[116.010621367188,38.474349591797],[116.021881132813,38.4483803535156],[116.033365507813,38.4388430000001],[116.0132434375,38.4221279121094],[116.043233671875,38.4091213203125],[116.030069609375,38.3861440253907],[116.032896757813,38.358452375],[116.021881132813,38.3493056464844],[116.017345,38.3338430000001],[116.00978640625,38.3240492988281],[115.955220976563,38.3321120429687],[115.874342070313,38.2717458320313],[115.86298953125,38.2994863105469],[115.847345,38.303843],[115.832896757813,38.3393959785156],[115.76259890625,38.3594960761719],[115.751890898438,38.3581642890625],[115.742545195313,38.3698378730469],[115.722589140625,38.3581081367187],[115.697345,38.3638430000001],[115.7060559375,38.3751308417969],[115.725675078125,38.3902724433594],[115.709014921875,38.4474135566406],[115.7286340625,38.4625551582032],[115.74170046875,38.4794863105469],[115.77298953125,38.4881996894532],[115.78170046875,38.5094863105469],[115.817345,38.5238430000001],[115.860094023438,38.5133425117188],[115.873013945313,38.5320558906251],[115.902843046875,38.5253688789063],[115.937345,38.533843]]],[[[115.853922148438,38.5360353828126],[115.857345,38.5238430000001],[115.845152617188,38.5272658515625],[115.853922148438,38.5360353828126]]]]}},{"type":"Feature","properties":{"name":"吴桥县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.56298953125,37.7794863105469],[116.605636015625,37.7537624335938],[116.632345,37.7698744941406],[116.655889921875,37.7556728339844],[116.689869414063,37.7606935859375],[116.697345,37.733843],[116.671793242188,37.7193959785157],[116.662896757813,37.6982900214844],[116.610709257813,37.6330336738281],[116.5601575,37.6023281074219],[116.532896757813,37.5682900214844],[116.516236601563,37.5549489570313],[116.507345,37.543843],[116.444464140625,37.5043508125],[116.428678007813,37.4699648261719],[116.397906523438,37.5044057441407],[116.372515898438,37.5270912910156],[116.362628203125,37.5591237617188],[116.340260039063,37.569389875],[116.327345,37.583843],[116.3335559375,37.6061537910157],[116.365953398438,37.6194130683594],[116.361529570313,37.6493544746094],[116.37298953125,37.6581996894532],[116.38170046875,37.6894863105469],[116.410894804688,37.7288661933594],[116.423160429688,37.7383315253907],[116.421519804688,37.7494130683595],[116.449659453125,37.7609291816407],[116.467345,37.783843],[116.496954375,37.7907045722657],[116.56298953125,37.7794863105469]]]]}},{"type":"Feature","properties":{"name":"献县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.192056914063,38.3794008613282],[116.318668242188,38.3437734199219],[116.333961210938,38.3615248847656],[116.392345,38.3568337226563],[116.429522734375,38.3598220039063],[116.44197390625,38.3184706855469],[116.457345,38.313843],[116.461158476563,38.2676552558594],[116.49281375,38.2568679023438],[116.497345,38.2138430000001],[116.477652617188,38.1793495917969],[116.438741484375,38.2016347480469],[116.317891875,38.1849379707031],[116.2884778125,38.2017848945313],[116.292896757813,38.158452375],[116.281881132813,38.1493056464844],[116.265455351563,38.1295290351562],[116.223604765625,38.1113784003907],[116.212633085938,38.0981703925781],[116.163487578125,38.1119106269531],[116.14275515625,38.0782912421875],[116.100616484375,38.0825868964844],[116.062808867188,38.0683803535156],[116.047345,38.0638430000001],[116.028189726563,38.0936659980469],[116.04298953125,38.1181996894531],[116.043863554688,38.1481996894532],[115.987345,38.1259804511719],[115.932081328125,38.1477053046875],[115.92298953125,38.1594863105469],[115.897345,38.163843],[115.88603640625,38.1698000312501],[115.90037234375,38.2017128730469],[115.861905546875,38.2219765449219],[115.853892851563,38.2603932929688],[115.839464140625,38.267993390625],[115.82541140625,38.2992714667969],[115.847345,38.303843],[115.86298953125,38.2994863105469],[115.874342070313,38.2717458320313],[115.955220976563,38.3321120429687],[116.00978640625,38.3240492988281],[116.017345,38.3338430000001],[116.102535429688,38.3183693671876],[116.141510039063,38.3401149726563],[116.162667265625,38.3384157539063],[116.17197390625,38.3492153144532],[116.18271609375,38.3584706855469],[116.192056914063,38.3794008613282]]]]}},{"type":"Feature","properties":{"name":"新华区"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.857345,38.283843],[116.857345,38.273843],[116.847345,38.273843],[116.847345,38.283843],[116.857345,38.283843]]],[[[116.857345,38.283843],[116.86170046875,38.3194863105469],[116.867345,38.353843],[116.90088015625,38.3679274726563],[116.92326296875,38.3597585273438],[116.93142703125,38.3479274726563],[116.947496367188,38.3368325019532],[116.941221953125,38.308843],[116.944503203125,38.2942116523438],[116.93267703125,38.2770839667969],[116.890714140625,38.2497585273438],[116.8710559375,38.2580861640626],[116.874215117188,38.2721938300782],[116.857345,38.283843]]]]}},{"type":"Feature","properties":{"name":"盐山县"},"geometry":{"type":"MultiPolygon","coordinates":[[[[117.248580351563,38.1210622382813],[117.291519804688,38.1080178046875],[117.317345,38.1038430000001],[117.345225859375,38.0966884589844],[117.340186796875,38.0742116523438],[117.35142703125,38.0579274726563],[117.384283476563,38.0494960761719],[117.365235625,38.0202455878906],[117.39326296875,38.0097585273438],[117.40142703125,37.9879274726563],[117.464136992188,37.9718349433594],[117.455650664063,37.93397971875],[117.491676054688,37.942055890625],[117.497345,37.933843],[117.47922,37.9213295722656],[117.424346953125,37.8398415351563],[117.316046171875,37.8664430976563],[117.307345,37.853843],[117.291881132813,37.8493056464844],[117.262608671875,37.838305890625],[117.207345,37.8439394355469],[117.152345,37.8383339667969],[117.06341921875,37.8473976875],[117.027345,37.8338430000001],[117.0216028125,37.8688088203126],[117.024561796875,37.888843],[117.021607695313,37.9088430000001],[117.02744265625,37.9483315253906],[116.99791140625,37.9711244941407],[117.027345,37.993843],[117.053170195313,37.9796681953125],[117.061519804688,37.9680178046875],[117.123170195313,37.9596681953126],[117.153780546875,37.9402346015625],[117.205943632813,37.95054221875],[117.187613554688,38.0108718085938],[117.171724882813,38.0077321601563],[117.143526640625,38.0470754218751],[117.1805871875,38.1054506660157],[117.219386015625,38.120415265625],[117.232345,38.1178554511719],[117.248580351563,38.1210622382813]]]]}},{"type":"Feature","properties":{"name":"运河区"},"geometry":{"type":"MultiPolygon","coordinates":[[[[116.847345,38.273843],[116.842711210938,38.2465724921876],[116.821900664063,38.2496474433594],[116.77220828125,38.2094863105469],[116.770621367188,38.2367397285157],[116.783424101563,38.2693080878906],[116.760611601563,38.2786452460938],[116.773160429688,38.2883315253907],[116.771549101563,38.299233625],[116.783140898438,38.318452375],[116.78154421875,38.3292739082031],[116.837345,38.4038430000001],[116.855797148438,38.4115920234376],[116.887345,38.4038430000001],[116.861690703125,38.358716046875],[116.867345,38.353843],[116.86170046875,38.3194863105469],[116.857345,38.283843],[116.847345,38.283843],[116.847345,38.273843]]]]}}]}

河北沧州的 不谢

谢谢。赶在2018年来之前给我了。我打算再没有，就在2018年自己描，这下子不需要。省下的时间，可以做pyecharts的地图扩展。


[FR]: Add Checkpoints to Sync for Holesky

Describe your idea
Offer various Checkpoint, for the user to choose from, for the Holesky testnet

Considered Alternatives?
--
Additional Context
--
Acknowledgment

[X] I looked through the feature requests/enhancements planned for this project before submitting a new idea

https://eth-clients.github.io/checkpoint-sync-endpoints/#holesky Now available for Holesky 🙏


Insufficient code coverage for lib/os/fdtable.c

Is your enhancement proposal related to a problem? Please describe.
Code coverage reports indicate we have a lack of unit tests for the code in lib/os/fdtable.c
Lines: 37/96 38.5%
Functions: 9/18 50%
Branches: 11/54 20.4%
At bare minimum we need 100% function coverage and greater than 90% line coverage, ideally 100% across the board.
The command line I am using for gathering coverage data is:
sanitycheck -n -p qemu_x86 -p mps2_an385 --coverage --coverage-platform qemu_x86 --coverage-platform mps2_an385 --gcov-tool /opt/zephyr-sdk/i586-zephyr-elf/bin/i586-zephyr-elf-gcov -T tests/kernel/ -T tests/lib/ -T tests/posix/ -j12 -x=CONFIG_ASSERT=n

Fixes should be backported to the v1.14 branch

It doesn't look like we have any dedicated unit tests for this code at all, the number we have are only because the APIs are used by some fs tests.
Need to write some tests under tests/lib/fdtable to prove that these APIs work. There may be bugs lurking.

A ticket for particular sub-issue was created: https://github.com/zephyrproject-rtos/zephyr/issues/25407, to hopefully be addressed for 2.3.

seems to be addressed.


Add names counter in the account details page

Please describe the problem that your request should resolve.

Describe the solution you'd like

Add names counter in the account details page.
Is it already possible to achieve the same outcome in any other way? If so, how?

Additional context

This counter is not implemented on the MDW side. I will request it

MDW Tracking https://github.com/aeternity/ae_mdw/issues/1629


[Helm] Fix typo in  ingress netpol

Hi. Is it possible to merge this in to bugfix, please?

Hi. Is it possible to merge this into bugfix, please? I know it will need rebase but it would be nice to have it available.

Sure, but I will create new PR. Will send a link here

@kiblik @cneill @Maffooch @mtesauro
New PR to bugfix - https://github.com/DefectDojo/django-DefectDojo/pull/10898


postgresql9[34]: Update documentation links

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same formula update/change?
[x] Have you built your formula locally prior to submission with brew install <formula> (where <formula> is the name of the formula you're submitting)?
[x] Does your submission pass brew audit --strict --online <formula> (after doing brew install <formula>)?
[x] Does your submission adhere to Versions "Acceptable Formulae" guidelines?

These links aren't technically broken, but they are outdated.

:+1:


errors while building avs device sdk

Briefly summarize your issue:

->I have downloaded the avs device sdk into the source directory and run the cmake command from the build directory(as  shown in the https://github.com/alexa/avs-device-sdk/wiki/Linux-Reference-Guide)
->But iam getting errors related to ssl and nghttp2 library linking.
What is the expected behavior?
->avs device sdk should be built and run
What behavior are you observing?
errors while building the as device sdk.
Tell us about your environment:
What version of the AVS Device SDK are you using?
  <x.y.z>

->Iam using avs device sdk 1.6 version.
Tell us what hardware you're using:

[ ] Desktop

Tell us about your OS (Type & version):

[ ] Linux

here iam attaching the screeen shot of the errors that i got.
->can  anyone please help me out in solving the errors.

hi again  @kclchan,  i have built curl with version 7.54  but libcurl is still 7.47.
so, can you please say how to upgrade libcurl to  7.54 version.
->As you said,this might be the problem.
->so, can you please say how to upgrade libcurl to  7.54 version. and help me to solve the problem.

Hi @bharath4e9, looks like there are two versions of libcurl in your system and the linker is picking the older version of the libcurl instead of v7.54.  I would like to confirm with you to see if you have done all these steps for curl as described in https://github.com/alexa/avs-device-sdk/wiki/Ubuntu-Linux-Quick-Start-Guide:
cd ~/sdk-folder/third-party
wget http://curl.haxx.se/download/curl-7.54.0.tar.bz2
tar -xvjf curl-7.54.0.tar.bz2
cd curl-7.54.0
./configure --with-nghttp2=/usr/local --with-ssl
make
sudo make install
sudo ldconfig
Especially the last step with "sudo ldconfig"?
Also can you do the command below to help us find out which libcurl and the order in which they are used:
ldconfig -v -N | grep 'libcurl|:'
Once that's known, you can modify /etc/ld.so.conf.d and run "ldconfig" to change the order of the library path so that the new libcurl library will be used first.

hi @kclchan, thanks for your reply, i will try to modify the /etc/ld.so.conf.d  file and will update you...thanks

sdk has been successfully built now,  but when i run the make all integration test,i got the errors as shown in the screenshots

can you please help to fix those issues in step 5 and step 6

Hi @bharath4e9,
Could you take a look at https://github.com/alexa/avs-device-sdk/issues/196 and see if that solves your issue.
Thanks,
Benny

Closing for now.  Please re-open if you need further assistance.


XHuman smplx params optimize

From Here, it seems that you don't optimize the smplx params of XHumans, so does it mean that we don't need to run deca, Hand4whole and fit.py for XHumans dataset and directly use pkl files in original XHumans dataset like here
Also, I'd like to know the camera Rt you use for XHumans dataset. For example, in your provided examples like 00034, to render smplx mesh, we should use the smplx params in "smplx_optimized/smplx_params/*.json", right? What's the corresponding cameras? Rt in cameras.npz or we should use virtual camera parameters like in Custom dataset? It seems that you don't use Rt of cameras.npz after using it in here.

Hi,

For XHumans dataset, I emperically found that not optimizing SMPL-X parameters gives better results, so I do not optimize it. I guess that is because SMPL-X parameters of XHumans are from multi-view loss, while optimization on ExAvatar's side is done from single-view loss. However, we need joint_offset and face_offset. Hence, we pick a single sequence from the training set to get them, available in here.

For XHuamns dataset, you can ignore any Custom dataset-related stuff. For the rendering, you can use the SMPL-X parameters, provided in the dataset. I use cameras.npz like here.

Wow, thanks for so quick response.
What's exact command to get joint_offset and face_offset from a single sequence? Sorry, I did not find it following your link.  Run fit.py using config.py/XHumans.py in XHumans branch?

You can see this: https://github.com/mks0601/ExAvatar_RELEASE/tree/main/fitting#xhumans-videos
set dataset='XHumans' in config,py and run python fit.py --subject_id 00034


Fix #34746: Add a size limit for variable size when pretty printing exception report

Introduces a maximum variable size threshold (512KB) for pretty printing in exception reports, use the default pprint for variables smaller than the threshold
Uses repr for variables exceeding the size limit
Significantly reduces the time and memory used to create an exception report when a frame with a large variable raises an exception.

[UPDATE]

Seems like the sys.getsizeof call is not accurate. If we need accurate information, we can use some of the third party libraries to deeply evaluate the value of an object but that becomes really slow, I think it would be best to switch entirely to reprlib with indentation instead of pprint.
Please let me know your thoughts!

Please let me know if we can continue with this approach I will add the limits for other data structures as well if so!

Please let me know if we can continue with this approach I will add the limits for other data structures as well if so!

Hello! Thank you for your contribution. I checked the proposed code and it seems to be in the right direction.
In order for this PR to be listed as "needing review" in the Django Development Dashboard, please remember to set the proper Trac flags in the ticket as described in the PR checklist when this is ready for review. You may also want to assign the ticket to yourself!

Hey @nessita, thanks for the go ahead!
One of the problems I found is the old tests seem to be relying on some of behaviours with pprint that are not the same with reprlib. For eg, rprlib doesn't raise an exception when there is one and instead just returns a generic string with the class name of the object and ID so a few of the test cases are failing right now.
I am assuming it's best to just retain old behavior so I'm trying to work around that.
Another thing I wanted to change was the trim message.
If a string of length 6000 is trimmed to fit 4096 limit, the message still says: <trimmed 6000 byte string>
isn't it better to say:
..1004 more items or something like that basically the count indicates the remaining elements instead of the total count. Or should I retain the current behaviour?

@felixxm I think the PR is ready for review!

@felixxm I think the PR is ready for review!

Hey @keerthivasansa, thank you again for your contribution!
There is no need to mention people directly when a PR is ready for a re-review, reviewers will get to this when they have some availability. As I posted in my previous comment and in the ticket, the proper procedure to get a re-review is described in these docs.
You need to unset the relevant ticket flags so this PR gets added back to the "patches needing review" section of the Django Developer Dahsboard .
Let me know if you have any question!

Gotcha, thanks!
Sorry this is my first time using Django Trac system so I don't know how to operate it. Hopefully it will be smoother in future contributions.
I have unset the "needs test" and "needs improvement" flags assuming that's what I have to do.

Hey @nessita, thanks for the go ahead! One of the problems I found is the old tests seem to be relying on some of behaviours with pprint that are not the same with reprlib. For eg, rprlib doesn't raise an exception when there is one and instead just returns a generic string with the class name of the object and ID so a few of the test cases are failing right now.
I am assuming it's best to just retain old behavior so I'm trying to work around that.
Another thing I wanted to change was the trim message. If a string of length 6000 is trimmed to fit 4096 limit, the message still says: <trimmed 6000 byte string>
isn't it better to say: ..1004 more items or something like that basically the count indicates the remaining elements instead of the total count. Or should I retain the current behaviour?

Hello @keerthivasansa!
I'm starting to review this today so I will provide answers/advice as I go thru it.

@keerthivasansa Thank you for your patience. We've been busy with the Django 5.1 Alpha release but I'll go back to this PR in a few weeks.
In the meantime, could you please update your work with the latest changes from main? A passing test suite would also help!
/remind me about this PR in 3 weeks

@nessita Cool, i'll merge with the latest changes now!

@nessita The tests were failing because the implementation of reprlib differed between Python 3.11 and 3.10, there was no way to customize the fillvalue in Python 3.10 reprlib. So I have copied the latest reprlib implementation, customized it to work for our case. Does that sound good? But unfortunately it adds a lot of complexity and burden to the code I guess :(, let me know if you have better ideas!

Is this still active?

Is this still active?

Yes, it is still active, I need to "seat" with this PR to provide an answer to the author. Would you like to provide a code review and/or suggestions to the latest comment?

@nessita we can't have our own replrlib in here, this will force the community to be responsible for testing the implementation of repllib (instead of python community) and will not receive updates, introduce redundancy and force the community to maintain it
if you want use reprlib, know first what changed between 3.10 and 3.11 and handle both cases, check python version, handle depending on the current version, using their own respective reprlibs

Hello @keerthivasansa! Thank you so much for your patience. I'm now back at reviewing this work. I have started catching up with our previous conversations (because in all honestly, I forgot a bit about the context), and I think I understand where we are at now. In order to answer this question:

the implementation of reprlib differed between Python 3.11 and 3.10 [...] So I have copied the latest reprlib implementation, customized it to work for our case. Does that sound good?

I need to ask you these questions:

Could you please provide the traceback of a failing test in 3.11 and 3.10 to understand the difference in each version? (the test results from this PR are no longer available to review that myself).
In an ideal word, the tests would also use reprlib to build the expected results, and so whichever difference that reprlib has between Python versions would be "encapsulated" in reprlib itself. Does this make sense? Is there a reason why this is not the case?

In general, copying and duplicating an implementation of a library or function that is provided by Python is not the best path forward. Before deciding on doing that, we should be absolutely sure that there is no other alternative. To help you finding more alternatives, I would need the answers from items above.
My advice would be to provide answers to the items above and undo the copy of the latest reprlib implementation, so we can see the errors and what are the alternatives in that case. Let me know if you have further questions, and please unset the ticket flags when this work is ready for re-review!
Thanks again for waiting for our review. :trophy:

The only difference is we can't provide fillvalues to the reprlib meaning,
In 3.11
We get something like
[1, 2, 3, 4,.... <trimmed 100 byte string>]
But in 3.10 it's always
[1, 2, 3, 4,....]
No way to change what's shown. While this is very trivial and can be easily be handled by only customising fill value for supported versions, this becomes an issue because in lot of the tests it's looking to check if <trimmed sentence is present with the final output. So it will always fail.
Or ig we could replace '...' to our custom string after reprlib processes it, but this doesn't seem like a proper solution.

Can I take over if this is no longer being done?

Can I take over if this is no longer being done?

Hello @LeOndaz! Thank you for your interest in helping with Django. This PR is active in that the author is waiting on some feedback and assistance in how to move this forward. I haven't had the time to invest a few hours with this PR to propose the best solution, but this needs some investigation and, ideally, a solution that does not copy the reprlib code and that it would not require "if python version" guards.
Do you think you could help by reviewing this PR and proposing ideas/solutions to the pending questions?

Hello @keerthivasansa! Thank you so much for your patience. I'm now back at reviewing this work. I have started catching up with our previous conversations (because in all honestly, I forgot a bit about the context), and I think I understand where we are at now. In order to answer this question:

the implementation of reprlib differed between Python 3.11 and 3.10 [...] So I have copied the latest reprlib implementation, customized it to work for our case. Does that sound good?

I need to ask you these questions:

Could you please provide the traceback of a failing test in 3.11 and 3.10 to understand the difference in each version? (the test results from this PR are no longer available to review that myself).
In an ideal word, the tests would also use reprlib to build the expected results, and so whichever difference that reprlib has between Python versions would be "encapsulated" in reprlib itself. Does this make sense? Is there a reason why this is not the case?

In general, copying and duplicating an implementation of a library or function that is provided by Python is not the best path forward. Before deciding on doing that, we should be absolutely sure that there is no other alternative. To help you finding more alternatives, I would need the answers from items above.
My advice would be to provide answers to the items above and undo the copy of the latest reprlib implementation, so we can see the errors and what are the alternatives in that case. Let me know if you have further questions, and please unset the ticket flags when this work is ready for re-review!
Thanks again for waiting for our review. 🏆

Thanks @nessita for responding, I'm gonna give you a quick idea, There're no failing tests as the problem is not related bugs, but rather, inconsistency, fillvalue was added in Python 3.11 and there's no way to customize it in 3.10, which means that if we customize it using fillvalue (python version check here), we will end up with two different representations for users with 3.10/3.11.
The traceback for 3.10 would end up something like (object1, ..., objectN)
The traceback for 3.11 would be (object1, ourCustomThingy, objectN)
While there's a depth paramter for pprint, it still doesn't cover what we want to do, my approach would be modify our pprint to truncate the string before passing it to pformat, as I'm assuming we want the same message format for all users, however, this is a debugging message and if we can afford to have it a bit different for some python versions, I believe it makes sense in some way, there're also some good 3rd party options, but I'm against adding dependencies tbh, if we were, I would definitely add rich library since that's a quality one, if we're gonna have our implemenntation, our pprint (should) detect big objects (in memory size) and truncate, now, we got into another problem which is, there's no builtin way to check for an object size, and we will have to implement one manually (probably using gc module), but still, there're many maintenance burdens being added and I'm not sure what can we tolerate in here,
And the code below is an auto-generated code to show the idea I have, this is a debug mode code, but it doesn't account for the memory-size, only the object length, we
def represent(obj, max_depth=10, recursive_repr="...", max_items=100, seen=None):
    """
    Represents any Python object, focusing on class instances and handling recursion,
    nested structures, truncation, and instance representation with their arguments.

    :param obj: The object to represent.
    :param max_depth: Maximum depth for nested structures.
    :param recursive_repr: String to use for recursive representations.
    :param max_items: Maximum number of items to display in collections (lists, dicts, etc.).
    :param seen: Set of seen objects to track recursion.
    :return: String representation of the object.
    """
    if seen is None:
        seen = set()

    # Handle recursive references
    if id(obj) in seen:
        return recursive_repr

    seen.add(id(obj))

    # Handle dictionaries or any Mapping
    if isinstance(obj, collections.abc.Mapping):
        if max_depth <= 0:
            return "{...}"
        items = []
        for i, (k, v) in enumerate(obj.items()):
            if i >= max_items:
                items.append("...")
                break
            items.append(f"{represent(k, max_depth-1, recursive_repr, max_items, seen)}: {represent(v, max_depth-1, recursive_repr, max_items, seen)}")
        return f"{{{', '.join(items)}}}"

    # Handle lists, tuples, sets, and any Iterable
    if isinstance(obj, collections.abc.Iterable) and not isinstance(obj, (str, bytes, collections.abc.Mapping)):
        if max_depth <= 0:
            return "[...]" if isinstance(obj, list) else "(...)" if isinstance(obj, tuple) else "{...}"
        container_repr = []
        for i, item in enumerate(obj):
            if i >= max_items:
                container_repr.append("...")
                break
            container_repr.append(represent(item, max_depth - 1, recursive_repr, max_items, seen))
        if isinstance(obj, list):
            return f"[{', '.join(container_repr)}]"
        elif isinstance(obj, tuple):
            return f"({', '.join(container_repr)})"
        else:
            return f"{{{', '.join(container_repr)}}}"

    # Handle class instances (objects)
    if hasattr(obj, '__class__') and not isinstance(obj, type):
        return represent_class_instance(obj)

    # Handle other objects by calling their repr
    return pformat(obj)

def represent_class_instance(instance):
    """Represents a class instance with its constructor arguments."""
    cls = instance.__class__
    try:
        sig = inspect.signature(cls.__init__)
        bound_arguments = sig.bind_partial(instance)
        bound_arguments.apply_defaults()
        positional = []
        keywords = []
        for name, value in bound_arguments.arguments.items():
            if name == 'self':  # Skip 'self'
                continue
            default = sig.parameters[name].default
            if default is inspect.Parameter.empty:
                positional.append(represent(value))
            else:
                keywords.append(f"{name}={represent(value)}")
        return f"{cls.__name__}({', '.join(positional + keywords)})"
    except (ValueError, TypeError):
        return f"<instance of {cls.__name__}>"

There're also dependencies for checking memorysize accurately, pympler
What do you think?


tinc: 1.0.34 -> 1.0.35, 1.1pre16 -> 1.1pre17 (security update)

Motivation for this change
Critical security update (CVE-2018-16737, CVE-2018-16738, CVE-2018-16758).
Should be backported to release-18.03 and release-18.09 as well.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Annoucement is here: https://www.tinc-vpn.org/pipermail/tinc/2018-October/005311.html

Verified the build locally. Lets see if ofborg is also happy :)
@GrahamcOfBorg build tinc tinc_pre

Success on x86_64-darwin (full log)
Attempted: tinc, tinc_pre
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/rnhf9i5m351mbl6zanpf4ysxqi5q9f35-tinc-1.1pre17/sbin
patching script interpreter paths in /nix/store/rnhf9i5m351mbl6zanpf4ysxqi5q9f35-tinc-1.1pre17
moving /nix/store/rnhf9i5m351mbl6zanpf4ysxqi5q9f35-tinc-1.1pre17/sbin/* to /nix/store/rnhf9i5m351mbl6zanpf4ysxqi5q9f35-tinc-1.1pre17/bin
gzipping man pages under /nix/store/wva383q83r030b6nfwyha1q75f83pn0c-tinc-1.1pre17-man/share/man/
strip is /nix/store/9xjkb4xz0b5lmizij9ppxy7lkxdxhx6b-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/wva383q83r030b6nfwyha1q75f83pn0c-tinc-1.1pre17-man
strip is /nix/store/9xjkb4xz0b5lmizij9ppxy7lkxdxhx6b-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/vyg73ajc72g9lqb95zli222gg4qzzfjy-tinc-1.1pre17-info
/nix/store/7k94r0xamv6mfbs3ahsprqxwh5hbz9b1-tinc-1.0.35
/nix/store/rnhf9i5m351mbl6zanpf4ysxqi5q9f35-tinc-1.1pre17

Success on aarch64-linux (full log)
Attempted: tinc, tinc_pre
Partial log (click to expand)
gzipping man pages under /nix/store/snyjhdr1w8ydgjm0yg0ndqsvv0f38qxr-tinc-1.1pre17-man/share/man/
strip is /nix/store/428gs2z4b8f9byvghzlpbjwjb3a7jwxx-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/snyjhdr1w8ydgjm0yg0ndqsvv0f38qxr-tinc-1.1pre17-man
checking for references to /build in /nix/store/snyjhdr1w8ydgjm0yg0ndqsvv0f38qxr-tinc-1.1pre17-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/rsrlmd5ry0dzz4wbz1bpd9pswhah5f6x-tinc-1.1pre17-info
strip is /nix/store/428gs2z4b8f9byvghzlpbjwjb3a7jwxx-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/rsrlmd5ry0dzz4wbz1bpd9pswhah5f6x-tinc-1.1pre17-info
checking for references to /build in /nix/store/rsrlmd5ry0dzz4wbz1bpd9pswhah5f6x-tinc-1.1pre17-info...
/nix/store/m1x0qfazpddd21g3qdvgsbc60ass8bhr-tinc-1.0.35
/nix/store/6dd787lzl32n9vp6pkam8hb7pnl6h0fp-tinc-1.1pre17

Success on x86_64-linux (full log)
Attempted: tinc, tinc_pre
Partial log (click to expand)
gzipping man pages under /nix/store/lk513wl25851f8f1cyf3rp7x6yh0gpa5-tinc-1.1pre17-man/share/man/
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/lk513wl25851f8f1cyf3rp7x6yh0gpa5-tinc-1.1pre17-man
checking for references to /build in /nix/store/lk513wl25851f8f1cyf3rp7x6yh0gpa5-tinc-1.1pre17-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/0q1ff0z6c8pgb3mvvzd8yk8xmsp97p50-tinc-1.1pre17-info
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/0q1ff0z6c8pgb3mvvzd8yk8xmsp97p50-tinc-1.1pre17-info
checking for references to /build in /nix/store/0q1ff0z6c8pgb3mvvzd8yk8xmsp97p50-tinc-1.1pre17-info...
/nix/store/fpiagibzs8pfi4snjvqn0h9fyyw3a1cc-tinc-1.0.35
/nix/store/7k0brbbzz5bg1z15fg07n8ikh7m43j6v-tinc-1.1pre17

Thank you @pacien :+1:

Backported in 859a4d3 & 21293d2


Errors installing tekton resources defined in default collection

There appears to be an ordering and/or timing problem when creating the default collection. Sometimes, Pipeline and Task resources cannot be created by the collection controller, presumably because the Tekton operator has not finished processing the Install resource yet (this causes Tekton to register the Pipeline and Task CRDs).  The error can happen in several ways, some of which include (from the Kabanero operator log):
"error":"no matches for kind \"Task\" in version \"tekton.dev/v1alpha1\""

or
"error":"the server could not find the requested resource"

Eventually, the CRDs are registered, but the operator does not seem to always detect this, and so future loops of the collection controller continue to receive the error.  We should investigate whether we can fix the timing here... perhaps if the Kabanero controller is going to create a Install, it could wait until the Pipeline and Task CRDs are available before trying to create the Collection instance.  It may be that the particular collection does not define a Pipeline or Task, but that's a harder problem to solve.

This may all be a moot point after #71 is resolved, if we move to pipelines 0.5.  The install process appears to be different and is done at the cluster level.

With issue #71 now resolved, the tekton.dev CRDs should be available well before a Kabanero instance is created, and the problem reported here should not occur.


fix fix update core for merge-on-write table

Proposed changes
Issue Number: close #xxx

After alter table, update table will coredump.
0# doris::signal::(anonymous namespace)::FailureSignalHandler(int, siginfo_t*, void*) at /root/code/doris/be/src/common/signal_handler.h:413
1# 0x00007FFA87761400 in /lib64/libc.so.6
2# doris::TabletSchema::column(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) const at /root/code/doris/be/src/olap/tablet_schema.cpp:938
3# doris::Tablet::fetch_value_by_rowids(std::shared_ptrdoris::Rowset, unsigned int, std::vector<unsigned int, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, COWdoris::vectorized::IColumn::mutable_ptrdoris::vectorized::IColumn&) in /root/code/doris/output/be/lib/doris_be
4# doris::segment_v2::SegmentWriter::fill_missing_columns(std::vector<COWdoris::vectorized::IColumn::mutable_ptrdoris::vectorized::IColumn, std::allocator<COWdoris::vectorized::IColumn::mutable_ptrdoris::vectorized::IColumn > >&, std::vector<bool, std::allocator > const&, bool) at /root/code/doris/be/src/olap/rowset/segment_v2/segment_writer.cpp:467
5# doris::segment_v2::SegmentWriter::append_block_with_partial_content(doris::vectorized::Block const*, unsigned long, unsigned long) at /root/code/doris/be/src/olap/rowset/segment_v2/segment_writer.cpp:409
6# doris::segment_v2::SegmentWriter::append_block(doris::vectorized::Block const*, unsigned long, unsigned long) at /root/code/doris/be/src/olap/rowset/segment_v2/segment_writer.cpp:526
7# doris::BetaRowsetWriter::_add_rows(doris::vectorized::Block const*, std::unique_ptr<doris::segment_v2::SegmentWriter, std::default_deletedoris::segment_v2::SegmentWriter >&, unsigned long, unsigned long) at /root/code/doris/be/src/olap/rowset/beta_rowset_writer.cpp:446
8# doris::BetaRowsetWriter::_flush_single_block(doris::vectorized::Block const*, int, long*, std::shared_ptrdoris::TabletSchema) at /root/code/doris/be/src/olap/rowset/beta_rowset_writer.cpp:540
9# doris::BetaRowsetWriter::flush_memtable(doris::vectorized::Block*, int, long*) at /root/code/doris/be/src/olap/rowset/beta_rowset_writer.cpp:521
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.25 seconds
stream load tsv:          511 seconds loaded<PHONE_NUMBER>9 Bytes, about 139 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          32 seconds loaded 861443392 Bytes, about 25 MB/s
insert into select:          30.2 seconds inserted 10000000 Rows, about 331K ops/s
storage size:<PHONE_NUMBER>0 Bytes


InputImage::_read_image bug ?

I think I found a bug with InputImage::read_image(), read_tiles() and read_scanines()
When you use the paramater xStride, in some situation OIIO ignore the value of the xStride paramater.
Let suppose I have a allocated buffer of unsigned char that will containt RGBA values.
When I call read_image with the format UCHAR and a xStride of 4 bytes to read by example a bmp file that contains RGB, the values goes in my buffer at the right place (OIIO skip the alpha channel in my buffer). But if I'm reading by example an OpenEXR image that only have the red channel and the data in the file are float, OIIO ignore my stride value.
I think the problem is, if the pixel size in the image file is equal to the xStride value, OIIO ignore the stride and write the data in continious memory.
Note: I tried with version 1.8

yes my buffer is unsigned char.
the format paramater is UCHAR.
the xStride is 4.
The image file internal data is float and the image only have the red channel.
OIIO convert the float to UCHAR write in my buffer without using the stride.
I can repro the same behaviour with an image file that only have the Red and Green channel
but the image file internal data is half-float.

OK, I think I understand. Looking into it...

Yes, I think I see how this happens. It's late, I will look at it more tomorrow. Should be an easy fix.

Fix proposed in #2108

Not sure why this issue didn't close when we merged the fix of #2108. But we did, so closing the ticket now.


Help needed for account registration

I'm sorry to ask, but I'm stack since two days with the account registration. I always get the AUTHENTICATION_FAILURE error.
An example of the data that I get is as follows:
mnemonic: oblige ball total smoke thumb drop hope ocean price move zero fold
derivationPath m/48'/0'/0'/0
privateKey: 6641784ffab8acf92ca67a128efdd73530d7e00a2c919c546468abc96cee6e73
publicKey: 03d9bf5972bcc3505272cb6e16ef799333a963919801fed2dc36855d86832fb104
address: 3J6EjhU4V8MdHZtkqFNPTXbkJ8R4QTqsVf
message: Peach Registration<PHONE_NUMBER>995
sha256Message: 6442bfecd377faf52cdd469e0af42f375466b9315629cfe6adf991fc69e4c3e1
signature G4EFz0dSv3UE6nCPeo2/pvZ1PJnKvbFwkOLCxiSP1WcTQuAi57/KyT1SES/TDiyiAEu263/PVfMr39nvPGQRUv8=

If I verify the signature on Sparrow Wallet or here it's marked as valid signature.
The body of my POST request to /v1/user/register/ is:
{
  "message":"Peach Registration<PHONE_NUMBER>995",
  "signature":"G4EFz0dSv3UE6nCPeo2/pvZ1PJnKvbFwkOLCxiSP1WcTQuAi57/KyT1SES/TDiyiAEu263/PVfMr39nvPGQRUv8=",
  "publicKey":"03d9bf5972bcc3505272cb6e16ef799333a963919801fed2dc36855d86832fb104",
  "uniqueId":"1694395422995836002"
 }

So the only wrong step I can think about is the sha256 hash of the message, that I do as follows:
crypto.createHash('sha256').update(message).digest('hex') but this should be pretty standard in nodejs/jvascript. I also tried with .digest('base64'). Without success.
This is my full code. I was able to sign for bity.com and receive and send a transaction on with a slightly different version, so I'm quite confident it should not contain an error, but I might be wrong.

plugins/bitcoin.client.js

import { networks, initEccLib, payments } from 'bitcoinjs-lib';
import * as bip39 from 'bip39';
import * as BIP32Factory from 'bip32';
// A replacemenet of tiny-secp256k1
// compatible with environments that do not support WebAssembly
import ecc from '@bitcoinerlab/secp256k1';
initEccLib(ecc);
const bip32 = BIP32Factory.default(ecc);
import bitcoinMessage from 'bitcoinjs-message';
import * as crypto from 'crypto';

export default defineNuxtPlugin(nuxtApp => {

  // Get the bitcoin mainnet network from bitcoinjs
  const network = networks.bitcoin;

  // Generate a random 12 words mnemonic
  const mnemonic = bip39.generateMnemonic();

  // Get the seed from the mnemonico
  const seedBuffer =  bip39.mnemonicToSeedSync(mnemonic);

  // Generate the keys and the address for the first p2wpkh address in the wallet
  const derivationPath = `m/48'/0'/0'/0`;

  const root = bip32.fromSeed(seedBuffer, network);

  const child = root.derivePath(derivationPath);

  // The private key
  const privateKeyHex = child.privateKey.toString('hex');

  // The publick key
  const publicKeyHex = child.publicKey.toString('hex');

  // The address
  const { address } = payments.p2sh({
    redeem: payments.p2wpkh({
      pubkey: child.publicKey,
      network,
    }),
    network,
  });

  // Convert the private key from hex string to buffer
  // to be used in the message sign function
  const privateKeyBuffer = Buffer.from(privateKeyHex, "hex");

  // Generate the message to sign
  const timeStamp = Date.now();
  const message = `Peach Registration ${timeStamp}`;

  // Hash the message to sign with sha256 alghoritm
  const sha256Message = crypto.createHash('sha256').update(message).digest('hex');

  // Generate the signature
  const signature =  bitcoinMessage.sign(sha256Message , privateKeyBuffer).toString('base64');

  // Generate the unique id to be associate with the account on Peach
  const randomId = Math.floor(100000 + Math.random() * 900000);
  const uniqueId = `${timeStamp}${randomId}`;

  // Register the peach account
  const proxy = (isDeployed) ? '' : 'https://corsproxy.io/?';
  const account = await $fetch(`${proxy}https://api.peachbitcoin.com/v1/user/register/`, {
    method: 'POST',
    body: {
      message: message,
      signature: signature,
      publicKey: publicKeyHex,
      uniqueId: uniqueId
    },
    async onRequestError({ request, options, error }) {
      console.log("[fetch request error]", request, error);
    },
    async onResponseError({ request, response, options }) {
      console.log("[fetch response error]", request, response.status, response.body);
    },
  });

  console.log('account', account)
})

Do you happen to notice where the error might be? Maybe I'm just missing something elementary.
Thank you a lot for your help.

Yes, the signature format supported is currently hex, but indeed following bitcoin signing standards we should migrate to base64.
I will add support for it alongside hex and let you know once this has been implemented.

I fought const signature = bitcoinMessage.sign(sha256Message , privateKeyBuffer).toString('hex'); should have solved the issue.
But with this body:
{"message":"Peach Registration<PHONE_NUMBER>350","signature":"1c43d1cbeedfadbc3c7750c70335e96a7536921e27ebea9d82cdacd15e4f753fc055e3e9b6379a9bf1919c468f8b29ae160a3334868b347b4cb3040968e6d7cafe","publicKey":"0208b858e1af1ecaee4992cfede6c2895ccd8e5e910a8ae24532bb5eb68e686ee3","uniqueId":"1696921392350223530"}

I still get 500 | AUTHENTICATION_FAILURE.
Shouldn't I get 400 | INVALID_SIGNATURE  instead?

Ah, I see what the problem is. It's not a bitcoin message but a simple one, signed using ECDSA
If you also use bitcoinjs-lib that would correspond to BIP32Interface.sign

It worked. Thanks a lot for your help!


Provide your download page in English Language?

the download link:https://drive.google.com/open?id=1iAchJ8EmAExkl9o1qKfIbwZsSO3mMM78

Thanks for the above link @chenjun2hao


Zero out entire struct in GetStartupInfoA

As I've understand GetStartupInfoA, the caller always passes a pointer to uninitialized memory, and the function will then fill in the values. Before this change, GetStartupInfoA read the value of cb as an input parameter to get the length of the struct. In my program that part of the memory was uninitialized and happened to be 0, so the rest of the values were never zeroed out, leading to garbage data being returned in the other field.
This change make sure to zero out the entire struct, and then sets cb to the actual length of the struct.
Lifted from #39

(copy-paste of my review comment from before, just for history reasons)
By the way, I checked and I now believe that STARTUPINFOA has never changed in size, so my worries about callers passing in an undersized buffer or something like that are unfounded. And further I checked and at least win2k's kernel32.dll does exactly what you've done here, so I think this is correct.


Translation issue on the customers  order section in the arabic locale

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
Master
Issue Description
Order  translation is missing in the Arabic locale
Preconditions
Setup Bagisto from the Master Repository
Steps to reproduce

Visit the admin end
Change the app locale to Arabic.
Go to the customers -> select orders.

Expected Result
Should not be any translation issue on the customer order section in the Arabic locale.
Actual Result
Order  translation is missing in the Arabic locale.
Screenshots

Additional context
No response

@jitendra-webkul
Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.


Add php 8.2/8.4

We only actively support the latest PHP version. Thanks for reminding me that I need to update it to 8.4 👍

On 8.2 is also a conflict for public const string.

Indeed, we don't support PHP 8.2


⚠ Samsung has degraded performance

In b6b245a, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2884 ms

Resolved: Samsung performance has improved in 66eb5df.


Extend JMeter to also download data files before executing a test

Currently the jmeter service only downloads the jmx file and executes it.
This is limiting the use of JMeter because its not possible to reference any e.g: data files
We should exted jmeter.conf.yaml to reference additional files that should be downloaded into the same local directory in the jmeter pod so that the .jmx file can reference them without an issue

We should exted jmeter.conf.yaml to reference additional files that should be downloaded into the same local directory in the jmeter pod so that the .jmx file can reference them without an issue

Would it also work if jmeter-service downloads everything that's in the jmeter folder (including sub-folders)?

Yes. That would even be better. And - a feature that every service could benefit from. In the end we say that files should be uploaded to a specific folder in the config repo. If there would be an easy way to "clone" either the full repo or get that partial directory tree it would be great help and would also reduce the need to additoinally configure which files to download!

@grabnerandi it looks like you are working on this? If so I would like to assign it to you :)


Survey Event UI Base (EXPOSUREAPP-4807, 4808 )

Draft PR for 4807, 4808,
SurveyConsentfragment & related, SurveyCard in RiskDetails, etc.
Basis UI & logic implementation.
Futher PR will come for link handling, etc.
to Test:
bring your smartphone to a high risk state & open the riskDetailsFragment. Select the new card...
Screens/Overview:

Nice Job! Tested on Samsung S8 (Android 10) and on a Huawei P30 (Android 10), looking good so far 👍


Add BUILD files for extraction and claiming for C++ [phab:D197]

Created by zarko at 2015-04-16 22:09:08:

schroederc accepted this revision at 2015-04-16 22:12:04

zarko closed via commit ae4340ac77e86aab98651bcdd069b84b0bb75a44 at 2015-04-16 22:15:50


Anonymous object creation

how to get from:
string strExpression = "x => new { x.Ido, x.OtdName }";
such expression:
Expression<Func<T, object>> result = x => new {x.Ido, x.OtdName };
I need this to select specific fields in Generic Repository:
public async Task<List<object>> GetList1(Expression<Func<T, object>> selectFields)
        {
            IQueryable<T> query = _dbSet;
            IQueryable<object> result;

            result = query.Select(selectFields);

            return await result.AsNoTracking().ToListAsync();
        }

For the same field works like this:
 string strExpression = "x.Ido";
            var interpreter = new Interpreter();
            Expression<Func<T, object>> expression = interpreter.ParseAsExpression<Func<T, object>>(whereExpression, "x");

How to do this for multiple fields?:
string strExpression = "x.Ido, x.OtdName";
For:
public async Task<List<object>> GetList1(Expression<Func<T, object>> selectFields)
        {
            IQueryable<T> query = _dbSet;
            IQueryable<object> result;

            result = query.Select(selectFields);

            return await result.AsNoTracking().ToListAsync();
        }

You are right, unfortunately for now anonymous object are not supported.
I will think about this for a future release...any help is appreciated 😃

I had a look, and it seems quite difficult: the anonymous type has to be defined at runtime, and to do that, you need to add a custom dynamic assembly to the current app domain, and then add the new anonymous type to that custom assembly. Also, that custom assembly must be unloaded when it's no longer needed, to avoid memory bloat. Also, the anonymous type must define fields, properties, a default constructor, and possibly a ToString() method, otherwise it might not be understood by Entity Framework.
Creating a dynamic assembly doesn't seem possible with netstandard 2.0, only with netstandard 2.1.
I found a project that does most of it, except that it doesn't unload the dynamic assembly, and it's also not compatible with netstandard.
https://github.com/dotlattice/LatticeUtils/blob/master/LatticeUtils/AnonymousTypeUtils.cs

Thank you @metoule  for the interesting analysis! I agree with your conclusion. For now let's keep the issue open.

If we make "x => new { x.Ido, x.OtdName }" return an Expando instead of anonymous type, the end result would be close enough for such use case.

Another possibility, depending on the outcome desired for this, is to return an ExpandoObject.  This would allow consuming code to be able to reference it as dynamic, or be passed to other interpreters since there is already some support for
I do have a decent amount of experience in building classes at run time, especially for the simple classes that are created as anonymous types.  Looking into how those are actually compiled out
var o = new { Prop1 = int.MaxValue, Prop2 = string.Empty };
ends up getting compiled out to a class as follows
public class <>f__AnonymousType0`2<Prop1, Prop2>
{
   private readonly Prop1<Prop1>i__Field;
   private readonly Prop2 <Prop2>i__Field;

    public <>f__AnonymousType0`2(Prop1 Prop1, Prop2 Prop2)
    {
        <Prop1>i__Field = Prop1;
        <Prop2>i__Field = Prop2;
    }

    public int Prop1 { get => <Prop1>i__Field; }
    public string Prop2 { get => <Prop2>i__Field; }

    public override string ToString()
    {
//Technically calls ToString() with a null check, but this shows the string format.
          return $"{{ Prop1: {Prop1}, Prop2: {Prop2} }}"
    }

    //Had to use ILDisassembler to get here.
    public override bool Equals(object o)
    {
        return o is <>f__AnonymousType0`2<Prop1, Prop2> a && EqualityComparer<Prop1>.Default.Equals(a.Prop1, Prop1) && EqualityComparer<Prop2>.Default.Equals(a.;
    }
    public override int GetHashCode()
    {
        //This is pretty ugly.  Having a hard time decompiling from MSIL in my head at the moment.
//Long story short, combines hash codes with the results from EqualityComparer<T>.Default
    }
}


Update to Bevy 0.11.0

Update to the new Bevy version.
Diffs look a bit more busy, it's because I ran cargo fmt.

Thank you for updating, didn't realize Bevy Rapier would update so quickly.
Can you please undo the formatting? I am going to address that in a separate commit.

Tested it and it works, thank you for bumping!


how to plot the model like the DCGAN.png ？

what is the tool use?

I didn't draw the figure. The figure is in DCGAN paper.


Application on stack

Description:
I want to add various applications on stack like
-reversal of string
-implement two stacks in an array
(using method 1 divide the space in two halves
method 2 A space efficient implementation)
Checklist:

[ ]I'm a Contributor in GSSoC-ext
[ ] I Want to work on it

Additional Information:
Function calls: Stacks are used to keep track of the return addresses of function calls, allowing the program to return to the correct location after a function has finished executing.
Recursion: Stacks are used to store the local variables and return addresses of recursive function calls, allowing the program to keep track of the current state of the recursion.

not planned


Voice Accessibility

Voice Accessibility
Voice Coding
For context, primarily I use Talon Voice in Visual Studio Code with the Cursorless extension and when browsing on the web I use the Rango extension which is also part of Talon Voice. The main thing it helps with is putting two letter labels on wherever you want to interact.
For a demonstration of Voice Coding with .NET Blazor and Visual Studio Code, see the following video, please note it's fairly long but it does have chapters so you can skip to the parts you are interested in:
Voice Coding with .NET Blazor and Visual Studio Code
Keyboard Shortcuts
This applies to the Aspire dashboard as well as the actual site.
It would be cool if there was a page that listed any keyboard shortcuts that are provided to navigate the site.
I've used these on other sites to create or get copilot to create a Talon Voice script file that maps all the keyboard shortcuts to a voice command. This allows me to navigate the site without using the mouse.
Also I can forget what the keyboard shortcuts are as they become irrelevant at this point.
Here's an example of a script file for the ChatGPT site:
app: msedge.exe
title: /chatgpt|chat gpt/i
-

new chat:     key(ctrl-shift-o)

focus input:    key(shift-esc)

copy code block:    key(ctrl-shift-;)

copy response:    key(ctrl-shift-c)

set instructions:    key(ctrl-shift-i)

toggle sidebar:    key(ctrl-shift-s)

delete chat:    key(ctrl-shift-backspace)

show shortcuts:    key(ctrl-/)

Summary

Suggest adding a keyboard shortcuts section on the website for easy access.
Implement an option to toggle visibility of shortcuts for users who need them.
Ensure the user interface is optimized for voice navigation to reduce cognitive load.
Focus on minimizing navigation complexity for users without mouse access
Tab order that is not in a logical sequence is a no no.
Please note that voice users would never intuitively use a mouse hover to discover something!
When there's an obvious place to have the keyboard focus when a page loads the focus should automatically be there.

Relates to my PR #173 - Talon Voice in Visual Studio Code

@Mark-Phillipson I added a PR to get out-of-the-box support for VScode debugging


Anchor links broken in 3.0.x Markdown specification documents

The anchor links in the Markdown specs for versions 3.0.0, 3.0.1, and 3.0.2 are broken. The links point to camelCase anchors, but the anchors themselves are kebab-case. For instance, in the 3.0.2 spec, the Media Types index link points at the #mediaTypes anchor, but the actual Media Types heading has the anchor #media-types. This issue is present throughout the documents.
There are also some minor naming inconsistencies. I haven't done a thorough check, but I noticed that the OpenAPI Document index link points to the #oasDocument anchor, when the actual anchor is #openapi-document (so even if #oasDocument were changed to #oas-document, the anchor link still wouldn't work).
Not sure if the spec files are autogenerated or written manually. Happy to submit a PR if someone can point me in the right direction.

This is being addressed.   There are some rather thorny logistical challenges involved in terms of change management process and deployment, which is why it's taking so long, but it's being addressed in the PR I linked.

Got it – thanks! Appreciate the quick response and sorry for the dupe.

Consolidating all broken link issues into issue #3054 and PR #3408


Template configuraions for securing web portals

Description:
xml configs listed in document https://apim.docs.wso2.com/en/latest/install-and-setup/setup/security/securing-api-m-web-portals/ need to be templated in deployment.toml
Steps to reproduce:
Affected Product Version:

Environment details (with versions):

OS:
Client:
Env (Docker/K8s):

Optional Fields
Related Issues:

Suggested Labels:

Suggested Assignees:

public fix added with https://github.com/wso2/carbon-kernel/pull/3047


Re-think command storage to associate different implementations of same command with each other

This issue is a continuation of the discussion in #19.
Problem
Poise currently generates multiple command objects per function, corresponding to each command type (prefix, slash, context menu). These command objects are stored completely separate from each other in PrefixFrameworkOptions and ApplicationFrameworkOptions respectively.
This makes it hard to tell which command invocations belong to the same command at runtime, which is needed for many things:

a dashboard for the bot to enable or disable commands: you need to know which command entry in the dashboard a command invocation belongs to (this was the motivator for #19)
help command: to display both slash commands and prefix commands in the help menu (#13), there needs to be a way to avoid displaying commands twice if they have both a prefix and a slash implementation
command cooldowns (#1): cooldowns should apply across invocation types

In #19 we discussed several ideas to redesign how commands are stored in order to fix the issues. But after thinking about each of them and starting to implement a couple in feature branches, none of them seemed great.
I'm currently relatively demotivated to work on this issue because to me it feels like no good solution is in sight. This issue functions as a reminder/placeholder for now, or as a place of discussion for ideas for solutions

By exploring several of the brainstormed design ideas again, the Arc<CommandId> way turned out to be the most straightforward that also addresses all current design issues


Does the Jekyll flash plugin work?

I see you've already integrated the very cool YouTube iframe based plugin. Awesome. But how about  the Flash one? Sad reality for many of us devs is that we still have a ton of Flash based content. In my case, this new site is dedicated to showcasing all my old junk for free, whereas my new sites are all HTML5.
I'll try using the current Jekyll flash plugin and post any results here, but wondered if you've thought of doing an integration directly in your OpenTheme plugins.

I did not have success with this plugin, but embedding Flash directly using swfobject works - I guess if you need to embed your flash in blog posts or something you would be out of luck, but for my purposes embedding directly in the HTML should be fine. Would be great to see a plugin nonetheless, although I understand people don't have a lot of motivation to develop for Flash unless they are in e-learning where it's a bit hard to escape it.

I won't recommend using Jekyll plugins, unless these work in --safe compilation mode. This way you can skip the Jekyll/Gulp process all together and "code/change" your site source directly in GitHub. GitHub will compile the Pages if you are using only supported plugins.


Is it possible for y to be multi-dimensional

In the classifier, is it possible for y to be a vector instead of a single number?

No but you can use a classifier to predict each dimension or you can transform the vector into categories.


Maximum function nesting level

I am hitting a max nesting level on phan 0.8.3 with PHP 7.0.15.
PHP Fatal error:  Maximum function nesting level of '256' reached, aborting! in /Users/chrisdekok/.composer/vendor/etsy/phan/src/Phan/Analysis/ScopeVisitor.php on line 40
PHP Stack trace:
PHP   1. {main}() /Users/chrisdekok/.composer/vendor/etsy/phan/phan:0
PHP   2. require_once() /Users/chrisdekok/.composer/vendor/etsy/phan/phan:2
PHP   3. Phan\Phan::analyzeFileList() /Users/chrisdekok/.composer/vendor/etsy/phan/src/phan.php:30
PHP   4. Phan\Analysis::parseFile() /Users/chrisdekok/.composer/vendor/etsy/phan/src/Phan/Phan.php:107
PHP   5. Phan\Analysis::parseNodeInContext() /Users/chrisdekok/.composer/vendor/etsy/phan/src/Phan/Analysis.php:78
PHP   6. Phan\Analysis::parseNodeInContext() /Users/chrisdekok/.composer/vendor/etsy/phan/src/Phan/Analysis.php:138
PHP   7. Phan\Analysis::parseNodeInContext() /Users/chrisdekok/.composer/vendor/etsy/phan/src/Phan/Analysis.php:138
PHP   8. Phan\Analysis::parseNodeInContext() /Users/chrisdekok/.composer/vendor/etsy/phan/src/Phan/Analysis.php:138
PHP   9. Phan\Analysis::parseNodeInContext() /Users/chrisdekok/.composer/vendor/etsy/phan/src/Phan/Analysis.php:138

That's not a PHP error. That is coming from xdebug. You shouldn't be running Phan with xdebug unless you are actually debugging/profiling it. It slow it down and causes problems like this one.

Perhaps something could be added which disables xdebug in a way like composer did?
https://github.com/composer/composer/blob/20c16f18f542a061aec90988bff250555e5b9576/src/Composer/XdebugHandler.php

It's reasonably simple:
(new \Composer\XdebugHandler(\Composer\Factory::createOutput()))->check();

Rather than stack puke, phan should complain and exit... this behavior just tripped me up too.


Examples v2.0 dashboard

This is the first of several PRs to add new quickstarts for Saturn. Since this is the first, it also includes cleaning up of the repo and removing the cpu and gpu examples. Specifically it:

Has a rewriten readme.md to cover the new structure of each quickstart
Removes the examples-cpu and examples-gpu folders. The materials in these are being migrated to other locations
Adds the first dashboard quickstart. This quickstart now:

Has an updated saturn.json metadata structure.
Removes a lot of the "non-dashboard" material (like pulling from s3), to make it more accessible for people who may not understand those technologies (like s3).
Moves the all of the material required by the quickstart into the git repo itself (like the csv files of data). This will make it substantially easier to maintain the quickstarts since all the material is in one place. Since the quickstarts are often used as examples and other documents outside of the actual Saturn projects, the code instead of just loading from the directory instead pulls from the github URL. it's a little weird but I think this is the best we can to do balance maintainability and usability across all our channels (examples docs, quickstarts, blogs, etc).
Should be our "single canonical example" of how to quickly get a dashboard running in Saturn. We should no longer have a separate "example doc" "examples repo" "saturn-cloud-examples repo" etc etc that we have to maintain, instead it should all just use this one location.

Added a comment about Github URLs vs S3. I tend to lean toward using something like S3 because it avoids showing a "bad pattern" of including data in the Jupyter server. For example, if a user uploads a data file into a Jupyter server, but then creates a cluster or deployment(s) that file won't exist on the other machines. If its S3, all machines would have access without any issues.

I think "storing data on the Jupyter server is a bad habit" is something we should think about. Like, so many of our customers will be used to having data stored right with there code, that making this something we have to train customers out of could be a huge struggle. I don't know if it's possible to instead have this be a more permanent data store, but like I want to make sure we don't put our needs (easy to write the backend for) above the needs of customers. That's kind of tangental to the S3 v GitHub thing.

Per a conversation with @jsignell, I added back the examples-cpu and examples-gpu since we'll still need them for existing enterprise customers. Those folders were added and a note was added to the readme as well.

Worth noting that there's a branch cut from this repo (release-YYYY.MM-DD) cut as part of our standard release process, and that's what's used from customer installs built from that release - it's not impossible to make breaking changes like that, but it has to be coordinated with the release cycle.

The changes in this PR require corresponding changes to Saturn itself and to Saturn's integration tests.
Before I review I want to know...have you and @jsignell talked about that?

Yes, we discussed this!

Okay, as of this morning here is where this PR stands:
Changes since original PR:

CPU and GPU examples have been returned
Any flat files required by the quickstart have been moved to the S3 bucket saturn-public-data in the folder examples/dashboard
The categories key in the saturn.json has been removed from the readme and weight has been added
The dashboard notebook was fixed and now correctly runs
The .gitignore rule to ignore data was readded since that's now going to be in S3

Open items:

Thumbnails - Whether the thumbnails should be left in GitHub with an action to move to S3 or put in S3 directly is unresolved. At this point I am okay with putting them in S3, but I'm not sure where in S3 they should go. If we put them in the saturn-public-data S3 it feels kind of weird since that's like, part of the website UI which feels different than data. If they go in saturn-public-files then I don't have access to this S3 bucket but also do we really want data scientists to have access to and editing prod?

I think besides the thumbnail thing I've covered everyone's comments, but let me know if I've missed anything. Now might be a good time to rereview it.

Also one minor point, my example is failing one test because it has readme.md instead of README.md. I don't believe any of the data science team is on systems that are case sensitive (we all use windows or mac), so if it's possible to have the test be case insensitive without it causing issues I think that would be good. I'm not sure if that would break something down the line though.

Also one minor point, my example is failing one test because it has readme.md instead of README.md. I don't believe any of the data science team is on systems that are case sensitive (we all use windows or mac), so if it's possible to have the test be case insensitive without it causing issues I think that would be good. I'm not sure if that would break something down the line though.

Can we just change the filename? We'd like to be consistent.

Yeah I am not sure if jupyterhub is case sensitive, but README.md is the standard that I've seen elsewhere.

Sure, I'll update it here to README.md

I spoke with @hhuuggoo yesterday and he is setting up a special bucket on S3 specifically for these quickstart thumbnails. So I think the easiest resolution for now will be to explicitly include thumbnail_image_url which will point to an image in the new bucket.
We need to update the schema validator to allow some additional fields to support including project_template options in the saturn.json. To fix this error:
'/home/runner/work/examples/examples/examples/dashboard/.saturn/saturn.json' has the following schema issues: {'environment_variables': ['Missing data for required field.'], 'thumbnail': ['Unknown field.'], 'title': ['Unknown field.'], 'weight': ['Unknown field.']}

On the note about the schema validator, it looks like one of the things it's failing is "environmental_variables". Since my code had none I removed that field, but I just put it back with "environment_variables": {}. Long term could that be set as an optional field?

Long term could that be set as an optional field?

Yeah we can make it optional.

I opened https://github.com/saturncloud/examples/pull/103 to change the schema validation.

Just a note that w.r.t examples, as @jsignell pointed out, Atlas currently by default, will create 1 example project per directory within examples.  We have a few options.

Holding back the next release until we can auto-populate quickstarts in enterprise installations
Disabling example population for users in Atlas, but that means new enterprise users will have a very blank experience
Be ok with creating 3 examples per user instead of 2
Since @jnolis is doing this for quickstarts, we can move this to a separate repository, and that won't impact examples at all.

I am not sure how to say this, but make sure the aspect ratio on the screenshot is 2x1 like

from: https://s3-us-east-2.amazonaws.com/saturn-public-files/dashboard-2x1.png

I vote strongly for 1

I am not sure how to say this, but make sure the aspect ratio on the screenshot is 2x1 like

from: https://s3-us-east-2.amazonaws.com/saturn-public-files/dashboard-2x1.png

All of the thumbnails I've made for quickstarts are 500px by 250 px and so they should be the right aspect ratio. Once the bucket is online I'll drop them all in there and make a note in the readme about it!

Additional changes now make this:
Changes since original PR:

CPU and GPU examples have been returned
Any flat files required by the quickstart have been moved to the S3 bucket saturn-public-data in the folder examples/dashboard
The categories key in the saturn.json has been removed from the readme and weight has been added
The dashboard notebook was fixed and now correctly runs
The .gitignore rule to ignore data was readded since that's now going to be in S3
Thumbnail moved to S3 and saturn.json changed to have thumbnail_image_url

Open items:

Size of the quickstart - I set it to be 4gb, figuring that was enough, but @jsignell suggested it be 10 or higher. I'm not sure what the minimum is but I'll change the config to whatever that is.

"10Gi" is the minimum.
I ran this on integration tests https://github.com/saturncloud/release-images/runs/2088941261?check_suite_focus=true with a few tweaks including that. I'll open up a PR now so that you can pull them in.

@jnolis can you also make sure you are good with https://github.com/saturncloud/examples/pull/103

and https://github.com/saturncloud/examples/pull/104 is the PR I mentioned above


Fix python client SDK generator

What this PR does / why we need it:
Added hard coded python files for both slirp and bridge interface .
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1181
client-python 21
Special notes for your reviewer:
Swagger code-gen doesn't generate code for empty structs. So we need to hard coded the python class files.
Release note:

Add slirp and bridge implementation for python client sdk

This change is

It would be nice to have examples at https://github.com/kubevirt/client-python/tree/master/examples expanded to include interfaces / networks but it shouldn't block the bug fix.


Onboarding Screen not Adapted to EOL

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[X] Bug is not already reported in another issue

Technical details

Device name: Google Pixel 6
Android version: 13
App version: 3.2.0

Describe the bug
Although CWA is EOL, it is still available in the Google Play Store until May 31th.
When installing it from there newly and starting for the first time, the app still shows the deprecated onboarding screen with sentences like:

Let's fight coronavirus together
Turn your smartphone into a coronavirus warning system
Display your test results

The next following screen "Data Privacy" is however up-to-date.
Steps to reproduce the issue
Install CWA from Google Play Store, or delete all app data in an existing installation.
Expected behaviour
Information removed.
Possible Fix
Drop the onboarding screen.
Additional context
This issue is similar to https://github.com/corona-warn-app/cwa-app-android/issues/5920

Under iOS, this is the screen flow:

1.
2.
3.

If you are looking for a 100% clean ramp-down, you will be disappointed.
In the Google Play Store it says:

and the first screen in onboarding continues like this, unaffected by ramp-down.
One positive point:
If you have no exposure warning app installed on Android and then go to Settings > Google > COVID-19 support > Select your region > Germany, it now says "Exposure Notifications isn't currently available" instead of displaying CWA.
So at least it has been removed from there.

Target of this issue is in fact only the CWA code, where at some locations things were overlooked by dev and test. Yours because the tester already had certificates, mine because the tester looked at an already installed app only.

@jkrwdf
I think you mean "adapted" not "adopted" in the subject.

@Ein-Tim
I don't know how much interest there will be in fixing these issues. As you say, the apps will no longer be available soon and no longer supported.  They don't affect the functionality. It's just a case of inconsistent text information in many places.


authentication for prometheus and alertManager

I've recently deployed the monitoring dashboards and components in AWS using the example files available in samples/ingress. The Grafana dashboard includes an authentication layer by default, but Prometheus and alertManager are not protected by any sort of authentication. Is there a way to configure authentication with the Prometheus and alertManager applications? If not, what do you recommend doing to ensure that these applications are not available to unauthenticated users.
For this deployment, we are using the same URL as the Viya applications themselves and it would be great if there was a way to leverage SASLogon so users could login using their SAS credentials to use the monitoring tools.

Hi there,
Updating our samples with more guidance on authentication is in our backlog. It's a bit too much to fully explain here, but what's needed is either to enable HTTP basic authentication in Prometheus or (more robustly) a sidecar authentication proxy container. We do this on OpenShift using their proxy (here).
It's fairly common to add an authentication sidecar proxy, so I'm sure a Google search can get you started. Making this easier either through enhancing our samples and documentation or even direct script support is under consideration, but we don't have a committed date yet.
I hope that helps, even if it isn't a simple flag you could set quite yet.


Evaluate new Numba hooks to support target-specific overload

Recent discussions with Numba upstream developers have led to a proposal to add a way to do target-specific overloads in Numba.
https://github.com/numba/numba/pull/6762
We need to review the PR and propose changes to numba-dppy that will make use of the new feature:

[ ] Evaluate https://github.com/numba/numba/pull/6762
[ ] Create a POC for numba-dppy based on https://github.com/numba/numba/pull/6762
[ ] Review/present findings with Numba upstream community
[ ] Finalize changes to numba-dppy.

@reazulhoque could we discuss this patch from Numba and share understanding?

I am marking this as done. We recently added target-specific overloads in the numba_dpex.experimental.DpexExpKernelTarget. As far as an evaluation goes, we are able to successfully use the feature.


Issue with package_data parameter in setup.py causing installation error

I've encountered an issue during installation where the package_data parameter in the setup.py file is causing an error. It appears that the description in the dictionary should not be an absolute path but should be a list of strings. When I modified it to an arbitrary list of strings, the installation proceeded without any errors.
This is the relevant part of the setup.py file that needs to be addressed:
# Before modification
   package_data  = {
"physo": ["/benchmark/FeynmanDataset/*.csv"]
}

# After modification
package_data={
    'my_module': ['111', '222'],
}

Please consider making this adjustment to ensure smooth installations. Thank you!

??7傔?D3衭{俘俔@@.**|!x??о瞂ftwn&?鼑  箱襒眘)喵  d?輑田璐Vm系y1太莭W棆鲾窓眙霿рd??e菄躞 tXF;驌

It looks like something went wrong with the encoding of the characters of your message, can you elaborate ?

Hi @pronoobe,
Please let me know if this fixed your issue so I can close this thread.
Thanks!

Hi @pronoobe,
I will close this thread now but feel free to re-open if you need further assistance !
Cheers !


Add DNS to the gcloud-java test apps

These apps are useful for testing gcloud-java on the platforms we support.  We should add more tests as new client libraries become available, like DNS.
@mderka, if/when you have time, do you mind adding a bit of really simple DNS code to these apps?

I will have a look at it when I am completely done with the batch implementation.

google-cloud-dns samples are in the google-cloud-java repo.


Silence vmbuilder output

It's creating alot of output, and is primarily relevant for debugging complicated problems, or adding new features which require modifying images. Having an option to silence it, and making that option the default behavior, would help reduce logspam.

Yes, It should have a -v / --verbose

Solved with https://github.com/hioa-cs/IncludeOS/commit/4acf575f8cf5f81468f8c3eeb6e860a2a34ce4b2