Gulp.test build task: type errors

Hi There,
I am trying to run your seed-test project without any modification. But it's failing in test with below errors:
C:\angular2\angular2-seed-test>gulp test
[09:55:50] Using gulpfile C:\angular2\angular2-seed-test\gulpfile.js
[09:55:50] Starting 'build.test'...
app\components\about\about_spec.ts(16,19): error TS2307: Cannot find module 'ang
ular2/src/dom/dom_adapter'.
app\components\about\about_spec.ts(24,31): error TS2345: Argument of type 'typeo
f TestComponent' is not assignable to parameter of type 'Type'.
  Type 'TestComponent' is not assignable to type 'Type'.
    Property 'apply' is missing in type 'TestComponent'.
app\components\home\home_spec.ts(16,19): error TS2307: Cannot find module 'angul
ar2/src/dom/dom_adapter'.
app\components\home\home_spec.ts(23,30): error TS2345: Argument of type 'typeof
TestComponent' is not assignable to parameter of type 'Type'.
  Type 'TestComponent' is not assignable to type 'Type'.
    Property 'apply' is missing in type 'TestComponent'.
[09:55:55] TypeScript: 4 semantic errors
[09:55:55] TypeScript: emit succeeded (with errors)
[09:55:55] Finished 'build.test' after 5.2 s
[09:55:55] Starting 'karma.start'...
INFO [karma]: Karma v0.12.37 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 44.0.2403 (Windows 8.1 0.0.0)]: Connected on socket PipeNHjYqtNISFs
yASA7 with id 48809517
Chrome 44.0.2403 (Windows 8.1 0.0.0): Executed 1 of 3 SUCCESS (0 secs / 0.008 se
Chrome 44.0.2403 (Windows 8.1 0.0.0): Executed 2 of 3 SUCCESS (0 secs / 0.209 se
Chrome 44.0.2403 (Windows 8.1 0.0.0): Executed 3 of 3 SUCCESS (0 secs / 0.228 se
Chrome 44.0.2403 (Windows 8.1 0.0.0): Executed 3 of 3 SUCCESS (0.239 secs / 0.22
8 secs)
[09:56:21] Finished 'karma.start' after 26 s
[09:56:21] Starting 'test'...
[09:56:21] Finished 'test' after 36 ms

Here are the steps I followed:

Downloaded zip version of seed-test project
Ran "npm install" command
Ran "gulp serve.dev" -> works fine
Ran "gulp test" -> failed.

Could you please let me how to solve this error?
Thanks!

@ultrasonicsoft your logs say that the test are passing (Executed 3 of 3 SUCCESS).
Even though there are some TypeScript type cheching error, they are not blocking ... I have to fix that in custom types

Thanks for reply ludohenin!
Yes, log says (Executed 3 of 3 SUCCESS). but there are errors too as below:
error TS2307: Cannot find module 'ang
ular2/src/dom/dom_adapter'.
app\components\about\about_spec.ts(24,31): error TS2345: Argument of type 'typeo
f TestComponent' is not assignable to parameter of type 'Type'.
  Type 'TestComponent' is not assignable to type 'Type'.
	Property 'apply' is missing in type 'TestComponent'.
app\components\home\home_spec.ts(16,19): error TS2307: Cannot find module 'angul
ar2/src/dom/dom_adapter'.
app\components\home\home_spec.ts(23,30): error TS2345: Argument of type 'typeof
TestComponent' is not assignable to parameter of type 'Type'.
  Type 'TestComponent' is not assignable to type 'Type'.
	Property 'apply' is missing in type 'TestComponent'.
[09:55:55] TypeScript: 4 semantic errors

I am very new to karma and jasmine. Could you please let me know whether should I ignore these errors, or should I take any latest code of yours to remove these erros?
Could you please also let me know if you have any e2e test using protractor?
Thanks a lot!

As stated above, they are TypeScript errors (occured during stranspiling phase: convertion es6/es7 -> es5) and have nothing to do with jasmine and/or karma. It is also stated in the log that TypeScript: emit succeeded (with errors)
No e2e tests at the moment.

Okay. Thank you very much for your help!

This is not solved, I have changed the title and types errors have to cleared.

Hi
When I re-ran "gulp test" for second time, I got below error. Seem 3rd test is failing. I haven't change anything. I have try to pull latest code 30 mins ago and then ran "npm install" and then "gulp test".
Am I missing anything?
Please advise.
Thanks in advance!
C:\TEMP\angular2-seed-test>gulp test
[15:46:39] Using gulpfile C:\TEMP\angular2-seed-test\gulpfile.js
[15:46:39] Starting 'build.test'...
app\components\about\about_spec.ts(16,19): error TS2307: Cannot find module 'ang
ular2/src/dom/dom_adapter'.
app\components\about\about_spec.ts(24,31): error TS2345: Argument of type 'typeo
f TestComponent' is not assignable to parameter of type 'Type'.
  Type 'TestComponent' is not assignable to type 'Type'.
	Property 'apply' is missing in type 'TestComponent'.
app\components\home\home_spec.ts(16,19): error TS2307: Cannot find module 'angul
ar2/src/dom/dom_adapter'.
app\components\home\home_spec.ts(23,30): error TS2345: Argument of type 'typeof
TestComponent' is not assignable to parameter of type 'Type'.
  Type 'TestComponent' is not assignable to type 'Type'.
	Property 'apply' is missing in type 'TestComponent'.
[15:46:41] TypeScript: 4 semantic errors
[15:46:41] TypeScript: emit succeeded (with errors)
[15:46:41] Finished 'build.test' after 1.46 s
[15:46:41] Starting 'karma.start'...
INFO [karma]: Karma v0.12.37 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 29.0.1547 (Windows 7 0.0.0)]: Connected on socket PXOMZir5VVB0p3pQQ
kBA with id 98949632
WARN [web-server]: 404: /base/node_modules/systemjs/dist/system-polyfills.js
WARN [Chrome 29.0.1547 (Windows 7 0.0.0)]: Disconnected (1 times), because no me
ssage in 10000 ms.

[15:46:54] 'karma.start' errored after 13 s
[15:46:54] Error: 1
	at formatError (C:\Users\apatel2\AppData\Roaming\npm\node_modules\gulp\bin\g
ulp.js:169:10)
	at Gulp.<anonymous> (C:\Users\apatel2\AppData\Roaming\npm\node_modules\gulp\
bin\gulp.js:195:15)
	at Gulp.emit (events.js:107:17)
	at Gulp.Orchestrator._emitTaskDone (C:\TEMP\angular2-seed-test\node_modules\
gulp\node_modules\orchestrator\index.js:264:8)
	at C:\TEMP\angular2-seed-test\node_modules\gulp\node_modules\orchestrator\in
dex.js:275:23
	at finish (C:\TEMP\angular2-seed-test\node_modules\gulp\node_modules\orchest
rator\lib\runTask.js:21:8)
	at cb (C:\TEMP\angular2-seed-test\node_modules\gulp\node_modules\orchestrato
r\lib\runTask.js:29:3)
	at removeAllListeners (C:\TEMP\angular2-seed-test\node_modules\karma\lib\ser
ver.js:215:7)
	at Server.<anonymous> (C:\TEMP\angular2-seed-test\node_modules\karma\lib\ser
ver.js:226:9)
	at Server.g (events.js:199:16)

C:\TEMP\angular2-seed-test>

Strange, it works perfectly well for me.
Karma is crashing because of this WARN [web-server]: 404: /base/node_modules/systemjs/dist/system-polyfills.js. Please make sure you have npm packages installed correctly and that you have this file.

I followed below steps:

downloaded latest code (45 mins back)
ran "npm install"
ran "npm install gulp -g"
ran "gulp serve.dev"

I can see mentioned files are there.
Will you please advise me whether I should follow any different command/sequence?

Thanks!

ca you try to add { pattern: 'node_modules/systemjs/dist/*.js', included: false, watched: false } to files array in karma.conf.js ?

You are Awesome man...
Hurray!! After adding this line, my test passed.
C:\aj\angular2-seed-test>gulp test
[17:33:55] Using gulpfile C:\aj\angular2-seed-test\gulpfile.js
[17:33:55] Starting 'build.test'...
[17:33:56] Finished 'build.test' after 1.46 s
[17:33:56] Starting 'karma.start'...
INFO [karma]: Karma v0.12.37 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 29.0.1547 (Windows 7 0.0.0)]: Connected on socket T4SBKlcus8KHc-Sup
HPF with id 78401738
Chrome 29.0.1547 (Windows 7 0.0.0): Executed 1 of 3 SUCCESS (0 secs / 0.003 secs
Chrome 29.0.1547 (Windows 7 0.0.0): Executed 2 of 3 SUCCESS (0 secs / 0.052 secs
Chrome 29.0.1547 (Windows 7 0.0.0): Executed 3 of 3 SUCCESS (0 secs / 0.059 secs
Chrome 29.0.1547 (Windows 7 0.0.0): Executed 3 of 3 SUCCESS (0.062 secs / 0.059
secs)
[17:34:02] Finished 'karma.start' after 5.17 s
[17:34:02] Starting 'test'...
[17:34:02] Finished 'test' after 9.18 ms

But "gulp serve.dev" still failing. Do you want me to share any of conf file?
Could you please let me know what's wrong in my any configuration?
Thanks!

gulp serve.dev may be related to #64

I am sorry but #64 seem to be very specific developer discussion who wrote it from scratch. In my gulpfile.js I can see "transformPath" function with same definition as of #64 .
I am really not getting where to use concatination or what action item is proposed solution for the issue (where to change and what to change).
Will you please give me bit more pointers?
Thanks!

As I understood it, it should be about replacing the line :
arguments[0] = join(APP_BASE, filename);

with :
arguments[0] = APP_BASE + filename;

I think the problem is that path.join() generates backslahes on windows platform.

Hi ludohenin and aboeglin,
Thank you for your reply.
I have replaced path.join with + but it didn't work. I also tried replacing all occurrences of "join" with "+" but it seem "dist/dev" is missing when I did "+". I guess "dist/dev" is provided by "join" with backslash.
Does same gulpfile.js is working at your end on windows 8 machine?
Could you please let me know what should I try else to solve this issue?
Thanks!
Updated gulpfile.js section:
function transformPath(env) {
  var v = '?v=' + getVersion();
  return function (filepath) {
	var filename = filepath.replace('/' + PATH.dest[env].all, '') + v;
	arguments[0] = APP_BASE + '/' + filename;
	console.log(arguments[0]);
	return inject.transform.apply(inject.transform, arguments);
  };
}

"gulp serve.dev" command output is:
C:\angular2\angular2-seed-master>gulp serve.dev
[09:27:57] Using gulpfile C:\angular2\angular2-seed-master\gulpfile.js
[09:27:57] Starting 'build.dev'...
[09:27:57] Starting 'clean.dev'...
[09:27:57] Starting 'livereload'...
[09:27:57] Finished 'livereload' after 2.32 ms
[09:27:57] Finished 'clean.dev' after 33 ms
[09:27:57] Starting 'build.lib.dev'...
[09:27:57] Finished 'build.lib.dev' after 38 ms
[09:27:57] Starting 'build.app.dev'...
[09:27:57] Starting 'clean.app.dev'...
[09:27:57] Finished 'clean.app.dev' after 4.73 ms
[09:27:57] Starting 'build.js.dev'...
[09:27:59] Finished 'build.js.dev' after 1.28 s
[09:27:59] Starting 'build.assets.dev'...
[09:27:59] Finished 'build.assets.dev' after 13 ms
[09:27:59] Starting 'build.index.dev'...
[09:27:59] gulp-inject 9 files into index.html.
//dist/dev/lib/traceur-runtime.js?v=0.0.0
//dist/dev/lib/es6-module-loader-sans-promises.js?v=0.0.0
//dist/dev/lib/Reflect.js?v=0.0.0
//dist/dev/lib/system.src.js?v=0.0.0
//dist/dev/lib/angular2.dev.js?v=0.0.0
//dist/dev/lib/router.dev.js?v=0.0.0
//dist/dev/app.css?v=0.0.0
[09:27:59] Finished 'build.index.dev' after 32 ms
[09:27:59] Finished 'build.app.dev' after 1.33 s
[09:27:59] Finished 'build.dev' after 1.41 s
[09:27:59] Starting 'serve.dev'...
[09:27:59] Finished 'serve.dev' after 11 ms

Browser output:

Dist folder structure:

If your APP_BASE is / then you shouldn't add the / but just concatenate like I posted above.

Hi aboeglin,
Even with your approach I am getting same error.
Below is the function where I have replaced "join" with "+".
function transformPath(env) {
  var v = '?v=' + getVersion();
  return function (filepath) {
	var filename = filepath.replace('/' + PATH.dest[env].all, '') + v;
	arguments[0] = APP_BASE + filename;
	return inject.transform.apply(inject.transform, arguments);
  };
}

Don't know what's wrong?
Sorry to bother you much..

@ultrasonicsoft it's been fixed. Would you please try with the latest master ?

Hi ludohenin,
I am following below steps:

Download latest master zip
Unzip folder
run "npm install" command
run "gulp serve.dev" command

I got below error:

After changing "join" to "+" in below function, I get below error:
function transformPath(env) {
  var v = '?v=' + getVersion();
  return function (filepath) {
	var filename = filepath.replace('/' + PATH.dest[env].all, '') + v;
	arguments[0] = APP_BASE + filename;
	console.log();
	return inject.transform.apply(inject.transform, arguments);
  };
}

output of above command:
C:\aj\seed-master\latest>gulp serve.dev
[17:19:53] Using gulpfile C:\aj\seed-master\latest\gulpfile.js
[17:19:53] Starting 'build.dev'...
[17:19:53] Starting 'clean.dev'...
[17:19:53] Starting 'livereload'...
[17:19:53] Finished 'livereload' after 2.96 ms
[17:19:53] Finished 'clean.dev' after 39 ms
[17:19:53] Starting 'build.lib.dev'...
[17:19:53] Finished 'build.lib.dev' after 47 ms
[17:19:53] Starting 'build.app.dev'...
[17:19:53] Starting 'clean.app.dev'...
[17:19:53] Finished 'clean.app.dev' after 4.18 ms
[17:19:53] Starting 'build.js.dev'...
[17:19:54] Finished 'build.js.dev' after 1.43 s
[17:19:54] Starting 'build.assets.dev'...
[17:19:54] Finished 'build.assets.dev' after 15 ms
[17:19:54] Starting 'build.index.dev'...
[17:19:54] gulp-inject 10 files into index.html.
//lib/traceur-runtime.js?v=0.0.0
//lib/es6-module-loader-sans-promises.js?v=0.0.0
//lib/Reflect.js?v=0.0.0
//lib/system.src.js?v=0.0.0
//lib/system.config.js?v=0.0.0
//lib/angular2.dev.js?v=0.0.0
//lib/router.dev.js?v=0.0.0
//app.css?v=0.0.0
[17:19:54] Finished 'build.index.dev' after 25 ms
[17:19:54] Finished 'build.app.dev' after 1.48 s
[17:19:54] Finished 'build.dev' after 1.58 s
[17:19:54] Starting 'serve.dev'...
[17:19:54] Finished 'serve.dev' after 15 ms

Could you please let me know what's I am missing?
Thanks!

Your lib path start with double backslashes \\lib\.... That's why.

So what's should be correct path?

/dist/lib/...
/lib/...

And should that change be done across gulpfile for replacing "join" with "+" or only in "transformPath" function?

It should work as it is (I'm also on Windows plateform).Correct path is /lib/my-lib.js.
 On Tuesday, September 1, 2015 1:59 PM, ultrasonicsoft<EMAIL_ADDRESS>wrote:

So what's should be correct path?

/dist/lib/...
/lib/...And should that change be done across gulpfile for replacing "join" with "+" or only in "transformPath" function?—
Reply to this email directly or view it on GitHub.


How to specify a model in the RAI Insights dashboard constructor component using model_info_path, model_info and model_input

[Enter feedback here]
I will include feedback on how to specify yaml for the RAI Insights dashboard constructor.
I believe the RAI Insights dashboard constructor component allows model_info_path, model_info, and model_input to be specified, but there is no mention of them.
I have written a suggested modification below, which I hope you will find useful.
The following samples are assumed to be used.
https://github.com/Azure/azureml-examples/tree/main/cli/responsible-ai/cli-responsibleaidashboard-programmer-regression

Parameter name
Description
Type

model_info_path
Specify the folder where model_info.json is located
path

model_info
Describe a string in the form of "<registered model name>:<registered model version>"
string

model_input
Specifies the MLflow model
mlflow_model

There are two ways to specify models in the RAI Insights dashboard constructor component.

Specify model_info_path
Specify model_info and model_input

Specify model_info_path
model_info_path specifies the folder of model_info.json.
model_info.json has the following format.
{"id": "<registered model name>:<registered model version>"}

A sample using model_info_path is shown below.
inputs:
  my_mlflow_model_info_path:
    type: uri_folder
    path: <folder path>

.
.
.

jobs:
  create_rai_job:
    type: command
    component: azureml://registries/azureml/components/microsoft_azureml_rai_tabular_insight_constructor/versions/0.3.0
    limits:
      timeout: 120
    inputs:
      title: From YAML snippet
      task_type: regression
      model_info_path: ${{parent.inputs.my_mlflow_model_info_path}}
      train_dataset: ${{parent.inputs.my_training_data}}
      test_dataset: ${{parent.inputs.my_test_data}}
      target_column_name: ${{parent.inputs.target_column_name}}
      categorical_column_names: '["location", "style", "job title", "OS", "Employer", "IDE", "Programming language"]'

Specify model_info and model_input
A sample of specifying model_info and model_input is shown below.
inputs:
  my_mlflow_model_input:
    type: mlflow_model
    path: azureml:<registered model name>:<registered model version>

.
.
.

jobs:
  create_rai_job:
    type: command
    component: azureml://registries/azureml/components/microsoft_azureml_rai_tabular_insight_constructor/versions/0.3.0
    limits:
      timeout: 120
    inputs:
      title: From YAML snippet
      task_type: regression
      model_info: "<registered model name>:<registered model version>"
      model_input:  ${{parent.inputs.my_mlflow_model_input}}
      train_dataset: ${{parent.inputs.my_training_data}}
      test_dataset: ${{parent.inputs.my_test_data}}
      target_column_name: ${{parent.inputs.target_column_name}}
      categorical_column_names: '["location", "style", "job title", "OS", "Employer", "IDE", "Programming language"]'

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

ID: 5952b4f0-934c-290a-b1a7-3203c814537c
Version Independent ID: 4051b100-a281-723b-8de5-eeca3f9bb274
Content: Generate a Responsible AI insights with YAML and Python - Azure Machine Learning
Content Source: articles/machine-learning/how-to-responsible-ai-insights-sdk-cli.md
Service: machine-learning
Sub-service: enterprise-readiness
GitHub Login: @minthigpen
Microsoft Alias: mithigpe

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

Hi @koheina, thank you very much for your time writing the feedback. Your understanding of the usage of model_info_path vs model_info + model_input are absolutely correct.
The parameter model_info_path is provided for backward compatibility reason and we are hoping to deprecate its usage in the near future. We recommend new customers using the model_info + model_input as provided in our notebook examples to specify model input.
Thank you!

The parameter model_info_path is provided for backward compatibility reason and we are hoping to deprecate its usage in the near future.

Please don't deprecate this.
It is the only way to chain RAI jobs in a YAML defined Azure ML pipeline, as shown in the example here.
If you are hell-bent on deprecating it, then allow an additional key that loads an MLFflow model (type: mlflow_model) directly from another jobs output (such as a sweep job which returns the best performing model), instead of insisting on a registered model path. We can already use data outputs directly from previous jobs, it seems silly to not allow model outputs from other jobs directly as well.


Support environment variables to override gogs.ini

Deploying gogs via docker is a reasonably common mode of operation these days. To better support this type of deployment, it would be excellent if Gogs supported reading configuration from gogs.ini from environment variables instead (as these can be passed to docker containers easily by most orchestration systems).

Environment variable names used by the utilities in the Shell and Utilities volume of IEEE Std 1003.1-2001 consist solely of uppercase letters, digits, and the '_' (underscore)

So for compatibility I suggest to prepend the sections with __ as separator, making them uppercase and replace dots with _.
Examples:

APP_NAME=Gogs
REPOSITORY__SCRIPT_TYPE=bash
UI_ADMIN__USER_PAGING_NUM=50

these variable have to be read at start, this could happen in setting.go, doing the same as Cfg.Append

Merge thread to https://github.com/gogits/gogs/issues/3682.


Fix compatibility with React Native 0.46 final release

Updated

Cool thanks. I'm about to go to bed. Should get around to testing this at some point tomorrow.

@petejkim Does this work for you? i changed it manually but it now shows, No bundle URL present

This requires the latest metro-bundler react-native depends on (^0.7.4)
If you see messages like Cannot find module 'react-native/packager/transformer', you should do rm yarn.lock package-lock.json && rm -rf node_modules && yarn install.

Yea @petejkim It's working. Other thing now is another transform issue with babel https://github.com/facebook/react-native/issues/14866

I didn't have that issue, but I was upgrading from 0.45.1 to 0.46, I believe new project generation is broken

Nice thanks. I was getting the same issue as @iRoachie with a brand new project and 0.46.0, but things worked after I restarted the packager (with this change) and rebuilt the app.


Add 'date_part' function to PostgresModule

Fixes #206

@riccardocorbella just one small fix and we're good to go!

@jczuchnowski #311 is still open, I think that I'm blocked unless I use the version of literal that @robmwalsh asked me to revert above...

@riccardocorbella I think that's ready to go now, just need @jczuchnowski to confirm he's happy with it to merge, then we should be able to get this one in

@riccardocorbella https://github.com/zio/zio-sql/pull/317 has been merged


[BugFix] fix zero scan ranges in hdfs backend selector

What type of PR is this：

[x] bugfix
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #https://github.com/StarRocks/StarRocksTest/issues/1050
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

[FE PR Coverage Check]
:disappointed: fail : 2 / 3 (66.67%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/HDFSBackendSelector.java
2
3
66.67%
[237]

run starrocks_admit_test


PUP-4918 - Updated Red Hat logrotate and init scripts

This patch updates logrotate script and aligns it what is defined in
defaults.rb, specifically:
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/defaults.rb#L1036-L1046
and
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/defaults.rb#L1258-L1274
Because of logrotate and puppet during restart were both "fighting" for correct
file permissions, this was causing issues with SELinux. Also fixed paths which
has been incorrect for Fedora/RHEL systems (/var/log/puppetlabs vs
/var/log/puppet). It contains both now which seems to work just fine.
I am not adding logrotate scriplet for master tho as I don't know if it
supports signals. When running master under webrick one should not expect fully
working log rotation tho. Open for discussion.
As part of this patch, I am also updating Red Hat startup scripts:

RHEL6 traditional UNIX-like "reload" command was actually sending HUP signal
and therefore restarting daemon instead correct USR1
RHEL7 systemd unit was extended with "reload" command using USR1 signal

Working well on el7 :+1:

CLA signed by all contributors.

@haus does this change look appropriate?

Thank you for your contribution. There are a couple guidelines we require contributors to follow at https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md, specifically filing a JIRA ticket and updating the commit message to conform to the described format.

puppetdlog isn't supposed to be needed on known operating systems... could this be a sign that the POSIX syslog service is unavailable to us on SELinux?

@MikaelSmith sure will do the ticketing excercise once we agree this is acceptable solution :-)

Cool thanks for following up and making changes.
Finally, USR1 appears as an odd choice for reload, to me at least. It will not cause the agent to consider configuration changes at all.
In recent Debian, the rsyslog initscript has received a (non-LSB?) rotate action (corresponding to USR2 in puppet). Would something along those lines be a viable route?

Ok implemented new rotate action for sysvinit script and also changed the logrotate systemd statement to actually send USR2 signal via systemctl kill -s USR2 puppet.service instead of sending reload command. Although systemd systems usually use journald, some distros still have syslog enabled in paralel.
If there are no objections I am creating a ticket for this one.

What is the status?
Also one question, we have a report in Fedora about incorrect behavior (https://bugzilla.redhat.com/show_bug.cgi?id=1246238) and I wonder why the systemd unit in puppet upstream does leverage --no-daemonize instead of default and generally preferred forking.
I could incorporate the change into this PR if you want. Something like:
diff --git a/ext/systemd/puppet.service b/ext/systemd/puppet.service
index 7050c9f..7dec513 100644
--- a/ext/systemd/puppet.service
+++ b/ext/systemd/puppet.service
@@ -1,15 +1,15 @@
 [Unit]
 Description=Puppet agent
 Wants=basic.target
-After=basic.target network.target
+After=basic.target network.target puppetmaster.service

 [Service]
 EnvironmentFile=-/etc/sysconfig/puppetagent
 EnvironmentFile=-/etc/sysconfig/puppet
+Type=forking
-ExecStart=/opt/puppetlabs/puppet/bin/puppet agent $PUPPET_EXTRA_OPTS --no-daemonize
+ExecStart=/opt/puppetlabs/puppet/bin/puppet agent $PUPPET_EXTRA_OPTS
 KillMode=process
+PIDFile=/run/puppet/agent.pid

I have amended one additional change which is related to the incorrect log file permissions. The package should distribute the file which is being created on every agent/server restart:
diff --git a/ext/redhat/puppet.spec.erb b/ext/redhat/puppet.spec.erb
index b2a6185..7b8681a 100644
--- a/ext/redhat/puppet.spec.erb
+++ b/ext/redhat/puppet.spec.erb
@@ -181,13 +181,16 @@ echo "D /var/run/%{name} 0755 %{name} %{name} -" > \
 # Create puppet modules directory for puppet module tool
 mkdir -p %{buildroot}%{_sysconfdir}/%{name}/modules

-
 # Install a NetworkManager dispatcher script to pickup changes to
 # # /etc/resolv.conf and such (https://bugzilla.redhat.com/532085).
 mkdir -p %{buildroot}%{_sysconfdir}/NetworkManager/dispatcher.d
 cp -pr ext/puppet-nm-dispatcher \
   %{buildroot}%{_sysconfdir}/NetworkManager/dispatcher.d/98-%{name}

+# Masterhttp.log is created on server start and should be distributed
+# with correct permissions
+touch %{buildroot}%{_localstatedir}/log/puppet/masterhttp.log
+
 %files
 %defattr(-, root, root, 0755)
 %doc LICENSE README.md examples
@@ -280,6 +283,7 @@ cp -pr ext/puppet-nm-dispatcher \
 %{_sysconfdir}/puppet/environments/example_env/README.environment
 %{_mandir}/man8/puppet-ca.8.gz
 %{_mandir}/man8/puppet-master.8.gz
+%attr(660, puppet, puppet) %{_localstatedir}/log/puppet/masterhttp.log

 # Fixed uid/gid were assigned in bz 472073 (Fedora), 471918 (RHEL-5),
 # and 471919 (RHEL-4)

@haus Could you weigh in on this one please?

Aside from my -x comment, this looks good. We should ticket making the same changes on the debian side so we don't have too much drift between the two.

Ok made the same change for Debian, I guess systemd fallback is also relevant on debian systems now.

Since nobody has brought this up in writing, apparently: Are we sure that the agent service's reload action should just kick of a new round-trip to the master and catalog transaction?
Users will expect reload to actually pick up changes in configuration files. I disbelieve that this is covered after this change.

I don't follow. Here is the actual code: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/daemon.rb#L109-Lundefined
:HUP => :restart, :USR1 => :reload, :USR2 => :reopen_logs

Before the patch, on RHEL6 "reload" sent HUP and on RHEL7 this was not implemented.
With the patch, on both platforms the "reload" command sends USR1 which is, I believe, correct. Maybe I am looking on the wrong piece of code, but I have tested this and it seems to work. Please elaborate.

At the bottom of the man page it states that USR1 causes the agent to

Immediately retrieve and apply configurations from the puppet master.

There is no mention about actually reloading agent configuration. That what HUP is for.

Restart the puppet agent daemon.

I don't believe that the agent has a reload action in the sense of "re-read process configuration without terminating the service (briefly)". So HUP is the best if awkward fit.

Oh ok the :reload method name was a bit misleading. I followed the code and I can confirm what man page says. Good catch, changed it to HUP in both cases.

@haus it looks like Debian got added here. Could you give this one final check? Thanks!
@lzap Since this now also includes debian, could you please update the commit message so it's a bit clearer what's contained in the PR.

This looks reasonable to me.

@lzap Since this now also includes debian, could you please update the commit message so it's a bit clearer what's contained in the PR.

Sure! Done.
--
Later,
Lukas #lzap Zapletal


QISKit compilation fails because SymbolicValue.swift can not be found

STR:

Clone the repo
cd qiskit-sdk-swift/tutorial/
open QisSwiftPlayground.xcodeproj/
Press Play to compile the project
It fails with the following error: <unknown>:0: error: no such file or directory: '/Users/manoel/Documents/Quantum/qiskit-sdk-swift/Sources/qiskit/datastructures/SymbolicValue.swift'

To fix the issue, I set the path to SymbolicValue.swift relative to the Xcode project (instead of relative to Developer Directory) and select the above file in folder datastructures

Thanks a lot @indisoluble !!!

@manoelmarques Happy to help.


How to stitch a floor image?

I have a series of photos of cement floors or walls, how can I stitch them into a complete plan？

Start with two simple Images, e.g. x21 and x23. Use the verbose mode to understand how the stitching works. Incrementally add more images


feat: Add a description for search results

Yeah, it's only intended to be used on the index page. The description for the actual pastes should probably be set to the same description that the user themself inputs in the description box.

Sounds good!


Force email to lower case in registration and signin

When signing into Medplum, we use exact string matching for emails.  That means if someone invites<EMAIL_ADDRESS>but then the user tries to sign in as<EMAIL_ADDRESS>it won't work.
It looks like the consensus is that email addresses are effectively case insensitive (despite technically being case sensitive):

https://mailchimp.com/resources/are-email-addresses-case-sensitive/
https://verifalia.com/help/email-validations/are-email-addresses-case-sensitive
https://stackoverflow.com/questions/9807909/are-email-addresses-case-sensitive
https://www.sendinblue.com/blog/are-emails-case-sensitive/

@codyebberson  Is it possible #1960 introduced a bug that prevents users with mixed case emails from logging in?


docs: update Flow documentation

Nuclide is discontinued, so I provided some alternatives.
Also, I let the users know they need to tweak their .flowconfig to make the absolute imports work with Flow.

I don't know why the build is failing, but I'm quite confident is not related to my changes.

LGTM although I am no Flow expert. Thanks for the PR!


Why do the fs and stream tokio readers not return tokio::read::ZipEntryReader

Why is it that only the tokio::read::seek module has a ZipFileReader that returns tokio::read::ZipEntryReaders? That means that one has to wrap the entry reader(s) in tokio_util::compat::Compat to use them in a tokio context.

The trait mustn't have a blanked implementation. But you're right, the two Generic-Implementations for tokio::AsyncRead and futures::AsyncRead could overlap and therefore conflict... Is this what you meant?
Maybe a 'ZipFileReader::new_tokio' would be a better choice

My only problem with having a new_tokio() is that we'd be returning a type where the reader is Compat<R>, which means if the library user wants to reference this type, they will have to pull in tokio-util themselves (which I want to avoid if possible).
That's why my current start on converting them over use types that shadow the base implementation but wrapping Compat<R> and the calls to .compat()internally to avoid having to pull it in.

True, that import would be bad for ergonomics. We could however just export a Type without the need for a Wrapper:
´pub type TokioZipFileReader = ZipFileReader<tokio_util::Compat>;`

@mineichen I saw a notification about your suggestion to provide type aliases which I quite like. Unsure if there was a specific reason for your deletion but from just playing around with it myself with with_tokio() methods, it's actually surprisingly ergonomic.
I've written up a short explainer: https://github.com/Majored/rs-async-zip/blob/846ec137907d70f96f93d08c96277f0ec7b788d0/src/tokio/mod.rs#L6
I'm happy to settle on this unless anyone else has any suggestions.

Makes sense, except the naming might be a bit confusing? I'd expect a with_foo constructor to always take at least one argument. Maybe for_tokio would be less confusing? 🤷

They do take the reader as a single argument but I assume you're mentioning this since the module documentation links are slightly confusing? Not sure there's anything we can do about that. Maybe omitting the parentheses helps but to me, it just looks a bit aesthetically odd without them.

anyone else has any suggestions

Sorry for the confusion. I wasn't sure if I misinterpreted your post and just suggesting what you meant already...


Will there be support for<EMAIL_ADDRESS>

Currently the service is throwing an "unmet peer dependency" error, because we have chromedriver 74.0.0 instead of ^2.45.0

Shouldn't be hard to fix - unless there are incompatible changes in there... Weird how they use semver though, just following the Chrome version number. Incrementing MAJOR (73, 74, 75 etc) should mean incompatible API changes... I guess the peer dependency must accept any future version, like ">2.45"?

Was already handled by #23. Must have missed that - now merged and published!


Installation fails in colab notebook

The installation command (!pip install git+https://github.com/JohnGiorgi/DeCLUTR.git) in the colab notebook fails with:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
torchvision 0.14.1+cu116 requires torch==1.13.1, but you have torch 1.6.0 which is incompatible.
torchtext 0.14.1 requires torch==1.13.1, but you have torch 1.6.0 which is incompatible.
torchaudio 0.13.1+cu116 requires torch==1.13.1, but you have torch 1.6.0 which is incompatible.
fastai 2.7.11 requires torch<1.14,>=1.7, but you have torch 1.6.0 which is incompatible.
en-core-web-sm 3.4.1 requires spacy<3.5.0,>=3.4.0, but you have spacy 2.3.9 which is incompatible.
confection 0.0.4 requires srsly<3.0.0,>=2.4.0, but you have srsly 1.0.6 which is incompatible.
Successfully installed allennlp-1.1.0 boto3-1.26.83 botocore-1.29.83 catalogue-1.0.2 declutr-0.1.0rc1 filelock-3.0.12 jmespath-1.0.1 jsonnet-0.19.1 jsonpickle-3.0.1 overrides-3.1.0 plac-1.1.3 pytorch-metric-learning-2.0.1 s3transfer-0.6.0 sacremoses-0.0.53 sentencepiece-0.1.97 spacy-2.3.9 srsly-1.0.6 tensorboardX-2.6 thinc-7.4.6 tokenizers-0.8.1rc1 torch-1.6.0 transformers-3.0.2 validators-0.20.0

Confirming that this is a failure, the next notebook cell doesn't work:
Traceback (most recent call last):
  File "preprocess_wikitext_103.py", line 10, in <module>
    from declutr.common.util import sanitize_text
ModuleNotFoundError: No module named 'declutr'

What adjustments are needed are needed to make it work?
I haven't been able to get it to install correctly in a plain linux environment either, but I think addressing the colab notebook is a better starting point since that notebook+environment combination might 'always' be expected to be working.

Hmm, I wasn't able to reproduce this. I can open the training.ipynb notebook in colab and Runtime > Run all without issue.
More generally, that snippet you posted is not an error traceback saying declutr wasn't installed; it is just pip's dependency resolver reporting some conflicts. I might need more information to help!

The error seems to have gone away by itself. I wonder if there was a temporary problem in some remote pip repository that was fixed.
I was not able to successfully pip install git+https://github.com/JohnGiorgi/DeCLUTR.git in linux in python 3.9.6, but it worked without errors in 3.8.10 (same version as colab notebook).


Isotope definition

Define an object that represents the physical properties of one gamma-emitting radioisotope.
Include attributes:

Atomic number
Mass number
Symbol
Half life in seconds
Decay constant in seconds
List of significant gamma emission energies
List of significant gamma emission branching ratios

It would probably be worthwhile to try scraping this info from the online TOI (http://nucleardata.nuclear.lu.se/toi/)

Resolved with pull request #7 of Gamma_Analysis.


choo components

Replacement for #606. Thanks!

Some more eyes on this would be great btw! @choojs/trainspotters

Not to derail but would this make more sense as a middleware rather than shipping with core?

@ungoldman First-class support for components in the framework helps tremendously with the accessibility effort. Having both state and emit exposed without any prop juggling in userland being most notable gain, personally.

@ungoldman yep, what @jondashkyle says. Components have shown to be a requirement people have in almost every project. Being able to use them straight from core lowers the barrier, and allows us to assume people can build on top of it in every project.

I'm ok with this, but I think docs should also be updated, to reflect the use of components.

ping @tornqvist @bcomnes @toddself your input on this patch would be greatly appreciated :pray:

Merged in @tornqvist's feedback. Thinking of merging this in 24 hours, and releasing it as a pre-release. Then follow up with a proper release next week. I think it's time to move this forward.
Please do chime in if there's any problems left with the implementation. If not, we'll be able able to try it out from a pre-release soon! :grin:

🎉 🎉 🎉 🎉 🎉

v6.11.0-preview1


Issue with more than one accessory

I have 7 soundtouch loudspeakers and I am getting the following messages. How can I add more than 1 speaker?. I am including the config file. Thanks:
[4/3/2017, 12:16:24 AM] Homebridge is running on port 51737.
[4/3/2017, 12:16:24 AM] New Plug Online: Amplifier [8006A2F548A0FC1DF22B7228A55BE137171E4CEE]
[4/3/2017, 12:16:24 AM] Configuring: Amplifier
[4/3/2017, 12:16:24 AM] [Living Room Front] Ignoring device because the room name 'Bedroom Front' does not match the desired name 'Living Room Front'.
[4/3/2017, 12:16:24 AM] [Living Room Front] Ignoring device because the room name 'Kitchen' does not match the desired name 'Living Room Front'.
[4/3/2017, 12:16:24 AM] [Living Room Front] Ignoring device because the room name 'Living Room Subwoofer' does not match the desired name 'Living Room Front'.
[4/3/2017, 12:16:24 AM] [Living Room Front] Found Bose SoundTouch device: Living Room Front
[4/3/2017, 12:16:24 AM] [Bedroom Rear] Ignoring device because the room name 'Living Room Front' does not match the desired name 'Bedroom Rear'.
[4/3/2017, 12:16:24 AM] [Living Room Front] Ignoring device because the room name 'Living Room Rear' does not match the desired name 'Living Room Front'.
[4/3/2017, 12:16:24 AM] [Living Room Front] Ignoring device because the room name 'Bathroom' does not match the desired name 'Living Room Front'.
[4/3/2017, 12:16:24 AM] [Living Room Front] Ignoring device because the room name 'Bedroom Rear' does not match the desired name 'Living Room Front'.
[4/3/2017, 12:16:24 AM] [Bedroom Rear] Ignoring device because the room name 'Living Room Subwoofer' does not match the desired name 'Bedroom Rear'.
[4/3/2017, 12:16:24 AM] [Bedroom Rear] Ignoring device because the room name 'Kitchen' does not match the desired name 'Bedroom Rear'.
[4/3/2017, 12:16:24 AM] [Bedroom Rear] Ignoring device because the room name 'Living Room Rear' does not match the desired name 'Bedroom Rear'.
[4/3/2017, 12:16:24 AM] [Bedroom Rear] Ignoring device because the room name 'Bathroom' does not match the desired name 'Bedroom Rear'.
[4/3/2017, 12:16:24 AM] [Bedroom Rear] Found Bose SoundTouch device: Bedroom Rear
[4/3/2017, 12:16:24 AM] [Bedroom Rear] Ignoring device because the room name 'Bedroom Front' does not match the desired name 'Bedroom Rear'.
[4/3/2017, 12:16:24 AM] [Bedroom Front] Found Bose SoundTouch device: Bedroom Front
[4/3/2017, 12:16:24 AM] [Bedroom Front] Ignoring device because the room name 'Kitchen' does not match the desired name 'Bedroom Front'.
[4/3/2017, 12:16:24 AM] [Bedroom Front] Ignoring device because the room name 'Living Room Front' does not match the desired name 'Bedroom Front'.
[4/3/2017, 12:16:24 AM] [Bedroom Front] Ignoring device because the room name 'Living Room Subwoofer' does not match the desired name 'Bedroom Front'.
[4/3/2017, 12:16:24 AM] [Bedroom Front] Ignoring device because the room name 'Bathroom' does not match the desired name 'Bedroom Front'.
[4/3/2017, 12:16:24 AM] [Bedroom Front] Ignoring device because the room name 'Bedroom Rear' does not match the desired name 'Bedroom Front'.
[4/3/2017, 12:16:24 AM] [Living Room Subwoofer] Ignoring device because the room name 'Living Room Front' does not match the desired name 'Living Room Subwoofer'.
[4/3/2017, 12:16:24 AM] [Bedroom Front] Ignoring device because the room name 'Living Room Rear' does not match the desired name 'Bedroom Front'.
[4/3/2017, 12:16:24 AM] [Living Room Subwoofer] Ignoring device because the room name 'Kitchen' does not match the desired name 'Living Room Subwoofer'.
[4/3/2017, 12:16:24 AM] [Living Room Subwoofer] Found Bose SoundTouch device: Living Room Subwoofer
[4/3/2017, 12:16:24 AM] [Living Room Subwoofer] Ignoring device because the room name 'Bathroom' does not match the desired name 'Living Room Subwoofer'.
[4/3/2017, 12:16:24 AM] [Living Room Subwoofer] Ignoring device because the room name 'Bedroom Front' does not match the desired name 'Living Room Subwoofer'.
[4/3/2017, 12:16:24 AM] [Living Room Subwoofer] Ignoring device because the room name 'Bedroom Rear' does not match the desired name 'Living Room Subwoofer'.
[4/3/2017, 12:16:24 AM] [Living Room Subwoofer] Ignoring device because the room name 'Living Room Rear' does not match the desired name 'Living Room Subwoofer'.
[4/3/2017, 12:16:24 AM] [Bathroom] Ignoring device because the room name 'Bedroom Front' does not match the desired name 'Bathroom'.
[4/3/2017, 12:16:24 AM] [Bathroom] Ignoring device because the room name 'Kitchen' does not match the desired name 'Bathroom'.
[4/3/2017, 12:16:24 AM] [Bathroom] Ignoring device because the room name 'Living Room Subwoofer' does not match the desired name 'Bathroom'.
[4/3/2017, 12:16:24 AM] [Bathroom] Ignoring device because the room name 'Living Room Front' does not match the desired name 'Bathroom'.
[4/3/2017, 12:16:24 AM] [Living Room Rear] Ignoring device because the room name 'Living Room Front' does not match the desired name 'Living Room Rear'.
[4/3/2017, 12:16:24 AM] [Bathroom] Ignoring device because the room name 'Living Room Rear' does not match the desired name 'Bathroom'.
[4/3/2017, 12:16:24 AM] [Bathroom] Found Bose SoundTouch device: Bathroom
[4/3/2017, 12:16:24 AM] [Bathroom] Ignoring device because the room name 'Bedroom Rear' does not match the desired name 'Bathroom'.
[4/3/2017, 12:16:24 AM] [Living Room Rear] Ignoring device because the room name 'Kitchen' does not match the desired name 'Living Room Rear'.
[4/3/2017, 12:16:24 AM] [Living Room Rear] Ignoring device because the room name 'Living Room Subwoofer' does not match the desired name 'Living Room Rear'.
[4/3/2017, 12:16:24 AM] [Living Room Rear] Ignoring device because the room name 'Bedroom Front' does not match the desired name 'Living Room Rear'.
[4/3/2017, 12:16:24 AM] [Living Room Rear] Ignoring device because the room name 'Bedroom Rear' does not match the desired name 'Living Room Rear'.
[4/3/2017, 12:16:24 AM] [Living Room Rear] Found Bose SoundTouch device: Living Room Rear
[4/3/2017, 12:16:24 AM] [Living Room Rear] Ignoring device because the room name 'Bathroom' does not match the desired name 'Living Room Rear'.
[4/3/2017, 12:16:24 AM] [Kitchen] Ignoring device because the room name 'Living Room Subwoofer' does not match the desired name 'Kitchen'.
[4/3/2017, 12:16:24 AM] [Kitchen] Ignoring device because the room name 'Living Room Front' does not match the desired name 'Kitchen'.
[4/3/2017, 12:16:24 AM] [Kitchen] Ignoring device because the room name 'Bathroom' does not match the desired name 'Kitchen'.
[4/3/2017, 12:16:24 AM] [Kitchen] Ignoring device because the room name 'Bedroom Rear' does not match the desired name 'Kitchen'.
[4/3/2017, 12:16:24 AM] [Kitchen] Ignoring device because the room name 'Bedroom Front' does not match the desired name 'Kitchen'.
[4/3/2017, 12:16:24 AM] [Kitchen] Found Bose SoundTouch device: Kitchen
[4/3/2017, 12:16:24 AM] [Kitchen] Ignoring device because the room name 'Living Room Rear' does not match the desired name 'Kitchen'.
[4/3/2017, 12:16:25 AM] [Remote] Fetching Logitech Harmony activities...
[4/3/2017, 12:16:25 AM] [Remote] Fetching Logitech Harmony activities...
[4/3/2017, 12:16:26 AM] [Remote] Found activities:
PowerOff
Watch Apple TV
[4/3/2017, 12:16:26 AM] [Remote] Found activities:
Watch Smart TV
Watch TV
Watch Apple TV
{
"bridge": {
"name": "MacProJose",
"username": "FD:19:3D:E1:BE:20",
"port": 51737,
"pin": "161-41-165"
},
    "description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",

    "accessories": [{
            "accessory": "SoundTouch",
            "name": "Living Room Front",
            "room": "Living Room Front"
    }, {
            "accessory": "SoundTouch",
            "name": "Bedroom Rear",
            "room": "Bedroom Rear"
    }, {
            "accessory": "SoundTouch",
            "name": "Bedroom Front",
            "room": "Bedroom Front"
    }, {
            "accessory": "SoundTouch",
            "name": "Living Room Subwoofer",
            "room": "Living Room Subwoofer"
    }, {
            "accessory": "SoundTouch",
            "name": "Bathroom",
            "room": "Bathroom"
    }, {
            "accessory": "SoundTouch",
            "name": "Living Room Rear",
            "room": "Living Room Rear"
    }, {
            "accessory": "SoundTouch",
            "name": "Kitchen",
            "room": "Kitchen"
    }],

    "platforms": [{
            "platform": "HarmonyHub",
            "name": "Remote"
    }, {
            "platform": "Hs100"
    }]

}

It is working. Sorry for the inconvenience. By the way is there any way I can learn how to use all parameters in your plug in resets etc? Can I define groups?


usb: update manufacturer HID descriptor to bitbox.swiss

Thanks. As usual, please add a CHANGELOG entry (this time for both firmware and bootloader).
Also please bump the bootloader version to v1.0.7.

I always forget about CHANGELOG :see_no_evil:

@benma done, PTAL


Regenerate AppState client

This PR was generated using Autosynth. :rainbow:
Here's the log from Synthtool:
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir16 scripts/generate_client.sh AppState
synthtool > Wrote metadata to clients/app_state/synth.metadata.

I don't know what any of this means I just know that I need my Google
Assistant to work and not be signed up for any memberships
On Fri, Aug 16, 2019, 5:34 PM Daniel Azuma<EMAIL_ADDRESS>wrote:

Merged #2455 https://github.com/googleapis/elixir-google-api/pull/2455
into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googleapis/elixir-google-api/pull/2455?email_source=notifications&email_token=AMTDQQQW6VLEVBZ3CC7SRPLQE5BSJA5CNFSM4IMMLTI2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTDHLIBI#event-2563683333,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMTDQQTIIAO6YATDA4BSEFLQE5BSJANCNFSM4IMMLTIQ
.


[JOSS Review] Feedback on the installation proccess

There is an extra \ at the end of this command:cd petsc
python configure --download-chaco \
...
--with-petsc4py=1

Without installing exta dependencies, one need to pass -DUSE_OCC=OFF to cmake when building ngsolve

This should have been fixed.


attribute error in plotting Stack and Partition

Naming in specification has changed the property of the Stack and Partition from self.cuts to self.thresholds
This fixes the pyroot specific plotting error.

Build failed in python 2.6 only


TF-SLIM : Tensor name "InceptionV3///// not found in checkpoint files

Similar problems are in stackoverlow, however they are using flowers example with flowers_train. Using
https://github.com/tensorflow/models/tree/master/slim Fine-tuning a model from an existing checkpoint. The  moving_variance and moving_mean have both had the NotFoundError.
The following train_iamge_classifier
train_image_classifier_nx.py
--checkpoint_path=data/model/inception-v3/model.ckpt-157585
--checkpoint_exclude_scopes=InceptionV3/Logits,InceptionV3/AuxLogits/Logits
--trainable_scopes=InceptionV3/Logits,InceptionV3/AuxLogits/Logits
--model_name=inception_v3
--train_dir=data/test/train
--dataset_dir=data/test/traindata
GPU initializes and immediately produces the traceback as follows:
NotFoundError (see above for traceback): Tensor name
"InceptionV3/Mixed_7a/Branch_1/Conv2d_0b_1x7/BatchNorm/moving_variance" not
found in checkpoint files
data/model/inception-v3/model.ckpt-157585
[[Node: save/RestoreV2_304 = RestoreV2[dtypes=[DT_FLOAT],
_device="/job:localhost/replica:0/task:0/cpu:0"](_recv_save/Const_0,
save/RestoreV2_304/tensor_names,
save/RestoreV2_304/shape_and_slices)]]
[[Node: save/RestoreV2_70/_653 =
_Recvclient_terminated=false,
recv_device="/job:localhost/replica:0/task:0/gpu:0",
send_device="/job:localhost/replica:0/task:0/cpu:0",
send_device_incarnation=1,
tensor_name="edge_1621_save/RestoreV2_70",
tensor_type=DT_FLOAT,
_device="/job:localhost/replica:0/task:0/gpu:0"]]

Does this help? https://github.com/tensorflow/tensorflow/issues/4249

arg_scope is mentioned by others, however i was following the documentation
using the command line train example which has no arg scope option.
On Wed, Feb 22, 2017 at 3:57 PM, Paul Tucker<EMAIL_ADDRESS>wrote:

Does this help? #4249
https://github.com/tensorflow/tensorflow/issues/4249
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/7775#issuecomment-281800841,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXVTUP6LkI2daBztL8XAT933Dz4iqpIks5rfKEtgaJpZM4MImli
.

The problem may be due to the fact that the TF-SLIM effort focused on
Python 2.7 and I'm using 3.5 on windows. I just tried the same TF-SLIM with
TF 1.0 and many more issues, it seems few can keep up with all progress on
TF and now with TF1.0 there have been more changes making TF1.0
compatibility with TF-SLIM more challenging. It seems we need a list
stating with contrib/etc. is compatible what version of TF.
On Wed, Feb 22, 2017 at 3:57 PM, Paul Tucker<EMAIL_ADDRESS>wrote:

Does this help? #4249
https://github.com/tensorflow/tensorflow/issues/4249
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/7775#issuecomment-281800841,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXVTUP6LkI2daBztL8XAT933Dz4iqpIks5rfKEtgaJpZM4MImli
.

The checkpoints get harder to deal with as TF moves forward.  One example is we would like to add fused batch_norm to slim to speed up training but that will likely further cause issues with the checkpoint.
I am marking this item as closed as I do not think this will get resolved until we redo this and create new checkpoints.  I know it does not help you but I am sorry that you had trouble.


docs(msg): Update sample message

:pencil: Description
Update sample message in README.md
:link: Related Issues
[skip release]

:tada: This PR is included in version 2.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Getters make the component re-renders when using signals

Hi there ! Thank you for this lib, it makes a perfect combo with preact/signals.
When I use the counter example in React from the docs :
import { deepSignal } from "deepsignal";

const state = deepSignal({
	count: 0,
	get double() {
		return state.count * 2;
	},
});

function Counter() {
	return (
		<button onClick={() => (state.count += 1)}>
			{state.$count} x 2 = {state.$double}
		</button>
	);
}

the component is re-rendered when I use {state.$double}.
The same computed value doesn't make a re-render when I use it with preact directly: const double = computed(() => count.value*2).
If I use the same principe with deepsignal, it doesn't make a re-render :
get double() {
		return computed(() => state.count * 2);
},

In the docs, you wrote : deepsignal will convert getters to computed values instead of signal instances underneath.
So I am not sure what's happening here. Is it the behaviour we should expect when using the signal state.$double ?
Thanks a lot for your help !

Hi @luisherranz , thanks for your answers here and twitter !
Indeed, I tried on Stackblitz and CodeSandBox and it works too. So I was testing the lib with React and Typescript from the Vite Scaffolding template using pnpm create vite@latest.
Then I found the "issue". Vite wrap the App component in React.StrictMode :
ReactDOM.createRoot(document.getElementById("root")!).render(
  <React.StrictMode>
    <App />
  </React.StrictMode>
);

The strict mode which expects things such as render to be pure, so maybe this is why I got re-rendering.
As strict mode is only used in development, when I build the app, everything works great.
So this can be solve by removing the strict mode.
Thanks again for your help and your work !

Haha it doesn't work, I thought it was the strict mode, but it seems related to Vite HMR... but I don't know how... I'll keep you posted if I find something.


Plutus core tidier

I'll have to come back and look at this again, but in the meantime I want to see how it gets on in CI. PLEASE DON'T REVIEW IT YET.  I have no idea what's going on in hie-cabal.yaml et al, for example.  I also need to update CostModel.md because the nix incantations seem to have changed.
The plutus-core-tidy PR broke a lot of the cost model stuff because some files contain hard-coded paths which have now changed. I've fixed this and tidied things up a bit (putting the R scripts, CSV files, and JSON files all in a data directory).
I'm also wondering if I should be using data-files in plutus-core.cabal in conjuction with Paths_plutus_core to access things in a path-independent way (particularly wrt costModel.json, which we need to access at runtime).

Pre-submit checklist:

Branch

[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

If you updated any cabal files or added Haskell packages:

[ ] nix-shell shell.nix --run updateMaterialized to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[ ] nix-shell shell.nix --run fix-stylish-haskell to fix any formatting issues

If you changed any Purescript files:

[ ] nix-shell shell.nix --run fix-purty to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

Oops, thanks for fixing things. I thought I tried running most of them and they seemed to work... evidently not.


drivers: eth_sam_gmac: fix eth_sam_gmac_set_config()

Fix handling of the return value by eth_sam_gmac_set_config function.
The function is used as a backend by
net_mgmt(NET_REQUEST_ETHERNET_SET_MAC_ADDRESS, ...) to change the
interface MAC address at run time.
Tested on sam_e70_xplained board.
Fixes #42151

@arvinf


Adds ConfigurationSources for system properties and environment varia…

…bles

This intents to solve https://github.com/cfg4j/cfg4j/issues/128

:+1: :clap:


140 GB tsserver log file

VSCode Version: 1.33.1
OS Version: Windows 10 Pro x64

Steps to Reproduce: i don't know
I usually do not close Visual Studio Code leaving it in the background and use hibernation instead of turning it off or rebooting it. Today I noticed that my 250GB SSD was fully used. Looking for the reason, I found a 140 Gbyte TypeScript server log file. I don't know how this happened or if it's possible to repeat the error, but I'm sure you can limit the size of the log file.
Does this issue occur when all extensions are disabled?: can't check

Turn off logging by setting "typescript.tsserver.log": "off". Only enable logging while investigating an issue with JavaScript or TypeScript
Moving this issue upstream to continue investigating why the logs grow this large

From the logs, it looks like the directory watcher is being triggered rapidly, for example:
Info 2497 [13:50:57.66] Elapsed:: 13ms DirectoryWatcher:: Triggered with p:/my-project/node_modules/typescript/lib/lib.es2016.full.d.ts :: WatchInfo: p:/my-project/node_modules 1 Project: p:/my-project/tsconfig.json WatchType: Failed Lookup Locations
Info 2498 [13:50:57.66] DirectoryWatcher:: Triggered with p:/my-project/node_modules/typescript/lib/lib.es2016.full.d.ts :: WatchInfo: p:/my-project/node_modules 1 Project: /dev/null/inferredProject2* WatchType: Failed Lookup Locations
Info 2499 [13:50:57.71] Elapsed:: 5ms DirectoryWatcher:: Triggered with p:/my-project/node_modules/typescript/lib/lib.es2016.full.d.ts :: WatchInfo: p:/my-project/node_modules 1 Project: /dev/null/inferredProject2* WatchType: Failed Lookup Locations

Hey there 👋

I think I got the same issue where I guess this is even making my VSC taking up 50% of my CPU for some reason. It happens randomly unfortunately...

@sebas2day The problem is probably related to FSWatcher then.

I am unable to repro this any more. Please reopen if you can repro this with typescript@next and vscode latest version. Thanks


BasicAer fails when shots requested exceeds a threshold

Environment

Qiskit Terra version: 371a2bc2171c6b610c7aa56d60b51f45a0fa7bad
Python version: 3.9.10
Operating system: Arch Linux

What is happening?
The BasicAer simulator is failing when the number of shots exceeds some threshold.
How can we reproduce the issue?
from qiskit import BasicAer, QuantumCircuit

backend = BasicAer.get_backend('statevector_simulator')
circuit = QuantumCircuit(1)
circuit.x(0)
backend.run(circuit, shots=100000)

Output:
---------------------------------------------------------------------------
QiskitError                               Traceback (most recent call last)
Input In [1], in <module>
      4 circuit = QuantumCircuit(1)
      5 circuit.x(0)
----> 6 backend.run(circuit, shots=100000)

File ~/projects/qiskit-terra/qiskit/providers/basicaer/qasm_simulator.py:409, in QasmSimulatorPy.run(self, qobj, **backend_options)
    407         else:
    408             out_options[key] = backend_options[key]
--> 409     qobj = assemble(qobj, self, **out_options)
    410     qobj_options = qobj.config
    411 else:

File ~/projects/qiskit-terra/qiskit/compiler/assembler.py:172, in assemble(experiments, backend, qobj_id, qobj_header, shots, memory, max_credits, seed_simulator, qubit_lo_freq, meas_lo_freq, qubit_lo_range, meas_lo_range, schedule_los, meas_level, meas_return, meas_map, memory_slot_size, rep_time, rep_delay, parameter_binds, parametric_pulses, init_qubits, **run_config)
    170 experiments = experiments if isinstance(experiments, list) else [experiments]
    171 pulse_qobj = any(isinstance(exp, (ScheduleBlock, Schedule, Instruction)) for exp in experiments)
--> 172 qobj_id, qobj_header, run_config_common_dict = _parse_common_args(
    173     backend,
    174     qobj_id,
    175     qobj_header,
    176     shots,
    177     memory,
    178     max_credits,
    179     seed_simulator,
    180     init_qubits,
    181     rep_delay,
    182     qubit_lo_freq,
    183     meas_lo_freq,
    184     qubit_lo_range,
    185     meas_lo_range,
    186     schedule_los,
    187     pulse_qobj=pulse_qobj,
    188     **run_config,
    189 )
    191 # assemble either circuits or schedules
    192 if all(isinstance(exp, QuantumCircuit) for exp in experiments):

File ~/projects/qiskit-terra/qiskit/compiler/assembler.py:327, in _parse_common_args(backend, qobj_id, qobj_header, shots, memory, max_credits, seed_simulator, init_qubits, rep_delay, qubit_lo_freq, meas_lo_freq, qubit_lo_range, meas_lo_range, schedule_los, pulse_qobj, **run_config)
    325     raise QiskitError("Argument 'shots' should be of type 'int'")
    326 elif max_shots and max_shots < shots:
--> 327     raise QiskitError(
    328         "Number of shots specified: %s exceeds max_shots property of the "
    329         "backend: %s." % (shots, max_shots)
    330     )
    332 dynamic_reprate_enabled = getattr(backend_config, "dynamic_reprate_enabled", False)
    333 if dynamic_reprate_enabled:

QiskitError: 'Number of shots specified: 100000 exceeds max_shots property of the backend: 65536.'

What should happen?
BasicAer should not have a shot limit.
Any suggestions?
No response

BasicAer is largely just meant for testing of things that need to run on a backend within Terra, and it's not efficient at all.  If there's a large number of shots, it's really a lot better to use the full Aer, and we probably don't really want to encourage people to use BasicAer for anything more than small-scale local testing.

Re-opening because we have decided we will support increased shots in BasicAer.  Since the max_shots field of backends should be an integer, there's probably no way to make this actually infinite, but we can bump up the limit to 2**32 or so.

Is this issue still open or is someone fixing it at the moment?

It should be fixed by https://github.com/Qiskit/qiskit-terra/pull/7801. @alejomonbar please add the line "Fixes #7634" to the opening post there.


Allow to save state just before rendering

Hi, when prerendering certain applications it is sometimes important to be able to save some state on the client, for example if using React and loadable-components  in order to avoid a dom diff and a re-render of the page we must save the loader state so we can later preload all our dynamic components that were loaded when prerendering the page. Another example could be to initialize a Redux store when prerendering but have it available on the client later.
For implementing this I see two different approaches:

Let the user specify a beforeRender option that will execute the given global function just before rendering, in that global function the user is in charge of storing the data he needs in an script tag or a data attribute and to handle serialization properly.

Provide a global function beforeRender that can be configured on the client by passing a callback that returns the application state. Then this object would be serialized and stored in a new script tag or in a data-attribute (to be compliant with csp) according to an optional second parameter.

What are your thoughts? I would be glad to P.R.

I prefer option 1, though in theory you can work around it's a sense using a function that only runs if prerenderer has injected a certain variable.

I prefer the first one as well, don't quite understand what you said there though.
I was thinking on evaluating window.beforeRender just before page.content()   on Puppeteer.
I don't really want to execute some function manually on the client because in that case I would have to care about when the page is fully loaded and when the prerender happens.


Cannot build static library for OIIO v1.3 and 1.4

When trying to do _make BUILDSTATIC=1_ on oiio v1.3 and v.1.4, I get the following error messages:
oiio 1.3
'''
...
[100%] Building CXX object src/python/CMakeFiles/PyOpenImageIO.dir/py_oiio.cpp.o
Linking CXX shared library OpenImageIO.so
/usr/bin/ld: ../libOpenImageIO/libOpenImageIO.a(formatspec.cpp.o): relocation R_X86_64_32 against .bss' can not be used when making a shared object; recompile with -fPIC ../libOpenImageIO/libOpenImageIO.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [src/python/OpenImageIO.so] Error 1 make[3]: Leaving directory/tmp/oiio-RB-1.3/build/linux64'
make[2]: *** [src/python/CMakeFiles/PyOpenImageIO.dir/all] Error 2
make[2]: Leaving directory /tmp/oiio-RB-1.3/build/linux64' make[1]: *** [all] Error 2 make[1]: Leaving directory/tmp/oiio-RB-1.3/build/linux64'
make: *** [cmake] Error 2
'''
oiio 1.4
'''
...
[100%] Building CXX object src/python/CMakeFiles/PyOpenImageIO.dir/py_oiio.cpp.o
Linking CXX shared library OpenImageIO.so
/usr/bin/ld: ../libOpenImageIO/libOpenImageIO.a(formatspec.cpp.o): relocation R_X86_64_32S against std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep::_S_empty_rep_storage' can not be used when making a shared object; recompile with -fPIC ../libOpenImageIO/libOpenImageIO.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [src/python/OpenImageIO.so] Error 1 make[3]: Leaving directory/tmp/oiio-master/build/linux64'
make[2]: *** [src/python/CMakeFiles/PyOpenImageIO.dir/all] Error 2
make[2]: Leaving directory /tmp/oiio-master/build/linux64' make[1]: *** [all] Error 2 make[1]: Leaving directory/tmp/oiio-master/build/linux64'
make: *** [cmake] Error 2
'''
Now, when building without BUILDSTATIC (so, only make), oiio builds perfectly fine for both versions.
I don't know if this is a bug or an issue on my side, would really appreciate any help.
I'm on CentOS 6.5, if you need more details about my build setup, please let me know.

Is any of this still an issue in 1.5 or master?

Closing, this refers to long-ago versions.


improve docs a bit

Hmm… there's a failing test, but it fails on master to… 🤔
@jgroth Ping!

Hmm… there's a failing test, but it fails on master to…
@jgroth Ping!

Yeah I noticed. I updated some dependencies last week after a discussion I saw on Slack and it seems some where breaking. That's what you get when you merge to master and assume it should just work I guess :sweat_smile:

I reverted the latest commit on master, will look into why it was failing at a later time :slightly_smiling_face:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


WIP Add dynamic ID to BaseDataProvider

Q
A

Is bugfix?
yes

New feature?
yes

Breaks BC?
no

Tests pass?
maybe

Fixed issues
#13376

https://travis-ci.org/yiisoft/yii2/jobs/216312719

@samdark Tests pass now. (Just Travis failing to run some of them).
Side note: Could the different PHP version tests in Travis be shown as separate checks in GitHub?
That would give us more information than just "The Travis CI build failed".

No, seems we can't have all the checks separately. We're going to look into both segfaults and not created DB issues soon...

Merged with minor adjustments https://github.com/yiisoft/yii2/commit/ae7378974e19a82f7716887d2429b3ac3c3dde98. Thank you!

Creating dynamic IDs using static $counter breaks testing compatibility (Codeception).
Use-case.
We have application with restful API which uses ActiveDataProvider (extends BaseDataProvider) in Index action to support pagination.
Let's consider we have one API resource /users with pagination (see http://www.yiiframework.com/doc-2.0/guide-rest-response-formatting.html#data-serializing) and we create two test methods.

Gets all items of /users resource.
Gets all items of /users resource from the second page (query parameter per-page=2).

Since both tests run within a single process calling the first one will initialize BaseDataProvider::$counter=0 and increase it by 1. Calling of the second test will use $counter=1 and ActiveDataProvider of the /users resource will have a different ID now. So it won't accept per-page parameter because it's waiting for the dp-1-per-page.
The fact this "dynamic ID" can not be disabled is frustrating.


Implement the base class MXFusionFunction

Issue #32 and #9:
Description of changes:
Introduce the base class MXFusionFunction for the functions in MXFusion. MXFusionGluonFunction and Gaussian process Kernels are inherited from this base class. These changes enables:

Transparently copying the function class when copying the model.
Use Gaussian process kernel functions as standard functions in MXFusion.

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

Codecov Report

Merging #35 into develop will increase coverage by 1.49%.
The diff coverage is 91.27%.

@@             Coverage Diff             @@
##           develop      #35      +/-   ##
===========================================
+ Coverage    80.32%   81.82%   +1.49%
===========================================
  Files           54       55       +1
  Lines         2191     2272      +81
  Branches       432      440       +8
===========================================
+ Hits          1760     1859      +99
+ Misses         321      306      -15
+ Partials       110      107       -3

Impacted Files
Coverage Δ

mxfusion/inference/inference_parameters.py
83.19% <ø> (ø)
:arrow_up:

mxfusion/components/distributions/gp/cond_gp.py
23.46% <ø> (ø)
:arrow_up:

.../components/distributions/gp/kernels/add_kernel.py
100% <ø> (+15%)
:arrow_up:

...sion/components/distributions/gp/kernels/static.py
93.33% <ø> (ø)
:arrow_up:

mxfusion/util/testutils.py
70.27% <0%> (ø)
:arrow_up:

mxfusion/__version__.py
0% <0%> (ø)
:arrow_up:

mxfusion/components/functions/__init__.py
100% <100%> (ø)
:arrow_up:

...fusion/components/functions/function_evaluation.py
92.85% <100%> (+6.31%)
:arrow_up:

...xfusion/components/distributions/gp/kernels/rbf.py
100% <100%> (ø)
:arrow_up:

mxfusion/components/functions/gluon_func_eval.py
100% <100%> (+15.55%)
:arrow_up:

... and 9 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 f9b7c4f...a1519b1. Read the comment docs.


Adding this plugin breaks IOS

I added this plugin, and my IOS version stopped working even with no programming at all added to the controllers etc...
Removed it, IOS version works again.
I need this for my Android app, but adding it in messes up IOS.  Is there a solution?
Can this be issue be fixed in the plugin itself?

You're the first to report it, can't find a similar issue on the upstream repo either. So please share your project so we have some more info. Also please share any errors you see.

is there any code we can add into the plugin so it will add an empty file or nothing to the IOS version and not the js file that android needs?
I assume there is a way for different platforms to have different js files or something.  As I don't write plugins I have no clue, just assuming.

That's why I need to see your code and know where it crashes. What I usually do is check for an object like this to exist.

it is a large and complex app with tons of plugins.  What I did to figure out why it suddenly was not working on IOS was I removed completely recent plugins, and yours is the one that caused the issue.  The symptom is startup stuff does not fire, so my access to the local file system, which normally works crashes the app with an undefined error.  there is no code I am adding or removing, just removing or adding the NFC plugin alone breaks it.  I noticed many plugins have different files for IOS and Android.  I am thinking that might be the solution to prevent cordova from adding any code code at all from this plugin to the IOS version, does that make sense?

This is not my plugin, just trying to help here.
If I were you I'd start a new hello world app, add this plugin, and run it on iOS. If it doesn't crash it's a combination of your app and this plugin which I won't be able to assist with unless you share a project that clearly shows the problem.

That is worth a shot.  With regard to my question, is there not a way to make a plugin have a different .js for ios, if we put an empty one there, would likely eliminate the situation.

Sure, fork the plugin, add an <ios> branch to plugin.xml and add something like this. However it's easier to check if (window.nfc)..

So I wanted to look at the plugin again, and added it back, this time as the last plugin added, and no issue.  So I am now totally confused as to why removing it and putting it back in a different order, changed things.


Persisting global powershell variables across releases and environments

Like in issue #375, is it possible to define a global variable that is available to the whole release, persistent between environments and tasks? Like the variables we can define in the configuration section, but do it via code...
Thanks!

We do not support persisting variables across environments at this stage.


Export tab that works for Safari

Description
For safari users export error fixed.

Thanks for the PR! 🍰
I was curious why this was so broken and fixed it properly in #6917. Turns out we just need to pass in a Promise so that Safari still registers transient activation.


Hint text for form fields/Refactor Input Text component

What
Placeholder text disappears when a form field is navigated to. Users need additional cues / hint text whilst filling in a form field.
Where
Form fields
TODO

[ ] Provide additional cues / hint text that persists whilst filling in a form field
[ ] Add pattern to Cardigan

Background
From the Hassell Inclusion accessibility audit August 2023.
Dovetail: https://proficient-wallaby-dpwd.dovetailapp.com/insights/Need-additional-cues-for-entering-information-in-form-fields-MjtohTWntPJtuP7J1y1YJ
Miro board: https://miro.com/app/board/uXjVMjsL5YE=/

Designs for this ticket are covered in #10269 Exploration around search filters behaviour when you get to the end of a filter

I think we have 2 options here

Use the form elements developed and defined for Wellcome FRP (Funding Relationship Platform product) and have been used across many of the other products at Wellcome.

Designs in Figma
https://www.figma.com/file/6bg5Y3Y4gLXgSdVa8Da8Vy/Wellcome-design-system?type=design&node-id=1429%3A5466&mode=dev&t=ALVqWmijUaT4oAZA-1

Use the UI that is used on this page across the whole site (although I can't point you towards designs for this option)
https://account.wellcomecollection.org/u/signup?state=hKFo2SAzRk1fLW1sb2hEZlo3dWRrcU1aR0xDRElXaDBlSl9Hb6Fur3VuaXZlcnNhbC1sb2dpbqN0aWTZIGxXLThmUlFqSXQ5WWZGZzZuOGxOT3dIeklfaU9zc01Zo2NpZNkgT3lGdjJIS0E0a1E2d2lDYjFXMDU5S1NMdVg5Z1V6cWg

Option ii. is similar to what we'd previously built ourselves, but I think we reverted to a more traditional (closer to option i.) approach for simplicity a while ago. The example in the link above is actually an Auth0 hosted page, so not an input we have control over.
I think given we moved away from option ii. the obvious route for us to take is to fill out what we already have in line with option i.

AFAIK it's only the search bar (which is displayed in an array of pages but always with the same component) and the newsletter pages (the block at the bottom of pages and the one on /newsletter.

Lots in this and trying to unpack it all and make sense, apologies if I have misunderstood or missed something.
My thoughts:

Update form inputs to align with the UI with the FRP (either all together in one ticket or just the hint text field for now, however, you want to split the work)
Keep the current validation error messaging for emails
Add hint text message that guides the user
Where possible remove duplication in the UX copy, specifically between the label and hint text

I have added designs for this pattern to this Figma file
https://www.figma.com/file/juZQR2wi2BsYG8TDH6R4uk/Wellcome-Collection-–-Styles-and-Component-Library-2023?type=design&node-id=1776%3A4028&mode=dev&t=Cu6Gm9mlde1dQRlV-1
Here are some screenshots for reference

Ahh I'm sorry, I'm throwing a few more inputs in the mix.
Dates filter:

Pagination:

tbh this one is pretty self explanatory and is never empty.
Identity info changes:

These are interesting because they are different from the other two styles, I think it might be a leftover from the fact that (I think?) an agency built Identity (I think?)
Anyway, they can be aligned to. I'm unsure about the Date filter bit though? They are a separate component called "NumberInput" versus the others which are "TextInput".

Changes are in prod


Opening downloads folder in quick access doesn't take it to the very top of the list

Description
Unfortunately I am bad at explaining things, but I'll try my best. So, when you click downloads, you assume that it would take you to the very top of the list so you can get the file you just downloaded, well for some reason, it doesn't do that. I hope this makes sense, but I will attempt to provide a video to show you what I mean.
Steps To Reproduce
Apologies for the bad video quality. OBS wasn't picking up the application in Window Capture, so I had to zoom in after the fact in desktop view. I hope this can still get my point across.
https://user-images.githubusercontent.com/48143202/189501411-2dafa557-3417-4bf4-8ddc-97045c9ec1ba.mp4
Steps to fix

Always go to the very top of the list (Vertical)

After accidentally clicking the today view in video, make sure the horizontal scroll thingy goes to the very far left

Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22000.918
Windows Version
Windows 11 21H2 22000.918
Relevant Assets/Logs
debug.log
debug_fulltrust.log
I would just like to say that I edited debug_fulltrust.log just to set my username to redacted. That's the only thing I did and I just wanted to tell you.

Merging with #6186


Add support for fine-grained websocket filtering

Issue: https://github.com/aporeto-inc/aporeto/issues/1699
ℹ This PR is building on-top of API changes to elemental introduced here: https://github.com/aporeto-inc/elemental/pull/61

This PR:

⚠ Breaking change: add new method to the Session interface, PushConfig, to make it possible to retrieve the push config currently active on the session.

Note: this was done so that this callback:

has enough context to decide whether it is worth parsing the entire identifiable
be able to do fine-grain identity filtering via https://github.com/aporeto-inc/elemental/blob/master/matcher.go#L10

:fire: Remove usage of deprecated type elemental.PushFilter; replaced with the re-named equivalent elemental.PushConfig

Parse the identity filters upon receipt of a elemental.PushConfig to avoid having to parse them on each push event received by the push server

in the event that parsing fails, the socket is closed.

TODO:

[ ] test for new session method
[ ] test for verifying parsing logic on receipt of an elemental.PushConfig from connected client

[ ] happy path
[ ] error case where the parsing fails - socket should get closed

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "websocket-filtering",
    "component": "elemental",
    "pr-id": "61",
    "commit-sha": "fe1cdd68fa5787ec71e7a33771ecd34bcefe2c7d"
  },
  {
    "project": "websocket-filtering",
    "component": "bahamut",
    "pr-id": "82",
    "commit-sha": "8973cff17ff60c1940fa600393b557811878b43a"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "websocket-filtering",
    "component": "bahamut",
    "pr-id": "82",
    "commit-sha": "8973cff17ff60c1940fa600393b557811878b43a"
  },
  {
    "project": "websocket-filtering",
    "component": "elemental",
    "pr-id": "61",
    "commit-sha": "fe1cdd68fa5787ec71e7a33771ecd34bcefe2c7d"
  }
]

Update

Added ability for the 'ShouldDispatch' callee to close the socket based on the error type it returns.

If ShouldDispatch returns an error type that has the method ShouldCloseSocket() (bool, int) then it can inform whether the socket should be closed along with a code to use in the close message. This is useful in cases where it makes no sense to continue serving the client (e.g. the client configured a semantically invalid push config, for example: they used a comparator that is not yet supported/implemented).
FYI: @primalmotion

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "websocket-filtering",
    "component": "elemental",
    "pr-id": "61",
    "commit-sha": "a1aa1431ac568f5a19c9793f9226696291b4a108"
  },
  {
    "project": "websocket-filtering",
    "component": "bahamut",
    "pr-id": "82",
    "commit-sha": "26fda9ee660a1039b385e811ff7cdf4b18b37d90"
  },
  {
    "project": "websocket-filtering",
    "component": "backend",
    "pr-id": "639",
    "commit-sha": "7a8e3502b96300b6f3d982622fa49b102b3e8c99"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "websocket-filtering",
    "component": "elemental",
    "pr-id": "61",
    "commit-sha": "8f033610ca1b9e881c44f6420f3d7a45a74d2a86"
  },
  {
    "project": "websocket-filtering",
    "component": "bahamut",
    "pr-id": "82",
    "commit-sha": "26fda9ee660a1039b385e811ff7cdf4b18b37d90"
  },
  {
    "project": "websocket-filtering",
    "component": "backend",
    "pr-id": "639",
    "commit-sha": "7a8e3502b96300b6f3d982622fa49b102b3e8c99"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "websocket-filtering",
    "component": "elemental",
    "pr-id": "61",
    "commit-sha": "8f033610ca1b9e881c44f6420f3d7a45a74d2a86"
  },
  {
    "project": "websocket-filtering",
    "component": "bahamut",
    "pr-id": "82",
    "commit-sha": "26fda9ee660a1039b385e811ff7cdf4b18b37d90"
  },
  {
    "project": "websocket-filtering",
    "component": "backend",
    "pr-id": "639",
    "commit-sha": "2499382adb60ae51cbf64ee78e9c9caf1e961519"
  }
]

Update 📈

Added 100% test unit test coverage around the behavioural changes made to when a client sends a push config containing an identity filter

socket is closed if the filter cannot be parsed
socket is closed if the filter is on an undeclared identity
push config is updated as expected if the identity filter is valid

Update 📈

Added 100% test coverage for when the ShouldDispatch callback returns an error satisfying the new CloserNotifierError interface:

The error indicates that the socket should be closed
The error indicates that the socket should remain open

Update
This is ready for potentially a final review! 🙏

Patched conflicts with go.sum

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "websocket-filtering",
    "component": "bahamut",
    "pr-id": "82",
    "commit-sha": "2eb7faf5acccad56ad232749d7e5e9f752967018"
  },
  {
    "project": "websocket-filtering",
    "component": "backend",
    "pr-id": "647",
    "commit-sha": "3a78720ba3874e8898393c7e87c1053091a2ae52"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "websocket-filtering",
    "component": "bahamut",
    "pr-id": "82",
    "commit-sha": "2eb7faf5acccad56ad232749d7e5e9f752967018"
  },
  {
    "project": "websocket-filtering",
    "component": "backend",
    "pr-id": "647",
    "commit-sha": "3a78720ba3874e8898393c7e87c1053091a2ae52"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "websocket-filtering",
    "component": "bahamut",
    "pr-id": "82",
    "commit-sha": "2eb7faf5acccad56ad232749d7e5e9f752967018"
  },
  {
    "project": "websocket-filtering",
    "component": "backend",
    "pr-id": "639",
    "commit-sha": "95bb6f439318d4c116e5aa62526f052e12cd291c"
  }
]


feat(rollup): support EIP-1559 in chunk/batch encoding/decoding

Purpose or design rationale of this PR
Note that this PR can be deployed before l2geth upgrade, thus rollup-relayer can be upgraded seamlessly.
This PR obsoletes the custom TransactionData implementation, adopting l2geth's built-in transaction processing mechanisms:

The TransactionData structure is relocated from the l2geth repository to the scroll repository, ensuring backward compatibility.
adding a new column named transactions_rlp to store transactions' rlp encoding.
remove L2 watcher (to increase coverage in /rollup, can remove to another PR for clarity, and can deploy together).

Additionally, this PR excises redundant block/chunk/batch encoding/decoding, consolidating these functions within the l2geth repository.
PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

[x] feat: A new feature

Deployment tag versioning
Has tag in common/version.go been updated or have you added bump-version label to this PR?

[x] Yes

Breaking change label
Does this PR have the breaking-change label?

[x] No, this PR is not a breaking change

The coverage decrease of unit tests in /common is caused by removing code (using l2geth's implementation).

Hi,
Based on the provided information, the purpose or design rationale of this pull request (PR) appears to be:

Utilization of l2geth's built-in transaction JSON encoding/decoding: The PR moves the TransactionData structure from the l2geth repository to the current repository to ensure backward compatibility. It also adds a new column named transactions_rlp to store transactions' RLP encoding.

Reduction of redundancy: The PR removes redundant block/chunk/batch encoding/decoding implementation by utilizing the existing implementation in the l2geth repository.

Deployment timing: The PR is intended to be deployed before l2geth's upgrade, indicating a focus on timely integration and compatibility with upcoming changes.

The PR title should follow conventional commits to align with the project's commit message convention for squash merging. Depending on the specific changes made, the PR title might start with one of the following types:

feat: for new features or functionalities added
fix: for bug fixes or corrections
refactor: for code refactoring without changing its external behavior
chore: for changes related to build processes, tooling, or documentation
docs: for documentation updates
style: for code style changes that do not affect the code's functionality

The actual PR title should provide a concise summary of the changes made and may include additional information relevant to the context of the PR.

Same reason as https://github.com/scroll-tech/go-ethereum/pull/622.


Release Candidate 2024-10-25

New terms added:

ID
Label

OBI:0003683
Illumina HiSeq Series Instrument

OBI:0003684
Illumina NextSeq Series Instrument

OBI:0003685
Illumina NovaSeq Series Instrument

Discussed on the OBI developer call 2024-10-28: Looks good to us. We'll wait a few more days for the normal one-week review window for a release candidate.


Timestamp on statuses

Add timestamps on the web worker statuses to understand a bit more what takes time (fetching, indexing)

Skipping for now


how to add CDS feature  to gft file?

how to add CDS feature  to gft file?

Thank you for your interest in TAGADA.
For identifying CDS we usually use TransDecoder but it's not currently included in the pipeline. Would be nice for a future version though.
Best,
Cervin


Add function to standardize data

This is more of a data cleaning task.

Questions to consider:

Does the same patient occur more than once in the data set?
Do the same values appear with a minor difference, such as date?

Related: #171


Tweak the 3D editor inertia defaults for better responsiveness (3.x)

3.x version of #35103.
The default orbit sensitivity was decreased to account for this change. Rotational inertia (orbit + freelook) was disabled by default due to known issues.
This also removes the need for separate manipulation inertia settings, as the default settings are more responsive.

Thanks!


[FLINK-4079] do not load Yarn properties file for per-job Yarn clusters

This is a backported fix for the release-1.0 branch to skip loading of the Yarn properties file for per-job Yarn clusters.

Travis has passed. Merging.

Merged with 3163638a61f49dd2df55467615096918bec3a890.


npm run build:examples failed

Do you want to request a feature or report a bug?
bug

What is the current behavior?
npm run build:examples fails.
Out of 43, 42 examples fail.
If the current behavior is a bug, please provide the steps to reproduce.
cloning repo,

npm install
npm link
npm link webpack
npm run build:examples

What is the expected behavior?
The command should run and build examples in webpack directory.
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.

Software
version

webpack
4.0.0-beta.2

OS
Ubuntu 16.04

node
8.0.0

related to webpack/webpack-cli#278, closing this issue, sorry.