Re-indexing Segments that contain thetaSketches

Is it possible to re-index segments and use thetaSketches?
Currently I have a datasource that is being ingested with the following supervisor spec (uid_sketch is working properly here):
    {
      "type": "kafka",
      "dataSchema": {
        "dataSource": "pageview",
        "parser": {
          "type": "avro_stream",
          "avroBytesDecoder": {
            "type": "schema_registry",
            "url": "http://schema-registry:8081"
          },
          "parseSpec": {
            "format": "avro",
            "flattenSpec": {
              "useFieldDiscovery": "true",
              "fields": [
                "articleId",
                "uid",
                "some-fields-that-need-to-be-flattened..."
              ]
            },
            "timestampSpec": {
              "column": "timestamp",
              "format": "auto"
            },
            "dimensionsSpec": {
              "dimensions": [
              	{
                  "type": "long",
                  "name": "articleId"
                },
                "some-other-dimensions..."
              ],
              "dimensionExclusions": [
                  "uid"
                ]
            }
          }
        },
        "metricsSpec": [
          {
            "type": "count",
            "name": "count"
          },
          {
		"type" : "thetaSketch",
		 "name" : "uid_sketch",
		 "fieldName" : "uid",
		"size": 4096
	 }
        ],
        "granularitySpec": {
          "type": "uniform",
          "segmentGranularity": "DAY",
          "queryGranularity": "minute",
          "rollup": true,
          "intervals": null
        },
        "transformSpec": {
          "filter": null,
          "transforms": []
        }
      },
      "ioConfig": {
        "topic": "kafka-topic",
        "replicas": 1,
        "taskCount": 1,
        "taskDuration": "PT18000S",
        "consumerProperties": {
          "bootstrap.servers": "kafka:9092"
        }
      }
    }

What I am trying to do is to re-index the "pageview" datasource into a new datasource "pageview-reindexed", for a certain interval and only for the dimension "articleId", the metric "uid_sketch" and a queryGranularity of "ten_minute".
The re-indexing task looks like this:
    {
        "type": "index",
        "spec": {
            "dataSchema": {
                "dataSource": "pageview-reindexed",
                "parser": {
                    "parseSpec": {
                        "flattenSpec": {
                            "useFieldDiscovery": "true",
                            "fields": [
                            "articleId",
                            "uid",
                            "some-fields-that-need-to-be-flattened..."
                          ]
                        },
                        "timestampSpec": {
                            "column": "timestamp",
                            "format": "auto"
                        },

                        "dimensionsSpec": {
                            "dimensions": [
                                {
                                    "type": "long",
                                    "name": "articleId"
                                }
                            ]
                        }
                    }
                },
                "metricsSpec": [
                    {
                        "type": "thetaSketch",
                        "name": "uid_sketch",
                        "fieldName": "uid",
                        "size": 4096
                    }
                ],
                "granularitySpec": {
                    "type": "uniform",
                    "segmentGranularity": "DAY",
                    "queryGranularity": "ten_minute",
                    "rollup": true,
                    "intervals": null
                }
            },
            "ioConfig": {
                "type": "index",
                "firehose": {
                    "type": "ingestSegment",
                    "dataSource": "pageview",
                    "interval": "2019-05-12/2019-05-15"
                },
                "appendToExisting": false
            }
        }
    }

The indexing task finishes successfully and the dimension "articleId" seems to be ingestet properly but the thetaSketches are "null" for every entry.
Executing the following query
    {
      "queryType": "select",
      "dataSource": "pageview-reindexed",
      "dimensions": [],
      "metrics": [],
      "intervals": [
         "2019-05-13T10:00:00.000Z/P1D"
      ],
      "granularity": "all",
      "pagingSpec": {
        "pagingIdentifiers": {},
        "threshold": 100
      }
    }

will give results where the metric "uid_sketch" is always null.
    [
        {
            "timestamp": "2019-05-13T10:00:00.000Z",
            "result": {
                "pagingIdentifiers": {
                    "pageview-raw-reindexed_2019-05-13T10:00:00.000Z_2019-05-14T00:00:00.000Z_2019-05-15T10:13:47.886Z": 99
                },
                "dimensions": [
                    "articleId"
                ],
                "metrics": [
                    "uid_sketch"
                ],
                "events": [
                    {
                        "segmentId": "pageview-raw-reindexed_2019-05-13T10:00:00.000Z_2019-05-14T00:00:00.000Z_2019-05-15T10:13:47.886Z",
                        "offset": 0,
                        "event": {
                            "timestamp": "2019-05-13T10:00:00.000Z",
                            "articleId": 219,
                            "uid_sketch": null,
                        }
                    },
    ...

Am I doing something wrong or is it simply not possible to use thetaSketches when re-indexing?

in reindexing task , try adding "isInputThetaSketch":true to metric spec for uid_sketch
more info can be found in http://druid.io/docs/latest/development/extensions-core/datasketches-theta.html


Add a path prefix

description
Changes the marketplace to sit at the index and all detail pages to be at /quickstart_name/uuid. Also adds configuration to set a path prefix for /instant-observability.
TODO:

[ ] Update readme
[ ] Get rid of commented out code

Closes newrelic/developer-website/issues/2004

This should be merged after #8


How to train 61 point ?

i want to train the model again with 61 points,
can you teach me?
thanks

i want to train the model again with 61 points, can you teach me? thanks

Hi,
https://github.com/gwxie/Document-Dewarping-with-Control-Points/blob/ba4639ff1a0c8884d549e7fae3a9bddf1bef14ab/Source/dataloader.py#L74
https://github.com/gwxie/Document-Dewarping-with-Control-Points/blob/ba4639ff1a0c8884d549e7fae3a9bddf1bef14ab/Source/dataloader.py#L75
set  row_gap and col_gap  = 0


Fix mozilla/thimble.mozilla.org#2252: Change position of Download action in the right-click menu

This is my first PR. Please let me know if any changes are required. Thanks.

Thanks very much for submitting @serendicoder - I'll test it out tomorrow.
Could you please add the following text to the PR description...

Fixes #XXXX - where XXXX is the number of the issue this addresses?

This way, once this is merged, that issue will be automatically closed. Thanks!

@flukeout it's in the commit itself so it should close automatically as well. @serendicoder, however, it would be good to mention the issue description (what is this pr fixing) in the pr description as well so that reviewers know immediately what this pr is meant to do.

Thanks @flukeout and @gideonthomas. I have added the link to the Thimble issue in description.

Nice job, @serendicoder, thanks for contributing to Thimble and Brackets.


Update bson to 4.7.1

Updates org.mongodb:bson from 4.2.3 to 4.7.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mongodb", artifactId = "bson" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.mongodb", artifactId = "bson" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #135.


Getting error while composing with binance-redis

Version

Description
Getting error with command docker-compose -f docker-compose.server.yml up -d

Here is the log
gitpod /workspace/binance-trading-bot $ docker-compose -f docker-compose.server.yml up -d
Creating binance-mongo ... done
Creating binance-redis ... error
Creating binance-bot   ... done
ERROR: for binance-redis  Cannot start service binance-redis: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: write sysctl key net.core.somaxconn: open /proc/sys/net/core/somaxconn: no such file or directory: unknown
ERROR: for binance-redis  Cannot start service binance-redis: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: write sysctl key net.core.somaxconn: open /proc/sys/net/core/somaxconn: no such file or directory: unknown
ERROR: Encountered errors while bringing up the project.
gitpod /workspace/binance-trading-bot $
I am in the master branch in case it might help!

That is nothing to do with the bot.
Maybe try to remove this line as the error message suggested.

https://github.com/chrisleekr/binance-trading-bot/blob/master/docker-compose.server.yml#L29

Please close the issue if your issue is resolved.

Yes, The problem looks solved but I cannot get any thing at port 8080 , It shows localhost didn't send any data.
Is there any thing to do with the line i removed in the previous error?
And i have ran docker logs and it too gave error and written log into error.log file
error.log
this log is created when i ran docker logs binance-bot --tail=1000 2> error.log
error1.log
This log is created when i ran docker logs binance-bot --tail=1000 1> error1.log
I can see that there is nothing problem in error1.log but i dont know about error.log file.
Hope this log files help.

Thanks for providing logs. I got the log, please remove your log.
[ioredis] Unhandled error event: Error: getaddrinfo ENOTFOUND binance-redis
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26)

If you see the log, binance redis is not accessible.
In second log, I can see you are running live mode without live api/secret key.

Yes i have used test api keys. Is there any problem to use test api keys?
I doubt.

Then set mode to test, not live

I will check it.

Yes it's working now.
But i am curious what is the role of "sysctls:
net.core.somaxconn: 1024" and why it this process is not able to run.

It's for Redis in Linux. You can do some more research on Google.
Good to hear your issue is resolved. Please close the issue. Thanks.

Ok

Ok


Installation fails

Hi all,
I'm getting the following error message when trying to install smt. Any ideas?

(base) minas-macbook:~ minas$ pip install smt
Collecting smt
  Using cached https://files.pythonhosted.org/packages/94/32/1a45b1d6018a758455b5da7e0adc0f518cfed77d3146172550f9655c167f/smt-0.4.0.tar.gz
Requirement already satisfied: scikit-learn in ./anaconda3/lib/python3.7/site-packages (from smt) (0.22)
Requirement already satisfied: pyDOE2 in ./anaconda3/lib/python3.7/site-packages (from smt) (1.2.1)
Requirement already satisfied: matplotlib in ./anaconda3/lib/python3.7/site-packages (from smt) (3.1.2)
Requirement already satisfied: numpydoc in ./anaconda3/lib/python3.7/site-packages (from smt) (0.9.1)
Requirement already satisfied: six>=1.10 in ./anaconda3/lib/python3.7/site-packages (from smt) (1.13.0)
Requirement already satisfied: scipy in ./anaconda3/lib/python3.7/site-packages (from smt) (1.4.1)
Requirement already satisfied: joblib>=0.11 in ./anaconda3/lib/python3.7/site-packages (from scikit-learn->smt) (0.14.1)
Requirement already satisfied: numpy>=1.11.0 in ./anaconda3/lib/python3.7/site-packages (from scikit-learn->smt) (1.17.4)
Requirement already satisfied: kiwisolver>=1.0.1 in ./anaconda3/lib/python3.7/site-packages (from matplotlib->smt) (1.1.0)
Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1 in ./anaconda3/lib/python3.7/site-packages (from matplotlib->smt) (2.4.5)
Requirement already satisfied: python-dateutil>=2.1 in ./anaconda3/lib/python3.7/site-packages (from matplotlib->smt) (2.8.1)
Requirement already satisfied: cycler>=0.10 in ./anaconda3/lib/python3.7/site-packages (from matplotlib->smt) (0.10.0)
Requirement already satisfied: Jinja2>=2.3 in ./anaconda3/lib/python3.7/site-packages (from numpydoc->smt) (2.10.3)
Requirement already satisfied: sphinx>=1.6.5 in ./anaconda3/lib/python3.7/site-packages (from numpydoc->smt) (2.3.0)
Requirement already satisfied: setuptools in ./anaconda3/lib/python3.7/site-packages (from kiwisolver>=1.0.1->matplotlib->smt) (42.0.2)
Requirement already satisfied: MarkupSafe>=0.23 in ./anaconda3/lib/python3.7/site-packages (from Jinja2>=2.3->numpydoc->smt) (1.1.1)
Requirement already satisfied: babel!=2.0,>=1.3 in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (2.7.0)
Requirement already satisfied: sphinxcontrib-serializinghtml in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (1.1.3)
Requirement already satisfied: alabaster<0.8,>=0.7 in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (0.7.12)
Requirement already satisfied: Pygments>=2.0 in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (2.5.2)
Requirement already satisfied: docutils>=0.12 in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (0.15.2)
Requirement already satisfied: sphinxcontrib-applehelp in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (1.0.1)
Requirement already satisfied: sphinxcontrib-devhelp in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (1.0.1)
Requirement already satisfied: imagesize in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (1.1.0)
Requirement already satisfied: requests>=2.5.0 in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (2.22.0)
Requirement already satisfied: packaging in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (19.2)
Requirement already satisfied: snowballstemmer>=1.1 in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (2.0.0)
Requirement already satisfied: sphinxcontrib-htmlhelp in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (1.0.2)
Requirement already satisfied: sphinxcontrib-qthelp in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (1.0.2)
Requirement already satisfied: sphinxcontrib-jsmath in ./anaconda3/lib/python3.7/site-packages (from sphinx>=1.6.5->numpydoc->smt) (1.0.1)
Requirement already satisfied: pytz>=2015.7 in ./anaconda3/lib/python3.7/site-packages (from babel!=2.0,>=1.3->sphinx>=1.6.5->numpydoc->smt) (2019.3)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in ./anaconda3/lib/python3.7/site-packages (from requests>=2.5.0->sphinx>=1.6.5->numpydoc->smt) (1.25.7)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in ./anaconda3/lib/python3.7/site-packages (from requests>=2.5.0->sphinx>=1.6.5->numpydoc->smt) (3.0.4)
Requirement already satisfied: idna<2.9,>=2.5 in ./anaconda3/lib/python3.7/site-packages (from requests>=2.5.0->sphinx>=1.6.5->numpydoc->smt) (2.8)
Requirement already satisfied: certifi>=2017.4.17 in ./anaconda3/lib/python3.7/site-packages (from requests>=2.5.0->sphinx>=1.6.5->numpydoc->smt) (2019.11.28)
Building wheels for collected packages: smt
  Building wheel for smt (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /Users/minas/anaconda3/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-install-osckrkkq/smt/setup.py'"'"'; __file__='"'"'/private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-install-osckrkkq/smt/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-wheel-wngmre_f --python-tag cp37
       cwd: /private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-install-osckrkkq/smt/
  Complete output (91 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.macosx-10.7-x86_64-3.7
  creating build/lib.macosx-10.7-x86_64-3.7/smt
  copying smt/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt
  creating build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/rmts.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/surrogate_model.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/qp.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/ls.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/kpls.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/krg.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/rbf.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/kplsk.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/gekpls.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/rmtc.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/rmtb.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/genn.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/krg_based.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  copying smt/surrogate_models/idw.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
  creating build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/ndim_cantilever_beam.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/robot_arm.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/tensor_product.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/cantilever_beam.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/ndim_robot_arm.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/reduced_problem.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/water_flow.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/lp_norm.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/ndim_rosenbrock.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/branin.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/welded_beam.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/ndim_step_function.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/problem.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/rosenbrock.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/wing_weight.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/sphere.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/torsion_vibration.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  copying smt/problems/water_flow_lfidelity.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
  creating build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
  copying smt/sampling_methods/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
  copying smt/sampling_methods/random.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
  copying smt/sampling_methods/sampling_method.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
  copying smt/sampling_methods/lhs.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
  copying smt/sampling_methods/full_factorial.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
  creating build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/silence.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/misc.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/sm_test_case.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/linear_solvers.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/line_search.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/options_dictionary.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/checks.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/caching.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/printer.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  copying smt/utils/kriging_utils.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
  creating build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  copying smt/utils/neural_net/metrics.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  copying smt/utils/neural_net/fwd_prop.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  copying smt/utils/neural_net/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  copying smt/utils/neural_net/model.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  copying smt/utils/neural_net/loss.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  copying smt/utils/neural_net/activation.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  copying smt/utils/neural_net/bwd_prop.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  copying smt/utils/neural_net/optimizer.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  copying smt/utils/neural_net/data.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
  creating build/lib.macosx-10.7-x86_64-3.7/smt/applications
  copying smt/applications/mfk.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
  copying smt/applications/vfm.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
  copying smt/applications/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
  copying smt/applications/application.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
  copying smt/applications/moe.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
  copying smt/applications/ego.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
  running build_ext
  building 'smt.surrogate_models.rbfclib' extension
  creating build/temp.macosx-10.7-x86_64-3.7
  creating build/temp.macosx-10.7-x86_64-3.7/smt
  creating build/temp.macosx-10.7-x86_64-3.7/smt/src
  creating build/temp.macosx-10.7-x86_64-3.7/smt/src/rbf
  gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/minas/anaconda3/include -arch x86_64 -I/Users/minas/anaconda3/include -arch x86_64 -Ismt/src/rbf -I/Users/minas/anaconda3/lib/python3.7/site-packages/numpy/core/include -I/Users/minas/anaconda3/include/python3.7m -c smt/src/rbf/rbfclib.cpp -o build/temp.macosx-10.7-x86_64-3.7/smt/src/rbf/rbfclib.o -std=c++11
  warning: include path for stdlibc++ headers not found; pass '-stdlib=libc++' on the command line to use the libc++ standard library instead [-Wstdlibcxx-not-found]
  smt/src/rbf/rbfclib.cpp:636:10: fatal error: 'ios' file not found
  #include "ios"
           ^~~~~
  1 warning and 1 error generated.
  error: command 'gcc' failed with exit status 1
  ----------------------------------------
  ERROR: Failed building wheel for smt
  Running setup.py clean for smt
Failed to build smt
Installing collected packages: smt
    Running setup.py install for smt ... error
    ERROR: Command errored out with exit status 1:
     command: /Users/minas/anaconda3/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-install-osckrkkq/smt/setup.py'"'"'; __file__='"'"'/private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-install-osckrkkq/smt/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-record-w936ox04/install-record.txt --single-version-externally-managed --compile
         cwd: /private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-install-osckrkkq/smt/
    Complete output (91 lines):
    running install
    running build
    running build_py
    creating build
    creating build/lib.macosx-10.7-x86_64-3.7
    creating build/lib.macosx-10.7-x86_64-3.7/smt
    copying smt/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt
    creating build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/rmts.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/surrogate_model.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/qp.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/ls.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/kpls.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/krg.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/rbf.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/kplsk.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/gekpls.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/rmtc.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/rmtb.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/genn.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/krg_based.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    copying smt/surrogate_models/idw.py -> build/lib.macosx-10.7-x86_64-3.7/smt/surrogate_models
    creating build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/ndim_cantilever_beam.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/robot_arm.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/tensor_product.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/cantilever_beam.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/ndim_robot_arm.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/reduced_problem.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/water_flow.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/lp_norm.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/ndim_rosenbrock.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/branin.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/welded_beam.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/ndim_step_function.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/problem.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/rosenbrock.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/wing_weight.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/sphere.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/torsion_vibration.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    copying smt/problems/water_flow_lfidelity.py -> build/lib.macosx-10.7-x86_64-3.7/smt/problems
    creating build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
    copying smt/sampling_methods/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
    copying smt/sampling_methods/random.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
    copying smt/sampling_methods/sampling_method.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
    copying smt/sampling_methods/lhs.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
    copying smt/sampling_methods/full_factorial.py -> build/lib.macosx-10.7-x86_64-3.7/smt/sampling_methods
    creating build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/silence.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/misc.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/sm_test_case.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/linear_solvers.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/line_search.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/options_dictionary.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/checks.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/caching.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/printer.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    copying smt/utils/kriging_utils.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils
    creating build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    copying smt/utils/neural_net/metrics.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    copying smt/utils/neural_net/fwd_prop.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    copying smt/utils/neural_net/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    copying smt/utils/neural_net/model.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    copying smt/utils/neural_net/loss.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    copying smt/utils/neural_net/activation.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    copying smt/utils/neural_net/bwd_prop.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    copying smt/utils/neural_net/optimizer.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    copying smt/utils/neural_net/data.py -> build/lib.macosx-10.7-x86_64-3.7/smt/utils/neural_net
    creating build/lib.macosx-10.7-x86_64-3.7/smt/applications
    copying smt/applications/mfk.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
    copying smt/applications/vfm.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
    copying smt/applications/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
    copying smt/applications/application.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
    copying smt/applications/moe.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
    copying smt/applications/ego.py -> build/lib.macosx-10.7-x86_64-3.7/smt/applications
    running build_ext
    building 'smt.surrogate_models.rbfclib' extension
    creating build/temp.macosx-10.7-x86_64-3.7
    creating build/temp.macosx-10.7-x86_64-3.7/smt
    creating build/temp.macosx-10.7-x86_64-3.7/smt/src
    creating build/temp.macosx-10.7-x86_64-3.7/smt/src/rbf
    gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/minas/anaconda3/include -arch x86_64 -I/Users/minas/anaconda3/include -arch x86_64 -Ismt/src/rbf -I/Users/minas/anaconda3/lib/python3.7/site-packages/numpy/core/include -I/Users/minas/anaconda3/include/python3.7m -c smt/src/rbf/rbfclib.cpp -o build/temp.macosx-10.7-x86_64-3.7/smt/src/rbf/rbfclib.o -std=c++11
    warning: include path for stdlibc++ headers not found; pass '-stdlib=libc++' on the command line to use the libc++ standard library instead [-Wstdlibcxx-not-found]
    smt/src/rbf/rbfclib.cpp:636:10: fatal error: 'ios' file not found
    #include "ios"
             ^~~~~
    1 warning and 1 error generated.
    error: command 'gcc' failed with exit status 1
    ----------------------------------------
ERROR: Command errored out with exit status 1: /Users/minas/anaconda3/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-install-osckrkkq/smt/setup.py'"'"'; __file__='"'"'/private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-install-osckrkkq/smt/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/var/folders/02/l70vh6k13r95s3_j908sgqrw0000gp/T/pip-record-w936ox04/install-record.txt --single-version-externally-managed --compile Check the logs for full command output.`

Compilation problem on MacOSX... Maybe solution in issue #130 will help.

Hi relf,
I managed to solve my issue by following your suggestion. In particular I added the following code on the top of the setup.py file and installed set from source.
if sys.platform == 'darwin':
    os.environ['MACOSX_DEPLOYMENT_TARGET'] = '10.9'

Moreover, I can confirm that one will encounter the same issue in most modern Mac machines. So it might be a good idea to include this line of code by default in the release version.
Cheers

Actually I think you can set the environment variable then install as usual:

$ export MACOSX_DEPLOYMENT_TARGET = '10.9'
$ pip install smt

I can not test it, but it should do the trick.

hi guys i have some problem with thath shit can u help me pls?
ERROR: Command errored out with exit status<PHONE_NUMBER>:
command: 'c:\users\sudurra\appdata\local\programs\python\python39\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\sudurra\AppData\Local\Temp\pip-install-zkqbpoic\smt\setup.py'"'"'; file='"'"'C:\Users\sudurra\AppData\Local\Temp\pip-install-zkqbpoic\smt\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base 'C:\Users\sudurra\AppData\Local\Temp\pip-pip-egg-info-j0t7eipb'
cwd: C:\Users\sudurra\AppData\Local\Temp\pip-install-zkqbpoic\smt
Complete output (1 lines):
Numpy import failed: please install numpy module
----------------------------------------
ERROR: Command errored out with exit status<PHONE_NUMBER>: python setup.py egg_info Check the logs for full command output.

You have to install numpy. You have some guidance in the doc


lock operation

As the title, is it possible to lock keys?

Need lock support too.

no stale pls


Add colors to diff lines

We currently log a truncated list of changes when there's a cache miss that results in a diff file.
https://github.com/ds300/lazyrepo/blob/1d58bf04fc28655613574d2e14b05fad077c1635/src/runTask.js#L45-L56
We should add some subtle color here to provide extra visual cues of what changed to cause the cache miss.
I previously had it so that the +, -, and ± symbols were green, red, and yellow respectively, with the rest of the line remaining gray. That worked for me, but feel free to experiment.

done in #77


Exclude null address from supply queries

Background
There is currently no mechanism to burn tokens on Osmosis.
One is required to account for the additional OSMO generated during the mistiming of the thirdening event this year.
Suggested Design
@ValarDragon suggested excluding an inaccessible address from being included in supply queries, thus creating a burn address.
This address would be osmo1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqmcn030 which is the osmo bech32 translation of the null address.
This can be confirmed with osmosisd debug addr<PHONE_NUMBER>000000000000000000000000000000
Acceptance Criteria
A user can dispose of tokens by either a burn transaction or performing a bank send to osmo1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqmcn030
Any tokens in this address are not included in any supply queries.

This has passed governance: https://www.mintscan.io/osmosis/proposals/551


Can't make it work on iOS

Which platform(s) does your issue occur on?
iOS
iOS: 14.3
emulator
Please, provide the following version numbers that your issue occurs with:
CLI: 8.0.2
@nativescript-community/ui-label": "^1.2.0
@nativescript/ios": "8.0.2
Please, tell us how to recreate the issue in as much detail as possible.
iOS you cant use html tags and class in the same time. You lost the class style if you do it.
For example:
  <label:Label class="warning body black-3 md" html="Hey I'm a <b>bold</b>" textWrap="true"/>
That's no going to work because I'm using html tags and class in the same time.

@angel-lizander i cant really tell what your issue really is but i can confirm that this plugin works perfectly fine while using class + html on both iOS / Android. Just tested it.

@angel-lizander i cant really tell what your issue really is but i can confirm that this plugin works perfectly fine while using class + html on both iOS / Android. Just tested it.

Are you using Nativescript Angular, Vue or Typescript? Could you give me more details. Cause I'm using Nativescript Typescript without any success using the last version of iOS on Simulator

@angel-lizander using vue there but would not make any difference. I cant tell your real issue with more details.
Something else is going on


[DEVOPS-531] Handle separate distro configs

Handle distro config split for deploy and maintenance firmware in
Makefile and CI

merge after https://github.com/iris-GmbH/meta-iris-base/pull/125

https://wiki.iris-sensing.net/x/xQF1Fw does something needs to be updated here afterwards?

https://wiki.iris-sensing.net/x/xQF1Fw does something needs to be updated here afterwards?

yes. However, merging is currently still blocked by introduction of gitlab runner builds anyways. Will update afterwards.

it would actually be smarter to use the distro configurations as new base config and statically include the configuration currently in the base config. This would remove an unnecessary, but currently mandatory dynamic include.
Reminder to myself to fix this.

Merged into https://github.com/iris-GmbH/iris-kas/pull/112


coq: 8.5pl1 -> 8.5pl2

Things done

[ ] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

This looks good to me, trying now.


add support for UUID v7 in RequestId

Linked Issue: #115

Description:
feature flag uuid_v7 is introduced which inturn enables v7 feature flag in the uuid dependency Support documentation is added in README.md, src/lib.rs and src/request_id.rs
This feature only works if this crate or any crate dependent on this crate has enabled the compile time configuration flag provided to the rust compiler. RUSTFLAGS="--cfg uuid_unstable".

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hey @LukeMathWalker, I have fixed the formatting and the Github action test created for uuid_v7. Let me know if I am missing something.

Thank you!


⚠ Bofrost.lu has degraded performance

In 3769558, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 844 ms

Resolved: Bofrost.lu performance has improved in 456caa0 after 7 minutes.


Why db_sampler is disabled by default?

Hi, Tianwei,
I noticed a enable=False in db_sampler in the configs. Does  that mean CenterPoint do not use copy-paste augmentation by default?
If there are no misunderstandings, I wonder why CenterPoint  disable it?

no, we use copy-paste.
For nuScenes, the improvements are not too large (maybe 0.5 nds), for Waymo, it doesn't improve vehicle / pedestrian, but matters a lot for cyclists
this enable=False is a dummy value, I simply copy the config from past configs and the code never use this value. To disable db_sampler, set it to None


show-event-details attribute was being ignored in Month view

Although the show-event-details attribute was visible to the Controller, the Month view template didn't do anything. Added an ng-show condition on showEventDetails. Seems to work now.
I've also added a section on the title-changed attribute to the README since this wasn't mentioned despite being used in the demo (and it's quite useful).

@anselanza You are right, I missed the show-event-details and title-changed attributes.
I'm happy to accept your commits. But could you do some slight modification to your commits.

Squash your commits into one or two commits, as I don't want to include the "debugging" commits into the history.
You are using ng-show to control the visibility of the event detail section. Could you instead use ng-if? Because it will align with my another pure AngularJS version calendar and it also won't generate extra dom elements into the tree.

Thanks.

Ah, thanks for the tips. I'll amend quickly.

Better?

@anselanza Thanks for the fix!

@anselanza I changed from ng-if to ng-show again. Because I found it's related to an issue.
https://github.com/driftyco/ionic/issues/4281

Ah, that's weird. Thanks for letting me know.


include CC license in footer

it would be nice to have a properly formatted CC license in the footer, perhaps in the style of the social links.
CC provides nice html for this purpose, like so, from: https://creativecommons.org/choose/

Dieses Werk ist lizenziert unter einer Creative Commons Namensnennung - Nicht kommerziell - Keine Bearbeitungen 4.0 International Lizenz

Will take the idea into account for the dev branch. No ETA or promise to implement yet.

As hugo-agency-theme is mostly in maintenance mode and no new features will be added.
We created Syna as a more flexible iteration of this theme.
Syna does support customizing a footer fragment to implement this.


Client login service

move signin signup logic to client login service

LGTM, should make a ticket to remove all the old SignIn/SignUp models once this is tested

https://nanopay.atlassian.net/browse/NP-9554


rename onExit to something else

onExit to closely implies it has the exact behavior of process.on('exit but as it is async it does not. Especially when it comes to which exist status code is chosen during some race scenarios.

Thanks @stefanpenner, we can circle back to this when we have free cycles...

Ya, the original intent was to be like on("exit" but this was before understanding the various exit code precedence rules. At which point it became obvious it needed to become a different thing.

one idea:
var captureExit = require('capture-exit');
captureExit.captureExit();

captureExit.asyncCleanup(function() { // renamed from onExit
  return ensureCleanup();
});

process.on('exit', function() {
  process.exit(1);
});

@rwjblue @stefanpenner perhaps beforeExit is the better analog.

it allows async code, as beforeExit does
its process.exit(code) semantics are closer to beforeExit's

The difference is that beforeExit code in node is not guaranteed to be run.  capture-exit more or less gives you a way of writing a beforeExit handler that will reliably run.

I'm nervous it is not quite the as node existing beforeExit. I believe our hook fires in more cases then beforeExit If that isn't true maybe its fine, but otherwise a unique name may be appropriate.

@stefanpenner yes our hook absolutely does fire more often than node's does.

The difference is that beforeExit code in node is not guaranteed to be run. capture-exit more or less gives you a way of writing a beforeExit handler that will reliably run.

It was the point I was making ^.
Still I can see that this difference may be enough to not want to make an analogy to any of node's exit event hooks at all.

we could called it betterBeforeExit or actuallyBeforeExit or something funny :P

beforeExitAndIMeanActuallyRunLikeAllTheTimeBecauseYouNeedThisShitToHappen

beforeExitAndIMeanActuallyRunLikeAllTheTimeBecauseYouNeedThisShitToHappen

sounds like the one!

what about addHandler?
var captureExit = require('capture-exit');
captureExit.captureExit();

captureExit.addHandler(function() {
  return ensureCleanup();
});


"Jirlău" is listed in the drop-down menu

Description:
"Jirlău" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Jirlău" in the search bar.

Expected results
The location is listed in the drop-down menu as "Jirlău, Brăila (Jirlău)".


[Feature Request] Image to text

Description of the new feature / enhancement
You can screenshot like using 'WIN + SHIFT + S' or use an already existing image and extract text from the given image. (similar to Google Lens)
Scenario when this would be used?
You have taken a photo were text is written on your phone and you want to add the text to your notes. You synchronize the photo onto your PC and extract the text.
You are watching a video (or online meeting or presentation) and your want to get the text.
You have an image in the web were text is written and you want to get the text.
Supporting information
Google Lens is doing a good job for smartphones. Idk if there are already any programs for Windows.

Related to  #16067

Duplicate of # 4371

Issue is a duplicate
Thank you for your issue! We've linked your report against another issue to centralize the thread.
Thanks for helping us to make PowerToys a better piece of software.


Include Kotlin source files in source jar.

The source jar generated so far is empty because gradle tries to add Java sources.

Coverage remained the same at 86.835% when pulling df76a3093fbe2714941c3d04bd17ea243abbdadf on swiftrs:master into 573898af55c0fec5a0698c8c0deec2ce049fe043 on pgutkowski:master.

Thank you @swiftrs for your PR, I've releases to JCenter new versions with your contribution: 0.2.9 and 0.3.0-beta.


adaptiveHeight: slider is only as tall as first slide if SlidesToShow is more than 1

When SlidesToShow is more than 1 and adaptiveHeight is true, the slider will only be as tall as the first slide in the set of currently active slides. If subsequent slide are taller than the first, they will be cut off.
https://jsfiddle.net/tusinga/d0r9fnzb/

We are facing the same issue. Is anyone taking care this one?


Support for Gradle toolchains in Spring AOT Gradle plugin

With version 0.10.2 a defined Gradle toolchain seems not to be respected.
Therefore building a project that requires JDK 11 with the respective toolchain defined fails when using JDK 8 on the command line.
Toolchain definition in build.gradle which replaces sourceCompatibility = '1.8'.
java {
    toolchain {
        vendor = JvmVendorSpec.GRAAL_VM // since Gradle 7.1
        languageVersion = JavaLanguageVersion.of(11)
    }
}

To trigger the issue the following class has to be added to samples/commandlinerunner-gradle where @Validated seems to be the relevant piece:
package com.example.commandlinerunner;

import org.springframework.context.annotation.Configuration;
import org.springframework.validation.annotation.Validated;

@Configuration
@Validated
class SomeProperties {}

Building the project with Gradle 7.x fails:
$ sdk use java 8.0.292.hs-adpt
$ cd samples/commandlinerunner-gradle
$ ./gradlew wrapper --gradle-version 7.1.1
$ # update build.gradle as outlined above
$ ./gradlew bootBuildImage # or nativeBuild

> Task :compileJava
> Task :generateAot
> Task :generateAot FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':generateAot'.
> com/example/commandlinerunner/SomeProperties has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0

Closed with 7d8c598dd1065b37504
Thanks @darxriggs for noticing!


Not able to set up working example based on README instructions

First of all, this is awesome and thanks so much for your contribution! I've been trying to set up a working example locally for the past couple of days - noticing we went from 2.0 to 2.2 - yet either way I end up in a situation where both apps compile just fine but the consuming app has some 404s on some bundles and fails to load the federated component from the remote.
I troubleshooted all options including naming, ports, etc.
I wonder if you could provide more detailed instructions on setting up:

covering a scenario from complete scratch, including every single bash command as trivial as creating or entering folders, also creating the nextJS apps themselves from scratch
being MORE explicit and specific about which addition of code/config goes EXACTLY in which file, with path and full filename, perhaps showing the added code in more context
provide an updated repo (and keep it up to date) that showcases a stable working example based on latest framework versions and dependencies

Both frameworks and dependencies are moving incredibly fast in today's JS ecosystem. Without explicit, verified instructions a lot of folks may be blocked by running into trivial issues. Much thanks!

@Pkearney2021 thanks! I tried downgrading but now I get compilation errors about the webpack configuration. it'd be super helpful if someone could share either a tutorial or a repo where the latest version of this plugin works with at least SOME designated version of next. as for now we're just looking to build a POC around it.

Can you send me on a minimal repo of your issues?

Here is a super minimal repo, only has next2 in it yet. After downgrading to 10.2.3 and adding the custom next.config.js it won't even run, says it's using webpack4. https://github.com/peter-gorgenyi-mgm/nextjs-mf-troubleshooting

Hey, sorry I was commenting with two different accounts before.
So to make it run webpack 5 in the next.config.js add this.
future: {     webpack5: true   }
below reactStrictMode: true,
I tried it there and it worked fine :)

Full comnfig
const { withFederatedSidecar } = require("@module-federation/nextjs-mf");

module.exports = withFederatedSidecar({
  name: "next2",
  filename: "static/chunks/remoteEntry.js",
  exposes: {
    "./sampleComponent": "./components/sampleComponent.js",
  },
  shared: {
    react: {
      // Notice shared are NOT eager here.
      requiredVersion: false,
      singleton: true,
    }
  },
})({
  reactStrictMode: true,
  future: {
    webpack5: true
  }
});

A good example to follow would be this repo
https://github.com/module-federation/module-federation-examples/tree/master/nextjs

Thanks a lot for the config details, Phil. Let me see if I can now complete a stable setup in that repo. Also yes, I have noticed that example repo, I was just disregarding it because of some outdated versions. But it seems like we'll have to wait for this plugin to work with the latest and greatest.

@Pkearney2021 ...aaaaand that was it! Thanks so much for walking me through the details! I can now successfully run an example as well as build them. I will update my example repo soon with the final working setup. I will also open a PR with more detail to the setup instructions as I'm sure others could use it as well. Then I will close this issue.

Here is my simplified working example repo, I will keep this up to date with new developments around this plugin:
https://github.com/peter-gorgenyi-mgm/nextjs-mf-troubleshooting

@ScriptedAlchemy I created a local branch adding more explicit setup instructions after my initial struggle of setting up a working example. Here is a gist of the proposed README.md:
https://gist.github.com/peter-gorgenyi-mgm/410cdd60495cce39f31365c509e7ec5f
Note that some of the additions are temporary for the NextJS 10.2 setup until support for NextJS 11 arrives. If you agree with the additions, add me as a contributor and I can open a pull request. Alternatively feel free to take any part of this gist.
Once again, your contribution is truly appreciated! I will now close this issue.

Hey if there's any updates that should be added to the readme, I'll gladly accept PRs to improve ease of use.
I suffer from knowing how all this works and spending many months deep in MF land.
What i think everyone knows vs. what is actually known is hard to reconcile


vs_BuildTools: Invalid parameter "--config"

I can run this command no problem:
vs_BuildTools --config C:\hello\.vsconfig

but if I try this:
vs_BuildTools --config C:\hello\.vsconfig --layout layout

I get this result:
Visual Studio Setup Layout Tool, version 3.3.2185.63263
c Microsoft Corporation. All rights reserved.

Error: Invalid parameter "--config".

Some people have said you can just use --add a bunch, but I don't want to do that. Current config file contains 11 items, but it could get much larger depending on the situation. So it seems silly to need to put tens of arguments on the command line, when I have a config file thats ready to go.

@89z -- Steven, thank you for your feedback.  Are you following a particular learn.microsoft.com article?  Meanwhile, please consider these resources:

Visual Studio on Microsoft Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

https://learn.microsoft.com/visualstudio/install/command-line-parameter-examples
https://learn.microsoft.com/visualstudio/install/set-defaults-for-enterprise-deployments
https://learn.microsoft.com/visualstudio/install/use-command-line-parameters-to-install-visual-studio

@89z -- Steven, thank you for those links.  Please try this experiment, placing --config as the last item, and let me know your results:
vs_BuildTools --layout layout --config C:\hello\.vsconfig

cc @anandmeg for awareness

Nope, same result. I would please ask that you not make any further suggestions, unless you've tested them yourself. I respect your time, so I ask the same of you.

@89z -- Steven, thank you for trying that.  I only work with the prose side, and don't have the setup to test this or possible alternatives.  My colleague Megha created those articles.
If you feel this is a product issue, please add it here:

Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.

@anandmeg -- Megha, please look into this potential documentation issue.

Hi @89z - This is an existing limitation that we've known about for a while and are planning to address soon.  It has to do with passing in a config file to a layout irrespective of SKU.  The community has made a feature request to fix this and you're welcome to upvote it and follow it to get progress updates.  Thanks for taking the time to report this issue.
@Tanuja-Kulal fyi

@christineruana with all due respect, its been nearly four years since that issue was posted.
I do appreciate your response and your respectful attitude, but the words ring hollow when you realize that no action has been done in that amount of time. I would rather just hear you say, "sorry but this is low priority, it will likely be another X years before this is addressed", or even just close the issue as WONTFIX, if the resolution is further years down the road. At least then people can drop any false hope that they might have. Again I appreciate your kind an respectful response, but I would also appreciate some openness and honesty about the reality of the situation.

@89z The reality is that I spoke to the dev today and believe that the fix has been already checked in.  I don't know exactly when it will ship and I want to try it out first to make sure it addresses the problems that you and the others are talking about before I commit publicly which release it will be in.  If you're interested in getting updates on this topic, I suggest you follow that Dev Community ticket which I will be posting status updates to.

@89z, thanks for your feedback. Please follow the ticket for updates.


Make Course Model parcel to prevent a bug when trying to save app states

Hi,
I was playing out with this app and checkout the new architecture.
I found this bug in implementing parcelable. I did this fix to make it better.
Thanks,
yifan

Wish to avoid using parcelable. Will fix this with AutoParcel. Thanks for reporting.


[Feature] Install tool directory to the ~/.cnf-testsuite directory and add it to the PATH

Is your feature request related to a problem? Please describe.
The tool directory is added to your current path.  The user could be anywhere.  How will the binary find the tools if you go to a new directory? How do they cleanup later?
Describe the solution you'd like
Install the tools to the cnf-testsuite folder (~/.cnf-testsuite).
Update the cnf-testsuite to use the tools from the new path.
Add the tool folder to the user PATH during setup (cnf-testsuite setup)
Describe alternatives you've considered
n/a
**How will this be tested? aka Acceptance Criteria (optional) **
(optional: unnecessary for things like some version bumps etc.)
Once this issue is addressed how will the fix be verified?
The tools folder will be in ~/.cnf-testsuite
Additional context

@taylor is this issue still relevant for CNTI?


Load .Rdata file via drag & drop/context menu option?

Currently, you can load an Rdata file via the load workspace button in the R Interactive Pane or by typing load(path/to/file.Rdata) in the interpreter. Dragging and dropping an Rdata file into the interactive pane writes the full path of the Rdata file to the current line of the interpreter. Double clicking on an RData file opens a new R GUI to load the RData file (outside of VS).
It would be nice if any one of the following features could be added:

dragging and dropping an R data file into the interactive pane automatically loads the workspace.
Right-clicking on an Rdata file gives the option: load workspace.
Double-clicking an Rdata file loads it into the active R interpreter.

Looks like option 3 has been implemented.


Bump requests to latest version

The requests package in setup.py is really old, and it breaks compatibility with other packages that I would like to have installed in the same virtualenv.
This could be as easy as changing "requests==2.2.1", to "requests>=2.2.1", in setup.py.

Good point. Let's make Python Tracker compatible to latest version in next release and pin it in setup.py.
Though if it is possible I would factor out as many dependencies from trackers as possible.


tvOS support in Produce and Deliver?

[x] Updated fastlane to the latest version
[x] I have read the [Contribution Guidelines]

Does Produce support creation of tvOS apps on iTunes yet? (I just use it to register Identifier on Apple dev portal for now though, and create app on iTunes manually and create Provisioning profiles for it manually).
if yes, how to what parameter to pass in command line?
And does Deliver supports metadata transfer support for tvOS apps? If yes guide me through it please.

Sorry, currently produce doesn't support tvOS. deliver already supports tvOS, the best way to get started is to run deliver init on a project that already has tvOS metadata.


Spend in get_spend_tx and set_spend_tx messages...

...serialized in base64 instead of hex.
Closes #94

ACK 509a48a


Failure creating vertex with name close to MAX_LABEL_NAME_LEN 65535

The maximum langth for label ( vertex ) name for application Age is defined as following:
#define MAX_LABEL_NAME_LEN 65535
in the file name_validation.h
Checking behavior of application, creating vertexs with length approaching limit of 65535 characters encountered this behavior:
1 Attempt to create first edge with name length 65536 success.
However
2 subsequent request to create vlabel with name with last two characters removed fails with message:
-- ERROR:  label "vertexwithextremelyveryveryveryverylongnamenamenamenamenamename" already exists
-- SQL state: 3F000
I think 65535 is not very reasonable length for the name of vertex. So, please do reconsider, but if it is decided to support 65535 character legth, please do ensure it is working.
select create_vlabel('test_graph', 'vertexwithextremelyveryveryveryverylongnamenamenamename<...>');
-- NOTICE:  VLabel "vertexwithextremelyveryveryveryverylongnamenamenamenamenamename" has been created
-- Successfully run. Total query runtime: 3 secs 93 msec.
-- 1 rows affected.

select create_vlabel('test_graph', 'vertexwithextremelyveryveryveryverylongnamenamenamename<...>');
-- ERROR:  label "vertexwithextremelyveryveryveryverylongnamenamenamenamenamename" already exists
-- SQL state: 3F000

@MironAtHome Good find!
This one is due to the usage of the PG type Name, see below. It looks like we'll either have to limit names to NAMEDATALEN or use a different method.
It appears that whomever used Name in this case either didn't realize the drawbacks or didn't expect it to ever be longer than NAMEDATALEN.
/*
 * Maximum length for identifiers (e.g. table names, column names,
 * function names).  Names actually are limited to one fewer byte than this,
 * because the length must include a trailing zero byte.
 *
 * Changing this requires an initdb.
 */
#define NAMEDATALEN 64

/*
 * Representation of a Name: effectively just a C string, but null-padded to
 * exactly NAMEDATALEN bytes.  The use of a struct is historical.
 */
typedef struct nameData
{
        char            data[NAMEDATALEN];
} NameData;
typedef NameData *Name;

@MironAtHome I'm going to need to check the whole data path to see which fix would be the best for this one.

@MironAtHome It appears that if the PG type Name is used, then it will always be truncated at NAMEDATALEN on input -
Datum
namein(PG_FUNCTION_ARGS)
{
        char       *s = PG_GETARG_CSTRING(0);
        Name            result;
        int                     len;

        len = strlen(s);

        /* Truncate oversize input */
        if (len >= NAMEDATALEN)
                len = pg_mbcliplen(s, len, NAMEDATALEN - 1);

        /* We use palloc0 here to ensure result is zero-padded */
        result = (Name) palloc0(NAMEDATALEN);
        memcpy(NameStr(*result), s, len);

        PG_RETURN_NAME(result);
}

This also means that there won't be any warning if it exceeds NAMEDATALEN :(

@MironAtHome I'm working on a fix. Hopefully, it will be done tomorrow.

@MironAtHome Unfortunately, this one can't be extended to 65535 due to naming constraints elsewhere. Basically, a label is a relation and relation names are constrained to NAMEDATALEN in length. There's that constant again.
I found this out when I tried creating labels with the new lengths. So, what I will need to do is create a constraint on label names to be less than (NAMEDATALEN - 2). This will allow us to catch names that are too long, because namein truncates then beyond that.

@MironAtHome See PR #1989 which addresses this.

@MironAtHome See PR #1989 which addresses this and is currently in review.

Great Thank you, John, I have approved and put optional suggestions for your considerations.


This is only a "go run" of authority

This is only a "go run" of authority simply，why a project for that?

an interpreter (go-eval) and an on-the-fly-compiler (go run) are 2 different things, with their own merits and use cases.
mainly, with an interpreter, you can fiddle with the current state of a program, adding new functions/types w/o recompiling+re-running from the top.

feel free to re-open if something isn't clear.


Nessus Connection Failed

We have an on-prem Nessus server.  I've added the credentials and hostname in the config file.  When I run vuln_whisperer.
InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecureRequestWarning)
[FAIL] Could not login to Nessus
[FAIL] Could not properly load your config!
Reason: [FAIL] Could not connect to nessus -- Please verify your settings in configs/frameworks_example.ini are correct and try again.
Reason: [FAIL] Could not login to Nessus
I am looking forward to taking this for a spin so any help would be appreciated.

My config file needed to be fully commented out for the other sections not in use.  I partially commented out the file originally.


[Bug] Owner property from TokenBalanceInfo is missing from GetTransactionAsync

Describe the bug
The GetTransactionAsync method returns an object of type TransactionMetaSlotInfo, and in the property Meta.PreTokenBalances, if we look at the class TokenBalanceInfo, it doesnt have the Owner property that the Solana API returns. I did some digging and I can see a PR was submitted to implement this property 2 years ago (https://github.com/bmresearch/Solnet/pull/406), but in the current versions, this property is just not there...
To Reproduce
Steps to reproduce the behavior:
Execute the GetTransactionAsync (or the syncronous version);
Check for the first item of the PostTokenBalances array;
You can see that it's missing
Screenshots
The decompiled version:

The latest version of solnet can be found under the net8 solana tags on nuget
https://www.nuget.org/packages/Solana.Rpc


[lapack-reference] fix cblas feature

closes #12911
depends #12895  for CI success

@Neumann-A Thanks for your PR. I installed lapack-reference[cblas] and got the following error:
Building package lapack-reference[blas-select,cblas,core,noblas]:x64-windows... done
Installing package lapack-reference[blas-select,cblas,core,noblas]:x64-windows...
The following files are already installed in E:/Lily/pr/vcpkg/installed/x64-windows and are in conflict with lapack-reference:x64-windows

Installed by openblas:x64-windows
    include/cblas.h

@LilyWangL: noblas and cblas are by design incompatible. Still if openblas is installed there will be a file conflict between those two ports if lapack-reference is built with feature cblas.

Yes, if noblas and cblas are by design incompatible, blas-select should not be default feature. If blas-select is default feature, when I install lapack-reference[cblas], it will install lapack-reference[blas-select,cblas,core,noblas]. lapack-reference[cblas] will build failed on Windows.

blas-select needs to be the default feature otherwise ci and users don't get what they expect. People who explicitly want cblas must deactivate the defaults by explicitly declaring [core,cblas]. Feature cblas only exists for corner cases and should be treated as such.

The feature is also up for removal as soon as a native windows fortran compiler is available

Could add message for feature cblas to declare that this feature does not support windows temporarily?

Could add message for feature cblas to declare that this feature does not support windows temporarily?

It should support windows if you install it without the feature noblas

I test lapack-reference[cblas]:x64-windows-static and it can install successfully.
Building package lapack-reference[blas-select,cblas,core]:x64-windows-static... done
Installing package lapack-reference[blas-select,cblas,core]:x64-windows-static...
Installing package lapack-reference[blas-select,cblas,core]:x64-windows-static... done
Elapsed time for package lapack-reference:x64-windows-static: 6.92 min

Total elapsed time: 10.11 min

Thanks for your contribution!


Develop Comms to CSV Receivers to determine their capability/need

Problem statement
There are several receivers currently on the CP that use the CSV download feature.
The UP does not have CSV download capability.
Therefore, we need to reach out to them to determine their capability and needs so we can develop a plan for how to accommodate them in the future.
What you need to know

Current CSV Download receivers are cities/counties:

ca-sbc-phd
ca-scc-phd
co-routt-county-phd
co-san-juan-basin-phd
fl-hillsborough-phd
oh-ccchd-doh
pa-chester-phd
pa-montgomery-phd
pa-philadelphia-phd
pima-az-phd

We likely need to determine:

if they still desire CSV download or if they are already getting their data elsewhere
if they can accept an ELR connection
do they want to remain connected to RS and why

Link to plan document
Acceptance criteria

[ ] Create comms to CSV receivers to identify their capability and needs for receiving data in the future

To do

[ ] ...

Doc complete and approved here


HDDS-4131. Container report should update container key count and bytes used if they differ in SCM

What changes were proposed in this pull request?
In HDDS-4037 it was noted that when blocks are deleted from closed containers, the bytesUsed and Key Count metrics on the SCM container are not updated correctly.
These stats should be updated via the container reports issued by the DNs to SCM periodically. However, in AbstractContainerReportHandler#updateContainerStats, the code assumes the values are always increasing and it will not update them if they are decreasing:
  private void updateContainerStats(final ContainerID containerId,
                                    final ContainerReplicaProto replicaProto)
      throws ContainerNotFoundException {
    if (isHealthy(replicaProto::getState)) {
      final ContainerInfo containerInfo = containerManager
          .getContainer(containerId);

      if (containerInfo.getSequenceId() <
          replicaProto.getBlockCommitSequenceId()) {
        containerInfo.updateSequenceId(
            replicaProto.getBlockCommitSequenceId());
      }
      if (containerInfo.getUsedBytes() < replicaProto.getUsed()) {
        containerInfo.setUsedBytes(replicaProto.getUsed());
      }
      if (containerInfo.getNumberOfKeys() < replicaProto.getKeyCount()) {
        containerInfo.setNumberOfKeys(replicaProto.getKeyCount());
      }
    }
  }

In HDDS-4037 a change was made to the Replication Manager, so it updates the stats. However I don't believe that is the correct place to perform this check, and the issue is caused by the logic shared above.
In this Jira, I have removed the changes to Replication Manager in HDDS-4037 (but retained the other changes in that Jira), ensuring the problem statistics are only updated via the containers reports if they are different in SCM from what is reported.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4131
How was this patch tested?
Small change to existing unit test. Used it to reproduce the problem before making the changed.

Hi @sodonnel, since a typical container has 3 replicas and container report are asynchronously, we need a consensus on what's the container size is in SCM. Basically AbstractContainerReportHandler is not the perfect place to handle this because it doesn't have a global view while Replication Manager has.
For OPEN container,  I think Math.min(replia1, replica2, replica3) is a safe way, and for CLOSED container, Math.max(replica1, replica2, replica3) is safer.

In HDDS-4037 a change was made to the Replication Manager, so it updates the stats. However I don't believe that is the correct place to perform this check, and the issue is caused by the logic shared above.

Agree, -- based on my understanding -- it's better to do before replication manager:

Replication manager can be more simple and easier to manage
If we do the fix in the replication manager it's possible to have an inconsistent view between the container report and replication manager execution.

@adoroszlai @ChenSammi Are you happy with this change at this stage? Can we commit it?

I think this change is good to commit now? @adoroszlai gave a thumbs up a few days back and I have addressed the only concern @ChenSammi raised.
I will commit tomorrow unless anyone objects before then.

+1.  Thanks @sodonnel for the contribution.


Add support for inline inputs

The example page for Twitter Bootstrap includes examples for multiple input fields inlined. We should explicitly support this.

I would suggest something like f.inputs :inline => true.

Possibly. All of the form helpers inside that block need to change how they output, which makes this a PITA to deal with. Then I have to figure out how best to display errors for multiple inputs in that one area...

I like the approach. Unfortunately, it's a non-trivial amount of work (basically, a new FormBuilder subclass) for something I don't currently use. So, you have two options: 1) wait for me to have time to do it, or 2) submit a patch. The latter would be very much welcomed. :) If you don't have time, I'll get to it but it may take me a bit.

Why does this need a new FormBuilder? It seems like you could just do:
f.inline_fields 'label' do
  f.text_field :start_time
  ...
end

All we're talking about is stylistic grouping, not new functionality.

The existing text_field method wraps everything in a
, creates a , another
 to go around the field, and finally the <input> itself.
The wrapped text_field method (and other input methods) would only emit the <input> tag itself. In order to accomplish this, the inline method would have to output the wrapper divs (
,
, and
, all nested) and yield a FormBuilder for the pared-down input methods.
Actually, thinking on it, it could just yield the normal FormBuilder, since the input methods don't need to do any extra magic.

That's what I was thinking. I may have some time tomorrow night to try a patch.

Sorry to punt on so much today. I've been swamped for the last two weeks, and haven't had the spare cycles to do much development on the side. Anything that's not a bug has to wait. :(

Ok, I'm trying to implement this, but not having much luck. Here's what I've got:

#
  # Creates bootstrap wrapping before yielding a plain old rails builder
  # to the supplied block.
  #
  def inline_inputs(label = nil)
    template.content_tag(:div, :class => 'clearfix') do
      template.concat template.content_tag(:label, label)
      template.concat template.content_tag(:div, :class => "input") {
        yield ActionView::Helpers::FormBuilder.new @object_name, @object, @template, @options, @proc if block_given?
      }
    end
  end

But the yielded object still seems to output the bootstrap divs, labels, etc. I'm pretty new to this. I'm going to keep trying, but if you see something I'm doing obviously wrong, let me know. The FormBuilder initialization must be wrong.

That looks reasonable to me. I'll have more time to look after work tonight.

Making a little progress. It actually works if I use the yielded object to render a text field directly. But if I use it like so:
= inline_inputs do |inline|
  = inline.fields_for :associated do |assoc|
    = assoc.text_field :name

then assoc is a TwitterBootstrapFormFor::FormBuilder. I thought it would be a regular FormBuilder as a result of spawning it from inline.fields_for... hmm...

Okay, looks like I just had to override the :builder option in the hash passed to the initializer. Pull Request #25 submitted.

Pull request merged. Release will go out in a day or two when I have time to do some thorough testing.

Cool - about that... Do you have a testing framework preference? I was going to add some specs (rspec), but didn't want to be presumptuous.

I was intending to use MiniTest. It's built into Ruby 1.9, is fast, and has an RSpec-like DSL syntax.

I've been tweaking this pull request, and came across an unfortunate limitation. If there are errors on inline fields, they won't show up (because we're using the default FormBuilder).
We might need to actually make a second FormBuilder later that doesn't emit the div wrappers, but handles the error messages.

I've released this in 1.0.4. I did, however, change the name of the method to inline rather than inline_inputs.

Yes. Those fields are rendered exactly as they would be outside of the t_b_f_f gem.

The change you made to the implementation causes problems when spawning child form builders inside the block passed. In my case, I do this when rendering fields for an object that the form accepts_nested_attributes_for My implementation didn't exhibit the same issues. I made a test repository to showcase this issue.
As you can see here, I make a call to fields_for inside the inline block. When those fields are rendered the field name is set improperly. The nesting is one level too deep. In my sample app, the comment text field is rendered with the name post[post][comments_attributes][0][text] which has an exta [post] in it. This means that data is silently discarded by the controller.
This doesn't happen with my older implementation that simply yielded a form builder back to the caller.

In fact, the reproduction of this issue can be simplified even further, eliminating the nested fields. The field names generated for ANY fields rendered with the inline builder are wrong. Check out my exmaple. Those fields are rendered with the names post[post][title] and post[post][body] when they should be post[title] and post[title] respectively.

Crap.
I chose that approach because it seemed less brittle than creating the builder myself. Will push a fix ASAP.

Yep, I'm going to be that guy.
!(Tests)[http://memegenerator.net/cache/instances/400x/11/11322/11594249.jpg]

https://github.com/stouset/twitter_bootstrap_form_for/issues/8 :(

(I was just kidding. I have definitely been guilty of the same.)

Hoping I get some time over the Thanksgiving break... been crazy busy, unfortunately.

dc6ac1fe97960499ea2c6a6d276ce756e97c2b95
This should fix the issue. I'll push a new release once I get confirmation from you guys. :)

Tested it with my test repo and verified this fixes the issue.

Released.

This doesn't work if ActionView::Base.default_form_builder is TwitterBootstrapFormFor::FormBuilder. The new form builder is another instance of t_b_f_f. I think that line 79 should be
self.options.merge(:builder => ActionView::Helpers::FormBuilder),

while line 76 remains the same.

Is anyone setting that? I hadn't considered that anyone ever would. :)

Definitely. That way I don't have to set it on every form_for if I want all of my forms to use Bootstrap.


AmazonChimeSDK.MediaErrorCode=1

I am getting above error on starting meeting. Tried to search for the issue but nothing found. The application is asking for permission of camera and microphone. After this I get this error.
Version of Amazon Chime SDK 0.8.2
Version of Amazon Chime Media SDK 0.6.1
Version of React Native 0.63.2

Thank you for reporting. Do you mind pasting full logs?

Thank you for reporting. Do you mind pasting full logs?

Okay will share the full logs.

Hey, just want to check if you got change to repro and share the log? Is the issue still ongoing?

Hey, just want to check if you got change to repro and share the log? Is the issue still ongoing?

Apology I forgot to update the issue. The reason we were getting error because we have not implemented videoTileSizeDidChangeWithTileState method in MeetingObservers.m
After adding it the issue is resolved.


Summary Links/Quick Links Transform Improvements

Category
[ ] Bug
[X] Enhancement
Expected or Desired Behavior
In the case where we transform Summary Links to Quick Links, the configuration of Quick Links e.g. Layout, Descriptions, alignments etc isn't configurable (from what I can see).
I would like to be able to specify or configure the following blocks (example JSON for Quick Links Web Part):

"properties": {
    "items": [
      {
        "sourceItem": {
          "itemType": 2,
          "fileExtension": "",
          "progId": ""
        },
        "thumbnailType": 3,
        "id": 2
      },
      {
        "sourceItem": {
          "itemType": 2,
          "fileExtension": "",
          "progId": ""
        },
        "thumbnailType": 3,
        "id": 1
      }
    ],
    **"isMigrated": true,
    "layoutId": "Button",
    "shouldShowThumbnail": true,
    "buttonLayoutOptions": {
      "showDescription": false,
      "buttonTreatment": 3,
      "iconPositionType": 2,
      "textAlignmentVertical": 1,
      "textAlignmentHorizontal": 2,
      "linesOfText": 2
    },
    "listLayoutOptions": {
      "showDescription": false,
      "showIcon": true
    },
    "waffleLayoutOptions": {
      "iconSize": 1,
      "onlyShowThumbnail": false
    },
    "hideWebPartWhenEmpty": true,**
    "dataProviderId": "QuickLinks",
    "webId": "7b178d79-89cf-4dbf-a67d-8de2e9920117",
    "siteId": "e9c7463c-7046-460d-82c7-2cd7fcf20810"
  }

between the RED bits (GitHub didn't like formatting example JSON). This would allow to control the presentation of the web part. Ideally, configured via the mapping file would be ideal.

@pkbullock : you could today update the webpartmapping file to change the defaults or use multiple web part mapping files. I could make it more configurable OOB but then I need to introduce additional mapping parameters...can maybe add 1 or 2 but adding all possible options will lead to too many parameters in my opinion.

@jansenbe I couldn't see how to map this, looking at this:
<Mapping Name="UseQuickLinks" Default="false" Functions="SummaryLinksToQuickLinksProperties({SummaryLinkStore})">
            <!-- Summary links html is tranformed to the quicklinks web part -->
            <ClientSideWebPart Type="QuickLinks" Order="10" JsonControlData="{"serverProcessedContent":{"htmlStrings":{},"searchablePlainTexts":{"title":"{Title}"{SearchablePlainTexts}},"imageSources":{{ImageSources}},"links":{"baseUrl":"{EncodedWeb}"{Links}},"componentDependencies":{"layoutComponentId":"706e33c8-af37-4e7b-9d22-6e5694d92a6f"}},"dataVersion":"2.1","properties":{JsonProperties}}"/>
          </Mapping>

in the section: properties":{JsonProperties} (decoded: "properties":{JsonProperties})
The token replacement replaces the inserts properties block including the braces, which is set by the SummaryLinksToQuickLinksProperties function - which led me to believe this isn't mappable.
We could specify in one parameter the JSON block to include e.g. AdditonalJsonProperties - specifically in the Web Part Mapping file.
What you think?

Right...this web part uses another flow due to it's complexity.
What are the key settings you're looking into?

Possible solution:

add JSON properties web part property to webpartmapping for SummaryLinks wp
provide that property into SummaryLinksToQuickLinksProperties function
when provided to SummaryLinksToQuickLinksProperties, use the set properties else use the current defaults
Add property to webpart mappings in the page layout mapping files, use the staticString function to provide a JSON (encoded) blob with the needed settings

Right...this web part uses another flow due to it's complexity.
What are the key settings you're looking into?

In this case the settings maybe dynamic depending on what layout option you choose, so this wouldn't be flexible.

Possible solution

That makes sense, would be highly flexible. I have used (for reference for others) the ?MaintenanceMode=True during transform testing to grab the relevant section of the properties to include. We wouldn't need to change the code (in theory) if new layout options are added to the web part in the future.

@pkbullock : I've implemented this. See below snippet of how to provide custom QuickLinks properties. Currently only works for publishing page transformation, also note that you only need to specify the JSON elements that you want to override.
Important: You need to take the latest webpartmapping.xml file to make this work or update yours accordingly.
<WebParts>
        <Field Name="SummaryLinks" TargetWebPart="Microsoft.SharePoint.Publishing.WebControls.SummaryLinkWebPart, Microsoft.SharePoint.Publishing, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Row="1" Column="2">
          <!-- No function specified, means the content of the PublishingPageContent field will be assigned to the value of the first listed web part property -->
          <Property Name="SummaryLinkStore" Type="string" />
          <Property Name="Title" Type="string" Functions="EmptyString()"/>
          <Property Name="QuickLinksJsonProperties" Type="string" Functions="StaticString('{"isMigrated": false, "layoutId": "Button", "shouldShowThumbnail": true, "buttonLayoutOptions": { "showDescription": false, "buttonTreatment": 1, "iconPositionType": 2, "textAlignmentVertical": 1, "textAlignmentHorizontal": 2, "linesOfText": 2}, "listLayoutOptions": { "showDescription": false, "showIcon": true}, "waffleLayoutOptions": { "iconSize": 1, "onlyShowThumbnail": false}, "hideWebPartWhenEmpty": true}')" />
        </Field>
        <Field Name="PublishingPageContent" TargetWebPart="SharePointPnP.Modernization.WikiTextPart" Row="1" Column="1">
          <!-- No function specified, means the content of the PublishingPageContent field will be assigned to the value of the first listed web part property -->
          <Property Name="Text" Type="string" Functions="" />
        </Field>
      </WebParts>

@jansenbe Awesomeness!!


Chrome on iPad Horizontal

Text sizing or CSS selections are off. Text in the homepage boxes is too big.

Fixed


send_email doesn't trim recipient's email address

The send_email function simply split email address list by comma, and this leads to email address like "<EMAIL_ADDRESS>(a space before the address).
The problem line is here
Suggest fix is:
for r in recipients:
    recipients_tmp.extend(r.split(',').strip())

Can you send a pull request? Thanks

Sure

great :)

@erikbern Ready for review.


Update README.md with self hosted bors link

Using our self hosted bors since the GitHub one is deprecated

bors try

Thanks @curquiza!

bors merge


Raw video from crunchyroll

Just tried to download a crunchyroll video. It works just fine, but I got the "Hard Subbed" video with English Subtitles. Is there any way to get the Raw video instead? and maybe an option to select subtitle language as well?
My current Command Line :
livestreamer --crunchyroll-username=xxx --crunchyroll-password=xxx http://www.crunchyroll.com/i-cant-understand-what-my-husband-is-saying/episode-13-happy-days-678059 high -o High.mp4
This works just fine. But, as mentioned above, can I just get the raw video and all the subtitles separately?

Found older threads regarding this.
Here.


deployer split to multiple files

Fixed https://github.com/eclipse-xpanse/xpanse/issues/2195
Based on https://github.com/eclipse-xpanse/xpanse/pull/2244

LGTM

LGTM

LGTM

LGTM

LGTM

LGTM

LGTM

LGTM

LGTM


Bug with Open XML SDK: It doesn't recognize SlideMaster part after v2.9.0

Describe the bug
A clear and concise description of what the bug is.
Customer is using OpenXML SDK read PPTX file, they found the GetPartById() method didn't return SlideMaster type for a special file.
They did more investigation then found SDK didn't recognize SlideMaster correctly if there is slideLayout1.xml in the “\ppt_rels\presentation.xml.rels" file.
We understand slideLayout1.xml should not appear here, but the SDK can recognize it correctly before v2.9.0
As XML is very open structure, so it seems like we should still read the SlideMaster type as v2.8.
Screenshots

To Reproduce
// Please add a self-contained, minimum viable repro of the issue.
// If you require external resources, please provide a gist or GitHub repro
// An Xunit style test is preferred, but a console application would work too.
Steps to reproduce the behavior:

Use the repro file, it's private, so could not share in the issue, will contact to issue owner directly later.

Use following code read the file.
`
string presentationFile = "C:\temp\repro.pptx";
 // Open the presentation as read-only.
 using (PresentationDocument presentationDocument = PresentationDocument.Open(presentationFile, false))
 {
     var tempPart = presentationDocument.PresentationPart.GetPartById("rId2");
     Console.WriteLine(tempPart.GetType());
 }

`
Observed behavior
The code returns "ExtendedPart" type.
Expected behavior
It should returns "SlideMasterPart"
Desktop (please complete the following information):

OS: Windows
Office version 16.0.15726.20202
.NET Target: (.NET Core)
DocumentFormat.OpenXml Version: (e.g. 2.18.0)

Additional context
Add any other context about the problem here.

HI @FullStackEngN
Thank you for reporting this issue. We will triage this issue shortly. It might be related to [(https://github.com/OfficeDev/Open-XML-SDK/issues/1225)] that was reported few months back.

@FullStackEngN, it would be good if could share your presentation file with a minimum structure for repro.
I've checked on new empty presentation and it works:
using var pres = PresentationDocument.Open("some.pptx", false);
var part = pres.PresentationPart!.GetPartById("rId1");

Console.WriteLine(part.GetType().Name);

Output:
SlideMasterPart

File:

.NET Target: .NET 6
DocumentFormat.OpenXml Version: 2.18.0

Hi @FullStackEngN,
Two questions - do we know which version of Open XML SDK was used to create the PPTX in question?
Could you also try creating PPTX with the latest Open XML SDK https://github.com/OfficeDev/Open-XML-SDK/pull/1234 to see if the issue is resolved?
Hung-Chun Yu
Microsoft Open Specifications Support

@hunyu , we and customer don't know how the PPTX file was created.
The scenario is customer developed an application which allow their users choose PPTX file and their application will try to parse the PPTX file, Customer's application worked well on OpenXML SDK v2.7.2. When they upgrade the SDK to v2.18, then users started reported issue the application doesn't work, they did investigate and found the PPTX file provided by their users are not well format, The root cause is the SliderMaster was not correctly recognized. So, they submitted the issue and would like a fix in the SDK that bypass the not-well formatted PPTX file.
I will ask customer to test the issue #1234 and share feedback, Thanks.

@hunyu @adamshakhabov Customer tested the latest code but still encountered issue.
Customer mentioned a possible fix, could you give your advice?
If adding the new "relationship.RelationshipType" check equal slideLayout or not, then the SDK can recognize their end users' PPTX file successfully?
`
internal void LoadReferencedPartsAndRelationships(OpenXmlPackage openXmlPackage, OpenXmlPart? sourcePart, RelationshipCollection relationshipCollection, Dictionary<Uri, OpenXmlPart> loadedParts)
{
foreach (var relationship in relationshipCollection)
{
// Fix bug https://github.com/OfficeDev/Open-XML-SDK/issues/1205
if (relationship.RelationshipType == @"http://schemas.microsoft.com/office/2006/relationships/recovered")
{
continue;
}
           **if (sourcePart is PresentationPart
                && relationship.RelationshipType == @"http://schemas.openxmlformats.org/officeDocument/2006/relationships/slideLayout")
            {
                continue;
            }**

`

That will be awesome. Thank youSent from my iPhoneOn Nov 20, 2022, at 11:56 PM, FullStackEngN @.***> wrote:
@hunyu @adamshakhabov Customer tested the latest code but still encountered issue.
Customer mentioned a possible fix, could you give your advice?
If adding the new "relationship.RelationshipType" check equal slideLayout or not, then the SDK can recognize their end users' PPTX file successfully?
`
internal void LoadReferencedPartsAndRelationships(OpenXmlPackage openXmlPackage, OpenXmlPart? sourcePart, RelationshipCollection relationshipCollection, Dictionary<Uri, OpenXmlPart> loadedParts)
{
foreach (var relationship in relationshipCollection)
{
// Fix bug #1205
if (relationship.RelationshipType == @"http://schemas.microsoft.com/office/2006/relationships/recovered")
{
continue;
}
if (sourcePart is PresentationPart
&& relationship.RelationshipType == @"http://schemas.openxmlformats.org/officeDocument/2006/relationships/slideLayout")
{
continue;
}
`
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

@hunyu @adamshakhabov Customer tested the latest code but still encountered issue.
Customer mentioned a possible fix, could you give your advice? If adding the new "relationship.RelationshipType" check equal slideLayout or not, then the SDK can recognize their end users' PPTX file successfully?
` internal void LoadReferencedPartsAndRelationships(OpenXmlPackage openXmlPackage, OpenXmlPart? sourcePart, RelationshipCollection relationshipCollection, Dictionary<Uri, OpenXmlPart> loadedParts) { foreach (var relationship in relationshipCollection) { // Fix bug #1205 if (relationship.RelationshipType == @"http://schemas.microsoft.com/office/2006/relationships/recovered") { continue; }
           **if (sourcePart is PresentationPart
                && relationship.RelationshipType == @"http://schemas.openxmlformats.org/officeDocument/2006/relationships/slideLayout")
            {
                continue;
            }**

`

@hunyu Thanks, customer did test locally and confirmed the new "relationship.RelationshipType" check works for them, so they would like OpenXML team consider it and may add it to next release then they can upgrade to next version SDK.

@hunyu May I have an update for this issue? Will customer have the fix in next OpenXML SDK version? Thanks.

@FullStackEngN
Next OpenXML SDK version will not have this fix. Our team won't be able to work on it until after next OpenXML SDK is released.


Send dialog remembers values

Since the send-form dialog was refactored it somehow and only sometimes remebers addresses which you put in, e.g.:

Not only was this probably not intended but it also doesn't work since you cannot click "Next" even though the address is already there and if you can click next it gives an exception :P
I tried to fix it, but didn't find a good solution yet.
I think it has something to do with the fact, that the $scope of the dialog is not "dismissed" anymore when it's closed? Maybe a solution would be to ensure the $scope is "cleaned" when the dialog is opened (or by simply opening a new (sub)$scope?
@j-a-m-l do you know what to do?

uhmm, that may work.


Use global sinon if it's available

In some use case sinon is loaded globally (I know this is a bad way of doing thing) and sinon as promised is not returning the right sinon instance.

Sorry, specifically remove the ability to do this a while back. There used to be a separate build that looked on the window. You can run exposify as a global transform to do this in your projects but I'm not up for adding an if statement.


Event subtitle field

Issue found in ecb937b164921f2fcdd623879642b412c8db704d
All the events also have a subtitle field. Would it be possible to add that to the editor so that it is easy to edit? Can its style also be modified to a heading of 4 (e.g. ####Vectors)?

Subtitle now displayed. Edit through metadata, like title.


[Support] How to get started with performance monitoring?

Versions used
sentry/sentry-laravel: 2.4.2
laravel/framework: 8.38.0

Hi,
I added 'traces_sample_rate' => 1.0 to my config/sentry.php file. Deployed my app, then made some API requests.
Later when I check the Performance tab on Sentry dashboard I don't see anything.
Do I need to make some extra configuration to enable this? Or it's only enabled for errors/exceptions? (Though I tried also that)

If you only have traces_sample_rate set to 1.0 and no traces_sampler it should work.
There are some things to check possibly:

If your plan has performance quota left if you are on sentry.io
If you checked to fast, performance takes a second to find it's way to the interface
If you are using frontend browser tracing too and the sentry-trace is sent to the backend (if that is the case the frontend decides if the backend should be traced)

Ok, I found the problem.
I disabled the auto-discovery for the package. And I'm registering it depending on the environment. But didn't know performance monitoring has a separate service provider. Now I also register the tracing provider, and it works :+1:
Sorry for the trouble.

Ah. Yeah, no worries I forgot about that too, glad it's working! 👍


grype: 0.63.1 -> 0.64.0

Diff: https://github.com/anchore/grype/compare/refs/tags/v0.63.1...v0.64.0
Changelog: https://github.com/anchore/grype/releases/tag/v0.64.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 243396 run on x86_64-linux 1

1 package built:

grype


bug: "Neovim: turn on/off" command no longer exists

Did you check docs and existing issues?

[X] I have read all the vscode-neovim docs
[X] I have searched the existing issues of vscode-neovim
[X] I can reproduce the issue with an empty init.vim/init.lua and no other vscode extensions (when applicable)

Neovim version (nvim -v)
0.9.4
Operating system/version
MacOS 14.1.1
Describe the bug
Command as described in #794 no longer exists.
Trying to call the command directly leads to: command 'vscode-neovim.toggle' not found
I found this stopped working ~4 weeks ago
Steps To Reproduce
cmd+p

Neovim:

does not show the command.
Expected Behavior
Command should appear

use restart and stop

why is there no toggle command? restart/stop means having to create two hotkeys instead of just one.

means having to create two hotkeys instead of just one.

No. See https://github.com/vscode-neovim/vscode-neovim/pull/1566#issuecomment-1852056253