display of  in connection with value of @met and values of @n in  when xml:lang is "san" or "kaw"

@ajaniak:
NB: this message does not concern any editions where xml:lang is "tam". Manu has to formulate rules for that language.
<lg n="1" met="anuṣṭubh">
	<l n="a">vahubhir vasudhā dattā</l>
	<l n="b">rāj<choice><sic>ā</sic><corr>a</corr></choice>bhis sagarādibhi<supplied reason="omitted">ḥ</supplied></l>
	<l n="c">yasya yasya yadā bhūm<unclear>i</unclear>s</l>
	<l n="d">tasya tasya tadā phalaṁ</l>
</lg>

currently leads to this display:

I would prefer it to be like this:

I have taken this example of desired layout from EIAD 188. We don't need such a large gap between the stanza number and the rest, but we do need the following:

the name of the meter is to be aligned with the lines of verse
when met="anuṣṭubh", <l> ab and cd are to be placed side by side, and no extra indent on the group cd vis-à-vis the group ab.

Let us call this second mode "grouped display" and let us call the present display "linewise display".
For proper display of <lg>, please take into account the following parameters

value of @met (refer to the tables under "Sanskrit syllabic metres" and "Sanskrit/Prakrit moraic metres" in EGD Appendix B)
values of @n in <l>

With those parameters, I think the following rules can be formulated:

If @n shows values "ab" and "cd", then always choose linewise display.
If @n shows values "a", "b", "c" and "d", then apply groupwise display if @met="sumānikā" or @met="anuṣṭubh". NB: if <l> shows @enjamb="yes" then place the next <l> after the first without intervening space; in all other cases, place a space between the two <l>s.
If @n shows values "a", "b", "c" and "d", the apply linewise display for all other values of @met.

I would suggest always using the same amount of indent on every displayed line.
It is quite possible that I have forgotten some complications, and I trust @danbalogh will intervene quickly if such is the case.

I'm OK with displaying anuṣṭubh and this weird sumānikā in the grouped manner. I see no complications at the moment, except possibly that in some rare cases there may be an @enjamb on line b. I think that is quite unlikely, but should it happen, line c must still be started in a new line and perhaps a hyphen should then be displayed at the end of line b. (I think this is what I suggested earlier for the default displaying of stanzas).
As for indenting, I personally much prefer to indent even lines (that is, to indent them more deeply than odd lines), but if Arlo definitely prefers all lines of a stanza to begin at the same level of indentation, then I can live with that.

If it comes to personal preferences, I - like Arlo - prefer all lines to begin at the same level of indentation.

Manu: can you cast your vote, so that Axelle can get to work on this?

I am in favour of linewise display in all cases, that is
1 line for <l n="a">, 1 line for <l n="b">, etc.
1 line for <l n="ab">, 1 line for <l n="cd">, etc.
Thus, option1:

Or, option 2 (my favourite)

Or even option 3 (I am not against furhter identation for <l n="b"> and <l n="d">)

As for Anuṣṭubh, I do not mind if it is italicised or not.

all of Manu's proposals would be fine with me. for me it is most important that we soon get a better layout than what we have now (so I can start using our html's in reading editions in the classroom). so let us take Manu's favorite option (no. 2).
@ajaniak: please go ahead and implement it.

@manufrancis, can you confirm you expect  a line/space between the line with the number and the @met and the first <l>?

Yes, I confirm.
Like this:

Not like this:

Thanks @manufrancis . To do so, I had to distinguish the first <l> and handle the space with the CSS. For now, the space has the value 10px. I can reduce it or make it bigger if necessary.
The idents are also handle with CSS.
Let me know if the alignment is conform to your expectations.

Fine with me!
Thank you, Axelle.

looks good to me me too! closing this now.


Update doc sections describing indexing behavior

Description
This commit removes the section describing behavior with fields not defined in the config since it is obsolete and the new behavior is already covered in details in the previous section on the mapping mode.
It also clarifies the section describing behavior with missing fields, which currently doesn't mention that missing fast fields will cause the entire record to be rejected.
How was this PR tested?
Manually verified that the newly documented behavior is indeed what happens.
Fixes #2711

Thanks @imotov!


JSDoc intellisense for Vue 3 setup events and component description

Discussed in https://github.com/johnsoncodehk/volar/discussions/1473

Originally posted by vincerubinetti June 17, 2022
I'm using Vue 3 and the composition API with <script setup>. Just upgraded to the latest version of Vue and and updated my Volar extension.
All of this works great (note the comments):
TestComponent.vue
<script setup lang="ts">
/** fun test component */

interface Props {
  /**  text to show in label */
  text: string;
}

const props = defineProps<Props>();

props.text; // hovering over this shows "text to show in label"

interface Emits {
  /** test event */
  (event: "test"): void;
}

const emit = defineEmits<Emits>();

emit("test"); // hovering over this shows "test event"
</script>

But if I use the component in another template, there are some holes:
<template>
  <TestComponent
    text="test text"
    @test="() => null"
  />
</template>

Hovering over the text attribute shows "text to show in label", but hovering over @test does not show "test event". It would also be cool if hovering over the TestComponent tag showed "fun test component" (and any other JSDoc info I suppose).
I did try different JSDoc tags like @description and @function to see if those would show up, but they didn't.
It'd be cool if Volar could support this. I think there are other tools/plugins that do this, but they all seem to be more on the side of doc generators. I don't need a doc generator because my app is small enough, but I do want/need intellisense for components/props/events because I forget what they are.
Sorry if this is the wrong place for this, I'm not sure if this falls under the scope of Vue/Volar/VS Code/TypeScript/etc.

Due to TypeScript limitation we can't support JSDoc for defineEmits, but for events from defineProps is possible.
interface Props {
  /** test event */
  onTest(): void;
}

const props = defineProps<Props>();

@johnsoncodehk will this be a thing for vue-tsc? Or only for IDE support?

@d8vjork all TS behavior is affected for vue-tsc and IDE support both.

I saw the pinned issue about maintaining this project.
Will be very happy to help with this project and this feature in particular, but I've 0 (none) idea about TypeScript's tsc.

What changes need to be done to copy the behavior of vue-styleguidist in volar?
See https://github.com/vue-styleguidist/vue-styleguidist/issues/1399.

Implemented via #4365, for script setup components that need to work with Vue 3.5, for generic components it should already work.


add profile auto completion for maven

The script will filter all profile id from pom.xml in current directory and support profile auto completion for '-P<tab>'.

Closing in favor of #2903


histogram feature enhancements and observations

Description
Creating this ticket to consolidate possible feature request for histogram

Shorthand notation of y-axis value like main chart (84119.84 vs. 84.12M)
Legend is not appearing to indicated what the histogram indicator is, or the ability to show/hide the indicator (macd example)
[Not possible based on lightweight library] Horizonal Crosshair of Histogram, but bringing this up for below point. Maybe it's possible to hack this my overlaying a hidden line chart that follows this histogram?
Tick Y-axis missing. Without a horizontal crosshair make it difficult to understand the magnitude of these bars if used on it's own to represent PNL. But when paired with line chart of equal magnitude, ticks show-up

Code example
    import pandas as pd
    from lightweight_charts import Chart
    import numpy as np
    import pandas_ta as ta

    np.random.seed(42)

    chart = Chart(inner_height=0.5, height=800)
    chart.legend(visible=True)

    df = pd.read_csv('ohlcv.csv')
    df[['macd', 'macd_hist', 'macd_signal']] = ta.macd(df.close, 20, 50, 10)
    df = df.tail(120).reset_index(drop=True)

    volume_df = df[['date', 'volume']]
    volume_df = pd.concat([volume_df, pd.Series(np.random.choice([-1, 1], size=len(volume_df)), name='factor')], axis=1)
    volume_df['pnl_value'] = volume_df['volume'] * volume_df['factor'].div(1_000)

    volume_df['color'] = np.where(volume_df.pnl_value >= 0, 'rgba(0,114,54,255)', 'rgba(201,29,35,255)')

    vol_chart = chart.create_subchart(position='bottom', width=1, height=0.25, sync=True)
    vol_chart = vol_chart.create_histogram(name='pnl_value')

    chart.set(df[['date', 'open', 'high', 'low', 'close', 'volume']])
    vol_chart.set(volume_df[['date', 'pnl_value', 'color']])
    vol_chart.horizontal_line(85_000.0, text='Outlier Wins')
    vol_chart.horizontal_line(-85_000.0, text='Outlier Losses')

    macd_chart = chart.create_subchart(position='bottom', width=1, height=0.25, sync=True)
    macd_chart.legend(visible=True)

    macd_line = macd_chart.create_line(name='macd', width=1)
    macd_signal = macd_chart.create_line(name='macd_signal', width=1, style='dotted')
    macd_hist = macd_chart.create_histogram(name='macd_hist')

    macd_df = df[['date', 'macd', 'macd_signal', 'macd_hist']]

    macd_line.set(macd_df[['date', 'macd']])
    macd_signal.set(macd_df[['date', 'macd_signal']])
    macd_hist.set(macd_df[['date', 'macd_hist']])

    chart.show(block=True)

Method of implementation
No response

Hey @karunkrishna,
Shorthand will be implemented in the next update. As for Histogram showing up in the legend, i'll add this in a later update most likely.
You could do the hidden line with the current version of the library; just set the color of the line to 'transparent'. Let me know if it works!
Louis

Btw, histogram can be none-scaled zero-based (example: logic True/False). ltw-charts allow it with autoscaleInfoProvider option.
For this feature i use dirty hack, may be you will do it better:
class Histogram(SeriesCommon):
    def __init__(self, chart, name, color, price_line, price_label, scale_margin_top, scale_margin_bottom,set_auto_scale=False):
        super().__init__(chart, name)
        self.color = color
        fautoscale=''
        fpricescale=''
        if set_auto_scale:
            fautoscale = f'''autoscaleInfoProvider: () => ({{
                        priceRange: {{
                            minValue: {scale_margin_bottom},
                            maxValue: {scale_margin_top},
                            }},
                        }}),'''
        else:
            fpricescale='''{self.id}.series.priceScale().applyOptions({{
                        scaleMargins: {{top: {scale_margin_top}, bottom: {scale_margin_bottom}}}
                        }})'''

        self.run_script(f'''
        {self.id} = {{
            series: {chart.id}.chart.addHistogramSeries({{
                color: '{color}',
                lastValueVisible: {jbool(price_label)},
                priceLineVisible: {jbool(price_line)},
                priceScaleId: '{self.id}'
            }}),
            {fautoscale}
            markers: [],
            horizontal_lines: [],
            name: '{name}',
            color: '{color}',
            precision: 2,
            }}
            {fpricescale}
        ''')

@karunkrishna, 1 and 2 have been implemented in the latest version.
@DmitryAkDev, I'm not entirely sure what your histogram implementation is indended to do?
Thanks,
Louis

@DmitryAkDev, I'm not entirely sure what your histogram implementation is indended to do?

Show histogram with hard visible range (-scale_margin_bottom, scale_margin_top).
Default behavior for True, False histogram after scale in:

Modified
   {self.id} = {{                 series: {chart.id}.chart.addHistogramSeries({{                     color: '{color}',                     lastValueVisible: {jbool(price_label)},                     priceLineVisible: {jbool(price_line)},                     priceScaleId: '{self.id}',                     priceFormat: {{type: "volume"}},                     autoscaleInfoProvider: () => ({{                         priceRange: {{                             minValue: {scale_margin_bottom},                             maxValue: {scale_margin_top},                             }},                         }}),                 }}),                 markers: [],                 horizontal_lines: [],                 name: '{name}',                 color: '{color}',                 precision: 2,                 }}

Hey @karunkrishna,
Shorthand will be implemented in the next update. As for Histogram showing up in the legend, i'll add this in a later update most likely.
You could do the hidden line with the current version of the library; just set the color of the line to 'transparent'. Let me know if it works!
Louis

Yeah don't think it's possible I think the histogram when it get's created always shifts the placement in relationship to the line chart
The line and the histogram is the same value (which is the volume) so it can only ever be above 0. and the histogram get's shifted and almost implies negative numbers. My assumption was that it would overlay on top of each other


bug: Typescript files are not being compiled, when I add million.webpack() to my webpack 5 configuration

Hi @aidenybai
Filing this issue again.  The original can be seen here. #476
I tried with both  v2.5.0 and latest which installed 2.5.2-beta.0 and get the following errors.

using windows 11, VS Code and:
"million": "^2.5.2-beta.0",
"typescript": "^5.1.6",
"webpack": "^5.88.2",
"webpack-cli": "^5.1.4",
"webpack-dev-server": "^4.15.1"

Can we get a repro please @TerrySlack? It'll be easier to help us set see the issue and then figure out possible solutions to it.

@tobySolutions
Here you go:
https://github.com/TerrySlack/millionjs-bug

@tobySolutions were you able to detect the issue(s) in the repo I provided?

@tobySolutions ?

@tobySolutions @TerrySlack @aidenybai any updates on this?

@norbertorok92 I've pinged them a few times, since providing a repo and no response.
I'd love to use this library, but at this point, I'm moving on.  If they ever decide to put out an update, I'll revisit.  I can't wait any longer

Hmm, sorry about this @TerrySlack and @norbertorok92.
Can you install the latest version please and then retry this. Also, I'd love to see your configuration file to see how you set up Million.

@tobySolutions
You can view it in the repo you requested, amd I provided in the comment from Aug 1

Really sorry for the late response. Nobert brought it up with the team too and I'm looking into it.
I'll keep you updated as I might not be able to look at this myself at the moment. I'm a bit under the weather.
Thanks for responding!

@tobySolutions How is it going?  Any progress?

@tobySolutions How is it going?  Any progress?

Hey Terry! Yep! Nobert was able to fix his bug, but, I'm not sure if the same thing can apply to you.
I'll share it here soon so you can have a read through of hos solution

Hey Toby,
Well, that's ambiguous :)
So are you saying it doesn't work with Windows? Or Webpack?  If it's a webpack thing, I can give it a try on Vite if necessary.
If it's my configuration in Webpack, I'm open to any suggestions your team has.  I really like what I have read about million and can see a perfect use for it in an upcoming project.

I'm going to be hitting a hard deadline on whether to use millions or not.
Do you have a solution for windows, typescript and webpack 5?
If the repo I provided needs tweaks that can happen.  Is this a lib that works cross platform?  If so, what tweaks need to be made to have ot work with webpack 5 and typescript?
I love the concept of this lib and hope there is a solution.

@tobySolutions Well, when I get a github bot pointing out how stale this issue is, I realize that a solution isn't coming.
To bad.  Really love the concept.

Hey there @TerrySlack; that's just github actions being weird though. The issue is still actively under review

Hey @tobySolutions , culd I get an update on what is happening?

Are you still getting this @TerrySlack? 🤔🤔

I can't answer for @TerrySlack, but I'm noticing the same error in https://github.com/NDLANO/h5p-editor-topic-map/pull/641. By setting the transpileOnly: true option on ts-loader, the errors disappeared from the build, but the browser console is now saying that React is not defined.

Thanks for looking into this!

@tobySolutions
I haven't tried using your library since I filed this bug. I haven't heard of any uodates regarding it.  Have things been fixed?  Curious, did you use the repo I provided to test things out?
Terry

Im having the same issue. It happens in auto and manual mode. Without this plugin it runs fine.
Im executing
"start": "NODE_ENV=development webpack-dev-server --mode development",

related packages
   "webpack": "^5.60.0",
    "webpack-bundle-analyzer": "^4.5.0",
    "webpack-cli": "^4.9.1",
    "webpack-dev-server": "^4.3.1",
    "webpack-server": "^0.1.2",
    "million": "^2.6.4",
    "typescript": "^4.4.4",

webpack.config.js
const dotenv = require('dotenv').config()
const Dotenv = require('dotenv-webpack')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const ModuleFederationPlugin = require('webpack/lib/container/ModuleFederationPlugin')
const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')
const MiniCssExtractPlugin = require('mini-css-extract-plugin')
const path = require('path')
const TerserPlugin = require('terser-webpack-plugin')

const webpack = require('webpack')
const million = require("million/compiler");

const APP_MODE = process.env.NODE_ENV || 'development'
const APP_PORT = process.env.APP_PORT || '3000'
const isProduction = process.env.NODE_ENV === 'production'

module.exports = {
  entry: './src/index.tsx',
  mode: APP_MODE,
  output: {
    filename: '[name].chunk.js',
    path: path.join(__dirname, 'build'),
    clean: true,
  },
  devServer: {
    port: APP_PORT,
    client: {
      overlay: {
        errors: true,
        warnings: false,
      },
    },
    allowedHosts: ['*', 'dev.cor.com', 'cor.com'],
  },
  module: {
    rules: [
      {
        /* The following line to ask babel
             to compile any file with extension
             .js */
        test: /\.js?$/,
        /* exclude node_modules directory from babel.
            Babel will not compile any files in this directory */
        exclude: [/node_modules/],
        // To Use babel Loader
        loader: 'babel-loader',
        options: {
          presets: ['@babel/preset-env' /* to transfer any advansed ES to ES5 */, '@babel/preset-react'], // to compile react to ES5
        },
      },
      {
        test: [/\.tsx?$/, /\.ts?$/],
        use: 'ts-loader',
        exclude: /node_modules/,
      },
      {
        // The following rule is set to add all css compiler rules
        test: /\.css$/i,
        use: [isProduction ? MiniCssExtractPlugin.loader : 'style-loader', 'css-loader'],
      },
      {
        test: /\.svg$/,
        use: [
          {
            loader: 'svg-url-loader',
            options: {
              limit: 10000,
            },
          },
        ],
      },
    ],
  },
  resolve: {
    extensions: ['.jsx', '.js', '.ts', '.tsx', '.json', '.css', '.jpg', '.jpeg', '.png', '.svg'],
    fallback: { 'process/browser': require.resolve('process/browser') },
    alias: {
      react: path.resolve('./node_modules/react'),
    },
  },
  plugins: [
    million.webpack(),
    // Dot env plugin to get .env variables to npm process
    new Dotenv(),
    new webpack.ProvidePlugin({
      Buffer: ['buffer', 'Buffer'],
      process: 'process/browser',
    }),
    new MiniCssExtractPlugin({
      filename: isProduction ? `static/css/[name].[contenthash].css` : '[name].css',
      chunkFilename: `static/css/[id].[contenthash].css`,
    }),
    new HtmlWebpackPlugin({
      template: './public/index.html',
    }),
  ],
  optimization: {
    minimize: true,
    minimizer: [new TerserPlugin({ parallel: true })],
    splitChunks: {
      // include all types of chunks
      chunks: 'all',
      cacheGroups: {
        vendor: {
          name: 'node_vendors',
          test: /[\\/]node_modules[\\/]/,
          chunks: 'all',
        },
      },
    },
  },
}

isProduction && (module.exports['devtool'] = 'source-map')
isProduction && module.exports['plugins'].push(new webpack.optimize.AggressiveMergingPlugin())

Im having the same issue. It happens in auto and manual mode. Without this plugin it runs fine. Im executing
"start": "NODE_ENV=development webpack-dev-server --mode development",

related packages
   "webpack": "^5.60.0",
    "webpack-bundle-analyzer": "^4.5.0",
    "webpack-cli": "^4.9.1",
    "webpack-dev-server": "^4.3.1",
    "webpack-server": "^0.1.2",
    "million": "^2.6.4",
    "typescript": "^4.4.4",

webpack.config.js
const dotenv = require('dotenv').config()
const Dotenv = require('dotenv-webpack')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const ModuleFederationPlugin = require('webpack/lib/container/ModuleFederationPlugin')
const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')
const MiniCssExtractPlugin = require('mini-css-extract-plugin')
const path = require('path')
const TerserPlugin = require('terser-webpack-plugin')

const webpack = require('webpack')
const million = require("million/compiler");

const APP_MODE = process.env.NODE_ENV || 'development'
const APP_PORT = process.env.APP_PORT || '3000'
const isProduction = process.env.NODE_ENV === 'production'

module.exports = {
  entry: './src/index.tsx',
  mode: APP_MODE,
  output: {
    filename: '[name].chunk.js',
    path: path.join(__dirname, 'build'),
    clean: true,
  },
  devServer: {
    port: APP_PORT,
    client: {
      overlay: {
        errors: true,
        warnings: false,
      },
    },
    allowedHosts: ['*', 'dev.cor.com', 'cor.com'],
  },
  module: {
    rules: [
      {
        /* The following line to ask babel
             to compile any file with extension
             .js */
        test: /\.js?$/,
        /* exclude node_modules directory from babel.
            Babel will not compile any files in this directory */
        exclude: [/node_modules/],
        // To Use babel Loader
        loader: 'babel-loader',
        options: {
          presets: ['@babel/preset-env' /* to transfer any advansed ES to ES5 */, '@babel/preset-react'], // to compile react to ES5
        },
      },
      {
        test: [/\.tsx?$/, /\.ts?$/],
        use: 'ts-loader',
        exclude: /node_modules/,
      },
      {
        // The following rule is set to add all css compiler rules
        test: /\.css$/i,
        use: [isProduction ? MiniCssExtractPlugin.loader : 'style-loader', 'css-loader'],
      },
      {
        test: /\.svg$/,
        use: [
          {
            loader: 'svg-url-loader',
            options: {
              limit: 10000,
            },
          },
        ],
      },
    ],
  },
  resolve: {
    extensions: ['.jsx', '.js', '.ts', '.tsx', '.json', '.css', '.jpg', '.jpeg', '.png', '.svg'],
    fallback: { 'process/browser': require.resolve('process/browser') },
    alias: {
      react: path.resolve('./node_modules/react'),
    },
  },
  plugins: [
    million.webpack(),
    // Dot env plugin to get .env variables to npm process
    new Dotenv(),
    new webpack.ProvidePlugin({
      Buffer: ['buffer', 'Buffer'],
      process: 'process/browser',
    }),
    new MiniCssExtractPlugin({
      filename: isProduction ? `static/css/[name].[contenthash].css` : '[name].css',
      chunkFilename: `static/css/[id].[contenthash].css`,
    }),
    new HtmlWebpackPlugin({
      template: './public/index.html',
    }),
  ],
  optimization: {
    minimize: true,
    minimizer: [new TerserPlugin({ parallel: true })],
    splitChunks: {
      // include all types of chunks
      chunks: 'all',
      cacheGroups: {
        vendor: {
          name: 'node_vendors',
          test: /[\\/]node_modules[\\/]/,
          chunks: 'all',
        },
      },
    },
  },
}

isProduction && (module.exports['devtool'] = 'source-map')
isProduction && module.exports['plugins'].push(new webpack.optimize.AggressiveMergingPlugin())

Hey there! Thanks for this, I think a reproduction will be much better actually. Thank you!

Im having the same issue. It happens in auto and manual mode. Without this plugin it runs fine. Im executing
"start": "NODE_ENV=development webpack-dev-server --mode development",

related packages
```
   "webpack": "^5.60.0",
    "webpack-bundle-analyzer": "^4.5.0",
    "webpack-cli": "^4.9.1",
    "webpack-dev-server": "^4.3.1",
    "webpack-server": "^0.1.2",
    "million": "^2.6.4",
    "typescript": "^4.4.4",
```
webpack.config.js
const dotenv = require('dotenv').config()
const Dotenv = require('dotenv-webpack')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const ModuleFederationPlugin = require('webpack/lib/container/ModuleFederationPlugin')
const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')
const MiniCssExtractPlugin = require('mini-css-extract-plugin')
const path = require('path')
const TerserPlugin = require('terser-webpack-plugin')

const webpack = require('webpack')
const million = require("million/compiler");

const APP_MODE = process.env.NODE_ENV || 'development'
const APP_PORT = process.env.APP_PORT || '3000'
const isProduction = process.env.NODE_ENV === 'production'

module.exports = {
  entry: './src/index.tsx',
  mode: APP_MODE,
  output: {
    filename: '[name].chunk.js',
    path: path.join(__dirname, 'build'),
    clean: true,
  },
  devServer: {
    port: APP_PORT,
    client: {
      overlay: {
        errors: true,
        warnings: false,
      },
    },
    allowedHosts: ['*', 'dev.cor.com', 'cor.com'],
  },
  module: {
    rules: [
      {
        /* The following line to ask babel
             to compile any file with extension
             .js */
        test: /\.js?$/,
        /* exclude node_modules directory from babel.
            Babel will not compile any files in this directory */
        exclude: [/node_modules/],
        // To Use babel Loader
        loader: 'babel-loader',
        options: {
          presets: ['@babel/preset-env' /* to transfer any advansed ES to ES5 */, '@babel/preset-react'], // to compile react to ES5
        },
      },
      {
        test: [/\.tsx?$/, /\.ts?$/],
        use: 'ts-loader',
        exclude: /node_modules/,
      },
      {
        // The following rule is set to add all css compiler rules
        test: /\.css$/i,
        use: [isProduction ? MiniCssExtractPlugin.loader : 'style-loader', 'css-loader'],
      },
      {
        test: /\.svg$/,
        use: [
          {
            loader: 'svg-url-loader',
            options: {
              limit: 10000,
            },
          },
        ],
      },
    ],
  },
  resolve: {
    extensions: ['.jsx', '.js', '.ts', '.tsx', '.json', '.css', '.jpg', '.jpeg', '.png', '.svg'],
    fallback: { 'process/browser': require.resolve('process/browser') },
    alias: {
      react: path.resolve('./node_modules/react'),
    },
  },
  plugins: [
    million.webpack(),
    // Dot env plugin to get .env variables to npm process
    new Dotenv(),
    new webpack.ProvidePlugin({
      Buffer: ['buffer', 'Buffer'],
      process: 'process/browser',
    }),
    new MiniCssExtractPlugin({
      filename: isProduction ? `static/css/[name].[contenthash].css` : '[name].css',
      chunkFilename: `static/css/[id].[contenthash].css`,
    }),
    new HtmlWebpackPlugin({
      template: './public/index.html',
    }),
  ],
  optimization: {
    minimize: true,
    minimizer: [new TerserPlugin({ parallel: true })],
    splitChunks: {
      // include all types of chunks
      chunks: 'all',
      cacheGroups: {
        vendor: {
          name: 'node_vendors',
          test: /[\\/]node_modules[\\/]/,
          chunks: 'all',
        },
      },
    },
  },
}

isProduction && (module.exports['devtool'] = 'source-map')
isProduction && module.exports['plugins'].push(new webpack.optimize.AggressiveMergingPlugin())

Hey there! Thanks for this, I think a reproduction will be much better actually. Thank you!

Forget it! just add transpileOnly: true, and it builds. Thanks ❤

Hmm, thank you very much @9gustin!! I should definitely document this. I'll put a tab on this.


Vec produce seems to not work properly with time-rs

It looks like format spec Vec<FormatItem> produced by ToFormatItemCollector does not work properly when passed to time-rs PrimitiveDateTime::parse or OffsetDateTime::parse.
I tried parsing this  2012-05-21 12:09:14 with a Vec<FormatItem> produced from Y-%m-%d %H:%M:%S and this was the error:
Err("the Parsed struct did not include enough information to construct the type")

@evanxg852000 I've added a couple of tests in 5abd6ed, and it seemingly working. Could you please provide a concrete #[test] that fails?

@MiSawa  Thanks for the follow up, I will be focusing on this as we need it.

As an amendment, the %z specifier is  "An RFC-822/ISO 8601 standard timezone specification."
According to https://en.wikipedia.org/wiki/ISO_8601#Time_zone_designators, it accepts  colon +01:00

Actually I was wrong. Although the example in my previous comment "works", it shouldn't have been used in that way. As the module name suggests, the return value of format::parse_to_format_items should be used to format a time to string, not to parse a string to time.
I guess what you'd want is the parse:: version of the function that emits more complicated FormatItems for case insensitivity, colon and such ambiguities.

Right now the changes I just need is to modify ToFormatItemCollector::timezone
self.items.push(FormatItem::Optional(&FormatItem::Literal(b":")));

I just want to support parsing +00:00 and +0000 for now. If that's OK, I can open a PR with a parse version that does this.
My only concern is: it might be almost a carbon copy of what's in ToFormatItemCollector or maybe we can introduce an intermediate trait in order to reuse.

@evanxg852000 Oops sorry, I was already started implementing it. And... you can now use parse::parse_to_format_items from v0.3.8!

No need to be sorry, Thanks a lot, I am grateful.


Neovim

Tried out these dotfiles with Neovim and things appear working for the most part. Have not conducted extensive tests.
Any interest in committing a $ ln -s vimrc init.vim here, and adding a note about an additional symlink of the repo to ~/.config/nvim?

I would accept a pull request that did this. I don't use Neovim so I don't have any context on the right way to do this.


484 landing page updates

https://app.zenhub.com/workspaces/ccbc---delivery-board-61c0c1204c8bcb001491c5f3/issues/bcgov/conn-ccbc-portal/484

@matthieu-foucault not sure what happened but I think one of the rebases unsigned all my commits


{AKS} Remove az acs command from service_name.json

Related command

az acs
Description

Remove az acs command from service_name.json.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

AKS


need a server.close() method

HttpServer's listen method should return http.Server, it returns only the port
listen(): Promise<number> {
		return new Promise((resolve) => {
			this.server.listen(this.port, () => resolve(this.port))
		})
	}

it should return http.server object.
let app = new HttpServer(PORT)
app.listen().then(callback)
// listen method returns only the port. when it should return node's http.server
// how we do it with express
let server = app.listen(PORT)
server.close()

is there any other way we can use close() method?


chore: codecleanup of unused AI Samples

Code cleanup of unused AI code sample
More details: b351822519

@msampathkumar Can you clarify why we're removing this sample?


IGNORE MEEEE

DO NOT MERGE
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/retest


Nothing happens

I have integrated the library as in the description and it does not work, unfortunately.

Could you tell me how you test your app? What version of Android is your device running? What is your project's target API?

same thing here, I am doing something as simple as this:
    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
        ImageView imageView = (ImageView) findViewById(R.id.imageView2);
        imageView.setOnTouchListener(new ImageMatrixTouchHandler(this));
    }

target: 25
android 5.0
Also, I am trying to do something this simple because the MainActivity.java doesn't display anything when I run that code.. everything compiles fine but the screen is just plain white.. so I decided to just take the piece that I need (pinch and zoom) and implement the viewpager myself

I know this is old, but for anyone looking to resolve this, try using this:
imageView = (ImageView) findViewById(R.id.imageLarge);
imageView.setOnTouchListener(new ImageMatrixTouchHandler(imageView.getContext()));

You indeed need to pass the view's context in order for it to work. I will update the documentation so that it is more clear.

I also solved this issue by setting image view's context but i want to detect the state of image view whether it's zoomed out or zoomed in?

Its not working either way, neither by using[ view.getContext()] nor by using[ imageView.getContext()]

@Dinesh2411 you should be able to detect this by inspecting the image matrix values.

Closed due to lack of activity


Cross Sell, Up-sell and related product information is not appearing in admin end if we create or edit any product in another locale.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
2.0.0
Issue Description
Cross Sell, Up-sell and related product information is not appearing in admin end if we create or edit any product in another locale.
Preconditions

Admin Should be logged in.

Steps to reproduce

Go to Admin -> Catalog -> Products.
Click on Create -> Create any product type in English Locale.
Scroll down and check the cross, related and up sell products.
Now change the Admin Locale to any other locale.
Click on Create -> Create any product type in Arabic Locale.
Now check the information related to cross, related and up sell, there we can see that the details are not appearing.

Expected Result
Details related to Cross Sell, Up Sell and Related products should appear.
Actual Result
Currently we are unable to see the details. Please check the video for reference,
Video
https://github.com/bagisto/bagisto/assets/92721837/fb87daf0-afd0-467e-8c7a-a7fdbc36f758
Screenshots
No response
Additional context
No response

Checked and Found that the issue has been fixed and working fine. Please check the screenshot for the same.
https://prnt.sc/3laogkwtxg0T
https://prnt.sc/yv8okMYH6MBa
https://prnt.sc/GWK0MhxvKwk2

Checked and Found that the issue has been fixed and PR has been merged. Please check the video for reference and I am closing the issue.
Video
Uploading cross sell.mp4…


[Improvement] Add brief description for built-in API functions and simple linter

Hello,
Your plugin is awesome, but I wonder if it's possible in the future to add:
(1) short&brief description for each built-in API functions (or at least those common ones)
(2) simple linter to check syntax error
Thanks! :)

Hello,
Your plugin is awesome, but I wonder if it's possible in the future to add:
(1) short&brief description for each built-in API functions (or at least those common ones)
(2) simple linter to check syntax error
Thanks! :)

Your first suggestion is good. But the second suggestion is restricted to jasshelper and not open source. The method you can take is to configure task in the vscode project to call jasshelper for syntax check.


I am working on a Awesome-Python-HTMX, seeking your feedback

A few of us at PyCon this year got together and brainstormed a new Web Stack that we are calling PyHAT (Python, htmx, ASGI, TailwindCSS). The first thing we set out to do is create awesome-python-htmx; a collection of active tools/libraries/projects in that space (including Tailwind). I have included your project a section listing tooling.
If you could also participate in PyHAT-stack/awesome-python-htmx#1 that would be greatly appreciated! I would in particular be interested to hear about sets your tailwind Python tooling apart from the alternatives.

@benjamin-kirkbride Thanks for reaching out to me and adding me to the list. I left a comment on the issue you mentioned.
Where should I drop the information what is the main difference between django-tailwind and my django-tailwind-cli?

You are welcome to make a PR to expand the section under your project :)
I'd ask:

That you try to keep it to a paragraph or less, so people aren't overwhelmed with huge descriptions of each project, and
That you try to keep the info relatively in sync with the intro to your project on your README; if you want to call out the differences, do it in both places.

Does that make sense/seem reasonable?

The entry on the package looks for me.


Update CMakeLists.txt

CMakeLists updated for  for_loop_test file

Can one of the admins verify this patch?

@deepaksuresh1411 please add this commit to your original PR. There is no need to create a new PR, just keep pushing to the branch you used to create #5778.


Create releases suitable for publication to the Terraform Registry

This addresses #37 and creates automated releases that can be verified for inclusion on the Terraform Registry:
https://www.terraform.io/docs/registry/providers/publishing.html#creating-a-github-release
Changes include:

I fixed the tests that were panicking on go test ./..., which relied on initialization that only happened during acceptance tests
I moved from CircleCI to GitHub Actions and from ghr to GoReleaser. HashiCorp provides official examples with these tools. It would have been possible to call GoReleaser from CircleCI, but the GitHub Action for importing GPG keys seemed worthwhile
Brought back the website from #35, which the registry can render! I tried some of the markup on the Docs Preview Tool and it looks good!
Removed some boilerplate that's stripped away in the official scaffolding (template) repo

The repo doesn't show up when I log in to the registry, so even if I had admin access to add the GPG private key here I wouldn't be able to finish the publication process. So @mrolla you'd need to:

Create a new GPG key
Add the private key and passphrase to the "Secrets" in the repo settings. With GitHub Actions, a GITHUB_TOKEN with the source repo is available automatically
Add the public key to your registry profile: https://registry.terraform.io/settings/gpg-keys
Initiate the publication process (https://www.terraform.io/docs/registry/providers/publishing.html#publishing-your-provider), which will pull in the signed binaries from GitHub

Let me know if I can do anything else to help!

Thanks @mrolla! Will keep an eye out for a tag. Ready to test whenever a release is available!

Amazing work @bendrucker! I'm currently tagging 0.4.0, let's see :)


Possible configuration issue, unable to get logs

Environment details:
used k3s (from rancher) to set up 2 node kubernetes cluster on centos7 vms, remote.
Steps to reproduce the issue:

use k3s create a cluster with two nodes
use helm to install chart for openwhisk
label one node with 'core' and one with invoker

Provide the expected results and outputs:
expected: wsk activation logs -l would have most recent logs from invokes
expected:
Provide the actual results and outputs:
in the hello.js example I'm unable to get any output from a console.log('test') as well as dotnet core examples
Additional information you deem important:
this is a deployment that is not on your standard cloud provider like aws/azure/gke, so is there anything I can check to see where logs are saved?
I noticed on another issue about logs that the command wskadmin syslog get was mentioned, I tried the following and got no such files:
kubectl -n openwhisk -ti exec owdev-wskadmin -- wskadmin syslog get -g *
grep: /var/log/dotnet-install.sh/dotnet-install.sh_logs.log: No such file or directory
grep: /var/log/getRuntimeAction.js/getRuntimeAction.js_logs.log: No such file or directory
grep: /var/log/hello.js/hello.js_logs.log: No such file or directory
grep: /var/log/helloDotNet.zip/helloDotNet.zip_logs.log: No such file or directory
grep: /var/log/helloWorldAction.js/helloWorldAction.js_logs.log: No such file or directory

sorry if this is a bit of a stretch, but are there any values I need to change on my helm charts to fix where it puts things? or should I just do a helm uninstall and reinstall and try again? the invoking and uploading of code is working great so far, just... no logs?

after building my own cluster with KubeAdm:

Weave Net (Ip Allocation of <IP_ADDRESS>/24)
Docker Container Runtime (with Json-file logging in daemon.json)
very basic openEbs install (helm chart, and using openebs-hostpath as storage class

I'm now able to get logs from activations and I'm feeling good, thanks for the help on this


critest: ensure server is running before portforward

What type of PR is this?
/kind flake
What this PR does / why we need it:
containerd CI hits many times on the connect refused when it run portforward related cases 1. Since the CI is running in the github-hosted runner, the host is 2-core CPU 2. When the host is in high load, the nginx server maybe not start in time. If we start to forward the target port which is not working, we will get the error like this:
// https://github.com/containerd/containerd/actions/runs/3449072353/jobs/5756699959
E1112 02:09:46.452379    5536 portforward.go:406] an error occurred forwarding 12002 -> 12003: error forwarding port 12003 to pod 416d9f91eeb0d1ed9c5f828b245d75b515ff81806e368334f2b0bc826705ca63, uid : failed to execute portforward in network namespace "host": failed to connect to localhost:12003 inside namespace "416d9f91eeb0d1ed9c5f828b245d75b515ff81806e368334f2b0bc826705ca63", IPv4: dial tcp4 <IP_ADDRESS>:12003: connect: connection refused IPv6 dial tcp6 [::1]:12003: connect: connection refused

It is easy to reproduce when you update the nginx image with the following changes:
cat /docker-entrypoint.sh
...
sleep 10s
exec "$@"

So we should ensure the port is working before portforward.
Which issue(s) this PR fixes:
Fixes: https://github.com/containerd/containerd/issues/7264
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

Signed-off-by: Wei Fu<EMAIL_ADDRESS>

cc @mikebrow

ping @feiskyer and @saschagrunert~


Multiple instances on Windows -  bad handshake

Hi
Thanks for a great product which I am slowly getting used to!
By issue at the moment is that I want to run 2 instances of cdp. I have started them both off in separate go routines but I get the following errors when running:
2018/03/20 10:20:26 error: could not create handler for 39832E6097A248A1B27E73AB0EB4F29 (): websocket: bad handshake 2018/03/20 10:20:26 error: could not create handler for 39832E6097A248A1B27E73AB0EB4F29 (): websocket: bad handshake
I understand that it is not creating separate handlers, but I am unsure why it is not if they are in different go routines.
The handlers are created
func createHandler(chromeContext context.Context, proxy string) *chromedp.CDP {
c, _ := chromedp.New(chromeContext, chromedp.WithRunnerOptions(
	runner.Proxy(proxy),
))

return c

}
In the temp folder it created 2 folders:
chromedp-runner.9222.528435458
chromedp-runner.9222.085241967
Any help would be appreciated.
Thanks Dov

I ran into the same thing, take a look at the pool example. That is the only way I could get opening two instances at the same time to work

Thanks for the pointer.
The only issue is can I use pool with runner (since I need to set the proxy server)?

Thanks for the pointer.
I rewrote my code to use pools, but am now getting the following error:
2018/03/20 18:02:01 pool allocating 9000
2018/03/20 18:02:01 pool allocating 9000
2018/03/20 18:02:01 pool could not start runner on port 9000: exec: "": executable file not found in %PATH%
2018/03/20 18:02:01 pool released 9000
What executable file is it looking for?

try this:
pool.Allocate(context.Background(), []runner.CommandLineOption{
		runner.Flag("headless", false),
		runner.Flag("no-default-browser-check", true),
		runner.Flag("no-first-run", true),
		runner.Flag("no-sandbox", linuxOS),
		runner.ExecPath('C:\Program Files (x86)\Google\Chrome\Application\chrome.exe'),
	})

The exec path should be the path of chrome on your machine which I think that is the default

Thanks for all your help.

@eurosoll  no problem, let me know if you need help with anything else, I just went through the same issues

Hi again!
I had everything running and was working perfectly until a week ago when it just stopped. The error I am getting is as follows:
2018/04/24 11:04:17 could not create handler for 10434847BE8C9BD7EC8EE9EF3847F50D (about:blank): websocket: bad handshake
2018-04-24 11:04:18AM   royal collection linen feel
2018/04/24 11:04:18 pool could not connect to 9000: timeout waiting for initial target
2018/04/24 11:04:18 pool released 9000
panic: runtime error: invalid memory address or nil pointer dereference2018-04-24 11:04:18AM
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x18 pc=0x7dbb45]
goroutine 6 [running]:
github.com/chromedp/chromedp.(*Res).Release(0x0, 0x0, 0x0)
d:/work/src/github.com/chromedp/chromedp/pool.go:143 +0x35
panic(0x852440, 0xbcb630)
C:/Go/src/runtime/panic.go:505 +0x237
github.com/chromedp/chromedp.(*Res).Run(0x0, 0x94d860, 0xc042180100, 0x94b0c0, 0xc0421aa200, 0x4, 0x0)
d:/work/src/github.com/chromedp/chromedp/pool.go:176 +0x29
main.runCdp(0xc042016ee0, 0x16, 0x8df752, 0x14, 0x8d6b4c, 0x5, 0xc042155920, 0xc0420166a0, 0x1f, 0x0)
d:/work/src/github.com/eurosoll/seo/main.go:224 +0x30b
main.startCdp(0xc04215a200, 0x10, 0x10, 0x8d6b4c, 0x5, 0x8df752, 0x14, 0xc042155920, 0xc042164060, 0xc0420166a0, ...)
d:/work/src/github.com/eurosoll/seo/main.go:188 +0x1b3
created by main.main
d:/work/src/github.com/eurosoll/seo/main.go:149 +0x33f
The first few lines are my own error reporting, the rest are from the panic.
From the errors can you suggest what might be causing the issue?
Thanks for any help. Always appreciated.


docs(phoenix): add example for elixir phoenix

patterned using example/rubyonrails

I see it's failing with:
+ pushd hello
./.test.sh: line 4: pushd: hello: No such file or directory

I see it's failing with:
+ pushd hello
./.test.sh: line 4: pushd: hello: No such file or directory

Oops my bad. Need to remove interactive promp: https://github.com/cachix/devenv/pull/1014


Add new 'Editor' class and edit pipeline without breaking anything (Related to #748)(Resolves #1087)

Add new 'Editor' class and edit pipeline without breaking anything (Related to #748)(Resolves #1087)
This is the first PR that moves us towards atomic commands, content reactions, and undo/redo.
This PR adds all the core concepts for the edit pipeline without changing any existing behavior. The purpose of this PR is to put the core API in front of other developers and see if there are any objections.
This API was created in a separate branch where I've implemented a handful of content reactions, including linkafication, image replacement, and user tagging.
I have a test suite for this Editor class, but I can't integrate that test until we're ready to break Document and DocumentComposer.
You can read a wiki article about how the edit pipeline concepts are meant to work: https://github.com/superlistapp/super_editor/wiki/How-it-works:-The-DocumentEditor

CC @jmatth @Jethro87

This PR has been up for a little while. I've made some minor adjustments based on feedback. Now I'm going to merge in so that we can move to the breaking changes.


Set Hostname after Image apply and print on Lable

Hello,
if I set the host name after writing the image via postscript, I would like to print the new host name on the label. is that possible?

That would be something you would need to develop yourself.
One way is patch our printing code directly.
Another way, would be if you want your changes to survive our future updates, is to write your own custom print label code, that only listen to the CmProvisioningComplete event cmprovision generates, and consult your own database for additional information that should be printed on the label based on serial number or other properties of the CM.
As in create /var/lib/cmprovision/app/Listeners/CustomPrintCode.php
<?php
namespace App\Listeners;

use App\Events\CmProvisioningComplete;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Support\Facades\Http;
use App\Models\Cm;
use App\Models\Setting;

class CustomPrintCode implements ShouldQueue
{
    use InteractsWithQueue;

    /**
     * Create the event listener.
     *
     * @return void
     */
    public function __construct()
    {
    }

    /**
     * Handle the event.
     *
     * @param  App\Events\CmProvisioningComplete  $event
     * @return void
     */
    public function handle(CmProvisioningComplete $event)
    {
        $cm = $event->cm;

        /* $cm contains information about the compute module that just finished provisioning
           Do something useful with it here. */
    }
}

This way you only need to ADD a single file to cmprovision, and do not have to modify existing code.
Less work to merge changes on updates.


[FEATURE] Produce

Todo
Produce
As a user, I should be able to,

View all produce

As a user, I should be able to

search for produce of a specific category

As a farmer, I should be able to

Post a new produce

As a farmer, I should be able to

update a produce

As a farmer, I should be able to

Mark a produce as out of stock

As a farmer, I should be able to

deleted a produce

Is there a UI mockup for this already or I'm developing one myself? @RuthChisom

@sudo-kaizen sorry @nues1979 is already working on this. I'd reassign you. Thanks


Not considering holes when path planning

It considers holes when making swath but, it ignores holes on the step of making route and path.
I think, to solve this problem decomposition part should be added. But it's not in Field2Cover.
Do you have any plan to improve when merging to nav2?

That is not currently a supported feature and won’t be until F2C itself supports it. This is a flexible wrapper for it.


Update cats-core, cats-free to 2.1.0

Updates

org.typelevel:cats-core
org.typelevel:cats-free

from 2.0.0 to 2.1.0.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: semver-minor

Y U set catsEffect to 2.1.0 ???


Allow clicking on buttons with no type

The default value for type is submit:
https://w3c.github.io/html/sec-forms.html#element-attrdef-button-type

Great catch! Thanks @xtian 🎉

Thanks for merging!

No prob. the 0.15.0 release has this fix in it.


Update adds-extend-domain.md

Fixed typo shuting -> shutting.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference-architectures/identity/adds-extend-domain.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Good catch, thanks!


Feature Request - PowerShell Hidden Window Launch Parameter

Summary of the new feature/enhancement
Windows PowerShell supports using the -WindowStyle Hidden launch parameter, however due to limitations of the console it is not possible to completely suppress the flicking, ultimately leading to a poor user experience.
Adding a feature to Terminal is an opportunity to resolve this issue entirely, which would ultimately lead to larger adoption and better overall experience with Windows Terminal.

There's, unfortunately, nothing Terminal can do to fix this. This is baked down into the lowest layers of process creation on Windows. 😦

There's, unfortunately, nothing Terminal can do to fix this. This is baked down into the lowest layers of process creation on Windows. 😦

Is the core of Terminal still a console? Or rather a framework that allows staging of multiple consoles? If it is the latter it could be considered a feature in lieu of the need for creating an entirely separate wscript-like host to simply suppress the console window entirely for background automation and GUI based scripts. This would give me a reason to use Terminal even if I were only planning to have a single console open during the session.


update map markers to only show deployment events and markers with deployment events

@DanielJMaher add deployment number and date to popup

@DanielJMaher one thing you didnt mention was which lat/lon to use, im just using the [0] index in the results


Improve load_dataset etc

Various updates:

break out download logic from mit_d3m main module into separate functions
add initial unit tests
allow unsigned public downloads from s3
other

thank you for your review, let me answer some of your high-level questions here, then i will respond inline above.

splitting the download function in two steps, download + decompress
there are two reasons. first, due to the large size of some of the files on s3, on my local machine (or even on a pretty beefy ec2 instance) one or both of these steps failed, so separating them makes it possible to execute the extraction only without requiring to redownload the dataset. in addition, these are logically two different steps so a "download dataset" downloads the file, and an "extract dataset" extracts the files. finally, as part of analysis i was running load_dataset in a loop for all of the datasets I wanted to analyze and this could have been significantly speeded up by using multiprocessing to separate the download of the files from the extraction, so while I have not implemented this it is facilitated by having these functions separate.

creating some of the new one-line functions, like get_dataset_tarfile_path
this is to facilitate understandability of the code and to make unit testing easier, i did not understand for a long time upon reading the original code that the path of the tarfile is not within the directory that will contain the extracted files, as one example, so the proposed code is more self-documenting

checking if files exist within the folder
i frequently encountered errors using mit-d3m in which the tarfile would download but the system would run out of memory trying to do the extraction, the result of which would be an empty folder. the presence of an empty folder indicates that the extraction failed to complete successfully.

adding the possibility to ignore memory errors
this is something that would have helped me run load_dataset in a loop without errors. if you think this behavior would be better handled by the library user, that makes sense to me as well. it is possible that mit-d3m would want to handle this instead of the user, in a way similar to pandas low_memory=True, by sacrificing time for memory in extracting files or by downloading files into separate chunks on disk.

thank you for your review, let me answer some of your high-level questions here, then i will respond inline above.

Fair points!
If anything, related to the memory errors, I think that it would be better to expect the user to handle it.
At the end, even if we control the error, they still need to check the return value individually to see if something was returned or not. Also, in this case we are handling MemoryErrors, but some other unrecoverable things could happen, like an invalid dataset name (user provded list of names, and you do not want to cut the process if one name is wrong).
So I think it's better if the users add their try/except blocks to control what they want.

So I think it's better if the users add their try/except blocks to control what they want.
done :)


Xcode 10.2 - Build Failed : Module compiled with Swift 4.2.1 cannot be imported by the Swift 5.0 compiler:

Please upgrade to frame work to swift 5 compatible.

I added support for it here:
https://github.com/ipraba/EPSignature/pull/70


Fix chaos in example code in the README

Pull Request Etiquette

[X] I have checked the PRs for upcoming features/bug fixes.
[X] I have read the contributing guidelines.

Changes

[ ] Internal code
[ ] Library interface (affecting end-user code)
[x] Documentation
[ ] Other: _____

Closes Issue: NaN
Description
This simple PR fixes 2 small aspects in example code in the README:

Curly brackets
Beginning of sentences (comments)

Consider this an addition to #2289

Thank you, but all of this is intentional/unimportant.

Braces on the same line are java convention
Spacing or casing of comments is irrelevant and a superficial change
None of this can be considered "chaos"

If this is a Java convention, why is this not case in all examples?

I don't agree with closure of this PR. I think in combination with #2289 it would improve readability. README doesn't look good right now. And if we agree with Java conventions, this should be the case in all examples - otherwise it looks carelessly.

I don't agree with closure of this PR. I think in combination with #2289 it would improve readability. README doesn't look good right now. And if we agree with Java conventions, this should be the case in all examples - otherwise it looks carelessly.

At least for the java comments I don't see much of an improvement here given it's just capitalization of a single letter that nobody should be hung up on.
Tho, I agree on the examples being onconsistent. Some have the bracket on a new lines and others don't. It looks weird and as if multiple people with their own coding style designed the readme without checking the currently used coding style...

I have plans to work on the readme, but it is currently a low priority since it does the job and other more important things are going on in my life. When I find time to work on this library, it needs to be towards getting it out of beta, which means I have to prioritize what I can spend my time on.
Ideally, I want all examples to follow the common java conventions, such as braces on the same line. If you want to make a PR specifically addressing just that, I'd be fine with merging it.
This PR, however, included both an unwanted change (moving braces on newlines) and superficial changes (casing that is irrelevant) so there is really no motivation to accept it.
The other PRs regarding grammar are mostly nitpicking, and I plan on reworking the readme anyway when the beta is completed. I keep that PR open to signal that I'm aware it's not perfect, but also not a priority at this time. For now, it is good enough to give an overview of the library and links to relevant other sources like the wiki and documentation.


Configurations and Projects/Colutions Oh My...

The VS GUI allows you do delete a Solution config, but that does not iterate through projects. I want to delete "ALL" project configurations and platforms except for a specific one...
I can iterate through them and identify them, but can not find the object to call a "remove like" method on...
               var allprojectConfigs = data.ProjectItemsConfigs.ToList();                 List<ProjectItemCfg> toRemove = new List<ProjectItemCfg>();                 foreach (ProjectItemCfg projectConfig in allprojectConfigs)                 {                     if (projectConfig.projectConfig.Platform == "x64")                     {                         Microsoft.Build.Evaluation.Project loadedProject = sln.Result.Env.GetOrLoadProject(projectConfig.project);                         toRemove.Add(projectConfig);                     }                 }                 // OK, now kill everything in the "toRemove" list"

Additional info... This would also need to remove any other elements that were specific to the removed configuration/platform.  At this point pretty sure that the package does not support this as a single call (but still hopeful), but perhaps someone has previously developed a snipped and can share.

How about
using var sln = new Sln(@"D:\prg\issues\MvsSln\issue40\TestStruct\TestStruct.sln", SlnItems.Env);
sln.Result.Env
    .LoadProjects(sln.Result.ProjectItemsConfigs.Where(p => p.solutionConfig.Platform == "x64"))
    .ForEach(xp => // TODO: more like we need add this as part of MvsSln, https://github.com/3F/DllExport/blob/c1cc52fa13f563f97a2b4fe08bfb541c69195866/Wizard/Extensions/XProjectExtension.cs#L121
        xp.Project.Xml.PropertyGroups.Where(p =>
                // NOTE: projectConfig should contain default IRuleOfConfig impl to avoid misunderstanding between "Any CPU" and "AnyCPU", or like;
                // MS "Any CPU" bug was described here: https://github.com/3F/vsSolutionBuildEvent/issues/14#issuecomment-246419276
                p.Condition.Contains($"'{xp.ProjectItem.projectConfig.ConfigurationByRule}|{xp.ProjectItem.projectConfig.PlatformByRule}'")
        )
        .ForEach(p => p.Parent?.RemoveChild(p))
        .E(_ => xp.Save())
    );

NOTE: The Project Configuration/Platform most likely does NOT exist in the Solution!!!!!!

Make sure about the "Any CPU" / "AnyCPU". You can simply use the default rules or implement something for the mentioned IRuleOfConfig

This would also need to remove any other elements that were specific to the removed configuration/platform.

Just add something else together with PropertyGroups logic above


Documentation...

i can't seem to find any mention of what OS  or Environment this needs to run on or its dependencies needed to install.
i do have the capability to run any OS as my PC is pretty much Virtualised. so which is best?
secondly is there a mode that will download *All Anime (inc. OVA, Specials, Movies etc)?

Hi @hi5kba. This is a pure Python library with no dependencies so it can be run in any environment.


ntfs mountpoints

Mountpoints of ntfs partitions/ file systems are not displayed.
This is because mount will only output "/dev/fuse" instead of a device name like "/dev/ada0p3".
I don't know how to work around that, yet.

So for the forseeable future, mounting/unmounting ntfs will not be supported. Closing this.


Default-named functions can't be found with BinaryView.get_symbols_by_name

Repro:

Open a function that's auto-named by Binary Ninja that's of the format sub_XXXXXX.
In the python shell: bv.get_symbols_by_name(current_function.name)
Result is []

Additionally, these symbols are not returned with a call to BinaryView.get_symbols()

That's because those aren't actually symbols. They're what are rendered if you don't have a symbol. You can see that by creating a symbol then deleting it. It will revert back to that auto-name.
That's currently by design -- is there a reason that doesn't work for something you're working on?

That makes sense.
The replacement function view that I made currently relies on BinaryView.get_symbols_by_name to find the address of the function to navigate to. Looking around some more, I could use BinaryView.functions, and check each name individually, which shouldn't be too bad unless there are a ton of functions.

I'm going to mark this as closed since the behavior is intended.
syms = [x for x in bv.functions if x.name == TARGET] works just fine for what I'm doing.

Sorry for the delay, dodging hurricanes. ;-)
I'm still a bit confused as to the original use case. If you've already got current_function.name, what do you need to lookup the function for that name? You've already got current_function...

No problem :)
So, current_function.name is a bit of a simplification of what I was trying to do. In my Function List UI modification, I replace the QListView with my own QTableView and install a QSortFilterProxyModel in between the existing model on the QListView, and my new QTableView (I wanted to be able to sort functions by name on top of the filtering).
The original Model (which I'm piggybacking on), only contains the text that corresponds to the name field in the Python Function class (I feel like this is a poor explanation, but I'm not sure how else to word it...). That name field is generated from some Symbol stuff that I didn't feel like diving through, but from what you said, and what I saw, it creates a temporary Symbol on the fly that's thrown away afterwards.
Since I don't have access to the internal Binary Ninja functions that navigate to a function based on the model index that's selected, I'm stuck looking up the function by name using the current BinaryView. I could probably instead look at "sub_FUNCNAME".split("_")[0], but that looks super hacky.
Now, while typing this up, I realized that I could likely be able to invoke the goToFunction(QModelIndex) slot through the Meta Object system, so I'm going to look at doing that instead :) (Maybe, I've been having issues with signals & slots from PyQt)


fix: Persist description and logo_url to plugin lock files

This PR resolves #6914. Also despite me not changing methods or local variables the pre-commit hooks failed with:
trim trailing whitespace.................................................Passed
fix end of files.........................................................Passed
check yaml...........................................(no files to check)Skipped
check for added large files..............................................Passed
check for merge conflicts................................................Passed
check toml...........................................(no files to check)Skipped
debug statements (python)................................................Passed
eslint...............................................(no files to check)Skipped
black....................................................................Passed
isort....................................................................Passed
flake8...................................................................Failed
- hook id: flake8
- exit code: 1

src/meltano/core/plugin/base.py:67:1: WPS214 Found too many methods: 8 > 7
class PluginType(YAMLEnum):
^
src/meltano/core/plugin/base.py:606:5: WPS210 Found too many local variables: 6 > 5
    def extra_settings(self):
    ^

I think this is good to take a look at. Wondering if I missed anything?

Thanks @DanielPDWalker!


feat(support-tags) add protocol and run_on tags to Plugins WiP

NOTE: Please read the CONTRIBUTING.md guidelines before submitting your patch,
and ensure you followed them all:
https://github.com/Kong/docs.konghq.com/blob/master/CONTRIBUTING.md
Summary
Protocol tags (http/stream/stream + http) display in the hub cards:

Both protocol and layer tags display on plugin detail page sidebar:

Full changelog

edited hub_cards.html to conditionally include protocol tag
edited extension.html to conditionally include both protocol and layer tags
edited /hmac-auth/index.md as an initial example
updated hub.css for card styles

Checklist:

[x ] Commit message & atomicity checked
[ ] Documentation N/A
[x ] Spellchecked my updates
[ ] Ready to be merged

@adamjkuhn I've added the new keys+values to the "fill in the blanks" page for new hub additions, I've moved the keys/values to the correct place, and I've added some more examples while we are testing.

@coopr I've updated the values to properly display both in the Hub cards and the plugin detail page sidebars, let me know if this requires further attention. I did remove the fixme comments under the assumption the three examples were properly tagged.

It'd be good to leave in the FIXMEs in - as pretty much all of this needs a check-in Core and/or OCTO, and every plugin needs to be reviewed, before we ship this.

@coopr the FIXMEs are back- if anything else requires attention please let me know.

Updated to new run_on terminology.

@adamjkuhn is this still a valid change that needs to get merged in?

@adamjkuhn is this still a valid change that needs to get merged in?

I think we can kill this, I believe it's no longer valid.


[move stdlib] Remove the store ability requirement from account resource function

Motivation
To keep compatibility with the Move borrow_global|move_to|move_from instruction, we need to remove the store ability requirement from the account resource function. In the future, we can support auto convert borrow_global to account::borrow_resource.
public fun borrow_resource<T: key + store>(account: address): &T

to
public fun borrow_resource<T: key>(account: address): &T

How can we remove store ability as T is stored in object field, which requires store ability?

Use the object module's internal functions.
fun add_field_internal<T: key, K: copy + drop, V>(obj_id: ObjectID, key: K, val: V)

make it public(friend).
public fun account_move_resource_to<T: key + store>(self: &mut Object<Account>, resource: T){
      assert!(!object::contains_field(self, key<T>()), ErrorResourceAlreadyExists);
      object::add_field(self, key<T>(), resource)
   }

to
public fun account_move_resource_to<T: key>(self: &mut Object<Account>, resource: T){
      assert!(!object::contains_field(self, key<T>()), ErrorResourceAlreadyExists);
      object::add_field_internal(object::id(self), key<T>(), resource)
   }

The V of FieldValue<V> does not require any ability.
struct FieldValue<V> has key, drop, store {
    val: V
}

It should be worked.


Does this still work...?

Sorry, this is not really an issue as much as a generic info request...
Does this code still work, as far as you know? I tried rewriting it and the DiffChecker api always returns 413 "payload too large". I'm comparing pdfs that are barely 250kb so I doubt I'm hitting any size limit -- unless the limit is now 0 for people with free accounts...?
Thanks in advance for any info you might have.

Hey, wow I haven't used this (or DiffChecker) for ages so I've got no idea. I could probably do with updating this as the code is kind of awful. Give me a few minutes to check. 👍🏻

Thanks for the quick reply! So it's not just me then 😅


Error when run composer require with Symfony 5.2.10

I tired to install the bundle with a fresh empty project Symfony version 5.2.10.
when i ran this command
composer require youshido/graphql-bundle
i got this error

Configuring youshido/graphql-bundle (>=v1.4.1): From auto-generated recipe
Executing script cache:clear [KO]
[KO]
Script cache:clear returned with error code 255
!!
Script @auto-scripts was called via post-update-cmd

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
`

`

I have the same problem 😢

Solution:
https://github.com/youshido-php/GraphQLBundle/pull/80/commits/8a56e4a81ccd8c580e0c3dfbea14847f663c5926
https://github.com/youshido-php/GraphQLBundle/pull/84/commits/8d848d03ba73e32313814f462449358f97613acc


Unsatisfiable when-clause is ignored, command is shown anyways

I am working on an extension, which should have a command which is not available in the command palette, but accessible through the context menu. However, when I build my extension the command is shown in the command palette: I have the following package.json;
{
    "name": "testextension",
    "version": "1.0.0",
    "publisher": "Myself",
    "engines": {
        "vscode": "^1.60.0"
    },
    "contributes": {
        "commands": [
            {
                "title": "MyCommand",
                "command": "testext.domycommand",
                "category": "test",
                "when": "0 == 1"
            }
        ],
        "explorer/context": [
                {
                    "when": "resourceExtname == .zip && !inDebugMode",
                    "command": "testext.domycommand",
                    "group": "navigation"
                }
        ]
    }
}

It should be evident that "when": "0 == 1" is not satisfiable, however I am still seeing the command in the command palette. Is this a known issue and is there a mitigation or fix available?
This also happens with "when": "false".

Also seeing this for my extension on the latest insider and stable:
Version: 1.67.0-insider (system setup)
Commit: 27dd7b41b6a830d5ea8eb896d5b2bb9c4bcd95ee
Date: 2022-04-12T18:38:45.140Z
Electron: 17.4.0
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000
Version: 1.66.2 (system setup)
Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977
Date: 2022-04-11T07:46:01.075Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000

@alexdima I was wondering if there are current plans to fix this? This is frustrating to work around.

Okay so I see what had happened, my problem was actually a case of 2 things which I had not accounted for in my example:

I had 2 commands with very similar names, say cmd1 and cmd2. cmd1 was listed explicitly in contributes.menus.commandPalette, cmd2 was not but apparently items in contributes.commands surface to the palette anyway so I was seeing cmd1 and cmd2
Because cmd2 was not explicitly listed in contributes.menus.commandPalette, and "when" does not apply to items in contributes.commands, the condition was not being followed

Is the implicit surfacing from contributes.commands to the command palette documented anywhere? If not, I suggest improving the docs, otherwise my issue is resolved without need for further action.


Docker ElasticSearch misconfiguration

Describe the bug
When running using the docker image (explained here),  indexes configuration on ElasticSearch includes one replica. Since ES instance is only one, this statemente cannot be fulfilled correctly, so ES health will always be yellow, instead of green.
Since ES health can only achieve yellow status, only first docker-compose up execution results on successful conductor server start, but further restarts will only result on failure due to unhealthy ES status.
Details
Conductor version: main branch
Persistence implementation:
Queue implementation:
Lock:
Workflow definition:
Task definition:
Event handler definition:
To Reproduce
Steps to reproduce the behavior:

follow (Use the pre-configured Docker image)[https://netflix.github.io/conductor/server/#3-use-the-pre-configured-docker-image] instructions and setup for the first time your docker image, even call the docker-compose up to start your server for the first time.
After conductor is up and running, control the ElasticSearch instance health by navigating to: http://localhost:9200/_cluster/health, you will probably get something like:

{
"cluster_name": "docker-cluster",
"status": "yellow",
"timed_out": false,
"number_of_nodes": 1,
"number_of_data_nodes": 1,
"active_primary_shards": 25,
"active_shards": 50,
"relocating_shards": 0,
"initializing_shards": 0,
"unassigned_shards": 25,
"delayed_unassigned_shards": 0,
"number_of_pending_tasks": 0,
"number_of_in_flight_fetch": 0,
"task_max_waiting_in_queue_millis": 0,
"active_shards_percent_as_number": 100
}

So, cluster status is yellow since the replica shards required by conductor when creating the indexes cannot be assigned.
3. Now stop the docker_conductor-server_1 server from docker and restart it.
4. See docker_conductor-server_1 logs by login into the instance and doing:
# tail -f app/logs/server.log

You may need to wait till 30 seconds to see the exception thrown from conductor server about a timeout waiting for ES's health status.
Expected behavior
Docker image out of the box should configure indexes without replica shards since only 1 ES instance is started.
Additional context
I will attempt to update the issue with a potential fixing commit.

Closed by #2590


Implement trial views

Trial views
        Forced choice (2 alternatives)
        Sentence choice
        Image selection
        Textbox Input task
        Slider rating
        Dropdown choice
        Rating scale
        Key press

@michael-franke Do you think it would be useful / desirable to support views that look like this? I.e. with multiple responses per view.

This could be very useful, especially if generalized to different types of questions. Currently the postSurvey view has a bunch of these lumped into one view. It’s very inconvenient presently to customize this, as it entails adding HTML and JS for response handling, with the usual book-keeping entailed. So, if a generalzation of this could cover a more flexible post-survey view, that would already be very helpful.

On 14. Jul 2020, at 18:26, Marcel Klehr<EMAIL_ADDRESS>wrote:
@michael-franke Do you think it would be useful / desirable to support views that look like this? I.e. with multiple responses per view.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Bag repartition can increase, docstring implies otherwise

The original issue https://github.com/dask/dask/issues/1699 solves being able to repartition a bag into more partitions (useful after a flatten() for example).
However, the doc string wasn't updated as part of the PR - it says: "Coalesce bag into fewer partitions."
I would suggest updating it to "Change number of partitions of bag". Happy to do a PR for it.
A similar fix was applied to dataframe for https://github.com/dask/dask/issues/3439

That would be great.  Thank you Adam
On Fri, Nov 8, 2019 at 6:12 AM Adam Faulconbridge<EMAIL_ADDRESS>wrote:

The original issue #1699 https://github.com/dask/dask/issues/1699
solves being able to repartition a bag into more partitions (useful after a
flatten() for example).
However, the doc string wasn't updated as part of the PR - it says:
"Coalesce bag into fewer partitions."
I would suggest updating it to "Change number of partitions of bag". Happy
to do a PR for it.
A similar fix was applied to dataframe for #3439
https://github.com/dask/dask/issues/3439
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/5570?email_source=notifications&email_token=AACKZTAAOSNFFDF3TM2XG6DQSVXUNA5CNFSM4JKXXUG2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HX7D4HA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTCCGTBLMPIARI2XMCLQSVXUNANCNFSM4JKXXUGQ
.


Justify the use of the method ValidateInterfaces

Inside the WorkBench class, we have a method called ValidateInterfaces:
https://github.com/Avanade/Liquid-Application-Framework/blob/d625dff6d3af90fc9aba210f8898564b7b4f02c7/src/Liquid.Base/WorkBench.cs#L100-L105
It checks if the type T implements the interface name you passed as a parameter. If it doesn't, it throws an ArgumentException.
Besides that, there are other methods to set up Workbench services (such as repository or message bus):
https://github.com/Avanade/Liquid-Application-Framework/blob/d625dff6d3af90fc9aba210f8898564b7b4f02c7/src/Liquid.Base/WorkBench.cs#L64
https://github.com/Avanade/Liquid-Application-Framework/blob/d625dff6d3af90fc9aba210f8898564b7b4f02c7/src/Liquid.Base/WorkBench.cs#L70
These methods also accept a generic type parameter which will be instantiated at runtime (new T()), but before instantiating them, they call ValidateInterfaces and pass their generic constraint as a parameter. Take the UseRepository as an example:
https://github.com/Avanade/Liquid-Application-Framework/blob/d625dff6d3af90fc9aba210f8898564b7b4f02c7/src/Liquid.Base/WorkBench.cs#L64-L68
Notice how it calls ValidateInterfaces<T>(nameof(ILightRepository));?
Is it necessary though? Since the methods already have generic constraints, it's impossible to violate them (not even via Reflection).
We just can't call WorkBench.UseRepository<string>() for example, because string does not meet the generic constraints, so the call to ValidateInterfaces seems to have no real use.

I agree that the call is unnecessary. Since those methods should only be called on application startup, the impact of the check is minimal, so this is an improvement and not a bug.
Also easy to validate a PR in this case, since we should just be removing the call to ValidateInterfaces.
Also, we must check if the method is used in some other place - if that's no the case, we should also remove it altogether.


Please solve my problem

Exception has occurred.
NoSuchMethodError (NoSuchMethodError: The method 'image' was called on null.
Receiver: null
Tried calling: image())

I'm going to need a lot more information to act on this, with the information you've posted it's not even clear whether this is a drift issue. What query are you running and why are you expecting image to be non-null? Is there a stack trace pointing towards drift?

Exception has occurred.
DioException (DioException [bad response]: This exception was thrown because the response has a status code of 404 and RequestOptions.validateStatus was configured to throw for this status code.
The status code of 404 has the following meaning: "Client error - the request contains bad syntax or cannot be fulfilled"
Read more about status codes at https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
In order to resolve this exception you typically have either to verify and fix your request code or you have to fix the server code.
)


added the test for colony method

i added a test file for our add_ants method in the colony class
however, i came upon an assertion error that i think is being caused by the method itself in the colony class.
i tried to debug but couldn't really find a solution to my problem, maybe someone has ideas as to how i can fix the error?
thanks :)
edit: regarding the assertion error, line 12 in test_colony.py file

Good job:)
I have modified the code a bit by now immediately checking if there are exactly colony.amount many ants in the colony. Notice that the add_ants() method is executed directly when the colony object is initialized. Then the list of ants is emptied and the method is executed manually with new values.
All tests are now passed.

Do you mean this line @honnigmelone:
assert ant.coordinates == (colony.coordinates[0] + 50, colony.coordinates[1] + 50)?
The +50 comes from the fact that the image for the colonies is 100x100 pixels in size and the coordinates of the colonies must be in the bottom left corner of the image. However, for the ants to appear in the center of the image, their coordinates must be extended by half the size of the image in both directions. These extensions depend on the size of the image of the colonies. You could of course replace the +50 with +colony.size[0]/2, but at the moment the size is not taken into account in the gui.

Hey @Jonah-gr, thanks for the detailed reply :) Yes, i mean that line.
I understand what you mean. I meant to just put it as a variable like colony_offset= 50  and then + colony_offset. This would just be for readability purposes and would not be that important for now. I wanted to mention it already 😄


add github action to auto-approve dependabot PRs

What's being changed:
Adding a Github Action to auto-approve Dependabot PRs to make managing dependency upgrades a bit easier

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

Very needed - thank you!


3.0 - Claims panic

Hey!
I'm trying out the 3.0.0 release, works perfectly fine except one thing, I can't read the claims.
Panic: jwt.Claims is *jwt.StandardClaims, not jwt.StandardClaims
Code is pretty much the same as it is in the readme.
token, err := jwt.ParseWithClaims(t, keyFunc, &jwt.StandardClaims{})
claims := token.Claims.(jwt.StandardClaims)
fmt.Println(claims.Subject)

Any idea how to fix it? Or should I just go back to 2.0 for the time being?

claims := token.Claims.(jwt.StandardClaims) should be claims := token.Claims.(*jwt.StandardClaims) - note the asterisk denoting a
pointer during the type assertion. You can guard against panics like
this by using the claims, ok := token.Claims(someType) idiom as per
https://golang.org/ref/spec#Type_assertions
On Fri, Oct 2, 2015 at 10:08 AM orangesoup<EMAIL_ADDRESS>wrote:

Hey!
I'm trying out the 3.0.0 release, works perfectly fine except one thing, I
can't read the claims.
Panic: jwt.Claims is *jwt.StandardClaims, not jwt.StandardClaims
Code is pretty much the same as it is in the readme.
token, err := jwt.ParseWithClaims(t, keyFunc, &jwt.StandardClaims{})claims := token.Claims.(jwt.StandardClaims)
fmt.Println(claims.Subject)
Any idea how to fix it? Or should I just go back to 2.0 for the time being?
—
Reply to this email directly or view it on GitHub
https://github.com/dgrijalva/jwt-go/issues/89.

Bah, thanks. Need to update the readme though!


Consideration section confusing

Lines 3 and 4 under the Considerations section of this page are confusing and not entirely clear.
Line 3 states : "When piloting, you'll be removing a test OU or group from Microsoft Entra Connect Sync scope. Moving objects out of scope leads to deletion of those objects in Microsoft Entra ID."
Then it goes on to say "A new link type has been introduced in Microsoft Entra Connect Sync, which will prevent the deletion in a piloting scenario."
Which is it? Will users, contacts, and/or groups be deleted using the steps on this page or not?
In then continues on Line 4 "Ensure that the objects in the pilot scope have ms-ds-consistencyGUID populated so cloud sync hard matches the objects." and then "Note: Microsoft Entra Connect Sync does not populate ms-ds-consistencyGUID by default for group objects." - What is the ramification or impact if group objects that were already synced using Entra Connect don't have ms-ds-consistencyGUID populated, and we sync it w/ Cloud Sync agent?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 18b71563-7abc-70d2-822b-61131f0e6216
Version Independent ID: 15c0d747-c0eb-95b9-1cd3-4601ebcff14b
Content: Tutorial - Migrate to Microsoft Entra Connect cloud sync for an existing synced AD forest - Microsoft Entra
Content Source: articles/active-directory/hybrid/cloud-sync/tutorial-pilot-aadc-aadccp.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@bdmcti
Thanks for your feedback! We will investigate and update as appropriate.

@bdmcti
Thank you for bringing this to my attention. I can understand how the wording in lines 3 and 4 of the Considerations section of the page you mentioned can be confusing.
To clarify, when piloting Azure AD Connect Cloud Sync, you may need to remove a test OU or group from the Microsoft Entra Connect Sync scope. If you move objects out of scope, it can lead to the deletion of those objects in Microsoft Entra ID. However, a new link type has been introduced in Azure AD Connect Cloud Sync that can prevent the deletion of objects in a piloting scenario. Therefore, it is important to ensure that you are using the correct link type when piloting Azure AD Connect Cloud Sync.
Regarding the ms-ds-consistencyGUID attribute, it is important to ensure that the objects in the pilot scope have this attribute populated so that cloud sync can hard match the objects. If group objects that were already synced using Entra Connect do not have the ms-ds-consistencyGUID attribute populated, and you sync them with the Cloud Sync agent, it may result in duplicate objects being created in Azure AD. Therefore, it is recommended to ensure that the ms-ds-consistencyGUID attribute is populated for all objects before syncing them with the Cloud Sync agent.
I hope this clarifies the issue. Let me know if you have any other questions or concerns.

@AjayBathini-MSFT - I think this would be helpful clarifying info to update the article with. I think further info and expanding upon the statement "Microsoft Entra Connect Sync does not populate ms-ds-consistencyGUID by default for group objects" would be helpful also. Can that statement be linked to an article that explains how to populate ms-ds-consistencyGUID using existing Connect Sync that is in place?

@bdmcti
I will pass your feedback to author regarding the update.
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Speed up qdac initialisation

Currently setting up a station containing a qdac is very slow.
This is due to getting voltage, voltage_range, current, and current_range for all channels. The time spend seems to be evenly split between these 4 parameters. There are at least to ways of speeding this up.

Make the current related parameters optional (and probably off by default). Should give a factor of 2
Don't ask for voltages for each channel individually. The QDaC can return all voltages in one command which is much faster. This may be fast enough to not need the removal of currents above.
There is already partial support for this in the channelised version of the QDac driver when asking for more than one channel voltage but it needs to be integrated into the snapshot functions.

This is implemented in #686


failed to npm install paypal-checkout

It's this again: https://github.com/paypal/paypal-checkout/issues/556
npm ERR<EMAIL_ADDRESS>postinstall: `flow-typed install`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'flow-typed install'.

For the time being I am going back to 4.0.173

Weird, I wonder why this is just cropping up now again. flow-typed install has been part of postinstall for a long time. Anyway -- removing this and re-publishing until I can debug properly.

OK, republished. Can you try once more?

@bluepnume good to go! Thanks!


test: add deletion of node_modules when a PR is merged

PR that adds automatic deletion of node_modules (via rm -rf) when a PR is merged into master. This allows for users to check in node_modules to test and have us delete them in the actual source.
A likely extension of this that I'm going to work on is triggering the Action on Pull Request Comments that include something like !install and !uninstall which could then be squash merged into the repo, removing the git history of node_modules before it's checked into the default branch.

going to close this as it's relatively unnecessary


Update Login Sessions

Updates login sessions within Update Info. Adds some fixes. May not be desired to be merged until tests have been added by has been opened so other can have working code.

Thanks for the help


Error in Component Slots

Laravel Version: 9.41.0
PHP Version: 8.1.13
Database Driver & Version: MySQL v8.0

Description:
Inside my application I have an x-card component that has a slot for the footer as follows:
@if (isset($footer))
    <div {{ $footer->attributes->class('flex') }}>
        {{ $footer }}
    </div>
@endif

And I have another component in my application called x-modal-card that uses the x-card and passes the footer as follows:
@if(isset($footer))
    <x-slot name="footer">
        {{ $footer }}
    </x-slot>
@endif

But I'm having trouble passing the attributes in the x-modal-card component. I tried the following solutions:
@if(isset($footer))
    <x-slot name="footer" {{ $footer->attributes }}>
        {{ $footer }}
    </x-slot>
@endif

@if(isset($footer))
    <x-slot name="footer" {{ $footer->attributes->toHtml() ?? '' }}>
        {{ $footer }}
    </x-slot>
@endif

@if(isset($footer))
    <x-slot name="footer" {{ $footer->attributes->getAttributes() ?? [] }}>
        {{ $footer }}
    </x-slot>
@endif

But all of them didn't work and returns error.
Images:

That's how it works:

Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to open up a new issue with a link to the original one and we'll gladly help you out.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!


A way to track S3 download/upload, for UI progress bars

I'm writing a macOS app that uploads files to S3. It seems like with the putObject operation there is no way to watch the byte-by-byte progress. On a slow internet connection, an upload can take some time (10-20+ seconds), even when the file is too small for a multipart upload.
I'd like a way to pass a callback into the putObject function, maybe part of the struct S3.PutObjectRequest. That callback would get called frequently, with info about how many bytes have been uploaded. This would allow me to implement a progress indicator in the user interface.
I'm focused on putObject, but obviously other operations could have a similar thing.

If you are using v4.9 or earlier then no. There is no way to do this.
If you are using the v5.0 beta then you can use the streaming request payloads to do this. See here for details on how it works. The .fileHandle payload mentioned in this article also takes a callback closure which is updated with how much of the file has been uploaded. As an aside if you want to cancel an upload you can throw an error from this callback.
Also if you are uploading files larger than 5mb then you can use the multipart upload which also provides progress callbacks.

Hi @rnikander do you need any more info? Are you able to move to the v5 beta to take advantage of the streaming functionality?

Yes, I can use the v5.0. I haven't had a chance to try it out yet, but I'm sure it work. Thank you for the response!

I don't know how to use 5.0 beta. This page suggests I could use the same URL and put 5.0.0 for the version, but if I try that in Xcode I get an error "Failed to resolve dependencies ... because no versions of soto match the requirement 5.0.0..<6.0.0 and root depends on soto 5.0.0..<6.0.0, version solving failed."

Ah nevermind, I got it. Xcode has a field for "branch". I used "5.x.x" there.


record  canvas into animated gif

when record canvas into animated gif,
there are some problem,
the gif backgoundColor is black.
How to fix it.


Small build and debug message fixes

Zev;
A couple of small issues I ran into when working with the latest WHAM updates

mergeIndv requires getopt import to compile on CentOS5
Avoid large number of INFO messages when gatherBamStats does not find
useful reads.

Great.  Thanks Brad.  I don't remember WHAM printing every 100 reads, but that is silly.

To be fair, I think it only does that if you accidentally run it on single end data (whoops, testing data) and it fails over and over to find any useful reads. Thanks for merging this.

Oh, one last thing, if you don't need genotypes use -k. It will drastically decrease runtimes. You can always genotype the output after filtering using -b.


Prepare Chef 11.18.0 release

Its time
cc @opscode/client-engineers

:shipit:^2

Neat! :+1:

LGTM :shipit:

:100: :tada: :balloon:


This should add safari support (i dont have a mac so i may have to check my mom's mac to confirm)

Thanks!
I'm waiting for the check on the mac.
Also it is missing the code in index.js which calls macos.js

I don't have permissions to write in your fork @iknowthebrazil .
Anyway you have to add:
function getSafariPath() {
	//For macOS only
	return macos.getSafari() || null;
}

and then add getSafariPath to exported functions, all in index.js.

@albertopasqualetto

Good.


AssertionError: Mismatch between model and given anchor and class sizes

I have trained my YOLO model on a custom dataset, with only one class(i.e to detect the text in the scene). But now when I am running this command I am getting an error.
python yolo_video.py --model model_data/yolo.h5 --anchors model_data/yolo_anchors.txt --classes model_data/coco_classes.txt  --image --input C:\Users\HPO2KOR\Desktop\Work\venv\Patent\Dataset\Dataset\train\text\FFDDAPMDD1.png
Error :
Traceback (most recent call last):
  File "yolo_video.py", line 73, in <module>
    detect_img(YOLO(**vars(FLAGS)))
  File "C:\Users\HPO2KOR\Desktop\Work\venv\Patent\keras-yolo3-master - Copy\yolo.py", line 45, in __init__
    self.boxes, self.scores, self.classes = self.generate()
  File "C:\Users\HPO2KOR\Desktop\Work\venv\Patent\keras-yolo3-master - Copy\yolo.py", line 78, in generate
    'Mismatch between model and given anchor and class sizes'
AssertionError: Mismatch between model and given anchor and class sizes

I have seen other people also have faced similar issue but none of them is working for me.

@masterhimanshupoddar I have retrained the model in this repo for one class only too. And i havent got any errors. I did it without changing the anchors, and they work smoothly. Take a chance playing with the default anchors. they may work as you need. If not, i recomment to check the whole code for the anchors, maybe something is wrong for exactly 1 class.
In other hand, i have also trained this repo for text, and worked great.

Did you change you yolo.cfg file? for classes? I also tried with default anchors but I am getting same error.
Two questions

Did you also alter the cfg file.
Is it necessary for us to scale the custom dataset images on the same scale?

Yes, of course you need to change the CFG file. This changes depending of the classes (classes and filters will be changed).
The reescale is not need as far as I remember. because when trainning the code itself shrinks the image to the net input size. Take a look at the code in deep and you will notice that. Also remember that normally when you work with a neural network, the code must do that. You have images with diferent sizes/shapes and when training or testing (inference) the code must frist do a preprocess to make the image able to be the input of the net.

Hi, Does that means that when I'm generating the h5 file, I do not change the CFG file. Only when I've generated the .h5 file, only then do I change the anchors and classes parameter in the CFG file to match my dataset? Do I need to comment out the testing code (batch = 1, subdivisions = 1) and uncomment out the training code (batch = 64, subdivisions =16)? Thank you!

Hello, as you said, you only trained one type, but you are using the file coco_classes.txt, the content inside is more than one type, please create a new type text yourself and use it.