Added time_key param

Added the ability to override fluentd's time with a time field in the record.
This was very useful to me when I had in a log time value that wasn't parsable using the time_format.
I needed to send that value "raw" to splunk (and splunk could parse it correctly)

Hi @yarinm
Looking through the PR the logic makes sense however we are keen to understand some examples where the log time value wasn't parsable using time_format.
Could you provide some examples of the issues you having, this may be something we can solve on the Splunk side.

@dtregonning
The main issue is when using HEC, parsing configurations defined in props.conf regarding time of the event won't work because it uses the time sent by the plugin. Other rules won't work as well, such as line merging etc.
I have a pod in kubernetes that writes several log files and I'm using side containers that tail those files to the stdout in order to have kubernetes report these logs with pod name and namespace to /var/log/containers/* in that machine.
Log format
{"log":"the content\n","stream":"stdout","time":"2018-11-15T08:49:34.814832464Z"}
I'm using fluentd to extract kubernetes container logs my actual log data ins the "log" field with the real time of the log. The time in the kubernetes log is the time the tail printed the line which is different.
The inner data in the log key is a json with a field with a timestamp.
When I try to parse the timestamp with time_format "%s%N" it fails because ruby doesn't support %s for strptime. It also seems that fluentd must parse the time I can't just put the string as-is in the time field in the record. So I had to put that string in a different field, e.g "splunk_time" and use the feature I've created to send it over as part of the record in HEC.

@dtregonning  when is this going to be merged?

@yarinm I'll discuss with @dtregonning tomorrow PST.

@dtregonning when is this going to be merged?

Hey @yarinm we haven't forgot about this. The delay to merging in these PRs has been us creating some more solid CI and automated testing practices. We wan't to get to a place where these feature PRs are merged and released at a much faster cadence.
You may have seen some CircleCI messages popping up here and there. We will update you and the other community members once we are good to go.
Thanks again for your submission and the follow up.


Dynamic page loading failed Error: Trying to replace an element that wasn't mounted!

Version
styled-components: 2.1.1
babel-plugin-styled-components: 1.1.7

SSR is configured with code-splitting using react-boilerplate.
Some components are imported from an npm package which exports components styled with styled-components.

Error stack trace
Dynamic page loading failed Error: Trying to replace an element that wasn't mounted!
    at BrowserTag.replaceElement (eval at ./node_modules/styled-components/lib/models/BrowserStyleSheet.js (main.js:4034), <anonymous>:122:36)
    at BrowserTag.addComponent (eval at ./node_modules/styled-components/lib/models/BrowserStyleSheet.js (main.js:4034), <anonymous>:63:27)
    at StyleSheet.getOrCreateTag (eval at ./node_modules/styled-components/lib/models/StyleSheet.js (main.js:4058), <anonymous>:141:18)
    at StyleSheet.deferredInject (eval at ./node_modules/styled-components/lib/models/StyleSheet.js (main.js:4058), <anonymous>:94:10)
    at new ComponentStyle (eval at ./node_modules/styled-components/lib/models/ComponentStyle.js (main.js:4042), <anonymous>:38:39)
    at createStyledComponent (eval at ./node_modules/styled-components/lib/models/StyledComponent.js (main.js:4074), <anonymous>:238:26)
    at templateFunction (eval at ./node_modules/styled-components/lib/constructors/constructWithOptions.js (main.js:3986), <anonymous>:26:14)
    at eval (eval at ./app/pages/CustomerStory/Quote.js (main.js:1815), <anonymous>:8:3)
    at Object../app/pages/CustomerStory/Quote.js (main.js:1815)
    at __webpack_require__ (main.js:660)

Reproduction
I cannot reliably reproduce the error on webpackbin. Things I can reproduce:

If I remove CSS injection on the server the error goes away (initially page is loaded without styles).
Error happens only in some of the pages, but not in every page. However, when it happens, it usually happens consistently.
Error always points to the same component. If I change / rename the component, the error starts pointing to another component, but the stacktrace is the same.
Error sometimes points to the component, that is not even present on the page.
We've never encountered this error when using styled-components v1. It started occurring once we switched to v2 (without any other changes to the setup).

What I've tried

Fiddling with babel-plugin-styled-components options

ssr on/off
preprocess on/off

Any suggestion that could point to the possible culprit / solution would be greatly appreciated.

Since this seems to be an SSR related issue, can you post some code on how you integrated our SSR API with the boilerplate? Cheers
cc @geelen

hm, I suspect that the two render phases are responsible for this trouble. Can you try this:
import { ServerStyleSheet, StyleSheetManager } from 'styled-components'

// 1st render phase - triggers the sagas
renderToString(
  <StyleSheetManager sheet={new ServerStyleSheet().instance}>
);

// ...
// 2nd render phase

const sheet = new ServerStyleSheet();

const appMarkup = renderToString(
  sheet.collectStyles(
    <AppRoot store={store}>
      <RouterContext {...renderProps} />
    </AppRoot>
  )
);

// ...
const css = sheet.getStyleElement();

The problem seems to be that in the 1st phase you're rendering loads of Styled Components without them being captured with the server stylesheet. We can't reuse the same one for two rendering cycles, but we can try to use two separate ones, I believe

Tried this:
import { ServerStyleSheet, StyleSheetManager } from 'styled-components'

// ...

// 1st render phase - triggers the sagas
renderToString(
  <StyleSheetManager sheet={new ServerStyleSheet().instance}>
    <AppRoot store={store}>
      <RouterContext {...renderProps} />
    </AppRoot>
  </StyleSheetManager>
);

// ...

// 2nd render phase - the sagas triggered in the first phase are resolved by now
const sheet = new ServerStyleSheet();

const appMarkup = renderToString(
  sheet.collectStyles(
    <AppRoot store={store}>
      <RouterContext {...renderProps} />
    </AppRoot>
  )
);

// capture the generated css
const css = sheet.getStyleElement();

and this
import { ServerStyleSheet, StyleSheetManager } from 'styled-components'

// ...

const sheet = new ServerStyleSheet();

// 1st render phase - triggers the sagas
renderToString(
  <StyleSheetManager sheet={sheet.instance}>
    <AppRoot store={store}>
      <RouterContext {...renderProps} />
    </AppRoot>
  </StyleSheetManager>
);
// ...

// 2nd render phase - the sagas triggered in the first phase are resolved by now

const appMarkup = renderToString(
  sheet.collectStyles(
    <AppRoot store={store}>
      <RouterContext {...renderProps} />
    </AppRoot>
  )
);

// capture the generated css
const css = sheet.getStyleElement();

Both result in the same error.

Error happens only in some of the pages, but not in every page. However, when it happens, it usually happens consistently.
Error always points to the same component. If I change / rename the component, the error starts pointing to another component, but the stacktrace is the same.
Error sometimes points to the component, that is not even present on the page.

Is there anything special about these components in the way they're used together with the state?

After reading through the code, I noticed that the error occurs when a style tag is not mounted in the head anymore. Which sounds weird. I'm not familiar with the rehydration yet, so @geelen might have to jump in.
Are you sure that the style tags are injected into the head statically and stay there?
https://github.com/styled-components/styled-components/blob/master/src/models/BrowserStyleSheet.js

Would it be possible to fail silently? Because when this error is thrown, the execution of the code stops and the page "breaks", which is undesired.

@DeividasK I'm not sure about that either, because it's a critical error in the rehydration. Again, Glen will probably be able to shine a light on this

@geelen Hey Glen, just wanted to bump this up. Any ideas / experiments that I could do to try and fix this would be really helpful.

He guys, any updates on this?

@DeividasK I can probably take a quick look and try out some things to solve this. Do you have a reproduction repo somewhere?

Hey Phil, not really. The main problem is that it is hard to precisely reproduce. The only way I am able to reproduce it now is in the main project repo. It disappears if I remove server side rendering. Removing code splitting does not help.

@philpl turns out that the issue was with duplicated styled-components modules. One of the dependencies for our npm package was styled-components. Once I removed that from dependencies to devDependencies (also added to peerDependencies for the warnings) AND in webpack config specified it with externals
externals: {
    react: 'react',
    'react-dom': 'react-dom',
    'styled-components': 'styled-components',
  },

the issues have disappeared.
Simply removing it from dependencies did not help as it was necessary to specify it together with other external libraries.
I closed this issue, but I think it's worth having a discussion if styled-components should somehow detect and prevent this from happening.

I had a similar issue using redux-connect and styled-components on the server.
I was doing something very similar to @DeividasK
// capture the generated css
const css = sheet.getStyleElement();

const doc = renderToStaticMarkup(
  <HtmlDocument
    appMarkup={appMarkup}
    css={css}
  />
);
return `<!DOCTYPE html>\n${doc}`;

But on the client after the JS loads I would get an error Trying to replace an element that wasn't mounted!, causing some css to be missing.
I was able to fix it by changing
const css = sheet.getStyleElement();
to
const css = sheet.getStyleTags();
and in my HtmlDocument I changed it from
<head>
  {css}
</head>

to
<head>
  <style dangerouslySetInnerHTML={{ __html: css}} />
</head>

@xiaolin I get the same error Uncaught Error: Trying to replace an element that wasn't mounted! however, this error is happening on the client-side only. I think const styleTags = sheet.getStyleTags(); Is fine just gets the stylesheet tags from styled-components, have you found any clean solution for this?

@ilanus This issue is extremely old! Please refrain from commenting in older issues that have been resolved
Check the docs on how to set up SSR: https://www.styled-components.com/docs/advanced#server-side-rendering

Using this API on the client is not supported
If the error is on the client but the API is set up correctly make sure that the style tags are injected into your HTML's head

@philpl old or not, I also ran into issue with the Next.js example and was able to fix them with @xiaolin's tweak.

This can be caused when multiple styled-components instances are used.
with npm use npm dedupe
with yarn add this to package.json with correct version and do yarn install after
"resolutions": {
  "styled-components": "your version"
}


Wrong statement in documentation about SQLModel.metadata.create_all()

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the SQLModel documentation, with the integrated search.
[X] I already searched in Google "How to X in SQLModel" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to SQLModel but to Pydantic.
[X] I already checked if it is not related to SQLModel but to SQLAlchemy.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
No code involved

Description
Moving create_all to function here just prevents creation on first import. Python modules are executed only once, you can check it yourself.
So statement "If SQLModel.metadata.create_all(engine) was not in a function and we tried to import something from this module (from this file) in another, it would try to create the database and table every time." is wrong ("every time" in particular).
Operating System
macOS
Operating System Details
No response
SQLModel Version
0.0.4
Python Version
3.9.5
Additional Context
No response

Thanks for the discussion! I added https://github.com/tiangolo/sqlmodel/pull/426 to improve the text. If you feel like there's something else to be done, please let me know. If it seems clearer to you now, you can close the issue. :coffee:


No StateError when adding event/s to unclosed non-broadcast stream controller whose stream is cancelled.

Consider:
void main() {
  final c = StreamController();
  c.close();

  c.add(0); //throws StateError
}

I think the motiviation for this Error is to alert the developer that they are potentially leaking resources, e.g. a timer was not cancelled.
However, consider:
void main() {
  final c = StreamController();
  c.stream.listen((event) {}).cancel();

  c.add(1);
}

In this example, after .cancel, the stream cannot receive events, yet the call to add doesn't throw an error.
I propose that the add methods on a non-broadcast stream controller whose stream is cancelled throw a StateError.
new StreamController()'s add methods have one purpose: add events to .stream.
Bonus question: should the call to cancel close the sink?
The factory constructor of StreamController could document this.

The current behavior is intentional.
The owner of the controller should know whether they have called close or not. As such, camping add after close is considered a bug.
The listener is likely not written as part of the same code that creates the events, so while it cancelling can be noticed immediately using an onCancel callback, it's too cumbersome in practice to have to check for cancellation all the time. Therefore the event producer is allowed to add events after cancel, and to check StreamController.hasListener only when it's convenient. The events will be discarded.


CI: Add support for tests on Apple Silicon

macos-14 was just announced and it is Apple Silicon (i.e. arm64 Apple chips), see https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/ . I also changed macos-latest to macos-12, as now macos-latest is an alias for macos-12 (see https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories) and it is a bit confusing otherwise.

Actually bfl was not on osx-arm64: https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/5450 .

Actually bfl was not on osx-arm64: conda-forge/conda-forge-pinning-feedstock#5450 .

Closing until this is fixed.


Fix #303

Thanks Felipe!  There seems to be an issue that Travis is complaining about.

This PR can be close, #313 will solve the same issue when merged.


K8SPXC-367 SmartUpdate e2e test

Test name
Status

storage
passed

scaling
passed

recreate
passed

init-deploy
passed

big-data
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

monitoring
failed

upgrade
passed

restore-to-encrypted-cluster
failed

monitoring-2-0
failed

self-healing-advanced
failed

affinity
passed

upgrade-consistency
failed

security-context
failed

operator-self-healing
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

smart-update
passed

demand-backup
failed

or upgrade via version service, for latest, recommended, the exact version

IMHO, we should not test smart update using version service.
Version service is just a source of information. It has its own tests.

@cap1984
Did you cover all these cases?
PXC upgrades auto e2e tests
  - for smart failover with ProxySQL
  - for smart failover with HAProxy
  - for deployment with version service reachable
  - for deployment with version service unreachable
  - for upgrade via version service, for latest, recommended, the exact version

Now it covers all the cases. However it won't work until https://github.com/percona/percona-xtradb-cluster-operator/pull/530 will be merged.

Test name
Status

storage
passed

scaling
passed

init-deploy
passed

recreate
passed

scaling-proxysql
passed

self-healing
failed

upgrade
passed

limits
passed

restore-to-encrypted-cluster
failed

self-healing-advanced
failed

upgrade-consistency
failed

security-context
failed

monitoring
failed

monitoring-2-0
failed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

smart-update
failed

operator-self-healing
failed

demand-backup
failed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
passed

scaling
passed

storage
passed

recreate
passed

big-data
passed

self-healing
failed

scaling-proxysql
passed

limits
passed

monitoring
passed

upgrade
passed

restore-to-encrypted-cluster
failed

upgrade-consistency
failed

monitoring-2-0
passed

affinity
passed

one-pod
passed

demand-backup
passed

security-context
passed

self-healing-advanced
passed

auto-tuning
passed

operator-self-healing
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

users
passed

smart-update
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

scaling
passed

scaling-proxysql
passed

upgrade
passed

storage
passed

upgrade-consistency
failed

recreate
passed

self-healing
failed

restore-to-encrypted-cluster
failed

init-deploy
passed

big-data
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

smart-update
passed

security-context
passed

demand-backup
passed

scheduled-backup
failed

self-healing-advanced
passed

operator-self-healing
passed

Test name
Status

big-data
passed

init-deploy
passed

scaling
passed

recreate
passed

storage
passed

self-healing
failed

scaling-proxysql
passed

limits
passed

monitoring
passed

upgrade
passed

monitoring-2-0
passed

restore-to-encrypted-cluster
failed

upgrade-consistency
failed

affinity
passed

one-pod
passed

self-healing-advanced
passed

demand-backup
passed

security-context
passed

auto-tuning
passed

operator-self-healing
passed

proxysql-sidecar-res-limits
passed

users
passed

scheduled-backup
failed

smart-update
passed

Test name
Status

init-deploy
passed

recreate
passed

big-data
passed

scaling
passed

storage
passed

limits
passed

scaling-proxysql
passed

self-healing
failed

monitoring
passed

upgrade
passed

restore-to-encrypted-cluster
failed

monitoring-2-0
passed

upgrade-consistency
failed

affinity
passed

demand-backup
passed

self-healing-advanced
passed

security-context
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

big-data
passed

storage
passed

self-healing
failed

recreate
passed

restore-to-encrypted-cluster
failed

scaling
passed

init-deploy
passed

scaling-proxysql
passed

limits
passed

upgrade
passed

monitoring
passed

upgrade-consistency
failed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

smart-update
failed

security-context
passed

demand-backup
passed

scheduled-backup
failed

self-healing-advanced
passed

operator-self-healing
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
failed

big-data
failed

recreate
failed

storage
failed

scaling
passed

smart-update
failed

scaling-proxysql
failed

limits
failed

restore-to-encrypted-cluster
failed

self-healing
failed

upgrade
failed

monitoring
failed

self-healing-advanced
failed

demand-backup
failed

upgrade-consistency
failed

monitoring-2-0
failed

operator-self-healing
failed

scheduled-backup
failed

security-context
failed

demand-backup-encrypted-with-tls
failed

affinity
failed

one-pod
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

users
failed

Test name
Status

storage
passed

smart-update
passed

scaling
passed

big-data
passed

recreate
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
failed

limits
passed

monitoring
passed

restore-to-encrypted-cluster
failed

upgrade
passed

monitoring-2-0
passed

demand-backup
passed

self-healing-advanced
passed

upgrade-consistency
failed

affinity
passed

one-pod
passed

operator-self-healing
passed

security-context
passed

auto-tuning
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

smart-update
passed

scaling
passed

big-data
passed

storage
passed

scaling-proxysql
passed

self-healing
failed

upgrade
passed

upgrade-consistency
failed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

recreate
passed

restore-to-encrypted-cluster
failed

security-context
passed

demand-backup
passed

scheduled-backup
failed

self-healing-advanced
passed

operator-self-healing
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

smart-update
passed

big-data
passed

scaling
passed

storage
passed

init-deploy
passed

recreate
passed

scaling-proxysql
passed

limits
passed

upgrade
passed

self-healing
passed

restore-to-encrypted-cluster
passed

monitoring
passed

upgrade-consistency
failed

monitoring-2-0
passed

self-healing-advanced
passed

demand-backup
passed

security-context
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

scaling
passed

init-deploy
passed

smart-update
passed

big-data
passed

storage
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

upgrade
passed

monitoring
passed

self-healing-advanced
passed

upgrade-consistency
failed

operator-self-healing
passed

monitoring-2-0
passed

security-context
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

Test name
Status

big-data
passed

smart-update
passed

storage
passed

recreate
passed

init-deploy
passed

scaling
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

upgrade
passed

monitoring
failed

restore-to-encrypted-cluster
failed

upgrade-consistency
failed

self-healing-advanced
passed

monitoring-2-0
failed

demand-backup
failed

operator-self-healing
passed

security-context
passed

affinity
passed

one-pod
passed

scheduled-backup
failed

auto-tuning
passed

demand-backup-encrypted-with-tls
failed

proxysql-sidecar-res-limits
passed

users
passed

Test name
Status

storage
passed

smart-update
failed

big-data
passed

recreate
passed

haproxy
passed

scaling
passed

self-healing
passed

init-deploy
passed

scaling-proxysql
passed

upgrade
failed

restore-to-encrypted-cluster
passed

limits
passed

self-healing-advanced
passed

monitoring
passed

demand-backup
passed

monitoring-2-0
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

scheduled-backup
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

big-data
passed

haproxy
passed

smart-update
failed

scaling
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

upgrade
failed

limits
passed

self-healing-advanced
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

Test name
Status

recreate
passed

smart-update
failed

scaling
passed

big-data
passed

storage
passed

haproxy
passed

self-healing
passed

init-deploy
passed

scaling-proxysql
passed

upgrade
failed

restore-to-encrypted-cluster
passed

limits
passed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

smart-update
failed

big-data
passed

scaling
passed

scaling-proxysql
passed

upgrade
failed

recreate
passed

haproxy
passed

restore-to-encrypted-cluster
passed

init-deploy
passed

demand-backup
passed

limits
passed

scheduled-backup
failed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

Test name
Status

scaling
failed

storage
failed

big-data
failed

haproxy
failed

smart-update
failed

recreate
failed

self-healing
failed

init-deploy
failed

restore-to-encrypted-cluster
failed

scaling-proxysql
failed

self-healing-advanced
failed

upgrade
failed

limits
failed

demand-backup
failed

scheduled-backup
failed

operator-self-healing
failed

monitoring
failed

demand-backup-encrypted-with-tls
failed

monitoring-2-0
failed

Test name
Status

Test name
Status

big-data
failed

smart-update
failed

Test name
Status

smart-update
failed

recreate
passed

scaling
passed

storage
failed

big-data
passed

haproxy
passed

init-deploy
passed

scaling-proxysql
failed

restore-to-encrypted-cluster
passed

limits
passed

monitoring
failed

demand-backup
passed

self-healing
passed

scheduled-backup
passed

upgrade
failed

self-healing-advanced
passed

monitoring-2-0
failed

operator-self-healing
passed

demand-backup-encrypted-with-tls
failed

affinity
failed

Test name
Status

haproxy
passed

init-deploy
passed

limits
passed

recreate
passed

monitoring
failed

restore-to-encrypted-cluster
passed

demand-backup
passed

smart-update
failed

scheduled-backup
passed

demand-backup-encrypted-with-tls
failed

storage
failed

big-data
passed

scaling
passed

scaling-proxysql
failed

monitoring-2-0
failed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

upgrade
failed

affinity
failed

upgrade-consistency
failed

one-pod
failed

security-context
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

Test name
Status

storage
failed

haproxy
passed

scaling
passed

smart-update
passed

big-data
passed

recreate
passed

scaling-proxysql
failed

init-deploy
passed

restore-to-encrypted-cluster
passed

limits
passed

monitoring
failed

demand-backup
passed

self-healing
passed

upgrade
failed

scheduled-backup
passed

self-healing-advanced
passed

monitoring-2-0
failed

operator-self-healing
passed

demand-backup-encrypted-with-tls
failed

affinity
failed

Test name
Status

haproxy
passed

storage
passed

recreate
passed

smart-update
passed

big-data
passed

scaling
passed

self-healing
passed

init-deploy
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

upgrade
failed

limits
passed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

tls-issue-self
passed

tls-issue-cert-manager
failed

Test name
Status

storage
passed

haproxy
passed

big-data
passed

self-healing
passed

init-deploy
passed

self-healing-advanced
passed

limits
passed

smart-update
passed

operator-self-healing
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

recreate
passed

auto-tuning
passed

restore-to-encrypted-cluster
passed

proxysql-sidecar-res-limits
passed

demand-backup
passed

users
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
failed

tls-issue-self
passed

scaling
passed

tls-issue-cert-manager
failed

scaling-proxysql
passed

upgrade
failed

tls-issue-cert-manager-ref
failed

Test name
Status

big-data
passed

scaling
passed

smart-update
passed

storage
passed

recreate
passed

haproxy
passed

self-healing
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

limits
passed

scaling-proxysql
passed

self-healing-advanced
passed

monitoring
passed

upgrade
failed

demand-backup
passed

operator-self-healing
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

tls-issue-self
passed

tls-issue-cert-manager
failed

Test name
Status

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
passed

scaling
passed

scaling-proxysql
passed

upgrade
failed

Test name
Status

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

big-data
passed

smart-update
passed

auto-tuning
passed

scaling
passed

proxysql-sidecar-res-limits
passed

scaling-proxysql
passed

users
passed

upgrade
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

storage
passed

self-healing
passed

recreate
passed

self-healing-advanced
passed

restore-to-encrypted-cluster
passed

operator-self-healing
passed

demand-backup
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
passed

tls-issue-cert-manager-ref
passed

upgrade-consistency
failed

security-context
failed

Test name
Status

big-data
passed

smart-update
passed

haproxy
passed

recreate
passed

scaling
passed

storage
passed

self-healing
failed

scaling-proxysql
passed

init-deploy
passed

upgrade
failed

restore-to-encrypted-cluster
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

demand-backup
passed

self-healing-advanced
passed

affinity
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

scheduled-backup
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

scaling
passed

scaling-proxysql
passed

upgrade
failed

smart-update
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
passed

storage
passed

demand-backup-encrypted-with-tls
passed

self-healing
failed

big-data
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

self-healing-advanced
passed

operator-self-healing
passed

upgrade-consistency
passed

security-context
passed

Test name
Status

haproxy
passed

smart-update
passed

storage
passed

recreate
passed

scaling
passed

big-data
passed

self-healing
passed

init-deploy
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

limits
passed

self-healing-advanced
passed

upgrade
failed

monitoring
passed

operator-self-healing
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

scheduled-backup
passed

tls-issue-self
passed

tls-issue-cert-manager
failed

demand-backup-encrypted-with-tls
passed

tls-issue-cert-manager-ref
passed

Test name
Status

storage
passed

smart-update
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

haproxy
passed

init-deploy
passed

big-data
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

scaling
passed

auto-tuning
passed

scaling-proxysql
passed

proxysql-sidecar-res-limits
passed

upgrade
failed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
passed

tls-issue-cert-manager-ref
passed

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-523-dd5fd3bc

Test name
Status

scaling
passed

recreate
passed

big-data
passed

smart-update
passed

haproxy
passed

storage
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

upgrade
passed

limits
passed

self-healing-advanced
passed

upgrade-consistency
passed

monitoring
passed

security-context
passed

operator-self-healing
passed

demand-backup
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

scheduled-backup
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

demand-backup-encrypted-with-tls
passed

tls-issue-cert-manager-ref
passed


Mrit build automation

Prerequisite
Docker is running on the server.
What it does

Creates Cassandra and Elasticsearch containers
Create Schema in Cassandra, and sets up elasticsearch indices
Runs all of the test cases
Removes the containers at the end of the test run

I noticed. Sorry about that. That was not the intention. ☺
From<EMAIL_ADDRESS>on behalf of Geoff Bourne<EMAIL_ADDRESS>Reply-To: rackerlabs/blueflood<EMAIL_ADDRESS>Date: Thursday, March 8, 2018 at 1:07 PM
To: rackerlabs/blueflood<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [metrics-dev] [rackerlabs/blueflood] Mrit build automation (#822)
@itzg approved this pull request.
For future reference, a more descriptive PR title would be good.

In run-integration-test.shhttps://github.com/rackerlabs/blueflood/pull/822#discussion_r173290280:

@@ -0,0 +1,30 @@

+#!/bin/bash

+BASE_DIR=pwd

+# Create Cassandra and Elasticsearch containers to run the integration test
+docker-compose -f contrib/blueflood-docker-compose/docker-compose-integration-test.yml up -d

+# Copy Cassandra schema file into Cassandra container
+docker cp src/cassandra/cli/load.cdl cassandra-node:/tmp/load.cdl
FYI you could volume-attach the file into the container, but not worth changing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/rackerlabs/blueflood/pull/822#pullrequestreview-102457758, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQBvO9jSx2ifjfnAvYgLAnZiuMgmfdGfks5tcZ12gaJpZM4SjNdM.


Use test data set for testing.

Tests that require data are using actual feed data whose values are therefore subject to change. Check in a minimal testing data set, add support in load_feeds() to load from an explicit path without updating, and recode tests against the test data where necessary.

A unit test testing number of nearby systems failed after FC patch because EDDB is currently reporting unpopulated systems visited by carriers as populated. Fixed test data will solve this issue separate from the whole "are they really populated" question.


Documentation for odo app list should say 'List all the applications in current project'

https://github.com/redhat-developer/odo/blob/e67cb82387437b2729a56c581951e5610c4f519f/cmd/application.go#L134
To follow the same pattern used in `odo list' https://github.com/redhat-developer/odo/blob/e67cb82387437b2729a56c581951e5610c4f519f/cmd/list.go#L17

PR here: https://github.com/redhat-developer/odo/pull/696


Prevent recreation of compute_instance_template on every apply

The device_name was always empty so I explicitly set it to the computed value to prevent Terraform recreating it on each apply. This might be a bug in the Google provider, but I haven't found an issue for it yet.
I also have a similar PR open for hashicorp/terraform-google-vault#1.

@madmod Thanks for submitting this PR. Let's resolve the similar discussion at https://github.com/hashicorp/terraform-google-consul/pull/2 and then apply appropriate changes here.

@josh-padnick Hi josh, what's left to address on this PR? It seems that the discussion at the PR linked on your previous comment never happened and it was closed due to inactivity.

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.

I believe this was fixed in the Google provider and my latest provider update should be compatible without any issues. I'm closing to close this PR, however, feel free to reopen if you are still having problems.


Can't log objects???

Logging an object with rn-bugfender I get:
com.facebook.bridge.ReadableNativeMap cannot be cast to java.lang.String

I kno I can JSON.stringify my object before logging, but, what a shame... :-(

Hi @marcolino , this is an open source project, please feel free to contribute

I will do it as soon I have some spare time... Thanks.
For the moment I added a hach on client code... :-(


Add Behaviour of SceneTree pausing to the doc

Text copied from: https://godot.readthedocs.io/en/3.0/tutorials/misc/pausing_games.html
Resolves #4001

Thanks!

Cherry-picked for 3.0.7.


Password is visible when connecting using console on Win10

OrientDB Version: 3.0.10
Java Version: SAP Java Server VM (build 8.1.032 25.51-b13, Jul 27 2017 17:00:59 - 81_REL - optU - windows amd64 - 6 - bas2:292506 (mixed mode))
OS: Windows 10
Expected behavior
Password should not be visible when connecting to the database
Actual behavior
Password is visible
Steps to reproduce
C:\Tools\orientdb-3.0.10\bin>console.bat

OrientDB console v.3.0.10 - Veloce (build eac0654847df662ca03b45a6a5efa5eadd229ca5, branch 3.0.x) https://www.orientdb.com
Type 'help' to display all the supported commands.
orientdb> connect remote:localhost root
Enter password: root

OK
orientdb {server=remote:localhost}>

or
orientdb> connect remote:localhost/test admin
Enter password: admin

Connecting to database [remote:localhost/test] with user 'admin'...OK
orientdb {db=test}>

Hi @Sygyzmundovych
Thank you for reporting, I'll check it ASAP
Thanks
Luigi


Does Dev Home work on Virtual Machine? having issue launching the app

Dev Home version
0.301.198.0
Windows build number
Windows 11 version 22H2 build 22621.1992 on Azure and VMWARE v7
Other software
I enabled developer mode and used winget to install dev home along with SDK on VMWARE/AZURE VM.  When i try to launch Dev Home, nothing happens.  Is Dev Home compatible on a virtual machine or it can only be installed on a physical
Steps to reproduce the bug

Enabled Developer Mode in Settings
Ran the following in PowerShell:

winget install --id "Microsoft.WindowsAppRuntime.1.3" -e
winget install --id "Microsoft.DevHome" -e

Launch Dev Home and nothing happens

/dup #797

@gitunder, Dev Home should run fine on a VM (just tested it from my end). This issue is likely related to an instant crash that is happening for a subset of users since the first release version.


How do I implement on my own dataset

I have got series of folders containing various image data. How do I train with this data as in mobilenet?

Convert your data to tfrecords files with image_dataset_to_tfrecords.py.
Change number of layers and complexity of the network as you like
in src/parts_of_the_net.py file. Look for _mapping function.
Use train.ipynb notebook to train.

I trained ShuffleNet on tiny-imagenet dataset, so I made a couple of changes to the original ShuffleNet architecture. For example, I use stride=1 in the first conv layer instead of stride=2.
Later, I will add more documentation and comments to the project.

where is src/parts_of_the_net.py？

I renamed it as shufflenet/architecture.py.


use capacitor AppLauncher instead of Browser

closes #686, thx for pointing out this capacitor library @TonyGiorgio
also remove the hard-coded primal option... on android it prompts anyway
tested on ios and android and web

CI failing

Does it still work with the URL redirect?


If a user clicks to remove a bookmark that is living on a dashboard, show modal asking for verification.

This modal should pop up when a user clicks to remove a CURRENTLY USED bookmark from the HUD.

@akonsowski - can you give me an update on the status of this ticket? - thanks,

they said they did not want this feature last time i brought it up at itterarion

@akonsowski - thanks for the update. Next time, please update the ticket with the reason(s) why you have changed status in the pipeline. - thanks,


Hide notifications not completely hiding notifications

From @GoogleCodeExporter on May 31, 2015 11:31
What device(s) are you experiencing the problem on?
Motorola Droid Bionic

What firmware version are you running on the device?
5.9.905.XT875.Verizon.en.US

What steps will reproduce the problem?
1. Tasker initiates sendemail.py after Hide Notifications setting is checked
2. Notification appears in notification panel at top of screen
3. Notification disappears when sendemail.py has conpleted

What is the expected output? What do you see instead?
No notifications

What version of the product are you using? On what operating system?
Version 6, rooted Gingerbread

Please provide any additional information below.
I know the hide notifications setting also fixes potential issues with fast
triggers, but doesn't it also hide notifications? If not, I'd like to change
this "issue" to an enhancement request to add a setting to remove notifications.

Original issue reported on code.google.com by heatherleigh on 10 Aug 2012 at 4:42
Copied from original issue: damonkohler/android-scripting#650

This issue was moved to damonkohler/sl4a#72


DRILL-8458: Use correct size of definition level bytes slice when reading Parquet v2 data page

DRILL-8458: Use correct size of definition level bytes slice when reading Parquet data page
Description
The byte buffer slice used for the definition level bytes when reading a Parquet v2 data page is sized correctly (in the call to ByteBuffer::limit)
Documentation
Bugfix only, no documentation changes
Testing
Unit test added in new test class org.apache.drill.exec.store.parquet.TestRepeatedColumn

A test data file name like that would be great thank you. Yes, please may you move the test itself inside TestParquetComplex and see if you can integrate your test data file generation code into ParquetSimpleTestFileGenerator? It already takes a Parquet version number parameter IIRC (up until now, only ever set to v1). I think we may need to come back and organise our tests better for Parquet v2, but I don't want to saddle this PR with that reorganisation.

P.S. if you find the test data generator only fits simply into ParquetSimpleTestFileGenerator as a standalone method that is unrelated to what's there already then I think that's fine. I'm pointing to things things I know are there and related but not going so far as to ask "How would this look in code?"

PR updated with refactored test code


Update OTEL Dependency

Which problem is this PR solving?
In preparation for using the OTel Kafka exporter (#2480) we need to update our OTel dependency.  This came with a fair amount of boilerplate update so I thought it'd be wise to keep them separate for readability.
Short description of the changes

Bumped OTel from v0.8.1-0.20200820012544-1e65674799c8 => v0.10.1-0.20200917170114-639b9a80ed46
Made necessary changes to match upstream
Fixed typo in file name zipkin_recevier.go → zipkin_receiver.go

✓ [endtoend] test_driver→ (services=go) ⇒ Pass

This is passing locally, but failed in CI.  If a maintainer could re-run tests, I would appreciate it.

restarted


Update Mirror

I would like to stay with Mirror. It's much more popular, migrating would require a lot of work, and I am pretty familiar with Mirror API.


Implement simple author disambiguation

Following investigations of the current "rabbit" legacy algorithm (thanks @tsgit), this is a high-level overview of how the simple author disambiguation should work.
First we need to define a few concepts:

signature: an element of authors in a Literature record
author profile: an Authors record
relevant metadata: metadata inside a signature used as an input for disambiguation (i.e. name, ids, email, affiliations), or on the paper (collaboration).

For every non-deleted modified Literature record:

Collect all signatures that have changed/been added compared to the previous version (added = new signature_uuid, changed = same signature_uuid, but relevant metadata has been modified). All of those need to be re-disambiguated (if the record is new, all signatures need to be disambiguated).
For each of those, search its IDs and emails in author records (similar to the exact match in the workflow). If there's only one result, assign the signature to that author.
For each remaining non-assigned signature, do some basic normalization of the name (TBD, might be done in ES directly through analyzers) and check whether there is a unique author record with the same assigned normalized name (by searching in Literature authors). If that's the case, assign the signature to that author.
For each remaining non-assigned signature, there will be either no matching name or several. For each one with no results, do a search for names with compatible initials (same logic as in the query parser). If there is exactly one result, assign the signature to that author. Is this done on legacy? do we want this?
For each remaining non-assigned signature with several matches, we add more information to the search to try to get less ambiguous matches: first collaboration, then affiliations. If there's exactly one match, assign the signature to that author.
For each remaining non-assigned signature, either the match is too ambiguous, or there are no matches. Create a new (stub) record for those and put somewhere in the metadata (_private_notes?) which case it corresponds to.

It's probably a good idea to use inspire-matcher to implement this.

email address is unreliable and often mixed up between authors
this is one reason Heath puts ORCIDs derived from email into subfield k instead of subfield j
and rabbit and autoclaim only look at j
I would advise caution when using email

Is this only for assigning to a profile, not autoclaim? There I would think email would be sufficient. Usually it comes in from catalogers or publisher metadata. Although it can get messed up I don't think it's too common.

I have repeatedly seen emails being swapped between authors, or multiple authors having the same email

True it happens, but at what level? It is an exact match otherwise which is valuable. I don't believe it shows up in Margaret's work with the wrong IDs being in profiles very often (I could ask her about this).

Create 2 tasks:
First one:

For new record add random UUID for every author entry in the paper
For record update, for every new author add random UUID for every author in the paper
Add record ID to new queue for disambiguation

Second one:
It should take a record id from disambiguation queue and match every author (unmatched - without $ref) as described in here:
For each of those, search its IDs and emails in author records (similar to the exact match in the workflow). If there's only one result, assign the signature to that author.
If there will be exact match then store $ref to this author in literature record.


New version not work with Icecast

Any suggestion for work with icecast server?
Metadata and album art not working.

You need two mount points for it to work.

@adoboligh1 I found that too. I just modified the api.php code to allow for 1 mount point.

wow! please share with me , would love to
On Sat, 3 Apr 2021, 9:32 am Ben Sampson, @.***> wrote:

@adoboligh1 https://github.com/adoboligh1 I found that too. I just
modified the api.php code to allow for 1 mount point.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gsavio/player-shoutcast-html5/issues/35#issuecomment-812840475,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKPHXKGJZKT5LVSDPPB3ZZTTG3OCPANCNFSM4Z2B7HDQ
.

Just replace this;
if(is_array($ice_stats["icestats"]["source"])) {

with
if (is_array($ice_stats["icestats"]["source"]) && isset($ice_stats["icestats"]["source"][0])) {

Line 155: https://github.com/gsavio/player-shoutcast-html5/blob/master/api.php#L155

Thanks, I'll check it out. Send A PULL request to the developer then😊
On Sat, 3 Apr 2021, 9:52 am Ben Sampson, @.***> wrote:

Just replace this;
if(is_array($ice_stats["icestats"]["source"])) {
with
if (is_array($ice_stats["icestats"]["source"]) && isset($ice_stats["icestats"]["source"][0])) {
Line 155:
https://github.com/gsavio/player-shoutcast-html5/blob/master/api.php#L155
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gsavio/player-shoutcast-html5/issues/35#issuecomment-812842517,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKPHXKBVHN3RYHQN4G2AYL3TG3QOJANCNFSM4Z2B7HDQ
.

Thanks for the fix

Just replace this;
if(is_array($ice_stats["icestats"]["source"])) {

with
if (is_array($ice_stats["icestats"]["source"]) && isset($ice_stats["icestats"]["source"][0])) {

Line 155: https://github.com/gsavio/player-shoutcast-html5/blob/master/api.php#L155

Thanks for the fix

@adoboligh1 I don't know it well enough to know why it was done like that. It solves my problem and others can use it if they want.
If someone else wants to submit it as a PR, please do.

I Will.
On Sat, 3 Apr 2021, 10:00 am Ben Sampson, @.***> wrote:

@adoboligh1 https://github.com/adoboligh1 I don't know it well enough
to know why it was done like that. It solves my problem and others can use
it if they want.
If someone else wants to submit it as a PR, please do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gsavio/player-shoutcast-html5/issues/35#issuecomment-812843269,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKPHXKA364BZSLJOTQRHMKTTG3RMRANCNFSM4Z2B7HDQ
.

Wow.. thanks... I will try try that

Just replace this;
if(is_array($ice_stats["icestats"]["source"])) {

with
if (is_array($ice_stats["icestats"]["source"]) && isset($ice_stats["icestats"]["source"][0])) {

Line 155: https://github.com/gsavio/player-shoutcast-html5/blob/master/api.php#L155

Thanks @bbashy !!! It works!!!


(GH-397) ChocolateyGUI Globalisation HowTo

there should be a localization-howto.md somewhere in docs
minimum requirements:

[x] basic introduction: the used method for localization in ChocolateyGUI
[x] explanation on howto add new languages that are not available in ChocolateyGUI
[x] explanation on howto test another language that is not the current system language

Relates to #397


Release v178

https://github.com/heroku/heroku-buildpack-python/compare/v177...3e49aeb940df368155ba710d39bf1593a06518a3
Closes<EMAIL_ADDRESS>

$ ./etc/publish.sh
Deploy as version: v178 [y/n]? y

Tagging commit ae56342a81c28682220e3ebec5c377479dc82a85 with v178...
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/heroku/heroku-buildpack-python
 * [new tag]         v178 -> v178
Two-factor code: ********************************************
Publishing buildpack heroku/python... done
Publishing buildpack was successful
Done.

$ h buildpacks:versions heroku/python | head -n4
Version  Released At               Status
───────  ────────────────────────  ─────────
178      2020-09-07T12:23:53.459Z  published
177      2020-08-18T11:59:25.353Z  published

https://devcenter.heroku.com/changelog-items/1880 (no update needed to https://devcenter.heroku.com/articles/python-support#supported-runtimes since 3.5 not in our official support list any more)


Timeout for commands with ACK

D1007 02:07:07.516869 83912 system.py:53] [02:07:07|Debug] Sent command 241 (mavlink_command_sender.cpp:428)
D1007 02:07:07.524811 83912 system.py:53] [02:07:07|Debug] Got timeout! (mavlink_command_sender.cpp:298)
D1007 02:07:07.524998 83912 system.py:53] [02:07:07|Warn ] sending again after 0.00809172 s, retries to do: 3  (241). (mavlink_command_sender.cpp:322)
D1007 02:07:07.535593 83912 system.py:53] [02:07:07|Debug] Got timeout! (mavlink_command_sender.cpp:298)
D1007 02:07:07.535791 83912 system.py:53] [02:07:07|Warn ] sending again after 0.0187866 s, retries to do: 2  (241). (mavlink_command_sender.cpp:322)
D1007 02:07:07.545903 83912 system.py:53] [02:07:07|Debug] Got timeout! (mavlink_command_sender.cpp:298)
D1007 02:07:07.546084 83912 system.py:53] [02:07:07|Warn ] sending again after 0.0291914 s, retries to do: 1  (241). (mavlink_command_sender.cpp:322)
D1007 02:07:07.556502 83912 system.py:53] [02:07:07|Debug] Got timeout! (mavlink_command_sender.cpp:298)

Please note the time between the sends and timeouts (~instant)
It appears to be due to _timeout_s with a default of 0, changed recently from 0.5. Hence me wondering if this was intended or not

Is this intended?
0 timeout seems to be causing issues on my side

Originally posted by @unjambonakap in e889188

Thanks @unjambonakap, presumably that was a mistake. Oh, now I see it! Maybe it didn't load correctly before? In any case, let's fix it.

Thanks for getting back so quickly
I'll make a PR in a bit!
On Mon, Oct 7, 2024, 11:00 AM Julian Oes @.***> wrote:

Thanks @unjambonakap https://github.com/unjambonakap, presumably that
was a mistake. Oh, now I see it! Maybe it didn't load correctly before? In
any case, let's fix it.
—
Reply to this email directly, view it on GitHub
https://github.com/mavlink/MAVSDK/issues/2420#issuecomment-2396332540,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6XYYCJC5CGIBFH46P7HATZ2JESRAVCNFSM6AAAAABPPNMCVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGMZTENJUGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Already done, sorry :)


Fallback to network on navigationRoute cache miss

R: @addyosmani @gauntface
This is 1/3 of #1188
It adds network fallback behavior to the workbox-routing's navigation route in the default export.

If I set a setCatchHandler what happens? Won't this change block it from working as intended?

Prior to this PR, any catchHandler you registered will be triggered when there's a cache miss and either a network failure or no response from the network for networkTimeoutSeconds.
With this PR, any catchHandler you registered will be triggered when there's a cache miss and a network failure, independent of networkTimeoutSeconds.
So that's a change in behavior for developers who are already using catchHandlers.
The argument in favor of this PR is that if we're in a world where "unexpected" cache misses are more likely, developers who would not think to use a catchHandler could benefit from Workbox doing more to provide a response by default.

Why don't we just have a default catch handler that is just the network given the lengths we are going to basically try and fallback to the network.

catchHandlers are tied to a Router instance. Making the change to the underlying strategy, like we do in this PR, let's us default to behaviors for certain strategies that isn't tied to using Router.

@jeffposnick I'm confused by your comment:

Making the change to the underlying strategy, like we do in this PR, let's us default to behaviors for certain strategies that isn't tied to using Router.

This PR is a single change to the Router module.

Apologies about that confusion. Serves me right for putting out different PRs in flight at the same time.

@jeffposnick is this still relevant?

It's still relevant, but it's not something we need to get implemented in time for v3.
I'd like to revisit some of the "cache resiliency" issues for a minor release, post v3.

CC: @philipwalton
So I wanted to revisit this, particularly in light of https://github.com/GoogleChrome/workbox/issues/1441, in which I believe @coryrylan is bumping up against this edge case. (As far as I can tell this scenario the most likely culprit.)
To clarify some of the crossed wires in response to the initial feedback:
This is a focused changes that detects one of two possible failure modes when the handler associated with workbox.routing.registerNavigationRoute() is executing, and it attempts to read the "fallback ULR" from the cache:

Either there's an exception that occurs during the initial caches.match()
Or there's a cache miss
In either case, this PR will cause the handler to attempt to obtain the fallback URL via the network using fetch(), rather than failing completely (and resulting in a broken navigation).

If that fetch() fails, then any default catchHandler that's registered with workbox.routing will still get a chance to deal with that failure. So this change neither requires or prevents a user from registering a global catchHandler.
Asking a user to manually deal with this situation via their own global catchHandler is problematic, because:

The fallback URL and the request's URL aren't the same, and the catchHandler would only have access to the request's URL. So you wouldn't have the context to know that it's the fallback URL which should be fetch()ed inside of the global catchHandler.
Adding in a default, global catchHandler that always did a fetch() can lead to some pathological scenarios. E.g., a network-first strategy times out after X seconds (and there's nothing in the cache), leading to an exception. If that exception triggers another fetch() automatically, then we're going to end up waiting another X seconds for the second failure before we finally give up. This PR just adds in a single fetch() that would execute if there's an issue with the cached response.

I took another pass through the code and added some comments to clarify these points, but I think it's a safe bet to move ahead with. (And it matches what we were doing in sw-precache previously.)

(Also, this PR uses v3 as its base, and it's going to be a mess to rebase to the current master. Assuming there's a 👍, I'm going to close this out and create a fresh PR against master.)

I'm good with this change, and I think falling back to network anytime we're dealing with cache (with the possible exception of cache only) is probably safest.


Security issue?!

The security of the application is a concern for all involved. However the problem is hyped up due to many people trying to make a dime on the fears of others.
Examples:

OWASP https://www.owasp.org/index.php/Category:OWASP_Top_Ten_2017_Project
SKYTALE https://skytale.academy/kurse/web_security_expert.html
mgm security partners https://www.mgm-sp.com/application-security/?gclid=CPD64bD18tQCFc0y0wodRwADOw
and many more

We even got unsolicited advice from "Oliver Weber (olvrweber@gmail.com)" about a vulnerability in the software (only if the user is logged in).
Requirements:

login shall be possible only with HTTPS
switching between HTTPS and HTTP shall be avoided
try to get a free "Symantec Secure Site Starter SSL" from Hostpoint
other?

Installing Let's Encrypt certificates was successfull, see file DropBox/TIXI24/howtos/HowToInstallCertbot.pages(.pdf)

This has been fixed in commit https://github.com/TIXI24/sfitixi/commit/b4f0286e8f64631f1fbacb2999713ec8ae923557


feat: Package for TES dashboard components

Is your feature request related to a problem? Please describe.
There is no package for the dashboard Web Component for Workflow and Task runs.
Describe the solution you'd like
Create separate packages which provide  user friendly Web Components for TES and WES. These components will provide an easy interface bypassing the programmatical approach to execute complex bioinformatics pipelines (selecting input
files, choosing from pre-configured analysis workflows, and customizing the parameters and
settings for the workflow and task) all without having to write code.
Acknowledgement

We thank you for your valuable contribution and would like to acknowledge it
on our contributors page. To help us with that, we would like
to kindly request that you help us with this by commenting on this issue with
a request to the @all-contributors bot of the form
@all-contributors please add @YOUR_GH_HANDLE for TYPE_1, TYPE_2, ..., where
TYPE_1 etc. refer to contribution types supported by the All Contributors
Specification, e.g., idea.

Note that this package would basically be a container component for separate WES and TES packages (each with multiple components for creating and listing workflow and task resources, respectively, and which again may share a set of common utility components).
Possibly the dashboard itself could be made generic to, later on, also include other related components like TRS and DRS clients. No need to fully think through this abstraction now, but it may be useful to consider that there would be such abstraction in the future to inform design choices, i.e., minimize WES/TES specific aspects and, where unavoidable for now, group together such bindings in as few places as possible.

@uniqueg To me, that seems more of a naming concern for the package (#46). In theory, individual packages can be scaled as much as we want, a package say package-a could contain an indefinite number or products, prod-a, prod-b .. so on, so with that regard, its just the matter of package naming which suits the future scope of the package itself.
ui-author would then be able to install package-a and use all its exports, but if we have had different products in different packages initially, that would mean diff npm packages for different products, migrating all the products to one package or vice-versa would then mean deprecating some packages or creating new ones.

Sorry, but I don't understand this comment or what it has to do with what I said. Maybe we are talking cross purposes. Can you tell me what this issue is about, from your perspective?
The title says "TES" and "dashboard", the description mentions "tasks" and "workflows" (which would be WES, not TES).
So which one is it? Is this issue for a TES client, a WES client or a dashboard that integrates the two? My comment was about that last case. If it's supposed to be a dashboard component, I was saying that while we might make that WES and TES specific for now, it may be useful to think that in the future the dashboard might contain other widgets, e.g., for exploring workflows via TRS.

Sorry, that was a misunderstanding; please ignore my last comment.


[chore] use Timeline instead of AnimationLoop

Hubble only uses features of the Timeline object. Eventually it would be great if Hubble could supply a timeline to deck instead of the other way around, since we can then remove the sceneBuilder callback.

Pull Request Test Coverage Report for Build 924240702

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

Totals

Change from base Build 924188885:
0.0%

Covered Lines:
2

Relevant Lines:
2

💛  - Coveralls


icons not resizing in titles and in headings

Describe the bug
icons don't resize in titles and headings. i'm utilizing minimal theme and iconize version 2.8.0
To Reproduce
the inline heading part:

open a note
try to put an icon inline in a heading

the title part:

enable "toggle icon in title"
open a note with a icon attached to it

Expected behavior
icons resize to the size of the headings.
Screenshots

Cannot reproduce. Minimal theme works fine for me!


500 Error - Log says "a bug in vite-plugin-ssr's source code"

Description
Hey, i got a runtime 500 error on a request to my vite server and the server has the following log:
Error<EMAIL_ADDRESS>You stumbled upon a bug in vite-plugin-ssr's source code. Reach out at https://github.com/brillout/vite-plugin-ssr/issues/new or https://discord.com/invite/qTq92FQzKb and include this error stack (the error stack is usually enough to fix the problem). A maintainer will fix the bug (usually under 24 hours). Do not hesitate to reach out as it makes vite-plugin-ssr more robust.

    at assertUrlPathname (/node_modules/vite-plugin-ssr/dist/cjs/utils/parseUrl.js:130:25)

    at analyzeBaseUrl (/node_modules/vite-plugin-ssr/dist/cjs/utils/parseUrl.js:134:5)

    at parseUrl (/node_modules/vite-plugin-ssr/dist/cjs/utils/parseUrl.js:48:36)

    at hasSuffix (/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage/handlePageContextRequestUrl.js:15:65)

    at handlePageContextRequestUrl (/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage/handlePageContextRequestUrl.js:8:10)

    at initializePageContext (/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage.js:136:140)

    at runMicrotasks (<anonymous>)

    at async renderPage_ (/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage.js:30:41)

    at async renderPage (/node_modules/vite-plugin-ssr/dist/cjs/node/renderPage.js:155:16)

    at async /packages/client/server/index.ts:43:25

vite.config.ts:
import react from "@vitejs/plugin-react";
import ssr from "vite-plugin-ssr/plugin";
import { UserConfig } from "vite";
import { resolve } from 'path'

const config: UserConfig = {
  plugins: [
    react({
      babel: {
        babelrc: false,
        configFile: false,
        plugins: [
          [
            "babel-plugin-styled-components",
            {
              ssr: true,
            },
          ],
        ],
      },
    }),
    ssr({ prerender: false }),
  ],
  resolve: {
    alias: {
      "@src": resolve(__dirname, "./src"),
    },
  },
};

export default config;

versions:
    "@vitejs/plugin-react": "^2.0.1",
    "vite": "^3.0.9",
    "vite-plugin-ssr": "^0.4.41"

Update to the latest version. Let me know if you still get the issue and I'll re-open.


Release/0.2.0

Release 0.2.0 provides new features on bulk entity classifications and simplification of support for Azure Purview and working with the Atlas Entity and Base Type Def classes in the AtlasClient / PurviewClient methods for upload.
Addresses the following issues.

#48 with updating the way update lineage is mapped in the readers, supporting multiple inputs and outputs in the same sheet / upload.
#54 with the bulk entity classifications endpoints being mapped to several functions.
#58 with the PurviewClient and two decorators to denote limitations of Purview vs Atlas support.
#59 with the kwargs of upload_typedef now allowing specific entityDefs, relationshipDefs being referenced.
#60 with supporting AtlasEntity in a list for the upload_entities method.

Lastly, this PR updates the main samples to now use the Purview client rather than the AtlasClient. If a user wants to use the AtlasClient they still can but they will have to modify the samples.

#Approve

#Approve


Adding support for named AMD modules.

This pull request adds support for named AMD modules and addresses the pain point of using TypeScript-generated AMD modules when anonymous modules and out-of-the-box bundlers (like r.js) are not an option.
This feature was previously discussed at https://typescript.codeplex.com/discussions/451454 and https://typescript.codeplex.com/workitem/285 where it was resolved as external/won't fix, but this feature was a big enough pain point in our recent adoption of TypeScript to warrant further investigation.

Just tried out this feature for the first time and found that the explicit name suppied in the "amd-module" directive was not then subsequently used when importing into another module. but kept the value used in the require statement.
/* app\classes\MyClass.ts */
/// <amd-module name="MyClass" />
class MyClass {
   ...
}

/* app\classes\MyClass.js */
define("MyClass", ["require", "exports"], function(require, exports) {
    ...
}

/* app\MyApp.ts */
import MyClass = require("classes/MyClass");
class MyApp {
    ...
}

/* app\MyApp.js */
define(["require", "exports", "classes/MyClass"], function(require, exports, MyClass) {
    ...
}

In this example I would have expected MyApp.js to use "MyClass" not "classes/MyClass" for the dependency name.
Is this expected ?  If so is there any plans to "close the loop" ?

The ///  is just used when emitting the file. it is more of an emitter directive if anything. We will need some clear language syntax that denoted a module name when it is different from a file name. possibly related to #17. Currently the assumption is that module names and file names are in sync, which does not really work with bundling scenarios, which i am amusing is what you are trying to do. We are looking into making module resolution work better with common AMD/CommonJS/SystemJs patterns (take a look at #2338).

Could this be realized
When in the module exists amd-module then need to be created .d.ts file, which will be located in well known place named_modules in the root directory of the project for example, then easy can be created reference to them from TypeScript and loading of JS files will be left to whichever module loader. If module name is "something1/somthig2/somthig3" then directory structure will be :
project
named_modules
something1
somthig2
somthig3.d.ts
only one catch here is, module do not need contain references to others with ./ or ../ - all references need to be typings


CSS & HTML evaluator

TODO:

[ ] compiler

[ ] global CSS (needed to get rid of padding)
[ ] overrides
[ ] watcher

[ ] Tidy

[ ] clean up project code, add comments
[ ] Ensure that we're not compiling more than what's necessary
[ ] Move IO to graph struct?

Test TODOs:

[ ] test "watch" functionality

[ ] Ensure that dependents are re-compiled

[ ] cache graph compilation (need to incude hash on dependency)


Copying snapshot of running instance fails on non-thin LVM pools

lxc storage create lvm lvm lvm.use_thinpool=false
lxc init images:ubuntu/focal v1 --vm -s lvm
lxc snapshot v1
lxc copy v1/snap0 v2 # OK
lxc delete v2
lxc start v1
lxc copy v1/snap0 v2 # Fails with Error: Create instance from copy: Failed to deactivate LVM logical volume "/dev/lvm/virtual-machines_v1.block": Failed to run: lvchange --activate n --ignoreactivationskip /dev/lvm/virtual-machines_v1.block: Logical volume lvm/virtual-machines_v1.block in use.

This issue is due to the way that with non-thin LVM pools, activating a snapshot volume will also activate the origin volume (and vice versa).
It is also to do with the limitation the storage subsystem currently has around expressing the concept of a 2-stage "mount" (i.e that some volumes need both activating and mounting, and thus when stopping the operation we may only need to undo one of those actions depending on what was needed to "mount").
I think only affects the VM instance volumes, because only they have this form of mount duality.


Recommended preset

Does this packages have a preset with recommended rules like tslint:recommended?

Not at the moment

This would be a nice add for our team - we want to do another pass at improving our linting but activating each rule individually is a bit time-consuming.

This has been discussed before, since a preset is opinionated this would cause many issues being open arguing about how to best set the configuration. I think this type of configurations should be left to another project, take https://github.com/blakeembrey/tslint-config-standard for instance.

@jmlopez-rod Thanks for the thoughts - we'll look over that repo!

Closing since we don't plan to have this.

I know I'm late to the party, but it would be nice to have a recommended preset that enables the same rules as the ones in ESLint's recommended preset.

It seems like the work is already being done to determine which rules are recommended (they are marked as "(Recommended)" in the README), so why not just publish this as a preset? Currently it's a very laborious process to actually write out the rules you want to use, going through the README one by one and transcribing to your tslint.json.

Totally agree with @pelotom - the cognitive work here is already done, publishing a recommended preset is the easy bit. Would you not accept a PR? @buzinas?


Thermostat service

Device Model
HeaterCoolor service vs Thermostat service
Is there an existing issue for this?

[X] I have searched the existing issues and did not find an existing issue.

Supported by Zigbee2MQTT?

[X] Device is supported by Zigbee2MQTT

Missing features / functionality
Nothing is missing, just inquiring about the finer details of exposing thermostat services to HomeKit.
HomeKit Services and Characteristics
HMServiceTypeHeaterCooler
HMServiceTypeThermostat
Exposes information from Zigbee2MQTT
n/a

Additional information / Other remarks
I'm curious if the properties exposed by Zigbee2MQTT define what "type" of thermostat Z2M creates for HomeKit?
For example, I have a thermostat which is a full feature (heating and cooling) thermostat, but I only use it connected to a furnace. (You helped me expose it in HomeKit by hiding the occupied_cooling_setpoint property.)
I'm not sure about the older Thermostat service, but I believe the default modes for the newer HeaterCooler service are AUTO, COOL, HEAT and OFF. Is there a way to hide other properties which then cause Z2M to reveal the Thermostat to HomeKit as just HEAT?
From researching, I gather that you can define specifically which modes to present, and can turn off unnecessary ones. It is locked to all four modes.
Is there any way to allow that selection to be made, or would it be very complicated? I have several actual heat only thermostats which still show all four modes. Also, I would love to eliminate AUTO entirely, always, because I I don't care for the way it works and just find it to be clutter.
I gather it is quicker and easier to interact with a heat-only Thermostat if HEAT is the only mode presented. (The widget displays differently.)
Thanks for your work on this plugin! This is more of a refinement curiosity, because everything already works perfectly!

I'm thinking my question must have been poorly explained, or of no interest at all. I'll go ahead and close out.


[BUG] Error CS7069 Reference to type 'MediaElement' claims it is defined in 'Xamarin.Forms.Core', but it could not be found

Describe the bug

After upgrading to Xamarin Forms <IP_ADDRESS>4, my project now fails to compile with the error CS7069 Reference to type 'MediaElement' claims it is defined in 'Xamarin.Forms.Core', but it could not be found for ReactiveUI .Events
This seems to be related to MediaElement changes as described in the Xamarin Forms <IP_ADDRESS>4 release notes

C# UI, Expander, and MediaElement Moved
These experimental features have been (or will be soon) migrated to the Xamarin Community Toolkit which everyone should be taking full advantage of. It's a wonderful library of extremely useful Xamarin controls, effects, value converters, and more. In fact, it even has a native CameraView, Avatar view, and RangeSlider control. These features and controls are continuing to grow and improve, and while Xamarin.Forms moves into an extended stable release, we feel it's better for those to ship for now in the tookit. At a future time, they may be brought back into the core library.

Adding the Xamarin Community Toolkit to the project, did not resolve the issue.
Steps To Reproduce

Use ReactiveUI Events in code
Upgrade to Xamarin Forms <IP_ADDRESS>4
Code no longer compiles
Workaround
Downgrade to Xamarin Forms <IP_ADDRESS>1
Expected behavior

Screenshots

Environment

OS:
Version
Device:

Additional context

Consider using pharmacist in your netstandard forms project. It will be a 100% match to your xamarin forms version

Consider using pharmacist in your netstandard forms project. It will be a 100% match to your xamarin forms version

The plan is to soonish deprecate the events based projects in favour of pharmacist btw.

The plan is to soonish deprecate the events based projects in favour of pharmacist btw.

Duplicate of #2638

Duplicate of #2638

+1

any idea to resolve it?

@josuepmarchena, as stated, you can downgrade your version of Forms as a work-around. The other work-around I've found is to stop using the ReactiveUI.Events.XamForms-library, as @glennawatson suggests - either by moving to Pharmacist or by simply not using the functionality it provides.

@glennawatson, the problem with the solution you're proposing, at least for me, is that my project uses a lot of NuGets hosted on a private repo. This still seems to cause issues.

@AlexanderMelchers, Thank you very much, I think, for now, I'm going to downgrade the Xamarin.Forms version

Use of the source generators or pharmacist is recommended if there is a mismatch with xamarin forms and our version. We also have bumped the Xamarin Forms to v5 now.


Command line injection on user data

Stratos Version

4.4.0
Frontend Deployment type

[ ] Cloud Foundry Application (cf push)
[ ] Kubernetes, using a helm chart
[ ] Docker, single container deploying all components
[ ] npm run start
[X] Other (please specify below)

Backend (Jet Stream) Deployment type

[ ] Cloud Foundry Application (cf push)
[ ] Kubernetes, using a helm chart
[ ] Docker, single container deploying all components
[ ] Other (please specify below)

Expected behaviour
Avoid using shell execution and/or a user-controlled variables in a shell context. Prefer instead using either a buitin API for the same functionality, or the command itself instead of spawning a shell to run it.
Example Code
cmd := exec.Command("ls", "tmp/MYUSER")
Actual behaviour
Use of direct shell execution and/or a user-controlled variables under exec.Command, exec.Context, or syscall.Exec can introduce command injection vulnerability.
Example Code
cmd := exec.Command("ls", "tmp/" + username)
cmd2 := exec.Command("/bin/sh", "-c", "touch tmp/" + username + "/" + filename)
Steps to reproduce the behavior
cfmr-ui\src\jetstream\plugins\analysis\container\kubescore.go:30
cfmr-ui\src\jetstream\plugins\cfapppush\vcs.go:101
Log output covering before error and any error statements
Insert log hereCopy

Detailed Description

command line injection on user passed data
Context

Possible Implementation

Both uses are within our controlled code


Update run-av-scan.md

Updated important note about supported OS

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5811


UI - Remove underlines/border-bottom from breadcrumb

Hi team,
Using border-bottom as a dotted underline is usually a bad practice. I have reported this a few times internally to @adamcogan but apparently we are still using it :)
It generates a pixel difference in the height which in some screens/sites may generate a glitch like the below (see how the content is pushed 1px down on hovering "SSW Rules" link):

In this case, there is a second issue which is the inconsistency between the first link (dotted) and the second link (solid).
I think it's pretty obvious that those are links, so the borders are mostly noise in the breadcrumb
I also think the text in red on hover is enough

Can we remove the borders from breadcrumbs on both states (a:link and a:hover) ?

The breadcrumb looking nice and clean without the borders:

Cheers,
Tiago
AB#59377

One more reason to remove borders - it goes over the actual text depending on the available area - see when you have more than 1 category:

One more reason to remove borders - it goes over the actual text depending on the available area - see when you have more than 1 category:

Hey @christianmorfordwaitessw
As per our conversation, these are the things I'd like to see improved in the breadcrumb:

Make markup is consistent (some .breadcrumb-content are in  others in )
We may keep the divs for technical reasons, but the CSS classes should be used in the same HTML tags
The red color on hover is not SSW default
The correct color is #cc4141
The underline is a border... and we believe we should not have them...
Since Adam will probably not approve removing them, we should we least make them "text-decoration:underline;" instead of "border-bottom"

The above should allow us to have a cleaner CSS
Thanks,
Tiago

As per my conversation with @adamcogan
I've

Updated the rule: https://rules.ssw.com.au/do-you-use-underlines-only-on-links
Fixed the breadcrumb on Rules in this PR: https://github.com/SSWConsulting/SSW.Rules/pull/328

Tiago

Cc: @adamcogan
Thanks @tiagov8,

Fixed the breadcrumb on Rules in this PR: #328

Change has been deployed to production


Not uploading to Google Drive

So I've been trying to configure everything, but no matter what it seems that the files are never encrypted and uploaded to Google Drive. Seems to never encrypt anything either. Here's the log from cloudupload.

[ 2017-10-14@12:53:07 ] Transfering file -> /mnt/Library/Plex-Servers/PleXXX/local-decrypt/PleXXX/PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/season-specials.tbn to Google Drive in /PleXXX/TV Shows/Halo 4 - Forward Unto Dawn.
[ 2017-10-14@12:53:07 ] Transfering file -> /mnt/Library/Plex-Servers/PleXXX/local-decrypt/PleXXX/PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/season01-banner.jpg to Google Drive in /PleXXX/TV Shows/Halo 4 - Forward Unto Dawn.
[ 2017-10-14@12:53:08 ] Transfering file -> /mnt/Library/Plex-Servers/PleXXX/local-decrypt/PleXXX/PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/season-specials-banner.jpg to Google Drive in /PleXXX/TV Shows/Halo 4 - Forward Unto Dawn.
[ 2017-10-14@12:53:09 ] Transfering file -> /mnt/Library/Plex-Servers/PleXXX/local-decrypt/PleXXX/PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/.actors/Tom_Green.tbn to Google Drive in /PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/.actors.
[ 2017-10-14@12:53:09 ] Transfering file -> /mnt/Library/Plex-Servers/PleXXX/local-decrypt/PleXXX/PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/.actors/Anna_Popplewell.tbn to Google Drive in /PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/.actors.
[ 2017-10-14@12:53:10 ] Transfering file -> /mnt/Library/Plex-Servers/PleXXX/local-decrypt/PleXXX/PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/tvshow.nfo to Google Drive in /PleXXX/TV Shows/Halo 4 - Forward Unto Dawn.
[ 2017-10-14@12:53:11 ] Transfering file -> /mnt/Library/Plex-Servers/PleXXX/local-decrypt/PleXXX/PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/folder.jpg to Google Drive in /PleXXX/TV Shows/Halo 4 - Forward Unto Dawn.
[ 2017-10-14@12:53:12 ] Transfering file -> /mnt/Library/Plex-Servers/PleXXX/local-decrypt/PleXXX/PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/poster.jpg to Google Drive in /PleXXX/TV Shows/Halo 4 - Forward Unto Dawn.
[ 2017-10-14@12:53:12 ] Transfering file -> /mnt/Library/Plex-Servers/PleXXX/local-decrypt/PleXXX/PleXXX/TV Shows/Halo 4 - Forward Unto Dawn/season01.tbn to Google Drive in /PleXXX/TV Shows/Halo 4 - Forward Unto Dawn.
root@PleXXX:/mnt/Library/Plex-Servers/PleXXX#

What is your rclone.conf? The logging it kind of... meh :) The transferring is a echo before the rclone command. So if it's not uploading anything, then the rclone.conf is wrong.

So the configuration I'm looking to have is:
/mnt/Library/Plex-Servers/PleXXX/{local-media, cloud-encrypt, etc...} #Local Media and Scripts location
gd:PleXXX/{Plex Library Folders} #Drive Location for Plex Servers
I have all of the configuration files updated to reflect "/mnt/Library/Plex-Servers/PleXXX/" instead of "/opt/cloud-media-scripts/" so all of the ./scripts/{mount.remount, cloudupload, etc} work without errors from them directly.
So I everything located here:
root@PleXXX:/mnt/Library/Plex-Servers/PleXXX# ls
cloud-decrypt  cloud-encrypt  config  cron  INSTALL  LICENSE  local-decrypt  local-media  plexdrive  rclone  README.md  scripts  setup.sh  uml_diagram.png

Here is my rclone.conf:
[gd]
type = drive
client_id = <CLIENT_ID>
client_secret = <CLIENT_SECRET>
token = ***

[gd-crypt]
type = crypt
remote = gd:PleXXX
filename_encryption = standard
password = ***
password2 = ***

[local-crypt]
type = crypt
remote = /cloud-encrypt/PleXXX
filename_encryption = standard
password = ***
password2 = ***

Actually, I think I finally got it! I missed one configuration spot that I didn't change... Debian had some different locations from the original script running and installing and whatnot.

Whelp, I thought I did...
2017/10/14 16:59:34 ERROR : Attempt 1/3 failed with 1358 errors and: couldn't list directory: Get https://www.googleapis.com/drive/v2/files?alt=json&fields=items%28id%2CdownloadUrl%2CexportLinks%2CfileExtension%2CfullFileExtension%2CfileSize%2Clabels%2Cmd5Checksum%2CmodifiedDate%2CmimeType%2Ctitle%29%2CnextPageToken&maxResults=1000&q=trashed%3Dfalse+and+%270B7irD2yyQw8dWXB4enNyeEpidzA%27+in+parents+and+title%3D%27j0hbn85nl6qd2kt591lvhas8gs%27+and+mimeType%3D%27application%2Fvnd.google-apps.folder%27: oauth2: cannot fetch token: 401 Unauthorized
Response: {
  "error" : "invalid_client",
  "error_description" : "The OAuth client was not found."

That means you didn't setup rclone properly. Make sure you press N and copy the URL to get your validation code to enter.

For some reason it kept reverting back to  and  in the configuration file. Made the file readonly, and now it seems to be sticking.


close acc resolver

as a dev, I want users and admins to be able to close accounts

merged with approveaccount


[Snyk] Upgrade nodesub from 0.0.9 to 0.0.12

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade nodesub from 0.0.9 to 0.0.12.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released 21 days ago, on 2023-06-08.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

please do this project in go. It will be easy to install. it's not installable now. Too much slow process and prone to error.


generator type now case insensitive to users input

As Referenced In https://github.com/driftyco/ionic-app-generators/issues/9
.
Since the CONSTANTS for the Gen type are all lowercase, all I did here was make the user input all lowercase to match the utils for generatorType.
so if a user now does something like Pipes, PIPE or pipe it shouldn't make a difference as long as the spelling of the param is correct for the generatorType

should also fix https://github.com/driftyco/ionic-app-generators/pull/11

@jthoms1 any word on this?

@danbucholtz @jthoms1 any info on this?

@saniyusuf,
Hi Sani, just seeing this now. We are totally revamping generators in app-scripts right now. They should launch within the next two weeks.
Thanks,
Dan


Remove or improve Configurator's 'sesame' option

sesame (Optional): Secret token to dynamically allow access from the IP the request originates from. Open your bookmark https://hassio.yourdomain.com:8123/somesecretnobodycanguess while allowed_networks is set to [] and boom! Open Sesame! You can use the Network status menu to revoke IP addresses for which access has been granted.

From a security point of view is this a pretty high risk. The token can be anything, as far as I can tell, which make it vulnerable for enumerations and simple guessing. The token is part of the request and will be visible in logs. It looks also like that we are facing a similar issue as with #14345 here.

I think having the sesame-option is far less insecure than having to allow access from <IP_ADDRESS>, which otherwise needs to be done for people who connect externally. So everybody with SSL who doesn't have a local DNS routing internally instead will just be protected by credentials. Attackers can start cracking the credentials right away. With the sesame it's credentials plus the token, with the requirement to brute force the token before you can even brute force the credentials.
From my point of view the sesame is about the same as having hass allow from <IP_ADDRESS> along with a strong API_KEY. A difference worth mentioning: attackers scanning random IPs will always get a 420 (policy not fulfilled) error. They would have to know that they are attacking the configurator with activated sesame to even think of brute forcing the sesame token.

This will allow to use a TOTP based sesame token instead of a static one. 6 digits provide much less entropy, but since these tokens are only valid for 30 seconds this seems fairly secure to me and makes brute forcing hard.


How to prevent tab clicks jumping to top

Hello Cristi,
First of thank you for this great component, we are using your Vue Paper Dashboard Pro and making some customization. As you know Vue Tabs is in that theme, and we thought we can use this in our front page too and completed the design. But if we click on the tab, it jumps to the top. I looked at your demo and our admin pages, it doesn't jump all the time. Changing the # link to #/ fixes the problem, but couldn't fix it because I'm using your library as dependency, what do you think, how can I overcome this problem?
Regards.

Hi @abdullahonden Please make sure you have the latest version installed. 0.5.6. There was a bug in 0.5.5 that you are describing.

Wow, thank you :)

Closing the issue if this solved the problem. Happy coding :)


No longer in-place modify input to apply

In Pennylane PR #4485, tape.operations will no longer be the sum of tape._prep and tape._ops.
This means any modification of the tape.operations list will mutate the tape itself, instead of a shallow copy of its contents.
A basic example of this can be shown with the below list manipulations:
>>> a = [1]
>>> b = [2]
>>> c = a+b
>>> c[0] = 5
>>> c
[5, 2]
>>> a
[1]
>>> d = a
>>> d[0] = 5
>>> a
[5]

Long story short, we do not want to in-place modify the operations list anymore. So instead of using del operations[0], I simply select out the contents from index one onward.

@albi3ro Don't you also want this fixed on master?

@albi3ro, feel free to merge it. You can ignore the CI fails.

@albi3ro Don't you also want this fixed on master?

I can open up a PR to master if need be.

I can open up a PR to master if need be.

I can do it too, I meant do you need it out asap (for example if this is a blocker in some CI pulling lightning@master)? Because  merge/monorepo will take some more time.

I can open up a PR to master if need be.

I can do it too, I meant do you need it out asap (for example if this is a blocker in some CI pulling lightning@master)? Because merge/monorepo will take some more time.

Let's get it into master now too then, as the CI is likely going to be heavily hit today, and having the most recent version will be worthwhile.

I can open up a PR to master if need be.

I can do it too, I meant do you need it out asap (for example if this is a blocker in some CI pulling lightning@master)? Because merge/monorepo will take some more time.

Let's get it into master now too then, as the CI is likely going to be heavily hit today, and having the most recent version will be worthwhile.

Will take care of it.


Improve Python syntax highlighting

This pull request improves syntax highlighting for Python language.
What was changed:

Types color:
def foo(a: int) -> float:
           ^^^     ^^^^^
           here    here

Parameters color:
def foo(a: int):
    pass

foo(a=5)
    ^
   here

Special functions color (__init__, __str__, __repr__ etc.)

self keyword color

Decorators color:
class Foo:
    @staticmethod
    ^^^^^^^^^^^^^
        here
    def static_method():
        pass

All colors were taken from the PyCharm 2023.2 classic UI color theme.
Before:

After:

@congard, undeniably, your edits related to colors of tokens must be included. However, Darcula Solid for VS Code follows the color scheme from the eponymous theme for JetBrains IDEs, so colors should be like in the screenshot below:

@congard, UPD: unfortunately, yellow brackets highlighting looks bad with colors from the original theme, and there is no way to avoid it without creating a similar theme specially for Python, because brackets highlighting is being defined outside the tokenColors section.
I've decided to use colors from JS / TS for self parameter and Python's types for better appearance, although it looks a bit different than in the original theme.

@jussiemion looks good to me. However, in my opinion, it would be better to visually distinguish self from keywords like class, def, if, None, etc. self is not a keyword; it is just a special variable, so it shouldn't have the same color as keywords.

@congard, I'm sure that the color theme shouldn't use a lot of different (and especially - high contrasting) colors for a consistent UI that is good for comfortable working for a long time. At the same time, people usually use VS Code with bolder fonts, so original colors from PyCharm will have worse appearance here. That's why I wanna suggest following for Darcula Solid adaptation:
Special functions. I guess that there is no necessity to define a different color for them as they visually stand out with their underscores at beginning and ending, e.g. __str__. It's already enough to realize that we're having business with a special function, so let's define for them the pale yellow color (#ffc66d), like regular functions have.
Function parameters. To be honest, red highlighting for function arguments is quite weird and makes the UI too flashy, so let's keep their default color.
Decorators. De facto they're functions, only one difference is that you use it a bit another way, writing them using well known decorator syntax. However, I guess, it's not such a strong reason to define a different color for them, color of regular functions (#ffc66d) will fit not bad too.
Self. It's a special parameter for representing a current class instance, and it should have some unique color. I'm sure, that's a really good moment to extend the color palette with #9899bf and use it for self.
Types. Darcula Solid already has the pale blue color for types (#8ba6c2), so let's re-use it.
With all these edits applied we'll have much better result, although it looks a bit different than the theme from PyCharm:


Run CI

(Sorry, meant to open this against my own fork. I'm attempting to debug this issue (https://github.com/astral-sh/uv/issues/1921#issuecomment-2058056192) reported by huggingface/datasets on the uv repo.)


Zihan/add hotjar

Description
#228 doesn't work. Trying another solution here.
Checklist

Do all Lints pass?

[] Have you ran pnpm spellcheck?
[] Have you ran pnpm fmt?
[] Have you ran pnpm lint?

Tested with https://deploy-preview-230--aptos-developer-docs.netlify.app/. Worked


Anybody got this "gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system"  error before?

I have been encountering this error recently, and the log generated by this error has unexpectedly expanded my syslog and user.log to 10GB (almost filling up my SD card). Does anyone know how to solve this error?
2024-07-30T22:26:45.183731+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system
2024-07-30T22:26:45.183779+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system
2024-07-30T22:26:45.183825+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system
2024-07-30T22:26:45.183867+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system
2024-07-30T22:26:45.183915+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system
2024-07-30T22:26:45.183960+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system
2024-07-30T22:26:45.184002+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system
2024-07-30T22:26:45.184050+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system
2024-07-30T22:26:45.184093+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system
2024-07-30T22:26:45.184141+08:00 NHI-RaspberryPi-4B gpsd[748]: gpsd:ERROR: accept: fail: Too many open files in system

and looks it create log super fast, this is my first time encountering this situation, is there anything I should check first?

I couldn't find any hints about an existing problem with gpsd that would cause that.
My best guess would be: something else in your system exhausts file-handles.
One way to narrow things down would be to disable all other services and software you are running on the Raspberry, and check if the problem still exists?


add Ki logo asset

Thank you!

Hi! Can you please make sure this is only the icon (and not the gitpod file) - thanks

added in 6c9c049b70bc8d78b4ad12b0e388c948a9d1967a


Naming guidelines for folders

What would be your naming guideline for naming folders?
content-blocks as the filenames or contentBlocks camelcased

Up to your preference. Craft won't care either way.