APP Released for WEB Problem

The charts blocks the UI and does not show the charts on an APP released for WEB.

I had the issue when I was on 0.12.2 with flutter stable 2.0.4.
Upgrading fl_chart to 0.35.0 fixed it.
Also quick tip: when you ask a question, try to give a meaningful title like "Charts don't show on web".

@GP4cK is right.
Thanks for explaining.
@Parufrade Also it is better to mention your fl_chart, and flutter version.

Hello, I have the same problem.
fl_chart v0.35
Flutter 2.0.1
It works on web with html render, but not with canvas render.
With canvas render, I have the following error
══ Exception caught by rendering library ═════════════════════════════════
BindingError: Tried to invoke ctor of Path with invalid number of parameters (1) - expected (0) parameters instead!
The relevant error-causing widget was
LineChart
..\…\graph-fl\graph-fl.dart:6
With a basic
class GraphFl extends StatelessWidget {
Widget build(BuildContext context) {
return LineChart(
sampleData1(),
swapAnimationDuration: Duration(milliseconds: 150), // Optional
swapAnimationCurve: Curves.linear, // Optional
);
}
}
coming directly from the documentation


Feature vertex migrations

@vanmh These are the mpm changes (I think) are needed to trick mpm into managing vertica migrations.  FYI

So old...

👋


Docker-compose up: Service 'indy_pool' failed to build

Trying to follow the "Indy Getting Started" guide, I face issues running docker-compose up in /indy-sdk/docs/getting started that seem to be rooting from indy-plenum (ci/indy-pool.dockerfile line28 following). An extract of the terminal can be found below.
Problems came up on Ubuntu 18.04, 16.04 and 20.04 VMs. Two colleagues of mine face the same issue, so it should'nt be a local problem.
Does anyone know how to fix this? I hope this is the right place to ask, thank you in advance for your help.
Step 14/22 : RUN apt-get update -y && apt-get install -y python3-pyzmq=${python3_pyzmq_ver} indy-plenum=${indy_plenum_ver} indy-node=${indy_node_ver} python3-indy-crypto=${python3_indy_crypto_ver} libindy-crypto=${indy_crypto_ver} vim
---> Running in bdb382729991
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [2376 kB]
Get:6 https://repo.sovrin.org/deb xenial InRelease [28.4 kB]
Get:7 https://repo.sovrin.org/deb xenial/master amd64 Packages [345 kB]
Get:8 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [1855 kB]
Get:9 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [1527 kB]
Fetched 6457 kB in 5s (1139 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
indy-plenum : Depends: python3-orderedset (= 2.0) but 2.0.3 is to be installed
Depends: python3-psutil (= 5.4.3) but 5.6.6 is to be installed
Depends: python3-psutil (= 5.4.3) but 5.6.6 is to be installed
Depends: python3-pympler (= 0.5) but 0.8 is to be installed
E: Unable to correct problems, you have held broken packages.
ERROR: Service 'indy_pool' failed to build: The command '/bin/sh -c apt-get update -y && apt-get install -y python3-pyzmq=${python3_pyzmq_ver} indy-plenum=${indy_plenum_ver} indy-node=${indy_node_ver} python3-indy-crypto=${python3_indy_crypto_ver} libindy-crypto=${indy_crypto_ver} vim' returned a non-zero code: 100

A solution was found.
In the the Hyperledger chat (https://chat.hyperledger.org/channel/indy-sdk/thread/7ioQx5oQJXfJCJKz9?jump=Xj7mTYbLwyzYehD7t) my colleague got an answer from @jovfer (I suppose).
In file /indy-sdk/ci/indy-pool.dockerfile changing the block from line 34 onwards to this (emphasis on the last 3 lines):
RUN apt-get update -y && apt-get install -y \
        python3-pyzmq=${python3_pyzmq_ver} \
        indy-plenum=${indy_plenum_ver} \
        indy-node=${indy_node_ver} \
        python3-indy-crypto=${python3_indy_crypto_ver} \
        libindy-crypto=${indy_crypto_ver} \
        vim \
        python3-orderedset=2.0 \
        python3-psutil=5.4.3 \
        python3-pympler=0.5

Afterwards the problems in issue #2237 occurred but could be solved with the solution provided there.
In the end,  we removed the image with docker system prune and could proceed to follow the getting started guide.

This will solve the problem:
ARG indy_plenum_ver=1.12.1~dev989
ARG indy_node_ver=1.12.1~dev1172
ARG python3_indy_crypto_ver=0.4.5
ARG indy_crypto_ver=0.4.5
ARG python3_pyzmq_ver=18.1.0
ARG python3_orderedset_ver=2.0
ARG python3_psutil_ver=5.4.3
ARG python3_pympler_ver=0.5

RUN apt-get update -y && apt-get install -y \
        python3-pyzmq=${python3_pyzmq_ver} \
        indy-plenum=${indy_plenum_ver} \
        indy-node=${indy_node_ver} \
        python3-indy-crypto=${python3_indy_crypto_ver} \
        libindy-crypto=${indy_crypto_ver} \
        python3-orderedset=${python3_orderedset_ver} \
        python3-psutil=${python3_psutil_ver} \
        python3-pympler=${python3_pympler_ver} \
        vim

Received the same error today trying to build on a Mac. Would be good to pull this fix into the repo.


[feature] Chaining duplication could have a dynamic position offset

Currently when we duplicate an element, the copy gets its position based on the source element (position + offset).
The offset is constant const offset = [16, 16].
If we position the new element (el 1) and duplicate it again, the third element (el 2) will be positioned with that fixed offset again.
An enhancement could be to use the delta pos between el 2 and el 1 as the next offset as long as we keep the duplicated elemente (el 2 and so on) selected. As far as I know it's a quite common behaviour.
What do you think ?

Hi, closing this as we won't be adding new features to this version of tldraw. Check https://github.com/tldraw/tldraw for the latest!


Test1

test123

The Copyright Check has failed!
The files listed below do not have a valid copyright statement:

data/templates/megaraid-config-cp.sh - debian/changelog


SASS loader & ExtractTextPlugin 2.0.0: Cannot read property 'node_modules/extract-text-webpack-plugin' of null

The same with #211 , but my extract-text-webpack-plugin version is 2.0.0-beta.3.
0 active/node_modules/loader-runner/lib/LoaderRunner.js:90 throw e; TypeError: Cannot read property '/node_modules/extract-text-webpack-plugin' of null     at /node_modules/extract-text-webpack-plugin/index.js:257:27     at /node_modules/webpack/lib/Compilation.js:462:4     at Array.forEach (native)     at callback (/node_modules/webpack/lib/Compilation.js:461:14)     at Compilation.<anonymous> (/node_modules/webpack/lib/Compilation.js:482:4)     at /node_modules/webpack/lib/Compilation.js:326:10     at /node_modules/async/lib/async.js:52:16     at Object.async.forEachOf.async.eachOf (/node_modules/async/lib/async.js:236:30)     at Object.async.forEach.async.each (/node_modules/async/lib/async.js:209:22)     at Compilation.addModuleDependencies (/node_modules/webpack/lib/Compilation.js:192:8)     at Compilation.processModuleDependencies (/node_modules/webpack/lib/Compilation.js:177:7)     at Compilation.<anonymous> (/node_modules/webpack/lib/Compilation.js:469:8)

Same here when used in the context of Angular2@beta:
When using this demo component:
import { Component } from "@angular/core";

@Component({
  selector: "another-component",
  template: require("./another.component.pug"),
  styles: [ require("./another.component.scss") ]
})
export class AnotherComponent {
  title = "Tour of Heroes!";
}

The resulting bundle looks like this (only the relevant parts):
var AnotherComponent = (function () {
    function AnotherComponent() {
        this.title = "Tour of Heroes!";
    }
    AnotherComponent = __decorate([
        __webpack_require__.i(__WEBPACK_IMPORTED_MODULE_0__angular_core__["Component"])({
            selector: "another-component",
            template: __webpack_require__(502),
            styles: [__webpack_require__(500)]
        }),
        __metadata('design:paramtypes', [])
    ], AnotherComponent);
    return AnotherComponent;
}());

Note the styles require which is id 500:
/***/ 500:
/***/ function(module, exports) {

// removed by extract-text-webpack-plugin

/***/ },

When I patch loader.js#39 to look like this it works:
		var resultSource;
		if(query.remove) {
			resultSource = "// removed by extract-text-webpack-plugin\nmodule.exports='';";
		} else {
			resultSource = undefined;
		}

Angular2 at least requires the styles options to returns a array of strings.
Don't know if that helps.
Cheers,
Frank

i had found the reason.
my file-loader
 {             test: /\.png|jpe?g|ico|bmp|gif$/,             loader: "file-loader?name=imgs/[name]-[hash].[ext]"         }
is not work.
and my css has
body{ background:url(bg.png) }
so have error
{ ModuleBuildError: Module build failed: ModuleParseError: Module parse failed: bg.png Unexpected character '�'
perhaps ExtractText try parse bg.png file.

+1 i have the same problem

+1 Same here

I have the same problem with 2.1.0-beta.20.  It was working on another machine.  So it may be a newer version of some other lib.  I'm still using '^'s everywhere in my package.json.
building modules 1114/1114 modules 0 active/home/rpoitras/dev/components-material-ui/node_modules/loader-runner/lib/LoaderRunner.js:104
                if(isError) throw e;
                            ^

TypeError: Cannot read property '/home/rpoitras/dev/components-material-ui/node_modules/extract-text-webpack-plugin' of null
    at /home/rpoitras/dev/components-material-ui/node_modules/extract-text-webpack-plugin/index.js:257:27
    at /home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:462:4
    at Array.forEach (native)
    at callback (/home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:461:14)
    at Compilation.<anonymous> (/home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:482:4)
    at /home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:326:10
    at /home/rpoitras/dev/components-material-ui/node_modules/async/lib/async.js:52:16
    at Object.async.forEachOf.async.eachOf (/home/rpoitras/dev/components-material-ui/node_modules/async/lib/async.js:236:30)
    at Object.async.forEach.async.each (/home/rpoitras/dev/components-material-ui/node_modules/async/lib/async.js:209:22)
    at Compilation.addModuleDependencies (/home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:192:8)
    at Compilation.processModuleDependencies (/home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:177:7)
    at Compilation.<anonymous> (/home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:469:8)
    at /home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:124:4
    at Array.forEach (native)
    at callback (/home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:123:12)
    at /home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compilation.js:147:10
    at setError (/home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/NormalModule.js:214:3)
    at /home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/NormalModule.js:178:18
    at /home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/NormalModule.js:137:11
    at /home/rpoitras/dev/components-material-ui/node_modules/loader-runner/lib/LoaderRunner.js:328:11
    at /home/rpoitras/dev/components-material-ui/node_modules/loader-runner/lib/LoaderRunner.js:150:20
    at context.callback (/home/rpoitras/dev/components-material-ui/node_modules/loader-runner/lib/LoaderRunner.js:87:13)
    at Object.<anonymous> (/home/rpoitras/dev/components-material-ui/node_modules/extract-text-webpack-plugin/loader.js:89:12)
    at Compiler.<anonymous> (/home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compiler.js:251:10)
    at /home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/Compiler.js:442:12
    at next (/home/rpoitras/dev/components-material-ui/node_modules/tapable/lib/Tapable.js:81:11)
    at Compiler.<anonymous> (/home/rpoitras/dev/components-material-ui/node_modules/extract-text-webpack-plugin/loader.js:82:4)
    at next (/home/rpoitras/dev/components-material-ui/node_modules/tapable/lib/Tapable.js:83:14)
    at Compiler.<anonymous> (/home/rpoitras/dev/components-material-ui/node_modules/webpack/lib/CachePlugin.js:61:4)
    at Compiler.applyPluginsAsync (/home/rpoitras/dev/components-material-ui/node_modules/tapable/lib/Tapable.js:85:13)

webpack.config.js
const path = require('path')
const webpack = require('webpack')
const validate = require('webpack-validator')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const ExtractTextPlugin = require('extract-text-webpack-plugin')

const PATHS = {
  app: './app/index.js',
  html: './app/index.html',
  lib: './lib/index.js',
  src: path.join(__dirname, 'app'),
  libDir: path.join(__dirname, 'lib'),
  dist: path.join(__dirname, 'dist'),
  routes: path.join(__dirname, 'app/routes'),
  eslintrc: path.join(__dirname, './.eslintrc')
}

const HtmlWebpackPluginConfig = new HtmlWebpackPlugin({
  template: PATHS.html,
  filename: 'index.html',
  inject: 'body'
})

module.exports = env => {
  return validate({
    entry: {
      hmr: [
        'webpack-dev-server/client?http://localhost:4000',
        'webpack/hot/only-dev-server'
      ],
      js: PATHS.app,
      route: PATHS.routes + '/routes',
      lib: PATHS.lib,
      vendor: [
        'react', 'react-router', 'react-dom', 'material-ui', 'babel-polyfill'
      ]
    },
    output: {
      filename: '[name].bundle.js',
      chunkFilename: '[id].bundle.js',
      path: PATHS.dist,
      publicPath: env.prod ? '/' : 'http://localhost:4000/dist/',
      pathinfo: !env.prod
    },
    context: __dirname,
    devtool: env.prod ? 'eval' : 'inline-source-map',
    bail: env.prod,
    externals: {
      'cheerio': 'window',
      'react/lib/ExecutionEnvironment': true,
      'react/lib/ReactContext': true
    },
    module: {
      loaders: [
        {
          test: /(\.js|\.jsx)$/,
          exclude: /node_modules/,
          loaders: ['react-hot', 'babel?presets[]=react,presets[]=es2015,presets[]=stage-0', 'eslint']
        },
        {
          test: /(\.scss|\.css)$/,
          loader: ExtractTextPlugin.extract({
            fallbackLoader: 'style-loader',
            loader: ['css', 'sass']
          })
        }
      ]
    },
    plugins: [
      HtmlWebpackPluginConfig,
      new webpack.optimize.CommonsChunkPlugin({
        name: 'vendor',
        minChunks: Infinity,
        filename: 'vendor.bundle.js'
      }),
      new ExtractTextPlugin({
        filename: '[name].[id].style.css',
        allChunks: false
      })
    ],
    devServer: {
      contentBase: PATHS.dist,
      port: 4000,
      historyApiFallback: true
    }
  })
}

Also I do not have any images in .css or .scss

That error... doesn't make much sense o_O
The code crashes on the last line of this simplified snippet:
var meta = module.meta && module.meta[NS];
if (meta && ...) {
  ...
  compilation.rebuildModule(module, function (err) {
    meta = module.meta[NS];

The second time module.meta[NS] is only reachable if module.meta[NS] was successfully read from before, and that can only happen if module.meta is an object; but you are seeing the crash because, inside rebuildModule, module.meta is suddenly null.
I wonder if the sass-loader is mistakenly resetting the module.meta?

I found out I was running node 4 when this happened. I reinstalled everything with node 6+npm 3 and it all went back to working.

I had the same issue when I forgot to remove the style loader from the "loader" property, so make sure to remove it to only keep it as a "fallback".

It looks like the callback to compilation.rebuildModule is not receiving an error value when there is an error in the compilation. After encountering this issue, I could determine that, when module.meta[NS] was, for some reason, suddenly null, module.errors was not empty and had compilation errors from previous loaders.

For some reason, the following commands fixed the issue for me:
rm -rf node_modules
npm i
npm dedupe

I'm having the same issue.. When I try to load font-awesome, it doesn't work:
My vendor.scss file:
`//# Bootstrap CSS
@import '../../node_modules/bootstrap/dist/css/bootstrap.min.css';
//# Font-Awesome
@import '../../node_modules/font-awesome/css/font-awesome.min.css';`
When I comment the font-awesome import line, it works.. I checked the folder and everything is there.. So, I don't know whats happening..

The issue i found with the same error message, was that ExtractTextPlugin did not like SASS / CSS rules that looked like this
errored
width: (1 / 3 * 100)%;

errored
width: calc(1 / 3 * 100)%;

ok
width: 33.33333%;

I can confirm @Kovensky's findings.
I used the node-inspector to debug webpack and set a breakpoint at extract-text-webpack-plugin/index.js:257. module.errors was indeed not empty when there was a problem with module.meta.
In my case it was a combination of missing packages (url-loader/file-loader) and invalid paths in url(...) values in some of the (S)CSS. Fixing those problems got everything working.

@Kovensky that's interesting at the time I don't think I had url-loader as a devDependency. If I can a chance I try this again and see if that helps.  It may help others that are still stuck if you could post your package.json and webpack.config.js.
@as-com I'm pretty sure npm does the dedupe by default as of version 3.0

@rpoitras npm dedupe was still able to remove and symlink some packages.

Thanks @as-com that's good to know.

@Kovensky Safe to close?

Let's close.


Cannot find reference 'encoding' in 'nerf_helper'.py'.

Dear export, hello! I want to learn about the details of "Cannot find reference 'encoding' in 'nerf_helper'.py'. ". I saw the description of pybind11 from CUDA EXTENSION. But there is a reference information "Cannot find reference 'encoding' in 'nerf_helper'.py'. "  in model.py when running. Thank you very much!
model.py
from nerf_helper import encoding

nerf_extension.cu
PYBIND11_MODULE (TORCH_EXTENSION_NAME, nerf_helper)
{
  	nerf_helper.def ("comservativeSampling", &cudaSampler, conservative_sampler_docs.c_str());
  	nerf_helper.def ("sampling", &easySampler, sampler_docs.c_str());
	nerf_helper.def ("encoding", &positionalEncode, pe_docs.c_str());  // This !! Thank you !!!
	nerf_helper.def ("invTransformSample", &inverseTransformSample, inv_tf_docs.c_str());
	nerf_helper.def ("invTransformSamplePt", &inverseTransformSamplePt, inv_tf_pt_docs.c_str());
	nerf_helper.def ("imageSampling", &imageSampler, image_sampler_doc.c_str());
	nerf_helper.def ("validSampling", &validSampler, valid_sampler_doc.c_str());
}

There is no nerf_helper.py. nerf_helper as you see, is defined by setup.py in folder cuda/ (line 10). The module is called nerf_helper and it is already compiled, dynamically linked and loaded by your executable script. Therefore there is no python definition for encoding. Function encoding is "declared" in python, and defined in CUDA c++ (plz refer to file cuda/pe.cu). The definition is linked to the name encoding.
So, if python interpreter can not fine encoding, it might be (if I got it right):

You didn't correctly compile pytorch CUDA extension (follow README.md, running setup.py), so the interpreter had no where to find the definition of this function. Solution is to compile CUDA extension correctly (normally, successful compilation will result in .egg .dist(?maybe) files and it will tell you Finished ... (I don't remember) in the terminal).

Thank you dear export!! I could generate nerf_helper.py after running cuda.
nerf_helper.py def __bootstrap__():     global __bootstrap__, __loader__, __file__     import sys, pkg_resources, importlib.util     __file__ = pkg_resources.resource_filename(__name__, 'nerf_helper.cpython-39-x86_64-linux-gnu.so')     __loader__ = None; del __bootstrap__, __loader__     spec = importlib.util.spec_from_file_location(__name__,__file__)     mod = importlib.util.module_from_spec(spec)     spec.loader.exec_module(mod) __bootstrap__()
Is this not normal? Thank you very much!

(9 line) Thank you very much!!!!

I directly run setup.py with your method, I understand that cuda is not used in the project, but I am just curious why the compiled nerf_helper cannot retrieve the encoding.

Well, it works for me even after checking out this older version and recompile:

Did you try importing this in a python shell? What does it output?

Yes! Your code will not generate any errors during runtime! They are as good as you are! ! Thank you very much!

Thank you. That's a little overstating. Hope u can learn the things u want.


Setting a User as "Restricted User" via API is missing.

Gitea version (or commit ref): 1.13.0
Git version:
Operating system:

Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No

Log gist:

Description
Setting a User as "Restricted User" is only possible via Web Interface not via API.
Screenshots

#14630 is a nice example how to extend api with a field to expose info and to edit info


Gather feedback and finalise framework docs spec

User story
As a content writer, I want to know what framework content to write, so I can create it confidently.
The existing framework docs spec is at https://docs.google.com/document/d/1T4s2R_aLefiNWxeC4g-dbEXXfBw_tGw5NdSOS6OCRvM/edit#heading=h.w95jqs1xx0k8
Acceptance Criteria

[ ] Spec has been finalized.

Tasks

[ ] Gather feedback from the people I have sent the framework docs spec to.

[ ] Finalize the docs spec.

I need to chase people up for feedback. Nothing recived so far.


Attempt to setup codecov for testing insights

Attempt to set up Covdecov in CI to improve code testing and overall code quality

Done in PR https://github.com/mcmancini/pyCLMS/pull/8


AMF pod can not run properly after DB dependency is removed

Bug Description
Today, I deployed the sdcore-k8s with sdcore from 1.5/edge channel and AMF is entered in a loop when we ran the simulation.
AllocateAmfUeNgapID method calls Drsm.AllocateInt32ID function and it tries to update DB which is the cause of this problem.
func (context *AMFContext) AllocateAmfUeNgapID() (int64, error) {
	// val, err := AllocateUniqueID(&amfUeNGAPIDGenerator, "amfUeNgapID")
	val, err := context.Drsm.AllocateInt32ID()
	if err != nil {
		logger.ContextLog.Errorf("Allocate NgapID error: %+v", err)
		return -1, err
	}

	logger.ContextLog.Infof("Allocate AmfUeNgapID : %v", val)
	return int64(val), nil
}

microk8s-localhost  microk8s/localhost  3.4.3    unsupported  17:11:55+03:00

App                       Version  Status   Scale  Charm                     Channel        Rev  Address         Exposed  Message
amf                                active       1  sdcore-amf-k8s            1.5/edge       422  <IP_ADDRESS>  no
ausf                               active       1  sdcore-ausf-k8s           1.5/edge       299  <IP_ADDRESS>  no
gnbsim                             active       1  sdcore-gnbsim-k8s         1.5/edge       265  <IP_ADDRESS>   no
grafana-agent             0.35.2   waiting      1  grafana-agent-k8s         latest/stable   68  <IP_ADDRESS>   no       installing agent
mongodb                            active       1  mongodb-k8s               6/beta          38  <IP_ADDRESS>  no       Primary
nms                                active       1  sdcore-nms-k8s            1.5/edge       303  <IP_ADDRESS>  no
nrf                                active       1  sdcore-nrf-k8s            1.5/edge       338  <IP_ADDRESS>  no
nssf                               active       1  sdcore-nssf-k8s           1.5/edge       244  <IP_ADDRESS>  no
pcf                                active       1  sdcore-pcf-k8s            1.5/edge       314  <IP_ADDRESS>   no
router                             active       1  sdcore-router-k8s         1.5/edge       201  <IP_ADDRESS>   no
secondwebui                        active       1  sdcore-webui-k8s          1.5/edge       251  <IP_ADDRESS>  no
self-signed-certificates           active       1  self-signed-certificates  latest/stable   72  <IP_ADDRESS>  no
smf                                active       1  sdcore-smf-k8s            1.5/edge       355  <IP_ADDRESS>  no
traefik                   v2.11.0  active       1  traefik-k8s               latest/stable  191  <IP_ADDRESS>        no
udm                                active       1  sdcore-udm-k8s            1.5/edge       274  <IP_ADDRESS>  no
udr                                active       1  sdcore-udr-k8s            1.5/edge       284  <IP_ADDRESS>  no
upf                                active       1  sdcore-upf-k8s            1.5/edge       346  <IP_ADDRESS>  no
webui                              active       1  sdcore-webui-k8s          1.5/edge       251  <IP_ADDRESS>   no

Unit                         Workload  Agent  Address      Ports  Message
amf/0*                       active    idle   <IP_ADDRESS>
ausf/0*                      active    idle   <IP_ADDRESS>
gnbsim/0*                    active    idle   <IP_ADDRESS>
grafana-agent/0*             blocked   idle   <IP_ADDRESS>         Missing ['grafana-cloud-config']|['logging-consumer'] for logging-provider; ['grafana-cloud-config']|['send-remote-wr...
mongodb/0*                   active    idle   <IP_ADDRESS>         Primary
nms/0*                       active    idle   <IP_ADDRESS>
nrf/0*                       active    idle   <IP_ADDRESS>
nssf/0*                      active    idle   <IP_ADDRESS>
pcf/0*                       active    idle   <IP_ADDRESS>
router/0*                    active    idle   <IP_ADDRESS>
secondwebui/0*               active    idle   <IP_ADDRESS>
self-signed-certificates/0*  active    idle   <IP_ADDRESS>
smf/0*                       active    idle   <IP_ADDRESS>
traefik/0*                   active    idle   <IP_ADDRESS>
udm/0*                       active    idle   <IP_ADDRESS>
udr/0*                       active    idle   <IP_ADDRESS>
upf/0*                       active    idle   <IP_ADDRESS>
webui/0*                     active    idle   <IP_ADDRESS>

To Reproduce
Deploy SD-Core using getting_started tutorial and try to run the simulation.
Environment
Juju: 3.4.3
Terraform 0.12.0
Relevant log output
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  88
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 88 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  7293
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 7293 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  13779
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 13779 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  3132
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 3132 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  13127
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 13127 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  6263
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 6263 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  8230
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 8230 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  3547
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 3547 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  4200
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 4200 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  5000
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 5000 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  5198
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 5198 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  12921
2024-06-14T12:58:48.051Z [amf] 2024/06/14 12:58:48 Adding chunk 12921 failed. Retry again
2024-06-14T12:58:48.051Z [amf] 2024-06-14T12:58:48Z [DEBU][DRSM][App] Found chunk Id block  4094

Additional context
No response

Closing this issue as we are not using the db integration anymore


[FEATURE]  add Dependabot

Description
To add Dependabot to a project, create a dependabot.yml file in project root. Configure it to check for updates in project's dependencies, and set up notifications for automated pull requests. Dependabot will then help keep dependencies up-to-date, enhancing project stability and security.
Screenshots
No response
Additional information
No response
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

was thinking of adding this, thanks for raising. assigned to you, make sure you follow the rules 👉🏽here👈🏽, else your PR will not be accepted and will be closed. Good Luck


build(deps): use utoipa crate upstream URL as git dependency

Type of Change

[ ] Bugfix
[ ] New feature
[ ] Enhancement
[ ] Refactoring
[x] Dependency updates

Description

This PR updates the repository URL for the utoipa crate to use the upstream repository URL instead of my fork.
Motivation and Context

Since juhaku/utoipa#436 was merged, my fork is no longer required. However, since it could take some time for the next release of the crate, we'll be using it as a git dependency.
How did you test it?

Regenerated the OpenAPI spec file, there are no changes in property order of the schemas.
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

I think it would be useful to add the comment that you're using github version for this particular issue, so that others will know when to move to the cratesio version.

I think it would be useful to add the comment that you're using github version for this particular issue, so that others will know when to move to the cratesio version.

Done!


Translation of html element attributes

Is there any support for the translation of html element attributes (e.g. alt, title, placeholder)?
This is supported out of the box by Angular i18n.  See Add i18n-... translation attributes.
To me, this is quite an important feature, especially for proper accessibility support.

<input placeholder="Some default text that should be translatable">

You can use bindings on attributes like this:
 or like this:
<input placeholder="{{'key' | translate}}">
I recommend the first one which will only set the value once it's available.

Could you please help me regarding this issue:
https://stackoverflow.com/questions/55646825/translate-attribute-values-with-ngx-translate-angular

I am trying to use ngx-translate for attribute values like p-messages text, p-column header, p-tabPanel header

I tried the following but it doesn't work:

Is there any way to use ngx-translate for these situations?

I am trying to use ngx-translate for attribute values like p-messages text, p-column header, p-tabPanel header

I tried the following but it doesn't work:

Is there any way to use ngx-translate for these?

I am trying to use ngx-translate for attribute values like p-messages text, p-column header, p-tabPanel header

I tried the following but it doesn't work:

Is there any way to use ngx-translate for these?


Rockets Stacking

Built a space station and I had a friend come up to my station. I have the proper pads down and they each have linkers that are individually connected to each pad. However it is not recognizing the the pad is occupied.

I'm having a bit of a hard time understanding the exact setup, you're describing so just to verify.  Do you have something like the following:
Pads A and B are on the space station
Pads C and D are on the ground
Pad C contains a linker programmed with the location of pad A, and pad D is likewise linked to B.  But you took off from pad C, your friend took off from pad D, and both of you landed on the same pad?

Both took off from the same pad.

Do you have time to get on my discord?

Question, Will their be any updates within the next 3-4 days? Just wondering. Would like to move the modpack to Curse.

I'll try to get back to you on everything at once.
Between you and your friend taking off, did you change the linker in the
pad you took off from?  Reason I ask is because it it expected behavior for
the rockets to land on each other if the same linker was used in the pad
the rockets are being launched from.  It was designed with flexibility in
mind for the player.  Rockets should only check if a pad is in use if no
linkers are being used to specify the landing location.
If you did swa out the linker does the location the rockets landed also
happen to be the spawn location for the station?  Because if so that would
indicate the linkers are not working at all.
Hate to say this, but I currently do no have time to come on a discord
server.  The earliest I can probably come on would be Thursday or Friday
night due to my obligations not related to minecraft, animation, or game
development.
That being said I'm going to try to get a build pushed laterm today.
Though that's contingent on whether or not it takes me more than 15 minutes
to backport the new planet discovery system to 1.7.10.  If I don't hAve a
release by 6 hours from the time of posting.  That'll also probably not
happen until Thursday or Friday.

Ok, I used different linkers for each rocket.
The reason I would like you to come to our Discord is to get some info and make some suggestions for advancement of your mod. It is one of the best Tek mods I have seen and would like to help you in advancement of your mod. Their is so many possibilities for your mod. Some of our ideas would propel you beyond the competition if you are willing to hear them. You can bring any of your Deb's you would like.

Would it be possible to either print rocket(s) assigned on a pad block (Rocket Monitoring Station?) and/or pads assigned on a rocket (Guidance Computer) block?  Maybe in a linker?  It wouldn't really matter how, popup GUI, placed on block, called through NEI/JEI, whatever.

@Tyrantin I'd be interested to hear them, will see if we can arrange something.  Though I will likely be unavailable for more than 4 or 5 minutes at a time until Friday or Saturday.
@DVorriose I'm not really sure how feasible that is currently, right now rocket destinations have kinda on odd heirarchy going on.  The way I've got it setup right now is that when a rocket takes off, nearby pads will check to see if a rocket is on top of it, if one is it overrides the destination, so rockets are not really assigned to pads per se.  The pads are really more assigned to dimensions and coordinates than anything.  The idea was that the user would be able to put signs down to remember which pad was which.
Though I have plans in the future to be able to name and then be able to select named pads.

That's cool, understandable. Will spot for Friday then what is you TZ so we can plan accordingly.

I'm EST, and should be available between 3EST and 5EST Friday

Awesome. I'm EST as well

Perhaps a bit late to ask, but is there an ip address or something I can use to connect or some kind of identifier?


Image screenshots slightly different from original

Not a major issue, but sometimes when the images are taken, they are slightly different from the original, so it fails the reg-viz diff test. I also tried using another diff tool and it appears to be the screenshots themselves that are different, not the reg-viz tester misreading them.
I am curious if anyone else experiences this issue, and how you have been dealing with it. Sometimes reg-viz comments on the PR that all our components have changed, when in reality they are just slightly off.
I can set the threshold on reg-viz, but I am curious why it is happening in the first place. Perhaps this is just specific to the docker image I am using with chromium?
Pictures below:

Hi @camsloanftc Thank you for Issues :smiley:
Unfortunately it seemed impossible to understand the cause soon ...
If possible, it would be very helpful if you could share the repository :+1:
In the case of a private repository, there is no problem even with the minimum reproducible code.

Subpixel Antialiasing. Could be mitigated by changing gamma, as long this operation will "cutoff" antialiasing. But how to change gamma?

Same type of issue by running storybook-chrome-screenshot + jest-image-snapshot on two developing work Linux station (one with KDE, the other with Mate). We have some diff regarding content. That seems to be linked to a font issue which are not exactly render the same on each device...

That's almost inevitable problem - the only way is to perform image shooting in consistent environment, like docker.

In general to create screenshots with puppeteer differ from every os, depending on graphic drivers/fonts and so on.
That is why the only way to get consistent results is to use some chromium driver container such as running in a docker container. The best and easiest solution is to use https://hub.docker.com/r/browserless/chrome/ and let it connect to it by ws://
It would be awesome to add some native support and help to this project.


DOCS-2048: Adds procedure to export custom roles

This PR adds a procedure for exporting custom roles from the Calico Cloud web console.
Product Version(s):

Issue:

https://tigera.atlassian.net/browse/DOCS-2060
Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@ozdanborne Can you take a look a this?

Perfect!


Make daemonsets upgradeable

Canal will be covered by a separate PR

ci check this

@chupsuk @jjungnickel @bogdando Can you folks review?


Fix uncaught AttributeError

Fixes this error:
Expected {W:(_ABC...) | "{" | "}" | "(" | ")" | "*" | "&" | "," | W:(::) | nested <> expression} (at char 4), (line:1, col:5)
Traceback (most recent call last):
File "/usr/share/glib-2.0/gdb/gobject_gdb.py", line 286, in next
emission = self.find_signal_emission ()
File "/usr/share/glib-2.0/gdb/gobject_gdb.py", line 274, in find_signal_emission
if frame_name(self.queue[i]) == "signal_emit_unlocked_R":
File "/usr/share/glib-2.0/gdb/gobject_gdb.py", line 148, in frame_name
return str(frame.function())
File "/.../gdb-pretty-frame-cpp/framefilter.py", line 16, in function
name = self.frame_printer.parse_line(str(frame.name()))
File "/.../gdb-pretty-frame-cpp/cpp_pretty_frame.py", line 109, in parse_line
return self.format_nested(nested.asList())
AttributeError: 'list' object has no attribute 'asList'

LGTM, many thanks :+1:


2.5.x

Coverage increased (+0.6%) to 91.449% when pulling 420c9790d82f7e17c9ce7466e9d22012cd931b5f on stianst:2.5.x into 34eca1e9880471aa6c449a636f856340e3de7450 on keycloak:2.5.x.

Coverage increased (+0.6%) to 91.449% when pulling 0a4c5f78387d9d77ac908507ab951f438617cff8 on stianst:2.5.x into 34eca1e9880471aa6c449a636f856340e3de7450 on keycloak:2.5.x.

Coverage increased (+0.6%) to 91.449% when pulling 0a4c5f78387d9d77ac908507ab951f438617cff8 on stianst:2.5.x into 34eca1e9880471aa6c449a636f856340e3de7450 on keycloak:2.5.x.

Coverage increased (+0.6%) to 91.449% when pulling 0a4c5f78387d9d77ac908507ab951f438617cff8 on stianst:2.5.x into 34eca1e9880471aa6c449a636f856340e3de7450 on keycloak:2.5.x.


beforeAll, beforeEach, afterEach, afterAll do not work from setupFilesAfterEnv

Hi there, thanks for the great project!
I consider jest's partial test isolation to be more trouble than it's worth and would rather switch to jest-light-runner, don't mess around with globals (expect with jest.spyOn) and use the built-in jest features to revert these changes after every test.
However, it seems that the resetMocks and restoreMocks config option no longer works with jest-light-runner (probably a separate bug), so I tried working around that using a custom setup script (with setupFilesAfterEnv).
Actual behavior
But it seems that beforeAll, beforeEach, afterEach, afterAll  simply do nothing when called from such a script, for example:
setup-after-env.js:
console.log("setup-after-env")
beforeAll(() => console.log("setup beforeAll"))
beforeEach(() => console.log("setup beforeEach"))
afterEach(() => console.log("setup afterEach"))
afterAll(() => console.log("setup afterAll"))

demo.test.js:
it("should work", () => console.log("test"))

With jest-light-runner, this only prints:
setup-after-env
test

edit: Here's a minimal reproduction repo
Expected behavior
setup-after-env
setup beforeAll
setup beforeEach
test
setup afterEach
setup afterAll

Same issue here


support purescript 0.13.x

There has been some confusion caused by people following the given directions to install purescript, which installs version 0.13.2.  The confusion is caused when they try to build an exercise, and the build fails.
This is because purescript version 0.13.x requires purescript-typelevel-prelude version v5.0.0 to work.
This PR bumps the version of purescript-test-unit to v15.0.0, which transitively updates the version of purescript-typelevel-prelude as well.
Note that this should still work with purescript v12.2.2 and up (see https://github.com/purescript/purescript-typelevel-prelude/releases/tag/v5.0.0)

So we seem to not have anyone maintaining this track atm, and none of the core team know PureScript, so we can’t promise it works, but it seems like it might help, so we're going to merge it! :)

@iHiD I noticed that if you do exercism download --exercise=hello-world --track=purescript it still downloads the old bower.json. Is there some other step I need to take to make sure the files get updated upstream?

@colinwahl Have you downloaded hello-world before? I think the system remembers which version you started and downloads your version on subsequent downloads as well.
It seems to be working for me with all new exercises I start.

I think I have to further investigate into this issue. I was expecting that in the case, you had already downloaded it before, you still get the old files, but there would be a button on the exercise page on exercism.io, that allows you to update to the current version. – But it seems there is no such button in this case.
I have to find out and ask other maintainers how this is working exactly.

But it seems there is no such button in this case.

I think this is because the test-suite hasn't changed. That's the trigger for the button appearing.


Wrong pluralization when there is "people" in the middle of the word

The pluralization of the word personal is wrong:
iex(10)> Inflex.pluralize "personal"
"peopleal"

Here, I expected the output to be personals.
In my use case, I wanted to translate personal trainer, but it finds people in the middle and pluralizes that.
iex(11)> Inflex.pluralize "personal_trainer"
"peopleal_trainer"

I expected the output to be personal_trainers.
The same happens when the words are separated by a space:
iex(6)> Inflex.pluralize "personal trainer"
"peopleal trainer"

Thanks! The fix has been merged


[Optimization-1761][admin,core,web] Remove shared session

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

LGTM


Call the value first instead of never for editor.selectSuggestions

Testing #42329
never option looks as if suggestion will never be selected. But the purpose of this setting value is to always select first suggestion (Description tells the same).
So I think it is easy to understand if we call the value first or similar that conveys the meaning directly.

We agreed on editor.suggestSelection with first, recentlyUsed, and recentlyUsedByPrefix


50 Readme - update onboarding instructions

Thanks to
https://github.com/trynmaps/tryn-react/commit/d1626c8ff51c1a68d0a2954a93d568b4a0ff6ad6
we can now run the client locally without needing the whole
backend set up. The Readme has been updated to reflect this.

@akeimach @frhino let me know if it's clear enough :)


Training results not good as expected

hi @Vegeta2020 , SE-SSD is a wonderful work ! but my results is so low after training about 50 epoch, I  only change the data path and set load_from to the model provided in README , could you give me some advice?
Here is my results after training 50 epochs

I guess you used the info / dbinfo pkl files or gt_database produced by other repositories? Otherwise, it's hard to get such an result.

Thanks @Vegeta2020
I use create_data.py in this repo to create gt_database.
I also try to use CIA-SSD pretrained model and se-ssd model trained from scrath to initialize teacher and student, but both results are not good. Could you share your initialization model? I assume the initialzation model is the keypoint.

@Vegeta2020 the loss during training gets larger and larger and I cant get a good result (like result in README, there is a 20 mAP gap). it block me several days :(

@Vegeta2020 the loss during training gets larger and larger and I cant get a good result (like result in README, there is a 20 mAP gap). it block me several days :(

Hi, pigtigger, did you reproduce the paper result?

@Vegeta2020 the loss during training gets larger and larger and I cant get a good result (like result in README, there is a 20 mAP gap). it block me several days :(

Hi, pigtigger, did you reproduce the paper result?

not yet

@Vegeta2020 the loss during training gets larger and larger and I cant get a good result (like result in README, there is a 20 mAP gap). it block me several days :(

Hi, pigtigger, did you reproduce the paper result?

not yet

so sad😭

@Vegeta2020 the loss during training gets larger and larger and I cant get a good result (like result in README, there is a 20 mAP gap). it block me several days :(

Hi, pigtigger, did you reproduce the paper result?

not yet

hi, pigtigger, now I can finally run the code, but I can set batch size = 1 with a v100 32 gpu, does it normal ? when set batch_size = 2, error happen, CUDNN_STATUS_NOT_SUPPORTED. This error may appear if you passed in a  non-contiguous input.
when set batch size = 1, the actually memory occupied is 12G.

@Vegeta2020 the loss during training gets larger and larger and I cant get a good result (like result in README, there is a 20 mAP gap). it block me several days :(

Hi, pigtigger, did you reproduce the paper result?

not yet

After training after 13 epochs， my loss looks like increasing。。so sad

I meet the same problem, does anyone reproduce the results?
------------------ 原始邮件 ------------------
发件人:                                                                                "Vegeta2020/SE-SSD"                                                                                @.>;
发送时间: 2021年9月9日(星期四) 晚上7:41
@.>;
<EMAIL_ADDRESS>主题: Re: [Vegeta2020/SE-SSD] Training results not good as expected  (#35)
@Vegeta2020 the loss during training gets larger and larger and I cant get a good result (like result in README, there is a 20 mAP gap). it block me several days :(
Hi, pigtigger, did you reproduce the paper result?
not yet
After training after 13 epochs， my loss looks like increasing。。so sad
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I meet the same problem, does anyone reproduce the results?
…

I just wonder how much gpu memory you need when reproducing, I can only set batch_size = 1 even I use a v100 32g gpu

I set 4 on 24G Titan, it's ok.
I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that?
------------------ 原始邮件 ------------------
发件人:                                                                                "Vegeta2020/SE-SSD"                                                                                @.>;
发送时间: 2021年9月9日(星期四) 晚上8:07
@.>;
<EMAIL_ADDRESS>主题: Re: [Vegeta2020/SE-SSD] Training results not good as expected  (#35)
I meet the same problem, does anyone reproduce the results?
…
I just wonder how much gpu memory you need when reproducing, I can only set batch_size = 1 even I use a v100 32g gpu
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I set 4 on 24G Titan, it's ok. I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that?
…

I did use pretrain model, in code I just change model_ema = build_detector(), no other change, when I set batch_size = 2, just error

I set 4 on 24G Titan, it's ok. I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that?
…

my initial loss is 0.55 around.

I set 4 on 24G Titan, it's ok. I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that?
…

what's more, I'm new to det3d, I didn't see the tensorboard log, did you have tensorboard log when reproducing the code.

I set 4 on 24G Titan, it's ok. I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that?
…

my initial loss is 0.55 around.

which pretrained model did you use ? I have tried CIA-pretrained model and the model provided in SE-SSD README, the initial loss is about 0.55 for CIA-pretrained model  and  0.45 for SE-SSD, but both  can not get a good result

I set 4 on 24G Titan, it's ok. I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that?
…

my initial loss is 0.55 around.

which pretrained model did you use ? I have tried CIA-pretrained model and the model provided in SE-SSD README, the initial loss is about 0.55 for CIA-pretrained model and 0.45 for SE-SSD, but both can not get a good result

CIA-pretrained, as I see the author say use this one in other question

I set 4 on 24G Titan, it's ok. I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that?
…

my initial loss is 0.55 around.

which pretrained model did you use ? I have tried CIA-pretrained model and the model provided in SE-SSD README, the initial loss is about 0.55 for CIA-pretrained model and 0.45 for SE-SSD, but both can not get a good result

It's a little strange why I can only set batch size = 1 with v100 32g

I did not meet the gpu memory error after using pretrained model, it is so strange , maybe  it is  env problem since you did not change the code, btw  I also change the line you mentioned before
------------------ 原始邮件 ------------------
发件人:                                                                                "Vegeta2020/SE-SSD"                                                                                @.>;
发送时间: 2021年9月9日(星期四) 晚上8:35
@.>;
<EMAIL_ADDRESS>主题: Re: [Vegeta2020/SE-SSD] Training results not good as expected  (#35)
I set 4 on 24G Titan, it's ok. I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that?
…
my initial loss is 0.55 around.
which pretrained model did you use ? I have tried CIA-pretrained model and the model provided in SE-SSD README, the initial loss is about 0.55 for CIA-pretrained model and 0.45 for SE-SSD, but both can not get a good result
It's a little strange why I can only set batch size = 1 with v100 32g
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I did not meet the gpu memory error after using pretrained model, it is so strange , maybe  it is  env problem since you did not change the code, btw  I also change the line you mentioned before  ------------------ 原始邮件 ------------------ 发件人: "Vegeta2020/SE-SSD" @.>; 发送时间: 2021年9月9日(星期四) 晚上8:35 @.><EMAIL_ADDRESS>主题: Re: [Vegeta2020/SE-SSD] Training results not good as expected (#35) I set 4 on 24G Titan, it's ok. I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that? … my initial loss is 0.55 around. which pretrained model did you use ? I have tried CIA-pretrained model and the model provided in SE-SSD README, the initial loss is about 0.55 for CIA-pretrained model and 0.45 for SE-SSD, but both can not get a good result It's a little strange why I can only set batch size = 1 with v100 32g — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

tomorrow morning will finish training, looking forward to the result.

I did not meet the gpu memory error after using pretrained model, it is so strange , maybe  it is  env problem since you did not change the code, btw  I also change the line you mentioned before  ------------------ 原始邮件 ------------------ 发件人: "Vegeta2020/SE-SSD" @.>; 发送时间: 2021年9月9日(星期四) 晚上8:35 @.><EMAIL_ADDRESS>主题: Re: [Vegeta2020/SE-SSD] Training results not good as expected (#35) I set 4 on 24G Titan, it's ok. I guess you need to use a pretrained model to initialize the student and teacher model, have you tried that? … my initial loss is 0.55 around. which pretrained model did you use ? I have tried CIA-pretrained model and the model provided in SE-SSD README, the initial loss is about 0.55 for CIA-pretrained model and 0.45 for SE-SSD, but both can not get a good result It's a little strange why I can only set batch size = 1 with v100 32g — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

So sad, after SE-SSD training, don't have improvement compared with the pretrained model provided by CIA-SSD repo.

@AndyYuan96 did you train the CIA-SSD pretrained model yourself?

@AndyYuan96 did you train the CIA-SSD pretrained model yourself?

no，I use the model from CIA-SSD repo as pretrained model.


Use database sepecified in the connect string when calling client.db().

This in service of specifying ONLY the url when connecting.  The operative bit here is the removal of config.name from the client.db() call that was on L592, and is now on L596. The unexpected behavior caused by this has been haunting me for a while.  The unexpected behavior occurs when one is specifying a self contained url string that is designed to provide the database, username and password, whereby none of these values are set to non-default values in the config.
For instance: mongodb://my-user:my-password@mongos.example.com:27075/my_database?ssl=true.  With this connect string solely, a valid authenticated database connection can be made.  However, with line client.db(config.name), the client tries to connect to a non-existent database, bedrock_dev (the default value) and an authentication error ensues because the user that has authenticated to the database my_database has no permissions for the bedrock_dev database.
client.db() when called with no options, returns the database that was from the connect string, and therefore it is redundant at best, and creates a problem if config.name is not being set because the url config is in effect.
See: https://mongodb.github.io/node-mongodb-native/3.5/api/MongoClient.html#db

I forgot to add that this is simply a patch release as it does not impact typical dev use cases where the typical bedrock.mongodb config options are utilized.  These are composed into the connect string, and the default database returned by client.db() is still the right database.

@aljones15 this branch has now been tested using authentication based solely on the URL config option (user provided connection string), specifying username/password via regular bedrock config (auto-composed connect string) and no authentication (test suite).
This does not alter any existing error handling.


data purger description

the description for the Data Purger role is very vague. Can it be enhanced?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 99581afb-7950-6daa-7227-055d04446b7e
Version Independent ID: f1a5bf89-9e54-aede-3a9a-70788a95927b
Content: Azure built-in roles - Azure RBAC
Content Source: articles/role-based-access-control/built-in-roles.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@DeanGross
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Hi @DeanGross
Thanks for the feedback. We made an update to the description. Update should appear sometime next week.
thanks

#please-close


Can not use AudioSource with bevy_asset_loader on the latest main branch

The following code fails to compile on the latest commit of bevy_kira_audio (b721820).
This issue is very similar to #31, however I can't find a commit that works for me. I absolutely need the feature introduced on this commit, but no commit after this one compiles successfully.
I also do not understand why this error is thrown in the first place. this code clearly shows that TypeUuid is defined for AudioSource so I'm not sure where the error is coming from.
Failing code:

NiklasEi/bevy_game_template
bevy and bevy_kira_audio set to the latest commit

#[derive(AssetCollection)]
pub struct AudioAssets {
    #[asset(path = "audio/flying.ogg")]
    pub flying: Handle<AudioSource>,
}

Error:
error[E0277]: the trait bound `AudioSource: TypeUuid` is not satisfied
   --> src/loading.rs:34:17
    |
34  |     pub flying: Handle<AudioSource>,
    |                 ^^^^^^^^^^^^^^^^^^^ the trait `TypeUuid` is not implemented for `AudioSource`
    |

Cargo.toml
...

[features]
default = [
    "bevy_kira_audio/ogg",
    "bevy/bevy_winit",
    "bevy/render",
    "bevy/png",
    "bevy/x11",
]

dev = ["bevy/dynamic"]

[dependencies]
bevy = { git = "https://github.com/bevyengine/bevy", rev = "7d554146524987b050923841de06c7d18adf66e9", default-features = false }
bevy_kira_audio = { git = "https://github.com/NiklasEi/bevy_kira_audio", rev = "b721820d0f7b479a136cc2a9d51c23bbedd2934e" }
bevy_asset_loader = "0.11.0"
rand = "0.8.5"

[target.'cfg(target_os = "linux")'.dependencies]
winit = { version = "0.26.1", features = ["x11"] }

[build-dependencies]
embed-resource = "1.7.2"

...

Yes, I have not been actively maintaining the bevy_main branches since the decision for Bevy train releases. If you are able to, I would be open for PR to update the bevy commit on these branches.
Latest ETA is probably in around 2 weeks with Bevy 0.8

In case you can't wait for the Bevy 0.8 release: the bevy_main branch is updated now.

Are you also using the bevy_main branch of bevy_asset_loader? They should work fine together on the pinned commit.

I tried deleting cargo.lock, specifying the version in Cargo.toml, deleting the ~/.cargo directory, using the bevy commit used by bevy_kira_audio, using the bevy commit used by bevy_asset_loader, etc. None of them worked. They always fail with the same error:
error: failed to select a version for `web-sys`.
    ... required by package `wgpu v0.12.0`
    ... which satisfies dependency `wgpu = "^0.12.0"` of package `bevy_render v0.8.0-dev (https://github.com/bevyengine/bevy?rev=518408dfdaa8884ba86a71512de2a7d57848413d#518408df)`
    ... which satisfies git dependency `bevy_render` of package `bevy_core_pipeline v0.8.0-dev (https://github.com/bevyengine/bevy?rev=518408dfdaa8884ba86a71512de2a7d57848413d#518408df)`
    ... which satisfies git dependency `bevy_core_pipeline` of package `bevy_internal v0.8.0-dev (https://github.com/bevyengine/bevy?rev=518408dfdaa8884ba86a71512de2a7d57848413d#518408df)`
    ... which satisfies git dependency `bevy_internal` of package `bevy v0.8.0-dev (https://github.com/bevyengine/bevy?rev=518408dfdaa8884ba86a71512de2a7d57848413d#518408df)`
    ... which satisfies git dependency `bevy` of package `bevy_kira_audio v0.10.0 (https://github.com/NiklasEi/bevy_kira_audio?rev=2d9a0050ed66c030d17e694fc04a8379c399a0e1#2d9a0050)`
    ... which satisfies git dependency `bevy_kira_audio` of package `exyleio v1.0.0 (/media/pomp/data/projects/exyleio/exyleio-client)`
versions that meet the requirements `^0.3.53` are: 0.3.58, 0.3.57, 0.3.56, 0.3.55, 0.3.54, 0.3.53

the package `wgpu` depends on `web-sys`, with features: `GpuBufferUsage` but `web-sys` does not have these features.

all possible versions conflict with previously selected packages.

  previously selected package `web-sys v0.3.58`
    ... which satisfies dependency `web-sys = "^0.3.53"` of package `wgpu v0.12.0`
    ... which satisfies dependency `wgpu = "^0.12.0"` of package `bevy_render v0.8.0-dev (https://github.com/bevyengine/bevy?rev=518408dfdaa8884ba86a71512de2a7d57848413d#518408df)`
    ... which satisfies git dependency `bevy_render` of package `bevy_core_pipeline v0.8.0-dev (https://github.com/bevyengine/bevy?rev=518408dfdaa8884ba86a71512de2a7d57848413d#518408df)`
    ... which satisfies git dependency `bevy_core_pipeline` of package `bevy_internal v0.8.0-dev (https://github.com/bevyengine/bevy?rev=518408dfdaa8884ba86a71512de2a7d57848413d#518408df)`
    ... which satisfies git dependency `bevy_internal` of package `bevy v0.8.0-dev (https://github.com/bevyengine/bevy?rev=518408dfdaa8884ba86a71512de2a7d57848413d#518408df)`
    ... which satisfies git dependency `bevy` of package `bevy_kira_audio v0.10.0 (https://github.com/NiklasEi/bevy_kira_audio?rev=2d9a0050ed66c030d17e694fc04a8379c399a0e1#2d9a0050)`
    ... which satisfies git dependency `bevy_kira_audio` of package `exyleio v1.0.0 (/media/pomp/data/projects/exyleio/exyleio-client)`

failed to select a version for `web-sys` which could resolve this conflict

Running cargo update when using this dependency config:
[dependencies]
bevy = { git = "https://github.com/bevyengine/bevy", rev = "518408dfdaa8884ba86a71512de2a7d57848413d", default-features = false }
bevy_kira_audio = { git = "https://github.com/NiklasEi/bevy_kira_audio", rev = "2d9a0050ed66c030d17e694fc04a8379c399a0e1" }
# bevy_asset_loader = { git = "https://github.com/NiklasEi/bevy_asset_loader", rev = "1d8e9acedcb05e3333ee62ccafd360156dbf04ab" }

does work, so I suspect this error is due to a bevy version incompatibility between bevy_kira_audio and bevy_asset_loader.

Can confirm! 👍
Native build works just fine but the web build is complaining about some errors.
This seems to be a separate issue tho.
Thanks for your help!


To re-align the links in the NavBar and to improve hover effect

Describe the bug
Links in Navbar not working properly and hover effect is also not so good
To Reproduce
Steps to reproduce the behavior:

Go to Navbar
Click / hover on links
See error

Expected behavior
links must to properly aligned and there can be a better hover animation
Screenshots

Please assign this issue to me, I will contribute to this issue under GSSoC'23.  I will improve the hovering animation and re-align the links with the help of CSS and HTML


SourceTree integration

I'm a fan of SourceTree and I use it everyday. Would it be possible to make the View button open the commit in SourceTree? BitBucket's website is kinda bulky and takes too much time to load.
If you don't use SourceTree I guess I will make a PR, but would love to hear if you would approve such a PR and if there is anything to keep in mind while working on it.

You are very welcome to try to make this work. I am unsure if it possible to open SoruceTree with a specific line and commit open but if it is and it doesn't make the ST process a child of VSCode I am all for it.
It is up to you if you want to make it a config option for commitUrl or its own configuration option.


MSVC ARM/ARM64 Desktop support

[X] documentation is added or updated
[X] tests are added or updated

Regarding CLA, you need to sign one before we can merge your change in.  Have a look here for more information...

I'd suggest (rather insist) that it goes to a separate file in Configurations as community-supported. We don't have hardware and won't test it, so we shouldn't give an impression that it's fully supported. I also wonder what hardware does this target? Windows IoT?

@levitte, we still need the -common thing then in 10-main, in order to allow the -ARM config to be simple.

Please see https://github.com/openssl/openssl/pull/4965#issuecomment-353585104.

Effectively resolved in #5502.


Create open_redirect_magneticmarketing.yml

Description
new coverage for observed open redirect
Associated hunts
If you ran any hunts with your rule, please link them here.

Hunt 1

/update-test-rules

no hits, hunt was also very low volume. marking for review


QA: write and review iota.rs/wallet.rs to iota-sdk migration documentation

Step by step guide on how to transition from the past crates to the SDK.

Any updates on this? I still think we need such a migration guide for the IOTA SDK given that also the Stronghold snapshot format has been changed etc.

We had these two examples for the stronghold/database migration
https://github.com/iotaledger/iota-sdk/blob/develop/bindings/nodejs/examples/wallet/migrate-db-chrysalis-to-stardust.ts
https://github.com/iotaledger/iota-sdk/blob/develop/bindings/nodejs/examples/wallet/migrate-stronghold-snapshot-v2-to-v3.ts


suggestion: new releases?

There have been many changes since last release.
Could you make another release?
Thanks!

hey, I think I'll make a new release once I get the currently open PRs merged, specially https://github.com/marc2332/freya/pull/811, for now you can use it from git. Is there anything specific blocking you?

oh thanks. I will try the git version.


Added HashiCorp Packer variables file

Reasons for making this change:

HashiCorp Packer uses a variables file that acts like secrets file containing variable values.
This file is usually not intended to be version controlled.
Links to documentation supporting these rule changes:
The file naming conventions are documented in the Packer website under:
https://www.packer.io/guides/hcl/variables#from-a-file
Below is excerpt from Packer website:

Given a file named variables.pkrvars.hcl Packer can be instructed to use the variable definitions file by using the -var-file command line flag.
$ packer build -var-file="variables.pkrvars.hcl" .

Packer will automatically load any var file that matches the name *.auto.pkrvars.hcl, without the need to pass the file via the command line. If we rename the above variable definitions file from variables.pkrvars.hcl to variables.auto.pkrvars.hcl, then we can run our build simply by calling
$ packer build .

This is similar in pattern to another HashiCorp product: Terraform
https://github.com/github/gitignore/blob/e89e04390435f1e7628740d7b4ce1fe65ac218fd/Terraform.gitignore#L12-L17

Thanks for the contribution, however per the contribution guidelines this file should be placed in the community folder. Please edit the location of the file.
https://github.com/github/gitignore#specialized-templates


Delay some memory allocation.

If this handler will not handle the request, no need to waste bytes in the request pool.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1829676 13f79535-47bb-0310-9956-ffa450edef68

Merged as 484abff


configure.py reads from stdin if no command line arg provided.

* changed configure.py to the following additional behaviour: if no command
  line argument given, read from stdin, otherwise retain old behaviour
  in treating arg as filename.

Yes, absolutely true, it was a quick hack anyways.  Remedied this nuisance.


Change gesture direction strings in NavigatorSceneConfigs

I see there is a string matching inconsistency in  Libraries/CustomComponents/Navigator/Navigator.js and Libraries/CustomComponents/Navigator/NavigatorSceneConfigs.js, which caused a bug resulting in gestures not working for vertical SceneConfigs. This PR fixes the inconsistency, and the bug.
Motivation for making this change
When working with the navigator, I was using the VerticalUpSwipeJump Navigator SceneConfig. The gesture to pop to the previous scene (in this case jumpBack) was not working.
How I tested?
I changed these strings (as shown in this PR) and swiped down. After these changes, everything worked as expected.
Example
In Libraries/CustomComponents/Navigator/Navigator.js, we check for gesture direction strings bottom-to-top and top-to-bottom in multiple places, but nowhere do we ever check for up-to-down and down-to-up.
var isTravelVertical = gesture.direction === 'top-to-bottom' || gesture.direction === 'bottom-to-top';
var isTravelInverted = gesture.direction === 'right-to-left' || gesture.direction === 'bottom-to-top';

I believe that the TravisCI tests did not fail due to the changes in this PR


Correct for rename of docker config file

Signed-off-by: Shpinkso<EMAIL_ADDRESS>

Looks like I made the same change in my PR, so I'll close this one.


[stable/rocketchat] updating RocketChat version to 3.6.0

Signed-off-by: LuluGO<EMAIL_ADDRESS>What this PR does / why we need it:
Updates Rocket.Chat version
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @geekgonecrazy

/ok-to-test

/approve

/lgtm


WIP: rewrite sensu_check into python

rewrite of the sensu_check ansible library to python.
This was done to get an idea of how much work it would be to rewrite the various libraries that use antsy.
I skipped the env_vars portion because we're not actually using it ( that I can see )   but it wouldn't be hard to add it in.

I just found some checks that use env_vars ...so I'll need to add that in.

:+1:   this is great!

I think this looks good, once you resolve the env_vars stuff. This is something that could also be submitted upstream, but it'd need full documentation first, in the style of the upstream modules. The more we can push out of our tree and into upstream, the better!
Looks like most other people out there use complex data structures and templates to create sensu checks, so this feels a bit better/nicer.

Looks like it still doesn't handle env_vars option passed in. Is that a concern?

:+1: feel free to merge when tests pass.

Uh oh, I might have broken this by merging the other first. Oops.

Merging after rebase.


Terminal window doesn't open at startup

Issue Type: Bug
I changed my Terminal->Integrated: Cwd setting to "$(workspaceFolder)".  Now, when Code starts up, the Terminal does not open, and I get a notification: "The terminal shell CWD "/home/gpudb/gpudb-dev-7.0/gpudb-core/gaiadb-cluster/${workspaceFolder}" does not exist".  This happens every time I launch Code.
However, once Code has loaded, I can then do Ctrl-` to open a Terminal window, and it works as expected (also every time).  Note that this is doing Remote development (so the Terminal is opening a session on my remote machine).
I suspect the issue is that Code is trying to start the Terminal before $workspaceFolder is set, but it is set later, when I manually open the Terminal.  It is a fairly easy work-around, but am reporting it in case this is not the expected behavior.

@Tyriar I would like to take this. Could you please guide me?

@lifez this one will need you to do a bit of debugging/investigation here:
https://github.com/microsoft/vscode/blob/06f94fb46c12fdb4095cf18a4a35068fc8d9e9d8/src/vs/workbench/contrib/terminal/common/terminalEnvironment.ts#L193-L204
I think that if statement is not entered on launch because configurationResolverService is undefined.

@Tyriar Thank you!! I would like to take this one

@Tyriar I cannot start the code. Could you please help me please?
➜  scripts git:(fix-terminal-startup) ./code.sh
yarn run v1.17.0
$ node build/lib/electron
✨  Done in 1.19s.
[07:16:02] Syncronizing built-in extensions...
[07:16:02] You can manage built-in extensions with the --builtin flag
[07:16:02] [marketplace]<EMAIL_ADDRESS>✔
[07:16:02] [marketplace]<EMAIL_ADDRESS>✔
[07:16:02] [marketplace]<EMAIL_ADDRESS>✔
Error: The module '/Users/phawin/mine/vscode/node_modules/spdlog/build/Release/spdlog.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func (electron/js2c/asar.js:138:31)
    at process.func [as dlopen] (electron/js2c/asar.js:138:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
    at Object.func (electron/js2c/asar.js:138:31)
    at Object.func [as .node] (electron/js2c/asar.js:138:31)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at bindings (/Users/phawin/mine/vscode/node_modules/spdlog/node_modules/bindings/bindings.js:112:48)
    at Object.<anonymous> (/Users/phawin/mine/vscode/node_modules/spdlog/index.js:3:35)
    at Module._compile (internal/modules/cjs/loader.js:786:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:798:10)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at NodeScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:747:39)
    at OnlyOnceScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:585:32)
    at loadNextPath (/Users/phawin/mine/vscode/out/vs/loader.js:1523:41)
    at Object.errorback (/Users/phawin/mine/vscode/out/vs/loader.js:1531:25)
    at OnlyOnceScriptLoader.triggerErrorback (/Users/phawin/mine/vscode/out/vs/loader.js:598:36)
    at /Users/phawin/mine/vscode/out/vs/loader.js:585:151
    at ReadFileContext.callback (/Users/phawin/mine/vscode/out/vs/loader.js:764:25)
    at FSReqCallback.readFileAfterOpen [as oncomplete] (fs.js:246:13) {
  phase: 'loading',
  moduleId: 'spdlog',
  neededBy: [ '===anonymous2===' ]
}
[main 2019-10-18T00:16:03.374Z] update#ctor - updates are disabled as there is no update URL
[main 2019-10-18T00:16:03.590Z] [storage state.vscdb] open(): Unable to open DB due to Error: The module '/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/build/Release/sqlite.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
[main 2019-10-18T00:16:03.609Z] [storage state.vscdb] open(): Unable to use backup due to Error: ENOENT: no such file or directory, unlink '/Users/phawin/Library/Application Support/code-oss-dev/User/globalStorage/state.vscdb'
[main 2019-10-18T00:16:03.610Z] [uncaught exception in main]: Error: The module '/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/build/Release/sqlite.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
[main 2019-10-18T00:16:03.610Z] Error: The module '/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/build/Release/sqlite.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func (electron/js2c/asar.js:138:31)
    at process.func [as dlopen] (electron/js2c/asar.js:138:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
    at Object.func (electron/js2c/asar.js:138:31)
    at Object.func [as .node] (electron/js2c/asar.js:138:31)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at Object.<anonymous> (/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/lib/sqlite3.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:786:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:798:10)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at NodeScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:747:39)
    at OnlyOnceScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:585:32)
    at loadNextPath (/Users/phawin/mine/vscode/out/vs/loader.js:1523:41)
    at Object.errorback (/Users/phawin/mine/vscode/out/vs/loader.js:1531:25)
    at OnlyOnceScriptLoader.triggerErrorback (/Users/phawin/mine/vscode/out/vs/loader.js:598:36)
    at /Users/phawin/mine/vscode/out/vs/loader.js:585:151
    at ReadFileContext.callback (/Users/phawin/mine/vscode/out/vs/loader.js:764:25)
    at FSReqCallback.readFileAfterOpen [as oncomplete] (fs.js:246:13)
[main 2019-10-18T00:16:03.610Z] Error: The module '/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/build/Release/sqlite.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func (electron/js2c/asar.js:138:31)
    at process.func [as dlopen] (electron/js2c/asar.js:138:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
    at Object.func (electron/js2c/asar.js:138:31)
    at Object.func [as .node] (electron/js2c/asar.js:138:31)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at Object.<anonymous> (/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/lib/sqlite3.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:786:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:798:10)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at NodeScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:747:39)
    at OnlyOnceScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:585:32)
    at loadNextPath (/Users/phawin/mine/vscode/out/vs/loader.js:1523:41)
    at Object.errorback (/Users/phawin/mine/vscode/out/vs/loader.js:1531:25)
    at OnlyOnceScriptLoader.triggerErrorback (/Users/phawin/mine/vscode/out/vs/loader.js:598:36)
    at /Users/phawin/mine/vscode/out/vs/loader.js:585:151
    at ReadFileContext.callback (/Users/phawin/mine/vscode/out/vs/loader.js:764:25)
    at FSReqCallback.readFileAfterOpen [as oncomplete] (fs.js:246:13) {
  phase: 'loading',
  moduleId: 'vscode-sqlite3',
  neededBy: [ '===anonymous3===' ]
}
[main 2019-10-18T00:16:03.711Z] [uncaught exception in main]: Error: The module '/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/build/Release/sqlite.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
[main 2019-10-18T00:16:03.712Z] Error: The module '/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/build/Release/sqlite.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func (electron/js2c/asar.js:138:31)
    at process.func [as dlopen] (electron/js2c/asar.js:138:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
    at Object.func (electron/js2c/asar.js:138:31)
    at Object.func [as .node] (electron/js2c/asar.js:138:31)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at Object.<anonymous> (/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/lib/sqlite3.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:786:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:798:10)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at NodeScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:747:39)
    at OnlyOnceScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:585:32)
    at loadNextPath (/Users/phawin/mine/vscode/out/vs/loader.js:1523:41)
    at Object.errorback (/Users/phawin/mine/vscode/out/vs/loader.js:1531:25)
    at OnlyOnceScriptLoader.triggerErrorback (/Users/phawin/mine/vscode/out/vs/loader.js:598:36)
    at /Users/phawin/mine/vscode/out/vs/loader.js:585:151
    at ReadFileContext.callback (/Users/phawin/mine/vscode/out/vs/loader.js:764:25)
    at FSReqCallback.readFileAfterOpen [as oncomplete] (fs.js:246:13)
[8392:1018/071606.782439:INFO:CONSOLE(17)] "Error: The module '/Users/phawin/mine/vscode/node_modules/spdlog/build/Release/spdlog.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).", source: file:///Users/phawin/mine/vscode/out/vs/platform/log/node/spdlogService.js (17)
[8392:1018/071606.793418:INFO:CONSOLE(17)] "Error: The module '/Users/phawin/mine/vscode/node_modules/spdlog/build/Release/spdlog.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).", source: file:///Users/phawin/mine/vscode/out/vs/platform/log/node/spdlogService.js (17)
[8392:1018/071606.793480:INFO:CONSOLE(17)] "Error: The module '/Users/phawin/mine/vscode/node_modules/spdlog/build/Release/spdlog.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).", source: file:///Users/phawin/mine/vscode/out/vs/platform/log/node/spdlogService.js (17)
[8392:1018/071606.801727:INFO:CONSOLE(138)] "Uncaught (in promise) Error: Module did not self-register.", source: electron/js2c/asar.js (138)
[8392:1018/071606.811598:INFO:CONSOLE(99)] "Uncaught (in promise) Canceled: Canceled", source: file:///Users/phawin/mine/vscode/out/vs/base/common/errors.js (99)
[main 2019-10-18T00:21:34.614Z] Error: The module '/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/build/Release/sqlite.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 69. This version of Node.js requires
NODE_MODULE_VERSION 73. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func (electron/js2c/asar.js:138:31)
    at process.func [as dlopen] (electron/js2c/asar.js:138:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
    at Object.func (electron/js2c/asar.js:138:31)
    at Object.func [as .node] (electron/js2c/asar.js:138:31)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at Object.<anonymous> (/Users/phawin/mine/vscode/node_modules/vscode-sqlite3/lib/sqlite3.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:786:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:798:10)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at NodeScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:747:39)
    at OnlyOnceScriptLoader.load (/Users/phawin/mine/vscode/out/vs/loader.js:585:32)
    at loadNextPath (/Users/phawin/mine/vscode/out/vs/loader.js:1523:41)
    at Object.errorback (/Users/phawin/mine/vscode/out/vs/loader.js:1531:25)
    at OnlyOnceScriptLoader.triggerErrorback (/Users/phawin/mine/vscode/out/vs/loader.js:598:36)
    at /Users/phawin/mine/vscode/out/vs/loader.js:585:151
    at ReadFileContext.callback (/Users/phawin/mine/vscode/out/vs/loader.js:764:25)
    at FSReqCallback.readFileAfterOpen [as oncomplete] (fs.js:246:13) {
  phase: 'loading',
  moduleId: 'vscode-sqlite3',
  neededBy: [ '===anonymous3===' ]
}

@lifez that means the node modules are using a different version of Electron that what's running, we recently changed the version fo Electron from 6->4->6. You should

Sync your branch with upstream
git clean -xfd (this will blow away all changes, commit or stash first if you need them)
yarn

I cannot make this work. I think it because Catalina https://github.com/nodejs/node-gyp/issues/1927
So that I won't work on this issue.

I cannot dupliacte this on Windows 10. Maybe this thread should be closed.

I am also getting the similar error

Error: The module '\?\D:\Projects\code-server\build\lib\vscode\node_modules\spdlog\build\Release\spdlog.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 75. This version of Node.js requires
NODE_MODULE_VERSION 72. Please try re-compiling or re-installing

@JoyceBabu try recompiling as in https://github.com/microsoft/vscode/issues/81231#issuecomment-543799165, we change the Electron version sometimes which means all native node modules will stop working until you do that.

@Tyriar I wouldn't mind taking a shot at this, but just want to confirm that I've understood the bug properly. If I set my Terminal -> Integrated Cwd setting to ${workspaceFolder}, my terminal never loads and always throws an error, not only on launch, but it sounds like the issue being reported is exclusive to launch/startup. Let me know if I'm misunderstanding.

Minor correction: ”not only on launch" – remove the “not”.  The issue I saw was only a problem when the Terminal was opening on Launch.  But once Code and completed launching, I was able to successfully open a terminal with the setting.
I haven’t tried this recently, since I changed my setting to work-around this issue.  If you are unable to repro, I can try again with the latest build.
From: Daniel Davis<EMAIL_ADDRESS>Sent: Tuesday, June 16, 2020 4:19 PM
To: microsoft/vscode<EMAIL_ADDRESS>Cc: Andy Jacobs<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/vscode] Terminal window doesn't open at startup (#81231)
@Tyriar https://github.com/Tyriar  I wouldn't mind taking a shot at this, but just want to confirm that I've understood the bug properly. If I set my Terminal -> Integrated Cwd setting to ${workspaceFolder}, my terminal never loads and always throws an error, not only on launch, but it sounds like the issue being reported is exclusive to launch/startup. Let me know if I'm misunderstanding.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/81231#issuecomment-644990200 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYOGSWTFHYEAYVLFPZ6KE3RW7HTJANCNFSM4IYXM37A .  https://github.com/notifications/beacon/ABYOGSQDZYXLJDPWGLYPOSDRW7HTJA5CNFSM4IYXM37KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZY4J6A.gif

@andyj513 I suspect this is still happening.


Add sembast to CLI

See folder structure design doc for placement of db (coming soon)

Yo gimme write access and assign me here

@DrCheddar No write access, pull request

I take that back


LightCycleSupportFragment examples

I believe that examples are not correct, because LightCycleSupportFragment only accepts fragment and not interfaces.
I'm having trouble integrating this with my application, because extending my fragment  LightCycleSupportFragment I keep having:
   java.lang.RuntimeException: Unable to start activity      java.lang.NullPointerException: Attempt to invoke interface method 'void com.soundcloud.lightcycle.SupportFragmentLightCycle.onAttach(android.support.v4.app.Fragment, android.app.Activity)' on a null object reference
I'm actually trying to use this with Dagger2 but until now without success:
public class MyFragment extends LightCycleSupportFragment<MyFragment> implements IMyFragmentView{

   @Inject
    @LightCycle
    public DialogManager mDialogManager;

public static Fragment newInstance() {
        return new MyFragment();
    }

 @Nullable
    @Override
    public View onCreateView(LayoutInflater inflater, @Nullable ViewGroup container, @Nullable Bundle savedInstanceState) {
        injectFragment(getContext());
        View view = inflater.inflate(R.layout.mylayout, container, false);
        ButterKnife.bind(this, view);

        setUIComponents();
        return view;
    }

    private void injectFragment(Context context) {
        MyFragmentComponent myComponent = DaggerMyFragmentComponent.builder()
                .fragmentModule(new FragmentModule())
                .build();
        myComponent.inject(context);
    }
}

DialogManager Implementation:
public class DialogManager extends DefaultSupportFragmentLightCycle{
  @Inject
    public DialogManager() {
    }
}

You should pass IMyFragmentView as parameter to LightCycleSupportFragment rather than MyFragment.
Your code should look like this
public class MyFragment extends LightCycleSupportFragment<IMyFragmentView> implements IMyFragmentView
This is the same as the sample
public class LicenseFragment extends LightCycleSupportFragment<LicenseView> implements LicenseView
Hope this can solve your problem!

Isn't LightCycleSupportFragment supporting only  type?
How would he accept an Interface. or is something here that I'm not understanding?

Sorry my bad, I thought this PR (https://github.com/soundcloud/lightcycle/pull/87) already released!
So before https://github.com/soundcloud/lightcycle/pull/87 it used to be like what you said (only accepting ) but after that PR we will support any HostType.
After looking again at your code, looks like the cause of the error is because you are injecting from onCreateView, and onAttach() is called before onCreateView(), and at that time your lightcycle (mDialogManager) is still null because it haven't been injected. I think you can inject the dependencies from the parent Activity or Fragment Constructor.
Hope this can solve your problem!

Actually, I thought it has been released too 😁

Luis, there is a pre-release if you want: 1.6.0.
I am going to test it a little more in the SoundCloud app but it should be
good to go
On Wed, Jan 18, 2017 at 1:04 PM, Luis Pereira<EMAIL_ADDRESS>wrote:

Closed #91 https://github.com/soundcloud/lightcycle/issues/91.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/soundcloud/lightcycle/issues/91#event-927350532, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAhkcQcakw91DPMsFSfcXcifpNvlsyWRks5rTf_PgaJpZM4Lg95K
.

--
Guillaume Lung
Engineer
SoundCloud Ltd. | Rheinsberger Str. 76/77, 10115 Berlin, Germany
Capture and share your music & audio on SoundCloud
http://soundcloud.com/creators


Submission_Group76_2352256_2352065_2352504_2252600_2350034

Member list:
2352256- Trần Võ Hải Đăng(Leader)
2352065- Trần Đức Anh
2352504- Trần Liên Khang
2252600- Lê Tiến Phát
2350034- Nguyễn Tôn Vĩnh
1)Greedy Algorithm
a) Strengths:
Fast and Simple: Quick execution and easy to implement, making decisions step-by-step without backtracking.
Easy to Understand: Suitable for real-world problems with straightforward logic.
b) Weaknesses:
Not Optimal: It does not guarantee the best solution as it focuses only on local choices.
Lacks Global Optimization: Independent decisions at each step can result in suboptimal outcomes.
No Exact Solution Guarantee: In complex problems, it may fail to find the optimal solution.
c) Result

2) Branch and Bound (B&B)
a) Strengths:
Optimal Solution: Ensures finding the best solution.
Pruning Capability: Reduces the search space using pruning techniques, saving time and resources.
Flexible: Can handle a variety of combinatorial optimization problems.
b)Weaknesses:
High Computational Cost: Time-consuming and memory-intensive for large problems.
Complex Implementation: Requires advanced knowledge and is harder to design.
Not Always Faster: May not outperform simpler algorithms, like Greedy, for smaller problems.
c) Result:

Conclusion:
Greedy is faster, simpler, and suitable for smaller or time-sensitive problems but lacks optimality.
Branch and Bound guarantees the best solution but is computationally expensive and complex for large problems.
Our policy uses Greedy algorithm and Branch and Bound to test valuation.

Please revise the PR in Dec 16. Otherwise, your group will get 0 score for code.


Kubernetes version is not preserved when cluster is restored from a snapshots taken before kubernetes version is upgraded.

Currently kubernetes version is not preserved when cluster is restored from a snapshots taken before kubernetes version is upgraded.
Consider the following scenario:
Create a cluster with K8s version say 1.13.
Deploy few workloads.
Take a snapshot , say S1.
Deploy few more workloads.
Upgrade K8s version on the cluster to say 1.14.
Restore from snapshot S1 which was taken when K8s version was in 1.13.
K8s version continue to be in 1.14.
Expected Behavior:
We should be able to get to K8s version 1.13 in this case , the k8s version that was present on the cluster when the snapshot was taken.

As we don't support rolling back k8s version for RKE clusters, we should prevent this from happening during restoration from the snapshot. Can be achieved via:

Store k8s version on the snapshot
Do an api validation when restoring

This looks closely related to an RFE I filed few days back. See https://github.com/rancher/rancher/issues/22232

In 2.4, we introduced being able to restoreand specify/change k8s version on restore. https://github.com/rancher/rancher/issues/22232

In 2.4, we introduced being able to restoreand specify/change k8s version on restore. https://github.com/rancher/rancher/issues/22232