ReferenceError: d3 is not defined

Attempting to render the "showcase" radar chart from here and I receive the below error. I'm unsure what I would be missing here.
Let me know if you need more information.
ReferenceError: d3 is not defined
(anonymous function)
node_modules/radar-chart/src/radar-chart.js:33
  30 | //
  31 | arc : 2 * Math.PI,												//圓弧
  32 | areaShow : true,												//是否顯示一個項目的區塊
> 33 | color : d3.scale.category10(),
  34 | horizontalDashEnable : true	,									//是否呈現虛線
  35 | verticalDashEnable : true,
  36 | itemTitleGap : 6,												//縱軸上的標題間隔

My package.json contains d3:
  "dependencies": {
    "d3": "^5.5.0",
    "d3-array": "^1.0.0",
    "d3-color": "^1.0.0",
    "d3-drag": "^1.0.0",
    "d3-geo": "^1.0.0",
    "d3-hexbin": "^0.2.0",
    "d3-interpolate": "^1.0.1",
    "d3-polygon": "^1.0.0",
    "d3-random": "^1.0.0",
    "d3-scale": "^1.0.0",
    "d3-tile": "0.0.3",
    "d3-time": "^1.0.0",
    "d3-voronoi": "^1.0.0",
    ...
  }

It looks like this is an error from outside of react-vis. Our top level node_modules name is react-vis, and it appears that package giving you problems is called radar-chart.
Also tip: if you install each of the d3 sublibaries, you don't need to install the top level d3 package (or vice versa).

I understand that it's not a react-vis, but it is used by the example in the showcase here. Is there someplace else that has a good example of the Radar Chart that I can use? I'm fairly new to React (as in the last couple weeks).
Appreciate the assist.

Oh! Gotcha.
The radar-chart that is used in the showcase makes use of the fact that it is in the same file structure as the rest of react-vis. Instead you always want to invoke the top level package, like so:
import React, {Component} from 'react';
import {format} from 'd3-format';

import {RadarChart} from 'react-vis';

const DATA = [
  {name: 'Mercedes', mileage: 7, price: 10, safety: 8, performance: 9, interior: 7, warranty: 7},
  {name: 'Honda', mileage: 8, price: 6, safety: 9, performance: 6, interior: 3, warranty: 9},
  {name: 'Chevrolet', mileage: 5, price: 4, safety: 6, performance: 4, interior: 5, warranty: 6}
];

const basicFormat = format('.2r');
const wideFormat = format('.3r');

export default class BasicRadarChart extends Component {
  render() {
    return (
      <RadarChart
        data={DATA}
        tickFormat={t => wideFormat(t)}
        startingAngle={0}
        domains={[
          {name: 'mileage', domain: [0, 10]},
          {name: 'price', domain: [2, 16], tickFormat: t => `$${basicFormat(t)}`, getValue: d => d.price},
          {name: 'safety', domain: [5, 10], getValue: d => d.safety},
          {name: 'performance', domain: [0, 10], getValue: d => d.performance},
          {name: 'interior', domain: [0, 7], getValue: d => d.interior},
          {name: 'warranty', domain: [10, 2], getValue: d => d.warranty}
        ]}
        width={400}
        height={300} />
    );
  }
}


fix: remove ion-content from app component html AB#7219 AB#7220 AB#7227

@gulfaraz did this solve all 3 sub-bugs at once? either way, nice! Cannot check anything now though, because ibf-test is down.


>  and other kinds of "Blocks"?

Hi Cobertos and thanks for md2notion!
As I don't know Python well enough to use notion-py, I piggybacked on your skills and wrote a quick zsh wrapper around this script, so I can use Notion as a place to dump various system logs. Basically I take whatever comes on stdin, dumps that to file and hands it to md2notion who does a great job.
However, I'd love for somehow to be able to add "toggle" Blocks in Notion.
You know the ones that start with > in Notion, but isn't a QuoteBlock?
Possible somehow?

Woops, forgot about this one.
Are you looking to support some sort of custom Markdown > Toggle Block conversion or would you like to handle it in the script?
I can give some code snippets the next time I loop back to this

Anything goes!
What would be awesome would be somehow to use md2notion as a CLI interface to Notion. My daemonized script is trying to parse what the user is doing, and decide when the activity changed context. Continously logging to inside a temporarily named, open, "toggle", and then upon changing context, somehow retroactively changing the text in the toggle block itself, then closing the toggle block and opening a new. As in opening and closing chapters in a book, that's the idea.


Elastic Index Lifecycle Management not working as expected

Bugs should be filed for issues encountered whilst operating logging-operator.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors. #logging-operator
Please provide as much detail as possible.

Describe the bug:
I want my indices to be rolled over regularly by using Elastic ILM policies. However, the ilm policy defined in my clusterOutput is not respected.
Expected behaviour:
ILM is created by logging-operator-logging
Steps to reproduce the bug:
These are the values of my logging-operator-logging helm chart:
# Reference name of the logging deployment
loggingRef: ""
# Disable configuration check before deploy
flowConfigCheckDisabled: false
# Use static configuration instead of generated config.
flowConfigOverride:	""

nameOverride: ""
fullnameOverride: ""

# If an immutable field is changed, delete the existing resource
# and recreate it with the new configuration.
enableRecreateWorkloadOnImmutableFieldChange: false

# Fluent-bit configurations https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/#fluent-bit-spec
fluentbit:
  resources:
    limits:
      cpu: 500m
      memory: 1Gi
    requests:
      cpu: 100m
      memory: 128Mi

#Node agent Definition
nodeAgents: {}

# Fluentd configurations https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/#fluentd-spec
fluentd:
  logLevel: debug
  resources:
    limits:
      cpu: 1000m
      memory: 4Gi
    requests:
      cpu: 100m
      memory: 256Mi

  bufferStorageVolume:
    pvc:
      spec:
        resources:
          requests:
            storage: 10Gi

# Enable secure connection between fluentd and fluent-bit
tls:
  enabled: false
  # Shared key for fluentd authentication
  sharedKey: ""
  fluentbitSecretName: ""
  fluentdSecretName: ""

# Limit namespaces from where to read Flow and Output specs
watchNamespaces: []
# Control namespace that contains ClusterOutput and ClusterFlow resources
controlNamespace: ""

# defaultFlow
defaultFlow: {}

# defaultFlow
globalFilters: []

# ClusterOutputs to deploy
clusterOutputs:
  - name: es-output
    spec:
      elasticsearch:
        host: elasticsearch-master.logging.svc.cluster.local
        port: 9200
        scheme: http
        ssl_verify: false
        ssl_version: TLSv1_2
        buffer:
          timekey: 1m
          timekey_wait: 30s
          timekey_use_utc: true
        index_name: "e7-logs"
        include_timestamp: true
        logstash_format: false
        application_name: e7
        index_date_pattern: "now/w{xxxx.ww}"
        enable_ilm: true
        rollover_index: true
        ilm_policy_id: "fluentd-policy"
        ilm_policy: '{"policy":{"phases":{"hot":{"min_age":"0ms","actions":{"rollover":{"max_size":"4gb","max_age":"7d","max_primary_shard_size":"2gb"}}},"cold":{"min_age":"7d","actions":{"set_priority":{"priority":0}}},"delete":{"min_age":"30d","actions":{"delete":{}}}}}}'
        # template_name: "e7-logs-template"
        data_stream_enable: true
        data_stream_name: "e7-stream"

clusterFlows:
  - name: es-output
    spec:
      filters:
       - dedot:
           de_dot_separator: "-"
           de_dot_nested: true
      globalOutputRefs:
        - es-output

Additional context:
Elastic Index Management tells me there is a stream defined and a ilm policy, however, the policy is not equals the defined policy inside my values.yaml
Environment details:

Kubernetes version (e.g. v1.15.2):
Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc): DigitalOcean
logging-operator version (e.g. 2.1.1): 3.12.0
logging-operator-logging version (e.g. 2.1.1): 3.9.5
Install method (e.g. helm or static manifests): helm
Logs from the misbehaving component (and any other relevant logs):
Resource definition (possibly in YAML format) that caused the issue, without sensitive data:

/kind bug

Hi @volleynator thanks for the report sorry for the late reply , can you confirm this issue is still exist with the current version ?

Sorry for any inconvenience, Do you have any solution to fix the issue? @volleynator

Do we have any fix for this issue?

No fix yet?

The logging operator is only generating a config for fluentd. Please check the fluentd configuration and verify it is what you would expect. If it's not then it's a config generation issue and we (or anyone) can fix it.
If it's what you would expect than it's a fluentd plugin issue. I'm working on cleaning up and prepping a new image version for fluentd v1.15 with ruby version 3, I will update and you can give it a try.

Please try this with the following image: ghcr.io/kube-logging/fluentd:v1.15-staging

Hey @pepov, I'm having similar issues, for me fluentd created ILM policy first time I've tried it but it didn't when I've tried to add more outputs with different policies. I've tried to use ghcr.io/kube-logging/fluentd:v1.15-staging but now fluentd pod fails because of a gem conflict:
/usr/lib/ruby/3.1.0/rubygems/specification.rb:2288:in `raise_if_conflicts': Unable to activate fluent-plugin-elasticsearch-5.2.5, because faraday-2.7.4 conflicts with faraday (~> 1.10) (Gem::ConflictError)
        from /usr/lib/ruby/3.1.0/rubygems/specification.rb:1419:in `activate'
        from /usr/lib/ruby/3.1.0/rubygems.rb:211:in `rescue in try_activate'
        from /usr/lib/ruby/3.1.0/rubygems.rb:204:in `try_activate'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:153:in `rescue in require'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:149:in `require'
        from /usr/lib/ruby/gems/3.1.0/gems/fluent-plugin-elasticsearch-5.2.5/lib/fluent/plugin/out_elasticsearch.rb:20:in `<top (required)>'
        from /usr/lib/ruby/gems/3.1.0/gems/fluent-plugin-elasticsearch-5.2.5/lib/fluent/plugin/out_elasticsearch_data_stream.rb:2:in `require_relative'
        from /usr/lib/ruby/gems/3.1.0/gems/fluent-plugin-elasticsearch-5.2.5/lib/fluent/plugin/out_elasticsearch_data_stream.rb:2:in `<top (required)>'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/registry.rb:103:in `block in search'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/registry.rb:100:in `each'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/registry.rb:100:in `search'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/registry.rb:44:in `lookup'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin.rb:169:in `new_impl'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/plugin.rb:114:in `new_output'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/agent.rb:130:in `add_match'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/agent.rb:74:in `block in configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/agent.rb:64:in `each'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/agent.rb:64:in `configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/label.rb:31:in `configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/root_agent.rb:146:in `block in configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/root_agent.rb:146:in `each'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/root_agent.rb:146:in `configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/engine.rb:105:in `configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/engine.rb:80:in `run_configure'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/supervisor.rb:731:in `run_supervisor'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/lib/fluent/command/fluentd.rb:350:in `<top (required)>'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from <internal:/usr/lib/ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
        from /usr/lib/ruby/gems/3.1.0/gems/fluentd-1.15.3/bin/fluentd:15:in `<top (required)>'
        from /usr/bin/fluentd:25:in `load'
        from /usr/bin/fluentd:25:in `<main>'

the above issue with ghcr.io/kube-logging/fluentd:v1.15-staging had been fixed, can you try with it again?

Thank you, the image does start correctly but still ILM policies are not created, I've created issue in fluent-plugin-elasticsearch repo, I believe root cause of my issue is in the plugin

thanks for checking, I will close this issue, but let me know if we help on the operator side with anything


Subgraph syncing "old cursor" error

Moving this here from Slack discussion.
When syncing on hosted service, getting this error from time to time:

Text:
INFO
2023-03-22 09:37:16 a.m.
Blockstreams connected, component: SubstreamsBlockStream
INFO
2023-03-22 09:37:16 a.m.
Blockstreams disconnected, connecting, cursor: -_zKZlp9K6Q-AAhrtI2lqqWwLpcyB1xnXQjmKRdLgtnxonXH2siuVWNyPhuEkKv3iBTvTQ6qj93KQn9498EGvoTjxr9i6Sc_FCp9loi9-Oa6e_r7PwgaI7JrX7iMYtLaXTTfYQj_c7sD4t3ka6fbMREwapQuLTXm2z9V9IJdJqsX7SZjkTv1JZ2E0qiWpIQQ-eJ2F-aiwSjyUjUuLE4LO8iBZ_GavDhz, start_block: 16870271, endpoint_uri: mainnet-substreams-sf-0, component: SubstreamsBlockStream
ERROR
2023-03-22 09:36:31 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
INFO
2023-03-22 09:36:31 a.m.
received err, component: SubstreamsBlockStream

Could be related to #195 because cursor is the same

hi! does this error resolve itself after a while (and keeps progressing) ?

Info:
That cursor points to:
block #16883336 (0x7b7b727e8e27f6d027e146d6a27f1351f2e9576467baa51c3be399621b990b20)
( I use https://github.com/streamingfast/opaque to decode it)
the correct (canonical) hash for block 16883336 is 0xc4f41c2b55475d421e046491b2df9bd1a47b13ae8a9016ed65051347f4509e63
I see that we have the forked version of this block at streamingfast:
eth-mainnet/v4-forked/0016883336-3be399621b990b20-899aa0b076a807cb-16883249-default.dbin.zst
The block 16883336 came in at 13h09 UTC (it must have been live at the time, since it is a forked block)
You tried to reconnect with that cursor at 13h36 UTC.
Do you know why it took so long to reconnect ?

I remember that, to replay from old forked blocks in substreams, we had to replay UP TO THAT WRONG BLOCK (generating the bad state...) in order send the proper "undo" data. this was never implemented in case of "old forks" (from blocks out of RAM and written to disk) because of the complexity needed in substreams codebase.
At the time, we figured that this situation would very rarely happen, because the cursor is still valid for quite a number of minutes before it becomes an "old" fork.
Do you have any insight on why it would have disconnected at 9h36 and try to reconnect with a cursor of a block from 9h09 ?

hi! does this error resolve itself after a while (and keeps progressing) ?

Here's a list of this error events (searched by "old cursor" keywords). Seems to go away. No real pattern - could go many hours without it, then happening every couple of minutes, etc.
ERROR
2023-03-22 09:44:12 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 09:43:24 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 09:36:31 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:57:57 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:57:11 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:56:26 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:55:40 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:54:55 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:54:09 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:53:23 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:52:38 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:39:41 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 08:38:55 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:56:42 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:55:53 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:55:03 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:54:13 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:53:23 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:52:33 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:51:42 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:45:04 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:44:13 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:43:24 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:42:34 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:41:44 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:40:55 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:40:05 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:39:15 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:38:25 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:37:34 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 03:36:42 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:52:48 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:51:14 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:50:26 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:49:39 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:48:51 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:48:03 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:47:16 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:46:28 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:39:39 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:38:52 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:38:05 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:37:17 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:35:43 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:34:55 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-22 02:34:05 a.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 03:08:36 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 03:07:42 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 03:06:48 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 03:05:55 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 03:05:03 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 02:58:10 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 02:57:16 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 02:51:08 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 02:50:09 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 01:26:07 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 01:25:19 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 01:24:32 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 01:23:44 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 01:22:57 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream
ERROR
2023-03-21 01:22:09 p.m.
An error occurred while streaming blocks: status: Internal, message: "cannot resolve 'old cursor' from files in passthrough mode -- not implemented", details: [], metadata: MetadataMap { headers: {} }, component: SubstreamsBlockStream

^ I don't see how it could go away... do you have proof that the cursor (and subgraph) is progressing ?

It was receiving recent blocks and applying entity operations, so I assume it was progressing:
INFO
2023-03-22 10:24:09 a.m.
Applying 3 entity operation(s), block_hash: 0xe415b1b8d639f5a69c3c5b097365436197fd7ff9522740f0fd15d70cccf59226, block_number: 16883702
INFO
2023-03-22 10:23:48 a.m.
Applying 3 entity operation(s), block_hash: 0xaec2c9ab2493a2cb51bc3888e79cb7488ea922ff9f67ca5b98fdd0414a0934f9, block_number: 16883701
INFO
2023-03-22 10:23:37 a.m.
Applying 3 entity operation(s), block_hash: 0x3fff3b7a6b02185bd5e3543691856e6640b23267e6ded47ce29ff97c3c6a9be9, block_number: 16883700
INFO
2023-03-22 10:23:26 a.m.
Applying 3 entity operation(s), block_hash: 0x2b8fe013025f7e422878c4636abdabc178f6275449c52c896364fdd9f4cd6c1d, block_number: 16883699
INFO
2023-03-22 10:23:13 a.m.
Applying 3 entity operation(s), block_hash: 0xc72b7335574b8f7d997603a92397d2d085f312286f35c430f804a414a80977df, block_number: 16883698
INFO
2023-03-22 10:23:02 a.m.
Applying 3 entity operation(s), block_hash: 0x7179bb1e873f15453e4750ed357d4896a17c131890421ee4590283462bf1b991, block_number: 16883697

I am very worried about the fact that it eventually started working. I will schedule some time to dig deeper into this this week or next week...

the main issue will be resolved by #199 .

I found out why it started working at some point:
when handling undo, in the case where we restarted directly from a cursor, the "content to UNDO" was actually not produced, so it is not part of the f.reversibleOutputs map, so the message is ignored:
https://github.com/streamingfast/substreams/blob/develop/pipeline/forkhandler.go#L36-L43
This is not pretty, because it means that your data may be corrupted after that point, since your instance did not perform the 'undo' operation.
Unfortunately, we cannot fix this issue directly without addressing this:
https://github.com/streamingfast/substreams/issues/199  (which will soon be implemented, but requires a change in the protocol)

https://github.com/graphprotocol/graph-node/issues/4531
^ graph-node side of implementation.

Is this still an issue? If so re-open the ticket


Chords sound "noisy"

When multiple notes are played it divides the wavelength by the amount being played, resulting in a more "impure" sound, as if one note were to be played with no notes in between (the periods of the notes that would be there).

I have found something very interesting written by someone here where they mention using pulse frequency modulation (same as PWM) combined with Pulse Interleaving to achieve polyphony. This works by changing the pwm duty cycle while keeping the same frequency allowing other information to be "inside" a single signal. For example we can have a 440Hz signal (A4) with a duty cycle of 1% on 99% off, and "inside" it we can have a 880Hz signal (A5) with a duty cycle of 2% on and 98% off, and so on; assuming the frequency remains the same

this would look something like this
1 signal: |‾|____________________________________________________________________________________________________|‾|
2 signals: |‾||‾‾|________________________________________________________________________________________|‾‾||‾|

normal signal would look like this:
|‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾|__________________________________________________

Also, after actually listening to one bit music, I've realised that literally nothing was wrong and this is how it was supposed to sound. So, I'm just going crazy.


Tech Doc?

Great framework. I am amazed by how easy it is to set up.
I believe there are 2 kinds of docs which are missing:

Tutorials and concepts explanations
Discussion and articles of how its core is designed and implemented.

This first one is for users to quickly start to write applications. It has examples right now, but not enough. The communities can probably contribute examples slowly.
I am personally more curious about the second. As far as I can tell, it's compiling CSS and HTML to platform native UI (directly to render engine?). I don't have much native UI experiences, therefore I can't tell if this framework is using web technologies or not for rendering at the pixel level. As you mentioned here https://github.com/murlokswarm/app/issues/21#issuecomment-277428710, I am also looking for a technology to allow me write native UIs with HTML and CSS for the views but without JS. Therefore, I wonder where this project is going.
If the devs can write an article to explain some of the low level tech details and design decisions, that will be super helpful and insightful!

Hi, thanks for the feedbacks.
It will be a little bit hard for me to produce a doc explaining what is going on under the hood but I can give a summary of the general ideas here:
General

Uses a web view only for UI
Uses Go for all the other things.
There is a virtual Dom written in Go, all the computations to parse a template and to do the diff between current state and new state is native Go code.
There is the app.Driver interface that describes the available operations between the app package and the platform used (Mac, web).

Mac

Uses WKWebView as a web view.
Uses OBJC and Cocoa to create window and all other macOS related stuff.
A RPC like API is written in C to make a bridge between Go and Cocoa.
This RPC calls are done into the mac.Driver implementation.

Web

An app.Driver implementation is compiled with Gopherjs. It is loaded in the browser and handles rendering.
An app.Driver implementation is compiled in Go. It creates a web server that will serve files and the goherjs driver.
The gopherjs implementation talk directly with javascript call since all is transpiled in javascript. No bridge to implement since gopherjs is the bridge.

Futur driver

Will work with a similar way as the mac driver.

Maybe we could use this post for specific technical questions and compile the answers in a wiki page.
That would allow me to incrementally focus on a precise question and not spend that much time to figure out what people want to know about it.

What about creating a GitHub pages branch with documentation?

Hi there, just giving some news about this issue.
I had been working for a while on the next version of this package and I'm currently finishing up things for a near to come release.
While there will be breaking changes, documentation will be available as examples in the demo directory and in the Github Wiki.
You can take a peek here.

@maxence-charriere wiki looks nice, but IMO would be also cool to have a web page with same content, built with app and Tailwind or anything else, alongside wiki

I totally agree with this. It will come eventually. Right now focusing on having decent documentation for the next release.

Hello there, I just released v6.0.0.
https://github.com/maxence-charriere/go-app/pull/349
As mentioned before, it brings a wiki and some demo examples.
Doing a website could be done eventually. In the meantime, I'm closing this ticket.
Feel free to open other issues if something is missing.
Best,
Maxence.


Won't work

I don't know what im doing wrong but il add the library to my project and it wants me to add "new" before calling GlimpseTransformation in Glide. Any suggestions?

It sounds like you're trying to use a sample code written in Kotlin in a Java context (?)

https://github.com/the-super-toys/glimpse-android/blob/master/sample-app/src/main/java/glimpse/sample/TestingApiFromJava.java

I was trying to add glimpse into my wallpaper app and where glide pulls the image from the url, i was going to use glimpse to show a better view of the image being processed but where i add the glide transformation, it wanted me to input "new" beside GlimpseTransformation and didn't understand why

Feel free to reopen the issue with a stacktrace or screenshots showing the issue, with the current information it's not possible to provide further support

https://www.dropbox.com/s/x6k708otbozbh2m/Screenshot from 2020-08-13 15-38-30.png?dl=0
its doing this, what am i doing wrong

ok so i had to add tensor flow to my gradle file and it works now and add new before initializing it


Error when extending the kubernetes cluster, lost payment

I received this error message when trying to extend the k8s cluster on the vdc,  after the payment and the transaction has not been reverted ( lost payment)
any ideas on how to solve this?

@BenjellounO Can you add more information ? where did you deploy that, vdc name, the workloads ids, is the vdc in grace period or not ?

Well, seems it's same as https://github.com/threefoldtech/js-sdk/issues/2542, vdc entered grace period

verified
extended the cluster successfully as the vdc still away of the grace period


Refactor of entire project

I've been working on refactoring this project.
Here are a summary of improvements:
General improvements

refactored entire project with a rollup build configuration
added package.json
added prettier
moved JS to ES6 modules over IIFE
removed iconInput.js (Figma no longer highlights icons on focus on inputs)
replaced SCSS vars with CSS vars to share variable/base with Figma Plugin DS Svelte
introducing new base also adds a selection of utility classes for flex / spacing
improvements to switch, checkboxes and radio buttons

Select menu improvements

added disabled states
automatically reinitialize menu when menu items are modified
expanded drop down will scroll and ensure menu fits within plugin iFrame
icon ability to include an icon within input

Closing this as I have abandon Rollup in favor of Gulp; greatly simplifies things and better plugin ecosystem as far as inline sources is concerned.


Wagtail version no longer visible in settings menu

Issue Summary
The wagtail version no longer appears in the Settings sub-nav, where it was added in #2769.
Initially I thought this was an HTML change, but the text is still there, it's just the same colour as the sub-nav background.
Steps to Reproduce

Start a new project with wagtail start myproject
Add an superadmin user
Log in to the admin panel
Click settings
Optionally, try and highlight the bottom of the settings panel, so you can see the version there

This used to be visible with a low contrast (possibly non-compliant) colour difference from the background of the nav.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes. Noticed it in one of the Squash builds

Technical details

Python version: 3.6.1
Django version: 2.1.7, 1.11.18
Wagtail version: 2.5a0, 2.3
Browser version: Chrome 73

Thanks for the report @haydnnewport! This will be fixed in Wagtail v2.6 (#5236).


[AutoPR sql/resource-manager] Update swagger file and examples with time zone parameter [DO NOT MERGE]

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5224

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/3769


New Features

Image-Sample.txt
Hi,
I tried to fork as add 2 fields to the metadata section of a post, without success. In my case, I use the following  https://github.com/ptsteadman/hexo-theme-corporate.git which when opened will show additional fields thumbnail and lede for each post.
If possible I would like those feilds added to the edit/insert mode of a post. It would also be awsome to add an uploaded image the thumbnail section along with the body. The following is an example
Image-Sample.md also attached as txt file.
title: Image Sample
tags:

image
test
categories:
hexo
date: 2016-09-03 13:30:00
thumbnail: http://localhost:4000/images/1483213724160.jpg
lede: "Hexo makes incredible static websites. Hexo Hey gives programmers, UX designers and end users the ability to add posts and allows for drag and drop images
that really stand out."

Upload an image using drag and drop
Abstract piece # 3

Thanks,
John

I know your concern, I think the easiest way for you to achieve it is write the mete section in the body directly
I'm planning to refactor this project this month, thanks for your interest

I know your concern, I think the easiest way for you to achieve it is write the mete section in the body directly
I'm planning to refactor this project this month, thanks for your interest

i think I tried the body but since it's past the meta section it does not get picked up. I'm willing to contribute some funds if interested. I was using hexo-admin and find your solution better fits my needs.
FYI, while I still have many angular 1.x apps I've moved on to Aurelia and react-native for all new stuff.
Thanks and Happy New Year
John

i think I tried the body but since it's past the meta section it does not get picked up. I'm willing to contribute some funds if interested. I was using hexo-admin and find your solution better fits my needs.
FYI, while I still have many angular 1.x apps I've moved on to Aurelia and react-native for all new stuff.
Thanks and Happy New Year
John

Aurelia is worth a look, more of complete framework than react which is why I use it for my desktop apps. I live in nyc and goto all Angular meetups and felt NG2 too verbose and difficult. Aurlia follows standards and is quite fun to work with.
John

Aurelia is worth a look, more of complete framework than react which is why I use it for my desktop apps. I live in nyc and goto all Angular meetups and felt NG2 too verbose and difficult. Aurlia follows standards and is quite fun to work with.
John

Hi,
Just checking on the status of the refactor if its still something on your plate.
Thanks,
John

yes, I will start after update one of my app, should be by next week, thanks for your remind

Just checking to see if you still have plans with this repo


Why keep non-tether css?

Both tooltip and popover keep maintaining a .tooltip-[direction] and .popover-[direction] classes, in addition to the tether classes:
// from scss/_tooltip.scss
  &.tooltip-top,
  &.bs-tether-element-attached-bottom {
    padding: $tooltip-arrow-width 0;
    margin-top: -$tooltip-margin;

I admit these non-tether classes are prettier than the tether ones, but they increase the minified bootstrap.css by almost 1k (see non-minified compare), and I can't see the purpose they fulfill. Perhaps it's a relic from the pre-tether era.
Worth mentioning that these classes are currently used in the docs in the static demo section. Even so, they can be easily replaced by the tether classes:
--- docs/components/tooltips.md	(date<PHONE_NUMBER>000)
+++ docs/components/tooltips.md	(revision )
@@ -50,7 +50,7 @@

-

+

       Tooltip on the top

Is it PR worthy? Notice that this will be a breaking change (in case someone relied on these classes), so it might be worth considering before the beta release.

Just one thing to consider: we (https://ng-bootstrap.github.io) are building Angular-specific widgets based on Bootstrap CSS and we do not use tether for positioning. So the proposed change would be indeed a breaking change.
But I feel like the proposed change would impact anyone just writing CSS (without using JS to open tooltips / popovers) - not only a breaking change but also a more verbose alternative.
More importantly I feel like the proposed change would "leak" internal implementation details of Bootstrap (3rd party lib being used). Since I think I've seen some chatter about replacing tether with sth else so the mentioned "leak of impl details" would play a role here.

Bum, speaking of replacing tether: #22444 :-)

good points @pkozlowski-opensource , when you put it like that it's worth the extra k.

We'll leave them as-is until we determine what we're doing with the Tether replacement.


s3 multipart: uploading same part twice results in duplicate data in 0.4.1

Hi guys,
I just upgraded from 0.4.0 to 0.4.1 and one of my test started failing.
When uploading the same part twice, data should be overwritten on S3, but starting with 0.4.1 data seems to be duplicated.
Here's a script that demonstrate the issue:
import boto
import moto

from io import BytesIO

m = moto.mock_s3()
m.start()
s3 = boto.connect_s3()
bucket_name = 'bucket'
s3.create_bucket(bucket_name)
bucket = s3.get_bucket(bucket_name)
mp = bucket.initiate_multipart_upload("test1")

data = b'0' * (5*1024*1024)
written_data = ""
mp.upload_part_from_file(BytesIO(data), 1)
mp.upload_part_from_file(BytesIO(data), 1)
written_data += data
mp.upload_part_from_file(BytesIO(data), 2)
written_data += data
mp.complete_upload()

content = bucket.get_key('test1').get_contents_as_string()

print "written_data len: ", len(written_data)
print "s3 content len: ", len(content)

m.stop()

Output from 0.4.0:
written_data len:  10485760
s3 content len:  10485760

0.4.1:
written_data len:  10485760
s3 content len:  15728640

I think this is fixed now. Please reopen if you see anything funny.
Thank you for reporting the issue and your help!

Nice,  thanks!


Profile Disease

Requester information

Name-
Eric Torstenson

Affiliations-
VUMC/AnVIL

Request Details

Purpose-
Condition maps very well to a researcher's Disease, however, our use of verificationStatus isn't exactly the same as the original intent and profiling these would allow us the opportunity to clarify what is to be expected when working Conditions of this sort. We can also restrict the codes to only the relevant codes to avoid misapplication or confusing data sneaking in.

Who it benefits-
Any research project in which there is a need to express Affected/Unaffected status to a disease.

Use case-
A dataset in which there is a traditional status of affected/unaffected can more clearly indicate their cases and controls using this profile.

This should likely align with the Phenopackets concept of Disease: https://phenopackets-schema.readthedocs.io/en/latest/disease.html including their recommendations for terminology to utilize.
Do we have some text we can use to describe the verificationStatus?

Re verificationStatus, I commented on a wrong issue, but here is my initial thought: https://github.com/ncpi-fhir/ncpi-model-forge/issues/35

@allisonheath Sorry, I forget that not everyone has been a party to our discussions here at vandy.
Our current implementation for CMG fhir plugin uses the following:

Confirmed => Affected
Refuted => Unaffected
Provisional => Possibly Affected

@liberaliscomputing, I couldn't find your comment.

@torstees, the first comment on this issue:  https://github.com/ncpi-fhir/ncpi-model-forge/issues/35 (my comment was on a Specimen issue, but the argument itself is about Condition.verficationStatus.

@torstees ok great, I think that aligns with how we want to use this for KF data as well. And the agreement was for now if something was not reported / unknown / etc., we would just leave it out, correct?

@allisonheath That is my understanding

In addition to verificationStatus, our team is also interested in capturing information about tumor progression/recurrence in the condition resource and clinicalStatus seems like it could be a good fit. Our recommendation is to use the required code set within this field to indicate active/inactive status and add a SNOMED code set to capture additional detailed information.

eigdwh_69.diagnosis
Condition.clinicalStatus
SNOMED CT

Initial CNS Tumor
-
86049000 or 372087000

active (level 0)
55561003

Progressive
-
255314001

-
remission (level 1)
277022003

-
relapse (level 1)
263855007

-
resolved (level 1)
723506003

Recurrence
recurrence (level 1)
246455001

Secondary Malignancy
-
128462008

-
inactive (level 0)
723506003

Section 3.1 in this document provides a more detailed description of our thoughts on this field. https://docs.google.com/document/d/1I-4OkQaUiFnVQbpXxplmTIVpdnfptSzMqnQvBYvLCC4/edit

In line with Nick's comment, our recommendation for verificationStatus is first select from the required codes and then add extra concepts from SNOMED CT (if our enumerations are not coverd by the required ValueSet).


Fix misspelling in removeLibCoreClrTraceProvider function

This PR corrects a very minor spelling mistake within the removeLibCoreClrTraceProvider function of src\coreclr-debug\main.ts.

:+1:

while I am sure this has no meaningful impact, we are locked down right now for RC2. Can you resubmit this against the dev branch and I'll merge it there?

A new PR (https://github.com/OmniSharp/omnisharp-vscode/pull/278) has been submitted for the dev branch. Closing this PR.


Proxied messages don't appear in console

Proxied messages don't show up in the server console

Expected behavior:
Something like [xx:xx:xx INFO] (Kaytastrophe) <Strawberry> this is a proxied message appearing in the console.

Fixed this issue in v0.4.11 (bdd700c), thanks for the report!

Will probably add an option, enabled by default, to have the username logged too, which would be helpful for administrative purposes, as you've suggested, but for now I'm just logging what players are shown.


Autocomplete member selectivity

This removes completions for TestClass::SOMETHING_ELSE when completing for TestClass::NOT_SOMETHING_ELS|. Same for -> completions.
This is based on #599 so this cannot be merged before that, and only the last commit contains any meaningful changes.

Is this still relevant?


Update Configuration to use URL for Callback URLs

Previously, the Configuration object kept track of Callback URIs as Strings.
The correct type is URL, and upon the process of making changes to authenticators I decided to change this to URL across the board to reduce the need to convert between the two types.
We also change the useFallback parameter to default false, as this parameter is only used to fall back to the Authorization Code flow. Since the end developer needs to set up a server to use Authorization Code flow, we make that usage opt-in.

Couple small changes, otherwise looks good.


Bulgarian translation for 12factor.net [WIP]

Started translating the 12factor.net website in bulgarian language.
Help from the community is appreciated.

This translation PR changes and add unrelated files for a Docker configuration.
While I suspect the maintainers will appreciate your contributions, those changes should be proposed in a separate PR.


Create Game Blank Screen

This is likely my own user error as not being very familiar with docker just yet.   But when I attempt to create a game, I am presented with a blank screen.   And similar, when I press on 'cockpit' in the top, I also receive a blank screen.
My main steps were to git clone the front and back ends, create an .env file and docker compose up.
Then within portainer, I have restart each container assigning the ports.
I can then access the front end.
Again, I assume this my own errors, but not sure where or what steps I may be doing incorrectly.
And any help is greatly appreciated.
Thank you

Hi, would you try to add:
COCKPIT_URL=https://buttons-against-humanity.github.io/decks/full.json

To the .env file and execute docker-compose up -d ?

@macno.
Thanks for trying to help me out, and still suspect just my setup or stupidity with docker.   I'm trying with Alpine Linux and
I changed the COCKPIT_URL to the above but still get the same result after restarting docker-compose up.    The front end starts.  When I press join a game, I see the option to enter an ID.   But pressing create a game or cockpit just gives me a blank screen.
My full .env file is:
PORT=8080
LOG_LEVEL=debug
RESTART_MODE=unless-stopped
FQDN=localhost
#COCKPIT_URL=https://github.com/macno/json-against-humanity/raw/full-json/decks/family.json
#COCKPIT_URL=https://github.com/macno/json-against-humanity/raw/full-json/decks/full.json
COCKPIT_URL=https://buttons-against-humanity.github.io/decks/full.json
SLACKIN_URL=https://slack.buttonsagainsthumanity.com/
Used to force a COCKPIT reload via API, it's sha256 (Authorization: Bearar secrett+ttoken)
ADMIN_TOKEN=514a1cd20c03cd8a234dca0fddb87cf53a26bb7b2a66e2aae62a0a544237f96b
Set MULTI_NODE to 1 to enable support for replicas
It requires a redis instance available
MULTI_NODE=0
STICKY_COOKIE=bah-sticky
REDIS_HOST=cache
REDIS_PORT=6379
REDIS_OPTS={"socket_keepalive":false}

could you paste the output of docker-compose logs be  ?

It looks like the server may not be starting?
adocker:~/bah-backend# docker-compose logs be
Attaching to bah-backend_be_1
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:40.293Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:41.512Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:42.680Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:44.100Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:45.884Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:53.870Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:55.170Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:56.460Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:57.877Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:33:59.667Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:34:02.311Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:34:06.525Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:34:13.976Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:34:27.803Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:34:54.424Z","v":0}
be_1       | {"name":"bah","hostname":"3e86d9ec071c","pid":1,"level":50,"msg":"Unable to start server cards.forEach is not a function","time":"2020-07-09T16:35:47.540Z","v":0}

I'm sorry, the latest images have some bugs. They have been already fixed, could you update your docker-compose.yaml to use these images:
  be:
    image: buttonsagainsthumanity/bah-backend:0.11.0-beta.0
  fe:
    image: buttonsagainsthumanity/bah-frontend:0.9.0-beta.0

Meanwhile I already pushed a new tag, so once the images are build and published you can switch back to use latests
Sorry about that

Images published

Well, I changed my docker-compose to use the beta images. and log shows "Attaching to bah-backend_be_1" with no errors.
But still stuck on that blank screen when creating a game.    I thinking it must be something I am doing and not the game or code, just can't figure it out.   I've tried with Alpine Linux and Ubuntu Server installs.  Docker compose up gets things goings, and then i am using Portainer to publish all the ports.
And I can access the front screen, just get that darn blank screen when pressing "create game" or "explore all extensions"
And accessing the back end appears be running and shows in a web browser:
{"name":"bah-backend","version":"0.11.0-beta.0"}
And my .env file is using the Cockpit url of:
COCKPIT_URL=https://buttons-against-humanity.github.io/decks/full.json
I must be missing something, probably a very easy thing I'm just doing incorrectly.

if you open the browser's console, do you see any error? Which URL are you using in your browser http://localhost?

I'm doing everything inside a VM using proxmox as my baremetal hypervisor, which may or may not be part of the issue.   So I do not visit http://localhost, but rather the IP address of the VM.   And VM's are running Alpine Linux and Ubuntu Server with no GUIs.
Should we be accessing it directly on the IP address at port 80?  ie, 192.168.xx.xx?   I just did a clean install of Ubuntu Server (as a VM) with no other dockers installed and latest docker images.  When I ran compose-up, that log showed an error of:
Attaching to bah-backend_be_1
be_1       | {"name":"bah","hostname":"69fdb7a89b1f","pid":1,"level":50,"msg":"Unable to start server Only absolute URLs are supported","time":"2020-07-10T13:26:24.364Z","v":0}

On my previous attempts, I have had the Portainer docker installed first, and then after running compose-up via CLI for buttons, went back to portainer (port 9000) and assigned the FE and BE specific ports to publish to ports 80 and 8080.   I could then in a browser open the game that directed to port 8080 with something like.  192.168.xx.xx:32768   where 32768 was publishing the port to 8080 for the FE container.   But was still stuck at blank screen when trying to create a game.
And thank you for all of you help.  You have gone above and beyond in attempting to help me trouble shoot.  If you have any kind of donation link for the game, I would be more than happy to make a donation.

Did you remove traefik from the docker-compose.yaml ? It supposed to be there since it proxies the requests to the BE and FE containers (their ports are not exposed).
if the port 80 is already busy, you can change it to 8080, for example:
  traefik:
    image: traefik:v2.2
    restart: ${RESTART_MODE}
    command:
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
    ports:
      - "8080:80"


SSL/TLS configuration

The Vert.x clients have some options for configuring SSL/TLS. Do we need to expose that stuff as properties?

The Vert.x clients have some options for configuring SSL/TLS. Do we need to expose that stuff as properties?

@Sanne any idea?

After investigating further, it seems that this API is way too complex to be configable via properties. So instead I introduced an API that lets you do it in code.
See #334.


Calendar.java needs to be able to sort the vevents by their start date

In order to compute the 'great circle distance,' the events that are taken in first have to be sorted. Note that this will break one of the tests. DO NOT SORT UNLESS ASKED TO :smiley:

I will go ahead and leave a stub for the sorting method. Note that the sorted elements are in a dynamically allocated array list and cannot be grabbed by index. This means that a O(n^2) may be required.

This method should also be able to be called by the user in Interface.java. I have opened a seperate issue for modifying Interface.java for whoever wants to take it.

@marcodlk finished this issue


feat: U45N supports single QDMA design

Without using num_qdma option, (by default) U45N can be built with a single QDMA as other Alveo cards. The interface to Arm SoC is disabled in this case.

Needs some additional changes. Will submit later.


Update k8s 1.20

https://github.com/rancher/rancher/issues/30556

https://github.com/rancher/rancher/issues/30556

https://github.com/rancher/rancher/issues/30134

https://github.com/rancher/rancher/issues/30134


Slow IntelliSense  in files with 4000+ lines

VSCode Version: 1.18.1 (latest)
OS Version: MacOS 10.12.5

Steps to Reproduce:

Open SCSS (or css) file with 4000+ lines of code
Try to quick type  dn (tab)  it must write display:none;  but it take around 1 second wait and only after it shows suggestions.

So as much larger scss (css) file as much slower works intelliSense, in files with 5000 lines i need wait about 1 second until it works.
In file with 11000 i need to wait  2-3 seconds.
Here is a ScreenCast (video)  so you can see this issue in REAL life.
https://monosnap.com/file/cERAp6q0qTuQks723H4ZVLfZgeuEG8

Reproduces without extensions: Yes

Anything will be slow at that many lines. I'd suggest breaking the file up, because that will slow VS Code down.

Thanks for the answer, but in my opinion it shows bad optimisation  of vscode, because i have been tested same files in  PhpStorm, and SublimeText3, and everything works perfect and super fast.

Hmm maybe reopen it for a response from the team, but I doubt they’ll say anything different. VS code is very well optimized, so it could just be that you’re dealing with a massive file.

Okay i open issue again,  I just want to say , the file is very small it is only 100KB starting slower, and with 250KB i need to wait 3 sec for IntelliSense .   Editor works perfectly, nothing lagging , tabs switching very fast, the problem is only with IntelliSense.

@skhtml Do you have any extensions installed that are providing intellisense other than what is already built in?
For css/scss, there are 2 built in extensions that provide intellisense

css
emmet

Run code --disable-extensions (to disable external extensions), add the below in your settings to disable emmet from providing intellisense and let us know if that makes any difference.
`"emmet.showExpandedAbbreviation": "never"
This will help us in narrowing down which of the extension is causing the lag.

For testing i already disabled all extensions.
As you ask, i disabled emmet in  vscode config with line
"emmet.showExpandedAbbreviation": "never"
After that , all emmet siggestions was gone, but build in suggestions was remain.
Also when Emmet was enabled  i wait 3 sec for suggestions, now i wait only 1-2 seconds.
I make a little video(screencast)  for you , so you can see  problem
https://monosnap.com/file/uM9lE7U6zNdMG7m6IRoI24otF8Yk2x
I will test it on Windows too later

@aeschli Thoughts on the 1-2 seconds time taken by css completions? Is that expected or we want to work towards a better experience for large files?

Actually, even 1 seconds it is very long,  because when  coders write css  they  use suggestions  everytime (every Line)  like:
w10  ->  width:10px;
r10p -> right:10%;
fz12 -> font-size:12px;
and etc.
on others Editors suggestions shows immediately (in files 100KB +)  but here it takes time (around 1-2 sec on each suggestion)
Thats why i create issue, it need work.  Also i think this is not only emmet problem because default suggestions also slow.
If it helps, I can give you 2 .SCSS files . one small (where suggestions works fine) ,  and one big (250KB) where its work bad.

@skhtml If you can provide the files that would be great so I can investigate what's slow.

Here is archive with 2 files
scss-for-test.zip

Thanks for the examples. I made some performance improvements, please give it a try.


Merge remote-tracking branch 'origin/master'

Merge remote-tracking branch 'origin/master'

Address comments and merge :+1:


How to set the img_scale parameter？

I am using the mask_rcnn_r50_fpn_1x.py configuration script. I have prepared my own data. I found that objects with smaller targets in my data were not recognized. My image size is (2748, 3840) and the smallest object is probably (36, 36).
How should img_scale be set?
Is it guaranteed that the minimum object pixel is greater than 1 after four times of downsampling?

When I set img_scale to (1374, 1920), the smallest object can be identified.
Still curious, what is the smallest object that can be detected? Four pixel sizes?
I am very much looking forward to someone to answer. Many thanks.

I also have the same puzzle.  Do you try to train model with the orginal size?

When I set img_scale to (1374, 1920), the smallest object can be identified.
Still curious, what is the smallest object that can be detected? Four pixel sizes?
I am very much looking forward to someone to answer. Many thanks.

I think it depends on the anchor size. By default, the anchor size (after scaling) would be (32,64,128,256,612). So the smallest anchor size is 32x32. Let's say your ground-truth bbox is MxM, if MxM/(32x32) < 0.3, it will be recognized as background. So I think there are basically two ways to solve this problem: 1): crop your image and zoom-in each part by 2X or even 4X. By doing so, your ground-truth bbox size will get larger; do not try resizing the image using img_scale, coz a very larger size would consume up all GPU, hence introduce long latency. 2): adjust the anchor size in mask-rcnn/faster-rcnn etc.

crop your image and zoom-in each part by 2X or even 4X. By doing so, your ground-truth bbox size will get larger; do not try resizing the image using img_scale, coz a very larger size would

very thank~
I am using mask_rcnn_r101_fpn_1x.py
1 、If I want to modify the cropped image, is it to modify the code getitem?
2 、anchor size  modify here?Set to 0.2 or less?

I saw the code.
If I want to detect smaller objects, I should modify the anchor_scales.
If I modify anchor_scales=[4]. Anchor_strides=[4, 8, 16, 32, 64]. Anchor_scales*anchor_strides=[16, 32, 64, 128, 256]。Where is parameter 0.3 set?

I'm still puzzled, if I use the anchor-free detection methods, and I use my own dataset, how should I set img_scale?


Book class incorrectly styles running headers

The current book cleass has some self defeating code resulting in unwanted indents in the header. The indents are removed, but outside of the closure that brings back in settings from elsewhere. The order of operations needs to be reviewed.
Concurrent to that specific issue, it seems there is some conflict of interest between functions which set content and functions that define style. These interests should be separated so that more than just indenting doesn't get messed up.

Reviewing the header output code, the logic is clearly broken. The style overrides need to be inside the closure.
https://github.com/simoncozens/sile/blob/c6a0c07911e50448acea660fcaf9a7d1a8bdaa55/classes/book.lua#L64-L82
https://github.com/simoncozens/sile/blob/c6a0c07911e50448acea660fcaf9a7d1a8bdaa55/classes/book.lua#L86-L89
In my publishing toolkit I see I've split the function that sets the header (\left-running-head) from the one that outputs it (\output-left-running-head). This results in a place where you can override default styling without messing up storing of the content in the expected variables.
https://github.com/alerque/casile/blob/f47396d72d5f37f20d35440c1f364c8e046b2025/cabook.lua#L25-L32
https://github.com/alerque/casile/blob/f47396d72d5f37f20d35440c1f364c8e046b2025/casile.lua#L99-L101
https://github.com/alerque/casile/blob/f47396d72d5f37f20d35440c1f364c8e046b2025/casile.lua#L127-L149


Improve travis CI integration

Only run the code coverage once. Slightly speeds up the other builds and should stop the duplicate notifications from coveralls.

Pull Request Test Coverage Report for Build 39

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.045%

Totals

Change from base Build 38:
0.0%

Covered Lines:
215

Relevant Lines:
247

💛  - Coveralls


UI: 2FA code entry field is a "counter"

Gitea version (or commit ref): 30560b0
Git version: 2.15.3
Operating system: Docker image (on Debian 9.6 stretch)
Database:

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

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

[x] Yes
[ ] No
[ ] Not relevant

Log gist: most probably not needed

Description
The field for the 2FA code is a "counter" field. Repro: login on a 2FA enabled account.
Screenshots

This is the expected behaviour since this is the input type number. The "counter" is feature provided by your browser.


Add Ecto type support

Adds support for the Ecto.Type behaviour (#12) without requiring Ecto as a dependency.
If a project doesn’t have Ecto, the Money.Ecto.Type module will be ignored.

:+1: I do like this impl.


chore: simplify dtslint tooling

Description:
The PR that I opened to have the localTs path resolved has been merged and a new version of dtslint has been published, so there is no longer a need to pass an absolute path via the command line.
This PR removes that script that was used to pass an absolute path to the local TypeScript install and passes a relative path, instead.
Related issue (if exists): None

@cartant Looks like we just need the conflict resolved and this is good to go.

@benlesh Conflicts in this should be resolved. I've not resolved those in #4790 because - AFAICT - it will conflict with the changes in this PR. I'll resolve #4790 after this PR is merged.


Added pglogical packages and repos

Pull pglogical packages from copr repo.
@Fryguy @gtanzillo @jrafanie

Should be merged with https://github.com/ManageIQ/manageiq-appliance/pull/57

note: This needs to be merged before 57, not at the same time as 57. So just merge this and don't wait for turn key synchronization.
This is very exciting.

@kbrock correct.  I'll make an edit.

Looks good

@carbonin should we hold off on merging this until nightlies are working again following the rails 5 update?

I don't think it really matters ...


Remove vapor-demo

Proposed Changes
Removed the vapor-demo package and the related build config.
@GermainBergeron any idea how to shut down http://vapor.surge.sh/ and http://coveo.github.io/vapor/ so that we don't have 3 demos up and running?
Potential Breaking Changes
http://vapor.surge.sh/ won't be deployed anymore.
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Codecov Report

Merging #1220 into ADUI-4680/merge-demos will not change coverage.
The diff coverage is n/a.

@@                  Coverage Diff                   @@
##           ADUI-4680/merge-demos    #1220   +/-   ##
======================================================
  Coverage                  99.66%   99.66%
======================================================
  Files                        354      354
  Lines                       8915     8915
  Branches                    2113     2113
======================================================
  Hits                        8885     8885
  Misses                        30       30

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f332d8c...6c58f21. Read the comment docs.

@gdostie To shutdown vapor.surge.sh I can manually deploy an html file that redirects to the actual website


Only configure the logger if S3FS_LOGGING_LEVEL is set

Allows people to opt-in to the basic logger config which outputs s3fs
messages while by default avoiding interfering with application-level
logging config.
The premise for piggy-backing on S3FS_LOGGING_LEVEL is that anyone
setting it expects to see some log output.  Anyone who doesn't want to
see log output can either not set it themselves or ensure it is unset
before s3fs is loaded.
Resolves #282.

Thanks, this looks nice. I think the "Logging" section in index.rst could be updated to explain how things work now.

Agreed, looks good, but needs documenting.

Ah, sorry, totally spaced on docs. Re-pushed with a doc update included.

Thank you.

Any chance of a new release soon? I'd love to be able to stop hacking around this logging issue. :-)

Yes, coming once I've finalised some things in fsspec

Thank you!


Relation manager attach action duplicate callback breaks recursive relationships

Package
filament/tables
Package Version
v3.0.25
Laravel Version
v10.19.0
Livewire Version
v3.0.0-beta.9
PHP Version
PHP 8.2.9
Problem description
I have a recursive relationship on my model. App\Models\Task can have many App\Model\Task and vice versa. When trying to attach on a relation manager, the duplicate check doesn't work correctly. I can attach as many models as I like.
Tables:
         Schema::create('task_edges', function (Blueprint $table) {
            $table->foreignId('parent_id')->references('id')->on('tasks');
            $table->foreignId('child_id')->references('id')->on('tasks');

            $table->unique(['parent_id', 'child_id']);
        });

Relationships:
    public function childTasks(): BelongsToMany
    {
        return $this->belongsToMany(Task::class, 'task_edges', 'parent_id', 'child_id');
    }

    public function parentTasks(): BelongsToMany
    {
        return $this->belongsToMany(Task::class, 'task_edges', 'child_id', 'parent_id');
    }

Problematic Code AttachAction.php:264
...
fn (Builder $query): Builder => $query->where(
    $table->getRelationship()->getParent()->getQualifiedKeyName(),
    $table->getRelationship()->getParent()->getKey(),
),
...

Generated SQL:
SELECT DISTINCT
    `tasks`.*

)
ORDER BY
    `tasks`.`name` ASC;

Because the tables in the query have the same name (because it is the same table), the query fails as the callback adds the sql condition AND tasks.id = ? to the query which excludes all entries.
This is fixed by using getKeyName() instead of getQualifiedKeyName() in which case just the condition AND id = ? is added which correctly uses the current scope laravel_reserved_0 and the query succeeds.
SELECT DISTINCT
    `tasks`.*

)
ORDER BY
    `tasks`.`name` ASC;

Expected behavior
The query should use the local scope incase both tables of the relationship are the same table. I don't know if this breaks other behavior.
Steps to reproduce

Create a model that relates to itself:

Schema::create('tasks', function (Blueprint $table) {
            $table->id();

            $table->string('name');

            $table->timestamps();
        });

        Schema::create('task_edges', function (Blueprint $table) {
            $table->foreignId('parent_id')->references('id')->on('tasks');
            $table->foreignId('child_id')->references('id')->on('tasks');

            $table->unique(['parent_id', 'child_id']);
        });

public function childTasks(): BelongsToMany
    {
        return $this->belongsToMany(Task::class, 'task_edges', 'parent_id', 'child_id');
    }

    public function parentTasks(): BelongsToMany
    {
        return $this->belongsToMany(Task::class, 'task_edges', 'child_id', 'parent_id');
    }

Create a relation manager for that relationship:

class ChildrenRelationManager extends RelationManager
{
    protected static string $relationship = 'childTasks';

    protected static ?string $inverseRelationship = 'parentTasks';
    ...
}

Try the attach action.

Relevant log output
No response

I also have the same problem https://github.com/filamentphp/filament/discussions/8950

Fixed by #10078


demos compilation error

I got some error compiling the folder demo. I changed the make_all.sh to be the following:
#!/usr/bin/env bash

# Linker opts is blank for OS X, FreeBSD and OpenSolaris
#LINKER_OPTIONS=""

# Must link with realtime libs for Linux
LINKER_OPTIONS="-lrt -lpthread"

gcc -Wall -c -o md5.o md5.c
gcc -Wall -c -o utils.o utils.c
gcc -Wall  md5.o utils.o -o premise premise.c -L. $LINKER_OPTIONS
gcc -Wall  md5.o utils.o -o conclusion conclusion.c -L. $LINKER_OPTIONS

It's just a comment that might be useful for someone in the future. Since I'm not an expert, I don't know why I had to add the lpthread library, I just googled and it worked. Also I moved $LINKER_OPTIONS to the end, because it was not working otherwise.

Thanks for the report. This GitHub repository is an unofficial archive/mirror of posix_ipc versions that Philip Semanchuk publishes at http://semanchuk.com/philip/posix_ipc/, so you might consider contacting him about this.

Oopps, thanks! I'll try to contact him.


[mongodb] [docs] Adds scanFullChangelog docs

This PR updates MongoDB CDC documentations.

Adds MongoDB 6.0 to tested version
Adds support of scan.full-changelog option
Removes limitation that timestamp startup mode cannot be used with legacy connector

@Jiabao-Sun Can you help review this pr ? :)


nut: fix compile error

Compile was failing with: ISO C++17 does not allow dynamic exception specifications
Installed and tested on x86_64-linux.
Description of changes
Added NIX_CFLAGS_COMPILE = "-std=c++14"; to derivation.

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Ping nut maintainer @nbp


"Nereju","Brădăcești","Chiricani","Nereju Mic","Sahastru" are listed in the drop-down menu

Description:
"Nereju","Brădăcești","Chiricani","Nereju Mic","Sahastru" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Preconditions : the website (https://peviitor-ro.github.io/ui.orase/) is up and running. After every step delete the text you typed from the search bar.

Step 1
Write in the search bar "Nereju"

Expected results
The location appears in the drop-down menu as "Sat Nereju, VRANCEA (Nereju)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Brădăcești"

Expected results
The location appears in the drop-down menu as "Sat Brădăcești, VRANCEA (Nereju)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Chiricani"

Expected results
The location appears in the drop-down menu as "Sat Chiricani, VRANCEA (Nereju)"

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Nereju Mic"

Expected results
The location appears in the drop-down menu as "Sat Nereju Mic, VRANCEA (Nereju)"

Step 9
Write in the search bar "Sahastru"

Expected results
The location appears in the drop-down menu as "Sat Sahastru, VRANCEA (Nereju)"


ImfChromaticities.h/cpp: Typo and pass by ref change.

Fix spelling typo in the comment block.
Better to pass "chroma" arg in by ref.

Will switching to pass-by-ref change the ABI? If so this change would need to be released in OpenEXR-2.5.0, rather than OpenEXR-2.4.1?

It certainly will change the ABI.

Yes this PR does change the ABI for those calls. Will make a mental note to flag it in my PRs next time... so u can squirrel it to the appropriate release candidate version.


Is there a guide to config HA ISCSI target for Ceph only with targetcli?

I am trying to using tcmu-runner on ubuntu. Currently I can't get ceph-iscsi-cli work , but targetcli-fb and rstlib-fb works fine.
Is there a guide to use only targetcli to config cross nodes active-passive HA?

Is there a guide to use only targetcli to config cross nodes active-passive HA?

No.
If something does not work on ubuntu for the ceph-iscsi-* packages, just report it. I installed ubuntu the other day and I had started removing the Red Hat specifics like in this patch
https://github.com/ceph/ceph-iscsi-cli/pull/53
but I have not had time to finish the work.

If something does not work on ubuntu for the ceph-iscsi-* packages, just report it

Actually do not waste your time. I will try to get some time to fix that up.

@mikechristie
Thank you.
I am having this issue now.The ceph-iscsi package requires rpm related libs but ubuntu uses dpkg:<
gwcli
/usr/local/lib/python2.7/dist-packages/rpm.py:15: UserWarning: The RPM Python bindings are not currently available via PyPI.
Please install them with your distro package manager (typically called
'python2-rpm' or 'python3-rpm'), and ensure that any virtual environments
needing the API are configured to be able to see the system site packages
directory.
warnings.warn(warning_msg)
Unable to access the configuration object : REST API failure, code : 500
GatewayError:


Modal doesn't close when clicking outside of the container

Issues:

click outside
click the button close
Not working the modal doesn't close.

Reproduce:

Click "New markdown"
Click "Create new section"

Thanks vansu! it's fixed


Create Takumi.png

Not being used by any asset?
Also, it's problematic to use images of real people, especially faces, and should be avoided.

Not being used by any asset? Also, it's problematic to use images of real people, especially faces, and should be avoided.

Hey Jeremy, It's part of a meme sticker set on Telegram.  It's not being used by any other asset currently.  Is the use of a face for a logo forbidden?  I chose this specifically because of the memes involved, so would like to run with it if possible.
Thanks,
Paul

Image additions need to be in the same PR as updating the JSON file that refers to it.


Adds support for activeElement to Polymer.dom.

For document and shadow root nodes, if the active element is a (possibly deep) descendant of the given node, Polymer.dom(node).activeElement will return the deepest element within the light tree of the node which is or deeply contains the active element. For all other nodes, the getter and setter will forward to the activeElement property on the node.

@sorvell ping

@sorvell This is ready for review again.

@sorvell ping again

So, since Polymer runs the tests on Chrome's native version of Shadow DOM, it looks like I didn't correctly interpret the retargeting algorithm for activeElement on ShadowRoots. Specifically, it seems like if the active element is within the light DOM of a ShadowRoot's host, activeElement of that ShadowRoot should be the active element rather than null. I need to fix this in the web components polyfills and then come back here. :/

(PR for activeElement fix in web components polyfill.)

Updated with the expectation that the web components polyfill PR will make it in, tests will fail until then.

Only 1 little nit left, otherwise LGTM after we get the webcomponents change merge. Thanks!

I had to add additional tests and make an update to the host-finding loop for this new case - might want to double check that.

@sorvell ping for this one, needed by https://github.com/PolymerElements/iron-overlay-behavior/pull/68

Depends on webcomponents/webcomponentsjs#475.

@sorvell: fixed stuff from your comments

LGTM


try to address #75, fix performance problem and succeed in self-profiling

In this PR, I will try to solve #75 , and succeed in the self-profiling.

Codecov Report

Merging #90 (77eb900) into master (643f1f5) will increase coverage by 0.14%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #90      +/-   ##
==========================================
+ Coverage   83.33%   83.47%   +0.14%
==========================================
  Files          10       10
  Lines         942      938       -4
==========================================
- Hits          785      783       -2
+ Misses        157      155       -2

Impacted Files
Coverage Δ

src/abstractinterpreterinterface.jl
91.30% <ø> (ø)

src/jetcache.jl
75.55% <100.00%> (ø)

src/typeinfer.jl
98.30% <100.00%> (-1.70%)
:arrow_down:

src/reports.jl
87.78% <0.00%> (+0.39%)
:arrow_up:

src/print.jl
79.79% <0.00%> (+1.58%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 643f1f5...77eb900. Read the comment docs.

Codecov Report

Merging #90 (77eb900) into master (643f1f5) will increase coverage by 0.14%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #90      +/-   ##
==========================================
+ Coverage   83.33%   83.47%   +0.14%
==========================================
  Files          10       10
  Lines         942      938       -4
==========================================
- Hits          785      783       -2
+ Misses        157      155       -2

Impacted Files
Coverage Δ

src/abstractinterpreterinterface.jl
91.30% <ø> (ø)

src/jetcache.jl
75.55% <100.00%> (ø)

src/typeinfer.jl
98.30% <100.00%> (-1.70%)
:arrow_down:

src/reports.jl
87.78% <0.00%> (+0.39%)
:arrow_up:

src/print.jl
79.79% <0.00%> (+1.58%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 643f1f5...77eb900. Read the comment docs.

Okay, I think the right solution for this would be lazy constructions of reports.

Okay, I think the right solution for this would be lazy constructions of reports.

approach 2. frame chain traverse via backedge

approach 1. revealed that the frame traverse itself can be very expensive
currently JET.jl traverses frame chain from a frame where a error is reported to an entry frame (i.e. traverse .parent chain)
this happens on every report construction including re-construction of cached reports, and so includes lots of duplicated works
as an alternative, we can traverse frame chain from caller to callee, i.e. each time we get back to higher level frame, we add the current frame to each virtual call stack of all the existing reports
this approach should cut off some of the previous duplicated works, since maybe lots of reports are discarded by constant prop'

approach 2. frame chain traverse via backedge

approach 1. revealed that the frame traverse itself can be very expensive
currently JET.jl traverses frame chain from a frame where a error is reported to an entry frame (i.e. traverse .parent chain)
this happens on every report construction including re-construction of cached reports, and so includes lots of duplicated works
as an alternative, we can traverse frame chain from caller to callee, i.e. each time we get back to higher level frame, we add the current frame to each virtual call stack of all the existing reports
this approach should cut off some of the previous duplicated works, since maybe lots of reports are discarded by constant prop'

Here is a MRE which should be fixed before merging:
julia> using JET

julia> struct Foo
           bar
       end

julia> @profile_call println(Foo(1))
ERROR: AssertionError: invalid global caching MethodInstance for fieldname(::DataType, ::Int64) MethodInstance for (::Base.var"#throw_need_pos_int#12")(::Int64)
Stacktrace:
   [1] _typeinf(interp::JET.JETInterpreter, frame::Core.Compiler.InferenceState)
     @ JET ~/julia/packages/JET/src/typeinfer.jl:167
   ...

Okay, this PR is good in shape.
Here is a summary of the main change

933c51e @aviatesk accumurate virtual stack trace on returning back to the parent frame
The idea is to stop a frame chain traversal on report construction or
cached report restoring, but rather update reports "frame-by-frame".
Before exiting the local inference (or cache retrieval), we keeps
reports that should be updated in interp.to_be_updated and they will
be updated when returning back to the parent frame
(i.e. the next inter-procedural context).
This should eliminate lots of the previous frame chain traversal works,
and should give us some performance improvements, especially we're
analyzing deep frames.
Caveat:
For now I couldn't find a right way to handle mutual recursion
cycle.
As such JET doesn't always make the following condition hold, and thus
its stack trace could be wrong.
# in `_typeinf` or cache retrieval points
@Assert first(report.st).linfo === current_linfo

I'd like to leave this problem as a future work for now, and improve
performance for now.

Okay, the self-profiling benchmark shows 40% analysis time improvements.
I'm going to merge this once all the CI runs successfully.


Make it depend on active record instead of rails

Unless I've missed s/th there's no reason to make rails a dependencies as it's a mere active record plugin.
Other than that: Good peace of software. Thanks! :)

+1


Many tiles are missing their item equivalent.

Many floors, such as the techmaint floor in engineering, are missing their correct item drop. This causes the wrong floor item to drop when crowbarring them.

Could maybe do with something like a tile painter for some of them.

Steel floor is a fallback. I believe at the time I added this there weren't a lot of floor item sprites. I'll  take a look at this though.

closed by #1055


Add CI check for stub files

To be merged after we get all stubs.
Here's the list of exercises missing stubs:

[x] alphametics
[x] atbash-cipher
[x] binary-search
[x] bowling
[x] change
[x] circular-buffer
[x] connect
[x] crypto-square
[ ] diffie-hellman
[x] forth
[x] kindergarten-garden
[x] meetup
[x] minesweeper
[ ] queen-attack
[x] react
[x] simple-linked-list
[x] two-fer
[x] word-search
[x] wordy
[x] zipper

Almost there 🎈 🎉 🌞


Add interactive tooltip to the bar chart and fix time display

This PR adds an interactive tooltip to the bar chart, which displays the push information
when the user hovers on a bar or the empty area above it. During hovering, the bar will
be highlighted, and the point corresponding to the bar in the boxplot will also be highlighted
and outlined in black. The interactions is trigger by events mouseover and mouseleave.
The startTime on the x axis is also fixed by reformatting x labels to yyyy:MM:dd HH:mm:ss
so that bars don't present on the same x position. The next PR will change the duration unit
depending on the time of the pushes and fix ticks overlaying for the boxplot.

Running version: https://pr38-e3ee0a8-dot-step189-2020.uc.r.appspot.com/

New running version: https://pr38-2e97745-dot-step189-2020.uc.r.appspot.com/


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1275 ms

Resolved: Bofrost.lu performance has improved in 3db9b1b after 13 minutes.


Save normalized audio to file?

@est31, thank you for the code, it works great!
Is it possible to dump/save the normalized buffer into a file?

Thanks that you appreciated it! The code was mainly meant as a demo. Quick googling found this example onto how to save something with WebAudio: https://developer.mozilla.org/en-US/docs/Web/API/MediaRecorder#example
Hope that helped!