text:
ADBDEV-4349: gplogfilter: fix timerange validation

Here are some reminders before you submit the pull request

[ ] Add tests for the change
[ ] Document changes
[ ] Communicate in the mailing list if needed
[ ] Pass make installcheck
[ ] Review a PR in return to support the community

Allure report https://allure-ee.adsw.io/launch/55418

Allure report https://allure-ee.adsw.io/launch/55453

Allure report https://allure-ee.adsw.io/launch/55472

Allure report https://allure-ee.adsw.io/launch/55599

To reproduce you may run next steps:
Cleanup the $MASTER_DATA_DIRECTORY/pg_log from .csv logs (only save gp_era, startup.log)
and run next scirpt to generate test-data from parent issue
declare -x temp_dir=$(mktemp -d)
mkdir $temp_dir/pg_log
export MASTER_DATA_DIRECTORY=$temp_dir
declare -a test_data=(
     gpdb-2023-07-19_000000.csv
     gpdb-2023-08-04_000000.csv
     gpdb-2023-08-07_000000.csv
     gpdb-2023-09-21_045815.csv
     gpdb-2023-09-21_045857.csv
     gpdb-2023-09-21_045901.csv
     gpdb-2023-09-21_050845.csv
     gpdb-2023-09-21_050847.csv
     gpdb-2023-09-21_050913.csv
     gpdb-2023-09-21_050915.csv
     gpdb-2023-09-21_053026.csv
     gpdb-2023-09-21_053028.csv
 )

 touch $MASTER_DATA_DIRECTORY/pg_log/gp_era
 touch $MASTER_DATA_DIRECTORY/pg_log/status.log
 for i in "${test_data[@]}"
 do
     touch $MASTER_DATA_DIRECTORY/pg_log/$i
 done

 # command from a parent issue, but with changed pattern
 gplogfilter -b "2023-09-21 00:00" -e "2023-09-21 20:00" -f '$USER'

On the master build the output is next:
  requested timestamp range from 2023-09-21 00:00:00 to 2023-09-21 20:00:00
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_053026.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_045857.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_050915.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_045901.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_050913.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_053028.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-08-04_000000.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-08-07_000000.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-07-19_000000.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_045815.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_050845.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_050847.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries

As we can see all files were processed, while next files doesn't match interval (gpdb-2023-07-19_000000.csv, gpdb-2023-08-04_000000.csv, gpdb-2023-08-07_000000.csv)
With current version it gives the next result:
requested timestamp range from 2023-09-21 00:00:00 to 2023-09-21 20:00:00
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_053026.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_045857.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_050915.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_045901.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_050913.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_053028.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
SKIP file: /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-08-04_000000.csv
SKIP file: /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-08-07_000000.csv
SKIP file: /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-07-19_000000.csv
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_045815.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_050845.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /tmp/tmp.HC73LCNBCk/pg_log/gpdb-2023-09-21_050847.csv ----------
      in:       0 lines,       0 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries

Seems current approach is not valid
Suppose, we have such log files in the MASTER_DATA_DIRECTORY:
-rw------- 1 imber imber 12546 Oct  2 21:25 gpdb-2023-10-02_212448.csv
-rw------- 1 imber imber  9095 Oct  2 21:25 gpdb-2023-10-02_212522.csv
-rw------- 1 imber imber 22802 Oct  3 08:46 gpdb-2023-10-02_212526.csv
-rw------- 1 imber imber 30387 Oct  3 09:48 gpdb-2023-10-03_000000.csv
-rw------- 1 imber imber  8898 Oct  3 09:48 gpdb-2023-10-03_094847.csv
-rw------- 1 imber imber 12522 Oct  3 10:04 gpdb-2023-10-03_094852.csv
-rw------- 1 imber imber  8863 Oct  3 10:05 gpdb-2023-10-03_100511.csv
-rw------- 1 imber imber  4197 Oct  3 10:05 gpdb-2023-10-03_100515.csv
-r-------- 1 imber imber   105 Oct  3 10:05 gp_era
-rw------- 1 imber imber  1676 Oct  3 10:05 startup.log

The gpdb-2023-10-03_000000.csv contains log entreis from 00:00 until 9:48, but the next command won't process it:
gplogfilter -b "2023-10-03 09:00" -e "2023-10-03 23:00" -f 'noting'

It's output:
requested timestamp range from 2023-10-03 09:00:00 to 2023-10-03 23:00:00
SKIP file: /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/gpdb-2023-10-02_212522.csv
----------  /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/gpdb-2023-10-03_100511.csv ----------
       in:      35 lines,      35 log entries; timestamps from 2023-10-03 10:05:11.164532 to 2023-10-03 10:05:12.672553
  time ok:      35 lines,      35 log entries; timestamps from 2023-10-03 10:05:11.164532 to 2023-10-03 10:05:12.672553
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/gpdb-2023-10-03_094847.csv ----------
       in:      35 lines,      35 log entries; timestamps from 2023-10-03 09:48:47.572302 to 2023-10-03 09:48:49.093229
  time ok:      35 lines,      35 log entries; timestamps from 2023-10-03 09:48:47.572302 to 2023-10-03 09:48:49.093229
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/gp_era ----------
       in:       3 lines,       1 log entries; no timestamps found
  time ok:       0 lines
    match:       0 lines
      out:       0 lines,       0 log entries
SKIP file: /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/gpdb-2023-10-02_212448.csv
----------  /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/gpdb-2023-10-03_100515.csv ----------
       in:      18 lines,      18 log entries; timestamps from 2023-10-03 10:05:16.000502 to 2023-10-03 10:05:17.073308
  time ok:      18 lines,      18 log entries; timestamps from 2023-10-03 10:05:16.000502 to 2023-10-03 10:05:17.073308
    match:       0 lines
      out:       0 lines,       0 log entries
----------  /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/startup.log ----------
       in:       7 lines,       7 log entries; timestamps from 2023-10-02 21:24:48.768287 to 2023-10-03 10:05:15.997601
  time ok:       4 lines,       4 log entries; timestamps from 2023-10-03 09:48:47.570313 to 2023-10-03 10:05:15.997601
    match:       0 lines
      out:       0 lines,       0 log entries
SKIP file: /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/gpdb-2023-10-02_212526.csv
SKIP file: /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/gpdb-2023-10-03_000000.csv
----------  /home/imber/Projects/arenadata/gpdb_src/gpAux/gpdemo/datadirs/qddir/demoDataDir-1/pg_log/gpdb-2023-10-03_094852.csv ----------
       in:      50 lines,      50 log entries; timestamps from 2023-10-03 09:48:52.369434 to 2023-10-03 10:04:57.089126
  time ok:      50 lines,      50 log entries; timestamps from 2023-10-03 09:48:52.369434 to 2023-10-03 10:04:57.089126
    match:       0 lines
      out:       0 lines,       0 log entries

As we can see file gpdb-2023-10-03_000000.csv is skipped, but it have the interesting log entreis for us. Seems it's not correct to filter-out files with name which doesn't inside an interval, seems we should order them by timestamp and include files to process which is before begin date bound and after the end date bound.

Failed job Build for x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/682736

Failed job Build for ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/682737

Allure report https://allure-ee.adsw.io/launch/56214

Allure report https://allure-ee.adsw.io/launch/56240

Allure report https://allure-ee.adsw.io/launch/56280

Allure report https://allure-ee.adsw.io/launch/56421

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/698313

Allure report https://allure-ee.adsw.io/launch/56481

Allure report https://allure-ee.adsw.io/launch/56502

I've fixed the corner case, as a result there is a new patch.
Also here is more information about the begin and end range: gplogfilter creates an FilterLogEntries pipeline for the current file which is processing, where beginstamp and endstamp are user specified command arguments begin and end respectively. As it described the beginstamp is inclusive and endstamp is exclusive (also it described at TimestampInBounds function which is called from  FilterLogEntries)

Why did gplogfilter skip files gpdb-2023-07-19_000000 and gpdb-2023-08-04_000000 and not skip file gpdb-2023-08-07_000000? Files with non-zero time are processed correctly.

Dates of log files with time stamps (gpdb-timestamp.csv) are discrete. Under the normal conditions (log_rotation_age GUC is set to 1 day, and there was no restrat of cluster) the pg_log directory would contain log files, which covers daily operations, for ex: gpdb-2023-01-01_000000 would contain the log entries for this day (time since 00:00:00 23:59:59). But there there is no guarantee that there was no restarts, or the GUC value wasn't changed. Thus we should always process all files that are inside the specified begin and end range plus file which log date is the nearest to the begin date in the ordered array by date of log file with time stamp. As a result the gpdb-2023-08-07_000000 file wasn't skipped.
that is before)

Allure report https://allure-ee.adsw.io/launch/56846

Allure report https://allure-ee.adsw.io/launch/56922

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/719177

Allure report https://allure-ee.adsw.io/launch/57009

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/719734

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/719735

Allure report https://allure-ee.adsw.io/launch/57024

Failed job Regression tests with Postgres on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/720626

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/720634

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/720635

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/721300

authors: BenderArenadata HustonMmmavr

repo: arenadata/gpdb


text:
chore:update operator-sdk and kubebuilder version to match sibling gitops/argocd-operators

Fixes #77

JIRA

source: gharchive/pull-request

repo: argoproj-labs/argo-rollouts-manager

license_type: permissive

license_source: github-api


text:
Add retry policy

c.p. https://github.com/argoproj-labs/hera-workflows/pull/116
More info: https://argoproj.github.io/argo-workflows/retries/#retry-policies

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@flaviuvadan would you mind taking a look at this?

authors: CLAassistant dmerrick

repo: argoproj-labs/hera-workflows


text:
Save dummy outputs when runner script raises an exception

Pull Request Checklist

[x] Fixes #948
[x] Tests added
[ ] Documentation/examples added
[x] Good commit messages and/or PR title

Description of PR
When running a script via the Hera Runner, if it raises an error, the declared outputs of the (script) template are not created as files in the container, leading to confusing Argo logs such as:
msg="cannot save parameter /tmp/hera-outputs/parameters/my-parameter"
argo=true
error="open /tmp/hera-outputs/parameters/my-parameter: no such file or directory"`

This PR makes the runner catch the exception, write dummy values, then pass the exception up.

JFYI - This PR is on top of the Runner IO models to avoid redoing the work

repo: argoproj-labs/hera


text:
UI init/wait logs overwritten with "no artifact logs are available" after pod deleted

you run any workflow, click on the logs button in the ui, select init container, it shows those logs, but then once pod dies the logs are no longer visible and "no artifact logs are available" error appears. i think the react ui could be made to not overwrite the log display if you already had it open (i understand anyone clicking the links for the first time after pod died, should still see the error)
pseudocode:
before fetching next set of logs, preserve current logs in memory
if next set of logs is unavailable then display what is in memory

This due to logs from init/wait are not archived.
More discussion here https://github.com/argoproj/argo-workflows/issues/12640

source: gharchive/issue

repo: argoproj/argo-workflows


text:
feat(controller): Store artifact repository in workflow status. Fixes #6255

Signed-off-by: Alex Collins alex_collins@intuit.com
Fixes #6255
Changes:

Store the artifact repository in the workflow status.
We don't need to to a Get configmap for each reconciliation (up to 50% reduction in requests).
Clients can use the field to find the resource.
If the underlying configuration changes, you can still look up the value.

Example:
  status:
    artifactRepositoryRef:
      artifactRepository:
        archiveLogs: true
        s3:
          accessKeySecret:
            key: accesskey
            name: my-minio-cred
          bucket: my-bucket
          endpoint: minio:9000
          insecure: true
          secretKeySecret:
            key: secretkey
            name: my-minio-cred
      configMap: artifact-repositories
      key: default-v1
      namespace: argo
    conditions:
    - status: "True"
      type: PodRunning
    finishedAt: null
    offloadNodeStatusVersion: fnv:1056331912
    phase: Running
    progress: 0/1
    startedAt: "2021-07-07T22:48:59Z"

Thank you! This is exactly what we wanted in #6255.
Several side effects that come with the change seems ideal for argo itself too (perf improvement, stable handling of artifact repository config change).

@jessesuen I need your review on the proto changes for this v3.1 fix. It is to enable Kubeflow Pipelines to use v3.1.

authors: Bobgy alexec


text:
Latest go version, implement go modules

Purpose
Addresses #1375 add support for go modules.

Update to latest go version in docker container
Convert go dep to go modules
Move build outside of go path for go modules compatibility
Update docs to remove go dep references

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant wesmcouch

repo: argoproj/argo


text:
feat: instanceID support for argo server. Closes #2004

Closes #2004
Make Argo server behaves the same as workflow controller:

Argo server only manages the workflows/CronWorkflows with the same instanceID (label xxxx/controller-instanceid), or wfs/cronWfs without instanceID, depends on if instanceID is configured in the ConfigMap.

argo cli without ARGO_SERVER ENV goes through kube api, argo list or argo cron list can see all the results. argo submit or argo cron create needs to give --instanceid=xxxx to create wf/cronWf targeting a specific controller.

argo cli with ARGO_SERVER ENV uses argo server, results of argo list and argo cron list might be different, depends on instanceID configuration in the ConfigMap.  As a result, argo submit or argo cron create by default will include the instanceID in the labels if it's configured in the ConfigMap.

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] I have written unit and/or e2e tests for my change. PRs without these are unlike to be merged.
[ ] Optional. I've added My organization is added to the README.
[ ] I've signed the CLA and required builds are green.

@alexec - could you review it again?


text:
Demo page for MenuBar has strange overlap

Current behavior
Looks fine in my app, but JAHU on the demo.

Steps to reproduce the bug

Open https://ariakit.org/examples/menu-bar

Expected behavior
look right aligned to the bottom of menu button.
Possible solutions
.

Are you still using the touchscreen laptop with Windows 10 and Chrome 99? Are you able to try it on another device? I remember this issue was present in your screenshot on #1091, but I could never reproduce it. I have macOS, Windows, iPad, iPhone, and Android, but none of them have this issue.
@atomiks Do you think it could be related to Floating UI?

@diegohaz we never got reports of "overlapping" as seen in the screenshot in Popper and that was with a ton of usage

Are you still using the touchscreen laptop with Windows 10 and Chrome 99? Are you able to try it on another device? I remember this issue was present in your screenshot on #1091, but I could never reproduce it. I have all browsers on macOS, Windows 10/11 (on PC and Mac), iPad, iPhone, and Android, but none of them have this issue.
Here are a few things to try, if you can:

Anonymous tab (without extensions).
Different browser.
Different devices.

@atomiks Do you think it could be related to Floating UI/Popper.js?

Exact same look on Firefox, and Edge. I just verified on my other laptop and it DOES look fine.  Maybe it's this flash code renderer thing?

Maybe it's this flash code renderer thing?

What do you mean?

When I right click on your demo I get a notice about Flash. Really odd..

On Apr 23, 2022, at 3:04 PM, Haz @.***> wrote:

Maybe it's this flash code renderer thing?
What do you mean?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

That's weird. There's no Flash on the site.

I would think it’s some extension but I see the exact same in the three browsers and they are virgin

On Apr 23, 2022, at 4:11 PM, Haz @.***> wrote:

That's weird. There's no Flash on the site.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

@diegohaz If I right click anywhere on your demo page I get:

Really strange. I don’t have the problem I originally reported but I don’t even have to try to get that strange placement. It was perfect one release ago.
It’s just a Dell Inspiron laptop it does have a touchscreen but I am using a 4K monitor

On Apr 22, 2022, at 1:53 PM, James N @.***> wrote:

@diegohaz we never got reports of "overlapping" as seen in the screenshot in Popper and that was with a ton of usage
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

authors: atomiks diegohaz httpete

repo: ariakit/ariakit

license: MIT


text:
Got phantomjs (official 1.9.7) crashed repeatedly.

Operating system: Linux
0.0.0 Linux 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64
CPU: amd64
family 6 model 60 stepping 3
1 CPU
Crash reason:  SIGSEGV
Crash address: 0x29
Thread 0 (crashed)
0  0x7f1084704130
rbx = 0x00007f10ca875038   r12 = 0x0000000000000200
r13 = 0x00007f10ca875038   r14 = 0xffff000000000000
r15 = 0xffff000000000002   rip = 0x00007f1084704130
rsp = 0x00007fffa4c4f330   rbp = 0x00007fffa4c4f3d0
Found by: given as instruction pointer in context
1  libc-2.19.so + 0x3bf75f
rip = 0x00007f10cd3bd760   rsp = 0x00007fffa4c4f350
rbp = 0x00007fffa4c4f3d0
Found by: stack scanning
2  phantomjs!JSC::Interpreter::executeCall [JITCode.h : 77 + 0x16]
rip = 0x0000000000f2e376   rsp = 0x00007fffa4c4f3e0
Found by: stack scanning
3  phantomjs!JSC::call [CallData.cpp : 38 + 0x21]
rbx = 0x00007fffa4c4f610   r12 = 0x00007f10c85c0188
r13 = 0x00007f10c85cb1d0   r14 = 0x00007f10ce724150
r15 = 0x00007f10ce7638f0   rip = 0x0000000000f7291d
rsp = 0x00007fffa4c4f4b0   rbp = 0x00007f1041b8eb50
Found by: call frame info
4  phantomjs!JSC::Bindings::QtConnectionObject::execute [qt_runtime.cpp : 1863 + 0x17]
rbx = 0x00007fffa4c4f610   r12 = 0x00007f10c85c0188
r13 = 0x00007f10c85cb1d0   r14 = 0x00007f10ce724150
r15 = 0x00007f10ce7638f0   rip = 0x0000000000542ece
rsp = 0x00007fffa4c4f4c0   rbp = 0x00007f1041b8eb50
Found by: call frame info
5  phantomjs!JSC::Bindings::QtConnectionObject::qt_metacall [qt_runtime.cpp : 1807 + 0xa]
rbx = 0x0000000000000000   r12 = 0x00007fffa4c4f830
r13 = 0x0000000003c72050   r14 = 0x0000000000000004
r15 = 0x0000000003c6e6d0   rip = 0x000000000054390c
rsp = 0x00007fffa4c4f740   rbp = 0x0000000000000000
Found by: call frame info
6  phantomjs!QMetaObject::activate [qobject.cpp : 3555 + 0x1f]
rbx = 0x0000000000000004   r12 = 0x0000000003c68901
r13 = 0x0000000000000000   r14 = 0x0000000000000004
r15 = 0x0000000003c6e6d0   rip = 0x0000000001cf7160
rsp = 0x00007fffa4c4f770   rbp = 0x0000000003c72050
Found by: call frame info
7  phantomjs!WebPage::qt_static_metacall [moc_webpage.cpp : 208 + 0x4]
rbx = 0x0000000003c689e0   r12 = 0x0000000003c689e0
r13 = 0x0000000003999ab0   r14 = 0x0000000003997208
r15 = 0x0000000005348d80   rip = 0x000000000046aada
rsp = 0x00007fffa4c4f890   rbp = 0x0000000005875380
Found by: call frame info
8  phantomjs!QObject::event [qobject.cpp : 1191 + 0x8]
rbx = 0x0000000003c689e0   r12 = 0x0000000005348d80
r13 = 0x0000000003999ab0   r14 = 0x0000000003997208
r15 = 0x0000000005348d80   rip = 0x0000000001cefc28
rsp = 0x00007fffa4c4f9c0   rbp = 0x0000000000000000
Found by: call frame info
9  phantomjs!QApplicationPrivate::notify_helper [qapplication.cpp : 4562 + 0xc]
rbx = 0x00007fffa4c50370   r12 = 0x0000000005348d80
r13 = 0x0000000003999ab0   r14 = 0x0000000003997208
r15 = 0x0000000005348d80   rip = 0x00000000015decaf
rsp = 0x00007fffa4c4fb60   rbp = 0x0000000003c689e0
Found by: call frame info
10  phantomjs!QApplication::notify [qapplication.cpp : 4423 + 0x17]
rbx = 0x00007fffa4c50370   r12 = 0x0000000005348d80
r13 = 0x00007fffa4c50370   r14 = 0x0000000003997208
r15 = 0x0000000005348d80   rip = 0x00000000015e793b
rsp = 0x00007fffa4c4fb90   rbp = 0x0000000003c689e0
Found by: call frame info
11  phantomjs!QCoreApplication::notifyInternal [qcoreapplication.cpp : 946 + 0x2]
rbx = 0x00000000039971c0   r12 = 0x0000000005348d80
r13 = 0x00007fffa4c50370   r14 = 0x0000000003997208
r15 = 0x00000000039971fc   rip = 0x0000000001cde3d4
rsp = 0x00007fffa4c50060   rbp = 0x0000000003c689e0
Found by: call frame info
12  phantomjs!QCoreApplicationPrivate::sendPostedEvents [qcoreapplication.h : 231 + 0x1f]
rbx = 0x0000000005348d80   r12 = 0x00000000039971c0
r13 = 0x0000000003c689e0   r14 = 0x0000000003997208
r15 = 0x00000000039971fc   rip = 0x0000000001cdf334
rsp = 0x00007fffa4c500b0   rbp = 0x00000000052b3830
Found by: call frame info
13  phantomjs!QEventDispatcherUNIX::processEvents [qeventdispatcher_unix.cpp : 909 + 0xc]
rbx = 0x0000000003c772a0   r12 = 0x00007fffa4c501c0
r13 = 0x0000000003996560   r14 = 0x0000000000000000
r15 = 0x00000000039972d8   rip = 0x0000000001d08023
rsp = 0x00007fffa4c50170   rbp = 0x000000000399b030
Found by: call frame info
14  phantomjs!QEventDispatcherQPA::processEvents [qeventdispatcher_qpa.cpp : 246 + 0x4]
rbx = 0x0000000003c772a0   r12 = 0x0000000000000000
r13 = 0x0000000003996560   r14 = 0x00007fffa4c50200
r15 = 0x00000000039972d8   rip = 0x000000000163a6a4
rsp = 0x00007fffa4c501c0   rbp = 0x000000000399b030
Found by: call frame info
15  phantomjs!QEventLoop::processEvents [qeventloop.cpp : 149 + 0x1]
rbx = 0x0000000003c772a0   r12 = 0x00007fffa4c50290
r13 = 0x00007fffa4c502a0   r14 = 0x0000000003997230
r15 = 0x00000000039972d8   rip = 0x0000000001cdd4b5
rsp = 0x00007fffa4c50200   rbp = 0x00007fffa4c50240
Found by: call frame info
16  phantomjs!QEventLoop::exec [qeventloop.cpp : 200 + 0x4]
rbx = 0x0000000003c772a0   r12 = 0x00007fffa4c50290
r13 = 0x00007fffa4c502a0   r14 = 0x0000000003997230
r15 = 0x00000000039972d8   rip = 0x0000000001cdd918
rsp = 0x00007fffa4c50230   rbp = 0x00007fffa4c50370
Found by: call frame info
17  phantomjs!QCoreApplication::exec [qcoreapplication.cpp : 1218 + 0x4]
rbx = 0x00000000039971c0   r12 = 0x00007fffa4c50370
r13 = 0x00007fffa4c50528   r14 = 0x00007fffa4c502e0
r15 = 0x0000000000000000   rip = 0x0000000001cdf7cb
rsp = 0x00007fffa4c50290   rbp = 0x00000000039971c0
Found by: call frame info
18  phantomjs!main [main.cpp : 121 + 0x4]
rbx = 0x0000000003a0b0a0   r12 = 0x00007fffa4c50370
r13 = 0x00007fffa4c50528   r14 = 0x00007fffa4c502e0
r15 = 0x0000000000000000   rip = 0x0000000000427cb2
rsp = 0x00007fffa4c502d0   rbp = 0x00007fffa4c50508
Found by: call frame info
19  libc-2.19.so + 0x21ec4
rbx = 0x0000000000000000   r12 = 0x0000000000407cc0
r13 = 0x00007fffa4c50500   r14 = 0x0000000000000000
r15 = 0x0000000000000000   rip = 0x00007f10cd01fec5
rsp = 0x00007fffa4c50430   rbp = 0x0000000000000000
Found by: call frame info
20  phantomjs + 0x27a5f
rip = 0x0000000000427a60   rsp = 0x00007fffa4c50450
Found by: stack scanning
Thread 1
0  libc-2.19.so + 0xc1d8d
rbx = 0x00007f10cbc75c80   r12 = 0x00007f10cbc75d00
r13 = 0x00007f104140c090   r14 = 0x0000000002a7e1a0
r15 = 0x0000000002a7e170   rip = 0x00007f10cd0bfd8d
rsp = 0x00007f10cbc75c60   rbp = 0x00000000ffffffff
Found by: given as instruction pointer in context
1  libc-2.19.so + 0xc1c23
rip = 0x00007f10cd0bfc24   rsp = 0x00007f10cbc75c70
Found by: stack scanning
2  ld-2.19.so + 0xa990
rip = 0x00007f10ce6f7991   rsp = 0x00007f10cbc75d20
Found by: stack scanning
3  libc-2.19.so + 0xe89f
rip = 0x00007f10cd00c8a0   rsp = 0x00007f10cbc75d28
Found by: stack scanning
4  phantomjs + 0x18b5c6f
rip = 0x0000000001cb5c70   rsp = 0x00007f10cbc75d88
Found by: stack scanning
5  libc-2.19.so + 0x3d27
rip = 0x00007f10cd001d28   rsp = 0x00007f10cbc75d98
Found by: stack scanning
6  libc-2.19.so + 0xe89f
rip = 0x00007f10cd00c8a0   rsp = 0x00007f10cbc75da8
Found by: stack scanning
7  phantomjs!WebPage::renderPdf [qstring.h : 880 + 0xc]
rip = 0x00000000004173d8   rsp = 0x00007f10cbc75db0
Found by: stack scanning
Thread 2
0  libc-2.19.so + 0xf2cb3
rbx = 0x0000000000000000   r12 = 0x00007f10cb474db0
r13 = 0x0000000000000008   r14 = 0x00007f10c4000a98
r15 = 0x00007f10c4000d30   rip = 0x00007f10cd0f0cb3
rsp = 0x00007f10cb474b80   rbp = 0x00007f10c40008e0
Found by: given as instruction pointer in context
1  phantomjs!qt_safe_select [qcore_unix.cpp : 83 + 0x15]
rip = 0x0000000001d06327   rsp = 0x00007f10cb474b90
Found by: stack scanning
2  phantomjs!QEventDispatcherUNIXPrivate::doSelect [qeventdispatcher_unix.cpp : 223 + 0xd]
rbx = 0x00007f10c40012b0   r12 = 0x00007f10cb474db0
r13 = 0x00007f10c40008e0   r14 = 0x0000000000000000
r15 = 0x00007f10c4000d30   rip = 0x0000000001d075e7
rsp = 0x00007f10cb474c20   rbp = 0x00007f10c40008e0
Found by: call frame info
3  phantomjs!QEventDispatcherUNIX::processEvents [qeventdispatcher_unix.cpp : 937 + 0x4]
rbx = 0x00007f10c40012b0   r12 = 0x00007f10cb474db0
r13 = 0x00007f10c40008c0   r14 = 0x0000000000000001
r15 = 0x00000000039f1768   rip = 0x0000000001d08092
rsp = 0x00007f10cb474d60   rbp = 0x00007f10c40008e0
Found by: call frame info
4  phantomjs!QEventLoop::processEvents [qeventloop.cpp : 149 + 0x1]
rbx = 0x00007f10c40012b0   r12 = 0x00007f10cb474e40
r13 = 0x00007f10cb474e50   r14 = 0x0000000003997230
r15 = 0x00000000039f1768   rip = 0x0000000001cdd4b5
rsp = 0x00007f10cb474db0   rbp = 0x00007f10cb474df0
Found by: call frame info
5  phantomjs!QEventLoop::exec [qeventloop.cpp : 200 + 0x4]
rbx = 0x00007f10c40012b0   r12 = 0x00007f10cb474e40
r13 = 0x00007f10cb474e50   r14 = 0x0000000003997230
r15 = 0x00000000039f1768   rip = 0x0000000001cdd918
rsp = 0x00007f10cb474de0   rbp = 0x00007fffa4c50370
Found by: call frame info
6  phantomjs!QThread::exec [qthread.cpp : 542 + 0xc]
rbx = 0x00000000039f16e0   r12 = 0x00000000039f1768
r13 = 0x0000000000000001   r14 = 0x00007f10cb4759c0
r15 = 0x00007f10cb475700   rip = 0x0000000001bdfdf6
rsp = 0x00007f10cb474e40   rbp = 0x00000000039f1768
Found by: call frame info
7  phantomjs!QThreadPrivate::start [qthread_unix.cpp : 338 + 0x9]
rbx = 0x00000000039f1768   r12 = 0x00000000039ead60
r13 = 0x0000000000000001   r14 = 0x00007f10cb4759c0
r15 = 0x00007f10cb475700   rip = 0x0000000001be2cc2
rsp = 0x00007f10cb474e90   rbp = 0x00000000039e7070
Found by: call frame info
8  libpthread-2.19.so + 0x8181
rbx = 0x00007f10cb475700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f10cb4759c0
r15 = 0x00007f10cb475700   rip = 0x00007f10cdbec182
rsp = 0x00007f10cb474ee0   rbp = 0x0000000000000000
Found by: call frame info
9  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f10cb474f80
Found by: stack scanning
Thread 3
0  libc-2.19.so + 0xf2cb3
rbx = 0x0000000000000200   r12 = 0x0000000003c7ab30
r13 = 0x0000000003c7ac10   r14 = 0x0000000003c7b1a0
r15 = 0x00007f10ca707dd0   rip = 0x00007f10cd0f0cb3
rsp = 0x00007f10ca707db0   rbp = 0x0000000000000000
Found by: given as instruction pointer in context
1  phantomjs!master_thread [mongoose.c : 3981 + 0x4]
rip = 0x0000000000452136   rsp = 0x00007f10ca707dc0
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f10ca708700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f10ca7089c0
r15 = 0x00007f10ca708700   rip = 0x00007f10cdbec182
rsp = 0x00007f10ca707ee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f10ca707f80
Found by: stack scanning
Thread 4
0  libpthread-2.19.so + 0xc414
rbx = 0x0000000003c7b170   r12 = 0x00007f107c0008c8
r13 = 0x0000000003c7ab30   r14 = 0x00007f10c9f079c0
r15 = 0x0000000003c7ac10   rip = 0x00007f10cdbf0414
rsp = 0x00007f10c9f04a20   rbp = 0x00007f107c0008c0
Found by: given as instruction pointer in context
1  phantomjs!worker_thread [mongoose.c : 3852 + 0xa]
rip = 0x00000000004526d8   rsp = 0x00007f10c9f04a50
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f10c9f07700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f10c9f079c0
r15 = 0x00007f10c9f07700   rip = 0x00007f10cdbec182
rsp = 0x00007f10c9f06ee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f10c9f06f80
Found by: stack scanning
Thread 5
0  libpthread-2.19.so + 0xc414
rbx = 0x00007f1080005860   r12 = 0x004189374bc6a7ef
r13 = 0xffffffffffffffff   r14 = 0x00007f1080005888
r15 = 0x00007f1080004ea0   rip = 0x00007f10cdbf0414
rsp = 0x00007f10c9700010   rbp = 0x00007f1080004ea0
Found by: given as instruction pointer in context
1  phantomjs!QWaitCondition::wait [qwaitcondition_unix.cpp : 86 + 0xa]
rip = 0x0000000001be39f5   rsp = 0x00007f10c9700040
Found by: stack scanning
2  phantomjs!QSemaphore::acquire [qsemaphore.cpp : 144 + 0x7]
rbx = 0x00007f1080004ea0   r12 = 0x00007f10c9700380
r13 = 0x00007f1080004ea1   r14 = 0x0000000000000001
r15 = 0x00007f10c9700380   rip = 0x0000000001bdeb2d
rsp = 0x00007f10c97000c0   rbp = 0x00007f1080004ea0
Found by: call frame info
3  phantomjs!WebServer::handleRequest [webserver.cpp : 257 + 0xc]
rbx = 0x00007f10c9700280   r12 = 0x0000000003c619d0
r13 = 0x00007f10c9700180   r14 = 0x0000000003c619d8
r15 = 0x00007f10c9700380   rip = 0x000000000042520c
rsp = 0x00007f10c97000f0   rbp = 0x0000000003c619d1
Found by: call frame info
4  phantomjs!callback [webserver.cpp : 87 + 0xc]
rbx = 0x0000000003c619b0   r12 = 0x0000000000000000
r13 = 0x00007f10800008c0   r14 = 0x00007f10800008c8
r15 = 0x00007f10c9702900   rip = 0x00000000004265f4
rsp = 0x00007f10c9700880   rbp = 0x0000000003c7ab30
Found by: call frame info
5  phantomjs!handle_request [mongoose.c : 3245 + 0x9]
rbx = 0x00007f10c9701900   r12 = 0x0000000000000000
r13 = 0x00007f10800008c0   r14 = 0x00007f10800008c8
r15 = 0x00007f10c9702900   rip = 0x0000000000451086
rsp = 0x00007f10c9700890   rbp = 0x0000000003c7ab30
Found by: call frame info
6  phantomjs!worker_thread [mongoose.c : 3836 + 0x7]
rbx = 0x00007f10c9705e90   r12 = 0x00007f10800008c8
r13 = 0x0000000003c7ab30   r14 = 0x00007f10c97069c0
r15 = 0x0000000003c7ac10   rip = 0x0000000000452f91
rsp = 0x00007f10c9703a50   rbp = 0x00007f10800008c0
Found by: call frame info
7  libpthread-2.19.so + 0x8181
rbx = 0x00007f10c9706700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f10c97069c0
r15 = 0x00007f10c9706700   rip = 0x00007f10cdbec182
rsp = 0x00007f10c9705ee0   rbp = 0x0000000000000000
Found by: call frame info
8  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f10c9705f80
Found by: stack scanning
Thread 6
0  libpthread-2.19.so + 0xc414
rbx = 0x0000000003c7b170   r12 = 0x0000000000000000
r13 = 0x0000000003c7ab30   r14 = 0x00007f10c8f059c0
r15 = 0x0000000003c7ac10   rip = 0x00007f10cdbf0414
rsp = 0x00007f10c8f02a20   rbp = 0x00007f106c0008c0
Found by: given as instruction pointer in context
1  phantomjs!worker_thread [mongoose.c : 3852 + 0xa]
rip = 0x00000000004526d8   rsp = 0x00007f10c8f02a50
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f10c8f05700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f10c8f059c0
r15 = 0x00007f10c8f05700   rip = 0x00007f10cdbec182
rsp = 0x00007f10c8f04ee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f10c8f04f80
Found by: stack scanning
Thread 7
0  libpthread-2.19.so + 0xc414
rbx = 0x0000000003c7b170   r12 = 0x0000000000000000
r13 = 0x0000000003c7ab30   r14 = 0x00007f107bfff9c0
r15 = 0x0000000003c7ac10   rip = 0x00007f10cdbf0414
rsp = 0x00007f107bffca20   rbp = 0x00007f10740008c0
Found by: given as instruction pointer in context
1  phantomjs!worker_thread [mongoose.c : 3852 + 0xa]
rip = 0x00000000004526d8   rsp = 0x00007f107bffca50
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f107bfff700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f107bfff9c0
r15 = 0x00007f107bfff700   rip = 0x00007f10cdbec182
rsp = 0x00007f107bffeee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f107bffef80
Found by: stack scanning
Thread 8
0  libpthread-2.19.so + 0xc414
rbx = 0x0000000003c7b170   r12 = 0x0000000000000000
r13 = 0x0000000003c7ab30   r14 = 0x00007f107b7fe9c0
r15 = 0x0000000003c7ac10   rip = 0x00007f10cdbf0414
rsp = 0x00007f107b7fba20   rbp = 0x00007f10640008c0
Found by: given as instruction pointer in context
1  phantomjs!worker_thread [mongoose.c : 3852 + 0xa]
rip = 0x00000000004526d8   rsp = 0x00007f107b7fba50
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f107b7fe700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f107b7fe9c0
r15 = 0x00007f107b7fe700   rip = 0x00007f10cdbec182
rsp = 0x00007f107b7fdee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f107b7fdf80
Found by: stack scanning
Thread 9
0  libpthread-2.19.so + 0xc414
rbx = 0x0000000003c7b170   r12 = 0x0000000000000000
r13 = 0x0000000003c7ab30   r14 = 0x00007f1072ffd9c0
r15 = 0x0000000003c7ac10   rip = 0x00007f10cdbf0414
rsp = 0x00007f1072ffaa20   rbp = 0x00007f105c0008c0
Found by: given as instruction pointer in context
1  phantomjs!worker_thread [mongoose.c : 3852 + 0xa]
rip = 0x00000000004526d8   rsp = 0x00007f1072ffaa50
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f1072ffd700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f1072ffd9c0
r15 = 0x00007f1072ffd700   rip = 0x00007f10cdbec182
rsp = 0x00007f1072ffcee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f1072ffcf80
Found by: stack scanning
Thread 10
0  libpthread-2.19.so + 0xc414
rbx = 0x0000000003c7b170   r12 = 0x0000000000000000
r13 = 0x0000000003c7ab30   r14 = 0x00007f107affd9c0
r15 = 0x0000000003c7ac10   rip = 0x00007f10cdbf0414
rsp = 0x00007f107affaa20   rbp = 0x00007f10600008c0
Found by: given as instruction pointer in context
1  phantomjs!worker_thread [mongoose.c : 3852 + 0xa]
rip = 0x00000000004526d8   rsp = 0x00007f107affaa50
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f107affd700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f107affd9c0
r15 = 0x00007f107affd700   rip = 0x00007f10cdbec182
rsp = 0x00007f107affcee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f107affcf80
Found by: stack scanning
Thread 11
0  libpthread-2.19.so + 0xc414
rbx = 0x0000000003c7b170   r12 = 0x0000000000000000
r13 = 0x0000000003c7ab30   r14 = 0x00007f107a7fc9c0
r15 = 0x0000000003c7ac10   rip = 0x00007f10cdbf0414
rsp = 0x00007f107a7f9a20   rbp = 0x00007f10540008c0
Found by: given as instruction pointer in context
1  phantomjs!worker_thread [mongoose.c : 3852 + 0xa]
rip = 0x00000000004526d8   rsp = 0x00007f107a7f9a50
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f107a7fc700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f107a7fc9c0
r15 = 0x00007f107a7fc700   rip = 0x00007f10cdbec182
rsp = 0x00007f107a7fbee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f107a7fbf80
Found by: stack scanning
Thread 12
0  libpthread-2.19.so + 0xc414
rbx = 0x0000000003c7b170   r12 = 0x0000000000000000
r13 = 0x0000000003c7ab30   r14 = 0x00007f1079ffb9c0
r15 = 0x0000000003c7ac10   rip = 0x00007f10cdbf0414
rsp = 0x00007f1079ff8a20   rbp = 0x00007f10580008c0
Found by: given as instruction pointer in context
1  phantomjs!worker_thread [mongoose.c : 3852 + 0xa]
rip = 0x00000000004526d8   rsp = 0x00007f1079ff8a50
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f1079ffb700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f1079ffb9c0
r15 = 0x00007f1079ffb700   rip = 0x00007f10cdbec182
rsp = 0x00007f1079ffaee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f1079ffaf80
Found by: stack scanning
Thread 13
0  libpthread-2.19.so + 0xc414
rbx = 0x0000000003c7b170   r12 = 0x0000000000000000
r13 = 0x0000000003c7ab30   r14 = 0x00007f10797fa9c0
r15 = 0x0000000003c7ac10   rip = 0x00007f10cdbf0414
rsp = 0x00007f10797f7a20   rbp = 0x00007f104c0008c0
Found by: given as instruction pointer in context
1  phantomjs!worker_thread [mongoose.c : 3852 + 0xa]
rip = 0x00000000004526d8   rsp = 0x00007f10797f7a50
Found by: stack scanning
2  libpthread-2.19.so + 0x8181
rbx = 0x00007f10797fa700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f10797fa9c0
r15 = 0x00007f10797fa700   rip = 0x00007f10cdbec182
rsp = 0x00007f10797f9ee0   rbp = 0x0000000000000000
Found by: call frame info
3  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f10797f9f80
Found by: stack scanning
Thread 14
0  libc-2.19.so + 0xf2cb3
rbx = 0x00007f1078ff8d60   r12 = 0x000000000000224e
r13 = 0x000000000000002b   r14 = 0x00007f1050000a98
r15 = 0x00007f1050000d30   rip = 0x00007f10cd0f0cb3
rsp = 0x00007f1078ff8b80   rbp = 0x0000000000065ab3
Found by: given as instruction pointer in context
1  phantomjs!qt_safe_select [qcore_unix.cpp : 93 + 0x16]
rip = 0x0000000001d06228   rsp = 0x00007f1078ff8b90
Found by: stack scanning
2  phantomjs!QEventDispatcherUNIXPrivate::doSelect [qeventdispatcher_unix.cpp : 223 + 0xd]
rbx = 0x00007f10500012b0   r12 = 0x00007f1078ff8db0
r13 = 0x00007f10500008e0   r14 = 0x00007f1078ff8d60
r15 = 0x00007f1050000d30   rip = 0x0000000001d075e7
rsp = 0x00007f1078ff8c20   rbp = 0x00007f10500008e0
Found by: call frame info
3  phantomjs!QEventDispatcherUNIX::processEvents [qeventdispatcher_unix.cpp : 937 + 0x4]
rbx = 0x00007f10500012b0   r12 = 0x00007f1078ff8db0
r13 = 0x00007f10500008c0   r14 = 0x0000000000000001
r15 = 0x0000000003c89ed8   rip = 0x0000000001d08092
rsp = 0x00007f1078ff8d60   rbp = 0x00007f10500008e0
Found by: call frame info
4  phantomjs!QEventLoop::processEvents [qeventloop.cpp : 149 + 0x1]
rbx = 0x00007f10500012b0   r12 = 0x00007f1078ff8e40
r13 = 0x00007f1078ff8e50   r14 = 0x0000000003997230
r15 = 0x0000000003c89ed8   rip = 0x0000000001cdd4b5
rsp = 0x00007f1078ff8db0   rbp = 0x00007f1078ff8df0
Found by: call frame info
5  phantomjs!QEventLoop::exec [qeventloop.cpp : 200 + 0x4]
rbx = 0x00007f10500012b0   r12 = 0x00007f1078ff8e40
r13 = 0x00007f1078ff8e50   r14 = 0x0000000003997230
r15 = 0x0000000003c89ed8   rip = 0x0000000001cdd918
rsp = 0x00007f1078ff8de0   rbp = 0x00007fffa4c50370
Found by: call frame info
6  phantomjs!QThread::exec [qthread.cpp : 542 + 0xc]
rbx = 0x0000000003c89e50   r12 = 0x0000000003c89ed8
r13 = 0x0000000000000001   r14 = 0x00007f1078ff99c0
r15 = 0x00007f1078ff9700   rip = 0x0000000001bdfdf6
rsp = 0x00007f1078ff8e40   rbp = 0x0000000003c89ed8
Found by: call frame info
7  phantomjs!QThreadPrivate::start [qthread_unix.cpp : 338 + 0x9]
rbx = 0x0000000003c89ed8   r12 = 0x0000000003c89f90
r13 = 0x0000000000000001   r14 = 0x00007f1078ff99c0
r15 = 0x00007f1078ff9700   rip = 0x0000000001be2cc2
rsp = 0x00007f1078ff8e90   rbp = 0x0000000003c5c170
Found by: call frame info
8  libpthread-2.19.so + 0x8181
rbx = 0x00007f1078ff9700   r12 = 0x0000000000000000
r13 = 0x0000000000000000   r14 = 0x00007f1078ff99c0
r15 = 0x00007f1078ff9700   rip = 0x00007f10cdbec182
rsp = 0x00007f1078ff8ee0   rbp = 0x0000000000000000
Found by: call frame info
9  libc-2.19.so + 0xfb38c
rip = 0x00007f10cd0f938d   rsp = 0x00007f1078ff8f80
Found by: stack scanning
Loaded modules:
0x00400000 - 0x0268dfff  phantomjs  ???  (main)
0x7f103e3d6000 - 0x7f103e470fff  DejaVuSans-BoldOblique.ttf  ???
0x7f10429ac000 - 0x7f1042a46fff  DejaVuSans-Oblique.ttf  ???
0x7f1042a47000 - 0x7f1042a79fff  UbuntuMono-R.ttf  ???
0x7f1042a7a000 - 0x7f1042a90fff  TlwgTypo.ttf  ???
0x7f1042a91000 - 0x7f1042aa7fff  TlwgMono.ttf  ???
0x7f1042aa8000 - 0x7f1042ac2fff  LiberationMono-Regular.ttf  ???
0x7f1042ac3000 - 0x7f1042b53fff  FreeMono.ttf  ???
0x7f1042b54000 - 0x7f1042b71fff  DroidSansMono.ttf  ???
0x7f1042b72000 - 0x7f1042bc3fff  DejaVuSansMono.ttf  ???
0x7f1042bc4000 - 0x7f1042bcdfff  c0419bt_.pfb  ???
0x7f1042bce000 - 0x7f1042be5fff  n022003l.pfb  ???
0x7f1042be6000 - 0x7f1042bfcfff  z003034l.pfb  ???
0x7f1042bfd000 - 0x7f1042c18fff  Saab.ttf  ???
0x7f1042c19000 - 0x7f1042c3ffff  utkal.ttf  ???
0x7f1042c40000 - 0x7f1042c50fff  lohit_hi.ttf  ???
0x7f1042c51000 - 0x7f1042c62fff  gargi.ttf  ???
0x7f1042c63000 - 0x7f1042c93fff  Vemana.ttf  ???
0x7f1042c94000 - 0x7f1042ca8fff  Rekha.ttf  ???
0x7f1042ca9000 - 0x7f1042d06fff  Rachana_04.ttf  ???
0x7f1042d07000 - 0x7f1042d36fff  Pothana2000.ttf  ???
0x7f1042d37000 - 0x7f1042d54fff  Malige-n.ttf  ???
0x7f1042d55000 - 0x7f1042d6dfff  Kedage-n.ttf  ???
0x7f1042d6e000 - 0x7f1042de2fff  Padauk-book.ttf  ???
0x7f1042de3000 - 0x7f1042e56fff  Padauk.ttf  ???
0x7f1042e57000 - 0x7f1042e88fff  opens___.ttf  ???
0x7f1042e89000 - 0x7f104322afff  NanumMyeongjo.ttf  ???
0x7f104322b000 - 0x7f1043628fff  NanumBarunGothic.ttf  ???
0x7f1043629000 - 0x7f1043635fff  KacstOne.ttf  ???
0x7f1043636000 - 0x7f1043654fff  mry_KacstQurn.ttf  ???
0x7f1043655000 - 0x7f1043672fff  KacstTitleL.ttf  ???
0x7f1043673000 - 0x7f1043683fff  KacstTitle.ttf  ???
0x7f1043684000 - 0x7f104368efff  KacstScreen.ttf  ???
0x7f104368f000 - 0x7f10436a0fff  KacstQurn.ttf  ???
0x7f10436a1000 - 0x7f10436abfff  KacstPoster.ttf  ???
0x7f10436ac000 - 0x7f10436b9fff  KacstPen.ttf  ???
0x7f10436ba000 - 0x7f10436cbfff  KacstOffice.ttf  ???
0x7f10436cc000 - 0x7f10436dcfff  KacstNaskh.ttf  ???
0x7f10436dd000 - 0x7f10436eafff  KacstLetter.ttf  ???
0x7f10436eb000 - 0x7f10436f9fff  KacstFarsi.ttf  ???
0x7f10436fa000 - 0x7f1043703fff  KacstDigital.ttf  ???
0x7f1043704000 - 0x7f1043713fff  KacstBook.ttf  ???
0x7f1043714000 - 0x7f1043769fff  Ubuntu-C.ttf  ???
0x7f104376a000 - 0x7f10437a9fff  Ubuntu-M.ttf  ???
0x7f10437aa000 - 0x7f10437eafff  KhmerOSsys.ttf  ???
0x7f10437eb000 - 0x7f104388afff  DejaVuSansCondensed-Bold.ttf  ???
0x7f104388b000 - 0x7f1043cd8fff  TibetanMachineUni.ttf  ???
0x7f1043cd9000 - 0x7f1043ffffff  FreeSerif.ttf  ???
0x7f1048000000 - 0x7f104800bfff  KacstDecorative.ttf  ???
0x7f104800c000 - 0x7f1048018fff  KacstArt.ttf  ???
0x7f1048019000 - 0x7f1048021fff  s050000l.pfb  ???
0x7f1048022000 - 0x7f104802dfff  d050000l.pfb  ???
0x7f104802e000 - 0x7f1048044fff  TlwgTypist.ttf  ???
0x7f1048045000 - 0x7f104805cfff  TlwgTypewriter.ttf  ???
0x7f104805d000 - 0x7f1048071fff  Sawasdee.ttf  ???
0x7f1048072000 - 0x7f1048098fff  Purisa.ttf  ???
0x7f1048099000 - 0x7f10480b2fff  Norasi.ttf  ???
0x7f10480b3000 - 0x7f10480c7fff  Kinnari.ttf  ???
0x7f10480c8000 - 0x7f10480edfff  LiberationSerif-Regular.ttf  ???
0x7f10480ee000 - 0x7f1048109fff  LiberationSansNarrow-Regular.ttf  ???
0x7f104810a000 - 0x7f104812cfff  LiberationSans-Regular.ttf  ???
0x7f104812d000 - 0x7f1048186fff  DejaVuSerif.ttf  ???
0x7f1048187000 - 0x7f104959bfff  uming.ttc  ???
0x7f104959c000 - 0x7f104a5f7fff  ukai.ttc  ???
0x7f104a5f8000 - 0x7f104abeafff  TakaoPGothic.ttf  ???
0x7f104abeb000 - 0x7f104bffffff  uming.ttc  ???
0x7f1068003000 - 0x7f1068019fff  Phetsarath_OT.ttf  ???
0x7f106801a000 - 0x7f1068044fff  DroidSerif-Regular.ttf  ???
0x7f1068045000 - 0x7f10680d2fff  AbyssinicaSIL-R.ttf  ???
0x7f10680d3000 - 0x7f10680edfff  p052003l.pfb  ???
0x7f10680ee000 - 0x7f1068106fff  n021003l.pfb  ???
0x7f1068107000 - 0x7f1068120fff  c059013l.pfb  ???
0x7f1068121000 - 0x7f1068139fff  b018012l.pfb  ???
0x7f106813a000 - 0x7f10682b7fff  FreeSans.ttf  ???
0x7f10682b8000 - 0x7f1068302fff  lklug.ttf  ???
0x7f1068303000 - 0x7f1068354fff  Meera_04.ttf  ???
0x7f1068355000 - 0x7f1068779fff  NanumGothic.ttf  ???
0x7f106877a000 - 0x7f106afa3fff  uming.ttc  ???
0x7f106afa4000 - 0x7f106bffffff  ukai.ttc  ???
0x7f1070005000 - 0x7f107000efff  Symbol.pfb  ???
0x7f107000f000 - 0x7f1070017fff  c0648bt_.pfb  ???
0x7f1070018000 - 0x7f1070027fff  a010015l.pfb  ???
0x7f1070028000 - 0x7f1070038fff  lohit_ta.ttf  ???
0x7f1070039000 - 0x7f107003ffff  lohit_pa.ttf  ???
0x7f1070040000 - 0x7f107004ffff  lohit_gu.ttf  ???
0x7f1070050000 - 0x7f1070072fff  lohit_bn.ttf  ???
0x7f1070073000 - 0x7f10700a0fff  MuktiNarrow.ttf  ???
0x7f10700a1000 - 0x7f10700e1fff  KhmerOS.ttf  ???
0x7f10700e2000 - 0x7f1072199fff  ukai.ttc  ???
0x7f107219a000 - 0x7f10721a1fff  DroidSansHebrew-Regular.ttf  ???
0x7f10721a2000 - 0x7f10721b5fff  Umpush.ttf  ???
0x7f10721b6000 - 0x7f10721c8fff  Garuda.ttf  ???
0x7f10721c9000 - 0x7f10721dcfff  Loma.ttf  ???
0x7f10721dd000 - 0x7f10721f2fff  Waree.ttf  ???
0x7f10721f3000 - 0x7f1072204fff  n019043l.pfb  ???
0x7f10730c7000 - 0x7f107317cfff  DejaVuSans.ttf  ???
0x7f10783f0000 - 0x7f10785f5fff  libnss_dns-2.19.so  ???
0x7f10785f6000 - 0x7f10787f8fff  libnss_mdns4_minimal.so.2  ???
0x7f10c8158000 - 0x7f10c8363fff  libnss_files-2.19.so  ???
0x7f10c8364000 - 0x7f10c857cfff  libresolv-2.19.so  ???
0x7f10cbc77000 - 0x7f10cbed3fff  libssl.so.1.0.0  ???
0x7f10cbed5000 - 0x7f10cc2aafff  libcrypto.so.1.0.0  ???
0x7f10cc2af000 - 0x7f10cc994fff  locale-archive  ???
0x7f10cc995000 - 0x7f10ccbbefff  libexpat.so.1.6.0  ???
0x7f10ccbbf000 - 0x7f10ccde4fff  libpng12.so.0.50.0  ???
0x7f10ccde5000 - 0x7f10ccffdfff  libz.so.1.2.8  ???
0x7f10ccffe000 - 0x7f10cd3befff  libc-2.19.so  ???
0x7f10cd3c4000 - 0x7f10cd5d9fff  libgcc_s.so.1  ???
0x7f10cd5da000 - 0x7f10cd8dffff  libm-2.19.so  ???
0x7f10cd8e0000 - 0x7f10cdbcefff  libstdc++.so.6.0.19  ???
0x7f10cdbe4000 - 0x7f10cddfdfff  libpthread-2.19.so  ???
0x7f10cde02000 - 0x7f10ce009fff  librt-2.19.so  ???
0x7f10ce00a000 - 0x7f10ce20dfff  libdl-2.19.so  ???
0x7f10ce20e000 - 0x7f10ce449fff  libfontconfig.so.1.8.0  ???
0x7f10ce44a000 - 0x7f10ce6ecfff  libfreetype.so.6.11.1  ???
0x7f10ce6ed000 - 0x7f10ce70ffff  ld-2.19.so  ???
0x7f10ce86a000 - 0x7f10ce870fff  gconv-modules.cache  ???
0x7f10ce871000 - 0x7f10ce871fff  libc.mo  ???
0x7f10ce872000 - 0x7f10ce872fff  libc.mo  ???
0x7f10ce873000 - 0x7f10ce873fff  c05880de57d1f5e948fdfacc138775d9-le64.cache-4  ???
0x7f10ce874000 - 0x7f10ce87efff  945677eb7aeaf62f1d50efc3fb3ec7d8-le64.cache-4  ???
0x7f10ce87f000 - 0x7f10ce884fff  2cd17615ca594fa2959ae173292e504c-le64.cache-4  ???
0x7f10ce885000 - 0x7f10ce885fff  e7071f4a29fa870f4323321c154eba04-le64.cache-4  ???
0x7f10ce886000 - 0x7f10ce886fff  0d8c3b2ac0904cb8a57a757ad11a4a08-le64.cache-4  ???
0x7f10ce887000 - 0x7f10ce88dfff  a755afe4a08bf5b97852ceb7400b47bc-le64.cache-4  ???
0x7f10ce88e000 - 0x7f10ce8a1fff  04aabc0a78ac019cf9454389977116d2-le64.cache-4  ???
0x7f10ce8a2000 - 0x7f10ce8a2fff  1ac9eb803944fde146138c791f5cc56a-le64.cache-4  ???
0x7f10ce8a3000 - 0x7f10ce8a6fff  385c0604a188198f04d133e54aba7fe7-le64.cache-4  ???
0x7f10ce8a7000 - 0x7f10ce8a7fff  dc05db6664285cc2f12bf69c139ae4c3-le64.cache-4  ???
0x7f10ce8a8000 - 0x7f10ce8a9fff  767a8244fc0220cfb567a839d0392e0b-le64.cache-4  ???
0x7f10ce8aa000 - 0x7f10ce8aefff  8801497958630a81b71ace7c5f9b32a8-le64.cache-4  ???
0x7f10ce8af000 - 0x7f10ce8b5fff  3047814df9a2f067bd2d96a2b9c36e5a-le64.cache-4  ???
0x7f10ce8b6000 - 0x7f10ce8bbfff  b47c4e1ecd0709278f4910c18777a504-le64.cache-4  ???
0x7f10ce8bc000 - 0x7f10ce8cefff  d52a8644073d54c13679302ca1180695-le64.cache-4  ???
0x7f10ce8cf000 - 0x7f10ce8d6fff  3f7329c5293ffd510edef78f73874cfd-le64.cache-4  ???
0x7f10ce8d7000 - 0x7f10ce8e1fff  d589a48862398ed80a3d6066f4f56f4c-le64.cache-4  ???
0x7f10ce8e2000 - 0x7f10ce8eefff  089dead882dea3570ffc31a9898cfb69-le64.cache-4  ???
0x7f10ce8f8000 - 0x7f10ce8f8fff  4794a0821666d79190d59a36cb4f44b5-le64.cache-4  ???
0x7f10ce8f9000 - 0x7f10ce8f9fff  56cf4f4769d0f4abc89a4895d7bd3ae1-le64.cache-4  ???
0x7f10ce8fa000 - 0x7f10ce8fafff  b9d506c9ac06c20b433354fa67a72993-le64.cache-4  ???
0x7f10ce8fb000 - 0x7f10ce8fbfff  0c9eb80ebd1c36541ebe2852d3bb0c49-le64.cache-4  ???
0x7f10ce8fc000 - 0x7f10ce908fff  e13b20fdb08344e0e664864cc2ede53d-le64.cache-4  ???
0x7f10ce909000 - 0x7f10ce90cfff  7ef2298fde41cc6eeb7af42e48b7d293-le64.cache-4  ???
0x7fffa4d55000 - 0x7fffa4d56fff  linux-gate.so  ???

Please upgrade to PhantomJS 2.0. 1.9.x is no longer supported, and known to have many crasher bugs that are fixed in 2 version.

authors: Vitallium weixy

repo: ariya/phantomjs


text:
Casting syntax

Is it possible to get the old cast syntax back? type(val) as opposed to cast(type, val) -- which is what we do now.

I think this will be easy if we move the resolve phase to between parsing and constructing.

This should currently be really easy after enum pr

Implemented with 5706e0f0880d8482ec65f794f86e2c87de38a675

authors: MovingtoMars felixangell kiljacken

repo: ark-lang/ark


text:
Clarify componentDidMount()

componentDidMount() only is called on the client. Server-side react using React.renderToString() will not call it.
https://facebook.github.io/react/docs/component-specs.html#mounting-componentwillmount

Hey there,
I see your point. You're right, that's worth mentioning, but I think that description is a bit too laconic. I think it's worth expanding a little bit. We didn't mention server-side React rendering before.
Thanks for contributing, have a nice day!

license: mit

license_source: bigquery


text:
rename molochconfig.h to arkimeconfig.h, include prefix in config.h

see if we can build both a /opt/arkime and /data/moloch and have life work out

the beginning of the end

repo: arkime/arkime


text:
StyleGuide: Update recommendations

Change-Id: Ie1084ab1eaadb24f80a1bd1b3bc64a0f8e99a786

Code Review comments can be found at https://gerrithub.io/q/

repo: arklian/patina


text:
Merge OAuth and Password Login Pages

Combined the OAuth and password login functionalities into a unified
login page. This consolidation allows users to choose between
password-based authentication and OAuth login methods on the same
page. The updated page includes options for both login methods and
seamlessly handles redirection based on the chosen method.
TEST=manual

Verified that both login methods work correctly.
Ensured proper redirection after successful and unsuccessful login
attempts.

Change-Id: I1a30405882d65760c510eb9358019402c639e41c

Code Review comments can be found at https://gerrithub.io/q/I1a30405882d65760c510eb9358019402c639e41c


text:
merge from arlac77/npm-package-template

package.json

chore(package): rollup@^1.20.1
chore(scripts): cover@#overwrite c8 -x 'tests/**/*.mjs' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
chore(engines): node@>=10.16.0
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/*-test.mjs' as in template
chore(package): set $.ava.extensions='mjs' as in template

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
Best approach to error message translation

Hi, we are using async-stripe on our rust server and i've been tasked with making it so all the possible error messages sent to the client be translated in another language. I was curious to know what the best approach would be and if that may even be something done directly onto the crate as a new feature.

Hmm, interesting question. The errors are hardcoded in english atm but that only affects the result of displaying them. You could conceivably match on the error type and provide your own translations but then you now have to punt along and translate all the serde erorrs (or provide a basic 'oops, can't serialize') as well as serde_qs, all of stripe's api errors, and finally the http client's errors which are deliberately left as a raw string since they are pluggable.
https://github.com/arlyon/async-stripe/blob/refactor/crates/crates/async_stripe_core/src/error.rs#L8-L23
I'm wondering if something like this would be good enough (pseudocode)?
trait ErrorMapper {
    fn map(err: StripeError) -> String;
}

struct JapaneseMapper;
impl ErrorMapper for JapaneseMapper {
    fn map(err: StripeError, lang: &ErrorMapper) -> String {
        match err {
            StripeError::Stripe(_) => "支払いプロバイダーの問題",
            StripeError::QueryStringSerialize(_) | StripeError::JsonSerialize(_) => "リクエストを作成できませんでした",
            ...
        }
    }
}

fn main() {
    let mapper = JapaneseMapper;
    client.do_request().map_err(mapper.map);
}

@arlyon
Would there be a way to make StripeError::Stripe give its ErrorCode and then map the codes to japanese and display them?
Like these guys:
    AccountCountryInvalidAddress,
    AccountInvalid,
    AccountNumberInvalid,
    AlipayUpgradeRequired,
    AmountTooLarge,
    AmountTooSmall,
    ApiKeyExpired,
    BalanceInsufficient,
    BankAccountExists,
    BankAccountUnusable,
    BankAccountUnverified,
    BitcoinUpgradeRequired,
    CardDeclined,
    ChargeAlreadyCaptured,
    ChargeAlreadyRefunded,
    ChargeDisputed,
    ChargeExpiredForCapture,
    CountryUnsupported,
    CouponExpired,
    CustomerMaxSubscriptions,
    EmailInvalid,
    ExpiredCard,
    IdempotencyKeyInUse,
    IncorrectAddress,
    IncorrectCvc,
    IncorrectNumber,
    IncorrectZip,
    InstantPayoutsUnsupported,
    InvalidCardType,
    InvalidChargeAmount,
    InvalidCvc,
    InvalidExpiryMonth,
    InvalidExpiryYear,
    InvalidNumber,
    InvalidSourceUsage,
    InvoiceNoCustomerLineItems,
    InvoiceNoSubscriptionLineItems,
    InvoiceNotEditable,
    InvoiceUpcomingNone,
    LivemodeMismatch,
    Missing,
    OrderCreationFailed,
    OrderRequiredSettings,
    OrderStatusInvalid,
    OrderUpstreamTimeout,
    OutOfInventory,
    ParameterInvalidEmpty,
    ParameterInvalidInteger,
    ParameterInvalidStringBlank,
    ParameterInvalidStringEmpty,
    ParameterMissing,
    ParameterUnknown,
    PaymentMethodUnactivated,
    PaymentIntentUnexpectedState,
    PayoutsNotAllowed,
    PlatformApiKeyExpired,
    PostalCodeInvalid,
    ProcessingError,
    ProductInactive,
    RateLimit,
    ResourceAlreadyExists,
    ResourceMissing,
    RoutingNumberInvalid,
    SecretKeyRequired,
    SepaUnsupportedAccount,
    ShippingCalculationFailed,
    SkuInactive,
    StateUnsupported,
    TaxIdInvalid,
    TaxesCalculationFailed,
    TestmodeChargesOnly,
    TlsVersionUnsupported,
    TokenAlreadyUsed,
    TokenInUse,
    TransfersNotAllowed,
    UpstreamOrderCreationFailed,
    UrlInvalid,```

I will look into this, sounds useful.

authors: arlyon parK-dev

repo: arlyon/async-stripe


text:
Thumbnail from feed

This is an example feed I parse:
<?xml version="1.0" encoding="utf-8"?>
    <rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:xumo="http://www.xumo.com/rss/extensions/" xmlns:dcterms="http://purl.org/dc/terms/">
    <channel>
        <title><![CDATA[Sportword - Gold Cup (Highlights)]]></title>
        <description/>
        <item>
            <id><![CDATA[8102743]]></id>
            <projectid scheme="sdn:projectid"><![CDATA[9308]]></projectid>
            <title><![CDATA[Mexiko - Honduras (Highlight)]]></title>
            <description><![CDATA[Mexiko - Honduras (Highlight)]]></description>
            <keywords><![CDATA[Gold Cup,Highlights]]></keywords>
            <genre><![CDATA[Sport]]></genre>
            <program><![CDATA[26228]]></program>
            <guid isPermaLink="false"><![CDATA[74bd5f94-d3d4-4e2c-8ddf-adda35bde88f]]></guid>
            <sdnPlayoutId><![CDATA[74bd5f94-d3d4-4e2c-8ddf-adda35bde88f]]></sdnPlayoutId>
            <language><![CDATA[]]></language>
            <media:group>
                <media:title type="plain"><![CDATA[Mexiko - Honduras (Highlight)]]></media:title>
                <media:description type="plain"><![CDATA[Mexiko - Honduras (Highlight)]]></media:description>
                <media:keywords><![CDATA[Gold Cup,Highlights]]></media:keywords>
                                <media:content description="Player App" url="https://playout.3qsdn.com/74bd5f94-d3d4-4e2c-8ddf-adda35bde88f" type="application/x-shockwave-flash" duration="176.064" sdnformatid="player-app"/>
                <media:content description="MPEG DASH" url="https://sdn-global-streaming-cache.3qsdn.com/stream/9308/files/23/06/26/8102743/9308-xtmvcNwqYJ2DPyb.ism/manifest.mpd" type="application/dash+xml" duration="176.064" sdnformatid="mpeg-dash"/>
                <media:content description="HLS" url="https://sdn-global-streaming-cache.3qsdn.com/stream/9308/files/23/06/26/8102743/9308-xtmvcNwqYJ2DPyb.ism/playlist.m3u8" type="application/x-mpegURL" duration="176.064"  sdnformatid="hls"/>
                <media:content description="HDS"  url="https://sdn-global-streaming-cache.3qsdn.com/stream/9308/files/23/06/26/8102743/9308-xtmvcNwqYJ2DPyb.ism/manifest.f4m" type="text/xml" duration="176.064"  sdnformatid="hds"/>
                <media:content description="MP4 360p" url="https://sdn-global-prog-cache.3qsdn.com/9308/files/23/06/26/8102743/4-NkgzcWKQwTmb28Ph7Ln9.mp4" type="video/mp4" height="360" medium="video" fileSize="19710965" duration="176.064" sdnformatid="4" />
                <media:content description="MP4 720p" url="https://sdn-global-prog-cache.3qsdn.com/9308/files/23/06/26/8102743/2-bMvhpmxCdG3H27BfZYPq.mp4" type="video/mp4" height="720" medium="video" fileSize="64882999" duration="176.064" sdnformatid="2" />
                <media:content description="MP4 1080p" url="https://sdn-global-prog-cache.3qsdn.com/9308/files/23/06/26/8102743/1-3dwZmjRy4fQTYtrgzchM.mp4" type="video/mp4" height="1080" medium="video" fileSize="89496372" duration="176.064" sdnformatid="1" />
                <media:thumbnail url="https://sdn-global-prog-cache.3qsdn.com/9308/files/23/06/26/8102743/d3c7e504-7ed9-495d-9aed-0e5f7164444b.jpg"/>
            </media:group>
            <pubDate>Mon, 26 Jun 2023 02:45:01 UTC</pubDate>
        </item>
    </channel>
</rss>

Unfortunately my specificItem in the MediaGroup.Media items do not contain a thumbnail, just the videos. Am I missing out on something?
I use FeedReader.ReadFromString(feed) which worked flawlessly until now.
Thanks for any help in advance (:
R0boc0p

Already addressed: https://github.com/arminreiter/FeedReader/issues/32

repo: arminreiter/FeedReader


text:
🛑 NWTFV is down

In 886019f, NWTFV (https://nwtfv.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NWTFV is back up in 5c01d41.

repo: arnef/status


text:
Multiple Connections with JSON configuration

Hi there!
I‘m currently thinking about replacing amqplib with rabbit and was wondering what’s the best way to handle multiple connections (different rabbitmqs) with the JSON config? Just calling configure multiple times with the different configuration objects?😊
Thanks a lot!

I don't think rabbit would be a good fit for that. Also, consider that the maintainer haven't had any activity in about six months.

@luddd3 What’s your suggestion/recommendation for easy to set up, high performance and flexible amqp lib?

I would write a thin wrapper around amqplib or use something based on it with active development. Currently I use rabbit for some projects, but I would be hesitant to recommend it to new users.

@luddd3 Tried amqplib-easy but it's performance is horrible. It just handles up to 1500 msg/s...rabbot up to 14000 msg/s.
And I don't wanna reinvent the wheel.
So if there're any existing high performance wrappers with active maintenance, let me know :)

Ok, I don't know if that lib does something special to kill performance, but I would expect them to be similar since both rabbit and amqplib-easy depend on amqplib to handle the communication with rabbitmq.

@felixheck - yep, just use multiple configure calls - you'll get a different promise for each. Since each connection and follow up set of topology operations is a stack of promises, I think you'll be happier treating each as a separate configure call.
Version 2 is out now and I hope to publish some follow up changes later today or tomorrow to address outstanding issues/requests.

authors: arobson felixheck luddd3

repo: arobson/rabbot


text:
Refactor tonatona db

This PR is implementing the suggestions from https://github.com/arow-oss/tonatona/issues/11.
In particular, the following changes are made:

Instead of using one top-level DB Shared type, instead have a Shared type defined in each child module: Tonatona.Db.Sqlite.Shared and Tonatona.Db.Postgres.Shared.
Change the DB Shared types to only contain a Pool SqlBackend instead of a function to actually run a query (like ReaderT SqlBackend m a -> TonaM conf shared a).
Change the HasShared type class to be defined in each child module: Tonatona.Db.Sqlite.HasShared and Tonatona.Db.Postgres.HasShared.
Change the run and runMigrate functions to be declared in each child module: Tonatona.Db.Sqlite.run and Tonatona.Db.Postgres.run.

There are a couple design points I have doubts about, and I will add them as questions inline.

@arowM
I added commit 63f1b81.  This commit updates this PR with your feedback from above.

data Shared = Shared
 { tonaSqlite :: TonaDbSqlite.Shared
 , tonaPostgres :: TonaDbPostgres.Shared
 , tonaLogger :: TonaLogger.Shared
 }

The problem with this code is that the Plug instance needs to initialize both the TonaDbSqlite.Shared and TonaDbPostgres.Shared like the following:
instance Plug Config Shared where
  init conf = do
    Shared
      <$> TonaDbSqlite.init conf stdoutLogger
      <*> TonaDbPostgres.init conf stdoutLogger
      <*> TonaLogger.init stdoutLogger

TonaDbSqlite.init and TonaDbPostgres.init need to initialize the connection pool for SQLite and PostgreSQL.  However, they are both being passed the same conf (which only has settings for one of them).
In this particular instance, this works fine as long as you don't use the incorrect connection pool, but I can imagine that there might be a database that throws an error when trying to do something like this.
Also, the end user is still forced to define their own dbRun function:
sharedDbRun ::
     (TonaDbPostgres.HasShared shared, TonaDbSqlite.HasShared shared)
  => ReaderT SqlBackend (TonaM Config shared) a
  -> TonaM Config shared a
sharedDbRun query = do
  conf <- askConf
  case dbToUse conf of
    Sqlite -> TonaDbSqlite.run query
    PostgreSQL -> TonaDbPostgres.run query

I don't know how much time we want to spend actually trying to support something like this, since most of the Haskell applications we have made only need to connect to one type of database.  Most of the applications we make don't need to worry about figuring out which type of database to use at runtime.

TonaDbSqlite.init and TonaDbPostgres.init need to initialize the connection pool for SQLite and PostgreSQL. However, they are both being passed the same conf (which only has settings for one of them).

The actual problem we have to resolve is the fields of TonaDb.Config, I guess.
The definition of TonaDb.Conf has dbConnString in its field as follows.
data Config = Config
  { dbConnString :: DbConnStr
  , dbConnNum :: DbConnNum
  }
  deriving (Show)

The problem is that the dbConnString is not actually the same value among Tonatona.Db.*, which is just the same type but not the same value.
(The dbConnNum would be the same value among Tonatona.Db.*, so it is no problem to be in the Tonatona.Db.Config.)
The ideal solution, I think, is to migrate dbConnString field to Tonatona.Db.*.Config (e.g., Tonatona.Db.Postgres.Config).

Also, the end user is still forced to define their own dbRun function:

I don't feel it's so bad.
It seems redundant because both postgres and sqlite have similar interface, but how about if we want to use postgres and memcached together?
(I guess it is not unnatural to declare run function like this, or we also need two independent query part for each usage, separately.)
Only another proper approach I believe is migrating Tonatona.Db.Postgres and Tonatona.Db.Sqlite to Tonatona.Db.Persistent.Sql.Postgres and Tonatona.Db.Persistent.Sql.Sqlite, and then we could declare same run function for them in Tonatona.Db.Persistent.Sql.

This is okay for the sample application (because calling TonaDbSqlite.init with incorrect information doesn't seem to cause any problems), but may not work for some other type of database.

In such meaning, we can say it is legal case to use error on HasShared instance declaration, so it would be better to revert  63f1b81 and use SharedDb data type instead.
After reverting, how about migrating dbConnString field to Tonatona.Db.*.Config (e.g., Tonatona.Db.Postgres.Config)?

@arowM
Allowing error to be called in the HasShared instance declaration makes it harder to reason about application code.
For instance, take the function from my previous post:
doSomething
  :: (TonaPostgres.HasShared shared, TonaMemcached.HasShared shared)
  => UserId
  -> TonaM conf shared User
doSomething userId = do

This type signature basically says, "Given a UserId, I will return you a User within the TonaM monad, as long as I am able to access both PostgreSQL and Memcached."
The TonaPostgres.HasShared and TonaMemcached.HasShared type classes give you an assurance that you will be able to access both Postgresql and Memcached.
However, if you allow HasShared to use error, then you lose those assurances and it becomes harder to reason about the code.
Maybe that is an okay compromise to make, in order to make the code as simple as possible?

After reverting, how about migrating dbConnString field to Tonatona.Db.*.Config (e.g., Tonatona.Db.Postgres.Config)?

I think this is a good idea, since different databases might use different types of configuration strings.

Of course, I agree with prevent using error in the HasShared when we have to use both Db A and Db B.
What I meant is "How about permit to use error in the HasShared only if we use Sum type such as SharedDb (in 63f1b81), which indicates that we only use one of the Db A or Db B".
In such meaning, what do you think? Is it harmful?

How about permit to use error in the HasShared only if we use Sum type such as SharedDb (in 63f1b81), which indicates that we only use one of the Db A or Db B

Okay, this sounds like a good plan.  I agree that it would be better to not have to use error, but I can't think of a good say.
In our use-case, it should be safe as long as the user makes sure to only use sharedDbRun (which is defined in tonatona-sample/src/Tonatona/Sample.hs):
sharedDbRun ::
     (TonaDbPostgres.HasShared shared, TonaDbSqlite.HasShared shared)
  => ReaderT SqlBackend (TonaM Config shared) a
  -> TonaM Config shared a
sharedDbRun query = do
  conf <- askConf
  case dbToUse conf of
    Sqlite -> TonaDbSqlite.run query
    PostgreSQL -> TonaDbPostgres.run query

If the user directly uses TonaDbSqlite.run or TonaDbPostgres.run, then they might get the error case.

I rebased this PR to delete commit 63f1b81576c9.  I then added commit a554994d391f.
Commit a554994d391f removes the tonatona-db module.  It adds the Config type and HasConfig class to Tonatona.Db.Postgresql module and Tonatona.Db.Sqlite module.
This should be as we discussed above.
How does this look?

It seems some binary files are included in the commit by mistake.
It looks good to me except that.

Thanks!  I have taken out the binary files and merged this in.

authors: arowM cdepillabout

repo: arow-oss/tonatona


text:
Problem with ClinVar causal alt allele handling

Hi,
When loading VCF into GEMINI 0.12.1 I got this error:
Traceback (most recent call last):
  File "/usr/bin/gemini", line 6, in <module>
    gemini.gemini_main.main()
  File "/usr/share/gemini/anaconda/lib/python2.7/site-packages/gemini/gemini_main.py", line 1141, in main
    args.func(parser, args)
  File "/usr/share/gemini/anaconda/lib/python2.7/site-packages/gemini/gemini_main.py", line 225, in loadchunk_fn
    gemini_load_chunk.load(parser, args)
  File "/usr/share/gemini/anaconda/lib/python2.7/site-packages/gemini/gemini_load_chunk.py", line 697, in load
    gemini_loader.populate_from_vcf()
  File "/usr/share/gemini/anaconda/lib/python2.7/site-packages/gemini/gemini_load_chunk.py", line 117, in populate_from_vcf
    (variant, variant_impacts, extra_fields) = self._prepare_variation(var)
  File "/usr/share/gemini/anaconda/lib/python2.7/site-packages/gemini/gemini_load_chunk.py", line 305, in _prepare_variation
    clinvar_info = annotations.get_clinvar_info(var)
  File "/usr/share/gemini/anaconda/lib/python2.7/site-packages/gemini/annotations.py", line 541, in get_clinvar_info
    clinvar_causal_allele += hit.alt.split(',')[causal_allele_number - 1]
IndexError: list index out of range

Most recent release of ClinVar for GEMINI contains only decomposed alternative alleles but value of causal_allele_number is loaded from CLNALLE info field.
Comment in annotations.py:528 is invalid because:
zcat clinvar_20150305.tidy.vcf.gz | grep -Eo 'CLNALLE=.' | sort | uniq -c
    227 CLNALLE=-
   3468 CLNALLE=.
    160 CLNALLE=0
 108825 CLNALLE=1
   4244 CLNALLE=2
    373 CLNALLE=3
      2 CLNALLE=4

So instead of:
clinvar_causal_allele = hit.alt.split(',')[causal_allele_number - 1]

should be:
clinvar_causal_allele = hit.alt

Does it make sense or I'm missing something?

Hi @nuada , thanks for reporting. This fix looks reasonable, but can you send me the genomic position CHR, POS of a variant that results in this error? I'd like to make sure I understand what is going on since the clinvar preprocessing is fairly complex.

So, when I run that, I get:
$ zcat clinvar_20150305.tidy.vcf.gz | grep -Eo 'CLNALLE=.' | sort | uniq -c
227 CLNALLE=-
3468 CLNALLE=.
160 CLNALLE=0
113444 CLNALLE=1

I'm checking further.

I had an older version of the clinvar up on AWS. I have uploaded a new one.  You can run:
rm clinvar_*.tidy.*
wget https://s3.amazonaws.com/gemini-annotations/clinvar_20150305.tidy.vcf.gz
wgethttps://s3.amazonaws.com/gemini-annotations/clinvar_20150305.tidy.vcf.gz.tbi

from your data directory.

ClinVar update fixed this problem,
Thank you @brentp

thanks for reporting!

authors: brentp nuada


text:
Module build failed

Hi @artbelikov ,
I use angular-starter which using Webpack3 Angular5.
In a lazy module, I import {TreeDiagram} from 'angular2-tree-diagram';
But however,when I run "npm start",  I got following error ：

ERROR in ./node_modules/angular2-tree-diagram/index.ts
Module build failed: Error:
/node_modules/angular2-tree-diagram/index.ts is not part of the compilation output. Please check the other error messages for details.
at AngularCompilerPlugin.getCompiledFile (/node_modules/@ngtools/webpack/src/angular_compiler_plugin.js:649:23)
at plugin.done.then (**/node_modules/@ngtools/webpack/src/loader.js:467:39)
at process._tickCallback (internal/process/next_tick.js:109:7)
@ ./src/app/app.module.ts 32:0-58
@ ./src/app/index.ts
@ ./src/main.browser.ts
@ multi (webpack)-dev-server/client?http://localhost:3000 ./src/main.browser.ts

Pls help me to fix this.
Thank you!

Hi.
As you may notice I publish the module uncompiled. So you have to compile it yourself. That may be not the best practice, but solution is quite simple. Setup your typescript compilation that way, so it doesn't ignore folder angular2-tree-diagram inside node_modules.

authors: artbelikov jendison


text:
command 'quitPlugin.keybindings.closeWindow' not found (also quit and closeEditor)

Steps to reproduce:

Install Quit Control for VSCode
Press either Ctrl+Shift+W - or - Ctrl+W - or - Ctrl+Q in an editor or system tab
Message pops up saying command 'quitPlugin.keybindings.closeWindow' not found (or quit or closeEditor)

Extension information:

Name: Quit Control for VSCode
Id: artdiniz.quitcontrol-vscode
Description: Stop mistyping keyboard shortctus that close/quit VSCode unintentionally
Version: 3.1.0
Publisher: Artur Diniz Adam
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=artdiniz.quitcontrol-vscode

VSCode version:
$ code -v
1.32.3
a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4
x64

This happens to me too. I can no longer close open files with Ctrl + W, I only get command 'quitPlugin.keybindings.closeEditor' not found in the bottom right.

I can also confirm.

Quit Control for VSCode 2019-03-16 (v3.1.0)

VSCode
Version: 1.33.0
Commit: 0dd516dd412d42323fc3464531b1c715d51c4c1a
Date: 2019-04-04T15:08:57.775Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.4.0-138-generic

I have same issue.

I could only replicate this in Ubuntu 18.04.  Can't say if it was happening in other Linux distros.
I couldn't replicate this issue in MacOS nor Windows. Both were functional.
Did some work on it and tested the fix in a Vscode 1.32/Ubuntu 18.04 VirtualBox VM 🙂 Releasing the fix right now in 3.1.1. If you update, please let me know if it's working for you.

I am running 3.1.1 right now and I am still getting the error "command 'quitPlugin.keybindings.closeEditor' not found".

I can confirm same error after update

Thanks for the feedback! I'm reopening this one @dotpointer.

Hi @artdiniz. I think I've found the problem. I've made a PR which I think can solve the problem. 🙂
I've tested locally in Ubuntu 18.04 and Mac OS Mojave 10.14.4. In Ubuntu, if the file name is different from the one in index.js, then the extension does not work, generating the error command 'quitPlugin.keybindings.closeWindow' not found. For example:
Ubuntu 18.04
Files CloseAll.js and index.js (as packaged in the vsix file)
// index.js
var closeAll_1 = require("./closeAll");

This doesn't work. But renaming CloseAll.js to closeAll.js and restarting VS Code, makes the extension works again.
Mac OS Mojave 10.14.4
In Mac OS the extension works normally. I've renamed CloseAll.js to CLOSEALL.js and restarted VS Code, the extension continued working. It only stops working when requiring wrong filename (for example with typo closeAlll.js).

Thank you @thiagobraga, for pointing it out!
Bad file names in vsix package were causing the issue.
#15 fixed this in the build process before publishing to the marketplace.
Fix will be released in 3.1.2 :)
Please let me know if this fixed the issue for you!

Works for me now, thanks.

I just had this issue in the following version on MacOS.
$ code -v
1.63.2
899d46d82c4c95423fb7e10e68eba52050e30ba3
x64

I fixed it by completely quiting vscode and restart it.

authors: Shineeeee artdiniz dotpointer ericgoe richarddewit sasa-friedrich-bitlab thiagobraga

repo: artdiniz/quit-control-vscode


text:
🛑 Libreddit is down

In 0a0693d, Libreddit (https://lr.artemislena.eu) was down:

HTTP code: 404
Response time: 798 ms

Resolved: Libreddit is back up in e50ccf8.

repo: artemislena/upptime


text:
🛑 Invidious is down

In 2d72718, Invidious (https://yt.artemislena.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Invidious is back up in cfacf43 after 7 minutes.


text:
🛑 CryptPad is down

In 9c1b027, CryptPad (https://pad.artemislena.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CryptPad is back up in 9b5e086 after 11 minutes.


text:
Add signal for process_tasks start

I'm suggesting addition of a new signal, such as process_tasks_started. The signal would be emitted by the process_tasks management command, and would serve as a signal to initialize repeated tasks.
The issue raises from multiple instances of Django running in parallel (multiple web workers, MQTT client etc). When a repeated task is started from AppConfig.ready(), it's done multiple times with the current setup. With a custom signal, the initialization of process_tasks_started the initialization could be tied to initialization of the process queue, at least reducing the possibility of triggering the task multiple times.
I'm planning on implementing this on my own fork, so if this is something to be considered, I'm willing to make a pull request.

This is now implemented in my own fork: https://github.com/kipe/django-background-tasks/commit/32109a87a60249aaf2785cdbbb06b97b4de26bea
As an example usage, the signals.py for one of my apps:
from django.dispatch import receiver
from background_task.signals import process_tasks_started

@receiver(process_tasks_started)
def start_nordpool_fetching(**kwargs):
    from background_task.models import Task
    from raspautomation.plugin.nordpool.tasks import fetch_nordpool

    fetch_nordpool(repeat=Task.HOURLY)

I had the same issue, but I am also running multiple instances of workers, and if I understand correctly that would mean that the issue would still remain, it would just be triggered by the workers and not Django.
In the end I have implemented a custom management command to trigger these repeated tasks and added it to my deployment pipeline.

Yeah, this doesn't solve that problem directly. For my own use I just added remove_existing_tasks=True to the background decorator, which seemed to fix the issue. Needs further testing though.
@background(remove_existing_tasks=True)
def fetch_nordpool():
    logger.info('Task started')

authors: hodossy kipe

repo: arteria/django-background-tasks


text:
reactive_dropdown_search showClearButton not visible

Hi,
i try to use the attribute showClearButton: true. But no clear button becomes visible.
Steps to reproduce

Use Example
https://pub.dev/packages/reactive_dropdown_search/example

FormGroup buildForm() => fb.group({
        'menu': FormControl<String>(value: 'Tunisia'),
      });

ReactiveDropdownSearch<String, String>(
                      formControlName: 'menu',
                      dropdownDecoratorProps: const DropDownDecoratorProps(
                        dropdownSearchDecoration: InputDecoration(
                          hintText: "Select a country",
                          helperText: '',
                          labelText: "Menu mode *",
                          contentPadding: EdgeInsets.fromLTRB(12, 12, 0, 0),
                          border: OutlineInputBorder(),
                        ),
                      ),
                      popupProps: PopupProps.menu(
                        showSelectedItems: true,
                        disabledItemFn: (s) {
                          return s.startsWith('I');
                        },
                      ),
                      items: const [
                        "Brazil",
                        "Italia (Disabled)",
                        "Tunisia",
                        'Canada'
                      ],
                      showClearButton: true,
                    )

Result:
No clear button.

Did i miss something?
Kind regards
Marcel

Hi,
but in the ReactiveDropdownSearchWidget exist the option "showClearButton".
https://github.com/artflutter/reactive_forms_widgets/blob/b6d21cd1a3315285f2f5e44ee6c30e60bc43c483/packages/reactive_dropdown_search/lib/src/reactive_dropdown_search.dart#L94
And the parameter is in the official examples
https://pub.dev/packages/reactive_dropdown_search/example
Maybee the parameter is forgotten to remove.
I will try it with the clearButtonProps Parameter.
Thanks for the hint.


text:
Player messages not showing

Messages are showing up in the minecraft chat when typing in the discord channel but not showing in the discord channel when typing from the minecraft chat (/say works but not talking normaly)

Minecraft version: 1.16.5
Fabric-Discord Link version: 0.9.0
mods: on image
config: only changed ```
"chatChannels"
"logChannels"
"token"

(can't link the json github doesn't let me)

I got the same problem

from discord it works perfectly fine, not the other way around

Duplicate of #158

authors: GlitchyIsTrash Redo11 arthurbambou

repo: arthurbambou/Fabric---Discord-Link


text:
Metrics on overall behavior

It's ok that we somehow estimate effectiveness of this controller, but having some test scenarios with metrics, would help alot with estimating this more precisely

I think this would be quite challenging for macro-behaviors. Smaller things like smoothness and exact path following can be more exactly quantified, but system level behavior I think is very much qualitative (depending on the application and desired properties).

But in general:

Smooth non-jerky motion
Away from obstacles to a "reasonable" degree, don't skirt right up to them
"fluid" in some cases, rigid-exact-path-following in others

I don't see a way to do it fast in nearest perspective

authors: SteveMacenski artofnothingness

repo: artofnothingness/mppic


text:
Create a UserManager of sorts

Ideally something that can store / retrieve an existing user, and support all the different types of sign up / sign in flows we have.
This is the old one. Open to removing / editing / composing etc etc
@interface ARUserManager : NSObject

+ (ARUserManager *)sharedManager;

+ (void)identifyAnalyticsUser;

- (User *)currentUser;
- (void)storeUserData;

@property (nonatomic, strong) NSString *trialUserName;
@property (nonatomic, strong) NSString *trialUserEmail;
@property (nonatomic, strong, readonly) NSString *trialUserUUID;

- (void)resetTrialUserUUID;

- (BOOL)hasExistingAccount;
- (BOOL)hasValidAuthenticationToken;
- (BOOL)hasValidXAppToken;

- (void)logout;

- (void)startTrial:(void(^)())callback failure:(void (^)(NSError *error))failure;

- (void)loginWithUsername:(NSString *)username
                 password:(NSString *)password
   successWithCredentials:(void(^)(NSString *accessToken, NSDate *expirationDate))credentials
                  gotUser:(void(^)(User *currentUser))gotUser
    authenticationFailure:(void (^)(NSError *error))authenticationFailure
           networkFailure:(void (^)(NSError *error))networkFailure;

- (void)loginWithFacebookToken:(NSString *)token
        successWithCredentials:(void(^)(NSString *accessToken, NSDate *expirationDate))credentials
                       gotUser:(void(^)(User *currentUser))gotUser
         authenticationFailure:(void (^)(NSError *error))authenticationFailure
                networkFailure:(void (^)(NSError *error))networkFailure;

- (void)loginWithTwitterToken:(NSString *)token
                       secret:(NSString *)secret
       successWithCredentials:(void(^)(NSString *accessToken, NSDate *expirationDate))credentials
                      gotUser:(void(^)(User *currentUser))gotUser
        authenticationFailure:(void (^)(NSError *error))authenticationFailure
               networkFailure:(void (^)(NSError *error))networkFailure;

- (void)createUserWithName:(NSString *)name email:(NSString *)email password:(NSString *)password success:(void(^)(User *user))success failure:(void (^)(NSError *error, id JSON))failure;
- (void)createUserViaFacebookWithToken:(NSString *)token email:(NSString *)email name:(NSString *)name success:(void(^)(User *user))success failure:(void (^)(NSError *error, id JSON))failure;
- (void)createUserViaTwitterWithToken:(NSString *)token secret:(NSString *)secret email:(NSString *)email name:(NSString *)name success:(void(^)(User *user))success failure:(void (^)(NSError *error, id JSON))failure;

- (void)sendPasswordResetForEmail:(NSString *)email success:(void(^)(void))success failure:(void (^)(NSError *error))failure;

@end

We shouldn't be creating a User model here, which kinda makes it a bit tricky.
The model is really the responsibility of the app, so it should deal entirely with dictionaries, e.g. gotUserDictionary:(NSDictionary *)userDict.
Might be interesting to allow for simple method chaining because for all of the methods you're really saying "do something" then you care about got token, got user dict, auth fail and network fail but maybe you don't care about got token?

Could login return a AuthenticationProcess (really a promise, I guess) object that you could then hook up to any those methods
AuthenticationProcess *process = [auth loginWithArtsyEmail:@"sfsdf" password:@"sdaddsa"];
process.gotCredentials = ^(NSString *accessToken, NSDate *expirationDate) {
};
process.gotUserDictionary = ^(NSDictionary *userDict) {
};

... etc

?


text:
Update Grid view

Changes that match web visual styles

We'll also want to verify that we order by lot number – probably are already, but the existing design doesn't guarantee that.

authors: ashfurrow katarinabatina

repo: artsy/eidolon


text:
chore: update metaphysics graphql schema

Greetings human :robot: this PR was automatically created as part of metaphysics' deploy process. #nochangelog

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against ba556c53b7a564194e803f628e7cd92940cc3a85

authors: ArtsyOpenSource artsyit

repo: artsy/eigen


text:
feat: Add swipe-to-interact functionality to Swipeable component

This PR resolves EMI-2127

Follow-Up PR for https://github.com/artsy/eigen/pull/10879

Description
This PR adds swipe-to-interact functionality to the Swipeable component. We might fine-tune the interaction later after testing it on a real device.

PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Add swipe-to-interact functionality to Swipeable component (not used yet) - ole

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (Add swipe-to-interact functionality to Swipeable component (not used yet) - ole)

  Generated by :no_entry_sign: dangerJS against c9a7e40d8f272b828bcfaa97caa68619b47f3bfe

Not sure if I follow the need for this extra function, I think the Reanimated element already provides onSwipeableOpen, where we can control kinda the same of actionOnSwipe without any extra code. Then it's up to the caller to control it and the swipeable element stays simpler and more performant.

Maybe my PR description wasn't very clear. This new functionality is about swiping until the end without tapping on the action button (The Jira ticket has a video and better description of the interaction). onswipeableopen is only called once when the user swipes and the buttons are displayed.

Ah it makes sense, not sure about the UX since there's nothing on the DS, looks legit just one thing we might consider to change.

You are right, the UX might change. The designs for the new home view's Tasks/Notifications section are still wip...

@olerichter00 - Is there any way to make it so that element doesn't just vanish? Looks a bit clunky just popping out like that.
In Moti, there's an <AnimatePresence> component that can be used to check if something is appearing and disappearing. Ie, if
<AnimatePresence>
  {foo &&
    <MotiView exit={{ ...someExitAnimation }} exitTransition={{ ... }}>

We should lean on that, even if its a simple opacity. But better: animate the height of the container to 0.

@olerichter00 - Is there any way to make it so that element doesn't just vanish? Looks a bit clunky just popping out like that.

Yes, there are a couple of options like LayoutAnimation, Disappearable, HeighTransition, or Animated.Flastlist,that can be used to animate the item disappearing.
Because it might depend on the context, I thought it would be good to not built the animation into this component.

authors: ArtsyOpenSource damassi olerichter00


text:
add stories

The type of this PR is: TYPE

This PR resolves []
Description

PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[ ] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a changelog entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 78de2a5863ad8c6532050abea93fe9bdfba62ebb

authors: ArtsyOpenSource pvinis


text:
chore: upgrade relay to 16 [future-friday]

[future-friday]
Description
This PR updates relay to version 16

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

upgrade relay to 16 - mounir

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (upgrade relay to 16 - mounir)

  Generated by :no_entry_sign: dangerJS against d1502ffd96adbc3895f00fbef0e64baae86ad573

@olerichter00 Ci doesn't run on draft PR so I am trying to see if it will pass then fix the broken types if any

@MounirDhahri this is a great example on how the canary would help to see if we broke anything!

Will do a more thorough review tomorrow! Really excited 🔥🔥🔥🔥 Thanks for pushing this forwards!

We would need to merge this before the release to catch any issues that might be related to it

I could almost swear i updated them already following Ole's comment 😄 - will make this a draft and take a look again at it

I could almost swear i updated them already following Ole's comment 😄 - will make this a draft and take a look again at it

No worries, thanks a lot!

@olerichter00 @gkartalis
Done ✅ 126 Typescript issues 😩

😬 - happy to do a mob - maybe during mobile office hours (?) to address some in parallel?

I fixed them all already actually 😄

omg THANKS!!!

@gkartalis we don't need to worry about the breaking changes.

Let's merge this before it explodes again with merge conflicts - glad to address any comments later

authors: ArtsyOpenSource MounirDhahri gkartalis


text:
fix: error on pressing back from collection page on Android

This PR resolves PHIRE-520
Description

Passes a ref to the deregister method, seems to be required now in latest react native.
Before
https://github.com/artsy/eigen/assets/49686530/acc05967-107b-45fa-a3b6-f245101fba2c
After
https://github.com/artsy/eigen/assets/49686530/678b31d2-a176-450f-a897-312c55cf2cde
PR Checklist

[ ] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 8cba6a2bc01cdc082359372bca035e34308520bb

authors: ArtsyOpenSource brainbicycle


text:
[msg] Retry state for failed messages

If a message mutation fails, the message text will show up in the Composer again so the user can try again

oh good catch! i totally agree and will update.

On Sep 18, 2017, at 15:55, Eloy Durán notifications@github.com wrote:
@alloy commented on this pull request.
In src/lib/Containers/Conversation.tsx:

@@ -127,9 +128,10 @@ export class Conversation extends React.Component<Props, State> {

 return (
   <Composer

   disabled={this.state.sendingMessage}

   disabled={this.state.sendingMessage || !this.state.isConnected}

   value={this.state.submissionError}

I’m not a big fan of this name, I wonder if it could be something like failedMessageText ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@sarahscott looks awesome! Wanna merge the conflicts with master? Then we can 🚢  🎉 !! :D

authors: mennenia sarahscott

repo: artsy/emission


text:
write.batch_benchmarks is very slow & inefficient

...additionally suggest adding to cli

fixed by 162

repo: arup-group/pam