[terra-i18n] Missing intlLoaders And translationsLoaders Dependencies

Issue Description
The terra-i18n component is using intlLoaders (link) and translationsLoaders (link) dependencies.
As a result when building our application with webpack the extract-text-webpack-plugin is throwing the following error:
ERROR in ./~/terra-i18n/lib/intlLoaders.js
Module not found: Error: Can't resolve 'intlLoaders' in '/home/pophealth/workspace/referral_management/client/node_modules/terra-i18n/lib'
 @ ./~/terra-i18n/lib/intlLoaders.js 3:19-41
 @ ./~/terra-i18n/lib/i18nLoader.js
 @ ./~/terra-i18n/lib/I18n.js
 @ ./~/terra-base/lib/Base.js
 @ <our react component>
 @ ./app/index.js
 @ multi ./app/index

ERROR in ./~/terra-i18n/lib/translationsLoaders.js
Module not found: Error: Can't resolve 'translationsLoaders' in '/home/pophealth/workspace/referral_management/client/node_modules/terra-i18n/lib'
 @ ./~/terra-i18n/lib/translationsLoaders.js 3:27-57
 @ ./~/terra-i18n/lib/i18nLoader.js
 @ ./~/terra-i18n/lib/I18n.js
 @ ./~/terra-base/lib/Base.js
 @ <our react component>
 @ ./app/index.js
 @ multi ./app/index
Child extract-text-webpack-plugin:

Issue Type

[ ] New Feature
[ ] Enhancement
[x] Bug
[ ] Other

Expected Behavior
Terra should include the intlLoaders and translationsLoaders as a dependencies so that build processes do not fail when looking for intlLoaders and translationsLoaders when using the terra-i18n component.
Current Behavior
Webpack build processes are not able to locate the intlLoaders and translationsLoaders dependencies, so they are failing.
Steps to Reproduce

Use the Terra-Popup component in a react component.
Use webpack with the extract-text-webpack-plugin with the following loaders: css-loader, postcss-loader, and sass-loader.
Run webpack.

Environment

Component Version: 2.0.0
Browser Name and Version: Google Chrome; Version 65.0.3325.181 (Official Build) (64-bit)
Operating System and version (desktop or mobile): macOS Sierra; Version 10.12.6

@joel-cohen could you post your webpack config?

@mjhenkes
const webpack = require('webpack');
const { resolve } = require('path');
const Autoprefixer = require('autoprefixer');
const I18nAggregatorPlugin = require('terra-i18n-plugin');
const i18nSupportedLocales = require('terra-i18n/lib/i18nSupportedLocales');
const ExtractTextPlugin = require('extract-text-webpack-plugin');
const CustomProperties = require('postcss-custom-properties');

const imageLoaderOptions = {};
const entryOutput = {};

if (process.env.RAILS_ENV === 'production') {
  imageLoaderOptions.outputPath = '/images/';
  entryOutput.filename = './[name].js';
  entryOutput.path = resolve(`${__dirname}./../public/`);
} else {
  entryOutput.filename = './[name].js';
  entryOutput.path = resolve(`${__dirname}./../public/javascripts`);
}

const config = {
  node: {
    fs: 'empty',
    child_process: 'empty',
  },

  context: resolve(__dirname),

  entry: {
    'commons-bundle': ['babel-polyfill', 'jquery-ujs'],
    'app-bundle': ['./app/index'],
  },
  output: entryOutput,
  resolve: {
    extensions: ['.js', '.jsx'],
    modules: [resolve(__dirname, 'aggregated-translations'), 'node_modules'],
    alias: {
      'react-intl': resolve(__dirname, 'node_modules/react-intl'),
    },
  },

  plugins: [
    new webpack.DefinePlugin({
      'process.env': {
        NODE_ENV: JSON.stringify(process.env.RAILS_ENV || 'production'),
      },
    }),
    new webpack.NamedChunksPlugin(),
    new ExtractTextPlugin(process.env.RAILS_ENV === 'development' ? './stylesheets/[name].css' : './[name].css'),
    new webpack.ProvidePlugin({
      $: 'jquery',
      jQuery: 'jquery',
    }),
    new I18nAggregatorPlugin({
      baseDirectory: __dirname,
      supportedLocales: i18nSupportedLocales,
    }),
  ],

  module: {
    rules: [
      {
        test: require.resolve('react'),
        use: {
          loader: 'imports-loader',
          options: {
            shim: 'es5-shim/es5-shim',
            sham: 'es5-shim/es5-sham',
          },
        },
      },
      {
        test: /\.(jsx|js)$/,
        use: 'babel-loader',
        exclude: /node_modules/,
      },
      {
        test: /\.(css|scss)$/,
        use: ExtractTextPlugin.extract(
          {
            fallback: 'style-loader',
            use: [
              {
                loader: 'css-loader',
                options: {
                  sourceMap: true,
                  importLoaders: 2,
                  localIdentName: '[name]__[local]___[hash:base64:5]',
                },
              },
              {
                loader: 'postcss-loader',
                options: {
                  plugins() {
                    return [
                      Autoprefixer(
                        {
                          browsers: [
                            'ie >= 10',
                            'last 2 versions',
                            'last 2 android versions',
                            'last 2 and_chr versions',
                            'iOS >= 8',
                          ],
                        }
                      ),
                      CustomProperties({ preserve: true, warnings: false }),
                    ];
                  },
                },
              },
              {
                loader: 'sass-loader',
                options: {
                  data: '$bundled-themes: "mock";',
                },
              },
            ],
          }
        ),
      },
      {
        test: /\.(png|svg|jpg|gif)$/,
        use: [
          {
            loader: 'file-loader',
            options: imageLoaderOptions,
          },
        ],
      },
    ],
  },
};

module.exports = config;

@joel-cohen  The installed module from npm includes intlLoaders.js and translationsLoaders.js.
I'm not sure whats wrong.

We do have a bug with no-transpiled files, but i'm not sure this is the same issue. https://github.com/cerner/terra-core/issues/1400

@mjhenkes
I am not sure if this is the same type of issue, but you may need to add intlLoaders and * translationsLoaders* dependencies to the package.json for the terra-i18n component.  I reported a similar issue here: link.

That shouldn't be a problem here. i18nLoaders references intlLoaders and translationLoaders relative to itself. i.e. var _intlLoaders = require('./intlLoaders');. So as long as it's included in the webpack package it should be found. Can you check your terra-i18n module in your node_modules folder and see if those files are present?

@mjhenkes You can close this issue, but I am not sure why this fixed the issue.  I noticed that webpack was indicating the following warning farther up in the logging:
WARNING: The terra-i18n aggregate-translations setup function should be used instead of the terra-i18n-plugin. Terra-i18n-plugin will be deprecated in the future. See https://github.com/cerner/terra-core/blob/master/packages/terra-i18n/docs/AggregateTranslations.md for usage.

I followed the guide and in the above link and removed the terra-i18n-plugin package and changed webpack config to not use terra-i18n-plugin as well.  Webpack built successfully, however I am not sure why that corrected the issue of not being able to resolve those dependencies with terra-i18n.

@mjhenkes
npm  v3.8.6

That version is supposed to support post install, but I'd recommend you go ahead and update npm. It's up to version 5 now.

I've run into the same issue.  When I run yarn install --force it seems to do some additional work and link packages then it works. I'm still not certain what the problem is.

We're going to remove the post install script https://github.com/cerner/terra-core/pull/1853

Degrading terra-clinical-application dependency from 3.2.0 to 2.3.0 resolved the issue for me

I also get the same issue.
./node_modules/terra-i18n/lib/intlLoaders.js
Module not found: Can't resolve 'intlLoaders' in 'C:\TerraReact\clayton\node_modules\terra-i18n\lib'
Webpack.config.js
const Autoprefixer = require('autoprefixer');
const PostCSSAssetsPlugin = require('postcss-assets-webpack-plugin');
const PostCSSCustomProperties = require('postcss-custom-properties');
const path = require('path');
const rtl = require('postcss-rtl');
const MiniCssExtractPlugin = require('mini-css-extract-plugin');
const { CleanWebpackPlugin } = require('clean-webpack-plugin');
const TerserPlugin = require('terser-webpack-plugin');
const webpack = require('webpack');
const merge = require('webpack-merge');
const DuplicatePackageCheckerPlugin = require('@cerner/duplicate-package-checker-webpack-plugin');
const aggregateTranslations = require('terra-aggregate-translations');
const ThemeAggregator = require('../../scripts/aggregate-themes/theme-aggregator');
const getThemeWebpackPromise = require('./getThemeWebpackPromise');
const webpackConfig = (options, env, argv) => {
const {
rootPath,
resolveModules,
staticOptions,
aggregatedLocales,
themeFile,
} = options;
const production = argv.p;
const fileNameStategy = production ? '[name]-[chunkhash]' : '[name]';
const chunkFilename = argv['output-chunk-filename'] || fileNameStategy;
const filename = argv['output-filename'] || fileNameStategy;
const outputPath = argv['output-path'] || path.join(rootPath, 'build');
const publicPath = argv['output-public-path'] || '';

const devConfig = {
    mode: 'development',
    entry: {
        raf: 'raf/polyfill',
        'core-js': 'core-js/stable',
        'regenerator-runtime': 'regenerator-runtime/runtime',
        ...themeFile && { theme: themeFile },
    },
    module: {
        rules: [{
                test: /\.(jsx|js)$/,
                exclude: /node_modules/,
                use: {
                    loader: 'babel-loader',
                    options: {
                        rootMode: 'upward', // needed to correctly resolve babel's config root in mono-repos
                    },
                },
            },
            {
                test: /\.(scss|css)$/,
                use: [{
                        loader: MiniCssExtractPlugin.loader,
                        options: {
                            hmr: !production, // only enable hot module reloading in development
                            sourceMap: true,
                        },
                    },
                    {
                        loader: 'css-loader',
                        options: {
                            modules: {
                                mode: 'global',
                                localIdentName: '[name]__[local]___[hash:base64:5]',
                            },
                            sourceMap: true,
                            importLoaders: 2,
                        },
                    },
                    {
                        loader: 'postcss-loader',
                        options: {
                            // Add unique ident to prevent the loader from searching for a postcss.config file. See: https://github.com/postcss/postcss-loader#plugins
                            ident: 'postcss',
                            sourceMap: true,
                            plugins() {
                                return [
                                    rtl(),
                                    Autoprefixer(),
                                ];
                            },
                        },
                    },
                    {
                        loader: 'sass-loader',
                        options: {
                            sourceMap: true,
                        },
                    },
                ],
            },
            {
                test: /\.md$/,
                use: 'raw-loader',
            },
            {
                test: /\.(png|svg|jpg|gif|otf|eot|ttf|svg|woff|woff2)$/,
                use: 'file-loader',
            }
        ],
    },
    plugins: [
        new MiniCssExtractPlugin({
            filename: `${filename}.css`,
            chunkFilename: `${chunkFilename}.css`,
            ignoreOrder: true,
        }),
        new PostCSSAssetsPlugin({
            test: /\.css$/,
            log: false,
            plugins: [
                PostCSSCustomProperties({
                    preserve: true,
                    // If we have a theme file, use the webpack promise to webpack it.  This promise will resolve to
                    // an object with themeable variables and values. This will then be used to update the end state CSS
                    // so that they are populated with values if variables aren't supported (e.g. IE10). This dance is
                    // necessary when code splitting to ensure the variables and values are applied across all code split
                    // css files
                    ...themeFile && { importFrom: [getThemeWebpackPromise(rootPath, themeFile)] },
                }),
            ],
        }),
        new DuplicatePackageCheckerPlugin({
            showHelp: false,
            alwaysEmitErrorsFor: [
                'react',
                'react-dom',
                'react-intl',
                'react-on-rails',
                'terra-application',
                'terra-breakpoints',
                'terra-disclosure-manager',
                'terra-navigation-prompt',
            ],
        }),
        new webpack.DefinePlugin({
            CERNER_BUILD_TIMESTAMP: JSON.stringify(new Date(Date.now()).toISOString()),
            TERRA_AGGREGATED_LOCALES: JSON.stringify(aggregatedLocales),
        }),
    ],
    resolve: {
        extensions: ['.js', '.jsx'],
        modules: resolveModules,
        mainFields: ['main'],
    },
    output: {
        filename: `${filename}.js`,
        chunkFilename: `${chunkFilename}.js`,
        path: outputPath,
        publicPath,
    },
    devServer: {
        ...staticOptions,
        host: '<IP_ADDRESS>',
        publicPath,
        stats: {
            colors: true,
            children: false,
        },
    },
    devtool: 'eval-source-map',
    resolveLoader: {
        modules: [path.resolve(path.join(rootPath, 'node_modules'))],
    },
    stats: { children: false },
};

if (!production) {
    return devConfig;
}

return merge.strategy({
    devtool: 'replace',
})(devConfig, {
    mode: 'production',
    devtool: false,
    plugins: [
        new CleanWebpackPlugin({ cleanOnceBeforeBuildPatterns: ['**/*', '!stats.json'] }),
    ],
    optimization: {
        minimizer: [
            new TerserPlugin({
                cache: true,
                parallel: true,
                sourceMap: true,
                terserOptions: {
                    compress: {
                        typeofs: false,
                    },
                },
            }),
        ],
    },
});

};
const defaultWebpackConfig = (env = {}, argv = {}) => {
const { disableAggregateTranslations, disableHotReloading } = env;
const staticOptions = {
    ...disableHotReloading && {
        hot: false,
        inline: false,
    },
};

const processPath = process.cwd();
/* Get the root path of a mono-repo process call */
const rootPath = processPath.includes('packages') ? processPath.split('packages')[0] : processPath;

const resolveModules = ['node_modules'];

let aggregatedLocales;
if (!disableAggregateTranslations) {
    aggregatedLocales = aggregateTranslations({ baseDir: rootPath, ...env.aggregateOptions });
    resolveModules.unshift(path.resolve(rootPath, 'aggregated-translations'));
}

const themeOverride = process.env.THEME; // Flexes root theme for theme visual regression testing.
const themeFile = ThemeAggregator.aggregate(themeOverride);

const options = {
    rootPath,
    resolveModules,
    staticOptions,
    aggregatedLocales,
    themeFile,
};

return webpackConfig(options, env, argv);

};
module.exports = defaultWebpackConfig;

@ayanchax
Can you provide a link to the project? The screenshot suggests the project was generated with create react app. I'd like to double check the configurations that were added after the project was generated.

just the UI components would do. I want to start a Demo TerraUI project.
How do I do that ?
Steps I followed:

npx create-react-app demoTerra
After Step 1 enter "cd demoTerra"
After Step 2 start the development server by entering "npm start"

The server starts and shows me the landing page as well, but then when I try installing TerraUI component into the project from the tutorial:
https://engineering.cerner.com/terra-ui/getting-started/terra-ui/basic-usage
It throws me the error when I restart the server again, the error being:
./node_modules/terra-i18n/lib/intlLoaders.js Module not found: Can't resolve 'intlLoaders' in 'C:\TerraReact\clayton\node_modules\terra-i18n\lib'
Am I doing something wrong here ?

I'm also facing this problem.
Have any solution?

@shaponpal6 can you provide information on when you are seeing this error?

I'm also getting same error above.
I have tried all the scope above.
This is my fresh installed react app.

I see you are using react-scripts, so this is a create-react-app project? Did you setup you project to aggregate terra's translations? https://engineering.cerner.com/terra-ui/guides/terra-ui/internationalization/aggregate-translations
This would require updates to your project's webpack configuration.

This is my repo
https://github.com/shaponpal6/tara-ui

Is there an example with webpack set up @emilyrohrbough ? I too have been trying and failing to set up webpack.

@SvenWritesCode the minimal setup we have provided in documentation is this: https://engineering.cerner.com/terra-ui/dev_tools/terra-ui/webpack#extending-the-default-config


Rething overflow_integer

From SG14 telecon: there are two distinct types:

saturated and modulo never overflow
throwing, undefined, contract and assert do not accept (either puke on or prohibit) the operation completes
Suggested name: fixed_width

Another suggestion: https://www.johndcook.com/blog/finite-fields/

I think I ran a Twitter poll about this and never got a satisfactory alternative naming scheme. It may come up again some day...


[Filip to repurpose] Approach with storing assets for VANotify

Filip to add details on the options that were discussed.
Notes:

The existing approach for storing VA assets needs to be resolved to work in Production
Interim approach for storing assets is in card #145
Additional card/s will be created once the approach is finalized
Sync with Filip on options that he has already discussed for the interim, and the limitations with the VA
Document the decision on how/where to store assets for VANotify

@ffafara-tw confirming that this story is no longer needed? Is it being handled differently or elsewhere?

Not needed. Please see ADRs for more information about considered apporoaches.


Incorrect Instructions

The instructions state to remove all values from the array greater than 5. The provided answer does just that, however the answer being looked for is an array with all values greater than or equal to 5 removed.

Challenge Waypoint: Filter Arrays with filter has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
var array = [1,2,3,4,5,6,7,8,9,10];
  // Only change code below this line.

array = array.filter(function(val) {
  return val < 5;
});

  // Only change code above this line.
(function() {return array;})();

Thanks for posting.  There is a similar issue; #3671 and a fix has been accepted; #3678.

Closing this issue as it is fixed in https://github.com/FreeCodeCamp/FreeCodeCamp/pull/3678 and, hopefully, the fix should be in production soon.


Username Password name of machine error

I ran the script and when i came to enter a username i get "username does not exist" and then it straight jumps to naming the machine, i name the machine and it sats "error" then finishes the installation and prompts me to eject the media and reboot, i reboot and eject the media and fire up arch. I am then welcomed with a screen that says Select your user and enter password. And i cant click anywhere and i am stuck on this screen.
What went wrong? i have retried this installation 4 times now and i end up with the same result every time.

Which username did you try?

Which username did you try?

I reinstalled it again at home with a different internet connection, then it worked flawlessly! I've tried it out for a couple of hours now and i went back to Pop os. I couldn't get Battle.net working, it wouldn't connect...
I am looking forward to debian titus however, will try that out as well when he is done with it!


[k8s] Remove chart from matchLabels in helper templates

This line will be prevent doing upgrades of the StatfulSet when a new version needs to be deployed
https://github.com/apache/pinot/blob/master/kubernetes/helm/pinot/templates/_helpers.tpl#L58
Kubernetes will fail with error
spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden

I think this issues refers to this line: https://github.com/apache/pinot/blob/bb2519494a15a3125dd509286d60ffd124f91c37/kubernetes/helm/pinot/templates/_helpers.tpl#L58
The line has been removed in #7177 (with a way to keep compatibility with already deployed charts) and so the issue can be closed?


Routing error with latest version

When I launch the latest version of Orchard.Cms.Web, this exception occurs:
An unhandled exception occurred while processing the request.

InvalidOperationException: Unable to find the required services. Please add all the required services by calling 'IServiceCollection.AddRouting' inside the call to 'ConfigureServices(...)' in the application startup code.
Microsoft.AspNetCore.Routing.RouteBuilder..ctor(IApplicationBuilder applicationBuilder, IRouter defaultHandler)

In Microsoft.AspNetCore.Modules.ModularTenantRouteBuilder.Build() in src\OrchardCore\Microsoft.AspNetCore.Modules\ModularTenantRouteBuilder.cs
line 23:
var routeBuilder = new RouteBuilder(appBuilder)
@Jetski5822 : Do you have any idea of what could have changed recently?

@agriffard not sure, going to take a look now

ShellFeaturesManager.cs fixed.


Add mkdocs install & preview instructions to CONTRIBUTING.md

Move CONTRIBUTING.md to repo root
This is the typical location a CONTRIBUTING file is expected to be.

Add mkdocs install & preview instructions to CONTRIBUTING.md

needs a rebase

Needed a merge a week ago ;-)


WebExtension (v3.x) does not show local files as bookmarked

The WebExtension bookmarks API does not seem to support URL queries other than http/https, including local files (file:///). This is Firefox bug 1352835. A workaround of using the string search is mentioned, but that would not be exact, so LSR is currently not querying bookmarks for file: URLs.

Hello,
link-status-redux doesn't work with any of my bookmarks is this related with this issue ?
Thanks

No, bookmarked links on a web page should work. If you mean they don't work when hovering over bookmark sidebar/menu, then that is issue #6: WebExtensions do not have access to hover events outside of "normal" web pages.

Yes it's the issue #6. Thanks for the information.


Pass though environment variables

Adding this flag to sudo will pass existing environment variables to the executed CI command for example phpunit

Signed-off-by: George Steel<EMAIL_ADDRESS>


Description tunl0 did not obtain an IP address

Expected Behavior

Expect to add cluster new node, Calico everything works fine.
Current Behavior

Deploy kubernetes using kubeamd to add nodes to the cluster，The tunl0 NIC of the node does not obtain the IP address (based on the ifconfig command query result).
In normal cases, the cluster is successfully added and the calico-node automatically runs on the new node. The new node automatically obtains the tunl0 network. However, this is not currently the case, currently using calico version v3.23.2, using the yaml file, via "kubectl apply -f calico.yaml" command deployment

Calico version：v3.23.2
kubernetes version：1.24.3
Operating System and version: Centos 6.7     #Kernel version：4.20.3

In addition to the above information, is there any other information that needs to be provided? If you encounter the same problem next time, ensure the integrity of information collection.
At present, the problem is replaced by a lower version deployment, and the problem is solved. If you are unsure of the cause of the problem, repeating the operation later to see if the problem can be reproduced to find the real cause will help prevent it from happening.

请问你能提供

输出自calicoctl get ippools -o yaml
输出自calicoctl get felixconfig -o yaml
来自 calico-node pod 的日志
谢谢！

In addition to the above information, is there any other information that needs to be provided? If you encounter the same problem next time, ensure the integrity of information collection.
At present, the problem is replaced by a lower version deployment, and the problem is solved. If you are unsure of the cause of the problem, repeating the operation later to see if the problem can be reproduced to find the real cause will help prevent it from happening.

请问你能提供

输出自calicoctl get ippools -o yaml
输出自calicoctl get felixconfig -o yaml
来自 calico-node pod 的日志
谢谢！

In addition to the above information, is there any other information that needs to be provided? If you encounter the same problem next time, ensure the integrity of information collection.
At present, the problem is replaced by a lower version deployment, and the problem is solved. If you are unsure of the cause of the problem, repeating the operation later to see if the problem can be reproduced to find the real cause will help prevent it from happening.

kubectl -n kube-system describe  pod   calico-node-vx655
Events:
  Type     Reason     Age                    From     Message
  ----     ------     ----                   ----     -------
  Warning  Unhealthy  2m31s (x400 over 61m)  kubelet  (combined from similar events): Readiness probe failed: 2022-11-22 06:43:43.465 [INFO][20972] confd/health.go 180: Number of node(s) with BGP peering established = 0
calico/node is not ready: BIRD is not ready: BGP not established with <IP_ADDRESS>

kubectl -n kube-system  logs   -f calico-node-vx655
2022-11-22 05:43:55.148 [WARNING][102] felix/ipip_mgr.go 163: Failed to list interface addresses error=message too long
2022-11-22 05:43:55.148 [WARNING][102] felix/ipip_mgr.go 141: Failed to set tunnel device IP error=message too long
2022-11-22 05:43:55.148 [WARNING][102] felix/ipip_mgr.go 88: Failed configure IPIP tunnel device, retrying... error=message too long
2022-11-22 05:43:56.149 [WARNING][102] felix/ipip_mgr.go 163: Failed to list interface addresses error=message too long
2022-11-22 05:43:56.149 [WARNING][102] felix/ipip_mgr.go 141: Failed to set tunnel device IP error=message too long
2022-11-22 05:43:56.149 [WARNING][102] felix/ipip_mgr.go 88: Failed configure IPIP tunnel device, retrying... error=message too long
2022-11-22 05:43:57.150 [WARNING][102] felix/ipip_mgr.go 163: Failed to list interface addresses error=message too long
2022-11-22 05:43:57.150 [WARNING][102] felix/ipip_mgr.go 141: Failed to set tunnel device IP error=message too long
2022-11-22 05:43:57.150 [WARNING][102] felix/ipip_mgr.go 88: Failed configure IPIP tunnel device, retrying... error=message too long
2022-11-22 05:43:58.112 [INFO][102] felix/health.go 242: Overall health status changed newStatus=&health.HealthReport{Live:true, Ready:true, Detail:"+------------------+---------+----------------+-----------------+--------+\n|    COMPONENT     | TIMEOUT |    LIVENESS    |    READINESS    | DETAIL |\n+------------------+---------+----------------+-----------------+--------+\n| async_calc_graph | 20s     | reporting live | reporting ready |        |\n| felix-startup    | 0s      | reporting live | reporting ready |        |\n| int_dataplane    | 1m30s   | reporting live | reporting ready |        |\n+------------------+---------+----------------+-----------------+--------+"}
2022-11-22 05:43:58.152 [WARNING][102] felix/ipip_mgr.go 163: Failed to list interface addresses error=message too long
2022-11-22 05:43:58.152 [WARNING][102] felix/ipip_mgr.go 141: Failed to set tunnel device IP error=message too long
2022-11-22 05:43:58.152 [WARNING][102] felix/ipip_mgr.go 88: Failed configure IPIP tunnel device, retrying... error=message too long
2022-11-22 05:43:59.154 [WARNING][102] felix/ipip_mgr.go 163: Failed to list interface addresses error=message too long
2022-11-22 05:43:59.154 [WARNING][102] felix/ipip_mgr.go 141: Failed to set tunnel device IP error=message too long
2022-11-22 05:43:59.154 [WARNING][102] felix/ipip_mgr.go 88: Failed configure IPIP tunnel device, retrying... error=message too long

./calicoctl --allow-version-mismatch get ippools -o yaml
apiVersion: projectcalico.org/v3
items:
- apiVersion: projectcalico.org/v3
  kind: IPPool
  metadata:
    creationTimestamp: "2022-11-11T01:34:02Z"
    name: default-ipv4-ippool
    resourceVersion: "9950273"
    uid: f7b2020b-5ddd-414c-86de-8deaa555380d
  spec:
    allowedUses:
    - Workload
    - Tunnel
    blockSize: 26
    cidr: <IP_ADDRESS>/10
    ipipMode: Always
    natOutgoing: true
    nodeSelector: all()
    vxlanMode: Never
kind: IPPoolList
metadata:
  resourceVersion: "11801136"

./calicoctl --allow-version-mismatch get felixconfig -o yaml
apiVersion: projectcalico.org/v3
items:
- apiVersion: projectcalico.org/v3
  kind: FelixConfiguration
  metadata:
    creationTimestamp: "2022-11-11T01:34:02Z"
    name: default
    resourceVersion: "9950275"
    uid: 165888d4-9886-4f0d-937b-30ecbfca763d
  spec:
    bpfLogLevel: ""
    floatingIPs: Disabled
    logSeverityScreen: Info
    reportingInterval: 0s
kind: FelixConfigurationList
metadata:
  resourceVersion: "11801190"

Due to the large number of calico-node Pod logs, avoid incomplete logs and export text.
calico-node-vx655.log

From your logs I see this repeating over and over:
[WARNING][102] felix/ipip_mgr.go 163: Failed to list interface addresses error=message too long
2022-11-22 05:43:43.130 [WARNING][102] felix/ipip_mgr.go 141: Failed to set tunnel device IP error=message too long
2022-11-22 05:43:43.130 [WARNING][102] felix/ipip_mgr.go 88: Failed configure IPIP tunnel device, retrying... error=message too long

Which certainly seems like it might point to why your tunl0 interface is not getting an ip address assigned. I noticed in your execution of the commands that lwr20 asked for you used the --allow-version-mismatch flag. I can't help but suspect that the messaging error might have something to do with a version-skew issue between components. @caseydavenport or @fasaxc have you see anything like this before?

I noticed in your execution of the commands that lwr20 asked for you used the --allow-version-mismatch flag

Unlikely to be due to a mismatched version of calicoctl. I've seen another issue with this "message too long" error recently, I'm not sure what the root cause is though.

That error (EMSGSIZE) comes from netlink, looks like the error it returns if the message that we send is either too big or too small.  https://github.com/torvalds/linux/blob/master/net/nfc/netlink.c  Change/bug in the netlink library or kernel?

You say you're on CentOS 6.7 (released 2015, EOLed 2020) does this reproduce on a recent version?

Can reopen if also an issue on recent versions.

From your logs I see this repeating over and over:
[WARNING][102] felix/ipip_mgr.go 163: Failed to list interface addresses error=message too long
2022-11-22 05:43:43.130 [WARNING][102] felix/ipip_mgr.go 141: Failed to set tunnel device IP error=message too long
2022-11-22 05:43:43.130 [WARNING][102] felix/ipip_mgr.go 88: Failed configure IPIP tunnel device, retrying... error=message too long

Which certainly seems like it might point to why your tunl0 interface is not getting an ip address assigned. I noticed in your execution of the commands that lwr20 asked for you used the --allow-version-mismatch flag. I can't help but suspect that the messaging error might have something to do with a version-skew issue between components. @caseydavenport or @fasaxc have you see anything like this before?

Me too, keep getting this error, Is there a way to solve?

Me too, keep getting this error, Is there a way to solve?

fasaxc suggested it was a kernel issue.  What OS version are you running?  Do you see it on an OS which is not EOL?


Can you apply template to a template?

@adammertel : It would be a way of copying (duplicating) a template (and then editing it), if you think it is a good way - I am not sure it is. Other than that, no - it is better to make something "non-templatish" a template.

Thanks for a quick reply. I am sorry, I should have appended an example.
Imagine, you created a template "Person" with many many properties and you like it. Then you realize, you want to use this template for creating the template "Person:Woman" or "Person:Monk" where a few properties will be changed / added ....
But yes, duplicating a template is basically the same as applying a template to a template.
In general, I have no strong opinion on this.

@adammertel : I think the better way to create a template from a non-template is to duplicate the entity I like, edit it a little bit, and tag it as template. But it is probably simpler to allow "apply template" without exception. The crucial question is, what "apply template" does with existing stuff, i.e. how does it add to / overwrite what is there. This is more important, and it will also help me answer whether "apply template to template" should be allowed.


Allow mutliple threads/cores per workflow in agent

Clear and concise description of the problem
It is possible to increase the number of workflows that run in parallel by increasing WOODPECKER_MAX_WORKFLOWS. However it seems like each workflow only gets a single CPU core/thread. I haven't confirmed this, but I did see that cargo was using only a single thread.
Suggested solution
It would be nice if we could increase the number of threads that each workflow gets. Workflows that can take advantage of many cores would benefit from this. For example, cargo will spawn multiple threads to compile things in parallel, which greatly speeds up compilation.
This should be configurable through an environment variable like WOODPECKER_MAX_THREADS_PER_WORKFLOW.
Alternative
Using multi-pipelines does allow multiple pipelines to run in parallel, which is amazing but not enough as steps like compiling one package can't be broken into multiple pipelines.
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

It looks like the code already supports (anong others) these config on a pipeline step:

cpu_quota
cpuset
cpu_shares

https://github.com/woodpecker-ci/woodpecker/blob/a884e13885b9519c6c7bf7f6e41a2f177207b50d/pipeline/frontend/yaml/container.go#L31-L34
See here for the meaning: https://docs.docker.com/config/containers/resource_constraints/#cpu
Can you try if this solves your problem.
As these are not documented ,use at your own risk

I don't have any limits placed on the agent though. It seems like the agent is placing limits on the containers it spawns. Is there a configuration for that?

Have you tried to put this into your pipeline configuration on the step / container you want more CPU?
The code says you can do something like this:
   -name: Run on more CPU
    image: debian
    cpu_shares: 100000
    commands:
     - ...

These should be the settings used by the agent to start the container, but i only started to understand the code.

re

It looks like the code already supports (anong others) these config on a pipeline step:
* cpu_quota

* cpuset

* cpu_shares

https://github.com/woodpecker-ci/woodpecker/blob/a884e13885b9519c6c7bf7f6e41a2f177207b50d/pipeline/frontend/yaml/container.go#L31-L34
See here for the meaning: https://docs.docker.com/config/containers/resource_constraints/#cpu
Can you try if this solves your problem.
As these are not documented ,use at your own risk

reminder: if it's not documented, it's a "feature" that can be refactored away at any time ... if it does get in the way ... until its officially added to the docs

how to handle resources ... is a bigger topic ..., ideas are welcome but I personally consider other issues more important for now :sweat:


opencv-python version mismatch between wild-visual-navigation and stego

Hi guys! First of all, thank you for the great work.
I am following the docker setup instructions on a 20.04 Noetic machine. Everything appears to work fine during the build and first setup, except this error that pops up:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. wild-visual-navigation 0.0.1 requires opencv-python==<IP_ADDRESS>, but you have opencv-python <IP_ADDRESS> which is incompatible.
If, instead, I try to force the installation of <IP_ADDRESS>, then I receive a similar error complaining that stego requires >= 4.6.
Am I doing something wrong or is there something wrong in the setup files?
Thanks in advance!

Hi Afonso, thanks for your interest in our paper!
We're a bit busy at the moment, but I can take a look early next week if that works. I agree that there could be a dependency mismatch that we oversaw. Pinning the versions might solve it but I'll need to test it to see if we need to propagate corrections to other repos.
I hope that works, but let me know if you are in a rush

Hi @AfonsoEloy , I just pushed a minor fix in the self_supervised_segmentation repo to relax the opencv version, which was set to >=4.6. I tested it locally on my laptop and it works as intended, let me know if the problem persists.

Hi @mmattamala. Your fix solved the issue, thanks! Final set of questions:

Is the docker container as-is suitable to run WVN with a dataset of real data, or only for the simulation demo?
The datasets we are collecting only have images from a single RGB-D front-facing camera (realsense d435i). Considering I see multiple front and rear cameras being referenced in your config files, can the system work with only one?
Aside from the images, are there any mandatory inputs that must come from a specific platform like ANYmal, or do other legged robots work (such as the Unitree Go1 EDU, which we are using).

Awesome, glad to know it worked. Regarding your questions:

The docker container should work with real data too, unless there are specific packages and dependencies required by your data (e.g., message definitions). I should have added a devcontainer config file to make the development easier (so you work with VSCode within the container, but I learned this after I prepared this docker). I could do it next week if you think it might help you
That's absolutely possible and it's actually the configuration we used for our RSS paper. The multi-camera feature was added in our extended paper but it still processes one camera at a time
If you inspect the Jackal simulation example more closely, it only requires the image, tf data with an odometry source (to generate the supervision signal via the reprojected path), and a velocity command. We did not use any raw proprioceptive signal (e.g., IMU or joint encoders). Jonas has a follow up paper using proprioception to estimate physical terrain properties: https://leggedrobotics.github.io/identifying_terrain_physical_parameters_webpage/

Don't worry about the devcontainer, I can manage without it. I'll spend the next few days working on integrating your system with our data. Your help has been incredibly valuable -- thank you!

Awesome, you're welcome! I look forward to seeing how WVN works with your system :)
I'll close the issue for now but feel free to reopen it if new problems arise.


Update helper.rb for minitest current version.

require minitest/autorun
Minitest.autorun

I'm closing out old PRs as part of #283 . I'm sorry I was never able to help get this to a point to be merged.


Request for trained model

Can you provide the trained RivaGan model (.pt)?

+1

+1

We can get the model in onnx format in here


Crashing node-red

When network is not available  it's crashing node-red process
node-red 0.17.5
node-red-contrib-blynk-ws 0.5.0
node --version
v6.14.1
Apr 15 12:06:52 lmc Node-RED[2054]: 15 Apr 12:06:52 - [error] [blynk-ws-client:Magellanic Clouds] Websocket error: Error: getaddrinfo ENOTFOU
ND blynk-cloud.com blynk-cloud.com:9443
Apr 15 12:06:52 lmc Node-RED[2054]: 15 Apr 12:06:52 - [info] [blynk-ws-client:Magellanic Clouds] Connection closed: wss://blynk-cloud.com:944
3/websockets
Apr 15 12:06:52 lmc Node-RED[2054]: 15 Apr 12:06:52 - [error] [blynk-ws-client:lmc wemos thermo] Websocket error: Error: getaddrinfo ENOTFOUN
D blynk-cloud.com blynk-cloud.com:9443
Apr 15 12:06:52 lmc Node-RED[2054]: 15 Apr 12:06:52 - [red] Uncaught Exception:
Apr 15 12:06:52 lmc Node-RED[2054]: 15 Apr 12:06:52 - Error: Uncaught, unspecified "error" event. (undefined)
Apr 15 12:06:52 lmc Node-RED[2054]:     at BlynkClientNode.emit (events.js:163:17)
Apr 15 12:06:52 lmc Node-RED[2054]:     at WebSocket.<anonymous> (/usr/lib/node_modules/node-red-contrib-blynk-ws/nodes/blynk-ws-client.js:42
8:10)
Apr 15 12:06:52 lmc Node-RED[2054]:     at emitOne (events.js:96:13)
Apr 15 12:06:52 lmc Node-RED[2054]:     at WebSocket.emit (events.js:188:7)
Apr 15 12:06:52 lmc Node-RED[2054]:     at ClientRequest.req.on (/usr/lib/node_modules/node-red-contrib-blynk-ws/node_modules/ws/lib/websocke
t.js:535:10)
Apr 15 12:06:52 lmc Node-RED[2054]:     at emitOne (events.js:96:13)
Apr 15 12:06:52 lmc Node-RED[2054]:     at ClientRequest.emit (events.js:188:7)
Apr 15 12:06:52 lmc Node-RED[2054]:     at TLSSocket.socketErrorListener (_http_client.js:310:9)
Apr 15 12:06:52 lmc Node-RED[2054]:     at emitOne (events.js:96:13)
Apr 15 12:06:52 lmc Node-RED[2054]:     at TLSSocket.emit (events.js:188:7)
Apr 15 12:06:52 lmc Node-RED[2054]:     at connectErrorNT (net.js:1040:8)
Apr 15 12:06:52 lmc Node-RED[2054]:     at _combinedTickCallback (internal/process/next_tick.js:80:11)
Apr 15 12:06:52 lmc Node-RED[2054]:     at process._tickCallback (internal/process/next_tick.js:104:9)
Apr 15 12:06:52 lmc systemd[1]: nodered.service: Main process exited, code=exited, status=1/FAILURE

Hi,
this not append on node-red 0.18.4 and node 8.9.4, which what version of Websocket module are you using?

Test on my live system Rpi3 with node-red 0.17.5 - node 6.14.1 - websocket 5.1.1
16 Apr 08:21:32 - [info] [blynk-ws-client:uno] ping
16 Apr 08:21:32 - [info] [blynk-ws-client:uno] SEND -> Cmd: PING, Id: 5603, len: 0, data: ""
16 Apr 08:21:41 - [info] [blynk-ws-client:uno] Connection closed: ws://blynk-cloud.com/websockets
16 Apr 08:21:46 - [info] [blynk-ws-client:uno] Start connection: ws://blynk-cloud.com/websockets
16 Apr 08:21:46 - [info] [blynk-ws-client:uno] login -> ***************************b94d0
16 Apr 08:21:46 - [info] [blynk-ws-client:uno] SEND -> Cmd: LOGIN, Id: 1, len: 32, data: "***************************b94d0"
16 Apr 08:21:46 - [info] [blynk-ws-client:uno] RECV <- Cmd: RSP, Id: 1, responseCode: OK
16 Apr 08:21:46 - [info] [blynk-ws-client:uno] Client logged
16 Apr 08:21:46 - [info] [blynk-ws-client:uno] SEND -> Cmd: INTERNAL, Id: 5605, len: 82, data: "ver|0.5.2|h-beat|10|buff-in|32767|dev|node-red|con|Blynk-ws|build|0.5.0 2018-04-14"
16 Apr 08:21:46 - [info] [blynk-ws-client:uno] RECV <- Cmd: RSP, Id: 5605, responseCode: OK
16 Apr 08:21:52 - [info] [blynk-ws-client:uno] ping
16 Apr 08:21:52 - [info] [blynk-ws-client:uno] SEND -> Cmd: PING, Id: 5607, len: 0, data: ""

maybe you can try going to the node-red-contrib-blynk-ws folder, then delete the node_modules folder and do a npm install that should download the updated dependency modules.
let me know!!


The packaged version doesn't read PATH

Extracting @alebcay's comment as a separate issue.
I'm also getting some other weird stuff with ls coloring and formatting. This is what I get when I run it through gulp - everything works the way it should:

but then, when I do npm run package and run it from the standalone app bundle, I get this:

It seems that the gulp version is reading my path - which ls returns my ls that I installed from MacPorts. However, the standalone doesn't seem to do that, and is instead using /bin/ls. Even so, I still can't figure out why it's only outputting the first line out output with /bin/ls (it only shows "Applications", nothing else).

We can use this tool. https://github.com/sindresorhus/fix-path


Feature/fix pydataprovider multiple obj bugs

Try to fix issue #436 and add unittest.

@QiJune Before you format python code, please check in this PR.

Coverage remained the same at 62.888% when pulling 4607d517bfba481cbb02b2beb1dfa3773eadfded on reyoung:feature/fix_pydataprovider_multiple_obj_bugs into 3fc338ad12b9ef3cc7743de967f04d772231248d on baidu:develop.


Removed unknown postcode

This postcode is unknown according to https://www.royalmail.com/find-a-postcode

Imo, it would be really helpful to add an expiration-date of fake information.
So you can generate fake information for items, which where created in a specific timespan (e.g. an purchase order)

thanks!


Fix: S3 ACL analysis rule for WRITE permissions never triggers

The S3 ACL analysis rule for WRITE permissions granted by an ACL can never trigger because of an invalid query statement. The query checks that acl.ownerid = acl.granteeid but acl.uri and acl.granteeid are mutually exclusive as per https://github.com/lyft/cartography/blob/f613c32959f4bbdab53f83b2a03532c62e180e8d/cartography/intel/aws/s3.py#L554-L578 So the "WRITE" rule would never trigger. And as these rules are all about detecting anonymous access permissions, there shouldn't be any clauses checking that the grantee is the owner.
Furthermore, as per AWS' documentation, the WRITE permission allows the s3:PutObject action, so that should be added to anonymous_actions. (s3:DeleteObjectVersion is only ever granted to bucket owners.)
For the "READ_ACP" rule the granted anonymous actions are incorrect.

Hi @achantavy, do you mind taking a look at this please? This is a second issue I found while reviewing S3 access control related features in Cartography. We've fixed this in our local copy of Cartography, but I would like to see this merged upstream as well so we don't have to maintain this patch on our end. Thx.

Hey @jhecking, thanks for the PR and sorry it took so long to review. Your write-up and changes make sense. Analysis jobs scare me a bit in that we don't have test coverage on them so I took some time to add them here.
I tried to fetch your branch and add tests to this PR but I messed up my git commands and it didn't work the way I thought -oops. So, I'm going to close this one and open https://github.com/lyft/cartography/pull/1244. You'll still get the credit in the commit history as a coauthor. Thanks again for the PR.


New versions don't work on "Windows 7"

The last version that works well with Windows 7 is 24.06.2019.
The new 1.1.2 version runs but the animation when a task is removed is wrong.
The new 1.1.3, 1.1.4 versions don't start by anyway.

@ChrisAnd1998 I can confirm the "animation doesn't change with options" issue Chris. Only "none" seem to be applied, everything else is one style.
Furthermore, when the computer boots up, there is an instance of FalconX visible in the Alt + Tab programs which you have to close. I have been reluctant to open separate issues for this since I'm not running the latest version, but if you prefer me to I can.

@froilson Does it work now with version 01.08.2019 ?
@user00101010 Its's better to use the latest version alot has been fixed the past few updates.

Hi, now with the las version, 01.08.2019 <IP_ADDRESS> is working but the animation is not working well because when remove or add an app, the animation starts whit all the icons at the original position, close to the start button, and then animate to the center position.

I test the new version 25.08.2019 <IP_ADDRESS> and the same issue is occurred I told in previous comment.

Hi froilson can you download this Pre-Release <IP_ADDRESS> and see if its fixed?
https://chrisandriessen.nl/web/downloads/falconx/Pre-Release/Pre-Release <IP_ADDRESS>.zip

Sorry, but unfortunately I'm on holidays till October first.
When I come back I try to test your pre-release asap.
Thanks
El sáb., 21 sept. 2019 13:08, Chris Andriessen<EMAIL_ADDRESS>escribió:

Hi froilson can you download this Pre-Release <IP_ADDRESS> and see if its fixed?
https://chrisandriessen.nl/web/downloads/falconx/Pre-Release/Pre-Release <IP_ADDRESS>.zip
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ChrisAnd1998/FalconX/issues/11?email_source=notifications&email_token=ADGXOZX7HDYRCYAKX2IDCEDQKXXC5A5CNFSM4IFN7XB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IOZMQ#issuecomment-533785778,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADGXOZQZ5EWDLFREE5JBWULQKXXC5ANCNFSM4IFN7XBQ
.

No problem 😁,
I'll be waiting.
Have a nice holiday!
On Mon, Sep 23, 2019, 2:27 PM froilson<EMAIL_ADDRESS>wrote:

Sorry, but unfortunately I'm on holidays till October first.
When I come back I try to test your pre-release asap.
Thanks
El sáb., 21 sept. 2019 13:08, Chris Andriessen<EMAIL_ADDRESS>escribió:

Hi froilson can you download this Pre-Release <IP_ADDRESS> and see if its
fixed?

https://chrisandriessen.nl/web/downloads/falconx/Pre-Release/Pre-Release <IP_ADDRESS>.zip

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/ChrisAnd1998/FalconX/issues/11?email_source=notifications&email_token=ADGXOZX7HDYRCYAKX2IDCEDQKXXC5A5CNFSM4IFN7XB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IOZMQ#issuecomment-533785778
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ADGXOZQZ5EWDLFREE5JBWULQKXXC5ANCNFSM4IFN7XBQ
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ChrisAnd1998/FalconX/issues/11?email_source=notifications&email_token=AMAZYT4FJIX6DPDQVXXGF2DQLCY4HA5CNFSM4IFN7XB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7KV3PY#issuecomment-534076863,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMAZYT46XHAKKDLN3QEVLLTQLCY4HANCNFSM4IFN7XBQ
.

Hello, can't download the file, when enter the URL in browser then
redirects me to your home page.
El lun., 23 sept. 2019 14:50, Chris Andriessen<EMAIL_ADDRESS>escribió:

No problem 😁,
I'll be waiting.
Have a nice holiday!
On Mon, Sep 23, 2019, 2:27 PM froilson<EMAIL_ADDRESS>wrote:

Sorry, but unfortunately I'm on holidays till October first.
When I come back I try to test your pre-release asap.
Thanks
El sáb., 21 sept. 2019 13:08, Chris Andriessen<EMAIL_ADDRESS>escribió:

Hi froilson can you download this Pre-Release <IP_ADDRESS> and see if its
fixed?

https://chrisandriessen.nl/web/downloads/falconx/Pre-Release/Pre-Release <IP_ADDRESS>.zip

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<

https://github.com/ChrisAnd1998/FalconX/issues/11?email_source=notifications&email_token=ADGXOZX7HDYRCYAKX2IDCEDQKXXC5A5CNFSM4IFN7XB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IOZMQ#issuecomment-533785778

,
or mute the thread
<

https://github.com/notifications/unsubscribe-auth/ADGXOZQZ5EWDLFREE5JBWULQKXXC5ANCNFSM4IFN7XBQ

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/ChrisAnd1998/FalconX/issues/11?email_source=notifications&email_token=AMAZYT4FJIX6DPDQVXXGF2DQLCY4HA5CNFSM4IFN7XB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7KV3PY#issuecomment-534076863
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AMAZYT46XHAKKDLN3QEVLLTQLCY4HANCNFSM4IFN7XBQ
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ChrisAnd1998/FalconX/issues/11?email_source=notifications&email_token=ADGXOZVZWDYSVRKKCCLJNT3QLC3QJA5CNFSM4IFN7XB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7KXU2Q#issuecomment-534084202,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADGXOZXV6S3MD6KG55XWO7LQLC3QJANCNFSM4IFN7XBQ
.

Well i created a virtual machine with Windows 7 and the bug is still there. I am currently looking through the older builds to find out why it's happening. Thank you very much for taking the time to test it out 😁. Those fixes i tried are currently in the latest stable build but, i can confirm it doesn't work 😓. I'll keep you updated when i find a proper fix.

Sadly i can't fix this due to some differences with the taskbar in Windows 7 and 10. Making it work for Windows 7 will require me to remove the fixes i made for Windows 10. For now i will be focusing on Windows 10 until FalconX is finished. After that i may decide to make a sepperate version for Windows 7.


[PKO-169] Move repo_test.go to integration tests

Summary
JIRA Task
Existing issues

repo_test.go was included as unit test but is in fact an integration test because it tries to connect to an external registry (originally quay.io).
the test could produce different results if the user running it was logged or not to quay.io.

What this PR does

Move repo_test.go under integration tests.
Configure repo_test.go to use the KinD internal registry (that we already configure) instead of quay.io.
Expand the internal registry configuration adding a proxy that enables authentication, while keeping the old usage intact (localhost:5001 still points to the plain registry, localhost:5002 points to the authenticated registry via proxy). This allows to test unauthenticated access.

Out of scope

repo_test.go is written with the standard test structure, while other tests in integration/kubectl-package uses the ginkgo library. Translating repo_test.go to run with ginkgo is out of scope for this PR. The test is working properly and the translation can be done in a separate task to make reviewing easier.

Change Type

Bug Fix

Check List Before Merging

[x] This PR passes all pre-commit hook validations.
[x] This PR is fully tested and regression tests are included.
[ ] Relevant documentation has been updated.
[ ] The commits in this PR follow the Conventional Commits
standard.

Additional Information

Hey @kostola,
I tried to authenticate to the registry proxy and got the following error:
$ ./.cache/deps/bin/crane auth login localhost:5002 -u registry -p foobar
Error: error storing credentials - err: exit status 1, out: `error storing credentials - err: exit status 1, out: `pass not initialized: exit status 1: Error: password store is empty. Try "pass init".``

Does it work for you?

Hey @kostola, I tried to authenticate to the registry proxy and got the following error:
$ ./.cache/deps/bin/crane auth login localhost:5002 -u registry -p foobar
Error: error storing credentials - err: exit status 1, out: `error storing credentials - err: exit status 1, out: `pass not initialized: exit status 1: Error: password store is empty. Try "pass init".``

Does it work for you?

@pbabic-redhat This works for me:
$ podman login --tls-verify=false localhost:5002 -u registry -p foobar
Login Succeeded!

Yours looks like an error with some password store, rather than the login itself.

@pbabic-redhat your command works as well for me:
$ .cache/deps/bin/crane auth login localhost:5002 -u registry -p foobar
2024/12/06 09:58:22 logged in via ~/.docker/config.json

imho this is another hint it's a problem with your password store


path/filepath: path traversal in filepath.Clean on Windows (CVE-2022-41722)

On Windows, the filepath.Clean function could transform an invalid path such as a/../c:/b into the valid path c:\b. This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack. The filepath.Clean function will now transform this path into the relative (but still invalid) path .\c:\b.
Thanks to RyotaK (https://ryotak.net/) for reporting this issue.
This is a PRIVATE issue for CVE-2022-41722, tracked in http://b/261991454 and fixed by http://tg/1675249.

@gopherbot please open backport issues. This is a security fix.

@gopherbot Please backport to 1.20.

How is this "for Windows"? Do you mean when cleaning Windows path names?

Yes. This vulnerability only exists when running with GOOS=windows, in which case the path/filepath package operates on Windows path names.


Implement Travis CI and other build / quality autoamtion

Would be really nice to have:

Travis CI to replace our old Gitlab CI
Coveralls or similar for code coverage

Travis CI implemented

Implemented CodeClimate for code coverage and code quality checks


Pi aggregation circuit

Description
[PR description]
Issue Link
[link issue here]
Type of change

[ ] 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

Contents

[item]

Rationale
[design decisions and extended information]
How Has This Been Tested?
[explanation]

How to fill a PR description
Please give a concise description of your PR.
The target readers could be future developers, reviewers, and auditors. By reading your description, they should easily understand the changes proposed in this pull request.
MUST: Reference the issue to resolve
Single responsability
Is RECOMMENDED to create single responsibility commits, but not mandatory.
Anyway, you MUST enumerate the changes in a unitary way, e.g.
This PR contains:
- Cleanup of xxxx, yyyy
- Changed xxxx to yyyy in order to bla bla
- Added xxxx function to ...
- Refactored ....

Design choices
RECOMMENDED to:

What types of design choices did you face?
What decisions you have made?
Any valuable information that could help reviewers to think critically

is the chunk here (ChunkPublicData, each corresponds to a chunk with max_txn transactions) same as chunk for keccak hash inputs (1788=1088 bits for each chunk)? I think each chunk has 300 Keccak rows but a hash may have 300*num_chunk rows?

is the chunk here (ChunkPublicData, each corresponds to a chunk with max_txn transactions) same as chunk for keccak hash inputs (17 * 8 * 8=1088 bits for each chunk)? I think each chunk has 300 Keccak rows but a hash may have 300 * num_chunk rows?

Thanks for spotting this. It is fixed with f4082a2e973835dbd09717e062b24ba2f5af56ce

Thanks for spotting this. It is fixed with f4082a2, with your idea of using is_final cell

Great! I'll take a careful look. For the hardcoded 300, I think it may not be seriously hard to change to parameter-dependent. In general this 300 is replaced by NUM_ROWS_PER_ROUND * 25 (24+1 which is never changed in Keccak). Also, the hash output is always at row[last]. The only problem might be with the hash input, which currently we put at row[6]. When the num of lookup bits change, the word split and transform modules in keccak codebase may incur this 6 to be changed in a little complicated way.


Add support for zstd encoder

Describe the solution you'd like
Currently SWS only supports brotli, deflate, and gzip. The async_compression library has support for zstd which would be beneficial when SWS is used in combination with other Rust tools, Ex. Vector.dev
https://docs.rs/async-compression/latest/async_compression/#compression-algorithm

Just out of curiosity. Can you please elaborate a bit more about what's your use case for zstd as a new content encoding?

@joseluisq Adding zstd as a content encoder can lead to faster load times, improved user experience, reduced bandwidth costs, and increased energy efficiency. These benefits make zstd an excellent choice for modern web services looking to optimize their performance and deliver the best possible experience to users.
There's several study cases explaining how zstd is used on service to service communications to reduce network i/o usage compared to gzip/brotli
Sources:

https://aws.amazon.com/blogs/containers/reducing-aws-fargate-startup-times-with-zstd-compressed-container-images/
https://docs.aws.amazon.com/athena/latest/ug/compression-support-zstd-levels.html
https://engineering.fb.com/2018/12/19/core-data/zstandard/
http://www.bioinformaticszen.com/post/use-zstd-for-raw-fastq/
https://daniel.haxx.se/blog/2020/08/19/curl-7-72-0-more-compression/

I'm currently using Caddy 2 to serve static content with zstd encoding. For some use cases using something like SWS would be ideal, even more if I could serve the content using zstd.

Ok, I got it.
Then, I think it can be used for backend-to-backend communication and backend-to-native-mobile/desktop apps.
I also saw that the QUIC protocol is including support for zstd (maybe browsers someday too).
Since Zstd looks can provide a good balance between compression ratio and decompression speed so why not.
Also noting that we could add on-the-fly zstd compression and pre-compressed file serving in a similar way to how is done for gzip/brotli actually.

@joseluisq It's slowly starting to get added everywhere. There's an issue open to add support for zstd in Firefox.
Browser tester: https://www.daniel.priv.no/tools/zstd-browser-test/

Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1301878
Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=1246971

Also, I recently noted that the Zstandard compression format for Content-Encoding positions has already started for major browsers. So it looks like the zstd adoption continues growing.

Firefox: https://github.com/mozilla/standards-positions/issues/775
WebKit: https://github.com/WebKit/standards-positions/issues/168
Chrome: Interested and under evaluation

Done. Check out PR #197 tests to know what it looks like.

@joseluisq Thank you, looking forward to testing this out!


Consider "clone-and-run" workflow

via @harperj in #22:

[...] The fact that it's called "moneybot" kind of implies (like the other bots we have used) it should run and do something cool with minimal changes. [...] This leaves us with something we want to both run as a CLI app that "just works" and also a library that is easy to use to write strategies. I don't have a specific answer here yet but I don't think it would be ideal to move the project much further from "clone and run".

Right now, the README (and project) is more oriented toward library use. For example, the README tells you how to run the tests before it tells you how to live-trade. (Arguably, the test instructions should be in CONTRIBUTING.md).
The README, and potentially other parts of the project, could lend themselves better to the "clone-and-run" scenario, in which CLI ("bot") functionality is the main use-case.
Of course, our library is also a library with backtesting. So, we should consider how to play these two sides of moneybot.
Off the top of my head: perhaps we could explain how to run the CLI, and what it does by default. In explaining, we can show the strategy a bit. From there, it's not hard to explain how one might make, backtest, and ultimately trade with novel strategies.
Thoughts?

A lot has happened since this issue was open. Now that Postgres makes installation a lot easier, I am assuming this issue is closed. We can re-open if we get lots of confused first-time users.


Can not analyze symbols with Chinese

Can not analyze the Chinese function name, variable name, please add the analysis of Chinese function name and variable name support.
Luajit can support gbk or utf8 Chinese function name and variable name.
example
`
function 中文函数名(参数1,参数2)
local 中文变量 = "Chinese variable name"
end

PUC Lua doesn't accept this code:
$ lua5.3
Lua 5.3.3  Copyright (C) 1994-2016 Lua.org, PUC-Rio
> function 中文函数名(参数1,参数2) end
stdin:1: <name> expected near '<\228>'

$ lua5.2
Lua 5.2.4  Copyright (C) 1994-2015 Lua.org, PUC-Rio
> function 中文函数名(参数1,参数2) end
stdin:1: <name> expected near char(228)

$ lua5.1
Lua 5.1.5  Copyright (C) 1994-2012 Lua.org, PUC-Rio
> function 中文函数名(参数1,参数2) end
stdin:1: '<name>' expected near '�'

Aparently LuaJIT allows any octet ≥ 128 inside identifiers. (The documentation only says 'UTF-8' characters are supported, but nothing actually checks the encoding for validity, and a comment in the source code suggests that other encodings are meant to be supported as well.) That at least makes it simple to implement; I worried we might have to import the Unicode character database to check character properties or something.
Well, sort of simple, because we parse Lua source code at the level of code points, not bytes, which brings back the conundrum I've had with interpreting string literals...
Given that it's an extension from PUC Lua, I'll probably implement this, but it will require being explicitly enabled by the user, like with the luaVersion option. Please note that this is not full LuaJIT support. For example, LuaJIT will accept code like this, unless LUAJIT_ENABLE_LUA52COMPAT is defined when compiling:
goto skip
local goto = print
goto "hello"
::skip::

Supporting code like this might be too tricky to be worth it, so I explicitly don't promise that.

Implemented in<PHONE_NUMBER>2a771e588a6c0ca2c70d3db7f9f254. Consider it unstable, however. I might still revisit the encoding issue.

That at least makes it simple to implement; I worried we might have to import the Unicode character database to check character properties or something.

I was able to convert a UnicodeData.txt into a lightweight 2MB string map of general categories recently. It's something like 'çççççççççççççççççAAAAAA'.
There's also the UnicodeSet tool for that, but it outputs a pattern-like set instead, with range elements. Range checking is generally slower than indexing into a string literal map.

I already wrote this is unnecessary. There's no need to check category codes at all; the LuaJIT parser doesn't work with Unicode characters anyway. The real issue is that luaparse does work with Unicode characters (given that JavaScript has no portable and expedient bytestring type), which causes problems here and in a couple other places.

@fstirlitz Well, you're kinda rudde.

Oops, I meant...  I remember that.

I read your post and I didn't try to help you, was just showing you I've done it and I'm able to.

Well, good for you. But with respect to this issue report, it's off-topic. If you want to demonstrate your programming prowess to your peers, there are plenty of forums meant for that purpose. This is not one of them.


Monitoring - some graphs are missing in RKE cluster

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

run Rancher v2.3.5 or master-head
add a DO cluster

K8s: v1.17.2
OS of nodes: Ubuntu 16.04.6 LTS

enable the cluster monitoring (0.0.7)
check requests sent to Rancher server for metrics data

Result:

one new graph is added to the section etcd metrics

etcd-peer-traffic

the following 3 metrics are missing in the section Kubernetes component metrics

    "apiserver-request-count",
    "scheduler-e-2-e-scheduling-latency-seconds-quantile",
    "apiserver-request-latency",

This issue is also seen in a custom RKE cluster using SUSE
k8s: v1.17.2
OS: SUSE Linux Enterprise Server 12 SP5

the following 3 metrics are missing in the section Kubernetes component metrics

 "apiserver-request-count"
 "scheduler-e-2-e-scheduling-latency-seconds-quantile"
 "apiserver-request-latency"

https://kubernetes.io/docs/setup/release/notes/#deprecated-changed-metrics
Some of the metrics used in these graphs has been turned off in k8s 1.17.
apiserver-request-count & apiserver-request-latency

Based on @daxmc99's comment, it seems as if these graphs are intentionally no longer available with k8s 1.17


Remove unused property.

Codecov Report

Merging #925 into master will decrease coverage by 1.74%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #925      +/-   ##
==========================================
- Coverage   94.45%   92.71%   -1.75%
==========================================
  Files          34       34
  Lines        6369     6366       -3
==========================================
- Hits         6016     5902     -114
- Misses        353      464     +111

Impacted Files
Coverage Δ

databricks/koalas/series.py
95.59% <ø> (+0.13%)
:arrow_up:

databricks/koalas/usage_logging/__init__.py
24.54% <0%> (-72.73%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
75.6% <0%> (-9.76%)
:arrow_down:

databricks/conftest.py
91.48% <0%> (-6.39%)
:arrow_down:

databricks/koalas/frame.py
95.43% <0%> (-0.61%)
:arrow_down:

databricks/koalas/generic.py
95.07% <0%> (-0.5%)
:arrow_down:

databricks/koalas/plot.py
94.04% <0%> (-0.24%)
:arrow_down:

databricks/koalas/groupby.py
91.18% <0%> (-0.21%)
:arrow_down:

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 8367c93...01aed58. Read the comment docs.

I'd merge this for now.


Include the option to also remove the Intune object

Currently our Entra ID joined, Intune managed AVD session hosts are cleaned up only in Entra ID. I also would like to have an option to also delete the object in Intune.

https://github.com/Azure/AVDSessionHostReplacer/pull/11
Added fix, Submitted pull request above to Willy.

In my testing I only needed to clean the object in Entra ID, and creating a new device with same name works. Why do we need to delete it in Intune?

Strange, because in my Intune tenant I see lots of duplicate device records in Intune

Added in v.0.2.8


Bug: For Certain user Storybook block doesn't properly work, if there is "/" instead of "//" before "iframe" in the URL

Issue
For Certain user Storybook block doesn't properly work, if there is / instead of // before iframe in the URL. It is an issue, because Storybook generates URL with / before iframe. The issue presents only on their WS, checked on my personal WSs - works fine with both URLs.
Scenario
Issue can be reproduced following this exact scenario below:

Go to https://cloud.supernova.io/
Impersonate<EMAIL_ADDRESS>Go to Docs tab
Add Storybook block with URL provided in Additional information

Expected result
As a user, I expect, that default Storybook link will work.
Additional information
URL: https://storybook.global.ssl.fastly.net/iframe.html?id=6·components-card--card&args&viewMode=story&full=1&addons=0&stories=0&panel=false&nav=false
User<EMAIL_ADDRESS>WS:  https://cloud.supernova.io/ws/component-library/ds/18045-my-design-system/latest/content/17944-default/resources/fonts

Versions used

Up-to-date https://cloud.supernova.io/.
Documentation Exporter version 2.0.1.
OS: macOS Monterey 12.1 (21C52).

  Helpdesk Information   ● Linked with helpdesk ticket: 116

@Ydus @artufimtcev FYI

I've reproduced this issue somehow, seems like this is some problem tied up with focus of Storybook block.
In my case when I was trying to paste Storybook url in block field it created new Storybook block with broken link like in example above instead of pasting url.


add airspeed velocity config and performance tests

This pull request adds configuration and test files for the airspeed velocity performance benchmarking tool.
This is new to me, but I'm putting it up here for feedback. I developed this while benchmarking #528 and #529. It seems useful. I'm not sure what the standard should be for merging this.
@mikofski do you have any experience using asv or similar tools? Anyone else?
In the long run, it would be ideal to set up a cloud service to automatically run these tests on the same (possibly virtual) hardware each time. As of now, I only want to consider running these tests locally.

[x] Closes #419
[x] I am familiar with the contributing guidelines.
[ ] Fully tested. Added and/or modified tests to ensure correct behavior for all reasonable inputs. Tests (usually) must pass on the TravisCI and Appveyor testing services.
[x] Updates entries to docs/sphinx/source/api.rst for API changes.
[x] Adds description and name entries in the appropriate docs/sphinx/source/whatsnew file for all changes.
[ ] Code quality and style is sufficient. Passes git diff upstream/master -u -- "*.py" | flake8 --diff
[ ] New code is fully documented. Includes sphinx/numpydoc compliant docstrings and comments in the code where necessary.
[ ] Pull request is nearly complete and ready for detailed review.

other:

[x] add a simple readme like scipy's -- rely on asv's documentation for all but the most basic commands and instructions
[ ] consider benchmarks/benchmarks rather than asv_bench/benchmarks (copied from xarray)

Airspeed velocity (asv) is used in SciPy, I had to use it to create a benchmark for the vectorized Newton PR, but that's my only experience, seems useful but not sure if there's any standard on benchmarks

closing in favor of https://github.com/pvlib/pvlib-python/pull/1049


Fix false positive for multi dep single use statements

Resolves #91
This also resolves some false detections of not_my_dep::my_dep_name::stuff_in_my_dep 😊 I couldn't find a way to avoid detection of futures in with the single line regexp
pub use {
    async_trait::{mod1, dep2},
    not_futures::{
        futures::{futures_mod1, futures_mod2::{futures_mod21, futures_mod22}}
    },
    reqwest,
};

This update does come at a small performance downside (that might be resolved by not instantiating a regexp per dependency?). On our repo of ~500k lines of machete goes from ~45s user time to ~48s of user time.

Hi @bnjbvr ,
Sorry for the delay, I missed your comments 😞 I've addressed them and added a .rustfmt.toml that seems to mostly fit with your expectations in order for other contributors to follow your lint rules automatically. If you're not aligned I can remove it.
Have a nice day!


Alter api key validation to log warning

Goal
Alters api key validation so that an error is logged and configuration is populated as normal.
This has the side effect of allowing the NSError parameter to be removed from initWithApiKey as it is no longer populated in any codepath.
Changeset

Updated initWithApiKey: signature by removing NSError parameter
Updated initWithApiKey to log an error and continue construction rather than returning nil
Removed constants used for populating the NSError

Tests
Relied on existing test coverage which was updated to use new method signatures.

Actually, from discussion on the Android/JS changes: we should be throwing an error if the API key is empty so unfortunately I think this means we need to reinstate the error parameter...

Discussed IRL and agreed with @fractalwrench that the proposed changes are probably the more preferable - either way we have a slight spec deviation, but with this implementation it doesn't affect the signature.

Fixed a compile issue with the mazerunner scenarios and verified by running the breadcrumb scenario manually.

LGTM as long as we're confident in the compile-time null check for which I'd like @robinmacharg's input.

From Apples dev blog: "The compiler will tell you if you try to break the rules."


add npm test

related to https://github.com/stormpath/generator-jhipster-stormpath/issues/4
I generated a project with the .yo-rc.json from test/
Then, I copy all pom.xml, bower.json, all src/ into test/templates/default
Not sure all files are needed, only the files the stormpath generator changes because here, there is a lot lot lot files -> as I didn't have a lot of time, I didn't sort them, I put them all
@mraible : don't hesitate to take my code, close this PR and sort the files needed!

Here the result you should see:
╭─pgrimaud@pgrxps  ~/projects/stormpath/generator-jhipster-stormpath  ‹npm-test›
╰─$ npm test

><EMAIL_ADDRESS>test /home/pgrimaud/projects/stormpath/generator-jhipster-stormpath
> mocha test/*

  JHipster generator Stormpath
    Automated build
      ✓ generates stormpath.config.js file
      ✓ stormpath lib inside pom.xml
      ✓ stormpath lib inside bower.json

  3 passing (385ms)

Thanks @pascalgrimaud! I think it's good to have the whole project in test/templates/default. That way, I can use the jhipster:upgrade subgenerator to update it when I need to.

BTW, what's the difference between npm test and gulp test? The first one works, but the second doesn't seem to.
$ gulp test
[07:04:38] Using gulpfile ~/dev/generator-jhipster-stormpath/gulpfile.js
[07:04:38] Starting 'pre-test'...
[07:04:39] Finished 'pre-test' after 97 ms
[07:04:39] Starting 'test'...

gulp test should display the test coverage
But for your module, it displays nothing! I don't know why.
Can you try my module ?

git clone https://github.com/pascalgrimaud/generator-jhipster-docker.git
npm install
gulp test

That's what I got with my module:
-----------|----------|----------|----------|----------|----------------|
File       |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
-----------|----------|----------|----------|----------|----------------|
 app/      |    48.82 |    32.79 |       85 |    48.36 |                |
  index.js |    48.82 |    32.79 |       85 |    48.36 |... 276,277,279 |
-----------|----------|----------|----------|----------|----------------|
All files  |    48.82 |    32.79 |       85 |    48.36 |                |
-----------|----------|----------|----------|----------|----------------|

=============================== Coverage summary ===============================
Statements   : 48.82% ( 62/127 )
Branches     : 32.79% ( 20/61 )
Functions    : 85% ( 17/20 )
Lines        : 48.36% ( 59/122 )
================================================================================
[15:34:18] Finished 'test' after 983 ms

Strange, it worked yesterday! I tried your module and it works fine.

I added a console.log to the test task and now I see the problem:
err { [Error: Cannot find module 'protractor-jasmine2-screenshot-reporter']
  code: 'MODULE_NOT_FOUND',
  name: 'Error',
  message: 'Cannot find module \'protractor-jasmine2-screenshot-reporter\'',
  stack: 'Error: Cannot find module \'protractor-jasmine2-screenshot-reporter\'\n    at Function.Module._resolveFilename (module.js:325:15)\n    at Function.Module._load (module.js:276:25)\n    at Module.require (module.js:353:17)\n    at require (internal/module.js:12:17)\n    at Object.<anonymous> (/Users/mraible/dev/generator-jhipster-stormpath/test/templates/default/src/test/javascript/protractor.conf.js:3:32)\n    at Module._compile (module.js:409:26)\n    at Object.Module._extensions..js (module.js:416:10)\n    at Object.Module._extensions.(anonymous function) [as .js] (/Users/mraible/dev/generator-jhipster-stormpath/node_modules/istanbul/lib/hook.js:109:37)\n    at Module.load (module.js:343:32)\n    at Function.Module._load (module.js:300:12)',
  showStack: true,
  showProperties: true,
  plugin: 'gulp-mocha' }

If I remove test/templates/default/src/test/javascript/protractor.conf.js, I get a new error about Angular missing.
err { [ReferenceError: angular is not defined]
  name: 'ReferenceError',
  message: 'angular is not defined',
  stack: 'ReferenceError: angular is not defined\n    at /Users/mraible/dev/generator-jhipster-stormpath/test/templates/default/src/main/webapp/app/app.constants.js:4:5\n    at Object.<anonymous> (/Users/mraible/dev/generator-jhipster-stormpath/test/templates/default/src/main/webapp/app/app.constants.js:8:3)\n    at Module._compile (module.js:409:26)\n    at Object.Module._extensions..js (module.js:416:10)\n    at Object.Module._extensions.(anonymous function) [as .js] (/Users/mraible/dev/generator-jhipster-stormpath/node_modules/istanbul/lib/hook.js:109:37)\n    at Module.load (module.js:343:32)\n    at Function.Module._load (module.js:300:12)\n    at Module.require (module.js:353:17)\n    at require (internal/module.js:12:17)\n    at /Users/mraible/dev/generator-jhipster-stormpath/node_modules/gulp-mocha/node_modules/mocha/lib/mocha.js:220:27',
  showStack: true,
  showProperties: true,
  plugin: 'gulp-mocha' }

It's almost like gulp test is doing a compilation of sorts, whereas npm test is not.

I figured it out, gulp was trying to run all the js files. Here's the fix: https://github.com/stormpath/generator-jhipster-stormpath/commit/a1714cadc8e34e93b57a6da8a05672e68a7f45fa

oh yes, you're right !!!
good catch


abide to ilias dir structure, changes to config.js logic

provide config-template.js
add config.js to gitignore so the tool can be ran directly from the repo
update readme to reflect changes

Already abiding to ilias dir structure


Logo added

📋 Description

Added logo in the home page and navbar
🔨 Changes Made

#80

✅ Checklist
Before submitting the PR, please make sure you have completed the following:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation (if applicable).
[x] My changes generate no new warnings.
[x] I have tested it locally and it works fine.
[x] Any dependent changes have been merged and published in downstream modules.

🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)

[ ] Bug fix (non-breaking change which fixes an issue) 🐛
[ ] New feature (non-breaking change which adds functionality) ✨
[x] UI enhancement (non-breaking change which enhances UI) 🎨
[ ] Documentation update 📚

🤝 Related Issues

Fixes #

📸 Screenshots (if applicable)

Reminder:
Please ensure your pull request is made to the test branch, not main.
Thank you for contributing to VigneshDevHub! We look forward to reviewing your PR and getting it merged!

@shreyad2806  please add the logo image in the PR body.

Can you remove the dotted underline also in the logo?

Added the new logo!

Please move the logo.png file to the icons folder in the public directory. Make sure there’s only one instance of logo.png. Also, set the logo as the web icon (favicon) only, and remove it from the navbars.


Issues with chicken-install

When I tried running chicken install as per the build instructions, I ran into a few issues. I'm using chicken scheme 5.2.0 on arch linux. Here's how I got around the problems:
The packages extras and scm2wiki couldn't be found. I removed both from the list and manually installed scm2wiki from its repo.
Compiling bintracker also required that I add the packages byte-blob, base64, imlib2, web-colors.
In the end I couldn't get the docs to build (didn't try very hard though, maybe I will later), so I just removed doc related stuff from the makefile and then the executable generated fine and works :)
p.s. Thanks for all the amazing work on this project!! It's a really fantastic idea.

Thanks for your report, much appreciated!
I've corrected the build instructions. Totally forgot about scm2wiki. The plan is to get it accepted into the official Chicken repo at some point but currently it's still too buggy.
For the docs, you are probably missing some Python packages (which I should add to the instructions of course). You could try pip install --user Pygments for a start. Anyway, please let me know if you manage to work it out.

same for me. I've installed chicken 5.2.0 from source, because the one on linux-mint 19 was too old (4).
I've removed the doc because it was complicated to build.
I got a bintracker binary, but I can't run it, the window start and just crash after that:

Error: bad argument type - not a structure of the required type
#f
bt-types#app-keys
Call history:
../bintracker-core.scm:33: g300
../bintracker-core.scm:36: pstk#tk-end
../bintracker-core.scm:37: simple-exceptions#raise
../bintracker.scm:42: k294
../bintracker.scm:42: g297
../bintracker.scm:44: bt-gui#current
../bt-gui.scm:4087: current
../bt-gui.scm:4079: bt-state#ui
../bt-state.scm:32: state
../bt-state.scm:25: chicken.string#->string
../bt-state.scm:25: scheme#string-append
../bt-state.scm:25: scheme#string->symbol
../bt-state.scm:25: scheme#eval
../bt-state.scm:24: g277
../bintracker.scm:45: pstk#tk-end
../bintracker.scm:46: simple-exceptions#raise

Ugh, that doesn't look good. This might be down to changes introduced in 5.2. I'll investigate asap. For now, if you don't want to wait till I have fixed this then you could try building on 5.0 or 5.1 instead.

Ok, found the bug. Nothing to do with 5.2 (it does break scm2wiki though, so I'll need to look into that).
For now, uncommenting line 20 in config/config.scm should do the trick. I'll provide a proper fix soon. I'll also make building the docs optional.

I've made it run.
I've got a few more issues:

the doc https://bintracker.org/documentation/setup.html talks about config/emulators.scm in the case the mame binary is not called mame64. We'll have to fix this in config/systems.scm
What operating system are you using that calls mame, "mame64"? Debian? On Ubuntu/Mint, it's simply called "mame". In the case "mame" is more widespread, maybe you could change this in the settings, and create a symbolic link on your system, it would confuse users less...

in the doc " Copy ROM files to roms/MACHINE, where MACHINE is MAME's target system identifier string". => it's not enough to copy rom files, zx roms are often called 48.rom but bintracker requires it to be called spectrum.rom. Which is fine, maybe you could change the doc: " Copy ROM files to roms/MACHINE/MACHINE.rom, where MACHINE is MAME's target system identifier string"

but now I wonder, it's still not working this way. I've renamed the 48.rom to spectrum.rom, in roms/spectrum folder.

focus add (block-view842 #<procedure (a37027)> #<procedure (a37033)> #<coops instance of <ui-block-view>'>) focus add (order-view843 #<procedure (a37027)> #<procedure (a37033)> #<coops instance of '>)
spectrum.rom NOT FOUND (tried in spectrum spectrum)

The same for channelf:

sl90025.rom NOT FOUND (tried in channelf channelf)
sl31254.rom NOT FOUND (tried in channelf channelf)

Also, when it's crashing for this purpose, you can't exit bintracker, I had to use xkill

ok, I made it work. Probably our versions of Mame are quite different (mine is 0.215)
in systems.scm, I had to specify the rompath option, like this:

("spectrum48" emulator: "mame" startup-args: ("spectrum" "-rompath" "roms")))

otherwise mame won't understand it had to look in the roms subfolder.

Done fixing the startup bug.
Regarding the application name of MAME, I'll need to find a more robust way to handle this. There should be some code that attempts to auto-detect it.
Regarding ROM names, it's pure coincidence that the Spectrum 48K ROM must be named "spectrum.rom". For the vast majority of systems, the names are pretty arbitrary. So the statement " Copy ROM files to roms/MACHINE/MACHINE.rom, where MACHINE is MAME's target system identifier string" would not hold true in many cases. Unfortunately MAME does not document this at all. There is a third party site that can help with this, perhaps I should link that in the docu.
You are absolutely correct that "-rompath roms" must be passed in. That should actually be in config/emulators.scm. Must've accidentally dropped that line at some point. I wonder why it works for me at all.
Regarding the program not shutting down on error, yes, unfortunately there are still various places where that can happen. I can probably fix this particular instance, but ultimately this problem is caused by pstk, which needlessly crashes on the Tk side when the pipe to the calling program is lost. Haven't been able to find a good solution yet but I'm on it.
One small request for the future, it's easier for me if you open a separate ticket for each issue.
Anyway, many thanks for all your reports, and sorry you had to go through all that trouble!

I wonder why it works for me at all.

maybe you have this setting in one config file in ~/.mame folder?

One small request for the future, it's easier for me if you open a separate ticket for each issue.

sure, I'll do it. I've used the first issue for general starting up... I'll open a few more tickets soon

I've made some changes to pstk, so a crash on the Scheme side should no longer freeze Bintracker. The changes should become available through chicken-install soon. You'll need to re-install pstk and then do a full rebuild of Bintracker with make clean && make.

I've installed again pstk and recompiled bintracker, but i didn't notice much difference so far.

You mean the Tk window still hangs on errors like missing ROMs? Then I'm pretty sure pstk was re-installed from your local cache. Try chicken-uninstall pstk followed by chicken-install pstk. Sorry for not being more clear about that.


Fix Newtonsoft.Json.JsonReaderException

Fix Issue #17 Newtonsoft.Json.JsonReaderException when a device has more than 2GB of total memory.

Looks great -- I left a minor comment, then we can merge. 👍

@anthturner, I don't see a comment anywhere in the PR, the files, or the issue.  Can you tell me where you left it?

If you look here:
https://github.com/anthturner/UniFiSharp/pull/21/files/86ee4b4ca83d215e60975a77c837f5dfa9ab8365#diff-13167a673a54979905bb9e64cd26af954c6a5d6c19f4c5300eefbb4e46f51f3e
On line 43, it shows the comment inline. It's part of the "review" process for PRs on GitHub; it allows you to respond directly to the specific concern with your own comments too. :)
(Incidentally, if you scroll up in this PR it should show as well, next to

anthturner started a review

Ha.  That comment never showed up on the file in my view of the pull request until now.  Sorry, I was going to follow up with a screenshot of no comments on the pull request, but then got distracted by other work.
In answer to your question—yes it was intentional.  A bit of OCD.  Putting the NetworkConfigurations in alphabetical order for readability.  I just have some standard improvements I do in any file I touch.  But its your project.  If changes like that bother you, I’ll stick to the minimum necessary in the future.
From: Anthony Turner @.>
Sent: Tuesday, February 22, 2022 3:31 PM
To: anthturner/UniFiSharp @.>
Cc: Mike Davis @.>; Author @.>
Subject: Re: [anthturner/UniFiSharp] Fix Newtonsoft.Json.JsonReaderException (PR #21)
@anthturner approved this pull request.
I've decided this isn't important enough to block integration.

In UniFiSharp/NetworkDeviceConfigurations.cshttps://github.com/anthturner/UniFiSharp/pull/21#discussion_r793923325:

     public static Func<string, NetworkDeviceConfigurations<string>> LedOverride =>

         new Func<string, NetworkDeviceConfigurations<string>>((v) =>

             new NetworkDeviceConfigurations<string>((object)new { led_override = v }));

   public static Func<string, NetworkDeviceConfigurations<string>> Name =>

Was this intentional? Not sure I'm following the purpose. Seems like things are just being shuffled around in this file.
—
Reply to this email directly, view it on GitHubhttps://github.com/anthturner/UniFiSharp/pull/21#pullrequestreview-865322955, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAKEYUSVYI2CXFX6PNTXQA3U4P6AXANCNFSM5M445LMA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Not a problem; I merged it anyways. 😀
Thanks for your contribution!


blueprint_register with two different controller with subdomain but url_for use first problem

from app.controllers.dashboard.admin import dashboard1
from app.controllers.dashboard.supply import dashboard2
app.register_blueprint(dashboard1, subdomain='admin')
app.register_blueprint(dashboard2, subdomain='supply')
but
@dashboard2.route('/')
def index():
return url_for('company.index')
is always appear that "http://admin.domain.com:5000/company"

Duplicate of #1091


phpPackages.phpstan: 0.11.12 -> 0.11.15

Motivation for this change
Changelog: https://github.com/phpstan/phpstan/releases/tag/0.11.15
Changelog: https://github.com/phpstan/phpstan/releases/tag/0.11.14
Changelog: https://github.com/phpstan/phpstan/releases/tag/0.11.13
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Built and tested locally :+1:


TensorFlow cannot use GPU.

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
No
Source
source
Tensorflow Version
tf 2.12.0
Custom Code
Yes
OS Platform and Distribution
Windows 11
Mobile device
No response
Python version
3.11.2
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
11.8/8.6
GPU model and memory
No response
Current Behaviour?
import tensorflow as tf
print("Num GPUs Available: ", len(tf.config.list_physical_devices('GPU')))
tf.config.list_physical_devices('GPU')
tf.config.list_physical_devices()
Num GPUs Available:  0
[PhysicalDevice(name='/physical_device:CPU:0', device_type='CPU')]

Standalone code to reproduce the issue
I install CUDA 11.8 and CUDNN 8.6, but TensorFlow cannot use GPU.I also set %PATH% variable.

Relevant log output
No response

import tensorflow as tf
print("Num GPUs Available: ", len(tf.config.list_physical_devices('GPU')))
tf.config.list_physical_devices('GPU')
tf.config.list_physical_devices()

Output :
Num GPUs Available:  1
[PhysicalDevice(name='/physical_device:CPU:0', device_type='CPU'),
 PhysicalDevice(name='/physical_device:GPU:0', device_type='GPU')]

When I running this code I was getting true output . Please check if It is possible that another process is already using the GPU, preventing TensorFlow from accessing it. Check if any other GPU-intensive programs are running on your system and close them.

Hi @NoteDancing,
As per the official Tensorflow documenation,

TensorFlow 2.10 was the last TensorFlow release that supported GPU on native-Windows. Starting with TensorFlow 2.11, you will need to install TensorFlow in WSL2, or install tensorflow-cpu and, optionally, try the TensorFlow-DirectML-Plugin

Also note that,

TensorFlow with GPU access is supported for WSL2 on Windows 10 19044 or higher.

Kindly refer to the official documentation for more information. Thank you!

@synandi Tensorflow 2.12.0 Can't use GPU on Windows 11?

@synandi Tensorflow 2.12.0 Can't use GPU on Windows 11?

@NoteDancing Yes. In order to leverage GPU with TensorFlow 2.12, you must install TensorFlow in WSL2 or you can also try the try the TensorFlow-DirectML-Plugin. Thank you!

@synandi Does tensorflow-directml-plugin make tensorflow 2.12.0 use GPU on windows 11?Thank you!

@synandi Does tensorflow-directml-plugin make tensorflow 2.12.0 use GPU on windows 11?Thank you!

@NoteDancing  Yes. Kindly refer to the TensorFlow-DirectML-Plugin. Thank you!

@synandi I try pip install tensorflow-directml-plugin, but I get error.
ERROR: Could not find a version that satisfies the requirement tensorflow-directml-plugin (from versions: none)
ERROR: No matching distribution found for tensorflow-directml-plugin


fix_xcursor

Hello your fix_xcursor fix the size of the cursor?
If it's the case can you share it please? I have this issue since a while and can't fix it.
Regards,

That's a part of the default i3 config of manjaro, but I stopped using manjaro a long time ago. It looks like a script made by the manjaro team, but I never used it again on any of my WM, neither in arch nor in debian.


CIF-1938: add ui tests for catalog page status bar

Description
This adds ui.tests to verify the catalog page status is shown on template pages and catalog pages.
The test Catalog Page Status is shown on specific pages requires an AddOn release and so is for now disabled.
Related Issue
CIF-1938
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[X] I have added tests to cover my changes and the overall coverage did not decrease.
[X] All unit tests pass on CircleCi.
[X] I ran all tests locally and they pass.

This doesn't work well yet, see CIF-2946


[Bug]: long text display bug

What happened?
A bug happened!

If the input crosses the line, it will not be a line change
I think related functions should be added
anyone have a same issue? or is depend on server's shell?
Node Version
16.16.0
NPM Version
8.11.0
Server OS Version
windows
WebSSH2 release version
0.5.0-pre-5
OS and Version of SSH server
No response
Browser Version
No response
Relevant log output
No response

it happend when first window render, it is working when resize
so i debugging it and find to bug with paramater

MR was opened @billchurch plz, check it, i dont have a permissions
#351

Have you encountered the same issue， Is there a fix commit available?