Declarative pipeline support

This adds support for declarative pipeline scripts, so that the persistent parameters can be created like the following (like requested in #8)
pipeline {
    parameters {
        persistentBoolean(name: 'Boolean', defaultValue: true, description: 'A boolean parameter', successfulOnly: false)
        persistentString(name: 'String', defaultValue: 'a single line', description: 'A string parameter', successfulOnly: false)
        persistentText(name: 'Text', defaultValue: 'text\nwith\nmultiple\nlines', description: 'A text parameter', successfulOnly: false)
        persistentChoice(name: 'Choices', choices: ['red', 'green', 'blue'], description: 'A choices parameter', successfulOnly: false)
    }
    ...
    stages {
        ...
    }
}

The parameters are also supported by the declarative snippet generator.
For this feature it's needed to bump the minimal required Jenkins version to 2.164.1. The additional code is basically copied from the build-in non-persistent variants of these parameter types.
Further visible improvements (as they exist on the non-persistent parameter types):

Option to trim the value of the persistent string parameter.
Proper rendering of HTML in the parameter description (see #4).

Code improvements:

Determination of default value for build moved into method getDefaultParameterValue() in order to separate it from the original default value used for editing the parameter definition.
Jelly code fixed and modernized.

Can someone please have a a look at it and merge?
This feature would be a fine addition to the plugin.

thanks for merging this. when will it be available for automatic upgrade from Jenkins ?  our devops say Jenkins  doesn't give them the option to upgrade from 1.2 and the github release is not in .hpi format.  I created an issue #13  for the same.

I am trying to add this in a seed job but I am getting this error:
Processing DSL script nonprod_deploy.jenkins
ERROR: (nonprod_deploy.jenkins, line 30) No signature of method: javaposse.jobdsl.dsl.helpers.BuildParametersContext.persistentBoolean() is applicable for argument types: (java.util.LinkedHashMap) values: [[name:Boolean, defaultValue:true, description:A boolean parameter, ...]]
Finished: FAILURE

Any idea what I am doing wrong?
This is my code:
...
	parameters {
		persistentBoolean(name: 'Boolean', defaultValue: true, description: 'A boolean parameter', successfulOnly: false)
	}
...

Resolved #8
Fixed #9
Fixes #4

I am trying to add this in a seed job but I am getting this error:
Processing DSL script nonprod_deploy.jenkins
ERROR: (nonprod_deploy.jenkins, line 30) No signature of method: javaposse.jobdsl.dsl.helpers.BuildParametersContext.persistentBoolean() is applicable for argument types: (java.util.LinkedHashMap) values: [[name:Boolean, defaultValue:true, description:A boolean parameter, ...]]
Finished: FAILURE

Any idea what I am doing wrong?

I guess this is a limitation of the Jenkins Job DSL plugin, it only supports the parameter types listed here: https://jenkinsci.github.io/job-dsl-plugin/#path/job-parameters


What is the recommended way to serve static html page

I can’t find what the best way to serve a static abc.html file is in Saturn? Is it to use Controller.text and feed that the content of the file and then also set the content type header? Or is it something built in that I haven’t found where you just can point to the file?

You can use the use_static command in the application and provide that with a physical path where static files live?

@isaacabraham, sounds simple enough. But how do you go about serving an index.html on /?

There is Controller.file helper function - https://github.com/SaturnFramework/Saturn/blob/master/src/Saturn/ControllerHelpers.fs#L42

I'd prefer doing a permanent redirect from / to /index.html, and if you were already serving static files at your root then that would do just fine.  This is nice because the underlying static files middleware handles etag calculation, HEAD requests, everything for you: https://github.com/aspnet/AspNetCore/blob/master/src/Middleware/StaticFiles/src/StaticFileContext.cs#L298-L341

Ooh, I found a better, more supported way: add app.UseDefaultFiles() before app.UseStaticFiles(): https://docs.microsoft.com/en-us/aspnet/core/fundamentals/static-files?view=aspnetcore-3.0#serve-a-default-document
But the use_static handler already sets app.UseDefaultFiles() (see https://github.com/SaturnFramework/Saturn/blob/master/src/Saturn/Application.fs#L209), so it looks like it should work already?

I had some problems getting it to work when I cloned the repo and tried to run the ChannelSample project. The app starts, but I can't reach any of the routes specified, this is even before me trying to modify them.
My goal was to create a minimalistic client sample for the ChannelSample to showcase how to connect to channels.

I'll open a separate issue on ☝

@baronfel that's exactly why I put that into Saturn a year or so ago re: usedefaultfiles :-)


Fix merge issue from PR #11857

There was a leftover variable declaration that was causing unused variable errors on some builds.

[approve ci freebsd]


When I edit network settings I expect to see the current data not default data

Here I added stacks granite API, then when I edit the Stacks API url  shown as the hiro api url again. I expect to see leather.granite.world there. Expected:

To reproduce.

Top right corner menu
click network
add network, any name, use leather.granite.world for the stacks API, leave rest unchanged but ad a unique bitcoin key for example 335
Then add network
top right corner menu again
click network
go to three dots and click... to "edit" next to the granite network you just added
See error

Video from 6 onwards:
https://github.com/user-attachments/assets/4e2a7cad-6920-4888-845f-471d80559ac2

Let's add an integration test when resolving

While fixing this, we should also update the title and button label to "Edit network" since it says "Add network" atm when editing a network:
https://github.com/user-attachments/assets/f0a33ba6-8882-49df-be5a-e53e87a9a51a

Related visual fix:
One of these links has a visual treatment (underline) but the other doesn't for some reason


"The system detected an overrun of a stack-based buffer in this application" error

Which registry key create this error when someone want to configure OS and how to fix it?
This window shows after hardening.

Settings: SystemSettings.exe - System Error
The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

Oof, not sure at the moment. I run it on all my Windows systems (various vendors) but no such error. But I am not on the Windows May 2020 update. Are you perhaps?
I did faced SystemsSettings.exe error myself, but that was due to corrupt files, and the error was different.
See these links:
https://answers.microsoft.com/en-us/windows/forum/all/solvederror-system-detected-an-overrun-of-a-stack/23ca258b-480a-448f-bd52-78591ea34cac
https://windowsreport.com/stack-based-buffer-application-overrun/
My advice, execute the following steps in this order.

Open a CMD window in Administrator mode
Run these commands:

** Clean up the image with unused stuff **
Dism.exe /online /Cleanup-Image /StartComponentCleanup
Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
** Verify the image files that are used **
Dism.exe /online /Cleanup-Image /RestoreHealth
** Verify system installation with the verified image **
sfc /scannow
And then do a reboot.

I could not reproduce it, and I am running the latest Windows.


Token Issue

Hi,
I am receiving the following error when trying to get userinfo with a fresh JWT token generated for the first time in a while:
2021-03-16 12:05:54,881 [66] ERROR - Error when initialising DocuSign: Error while requesting server, received a non successful HTTP code Completed with response Body: {"error":"internal_server_error","reference_id":"3b6a9d74-1fb6-48b5-aef1-d66ac4361155"}
DocuSign.eSign.Client.ApiException: Error while requesting server, received a non successful HTTP code Completed with response Body: {"error":"internal_server_error","reference_id":"3b6a9d74-1fb6-48b5-aef1-d66ac4361155"}
at DocuSign.eSign.Client.ApiClient.GetUserInfo(String accessToken)
...
Subsequent JWT retrievals seem to execute this method without issue (not caching the token my side), and this seems to re-occur if I try to get a JWT token a while later (i.e. after the expiry). Please can someone take a look at the reference id and let me know what the internal server error is to give me an idea on what I'm doing wrong (if anything) my side?
Many thanks
Matt

Hi JMatt, looks like you were getting an "EXPIRED_ACCESS_TOKEN", its strange that you say you were getting it after creating a fresh JWT assertion as this would normally happen if a previously acquired token was submitted 1 hour after creation. It looks like you managed to solve your issue though.

Hi Ben, thanks for your reply. Yeah, contrary to what I thought previously I was somehow caching the token asynchronously my side. So when it tried to get the token from DocuSign, it would keep going into the next Api call to DocuSign and fail. Subsequent requests however worked as the token came back almost immediately after the failure to be stored into my caching process asynchronously.
I'm not sure if the asynchronous functionality was being triggered by this DocuSign code (I couldn't see anything suspicious) or my custom caching code, but removing the cache resolved it so I'm looking to use the caching functionality developed by Microsoft going forward.
Thanks again for your help.


⚠ Processors has degraded performance

In 1cac96c, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 50 ms

Resolved: Processors performance has improved in dd94900.


Question about 'Enet (Doc3D + DIW) + Tnet (Doc3D + DIW)' pipeline

Hi, May I ask how do you implement the Enet (Doc3D + DIW) + Tnet (Doc3D + DIW) pipeline with the training functions? I already run through the training model with the Enet (Doc3D + DIW) based on the pretrained model , but when it comes to Tnet, I don't know how can I transfer the Enet result(netG) to Tnet, take the code as example:
def train_L_step_w(engine, batch):
        #doc3d data
        .......
        # pass the global warp net
        netG.eval()
        dg = netG(x)

how do you make sure the netG here is the trained result, should I simplely replace the pretrained pt model in /models with my Enet trained result（.pt）? and should I use the 'trainer = Engine(train_G_step_w)' and 'trainer = Engine(train_L_step_w)' at the same time?
sry that some of my questions may be dumb, looking forward to hear from u

Basically after training Enet, you should create a new training config json file and point the Enet checkpoint:
https://github.com/cvlab-stonybrook/PaperEdge/blob/main/configs/train.json#L7
https://github.com/cvlab-stonybrook/PaperEdge/blob/main/train.py#L50-L51
then in train_L_step_w the Enet is running with the weights from the previous step.
(sry there are some name confusion for Enet, Gnet, Tnet, Lnet...train and eval have different names...)
train_L_step_w is enough. Do not use 2 engines at the same time...(at least I have not tried)
(sry it took me longer and longer to read all the emails...)

thx for the reply
I see, so what I did is correct, firstly I trained the Enet model and obtained the trained Enet model(pt), then I replace the G_ckpt in train.json with the trained Enet model(pt) and train the Tnet model.
I also agree with you that we should not run the two trainers at the same time.


(SERIOUS BUG) Bulk Crap Uninstaller FAILS to detect or show up "Edge Browser" in the searches for uninstallation. W11.

(SERIOUS BUG) Bulk Crap Uninstaller FAILS to detect or show up "Edge Browser" in the searches for uninstallation thus killing the purpose behind 3rd party uninstallers (since uninstalling a program feature exists within Windows settings itself). Seen this with other system proprietary bloatware that comes out of the box with Windows.

a bit late to check now unless you're willing to re-install Edge, but does it show up if you select "Show system components" and "Show protected items"?


更新到1.17之后vs 启动变得很卡

VSCode Version: 1.17.2
OS Version:win10企业版

Steps to Reproduce:

关于vs code刚刚打开的时候Microsoft VS Code\resources\app\node_modules\vscode-ripgrep\bin文件夹下的rg.exe卡电脑cup的问题

Reproduces without extensions: Yes/No

@octref can you please help.
@qianyeyixia we don't speak the language you used. Can you provide the issue report in English please.

@qianyeyixia 重复了https://github.com/Microsoft/vscode/issues/36414
清空目录的node_modules, 然后使用cnpm i --by=npm

@dbaeumer He's saying "After upgrading to 1.17 VS Code becomes slow".
@qianyeyixia Please give @deepkolos's solution a try.

@qianyeyixia do you mean startup or the first typing in the editor ?

@dbaeumer In the repro steps he mentioned rg.exe so I guess it's https://github.com/Microsoft/vscode/issues/36414#issuecomment-337935610

OK. Thanks. Didn't see that you already closed the issue.

Not how attention, not bashful. It's the first time to enter the editor's card, and @octref says it's useless to try that. And the installation failed.

@qianyeyixia
I don't understand what you are saying.
First, are you using cnpm?
Second, did you try @deepkolos's suggestion of running cnpm i --by=npm in your workspace? If it errors out what's the error log?
Third, in the next version you can set "search.followSymlinks" to false to avoid this issue.

@octref没怎么注意看是什么错误错，我再试试吧。用翻译软件翻译出来的差太多。

@octref
<EMAIL_ADDRESS>I:\Program files\Microsoft VS Code\resources\app
`--<EMAIL_ADDRESS>extraneous
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@github:bpasero/fsevents#vscode (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! Windows_NT 10.0.15063
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "i"
npm ERR! node v6.11.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>preinstall: node build/npm/preinstall.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script 'node build/npm/preinstall.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the Code package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node build/npm/preinstall.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs Code
npm ERR!  There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR!     I:\Program files\Microsoft VS Code\resources\app\npm-debug.log
PS I:\Program files\Microsoft VS Code\resources\app>

@octref
PS I:\Program files\Microsoft VS Code\resources\app> cnpm i
\ module.js:471
throw err;
^
Error: Cannot find module 'I:\Program files\Microsoft VS Code\resources\app\build\npm\preinstall.js'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:389:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:504:3
× Install fail! Error: Run "C:\WINDOWS\system32\cmd.exe /d /s /c node build/npm/preinstall.js" error, exit code 1
Error: Run "C:\WINDOWS\system32\cmd.exe /d /s /c node build/npm/preinstall.js" error, exit code 1
at ChildProcess.proc.on.code (C:\Users\Administrator\AppData\Roaming\npm\node_modules\cnpm\node_modules\runscript\index.js:74:21)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:891:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npminstall version: 3.1.4
npminstall args: C:\Program Files\nodejs\node.exe C:\Users\Administrator\AppData\Roaming\npm\node_modules\cnpm\node_modules\npminstall\bin\install.js --china --userconfig=C:\Users\Administrator.cnpmrc --disturl=https://npm.taobao.org/mirrors/node --registry=http://registry.npm.taobao.org
PS I:\Program files\Microsoft VS Code\resources\app>


Does not seem to work consistently w/ source maps enabled in webpack

Using devtool: 'eval-source-map' or devtool: 'cheap-module-eval-source-map' causes either babel-plugin-react-transform or react-transform-hmr to not work consistently. I don't have a small repro yet, but on my project if I use devtool: 'eval' then all components are hot reloadable. If I use any source-map enabled devtool, it only appears to make the first component it sees hot reloadable.
I'll keep digging and add more information as I find it.

Some more information, if I make any change to a component file it becomes hot reloadable. It's as if something is being cached somewhere, but I cannot figure out where. If I change the file back to what it was, it is no longer hot reloadable.
The browser I use doesn't appear to matter.
I blew away my source directory including node_modules and that didn't make a difference.

Repro would definitely be useful.

So it looks like the webpack-dev-middleware output is totally different if I make a change or do not make a change to a file locally.
So to be clear, I switched from react-hot-loader to babel-plugin-react-transform. If I do not actually make a change (any change) to a file, then babel-plugin-react-transform does not appear to run on that file. If I make a change, it does. This persists even if I restart the server. If I undo the change (revert the file to what was) then babel-plugin-react-transform no longer has its effect. Something is cached somewhere. Not sure where yet.
Output when Layout.js is as it was before switching to babel-plugin-react-transform:
/***/ },
/* 270 */
/***/ function(module, exports, __webpack_require__) {

	eval("'use strict';

var React = __webpack_require__(10);
var PropTypes = React.PropTypes;

var _require = __webpack_require__(182);

var RouteHandler = _require.RouteHandler;

var GlobalHeader = __webpack_require__(271);
var GlobalFooter = __webpack_require__(412);
var Query = __webpack_require__(413);

var Layout = React.createClass({
  displayName: 'Layout',

  propTypes: {
    event: PropTypes.object,
    children: PropTypes.node
  },

  render: function render() {
    return React.createElement(
      'div',
      null,
      React.createElement(Query, null),
      React.createElement(GlobalHeader, { event: this.props.event }),
      React.createElement(
        'div',
        { className: 'content-wrapper' },
        React.createElement(
          'div',
          { className: 'content-container' },
          this.props.children || React.createElement(RouteHandler, { event: this.props.event })
        )
      ),
      React.createElement(GlobalFooter, { event: this.props.event })
    );
  }
});

module.exports = Layout;

Output after a single newline is added:
/***/ },
/* 270 */
/***/ function(module, exports, __webpack_require__) {

  eval("/* WEBPACK VAR INJECTION */(function(module) {'use strict';

var _reactTransformHmr2 = __webpack_require__(272);

var _reactTransformHmr3 = _interopRequireDefault(_reactTransformHmr2);

var _react = __webpack_require__(10);

var _reactTransformCatchErrors2 = __webpack_require__(314);

var _reactTransformCatchErrors3 = _interopRequireDefault(_reactTransformCatchErrors2);

var _redboxReact = __webpack_require__(315);

var _components = {
  _$Layout: {
    displayName: 'Layout'
  }
};

var _reactComponentWrapper = _reactTransformHmr3['default']({
  filename: '/Users/aaronjensen/Source/curadora/booking-site/js/components/Layout.js',
  components: _components,
  locals: [module],
  imports: [_react]
});

var _reactComponentWrapper2 = _reactTransformCatchErrors3['default']({
  filename: '/Users/aaronjensen/Source/curadora/booking-site/js/components/Layout.js',
  components: _components,
  locals: [],
  imports: [_react, _redboxReact]
});

function _wrapComponent(uniqueId) {
  return function (ReactClass) {
    return _reactComponentWrapper2(_reactComponentWrapper(ReactClass, uniqueId), uniqueId);
  };
}

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { 'default': obj }; }

var React = __webpack_require__(10);
var PropTypes = React.PropTypes;

var _require = __webpack_require__(182);

var RouteHandler = _require.RouteHandler;

var GlobalHeader = __webpack_require__(271);
var GlobalFooter = __webpack_require__(412);
var Query = __webpack_require__(413);

var Layout = _wrapComponent('_$Layout')(React.createClass({
  displayName: 'Layout',

  propTypes: {
    event: PropTypes.object,
    children: PropTypes.node
  },

  render: function render() {
    return React.createElement(
      'div',
      null,
      React.createElement(Query, null),
      React.createElement(GlobalHeader, { event: this.props.event }),
      React.createElement(
        'div',
        { className: 'content-wrapper' },
        React.createElement(
          'div',
          { className: 'content-container' },
          this.props.children || React.createElement(RouteHandler, { event: this.props.event })
        )
      ),
      React.createElement(GlobalFooter, { event: this.props.event })
    );
  }
}));

module.exports = Layout;
/* WEBPACK VAR INJECTION */}.call(exports, __webpack_require__(2)(module)))

Solved. We are using the babel loader with  babel?cacheDirectory
https://github.com/babel/babel-loader#options
It's supposed to take the babelrc into account. For some reason, I got into a state where the babelrc I had was synced up with old cache. Maybe it was because I changed the babelrc while webpack was running, I do not know. Either way, removing the cacheDirectory or changing my babelrc file again seems to fix it.


Checkpoint

Coverage decreased (-3.03%) to 80.902% when pulling 3cc5a626f34412198e9fb2bc39a8c564357af9d6 on apply_dashboard_function into bf8280421dae1eb92a91df097c8852aee28624f3 on master.


Update pt_BR translation

coverage: 59.829%. remained the same
when pulling af87cf41f7651d26d52a80214b854390355384c8 on andrelcmoreira:update_ptbr_translation
into 967db2d144a324b1ddd41286ba290e62cb7f2eb8 on newsboat:master.

yeah, I will take a look on them, thanks!


MudDataGrid: Fix the FilterHeaderCell visible when the Column is hidden

Description

When the filter mode is set to ColumnFilterRow and a ColumnFilterRow is hidden, the HeaderFilterCell remains visible.
I have added a check in FilterHeaderCell so it is not rendered when the column is hidden.
How Has This Been Tested?

I have added a new test and also tested visually.
Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Hi @tjscience, I suppose this fix need your review first. Can you take a look at it?
Thank you

@henon Sorry to bother, can someone look at this PR?

Looks solid. Thank you very much!


Cannot disable individual options in select

We currently cannot disable individual options in the select component:
{
  type: "select",
  key: "name",
  templateOptions: {
    label: "Name",
    theme: "custom",
    multiple: true,
    labelProp: "firstName",
    valueProp: "id",
    options: [
        {firstName: "Sarah", id: 1, disabled: true},  // I need to display this option in a disabled state
        {firstName: "Jessica", id: 2},
        {firstName: "Parker", id: 3}
    ],
    onOpen: () => {
      console.log('select is opened');
    },
    onClose: () => {
      console.log('select is closed');
    }
  }
}

@kamilkisiela if I make a PR for this, would you merge it?

@U-like YES!

@U-like @mention me there
Maybe you want to take in charge of this repository?

@kamilkisiela I really would like that, but I've never been in charge of a repository. Maybe this is an opportunity to learn how to do it.

@U-like please do! This is very important for people using Formly and Angular Material, they are both great tools!

Angular documentation specifies, that to disable a single option you need to set notAnOption flag to true.  I'd say this should be implemented here, dang I was sure I've seen it working previously with this lib...

For my use case, I did this sort of workaround:
  formlyConfig.setType({
      name: 'my-select',
      extends: 'select',
      template: `
        <md-select ng-model="model[options.key]" md-theme="{{to.theme}}">
          <md-option ng-disabled="option.notAnOption" ng-repeat="option in to.options" ng-value="option[to.valueProp || 'value']">
            {{ option[to.labelProp || 'name'] }}
          </md-option>
        </md-select>
      `
    });

And you can mark option as disabled as per angular docs: { name: '...', value: '...', notAnOption: true }


Fill in some test coverage

This adds tests for delete, head, options, and afterJSON, and covers some code paths that were previously not covered in expectHeaderToMatch and the JSON request code.

Also needs the fix from #28.

Coverage increased (+1.8%) to 92.703% when pulling 590d6e3cd7262726108036d52c66cb5a9faae9c5 on paulmelnikow:test-coverage into 11152af05a1fff3b39265bea575df5da0b8f824f on MarkHerhold:master.

Coverage increased (+1.8%) to 92.703% when pulling 590d6e3cd7262726108036d52c66cb5a9faae9c5 on paulmelnikow:test-coverage into 11152af05a1fff3b39265bea575df5da0b8f824f on MarkHerhold:master.

Coverage increased (+1.8%) to 92.703% when pulling 590d6e3cd7262726108036d52c66cb5a9faae9c5 on paulmelnikow:test-coverage into 11152af05a1fff3b39265bea575df5da0b8f824f on MarkHerhold:master.

Got :+1: offline from @cvega.


Closes #261 "none" mode for key signature.

Simple fix for mode=='none'.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (093168a) 85.65% compared to head (ec49da1) 85.65%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #262   +/-   ##
========================================
  Coverage    85.65%   85.65%
========================================
  Files           75       75
  Lines        12845    12845
========================================
  Hits         11003    11003
  Misses        1842     1842

Impacted Files
Coverage Δ

partitura/io/matchfile_utils.py
97.45% <100.00%> (ø)

partitura/utils/music.py
74.79% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


#482 - Changed name to label property

Coverage remained the same at 71.955% when pulling 6037effe934f215efef683a88f3328f32edb1c8b on MBCSDave:bugfix/use-label-in-filter-textfield into 247b6703015edb404730ef39a9c83a760a3225b8 on gregnb:master.


--abort help message needs to be updated

https://github.com/perftool-incubator/roadblock/blob/fa2c59533ba6d728130181efd73f98e2f096e4b2/roadblock.py#L711

Fixed with PR #23


Support for Wasm OCI Artifacts

What is the problem you're trying to solve
Run WASM OCI artifact workloads in Containerd
The CNCF wasm working group has been working on defining an OCI artifact that will enable storing WASM workloads that will work across Wasm and Container Runtimes.  The first version of the recommendations are published  at https://tag-runtime.cncf.io/wgs/wasm/deliverables/wasm-oci-artifact/
In the Runwasi, we see this as the way forward for small, cross platform WASM and have been using OCI images with WASM layers, https://github.com/containerd/runwasi?tab=readme-ov-file#demo-2-using-oci-images-with-custom-wasm-layers.  We would like to start to use this new artifact as tools like wasm's Warg registry will begin using it.
Describe the solution you'd like
Adding logic to containerd that will:

recognize the Wasm OCI Artifact type  application/vnd.wasm.config.v0+json
pull the wasm layers into the containerd content store
Set up a scratch container storage layer
pass information to the shim about the layers pulled

In the future, it would be nice to be able to have a plug-in system that can pre-compile/compose wasm/etc components.
Additional context
The previous attempt at this was via annotations, and the initial feedback was we needed more clarity on the naming.
The current solution in runwasi is based on https://github.com/containerd/containerd/pull/9142 and requires the shim to talk back to containerd to load the layer properly.  By adding knowledge of the Artifact type directly into container we can simplify and speed up the loading of the Wasm layers.

@jsturtevant where is application/vnd.wasm.config.v0+json defined? (in a spec somewhere?)

defined in https://tag-runtime.cncf.io/wgs/wasm/deliverables/wasm-oci-artifact/ along with other fields/types

It ends up there are no changes required to support this via the CRI api: https://github.com/containerd/runwasi/pull/661
There are a few rough edges:

CTR and a few of the option helpers do need some updates to avoid unknown image config media type application/vnd.wasm.config.v0+json
messages like  reference for unknown type: application/wasm are in the logs.

I can think of two ways to approach fixing these (both prototypes):

update container aware of the mediatypes like this one:

see https://github.com/containerd/containerd/compare/main...jsturtevant:containerd:oci-pulling

update containerd to support custom mediatypes. This is more align the approach with #10285.

See https://github.com/containerd/containerd/compare/main...jsturtevant:containerd:oci-wasm-artifact-generic

I lean toward the second


Fix Issue: #1819 Add Geoip plugin to httpserver/plugin.go

1. What does this change do, exactly?
Add geoip directive to Caddyfile for github.com/kodnaplakal/caddy-geoip
2. Please link to the relevant issues.
https://github.com/mholt/caddy/issues/1819
3. Which documentation changes (if any) need to be made because of this PR?
No
4. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I am willing to help maintain this change if there are issues with it later

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

@kodnaplakal why did you close this PR?

@elcore My fail with wrong repository. Reopened here https://github.com/mholt/caddy/pull/2066

@kodnaplakal You could have updated this PR, it was unnecessary to create a new one.


Add useProgressState hook

Description
There is a common use case when you want to provide feedback to the user that an action is happening and usually that requires defining some state as false and wrapping your method in a couple setters. This can be simplified with a hook.
async function handleFooEvent() {
    setFoo(true);
    await callFooEvent();
    setFoo(false);
}

This is duplicate code, duplicate testing, and there is room for improvement.
useProgressState is a abstraction for this pattern that accepts any method that returns a promise and will give you the same interface as use state that returns your boolean and handler.
const [fooInProgress, handleFoo] = useProgressState(fooEvent);

Fixes (issue #)

Type of change

[ ]  Patch: Bug (non-breaking change which fixes an issue)
[x]  Minor: New feature (non-breaking change which adds functionality)
[ ]  Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[ ] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish new version)

Can you provided a few example where this pattern is being use currently?
I personally would prefer to use useState myself, mostly because I can see all the possibilities of having to break out of this pattern as a project change and using a base functionality unsure the easiest understanding / maintenance in the future.

Can you provided a few example where this pattern is being use currently?
I personally would prefer to use useState myself, mostly because I can see all the possibilities of having to break out of this pattern as a project change and using a base functionality unsure the easiest understanding / maintenance in the future.

Folks use many names for their state properties so this isnt exhaustive but grepping for setLoading shows some of the uses within web, here are some of them link 1, link2, link3, link 4 (and dozens more).
I agree there is places where you want more control but the general pattern of clicking a button that triggers an async action and wanting to disable that button until it resolves is common enough to warrant a hook like this. In fact some of the examples I link are more complicated then needed because they use useState for example this calls setLoading(false); 4 times due to error handling but if they used useAsyncActionState it would have eliminated those 5 lines of code and the chance of a bug if somebody forgot to setLoading(false) in one of the conditionals.

Another point is if you have 2 different callbacks that need to toggle the loading, you will have to use this hook twice.
This will create two "loading" state. Every check for the loading state will have to contain those 2 states.

Another point is if you have 2 different callbacks that need to toggle the loading, you will have to use this hook twice.
This will create two "loading" state. Every check for the loading state will have to contain those 2 states.

is its a common case where you have different actions that toggle the same loading property? for example if you had an element on a page with a delete action and a save action I would imagine you would want the loading feedback to exist either one each button so you would need deleteLoading and saveLoading anyways. Maybe Im missing some use cases though.

is its a common case where you have different actions that toggle the same loading property? for example if you had an element on a page with a delete action and a save action I would imagine you would want the loading feedback to exist either one each button so you would need deleteLoading and saveLoading anyways. Maybe Im missing some use cases though.

Why you would need deleteLoading and saveLoading? I think most of the time we disable other buttons when an action is in progress. I think just loading is fine here no? You will toggle loading to true or increment the loading count by one if one of those actions (save/delete) happens. I'm not against this hook if a lot of folks think it's useful but I personally will rarely use it.


Makes the error messages better usable for bug tracking

If an exception occurs while centering/mapping/computing features, include the name of the variant (with pdb) with the error message. This way the error is more reproducible.
Also check for NaN output.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 9 (33.33%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 70.538%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

deeprank/generate/DataGenerator.py
3
9
33.33%

Files with Coverage Reduction
New Missed Lines
%

deeprank/generate/DataGenerator.py
1
43.91%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
2308

Relevant Lines:
3272

💛  - Coveralls


Thom/Shu trib review updates

@smnorris is the crossings_wcrp_vw ownership issue something we need to address on our end?

No, all automated testing of this repository is done against the BC/New Graph test db. I need to remove calls to WCRP refreshes from the general scripts.

No, all automated testing of this repository is done against the BC/New Graph test db. I need to remove calls to WCRP refreshes from the general scripts.

Ok, so when a PR runs correctly, then all we need to do are run the cwf jobs?

No, all automated testing of this repository is done against the BC/New Graph test db. I need to remove calls to WCRP refreshes from the general scripts.

Ok, so when a PR runs correctly, then all we need to do are run the cwf jobs?

Yes, after changes are merged. Currently the cwf workflow pulls from main branch.

No, all automated testing of this repository is done against the BC/New Graph test db. I need to remove calls to WCRP refreshes from the general scripts.

Ok, so when a PR runs correctly, then all we need to do are run the cwf jobs?

Yes, after changes are merged. Currently the cwf workflow pulls from main branch.

Automatically running the PRs on the CWF test db is an open issue currently - https://github.com/Canadian-Wildlife-Federation/bcfishpass_jobs_cwf/issues/2. It should be possible but things have not been ready to set this up till now.

Thanks, @smnorris . I'm ok with cwf workflows pulling from main branch for now. Would it be possible to resolve this conflict and merge changes today? We need some of these fixes to provide a ranked list to partners for their field season.

Thanks, @smnorris . I'm ok with cwf workflows pulling from main branch for now. Would it be possible to resolve this conflict and merge changes today? We need some of these fixes to provide a ranked list to partners for their field season.

~There is no merge conflict~ the merge conflict isn't the issue, just looking for context. Deleting records from user_modelled_crossing_fixes.csv isn't a fix I'd expect, I'd expect a change to the crossing type.
I'll merge but we need a method for providing background or a framework for tracking.

We're working on something and are close to having a framework we want to run by you, we'll let you know when it is ready.


Ipython notebook mime type media embed changes

Overview: What does this pull request change?

Motivation and Explanation: Why and how do your changes improve the library?

Links to added or changed documentation pages

Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

duplicate of #3618?


Fix typo

Fixes

Related to #590 by @TimidRobot
Description
Just a small typo, pag => page
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

While we're at it, why not make the names hyperlinks instead of a separate column?

It makes sense @dhruvkb , will do, so basically you want me to just add hyperlinks to the name and remove the last hyperlink column, right?


One click play a full attack animation & continue combo. ( 2nd try )

Follow: https://github.com/webaverse/app/pull/2804 , https://github.com/webaverse/app/pull/2804#issuecomment-1096711630 , https://github.com/webaverse/app/pull/3082

Apply the same one-click logic ( check known animation duration in update() ) as https://github.com/webaverse/app/pull/3082 to combo attacks, instead of animationEnd events.
Update to continuous combo attack animations, which compatible with this logic.
Use avatar.useAnimations.pickUpThrow.duration instead of const throwAnimationDuration.

The avatar is unable to move in street scene. You can see even the dash function is not working properly. Can't pick the sword from street scene.
https://user-images.githubusercontent.com/104460803/171660599-cf36e67a-5a1a-4263-88c7-836e5cafdb72.mp4

After switching the scene, I'm able to equip Bow from the tree house scene. The functionality is not working on the bow weapon.
https://user-images.githubusercontent.com/104460803/171660834-6b2e0d9a-b0ce-4c07-a917-97363f2e6c4f.mp4

@msm0823 Thanks for testing!
Sorry, I have not emphasised that, the one click logic is only applied to sword and silsword in this PR.
So it's correct that the bow and other weapons keep the existing behavior.

@msm0823 Thanks for testing! Sorry, I have not emphasised that, the one click logic is only applied to sword and silsword in this PR. So it's correct that the bow and other weapons keep the existing behavior.

Got it! Thanks for the clarification!


HDDS-4141. Implement Finalize command in Ozone Manager.

What changes were proposed in this pull request?
So far the PR is adding the CLI subcommand implementation, basic design idea about how the RPC requests related to finalization should look like and work, and stub implementations on the client and server side for the RPC calls.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4141
How was this patch tested?
So far the command itself is not tested, I will try to add tests to test the subcommand behaviour, and also to the RPC call implementations as those should be tested as well later on as they get implementations.

Codecov Report

Merging #1 into HDDS-3698-upgrade will decrease coverage by 0.14%.
The diff coverage is 1.29%.

@@                   Coverage Diff                   @@
##             HDDS-3698-upgrade       #1      +/-   ##
=======================================================
- Coverage                74.48%   74.33%   -0.15%
+ Complexity               10371    10363       -8
=======================================================
  Files                      991      992       +1
  Lines                    51803    51880      +77
  Branches                  4953     4960       +7
=======================================================
- Hits                     38584    38565      -19
- Misses                   10847    10939      +92
- Partials                  2372     2376       +4

Impacted Files
Coverage Δ
Complexity Δ

...hadoop/ozone/om/protocol/OzoneManagerProtocol.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

...PB/OzoneManagerProtocolClientSideTranslatorPB.java
90.09% <0.00%> (-0.28%)
76.00 <0.00> (ø)

.../java/org/apache/hadoop/ozone/om/OzoneManager.java
69.70% <0.00%> (-0.09%)
207.00 <0.00> (ø)

...java/org/apache/hadoop/ozone/admin/om/OMAdmin.java
38.09% <ø> (ø)
3.00 <0.00> (ø)

...doop/ozone/admin/om/FinalizeUpgradeSubCommand.java
1.36% <1.36%> (ø)
1.00 <1.00> (?)

.../apache/hadoop/hdds/scm/node/StaleNodeHandler.java
88.88% <0.00%> (-11.12%)
4.00% <0.00%> (ø%)

...ache/hadoop/ozone/om/codec/S3SecretValueCodec.java
90.90% <0.00%> (-9.10%)
3.00% <0.00%> (-1.00%)

...e/hadoop/ozone/recon/tasks/OMUpdateEventBatch.java
75.00% <0.00%> (-8.34%)
6.00% <0.00%> (-1.00%)

...e/commandhandler/CreatePipelineCommandHandler.java
81.25% <0.00%> (-6.25%)
8.00% <0.00%> (ø%)

...apache/hadoop/hdds/scm/block/BlockManagerImpl.java
70.17% <0.00%> (-5.27%)
20.00% <0.00%> (ø%)

... and 10 more

Continue to review full report at Codecov.

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

Thanks for working on this @fapifta. The general flow looks promising to me. Do we need a Ratis request OMFinalizeUpgradeProgressRequest? We maybe OK with doing a Read request on the leader for that.


Jenkinsfile.integration: add build number to cluster prefix

Include build number in cluster prefix for PR triggered jobs.
Signed-off-by: Kyr Shatskyy<EMAIL_ADDRESS>

retest this please

@jhesketh My changes are not picked up by pipeline because of this:
Obtained Jenkinsfile.integration from 88fa66928c34ba353566a71e20ee200c250157ce
Jenkinsfile.integration’ has been modified in an untrusted revision```

Changing the Jenkinsfile is equivalent to changing the job configuration. Only users with a certain level of trust should be allowed to do it.
Jenkins handles it that way: when changes to the Jenkinsfile are committed to a PR , Jenkins asks GitHub whether the PR author has the permission to push to the origin repository, if yes they are trusted, otherwise they are not.
Therefore there are 2 ways to handle this:
Give push access (i.e. Write permission) to the PR author on the repository in GitHub
Explain to users that changing the Jenkinsfile requires a certain level of permission in GitHub

This is stupid, because I am as admin of Jenkins cannot change this behavior and add myself as trusted, given that I don't want to have push access to that particular repo.

retest this please

Hmm, I thought anybody in the SUSE github org had those permissions. Looks like the job is currently running.

@jhesketh no, the problem is not that the job is running, the problem is that Jenkinsfile.integration is not used, correspondingly it is not tested, another issue with this, is that job started and code and the tests are running and jenkins will report that tests are passed whatever is in Jenkinsfile.integration and can merge it by mistake.

Ah, I see! I'm not sure how I trigger it with the correct JenkinsFile though?

Ah, I see! I'm not sure how I trigger it with the correct JenkinsFile though?

@jhesketh The PR should be submitted by you or anyone who is admin for suse/rookcheck repo or has write access to it.

I couldn't create a new PR from your repo because this one already exists. Instead I've pulled it into my personal fork and created one from there (https://github.com/SUSE/rookcheck/pull/165).


Get-ChildItem in Out-GridView with ANSI Escape sequences :-(

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Using for example PowerShell 7.3.0-preview.5 on Windows 10 21H1.
With PowerShell 7.1.4 it don't work, because it needs the file and directory coloring.
Input then Get-ChildItem | Out-GridView on the PowerShell in a directory with subdirectories and *-.exe-files.
Expected behavior
That a directory called "Downloads" is in the Out-GridView shown as "Downloads".
And that an executable called "program.exe" is in the Out-GridView shown as "program.exe".

Actual behavior
The directory called "Downloads" is in the Out-GridView shown as "[44;1mDownloads[0m".
And the executable called "program.exe" is in the Out-GridView shown as "[32;1mprogram.exe[0m".

Error details
there is no error

Environment data
PS D:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.3.0-preview.5
PSEdition                      Core
GitCommitId                    7.3.0-preview.5
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PS D:\>

Visuals

This is a more general issue – also happens with ls >out.txt, ls | clip,...
It seems that ls unconditionally adds the colors whenever the output is converted to string, without checking if the output actually goes to the terminal.

@MatejKafka No, if I output it to out.txt it isn't there.
But I don't know, why they are using on any point of the PowerShell Escape sequences.
If I write in C# a program with
Console.ForegroundColor=ConsoleColor.Red;
Console.Write("Hello ");
Console.ForegroundColor=ConsoleColor.Yellow;
Console.WriteLine("there!");

I can move it to Out-GridView and every point else and there are no escape sequences.
If I write in PowerShell
Write-Host -ForegroundColor "Red" "Hello " -NoNewLine ; Write-Host -ForegroundColor "Yellow" "there!"
Thats the way  https://github.com/joonro/Get-ChildItemColor works.
And Get-ChildItemColor is written in PowerShell, creates an colorizes Get-ChildItem output, and it can be output to Out-GridView without ANSO escape sequences.
So why have the current implementation of the Get-ChildItem ANSI escape sequences, when they are not needed and other implementations are possible?

@theuserbl Ah, you're right, the ls >out.txt scenario must have been fixed somewhere between -preview.2 (which I use) and -preview.5.

As for your other points, I think VT color escape sequences might be used to allow easier configuration using $PSStyle, but I'm only guessing.

Yes seems to be a bug with the PSAnsiRenderingFileInfo experimental feature. The bug does not happen when it is disabled

I believe the problem is that out-gridview is using the formatdata and not the original object data

Trying to see if this is a somewhat easy fix as this would affect any formatting that adds ANSI escape sequences and used with Out-GridView

@SteveL-MSFT this is also impacting Out-ConsoleGridView https://github.com/PowerShell/PowerShell/issues/17439. If you fix it for one it may be fixed for both.


Maybe we can set the requirement level to something

Maybe we can set the requirement level to something
'conditionally_required: if instrumented technology supports different transports and value cannot be inferred from other attributes such as network.protocol.name'
This would eliminate the concern for ports and also would require instrumentations to populate it whenever it's helpful.
Originally posted by @lmolkova in https://github.com/open-telemetry/semantic-conventions/pull/289#discussion_r1336505431

Removing from HTTP semconv stability project since HTTP semconv is already overriding network.transport to be conditionally required.

Closing, I think we've come to consensus on not adding requirement levels in the attribute registry.


Update terragrunt.hcl

Ran Plan for dir: ap-southeast-1/ec2/prod/test-ec2 workspace: default
Plan Error
running "terragrunt plan --no-color -out $PLANFILE" in "/atlantis-data/repos/neeltom92/infrastructure-aws/17/default/ap-southeast-1/ec2/prod/test-ec2": exit status 127: running "terragrunt plan --no-color -out $PLANFILE" in "/atlantis-data/repos/neeltom92/infrastructure-aws/17/default/ap-southeast-1/ec2/prod/test-ec2":
sh: terragrunt: not found


[Developer Needs Dashboard] Web Component Updates

A few things I see in the dashboard are out of date:

Declarative Shadow DOM is already implemented everywhere. So, I'm not sure it needs to be in the dashboard, if the goal is to track features that still need doing. If we want to track overall progress, consider some re-design of the dashboard so that we can see the work that is complete and track those as successes of the effort. Put DSD in that section, along with CSS Nesting, Text directionality, backdrop-filter, and popover.
Customizable built-in elements are "dead". I wouldn't even list them. At TPAC 2023 we resolved to pursue an alternative approach, which can be thought of as "Custom Attributes". That's what should probably be listed in its place.

I would encourage folks to take a look at the Web Components CG 2023 TPAC report, which provides the results of developer surveys around the most requested features related to Web Components. The top requests gathered from the community were:

Declarative Shadow DOM (shipped)
Scoped Registries
Cross-root Aria
CSS Slot Content Detection

For cross-root aria, there have been a number of proposals, but the one that folks want to see move forward is Reference Target for Cross-root ARIA. I can't stress enough how important this is to address many long-term accessibility challenges.
Beyond these features, there was huge interest at TPAC in Declarative Custom Elements, across all engine implementors and the community. On X I conducted a survey with over 400 responses, which yielded the following community interest in a declarative model for Web Components:

26.3% of respondents indicated that a declarative model is the way that Web Components should have been standardized from the beginning.
An additional 33.7% of respondents indicated that they wanted to use a declarative model for Web Components.
27% of respondents had interest and would use a declarative model for Web Components, depending on the details.
Only 12.9% of respondents had no interest in declarative Web Components.

Altogether, about 60% of all respondents were anxious to have and use a declarative API for Web Components now and about 87% of respondents were interested in some way, depending on the details of the API. Such a large community interest seems to indicate that at least exploring a potential standard is in order.

Survey Notes
I asked those who responded "maybe" or "no" to provide me with some additional explanation behind their response. This turned out to be quite interesting, indicating that some "maybe" responses were more likely to be "yes" and that some "no" responses were more like "maybe".  Furthermore, some of the "no" responses came from people who weren't Web Developers and had no interest in the Web Platform, skewing the numbers a bit. Based on these additional insights, the community signal is likely even more positive than the numbers above show.

Hi @EisenbergEffect, thanks for the feedback! We're still refining the inclusion criteria, but the initial set of features we included have both a mature-ish spec and non-tentative WPT tests (though as pointed out in #787 we should update the dashboard to reflect these criteria more clearly). I don't think Scoped Registries, Cross-root Aria, and CSS Slot Content Detection meet that bar yet.
That's not to say they aren't important for developers; we're going to regularly revisit the set of features included here and these will be strong contenders as specs and tests are developed.


How to manage multi whiteboards?

I want to save my whiteboard to a folder based on cloud storage, and read them from it when I sign in.

Hey @jearton. What you're describing is exactly what we're doing at https://plus.excalidraw.com. Try it out.


Webpack guide updates for webpack 4

What's changed, or what was fixed?

Updated the guide for webpack 4
Fixed a few wording/formatting issues

Target Live Date: 2018-02-24 (webpack 4 release)

[ ] This has been reviewed and approved by (NAME)
[ ] I have run gulp test locally and all tests pass. (I’m on windows, and it’s hard here, sorry.)
[ ] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

Please don’t merge this yet. I was unable to test some plugins with webpack 4 because they weren’t made compatible yet. Here’s what left to do:

[ ] Test the InlineChunkWebpackPlugin instructions and update them if necessary
[ ] Test the WebpackManifestPlugin instructions and update them if necessary

I’ll re-check the status of these plugins on the next week.
Feel free to review the remaining text meanwhile, it should be stable.
CC: @petele @addyosmani

Thanks for working on the updates to this guidance for webpack 4, Ivan! My first question was going to be whether we wanted to align this with the stable launch but it looks like you've already thought about that :)
I'll take a read through and do a technical review shortly

@addyosmani - please remove the DO NOT MERGE label when it's ready feel free to squash and merge yourself

OK, so the webpack ecosystem isn’t quite ready yet:

The HTMLWebpackPlugin won’t likely be updated for webpack 4 until the beginning of March: https://github.com/jantimon/html-webpack-plugin/pull/823#issuecomment-365070707. We recommend this plugin in the article, and it’s the most popular solution for doing this kind of thing, so it’s not easy to replace.

The WebpackManifestPlugin has a PR open for webpack 4, but there were no updates for the last 9 days: https://github.com/danethurber/webpack-manifest-plugin/pull/118. We also recommend this plugin in the article, and it’s popular, so no easy replacement too.

Given this, I’d delay the article update for a week or two until these plugins are properly updated. I feel like existing webpack users would also delay their migration because of these plugins, so the article outdatedness won’t be such an issue.
I’d prepare a separate PR to add a note like

This article covers optimization strategies for webpack 3. A few parts of it aren’t necessary or work slightly differently with webpack 4. We’re waiting for the webpack ecosystem to stabilize, and then we’ll update this guide.

The HTMLWebpackPlugin won’t likely be updated for webpack 4 until the beginning of March: jantimon/html-webpack-plugin#823 (comment). We recommend this plugin in the article, and it’s the most popular solution for doing this kind of thing, so it’s not easy to replace.

There's a patched fork of the project in https://github.com/jantimon/html-webpack-plugin/pull/823#issuecomment-369065177 that works with webpack 4, but I think we might want to wait for the actual upstream project to adopt this change so the fork doesn't end up being recommended for too long. Wdyt?

The WebpackManifestPlugin has a PR open for webpack 4, but there were no updates for the last 9 days: danethurber/webpack-manifest-plugin#118. We also recommend this plugin in the article, and it’s popular, so no easy replacement too.

Looks like we're waiting on some further movement to https://github.com/danethurber/webpack-manifest-plugin/pull/128

Given this, I’d delay the article update for a week or two until these plugins are properly updated. I feel like existing webpack users would also delay their migration because of these plugins, so the article outdatedness won’t be such an issue.

This sounds very reasonable to me. We can check back in a few weeks to see if the status of the above two projects has improved before landing this.

I’d prepare a separate PR to add a note like

This article covers optimization strategies for webpack 3. A few parts of it aren’t necessary or work slightly differently with webpack 4. We’re waiting for the webpack ecosystem to stabilize, and then we’ll update this guide.
👍

There's a patched fork of the project in jantimon/html-webpack-plugin#823 (comment) that works with webpack 4, but I think we might want to wait for the actual upstream project to adopt this change so the fork doesn't end up being recommended for too long. Wdyt?

Yeah! Exactly what I was thinking :–)

Looks like we're waiting on some further movement to danethurber/webpack-manifest-plugin#128

Good point, thanks! Didn’t notice there was an additional PR open

Regarding html-webpack-plugin, I talked to @jantimon, he will release a major today. If not I will probably do it
About webpack-manifest-plugin we are finalising stuff and I will make that we have at least something out by today (even if it's only a broken rc...)

@mastilver Superb, glad to hear that! I’ll update the article tomorrow then.
I’ll have to find a replacement for InlineChunkWebpackPlugin – it’s not popular, and I haven’t seen any webpack 4 updates there – but that should be rather quickly.

Resolved conflicts, proof-read the updated sections and replaced InlineChunkWebpackPlugin with InlineSourcePlugin. The latter plugin is also not upgraded yet, but there’s an PR which works: https://github.com/DustinJackson/html-webpack-inline-source-plugin/pull/38
So, right now, I’m waiting for https://github.com/DustinJackson/html-webpack-inline-source-plugin/pull/38 and https://github.com/danethurber/webpack-manifest-plugin/pull/128. Once they are merged, we’re good to merge the article.

SGTM. Looking at the latest updates on those issues, it appears we'll be waiting another short while before they get reviewed/landed.

DustinJackson/html-webpack-inline-source-plugin has been updated. @iamakulov

Excellent. It looks like we're just waiting for the memory leak issues to be addressed in https://github.com/danethurber/webpack-manifest-plugin/pull/128 now.

Yeah! Waiting for it.
If it doesn’t get fixed in a few days, I’ll merge this anyway I believe – memory leak is thing we can live with.

@addyosmani https://github.com/danethurber/webpack-manifest-plugin/pull/128 isn’t merged yet, but I’d say let’s merge this. What do you think?
I’ve also updated the training project: https://github.com/GoogleChromeLabs/webpack-training-project/pull/5

@iamakulov For confirmation, the only issue folks will run into with the manifest plugin in the current state is they might run into race conditions. It should otherwise continue to function. Is that correct?

@addyosmani Yeah, it's just a really rare race condition. I will ignore the test for webpack 4 then release
I will then try to make sure this can't happens with webpack 4

Thank you for confirming, @mastilver! ⭐

:tada: This has been pushed live to https://developers.google.com/web/


draft launchtemplate docs

1. Issue, if available:
https://github.com/awslabs/karpenter/projects/4#card-65981773
2. Description of changes:
Add a new page describing launch templates, including requirements and sample procedure.
3. Does this change impact docs?

[x] Yes, PR includes docs updates
[ ] Yes, issue opened: link to issue
[ ] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

new draft pushed and ready for review 🥳


Report nightly CI failures to the team

Based on recent issues with release-0.3 failing builds, it is needed to report nightly CI failures directly to the team. Most likely using Slack.
Started with https://github.com/konveyor/ci/pull/34
Tiers, branches, messages TBD / WIP
All nightly CI builds.

branch
CI/tier
message
note

main
upstream CI
:alarmsomething:
Link to github action detail

main
internal tier3
:alarmsomething:
Link to jenkins log

release-0.3
upstream CI
3x alarm @here
Link to github action detail

...

Reporting
Use Slack webhook, example:
$ curl -X POST -H "Content-Type: application/json" -v -d '{"test":"E2E API","branch":"release-0.3","note":"Failed run: https://github.com/konveyor/ci/actions/runs/..."}'  https://hooks.slack.com/triggers/<SECRETS>

TIER3 reporting https://github.com/konveyor/go-konveyor-tests/pull/122

Basic reporting for main&release0.3&TIER3 main was added and is working.
Feel free add a followup or reopen the issue.


Intro To Alexa for IoT - Build fails

Hi @haybnann , is it still failing? Do you have any logs or additional information to provide?

M5tack was configured and after about  3 weeks of inactivity, the device screen is blank and I can hear a clicking noise. Efforts to power on/power off and reset have no effect. Just a blank screen and a clicking noise. Any ideas on how to fix?

@maulsparks if you could in the future post support questions and not possible bugs in its own support discussion thread on https://github.com/aws-samples/aws-iot-edukit-tutorials/discussions instead of posting it as a reply in a issue that isn’t related, it helps keep things organized and easier for others in the future to find the right help.
That said, there’s nothing wrong with the device. You probably just don’t have any application loaded in your device after erasing as noted in here:  https://edukit.workshop.aws/en/getting-started/run-rainmaker.html#erasing-the-firmware-with-platformio . So the device just reboots over and over causing the speaker amplifier to power cycle on and off repeatedly. To have it stop doing that, you just need to upload one of the provided projects like in here: https://edukit.workshop.aws/en/getting-started/run-rainmaker.html


Improve caching in Dockerfile

Use Docker caching feature to speedup builds.

#112
I added a PR to improve the caching in Dockerfile. Review my pull request


Rate limiting

Consider turning on rate limiting, or at least verify that it works and can be activated easily

This is verified to be fairly simple. We have a PR we can merge, though we might end up using a different caching mechanism on production after talking with Michael.


Unsticky inline styles

This "unstickies" inline styles, so that when you type bold text, backspace to the ending edge of the bold text and start typing again the bold doesn't "stick" to the text, only when typing within it. This feels much better than before.
Recorded demo:
Live demo: https://public-mffnxzocik.now.sh
/cc @brianlovin @wmertens this should be a fix for the issues you were having!

This looks pretty cool! Do you use it in an editor that also has normal keyboard shortcuts or toolbar buttons for inline styles? While for Markdown shortcuts I think it makes perfect sense, I wonder how end users like it if they use the usual Ctrl + B.

@thibaudcolas yes, this is just a small piece in our overall editing experience—we're also working on adding an inline toolbar to trigger those inline styles.

I don't know, I would really prefer that the invisible markers become
visible again. If I type some cod and realize the e is missing, I would
have to go before the d, type de and then remove the ending d.
If instead backspacing deletes the invisible ` character, it would be
obvious how to fix the text.
On Thu, May 24, 2018 at 2:24 PM Max Stoiber<EMAIL_ADDRESS>wrote:

@mxstbr commented on this pull request.
In src/test/plugin.test.js
https://github.com/withspectrum/draft-js-markdown-plugin/pull/83#discussion_r190565962
:

         currentSelectionState = currentSelectionState.merge({

           focusOffset: 5,

           anchorOffset: 5,

         });

         expect(subject()).toBe("handled");

         expect(store.setEditorState).toHaveBeenCalled();

         newEditorState = store.setEditorState.mock.calls[0][0];

         const block = newEditorState.getCurrentContent().getLastBlock();

         const length = block.getLength();

         expect(block.getInlineStyleAt(length - 1).toJS()).toEqual([]);

         expect(block.getInlineStyleAt(length - 2).toJS()).toEqual([

           "BOLD",

         ]);

       });

I tried for like an hour to write another test, but it always has the
wrong content state (text: altered!!) and I don't know where it's coming
from or how to fix it 😢 Any clues?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/withspectrum/draft-js-markdown-plugin/pull/83#discussion_r190565962,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADWliqDpDxGuEiuVLic3Q-keKD0JYlhks5t1qZogaJpZM4ULvcP
.

Great catch, done

How about adding a right-hand border on the current range, and allowing the
cursor to be to the left or to the right of the border, even though the
border is not an actual character? Is that possible? Then you can easily
choose to add to the end or not…
On Thu, May 24, 2018 at 3:39 PM Max Stoiber<EMAIL_ADDRESS>wrote:

Great catch, done
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/withspectrum/draft-js-markdown-plugin/pull/83#issuecomment-391718013,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADWlpvZffCOrLsOzuHOK9mZoMZ4HAynks5t1rf1gaJpZM4ULvcP
.

Probably possible somehow, but again a lot more work and doesn't really have an impact on this change :wink:


Create web part of event template

Depends on #598

@SvSven  Can we assume that this is no longer blocked since it is in review?

@SvSven  Are we sure that we need an additional event folder in the pages folder for events? We talked about just solving this in the same way as with the Landing pages? E.g. create the content, add to a route and let the web see which template to use. Even if the requirement is to have all events published under the /event top level route, that could be solved by the create route? I'm worried about the extra duplication in the pages folder and that we no longer have a separation for news and "the rest" in the way they create content? Did you discuss this with someone? Am I plain wrong?

I've refactored it to use the catch-all set up we have now, but still currently using the slug similar to the news pending discussion on how we want to solve that.

@BirteThornquist This should be ready for design review now, the date and time are still missing but being worked on.

Looks good @SvSven! Two comments:

the people promo component should have an optional title
there shall not be an option to select a background color for the iFrame in the event template

@BirteThornquist There is now an optional title for the people promo and the background selector for the iframe has been removed 👍

@SvSven @BirteThornquist Very good. I set the page up below and seems like there some spacing issues on PREVIEW and website. Bigger than spacing between components. Doesnt seem to be related to missing text fields.
https://equinor.sanity.studio/desk/event;5d90217b-c428-4d38-a8bf-703f78a767bb|%2Cview%3Dpreview

I see the people promote header is not left aligned as done in Figma, but in the middle @SvSven...

Also raised as an issue in #636

@SvSven Looking good.  @BirteThornquist any final comments?

Hi @padms I think the subscribe form looks a bit messy like it is now
I think we should change the check box columns into 2 instead of 3. I also added a selection "all". Texts are floating too much together, so we'll remove the help text and rewrite the sub header instead. The error text will only show up on validation. I have updated the  Figma design.
I also noticed that the validation error text has an icon that shall not be there - only use the icon inside the text field. And the color for the error text should also be the "clear red 100".

Seems like there is not the right padding (space) after the subscribe button...? Maybe you have used float?

Just a final little detail - could the check boxes be left aligned same as the text fields? I know there is a clickbound, but could they be wrapped in a way to get them aligned?

@BirteThornquist wrong issue 😅
But I copied your feedback over to the right issue: https://github.com/equinor/energyvision/issues/590#issuecomment-989692291

Oops - sorry! Thx @SvSven

@SvSven There is something happening with the padding/alignement .... Look at the Contact and Event list in the example attached:

@BirteThornquist Should be fixed now 😬

@SvSven The alignment looks fine now! But the headers h2 have different font sizes....?

Hmm, yeah that is likely because of inconsistencies between the different templates (news, topic page, event).
I'll have a look to see what could be the best way of addressing that.

@BirteThornquist The headings for the contact list and related content should both be set to the same size as the iframe and people promotion now (size XL), which is consistent with the topic pages. We might run into this issue again when we have another look at the news template, but we'll deal with that then 😅

Great @SvSven. Looking good! I'm closing!


install man pages

Old TODO that was originally added by Tom Browder in 07d735dbf
    # TODO: For the moment rakudo doc pod files were copied
    #       from its repo to subdir doc/Programs and modified to Perl 6 pod.
    #       The rakudo install needs
    #       to (1) copy those files to its installation directory (share/pod)
    #       and (2) use Perl 5's pod2man to convert them to man pages in
    #       the installation directory (share/man).
    #
    #       Then they can be copied to doc/Programs.

Not clear what you mean here.

That was a while ago, but the TODO note was meant to suggest turning the POD text to a man page, but that was before I knew about p6doc.

So maybe close it now?

@JJ, let me take another look first...

OK

I still think we need to somehow generate *nix man pages from available pod6 and any other suitable docs available, but that whole idea is probably best left for more discussion on module and other program documentation requirements.
You may close this issue.

I am all for a Pod::To::Man module, sadly I don't know too much on how to work with Pod to generate a man page out of it. Might be an interesting thing to look at when I'm bored, though.


Generating scheduled events two weeks ahead

According to common/good practice, we generate events from a schedule up to two weeks into the future.
Note about this from @odscjames:

If an thing is published for 2 months starting 1st Aug on the 1st Aug, we get the data 2nd Aug and make events till 15th Aug, and then it's never updated again ..... won't the system never generate normalised events for the rest of Aug and Sept?

To resolve this we could:
a) Not have a restriction, and just generate all events from a schedule (but with a sensible bigger cap, for schedules with no count or endDate).
b) Not have a restriction, and just generate all events from a schedule into the database, but limit it to two weeks into the future output from our RPDE feed. (Problem: how do we know which events came from a schedule? Do we implement this restriction for everything?)
c) Re-run the NormaliseSchedulePipe on its own, ahem, schedule, every two weeks.

I was thinking about C too. Something where we generate events 30 days ahead (or something) but turn the "normalised" boolean on the raw data table into a date/time column and use it to to re-normalise things every 15 days (or something). Could maybe have the pipes return a flag so we only do that to relevant events?

@thill-odi says current practice is for publishers to regularly keep their schedule updated, so new events should get triggered by this. So nothing extra to do here, closing.


When will gdx-ai released a new version

Please ensure you have given all the following requested information in your report.
Issue details
Please provide the details of your issue
Reproduction steps/code
Please provide the steps to reproduce this issue, or even better, a SSCCE that reproduces your issue.
Version of gdx-ai and/or relevant dependencies
Please provide the version(s) affected.
Stacktrace
//Please provide the stacktrace if applicable

there is no changes since latest version.


Add SPQR Token

[x] I will not ping on Discord/Twitter/email about this pull request.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: EPbGMeTWxqVz8kh3cCH3kCz5dLGKUJvYtJdLazLkkasS
Token Name: Sestertius
Token Symbol: SPQR
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Please include website and social links to the project, new tags should be defined at the top of token list.


package HISTORY.rst

A pedantic packaging fix: probably not making a meaningful difference today but likely saving trouble in the future
packaging connectedk8s using the tooling recommended in current python packaging reveals that HISTORY.rst is not included in the sdist, and therefore not available for use by setup.py when building the wheel.
$ pip install build ; python -m build
<snipped output>
* Getting build dependencies for wheel...
Wheel is not available, disabling bdist_wheel hook
Traceback (most recent call last):
  File "/home/dch/.virtualenvs/foo/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 373, in <module>
    main()
  File "/home/dch/.virtualenvs/foo/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 357, in main
    json_out["return_val"] = hook(**hook_input["kwargs"])
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dch/.virtualenvs/foo/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 134, in get_requires_for_build_wheel
    return hook(config_settings)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/tmp/build-env-4bdqbk0w/lib/python3.12/site-packages/setuptools/build_meta.py", line 327, in get_requires_for_build_wheel
    return self._get_build_requires(config_settings, requirements=[])
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/tmp/build-env-4bdqbk0w/lib/python3.12/site-packages/setuptools/build_meta.py", line 297, in _get_build_requires
    self.run_setup()
  File "/tmp/build-env-4bdqbk0w/lib/python3.12/site-packages/setuptools/build_meta.py", line 497, in run_setup
    super().run_setup(setup_script=setup_script)
  File "/tmp/build-env-4bdqbk0w/lib/python3.12/site-packages/setuptools/build_meta.py", line 313, in run_setup
    exec(code, locals())
  File "<string>", line 45, in <module>
  File "<frozen codecs>", line 918, in open
FileNotFoundError: [Errno 2] No such file or directory: 'HISTORY.rst'

per https://github.com/pypa/setuptools/blob/08bd31115732ece3cca50bd93f338e1b90dead34/docs/userguide/miscellaneous.rst#controlling-files-in-the-distribution, setuptools includes certain files by default - eg README.md - and HISTORY.rst is not among them.
Therefore explicitly package HISTORY.rst, after which this works fine.

Thank you for your contribution! We will review the pull request and get back to you soon.

Please write the description of changes which can be perceived by customers into HISTORY.rst.

no customer-visible changes

Please fix CI issues

azdev style issues are obviously nothing to do with this pull request and it makes no sense to fix them as part of it


Fix github link on docs

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

Hi @paivagustavo! Thank you for updating the docs! Please sign the CLA so we can merge your PR =).

I've signed it @svekars! :)


Example in documentation of sfs.mono.source.point_velocity shows sound pressure of a dipole

The example in documentation of sfs.mono.source.point_velocity shows sound pressure of a dipole. See http://python.sfstoolbox.org/en/0.4.0/frequency-domain.html#sfs.mono.source.point_velocity

The docs are somehow messed up on RTD. The functions were in alphabetical order, even though they should be in the order from the source file.
I've "wiped" and re-built the docs for master and 0.4.0 on RTD. Now the order of functions is correct, but the plot images are completely mixed up ... when I build it locally, it looks fine.

If I look at http://python.sfstoolbox.org/en/0.4.0/frequency-domain.html#sfs.mono.source.point_velocity the figures are not mixed up, or do I miss something?

Indeed, now it looks OK! This may have been a caching issue on my browser (or on the server?).
AFAICT, now everything looks as expected, I think we can close this issue.


name 'AdapPool' is not defined

AdapPool is not defined in class HighFPNRetinanet

Sorry for the mistake. Fixed that.


Qt: update to 5.12.3

Issue description
https://blog.qt.io/blog/2019/02/01/qt-5-12-1-released/
Unfortunately it appears non-trivial to update, but seems like something we should tackle soon.
Has anyone looked into this, or might be in a good position to put together an upgrade?
Also thoughts on the priority this effort should have, are appreciated :).

In the meantime 5.12.3 has been released.
https://blog.qt.io/blog/2019/04/17/qt-5-12-3-released/
Simply adapting pkgs/development/libraries/qt-5/5.12/fetch.sh and running
maintainers/scripts/fetch-kde-qt.sh pkgs/development/libraries/qt-5/5.12

is not enough. Many patches do not apply anymore.

Here is a first stab at upgrading qt 5.12.0 to 5.12.3. The patches for base are adapted to apply. However, qtbase does not compile yet: it fails at the configuration step.
Qt 5.12.1 has removed the -xkbcommon_evdev flag. See c3226bd5cc6bf009d2fb3c233a09f3ef5cf618e9 and 28fd625873f9bb191cb10a2a36a1b974c6e8c97e and QTBUG-65503.
https://github.com/vandenoever/nixpkgs/commit/8bf128e075c4ee537bebd7ef366007eb994cab73
I'm stuck but perhaps you or @ttuegel have a clue how to continue.

I've opened an editable pull request here: https://github.com/NixOS/nixpkgs/pull/60119

This is done, but we need a new issue for 5.12.4 maybe?

Or perhaps 5.13.1? https://www.qt.io/blog/qt-5.13.1-released
On Mon, 09 Sep 2019 05:32:30 -0700, Milan<EMAIL_ADDRESS>wrote:

This is done, but we need a new issue for 5.12.4 maybe?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/issues/57042#issuecomment-529450899Non-text part: text/html

Either one would be great


fix: TeaserGrid use the teaser template from this addon #251893

Grid uses teaser from blocksConfig.__grid.blocksConfig.teaser and not blocksConfig.teaser
Since we override the teaser in blocksConfig, the one in blocksConfig.__grid.blocksConfig.teaser is not changed.
This ensures the Template for Teaser is coming from volto-listing-block customization and not kitconcept/volto-blocks-grid

https://github.com/kitconcept/volto-blocks-grid/blob/main/src/components/Grid/Edit.jsx#L248


Program wont open?

So I've used your program for a while now but it suddenly stopped working. I downloaded the new version, but whenever I try to open the program nothing happens (ran it as admin).
Two files are created on my desktop (where the .exe file is located) "CrashReporter.NET".dll and "Xceed.Wpf.Toolkit.dll". Do you know what could be the problem?
I've running W10 if that makes a difference.

Fixed the problem, I had a d3d9.dll file from ArchDPS on my desktop, somehow that prevents the program from running.


Cleanup of application code traces

Describe the bug
Lot of application code traces are leftover in the framework code. Specially: AbsControlModule, MMQ, Commands etc
To Reproduce
Ctrl +F
Expected behavior
We have the verified the design that will decouple the fw level code from application changes.
Additional context
ApraProduct development side effect
Would you like to work on the issue?
@Vinayak-YB

Yes I'll work on the issue


Stats per package

Is there a way to view stats per package?
For example, the marked package source can be found here<EMAIL_ADDRESS>Can I view the number of downloads as a chart or monthly hits like JS Delivr?
Example:

OR

There isn't currently a way to view downloads per package, and it's not currently on our roadmap. A few other people have mentioned it though, so if someone is up for adding this functionality I wouldn't be opposed to adding it.

I'd love to have this as well, even if it were merely in the form of raw data. #262 seems related.

I agree that stats would be nice to have. Is this data even collected at the CDN level?

Visiting this issue from Google Search.
It would be awesome to have these metrics for comparison between how many consumers download a dependency though npm and bundle it in their browser application, vs how many consumers used it directly from unpkg.


Set charge current, not working for me

HI, I'm glad you've picked up on this integration.
I have been able to pause and resume charging for a while, using node red, and it has worked perfectly.
Have missed adjusting the charging voltage :-)
To test it out, I created a script last night with:
service: zaptec.update_installation_1
data:
installation_id: xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
available_current: 12
Have tried after waiting ½ hour with 16 etc.
What happens is that I get allocated 0 A anyway.
What am I doing wrong :-)

There are a few things to test. First off all, I have deployed a new test version (0.6.0b230722), where the service is improved and renamed to zaptec.limit_current. Please test this.
If this doesn't work:
Go into Developer tools -> States and find (or filter) your entity named sensor.zaptec_installation_*. There should be four attributes like this: What do they read?
available_current: 32
available_current_phase1: 32
available_current_phase2: 32
available_current_phase3: 32

ensor.zaptec_installation_
Sorry but i'm a newbee in this, but latest bete downloaded from HACS 0.0.6b2, where do i find test version.
And,  right now i'm only have 1 phase, right now, and available_current set to 16A
Is't only work with 3phase?

I'm working on a development version, which you'll find in this repo. In order not to create confusion, I suggest you head over to the main repo https://github.com/custom-components/zaptec and add the question there to show visibility about the problem.
When that is said, the set current function is not currently working in the official version. I do have a development version I'm working on where this is fixes. I must stress that this is an development version and not at all official, so no guarantees. You can go to the readme https://github.com/sveinse/zaptec#readme, and you'll see instructions how to set it up. You MUST uninstall the zaptec version you have installed first.

Hi thanks for the reply and the development you working on. I would love to test out your versjon, so thank's for your explanation.
As mention's, the official versjon has work fine for me almost a year, but getting the possibility to set current, is a gamechanger. (then I install 32A and 3phase) :-)


Question regarding initialScrollY prop

as mentioned in the docs if i want to set a scroll position, for example
if I have a list of 50 items and want to scroll to the 30th item when the component is render
is there anything I can do for that?

I was also trying this in CodeSandbox (https://codesandbox.io/s/hungry-surf-112i3?file=/src/index.js). Doesn't seem to work (or I'm missing something) 😅

I think you guys are right, it should scroll in the y direction with the value passed.
Problem is this condition, without this it should work just fine.
https://github.com/ankeetmaini/react-infinite-scroll-component/blob/de6e954a7f9c27fe0834eb665f6224e918b6cbef/src/index.tsx#L89

@ankeetmaini
can you fix that in next release

https://codesandbox.io/s/eloquent-breeze-5vb4b?file=/src/index.js
you have to specify height

@axeljeremy7 well thanks for the response
i have tried this in my scenario but its not working in my code
I know its strange but your help will be highly appreciated
<InfiniteScroll
style={{ overflow: "hidden" }}
dataLength={
this.state.tableRows && this.state.tableRows.length
}
next={
this.state.searchValue
? () => this.searchResult_Next()
: () =>
this.fetchAlertListByFolder(
this.props.match.params.folderId,
this.state.offset,
limit
)
}
scrollableTarget="scrollableDiv"
hasMore={this.state.hasMore}
height={300}
initialScrollY={500}
useWindow={false}
              endMessage={

                  {!this.state.alertListingDisplay
                    ? NoRightsMessage
                    : this.state.tableRows.length === 0
                    ? NoRecordFound
                    : ""}

              }
              loader={

                    {" "}
                    <MDBSpinner multicolor />

              }
            >
              {this.state.tableRows.length > 0 && (
                <MDBTable
                  sortable={"false"}
                  striped
                  borderless
                  searching={"false"}
                  paging={"false"}
                >
                  <MDBTableHead columns={data.columns} />
                  <MDBTableBody
                    style={{
                      cursor: this.state.isEnableEdit
                        ? "default"
                        : "pointer",
                    }}
                    rows={data.rows}
                  />
                </MDBTable>
              )}
            </InfiniteScroll>

The initial scroll works like height of the row multiple by a number of how many rows you want to forward. The trick is to know ahead of time the height.
https://codesandbox.io/embed/eloquent-breeze-5vb4b?file=/src/index.js&codemirror=1

@axeljeremy7 i am using mdb react for table, they have pre defined height of rows
https://mdbootstrap.com/docs/react/tables/basic/#docsTabsAPI
I am doing the same thing as you described earlier, I am kinda stuck here don't know what to do
any type of help is appreciated
thanks

also facing this problem, our rows don't have a fixed height per row, it's a chat feed. Really need a way to just pass in the index number of the item in the array we want it scrolled to. ie first unread message might be item 10 in an array of 50, where the remaining 40 are after item 10 (it's in reverse mode).
so we don't want the message list to just appear scrolled to the bottom, we want it to start at message 10 so the user can scroll down to the latest message. every message has a different height, any input on how to achieve that using the index number of the message in the array would be really appreciated.

Any news on this?
@fridaystreet what did you end up doing?

@ankeetmaini any update on moving this condition
this.el.scrollHeight > this.props.initialScrollY


[SPARK-14789][SQL] Move FunctionResourceLoader into SessionState

What changes were proposed in this pull request?
Just a small refactor. It really doesn't belong to SQLContext.
How was this patch tested?
Jenkins.

@yhuai

Test build #56458 has started for PR 12554 at commit d51aaee.

Oh I just did this locally too for something else. LGTM.

Thanks! LGTM

Test build #56458 has finished for PR 12554 at commit d51aaee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56458/
Test PASSed.

Actually I merged my other PR which includes this. Can you close this now? Thanks.


More executor changes

After merging the first batch of changes related to executors (see #1510), there is a list of things to implement to finalize their design and integration with the rest of the code base:

[ ] allow dataflow to be used with executors (#1545)
[ ] remove .on() functionality from the existing 'shim' execution policies (inhibit chaining of .on() calls)
[ ] enable all existing parallel algorithms to be usable with execution policies generated by .on()
[ ] create a NUMA aware executor (run tasks on this NUMA domain)
[ ] integrate executors with hpx::vector and hpx::unordered_map to enable seamless SPMD style of execution
[ ] integrate executors with distribution policies (e.g. run tasks on this locality, etc.)

Am 23.05.2015 5:47 nachm. schrieb "Hartmut Kaiser"<EMAIL_ADDRESS>

create a NUMA aware executor (run tasks on this NUMA domain)

This will be a tough one, not only do we want to confine tasks to run on
this NUMA domain only, we also want to be able to partition a set of
tasks over different NUMA domains. This needs to be closely coordinated
with the GSoC project. I think proper resource sharing of the available
hardware resources is a mandatory pre condition to that.

integrate executors with hpx::vector and hpx::unordered_map to enable
seamless SPMD style of execution
integrate executors with distribution policies (e.g. run tasks on this
locality, etc.)

Another important aspect is to associate actions with executors.

—
Reply to this email directly or view it on GitHub.

Another important aspect is to associate actions with executors.

That's what I meant when I wrote ' integrate executors with distribution policies'

Am 23.05.2015 7:55 nachm. schrieb "Hartmut Kaiser"<EMAIL_ADDRESS>
:

Another important aspect is to associate actions with executors.

That's what I meant when I wrote ' integrate executors with distribution
policies'

Distribution policies would take care of this at the caller site indeed. A
challenge will be heterogeneous systems.
What I had in mind was choosing a executor at the callee site (for example
a component could decide where the action is run, aligned with the policy
engine for example).

—
Reply to this email directly or view it on GitHub.

What I had in mind was choosing a executor at the callee site (for example a component could decide where the action is run, aligned with the policy engine for example).

Sure, but this is not what the executor_traits are meant to be used for. They are used for selecting the proper agent at the call site.

Am 23.05.2015 11:40 nachm. schrieb "Hartmut Kaiser" <
<EMAIL_ADDRESS>

What I had in mind was choosing a executor at the callee site (for
example a component could decide where the action is run, aligned with the
policy engine for example).

Sure, but this is not what the executor_traits are meant to be used for.
They are used for selecting the proper agent at the call site.

One could think of a component as an executor. They already have a
schedule_thread  function after all. Using executor_traits for that as
well makes sense to me.

—
Reply to this email directly or view it on GitHub.

One could think of a component as an executor. They already have a schedule_thread  function after all. Using executor_traits for that as well makes sense to me.

You will have to elaborate (help). Even after thinking about it some more I was not able to make the concepts fit.

@heller I realized that we have an example demonstrating how to bind the execution of all actions of a particular component to a specified executor: https://github.com/STEllAR-GROUP/hpx/blob/master/examples/quickstart/component_with_executor.cpp
Would this be what you were looking for?

@sithhell see above, pls

It still seems very low level, but a start. What's missing is a way to
select executors on an action by action basis.

Moving this to 1.0.0.


memory leak?

I found that after I generated a psd, the vram is not released, the only way to release it is re-run the webui.
OS: windows 10
GPU: RTX 3050 8G

try pasting in code to chatgpt to find leak


Update hot-reload example to use require()

This was the only way I could get it to work, migrating from webpack 1 on a fairly simple project.
Also, seems logical since you either need to render the new reference to App, or re-require it on every render call (see https://github.com/gaearon/react-hot-loader/issues/243#issuecomment-213796910)

@jmreidy, can you confirm this?

In webpack 2 it should work with import as the accept updates the bindings.
If it doesn't work this way, it's a webpack bug.


Include ref-only packages in prebuilt report

Including ref-only prebuilts as IL in the tarball is ok because the IL can be maintained, but it's still better if we can avoid them altogether. We should include these in the prebuilt report with proper annotations for tracking purposes. (Right now, they're just removed.)

@dseefeld I'm thinking about how this affects the dashboard... would just adding an attribute to the AnnotatedUsage affect the packageversion count delta? Is that fixable? Or should I try something different like change the element name or only include it in the other (not annotated-usage.xml) files?
If an attribute is ok, another thought is that I should always include the annotation with true/false, so when/if they all go away it doesn't break the report like the test annotations.

I'm probably overthinking it and adding a RefOnlyPrebuilt="true/false" is fine. Let me know if something else would be better. 🙂

Ref-only prebuilts as IL was removed in 5.0.  Tracking these no longer applies.  Closing.


dbm-gorm-diff and dbm-generate-gorm-changelog do not behave the same

dbm-gorm-diff will use my custom Dialect and generate a changeset with my org.joda.time.DateTime columns to timestamptz
dbm-generate-gorm-changelog will write timestamp
I tried something else : writing lol when a Boolean type is used. Both commands will write a changes with lol.
So there is something weird with timestamp
ALSO
dbm-gorm-diff will generate a changeset with int4 for an Integer but dbm-generate-gorm-changelogwill generate a changeset with int
Versions :
Grails 3.1.6
database-migration-plugin 2.0-RC4
DB postgressql 9.4 with driver 9.4.1208.jre7
joda-time-plugin 2.0.0
usertype.jodatime 2.0.1

I just did a dbm-gorm-diff to a groovy file and the behaviour is the same as as dbm-generate-gorm-changelog. So it seems like the data types are changed when writing to the groovy file...

The issue is not about those command, I'll close this one and open another one.