text:
localhost installation

Hello,
I Am trying to install it on my local machine on apache server, see below
<Directory /var/www/laravel/goodwork/public/>
Options Indexes FollowSymLinks
AllowOverride All
Require all granted

But I get the below error

I see the uri is project.conf, there is no route like that in the app, might wanna check out what url you actually trying to reach.

I managed to fix it but now, as an Admin, I can't create a project  nor create a team, It gives me the below error...

@m2ura did you run the seeder, if not please run php  artisan db:seed

I ran php artisan migrate --seed, but still the same issue.

can you check the permission_settings table is there any records in the table

@Hasnayeen I took a sceen shot of it

can you also post the role_has_permission table screenshot?

no problem there, can you check the laravel log file for any error.

This is what I had on logs, then I remigrated and seeded
[2019-06-26 15:54:14] local.ERROR: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'admin' for key 'users_username_unique' (SQL: insert into users (name, username, email, active, password, created_at, updated_at) values (Admin, admin, admin@example.com, 1, $2y$10$5bm5fiR5xYM02FVT7MU4z.GHRS5Q4eIlBXhcL2H98mnZDSHD7pcu6, 2019-06-26 15:54:13, 2019-06-26 15:54:13)) {"exception":"[object] (Illuminate\Database\QueryException(code: 23000): SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'admin' for key 'users_username_unique' (SQL: insert into users (name, username, email, active, password, created_at, updated_at) values (Admin, admin, admin@example.com, 1, $2y$10$5bm5fiR5xYM02FVT7MU4z.GHRS5Q4eIlBXhcL2H98mnZDSHD7pcu6, 2019-06-26 15:54:13, 2019-06-26 15:54:13)) at /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Connection.php:664, Doctrine\DBAL\Driver\PDOException(code: 23000): SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'admin' for key 'users_username_unique' at /var/www/laravel/goodwork/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:119, PDOException(code: 23000): SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'admin' for key 'users_username_unique' at /var/www/laravel/goodwork/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:117)
[stacktrace]
#0 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Connection.php(624): Illuminate\Database\Connection->runQueryCallback('insert into us...', Array, Object(Closure)) #1 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Connection.php(459): Illuminate\\Database\\Connection->run('insert into us...', Array, Object(Closure))
#2 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Connection.php(411): Illuminate\Database\Connection->statement('insert into us...', Array) #3 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Query/Processors/Processor.php(32): Illuminate\\Database\\Connection->insert('insert into us...', Array)
#4 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(2628): Illuminate\Database\Query\Processors\Processor->processInsertGetId(Object(Illuminate\Database\Query\Builder), 'insert into `us...', Array, 'id')
#5 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(1338): Illuminate\Database\Query\Builder->insertGetId(Array, 'id')
#6 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(823): Illuminate\Database\Eloquent\Builder->__call('insertGetId', Array)
#7 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(788): Illuminate\Database\Eloquent\Model->insertAndSetId(Object(Illuminate\Database\Eloquent\Builder), Array)
#8 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(651): Illuminate\Database\Eloquent\Model->performInsert(Object(Illuminate\Database\Eloquent\Builder))
#9 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(793): Illuminate\Database\Eloquent\Model->save()
#10 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Support/helpers.php(1027): Illuminate\Database\Eloquent\Builder->Illuminate\Database\Eloquent\{closure}(Object(App\Core\Models\User))
#11 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(794): tap(Object(App\Core\Models\User), Object(Closure))
#12 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Support/Traits/ForwardsCalls.php(23): Illuminate\Database\Eloquent\Builder->create(Array)
#13 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1608): Illuminate\Database\Eloquent\Model->forwardCallTo(Object(Illuminate\Database\Eloquent\Builder), 'create', Array)
#14 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1620): Illuminate\Database\Eloquent\Model->__call('create', Array)
#15 /var/www/laravel/goodwork/database/seeds/AdminUserSeeder.php(23): Illuminate\Database\Eloquent\Model::__callStatic('create', Array)
#16 [internal function]: AdminUserSeeder->run()
#17 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(29): call_user_func_array(Array, Array)
#18 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(87): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#19 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(31): Illuminate\Container\BoundMethod::callBoundMethod(Object(Illuminate\Foundation\Application), Array, Object(Closure))
#20 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/Container.php(572): Illuminate\Container\BoundMethod::call(Object(Illuminate\Foundation\Application), Array, Array, NULL)
#21 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Seeder.php(122): Illuminate\Container\Container->call(Array)
#22 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Seeder.php(42): Illuminate\Database\Seeder->__invoke()
#23 /var/www/laravel/goodwork/database/seeds/DatabaseSeeder.php(16): Illuminate\Database\Seeder->call('AdminUserSeeder')
#24 [internal function]: DatabaseSeeder->run()
#25 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(29): call_user_func_array(Array, Array)
#26 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(87): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#27 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(31): Illuminate\Container\BoundMethod::callBoundMethod(Object(Illuminate\Foundation\Application), Array, Object(Closure))
#28 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/Container.php(572): Illuminate\Container\BoundMethod::call(Object(Illuminate\Foundation\Application), Array, Array, NULL)
#29 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Seeder.php(122): Illuminate\Container\Container->call(Array)
#30 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Console/Seeds/SeedCommand.php(63): Illuminate\Database\Seeder->__invoke()
#31 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/GuardsAttributes.php(122): Illuminate\Database\Console\Seeds\SeedCommand->Illuminate\Database\Console\Seeds\{closure}()
#32 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Database/Console/Seeds/SeedCommand.php(64): Illuminate\Database\Eloquent\Model::unguarded(Object(Closure))
#33 [internal function]: Illuminate\Database\Console\Seeds\SeedCommand->handle()
#34 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(29): call_user_func_array(Array, Array)
#35 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(87): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#36 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(31): Illuminate\Container\BoundMethod::callBoundMethod(Object(Illuminate\Foundation\Application), Array, Object(Closure))
#37 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Container/Container.php(572): Illuminate\Container\BoundMethod::call(Object(Illuminate\Foundation\Application), Array, Array, NULL)
#38 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Console/Command.php(183): Illuminate\Container\Container->call(Array)
#39 /var/www/laravel/goodwork/vendor/symfony/console/Command/Command.php(255): Illuminate\Console\Command->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Illuminate\Console\OutputStyle))
#40 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Console/Command.php(170): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Illuminate\Console\OutputStyle))
#41 /var/www/laravel/goodwork/vendor/symfony/console/Application.php(901): Illuminate\Console\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#42 /var/www/laravel/goodwork/vendor/symfony/console/Application.php(262): Symfony\Component\Console\Application->doRunCommand(Object(Illuminate\Database\Console\Seeds\SeedCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#43 /var/www/laravel/goodwork/vendor/symfony/console/Application.php(145): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#44 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Console/Application.php(89): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#45 /var/www/laravel/goodwork/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(122): Illuminate\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#46 /var/www/laravel/goodwork/artisan(35): Illuminate\Foundation\Console\Kernel->handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#47 {main}
"}

can you visit the admin page?

This is when I Add new project as Admin

And Headers

can you visit the /admin page? click the profile avatar and in dropdown menu you'll see admin link? can you visit that?

I clicked then I got this

what's the role_id of admin user in users table and post the roles table screeenshot

Okay, it seems like users table is missing, there is team_user, office_user, and project_user table.

how can you login without a users table, you wouldn't be able to login if there is no users table. check again

These are the only tables that wer migrated, not sure how I login without users table.

run php artisan migrate:fresh --seed

Done... Role id...

role_id should be 1

Thank you very much my guy, you have helped me :dancing_men:

which version are you using? that looks outdated. make sure to pull latest commits from master branch

current admin page looks like this

repo: iluminar/goodwork


text:
Add GameViewModel

Необходимо реализовать вьюмодель, где будет реализована логика процеса игры.

#25 я добавила вьюмодель

source: gharchive/issue

authors: ilyapaddubny mabolotska

license: MIT

license_type: permissive

license_source: github-api


text:
Create convolution function handling returning an array

Modify the convolution functions so that the code handling the data is moved to its own function. The goal is to have a function that takes in an image's data and that returns a data array as well. This allows not to round the values of the data every time convolution is used.
function rawDirectConvolution(data: ImageDataArray, options: ConvolutionOptions): Float64[];

Done in baff97d9791907240955f512e7633a39ffc12f48.

repo: image-js/image-js-typescript


text:
Implement Montage

feat: implement getCrosscheckMatches
fix: optimise crosscheck using pointers
test: start crosscheck test
fix: debug sortBySourceDest
test: fix getCrosscheckMatches test
refactor: rename draw to visualize
fix: add origin option to drawKeypoint
feat: implement getBasicMontage
refactor: rename getScoreColors to getColors
feat: implement getMatchColor
feat: implement Montage class
fix(drawMatches): use Montage
test: fix coverage

TODO: document the class

Is this really ready for review ? I don't want to comment on outdated code.

source: gharchive/pull-request

authors: opatiny targos


text:
Make resizing actually resize to the given dimensions

By default, using gm to resize will resize to what it deems the best constraint proportionally sized image (unless you pass in "!" as the third argument for resize()). It should still resize the images, but with the size that was passed in. Not sure if this is a node-gm thing in itself, but I spent some time trying to figure it out and it seems the only way to fix it is to force a crop, or use the third param (which won't resize it proportionally).

.resize(preset.size.split('x')[0], preset.size.split('x')[1], '^') in lib/imager.js:343 would fix this behaviour

authors: LucidityDesign pruhstal

repo: imagerjs/imager

license: mit

license_source: bigquery


text:
adopt std::mutex

Now that we're at a minimum of C++11, we should re-evaluate

std::mutex or std::recursive_mutex ?
The code indicates that the recursivity is forbidden but I do see any good reason.
The comment is coming from one of my changes when I discovered that the behavior was different between the implementations (Windows implementation versus POSIX implementation). Using the new C++11 capability we should now think about the type of mutex.

Not having a good way to answer, use the most restrictive one i.e. std::mutex

authors: hodoulp scoopxyz

repo: imageworks/OpenColorIO


text:
菜单位置异常，bug较为严重

我尝试去在element tree组件上鼠标右键显示菜单，但是会造成如下结果，错误

不清楚这里为什么是max-height：69px固定了

另外，不知道为什么会显示轮播箭头，我并不需要它，我只能在全局css中设置它为display：none

我尝试在配置里对y的值进行修改，但是会存在未知的bug

vue版本：3.2.45
@imengyu/vue3-context-menu版本:   1.1.3
最后感谢开发者的贡献

你好，可否给一个最小的可复现demo，这样我好排查一下问题，非常感谢
不知道你是否在tree组件外层包裹了什么其他组件导致菜单计算最大高度不正常，可以尝试设置 adjustPosition: false 关闭自动调整大小功能。

我新建了一个项目试了一下，在 el-tree 的 node-contextmenu 事件中弹出菜单，代码是这样的
<el-tree :data="data" :props="defaultProps" @node-contextmenu="handleNodeContextmenu" />

const handleNodeContextmenu = (e) => {
  ContextMenu.showContextMenu({
    x: e.x,
    y: e.y,
    zIndex: 3000,
    items: [
      {
        label: "A menu item",
        onClick: () => {
          alert("You click a menu item");
        }
      },
      {
        label: "A submenu",
        children: [
          { label: "Item1" },
          { label: "Item2" },
          { label: "Item3" },
        ]
      },
    ]
  })
}

这是我实际测试的结果，在单独组件或者是 el-dialog 中的 el-tree 弹出，状态都是正常的。版本 element-plus 2.2.26、vue 3.2.45。

更新了 1.1.5 版本，估计可能是获取窗口高度的地方写错了，导致自动调整菜单高度出问题。试一下是否可以解决问题

更新到最新版本1.1.5，非常完美，没有出现以上bug了，感谢。

authors: imengyu kongbair


text:
chore(fp-ts): refactor createImgixFluidFieldConfig

This is part of the Gatsby fp-ts refactor.

Current dependencies on/for this PR:

main

PR #198

PR #188

PR #189

PR #191

PR #192

PR #193

PR #194

PR #195

repo: imgix/gatsby


text:
Support Last-Modified response header and support If-Modified-Since request header.

Support responding with the Last-Modified of the upstream image. This is a very useful header to determine if we are dealing with a new or old image. As we allow returning the upstream ETag, it makes sense to also return the upstream Last-Modified header.
Also support the If-Modified-Since request header to help manage caching. previously discussed in #348.

Add the IMGPROXY_USE_LAST_MODIFIED config, disabled by default. If-Modified-Since can't take config and processing options changes into account, so users may not want to use it. Thus we shouldn't use it by default.

Done.

@ehiggs I refactored ETag support in transports so it should be easier to add Last-Modified support: https://github.com/imgproxy/imgproxy/commit/49e5eb063c65721e62f9cae980b875e35dea6cb6

Could you add If-Modified-Since support to the rest of the transports?

Could you add If-Modified-Since support to the rest of the transports?

Sure. Are we ok with the fact that we format the time to a string in the GCS Object. Then we parse it again in the notmodified module to compare it with the parsed If-Not-Modified time. It seems wasteful to go back and forth between formats, but I don't want to go on refactoring adventures here.

Could you add If-Modified-Since support to the rest of the transports?

Should be done with tests now.
Note: gofakes3 doesn't support Last-Modified.

LGTM! I'll try to patch gofakes3 before merging this. Doesn't look like a big deal.

LGTM! I'll try to patch gofakes3 before merging this. Doesn't look like a big deal.

Do you have a link to your upstream ticket? Thanks!

I updated the master branch to use my fork of gofakes3. Could you uncomment the test?

Done!

Great job, Ewan! Thanks for your contribution!

authors: DarthSim ehiggs ehiggs-deliverect

repo: imgproxy/imgproxy


text:
AvifSpeed value checker

Hello,
As I understand valid values for AvifSpeed is 0-8, including 0 and 8. But the checker does not allow 0.
So here is fix

Thanks!

authors: AleksandrKrokis DarthSim


text:
Integrate LLVM at llvm/llvm-project@131dda9

Updates LLVM usage to match llvm/llvm-project@131dda9.
Further updates the MLIR-HLO submodule to tensorflow/mlir-hlo@3c6e1c8.

Had to address that clang-format failed...

Blocked by https://github.com/tensorflow/tensorflow/pull/57100.

I bumped the the mlir-hlo submodule to 817776b as in incorporates the fix.


text:
Bug |

Describe the bug
A clear and concise description of what the bug is.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

;

authors: imniladri niloysikdar

repo: imniladri/DevHub


text:
Add misclassification demo

Adding a new demo for misclassification tests using design validation apis.
Demo is currently talking to the backend apis and will be updated when the APIM endpoints are made available. I added a fallback to a hardcoded results dataset as well until the issues with the scopes for the auth token are sorted out.
Trying to get this in before the sprint review on Wednesday morning, so if this could be looked at ASAP that would be great. Thanks!

Looks good mostly just mechanical changes requested.

The thumbnail looks a little wider and shorter than the others. Can you try to take a more square screenshot?

The thumbnails should be the following sizes:
1x = 370x225 px
2x = 740x450 px

authors: Josh-Schifter lumiio

repo: imodeljs/frontend-sample-showcase


text:
Explain left and right labels

When creating a likert question, expain what the left and right labels are

Consider that #27 is being added. This may affect the design and layout of the new likert question component

repo: impactasaurus/app


text:
hexo博客的gitment评论开启一直失败

按照教程上配的，我的github pages绑定了个人域名
https//:hongbb.top
OAuth配置如下，应该是没有错误的

_config.yml的配置如下，保证client_id 和 client_secret没有填错
comment:
  gitment:
    enable: true
    owner: 'JJXiangJiaoJun' # 必填项, 你的GitHub ID
    repo: 'JJXiangJiaoJun.github.io' # 必填项  你的存储评论的repo
    oauth:
      client_id: 'd7df3d5d159f81371d76' # 必填项
      client_secret: '3794527fca067871d3795782ae7fd14f94ce3a74' # 必填项
      redirect_uri: # 可以填也可以不填

设置后博客上显示　Error: Comments Not Initialized
点击　登录　按钮后，无法跳转到github授权界面
浏览器上信息为 https://hongbb.top/?error=redirect_uri_mismatch&error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application.&error_uri=https%3A%2F%2Fdeveloper.github.com%2Fapps%2Fmanaging-oauth-apps%2Ftroubleshooting-authorization-request-errors%2F%23redirect-uri-mismatch
看起来好像是call-back url填错了,不过我试了 原来的ＵＲＬ也没用

同样的问题

我的也是，昨天弄的，github登陆之后浏览器显示：
[object XMLHttpRequestProgressEvent]，然后一直在转圈。。。loading commetns

可以看这里 https://sherry0429.github.io/2019/02/12/gitment修复/

可以看这里 https://sherry0429.github.io/2019/02/12/gitment修复/

你目前博客的gitment就会报object ProgressEven 不知道什么原因，我的icarus也是这种情况

我也遇到同样问题了 = =

解决了吗    我也是一样的问题哎     满脑子很糊涂

解决方案参考：https://adamhu.github.io/2019/06/GitHub-Pages个人博客搭建流程/

目前网上大部分解决方案都失效了，可以使用下面的方法解决：
打开你的blog本地仓库themes\next\layout_third-party\comments\gitment.ejs将
<link rel="stylesheet" href="https://imsun.github.io/gitment/style/default.css">
<script src="https://imsun.github.io/gitment/dist/gitment.browser.js"></script>

修改为：
<link rel="stylesheet" href="https://billts.site/extra_css/gitment.css">
<script src="https://billts.site/js/gitment.js"></script>

上面给出的是gitment汉化版

说一下本人的 解决办法 :
我的github pages绑定了个人域名
https//:hongbb.top  导致重定向一直错误，我只修改了_config.yml 中的 redirect_uri , 就解决了问题，现在使用正常
comment:
  gitment:
    enable: true
    owner: 'JJXiangJiaoJun' # 必填项, 你的GitHub ID
    repo: 'JJXiangJiaoJun.github.io' # 必填项  你的存储评论的repo
    oauth:
      client_id: 'd7df3d5d159f81371d76' # 必填项
      client_secret: '3794527fca067871d3795782ae7fd14f94ce3a74' # 必填项
      redirect_uri: https//:hongbb.top    #如果绑定了个人域名，这里一定要填上绑定的个人域名!!!!!!!!!!!!!

可以试试将redirect_uri 改成自己绑定的个人域名

按照楼上所说的方法,没搞定.换了一个评论系统,gittalk

关于不能初始化的问题，我在手机上解决了。这是什么情况？

说一下本人的 解决办法 :
我的github pages绑定了个人域名
https//:hongbb.top 导致重定向一直错误，我只修改了_config.yml 中的 redirect_uri , 就解决了问题，现在使用正常
comment:
  gitment:
    enable: true
    owner: 'JJXiangJiaoJun' # 必填项, 你的GitHub ID
    repo: 'JJXiangJiaoJun.github.io' # 必填项  你的存储评论的repo
    oauth:
      client_id: 'd7df3d5d159f81371d76' # 必填项
      client_secret: '3794527fca067871d3795782ae7fd14f94ce3a74' # 必填项
      redirect_uri: https//:hongbb.top    #如果绑定了个人域名，这里一定要填上绑定的个人域名!!!!!!!!!!!!!

可以试试将redirect_uri 改成自己绑定的个人域名

亲测无效

我迪纳基login后出现了下面的代码：
> <%- _partial('common/head') %> <%- _partial('common/navbar') %> <% function main_column_class() { switch (column_count()) { case 1: return 'is-12'; case 2: return 'is-8-tablet is-8-desktop is-8-widescreen'; case 3: return 'is-8-tablet is-8-desktop is-6-widescreen' } return ''; } %>
<%- body %>
<%- _partial('common/widget', { position: 'left' }) %> <%- _partial('common/widget', { position: 'right' }) %>
<%- _partial('common/footer') %> <%- _partial('common/scripts') %> <% if (has_config('search.type')) { %> <%- _partial('search/' + get_config('search.type')) %> <% } %>

有人解决这个问题吗，我的gitment也是一直开启不了

按照楼上所说的方法,gitment没搞定.换了一个评论系统,gittalk ,[https://yunhao.space/2018/07/04/hexo-next-gitalk-comments-tutor/这是教程地址..配置起来很简单](Car Gameshttps://yunhao.space/2018/07/04/hexo-next-gitalk-comments-tutor/这是教程地址..配置起来很简单)..

"Thanks, great blog!"

repo: imsun/gitment


text:
Any HTML properties are not reflected.

Describe the issue
https://github.com/imzbf/md-editor-v3/issues/257#issuecomment-1532835563

Similarly for classes and styles.
Procedure version
4.12.1
Reproduction link
No response

Disable XSS extensions or set supported properties
https://imzbf.github.io/md-editor-v3/en-US/demo#🔏 Modify XSS configuration

Oh, thanks!

authors: Gypsy-H-Takumi imzbf


text:
Use ObservationSound UUID

Currently we have an ObservationSound model in the app that basically corresponds to the Sound model on the web, and confusingly not with the ObservationSound model on the web. This is further complicated by the fact that at present the API does not return UUIDs for ObservationSound records or Sound records, making it impossible for us to delete individual sounds or even populate the local UUID attribute of the app's ObservationSound model.
So, pending the necessary API changes, I want to make these changes in the app to bring it in line with the web and reduce confusion in the future:

[ ] Model sounds the same way we model photos, i.e. ObservationSound should be a join model that has one Sound and its own UUID
[ ] When we upsert observations into the local database, stop minting a new UUID for ObservationSound records and use the value we get from the API for the ObservationSound (not the Sound)

Most of the heavy lifting happened in https://github.com/inaturalist/iNaturalistReactNative/pull/1416

repo: inaturalist/iNaturalistReactNative


text:
Skeleton UI and server results for adding a comment in ObsDetail

This handles skeleton UI and displaying a new comment posted and successfully returned from the server. The code is pretty similar to what we're already doing for adding an identification. A comment is shown at 50% opacity, with a loading wheel underneath, until the server returns results. The API call now returns the correct fields to be able to display a new comment in the ActivityTab.
I also cleaned up styling using Tailwind & removed some unnecessary code from the ObsDetails tests.

Fixed merge conflicts.


text:
remove the photo invite tool

It was never much more than a spam enabler, and I think it might be broken for Flickr.

@loarie apparently thinks it's worth keeping around for the ~1 person that uses it.

repo: inaturalist/inaturalist


text:
can't select text with keyboard in comments for safari

From @carrieseltzer:

Running OS X 10.10.4 and Safari Version 8.0.7 (10600.7.12)
2. Comments box doesn't show text selections/cursor movements well.
I noticed in the last couple of days that I can't interact with text as easily in comment boxes, especially using my usual keyboard shortcuts, like using shift+arrows to select text for copying or deleting. I realized accidentally that the shift+arrows IS selecting text, but the cursor and highlight isn't showing it. For example, if I use that keyboard shortcut and then hit delete, it will remove text even though I couldn't see what was highlighted. Text selection with the mouse is also less predictable. No idea what is causing this, but I've never noticed it before.

I can confirm this is happening but only in Safari, not in Firefox or Chrome. I haven't noticed any mouse issues. @pleary, timing seems to match up with the release of mentions, though functionally it seems like it could be related to my keyboard shortcut stuff. If you can think of any mentions-related explanations please holler, otherwise I'll take a look.

I can confirm this is a bug with the text highlighting lib we're using. You can replicate it on their demo page: http://mistic100.github.io/jquery-highlighttextarea/
@pleary, I don't think highlighting really adds much, that library is not maintained, and now there's the Safari issue. Should we drop it?

We can definitely drop it. It's a weird implementation that I suspect will just keep causing issues

authors: kueda pleary


text:
Support social sign-in buttons on mobile web view

When I receive an iNaturalist email and click on an image, it takes me to the mobile web view. I'd like to be able to log in easily from this view, but unlike the desktop view, it does not offer the social sign-in buttons (Facebook, Google, etc).

I also noticed I'm seeing a weird number at the top of the screen on the login page. It looks like it's coming from this commit: https://github.com/inaturalist/inaturalist/commit/b2ccfea8ec131cf1aa34e8c75369e905d1498770
I'm using Chrome on Android 5.1.1.

Count me in on the desired support for mobile social sign in!
—
Sent from Mailbox
On Tue, Dec 15, 2015 at 3:47 PM, Mike Dillon notifications@github.com
wrote:

I also noticed I'm seeing a weird number at the top of the screen on the login page. It looks like it's coming from this commit: https://github.com/inaturalist/inaturalist/commit/b2ccfea8ec131cf1aa34e8c75369e905d1498770
I'm using Chrome on Android 5.1.1.
Reply to this email directly or view it on GitHub:
https://github.com/inaturalist/inaturalist/issues/795#issuecomment-164891965

@carrieseltzer :+1:

The mobile web view is long gone, and social sign in is possible from the web sign in page (which is responsive), so I'm going to close this.


text:
Update Mediawiki version

The current Mediawiki version 1.17 is quite out of date. Need to update to the current version. The main challenge will be making sure the plugins and skin is compatible.

We took the first step towards this finally which was to switch to the default Vector theme. Now we can update the wiki without significantly changing the style.

We finished the upgrade a while ago!

repo: indieweb/wiki

license: unlicense


text:
[13.0.x]fix server readme link

Fix attribute for linking to server readme

Thanks @dvagnero

authors: dvagnero ryanemerson

repo: infinispan/infinispan


text:
ISPN-5803 Extract MarshalledValues in JCache

https://issues.jboss.org/browse/ISPN-5803

JCache cache store loader and writers should extract values from
marshalled values so that cache store/writer implementations can deal
with true types instead of wrapped ones.

Besides the minor comments, I'm wondering if we shouldn't do this for core loaders/writers as well. The CacheWriter interface already deals with MarshalledEntry, which has separate getKey() and getKeyBytes() methods (and the same for values/metadata), so couldn't we make MarshalledEntry.getKey() always strip the MarshalledValue wrapper?

@danberindei Not sure I understand your question...

Dan made a good point there, closing this PR to send a new one with a different fix.

authors: danberindei galderz


text:
ISPN-6239 InitialClusterSizeTest.testInitialClusterSizeFail random failures

Increases the timeout in InitialClusterSizeTest and fixes some issues in TEST_PING and JGroupsTransport.
https://issues.jboss.org/browse/ISPN-6239
https://issues.jboss.org/browse/ISPN-6390
https://issues.jboss.org/browse/ISPN-6391
Please cherry-pick to 8.2.x as well.

Only some minor things... otherwise looks ok to me.

Pulling

Pushed to master branch. 8.2.x needs a rebase. Would you open another PR just for that?

Integrated thanks!

authors: danberindei slaskawi


text:
ISPN-11961 DefaultIracManager should handle ImmutableSet

https://issues.redhat.com/browse/ISPN-11961

Thanks @pruivo

authors: pruivo ryanemerson


text:
🛑 Homepage is down

In f0aa934, Homepage (https://infinite8.co) was down:

HTTP code: 404
Response time: 202 ms

Resolved: Homepage is back up in 2287e77.


text:
JSONでの取得を試みると、Internal Server Errorとなる

環境：Raspberry pi3
OS：Raspbian Stretch Lite(Kernel 4.9、Release 2017-09-07)
ソフト：最新版(11/28版)ミドルウェア
題記の通りですが、オプション"json"を1にすると、Internal Server Errorが返ります。
例：Python3.5コンソールより

import requests
uri = "http://＜addr＞/ctrl/?color=100,80,0&mode=0&repeat=0&period=1000&json=1"
res = requests.get(uri)
print(res)

<Response [500]>  ←レスポンス

print(res.text)

'<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">\n\n<title>500 Internal Server Error</title>\n\n
Internal Server Error
\n
The server encountered an internal error or\nmisconfiguration and was unable to complete\nyour request.
\n
Please contact the server administrator at \n webmaster@localhost to inform them of the time this error occurred,\n and the actions you performed just before this error.
\n
More information about this error may be available\nin the server error log.
\n
\n<address>Apache/2.4.25 (Raspbian) Server at 192.168.88.17 Port 80</address>\n\n'

設定のuriは、UI上の「アラート実行コマンド」に表示されるコマンドの引き写しで、UI上ではレスポンスが正しく返っているようですが、ブラウザで上記コマンドを直接コピペしても、Internal Server Errorとなります。
　なお、点滅自体は指定の通りに動作しているように見えます。また、json=0の場合、レスポンスは200が返っています

報告をありがとうございます！
明日確認します。

問題が現在のクリシグミドルウエアを使用し、OSがjessieとstretch、どちらでも再現できました。調べ中。

修正しました。
https://github.com/infiniteloop-inc/crystal-signal/commit/57d760f970ddbdcaa9d6446a58a798b91308b1e1#diff-a42042e7b03d6429399523f47216c0ea
原因：
2017年6月に、controller.pyを整理し、JSONの場合、サーバ返事に"Content-type: text/html \n\n"が不要と間違って判断してしまいました。

修正が行われたことを確認しました(Stretch)。
迅速な対応をありがとうございます。

authors: T-Kuhn yuhkan

repo: infiniteloop-inc/crystal-signal


text:
upgrade to rn 0.49.2 fails

What's going on?
After a classic ignite new myapp I tried to upgrade from RN 0.47 to 0.49.2 using rect-native-git-upgrade. A lot of errors are revealed and the react-native run-ios fails.
Steps to reproduce
run rect-native-git-upgrade
ignite doctor results:

We'll be taking a look at this soon.

@valinaga - merged updates for everything, please take a look and give feedback.

@GantMan do I need to  npm install -g ignite-cli ?

we'll update the latest version tomorrow.   Or you can point at master branch tonight.

They had some issues with react-native-git-upgrade.  Check out the 0.49 release notes in the section called updating your code.
They say how you can solve it.  🎉

authors: GantMan skellock valinaga

repo: infinitered/ignite


text:
Is Redux a must?

Hello and thank you for ignite.
Is it mandatory to use Redux?
Ignite seems great but at the same time I dislike Redux with passion.
I'm sure one can find ways to use Ignite without Redux but how practical would that be?
Thanks for your feedback in davance.

(I am just an ignite user)
I can't believe that someone can dislike redux, but thats one of the benefits of using react: you can use any state-container you want, or none if you want to manage your state by yourself.
Practically you would need to remove all redux relevant code from your Root (App/Root.js) component and add your own store (any flux store, or rxjs store, or none).
Nevertheless, if your app or products grows you'll face some challanges which are solved by using redux and the architecture of ignite (which occasional is completely equal to our companies react arcitecture).

Thanks @hknd

if your app or products grows you'll face some challanges which are solved by using redux and the architecture of ignite
Is there something inherently biased towards Redux that mandates it use if the app "grows in complexity". One can simply use their own state management "thing" or would that alternative turn to be tedious due to ignite inner nature?
PS: We do exist (developers disliking Redux) but we are just hiding for now :)

Nothing is a must.  Ignite is indeed opinionated when it comes to state container choice.   We've seen Redux make a big difference in the apps we're building.
There is still value though in Ignite if you remove Redux, although considerably less.
Before you jump in, have a look around.  See how we do our theming.  Checkout our API access and our developer screens.
Redux is awesome.   But so is mobx, rxjs, and cerebral.   Use what's right for you.  And don't hide.  By exposing problems with Redux, it'll get better, or it's successor will.

Thank you for your reply.
Hiding was just a joke at ( I can't believe that someone can dislike redux )!

Ha!  Totally flew over my head!  :)

@mehdi-cit  - As our version 2 evolves, we hope to become more amicable towards differing opinions.   For example, right now you get push notifications... you may not want that.   Only a subset of our apps need it.  BUT for version 1.0 we decided to go kitchen sink.   Version 2.0 will be generator based, a la ignite add push etc.   There's no rule that says that there won't be a ignite add mobx one day... just depends on the demands and ecosystem.
Personally, I'm a fan of Redux :)  so I'll be making that generator first, but comparability will be our ultimate goal.   Please take this with a grain of salt, though, as we just released version 1.0, so 2.0 is far far away.

Thanks @GantMan !.
I will keep an eye on ignite

I must say I started using sagas because of ignite and I Love how simple my control flows become with sagas! :)
so.. my vote against redu(e)xit  for the sake of redux-sagas :D

With the new app-templates and plugins in 2.0, redux is now optional.

authors: GantMan ahmed1490 hknd mehdi-cit skellock


text:
npx ignite-cli remove-demo-markup unable to run prettier if no deps installed

The way npx ignite-cli remove-demo-markup works is removing some comment blocks related to marking demo code and then runs prettier over the codebase to correct any formatting that is needed.
However, if the user decided not to install dependencies yet and decides to run this command, the prettier formatting will fail.
We'll need to improve the regex to get the spacing right during string replacement, consider running npx prettier or come up with another solution (possibly just warning the user it can't be run as the dependency wasn't found).

:tada: This issue has been resolved in version 8.2.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: frankcalise infinitered-circleci


text:
new install in Win10 - not finding react-native-cli

Hello,
I've just made a fresh install of everything on Win 10.
When I run command 'ignite new testApp'
I get error:
Igniting testApp
� Must have at least version 1.x - 'npm install -g react-native-cli'
I did ran that command and it finished with a message '`-- react-native-cli@1.0.0'
node v6.3.0
npm v3.8.3

I'm also getting the same error. I also have react-native-cli@1.0.0 installed.

me too

Install grep please, we think this might be the issue.
This code will fail without grep:
https://github.com/infinitered/ignite/blob/6f2c628440fc20f622aa1420b7cc11456c458729/ignite-generator/src/app/index.es#L140-L142
We'll update the check to alarm windows users

please upgrade to 1.4.0 and try again.

Everything is working for me with the following versions:
Computer
  Platform: win32

Ignite
  Version: 1.4.0
  Path: C:\USERS\KEVIN\APPDATA\ROAMING\NPM\IGNITE.CMD

Node
  Version: v6.3.1
  Path: C:\PROGRAM FILES\NODEJS\NODE.EXE

NPM
  Version: 3.10.6
  Path: C:\PROGRAM FILES\NODEJS\NPM.CMD

Yeoman
  Version: 1.8.3

React Native CLI
  Version: 1.0.0

App
  React Native Version: ¯\_(ツ)_/¯

did you have to install grunt-cli globally?

I already had it. Keep in mind that I'm on Microsoft's Windows Insider builds, so I have early access to things like Bash in CMD.

I can confirm, it's working now
Thanks a lot!

excellent!  Closing now

authors: GantMan akhenda kevinvangelder mengyou658 xims


text:
Update ci.yml

use stable for better reliability on PRs

bors r+

@sehz maybe also needed to update branch protection rules here for bors?

Let me check

updated

bors r+

authors: morenol sehz

repo: infinyon/http-connector


text:
404 error on Troubleshooting Link with Internet Speed Plugin of InfluxDB Cloud

Describe the issue here.
Relevant URLs

Provide relevant URLs
https://docs.influxdata.com/telegraf/v1.23/administration/troubleshooting/

What products and version are you using?

InfluxDB cloud https://us-east-1-1.aws.cloud2.influxdata.com/orgs/cea12de46a986fa7/load-data/telegraf-plugins/internet_speed/new
after configuring API token & successfully starting telegraf on client, "Listen for Data" comes back with error "Error Listening for Data"
selecting "Telegraf Troubleshoot" link points to https://docs.influxdata.com/telegraf/v1.23/administration/troubleshooting/ which gives a 404 error

Following instructions from https://www.influxdata.com/blog/how-monitor-internet-speed-telegraf-influxdb-cloud/


text:
Feat/token

Hey ! Thanks for this Github Action, it's very convenient :)
Would you mind adding support for API token ?
I miss a proper way to test it locally, and being a bit rusty with bash I'd greatly appreciate a review (if changes are required, please let me know)

Any reason this PR is not merged?
Seems like API Token is the default way to work with in influxDB v2.

+1

repo: influxdata/influxdb-action


text:
Unable to install and run Influxdb-relay

I am following all instructions in the readme.md, yet it fails at the very first step at
$ go install github.com/influxdata/influxdb-relay
Error:
can't load package: package github.com/influxdata/influxdb-relay: no buildable Go source files.
I even tried cloning the code in the directory and tried running build.py
it gives error saying could not find dependencies; go
I have installed go properly on my system. I am sure there is no issue on your part, but I am fairly new to both influxdb-relay as well as Go. Also if someone can dockerize the relay, it will be great help.
Thanks

I am having the same issue as issue#12, but even when I do a go get ...
it gives Error:
can't load package: package github.com/influxdata/influxdb-relay: no buildable Go source files in /home/sagar/influxdbrelay/go/src/github.com/influxdata/influxdb-relay

Sorry, the command should be go get -u github.com/influxdata/influxdb-relay
I'll update the docs to include that.

If you are still getting that error, you might need to remove the influxdb-relay directory from your current GOPATH

Hello,
Thanks for the update of the readme.md. I am still having issues,
When I run $ go get -u github.com/influxdata/influxdb-relay
Error:
package github.com/influxdata/influxdb-relay: directory "/usr/local/go/src/github.com/influxdata/influxdb-relay" is not using a known version control system
So I removed the directory influxdb-relay and tried again and got,
package github.com/influxdata/influxdb-relay: cannot download, $GOPATH not set. For more details see: go help gopath
I have the right gopath as we can see in the ~/.profile
`# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
export PATH=$PATH:/usr/local/go/bin
`
still gives gopath not set error.
Can you please help me out, also is there a reliable ready image on dockerhub for the influxdb-relay?

authors: joelegasse sagarmah

repo: influxdata/influxdb-relay


text:
Division operator returns weird results on division by float

System info:
Influxd version: 1.5.2
Influx shell version: 1.5.2
Steps to reproduce:
I'm running these queries on a normal timeseries. For some reason the last query returns results all over the value range.
> select sum("value") from "foo" WHERE time >= now() - 10m GROUP BY time(10s)
name: foo
time                sum
----                ---
1535552200000000000
1535552210000000000 28507
1535552220000000000 28089
1535552230000000000 27968
1535552240000000000 27944
1535552250000000000 28543
1535552260000000000 28382
1535552270000000000 27781
1535552280000000000 26966
1535552290000000000 29876
1535552300000000000 28340
1535552310000000000 27465
1535552320000000000 27499
1535552330000000000 27138
1535552340000000000 30250
1535552350000000000 28276
1535552360000000000 28259
1535552370000000000 28726
1535552380000000000 28009
1535552390000000000 28652
1535552400000000000 27988
1535552410000000000 27722
1535552420000000000 28586
1535552430000000000 28790
1535552440000000000 28720
1535552450000000000 28651
1535552460000000000 28553
1535552470000000000 28779
1535552480000000000 29252
1535552490000000000 29244
1535552500000000000 27998
1535552510000000000 28398
1535552520000000000 28655
1535552530000000000 28010
1535552540000000000 29402
1535552550000000000 28744
1535552560000000000 28872
1535552570000000000 27587
1535552580000000000 28841
1535552590000000000 30029
1535552600000000000 29708
1535552610000000000 29329
1535552620000000000 28925
1535552630000000000 29278
1535552640000000000 29213
1535552650000000000 28716
1535552660000000000 29603
1535552670000000000 29117
1535552680000000000 28906
1535552690000000000 29114
1535552700000000000 28749
1535552710000000000 28993
1535552720000000000 29046
1535552730000000000 28867
1535552740000000000 28880
1535552750000000000 29212
1535552760000000000 28969
1535552770000000000 28414
1535552780000000000 29236
1535552790000000000 29174
1535552800000000000 28616

> select sum("value")/3 from "foo" WHERE time >= now() - 10m GROUP BY time(30s)
name: foo
time                sum
----                ---
1535552190000000000
1535552220000000000 28000.333333333332
1535552250000000000 28235.333333333332
1535552280000000000 28394
1535552310000000000 27367.333333333332
1535552340000000000 28928.333333333332
1535552370000000000 28462.333333333332
1535552400000000000 28098.666666666668
1535552430000000000 28720.333333333332
1535552460000000000 28861.333333333332
1535552490000000000 28546.666666666668
1535552520000000000 28689
1535552550000000000 28401
1535552580000000000 29526
1535552610000000000 29177.333333333332
1535552640000000000 29177.333333333332
1535552670000000000 29045.666666666668
1535552700000000000 28929.333333333332
1535552730000000000 28986.333333333332
1535552760000000000 28873
1535552790000000000 29087.666666666668

> select sum("value")/1.5 from "foo" WHERE time >= now() - 10m GROUP BY time(15s)
name: foo
time                sum
----                ---
1535552220000000000 18645.333333333332
1535552235000000000 18629.333333333332
1535552250000000000 37950
1535552265000000000 18520.666666666668
1535552280000000000 37894.666666666664
1535552295000000000 18893.333333333332
1535552310000000000 36642.666666666664
1535552325000000000 18092
1535552340000000000 39017.333333333336
1535552355000000000 18839.333333333332
1535552370000000000 37823.333333333336
1535552385000000000 19101.333333333332
1535552400000000000 37140
1535552415000000000 19057.333333333332
1535552430000000000 38340
1535552445000000000 19100.666666666668
1535552460000000000 38221.333333333336
1535552475000000000 19501.333333333332
1535552490000000000 38161.333333333336
1535552505000000000 18932
1535552520000000000 37776.666666666664
1535552535000000000 19601.333333333332
1535552550000000000 38410.666666666664
1535552565000000000 18391.333333333332
1535552580000000000 39246.666666666664
1535552595000000000 19805.333333333332
1535552610000000000 38836
1535552625000000000 19518.666666666668
1535552640000000000 38619.333333333336
1535552655000000000 19735.333333333332
1535552670000000000 38682
1535552685000000000 19409.333333333332
1535552700000000000 38494.666666666664
1535552715000000000 19364
1535552730000000000 38498
1535552745000000000 19474.666666666668
1535552760000000000 38255.333333333336
1535552775000000000 19490.666666666668
1535552790000000000 38526.666666666664
1535552805000000000 19648.666666666668
1535552820000000000 19741.333333333332

Expected behavior:
All 3 queries should have returned data in similar range

Maybe the real issue here is that each metric is 10s apart, so maybe group by time(15s) is causing the issue?

This looks like it's to do with the grouping boundaries. What's the interval frequency of the data?

Hi, yes this is due to the collection interval being 10s. This is basically
an issue due to grafana choosing the value of 15s for it's automatic
interval.
Is there any way to group by 15s and still get correct results using some
influx query?

@Navgeet not sure if it will help but maybe a group by time with offset to shift the boundary?

closing due to lack of response.

authors: Navgeet dgnorton e-dard russorat

repo: influxdata/influxdb


text:
Flux REPL incorrectly loaded in Windows

System info: [Include InfluxDB version, operating system name, and other relevant details]
Windows 7
InfluxDB version 1.7.0~n201811210800 (also occurs within the released version of 1.7 for Windows)
enable-flux is set to true within the config file
Steps to reproduce:

Within powershell (or command line) execute influx.exe -type=flux

Expected behavior: [What you expected to happen]
I am able to type flux commands into the window as I would any other REPL environment.
Actual behavior: [What actually happened]
The system prints out a seemingly random selection of characters at startup and whenever I attempt to type or simple click on the window as shown within the screenshot.

Additional info: [Include gist of relevant config, logs, etc.]
Within the influxdb process I get the following message, which occurs when I attempt to open the influx.exe process with the flux flag:
[httpd] ::1 - - [21/Nov/2018:15:00:44 +0000] "GET /ping HTTP/1.1" 204 0 "-" "InfluxDBShell/1.7.0~n201811210800" '386754a1-ed9e-11e8-8004-5048494f4e43 0'

After leaving the powershell window with the influx.exe running in this state it has finally threw an exception after 1069 minutes, which may be of help in diagnosing this issue.
Exception 0xc0000005 0x1 0xc0002
88498 0x7768c4e0
PC=0x7768c4e0

syscall.Syscall6(0x776d54f0, 0x4, 0xf, 0xc0004fdce0, 0x1, 0xc000288498, 0x0, 0x0, 0x0, 0x0, ...)
        /usr/local/go/src/runtime/syscall_windows.go:185 +0xfc
syscall.(*Proc).Call(0xc0002d8040, 0xc0004fdd00, 0x4, 0x4, 0x20, 0xb0abc0, 0xce6e01, 0xc0004fdd00)
        /usr/local/go/src/syscall/dll_windows.go:152 +0x39d
syscall.(*LazyProc).Call(0xc000118cc0, 0xc0004fdd00, 0x4, 0x4, 0x40c3af, 0x20, 0xb9fa80, 0x1000000012ca601)
        /usr/local/go/src/syscall/dll_windows.go:302 +0x66
github.com/influxdata/influxdb/vendor/github.com/mattn/go-tty.readConsoleInput(0xf, 0xc0004fdce0, 0xc000423fa0, 0x18406a
0)
        /root/go/src/github.com/influxdata/influxdb/vendor/github.com/mattn/go-tty/tty_windows.go:134 +0xad
github.com/influxdata/influxdb/vendor/github.com/mattn/go-tty.(*TTY).readRune(0xc0001e2780, 0xafdda0, 0x1, 0xc0000cdc00)

        /root/go/src/github.com/influxdata/influxdb/vendor/github.com/mattn/go-tty/tty_windows.go:201 +0xce
github.com/influxdata/influxdb/vendor/github.com/mattn/go-tty.(*TTY).ReadRune(0xc0001e2780, 0x400, 0x400, 0xc0000cdc00)
        /root/go/src/github.com/influxdata/influxdb/vendor/github.com/mattn/go-tty/tty.go:30 +0x32
github.com/influxdata/influxdb/vendor/github.com/c-bata/go-prompt.(*WindowsParser).Read(0xc000094398, 0xc000532480, 0x0,
 0x400, 0x0, 0x0)
        /root/go/src/github.com/influxdata/influxdb/vendor/github.com/c-bata/go-prompt/windows_input.go:47 +0x79
github.com/influxdata/influxdb/vendor/github.com/c-bata/go-prompt.(*Prompt).readBuffer(0xc0000a28a0, 0xc0000a2960, 0xc00
0532480)
        /root/go/src/github.com/influxdata/influxdb/vendor/github.com/c-bata/go-prompt/prompt.go:246 +0x96
created by github.com/influxdata/influxdb/vendor/github.com/c-bata/go-prompt.(*Prompt).Run
        /root/go/src/github.com/influxdata/influxdb/vendor/github.com/c-bata/go-prompt/prompt.go:56 +0x169

As a (potentially huge) workaround you can use Windows Subsystem for Linux (WSL), install influxdb from the influxdata package-repository (to get the newest flux-enabled release) and use the wsl-terminal. This will render the flux-mode correctly.

Install and set up WSL (choose whatever distribution you like)
Download wsl-terminal and start open-wsl.exe (no install required)
Follow the InfluxDB install instructions for the distribution you chose earlier
Start and enjoy influx -type=flux


text:
Column order function

Proposal:
Need a function to order columns manually.
Current behavior:
Table columns are received in a specific order and cannot be changed
Desired behavior:
InfluxDB 2.0 result table columns could respect function keep() column order and return results columns in that order
|> keep(columns: [“inventory_no”,“temp1”,“temp2”,“battery1”,“rssi”])

Alternatives considered:
Alternatevy there could be specific column order (priority) function.
Use case:
GUI respects columns order received from InfluxDB?

In the UI, we recently added the ability to reorder the columns in a table view: https://github.com/influxdata/influxdb/pull/15944
Added @nathanielc to comment on the Flux function for column ordering.

Is there any Progress on this?

Is there any Progress on this?

There is a hack for this - do a map to a series of numbered columns which will keep their order, then rename them:
|> map(fn: (r) => ({ _time: r._time, "1": r.first, "2": r.second, "3": r.third, "4": r.fourth}))
|> rename(columns: { "1": "First", "2": "Second", "3": "Third", "4": "Fourth" })
Works well for me doing stacked bars in Grafana; typically I also start with a pivot to get the columns from fields.

I also want this!

Yeah. I need this too. I can't use anything done outside the database query, as the column names are not constant.
Consider column names being numbers generated from data (via pivot). The column names will then depend on the data. Some columns are staying constant as well. So my column names are A, B, C, D, E, 567, 568, 569.
The number of columns with numbered names vary, sometimes there's only one, sometimes there's 10. And I want to order them as A, B, 567, 568, 569 (as many numbered columns as there is), C, D, E.
Even the map and rename is not working here...

I need this as well.
For now i'm using @pseudocoder 's hack, but I would prefer to use a real function.

@pseudocoder 's solution worked perfectly for the time being.  Thanks!!!!!

I tried this one in my application to get data from my influxdb2.

|> map(fn: (r) => ({ _time: r._time, "1": r.first, "2": r.second, "3": r.third, "4": r.fourth}))
|> rename(columns: { "1": "First", "2": "Second", "3": "Third", "4": "Fourth" })

I use these statements in the query with "|> schema.fieldsAsCols()"
It seems that the rearrange does not work here (12 different columns). The Columns seem to be ordered randomly and not alphabetically?
With a Table with 2 columns it works fine. But maybe its just a coincidence because there are not as many cases as in the first scenario.

This only works when viewing raw data and not in the actual table within the UI.
upvote for this feature to be added

There is a hack for this - do a map to a series of numbered columns which will keep their order, then rename them:
|> map(fn: (r) => ({ _time: r._time, "1": r.first, "2": r.second, "3": r.third, "4": r.fourth})) |> rename(columns: { "1": "First", "2": "Second", "3": "Third", "4": "Fourth" })
Works well for me doing stacked bars in Grafana; typically I also start with a pivot to get the columns from fields.

This only works when viewing raw data and does not work in the cell within the UI - well in v2.6.1 anyway
Upvote this FR as this is certainly needed from a column relationship perspective

I also want this!
Edit: Can't you just go the Cell > Configure > and on the Table select Customize and under Column Settings just rearrange the Table Columns? Which I just figured out.

Good spot!!!!

This one would be much appreciated. Grafana logs panel after pivot is useless with random column ordering

authors: FinnHuelsbusch Help-i-am-lost Tobist burmajam fmichaut-dev myka280 oneofthemany pseudocoder psychogun russorat toddwarrington


text:
InfluxDB 2 Cloud doesn't expose /health endpoint at root URL

According to swagger definition the /health and /ready endpoint should be exposed at root path, but it works only for OSS instances.
https://github.com/influxdata/influxdb/blob/26cf6af07aeb2956ddf5792a31269a94c0f0528e/http/swagger.yml#L2002
Steps to reproduce:
List the minimal actions needed to reproduce the behaviour.

curl -i -X GET https://us-west-2-1.aws.cloud2.influxdata.com/health \
    -H "Authorization: Token mytoken"

Expected behavior:
Return JSON with health information.
HTTP/2 200
date: Tue, 18 Aug 2020 08:28:06 GMT
content-type: application/json; charset=utf-8
content-length: 994
vary: Accept-Encoding
strict-transport-security: max-age=15724800; includeSubDomains

{
	"authorizations": "/api/v2/authorizations",
	"backup": "/api/v2/backup",
	"buckets": "/api/v2/buckets",
	"checks": "/api/v2/checks",
	"dashboards": "/api/v2/dashboards",
	"delete": "/api/v2/delete",
	"external": {
		"statusFeed": "https://www.influxdata.com/feed/json"
	},
	"flags": "/api/v2/flags",
	"labels": "/api/v2/labels",
	"me": "/api/v2/me",
	"notificationEndpoints": "/api/v2/notificationEndpoints",
	"notificationRules": "/api/v2/notificationRules",
	"orgs": "/api/v2/orgs",
	"plugins": "/api/v2/telegraf/plugins",
	"query": {
		"analyze": "/api/v2/query/analyze",
		"ast": "/api/v2/query/ast",
		"self": "/api/v2/query",
		"suggestions": "/api/v2/query/suggestions"
	},
	"scrapers": "/api/v2/scrapers",
	"setup": "/api/v2/setup",
	"signin": "/api/v2/signin",
	"signout": "/api/v2/signout",
	"sources": "/api/v2/sources",
	"swagger": "/api/v2/swagger.json",
	"system": {
		"debug": "/debug/pprof",
		"health": "/health",
		"metrics": "/metrics"
	},
	"tasks": "/api/v2/tasks",
	"telegrafs": "/api/v2/telegrafs",
	"users": "/api/v2/users",
	"variables": "/api/v2/variables",
	"write": "/api/v2/write"
}

Actual behavior:
Return HTML page:
HTTP/2 200
date: Tue, 18 Aug 2020 08:28:19 GMT
content-type: text/html
content-length: 1017
vary: Accept-Encoding
strict-transport-security: max-age=15724800; includeSubDomains
last-modified: Mon, 17 Aug 2020 23:09:22 GMT
vary: Accept-Encoding
etag: "5f3b0e22-3f9"
accept-ranges: bytes

<!doctype html><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>InfluxDB 2.0</title><base href="/"><link rel="shortcut icon" href="/favicon.ico">

%

Environment info:

InfluxDB version: https://us-west-2-1.aws.cloud2.influxdata.com/

Swagger definition:

Related to https://github.com/influxdata/influxdb-client-java/issues/143

The "expected behavior" is NOT the expected behaviour in cloud. A change to expose that information in cloud is not valid, as I far as I understand it.

(1) Verify that we never expose the k8s /health or /ready endpoints on a public cloud API endpoint. These should only be bind’d to internal interfaces in cloud and should not be part of the public API.
(2) Verify what the /health and /ready endpoints return in OSS.
(3) Verify if OSS has  /api/v2/health and /api/v2/ready routes in addition to /health and /ready
(4) Verify which endpoint is used by the CLI ping command.
Then let’s get together and see what sorts out from this.
I think the cleanest implementation is to support a top level /ping endpoint for OSS and for Cloud that returns a 200 OK when up and to port all the liveness checks to that.  OSS will need to possibly report health/status information that’s not appropriate within cloud.  We can figure out how to have OSS-only endpoints for those things.

Hi @rbetts,
I've prepare change for exposing /ping endpoint.
Could you check it out:

https://github.com/influxdata/openapi/pull/140
https://github.com/influxdata/influxdb/pull/21723
?

Regards

authors: bednar rbetts


text:
Eliminate use of golang.org/x/crypto/ssh/terminal package

Proposal:
Eliminate use of golang.org/x/crypto/ssh/terminal package in influxdb. The only function used is terminal.IsTerminal, which is just a wrapper around term.IsTerminal. Eliminating golang.org/x/crypto/ssh/terminal will ease auditing of the enterprise FIPS build.
Current behavior:
Non-FIPS (BoringCrypto) crypto libraries get pulled in, which creates potential issues with FIPS auditing due to pulling non-FIPS crypto functions.
Desired behavior:
The entire golang.org/x/crypto/ssh package is eliminated from the build.
Alternatives considered:
Using a Go workspace to substitute an alternate golang.org/x/crypto module. This requires a lot of code to replicate functionality in golang.org/x/crypto, as there are portions of golang.org/x/crypto that will call to the BoringCrypto library when used and can be linked into the final binary. This also requires a large chunk of code that isn't actually relevant to InfluxDB OSS.
Use case:
FIPS

This is for InfluxDB 1.x (master-1.x)


text:
Influx apply creates duplicate Tasks and Notification Rules.

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

Create a Task
Export template

influx export all -f template.yaml

Apply template (previews show the task as being added, not unchanged/replaced)

influx apply -f template.yaml

Seeing the same behavior with Notification Rules.

I'm happy to work up a PR if we agree this is a bug.

Expected behavior:
A single copy of the task exists, and the preview shows unchanged or replaced.
Actual behavior:
A duplicate task is created.
Environment info:

System info: Run uname -srm and copy the output here

Linux 5.10.102.1-microsoft-standard-WSL2 x86_64

InfluxDB version: Run influxd version and copy the output here

InfluxDB v2.6.1 (git: 9dcf880fe0) build_date: 2022-12-29T15:53:07Z
Influx CLI 2.6.1 (git: 61c5b4d) build_date: 2022-12-29T15:41:09Z

Other relevant environment details: Container runtime, disk info, etc

Docker image: influxdb:2.6-alpine

Config:
Running using Docker Compose and running the CLI commands by execing into the running container.

Hey @ryanrolds, I do agree that I would expect to see "unchanged" for applying back the same resources I already have. This seems to work as expected for buckets, though not for others. PRs are always welcome! The API endpoint that is being called for influx apply is here, that would be a good place to start investigating.

Thanks. I will take a look and try to work something over the next week or so.

It looks like the model for Buckets fetches by name when an ID isn't present, and templates do not include the ID. I'm under the impression that names are not unique for all models (as I've seen Tasks, and others, have entities with the same name). Would exporting the id along with the name and only looking up existing entities by ID be acceptable?
If we have to fetch by name, not id, then a policy on handling multiple entities with the same name while importing will need to be decided.
Concerns:

Templates that include multiple entities of the same type with the same name.

How do we know we are updating the right one without a unique id?
Should these entities be rejected?

When importing a single entity and multiple entities of that type with the same are found.

Which one is updated?
How do we know that is the one the user expected to be updated?
Should the entity be rejected?

IMHO, not fetching+merging by name and only using a unique ID is the best path forward, but I don't have the business context/concerns that drive the current implementation.

I agree with your suggestion, the ID is the only thing that is guaranteed to be unique on a lot of these models. That's what should be used for export/import and determining existence or not.
Thanks again for taking a look at this!

Is there any concerns with the shared templates? If people have already imported a template without an id (name instead) what is the expected behavior when importing a new version (is this even a thing?) of the template that has IDs?

I think when importing a template with ids, it should use that to validate uniqueness. If there are not ids in the template, then we should fall back to the current behavior to prevent potentially breaking things.
I think that will handle things okay? I'm not super familiar with templates or their usage patterns so I don't know how often people are applying the same template over and over again unless testing?

Hi, any update on the argument?
I'm looking forward to use influx apply with ansible where the idempotency is almost a necessity.

I looked at doing the work, but the API would need significant rework and I abandoned the idea. I just put up with the wonky behavior and hope they fix it in the next version.

Hello, I run across the same issue.
I need a idempotente behavior for a complexe monitoring where the desired config is version controlled with git.
Is there any plan to work on this issue or at leas a workaround ?

I recall that the issue's crux is that the identifiers could be more consistent. What ends up in the files that would get imported don't have the right IDs.
A workaround will likely involve a script that creates any missing data in the right order and with the right IDs.

Hello people. Does anyone found some workaround for this?

authors: LCerebo impresionista jeffreyssmith2nd nykopol ryanrolds


text:
Is there any way to get Influxdb worked on HP-UX systems ?

Directions
GitHub Issues are reserved for actionable bug reports and feature requests.
General questions should be sent to the InfluxDB Community Site.
Before opening an issue, search for similar bug reports or feature requests on GitHub Issues.
_If no similar issue can be found, fill out either the "Bug Report" or the "Feature Request" section below.
Erase the other section and everything on and above this line.
Bug report
System info: [Include InfluxDB version, operating system name, and other relevant details]
Steps to reproduce:

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Additional info: [Include gist of relevant config, logs, etc.]
Also, if this is an issue of for performance, locking, etc the following commands are useful to create debug information for the team.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=true"

curl -o vars.txt "http://localhost:8086/debug/vars"
iostat -xd 1 30 > iostat.txt

Please note It will take at least 30 seconds for the first cURL command above to return a response.
This is because it will run a CPU profile as part of its information gathering, which takes 30 seconds to collect.
Ideally you should run these commands when you're experiencing problems, so we can capture the state of the system at that time.
If you're concerned about running a CPU profile (which only has a small, temporary impact on performance), then you can set ?cpu=false or omit ?cpu=true altogether.
Please run those if possible and link them from a gist or simply attach them as a comment to the issue.
Please note, the quickest way to fix a bug is to open a Pull Request.
Feature Request
Opening a feature request kicks off a discussion.
Requests may be closed if we're not actively planning to work on them.
Proposal: [Description of the feature]
Current behavior: [What currently happens]
Desired behavior: [What you would like to happen]
Use case: [Why is this important (helps with prioritizing requests)]

This issue appears to have just posted the default issue template so I'm going to close it.


text:
fix(upgrade): add log-level option

Closes #19923
Adds --log-level option to upgrade command with the same default level as run ie. info.

[X] Well-formatted commit messages
[X] Rebased/mergeable
[X] Tests pass

@alespour sorry, I forgot: can you add a line to the CHANGELOG?

You're right, I forgot about the CHANGELOG. Done.

authors: alespour danxmoran


text:
Fix Kapacitor Issue #942: HTTPS subscriptions don't work

Required for all non-trivial PRs

[X] Rebased/mergable
[X] Tests pass
[x] CHANGELOG.md updated
[X] Sign CLA (if not already signed)

Hey @e-dard thanks for looking.
I'm not certain I understand you though. This feature doesn't need private keys to work, you just need the public key certificate to establish the trust relationship. By default, this was loading the CA Certs from where ever they lived on the current host (see: https://golang.org/src/crypto/x509/root_linux.go). I'm just supplying the configuration to load it from a different location.

@mglazer ah cool. Sorry I hadn't had my coffee this morning and immediately assumed you were using these certs for server-side stuff 😄
@nathanielc can you take a look at the PR?

@mglazer Changes look good, just looks like there is a compilation error with the recent log message change.
services/subscriber/service.go:330: undefined: c in c.InsecureSkipVerify

My apologies. Fixed.

@mglazer Thanks!

authors: e-dard mglazer nathanielc


text:
🛑 alternative site is down

In fe1870f, alternative site (https://almgro7al3nzy.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: alternative site is back up in 58f1cc2 after 17 minutes.


text:
Add changelog entries for quint conversions

Preparation for a release so i can add integration tests to the quint
side.
Going forward, I'll be sure to add these entries as each fragment is
added.

[x] Entries added to ./unreleased/ for any new functionality

Codecov Report

Merging #2463 (4d0f4b2) into main (830f96e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2463   +/-   ##
=======================================
  Coverage   78.34%   78.34%
=======================================
  Files         441      441
  Lines       15388    15388
  Branches     2476     2439   -37
=======================================
  Hits        12056    12056
  Misses       3332     3332

Impacted Files
Coverage Δ

.../forsyte/apalache/tla/pp/ConstSimplifierBase.scala
96.93% <0.00%> (-1.03%)
:arrow_down:

...he/io/annotations/parser/CommentPreprocessor.scala
96.70% <0.00%> (+1.09%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter shonfeder

repo: informalsystems/apalache


text:
feat!: port LSM module to SDK v0.50.x

Description
Port the LSM module changes from feature/v0.47.x-ics-lsm
Ported PRs:
https://github.com/cosmos/cosmos-sdk/pull/18694
https://github.com/cosmos/cosmos-sdk/pull/19056
https://github.com/cosmos/cosmos-sdk/pull/19076
https://github.com/cosmos/cosmos-sdk/pull/19491
https://github.com/cosmos/cosmos-sdk/pull/19614
https://github.com/cosmos/cosmos-sdk/pull/20444
Backported:
#17352 and #18214  and partially #18737
Except those changes, code is adapted to follow the changes from sdk v0.50 such as the way addresses are parsed from strings and use of LegacyDec values. Also, when reviewing pay attention to the following changes:
x/staking/keeper/msg_server.go
->RedeemTokensForShares()
- GetDelegation used to return bool, and now returns error. If delegation is not found, types.ErrNoDelegation is returned and the code is changed according to it.
x/staking/keeper/liquid_stake.go
->RemoveExpiredTokenizeShareLocks()
- modified signature to return error
->GetTotalLiquidStakedTokens()
- added panic() call if store.Get() fails, because other panic() already existed before
->CheckExceedsGlobalLiquidStakingCap()
- modified signature to return error
->GetTokenizeSharesLock()
- added panic() call if store.Get() fails, because other panic() already existed before
->GetPendingTokenizeShareAuthorizations()
- added panic() call if store.Get() fails, because it makes more sense than returning an error
x/staking/keeper/tokenize_share_record.go
->hasTokenizeShareRecord()
- modified signature to return error
->GetLastTokenizeShareRecordID()
- added panic() call if store.Get() fails, because error should be returned only if the key is nil, which is not the case
x/staking/keeper/params.go
ValidatorBondFactor(), GlobalLiquidStakingCap(), ValidatorLiquidStakingCap()
- modified signature to return error
x/distribution/keeper/keeper.go
->WithdrawSingleShareRecordReward()
- this is only called from staking module hooks in RedeemTokensForShares() and delegation is removed as part of that execution, so it will never exist when called in WithdrawSingleShareRecordReward()
- we made the same change as in RedeemTokensForShares()
proto/cosmos/staking/v1beta1/tx.proto
proto/cosmos/distribution/v1beta1/tx.proto
-> for newly added msgs, ValidateBasic is in the msg server instead in separate ValidateBasic fn (core sdk v0.50 changed this for other msgs, so we addapted newly added lsm msgs according to this)

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] included the necessary unit and integration tests
[ ] added a changelog entry to CHANGELOG.md
[ ] updated the relevant documentation or specification, including comments for documenting Go code
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

All the LSM-related logic LGTM!
I just want to make sure that keeping #18214 is safe.
A nice to have would also be to get rid of github.com/gogo/protobuf.

@stana-miric I guess this PR can be closed now, right?

authors: mpoke sainoe stana-miric

repo: informalsystems/cosmos-sdk


text:
Move more default implementations to ChainEndpoint

Summary
Move default implementations of init_event_monitor, id, get_key, and add_key from CosmosSdkChain to ChainEndpoint.
Problem Definition
The implementations in CosmosSdkChain are generalizable, so moving them to ChainEndpoint reduces the amount of boilerplate for other chains.
Proposal
See the summary.
Acceptance Criteria
The functions are moved over to ChainEndpoint.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Thanks for documenting this issue and opening a PR for it! The requested change seems straightforward. One of us will look into it in more detail and review your PR.

authors: adizere kevinji

repo: informalsystems/hermes


text:
Better message, usage, option help and completion for CLIs

@ljoss17 @mzabaluev
Summary
So not sure this is a feature request or a bug and if there is anything we can do about it.
With the new CLIs in master, the USAGE and help are strange and sometimes not correct.
For example:
$ hermes create channel -h
hermes-create-channel
Create a new channel between two chains using a pre-existing connection

USAGE:
    hermes create channel [OPTIONS] --a-chain <A_CHAIN_ID> --a-port <A_PORT_ID> --b-port <B_PORT_ID>

OPTIONS:
        --a-chain <A_CHAIN_ID>
            Identifier of the side `a` chain for the new channel

        --a-connection <A_CONNECTION_ID>
            Identifier of the connection on chain `a` to use in creating the new channel.

        --a-port <A_PORT_ID>
            Identifier of the side `a` port for the new channel

        --b-chain <B_CHAIN_ID>
            Identifier of the side `b` chain for the new channel

        --b-port <B_PORT_ID>
            Identifier of the side `b` port for the new channel

        --channel-version <VERSION>
            The version for the new channel

    -h, --help
            Print help information

        --new-client-connection
            Indicates that a new client and connection will be created underlying the new channel

        --order <ORDER>
            The channel ordering, valid options 'unordered' (default) and 'ordered' [default:
            ORDER_UNORDERED]

        --yes
            Skip new_client_conn confirmation

There are a few issues for this one:

Create a new channel between two chains using a pre-existing connection is wrong, that is not the only option. Seems that a blank line (create.rs) in the description drops everything after when displayed with -h
the USAGE is wrong. not sure how much control we have with abscissa and clap but --a-chain appears both in USAGE and in OPTIONS. The required flags should not be [OPTIONS]

Not sure about this in fact as we wouldn't have a way to describe the required flags. Maybe have a [REQUIRED] section

the list of options in alphabetical order makes reading them hard, e.g. -h, --help appears in the middle of the option list. Is there a way to control the order in which they are listed?
completion seems to work for the first few options and then it stops working.

Haven't checked all CLIs but I expect most of the above will show there.
Maybe most or all of these issues where there before but we should cleanup as much as possible before v1.0.

Problem Definition

Proposal

Acceptance Criteria

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

There are a few issues for this one:
* `Create a new channel between two chains using a pre-existing connection` is wrong, that is not the only option. Seems that a blank line (`create.rs`) in the description drops everything after when displayed with -h

* the USAGE is wrong. not sure how much control we have with abscissa and clap but `--a-chain` appears both in `USAGE` and in `OPTIONS`. The required flags should not be `[OPTIONS]`

  * Not sure about this in fact as we wouldn't have a way to describe the required flags. Maybe have a [REQUIRED] section

* the list of options in alphabetical order makes reading them hard, e.g. `-h, --help` appears in the middle of the option list. Is there a way to control the order in which they are listed?

* completion seems to work for the first few options and then it stops working.

Haven't checked all CLIs but I expect most of the above will show there. Maybe most or all of these issues where there before but we should cleanup as much as possible before v1.0.

The description is the short version since the help was called with -h. By using the flag --help the long version will be displayed with more information. But I think the short help could be changed to be more clear.
Regarding the other issues you mentioned, I will look them up while working on the PR for the unit tests of the CLI command parsing.

After some additional experimentation, there is a potential solution for the ordering and the help headers, but it requires modifying every commands.
By adding AppSettings::NoAutoHelp and next_line_help = true from clap and then adding the following argument:
/// Query client consensus command
#[derive(Clone, Command, Debug, Parser, PartialEq)]
#[clap(global_setting(AppSettings::NoAutoHelp), next_line_help = true)]
pub struct QueryClientConsensusCmd {
    #[clap(
        short = 'h',
        long = "help",
        action = ArgAction::Help,
        hidden = true,
    )]
    h: bool,

It is possible to remove the -h, --help from the help message.
Once the -h, --help is removed, by adding a help_header = "REQUIRED" and help_header = "OPTIONS" to respectively the required and optional flags, it is possible to have the following help display:
Query the client consensus state

USAGE:
    hermes query client consensus [OPTIONS] --chain <CHAIN_ID> --client <CLIENT_ID>

REQUIRED:
        --chain <CHAIN_ID>
            Identifier of the chain to query

        --client <CLIENT_ID>
            Identifier of the client to query

OPTIONS:
        --consensus-height <CONSENSUS_HEIGHT>
            Height of the client's consensus state to query

        --height <HEIGHT>
            The chain height context to be used, applicable only to a specific height

        --heights-only
            Show only consensus heights

The advantages are that the help display message has the essential information and cleanly organised.
The disadvantage is that this requires modifying every command, so there is a higher risk that a command's help message won't be correctly formatted.
The disadvantage could be compensated with a unit test with the following format:
static HELP: &str = "hermes
Query the client consensus state

USAGE:
    hermes [OPTIONS] --chain <CHAIN_ID> --client <CLIENT_ID>

REQUIRED:
        --chain <CHAIN_ID>
            Identifier of the chain to query

        --client <CLIENT_ID>
            Identifier of the client to query

OPTIONS:
        --consensus-height <CONSENSUS_HEIGHT>
            Height of the client's consensus state to query

        --height <HEIGHT>
            The chain height context to be used, applicable only to a specific height

        --heights-only
            Show only consensus heights
";

    #[test]
    fn test_help_output() {

        let mut cmd = QueryClientConsensusCmd::command();

        let mut buf = Vec::new();

        cmd.write_help(&mut buf).unwrap();
        assert_eq!(HELP, String::from_utf8(buf).unwrap());
    }

What do you think ?

Thanks a lot for looking into this! While this would work, it seems like a lot of effort for fairly minimal gains. I think we'll just stick with -h and --help and their discrepancies.
What we can do to ensure users are more likely to see the full help message is direct them towards using the help subcommand (eg. hermes help create client) in the guide. What d you think?

I agree, the tradeoff between effort and gain was one of my concerns. I will stick to only adding the help_header to separate the required and optional flags in the help message.
I think it's a great idea to encourage the usage of the help subcommand.

authors: ancazamfir ljoss17 romac

repo: informalsystems/ibc-rs


text:
Turn non-200 HTTP responses into an error instead of trying to parse the body as a JSON-RPC response

Closes: #1359
This PR checks for the status code to be 200 OK, if not it returns an error with the actual status code and the body of the response, but does not attempt to parse the response body as a JSON-RPC payload.
CometBFT will always set the status code to 200 OK and the content type to JSON for response which were successfully handled (which does mean that the JSON-RPC response itself is successful).

[x] Referenced an issue explaining the need for the change
[x] Updated all relevant documentation in docs
[x] Updated all code comments where relevant
[ ] Wrote tests
[x] Added entry in .changelog/

Conditional compilation needs to be fixed for wasm, otherwise looks fine.

I will do this after we merge #1362

Conditional compilation needs to be fixed for wasm, otherwise looks fine.

https://github.com/informalsystems/tendermint-rs/pull/1361/commits/0b0f4c482b67b13357b1f0ba40acecb804829f33

I've tested this from Hermes, and it works as expected.

Conditional compilation needs to be fixed for wasm, otherwise looks fine.

In fact, why do we build RPC stuff for wasm?

In fact, why do we build RPC stuff for wasm?

Because one can define a Client implementation which uses eg. the browser's fetch method and then compile all that to WASM.

authors: mzabaluev romac

repo: informalsystems/tendermint-rs


text:
🛑 Meyer Lab mail server is down

In 6514a0c, Meyer Lab mail server (vps-1397470-x.dattaweb.com) was down:

HTTP code: 403
Response time: 571 ms

Resolved: Meyer Lab mail server is back up in 91e5150 after 22 minutes.

repo: informaticaMeyerlab/statusPageMeyerLab


text:
Internal Server Error while creating foreign Keys

@karlcz Basically when you create new tables and try creating a foreign key immediately after creation, you get a 500 Internal Server error.
Request
POST /ermrest/catalog/71/schema/EUVAv/table/dataset_preview/foreignkey HTTP/1.1
HOST: dev.isrd.isi.edu
cookie: ermrest=C6KFIQn2JS37CGovofWnjKfu;
content-type: application/json
content-length: 219

 {"foreign_key_columns":[{"table_name":"dataset_preview","schema_name":"EUVAv","column_name":"preview_id"}],"annotations":{},"referenced_columns":[{"table_name":"sample_name","schema_name":"EUVAv","column_name":"term"}]}

Response
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<title>500 Internal Server Error</title>

Internal Server Error

The server encountered an internal error or
misconfiguration and was unable to complete
your request.

Please contact the server administrator at
 root@localhost to inform them of the time this error occurred,
 and the actions you performed just before this error.

More information about this error may be available
in the server error log.

After 10-15 seconds, if you try creating the foreign key again, the call succeeds.

This is fixed in master so you'll see it once it rolls out to the CI dev server

@robes  see fix in db1de8b4f36d960be21045196fbd0bcae814294c and test cases in dd13799fc070b5878d98e398e8ed75fb78c652da

authors: chiragsanghvi karlcz

repo: informatics-isi-edu/ermrest


text:
'information content entity' uses old BFO id in ontology-metadata

From albertgo...@gmail.com on May 06, 2012 09:49:49
Any OWL ontology using new BFO ids and importing ontology-metadata will have a duplicate GenericallyDependentContinuant because the superclass of 'information content entity' is still:
" http://www.ifomis.org/bfo/1.1/snap#GenericallyDependentContinuant "
Any idea when ontology-metadata will get the new BFO ids?
Original issue: http://code.google.com/p/information-artifact-ontology/issues/detail?id=134

From mcour...@gmail.com on May 07, 2012 11:32:23
See https://groups.google.com/forum/?fromgroups#!topic/information-ontology/T6X_IuPV4Kw The issue is which version of BFO2 should be used if any, as nothing has been officially released by the BFO2 OWL working group yet.
We had a discussion about whether or not IAO should switch to BFO2. As you can see from the thread, we didn't come to any resolution. Based on recent exchanges on bfo-owl-devel, it seems we may not be that far away to getting a pre-alpha-release (name subject to change) of BFO2 OWL (Alan committed to producing something for review in the next 2 weeks), so I am willing to give it a bit more time.

From alanruttenberg@gmail.com on May 08, 2012 11:06:18
I will try to publish, only as a dated purl, the version of IAO that uses the IAO with BFO2 ids that OBI uses. Melanie correctly notes the status of that version.
Labels: -Type-Defect -Priority-Medium Type-Task Priority-Low

From zhengj2...@gmail.com on May 08, 2012 12:48:34
BFO2 (Alan version) compatible IAO is under https://information-artifact-ontology.googlecode.com/svn/releases/2012-01-05/ontology/
Owner: zhengj2...@gmail.com

repo: information-artifact-ontology/IAO


text:
🛑 Uvirtual is down

In a2148bf, Uvirtual (https://uvirtual.unimonserrate.edu.co/) was down:

HTTP code: 503
Response time: 431 ms

Resolved: Uvirtual is back up in 450ee35.

repo: infraestructuraidt/status


text:
Please invite me to the community

Name
Cryptodev
Additional Context
I wanna become a open source contributor in infraform community.

Invitation sent to join the GitHub Organization. Welcome to Infraform 🎉Please check your mail to accept the invitation sent by GitHub! 🤖About usInfraform is an open source solution for serverless platforms, it is designed for developing solutions and enhancing creators to create their infrastructure 💻 Great to have you in our community ✨ Looking forward to your valuable contributions! 🤓 You can also check our community ✨ Github ✨ LinkedIn 💜 You can also share our community with other folks who want to learn about development, DevOps, tech, and contribute together and with us 👉💜👈

repo: infraform/contribute


text:
Installation of loki-operator blocked by Docker Hub rate limit

When deploying via stf-run-ci the builds of loki-operator results in a pull of golang image, which is hosted on hub.docker.com. If the deployment of this run-ci.yaml is run behind a corporate firewall, there is an extremely likely chance the deployment will fail.
The deployment of loki-operator needs to be wrapped so it can skipped, or a path parameter added that allows a different base image for loki-operator to be specified and in-line replaced in the build/working/loki-operator/Dockerfile.
This is a high priority issue as this will quickly block our ability to run CI.

Pulling image golang:1.16 ...
Warning: Pull failed, retrying in 5s ...
Warning: Pull failed, retrying in 5s ...
Warning: Pull failed, retrying in 5s ...
error: build error: failed to pull image: After retrying 2...g and upgrading: https://www.docker.com/increase-rate-limit

repo: infrawatch/service-telemetry-operator


text:
hi can show on render progress on html

hi, first Thanx very much for this incredible module. I am new on Node/express. I could install the nexrender and all works ok. I use the method 👍
 main().finally(function () {
          console.log(" task finished")
        })

And all work fine but I want to do think after the task has finished, but all functions I put inside the terminal return me a promise error for example
 main().finally(function () {
          console.log(" task finished")
          res.render('task finished')
        })

The second question how can I show the progress on the front end, is there another main() function? or the key is with onrender progress that is inside the jsdon after actions?
thanx

Hey @chaza1984
Could you show your full code, what is the main function, etc.
Also most likely it is the problem related to the promises/javascript language in general, so I would also recommend reading more on those. Possibly you will be able to fix everything on your own.
Regarding progress, it should be reported via various ways, depending on what exact package are you using. You can refer to the source code as well, that right now is the best source of "truth" if readme does not cover the topic.
Cheers!

HI, probably you are right, I am try to apply the promise and asyc await without good results. My code is working but i now its not good write.  Maybe you can helpme with the progress. At the end I render a html and I show a mensage but all the time I receive undefined.
thanx
//MULTER (Module for capture images)
const storage = multer.diskStorage({
destination: (req, file, cb) => {
cb(null, 'src/public/images/')
},
filename: (req, file, cb) => {
archivoFoto = file.fieldname + '-' + Date.now() + path.extname(file.originalname)
//fieldname va a estampar en el archivo el nombre que tenga "name" en la etiqueta input. (para no usar el nombre que viene con el archivo.)
cb(null, archivoFoto)
}
});
const upload = multer({
storage: storage,
limits: { fileSize: 1000000 },
fileFilter: function (req, file, cb) {
checkFileType(file, cb);
}
}).single('photoUpload');
function checkFileType(file, cb) {
const filetypes = /jpeg|jpg|png|gif/;
const extname = filetypes.test(path.extname(file.originalname).toLowerCase());
const mimetype = filetypes.test(file.mimetype);
if (mimetype && extname) {
return cb(null, true);
}
else {
cb('Error: Images Only!');
}
}
router.post('/Frozen2', async (req, res) => {
procesos();
})
upload(req, res, (err) => {
if (err) {
  res.render('Frozen2', {
    msg: err
  });
}

else {
  if (req.file == undefined) {
    res.render('Frozen2', {
      msg: 'Error: No File Selected'
    })
  }

  else {

    let fechaNombre = Date.now()
    const { fecha1, fecha2, mensaje1, mensaje2, direccion1, direccion2, direccion3, despedida1, despedida2 } = req.body

    if (!fecha1 || !direccion1 || !direccion2 || !despedida1) {
      res.render('Frozen2.ejs', {
        msg: 'Error: Completa todos los campos'
      })

    }

    const job = {

      "template": {
        "src": "file:///C:/Users/chaza/Desktop/paginas/invitaciones/assets/frozen 2/after
                   effects/frozen2ok15.aep",
        "composition": "frozen2"
      },
      "assets": [
        {
          "src": "file:///C:/Users/chaza/Desktop/paginas/invitaciones/prueba 4/src/public/images/" +
                     archivoFotoReSize,
          "type": "image",
          "layerName": "fotomia"
        },
        {
          "type": "data",
          "layerName": "1fecha",
          "property": "Source Text",
          "value": fecha1
        }

      ],
      "actions": {

        "postrender": [
          {
            "module": "@nexrender/action-encode",
            "output": "encode.mp4",
            "preset": "mp4",
            "params": { "-vcodec": "libx264", "-r": 25 }
          },

          {
            "module": "@nexrender/action-copy",
            "output": "C:/Users/chaza/Documents/nexrender/exports mp4 copis/thisIsACopy" +
                             fechaNombre + ".mp4"
          },

        ]
      },

      onChange: (job, state) => console.log("testing onChange en json:", state),

      onRenderProgress: (job, value) => ("onrender progres:", value)

    }

    console.log(job)
    const json_videos = JSON.stringify(job)

    //res.send('recibido')

    const main = async () => {

      const result = await render(job, {
        workpath: 'C:/Users/chaza/Documents/nexrender/',
        //binary: 'C:/Program Files/Adobe After Effects CC 2019/Support Files/aerender.exe',
        binary: 'C:/Program Files/Adobe/Adobe After Effects CC 2018/Support Files/aerender.exe',
        skipCleanup: true,
        addLicense: false,
        debug: true,

      })

    }

    main().catch(console.error);
    console.log("error catch del main")

    main().finally(function () {
      console.log("Tarea finalizada!!!!!!!!!!!!!!!!!!!!!!!!!!")

    })

    main().then(function () {

      res.render('frozen2', {
        msgProgress: "progress : + job.value (Here would like yo show the progress) "
      })

    })

  }

}

})
})

Yea, I feel like there are some issues in your javascript code that might cause invalid behavior.
First thing I see is that you are calling main (and as result render) function 3 times, and additionally you are not returning the result from render outside of main function.

repo: inlife/nexrender