Datasets:

loubnabnl

/

pre-processed-issues

like 0

{ "number": 2193, "repo": "lambda-serverless-api", "user_login": "blackflux" }

[ { "action": "opened", "author": "MrsFlux", "comment_id": null, "datetime": 1615960372000, "masked_author": "username_0", "text": "Automatically created by Git-Ally", "title": "[Gally]: master <- dev", "type": "issue" }, { "action": "created", "author": "MrsFlux", "comment_id": 801194105, "datetime": 1615996200000, "masked_author": "username_0", "text": ":tada: This PR is included in version 8.0.5 :tada:\n\nThe release is available on:\n- [npm package (@latest dist-tag)](https://www.npmjs.com/package/lambda-serverless-api/v/8.0.5)\n- [GitHub release](https://github.com/blackflux/lambda-serverless-api/releases/tag/v8.0.5)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "aaitor", "comment_id": null, "datetime": 1614684663000, "masked_author": "username_0", "text": "NFT Sales (NFTSalesTemplate) will require to execute the following conditions:\r\n- [ ] Owner lock the NFTs to sell in an escrow contract\r\n- [ ] Consumer lock payment via the existing Lock Reward condition\r\n- [ ] Owner or Provider Transfer the NFTs via the new condition\r\n- [ ] Whoever can distribute rewards to the owner (and royalties to the original creator)", "title": "Create new NFT Sales template", "type": "issue" }, { "action": "closed", "author": "aaitor", "comment_id": null, "datetime": 1616070899000, "masked_author": "username_0", "text": "", "title": null, "type": "issue" } ]

{ "number": 6, "repo": "esp-idf", "user_login": "zephyrproject-rtos" }

[ { "action": "opened", "author": "sylvioalves", "comment_id": null, "datetime": 1607020002000, "masked_author": "username_0", "text": "This PR is the baseline for the upcoming commits related to ESP32 Development ([ESP Development](https://github.com/zephyrproject-rtos/zephyr/issues/29394))\r\n\r\nAs from [here](https://github.com/zephyrproject-rtos/esp-idf/issues/4), we keep current esp-idf structure and not creating a new repo/branch.", "title": "esp32: add wifi hal interface and update to esp-idf v4.2 ", "type": "issue" }, { "action": "created", "author": "sylvioalves", "comment_id": 738726794, "datetime": 1607080477000, "masked_author": "username_0", "text": "@nashif, once approved, we need to sync with [this](https://github.com/zephyrproject-rtos/zephyr/pull/30424).", "title": null, "type": "comment" }, { "action": "created", "author": "carlescufi", "comment_id": 738891642, "datetime": 1607100711000, "masked_author": "username_1", "text": "@username_0 thanks, could you please rebase this properly so that only the commits relevant to this PR are shown?", "title": null, "type": "comment" }, { "action": "created", "author": "sylvioalves", "comment_id": 740666148, "datetime": 1607439079000, "masked_author": "username_0", "text": "Closing this PR as we will move to `hal_espressif`.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "adamchenwei", "comment_id": null, "datetime": 1618848093000, "masked_author": "username_0", "text": "", "title": "is this same as the Lyft's refactorator? or its just same name?", "type": "issue" }, { "action": "created", "author": "johnno1962", "comment_id": 822589283, "datetime": 1618848433000, "masked_author": "username_1", "text": "I don't think so. What is the link to Lyft's refactorator?", "title": null, "type": "comment" }, { "action": "created", "author": "adamchenwei", "comment_id": 822590998, "datetime": 1618848571000, "masked_author": "username_0", "text": "I can't find one that's reason I popup here :D haha thanks for the quick verification!", "title": null, "type": "comment" }, { "action": "closed", "author": "johnno1962", "comment_id": null, "datetime": 1619243351000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

{ "number": 197, "repo": "arikawa", "user_login": "diamondburned" }

[ { "action": "opened", "author": "twoscott", "comment_id": null, "datetime": 1621566078000, "masked_author": "username_0", "text": "Just some methods I thought would be convenient. I haven't used most of these structs yet but I figured the CreatedAt methods should be on any object that has a snowflake directly identifying it (not sure if I missed any).", "title": "discord: Helper methods & doc fixes", "type": "issue" }, { "action": "created", "author": "diamondburned", "comment_id": 845617473, "datetime": 1621566170000, "masked_author": "username_1", "text": "Is there a reason why `CreatedAt` returns `discord.Timestamp` and not `time.Time`?", "title": null, "type": "comment" }, { "action": "created", "author": "twoscott", "comment_id": 845618929, "datetime": 1621566454000, "masked_author": "username_0", "text": "I honestly just wasn't sure which to use, figured you might prefer to use `discord.Timestamp` to keep consistency but I could see `time.Time` working just as well if not better", "title": null, "type": "comment" }, { "action": "created", "author": "diamondburned", "comment_id": 845653329, "datetime": 1621573093000, "masked_author": "username_1", "text": "`discord.Timestamp` would indeed be more consistent, but since these are methods, it doesn't really matter. The type was made just so JSON can be marshaled properly, so it doesn't matter as far as usage goes.", "title": null, "type": "comment" } ]

{ "number": 266, "repo": "7-billion-humans-solutions", "user_login": "hingston" }

[ { "action": "opened", "author": "danrudmin", "comment_id": null, "datetime": 1610785007000, "masked_author": "username_0", "text": "1 fewer steps (this is DMR)", "title": "Update Year 62 - The Sorting Floor (size).txt", "type": "issue" }, { "action": "created", "author": "hingston", "comment_id": 846567897, "datetime": 1621778439000, "masked_author": "username_1", "text": "Sorry about the slow response!", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "omacesc", "comment_id": null, "datetime": 1565607645000, "masked_author": "username_0", "text": "* **I'm submitting a ...**\r\n - [ ] bug report\r\n - [ ] feature request\r\n - [x] support request\r\n\r\n* **Do you want to request a *feature* or report a *bug*?**\r\nReport a bug\r\n\r\n* **What is the current behavior?**\r\nWhen create a new log group, no put the correct retention\r\n\r\n* **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem**\r\nI use laravel 5.5 monolog\r\n\r\n* **What is the expected behavior?**\r\nPut the correct number in retention\r\n\r\n* **What is the motivation / use case for changing the behavior?**\r\n\r\n* **Please tell about your environment:**\r\n \r\n - PHP Version: 7.1\r\n - Operating system (distro): debian\r\n - Application mode (web app / cli app / daemon cli app): web app\r\n\r\n* **Other information** (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links to have context, eg. stackoverflow, etc)\r\nLaravel 5.5\r\n\r\n`$cwClient = App::make('aws')->createClient('CloudWatchLogs');\r\n $cwGroupName = config('laravel-monolog-ext.drivers.cloudwatch.group');\r\n $cwStreamNameApp = 'laravel-' . now()->toDateString() . '.log';\r\n $cwRetentionDays = config('laravel-monolog-ext.drivers.cloudwatch.retention');\r\n $cwLevel = config('laravel-monolog-ext.drivers.cloudwatch.level');\r\n $this->cwHandlerApp = new CloudWatch($cwClient, $cwGroupName, $cwStreamNameApp, $cwRetentionDays, 10000, [], $cwLevel);\r\n$monolog->pushHandler($this->cwHandlerApp);`\r\n\r\nThe user AWS have full access in CloudWatch Logs", "title": "No apply retention days", "type": "issue" }, { "action": "closed", "author": "maxbanton", "comment_id": null, "datetime": 1605628937000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "AlexeyKurakin", "comment_id": null, "datetime": 1611956535000, "masked_author": "username_0", "text": "Typically user has to specify list of variables used by a function:\r\n\r\n```python\r\nmodel = WideResNet(nin=3, nclass=10, depth=wrn_depth, width=wrn_width)\r\n\r\n@objax.Function.with_vars(model.vars())\r\ndef loss_fn(x, label):\r\n logit = model(x, training=True)\r\n return objax.functional.loss.cross_entropy_logits_sparse(\r\n logit, label).mean()\r\n```\r\n\r\nThe goal of the tracing is to automatically detect used variables, so the code could look like following:\r\n```python\r\nmodel = WideResNet(nin=3, nclass=10, depth=wrn_depth, width=wrn_width)\r\n\r\n@objax.Function.auto_vars\r\ndef loss_fn(x, label):\r\n logit = model(x, training=True)\r\n return objax.functional.loss.cross_entropy_logits_sparse(\r\n logit, label).mean()\r\n```", "title": "Prototype automatic tracing of variables used by a function", "type": "issue" }, { "action": "closed", "author": "AlexeyKurakin", "comment_id": null, "datetime": 1615586614000, "masked_author": "username_0", "text": "", "title": null, "type": "issue" } ]

{ "number": 1255, "repo": "serenity", "user_login": "serenity-rs" }

[ { "action": "opened", "author": "FelixMcFelix", "comment_id": null, "datetime": 1615150586000, "masked_author": "username_0", "text": "## Description\r\n\r\nThis removes a `let _ = ...` which was silently causing some resume failures to become permanent, causing the shard to crash the next time it attempted to use its (closed) WS client. This is replaced with code to trigger a further resume and/or reidentification attempt.\r\n\r\nIn the worst case, this will attempt one further resume before \"promoting\" the resume into a full reidentify. The `ShardQueuer` is then already responsible for repeated full reidentify attempts from that point on.\r\n\r\n## Type of Change\r\n\r\nThis fixes a (rare) bug in the shard runner triggered when TLS or socket initialisation spuriously fails.\r\n\r\n## How Has This Been Tested?\r\n\r\nThis has been tested by (locally) adding in extra `ShardRunnerMessage` types to test and access the new code paths individually. The underlying bug has not been observed (using the new `warn!`/`debug!` invocations); I haven't seen this bug reoccur in over two weeks, in spite of it being a nightly occurrence around that time (most likely due to my hosting provider).", "title": "Reconnect in event of failed ShardActions", "type": "issue" }, { "action": "created", "author": "FelixMcFelix", "comment_id": 800215530, "datetime": 1615897525000, "masked_author": "username_0", "text": "This seems to now catch and correctly act on serial failure states as required. I observed this in my logs this morning:\r\n\r\n```\r\nMar 16 07:09:58.139 DEBUG run: serenity::client::bridge::gateway::shard_runner: [ShardRunner [0, 1]] Reconnecting due to error performing Reconnect(Resume): Tungstenite(Io(Custom { kind: Other, error: Ssl(Error { code: ErrorCode(5), cause: None }, X509VerifyResult { code: 0, error: \"ok\" }) }))\r\nMar 16 07:09:58.145 DEBUG run:resume: serenity::gateway::shard: [Shard [0, 1]] Attempting to resume\r\nMar 16 07:09:58.145 DEBUG run:resume:initialize: serenity::gateway::shard: [Shard [0, 1]] Initializing.\r\nMar 16 07:10:32.111 WARN run: serenity::client::bridge::gateway::shard_runner: [ShardRunner [0, 1]] Resume failed, reidentifying: Tungstenite(Io(Os { code: 32, kind: BrokenPipe, message: \"Broken pipe\" }))\r\nMar 16 07:10:32.115 DEBUG run:request_restart: serenity::client::bridge::gateway::shard_runner: [ShardRunner [0, 1]] Requesting restart\r\nMar 16 07:10:32.119 DEBUG serenity::client::bridge::gateway::shard_queuer: [ShardRunner [0, 1]] Stopping\r\nMar 16 07:10:32.134 INFO start:start_connection{shard_data=[0, 0, 1]}:run:restart{shard_id=ShardId(0)}: serenity::client::bridge::gateway::shard_manager: Restarting shard 0\r\nMar 16 07:10:32.138 INFO start:start_connection{shard_data=[0, 0, 1]}:run:restart{shard_id=ShardId(0)}:shutdown{shard_id=ShardId(0) code=4000}: serenity::client::bridge::gateway::shard_manager: Shutting down shard 0\r\nMar 16 07:10:32.138 DEBUG run: serenity::client::bridge::gateway::shard_queuer: [Shard Queuer] Received to shutdown shard 0 with 4000.\r\nMar 16 07:10:32.139 INFO run:shutdown{shard_id=ShardId(0) code=4000}: serenity::client::bridge::gateway::shard_queuer: Shutting down shard 0\r\nMar 16 07:10:32.139 WARN run:shutdown{shard_id=ShardId(0) code=4000}: serenity::client::bridge::gateway::shard_queuer: Failed to cleanly shutdown shard 0 when sending message to shard runner: TrySendError { kind: Disconnected }\r\nMar 16 07:10:37.139 WARN start:start_connection{shard_data=[0, 0, 1]}:run:restart{shard_id=ShardId(0)}:shutdown{shard_id=ShardId(0) code=4000}: serenity::client::bridge::gateway::shard_manager: Failed to cleanly shutdown shard 0, reached timeout: Elapsed(())\r\nMar 16 07:10:37.142 INFO start:start_connection{shard_data=[0, 0, 1]}:run:restart{shard_id=ShardId(0)}:boot{shard_info=[ShardId(0), ShardId(1)]}: serenity::client::bridge::gateway::shard_manager: Telling shard queuer to start shard 0\r\nMar 16 07:10:37.142 DEBUG run: serenity::client::bridge::gateway::shard_queuer: [Shard Queuer] Received to start shard 0 of 1. Mar 16 07:10:37.142 DEBUG run:checked_start{id=0 total=1}: serenity::client::bridge::gateway::shard_queuer: [Shard Queuer] Checked start for shard 0 out of 1\r\nMar 16 07:10:37.518 DEBUG run:checked_start{id=0 total=1}:start{shard_id=0 shard_total=1}:create_native_tls_client{url=Url { scheme: \"wss\", username: \"\", password: None, host: Some(Domain(\"gateway.discord.gg\")), port: None, path: \"/\", query: Some(\"v=8\"), fragment: None }}: tungstenite::handshake::client: Client handshake done.\r\nMar 16 07:10:37.519 INFO run: serenity::client::bridge::gateway::shard_runner: [ShardRunner [0, 1]] Running\r\n```\r\n\r\nThis PR doesn't deal with the transfer of any unhandled `Intermessage`s between `ShardRunner`s after a full restart, which affects songbird somewhat. I think the best method to handle this is to put a (configurable) timeout on those connection attempts for now, as that requires less engineering work.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "BRAVO68WEB", "comment_id": null, "datetime": 1602307650000, "masked_author": "username_0", "text": "**What can be done?**\r\nAdding Hexo Framework as a skill under \"Static Site Generators\"\r\n\r\n**Hexo**\r\n\r\n\r\n**Solution**\r\nI can add it, can you assign me!", "title": "Adding HEXO framework as a skill", "type": "issue" }, { "action": "created", "author": "BRAVO68WEB", "comment_id": 706491213, "datetime": 1602307682000, "masked_author": "username_0", "text": "@rahuldkjain Can you assign me?", "title": null, "type": "comment" }, { "action": "created", "author": "BRAVO68WEB", "comment_id": 706493494, "datetime": 1602309221000, "masked_author": "username_0", "text": "Thx", "title": null, "type": "comment" }, { "action": "created", "author": "BRAVO68WEB", "comment_id": 706705689, "datetime": 1602423249000, "masked_author": "username_0", "text": "Done", "title": null, "type": "comment" }, { "action": "closed", "author": "BRAVO68WEB", "comment_id": null, "datetime": 1602423251000, "masked_author": "username_0", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "WelisonR", "comment_id": null, "datetime": 1620055854000, "masked_author": "username_0", "text": "## Descrição\r\n\r\nA presente issue busca automatizar a recuperação das releases dos repositórios do projeto a fim de disponibilizá-las em um local único.\r\n\r\n## Tarefas\r\n\r\n- [ ] Criar script para automatizar o processo de recuperação dos arquivos do sonarcloud dos outros repositórios;\r\n- [ ] Criar rotina (job) com GitHub Actions que execute semanalmente o script que recupera os arquivos do sonarcloud;\r\n- [ ] Disponibilizar, através da rotina, arquivos de métricas em uma branch específica no github (_metrics_).\r\n\r\n## Critérios de Aceitação\r\n\r\n- Últimos arquivos de métricas disponibilizados na branch _metrics_, separados por pastas de acordo com os microsserviços.\r\n\r\n## Observação\r\n\r\n- Usar a biblioteca `act` para testar as github actions localmente.", "title": "Automatizar recuperação de arquivos sonarcloud com Github Actions", "type": "issue" }, { "action": "created", "author": "WelisonR", "comment_id": 841701238, "datetime": 1621101432000, "masked_author": "username_0", "text": "Decidido pela equipe que não será necessário desenvolver essa atividade, pois o custo seria maior que o benefício. Portanto, a extração das releases será feita de forma manual.", "title": null, "type": "comment" }, { "action": "closed", "author": "WelisonR", "comment_id": null, "datetime": 1621101432000, "masked_author": "username_0", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "shifenis", "comment_id": null, "datetime": 1618080844000, "masked_author": "username_0", "text": "Like the title, it would be awesome if `TextStyle`, allows handling Inner Shadow and not just for the background.", "title": "Inner shadow on Text", "type": "issue" }, { "action": "created", "author": "pedromassangocode", "comment_id": 817563811, "datetime": 1618212816000, "masked_author": "username_1", "text": "Hi @username_0 \r\nCan you please elaborate more?\r\nDoes the code bellow works for you?\r\n\r\n\r\n\r\n\r\n\r\n<details>\r\n<summary>code sample</summary>\r\n\r\n```dart\r\nimport 'package:flutter/cupertino.dart';\r\nimport 'package:flutter/material.dart';\r\n\r\nvoid main() => runApp(MyApp());\r\n\r\nclass MyApp extends StatelessWidget {\r\n @override\r\n Widget build(BuildContext context) {\r\n return MaterialApp(\r\n title: 'Flutter Demo',\r\n home: Scaffold(\r\n body: Center(\r\n child: Text(\r\n \"Forgot Password?\",\r\n style: TextStyle(\r\n shadows: [\r\n Shadow(\r\n color: Colors.green,\r\n offset: Offset(0, -2))\r\n ],\r\n ),\r\n ),\r\n ),\r\n ),\r\n );\r\n }\r\n}\r\n\r\n```\r\n\r\n</details>", "title": null, "type": "comment" }, { "action": "created", "author": "shifenis", "comment_id": 817596473, "datetime": 1618215519000, "masked_author": "username_0", "text": "Hi @username_1, the code you provide is not really an inner shadow, indeed, it's a background shadow.\r\n\r\n\r\n\r\nThis is the result I would like to achieve.\r\nAt the moment I don't think Flutter can allow this, at least for the `Text` widget.", "title": null, "type": "comment" }, { "action": "created", "author": "zanderso", "comment_id": 915615993, "datetime": 1631140073000, "masked_author": "username_2", "text": "I think we should probably put a little more effort in to determining whether an effect like this is already possible given the primitives that exist today.", "title": null, "type": "comment" } ]

{ "number": 6418, "repo": "NeoAlgo", "user_login": "TesseractCoding" }

[ { "action": "opened", "author": "Nidhideveloper", "comment_id": null, "datetime": 1619096777000, "masked_author": "username_0", "text": "<!--\r\nThank you for sending the PR! We appreciate you spending the time to work on these changes.\r\n\r\nHelp us understand your motivation by explaining why you decided to make this change.\r\nYou can learn more about contributing to NeoAlgo here: https://github.com/TesseractCoding/NeoAlgo/blob/master/CONTRIBUTING.md\r\n\r\nHappy Contributing!\r\n\r\n-->\r\n\r\n### Have you read the [Contributing Guidelines on Pull Requests](https://github.com/TesseractCoding/NeoAlgo/blob/master/CONTRIBUTING.md#pull-requests)?\r\n\r\nYes\r\n\r\n### Description\r\n\r\nAdded Total Ones\r\n\r\n### Checklist\r\n\r\n- [x] I've read the contribution guidelines.\r\n- [x] I've checked the issue list before deciding what to submit.\r\n- [x] I've edited the `README.md` and link to my code.\r\n\r\n## Related Issues or Pull Requests\r\n\r\n#6414", "title": "Added Total Ones", "type": "issue" }, { "action": "created", "author": "Nidhideveloper", "comment_id": 824826193, "datetime": 1619096895000, "masked_author": "username_0", "text": "@HarshCasper Sir Please review this pr and plz let me know if further changes are required.", "title": null, "type": "comment" } ]

{ "number": 50, "repo": "ros2_java", "user_login": "osrf" }

[ { "action": "opened", "author": "jacobperron", "comment_id": null, "datetime": 1604976765000, "masked_author": "username_0", "text": "This fixes two issues:\r\n\r\n1. The default constructor for ParameterAndDescriptor initializes it's members to null.\r\n This can cause a segfault when trying to access a parameters descriptor if undeclared\r\n parameters are allowed and it has been set without a descriptor\r\n (e.g. using setParameters()).\r\n\r\n This change defines the constructor for ParameterAndDescriptor so that we don't hit\r\n any null values.\r\n\r\n2. Parameters that are not declared and set with setParameters() do not have their\r\n descriptors set to the correct value.\r\n This change makes sure that the descriptor is initialized with the values of the\r\n parameter being set.", "title": "Fix issues with parameters descriptors", "type": "issue" }, { "action": "created", "author": "jacobperron", "comment_id": 724843425, "datetime": 1605028549000, "masked_author": "username_0", "text": "Though there are no explicit tests covering these cases, the tests introduced in https://github.com/osrf/ros2_java/pull/48 caused both of these issues to surface, so at least it's covered.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "yunxag", "comment_id": null, "datetime": 1615197059000, "masked_author": "username_0", "text": "这个培训机构换到隔壁继续行骗，5楼全是培训机构\r\n公司:深圳有数科技有限公司\r\n地址:深圳市宝安区新安街道群辉路5号优创空间3栋503室", "title": "培训机构", "type": "issue" }, { "action": "created", "author": "ZGWS88", "comment_id": 797865625, "datetime": 1615610389000, "masked_author": "username_1", "text": "这家公司名找不到。不过同地址的更新了几家。感谢提供", "title": null, "type": "comment" }, { "action": "closed", "author": "npcola", "comment_id": null, "datetime": 1639469938000, "masked_author": "username_2", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "applePrincess", "comment_id": null, "datetime": 1623988597000, "masked_author": "username_0", "text": "```\r\nfull log (produced by nix log /nix/store/smrzwazd7hxy58rbmkrmlb4ml0bb4kiy-python3.8-pecan-1.4.0.drv) is available at: https://gist.github.com/username_0/3164282320c2067d86438c07e77564a8\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\n1. nix build nixpkgs#python3Packages.pecan\r\n\r\n**Expected behavior**\r\nA successful build\r\n\r\n**Screenshots**\r\nIf applicable, add screenshots to help explain your problem.\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n\r\n**Notify maintainers**\r\nNo maintainers set so CC to list of contributers instead.\r\n@FRidh @prusnak @username_2 @ryantm @username_1 @Profpatsch @Mic92 @drewrisinger @adisbladis \r\n\r\n**Metadata**\r\n\r\n```\r\n - system: `\"x86_64-linux\"`\r\n - host os: `Linux 5.12.10, NixOS, 21.11.20210612.d51b663 (Porcupine)`\r\n - multi-user?: `yes`\r\n - sandbox: `yes`\r\n - version: `nix-env (Nix) 2.4pre20210601_5985b8b`\r\n - channels(root): `\"nixos-20.09.4242.cee3ca37c68, nixos-unstable-21.11pre293089.1c2986bbb80\"`\r\n - channels(username_0): `\"\"`\r\n - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`\r\n\r\n```\r\nnixpkgs git commit: `ea12a8ea1742389348950c77e75097320bd9d2dd`\r\nMaintainer information:\r\n```yaml\r\n# a list of nixpkgs attributes affected by the problem\r\nattribute:\r\n# a list of nixos modules affected by the problem\r\nmodule:\r\n```", "title": "Cannot build python3Packages.pecan", "type": "issue" }, { "action": "created", "author": "dotlambda", "comment_id": 863978376, "datetime": 1624016696000, "masked_author": "username_1", "text": "You should make a PR applying https://github.com/pecan/pecan/commit/a520bd544c0b02a02dbf692b8d6e2f7a503ee6d4 using `fetchpatch` and consider making yourself a maintainer.", "title": null, "type": "comment" }, { "action": "closed", "author": "SuperSandro2000", "comment_id": null, "datetime": 1624047487000, "masked_author": "username_2", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "charlie1404", "comment_id": null, "datetime": 1613590954000, "masked_author": "username_0", "text": "React version: latest (tested with 16 and 17 both)\r\n\r\n## Steps To Reproduce\r\n\r\nPlease see attached videos for reference and code sandbox for live experiment\r\n\r\n1. Set component in StrictMode but wrapping it in `<React.StrictMode>`\r\n2. Have a useRef in that component which takes empty array as input.\r\n3. Try mutating it on every render, maybe something like `refVar.current.push(\"doesn't really matter what goes in here\")`\r\n4. use that array (have made simple list from that, but should apply to all cases)\r\n5. array is being mutated from different universe.\r\n\r\nLink to code example:\r\nhttps://codesandbox.io/s/strict-bug-mrv-w7r11\r\n\r\n## The current behavior\r\nThere are console to show the value of array before and after to array mutation.\r\nIn strict mode which clicked button array adds extra element (Please see attachment one)\r\n\r\n## The expected behavior\r\nI believe this should be same as when not in not strict mode.\r\n\r\n\r\nApart from this I also have tried using debugger to see what actually is happening. When added breakpoint to `list.current.push()` it seems devtools is stopping on that line twice. What even more confusing to me is, if in case function ran(rendered) twice, how come there is console only once, please attached video for the same.\r\n\r\nAttachments:\r\n 1. https://user-images.githubusercontent.com/20264337/108258484-12ce5300-7186-11eb-8bb2-6e82a14ac856.mov\r\n 2. https://user-images.githubusercontent.com/20264337/108256943-1fea4280-7184-11eb-9840-2dfc243eb6ae.mov", "title": "Bug: useRef acting weird in Strict mode.", "type": "issue" }, { "action": "created", "author": "eps1lon", "comment_id": 780853277, "datetime": 1613595996000, "masked_author": "username_1", "text": "Thanks for the report. \r\n\r\nThat is definitely a common confusion. In case you're not aware of what StrictMode does and why it is used: StrictMode warns about various problematic patterns. \r\n\r\nOne of which is having [methods with side-effects that shouldn't have side-effects in React](https://reactjs.org/docs/strict-mode.html#detecting-unexpected-side-effects). Mutating a ref is such a side-effect and doing it when rendering a component is problematic. StrictMode calls the render method twice to help detect these problems.\r\n\r\nThe unfortunate part is that you've also hit another \"quirk\" of StrictMode (which only applies to React 17): [Calls to console methods during the second render call (by StrictMode) are ignored](https://github.com/facebook/react/pull/18547). There are [plans to enable double-logging in StrictMode](https://github.com/facebook/react/pull/19710). If you're interested in these, please upvote https://github.com/facebook/react/pull/19710.\r\n\r\nI hope this clears up any confusion about the observed behavior. Feel free to ask further questions if some explanations are unclear.", "title": null, "type": "comment" }, { "action": "closed", "author": "bvaughn", "comment_id": null, "datetime": 1613597867000, "masked_author": "username_2", "text": "", "title": null, "type": "issue" }, { "action": "created", "author": "bvaughn", "comment_id": 780871086, "datetime": 1613597867000, "masked_author": "username_2", "text": "As @username_1 mentioned, mutation during render is specifically something React does not support and `StrictMode` exists to help flush out cases of this. 😄 \r\n\r\nI'm going to go ahead and close this issue since everything seems to be working as designed. We can talk more if you still have questions or concerns though! 👍", "title": null, "type": "comment" }, { "action": "created", "author": "charlie1404", "comment_id": 781077086, "datetime": 1613627785000, "masked_author": "username_0", "text": "@username_1 @username_2 Thanks for the explanation, I think I got it.\r\nYes I was aware that we should not do mutations in render but was not aware of render being called twice in strict mode 😅 \r\n\r\nThe bigger source of confusion was that console's are being silent. Not sure but to me this behavior by default seems not beginner-friendly.\r\n\r\nmy use case was to count the number of renders and show them on UI (nothing real but an experiment), which I ended up doing using `useEffect` without dependency array.", "title": null, "type": "comment" }, { "action": "created", "author": "bvaughn", "comment_id": 781393974, "datetime": 1613659621000, "masked_author": "username_2", "text": "Yeah, this is a feature that has pros and cons that have been debated at length (on other issues and within the React team) without a clear solution. We chose the default we thought was best but it's not perfect. In the future we plan to add some extra tools to DevTools to help with discoverability (and maybe to allow you to override the default) FWIW.", "title": null, "type": "comment" }, { "action": "created", "author": "gaearon", "comment_id": 1083431464, "datetime": 1648662101000, "masked_author": "username_3", "text": "To follow up on this, we've changed the logging behavior in 18 to be more intuitive.\r\nhttps://github.com/facebook/react/issues/21783#issuecomment-1083412766", "title": null, "type": "comment" } ]

{ "number": 205, "repo": "fs2-google-pubsub", "user_login": "permutive" }

[ { "action": "opened", "author": "scala-steward", "comment_id": null, "datetime": 1614700976000, "masked_author": "username_0", "text": "Updates \n* [org.http4s:http4s-client](https://github.com/http4s/http4s)\n* [org.http4s:http4s-dsl](https://github.com/http4s/http4s)\n* [org.http4s:http4s-okhttp-client](https://github.com/http4s/http4s)\n\n from 0.21.19 to 0.21.20.\n[GitHub Release Notes](https://github.com/http4s/http4s/releases/tag/v0.21.20) - [Version Diff](https://github.com/http4s/http4s/compare/v0.21.19...v0.21.20)\n\nI'll automatically update this PR to resolve conflicts as long as you don't change it yourself.\n\nIf you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.\n\nConfigure Scala Steward for your repository with a [`.username_0.conf`](https://github.com/username_0-org/username_0/blob/b60b38e518586b7bd87619b7b6c48cda51ab8dd3/docs/repo-specific-configuration.md) file.\n\nHave a fantastic day writing Scala!\n\n<details>\n<summary>Ignore future updates</summary>\n\nAdd this to your `.username_0.conf` file to ignore future updates of this dependency:\n```\nupdates.ignore = [ { groupId = \"org.http4s\" } ]\n```\n</details>\n\nlabels: library-update, semver-patch", "title": "Update http4s-client, http4s-dsl, ... to 0.21.20", "type": "issue" }, { "action": "created", "author": "scala-steward", "comment_id": 809321964, "datetime": 1617019346000, "masked_author": "username_0", "text": "Superseded by #212.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "mdb", "comment_id": null, "datetime": 1591457528000, "masked_author": "username_0", "text": "**Is your feature request related to a problem?**\r\nAs a user, it would be helpful to be able to enable the logging of HTTP response data.\r\n\r\n**Describe the solution you'd like**\r\nCurrently, establishing a `GF_LOG=true` environment variable results in the logging of request data like so, for example:\r\n\r\n```\r\n2020/06/06 11:29:31 request (GET) to http://my-grafana.com/api/users with no body data\r\n```\r\nAdditionally, it would be helpful of response data were also logged:\r\n\r\n```\r\n2020/06/06 11:29:31 response status 200 with body {\"id\":1,\"email\":\"admin@localhost\",\"name\":\"\",\"login\":\"admin\",\"theme\":\"\",\"orgId\":1,\"isGrafanaAdmin\":true}\r\n```", "title": "Log HTTP response status and body", "type": "issue" }, { "action": "closed", "author": "tonglil", "comment_id": null, "datetime": 1591780850000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

{ "number": 966, "repo": "gpuweb", "user_login": "gpuweb" }

[ { "action": "opened", "author": "toji", "comment_id": null, "datetime": 1596228018000, "masked_author": "username_0", "text": "Working my way through all the existing method definitions and trying to normalize them as much as possible. Not examining the existing steps too critically outside of style, but happy to make any fixes to existing algorithms you may notice while reviewing.\n\n\n<!--\n This comment and the below content is programatically generated.\n You may add a comma-separated list of anchors you'd like a\n direct link to below (e.g. #idl-serializers, #idl-sequence):\n\n Don't remove this comment or modify anything below this line.\n If you don't want a preview generated for this pull request,\n just replace the whole of this comment's content by \"no preview\"\n and remove what's below.\n-->\n***\n<a href=\"https://pr-preview.s3.amazonaws.com/username_0/gpuweb/pull/966.html\" title=\"Last updated on Aug 4, 2020, 7:54 PM UTC (0bc526f)\">Preview</a> | <a href=\"https://pr-preview.s3.amazonaws.com/gpuweb/gpuweb/966/616efb5...username_0:0bc526f.html\" title=\"Last updated on Aug 4, 2020, 7:54 PM UTC (0bc526f)\">Diff</a>", "title": "Updating multiple methods to the new style (Pt. 3)", "type": "issue" }, { "action": "created", "author": "toji", "comment_id": 668793883, "datetime": 1596570865000, "masked_author": "username_0", "text": "Thanks @kvark and @username_1! Remaining feedback has been addressed.", "title": null, "type": "comment" }, { "action": "created", "author": "kainino0x", "comment_id": 668844237, "datetime": 1596578145000, "masked_author": "username_1", "text": "Thanks!", "title": null, "type": "comment" } ]

{ "number": 1141, "repo": "kaspad", "user_login": "kaspanet" }

[ { "action": "opened", "author": "someone235", "comment_id": null, "datetime": 1606142459000, "masked_author": "username_0", "text": "Based on https://sourcegraph.com/github.com/kaspanet/kaspad@v0.7.3-dev/-/blob/domain/blockdag/validate_test.go#L465:6", "title": "[NOD-1561] Add TestValidateMedianTime", "type": "issue" }, { "action": "created", "author": "ci-dag", "comment_id": 732207337, "datetime": 1606142769000, "masked_author": "username_1", "text": "Rebuild after update in master", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "NJaku01", "comment_id": null, "datetime": 1605690420000, "masked_author": "username_0", "text": "After shipping the ERC to, for example, Zenodo, all important files (e.g. display.html) are moved by the shipper. The files are then stored under id/data/data/display.html instead of id/data/display.html.", "title": "data file path changing by shipment", "type": "issue" }, { "action": "created", "author": "nuest", "comment_id": 730345677, "datetime": 1605789287000, "masked_author": "username_1", "text": "@username_0 Note that a path `id/data/data` is not what we want.\r\n\r\nIf the ERC is already a bag (which by definition it is, otherwise it is a workspace), then we need to make sure that the shipper updates but not recreates the bag.\r\n\r\nIf there is a `data` directory, but there is no `bagit.txt`, then the path `id/data/data/display.html` _could_ be correct. Please be sure to keep the paths in the `erc.yml` in sync with the values in the database.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "suprafun", "comment_id": null, "datetime": 1619389493000, "masked_author": "username_0", "text": "Hello, under what license is this project released under ? I would like to study it to learn from it. Thank you.", "title": "License ?", "type": "issue" }, { "action": "created", "author": "Jordan-Cottle", "comment_id": 827782211, "datetime": 1619544582000, "masked_author": "username_1", "text": "I hadn't applied a license to the code here, but since you mentioned it I just added a `LICENSE.txt` using the MIT template github provides. \r\n\r\nI hope that is satisfactory for what you plan to use this project for.", "title": null, "type": "comment" } ]

[ { "action": "closed", "author": "124857045", "comment_id": null, "datetime": 1605493075000, "masked_author": "username_0", "text": "", "title": null, "type": "issue" }, { "action": "reopened", "author": "124857045", "comment_id": null, "datetime": 1605493097000, "masked_author": "username_0", "text": "# :wave: Welcome to GitHub Learning Lab's \"Introduction to GitHub\"\n\nTo get started, I’ll guide you through some important first steps in coding and collaborating on GitHub.\n\n:point_down: _This arrow means you can expand the window! Click on them throughout the course to find more information._\n<details><summary>What is GitHub?</summary>\n<hr>\n\n## What is GitHub?\n\nI'm glad you asked! Many people come to GitHub because they want to contribute to open source ^{[:book:](https://help.github.com/articles/github-glossary/#open-source)} projects, or they're invited by teammates or classmates who use it for their projects. Why do people use GitHub for these projects?\n\n**At its heart, GitHub is a collaboration platform.**\n\nFrom software to legal documents, you can count on GitHub to help you do your best work with the collaboration and security tools your team needs. With GitHub, you can keep projects completely private, invite the world to collaborate, and streamline every step of your project.\n\n**GitHub is also a powerful version control tool.**\n\nGitHub uses Git ^{[:book:](https://help.github.com/articles/github-glossary/#git)}, the most popular open source version control software, to track every contribution and contributor ^{[:book:](https://help.github.com/articles/github-glossary/#contributor)} to your project--so you know exactly where every line of code came from.\n\n**GitHub helps people do much more.**\n\nGitHub is used to build some of the most advanced technologies in the world. Whether you're visualizing data or building a new game, there's a whole community and set of tools on GitHub that can get you to the next step. This course starts with the basics, but we'll dig into the rest later!\n\n:tv: [Video: What is GitHub?](https://www.youtube.com/watch?v=w3jLJU7DT5E)\n<hr>\n</details><br>\n\n<details><summary>Exploring a GitHub repository</summary>\n<hr>\n\n## Exploring a GitHub repository\n\n:tv: [Video: Exploring a repository](https://www.youtube.com/watch?v=R8OAwrcMlRw)\n\n### More features\n\nThe video covered some of the most commonly-used features. Here are a few other items you can find in GitHub repositories:\n\n- Project boards: Create Kanban-style task tracking board within GitHub\n- Wiki: Create and store relevant project documentation\n- Insights: View a drop-down menu that contains links to analytics tools for your repository including:\n - Pulse: Find information about the work that has been completed and the work that’s in-progress in this project dashboard\n - Graphs: Graphs provide a more granular view of the repository activity including who contributed to the repository, who forked it, and when they completed the work\n\n### Special Files\n\nIn the video you learned about a special file called the README.md. Here are a few other special files you can add to your repositories:\n\n- CONTRIBUTING.md: The `CONTRIBUTING.md` is used to describe the process for contributing to the repository. A link to the `CONTRIBUTING.md` file is shown anytime someone creates a new issue or pull request.\n- ISSUE_TEMPLATE.md: The `ISSUE_TEMPLATE.md` is another file you can use to pre-populate the body of an issue. For example, if you always need the same types of information for bug reports, include it in the issue template, and every new issue will be opened with your recommended starter text.\n\n<hr>\n</details>\n\n### Using issues\n\nThis is an issue ^{[:book:](https://help.github.com/articles/github-glossary/#issue)}: a place where you can have conversations about bugs in your code, code review, and just about anything else.\n\nIssue titles are like email subject lines. They tell your collaborators what the issue is about at a glance. For example, the title of this issue is Getting Started with GitHub.\n\n\n<details><summary>Using GitHub Issues</summary>\n\n## Using GitHub issues\n\nIssues are used to discuss ideas, enhancements, tasks, and bugs. They make collaboration easier by:\n\n- Providing everyone (even future team members) with the complete story in one place\n- Allowing you to cross-link to other issues and pull requests ^{[:book:](https://help.github.com/articles/github-glossary/#pull-request)}\n- Creating a single, comprehensive record of how and why you made certain decisions\n- Allowing you to easily pull the right people and teams into a conversation with @-mentions\n\n:tv: [Video: Using issues](https://www.youtube.com/watch?v=Zhj46r5D0nQ)\n\n<hr>\n</details>\n\n<details><summary>Managing notifications</summary>\n<hr>\n\n## Managing notifications\n\n:tv: [Video: Watching, notifications, stars, and explore](https://www.youtube.com/watch?v=ocQldxF7fMY)\n\nOnce you've commented on an issue or pull request, you'll start receiving email notifications when there's activity in the thread. \n\n### How to silence or unmute specific conversations\n\n1. Go to the issue or pull request\n2. Under _\"Notifications\"_, click the **Unsubscribe** button on the right to silence notifications or **Subscribe** to unmute them\n\nYou'll see a short description that explains your current notification status.\n\n### How to customize notifications in Settings\n\n1. Click your profile icon\n2. Click **Settings**\n3. Click **Notifications** from the menu on the left and [adjust your notification preferences](https://help.github.com/articles/managing-notification-delivery-methods/)\n\n### Repository notification options\n\n* **Watch**: You'll receive a notification when a new issue, pull request or comment is posted, and when an issue is closed or a pull request is merged \n* **Not watching**: You'll no longer receive notifications unless you're @-mentioned\n* **Ignore**: You'll no longer receive any notifications from the repository\n\n### How to review notifications for the repositories you're watching\n\n1. Click your profile icon\n2. Click **Settings**\n3. Click **Notification** from the menu on the left\n4. Click on the [things you’re watching](https://github.com/watching) link\n5. Select the **Watching** tab\n6. Click the **Unwatch** button to disable notifications, or **Watch** to enable them\n\n<hr>\n</details>\n\n<hr>\n<h3 align=\"center\">Keep reading below to find your first task</h3>", "title": "Getting Started with GitHub", "type": "issue" }, { "action": "closed", "author": "124857045", "comment_id": null, "datetime": 1605493216000, "masked_author": "username_0", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "evelynpestevao", "comment_id": null, "datetime": 1614188577000, "masked_author": "username_0", "text": "<!-- IMPORTANTE:\r\n1. Só poste vaga de QA.\r\n2. Utilize o template abaixo como guia, sem apagar as seções e apenas alterando as informações de dentro delas.\r\n3. Não faça distinção de gênero.\r\n4. Respeite o código de conduta -->\r\n\r\n## Sobre a empresa\r\n\r\nA Iterative é uma Fábrica de Software inovadora, dinâmica e moderna, em plena ascensão e expansão com serviços diversificados e produtos, localizada em São Paulo.\r\n\r\nSão quase 9 anos de mercado, proporcionando um ambiente acolhedor e disruptivo, que favorece o mindset ágil, permitindo que as pessoas mantenham sua subjetividade e ao mesmo tempo, fomentando a colaboração, o encorajamento, a liberdade de ação e a inovação entre os times.\r\n\r\nTemos 3 principais frentes de negócios: Fábrica de Software, alocações de profissionais e incubadora de startups.\r\n\r\n\r\n## Descrição da vaga\r\n\r\nNossa área de quality assurance é a responsável por garantir que os nossos produtos sejam entregues dentro dos padrões de qualidade. Trabalhamos em conjunto com outras áreas da engenharia e somos indispensáveis para as entregas finais. \r\nSe você é uma pessoa desenrolada, saiba que você é quem vai garantir que nenhuma entrega seja feita abaixo da régua (que é alta!).\r\nOportunidade para atuação em Startup super inovadora consolidada no mercado de marketplace e e-commerce.\r\n\r\nSuas principais responsabilidades serão:\r\n\r\nComo QA, você irá desenvolver planos de testes e casos de testes funcionais e não funcionais;\r\nSerá responsável pela criação de scripts de automação de teste; \r\nAtuará na criação e modelagem dos casos de testes focados em testes automatizados; Realizará a execução dos testes automatizados; \r\nRealizará a construção de massa de dados; \r\nFará o reporte do andamento das atividades; \r\nRealizará o levantamento dos cenários de teste;\r\nAtuará com automação de testes Mobile.\r\n\r\n\r\n## Local de trabalho\r\n<!-- escolha apenas 1 das linhas abaixo, ajuste para o seu contexto e exclua as outras -->\r\n- 100% Remoto, de qualquer lugar do Brasil!\r\n\r\n\r\n## Requisitos da vaga\r\n\r\nO que esperamos de você:\r\n\r\nExperiência prévia com metodologia ágil (Scrum);\r\nExecução de testes manuais e automatizados;\r\nExperiência com as ferramentas: Selenium Webdriver, APIs, Cucumber, Xcuitest, Js e Json. Appium seria um diferencial;\r\nElaborar casos de testes com técnica BDD;\r\nExecução de testes progressivos e regressivos; \r\nGraduação em Ciências da Computação, Análise de Sistemas, Sistemas da informação e outras áreas correlatas;\r\nColaborar com times de desenvolvimento e de testes;\r\nAtenção aos pequenos detalhes.\r\n\r\n\r\n## Forma de contratação\r\n\r\nRemuneração PJ a combinar;\r\n\r\n\r\n## Como se candidatar\r\n\r\nSe identificou com a oportunidade? Então venha ser um(a) Iterativo(a)!\r\nPor favor, envie seu currículo para o e-mail evelyn.estevao@iterative.com.br e vamos conversar!\r\n\r\n## Tempo médio de feedbacks\r\n\r\nCostumamos enviar feedbacks em até 10 dias após cada processo.\r\n\r\nE-mail para contato em caso de não haver resposta: evelyn.estevao@iterative.com.br\r\n\r\n## Labels\r\n<!-- Label é uma forma dos QAs conseguirem pesquisar as vagas. Após cadastrar a vaga, ela receberá label automaticamente em até 2 minutos.\r\nApague os itens abaixo que não corresponderem à vaga. -->\r\n- PJ\r\n- Sênior\r\n- Especialista\r\n<!-- Se a vaga for mista (X dias presencial e Y dias remoto) deixe as 2 linhas abaixo -->\r\n\r\n- Remoto\r\n<!--- Informar abaixo o nome do estado por extenso se for do Brasil. --->\r\n\r\n<!--- Se sua vaga não for do Brasil, apague a linha de estado acima e deixe a de baixo --->", "title": "[Remoto] Analista QA Sênior na Iterative;", "type": "issue" } ]

{ "number": 797, "repo": "OpenLoco", "user_login": "OpenLoco" }

[ { "action": "opened", "author": "duncanspumpkin", "comment_id": null, "datetime": 1614369247000, "masked_author": "username_0", "text": "Calculation was incorrectly adding the offset to the first tile instead of removeing the offset from the current tile. This meant that it would set the waypoint at the wrong location", "title": "Fix waypoint setting function", "type": "issue" }, { "action": "created", "author": "AaronVanGeffen", "comment_id": 786866942, "datetime": 1614369995000, "masked_author": "username_1", "text": "How would we best go about testing this?\n\nPerhaps we can share a CI build for testing with the users who reported the issue?", "title": null, "type": "comment" }, { "action": "created", "author": "duncanspumpkin", "comment_id": 786872794, "datetime": 1614370743000, "masked_author": "username_0", "text": "its immediately obvious when you try set a waypoint on curved track the waypoint changes position depending on where you clicked on the track. What is meant to happen is the waypoint is always at the first tile of the curve.", "title": null, "type": "comment" }, { "action": "created", "author": "senner007", "comment_id": 787031242, "datetime": 1614411975000, "masked_author": "username_2", "text": "@username_1 \r\nCan it not be set to automatically create a windows executable for each pr?", "title": null, "type": "comment" }, { "action": "created", "author": "AaronVanGeffen", "comment_id": 787031709, "datetime": 1614412260000, "masked_author": "username_1", "text": "@username_2 It already does. You can find the CI artefacts in the Checks tab for this PR, for example. Unfortunately, this isn't very discoverable for most users.", "title": null, "type": "comment" }, { "action": "created", "author": "senner007", "comment_id": 787032012, "datetime": 1614412466000, "masked_author": "username_2", "text": "@username_1 \r\nYes I see", "title": null, "type": "comment" }, { "action": "created", "author": "senner007", "comment_id": 787040546, "datetime": 1614416647000, "masked_author": "username_2", "text": "This does not fix #798", "title": null, "type": "comment" }, { "action": "created", "author": "AaronVanGeffen", "comment_id": 787042961, "datetime": 1614417914000, "masked_author": "username_1", "text": "@username_2 The bug is in setting the waypoints. Did you remove and set the waypoints again? Otherwise, the bad waypoint will persist.", "title": null, "type": "comment" }, { "action": "created", "author": "senner007", "comment_id": 787043709, "datetime": 1614418335000, "masked_author": "username_2", "text": "Yes I did that. Could this be an original bug?", "title": null, "type": "comment" }, { "action": "created", "author": "duncanspumpkin", "comment_id": 787057913, "datetime": 1614424980000, "masked_author": "username_0", "text": "There's two issues with waypoints one is that people feel they are ignored the other was that setting them on multi tile tracks wasn't working. This corrects the second issue", "title": null, "type": "comment" } ]

{ "number": 30184, "repo": "void-packages", "user_login": "void-linux" }

[ { "action": "opened", "author": "Chocimier", "comment_id": null, "datetime": 1618241925000, "masked_author": "username_0", "text": "", "title": "shiboken2: add transitional packages back", "type": "issue" }, { "action": "created", "author": "Duncaen", "comment_id": 817920603, "datetime": 1618242428000, "masked_author": "username_1", "text": "I don't think because one user messed up their installation and is unable to cleanly remove those packages with `xbps-remove --remove-orphans` it is necessary to add back transitional packages that have been there since 2019 and were removed in January 2021.", "title": null, "type": "comment" } ]

{ "number": 523, "repo": "procosys-preservation-api", "user_login": "equinor" }

[ { "action": "opened", "author": "janid1967", "comment_id": null, "datetime": 1618407712000, "masked_author": "username_0", "text": "See commit comments\r\n\r\n[AB#82143](https://statoildeveloper.visualstudio.com/b6d97460-2e53-47ae-aad4-b41396d90828/_workitems/edit/82143)", "title": "82143 - TECH Rename Procosys to ProCoSys", "type": "issue" }, { "action": "created", "author": "hbjorgo", "comment_id": 820133918, "datetime": 1618465823000, "masked_author": "username_1", "text": "The folder Equinor.Procosys.Preservation.WebApi does not have the correct casing.\r\nUpdate path in Docker-compose.yml", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "runxel", "comment_id": null, "datetime": 1622926746000, "masked_author": "username_0", "text": "Sometimes people write `x**2` instead of `x^2`.\r\nMathJS seemingly doesn't support this right now.\r\nThis should be added.", "title": "Exponentiation notation", "type": "issue" }, { "action": "created", "author": "josdejong", "comment_id": 855296602, "datetime": 1622927583000, "masked_author": "username_1", "text": "Whilst it could be convenient for some people, it would also cause confusion: why are there two operators for exponentiation? Which one should I use? Do they differ or not? \r\n\r\nI think it's best in this case to keep just a single operator. What would be nice is to give a clear hint \"did you mean the exponentiation operator ^ ?\" when someone uses **.", "title": null, "type": "comment" }, { "action": "created", "author": "runxel", "comment_id": 856067216, "datetime": 1623081900000, "masked_author": "username_0", "text": "Thanks for your input, @username_1.\r\nI am not really sure if this is the right approach, tho.\r\nLet me explain:\r\nI'm always a bit mad, if I as a user get those kind of hints. Because this tells me: \"Well, I certainly know _exactly_ what you want to do, but I won't let you do it. You have to do it my way\".\r\nThat is the opposite of being user-centric.\r\nWhy not just add it, and being silent about it? ;)", "title": null, "type": "comment" }, { "action": "created", "author": "m93a", "comment_id": 856141075, "datetime": 1623088293000, "masked_author": "username_2", "text": "I agree with @username_1 on this. Introducing multiple different syntaxes to achieve the exact same result sounds like a way to having a messy and overly complicated expression parser soon. I like to introduce new features not merely because “it would be nice” to have them, but because they solve an actual problem. Sorry to disappoint you, but here the problem sounds like a minor inconvenience that takes ~1 second to fix ;)\r\n\r\nTo demonstrate that there *is* a real difference between how one would implement a hint vs proper syntax:\r\n\r\n**Proper `**` operator**:\r\n * Implementation:\r\n * When the lexer sees `*`, make it look ahead if theres another `*`. Produce either a `*` or a `**` token accordingly.\r\n * In the parser, add grammar for `a ** b` that is the same as for `a ^ b`\r\n * Make sure that `a ^ b` and `a ** b` emit exactly the same code\r\n * When any change is done to one, it has to be perfectly replicated in the other\r\n * All the tests have to check for both `a ^ b` and `a ** b` to ensure this is the case\r\n * Pros:\r\n * Users can type whichever operator they want\r\n * Cons:\r\n * More complicated lexer and parser\r\n * A lot of code duplication that has to be kept in sync\r\n * Possible confusion of users, as Jos noted\r\n\r\n**Hint:**\r\n * Implementation\r\n * When the parser throws an error throws 'Value expected', check if the string contains '**'\r\n * If so, show the hint\r\n * Pros:\r\n * No code duplication, no complication in parser\r\n * Very simple to maintain\r\n * Users are told exactly what operator to use ⇒ no confusion\r\n * Cons:\r\n * User has to follow the hint and change '**' to '^'", "title": null, "type": "comment" }, { "action": "created", "author": "josdejong", "comment_id": 856191448, "datetime": 1623093336000, "masked_author": "username_1", "text": "@username_2 I think the most important is what we want to achieve functionally - how complex it is to implement is secondary :) \r\n\r\n@username_0 I understand it is very convenient, and it will work just fine if you're working on your own. But if you develop a script or application together with some colleagues, and you do it _your_ way using `**` and a second colleague starts using `^` because that is _his_ way, and a third colleague is simply confused to find these two mixed together in a single file and starts wondering if those two operators work the same or whether there is a difference and which one to use. I think in general a good approach is to try to keep an API minimal, have a single way to do something, and where relevant give a user hints to help him figure out how something like exponentiation works in _this_ environment (\"did you mean...?\"). \r\n\r\nJust to think in solutions: if you do want to have a `**` operator in your application, you could do a simple pre-processing step of the expression using a regexp: replace all occurrences of `**` with `^`.", "title": null, "type": "comment" }, { "action": "created", "author": "runxel", "comment_id": 856249819, "datetime": 1623099199000, "masked_author": "username_0", "text": "Okay, working together on large projects is a valid argument.\r\nTo be honest, I was more concerned with cases where people aren't using Math.js directly as a lib, but as an engine.\r\nE.g. take the VSCode plugin [Calculate](https://marketplace.visualstudio.com/items?itemName=acarreiro.calculate), which uses VSCode. This is how I originally stumbled upon the missing double asterisk notation.\r\nIt didn't worked and it took me quite some time to find out, it wasn't a problem of me the user, or the plugin, but Math.js.\r\nSo while I think you have some good points, I still believe that this decision could be reconsidered :)\r\nAs possible solution could be a global switch to enable this behaviour or something similar.\r\nBut yeah, a _hint_ is a start at least ;)", "title": null, "type": "comment" }, { "action": "closed", "author": "josdejong", "comment_id": null, "datetime": 1623179083000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" }, { "action": "created", "author": "josdejong", "comment_id": 857022007, "datetime": 1623179083000, "masked_author": "username_1", "text": "👍 \r\n\r\nYes good point about using mathjs as an engine. Like when entering an expression in google, you just want to get the result. I'm afraid though there is no silver bullet in always understanding the users intentions. When supporting both `**` and `^`, it could be even more likely that a user expects `6` as result of `5^3`, since, you know, `^` in many programming languages is the XOR operator. In the expression parser we do our best to offer a coherent API, trying to stay close to an API that mathematicians will be familiar with. This differs at some points from the syntax that programmers are familiar with. See https://mathjs.org/docs/expressions/syntax.html#differences-from-javascript\r\n\r\nTo conclude, let's not add `**` as an alias for `^`. If there is enough interest in providing a hint when this operator is used, or when there are more similar cases that can benefit from giving the user a hint, we can look into extending the expression parser to provide such hints. I'll close this issue now, thanks for all your inputs.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "JamesLovie", "comment_id": null, "datetime": 1620375399000, "masked_author": "username_0", "text": "I've been Googling and going through logs to try and solve this, but I can't seem to get microk8s to work on my Raspberry Pi, running Ubuntu 20.10\r\n\r\nMicrok8s 1.21 just fails to start the node at all. Gets stuck on \"kube-proxy Starting kube-proxy.\" when running describe node command.\r\n\r\nI then snap install v1.15 which at least starts the node to running state.\r\nsudo snap install microk8s --classic --channel=1.15/stable\r\n\r\nI can confirm that microk8s.status returns that it is running.\r\nkubectl get nodes --namespace kube-system returns:\r\n```\r\nNAME STATUS ROLES AGE VERSION\r\nmydnsname Ready <none> 22h v1.15.11 \r\n```\r\n\r\nI have installed the following enabled: dashboard\r\nI had dashboard dns ingress - installed but the same issue was present.\r\n\r\nkubectl get all --all-namespaces returns\r\n```\r\nNAMESPACE NAME READY STATUS RESTARTS AGE\r\nkube-system pod/heapster-v1.5.2-c4dcfd9f8-kl5g5 0/4 ContainerCreating 0 68s\r\nkube-system pod/kubernetes-dashboard-c775bf88b-pmhz6 0/1 ContainerCreating 0 68s\r\nkube-system pod/monitoring-influxdb-grafana-v4-6f74479987-rd5ck 0/2 ContainerCreating 0 68s\r\n\r\n\r\nNAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE\r\ndefault service/kubernetes ClusterIP 10.152.183.1 <none> 443/TCP 18h\r\nkube-system service/heapster ClusterIP 10.152.183.195 <none> 80/TCP 68s\r\nkube-system service/kubernetes-dashboard ClusterIP 10.152.183.171 <none> 443/TCP 68s\r\nkube-system service/monitoring-grafana ClusterIP 10.152.183.120 <none> 80/TCP 68s\r\nkube-system service/monitoring-influxdb ClusterIP 10.152.183.175 <none> 8083/TCP,8086/TCP 68s\r\n\r\n\r\nNAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE\r\nkube-system deployment.apps/heapster-v1.5.2 0/1 1 0 68s\r\nkube-system deployment.apps/kubernetes-dashboard 0/1 1 0 68s\r\nkube-system deployment.apps/monitoring-influxdb-grafana-v4 0/1 1 0 68s\r\n\r\nNAMESPACE NAME DESIRED CURRENT READY AGE\r\nkube-system replicaset.apps/heapster-v1.5.2-c4dcfd9f8 1 1 0 68s\r\nkube-system replicaset.apps/kubernetes-dashboard-c775bf88b 1 1 0 68s\r\nkube-system replicaset.apps/monitoring-influxdb-grafana-v4-6f74479987 1 1 0 68s\r\n```\r\n\r\nkubectl describe pods kubernetes-dashboard-c775bf88b-pmhz6 --namespace kube-system returns\r\n```\r\nWarning FailedCreatePodSandBox 2m26s (x3 over 2m54s) kubelet, mydnsname (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: failed to mount rootfs component &{overlay overlay [workdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/1386/work upperdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/1386/fs lowerdir=/var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/2/fs]}: invalid argument: unknown\r\n Warning MissingClusterDNS 2m14s (x13 over 4m58s) kubelet, mydnsname pod: \"kubernetes-dashboard-c775bf88b-pmhz6_kube-system(777df7aa-d4de-40f0-8275-70b36d2e5029)\". kubelet does not have ClusterDNS IP configured and cannot create Pod using \"ClusterFirst\" policy. Falling back to \"Default\" policy.\r\n```\r\n\r\nI have checked and I am not using ZFS as my filesystem for my main partition, I'm using overlayfs\r\ndf -Th\r\n```\r\nFilesystem Type Size Used Avail Use% Mounted on\r\nnone **overlay** 59G 21G 36G 37% /\r\ntmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm\r\ntmpfs tmpfs 743M 1.2M 742M 1% /run\r\ntmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock\r\ntmpfs tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup\r\ntmpfs tmpfs 372M 104K 372M 1% /run/user/1000\r\n```\r\n[inspection-report-20210507_181312.tar.gz](https://github.com/ubuntu/microk8s/files/6440095/inspection-report-20210507_181312.tar.gz)\r\n\r\nTherefore I'm not sure why containerd can't mount or has an issue, considering that containerd doesn't have any issues with overlayfs.\r\n\r\nHave tried microk8s.reset and uninstalling and reinstalling, and tried a few different versions and still to no avail.\r\n\r\nAny ideas or assistance is greatly appreciated as I'm keen to get a local kubernetes setup for local dev!\r\n\r\nThanks in advance!", "title": "MicroK8s 1.15 containers unable to start. All pods stuck on \"ContainerCreating\" state. Ubuntu 20.10 RP4", "type": "issue" }, { "action": "created", "author": "balchua", "comment_id": 834287394, "datetime": 1620386878000, "masked_author": "username_1", "text": "I will recommend that we fix your issue with MicroK8s v 1.21 atleast. 1.15 is no longer active.\r\n\r\nSo when you install microk8s v1.21 can you run the inspect command and upload the tarball?\r\nThanks.", "title": null, "type": "comment" }, { "action": "created", "author": "JamesLovie", "comment_id": 834297432, "datetime": 1620387726000, "masked_author": "username_0", "text": "Thanks @username_1 for getting back to me.\r\n\r\nI have just:\r\n```\r\nsudo microk8s.reset\r\nsudo microk8s stop && sudo snap remove microk8s\r\nsudo snap install microk8s --classic --channel=1.21 \r\n```\r\n\r\nThen ran microk8s.inspect and uploaded tarball.\r\n\r\nThanks\r\n[inspection-report-20210507_214053.tar.gz](https://github.com/ubuntu/microk8s/files/6441245/inspection-report-20210507_214053.tar.gz)", "title": null, "type": "comment" }, { "action": "created", "author": "balchua", "comment_id": 834311156, "datetime": 1620388860000, "masked_author": "username_1", "text": "Suggest to do \r\n`sudo snap remove microk8s --purge`. This will remove any remnants of microk8s.\r\n\r\nThen you can do `sudo snap install microk8s --channel 1.21/stable`\r\n\r\nMay i know the rpi 4 specs? Just so you know if ur running on a 1GB RAM, the kernel might kill the apiserver due to OOM.", "title": null, "type": "comment" }, { "action": "created", "author": "balchua", "comment_id": 834331552, "datetime": 1620390490000, "masked_author": "username_1", "text": "Hi @username_0 i just looked at the last tarball you uploaded.\r\n\r\nI wonder if you have storage in place. Microk8s need to have a good amount of storage in `/var/snap/microk8s`. Make sure you have that.\r\n\r\nIn the inspect tarball `df -h` yields nothing.\r\nCan you do a `df -h|?", "title": null, "type": "comment" }, { "action": "created", "author": "JamesLovie", "comment_id": 835267802, "datetime": 1620468876000, "masked_author": "username_0", "text": "Hi @username_1 I think it's working now!\r\n\r\nYou were correct in that Microk8s, specifically containerd, didn't work with a squashfs with overlay.\r\n\r\nReason being, BerryBoot uses SquashFS images and the lowerdir I think was SquashFS for root.\r\n\r\nI reinstalled Ubuntu using PINN, which makes root ext4 filesystem.\r\n\r\nAfter enabling cgroups, I was able to start microk8s 1.21 and see the node in running state.\r\n\r\nAfter running kubectl get all --namespace kube-system\r\nI get all nodes returning running state now!\r\n\r\nThanks for your help.\r\n\r\nJames", "title": null, "type": "comment" }, { "action": "created", "author": "balchua", "comment_id": 835275166, "datetime": 1620469628000, "masked_author": "username_1", "text": "Glad that it's working!! Im going to close this issue! Thanks for using MicroK8s! 👍", "title": null, "type": "comment" }, { "action": "closed", "author": "balchua", "comment_id": null, "datetime": 1620469629000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

{ "number": 54, "repo": "linz-lds-bde-schema", "user_login": "linz" }

[ { "action": "opened", "author": "strk", "comment_id": null, "datetime": 1510527364000, "masked_author": "username_0", "text": "See #42", "title": "Add tests for linz-lds-bde-schema-load", "type": "issue" }, { "action": "created", "author": "strk", "comment_id": 343799875, "datetime": 1510543385000, "masked_author": "username_0", "text": "Current failure for this is unrelated to the topic of this PR but rather related to #55 which will be fixed by #56 This is to be rebased after merge of the latter.", "title": null, "type": "comment" }, { "action": "created", "author": "strk", "comment_id": 344384409, "datetime": 1510690610000, "masked_author": "username_0", "text": "This PR adds dependency (of the testing infrastructure: \"make installcheck\") on yet-to-be-released versions of table_version, dbpatch and linz-bde-schema. This is because the new \"installcheck\" rule will use their \"loader\" scripts to simplify things (ie: figuring out where the sql scripts are installed)\r\n\r\nMaybe it should wait for an actual new release of those deps to be cut.", "title": null, "type": "comment" }, { "action": "created", "author": "imincik", "comment_id": 347897536, "datetime": 1511969669000, "masked_author": "username_1", "text": "@username_0 , is there any reason why we can't install dbpatch and tableversion from LINZ public PPA ? One of advantages will be that we will always have latest version. Or is it because PPA doesn't contain required versions yet ?", "title": null, "type": "comment" }, { "action": "created", "author": "imincik", "comment_id": 347898249, "datetime": 1511969792000, "masked_author": "username_1", "text": "I see, we have old versions in PPA. Would you please add ticket to migrate tests to PPA once packages will be updated there ? Thanks", "title": null, "type": "comment" } ]

{ "number": 7752, "repo": "cudf", "user_login": "rapidsai" }

[ { "action": "opened", "author": "ttnghia", "comment_id": null, "datetime": 1617041924000, "masked_author": "username_0", "text": "This PR implements scattering for struct columns. It also fixes #7638 when calling `cudf::partitioning` on struct data due to wrongly scattering data inside the partitioning kernels.", "title": "Implement scatter for struct columns", "type": "issue" }, { "action": "created", "author": "ttnghia", "comment_id": 809604715, "datetime": 1617041971000, "masked_author": "username_0", "text": "Currently I'm working on unit tests for struct scattering, which should be done shortly.", "title": null, "type": "comment" }, { "action": "created", "author": "ttnghia", "comment_id": 810691063, "datetime": 1617154826000, "masked_author": "username_0", "text": "Rerun tests.", "title": null, "type": "comment" }, { "action": "created", "author": "ttnghia", "comment_id": 811301809, "datetime": 1617214406000, "masked_author": "username_0", "text": "Rerun tests.", "title": null, "type": "comment" }, { "action": "created", "author": "ttnghia", "comment_id": 812142834, "datetime": 1617307678000, "masked_author": "username_0", "text": "@gpucibot merge", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "Vishvak365", "comment_id": null, "datetime": 1606338541000, "masked_author": "username_0", "text": "- [ ] Car running\r\n- [ ] Car accelerating\r\n- [ ] Car crash\r\n- [ ] Music in Menu\r\n- [ ] Winning Music", "title": "Include audio for different events", "type": "issue" }, { "action": "closed", "author": "carsonhamel", "comment_id": null, "datetime": 1606680566000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "NickNo-dev", "comment_id": null, "datetime": 1610100505000, "masked_author": "username_0", "text": "Currently the builder spits out UNIX Line endings instead of the *required* Windows line endings.\r\nThis results in none of the files being read by the LP engine. (At least on Windows host OS)", "title": "critical: UNIX line endings instead of windows CRLF", "type": "issue" }, { "action": "created", "author": "NickNo-dev", "comment_id": 756669851, "datetime": 1610100589000, "masked_author": "username_0", "text": "To be precise: as the bulder also touches all other file this renders the lpmod, lpaction, lpstat etc etc ununsable as well.", "title": null, "type": "comment" }, { "action": "closed", "author": "Rizean", "comment_id": null, "datetime": 1610109567000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" }, { "action": "created", "author": "NickNo-dev", "comment_id": 756755331, "datetime": 1610112469000, "masked_author": "username_0", "text": "Not fixed completely. 👎 \r\nIncludes will still result in LF.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "kaplan441", "comment_id": null, "datetime": 1605800707000, "masked_author": "username_0", "text": "I'm using spring boot admin. My boot admin clients run as docker swarm service.\r\nWhen I start my client application as container it register to admin server. But when I start client as docker swarm service then register fail.\r\nI tried spring.boot.admin.client.prefer-ip=true but it still.\r\nHow can i fix this problem?\r\n\r\n`java.lang.IllegalArgumentException: b77cbc25ddfb: b77cbc25ddfb: Temporary failure in name resolution\r\n\tat de.codecentric.boot.admin.client.registration.DefaultApplicationFactory.getLocalHost(DefaultApplicationFactory.java:186) ~[spring-boot-admin-client-2.3.1.jar:2.3.1]\r\n\tat de.codecentric.boot.admin.client.registration.DefaultApplicationFactory.getServiceHost(DefaultApplicationFactory.java:168) ~[spring-boot-admin-client-2.3.1.jar:2.3.1]\r\n\tat de.codecentric.boot.admin.client.registration.DefaultApplicationFactory.getServiceBaseUrl(DefaultApplicationFactory.java:103) ~[spring-boot-admin-client-2.3.1.jar:2.3.1]\r\n\tat de.codecentric.boot.admin.client.registration.ServletApplicationFactory.getServiceUrl(ServletApplicationFactory.java:63) ~[spring-boot-admin-client-2.3.1.jar:2.3.1]\r\n\tat de.codecentric.boot.admin.client.registration.ServletApplicationFactory.getManagementBaseUrl(ServletApplicationFactory.java:76) ~[spring-boot-admin-client-2.3.1.jar:2.3.1]\r\n\tat de.codecentric.boot.admin.client.registration.DefaultApplicationFactory.getHealthUrl(DefaultApplicationFactory.java:154) ~[spring-boot-admin-client-2.3.1.jar:2.3.1]\r\n\tat de.codecentric.boot.admin.client.registration.DefaultApplicationFactory.createApplication(DefaultApplicationFactory.java:80) ~[spring-boot-admin-client-2.3.1.jar:2.3.1]\r\n\tat de.codecentric.boot.admin.client.registration.DefaultApplicationRegistrator.register(DefaultApplicationRegistrator.java:56) ~[spring-boot-admin-client-2.3.1.jar:2.3.1]\r\n\tat org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-5.2.9.RELEASE.jar:5.2.9.RELEASE]\r\n\tat java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[na:na]\r\n\tat java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source) ~[na:na]\r\n\tat java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) ~[na:na]\r\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[na:na]\r\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[na:na]\r\n\tat java.base/java.lang.Thread.run(Unknown Source) ~[na:na]\r\n\r\nCaused by: java.net.UnknownHostException: b77cbc25ddfb: b77cbc25ddfb: Temporary failure in name resolution\r\n\tat java.base/java.net.InetAddress.getLocalHost(Unknown Source) ~[na:na]\r\n\tat de.codecentric.boot.admin.client.registration.DefaultApplicationFactory.getLocalHost(DefaultApplicationFactory.java:183) ~[spring-boot-admin-client-2.3.1.jar:2.3.1]\r\n\t... 14 common frames omitted\r\nCaused by: java.net.UnknownHostException: b77cbc25ddfb: Temporary failure in name resolution\r\n\tat java.base/java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) ~[na:na]\r\n\tat java.base/java.net.InetAddress$PlatformNameService.lookupAllHostAddr(Unknown Source) ~[na:na]\r\n\tat java.base/java.net.InetAddress.getAddressesFromNameService(Unknown Source) ~[na:na]\r\n\tat java.base/java.net.InetAddress$NameServiceAddresses.get(Unknown Source) ~[na:na]\r\n\tat java.base/java.net.InetAddress.getAllByName0(Unknown Source) ~[na:na]\r\n\t... 16 common frames omitted`", "title": "Client does not register to admin server in docker", "type": "issue" }, { "action": "created", "author": "kaplan441", "comment_id": 730605270, "datetime": 1605816157000, "masked_author": "username_0", "text": "Edit: \r\n \r\n```\r\nspring:\r\n boot:\r\n admin:\r\n client:\r\n instance:\r\n prefer-ip: true\r\n service-url: http://${HOST_NAME}:${PORT}/\r\n name: ${APP_NAME}\r\n```\r\nAfter this addition docker service registered to admin server. But when i increase service instance count( ex: from 1 to 2), only one application registered to admin server(so naturally all instance executed one exposed port)\r\n\r\nCan i set docker container id etc information to client, so i see all instance of application in admin server?", "title": null, "type": "comment" }, { "action": "created", "author": "joshiste", "comment_id": 734407131, "datetime": 1606410167000, "masked_author": "username_1", "text": "SBA uses the health url to differentiate the services. Also to check the health of the individual instances we need the individual urls.", "title": null, "type": "comment" }, { "action": "closed", "author": "joshiste", "comment_id": null, "datetime": 1606410199000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" }, { "action": "created", "author": "joshiste", "comment_id": 734407697, "datetime": 1606410256000, "masked_author": "username_1", "text": "looks like a general issue and not specific to SBA", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "SimonHogstromRonbol", "comment_id": null, "datetime": 1614757736000, "masked_author": "username_0", "text": "## Describe the new feature or change to an existing feature you'd like to see\r\n\r\nHi, i brought this up on slack and was directed to make an issue about it.\r\n\r\nOnline chat service support is something that we have a lot of clients requesting, especially recently.\r\nCurrently, the solution we've come up with is having the chat widget run in an iframe on the site.\r\n\r\nThe problem with the iframe solution is that it isn't very flexible, and you often end up with a janky semi solution.\r\n\r\nSo I saw an ad yesterday for Google Business Messages, and it looks like instead of it being something that our clients would have to request from us and get a janky solution, we could instead actually provide a first party solution for AMP with an integrated \"Google Business Messages\" widget directly on the website.\r\n\r\nThen I realized that there wasn't such a component yet, for the website widget and that brings me here.\r\n\r\nIs there a Google Business Messages component being worked on, or is it something you would consider supporting in the future?\r\n\r\n\r\n## Describe alternatives you've considered\r\n\r\nWe've tried using Zendesk for a live chat, and we came pretty close with an iframe solution, we made a button that looked like a Zendesk button that opens an iframe with the chat widget expanded inside, but the solution is a little too janky cause the button is supposed to have different text dependent on different factors in your zendesk app, and it all becomes very messy, fast.\r\n\r\n[here](https://www.proventic.dk/) is the widget on a site in production, note that there is a mandatory delay before the widget shows up.\r\n\r\n## Additional context\r\n\r\nhere is the current integration documentation for implementing the Google Business Messages website on a non-amp site:\r\nhttps://developers.google.com/business-communications/business-messages/guides/build/web-widget\r\n\r\n@username_1", "title": "Google Business Messages component for AMP", "type": "issue" }, { "action": "created", "author": "erwinmombay", "comment_id": 790037270, "datetime": 1614803699000, "masked_author": "username_1", "text": "thanks @krdwan . leaving this for your team to triage", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "webebox", "comment_id": null, "datetime": 1584002749000, "masked_author": "username_0", "text": "**Describe the bug**\r\nI just installed Blazord Modal. everything works good but when I want to use BlazoredModalInstance it says.\r\nhe type of namespace name 'BlazoredModalInstance' could not be found.\r\nI tryed to use Blazored.Modal.BlazoredModalInstance\r\nbut this component is not exists.\r\nMy version is 3.1.2.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\n1. Go to '...'\r\n2. Click on '....'\r\n3. Scroll down to '....'\r\n4. See error\r\n\r\n**Expected behavior**\r\nA clear and concise description of what you expected to happen.\r\n\r\n**Screenshots**\r\nIf applicable, add screenshots to help explain your problem.\r\n\r\n**Hosting Model (is this issue happening with a certain hosting model?):**\r\n - Blazor Server\r\n - Blazor WebAssembly\r\n - etc...\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.", "title": "[Bug] the type of namespace name 'BlazoredModalInstance' could not be found", "type": "issue" }, { "action": "created", "author": "larsk2009", "comment_id": 598072444, "datetime": 1584002939000, "masked_author": "username_1", "text": "Hi @username_0 . If you are using v3.1.2 of blazored.modal, please see this version of the readme instructions: https://github.com/Blazored/Modal/tree/v3.1.0. THe BlazoredModalInstance is introduced in v4.0.0 of blazored.modal, which has not been released yet.", "title": null, "type": "comment" }, { "action": "created", "author": "webebox", "comment_id": 598076946, "datetime": 1584003583000, "masked_author": "username_0", "text": "Hi @username_1 , thank you for your reply. I just tryed the BlazorServer example, it includes 'Blazored.Modal' class library contains 'BlazoredModalInstance.razor' \r\nSo how I can close the modal inside it when I can not make use of BlazoredModalInstance.Close method ?", "title": null, "type": "comment" }, { "action": "created", "author": "chrissainty", "comment_id": 598079079, "datetime": 1584003891000, "masked_author": "username_2", "text": "@username_0 If you [browse the repo at this point in time](https://github.com/Blazored/Modal/tree/3f8a54eaf3e4cdcc985ebe67249bb6c2f4ad3540) you can see the correct configuration you need.\r\n\r\nApologies for this, I'm hoping to push the new version today so everything will be in sync again.", "title": null, "type": "comment" }, { "action": "created", "author": "webebox", "comment_id": 598097147, "datetime": 1584006474000, "masked_author": "username_0", "text": "@username_2 We are waiting impatiently! I asked the team to stop the project until your release.\r\nThanks", "title": null, "type": "comment" }, { "action": "created", "author": "chrissainty", "comment_id": 598098329, "datetime": 1584006651000, "masked_author": "username_2", "text": "@username_0 This is something I do in my spare time, on top of a full-time job and other community activitiesd, FOR FREE. Please keep this in mind.", "title": null, "type": "comment" }, { "action": "closed", "author": "chrissainty", "comment_id": null, "datetime": 1584099243000, "masked_author": "username_2", "text": "", "title": null, "type": "issue" } ]

{ "number": 1954, "repo": "souffle", "user_login": "souffle-lang" }

[ { "action": "opened", "author": "b-scholz", "comment_id": null, "datetime": 1624336689000, "masked_author": "username_0", "text": "The scanner structure `scanner_data` is renamed to ScannerInfo (for sake of consistency) and is moved to the header `SrcLocation.h`. The local definition in `parser.hh` caused issues with cmake.", "title": "Move struct def to header file", "type": "issue" }, { "action": "created", "author": "b-scholz", "comment_id": 865529400, "datetime": 1624336728000, "masked_author": "username_0", "text": "Please merge after previous PR.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "WeMayNeverKnow", "comment_id": null, "datetime": 1620006602000, "masked_author": "username_0", "text": "Tag commands? We all know this I don't need to explain", "title": "New Command Suggestion: Tag", "type": "issue" }, { "action": "closed", "author": "m0nk3ybraindead", "comment_id": null, "datetime": 1644488910000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "gnnslav", "comment_id": null, "datetime": 1620043893000, "masked_author": "username_0", "text": "Посилання на соцмережі (Facebook чи Instagram, тощо), номер телефону чи адреса електронної скриньки, тощо. Може не всі лінки в світі, а тільки ті, що дійсно доречні.", "title": "Скласти блок контактної інформації", "type": "issue" }, { "action": "created", "author": "nadiya-gizhitska", "comment_id": 831225693, "datetime": 1620044706000, "masked_author": "username_1", "text": "https://www.facebook.com/profile.php?id=100004808958030\r\nryuwins@gmail.com\r\nhttps://twitter.com/denjinryu\r\nhttps://www.instagram.com/sworn_ryu/", "title": null, "type": "comment" }, { "action": "closed", "author": "gnnslav", "comment_id": null, "datetime": 1620044964000, "masked_author": "username_0", "text": "", "title": null, "type": "issue" } ]

{ "number": 4827, "repo": "strimzi-kafka-operator", "user_login": "strimzi" }

[ { "action": "opened", "author": "PaulRMellor", "comment_id": null, "datetime": 1619520064000, "masked_author": "username_0", "text": "**Documentation**\r\n\r\nNew section for the _Using_ guide that provides tips on tuning broker configuration\r\n\r\nIncludes new diagrams that will be refined and standardized after review.\r\n\r\n### Checklist\r\n\r\n_Please go through this checklist and make sure all applicable tasks have been done_\r\n\r\n- [ ] Write tests\r\n- [ ] Make sure all tests pass\r\n- [ ] Update documentation\r\n- [ ] Check RBAC rights for Kubernetes / OpenShift roles\r\n- [ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally\r\n- [ ] Reference relevant issue(s) and close them after merging\r\n- [ ] Update CHANGELOG.md\r\n- [ ] Supply screenshots for visual changes, such as Grafana dashboards", "title": "[DOC] broker tuning", "type": "issue" }, { "action": "created", "author": "PaulRMellor", "comment_id": 829339259, "datetime": 1619710319000, "masked_author": "username_0", "text": "Right. Well, we're reusing this content in the RHEL doc too, so probably best to keep the `=`. The headers I can change to [source, env]", "title": null, "type": "comment" }, { "action": "created", "author": "scholzj", "comment_id": 829359371, "datetime": 1619711726000, "masked_author": "username_1", "text": "Not sure how confusing it will be for users - but I guess in the worst case they will get an error when creating the resource. And so far IMHO nobody complained. So I'm fine to keep the examples as they are and fix the headers.", "title": null, "type": "comment" }, { "action": "created", "author": "PaulRMellor", "comment_id": 838504033, "datetime": 1620740784000, "masked_author": "username_0", "text": "@tombentley Thanks for the latest comments. I've left a couple unresolved, which you might want to check. \r\nI've also rearranged the sections on _Managing logs with data retention policies_ and _Removing log data with cleanup policies_, with additions like using topic-level cleanup policy and _tombstones_.", "title": null, "type": "comment" }, { "action": "created", "author": "PaulRMellor", "comment_id": 841137101, "datetime": 1620985499000, "masked_author": "username_0", "text": "@LiamClarkeNZ has no further comments to add.", "title": null, "type": "comment" } ]

{ "number": 234, "repo": "pandora", "user_login": "rmcolq" }

[ { "action": "opened", "author": "mbhall88", "comment_id": null, "datetime": 1601102130000, "masked_author": "username_0", "text": "I found myself needing to expose more and more *de novo* parameters at the CLI and realised it was all cluttering `map`. There could also a *slightly* misleading perception that using `--discover --genotype` in `map` would genotype with the discovered variants (which it doesn't). Anyway, I forsee - when we have self-container *de novo* variant integration - the need to have this subcommand output a new PRG with variants added, or even another subcommand `augment`.\r\n\r\n## Added\r\n- New subcommand `pandora discover`\r\n```\r\n$ pandora discover --help\r\nQuasi-map reads to an indexed PRG, infer the sequence of present loci in the sample and discover novel variants.\r\nUsage: ./pandora discover [OPTIONS] <TARGET> <QUERY>\r\n\r\nPositionals:\r\n <TARGET> FILE [required] An indexed PRG file (in fasta format)\r\n <QUERY> FILE [required] Fast{a,q} file containing reads to quasi-map\r\n\r\nOptions:\r\n -h,--help Print this help message and exit\r\n --discover-k INT K-mer size to use when discovering novel variants [default: 11]\r\n --max-ins INT Max. insertion size for novel variants. Warning: setting too long may impair performance [default: 15]\r\n --covg-threshold INT Positions with coverage less than this will be tagged for variant discovery [default: 3]\r\n -l INT Min. length of consecutive positions below coverage threshold to trigger variant discovery [default: 1]\r\n -L INT Max. length of consecutive positions below coverage threshold to trigger variant discovery [default: 50]\r\n -P,--pad INT Padding either side of candidate variant intervals [default: 22]\r\n -d,--merge INT Merge candidate variant intervals within distance [default: 22]\r\n --min-dbg-dp INT Minimum node/kmer depth in the de Bruijn graph used for discovering variants [default: 2]\r\n -v Verbosity of logging. Repeat for increased verbosity\r\n\r\nIndexing:\r\n -w INT Window size for (w,k)-minimizers (must be <=k) [default: 14]\r\n -k INT K-mer size for (w,k)-minimizers [default: 15]\r\n\r\nInput/Output:\r\n -o,--outdir DIR Directory to write output files to [default: pandora_discover]\r\n -t,--threads INT Maximum number of threads to use [default: 1]\r\n --kg Save kmer graphs with forward and reverse coverage annotations for found loci\r\n -M,--mapped-reads Save a fasta file for each loci containing read parts which overlapped it\r\n\r\nParameter Estimation:\r\n -e,--error-rate FLOAT Estimated error rate for reads [default: 0.11]\r\n -g,--genome-size STR/INT Estimated length of the genome - used for coverage estimation. Can pass string such as 4.4m, 100k etc. [default: 5000000]\r\n --bin Use binomial model for kmer coverages [default: negative binomial]\r\n\r\nMapping:\r\n -m,--max-diff INT Maximum distance (bp) between consecutive hits within a cluster [default: 250]\r\n -c,--min-cluster-size INT Minimum size of a cluster of hits between a read and a loci to consider the loci present [default: 10]\r\n\r\nPreset:\r\n -I,--illumina Reads are from Illumina. Alters error rate used and adjusts for shorter reads\r\n\r\nFiltering:\r\n --clean Add a step to clean and detangle the pangraph\r\n --max-covg INT Maximum coverage of reads to accept [default: 600]\r\n\r\nConsensus/Variant Calling:\r\n --kmer-avg INT Maximum number of kmers to average over when selecting the maximum likelihood path [default: 100]\r\n```\r\n- function to merge candidate regions within a certain distance [closes #228] and `-d,--merge` to specify the distance at CLI\r\n- `--min-dbg-dp` to expose minimum adbundance in GATB graph\r\n- `-l` and `-L` for min/max candidate region length\r\n- `-P,--pad` to specify candidate region padding\r\n\r\n## Changed\r\n- allow `-g,--genome-size` to take a string such as `4.4m` [closes #233]\r\n- some logging cleanup/level changes\r\n \r\n## Removed\r\n- `--coverages` option from `map` as it wasn't being used", "title": "Move variant discovery to its own subcommand", "type": "issue" }, { "action": "created", "author": "mbhall88", "comment_id": 700430878, "datetime": 1601356419000, "masked_author": "username_0", "text": "I have (successfully) run the tip of this branch on multiple samples.", "title": null, "type": "comment" }, { "action": "created", "author": "mbhall88", "comment_id": 707505623, "datetime": 1602568314000, "masked_author": "username_0", "text": "As a way of validating this is working - in tandem with https://github.com/username_0/head_to_head_pipeline/issues/54 - here is a picture of the precision and recall for the version of pandora in this PR\r\n\r\n**fixed_prgs is the data from this PR**\r\n\r\n## Recall\r\n\r\n\r\n\r\n## Precision\r\n\r\nNote: fixed_prgs is unfiltered here\r\n\r\n", "title": null, "type": "comment" } ]

{ "number": 4658, "repo": "realm-core", "user_login": "realm" }

[ { "action": "opened", "author": "cmelchior", "comment_id": null, "datetime": 1619962544000, "masked_author": "username_0", "text": "We already have `freeze` API's for all classes, but the reverse API `thaw()` has only been implemented directly in the Cocoa SDK (https://github.com/realm/realm-cocoa/pull/6975).\r\n\r\nThe Kotlin SDK needs similar mechanisms for it to work, so this PR adds `freeze/thaw` to SharedRealm, Results, List and Object in both ObjectStore and the C-API.\r\n\r\nWhile the `thaw()` API more or less directly mirrors the `import_copy()` API in Core, having it exposed in the higher-level semantics of ObjectStore makes it much easier to reason about and use, as well as allows for future optimizations.\r\n\r\nTODO:\r\n- [x] Understand why some methods in the C-API return `bool` and others have `out_<param>`. For now I followed the pattern already existing for `freeze()`\r\n- [x] Add unit tests for ObjectStore and the C-API for the new methods\r\n\r\nRegarding error reporting: All added functions returns pointers that follows the existing scheme in the C-API (AFIK)\r\nRegarding unit tests: Added tests for the C-API. Don't know if we need explicit test for the ObjectStore API.", "title": "Add Freeze/Thaw API's to Realm/Results/List/Object.", "type": "issue" }, { "action": "created", "author": "rorbech", "comment_id": 837968020, "datetime": 1620717204000, "masked_author": "username_1", "text": "@simonask I addressed your comments by adding some comments and aligning the asserts. However, I guess introducing asserts for the existing `freeze` on objects and results are technically breaking, though I don't think SDK will ever call these with a non-frozen realm. Is it safe enough to add?\r\n\r\nAlternatively we could have done a generic `import_copy_of` so it was up to the SDK to keep track of frozen/life-state of the realms themselves and reasoning about the resulting object from that, but it would introduce another ffi-call if we would like to do similar asserts in the SDK.", "title": null, "type": "comment" }, { "action": "created", "author": "rorbech", "comment_id": 901909535, "datetime": 1629379168000, "masked_author": "username_1", "text": "I removed the asserts that caused a breaking API. Don't know if we should also remove the assert in the thawing methods too to make it symmetrical? 🤔\r\n\r\nOnly lacking thing is that it would be nice with a specific error/error code if we are trying to thaw an object that has been deleted. In Kotlin we are offering a `findLatest(object)` that we would like to return null in case the object is no longer needed. Our current implementation catches C-API errors and returns null, but we should only do this in the specific situation where the object is just not longer valid. Given the latest discussion about error codes, this is maybe not for this PR.", "title": null, "type": "comment" }, { "action": "created", "author": "nirinchev", "comment_id": 910082726, "datetime": 1630486759000, "masked_author": "username_2", "text": "Okay, I saw your comment that thawing a deleted object will throw an error. I think this is wrong. That is not an unexpected/erroneous situation and we should not use exceptions to relay such information. I would propose that we align the C API to that of the SDK and rework these functions as `try_freeze` and `try_thaw` or whatever follows the C API conventions.", "title": null, "type": "comment" }, { "action": "created", "author": "rorbech", "comment_id": 910186577, "datetime": 1630495205000, "masked_author": "username_1", "text": "Simon was the one suggesting the specific error code when the object was deleted. Returning a null pointer is a bit problematic that this conventionally used to indicate the the api call might have caused an error that should be inspected through `realm_get_last_error`. Probably need somebody with more insight than me to decide on that.", "title": null, "type": "comment" }, { "action": "created", "author": "nirinchev", "comment_id": 910196443, "datetime": 1630495845000, "masked_author": "username_2", "text": "I don't see any SDK throwing an error from thaw, which makes it silly to have an API discrepancy between the C API and the SDK API. I believe the solution here would be to change the signature of `freeze/thaw` to something like:\r\n\r\n```cpp\r\nRLM_API bool realm_object_freeze(const realm_object_t* live_object, const realm_t* frozen_realm, realm_object_t* out_frozen_object);\r\n```\r\n\r\nWhere the return value indicates whether the method succeeded or failed and `out_frozen_object` may contain a valid pointer or nullptr.\r\n\r\nIt's possible I'm missing some context here, but generally, it's a bad practice to use errors to handle expected scenarios.", "title": null, "type": "comment" }, { "action": "created", "author": "fealebenpae", "comment_id": 910335781, "datetime": 1630506171000, "masked_author": "username_3", "text": "I agree with Nikola. I think using error codes to signal the object no longer being there is too close to using exceptions for flow control for my taste. His suggestion about returning bool and using an out parameter seems sound to me.", "title": null, "type": "comment" }, { "action": "created", "author": "rorbech", "comment_id": 912516311, "datetime": 1630673624000, "masked_author": "username_1", "text": "I updated the C-API for the thaw-functions where the object or parent object can have been deleted, added test cases (and fixed the error in the implementation).", "title": null, "type": "comment" }, { "action": "created", "author": "fealebenpae", "comment_id": 912520752, "datetime": 1630674044000, "masked_author": "username_3", "text": "The changes in the C API look good, but I'm wondering whether the C++ `thaw()` methods have the correct behavior. Perhaps their signature should be something like `util::Optional<T> T::thaw(const std::shared_ptr<Realm>&)` to indicate that the object returned might not be valid? Otherwise we need to rely on what I think is implicit semantics on Object, List, and Results.", "title": null, "type": "comment" }, { "action": "created", "author": "rorbech", "comment_id": 912549181, "datetime": 1630676471000, "masked_author": "username_1", "text": "I discussed with @username_4 and just followed the pattern of the existing implementation. I don't see that freeze is returning an optional to signal that the object cannot be frozen in the given realm. Maybe somebody from core could take over as it seems like it requires more insight into the overall behaviour. Or we could just go with the current implementation and then add a follow up issue to align the internals. @username_3?", "title": null, "type": "comment" }, { "action": "created", "author": "fealebenpae", "comment_id": 912561546, "datetime": 1630677580000, "masked_author": "username_3", "text": "Optional-ness is sort of a general question I have about the API, I guess, and it's definitely not just about these new methods in this PR. I am happy to merge this as-is, and revising the API with explicit optionality in the type system is definitely something that can happen at a later point and shouldn't block this work.", "title": null, "type": "comment" }, { "action": "created", "author": "rorbech", "comment_id": 914064466, "datetime": 1631000057000, "masked_author": "username_1", "text": "@username_3 @username_2 I updated the C-API to return optional/null when trying to thaw deleted objects/lists. I don't see freezing deleted objects/list as a similar SDK use cases and also wouldn't be able change the API for chose without being a breaking change.", "title": null, "type": "comment" }, { "action": "created", "author": "finnschiermer", "comment_id": 914092703, "datetime": 1631002604000, "masked_author": "username_4", "text": "I think the freeze methods needs to throw if the object isn't present in the target frozen realm.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "ForrestPi", "comment_id": null, "datetime": 1597304468000, "masked_author": "username_0", "text": "## ❓ Questions on how to use PyTorch3D\r\n\r\nHi! I'm new to pytorch3d and I am looking for a sampling function for UV space to vertex space conversion and vertex space to UV map which is differentiable \r\n\r\nThanks, your reply will be vary appreciated.", "title": "Sampling function for UV space to vertex space conversion ", "type": "issue" }, { "action": "created", "author": "gkioxari", "comment_id": 675577618, "datetime": 1597767603000, "masked_author": "username_1", "text": "We provide texture sampling functions with maps and uv coordinates. \r\n\r\nhttps://github.com/facebookresearch/pytorch3d/blob/f03aa5803bcdba3b9447a8c2ffdc77e693d51c87/pytorch3d/renderer/mesh/textures.py#L543", "title": null, "type": "comment" }, { "action": "closed", "author": "gkioxari", "comment_id": null, "datetime": 1601069355000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" }, { "action": "created", "author": "gkioxari", "comment_id": 699164360, "datetime": 1601069355000, "masked_author": "username_1", "text": "No response! Closing this issue.", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "ioBrokerChecker", "comment_id": null, "datetime": 1620225693000, "masked_author": "username_0", "text": "Dear Adapter developer,\r\n\r\nwith js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.\r\n\r\nIf something is not correct this is logged as 'warning' or 'info' log.\r\n\r\nPlease take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.\r\n\r\nFor questions please refer to https://github.com/ioBroker/ioBroker.js-controller/issues/1301 \r\n\r\nAdditionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.\r\n\r\nMore informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui \r\n\r\nPlease close the issue after you checked it.\r\n\r\nThank you very much for your support!", "title": "Compatibility check to js-controller 3.3 and Admin5 React UI", "type": "issue" }, { "action": "closed", "author": "jogibear9988", "comment_id": null, "datetime": 1622968329000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "gkatsanos", "comment_id": null, "datetime": 1612087112000, "masked_author": "username_0", "text": "Hey guys, \r\n\r\nI'd like to contribute to the docs on the topic. If someone throws some quick info in this thread as I've spent hours and hours trying to get SSR VSCode debugging to work. Specifically there's nothing with regards to sourcemaps. \r\nAs it stands, standard starter template is unable to bind to any breakpoints on VSCode for SSR code (`asyncData()` for example)", "title": "One more issue for SSR debugging not working", "type": "issue" }, { "action": "created", "author": "gkatsanos", "comment_id": 770414362, "datetime": 1612112762000, "masked_author": "username_0", "text": "@danielpost if anyone from the team has experience on debugging and can give a tip or two, I'd gladly redact the doc for this and make a MR. It's possible though that some changes in the base webpack configuration are needed?", "title": null, "type": "comment" }, { "action": "created", "author": "fabis94", "comment_id": 776091503, "datetime": 1612890356000, "masked_author": "username_1", "text": "Some sort of docs for debugging SSR are definitely necessary, I've also been unable to find any useful documentation for setting it up. I was able to start the nuxt process with the `--inspect` flag, but no breakpoints work.", "title": null, "type": "comment" }, { "action": "created", "author": "ed3899", "comment_id": 798576737, "datetime": 1615652292000, "masked_author": "username_2", "text": "Same issues here. I'm developing a static website with Nuxt and Typescript (No custom server) with these launch.json specs\r\n\r\n\r\n```\r\n{\r\n \"version\": \"0.2.0\",\r\n \"configurations\": [\r\n {\r\n \"type\": \"chrome\",\r\n \"runtimeExecutable\": \"C:\\\\Program Files (x86)\\\\BraveSoftware\\\\Brave-Browser\\\\Application\\\\brave.exe\",\r\n \"request\": \"launch\",\r\n \"name\": \"client: chrome\",\r\n \"url\": \"http://localhost:4000\",\r\n \"webRoot\": \"${workspaceFolder}\"\r\n },\r\n {\r\n \"type\": \"node\",\r\n \"request\": \"launch\",\r\n \"name\": \"server: nuxt\",\r\n \"args\": [\"dev\"],\r\n \"osx\": {\r\n \"program\": \"${workspaceFolder}/node_modules/.bin/nuxt-ts\"\r\n },\r\n \"linux\": {\r\n \"program\": \"${workspaceFolder}/node_modules/.bin/nuxt-ts\"\r\n },\r\n \"windows\": {\r\n \"program\": \"${workspaceFolder}/node_modules/nuxt/bin/nuxt.js\"\r\n }\r\n }\r\n ],\r\n \"compounds\": [\r\n {\r\n \"name\": \"fullstack: nuxt\",\r\n \"configurations\": [\"server: nuxt\", \"client: chrome\"]\r\n }\r\n ]\r\n}\r\n```\r\n\r\n\r\nAnd this is my debugging console on the server side:\r\n```\r\nC:\\Program Files\\nodejs\\node.exe .\\node_modules\\nuxt\\bin\\nuxt.js dev\r\nCould not read source map for file:///d:/Documents/Web%20Portfolio/2.CMS%20Blog/cms-blog/node_modules/vue-template-es2015-compiler/buble.js: ENOENT: no such file or directory, open 'd:\\Documents\\Web Portfolio\\2.CMS Blog\\cms-blog\\node_modules\\vue-template-es2015-compiler\\buble-browser-deps.umd.js.map'\r\nCould not read source map for file:///d:/Documents/Web%20Portfolio/2.CMS%20Blog/cms-blog/node_modules/postcss-nesting/index.cjs.js: ENOENT: no such file or directory, open 'd:\\Documents\\Web Portfolio\\2.CMS Blog\\cms-blog\\node_modules\\postcss-nesting\\index.cjs.js.map'\r\n2\r\nCould not read source map for file:///d:/Documents/Web%20Portfolio/2.CMS%20Blog/cms-blog/node_modules/typescript/lib/typescript.js: ENOENT: no such file or directory, open 'd:\\Documents\\Web Portfolio\\2.CMS Blog\\cms-blog\\node_modules\\typescript\\lib\\typescript.js.map'\r\nCould not read source map for file:///d:/Documents/Web%20Portfolio/2.CMS%20Blog/cms-blog/node_modules/ts-loader/dist/index.js: ENOENT: no such file or directory, open 'd:\\Documents\\Web Portfolio\\2.CMS Blog\\cms-blog\\node_modules\\ts-loader\\dist\\index.js.map'\r\nCould not read source map for file:///d:/Documents/Web%20Portfolio/2.CMS%20Blog/cms-blog/node_modules/ts-loader/dist/constants.js: ENOENT: no such file or directory, open 'd:\\Documents\\Web Portfolio\\2.CMS Blog\\cms-blog\\node_modules\\ts-loader\\dist\\constants.js.map'\r\nCould not read source map for file:///d:/Documents/Web%20Portfolio/2.CMS%20Blog/cms-blog/node_modules/ts-loader/dist/instances.js: ENOENT: no such file or directory, open 'd:\\Documents\\Web Portfolio\\2.CMS Blog\\cms-blog\\node_modules\\ts-loader\\dist\\instances.js.map'\r\nCould not read source map for file:///d:/Documents/Web%20Portfolio/2.CMS%20Blog/cms-blog/node_modules/ts-loader/dist/after-compile.js: ENOENT: no such file or directory, open 'd:\\Documents\\Web Portfolio\\2.CMS Blog\\cms-blog\\node_modules\\ts-loader\\dist\\after-compile.js.map'\r\nCould not read source map for file:///d:/Documents/Web%20Portfolio/2.CMS%20Blog/cms-blog/node_modules/ts-loader/dist/utils.js: ENOENT: no such file or directory, open 'd:\\Documents\\Web Portfolio\\2.CMS Blog\\cms-blog\\node_modules\\ts-loader\\dist\\utils.js.map'\r\n```\r\n\r\nMy tsconfig.json\r\n```\r\n{\r\n \"compilerOptions\": {\r\n \"target\": \"ES2018\",\r\n \"module\": \"ESNext\",\r\n \"moduleResolution\": \"Node\",\r\n \"lib\": [\"ESNext\", \"ESNext.AsyncIterable\", \"DOM\"],\r\n \"esModuleInterop\": true,\r\n \"jsx\": \"preserve\",\r\n \"noEmitOnError\": true,\r\n \"allowJs\": true,\r\n \"sourceMap\": true,\r\n \"strict\": true,\r\n \"noEmit\": true,\r\n \"experimentalDecorators\": true,\r\n \"baseUrl\": \".\",\r\n \"paths\": {\r\n \"~/*\": [\"./*\"],\r\n \"@/*\": [\"./*\"]\r\n },\r\n \"types\": [\r\n \"@nuxt/types\",\r\n \"@nuxtjs/axios\",\r\n \"@types/node\",\r\n \"@nuxt/content\",\r\n \"@nuxt/vue-app\",\r\n \"@nuxtjs/vuetify\"\r\n ]\r\n },\r\n \"exclude\": [\"node_modules\", \".nuxt\", \"dist\"]\r\n}\r\n```\r\n\r\nAnd my nuxt.config.js:\r\n```\r\nexport const config = {\r\n // Target: https://go.nuxtjs.dev/config-target\r\n target: \"static\",\r\n\r\n // Global page headers: https://go.nuxtjs.dev/config-head\r\n head: {\r\n titleTemplate: \"%s - cms-blog\",\r\n title: \"cms-blog\",\r\n meta: [\r\n { charset: \"utf-8\" },\r\n { name: \"viewport\", content: \"width=device-width, initial-scale=1\" },\r\n { hid: \"description\", name: \"description\", content: \"\" }\r\n ],\r\n link: [{ rel: \"icon\", type: \"image/x-icon\", href: \"/favicon.ico\" }]\r\n },\r\n\r\n // Global CSS: https://go.nuxtjs.dev/config-css\r\n css: [],\r\n\r\n // Plugins to run before rendering page: https://go.nuxtjs.dev/config-plugins\r\n plugins: [],\r\n\r\n // Auto import components: https://go.nuxtjs.dev/config-components\r\n components: true,\r\n\r\n // Modules for dev and build (recommended): https://go.nuxtjs.dev/config-modules\r\n buildModules: [\r\n // https://go.nuxtjs.dev/typescript\r\n \"@nuxt/typescript-build\",\r\n // https://go.nuxtjs.dev/vuetify\r\n \"@nuxtjs/vuetify\",\r\n \"@nuxtjs/fontawesome\",\r\n \"nuxt-typed-vuex\"\r\n ],\r\n\r\n // Modules: https://go.nuxtjs.dev/config-modules\r\n modules: [\r\n // https://go.nuxtjs.dev/axios\r\n \"@nuxtjs/axios\",\r\n // https://go.nuxtjs.dev/pwa\r\n \"@nuxtjs/pwa\",\r\n \"@nuxt/content\",\r\n \"@nuxtjs/google-fonts\"\r\n ],\r\n\r\n // Axios module configuration: https://go.nuxtjs.dev/config-axios\r\n axios: {},\r\n\r\n // PWA module configuration: https://go.nuxtjs.dev/pwa\r\n pwa: {\r\n manifest: {\r\n lang: \"en\"\r\n }\r\n },\r\n\r\n //Font awesome config\r\n fontawesome: {\r\n component: \"Fa\",\r\n suffix: true,\r\n icons: {\r\n solid: [\"faSearch\"]\r\n }\r\n },\r\n\r\n // Vuetify module configuration: https://go.nuxtjs.dev/config-vuetify\r\n vuetify: {\r\n customVariables: [\"~/assets/variables.scss\"],\r\n theme: {\r\n dark: true,\r\n default: false,\r\n disable: false,\r\n options: {},\r\n themes: {\r\n dark: {\r\n primary: colors.blue.darken2,\r\n accent: colors.grey.darken3,\r\n secondary: colors.amber.darken3,\r\n info: colors.teal.lighten1,\r\n warning: colors.amber.base,\r\n error: colors.deepOrange.accent4,\r\n success: colors.green.accent3\r\n },\r\n light: {\r\n primary: colors.blue.lighten2,\r\n accent: colors.grey.lighten3,\r\n secondary: colors.amber.lighten3,\r\n info: colors.teal.darken1,\r\n warning: colors.amber.base,\r\n error: colors.deepOrange.accent4,\r\n success: colors.green.accent3\r\n }\r\n }\r\n }\r\n },\r\n\r\n //Dev configuration\r\n server: {\r\n port: 4000\r\n },\r\n\r\n // Build Configuration: https://go.nuxtjs.dev/config-build\r\n build: {\r\n cssSourceMap: true,\r\n\r\n extend(config, { isDev, isClient }) {\r\n if (isDev) {\r\n config.devtool = \"source-map\";\r\n }\r\n }\r\n },\r\n\r\n //env\r\n publicRuntimeConfig: {\r\n mode: process.env.NODE_ENV\r\n }\r\n}\r\n```", "title": null, "type": "comment" }, { "action": "created", "author": "fabis94", "comment_id": 876204549, "datetime": 1625729625000, "masked_author": "username_1", "text": "I don't see why you wouldn't be able to reproduce this with the latest version, the issue would only disappear with some serious architectural changes. The resolution here, in my opinion, is to just write some useful guidelines/docs on how to debug server-side code.", "title": null, "type": "comment" }, { "action": "created", "author": "imuradevelopment", "comment_id": 914351193, "datetime": 1631024690000, "masked_author": "username_3", "text": "After all, what do I need to do to set a \"breakpoint\" for the SSR code in \"VScode\" and debug the NuxtApp rendered in \"chrome\"?\r\nNuxt is great, but if debugging is unstable...", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "MrRiky54", "comment_id": null, "datetime": 1612913200000, "masked_author": "username_0", "text": "In [`7e6fef6`](https://github.com/username_0/upptime/commit/7e6fef692dcc56253a0233195c86d78eb065efff\n), Mail ($HELIOHOST) was **down**:\n- HTTP code: 0\n- Response time: 0 ms", "title": "🛑 Mail is down", "type": "issue" }, { "action": "created", "author": "MrRiky54", "comment_id": 776320714, "datetime": 1612914127000, "masked_author": "username_0", "text": "**Resolved:** Mail is back up in [`0e052e5`](https://github.com/username_0/upptime/commit/0e052e592559c9079888e4918ad262767cde5eb5\n).", "title": null, "type": "comment" }, { "action": "closed", "author": "MrRiky54", "comment_id": null, "datetime": 1612914128000, "masked_author": "username_0", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "pys078", "comment_id": null, "datetime": 1621651452000, "masked_author": "username_0", "text": "**Describe the bug**\r\nA clear and concise description of what the bug is.\r\n清楚简明地描述了该错误是什么。\r\n\r\n**Error information (Help->Toggle Developer Tools->Console)**\r\nPaste or screenshot the content in `Help->Toggle Developer Tools->Console`\r\n粘贴或截屏`帮助->切换开发者工具->控制台`中的内容\r\n\r\n- Linux/MacOS: `~/.cloudmusic/err.log`\r\n- Windows: `%homepath%/.cloudmusic/err.log`\r\n\r\n**Environment (Help->About)**\r\nPaste the content in `Help->About`\r\n粘贴`帮助->关于`中的内容\r\n通过vsix文件安装，在code-server上帐号栏处一直处于加载无法添加账户", "title": "code-server上无法使用", "type": "issue" } ]

[ { "action": "opened", "author": "u1735067", "comment_id": null, "datetime": 1623677891000, "masked_author": "username_0", "text": "<!--\r\n NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED.\r\n\r\n This form is only for reporting reproducible bugs. If you need assistance\r\n with Nautobot installation, or if you have a general question, please start a\r\n discussion instead: https://github.com/nautobot/nautobot/discussions\r\n\r\n Please describe the environment in which you are running Nautobot. Be sure\r\n that you are running an unmodified instance of the latest stable release\r\n before submitting a bug report, and that any plugins have been disabled.\r\n-->\r\n### Environment\r\n* Python version: 3.6\r\n* Nautobot version: 1.0.2\r\n\r\n<!--\r\n Describe in detail the exact steps that someone else can take to reproduce\r\n this bug using the current stable release of Nautobot. Begin with the\r\n creation of any necessary database objects and call out every operation\r\n being performed explicitly. If reporting a bug in the REST API, be sure to\r\n reconstruct the raw HTTP request(s) being made: Don't rely on a client\r\n library such as pynautobot.\r\n-->\r\n### Steps to Reproduce\r\n1. Create Git repo with /export_templates/ipam/vlan/html_export.html export template\r\n2. Add Git repo in Nautobot\r\n3. Launch (or relaunch) sync\r\n\r\n<!-- What did you expect to happen? -->\r\n### Expected Behavior\r\nTemplate is imported and kept\r\n\r\n<!-- What happened instead? -->\r\n### Observed Behavior\r\nTemplate is imported and then immediately removed, in log we can observe: \r\n```\r\nworker_1 | 11:52:36.095 INFO nautobot.datasources.git :\r\nworker_1 | Loading `ipam.vlan` export template from `text_export.html`\r\nworker_1 | 11:52:36.179 INFO nautobot.datasources.git :\r\nworker_1 | Successfully created export template\r\nworker_1 | 11:52:36.190 WARNING nautobot.datasources.git :\r\nworker_1 | Deleted export template [GitLab] ipam | VLAN: text_export.html\r\n```\r\n\r\nThis seems to be caused by https://github.com/nautobot/nautobot/blob/v1.0.2/nautobot/extras/datasources/git.py#L694, where `template_record.content_type.name` (=`VLAN`) is used instead of `template_record.content_type.model` (=`vlan`), may I submit a PR with this change?", "title": "Git imported template immediately removed during import", "type": "issue" }, { "action": "created", "author": "glennmatthews", "comment_id": 860699446, "datetime": 1623678515000, "masked_author": "username_1", "text": "Thank you for the report and for the analysis! I agree with your analysis; please do feel free to submit a PR that fixes this and adds an appropriate unit test covering this issue.", "title": null, "type": "comment" }, { "action": "created", "author": "u1735067", "comment_id": 860871661, "datetime": 1623692787000, "masked_author": "username_0", "text": "While I have a PR ready for the fix, I don't have the tests parts and cannot work on it until maybe wednesday because of workstation lacking ressources for another dev environment, so I'll then look into it, if you haven't already completed it by this time.", "title": null, "type": "comment" }, { "action": "closed", "author": "glennmatthews", "comment_id": null, "datetime": 1624296418000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "jakebolewski", "comment_id": null, "datetime": 1611691571000, "masked_author": "username_0", "text": "### Description\r\n\r\nRunning the tests with a custom system image has been disabled due to Julia runtime bugs in 1.5.2 and 1.5.3. Re-enable testing with custom system image when Julia 1.5.4 is released https://github.com/JuliaLang/julia/pull/39351", "title": "Re-enable Sysimg CI build when Julia v1.5.4 is released.", "type": "issue" }, { "action": "created", "author": "jakebolewski", "comment_id": 768423927, "datetime": 1611766573000, "masked_author": "username_0", "text": "In addition we need to undo: https://github.com/CliMA/ClimateMachine.jl/pull/1958/commits/5fa0b830fe47cebb5cfc40e0efd82e70fa1c1d94", "title": null, "type": "comment" } ]

{ "number": 11, "repo": "awesome-job-boards", "user_login": "emredurukn" }

[ { "action": "opened", "author": "sewinter", "comment_id": null, "datetime": 1605937903000, "masked_author": "username_0", "text": "Carrots is a hiring platform specifically for software engineers. Engineers can connect their GitHub, Stack Overflow, LinkedIn, and more to showcase much more than their resumes. Its proprietary algorithm ranks world-class talent and surfaces their profiles to top companies.", "title": "Add Carrots to Programming Job Boards", "type": "issue" }, { "action": "created", "author": "emredurukn", "comment_id": 731556335, "datetime": 1605952437000, "masked_author": "username_1", "text": "Thanks", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "chandras-xl", "comment_id": null, "datetime": 1599569373000, "masked_author": "username_0", "text": "<!-- Thanks for filing an issue! Before hitting the button, please answer these questions. It's helpful to search the existing GitHub issues first. It's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of \r\n\r\nFill in as much of the template below as you can. If you leave out information, we can't help you as well.\r\n\r\nBe ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why.\r\n-->\r\n\r\n**Describe the bug**\r\n I want to create DB schemas when the patroni containers start. Currently am doing it manually by exec into the pod, I want to automate that and it should create when the container starts. How exactly can we do that, Is it possible to create the DB schema upfront? if yes, what all the files that I need to change?\r\n\r\n**Version of Helm and Kubernetes**: \r\nhelm version\r\nv3.2.4\r\n\r\nKubernetes version:\r\nv1.18.6\r\n\r\n**Which chart**: incubator/patroni\r\n\r\n\r\n**What happened**: I need to create the DB schemas manually after the patroni container starts by exec into the pod\r\n\r\n\r\n**What you expected to happen**: How to create the DB schema automatically during the container startup\r\n\r\n\r\n**How to reproduce it** (as minimally and precisely as possible):\r\n\r\n\r\n**Anything else we need to know**:", "title": "[charts/incubator/patroni/]: How to create db schema during the patroni container startup", "type": "issue" } ]

[ { "action": "opened", "author": "jaclyn-taroni", "comment_id": null, "datetime": 1615733530000, "masked_author": "username_0", "text": "With #394, the intro to R/Tidyverse module has all of the current file names. `module_structure_detail.png` is outdated. This image is used in the template repository file [virtual-workshop/workshop-materials.md](https://github.com/AlexsLemonade/training-specific-template/blob/master/virtual-workshop/workshop-materials.md) and as such, is used in `workshop/workshop-materials.md`. \r\n\r\nWhen we update that PNG file, we should also update the main README of this repository to use that image _instead_ of [`structure_course.png`](https://github.com/AlexsLemonade/training-modules/blob/master/structure_course.png), which should also be removed because it is out of date.", "title": "Update module_structure_detail.png to reflect the new exercise notebook naming convention", "type": "issue" }, { "action": "closed", "author": "cbethell", "comment_id": null, "datetime": 1615896701000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

{ "number": 5628, "repo": "cbmc", "user_login": "diffblue" }

[ { "action": "opened", "author": "tautschnig", "comment_id": null, "datetime": 1606081375000, "masked_author": "username_0", "text": "Apple decided to deviate from aarch64 configurations used by other\r\nUnix-like operating systems as documented at\r\nhttps://developer.apple.com/documentation/xcode/writing_arm64_code_for_apple_platforms#//apple_ref/doc/uid/TP40013702-SW1.\r\n\r\nFixes: #5627\r\n\r\n<!---\r\nThank you for your contribution. Please make sure your pull request fulfils all of the below requirements. If you cannot currently tick all the boxes, but would still like to create a PR, then add the label \"work in progress\" and assign the PR to yourself.\r\n--->\r\n\r\n- [x] Each commit message has a non-empty body, explaining why the change was made.\r\n- n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.\r\n- n/a The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/\r\n- [ ] Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).\r\n- n/a My commit message includes data points confirming performance improvements (if claimed).\r\n- [x] My PR is restricted to a single feature or bugfix.\r\n- n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.\r\n\r\n<!---\r\nSee, e.g., https://chris.beams.io/posts/git-commit/ for general guidelines on commit messages.\r\n\r\nIf you have created commits mixing multiple features and/or unrelated white-space changes, use a sequence involving git reset and git add -p to fix this.\r\n--->", "title": "Fix MacOS ARM platform configuration", "type": "issue" } ]

{ "number": 19, "repo": "ratio-spoof", "user_login": "ap-pauloafonso" }

[ { "action": "opened", "author": "ap-pauloafonso", "comment_id": null, "datetime": 1616105008000, "masked_author": "username_0", "text": "My take on @jhuggart idea of removing the channel \r\n- removal of ioutill calls (go 1.16)\r\n- callback instead of channel to update the estimated time to announce\r\n\r\n\r\nThe other way would be as you said to move the estimated-time to the tracker.go, but i feel like all the state management should be located on ratiospoof.go, and let the tracker.go do as little as possible, what do you think?", "title": "callback instead of channel", "type": "issue" }, { "action": "created", "author": "ap-pauloafonso", "comment_id": 803156755, "datetime": 1616191000000, "masked_author": "username_0", "text": "will merge #20 instead", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "rrhyne", "comment_id": null, "datetime": 1619639580000, "masked_author": "username_0", "text": "Search bar has been modified for the redesign. \r\n\r\nNote that at XS sizes, slightly different behavior occurs. \r\n\r\n\r\n# Figma\r\nhttps://www.figma.com/file/NIsN34NH7lPu04olBzddTw/Design-Refresh-Systemization-source-of-truth?node-id=1285%3A25746", "title": "Search bar design", "type": "issue" }, { "action": "created", "author": "limitedmage", "comment_id": 833097746, "datetime": 1620254794000, "masked_author": "username_1", "text": "I'll initially only implement the full-size design and will do the responsive design as part of https://github.com/sourcegraph/sourcegraph/issues/20685", "title": null, "type": "comment" }, { "action": "closed", "author": "limitedmage", "comment_id": null, "datetime": 1620258086000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" }, { "action": "reopened", "author": "umpox", "comment_id": null, "datetime": 1620636562000, "masked_author": "username_2", "text": "Search bar has been modified for the redesign. \r\n\r\nNote that at XS sizes, slightly different behavior occurs. \r\n\r\n\r\n# Figma\r\nhttps://www.figma.com/file/NIsN34NH7lPu04olBzddTw/Design-Refresh-Systemization-source-of-truth?node-id=1285%3A25746", "title": "Search input design", "type": "issue" }, { "action": "created", "author": "umpox", "comment_id": 836397957, "datetime": 1620636562000, "masked_author": "username_2", "text": "Reopening for implementation review, @sourcegraph/design please review, raise any changes as new tickets and close this issue!", "title": null, "type": "comment" }, { "action": "created", "author": "rrhyne", "comment_id": 837005333, "datetime": 1620667568000, "masked_author": "username_0", "text": "I'll leave this one open, pending:\r\n\r\nhttps://github.com/sourcegraph/sourcegraph/issues/20685", "title": null, "type": "comment" }, { "action": "created", "author": "limitedmage", "comment_id": 849936647, "datetime": 1622149056000, "masked_author": "username_1", "text": "@username_0 @AlicjaSuska work on the redesigned search box has been completed, including QA items. Can this issue be closed?", "title": null, "type": "comment" }, { "action": "created", "author": "rrhyne", "comment_id": 849993475, "datetime": 1622156032000, "masked_author": "username_0", "text": "Yes, thanks!", "title": null, "type": "comment" }, { "action": "closed", "author": "rrhyne", "comment_id": null, "datetime": 1622156032000, "masked_author": "username_0", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "artinalbert", "comment_id": null, "datetime": 1606320044000, "masked_author": "username_0", "text": "Unshaky despite still lunching automatically on Big Sur doesn't prevent any double or triple taps on any keys.", "title": "Is there going to be a version that works on Mac OS Big Sur?", "type": "issue" }, { "action": "created", "author": "aahung", "comment_id": 733888445, "datetime": 1606330058000, "masked_author": "username_1", "text": "I tested on big sur in #168, if Unshaky does not work, can you check this workaround? https://github.com/username_1/Unshaky/issues/166", "title": null, "type": "comment" }, { "action": "closed", "author": "aahung", "comment_id": null, "datetime": 1606987660000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]

[ { "action": "opened", "author": "DAmNRelentless", "comment_id": null, "datetime": 1625937620000, "masked_author": "username_0", "text": "Before formatting my file looks like this:\r\n\r\n\r\nAfter formatting, it looks like this:\r\n\r\n\r\nLooks like the formatting is moving the comment behind the previous key when there are multiple comment lines.\r\nThis is a problem since both lines describe the next key in the TOML.\r\nIt would be nice to have an option to keep multi-comments.\r\n\r\nExtension Version: 0.13.1\r\n\r\nVSCode\r\nVersion: 1.58.0 (user setup)\r\nCommit: 2d23c42a936db1c7b3b06f918cde29561cc47cd6\r\nDate: 2021-07-08T06:54:55.083Z\r\nElectron: 12.0.13\r\nChrome: 89.0.4389.128\r\nNode.js: 14.16.0\r\nV8: 8.9.255.25-electron.0\r\nOS: Windows_NT x64 10.0.19042", "title": "Option to keep multiple comments", "type": "issue" }, { "action": "created", "author": "tamasfe", "comment_id": 877673363, "datetime": 1625938199000, "masked_author": "username_1", "text": "Yes, it's definitiely a bug in the new formatter, sorry.\r\n\r\nCan you please provide code blocks instead of screenshots? Would help a lot with just copy/pasting the expected behaviour in a test.", "title": null, "type": "comment" }, { "action": "created", "author": "DAmNRelentless", "comment_id": 877673609, "datetime": 1625938301000, "masked_author": "username_0", "text": "sure thing, this is enough to reproduce it\r\n```toml\r\n#General settings\r\n[general]\r\n\t#Is Enabled?\r\n\tenabled = true\r\n\t#Cost\r\n\t#Range: > -2147483648\r\n\tcost = 10\r\n\t#Is Starter Glyph?\r\n\tstarter = false\r\n\t#The maximum number of times this glyph may appear in a single spell\r\n\t#Range: > 1\r\n\tper_spell_limit = 2147483647\r\n```", "title": null, "type": "comment" }, { "action": "created", "author": "tamasfe", "comment_id": 877675713, "datetime": 1625939079000, "masked_author": "username_1", "text": "Thanks!\r\n\r\nShould be fixed in 2d87495d3e04a79adb1cc9346db8d63c640a7509, I'll promptly push a new release with it.", "title": null, "type": "comment" }, { "action": "closed", "author": "tamasfe", "comment_id": null, "datetime": 1625939080000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" }, { "action": "created", "author": "DAmNRelentless", "comment_id": 877676726, "datetime": 1625939445000, "masked_author": "username_0", "text": "Thanks for the fast response and the fast work! :)", "title": null, "type": "comment" } ]

[ { "action": "opened", "author": "dream-is-g-aay", "comment_id": null, "datetime": 1615190118000, "masked_author": "username_0", "text": "lol", "title": "3111", "type": "issue" }, { "action": "closed", "author": "samcoe", "comment_id": null, "datetime": 1616171583000, "masked_author": "username_1", "text": "", "title": null, "type": "issue" } ]