Multiple Pipelines problem with docker image

Just starting to use the LS 6.0 docker images for the first time and ran into some problems.  I followed the instructions on the wiki page, notably:
FROM docker.elastic.co/logstash/logstash:6.0.0-rc2
RUN rm -f /usr/share/logstash/pipeline/logstash.conf
ADD pipeline/ /usr/share/logstash/pipeline/
ADD config/ /usr/share/logstash/config/

And received this error:
ERROR: Pipelines YAML file is empty. Location: /usr/share/logstash/config/pipelines.yml
usage:
  bin/logstash -f CONFIG_PATH [-t] [-r] [] [-w COUNT] [-l LOG]
  bin/logstash --modules MODULE_NAME [-M "MODULE_NAME.var.PLUGIN_TYPE.PLUGIN_NAME.VARIABLE_NAME=VALUE"] [-t] [-w COUNT] [-l LOG]
  bin/logstash -e CONFIG_STR [-t] [--log.level fatal|error|warn|info|debug|trace] [-w COUNT] [-l LOG]
  bin/logstash -i SHELL [--log.level fatal|error|warn|info|debug|trace]
  bin/logstash -V [--log.level fatal|error|warn|info|debug|trace]
  bin/logstash --help

It's even more confusing because the docs page (https://www.elastic.co/guide/en/logstash/6.0/docker.html) doesn't mention pipelines.yml the way it mentions logstash.yml and the linked docs page (https://www.elastic.co/guide/en/logstash/6.0/config-setting-files.html) doesn't mention pipelines.yml.  I've opened a separate docs ticket for that second link on the logstash repo.
I think maybe either the docker docs page should mention that you need to supply both a logstash.yml as well as pipelines.yml AND your pipeline conf files, or maybe we default the docker image to the old behavior of ignoring pipelines.yml and just loading all the pipelines defined in pipelines/ i'm not sure which way is better, I don't really have a strong opinion.

Is the line:
ADD config/ /usr/share/logstash/config/

replacing logstash.yml?
If so, does the new logstash.yml contain:
path.config: /usr/share/logstash/pipeline

?

Yes it is replacing logstash.yml (the only line in that file is to disable monitoring).
Not it doesn't contain that path.config line.

Thanks, that helps. It's tricky when replacing the "default" file that we provide. The user ends up masking settings that we put there on purpose to make things work smoothly.
I've added an explicit callout for this in the Kibana docs, but I think we should call it out for all products.

Of course, using the environment for configuration avoids this problem. Your new settings then overwrite only the ones you specify, instead the ones you don't specifically, as is the case with logstash.yml.

Did you mean to say you added a callout in the logstash docs?
It might just be as simple as saying in the logstash docker docs "If you replace config/logstash.yml you either need to ensure that path.config: /usr/share/logstash/pipeline is set or you need to create a config/pipelines.yml file exists"
Or something like that

The same principle applies to all products. So far, I've documented it for Kibana. I'm working on the Logstash docs right now, so I'll add in the warning there too. 👍

Is it worth pointing out in the docs what the default logstash.yml in the docker image looks like so people can easily see how to recreate it if they overwrite it?
I guess what I mean is, I don't know if a generic "be careful if you overwrite the config files" warning is enough to help people easily triage the problem I hit since they'd have to go look at the code in github to see what the default is in the first place if they're following our example in the docs.
I'll close this issue now.  Thanks!

Absolutely! People need to know what the defaults are if they are going to preserve them.
Thanks for the report. It's great to get these kinds of things from people who really trying stuff out.

WOUld it help if you could specify a second file to provide overrides? IMO
environment variables can be easily user-hostile. Maybe we make logstash
able to accept multiple logstash.yml files and one overrides settings of
the others?
On Wed, Nov 1, 2017 at 9:31 PM Toby McLaughlin<EMAIL_ADDRESS>wrote:

Absolutely! People need to know what the defaults are if they are going to
preserve them.
Thanks for the report. It's great to get these kinds of things from people
who really trying stuff out.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/elastic/logstash-docker/issues/58#issuecomment-341315046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIC6qQB1veZSDkDHaM3kmI-jAnucrp2ks5syUWegaJpZM4QOPSp
.

I could see that working, for sure. You can't ignore ENV in container-land though. It's just "the way it's done", for better, or for worse.

I don't know if we want to stray too far from the rest of the stack. It would be weird if logstash had multiple yml with overrides but es, kibana, and beats did not.
Honestly I think this was primarily a documentation problem with us not showing that they had to set the path config or create a pipelines.yml if not.

It's certainly possible that they might want multiple pipelines so just documenting the examples and giving them the option when they do their immutable config is the best way forward I think.

For sure. Strict option parsing is the change that causes the breakage. I look like it was introduced in Kibana 6:
https://github.com/elastic/kibana/pull/12554
We'll have to do a workaround of some kind.

@jarpy , and @ctindel , I get the same error, I don't know any fix for this. Do you guys know how I need to setup my Dockerfile?
Dockerfile content:
FROM docker.elastic.co/logstash/logstash:7.0.1
RUN rm -f /usr/share/logstash/pipeline/logstash.conf
ADD pipeline/ /usr/share/logstash/pipeline
ADD config/ /usr/share/logstash/config

It's likely that this is the only comment you need: https://github.com/elastic/logstash-docker/issues/58#issuecomment-341301766
You are replacing logstash.conf so the error is probably in that file. You haven't shared it here, so it's hard to say. Try adding:
path.config: /usr/share/logstash/pipeline

to it.

@koursoh If you are reading by email, please see my edited response above on GitHub. I messed up my initial response, sorry.

@jarpy , thanks for your reply. I was using github itself, so it is all good :)
I assume by replacing logstash.yml, you mean replacing it inside the image I created right, not the base one from docker.elastic.co/logstash/logstash?
The content of my logstash.yml inside my image:
# Settings file in YAML
#
# Settings can be specified either in hierarchical form, e.g.:
#
#   pipeline:
#     batch:
#       size: 125
#       delay: 5
#
# Or as flat keys:
#
#   pipeline.batch.size: 125
#   pipeline.batch.delay: 5
#
# ------------  Node identity ------------
#
# Use a descriptive name for the node:
#
# node.name: test
#
# If omitted the node name will default to the machine's host name
#
# ------------ Data path ------------------
#
# Which directory should be used by logstash and its plugins
# for any persistent needs. Defaults to LOGSTASH_HOME/data
#
# path.data:
#
# ------------ Pipeline Settings --------------
#
# The ID of the pipeline.
#
# pipeline.id: main
#
# Set the number of workers that will, in parallel, execute the filters+outputs
# stage of the pipeline.
#
# This defaults to the number of the host's CPU cores.
#
# pipeline.workers: 2
#
# How many events to retrieve from inputs before sending to filters+workers
#
# pipeline.batch.size: 125
#
# How long to wait in milliseconds while polling for the next event
# before dispatching an undersized batch to filters+outputs
#
# pipeline.batch.delay: 50
#
# Force Logstash to exit during shutdown even if there are still inflight
# events in memory. By default, logstash will refuse to quit until all
# received events have been pushed to the outputs.
#
# WARNING: enabling this can lead to data loss during shutdown
#
# pipeline.unsafe_shutdown: false
#
# ------------ Pipeline Configuration Settings --------------
#
# Where to fetch the pipeline configuration for the main pipeline
#
# path.config:
#
# Pipeline configuration string for the main pipeline
#
# config.string:
#
# At startup, test if the configuration is valid and exit (dry run)
#
# config.test_and_exit: false
#
# Periodically check if the configuration has changed and reload the pipeline
# This can also be triggered manually through the SIGHUP signal
#
# config.reload.automatic: false
#
# How often to check if the pipeline configuration has changed (in seconds)
#
# config.reload.interval: 3s
#
# Show fully compiled configuration as debug log message
# NOTE: --log.level must be 'debug'
#
# config.debug: false
#
# When enabled, process escaped characters such as \n and \" in strings in the
# pipeline configuration files.
#
# config.support_escapes: false
#
# ------------ Module Settings ---------------
# Define modules here.  Modules definitions must be defined as an array.
# The simple way to see this is to prepend each `name` with a `-`, and keep
# all associated variables under the `name` they are associated with, and
# above the next, like this:
#
# modules:
#   - name: MODULE_NAME
#     var.PLUGINTYPE1.PLUGINNAME1.KEY1: VALUE
#     var.PLUGINTYPE1.PLUGINNAME1.KEY2: VALUE
#     var.PLUGINTYPE2.PLUGINNAME1.KEY1: VALUE
#     var.PLUGINTYPE3.PLUGINNAME3.KEY1: VALUE
#
# Module variable names must be in the format of
#
# var.PLUGIN_TYPE.PLUGIN_NAME.KEY
#
# modules:
#
# ------------ Cloud Settings ---------------
# Define Elastic Cloud settings here.
# Format of cloud.id is a base64 value e.g. dXMtZWFzdC0xLmF3cy5mb3VuZC5pbyRub3RhcmVhbCRpZGVudGlmaWVy
# and it may have an label prefix e.g. staging:dXMtZ...
# This will overwrite 'var.elasticsearch.hosts' and 'var.kibana.host'
# cloud.id: <identifier>
#
# Format of cloud.auth is: <user>:<pass>
# This is optional
# If supplied this will overwrite 'var.elasticsearch.username' and 'var.elasticsearch.password'
# If supplied this will overwrite 'var.kibana.username' and 'var.kibana.password'
# cloud.auth: elastic:<password>
#
# ------------ Queuing Settings --------------
#
# Internal queuing model, "memory" for legacy in-memory based queuing and
# "persisted" for disk-based acked queueing. Defaults is memory
#
# queue.type: memory
#
# If using queue.type: persisted, the directory path where the data files will be stored.
# Default is path.data/queue
#
# path.queue:
#
# If using queue.type: persisted, the page data files size. The queue data consists of
# append-only data files separated into pages. Default is 64mb
#
# queue.page_capacity: 64mb
#
# If using queue.type: persisted, the maximum number of unread events in the queue.
# Default is 0 (unlimited)
#
# queue.max_events: 0
#
# If using queue.type: persisted, the total capacity of the queue in number of bytes.
# If you would like more unacked events to be buffered in Logstash, you can increase the
# capacity using this setting. Please make sure your disk drive has capacity greater than
# the size specified here. If both max_bytes and max_events are specified, Logstash will pick
# whichever criteria is reached first
# Default is 1024mb or 1gb
#
# queue.max_bytes: 1024mb
#
# If using queue.type: persisted, the maximum number of acked events before forcing a checkpoint
# Default is 1024, 0 for unlimited
#
# queue.checkpoint.acks: 1024
#
# If using queue.type: persisted, the maximum number of written events before forcing a checkpoint
# Default is 1024, 0 for unlimited
#
# queue.checkpoint.writes: 1024
#
# If using queue.type: persisted, the interval in milliseconds when a checkpoint is forced on the head page
# Default is 1000, 0 for no periodic checkpoint.
#
# queue.checkpoint.interval: 1000
#
# ------------ Dead-Letter Queue Settings --------------
# Flag to turn on dead-letter queue.
#
# dead_letter_queue.enable: false

# If using dead_letter_queue.enable: true, the maximum size of each dead letter queue. Entries
# will be dropped if they would increase the size of the dead letter queue beyond this setting.
# Default is 1024mb
# dead_letter_queue.max_bytes: 1024mb

# If using dead_letter_queue.enable: true, the directory path where the data files will be stored.
# Default is path.data/dead_letter_queue
#
# path.dead_letter_queue:
#
# ------------ Metrics Settings --------------
#
# Bind address for the metrics REST endpoint
#
# http.host: "<IP_ADDRESS>"
#
# Bind port for the metrics REST endpoint, this option also accept a range
# (9600-9700) and logstash will pick up the first available ports.
#
# http.port: 9600-9700
#
# ------------ Debugging Settings --------------
#
# Options for log.level:
#   * fatal
#   * error
#   * warn
#   * info (default)
#   * debug
#   * trace
#
# log.level: info
# path.logs:
#
# ------------ Other Settings --------------
#
# Where to find custom plugins
# path.plugins: []
#
# ------------ X-Pack Settings (not applicable for OSS build)--------------
#
# X-Pack Monitoring
# https://www.elastic.co/guide/en/logstash/current/monitoring-logstash.html
#xpack.monitoring.enabled: false
#xpack.monitoring.elasticsearch.username: logstash_system
#xpack.monitoring.elasticsearch.password: password
#xpack.monitoring.elasticsearch.hosts: ["https://es1:9200", "https://es2:9200"]
#xpack.monitoring.elasticsearch.ssl.certificate_authority: [ "/path/to/ca.crt" ]
#xpack.monitoring.elasticsearch.ssl.truststore.path: path/to/file
#xpack.monitoring.elasticsearch.ssl.truststore.password: password
#xpack.monitoring.elasticsearch.ssl.keystore.path: /path/to/file
#xpack.monitoring.elasticsearch.ssl.keystore.password: password
#xpack.monitoring.elasticsearch.ssl.verification_mode: certificate
#xpack.monitoring.elasticsearch.sniffing: false
#xpack.monitoring.collection.interval: 10s
#xpack.monitoring.collection.pipeline.details.enabled: true
#
# X-Pack Management
# https://www.elastic.co/guide/en/logstash/current/logstash-centralized-pipeline-management.html
#xpack.management.enabled: false
#xpack.management.pipeline.id: ["main", "apache_logs"]
#xpack.management.elasticsearch.username: logstash_admin_user
#xpack.management.elasticsearch.password: password
#xpack.management.elasticsearch.hosts: ["https://es1:9200", "https://es2:9200"]
#xpack.management.elasticsearch.ssl.certificate_authority: [ "/path/to/ca.crt" ]
#xpack.management.elasticsearch.ssl.truststore.path: /path/to/file
#xpack.management.elasticsearch.ssl.truststore.password: password
#xpack.management.elasticsearch.ssl.keystore.path: /path/to/file
#xpack.management.elasticsearch.ssl.keystore.password: password
#xpack.management.elasticsearch.ssl.verification_mode: certificate
#xpack.management.elasticsearch.sniffing: false
#xpack.management.logstash.poll_interval: 5s

@jarpy , I realized I have to remove and copy it back in.  Am I doing the right thing?

I need to see pipelines.yml and logstash.yml. The third line of that Dockerfile also tries to delete pipeline.yml (singular) but it doesn't exist. The error is suppressed by -f so it's hard to notice.

I fixed the issue, the problem was pipelines.yml wasn't being overriden; it was empty. Also, had to install cloudwatch_logs for usr/share/logstash as well since I need to transport cloudwatch logs to logstash and elasticsearch.
Fix:
Dockerfile:
FROM docker.elastic.co/logstash/logstash:7.0.1
RUN rm -f /usr/share/logstash/pipeline/logstash.conf
RUN rm -f /usr/share/logstash/config/pipeline.yml
RUN /usr/share/logstash/bin/logstash-plugin install logstash-filter-json && \
 /usr/share/logstash/bin/logstash-plugin install logstash-input-cloudwatch_logs
ADD pipeline/ /usr/share/logstash/pipeline
ADD config/ /usr/share/logstash/config

pipelines.yml:
The only thing that I changed was this.
- pipeline.id: pipeline1
  pipeline.workers: 1
  queue.type: persisted
  path.config: "/usr/share/logstash/pipeline/*.conf"

logstash.conf:
input{
  cloudwatch_logs {
    access_key_id => "..."
    secret_access_key => "...."
    log_group => ["/aws/lambda/elk_logs"]
    region => "...."
  }
}

output{
  elasticsearch{
    hosts => ["***.found.io:9243"]
    user => "...."
    password => "...."
    index => "cloudwatch"
  }
  stdout {
    codec => rubydebug
  }
}


helm: fix annotations on DaemonSets

:tada: This PR is included in version 3.7.0-beta.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


realMouseMove() uses hardcoded position "topLeft"

I think the cy.realMouseMove() command has a hardcoded position as seen below.
https://github.com/dmtrKovalenko/cypress-real-events/blob/2282480708dbf42f5899ffba1288e1c6364d0ea2/src/commands/mouseMove.ts#L29-L33
I tried to use it with position: center as in the code example below but the event happened in the same hardcoded topLeft position.
https://github.com/dmtrKovalenko/cypress-real-events/blob/e9ca39f3fe1b1e03d57728aa8b1140d98df65739/README.md?plain=1#L314
I made Cypress test cases for all Cypress positions listed here:
https://github.com/dmtrKovalenko/cypress-real-events/blob/e9ca39f3fe1b1e03d57728aa8b1140d98df65739/src/getCypressElementCoordinates.ts#L1-L10
Here is the pattern for my Cypress tests.:
cy.get("body")
  .realMouseDown()
  .realMouseMove(20, 10, { position: "topLeft" })
  .realMouseMove(30, 20, { position: "topLeft" })
  .realMouseUp();
cy.get("body")
  .realMouseDown()
  .realMouseMove(20, 10, { position: "top" })
  .realMouseMove(30, 20, { position: "top" })
  .realMouseUp();
cy.get("body")
  .realMouseDown()
  .realMouseMove(-20, 10, { position: "topRight" })
  .realMouseMove(-30, 20, { position: "topRight" })
  .realMouseUp();

Outcomes

Ideal
Current

Currently, the marks are all overlapping. Ideally, they should all be in different positions according to the options given to cy.realMouseMove()

any news on this one?

That's a bug 😱 wow need to fix it.

:tada: This issue has been resolved in version 1.7.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


bug: appium server is showing 500 error when calling to get_screenshot_as_base64 while running Windows app test

Do I have the most recent component updates?

[X] I use the most recent available driver/plugin and server versions

Is the component officially supported by the Appium team?

[X] I have verified the component repository is present under the Appium organization in GitHub

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
While running windows app appium test, once I am calling to driver.get_screenshot_as_base64() I am getting the following error in appium server log:
[debug] [WindowsDriver@b02c (94a11461)] Calling AppiumDriver.getScreenshot() with args: ["94a11461-2ced-4895-b689-7cd4e44c6446"]
[debug] [WindowsDriver@b02c (94a11461)] Matched '/screenshot' to command name 'getScreenshot'
[debug] [WindowsDriver@b02c (94a11461)] Proxying [GET /screenshot] to [GET http://<IP_ADDRESS>:4724/wd/hub/session/B70CACF5-8A7E-4E2C-91BD-55B62AD131F1/screenshot] with no body
[debug] [WindowsDriver@b02c (94a11461)] ഀ਀ഀ਀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀㴀ഀ਀䜀䔀吀 ⼀眀搀⼀栀甀戀⼀猀攀猀猀椀漀渀⼀䈀㜀　䌀䄀䌀䘀㔀ⴀ㠀䄀㜀䔀ⴀ㐀䔀㈀䌀ⴀ㤀㄀䈀䐀ⴀ㔀㔀䈀㘀㈀䄀䐀㄀㌀㄀䘀㄀⼀猀挀爀攀攀渀猀栀漀琀 䠀吀吀倀⼀㄀⸀㄀ഀഀ਀䄀挀挀攀瀀琀㨀 愀瀀瀀氀椀挀愀琀椀漀渀⼀樀猀漀渀Ⰰ ⨀⼀⨀ഀഀ਀䄀挀挀攀瀀琀ⴀ䔀渀挀漀搀椀渀最㨀 最稀椀瀀Ⰰ 挀漀洀瀀爀攀猀猀Ⰰ 搀攀昀氀愀琀攀Ⰰ 戀爀ഀഀ਀䌀漀渀渀攀挀琀椀漀渀㨀 欀攀攀瀀ⴀ愀氀椀瘀攀ഀഀ਀䌀漀渀琀攀渀琀ⴀ吀礀瀀攀㨀 愀瀀瀀氀椀挀愀琀椀漀渀⼀樀猀漀渀㬀 挀栀愀爀猀攀琀㴀甀琀昀ⴀ㠀ഀഀ਀䠀漀猀琀㨀 ㄀㈀㜀⸀　⸀　⸀㄀㨀㐀㜀㈀㐀ഀഀ਀唀猀攀爀ⴀ䄀最攀 渀琀㨀 愀瀀瀀椀甀洀ഀഀ਀ഀഀ਀ഀ਀
[debug] [WindowsDriver@b02c (94a11461)] 䠀吀吀倀⼀㄀⸀㄀ 㔀　　 䤀渀琀攀爀渀愀氀 䔀爀爀漀爀ഀഀ਀䌀漀渀琀攀渀琀ⴀ䰀攀渀最琀栀㨀 ㄀㌀㌀ഀഀ਀䌀漀渀琀攀渀琀ⴀ吀礀瀀攀㨀 愀瀀瀀氀椀挀愀琀椀漀渀⼀樀猀漀渀ഀഀ਀ഀഀ਀笀∀猀琀愀琀甀猀∀㨀㄀㌀Ⰰ∀瘀愀氀甀攀∀㨀笀∀攀爀爀漀爀∀㨀∀甀渀欀渀漀眀渀 攀爀爀漀爀∀Ⰰ∀洀攀猀猀愀最攀∀㨀∀䄀渀 甀渀欀渀漀眀渀 攀爀爀漀爀 漀挀挀甀爀爀攀搀 椀渀 琀栀攀 爀攀洀漀琀攀 攀渀搀 眀栀椀氀攀 瀀爀漀挀攀猀猀椀渀最 琀栀攀 挀漀洀洀愀渀搀⸀∀紀紀ഀ਀
[WindowsDriver@b02c (94a11461)] Got response with status 500: {"status":13,"value":{"error":"unknown error","message":"An unknown error occurred in the remote end while processing the command."}}
[debug] [W3C] Matched W3C error code 'unknown error' to UnknownError
[debug] [WindowsDriver@b02c (94a11461)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: An unknown error occurred in the remote end while processing the command.
[debug] [WindowsDriver@b02c (94a11461)]     at errorFromW3CJsonCode (C:\Users\qahw\AppData\Roaming\npm\node_modules\appium\node_modules\@appium\base-driver\lib\protocol\errors.js:1040:25)
[debug] [WindowsDriver@b02c (94a11461)]     at ProxyRequestError.getActualError (C:\Users\qahw\AppData\Roaming\npm\node_modules\appium\node_modules\@appium\base-driver\lib\protocol\errors.js:909:14)
[debug] [WindowsDriver@b02c (94a11461)]     at WADProxy.command (C:\Users\qahw\AppData\Roaming\npm\node_modules\appium\node_modules\@appium\base-driver\lib\jsonwp-proxy\proxy.js:352:19)
[debug] [WindowsDriver@b02c (94a11461)]     at processTicksAndRejections (node:internal/process/task_queues:95:5)
[debug] [WindowsDriver@b02c (94a11461)]     at WinAppDriver.sendCommand (C:\Users\qahw\.appium\node_modules\appium-windows-driver\lib\winappdriver.js:223:12)
[debug] [WindowsDriver@b02c (94a11461)]     at WindowsDriver.getScreenshot (C:\Users\qahw\.appium\node_modules\appium-windows-driver\lib\commands\general.js:48:22)
[HTTP] <-- GET /session/94a11461-2ced-4895-b689-7cd4e44c6446/screenshot 500 27 ms - 1221
[HTTP]

Expected Behavior
Screen short from windows application should be captured successfully
Minimal Reproducible Example
driver.get_screenshot_as_base64()
Environment

Operating system: Windows 10 OS, 64 bit
Appium server version (output of appium --version): appium 2.0.0 RC3
Appium driver(s) and their version(s<EMAIL_ADDRESS>(automationName 'UiAutomator2')
Appium plugin(s) and their version(s<EMAIL_ADDRESS>(automationName 'UiAutomator2')
Node.js version (output of node --version): v18.12.0
npm version (output of npm --version): 8.19.2
Last component(s) version which did not exhibit the problem: never worked
Platform and version under test: Windows
Real device or emulator/simulator: real windows app

Link to Appium Logs
https://github.com/bwomsm1/AppiumLogs/blob/master/win_app_appium.log
Futher Information
No response

Windows Application Driver is <IP_ADDRESS>

Any good reason that you want the image with base64?

I am attaching the base64 data to html page, it has to be in base64.

Can you try taking normal screenshot without base64?

Can you try taking normal screenshot without base64?

@anunay1 what API you are suggesting? I see that also get_screenshot_as_png() is passing through get_screenshot_as_base64() which I am using today.


Fix Ignore Subnet ID

Do not recreate the instance if the subnet ID changes. This is because
the data.aws_subnet_ids data source has been deprecated and the
replacement does not return the subnets in the same order.

Don't use data.aws_subnet_ids data source...
This PR is not going to be merged because it does not satisfy everyone's needs and Terraform doesn't allow usage of variables in lifecycle block.


How to easily build and distribute on stores with capacitor electron ? (Microsoft store, OSX, Chrome)

Distributing Electron desktop apps is a big pain, especially on Microsoft store.
Updating these apps are also a big thing, autoUpdater work differently on different devices. Specific certificates are necessary on Microsoft, etc....
How do you distribute new versions of your desktop apps with Capacitor in a blink ?
Thanks a lot !

A more seem-less way of doing OTA type updates for electron apps would be great and I am kinda poking at it, but check out electron-builder and electron-windows-store and see if those at least aid you in distribution.

@IT-MikeS electron-builder and electron-windows-store are really heavy with a lot of configs needed to build on stores

They are yes, but unfortunately they are really the only good options for electron apps at the time.
I do know they are really open to suggestions to make the tools better, so if you have any ideas on how to streamline the processes they do, or how to slim down the install base of the apps, I'm sure they'd love to hear it over on their respective repos 🚀

a tool like Appflow would be the best

And also a simple medium article about Electro build / distribution on all stores

A tool like AppFlow would be great but that's a really tall order for the time I currently have in my free time outside of my 9-5, but someone else is always free to build such a tool.
As for the article, there are plenty out there including some great video tutorials on building electron apps into store or other distributions, and my tutorial writing is rusty at best when you compare it to some of the awesome guide writers out there.

@IT-MikeS you should really talk with https://todesktop.com/, they provide a standard api / builder for desktop apps https://docs.todesktop.com/

It's really easy to use and powerfull, could be awesome to share the same apis


Add JSDoc documentation to Webpack 2

I'm submitting a feature request
Please consider adding JSDoc documentation to Webpack 2. This will allow code completion/inspection of webpack config files for IDE that supports it, such as WebStorm.
Webpack version:
2.x

I would much rather see a Flow type annotations than JSDoc.
JSDoc gets easily de-synced with the code. It does not provide any use outside of documentation.
Flow type does not need to enforced. It can be used to simply document the code. Here is an example of a codebase that uses Flow type annotations to document the code.
https://github.com/gajus/gitinfo/blob/master/src/gitinfo.js

Or Typescript 😏.

@kevinlaw91 this would be a substantial undertaking, but also incredibly impactful. We would certainly consider a PR.

Or Typescript 😏.

I am not proposing to adapt strict typing. As you said, that would be a significant chunk of work.
I am suggesting to use types for documentation purposes instead of JSDoc, e.g.
Instead of:
/**
 * @param {string} value The haystack value.
 * @param {string} searchValue The needle value.
 * @returns {boolean}
 */
const includes = (value, searchValue) => {

};

Use:
/**
 * @param value The haystack value.
 * @param searchValue The needle value.
 */
const includes = (value: string, searchValue: string): boolean => {

};

it becomes even more succinct if you don't use description:
const includes = (value: string, searchValue: string): boolean => {

};

You can then leverage https://github.com/gcanti/babel-plugin-tcomb or https://github.com/codemix/babel-plugin-typecheck to enable type checking during runtime (for testing purposes).
This does not require full transformation/ compliance to Flow or TS.

I believe converting to strict typing would be a different topic here. The main idea is to start adding basic documentation within the code.
Flow is nice to have, I do agree with @gajus . However, consider the effort needed for the transformation, it only brings huge benefits to webpack developers and offer less to the normal webpack users.
JSDoc are easier and faster to implement. and both users and developers can enjoy the advantages.

Type definition is optional in JSDoc, much easier to write
Javadoc like syntax, don't have to learn Flow to write
Selectively documents parts of the code (most important first) and cover more later
In the future when the time is right, existing JSDoc can be transformed to Flow with less work too

However, consider the effort needed for the transformation

The only addition would be a required to have a transpilation step to either remove Flow annotations or to convert them to JSDoc.

Javadoc like syntax, don't have to learn Flow to write

This assumes that more developers are familiar with JSDoc syntax than with Flow. While that might be true, JSDoc is also infamous for inconsistent use. Hey, but either, I have got you covered regarding consistency:

https://github.com/gajus/eslint-plugin-flowtype
https://github.com/gajus/eslint-plugin-jsdoc

:-)

Selectively documents parts of the code (most important first) and cover more later

That is equally true to Flow and JSDoc.

In the future when the time is right, existing JSDoc can be transformed to Flow with less work too

It is easier to transform Flow to JSDoc than JSDoc to Flow.

I think "code-only documentation" or "C.O.D (piece)" as I like to call it, is great for experienced developers. However, I use documentation in my workflow specifically because we don't always live in a perfect world with top notch developers writing every line of code with the ability to understand why a linter is complaining or why the world works the way it does. There is more than one way to work and I, preferably, like to make sure that the tools I choose, like webpack, are inclusive to all levels of developers and even non-developers who sometimes need to understand your work.
TL;DR:  +1 for jsDocs. If you don't like it, don't use it.

TL;DR: 👍 for jsDocs. If you don't like it, don't use it. :-)

Is not an argument. It creates additional work and requires to maintain duplicate set of information, which increases the odds of an error.

Is not an argument.

Correct, it's a discuss...and just adding a point of view and support, which is "having jsDoc in Webpack would be nice-to-have inclusive feature and it doesn't prevent you (or I for that matter) from using Flow."

I would love to implement JSDOC for webpack. Our only hurdle is that our code is run as is via node. That is to say that we do not transpile our SRC when the user uses it. So although I see the obnoxious benefits, we can't jump to it just yet without already pursuing some sort of build process which doesn't exist today.

obnoxious benefits,
I think you mean "obvious" but obnoxious works too


include table

As far as i see there is no support for tables - am i right?

http://gtk-rs.org/docs/gtk/struct.Grid.html ?

Gtk.Table has been deprecated since GTK+ version 3.4 and should not be used in newly-written code. Use the Grid class instead.

Thanks!


Add TacBlok Logo to Header

https://github.com/sopra-fs23-group-40/Client/commit/f1a1d1f027b9a021b7d267fc2683ef6af9373b48


Mobile | Search on homepage broken

Device: iPhone 6, Browser: Firefox (however, since all browsers on iOS uses the same Webkit engine, results are similar).

fixed in the latest build. Issue: clamp() not supported on older ios


add CFA taxon

Could you elaborate a bit? I began the work but then struggled. My idea was that you could compose GFactors:
https://github.com/StructuralEquationModels/Taxonomy.jl/blob/f75706f583f88782ec57a55571085b21c18a95aa/src/taxons/cfa.jl#L1
To build hierachical models:
https://github.com/StructuralEquationModels/Taxonomy.jl/blob/f75706f583f88782ec57a55571085b21c18a95aa/src/taxons/cfa.jl#L17-L20

I was thinking about cases like 3 factor CFA like conducted here: https://journals.sagepub.com/doi/suppl/10.1177/1073191120905892
Would we compose a GFactor for every Factor and then combine them?

No simply combining will not do, instead we need something that describes how many items are loaded by how many latent variables.

OK, i will make a proposition ...

I am wondering if it is possible to also code something like bifactor models:


Add IAM Access Groups service and tests to the project

PR summary
This PR adds the IAM Access Groups service, unit test and a skeleton integration test to the project.
Fixes: n/a
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

:tada: This PR is included in version 0.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


integrate react native with jose

Hi,
I write an application that receives data in JSON format and I want to validate the data source before the application starts to process the data.
currently the data is stored in Amazon and the application is written in React Native (version 0.45.1).
I wonder:

Is it possible to integrate jose package with react native?
If yes, how?
In the 1st stage I will have static data in Amazon, so I wonder how I can sign the data with jose

Thanks

Hi,
On client side, it looks difficult to integrate this library in your application as it is writtent in PHP and your application is in JS.
I found a nice blog post where tokens are used. It may help you to validate those signatures in your react native application.
I do not use Amazon services, however if you can run PHP applications on their servers, then you will be able to sign your data with this library.

As I understand from the article the validation is done using 'tcomb-form-native' library which works on forms, and it only validate that the data is in the expected type and not the value.
The tokens are used to perform authorization, this is an issue that currently I don't need to address.
I need to validate if the data arrived from the source I expect, to prevent Man In the Middle Attack.

I am sorry I misunderstood your need.
So I think you could directly use jsrsasign to verify the tokens from your application (see http://kjur.github.io/jsrsasign/slide_e/#/11 for an example of verification).

Thanks, I am already trying to use jsrsasign..hopefully it will work

Closing as I do not think this library will help you (JS application).
Feel free to reopen it if you think so.


Why is pyparsing a requirement for this library

I think this is a hold-over from previous changes which can be removed.

Fixed with e410bdb21c8070dc9f3fe82e397732c21ca376c0


Departures re-entering airspace request taxi

If departures leave your airspace and rejoin your airspace again, they will request taxi instead of report their altitude. They continue en-route despite this, however.
http://prntscr.com/b6rqyv

It isn't ideal that they request taxi, but it doesn't really seem possible to me that the airspace could possibly be set up for this flightpath to be the case... If VIDP Approach really does own that long skinny piece of airspace the aircraft is entering in the screenshot, they would definitely own the area around it too... this is probably another instance of the need to find the associated outer area, and not just the TMA/TCA, as discussed in #511.
I agree that the airplanes are saying something odd, but really the issue lies with the probability that the airspace provided to the game is not the same airspace the ATC facility actually owns, but only the portion that is of an elevated airspace classification.

If en route mode becomes a thing, we can make a fix for this, but for now, it should suffice to just use airspace shapes that don't cause this issue. Closing :smile:


Issue 161

@vothaison
Please get latest code and continue the backend (read file and generate code)
For the UI,

Can select multiple test routine but not all  (parameters contains list of dataset id)
Can select all dataset  (parameters contains '*')

See below image


Examples of commands for browsertime

#118 First round to get documentation going along with a few examples.

Looking great! It'd be great if you could tweak some minor things before merge:

All examples assumes running from a checked out git repo. If installed via npm (e.g. npm install  -g<EMAIL_ADDRESS>the commands will be run with "browsertime …". Could be good to at least mention initially.
Could you have an option value in all cases where it's required, so the examples parse ok. I think that'l be less confusing. I.e. "bin/browsertime.js https://www.sitespeed.io --chrome.mobileEmulation.width -b chrome" would need a width, as well as width and pixelRatio to run).
Squashing the commits would be nice.

Will do on all of the above. Keep the feedback coming!

Sweet. Thanks Jonathan!


handle packets that are too large more gracefully

currently we don't check packet size in voyager, which is an issue if the packet is too large for a block. on evm we will get a message that looks like: (code: -32000, message: oversized data: transaction size 219901, limit 131072, data: None)

update: with the new voyager plugin-based design, this is now the responsibility of the ethereum transaction submission module.


demo.R script - OutputCollect pareto_fronts error

Project Robyn
Describe issue
Just installed Robyn today and while trying to run through the standard demo.R script, I have hit an error at the OutputCollect generation line. This is the error I get:
> OutputCollect <- robyn_outputs(
+   InputCollect, OutputModels,
+   pareto_fronts = "auto", # automatically pick how many pareto-fronts to fill min_candidates
+   # min_candidates = 100, # top pareto models for clustering. Default to 100
+   # calibration_constraint = 0.1, # range c(0.01, 0.1) & default at 0.1
+   csv_out = "pareto", # "pareto", "all", or NULL (for none)
+   clusters = TRUE, # Set to TRUE to cluster similar models by ROAS. See ?robyn_clusters
+   plot_pareto = TRUE, # Set to FALSE to deactivate plotting and saving model one-pagers
+   plot_folder = robyn_object, # path for plots export
+   export = TRUE # this will create files locally
+ )
>>> Running Pareto calculations for 1000 models on auto fronts...
Error in 1:pareto_fronts : NA/NaN argument
In addition: Warning message:
In robyn_pareto(InputCollect, OutputModels, pareto_fronts, calibration_constraint,  :
  NAs introduced by coercion

The only things I have changed in the demo script are:

Reduced the iterations to 500 and trials to 2 - I know this is below recommended levels but I didn't have time so was trying to get something quickly - if this is the reason behind the error then that is simple enough, but just want to be sure as the error message doesn't really indicate it has anything to do with those parameters.
Deleted train_size as a key in the hyperparameters list - this was because I got the following error earlier:

> InputCollect <- robyn_inputs(InputCollect = InputCollect, hyperparameters = hyperparameters)
Error in check_hyperparameters(InputCollect$hyperparameters, InputCollect$adstock,  :
  Input 'hyperparameters' contains following wrong names: train_size

Provide reproducible example
As mentioned above, the standard demo.R file on this Github with iterations=500 and trials=2 on lines 332 and 333 respectively, as well as deleting train_size in the hyperparameters list on line 200.
Environment & Robyn version

Robyn version: 3.7.2
R version: 4.2.1 (2022-06-23 ucrt)

Any help would be great, thank you! Happy to share additional debug information if needed.

Thank you @laresbernardo! I'm trying robyn_update() and getting the following error (of course it couldn't be simple :)):
Downloading GitHub repo facebookexperimental/Robyn@HEAD
Error in utils::download.file(url, path, method = method, quiet = quiet,  :
  cannot open URL 'https://api.github.com/repos/facebookexperimental/Robyn/tarball/HEAD'

I have installed the remotes package - I'm on Windows.
I've also tried the options(timeout=400) solution mentioned elsewhere in the repo, but no dice. I might not be doing it properly though - I ran it as a standalone command, as well as an argument to the remotes::install_github command, didn't work either way.
For now I'll just use the older demo.R file, but would be great to figure out how to get to the dev branch if that's what you guys recommend. Thanks again!

So I ended up running into an error in the same place in the older demo.R file - keeping it in this thread just in case it's an easy fix otherwise happy to open another issue.
> OutputCollect <- robyn_outputs(
+   InputCollect, OutputModels,
+   pareto_fronts = 3,
+   # calibration_constraint = 0.1, # range c(0.01, 0.1) & default at 0.1
+   csv_out = "pareto", # "pareto" or "all"
+   clusters = TRUE, # Set to TRUE to cluster similar models by ROAS. See ?robyn_clusters
+   plot_pareto = TRUE, # Set to FALSE to deactivate plotting and saving model one-pagers
+   plot_folder = robyn_object # path for plots export
+ )
>>> Running Pareto calculations for 1000 models on 3 fronts...
Error in `bind_rows()`:
! Can't combine `..1$ds` <date> and `..2$ds` <IDate>.

Running the last trace gives:
<error/vctrs_error_ptype2>
Error in `bind_rows()`:
! Can't combine `..1$ds` <date> and `..2$ds` <IDate>.
---
Backtrace:
     ▆
  1. ├─Robyn::robyn_outputs(...)
  2. │ └─Robyn:::robyn_pareto(...)
  3. │   └─dplyr::bind_rows(...)
  4. │     ├─dplyr:::fix_call(vec_rbind(!!!dots, .names_to = .id))
  5. │     │ └─base::withCallingHandlers(...)
  6. │     └─vctrs::vec_rbind(!!!dots, .names_to = .id)
  7. └─vctrs (local) `<fn>`()
  8.   └─vctrs::vec_default_ptype2(...)
  9.     ├─base::withRestarts(...)
 10.     │ └─base (local) withOneRestart(expr, restarts[[1L]])
 11.     │   └─base (local) doWithOneRestart(return(expr), restart)
 12.     └─vctrs::stop_incompatible_type(...)
 13.       └─vctrs:::stop_incompatible(...)
 14.         └─vctrs:::stop_vctrs(...)
 15.           └─rlang::abort(message, class = c(class, "vctrs_error"), ..., call = vctrs_error_call(call))

Again, haven't changed anything from the demo.R script this time except reducing the number of trials (2) and iterations (500).
If there's any other output I can provide to help let me know!

Hi! I am getting this error when trying to add train_size hyperparameter in the Inputcollect. I see that this issue has been brought up here, but I didn't understand the solution besides having the latest dev version of Robyn. I have recently installed Robyn following the instructions provided on the website. @laresbernardo could you please guide me in fixing this error?

! Can't combine ..1$ds  and ..2$ds .

@aazimh  This error comes from a very old version that was fixed some time ago. It occurred when trying to bind data.table's date format with basic Date format. I strongly suggest you update to latest versions.

this error when trying to add train_size hyperparameter in the Inputcollect

@CJ2407 what error exactly? The (...) Can't combine ..1$ds (...)? When updating to latest dev version (Robyn::robyn_update()) be sure to reset your R session before retrying.

@laresbernardo I keep getting this error and hence unable to enable ts_validation -
Error in check_hyperparameters(InputCollect$hyperparameters, InputCollect$adstock, :
'hyperparameters' contains following wrong names: train_size

'hyperparameters' contains following wrong names: train_size

If you're using version >=3.9, then you can define train_size hyperparameter range. If <3.9, then it'll give you that error. So, exclude that hyperparameter from your hyperparameter input if you're in <3.9.

Robyn::robyn_update()

If you don't have this function, you're not even using the latest stable version from CRAN, thus a very old function. That's the same as running remotes::install_github("facebookexperimental/Robyn/R").
It's quite relevant 1) updating Robyn frequently, 2) knowing which version you're using and 3) knowing what changes and updates we've deployed to understand these errors and warnings.

I am getting this error when running OutputCollect..
Using robyn object location: C:/BurgerKing_mmm/NM

Running Pareto calculations for 50000 models on auto fronts...
Automatically selected 1 Pareto-fronts to contain at least 100 pareto-optimal models (247)
Calculating response curves for all models' variables (494)...
Pareto-Front: 1 [247 models]
00:02:23 [=================================================================================================] 100% | 247
Error in robyn_outputs(InputCollect, OutputModels, pareto_fronts = "auto",  :
object 'create_files' not found

Hey @tgtod002 that's because you have to define the create_files object or replace it with TRUE or FALSE.

Please reopen if necessary.


Possible bug

https://github.com/cretueusebiu/laravel-vue-spa/blob/5fffeee89d9e5aa78cd626f4e8ef7c4e2781d487/resources/js/plugins/i18n.js#L26
store is undefined when called from middleware locale.js
https://github.com/cretueusebiu/laravel-vue-spa/blob/5fffeee89d9e5aa78cd626f4e8ef7c4e2781d487/resources/js/middleware/locale.js#L5
please check

solved by moving anon function before new Vue in app.js


Add support for multipart form requests

Fixed in https://github.com/aaronvb/request_hole/releases/tag/v1.2.1


Simple linalg.generic segmentation faults on M1 Mac

This simple linalg.generic fails on M1 Mac. The program executes correctly on x86 linux and when traced through compilation produces identical LLVM IR (no target specific IR). It appears to be in LLVM-core for compilation to Mac OS X.
Unsure how to triage from here.
failure.mlir.zip

Could you check if https://reviews.llvm.org/D140806 has any impact here? (It shouldn't be unless you happened to use universal build and ran with different arch than arch when it was built, but just in case)


python311Packages.google-cloud-translate: 3.15.2 -> 3.15.3

Changelog: https://github.com/googleapis/python-translate/blob/v3.15.3/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.11 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.

Add a :+1: reaction to pull requests you find important.

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

4 packages marked as broken and skipped:

python312Packages.google-cloud-translate
python312Packages.google-cloud-translate.dist
python312Packages.wagtail-localize
python312Packages.wagtail-localize.dist

4 packages built:

python311Packages.google-cloud-translate
python311Packages.google-cloud-translate.dist
python311Packages.wagtail-localize
python311Packages.wagtail-localize.dist


eodash-catalog self attribute should be absolute URL

https://eurodatacube.github.io/eodash-catalog/RACE/catalog.json currently has
{
      "rel": "self",
      "href": "/home/runner/work/eodash-catalog/eodash-catalog/build/RACE/catalog.json",
      "type": "application/json"
}

should be
"href": "https://eurodatacube.github.io/eodash-catalog/RACE/catalog.json"

example code snippet
        catalog_file_path = os.path.join(catalog_path, "catalog.json")
        with open(catalog_file_path) as f:
            stac_catalog_content = json.load(f)
        for index, x in enumerate(stac_catalog_content["links"]):
            if x.get("rel") == "self":
                break
        stac_catalog_content["links"][index]["href"] = "catalog-self-href"
        # save updated catalog
        with open(catalog_file_path, "w") as f:
            json.dump(stac_catalog_content, f, indent=2)


Get rid of invites system

The title explains it all

HOLD

Stop talking to yourself.

TEST - Not working so far.


chore: husky commit linting on mac

Summary
husky commit linting was not running as expected on mac (see screenshot below).
ran
chmod +x .husky/pre-commit
chmod +x .husky/commit-msg
modifies husky file permissions, allowing functionality for mac users
Screenshots

:tada: This PR is included in version 1.7.0-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update Gcloud version

Update google-cloud-bigquery==3.2.0
Tested with meltano elt

@seanglynn-thrive Thank you for updating this. I tested in my env and it works after the update. Merging and cutting a new version on pypi.


Increase click area of thumb in Slider

It would be great if there would be such functionality.
Or maybe there is already?

I have added sl_thumbTouchRadius attribute for Slider in dev branch. It will available in next release.


feat: validate just the PIA can call issue and redeem token

:tada: This PR is included in version 4.0.0-alpha.11 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0-alpha.11 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


PLS HELP

Hi, the program breaks at step 5 of "Usage" for me. I have the cookies all set up but it's giving me the first attachment when I try to run the .exe, and the second after I hit enter, no matter how many times I run it.

Im sorry about that, thanks for letting me know. I will look into it

I will delete the latest release so you can still use it, if it tries to update after i delete the latest release download the 1.3.2 version

Reuploaded the latest release 1.3.3

Thanks! It worked, but it ran into captchas it couldn't get through after a few codes

Hey sorry, i didnt get any notifications for this. When you get the captchas you should not use it for a day or so because you are being rate limited, it should go away after some time so probably a day or 2 maybe

Hey @Asharm123, just wanted to check in before closing this issue. Have you been able to redeem the glyphs?

@Noxde I don't know about the other guy, but the program works and I was able to claim the glyphs.

@Noxde I don't know about the other guy, but the program works and I was able to claim the glyphs.

Glad to know that it worked fine for you, I will close this issue now since he hasnt answered in a week and it only was a rate limit issue


Add docs to integrate new apps to the tool

@ernesgonzalez33 please, it is required to include some aspects in the documentation:

create the respective case in deleteAppBundle function
create the respective case in calculateAppsFillCluster function

@acidonper done! Kindly check the last commit.

I have added new examples and explanations to the docs to make it more visible and more specific in some of the steps


cel-key/rpc: different celestia account addresses comparing to rpc cli call

Celestia Node version
v0.13.1
OS
osx
Install tools
No response
Others
No response
Steps to reproduce it

Expected result
same addresses from cel-key and rpc cli calls
Actual result
not same addresses from cel-key and rpc cli call
Relevant log output
No response
Notes
No response

Aha - reproduced it
using --home won't take effect if --node.type is provided as --node.type flag overrides home dir and looks for the default celestia directory when no network is provided which is mainnet (~/.celestia-light)
Use --keyring-dir ~/.celestia-light-mocha-4/keys instead of --home and that will fix the issue.
We do need to improve keyring directory identification for cel-key though, it's currently all over the place. Apologies for the jankyness.

Repurposing this issue to change UX around directory determination in cel-key


Clean up session directory

We have an instance of Omero in production and it is recently causing the VM to perform poorly. We checked the session directory (omero/sessions) and there are 144K+ sessions there. I know that we may break some clients' connections by cleaning up this directory and just would like to make sure that we do not break the Omero on our side. Do you suggest this?

Hi @Hamedhm. Do you have any automated processes that are running on the server itself?
You are right that a clean or garbage collect step would be useful, but at the same time, I've not seen this problem before. Typically on the client side, when a user logins in, an older, inactive session is cleaned up.
If the sessions are coming from an automated process and therefore aren't being re-used, then getting rid of the files will likely go unnoticed.
~Josh
P.S. depending on how such processes are being launched, you can have them use their own temporary sessions directory to make clean up easier.

Hi @joshmoore
Thank you for following this up.
Yes, we have an automated process to upload 100K+ images to Omero, one by one by creating independent sessions; and we are the only clients that connect to that server (it is a dev server).
I am planning to clean the sessions up and create a job that cleans them regularly.
Thank you so so much for your help.

@Hamedhm :+1: Glad to hear it.
See https://docs.openmicroscopy.org/omero/5.6.3/users/cli/sessions.html#sessions-directory if you want to attempt the separate sessions directory.
All the best.


Neither the property ... exist in "Symfony\Component\Form\FormView" in LexikMailerBundle:Email:new.html.twig

Hello, after applying your steps , when i try to create  a new email it gives me this error:

Neither the property "_token" nor one of the methods "_token()", "get_token()"/"is_token()" or "__call()" exist and have public access in class "Symfony\Component\Form\FormView" in LexikMailerBundle:Email:new.html.twig at line 71

Have you disabled CSRF protection on your forms? What version of symfony are you using?


[IOTDB-5134] Fix Auth Module Contain

fix READ_DATA, READ_SCHEMA, WRITE_DATA, WRITE_SCHEMA

coverage: 47.929% (-0.01%) from 47.941% when pulling 7cd26c634013500d8072fa11dfd1a1bf5ebd5cb0 on refactor/auth_contain into a9c615db50d4062c0065a04dd3a123de1a632213 on master.


Frontend feed new

Working feed, yay!

Coverage remained the same at 71.067% when pulling 16ab9d390b206a526fe264f07a45bfb62453240b on frontend-feed-new into 13cc4b7952d1c27dbf0922ac3a24ce07ac365d50 on master.


Collect python sub-resources from all hiera levels

Pull Request (PR) description
Hiera may be used at module, environment and global levels.
Default lookup strategy is "first", so pips, virtualenvs, pyvenvs,
requirements and dotfiles will be collected just from one level and in
case of two independent modules wants some pips (for example), only one pip will
be chosen for installing.
To avoid it we should use deep merge strategy in lookup function.

I prefer not do a deep merge in a module because there might be people who don't need it and they cannot simply change this option.
I would suggest to use lookup_options directly in Hiera --> https://puppet.com/docs/puppet/5.5/hiera_merging.html#concept-2997

I prefer not do a deep merge in a module because there might be people who don't need it and they cannot simply change this option.
I would suggest to use lookup_options directly in Hiera --> https://puppet.com/docs/puppet/5.5/hiera_merging.html#concept-2997

I see.
Thank you for explanation and sorry for disturbance.


Half Donut Vertical Centering

Work In Progress Towards https://github.com/f5/unovis/issues/441

Current status:

Current status: This PR makes the half donut centered vertically.

I think this is ready for review and testing. Thanks!

Direction forward:

[ ] Modify the examples to showcase the responsive behavior of all pie examples when resizing the SVG both vertically and horizontally
[ ] Compute the bounding box that surrounds the donut
[ ] Use the bounding box for the scaling logic to fill the available space in the SVG

Current status:

Got the resizing and scaling behavior to a point where it feels right
Scaffolded the scaling and translation logic for all 4 types of half-donut (but haven't tested those yet - I'm debating whether I should create a new example for each case, or maybe just spot check them in development)

https://github.com/user-attachments/assets/abe74484-43d9-4ab3-a0a3-592714463aa1

Problem with this: the sub-label gets cut off, because it's below the edge of the half donut
Proposed solution: we allow configuration of the margin (called bleed in this codebase) from the example
If we allow configuration of the margin, then the example could set a bottom margin to account for the space needed by the sub-label

I propose to make it configurable like this:
      <VisDonut
        ...
        bleed={{ top: 0, bottom: 0, left: 0, right: 0 }} // Current not available as a prop
      />

What do you think of this idea to expose the bleed as a prop @rokotyan ? Thanks!

What do you think of this idea to expose the bleed as a prop @rokotyan ? Thanks!

All other Unovis components calculate the bleed value automatically, so exposing it as a prop goes a bit against the philosophy of the library. Also, we already have container properties like margin and padding, and I think adding bleed might make it more confusing for users.

Scaffolded the scaling and translation logic for all 4 types of half-donut (but haven't tested those yet - I'm debating whether I should create a new example for each case, or maybe just spot check them in development)

You can have all 4 of them on one page. This way it'll also be easier to test them with a visual testing framework.

we already have container properties like margin and padding

Oh that's excellent news! I didn't think the margin was already configurable, since I didn't see it in DonutConfigInterface or its superclass ComponentConfigInterface. I did not think to look in the VisSingleContainer props, but sure enough it's there and it works like a charm:

Thank you for the tip!

Current status:

Got a setup working where I can test all the various half-donut cases. Here's what they look like:

Idea: export the angle ranges from Unovis somehow. WDYT @rokotyan ? Something like this:

export const halfDonutTopAngleRange: [number, number] = [-1.5707963267948966, 1.5707963267948966]
export const halfDonutRightAngleRange: [number, number] = [0, 3.141592653589793]
export const halfDonutBottomAngleRange: [number, number] = [1.5707963267948966, 4.71238898038469]
export const halfDonutLeftAngleRange: [number, number] = [3.141592653589793, 6.283185307179586]

Not sure the best way to do that within the Unovis setup... Attach them as properties of VisDonut maybe?
e.g.
import { VisSingleContainer, VisDonut } from '@unovis/react'

...
      <VisDonut
        value={d => d}
        data={data}
        showEmptySegments={true}
        padAngle={0.02}
        arcWidth={100}
        duration={props.duration}
        angleRange={VisDonut.halfDonutTopAngleRange}
        // angleRange={VisDonut.halfDonutRightAngleRange}
        // angleRange={VisDonut.halfDonutBottomAngleRange}
        // angleRange={VisDonut.halfDonutLeftAngleRange}
        centralLabel='Central Label'
        centralSubLabel='Sub Label'
      />
...

Another option would be:

import {halfDonutTopAngleRange} from '@unovis'

or something like that. Curious to know what the idiomatic Unovis API design would look like for something like this.

 * Working through getting the scaling right for all cases.
 * I do like the idea of a big example page with all the options, but that approach makes it more difficult to test out the responsive scaling as I go

Plan for next steps:

 * Get the scaling to work properly, each possibility in isolation
 * Make a new example page that shows all the possible half-donut configurations in one place (likely without nice responsive behavior)
 * Iterate once more on the PR based on feedback, then I think this will be ready to go!

@curran
Instead of forcing the users to use margin, I would change the text baseline and alignment and of the labels automatically to always stay visible, or make it configurable at least.
For example:

As for exporting the constants, we can add a constants.ts file to components/donut and re-export it from index.ts. The only thing, I would like to prefix the constants with the component name and maybe use the UPPER_CASE. i.e. DONUT_HALF_ANGLE_RANGE_TOP instead of halfDonutTopAngleRange.

Excellent! Thank you for this feedback. I will do it that way.

[ ] Donut half right: align text to start
[ ] Donut half left: align text to end
[ ] Donut half top: offset text vertically (upwards) to fit the sub-label within the bounds of the half donut rectangle
[ ] Donut half bottom: offset text vertically (downwards) to fit the sub-label within the bounds of the half donut rectangle

Finally nailed the scaling for top half donut!
https://github.com/user-attachments/assets/734845dd-eb31-4bc6-934d-4560583a44bc


fix: upgrade jest to v26

BREAKING CHANGE: Jest peerDependency has been moved from 24->26

Bors merge bot cheat sheet
We are using bors-ng to automate merging of our pull requests. The following table provides a summary of commands that are available to reviewers (members of this repository with push access) and delegates (in case of bors delegate+ or bors delegate=[list]).

Syntax
Description

bors merge
Run the test suite and push to master if it passes. Short for "reviewed: looks good."

bors merge-
Cancel an r+, r=, merge, or merge=

bors try
Run the test suite without pushing to master.

bors try-
Cancel a try

bors delegate+
Allow the pull request author to merge their changes.

bors delegate=[list]
Allow the listed users to r+ this pull request's changes.

bors retry
Run the previous command a second time.

This is a short collection of opinionated commands. For a full list of the commands read the bors reference.

bors merge


How can I open get parameters from branch link without opening it like deep-link?

I need to get parameters from branch link without application restart. It is uncomfortable for user when I open branch link as
startActivity(new Intent(Intent.ACTION_VIEW).setData(Uri.parse(link)));

and in first time user should choose an application, where he want open that link

Hey Ray - we never added a function to the SDK to do this it didn't occur to us as a use case. However, you can use this API endpoint we have to retrieve the parameters: https://github.com/BranchMetrics/Deferred-Deep-Linking-Public-API#viewing-state-of-existing-deep-linking-urls
Hope this helps!

we never added a function to the SDK to do this it didn't occur to us as a use case.

That's a shame. It would be very useful. I want to embed a link in a QRCode, so during on boarding a user could scan the code, I can would extract the parameters so I can customise on boarding without leaving the app.
Without this feature I need to open the url and the user now exits the app :(

@sclancy we added support for this use case recently. SDK provides option to add a link to an activity and get params. Please check here
https://github.com/BranchMetrics/android-branch-deep-linking#deeplink-via-push-notification
Once you get the link from QR code activity launch your activity to receive the deep link params with above inent.

This documentation is quite bad. Do you have any further information about how to parse a link and get the BranchUniversalObject without restarting the activity? Just think of the usecase of a QRcode and scanned within the application.
Is there really no functionality to simply parse an Uri and get the information? (public boolean initSession(BranchUniversalReferralInitListener callback, @NonNull Uri data) does not work)

@mlostekk Really sorry that you are having an issue with the documentation. The link shared in the above comment is specifically for handling deep linking through push notifications. For the QR code can you please try the following

QR code scanner Activity  scans the QR code and get the Branch link embedded  in the QR Code
Open yourDeepLinkActivity.java with the following intent  Intent intent = new Intent(ScannerActivity.this, DeepLinkActivity.class);
  intent.putExtra("branch_force_new_session", true);
  intent.putExtra("branch", "branch_link_embedded_in_qr_code");
  ScannerActivity.this.startActivity(intent);

3. In your DeepLlinkActivity.java#onStart()

Branch.getInstance().initSession(new Branch.BranchUniversalReferralInitListener() {
@Override
public void onInitFinished(BranchUniversalObject branchUniversalObject, LinkProperties      linkProperties, BranchError error) {
// Use the BUO
}
})
Unfortunately SDK doesn't support init again in the same activity. If you are looking for getting the deep link params without using intent as explained above please try our public API to retrieve link params
https://github.com/BranchMetrics/branch-deep-linking-public-api#viewing-state-of-existing-deep-linking-urls

Well, this is not possible in my setup. I cant start the DeepLinkAcitivty from my ScannerActivity due to dependency restrictions.
I am starting the ScannerActivity with startActivityForResult and returning the qr code to the ScannerActivity with setResult and finish. In this situation your mentioned solution does not work (onInitFinished is invoked with null objects).
Is there a way for my setup to solve this without restarting the whole application?

@mlostekk  Thanks for explaining the way you need it. You can achieve this simply by doing the following
 protected void onActivityResult(int requestCode, int resultCode, Intent data) {
        super.onActivityResult(requestCode, resultCode, data);
        if (requestCode == SCANNER_ACTIVITY_LAUNCH_CODE) {
            // Get link from scanner activity here
            getIntent().putExtra("branch_force_new_session", true);
            getIntent().putExtra("branch", "branch_link_embedded_in_qr_code");
        }
    }

Now you will get the deep link params in  InitFinished() . Please make sure you reset the both params added to the intent params after receiving the params.

@mlostekk Hope the above helped to solved the issue?

Hello @sojanpr
unfortuantely initSession still returns with all objects = null

by the way.. should getIntent().putExtra("branch", "branch_link_embedded_in_qr_code");  contain a string or an uri?

Okay, it seems to be working with an Uri. I will do intense testing and get back with the results. Thanks for your help

@mlostekk Glad that you got it working.  Let us know if you find any other issue


Update s3-utils to 0.1.177 in scala-steward-dependencies

About this PR
📦 Updates uk.gov.nationalarchives:s3-utils from 0.1.172 to 0.1.177
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
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 = "uk.gov.nationalarchives", artifactId = "s3-utils" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "uk.gov.nationalarchives", artifactId = "s3-utils" }
}]

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

Superseded by #61.


MAINTAINERS: remove Brandon Philips @philips

I have not been active in the project for quite some time so I am
stepping down.
Thank you for all of the work over the years to standardize container
formats everyone!

LGTM
Thanks Brandon
-------- Original Message --------
On Feb 5, 2020, 19:18, Brandon Philips wrote:

I have not been active in the project for quite some time so I am
stepping down.
Thank you for all of the work over the years to standardize container
formats everyone!

You can view, comment on, or merge this pull request online at:
https://github.com/opencontainers/image-spec/pull/798
Commit Summary

MAINTAINERS: remove Brandon Philips @philips

File Changes

M MAINTAINERS (1)

Patch Links:

https://github.com/opencontainers/image-spec/pull/798.patch
https://github.com/opencontainers/image-spec/pull/798.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

LGTM, thanks for all your work Brandon!


GDAL:x86-windows does not build because it depends on libmysql

GDAL:x86-windows does not build because it depends on libmysql
See also:
https://github.com/Microsoft/vcpkg/issues/3574 (same issue but lacks clear title)
https://github.com/Microsoft/vcpkg/issues/3614 (osgearth fails, depends on gdal and hence libmysql)
https://github.com/Microsoft/vcpkg/issues/3029 (libmysql fails, how about dependent libraries?)

One possible solution is to make libmysql optional using features.
I have done this for a fork of vcpkg that has a port for the legacy version of GDAL (1.x). Basically, you'd need to remove libmysql from Build-Depends in the CONTROL file and then add the following new section:
Feature: mysql
Description: MySQL support for GDAL 1.x
Build-Depends: libmysql

Next, portfile.cmake needs to be modified by guarding the file commands for libmysql with an if:
if("mysql" IN_LIST FEATURES)
    file(TO_NATIVE_PATH "${CURRENT_INSTALLED_DIR}/include/mysql" MYSQL_INCLUDE_DIR)
    file(TO_NATIVE_PATH "${CURRENT_INSTALLED_DIR}/lib/libmysql.lib" MYSQL_LIBRARY_REL)
    file(TO_NATIVE_PATH "${CURRENT_INSTALLED_DIR}/debug/lib/libmysql.lib" MYSQL_LIBRARY_DBG)
endif()

Now, vcpkg install gdal should work since it won't rely on libmysql. If you want to have MySQL support for the 64 bits version of gdal, you could execute gdal[mysql]:x64-windows.

Another option is to use libmariadb..

@OlafvdSpek That is certainly another option, but I don't know how much work it entails to get that working. Making libmysql support an optional feature was quite easy.

Changing Build-Depends might be all that's required.

Thank you both. I followed ShinNoNoir's advice now, because I don't really need libmysql at the moment. It is not clear to me whether Olaf's solution would require a GDAL and/or vcpkg fix, but replacing the dependency on a library that is no longer supported seems to be the sustainable solution.

I revert the libmysql to the previous version 5.7.17-3, pass build x86-windows and install successfully.

Hi @ahhz , thanks for reporting this issue!
Now GDAL has been fixed by adding a feature gdal [mysql-libmariadb]. Please update vcpkg and rebuild GDAL. If still has problem, please open a new issue.
Thanks.


How do I find the third paper?

Hello! Your work is excellent! and How do I find the third paper? I can't find it on Google Scholar. Thank you!

Hi @Dosiyoung, thanks for the interest in our work! Our paper is under review and we will post the pre-print arxiv later in the review process.

Hi @Dosiyoung, thanks for the interest in our work! Our paper is under review and we will post the pre-print arxiv later in the review process.

@Dosiyoung you can find the paper in https://ieeexplore.ieee.org/document/9387093 and also for the preprint version https://arxiv.org/abs/2103.07587


Ubuntu 20.04 support

As there are no 20.04 packages in PPA, I was using ubuntu build instructions, pkg-config is required but not mentioned in dependencies, installing pkg-config before using automake or executing autoreconf -i -f after resolves an issue.

As an add-on, please add 20.04 to the PPA. It would be very helpful to keep a clean system without too much self-compiled stuff.

Really need HSTR on my Ubuntu 20.04, too.. Without it I don`t have a good documentation ;)
BTW thank you for this great program! I use it everyday on every Linux System. 🙏
sudo add-apt-repository ppa:ultradvorka/ppa && sudo apt-get update && sudo apt-get install hstr && hstr --show-configuration >> ~/.bashrc && . ~/.bashrc
 Admin utilities and productivity applications.
 More info: https://launchpad.net/~ultradvorka/+archive/ubuntu/ppa
Press [ENTER] to continue or Ctrl-c to cancel adding it.

Hit:2 http://security.ubuntu.com/ubuntu focal-security InRelease
Ign:3 http://ppa.launchpad.net/ultradvorka/ppa/ubuntu focal InRelease
Hit:4 http://de.archive.ubuntu.com/ubuntu focal InRelease
Hit:5 http://de.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:6 http://de.archive.ubuntu.com/ubuntu focal-backports InRelease
Err:7 http://ppa.launchpad.net/ultradvorka/ppa/ubuntu focal Release
  404  Not Found [IP: 2001:67c:1560:8008::15 80]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/ultradvorka/ppa/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

I'm still on 18.04 - installing 20.04 VM and will fix the build and prepare PPA. I apologize for the delay.

@isanych @emk2203 @Armatorix I just finished release of HSTR for HSTR 20.04 - please install from PPA.

Installation successfully finished via PPA on my 20.04, thank you very much!!! :+1:
If someone wants to install HSTR via ansible, here is my little ansible playbook (rename it to pb_localhost_hstr.yml): pb_localhost_hstr.txt
Install ansible (apt install ansible). Afterwards you need to open a shell,  run sudo -i  and exit (so that you don´t need to enter PW for this session again and ansible can become root). Now run the downloaded playbook: ansible-playbook pb_localhost_hstr.yml


Disable cross-origin check

The viewer for PDF.js does its own cross-origin checks, refusing to load any remote PDFs, which stops the viewer loading PDFs from CDNs or remote storage locations, such as S3.

I don't think it's the way to comment out the whole validation code.
I think the solution would be:
var HOSTED_VIEWER_ORIGINS = ['*'];

(at line 7145)
Or delete the all of the validations, but I think there's a reason why this is in here.
@senny What do you think?

@MattFenelon can't we follow the suggestion in #12 and make HOSTED_VIEWER_ORIGINS configurable?

Closed by #20

What's... the latest on this


arm-gcc-8 takes much more time to run tests

Describe the bug
In Travis-CI, it takes more than double time to finish arm-gcc-8 test. Not sure if anyone knows to enhancement that.
see: https://travis-ci.org/openthread/openthread/builds/566705354

It seems other users of arm-gcc-8 are reporting similar concerns in the Arm Compilers Forum.

Yes, please feel free to close this issue.


Remove Link and File Tracking until they make sense to user.

Affected Version
Latest stable version of SS
Description
When I install the latest version of SS I now get some weird stuff about Link and File Tracking. I am sure this is really important but it is completely meaningless to the Content Editor. I have created one site where I have simply hidden the two tabs on the 10 Models or so.
I would recommend we remove their visibility from the CMS until someone has looked at this from a user's perspective. What do they do, what are they for, why do I need them, etc... etc...

There's been a lot of work in this area over the last few months. I think it's been disabled for models like members etc, can you please pull in the latest 4.2.x-dev branch and see if that is any better?

Thanks @ScopeyNZ. Closing as a duplicate of those

Thank you for your quick reply. Great to see that it has been fixed. Weird how something as major as that gets released. I mean, so much of the SS work is completely brilliant and all that, but it seems we sometimes forget the end goal: the user experience.

Thanks @sunnysideup. There's always a lot going on in the core development, and sometimes things slip through unnoticed for some time.

Totally, I understand that better than anyone else.  I guess what I am advocating is that perhaps more emphasis be placed on the user experience. I, for one, would be super happy to test a new release before it goes live. I am sure others would too.  The cost of such a test would be minimal in comparison to the costs of dealing with it after it has been released (i.e. AFAIK these Tracking Tabs are now on every CWP install).


Changes

I have created a branch
Created a file
Made a commit
Opened a pull request

This pull request has been closed because the repository is deleted


Problem with response HTML

Hi guys. I have followed the Visual Recognition tutrial however, the sample HTML is not producing the label_name or label_score variables

Suggestions?

Hello Matt,
Thanks for reporting the issue, I'll look into it.

Hello Matt,
I tried on my setup right now and it works (pasted the flow from this repository to make sure).
Only thing I can think of is that it may be an issue with service credentials, when running on bluemix, the service should be bound to the Node-RED application in BlueMix. This way, the credentials are automatically filled-in on the node:

One thing that I have not yet put upfront in the lab instructions is that the service should be bound to the Node-RED App. This is alluded to in the overall node-red labs, but we need to remind it in each lab I think.
BTW, are you getting any error message in the Node-RED log or console?
Thanks,

So, I added some instructions in PR #48 to the lab to warn about binding the service in BMix.
Can you check if that fixes the issue for you?
Thanks,

Thanks! Leave it with me, I probably did something wrong.

cheers

Matt Taloni
Client Solutions Asia Pacific/GCG/Japan                        Phone: +61 408 882 547                        Email<EMAIL_ADDRESS>
What will you do with Watson?

----- Original message -----From: philippe-gregoire<EMAIL_ADDRESS>NodeREDWatson/Watson-Node-Red-Samples<EMAIL_ADDRESS>Matthew Taloni/Australia/IBM@IBMAUSubject: Re: [Watson-Node-Red-Samples] Problem with response HTML (#46)Date: Thu, Sep 24, 2015 7:32 PM
Hello Matt,I tried on my setup right now and it works (pasted the flow from this repository to make sure).
Only thing I can think of is that it may be an issue with service credentials, when running on bluemix, the service should be bound to the Node-RED application in BlueMix. This way, the credentials are automatically filled-in on the node:
One thing that I have not yet put upfront in the lab instructions is that the service should be bound to the Node-RED App. This is alluded to in the overall node-red labs, but we need to remind it in each lab I think.
BTW, are you getting any error message in the Node-RED log or console?
Thanks,
—Reply to this email directly or view it on GitHub.

I have added a note to the top level .md files for watson services and advanced labs .md to indicate that the Node-RED starter boilerplate is assumed to be used for all labs, also included link to introduction to node-RED lab which documents this anyway


Key error when exporting

Description
add a human readable error message when there is a key error on export
closes #3787
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

@sanderr I don't really now what to put as message for the RuntimeException and PluginException and how to test those.
Is it ok like this?

@sanderr I don't really know what to put as message for the RuntimeException and PluginException and how to test those. Is it ok like this?

I responded in a comment attached to those lines.

Processing this pull request

Failed to merge changes into iso4 due to merge conflict.Please open a pull request for these branches separately.

Merged into branches master in f9246f24b55a7045222b8be8c7c271af31e02b08

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches. You can safely close this pull request and delete the source branch.

Processing #3934.


Update Cards Dynamically

I want to update cards dynamically based on the response from an API that i've made to update the contents of the card. I've created a function that onSwiped will call the API and a request is sent to the API to fetch the data for the new card. This is what the function looks like.
fetchNextCardDetails = async () => {
   const response = await fetch("<IP_ADDRESS>:5000/get-next-card-details")
   const json = await response.json();
   this.setState({ dataNextCard : json });
}

I understand that i need to update a key in the card component to be able to render a new card with the new data. Now since i am getting the data from an API, how should i update the key? Can the key be any random number or does it have to be in a sequence. Each card contains information about a new place, which is obtained from google's places API, which is then sent to the react-native app. Can i use the place_id that i get from Google as a key instead of numbers?
Fairly new with react-native needed help with my first app.

You can just append the new card att the end of your list with cards
 {cards.map((card, index) => (             <Card key={card} style={[styles.card]}>               <Text style={styles.label}>{card}</Text>             </Card> ))} </CardStack>
addCard = () => {     const { cards } = this.state;     cards.push('New card')     this.setState({ cards })   }


Ios push notifications not working

I have been implementing push notifications for a Xamarin app I have written with Plugin.FirebasePushNotification in Android all works as expected but in IOS the OnNotificationReceived is not triggered.
I have an Apple developer account.
I have downloaded GoogleService-Info.plist
I have configured the Info.plist to enable Background Modes and Remote notifications and set FirebaseAppDelegateProxyEnabled to no.
I have added a certificate to the Bundle.
And still, when I send the message using postman
{
"registration_ids": ["My device registration id"],
"aps" : {
"alert" : {
"body" : "great match!",
"title" : "Portugal vs. Denmark",
"content_available": 2,
"priority":"high"
},
"badge" : 1
}
}
I get success in postman but nothing in the device.
Any assistance will be much appreciated.

Not sure if you are still having this issue, I have been looking at it for days, found this
https://www.youtube.com/watch?v=GNBuaAB8nR8
I needed to get a certificate from my apple developer account which I imported into FCM console, now push notifications work.
It seems a step that is missing from the getting started guide for later versions of ios


Comments trigger auto-complete.

Godot version:

dbb0ad3b5
OS/device including version:

Win10 64-bit
Issue description:

When typing comments, auto-complete hints keep appearing.
From testing it seems to be a regression from 3.2.2.

Steps to reproduce:
Start a comment in the build at the commit above.  Continue typing.
Minimal reproduction project:

None needed.

Fixed by #41451.


Update github README with latest documentation

Currently the github README is not up to date.
It would be nice to have this updated with the latest documentation from here so one could just get setup with the README.

The readme should not get to big. For details we should always refer to the main docs https://docs.human-connection.org/nitro/
But it should be very clear so everyone can get started quickly.

I'll take over this.
Anyway it was and is planned already, so i'll close this issue.

@Lulalaby what do you mean with it’s planned already? Do you have some reference?

I talked with @roschaefer that i'll enhance some things like the documentation, the readme and other things.

@Lulalaby try to be more specific, people don't know what we talked about.
Actually I don't even know what you mean :thinking: what did we talk about?


Enable-disable dolby vision in setting

Marcel can you please make switch in setting disable-enable dolby vision?
I have nvidia shield 2019 pro with dolby vision, tv sony without dolby vision, some movies with dolby vision and hdr10 can't switch to hdr mode on my tv. For example  this setting appeared in vimu player and when i disable dolby vision i can watch movie with hdr10 because my tv switch to hdr mode
I don't know how it happens but it works.
Thank you for this great player.

I will add option to allow playback of DV profile 7 videos as HDR/HEVC.

Duplicate of https://github.com/moneytoo/Player/issues/270. Is this about DV profile 7 or some other profile?

I'll answer it here.
Apparently what we're trying to play are Dual Layer.
This is a quote from makemkv website, hope it helps.
All UHD discs use Dolby Vision Profile 7, which is dual layer. The first, base layer is standard HDR10. The second layer is known as the "Enhancement layer." Enhancement Layers come in two varieties. Some titles use a so-called "Full Enhancement Layer" aka FEL. A FEL contains dynamic tone mapping metadata (aka "RPU"), as well as residual information that boosts the video bit depth from 10 to 12 bit. Other titles use a so-called "Minimum Enhancement Layer" aka MEL. A MEL only contains the RPU and does not contain any residual information.
The current version of MakeMKV creates .mkv files that retain all of the information stored in the Dolby Vision Enhancement Layer. However, few players are capable of playing back the Enhancement Layer, and even fewer players are capable of decoding the residual color information contained in a FEL.

Available in v0.126.


bug: IonActionSheet uses non-standard cssClass instead of className

Bug Report
Ionic version:

[x] 4.x
Current behavior:

Attempting to do: <IonActionSheet ... className="dark" /> throws a TypeScript error:
Property 'className' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<{ overlay?: HTMLIonActionSheetElement | undefined; el: HTMLDivElement; componentDidMount(): void; componentWillUnmount(): void; componentDidUpdate(prevProps: ActionSheetOptions & ReactOverlayProps): Promise<...>; ... 7 more ...; refs: { ...; }; }> & Readonly<...> & Read...'.  TS2322

Expected behavior:

The className "dark" should be added to my action sheet.
Ionic info:

Ionic:

   Ionic CLI       : 5.4.4
   Ionic Framework : @ionic/react 4.11.3

Capacitor:

   Capacitor CLI   : 1.2.1
   @capacitor/core : 1.2.1

Utility:

   cordova-res : not installed
   native-run  : not installed

System:

   NodeJS : v12.11.0
   npm    : 6.11.3
   OS     : macOS Mojave

If I open up Dev Tools and added the class name manually it behaves as desired.

I found cssClass in the docs. Any reason to use a different prop name than the rest of the components?

Hi @schontz,
Yes, its a bit complicated, but using className doesn't work because there is no actual html rendered until the action sheet is shown. Once the isOpen is set to true, the ionic core components add the modal to the DOM, and then remove it when isOpen goes to false. The cssClass is used to pass any custom classes you want to the element.
It might be possible to just pass whatever is set in the className prop to cssClass, which would certainly avoid confusion like this. I'll investigate that some more and leave this issue open in the meantime.
Thanks!


support specifying extra attributes for a tags

Is your feature request related to a problem? Please describe.
If I try to go to my self-hosted qBittorrent instance through Hajimari, I get hit with an "unauthorized" due to the CSRF protection of qBittorrent. More specifically, because of the requirement that the Referer and Target headers must be the same:
(W) 2022-09-28T09:47:04 - WebUI: Referer header & Target origin mismatch! Source IP: '::ffff:<IP_ADDRESS>'. Referer header: 'https://lab.invak.id/'. Target origin: 'qbit.lab.invak.id'

Note: lab.invak.id is Hajimari, and qbit.lab.invak.id is my qBittorrent instance.
Describe the solution you'd like
I'd like to have a way of specifying rel="noreferrer" on the link. Speaking more generally, I think it makes sense to have a way to add extra attributes to the a tags. For example, it could be useful for opening links in a new tab (target="_blank") as well.
Describe alternatives you've considered
For my specific case, an alternative would be to disable the CSRF protection of qBittorrent. Still, I'm not really a fan of the idea of deliberately reducing security settings in order to be able to have my qBittorrent instance bookmarked. And I do think that my feature request would be useful in the general case as well.
Additional context
FWIW, here are my full Hajimari manifests: link to my home cluster repo

@toboshii
I was working on a PR to add the ability to change the link target for the a tags with a boolean ("" or "_blank" depending on the value), but I can pivot and add an annotation to add arbitrary html code to the app.url links and cover this issue if you prefer that solution.
If so, any preferences for the naming of the annotation?
Other option is to make both these use-cases boolean toggles or strings rather than allow arbitrary html code.

From my testing adding rel="noopener noreferrer" makes no difference on fixing the qBittorrent CSRF issue, unless you also include target="_blank" (in Firefox at least).
I'm a little against end users being able to inject random attributes into html unless there's a really good reason so I'm leaning more towards a simple boolean that toggles target="_blank" rel="noopener noreferrer". According to several of the links and comments here, most if not all modern browsers automatically include noopener on any blank targets, and noreferrer includes the functionality of noopener, but no harm in including  both just to be sure.
That is unless someone has some really good use cases for other anchor attributes, or a valid use case where always including noreferrer on a blank target is an issue.
As far as configuration and naming I'd like to see an annotation (perhaps hajimari.io/targetBlank?) that controls it per app, as well as a global toggle (linksTargetBlank?) that affects all app and bookmark links. Open to any suggestions here though.

Odd, rel="noreferrer" seems to be enough on my end in both Vivaldi and Firefox:
https://user-images.githubusercontent.com/38114607/193315852-9be6c252-61c5-41ae-b4ae-2179c97f56a6.mp4
Could it be caused by some difference in our configs?

I agree that random html could be iffy, no telling what could break and it is not a great security practice.
Initially I started out allowing different targets but I saw that the functionality had been deprecated in HTML5, only "" or _blank are valid options going forward.

Adding  linksTargetBlank, defaulting to false in order to not change current behavior.
Apps and Bookmarks get a targetBlank attribute that will override the global default.
When set to true it adds target="_blank" rel="noopener noreferrer" to the app/bookmark a tags.

Or alternatively we split the targetBlank from the noreferrer thing in case someone needs the granularity?

I personally would like a bit more granularity than a single annotation that toggles both target="_blank" and rel="noopener noreferrer", I think it makes sense to have two separate annotations at the very least, as I personally only need the latter and I'd prefer if my links still open in the same tab, considering it works fine for me (and for plenty of other people as well I'd assume).

Is there a drawback to adding noopener noreferrer to the links by default?

I saw you added the noreferrer by default so I created a PR for just the targetBlank option - #49

Odd, rel="noreferrer" seems to be enough on my end in both Vivaldi and Firefox:

Ah, thanks for confirming, may be something to do with me having Authelia in the mix.

Is there a drawback to adding noopener noreferrer to the links by default?

Yea I can't think of a scenario where having these as default breaks something, so lets just have it default and we can add a flag later if someone reports a problem.

Added in #44

@toboshii now that there's a release of the Svelte version and I could test it properly, I can see why you said that rel="noreferrer" does nothing: because it actually doesn't. The detail we overlooked is that SvelteKit's client-side router gets in the way. The fix is basically to add rel="external" as well, which effectively disables the SvelteKit client-side router for those anchor tags. I've opened a PR with the fix: https://github.com/toboshii/hajimari/pull/50


Create A Readme ( TicTacToe - JS )

Location of the Document
You have to create a Readme for TicTacToe
What needs to be added
Create and Add details about the game.

Assign this to me.

This issue has been resolved.


Saga Edition compatability? / Make parts of module system independent?

I play Saga Edition and there are functions of the mod like the intro creator, transitions, and the bounties + datapad entries that I think could be made system independent without much difficulty. In addition, the shop generator, the attack animations, the renamer, and the status adder could probably be re-targeted for Saga equivalents without being too crazy.

Feel free to rip code out and port it to another module. This one is designed specifically for the FFG system, though - sorry, I simply don't have the time to rewrite it to be generic.


Remove my app as my income is not based on it

To be honest after reading the whole Readme, this is my indie app, but my income is not based on it as I have a separate job. Therefore I think it's unfair to get it promoted here when others are struggling with them.
However, I'll still help others to get promotion! Apologies and thanks for this initiative!

No need to apologize @joamafer, thanks for for being so open and honest about that 🙂 Wish you best of luck with your app regardless 👍


Grpc.Tools fails when used in a .NET Core 3.0 WPF project

Copied from https://github.com/grpc/grpc-dotnet/issues/488.
Moved here because the issue is inside Grpc.Tools. Code generation is not working correctly when used in a .NET Core 3.0 WPF project. WPF projects have unusual build steps (I think it involves multiple compilations), and that is causing Grpc.Tools to fail.

What version of gRPC and what language are you using?

C#

I use following packages.

Google.Protobuf 3.9.1
Grpc.Net.Client 0.1.22-pre3
Grpc.Tools 2.23.0

What operating system (Linux, Windows,...) and version?

Windows 10

What runtime / compiler are you using (e.g. python version or version of gcc)

WPF on .NET Core 3.0 (.NET Core 3.0.100-preview8-013656)

What did you do?
I just create a simple .proto file, and generate C# code.
When use the generated code on WPF on .NET Core project, then compile errors is occurred.
On Console App on .NET Core project, there is no compile error.
What did you expect to see?
No compile error.
What did you see instead?
Following message:
> dotnet build
Microsoft (R) Build Engine version 16.3.0-preview-19377-01+dd8019d9e for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 51.27 ms for C:\Users\k_ota\source\repos\GrpcErrorRepro\WpfApp\WpfApp.csproj.
  You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
MainWindow.xaml.cs(35,55): error CS0246: The type or namespace name 'MyGrpcServices' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\k_ota\source\repos\GrpcErrorRepro\WpfApp\WpfApp_v4a1l2r4_wpftmp.csproj]
MainWindow.xaml.cs(36,47): error CS0246: The type or namespace name 'MyGrpcServices' could not be found (are you missing a using directive or an assembly reBuild FAILED.

MainWindow.xaml.cs(35,55): error CS0246: The type or namespace name 'MyGrpcServices' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\k_ota\source\repos\GrpcErrorRepro\WpfApp\WpfApp_v4a1l2r4_wpftmp.csproj]
MainWindow.xaml.cs(36,47): error CS0246: The type or namespace name 'MyGrpcServices' could not be found (are you missing a using directive or an assembly reference?) [C:\Users\k_ota\source\repos\GrpcErrorRepro\WpfApp\WpfApp_v4a1l2r4_wpftmp.csproj]
    0 Warning(s)
    2 Error(s)

Anything else we should know about your project / environment?
This is a sample project:
https://github.com/runceel/GrpcErrorRepro

FYI, if you update all the packages to the latest versions then you'll need to update the gRPC client code because of changes since the preview.
Update it to the following to avoid a compilation error:
public async void HelloWorldButton_Click(object sender, RoutedEventArgs args)
{
    var c = Grpc.Net.Client.GrpcChannel.ForAddress("https://example.com");
    var s = new MyGrpcServices.HelloWorldService.HelloWorldServiceClient(c);
    var r = await s.SayHelloAsync(new MyGrpcServices.HelloWorldRequest { Name = "xxx" });
    MessageBox.Show(r.Message);
}

CC @kkm000

I have talked with the WPF folks about this issue and there is no way to fix it in Grpc.Tooling. The fix has to be made inside the WPF build process.
Workaround:
Move code generation with proto files to a regular class library. You can then reference the class library from the WPF app and use the generated types inside it.

@itshemant09, @ghord, /cc @jtattermusch, my apologies again for keeping my issues open for such long a time (not this one--my luck spared me this time--but there is limited supply of this rare stuff in the Universe). But being a senior SWE+scientist+IT planner+everything else in a startup-size company is really a feat to pull. I understand that ever postponed promises do not really cut it, real fixed do, and I am doing my best to carve off a week to work on my piling gRPC issues uninterrupted. I do remember of them (holy guacamole, and it does not help that I need to finish my taxes by October 15, too--all I had time for back in April is file for an extension!). We are dogfooding NuGet packages on the C# client size, but our C++ servers have not been upgraded since gRPC 1.6.7 (and I think that was the only upgrade since gRPC was in alpha... :))
I am so glad we are being helped by @JunTaoLuo and other guys from MS--thank you folk for your attention.
This is a note mostly to confirm I'm still around, read every new issue, and do feel responsible for them.