Conflict: Constraint error on the latest vulcan-starter (published 4 days ago) and temporary work around

Hi,
On the latest vulcan-starter published 4 days ago, after running
npm install
and npm start I got many Conflict: Constraint error.
The work around solution is to import each vulcan package manually into vulcan-starter and install them.
Please found below my work around solution.
Thank You
Adalidda

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ npm start

<EMAIL_ADDRESS>prestart /home/kauprey/Adalidda-V6.4.X/Vulcan-Starter
node .vulcan/prestart_vulcan.js

\\  ////
\\////    Vulcan.js
\///    The full-stack React+GraphQL framework
────

Creating your own settings.json file...

Happy hacking with Vulcan!
The docs are available at: http://docs.vulcanjs.org

<EMAIL_ADDRESS>start /home/kauprey/Adalidda-V6.4.X/Vulcan-Starter
meteor --settings settings.json

[[[[[ ~/Adalidda-V6.4.X/Vulcan-Starter ]]]]]
=> Started proxy.
=> Meteor 2.1 is available. Update this project with 'meteor update'.
=> Errors prevented startup:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.0 <- vulcan:core 1.16.0
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:core 1.16.0.
Constraints on package "vulcan:core":

<EMAIL_ADDRESS><- vulcan:i18n-en-us 1.16.0
<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:forms 1.3.2 <- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:ui-bootstrap 1.10.1.
Constraints on package "vulcan:ui-bootstrap":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.0 <- vulcan:core 1.16.0
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

=> Your application has errors. Waiting for file change.
^C
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ npm install
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^3.0.0 but none is installed. You must install peer dependencies yourself.
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":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
audited 2230 packages in 13.935s
92 packages are looking for funding
run npm fund for details
found 119 vulnerabilities (85 low, 23 moderate, 11 high)
run npm audit fix to fix them, or npm audit for details
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ npm start

<EMAIL_ADDRESS>prestart /home/kauprey/Adalidda-V6.4.X/Vulcan-Starter
node .vulcan/prestart_vulcan.js

\\  ////
\\////    Vulcan.js
\///    The full-stack React+GraphQL framework
────

Happy hacking with Vulcan!
The docs are available at: http://docs.vulcanjs.org

<EMAIL_ADDRESS>start /home/kauprey/Adalidda-V6.4.X/Vulcan-Starter
meteor --settings settings.json

[[[[[ ~/Adalidda-V6.4.X/Vulcan-Starter ]]]]]
=> Started proxy.
=> Meteor 2.1 is available. Update this project with 'meteor update'.
=> Errors prevented startup:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.0 <- vulcan:core 1.16.0
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:core 1.16.0.

Constraints on package "vulcan:ui-bootstrap":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:voting 1.3.2.
Constraints on package "vulcan:voting":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:events 1.3.2.
Constraints on package "vulcan:events":

<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:comments 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0
<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.0 <- vulcan:core 1.16.0
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

=> Your application has errors. Waiting for file change.
^C
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor remove getting-started
=> Errors after removing packages
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.0 <- vulcan:core 1.16.0
<EMAIL_ADDRESS><- accounts-password 1.6.3

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add example-forum
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.0 <- vulcan:core 1.16.0
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- example-forum 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:core 1.16.0.

Constraints on package "vulcan:ui-bootstrap":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- example-forum 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:voting 1.3.2.
Constraints on package "vulcan:voting":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- example-forum 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- example-forum 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- example-forum 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- example-forum 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:events 1.3.2.
Constraints on package "vulcan:events":

<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:comments 1.3.2 <- vulcan:voting 1.3.2 <- example-forum 1.16.1
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:voting 1.3.2 <- example-forum 1.16.1
<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- example-forum 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- example-forum 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- example-forum 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.0 <- vulcan:core 1.16.0
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- example-forum 1.16.1

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:core
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:lib 1.10.1.
Constraints on package "vulcan:lib":

<EMAIL_ADDRESS><- vulcan:core 1.16.1
<EMAIL_ADDRESS><- vulcan:i18n 1.5.0 <- vulcan:core 1.16.1
<EMAIL_ADDRESS><- vulcan:users 1.3.2 <- vulcan:core 1.16.1
<EMAIL_ADDRESS><- vulcan:ui-bootstrap 1.10.1 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:i18n 1.5.0.
Constraints on package "vulcan:i18n":

<EMAIL_ADDRESS><- vulcan:core 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:users 1.3.2.
Constraints on package "vulcan:users":

<EMAIL_ADDRESS><- vulcan:core 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.10.1 <- vulcan:core 1.16.1
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:ui-bootstrap 1.10.1.
Constraints on package "vulcan:ui-bootstrap":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:voting 1.3.2.
Constraints on package "vulcan:voting":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:events 1.3.2.
Constraints on package "vulcan:events":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:comments 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.10.1 <- vulcan:core 1.16.1
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:lib
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:i18n 1.5.0.
Constraints on package "vulcan:i18n":

<EMAIL_ADDRESS><- vulcan:core 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:users 1.3.2.
Constraints on package "vulcan:users":

<EMAIL_ADDRESS><- vulcan:core 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:ui-bootstrap 1.10.1.
Constraints on package "vulcan:ui-bootstrap":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:voting 1.3.2.
Constraints on package "vulcan:voting":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:events 1.3.2.
Constraints on package "vulcan:events":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:comments 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.1
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ ^C
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:i18n
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:users 1.3.2.
Constraints on package "vulcan:users":

<EMAIL_ADDRESS><- vulcan:core 1.16.1

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:ui-bootstrap 1.10.1.
Constraints on package "vulcan:ui-bootstrap":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:voting 1.3.2.
Constraints on package "vulcan:voting":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:events 1.3.2.
Constraints on package "vulcan:events":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:comments 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.1 <- vulcan:core 1.16.1
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ ^C
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:users
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:ui-bootstrap 1.10.1.
Constraints on package "vulcan:ui-bootstrap":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:voting 1.3.2.
Constraints on package "vulcan:voting":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:events 1.3.2.
Constraints on package "vulcan:events":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:comments 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.1 <- vulcan:core 1.16.1
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:ui-bootstrap
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:voting 1.3.2.
Constraints on package "vulcan:voting":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:events 1.3.2.
Constraints on package "vulcan:events":

<EMAIL_ADDRESS><- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:comments 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0
<EMAIL_ADDRESS><- vulcan:posts 1.3.2 <- vulcan:voting 1.3.2 <- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.1 <- vulcan:core 1.16.1
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:events
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:voting 1.3.2.
Constraints on package "vulcan:voting":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.1 <- vulcan:core 1.16.1
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ ^C
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:voting
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:accounts 1.3.2.
Constraints on package "vulcan:accounts":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by email 2.0.0.
Constraints on package "email":

<EMAIL_ADDRESS><- top level
<EMAIL_ADDRESS><- vulcan:lib 1.16.1 <- vulcan:core 1.16.1
<EMAIL_ADDRESS><- accounts-password 1.6.3
<EMAIL_ADDRESS><- vulcan:accounts 1.3.2 <- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ ^C
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:accounts
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:email 1.3.2.
Constraints on package "vulcan:email":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:email
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:forms 1.3.2.
Constraints on package "vulcan:forms":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:forms
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:embed 1.8.11.
Constraints on package "vulcan:embed":

<EMAIL_ADDRESS><- getting-started 0.0.0

Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:embed
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint<EMAIL_ADDRESS>is not satisfied by vulcan:admin 1.6.1.
Constraints on package "vulcan:admin":

<EMAIL_ADDRESS><- getting-started 0.0.0

kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add vulcan:admin
boilerplate-generator: updating npm dependencies -- combined-stream2...
Changes to your project's package version selections:
accounts-base              added, version 1.7.1
accounts-password          added, version 1.6.3
allow-deny                 added, version 1.1.0
apollo                     added, version 4.0.0
autoupdate                 added, version 1.6.0
babel-compiler             added, version 7.5.5
babel-runtime              added, version 1.5.0
base64                     added, version 1.0.12
binary-heap                added, version 1.0.11
blaze-tools                added, version 1.0.10
boilerplate-generator      added, version 1.7.1
buffer                     added, version 0.0.0
caching-compiler           added, version 1.2.2
caching-html-compiler      added, version 1.1.3
callback-hook              added, version 1.3.0
check                      added, version 1.3.1
ddp                        added, version 1.4.0
ddp-client                 added, version 2.3.3
ddp-common                 added, version 1.4.0
ddp-rate-limiter           added, version 1.0.9
ddp-server                 added, version 2.3.2
deps                       added, version 1.0.12
diff-sequence              added, version 1.1.1
dynamic-import             added, version 0.5.5
ecmascript                 added, version 0.14.4
ecmascript-runtime         added, version 0.7.0
ecmascript-runtime-client  added, version 0.11.0
ecmascript-runtime-server  added, version 0.10.0
ejson                      added, version 1.1.1
email                      added, version 2.0.0
es5-shim                   added, version 4.8.0
fetch                      added, version 0.1.1
fourseven:scss             added, version 4.12.0
geojson-utils              added, version 1.0.10
getting-started            added, version 0.0.0
hot-code-push              added, version 1.0.4
html-tools                 added, version 1.0.11
htmljs                     added, version 1.0.11
http                       added, version 1.4.3
id-map                     added, version 1.1.0
inter-process-messaging    added, version 0.1.1
littledata:synced-cron     added, version 1.5.1
localstorage               added, version 1.2.0
logging                    added, version 1.1.20
meteor                     added, version 1.9.3
meteorhacks:picker         added, version 1.0.3
minifier-css               added, version 1.5.3
minifier-js                added, version 2.6.0
minimongo                  added, version 1.6.1
modern-browsers            added, version 0.1.5
modules                    added, version 0.15.0
modules-runtime            added, version 0.12.0
mongo                      added, version 1.10.1
mongo-decimal              added, version 0.1.2
mongo-dev-server           added, version 1.1.0
mongo-id                   added, version 1.0.7
npm-bcrypt                 added, version 0.9.3
npm-mongo                  added, version 3.8.1
ordered-dict               added, version 1.1.0
promise                    added, version 0.11.2
random                     added, version 1.2.0
rate-limit                 added, version 1.0.9
reactive-dict              added, version 1.3.0
reactive-var               added, version 1.0.11
reload                     added, version 1.3.1
retry                      added, version 1.1.0
routepolicy                added, version 1.1.0
server-render              added, version 0.3.1
service-configuration      added, version 1.0.11
session                    added, version 1.2.0
sha                        added, version 1.0.9
shell-server               added, version 0.5.0
socket-stream-client       added, version 0.3.1
spacebars-compiler         added, version 1.1.3
srp                        added, version 1.1.0
standard-minifier-css      added, version 1.6.1
standard-minifier-js       added, version 2.6.0
static-html                added, version 1.2.2
templating-tools           added, version 1.1.2
tracker                    added, version 1.2.0
underscore                 added, version 1.0.10
url                        added, version 1.3.1
vulcan:accounts            added, version 1.16.1
vulcan:admin               added, version 1.16.1
vulcan:core                added, version 1.16.1
vulcan:email               added, version 1.16.1
vulcan:embed               added, version 1.16.1
vulcan:events              added, version 1.16.1
vulcan:forms               added, version 1.16.1
vulcan:i18n                added, version 1.16.1
vulcan:i18n-en-us          added, version 1.13.2
vulcan:lib                 added, version 1.16.1
vulcan:ui-bootstrap        added, version 1.16.1
vulcan:users               added, version 1.16.1
vulcan:voting              added, version 1.16.1
webapp                     added, version 1.9.1
webapp-hashing             added, version 1.0.9
vulcan:admin: Vulcan components package
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor add example-forum
Changes to your project's package version selections:
example-forum  added, version 1.16.1
example-forum: Vulcan forum package
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ meteor start
'start' is not a Meteor command. See 'meteor --help'.
kauprey@ubunextjs:~/Adalidda-V6.4.X/Vulcan-Starter$ npm start

<EMAIL_ADDRESS>prestart /home/kauprey/Adalidda-V6.4.X/Vulcan-Starter
node .vulcan/prestart_vulcan.js

Hey @eric-burel @SachaG
I am very sorry writing this and hopefully you take this as a really touched comment and well-intentioned criticism.
Again I am here at Vulcan willing to check and use this stack for a new customer project - but - also again - I am giving up in case that not even the Starter repo is working to have some fiddle around before diving into a project.
That's really a pitty for all the time and effort you invest in this project. For me it is not quite clear if you use Vulcan for any of your own projects and so it makes sense for you as a development company? But when you doing this work in case of getting others onboard - it should at least - imho - have always a functional starter.
I tried to run just the Starter Repo with the meteor .release left in the Repo, I tried the two Repos installation and I tried to update all to meteor 2.2 - but - in any case still get "your application is crashing" or "has constraints".
Sorry to say this, but I hope you understand that a "Hmmm - what a ...
This won't bring friends to the Vulcan project.
Cheers
Tom

Hi @TomFreudenberg , we use Vulcan only on existing projects (Live for Good platform for me, and Sacha has his own projects like Sidebar).
I don't really advise to start new projects based on Vulcan Meteor, as we are transitioning toward Next and the NPM ecosystem : https://github.com/VulcanJS/vulcan-next. This work is ongoing, so Vulcan Next already includes many of Vulcan backend capabilities, but is still in beta-testing phase. We are also working on reintroducing components like the SmartForm right now.
So if you need to start something right now, I think you'd be better of with switching to Vulcan Next (and bear with us until it's a bit more complete) or going back to vanilla Meteor, now it's actively maintained again.
The goal of having the Starter ok at any time is sadly unachievable:

Meteor build time and test time are awful. This prevents us from setting up free automated CI/CD on Github
Builds often work on our machine when we push, but not on other users machine, without obvious reasons. Versioning is not reliable and very time-consuming to debug.

The bug you are suffering from, we are hitting them as well and have no better solution. As contributors we cannot sustain contributing to Vulcan when it takes an hour to just get the version right with obscure error messages and dependency conflicts, even if we still try our best to keep the framework up and running (happy to take PR in as well!). All the more that the server build often fails, Meteor not being able to handle some packages like Material UI.
Hopefully Next and NPM solves most of those issues, and let us go back to a wider JavaScript ecosystem where we can find more support and answers. Also no time is lost because we are porting all Vulcan's code to this new ecosystem.

Hi @eric-burel
thanks for your open and clear words - Currently with this project I am not able to step into "Vulcan Next" - but I checkout earlier for the next time.
Until then - good luck to you and your projects!
Tom


fix: show methods for ComputeConfig and NodeSpec

The oneliner show/repr methods were outdated. This adds tests that actually parse the output, making sure we recover the original object.

Codecov Report

Merging #34 (188e8d9) into main (ba66d96) will decrease coverage by 7.50%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
- Coverage   75.36%   67.86%   -7.50%
==========================================
  Files          16       16
  Lines        2192     2082     -110
==========================================
- Hits         1652     1413     -239
- Misses        540      669     +129

Files Changed
Coverage Δ

src/jobsubmission.jl
70.03% <100.00%> (-10.33%)
:arrow_down:

src/node.jl
76.47% <100.00%> (-16.29%)
:arrow_down:

... and 14 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Bug]: Component - Filter chips - outline affecting position

Prerequisites

[X] I have searched the backlog for duplicate or closed feature requests

Your test device
iPhone 13
OS Version
16.1.1
App version
0.18.0
Describe the issue
The size inconsistency has been resolved in a previous bug, however there remains a small issue with the difference in selected and unselected states. when unselected (outline) the border is slightly bigger than the selected (filled orange) state. This change pushes surrounding filter chips vertically and horizontally by a small amount.
Expected Behavior
The selected and unselected state should be exactly the same size, therefore no chips will move as a result of changing the state


fix: tree structure on tasks

A small fix on the issue I opened a while ago.
On the tasks.json of seed/osc and seed/Drum I changed "${workspaceFolder}/../../../DaisySP" to "${workspaceFolder}/../../DaisySP".

nice catch! Thanks for the issue, and PR!
I think these particular examples used to live in folder one-level up, and the VS code tasks didn't get updated when the moved to the base seed/ folder.
Thanks for fixing it!


cgmath->0.12.0; associated changes in teapot example

Minor updates to teapot use of cgmath associated with version update 0.7->0.12
Use of PI/2 constant in cgmath

Thanks
r+, will merge when that travis thing with Cargo is fixed.

Please remove the .idea thing. :-/

Sigh :)  Many of us use Intellij and it keeps that trash from the repo. Will do.

Hopefully I don't forget to merge this time.


Saboteur camo is labeled "Shade"

The military camo for 40 headshots, saboteur, is shown as "shade" in the tracker.

Fixed in #16.


test_bucket is flaky

when running with cargo nextest run locally, I get the following error quite often.
thread 'tower::rate_estimator::tests::test_bucket' panicked at 'assertion failed: `(left == right)`
  left: `9`,
 right: `10`', quickwit-common/src/tower/rate_estimator.rs:213:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Fixed via #3210.


Any custom receiver examples?

Great work, it is coming to fruition just as we need to build .Net Core Webhook receivers. I need to build custom receivers for a variety of systems not covered in the out-of-the box receivers. Can you point me at an example for custom receiver development. I've been searching around for a day or two but not finding anything. Thanks.

@codermrrob I am currently working on a fitbit one which, once this library stablises and generates a nuget pacakge, I will be publishing in it's own repository and packaging to nuget etc.
However until that point I have found that it's easier to develop it in the WebHooks solution as it gets the latest package references and you can debug into the library easily.
If you want to take a look my current development as an example can be found in https://github.com/WestDiscGolf/WebHooks/tree/fitbit
Hope it helps!

thanks... I had just realized the same, that better to develop it in the WebHooks solution. Cheers for your fitbit link.


docs(readme): Add HauseMaster to Examples

Add HauseMaster to example usage.

My bad, I actually used it in one of my repos, I've added some in my profile readme now

My bad, I actually used it in one of my repos, I've added it in my profile readme now.

Ok, if you want to add a link to the repo too, that's fine. You'll just need to find a suitable square icon to represent it.


[DOC] Be more explicit about netCDF groups and xarray.Dataset relationship.

This PR is related to the discussion in #2916.  In https://xarray.pydata.org/en/stable/io.html#netcdf there are statements like

netCDF files on disk directly correspond to Dataset objects.

This is useful conceptually but can be confusing when working with netCDF groups which are not supported as part of the data model.  I thought it would be clearer if the description of how to work with groups explicitly said this.

Thanks @zdgriffith, this is great!


Asserts existence of required environment variables

I've changed quite some things, which might be overwhelming. I am sorry for that, I just can't get a hold of myself.
Changes are explained on commit messages in more detail, but this should solve assertion of environment variables along with keeping previous behavior unchanged.
PS: Thanks for sharing the code. ♥

Thanks, this looks like good work.
I noticed that you changed habash getidoftask to habash id. Is there a reason for this? I'd prefer to keep getidoftask if possible (maybe add a warning that it will be deprecated in the future?) rather than cause breaking changes.
(I haven't had a chance to test the code yet so habash getidoftask may still work, feel free to correct me.)

I noticed that you changed habash getidoftask to habash id. Is there a reason for this?

It is shorter and difficult to read words together without any form of separation between them.

I'd prefer to keep getidoftask if possible

It still works, just not documented.

I agree, getidoftask is cumbersome but I think id is a little too vague. Maybe get-task-id or something?
I also noticed createhabit is now habit etc.. Descriptive names are better than short names here, I'd prefer create-habit if that's more readable?

Merging for now, we can figure out command names later.


0.4.0

Pull Request Test Coverage Report for Build 259

552 of 552 (100.0%)  changed or added relevant lines in 13 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 201:
0.0%

Covered Lines:
2789

Relevant Lines:
2789

💛  - Coveralls


Reimplemented email analytics prioritizing email opens

ref https://github.com/TryGhost/Ghost/pull/20835

reimplemented email analytics changes that prioritized opened events over other events in order to speed up open analytics
added db persistence to fetch missing job to ensure we re-fetch every window of events, especially important if we restart following a large email batch

We learned a few things with the previous trial run of this. Namely, that event throughput is not as high as we initially saw in the data for particularly large databases. This set of changes is more conservative, while a touch more complicated, in ensuring we capture edge cases for really large newsletter sends (100k+ members).
In general, we want to make sure we're fetching new open events at least every 5 mins, and often much faster than that, unless it's a quiet period (suggesting we haven't had a newsletter send or much outstanding event data).

I'm thinking we may want to include some sort of backstop for the jobs table data in case it isn't cleared during this migration, the migration isn't run, etc. I don't know what would be reasonable and I also don't want to obscure the existing code with weird handling of cases like this. Ideas?

I don't know what would be reasonable and I also don't want to obscure the existing code with weird handling of cases like this. Ideas?

Maybe a silly idea, but could we use a new name for the job, so it wouldn't even look at the same rows if the migration doesn't run/fails for some reason? Maybe we could introduce a concept of job version, so the rows would become e.g. email-analytics-latest-opened-v2 or something along those lines? And if we ever come across a similar challenge in the future, we just increment the version and Ghost should fallback to running the full query if it doesn't find a matching row in the table?

While that does work, I don't see a need to version and that makes future migrations to try and clear this out extra messy. I'd personally rather avoid that.

I think I'm missing something here, maybe you can help me understand. I'm not sure I see how this avoids us missing events with fetchMissing. I see the main changes here are that we're fetching a max of 10k opened events, rather than infinity.
As I understand this logic, if we fetch 10k opened events, we'll stop there and wait for the job to kick off again. If we end up fetching 10k opened events for a couple iterations in a row, couldn't we fall behind on fetchMissing again?
Again, I'm probably just confused! Maybe we can get on a call tomorrow AM to go over it 😃


remove load and save functions from index html file

move these load/save functions somewhere else - action-controls or new component?
https://www.useloom.com/share/9183e84688ec4c3ba55943408fd3d582

also remove jquery dependency, save/load is the only thing that still requires jquery


PowerToys Run Bug

Microsoft PowerToys version
0.63
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
Search for "douyin" first click on the copy path, and then click on the location where the file is opened, and the duplicate operation bug will appear

2022-08-18.txt
✔ Expected Behavior
No response
❌ Actual Behavior

Other Software
I turned on scrcpy version <IP_ADDRESS> in the background, see Task Manager to find programs running together, as shown in the figure

Is this issue still relevant in v0.73? /needinfo

This issue has been resolved in the new (v0.79.0) version of PowerToys Run


Running tests in :core runs full Groovy recompilation

Task ':core:compileTestGroovy' is not up-to-date because:
  Input property 'stableSources' file /Users/asodja/workspace/gradle/subprojects/core/src/test/groovy/org/gradle/api/internal/initialization/DefaultScriptHandlerTest.groovy has changed.
Groovy compilation avoidance is an incubating feature.
Created classpath snapshot for incremental compilation in 0.01 secs.
Full recompilation is required because Incremental annotation processing is not supported by Groovy.. Analysis took 0.033 secs.

If we will run ann. processor for every project https://github.com/gradle/gradle/issues/25990, we need a solution for that.
Build scan: https://ge.gradle.org/s/x7n7kry6ov5fw

We add ann. processor for code instrumentation.

I think solution is, that we exclude project :internal-instrumentation-processor from testAnnotationProcessor classpath


Date filter - add an option to see the last X accidents

Add an option to see the last X accidents.
X- user specify

@galraij Is this still interesting? Or do we prefer something like: "Accidents from the last x month with severity higher than y?"

Yes it is!
And no, we want X number of last accidents of the time mentioned in the filters.

On 28 Dec 2015, at 21:32, Simona Holstein<EMAIL_ADDRESS>wrote:
@galraij https://github.com/galraij Is this still interesting? Or do we prefer something like: "Accidents from the last x month with severity higher than y?"
—
Reply to this email directly or view it on GitHub https://github.com/hasadna/anyway/issues/37#issuecomment-167634929.


Possibility to set a property

Hi thanks for Anime.js!
This is more of a question than a issue.
But I was wondering if you could set a property to alter the animation.
For example:
``
var openMenu = anime({
targets: ['.menu'],
translateX: '20rem',
duration: 1000,
autoplay: false,
direction: 'normal',
complete: function() {
console.log( this.translateX ); // logs 20rem
}
});
$(document).on('click', '.hamburger', function() {
openMenu.translateX = '40rem'; // set obj property
console.log( openMenu ); // checks out with new set value
openMenu.play();
});
``
Should this be possible? Or.. :)
thanks!

This set method would be also nice to change the animation target while the animation is running

I found a way to do so, but I think it would have a lot of value to make it accessible in the public API.
Here is what I did:
startAnimation = anime({     targets: myObj,     x: targetX,     y: targetY,     duration: 500,     easing: 'easeOutQuad' })
With initial values for targetX and targetY (let's say its the position of the user mouse/finger)
I'm capable of altering those values with the following code
startAnimation.tweens[0].to.numbers = [newTargetX] startAnimation.tweens[1].to.numbers = [newTargetY]
I'm not sure it's exactly following the proper easing function, but it clearly works visually speaking.
Hope this helps 👍

Simply wrap your animation in a function, and make sure to remove the elements from anim before each call.
Like this:
function followCursor(e) {
  var targets = ['.blue', '.green'];
  anime.remove(targets)
  anime({
    targets: targets,
    translateX: e.pageX,
    translateY: e.pageY,
    delay: function(el, i) {
      return i * 80;
    }
  });
}

document.body.onclick = followCursor;

Live example: http://codepen.io/juliangarnier/pen/ozpGdd


Cost&Usage app doesn't show version number when you are in the app

Can we please have a version identifier in the Cost&Usage app? We have the version in the AppStore C&U card but there is no way I have found to see the version of C&U when in the app.

Yes. We'll add a version identifier in the app.

Yes. We'll add a version identifier in the app.


Account is not Active

when I install mysql from kinematic, it reports the error
Error: Status 403 trying to pull repository library/mysql: "Account is not Active"

I wonder which account used here

The account should be specified in the top left corner of the Kitematic app - There's a good chance you logged into the Hub for which you need to activate the account.

@qianyiliushang Can you try to log out and log in again? Thanks!
The problem should be fixed after. If not please reopen this issue. Thanks!

Now I cannot login hub via kitematic on my 2 macbooks(I can sign in hub with web site) it seems that I only successfully sign in after kitematic installed.

@qianyiliushang It seems like you have not activated your Docker Hub account through the sign up email yet.
Please try to log in again from hub.docker.com
If you are still having trouble, please contact<EMAIL_ADDRESS>They will help you with any Hub issues.
Thank you!


Sort out our project metrics

We identified some threads of feedback, input and other project metrics that we want to consolidate and make sure our team can access when we need it.

[ ] Page feedback report
[ ] Event tracking (on website interactions) #590
[ ] Contact us
[ ] Access to regular Google analytics
[ ] Insights on code access (distinction from NPM package downloads)

Set as p1 for getting our basic plan rolling.
Some of these tasks may need to become their own issues.

@jaredwyee


load flag is required in buildx

Signed-off-by: Youka<EMAIL_ADDRESS>Usually docker build load automatically the build results to local registry, in buildx --load is required
Close #797

Thanks @youkaclub for spotting and fixing this.

@allcontributors please add @youkaclub for bugs


CallCompressed and compression_type

Adds support for new RPC call CallCompressed and a @compression_type decorator. A protocol can specify a top level @compression_type (defaults to none) and individual methods can override this default.
depends on changes in https://github.com/keybase/go-framed-msgpack-rpc/pull/162

waiting on https://github.com/keybase/go-framed-msgpack-rpc/pull/162 and manual client testing before merge

depends on https://github.com/keybase/node-avdl-compiler/pull/23


Using auto-accessor with readonly or declare should raise an error

Bug Report
🔎 Search Terms
auto accessor readonly declare
🕗 Version & Regression Information
Version 4.9.3

I was unable to test this on prior versions because the auto-accessor feature is new in 4.9

⏯ Playground Link
Playground link with relevant code
💻 Code
class Foo {
    accessor readonly foo: number = 5;
    //       ^ no error here
    accessor declare bar: string;
    //       ^ no error here
}

const myc = new Foo();
myc.foo = 6;
// property is not read-only, which is correct because trying to
// define it read-only as above should be an error in the first place

🙁 Actual behavior
No TypeScript error is shown, neither for readonly nor for declare.
readonly is completely ignored, i.e. writing to the property also does not result in an error.
🙂 Expected behavior
In the auto-accessor PR description, it is explicitly stated that

accessor cannot be used with readonly or declare on the same field declaration.

So I'd expect a corresponding TypeScript error message for both accessor declarations in the example above.
Once using readonly on an accessor raises an error, it is correct to ignore this for further analysis, so the current behavior to not report an error when trying to write to the property is correct and should remain as-is.

I'm a bit confused why declare accessor wouldn't be legal, but accessor declare is just weird and looks like an oversight in the parser.

Yeah, modifier order is always enforced. This is a bug.

That was fast! 👍


question how to remove

Hi sir, how can i delete/remove the package from Ubuntu?

i added the uninstall script, try https://github.com/jothi-prasath/auto-epp?tab=readme-ov-file#uninstall

Hi Jothi, i receive errors:
chmod +x ./uninstall.sh
sudo ./uninstall.sh
chmod: kan geen toegang krijgen tot './uninstall.sh': Bestand of map bestaat niet
sudo: ./uninstall.sh: opdracht niet gevonden

try this
git clone https://github.com/jothi-prasath/auto-epp
cd auto-epp
chmod +x ./uninstall.sh
sudo ./uninstall.sh

Still can't:
fatal: destination path 'auto-epp' already exists and is not an empty directory.

remove that auto-epp folder and try it again

That did the trick : ) thanks

Nope still not delete

how you know it is not deleted

map and files are still there and prompts for monitor still works

also with no luck


extract test doesn't work when extracting to a variable

If you try to extract a test from a snippet to an existing variable in the snippet, then it doesn't work. For example, if you try to extract the following, it doesn't do anything:
(compiler := SmaCCGrammarCompiler new) codeGenerator
	defaultCategory: test class category.
compiler
	buildDefinition: '<whitespace> : \s+;
			%root FooNode;
			A : B "a" ''a'' {{FooNode}} ;
			B : A | C ;
			C : "c" ''c''; '.
test
	assert: ([ compiler compileInto: 'TestScanner' andParser: 'TestParser'.
		false ]
			on: SmaCCCompilationNotification
			do: [ :ex |
				('Node creation' = ex messageText and: [ '*>>>A<<<*' match: ex tag ])
					ifTrue: [ ex return: true ]
					ifFalse: [ ex resume: nil ] ])

Fixed to show the class and test selector inputs:


PHOENIX-5673 : The mutation state is silently getting cleared on the …

@ChinmaySKulkarni  @abhishek-chouhan Creating this PR to get feedback on the approach.
I have added a config to enable this behaviour ( default false).
Ran all the IT locally for the same

@ChinmaySKulkarni Tested view creation and index creation also


MSID: 86635 Version: 2 DOI: 2<IP_ADDRESS>5764

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[ ] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=86635)

or (only one should be ticked. remove other from description.)

[ ] Confirmed with Ted at bioRxiv that MECA archive is available

Send the following email to Ted and wait for his reply.
Hi Ted,

Please can you prepare the preprint MECA for 10.1101/2<IP_ADDRESS>5764

Thanks

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/86635/v2)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews
Who can help: Editorial team

[ ] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>5764)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/86635/v2/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/86635)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/86635

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/86635

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/86635/v2/86635-v2.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/86635)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

(V2 should use preprint V3)


protocol(ticdc): remove useless code and setup DefaultMaxMessageBytes

What problem does this PR solve?

Issue Number: None
What is changed and how it works?
remove useless code.
Check List
Tests

No code

Code changes

Has exported function/method change
Has exported variable/fields change

Side effects
None
Related changes
None
Release note
None

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-5.0@0c262b7). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release-5.0      #4070   +/-   ##
================================================
  Coverage               ?   64.0413%
================================================
  Files                  ?        160
  Lines                  ?      16747
  Branches               ?          0
================================================
  Hits                   ?      10725
  Misses                 ?       5075
  Partials               ?        947

/run-all-tests

/merge

/run-integration-test


BatchNorm2D Bessel's correction

Added Bessel's correction to BatchNorm2D.
When using the unbiased estimate, the running average of the standard deviation will also use the unbiased variance.
Unlike Pytorch (https://github.com/pytorch/pytorch/issues/77427).
Would be great if someone could add some tests.

Needs tests, tabs are wrong, and should reuse Tensor.std if possible

see #779


Docs: Add/update section on how to override key properties and replication key in metadata key in meltano.yml

Discuss in slack thread: https://meltano.slack.com/archives/C01TCRBBJD7/p1676478682584279?thread_ts=1676381259.070699&cid=C01TCRBBJD7
StackOverflow: https://stackoverflow.com/a/71669575/4298208

Someone else asked about this in Slack: https://meltano.slack.com/archives/C069CQNHDNF/p1706094046490359


Multi-line command history inconsistent behavior

When pressing up-arrow a previous command is displayed as expected, again pressing up-arrow the cursor moves to the beginning of the command line.  It should display the next command in history.  Third up-arrow displays the next command in history. This behavior repeats for each command in history. Down-arrow seems to  work fine.

leaving the cursor at the beginning of the line when stepping thru history would "solve" this issue, but also feel weird in use when you want to edit a previously used command

Being able to continuously scroll up and down with the up & down keys through the command history unimpeded is preferable.  If the "home" & "end" keys are working properly, perhaps they could be used to opt-in and/or opt-out of "command history mode" based on the current context (the cursor's current position, whether it be at the beginning, end, or middle of a line; the current keyboard mode, whether it be "command history mode" or "editing mode"; etc.).
As you mentioned, though, I'm not sure how complex the algorithms would be to implement, or whether or not folks would find using the "home" and "end" keys to influence the keyboard mode behavior to feel too unnatural.  I can understand why you want to transfer the command history control keys from the up & down keys to the page up & page down keys.

Hi Steve, thanks for explaining the logic behind the design. All is well. Looking forward to '*KEY' implementation;)

@tonedef71  the recent Console8 2.2.x release contains support for moving thru command history using the page up and page down keys.  the up and down arrows, when at the beginning or end of the command line respectively, maintain their behaviour of also stepping thru the history.
@leventp that release also includes the *hotkey command


Adding Transaction after importing .CSV with unordered ID cause the application crashed

When user creating new account and importing transactions from .CSV file which contains some missing ID, after importing all the transactions then adding new transactions the application will crash

CSV file example (this file doesn't have the ID 2 and ID 3 transactions)

ID;Date (en_US Format);Description;Type;RepeatInterval;RepeatFrom (-1=None,0=Original,Other=Id Of Source);RepeatEndDate (en_US Format);Amount (en_US Format);RGBA;Group(Id Starts At 1);GroupName;GroupDescription
1;3/29/2023;a;0;0;-1;;1000;rgb(53,132,228);-1;;
4;3/29/2023;a;0;0;-1;;1000;rgb(53,132,228);-1;;
5;3/29/2023;asdf;0;0;-1;;12313;rgb(53,132,228);-1;;

However, if users reopened the app after importing, the app will just fine

error log

Unhandled exception. Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: transactions.id'.
   at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
   at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader()
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteNonQuery()
   at System.Data.Common.DbCommand.ExecuteNonQueryAsync(CancellationToken cancellationToken)
--- End of stack trace from previous location ---
   at NickvisionMoney.Shared.Models.Account.AddTransactionAsync(Transaction transaction) in /run/build/org.nickvision.money/NickvisionMoney.Shared/Models/Account.cs:line 800
   at NickvisionMoney.Shared.Controllers.AccountViewController.AddTransactionAsync(Transaction transaction) in /run/build/org.nickvision.money/NickvisionMoney.Shared/Controllers/AccountViewController.cs:line 613
   at NickvisionMoney.GNOME.Views.AccountView.<>c__DisplayClass90_0.<<NewTransaction>b__1>d.MoveNext() in /run/build/org.nickvision.money/NickvisionMoney.GNOME/Views/AccountView.cs:line 935
--- End of stack trace from previous location ---
   at NickvisionMoney.GNOME.Views.AccountView.<>c__DisplayClass90_0.<<NewTransaction>b__0>d.MoveNext() in /run/build/org.nickvision.money/NickvisionMoney.GNOME/Views/AccountView.cs:line 935
--- End of stack trace from previous location ---
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_1(Object state)
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()

https://github.com/nlogozzo/NickvisionMoney/releases/tag/2023.4.0-beta1


[Move Prover] Changed signature of WriteRef and refactored Branch instruction

Motivation
This PR makes three changes:

Changes signature of WriteRef so that the reference being written is an input rather than output of the instruction. This change will simplify the new pack analysis in a downstream PR.
Refactors the Branch bytecode into Jump and Branch with the latter explicitly supply both the then and the else labels.  This change continues the work started earlier by creating abstract labels for all jumps and branches.  The changes also simplifies code in various places.
Changes the propagation rules in liveness analysis with greater attention to side effects of all bytecodes.

Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Existing tests
Related PRs

@bors-libra r=wrwg

:pushpin: Commit ee1b481 has been approved by wrwg

:hourglass: Testing commit ee1b481da417dccde3ec2dd74e7962a66530b1c6 with merge b3dfe549b9c6153a5b75363b849e7eb3983dd557...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: wrwg
Pushing b3dfe549b9c6153a5b75363b849e7eb3983dd557 to master...


Move F# to consume Roslyn 2.6.0-vs-for-mac-62317-08

This carries along some breaking changes (dotnet/roslyn@efd59a3bf863d2516ae96c95678f8200bb816982) in Roslyn's Quick Info implementation that we must react to. Since it's our first move to the 2.6 line it also carries along some deprecation of some APIs (namely, classification and comment handling) that we also respond to as well.

From the Jenkins log:
"D:\j\w\release_ci_pa---5a4853ab\vsintegration\tests\unittests\VisualFSharp.Unittests.fsproj" (Build target) (45) ->
(CoreCompile target) ->
  D:\j\w\release_ci_pa---5a4853ab\vsintegration\tests\unittests\TestLib.LanguageService.fs(368,17): error FS0074: The type referenced through 'Microsoft.CodeAnalysis.Editor.QuickInfo.DeferredContentFrameworkElementFactory' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.CodeAnalysis.EditorFeatures.Wpf'. [D:\j\w\release_ci_pa---5a4853ab\vsintegration\tests\unittests\VisualFSharp.Unittests.fsproj]

@brettfo I find your lack of PackageReferences disturbing.

Adding @KevinRansom as an FYI.  I've also turned off all auto-merges into and out of dev15.6 since we'll need to be more deliberate now.


ci: Add vnu to dev docker image

Whoops - why is the diff so huge?

This currently assumes an x86 architecture on the developer's machine.

Oh. Yes. The alternate way to do this is to install the JDK from apt and then just pull the JAR. Will do that.

Whoops - why is the diff so huge?

The original file was incorrectly created using CRLF instead of just LF (thanks Windows). So this is ok.


How can I update memory setting for "Gradle Test Executor"

I can see that by default, its memory setting is "Xmx:2048m MaxHeapSize=512m"
How can I update it if I feel it is not enough?

I don't believe that's the default, but you can set the max heap size or JVM arguments with the Test task: https://docs.gradle.org/current/dsl/org.gradle.api.tasks.testing.Test.html#org.gradle.api.tasks.testing.Test:maxHeapSize


Output of cell is too verbose

This example should have a one-line output [16, 28, 28]. Instead it has a 5 line output.
images.shape

[
  16,
  28,
  28
]

http://propelml.org/notebook/?nbId=yQW73rabuUBeTa72OiHL
See also #276

Started #276 at q/inspector

closed in favor of #276


deprecation warning for scut-reverse-italics with sass 3.4.11

Loving this gem - very handy!
Today, I upgraded my Padrino project to compass 1.0.3, which came with sass 3.4.11. It generated a deprecation warning for one of scut's mixins:
DEPRECATION WARNING: Passing false, a non-string value, to unquote() will
be an error in future versions of Sass.

on line 1425 of /Users/timmy/.rbenv/versions/2.2.0/gemsets/midwest-website/gems/scut-1.1.0/dist/_scut.scss, in `scut-reverse-italics'
from line 1436 of /Users/timmy/.rbenv/versions/2.2.0/gemsets/midwest-website/gems/scut-1.1.0/dist/_scut.scss
from line 4 of /Coder/projects/mwdl/midwest-website/app/stylesheets/application.scss

I'm aspiring to take a look at it within the week, and offer up a pull request.

PR #177 fixes the issue.

Fixed in v1.1.2


Dummy

added the number of dummy on the map.

Added?
Past?

On the information of the map. Add information on the number of dummy present on the map.

Working on it, will be added soon


Java and Python AVRO compatibility - stringType

The Java AVRO class generator makes Java specific modifications to schemas, that then later when a Schema Registry validation is performed causes new versions of the schema to be added to the Confluent registry.
See:

https://issues.apache.org/jira/browse/AVRO-2838
https://issues.apache.org/jira/browse/AVRO-3077
https://github.com/davidmc24/gradle-avro-plugin/discussions/156
https://github.com/confluentinc/schema-registry/issues/868
https://github.com/confluentinc/schema-registry/issues/1677
https://github.com/confluentinc/schema-registry/issues/1352

My pull request has been ignored for months: https://github.com/apache/avro/pull/1235.  In the meantime, Confluent has added a new flag to work around this issue:
KafkaAvroSerializerConfig.AVRO_REMOVE_JAVA_PROPS_CONFIG = true

It seems the easiest path forward at this point is to simply accept AVRO compiler's demands that AVRO schemas must have Java specific types.  Initial testing suggests this fixes the issue - Python scripts appear to silently ignore unrecognized logical type and inherit the logical base type string.   However, I've noticed the AlarmActivationUnion.avsc is bumped to version 2 the first time set-override.py is executed.   Maybe a separate issue?   More investigation needed.

I've created a separate issue for this new anomaly: https://github.com/JeffersonLab/jaws/issues/28.
I'm closing this issue for now, as the ugly fix of simply accepting that our schemas have Java specific logical types appears to be working.


Enum as Lookup Table

Is it possible to create a a Lookup Table from an Enum and apply foreign key constraints on related entities.
In EF6, we can use this library:

https://github.com/timabell/ef-enum-to-lookup

Creates lookup tables and foreign key constraints based on the enums used in your model.

This may also be related to #12206.
Would this require EF to treat Enum as an entity?
References:

https://stackoverflow.com/questions/34557574/how-to-create-a-table-corresponding-to-enum-in-ef6-code-first
https://stackoverflow.com/questions/11167665/ef5-code-first-enums-and-lookup-tables
https://stackoverflow.com/questions/31372549/code-first-enumerations-put-into-lookup-tables
http://gentlelogic.blogspot.com/2014/07/ef-code-first-create-table-out-of-enum.html

@gojanpaolo Thanks for suggesting this. We discussed this in triage and it is not something we are planning to implement. We might consider a community PR to add this if a reasonable design is proposed and the implementation is not too complex.

This seem to be possible already with data seeding (see below).
While playing with this concept I've found some limitations though:

when data seeding has an Enum as key it doesn't seem to be able to do compare and always recreates deletes and recreates all data (even when creating migration that actually has no changes.. possibly bug?), so I've worked around it by introducing a additional numeric key
when you change enum value it will get recreated by delete/create (which is expected), but you might be surprised that all data with that value has cascade deleted with it because cascade is the EF default, so maybe use DeleteBehavior.Restrict or don't use FK here at all.

    /// <summary>
    /// Generic entity representing a enum.
    /// </summary>
    /// <typeparam name="T">Enum type.</typeparam>
    public class EnumLookup<T>
        where T : Enum
    {
        public EnumLookup()
        {
        }
        public EnumLookup(T value)
        {
            Id = Convert.ToInt32(value);
            Value = value;
            Name = value.ToString();
        }

        public int Id { get; set; }
        public T Value { get; set; }
        public string Name { get; set; }
    }

    public static class EnumLookupExtensions
    {
        /// <summary>
        /// Scan all registered entities and build a enum lookup table for any enum properties.
        /// </summary>
        /// <param name="modelBuilder">The model builder.</param>
        /// <param name="createForeignKeys">Create foreign keys. Note that default delete behavior of EF is Cascade, so changes in enums might delete your data!</param>
        public static void CreateEnumLookupTable(this ModelBuilder modelBuilder, bool createForeignKeys = false)
        {
            foreach (var property in modelBuilder.Model.GetEntityTypes().SelectMany(t => t.GetProperties()).ToArray())
            {
                var entityType = property.DeclaringEntityType;
                var propertyType = property.ClrType;

                if (!propertyType.IsEnum)
                    continue;

                var concreteType = typeof(EnumLookup<>).MakeGenericType(propertyType);
                var enumLookupBuilder = modelBuilder.Entity(concreteType);
                enumLookupBuilder.HasAlternateKey(nameof(EnumLookup<Enum>.Value));

                var data = Enum.GetValues(propertyType).Cast<object>()
                    .Select(v => Activator.CreateInstance(concreteType, new object[] { v }))
                    .ToArray();

                enumLookupBuilder.HasData(data);

                if (createForeignKeys)
                {
                    modelBuilder.Entity(entityType.Name)
                        .HasOne(concreteType)
                        .WithMany()
                        .HasPrincipalKey(nameof(EnumLookup<Enum>.Value))
                        .HasForeignKey(property.Name);
                }
            }
        }
    }

Sample usage:
    public enum AssignmentType
    {
        Bug = 100,
        Feature = 200,
        Enhancement = 300,
    }

    public enum AssignmentPriority
    {
        Urgent = 100,
        Urgenter = 200,
        Urgentest = 300,
        Critical = 1105,
        Criticaler = 1200,
        Criticalest = 9001
    }

    public class Assignment
    {
        public int Id { get; set; }

        public AssignmentType Type { get; set; }

        public AssignmentPriority Priority { get; set; }
    }

    public class WorkContext : DbContext
    {
        public DbSet<Assignment> Assignments { get; set; }

        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            optionsBuilder.EnableSensitiveDataLogging();

            optionsBuilder.UseLoggerFactory(
                new LoggerFactory().AddConsole()
            );

            optionsBuilder.UseSqlServer("Server=.;Initial Catalog=efenumlookup;Integrated Security=True");
        }

        protected override void OnModelCreating(ModelBuilder modelBuilder)
        {
            modelBuilder.Entity(typeof(Assignment))
                .HasData(new object[]
                {
                    new Assignment() { Id = 15, Priority = AssignmentPriority.Critical, Type = AssignmentType.Enhancement },
                    new Assignment() { Id = 16, Priority = AssignmentPriority.Criticaler, Type = AssignmentType.Enhancement },
                    new Assignment() { Id = 17, Priority = AssignmentPriority.Criticalest, Type = AssignmentType.Enhancement }
                });

            modelBuilder.CreateEnumLookupTable(createForeignKeys: true);
        }
    }

    class Program
    {
        static void Main(string[] args)
        {
            using (var context = new WorkContext())
            {
                var assignments = context.Assignments.ToArray();
                var assignmentTypeLookups = context.Set<EnumLookup<AssignmentType>>().ToArray();
                var assignmentPriorityLookups = context.Set<EnumLookup<AssignmentPriority>>().ToArray();

                foreach (var assignment in assignments)
                {
                    Console.WriteLine($"{assignment.Id} {assignment.Type} {assignment.Priority}");
                }
                foreach (var typeLookup in assignmentTypeLookups)
                {
                    Console.WriteLine($"{typeLookup.Name} {typeLookup.Value}");
                }
                foreach (var priorityLookup in assignmentPriorityLookups)
                {
                    Console.WriteLine($"{priorityLookup.Name} {priorityLookup.Value}");
                }
            }

            Console.ReadKey();
        }
    }

@Kukkimonsuta hi, using your solution i keep getting the following error
{System.InvalidOperationException: The seed entity for entity type 'EnumLookup<AddressSearchTypeEnum>' cannot be added because there was no value provided for the required property 'Id'.
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelValidator.ValidateData(IModel model)
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelValidator.Validate(IModel model)
   at Microsoft.EntityFrameworkCore.Infrastructure.RelationalModelValidator.Validate(IModel model)
   at Microsoft.EntityFrameworkCore.Internal.SqlServerModelValidator.Validate(IModel model)
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.CreateModel(DbContext context, IConventionSetBuilder conventionSetBuilder, IModelValidator validator)
   at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
   at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
   at System.Lazy`1.CreateValue()
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.CreateModel()
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.get_Model()
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
   at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
   at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
   at Microsoft.EntityFrameworkCore.DbContext.EntryWithoutDetectChanges[TEntity](TEntity entity)
   at Microsoft.EntityFrameworkCore.DbContext.SetEntityState[TEntity](TEntity entity, EntityState entityState)
   at LocationAzureApi.Services.AddressSearch.AddressSearchService.AddRecord(AddressSearchRecord record) in C:\WS\TS\LocationAPI\LocationAzureApi\Services\AddressSearch\AddressSearchService.cs:line 18}

@Kukkimonsuta sorted the above error. Originally i wasn't setting the enum id and the first enum id will be 0 which was causing the error.
BUT now i'm not getting any error and the enum tables are not being created.


feat: Does this module support multi-tenant MCA-E billing configuration

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
I know that the module is capable of vending subscriptions for a MCA contract where the MCA license is local to the tenant. The setup we are facing is that there is one MCA Billing Account defined in the "main/source" tenant, and we have several "destination" tenants that are part of this contract by way of invoice sections.
In the documentation for programatically creation of subscriptions across tenants in MCA scenario we learn that the subscription is to initially be provisioned in the source tenant and then be transferred (change ownership) to the destination tenant. In the API call to facilitate that I can see the following additional properties that need to be provided in the call
PUT https://management.azure.com/providers/Microsoft.Subscription/aliases/{{guid}}?api-version=2021-10-01
Authorization: Bearer {{access_token}}
Content-Type: application/json

{
  "properties": {
    "displayName": "{{subscription_name}}",
    "workload": "Production",
    "billingScope": "/billingAccounts/{{billing_account}}/billingProfiles/{{billing_profile}}/invoiceSections/{{invoice_section}}",
    "subscriptionId": null,
    "additionalProperties": {
      "managementGroupId": null,
      "subscriptionTenantId": "{{destination_tenant_id}}",
      "subscriptionOwnerId": "{{destination_service_principal_id}}"
    }
  }
}

I can see that the module does not support these additional properties (yet). On top of that the destination tenant principal with the right billing permissions needs to accept the ownership transfer using an API call, which in Terraform logic
We still would like to keep using this module but I fear we have to abandon it now for lack of the multi-tenant MCA configuration we are forcefully moved into as our procurement office without having a clue of the effects changed the contract from EA to MCA-E. Leaving us crippled as this broke our multi-tenant vending solution using this module.
Do you have any pointers for us on what we could do? Is MCA multi-tenant somewhere on the road map, so we could revert back to this module at some point?
Any comments / suggestions are appreciated
Describe the solution you'd like
I would like to see the multi-tenant MCA billing setup available in the module
Additional context

Hey @MarcelHeek,
This doc from the PG is a way to do it, but not the way ive done it with customers. after working with the MCA PG to discover a better way and more like the way it works on an EA.
They way to do it is as per below:

Create associated tenant link from primary tenant
In primary tenant invite user from associated tenant with billing owner (so they can grant RBAC to SPN later) on desired scope
User doesn't have to have a mailbox - use invite link instead via manage requests on billing profile/scope
Accept iniviation as invitied user in their home tenant
As newly invited user, grant single tenant SPN/App sub creator on desired billing profile/scope
Create subs as SPN/App etc.

Manage billing across multiple tenants - Microsoft Cost Management | Microsoft Learn
Let me know if this helps, as you can use this module then and just run the module with an identity with the SPN from each tenant and the sub will appear in each tenant as desired 👍

@jtracey93
Thanks....You saved the day. This works like a charm. The PG should update their documentation to provide this alternative method.


select macro

Both Tokio and futures-rs provide a select macro, they provide roughly the same functionality but have different implementations, APIs (in the mini-language supported), and constraints (notably, futures-rs requires futures to be fused).
There seems to be a lot of demand for select (and it is runtime-agnostic), so it is a good candidate for inclusion in std, rather than it being supplied with a runtime. However, there seem to be a lot of questions:

is it the right thing to support at all (c.f., race and complete macros, or other alternatives)?
should we require fusing futures? (I'm picking up a preference for not (the Tokio approach) but there is some discussion about whether that permits subtle footguns).
There may be questions about the interaction of select with cancellation. Looking at cancellation again is one of the goals of the ongoing async work (see, roadmap)

Note that since it is a macro, select is likely to be insta-stable. Also note that if we don't require fusing in select, then there is probably no reason for FusedFuture to exist at all.
Previous discussion:

Tokio PR
future-rs issue
user.r-l.o thread
StackOverflow question

A tiny improvement w.r.t. footguns could be to:

maybe make the if guard mandatory for non-FusedFutures
and/or some other way to express the intent that "I, as a user, hereby declare to be the one keeping track of completion". Even something as basic as an #[unfused] annotation or an .unfused() zero-cost adapter, or something along these lines.

I wrote an in-depth analysis of select! {} here: https://blog.yoshuawuyts.com/futures-concurrency-3/.


BUG: Unable to start docker-compose via CLI

Describe the bug
Trying to run the auto config version of docker-compose.yml via CLI using 'docker compose up' spits out the following errors:
PS C:\Snap Camera Server\snap-camera-server-3.1.1> docker compose up
parsing C:\Snap Camera Server\snap-camera-server-3.1.1\docker-compose.yml: yaml: unmarshal errors:
  line 27: mapping key "image" already defined at line 16
  line 28: mapping key "environment" already defined at line 17
  line 42: mapping key "ports" already defined at line 20
  line 45: mapping key "depends_on" already defined at line 22

However, using the Docker Desktop GUI, all containers start normally.
To Reproduce
Steps to reproduce the behavior:

Start Docker Desktop
Open PowerShell, cd to snap camera server
run 'docker compose up'
See errors

Expected behavior
All containers start up as normal, similar to using the Docker desktop GUI.
System (please complete the following information):

OS: Windows 11 Pro 22H2, build 22621.3007
Server Version: 3.1.1
Snap Camera Version: 1.21
Signature Patch applied: yes
Docker desktop: v4.25.1
Docker Compose: v2.23.0-desktop.1

Additional context
I used the auto config tool to set up this installation. This error is preventing me from automating the startup process.
This may be related to the following issues: https://github.com/docker/compose/issues/10394 and https://github.com/docker/compose/issues/10407
Docker Compose 2.16.0 and earlier handled merge keys differently than 2.17+.

Did you edit the file?
Looks like the file is corrupted.
Re-downloading the orignal file should help.


[#3378] aggregate agent's dataSource to show application's dataSource

Codecov Report

Merging #3431 into master will increase coverage by 0.3%.
The diff coverage is 77.81%.

@@            Coverage Diff            @@
##           master    #3431     +/-   ##
=========================================
+ Coverage   40.13%   40.43%   +0.3%
=========================================
  Files        2143     2160     +17
  Lines       70041    70561    +520
  Branches     9721     9764     +43
=========================================
+ Hits        28111    28532    +421
- Misses      39198    39283     +85
- Partials     2732     2746     +14

Impacted Files
Coverage Δ

...nt/web/service/stat/ApplicationCpuLoadService.java
0% <ø> (ø)

.../pinpoint/common/server/bo/stat/join/StatType.java
43.47% <ø> (ø)
:arrow_up:

...n/server/bo/codec/stat/join/DataSourceEncoder.java
0% <0%> (ø)

...ercorp/pinpoint/flink/dao/hbase/DataSourceDao.java
0% <0%> (ø)

...ercorp/pinpoint/flink/dao/hbase/StatisticsDao.java
0% <0%> (ø)
:arrow_up:

...oint/web/controller/ApplicationStatController.java
0% <0%> (ø)
:arrow_up:

...n/java/com/navercorp/pinpoint/flink/Bootstrap.java
0% <0%> (ø)
:arrow_up:

.../bo/serializer/stat/join/DataSourceSerializer.java
0% <0%> (ø)

...t/web/dao/hbase/HbaseApplicationDataSourceDao.java
0% <0%> (ø)

...mmon/server/bo/codec/stat/join/CpuLoadDecoder.java
100% <100%> (ø)
:arrow_up:

... and 54 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 9be29db...454b7b7. Read the comment docs.


ippserver: Duplicate "notify-lease-duration-default" attribute in printer-attributes-tag group

If you run ippserver with an appropriate configuration (sample configuration attached - unzip and run 'start-server.sh') and run the IPP Everywhere Self Certification test suite's "bonjour-tests.sh" script against it, test B-4 fails with the explanation 'Duplicate "notify-lease-duration-default" attribute in printer-attributes-tag group'.
Here is sample output:
neuromancer: sw-ippeveselfcert10-smitty [1662]$ ./bonjour-tests.sh 'IPP Everywhere Basic'
B-1. IPP Browse test: PASS
B-2. IPP TXT keys test: PASS
B-3. IPP Resolve test: PASS
B-4. IPP TXT values test: FAIL
"bonjour-value-tests.test":
Validate TXT record values using Get-Printer-Attributes              [FAIL]
RECEIVED: 7149 bytes in response
status-code = successful-ok (successful-ok)
Duplicate "notify-lease-duration-default" attribute in printer-attributes-tag group
B-5. TLS tests: SKIP
B-5.1 HTTP Upgrade test: SKIP
B-5.2 IPPS Browse test: SKIP
B-5.3 IPPS TXT keys test: SKIP
B-5.4 IPPS Resolve test: SKIP
B-5.5 IPPS TXT values test: SKIP
Summary: 10 tests, 3 passed, 1 failed, 6 skipped
Score: 90%
ippserver-ipp-everywhere-basic.zip

[master 3b5b992] Fix duplicate notify-lease-duration-default attribute (Issue #21)


Don't rotate to search card on single card removal

What
The carousel should stay on the same spot
https://user-images.githubusercontent.com/39344769/165889042-d818d5bb-c8b9-43d3-adbb-e7dd9e953b41.mp4

BEFORE:
Rotate to search card on removing a card
AFTER:
Rotate to N+1 card on removing the Nth card
Rotate to next to last card on removing the last card
TEST PROOF:
https://user-images.githubusercontent.com/87010739/167406110-2ace62a6-4bfc-42ee-bc67-46976970d299.mp4


[1.0.0] Required errors messages are no longer injected

Hi @sha256
Since version 1.0.0,  All errors messages are properly injected except for the required one.
Can you check please ?

Can you give me an example to check? I can see that it works properly here:
https://codepen.io/sha256/pen/JezmLp

Sorry for not being precise.
It's related to addValidator
Before 1.0.0, data-pristine-required-message was stronger than the message in addValidator, this is no longer valid since version 1.0.0.
Pristine.addValidator(
  'required',
  function(value) {
    if (this.type === 'radio' || this.type === 'checkbox') {
      return this.pristine.self.form.querySelector('[name="' + this.name + '"]:checked');
    } else {
      return value.trim() !== '';
    }
  },
  '',
  1,
  true

Change the line '' to false solves my problem
Pristine.addValidator(
  'required',
  function(value) {
    if (this.type === 'radio' || this.type === 'checkbox') {
      return this.pristine.self.form.querySelector('[name="' + this.name + '"]:checked');
    } else {
      return value.trim() !== '';
    }
  },
  false, <----- this line
  1,
  true
);

Sorry to have wasted your time and thank you for keeping this library alive!


PHP8 Support

CI job is missing; once added, it will show that we're blocked by https://github.com/getsentry/sentry-php/pull/1087

Hi @KartaviK, this is currently blocked by getsentry/sentry-php#1087, you can follow the progress there.


WFCORE-1797: Move temp file handling to SelfContainerServer

The temp files created in LaunchType.SELF_CONTAINED are now managed by the SelfContainedContainer.  Alongside I've added a SelfContainedContainer#stop() to explicitly manage the teardown lifecycle.

Added the i18n logging as requested


Personally Identifiable Information (PII) Detection cognitive skill samples return HTTPError: 400

The samples for input and output in cognitive-search-skill-pii-detection.md
are not correct and when we run them the server return HTTPError: 400 Client Error: Bad Request for url:

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

ID: a60412bb-3a94-59e2-ee26-f0f9d9922a60
Version Independent ID: e25ab48b-0ec4-9a13-8813-6ee3dd6ee78b
Content: PII Detection cognitive skill - Azure Cognitive Search
Content Source: articles/search/cognitive-search-skill-pii-detection.md
Service: cognitive-search
GitHub Login: @Careyjmac
Microsoft Alias: chalton

@squassina Could you please share the document you are referring to?

It's here: https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/search/cognitive-search-skill-pii-detection.md

@squassina  This is just a suggestion that may unblock you.  The PII skill is available through the Import Data wizard in the search service page in Azure portal.  The wizard creates all of the objects and object references.  You'll have to load your PII test data into an external file that the wizard (indexer) can read.  I think uploading to a blob container is always the simplest.  Hope that helps.

Thanks! I did that and it worked great!
I'm just puzzled about the difference between the inputs and outputs formats from one sample to the other. I'm still not sure what's the endpoint in the cognitive-search-skill-pii-detection.md as the samples from Quickstart: Detect Personally Identifiable Information (PII) or the API Reference Cognitive Services APIs Reference (microsoft.com)

Thanks! I did that and it worked great!
I'm just puzzled about the difference between the inputs and outputs formats from one sample to the other. I'm still not sure what's the endpoint in the cognitive-search-skill-pii-detection.md as the samples from Quickstart: Detect Personally Identifiable Information (PII) or the Cognitive Services APIs Reference (microsoft.com)

@squassina , the two documents you linked are for the Azure Cognitive Services API, not the Azure Cognitive Search skill API. The Cognitive Search skill does call the Cognitive Services API under the hood to retrieve the results, but as I mentioned in the PR you sent to attempt to fix this, the naming of the output fields does not match exactly as the skill was originally implemented using an earlier preview version of the Cognitive Services API that did have that naming, and we cannot change the naming in the skill without it being a breaking change to existing Search customers. Whenever possible we do our test to make sure our skills that call into Cognitive Services have the same API definition, but this is an unfortunate case where we have to deal with a difference due to the Cognitive Services API changing overtime but no easy way to transition existing Cognitive Search customers to the new contract due to the statefulness of skillsets and index definitions.
Hopefully that makes sense. We have been discussing ways to deal with adding incremental breaking changes to skills overtime such as this one but at this time we haven't bottomed out on a strategy on how to deal with this type of problem. I will be adding a link to this issue as an example of your completely understandable confusion to the work item so we can better prioritize it.

@squassina, if there are no more questions for this thread, I'll go ahead and close the issue.  Feel free to reopen or just repost if anything more comes up.
#please-close


Installation Problem

OS: Ubuntu 20.04.03
Docker version 20.10.21, build baeda1f
Steps Followed:
git clone https://github.com/VLSIDA/OpenRAM
cd OpenRAM/docker
make build

The error:
Removing intermediate container e34bca9e422a
 ---> 8c0cd8bb8731
Step 61/74 : COPY mrg.patch /root/magic
 ---> 9f7403a19450
Step 62/74 : RUN git apply mrg.patch
 ---> Running in 26066a2ba0f1
mrg.patch:10: space before tab in indent.
		    	if (idx < i || i == -1) i = idx;
error: patch failed: commands/CmdLQ.c:1745
error: commands/CmdLQ.c: patch does not apply
The command '/bin/sh -c git apply mrg.patch' returned a non-zero code: 1
docker tag  vlsida/openram-ubuntu:2022-11-03 vlsida/openram-ubuntu:latest
Error response from daemon: No such image: vlsida/openram-ubuntu:2022-11-03
make: *** [Makefile:11: build] Error 1

If I edit the docker file and add --reject --whitespace=fix to the git command. The error evolves into this:
Step 62/74 : RUN git apply --reject --whitespace=fix mrg.patch
 ---> Running in 5646a674572b
Checking patch commands/CmdLQ.c...
error: while searching for:
			if (sl->lab_flags & PORT_DIR_MASK)?
			{?
				idx = (int)sl->lab_port;?
				if (idx < i) i = idx;?
			}?
		}?
#ifdef MAGIC_WRAPPER?

error: patch failed: commands/CmdLQ.c:1745
error: while searching for:
			{?
				idx = (int)sl->lab_port;?
				if (idx > refidx)?
					if (idx < i) i = idx;?
			}?
		}?
#ifdef MAGIC_WRAPPER?

error: patch failed: commands/CmdLQ.c:1764
Applying patch commands/CmdLQ.c with 2 rejects...
Rejected hunk #1.
Rejected hunk #2.
The command '/bin/sh -c git apply --reject --whitespace=fix mrg.patch' returned a non-zero code: 1

The solution is to apply dos2unix to all files before compiling.
find /path -type f -print0 | xargs -0 dos2unix --

Nope. The line endings were correct in the repo. My git preferences were wonky.  Git automatically converts line endings if autocrlf = true is set in preferences. That was the case for me.
Changing my gitpereferences fixed it.
[core]
	autocrlf = false
	eol = lf


Mobius Logos

uploading Mobius logos.

Images have been added to the top level as I couldn't work out how to add a directory via a pull request.  Maybe create an images folder and move them? if you do the paths within the readme.md will need updating accordingly.

Thanks!  I'll merge and adjust the paths later.