[SPARK-21692][PYSPARK][SQL] Add nullability support to PythonUDF.

What changes were proposed in this pull request?
When registering a Python UDF, a user may know whether the function can return null values or not. PythonUDF and all related classes should handle nullability.
How was this patch tested?
Existing tests and a few new tests.

Can one of the admins verify this patch?

@ptkool Thank you for working on this!
I'd like to ask what your use-case is. Users have historically been confused about what nullable means, and we don't think we should give them yet another avenue to get it wrong.

@ueshin Thanks for commenting.
It's unfortunate that users find nullability confusing. If you're coming from a SQL world, you should be quite familiar with nullability and null values. Nevertheless, Spark has a few issues with nullability, this being one of them, that I believe need to be addressed. And given the fact that the Catalyst optimizer considers nullability in several optimization rules makes this extremely important.
As far as a use case, consider any platform using Spark where a null value is considered a "real" value, whether valid or invalid, in the given context, and where data must conform to a particular schema. When Python UDFs are being used, nullability must be specified correctly in order for conformance to work correctly.
Also, a PR was recently merged to address this issue on the Scala side.
https://issues.apache.org/jira/browse/SPARK-20668

@ptkool have you seen a real use case so far that you need this? I'm a bit surprised since Python UDFs are already pretty slow, and you'd care about this. Are there other cases you run into?
One thing we can do is to do a runtime non-null check (insert an AssertNotNull) when this is annotated with not null.

@rxin We have several large systems with 100s of Spark jobs implemented in Python and PySpark, and use Python UDFs due to lack of equivalent functionality in Spark. I understand what your saying re Python UDFs being slow and using AssertNotNull, but making this kind of change would be a huge effort.

I understand why you are using Python. What I don't understand is why you'd need to annotate nullability, because those are typically annotated for the purpose of performance improvement, but Python UDFs are already slow and most performance improvements are probably not going to help you much there.
Can you tell me the case why you care about this?

@rxin
This PR isn't about performance at all. I realize Python UDFs do not perform well and I also realize annotating Python UDFs with nullability is not going to make any difference performance-wise.
This PR is about:

Providing users an avenue to get nullability right.
Satisfying a use case that I described in my initial comments.
Consistency between the Python and Scala APIs.

Can one of the admins verify this patch?

Jenkins, ok to test.

Test build #83752 has started for PR 18906 at commit 38dc32d.

Test build #83752 has finished for PR 18906 at commit 38dc32d.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83752/
Test FAILed.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83784/
Test FAILed.

Test build #83786 has started for PR 18906 at commit 38dc32d.

Test build #83786 has finished for PR 18906 at commit 38dc32d.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83786/
Test FAILed.

Test build #83796 has started for PR 18906 at commit 0bee999.

Test build #83796 has finished for PR 18906 at commit 0bee999.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83796/
Test FAILed.

Test build #83798 has started for PR 18906 at commit 402a814.

Test build #83798 has finished for PR 18906 at commit 402a814.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83798/
Test FAILed.

Test build #83814 has started for PR 18906 at commit feefb3e.

Test build #83814 has finished for PR 18906 at commit feefb3e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83814/
Test PASSed.

CC @HyukjinKwon

Test build #83846 has started for PR 18906 at commit 9856be6.

Satisfying a use case that I described in my initial comments.

I am actually not quite clear of the usecases. Providing actual codes and elaborating it should be helpful.

Consistency between the Python and Scala APIs.

Could you link the equivalent Scala side API endpoints to check the API consistency?

Here are the similar changes in the Scala API: https://github.com/apache/spark/pull/17911

I meant the actual equivalent endpoints and actual codes with usecases.

Test build #83846 has finished for PR 18906 at commit 9856be6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83846/
Test PASSed.

So I think with the performance improvements coming into Python UDFs considering annotating results as nullable or not could make sense (although I imagine we'd need to do something differeent for the vectorized UDFs if they aren't already being done).
Let's loop in @BryanCutler , but the I think the performance improvements could be reasonable to be thinking about in Spark 2.3+.

I believe the equivalent API in Scala would only be in the following form when registering a UDF
spark.udf.register("func", () => { 1 }).asNonNullable()

Would it be preferable to just stick with a similar API for Python if we are trying to match the behavior?

So I think with the performance improvements coming into Python UDFs considering annotating results as nullable or not could make sense (although I imagine we'd need to do something differeent for the vectorized UDFs if they aren't already being done).

Regarding performance increases with vectorized UDFs, right now the Java side is only implemented to accept nullable return types, so there wouldn't be any difference.  In the future it would be possible to accept either and that would give a little performance bump.

Thanks for the background Bryan :) So it sounds like from an API perspective it makes sense to support this in the future possibly on the Pandas UDFs (but the code isn't there on the JVM side). I'd say if @ptkool has the time it might make sense to match the scala API on the current UDFs its easier when we want to add this to the Panda's UDFs

Test build #84359 has started for PR 18906 at commit 90e1684.

Test build #84359 has finished for PR 18906 at commit 90e1684.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84359/
Test FAILed.

Test build #84360 has started for PR 18906 at commit 0727597.

@holdenk I believe the changes in this PR match what's provided in the scala API. Am I missing something?

Test build #84361 has started for PR 18906 at commit f8e4904.

Test build #84361 has finished for PR 18906 at commit f8e4904.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84361/
Test FAILed.

Test build #84360 has finished for PR 18906 at commit 0727597.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84360/
Test FAILed.

@ptkool, for https://github.com/apache/spark/pull/18906#issuecomment-348350023. can you point out Scala API rather than just saying it's consistent with Scala side and making reviewers checking through the codes here and there?

@HyukjinKwon As requested, here are the related Scala API changes:
https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/ScalaUDF.scala#L42
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/expressions/UserDefinedFunction.scala#L69
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/functions.scala#L3281
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/UDFRegistration.scala#L167

For https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/ScalaUDF.scala#L42, I don't think it's a public API.
So, Scala side are:
case class UserDefinedFunction protected[sql] (
    f: AnyRef,
    dataType: DataType,
    inputTypes: Option[Seq[DataType]]) {

def udf[RT: TypeTag](f: Function0[RT]): UserDefinedFunction = {

def register[RT: TypeTag](name: String, func: Function0[RT]): UserDefinedFunction = {

You are proposing adding nullable as below:
 class UserDefinedFunction(object):
     """
     User defined function in Python

     .. versionadded:: 1.3
      """
      def __init__(self, func,
                  returnType=StringType(), name=None,
                  evalType=PythonEvalType.SQL_BATCHED_UDF,
                  nullable=True):

def udf(f=None, returnType=StringType(), nullable=True):

def registerFunction(self, name, f, returnType=StringType(), nullable=True):

I don't think these are quite consistent?

Test build #84715 has started for PR 18906 at commit d992f93.

Test build #84715 has finished for PR 18906 at commit d992f93.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84715/
Test FAILed.

Can one of the admins verify this patch?

ok to test

Test build #85419 has started for PR 18906 at commit d992f93.

Right, let's go ahead. Please let me know anyone has an explicit objection for this one.

Test build #85419 has finished for PR 18906 at commit d992f93.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/85419/
Test FAILed.

Build finished. Test FAILed.

Test build #85472 has started for PR 18906 at commit ca52538.

@HyukjinKwon @holdenk There is still an issue with the use of SparkSession.udf.register that needs to be resolved.
For instance, the following will not work as expected:
spark.udf.register("func", lambda x: x * 4, IntegerType()).asNonNullable()`

As well, the following is not currently possible:
f = udf(lambda x: x * 4, IntegerType()).asNonNullable())
f = spark.udf.register(f)

The same applies to the use of asNondeterministic in the above examples.
One other thing I noticed with the implementation of asNondeterministic in Python class UserDefinedFunction is that it returns an instance of UserDefinedFunction, not a function object.
>>> udf_random_col = udf(lambda: int(100 * random.random()), IntegerType())
>>> udf_random_col
<function <lambda> at 0x10fad28c0>
>>> udf_random_col = udf_random_col.asNondeterministic()
>>> udf_random_col
<pyspark.sql.udf.UserDefinedFunction object at 0x10fac3e50>
>>>

Is this correct?

Test build #85472 has finished for PR 18906 at commit ca52538.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/85472/
Test PASSed.

Test build #87742 has started for PR 18906 at commit e94960c.

Test build #87742 has finished for PR 18906 at commit e94960c.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87742/
Test FAILed.

Test build #87743 has started for PR 18906 at commit e6e6dbf.

Test build #87743 has finished for PR 18906 at commit e6e6dbf.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87743/
Test FAILed.

Test build #88354 has started for PR 18906 at commit 64f0500.

Test build #88354 has finished for PR 18906 at commit 64f0500.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88354/
Test FAILed.

Can one of the admins verify this patch?

Test build #94652 has started for PR 18906 at commit cdd16a9.

Test build #94652 has finished for PR 18906 at commit cdd16a9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/94652/
Test FAILed.

Test build #95624 has started for PR 18906 at commit 9038520.

Test build #95677 has finished for PR 18906 at commit dcf3f07.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95677/
Test FAILed.

Test build #95712 has finished for PR 18906 at commit 97305f5.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95712/
Test FAILed.

Test build #96765 has started for PR 18906 at commit fac6f1e.

Test build #96765 has finished for PR 18906 at commit fac6f1e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96765/
Test FAILed.

Test build #108464 has finished for PR 18906 at commit e1d68e8.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108464/
Test FAILed.

Test build #108477 has started for PR 18906 at commit be5735a.

Test build #108477 has finished for PR 18906 at commit be5735a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108477/
Test PASSed.

Test build #110287 has started for PR 18906 at commit 9cfc5b6.

Test build #110287 has finished for PR 18906 at commit 9cfc5b6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110287/
Test PASSed.

@HyukjinKwon @rxin Any chance of this being merged some time?

Can one of the admins verify this patch?


alpha-54: Site title no longer wraps - search box moves

🐛 Bug Report
In alpha-0.49 and previous (I believe but I'm struggling to get these to build now), longer site titles would wrap at the search in the header bar. This was especially important on mobile browsers where the width is obviously limited. As of alpha-54, the title is not wrapping and search box is being pushed out of the header.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

Install Docusaurus and set up with a multi-word site title (total length more than 12 characters or so)
Enable the search plug in
Visit site on a mobile browser

Expected behavior
Words should wrap to ensure proper placement of search box
Actual Behavior
Title is shown on one line and search is moved
iOS:

Pixel 4 (on BrowserStack)

Your Environment

Docusaurus version used: alpha-54
Environment name and version: Chrome and Safari on iOS,
Operating system and version (desktop or mobile): iOS on iPhone XS. Using browser stack I see it on other devices, including android, depending on screen size/resolution

There's no good way around this as the site title can be potentially very long. I think as a lasting solution we could make the search as an icon-only on mobile, and focusing on it will expand and fill the whole bar.

An icon that expands (on top of title) when tapped would be a really nice solution. Or on mobile move the search into the hamburger menu

Hi the only thing to do is to change the media query of the search-bar class.
Now the icon is shown under 360px. I think that we need to change it


NodeJS using Prism on the server-side

NodeJS appears to be using Prism on the server side: view source e.g. here and look at the class names. Is that enough to feature it?

They are using Prism. Here's the build script of the website. They use Prism via a plugin for their markdown render.
I think that's enough to feature it.

Great!
In general, I suspect there are many big websites using Prism that we have not featured. I mean, we have 3 million weekly downloads on npm alone!
I wonder how we could find them...

Look at https://www.nerdydata.com/
Search for prism.js, prism.min.js, or prismjs.

I often "get a feel" for it when I see the code blocks on a website, somehow.
Note that NodeJS still uses HighlightJS in the API docs.
From a quick tour I just did on some tech websites (in quite a random order):
Tailwind CSS uses Prism too (at least the tokenizer).
Preact (https://github.com/preactjs/preact-www/tree/master/src/components/code-block)
Svelte (https://github.com/sveltejs/svelte/blob/master/site/src/utils/highlight.js#L2)
Font Awesome
NextJS
Gatsby
GraphQL
Apollo
Redux
Express
Deno (https://github.com/denoland/deno_website2/blob/master/components/CodeBlock.tsx#L4)
Storybook
Laravel
And probably many many more. :)

We should feature all these sites in the homepage! At least the big ones!

I think if we decide to feature more websites on the homepage, we'll need to revisit the design though, cause we can't spam a lot more logos as huge as they are right now haha.

Here are my findings.
Docs for frameworks and libraries

Composer, a PHP dependency manager (proof);
JointJS, a diagramming library;
Materialize, a popular CSS framework;
Material Design Lite;
Meteor, a JavaScript app platform;
Nest (NestJS), a Node.js framework (see polyfills-es5.js);
p5.js, a JavaScript library for creative coding;
Qooxdoo, a JavaScript framework;
RavenDB, a NOSQL DBMS (see main.js);
Slim, a micro framework for PHP.

Site generators

docsify, a quite popular documentation site generator (proof).

Text editors

MacDown (see the list of dependencies or unpack the package and see the Contents/Resources/Prism/ directory);
TinyMCE. The @ephox/wrap-prismjs package wraps PrismJS in a ECMAScript 2015 module.

PaaS & other sites

DevDocs, a documentation browser (proof);
paddle, a PaaS for B2B SaaS (proof);
Tutorial Republic;
Vue.js Examples.

refractor. 2M downloads weekly.

I wonder if we should have a longer text-only list of websites using Prism, in addition to the bigger ones that we list with logos.

I wonder if we should have a longer text-only list of websites using Prism

I wonder. For most of those sites, libraries, and frameworks, using Prism is probably just an implementation detail, so I would expect a text-only list to change "frequently" (maybe every month or so depending on the length of the list) and I wouldn't want to check and update it manually.
But I am very much for diversifying our current list of popular sites.

Maybe another site to add to the list:

Crates.io, Rust's main package registry (example)

This is HUGE: Google's web.dev uses Prism!! Evidence: https://web.dev/publish-modern-javascript/
We should definitely list this on the homepage!

Reactjs.org uses Prism too: (package.json).

Another one we could mention: v8.

There's CSS-Tricks too.

There's CSS-Tricks too.

We already list that on the homepage.

@mui/material is a trending React UI library. The project team uses Prism on their site [1; 2].


Error XHR 404 loading (traceur) "ng2-progressbar"

When loading my app, after importing ng2-progressbar, I get the following

Systemjs.config file:

App.module.ts file:

Is this working with Angular 2.3.0 ?

Sure, i use it with the latest version, but I don't use system.js so I'm not familiar with the error, which starter are you using?

@MurhafSousli . Thanks for the update...but I'm not sure what you mean by starter.

@jandresampaio a starter such as angular-cli or angular2-webpack-starter..

@MurhafSousli
None of those...we're using Visual Studio with sample ASP.NET core project, using Gulp task runner . Maybe you are refering to angular2-quickstart (as in package.json):
{
"name": "angular2-quickstart",
"version": "1.0.0",
"scripts": {
"start": "tsc && concurrently "npm run tsc:w" "npm run lite" ",
"lite": "lite-server",
"postinstall": "typings install",
"tsc": "tsc",
"tsc:w": "tsc -w",
"typings": "typings"
},

@jandresampaio I have tried a similar starter, I got the same error, but I couldn't figure out how to fix it.
Umm It seems that the starter is looking for a umd module, which I'm not familiar with.
If you find a solution, please share it here or send me a pull request and I will merge it.

I have seen errors related to traceur when you have multiline comments somewhere at the end or beginning of any component... I'm sorry, my two cents...

Error : ng2-progressbar not found
I am using angularjs2.4.2.
Steps  :
I have install in node_modules using given command :
define in system.config.js as :
map: {
'ng2-progressbar': 'npm:ng2-progressbar
}
3)- importing in app.module.ts as :
import { NgProgressModule } from "ng2-progressbar";
@NgModule({
imports: [NgProgressModule],
declarations: [ ],
bootstrap: [ ]
})
4)- Importing in app.component.ts as :
import {NgProgressService} from "ng2-progressbar";
@Component({
selector: 'my-app',
template:  Hello {{name}}
})
export class AppComponent {
name = 'Angular delhi';
constructor(private pService: NgProgressService) {
}
ngOnInit(){
/** request started /
this.pService.start();
this.http.get('abc.com').subscribe(res){
/* request completed */
this.pService.done();
}
}
}
Then Error in console ------ :
GET http://localhost:3000/node_modules/ng2-progressbar/ 404 (Not Found) zone.js:1645
Error: (SystemJS) XHR error (404 Not Found) loading http://localhost:3000/node_modules/ng2-progressbar(…) (index):16

Untill we find out what is causing it to fail in system.js, a workaround is to copy the (source typescript)[https://github.com/MurhafSousli/ng2-sharebuttons/tree/master/src] files into your project and import it from there

Related issues for XHR error (404 Not Found) loading (traceur) see #12500, #11358 on Angular repo

Systemjs is supported now in v1.3.0


when copy the project to a new folder and try training, change do not work

hi, I have download the code ,and trainning a model in folder A, and I have copy the source code to folder B, and change some code, but it seems use the folder A's code, for example, the PROJECT_ROOT defined in settings.py, is always A .

I think I solved the issue.
Because I have change the folder, but not change the environment PYTHONPATH


Fix test race condition

Summary

This small change should resolve the race condition in GivenMaintenanceTooLong_ThenExpectNoRepack test

Checklist

[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog

There's a typo in the title.
Could you also please elaborate how this should fix the race condition? Did it run into a timeout because it waited too long?

There's a typo in the title.
Could you also please elaborate how this should fix the race condition? Did it run into a timeout because it waited too long?

The problem can occur only in a test. Apparently the updates to the fake client are so fast that 1 second is too much for the test to go into timeout therefore I set it to a millisecond which will trigger right away the timout.


I have a problem

Every time I run the code, everything is fine, but when he tries to download the post reddit gallery, he crashes, can this problem be solved?

Any progress on the bot?

@DaYzTm Yeah i have been working on including gallery posts from reddit in bot. Hopefully by the end of this week this issue will be resolved.

@DaYzTm Yeah i have been working on including gallery posts from reddit in bot. Hopefully by the end of this week this issue will be resolved.

Well, that’s very good, I’ll wait, I’m just not very experienced yet.

@DaYzTm check now. i have added the support there have been some changes the bot can be run from main.pyfrom now on.

@DaYzTm check now. i have added the support there have been some changes the bot can be run from main.pyfrom now on.

Thank you very much for helping me, so we can close the subject on this occasion


feat(cadence): ✨ add enum

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-4 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 99.629%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/src/scale/cadence.dart
0
4
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
1074

Relevant Lines:
1078

💛  - Coveralls


remove super from actions and private

common code shouldn't use inheritance it should use mixins or
ideally composition -- the slave_jnlp providers should probably
use jenkins_slave sub-providers to do their work, but they do
not.
anyway super is busted, so do the minimum amount to move that to a
function which can then at least be called directly.
also it seems someone mistakenly thought they needed to use
protected so that subclasses could use methods, which is incorrect,
this is ruby, not java, subclasses can call all private methods in
the superclass (protected is weird in ruby -- it allows a receiver
to be a different instance of the same clas, which is occasionally
useful, but 99% of the time in our code protected is used when
private is meant).
Signed-off-by: Lamont Granquist<EMAIL_ADDRESS>

The change to slave_windows.rb's :create action now skips everything in slave_jnlp's :create. This includes creating the remote filesystem folders and slave.jar downloading.

@rimitchell You can open an issue with some additional information around replication of the issue? Thanks!


De-flow the domain layer

I don't think we need flows down at this layer. We can represent all of this work as suspending functions then utilize flow in the VM.

Eh, on second though... this is probably better with flow in place. It has built in support for accumulators, etc.


White border around workflow graph

Summary
In both Firefox and Chrome (v86 and 89 respectively) on a Mac, I have a white border around my workflow graph. (bottom and to the right)
This is purely a cosmetic issue. Occurs on all workflow graphs.
Workflow removed in this screenshot, but hopefully you get the idea:

Diagnostics
What Kubernetes provider are you using? EKS 1.19
What version of Argo Workflows are you running?  3.0 rc8

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

On initial testing, this seems to have been fixed in rc9

This is NOT resolved in rc9.
However, it does only seem to occur at different resolutions. My current res is 2560x1440 and this displays the issue.

I can no longer replicate this issue in 3.1 (rc 12)


Plugin is not available

Seems the plugin is not available anymore

n

Sometimes this is temporal network issue. But this/next year it may be larger problem:
Nodeclipse Repository has been hosted on Bintray, and as Bintray is shutting down, and I have no plans to do new releases
it may be the end of all my previous work on Nodeclipse plugins.
Help is needed, just to rebuild and publish to some other place, like GitHub releases

I am not an expert about repositories, I am assuming that the own Eclipse plugins are hosted in its own servers.

The exact problem is that own servers cost money, so free hosting on Bintray was used
(that time GitHub discouraged hosting binaries on GitHub)
As I am not using Eclipse now, I am not going to spend time to deploy, install to test etc
That is unlucky that Bintray stopped, but for future new maintainer is wanted anyways.


feat(wash-cli): add host log path option

This commit adds a --host-log-path`` option to the wasmcloud-related options for wash up`. With this command, a custom path can be specified to write to when the host is producing logs.
Feature or Problem

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

Hey @brooksmtownsend > Yeah that is a good idea I think!
Made a follow-up issue here:
https://github.com/wasmCloud/wasmCloud/issues/3012


Usage without encryption

From what I saw, saving notes unencrypted isn't possible with the current code and there's no "switch" to configure it to behave that way. A way to configure, i.e. turn encryption on/off, would be nice.
I know this sounds like a step back, but I personally think the risk of forgetting a password is far worse than the risk of the local admin being able to read the notes in cleartext. With the current setup, you need to fully trust the administrator (and environment the app is running) anyway.
(I think being able to use something like Mailvelope or WebPG together with mininote, or encrypting the database as whole (i.e. to be able to store it in more unsafe locations securely) would make more sense.)

I've installed the Mailvelope add-on and created a new notebook (pw:1234 with 1234 as passwort) in the demo as an example and a note called secret.txt which should be safely encrypted, even though everyone can open it.

Hi @espressoelf! I see the issue that not everyone might want encryption. However, I'd still like to have it included as a built-in feature. Using third-party browser plug-ins is too much of a hassle for the average user. I could imagine a solution where encryption can optionally be turned off by the server admin using a feature flag in the config. PRs are welcome!

That's understandable, users want a simple solution and not another bloated complete solution for every problem. I still think the current solution is more or less a placebo, protecting a leaked db at most. I'll try to read more into the code and see if I can add something. I'll create a PR when I'm able to. Until then, I'll leave this as suggestion and also as hint for users looking for other ways to encrypt their text without trusting the server.
Feel free to close this for now if you want :)

Actually, considering the issue described in https://github.com/muety/mininote/issues/73, I think the option to disable encryption (globally for the whole instance) would be helpful after all. I'll have a look once I get to it.

I still think the current solution is more or less a placebo, protecting a leaked db at most.

Quick comment on that. The current type of encryption is more than just encryption at rest. It's in fact end-to-end encryption, but, admittedly, with the caveats mentioned at https://github.com/muety/mininote#-encryption.
We might actually get rid of the password entirely, which would drastically improve security in a way that there wouldn't be a need to trust the server admin to not use modified code anymore. I created https://github.com/muety/mininote/issues/74.


Crash with object selector tool

When I choose the smart object selector tool I get "Runtime error" and the program crashes.

Hello,
Thanks for your report.
I'll check if I can reproduce when I'm at home this evening
Until then if you can run Photoshop via the terminal (go to your install folder then in drive c you should find launcher.sh just run it) and paste the logs here or on a pastbin so if I can't reproduce later I'll be able to check what's wrong..

I reproduced it.
If you need that tool you can use the 2021 install in the meantime. (this tool worked on 2021 on linux)
You can find them here : https://github.com/MiMillieuh/Photoshop-CC2022-Linux/tree/main/scripts
I hope I can fix it soon because it's a major tool in photoshop
I let the issue open until I find something

Great thanks, the 2021 version works fine for the object selector, in the 2022 version also it did not detect gpu so couldn't do gpu intensive things, in the 2021 version this works fine.
The neural filters button is also greyed out on both 2021 and 2022.
Thanks for all your work on this.

Great thanks, the 2021 version works fine for the object selector, in the 2022 version also it did not detect gpu so couldn't do gpu intensive things, in the 2021 version this works fine.
The neural filters button is also greyed out on both 2021 and 2022.
Thanks for all your work on this.

I know it's because new PS2022 use Child window and it didn't work with vulkan so I need to patch it

Update on it :
Photoshop doesn't crash anymore. but the tool still unusable due to a programming error...
I just have to fix this and it should be good to go
Sorry it take more time that I was expecting...


[Feature] Adding Custom Scrollbar

Description:
The platform currently lacks the functionality of theme-matching scrollbar which are pivotal for improving user comfort and navigation fluidity. By integrating this feature, I aim to provide users with a smoother and more personalized browsing experience.
I have implemented this feature multiple times in open source as well as personal projects, so please assign this issue to me under GSSoC'24.

Go ahead @SwanandD121


Way of Expanding Photos that are Difficult to See

There are some photos in the workshop that are difficult to see, such as the OpenShift Pipelines Operator Install section. It would be helpful to add a way to expand the photo to get a better view of the picture.

Simple workarounds for now. Drag divider to right. Or click on hamburger menu and select "Open Workshop" and look at it full screen.

Thanks for these suggestions. I'll take a look and see what the best way to include in instructions would be.

See also https://github.com/openshift-homeroom/workshop-dashboard/issues/41


v1.2.0 breaks ElysiaJS app (lucia auth)

I finished working on an Elysia JS web app using Lucia Auth, Lucia has some dependencies on Oslo.
Everything was working perfectly til un update to my Oslo package from 1.1.3 to 1.2.0, now my server cannot initialize, throwing the error:
1 | (function (entry, fetcher)
    ^
SyntaxError: Export named 'base32' not found in module '...\node_modules\lucia\node_modules\oslo\dist\encoding\index.js'.
error: script "start" exited with code 1

Has the base32 function been replaced or just deprecated?

My bad, just realized Lucia was updated to 3.2.0 which works around this 🫢


Evaluate Kotlin plugin support for instant execution

This branch is configured to build and test Gradle against the latest development version of Kotlin with support for instant execution, 1.3.70-dev-1099 at this time.

Running :instantExecution:compileKotlin against a distro built from this branch currently fails with:
> Task :instantExecution:compileKotlin FAILED
Could not resolve compiler classpath. Check if Kotlin Gradle plugin repository is configured in project ':instantExecution'.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':instantExecution:compileKotlin'.
> Configuration with name 'kotlinCompilerClasspath' not found.

It is possible that this is caused by an older version of Kotlin leaking from buildSrc.


[BUG]: Getting errors on startup

How are you running AnythingLLM?
AnythingLLM desktop app
What happened?
:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser”
[22883:0521/233124.387191:ERROR:select_file_dialog_linux_portal.cc(274)] Failed to read portal version property
[22883:0521/233124.669827:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop
glx: failed to create dri3 screen
failed to load driver: nouveau
glx: failed to create dri3 screen
failed to load driver: nouveau
prisma:warn Prisma doesn't know which engines to download for the Linux distro "artix". Falling back to Prisma engines built "debian".
Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros.
prisma:warn Prisma doesn't know which engines to download for the Linux distro "artix". Falling back to Prisma engines built "debian".
Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros.
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:/home/mts/.config/anythingllm-desktop/storage/anythingllm.db"
Error: Schema engine exited. Error: Could not find schema-engine binary. Searched in:

<EMAIL_ADDRESS>/tmp/.mount_AnythiDCKQSH/resources/backend/node_modules/prisma/schema-engine-debian-openssl-1.1.x
/tmp/.mount_AnythiDCKQSH/resources/backend/node_modules/schema-engine-debian-openssl-1.1.x
/tmp/.mount_AnythiDCKQSH/resources/backend/node_modules/prisma/runtime/schema-engine-debian-openssl-1.1.x
prisma:warn Prisma doesn't know which engines to download for the Linux distro "artix". Falling back to Prisma engines built "debian".
Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros.
Prisma schema loaded from prisma/schema.prisma
prisma:warn Prisma doesn't know which engines to download for the Linux distro "artix". Falling back to Prisma engines built "debian".
Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros.
Error:
EROFS: read-only file system, unlink '/tmp/.mount_AnythiDCKQSH/resources/backend/node_modules/.prisma/client/index.js'

Are there known steps to reproduce?
No response

You are using an unsupported xdg-desktop app to show the UI for your linux distro and will not work with our AppImage
Reddit: https://www.reddit.com/r/hyprland/comments/14bpjuy/no_such_interface_orgfreedesktopportalfilechooser/
Additionally:

prisma:warn Prisma doesn't know which engines to download for the Linux distro "artix". Falling back to Prisma engines built "debian".
Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros.
Prisma schema loaded from prisma/schema.prisma
prisma:warn Prisma doesn't know which engines to download for the Linux distro "artix". Falling back to Prisma engines built "debian".
Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros.
Error:
EROFS: read-only file system, unlink '/tmp/.mount_AnythiDCKQSH/resources/backend/node_modules/.prisma/client/index.js'

Indicates you will have the exact same issue after you solve the desktop issue as the pinned issue https://github.com/Mintplex-Labs/anything-llm/issues/898 for which there is a solution, but both of these problems would be fixed by using docker instead of the AppImage


Add Aggregation and Variability to Summary Result

The Summary Result takes data from all directories that have a run id (e.g. run-17173f3298) and pull the records together into one big file.  It does no aggregation nor does it add any columns.

Aggregate tests that have the same name.  For test-rate use the median value
Add a variability column to show the variability between test runs from the same test (probably percent standard deviation)
Add a run_count column to show how many runs made up the aggregated column

This was done with the GCloud script work that shows variability, metrics, differences, row_count, variability and much more.
See https://storage.googleapis.com/deephaven-benchmark/benchmark_tables.dh.py


A few reaction drawing tweaks

All are on the Python side.
These are small ones.

I was just about to make  PR for reaction SVG!  You beat me to it  :)


"well" as interjection

https://simple.wiktionary.org/wiki/well gives

Well, I guess I'm leaving now.

as an adverb, but most dictionaries (including PTB tag guidelines) call it an interjection. Should we follow suit? For me, at least, the above example makes no suggestion that things are "well": it has no element of approval and cannot be modified by "very". The mid-utterance continuation usage ("He said that, well, it wouldn't be appropriate") also feels like an interjection.
By contrast, the discourse expression "Very well" means something like "All right", with a flavor of 'things are OK/all taken care of'. I support Adv for that usage.

Yes, I think you're right. I'll make the change on Simple English Wiktionary.


Setup a CI build.

We should have at least one CI build for the client library.

This was fixed in #12.


[2201.8.x] Introduce transactionAutoCommitTimeout and transactionCleanupTimeout configuration values for transactions

Purpose
Introduces new configurations to prevent premature commits of long-running transactions before reaching the commit phase.
Related #42922
Approach
This PR introduces two new configurations values for transactions, transactionAutoCommitTimeout and transactionCleanupTimeout.
Samples
You can change the Config.toml with these two new configs as below.
[ballerina.lang.transaction]
transactionAutoCommitTimeout=120
transactionCleanupTimeout=600

Remarks
ballerinai-transaction PR: https://github.com/ballerina-platform/module-ballerinai-transaction/pull/549
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Closing this, since a new PR was created to merge into 2201.8.7-stage instead of 8.x.


Too long description of organizations breaks UI

Gitea version (or commit ref): 1.8.0 (https://dl.gitea.io/gitea/1.8.0/gitea-1.8.0-linux-amd64.xz)
Git version: 2.11.0
Operating system: Debian 9
Database (use [x]):

[x] SQLite

Description

create a new organization and/or edit an existing one
In the description field use more than 254 characters
click on update setting

You'll get the following error:
template: org/settings/options:41:110: executing "org/settings/options" at <eq .CurrentVisibility 0>: error calling eq: invalid type for comparison

The text field should allow max. 254 characters or the description in the database should allow more characters.

I cannot replicate this. There is actually validation in place to protect against this kind of thing.
@shaoran How were you able to make a description of more than 254 characters

@adelowo that is the repo description -- this error is about the description of an org: if you go to https://example.com/org/orgname/settings you can see.

Lol... I haven't had enough water today :)
Will take a look at it

@adelowo no problem, we all do mistakes. To answer your question, I copied and pasted a couple of paragraphs (3 to be precise) from our company homepage, that leads to more than 255 characters.

it looks like updating an org settings is maybe missing helper functions to check these types of things similar to what repos and org_teams have:
https://github.com/go-gitea/gitea/blob/81059a2567be0cd811ca10e3545282c9aa53276a/models/repo.go#L1675
https://github.com/go-gitea/gitea/blob/81059a2567be0cd811ca10e3545282c9aa53276a/models/org_team.go#L370
Updating an org uses updateUser:
https://github.com/go-gitea/gitea/blob/81059a2567be0cd811ca10e3545282c9aa53276a/models/user.go#L971-L974
But the truncating for a user happens in this BeforeUpdate:
https://github.com/go-gitea/gitea/blob/81059a2567be0cd811ca10e3545282c9aa53276a/models/user.go#L156
Which maybe doesn't happen for an org. I'm not totally familiar with how it all works though

This also affects the organisation name if there are added more than 40 letters

Which maybe doesn't happen for an org. I'm not totally familiar with how it all works though

@mrsdizzie JFYI: I found, that organisations are nearly the same as users, they share the same model. It's a flag, so these update functions got called. It was just a missing variable for template.


Add pymongo3.x compatibility layer

@srossross I also bumped the required version of pymongo to 2.8 (so it is leveled with AS)

:+1:


Enable multi targeting to support .NET Core 3.1 and .NET 5.0

Applications compiled for .NET Core 3.1 or .NET 5.0 can also use the library to run distributed transactions with MSSQL servers on Windows.

Applications under .NET Core 3.1 and .NET 5.0 are supported from version 1.1.0 and higher.


Latency, Throughput, and Scalability question

Hello,
I am researching various P2P projects for a low-latency, high-throughput, and hugely scaling project that might be considered to be used as the core to build out a unique type of P2P network in which data (i.e. files, streams, database, etc.) will be spread across the network and users will interact in various groups on the network which might be similar to the "rooms" in your atm0s-sdn project.
Originally the idea was to use Wireguard VPN tunnels along with STUN/TURN relays for computers behind NAT firewalls as to a possibly VPN type typical solution, but came across your project and it made me start to think outside-the-box to see is perhaps something new might be possible.
Recently, I also looked at your "Decentralized Ultra-Low Latency Streaming Server" (https://github.com/8xFF/atm0s-media-server) and am very impressed with what I saw there as well.
Any thoughts or suggestions would be greatly appreciated.
I would also be very interested to see any network benchmarks that you might have as well.
Thanks in advance and Happy New Year.

@lonnietc Can you explain more details about your usecase? How many groups you will create? How big and how wide your network will be established?

@lonnietc Sorry I missed your question, currently I too busy with media-server and SDN features for integrating to some company systems. The SDN transport is just plain UDP with noise-protocol encryption, so it will be fast, SDN packet forward it self only fire and forget style the it will be fast too. If any application which need more, It can be done by implement ebpf-XDP packet forward instead of doing in userspace (this solution is considered a company working on CloudProvider).
When I done above tasks, I will doing some benchmark both on SDN and media-server.


Bugfix/dapp transfer route can not handle optional route parameter

Fixes #2144
Short description
Nothing to add.
Based on #2143 Will become rebased as soon as the parent PR gets merged. Just review the last commit please.
Definition of Done

[ ] Steps to manually test the change have been documented
[ ] Acceptance criteria are met
[ ] Change has been manually tested by the reviewer (dApp)

Steps to manually test the change (dApp)

Enter the /transfer route without the optional token address parameter
Check that you see a "first" token that you are connected with
Check that there are no error messages in the console

Sorry for the delayed comment.
I rebased this PR on master as announced in the description. As result only the 2 last commits are remaining.
As soon as CI runs through I'll merge it. This will then produce a new master state that we can branch from without fearing any conflicts.


Failed to Check sensors command functionality with different options

Hi,
I have executed test_hwmon_driver() from op-test-framework/testcases/OpTestSensors.py on garrison system. Manually I am able to get output for  "sudo yes | sensors-detect" but when i tried  Checking sensors command functionality with different options... i saw this issue
root@g68L:/home/tyan# sudo sensors -f; echo $?
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
1
can you please tell me what are the prerequisites to execute above command
System info:
bmc: g68.aus.stglabs.ibm.com
lpar: g68L.aus.stglabs.ibm.com
From BMC:
cat /proc/ractrends/Helper/FwInfo
FW_VERSION=2.13.00022
FW_DATE=Apr 14 2016
FW_BUILDTIME=16:53:41 CDT
FW_DESC=8335-GTB PASS1 89a207b gar.820.160414a
FW_PRODUCTID=1
FW_RELEASEID=RR9
FW_CODEBASEVERSION=2.X

-bash-4.1$  ipmitool -H g68 -I lanplus -U ADMIN -P admin fru print 43
Product Manufacturer  : 2c80
Product Name          : 0b
Product Part Number   : 18KSF1G72PDZ-1G6N1
Product Version       : 314e
Product Serial        : 0f5f0f9f
-bash-4.1$

Hi Sridevi,
Can you tell us which is the Linux HOST OS you have installed on Garrisson box.
Have you installed Ubuntu 16.04 or RHEL 7.2 or PKVM as the OS on the machine.

Hi,
I am using
tyan@g68L:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="15.04 (Vivid Vervet)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 15.04"
VERSION_ID="15.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
tyan@g68L:~$ cat /boot/config-3.19.0-58-generic | grep -i --color=never CONFIG_SENSORS_IBMPOWERNV
CONFIG_SENSORS_IBMPOWERNV=m
===> 'm' in powerNV OS(i.e RHEL7.2 LE and Ubuntu14.04.04)

We have to load the kernel module manually on your Ubuntu 15.04 HOST OS, since CONFIG_SENSORS_IBMPOWERNV=m is mentioned for this kernel.
So, do the following manually for loading the "ibmpowernv" kernel module.
modprobe ibmpowernv
lsmod | grep ibmpowernv
Then execute the sensors commands with options.
If the kernel config showed CONFIG_SENSORS_IBMPOWERNV=y, then the module would have loaded by default.

Hi pavaman,
"ibmpowernv" is running
===> This the output of the echo YES | sensor-detect command
root@g68L:/etc/init.d# echo YES | sensors-detect
sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
DMI data unavailable, please consider installing dmidecode 2.7
or later for better results.
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): modprobe: FATAL: Module cpuid not found.
Failed to load module cpuid.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): Sorry, no supported PCI bus adapters found.
Next adapter: cen_80000004_e0p0 (i2c-0)
Do you want to scan it? (YES/no/selectively): Client found at address 0x1a
Probing for Analog Devices ADM1021'...                     No Probing for Analog Devices ADM1021A/ADM1023'...            No
Probing for Maxim MAX1617'...                              No Probing for Maxim MAX1617A'...                             No
Probing for Maxim MAX1668'...                              No Probing for Maxim MAX1805'...                              No
Probing for Maxim MAX1989'...                              No Probing for Maxim MAX6655/MAX6656'...                      No
Probing for TI THMC10'...                                  No Probing for National Semiconductor LM84'...                No
Probing for Genesys Logic GL523SM'...                      No Probing for Onsemi MC1066'...                              No
Probing for Maxim MAX1618'...                              No Probing for Maxim MAX1619'...                              No
Probing for National Semiconductor LM82/LM83'...           No Probing for Maxim MAX6654'...                              No
Probing for Maxim MAX6690'...                              No Probing for Maxim MAX6680/MAX6681'...                      No
Probing for Maxim MAX6695/MAX6696'...                      No Probing for Texas Instruments AMC6821'...                  No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                No Probing for ST STTS3000'...                                No
Probing for NXP SE97/SE97B'...                             Success!     (confidence 5, driver jc42')
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x1b Probing for ST STTS424'...                                 No
Probing for ST STTS424E'...                                No Probing for ST STTS2002'...                                No
Probing for ST STTS3000'...                                No Probing for NXP SE97/SE97B'...                             Success!
(confidence 5, driver jc42') Probing for NXP SE98'...                                   No
Probing for Analog Devices ADT7408'...                     No Probing for IDT TS3000/TSE2002'...                         No
Probing for Maxim MAX6604'...                              No Probing for Microchip MCP9804'...                          No
Probing for Microchip MCP98242'...                         No Probing for Microchip MCP98243'...                         No
Probing for Microchip MCP98244'...                         No Probing for Microchip MCP9843'...                          No
Probing for ON CAT6095/CAT34TS02'...                       No Probing for Atmel AT30TS00'...                             No
Client found at address 0x1c
Probing for Texas Instruments TMP421'...                   No Probing for SMSC EMC1072'...                               No
Probing for SMSC EMC1073'...                               No Probing for SMSC EMC1074'...                               No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                No Probing for ST STTS3000'...                                No
Probing for NXP SE97/SE97B'...                             Success!     (confidence 5, driver jc42')
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x1d Probing for Texas Instruments TMP421'...                   No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                No Probing for ST STTS3000'...                                No
Probing for NXP SE97/SE97B'...                             Success!     (confidence 5, driver jc42')
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x52 Handled by driver at24' (already loaded), chip type 24c02'     (note: this is probably NOT a sensor chip!) Client found at address 0x53 Handled by driver at24' (already loaded), chip type `24c02'
(note: this is probably NOT a sensor chip!)
Next adapter: cen_80000005_e0p0 (i2c-1)
Do you want to scan it? (YES/no/selectively): Client found at address 0x1a
Probing for Analog Devices ADM1021'...                     No Probing for Analog Devices ADM1021A/ADM1023'...            No
Probing for Maxim MAX1617'...                              No Probing for Maxim MAX1617A'...                             No
Probing for Maxim MAX1668'...                              No Probing for Maxim MAX1805'...                              No
Probing for Maxim MAX1989'...                              No Probing for Maxim MAX6655/MAX6656'...                      No
Probing for TI THMC10'...                                  No Probing for National Semiconductor LM84'...                No
Probing for Genesys Logic GL523SM'...                      No Probing for Onsemi MC1066'...                              No
Probing for Maxim MAX1618'...                              No Probing for Maxim MAX1619'...                              No
Probing for National Semiconductor LM82/LM83'...           No Probing for Maxim MAX6654'...                              No
Probing for Maxim MAX6690'...                              No Probing for Maxim MAX6680/MAX6681'...                      No
Probing for Maxim MAX6695/MAX6696'...                      No Probing for Texas Instruments AMC6821'...                  No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                Success!     (confidence 5, driver jc42')
Probing for ST STTS3000'...                                No Probing for NXP SE97/SE97B'...                             No
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x1b Probing for ST STTS424'...                                 No
Probing for ST STTS424E'...                                No Probing for ST STTS2002'...                                Success!
(confidence 5, driver jc42') Probing for ST STTS3000'...                                No
Probing for NXP SE97/SE97B'...                             No Probing for NXP SE98'...                                   No
Probing for Analog Devices ADT7408'...                     No Probing for IDT TS3000/TSE2002'...                         No
Probing for Maxim MAX6604'...                              No Probing for Microchip MCP9804'...                          No
Probing for Microchip MCP98242'...                         No Probing for Microchip MCP98243'...                         No
Probing for Microchip MCP98244'...                         No Probing for Microchip MCP9843'...                          No
Probing for ON CAT6095/CAT34TS02'...                       No Probing for Atmel AT30TS00'...                             No
Client found at address 0x1c
Probing for Texas Instruments TMP421'...                   No Probing for SMSC EMC1072'...                               No
Probing for SMSC EMC1073'...                               No Probing for SMSC EMC1074'...                               No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                No Probing for ST STTS3000'...                                No
Probing for NXP SE97/SE97B'...                             Success!     (confidence 5, driver jc42')
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x1d Probing for Texas Instruments TMP421'...                   No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                No Probing for ST STTS3000'...                                No
Probing for NXP SE97/SE97B'...                             Success!     (confidence 5, driver jc42')
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x52 Handled by driver at24' (already loaded), chip type 24c02'     (note: this is probably NOT a sensor chip!) Client found at address 0x53 Handled by driver at24' (already loaded), chip type `24c02'
(note: this is probably NOT a sensor chip!)
Next adapter: cen_80000014_e0p0 (i2c-2)
Do you want to scan it? (YES/no/selectively): Client found at address 0x1a
Probing for Analog Devices ADM1021'...                     No Probing for Analog Devices ADM1021A/ADM1023'...            No
Probing for Maxim MAX1617'...                              No Probing for Maxim MAX1617A'...                             No
Probing for Maxim MAX1668'...                              No Probing for Maxim MAX1805'...                              No
Probing for Maxim MAX1989'...                              No Probing for Maxim MAX6655/MAX6656'...                      No
Probing for TI THMC10'...                                  No Probing for National Semiconductor LM84'...                No
Probing for Genesys Logic GL523SM'...                      No Probing for Onsemi MC1066'...                              No
Probing for Maxim MAX1618'...                              No Probing for Maxim MAX1619'...                              No
Probing for National Semiconductor LM82/LM83'...           No Probing for Maxim MAX6654'...                              No
Probing for Maxim MAX6690'...                              No Probing for Maxim MAX6680/MAX6681'...                      No
Probing for Maxim MAX6695/MAX6696'...                      No Probing for Texas Instruments AMC6821'...                  No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                Success!     (confidence 5, driver jc42')
Probing for ST STTS3000'...                                No Probing for NXP SE97/SE97B'...                             No
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x1b Probing for ST STTS424'...                                 No
Probing for ST STTS424E'...                                No Probing for ST STTS2002'...                                Success!
(confidence 5, driver jc42') Probing for ST STTS3000'...                                No
Probing for NXP SE97/SE97B'...                             No Probing for NXP SE98'...                                   No
Probing for Analog Devices ADT7408'...                     No Probing for IDT TS3000/TSE2002'...                         No
Probing for Maxim MAX6604'...                              No Probing for Microchip MCP9804'...                          No
Probing for Microchip MCP98242'...                         No Probing for Microchip MCP98243'...                         No
Probing for Microchip MCP98244'...                         No Probing for Microchip MCP9843'...                          No
Probing for ON CAT6095/CAT34TS02'...                       No Probing for Atmel AT30TS00'...                             No
Client found at address 0x1c
Probing for Texas Instruments TMP421'...                   No Probing for SMSC EMC1072'...                               No
Probing for SMSC EMC1073'...                               No Probing for SMSC EMC1074'...                               No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                Success!     (confidence 5, driver jc42')
Probing for ST STTS3000'...                                No Probing for NXP SE97/SE97B'...                             No
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x1d Probing for Texas Instruments TMP421'...                   No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                Success!     (confidence 5, driver jc42')
Probing for ST STTS3000'...                                No Probing for NXP SE97/SE97B'...                             No
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x52 Handled by driver at24' (already loaded), chip type 24c02'     (note: this is probably NOT a sensor chip!) Client found at address 0x53 Handled by driver at24' (already loaded), chip type `24c02'
(note: this is probably NOT a sensor chip!)
Next adapter: cen_80000015_e0p0 (i2c-3)
Do you want to scan it? (YES/no/selectively): Client found at address 0x1a
Probing for Analog Devices ADM1021'...                     No Probing for Analog Devices ADM1021A/ADM1023'...            No
Probing for Maxim MAX1617'...                              No Probing for Maxim MAX1617A'...                             No
Probing for Maxim MAX1668'...                              No Probing for Maxim MAX1805'...                              No
Probing for Maxim MAX1989'...                              No Probing for Maxim MAX6655/MAX6656'...                      No
Probing for TI THMC10'...                                  No Probing for National Semiconductor LM84'...                No
Probing for Genesys Logic GL523SM'...                      No Probing for Onsemi MC1066'...                              No
Probing for Maxim MAX1618'...                              No Probing for Maxim MAX1619'...                              No
Probing for National Semiconductor LM82/LM83'...           No Probing for Maxim MAX6654'...                              No
Probing for Maxim MAX6690'...                              No Probing for Maxim MAX6680/MAX6681'...                      No
Probing for Maxim MAX6695/MAX6696'...                      No Probing for Texas Instruments AMC6821'...                  No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                Success!     (confidence 5, driver jc42')
Probing for ST STTS3000'...                                No Probing for NXP SE97/SE97B'...                             No
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x1b Probing for ST STTS424'...                                 No
Probing for ST STTS424E'...                                No Probing for ST STTS2002'...                                Success!
(confidence 5, driver jc42') Probing for ST STTS3000'...                                No
Probing for NXP SE97/SE97B'...                             No Probing for NXP SE98'...                                   No
Probing for Analog Devices ADT7408'...                     No Probing for IDT TS3000/TSE2002'...                         No
Probing for Maxim MAX6604'...                              No Probing for Microchip MCP9804'...                          No
Probing for Microchip MCP98242'...                         No Probing for Microchip MCP98243'...                         No
Probing for Microchip MCP98244'...                         No Probing for Microchip MCP9843'...                          No
Probing for ON CAT6095/CAT34TS02'...                       No Probing for Atmel AT30TS00'...                             No
Client found at address 0x1c
Probing for Texas Instruments TMP421'...                   No Probing for SMSC EMC1072'...                               No
Probing for SMSC EMC1073'...                               No Probing for SMSC EMC1074'...                               No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                Success!     (confidence 5, driver jc42')
Probing for ST STTS3000'...                                No Probing for NXP SE97/SE97B'...                             No
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x1d Probing for Texas Instruments TMP421'...                   No
Probing for ST STTS424'...                                 No Probing for ST STTS424E'...                                No
Probing for ST STTS2002'...                                Success!     (confidence 5, driver jc42')
Probing for ST STTS3000'...                                No Probing for NXP SE97/SE97B'...                             No
Probing for NXP SE98'...                                   No Probing for Analog Devices ADT7408'...                     No
Probing for IDT TS3000/TSE2002'...                         No Probing for Maxim MAX6604'...                              No
Probing for Microchip MCP9804'...                          No Probing for Microchip MCP98242'...                         No
Probing for Microchip MCP98243'...                         No Probing for Microchip MCP98244'...                         No
Probing for Microchip MCP9843'...                          No Probing for ON CAT6095/CAT34TS02'...                       No
Probing for Atmel AT30TS00'...                             No Client found at address 0x52 Handled by driver at24' (already loaded), chip type 24c02'     (note: this is probably NOT a sensor chip!) Client found at address 0x53 Handled by driver at24' (already loaded), chip type `24c02'
(note: this is probably NOT a sensor chip!)
Next adapter: p8_00000000_e0p0 (i2c-4)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Handled by driver at24' (already loaded), chip type 24c128'
(note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver at24' (already loaded), chip type 24c128'
(note: this is probably NOT a sensor chip!)
Next adapter: p8_00000000_e0p1 (i2c-5)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Handled by driver at24' (already loaded), chip type 24c128'
(note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver at24' (already loaded), chip type 24c128'
(note: this is probably NOT a sensor chip!)
Next adapter: p8_00000000_e1p2 (i2c-6)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Handled by driver at24' (already loaded), chip type 24c128'
(note: this is probably NOT a sensor chip!)
Next adapter: p8_00000001_e0p0 (i2c-7)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Handled by driver at24' (already loaded), chip type 24c128'
(note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver at24' (already loaded), chip type 24c128'
(note: this is probably NOT a sensor chip!)
Next adapter: p8_00000001_e0p1 (i2c-8)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Handled by driver at24' (already loaded), chip type 24c128'
(note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver at24' (already loaded), chip type 24c128'
(note: this is probably NOT a sensor chip!)
Next adapter: AST i2c bit bus (i2c-9)
Do you want to scan it? (yes/NO/selectively):
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `jc42':

Bus cen_80000004_e0p0' Busdriver UNKNOWN', I2C address 0x1a
Chip `NXP SE97/SE97B' (confidence: 5)
Bus cen_80000004_e0p0' Busdriver UNKNOWN', I2C address 0x1b
Chip `NXP SE97/SE97B' (confidence: 5)
Bus cen_80000004_e0p0' Busdriver UNKNOWN', I2C address 0x1c
Chip `NXP SE97/SE97B' (confidence: 5)
Bus cen_80000004_e0p0' Busdriver UNKNOWN', I2C address 0x1d
Chip `NXP SE97/SE97B' (confidence: 5)
Bus cen_80000005_e0p0' Busdriver UNKNOWN', I2C address 0x1a
Chip `ST STTS2002' (confidence: 5)
Bus cen_80000005_e0p0' Busdriver UNKNOWN', I2C address 0x1b
Chip `ST STTS2002' (confidence: 5)
Bus cen_80000005_e0p0' Busdriver UNKNOWN', I2C address 0x1c
Chip `NXP SE97/SE97B' (confidence: 5)
Bus cen_80000005_e0p0' Busdriver UNKNOWN', I2C address 0x1d
Chip `NXP SE97/SE97B' (confidence: 5)
Bus cen_80000014_e0p0' Busdriver UNKNOWN', I2C address 0x1a
Chip `ST STTS2002' (confidence: 5)
Bus cen_80000014_e0p0' Busdriver UNKNOWN', I2C address 0x1b
Chip `ST STTS2002' (confidence: 5)
Bus cen_80000014_e0p0' Busdriver UNKNOWN', I2C address 0x1c
Chip `ST STTS2002' (confidence: 5)
Bus cen_80000014_e0p0' Busdriver UNKNOWN', I2C address 0x1d
Chip `ST STTS2002' (confidence: 5)
Bus cen_80000015_e0p0' Busdriver UNKNOWN', I2C address 0x1a
Chip `ST STTS2002' (confidence: 5)
Bus cen_80000015_e0p0' Busdriver UNKNOWN', I2C address 0x1b
Chip `ST STTS2002' (confidence: 5)
Bus cen_80000015_e0p0' Busdriver UNKNOWN', I2C address 0x1c
Chip `ST STTS2002' (confidence: 5)
Bus cen_80000015_e0p0' Busdriver UNKNOWN', I2C address 0x1d
Chip `ST STTS2002' (confidence: 5)

To load everything that is needed, add this to /etc/modules:
#----cut here----
Chip drivers
jc42
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)

Warning: the preferred way to run this script non-interactively
is with option --auto. Other methods are discouraged and may
stop working at some point in the future.

===> I did sudo apt-get install lm-sensors and lm-sensors seems to be running
root@g68L:/etc/init.d# ps -eaf | grep lm-sensors
root       3525   3501  0 13:10 pts/0    00:00:00 grep --color=auto lm-sensors
===> but when i run the "sensors; echo $?" command it fails
root@g68L:/etc/init.d# sensors; echo $?
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
1

my issue is i am unable to check  sensors command functionality with different options
I doubt that lm-sensors are not properly configured
can u plz share the procedure how to configure lm-sensors

Can you check if you can install Ubuntu 16.04 or 14.04.03 release and try to execute the sensors command, since they are LTS releases and also we had executed these tests on them.
Also, you can try on Ubuntu 15.04 by giving the command:
apt-get install lm-sensors  ==> this will install the lm-sensors package
lm-sensors is not a process which you can verify through "ps -eaf | grep lm-sensors" command as you have tried. This is just a package which has the utility or command sensors-detect, sensors etc.

In my previous comment i have mentioned already that i could do 'apt-get install lm-sensors' ....and sensors seems to be not working....this is my issue

You can raise a defect for the sensors command not working for Ubuntu 15.04 OS release which you have installed here. Then the development team can look into the same and comment.

There's been a lot of rework happen in op-test-framework since this was opened, which I believe solves this issue by automatically loading the appropriate drivers if needed.
I'm going to open a separate issue to track the issue of how sensor tests could pass even if no (or too few) sensors are detected.


Future feature: adapt the homepage for operators and admins

Right now the same homepage as per users is shown to operators and admins
It should probably be different, even if I can't really say how
Probably showing management pages first

Fixed via<PHONE_NUMBER>71c931f512a2bbe3c419d44accf2f8


Question: how to cloak on inital load?

Do NOT ignore this template or your issue will have a very high chance to be closed without comment.

Describe the bug
A clear and concise description of what the bug is.
Hi, I apologize in advance for opening issue as a "bug". I also apologize in advance if this comes across as nit-picking. The intentions are good here.
This may be best under a "question" template. First the good: yes, the HMR is pretty awesome. My question is, on my initial page load, I see what appears to be "basic HTML" content (unstyled), and then in a blink of an eye, it's style correctly. It appears that even with v-cloak on a root elem it isn't applying the style.

The flicker is only for a really short time, and from my experience only occurs on initial page load, subsequent reloads are instant. So the DX improvement is awesome. Also, from my first experience, the flicker is only in dev mode, not in the production build. So a bit of relief there.
Reproduction
Please provide a link to a repo that can reproduce the problem you ran into.
A reproduction is required unless you are absolutely sure that the the problem is obvious and the information you provided is enough for us to understand what the problem is. If a report has only vague description (e.g. just a generic error message) and has no reproduction, it will be closed immediately.
Wrap with "v-cloak"
<template>
  <div v-cloak>
    <img alt="Vue logo" src="./logo.png" />
    <HelloWorld msg="Hello Vue 3.0 + Vite" />
  </div>
</template>

<style scoped>
[v-cloak] {
  display: none;
}
</style>

## System Info

- **required** `vite` version: 0.15.0
- **required** Operating System: Debian Linux 9.9
- **required** Node version: 12.16.3
- Optional:
  - npm/yarn version: npm v6.14.4
  - Installed `vue` version (from `yarn.lock` or `package-lock.json`) 3.0.0-beta.12
  - Installed `@vue/compiler-sfc` version 3.0.0-beta.12

## Logs (Optional if provided reproduction)

1. Run `vite` or `vite build` with the `--debug` flag.
2. Provide the error log here.

Builds were successful.

Bug template should probably also have browser version. Chromium v73.

This is because in development everything is loaded via es module imports, including the css. Because Imports are async, the css is only inserted after they are fetched.
The only way around this would be pre-collecting all the CSS and insert them before any rendering happens - which requires a full bundling process (exactly what we are trying to avoid).
In production, all the CSS is extracted into a single file and inserted via static links, so they are guaranteed to load before the render.


Lab 4 - DAX - Missing the instructions to create additional measures that will be later required in lab 6

Module: 05
Lab/Demo: 04
Task: 02
Step: all
Description of issue
Exercise 2: Create Measures > Task 2: Create additional measures has been removed from PL-300 lab (https://github.com/MicrosoftLearning/DA-100-Analyzing-Data-with-Power-BI/blob/master/Instructions/Labs/05-create-dax-calculations-in-power-bi-desktop.md#task-2-create-additional-measures). However, there is a dependency on the measures created in this task in the Report Lab > Exercise 1: Create a Report > Task 6: Design page 3 > Step 7 (https://github.com/MicrosoftLearning/PL-300-Microsoft-Power-BI-Data-Analyst/blob/Main/Instructions/06-design-report-in-power-bi-desktop.md#task-6-design-page-3)

MOC Labs Review did not experience this issue.

These have been added back into the lab.


RaGOO out visualization

Hi Michael!
Thank you for the super-fast RaGOO algorithm!
Do you have any good solutions for fast RaGOO out visualization?
Do you have any idea how to visualize
contigs_against_ref.paf
and the files from /groupings /orderings?
Thank you in advance!
Best regards,
Ural

Hi there,
Were you thinking something along the lines of a dotplot like mummerplot or assemblytics? Those both require base level alignments so the contigs_against_ref.paf can't be used for those. Dotplots cant be easily made in R or python, but the tricky part is displaying the many contigs against the many reference chromosomes.
Or maybe you had some other visualization in mind?

Hi,
I would be interested in visualising structural variation from Ragoo's output.
Thank you in advance,
Michal

Yes, I had in mind the visualization of the contigs_against_ref.paf
Oh! Yes, we are thinking in the same direction. I am also going to visualize SV from Ragoo's output. My plan is to align Nanopore reads to ragoo.fasta then visualize the ragoo.fasta.bam using Ribbon.
What do you think about this plan? Is there any other way to visualize SVs?

Hi there,
To answer your question more specifically, I wonder what relationship you want to study. It sounds like you want to use ragoo.fasta as a reference genome and use nanopore reads from other samples to call SVs with respect to ragoo.fasta. Is that right? One could also look at SVs in ragoo.fasta with respect to another reference.

First, I want to visualize the synteny between the target contigs and guide chromosome, then between the target contigs and output chromosome. Like this:
Guide  chr  ===============================  ragoo/in/reference.fasta
            |||  ||||||  |||  |  ||||||||||

Target cont ===  ======  ===  =  ==========  ragoo/in/contigs.fasta
            |||  ||||||  |||  |  ||||||||||
Output chr  ===============================  ragoo/out/ragoo.fasta

Did you try minimap2 with paftools.js ? That will give that type of output of pairwise alignment on large scale.
If you want too see dot plot, D-GENIES works well http://dgenies.toulouse.inra.fr/
Jason Stajich, PhD
<EMAIL_ADDRESS>On Dec 2, 2019, 11:18 PM -0800, Ural Yunusbaev , wrote:

First, I want to visualize the synteny between the target contigs and guide chromosome, then between the target contigs and output chromosome. Like this:
Guide  chr  ===============================  ragoo/in/reference.fasta
|||  ||||||  |||  |  ||||||||||
Target cont ===  ======  ===  =  ==========  ragoo/in/contigs.fasta
|||  ||||||  |||  |  ||||||||||
Output chr  ===============================  ragoo/out/ragoo.fasta
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi, I was able to  get Assemblytics running with:
> cd ragoo_output/
> gzip pm_alignments/pm_against_ref.sam.delta
Upload the gz file to http://assemblytics.com/

However, does RaGOO has any script for SplitThreader?
Thank you in advance,
Michal

ragoo_output/

gzip pm_alignments/pm_against_ref.sam.delta

Hi Michal! But how did you obtain pm_against_ref.sam.delta using ragoo?
Thank you in advance,
Ural

@mictadlo For SplitThreader, it looks like you need a VCF file and a CNV file. You can convert the assemblytics output format to VCF format using SURVIVOR. I am not sure about the CNV file.


⚠ 한경주요지수-코스피200 has degraded performance

In 0be7ba5, 한경주요지수-코스피200 (https://markets.hankyung.com/indices/kospi200) experienced degraded performance:

HTTP code: 200
Response time: 5171 ms

Resolved: 신규상장 performance has improved in e9ab8b2.


Add reference to http://www.osmhydrant.org

In the new help button on the hydrants page, maybe add a reference to http://www.osmhydrant.org after the link to the openfiremap wiki.
I think that http://www.osmhydrant.org provides a very easy to use interface for adding hydrants etc.

Hi, thanks! Does a change on osmhydrant.org affect OpenFireMap entries?

Hi,
yea, osmhydrand.org is just an easy frontend to add hydrants et al. to openstreetmap.org.
Openfiremap.org takes all hydrants from openstreetmap and renders an overlay map.
Thanks,
Philipp
Am 4. November 2015 20:15:11 MEZ, schrieb Alex Gassner<EMAIL_ADDRESS>
Hi, thanks! Does a change on osmhydrant.org affect OpenFireMap entries?

Reply to this email directly or view it on GitHub:
https://github.com/Grisu-NOE/mobile-app/issues/97#issuecomment-153834851

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Ok nice to know :) I saw you forked the project, please be cool and create a first pull request :+1:


EC group initialization overly expensive and uncached in TLS layer

When generating an ECDH keypair, the TLS layer calls ssl_pkey_generate_group that then calls EVP__PKEY_generate. This turns into provider call that end up in ec_gen. Unfortunately ec_gen does not have a group to work with and calls EC_GROUP_new_by_curve_name_ex (after some intermediates) which ends up spending a good amount of time in BN_MONT_CTX related calls and BN_mod inverse for the order of the group.
This takes up as much time as the ecp_nistz256_points_mul used to make the keypair, and it isn't clear how to avoid this inefficiency given the overall design. At one extreme would be exposing ECDH as a pseudo-KEM to the TLS layer, and then implementing directly on top of nistz_* calls, but this is a big departure from the current provider. Alternatively the TLS layer could somehow cache the group, but the parameter interface to the key generation makes this tricky.
It's not clear to me why BN_MONT_CTX is a good idea in the group https://eprint.iacr.org/2019/266 shows a much faster modular inversion for ECDSA, and other groups have inversion free signatures, but that doesn't help with the FIPS provider that exists.

Could we not somehow cache the calculated group values somewhere in the ec layer? i.e. so next time EC_GROUP_new_by_curve_name_ex() is called we just return the pre-cached group (or possibly a copy of it).

I don't think the EC function call have a place to put that cache but the provider context would. Now to do this efficiently without another read-write lock mess...

I don't think the EC function call have a place to put that cache but the provider context would.

It could be done in the libctx potentially. But, yeah, provider context would also work.

Now to do this efficiently without another read-write lock mess...

Atomic store/load of a pointer?

or possibly a copy of it

EC_GROUPs are not ref counted and I'm not sure to what extent they are thread safe so we might need to be careful here.

EC_GROUPs are not ref counted and I'm not sure to what extent they are thread safe so we might need to be careful here.

Indeed there are a few API issues that may get in the way here. :-( Quite a lot of the EC_GROUP API is mutable. Run git grep '(EC_GROUP' in include/openssl to see all the non-const methods. Many of them are initialization functions, like EC_GROUP_set_generator, which you may be able to ignore. (Though it's a bit ambiguous. #5158 strikes again!) But some like EC_GROUP_set_asn1_flag and EC_GROUP_set_point_conversion_form are actually really really bad APIs for callers to pass in options that should have been passed in more straightforwardly. E.g., you use EC_GROUP_set_asn1_flag to request explicit curve encoding in i2d APIs.
That means that, even if locked, two unrelated components cannot share an EC_GROUP without interfering with each other. They'd have to, at best, share some internal, immutable subset of the EC_GROUP. Mutability can be pretty problematic.
It is possible to subset the APIs down to avoid this problem. BoringSSL turns some of those setters into no-ops or aborts—in practice, no one calls EC_GROUP_set_point_conversion_form except with POINT_CONVERSION_UNCOMPRESSED and EC_GROUP_set_asn1_flag is used to request explicit curve encoding, which is always, always a bad idea. That has allowed us to make the built-in curves static and shared. Our setup is not quite right (we still lazily initialize it, and I used a silly synchronization primitive), but our immutability and focus on named curves avoid it being a problem. (And I have some changes in progress to clear the remaining issues.)
But that's likely not within OpenSSL's stability goals, so it's not an immediate option. But I point that out because it means OpenSSL can consider deprecating the problematic APIs. (If BoringSSL finds an API problematic enough to warrant these sorts of antics, it's probably also problematic enough for OpenSSL to warrant a removal long-term.)

Could we just precompute these values for the NIST  FIPS curves and have them statically initialized? I.e., do not change any EC_GROUP internal mechanics in regards to mutability/caching but for the well-known curves instead of computing the values copy them from read-only data?

I think so, but I also think these values aren't actually used by the efficient NIST implementations. So in a no-asm case we need them, but that's not where we really have this problem because everything else is slow. But that's a more radical change than keeping them, just including them in the precomputed data.

I've looked more into @t8m's suggestion and it seems to me that it would require extending the method struct as the current way of doing things just passes p, a, b into the set_curve method and additional parameters in the data aren't passed in. So perhaps we have an initialization function in the method that takes the data, but then we have some more close coupling with the group struct.

Looks like some of the issue is downstream of Issue #21351

@romen FYI

I'm working on a patch to permit precomputation and an implementation for the nist curve. Will submit PR after I test that it works for our application.

Should this be triaged performance? Have not forgotten the patch I promised to push up: things have gotten in way

Yes, well spotted.  I've tagged it.