Please update docs on potentia issues

I'm not sure how to interpret below message. After I followed all steps in the documentation and ran webpack on dev configuration, I get below error, what does it mean?  I did not setup a webpack-dev-server.
[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)
[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)
[webpack-isomorphic-tools] (waiting for the first Webpack build to finish)

So, are you running Webpack in parallel? (or before)

I have updated the docs:
### Infinite "(waiting for the first Webpack build to finish)"

If you're getting this message infinitely then it means that `webpack-assets.json` is never generated by Webpack.

It can happen, for example, in any of these cases

  * you forgot to add `webpack-isomorphic-tools` plugin to your Webpack configuration
  * you aren't running your Webpack build either in parallel with your app or prior to running you app
  * you're using `webpack-dev-middleware` inside your main server code [which you shouldn't](https://github.com/halt-hammerzeit/webpack-isomorphic-tools/issues/47)
  * Webpack build is taking forever to complete due to misconfiguration
  * ...

@halt-hammerzeit Appreciate prompt response.

I've added webpack-isomorphic-tools plugin to me webpack dev configuration in (projectRoot/webpack directory).

var path = require('path');
var webpack = require('webpack');
var bourbon = require('node-bourbon');

var WebpackIsomorphicToolsPlugin = require('webpack-isomorphic-tools/plugin')
var webpackIsomorphicToolsPlugin = new WebpackIsomorphicToolsPlugin(require('./isomorphic.config'))
var ExtractTextPlugin = require('extract-text-webpack-plugin');

var sassLoaders = [
    'css-loader?sourceMap',
    'sass-loader?includePaths[]=' + bourbon.includePaths
];

module.exports = {
  devtool: 'cheap-source-map',
  context: __dirname,
  entry: '../lib/client/index.js',
  output: {
    path: path.resolve(__dirname),
    filename: 'app.js',
    publicPath: '/build/'
  },
  sasslint: {
    configFile: '../.sass-lint.yml'
  },
  module: {
    preLoaders: [{
        test: /\.scss$/,
        loader: 'sasslint',
        exclude: /node_modules/
    }],
    loaders: [{
      test: /\.(js|jsx)$/,
      loader: 'babel',
      query: {
        presets: ['react', 'es2015', 'stage-0']
      },
      exclude: /node_modules/
    }, {
      test: /\.(sass|scss)$/,
      loader: sassLoaders.join('!'),
      exclude: /node_modules/
    },
    { test: /\.woff(\?v=\d+\.\d+\.\d+)?$/, loader: "url?limit=10000&mimetype=application/font-woff" },
    { test: /\.woff2(\?v=\d+\.\d+\.\d+)?$/, loader: "url?limit=10000&mimetype=application/font-woff" },
    { test: /\.ttf(\?v=\d+\.\d+\.\d+)?$/, loader: "url?limit=10000&mimetype=application/octet-stream" },
    { test: /\.eot(\?v=\d+\.\d+\.\d+)?$/, loader: "file" },
    { test: /\.svg(\?v=\d+\.\d+\.\d+)?$/, loader: "url?limit=10000&mimetype=image/svg+xml" },
    { test: webpackIsomorphicToolsPlugin.regular_expression('images'), loader: 'url-loader?limit=10240' }
    ]
  },
  plugins: [
    new webpack.DefinePlugin({
      __CLIENT__: true,
      __SERVER__: false,
      __DEVELOPMENT__: true,
      __DEVTOOLS__: true  //  <<<--- DISABLE redux-devtools HERE...
    }),
    webpackIsomorphicToolsPlugin
    //  webpackIsomorphicToolsPlugin.development()
    // also enter development mode since it's a development webpack configuration
    // when in development mode, it disables asset caching (and enables asset hot reload).
    // Just call it if you're developing your project with webpack-dev-server using this config
    // don't call it for your production webpack build
    // .development();
  ]
};

I'm running Webpack build before running the app
I'm not using webpack-dev-middleware inside main server code
Misconfiguration... here's my isomorphic configuration...

var WebpackIsomorphicToolsPlugin = require('webpack-isomorphic-tools/plugin');

// see this link for more info on what all of this means
// https://github.com/halt-hammerzeit/webpack-isomorphic-tools
module.exports = {

  // when adding "js" extension to asset types
  // and then enabling debug mode, it may cause a weird error:
  //
  // [0] npm run start-prod exited with code 1
  // Sending SIGTERM to other processes..
  //
  // debug: true,

  assets: {
    images: {
      extensions: ['jpeg', 'jpg', 'png', 'gif'],
      parser: WebpackIsomorphicToolsPlugin.url_loader_parser
    },
    fonts: {
      extensions: ['woff', 'woff2', 'ttf', 'eot'],
      parser: WebpackIsomorphicToolsPlugin.url_loader_parser
    },
    svg: {
      extension: 'svg',
      parser: WebpackIsomorphicToolsPlugin.url_loader_parser
    },
    style_modules: {
      extensions: ['css', 'scss'],
      filter: function(module, regex, options, log) {
        if (options.development) {
          // in development mode there's webpack "style-loader",
          // so the module.name is not equal to module.name
          return WebpackIsomorphicToolsPlugin.style_loader_filter(module, regex, options, log);
        } else {
          // in production mode there's no webpack "style-loader",
          // so the module.name will be equal to the asset path
          return regex.test(module.name);
        }
      },
      path: function(module, options, log) {
        if (options.development) {
          // in development mode there's webpack "style-loader",
          // so the module.name is not equal to module.name
          return WebpackIsomorphicToolsPlugin.style_loader_path_extractor(module, options, log);
        } else {
          // in production mode there's no webpack "style-loader",
          // so the module.name will be equal to the asset path
          return module.name;
        }
      },
      parser: function(module, options, log) {
        if (options.development) {
          return WebpackIsomorphicToolsPlugin.css_modules_loader_parser(module, options, log);
        } else {
          // in production mode there's Extract Text Loader which extracts CSS text away
          return module.source;
        }
      }
    }
  }
}

It's generating webpack-assets.json in the /projectRoot/webpack directory, which isomorphic-tools plugin is unable to find for some reason. There's something I'm missing in the webpack dev configuration (above) which tells isomorphic plugin to find the webpack-assets.json.

Hmm, if webpack-assets are generated then it should work.
You may upload your project to github and i may try to run it
On Sunday, February 14, 2016, Chandra Veera<EMAIL_ADDRESS>wrote:

@halt-hammerzeit https://github.com/halt-hammerzeit Appreciate prompt
response.

I've added webpack-isomorphic-tools plugin to me webpack dev
configuration in (projectRoot/webpack directory).

var path = require('path');
var webpack = require('webpack');
var bourbon = require('node-bourbon');
var WebpackIsomorphicToolsPlugin = require('webpack-isomorphic-tools/plugin')
var webpackIsomorphicToolsPlugin = new WebpackIsomorphicToolsPlugin(require('./isomorphic.config'))
var ExtractTextPlugin = require('extract-text-webpack-plugin');
var sassLoaders = [
'css-loader?sourceMap',
'sass-loader?includePaths[]=' + bourbon.includePaths
];
module.exports = {
devtool: 'cheap-source-map',
context: __dirname,
entry: '../lib/client/index.js',
output: {
path: path.resolve(__dirname),
filename: 'app.js',
publicPath: '/build/'
},
sasslint: {
configFile: '../.sass-lint.yml'
},
module: {
preLoaders: [{
test: /.scss$/,
loader: 'sasslint',
exclude: /node_modules/
}],
loaders: [{
test: /.(js|jsx)$/,
loader: 'babel',
query: {
presets: ['react', 'es2015', 'stage-0']
},
exclude: /node_modules/
}, {
test: /.(sass|scss)$/,
loader: sassLoaders.join('!'),
exclude: /node_modules/
},
{ test: /.woff(?v=\d+.\d+.\d+)?$/, loader: "url?limit=10000&mimetype=application/font-woff" },
{ test: /.woff2(?v=\d+.\d+.\d+)?$/, loader: "url?limit=10000&mimetype=application/font-woff" },
{ test: /.ttf(?v=\d+.\d+.\d+)?$/, loader: "url?limit=10000&mimetype=application/octet-stream" },
{ test: /.eot(?v=\d+.\d+.\d+)?$/, loader: "file" },
{ test: /.svg(?v=\d+.\d+.\d+)?$/, loader: "url?limit=10000&mimetype=image/svg+xml" },
{ test: webpackIsomorphicToolsPlugin.regular_expression('images'), loader: 'url-loader?limit=10240' }
]
},
plugins: [
new webpack.DefinePlugin({
CLIENT: true,
SERVER: false,
DEVELOPMENT: true,
DEVTOOLS: true  //  <<<--- DISABLE redux-devtools HERE...
}),
webpackIsomorphicToolsPlugin
//  webpackIsomorphicToolsPlugin.development()
// also enter development mode since it's a development webpack configuration
// when in development mode, it disables asset caching (and enables asset hot reload).
// Just call it if you're developing your project with webpack-dev-server using this config
// don't call it for your production webpack build
// .development();
]
};

I'm running Webpack build before running the app
I'm not using webpack-dev-middleware inside main server code
Misconfiguration... here's my isomorphic configuration...

var WebpackIsomorphicToolsPlugin = require('webpack-isomorphic-tools/plugin');
// see this link for more info on what all of this means
// https://github.com/halt-hammerzeit/webpack-isomorphic-tools
module.exports = {
// when adding "js" extension to asset types
// and then enabling debug mode, it may cause a weird error:
//
// [0] npm run start-prod exited with code 1
// Sending SIGTERM to other processes..
//
// debug: true,
assets: {
images: {
extensions: ['jpeg', 'jpg', 'png', 'gif'],
parser: WebpackIsomorphicToolsPlugin.url_loader_parser
},
fonts: {
extensions: ['woff', 'woff2', 'ttf', 'eot'],
parser: WebpackIsomorphicToolsPlugin.url_loader_parser
},
svg: {
extension: 'svg',
parser: WebpackIsomorphicToolsPlugin.url_loader_parser
},
style_modules: {
extensions: ['css', 'scss'],
filter: function(module, regex, options, log) {
if (options.development) {
// in development mode there's webpack "style-loader",
// so the module.name is not equal to module.name
return WebpackIsomorphicToolsPlugin.style_loader_filter(module, regex, options, log);
} else {
// in production mode there's no webpack "style-loader",
// so the module.name will be equal to the asset path
return regex.test(module.name);
}
},
path: function(module, options, log) {
if (options.development) {
// in development mode there's webpack "style-loader",
// so the module.name is not equal to module.name
return WebpackIsomorphicToolsPlugin.style_loader_path_extractor(module, options, log);
} else {
// in production mode there's no webpack "style-loader",
// so the module.name will be equal to the asset path
return module.name;
}
},
parser: function(module, options, log) {
if (options.development) {
return WebpackIsomorphicToolsPlugin.css_modules_loader_parser(module, options, log);
} else {
// in production mode there's Extract Text Loader which extracts CSS text away
return module.source;
}
}
}
}
}
It's generating webpack-assets.json in the /projectRoot/webpack directory,
which isomorphic-tools plugin is unable to find for some reason. There's
something I'm missing in the webpack dev configuration (above) which tells
isomorphic plugin to find the webpack-assets.json.
—
Reply to this email directly or view it on GitHub
https://github.com/halt-hammerzeit/webpack-isomorphic-tools/issues/49#issuecomment-183895335
.

Ok great will do, thanks for help @halt-hammerzeit

@halt-hammerzeit here's the repo. It's generating assets.json in the webpack directory where the isomorphic tools plugin is unable to find.
npm install && npm run dev
https://github.com/veeracs/isomorphic-tools-seed.git

Fixed
https://github.com/veeracs/isomorphic-tools-seed/pull/1

FYI
I'm posting this in every issue and PR to notify whoever may be interested:
today I've released an alternative helper library called universal-webpack.
It takes a different approach than webpack-ismorphic-tools and instead of hacking Node.js require() calls it just compiles all code with target: 'node' webpack configuration option.
As a result, all Webpack plugins and features are supported.
If you think you might need that here's an example project:
https://github.com/halt-hammerzeit/webpack-react-redux-isomorphic-render-example

Awesome @halt-hammerzeit! Thank you for letting me know.


Not an issue, just sharing a great base class for Redux and Immutable.js

not an issue, more of a discussion...
so I was shopping around looking for the best way to support Immutable.js with redux.
I ended up coming up with a solution which works really nice, it gives you the full support of Typescript's typing and it allows you to inject any class instance into redux so you have full typing support around your redux functions.
import {Map} from 'immutable';
import { UUID } from 'angular2-uuid';

/**
 * StoreModel is a thin wrapper of Immutable data around for a Class
 * uses the internal immutable map to hold all values.
 * This allows us a base class on which we can extend and inject
 * into any Redux store as we follow Immutability
 *
 * Also ships with a helper static method to create unique IDs
 **/
export class StoreModel {

    static UniqueId(){
        return UUID.UUID();
    }

    constructor(data:any = {}) {
        this._data = Map<string, any>(data);
    }

    _data:Map<string, any>;

    public setKey<T>(ClassName:any, key:string, value:any):T {
        return this.setData(ClassName, this._data.set(key, value)) as T;
    }

    public getKey(key:string) {
        return this._data.get(key);
    }

    public setData<T>(ClassName, data:any):T {
        function ClassFactory(className:{new(data): T;}, data:any):T {
            var created:T = new className(Map<string, any>(data));
            return created;
        }

        return ClassFactory(ClassName, data);
    }

    public getData():Map<string, any> {
        return this._data;
    }

}

and so you can simply extend the base such as a Todo:
export class TodoModel extends StoreModel {

    constructor(data:any = {}) {
        super(data);
    }

    invalidateTodoId(i_id = -1) {
        return this.setKey<TodoModel>(TodoModel, 'modelId', i_id);
    }

}

and insert that todo into redux with all the goodness of typing support
export function todos(state:List<TodoModel> = List<TodoModel>(), action:ITodoAction):List<TodoModel> {

    function indexOf(id:string) {
        return state.findIndex((i:TodoModel) => i.getKey('modelId') === id);
    }

    switch (action.type) {
        case TodoAction.ADD_TODO:
            return state.push(action.todoModel);
        case TodoAction.REMOVE_TODO:
            return List<TodoModel>(state.filter((i:TodoModel) => i.getKey('modelId') !== action.modelId));
        case TodoAction.CLEAR_TODOS:
            return List<TodoModel>();
        case TodoAction.EDIT_TODO:
            return state.update(indexOf(action.modelId), (todoModel:TodoModel) => {
                return todoModel.setKey<TodoModel>(TodoModel, action.key, action.value)
            });
        default:
            return state;
    }
}

and you also get the same typing support on the subscription side:
appStore.subscribe((businesses:List<BusinessModel>)=> {

            function indexOf(businessId:string) {
                return businesses.findIndex((i:BusinessModel) => i.getKey('businessId') === businessId);
            }

            var b:BusinessModel = businesses.get(3);
            var id = b.getKey('businessId');
            var idx:string = indexOf(id);
            console.log(idx);

            // console.log(value);
        }, 'business');

 ...

full source @: https://github.com/born2net/ng2Boilerplate
works GREAT...
Sean

Hi, thank you for sharing. In general we recommend that both actions and the state are plain objects (or something like Immutable Maps) so they are easy to serialize, record and replay, hydrate and dehydrate.

tx, yes I am using a  for my store, but internally using classes.
regards


Update references from main to master

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes: #95, #96
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.
Update references from main to master to run testPublish workflow.
Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

:tada: This PR is included in version 1.2.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Summary Statistics not Working

After a crawl has finished, I don't see the statistics at the bottom of the screen.

Nutch crawls, right?  Is this a dupe of https://github.com/memex-explorer/memex-explorer/issues/732?

Yes, its the same, sorry. Closing.


[Bug]  spark run on k8s Error: Master must start with yarn, spark, mesos, or local

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
准备在ds中运行spark on k8s任务提示  Error: Master must start with yarn, spark, mesos, or local
What you expected to happen
export KUBECONFIG=/tmp/dolphinscheduler/exec/process/default/11930573660864/11985906373952_1/9/9/config
${SPARK_HOME}/bin/spark-submit --master k8s://https://<IP_ADDRESS>:6443/ --deploy-mode cluster --class uml.tech.spark.SparkApp --conf spark.driver.cores=1 --conf spark.driver.memory=512M --conf spark.executor.instances=2 --conf spark.executor.cores=2 --conf spark.executor.memory=2G --name TE --conf spark.kubernetes.driver.label.dolphinscheduler-label=9_9 --conf spark.kubernetes.namespace=spark-job file:/dolphinscheduler/default/resources/spark-job/uml-ne-gblogs-to-tdengine-1.0.0/lib/uml-ne-gblogs-to-tdengine-1.0.0.jar 20220311 200
[INFO] 2023-12-21 11:00:11.546 +0800 - Executing shell command : sudo -u dolphinscheduler -i /tmp/dolphinscheduler/exec/process/default/11930573660864/11985906373952_1/9/9/9_9.sh
[INFO] 2023-12-21 11:00:11.565 +0800 - process start, process id is: 14145
[INFO] 2023-12-21 11:00:12.565 +0800 -  ->
WARNING: User-defined SPARK_HOME (/opt/cloudera/parcels/CDH-5.9.0-1.cdh5.9.0.p0.23/lib/spark) overrides detected (/opt/cloudera/parcels/CDH/lib/spark).
WARNING: Running spark-class from user-defined location.
[INFO] 2023-12-21 11:00:14.567 +0800 -  ->
Error: Master must start with yarn, spark, mesos, or local
Run with --help for usage help or --verbose for debug output
[ERROR] 2023-12-21 11:00:27.571 +0800 - Handle pod log error
java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.RuntimeException: The driver pod does not exist.
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at org.apache.dolphinscheduler.plugin.task.api.AbstractCommandExecutor.run(AbstractCommandExecutor.java:211)
at org.apache.dolphinscheduler.plugin.task.api.AbstractYarnTask.handle(AbstractYarnTask.java:52)
at org.apache.dolphinscheduler.server.worker.runner.DefaultWorkerDelayTaskExecuteRunnable.executeTask(DefaultWorkerDelayTaskExecuteRunnable.java:57)
at org.apache.dolphinscheduler.server.worker.runner.WorkerTaskExecuteRunnable.run(WorkerTaskExecuteRunnable.java:175)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:131)
at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:74)
at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:82)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: The driver pod does not exist.
at org.apache.dolphinscheduler.plugin.task.api.AbstractCommandExecutor.lambda$collectPodLogIfNeeded$0(AbstractCommandExecutor.java:287)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
... 3 common frames omitted
Caused by: java.lang.RuntimeException: The driver pod does not exist.
at org.apache.dolphinscheduler.plugin.task.api.AbstractCommandExecutor.lambda$collectPodLogIfNeeded$0(AbstractCommandExecutor.java:277)
... 7 common frames omitted
[INFO] 2023-12-21 11:00:27.572 +0800 - process has exited. execute path:/tmp/dolphinscheduler/exec/process/default/11930573660864/11985906373952_1/9/9, processId:14145 ,exitStatusCode:1 ,processWaitForStatus:true ,processExitValue:1
[INFO] 2023-12-21 11:00:27.572 +0800 - Start finding appId in /opt/dolphinscheduler/worker-server/logs/20231221/11985906373952/1/9/9.log, fetch way: log
[INFO] 2023-12-21 11:00:27.575 +0800 - ***********************************************************************************************
[INFO] 2023-12-21 11:00:27.575 +0800 - *********************************  Finalize task instance  ************************************
[INFO] 2023-12-21 11:00:27.575 +0800 - ***********************************************************************************************
[INFO] 2023-12-21 11:00:27.578 +0800 - Upload output files: [] successfully
[INFO] 2023-12-21 11:00:27.579 +0800 - Send task execute status: FAILURE to master : <IP_ADDRESS>:1234
[INFO] 2023-12-21 11:00:27.579 +0800 - Remove the current task execute context from worker cache
[INFO] 2023-12-21 11:00:27.579 +0800 - The current execute mode isn't develop mode, will clear the task execute file: /tmp/dolphinscheduler/exec/process/default/11930573660864/11985906373952_1/9/9
[INFO] 2023-12-21 11:00:27.786 +0800 - Success clear the task execute file: /tmp/dolphinscheduler/exec/process/default/11930573660864/11985906373952_1/9/9
[INFO] 2023-12-21 11:00:27.787 +0800 - FINALIZE_SESSION
How to reproduce
添加k8s进群到ds控制台，新建工作流，

Anything else
No response
Version
3.2.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

It seems like your Spark version doesn't support run on K8S.


Updated to indicate Engagement Insights content.

Will work on a few more thing and put all my changes in a single branch to make it easier to manage,

Will work on a few more thing and put all my changes in a single branch to make it easier to manage,


Error in ToggleCommandComponent  -   Property '"toolbarItem"' is incompatible with index signature.     Type '{ alias: "toolbarItem"; required: false; }' is not assignable to type 'string'.

What happened?
Hi Apologies first !
It is my first issue so bear with me .
I installed ngx-editor using npm
and i added imports in my module.ts
on build or ng serve , it gives me following error

Error: node_modules/ngx-editor/lib/modules/menu/toggle-command/toggle-command.component.d.ts:26:97 - error TS2344: Type '{ toolbarItem: { alias: "toolbarItem"; required: false; }; }' does not satisfy the constraint '{ [key: string]: string; }'.
Property '"toolbarItem"' is incompatible with index signature.
Type '{ alias: "toolbarItem"; required: false; }' is not assignable to type 'string'.

26     static ɵcmp: i0.ɵɵComponentDeclaration<ToggleCommandComponent, "ngx-toggle-command", never, { "toolbarItem": { "alias": "toolbarItem"; "required": false; }; }, {}, never, never, false, never>;

× Failed to compile.
I am using following package
"ngx-editor": "^16.0.1",
Version
16.0.1
Angular Version
!5.0.1
What browsers are you seeing the problem on?
Chrome
Link to reproduce
No response
Relevant log output
No response
Willing to submit a PR?
None

Hey Thank you ... i am going to use 15.3.0 till our project move to Angular 16


All endpoints return 400

Describe the bug
Trying unleash-edge out locally (running via docker) and observing 400s on pretty much any type of request I do. The body is empty so this is completely un-actionable.
Trying endpoints like http://localhost:3063/api/proxy/all and including the Authorization header.
Was trying to migrate from unleash-proxy, but missing a concrete migration guide. The edge doesn't seem to be 1:1 compatible with proxy (different API endpoints etc...).
Steps to reproduce the bug
No response
Expected behavior
No response
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
No response
Subscription type
None
Hosting type
None
SDK information (language and version)
No response

Hi @Meemaw
We do need to come up with a migration guide from the proxy, that is on us.
I'm going to try to help you a bit further:
Since you're getting HTTP Status Code 400, I'm guessing you're trying to use old proxy keys to access Edge, and you started edge in Edge mode? When started in Edge mode, you will need to create proper client keys using Unleash's admin panel.
https://docs.getunleash.io/reference/api-tokens-and-client-keys
Edge will return 400 (Bad Data) if it can't parse the token being used in the authorization header following the <project>:<environment>.<secret> format.
If you're using the proxy sdk, you'll need a Frontend token, but you'll also give Edge a client token that is allowed to read the features you're trying to evaluate. See https://docs.getunleash.io/reference/unleash-edge#edge and particularly the paragraph about frontend tokens.

Hi @chriswk thanks for the reply.
Is a migration guide in the works/planned? In that case I would wait for that so I don't have to nag you for any issue we'll hit 🙂

Yes it is in the works. I've added a issue to this repo as well to be more transparent on what we're doing.


Create Docker image for Raspberry Pi

Create a docker image for the raspberry pi. This should include the kafka producer and the code to capture and transmit the images.

This is a link from nVidia to run a camera from the Jetson Nano: https://developer.nvidia.com/embedded/learn/tutorials/first-picture-csi-usb-camera#CameraGuide-Usethecamerawithinacontainer
Here is a link for the container that we used to initialize our container: https://ngc.nvidia.com/catalog/containers/nvidia:l4t-ml/collections


Fixes #3117
Master:

visual.c:28422: Driver string: "nvd3dum.dll"
visual.c:28423: Description string: "NVIDIA GeForce RTX 3090"
visual.c:28426: Device name string: "\.\DISPLAY1"
visual.c:28428: Driver version 32767.65535.65535.65535
visual.c:5709: Test failed: quad 4 has color 00000000, expected 0x0033cc00
visual.c:5375: Test failed: D3DTTFF_COUNT3 | D3DTTFF_PROJECTED (draws non-projected) - top right: pixel (341, 211) has color ff000000, expected ffffffff.
visual.c:5375: Test failed: D3DTTFF_COUNT3 | D3DTTFF_PROJECTED (draws non-projected) - top right: pixel (341, 224) has color ff000000, expected ffffffff.
visual.c:5375: Test failed: D3DTTFF_COUNT3 | D3DTTFF_PROJECTED (draws non-projected) - top right: pixel (359, 211) has color ff000000, expected ffffffff.
visual.c:5375: Test failed: D3DTTFF_COUNT3 | D3DTTFF_PROJECTED (draws non-projected) - top right: pixel (359, 224) has color ff000000, expected ffffffff.
visual.c:5375: Test failed: D3DTTFF_PROJECTED (like COUNT3 | PROJECTED, texcoord has only 3 components) - bottom right: pixel (401, 361) has color ff000000, expected ffffffff.
visual.c:5375: Test failed: D3DTTFF_PROJECTED (like COUNT3 | PROJECTED, texcoord has only 3 components) - bottom right: pixel (401, 419) has color ff000000, expected ffffffff.
visual.c:5375: Test failed: D3DTTFF_PROJECTED (like COUNT3 | PROJECTED, texcoord has only 3 components) - bottom right: pixel (479, 361) has color ff000000, expected ffffffff.
visual.c:5375: Test failed: D3DTTFF_PROJECTED (like COUNT3 | PROJECTED, texcoord has only 3 components) - bottom right: pixel (479, 419) has color ff000000, expected ffffffff.
visual.c:5375: Test failed: D3DTTFF_COUNT1 (draws non-projected) - top right: pixel (341, 209) has color ffffffff, expected ff000000.
visual.c:5375: Test failed: D3DTTFF_COUNT1 (draws non-projected) - top right: pixel (341, 226) has color ffffffff, expected ff000000.
visual.c:5375: Test failed: D3DTTFF_COUNT1 (draws non-projected) - top right: pixel (359, 209) has color ffffffff, expected ff000000.
visual.c:5375: Test failed: D3DTTFF_COUNT1 (draws non-projected) - top right: pixel (359, 226) has color ffffffff, expected ff000000.
visual.c:5979: Test failed: quad 3 has color 00000000, expected 0x000000ff
visual.c:5981: Test failed: quad 4 has color 00000000, expected 0x00ffffff
visual.c:6068: Test failed: quad 3 has color 00ffffff, expected 0x00ff0000
45d4:visual: 460 tests executed (0 marked as todo, 0 as flaky, 16 failures), 0 skipped.

PR:

visual.c:28422: Driver string: "nvd3dum.dll"
visual.c:28423: Description string: "NVIDIA GeForce RTX 3090"
visual.c:28426: Device name string: "\.\DISPLAY1"
visual.c:28428: Driver version 32767.65535.65535.65535
a4d0:visual: 460 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped.

I'd appreciate testing for regressions with:
#3293 (maybe @mrdeathjr28) I still had the Apitrace of Coldfear and that is fine with the PR.
#3628 (@Blisto91) I still had the Project Snowblind Apitrace and that also renders fine with the PR.
and Sims 2 (maybe @tannisroot)

Didn't see any regressions with this build in Sims 2 compared to 2.3.1.

Hello guys, i've tested the latest changes in PSOBB and the texture movement issue is fixed everywhere!!, theres a little detail with the refraction effect used in some monsters and for the splashing effects in water that seems to be a little bit off, not sure if its related to this texture fix but I've attached here a small video showcasing it.
@K0bin @doitsujin Moreover I wanted to mention that at least in the case of PSOBB, this game is actually a DX8 game not a DX9, so to be able to see the improvements i had to use d3d8to9 + your latest d3d9.dll as overrides not sure if that also might affect the outcome either
https://github.com/doitsujin/dxvk/assets/5244595/996ee404-53b8-46f0-9787-4a83c349e195

@nolrinale Can you make an apitrace of the part that's not quite correct now?

https://github.com/doitsujin/dxvk/wiki/Using-Apitrace
@nolrinale

https://github.com/doitsujin/dxvk/wiki/Using-Apitrace
@nolrinale
@K0bin
I'm having troubles setting it up with your fixed d3d9.dll from the artifacts, and is not loading correctly for me. I'm getting the old versionw ithout the fixes instead....

However since you seem to have the game up and running from the previous main issue, create a Episode 2 Party and use the /warp command between areas 6-12 all these areas have water where you can splash around and see the issue

@K0bin I tried again to get you an apitrace of the affected area, but it looks like it wont get me a trace if I load the game with the d3d8to9's d3d8.dll.... and I require it to be able to elevate the game to DX9 to be able to see the fixed changes.
If i load the game with the default d3d8.dll included in the apitrace package it does work and I can get a trace file but then I'm stuck with the old graphic issues, however in this specific case the water ripples and refraction works fine (minus the broken moving textures) so I guess there was a regression somewhere in this PR that affected this functionality.

@nolrinale You don't have to use the latest fixed DXVK version. Apitrace records the D3D9 commands and those should be identical regardless of whether you use a DXVK build with my recent fixes or an older one.

@K0bin oh lol I had no clue about that!! well here you have it
https://drive.google.com/file/d/1UEU3vOvYtv4FbaFd7TFeebuBnnvP2jH8/view?usp=sharing
The recording goes up to a little debug room at the end with lots of water where im walking in circles showing you the effect

Nice job!


InlineVariable Java recipe

Inline variables that are used immediately after in a return.
int test() {
    int n = 0;
    return n;
}

cc / @nmck257


feat(toast): align slots

Describe pull-request

Alignes slot names
Simplifies logic for conditional rendering of slots vs props.

Solving issue
Fixes: https://tegel.atlassian.net/browse/DTS-1952
How to test

Go to storybook
Check in Components -> Toast
Test the controls and check the styles.

Nice. Might be nice if the way the slot is styled is aligned with what you did in banner though.

Agree, will fix

Nice. Might be nice if the way the slot is styled is aligned with what you did in banner though.

Agree, will fix

Hmm actually i think you didnt do that thing, but perhaps you saw something else, great!


JsonInput formatOnBlur is always on

It seems like the formatOnBlur attribute does not change the behavior of the JsonInput field.
This is what I have in my layout:
dmc.JsonInput(
    id="msa-json-config",
    label="MSA Config",
    placeholder="This component will auto-size to fit the content.",
    validationError="Invalid json",
    formatOnBlur=False,
    autosize=True,
    minRows=4,
)

However, each time I exit the JsonInput field, it formats the json text.
A solution for me would be to either be able to overwrite the format function in JS (but I would need a little help as to how), or being able to disable the formatting from the python object
dash_bootstrap_components==1.4.2
dash-extensions==1.0.3
dash-mantine-components==0.12.1
dash-ag-grid==2.3.0

Hi @revmlx
I can confirm the issue you reported when running in dmc 0.12.1, but it appears to be fixed in dmc 0.14.4.
Here is a minimal example using the latest version.
import dash_mantine_components as dmc
from dash import Dash, _dash_renderer, Input, Output, callback, no_update
_dash_renderer._set_react_version("18.2.0")

app = Dash(external_stylesheets=dmc.styles.ALL)

app.layout = dmc.MantineProvider([
    dmc.JsonInput(
        label="Your package.json",
        placeholder="Textarea will autosize to fit the content",
        validationError="Invalid JSON",
        formatOnBlur=False,
        autosize=True,
        minRows=4,
    ),
])

if __name__ == "__main__":
    app.run(debug=True)

I'm going to close this for now since I can't replicate the issue with the current version, but feel free to re-open if you have any other questions on this topic.


Typo in "return value" documentation

"The int difference between the startdate and enddate, expressed in the ->coundary<- set by datepart."
Should be "boundary", not "coundary".

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

ID: 340056a9-0593-4289-7b72-601ae718b05f
Version Independent ID: 1db8e288-8068-be96-b2f2-c8a2fe5a857a
Content: DATEDIFF (Transact-SQL) - SQL Server
Content Source: docs/t-sql/functions/datediff-transact-sql.md
Product: sql
Technology: t-sql
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

THanks for noticing this - we're fixing it in https://github.com/MicrosoftDocs/sql-docs-pr/pull/11115


drivers: clock_control:  stm32f3: Enable PWR clock to access BDCR

BDCR could be required for LSE or RTC for instance. Enable it here as for now, no sophisticated PM handling is available on F3 series.
Fixes #56449

Please, Fix typo (comment, title) as the register is named BDCR for Domain Control Register

Fixed, txs

@erwango Seems stm32f0 have same problem. Could you fix f0 too?


Error handlers

Added the onPublisherInitError and onPublishError as props
for . These wil be triggered when the publisher
fails to initiate and when the publisher fails to publish
repectively

Added the onSessionConnectError property for the createSession
helper. Will be triggered is session.connect fails

@aiham - as we discussed in #7, this is just from the top of my mind. Let me know what you think and if that is the direction in which you were thinking!

Awesome thanks. Let me think about this a bit.


Event data not decoded anymore

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (e85435a 2022-04-14T00:06:25.800261822+00:00)
What command(s) is the bug in?
forge test
Operating System
Linux
Describe the bug
When I run forge test -vvvv, the event data used to be decoded and shown nicely, like in https://github.com/leonardoalt/dl_symb_exec_sol
[687208634] SymbExecTest::test_symb_run_unreachable()
    ├─ emit UnreachableBranch(pc: 382)
    ├─ emit UnreachableBranch(pc: 425)
    ├─ emit UnreachableBranch(pc: 468)
    ├─ emit UnreachableBranch(pc: 550)
    └─ ← ()

The same command on the same repo now gives me (with solc 0.8.10):
[644522094] SymbExecTest::test_symb_run_unreachable()
    ├─  emit topic 0: 0xd53db689eb18f6139abb6f9e12451eb80c57984e8130bb07952e69ec5dc5f0da
    │           data: 0x000000000000000000000000000000000000000000000000000000000000017e
    ├─  emit topic 0: 0xd53db689eb18f6139abb6f9e12451eb80c57984e8130bb07952e69ec5dc5f0da
    │           data: 0x00000000000000000000000000000000000000000000000000000000000001a9
    ├─  emit topic 0: 0xd53db689eb18f6139abb6f9e12451eb80c57984e8130bb07952e69ec5dc5f0da
    │           data: 0x00000000000000000000000000000000000000000000000000000000000001d4
    ├─  emit topic 0: 0xd53db689eb18f6139abb6f9e12451eb80c57984e8130bb07952e69ec5dc5f0da
    │           data: 0x0000000000000000000000000000000000000000000000000000000000000226
    └─ ← ()

Any idea what caused the change?
To reproduce: clone the repo and run forge test --match symb_run -vvvv.

@onbjerg I just debugged this a bit, it seems like the event UnreachableBranch is not included in the event set of the CallTraceEncoder.
the event is defined outside of the test, in a separate library which probably caused this? not sure yet where we populate the event set

We should get the deployment traces for the libraries here:
https://github.com/foundry-rs/foundry/blob/64cbc981c358fee7d52b51172a07cc31af20bfd5/forge/src/runner.rs#L214-L226
Then when we do the identify step this is called by the decoder in the test command:
https://github.com/foundry-rs/foundry/blob/64cbc981c358fee7d52b51172a07cc31af20bfd5/evm/src/trace/identifier/local.rs#L27-L48
And that should add the event

it's definitely not included in the set in this case.

I also tested this separately in a fresh repo, and if an event was defined inside a contract, the data would be decoded. If the event was in a library, not decoded. I thought then that this had to do with solc not exporting the events of a library, but then I remembered that it did use to work in this repo, and I haven't changed the repo.

@mattsse My best guess is that it's the bytecode matching, similar to the other issue :/

perhaps it has something to do with the fact that the lib is merely a container for the event,
library SymbExec {
	event UnreachableBranch(uint pc);
}

@mattsse Ah, right. So no runtime bytecode and we hit
https://github.com/foundry-rs/foundry/blob/64cbc981c358fee7d52b51172a07cc31af20bfd5/evm/src/trace/identifier/local.rs#L55-L58

happens here
https://github.com/foundry-rs/foundry/blob/ad86fae33857f489823cbafd5767b649b3bf6db8/evm/src/trace/decoder.rs#L242
and the event in question is not included in the set

Yeah, but what I mean is: runtime bytecode of the library is 0, so when the local identifier tries to identify the contract, it says there are no matches since a runtime bytecode of 0 could mean anything. You could have multiple contracts that are just empty containers, so we can't really make a good guess

what if we gather all events of the output?

Yeah that's what I mean, sorry if I wasn't clear 😅


Adjust keywait for numpad wait/enter and shortcut key

Summary

Adjusts the numpad wait and enter keys to be delayed.
Adjusts shortcut keys to never repeat properly repeat.
Increases delay on wait keypress.

@Ruin0x11
If shortcuts do not repeat, you cannot

cast a spell repeatedly.
eat food repeatedly.
read scrolls repeatedly.

via shortcut key.
In Elona, players often do one action again and again so shortcut keys should be repeatable.

Makes sense, I'll make it repeatable. Although it seems like there was a strange issue with the shortcut key repeat to begin with. Before the player's main input key_check(1) is called. But this forced the delay to 1 instead of keywait. Should it be the opposite?

Makes sense, I'll make it repeatable. Although it seems like there was a strange issue with the shortcut key repeat to begin with. Before the player's main input key_check(1) is called. But this forced the delay to 1 instead of keywait because the input argument to key_check was 1. Should it be the opposite?

The previous key wait of shortcut keys were intended, but it seemed to be not good.

Key response are very improved, thank you! Merging.


downloading videos from archive

How can i download videos from archive.txt? I want to download these videos, but don't really know how

Videos in archive are already downloaded videos.


docs: Convert reST index pages to Markdown

Testing plan: Reviewed HTML diff.

Also, I enabled preview builds for PRs in ReadTheDocs. The Details link in the checks menu points to the preview build for this PR.

Merged, thanks for doing all this cleanup @andersk!


[flash, dv] Fix CI failures

Due to merging of these 2 PR - #11823 and #11770
Signed-off-by: Weicai Yang<EMAIL_ADDRESS>

Merging as it's passing in my local


Add podspec file

Created and added a pod spec file for future pod creation.

Closing as Pod has been made public on the Cocoapods Spec, which negates the need for this PR and the pod branch.


Reusing a typed array for writing a dataset causes a fatal error

Considering this code snippet:
const hdf5 = require('hdf5').hdf5;
const h5lt = require('hdf5').h5lt;
const Access = require('hdf5/lib/globals').Access;
const H5Type = require('hdf5/lib/globals').H5Type;

var file = new hdf5.File('t.h5', Access.ACC_CREAT);
var data = new Float32Array(10);
data.type = H5Type.H5T_NATIVE_FLOAT;
data.rank = 3;
data.sections = 1;
// create dataset with data
h5lt.makeDataset(file.id, 'data', data);

data[3] = 5;

// reuse typed array to overwrite content
h5lt.writeDataset(file.id, 'data', data);

file.close();

This program fails with the following message (master branch, Node.js v5.8.0):

FATAL ERROR: v8::ArrayBuffer::Externalize ArrayBuffer already externalized
Aborted (core dumped)

This is fundamental to V8 native side at this time.  I'll relook at the state of this in the latest v8 version and see if better error handling is now possible

In nodejs v9.9.0 they have a way to get to content without the Externalize.  I've committed the change

Will be testing backward version compatibility

works from nodejs v8.0.0. onward


Please add a license

Hi,
This is a cool project and I'd like to use it. Please add a license.

Thank you. I added the MIT License.


[Docs]: Updayed OIDC docs for Refresh token

Is there an existing issue for this?

[X] I have searched the existing issues

Documentation Link
No response
Discord/slack/intercom Link
No response
Describe the problem and improvement.
#17478. The changes are available in branch v1.4. Translate the changes to main for refresh tokens.

CC: @danciaclara - FYI.


[Backup] az backup vault backup-properties: Add new parameter --hybrid-backup-security-features to support setting the security features for hybrid backups

Description
az backup vault backup-properties set: Add a new optional parameter --hybrid-backup-security-features
Testing Guide

History Notes

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

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

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Backup


Run AsyncAPI studio without internet

Reason/Context

The current tool retrieves the loader.js file at first launch (from internet) which is then placed in the cache. At next launches, the file is retrieved directly from the cache
Some users may need to setup the AsyncAPI studio in an environment without internet. In that case, launch is not possible since the loader.js file cannot be retrieved from internet

Description

For the moment, to setup the tool on an environment without internet, the loader.js file has to be placed manually in the \public\js\ folder and \public\index.html file shall be adapted by adding:  <script src="%PUBLIC_URL%/js/loader.js"></script> before the ending body markup
Proposal is to modify the tool to include the loader.js file directly in it to be able to run it without internet and if the internet is available the tool only verifies there isn't a new version of the loader.js file to be used.

@antoineApi Ok, new version of studio 0.12.4 is out and I was able to fix this problem with the external loader. I check the network tab in the browser and the only sources are from our site (nothing external), so the build itself should already go without internet. Let us know. I am closing the issue, but if there would be any problems then give a comment :)

Fixed in https://github.com/asyncapi/studio/pull/352


Bug 2094665: dedicated resources modal stuck loading for non priv user

📝 Description
this PR include fixes for:

non-privileged users cant list nodes, so we do not show any info about the qualified nodes for a non-privileged user.
disable the link to search for nodes as it will lead to an error.
fixing title from Dedicated Resources to Dedicated resources

🎥 Demo
before:

after:
non-privileged user view:

admin view:

Signed-off-by: Aviv Turgeman<EMAIL_ADDRESS>

/lgtm


posted_at can't be blank

Hi
I have news content_type which has a field posted_at which is required: true
In my data/news.yml file, all the news have a posted_at: field filled in with data of this type
posted_at: '2015-11-11 18:00:00 +0100'

When pushing to the Engine, with the latest version of Coal (locomotivecms_coal (~> 1.0.0.rc3)) and Wagon (locomotivecms_wagon (2.0.0.rc5)), I get the error below.
This error did not occur with the previous versions.
Resource invalid: posted_at can't be blank, formatted_posted_at can't be blank
Resource invalid: posted_at can't be blank, formatted_posted_at can't be blank
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_coal-1.0.0.rc3/lib/locomotive/coal/resources/concerns/request.rb:36:in `do_request'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_coal-1.0.0.rc3/lib/locomotive/coal/resources/concerns/request.rb:15:in `put'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_coal-1.0.0.rc3/lib/locomotive/coal/resources/base.rb:35:in `update_with_locale'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_content_entries_command.rb:42:in `persist'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:34:in `block in _push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `each'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:30:in `_push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_content_entries_command.rb:12:in `block in _push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_content_entries_command.rb:10:in `each'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_content_entries_command.rb:10:in `_push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:25:in `block in _push_with_timezone'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/activesupport-4.2.5/lib/active_support/core_ext/time/zones.rb:48:in `use_zone'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:24:in `_push_with_timezone'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:18:in `block in push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/activesupport-4.2.5/lib/active_support/notifications.rb:166:in `instrument'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:47:in `instrument'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:16:in `push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_sub_commands/push_base_command.rb:12:in `push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_command.rb:54:in `block in _push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_command.rb:82:in `block in each_resource'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_command.rb:75:in `each'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_command.rb:75:in `each_resource'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_command.rb:53:in `_push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_command.rb:40:in `push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/commands/push_command.rb:30:in `push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon.rb:73:in `push'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/lib/locomotive/wagon/cli.rb:313:in `deploy'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
  /Users/cedriclor/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/locomotivecms_wagon-2.0.0.rc5/bin/wagon:12:in `<top (required)>'
  /Users/cedriclor/.rbenv/versions/2.2.3/bin/wagon:23:in `load'
  /Users/cedriclor/.rbenv/versions/2.2.3/bin/wagon:23:in `<main>'

Temporary work around.
Define posted_at as not required in the content_type/news.yml file

More details because the issue occurs also with other fields. The issue occurs when both required: true and localized: true
However, you would expect that providing localized versions of the field would solve the issue. This is not the case.
I have an event content_type which has a category field defined as follows:
category: # The lowercase, underscored name of the field
    label: Category of the event. This will be displayed on the events lists page. # Human readable name of the field
    type: select
    select_options:
      en: ["Dance", "Theater", "Poetry", "Performance"]
      fr: ["Danse", "Théatre", "Poésie", "Performance"]
      ru: ["танец", "Театр", "", "поэзия", "Представление"]
      "zh-CN": ["舞蹈", "剧院", "诗", "性能"]
    required: true
    localized: true

In my data/event.yml file, I define my events as follows:
"Sample 1":
    description: "Odio ad eaque voluptate aut amet earum et. Nihil necessitatibus excepturi fugiat veritatis et ut. Atque blanditiis suscipit mollitia rerum voluptas id eum. Aliquid voluptas qui."
    location: "Paris, Théâtre National du Palais de Chaillot"
    category:
      en: 'Dance'
      fr: 'Danse'
      ru: 'танец'
      "zh-CN": "舞蹈"
    main_star: Alexeï Guerman
    event_date: 2015/12/03 # YYYY/MM/DD
    event_start_date: 2015/12/24
    event_end_date: 2015/12/28
    featured_image: null # Path to a file in the public/samples folder or to a remote and external file.

and I get the same error.
The only work around consists in turning either required or localized as false.
However, if localized is turned as false, then it won't my subentries in the various locals from the data/events.yml file.

thanks @did, this was effectively the case. My bad, because the date was in ISO format, I thought it was not necessary to use subkeys for each locale.  Providing the subkeys solved the issue as regards posted_at.
However, I still haven't figured out what to do with the select field in my comment. Will make some more test and keep you posted.

@did I had not seen that you had fixed that in your last steam commit.... new steam commits are going at such a pace nowadays. You're CMS is evolving faster than any JS trendy framework!!!


fix two bugs

remove error label if the validations becomes valid
fix issue that response is null if ajax request is abort

+1 for this one as well.


Windracers Agenda post: Preview

Windracers Visit to Purdue University
West Lafayette, IN
May 24-26, 2023
Stephen Wright - Chairman, Windracers | www.windracers.com
http://linkedin.com/in/stephen-wright-74a88b33
Simon Muderack - CEO, Windracers
https://www.linkedin.com/in/simonmuderack/
Contact information for any assistance we can provide during your visit to Purdue University:
Sabine Brunswicker | Founding Director of the Research Center for Open Digital Innovation (RCODI)<PHONE_NUMBER> (c) |<EMAIL_ADDRESS>Howard Sypher | Brian Lamb School of Communication (BLSC) |<PHONE_NUMBER> (c) |<EMAIL_ADDRESS>Joe Krok | Purdue Research Foundation (PRF) |<PHONE_NUMBER> (c) |<EMAIL_ADDRESS>

Time
Meeting
Location

Wednesday, May 24 2023

17:00
Arrival PMU, Pickup
Chicago O'Hare

19:30
Dinner with Joe Krok PRF, William Crossley, Head, Aeronautics and Astronautics, John Norberg, author of Spacewalker, Vice President, Discovery Park District. Sabine Brunswicker, RCODI
PMU 8Eleven Bistro

Thursday, May 25 2023

07:30
Breakfast/Coffee with Entrepreneurial Community: Breakfast/Coffee Howard Sypher (Professor, Founding Head, BLSC), Mikel Berger, Founder, Delmar Software, Lindsay Mason, Founder, Frenchknot, Danny Milisavljevic, Purdue Physics - Webb Telescope Lead Researcher
PMU 8Eleven Bistro

10:00
Meeting Cyber Security Experts: Santiago de Torres, Joel Rasmus, Sabine Brunswicker, RCODI
Convergence Center Room 2321

11:00
Meeting with Dan Cziczo, Meteorology Expert (Stephen)
Convergence Center Room 2321

11:00
Wine Library Tour and Tasting
Nelson Hall of Food Science (Basement)

11:30
Lunch: Dan Whitenack, Physicist, AI researcher, Howard Sypher, Brian Lamb School of Communication, Amy Greehan, Consultant, formerly with DOE, Dave Banquert, writer, "Based in Lafayette"; Windracers' fellow candidates (two PhD students, Aimee (potential manager)
Convergence Center Room 2321

13:00
Meeting with PRF: Brian Edelman, John Ferency, Kimberly Allen, Joseph Krok:  Review of Operations Model;  Co-investment strategy
Convergence Center Room 2321

14:00
Meeting William Crossley, Dean Castro (Dean of Polytechnic Institute), Weinong Chen (Associate Dean of Research Engineering)
-

15:00
Meeting with Dan Cziczo, Meteorology Expert (Stephen)
Convergence Center Room 2321

15:30
Boeing Simulator with Paul Strickland, Pilot
-

16:00
Departure of Stephen to Chicago Airport
Purdue Memorial Union

18:00
Dinner: Sabine Brunswicker, RCODI and Simon Murdoch, Windracers
Nam Nam

Friday May 26, 2023

08:30
Breakfast/Coffee with Howard Sypher, BLSC; Tanya Gordiienko, MDF Ukraine, Purdue visting scholar; Amy Greehan, consultant, formerly with DOD
The Lobby Downtown

10:30
Departure to PURT
Purdue Memorial Union

11:00
Tour of PURT with Karen Plaut (Executive VP of Research, two fellow PhDs
PURT

12:30
Meeting with Dan DeLaurentis
Room needed or LEAPS

14:00
Late lunch and tour around campus with Howard Sypher and Kelley Bradstad, 4thSpaceHR
TBD

16:00
-
-

Marking as completed.


Feature/date

date timestamp added + csv customer names file fixed

Line 196: There should not be a space between the day and the T in the date string.

Line 196: There should not be a space between the day and the T in the date string.

Line 196: There should not be a space between the day and the T in the date string.


using controlled pagination default rows are not working

Hello Every one,
Not sure if this is a bug or code issue.
I started using the react table few days ago , i was trying to customize my table having a button which should should +10 more records, but up on initial loading i need to display only 10 records per page.o
I read the documentation even though if i didn't mention the pageSize it will take as default to 10, but what i see from my code it is defaulting to total number of available rows i.e, 14 which i was expecting 10 should be displayed at the first instance then later on when i click on the show more button it should the other 4 records.
I tried the same example but am i missing something or is it abug,
Please find the below code sandbox
https://codesandbox.io/s/gifted-dream-xbqnd?file=/src/App.js
Thank you

It is not a bug, it is just that the product array contains 14 items, and each page is captured the property of the data.length component of that product array. Each changed page restarts the cycle and displays the same result. It would be interesting to have a limit on the quantity of items to present, I think it is an interesting feature to implement


Errors when running nunitlite tests if SUT contains InternalTrace logs.

The fix made for issue #12 was an improvement. However, it turns out that the original problem of logging being ignored was actually useful in certain cases. In particular, when running tests under nunitlite, if the SUT contains log entries but doesn't initialize InternalTrace, an exception is now thrown.
This is a valid case, because some modules we test are normally used under the control of other modules, which do that initialization. In such a case, the NUnitLite  test has to be modified to initialize InternalTrace, generally its Main.
This issue is intended to explore ways of either eliminating the issue or making it easier to deal with.

Exploring the possibility of eliminating initialization entirely...

If anything is logged before initialization, write to "InternalTrace_" in the current directory.
If the user changes the output file in an initialization call after any output has been written close the original file and add a comment at the start of the new file.
Eliminate exception if the user calls initialize a second time.
Allow Initialization with only the trace level specified.

After some experimentation, I think the approach above is workable. Essentially, uninitialized logging calls will act as if the highest level (Debug) had been called for. This should make the source of the problem more discoverable. If a non-default file path is specified on initialization, two files will be output and each of them will indicate where the other is found. In simple cases, no file name needs to be specified at all.

I'm reopening this because the fix, although it works as described in an earlier comment turns out to be inconvenient in some cases. That was probably inevitable since I was trying to solve two different problems...

The original bug fix for #12, which was caused by logging occurring on one thread before initialization could happen on a different thread. In that case, the approach in this issue worked fine. The original default trace file contained a few entries while most were in the file created at the time of initialization. If the user located either file, they would then know where to find the other, which is a (small) improvement over just throwing an exception.

The second case this was intended to fix was testing under a runner without any knowledge of TestCentric.InternalTrace. This may seem odd, since the package is aimed at TestCentric development only. However, I do a lot of TestCentric  testing using NUnitLite. The current fix still requires modifying the standard Program.cs so it calls InternalTrace.Initialize specifying InternalTrace.Off in order to avoid creation of a rather large log file for each run.

In fact, that second case is much more common than the first, which arose from an error in our agent code.
So, I'll modify the existing fix as follows...

Stop allowing uninitialized logging, i.e. go back to ignoring such calls., but remember that they occurred.
When initialization takes place, if there was any prior logging we ignored, add a warning message at the start of the file.
Allow automatic initialization of the logging level by use of an environment variable. The user could set this after noticing the above warning message. If feasible, modify our cake recipe to allow an option that sets that variable.
Keep most of the refactoring changes already made for this issue as well as all new tests.


Should Scrollbar include wheel listeners?

Re: schrodinger/fixed-data-table-2/issues/316
I have an issue where when react-custom-scrollbars is floating over an element with a wheel listener, react-custom-scrollbars will not scroll.
The details are outlined further in the other issue, but I'll summarize here:
Scrollbar floats above DataTable.
Scrollbar has a scroll event listener to move its scrollbar.
DataTable has a wheel event listener to move its scrollbar.
DataTable's wheel event listener calls event.preventDefault().
The mouse is positioned over the Scrollbar element.
The mouse wheel is moved.
The Scrollbar element does not respond, as it has no wheel event listener.
The event propagates to background elements.
The DataTable's wheel event listener fires and prevents the scroll event from firing.
DataTable scrolls in response to the mouse wheel event.
Scrollbar never receives a scroll event.
Scrollbar never scrolls.
Contrary to expected behavior, the background element is now scrolling instead of the custom scrollbar, simply due to the fact that the background element has a wheel event listener.
Should the custom scrollbar have a wheel event listener to capture scroll attempts by the user? Or would you say this is an issue with the background element?

@CharlesStover may be add the wheel listener to view element of custom scroll on your own and make event.stopPropagation() ?


Typescript Support

Is there any support for typescript?

there are no plans to - if you want to add support, having for you to add it 👍

This is my first attempt at making an external TypeScript definition, so bear with me.
declare module "body-scroll-lock" {
  export interface BodyScrollOptions {
    reserveScrollBarGap: boolean;
  }

  export function disableBodyScroll(
    targetElement: HTMLElement,
    options?: BodyScrollOptions
  ): void;

  export function enableBodyScroll(targetElement: HTMLElement): void;

  export function clearAllBodyScrollLocks(): void;
}

I can make a pull request if needed.

Thanks @Egoscio

@Egoscio why is the targetElement an HTMLElement? This prevents us from passing body for example as the targetElement.


added support for no suggestion selected

Handling case where user press enter and/or the field loses focus, or gets cleared.

@PiegoIlTempo  Thanks!
I incorporated your PR into ver 1.2.2 of https://pub.dev/packages/google_maps_places_autocomplete_widgets
My package is a evolution of @leandro-zanardi 's maps_places_autocomplete and is upward compatible (with changes to the import and widget names).
As you added the onFinishedEditingWithNoSuggestion callback I have added a number of other callback hooks and added a TextFormField widget and also refactored the overlay into a generic mixin that is used by both the TextField and TextFormField widgets.
There examples have been expanded to illustrate the new features.
github repo:
https://github.com/timmaffett/google_maps_places_autocomplete_widgets


MANIFEST.in doesn't included the ckeditor_uploader/templates/ckeditor/browse.html

Today I tried the new django-ckeditor 5.0.1.
It seems that in MANIFEST.in file doesn't included the ckeditor_uploader/templates, which leads to the following error:
TemplateDoesNotExist at /ckeditor/browse/

when you try to access, localhost:8000/ckeditor/browse/. I am supposing that, adding:
recursive-include ckeditor_uploader/templates *

at MANIFEST.in the malfunction will be fixed.

I keep getting this error when I clink on browse in the image info tab please help and I get import error at ckeditor/upload in the upload tab when I click on send to server. please help. thanks.

Do you have the ckeditor and ckeditor_uploader in INSTALLED_APPS?

I have ckeditor_uploader in installed apps but I still get import error in the upload tab. Thanks for your help

you may need both, and check what the exception is saying. maybe it's something else too

I get the error 'ImportError at /ckeditor/upload/'  No module named image..
Might it have something to do with my file path?
On 15 Aug 2016 13:52, "Piotr Maliński"<EMAIL_ADDRESS>wrote:

you may need both, and check what the exception is saying. maybe it's
something else too
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/django-ckeditor/django-ckeditor/issues/221#issuecomment-239794346,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT31JhjpKQ89utZuTVYeCGzfkhgLWwEIks5qgGEQgaJpZM4F7N0q
.

Pillow not installed

Sorry for troubling you. I have the CKEDITOR_IMAGE_BACKEND = "pillow"
On 15 Aug 2016 14:21, "Piotr Maliński"<EMAIL_ADDRESS>wrote:

Pillow not installed
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/django-ckeditor/django-ckeditor/issues/221#issuecomment-239799969,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT31JjZhK0Ae5wwjcfoVRwvh5Tir4m70ks5qgGf0gaJpZM4F7N0q
.


Add checks for ftype=1 for docker and mesos directories if using XFS

High-level description
This is backport of #2768
When using XFS (only supported filesystem for lower level filesystems for Centos) the volumes must be mounted d_type support enabled (ftype=1). This requirement is documented here https://docs.mesosphere.com/1.10/installing/ent/custom/system-requirements/install-docker-centos/#requirements-and-recommendations. DC/OS installer currently does not enforce this and can lead to a lot of pain for users and customers if they discover this requirement after setting installing the cluster and having it operational for some time. Reformatting the volumes is not a trivial task. So If we short circuit the install of DC/OS if the requirement is not met we can save a lot of pain to the users and customers
What features does this change enable? What bugs does this change fix?
Enforce the system requirement of ftype=1 for XFS volumes
Corresponding DC/OS tickets (obligatory)
COPS-3158 Block DC/OS install if mesos work dir or docker root dir is XFS but not mounted with ftype=1
Related tickets (optional)
None
Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[X] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@surdy This backport is legitimately failing tests, it breaks genconf for an advanced install. Looks like we hardcode the Mesos agent work dir in 1.10: https://github.com/dcos/dcos/blob/c7d83a25e1ff109e083acfafb46f237e0a799d6f/gen/dcos-config.yaml#L427

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ready for review

@mesosphere-mergebot override-status teamcity/dcos/build/tox https://jira.mesosphere.com/browse/DCOS_OSS-2422

I guess this missed the 1.10.7 deadline 💔 . Something I could have done to prevent that ?

@surdy  - It is not. I have not built it yet, as I raised an important metronome bug. I will include this in 1.10.7.

@surdy  - Please let your status checks to green with reviews and overrides from owners.


feat(timepicker): add spinner support for TimePicker

Needed for #854
Summary

The new DateTimePicker component requested on #854 needs some new components, like an inline calendar and a TimePicker with a numeric spinner. This PR takes care of the latter.

Change List (commits, features, bugs, etc)

Overridden and extended TimePicker so we can increment hours and minutes with the spinner buttons and/or keyboard
Works with RTL
Doesn't throw any a11y error

Acceptance Test (how to verify the PR)

new basic test suite available here: ?path=/story/watson-iot-experimental-timepicker--with-spinner

@sstone2423 good observation! i updated it to take care of the flip. I checked other spinners around and the consensus seem to be not to interact with incrementing hours when you perform a flip of the minutes, so I kept it simple and kept the flips independent.
Also, remove the useEffect to highlight the portion of time that is currently selected - that messed up a lot with manually writing the time

@lukefirth this seems like a piece of functionality that is well isolated and would be a great candidate to push into Carbon. Did we discuss adding this to Carbon?

After a discussion with @davidicus, I think an alternative approach that will allow us to avoid overriding the Carbon TimePicker would be ideal. TimePicker takes children as a prop, and places it at the same place in the markup that you have configured the "spinner" markup to render.
The first change would be to isolate the spinner arrows to their own presentational SpinnerControl component that we could compose as a child of TimePicker.
From here we have two options:

Export a TimePickerSpinner component that pre-configures TimePicker children to be the SpinnerControl and would hold the stateful logic controlling the stock TimePicker via the click/key events from SpinnerControl. This component would probably render something simple like:

<TimePicker>
  <SpinnerControl/>
<TimePicker>

Export a custom hook to contain the stateful logic. The hook would accept the parameters required for the stateful event logic - the TimePicker ref, a ref for the SpinnerControl, events etc.
With this option we could provide documentation/story to demonstrate how to utilize this, but in sense it would be

import React from "react";
import { TimePicker, SpinnerControl, useTimePickerSpinner } from "carbon-addons-iot-react";

const App = () => {
  const { pickerValue } = useTimePickerSpinner({ timePickerRef ...whateverTheArgsNeedToBe });

  return (
    <TimePicker
      ref={timePickerRef}
      pickerValue
      ...etc
    >
      <SpinnerControl ...etc />
    </TimePicker>
  );
};

Either way, encapsulating this logic and using it as an augmentation to the Carbon component seems to be a much more sustainable approach than overriding the component. We can/should hop on a webex to chat, I realize this is quite the barrage of feedback for you today! 😅

The knobs are acting oddly - when I deselect the picker, knobs disappear, but when re-enabled the knobs do not reappear.

@tay1orjones  I've been noticing some odd behavior with other stories in that same fashion. There may be some leakage from other stories. Particularly the Munich Building title in stories that doesn't have that knob at all. May be a larger bug

The knobs are acting oddly - when I deselect the picker, knobs disappear, but when re-enabled the knobs do not reappear.

@tay1orjones I've been noticing some odd behavior with other stories in that same fashion. There may be some leakage from other stories. Particularly the Munich Building title and the isEditable knobs in stories that don't have those knobs at all. May be a larger bug. From the looks of it, they're knobs coming from Card

@tay1orjones @sstone2423 it seems actually they are a mix of knobs from Dashboard and TileGallery - Apparently other people have it too

Ok, responses to @tay1orjones 's comments. Take these in context as gut reactions of what I think perfect will be, and then we can back and forth.

it is impossible to tell if I will increase the hour or minute value by pressing the up arrow. A reasonable remedy could be to place a slight underline below the currently selected time parameter (hours or minutes).

I like this approach. I would anticipate the interaction to be that these would only be visible when the spinner chevrons are being interacted with (hover, focus, click) and not otherwise (so don't show by default, don't show when typing inside the input etc).
That being said, this is a relatively low priority as immediately when a user interacts once, they get the feedback they need to understand what is happening, and the nature of this is that is wouldn't be slow or disruptive for them to recover from if it did do the opposite of what they expected.

The cursor should either stay put or not be visible when incrementing via up/down arrows. I'd like to ask for a visual/interaction review on these items.

Agreed, from what I can see in this PR and what looks like the implementation has been updated to do- not showing the cursor when interacting with the up/down chevrons looks to be the most natural way forward.

I don't know where we ended with ease/ability to contribute back, but this would be a nice one if we can!

:tada: This PR is included in version 2.59.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


V2 issue: RemixServer context types are not happy with EntryContext from remix-run/node

What version of Remix are you using?
0.0.0-nightly-49e8da1-20230823
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
Here's the TypeScript playground:
import * as React from 'react'
import { renderToString } from 'react-dom/server'
import { type EntryContext } from '@remix-run/node' // types: 0.0.0-nightly-49e8da1-20230823
import { RemixServer } from '@remix-run/react' // types: 0.0.0-nightly-49e8da1-20230823

export default async function handleRequest(
	request: Request,
	responseStatusCode: number,
	responseHeaders: Headers,
	remixContext: EntryContext,
) {
	const markup = renderToString(
		<RemixServer context={remixContext} url={request.url} />, // <-- error here
	)

	responseHeaders.set('Content-Type', 'text/html')

	return new Response('<!DOCTYPE html>' + markup, {
		status: responseStatusCode,
		headers: responseHeaders,
	})
}

Expected Behavior
You should be able to pass context without issue
Actual Behavior
You get the following error:
Type 'import("file:///node_modules/@remix-run/server-runtime/dist/entry").EntryContext' is not assignable to type 'import("file:///node_modules/@remix-run/react/dist/entry").EntryContext'.
  Types of property 'routeModules' are incompatible.
    Type 'RouteModules<EntryRouteModule>' is not assignable to type 'RouteModules'.
      'string' index signatures are incompatible.
        Type 'EntryRouteModule' is not assignable to type 'RouteModule'.
          Types of property 'meta' are incompatible.
            Type 'MetaFunction<unknown, {}> | V1_HtmlMetaDescriptor | undefined' is not assignable to type 'MetaFunction<unknown, Record<string, unknown>> | undefined'.
              Type 'MetaFunction<unknown, {}>' is not assignable to type 'MetaFunction<unknown, Record<string, unknown>>'.
                Types of parameters 'args' and 'args' are incompatible.
                  Property 'parentsData' is missing in type 'MetaArgs<unknown, Record<string, unknown>>' but required in type '{ data: any; parentsData: {} & RouteData; params: Params; location: Location; }'.

huh - I don't know where V1_HtmlMetaDescriptor is coming from in there but I suspect that's the weasel

Should be fixed by #7249 in tonights release

Awesome! Thank you!

I just had this issue again with Remix 2.5.0. I noticed that in package.lock, @remix-run/testing resolved @remix-run/node version 2.5.1 while all others resolved to 2.5.0.
I fixed the issue by deleting package.lock and reinstalling all node modules.

Huh - not entirely sure how that might happen - but if you find reproducible steps with installation or upgrades please open a new issue so we can take a look and see if we've got some deps wrong.
I created a utility for updating everything in lock step a while back that may be of use (I am too lazy to type them all out or manually update them all in package.json 😂 ): https://github.com/brophdawg11/upgrade-remix

Huh - not entirely sure how that might happen - but if you find reproducible steps with installation or upgrades please open a new issue so we can take a look and see if we've got some deps wrong.
I created a utility for updating everything in lock step a while back that may be of use (I am too lazy to type them all out or manually update them all in package.json 😂 ): https://github.com/brophdawg11/upgrade-remix

Thanks


feat(pinia-orm): Improve DateCast & orderBy for Dates

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
orderBy can now handle correctly Date objects for sorting and DateCast supports now also numbers for timestamps
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.73%. Comparing base (64b3b57) to head (bbf5c6e).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1825      +/-   ##
==========================================
+ Coverage   99.67%   99.73%   +0.05%
==========================================
  Files          87       87
  Lines        5923     5934      +11
  Branches      505      508       +3
==========================================
+ Hits         5904     5918      +14
+ Misses         17       14       -3
  Partials        2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


req.swagger.params decoding

I ran into this issue:
I have a path parameter like: abc:HZ and a URL like: http://localhost:3000/accounts/{accountId}
I call my URL (parameter is encoded): http://localhost:3000/accounts/abc%3AHZ
Using swagger-tools:
req.swagger.params.accountId.value = abc%3AHZ

Using express:
req.params.accountId = abc:HZ

Why the difference? It seems express is actually decoding the URL parameters while swagger tools are not. Shouldn't the values be decoded always?
Thanks

We use the same body parser as Express but since this is not a body parameter, it seems we need to explicitly decode path parameters.

Do you mean we as library users need to explicitly decode them or is it something you are planning to do in the library itself?
Thanks

Nope, I'll do it in the library.

Thanks man!


Congratulate people who have their first commit merged

Ported from old cobot repo, opened by @sils - https://gitlab.com/coala/cobot/issues/6

Similar to https://github.com/coala/corobo/issues/245

And ask them to fill in the newcomer survey.


[Bug]: Can't use yarn rope config for long context in Qwen2 model

Your current environment

The output of `python collect_env.py`

Collecting environment information...
 However, if input's len is larger than 32768(original_position_embedding_len), the model's output will be something confusing, similar to a kind of repetition of the input.
this error happened in the version of 0.6.3.post1, but when I switch to v0.6.0, everything is OK.
I find that transformers's repo from recent versions don't accept "original_max_position_embeddings", but vllm need it. Maybe this is a confict between transformers and vllm ?
Does anyone know how to correctly enable the long context feature? Thanks ^_^
PS: I can't run collect_env.py script in v0.6.0's docker image, but 0.6.3.post1's docker image is OK.
PPS: I just search issues about "original_max_position_embeddings", but got nothing releated.
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

@WoosukKwon do you know about the context of this config field?

Hi @DarkLight1337 the config is listed on the Qwen documentation in guidance for configuring long context with vllm:
https://qwen.readthedocs.io/en/latest/deployment/vllm.html#extended-context-support

@spgoodman the configuration provided by the @FlyCarrot  matches the documentation. I can also report the presence of the bug on 0.6.3.post1. using vLLM 0.6.0 does not remove the warning:
Unrecognized keys in `rope_scaling` for 'rope_type'='yarn': {'original_max_position_embeddings'}

However, empirically, version 0.6.0 does allow for longer context with the configuration enabled. So thanks for that tip @FlyCarrot !

I think this is link maybe help. https://huggingface.co/meta-llama/Llama-3.1-8B-Instruct/discussions/15#670a76a4e3d216b4243b2d4d
In short, I Guess : vllm nedd original_max_position_embeddings but transformers do not allow this key.
So, anybody knows how to balance it?
Thanks!

You should pass "rope_type" key instead of "type".

same issue with vllm 0.6.2...

same issue with vllm 0.6.4

same issue with vllm 0.6.4.post1
and If this warning occurs, the model's generation gets cut off at a very early stage.


Huge input causes OOM.

With the changes in Correctly split text into sentences #204, SudachiTokenizer analyzed all characters (was only first 4096).
The change is fine. But due to the change, I see OOM issue.
SudachiTokenizer.reset() analyzes all text and store the result in ArrayList<MorphemeList>.  It causes OOM due to large list size.
I think it would be better to change the analyzing to be done gradually with the SudachiTokenizer.incrementToken() function, instead of all at once with the SudachiTokenizer.reset() function.  as well as StandartTokenizer.java

Further investigation,
JapaneseTokenizer.tokenizeSentences() in the Sudachi library is analyzing all text at once and storing it in local list, which seems to be the cause of the OOM.
Therefore, I move this issue to Sudachi.

Could you please close this issue, because  https://github.com/WorksApplications/elasticsearch-sudachi/pull/132 is merged.

Option 1. Fix Sudachi Plugin (this repo). SudachiTokenizer pass small chunk of text to JapaneseTokenizer.
Option 2. Fix Sudachi. JapaneseTokenizer.tokenizeSentences() does not analyze all text all at once.

It applied Option 1.


Improved performance in album load

Removed nested loop for thumbnail retrieval

Maybe I'm missing something, but it looks like the implementation is missing the sorting of the thumbs ($this->settings['sortingPhotos']). The first 3 thumbs are always the first 3 photos of the album, based on the photo-sorting. https://github.com/electerious/Lychee/pull/372/files#diff-c2d1bf354e4b5d583df1a7213adec491L213

Will add that in; I had accounted only for the album sort.
Kirk

Kirk Friedenberger
312.925.2661

On Jul 1, 2015, at 1:07 PM, Tobias Reich<EMAIL_ADDRESS>wrote:
Maybe I'm missing something, but it looks like the implementation is missing the sorting of the thumbs ($this->settings['sortingPhotos']). The first 3 thumbs are always the first 3 photos of the album, based on the photo-sorting. https://github.com/electerious/Lychee/pull/372/files#diff-c2d1bf354e4b5d583df1a7213adec491L213
—
Reply to this email directly or view it on GitHub.

This was the part I couldn't get working. Maybe you have more luck.

Yes I have it working -- question though, should the thumbs sort by star
DESC, then the photo sorting order setting? Or just the photo order
setting. Meaning if there are favorites in the album, should they appear as
the preferred thumbnails?
On Wed, Jul 1, 2015 at 2:26 PM, Tobias Reich<EMAIL_ADDRESS>wrote:

This was the part I couldn't get working. Maybe you have more luck.
—
Reply to this email directly or view it on GitHub
https://github.com/electerious/Lychee/pull/372#issuecomment-117800688.

--
Kirk Friedenberger

Favorites should have a higher priority, no matter what the sorting says.

@kfriedenberger Can you add your updated version to the PR?

@kfriedenberger Any news?

I've moved to another platform but will dig up the code and send across.
Thanks.
Kirk

Kirk Friedenberger
312.925.2661

On Aug 9, 2015, at 7:01 AM, Tobias Reich<EMAIL_ADDRESS>wrote:
@kfriedenberger Any news?
—
Reply to this email directly or view it on GitHub.


python 3.11 support

Description
can we have a release for python 3.11?
Justification
We intend to us smartredis as part of an MLCommons benchmark that also uses tensorflow. Although we can use python3.10, it would be best to support also python.3.11 as tensorflow  and tensorflow-serving is now also for them.
Implementation Strategy

create a while that is supported on python 3.11 with pip install
create an Dockerfile example in the source code, so we can add it to docker images we create for the benchmark
create a build.def file so we can add it easier to apptainer images we create for the benchmark

My contact<EMAIL_ADDRESS>

Thanks for posting this issue.  We are working on supporting Python 3.11 in the next releases of SmartSim and SmartRedis.  The SmartSim Python 3.11 support can be tracked via https://github.com/CrayLabs/SmartSim/issues/376 .  We will post here when there is a PR available to test with 3.11 support.

Python 3.11 support for SmartRedis has been added to the development branch with the merge of #450! While you should be able to start using it now, we highly recommend using SmartRedis and SmartSim with the same version of Python. SmartSim should also be receiving Python 3.11 shortly with https://github.com/CrayLabs/SmartSim/pull/461.
Both libraries will have official support for Python 3.11 in the next release!


Winch Subsystem

@Travis-Team2619  was leading this one, and @cole-s  was helping out as well if I recall.
The idea was to have something on the back of the robot for grabbing bins off the step.

Yes @cole-s was helping... and just a note, we need to have 3 separate inputs in the code for the three separate inputs.


[C++][Parquet] Bring parquet::arrow up to date with API changes in arrow::io

See patches in ARROW-280 and ARROW-267
Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wesm) / @wesm
Note: This issue was originally created as PARQUET-728. Please see the migration documentation for further details.

Wes McKinney / @wesm:
Issue resolved by pull request 167
https://github.com/apache/parquet-cpp/pull/167

Wes McKinney / @wesm:
See https://github.com/apache/parquet-cpp/pull/167


Fuzzing: Add experimental version of container fuzzer

Adds another version of the container_fuzzer that downloads the containerd binaries when starting a new fuzz run, instead of using the binaries that were built by make.
Moves the initialization out of init() since it now does not apply to all fuzzers.

The current approach to managing the containerd binaries works fine locally in the OSS-fuzz environment, but when running continuously by OSS-fuzz, then the performance is unsatisfactory. It would be great to get this version of the fuzzer up and running to observe it when running continuously.

/ok-to-test


Implement StarkConfig Validation Functionality

We are initiating a task to develop a validation function for StarkConfig objects. This function, to be named stark_config_validate, will be responsible for ensuring the integrity and correctness of StarkConfig objects. It will include a series of checks and validations tailored to our specific operational and security needs.
Reference: https://vscode.dev/github/Okm165/cairo-lang/blob/v0.11.0-run-proof-sw-patch/cairo-lang-0.11.0/starkware/cairo/stark_verifier/core/config.cairo#L42

Functions that needs to be implemented:

[ ] stark_config_validate
[ ] proof_of_work_config_validate
[ ] traces_config_validate
[ ] validate_vector_commitment
[ ] fri_config_validate
[ ] fri_layers_config_validate


segment_size for task creation not used

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

I want to segment tasks via SDK just like in the UI
Steps to Reproduce (for bugs)

Add a task via SDK
add data_params

data_params = {
    "image_quality": 85,
    "segment_size": 4
}

no split of the data done

Expected Behaviour

New created task will split up the images into segments like in the UI
Current Behaviour

No split done, segment_size ignored in code (not 100% sure if this is the right place actually)
https://github.com/opencv/cvat/blob/5a9858cc5224a5ad7b18a2f18679f0e47274de4e/cvat-sdk/cvat_sdk/core/proxies/tasks.py#L87
Possible Solution

Add a segment_size to the task creation data_params
Context

I want to segment tasks via SDK just like in the UI
Your Environment

cvat2.3  & cvat-sdk2.3 & debian

Hi, this parameter should be specified in the task creation parameters, not in the data parameters.

Thanks, this works!
I didnt see this.


Improvement/add custom config

Thi PR will allow specifiying custom configuration is rundeck-config

@pcross616 I think its a good idea to let people use custom configuration in the rundeck-proerties file. Its  a bit hectic if we want to support every configuration option. Presently I need to use rundeck s3 log plugin to store logs on s3 and for that I need to set some parameters in the rundeck-config.properties file.

@pcross616
I am using the s3 log plugin for storing the logs. But there is some bug in rundeck that needs me to set a JVM property  "-Djava.io.tmpdir=".  You can see the bug details https://github.com/rundeck-plugins/rundeck-s3-log-plugin/issues/6. Thats why I need the custom JVM properties there.
I have a use case to separate the execution log directory from base directory. The reason is to use a faster disk. That explains the need for having the execution log directory attribute.

@pcross616 Although with subsequent commits I have changed the profile file. Still keeping the ability to specify custom JVM option would make sense


unable to deploy with test data

Hello, I'm trying to create a cortex data foundation deployment inside a test project i have owner permissions on. I've followed the docs and i can run the mando command, everything runs fine and it tells me the project is OK for deployment.
I get the following error when i attempt to run with _TEST_DATA=true and _DEPLOY_CDC=true
aaron_cross@cloudshell:~/cortex-data-foundation (cortex-customer-361107)$ gcloud builds submit --project cortex-customer-361107 --substitutions _PJID_SRC=cortex-customer-361107,_PJID_TGT=cortex-customer-361107,_DS_CDC=CDC_PROCESSING,_DS_RAW=RAW_LANDING,_DS_REPORTING=TraceMarkReporting,_DS_MODELS=TraceMarkML,_GCS_BUCKET=ngis-cortex-customer-logs,_TGT_BUCKET=ngis-cortex-customer-dags,_TEST_DATA=true,_DEPLOY_CDC=true,_GEN_EXT=true
Creating temporary tarball archive of 203 file(s) totalling 5.3 MiB before compression.
Some files were not included in the source upload.

Check the gcloud log [/tmp/tmp.T9dZ5OS1ek/logs/2022.08.31/<IP_ADDRESS>222.log] to see which files and the contents of the
default gcloudignore file used (see `$ gcloud topic gcloudignore` to learn
more).

Uploading tarball of [.] to [gs://cortex-customer-361107_cloudbuild/source/1661932154.324673-5f37490f44da470e9d4bb2e402d16614.tgz]
Created [https://cloudbuild.googleapis.com/v1/projects/cortex-customer-361107/locations/global/builds/72a34886-3b9a-43be-9c38-62ece9619b0e].
Logs are available at [ https://console.cloud.google.com/cloud-build/builds/72a34886-3b9a-43be-9c38-62ece9619b0e?project=501874947377 ].
--------------------------------------------------------------------------------------------- REMOTE BUILD OUTPUT ---------------------------------------------------------------------------------------------
starting build "72a34886-3b9a-43be-9c38-62ece9619b0e"

FETCHSOURCE
Fetching storage object: gs://cortex-customer-361107_cloudbuild/source/1661932154.324673-5f37490f44da470e9d4bb2e402d16614.tgz#1661932156638158
Copying gs://cortex-customer-361107_cloudbuild/source/1661932154.324673-5f37490f44da470e9d4bb2e402d16614.tgz#1661932156638158...
/ [1 files][  4.5 MiB/  4.5 MiB]
Operation completed over 1 objects/4.5 MiB.

Step #1: Uploading tarball of [./src/SAP_CDC/] to [gs://cortex-customer-361107_cloudbuild/source/1661932255.252384-23319bb9532d4fc590049c7ca2b908f1.tgz]
Step #1: Created [https://cloudbuild.googleapis.com/v1/projects/cortex-customer-361107/locations/global/builds/721a0178-1a63-420f-95d4-e493ddfaf1a2].
Step #1: Logs are available at [ https://console.cloud.google.com/cloud-build/builds/721a0178-1a63-420f-95d4-e493ddfaf1a2?project=501874947377 ].
Step #1:
Step #1: BUILD FAILURE: Build step failure: build step 1 "gcr.io/kittycorn-public/deploy-kittycorn-cdc:v1.0" failed: step exited with non-zero status: 1
Step #1: ERROR: (gcloud.builds.submit) build 721a0178-1a63-420f-95d4-e493ddfaf1a2 completed with status "FAILURE"
Step #1: ----------------------------- REMOTE BUILD OUTPUT ------------------------------
Step #1: starting build "721a0178-1a63-420f-95d4-e493ddfaf1a2"
Step #1:
Step #1: FETCHSOURCE
Step #1: Fetching storage object: gs://cortex-customer-361107_cloudbuild/source/1661932255.252384-23319bb9532d4fc590049c7ca2b908f1.tgz#1661932255762367
Step #1: Copying gs://cortex-customer-361107_cloudbuild/source/1661932255.252384-23319bb9532d4fc590049c7ca2b908f1.tgz#1661932255762367...
/ [1 files][ 34.8 KiB/ 34.8 KiB]
Step #1: Operation completed over 1 objects/34.8 KiB.

Hi @aaron-ngis, would you be able to share the logs of the cloud build step that is failing? And can you also add a screenshot of the execution details tab of that step?
I'd also like you to check whether any tables have been created in the RAW or CDC datasets, can you check your BigQuery workspace as well and provide some feedback?
Finally, did you make any adjustments to the files prior to starting the deployment that we should be aware of?
I'll be looking forward to your response to get you back on track with your Cortex deployment.
Best regards,
Benjamin

@benschuler certainly, thanks for the assistance;
logs
starting build "721a0178-1a63-420f-95d4-e493ddfaf1a2"

FETCHSOURCE
Fetching storage object: gs://cortex-customer-361107_cloudbuild/source/1661932255.252384-23319bb9532d4fc590049c7ca2b908f1.tgz#1661932255762367
Copying gs://cortex-customer-361107_cloudbuild/source/1661932255.252384-23319bb9532d4fc590049c7ca2b908f1.tgz#1661932255762367...
/ [0 files][    0.0 B/ 34.8 KiB]
/ [1 files][ 34.8 KiB/ 34.8 KiB]
Operation completed over 1 objects/34.8 KiB.

Thanks for the additional details @aaron-ngis , on that second screenshot can you switch to the tab "execution details" and attach a screenshot of that as well?
I am also noticing that your BigQuery dataset is called CDC_PROCESSED, while your deployment parameters are maintained as CDC_PROCESSING. Can you please try the deployment again with _DS_CDC=CDC_PROCESSED to make sure the dataset can be found?

@benschuler thanks! it was your second point that solved it? maybe we could have a "dataset not found" type of check before the main CDC work kicks off?
Either way, thanks for your help


syncer(dm): discard checkpoint snapshot when syncer reset

What problem does this PR solve?

Issue Number: close https://github.com/pingcap/tiflow/issues/8374
checkpointFlushWorker may skip calling FlushPointsExcept if execError is not nil. This leads to inconsistent snapshot status.
https://github.com/pingcap/tiflow/blob/2f363f653a49fc557ebaab1afa7a47f900fbfc8f/dm/syncer/checkpoint_flush_worker.go#L82
https://github.com/pingcap/tiflow/blob/2f363f653a49fc557ebaab1afa7a47f900fbfc8f/dm/syncer/checkpoint.go#L662
What is changed and how it works?
Always discard checkpoint snapshots after the syncer is reset.
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

UT is needed to be updated

@lance6716 @GMHDBJD PTAL again, test passed.

/merge