build logs and status is not working with OpenShift

Description
For OpenShiftv3.7 build logs not coming with build goal. It keeps throwing following backoff messages
Info
-> [INFO] F8: Creating ImageStream http-vertx
-> [INFO] F8: Starting Build http-vertx-s2i
-> [INFO] F8: Waiting for build http-vertx-s2i-1 to complete...
-> [INFO] Current reconnect backoff is 1000 milliseconds (T0)
-> [INFO] Current reconnect backoff is 2000 milliseconds (T1)
-> [INFO] Current reconnect backoff is 4000 milliseconds (T2)
-> [INFO] Current reconnect backoff is 8000 milliseconds (T3)
-> [INFO] Current reconnect backoff is 16000 milliseconds (T4)
-> [INFO] Current reconnect backoff is 32000 milliseconds (T5)

f-m-p version : v3.5.34
Maven version (mvn -v) :
Apache Maven 3.3.9 (NON-CANONICAL_2016-07-01T11:53:38Z_mockbuild; 2016-07-01T17:23:38+05:30)
Maven home: /usr/share/maven
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>-1.b12.fc25.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.11.10-200.fc25.x86_64", arch: "amd64", family: "unix"

Kubernetes / OpenShift setup and version : v3.7.0
If it's a bug, how to reproduce : run mvn fabric8:build
If it's a feature request, what is your use case : issue
Sample project : https://github.com/fabric8io/fabric8-maven-plugin/tree/master/samples/spring-boot

Description
For OpenShiftv3.7 build logs not coming with build goal. It keeps throwing following backoff messages
Info
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@399df1a2 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@7c9f68f5[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 2]
-> 	at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
-> 	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
-> 	at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
-> 	at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533)
-> 	at java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:729)
-> 	at io.fabric8.kubernetes.client.dsl.internal.WatchHTTPManager$3.run(WatchHTTPManager.java:207)
-> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
-> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
-> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
-> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
-> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
-> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
-> 	at java.lang.Thread.run(Thread.java:748)

f-m-p version : v3.5.34
Maven version (mvn -v) :
Apache Maven 3.3.9 (NON-CANONICAL_2016-07-01T11:53:38Z_mockbuild; 2016-07-01T17:23:38+05:30)
Maven home: /usr/share/maven
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>-1.b12.fc25.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.11.10-200.fc25.x86_64", arch: "amd64", family: "unix"

Kubernetes / OpenShift setup and version : v3.7.0
If it's a bug, how to reproduce : run mvn fabric8:build
If it's a feature request, what is your use case : issue
Sample project : https://github.com/fabric8io/fabric8-maven-plugin/tree/master/samples/spring-boot

Confirmed, build logs are not showing up on OpenShift 3.7.0. These reconnect
backoff statements appearing in logs are from WatchHttpManager. basically, reconnect attempts whenever we have lost our watch.
Watching over pods in OpenShift 3.7.0, I observed that build pod is taking some time
to get ready, and some more intermediate states:

fabric8-maven-sample-spring-boot-s2i-4-build   0/1       Pending   0         0s
fabric8-maven-sample-spring-boot-s2i-4-build   0/1       Pending   0         0s
fabric8-maven-sample-spring-boot-s2i-4-build   0/1       Init:0/2   0         0s
fabric8-maven-sample-spring-boot-s2i-4-build   0/1       Init:0/2   0         2s
fabric8-maven-sample-spring-boot-s2i-4-build   0/1       Init:1/2   0         4s
fabric8-maven-sample-spring-boot-s2i-4-build   0/1       PodInitializing   0         5s
fabric8-maven-sample-spring-boot-s2i-4-build   1/1       Running   0         6s
fabric8-maven-sample-spring-boot-2-deploy   1/1       Terminating   0         16s
fabric8-maven-sample-spring-boot-2-deploy   0/1       Terminating   0         17s
fabric8-maven-sample-spring-boot-s2i-4-build   0/1       Completed   0         10s
fabric8-maven-sample-spring-boot-3-deploy   0/1       Pending   0         0s
fabric8-maven-sample-spring-boot-3-deploy   0/1       Pending   0         0s
fabric8-maven-sample-spring-boot-3-deploy   0/1       ContainerCreating   0         0s
fabric8-maven-sample-spring-boot-3-deploy   1/1       Running   0         1s
fabric8-maven-sample-spring-boot-2-deploy   0/1       Terminating   0         18s
fabric8-maven-sample-spring-boot-2-deploy   0/1       Terminating   0         18s

On the other hand, when i run these on OpenShift 3.6.0, i get:
fabric8-maven-sample-spring-boot-s2i-1-build   0/1       Pending   0          0s
fabric8-maven-sample-spring-boot-s2i-1-build   0/1       Pending   0         0s
fabric8-maven-sample-spring-boot-s2i-1-build   0/1       ContainerCreating   0         0s
fabric8-maven-sample-spring-boot-s2i-1-build   1/1       Running   0         7s
fabric8-maven-sample-spring-boot-s2i-1-build   0/1       Completed   0         1m
fabric8-maven-sample-spring-boot-s2i-2-build   0/1       Pending   0         0s
fabric8-maven-sample-spring-boot-s2i-2-build   0/1       Pending   0         0s
fabric8-maven-sample-spring-boot-s2i-2-build   0/1       ContainerCreating   0         0s
fabric8-maven-sample-spring-boot-s2i-2-build   1/1       Running   0         1s
fabric8-maven-sample-spring-boot-s2i-2-build   0/1       Completed   0         6s
fabric8-maven-sample-spring-boot-1-deploy   0/1       Pending   0         0s


xfail test_describe when using Pandas 0.24.2

I observed some test failures over in #5947 that I think are unrelated to the changes in that PR. This PR runs CI on the current master

Looks like CI was temporarily broken because Appveyor was pulling in Pandas 0.24.2, which has a bug causing test_describe to fail. This PR now xfails that test when using Pandas 0.24.2
cc @TomAugspurger


Support request for custom tf model

Hello, I would like to know if the compiler can support 3d cnn.
A full list of currently supported tf functions would be helpful.
The list on the website seems really short.

@jessecha
If you are talking about conv3d like this, https://www.tensorflow.org/api_docs/python/tf/nn/conv3d
No, we don't support that operator. All the operators supported are listed here.
https://aiyprojects.withgoogle.com/vision/#makers-guide


Bootstrap not imported

Hi there,
in my project I'm using bootstrap--loader within the entry configuration, in storybook I have:
import { configure } from '@kadira/storybook';
import 'bootstrap-loader';

function loadStories() {
  require('../src/views/visualization/widgets/widget-container/react-component-stories.jsx');
  require('../src/views/visualization/widgets/horizontal-data/react-component-stories.jsx');
}

configure(loadStories, module);

and
const path = require('path');
const paths = {
  root: __dirname,
  src: path.join(__dirname, '..', 'src'),
  build: path.join(__dirname, '..', 'dist'),
  static: path.join(__dirname, '..', 'static'),
  node_modules: path.join(__dirname, '..', 'node_modules')
};
const ExtractTextPlugin = require('extract-text-webpack-plugin');

module.exports = {
  module: {
    loaders: [
      { test: /\.less$/, loader: `style!css?root=${paths.static}&sourceMap&importLoaders=2&localIdentName=[local]___[hash:base64:5]!autoprefixer?browsers=last 2 version!less?outputStyle=expanded&sourceMap` },
      { test: /\.scss$/, loader: `style!css?root=${paths.static}&sourceMap&importLoaders=2&localIdentName=[local]___[hash:base64:5]!autoprefixer?browsers=last 2 version!sass?outputStyle=expanded&sourceMap` },
      { test: /\.css$/, loader: `style!css?root=${paths.static}&sourceMap&importLoaders=2&localIdentName=[local]___[hash:base64:5]` },
      { test: /\.sass$/, loader: `style!css?root=${paths.static}&sourceMap&importLoaders=2&localIdentName=[local]___[hash:base64:5]!autoprefixer?browsers=last 2 version!sass?outputStyle=expanded&sourceMap&indentedSyntax` },
      { test: /\.woff(\?v=\d+\.\d+\.\d+)?$/, loader: 'file?limit=10000&mimetype=application/font-woff&name=assets/fonts/[name]-[hash].[ext]' },
      { test: /\.woff2(\?v=\d+\.\d+\.\d+)?$/, loader: 'file?limit=10000&mimetype=application/font-woff&name=assets/fonts/[name]-[hash].[ext]' },
      { test: /\.ttf(\?v=\d+\.\d+\.\d+)?$/, loader: 'file?limit=10000&mimetype=application/octet-stream&name=assets/fonts/[name]-[hash].[ext]' },
      { test: /\.eot(\?v=\d+\.\d+\.\d+)?$/, loader: 'file?name=assets/fonts/[name]-[hash].[ext]' },
      { test: /\.svg(\?v=\d+\.\d+\.\d+)?$/, loader: 'file?limit=10000&mimetype=image/svg+xml&name=assets/images/[name]-[hash].[ext]' },
      { test: /\.(png|jpg|gif)$/, loader: 'file?name=assets/images/[name]-[hash].[ext]' }
    ]
  },
  resolve: {
    modulesDirectories: ['src', 'node_modules'],
    extensions: ['', '.json', '.js', '.jsx'],
    root: [paths.src, paths.static]
  },
  plugins: [
    new ExtractTextPlugin('assets/stylesheets/[name]-[chunkhash].css', { allChunks: true })
  ]
};
``

but still, no errors and bootstrap isn't included, is there anything else I need to do to include it?

In the css guide it says just to require it in `config.js``

Hi alex88, did you manage to get this to work?

Hi @hirviid, unfortunately nope, I haven't :(

same issue.  I'm specifically trying to get the javascript to load.  have you had any luck here?

For anyone that comes back to this later, I've got it working by:

Add bootstrap-loader as an entry point to Storybook's webpack.config.js
Import it in config.js as @alex88 did.

Full webpack.config.js (Mostly just the CSS loaders from React Redux Starter Kit):
const path = require('path');

const BASE_CSS_LOADER = 'css?sourceMap&-minimize';

module.exports = {
  module: {
    entry: {
      app: ['bootstrap-loader']
    },
    loaders: [
      {
        test: /\.scss$/,
        loaders: [
          'style',
          BASE_CSS_LOADER,
          'postcss',
          'sass?sourceMap'
        ]
      },
      {
        test: /\.css?$/,
        loaders: [
          'style',
          BASE_CSS_LOADER,
          'postcss'
        ],
        include: path.resolve(__dirname, '../')
      }
    ]
  }
}

And then in storybook/config.js:
import 'bootstrap-loader';

Hi all, thanks for the solution.
Unfortunately it fails for me. I'm getting webpack errors for file extention such as "ttf", "svg", "woff"...
I tried to add the following loader to my webpack config file:
loaders: [
... other loaders
{
    test: /\.(eot|woff|woff2|ttf|svg|png|jpg)$/,
    loader: 'url-loader?limit=30000&name=[name]-[hash].[ext]'
}

but after this none of my stories loads. Any idea?
Thanks

I manage to isolate the issue but I have no idea why this is not working.
My config files is  the following:
import { configure } from '@kadira/storybook';
import { setStubbingMode } from 'react-komposer';
import 'bootstrap-loader';

// Enable react-komposer stubbing.
// See: https://github.com/kadirahq/react-komposer#stubbing
setStubbingMode(true);

function loadStories() {
    require('../client/modules/core/components/.stories');
    require('../client/modules/noises/components/.stories');
    require('../client/modules/users/components/.stories');
    // require as many as stories you need.
}

configure(loadStories, module);

my webpack.config.js is like:
const path = require('path');

const BASE_CSS_LOADER = 'css?sourceMap&-minimize';

module.exports = {
    module: {
        entry: {
            app: ['bootstrap-loader']
        },
        loaders: [
            {
                test: /\.scss$/,
                loaders: [
                    'style',
                    BASE_CSS_LOADER,
                    'postcss',
                    'sass?sourceMap'
                ]
            },
            {
                test: /\.css?$/,
                loaders: [
                    'style',
                    BASE_CSS_LOADER,
                    'postcss'
                ],
                include: path.resolve(__dirname, '../')
            },
            {
                test   : /\.(ttf|eot|svg|woff(2)?)(\?[a-z0-9=&.]+)?$/,
                loader : 'file-loader'
            }
        ]
    }
}

when I start sorybook I do not see any story loaded on the storybook.
But If I remove the import 'bootstrap-loader' from the config they show up.
It is like the import is preventing the stories to be loaded...
After Investigating a bit I saw that when using import bootstrap-loader it also requires JQuery.
I'm getting the following error.
Uncaught ReferenceError: jQuery is not defined
I'm now looking for a solution for this.

Had the same issue but adding the following loader solved the issue with jQuery for me:
{
  test: /bootstrap-sass(\\|\/)assets(\\|\/)javascripts(\\|\/)/,
  loader: 'imports?jQuery=jquery'
}

You also need to install the imports-loader package.

Hey gkaran, thanks for the solution. It did the trick for me. :)

I'm try to add bootstrap-loader into storybook (React 16, storybook 3.1.9).
I have 'compile' solutions above, but I get errors for files eot, woff2, woff, ttf, svg
my config
import { configure } from '@storybook/react';

import 'bootstrap-loader';

function loadStories() {
  require('../stories');
}

configure(loadStories, module);

webpack
const path = require('path');

const BASE_CSS_LOADER = 'css?sourceMap&-minimize';

module.exports = {
  module: {
    entry: {
      app: ['bootstrap-loader']
    },
    loaders: [
      {
        test: /\.scss$/,
        loaders: [
          'style',
          BASE_CSS_LOADER,
          'postcss',
          'sass?sourceMap'
        ]
      },
      {
        test: /\.css?$/,
        loaders: [
          'style',
          BASE_CSS_LOADER,
          'postcss'
        ],
        include: path.resolve(__dirname, '../')
      },
      {
        test: /\.woff(2)?(\?v=[0-9]\.[0-9]\.[0-9])?$/,
        loader: 'url-loader?limit=10000&mimetype=application/font-woff'
      },
      {
        test: /\.(ttf|eot|svg)(\?v=[0-9]\.[0-9]\.[0-9])?$/,
        loader: 'file-loader'
      },
      {
        test   : /\.(ttf|eot|svg|woff(2)?)(\?[a-z0-9=&.]+)?$/,
        loader : 'file-loader'
      },
      {
        test: /bootstrap-sass(\\|\/)assets(\\|\/)javascripts(\\|\/)/,
        loader: 'imports?jQuery=jquery'
      }
    ]
  }
};

so what I could miss/mistake?

@ndelangen , this way?
    rules: [
      {
        test: /\.scss$/,
        rules: [
          'style',
          BASE_CSS_LOADER,
          'postcss',
          'sass?sourceMap'
        ]
      },
      ...
      {
        test: /\.(ttf|eot|svg|woff(2)?)(\?[a-z0-9=&.]+)?$/,
        rules: 'file-loader'
      },
      {
        test: /bootstrap-sass(\\|\/)assets(\\|\/)javascripts(\\|\/)/,
        rules: 'imports?jQuery=jquery'
      }
    ]

Check out the webpack 1 to webpack 2 migration.
https://webpack.js.org/guides/migrating/
the queries (?) and options (!) should be split out,
the property you set on a rule-object is use:
https://webpack.js.org/guides/migrating/#module-loaders-is-now-module-rules
Basicly, you webpack config is a webpack 1. Which storybook does not support anymore.

Could somebody help with properly webpack.config.js for Webpack 3?

I think such a question would be best asked on https://stackoverflow.com where there are more users with webpack knowledge.

Crikey!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.0.0-rc.0 containing PR #21491 that references this issue. Upgrade today to the @next NPM tag to try it out!
npx sb@next upgrade --prerelease


Visualization should support adding non-linearization related events

Porcupine visualization is a great tool to view history of operations done in model. However it only graphs event history outputted from linearization.
In the real system there might be events that are not directly  part of model of linearization, still they might have a influence of correctness of the system. For example we might want to test database like etcd correctness under different types of disruptions, like process kill. Process kill event is not directly part of linearization, however it would be really useful to be able to show the event in the visualization.
Would be great to have a method linearizationInfo.AddEvent(start, end int, name string), that allows to additional block that will be showed on the visualization. Additional recommendation would be to make linearizationInfo public struct. Having a public function returning private struct is a antipattern in Go.
As a workaround, it is possible to add this event as no-op operation to model. This however this will have negative impact on performance.

Sounds useful! Would you be interested in submitting a PR for this?On Jan 21, 2023, at 5:48 AM, Marek Siarkowicz @.***> wrote:
Porcupine visualization is a great tool to view history of operations done in model. However it only graphs event history outputted from linearization.
In the real system there might be events that are not directly  part of model of linearization, still they might have a influence of correctness of the system. For example we might want to test database like etcd correctness under different types of disruptions, like process kill. Process kill event is not directly part of linearization, however it would be really useful to be able to show the event in the visualization.
Would be great to have a method linearizationInfo.AddEvent(start, end int, name string), that allows to additional block that will be showed on the visualization. Additional recommendation would be to make linearizationInfo public struct. Having a public function returning private struct is a antipattern in Go.
As a workaround, it is possible to add this event as no-op operation to model. This however this will have negative impact on performance.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


PHP4-style private properties

Why does 2.x still has PHP4-style properties starting with an underscore?
They are not even all private!
Please advise.

$_wp_using_ext_object_cache is a core thing.

Hey @szepeviktor

Why does 2.x still has PHP4-style properties starting with an underscore?

We will fix this as a part of https://github.com/timber/timber/pull/2332. The WordPress Coding Standards don’t allow variables starting with an underscore anyway, so we won’t need to add a special check for that.


Failing to serialize flatten

Maybe an user error, does onnx have an alternative to flatten? In any case, the following code errors on
Flux version = "0.11.4"
ONNXmutable version = "0.1.0"
using Flux
using ONNXmutable

model = Chain(
    Conv((5,), 54 => 10, relu; stride=1),
    Conv((3,), 10 => 3, relu; stride=1),
    Conv((3,), 3 => 1, relu; stride=1),
    flatten,
    Dense(23, 15, relu),
    Dense(15, 2),
    softmax
)

model(rand(31, 54, 1))
onnx("model.onnx", model)

Gives
ERROR: LoadError: MethodError: no method matching flatten(::ONNXmutable.ProtoProbe{String,ONNXmutable.var"#268#269"{typeof(ONNXmutable.genname),Set{String}},ONNXmutable.BaseOnnx.GraphProto,Tuple{Missing,Int64,Missing}})

Thanks for the report.
Not a user error at all, its just Flux who is a bit too picky about what types flatten accepts. Will submit a fix asap.

Thanks for the report.
Not a user error at all, its just Flux who is a bit too picky about what types flatten accepts. Will submit a fix asap.


About performing adversarial training with advprop

Hi, Yucheng,
Thanks for your nice implementations of advprop. I have a question about performing adversarial training with advprop. In standard training, the clean data pass the main BNs and the generated adversarial data pass the auxiliary BNs. However, if we perform adversarial training, only the adversarial data will be used. So how can we perform adversarial training with advprop?

If there is any other questions, feel free to ask it.


Needs to be migrated to AndroidX.

/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/java/VisionProcessorBase.java:18: error: package android.support.annotation does not exist
import android.support.annotation.NonNull;
^
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/java/barcodescanning/BarcodeScanningProcessor.java:16: error: package android.support.annotation does not exist
import android.support.annotation.NonNull;
^
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/common/CameraSource.java:25: error: package android.support.annotation does not exist
import android.support.annotation.Nullable;
^
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/common/CameraSource.java:26: error: package android.support.annotation does not exist
import android.support.annotation.RequiresPermission;
^
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/FastQrReaderViewPlugin.java:18: error: package android.support.annotation does not exist
import android.support.annotation.NonNull;
^
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/FastQrReaderViewPlugin.java:19: error: package android.support.annotation does not exist
import android.support.annotation.Nullable;
^
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/java/VisionProcessorBase.java:133: error: cannot find symbol
@NonNull T results,
^
symbol:   class NonNull
location: class VisionProcessorBase
where T is a type-variable:
T extends Object declared in class VisionProcessorBase
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/java/VisionProcessorBase.java:134: error: cannot find symbol
@NonNull FrameMetadata frameMetadata);//,
^
symbol:   class NonNull
location: class VisionProcessorBase
where T is a type-variable:
T extends Object declared in class VisionProcessorBase
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/java/VisionProcessorBase.java:137: error: cannot find symbol
protected abstract void onFailure(@NonNull Exception e);
^
symbol:   class NonNull
location: class VisionProcessorBase
where T is a type-variable:
T extends Object declared in class VisionProcessorBase
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/java/barcodescanning/BarcodeScanningProcessor.java:78: error: cannot find symbol
@NonNull List barcodes,
^
symbol:   class NonNull
location: class BarcodeScanningProcessor
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/java/barcodescanning/BarcodeScanningProcessor.java:79: error: cannot find symbol
@NonNull FrameMetadata frameMetadata) { //,
^
symbol:   class NonNull
location: class BarcodeScanningProcessor
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/java/barcodescanning/BarcodeScanningProcessor.java:93: error: cannot find symbol
protected void onFailure(@NonNull Exception e) {
^
symbol:   class NonNull
location: class BarcodeScanningProcessor
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/common/CameraSource.java:159: error: cannot find symbol
@RequiresPermission(Manifest.permission.CAMERA)
^
symbol:   class RequiresPermission
location: class CameraSource
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/common/CameraSource.java:186: error: cannot find symbol
@RequiresPermission(Manifest.permission.CAMERA)
^
symbol:   class RequiresPermission
location: class CameraSource
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/common/CameraSource.java:402: error: cannot find symbol
@Nullable Camera.Size pictureSize) {
^
symbol:   class Nullable
location: class SizePair
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/common/CameraSource.java:413: error: cannot find symbol
@Nullable
^
symbol:   class Nullable
location: class SizePair
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/FastQrReaderViewPlugin.java:263: error: cannot find symbol
void startScanning(@NonNull Result result) {
^
symbol:   class NonNull
location: class FastQrReaderViewPlugin
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/FastQrReaderViewPlugin.java:329: error: cannot find symbol
void stopScanning(@NonNull Result result) {
^
symbol:   class NonNull
location: class FastQrReaderViewPlugin
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/FastQrReaderViewPlugin.java:392: error: cannot find symbol
QrReader(final String cameraName, final String resolutionPreset, final ArrayList formats, @NonNull final Result result) {
^
symbol:   class NonNull
location: class FastQrReaderViewPlugin.QrReader
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/FastQrReaderViewPlugin.java:563: error: cannot find symbol
private void open(@Nullable final Result result) {
^
symbol:   class Nullable
location: class FastQrReaderViewPlugin.QrReader
/Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/java/VisionProcessorBase.java:116: error: cannot find symbol
public void onFailure(@NonNull Exception e) {
^
symbol: class NonNull
Note: /Users/philipneves/flutter/.pub-cache/hosted/pub.dartlang.org/fast_qr_reader_view-0.1.5/android/src/main/java/co/apperto/fastqrreaderview/common/CameraSource.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
21 errors
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':fast_qr_reader_view:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 4s
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                         5.0s

The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.

Gradle task assembleDebug failed with exit code 1

I would appreciate this to.

Have you tried using this library from the git repo instead of the pub?

When I do this
  fast_qr_reader_view:
     git:
      url: git://github.com/facundomedica/fast_qr_reader_view.git

I get this

* What went wrong:
Could not determine the dependencies of task ':firebase_core:compileReleaseAidl'.
> Failed to notify dependency resolution listener.
   > The library com.google.android.gms:play-services-measurement-api is being requested by various other libraries at [[16.0.3,16.0.3]], but resolves to 16.0.2. Disable the plugin and check your dependencies tree using
./gradlew :app:dependencies.
   > The library com.google.firebase:firebase-analytics is being requested by various other libraries at [[16.0.5,16.0.5]], but resolves to 16.0.4. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.

I tried with pub/git/local importing to run the App, resulted the same error @pneves001 first experienced.

I finally got it working under AndroidX ... I'm not guaranteeing that this will work for you or that you need to do all of these steps, but here's what I did...
1. In your pubspec.yaml file, include two things
  fast_qr_reader_view:
    git:
      url: git://github.com/facundomedica/fast_qr_reader_view.git

.... and also ...
 permission_handler: 2.2.0
Note: on the permission_handler, I didn't use 3.0.0 or ^2.0.0 because there were dependency issues with geolocator.
2. As in the documentation for fast_qr_reader_view, increase the minSdkVersion to 21 in your build.gradle file located in the ../android/app folder.
3. In the documentation for fast_qr_reader_view, it says "Add Firebase to your project following this step (only that step, not the entire guide).", with "this step" pointing to Step 6, "Create a Firebase Project". In fact, you need to do both Step 6 AND Step 7 (the documentation for fast_qr_reader_view should be updated to say do both steps).  Start with this step and then do this step.
4. One thing that threw me off (as primarily an iOS developer) is that there are two build.gradle files. One at the ../android level and the other at the ../android/app level.  At the ../android level add
classpath 'com.google.gms:google-services:3.2.1'
Make sure you use 3.2.1, it is the latest that is compatible with Flutter. There are later releases (4.0 and 4.2, I think), but they are not compatible with Flutter.
At the ../android/app level, modify the build.gradle file by ensuring the minSdkVersion is 21 or greater and also by adding this as the last line in the file.
apply plugin: 'com.google.gms.google-services'
also, don't forget... in step 7 of the Add Firebase instructions, you have to download the google-services.json file that has been generated with your specific project details and include it in the ../android/app folder.
5. With these changes above, it might be enough to get it working... however, I also added permissions for the camera in the various AndroidManifest.xml files for main, profile and debug
<uses-permission android:name="android.permission.CAMERA" />
Then in my code, near to where the app is launched, I added:
import 'package:permission_handler/permission_handler.dart';
and
await PermissionHandler().requestPermissions([PermissionGroup.camera]);
That should do it!!!
There are a lot of steps, and more than a few places where you could go wrong. For me what was causing me the most problems is I didn't notice that there were two separate build.gradle files that needed to be modified... the first time around, I put all of the changes in the build.gradle file at ../android instead of also putting the necessary changes in the build.gradle file at ../android/app.
The good news is it now works fine. For me, there are two areas I'm still a bit concerned about. When it executes it produces a lot of errors in the debug console even though it is working fine. The other problem I have is that the camera is fixed on "far focus", making it nearly impossible to read complex QR codes with a lot of detail by moving them closer to the lens.
I hope this helps. There aren't many good QR readers out there, and this one seems to be the best in my opinion. Hopefully this will stabilize over the next few releases and / or the documentation will be updated to make it more clear how to get this working under AndroidX.
Good luck!  :-)
JW
Just for additional context, I'm running on a fairly new Nokia phone (6.1) with Android 1.  I recently had to downgrade my Flutter and Dart plugins, along with VS Code to the January 2019 versions because hot reload seems to be broken in the Feb release.  I'm working on a Mac.

I still get this after following the steps
* What went wrong:
Could not determine the dependencies of task ':fast_qr_reader_view:compileDebugAidl'.
> Failed to notify dependency resolution listener.
   > The library com.google.android.gms:play-services-measurement-api is being requested by various other libraries at [[16.3.0,16.3.0]], but resolves to 16.0.3. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.
   > The library com.google.firebase:firebase-analytics is being requested by various other libraries at [[16.3.0,16.3.0]], but resolves to 16.0.5. Disable the plugin and check your dependencies tree using ./gradlew :app:dependencies.

I tried with AndroidX and works flawlessly (only 1st time crash when dont have permission yet)


testing "upgrade 5 refactor"

TODO:
need some small change, so batch prover can load chunk_halo2.protocol and chunk_sp1.protocol
need to manually copy vk_batch_agg.vkey
the save/load must be broken.  After it generated batch proof (but panics due to lack of "vk_batch_agg.vkey"), i rebooted it with OUTPUT_DIR=XXX, but it is proving chunk again.. chunk proof loading must be broken.
need to adjust batch circuit size:
index be4fea7..6b6b86a 100644
--- a/integration/configs/layer3.config
+++ b/integration/configs/layer3.config
@@ -2,7 +2,7 @@
   "strategy": "Simple",
   "degree": 21,
   "num_advice": [
-    63
+    85
   ],
   "num_lookup_advice": [
     8

panic in last step
2024-11-07T12:33:31.001545284+00:00 DEBUG prover::utils - read env var SCROLL_PROVER_DUMP_YUL, result: true
thread 'test_e2e_prove_verify' panicked at integration/src/prove.rs:95:10:
called `Result::unwrap()` on an `Err` value: Serde(Error("can only flatten structs and maps (got unit struct)", line: 0, column: 0))
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: integration::prove::prove_and_verify_bundle
   4: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
test test_e2e_prove_verify ... FAILED


Enable Okta authentication via OpenID

The basics of "auth with Okta" are straightforward.  The challenge here will be weaving it into the current auth flow, which is quite complex.
In a perfect world, we could add Okta simply as another auth provider at the beginning of the flow:

Unfortunately, Okta partitions auth endpoints by customer, so there is no global auth endpoint.  Instead, you need to know the domain by customer.
Options:

Global rule by email address
a. For example, first ask for email.  If the email address ends with<EMAIL_ADDRESS>then redirect to the Okta auth page configured for "example.com".  This is what Box does.
b. This is probably the simplest and least intrusive option.
c. Important distinction between "global user" and "project user".  By default, we configure most users as "global users", meaning that they can be members of multiple projects.  For open patient registration, we use "project user", which means that the user account is isolated to the project.  We should only apply this global Okta rule to global users, and not project users.
Ask for project at top of sign-in
a. For example, ask for a project ID or a project alias as the first field in the sign-in page. This is what the AWS console does.
b. This would simplify things for Medplum engineering, but it's a pretty bad experience for users, because now they need to remember another piece of information.  Even if we make it easy to use friendly alias names like "foo", it will be confusing and will probably increase support tickets.

This is a hard one - as there aren't really any good options that you need to know a lot alot about a user in order to choose the right authentication method - but we are authenticating them because we don't know who they are.
Both options are viable, but there are drawbacks to each.  Our multi-project UI is another good experience that would be hampered by this as well.
It does seem like Option 1 is preferable to Option 2 as we it is least intrusive, and represents the spirit of what customers want.
We need to improve the error message for developers who are using the register and sign in react components to ensure that they are passing in project Ids to streamline the login for end users.
Question: this will force Okta login for customers with linked emails if they are developing on localhost right?  Will Okta allow that?

Question: this will force Okta login for customers with linked emails if they are developing on localhost right? Will Okta allow that?

Oo.  Good catch.  Not only localhost, but all separate front-ends.

Just chiming in here, it does seem like option 1 is preferrable if we can make it work. We have a lot of name collisions for Project names, so creating some kind of alias system for them would be difficult at a practical level as well.

Closing this out with related PRs as follows:
https://github.com/medplum/medplum/pull/1394


0.9.0 release fails to build AmazonLinux2 drivers

Description of Bug
We tested out 0.9.0 today and noticed a new issue with AmazonLinux2 kernel drivers (specifically for libs version 3aa7a83bf7b9e6229a3824e3fd1f4452d1e95cb4). Here's some output from our automation that utilizes driverkit:
[ 2022-06-15 16:31:55,897 ] INFO - driverkit.py:137 - Does not exist in bucket! Building: [ scwx_amzn_5.4.68-34.125.amzn2.x86_64_1.ko ]
INFO driver building, it will take a few seconds   processor=docker
FATA exiting                                       error="Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub"

It seems the x86_64 binary is built with CGO_ENABLED=0.

Steps to Reproduce
Can be reproduced with the following using the amd64 release from the releases page:

Download 0.9.0 release from release page: https://github.com/falcosecurity/driverkit/releases/download/v0.9.0/driverkit_0.9.0_linux_amd64.tar.gz
Un-tar to $(pwd)
Spin up linux container (if not on linux):

docker run -it -v $(pwd):/test ubuntu:latest

Run a build for Amazon Linux 2 (with libs version 3aa7a83bf7b9e6229a3824e3fd1f4452d1e95cb4):

root@ab26a4643071:/test# ./driverkit docker --output-module ./test-amazonlinux2.ko --timeout 520 --target amazonlinux2 --kernelrelease 5.4.186-102.354.amzn2.x86_64 --driverversion=3aa7a83bf7b9e6229a3824e3fd1f4452d1e95cb4 --kernelversion 1
INFO driver building, it will take a few seconds   processor=docker
FATA exiting                                       error="Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub"

Additional Context
Looking at previous MRs... It seems there was a recent change to set CGO_ENABLED to 0: https://github.com/falcosecurity/driverkit/pull/157/files
I wonder if setting CGO_ENABLED=0 only for arm builds would solve the issue? Maybe make the Makefile detect if arm, then CGO_ENABLED=0?
I tried adding some logic to the Makefile to detect arm vs. x86, and it does get x86 building again... But the mattn/go-sqlite3 lib requires CGO_ENABLED=1 to run.

Thank you, I come late to the party but I confirm that Amazon stores info in an SQLite DB that the AL2 builder needs to download and query...
Therefore PR #157 breaks AL2 builders.

/priority high

@leodido: The label(s) priority/high cannot be applied, because the repository doesn't have them.

In response to this:

/priority high

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Update real-time-marketing-outbound-text-messaging.md

Improvements based on customer feedback for vague description on current ACS status and updates to indicate the 2-way SMS flow is now released.

@alfergus Please review


Questions about the vanilla-js version

I'm planning to migrate away from jQuery and vanilla-js version of rowGrid seems to be the way to go. @brunjo can you please confirm whether (functionally) these versions are equivalent? Also, I'm suspecting that vanilla-js version would need a separate npm entry to be available from npm, correct?

Yes, the two variations are nearly the same. The only difference is that the vanilla JS version doesn't support IE8.
I will publish the vanilla js version on npm in the next days.

The vanilla JavaScript version moved now to its own repository: https://github.com/brunjo/rowGrid. Now both versions (jQuery and vanilla JS) support npm and bower.

Great, thanks!


Add linters to CI workflow

Codecov Report

Merging #28 (07cb3be) into main (a865073) will decrease coverage by 0.24%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #28      +/-   ##
==========================================
- Coverage   43.83%   43.58%   -0.25%
==========================================
  Files          13       13
  Lines         381      530     +149
==========================================
+ Hits          167      231      +64
- Misses        202      286      +84
- Partials       12       13       +1

Impacted Files
Coverage Δ

pkg/pending_review/client.go
50.00% <0.00%> (-5.56%)
:arrow_down:

pkg/pending_review/repository.go
41.46% <0.00%> (-3.70%)
:arrow_down:

internal/stats/counts.go
93.93% <0.00%> (-1.72%)
:arrow_down:

internal/duration/moving_average.go
76.92% <0.00%> (-0.86%)
:arrow_down:

internal/commit.go
15.09% <0.00%> (-0.30%)
:arrow_down:

internal/format/reviews.go
85.52% <0.00%> (-0.19%)
:arrow_down:

internal/stats/stats.go
0.00% <0.00%> (ø)

internal/format/under_way.go
0.00% <0.00%> (ø)

internal/duration/duration.go
100.00% <0.00%> (ø)

internal/format/statistics.go
0.00% <0.00%> (ø)

... and 3 more

Continue to review full report at Codecov.

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


Sprinkler Tracking

I would like to propose an idea.
Would it be possible to include the entity of the respective sprinklers for each zone? This way, the integration could track the seconds each zone is irrigated and update the bucket accordingly. This could avoid the need to reset the bucket and also account for any manual activations of individual zones.

that's a great idea! Very interesting, let me see if I understand what you mean:

add optional entity for each zone
if entity is provided, automatically update bucket to reflect changes based on throughput * activation time. this will cover then for automatic irrigation as part of the normal behavior as well as manual activations of the entity.

did I get that right?

Yes, that's exactly what I mean! By adding an optional entity for each zone and updating the bucket based on throughput and activation duration, the integration would become more accurate and efficient. The bucket would be adjusted according to the calculation of millimeters of water replenished by the irrigation. This would account for both automatic and manual irrigation, making the system more reliable.Thank you for considering this idea. As I'm not familiar with the development of integrations, I wasn't sure if this was feasible


The site is to narrow

(Except on the front page) We're only using about a third of the screen. We need to widen that.

Change class="col-md-6 col-md-offset-3" to class="col-md-10 col-md-offset-1" in https://github.com/idmontie/ChibiCritters/blob/4d5c90c3b4c4dcb8ffc4224ac9fc9a178dc4e86e/wordpress/wp-content/themes/chibicritters/content.php#L14.
That should be the only file that needs changing.

Yeah I changed it on the blog post section. I'll get to the rest of the site soon.


✨ Add more logs to the Application Insights

Cc: @adamcogan @pierssinclairssw @GordonBeeming @jimmidier

To myself,
Pain

The query "Who is in Brisbane office now" was not working before and we don't know when that happened. We need to add more logs to the Application Insights.
Suggested Solution

Add Application Insights to:

SophieBot to record the query result
People API to record the UniFi calls

Tasks

[x] Investigate
[x] implement

Definition of Done

[ ] All tasks are updated and closed
[ ] No high priority defects/bugs are on that user story
[ ] Code reviewed by one other team member (e.g. Checked by Bill)
[ ] All acceptance criteria have been met
[ ] Deployed to Dev
[ ] (If implemented) Pass automated UI testing
[ ] (If not implemented above) Do a manual test on all supported commands (at least one for each LUIS intent) against Dev
[ ] Complex code is documented (removing technical debt)
[ ] Deployed to Production
[ ] Add description about the changes for the PBI
[ ] Tick off the definition of done tasks in the PBI
[ ] (Optional) A Done Video, particularly for PBI with multiple stages

Thanks!

People API to record the UniFi calls

Telemetry in People API UniFi calls is already implemented

Figure: Existing logs in Azure App Insights


[Feature Request] Custom Help hide absent cog names

Ability to refresh everything. Currently, when you unload a cog, it still stays on the help menu on the main bit. This would also remove those cogs that are not loaded from the help menu making it look less crowded and will no longer show cogs that are unloaded.

This is one such major bug where no one complained so I just assumed ppl didn't care.
The problem is Red doesn't tell you when a cog is unloaded or uninstalled. So the cog still remains in the cache unfortunately.
This only affects the "main" feature of a specific theme as shown in screenshot. The cog help won't be shown if u go into the category.
A cog unload listener is planned, will fix sooner or later.
Meanwhile a hotfix is manually removing the cog using [p]chelp remove cog CogName.

Resolved this in the dpy2 branch, will be imposed whenever red 3.5 version comes out.


[Not really an issue] - Extraneous line

Hi Court,
Thanks for the article, I am at the moment following the tutorial and came across this line in your source code.
https://github.com/schuettc/cdk-private-rds-with-lambda/blob/f0e0b4a5d498ededcb72c27a7ad1267c5d6f5b30/src/rds.ts#L38C31-L38C46
I believe it is not doing anything as allowInternally is not actually called.

Thanks!  Removed here: https://github.com/schuettc/cdk-private-rds-with-lambda/commit/d894614add4eaca913aa02b393e159054b942ce1


[BUG]azure-storage: High Lock Contention for concurrent Blob Uploads at scale

Describe the bug
We are using Azure java SDK storage APIs to upload large number of files (blobs) to Azure Blob Storage. To do this, we are creating multiple BlobClient instances using a single BlobContainerClient which is being cached and is a shared resource. Each thread creates its own BlobClient for each blob it needs to upload. However, we have observed high lock contention and performance degradation as the number of uploads increases. During load tests when creating the BlobContainerClient using SAS tokens, we observed that there is a high contention at java.util.HashTable.

When trying do the same load tests using connectionString authorization, we observed the contention at java.text.RuleBasedCollator.

These 2 images are taken when we do 2Mn calls to the blob storage when using one single BlobContainerClient and we create 2Mn separate BlobClients to upload each single blob.
Note: We cannot batch upload all the files to the blob storage service as our use case demands that we make separate requests to the blob service.
Exception or Stack Trace
Provided in the JFR screenshots.
To Reproduce
Create a file of random characters of 500 bytes and do separate Blob requests to a specific Blob container where you can use either connectionString authorization or SAS tokens. Create separate BlobClients for each Blob and when making the request, add a random character as your blobName. Submit all these tasks to an executorService where at least 3.5k threads are doing the blob calls.
Code Snippet
// just adding sample code to hammer the blob service with 2Mn requests
BlobContainerClient containerClient = new BlobContainerClientBuilder()
                .containerName(containerName)
                .connectionString(connectionString)
                .httpClient(httpClient) // create a specific one for high throughput
                .buildClient();
ExecutorService executorService = Executors.newFixedThreadPool(numThreads);
for (int i = 0; i < 2_000_000; i++) {
            executorService.submit(() -> {
                String blobName = "blob-" + i + ".txt";
                BlobClient blobClient = containerClient.getBlobClient(blobName);

                String data = getRandomString();
                ByteArrayInputStream dataStream = new ByteArrayInputStream(data.getBytes(StandardCharsets.UTF_8));

                blobClient.upload(BinaryData.fromBytes(data.getBytes()), true); // our usecase demands that we overwrite if the blob name is same by accident
            });
        }
executorService.shutdown();
executorService.awaitTermination(1, TimeUnit.HOURS);

Expected behavior
It is understandable to have intermittent fluctuations in the request call latency to blob service but contention at the sdk level causes the throughput of the number of blobs uploaded to be reduced by a huge amount. Azure documentation says that the throughput that can be handled by storage account is 20k requests per sec but this contention seems to be a bottleneck in reaching this threshold.
Setup:

OS: Linux
IDE: IntelliJ
Library/Libraries: com.azure:azure-storage-blob:12.25.3
Java version: JDK 17

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

Thanks for reporting this @saty101, I was able to validate this concern with a simpler reproduction.
For the SAS token-based usage, this can be reproduced using a thread pool of 5 thousand threads and 20 million new URL(String) calls. In my testing Java Flight Recorder reported over a day worth of lock contention.
For the connection string-based usage, this can be reproduced using a thread pool of 5 thousand, a static Collator.getInstance(Locale.ROOT), and 20 million calls to sort a list of strings. In my testing Java Flight Recorder reported many days worth of lock contention.
I'll look into this further on how the designs of these two code patch can be changed to reduce the amount of locking happening.

Hey @alzimmermsft is there any update regarding this bug?

Hi @saty101, a change was made to azure-core 1.53.0 to circumvent the HashTable lookup during URL creation in UrlBuilder. A change to reduce contention in StorageSharedKeyCredential is only available in a preview release 12.28.0-beta.1, which can be inspected for resolving your issue until it releases GA.

Hey @alzimmermsft I tested my use case with preview release 12.28.0-beta.1 and it definitely showed better performance for large scale PUT operations to the blob storage. Just wondering when can we expect to get this on GA release?

@saty101, there is a GA release, which should include this fix, planned for some time in the middle of November.

This should be available in azure-storage-blob 12.29.0.


Use special double entries in gdextension

Godot version
https://github.com/V-Sekai/godot/commit/35b10e36d919247cf9e7c06892bf1c38ef027b0b
godot-cpp version
https://github.com/godotengine/godot-cpp/tree/fbbf9ec4efd8f1055d00edb8d926eef8ba4c2cce
System information
Macos
Issue description
Godot added a feature for the particular naming of the double extension libraries.
https://github.com/libriscv/godot-sandbox/blob/main/bin/addons/godot_sandbox/bin/godot-riscv.gdextension
godot-cpp-template does not use it. https://github.com/godotengine/godot-cpp-template/blob/main/demo/bin/example.gdextension
godot-cpp-template should use the special syntax. Note that the order of the double vs single matters.

This is half addressed in #55, through the use of env["suffix"] in the naming scheme, which is defined here and (i think) intended for this purpose. The PR does not currently add new entries to the .gdextension file.

I downloaded

from https://github.com/godotengine/godot-cpp-template/actions/runs/11691017198/job/32557244884 doubles build.
godot-cpp-template.zip and it does not build doubles libEXTENSION-NAME.macos.template_debug, I suspect it is overwriting.
Secondly libEXTENSION-NAME.macos.template_debug is missing env["arch"]

Secondly libEXTENSION-NAME.macos.template_debug is missing env["arch"]

That one is actually fixed by #55.


add temp option and memdb with tests

Possible implementation for #516. The main downside is the additional memdb dependency.
There were a few other suggestions in that issue discussion and those may be better.
Need to add docs & update changelog if/before this is merged.

LGTM 👍


Poc: Implement plugin-wise error code to achieve strong encapsulation

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description
AppsmithPluginError enum will have all the common error codes shared by all the plugins.
Each plugin will have its own Error enum e.g. MySQLPluginError that implements an interface AppsmithPluginErrorBaseType. Please note that AppsmithPluginError also implements the AppsmithPluginErrorBaseType interface.

Add a TL;DR when description is extra long (helps content team)

Fixes # (issue)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.
Delete anything that is not important

Manual
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

This PR was raised as part of POC and hence closing it.


Can't set the video player width/height other than fixed pixels, so It doesn't adjust to page/div size.

Hello! I really like the video player but can't seem to set a size to other than pixels.On the video player settings only numbers/pixels are allowed. If I don't set a width or height on playerOptions and rather use CSS to set the player width to lets say 50% it doesn't apply, event with !important.
The Player
        class="video-player-box vjs-16-9"
        v-if="sourceList[0]"
        @ended="onPlayerEnd($event)"
        v-video-player:myVideoPlayer="playerOptions"
      ></div>

These are my settings
  playerOptions: {
        muted: false,
        autoplay: 'play',
        loop: false,
        width: 1000,
        language: 'en',
        playbackRates: [0.7, 1.0, 1.5, 2.0],
        sources: [
          {
            type: 'video/mp4',
            src: "asd"
          }
        ]
      }

My CSS, which the player is ignoring
.video-player-box{
  margin: auto;
  width: 50vw !important;
  align-content: center;
  align-items: center;
  text-align: center;
}

Also why when deployed the play button displays on the top left of the player, even on videojs official homepage?

Solved, I was using it inside a VUE component, which styling is by default scoped. But since the videjs styling is inserted on the head, it wasn't being affected. Removing the scoped solved the problem. This issue should be closed.


add racobit_radar and build passed.

add racobit_radar_drivers, build passed

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


Avoid call sync method in async rest API for force delete subscription

Motivation
Same to  #13666
Modifications

Change sync method to async.

Verifying this change

[x] Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: ( no )
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

[x] no-need-doc

@codelipenghui
PTAL :)

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

@codelipenghui please don't add labels to cherry pick this kind of patches to branch 2.8 and 2.9.
We should cherry pick only critical fixes

@mattisonchao I have left a few comments, PTAL.

@mattisonchao I have left a few comments, PTAL.

I will fix it ASAP.

/pulsarbot run-failure-checks


Chrome 54+ supports SVGElement.dataset

See https://bugs.chromium.org/p/chromium/issues/detail?id=636108
and https://www.chromestatus.com/feature/5727911176830976

Thanks!


font_family no longer changes terminal font

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
Setting font_family no longer changes the terminal font, it falls back to the buffer_font
Environment
Zed: v0.111.6 (stable)
OS: macOS 14.0.0
Memory: 32 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
1: Monaspace Neon working in buffer, no font_family set.

2: Change buffer font to Hack Nerd Font Mono, see both terminal and buffer change:

3: Switch buffer_font_family to Monaspace and font_family to Hack Nerd Font Mono, note that the terminal also changes despite the new setting:

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
Zed.log

I believe you have to set the terminal explicitly like so:
"terminal": {
        "font_family": "FiraCode Nerd Font",
        "font_size": 16
    }

See: https://docs.zed.dev/configuration/configuring-zed#terminal

I believe you have to set it to the terminal explicitly like so:

That did it, thanks! That's easy to miss if you're just searching for font in the docs rather than reading them fully.


support for structs

Raising the PR again in an upstream branch to get rid of build permission issues, made changes as per the  review comments
https://github.com/CommBank/beeswax/pull/7

@rowandavies  this is based on a previous PR that was raised quite a while ago. It took some time for me to understand that I need to push it to upstream branch to properly invoke the travis build. I have made some changes based a few of the review comments. Could you please look at it?

@toddmowen thanks for the review. Il make sure that it works for list of structs. I will have to look at how we can have a separate behaviour for Scrooge and humbug. Can we have a design discussion? Should beeswax have a tight coupling with humbug (and its inherent restrictions)?

@toddmowen I added support for list/map of structs and their tests.
On Separting out Humbug and Scrooge behaviour
We can distinguish Humbug and Scrooge by checking if the runTimeClass contains an interface HumbugThriftStruct. I can do this. However, we should be aware that the whole project is currently developed and tested using com.twitter.scrooge.ThriftStruct for  the features common to humbug and Scrooge (asserting the exclusive features of Scrooge to exceptions). To prove this fact, we could remove the humbug plugins from the build, and all the tests still passed.

@toddmowen
Also, here are few key points that I consider to be the reasons for why we don't need explicit error messages for humbug thrifts:

A humbug thrift class extends com.twitter.scrooge.ThriftStruct with HumbugThriftStruct. Beeswax handles everything with just  com.twitter.scrooge.ThriftStruct and doesn't care about how  _ <:ThriftStruct is created.
As of now, it is impossible for anyone to pass a  ThriftStruct using humbug plugin to beeswax, as such a ThriftStruct can't exist.
If by any chance, if someone creates a complex thrift struct using humbug plugin in future, then it should be treated in the same way as it is now in beeswax (in this PR).

@afsalthaj In other words, beeswax works with all humbug-generated thrifts. Sure, that's no problem. I misunderstood, thinking you meant there would be some runtime or compile error if using humbug.
I'll finish the review today.


bad encoding on commit page

https://subgroup.org/git/mr_tron/karl/commit/c027a7267e3191b7775e9f0b3d34ac4833ac346c
file webui/triggers.py line 6
But in https://subgroup.org/git/mr_tron/karl/src/c027a7267e3191b7775e9f0b3d34ac4833ac346c/webui/triggers.py - encoding os ok
Looks like utf-8 text showed as cp-1252.

I don`t know that have been changed, but now it work ok.

Good to know! Thanks your confirmation


Version 1 Release

replaces #143
As per the dicussion on #568 we should get pydantic to version 1 then aggressively follow semvar for breaking changes.
However before we release version 1, I want to make any breaking changes that are obviously required now.
So, to do before version 1:

[x] rename Schema to Field? #577
[ ] remove references to validation and use parse instead #578
[ ] decide about load_alias and dump_alias #477 #624 not required for v1.
[x] fix any significant open bugs (see issue tracker / filter by "bug")
[x] need to decide about #508

anything else? no point in spending too long perfecting the library and never getting to v1, but still, let's get anything obviously wrong right now.

some things on #577 and #578 and maybe other issues will require deprecation warnings and a couple of versions before we remove the old behaviour.
I guess we should get all these changes out of the way before we get to version 1.

@tiangolo maybe you have some feedback/input on this?
@gangefors you said "we have considered it [pydantic] really stable" on #568, would the changes above be okay with you? Anything we an do to mitigate the impact?

We are totally fine with the changes. Moving to 1.x we can feel relaxed that there should not be breaking changes when upgrading within the same major version.
I appreciate all the work you do on this project and I'm really happy that you want to take it out of the pre-release phase. Many good python projects never end up with a 1.0 release.

Great. Thanks for tagging me. I agree with all the points.

One extra thing that I wanted to propose was when allowing custom data types (currently with __get_validators__), also support:

__get_json_schema__ (or equivalent): to allow user-defined types to provide their own JSON Schema. E.g. with a class inheriting from MongoDB's ObjectId.
__get_json__ (or equivalent): to allow user-defined types to have their own JSON encoder.

Still, I think that's an extra feature that could go in a minor version bump, but I wanted to share the idea in case you see some compatibility that could be broken by these next changes or that would make sense to try and do it now.

__get_json_schema__ and __get_json__ makes sense to me, please create a new issue. I agree this doesn't need to be done before v1.

Add https://github.com/samuelcolvin/pydantic/issues/579 to the list of TODOs?

Agreed

also #589 if we decide to do it.

Question: which is better;

One big release with many breaking changes, or
Multiple releases each with a few or one breaking change

?

will be harder work and involve more conflicts, I guess we would need a v1 branch which breaking changes are merged into. But I guess it would be easier for most people.

@tiangolo @dmontagu @jasonkuhrt @gangefors

If making them non-backwards-compatible, I guess 1. To avoid scattered mutually exclusive/incompatible versions.
If keeping them backwards-compatible for a while (so, no mutually exclusive scattered versions), then 2 will probably be easier to manage. I imagine having a v1 branch might lead to code diverging and needing to implement fixes/changes in both branches, etc.

some things like new bool behaviour #617 has to be backwards incompatible, so I guess that should go onto a v1 branch and only be released with version 1.
Everything backwards compatible should be included in minor releases with warnings, then the warnings and fallback behaviour removed in v1?

Hmm, right, get it. But I don't think there's much more that is exclusively backwards incompatible, right?
I think it would be ok to release the new bool with the current master, under a minor version bump.
I would like/ask to have the backward compatibility (for the things that we can, like __validator__ and Schema) for a couple of versions after-v1 with warnings, and then drop it after some minor versions after v1. That would give a bit of margin for people to notice the change and upgrade.
But if we can have, e.g. Schema() still working after v1 with a warning while the new Field()/field() is already supported (and used/documented by default), I think it would be OK to just do it in master.
I guess my main concern is that I think it would be quite cumbersome to handle the 2 branches master and v1. And add features to both, etc.

What else is exclusively backwards incompatible apart from the strict bool? What am I missing?

What else is exclusively backwards incompatible apart from the strict bool? What am I missing?

sound about right to me, I don't think you're missing anything.
Otherwise all sounds good to me.

I agree with the conclusion/direction you @samuelcolvin and @tiangolo came to. SGTM

SGTM too.

See #719, pydantic is now effectively on a sprint for version 1.
(Sprint in the sense of not working on anything else except critical bug fixes, not sprint in the sense of necessarily being fast :smiling_imp: :running_man:)

So, to do before version 1:

I would like to see these two fields become default:
class Config(BaseSettings):

  Config:
    env_prefix = ""
    case_insensitive = True

Couple of points:

We can add windows only tests, since CI runs in windows and linux that should work fine, just skipIf.
I'd be entirely up for removing case sensitivity altogether, I can't imagine a situation where you'd ever desire case sensitivity. It was added as an option to avoid a breaking change, but if we think that switch is superfluous, now would be the time to remove it.

I've been thinking about how BaseSettings works, I'll add more general points to #747.
Let's agree there before we move forward here.

I'd be entirely up for removing case sensitivity altogether, I can't imagine a situation where you'd ever desire case sensitivity. It was added as an option to avoid a breaking change, but if we think that switch is superfluous, now would be the time to remove it.

👍

I'm going to try and get a beta release of v1 out before the end of the week (September 20th). I then go on holiday for 10 days which will give others time to try v1 and give feedback/find bugs.
However to do that I need to merge some PRs without waiting for others to review them. I hope that's okay, I see no other approach.

Unfortunately I haven't been able to get a beta for v1 out due to a combination of:

life
@dmontagu's excellent suggestions around from_orm and root validators #811
problems around stripe and SCA at my day job

Sorry.
I also wanted to allow more time for feedback on the features/changes I've implemented recently, in particular I'd love y'all's feedback on:

root validators #817 and an extension to that which improves ORM integration #822
custom JSON encoding/decoding #823
renaming of numerous classes, primarily Schema -> Field

As far as I know (apart from merging the above) the only things remaining to do for v1 are:

better support for env. variables in BaseSettings #721 (will either need to be branched of Schema-2-Field or wait for it to be merged)
a script to build history from changes/ files

I'd love help on either of those, otherwise I'll fix them and release a beta in the week beginning 30th (promise).

I'm sorry I haven't been able to help recently as I wished :disappointed:
Thanks for all this! :tada:

The first beta of version 1 is released :rocket: :fireworks: :tada:. It should be on pypi soon.
Please try it, break it and give feedback. :bug: :broken_heart:
Unless another beta is required, I'll try and release v1 proper in a couple of weeks. :clock1:

Awesome! Thanks for that! :tada: :clap: :rocket: :bowing_man:

@samuelcolvin Any ideas on the timeline here? We are pretty excited about a 1.0, but there are some breaking changes for us and we want to be prepared.

Hopefully very soon, there are already way too many changes since we got to beta, but I really hope they should all make pydantic v1 better once it's released.
Still to do:

[ ] #909 this became a much bigger hassle than I'd hoped
[ ] #913 which I discovered while working on #909
[ ] #523 which hopefully @dmontagu will work on
[ ] #898, just waiting for the docs to be completed by @ashears in #907
[ ] we need a new page for the docs on migrating to v1; part of #862

Once they're all merged, I'll release v1.

DONE :rocket:
https://pydantic-docs.helpmanual.io/
If anyone in the reddit-sphere felt like crowing about the release, that would be great.

That's awesome! Thanks for that. Congrats and great job! :tada: :cake: :rocket:
Also, where is it on Reddit? Didn't see it on r/Python

Yes please, if possible? :see_no_evil:
I did put it on hacker news

Awesome! I'll do it on Reddit!
Also, don't post the link directly to Hacker News, just that it's on https://news.ycombinator.com/newest, otherwise they don't allow to vote it up.


Add configuration option for highlight - service

so that some content is ignored, like described here:
https://github.com/dhlab-basel/Salsah/pull/234#issuecomment-381061783

Hi, I'll do this as my next task, starting on Tuesday. Thank you for your patience!!

Ok :-)
Thanks!

It would also be great if the amount of text could be reduced to the context surrounding the search terms (so the user only sees the highlighted search terms and some context).


bump: bump up notation-go v1.1.1 and other dependencies

Signed-off-by: Junjie Gao<EMAIL_ADDRESS>

We should also update the dependencies in test/e2e. They are test/e2e/go.mod and test/e2e/plugin/go.mod.

Updated.

LGTM, but waiting for the DCO status.


Ikigai cambio de dominio

Source information
Ikigai 1.4.10
Source language
Español
Source new URL
https://ikigaimangas.com/
Other details
No se cambio el dominio de ikigai
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

Arreglado


Overhaul branches

Use main instead of master
Removal of the "develop" branch. Setup features and merge directly into main?

@acalatrava  any thoughts?

Moved develop to main..
getting rid of master branch... main will be tagged with versions


changes not applying to print jobs?

We've used Stylebot to auto-format text entries within a web-based POS system, and it looks fine within the program, but when printing the text the changes are not applying...Is there a way to fix this or have I done something incorrectly?

desperate for any advice on this...anyone have insight they can share?? Thank you!


What does the mod do?
improves overall game performance by decreasing gui and screens framerate
Is this mod on Modrinth?
Yes
Link to the mod
https://modrinth.com/mod/exordium
Images
No response

As much as this mod improves performance, it could cause issues with some mods and their GUI's so I wouldn't recommend adding this mod.

Closed as it was marked as "won't add".


String interpolation

Use string interpolation instead of "some text" + someValue"

sorry didn't see the PR.
I just renamed PropertySiteProcessor.
could you exlcude the changes to PropertySiteProcessor and just merge directly?

sorry didn't see the PR.
I just renamed PropertySiteProcessor.
could you exlcude the changes to PropertySiteProcessor and just merge directly?

Wait on more commits until this finishes processing


Chat - Message on first window is appeared on second window it should get focused

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open website and any chat on 2 windows
For second window click out of message box to lose focusing
Type something for first window's message box and go to second one

Expected Result:
When message on first window is appeared, it should get focused on second window
Actual Result:
Message on first window is appeared on second window, but it doesn't get focused
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.57-5
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/787d8eda-7cf5-4881-8d47-5d97f6e62267
https://github.com/Expensify/App/assets/115492554/e858a2e1-2f1d-4fb5-b2de-3250e3f201a8
Expensify/Expensify Issue URL:
Issue reported by: @mahmudjontoraqulov
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692532500119099
View all open jobs on GitHub

closing this -very edge behavior, mostly a polish


CAN-bus transport coding for micro-XRCE-Client and Agent

Hi Pablo,
It would be very appreciated you could share your opinions on where-about the code for CAN-bus transport should be placed.

I will use the CAN-RX interrupt, and place them incoming bytes into a circular buffer for the uxr_xx_read() and uxr_xx_write() in udp_transport.c. As such, STM32CubeMX will be used to create the skeleton of the CAN-RX interrupt, and its, the interrupt body will fill up the circular buffer from which the uxr_xx_read() will be reading. For the same reason, the CAN-TX function will also reside in the stm32-e407 main(), and uxr_xxx_write() will call it, the CAN_Tx() when transmitting data. I think microROS which has the controller's low-level files, is needed. Does it make sense?

I have read about CANSocket, which is a replica of Network Socket. With that I think I can change the body of UDPv4AgentLinux.cpp, i.e., bool UDPv4Agent::init(),  bool UDPv4Agent::fini()
bool UDPv4Agent::send_message(),
bool UDPv4Agent::recv_message(). I would like to seek your opinion on that, please?

BTW, can you please look into the read messages when I compiling in Raspberry Pi4? FYI, I did not specify it was Raspberry. I was wondering if that is the cause of the errors.

I look forward to hearing from you.
Thank you
V!

I guess, the case #1 is no longer valid, as it has been answered in the other issues. However, any comments of case #2 and #3 would be appreciated.
Thank you

Hello,

Share code if possible
I have not implemented any custom transport in Micro XRCE-DDS Agent, so I'm not sure about the feasibility of rewriting transports like this. Maybe @jamoralp can help us here.
Answered here

Sure! I will, very soon.
On Mon, 19 Oct 2020 at 18:22, Pablo Garrido<EMAIL_ADDRESS>wrote:

Hello,

Share code if possible
I have not implemented any custom transport in Micro XRCE-DDS
Agent, so I'm not sure about the feasibility of rewriting transports like
this. Maybe @jamoralp https://github.com/jamoralp can help us here.
Answered here
https://github.com/eProsima/Micro-XRCE-DDS-Agent/issues/192

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/eProsima/Micro-XRCE-DDS-Client/issues/169#issuecomment-711593264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADCYQVRR2PTAYMT6SC3WLBTSLPEI3ANCNFSM4SU7TPKA
.

Closing this since inactive for two months. Please continue the discussion in the issue of the Agent repo, and slack channel


feat(util): shorts and default helper

references #2588

@antfu it's now ready for review
I also fixed that it does not override short values if they already exists

Closing this for now until we see really and general use cases. Thanks for bringing this up.


[Avatar]: Remove icon prop from rendering on DOM element

Description
Stops the icon prop from rendering on the Avatar component DOM element
Motivation and context
closes #584
Screenshots, videos, or demo, if appropriate
https://584-avatar--mineral-ui.netlify.com/components/avatar/
How to test

View the source of an Avatar component that renders an Icon in the website. Note that it no longer contains icon="[object Object]".
Verify that the icon functionality of the Avatar component still works

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] Renders and functions properly in all supported browsers - [n/a]
[x] Automated tests written and passing - [n/a]
[x] Accessibility and inclusivity considered - [n/a]
[x] Rendering performance (initial load time & 60fps) and perceived performance considered - [n/a]
[x] Documentation created or updated - [n/a]
[x] Tested in sandbox if new component or breaking change - [n/a]

why is this a problem?

This obviously wasn't a big problem @coldpour.  I was just recently adding some stories of small things that I noticed and had a few spare minutes so I just fixed it.  The only reason that I PR'd it was to show any team members how to fix similar issues in the future, in case they weren't aware.


Increment version for synapse releases

Increment package version after release of com.azure azure-analytics-synapse-artifacts

/check-enforcer evaluate


how to install fydeos in raseberrypi noobs?

Please elaborate on what is "install fydeos in raspberry pi noobs"?

I think they want to dual boot and are asking how to install this via NOOBS


Prefix all shell commands with backslashes to ignore aliases

I recently began using exa to replace ls. To make the switch easier, I aliased ls:
$ which ls
ls: aliased to exa --icons --classify --header --git

As a result, the command this package uses to get the latest log file (ls -t) throws an error instead of listing the sorted files:
$ ls -t
exa: Flag -t needs a value (choices: modified, changed, accessed, created)
To sort newest files last, try "--sort newest", or just "-snew"

The package uses the ls, head, tail, and grep shell commands, and they all could potentially be aliased/overwritten on the user's system. This could break the package, and there is no way of knowing because the output is suppressed:

This PR simply adds backslashes to the beginning of each shell command so that aliases are ignored and the native shell commands are used instead.
I can manually specify the escaped command with --file to get it to work, but it's janky and you'll only know to do it this way if you know why it's throwing the error in the first place:
php artisan tail --file="\`\\ls -t | \\head -1\`"

Thanks!

It seems that this PR also contains code gormatting changes, making it harder to review.
Could you remove all code formatting changes?

Oh geez, I’m so sorry! It’s a good reminder that all of my diff tools are set to ignore whitespace changes, so I didn’t even see those formatting changes 🤦🏼♂ I’ll revert everything except the actual changed lines and push.

@freekmurze The unrelated whitespace/formatting changes have been reverted 👍🏻

Thanks!

My pleasure!


Upload a merged coverage report to Codecov

Multiple coverage reports are currently sent to Codecov, one for each module that contains tests. This is not optimal as tests in a module should be able to add coverage data to another one. The JaCoCo Report Aggregation Plugin could help with it.

Done!


Added details for using links within markup.

Issue #958
Additions:

Links section on Markdown page.
link row within Styles page table.

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

@phil-scott-78 I think I did this correctly?


Feature: Add devcontainer configuration

Checklist

[x] Used a personal fork of the feedstock to propose changes

Description
Adds a devcontainer configuration that installs conda-smithy and docker-in-docker (for local build testing).

Why is
conda debug -m .ci_support/linux.... recipe

or
python build-locally.py --debug

enough?

@hmaarrfk The purpose of the devcontainer configuration is precisely to enable running the two commands you listed in a completely isolated development environment. You make no assumptions about any pre-installed software (e.g. conda or conda-smithy) the developer is likely to have on their machine and instead provide a configuration that installs everything for them.
I find this particularly useful because it's compatible with Github Codespaces which allows you to shift your development environment into the cloud as well.
If you want to take it for a spin, go to this link to create a Codespace using the devcontainer configuration in this branch. Despite the failing CI pipelines it's working correctly locally.

does all this run on the GitHub cloud? if so. that is pretty interesting.
let's discuss this feature outside of this feedstocks. this kind of tooling should be automatically generated by conda smithy and not added in an adhoc fashion. ya least in my opinion.
conda forge tends to suck up public resources and I'm somewhat worried we would damage the goodwill of Microsoft (Azure, and recently Github) where we build most of the packages

does all this run on the GitHub cloud? if so. that is pretty interesting.

A devcontainer.json configuration can be used in two ways:

Locally in Docker via VSCode DevContainers - this relies on no cloud infrastructure
In the cloud on Github's Codespaces servers. - This is a paid service, but each Github account has a certain amount (~40 hours IIRC) of free usage per month.

let's discuss this feature outside of this feedstocks. this kind of tooling should be automatically generated by conda smithy and not added in an adhoc fashion. ya least in my opinion.

I'm new to contributing conda-smithy and the feedstocks. My intuition was that adding some convenience functions to aid maintainers in debugging their failed recipes would be allowable. But if you think this would be better to add directly to the templates, I'd be happy to open a feature request and a PR at conda-smithy. Would this be the correct place to add that?.

conda forge tends to suck up public resources and I'm somewhat worried we would damage the goodwill of Microsoft (Azure, and recently Github) where we build most of the packages

I don't think this is a concern when hands-on developer time is probably a tiny fraction of what the automated actions workflows consume. Also, the codespaces usage is tracked/billed for each individual developer and using the local docker option uses no cloud resources.

I unfortunately I think we should try to limit "customization" like this.
You have a few options:

Create a pinned issue to help you debug
use the commands i listed above
make a case for it in github.com/conda-forge/conda-smithy

Do take into account the discussion in: https://github.com/conda-forge/conda-smithy/pull/1413
where effectively some are considering ignoring everything outside the recipe folder.
While I am but 1 core developer I think that the commands:
conda debug
python build-locally --debug

will just really be enough for 99% of the packages.
adding too many layers of abstractions really hurts development sometimes.

Thanks for the explanation @hmaarrfk . I'll make the appropriate feature request in conda-smithy.


SSH failed - expected host key does not match

Hi there,
I am running the SSH integration on HASS OS and I added a host successfully with the integration for testing. After a while I reinstalled an Pi Os image on the host and since then I am not able to connect to the host again. I get the following error:
SSH connection failed (Host key for server '192.168.0.x' does not match: got 'abc', expected 'xyz').
Makes sense, since the image changed, hence the key files also changed. I wanted to delete the host key file on HASS OS but there is no file in ~/.ssh/known_hosts. I tried it in different locations, with root but had no success. The known_hosts file does not exist.
There is a known_hosts file in /homeassistant(config) and it shows a different host that I added to the integration, but not the one with the mismatch.
Any ideas?
Thanks in regards!

The known_hosts file inside the config folder should be the correct one. I have experienced this a couple of times before, and it works just fine for me removing the line within the file.
Would be a nice addition if you would get a question rasied if you want to overwrite the entry.

Followup: I'm running out of ideas at this point. I've removed the key from just about every single file it could exist on, removed and reinstalled the integration, and rebooted the OS. I'm out of places to check for where it's cached this host key, and I can no longer connect to my device.
I modified the SSH component to print out the known_hosts file name and contents, and it's loading the correct file. I can see the contents change—I can even see the correct key within the file once I manually add it (it shows the empty array before, then the correct info after):
Logger: custom_components.ssh.config_flow
Source: custom_components/ssh/config_flow.py:495
integration: ssh ([documentation](https://github.com/zhbjsh/homeassistant-ssh), [issues](https://github.com/zhbjsh/homeassistant-ssh/issues))
First occurred: 2:51:04 PM (2 occurrences)
Last logged: 2:52:13 PM

    []
    ['<IP_ADDRESS> ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBG/ytEmKSLda9LsY/bLiANMNFHWltnW/AaPmvD1ZXdnnH5WeaUxvTP6iHufE67QIFZgmxROrIGJeI4UX4/bOr9U=\n', '\n']

Yet immediately after this, the SSH connection fails:
This error originated from a custom integration.

Logger: custom_components.ssh.config_flow
Source: custom_components/ssh/config_flow.py:576
integration: ssh (documentation, issues)
First occurred: 2:51:05 PM (2 occurrences)
Last logged: 2:52:14 PM

SSH connection failed (Host key for server '<IP_ADDRESS>' does not match: got 'AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBG/ytEmKSLda9LsY/bLiANMNFHWltnW/AaPmvD1ZXdnnH5WeaUxvTP6iHufE67QIFZgmxROrIGJeI4UX4/bOr9U=', expected 'AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBF3g1fIiEb+4X6YmIjSpP5PJ0U+Z/24wwc46hd8lrV3Iz/eKYkQdpgfemZIYmInOcEkRC/QEgv/aDVJ9Lh9cY+M=')

Hopefully someone can help, because at this point the only solution I can come up with is to change the IP of my device, which is bonkers.

I figured it out! I had also configured some shell commands, and since these also use SSH, it apparently added a key to /root/.ssh/known_hosts, which is not accessible to the normal login for HA.
I ended up adding an additional shell_command for ssh-keygen -R <IP>, which I can run manually to remove the key from this hidden file, and it allowed me to access the device again.

I figured it out! I had also configured some shell commands, and since these also use SSH, it apparently added a key to /root/.ssh/known_hosts, which is not accessible to the normal login for HA.
I ended up adding an additional shell_command for ssh-keygen -R <IP>, which I can run manually to remove the key from this hidden file, and it allowed me to access the device again.

same issue here,  can you explain what you did to fix this ?
i have a empty folder on  /root/.ssh/

@puerto-rico
I added a shell command to reset the known_hosts, which looks like this:
shell_command:
  crestron_reset_host_key: ssh-keygen -R "<IP_ADDRESS>"

You'll have to restart HA for it to take effect. Make sure you change the IP address to your screen's address.
Then inside HomeAssistant, just run the new command using the developer tools. It has no arguments.

Hi! Sorry to keep you waiting...
Since version 0.9.8 you can choose to ignore the system host keys (the one in ~/.ssh/known_hosts) and only use the file generated by the integration. You can change the setting by clicking on the three dots in the device settings and then on Reconfigure . The former behavior was indeed a bit confusing, I hope it makes more sense now!

thanks, but i could not find out how to do this, i am just a basic user of HA.
But found a more simple solution, that i did not think of before.
i used the built  in "file editor" with that i could just edit the file.
Now the integration works again :)


Using open_manipulator_6dof with Moveit!

Hi,
ROS Kinectic on Ubuntu 16.06
Joint Dynamixel ID : 11, Model Name : XM430-W210
Joint Dynamixel ID : 12, Model Name : XH430-W350
Joint Dynamixel ID : 13, Model Name : XH430-W350
Joint Dynamixel ID : 14, Model Name : XM430-W210
Joint Dynamixel ID : 15, Model Name : XM430-W210
Joint Dynamixel ID : 16, Model Name : XM430-W210
Gripper Dynamixel ID : 17, Model Name :XM430-W210
I am following this and made a 6dof open manipulator.
When I use the moveit, the arm_group works fine.
However, I am not able to control the gripper with MoveIt Commander Scripting, even if the range is -0.01 ~ 0.01.
I can see the path planned in Rviz, but it is not executed to the real robot.
This is the error:
[INFO] [OpenManipulator Controller] Execute Moveit planned path
terminate called after throwing an instance of 'std::out_of_range'
  what():  vector::_M_range_check: __n (which is 1) >= this->size() (which is 1)
[open_manipulator_6dof-6] process has died [pid 41350, exit code -6, cmd /home/cybernetchi/catkin_ws/devel/lib/open_manipulator_6dof_controller/open_manipulator_6dof_controller /dev/ttyUSB0 1000000 __name:=open_manipulator_6dof __log:=/home/cybernetchi/.ros/log/518d038e-0c2c-11ec-baa5-000c2960058a/open_manipulator_6dof-6.log].
log file: /home/cybernetchi/.ros/log/518d038e-0c2c-11ec-baa5-000c2960058a/open_manipulator_6dof-6*.log

Any help would be appreciated!
Thank you very much!

Hi @cybernetchi
The 6 DOF OpenMANIPULATOR is created by a community developer so please contact the developer for more details.
If I were you, I'd run the keyboard teleop and check the gripper's working range.
https://github.com/zang09/open_manipulator_6dof_application#keyboard
Thank you.

This issue will be closed due to prolonged inactivity.


Support inclusion of related resources

http://jsonapi.org/format/#fetching-includes

Implemented in release 3.4.0


Leverage Nova 3.1 separate method fields

Nova 3.1 introduced the ability to split fields declaration in separate methods (fieldsForIndex, FieldsForDetail, FieldsForCreate, fieldsForUpdate).
This PR add support to these new methods.

Duplicate of #126

This PR also work with Nova prior to 3.1.

Hi @ragingdave,
do you think this PR is ready to be merged?
Thanks


do packages that use ts-toolbelt a major upgrade for ts-toolbelt v9?

🤔 Question
2 short questions!

if my "util" package has ts-toolbelt as dependency. Should I make TS-Toolbelt a dependency a devDependency or a peerDependency ?
if my package upgrades to ts-toolbelt v9, should it do a major upgrade?

It must be a dependency. If you set it as a devDependency, your package consumers will not benefit from the types packaged in the ts-toolbelt - it will appear to be broken at first. They might have to install ts-toolbelt by hand, that's why you could enable peerDependency. But since two ts-toobelt versions can now cohabitate, it really only makes sense to add it as a direct dependency.

The short answer is "No". The types are safer, so stuff might break. But we can generally consider this as a patch - not a breaking change. These changes mostly affect output of types that use the At utility. The breaking change is more for you, who will have to do the work to adapt to the new API.


Initial pass at "relaxed" multiply and add operations.

This commit adds the following implementation hooks to the AlgebraicField protocol:
static func _relaxedAdd(_:Self, _:Self) -> Self
static func _relaxedMul(_:Self, _:Self) -> Self

These are equivalent to + and *, but have "relaxed semantics"; specifically, they license the compiler to reassociate them and to form FMA nodes, which are both significant optimizations that can easily make many common loops 8-10x faster. These transformation perturb results slightly, so they should not be enabled without care, but the results with the relaxed operations are--for most purposes--"just as good as" (and often better than) what strict operations produce. The main thing to beware of is that they are no longer portable; different compiler versions and different targets and optimization flags will result in different results.
These are then exposed under the Relaxed namespace as:
Relaxed.sum(a, b)
Relaxed.product(a, b)

@swift-ci test

@swift-ci test

Hrm, why are we using a Swift-5.3.3 Linux toolchain for testing instead of something more recent? Still, good to know--if unfortunate--that reassociate(on) is not supported there. I'll have to add a workaround and a note for that.

@swift-ci test

@swift-ci test

@swift-ci test

Some quick perf numbers from my M1 laptop:
repeatedly summing 1024 Floats
time using reduce(0, +): 0.091 sec
time using reduce(0, Relaxed.sum): 0.009 sec
time using vDSP.sum from Accelerate: 0.004 sec
repeated dot-product of 1024 Floats
time using reduce(0) { $0 + $1*$1 }: 0.085 sec
time using reduce(0) { Relaxed.multiplyAdd($1, $1, $0): 0.011 sec
time using vDSP.sumOfSquares from Accelerate: 0.005 sec
For "typical" reduction workloads as above, we see about a 10x speedup over the strict operators, and we're about 2x off of hand-written SIMD.


Path-mapping issue

RxJS version:
5.5.0
Angular-cli: 1.4.9
Code to reproduce:
import {startWith} from 'rxjs/operators/startWith'
Expected behavior:
Should import without errors
Actual behavior:
node_modules/rxjs/_esm5/operators/index.js/startWith.js doesn't exist
Note index.js in path
Additional information:
The issue is probably related to rxjs/_esm5/path-mapping.js file:
...
    "rxjs/operators/groupBy": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/groupBy.js"),
    "rxjs/operators/ignoreElements": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/ignoreElements.js"),
    "rxjs/operators/index": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/index.js"),
    "rxjs/operators": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/index.js"),
    "rxjs/operators/isEmpty": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/isEmpty.js"),
    "rxjs/operators/last": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/last.js"),
    "rxjs/operators/map": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/map.js"),
    "rxjs/operators/mapTo": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/mapTo.js"),
    "rxjs/operators/materialize": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/materialize.js"),
...

As you see, "rxjs/operators" is between other modules. Importing modules that are before this line works as expected, but all modules after it fail with error. I think need to move line
"rxjs/operators": path.resolve(PATH_REPLACEMENT, "rxjs/_esm5/operators/index.js"),

after other "rxjs/operators/..." modules.

Same problem. It tries to load operators.js and there isn't a file like that.

/cc @jasonaden

@aksyonov Thanks. I also found this issue. It's due to a problem with how Webpack handles aliasing. Here's the PR that fixes it for rxjs: #2987. I also filed an issue against Webpack as depending on sequence of keys in an object is not good.

The fix landed in 5.5.2 (https://github.com/ReactiveX/rxjs/commit/24854cf66172f91f55729765c4d64e61607563c8#diff-4ac32a78649ca5bdd8e0ba38b7006a1eR7). Could this be closed then?