https://gradle.com/ logo
Join Slack
Powered by
What's the proper place to report about Develocity...
# develocity
v
What's the proper place to report about Develocity Gradle plugin issue?
e
v
Nope, just the plugin
Not from paying customer
e
It's fine to report plugin issues there, as it is just a component of the overall Develocity product. However, I'm not sure we have a proper procedure in place for non-customer issues, as it's not common for them to happen. Can you tell me what the issue is in this thread, and I will make sure it is passed along?
v
Oh, so anyone can get a support login?
I assumed it is customer-only
e
I think anyone can sign up, but I'm not certain.
v
I had a quite long-running build with Gradle 9.2.1 and Develocity plugin 4.2.2 applied. I had to catch the bus, so during the build I disconnected the docking station, then sent the laptop to hibernation. On the bus I resumed the laptop with WiFi available. As a result I was constantly spammed by an endless stream of messages like 
Failed to retrieve data for interface 90, wireless_18
most probably coming from 
com.gradle.scan.plugin.internal.dep.oshi.hardware.platform.windows.WindowsNetworkIF#updateAttributes
.
👍 1
Attached to the docking station wan access was through network port on the docking station.
e
Thanks. I will pass it along.
v
Thanks, I also have a Zendesk account now for the next time, thanks :-)
🙌 1
Hm, I'm seeing now that even in the build that I started after that, those messages continued to be spammed at me. Probably because they were run in the same daemon. 😞
e
Hi, @Vampire. This message originates from Oshi itself. There does not appear to be a way to configure it aside from turning off all error reporting.
v
Well, but constantly spamming such messages seems to be wrong to me. It is not even clear to me when this happens. I can just assume that it is because the network interface contributed by the docking station vanished. But also it is unclear to me why the network interfaces are checked anyway. The plugin is applied, but build scan is configured to be done only on explicit request. And even if not, it comes during the whole build, not only during uploading the build scan.
It is even worse than I thought. This is really annoying and it does not only happen when docking / undocking. I the last nights I have run some heave builds and eventually this message was spammed to the console each night from some point on. 😞
It is that disturbing that I think about removing the develocity plugin and stop recommending to always apply it. 😞
e
Hi, @Vampire. Could you try disabling resource usage capturing? That may stop the message from being printed. https://docs.gradle.com/develocity/gradle/current/gradle-plugin/#capturing_resource_usage
v
Thanks, I added it to my user-level Gradle properties now and will keep an eye on it. It is hard to verify though, as it only happens occasionally. Besides that losing that information is very sad of course. :-(
👍 1
3 Views
Open in Slack
PreviousNext
Powered by