Heatmap support on ElasticSearch

docker hub terranodo/elasticsearch:heatmap
https://github.com/o19s/elasticsearch/tree/feature/heatmap

I think I am having errors related with the geoheatmap work.
...elasticsearch/core/src/main/java/org/elasticsearch/search/aggregations/bucket/geoheatmap/GeoHeatmapAggregationBuilder.java:97: warning: no description for @throws
     * @throws IOException
       ^
error: warnings found and -Werror specified
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
4 warnings
:core:compileJava FAILED

looking into it.

they made some fixes here but not applied to the GeoHeatmapAggregationBuilder.java class. commenting code btw GeoHeatmapAggregationBuilder.java:94-98.

@ingenieroariel just wondering why:
master has a folder: geoheatmap:
https://github.com/o19s/elasticsearch/tree/master/core/src/main/java/org/elasticsearch/search/aggregations/bucket
feature/heatmap not:
https://github.com/o19s/elasticsearch/tree/feature/heatmap/core/src/main/java/org/elasticsearch/search/aggregations/bucket

I'll point the main author of the feature branch at this thread. Thanks
Luis.
On Sep 12, 2016 4:03 PM, "Luis Pallares"<EMAIL_ADDRESS>wrote:

@ingenieroariel https://github.com/ingenieroariel just wondering why:
master has a folder: geoheatmap:
https://github.com/o19s/elasticsearch/tree/master/core/src/main/java/org/
elasticsearch/search/aggregations/bucket
feature/heatmap not:
https://github.com/o19s/elasticsearch/tree/feature/
heatmap/core/src/main/java/org/elasticsearch/search/aggregations/bucket
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cga-harvard/HHypermap/issues/204#issuecomment-246492524,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADW1w92DeaZjXoUUCJj3eY-qCb9ib3lks5qpb4RgaJpZM4J5aHb
.

@panchicore, we had been collecting document "hits" on the heatmap (so that would be a bucket aggregation), but since the Lucene heatmap doesn't keep track of this at all there's no reason for us to do that, and there's a margin for error.
Instead we decided to use the metrics aggregation type, and so we moved the classes from the bucket package to the metrics package:
https://github.com/o19s/elasticsearch/tree/feature/heatmap/core/src/main/java/org/elasticsearch/search/aggregations/metrics/geoheatmap

@sstults good to know.
@sstults do you have query samples about how to filter with that aggregation type?
our docs has this mapping:
mapping = {
            "mappings": {
                "layer": {
                    "properties": {
                        "layer_geoshape": {
                           "type": "geo_shape",
                           "tree": "quadtree",
                           "precision": REGISTRY_MAPPING_PRECISION
                        }
                    }
                }
            }
        }

so we will be creating heatmaps from the layer_geoshape geo shape.
I was looking into the documentation and found geohash aggregations but in my tests it only works with geo_point type, not with the geo_shape one.
but I realize that maybe I will find the implementation by looking in the geoheatmap tests: https://github.com/o19s/elasticsearch/tree/feature/heatmap/core/src/test/java/org/elasticsearch/search/aggregations/metrics/geoheatmap
thanks in advance.

Correct - there aren't any aggregations so far that support geo_shape types.
Right now we've got two layers to restrict the bounds on the heatmap. The first is through normal query/filter parameters. So if you execute a regular geo_shape query or filter and look at the resulting documents, those are what would be passed to the heatmap agg.
The heatmap itself is another way to restrict what gets into the heatmap. There's a "geom" parameter that takes a geo_shape query as another filter. So for example you could do a top-level query for things in a country, and then use the geom field in the agg to restrict to a particular city.
Something like this:
{
    "query": {
        "geo_shape": {
            "location": {
                "shape": {
                    "type": "envelope",
                    "coordinates" : [[-50.0, 43.0], [50.0, 44.0]]
                },
                "relation": "within"
            }
        }
    },
    "aggs" : {
        "viewport" : {
            "heatmap" : {
                "field" : "location",
                "grid_level" : 4,
                "max_cells" : 100,
                "geom" : {
                    "geo_shape": {
                        "location": {
                            "shape": {
                                "type": "envelope",
                                "coordinates" : [[-30.0, 30.0], [40.0, -30.0]]
                            },
                            "relation": "within"
                        }
                    }
                }
            }
        }
    }
}

The actual coordinates above are silly, but hopefully you get the idea.

with 350 layers where the majority covers entire earth.
the following is the query I am running against es5.0 feature/heatmap:
{
    "sort":{
        "_score":{
            "order":"desc"
        }
    },
    "query":{
        "bool":{
            "filter":{
                "geo_shape":{
                    "layer_geoshape":{
                        "shape":{
                            "type":"envelope",
                            "coordinates":[
                                [
                                    "-180.0",
                                    "90.0"
                                ],
                                [
                                    "180.0",
                                    "-90.0"
                                ]
                            ]
                        },
                        "relation":"intersects"
                    }
                }
            }
        }
    },
    "from":0,
    "aggs":{
        "viewport":{
            "heatmap":{
                "field":"layer_geoshape",
                "geom":{
                    "geo_shape":{
                        "layer_geoshape":{
                            "shape":{
                                "type":"envelope",
                                "coordinates":[
                                    [
                                        "-180.0",
                                        "90.0"
                                    ],
                                    [
                                        "180.0",
                                        "-90.0"
                                    ]
                                ]
                            },
                            "relation":"intersects"
                        }
                    }
                },
                "grid_level":3,
                "max_cells":18432
            }
        }
    }
}

getting as result:

{
    "a.hm":{
        "minX":-180.0,
        "minY":-90.0,
        "maxX":180.0,
        "rows":8,
        "projection":"EPSG:4326",
        "counts_ints2D":[
            [
                [
                    350,
                    311,
                    342,
                    350,
                    350,
                    350,
                    350,
                    350
                ]
            ],
            [
                [
                    350,
                    311,
                    342,
                    350,
                    350,
                    350,
                    350,
                    350
                ]
            ],
            [
                [
                    350,
                    311,
                    342,
                    350,
                    350,
                    350,
                    350,
                    350
                ]
            ],
            [
                [
                    322,
                    311,
                    314,
                    322,
                    322,
                    322,
                    322,
                    322
                ]
            ],
            [
                [
                    320,
                    309,
                    312,
                    320,
                    320,
                    320,
                    320,
                    320
                ]
            ],
            [
                [
                    316,
                    309,
                    310,
                    316,
                    316,
                    316,
                    316,
                    316
                ]
            ],
            [
                [
                    309,
                    309,
                    309,
                    309,
                    309,
                    309,
                    309,
                    309
                ]
            ],
            [
                [
                    309,
                    309,
                    309,
                    309,
                    309,
                    309,
                    309,
                    309
                ]
            ]
        ],
        "gridLevel":3,
        "maxY":180.0,
        "columns":8
    },
...
}

(thats a transformed response from the original response)
the findings in that response versus the solr response with the same 350 layers are:

ES returns rows:8 colums:8 square. Solr returns rows:4 colums:8 rect.
ES was set to gridLevel=3. Solr was set to 1. ES with 1 returned a rows:2 columns:2 matrix, so I incremented the gridLevel to get nearest result to Solr.
columns: Solr values are contained in ES values.

es[0]==solr[0]
es[1]==solr[1]
es[4]==solr[2]
es[5]==solr[3]
here Solr results:

{
    "a.hm":{
        "minX":-180.0,
        "minY":-90.0,
        "maxX":180.0,
        "rows":4,
        "projection":"EPSG:4326",
        "counts_ints2D":[
            [
                350,
                311,
                342,
                350,
                350,
                350,
                350,
                350
            ],
            [
                350,
                311,
                342,
                350,
                350,
                350,
                350,
                350
            ],
            [
                320,
                309,
                312,
                320,
                320,
                320,
                320,
                320
            ],
            [
                309,
                309,
                309,
                309,
                309,
                309,
                309,
                309
            ]
        ],
        "gridLevel":1,
        "maxY":90.0,
        "columns":8
    }
}

@ingenieroariel @sstults  thoughts?
@ingenieroariel reference for us:
solr: http://localhost:8000/registry/hypermap/api/?a.hm.gridlevel=1&a.hm.limit=1&a.text.limit=0&a.time.gap=P1D&a.time.limit=0&a.user.limit=0&d.docs.limit=0&d.docs.page=1&d.docs.sort=score&format=json&original_response=0&q.geo=%5B-90%2C-180+TO+90%2C180%5D&q.time=%5B1900-01-01+TO+2016-12-31T00%3A00%3A00%5D
es: http://localhost:8000/registry/hypermap/api/?a.hm.gridlevel=3&a.hm.limit=1&a.text.limit=0&a.time.gap=P1D&a.time.limit=0&a.user.limit=0&d.docs.limit=0&d.docs.page=1&d.docs.sort=score&format=json&original_response=0&q.geo=%5B-90%2C-180+TO+90%2C180%5D&q.time=%5B1900-01-01+TO+2016-12-31T00%3A00%3A00%5D

It could be a bug in how we're converting the counts to JSON -- that's the very last functionality I added. The internal array should be the same since I'm doing exactly the same thing as Solr. One difference could be in the underlying field definition. Can you tell me how layer_geoshape is defined in both Solr and ES?
By the way, score doesn't have meaning in strictly geo_shape queries so sorting might use memory and time unnecessarily. But if you're combining the geo_shape query with some sort of text query then score will matter.

@sstults,
in Solr we declare the field like this:
{"name": "bbox", "type": "location_rpt"},

that is what shows the eschema explorer:

Field-Type:org.apache.solr.schema.SpatialRecursivePrefixTreeFieldType
with ES we have this mapping at the moment of the indice creation:
"mappings": {
                "layer": {
                    "properties": {
                        "layer_geoshape": {
                           "type": "geo_shape",
                           "tree": "quadtree",
                           "precision": REGISTRY_MAPPING_PRECISION
                        }
                    }
                }
            }

http://localhost:9200/hypermap/_mapping/layer shows
"layer_geoshape":{
                        "type":"geo_shape",
                        "tree":"quadtree",
                        "precision":"500.0m"
                    }

that is the complete response json.
solr SpatialRecursivePrefixTreeFieldType == es geo_shape quadtree ?
what do you think?

btw, thanks for the annotation about the score sorting.

@panchicore, check out minX, minY, maxX, and maxY between the two responses. I think you need to switch the coordinates. I'm looking for a good reference on GeoJSON now, but the only thing I've found is this, and it doesn't describe the coordinate order for Envelope:
http://wiki.geojson.org/GeoJSON_draft_version_5#Including_Bounding_Box.2FEnvelope

@sstults,
ENVELOPE Catalogue Service Specification, I know because this thread here.
What happens if I switch the coords?

{

    "query":{
        "bool":{
            "filter":{
                "geo_shape":{
                    "layer_geoshape":{
                        "shape":{
                            "type":"envelope",
                            "coordinates":[
                                [
                                    "-180.0",
                                    "-90.0"
                                ],
                                [
                                    "180.0",
                                    "90.0"
                                ]
                            ]
                        },
                        "relation":"intersects"
                    }
                }
            }
        }
    },
    "from":0,
    "aggs":{
        "viewport":{
            "heatmap":{
                "field":"layer_geoshape",
                "geom":{
                    "geo_shape":{
                        "layer_geoshape":{
                            "shape":{
                                "type":"envelope",
                                "coordinates":[
                                    [
                                        "-180.0",
                                        "-90.0"
                                    ],
                                    [
                                        "180.0",
                                        "90.0"
                                    ]
                                ]
                            },
                            "relation":"intersects"
                        }
                    }
                },
                "grid_level":3,
                "max_cells":18432
            }
        }
    }
}

the response is exactly the same.
in case you want to dump the 350 layers, you can download them here. I got it with http://localhost:9200/hypermap/_search?size=400
what do you think?

@sstults I will prepare a test script for you to know about the responses expected from some queries taking as base reference the solr responses. WIP.

@panchicore, I think I found the error. Have a look at the change I just posted in the patch to views.py.

ok. I will check and let you know today.
https://github.com/sstults/HHypermap/commit/429a82985f50baa4511cb32d79d5d6fed41d6457

@sstults thanks for the feedback. You found an error when the ES output is extracted to match with the response model, that error does not affect:

the input: the data sent to ES is the same that is being sent to Solr.
the throughput: the process is based in the information here:  https://github.com/sstults/HHypermap/blob/429a82985f50baa4511cb32d79d5d6fed41d6457/hypermap/search_api/views.py#L261 where geo shape envelope coords are set OK.

Anyways, I re runned the tests and your finding is not conclusive and does not affect the results of my prev comments.
I will send you a python script with some tests in order to you know what we spec for ES.
thanks in advance,
Luis.

Correct. I was concerned that maybe the bounding box coordinates weren't being sent in the right order, but it looks like the error was just in the output.
With respect to the extra column, I ran into something similar in my unit test and that was actually an indexing problem. I was reproducing a Lucene test that indexed an envelope like this:
ENVELOPE(100, 120, 80, 40)

My mistake was in taking the values in pairs:
"shape": {
                            "type": "envelope",
                            "coordinates" : [[100, 120], [80, 40]]
                }

When instead Solr puts the longitudes first, followed by the latitudes. So in ES my envelope should be:
"shape": {
                            "type": "envelope",
                            "coordinates" : [[100, 80], [120, 40]]
                }

It looks like the agg is built correctly in views.py, but I'm wondering if the indexing code mixes up the value order. Can you point me to where that would be?
Anyway, when I corrected the value order in the indexed docs in my own test I ended up with exactly the same output as the core Solr unit test, so that's encouraging.

@panchicore, I've submitted the PR to the main ES project based off of a copy of the code we've been working on. Everything's the same except there's no CircleCI and I added another unit test. Here's the fork I submitted:
https://github.com/sstults/elasticsearch
And here are the PR and Ticket
I'm not really sure whether we should keep working off of the o19s fork or the sstults fork, or if we can use the actual PR. Do you have a suggestion?

@sstults I dont know what suggestion give. I am just compiling those sources (https://github.com/o19s/elasticsearch/tree/feature/heatmap) and running my tests. so, you mean I must clone your repo to make the tests?

@sstults we need pick the grid level indirectly; we dont always specify a heatmap grid level, we calculate the distErr from the viewport rectangle and provide to solr a facet.heatmap.distErr parameter. see here: https://github.com/cga-harvard/HHypermap/blob/master/hypermap/search_api/utils.py#L279
Any posibility to make it work in your branch?

@panchicore let's move our build to use the branch on this repo: https://github.com/sstults/elasticsearch
For now let's use a fixed grid level if distErr is not supported.

That particular formula was, I believe, lifted from my HHypermap BOP web-service (Kotlin code)?  I think it's only valid for a quad-tree, by the way.  Consider it a best-effort estimate.

thats an update from the heatmap implementation in both backends.

I set gridlevel 7 in elasticsearch because I wanted to match the heatmap intensity with the solr one.
@dsmiley @sstults the gridlevel integer, its a standart value? I mean, both backends should give me the same gridlevel from exactly the same query?
If I manualy set gridlevel 7 to elasticsearch, it will result a less intense heatmap, what I think looks better.

see the difference btw counts_ints2D and the columns count. why are so different but the map is drawing the same heatmap?

@ingenieroariel and @panchicore: I added distErr and distErrPct parameters to the heatmap as they're implemented in Solr, and in testing I've found something odd which may have the same root cause as the column disparity above.
The unit test I made follows the same logic as the Solr unit test and uses the same parameter values. However, when I use geom + dist_err_pct parameters, and when I use geom + dist_err_pct parameters, I'm getting a computed grid_level that's one less than expected. When I use the default geom though (the world rect) and dist_err_pct I get the expected value.
There are a couple of units conversions that could be throwing things off. The default units in Solr are degrees, whereas it looks like ES wants to use meters. I'm looking into whether or not this impacts the grid level calculation.
Would it be best for me to commit what I have now and follow up on the discrepancy at a later date?

I agree it'sbest to commit what's there and worry about the discrepancy later.

We can switch Solr to use meters instead I believe without much trouble.


University official url:           https://www.nvcc.edu/

IT related (> 1 year) program url: https://catalog.nvcc.edu/preview_program.php?catoid=2&poid=194&returnto=62
University recognised domain:      https://www.nvcc.edu/ithd/students/email/index.html

@bishoyshaheer I am sorry, this domain is blacklisted because the college allows to register an email address there even if you are not a student of the college. If you are the student of this college, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


Add support for Nexmo Short Codes

https://www.nexmo.com/platform/short-codes
Currently all SMS messages from Nexmo have a phone number. I want to be able to use their Short Code API so messages could come from a short code like 888-111

There are two types of short codes:

2FA
Alerts

Here is the API call for alerts: https://rest.nexmo.com/sc/us/alert/json?api_key={$your_key}&api_secret={$your_secret}&to={$to}&key1={$value1}&key2={$value2}

Feel free to send in a PR that doesn't breaks too much.

This was merged a while ago


Why have two incompatible Bytes modules (FStar.Bytes and Platform.Bytes) and do they need to be named the same way?

Type-checking the following code:
val code_length : ss:(list (symbol * pos)) -> cs:(list bytes) -> Pure nat
  (requires (sorted ss /\ List.Tot.length cs == List.Tot.length ss))
  (ensures (fun _ -> True))
let code_length ss cs =
  fold_left2 (fun (a:nat) (sw:symbol*pos) c ->
              let (s,w) = sw in a + w `op_Multiply` (Bytes.length c)) 0 ss cs

is giving me a dubious typing error:
[hritcu@detained algorithms]$ fstar.exe --include ../../ucontrib/Platform/fst --print_implicits --print_universes --log_queries Huffman.fst
./Huffman.fst(19,75-19,77) : (Error) Expected expression of type "(Prims.list<?151930> FStar.Bytes.bytes)"; got expression "cs" of type "(Prims.list<0> Platform.Bytes.bytes)"

So I looked in the debugger and it seems the error is still bogus, but a bit more explicit before the normalization the printing now does by default.

The computed type of the expression (Prims.list<?151930> ((fun ss cs -> (FStar.Bytes.bytes $$ Tot Type(?151930))) ss cs)) is 2 eta reduction steps away from the required type Prims.list<0> Platform.Bytes.bytes), but F* only eta reduces this when printing the error message.
At least this is my understanding of this after staring at it for a while.

Just realized that Bytes.length was pointing to FStar.Bytes (one Bytes implementation in F* is of course not enough) and that removing the Bytes prefix makes the error go away. Argh!!!

I joined the club today.

Bumping this to high priority. I think this is particularly important right now, as we start rolling out the new parser combinators, which operate mainly on bytes (but currently neither Platform.Bytes.bytes nor FStar.Bytes.bytes).

Platform.Bytes is now moved out to ucontrib. Perhaps we should now remove it altogether


Openglexample modernized

this updates the opengl example with a bunch of useful stuff.

it sets the window based on the HMD reported resolution
it uses the universal shader
it adds crosshairs which you can use to estimate lens_sep on cv1 style adjustable IPD displays
it allows disabling lens distortion
it allows adjusting the distortion scale, in case of calibration FoV mismatches

Looks good. Gotta test it though. We also have another PR with SDL2 etc. Perhaps we should merge these changes with that PR?

Updated to also build with SDL2, and GLEW.

Hey, don't take this a strict no. But I wonder if it would be possible to use gald http://glad.dav1d.de/ instead? Its a generate your own bindings project, it makes it so we can limit the amount of functions that we need to import/parse and so on.
Again you can go ahead and commit as is and switch to glad further down the line or not at all.

Since this is fully functional, I will pull this to master.
I am all for exploring Gald as alternative, but rather have that as a additional pull request.


Added accessibility information

Docs Build status updates of commit caf0405:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingMaps/sdk-native/map-control-api/mapelement-class.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Dashboard heatmap always loading on mysql 8

Gitea version (or commit ref): d4e62787644bf08e5044b7aeb36c0080cd892fef
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:

https://gist.github.com/gaydin/ee00f012fbefe913daa53a98c0c55f1c
Description
Maybe need changed
https://github.com/go-gitea/gitea/blob/master/models/user_heatmap.go#L26
UNIX_TIMESTAMP(DATE_FORMAT(FROM_UNIXTIME(created_unix), '%Y%m%d'))
to
UNIX_TIMESTAMP(DATE(FROM_UNIXTIME(created_unix)))

Does this also fail in mysql 5/ mariadb 10?

I tested on MySQL 5.6.37 - work fine.
Trouble with mysql 8.0.13 only.
After changing DATE_FORMAT to DATE works fire on MySQL 5.6 and 8

@gaydin do you know how to make a PR ?
If not maybe we could add a label good first issue to attract new contributor ?


Merge master to release (v236)

(Git/karl-police) Added :customshirt, :custompants, :customface for non-clothing asset IDs (#710)
(Git/ccuser44) Anti-exploit improvements (#718)
(Git/NNickey) Added new toggles for anti-exploit (#729)
(Git/P3tray) Audio player improvements (#734)
(Git/pbstFusion) Minor icon change for audio player (#735)
(Git/P3tray) Fix some audio permission errors (#736)
(Git/L8X) Various minor code optimizations (#739/#740/#741/#742)
(Git/ccuser44) Minor server loader improvement (#743)
(Git/ccuser44) Removed obsolete FilteringEnabled code (#746/#755)
(Git/fxeP1) Fix settings.PlayerCommands, add experimental "NoEnv" (#750)
(Git/P3tray) Removed private audios (#751)
(Git/P3tray) Added settings.Messages (#757)
(Git/ccuser44) Anti-idle improvements (#756)
(Git/P3tray) Fix NotificationHolder canvas size issue (#760)
(Git/ccuser4) Fix bug that caused users to be kicked randomly (#766)
(Git/xvarmkorv2) Fix Dex issue (#771)
(Git/joritochip) Fix group cache memory leak
(Git/joritochip) Fix in-studio DataStore checks
(Git/joritochip) Trello integration improvements
(Git/joritochip) Restrict allowed :makecard lists
(Git/coasterteam) Update HandleExplore security checks

when

I think the time hath come.


Create wanfeng.txt

good evening
please add my school to the list
天津商业大学宝德学院
Tianjin University of Commerce Boustead College
Thank you so much

@alexlee0116 Thank you for your request. Regrettably, this request has signs of fraud. I have to close it without merging. If you are a student of this school, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


Feature/use gnark-crypto for ecc precompiles

PR description
Use gnark-crypto from besu-native for ECC precompiles

eip-2537
eip-196
eip-197

This will get besu onto a supported and more performant ECC library, and should allow us to remove tech debt in besu-native.
This PR also addresses some templating problems that exist with some of the execution spec tests, where tests are created in directories that do not match their namespace (and thus were not being run)
Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

[ ] Checked out our contribution guidelines?
[ ] Considered documentation and added the doc-change-required label to this PR if updates are required.
[ ] Considered the changelog and included an update if required.
[ ] For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

[ ] unit tests: ./gradlew build
[ ] acceptance tests: ./gradlew acceptanceTest
[ ] integration tests: ./gradlew integrationTest
[ ] reference tests: ./gradlew ethereum:referenceTests:referenceTests

LGTM except there are 10 tests failing
GeneralStateReferenceTest_507 > execution(String, GeneralStateTestCaseEipSpec, boolean) > Name: idPrecomps-Berlin[5] FAILED
java.lang.RuntimeException at GeneralStateReferenceTest_507.java:39


Render asterisks for required inputs' labels

Partially addresses #1177.
Currently only renders the asterisks next to inputs that are classified as isRequired in the constraints prop. This does not include the function or proportion inputs. The asterisks will be added to the function and proportion inputs as part of the work outlined in issue #1038.

Great points. I agree that we have no need for "(optional)" now that we're indicating what is required, thereby implying all other inputs are optional. I'll wait to hear what Danica thinks both about excising "optional" and about providing the user information about the asterisk.
Thanks for the feedback.

I just pushed the following changes:

Removed "(optional)" from Stratification variables (optional) label
Replaced the Y-axis aggregation's tooltip with the HelpIcon from web-components; this serves two purposes: fixes the slow render of the tooltip (was using the default 1 second hover before rendering) and moves toward unifying help icons to look/feel the same throughout the site
Also replaced the BirdsEyeView's tooltip with the HelpIcon
Added a tooltip to the axis labels that reads Required input

@jernestmyers please see comments in https://github.com/VEuPathDB/EdaNewIssues/issues/407

Addresses #1322


adds ability for admin to change filestore provider for managed jobs

https://github.com/Shippable/admiral/issues/2830
https://github.com/Shippable/admiral/issues/2831
https://github.com/Shippable/admiral/issues/2832

Going ahead and merging it. @rageshkrishna and @ric03uec take a look whenever free.


docs(readme): fix example usage for action function

Fix #41
successRedirect is not triggered in actions, turns out we need to throw the response.

With v4 of Remix Auth the successRedirect option was removed


DSC module for S2D

Hey, I cant any module for creating S2D pool and clusted shared volumes, is it possible for somebody to create this please?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 706b2e1a-e90e-d70e-431f-5476b0ca52c1
Version Independent ID: 70721d4c-642c-61f8-6c61-84b1dd1ae96c
Content: Deploy a two-node Storage Spaces Direct SOFS for UPD storage in Azure
Content Source: WindowsServerDocs/remote/remote-desktop-services/rds-storage-spaces-direct-deployment.md
Product: windows-server-threshold
GitHub Login: @Haley-Rowland
Microsoft Alias: harowl

Let me see what I can find about this. I'll update after talking to a few teams here. Thanks!

Thanks Liza


Support for a THREE.ParametricGeometry

Hello Erich!!
I noticed you have equivalent functions to generate spheres and cubes, but what about an implementation of a custom parametric function that is rendered as a 3D geometry?
https://laustep.github.io/stlahblog/frames/threejs_RosesBouquet.html
^I've been working on a really involved project using parametric 3D flowers and I was wondering how you'd go about rendering those in your pathtracer without triangles? or if that's even possible 👀?
Please let me know!! I'm so excited to see the progress you've made so far and your renderer is amazing!!
thank you!!

Hello @yure-r !
Thank you for the kind words.  The Roses bouquet demo is really cool! The petals have a beautiful, organic shape. Speaking of shapes like these, I'm afraid I don't have much experience in ray tracing parametric 3D geometry. You asked if these shapes were possible with my renderer - sadly, not as of yet.
If you'll allow me, I can explain further why I haven't yet tackled this type of geometry for my ray/path tracer. Forgive me if you already know what I'm about to say, but basically ray casting any shapes other than planes, triangles, boxes, and the family of quadrics (spheres,  cylinders, cones, paraboloids,  etc.) is not only expensive, it can also be numerically unstable and unpredictable with visual artifacts (such as holes and surface tearing). If you look at my PathTracingCommon.js file, which contains the various ray vs. *(insert your favorite shape here) that I've collected/or implemented over the years, you'll likely notice that these routines stay within the confines of simpler shapes with well-known analytical solutions. For instance, all of the quadrics don't go above degree 2, and therefore have a nice analytical quadratic equation to solve for t at the end, which computers can easily do, and even us humans could do with pencil and paper if we had to, like back in high school, lol.
But then we have something like the famous Torus shape which is used heavily in certain areas of computer graphics. The problem is that this seemingly simple donut shape is quartic, or of degree 4. If you look at my source code to intersect a ray with a torus, you'll see that it is over a hundred lines long of complex shader code with multiple contributing functions (as opposed to 6 lines of code for a sphere,  ha). Even with all that, I don't fully trust it, lol - it is a black box to me that I lifted off of a math whiz over on ShaderToy (who I give credit to in my copied code). If it stopped working one day, I wouldn't know how to fix it. Even though this bothers me, because I like knowing how every line in my codebase works and what it's purpose is, I've had to come to terms with the fact that I will probably never understand how to solve a quartic equation of degree 4. In fact, it bothers me so much that for weeks I have been working on my own "poor man's" torus intersection routine that doesn't go above degree 2! I figured out a cool trick to combine a section of an elongated Ellipsoid that is chopped off at its top and bottom, and on the inside, I intersect a friendly quadric (degree 2) Hyperboloid (fat hourglass), that is chopped off in a similar manner at top and bottom, in order to exactly meet the outside Ellipsoid shell. There is a problem with the seams where the 2 cheap quadrics meet, but I'm working on smoothing out the sharp transition. Personally,  I'd much rather use my own hacked version of a Torus, even with its slight artifacts, over the huge black box that solves the traditional quartic torus analytically and mysteriously. In other words,  at least I know how it works under the hood, so I feel like I'm in control more of the algorithm and the situation.
Which brings us to your lovely rose petal shapes. If I had to guess, I would say that those shapes require at least a degree 3 polynomial, or cubic equation in t. That's probably too conservative of an estimate- it might require higher degrees than that. Now assuming you didn't have to go above degree 3 for the curved surfaces, there are cubic solvers out there.  For instance, in the monumental  quartic solver, there is a whole section for 'polishing' the roots - otherwise we get numerous artifacts. I assume the same would need to be done with anything higher than degree 2 simple quadric shapes (which have a nice, closed form, stable solution).
However, all that being said, if you really want to render these shapes faithfully and accurately with some kind of Ray or path tracing, there are a couple of ways you could do it. The 1st is, as you probably guessed, bringing the shapes into a program like Blender, and triangulating everything. I know you wanted to be more pure about it, but with a decent stock triangle BVH accelerator, you could probably ray trace all the flowers in your demo in real time, even on mobile. The 2nd way is still a little of a black art: namely turning every rose petal into an SDF (Signed Distance Field) and 'warping' the 3D space around the petals. Then, rather than doing a possibly unstable, expensive,  analytical single ray cast, you would incrementally ray-'march' several steps into the SDF of each petal. This alternative has its positives and negatives - on the plus side, you can ray march almost any imaginable shape, even with no known closed form analytical solutions, cheaply (as the legendary Inigo Quilez (iq) has proven) on ShaderToy. The negative is that ray marching takes much more time, especially around the edges of the petals where the marching ray origins get really close, but just miss and continue on to the background of the scene. Again, you kind find numerous SDF flower examples on ShaderToy- some of which are very convincing.
So that was my very long way of saying - no unfortunately, the flower petals cannot be rendered with my path tracer, but all is not lost if you look to other possible solutions.
Hope this helps, and again, apologies if you already knew some of these renderering/math-related issues.
Cheers, 🙂
-Erich


Refactor ASN1_TIME_print functions to reduce duplicated code

This follow[s] what discussed at https://github.com/openssl/openssl/pull/4001#discussion_r129092251

Red cross from travis is relevant.

Resolved CI failure by reuse a shadowed local variable

Don’t add an assert.

Don’t add an assert.

what is the consideration?

It's not a possibly-fatal error, it's possibly malformed input. There's no need to debug/assert since you have to do the right thing -- return an error -- anyway.

new commits add to address comments and a new PR #4041 is created to document the 'fractional-sec-lost' situation of ASN1_TIME_to_tm

I added a new commit to maximize the usage of asn1_time_to_tm function to get date/time infos from it and parse the fractional stuff alone in the caller. This is like a 'final stroke' at current stage : )

squashed and merged to master.  thanks!


the latest docker version 139 cannot send file

Run npm run doctor or wechaty run doctor(for docker user), paste output here
Starting Wechaty v0.8.139 with Node.js v7.10.1 ...

><EMAIL_ADDRESS>doctor /wechaty
> npm run check-node-version && ts-node bin/doctor

><EMAIL_ADDRESS>check-node-version /wechaty
> check-node-version --node ">= 6.9"

node: 7.10.1
npm: 4.6.1
yarn: 0.27.5

  #### Wechaty Doctor

  1. Wechaty version: 0.8.139
  2. Linux x64 version 3.16.0-4-amd64 memory 74/998 MB
  3. Docker: true
  4. Node version: v7.10.1
  5. Tcp IPC TEST: PASS
  6. Chromedriver: ChromeDriver 2.25 (5a911c1ac99b36efadff2041357740080cc27220)

Expected behavior
send file  according to the #710 #714
Actual behavior
cannot send file  according to the #710 #714  using docker
But can send file using the source code:  git[6c576c5] version
Full Output Logs
$ WECHATY_LOG=silly npm run ts-node mybot.ts

# or

$ WECHATY_LOG=silly node dist/mybot.js

Paste the full output logs here with WECHATY_LOG=silly set
# PASTE FULL LOG OUTPUT AT HERE:

11:44:23 SILL Message constructor() SN:3
11:44:23 VERB Room say(小桔机器人产品介绍.pdf, )
TALK Task Done
11:44:23 SILL PuppetWebBridge execute()
11:44:23 SILL PuppetWebBrowser Browser.execute(" const callback = arguments[arguments.length - 1] const isAsync = (typeof  ... ")
11:44:23 SILL StateSwitch Browser:target() is open
11:44:23 SILL StateSwitch Browser:current() is open
11:44:23 SILL Message constructor() SN:4
11:44:23 SILL Message ready()
11:44:23 SILL Contact ready()
11:44:23 SILL Room ready()
11:44:23 SILL Message ready()
11:44:23 SILL Contact ready()
11:44:23 SILL Room ready()
11:44:23 VERB PuppetWebBridge getBaseRequest()
11:44:23 VERB PuppetWebBridge proxyWechaty(getBaseRequest, )
11:44:23 SILL PuppetWebBridge execute()
11:44:23 SILL PuppetWebBrowser Browser.execute("return typeof WechatyBro === "undefined"")
11:44:23 SILL StateSwitch Browser:target() is open
11:44:23 SILL StateSwitch Browser:current() is open
11:44:23 SILL PuppetWebBridge execute()
11:44:23 SILL PuppetWebBrowser Browser.execute(" const callback = arguments[arguments.length - 1] const isAsync = (typeof  ... ")
11:44:23 SILL StateSwitch Browser:target() is open
11:44:23 SILL StateSwitch Browser:current() is open
11:44:23 VERB PuppetWebBridge getPassticket()
11:44:23 VERB PuppetWebBridge proxyWechaty(getPassticket, )
11:44:23 SILL PuppetWebBridge execute()
11:44:23 SILL PuppetWebBrowser Browser.execute("return typeof WechatyBro === "undefined"")
11:44:23 SILL StateSwitch Browser:target() is open
11:44:23 SILL StateSwitch Browser:current() is open
11:44:23 SILL PuppetWebBridge execute()
11:44:23 SILL PuppetWebBrowser Browser.execute(" const callback = arguments[arguments.length - 1] const isAsync = (typeof  ... ")
11:44:23 SILL StateSwitch Browser:target() is open
11:44:23 SILL StateSwitch Browser:current() is open
11:44:23 VERB PuppetWebBridge getUploadMediaUrl()
11:44:23 VERB PuppetWebBridge proxyWechaty(getUploadMediaUrl, )
11:44:23 SILL PuppetWebBridge execute()
11:44:23 SILL PuppetWebBrowser Browser.execute("return typeof WechatyBro === "undefined"")
11:44:23 SILL StateSwitch Browser:target() is open
11:44:23 SILL StateSwitch Browser:current() is open
11:44:23 SILL PuppetWebBridge execute()
11:44:23 SILL PuppetWebBrowser Browser.execute(" const callback = arguments[arguments.length - 1] const isAsync = (typeof  ... ")
11:44:23 SILL StateSwitch Browser:target() is open
11:44:23 SILL StateSwitch Browser:current() is open
11:44:23 VERB PuppetWebBrowserCookie read()
11:44:23 SILL PuppetWebBrowserCookie read() webwx_data_ticket,wxsid,wxpluginkey,pgv_si,MM_WX_SOUND_STATE,wxuin,webwxuvid,MM_WX_NOTIFY_STATE,mm_lang,last_wxuin,webwx_auth_ticket,wxloadtime,pgv_pvi,login_frequency
11:44:23 VERB PuppetWebBrowser hostname()
11:44:23 SILL PuppetWebBrowser Browser.execute("return document.domain")
11:44:23 SILL StateSwitch Browser:target() is open
11:44:23 SILL StateSwitch Browser:current() is open
11:44:23 SILL PuppetWebBrowser hostname() got qq.com
11:44:23 VERB PuppetWeb self()

Need More Information
Sorry, you did not follow the ISSUE Template, and there's not enough information about your problem.
In order to help us to find the problem out, you should provide all the detail information about the issue. Please make sure you are following the ISSUE Template, answer all the question, and the more important: provide the steps to reproduce the problem.
I'll close this issue. Please re-submit a new issue to provide the information that needed.


Add information to connect to Pay-as-you-go

Just shows instructions for EA

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d2d95443-afbf-fadd-6932-1edef039548f
Version Independent ID: b5a9d263-4b72-e566-a53f-5c5e0bebafae
Content: Connect to Microsoft Azure Consumption Insights with Power BI - Power BI
Content Source: powerbi-docs/service-connect-to-azure-consumption-insights.md
Service: powerbi
GitHub Login: @SarinaJoan
Microsoft Alias: sarinas

Thanks for your comment, @atxjd. We’ve forwarded your feedback to the writer, who should respond to this thread shortly. In the meantime, can you provide a little more detail on the issue you raised?


Unify scpv0 code

Update 2021-11-04 This PR is now ready for review, following my own testing.
The point of the PR is to get xrdp and sesrun to use libscp to communicate with sesman. Once this is done, it becomes a lot easier to replace SCP V0/V1 with an SCP V2 to support #1961
Most of it is relatively straightforward. The complication is within xrdp, and centres around two issues:-
1 The interface between xrdp_mm.c and xrdp_wm.c
2  Replacing the synchronous access_control() function in xrdp_mm.c with asynchronous calls to libscp.
For the first of these, I've added a function xrdp_wm_mod_connect_done() to xrdp_wm.c. The idea is that xrdp_mm.c uses this to notify the window manager of all connection results. As well as simplifying the interface, this should result in uniform behaviour when a connection attempt fails. At the moment, strange things happen when (for example) a neutrinordp proxy connection does not authenticate properly with pamusername. This is fixed by this PR.
The second of these is complicated by not moving to UDS yet. I've approached it by using a second connection to sesman to fire off the PAM authentication request. This makes the eventual move to UDS a lot easier, as the second connection can simply be removed.
There's a state machine xrdp_mm_connect_sm() in xrdp_mm.c to manage the connection request. I'm hoping this makes the steps which go into a connection easier to follow.
I haven't spent a lot of time unifying SCP V0 and SCP V1 further. At the moment I can't see the point, but I'm open to being convinced otherwise if necessary.

No functional changes - simply rebased and checked against new functionality.
@metalefty - I'd like to get this in to v0.9.18 if possible, so I can start refactoring SCP.


fix: Fixed type annotations based on required python versions

Description of changes

Improvements & Bug fixes

In the following line we are using | instead of Union.
https://github.com/chroma-core/chroma/blob/47447b6f9846fb63cc17d3f458df405387f46127/chromadb/proto/convert.py#L45

Here we are using type[S] instead of Type[S]
https://github.com/chroma-core/chroma/blob/47447b6f9846fb63cc17d3f458df405387f46127/chromadb/segment/impl/manager/distributed.py#L81

Here we are annotation using list instead of List
https://github.com/chroma-core/chroma/blob/47447b6f9846fb63cc17d3f458df405387f46127/chromadb/segment/impl/metadata/sqlite.py#L489

I see that project targets Python versions <= 3.10 and >=3.8.
So, if someone is using Python 3.8 or 3.9 using these annotations will cause runtime errors.
Closes #1581
Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js

Documentation Changes
No documentation changes are needed.

Hey @Sai-Suraj-27, thanks for the PR. The distributed stuff is still in active development, so my two cents on trying to fix anything in a fluid codebase is that it isn't worth the effort, unless it breaks UX/DX.
Maybe it is important to note that the distributed version of Chroma is intended to run mostly in cloud-native environments like k8s where the Python version is not such a big issue as pre-built images will be shipped.

Hey @Sai-Suraj-27, thanks for the PR. The distributed stuff is still in active development, so my two cents on trying to fix anything in a fluid codebase is that it isn't worth the effort, unless it breaks UX/DX.
Maybe it is important to note that the distributed version of Chroma is intended to run mostly in cloud-native environments like k8s where the Python version is not such a big issue as pre-built images will be shipped.

Ok, I understand. But it is still good to follow the same type of annotations everywhere in the codebase.
So, I guess it's better to change these 3 type annotations according to the standard used everywhere else in this codebase.


Added powify auto completion.

Is powify better than powder?
Thanks for the completion attempt, but this is broken and incomplete. Please write a proper completion and submit it to zsh-completions.

I don't know if powify is better than powder, I'm just used to it. Even tried powder, but switched back to powify because I missed something (too long ago to remember it exactly).
Btw I'm new to zsh so can you help me with the completion script? What's missing and/or broken? It works perfectly on my local machine…

It's slow. It completes commands multiple times. It doesn't complete arguments to commands.
Writing completions is not easy, but if you wish to study, there are many examples at zsh-completions.

@haihappen After reviewing the link that @sorin-ionescu posted, do you want to re-submit this?


"Cannot get ratio when minimum and maximum value are equal"

Godot version:

3.2.3 stable
OS/device including version:

Windows
Issue description:

When I set a slider min and max val to 0, it throws the following error:
Cannot get ratio when minimum and maximum value are equal

Q: Why do I need this at all?
A: I'm creating an Undo slider like in ZBrush.
When a project starts, there's nothing to undo, so the undo slider max val is 0 (and min val is always 0)
Steps to reproduce:
set a slider (HSlider or VSlider) min and max val to an equal value, say to 0, in Ispector or with a script.
Minimal reproduction project:

At some point, this behaviour would yield dividing by zero. First of all, if the min and max are zero and the value is also zero, where does the thumb of the slider reside?

Just like @nathanfranke said, this doesn't look like a bug; the slider is not meant to be used with non proper max and min values, so it's kind of creating a problem where there isn't one.

@Ev1lbl0w these are proper values.
At least many popular UI frameworks work fine with setting equal min max values:
Vue:
https://vuetifyjs.com/en/components/sliders/
Andular:
https://material.angular.io/components/slider/examples
Kivy:
Slider(min=0, max=0, value=0)
etc
I see a work-round for setting max value to something more than min val + setting editable to false, although this is inelegant and requires more code
I think the user shouldn't have any problems with this, so this bug should either be fixed, or this feature should be documented.

@me2beats That's a fair argument, but before changes will be made we must agree on exact behaviour, including but not necessarily limited to my last two questions:

Where should the thumb of the slider reside?
What should the percentage show?
What should get_as_ratio return? 0.0? NaN?

According to the above links, when min = max, the slider gets all the way up to 100%, so the measure value should be equal to max.

Btw, this error does not seem to interfere with starting the game. But not sure that ignoring it won't cause the game to crash someday.

now (with min 0 and max 0) the thumb of the slider resides left, like in kivy.
Vue and Angular reside right.
Not sure which one is more intuitive.
ZBrush in its Undo slider shows the thumb left, when there's no undo history
percentage is something that the user would implement on his own? Didn't find such an option in godot.
I would let the user decide it for himself.
with min 0 and max 0, ratio returns 0. I think that's ok in this case.

percentage is something that the user would implement on his own? Didn't find such an option in godot.

Understandable, I was actually referring to percent_visible in ProgressBar which extends Range.

This error was added in #33583.

Btw, this error does not seem to interfere with starting the game.

This is because most error macros are not harmful, those are just return statements with error printing. 🙂
In my opinion, the class implementation should just handle those cases gracefully, and return either 0 or 1. Returning 1 may be less error-prone because it's unlikely to lead to division by zero.

If this is going to take a while to get addressed, can we at least get the error log in the console to link to the line of code that is generating the error?
I've got this thing popping up and failing silently all over my code, and I have no idea where it's coming from.

If this is going to take a while to get addressed, can we at least get the error log in the console to link to the line of code that is generating the error?
I've got this thing popping up and failing silently all over my code, and I have no idea where it's coming from.

I've got this thing popping up and failing silently all over my code, and I have no idea where it's coming from.

You can use a divide and conquer approach for now. Try removing nodes inheriting from Range from your scene tree until the error no longer pops up.

I've got this thing popping up and failing silently all over my code, and I have no idea where it's coming from.

You can use a divide and conquer approach for now. Try removing nodes inheriting from Range from your scene tree until the error no longer pops up.


Rename FATAL_FAILURE SHUTDOWN

This was talked about a few weeks ago during the gRPC Python GA API code review.

lgtm


docs/installation/rhel.md documentation is incorrect in steps 2 & 3

An extra "0". is in the file name.
It ends up downloading a bogus file which can't be installed with yum.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

thanks! https://github.com/docker/docker/issues/14054 was just merged so I think this can be close (docs may need some time to be published)


5 create dockerfile and docker compose to simplify deployment

Closes #5
Merging #9 and #10 will make this PR easier to review.

Current dependencies on/for this PR:

main

PR #9

PR #10

PR #12   👈

This comment was auto-generated by Graphite.

Please, merge main branch into this one and resolve all conflicts


Add

Let's create a button that will be used for buying the products. For example, it will look like the 'BUY NOW' buttons that we find in many e-commerce websites. Let's not put too much effort in styling as it has to be changed in the later stage once we are given the specific designs.

Would like to work on this issue

Blocked by #10

I would like to work on this issue

Sure. Let us know if you need any help :)

Can I take this up or is someone working on this?

I am working on this


0.1.5 to 0.1.6 is not a minor release

You need to bump the version number way higher, make 0.1.6 = 1.0.0 or something as this doesn't seem to be a minor release at all. Everyone who has this in a bower.json or similar is going to get there sites broken.
Thanks for the plugin.

Thanks for the info, i changed it...

http://semver.org/


Nightly builds not available

Describe the bug
The latest 5 nightly builds ran with failed. No new nightly versions are available.
Is this something easy to fix?
Can a manual nightly build be ran to produce the latest version?
Steps to reproduce
(https://github.com/evcc-io/evcc/actions/workflows/nightly.yml)
Configuration details
not applicable

Log details
not applicable

What type of operating system are you running?
Linux
Version
not applicable

Reverted 0df815729b5471bc7c448857d60137684b926611 and 536dbc936c7ced16f8bd00409a8cc00e5e807e57 which was a fix.


Debug console cannot line feed

Issue Type: Feature Request
When I debug a python program, I wish arrays are in alignment.
But the debug console dosen't line feed though there is a '\n' in the end of the array.
Generally, the output of the debug console should be on every 5 elements in a row, and now, they are crowded together.
see:

Extension version: 2019.4.12954
VS Code version: Code 1.34.0 (a622c65b2c713c890fcf4fbf07cf34049d5fe758, 2019-05-15T21:59:37.030Z)
OS version: Windows_NT x64 10.0.17134

Issue moved to microsoft/ptvsd #1471 via ZenHub


7pm-a-MessagesPerChannel: Searching messages by user will now also display all the channels they've participated in and how many messages there are per channel

I know you just made this PR, but the name is kinda long... maybe shorten it?
I'll give my full review tomorrow


Bar chart - Dataset Properties  vs Dataset Configuration

When browsing docs for bar chart, I have come across two distinct sub-sections:

Dataset Properties
Dataset Configuration

Both belong to datasets (as object properties) but why were they moved to separate sub-sections?

Looks like the first one can be specefied for each dataset and the other one are options for all datasets of that chart.

Looks like the first one can be specefied for each dataset and the other one are options for all datasets of that chart.

That makes sense but in the given example these properties are set for a specific data set:
data: {
    datasets: [{
        barPercentage: 0.5,
        barThickness: 6,
        maxBarThickness: 8,
        minBarLength: 2,
        data: [10, 20, 30, 40, 50, 60, 70]
    }]
};

That makes sense but in the given example these properties are set for a specific data set:
data: {
    datasets: [{
        barPercentage: 0.5,
        barThickness: 6,
        maxBarThickness: 8,
        minBarLength: 2,
        data: [10, 20, 30, 40, 50, 60, 70]
    }]
};

how to decrease space between bar when barThickness given value to 12?

how to decrease space between bar when barThickness given value to 12?

Circling back to this, I think both those sections can be merged together. I think the likely route is to remove the dataset configuration setting in favour of dataset properties.


Fine-tuning (BERT & RoBERTa) base outperforms large

❓ Questions & Help
On all datasets I have used so far, base always outperforms large after the fine-tune. This is true for both BERT and RoBERTa.
Why is that? Am I doing something wrong? Does large require far more epochs to train or a different learning rate?

Maybe you need more GPUs and a bigger batch size

I have 8 GPUs 2080 rtx, each with 10gb of data. But yeah I use a batch size of 4. However, I need the sequence length of 512 so it is impossible to increase the batch size.


wine: cannot find '/root/.wine/drive_c/Python27/python.exe

Error message:
wine: cannot find '/root/.wine/drive_c/Python27/python.exe
Does not install pywin32-220
http://imgur.com/jCcuDMm
Python 2.7.12

me also have  same issue

I solved it the same day xD!
Is pywin32-220 for x64bits xD!

@zerolshen What you've do to solve?

Got the same issue here as well :/ tried to clone again but same results, any solutions?

All x64bits, Force Install Python with Wine

Install "git". To use the "git" command

Sorry, I'm still kinda new to this, could you explain how or give a link to a video where it shows me how to do it?

Don't cancel the system upgrade. Run ./install.sh

I tried and it's still the same thing. Maybe you can see what I'm doing wrong here.
W: Target DEP-11-icons (non-free/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list:12 and /etc/apt/sources.list:17
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
Traceback (most recent call last):
File "C:\Python27\lib\runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
File "C:\Python27\lib\runpy.py", line 111, in get_module_details
import(mod_name)  # Do not catch exceptions initializing package
File "C:\Python27\lib\ensurepip_init.py", line 9, in
import tempfile
File "C:\Python27\lib\tempfile.py", line 35, in
from random import Random as _Random
File "C:\Python27\lib\random.py", line 885, in
_inst = Random()
File "C:\Python27\lib\random.py", line 97, in init
self.seed(x)
File "C:\Python27\lib\random.py", line 113, in seed
a = long(_hexlify(_urandom(2500)), 16)
WindowsError: [Error -2146893801] Windows Error 0x80090017
err:msi:ITERATE_Actions Execution halted, action L"UpdatePip" returned 1627
err:msi:ITERATE_Actions Execution halted, action L"ExecuteAction" returned 1627

i have the same problem :(
File "C:\Python27\lib\runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
File "C:\Python27\lib\runpy.py", line 111, in get_module_details
import(mod_name) # Do not catch exceptions initializing package
File "C:\Python27\lib\ensurepip_init.py", line 9, in
import tempfile
File "C:\Python27\lib\tempfile.py", line 35, in
from random import Random as _Random
File "C:\Python27\lib\random.py", line 885, in
_inst = Random()
File "C:\Python27\lib\random.py", line 97, in init
self.seed(x)
File "C:\Python27\lib\random.py", line 113, in seed
a = long(_hexlify(_urandom(2500)), 16)
WindowsError: [Error -2146893801] Windows Error 0x80090017
err:msi:ITERATE_Actions Execution halted, action L"UpdatePip" returned 1627
err:msi:ITERATE_Actions Execution halted, action L"ExecuteAction" returned 1627
Someone can help us? :c

wine: cannot find '/root/.wine/drive_c/Python27/python.exe'
Same problem, looking for a fix. I've tried a lot of apt-gets, updates and upgrades, etc.


 Please close it.
Wrote a small script to automate the reporting, Just like the spammer did.
Script here: https://gist.github.com/VISWESWARAN1998/cf74dd0890534ad3e72f326e46460cd3
Regards,
Visweswaran N


Smoothing

Is it possible to set smoothing true?

The smoothing of Sprite rendering is true by default.


So, I didn't mean for these to go into one pull request. Saw just now that the request updates itself with the latest diff. Can spit if it bothers you.

Added, hopefully, useful properties.
Fixed the segment to use the true name.

Thanks for the pull request!
Just a few things...
Can you show a use-case for has_xrefs_xxx?
calls is an ambiguous name. Is it calls_from or calls_to?
When adding properties to Line objects, it is probably a good idea to add the matching properties to Function objects as well.
The Segment.name fix is a good one, though :+1:

Good feedback!
use case  for has_xrefs_xxx
I've used it twice in my code, both times to check if the data I'm looking at is a pointer.
It didn't feel entirely right to me too, but I need a way to spot a  pointer.
So, I'm ready to drop the pull request for this one.
calls
So, you are saying, add both calls_from and calls_to,right?
Function/Line properties
Do you think we need calls_from/to in the Line as well?


Not connecting to ioniq 5

Pi0 seems to boot and offers a wifi address but then nothing happens, I would ssh into the pi but can't get in using juicessh to<EMAIL_ADDRESS>is this the correct way to get in?

The address to SSH into the Pi is <IP_ADDRESS>.

Thanks that let's me in so I can now look at tge logs
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: admiralspeedy @.>
Sent: Friday, March 8, 2024 2:40:26 PM
To: nisargjhaveri/WirelessAndroidAutoDongle @.>
Cc: blondini23 @.>; Author @.>
Subject: Re: [nisargjhaveri/WirelessAndroidAutoDongle] Not connecting to ioniq 5 (Issue #77)
The address to SSH into the Pi is <IP_ADDRESS>.
—
Reply to this email directly, view it on GitHubhttps://github.com/nisargjhaveri/WirelessAndroidAutoDongle/issues/77#issuecomment-1985811308, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A33I7I7UKJMPK5XKGFUWJ33YXHEVVAVCNFSM6AAAAABEMUCJ2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBVHAYTCMZQHA.
You are receiving this because you authored the thread.Message ID: @.***>

Am I allowed to  add tge contents of /var/log/messages?

Am I allowed to add tge contents of /var/log/messages?

Yes, please share the logs here if you're also facing similar issues.

/var/log/messages
Jan  1 00:00:03 buildroot syslog.info syslogd started: BusyBox v1.36.1
Jan  1 00:00:03 buildroot kern.notice kernel: klogd started: BusyBox v1.36.1 (2024-03-01 07:28:45 UTC)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Booting Linux on physical CPU 0x0
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.000000] Linux version 6.1.61 (runner@fv-az1269-741) (arm-buildroot-linux-gnueabihf-gcc.br_real (Buildroot -g7a59c3a4) 12.3.0, GNU ld (GNU Binutils) 2.40) #1 Fri Mar  1 08:00:43 UTC 2024
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] OF: fdt: Machine model: Raspberry Pi Zero W Rev 1.1
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.000000] random: crng init done
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Memory policy: Data cache writeback
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Reserved memory: created CMA memory pool at 0x15800000, size 64 MiB
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Zone ranges:
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000]   Normal   [mem 0x0000000000000000-0x0000000019bfffff]
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Movable zone start for each node
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Early memory node ranges
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x0000000019bfffff]
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000019bfffff]
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 104545
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5F:26:E9 vc_mem.mem_base=0x1ec0000
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] Memory: 340196K/421888K available (7906K kernel code, 702K rwdata, 2184K rodata, 256K init, 498K bss, 16156K reserved, 65536K cma-reserved)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000006] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every<PHONE_NUMBER>500ns
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000055] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>275 ns
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000158] bcm2835: system timer (irq = 27)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.000946] Console: colour dummy device 80x30
Jan  1 00:00:03 buildroot kern.info kernel: [    0.001443] printk: console [tty1] enabled
Jan  1 00:00:03 buildroot kern.info kernel: [    0.001523] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.060290] CPU: Testing write buffer coherency: ok
Jan  1 00:00:03 buildroot kern.info kernel: [    0.060396] pid_max: default: 32768 minimum: 301
Jan  1 00:00:03 buildroot kern.info kernel: [    0.060584] LSM: Security Framework initializing
Jan  1 00:00:03 buildroot kern.info kernel: [    0.060797] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.060867] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.062264] cgroup: Disabling memory control group subsystem
Jan  1 00:00:03 buildroot kern.info kernel: [    0.064143] cblist_init_generic: Setting adjustable number of callback queues.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.064225] cblist_init_generic: Setting shift to 0 and lim to 1.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.064550] Setting up static identity map for 0x8220 - 0x8258
Jan  1 00:00:03 buildroot kern.info kernel: [    0.065801] devtmpfs: initialized
Jan  1 00:00:03 buildroot kern.info kernel: [    0.076658] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
Jan  1 00:00:03 buildroot kern.info kernel: [    0.077054] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
Jan  1 00:00:03 buildroot kern.info kernel: [    0.077167] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.087607] pinctrl core: initialized pinctrl subsystem
Jan  1 00:00:03 buildroot kern.info kernel: [    0.089312] NET: Registered PF_NETLINK/PF_ROUTE protocol family
Jan  1 00:00:03 buildroot kern.info kernel: [    0.091810] DMA: preallocated 1024 KiB pool for atomic coherent allocations
Jan  1 00:00:03 buildroot kern.info kernel: [    0.097579] audit: initializing netlink subsys (disabled)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.099018] thermal_sys: Registered thermal governor 'step_wise'
Jan  1 00:00:03 buildroot kern.info kernel: [    0.099331] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.099424] hw-breakpoint: maximum watchpoint size is 4 bytes.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.099616] Serial: AMBA PL011 UART driver
Jan  1 00:00:03 buildroot kern.info kernel: [    0.106962] bcm2835-mbox 2000b880.mailbox: mailbox enabled
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.110670] audit: type=2000 audit(0.090:1): state=initialized audit_enabled=0 res=1
Jan  1 00:00:03 buildroot kern.info kernel: [    0.130725] raspberrypi-firmware soc:firmware: Attached to firmware from 2023-10-17T15:42:39, variant startJan  1 00:00:03 buildroot kern.info kernel: [    0.140751] raspberrypi-firmware soc:firmware: Firmware hash is 30f0c5e4d076da3ab4f341d88e7d505760b93ad7
Jan  1 00:00:03 buildroot kern.info kernel: [    0.187436] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.191053] bcm2835-dma 20007000.dma: DMA legacy API manager, dmachans=0x1
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.193538] SCSI subsystem initialized
Jan  1 00:00:03 buildroot kern.info kernel: [    0.193968] usbcore: registered new interface driver usbfs
Jan  1 00:00:03 buildroot kern.info kernel: [    0.194109] usbcore: registered new interface driver hub
Jan  1 00:00:03 buildroot kern.info kernel: [    0.194237] usbcore: registered new device driver usb
Jan  1 00:00:03 buildroot kern.warn kernel: [    0.194550] usb_phy_generic phy: supply vcc not found, using dummy regulator
Jan  1 00:00:03 buildroot kern.info kernel: [    0.195268] pps_core: LinuxPPS API ver. 1 registered
Jan  1 00:00:03 buildroot kern.info kernel: [    0.195325] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>Jan  1 00:00:03 buildroot kern.info kernel: [    0.195405] PTP clock support registered
Jan  1 00:00:03 buildroot kern.info kernel: [    0.197631] clocksource: Switched to clocksource timer
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.198292] VFS: Disk quotas dquot_6.6.0
Jan  1 00:00:03 buildroot kern.info kernel: [    0.198446] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.198697] FS-Cache: LoadedJan  1 00:00:03 buildroot kern.info kernel: [    0.199120] CacheFiles: LoadedJan  1 00:00:03 buildroot kern.info kernel: [    0.217518] NET: Registered PF_INET protocol family
Jan  1 00:00:03 buildroot kern.info kernel: [    0.217967] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.220476] tcp_listen_portaddr_hash hash table entries: 1024 (order: 0, 4096 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.220604] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.220689] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.220805] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.220945] TCP: Hash tables configured (established 4096 bind 4096)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.221123] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.221200] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.221597] NET: Registered PF_UNIX/PF_LOCAL protocol family
Jan  1 00:00:03 buildroot kern.info kernel: [    0.222606] RPC: Registered named UNIX socket transport module.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.222684] RPC: Registered udp transport module.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.222716] RPC: Registered tcp transport module.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.222743] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan  1 00:00:03 buildroot kern.warn kernel: [    0.223246] armv6-pmu arm-pmu: hw perfevents: no irqs for PMU, sampling events not supported
Jan  1 00:00:03 buildroot kern.info kernel: [    0.223357] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.224868] Initialise system trusted keyrings
Jan  1 00:00:03 buildroot kern.info kernel: [    0.225503] workingset: timestamp_bits=14 max_order=17 bucket_order=3
Jan  1 00:00:03 buildroot kern.info kernel: [    0.234950] zbud: loaded
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.238986] NFS: Registering the id_resolver key type
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.239113] Key type id_resolver registered
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.239152] Key type id_legacy registered
Jan  1 00:00:03 buildroot kern.info kernel: [    0.239346] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Jan  1 00:00:03 buildroot kern.info kernel: [    0.239404] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.241333] Key type asymmetric registered
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.241413] Asymmetric key parser 'x509' registered
Jan  1 00:00:03 buildroot kern.info kernel: [    0.241710] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.241771] io scheduler mq-deadline registered
Jan  1 00:00:03 buildroot kern.info kernel: [    0.241807] io scheduler kyber registered
Jan  1 00:00:03 buildroot kern.info kernel: [    0.246389] bcm2708_fb soc:fb: FB found 1 display(s)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.258399] Console: switching to colour frame buffer device 90x30
Jan  1 00:00:03 buildroot kern.info kernel: [    0.266477] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 720x480
Jan  1 00:00:03 buildroot kern.info kernel: [    0.276105] bcm2835-rng 20104000.rng: hwrng registered
Jan  1 00:00:03 buildroot kern.info kernel: [    0.280056] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.306129] brd: module loadedJan  1 00:00:03 buildroot kern.info kernel: [    0.317864] loop: module loaded
Jan  1 00:00:03 buildroot kern.info kernel: [    0.322038] Loading iSCSI transport class v2.0-870.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.327225] usbcore: registered new interface driver smsc95xx
Jan  1 00:00:03 buildroot kern.info kernel: [    0.330471] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.333752] dwc_otg: FIQ enabled
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.333773] dwc_otg: NAK holdoff enabled
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.333783] dwc_otg: FIQ split-transaction FSM enabled
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.333809] Module dwc_common_port init
Jan  1 00:00:03 buildroot kern.info kernel: [    0.334254] usbcore: registered new interface driver usb-storage
Jan  1 00:00:03 buildroot kern.info kernel: [    0.337995] mousedev: PS/2 mouse device common for all mice
Jan  1 00:00:03 buildroot kern.info kernel: [    0.343096] sdhci: Secure Digital Host Controller Interface driver
Jan  1 00:00:03 buildroot kern.info kernel: [    0.346242] sdhci: Copyright(c) Pierre Ossman
Jan  1 00:00:03 buildroot kern.info kernel: [    0.349711] sdhci-pltfm: SDHCI platform and OF driver helper
Jan  1 00:00:03 buildroot kern.info kernel: [    0.354109] ledtrig-cpu: registered to indicate activity on CPUs
Jan  1 00:00:03 buildroot kern.info kernel: [    0.357959] hid: raw HID events driver (C) Jiri Kosina
Jan  1 00:00:03 buildroot kern.info kernel: [    0.361240] usbcore: registered new interface driver usbhid
Jan  1 00:00:03 buildroot kern.info kernel: [    0.364285] usbhid: USB HID core driver
Jan  1 00:00:03 buildroot kern.info kernel: [    0.367456] bcm2835_vchiq 2000b840.mailbox: there is not valid maps for state default
Jan  1 00:00:03 buildroot kern.info kernel: [    0.376284] Initializing XFRM netlink socket
Jan  1 00:00:03 buildroot kern.info kernel: [    0.380118] NET: Registered PF_PACKET protocol family
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.384018] Key type dns_resolver registered
Jan  1 00:00:03 buildroot kern.info kernel: [    0.387972] registered taskstats version 1
Jan  1 00:00:03 buildroot kern.notice kernel: [    0.391136] Loading compiled-in X.509 certificates
Jan  1 00:00:03 buildroot kern.info kernel: [    0.402690] uart-pl011 20201000.serial: cts_event_workaround enabled
Jan  1 00:00:03 buildroot kern.info kernel: [    0.406043] 20201000.serial: ttyAMA1 at MMIO 0x20201000 (irq = 81, base_baud = 0) is a PL011 rev2
Jan  1 00:00:03 buildroot kern.info kernel: [    0.412754] serial serial0: tty port ttyAMA1 registered
Jan  1 00:00:03 buildroot kern.info kernel: [    0.418032] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Jan  1 00:00:03 buildroot kern.info kernel: [    0.421749] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Jan  1 00:00:03 buildroot kern.info kernel: [    0.427036] mmc-bcm2835 20300000.mmcnr: mmc_debug:0 mmc_debug2:0
Jan  1 00:00:03 buildroot kern.info kernel: [    0.430429] mmc-bcm2835 20300000.mmcnr: DMA channel allocated
Jan  1 00:00:03 buildroot kern.info kernel: [    0.460346] sdhost: log_buf @ 83506ee5 (95910000)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.512744] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.516903] of_cfs_init
Jan  1 00:00:03 buildroot kern.info kernel: [    0.521390] of_cfs_init: OK
Jan  1 00:00:03 buildroot kern.info kernel: [    0.527271] Waiting for root device /dev/mmcblk0p2...
Jan  1 00:00:03 buildroot kern.warn kernel: [    0.588995] mmc0: host does not support reading read-only switch, assuming write-enable
Jan  1 00:00:03 buildroot kern.info kernel: [    0.596332] mmc0: new high speed SDHC card at address aaaa
Jan  1 00:00:03 buildroot kern.info kernel: [    0.600990] mmcblk0: mmc0:aaaa SL32G 29.7 GiB
Jan  1 00:00:03 buildroot kern.info kernel: [    0.610057]  mmcblk0: p1 p2
Jan  1 00:00:03 buildroot kern.info kernel: [    0.614511] mmcblk0: mmc0:aaaa SL32G 29.7 GiB (quirks 0x00004000)
Jan  1 00:00:03 buildroot kern.info kernel: [    0.630729] mmc1: new high speed SDIO card at address 0001
Jan  1 00:00:03 buildroot kern.info kernel: [    0.655411] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
Jan  1 00:00:03 buildroot kern.info kernel: [    0.658861] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
Jan  1 00:00:03 buildroot kern.info kernel: [    0.761796] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
Jan  1 00:00:03 buildroot kern.info kernel: [    0.765262] EXT4-fs (mmcblk0p2): recovery complete
Jan  1 00:00:03 buildroot kern.info kernel: [    0.773699] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.779996] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.786238] devtmpfs: mounted
Jan  1 00:00:03 buildroot kern.info kernel: [    0.790260] Freeing unused kernel image (initmem) memory: 256K
Jan  1 00:00:03 buildroot kern.warn kernel: [    0.793358] Kernel memory protection not selected by kernel config.
Jan  1 00:00:03 buildroot kern.info kernel: [    0.796451] Run /sbin/init as init process
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.799520]   with arguments:Jan  1 00:00:03 buildroot kern.debug kernel: [    0.799538]     /sbin/init
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.799548]   with environment:
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.799555]     HOME=/
Jan  1 00:00:03 buildroot kern.debug kernel: [    0.799561]     TERM=linux
Jan  1 00:00:03 buildroot kern.info kernel: [    0.965903] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.
Jan  1 00:00:03 buildroot kern.notice kernel: [    1.435332] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Jan  1 00:00:03 buildroot kern.notice kernel: [    1.557078] cfg80211: Loaded X.509 cert<EMAIL_ADDRESS>577e021cb980e0e820821ba7b54b4961b8b4fadf'
Jan  1 00:00:03 buildroot kern.notice kernel: [    1.567739] cfg80211: Loaded X.509 cert<EMAIL_ADDRESS>3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
Jan  1 00:00:03 buildroot kern.notice kernel: [    1.578477] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Jan  1 00:00:03 buildroot kern.debug kernel: [    1.739084] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
Jan  1 00:00:03 buildroot kern.info kernel: [    1.745228] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Jan  1 00:00:03 buildroot kern.info kernel: [    1.753590] usbcore: registered new interface driver brcmfmac
Jan  1 00:00:03 buildroot kern.info kernel: [    2.009274] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Jul 19 2021 03:24:18 version 7.45.98 (TOB) (56df937 CY) FWID 01-8e14b897
Jan  1 00:00:03 buildroot kern.info kernel: [    2.120349] Bluetooth: Core ver 2.22
Jan  1 00:00:03 buildroot kern.info kernel: [    2.124210] NET: Registered PF_BLUETOOTH protocol family
Jan  1 00:00:03 buildroot kern.info kernel: [    2.127959] Bluetooth: HCI device and connection manager initialized
Jan  1 00:00:03 buildroot kern.info kernel: [    2.131727] Bluetooth: HCI socket layer initialized
Jan  1 00:00:03 buildroot kern.info kernel: [    2.135445] Bluetooth: L2CAP socket layer initialized
Jan  1 00:00:03 buildroot kern.info kernel: [    2.139169] Bluetooth: SCO socket layer initialized
Jan  1 00:00:03 buildroot kern.info kernel: [    2.174309] Bluetooth: HCI UART driver ver 2.3
Jan  1 00:00:03 buildroot kern.info kernel: [    2.177989] Bluetooth: HCI UART protocol H4 registered
Jan  1 00:00:03 buildroot kern.info kernel: [    2.181605] Bluetooth: HCI UART protocol Three-wire (H5) registered
Jan  1 00:00:03 buildroot kern.warn kernel: [    2.185562] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
Jan  1 00:00:03 buildroot kern.info kernel: [    2.189256] Bluetooth: HCI UART protocol Broadcom registered
Jan  1 00:00:03 buildroot kern.warn kernel: [    2.192989] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
Jan  1 00:00:03 buildroot kern.info kernel: [    2.316917] uart-pl011 20201000.serial: no DMA platform data
Jan  1 00:00:03 buildroot kern.info kernel: [    2.568706] Bluetooth: hci0: BCM: chip id 94
Jan  1 00:00:03 buildroot kern.info kernel: [    2.572721] Bluetooth: hci0: BCM: features 0x2e
Jan  1 00:00:03 buildroot kern.info kernel: [    2.577570] Bluetooth: hci0: BCM43430A1
Jan  1 00:00:03 buildroot kern.info kernel: [    2.580831] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000
Jan  1 00:00:03 buildroot kern.info kernel: [    2.588960] Bluetooth: hci0: BCM43430A1 'brcm/BCM43430A1.raspberrypi,model-zero-w.hcd' Patch
Jan  1 00:00:03 buildroot kern.warn kernel: [    3.073190] dwc2 20980000.usb: supply vusb_d not found, using dummy regulator
Jan  1 00:00:03 buildroot kern.warn kernel: [    3.076643] dwc2 20980000.usb: supply vusb_a not found, using dummy regulator
Jan  1 00:00:03 buildroot kern.info kernel: [    3.178665] Bluetooth: hci0: BCM: features 0x2e
Jan  1 00:00:03 buildroot kern.info kernel: [    3.181975] dwc2 20980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM
Jan  1 00:00:03 buildroot kern.info kernel: [    3.185950] Bluetooth: hci0: BCM43438A1 37.4MHz Raspberry Pi 3-0141
Jan  1 00:00:03 buildroot kern.info kernel: [    3.188934] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0508
Jan  1 00:00:03 buildroot daemon.notice haveged: haveged starting up
Jan  1 00:00:03 buildroot daemon.info rngd: Initializing available sources
Jan  1 00:00:03 buildroot daemon.info rngd: [hwrng ]: Initialized
Jan  1 00:00:03 buildroot daemon.info rngd: [jitter]: JITTER timeout set to 5 sec
Jan  1 00:00:04 buildroot daemon.info bluetoothd[130]: Bluetooth daemon 5.68
Jan  1 00:00:04 buildroot daemon.info bluetoothd[130]: Starting SDP server
Jan  1 00:00:04 buildroot daemon.warn bluetoothd[130]: src/plugin.c:plugin_init() System does not support csip plugin
Jan  1 00:00:04 buildroot daemon.warn bluetoothd[130]: src/plugin.c:plugin_init() System does not support bass plugin
Jan  1 00:00:04 buildroot daemon.warn bluetoothd[130]: profiles/network/bnep.c:bnep_init() kernel lacks bnep-protocol support
Jan  1 00:00:04 buildroot daemon.warn bluetoothd[130]: src/plugin.c:plugin_init() System does not support network plugin
Jan  1 00:00:04 buildroot daemon.info bluetoothd[130]: Bluetooth management interface 1.22 initialized
Jan  1 00:00:04 buildroot kern.info kernel: [    4.514234] Bluetooth: MGMT ver 1.22
Jan  1 00:00:04 buildroot kern.info kernel: [    4.634349] NET: Registered PF_ALG protocol family
Jan  1 00:00:06 buildroot daemon.info rngd: [jitter]: Initializing AES bufferJan  1 00:00:06 buildroot kern.info kernel: [    6.789208] NET: Registered PF_INET6 protocol family
Jan  1 00:00:06 buildroot kern.info kernel: [    6.809467] Segment Routing with IPv6
Jan  1 00:00:06 buildroot kern.info kernel: [    6.816042] In-situ OAM (IOAM) with IPv6
Jan  1 00:00:06 buildroot authpriv.info dropbear[173]: Running in background
Jan  1 00:00:06 buildroot daemon.info dnsmasq[177]: started, version 2.89 cachesize 150
Jan  1 00:00:07 buildroot daemon.info dnsmasq[177]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-nftset auth no-cryptohash no-DNSSEC loop-detect inotify dumpfile
Jan  1 00:00:07 buildroot daemon.info dnsmasq-dhcp[177]: DHCP, IP range <IP_ADDRESS> -- <IP_ADDRESS>, lease time 12h
Jan  1 00:00:07 buildroot daemon.info dnsmasq[177]: read /etc/hosts - 2 namesJan  1 00:00:07 buildroot kern.info kernel: [    7.909820] file system registered
Jan  1 00:00:08 buildroot kern.info kernel: [    8.061197] read descriptors
Jan  1 00:00:08 buildroot kern.info kernel: [    8.063913] read strings
Jan  1 00:00:09 buildroot user.info usb_gadget: Enabled default usb gadget
Jan  1 00:00:09 buildroot daemon.info : starting pid 216, tty '/dev/tty1': '/sbin/getty -L  tty1 0 vt100 '
Jan  1 00:00:09 buildroot user.info aawgd[215]: AA Wireless Dongle
Jan  1 00:00:09 buildroot user.info aawgd[215]: Starting uevent monitoring
Jan  1 00:00:09 buildroot user.info aawgd[215]: Uevent monitoring started
Jan  1 00:00:09 buildroot user.info aawgd[215]: Initializing USB Manager
Jan  1 00:00:09 buildroot user.info aawgd[215]: USB Manager: Disabled all USB gadgets
Jan  1 00:00:09 buildroot user.info aawgd[215]: USB Manager: Found UDC 20980000.usb
Jan  1 00:00:09 buildroot user.info aawgd[215]: Unique Name: :1.2
Jan  1 00:00:09 buildroot user.info aawgd[215]: Using bluetooth adapter at path: /org/bluez/hci0
Jan  1 00:00:09 buildroot kern.info kernel: [    9.788177] Bluetooth: RFCOMM TTY layer initialized
Jan  1 00:00:09 buildroot kern.info kernel: [    9.790439] Bluetooth: RFCOMM socket layer initialized
Jan  1 00:00:09 buildroot kern.info kernel: [    9.792599] Bluetooth: RFCOMM ver 1.11
Jan  1 00:00:09 buildroot user.info aawgd[215]: Bluetooth AA Wireless profile active
Jan  1 00:00:09 buildroot user.info aawgd[215]: HSP Handset profile active
Jan  1 00:00:09 buildroot user.info aawgd[215]: Starting tcp server
Jan  1 00:00:09 buildroot user.info aawgd[215]: Tcp server listening on 5288
Jan  1 00:00:09 buildroot user.info aawgd[215]: Bluetooth adapter was powered on
Jan  1 00:00:09 buildroot user.info aawgd[215]: Bluetooth adapter is now discoverable and pairable
Jan  1 00:00:09 buildroot user.info aawgd[215]: Did not find any connected bluetooth device
Jan  1 00:00:11 buildroot daemon.info rngd: [jitter]: Unable to obtain AES key, disabling JITTER source
Jan  1 00:00:11 buildroot daemon.err rngd: [jitter]: Initialization Failed
Jan  1 00:00:22 buildroot daemon.info hostapd: wlan0: STA de:8a:8f:a6:57:0c IEEE 802.11: associated
Jan  1 00:00:22 buildroot daemon.info hostapd: wlan0: STA de:8a:8f:a6:57:0c WPA: pairwise key handshake completed (RSN)
Jan  1 00:00:25 buildroot daemon.info dnsmasq-dhcp[177]: DHCPDISCOVER(wlan0) de:8a:8f:a6:57:0c
Jan  1 00:00:25 buildroot daemon.info dnsmasq-dhcp[177]: DHCPOFFER(wlan0) <IP_ADDRESS> de:8a:8f:a6:57:0c
Jan  1 00:00:25 buildroot daemon.info dnsmasq-dhcp[177]: DHCPDISCOVER(wlan0) de:8a:8f:a6:57:0c
Jan  1 00:00:25 buildroot daemon.info dnsmasq-dhcp[177]: DHCPOFFER(wlan0) <IP_ADDRESS> de:8a:8f:a6:57:0c
Jan  1 00:00:25 buildroot daemon.info dnsmasq-dhcp[177]: DHCPDISCOVER(wlan0) de:8a:8f:a6:57:0c
Jan  1 00:00:25 buildroot daemon.info dnsmasq-dhcp[177]: DHCPOFFER(wlan0) <IP_ADDRESS> de:8a:8f:a6:57:0c
Jan  1 00:00:25 buildroot daemon.info dnsmasq-dhcp[177]: DHCPREQUEST(wlan0) <IP_ADDRESS> de:8a:8f:a6:57:0c
Jan  1 00:00:25 buildroot daemon.info dnsmasq-dhcp[177]: DHCPACK(wlan0) <IP_ADDRESS> de:8a:8f:a6:57:0c Nick-s-S24
Jan  1 00:00:48 buildroot kern.info kernel: [   48.106865] read descriptors
Jan  1 00:00:48 buildroot kern.info kernel: [   48.109191] read strings
Jan  1 00:01:21 buildroot authpriv.info dropbear[222]: Child connection from <IP_ADDRESS>:58994
Jan  1 00:01:26 buildroot authpriv.info dropbear[222]: Exit before auth from <<IP_ADDRESS>:58994>: (user 'root', 0 fails): Exited normally
Jan  1 00:01:28 buildroot kern.info kernel: [   88.128143] read descriptors
Jan  1 00:01:28 buildroot kern.info kernel: [   88.130156] read strings
Jan  1 00:01:29 buildroot authpriv.info dropbear[223]: Child connection from <IP_ADDRESS>:49748
Jan  1 00:01:29 buildroot authpriv.notice dropbear[223]: Password auth succeeded for 'root' from <IP_ADDRESS>:49748

nick@pi5:~ $

I can't see any errors that might indicate why it doesn't work

I didn't realise it needed to connect with WiFi and Bluetooth but suspect thus will make it work

You don't really need to connect to Wifi manually, but bluetooth needs to be paired the first time.

Looks like this might be fixed now. Closing the issue for now, feel free to reopen if this is still an issue.


vue init webpack#1.0 vue-demo1not work

hi, I want to use Vue1.x and install vue-cli(2.4.0)
but vue init webpack#1.0 vue-demo1 is not work

npm i vue-cli@1 -g and vue init webpack#1.0 vue-demo1 is also not work
thanks! it maybe a simple issue, but it confuses me a lot.

I can't reproduce this issue,

if me enter a template of error, vue-cli will return 404

I have the same problem here

Hi, it seems to be a bug of zsh, try to use bash instead.


KAFKA-7853: refactor coordinator config

A test attempt to refactor current coordinator logic.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@stanislavkozlovski @hachikuji Do you think this makes sense to you?

retest this please

I've made another pass on the PR and it looks good to me. Would like to ping another pair of eyes to review before merging, cc @stanislavkozlovski @hachikuji @rajinisivaram.
Also, could you rebase (there's a minor conflict).

System tests passed for consumer and connect: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/2718/ and https://jenkins.confluent.io/job/system-test-kafka-branch-builder/2716/


Bump netty version to 4.1.108.Final to fix CVE-2024-29025 in 5.x and 6.x versions

Description:
$subject

Modules needed

[ ] gRPC
[ ] Websocket
[ ] TCP
[ ] UDP
[x] HTTP


operator ||= is not supported in version 14 of node

Node.js (v14.21.3) build error since the assignment operator ||= is not supported, fixing this line lets the build complete
Apr  7 02:14:54 ip-172-31-32-220 web: > node dist/main
Apr  7 02:14:57 ip-172-31-32-220 web: /var/app/current/node_modules/@apricote/nest-pg-boss/dist/pg-boss.module.js:41
Apr  7 02:14:57 ip-172-31-32-220 web: dynamicModule.exports ||= [];
Apr  7 02:14:57 ip-172-31-32-220 web: ^^^
Apr  7 02:14:57 ip-172-31-32-220 web: SyntaxError: Unexpected token '||='

Hey @mmendivilg,
Node 14 is End-Of-Life. This library targets ES2022, which is mostly supported in later versions of Node 16 and fully from Node 17.
I would recommend you to use a currently maintained version of Node: https://github.com/nodejs/Release/?tab=readme-ov-file#release-schedule


FR: Dialog that uses Remote Config to enforce minimum app version

It's pretty common for apps to enforce that users upgrade after a certain amount of time.  For example Snapchat does this when they change something about their internal API.
Remote Config is actually great for this.  You can set a minimum_app_version variable and then have the app check it against the installed version.  If installed < min we should show a dialog that says "You're using an out of date version of this app, please update to continue" with a button to Intent out to the Play Store.
Apps could throw this in their first Activity before a certain critical point and therefore be able to do things like backend DB migrations in a safer way.

Two years have passed since this issue was first created and we now have:

Play Store in-app updates - for apps distributed through the PlayStore.
Firebase App Distribution in-app alerts - for apps distributed through App Distribution.

I think we can still consider this as a valid issue because it would be useful for stores other than Play and FAD (e.g. Amazon Store, Samsung Store, etc) but I think the demand is lower now.


Port changes of [#16137] to branch-2.8

When we have a large cluster, we found that is very slowly to register
all workers to master. Because of default 25 workers register a time and
the lease lasts for 1 minute since the worker have finished the
register. And I found when not use stream register, it will release
lease. So I think it should be the same as before.
Greatly increase the worker registration speed when you have a large
scale cluster.
Please list the user-facing changes introduced by your change, including
no
pr-link: Alluxio/alluxio#16137
change-id: cid-20fd21e04cb74c5861cd692764a4b5f3db896178

alluxio-bot, merge this please


SesameSession does not apply any custom http headers set by additionalHeaders

SesameSession overrides getQueryMethod/getUpdateMethod but it does not apply the values from additionalHeaders field. The result is that the client app could not use that functionality. SparqlSession does do that.

Be aware that in RDF4J 2.2, SesameSession was refactored and renamed (to RDF4JProtocolSession). See #721 .
If you want this fixed in a 2.1.x patch release, we will need to create a release branch (from the 2.1.6 tag) before you can patch it. In addition, when merging the fix back into master there will probably need to be some manual labor to move the fix to the correct class.
The simplest would be not do a 2.1.7 patch, but to fix this as part of a 2.2.1 patch instead.