为什么我脚本安装了trajon-go之后链接不上？

脚本中6选项安装完之后，用v2ray客户端和igniter客户端都链接不上
账号密码都正确

在服务器 运行 systemctl status trojan-go 看看状态运行成功没？  还可以看看log显示什么？  运行cat trojan-go-access.log

[root@racknerd-afe286 ~]# cat trojan-go-access.log
[WARN]  2020/12/21 04:59:15 empty tls fallback port
[WARN]  2020/12/21 05:05:06 empty tls fallback port
[INFO]  2020/12/21 05:06:29 tcp connection from <IP_ADDRESS>:45904
[INFO]  2020/12/21 05:06:29 tls connection from <IP_ADDRESS>:45904
[INFO]  2020/12/21 05:06:39 tcp connection from <IP_ADDRESS>:45956
[INFO]  2020/12/21 05:06:39 tls connection from <IP_ADDRESS>:45956
[INFO]  2020/12/21 05:06:39 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:45956 tunneling to dns.google:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:06:44 tcp connection from <IP_ADDRESS>:45988
[INFO]  2020/12/21 05:06:44 tls connection from <IP_ADDRESS>:45988
[INFO]  2020/12/21 05:06:44 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:45988 tunneling to dns.google:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:06:50 tcp connection from <IP_ADDRESS>:46030
[INFO]  2020/12/21 05:06:50 tls connection from <IP_ADDRESS>:46030
[INFO]  2020/12/21 05:06:50 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46030 tunneling to chrome.cloudflare-dns.com:443 closed sent: 0 B recv: 557 B
[INFO]  2020/12/21 05:07:01 tcp connection from <IP_ADDRESS>:46068
[INFO]  2020/12/21 05:07:01 tls connection from <IP_ADDRESS>:46068
[INFO]  2020/12/21 05:07:01 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46068 tunneling to chrome.cloudflare-dns.com:443 closed sent: 0 B recv: 557 B
[INFO]  2020/12/21 05:07:10 tcp connection from <IP_ADDRESS>:46092
[INFO]  2020/12/21 05:07:10 tls connection from <IP_ADDRESS>:46092
[INFO]  2020/12/21 05:07:10 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46092 tunneling to chrome.cloudflare-dns.com:443 closed sent: 0 B recv: 557 B
[INFO]  2020/12/21 05:07:20 tcp connection from <IP_ADDRESS>:46150
[INFO]  2020/12/21 05:07:20 tls connection from <IP_ADDRESS>:46150
[INFO]  2020/12/21 05:07:20 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46150 tunneling to my.racknerd.com:443 closed sent: 0 B recv: 547 B
[INFO]  2020/12/21 05:07:31 tcp connection from <IP_ADDRESS>:46182
[INFO]  2020/12/21 05:07:31 tls connection from <IP_ADDRESS>:46182
[INFO]  2020/12/21 05:07:31 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46182 tunneling to android.googleapis.com:443 closed sent: 0 B recv: 539 B
[INFO]  2020/12/21 05:07:41 tcp connection from <IP_ADDRESS>:46210
[INFO]  2020/12/21 05:07:41 tls connection from <IP_ADDRESS>:46210
[INFO]  2020/12/21 05:07:41 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46210 tunneling to dns.google:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:07:50 tcp connection from <IP_ADDRESS>:46230
[INFO]  2020/12/21 05:07:50 tls connection from <IP_ADDRESS>:46230
[INFO]  2020/12/21 05:07:50 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46230 tunneling to dns.google:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:08:00 tcp connection from <IP_ADDRESS>:46250
[INFO]  2020/12/21 05:08:00 tls connection from <IP_ADDRESS>:46250
[INFO]  2020/12/21 05:08:00 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46250 tunneling to dns.google:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:08:10 tcp connection from <IP_ADDRESS>:46256
[INFO]  2020/12/21 05:08:10 tls connection from <IP_ADDRESS>:46256
[INFO]  2020/12/21 05:08:10 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46256 tunneling to chrome.cloudflare-dns.com:443 closed sent: 0 B recv: 557 B
[INFO]  2020/12/21 05:08:20 tcp connection from <IP_ADDRESS>:46268
[INFO]  2020/12/21 05:08:20 tls connection from <IP_ADDRESS>:46268
[INFO]  2020/12/21 05:08:20 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46268 tunneling to chrome.cloudflare-dns.com:443 closed sent: 0 B recv: 557 B
[INFO]  2020/12/21 05:08:30 tcp connection from <IP_ADDRESS>:46276
[INFO]  2020/12/21 05:08:30 tls connection from <IP_ADDRESS>:46276
[INFO]  2020/12/21 05:08:30 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46276 tunneling to chrome.cloudflare-dns.com:443 closed sent: 0 B recv: 557 B
[INFO]  2020/12/21 05:08:40 tcp connection from <IP_ADDRESS>:46304
[INFO]  2020/12/21 05:08:40 tls connection from <IP_ADDRESS>:46304
[INFO]  2020/12/21 05:08:40 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46304 tunneling to safebrowsing.google.com:443 closed sent: 0 B recv: 589 B
[INFO]  2020/12/21 05:08:50 tcp connection from <IP_ADDRESS>:46330
[INFO]  2020/12/21 05:08:51 tls connection from <IP_ADDRESS>:46330
[INFO]  2020/12/21 05:08:51 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46330 tunneling to www.picaacg.com:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:09:00 tcp connection from <IP_ADDRESS>:46332
[INFO]  2020/12/21 05:09:00 tls connection from <IP_ADDRESS>:46332
[INFO]  2020/12/21 05:09:00 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46332 tunneling to www.picaacg.com:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:09:10 tcp connection from <IP_ADDRESS>:46334
[INFO]  2020/12/21 05:09:10 tls connection from <IP_ADDRESS>:46334
[INFO]  2020/12/21 05:09:10 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46334 tunneling to dns.google:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:09:20 tcp connection from <IP_ADDRESS>:46358
[INFO]  2020/12/21 05:09:20 tls connection from <IP_ADDRESS>:46358
[INFO]  2020/12/21 05:09:20 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46358 tunneling to dns.google:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:09:30 tcp connection from <IP_ADDRESS>:46364
[INFO]  2020/12/21 05:09:30 tls connection from <IP_ADDRESS>:46364
[INFO]  2020/12/21 05:09:30 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46364 tunneling to dns.google:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:09:40 tcp connection from <IP_ADDRESS>:46390
[INFO]  2020/12/21 05:09:40 tls connection from <IP_ADDRESS>:46390
[INFO]  2020/12/21 05:09:40 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46390 tunneling to chrome.cloudflare-dns.com:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:09:50 tcp connection from <IP_ADDRESS>:46398
[INFO]  2020/12/21 05:09:50 tls connection from <IP_ADDRESS>:46398
[INFO]  2020/12/21 05:09:50 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46398 tunneling to chrome.cloudflare-dns.com:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:10:00 tcp connection from <IP_ADDRESS>:46406
[INFO]  2020/12/21 05:10:00 tls connection from <IP_ADDRESS>:46406
[INFO]  2020/12/21 05:10:00 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46406 tunneling to chrome.cloudflare-dns.com:443 closed sent: 0 B recv: 517 B
[INFO]  2020/12/21 05:10:06 tcp connection from <IP_ADDRESS>:46426
[INFO]  2020/12/21 05:10:06 tls connection from <IP_ADDRESS>:46426
[INFO]  2020/12/21 05:10:06 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:46426 tunneling to safebrowsing.google.com:443 closed sent: 0 B recv: 589 B
[INFO]  2020/12/21 05:10:16 tcp connection from <IP_ADDRESS>:46446
[INFO]  2020/12/21 05:10:26 user 39295aa482c43c69fe6d9554628a76457266e9e627971d0a622bfb29 from <IP_ADDRESS>:45904 tunneling to dns.google:443 closed sent: 8.86 KiB recv: 2.32 KiB
[ERROR] 2020/12/21 05:10:26 github.com/p4gefau1t/trojan-go/tunnel/tls.(*Server).acceptLoop.func1:server.go:135 tls handshake failed | read tcp <IP_ADDRESS>:443-><IP_ADDRESS>:46446: read: connection reset by peer
[WARN]  2020/12/21 05:09:23 empty tls fallback port
[INFO]  2020/12/21 05:11:26 tcp connection from <IP_ADDRESS>:55343
[ERROR] 2020/12/21 05:11:29 github.com/p4gefau1t/trojan-go/tunnel/tls.(*Server).acceptLoop.func1:server.go:135 tls handshake failed | EOF
[WARN]  2020/12/21 05:21:14 empty tls fallback port
见上文，是有什么错误吗？

看样子是连接成功了啊， 是不是Android 客户端 代理模式设置不对， 你可以找台PC 装个v2rayN 软件试试  https://github.com/2dust/v2rayN/releases

v2rayN怎么用？

PC可以连接，为什么手机不行？

PC可以连接，为什么手机不行？

应该还是手机客户端设置的问题
或者换个android 客户端 试试
https://github.com/2dust/v2rayNG
https://github.com/Kr328/ClashForAndroid/releases

换了那个torjan能连上了，是因为手机端会验证服务器时间吗？

刚v2rayNG手机端又连接上了，但是ping700多，直接ping服务器是200左右来着，之前用v2ray的时候也只有400左右，不是说trajon go是低延迟吗

能加QQ吗，有几个问题想问一下

在吗大佬？

换了那个torjan能连上了，是因为手机端会验证服务器时间吗？

肯定不是服务器时间问题， 服务器时间已经改成北京时间了

能加QQ吗，有几个问题想问一下

https://t.me/tgfcer2020  可以用电报  国内的软件不安全


Version 0.2

Reference Issues/PRs
#12 #13 #21
What does this implement/fix? Explain your changes.
Version 0.2 release PR
Any other comments?

Guys, after reviewing it, please do not merge it.

I may have a very minor PR (not sure, reviewing every single detail)

Remember to update release with current dev.

Remember to update release with current dev.
@sadrasabouri
Is it necessary? I think there is no conflict here.

Remember to update release with current dev.
@sadrasabouri
Is it necessary? I think there is no conflict here.

You can try. But I always wonder merging such a PRs. The dev that release originated from is not the same dev it's merging to.


Improve the UI of Hotel Website

The current UI of the Hotel Website isn't eye catchy. Enhance it, it must be fully responsive.

I would like to work

Can u please assign this issue to me? @VidhiBhatt01

I know UI / UX theory so i can modify it

The current UI of the Hotel Website isn't eye catchy. Enhance it, it must be fully responsive.

i can work for its design

I would like to work for this issue


Feature: Support RFM96 LoRa chip

I have custom board which using RFM96 modules. Since RFM96 is quite similar to SX127x there should not be lot of changes. I just making this as placeholder for future work on it.
I wanted show it today, but it does not work out-of-box, so before I will forgot I will make this as placeholder to remember.
now I am in boot loop
[INFO][LoRa] Set SPI pins!
Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

Core  1 register dump:
PC      : 0x400db920  PS      : 0x00060a30  A0      : 0x800d2aec  A1      : 0x3ffd1740
A2      : 0x3ffc4db4  A3      : 0x3ffc63b8  A4      : 0x3ffc4b58  A5      : 0x3f4022db
A6      : 0x3ffc6ba4  A7      : 0x3f426863  A8      : 0x00000000  A9      : 0x3ffd1720
A10     : 0x3ffc63b8  A11     : 0x0000001a  A12     : 0xffffffff  A13     : 0x0000001b
A14     : 0x0000001a  A15     : 0x0000e100  SAR     : 0x00000009  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000000  LBEG    : 0x4010dd75  LEND    : 0x4010dd84  LCOUNT  : 0x00000000

Backtrace: 0x400db91d:0x3ffd1740 0x400d2ae9:0x3ffd17c0 0x4010eb9e:0x3ffd1880

Inspiration for example in Meshastic https://github.com/meshtastic/firmware/blob/master/src/mesh/RadioLibRF95.cpp

So this is a "new" (old) board to add to tracker possibilities , right?
It seems that I runs over Radiolib and the pinouts are similar to sx1278 boards
do you have success using it on any custom code (not meshtastic?) to validate this fast?

Something like that. I have development boards before ttgo or others existed and I make break out board for rfm9x modules. And since I wanted to show aprs to one friend, who asked for it. I decide to try it on mine board as I have them and do not wanted wait 1 month for aliexpress one.
I used those boards back to 2018/2019 on TTN lorawan and later on HNT/Helium
Here I was using LMIC library with it
https://github.com/petrkr/helium-lora-sht3x

Something like that. I have development boards before ttgo or others existed and I make break out board for rfm9x modules. And since I wanted to show aprs to one friend, who asked for it. I decide to try it on mine board as I have them and do not wanted wait 1 month for aliexpress one.
I used those boards back to 2018/2019 on TTN lorawan and later on HNT/Helium
Here I was using LMIC library with it https://github.com/petrkr/helium-lora-sht3x

which pins definitions change did you change on yours to make it work?
or what did you try (and change) to know where to start(over)

Here I did fork and created new board definition
https://github.com/petrkr/LoRa_APRS_Tracker/commit/0752172b6dd1b3417398954dc4d3442c1a9f1b2a

Here I did fork and created new board definition
petrkr@0752172

this fork got the reboot loop?
but did you upload filesystem? as Lora pins definitions dont produce reboot loops :P

Filesystem? Nope :)
Time to read carefully build instructions. I had like half hour, so I did platform build and upload.
Now I am on way to HAM meetup. I will maybe have some time there too.
De OK1PKR

Check this :
tutorial-wiki

Well. Bootloop fixed, really flashing filesystem helps.
But for now really does not initialized that LoRa Radio
[INFO][LoRa] Set SPI pins!
[ERROR][LoRa] Starting LoRa failed!

Well. Bootloop fixed, really flashing filesystem helps.
But for now really does not initialized that LoRa Radio
[INFO][LoRa] Set SPI pins!
[ERROR][LoRa] Starting LoRa failed!

time to revalidate pins definitions on pins_config.h

I have to test some test code for that module to check if module itself works. Pinout is fine, checked again.
I have to check how to add some more debug output/messages. So I can try RAW SPI messages.
Anyway thank you

I have to test some test code for that module to check if module itself works. Pinout is fine, checked again.
I have to check how to add some more debug output/messages. So I can try RAW SPI messages.
Anyway thank you

let me know how the testing goes, to add this also as a valid board later ;)


Can set a default base URL

http://www.w3schools.com/tags/tag_base.asp

Useless finally + some issues with loading svg


Integration with the webpack DllPlugin

Library Affected:
workbox-webpack-plugin
@guymestef wrote at https://github.com/GoogleChrome/workbox/issues/1341#issuecomment-370746634:

I used ManifestTransform and glob* because I'm generated a vendors bundle with the DllPlugin of webpack in a separate build, in order to speed up the build of my app during development.
Is it planned or already done for workbox v3 to deal with the use of DllPlugin/DllReferencePlugin?

@guymestef, could you share the configuration you're using for DllPlugin—I gather it's in a separate webpack build?
The docs for DllPlugin are at https://webpack.js.org/plugins/dll-plugin/, and from reading that, it looks like it spits out its own manifest.json file that we might be able to repurpose as a source of files to precache.

You are right. I'm using two webpack config files:

webpack.config.vendor.js

const path = require('path');
const webpack = require('webpack');
const ExtractTextPlugin = require('extract-text-webpack-plugin');
const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin;

module.exports = (env) => {
    const analyzeBundle = env && env.analyzeBundle;
    const extractCss = new ExtractTextPlugin('vendor.css');
    return [{
        stats: {
            modules: false
        },
        resolve: {
            extensions: ['.js']
        },
        module: {
            rules: [{
                    test: /\.(png|jpg|jpeg|gif|woff|woff2|eot|ttf|svg)(\?|$)/,
                    use: 'url-loader?limit=100000'
                },
                {
                    test: /\.scss$/,
                    use: ExtractTextPlugin.extract({
                        fallback: 'style-loader',
                        use: [{
                            loader: 'css-loader',
                            options: {
                                importLoaders: 1
                            }
                        }, {
                            loader: 'sass-loader'
                        }]
                    })
                },
                {
                    test: /\.less$/,
                    use: ExtractTextPlugin.extract({
                        fallback: 'style-loader',
                        use: [{
                            loader: 'css-loader',
                            options: {
                                importLoaders: 1
                            }
                        }, {
                            loader: 'less-loader'
                        }]
                    })
                },
                {
                    test: /\.css$/,
                    use: ExtractTextPlugin.extract({
                        fallback: 'style-loader',
                        use: 'css-loader'
                    })
                },
                {
                    test: require.resolve('jquery'),
                    use: [{
                        loader: 'expose-loader',
                        query: 'jQuery'
                    }, {
                        loader: 'expose-loader',
                        query: '$'
                    }]
                },
                {
                    test: require.resolve('moment'),
                    use: [{
                        loader: 'expose-loader',
                        query: 'moment'
                    }]
                },
                {
                    test: require.resolve('knockout'),
                    use: [{
                        loader: 'expose-loader',
                        query: 'ko'
                    }]
                }
            ]
        },
        entry: {
            vendor: [
                'popper.js',
                'bootstrap',
                'bootstrap/scss/bootstrap.scss',
                'bootstrap-social',
                'knockout',
                'knockout-mapping',
                'knockout-postbox',
                'knockout.validation',
                'event-source-polyfill',
                'isomorphic-fetch',
                'jquery',

                'babel-polyfill',
                'stacktrace-js',

                'i18next',

                'jquery-validation',
                'jquery-validation/dist/additional-methods',
                'jquery-validation-unobtrusive',
                'css-toggle-switch/dist/toggle-switch.css',
                'moment',
                'tempusdominus-bootstrap-4',
                'tempusdominus-bootstrap-4/build/css/tempusdominus-bootstrap-4.css',
                'bootstrap-tagsinput',
                'bootstrap-tagsinput/dist/bootstrap-tagsinput.less',
                'font-awesome/less/font-awesome.less',
                'd3',
                'nvd3',
                'nvd3/build/nv.d3.css',
                'jquery-ui',
                'jquery-ui/ui/widgets/draggable',
                'jquery-ui-touch-punch',
                'iscroll/build/iscroll-zoom',
                'jquery.cookie',

                'offline-js',
                'offline-js/themes/offline-theme-chrome.css',

                'file-size',

                'jquery.complexify/jquery.complexify.banlist',
                'jquery.complexify',
                'jquery.payment',
                'mangopay-cardregistration-js-kit',
                'select2',
                'select2/dist/css/select2.css',
                'select2-bootstrap-theme/dist/select2-bootstrap.css',
                'openlayers',
                'openlayers/dist/ol.css',
                'google-maps',
                'clipboard',
                'lightbox2',
                'lightbox2/dist/css/lightbox.css',
                'aos',
                'aos/dist/aos.css',
                'animate.css/animate.css',
                'screenfull',
                'dotdotdot',
                'youtube-player',
                'jquery-nearest'
            ]
        },
        output: {
            path: path.join(__dirname, 'wwwroot', 'dist'),
            publicPath: '/dist/',
            filename: '[name].js',
            library: '[name]_[hash]'
        },
        plugins: [
            extractCss,
            new webpack.ProvidePlugin({
                $: 'jquery',
                jQuery: 'jquery',
                moment: 'moment'
            }), // Maps these identifiers to the jQuery package (because Bootstrap expects it to be a global variable)
            new webpack.DllPlugin({
                path: path.join(__dirname, 'wwwroot', 'dist', '[name]-manifest.json'),
                name: '[name]_[hash]'
            })
        ]
    }];
};

webpack.config.js

const path = require('path');
const webpack = require('webpack');
const CleanWebpackPlugin = require('clean-webpack-plugin');
const ExtractTextPlugin = require('extract-text-webpack-plugin');
const WebpackPwaManifest = require('webpack-pwa-manifest');
const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin;
const {
    GenerateSW
} = require('workbox-webpack-plugin');
const ForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin');
const bundleOutputDir = './wwwroot/dist';

module.exports = (env) => {
    const isDevBuild = !(env && env.prod);
    return [{
        stats: {
            modules: false
        },
        entry: {
            'main': ['./ClientApp/boot.js'].concat(isDevBuild ? ['./ClientApp/offline-simulate-ui.min.js'] : []),
            'vendor.config.fr': './ClientApp/vendor.config.fr.js',
            'vendor.config.es': './ClientApp/vendor.config.es.js',
            'vendor.config.de': './ClientApp/vendor.config.de.js',
            'vendor.config.en': './ClientApp/vendor.config.en.js',
            'vendor.config.it': './ClientApp/vendor.config.it.js',
            'vendor.config.pt': './ClientApp/vendor.config.pt.js'
        },
        resolve: {
            extensions: ['.ts', '.js', '.json']
        },
        output: {
            path: path.join(__dirname, bundleOutputDir),
            filename: '[name].js',
            publicPath: '/dist/'
        },
        module: {
            rules: [{
                    test: /locales/,
                    loader: '@alienfast/i18next-loader',
                    query: {
                        basenameAsNamespace: true
                    }
                },
                {
                    test: /\.ts$/,
                    include: /ClientApp/,
                    use: [{
                        loader: 'ts-loader',
                        options: {
                            transpileOnly: true
                        }
                    }]
                },
                {
                    test: /\.html$/,
                    use: 'raw-loader'
                },
                {
                    test: /\.scss$/,
                    use: ExtractTextPlugin.extract({
                        fallback: 'style-loader',
                        use: [{
                            loader: 'css-loader',
                            options: {
                                importLoaders: 1
                            }
                        }, {
                            loader: 'sass-loader'
                        }]
                    })
                },
                {
                    test: /\.css$/,
                    use: ExtractTextPlugin.extract({
                        fallback: 'style-loader',
                        use: 'css-loader'
                    })
                },
                {
                    test: /\.(png|jpg|jpeg|gif|svg)$/,
                    use: 'url-loader?limit=25000'
                },
                {
                    test: /\.js$/,
                    exclude: /(node_modules|bower_components)/,
                    use: {
                        loader: 'babel-loader',
                        options: {
                            presets: ['@babel/preset-env']
                        }
                    }
                },
                {
                    test: /\.worker.js$/,
                    use: [{
                        loader: 'worker-loader',
                        options: {
                            inline: true
                        }
                    }]
                },
                {
                    test: /\.html$/,
                    use: [{
                        loader: 'html-loader'
                    }]
                }
            ]
        },
        plugins: [
                new CleanWebpackPlugin([
                    'wwwroot/dist/precache-manifest.*.js',
                    'wwwroot/dist/manifest.json',
                    'wwwroot/dist/icons',
                    'wwwroot/dist/workbox*'
                ]),
                new ForkTsCheckerWebpackPlugin(),
                new webpack.DllReferencePlugin({
                    context: __dirname,
                    manifest: require('./wwwroot/dist/vendor-manifest.json')
                }),
                new ExtractTextPlugin({
                    filename: '[name].css'
                }),
                new WebpackPwaManifest({
                    filename: 'manifest.json',
                    name: 'MesHôtes.com ',
                    short_name: 'MesHôtes',
                    description: 'A wedding seating chart? A table plan for a birdthday or a gala? Make your seating plan online and let our robot Nono place your guests for you',
                    background_color: '#e71d79',
                    fingerprints: false,
                    icons: [{
                            src: path.resolve('ClientApp/css/images/icon.png'),
                            sizes: [120, 152, 167, 180, 1024],
                            destination: path.join('icons', 'ios'),
                            ios: true
                        },
                        {
                            src: path.resolve('ClientApp/css/images/icon.png'),
                            size: 1024,
                            destination: path.join('icons', 'ios'),
                            ios: 'startup'
                        },
                        {
                            src: path.resolve('ClientApp/css/images/icon.png'),
                            sizes: [36, 48, 72, 96, 144, 192, 512],
                            destination: path.join('icons', 'android')
                        }
                    ]
                })
            ].concat(isDevBuild ? [
                // Plugins that apply in development builds only
                new webpack.SourceMapDevToolPlugin({
                    filename: '[file].map', // Remove this line if you prefer inline source maps
                    moduleFilenameTemplate: path.relative(bundleOutputDir,
                        '[resourcePath]') // Point sourcemap entries to the original file locations on disk
                })
            ] : [])
            .concat([new GenerateSW({
                swDest: 'service-worker.js',
                manifestTransforms: [
                    (manifestEntries) => ({
                        manifest: manifestEntries.map((entry) => {
                            if (entry.url.startsWith('dist/')) {
                                entry.url = entry.url.replace(/^dist\//i, '');
                            }
                            return entry;
                        })
                    })
                ],
                cacheId: 'sp-admin',
                importWorkboxFrom: 'local',
                maximumFileSizeToCacheInBytes: 10 * 1024 * 1024,
                globDirectory: './wwwroot',
                globPatterns: ['**/*.{js,png,jpg,gif,ico,html,css,eot,svg,ttf,json}'],
                globIgnores: [
                    '**/vendor-manifest.json',
                    '**/workbox*.js',
                    '**/*.hot-update.js',
                    '**/*.hot-update.json',
                    '**/precache-manifest.*.js'
                ],
                clientsClaim: true,
                skipWaiting: true
            })])
    }];
};

When I'm adding a vendor that I know will be fully embedded in my app, I add it to the list in webpack.config.vendor.js.
And I run webpack to generate vendor.js, vendor.css and copy to dist folder all required files (images, font, ...). Webpack DllPlugin generate a vendor-manifest.json file that will be used by DllReferencePlugin in the webpack.config.js build.

in order to speed up the build of my app during development

The DllPlugin is really only used for development right?
In production either CommonChunksPlugin (webpack 3) or splitChunks (webpack 4) are used for more optimised code splitting
What is the benefit of combining DllPlugin and Workbox in development?

DllPlugin + Workbox is not a production scenario, any bugs are a time sink
Assume adding Workbox does not increase developer iteration speed
If you are already willing to alter how development operates compared to production for compile speed, why not also drop the requirement for service worker testing, to make core development as streamlined as possible

Instead, maybe create a third webpack environment, an extra DEV configuration, so service worker testing is verifying the actual chunks you are expecting in production.
It may be a little slower to compile without DllPlugin, but at least you are testing closer to the chunks you expect in production
eg

DEV1 with DllPlugin = fast compile + hot etc
DEV2 with chunks and workbox = slower compile + test service workers + hot etc
PROD with chunks and workbox

Since my previous post, I've implemented splitChunks too.
DllPlugin allows to pre-built dependencies in a separate bundle and optimizations are applied on the generated bundle as well, like for a classic webpack build (except for tree shaking of course).
So basically, I've:

DEV: DllPlugin, Hot, workbox
PROD: DllPlugin, splitChunks, workbox

I agree that in PROD, DllPlugin can be just removed to only use splitChunks (probably better optimizations with tree shaking, ...)
But I prefer to keep workbox in DEV to have a DEV env as close as possible as the PROD env. For workbox, it allows to see the impacts/side effects of runtime caching during the development of a feature, instead of discovering them after the development while testing the app. (I'm experimenting caching on particular GET requests on my app)
And I don't think having multiple DEV configurations is a good idea, since I'm sure that people will always use the same one.

Oh you are using DllPlugin in PROD, makes sense now for the service workers, please ignore my comment.
I recommend to you thought, being able to swap between multiple DEV configs. Optimal dev tool operation generally conflicts with configuration required by other dev tools. Compile speed vs runtime speed vs bundle size vs source map vs HMR vs service worker ... etc

This issue's been open for a few years now, and my hope is that it's addressed by the workbox-webpack-plugin v5. Please give it a try with v5, and if it's still an issue, we can reopen this bug.

so i have this problem still. im using "workbox-webpack-plugin": "^5.1.4"
basically we have a vendor build and an app build:
# from vendor
                                    Asset      Size  Chunks                                Chunk Names
     205f07b3883c484f27f40d21a92950d4.ttf   200 KiB          [emitted]
     2f12242375edd68e9013ecfb59c672e9.svg   730 KiB          [emitted]              [big]
     3602b7e8b2cb1462b0bef9738757ef8a.svg   141 KiB          [emitted]
    4451e1d86df7491dd874f2c41eee1053.woff   102 KiB          [emitted]
     664de3932dd6291b4b8a8c0ddbcb4c61.svg   896 KiB          [emitted]              [big]
     8300bd7f30e0a313c1d772b49d96cb8e.ttf   133 KiB          [emitted]
     8ac3167427b1d5d2967646bd8f7a0587.eot   200 KiB          [emitted]
     e2ca6541bff3a3e9f4799ee327b28c58.eot   134 KiB          [emitted]
           vendor.7b437f303d916fdefeca.js   293 KiB       0  [emitted] [immutable]  [big]  vendor
                               vendor.css  2.73 MiB       0  [emitted]              [big]  vendor

# from build
                                 Asset      Size  Chunks                                Chunk Names
                               my.docx    15 KiB          [emitted]
                             my_logo.png  11.4 KiB          [emitted]
                              favicon.ico  1.12 KiB          [emitted]
                          header_logo.png    27 KiB          [emitted]
                               index.html   1.3 KiB          [emitted]
                        main~19a26b3e.css  49.2 KiB       0  [emitted]                     main~19a26b3e
    main~19a26b3e.f2ab6cc05c381c176983.js  7.71 MiB       0  [emitted] [immutable]  [big]  main~19a26b3e
    main~203e0718.62b9033a01ff8309f310.js    13 MiB       1  [emitted] [immutable]  [big]  main~203e0718
    main~678f84af.485197aa3ff38c5d892a.js  13.4 MiB       2  [emitted] [immutable]  [big]  main~678f84af
    main~748942c6.446315a7970b3be9bcf8.js  6.62 MiB       3  [emitted] [immutable]  [big]  main~748942c6
    main~b5906859.e5e8694f638ec4597190.js   766 KiB       4  [emitted] [immutable]  [big]  main~b5906859
    main~fdc6512a.2ecc0d9a19eabd4bc993.js   5.8 MiB       5  [emitted] [immutable]  [big]  main~fdc6512a
                                    sw.js   710 KiB          [emitted]              [big]

everything is configured correctly i assume, because all of our vendor packages imports work like vuex, bootstrap, etc.
plugins: [
      new VueLoaderPlugin(),
      new CopyWebpackPlugin([
        {
          from: './ClientApp/images'
        }
      ]),
      new webpack.DllReferencePlugin({
        context: __dirname,
        manifest: require('./wwwroot/dist/vendor-manifest.json')
      }),
      new HtmlWebpackPlugin({
        title: 'MYTITLE',
        template: 'ClientApp/templates/index.template.ejs'
      }),
      new InjectManifest({
        swSrc: './ClientApp/sw/sw.js',
        swDest: 'sw.js',
        maximumFileSizeToCacheInBytes: maxChunkCacheSize
      })
    ]

this is the manifest injected into the service worker:
[
  {
    "revision": "edd825aefbed96fed840f30d2fc8a439",
    "url": "/my.docx"
  },
  {
    "revision": "128a9a1e9d08815847191ae099565c72",
    "url": "/my_logo.png"
  },
  {
    "revision": "c1ba78fd0984aa4f779cddcb042f9670",
    "url": "/favicon.ico"
  },
  {
    "revision": "7f5437f1584f0dd1ca8318224690626b",
    "url": "/header_logo.png"
  },
  {
    "revision": "4211d09469c018345b8a4fc6ea573dff",
    "url": "/index.html"
  },
  {
    "revision": "87aa2377e2defbb85a61c193eedab976",
    "url": "/main~._e.js"
  },
  {
    "revision": "8c1335d24eee765456edf3042e79c511",
    "url": "/main~._node_modules_d.js"
  },
  {
    "revision": "7d4d3bb0ef5a8c0136c2c819b5e726af",
    "url": "/main~._node_modules_v.js"
  }
]

i original attempted to use config.additionalManifestEntries but saw i needed to generate the revision information and quickly moved on. i then took a look at the config.include option thinking that it would reference additional files as well as the build assets, only to debug the code and come to the conclusion that its only for the ascertained assets from the current webpack build.
const isIncluded = !Array.isArray(config.include) || checkConditions(asset, compilation, config.include);
if (!isIncluded) {
  continue;
} // If we've gotten this far, then add the asset.
filteredAssets.add(asset);

so i borrowed some of your logic for ascertaining the asset and its hash
const bundleOutputDir = './wwwroot/dist'

const path = require('path')
const glob = require('glob')
const webpack = require('webpack')
const fs = require('fs')
const { InjectManifest } = require('workbox-webpack-plugin')
const { RawSource } = require('webpack-sources')
const getAssetHash = require('workbox-webpack-plugin/build/lib/get-asset-hash')

...
module.exports = async (env) => {

  const findVendorFiles = function (root) {
    const anyFiles = [
      // globed files from paths
      // glob does not yet support multiple extensions
      // https://github.com/isaacs/node-glob/issues/217
      { key: 'script', glob: glob.sync(`${root}/vendor.*.js`) },
      { key: 'svg', glob: glob.sync(`${root}/*.svg`) },
      { key: 'ttf', glob: glob.sync(`${root}/*.ttf`) },
      { key: 'woff', glob: glob.sync(`${root}/*.woff`) },
      { key: 'eot', glob: glob.sync(`${root}/*.eot`) }
    ]
    const files = [
      // actual files by name
      { name: 'vendor-manifest.json', path: path.resolve(`${root}/vendor-manifest.json`), url: '/vendor-manifest.json', revision: undefined },
      { name: 'vendor.css', path: path.resolve(`${root}/vendor.css`), url: '/vendor.css', revision: undefined }
    ]

    const getFileName = function (file) {
      const paths = file.split('/')
      return paths[paths.length - 1]
    }

    const onError = function (err) {
      console.error(err)
    }

    const vendorJsGlob = anyFiles[0].glob
    if (!vendorJsGlob || vendorJsGlob.length !== 1) {
      console.error('#### ANNOYING BUILD ERROR - NOT CONFIGURED FOR MULTIPLE OR NULL VENDOR.[HASH].JS FILES.', vendorJsGlob)
      console.error('#### IF YOU ARE ATTEMPTING TO CHUNK THE VENDOR PACKAGES YOU NEED TO ITERATE THE OPTIONS IN INDEX.HTML.EJS AS IT ASSUMES 1 FILE')
      throw new Error('you shall not pass!')
    }

    const promises = []

    files.forEach((file) => {
      promises.push(
        new Promise((resolve, reject) => {
          fs.readFile(file.url, (err, source) => {
            if (!err) {
              file.revision = getAssetHash(new RawSource(source))
              resolve()
              return
            }

            onError(err)
            reject(err)
          })
        })
      )
    })

    // for every data point in globs
    anyFiles.forEach((data) => {
      let { glob } = data
      // for every file found by glob
      glob.forEach((file) => {
        let name = getFileName(file)
        let url = `/${name}`
        promises.push(
          new Promise((resolve, reject) => {
            fs.readFile(file, (err, source) => {
              if (!err) {
                files.push({ name, url, revision: getAssetHash(new RawSource(source)) })
                resolve()
                return
              }

              onError(err)
              reject(err)
            })
          })
        )
      })
    })

    return Promise.all(promises).then(() => files)
  }

  const outputPath = path.join(__dirname, bundleOutputDir)
  const allVendorFiles = await findVendorFiles(outputPath)
  const vendorJsFileName = allVendorFiles.find((file) => {
    return /vendor\..*\.js/.test(file.name)
  }).name

  const additionalManifestEntries = allVendorFiles.map(({ url, revision }) => {
    return {
      url,
      revision
    }
  })

  const options = [{
    plugins: [
        new VueLoaderPlugin(),
        new CopyWebpackPlugin([{ from: './ClientApp/images', to: outputPath }], {
          concurrency: 100,
          logLevel: debug ? 'debug' : 'warn',
          copyUnmodified: true
        }),
        new webpack.DllReferencePlugin({
          context: __dirname,
          manifest: './wwwroot/dist/vendor-manifest.json'
        }),
        new HtmlWebpackPlugin({
          title: 'DCATS',
          customOptions: {
            vendorJs: vendorJsFileName
          },
          template: 'ClientApp/templates/index.template.ejs'
        }),
        new InjectManifest({
          swSrc: './ClientApp/sw/sw.js',
          swDest: 'sw.js',
          maximumFileSizeToCacheInBytes: maxChunkCacheSize,
          additionalManifestEntries
        })
      ]
}]
 ...

and behold
[
  {
    "revision": "205f07b3883c484f27f40d21a92950d4",
    "url": "/205f07b3883c484f27f40d21a92950d4.ttf"
  },
  {
    "revision": "2f12242375edd68e9013ecfb59c672e9",
    "url": "/2f12242375edd68e9013ecfb59c672e9.svg"
  },
  {
    "revision": "3602b7e8b2cb1462b0bef9738757ef8a",
    "url": "/3602b7e8b2cb1462b0bef9738757ef8a.svg"
  },
  {
    "revision": "4451e1d86df7491dd874f2c41eee1053",
    "url": "/4451e1d86df7491dd874f2c41eee1053.woff"
  },
  {
    "revision": "664de3932dd6291b4b8a8c0ddbcb4c61",
    "url": "/664de3932dd6291b4b8a8c0ddbcb4c61.svg"
  },
  {
    "revision": "8300bd7f30e0a313c1d772b49d96cb8e",
    "url": "/8300bd7f30e0a313c1d772b49d96cb8e.ttf"
  },
  {
    "revision": "8ac3167427b1d5d2967646bd8f7a0587",
    "url": "/8ac3167427b1d5d2967646bd8f7a0587.eot"
  },
  {
    "revision": "edd825aefbed96fed840f30d2fc8a439",
    "url": "/my.docx"
  },
  {
    "revision": "128a9a1e9d08815847191ae099565c72",
    "url": "/my_logo.png"
  },
  {
    "revision": "e2ca6541bff3a3e9f4799ee327b28c58",
    "url": "/e2ca6541bff3a3e9f4799ee327b28c58.eot"
  },
  {
    "revision": "c1ba78fd0984aa4f779cddcb042f9670",
    "url": "/favicon.ico"
  },
  {
    "revision": "7f5437f1584f0dd1ca8318224690626b",
    "url": "/header_logo.png"
  },
  {
    "revision": "95198d80e58c2668caf9355f102091bc",
    "url": "/index.html"
  },
  {
    "revision": "87aa2377e2defbb85a61c193eedab976",
    "url": "/main~._e.2b5c0027f1020ffd25eb.js"
  },
  {
    "revision": "8c1335d24eee765456edf3042e79c511",
    "url": "/main~._node_modules_d.ab5802ca71b75ab23c9d.js"
  },
  {
    "revision": "7d4d3bb0ef5a8c0136c2c819b5e726af",
    "url": "/main~._node_modules_v.1578962663fb55e68199.js"
  },
  {
    "revision": "7b08f859f3e7280a710eab795b31a443",
    "url": "/vendor-manifest.json"
  },
  {
    "revision": "4ba04dff11ff8916dd57b7c246aafba1",
    "url": "/vendor.css"
  },
  {
    "revision": "21eb37fdc7457781e350efaa026cc367",
    "url": "/vendor.f8532336d4a3331b4282.js"
  }
]

which i have to say is a pain in the 🤬. am i missing something like a pre InjectManifest plugin that spits out partial manifest files from previous builds that are consumed as part of the current build? If not would that be a logical way to solve this?

So another update. Looking back at our git history has revealed back when we used version 4 we depended on the following InjectManifest plugin options:
https://developers.google.com/web/tools/workbox/reference-docs/latest/module-workbox-build#.injectManifest

Parameter
Type
Description

globDirectory
string
The local directory you wish to match globPatterns against. The path is relative to the current directory.

globPatterns
Array
Files matching any of these patterns will be included in the precache manifest. For more information, see the glob primer.

When I tried to bring these values back I run into the following errors:
ERROR in Please check your InjectManifest plugin configuration:
    "globDirectory" is not a supported parameter.. "globPatterns" is not a supported parameter.

    ERROR in Cannot read property 'push' of undefined

Removing globDirectory and leaving globPatterns:
ERROR in Please check your InjectManifest plugin configuration:
    "globPatterns" is not a supported parameter.

    ERROR in Cannot read property 'push' of undefined

Both of these parameters are still in what I perceive as the latest v5 documentation:
https://developers.google.com/web/tools/workbox/reference-docs/latest/module-workbox-build#.injectManifest

After having a coworker point out that the document link above clearly references 6.1.5 🤦 I upgraded and repeated the build and still see the same error output.
// package.json versions
"webpack": "^4.44.2",
"workbox-webpack-plugin": "~6.1.5"

// package-lock.json
"workbox-webpack-plugin": {
  "version": "6.1.5",
  "resolved": "https://registry.npmjs.org/workbox-webpack-plugin/-/workbox-webpack-plugin-6.1.5.tgz",
  "integrity": "sha512-tsgeNAYiFP4STNPDxBVT58eiU8nGUmcv7Lq9FFJkQf5MMu6tPw1OLp+KpszhbCWP+R/nEdu85Gjexs6fY647Kg==",
  "dev": true,
  "requires": {
    "fast-json-stable-stringify": "^2.1.0",
    "pretty-bytes": "^5.4.1",
    "source-map-url": "^0.4.0",
    "upath": "^1.2.0",
    "webpack-sources": "^1.4.3",
    "workbox-build": "^6.1.5"
  },
  "dependencies": {
    "fast-json-stable-stringify": {
      "version": "2.1.0",
      "resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz",
      "integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==",
      "dev": true
    },
    "webpack-sources": {
      "version": "1.4.3",
      "resolved": "https://registry.npmjs.org/webpack-sources/-/webpack-sources-1.4.3.tgz",
      "integrity": "sha512-lgTS3Xhv1lCOKo7SA5TjKXMjpSM4sBjNV5+q2bqesbSPs5FjGmU6jjtBSkX9b4qW87vDIsCIlUPOEhbZrMdjeQ==",
      "dev": true,
      "requires": {
        "source-list-map": "^2.0.0",
        "source-map": "~0.6.1"
      }
    }
  }
}

webpack-config.js
new InjectManifest({
  swSrc: './ClientApp/sw/sw.js',
  swDest: 'sw.js',
  maximumFileSizeToCacheInBytes: 20 * 1024 * 1024,
  globDirectory: './ClientApp/wwwroot/dist',
  globPatterns: ['vendor.css', 'vendor.*.js']
  // additionalManifestEntries,
  // dontCacheBustURLsMatching: /(main|vendor).*\.js$/
})

npm build output
Hash: 2d9a0004d0d32492ac96
Version: webpack 4.44.2
Child
    Hash: 2d9a0004d0d32492ac96
    Time: 43542ms
    Built at: 06/16/2021 12:04:48 PM
                       Asset      Size                 Chunks             Chunk Names
                  daily.docx    15 KiB                         [emitted]
                my_logo.png  11.4 KiB                         [emitted]
                 favicon.ico  1.12 KiB                         [emitted]
             header_logo.png    27 KiB                         [emitted]
                  index.html  1.14 KiB                         [emitted]
                 main~._C.js  15.3 MiB               main~._C  [emitted]  main~._C
                 main~._e.js  7.34 MiB               main~._e  [emitted]  main~._e
    main~._node_modules_d.js   811 KiB  main~._node_modules_d  [emitted]  main~._node_modules_d
    main~._node_modules_f.js  13.2 MiB  main~._node_modules_f  [emitted]  main~._node_modules_f
    main~._node_modules_r.js  13.9 MiB  main~._node_modules_r  [emitted]  main~._node_modules_r
    main~._node_modules_v.js  6.69 MiB  main~._node_modules_v  [emitted]  main~._node_modules_v

    ERROR in Please check your InjectManifest plugin configuration:
    "globDirectory" is not allowed

    ERROR in Cannot read property 'push' of undefined

Hello @steven87vt—regarding the supported options, they're documented for v6 at https://developers.google.com/web/tools/workbox/reference-docs/latest/module-workbox-webpack-plugin.InjectManifest#InjectManifest
(you were looking at the workbox-build docs, which support a different set of parameters).
The latest version of workbox-webpack-plugin differs from v4 in that it no longer uses glob patterns against the filesystem to try to determine the list of build assets created by a webpack compilation. Instead, workbox-webpack-plugin obtains its list of assets to precache by looking at the actual assets produced by a webpack compilation.
This might lead to some different issues—like what you've identified with the DllPlugin—but at the same time, it fixed a whole class of bugs related to the plugin not picking up assets that weren't actually written to disk.

Awesome thanks for that clarification! So then additionalManifestEntries is the correct way forward with capturing that information?
If  additionalManifestEntries is the way to go my hash generation technique employed above (borrowing the hash from workbox) no longer works for me as  packages/workbox-webpack-plugin/src/lib/get-asset-hash.js changed to support webpack 5 (somewhere along the line source.source() changed to asset.source.source()). I can work around this but I feel like its probably not the correct way to go.
const fs = require('fs')
const getAssetHash = require('workbox-webpack-plugin/build/lib/get-asset-hash')

fs.readFile(path, (err, source) => {
  // getAssetHash (new RawSource(source))`
    getAssetHash ({source: new RawSource(source)})`
})

All this leads me to the question: do I even need webpack's filename hashing for browser cache in a system where sw is always loaded and calling precacheAndRoute since webpack is already providing the Asset.Info?
output: {
  "filename": "[name].[contenthash].js"
}

My root issue stems from a situation where some users get site updates and sometimes they get cached changes. Our web server (kestrel) will issue 304 responses for the same files in the manifest (it defaults to using etag headers). Does that effect sw.js precacheAndRoute(manifest) handling on page refresh (cache first?)?  When I inspect chrome's application tab/cache data the runtime cache only displays registered routes and has no manifest entries, I hope this is correct.
Maybe I should just merged the vendor and main builds into 1 build, remove the DDL plugin & turn off kestrel's etag support for anything related to index.html and hope for the best?
Any insight is appreciated.

Hi there,
Workbox is moving to a new engineering team within Google. As part of this move, we're declaring a partial bug bankruptcy to allow the new team to start fresh. We realize this isn't optimal, but realistically, this is the only way we see it working. For transparency, here're the criteria we applied:

For PRs, we closed everything that doesn't target the current v7 branch.
For Issues, we closed everything that was created before 2024.

Thanks, and we hope for your understanding!
The Workbox team


[Suggestion]Organize adopters in alphabetical order

Adopters added later, starting from iYUNDONG, are not sorted in alphabetical order.
https://milvus.io/docs/v2.0.0/milvus_adopters.md

/assign @kartikcho
(I'll push a PR in the next month for it to count towards the Hacktober contributions if it's alright!)

Hey! Can you please assign this issue to me,
I would like to work on it.

Hey @claireyuw !
Can you please assign this issue to me? I would like to work on it.

I have created a Pull Request making all the necessary changes.
Please acknowledge it @claireyuw .

@iamartyaa I have assigned the issue to you. Thank you again!


fails to build on debian mipsel

Hi,
bedtools fails to build on debian mipsel [0].
The important error message seems to be:
[...]
In file included from BinTree.h:16:0,
                 from BinTree.cpp:1:
../../utils//general/QuickString.h:41:15: error: 'QuickString& QuickString::operator=(size_t)' cannot be overloaded
  QuickString &operator = (size_t);
               ^
[...]

Do you have any idea or hint about how to solve that?
Thanks, best regards.
[0] https://buildd.debian.org/status/fetch.php?pkg=bedtools&arch=mipsel&ver=2.24.0-1&stamp=1436289056

I think commit b47dbefcb5 should address this.  Could you clone and try to compile?  Sorry, I don't have debian to test.

Thanks, it seems to work here in my mipsel machine :-)


ability to click on menu item to view recipe

In my setup, I would hang the qr code in my homebar, would be nice if I can then see the recipe for a cocktail .
If I'm correct, it should be visible already since it is included in the public facing page? https://github.com/karlomikus/vue-salt-rim/blob/00e337c94c68431d898370bc57da3cdc48d1e9bb/src/components/Menu/MenuPublicIndex.vue
however, I'm unable to see this. In that case, I'm unsure if this is a bug or something is going wrong?
Happy 2025!

Hello,
This will work if specified cocktail has a generated public link. You can generate a new public link on cocktail details page.


Remove samalba/dockerclient

Fix #1879
Finally, we can now get rid of the old docker client. One less dependency.

Ping @allencloud can you take a look? It would be nice to merge this.

Thanks for your explanation.
LGTM


codegen output e0e6ba3f12b9465bb84cb2ff665f96b1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 38.786%

Totals

Change from base Build<PHONE_NUMBER>:
0.9%

Covered Lines:
6278

Relevant Lines:
12200

💛  - Coveralls


Calendar looks blank in RTL mode

Hi folks,
I'm working on an application that supports i18n, and I tried to implement calendar-kit.
It looks fine on LTR but not on RTL.
Here is screenshot for the issue:

Current used libraries:
"react-native": "0.70.6"
"react": "18.1.0"
"@shopify/flash-list": "^1.4.1"
"react-native-reanimated": "^2.14.4"
"@howljs/calendar-kit": "^1.13.1"
....
Anyone can help or suggest a solution for me? thanks.

@howljs

@howljs Thank you for this amazing package. I really like it
and could you please help me to solve this issue?

I’m busy with my work at the company right now ☹ I’ll try to take the time to write this feature later. Sorry

Thank you @howljs for your effort.

am facing the same issue @howljs @fakhergh  any update on this ?

For me what fixed it was using direction: 'ltr' inside the Timeline style for content and container
src/components/Timeline/index.tsx
const styles = StyleSheet.create({
container: { flex: 1, direction: 'ltr' },
content: { flexGrow: 1, direction: 'ltr' },
});

@Deblancd  i believe that will work on iOS but not android

Yes I am running into this problem as well on android. It seems to work fine on IOS but the schedule does not render properly with RTL on android. Is there any fix to this other than having the user change their system language setting to something that is RTL?

Hi @derickdecesare , @Deblancd, @FadiAboMsalam , did you guys found any solution ?


Error: Expected more than 1 value per channel when training

I cannot use batch_size more than 1 when training ISBNet using this command 'python3 tools/train.py configs/scannetv2/isbnet_scannetv2.yaml --trainall --exp_name default'. Then this error occurs.
' raise ValueError("Expected more than 1 value per channel when training, got input size {}".format(size))
ValueError: Expected more than 1 value per channel when training, got input size torch.Size([1, 224])'
How to solve this error? Thanks in advance!!!!

This is because BatchNorm layer expects more than 1 batch size during training. You can try training with batch_size>=2 , or reducing max_npoint int the config file.

This is because BatchNorm layer expects more than 1 batch size during training. You can try training with batch_size>=2 , or reducing max_npoint in the config file.

I have to use batch_size=1, if not, the program will occur bugs. So I have to reduce the number of max_npoint, but which number should I set it? Reduce half of it once?

You could set max_npoint to 200k or 100k to avoid OOM during training. If you want to set batch_size=1, try freezing all BatchNorm layers during training:
for m in model.modules():
      if isinstance(m, nn.BatchNorm1d):
           m.eval()

You could set max_npoint to 200k or 100k to avoid OOM during training. If you want to set batch_size=1, try freezing all BatchNorm layers during training:
for m in model.modules():
      if isinstance(m, nn.BatchNorm1d):
           m.eval()

I wonder where these codes should be placed, which file. Thank you so much for your attention and participation.

You can put them below this line https://github.com/VinAIResearch/ISBNet/blob/7c18fdb9e68ab5f5b53c00713a659626f788d2fc/tools/train.py#L54


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter message-queue for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.message-queue
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 2.5.1 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E036] @iobroker/testing 3.0.2 specified. 4.1.3 is required as minimum,  4.1.3 is recommended. Please update devDependencies at package.json
[ ] :heavy_exclamation_mark: [E162] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E518] "@alcalzone/release-script" (>=3.0.0) is used, but ".releaseconfig.json" not found. Please create.
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2024 MK-2001<EMAIL_ADDRESS>at the end of README.md
[ ] :heavy_exclamation_mark: [E606] Current adapter version 0.0.3 not found in README.md
[ ] :heavy_exclamation_mark: [E851] .npmignore found but "files" is used at package.json. Please remove .npmignore.

WARNINGS:

[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

SUGGESTIONS:

[ ] :pushpin: [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Mon, 09 Sep 2024 04:12:57 GMT

Issue outdated due to RECREATE request. Follow up issue #102 has been created.
This issue will be closed.
your
ioBroker Check and Service Bot


Update gemspec to allow usage with Rails 5.1

Closes #204

Could you also modify the Rails dependencies in the Gemfile please? >= 4 and < 5.2 should be fine.


PT Run does not dismiss when it loses focus

Microsoft PowerToys version
0.59.1
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
This one is bugging me. Another version of this (I think underlying reasons are the same):

Open non elevated cmd
Open elevated cmd
Click the non-elevated cmd
Open PTRun*
Click the elevated cmd

I am using elevated PT, Win+Space for activation, and central kb hook

You will see that PT Run does not get dismissed.
Bonus fun: it might work for you (PT Run is hidden). If it works for you swap 3 and 5. It likely will not break (PT Run does not dismiss).
The only way I can get PT Run to reliably dismiss when it's not supposed to is to never click anything that is elevated. This is a tall order.
✔ Expected Behavior
If you click ANY window/desktop, anything that is not PT Run, PT Run should go away.
❌ Actual Behavior
Sometimes it does not. It stays on the screen and is confusing. Because it depends on the elevation level of the item you clicked it can seem random.
Other Software
No response

Are you still experiencing this issue? /needinfo

Are you still experiencing this issue? /needinfo

Yes, but it's not been a BIG deal.
https://github.com/user-attachments/assets/1fb729f5-3842-4b90-9a0e-b12ca4172d49


Make Install error on Alpine

Hi, I'm trying to install your package on Alpine version of debian (home assistant installed on raspberry 3).
I have an error when i make install :
gcc -03 -Wall -pthread -fpic -c -o pigpio.o pigpio.c
make: gcc: No such file or directory
make: *** [Makefile:48: pigpio.o] Error 127

Do you have any clue ?
Thanks

Are you doing this?
wget https://github.com/joan2937/pigpio/archive/master.zip
unzip master.zip
cd pigpio-master
make
sudo make install

Yes and the error apear on the make command

You may want to search “make error 127”.


Updated mirrors

Updated to use pypi.org mirror instead of pypi.python.org
Description
Updated the codes to use pypi.org from pypi.python.org.
Since pypi.python.org is deprecated.

Coverage increased (+0.03%) to 73.251% when pulling 67ff4924e295a6548fef05a379069865205bad68 on sourcepirate:patch-1 into 3ccf7490a8d8b8fa74a61ee39bf44234f3567739 on Miserlou:master.

@mbeacom any update on this ?

@sourcepirate Nothing I can really do...  LGTM, but I can't merge it. 😅


Add new layers in the right place

Fixes first part of #7342:

[x] Add an empty CartoDB layer instead of cloning the one at the top.
[x] Make sure layer is added below the torque layer/layer with labels.

@xavijam would you please take a look? Thx

👍  after tests say everything is 🍏

Retest this please


React-Native web3auth.login issue when redirecting back to app after login

After Successful login in the browser it redirects back to the application with an error
[TypeError: undefined is not a function]
No problem from the browser end but the app end.
Can you please help me out.
Attaching a video of app working
https://drive.google.com/file/d/1fzdx2lDeMkkKsomhxZnSpj08279slnk_/view?usp=drivesdk

hey @azazmushtaq can you please try again? There were a few errors in android integration, we fixed that a few weeks ago. It should work as expected now.

yes it worked... one thing more when there will be the Feature of
Import External Solana wallets be integrated in React Native  Sdk?
On Wed, 9 Nov 2022 at 2:37 PM, Yashovardhan Agrawal <
@.***> wrote:

hey @azazmushtaq https://github.com/azazmushtaq can you please try
again? There were a few errors in android integration, we fixed that a few
weeks ago. It should work as expected now.
—
Reply to this email directly, view it on GitHub
https://github.com/Web3Auth/examples/issues/14#issuecomment-1308473790,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH5RN4SWNDKJKJQGFKDEQF3WHNWF5ANCNFSM6AAAAAAQ4VNCYU
.
You are receiving this because you were mentioned.Message ID:
@.***>

As of now we don't have that on the roadmap. It will be great if you can suggest in the feature requests discussions, so that we can look into it 😄 https://github.com/orgs/Web3Auth/discussions/categories/feature-requests
Closing this issue for now. Please ask any support questions in the GitHub Discussions for prompt responses.


Lucene plugin not work for local testing.

Hi Team:
I'm trying to use this plugin to integrate local cordova project. but the demo code not work, just throw "segments does not exist".
I use eclipse lucene 2.9.4 to generate index folder, and just copy it to www folder.
any suggestion?  please check my screen shot.

Hi,
From an ios code, just indexes generated with Lucene 1 is usable. It is a limitation of the ios port.
Try again with this release.

Hi @gigaga
Try use Lucene 1.9.1 to generate indexes, and still not work under ios.
var indexPath = cordova.file.applicationDirectory+"www/storage/sdcard/full_text_index/";

indexPath can be founded but not result hits, also the error message still log.

Your path is incorrect. There is no sdcard in ios device.

@gigaga use V1.4.3 and absolute path, it works.
Thanks.

Really good news, thanks!


Plotting results from analysis script

Changes
Made a stacked bar chart for the output of the analysis script.
Thought I might as well upload this and let you decide if you want it. Either way doesn't matter to me!

Note: I didn't touch poetry at all so that could be a possible issue

Example:

Thanks for the PR, I really prefer the visual representation for the results now!

Note: I didn't touch poetry at all so that could be a possible issue

I went ahead and added all the dependencies needed. Thanks!


Freezing after opening camera on Fedora Asahi Remix aarch64 Linux on Apple Silicon

Aware that this is not a common OS to use (linux on Mac M1), but reporting in case others get the same or it is easy to fix.
Running sparrow-2.0.0-1.aarch64.rpm
on:
uname -a
Linux fedora 6.12.4-400.asahi.fc41.aarch64+16k #1 SMP PREEMPT_DYNAMIC  aarch64 GNU/Linux

When I click anything using the camera the picture appear temporarily then freezes. Able to close the camera window, but then Sparrow freezes and needs to be forcefully killed.
Logs:
(Sparrow:17477): Gdk-WARNING **: 21:30:27.499: XSetErrorHandler() called with a GDK error trap pushed. Don't do that.
2024-12-27 21:30:34,194 ERROR Error executing hwi-3.1.0
java.io.IOException: [17654] Error loading Python lib '/tmp/_MEIKGqx8o/libpython3.9.so.1.0': dlopen: libcrypt.so.1: cannot open shared object file: No such file or directory

	at com.sparrowwallet.sparrow@2.0.0/com.sparrowwallet.sparrow.io.Hwi.getProcessOutput(Unknown Source)
	at com.sparrowwallet.sparrow@2.0.0/com.sparrowwallet.sparrow.io.Hwi.execute(Unknown Source)
	at com.sparrowwallet.sparrow@2.0.0/com.sparrowwallet.sparrow.io.Hwi.enumerateUsb(Unknown Source)
	at com.sparrowwallet.sparrow@2.0.0/com.sparrowwallet.sparrow.io.Hwi.enumerate(Unknown Source)
	at com.sparrowwallet.sparrow@2.0.0/com.sparrowwallet.sparrow.io.Hwi$ScheduledEnumerateService$1.call(Unknown Source)
	at com.sparrowwallet.sparrow@2.0.0/com.sparrowwallet.sparrow.io.Hwi$ScheduledEnumerateService$1.call(Unknown Source)
	at javafx.graphics@22/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at javafx.graphics@22/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at javafx.graphics@22/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Killed

Partially fixed with:
sudo dnf install libxcrypt-compat

Still remains:
/opt/sparrow/bin/Sparrow

(Sparrow:23809): Gdk-WARNING **: 21:44:17.053: XSetErrorHandler() called with a GDK error trap pushed. Don't do that.

Thanks for the report. This is a duplicate of #1504, and will be solved by replacing HWI with Lark in the next release.
The error trap message is harmless - you can read more about it in #1059.

I may have closed this too early - is the camera still freezing?

Closing as fixed after a dnf update and restart.


Cops restricted by Include are not run when linting a single file

Expected behavior
If I pass a cop to run with --only it should run, even if it restricts itself to certain folders/patterns through the Include config.
The repro below is a bit contrived since not many buildin cops use Include but the same is not true for extensions like rubocop-rails.
Steps to reproduce the problem
# .rubocop.yml

AllCops:
  DisabledByDefault: enable

Style/StringLiterals:
  Enabled: true
  Include:
    - lib/**/*.rb

# test.rb

""
''

earlopain@DESKTOP-PC rubocop]$ bundle exec rubocop test.rb --only Style/StringLiterals
Inspecting 1 file
.

1 file inspected, no offenses detected

Moving the file into the lib folder, or removing the Include config makes the cop run.
RuboCop version
$ bundle exec rubocop -V
1.65.1 (using Parser <IP_ADDRESS>, rubocop-ast 1.32.0, running on ruby 3.4.0) [x86_64-linux]

This would also apply to Exclude.
I'm going to close this since I'm doing something unconventional and a solution would benefit barely anyone (if any).
Additional, this is only one case where you can apply this logic to. For example, if running rubocop from the app root against another  application in a folder like ../my_other_app. It's  not possible for rubocop to correctly infer user intention.


Memory Setting issue

Can I set max server running memory? If I can, how can I set it?
Thanks for help!
Thanks for this awesome project!

only in MultiAdmin

only in MultiAdmin

How to?

https://github.com/Grover-c13/MultiAdmin/blob/master/README.md#config-settings

ok thanks!


feat: Support indexed queries with Filter.or

Motivation / Background

This Pull Request ...
Details

Additional information

#6732  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @mykola-vrmchk and the rest of your teammates on  Graphite


velero upstream main rebase as of Mar 27, 2023

Do you think it would make sense to bump to v1.11 here? just to signal to human readers what version we intend to be compatible with.
https://github.com/openshift/oadp-operator/blob/84636765553916f76f8f056464ed180c8902ce56/go.mod#L18
Also would it make sense to up go.mod to 1.19 by now?

Hmm. Not sure about 1.11 -- I'm wary of bumping that up when there is no actual release for it yet. With the replace directive, it doesn't really matter, but I think I'd prefer to wait for 1.11 release to bump up the primary dep. I'm open to persuasion there if anyone else has strong opinions.
As for golang version, that's probably worth doing, but maybe as a separate PR?

/retest


Adding docker images for the V3

Breaking change

Proposed change

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the [development checklist][dev-checklist]
[ ] The code compiles without warnings (code quality chek)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

Codecov Report

Merging #588 (1d1b7c7) into app_model (ff24a67) will decrease coverage by 0.27%.
The diff coverage is 78.68%.

@@              Coverage Diff              @@
##           app_model     #588      +/-   ##
=============================================
- Coverage      86.51%   86.23%   -0.28%
=============================================
  Files            108      108
  Lines           2915     2943      +28
  Branches         309      312       +3
=============================================
+ Hits            2522     2538      +16
- Misses           259      268       +9
- Partials         134      137       +3

Flag
Coverage Δ

unittests
86.23% <78.68%> (-0.28%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...tDaemon.HassClient/Internal/HomeAssistantRunner.cs
88.29% <50.00%> (-4.89%)
:arrow_down:

...tDaemon.HassClient/Internal/HomeAssistantClient.cs
82.08% <71.42%> (-3.63%)
:arrow_down:

...ime/NetDaemon.Runtime/Internal/NetDaemonRuntime.cs
85.00% <72.22%> (-3.24%)
:arrow_down:

...mmon/Extensions/IConfigurationBuilderExtensions.cs
96.77% <85.71%> (ø)

...on.AppModel/Common/Settings/AppLocationSettings.cs
100.00% <100.00%> (ø)

...n.AppModel/Internal/Compiler/SyntaxTreeResolver.cs
100.00% <100.00%> (ø)

...t/NetDaemon.HassClient/Common/Settings/Settings.cs
100.00% <100.00%> (ø)

...Runtime/Common/Extensions/HostBuilderExtensions.cs
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Can tanker drop records that can't be found?

From time to time, things are getting into my index that do not exist in my database. When this happens, I get an ActiveRecord::RecordNotFound exception (I'm using rails). I have fixed this locally by monkey patching the instantiate_results_from_db method. I know I could use rescue to handle that exception, but it seems like a shame when tanker could return 1,000 id's and one of them might not be in the database anymore. Here is how I fixed it:
#tanker.rb - instantiate_results_from_db
...
id_map.each do |klass, ids|
  # narrow ids down to records that exist
  ids = ids.find_all {|x| constantize(klass).exists? x}
  ...
end

I hear this is what Sunspot does. What do you think? I suppose it could be configurable.

Shouldn't these scenarios be handled by
after_save :update_tank_indexes
after_destroy :delete_tank_indexes
?

Yes, you would think so. This would essentially be a fail safe. The issue seems to come up most often in the test environment. When it happens, several of my tests fail and I have to manually find and remove things in the index.

Just execute it for the environment you need it for


Disable smooth scrolling in the webview

VSCode Version: 1.19.0-insider 6bc5a14bf34e44b3af5508350cc1221fcc999ceb
OS Version: Ubuntu 17.10

Steps to Reproduce:

In user settings, set "editor.smoothScrolling" to false.
Observe that scrolling in the settings, and in code is correctly not smoothed.
Open the extensions sidebar and click an extension to open its Marketplace page.
Assuming the extension has a readme that is long enough to permit scrolling, observe that the scrolling is smoothed.

Expected Behaviour:
Disabling smooth scrolling disables it application-wide.
Reproduces without extensions: Yes

Looks like the request is to support smooth scrolling across application.

This probably has to do into the list/tree widget.

@bpasero This clearly has nothing to do with the list/tree widget; the user is referring to the webview... cc @mjbvz
@theFroh Note that the setting starts with editor., so it only applies to the editor.

I am clearly sorry for the inconvenience I caused...

@joaomoreno Good call mate, I didn't connect 'editor' specifically to the text editing views.
I suppose I was referring more to this behaving like the --disable-smooth-scroll flag (which I've tested anyhow, knowing that it'd not work due to the way views work here).


Cloud chuck record HTTPS's request and response?

@lijiankun24 yes it can. It is interceptor in your app. so it will record https/http or any call from your app


Indexer not restarted when the git clone operation fails

Describe the bug
In some cases the operator doesn't restart the indexer if the git clone operation fails. We should update the indexer to always restart the indexer or mark it as errored:

If the error is temporary (e.g. bad internet connection), the indexer should be restarted.
If the error is fatal (e.g. bad git url or missing authentication credentials) the indexer should be marked as error and its status updated.

In all cases the number of restarts should be incremented by one.

Hi @fracek i can work on this


[skip ci] swiftui-modals - Added modal option to PresentationTypes - MZ TT

Co-authored-by: Tyler Thompson<EMAIL_ADDRESS>
Linked Issue:

Checklist:

[ ] Did you sign the Contributor License Agreement?
[ ] Is the linter reporting 0 errors?
[ ] Did you comply with our styleguide?
[ ] Is there adequate test coverage for your new code?
[ ] Does the CI pipeline pass?
[ ] Did you update the documentation?
[ ] Did you update the sample app?
[ ] Do we need to increment the minor/major version?
[ ] Did you change the public API?
[ ] Have you done everything you can to make sure that errors that can occur are compile-time errors, and if they have to be runtime do you have adequate tests and documentation around those runtime errors? For more details.

If Applicable:

[ ] Did you test when the first item is skipped?
[ ] Did you test when the last item is skipped?
[ ] Did you test when middle items are skipped?
[ ] Did you test when incorrect data is passed forward?
[ ] Did you test proceeding backwards?

If Public API Has Changed:

[ ] Did you deprecate (rather than remove) any old methods/variables/etc? Our philosophy for deprecation.
[ ] Have you done the best that you can to make sure that the compiler guides people to changing to the new API? (Example: the renamed attribute)
[ ] If necessary, have you tested the upgrade path for at least N-1 versions? For example, if data persists between v1 and v2 then that upgrade should be tested and as easy as we can make it.

Codecov Report

Merging #118 (51bfc65) into main (c42b2aa) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #118   +/-   ##
=======================================
  Coverage   94.26%   94.27%
=======================================
  Files          76       76
  Lines        1867     1869    +2
=======================================
+ Hits         1760     1762    +2
  Misses        107      107

Impacted Files
Coverage Δ

...iftUI/Extensions/SwiftUILaunchStyleAdditions.swift
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Upgrading helm release to include a set for patroni postgres parameter (dcs configs) causes stuck at "PENDING_UPGRADE" until times out and fails

Description
We had an existing timescale release. We decided to up the max_connections by running:
$ helm upgrade -n xyz --install <name>  timescaledb/timescaledb-single ... --set patroni.bootstrap.dcs.postgresql.parameters.max_connections=750 ... --version=0.5.5

However, it's perpetually stuck at this state until the timeout, when it fails:
helm history timescaledb-live
REVISION	UPDATED                 	STATUS         	CHART                   	APP VERSION	DESCRIPTION
1       	Wed Mar 11 19:53:04 2020	SUPERSEDED     	timescaledb-single-0.5.3	           	Install complete
2       	Thu Apr  2 10:00:39 2020	DEPLOYED       	timescaledb-single-0.5.5	           	Upgrade complete
3       	Mon Apr 13 14:24:21 2020	FAILED         	timescaledb-single-0.5.5	           	Upgrade "timescaledb-xyz" failed: timed out waiting for ...

Before Revision 3 got swithced to FAILED after timing out, it was at:
3       	Mon Apr 13 XX:XX:XX 2020	PENDING_UPGRADE	timescaledb-single-0.5.5	           	Preparing upgrade

Environment
Chart version: 0.5.5
Helm version: v2.16.5
Kubernetes version: 1.14
Current Workaround
It looks like this job never gets triggered: https://github.com/timescale/timescaledb-kubernetes/blob/master/charts/timescaledb-single/templates/job-update-patroni.yaml
To work around this, I tried to manually do these steps:

Update patroni configmap to change value for "max_connections" from 100 to 300

$ kubectl edit configmap timescaledb-xyz-patroni -n live
configmap/timescaledb-xyz-patroni edited

Now, curl the patroni server to get the current configuration

$ kubectl exec -it timescaledb-xyz-0 -c timescaledb  -n live -- bash
postgres@timescaledb-xyz-0:~$ curl http://timescaledb-xyz-config:8008/config

(2) spits out a JSON, copy it and edit the max_connections to 300, then PATCH it back to the server:

postgres@timescaledb-xyz-0:~$ curl --connect-timeout 10 --include --silent --show-error --fail -X PATCH --data '<TheJSONFromAbove>' -H "content-type: application/json"  "http://timescaledb-xyz-config:8008/config"

Delete the pod so statefulset can bring it back up again with the new config.

Other notes
I noticed --set of the dcs config worked fine on a test cluster where timescaledb was deployed on the default namespace. Not sure if the fact this error occurs on clusters where it's deployed on a non-default namespace is related.

Not sure if the fact this error occurs on clusters where it's deployed on a non-default namespace is related.

We deploy them in different namespaces pretty much always and don't run into this, so that's not the issue.
We'll try to investigate; using a Job inside a Helm Upgrade path might not be the best thing ever; as it can fail, I don't think failure of the Job is covered very well in these Helm Charts.
The whole purpose of the Job is to do exactly what you described: up the connections from say 100 to 120, without having to restart the pods.

@feikesteenbergen thanks for that tidbit... So today I was able to get more information (yesterday I was more focused on getting workaround out to unblock our production).
I was remiss in not pasting/checking tiller logs when helm was stuck. Today, as I did the helm upgrade described in the ticket, I checked to see what tiller was waiting on, and sure enough, it complains that the "backup" pods are not in a "ready" state (which they aren't because the backup job terminates the pods upon completion):
$  kubectl logs tiller-deploy-xxx -n yyy
...
[kube] 2020/04/14 16:36:49 Pod is not ready: <namespace>/timescaledb-xyz-full-weekly-1586657520-bgspt
[tiller] 2020/04/14 16:36:49 warning: Upgrade "timescaledb-xyz" failed: timed out waiting for the condition

Deleting each of the pods it complained about (full-weekly and incremental-daily), helped resolve the issue. Before deleting the pods, the jobs and their pods look like they ran fine (but obviously in a Not Ready State because it "Completed"):
Info on Backup Jobs and Pods
$ kubectl get cronjob,job -l release=timescaledb-live -n xyz
...
NAME                                                      COMPLETIONS   DURATION   AGE
job.batch/timescaledb-xyz-full-weekly-1586657520         1/1           3s         2d17h
job.batch/timescaledb-xyz-incremental-daily-1586571120   1/1           5s         3d17h
job.batch/timescaledb-xyz-incremental-daily-1586743920   1/1           3s         41h
job.batch/timescaledb-xyz-incremental-daily-1586830320   1/1           5s         17h

$ kubectl get pods...
...
timescaledb-xyz-full-weekly-1586657520-bgspt              0/1     Completed   0          2d16h
<similar for a few incremental-daily>

How Helm Deployed Successfully
So basically, while helm was upgrading today, and before it timed out, I deleted the weekly and daily backup pods. Basically kubectl delete po timescaledb-xyz-full-weekly-1586657520-bgspt along with the incremental-daily pods, and finally helm got the release in a "Deployed" state (rather than "Failed")
Questions:

Any reason the helm upgrade has tiller complaining about those completed backup pods? It doesn't seem to complain in our test cluster (with only difference being the default namespace).
I'll wait until the next incremental backup job runs to see if I can indeed reproduce this by doing an upgrade again. In meantime, any ideas?

OK, ☝ reproducible in my environment... I disabled and then re-enabled backup:

The backup job was started and completed:

$ kubectl get cronjob,job -l release=timescaledb-xyz -n xyz
NAME                                               SCHEDULE        SUSPEND   ACTIVE   LAST SCHEDULE   AGE
cronjob.batch/timescaledb-xyz-full-weekly         12 02 * * 0     False     0        <none>          7h
cronjob.batch/timescaledb-xyz-incremental-daily   12 02 * * 1-6   False     0        57m             7h

NAME                                                      COMPLETIONS   DURATION   AGE
job.batch/timescaledb-xyz-incremental-daily-1587003120   1/1           5s         57m

## And the Pod
$ kubectl get pods -n xyz
...
timescaledb-xyz-incremental-daily-1587003120-x2rwg             0/1     Completed   0          57m
...

Did a helm upgrade ... by changing a parameter... It was stuck in "PENDING_UPGRADE" so we check the tiller log:

$ kubectl logs tiller-deploy-6dbd4749b6-rxqx5 -n kube-system
[kube] 2020/04/16 03:00:39 beginning wait for 15 resources with timeout of 5m0s
[kube] 2020/04/16 03:00:41 Pod is not ready: xyz/timescaledb-xyz-incremental-daily-1587003120-x2rwg
[kube] 2020/04/16 03:00:43 Pod is not ready: xyz/timescaledb-xyz-incremental-daily-1587003120-x2rwg
[kube] 2020/04/16 03:00:45 Pod is not ready: xyz/timescaledb-xyz-incremental-daily-1587003120-x2rwg

It will stay like this until i delete the pod timescaledb-xyz-incremental-daily-1587003120-x2rwg, at which point it upgrades successfully.

Any clues how we can upgrade parameters without it "waiting" on the already terminated backup job pods?

I've updated the title to reflect root reason for the "PENDING_UPGRADE". @feikesteenbergen or anyone else in the timescale community: thoughts on how we can get around that rather than manually deleting pods before the helm upgrade? Or if we're missing something in the above?

I'll have a look; I think it may be an issue with labelling: The Backup jobs getting labels that are interpreted by Helm as saying these jobs belong to Helm (they don't).

I cannot reproduce this somehow, I used helm 2 and helm 3.
Could you give more information:

what is your helm version
what is your charts version

Regardless of this, I'm going to be removing some labels from the jobs and the pods that are scheduled, because I think they are not useful and may actually be the cause here.

This is (probably) fixed with This should be fixed with https://github.com/timescale/timescaledb-kubernetes/releases/tag/v0.6.1.
However I could not reproduce it locally, so it would be graet if you could verify whether or not it is fixde? @schahal

We'll give it a shot in the coming weeks! We have to schedule an activity to do the 0.5 -> 0.6 upgrade because clusters we can currently reproduce this on are being used. I'll update this ticket when complete.

Feel free to reopen if the issue persists, as it should have been fixed.

Facing exactly the same issue on a big chart I'm building. Very hard to reproduce as well :-(


Can't specify trusted SSL certificate

I can't find how to specify a trusted cert to use when communicating with my vcenter server. I tried doing knife ssl fetch and the cert shows up in my trusted_certs directory, but knife vsphere ignores it.
I'd prefer to give a trusted cert instead of opening the ssl connection wide open.

Are you talking about the VSphere API interaction or the communication between the chef client and the server? I think to talk to the VSphere API you need to get the vsphere key in your local certificate store. trusted_certs is only used for the Chef API.

Hi, closing this as we haven't heard back in a little while. If you're still interested in discussing this, please re-open and let me know. Thanks.


Always return 'views from this post' in view_count

Closes #41
Same as #41 except that the PR is from origin, not from a fork.
Just an experiment to see whether Travis only reads environment variables in PR from origin, since in #41 I cannot manage to have the FB ENV used by Travis.

Coverage remained the same at 100.0% when pulling e2e4823ffd6f2b9a27dd0a3f961ca4276cf4f57b on dont-use-cumulative into 09bb933640e91e03d2f89e9b48c8f3ed969ec88f on master.

Tests are passing.
The problem is https://github.com/travis-ci/travis-ci/issues/1946

Coverage remained the same at 100.0% when pulling f2e3dc2e4696ec3f7c620f990ce1669996483674 on dont-use-cumulative into 09bb933640e91e03d2f89e9b48c8f3ed969ec88f on master.


[kmac]  SW cmd during App operation triggers SwSequence error

Hi Eunchan,
I'm testing a scenario where SW sends a random command (in this case CmdManualRun) to the KMAC during operation of the App interface, expecting that the RTL raises a ErrSwIssuedCmdInAppActive error.
However, I end up getting an ErrSwCmdSequence error from the RTL instead, which IMO is incorrect.
This is because the kmac_errchkr module processes the incoming SW cmd one cycle before sending it out to the rest of the IP (including kmac_app) .
The FSM remains in StIdle as app_active_i will be high, so the sequencing check logic sees a CmdManualRun while the FSM is still in Idle state and raises a ErrSwCmdSequence one cycle before the kmac_app has a chance to do anything.
I think the fix for this would be to only treat sequence errors as valid inside the kmac_errchkr if we are not in App mode, as the kmac_app will detect any SW commands sent during App operations.
WDYT?

Hi @eunchan, could you take a look at this issue if you have time?

OK Sorry for missed this! Let me take a look.

I just read your description. It looks like the stimuli sent ManualRun without Start command. I expect that one could fall into both category. As the state machine won't move from StIdle to next states, the kmac_errchk logic only accepts Start command and hand over to kmac_app module.
The case we may see the ErrSwIssuedCmdInAppActive is when the SW sends Start command while the App Interface is active.

ahh got it, so SwIssuedCmdInAppActive is specifically when SW sends Start command during App interface.
Is it possible to update the specs to reflect this?

@eunchan do you mind having a look at this? from what i remember this has also been addressed.

Yep. Thanks for pinging me. This has been addressed. There's explicit errchk module to check the sequence.


TabularProjector should accept files with header line

Add parameter to assume first line of the dictionary is a header with column names.
Also features names should correspond to column names.

Done with: da3d911d6fae6e55cdc1bddc202a8864be244521


feat(Makefile): containerize project bootstrapping

The prototype repo was demonstrating a "two stage" build build (which is really a containerized build) using the golang:1.5.1 image.  That has been a very positive step toward my dream of containerizing the development environment, unfortunately, because of all the things golang:1.5.1 does not include (e.g. glide), I am seeing new deis v2 repos pop up that are including a project bootstrap / dependency resolution target such as bootstrap that runs outside of a container and that negates the progress made toward containerizing the development environment.
This fixes that.  I have incepted deis/docker-go-dev as the source of the deis/go-dev on quay.io.  This image is the official Alpine-based Go 1.5.1 + glide and a few other build essentials.  This creates the possibility of containerizing a "bootstrap" target and advancing us further toward a fully containerized development environment.
This PR adds support for this to the proto-Makefile.

I'm not sure building on an Alpine-based distro is a good idea because of it's non-compliant libc implementation. How much testing have we done on that?

Ah.  Whoops.  I am correcting that statement.  This is not based on the golang:1.5.1-alpine image.  I do have a PR open for that, but this image is built from regular golang:1.5.1.  I will strike the appropriate parts of the OP.

I'm not sure building on an Alpine-based distro is a good idea because of it's non-compliant libc implementation. How much testing have we done on that?

We should move this (part of the) discussion to here: https://github.com/deis/docker-go-dev/pull/1

I like this idea.


token option has no effect

I'm trying to use hardhat-gas-reporter with Polygon.
To do so, I have :

created a coinmarket account and exported the private key in .env file
modified hardhat.config.js to use MATIC and my country's currency

When I generate the report, the token and gas prices are still based on Ethereum instead of Polygon
Here is my config and my output:
  gasReporter: {
    currency: "CHF",
    token: "MATIC",
    coinmarketcap: process.env.COINMARKETCAP || null,
    enabled: true,
  },

Calls are being made to the coinmarket API, but with ETH as symbol.

What I expected: An output with MATIC price and symbol

I'm not sure why this wasn't working for you, nothing jumps out as wrong in your config. I just now used:
gasReporter: {
    coinmarketcap: process.env.CMC_API_KEY,
    token: "MATIC",
    gasPriceApi: "https://api.polygonscan.com/api?module=proxy&action=eth_gasPrice"
  }

and got:

which is pretty close to polygonscan rn:

Closing


Script as a binary

Proposal Title
Script as a binary
Context and Problem Statement
Need a performant and portable script
Describe the feature / enhancement and how it helps to overcome the problem or limitation
Use wasgo for godot 4
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

port wasgo to 4
download as binaries
???
game

If this enhancement will not be used often, can it be worked around with a few lines of script?
Need to collaborate with mmae
Positive Consequences
No response
Negative Consequences
No response
Is there a reason why this should be core and done by us?
We know how this works.
References
No response
Derivative License
Copyright (c) 2020-2021 V-Sekai contributors.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

33b74881debe7306f4dd3f691bdde2bfa6b8681a


client/x11: fix + simplify invalidate_poly_region

This should also fix  issue #2618

+1 LGTM
The autoclose parameter was quite strange...

+1


Fix parameter name missmatch introduced in 8ed8b88c

(Sometimes Lua not throwing errors on undefined variables makes it really hard to debug!)

That's clearly wrong and you have clearly the right fix, but I am concerned that tests didn't pick this up; keeping this open until I've added a test for it.

The tests didn't  break  because nothing was actually using that code, there were two separate processors for % units and this one wasn't getting hit. My suggestion is that the whole ideas of percentages without being explicitly relative to something is broken and should be abandoned (see #304).

Looks like we're moving in favor of the full fix rather than the band-aid, so this will be obsolete. Closing it so it stays out of the noise.


Global constraint search ignores timeout when trajectories are not connected

Following scenario:

load frozen state with multiple trajectories 0 & 1 (e.g. assembled in cloud)
start a trajectory 3 with initial pose relative to trajectory 0 of those frozen trajectories

Now 3 & 0 are connected, but 3 & 1 are not. This means that LastConnectionTime(3, 0) returns a 0 time value by convention, and thus we can trigger a global constraint search in this code path (regardless of how you set global_constraint_search_after_n_seconds):
https://github.com/googlecartographer/cartographer/blob/ea2bf3b1b2fc9ea00f094ccfca24c4d17f10763a/cartographer/mapping/internal/2d/pose_graph_2d.cc#L267-L287

My question: is this a bug? The name global_constraint_search_after_n_seconds implies that the search is done after n seconds, but here it's scheduled immediately if the sampler pulses.

This discussion is related, however it only considers the single trajectory case: https://github.com/googlecartographer/cartographer/pull/1142#issuecomment-393855562
Citing @wohe :

without an initial pose there is not guaranteed connection between the two coordinate systems of the robot and the map

In the multi trajectory scenario I outlined here, there is however a connection. I'm fully aware that setting global_sampling_ratio to 0 finally disables global searches, but this is not obvious in this case.


ARROW-2489: [Plasma] Fix PlasmaClient ABI variation

When compiled with GPU support, the PlasmaClient ABI would differ, leading to a crash in the Python bindings to Plasma.

I think the AppVeyor failure is unrelated. It also succeeded on my AppVeyor account: https://ci.appveyor.com/project/pitrou/arrow/build/1.0.331