link logic for ZK not working.

After updating to the latest ZK cook book I've been getting this error below about the link not being able to be created due to folder existing. Even after trying to delete the folders and running chef client again I get the same error. It looks to be that some logic is creating a /opt/zookeeper/data directory with recursive true before ark installs and links the installed zk-version folder to /opt/zookeeper.
Recipe: zookeeper::install

zookeeper[3.4.8] action install
Recipe: java::notify

log[jdk-version-changed] action nothing (skipped due to action :nothing)
Recipe: java::set_java_home

ruby_block[set-env-java-home] action run (skipped due to not_if)

directory[/etc/profile.d] action create (up to date)

template[/etc/profile.d/jdk.sh] action create (up to date)
Recipe: java::oracle

yum_package[tar] action install (up to date)

java_ark[jdk] action install (up to date)

java_alternatives[set-java-alternatives] action set (up to date)

chef_gem[zookeeper] action install (up to date)

group[zookeeper] action create (up to date)

user[zookeeper] action create (up to date)

directory[/opt] action create (up to date)

directory[/var/log/zookeeper] action create (up to date)

directory[/opt/zookeeper/data] action create

create new directory /opt/zookeeper/data
change mode from '' to '0700'
change owner from '' to 'zookeeper'
change group from '' to 'zookeeper'
restore selinux security context

ark[zookeeper] action install

directory[/opt/zookeeper-3.4.8] action create

create new directory /opt/zookeeper-3.4.8
restore selinux security context

remote_file[/var/chef/cache/zookeeper-3.4.8.tar.gz] action create (up to date)

execute[unpack /var/chef/cache/zookeeper-3.4.8.tar.gz] action nothing (skipped due to action :nothing)

execute[set owner on /opt/zookeeper-3.4.8] action nothing (skipped due to action :nothing)

link[/opt/zookeeper] action create
================================================================================
Error executing action create on resource 'link[/opt/zookeeper]'
Errno::EISDIR
Is a directory @ unlink_internal - /opt/zookeeper
Cookbook Trace:
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in run_action' /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in run_action'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in `run_action'
Resource Declaration:
In /var/chef/cache/cookbooks/ark/providers/default.rb
75:     link new_resource.home_dir do
76:       to new_resource.path
77:     end
78:
Compiled Resource:
Declared in /var/chef/cache/cookbooks/ark/providers/default.rb:75:in `block in class_from_file'
link("/opt/zookeeper") do
action [:create]
retries 0
retry_delay 2
default_guard_interpreter :default
to "/opt/zookeeper-3.4.8"
link_type :symbolic
target_file "/opt/zookeeper"
declared_type :link
cookbook_name "zookeeper"
end
Platform:
x86_64-linux

execute[unpack /var/chef/cache/zookeeper-3.4.8.tar.gz] action run

execute /bin/tar xzf /var/chef/cache/zookeeper-3.4.8.tar.gz --strip-components=1

execute[set owner on /opt/zookeeper-3.4.8] action run

execute chown -R root:0 /opt/zookeeper-3.4.8

================================================================================
Error executing action install on resource 'ark[zookeeper]'
Errno::EISDIR
link[/opt/zookeeper] (/var/chef/cache/cookbooks/ark/providers/default.rb line 75) had an error: Errno::EISDIR: Is a directory @ unlink_internal - /opt/zookeeper
Cookbook Trace:
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in run_action' /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in run_action'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in `run_action'
Resource Declaration:
In /var/chef/cache/cookbooks/zookeeper/resources/default.rb
83:   ark 'zookeeper' do
84:     url         "#{mirror}/zookeeper-#{new_resource.version}/zookeeper-#{new_resource.version}.tar.gz"
85:     version     new_resource.version
86:     prefix_root install_dir
87:     prefix_home install_dir
88:     checksum    new_resource.checksum if property_is_set? :checksum
89:   end
90: end
Compiled Resource:
Declared in /var/chef/cache/cookbooks/zookeeper/resources/default.rb:83:in `block in class_from_file'
ark("zookeeper") do
action [:install]
updated true
updated_by_last_action true
retries 0
retry_delay 2
default_guard_interpreter :default
declared_type :ark
cookbook_name "zookeeper"
url "http://apache.mirrors.tds.net/zookeeper//zookeeper-3.4.8/zookeeper-3.4.8.tar.gz"
version "3.4.8"
prefix_root "/opt"
prefix_home "/opt"
extension "tar.gz"
prefix_bin "/usr/local/bin"
home_dir "/opt/zookeeper"
path "/opt/zookeeper-3.4.8"
release_file "/var/chef/cache/zookeeper-3.4.8.tar.gz"
owner "root"
end
Platform:
x86_64-linux

================================================================================
Error executing action install on resource 'zookeeper[3.4.8]'
Errno::EISDIR
ark[zookeeper] (/var/chef/cache/cookbooks/zookeeper/resources/default.rb line 83) had an error: Errno::EISDIR: link[/opt/zookeeper] (/var/chef/cache/cookbooks/ark/providers/default.rb line 75) had an error: Errno::EISDIR: Is a directory @ unlink_internal - /opt/zookeeper
Cookbook Trace:
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in run_action' /var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in run_action'
/var/chef/cache/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/runner.rb:41:in `run_action'
Resource Declaration:
In /var/chef/cache/cookbooks/zookeeper/recipes/install.rb
18: zookeeper node['zookeeper']['version'] do
19:   username          node['zookeeper']['user']
20:   user_home         node['zookeeper']['user_home']
21:   mirror            node['zookeeper']['mirror']
22:   checksum          node['zookeeper']['checksum']
23:   install_dir       node['zookeeper']['install_dir']
24:   log_dir           node['zookeeper']['log_dir']
25:   data_dir          node['zookeeper']['config']['dataDir']
26:   use_java_cookbook node['zookeeper']['use_java_cookbook']
27: end
Compiled Resource:
Declared in /var/chef/cache/cookbooks/zookeeper/recipes/install.rb:18:in `from_file'
zookeeper("3.4.8") do
action [:install]
updated true
updated_by_last_action true
retries 0
retry_delay 2
default_guard_interpreter :default
declared_type :zookeeper
cookbook_name "zookeeper"
recipe_name "install"
username "zookeeper"
user_home "/opt/zookeeper/home"
mirror "http://apache.mirrors.tds.net/zookeeper/"
checksum "f10a0b51f45c4f64c1fe69ef713abf9eb9571bc7385a82da892e83bb6c965e90"
install_dir "/opt"
log_dir "/var/log/zookeeper"
data_dir "/opt/zookeeper/data"
use_java_cookbook true
version "3.4.8"
end
Platform:
x86_64-linux

Running handlers:
[2016-07-25T11:23:34-05:00] ERROR: Running exception handlers

Motd::KnifeStatus
Running handlers complete
[2016-07-25T11:23:34-05:00] ERROR: Exception handlers complete
Chef Client failed. 15 resources updated in 24 seconds
[2016-07-25T11:23:34-05:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2016-07-25T11:23:34-05:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-07-25T11:23:34-05:00] ERROR: zookeeper[3.4.8] (zookeeper::install line 18) had an error: Errno::EISDIR: ark[zookeeper] (/var/chef/cache/cookbooks/zookeeper/resources/default.rb line 83) had an error: Errno::EISDIR: link[/opt/zookeeper] (/var/chef/cache/cookbooks/ark/providers/default.rb line 75) had an error: Errno::EISDIR: Is a directory @ unlink_internal - /opt/zookeeper
[2016-07-25T11:23:34-05:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

[root@paw2cl-zookpr03 opt]# ls -alh /opt
total 32K
drwxr-xr-x.  8 root root 4.0K Jul 25 11:23 .
dr-xr-xr-x. 28 root root 4.0K Jul 19 04:49 ..
drwxr-xr-x.  6 root root 4.0K Jul 18 14:45 chef
drwxr-xr-x. 10 root root 4.0K Mar 23 15:04 collectd
drwxr-xr-x.  4 root root 4.0K Nov 13  2015 opscode-push-jobs-client
drwxr-xr-x.  2 root root 4.0K Mar 26  2015 rh
drwxr-xr-x.  3 root root 4.0K Jul 25 11:23 zookeeper
drwxr-xr-x. 10 root root 4.0K Jul 25 11:23 zookeeper-3.4.8
[root@paw2cl-zookpr03 opt]# ls -alh /opt/zookeeper
total 12K
drwxr-xr-x. 3 root      root      4.0K Jul 25 11:23 .
drwxr-xr-x. 8 root      root      4.0K Jul 25 11:23 ..
drwx------. 2 zookeeper zookeeper 4.0K Jul 25 11:23 data
[root@paw2cl-zookpr03 opt]# ls -alh /opt/zookeeper/data/
total 8.0K
drwx------. 2 zookeeper zookeeper 4.0K Jul 25 11:23 .
drwxr-xr-x. 3 root      root      4.0K Jul 25 11:23 ..

This is on CentOS 6.8 with chef-client 12.12.15


Fix building with latest TS version

Fixes a few error that prevent building with TS 2.4+

Use lib for getting promise type instead typings
Update package.json typescript and vscode versions
Add explicit typings to function to fix compile error

Fixed in 8dfd380a, released in 1.6.2.


[Here’s*freE TV]** Chelsea vs Arsenal LIVE STreams ON TV Channel 10 November 2024

Chelsea v Arsenal LIVE: Team news and line-ups from crunch Premier League clash at Stamford Bridge
Arsenal travel across the capital looking to reignite their title ambitions in a showdown with London rivals Chelsea Chelsea host Arsenal at Stamford Bridge today in the Premier League, with both sides on 18 points after 10 games and looking to climb the table after Manchester City slipped up against Brighton yesterday.
Chelsea laboured to a disappointing draw away at Manchester United last weekend and missed the chance to go third in the table, though they could yet jump that high should they triumph here. Meanwhile Arsenal enter the weekend after back-to-back defeats, the latest to Inter Milan in the Champions League, and find themselves 10 points behind leaders Liverpool.
The Gunners will want to remind neutrals of their title credentials, and a game against an old enemy at Stamford Bridge is the perfect chance to do so, while Enzo Maresca’s side will want to build on their early promise with a statement result.
How to watch Chelsea vs Arsenal: TV channel and live stream for Premier League game today
Derby showdown at Stamford Bridge is the final game before the international break
Chelsea face Arsenal in a huge Premier League showdown at Stamford Bridge.
Arsenal badly need to get their title bid back on track after three games without a win, while Chelsea are eyeing their first real statement win under Enzo Maresca.
Victory for Chelsea could see them go into the international break in third place in the table.
Defeat for Arsenal would leave the Gunners 10 points behind table-toppers Liverpool, who extended their lead at the top on Saturday after they beat Aston Villa and Manchester City lost at Brighton.
Here’s everything you need to know about where to watch the game...
How to watch Chelsea vs Arsenal
TV channel: The game will be broadcast on Sky Sports Main Event, Sky Sports Premier League and Sky Sports Ultra HDR. Coverage starts at 4pm GMT ahead of a 4.30pm kick-off.
Chelsea vs Arsenal LIVE! Premier League match stream, latest team news, lineups, TV, prediction today
Chelsea host Arsenal in a highly-anticipated London derby this afternoon, in the final Premier League match before the international break. The rivals sit level on points heading into the clash at Stamford Bridge, with the chance there for either of them to make a major statement.
The Blues have quickly settled into life under Enzo Maresca, with signs of some much-needed stability in west London. They came into this match having thrashed FC Noah 8-0 in midweek, even if little can be read into a match against the Armenian minnows. The big news for Chelsea will come ahead of kick-off, with doubts remaining over Cole Palmer’s fitness.
Arsenal, meanwhile, are looking to prevent their season derailing, having not won any of their past three Premier League matches. Having already lost to Newcastle and Inter Milan this week, Mikel Arteta’s side cannot afford another poor away day. Follow all the action with Standard Sport’s LIVE blog below, featuring expert analysis from Malik Ouzia and Simon Collings at the ground!
watch today's Chelsea vs Arsenal Premier League game: Live stream, TV channel, and start time
How to watch the Premier League match between Chelsea and Arsenal, as well as kick-off time and team news.
The last Premier League clash before the international break promises to be thrilling, as London rivals Chelsea and Arsenal square off at Stamford Bridge on Sunday.
Currently, both teams sit close in the standings after a promising start to the season for Enzo Maresca's Blues. While they've impressed in major matches, their recent 1-1 draw with Manchester United left fans wanting more.
Meanwhile, Mikel Arteta is likely frustrated with the Gunners holding onto fifth place after 10 matches, especially given their high standards from the past two seasons. They will approach this clash with something to prove, hoping to revive their title bid after a recent slump.
They also suffered a setback midweek, falling 1-0 to Inter Milan in the Champions League, which snapped their unbeaten European run. Nevertheless, a crucial three points are up for grabs, and both sides will be determined to come away with the victory.
Here, GOAL brings you everything you need to know about how to watch, including TV channel, streaming details and more.
How to watch Chelsea vs Arsenal online - TV channels & live streams

xcxc


Bot framework cant find /api/messages

Hello I'm working with Microsoft Bot Framework
I try to make a Skype bot but there is whenever i'm in the bot framework test 404 not found, There is no folder /api/messages and I cant find that folder too in de ftp
But when I try it in visual studio can I find /api/messages
Can anyone help me please?
Here is the test connection!
http://pastebin.com/2VsQGwJx

/api/messages refers to the controller path in your project. Are you using the C# or the Node builder? You should be able to find the controller in Visual Studio. This does not exist as a filesystem path.


ADBDEV-4908-51: Remove dependency to system calls for memory allocation in refint and regress_gp

Remove dependency to system calls for memory allocation in refint and regress_gp
Failures in allocations could lead to crashes with NULL pointer
dereferences . Memory context TopMemoryContext is used instead to keep
alive the plans allocated in the session. A more specific context could
be used here, but this is left for later.
This is backport from postgres/b0b61963866 commit for refint file.
Also logic of this commit was applied to regress_gp file.

Did anything change from the previous version of this patch?

Did anything change from the previous version of this patch?

yes, I changed realloc to repalloc in second commit

Can you please paste a diff between the previous patch and this one in ```diff block here?

Can you please paste a diff between the previous patch and this one in ```diff block here?

sure
diff 37c0da527153c78b25bf8eb1518e8c303c3b8f9a.diff ffa3f83baaac3eb9f94ffb2e1b105eca4d0ede89.diff
2c2
< index 1f8321129d67..2f4641f29eeb 100644
---
> index 1f8321129d67..988a9a0d2252 100644
52a53
> -		*eplan = (EPlan *) realloc(*eplan, (i + 1) * sizeof(EPlan));
54c55
<  		*eplan = (EPlan *) realloc(*eplan, (i + 1) * sizeof(EPlan));
---
> +		*eplan = (EPlan *) repalloc(*eplan, (i + 1) * sizeof(EPlan));


Add ability to delete scripts by name or delete all non-default scripts

Depends on the feature/delete-scripts branch in frodo-lib.

Merged into rockcarver main


linux/clang error: use of overloaded operator '==' is ambiguous

after fixing #380, I have another issue : https://gist.github.com/avilleret/80e0935a38542ca2e5f8
According to http://www.drdobbs.com/cpp/three-guidelines-for-effective-iterator/184401406 it is due to a poor implementation of STL and swapping value on each side of == should solve the issue.
But I don't know which value I have to swap...

I don't think this issue is still relevant since #380 is closed


Adding custom relays doesn’t seem to “stick”

If I add my self-hosted relay, it goes up into the list of relays but then no matter how I leave that screen (pressing the purple post button, or pressing the grey cancel button, or gesturing “back”), when I re-enter that relays screen my relay is not there anymore.
I also tried deleting one of the default relays and that change is also not saved as far as I can tell.
Is the save functionality on that screen yet to be implemented?

Hum.. this seems to be working. Which version are you on?

0.10.4 - under grapheneOS which maybe could be a thing?

Does graphene block saving encrypted preferences in the app? That could be it.

I don’t know specifically about that, but I do know that graphene has substantial hardening that includes where and how apps can write. Some of that stuff is optionable so I’ll play with the app settings a bit and see if I can make it work and report back here.

None of the hardening / memory / storage app options in graphene made any difference. I assume that after making changes on the relays screen, pressing the “post” button in the upper right is the correct way to save those changes (let me know if that’s wrong).
I tried clearing the app cache and app storage and starting over from scratch but the same behavior occurs.
Another data point: the app does not forget my private key which I guess from the architecture notes it is poking into the android keystore.
In use, the app is accumulating both data storage and cache, so it’s not being blocked from storing stuff. Could there be an issue with the encryption and decryption?
I’m a long ways away from an Android dev and pretty allergic to Java. Anything I can do as a user to help debug this?

Not a graphene problem. It's happening with me too.
Video

@pjv
So the app doesn't allow you to log off? Or what do you mean by it doesn't forget your private keys?
When you press the log off button, it deletes the private key from the encrypted storage.

@vitorpamplona ahhh - sorry for the confusion. I can log off fine. I was just trying to say that the app doesn’t have any trouble saving some stuff - just doesn’t save changes to the relays.

@pjv it's working for me now on the latest version. Can you test to see if it's working now?

@greenart7c3 @vitorpamplona Yup, not only is it working, when I updated to 0.10.7 the relay I added previously showed up in the list of relays without my having to re-enter it. So it was there all the time and the screen not showing it to me must have been a cosmetic thing.
Thanks for Amethyst @vitorpamplona - it’s looking great.


Switch Auth call to use SSL

Received this email and was digging through our Hubot script to ensure everything would continue working. This appears to be the only instance where SSL is not being used.

As an Untappd API developer, we wanted to inform you that you will need to update your application to use our secure, HTTPS API endpoint (https://api.untappd.com). We will be discontinuing our standard HTTP API endpoint on 2/1/15. This will require you to update your code for your application to change the http:// protocol to https://.
After 2/1/15, your API key will no longer work over HTTP and return a 500 HTTP error. The security of the Untappd community is extremely important to us and this change will help keep things safer.
We recommend that you join our API Developer Group at http://untpd.it/apigroup for up the information about the API.
If you have any questions or concerns, please visit our API Developer group or http://help.untappd.com.
Thanks,
The Untappd Team

Thank you!

Worth noting that this also required a change to the port number being used to go over 443 for https instead of 80.
Published new version (0.3.0) including this fix and some other small style fixes.

Oh, cool. I didn't catch that.


Make certificate validation work again

ASN1.c lost an increment, leading to certificates being parsed with
the wrong value read as the key usages (leading to failures in some cases).
Re-apply from the original axtls sources.

@igrr, sorry but I broke the asn1 parsing when I removed compile errors 2 merges back.  This fixes it and now CACert test works properly.

@igrr Can you merge this PR?

Closes #59


Fix build warnings with custom Razor SDK

@pranavkm, were you looking at this? Were you able to repro it based on the sample I sent? Thanks!
C:\Users\username\Desktop>dotnet new blazor -o blazorapp2
The template "Blazor (standalone)" was created successfully.

Processing post-creation actions...
Running 'dotnet restore' on blazorapp2\blazorapp2.csproj...
<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.props(25,3)>: warning MSB4011: "<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props>" cannot be imported again. It was already imported at "<C:\Users\username\.nuget\packages\microsoft.net.sdk.razor\2.1.0-preview2-30230\Sdk\Sdk.props (18,3)>". This is most likely a build authoring error. This subsequent import will be ignored. [C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj]
<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.props(27,3)>: warning MSB4011: "C:\Users\username\.nuget\packages\microsoft.net.sdk.razor\2.1.0-preview2-30230\Sdk\Sdk.props" cannot be imported again. It was already imported at "C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj". This is most likely a build authoring error. This subsequent import will be ignored.
<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.targets(14,3)>: warning MSB4011: "<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.targets>" cannot be imported again. It was already imported at "<C:\Users\username\.nuget\packages\microsoft.net.sdk.razor\2.1.0-preview2-30230\Sdk\Sdk.targets (14,3)>". This is most likely a build authoring error. This subsequent import will be ignored. [C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj]
<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.targets(16,3)>: warning MSB4011: "C:\Users\username\.nuget\packages\microsoft.net.sdk.razor\2.1.0-preview2-30230\Sdk\Sdk.targets" cannot be imported again. It was already imported at "C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj". This is most likely a build authoring error. This subsequent import will be ignored.
<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.props(25,3)>: warning MSB4011: "<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props>" cannot be imported again. It was already imported at "<C:\Users\username\.nuget\packages\microsoft.net.sdk.razor\2.1.0-preview2-30230\Sdk\Sdk.props (18,3)>". This is most likely a build authoring error. This subsequent import will be ignored. [C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj]
<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.props(27,3)>: warning MSB4011: "C:\Users\username\.nuget\packages\microsoft.net.sdk.razor\2.1.0-preview2-30230\Sdk\Sdk.props" cannot be imported again. It was already imported at "C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj". This is most likely a build authoring error. This subsequent import will be ignored.
<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.targets(14,3)>: warning MSB4011: "<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.targets>" cannot be imported again. It was already imported at "<C:\Users\username\.nuget\packages\microsoft.net.sdk.razor\2.1.0-preview2-30230\Sdk\Sdk.targets (14,3)>". This is most likely a build authoring error. This subsequent import will be ignored. [C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj]
<C:\Program Files\dotnet\sdk\2.1.300-preview2-008315\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.targets(16,3)>: warning MSB4011: "C:\Users\username\.nuget\packages\microsoft.net.sdk.razor\2.1.0-preview2-30230\Sdk\Sdk.targets" cannot be imported again. It was already imported at "C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj". This is most likely a build authoring error. This subsequent import will be ignored.
  Restoring packages for C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj...
  Restoring packages for C:\Users\username\Desktop\blazorapp2\blazorapp2.csproj...
  Generating MSBuild file C:\Users\username\Desktop\blazorapp2\obj\blazorapp2.csproj.nuget.g.props.
  Generating MSBuild file C:\Users\username\Desktop\blazorapp2\obj\blazorapp2.csproj.nuget.g.targets.
  Restore completed in 443.31 ms for C:\Users\username\Desktop\blazorapp2

Just got around to looking at it. Like @rynowak said, the issue is that Microsoft.NET.Sdk.Web already has an implicit reference to Microsoft.NET.Sdk.Razor. Adding an additional Sdk reference to a specific version of the Razor Sdk produces the build warnings. Making the warnings go away would require changing the Web.Sdk to add some conditional import behavior. We could address that in preview2 if this is a scenario we want to support. Microsoft.NET.Sdk would have the same issue if it was explicitly imported along with Web.Sdk.
The alternative which is what I'd sort of originally designed before the advent of Sdk resolvers was to replace the Sdk reference with a PackageReference to Microsoft.NET.Sdk.Razor package
<PackageReference Include="Microsoft.NET.Sdk.Razor" Version="2.1.0-preview2-30230" PrivateAssets="All" />. This should use the right Razor Sdk and you wouldn't see the warning.
cc @vijayrkn

OK great - thanks! I'll change the templates to use PackageReference for that.

Wanted to confirm something - are you going to require the 2.1.0-preview2 sdk? Referencing the package by itself would not work if you're targeting the RTM (2.0.0) sdk.

For our 0.1.0 release we can only require a .NET Core SDK version that has shipped in some way. .NET Core 2.0 SDK would be ideal. Requiring 2.1 Preview1 would be fine. Requiring 2.1 Preview2 doesn't work, because it hasn't shipped yet.

Ok. So having it specifically import the Sdk, the way it's currently doing is the only way to make this work. The PackageReference doesn't help with shipped Sdks.

.NET Core 2.0 SDK would be ideal.

This will not be possible. It has to be preview1 or newer because that's the version that knows how to acquire SDKs via nuget.

Preview1 is fine. How should acquisition of the Razor SDK work for 0.1.0? Right now our templates pull packages from MyGet, but typically for an official preview we pull from NuGet. Presumably the version of the Razor SDK we need isn't on NuGet yet, correct?

The Razor SDK that has all of the features we need will ship in preview2. Beyond that, I don't have a lot of clarity to offer you. This work all depends on other things that are being worked on.

@Eilon @DamianEdwards Could we push a preview1 version of the Razor SDK to NuGet in advance of shipping preview2?

I leave it to @DamianEdwards . I have no particular issue with it, but I'd like to understand in technical terms what we would have to do to make that happen.

@pranavkm Am I understanding correctly then that the <PackageReference> workaround isn't a viable way to make all the build warnings disappear? Can you propose any other way we can avoid all those build warnings?

If you're referencing the preview1 Sdk, you wouldn't see the warning. Since that seems to be the Sdk we're attempting to target, the template in it's current format should work. Once preview2 Sdk becomes available, we'd tell users to install it and remove the explicit reference to the Razor Sdk. Does that help?

@pranavkm I'm not doing a great job of understanding this. Could you suggest what you think we should change in the code, for example as a PR?

Reopening. Although the warnings aren't present when you build with Korebuild, they are still present when you build an actual Blazor app outside this repo.
@pranavkm Any chance you could look at this further? If you know what's going on, are you able to suggest a specific change to the code (either in Blazor itself, or in the project templates) that eliminates the slew of warnings? Or is there some specific version of the .NET SDK that people need to install (I'm using 2.1.300-preview2-008322 and do get the warnings)?
If you want a repro case, you can use the same project I emailed to you before, optionally updating the Blazor package references to an up-to-date version such as 0.1.0-preview1-10092.

This is now resolved for the preview1 SDK. There's a separate issue (#273) for the equivalent for preview2.

Preview1 is fine. How should acquisition of the Razor SDK work for 0.1.0? Right now our templates pull packages from MyGet, but typically for an official preview we pull from NuGet. Presumably the version of the Razor SDK we need isn't on NuGet yet, correct?

Hi, it looks like you are   posting on a closed issue/PR/commit!
We're very likely to lose track of your bug/feedback/question unless you:

Open a new issue
Explain very clearly what you need help with
If you think you have found a bug, include detailed repro steps so that we can investigate the problem.


⚠ Bofrost.be has degraded performance

In 741cfdd, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 997 ms

Resolved: Bofrost.be performance has improved in fa9a0ac.


fix: fix observe when receiving block2 response

This PR incorporates the suggested change by @Thousif-khan and should fix #336.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 94.506%

Files with Coverage Reduction
New Missed Lines
%

lib/server.ts
2
86.93%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
8679

Relevant Lines:
9085

💛  - Coveralls

I think we should probably merge #344 first (which addresses some more fundamental observe issues) and see afterwards if this PR is still needed.

Ok, I release a 1.0.8 with #34 in and then we test again

Ok, I release a 1.0.8 with #34 in and then we test again

Awesome, thank you :)

Hmm. Not sure if the additional if check changed anything?

Will merge and release tonight. Sorry for the delay


Getting device info and pwning

nothing happens after that the device just reboots into ios
command used ./sshrd.sh 9.3.5
iphone 5s

try to create with ios 12 or 11
if u got problem u can contact me
t.me/ethhab


Error with strictNullChecks when destructuring and renaming

TypeScript Version: 2.7.0-dev.20171126 and 2.6.2
Code
Similar to #9341, when destructuring and renaming, the bug resurfaces.
const a: { x?: number; } = { };
let y: number;
({ x:y = 1 } = a); // error TS2322: Type 'number | undefined' is not assignable to type 'number'.

const a: { x?: number; } = { };
let { x = 1 } = a;
let y: number = x; // ok, x has type 'number'

Expected behavior:
No error
Actual behavior:
test.ts(3,6): error TS2322: Type 'number | undefined' is not assignable to type 'number'.
Type 'undefined' is not assignable to type 'number'.

This was just recently fixed in 4.8 by #41042. I won't add a test; the one in the PR is effectively identical.


Codi 🐶

Welcome Codi! 🐶
I have replaced Jest with the lightweight test framework Codi.
Codi is a lightweight JavaScript test framework that allows you to write and run tests for your JavaScript code. It provides a simple and intuitive API for defining test suites and test cases, making it easy to ensure the correctness of your code. ✨

You can refer to the README.md on the Codi package for the different assertions built into Codi.

I have also included a new Roles test which will need to be updated in #1185.

To run the tests locally you will just need to execute npm test which will run codi against the tests directory.

Codi working in actions

Works with failing tests.


Is there a way to add a twitter feed (or any other html snippet) to the subtitle field of post widget

Would it be possible to add the generated html snippet from twitter just in the subtitle field of recent post widget?
I mean, I think a clean way to include it in the page would be to put it at the left column, which in this widget is mostly blank.
Thanks

The subtitle is a Markdown field for writing a subtitle. If you would like to put something else there, then you can create your own widget for that purpose - refer to the docs on creating widgets.


Veri split

Modify the Experiment API to allow for excluding certain keys. Also create a deterministic helper function that splits based on the hash of the key

Usage:
from functools import partial
from pelops.utils import train_test_key_filter

eg_train = ExperimentGenerator(dataset,
                               CAMERAS,
                               ITEMSPERCAMERA,
                               DROPPED,
                               YRANDOM,
                               key_filter=partial(train_test_key_filter, split="train"))

Codecov Report

Merging #85 into master will decrease coverage by 0.91%.
The diff coverage is 10%.

@@            Coverage Diff             @@
##           master      #85      +/-   ##
==========================================
- Coverage   87.73%   86.82%   -0.92%
==========================================
  Files          29       29
  Lines        1672     1692      +20
  Branches      223      229       +6
==========================================
+ Hits         1467     1469       +2
- Misses        177      195      +18
  Partials       28       28

Impacted Files
Coverage Δ

pelops/utils.py
44.32% <10%> (-8.92%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 15eb35f...aa4629b. Read the comment docs.


[Bug]: Crash on launch when using ViaVersionPlus

Here the log with ViaFabricPlus
crash.txt
and here without
working.txt
ViaFabricPlus v3.0.6
Essential Client v1.4.1
Carpet Mod v1.4.128+v231205
Essential Client (not Carpet Mod) is causing the problem.

Duplicate of #125


Add the implementation for the optimal use case of creating a customer

Many thanks for contributing to this project!
PR Checklist
Please fill in the appropriate checklist below (delete whatever is not relevant). These are the most common things requested on pull requests (PRs).

[x] This comment contains a description of changes (with reason)
[ ] Referenced issue is linked
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] Documentation in docs is updated
[x] CHANGELOG.rst is updated

Description of changes
Connected and implemented classes required for creating a customer in the database from the GUI of qoffer-2
Technical details
Set up the right references between the classes, please check our architecture diagram to verify the classes are connected correctly

 Implement optimal use case (customer creation)


Wrong method body is shown

This might be a duplicate. When a method is expanded in a Coder, sometimes a different method is shown.

This should have been addressed in the meantime.


Increase the size of MOF generation backlog

Be more aggressive about ensuring we have MOFs that are ready to run

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 41.479%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
4089

Relevant Lines:
9858

💛  - Coveralls


About publishing project

Since the requirement of my project, I need some functions like change scan parameters, change connect parameters and connect cancel..., but I can't test them on OS X, so I think you may not accept my pull request. Therefore I fork your noble project to my github and add some functions that I need in my project. May I publish this modified project to npm?
Thanks.

@hedywings thank you for contacting me about this. Do you absolutely need to publish your module to npm?
If you do not plan to maintain your fork, I would prefer it was not published to npm. For example, noble-nan a fork of noble was published about a year ago and has not received any updates, it also shows up when you search for noble on npm.
A few options:

Refer to your fork on Github when using npm/package.json: npm install --save hedywings/noble.

Use a scoped package name on npm: http://blog.npmjs.org/post/116936804365/solving-npms-hard-problem-naming-packages - I believe you will have to modify the name in package.json to be @hedywings/noble.

Let me know what you think. Again thanks for brining this up with me.

Thank you for provide options for me, I don't even know these methods!!
After consideration I have decided to adopt the first approach to refer my fork!
Thanks a lot~


PromptOptions should be QuestionOptions

We recently renamed prompt() to question() in #12
But the interface is still PromptOptions
The idea is to rename the interface to QuestionOptions to match the new function


feat :  added tries implementation using typescript

hi, @appgurueu , I removed redundant comments and package-lock.json file from my PR, please have a look. also, I document isPrefixMatch flag variable in the form of a comment, please have a look. If further modification needs to be done, let me know.
thanks for figuring out my mistakes and reviewing my PR

Hi @raklaptudirm, please review my PR.

Your tests are failing. Also undo the deletion of the package-lock file.

hi @raklaptudirm, I updated my PR

Hi @appgurueu  which changes i need to undo?

Hi @raklaptudirm, I can see all checks have passed successfully

You need to undo the deletion of the package-lock.json file.

Hi @raklaptudirm, I added again package-lock.json file

Add the file without changes, please.

hi @raklaptudirm  I added package-lock.json without any changes. just like present in master branch

hi @raklaptudirm, my PR was approved by @appgurueu. please review my PR so that I can able to merge my PR

Please be patient. Rak will get to review your PR when he has time.


Make it clear that the Approval Stage is clickable

What would you like to be added:
Why is this needed:
/label area/web

Staled!


[FORMAT]Where is the specific python format file?

I noticed that .style.yapf and .pylintrc exist here, but there are still tons of problems with using this format file. like Missing function or method docstringPylint[C0116:missing-function-docstring] Constant name "version" doesn't conform to UPPER_CASE naming stylePylint[C0103:invalid-name] etc. . Could you explain it, plz ?

the IDE is vscode I used, or, which extensions you are using, if you teams also use vsc

I saw there are two linter resource file(flake and pylint), which one is correct ? or both all

@loadams thanks for your explaination. So you aren't using some plugin or extension like vscode format which can real-time format your modification, just postprocess by command line like. In addition, it seems the .pylintrc isn't used anywhere since there isn't a pylint hook in pre-commit yaml file.


Release name for 0.10.x series

Please make a release one of these days, as we've fixed a crash bug.
(and yes, I misspelled extravaganza :stuck_out_tongue: )

Hahaha I hate you

Grudging Gpproval


[Issue]: Create Datadog Dashboard For Arpa Reporting Performance

Why is this issue important?
Multiple users want to follow and understand the reporting performance. This will help determine the prioritization of reporting fixes. A dashboard will help simplify that process. Datadog is an easy-to-use platform, but finding the relevant information quickly for arpa reporting may be difficult and time consuming.
Current State
Data such as logs and traces are recorded in Datadog. Users must go through Datadog on their own to correlate events.
Expected State
A member of the team will be able to access a dashboard page on Datadog to quickly and easily understand and correlate the logs and traces.
Implementation Plan
This may not need any code changes. This Jira is primarily a placeholder for assigned work.
Relevant Code Snippets
No response

Closing this as it is done with the ARPA Reporting Dashboard in Datadog


Inconsistent naming found in SLAM: attribute FrameInfo frameData

When I was learning how to use FrameDataAssember class, I found this:
interface TrackingResult {
  readonly attribute TrackingAccuracy accuracy;
  readonly attribute float[] cameraPose;
  readonly attribute FrameInfo frameData;
};

DonnaWuDongxia:
The type if FrameInfo and the attribute name is frameData. What's your concern? Do you advising to change frameData to frameInfo?

Invalid, the type has been changed to FrameData. @kenny-y @haoyunfeix


[SourceKit] Initialize pointer as nullptr to fix a crash. rdar://2895…

@swift-ci Please smoke test and merge


Tesla restricting api request frequency, leading to multiple malfunctions in Teslamate

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Teslamate cannot fetch vital data from Tesla servers due to Tesla has restricted its api query frequency.
Expected Behavior
Teslamate should fetch data normally from Tesla servers
Steps To Reproduce
Just simply boot the teslamate services
Relevant log output
teslamate-1  | 2024-06-16 07:14:36.061 [info] GET https://owner-api.vn.cloud.tesla.cn/api/1/vehicles/XXXXXXXXXXXXXXX/vehicle_data -> 429 (263.169 ms)
teslamate-1  | 2024-06-16 07:14:36.061 [warning] TeslaApi.Error / :too_many_request 2725
teslamate-1  | 2024-06-16 07:14:36.062 car_id=2 [error] Too many request / Retry after 2725 seconds

Screenshots
N/A
Additional data
N/A
Type of installation
Docker
Version
1.29.2-dev

See #3957


Test for windows support of MTU 1500 from previous 1460

Since changing this test would likely break all of the linux CIT tests so closing the PR.


AI proxy test: start and refund conversation

This addition generates the conversation id  and call the Fungible Token contract to start the conversation from the frontend javascript code. Also the refunding process is now initiated from the frontend. Both transactions are submitted using function access keys ( not full access keys ).
The full flow is now like this:
sequenceDiagram
    participant User
    participant Contract
    participant AIService

    User->>Contract: call_js_func(start_ai_conversation, conversation_id_hash)
    Contract->>Contract: ft_transfer_internal(user, AIService, amount)
    Contract->>User: conversation_id_hash and deposit registered

    User->>AIService: Initiate AI request with conversation_id
    AIService->>Contract: Check deposit for conversation_id
    Contract->>AIService: Confirm deposited tokens

    AIService->>User: Provide AI-generated content
    AIService->>AIService: Track spent AI tokens
    User->>AIService: Initiate refund for conversation_id
    AIService->>User: Sign message with unspent tokens

    User->>Contract: call_js_func(refund_unspent, {signature, refund_message})
    Contract->>Contract: Verify signature
    Contract->>Contract: Process refund

    Contract->>User: Return unspent tokens

Here is the video generated from the playwright test running:
https://github.com/user-attachments/assets/1db3fa1a-df1b-4d73-97a2-0d1888c21fdf

@race-of-sloths include

@petersalomonsen Thank you for your contribution! Your pull request is now a part of the Race of Sloths!
Weekly streak is on the road, smart strategy! Secure your streak with another PR!

Current status: waiting for scoring
We're waiting for maintainer to score this pull request with @race-of-sloths score [0,1,2,3,5,8,13] command. Alternatively, autoscoring [1,2] will be applied for this pull request
What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow
For contributors:

Tag @race-of-sloths inside your pull requests
Wait for the maintainer to review and score your pull request
Check out your position in the Leaderboard
Keep weekly and monthly streaks to reach higher positions
Boast your contributions with a dynamic picture of your Profile

For maintainers:

Score pull requests that participate in the Race of Sloths and receive a reward
Engage contributors with fair scoring and fast responses so they keep their streaks
Promote the Race to the point where the Race starts promoting you
Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

For contributors

Include a PR: @race-of-sloths include to enter the Race with your PR

For maintainers:

Invite contributor @race-of-sloths invite to invite the contributor to participate in a race or include it, if it's already a runner.
Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called

🥁  Score it!
@petersalomonsen, please ask your peers to score the PR using @race-of-sloths score [1/2/3/5/8/13].
If no scoring is provided within 24 hours, this PR will be scored as 1 🦥

@race-of-sloths score 8

⏰ Scoring closed
24 hours have already passed since the merge


Support missing charsets

Feature Request
MySQL supported charsets: https://dev.mysql.com/doc/refman/8.0/en/charset-charsets.html
parser supported charsets: https://github.com/pingcap/parser/blob/master/charset/charset.go#L55-L61
I get a parse error if I use unsupported charset:
CREATE TABLE `message` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `msg` text DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=euckr;

Error message:
[parser:1115]Unknown character set: 'euckr'

Hi, thanks for reporting!
BTW, do you want "euckr" to be supported by TiDB, or just the parser(able to parse it, but reports an error in TiDB server)?

@lechuckroh hi, do you have any interest to contribute? you can join the slack of the SIG channel(sig-sql-infra) via: https://slack.tidb.io/invite?team=tidb-community&channel=sig-sql-infra

@bb7133
I'm using just the parser in my application.
Will TiDB have any problem if new charset is added to parser only?

Got it!
Probably we need additional check for TiDB but it should be simple and reasonable.


"No ElasticSearch Node Available"

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[ ] elastic.v2 (for Elasticsearch 1.x)
[x ] elastic.v3 (for Elasticsearch 2.x)
Please describe the expected behavior
NewClient(elastic.SetURL("http://:9200")
would correctly generate a new Client object connecting to the node
Please describe the actual behavior
"no ElasticSearch node available"
Any steps to reproduce the behavior?
elastic.NewClient(elastic.SetURL("http://:9200")

Does it work with "http://<IP_ADDRESS>:9200"?

What does curl 'http://:9200/_nodes/http?pretty' return? Because Elastic uses a process called Sniffing to determine the other nodes of the cluster. Maybe they're unavailable?

Please respond to the issue if the question remains. Otherwise I'll close the issue. Thank you.

I apologize for the delay. I made a mistake in formatting the markdown here.
The issue is when I do something like elastic.NewClient(elastic.SetURL("http://someaddresshere:9200"))
A curl to that address works just fine, however it tells me that no elastic search node is available still.

Can you please try what I wrote in the 2nd comment?

elastic.NewClient(elastic.SetURL("http://<IP_ADDRESS>:9200")) works

What does curl 'http://:9200/_nodes/http?pretty' return?

{
"cluster_name" : "nicolaifsf-dev",
"nodes" : {
"e7123kDbSdmTdB-j3YV5iQ" : {
"name" : "nico_node01-dev",
"transport_address" : "<IP_ADDRESS>:9300",
"host" : "<IP_ADDRESS>",
"ip" : "<IP_ADDRESS>",
"version" : "2.3.3",
"build" : "218bdf1",
"http_address" : "<IP_ADDRESS>:9200",
"http" : {
"bound_address" : [ "[fe80::1]:9200", "[::1]:9200", "<IP_ADDRESS>:9200" ],
"publish_address" : "<IP_ADDRESS>:9200",
"max_content_length_in_bytes" : 104857600
}
}
}
}

I ended up using SimpleClient and it worked, however I just thought I should let you know that I was having some issues with NewClient. Are there any major differences between the two that could have been the root cause?

SimpleClient simply disables a few things like automatically finding new nodes added to your cluster by the Sniffing procedure I linked to above. You can disable sniffing via options in NewClient, as described in the Wiki.
Not sure what's wrong with your setup. Cluster output is looking good, sniffing should pick up the setting in http_address.

Ah well, thanks for your help!

I have the same issue, directly using CURL to my node on localhost works, including the _nodes call mentioned above.
I use SetSniffer(false) and it all started working. What information can I provide that would help with debugging?

This problem is most probably due to Elastic picking up the address returned by Nodes API, which simply isn't routable. This is e.g. the case for ES running inside a Docker container. Does it work with sniffing disabled? Refer to the wiki for details.

Am 17.09.2016 um 00:17 schrieb arglucas<EMAIL_ADDRESS>I have the same issue, directly using CURL to my node on localhost works, including the _nodes call mentioned above.
I use SetSniffer(false) and it all started working. What information can I provide that would help with debugging?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

What is the output from the Nodes API call mentioned earlier?

Am 17.09.2016 um 00:17 schrieb arglucas<EMAIL_ADDRESS>I have the same issue, directly using CURL to my node on localhost works, including the _nodes call mentioned above.
I use SetSniffer(false) and it all started working. What information can I provide that would help with debugging?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Same issue here.
I do some tests with two machines in one LAN. And they can ping each other well.
ES(PC1)     GoProgram(PC2)
I tried put Goprogram on PC1 and PC2.
I got "no ElasticSearch node available" no matter where I put go program or SetSniff(false) until I change to elastic.SimpleClient().
I do curl http://localhost:9200/_nodes/http?pretty' on PC1
{
  "_nodes" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "cluster_name" : "testcluster",
  "nodes" : {
    "wsu6A6VUSSyAWTfVu-S0gg" : {
      "name" : "node1",
      "transport_address" : "<IP_ADDRESS>:9300",
      "host" : "<IP_ADDRESS>",
      "ip" : "<IP_ADDRESS>",
      "version" : "5.0.0",
      "build_hash" : "253032b",
      "roles" : [
        "master",
        "data",
        "ingest"
      ],
      "http" : {
        "bound_address" : [
          "[::]:9200"
        ],
        "publish_address" : "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes" : 104857600
      }
    }
  }
}

I notice that http bound address  "[::]:9200"
So, I changed network.host from <IP_ADDRESS> to the exact IP address of PC1 - <IP_ADDRESS>.
And curl http://<IP_ADDRESS>:9200/_nodes/http?pretty' which gave me
{
  "_nodes" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "cluster_name" : "testcluster",
  "nodes" : {
    "wsu6A6VUSSyAWTfVu-S0gg" : {
      "name" : "node1",
      "transport_address" : "<IP_ADDRESS>:9300",
      "host" : "<IP_ADDRESS>",
      "ip" : "<IP_ADDRESS>",
      "version" : "5.0.0",
      "build_hash" : "253032b",
      "roles" : [
        "master",
        "data",
        "ingest"
      ],
      "http" : {
        "bound_address" : [
          "<IP_ADDRESS>:9200"
        ],
        "publish_address" : "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes" : 104857600
      }
    }
  }
}

But NewClient(elastic.SetURL("http://<IP_ADDRESS>:9200")) still not work. Any suggestion?

@jairwen Which version of elastic are you using? v2, v3 or v5?

I am using v5.
curl localhost:9200
{
  "name" : "node-1",
  "cluster_name" : "dnscluster",
  "cluster_uuid" : "OS9mmFYmRLC2gUklA3WrcA",
  "version" : {
    "number" : "5.0.0",
    "build_hash" : "253032b",
    "build_date" : "2016-10-26T05:11:34.737Z",
    "build_snapshot" : false,
    "lucene_version" : "6.2.0"
  },
  "tagline" : "You Know, for Search"
}

@jairwen Which version of elastic are you using? v2, v3 or v5?

@jairwen Yes, that's Elasticsearch 5.0. But are you using elastic.v5? What does this little program print for you?
package main

import (
	"log"

	elastic "gopkg.in/olivere/elastic.v5"
)

func main() {
	_, err := elastic.NewClient()
	if err != nil {
		log.Fatalf("Connect failed: %v", err)
	}
	log.Print("Connected")
}

Oh! my bad. Sorry for missing the release of .v5. I still use the .v3 got earlier. works like a charm

No worries... you're welcome. It'll probably be FAQ issue no. 1 :-)
The problem with the sniffing process (and hence the "no ElasticSearch node available" error) is that Elasticsearch changed the return structure of the Nodes Info API at least 4 times. :-(

@mahmoudhossam Do you have a reproducible test case for me?

Unfortunately, no.
I'd be happy to supply more information when it happens again, but I'm not sure what causes that exactly.

Same issue here:
curl http://localhost:9200/_nodes/http?pretty
{
  "_nodes" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "cluster_name" : "log",
  "nodes" : {
    "Bi1yAbQ0Tv60MwC9sVpfzw" : {
      "name" : "Bi1yAbQ",
      "transport_address" : "<IP_ADDRESS>:9300",
      "host" : "<IP_ADDRESS>",
      "ip" : "<IP_ADDRESS>",
      "version" : "5.0.2",
      "build_hash" : "f6b4951",
      "roles" : [
        "master",
        "data",
        "ingest"
      ],
      "http" : {
        "bound_address" : [
          "[::]:9200"
        ],
        "publish_address" : "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes" : 104857600
      }
    }
  }
}

ES running in Docker container:
$ elktail --url http://localhost:9200
ERROR: Could not connect Elasticsearch client to http://localhost:9200: no Elasticsearch node available.

I use ES v5, it is this error: #13 ?

This is the most frequently asked question so I've dedicated a Wiki page to
it:
https://github.com/olivere/elastic/wiki/Connection-Problems#how-to-figure-out-connection-problems
The node publishes at <IP_ADDRESS>:9200. Can you connect to that from the
outside?
There's two ways out of this:
Configure your clients so that they're available from the clients outside,
or disable sniffing.
On 4 December 2016 at 20:38, Stéphane Klein<EMAIL_ADDRESS>wrote:

Same issue here:
curl http://localhost:9200/_nodes/http?pretty
{
"_nodes" : {
"total" : 1,
"successful" : 1,
"failed" : 0
},
"cluster_name" : "log",
"nodes" : {
"Bi1yAbQ0Tv60MwC9sVpfzw" : {
"name" : "Bi1yAbQ",
"transport_address" : "<IP_ADDRESS>:9300",
"host" : "<IP_ADDRESS>",
"ip" : "<IP_ADDRESS>",
"version" : "5.0.2",
"build_hash" : "f6b4951",
"roles" : [
"master",
"data",
"ingest"
],
"http" : {
"bound_address" : [
"[::]:9200"
],
"publish_address" : "<IP_ADDRESS>:9200",
"max_content_length_in_bytes" : 104857600
}
}
}
}
ES running in Docker container:
$ elktail --url http://localhost:9200
ERROR: Could not connect Elasticsearch client to http://localhost:9200: no Elasticsearch node available.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/olivere/elastic/issues/312#issuecomment-264725479,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIOwFZKm8U6Uj9w-piNPLnpBxJbidRbks5rExa4gaJpZM4I9PXB
.

Just for the record: I think Amazon Elastic search does the load balancing to the node itself and that discovering nodes does not return any transport, despite the fact that several nodes are available. Disabling sniffing seems to be the right option in that case.
I hope this helps.

Also affected by this issue. I am using:
package main

import (
	"fmt"
	"log"
	"net"
	"os"

	"gopkg.in/olivere/elastic.v3"
)

func main() {
	if len(os.Args) < 2 {
		fmt.Fprintf(os.Stderr, "ERROR: no Elasticsearch hosts specified\n")
		os.Exit(1)
	}
	args := os.Args[1:]
	for _, arg := range args {
		r, err := net.LookupHost(arg)
		if err != nil {
			fmt.Fprintf(os.Stderr, "ERROR: %v\n", err)
			os.Exit(2)
		}
		fmt.Fprintf(os.Stdout, "%q resolved as: %v\n", arg, r)

		// now perform Elasticsearch-specific ping
		es, err := elastic.NewSimpleClient(elastic.SetURL(arg))
		if err != nil {
			log.Fatalf("error creating elastic client to %q: %v", arg, err)
		}

		_, err = es.IndexNames()
		if err != nil {
			log.Fatalf("error fetching indices from %q: %v", arg, err)
		}
	}
}

Using SetSniff(false) doesn't change anything.
This the nodes output:
{
  "cluster_name" : "es.example.com",
  "nodes" : {
    "ECBFak3BSuaeNjiwzGziQA" : {
      "name" : "es-1.example.com",
      "transport_address" : "<IP_ADDRESS>:9300",
      "host" : "<IP_ADDRESS>",
      "ip" : "<IP_ADDRESS>",
      "version" : "2.4.3",
      "build" : "d38a34e",
      "http_address" : "<IP_ADDRESS>:9200",
      "http" : {
        "bound_address" : [ "[::]:9200" ],
        "publish_address" : "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes" : 104857600
      }
    },
    "VpQlXfBHSa2qJSVMn4AIDg" : {
      "name" : "es-2.example.com",
      "transport_address" : "<IP_ADDRESS>:9300",
      "host" : "<IP_ADDRESS>",
      "ip" : "<IP_ADDRESS>",
      "version" : "2.4.3",
      "build" : "d38a34e",
      "http_address" : "<IP_ADDRESS>:9200",
      "http" : {
        "bound_address" : [ "[::]:9200" ],
        "publish_address" : "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes" : 104857600
      }
    },
    "6Wxtssi8S4a-Dl9W8QNYdQ" : {
      "name" : "es-3.example.com",
      "transport_address" : "<IP_ADDRESS>:9300",
      "host" : "<IP_ADDRESS>",
      "ip" : "<IP_ADDRESS>",
      "version" : "2.4.3",
      "build" : "d38a34e",
      "http_address" : "<IP_ADDRESS>:9200",
      "http" : {
        "bound_address" : [ "[::]:9200" ],
        "publish_address" : "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes" : 104857600
      }
    }
  }
}

@gm42 What are you using as arguments? Any chance you got bitten by this?

@olivere I am using an URL like this: http://es.example.com:9200
It's a DNS entry with 3 addresses within.

@gm42 Hmm... can't reproduce locally: Your example code works fine here.
What elastic does is try to find the http.publish_address (or https.publish_address) for each node, put it in a list, and keep watching that list, periodically looking for new entries and ignoring those that failed etc. You may not like that, but that's what all official clients do last time I checked.
Elasticsearch has changed the return structure of the /_nodes/http endpoint several times between the different versions (sometimes even in minor updates), hence I always get a heart attack when I read this error message ;-)
So if the executable performing HTTP requests is able to connect the 3 nodes http://<IP_ADDRESS>:9200, http://<IP_ADDRESS>:9200, and http://<IP_ADDRESS>:9200, then all should be fine.
If you're using containers, this inability to talk to each other is typically the problem with the "No Elasticsearch node available" error.

@olivere sorry for the noise. It was a docker usage problem. For reference, if you use docker run --env myenv.txt then your myenv.txt file cannot use double quotes.
Example of wrong configuration:
ES_URL="http://<IP_ADDRESS>:9200"

(Docker will pass the double quotes along)
Correct env:
ES_URL=http://<IP_ADDRESS>:9200

Just wanted to leave a comment here for anyone else who comes across this:
If you are using Amazon's AWS Elasticsearch service then you must turn sniffing off. The nodes are not routable and the ES url they provide does the routing for you.

If anyone else comes here with the same problem, make sure you have http:// as part of your connection URL. I just wasted a few hours on this.. :)

@viktornordling I'm sorry to hear. I changed this because Go 1.8 changed parsing URLs to be more strict (see this commit). Before that, you could use localhost:9200, but it's not a valid URL according to the spec, and Go 1.8 failes to parse that (or to be more precise: it doesn't do what you expect => The URL scheme will be localhost, not the host! Just try yourself).
If you want to help others, feel free to add a section to the connection problems page on the wiki.

Thanks for your response @olivere! Could we not raise an error if after the canonicilization we have 0 URLs?
It seems we currently insert the DefaultURL in this case, I'm not sure what would break if we change that behavior? I'm happy to create a PR, but I'd need to know how to deal with this tension. In the meantime, I'll update the docs.
Thanks for an awesome library btw!

Yes, I agree: Raising an error would be preferred.
I also think #510 would make underlying errors more transparent. You'd get an elastic.ErrNoClient error, but would have access to the underlying reason why that really happened.

FYI: In case of a connection problem, we now pass the underlying error in the error message as well.

Sorry, I'm newbie on go and elasticsearch...
Got "no ElasticSearch node available" too, using elasticSearch v.5.4.0 on docker.
After many attempt, I can make it work...
The different with previous configuration, is using Basic Auth (since elasticSearch already come with X-Pack).
I define new role and new user, but on call NewClient, I got this error and on log said something like
[2017-05-24T09:28:23,266] [transport] [access_denied]	origin_type=[rest], origin_address=[<IP_ADDRESS>], principal=[new_user], action=[cluster:monitor/main], request=[MainRequest]
In the end, I fix this by adding cluster "monitoring" to new_role, ex.
  "cluster" : [ "monitor" ],
  "indices" : [
    {
      "names" : [ "news*" ],
      "privileges" : [ "all" ]
    }
  ]
}'```

Is this the correct approach?

this issue really helped me. I'm using kubernetes and just experimenting at the moment. My nodes api returns the internal ip, i need to use the external. i added elastic.SetSniff(false) and 💥 it works

@rileytg That's true. But remember that when your nodes change, elastic won't find the new nodes. Disabling sniffing means: Keep the list of IPs I initially gave you, and don't care about updates in the cluster.

@kevin-cantwell I still have same issue with Elasticsearch service on AWS. Could you explain more details about this?

My elastic version is 6.X. And I use the example code form https://olivere.github.io/elastic/.
I get a error:
panic: health check timeout: Head http://<IP_ADDRESS>:9200: dial tcp <IP_ADDRESS>:9200: connectex: No connection could be made because the target machine actively refused it.: no Elasticsearch node available
Can you help me?

My elastic version is 6.X. I ran the example code from https://olivere.github.io/elastic/. I got a error:
panic: health check timeout: Head http://<IP_ADDRESS>:9200: dial tcp <IP_ADDRESS>:9200: connectex: No connection could be made because the target machine actively refused it.: no Elasticsearch node available
Can you help me?

@yuluopiaoyang Can you please try this first? Otherwise, disable sniffing.

use   elastic connection elasticsearch print   no Elasticsearch node available, help me!!!

@Single430 Can you try this first? Otherwise, disabling sniffing works most of the time.

$ curl -X POST MY_URL:9200/monitor/logs?pretty -d '{ "kind": "info", "message": "The server is up and running"}'
{
"_index" : "monitor",
"_type" : "logs",
"_id" : "AWJN01yPxa3T42gIpjPg",
"_version" : 1,
"result" : "created",
"_shards" : {
"total" : 2,
"successful" : 1,
"failed" : 0
},
"created" : true
}

_, err := elasticcli.NewClient(elasticcli.SetURL(elastic.Url))
if err != nil {
	panic(err)
}

panic: health check timeout: no Elasticsearch node available
goroutine 1 [running]:
main.main()
PATH/go/src/chat/src/main/main.go:28 +0x462
Process finished with exit code 2

Hey guys, I got this error recently and it waste me about 2 days to work out. Here is how I did, maybe helpful for you.
First of all, I use govendor to manage golang dependency. Since I use elasticsearch6.1.3, so I aim to get the latest version of elastic, which is v6. I do this in govendor : "govendor fetch github.com/olivere/elastic". But actually get vendor.json like this:
"package": [
{
"checksumSHA1": "JU+kcMNB8CPi7DJmxK5E3vpNxcg=",
"path": "github.com/olivere/elastic",
"revision": "eb69fbabfd6151d6c0f6d3d850d4f61edcff3763",
"revisionTime": "2016-10-08T09:19:33Z"
},
{
"checksumSHA1": "AmcqvKDAUGvVsrf8NDCQ/B8cMj4=",
"path": "github.com/olivere/elastic/uritemplates",
"revision": "eb69fbabfd6151d6c0f6d3d850d4f61edcff3763",
"revisionTime": "2016-10-08T09:19:33Z"
},
{
"checksumSHA1": "O5dZe+m70S7vbkgePsMLrUc86DA=",
"path": "gopkg.in/olivere/elastic.v2/uritemplates",
"revision": "2cd27b9ae892f6b4dd8dd6d73489797c99e9c6fa",
"revisionTime": "2018-05-17T14:35:08Z"
}
],
Which means I got elastic.v2 ??? Then I go to see the code in olivere/elastic/client.go:
const (
// Version is the current version of Elastic.
Version = "2.0.23"
// DefaultUrl is the default endpoint of Elasticsearch on the local machine.
// It is used e.g. when initializing a new Client without a specific URL.
DefaultURL = "http://<IP_ADDRESS>:9200"

}
It's true!!!
So there is a version mismatch between my elasticsearch(6.1.3) and elastic client(2.0.23).
I think mostly this problem is caused by version mismatch. You need to check client version(in olivere/elastic/client.go) and version of elasticsearch you actually use. In my case, I think there must be some error with go vendor, maybe it does not know the lastest version(6.0.0) of github/olivere/elastic. I decide to move to dep cause vendor hurt me!

@hzjiangjian Seems like an issue with govendor. Use dep if you can: It's doing the right thing (tm).

@olivere  That's right !  It works well with dep.

I ran into the same issue and even after setting elastic.SetSniff(false), I would still get "No active connection" errors.
Turned out that I also needed to set elastic.SetHealthcheck(false), because the Elasticsearch server (via elastic.io/found.io) did not respond to HEAD requests and as a result the connection was marked bad.

@thoellrich Interesting. We use Elastic Cloud (https://www.elastic.co/cloud) in one project, and we disabled neither sniffing nor health checks. This is a project hosted on Google Cloud, using a hosted Elasticsearch Cloud cluster. Everything just works. Can you get a bit more into detail?

@olivere - I guess I need to revise my statement above: the health-check indeed does not seem to make a difference in the test case I created at: https://gist.github.com/thoellrich/fbe650e8e23b78f866ff82034bcf75a4
For my Elastic Cloud server (AWS), I see the following output:
$ go run main.go --url="https://<username>:<password>@<xxx>.us-east-1.aws.found.io:<ppp>"
health=true, sniff=true - err=no active connection found: no Elasticsearch node available
health=true, sniff=false - version=6.2.4, version_err=<nil>, index_count=82, index_err=<nil>
health=false, sniff=true - version=6.2.4, version_err=<nil>, index_count=0, index_err=Get http://172.25.aaa.bbb:ccc/_all/_settings: dial tcp 172.25.aaa.bbb:ccc: i/o timeout
health=false, sniff=false - version=6.2.4, version_err=<nil>, index_count=82, index_err=<nil>

Not sure what I saw yesterday. I'll try to recreate that and if it fails again, will report back.

@thoellrich I'm not an expert on AWS: It's not related to AWS signing, is it? See this recipe which I tested against an Elasticsearch service on AWS a few weeks ago.

Thanks for the pointer and, no, this is certainly not the issue: request signing is only necessary if you talk to AWS's Elasticsearch service. I talk to an Elastic Cloud server which happens to be hosted in AWS. Confusing - I know :-)
This one compares/contrasts the two: https://www.elastic.co/blog/hosted-elasticsearch-services-roundup-elastic-cloud-and-amazon-elasticsearch-service

Oh, I see, you're hosting your own Elasticsearch cluster.
The key to make sniffing and health checks work is that the node IPs returned from the cluster must be routeable/accessible from your application. I often see people start their cluster in Docker and then use something like <IP_ADDRESS> or <IP_ADDRESS> in the connection URL, only to see the cluster returning private node IPs like 172.aaa.bbb.ccc, which are not routable from the host. When sniffing is enabled, the <IP_ADDRESS> is only the starting point when drilling into the cluster. It's using http://<IP_ADDRESS>/_nodes/http?pretty=true to retrieve information about the nodes and uses those IPs to try to connect to all nodes in a round-robin mode; that obviously fails if the IPs are not accessible from your application. It generally works well when e.g. your application lives inside a scheduler like Kubernetes, and your ES cluster lives there as well, so routing will succeed.

Sorry to have to correct you again: I'm not running those instances, Elastic Cloud does.
When you sign up with Elastic Cloud you can pick which cloud (AWS, GCP, Kubernetes) you want to be used for the instances (see https://www.elastic.co/cloud/elasticsearch-service). I have no control over the public and/or private IP address space used for them. But it makes perfectly sense that sniffing won't work for inaccessible IP addresses.

Oh well. I'm on vacation and just flying over the comments. I'm sorry.

Please, no need to be sorry at all. The package works as expected. I posted something that turned out to be a red herring. My turn to say sorry and wish you a nice vacation!

Solution One:
        client, err := elastic.NewClient(                 elastic.SetSniff(false),                 elastic.SetURL("http://<IP_ADDRESS>:9200"))
Solution Two:
        client, err := elastic.NewSimpleClient(                 elastic.SetURL("http://<IP_ADDRESS>:9200"))

Solution Three:
Configure network.host and/or network.publish_host in Elasticsearch properly (see e.g. here).

I fought with this problem for about 3 hours and finally tried the official package.
It worked first try: https://github.com/elastic/go-elasticsearch
Doesn't look super developed as it's only been out for a couple weeks, but works for what I need.

I got this error when I provided the bare URL i.e. without the prefix http[s]://, and when I added the same, it worked. The error no active connection found was misleading in this case. If in the current code, this error is supposed to happen all the time when a URL prefix is not specified, then probably this should be checked and a better error message should be displayed ("did you miss URL prefix http[s]//:?") or alternatively, append automatically. Thanks!

I am having the same problem. But, my elastic cluster is running in https://www.elastic.co/ (elastic as a service). When i run my service by docker, i got the error: no active connection found: no Elasticsearch node available, but when i run outside of docker (go run main.go) just work fine. Someone pass through this or have some ideia?
I tried some things thats was commented.
My elastic client configuration already set the sniff and health check to false.
client, err := elastic.NewClient(
		elastic.SetURL(url),
		elastic.SetBasicAuth(c.Username, c.Password),
		elastic.SetSniff(false),
		elastic.SetHealthcheck(false),
)

I have the same issue, directly using CURL to my node on localhost works, including the _nodes call mentioned above.
I use SetSniffer(false) and it all started working. What information can I provide that would help with debugging?

It works for me, thanks.

i have same issue, but i deploy es with docker; i get error "curl: (52) Empty reply from server"  when exec  curl 'http://localhost:9200/_nodes/http?pretty'


⚠ Bofrost.com has degraded performance

In 984f805, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1185 ms

Resolved: Bofrost.com performance has improved in 4c5ebb1 after 6 minutes.


XRE-14362: Adding properties to VAP plugins

Reason for change: Adding properties & events
to VAP plugins required by Premium apps
Test Procedure: check ticket
Risks: Low
Signed-off-by: Vinod Jacob<EMAIL_ADDRESS>

Changes requested in Thunder


HLint

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Скопируй изменения из ветки origin/hlint

Comments from Reviewable

a discussion (no related file):
Previously, cblp (Yuriy Syrovetskiy) wrote…
Скопируй изменения из ветки origin/hlint

?

Comments from Reviewable


Different shortcuts for single-line or multi-line suggestions

Is your feature request related to a problem? Please describe.
Usually I only want a single-line-suggestion (in most contexts it works better); but then sometimes I want a multiline suggestion (I have developed a gut-feeling for where it works and then it's really useful).
Describe the solution you'd like
Allow different shortcuts for different types of suggestions (e.g. single line for the normal-inline-suggestion shortcut), medium amount of lines (configurable) for custom shortcut b, large amount of lines for custom shortcut c.
Describe alternatives you've considered
None to be honest since the problem is that the multiline-suggestions are unreliable, so an automatism is most-likely also unreliable. Mode-switching via shortcut could be a possibility; but this requires the user to keep track of the current state in their mind which seems less comfortable.

Hey, do you have any suggestions for the shortcuts?

I think thats very opinionated; and it might be reasonable to not add a default shortcut (if someone wants to enable this feature, they have to provide a shortcut themselves)?
However, currently I use "⌥ /" for normal inline completion, so "⌥ / chord to ⌥ /" would feel natural (i.e. press "option + /" and then press "/" again).


added code for subtree of another tree

Fixes #1986
Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

please merge it sir @Ayush7614 @ravikr126


Not necessary restarts?

It it really necessary to restart the containers, even if there is no change in the certificates?
[2020-06-15T00:35:33+0000]: Clearing dumping directory
[2020-06-15T00:35:33+0000]: Dumping certificates
[2020-06-15T00:35:34+0000]: Certificate and key for 'mail.domain1.tld' still up to date, doing nothing
[2020-06-15T00:35:34+0000]: Certificate and key for 'mail.domain2.tld' still up to date, doing nothing
[2020-06-15T00:35:34+0000]: Certificate and key for 'mail.domain3.tld' still up to date, doing nothing
[2020-06-15T00:35:34+0000]: Trying to restart containers
[2020-06-15T00:35:34+0000]: Looking up container with name mailcowdockerized_postfix-mailcow_1
[2020-06-15T00:35:34+0000]: Found '2b8bf99aa16b'. Restarting now...
2b8bf99aa16b
[2020-06-15T00:35:37+0000]: Restarting container '2b8bf99aa16b' was successful
[2020-06-15T00:35:37+0000]: Looking up container with name mailcowdockerized_dovecot-mailcow_1
[2020-06-15T00:35:37+0000]: Found '0c93c377595b'. Restarting now...
0c93c377595b
[2020-06-15T00:35:43+0000]: Restarting container '0c93c377595b' was successful
[2020-06-15T00:35:43+0000]: Looking up container with name mailcowdockerized_nginx-mailcow_1
[2020-06-15T00:35:43+0000]: Found '95c7718b7f28'. Restarting now...
95c7718b7f28
[2020-06-15T00:35:47+0000]: Restarting container '95c7718b7f28' was successful
[2020-06-15T00:35:47+0000]: Container restarting process done.

Yep, it isn't. I'm sorry for that. I'll try to start working on it as soon as I can. :)

Pull request #11 was created to encounter this issue. Should be fixed with the next version: 👍

Fix has been merged. I'm sorry for the delay. I'm currently busy with some other stuff. I'll create a release later this day.
Thank you for reporting this issue. 👍


Migration to new project structure

Checklist:

[x] Initialize new project structure
[x] Migrate existing code to new project structure
[x] Generate code and manifests according to new structure
[x] Update tests
[x] Update make targets
[x] Build ocs-operator binary and image
[x] Generate unified bundle (CRDs, unified CSV and RBACs)
[x] Generate bundle image
[x] Generate Index image
[x] Fix CI

/retest ci/prow/ocs-operator-ci

/test ci/prow/ocs-operator-ci

Thanks @umangachapagain !
Overall the changes look good in general.
But there is a failure in the CI (e2e tests) and I am not sure, it might be related:
 Waiting for ClusterServiceVersion to become ready...
Timed out waiting for csv to become ready
Dumping Namespace openshift-storage as /tmp/artifacts/ns-openshift-storage.yaml
Dumping OperatorGroup oo-46sgq as /tmp/artifacts/og-oo-46sgq.yaml
Dumping CatalogSource oo-g9hft as /tmp/artifacts/cs-oo-g9hft.yaml
Dumping Subscription oo-2l682 as /tmp/artifacts/sub-oo-2l682.yaml
  Subscription oo-2l682 status state: AtLatestKnown
ClusterServiceVersion ocs-operator.v4.7.0 was created but never became ready
Dumping ClusterServiceVersion ocs-operator.v4.7.0 as /tmp/artifacts/csv-ocs-operator.v4.7.0.yaml
  ClusterServiceVersion ocs-operator.v4.7.0 status phase: Installing
  ClusterServiceVersion ocs-operator.v4.7.0 status message: installing: waiting for deployment ocs-operator to become ready: Waiting for rollout to finish: 0 out of 1 new replicas have been updated...
  ClusterServiceVersion ocs-operator.v4.7.0 status reason: InstallWaiting
error: failed to execute wrapped command: exit status 1
2020/12/22 17:28:55 Container test in pod ocs-operator-bundle-e2e-aws-optional-operators-ci-subscribe failed, exit code 1, reason Error

Looking at it.

Furthermore, I think the file bin/manager has been committed accidentally.

Removed it

Lastly, I would like to understand if this change would require changes in the downstream build configuration (due to changed binary paths or so ..).

No changes required AFAICT. I've modified most of the things to be backward compatible.

/override ci/prow/red-hat-storage-ocs-ci-e2e-aws


Add second author and live demo link

In this pull request I've:

Add a second author
Update live demo link using github pages

Great job Dani! Now our project is ready for an external review. Congratulations🎉🎉🎉


Update Scene Import to use Owner Field

Airflow needs to set the owner field for created scenes to the owner of the upload that kicked off the import/scene creation.

Also update all airflow tasks to use new owner field.


x/build: trybots should check all source files for license header

A common mistake when adding a new Go source file to the Go project is to omit the license header.
This means that a human has to point out the mistake every time, and for each file.
I think it makes sense to have the trybots do this instead. It'll save a bit of time and effort for reviewers, and help catch an easy mistake earlier in the review process for the author of the CL.
Thoughts?
/cc @bradfitz

This might be a better fit for the codereview plugin, which I believe already has a check that all Go files are gofmt-compliant.

That would be fine with me as well.  I suppose I haven't ever run into that check since my editor takes care of formatting for me.
Either way, I think some automation could be very helpful.

@ianlancetaylor, once we accept Github PRs, it's no longer a good assumption that all users use git-codereview. We want to build something like Google's Tricorder where bots leave comments on the CLs (in Gerrit) instead, so it doesn't matter which tool they used to send a change.

@andybons, this bug is about doing a Tricorder-style thing for Go, where gopherbot looks at pending CLs and runs plugins and drops review comments in Gerrit.
Start of work for it is in pending CL https://go-review.googlesource.com/c/build/+/38285

Dup of #18548


Navigation prop not passed to navigable components.

Current Behavior
Link to respository :
When the Button component is pressed on the first screen (DeckListView), the user should be able to navigate to the NewDeckView, because both views are part of the StackNavigator() call.  Instead the error "undefined is not an object (evaluating '_this3.props.navigation.navigate')" pops up.  Using console.log tests I see the props object passed to the DeckListView component is empty,  So is seems the cause of the error is that the navigation property is not being passed to the component, but why not?
Expected Behavior

I expected the components listed as screens in the call to StackNavigator() to receive the navigation prop and I expected to be able to call navigate() on the prop to allow my user to navigate to a new screen.

Your Environment

software
version

react-navigation
v 1.0.0-beta.15

react-native
v0.48.4

node
v6.11.0

yarn
v1.2.1

Well from my understanding in your App.js you are not rendering the Stack but instead return <DeckListView/>.
Change that to return the Stack and it will work.
Not an issue caused by the library.

@kelset Thank you!  Somehow this wasn't clear for me in the documentation.  At least it wasn't clear in Quick Start.

I am a bit confused, aren't you following a tutorial? Your repo says "This is the third project of the udacity React Nanodegree.".
That said feel free to submit a PR if you think that the wording in the Quick Start isn't clear enough.


Add splitted_url_query and splitted_referrer_query for better UTM/Query Params filtering

Describe the feature or enhancement
Many issues and discussions already asking the same thing, this feature request is meant to group them and therefore show the significant interest in this feature.
Exemple:
Being able to filter stats/metrics/events by campaign source.
URIs:
https://mysite.com/blog-1?utm_source=twitter&utm_medium=social&utm_campaign=feature-1
https://mysite.com/blog-1?utm_source=facebook&utm_medium=social&utm_campaign=feature-1
https://mysite.com/blog-1?utm_source=twitter&utm_medium=social&utm_campaign=feature-2
https://mysite.com/blog-1?utm_source=twitter&utm_medium=social&utm_campaign=feature-3

Right now we can only filter by all query params at the same time, and not by specific utm_campaign or utm_source.
Mentions of this feature:

https://github.com/umami-software/umami/issues/2086
https://github.com/umami-software/umami/issues/1850#issuecomment-1536359290
https://github.com/umami-software/umami/discussions/619#discussioncomment-6091104
https://github.com/umami-software/umami/issues/273#issuecomment-821990623
https://github.com/umami-software/umami/issues/845

We currently have a UTM report that will go out next release. It isn't exactly what your requesting since it won't filter from the dashboard, but it will give a general summary on UTM param vs views across a date range.

It's looking pretty neat, will give it a try!
It seems to fulfill the goal of tracking campaigns performances, so it might not be needed to implement my suggestion.


Make sure only /scanner/ is used

Right now we have /scanner and /scanner/. We should only have /scanner/.

I think this is already done in sonarwhal.com, I'm going to fix a link in the sonarwhal documentation.

In the analytics I can still see a few instances of /scanner/ thought. It could be just people hitting that url directly from links so maybe we should have a redirect in place for it as well.


node['bcpc']['node_number'] is not derived from cluster_def node_id

We have taken to setting node_id in cluster.txt, and some code relies on those node IDs.  Unfortunately, those node IDs are at no point copied into node objects, so older code that relies on node[:bcpc][:node_number] will get a bogus value derived from the MAC address.
This is particularly dangerous on Zookeeper clusters, where one value is used for the zoo.cfg cluster definition, and the other value is used for the myid file.
For now we can work around this issue by copying the values in chef-shell after chef installation but before cheffing nodes:
sudo chef-shell -z -o 'bach_hadoop_wrapper'

require 'cluster_def'
BACH::ClusterDef.new.fetch_cluster_def().map { |ss|
  nn = Chef::Node.load(ss[:fqdn])
  nn.normal[:bcpc][:node_number] = ss[:node_id]
  nn.save
}

At some point we need to really fix this.

This may have been an omission on my part, however it is also possible at the time of writing I mean to make sure all node number requests are serviced from the file.  Perhaps I should have documented this explicitly


Use ES6 features

Convert the codebase to use all the new ES6 features. Automated via:
$ lebab --transform arrow,for-of,arg-spread,obj-method,no-strict,obj-shorthand,let,template,default-param --replace ./lib/
$ eslint --fix ./lib/

Again, if the build passes we should be good :+1:

👍

Hmm so Node v4 errors with:

So it looks like node --use_strict doesn't work with Mocha, so I'm now using require('use-strict') in the example server.

That was a no-go either, now I'm trying mocha --require use-strict...

Ahhh now Node v4 doesn't support array-spread. I'll close this and trim it a little.


feat: provide better support for the underlying shells

As mentioned in a number of issues (#5, #9, #10, #11, #19, and more) inshellisense's current support for the underlying shell is incomplete and needs to be improved. Currently inshellisense merely passes each command to a new pty session with the same shell as the user's current shell or the selected shell via the -s/--shell flag. This will be change moving forward to a more robust solution that will support complex shell behaviors with aliases, custom prompts, and more. As a result, PRs adding new functionality to the ink implementation of the root command will not be merged as that code will be removed in the rewrite.
More updates will be added to this issue when available.

[x] implement isterm, a terminal layer that is capable of detecting a shell's input buffer via custom escape sequences in while passing through all the default behavior of the underlying shell #87
[x] implement the ui layer which shows the suggestions with the shell's output #90
[ ] improve shell inference capabilities
[ ] more to come...

implement the ui layer which shows the suggestions with the shell's output

By this, do you mean that inshellisense will not start a new pseudo shell session, and will instead add the suggestions onto the existing shell UI, similar to other command-line tools?

implement the ui layer which shows the suggestions with the shell's output

By this, do you mean that inshellisense will not start a new pseudo shell session, and will instead add the suggestions onto the existing shell UI, similar to other command-line tools?

It will start a long running psuedo terminal which it will then add suggestions too, so while a new shell session will be started, that session will be a fully functional shell, similar to starting a new terminal session in VSCode


Using jwtClient.authenticate() behind a proxy results in ETIMEDOUT error

I've been attempting to authenticate requests using the JWT client.
I've set up my request:
var google = require('googleapis');
var key = require('./config/key.json');

var proxy = {
    user: 'user',
    pass: 'pass',
    hostname: 'foobar.com',
    portnumber: '8080'
}

// Set up the proxy as per the documentation
google.options({
    proxy: `http://${proxy.user}:${proxy.pass}@${proxy.hostname}:${proxy.portnumber}`
});

// Scope to GA
var scope = 'https://www.googleapis.com/auth/analytics.readonly';

// Set up the client as per the documentation
var jwtClient = new google.auth.JWT(
    key.client_email,
    null,
    key.private_key,
    scope,
    null
);

// I try to get an access tokens, this is where it hangs.
jwtClient.authorize(function (err, tokens) {
    if (err) {
        // There is a long pause, followed by an error here
        console.log(err);
        return;
    }
    // some code
}

I've tracked the execution (through breakpoints) through the googleapi library and its dependencies, but nowhere do I see a mention of that proxy option I set above. The error logged to the console:
{
  Error: connect ETIMEDOUT <IP_ADDRESS>:443
    at Object.exports._errnoException (util.js:1026:11)
    at exports._exceptionWithHostPort (util.js:1049:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1085:14)
  code: 'ETIMEDOUT',
  errno: 'ETIMEDOUT',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 443
}

I've tried googling around, but I haven't seen anyone else with this exact issue. I apologize if there's some silly reason the request is timing out, but I really am at wit's end with this problem.

So after some more digging, I realized #336 offered some insight.
You can configure a proxy through HTTP_PROXY and HTTPS_PROXY environment variables. This is not desirable for everyone and I wish the following code just worked for all cases:
google.options({
    proxy: `http://${proxy.user}:${proxy.pass}@${proxy.hostname}:${proxy.portnumber}`
});


JBPM-4646 - Case management - get tasks for cases as stakeholder

depends on https://github.com/droolsjbpm/jbpm/pull/689
@krisv and here is its remote counterpart

jenkins retest this

+1


Local html imports not cached in Google Chrome.

Google Chrome is not caching my local html imports.

✔ Local and remote css's, scripts, ... are well cached.
✔ Remote html imports are well cached.
❌ It seems the issue is only for Local html imports.
Is this Polymer related issue ? Google Chrome issue ?
(Google Chrome Version 59.0.3071.115)

This is probably an issue with your local dev server. Polymer does not set any caching headers.

@TimvdLippe just realized that. thanks for your answer.

Okay great, good luck debugging!


Generic Cell integration failure with generalized tracers

Here's a case of generic failure of Cell integation for pretty standard inputs. It would be great if we could investigate what drives this. @vitenti @damonge
Failed_integr_Cl.pdf

@elisachisari did you try to create one of these directly as a WeakLensingTracer setting has_shear=False (see here)?

@elisachisari bumping David's above question here

ay, yes, sorry! I might have tried that in the past, but not for this example. I'll give it a go and report back.

Ok, this option does work for the same cosmology and alignment bias. I also tried changing the use_A_ia keyword and it still completes the calculation. Do we understand the internal difference between this and creating a generalized tracer? @damonge

@damonge thoughts on Elisa's question above?

OK, almost two years later, here's the answer: this line
transfer_b1 = (sf,bi1)

should be changed to
transfer_b1 = (sf[::-1],bi1[::-1])

Because scale factors need to be monotonically increasing.
I'm gonna try and either document this better or make CCL throw a more useful message.


Modified deviceinfo lib to create singleton without SingletonType template class.

It is done to avoid crash in SingletonList::Dispose() when any deviceinfo application ends.

Hi Neeraj,
We have in the mean time a different solution for this issue. You can ask Karthick if you are interested or we can discuss tomorrow in the team meeting.
Best, Marcel


[SPARK-35647] Merge contents and remove obsolete pages in User Guide section

What changes were proposed in this pull request?

Renamed import from databricks.koalas to pyspark.pandas
Renamed to_koalas -> to_pandas_on_spark
Renamed (Series|DataFrame).koalas -> (Series|DataFrame).pandas_on_spark
import pyspark.pandas as ks -> import pyspark.pandas as ps
Remane some dataframe name from kdf to sdf
Fix some broken links
Koalas -> pandas on Spark

Why are the changes needed?

Update pandas APIs on Spark in the User Guide section.
Does this PR introduce any user-facing change?

Yes, it adds new documentations.
How was this patch tested?

Pass the CIs.

Oh @pingsutw, this JIRA actually targets the higher level of structure reorginisation (I have been working on it).
The changes you proposed are a part of SPARK-35591 which @itholic is working on ...

Can one of the admins verify this patch?

@HyukjinKwon Okay, no problem. Let's close it.


Multiplatform support for BigDecimal/BigInteger

YAML has no restrictions on how large or precise numbers can be.
Kotlin Multiplatform does not support numeric types that can represent such large numbers.
Options

actual/expect for each platform
Represent large numbers as a string, to be converted by each platform manually
Use an external library (e.g. https://github.com/ionspin/kotlin-multiplatform-bignum/)

KMath also provides a multiplatform BigInt implementation in their core module. Both seem like good libraries.


api: audit log api specific to RBAC http filters

Commit Message: Add audit_log typed config in HCM and audit_condition enum in RBAC config protos.
Risk Level: low
Docs Changes: N/A
Release Notes: N/A
API Considerations:
This API change is proposed for the feature implementation in gRPC first.
gRPC authorization is based on xDS RBAC proto. The audit logging support we are trying to add is to enable users configure loggers and audit authorization events when the audit condition is met.
The primary different from the access log is that audit log should be invoked right after the RBAC evaluation is done and will not wait till after the entire call finishes. It seems to me this is something Envoy also lacks and could potentially benefit from.
The API change presented here has gone through some preliminary reviews by @markdroth and @ejona86. I'm working on a gRFC which will be linked here as soon as it's available. Meanwhile, I am opening this PR now such that any question or concern could be raised early.

Messed up the commits. Closing this one..


[CLI] avoid api report warning for @packageDocumentation comment

Hey, I just made a Pull Request!
created a new module using the backstage cli and when I was going to generate the api report I got the following warning
// Warnings were encountered during analysis:
//
// src/index.d.ts:2:1 - (ae-misplaced-package-tag) The @packageDocumentation comment must appear at the top of entry point *.d.ts file

// (No @packageDocumentation comment for this package)

Since the template index files starts with /***/ I had to remove that line and then re-generate the report to get rid of the warning. Here is a PR removing that line from the templates that originally had this in place. If there is a reason to why this line is there, feel free to close this PR!
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Missed this one, but for posterity: the /***/ is there as a workaround to the eslint notify plugin removing the first comment in the file when auto fixing, which would otherwise remove the package doc comment. For now repos without the need for a copyright header will need to remove it manually : /


Fix bug where files without .jade extension can't be loaded

Fix for #135
Only files without an explicit file extension are assumed to be .jade files.

Will be fixed in 1.2.0. I actually removed the whole Suffix Check because it's already in the parser and lexer.


[WIP] PROT-244

Add two new methods to GlobalL0Service to only pull snapshots from the majority.

btw - missing label

FYI I'm going to Resolve conversations that are based on outdated code or the issue has been addressed.

@sdavidp would you mind changing the PR title to match the commit name or basically be more descriptive?
Also, no need for [WIP] if it's already a draft PR


Rare 404 on Dailymotion

Video plays on Dailymotion. However, my attempt to download it had this result (repeatedly). I've used youtube-dl for this purpose many times.
`G:\Watch\The Gene Code (59)>youtube-dl --version
2021.03.14
G:\Watch\The Gene Code (59)>youtube-dl https://www.dailymotion.com/video/x14wrke --recode-video mp4
[dailymotion] Downloading Access Token
[dailymotion] x14wrke: Downloading media JSON metadata
[dailymotion] x14wrke: Downloading metadata JSON
[dailymotion] x14wrke: Downloading m3u8 information
ERROR: unable to download video data: HTTP Error 404: Not Found
`

the best quality(608x336) is not playable in browser either, select another format.


Difference between Percentage of Actors vs. Percentage of Time?

To me they almost sound the same, if someone clarify, that would be great!
https://github.com/jnunemaker/flipper/blob/master/docs/Gates.md
Thanks

The article answered my question perfectly, thank you :)