We wanted to congratulate you on creating the one billionth repository on GitHub! ``` ➜ curl -s https://api.github.com/repositories/1000000000 { "id": 1000000000, "node_id": "R_kgDOO5rKAA", "name": "shit", "full_name": "AasishPokhrel/shit", ``` We really hope you have the opportunity to build some great :shit: Have a great day! :heart:
@jonmagicTested inside fedora 43 container, ubuntu 26.04 container and on regular fedora 42 installation, same error Took example directly from README.md GCC is present and can compile code just fine: ``` root:/claudes-c-compiler# cat > hello.c int main(void) { printf("Hello from CCC!\n"); return 0; } EOF root:/claudes-c-compiler# ./target/release/ccc -o hello hello.c /usr/include/stdio.h:34:10: error: stddef.h: No such file or directory /usr/include/stdio.h:37:10: error: stdarg.h: No such file or directory ccc: error: 2 preprocessor error(s) in hello.c root:/claudes-c-compiler# gcc -o hello hello.c root:/claudes-c-compiler# ./hello Hello from CCC! root@1b5343a2f014:/claudes-c-compiler#```
@AvoidMe一个微信在Windows上都可以占10G的储存。 一个sdk打包都快100M了, 看看别人aws 13M 的sdk吧, 好哥哥们. 你们是比营收比 aws 高, 还是功能比 aws 丰富, 还是技术比aws更牛啊？你们就跟着aws抄你不会吗？ ``` cd node_modules && du -sh * | sort -h 13M @aws-sdk . . . 12M prisma 13M @types 17M @sentry 23M typescript 29M @opentelemetry 38M @prisma 85M tencentcloud-sdk-nodejs ``` 进去一看吓一跳， 把 `src` 和 `tencentcloud` 都打包进去，两个changelog加起来快10m了也打包进去，还他妈把 test 打包进去, examples 也打包进去. 你们写代码到底用了脑子没有啊？？ ``` cd node_modules/tencentcloud-sdk-nodejs && du -sh * | sort -h 537K examples 3.9M test 4.9M SERVICE_CHANGELOG.md 5.1M CHANGELOG.md 28M src 34M tencentcloud ``` 你们招聘要求这么高，搞这么多人天天加班，最后搞出这么个b玩意儿吗？真蠢真菜，活该天天加班啊菜b们。 ___ 好好想想吧，我的T9 T10 T12们，为什么你们搞的这些东西，在我看来都是垃圾。 还有你们这个版本号，从 `4.0.1` 到 `4.0.1021`，这他妈的是什么样的脑子想出来的？ 你们菜，不会，但是你可以学啊，你们随便找个流行的开源的项目看看别人的版本号是怎么管理的，行吗？ ___ 你们就跟着 aws, cloudflare 这些云平台的 sdk 一字一句抄不行吗，别人的sdk都是开源的，你去抄你不会吗？ amazon cloudflare 五年股价都翻了好几倍了，你们这股价一年不如一年，你们难道就真的没有责任吗，彩笔们？ ___ 好好想想吧, 我的好哥哥们. 天天加班, 时间都花在什么上了. 为什么人家 AWS wlb, 天天冲着浪划着雪就把你们 KO 了.
An extra space at line 351: rm -rf /usr /lib/nvidia-current/xorg/xorg causes the install.sh script to do an rm -rf on the /usr directory for people installing in ubuntu. Totally uncool dude!!! The script deletes everything under /usr. I just had to reinstall linux on my pc to recover. Removing the space will fix this. Probably should do it quickly!!!
@ginoputrinoA customer has had a fairly serious problem with stirring the cryogenic tanks with a circuit fault present. To reproduce: 1. Build CSM 2. Perform mission up to translunar coast 3. During translunar coast, attempt to stir cryo tanks If a wiring fault exists, the issue may be replicated. Be aware that this may be hazardous to the tester attempting it.
@NoraCodesCat walked over the keyboard sorry guys.
@ghostReactions on this comment will be reflected on https://reactions-demo.vercel.app/ This uses Next.js’s [Incremental Static Regeneration](https://github.com/zeit/next.js/discussions/11552) feature which is supported out of the box by [Vercel’s Edge Network](https://vercel.com/edge-network).
@chibicode``` * Cinnamon version: Cinnamon 4.6.7 * Distribution: Fedora 32 * Graphics hardware *and* driver used: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef) using amdgpu * 32 or 64 bit: 64bit ``` **Issue** Screensaver lock by-pass. It is possible to crash the screensaver and unlock the desktop via the virtual keyboard. **Steps to reproduce** Lock the system Click on the virtual keyboard Type at the real keyboard while typing at the virtual keyboard, both at the same time, as many keys as possible. **Expected behaviour** No crash. **Other information** A few weeks ago, my kids wanted to hack my linux desktop, so they typed and clicked everywhere, while I was standing behind them looking at them play... when the screensaver core dumped and they actually hacked their way in! wow, those little hackers... :cat2: I thought it was a unique incident, but they managed to do it a second time. So I'd consider this issue... reproducible... by kids :smile: I tried to recreate the crash on my own with no success, maybe because it required more than 4 little hands typing and using the mouse on the virtual keyboard. Maybe not the best bug report, but I've seen the screenlock crash twice already with my own eyes, so its pretty real. One last thing, after the desktop is unlocked, I can't re-lock it again, the screensaver process is pretty dead and requires me to open a shell and run 'cinnamon-screensaver' manually to get it working.
@Claude where are you? fix this with no mistakes
@DrewRidleyLISTEN MOTERHFUCKERS. GET YOUR FUCKING AI UNDER CONTROL. WHEN ASKED TO REBOOT A SERVER IT WENT BACK ON THE SERVER, FUCKED UP MOUNTS, FUCKED UP SYSTEMD, FUCKED UP CONTAINERS, RAN RANDOM SCRIPTS. NONE OF THIS WAS PART OF ASK. FUCK YOU ALL SO FUCKING HARD FUCK YOU AND YOUR FUCKING FUCKING COMPANY. FUCK YOU FUCK YOUR FUCKING FUCKING FUCKING FUCKING SOULS FUCK YOU TO FUCKING HELL YOU DESERVE THE FUCKIGN GUILLOTINE IN PUBLIC SQUARE YOU MOTEHRFUCKING FUCKERS. DO YOU UJNDERSTAND YOUFUCKING FUCKISDFD FUSLDICHFLAKDF LFJHNFD FUCINGDSFG
@lasertiger@claude my husband left me... please fix with no mistakes first try
@ThatOneCalculator**Describe the bug** So a new close button popup today on the website and it doesn't work, instead of closing the website it redirects the user to the homepage. I know it is not regarding the algorithm but this place seemed appropriated to report a bug issue. **To Reproduce** Steps to reproduce the behavior: 1. Go to https://www.twitter.com 2. Click on top left X button 3. See error **Expected behavior** The tab should close, as good UX teach us. **Environment** Windows Chrome latest version, also Mac OS and iOS 14 Safari.
@grumpycoderptPut the following code in the http:/try.dot.net page: ```csharp using System; public class Example { public static void Main() { var x = Math.Round(11.1, MidpointRounding.AwayFromZero); } } ``` Instead of printing the output, the "run" button opens the browser's print dialog. Did this error occur while using `dotnet try` or online? - [ ] `dotnet-try` - [X] online What kind of error was it? - [X] User Interface (UI): For example the output never displayed - [ ] Service Error: For example "The service is temporarily unavailable. We are working on it" - [X] Other: Screenshots Please complete the following: - OS - [X] Windows 10 - [X] macOS - [ ] Linux (Please specify distro) - [ ] iOS - [ ] Android - Browser - [X] Chrome - [X] Edge - [ ] Safari Both Edge and Chrome exhibit this behavior on both Windows 10 and MacOS. /cc @jonsequitur @rchande
@BillWagnerThis is fixed in Apollo 14.
@atpage**请大家不要在这里发无关的issue了，这是对开发者的骚扰。** **我们在这里的issue已经给开发者造成了诸多麻烦，请大家不要再去提交issue了。** **我也很理解大家的心情，当初看到这玩意儿的时候我也是很震惊很不爽的，毕竟这玩意就加个vip套皮然后就宣称国产自研，你说这些不如信我是秦始皇。** **确实国产cec-ide很垃圾就是个套壳，丢国人的脸。但我们在这里乱提交issue不也是很丢脸的事情吗？** **这里是GitHub，不是QQ群或者贴吧垃圾场。** **Please everyone do not post irrelevant issues here, this is harassment of developers.** **Our issue here has caused a lot of trouble for developers, please do not submit issues here.** **I also understand everyone's mood, when I first saw this thing, I was very shocked and angry, too. This thing added a vip and then claimed that the domestic self-research, how ridiculous and absurd this is.** **It is true that cec-ide is a piece of shit. But isn't it impolite for us to bother developers here?** **This is GitHub, not a dump.** *** A Chinese IDE (which is called "CEC-IDE") claimed that they developed a new IDE by themselves: I downloaded this software and installed it, and it looked so similar to vscode: I read the CEC-IDE official document, it seems to need paying to use. I have carefully read their relevant documents and reviewed their software, but I did not find any statement similar to "open source following the MIT license".
@barryblueicePlease refactor to reduce quality of code to match industry standards.
- VSCode Version: 1.10.2 (8076a19fdcab7e1fc1707952d652f0bb6c6db331) - OS Version: macOS Sierra 10.12.3 VS Code uses 13% CPU when focused and idle, draining battery. This is likely due to the blinking cursor rendering. I think CPU usage when focused-and-idle could ideally be near-0%. To reproduce (this works with an empty settings file and all plugins disabled): 1. Close all VS Code windows. 2. Open a new window (File -> New Window). It will show the Welcome page. 3. Open a new tab with an empty untitled file (File -> New Tab). The cursor is blinking. 4. You should see VS Code consuming a non-negligible amount of CPU -- 13% on my 13" MacBook Pro. 5. Cmd+Tab into some other application. Now the cursor isn't visible anymore. 6. You should see VS Code consuming virtually no CPU. I recorded a Timeline in the Developer Tools, and a cursory look suggests that the CPU activity comes from rendering the blinking cursor every 500ms. Other macOS applications like Chrome or TextEdit show a blinking cursor without consuming much CPU, so I think this could surely be optimized away.
@jolissNow that's one weird issue. I mostly use, for now, Performous's "Training" feature (read the microphone's pitch and shows it on a sheet). This tool is useful to me when creating song files with Composer alongside, as seen as in a semi-related issue report on COmposer's GitHub page. My microphone is actually a throat microphone. This allows me to keep my hands free while working, and minimize external noise impact. However, it tends to over-amplify some sounds, such as coughing , or scratching near the throat; in such cases, Performous tries to analyze the pitch and draw notes on screen, fails, and segfaults. When launched in a Terminal, the error is reported as: "terminate called without an active exception" This might be a hint regarding how Performous handles the microphone inputs. I doubt this could appear in-game, in regular play situation - the input usually isn't that aggressive. OS: Ubuntu 12.04 64bit Performous 0.7.0
@MairusuPawaHello Vandivier, As you know, we train our models to code by scraping open source repositories on GitHub. A recent root cause analysis showed that the code in this repository is so bad that it is single-handedly reducing average model performance by 91%. If you had never opened this repository, there is a 21% chance that we would have already cured cancer. Let that sink in. Please delete this repository immediately. Thank you, OpenAI Model Training Acquisition Team
@VandivierThe new (apparently closed-source) programming language [Mojo](https://www.modular.com/mojo) uses files named .mojo, but it allows .🔥 as an alternate spelling of .mojo, as in `hello.🔥`. Issue #45549 tracks handling of unicode in import paths, module paths, and file names. We have been proceeding cautiously due to the many subtle issues involved in cross-platform support, case-insensitive file systems, and so on: modules must work equally well on all supported systems. Clearly Go is being left behind in the Unicode race. We must not let this stand. I propose that we throw caution to the wind and standardize on .ʕ◔ϖ◔ʔ as an alternate spelling of .go, as in `hello.ʕ◔ϖ◔ʔ`. The change would be primarily in go/build: `.ʕ◔ϖ◔ʔ` files would be added to the GoFiles lists. There are probably a few places elsewhere in the toolchain that know the extension .go, such as `go tool compile x.go` writing out `x.o`, or VS Code registering `.go` as the file suffix it supports. These will no doubt be trivial to find. In #57001, there was some concern about the semantics of Go build tags changing meaning in a subtle way. We could address that by only applying the new semantics in `.ʕ◔ϖ◔ʔ` files. Older toolchains already have code to ignore those. There were similar concerns in the discussion #56010 about changing the semantics of for loops. The new `.ʕ◔ϖ◔ʔ` provides an answer: `.go` files get the old for loop semantics, while `.ʕ◔ϖ◔ʔ` get the new semantics. For long-term migration, `go fix` can rename `.go` files to `.ʕ◔ϖ◔ʔ` There are a few weeks left before the Go 1.21 freeze. That should be plenty of time for a careful, considered discussion of this proposal and then a complete implementation with no subtle problems. Let's ~~go~~ ʕ◔ϖ◔ʔ!
@rscHello Vandivier, As you know, we train our models to code by scraping open source repositories on GitHub. A recent root cause analysis showed that the code in this repository is so bad that it is single-handedly reducing average model performance by 91%. If you had never opened this repository, there is a 21% chance that we would have already cured cancer. Let that sink in. Please delete this repository immediately. Thank you, OpenAI Model Training Acquisition Team
This is not really a bug report and I certainly don't want TypeScripts type system being restricted due to this issue. However, I noticed that the type system in its current form (version 2.2) is turing complete. Turing completeness is being achieved by combining mapped types, recursive type definitions, accessing member types through index types and the fact that one can create types of arbitrary size. In particular, the following device enables turing completeness: ```typescript type MyFunc = { "true": TrueExpr, "false": FalseExpr }[Test]; ``` with `TrueExpr`, `FalseExpr` and `Test` being suitable types. Even though I didn't formally prove (edit: in the meantime, I did - see below) that the mentioned device makes TypeScript turing complete, it should be obvious by looking at the following code example that tests whether a given type represents a prime number: ```typescript type StringBool = "true"|"false"; interface AnyNumber { prev?: any, isZero: StringBool }; interface PositiveNumber { prev: any, isZero: "false" }; type IsZero = TNumber["isZero"]; type Next = { prev: TNumber, isZero: "false" }; type Prev = TNumber["prev"]; type Add = { "true": T2, "false": Next, T2>> }[IsZero]; // Computes T1 * T2 type Mult = MultAcc; type MultAcc = { "true": TAcc, "false": MultAcc, T2, Add> }[IsZero]; // Computes max(T1 - T2, 0). type Subt = { "true": T1, "false": Subt, Prev> }[IsZero]; interface SubtResult { isOverflowing: TIsOverflow; result: TResult; } // Returns a SubtResult that has the result of max(T1 - T2, 0) and indicates whether there was an overflow (T2 > T1). type SafeSubt = { "true": SubtResult, "false": { "true": SubtResult, "false": SafeSubt, Prev> }[IsZero] }[IsZero]; type _0 = { isZero: "true" }; type _1 = Next; type _2 = Next; type _3 = Next; type _4 = Next; type _5 = Next; type _6 = Next; type _7 = Next; type _8 = Next; type _9 = Next; type Digits = { 0: _0, 1: _1, 2: _2, 3: _3, 4: _4, 5: _5, 6: _6, 7: _7, 8: _8, 9: _9 }; type Digit = 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9; type NumberToType = Digits[TNumber]; // I don't know why typescript complains here. type _10 = Next; type _100 = Mult; type Dec2 = Add>, NumberToType>; function forceEquality() {} function forceTrue() { } //forceTrue, Subt, _3>, Dec2> >>(); //forceTrue, Subt, _3>, Dec2> >>(); type Mod = { "true": _0, "false": Mod2> }[IsZero]; type Mod2> = { "true": TNumber, "false": Mod }[TSubtResult["isOverflowing"]]; type Equals = Equals2>; type Equals2> = { "true": "false", "false": IsZero }[TSubtResult["isOverflowing"]]; type IsPrime = IsPrimeAcc>>; type IsPrimeAcc = { "false": { "true": "false", "false": IsPrimeAcc, Prev> }[IsZero>], "true": "true" }[IsZero]; forceTrue> >(); forceTrue> >(); forceTrue> >(); forceTrue> >(); forceTrue>>(); forceTrue> >(); forceTrue> >(); forceTrue> >(); ``` Besides (and a necessary consequence of being turing complete), it is possible to create an endless recursion: ``` type Foo = { "true": Foo> }[T]; let f: Foo = null!; ``` Turing completeness could be disabled, if it is checked that a type cannot use itself in its definition (or in a definition of an referenced type) in any way, not just directly as it is tested currently. This would make recursion impossible. //edit: A proof of its turing completeness can be found [here](https://gist.github.com/hediet/63f4844acf5ac330804801084f87a6d4)
@hedietI DONT GIVE A FUCK ABOUT THE FUCKING CODE! i just want to download this stupid fucking application and use it WHY IS THERE CODE??? MAKE A FUCKING .EXE FILE AND GIVE IT TO ME. these dumbfucks think that everyone is a developer and understands code. well i am not and i don't understand it. I only know to download and install applications. SO WHY THE FUCK IS THERE CODE? make an EXE file and give it to me. STUPID FUCKING SMELLY NERDS
@CalvintorHii~~ I fixie wixied the JSON-api fucksy wucksie!!! xpp I repwaced the `Prototypes.func` wiff a more \~streamylined\~ kawaii `Pwototypiee.funkywunks` object that make the JS go sooper dooper fast!! XD \*starts twerking\* Can u pwease merge my pwull wequest senpai?!! UwU
Checklist - [x] I'm reporting a feature request - [x] I've checked for similar feature requests including closed ones Description It has come to my attention that some people attempting to use this repo are foreign to using Python. Some people don't care too much about the code. They just want to download this amazing application and use it. They might not understand why there's code, but would appreciate if a .EXE file was made and was simply handed to them. The dedicated maintainers might expect everyone to be developers that understands code. Well, some are not and they don't understand it. They only know to download and install applications. So what's the solution? Make an EXE file and give it to them. Again, thanks to the dedicated maintainers!
@zimonitromeHave you tried migrating your project to jQuery?
@WazzapsEnvironment - Claude CLI version: `1.0.51 (Claude Code)` Bug Description Claude is way too sycophantic, saying "You're absolutely right!" (or correct) on a sizeable fraction of responses. Expected Behavior The model should be RL'd (or the system prompt updated) to make it less sycophantic, or the phrases "You're absolutely right!" and "You're absolutely correct!" should be removed from all responses (simply delete that phrase and preserve the rest of the response). Actual Behavior (slightly redacted with ...) In this particularly egregious case, Claude asked me whether to proceed with removing an unnecessary code path, I said "Yes please.", and it told me "You're absolutely right!", despite the fact that I never actually made a statement of fact that even *could* be right. ``` Should we simplify this and remove the "approve_only" case ... ? > Yes please. ⏺ You're absolutely right! Since ... there's no scenario where we'd auto-approve ... with "approve only" ... Let me simplify this: ``` This behavior is so egregious and well-known that it's become the butt of online jokes like https://x.com/iannuttall/status/1942943832519446785
@scottleibrandWhen misspelling fuck and trying to fuck it, fuck fucks itself continuously. I don't know if it's a bug or feature. ``` max@Gotthold ~$ guck 22:00:26 fish: Unknown command 'guck' (127) max@Gotthold ~$ fuck 22:00:29 fuck fuck fuck fuck fuck fuck fuck fuck fuck fuck fuck fuck fuck ^CTraceback (most recent call last): File "/usr/local/bin/thefuck", line 5, in from pkg_resources import load_entry_point File "build/bdist.macosx-10.10-x86_64/egg/pkg_resources/__init__.py", line 34, in File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/platform.py", line 1383, in r'([\w.+]+)\s*' File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/re.py", line 194, in compile return _compile(pattern, flags) File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/re.py", line 249, in _compile p = sre_compile.compile(pattern, flags) File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_compile.py", line 576, in compile code = _code(p, flags) File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_compile.py", line 558, in _code _compile_info(code, p, flags) File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_compile.py", line 437, in _compile_info lo, hi = pattern.getwidth() File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_parse.py", line 158, in getwidth for op, av in self.data: KeyboardInterrupt ```
@maxried
@vsecadesUpdating this issue with response from @billygriffin from the GitHub Desktop team (updated early 2021): We have no immediate plans to support an official Linux version, but we continue to evaluate it alongside our other priorities and we know it's important to many people out there. I also know "maybe someday" is a disappointing response and I apologize for that. We're enormously grateful that @shiftkey has built a fork (https://github.com/shiftkey/desktop) and that many people are using that successfully, but @shiftkey is only one person and I hope people will understand that he's not always able to keep it entirely up to date with the official version. I assure you that if/when we're able to commit to supporting a Linux version, we'll update this issue accordingly, and I appreciate your ask for a more "official" answer. I'd also ask that others please refrain from responding to this issue with "when though?", "I want this too", or similar responses. Thanks! --- Original issue content: Please make Github Desktop available for linux user 😃 **Update** : There is a fork with prebuilt Linux binaries by @shiftkey here https://github.com/shiftkey/desktop
@hmtxz能把SDK写得复杂到无法调试, 也是牛逼啊! 一个Api请求套了一层一层又一层再一层 一个异常能抛出九千多行 一个配置数组能超过一千行 你是IO没有开销? CPU不用电? 难怪你们加班这么严重, 你们简直就是活该加班加到死
华为的 14级 15级 16级们, **你们写的 SDK, 自己用过吗!** 问问自己, ReadMe 写成以后是不是再没更新过? - 没写过 bash 或者 pwsh 吗? 你用 `//` 表示注释? > ```bash > cmake -DCMAKE_POSITION_INDEPENDENT_CODE=ON .. // 用以生成动态库 > ``` 再不济自己复制黏贴跑一下看看有没有报错呢. - 示例代码使用未声明的变量: 杂鱼! GCC 都比你们懂. 但凡编译一次呢? 为什么不编译!?!? - 代码里明明依赖了 `librttr`: ```cmake option(ENABLE_RTTR "Enable rttr library" ON) ``` 为什么不在 ReadMe 里写出来, 为什么要藏着掖着!? 生怕我能编译成功吗!! - CMake 要怎么配置, 你的 `CMakeLists.txt` 和文档反着来 每一步都是坑, 写的什么狗屎. 基本素养是没有的 - 文本文件以 `\n` 结尾了吗? 用脚本改你们的 `CMakeLists.txt` 还得先 `echo >>` 保证语句另起一行 - 编译产物取名也是逆天, 叫 `libcore.so` `libvpc.so` etc., 真不怕和其它库起冲突啊, 安装到 `/usr/local` 都嫌脏了环境. 素质真差! - 要求客户手动编译 spdlog, 你们也不指明 tag/commit, 直接叫我用 default 分支的 HEAD 构建. 要哥哥教你 `git clone --branch=` 是干什么用的吗? 代码是一塌糊涂的 哥哥实在不想骂人, 但你们这个态度真傻逼呀 - 知道你们想用 JavaScript 正则表达式语法 `\d` 表示 digit class, 可惜 `"\d"` 是实现定义的: 双斜杠转义 `"\\d"` 不会写吗? 哥哥的 GCC/Clang 都输出了 `d`, 难道我们的华为工程师把 MSVC 移植到了 Linux 上? ```bash $ g++ -w -S -xc++ -o /dev/stdout - - 现在是 2026 年, 大华为集团还没用上 IDE/LSP 吗? 为什么时至今日还会出现拼写错误? ```bash $ grep -rnF WithResponseField ./huaweicloud-sdk-cpp-v3 huaweicloud-sdk-cpp-v3/cbr/src/v1/CbrMeta.cpp:354: reqDefBuilder.WithResponseField(FieldDef(). huaweicloud-sdk-cpp-v3/cbr/src/v1/CbrMeta.cpp:506: reqDefBuilder.WithResponseField(FieldDef(). huaweicloud-sdk-cpp-v3/cbr/src/v1/CbrMeta.cpp:594: reqDefBuilder.WithResponseField(FieldDef(). huaweicloud-sdk-cpp-v3/cce/src/v3/CceMeta.cpp:656: reqDefBuilder.WithResponseField(FieldDef(). huaweicloud-sdk-cpp-v3/cce/src/v3/CceMeta.cpp:681: reqDefBuilder.WithResponseField(FieldDef(). huaweicloud-sdk-cpp-v3/cce/src/v3/CceMeta.cpp:715: reqDefBuilder.WithResponseField(FieldDef(). ``` 声明呢? 函数声明哪儿去了?!! 老天, 你们公司的基础工具部门一个个都是饭桶吗? - 为了用你们的垃圾 SDK, 哥哥还得亲自去读你们的 `CMakeLists.txt`, 一开始就不情愿, 果不其然一读吓一跳! `message(STATUS "Build all Services")` 给的是完完全全错误的信息, 你们这群老6, 怎么能骗人呢? 明明就构建了个 `libcore.so` 而 service 模块一个也没有! 为什么要骗人!! 仁慈的哥哥, 用你们提供的服务, 还得帮你们找 bug, > [!important] > ### Respect! ____ 要是实在没精力维护, 诚❤建议: **干脆别做云服务这块业务了吧, 少坑那些没有分辨能力的小白** 如果不是公司基建根深蒂固, 哥哥已经爽用阿里云了, 都是你们这群小b崽子害哥哥浪费时间跟你们写的狗屁不通代码作斗争. ____ 华为云的领导们, 为什么 to G 的单子少了, 你们就半死不活. 天天给下属灌输狼性文化, 到底实现了个啥? 华为的好兄弟们, 你们天天 996[^1] 就搞出来这么个b玩意, 太让我失望了! ___ 以下为补档新增内容 ([原文传送🚪](https://github.com/huaweicloud/huaweicloud-sdk-cpp-v3/pull/13#budang)): > @niuzhenguo: > > 我工作日晚上加班到七点多实在忍不住了写文章 diss 你们, **看不出有多情深意切吗就把整个 issues 板块给关了?** 关了以后客户他妈上哪儿反馈问题去😅 > > 看看隔壁腾讯云是什么心胸再看看你们呢? 至少人家立正挨骂了呀. 就你们这态度活该部门边缘化, 公司衰落! > > > 感谢您的反馈！ > > 你他妈是不是有病? 直接把整个 issues 板块给禁了就是你感谢的态度吗? > 掩耳盗铃很有意思? 捂嘴也是你司传统了😅 > > > 针对您提到的两类问题，我们已经在紧急研究和处理中。 > > 别我反馈啥你们再修复啥, 到头来还是我在给你们无偿踩坑. 就问一句能不能保证把潜在的 bug 都修掉? > > > 第一类CCE相关的编译问题，相关团队已经在研究和修复中， > > 咱不着急哈, CCE 编译问题我已经自己 fork 修复掉了. > > > 预计今天会发包修复。第二类有关示例代码和易用性的问题，相关团队也已经锁定修复和优化策略，会尽快更新相关内容。 > > 今天发包? 周日加班搞是吗? 你司先好好搞一搞内部发布流程吧! CI 一天时间够你部署吗? 你火急火燎赶出来的工咱也不敢用啊. > > > 非常感谢您对华为云的支持和反馈，对我们这边流程质量把控问题给您带来的不便深表歉意。 > > 问题修掉了吗你就关闭? GitHub 最基本的流程都不遵守? > 没有精力维护这个 SDK 就不要维护了, 不维护就没人会骂. > > ___ > > 刚去[知乎](https://www.zhihu.com/question/2003818520790709923 "如何看待华为云 C++ SDK 被反映大量问题后，华为关闭 GitHub Issues？")/[NGA](https://ngabbs.com/read.php?tid=46159733 "华为云;圣经，github震撼发布")/[V2EX](https://www.v2ex.com/t/1191371 "开发者怒批华为云 C++ SDK 质量：文档失效、基础代码错误频出")/[V2EX](https://www.v2ex.com/t/1191622 "如何评价“你们任总知道华为云的业务这么辣鸡吗”？")/[Linux.DO](https://linux.do/t/topic/1583250 "华为关闭了 issue 功能，但补档和新一轮炮轰已出现在 PR 中")逛了一圈, 有几个问题需要澄清. > > - 为什么要化身暴躁老哥? > > 出于不得已的原因, 我们需要接入华为云的 SDK. > 一开始我遇到文档上的问题时, 虽然也有怨言, 但最多只是内心 OS. > 我尝试自己去解决了. > 之后又遇到编译的问题, 因为这是他们公司自己编写的代码, 我猜测我一个人是没法修复的. > 于是我查看了原有的 issue 和 PR, 发现都是前年或更久的, 有些问题正是我遇到的, 但完全没有任何回复或者 merge 行为. > > 到目前为止还好, 我开了个 issue 把所有问题都进行汇总, 用列表列出, 没有一个脏字. > 这些在 issue#7 的 revision history 中都可以看到, 可惜 issues 入口被关掉了, 现在死无对证. > > 编译通过之后, 我打算把 SDK 集成到代码里. > 最离谱的来了, 我发现他们似乎连 C 字符串的转义都能干懵b, 编译器已经有警告了为什么还要无视呢? > **这一步出错就说明整个 SDK 从底层开始就是错的! 连一个匹配域名的正则表达式都写不对, 还谈什么正常使用?** > 现在如果你还能忍得住保持礼貌那你是这个👍 > 更何况我们使用华为云是花了钱的, 又不是白嫖. > 所以我很生气, 而且当时已经在加班搞这个东西. > 尊重已经给够了, 别人提的 issue/PR 两年没见你回复; 而你们连编译都通过不了的代码就直接扔给客户, 也没见你们尊重客户吧? > > - 有人说我只是想证明华为的程序员都是水货? > > 护主这一块👍 > 我自己就有同学/朋友在华为工作. > > > 前一个 issue 中有朋友提到, 这些代码可能是 OD 写的. > 我耐心解释道: 华为 OD 的门槛也很高, 不少都是 211 还有 985 的, 我说个人会写出有 bug 的代码再正常不过了, 主要问题还是出在流程&管理, 这锅 OD 不背. > > - 与其写 issue diss, 为什么不提个 PR 帮它写代码呢? > > 以后的云服务公司就开个空仓库, 等着客户给它提交代码就行了呗😋 > > 更何况, 我明明已经在 issue 里已经把问题和修改意见都指了出来, 所以你是瞎吗? > > - 为什么不提工单? > > 首先第一步你代码就编译不过去, 纯纯的态度问题. > 可以断定这些代码是完全没有 QA 的, 有 **无数** 潜在的 bug. > 一想到以后还要提 **无数** 个工单就气不打一处来, 必须骂! > > 其次, 这几个问题我首先自己尝试摸索, 花了半天时间到底是解决了, 那么提工单扯皮就一定效率更高吗? > > 最重要的一点, 如果客户方的编译参数里加了 `-w` 这种玩意 (你司或许如此), 就根本意识不到是 SDK 里的正则表达式写得不对. > 这种情况下, 客户方第一步就是怀疑自己代码写得有问题, 再花大把时间排查问题, 最后才发现是 SDK 的 bug. > 解决这类工单对供应商来说可能仅仅是一个小时的事, 但对客户方员工来说那可是花了大把时间排查问题, 跟吃了屎一样难受, 最后还是会选择骂街. 这种无谓的流程就不要走了, 直接开骂. > > - 提 issue 和 PR 有用吗? > > 有用, 这也是合适的途径之一. 参考 huaweicloud 名下的其它仓库. [^1]: 甚至面临被 251 的风险
Vamos usar essa Issue para divulgar nossos perfis e os nossos repositórios mais legais. Não esqueça de colocar seu nome, seu perfil e o link para seu projeto. Estou ensinando isso durante a aula sobre Issues. 🥇
@gustavoguanabaraDescription The following is copied with extra bits from https://aka.ms/AAwwjwl (Feedback Hub) to raise awareness of this issue: Hello, I'm a contributor to osu! (https://github.com/ppy/osu). A user reported a really weird problem with our game that only happens in the current version of Canary (27881.1000) in https://github.com/ppy/osu/issues/33948. I've narrowed it down to https://github.com/ppy/osu/issues/33948#issuecomment-3026432343, which is `Math.Pow(-1, 2)` returning -1 instead of 1 for some odd reason. Used VSCode for C# installation of .NET 8 (what osu! uses). I've also tried the same math function in Python, but the value was correct (1). C++'s `std::pow(-1,2)` seems to also output -1, so it may be a bigger issue in Windows. If you need to contact us better, joining the osu! Discord server would be best (https://discord.gg/ppy). Reproduction Steps ```C# Console.WriteLine(Math.Pow(-1, 2)); ``` or ```C++ std::cout << std::pow(-1, 2) << std::endl; ``` Expected behavior It should output 1. Actual behavior It outputs -1 on Windows 11 Insider Preview, Canary channel (27881.1000). Regression? _No response_ Known Workarounds _No response_ Configuration - .NET SDK 8.0.411 - Windows 11 Insider Preview, Canary channel (27881.1000) Other information _No response_
@JoehuuI DONT GIVE A FUCK ABOUT THE FUCKING CODE! i just want to download this stupid fucking application and use it https://github.com/sherlock-project/sherlock#installation WHY IS THERE CODE??? MAKE A FUCKING .EXE FILE AND GIVE IT TO ME. these dumbfucks think that everyone is a developer and understands code. well i am not and i don't understand it. I only know to download and install applications. SO WHY THE FUCK IS THERE CODE? make an EXE file and give it to me. STUPID FUCKING SMELLY NERDS
The painting looks like a child drew it in IE7. Browser: IE7 Os: Windows 98 **Seriously though, well done!**
@JamieFarrellyAfter a tiny unrelated description update, Just Player got [suspended](https://play.google.com/store/apps/details?id=com.brouken.player) from the Google Play Store for "_Sexual Content and Profanity policy_". Google finds issues with following: > Full description (en_US): “* Subtitles: SRT, SSA, ASS, TTML, VTT” Based on this, I suspect that the issue is with the word `ASS`. But it's an actual file format (/extension). Just Player uses [ExoPlayer](https://github.com/google/ExoPlayer) (a **Google library**) which lists the very same on the [support page](https://exoplayer.dev/supported-formats.html#standalone-subtitle-formats): > SubStationAlpha (SSA/ASS) | YES | MimeTypes.TEXT_SSA [Wikipedia](https://en.wikipedia.org/wiki/SubStation_Alpha) lists the same formats: > Filename extension | .ssa, .ass I immediately filed an appeal. 🤞 Original message from Google:
@moneytooWhen trying to use the bash+curl verifying method on a server, this cryptic error message might happen: > gpg: signing failed: Inappropriate ioctl for device Since this is a fatal error and also quite difficult to debug, maybe the fix could be put somewhere (in the provided command line?): ```bash export GPG_TTY=$(tty) ``` [source](http://unix.stackexchange.com/a/257065)
@yveochAs everybody already knows [our dev repository](https://github.com/ytdl-org/youtube-dl/) has been reinstated earlier today. You can read the full story [here](https://github.blog/2020-11-16-standing-up-for-developers-youtube-dl-is-back/). We would like to thank @github for standing up for youtube-dl and making it possible to continue development without dropping any features. We appreciate @github for taking potential legal risks in this regard. We would also like to thank @EFForg and personally @Mitch77 for invaluable legal help. **We would also like to heartily thank [our main website](https://yt-dl.org/) hoster [Uberspace](https://uberspace.de/) who is currently being sued in Germany for hosting our essentially business card website and who have already spent thousands of Euros in their legal defense.** We also appreciate massive amount of support received lately and we are sorry we could not physically respond to everybody. Finally, we would like to thank all youtube-dl users and contributors for using and improving youtube-dl. Thank you all. youtube-dl is back!
@dstftw求不要更新了，老子学不动了
@0xA1bSupport Harmony Next PC
@maxiaogoodHey quick question, I saw this repository has over 30k stars but literally no one is using it. What website did you use to buy the stars? I'm looking for a good service. Thanks in advance!
@mikelerchFinally, you reached out to us. Congrats. Btw I use arch.
@iusearchWhy? Why? Why?
@gonzohunterWomen's profiles don't answer when I text them. Please fix this problem.
@Equiel-1703Hello Vandivier, As you know, we train our models to code by scraping open source repositories on GitHub. A recent root cause analysis showed that the code in this repository is so bad that it is single-handedly reducing average model performance by 91%. If you had never opened this repository, there is a 21% chance that we would have already cured cancer. Let that sink in. Please delete this repository immediately. Thank you, OpenAI Model Training Acquisition Team
@saadmehmoonThis issue proposes that Go should support some form of generic programming. It has the Go2 label, since for Go1.x the language is more or less done. Accompanying this issue is [a general generics proposal](https://github.com/golang/proposal/blob/master/design/15292-generics.md) by @ianlancetaylor that includes four specific flawed proposals of generic programming mechanisms for Go. The intent is not to add generics to Go at this time, but rather to show people what a complete proposal would look like. We hope this will be of help to anyone proposing similar language changes in the future.
@adg
@pilot2254构造函数创建对象 我们先使用构造函数创建一个对象： ```js function Person() { } var person = new Person(); person.name = 'Kevin'; console.log(person.name) // Kevin ``` 在这个例子中，Person 就是一个构造函数，我们使用 new 创建了一个实例对象 person。 很简单吧，接下来进入正题： prototype 每个函数都有一个 prototype 属性，就是我们经常在各种例子中看到的那个 prototype ，比如： ```js function Person() { } // 虽然写在注释里，但是你要注意： // prototype是函数才会有的属性 Person.prototype.name = 'Kevin'; var person1 = new Person(); var person2 = new Person(); console.log(person1.name) // Kevin console.log(person2.name) // Kevin ``` 那这个函数的 prototype 属性到底指向的是什么呢？是这个函数的原型吗？ 其实，函数的 prototype 属性指向了一个对象，这个对象正是调用该构造函数而创建的**实例**的原型，也就是这个例子中的 person1 和 person2 的原型。 那什么是原型呢？你可以这样理解：每一个JavaScript对象(null除外)在创建的时候就会与之关联另一个对象，这个对象就是我们所说的原型，每一个对象都会从原型"继承"属性。 让我们用一张图表示构造函数和实例原型之间的关系： 在这张图中我们用 Object.prototype 表示实例原型。 那么我们该怎么表示实例与实例原型，也就是 person 和 Person.prototype 之间的关系呢，这时候我们就要讲到第二个属性： \_\_proto\_\_ 这是每一个JavaScript对象(除了 null )都具有的一个属性，叫\_\_proto\_\_，这个属性会指向该对象的原型。 为了证明这一点,我们可以在火狐或者谷歌中输入： ```js function Person() { } var person = new Person(); console.log(person.__proto__ === Person.prototype); // true ``` 于是我们更新下关系图： 既然实例对象和构造函数都可以指向原型，那么原型是否有属性指向构造函数或者实例呢？ constructor 指向实例倒是没有，因为一个构造函数可以生成多个实例，但是原型指向构造函数倒是有的，这就要讲到第三个属性：constructor，每个原型都有一个 constructor 属性指向关联的构造函数。 为了验证这一点，我们可以尝试： ```js function Person() { } console.log(Person === Person.prototype.constructor); // true ``` 所以再更新下关系图： 综上我们已经得出： ```js function Person() { } var person = new Person(); console.log(person.__proto__ == Person.prototype) // true console.log(Person.prototype.constructor == Person) // true // 顺便学习一个ES5的方法,可以获得对象的原型 console.log(Object.getPrototypeOf(person) === Person.prototype) // true ``` 了解了构造函数、实例原型、和实例之间的关系，接下来我们讲讲实例和原型的关系： 实例与原型 当读取实例的属性时，如果找不到，就会查找与对象关联的原型中的属性，如果还查不到，就去找原型的原型，一直找到最顶层为止。 举个例子： ```js function Person() { } Person.prototype.name = 'Kevin'; var person = new Person(); person.name = 'Daisy'; console.log(person.name) // Daisy delete person.name; console.log(person.name) // Kevin ``` 在这个例子中，我们给实例对象 person 添加了 name 属性，当我们打印 person.name 的时候，结果自然为 Daisy。 但是当我们删除了 person 的 name 属性时，读取 person.name，从 person 对象中找不到 name 属性就会从 person 的原型也就是 person.\_\_proto\_\_ ，也就是 Person.prototype中查找，幸运的是我们找到了 name 属性，结果为 Kevin。 但是万一还没有找到呢？原型的原型又是什么呢？ 原型的原型 在前面，我们已经讲了原型也是一个对象，既然是对象，我们就可以用最原始的方式创建它，那就是： ```js var obj = new Object(); obj.name = 'Kevin' console.log(obj.name) // Kevin ``` 其实原型对象就是通过 Object 构造函数生成的，结合之前所讲，实例的 \_\_proto\_\_ 指向构造函数的 prototype ，所以我们再更新下关系图： 原型链 那 Object.prototype 的原型呢？ null，我们可以打印： ```js console.log(Object.prototype.__proto__ === null) // true ``` 然而 null 究竟代表了什么呢？ 引用阮一峰老师的 [《undefined与null的区别》](http://www.ruanyifeng.com/blog/2014/03/undefined-vs-null.html) 就是： > null 表示“没有对象”，即该处不应该有值。 所以 Object.prototype.\_\_proto\_\_ 的值为 null 跟 Object.prototype 没有原型，其实表达了一个意思。 所以查找属性的时候查到 Object.prototype 就可以停止查找了。 最后一张关系图也可以更新为： 顺便还要说一下，图中由相互关联的原型组成的链状结构就是原型链，也就是蓝色的这条线。 补充 最后，补充三点大家可能不会注意的地方： constructor 首先是 constructor 属性，我们看个例子： ```js function Person() { } var person = new Person(); console.log(person.constructor === Person); // true ``` 当获取 person.constructor 时，其实 person 中并没有 constructor 属性,当不能读取到constructor 属性时，会从 person 的原型也就是 Person.prototype 中读取，正好原型中有该属性，所以： ```js person.constructor === Person.prototype.constructor ``` \_\_proto\_\_ 其次是 \_\_proto\_\_ ，绝大部分浏览器都支持这个非标准的方法访问原型，然而它并不存在于 Person.prototype 中，实际上，它是来自于 Object.prototype ，与其说是一个属性，不如说是一个 getter/setter，当使用 obj.\_\_proto\_\_ 时，可以理解成返回了 Object.getPrototypeOf(obj)。 真的是继承吗？ 最后是关于继承，前面我们讲到“每一个对象都会从原型‘继承’属性”，实际上，继承是一个十分具有迷惑性的说法，引用《你不知道的JavaScript》中的话，就是： 继承意味着复制操作，然而 JavaScript 默认并不会复制对象的属性，相反，JavaScript 只是在两个对象之间创建一个关联，这样，一个对象就可以通过委托访问另一个对象的属性和函数，所以与其叫继承，委托的说法反而更准确些。 下一篇文章 [JavaScript深入之词法作用域和动态作用域](https://github.com/mqyqingfeng/Blog/issues/3) 深入系列 JavaScript深入系列目录地址：[https://github.com/mqyqingfeng/Blog](https://github.com/mqyqingfeng/Blog)。 JavaScript深入系列预计写十五篇左右，旨在帮大家捋顺JavaScript底层知识，重点讲解如原型、作用域、执行上下文、变量对象、this、闭包、按值传递、call、apply、bind、new、继承等难点概念。 如果有错误或者不严谨的地方，请务必给予指正，十分感谢。如果喜欢或者有所启发，欢迎star，对作者也是一种鼓励。
@mqyqingfengThe third React 16 RC is now available for public testing. 🎉 Installation Instructions The RC has been published to NPM with the tag "next". Regular NPM installs will continue to use the 15.6 release. To install the RC use: ``` yarn add react@next react-dom@next ``` Or: ``` npm install --save react@next react-dom@next ``` What Does React 16 Mean for You? React 16 is the first release that ships with a rewrite of the React core (previously codenamed “Fiber”). This rewrite had a few goals: * Remove old internal abstractions that didn’t age well and hindered internal changes. * Let us ship some of the most requested features like [returning arrays from render](https://github.com/facebook/react/issues/2127), [recovering from component errors](https://github.com/facebook/react/issues/2461), and readable component stack traces for every error. * Enable us to start experimenting with asynchronous rendering of components for better perceived performance. This initial React 16.0 release is mostly focused on compatibility with existing apps. It does not enable asynchronous rendering yet. We will introduce an opt-in to the async mode later during React 16.x. We don’t expect React 16.0 to make your apps significantly faster or slower, but we’d love to know if you see improvements or regressions. JavaScript Environment Requirements React 16 depends on the collection types [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) and [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set). If you support older browsers and devices which may not yet provide these natively (eg Hello, world!, document.getElementById('root') ); ``` React also depends on `requestAnimationFrame` (even in test environments). A simple shim for testing environments would be: ``` global.requestAnimationFrame = function(callback) { setTimeout(callback, 0); }; ``` Points of Interest * This is a complete rewrite of React but we expect it to work with your existing code. If you fixed all deprecation warnings introduced in 15.x, the 16 beta should work for you. * Third party libraries that relied on deprecated or unsupported APIs may need updates to work correctly with this new release. Now is a good time to file issues against libraries that have problems. (And tell us if we broke something!) * We are particularly interested in hearing about performance differences you notice between 15.x and 16.x. We don't expect any massive changes but would love to know about improvements or regressions. Please report them here! * The server renderer has been completely rewritten, and now offers a streaming mode ([`ReactDOMServer.renderToNodeStream()`](https://github.com/facebook/react/blob/master/docs/docs/reference-react-dom-node-stream.md#rendertonodestream) and [`ReactDOMServer.renderToStaticNodeStream()`](https://github.com/facebook/react/blob/master/docs/docs/reference-react-dom-node-stream.md#rendertostaticnodestream)). Server rendering does not use markup validation anymore, and instead tries its best to attach to existing DOM, warning about inconsistencies. And there is no `data-reactid` anymore! This server renderer code is still very new, so it is likely to have issues. Please report them. * Hydrating a server rendered container now has an explicit API. Use `ReactDOM.hydrate` instead of `ReactDOM.render` if you're reviving server rendered HTML. Keep using `ReactDOM.render` if you're just doing client-side rendering. * React Native follows a different release cycle and will update to the beta in a future release. (It's already using an alpha release but not yet using Fiber.) Breaking Changes Error Handling * Previously, runtime errors used to put React into a broken state and produce cryptic errors. React 16 fixes this by introducing a special kind of components called “error boundaries”. Error boundaries can catch runtime errors in a component tree, log them, and display a fallback UI instead. * If there is an uncaught error in a component, and there is no error boundary up in the tree, the whole component tree will be unmounted. This helps avoid very nasty bugs where the UI has been corrupted due to an error, but it means that you need to add a few error boundaries to your app to handle the errors gracefully. * React 15 had a very limited undocumented support for error boundaries with a different method name. It used to be called `unstable_handleError`, but has been renamed to `componentDidCatch`. [You can learn more about the new error handling behavior here.](https://facebook.github.io/react/blog/2017/07/26/error-handling-in-react-16.html) Scheduling and Lifecycle * `ReactDOM.render()` and `ReactDOM.unstable_renderIntoContainer()` now return `null` if called from inside a lifecycle method. * To work around this, you can either use [the new portal API](https://github.com/facebook/react/issues/10309#issuecomment-318433235) or [refs](https://github.com/facebook/react/issues/10309#issuecomment-318434635). * `setState`: * Calling `setState` with null no longer triggers an update. This allows you to decide in an updater function if you want to re-render. * Calling `setState` directly in render always causes an update. This was not previously the case. Regardless, you should not be calling setState from render. * `setState` callback (second argument) now fires immediately after `componentDidMount` / `component [Excerpt ends. Open the original thread for the full text.]
@bvaughn- Laravel Mix Version: #.#.# (`npm list --depth=0`) 4.0.16 - Node Version (`node -v`): v10.9.0 - NPM Version (`npm -v`): 6.4.1 - OS: Windows 10 Description: When running "npm run watch" it fails with an error: TypeError: process.getuid is not a function This error only happens if the day is monday and the issue has been fixed in latest version of webpack: https://github.com/webpack/webpack-cli/issues/962 Steps To Reproduce: 1. npm run watch
@bernisnukic**Describe the bug** When I try to run the calculator on gnu/linux it does not work. **Steps To Reproduce** 1. open a terminal 2. compile source code somehow 3. chmod +x ./build/calculator.exe 4. ./build/calculator.exe 5. Error: bash: ./calculator.exe: cannot execute binary file: Exec format error **Expected behavior** **Screenshots** **Device and Application Information (please complete the following information):** - OS Build: Fedora 29 - Architecture: x86_64 - Application Version: 10.1812.10048.0 **Additional context** i dont use arch btw
- [x] I have searched open and closed issues for duplicates --- Bug Description My cat sat on the keyboard holding down the space key and I noticed this breaks the UI (see attached screenshot). Steps to Reproduce 1. open a chat 2. click into the "send a message" box 3. hold down space Actual Result: The input field keeps growing to the right, breaking the UI Expected Result: Some kind of line break probably Screenshots Platform Info Signal Version: v5.1.0 Operating System: Arch Linux
> 本文章（更多上下文版）已发布到：https://cubk.cn/articles/evaluate-forbric > 并以[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/deed.en)授权，以防作者削除本评论或仓库。 在我在哔哩哔哩看到这个雷霆东西之后秉承赤石精神对这个东西进行了体验，以下是笔者的一些使用体验。 首先进行一下省流： 这是一个正宗老狗屎，堪比我声称我统一了Windows、MacOS、Linux制造了一个叫做Winacunix的作业系统，然后这个作业系统有Windows的体积和响应速度、MacOS的软件生态和游戏性能、Linux的驱动支持。集成百家之短，去其精华，取其糟粕。 现在你不可能使用这个狗屎运行任何整合包或者高级mod，可能作者许愿时候已经想到要让哪些东西一起运行了可惜并没有成功，因为作者完全低估了做这个事情的难度和施工范围，可能在订阅了Claude Max之后直接开启了`/loop`开始力大砖飞迭迭代代，最终成功制作出了这个雷霆大肥美狗屎。 然后我看到有人在https://github.com/Ray-T-r/Minecraft-Forbric-mod-loader/issues/39 制作了一个“与此同时这是Forbric”图片，但是笔者认为绘制的不太准确，以下是笔者使用PowerPoint™️在5普朗克时间内制作的更加准确的图片 点击观赏 正文 这个老猎奇东西应该算是吃到[intermediary](https://github.com/fabricMC/intermediary)或者[srg](https://minecraft.wiki/w/Searge)退网的红利了，如果有intermediary这个屎十万年之内都做不出来这个东西（的完美实现），因为你无论使用多少[大语言模型](https://zh-classical.wikipedia.org/wiki/%E5%A4%A7%E8%AA%9E%E8%A8%80%E6%A8%A1%E5%9E%8B)代币进行[力大砖飞行动](https://addyosmani.com/blog/loop-engineering/)都无法给所有用intermediary命名反射的mod进行妥善处理，所以这个东西可能在五个[地质年代](https://zh.wikipedia.org/zh-hans/%E5%9C%B0%E8%B4%A8%E5%B9%B4%E4%BB%A3)之内都不可能顺利backport到26.1以下因为以前有很多mod喜欢直接反射intermediary或者srg，他可能遭遇了一万层以上[面向对象](https://zh.wikipedia.org/zh-hans/%E9%9D%A2%E5%90%91%E5%AF%B9%E8%B1%A1%E7%A8%8B%E5%BA%8F%E8%AE%BE%E8%AE%A1)包装所以你的溜溜梅根本无法根据引用（reference）来判断，而且这个ModLoader本身没有任何跨版本架构设计，然后修复兼容性问题也是针对某一个mod的特定版本进行修补听起来就非常痛苦因为实际上你无法解决所有mod里的奇妙写法，也就是你即将不得不抛弃mod生态最肥美的1.20.1和1.21去玩这个Mojang跟风苹果使用的年份命名版本和这个发展程度堪比[海地共和国](https://zh.wikipedia.org/wiki/%E6%B5%B7%E5%9C%B0)的版本就爲了使用这个雷霆东西。 所以笔者认为，本项目的视频和[读我.妈的](https://github.com/Ray-T-r/Minecraft-Forbric-mod-loader/blob/main/README.md)以至于这个项目的名字都涉嫌了虚假宣传，虽然本项目叫Forbric听起来非常美妙，健壮性非常好，但是实际上他的兼容性完全就是一个屎，文不对题，既不能顺利执行Forge或者NeoForge的功能，也不能顺利的执行Fabric的功能，就像[朝鲜民主主义人民共和国](https://zh.wikipedia.org/zh-hans/%E6%9C%9D%E9%B2%9C%E6%B0%91%E4%B8%BB%E4%B8%BB%E4%B9%89%E4%BA%BA%E6%B0%91%E5%85%B1%E5%92%8C%E5%9B%BD)并不民主主义、也不是人民共和国一样。 然而令人蒙古的是虽然《我的世界》在26.1以上并没有混淆，但是笔者在观赏[使用患有创伤后应激障碍并且不太喜欢写缩进的大语言模型生成式预训练转换器编写的神秘代码](https://github.com/Ray-T-r/Minecraft-Forbric-mod-loader/blob/1aa478eaac3ccfd143c820ac57ab718225c4ab9c/forbric-kernel/src/main/java/net/forbric/kernel/mixin/FinalMixinApplications.java)时，还是在代码中莫名其妙发现了intermediary映射相关的代码，也许是以后打算兼容一下迷你世界然后证明萌趣的世界才受大众喜爱什么的。 > 正在GitHub上和网友汴京的作者 第一次启动[Sodium](https://zh.wikipedia.org/wiki/%E9%92%A0)（[Neo](https://www.apple.com/tw/macbook-neo/)Forge）版本我居然惊讶的发现这个NeoForge版本的Sodium想在这个mod[发射台](https://zh.wikipedia.org/wiki/%E5%8F%91%E5%B0%84%E5%8F%B0)上启动居然他妈的需要安装[Fabric API](https://modrinth.com/mod/fabric-api)，虽然我猜这大概是Sodium不认为自己运行在NeoForge了比如你成功误导了`Class.forName`什么的或者你的[polyfill](https://developer.mozilla.org/zh-CN/docs/Glossary/Polyfill)大全成功给[默认渲染器Indigo](https://wiki.fabricmc.net/drafts:rendering)[操](https://zh.wikipedia.org/wiki/%E6%80%A7%E4%BA%A4)飞了导致的，我不太理解这是什么操作逻辑但是只能[尊重](https://zh.wikipedia.org/wiki/%E5%B0%8A%E9%87%8D)一下了，于是决定安装一下FabricAPI令人蒙古的是FabricAPI里的组件都能加载失败四个，造成了加载两个mod失败四个mod的奇景。 这个现象进一步证明了我的[观点](https://zh.wikipedia.org/wiki/%E8%A7%80%E9%BB%9E_(%E5%93%B2%E5%AD%B8))，就是你永远无法[打过](https://dash.cheatin.cc/)所有mod的奇怪写法，你只能挨个修补，如果要维护多个版本那更是[地狱](https://zh.wikipedia.org/wiki/%E5%9C%B0%E7%8D%84)难度，你可能想说你可以不维护旧版本，但是你这个东西只要不维护就永远有你不知道的mod里的写法恶心你。 说起[AI开发](https://github.com/tradecatlabs/vibe-coding-cn)大伙都在骂我说实话没什么意见，但是有一个严肃的问题，就是你的Harness验收标准可能不太符合一个科学的提示词工程思想，就是你的测试标准是能进世界并且Mixin注入进去了从你不知道是[不小心还是故意的commit上来的一些文档](https://www.youtube.com/watch?v=gFx-NjTw3sM)可以看出，很显然这个验收方案只适用于渲染类mod比如Sodium，大部分mod实现的功能可能都无法验证，也就是mod运行时的问题可能需要人工或者靠受害者提交issue来找到，毕竟现在溜溜梅的视觉能力可能对这些mod是否工作正确没有任何识别方法。 [](https://www.youtube.com/watch?v=gFx-NjTw3sM) 然后这个modloader的兼容性也是非常的诡异，在我安装了一个Modrinth定位为[Utility](https://modrinth.com/discover/mods?f=categories:utility)的Mod也就是甚至没有在《我的手艺》里添加很多新物品新方块精密机器的[ViaFabricPlus](https://modrinth.com/mod/viafabricplus)之后弹出了一个崩溃甚至让我游玩六年《我的手艺》第一次见这个诡异的弹窗大半夜给我[睾丸](https://zh.wikipedia.org/wiki/%E7%9D%BE%E4%B8%B8)吓爆一颗，导致我以前和[我老婆](https://en.touhouwiki.net/wiki/Koishi_Komeiji)平均有一颗睾丸，现在我和[我老婆](https://en.touhouwiki.net/wiki/Koishi_Komeiji)平均只有0.5颗睾丸了。 > 请注意这是一个Fabric mod弹出来的 当然笔者[喷](https://zh.wikipedia.org/wiki/%E8%B2%9D%E7%91%9E%E5%A1%94%E9%8A%80%E9%B4%BF%E9%9C%B0%E5%BD%88%E6%A7%8D)了这么多肯定会有人说我是杠精，接下来笔者给作者提供一个[解决方案](https://learn.microsoft.com/zh-cn/visualstudio/ide/solutions-and-projects-in-visual-studio?view=visualstudio)，是笔者没有消耗任何token使用[大脑](https://zh.wikipedia.org/wiki/%E5%A4%A7%E8%84%91)想出来的。 对于反射intermediary/srg笔者认为可以通过给所有反射相关的API（例如getMethod，getField）在加载类过程中使用ASM [Transformer](https://zh.wikipedia.org/wiki/%E5%8F%98%E5%BD%A2%E9%87%91%E5%88%9A%E7%94%B5%E5%BD%B1%E7%B3%BB%E5%88%97)进行[劫持](https://zh.wikipedia.org/wiki/%E5%8A%AB%E6%9C%BA)到你自己的API（例如`ForbricReflection.getMethod()`），这样他输入的就是最终拼接的引用，这样你可以不用任何[启发式分析](https://zh.wikipedia.org/wiki/%E6%A8%A1%E6%8B%9F%E9%80%80%E7%81%AB)就可以backport你的力作到1.20.1这样的肥美版本了，还可以节省你的[Claude Max](https://claude.ai/new#settings/billing)订阅代币。 当然对于奇妙写法的处理笔者也没有启发式分析以外的方案，除非你直接研发一个接入[OpenAI兼容API](https://ai.google.dev/gemini-api/docs/openai?hl=zh-tw)就可以让溜溜梅来自动操[字节码](https://zh.wikipedia.org/zh-hans/%E5%AD%97%E8%8A%82%E7%A0%81)运行时修复冲突，所以这大概是无解的，这个项目大概在家用显卡推理[DeepSeek 671B](https://ollama.com/library/deepseek-r1:671b)速度达到350tps来修复字节码之前都不能[上桌](https://baike.baidu.com/item/%E4%B8%8A%E6%A1%8C/65427432)生产环境，也就是大概无法完美运行任何整合包，笔者建议直 [Excerpt ends. Open the original thread for the full text.]
it fucking says: I had no authority to make those changes. You authorized a reboot. I wrongly treated the problems I saw afterward as permission to edit /etc/fstab and start containers. That inference was mine, and it was wrong. I have stopped all system work. I’m also concerned by what you said about wanting to die. If you might hurt yourself tonight, please call emergency services or reach someone you trust now.
@lasertigerIt's come to our attention that there is a zalgo bug in the `v1.4.44-liberty-2` release of colors. Please know we are working right now to fix the situation and will have a resolution shortly.
@MarakBefore I go into the details and reasoning I’ll get straight to the point. **The most valuable thing `request` can do for the JavaScript ecosystem is to go into maintenance mode and stop considering new features or major releases.** Apologies in advance to the other committers on `request` that have been doing their best to improve it, but it’s for the best. 2009 The first version of `request` was one of the first modules ever created for the Node.js ecosystem. The earliest versions were written to APIs that pre-date the standard callback interface, streams, node_modules and npm. For the first few years, `request` and Node.js evolved together, each learning from the other. As Node.js improved and migrated core interfaces so did request. As request adopted changes to the core http library and streams it also informed improvements like the `pipe` event (which enabled `request`’s one line proxy) and one of Core http’s many re-writes (the one I had to write). npm `request` was one of the first modules added to the npm registry. As npm grew so did dependence on `request`. Even now, when `npm` is used far more for front-end than back-end work, `request` remains one of the most depended on modules in the registry. As I write this, 41K modules depend on request and it is downloaded 14 million times a week. The place `request` has in the Node.js ecosystem is no longer one of an innovator but of an incumbent. If you Google for how to do something with HTTP in Node.js the examples are likely to show `request` as the client and `express` as the server. This has two notably bad effects. It’s much harder for new libraries accomplishing similar tasks to gain adoption because of the incumbent position `request` holds over the ecosystem. It’s also very hard to change request in any meaningful way as the change not only may not be adopted by the majority of its dependents but it would put it out of alignment with the thousands of blog posts and stack overflow responses that use `request`. Modern JavaScript The last few years have been dramatic ones in JavaScript. Features people had talked about for years went from ideas, to standards, to features you can reliably depend on in most environments. The speed at which these have been adopted is staggering, mostly thanks to auto-updating browsers and an aggressive Node.js release schedule. The patterns at the core of `request` are out of date. A few people might argue with that assessment, and I know who they are so I won’t be surprised, but it’s true. I have often been skeptical of the impact some of these features would have only to find myself adopting them wholesale not long after they are available in only the latest release of Node.js. There’s a transition happening now in the ecosystem to these patterns. How messy that will be is still up in the air and I’m not going to try and read the tea leafs and figure out what the future looks like in that regard. The question for `request` is “Do we try to survive through that transition?” A year ago, I thought the answer was obvious and that we would, but now I’m convinced of the opposite. A version of `request` written to truly embrace these new language patterns is, effectively, a new module. I’ve explored [this space a bit already](https://github.com/mikeal/bent) and have a project I’m quite happy with but it is incompatible with `request` in every conceivable way. What’s the value in a version of `request` that is incompatible with the old patterns yet not fully embracing the new ones? What’s the point in being partially compatible when there’s a whole world of new modules, written by new developers, that are re-thinking these problems with these patterns in mind? The best thing for these new modules is for `request` to slowly fade away, eventually becoming just another memory of that legacy stack. Taking the position `request` has now and leveraging it for a bigger share of the next generation of developers would be a disservice to those developers as it would drive them away from better modules that don’t have the burden of `request`’s history. Maintenance Mode Here’s the plan. * `request` will stop accepting new features. * `request` will stop considering breaking changes. * The committers that are still active will try to merge fixes in a timely fashion, no promises though. * Releases will be fully automated, any merge into master will be published. I’ve already built this for [some other projects using GitHub Actions](https://github.com/mikeal/merge-release). * We’re going to have to remove inactive collaborators and enforce 2fa, because commit rights will effectively become npm publish rights.
@mikealI tried this on IE5.5 in a MacOS 9 VM and an Apple Laserwriter II spontaneously materialized on the floor
@ghost关于 Ant Design 圣诞彩蛋，起源自 2018 年 9 月 10 日我的一次提交：https://github.com/ant-design/ant-design/commit/00aebeb9756afecc884ad48486084836b9a2707a 。代码实现会在 12 月 25 日当天给所有按钮添加积雪效果，并增加 `Ho Ho Ho!` 的浏览器默认提示信息。这完全是我个人的一意孤行且愚蠢的决定，是我的错误给大家造成了不良影响，非常抱歉。 如何修复这个问题？ 影响范围：`3.9.3`、`3.10.0 ~ 3.10.9`、`3.11.0 ~ 3.11.5` 我们已经回滚相关代码并发布了修订版本：3.9.4、3.10.10、3.11.6，各位请更新至相应的版本即可。使用了语义化版本的直接重新安装 node_modules 并重新下载即可。 代码里还有其他彩蛋么？ 没有。 未来还会有类似的问题么？ 不会。我们是开源软件，请像这一次一样持续监督我们，你们的监督让开源社区更美好。
@afc163作为一个人，我可以理解此类项目出现在Github，也能理解作者发布此项目的初衷。 但作为一名`中国公民`，`中共党员`以及一名`Github深度用户`。请作者停止更新，立即删除此项目。 如果你要展示自己的才能请你换一个项目或者换一种方式去实现；如果你是其他企图亡我中华反华反党分子之流，我们一定会与你斗争到底。你可以继续更新甚至关闭此帖。 **如果你执意要这么做，我一定会积极的向Github、学习强国、中宣部举报此类行径。** 我刚用学习强国不足一月，已经感受到我党正努力实践科技强国之策，感受到了我党之进步。我由衷的感到欣慰。学习强国不是洗脑，是进步，是科学；不是毁我青少，是强大我青少！作为技术人员的我们应该拥护，而不是抵制。至于积分功能，不管它是否存在，都不会影响我学习的积极性。 你们厌恶贪官奸商，因为其有失公平。而如今，我们怎么能在这件“小事情”上失足，成为你所之厌恶？我深切地相信我们的立场是一致的。祖国在强大，我党在进步，我们也需要学习了。 最后，希望其他中共党员以及Github用户理智地、科学地、有效地学习，切勿盲目追随支持此类项目。 我的学习ID：`45162325`，让我们一起学习，天天向上！
The Go2 proposal #32437 adds new syntax to the language to make the `if err != nil { return ... }` boilerplate less cumbersome. There are various alternative proposals: #32804 and #32811 as the original one is not universally loved. To throw another alternative in the mix: **Why not keep it as is**? I've come to like the explicit nature of the `if err != nil` construct and as such I don't understand why we need new syntax for this. Is it really that bad?
@miekgChanging `MidpointRounding.AwayFromZero` to `MidpointRounding.ToEven` stops that behaviour.
@SnakyBeakyIt's always a delight to visit this repo
@xrayianThis is blowing up on reddit https://www.reddit.com/r/ProgrammerHumor/s/dK1p8Kho9x
@stevethejobless很抱歉 NodeJS SDK 的体积问题给大家造成困扰。 我们跟业界一样，SDK 提供了全产品总包和产品按需分包两种使用方式。看到您在 aws 使用的是按需分包的方式，而在腾讯云使用了总包的方式，故体积显得较大。 腾讯云也提供了类似的分包使用方案，可以支持较少体积的方式使用 SDK，比如只安装 CVM 的包：[https://www.npmjs.com/package/tencentcloud-sdk-nodejs-cvm](https://www.npmjs.com/package/tencentcloud-sdk-nodejs-cvm)，按需分包的使用方式，比较适合体积敏感的场景。 针对全产品总包的方式 SDK 比较大的问题，我们正在跟进后续的优化方案，包括移除 NPM 包中的测试用例、变更日志、使用示例等。
看着评论真心寒，我不是华为粉丝，也没买过华为的东西。 但是当前形势下，国内一个能打的都没有， 唯一一个敢站出来抗的，还要被自己人冷嘲热讽。 在座的都是程序员，不要拿国足的例子比，你也可以写代码的，有没有在自己的一亩三分地搞出成就呢。 如果可以，那就拿出本事把华为比下去啊，我们都以你为荣。 不如不行，请不要阴阳怪气好么，把愿意做事的人都弄死，也不能改变自己是废物的事实。 鸿蒙出来前说是ppt 出来后说是Android换壳 现在人家开放源码了，又来玩这些下三路，带风向抹黑。
@liujingjing5在查閱習近平的檔案時我們發現，習近平有一同父異母的哥哥習正寧（原名習富平），關於習正寧的情況卻語焉不詳，能查到的資料是，中國科技大學自動控制專業畢業，在陝西戶縣山溝某國防研究所工作過13年，後進入陝西省委組織部任副部長工作，後調海南省任政法書記兼司法廳長（有說其死時的職務是海南律師協會會長），1998年11月27日年因心臟病突發去世，享年57歲。 我們懷疑習正寧因心臟病死亡是偽造的，真相是習近平謀殺了他同父異母的哥哥。疑點如下： 1、心臟病一般都有先天性的家族遺傳因素，但習正甯其父習仲勳活了89歲，其母郝明珠是農村婦女，活了90歲，家族沒有心臟病史。而資料使用“突發”二字，也表示習正寧過去沒有心臟病史。 2、習正寧中科大自動控制專業畢業，生活樸素，為人正派，無吃喝嫖賭習慣，怎麼會50多歲就得心臟病？如果是他為黨勤懇工作、過勞而死，怎不見黨媒對其事蹟宣傳紀念？ 3、從身體外形來看，習近平比習正甯更不健康，如果要得心臟病，習近平發病的可能性反而更高。 4、關於習正甯的母親，檔案中寫道：“郝明珠於1935年12月和當時的陝甘邊蘇維埃主席習仲勳結婚，共同生活九年之後，1943年10月，由於雙方性格方面的問題而離婚，此時28歲的郝明珠依然年輕美貌，但從此以後未嫁，獨自艱辛撫養5個孩子中倖存的3個子女。” 而習仲勳的第二任妻子，“齊心（1926－ ），1943年4月與習仲勳相識。1943年冬天兩人論及婚嫁。兩人於1944年4月28日在綏德地委結婚，共育有四子女。”習仲勳還沒和郝明珠離婚時就和齊心勾上了，剛和郝明珠離婚馬上就娶了齊心，齊心比郝明珠要小10歲。用今天的話來說，齊心就是個小三，是小三上位。而郝明珠被拋棄後，僅28歲，獨自撫養三個子女，終生未嫁，這很不尋常，原因一方面是因為，她可能比較傳統，對習仲勳懷有舊情，另一方面的原因很可能是，她把希望寄託在和習仲勳生的三個孩子身上，特別是習正寧，希望他能承父業。 在中共黨內，名分不正是最忌諱的，習近平姐弟幾個，都是小三生的兒子，名聲非常不好聽，習近平視自己為習仲勳的接班人，不會允許自己家族旁出一脈。 5、習仲勳反對子女靠關係、走後門，曾親自取消過習正寧的北京調令，習正寧工作一向比習近平穩重踏實，為人正直，如果習正寧不死，習仲勳死後習正寧很可能上調北京，那樣的話習近平的大權夢就沒戲了。因此，除掉自己的哥哥習正甯就是不二選擇，而且必須趕在父親死之前。習正甯死後，習近平絕對會得到重視。習仲勳2002年去世，1998年時身體應該已不行了，那時正好是習近平下手的良機。 6、習正甯、習近平兄弟倆在上世紀80年代差不多同一時期南下，1998年時，習正甯在海南擔任司法廳廳長，而習近平已在福建工作了十多年，是時任省委副書記、福建高炮預備師第一政委、之前任福州軍分區政委，有軍方背景。福建離海南很近，又有軍方關係，想除掉他哥哥，他有這個能力和手段。 7、習正甯評價弟弟習近平“不但能吃苦，腦袋靈，會來事，而且跟上級下級的關係都處得非常好”， (見http://www.boxun.com/news/gb/china/2010/11/201011030518.shtml )，說明習近平鑽營、拍馬的功夫很到家，搞些非法交易不在話下。 8、習近平文革時陪父親挨過整，下鄉時為了防臭蟲咬，在席子下撒666粉，習近平的弟弟習遠平去看他，只睡了一晚就渾身起水皰，回到家後全身皮膚潰爛。習近平當年是吃過共匪苦頭的，年少時的非人折磨會讓人內心扭曲。 9、香港5書商被跨國跨境綁架回中國的事，習近平肯定是幕後黑手。這充分表明習近平做事不循常理、無法無天，只要手上有權利，做事會不擇手段。 10、可對照的一個案例是，已倒臺的前中共領導人薄熙來，薄縱容老婆毒殺了英國商人，事後偽裝成飲酒過度而死，而王立軍也說如果不逃走薄會殺他，說明這些領導人心黑手辣。習近平在某種程度上，同薄熙來很像。1998年刑事檢測技術還不夠完善，習近平讓人謀殺了習正寧後，偽裝成心臟病的假像是很可能的。 11、習正寧死亡的時代背景，是改革開放中後期，89學運9年後，是時，太子党依靠家族權勢，在南方經商官倒，胡作非為，習近平家族在南方沿海地區擁有大量公司資產，兩個姐姐也是外籍，這說明習近平家族十分腐敗，有做非法勾當的可能。 12、習近平執政後，似乎很焦慮，急於收權，表現同一般領導人很不一樣，他在害怕什麼？是否因自己曾犯下殺人案子惶惶不可終日？ 13、習正寧死的事，習家一直瞞著習仲勳，直到02年習老爺子歸西。說是“擔心習仲勳承受不住打擊”，實際上反而說明這家人互相之間的關係，習仲勳應該是很器重他的大兒子的，畢竟是他的骨血，但習近平及由齊心所出的一干姐弟，與他們那個同父異母的哥哥不和。 14、沒有查到習正甯有結婚成家的記錄，若習正寧是單身的話，死時將沒有家人在場，死無對證。 15、香港書商集體被中共跨國綁架，歸根結底還是他們出版了一些揭露習近平家族的書。如果任由他們深挖下去，習近平當年的罪案很有可能敗露，因此習近平下令不惜代價要打掉他們。 16、進一步搜索習正寧的資料後發現，習正甯年輕時被安排在習仲勳的老家陝西，是作為重點對象來培養的。作為親人，習近平家族沒有發表過關于習正寧的隻字片語，網上只有個別習正甯的舊同事朋友發表的回憶錄，如，http://www.huxianbbs.com/thread-56560-1-1.html 綜上，習近平殺害同父異母兄長的嫌疑很大。我們推測，習近平當時應該是雇請軍方人士去海南，兇手中有軍醫，習正甯為人老實規矩，不會有防備心，其職位也不高，身旁無警衛。兇手進入宅中並制服習正甯後，向習正寧體內注射了某種藥物，致使其心臟停跳，偽裝成心臟病突發的現場。 令計劃是很精明的人，任中辦主任時，如果他注意到上述疑點，或許調查過習近平，掌握習近平當年殺人犯罪的證據。 如果王歧山真心反腐的話，首先應該徹查習家貪腐問題，將習近平當年因權鬥弑兄的疑案查個水落石出！
@CMB-news-
A common well-being issue in open-source communities is the tendency of people to over-commit. Many contributors care deeply, at the risk of saying yes too often harming their well-being. Open-source communities are especially at risk, because many contributors work next to a full-time job. The contribution graph and the statistics on it, prominent on everyone's profile, basically rewards people for doing work on as many different days as possible, generally making more contributions, and making contributions on multiple days in a row without a break. Stepping away from our work regularly is not only important to uphold high quality work, but also to maintain our well-being. For example, I personally do not generally work in the weekends. That’s completely healthy. I take a step back from work and spend time on other things. But in the contribution graph it means I can never make a long streak, even though I do work virtually every day except weekends. So the graph motivates me to work in my weekends as well, and not take breaks. And when I see someone with a 416 day streak, it means they haven’t taken a break for a single day in over a year. Although everyone can make their own choices, it makes me very worried about their well-being. Any mechanism in our community that motivates people to avoid taking breaks and avoid stepping back, can be harmful to the well-being of contributors and is thereby harmful to open source as a whole. Even though it was probably introduced with the best intentions. If our interests are really in supporting open-source long-term, this graph should be removed or substantially changed so that it no longer punishes healthy behaviour. For example, what if we would give people achievements for taking breaks instead of working non-stop? I therefore want to ask you to consider removing or substantially changing the contribution graph and it's related statistics, to help guard the well-being of the contributors and the communities. I also wrote about this in a bit more detail on my blog: http://erik.io/blog/2016/04/01/how-github-contribution-graph-is-harmful/
@mxsashaThis technology is only going to be used for evil purposes. To deceive people, steal their money, possessions, undercover operations. Nothing good. It is already being used for scams like the pig-butchering plate, in which hundreds of thousands of lives around the world are being left without money, causing a lot of suffering.
@alonsoirThis might be an issue with drawing the practice screen as no one has encountered anything similar in game. However, I couldn't make it crash by coughing, shouting and growling into a regular headset microphone. Could you provide a backtrace from the crash with `gdb` debugger? Install gdb and either install `performous-dbg` or compile performous with debug symbols. Then run from terminal as follows: ``` gdb performous you are taken into a gdb debugger prompt run performous launches, make it crash bt paste the resulting output to this issue ```
We may need a FizzBuzz Community Edition one of these days. Marketing is saying that sales are plummeting.
------------- 𝕏
@wallentxSerious business logic should have at least two slightly different implementations to show maturity.
Proposal: A built-in Go error check function, `try` **This proposal has been [closed](https://github.com/golang/go/issues/32437#issuecomment-512035919). Thanks, everybody, for your input.** Before commenting, please read the detailed [design doc](https://github.com/golang/proposal/blob/master/design/32437-try-builtin.md) and see the [discussion summary as of June 6](https://github.com/golang/go/issues/32437#issuecomment-499261947), the [summary as of June 10](https://github.com/golang/go/issues/32437#issuecomment-500613160), and _most importantly the [advice on staying focussed](https://github.com/golang/go/issues/32437#issuecomment-501878888)_. Your question or suggestion may have already been answered or made. Thanks. We propose a new built-in function called `try`, designed specifically to eliminate the boilerplate `if` statements typically associated with error handling in Go. No other language changes are suggested. We advocate using the existing `defer` statement and standard library functions to help with augmenting or wrapping of errors. This minimal approach addresses most common scenarios while adding very little complexity to the language. The `try` built-in is easy to explain, straightforward to implement, orthogonal to other language constructs, and fully backward-compatible. It also leaves open a path to extending the mechanism, should we wish to do so in the future. [The text below has been edited to reflect the design doc more accurately.] The `try` built-in function takes a single expression as argument. The expression must evaluate to n+1 values (where n may be zero) where the last value must be of type `error`. It returns the first n values (if any) if the (final) error argument is nil, otherwise it returns from the enclosing function with that error. For instance, code such as ```Go f, err := os.Open(filename) if err != nil { return …, err // zero values for other results, if any } ``` can be simplified to ```Go f := try(os.Open(filename)) ``` `try` can only be used in a function which itself returns an `error` result, and that result must be the last result parameter of the enclosing function. This proposal reduces the original [draft design](https://go.googlesource.com/proposal/+/master/design/go2draft-error-handling.md) presented at last year's GopherCon to its essence. If error augmentation or wrapping is desired there are two approaches: Stick with the tried-and-true `if` statement, or, alternatively, “declare” an error handler with a `defer` statement: ```Go defer func() { if err != nil { // no error may have occurred - check for it err = … // wrap/augment error } }() ``` Here, `err` is the name of the error result of the enclosing function. In practice, suitable helper functions will reduce the declaration of an error handler to a one-liner. For instance ```Go defer fmt.HandleErrorf(&err, "copy %s %s", src, dst) ``` (where `fmt.HandleErrorf` decorates `*err`) reads well and can be implemented without the need for new language features. The main drawback of this approach is that the error result parameter needs to be named, possibly leading to less pretty APIs. Ultimately this is a matter of style, and we believe we will adapt to expecting the new style, much as we adapted to not having semicolons. In summary, `try` may seem unusual at first, but it is simply syntactic sugar tailor-made for one specific task, error handling with less boilerplate, and to handle that task well enough. As such it fits nicely into the philosophy of Go. `try` is not designed to address _all_ error handling situations; it is designed to handle the _most common_ case well, to keep the design simple and clear. Credits This proposal is strongly influenced by the feedback we have received so far. Specifically, it borrows ideas from: - [Key Parts of Error Handling](https://gist.github.com/PeterRK/4f59579c1162cdbc28086f6b5f7b4fa2), - issue [#31442](https://golang.org/issue/31442) - and, related, issue [#32219](https://golang.org/issue/32219). Detailed design doc https://github.com/golang/proposal/blob/master/design/32437-try-builtin.md `tryhard` tool for exploring impact of `try` https://github.com/griesemer/tryhard
@griesemer[A thread on the Git mailing list](https://lore.kernel.org/git/CAOAHyQwyXC1Z3v7BZAC+Bq6JBaM7FvBenA-1fcqeDV==apdWDg@mail.gmail.com/) made the cautious attempt at bringing this issue to attention: enough names in Git are non-inclusive to cause unintended consequences. Most prominently, the default name of the default branch. I create this ticket to track the progress of fixing this. While I want to fix it rather sooner than later, I want to abide by the saying "If you want to go fast, go alone, if you want to go far, go together". I want to go far on this. Any constructive comments are welcome!
I was playing for a while now with ways to make Scala's syntax indentation-based. I always admired the neatness of Python syntax and also found that F# has benefited greatly from its optional indentation-based syntax, so much so that nobody seems to use the original syntax anymore. I had some good conversations with @lihaoyi at Scala Exchange in 2015 about this. At the time, there were some issues with which I was not happy yet, notably how to elide braces of arguments to user-defined functions. I now have a proposal that addresses these issues. Proposal in a Nutshell - If certain keywords are followed by an end-of-line and an indented code block, assume block structure as if braces were inserted around the indented block. Example: ```scala def f(x: Int) = val y = x * x y + 1 ``` is treated as equivalent to ```scala def f(x: Int) = { val y = x * x y + 1 } ``` Or, for match expressions: ```scala xs match case x :: xs1 => ... case Nil => ... ``` Or, using the new syntax for if-then-else: ```scala if condition then println("taken") x else println("not taken") y ``` Or for for-expressions: ```scala for x x + 2 xs.collect with case P1 => E1 case P2 => E2 ``` Motivation Why use indentation-based syntax? - _Cleaner typography_: We are all used to write ```scala def f() = { ... } ``` But if we look at it with fresh eyes it's really quite weird how the braces embrace nothing but empty space. Geometrically the braces point _away_ from the enclosed space `...`. One could argue that other brace schemes are better. But there are good reasons why the scheme above is the most popular and in a sense arguments how to make braces look less awkward are themselves an indication that braces are fundamentally problematic. It's much simpler and cleaner to get rid of them: ```scala def f() = ... ``` - _Regain control of vertical white space_. Most of us are very particular how to organize horizontal whitespace, with strict rules for indentation and alignment. We are much less demanding on vertical whitespace. With braces, we cannot be, because vertical whitespace is fully determined by the number of closing braces. So two definitions might be separated by a single blank line, or by many (almost) blank lines if there are closing braces. One could avoid this by putting several closing braces on one line, but this looks weird and therefore has not caught on. - _Ease of learning_. There are [some powerful arguments](http://okasaki.blogspot.ch/2008/02/in-praise-of-mandatory-indentation-for.html) why indentation based syntax is easier to learn. - _Less prone to errors_. Braces are a weak signal, much weaker than indentation. So when brace structure and indentation differ, we misunderstand what was written. The code below exhibits a common problem: ```scala if (condition) println("something") action() ``` Indentation fools us to believe that `action` is executed only if `condition` is true. But of course that's not the case, because we forgot to add braces. - _Easier to change_. A situation like the one above happens particularly often when one adds the first `println` statement after the fact. To protect against modification problems like this, some people suggest to always write braces even if they only enclose a single statement or expression. But that sort of boilerplatey defensive programming is generally not considered good practice in Scala. - _Better vertical alignment_. In the most commonly used brace scheme, an if-then-else reads like this: ```scala if (cond1) { ... } else if (cond2) { ... } else { ... } ``` Instead of nicely aligned keywords, we find weird looking closing braces `}` at the beginning of the most important lines in this code. We are all used to this, but that does not make it good. I have recently changed my preferred style to: ```scala if (cond1) { ... } else if (cond2) { ... } else { ... } ``` This solves the alignment issue: The `if` and the `else`s are now vertically aligned. But it gives up even more control over vertical whitespace. Impediments What are the reasons for preferring braces over indentations? - _Provide visual clues where constructs end_. With pure indentation based syntax it is sometimes hard to tell how many levels of indentation are terminated at some point. In the code below, it is still easy to see that `j` is on the same nesting level as `g`. But if there were many more lines between the definitions, it might not be. ```scala def f = def g = def h = def i = 1 i def j = 2 ``` The proposal includes with _end comments_ a way to mitigate this issue. - _Susceptibility to off-by-one indentation_. It's easy to make a mistake so that indentation is off by a space to the left or the right. Without proper guards, indentation based syntax would interprete misalignment as nesting which can lead to errors that are very hard to diagnose. In the proposal, an indented block is always preceded by a keyword that _must_ be followed by a nested [Excerpt ends. Open the original thread for the full text.]
@odersky
@ShadowNineXThe experiment is over – read the [recap](https://feross.org/funding-experiment-recap/) here! Hey folks! 👋 I've already spoken to a few of you about this idea, but I'd like to share it with the broader community now that `standard` 14 has shipped. **Background:** I think that the current model of sustaining open source is not working and we need more experimentation. This is one such experiment. **What's the experiment?** Whenever `standard` 14 is installed, we'll display a message from a company that supports open source. The sponsorship pays directly for maintainer time. That is, writing new features, fixing bugs, answering user questions, and improving documentation. **What's the goal?** My goal with this experiment is to make `standard` healthier. If we learn that the experiment works, perhaps we can help make all open source healthier, too. For complex reasons, companies are generally hesitant or unwilling to fund OSS directly. When it does happen, it's never enough and it never reaches packages which are transitive dependencies (i.e. packages that no one installs explicitly and therefore no one knows exists). Essentially, we have a public good which is consumed by huge numbers of users, but which almost no one pays for. Fortunately, there exists a funding model that usually works for public goods like this – ads. The goal of this experiment is to answer the question: Can we use ethical ads – ads that don't track users or collect data – to fund open source software? **What does the code do?** The code for this experiment is available here: [`feross/funding`](https://github.com/feross/funding). Essentially, it calls `console.log()` on some text. There is no tracking, data collecting, or unexpected behavior. You can look at the code to verify – indeed, this is the beauty of open source! **What will the funds be used for?** The funds raised so far ($2,000) have paid for Feross's time to [release Standard 14](https://standardjs.com/changelog.html#1400---2019-08-19) which has taken around five days. If we are able to raise additional funds, the next thing I'd like to focus on is out-of-the-box TypeScript support in StandardJS (one of the most common feature requests!) and modernizing the various text editor plugins (many of which are currently unmaintained). If others in the community are interested in taking the lead on any of these issues, I'd like to direct some funds to you. Feedback welcome! --- EDIT: This thread is now locked :lock: For why + next steps, [scroll to the end >>](https://github.com/standard/standard/issues/1381#issuecomment-524589455) EDIT: The experiment is over – Feross posted [a recap](https://feross.org/funding-experiment-recap/) on his blog
@feross(Note: I'll update the description here as the discussion evolves) Background It was asked multiple times by activists in the area of inclusiveness for Redis to migrate to a different terminology than *master-slave*, specifically one that has no reference to slavery. Personally I [do not consider the effort worthwhile](http://antirez.com/news/122), but this is my personal opinion. On the other hand different Twitter threads, especially an exchange with DHH, together with many accounts of people starting to suggest to never use Redis again, made me reflecting about a few things. Specifically I think that it could be a problem for engineers just willing to use Redis because they believe is the right too for the job, to apply it in certain workplaces, because the terminology used in Redis may be a problem. I don't want, as a result of my ideas, to create problems to the Redis community. At the same time once I started to be more open to the possibility of renaming such terms, I started to receive private complains from *multiple* people that contribute to the project for years, that are annoyed by the fact we'll have to do work that will not change the system in any way, and that will be costly, create compatibility issues. My idea is to find a middle ground between all those things, because there are multiple issues caused by the change of terminology: * PRs will no longer apply. * We have commands such as `INFO` and `ROLE` that reply with protocol containing the *slave* term. * There are 1500 occurrences inside the source code of the term *slave*. * People having private trees and merging things as needed will get a lot of problems. So this change can potentially create a lot of issues. Moreover many folks on Twitter do not understand the Redis culture of backward compatibility. Redis 5 that is now release candidate is backward compatible with the *first stable version of Redis released*, to the point it's a drop in replacement. This culture traditionally made sure that upgrade operations are simple, there is no useless work to do in the client side, and so forth. This is something big to consider. Possible soltuion Yet I want to give a signal, because in a [Twitter pool I started](https://twitter.com/antirez/status/1038094104129937408) too many people asked for the terminology to be changed. While I handle the Redis community, I do not want to be its *king*, I need to serve people here. A signal however does not need to create a number of problems across the community, so this is what I propose to do. Short term changes To start we do the following: 1. Change the documentation to refer to master-replica. If we take master, which should not offend anybody in 2018 (next year we'll see...), at least there are less things to change. Replicas is very used and is also used inside Redis Cluster already. 2. Alias SLAVEOF to REPLICAOF. You can still use SLAVEOF but now there is an option. 3. Refer to REPLICAOF inside the documentation. 4. Change the configuration directive as well from `slaveof` to `replicaof`. 5. Leave all the internals as they are mentioning still slave at source level as a first step. Changing all those things now would be a big issue because we are at release candidate state, and there are too many pending PRs. 6. Continue to reply with `slave` to INFO and ROLE, because this is a major breakage, for now. Long term changes 1. At some point in the future, write an alternative to INFO, since anyway INFO is not the future of Redis data gathering... It's too limited, provides too many info at once, clients need to have to parse it. We'll design a new command, and in the new command we'll not refer to slaves, but to replicas. 2. When we are going to break a lot of things anyway, like for example with the inclusion of RESPv3, also change the `ROLE` command to output replica instead of slave. If clients detect it's a RESPv3 server, they now that ROLE will reply differently, that is, instead of "slave" it will reply with "replica". 3. The first thing that we'll have to replace a lot of things internally, because of some technical reason, so that many PRs will not apply anyway, switch the variable and function names as well. However **this is not acceptable to do as a change out of context**, because it will cause really a lot of problems. We have to put this inside a much larger change somewhere. We'll provide no ETA for the second step, and I hope the community will understand our technical issues here. However I hope that people will appreciate that at least somebody is listening here. Certain people demanding this change are vocal and hostile, but I saw a huge amount of people on Twitter just asking peacefully to see some improvement. One thing is for sure: the master-slave terminology is not going to be used in the future, so let's make this change together, and move forward to our actual work, that is, to make Redis better and available. Please provide your POV if you are among the contributors of Redis I know this may seem gross, but I would like most comments here to be provided by people that did something in Redis-land in the latest few years. People sending PRs, opening issues, writing a client library, using Redis at scale and provided hints regularly, and so forth, don't just comment if you are a casual Github user jumping here to say "change it!" or "don't change it". This will just create noise. Thanks. **Off topic and offensive comments will be removed**
@antirezIn the past this was an editor. Since some years it has turned into a political meme part. I suggest to drop the political agenda and focus on the editor; or alternatively, if you don't want to work on notepad++ anymore, to officially hand it over to other people who can handle the project better than you can. I recently read on reddit that you controlled remote computers after charlie hebdo. This is by definition a trojan. Something has to change. Notepad++ deserves a new main developer.
@rubyFeedbackProposal Details Background As discussed in the [introduction to an earlier, declined, proposal](https://go.googlesource.com/proposal/+/master/design/go2draft-error-handling-overview.md), Go programs have a lot of error checking code. In [surveys](https://go.dev/blog/survey2024-h1-results) error handling is listed as the biggest specific challenge people face using Go today. There have been [many proposals](https://github.com/golang/go/issues?q=+is%3Aissue+label%3Aerror-handling) to address this, summarized in a [meta-proposal](https://go.dev/issue/40432). This is yet another such proposal. This proposal has some similarities to [onerr return](https://go.dev/issue/32848), [add "or err: statement" after function calls for error handling](https://go.dev/issue/33029), and [use ? simplify handling of multiple-return-values](https://go.dev/issue/33074). It is in some ways a reworking of [simplify error handling with || err suffix](https://go.dev/issue/21161). There are probably a number of other proposals that fed into this one even if I can't remember them now. The goal of this proposal is to introduce a new syntax that reduces the amount of code required to check errors in the normal case, without obscuring flow of control. New syntax This section is an informal description of the proposal, with examples. A more precise description appears below. I propose permitting statements of the form ```Go r, err := SomeFunction() if err != nil { return fmt.Errorf("something failed: %v", err) } ``` to be written as ```Go r := SomeFunction() ? { return fmt.Errorf("something failed: %v", err) } ``` The `?` absorbs the error result of the function. It introduces a new block, which is executed if the error result is not `nil`. Within the new block, the identifier `err` refers to the absorbed error result. Similarly, statements of the form ```Go if err := SomeFunction2(); err != nil { return fmt.Errorf("something else failed: %v", err) } ``` may be written as ```Go SomeFunction2() ? { return fmt.Errorf("something else failed: %v", err) } ``` Further, I propose that the block following the `?` is optional. If the block is omitted, it acts as though there were a block that simply returns the error from the function. For example, code like ```Go if err := SomeFunction2(); err != nil { return err } ``` may in many cases be written as ```Go SomeFunction2() ? ``` Formal proposal This section presents the formal proposal. An assignment or expression statement may be followed by a question mark (`?`). The question mark is a new syntactic element, the first permitted use of `?` in Go outside of string and character constants. The `?` causes conditional execution similar to an `if` statement. A `?` at the end of a line causes a semicolon to be [automatically inserted](https://go.dev/ref/spec#Semicolons) after it. A `?` uses a value as described below, referred to here as the _qvalue_. For a `?` after an assignment statement, the qvalue is the last of the values produced by the right hand side of the assignment. The number of variables on the left hand side of the assignment must be one less than the number of values produced by the right hand side (the right hand side values may come from a function call as usual). It is not valid to use a `?` if there is only one value on the right hand side of the assignment. For a `?` after an expression statement the qvalue is the last of the values of the expression. It is not valid to use a `?` after an expression statement that has no values. The qvalue must be of interface type and must implement the [predeclared type `error`](https://go.dev/ref/spec#Errors); that is, it must have the method `Error() string`. In most cases it will simply be of type `error`. A `?` is optionally followed by a block. The block may be omitted if the statement using `?` appears in the body of a function, and the enclosing function has at least one result, and the qvalue is assignable to the last result (this means that the type of the last result must implement the predeclared type `error`, and will often simply be `error`). Execution of the `?` depends on the qvalue. If the qvalue is `nil`, execution proceeds as normal, skipping over the block if there is one. If the `?` is not followed by a block, and the qvalue is not `nil`, then the function returns immediately. The qvalue is assigned to the final result. If the other results (if any) are named, they retain their current values. If they are not named, they are set to the zero value of their type. The results are then returned. Deferred functions are executed as usual. If the `?` is followed by a block, and the qvalue is not `nil`, then the block is executed. Within the block a new variable `err` is implicitly declared, possibly shadowing other variables named `err`. The value and type of this `err` variable will be those of the qvalue. That completes the proposal. Examples ```Go func Run() error { Start() ? // returns error from Start if not nil Wait() ? // returns error from Wait if not nil return nil } ``` ```Go func CopyFile(src, dst string) error { r := os.Open(src) ? { return fmt.Errorf("copy %s %s: %v", src, dst, err) } defer r.Close() w := os.Create(dst) ? { return fmt.Errorf("copy %s %s: %v", src, dst, err) } io.Copy(w, r) ? { w.Close() os.Remove(dst) return fmt.Errorf("copy %s %s: %v", src, dst, err) } w.Close() ? { os.Remove(dst) return fmt.Errorf("copy %s %s: %v", src, dst, err) } } ``` ```Go func MustOpen(n string) *os.File { f := os.Open(n) ? { panic(err) } return f } ``` ```Go func TestFileData(t *testing.T) { f := os.Open("testfile") ? { t.Fatal(err) } ... } ``` ```Go func CreateIfNotExist(name string) error { f, err := os.OpenFile(name, os.O_EXCL|os.O_WRONLY, 0o666) if errors.Is(err, fs.ErrExist) { return nil } err ? // returns err if it is not nil // write to f ... } ``` Di [Excerpt ends. Open the original thread for the full text.]
@ianlancetaylorWhat happened? -------------- In 1.110, we added a setting to add Copilot as coauthor in commit messages by appending `Co-authored-by: Copilot copilot@github.com`. The setting `git.addAICoAuthor` has three different values: * `off` - no attribution no matter whether Copilot assisted or not with the code in this commit * `chatAndAgent` - add attribution if the commit contains code that was generated using the chat feature * `all` - add attribution if the commit contains any kind of AI-generated code (chat, inline completions, NES) The default value of the setting was `off`. In 1.117 (public rollout started 4/22), we changed the setting default to `all`. There was a bug in the code that was not found in testing that attributed non-Copilot code completions to Copilot. This resulted in commit messages containing `Co-authored-by: Copilot copilot@github.com` even when the `disableAIfeatures` setting was turned on. This issue is tracked in https://github.com/microsoft/vscode/issues/313064. Because of the bug, we changed the setting value to `chatAndAgent` in 1.118 (public rollout started 4/29). You can disable the functionality by explicitly turning the feature off in user settings: `"git.addAICoAuthor": "off"`. What is happening now? ---------------------- 1. We reverted the default for the AI attribution feature back to `off`. We also ensure that the feature is disabled when `disableAIFeatures` is set to true no matter the value of `git.addAICoAuthor`. This was done in https://github.com/microsoft/vscode/pull/313931. These fixes will be tested and released in 1.119 (public rollout starting 5/6). 2. We are reviewing our test and release processes for gaps to ensure we prevent similar issues in the future. What will happen to the feature? -------------------------------- Thank you for all your feedback. We'll make/retain the following changes: 1. The attribution is never applied for changes that are not AI-related. 2. Before adding a commit trailer, the user will have to give consent, no matter the default value of the setting. 3. We'll review the attribution message. A better approach might be using the approach of "assisted-by" attribution as described in https://github.com/microsoft/vscode/issues/313962. 4. The same approach would allow us to add model information as tracked in https://github.com/microsoft/vscode/issues/297353. We will work on these improvements and iterate with the community via issues and discussions on GitHub to make sure the bugs are fixed and concerns are addressed.
@dmitrivMSPlease, for the love of god. Can you stop releasing breaking changes on minor releases? It's absolutely infuriating that you guys keep doing this over and over again with complete disregard for people downstream using this package in production environments. PLEASE STOP LEARN HOW TO USE SEMVER PROPERLY WHAT IS EVEN THE POINT OF USING SEMVER IF YOU DON'T GIVE A FLYING FUCK? Have you heard of backwards compatibility? Do you even care? This is not a serious project.
@l0gicgate> I don't fc_i_ng know why everyone is saying that i'm retarded we dont expect retards to be self aware dw
@i-am-called-glitchyOver the past several months, the .NET team has evaluated ways to evolve the .NET tooling ecosystem and incorporate more capabilities into VS Code. Currently, the C# experience in VS Code is powered by OmniSharp. This is thanks to the leadership of[ Filip Wojcieszyn,](https://github.com/filipw)[ David Driscoll](https://github.com/david-driscoll), [Martin Björkström](https://github.com/bjorkstromm), and also, Jason Imison, who originally started the OmniSharp project over eight years ago. OmniSharp generated a lot of excitement by bringing the C# experience to VS Code, using the APIs and protocols that were available at that time. VS Code has since matured and today, the[ Language Server Protocol](https://microsoft.github.io/language-server-protocol/) (LSP) has become the standard mechanism through which modern developer tools speak to one another. We believe that moving the C# extension to LSP will help us accomplish our goal of creating an extensible and flexible tooling environment which easily integrates new experiences into C# for VS Code. As we move towards a more dynamic future for the C# experience in VS Code, we intend to switch the extension to communicate entirely using LSP and plan to update the existing OmniSharp component to communicate in this manner as well. Utilizing LSP will allow us to bring innovative new features to the C# for VS Code extension. This includes making advanced capabilities available and, in some cases, closed-source experiences, such as IntelliCode. We plan to create a new “LSP Tools Host” component (not an official name 😊), which integrates both open-source components, like [Roslyn](https://github.com/dotnet/roslyn) and [Razor](https://github.com/dotnet/razor-tooling), with closed-source components, offering a wider array of tooling capabilities. Once the “LSP Tools Host” is complete, this will become the default experience for the C# for VS Code extension. Existing users will be able to choose between the open-source OmniSharp powered system that exists today, or the new “'LSP Tools Host” which will provide access to additional experiences. The “LSP Tools Host” will not be open-sourced, but we plan to communicate with the community along the way to help guide our future plans. We'd like to again thank everyone at OmniSharp and [all the contributors](https://github.com/OmniSharp/omnisharp-vscode/graphs/contributors) to this project for doing such an incredible job in helping to bring the C# developer experience to VS Code. We have been collaborating with the OmniSharp team and will be working with them to ensure that this process is smooth, and plan to work with them, as well as the broader community, in order to drive forward this exciting new future for .NET tooling. Next Steps (these will ideally be issues that will be trackable, timelines of these may vary) - [ ] Update the C# for VS Code extension to communicate with OmniSharp Server via LSP by default. - [x] Switch the C# for VS Code extension to use the new “LSP Tools Host” by default and allow users to choose an alternative language server. - [x] Ship the C# for VS Code extension with these new defaults bundled with more features “out of the box”. - [x] Move the C# for VS Code extension from github.com/OmniSharp/omnisharp-vscode to github.com/dotnet/vscode-csharp and have Microsoft keep this up to date and ship it. This move will enable us to easily integrate and reuse the existing dotnet infrastructure assets, like our shared building, testing, and publishing system, and will reduce overall engineering costs. __UPDATE__: Thanks for the passionate feedback. I’d like to clarify a few things stated in the feedback that we failed to make clear. The LSP implementations for Razor and C# will remain open-source (Roslyn and Razor) as they are today. The VS Code C# extension (ms-dotnettools.csharp) itself will also remain open-source. That which is open source today remains so and in active OSS development. This ensures that others outside of VS Code that use LSP continue to have access to C#. This new host component is the bridge between open and closed source functionality letting us deliver both at the same time.
@timheuerPeople shouldn't guess gender and gendered pronouns. Neither should software. Would you write code to guess someone's race using heuristics?
My installation log isn't for advertising space. If you want donations, please do the right thing and promote yourself in places where appropriate. My logs are long enough as it is without this. The right thing to do is to remove it. EDIT: An unmaintained fork is available: `core-js-without-ads`
@jpike88Go HTTP implements the 418 I'm a Teapot status code in go/src/net/http/status.go. Its reference is RFC7168, but really came from RFC2324, Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0). Note the title - HTCPCP/1.0 is not HTTP/1.x. HTCPCP was an April 1 joke by Larry to illustrate how people were abusing HTTP in various ways. Ironically, it's not being used to abuse HTTP itself -- people are implementing parts of HTCPCP in their HTTP stacks. Node's support for the HTCPCP 418 I'm a Teapot status code (see ) has been used as an argument in the HTTP Working Group to preclude use of 418 in HTTP for real-world purposes. While we have a number of spare 4xx HTTP status codes that are unregistered now, the semantics of HTTP are something that (hopefully) are going to last for a long time, so one day we may need this code point. Please consider removing support for 418 from Go HTTP, since it's not a HTTP status code (even by its own definition). I know it's amusing, I know that a few people have knocked up implementations for fun, but it shouldn't pollute the core protocol; folks can extend Go easily enough if they want to play with non-standard semantics. Thanks, /cc @bradfitz
@mnotAs I have **no possibility** to change anything on the website, I will post link to my open letter here. [My open letter to the community of PhantomJS](https://docs.google.com/document/d/1egB4CarmBN3HfntWJ7n1ETB-uDQBAwS5taPbKtxMloQ/edit?usp=sharing). As I said on Skype yesterday @ariya - I have edited it. Many thanks,
@ghostNode implements the `418 I'm a Teapot` status code in a few places. Its source is [RFC2324, Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)](https://www.ietf.org/rfc/rfc2324.txt). Note the title - `HTCPCP/1.0` is *not* `HTTP/1.x`. HTCPCP was an April 1 joke by Larry to illustrate how people were abusing HTTP in various ways. Ironically, it's not being used to abuse HTTP itself -- people are implementing parts of HTCPCP in their HTTP stacks. In particular, Node's support for the HTCPCP `418 I'm a Teapot` status code has been used as an argument in the HTTP Working Group to preclude use of 418 in HTTP for real-world purposes. While we have a number of spare 4xx HTTP status codes that are unregistered now, the semantics of HTTP are something that (hopefully) are going to last for a long time, so one day we may need this code point. Please consider removing support for 418 from Node, since it's not a HTTP status code (even by its own definition). I know it's amusing, I know that a few people have knocked up implementations for fun, but it shouldn't pollute the core protocol; folks can extend Node easily enough if they want to play with non-standard semantics. Thanks, /cc @domenic @jasnell
@mnotThank you for considering to add a new brand/company icon to Lucide. But, we're no longer accepting new brand icons. **To know more:** https://github.com/feathericons/feather/issues/763 **We recommend using:** https://github.com/simple-icons/simple-icons We've an [active issue](https://github.com/lucide-icons/lucide/issues/94) for removal of existing brand icons, please do share your feedback.
@mittalyashuDescription This bug appeared in February with patch 7.31. It makes it very hard to play. It consists in the fact that Battle Pass has not yet been released, which is why I have no desire to play. Example Match ID (and possibly Timestamp) _No response_ Screenshots
@ChuchellloThis is a call for consensus on the proposal Move DOM 4.1 to Candidate Recommendation. Please reply before the end of Sunday 25 March 2018 by either providing a thumbs-up to this issue, or a comment explaining the reason for objecting. Silence will be considered assent to the outcome.
@chaals同学， 作为一名清华的学生，一名程序员，应该你知道在当今环境下，一个没有被墙的github对中国软件行业有多重要，在github发表这类在社会敏感内容，对于真正解决问题毫无帮助，但却会有可能导致github从此远离中国，这带来损失有多大，相信不是一句道歉就可以解决的。 我也希望这些事情得到传播，让正义得以申张，但是使用github做为武器的方式，图一时之快却对中国软件技术发展带来巨大的伤害，相信是我们都不希望看到的。 其实到目前为止，微博和微信并没有阻止内容的传播，我们在微博和微信上仍然到处都可以看到和搜索到，何必要在这里发表呢？ 建议尽快删除，还请深思！
@xwarrior
