[global] Broken build with migration of npm to yarn

It looks like the most recent commit (https://github.com/codefoundries/UniversalRelayBoilerplate/commit/ca818468513e5ac33a5b22053b4445a331c2c2aa) has broken a build with a fresh repo.
From a fresh pull:
yarn install v0.16.1
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
success Saved lockfile.
✨  Done in 93.41s.
shannon:spac-fusion-editor -> yarn dev
yarn dev v0.16.1
$ rm -rf build && concurrently --kill-others "npm run dev-webpack" "npm run dev-server" "npm run start"
[1]
[1] > @13.4.2 dev-server /Users/shannon/dev/andrew/spac/spac-fusion-editor
[1] > better-npm-run dev-server
[1]
[0]
[0] > @13.4.2 dev-webpack /Users/shannon/dev/andrew/spac/spac-fusion-editor
[0] > rm -rf build && better-npm-run dev-webpack
[0]
[2]
[2] > @13.4.2 start /Users/shannon/dev/andrew/spac/spac-fusion-editor
[2] > node node_modules/react-native/local-cli/cli.js start --reset-cache
[2]
[0] running better-npm-run in /Users/shannon/dev/andrew/spac/spac-fusion-editor
[1] running better-npm-run in /Users/shannon/dev/andrew/spac/spac-fusion-editor
[0] Executing script: dev-webpack
[0]
[0] to be executed: ./node_modules/.bin/webpack-dev-server --hot --inline --no-info --colors
[1] Executing script: dev-server
[1]
[1] to be executed: ./node_modules/.bin/nodemon --exec ./node_modules/.bin/babel-node -- ./server/server.js
[1] [nodemon] 1.11.0
[1] [nodemon] to restart at any time, enter `rs`
[1] [nodemon] watching: *.*
[1] [nodemon] starting `./node_modules/.bin/babel-node ./server/server.js`
[0] Running Webpack, process.env.NODE_ENV=undefined, version=<IP_ADDRESS>
[0]  http://localhost:8080/
[0] webpack result is served from http://undefined:8080/<IP_ADDRESS>/
[0] content is served from /Users/shannon/dev/andrew/spac/spac-fusion-editor
[1] { Error: ENOENT: no such file or directory, open '.env'
[1]     at Error (native)
[1]     at Object.fs.openSync (fs.js:640:18)
[1]     at Object.fs.readFileSync (fs.js:508:33)
[1]     at Object.config (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/dotenv/lib/main.js:30:37)
[1]     at Object.<anonymous> (/Users/shannon/dev/andrew/spac/spac-fusion-editor/server/log.js:9:21)
[1]     at Module._compile (module.js:556:32)
[1]     at loader (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/babel-register/lib/node.js:144:5)
[1]     at Object.require.extensions.(anonymous function) [as .js] (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/babel-register/lib/node.js:154:7)
[1]     at Module.load (module.js:473:32)
[1]     at tryModuleLoad (module.js:432:12) errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' }
[1] { Error: ENOENT: no such file or directory, open '.env'
[1]     at Error (native)
[1]     at Object.fs.openSync (fs.js:640:18)
[1]     at Object.fs.readFileSync (fs.js:508:33)
[1]     at Object.config (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/dotenv/lib/main.js:30:37)
[1]     at Object.<anonymous> (/Users/shannon/dev/andrew/spac/spac-fusion-editor/server/defaultRequestLoggerAuth.js:8:21)
[1]     at Module._compile (module.js:556:32)
[1]     at loader (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/babel-register/lib/node.js:144:5)
[1]     at Object.require.extensions.(anonymous function) [as .js] (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/babel-register/lib/node.js:154:7)
[1]     at Module.load (module.js:473:32)
[1]     at tryModuleLoad (module.js:432:12) errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' }
[1] undefined:1
[1] undefined
[1] ^
[1]
[1] SyntaxError: Unexpected token u in JSON at position 0
[1]     at Object.parse (native)
[1]     at Object.<anonymous> (/Users/shannon/dev/andrew/spac/spac-fusion-editor/server/defaultRequestLoggerAuth.js:11:25)
[1]     at Module._compile (module.js:556:32)
[1]     at loader (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/babel-register/lib/node.js:144:5)
[1]     at Object.require.extensions.(anonymous function) [as .js] (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/babel-register/lib/node.js:154:7)
[1]     at Module.load (module.js:473:32)
[1]     at tryModuleLoad (module.js:432:12)
[1]     at Function.Module._load (module.js:424:3)
[1]     at Module.require (module.js:483:17)
[1]     at require (internal/module.js:20:19)
[1] [nodemon] app crashed - waiting for file changes before starting...
[2] Scanning 1021 folders for symlinks in /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules (16ms)
[2]  ┌────────────────────────────────────────────────────────────────────────────┐
[2]  │  Running packager on port 8081.                                            │
[2]  │                                                                            │
[2]  │  Keep this packager running while developing on any JS projects. Feel      │
[2]  │  free to close this tab and run your own packager instance if you          │
[2]  │  prefer.                                                                   │
[2]  │                                                                            │
[2]  │  https://github.com/facebook/react-native                                  │
[2]  │                                                                            │
[2]  └────────────────────────────────────────────────────────────────────────────┘
[2] Looking for JS files in
[2]    /Users/shannon/dev/andrew/spac/spac-fusion-editor
[2]
[2] [Hot Module Replacement] Server listening on /hot
[2]
[2] React packager ready.
[2]
[2] jest-haste-map: @providesModule naming collision:
[2]   Duplicate module name: lodash
[2]   Paths: /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/react-native/node_modules/babel-core/node_modules/lodash/package.json collides with /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/react-native/node_modules/async/node_modules/lodash/package.json
[2]
[2] This warning is caused by a @providesModule declaration with the same name across two different files.
[2] jest-haste-map: @providesModule naming collision:
[2]   Duplicate module name: lodash
[2]   Paths: /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/react-native/node_modules/babel-register/node_modules/lodash/package.json collides with /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/react-native/node_modules/async/node_modules/lodash/package.json
[2]
[2] This warning is caused by a @providesModule declaration with the same name across two different files.
[2] [10/31/2016, 10:22:09 PM] <START> Initializing Packager
[2] [10/31/2016, 10:22:09 PM] <START> Building in-memory fs for JavaScript
[2] [10/31/2016, 10:22:10 PM] <END>   Building in-memory fs for JavaScript (695ms)
[2] [10/31/2016, 10:22:10 PM] <START> Building Haste Map
[2] [10/31/2016, 10:22:11 PM] <END>   Building Haste Map (755ms)
[2] [10/31/2016, 10:22:11 PM] <END>   Initializing Packager (1785ms)
^C[1] npm run dev-server exited with code null

Looks like maybe a yarn setup-local might do the trick from package.json.
shannon:spac-fusion-editor -> yarn setup-local
yarn setup-local v0.16.1
$ cp ./configuration/default.env ./.env && cp ./configuration/app/default.publicURL.js ./configuration/app/publicURL.js && npm run update-default-persister -- memory && npm run update-ip && react-native link

> @13.4.2 update-default-persister /Users/shannon/dev/andrew/spac/spac-fusion-editor
> babel-node ./scripts/update-default-persister.js "memory"

Written: /Users/shannon/dev/andrew/spac/spac-fusion-editor/configuration/graphql/defaultPersister.js

> @13.4.2 update-ip /Users/shannon/dev/andrew/spac/spac-fusion-editor
> babel-node ./scripts/update-ip.js

IP Address:<IP_ADDRESS>
fs.js:640
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open './ios/Rebar/AppDelegate.m'
    at Error (native)
    at Object.fs.openSync (fs.js:640:18)
    at Object.fs.readFileSync (fs.js:508:33)
    at updateIPInFile (/Users/shannon/dev/andrew/spac/spac-fusion-editor/scripts/update-ip.js:41:22)
    at Object.<anonymous> (/Users/shannon/dev/andrew/spac/spac-fusion-editor/scripts/update-ip.js:15:3)
    at Module._compile (module.js:556:32)
    at loader (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)

npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node/6.6.0/bin/node" "/usr/local/bin/npm" "run" "update-ip"
npm ERR! node v6.6.0
npm ERR! npm  v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! @13.4.2 update-ip: `babel-node ./scripts/update-ip.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @13.4.2 update-ip script 'babel-node ./scripts/update-ip.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel-node ./scripts/update-ip.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/shannon/dev/andrew/spac/spac-fusion-editor/npm-debug.log
error Command failed with exit code 1.

That runs into an error as well, looks like something to with Rebar.
I was able to get the app up and running after that though, even though it didn't complete successfully.
shannon:spac-fusion-editor -> yarn dev
yarn dev v0.16.1
$ rm -rf build && concurrently --kill-others "npm run dev-webpack" "npm run dev-server" "npm run start"
[0]
[0] > @13.4.2 dev-webpack /Users/shannon/dev/andrew/spac/spac-fusion-editor
[0] > rm -rf build && better-npm-run dev-webpack
[0]
[1]
[1] > @13.4.2 dev-server /Users/shannon/dev/andrew/spac/spac-fusion-editor
[1] > better-npm-run dev-server
[1]
[2]
[2] > @13.4.2 start /Users/shannon/dev/andrew/spac/spac-fusion-editor
[2] > node node_modules/react-native/local-cli/cli.js start --reset-cache
[2]
[1] running better-npm-run in /Users/shannon/dev/andrew/spac/spac-fusion-editor
[0] running better-npm-run in /Users/shannon/dev/andrew/spac/spac-fusion-editor
[1] Executing script: dev-server
[1]
[1] to be executed: ./node_modules/.bin/nodemon --exec ./node_modules/.bin/babel-node -- ./server/server.js
[0] Executing script: dev-webpack
[0]
[0] to be executed: ./node_modules/.bin/webpack-dev-server --hot --inline --no-info --colors
[1] [nodemon] 1.11.0
[1] [nodemon] to restart at any time, enter `rs`
[1] [nodemon] watching: *.*
[1] [nodemon] starting `./node_modules/.bin/babel-node ./server/server.js`
[2] Scanning 1021 folders for symlinks in /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules (31ms)
[2]  ┌────────────────────────────────────────────────────────────────────────────┐
[2]  │  Running packager on port 8081.                                            │
[2]  │                                                                            │
[2]  │  Keep this packager running while developing on any JS projects. Feel      │
[2]  │  free to close this tab and run your own packager instance if you          │
[2]  │  prefer.                                                                   │
[2]  │                                                                            │
[2]  │  https://github.com/facebook/react-native                                  │
[2]  │                                                                            │
[2]  └────────────────────────────────────────────────────────────────────────────┘
[2] Looking for JS files in
[2]    /Users/shannon/dev/andrew/spac/spac-fusion-editor
[2]
[2] [Hot Module Replacement] Server listening on /hot
[2]
[2] React packager ready.
[2]
[0] Running Webpack, process.env.NODE_ENV=undefined, version=<IP_ADDRESS>
[0]  http://<IP_ADDRESS>:8080/
[0] webpack result is served from http://<IP_ADDRESS>:8080/<IP_ADDRESS>/
[0] content is served from /Users/shannon/dev/andrew/spac/spac-fusion-editor
[2] jest-haste-map: @providesModule naming collision:
[2]   Duplicate module name: lodash
[2]   Paths: /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/react-native/node_modules/babel-register/node_modules/lodash/package.json collides with /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/react-native/node_modules/async/node_modules/lodash/package.json
[2]
[2] This warning is caused by a @providesModule declaration with the same name across two different files.
[2] jest-haste-map: @providesModule naming collision:
[2]   Duplicate module name: lodash
[2]   Paths: /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/react-native/node_modules/babel-core/node_modules/lodash/package.json collides with /Users/shannon/dev/andrew/spac/spac-fusion-editor/node_modules/react-native/node_modules/async/node_modules/lodash/package.json
[2]
[2] This warning is caused by a @providesModule declaration with the same name across two different files.
[2] [10/31/2016, 10:26:36 PM] <START> Initializing Packager
[2] [10/31/2016, 10:26:36 PM] <START> Building in-memory fs for JavaScript
[2] [10/31/2016, 10:26:37 PM] <END>   Building in-memory fs for JavaScript (725ms)
[2] [10/31/2016, 10:26:37 PM] <START> Building Haste Map
[2] [10/31/2016, 10:26:39 PM] <END>   Building Haste Map (1307ms)
[2] [10/31/2016, 10:26:39 PM] <END>   Initializing Packager (2415ms)
[1] info: Starting application name=urb, version=<IP_ADDRESS>, NODE_ENV=development, HOST=<IP_ADDRESS>, PORT=4444, PUBLIC_URL=http://localhost:4444, process_title=/usr/local/Cellar/node/6.6.0/bin/node, process_pid=2988, local_ip=<IP_ADDRESS>
[1] DEVELOPMENT. Server listening on <IP_ADDRESS>

So it looks like documentation or the build script might need to be updated, and also that issue with Rebar.

Sorry about the mix up. I will fix it up shortly. The documentation is indeed missing the step for setup-local. As for Rebar, this is just a mistake, it should say UniversalRelayBoilerplate.

I believe I fixed the issues, can you please try again?

Just retested, it seems like the order of setup should be:

git clone
yarn
yarn setup-local

Running yarn setup-local before yarn complained about missing dependencies (or at least it looks like that might be the issue).
shannon:spac-fusion-editor -> yarn setup-local
yarn setup-local v0.16.1
$ cp ./configuration/default.env ./.env && cp ./configuration/app/default.publicURL.js ./configuration/app/publicURL.js && npm run update-default-persister -- memory && npm run update-ip && react-native link

> @13.4.2 update-default-persister /Users/shannon/dev/andrew/spac/spac-fusion-editor
> babel-node ./scripts/update-default-persister.js "memory"

sh: babel-node: command not found

npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node/6.6.0/bin/node" "/usr/local/bin/npm" "run" "update-default-persister" "--" "memory"
npm ERR! node v6.6.0
npm ERR! npm  v3.10.7
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! @13.4.2 update-default-persister: `babel-node ./scripts/update-default-persister.js "memory"`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @13.4.2 update-default-persister script 'babel-node ./scripts/update-default-persister.js "memory"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel-node ./scripts/update-default-persister.js "memory"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/shannon/dev/andrew/spac/spac-fusion-editor/npm-debug.log
error Command failed with exit code 1.

After re-running in the order above everything completed successfully and the servers came up correctly from the looks of it.
Looks like just updating that last tidbit in the README to the correct order should resolve the remainder of the issues.
Thanks for the quick turn-around, much appreciated!
Andrew

Sorry about this, .md dyslexia. Thank you for catching it. Hope it goes smoother for you from here on.


Add "How it works" developer documentation

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 41.25%. Comparing base (8251cb3) to head (34e3144).
Report is 2 commits behind head on main.

:exclamation:  There is a different number of reports uploaded between BASE (8251cb3) and HEAD (34e3144). Click for more details.
HEAD has 3 uploads less than BASE

Flag
BASE (8251cb3)
HEAD (34e3144)

4
1

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #174       +/-   ##
===========================================
- Coverage   91.65%   41.25%   -50.41%
===========================================
  Files          37       36        -1
  Lines        1786     1515      -271
===========================================
- Hits         1637      625     -1012
- Misses        149      890      +741

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


Lua's script is pulled into ftdetec.vim

Warning:  I will close the bug issue without the minimal init.vim and the reproduce ways.
Originally, I thought it was a problem of orgmode, the way to reproduce is documented here https://github.com/nvim-orgmode/orgmode/issues/210
Problems summary
orgmode has a file named filetype.lua. When the plugin managed by dein,  it's loaded into .dein/ftdetect/ftdetect.vim, which leads to an error whenever opening the neovim.

Fixed.  Please use the latest.


Project refactor work

What I did with this PR:

bump go version to v1.21 align with kubernetes
Rename foler internal to pkg as kueue does
Remove *.out and add a .gitignore file to this project.
change repo name leader-worker-set to lws
fix test error

part of https://github.com/kubernetes-sigs/lws/issues/8

/easycla

cc @ahg-g can we merge?

cc @ahg-g can we merge?

the test is failing, how did you verify that it passes? does it pass for you locally?

cc @ahg-g can we merge?

the test is failing, how did you verify that it passes? does it pass for you locally?

Yes, the test is always failing, I'm try to dig the reason, but I ran locally yesterday, the lws works as expected.

Let me fix the error first.

/test pull-lws-test-main

/test pull-lws-test-main

Test error is not related to the controller logic. Add a flag -h to controller-gen solved this, have no idea why this happens, tracking here https://github.com/kubernetes-sigs/controller-tools/issues/888. cc @ahg-g

/lgtm
/approve
Thanks!

/label tide/merge-method-squash


Sign in with Google account ends up at localhost with 403 result

(Please ensure you are running the latest version of Cloud Tools for IntelliJ with Help > Check for Updates.)

Cloud Tools for IntelliJ version: 17.12.2
Google Cloud SDK version (run gcloud version on the command line): 183.0.0
OS: Linux - Fedora 27

What did you do?
Install Cloud Tools, restart IntelliJ and click "Sign in with Google account". Gave permission on the resulting website.
What did you expect to see?
See the granted permission be picked up by IntelliJ.
What did you see instead?
http://localhost:40085/Callback?code=XXXXXXX# with HTTP ERROR 413 and idle progress bar in IntelliJ
I've tried the same with a Google Core plugin in Android Studio 3.0.1 and the localhost URL also does not reach the IDE.

hi @rcgroot. do you mind trying again? It seems to be working now, so I just want to check to see if it was some intermittent failure you ran into. Thanks.

Hi @etanshaul still happening

Workaround: copy/paste the url and from commandline
# curl <url>
and it connects my account


Breaking Changes in Beeping

Hi there,
I'm glad to inform you about many new feature on Beeping ! But these feature made some little breaks in the API. Please check out the 0.5.0 changelog to fix the Python Structure you uses.
Thanks !

Hi,
I will check that and make the changes needed.
Thanks for the update.


Add distro and full stack integration tests

Also document how to change the backend host and port with the default recipe.

The full stack test set's up a minimal install nginx and just tests to make sure the index.html is being returned successfully and getting cached.


rtl props seems wrong typed

Hello
rtl props is typed as string but it seems it should be boolean to work with dir={rtl && 'rtl'}

I think in fact it should be dir={rtl === 'rtl'}. The type is right, the usage of the prop that is wrong

No I think the html props dir is waiting for rtl, ltr or auto but not a boolean.

I think the current prop type for rtl is correct

Its not correct, even if i pass ltr, it treats it as RTL
and if i dynamically change from RTL to LTR
there is a bug that lets the swiper overflow to the left

For far as I remember, swiper had this issue always...
For every project, I say I would never use this package and end up using it because I've no enough time to find a better one without any issue...
When you try to change the direction dynamically, it won't work, but it's fine with reload... please please please fix this issue. I'm dealing with this bug for 2 years and it's still there!!!


Add support for DYMO LabelWriter and Zebra label printers

Add support for DYMO LabelWriter and Zebra label printers
using https://github.com/michaelrsweet/lprint

Beware! Do not buy newer Dymo LabelWriter 5xx!

Louis Rossmann - Dymo printers are putting DRM in the paper
EEVblog 1462 - Why Dymo Label Printers SUCK!


"hatch env remove" leaves partial environment in place

Hatch environments created with hatch-pip-compile are not fully removed when running hatch env prune or hatch env remove. When entering the environment (for example with hatch shell) after running removal commands, the environment is not recreated and we enter a partial environment (no dependencies are installed except for Python itself).

Hmm... it seems like hatch env prune isn't doing exactly what I would expect it to while hatch env remove <envName> is:
❯ ls .venv/
hatch-pip-compile
❯ hatch env prune
❯ ls .venv/
hatch-pip-compile
❯ hatch env remove default
❯ ls .venv/
ls: .venv/: No such file or directory

Is this something you're able to replicate when using a virtual environment type instead of pip-compile type?

Thanks for checking!
You are right, hatch env remove works most of the time, but there is an edge case where it fails as well. I must have encountered that edge case during my initial test. You can reproduce it as follows:
[env]
requires = [ "hatch-pip-compile" ]

[envs.default]
type = "pip-compile"
pip-compile-constraint = "default"
dependencies = [ "pyinfra>=2.9" ]

[envs.dev]
extra-dependencies = [ "black" ]

> hatch --env default shell
(default) > pyinfra
Usage: pyinfra [OPTIONS] INVENTORY OPERATIONS...
Try 'pyinfra --help' for help.

Error: Missing argument 'INVENTORY'.
(default) > exit
> hatch --env dev shell
(dev) > exit
> hatch env remove default
> hatch env remove dev
> hatch --env default shell
(default) > pyinfra
bash: pyinfra: command not found

The hatch env remove dev command removes the dev environment, but at the same time creates a broken default environment. While trying to reproduce this edge case, I noticed that the pip-compile-constraint = "default" setting is responsible for the issue. When this setting is not present, hatch env prune works as well.

Oh very interesting! I think this is actually the same as https://github.com/juftin/hatch-pip-compile/issues/63
In order for the pip-compile-constraint feature to hatch-pip-compile has to check inside the constraint environment from whichever environment you're operating from. This is inadvertently creating the environment but not actually installing the dependencies into it.
I'll keep digging and get this fixed up. Thanks very much for reporting the issue.

:tada: This issue has been resolved in version 1.10.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Thanks @juftin, working as expected now 👍


Consolidate README setup instructions into Bash/Batch scripts

The README for the main page includes a number of step-by-step console instructions which could be consolidated into shell and/or batch scripts which the README could then direct the user to. This would declutter the README and abstract away some of the details of setup that the user might not need to see, and reduce the risk of them missing an instruction.
For example, here could be a file called setup.sh:
#!/bin/bash

# Exit script on error
set -e

# Check for virtualenv and install if not present
if ! command -v virtualenv &> /dev/null
then
    echo "virtualenv could not be found, installing..."
    pip install virtualenv
fi

# Create a virtual environment
virtualenv -p python3.9 venv

# Activate the virtual environment
source venv/bin/activate

# Install dependencies
pip install -r requirements.txt

echo "Setup complete."

And here could be a file called run.sh:
#!/bin/bash

# Exit script on error
set -e

# Activate the virtual environment
source venv/bin/activate

# Run the Python app
echo "Starting Python application..."
python3 app.py &

# Wait for the Python app to initialize
sleep 5

# Navigate to the client directory, install dependencies, and run the development server
echo "Setting up and starting the Vue app..."
cd client
npm install
npm run dev

Eh, in retrospect this would probably just add more clutter than it solves.


Error Expresion

Hi, view your main.js have a error expresión in 1 line (you have reuire) and I think it would be require, The code is still working but it is a syntax error
define(function (require, exports, module)

Hello ! Thx for posting this issue :)
This is a typing error that I will correct next commit !
However, I can't reproduce this error. I only can try on Windows right now.
Can you send me a screenshot, or the error explanation, and your OS version, please ?

This is the image in Linux, I use windows 10 and linux,  the explanation of the error is the syntax is badly writte, I hope this answer helps you

The 'reuire' that was a typing error as I already said, but it's not making an error into the Brackets webtools console that you can access here.

The other error I can see in your console (and mine now) is lint error, that not cause problem to the extension.


Errors building franka_ros2 in ros Iron

Hello,
Because of circunstances I have ros Iron installed and I tried to install franka_ros2 even if humble is the recommended one. So, I followed the steps in the tutorial adapting the steps to iron:
https://support.franka.de/docs/franka_ros2.html
sudo apt install -y libpoco-dev libeigen3-dev
git clone https://github.com/frankaemika/libfranka.git --recursive
cd libfranka
git switch 0.11.0
mkdir build && cd build
cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=OFF  ..
cmake --build . -j$(nproc)
cpack -G DEB
sudo dpkg -i libfranka-0.9.2-x86_64.deb

sudo apt install -y ros-iron-hardware-interface ros-iron-generate-parameter-library ros-iron-ros2-control-test-assets ros-iron-controller-manager ros-iron-control-msgs ros-iron-xacro ros-iron-angles ros-iron-ros2-control ros-iron-realtime-tools ros-iron-control-toolbox ros-iron-moveit ros-iron-ros2-controllers ros-iron-joint-state-publisher ros-iron-joint-state-publisher-gui ros-iron-ament-cmake ros-iron-ament-cmake-clang-format python3-colcon-common-extensions

mkdir -p ~/franka_ros2_ws/src

source /opt/ros/iron/setup.bash
cd ~/franka_ros2_ws
git clone https://github.com/frankaemika/franka_ros2.git src/franka_ros2
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release
source install/setup.sh

But somehow fails in joint_trayectory_controller and aborts franka_msgs. Can someone help me with this issue?
`colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release
source install/setup.sh
Cloning into 'src/franka_ros2'...
remote: Enumerating objects: 2149, done.
remote: Counting objects: 100% (692/692), done.
remote: Compressing objects: 100% (161/161), done.
remote: Total 2149 (delta 583), reused 585 (delta 525), pack-reused 1457
Receiving objects: 100% (2149/2149), 4.06 MiB | 2.01 MiB/s, done.
Resolving deltas: 100% (1262/1262), done.
[1.518s] WARNING:colcon.colcon_core.package_selection:Some selected packages are already built in one or more underlay workspaces:
	'joint_trajectory_controller' is in: /opt/ros/iron
If a package in a merged underlay workspace is overridden and it installs headers, then all packages in the overlay must sort their include directories by workspace order. Failure to do so may result in build failures or undefined behavior at run time.
If the overridden package is used by another package in any underlay, then the overriding package in the overlay must be API and ABI compatible or undefined behavior at run time may occur.

If you understand the risks and want to override a package anyways, add the following to the command line:
	--allow-overriding joint_trajectory_controller

This may be promoted to an error in a future release of colcon-override-check.
Starting >>> franka_msgs
Starting >>> franka_description
Starting >>> integration_launch_testing
Starting >>> joint_trajectory_controller
Finished <<< integration_launch_testing [0.91s]
Finished <<< franka_description [1.18s]
--- stderr: joint_trajectory_controller
In file included from /home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:37:
/opt/ros/iron/include/rclcpp/rclcpp/qos_event.hpp:18:2: warning: #warning This header is obsolete, please include rclcpp/event_handler.hpp instead [-Wcpp]
   18 | #warning This header is obsolete, please include rclcpp/event_handler.hpp instead
      |  ^~~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp: In member function ‘virtual controller_interface::CallbackReturn joint_trajectory_controller::JointTrajectoryController::on_configure(const rclcpp_lifecycle::State&)’:
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:685:26: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘desired’
  685 |   state_publisher_->msg_.desired.positions.resize(dof_);
      |                          ^~~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:686:26: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘desired’
  686 |   state_publisher_->msg_.desired.velocities.resize(dof_);
      |                          ^~~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:687:26: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘desired’
  687 |   state_publisher_->msg_.desired.accelerations.resize(dof_);
      |                          ^~~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:688:26: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘actual’
  688 |   state_publisher_->msg_.actual.positions.resize(dof_);
      |                          ^~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:692:28: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘actual’
  692 |     state_publisher_->msg_.actual.velocities.resize(dof_);
      |                            ^~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:697:28: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘actual’
  697 |     state_publisher_->msg_.actual.accelerations.resize(dof_);
      |                            ^~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp: In member function ‘void joint_trajectory_controller::JointTrajectoryController::publish_state(const JointTrajectoryPoint&, const JointTrajectoryPoint&, const JointTrajectoryPoint&)’:
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:912:28: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘desired’
  912 |     state_publisher_->msg_.desired.positions = desired_state.positions;
      |                            ^~~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:913:28: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘desired’
  913 |     state_publisher_->msg_.desired.velocities = desired_state.velocities;
      |                            ^~~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:914:28: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘desired’
  914 |     state_publisher_->msg_.desired.accelerations = desired_state.accelerations;
      |                            ^~~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:915:28: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘actual’
  915 |     state_publisher_->msg_.actual.positions = current_state.positions;
      |                            ^~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:919:30: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘actual’
  919 |       state_publisher_->msg_.actual.velocities = current_state.velocities;
      |                              ^~~~~~
/home/mikel/franka_ros2_ws/src/franka_ros2/joint_trajectory_controller/src/joint_trajectory_controller.cpp:924:30: error: ‘struct control_msgs::msg::JointTrajectoryControllerState_<std::allocator<void> >’ has no member named ‘actual’
  924 |       state_publisher_->msg_.actual.accelerations = current_state.accelerations;
      |                              ^~~~~~
gmake[2]: *** [CMakeFiles/joint_trajectory_controller.dir/build.make:76: CMakeFiles/joint_trajectory_controller.dir/src/joint_trajectory_controller.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:208: CMakeFiles/joint_trajectory_controller.dir/all] Error 2
gmake[1]: *** Waiting for unfinished jobs....
gmake: *** [Makefile:146: all] Error 2
---
Failed   <<< joint_trajectory_controller [10.5s, exited with code 2]
Aborted  <<< franka_msgs [15.0s]

Summary: 2 packages finished [16.3s]
  1 package failed: joint_trajectory_controller
  1 package aborted: franka_msgs
  1 package had stderr output: joint_trajectory_controller
  7 packages not processed
not found: "/home/mikel/franka_ros2_ws/install/joint_trajectory_controller/share/joint_trajectory_controller/local_setup.sh"
`

maybe try adding this line to the build argument --allow-overriding joint_trajectory_controller. Be aware we have not tested the packages with Iron, only Humble distro is officially supported.

Hi @mikelasa ,
did it work in the end? If not, please re-open the issue and find a solution :smile:


Website social prefixing https://

Observed/problematic behavior
When I set my website under Socials in Settings, it requires me to put https://srnyx.com rather than just srnyx.com
Then, when I go to my profile and click on the website button, it takes me to https://https://srnyx.com
Expected behavior
[1] The website field in settings shouldn't require https://, [2] the website button shouldn't prefix https://, or [3] it should be dynamic (if it doesn't have a protocol, add one, if it already has one, do nothing)
I think either 2 or 3 should be done, as since it's been requiring https:// this entire time, it would break everyone's current websites if 1 is done
Steps to reproduce

Add a website to your profile (it'll make you put https://)
Click the button (it'll take you to https://https://website.com)

Other
No response

prod DB has been adjusted


Consolidate Lanuages To Their Own Folders

-Put ENG and CHN in separate folders for ease of organization
-Revised links within structure to reflect the change.

@chuckn408 Thanks so much for your patch. but when I pushed this change to the wiki of drogon, all super links return 404 pages when I clicked them. Please do some tests to find a solution or I had to reverse those changes.
I did a little testing and it seems that GitHub's wiki does not require or support the path structure of pages. That is to say, even if I put a certain md file into a folder, there is no need to modify the reference connected to it on the wiki. It can also be found.


CRITICAL: gst_gl_window_show problem?

This is logged when using owr native API on iOS using Cerbero:
** (<unknown>:2335): CRITICAL **: gst_gl_window_show: assertion 'window_class->show != NULL' failed

Is this something that needs to be fixed? The video is shown.

This is fixed now here: http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/commit/?id=475dfaedc1f06904bed9f2c230cedc23b8c024a7
As you already guessed, it's not really a problem.


[Feature] Add a file tree browser to the 'Create' tab (2)

requires #185
This will entail adding the DirectoryTree to the 'Create' page. It should be aligned to the left of the page. We can start by it taking up to say roughly ~1/4 of the width of the page. We can remove the 'Create' text label that was used for testing in #185.
In terms of functionality, the two things we will want from this down the line are:

The top level folder (at least by default) should be the project name. It would be cool to just test this can be implemented by trying to configure it to default so that the top folder on the file tree is a specific folder. We can test this with a path on our individual local machines, then make a note of how this is done (if its possible). This will be difficult to test across PCs so we can just check if it's possible now, and if it's not make another issue.

We will (down the line) watch to fill the text input boxes with the folder names from the file tree brower. As a first instance, we can see if we can link a double-click event to folders on the directory tree. If a folder is double clicked, we can try to print the folder name to the console.

Overall we can:

remove the 'create' tab from #185
Add a DirectoryTree widget to the left of the page (taking up say 1/4 of it)
See if we can configure it such that the top folder displayed is of our choosing (by suppllying a path)
See if we can configure it so that double-clicking the name of a folder prints it to console
Add a .css file for this widget

For now, let's contain all the functional logic (e.g. for printing) in the same file as the widget. Later we will probably factor this out.

This will also be a good time to think about how / how much we need to test file-tree searches #65


Prometheus not monitoring Rancher Server

What did you do?
Deployed Prometheus/Grafana stak on a Rancher environment, on AWS.
What did you expect to see?
Prometheus collecting metrics from the Rancher Server as well (container and Rancher host metrics seem to work)
What did you see instead? Under which circumstances?
No data points collected in Rancher Stats dashboard.
Environment
Rancher Server:
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

"CATTLE_RANCHER_SERVER_VERSION=v1.6.14",

Rancher Host:
[rancher@rancher-node01 ~]$ cat /etc/os-release
NAME="RancherOS"
VERSION=v1.1.3
ID=rancheros
ID_LIKE=
VERSION_ID=v1.1.3
PRETTY_NAME="RancherOS v1.1.3"
HOME_URL="http://rancher.com/rancher-os/"
SUPPORT_URL="https://forums.rancher.com/c/rancher-os"
BUG_REPORT_URL="https://github.com/rancher/os/issues"
BUILD_ID=

[rancher@rancher-node01 ~]$ docker ps | grep -i rancher | awk '{print $2}'
rancher/scheduler:v0.8.3
infinityworks/prometheus-rancher-exporter:v0.22.52
rancher/lb-service-haproxy:v0.7.15
rancher/external-lb:v0.3.3
rancher/rancher-ecr-credentials:v2.0.1
rancher/net:v0.13.7
rancher/net:v0.13.7
rancher/net:v0.13.7
rancher/dns:v0.15.3
rancher/network-manager:v0.7.19
rancher/net:holder
rancher/healthcheck:v0.3.3
rancher/metadata:v0.9.5
rancher/agent:v1.2.9

System information:

Rancher Server:
$ uname -srm
Linux 4.4.0-1049-aws x86_64

Rancher Host:
[rancher@rancher-node01 ~]$ uname -srm
Linux 4.9.75-rancher x86_64

Prometheus version:
insert output of prometheus --version here

Alertmanager version:
insert output of alertmanager --version here (if relevant to the issue)

Prometheus configuration file:

insert configuration here

Alertmanager configuration file:

insert configuration here (if relevant to the issue)

Logs:

insert Prometheus and Alertmanager logs relevant to the issue here

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


Add support for disabling menu bar via settings.

This adds the ability for a user to completely disable the menu bar via editing the settings directly. This is to support a use-case that requires disabling most of the Cairo UI before instantiating alternate UI components.

Thanks for the PR! While this isn't a setting we wish to support, I can see valid use cases provided your replacement UI handles the necessary functionality. I am going to merge this with the understanding that since this is a hidden setting, it isn't going to be supported or tested by us, so it may break at any time or have unintended side effects (like our other hidden settings).
In the hopefully-near future we plan to extract the core shell services out from Cairo into a common library which might end up being a more appropriate base for your project, so keep a look out for that!


Add support to the animated_field! macro for tuple structs

What problem does this solve or what need does it fill?
Components like TextColor and BackgroundColor cannot currently be easily animated without creating a custom AnimatableProperty.
What solution would you like?
Add support to the animated_field! macro (and consequently AnimatedField) for tuple structs. I'm not sure what the cleanest way to do this is from an implementation perspective, since the $ident pattern doesn't match tuple struct field indices and I'm not sure if it makes sense to use $literal, as that matches more than just field indices.
What alternative(s) have you considered?

Add an alternative easy way to animate tuple structs (e.g. a separate macro/type)
Maybe something could be done with Deref and a blanket implementation of AnimatableProperty? But this puts the burden on components to implement Deref, only works for tuple structs with single fields, and also introduces potential conflicts with trait implementations because it would be a blanket implementation

Additional context
I was specifically trying to animate UI color alpha when I ran into this, and I wonder if it's worth considering if there should be easy ways to get a &mut to a Color's alpha and also possibly animate individual fields of a component's fields (e.g. animating Transform::translation::x), but that's a separate issue and probably a little more complicated.

Can you use _0 and so on? That's the field name of tuple structs.

_0 and friends don't seem to work with the macro, Rust complains about incorrect field names because the macro does field access via the provided field name.
You can try to construct an AnimatedField directly (the below compiles):
#[derive(Clone, Debug, Component, Reflect)]
struct MyTupleStruct(f32);

let mut clip = AnimationClip::default();
clip.add_curve_to_target(
    AnimationTargetId::from_name(&Name::new("target")),
    AnimatableCurve::new(
        AnimatedField::new_unchecked(
            "_0",
            |my_tuple_struct: &mut MyTupleStruct| &mut my_tuple_struct.0
        ),
        EasingCurve::new(0., 1., EaseFunction::Linear),
    )
);

...but running it panics because AnimatedField only supports non-tuple structs. I could probably draft a PR to make it possible to manually construct an AnimatedField (it seems like a trivial fix, just check for tuple structs as well), but I'm not as sure what the "correct" way to change the macro would be, or if changing AnimatedField would be useful without also fixing the macro.

Let's start with that and get more feedback in review.


colymba/gridfield-bulk-editing-tools has the wrong version on 6.0 branch

PR

https://github.com/silverstripe/supported-modules/pull/48
https://github.com/silverstripe/recipe-kitchen-sink/pull/79

PRs merged


Understanding type checker cache

Acknowledgement

[X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment
I've written a library that offers complex types, the in-editor performance used to be very poor (> 2sec to get autocompletion). While looking at the trace and the output of  --extendedDiagnostics, I noticed more than 4M+ instantiations. So I've started to dive deep down the performance of the lib and through many optimizations I managed to lower the instantiations to about 1.4M and autocompletion to something that feels ~200ms.
1.4M instantiations still feels quite high though, compared to other lib I've written, admittedly less complex.
So my question focuses on in-editor performance more than type-checking during build.

Is there a way to measure improvement made on cache usage ? I assume --extendedDiagnostics will show less instantiations, right ? The check time can vary quite a bit, making it difficult to know if we are moving in the right direction.

Given the following :

type Arg1 = { title: string };
type Arg2 = { title: string };

type AsArray<T> = T extends unknown ? [T] : never;

type Result1 = AsArray<Arg1>;
type Result1bis = AsArray<Arg1>;
type Result2 = AsArray<Arg2>;

Will the cache be used to evaluate Result1bis ? What about Result2 ? It's a different alias but it's exactly the same type.
I've read a bit of the compiler cache source code and I think it uses the type alias id so I would guess cache is used for Result1bis because it's the same type alias, but cache would not be used for Result2.

What about in a nested, conditional type ?

type Describe<T> =
  T extends string ? `string: ${T}` :
    T extends number ? `number: ${T}` :
    `unknown`
;

type DescribeAll<T> = T extends readonly [infer A] ? Describe<A> : never;

type Result1 = DescribeAll<['hi']>;
type Result2 = DescribeAll<[3, 'hi']>;

In this scenario, will the cache be used when evaluating Result2 ? Describe<'hi'> has already been evaluated before for Result1, so that step uses cache, right ?

Is there any particular condition that would prevent hitting the cache ?

Is there a way to measure improvement made on cache usage ? I assume --extendedDiagnostics will show less instantiations, right ?

Correct; the counts here are a good proxy for how much work is being saved/not-saved

Will the cache be used to evaluate Result1bis ? What about Result2 ? It's a different alias but it's exactly the same type.

There's no interning of "identical" object types, so computations on Arg1 and Arg2 will be independent (literal types are interned). Identical instantiations are cached, so Result1 and Result1bis will point to the same type.

In this scenario, will the cache be used when evaluating Result2 ? Describe<'hi'> has already been evaluated before for Result1, so that step uses cache, right ?

Yes (because literal types are interned)

Is there any particular condition that would prevent hitting the cache ?

This is pretty vague; I don't know how to give a useful answer

Yes (because literal types are interned)

So the following wouldn't hit the cache because the type arguments are objects ?
type Result3 = DescribeAll<[{ title: string }, { tags: string[] }]>;

This is pretty vague; I don't know how to give a useful answer

For example, for tail recursive evaluation to take place, the following conditions need to be met :

We tail-recurse for generic conditional types that (a) have not already been evaluated and cached, and
(b) are non distributive, have a check type that is unaffected by instantiation, or have a non-union check
type. Note that recursion is possible only through aliased conditional types, so we only increment the tail

Come on @typescript-bot !
For the following code, the number of instantiation increases by 4 each type I compute AsArray<Arg1>.
type Arg1 = { title: string };

type AsArray<T> = T extends unknown ? [T] : never;

type Result1 = AsArray<Arg1>; // Instantiations : 4
type Result2 = AsArray<Arg1>; // Instantiations : 8
type Result3 = AsArray<Arg1>; // Instantiations : 12

I expected the number of instantiation to stay exactly the same, but apparently the evaluation it's not skipped entirely.
So I ran the following :
type Describe<T> = T extends string
  ? `string: ${T}`
  : T extends number
    ? `number: ${T}`
    : `unknown`;

type DescribeAll<T extends ReadonlyArray<unknown>> = T extends [infer A, ...infer Rest]
  ? Describe<A> | DescribeAll<Rest>
  : never;

// 29 instantiations

type Result1 = DescribeAll<['hi']>; // + 42 (71)
type Result2 = DescribeAll<['hi']>; // + 13 (84)
type Result3 = DescribeAll<['hi']>; // + 13 (97)
type Result4 = DescribeAll<['John']>; // + 22 (119)
type Result5 = DescribeAll<['Doe']>; // + 22 (141)

type Obj = { title: string };
type Obj2 = { title: string };

type Result6 = DescribeAll<[Obj]>; // + 22 instantiations (163)
type Result7 = DescribeAll<[Obj]>; // + 15 instantiations (178)
type Result8 = DescribeAll<[Obj2]>; // + 22 instantiations (200)

So it looks like some things are cached. The first call to DescribeAll triggers 42 instantiations while subsequent calls with the same parameter cost only 13. Calls with a new string parameter cost 22 so I guess out of the 42 instantiations required to evaluate the type, 13 can't ever be cached, and 9 needs to be evaluate for each new parameter met.

So the following wouldn't hit the cache because the type arguments are objects ?

Correct, type literals will get their own ID and thus be a cache miss.
At the level of analysis you're doing here, I'd recommend setting a few breakpoints in tsc and stepping through it. It'll be much more instructive (and accurate!) than my prose.


ArcsLib.js must be loaded as a module

Note that debug mode is also available by adding debug parameter to the regular index.html URL (e.g. index.html?debug).
I'd like to deprecate the index.debug.html file in favor of the parameter, unless it would be inconvenient.

deprecating index.debug.html SGTM.


Fix social auth backend handling of attempts to login by deactivated users

We just got a report that while trying to login with our Google auth backend with an email address that has a deactivated account did something reasonable (took them back to /login with a clear error message), our GitHub backend took them back to /login and then redirected again to /accounts/go.  So it seems likely we have buggy error handling in SocialAuthBackend for this error situation.  We should investigate and fix.  Tagging as a priority because investigating this is probably a blocker for #11450.
@HarshitOnGitHub FYI.

@zulipbot claim

@zulipbot claim


Support automatic data volume expansion

Driver should be able to expand the volume size. With XFS Quotas it should be fairly easy.
Driver should:

Implement VolumeExpansion plugin capability.
Implement EXPAND_VOLUME controller capability or implement EXPAND_VOLUME node capability or both.

@tnozicka -- I was looking to use k8s-local-volume-provisioner in prod envs. Thought of having a look at this volumeExpansion. Does that mean currently we can't able expand the volumes once created via NodeConfig?
Any ETA on this feature? Thanks!

/remove-lifecycle stale
/triage accepted


Has default timeout of 4000ms

It looks like the library has 4000ms timeout by default:
https://github.com/tinylibs/tinyexec/blob/9bbc2b46287644b2473489cc57d8b6df6da163b8/src/main.ts#L50
It doesn't seem documented and caught me off guard when migrating from execa. Should it not have an opinionated timeout by default?

Also reported in https://github.com/antfu/install-pkg/pull/12
I agree there should not be a timeout by default

Do you plan to fix it soon? Otherwise I think I would need to revert https://github.com/antfu/install-pkg/pull/12 first

It can be worked around with { nodeOptions: { timeout: undefined } } so that it overrides the default.

Code was updated, but it will be another couple of days before a release can be made

Released in 0.2.0


Fix keystore exception.

Hi,
I got the following exception using your lib. (I've a Pixel 3XL running under Android 9 Pie):
W/KeyStore: KeyStore exception
    android.os.ServiceSpecificException:  (code 7)
        at android.os.Parcel.createException(Parcel.java:1964)
        at android.os.Parcel.readException(Parcel.java:1918)
        at android.os.Parcel.readException(Parcel.java:1868)
        at android.security.IKeystoreService$Stub$Proxy.get(IKeystoreService.java:786)
        at android.security.KeyStore.get(KeyStore.java:195)
        at android.security.keystore.AndroidKeyStoreSpi.engineGetCertificateChain(AndroidKeyStoreSpi.java:118)
        at java.security.KeyStoreSpi.engineGetEntry(KeyStoreSpi.java:484)
        at java.security.KeyStore.getEntry(KeyStore.java:1560)
        at duo.labs.webauthn.util.CredentialSafe.getKeyPairByAlias(CredentialSafe.java:177)
        at duo.labs.webauthn.Authenticator.makeCredential(Authenticator.java:171)
        at test.thavel.webauthn.MainActivity$register$1.run(MainActivity.kt:44)
        at java.lang.Thread.run(Thread.java:764)

Apparently, the proper way to get a private key from the Android keystore (since Android 9) is:
PrivateKey privateKey = (PrivateKey) keyStore.getKey("my-alias", null);

This PR actually fixes the exception.

Hey @thavel -- I'm about ready to merge this PR. The tests are all passing in my local repo. I'm curious where you found the recommendation to get the private key this way? All the KeyStore documentation I've read shows the "cast to PrivateKeyEntry, then getPrivateKey" method.
I've noticed the docs tend to be out of date and that calling getKey directly doesn't throw this exception, I'd just love to be able to link out to some official guidance.
Also FWIW, you should be able to use the library as-is -- this is a warning exception, so shouldn't actually stop control flow. Still would rather fix it!

Hey,
You're right, this actually doesn't affect the lib. I was struggling to make my app work and I ran into this issue thinking it could be the cause (well, actually, it wasn't).
Anyway, I found this answer, I read the official doc about getKey() to make sure it makes sense, then I tried it out and it worked.
I only got this warning on Android 9 though.


Error status code

It'd be great if API.responseErrorFromObject(object:) returned a NSHTTPURLResponse - it'd help to  validate HTTP status codes.

Or maybe return the status code.

Yes, we will add NSHTTPURLResponse to the arguments of responseErrorFromObject(_:).

NSHTTPURLResponse is now available in Request.responseFromObject(_:URLResponse:)!
https://github.com/ishkawa/APIKit/blob/a5c6faf2c1c68f56c180354101be5fa14d971ed9/APIKit/Request.swift#L39


Feature request: oncodrive return altered sample IDs

Dear @PoisonAlien,
I tried oncodrive() function today. I want to get the samples the driver exists, I found the function returns a column called AlteredSamples, so I think it is possible. Could you add this feature?
Best,
Shixiang

Hi @ShixiangWang
Actually you can run genesToBarcodes on genes of interest (in this case driver gene) and it should the job.

I got it, thanks :).


Build dynamic libs

Solve #4

It can successful compile a hello-world dynamically now:
inplace/bin/ghc-stage2 -dynamic --make ~/Desktop/Playground/Main.hs

@izgzhen Whoa, hang on, you're moving too fast! You were supposed to start yesterday, but you already resolved two main issues :D
I'll do my best to review both PRs tomorrow -- today's is a bit busy.

I'll do my best to review both PRs tomorrow -- today's is a bit busy.

:-) Take your time, thanks

Nice, looks a lot simpler than I imagined :-)
I've added a few minor comments.
Does this fully solve #4? I remember varous mysterious settings like DynamicGhcPrograms, DYNAMIC_TOO, etc. Also, what about Windows? Wasn't there a recent GHC patch that implemented dynamic way on Windows?

By the way, Linux CI fails.

By the way, Linux CI fails.

Ah, my bad, dylib is a mac OS thing, the Linux uses so

Also, what about Windows? Wasn't there a recent GHC patch that implemented dynamic way on Windows?

Including Windows, I will work on the platform thing soon

Including Windows, I will work on the platform thing soon

Well, I found that it is hard to test Windows-version on my machine for now. Can I leave it for future?

Well, I found that it is hard to test Windows-version on my machine for now. Can I leave it for future?

Yes, sure.

I remember varous mysterious settings like DynamicGhcPrograms, DYNAMIC_TOO

Relevant wiki:

https://ghc.haskell.org/trac/ghc/wiki/DynamicGhcPrograms
https://ghc.haskell.org/trac/ghc/wiki/DynamicLinkingDebate
https://ghc.haskell.org/trac/ghc/wiki/DynamicByDefault

Looks like this issue is around GHCi, a more specialized problem. I believe it is one of the dynamic way milestone tasks, but I prefer to submit a separate issue and PR for it.
Then how should I define this PR? "Build dynamic libs for GHC executable compilation"?

BTW, I should have fixed the Linux dynamic lib. The weird bit is, for object like rts/Adjust.dyn_o, the old system use ghc-stage2 to build it (the source is C and it works!), while our system will use Cc builder. So the ultimate .dyn_o is built by different commands, comparing my patch and the reference.

Looks like this issue is around GHCi, a more specialized problem. I believe it is one of the dynamic way milestone tasks, but I prefer to submit a separate issue and PR for it.

Yes, sounds good.

Then how should I define this PR? "Build dynamic libs for GHC executable compilation"?

Works for me!

I pushed the changes to follow the upstream change of dropping hoopl dependency in this PR as well. Should I open another PR for it?
Also, it should really work now, but both Linux and OS X CI timeout due to the lengthy process of building dynamic libs.

@izgzhen I'd prefer a separate PR for dropping hoopl.

but both Linux and OS X CI timeout due to the lengthy process of building dynamic libs

So, let's remove dynamic from quickest. We have a separate issue where we'll keep discussing this.

So, let's remove dynamic from quickest. We have a separate issue where we'll keep discussing this.

Done (quick still keeps it).

@izgzhen Thanks! Shall I merge this one too?

I've added a couple of more comments after looking through the code again.

Shall I merge this one too?

I am ready now, you may merge if as you see fit.

Thanks! Merged.


RequireNewInstance default value

Docs say that default value for RequireNewInstance is false.
I made some testing using connection string without specified RequireNewInstance and it seems like default is true.
Also I decompiled Microsoft.CrmSdk.XrmTooling.CoreAssembly and source code in CrmConnection.cs says that default is true

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

ID: acf4a7bc-1ccb-26e5-f9e8-85c2843e98b7
Version Independent ID: 64536f0c-1005-cd5c-9fdb-01c301108d46
Content: Use connection strings in XRM tooling to connect to Microsoft Dataverse (Dataverse) - Power Apps
Content Source: powerapps-docs/developer/data-platform/xrm-tooling/use-connection-strings-xrm-tooling-connect.md
Service: powerapps
GitHub Login: @Nkrb
Microsoft Alias: nabuthuk

You are correct @zzzzz0908 ,
We changed the default behavior of this flag in Nuget version <IP_ADDRESS> .
We will get this fixed in the docs.

Thanks for contacting us. We have updated the docs and pushed it live. Closing the issue. If you need further help, please reopen or create a new issue.


Color Button of Dialog Box is not changing

Hello Krish
I was working with another database using your last update of the dlls files, and I realize that the color of the button of the dialog box are not changing despite changing the colors:
gDll.ShowDialog(Me.Text2.value, vbInformation, "Title", "OK", "", "#A25151", "#FFFFFF")
gDll.ShowDialog(Me.Text2.value, vbInformation, "Title", "OK", "", "#00C851", "#FFFFFF")

Previous version, when changing the "ThemeBg" color, changed also the button color using the same color.
Maybe you can check out what's going on with this..
Thanks in advance.

Fixed. Update released


[bug] ast-grep prebuilt binaries are missing from release

⏯ Playground Link
N/A
💻 Code
N/A
🙁 Actual behavior
Only sg binaries are attached to releases.
https://github.com/ast-grep/ast-grep/releases/tag/0.22.0

🙂 Expected behavior
ast-grep binaries and sg binaries are both attached to releases (ideally bundled in a single zip file to reduce network bandwidth).
sg and ast-grep binaries behaves almost the same except sg --help / ast-grep --help. The usage output differs: Usage: sg <COMMAND>/Usage: ast-grep <COMMAND>. I might be missing other parts.
Also the VSCode extension searches for the ast-grep binary, not the sg binary, so I'll have to make sure I rename/copy the binary to ast-grep or set the astGrep.serverPath settings in vscode.
Alternatively, distributing only the ast-grep binary and let users set an alias would work too.
It's not a big deal but would be nice to make it work OOTB.

Fix this is too hard. installing from npm/cargo is recommended.

Thanks for taking a look!


Malformed json causes docmentation UI to hang

The JavaScript UI front end hangs with a parsing exception when it tries to parse malformed json. It should catch the exception and show it in the result box.
This was found by user @SuperJMN

VM21:1 Uncaught SyntaxError: Unexpected token F in JSON at position 4
at JSON.parse ()
at u. (easy-rpc-javascript.js:289)
at Array.forEach ()
at u.each (umbrella.min.js:2)
at HTMLButtonElement.executeMethod (easy-rpc-javascript.js:286)
at Function.handler (rivets.bundled.min.js:6)
at HTMLButtonElement. (rivets.bundled.min.js:6)

This is no longer applicable as version 5 uses swagger


Enable rule SA1629

Fix #1386

@akshay-zz Could you resolve the conflicts?

@akshay-zz Could you resolve the conflicts?

I have rebased the branch after pulling the latest master changes. Really confused why PR is showing differences from older commits. Although I have compared it with the latest master branch there is no difference other than changes related to SA1629. @kblok

@akshay-zz It seems the rebase was based on an old master branch. Fixed it :)


Easy to lose in-progress capture that only ends up in temp dir with :w

Describe the bug
If you have an in-progress capture, it can be very easy to lose it entirely. It seems to be recoverable as long as you don't close nvim, and know exactly what to do, but it doesn't seem intuitive to do so.
It appears that until you actually file the capture, it doesn't really live anywhere persistent (expected), even if you write the buffer (not expected).
Before you file or write with :w, if you use <TAB> from the agenda to open a different TODO, you'll get this error: [orgmode] vim/_editor.lua:341: nvim_exec2(): Vim(edit):E37: No write since last change (add ! to override). Similar story if you try to close the buffer or nvim as a whole. However, if you use :w, then that in-progress capture's buffer is allowed to close without being filed and without warning.
The buffer also seems to disappear entirely (ls! does not show it) when closed, which exacerbates the issue. I am not sure if this is just because it's unlisted or some other reason, but I was not able to identify a way to get this buffer back outside of manually identifying and opening the temp file. At that point, it's a plain file with no orgmode support (maybe a way to re-enable that?) but I think you'd have to manually file it.
If you don't do that, you will permanently lose that capture when nvim is closed as that temp file seems to get cleaned up.
The end result here is that I lost some notes for a meeting that, thankfully, I was just taking to get used to orgmode.
This is just one example workflow, but any way that you end up leaving nvim after saving an in-progress capture using :w will run into this, as the :w prevents any warnings.
Steps to reproduce
Edit: Keeping the below for posterity, but they don't actually reproduce the issue.
See https://github.com/nvim-orgmode/orgmode/issues/644#issuecomment-1879921992 for steps that actually reproduce.
The simplest workflow, I think:
1. Start a new capture with <leader>oc
2. Write the capture buffer with :w, noting the temp file name it is written to
3. Close nvim with :q
4. See that the temp file is gone, and the capture was never filed
Expected behavior
I think there are a couple of improvements that could potentially be made here:

Warn about any un-filed captures before overwriting the capture buffer (or allowing vim to close, if possible), regardless of whether they've been written to the temp file.
Make the capture buffers listed. This makes them way more discoverable and provides general benefits outside of just this problem.
Provide a command/keymap to get back to an in-progress capture with full orgmode support

Emacs functionality
No response
Minimal init.lua

local nvim_root = '/tmp/nvim_orgmode'
local lazy_root = nvim_root .. '/lazy'
local lazypath = lazy_root .. '/lazy.nvim'

-- Install lazy.nvim if not already installed
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    'git',
    'clone',
    '--filter=blob:none',
    'https://github.com/folke/lazy.nvim.git',
    '--branch=stable', -- latest stable release
    lazypath,
  })
end
vim.opt.rtp:prepend(lazypath)

require('lazy').setup({
  {
    'nvim-orgmode/orgmode',
    dependencies = {
      { 'nvim-treesitter/nvim-treesitter', lazy = true },
    },
    event = 'VeryLazy',
    config = function()
      -- Load treesitter grammar for org
      require('orgmode').setup_ts_grammar()

      -- Setup treesitter
      require('nvim-treesitter.configs').setup({
        highlight = {
          enable = true,
          additional_vim_regex_highlighting = { 'org' },
        },
        ensure_installed = { 'org' },
      })

      -- Setup orgmode
     require('orgmode').setup({
        org_agenda_files = nvim_root .. '/org/**/*',
        org_default_notes_file = nvim_root .. '/org/refile.org',
     })
    end,
  },
}, {
  root = lazy_root,
  lockfile = nvim_root .. '/lazy.json',
  install = {
    missing = false,
  },
})

require('lazy').sync({
  wait = true,
  show = false,
})

Screenshots and recordings
No response
OS / Distro
macOS 14.2
Neovim version/commit
v0.9.4
Additional context
Also reproduced in v0.9.2 on Windows 10

Are you sure, that the content of your capture window is really lost? The default behavior is, when the temporary capture file get's closed, the content is appended to your default notes file (see org_default_notes_file in the documentation).
I just tested, what you described:

Open a capture
Write some content and save with :w
Open the agenda, select an entry and open it in the capture window with
Look into my default notes file and, voila, the content I just wrote in the capture temporary file is there.

The "simplest" workflow you describe is actually the intended one:

Open a capture
Write some content, save and close the capture window with :wq or :w and :q (both is fine)
Open the default notes file and see the content appended at the end of the file

You can also have more complicated captures, where you explicitly state in the capture definition the target - the file, where the capture is moved into, and even - optionally - the headline, a section into which the capture is appended.
So I'm actually unable to reproduce the issue, you describe. Maybe you can double-check, if the content is really not refiled to your default note files and if so, give a more detailed step-by-step description, how to reproduce the error. And please ensure, that you have the latest master. I did some fixes in refiling recently.

Well, naturally I'm having trouble reproducing this in exactly the same way I listed in the reproduction steps. I'm not sure what I was seeing on Thursday, but I am still able to reproduce this a more complicated way (that I think is how I actually hit it in the real world). I may have just gotten confused and thought I'd reproduced it while trying to simplify the instructions - apologies for that.
Try these steps, using that same minimal config:

Create a todo using <leader>oc
Give it a title of "Test 1"
Save and file it
Create a second todo
Give it a title of "Test 2"
Save it with :w but don't close the buffer
Open the todo list with <leader>oa => t
Navigate to the first todo in the todo list and hit <TAB>
See that the "Test 2" buffer is replaced with the refile.org file contents, showing "Test 1"
Close nvim with :qa
See that refile.org contains only "Test 1" -- "Test 2" appears to be lost

Very interesting.
What actually happens is, that when I do step 4 to 10, that my refile.org get's somehow scrambled additionally to the lost content of the second capture buffer.
Thanks for pointing my nose to it, I will investigate this.

I created PR #647, which fixes this bug. @kristijanhusak I created it upon another PR (#641), so we either need to merge #641 first or we close it after merging #647 directly.

@seflue I tested against your fix branch and confirmed that this appears to be working as expected now. Thank you for the quick fix!


Random Server Crash 0.5.1-dev

Minecraft Version
1.20.1
Describe the Bug
While running the server randomly crashes and continues to crash once a chunk with some entity (not sure what) is loaded.
This was done in a modpack I'm working on. Crash report here https://pastebin.com/xd64g6xt
As a side note I was able to 'patch' this by adding the below in where the crash was happening.
if(blockEntity == null){
    return Blocks.AIR.defaultBlockState();
}

This was just a temporary workaround to get the world to load, I'm unsure if this is causing any unexpected behavior.
Reproduction Steps
The exact repo steps are unknown, this happened upon exploring a world for a while on the latest version
Expected Result
Server Doesn't crash
Screenshots and Videos
No response
Crash Report or Log
https://pastebin.com/xd64g6xt
Other Mods
See crash report, but there are a lot of them.
Mod Version
0.5.1
Forge Version
47.2.0

I can confirm this exact bug. Just received it myself. I have no idea what's causing it, but there's over half a dozen completely unrelated mods mentioned, and this is the first one mentioned.

Imcompatible with Computer Craft. I'll figure out a fix.

I feel a better fix here would be to fix DelegatingSmartTileEntity to return a sensible default value for getBlockState, rather than adding mixins to mods that call getBlockEntity within AttachCapabilitiesEvent.


Added input features

Fixed some bugs, added inputevent feature, and added activity manager class to broadcast intents into the device.

Thanks for your pr, it was rather long. I'll look into it shortly.

Fixed the whitespaces in code.
The reason for the flush is because closing the stream immediately after running executeShell seems to prevent the shell from running. Flushing the inputstream returned seemed to fix this. Added the flushStream function as a static method in the Stream class.
Added try-with-resource for as requested.
The original though with the keyinput interface was that you can simulate pressing multiple keys. I added the option to input multiple key codes using the manager interface you mentioned, and made the longPress() option into an actual key event that performs a long press on passed key codes.
Added BatteryManager class to handle usb connect/disconnect.
Reverted the apk install functions.

Thanks for the cleanup!
Regarding the API, it makes a lot of sense to be able to send a combination of keys and an optional long press flag. But it would be nice if the most common case - Single key is also very easy. How about we have two functions like so
KeyManager keys = new KeyManager(any);
keys.press(Keys.KEYCODE_POWER); // Single key press
keys.press(Keys.combination(Keys.A, Keys.B).longpress()); // Multiple keys and long press

Or something like that? Then the combination would be static in Keys class  and return a builder. The builder class would then need to be non-static to be able to access the execute (should probably be renamed) function in KeyManager.

The reason for the execute command was due to the input command allowing mouse, gamepad, trackball, etc. commands to be used. The idea was to be able to create an abstracted InputManager object that was prebuilt using a child class (KeyManager), and passing it around as needed to perform a the defined actions.
However, thinking about it further, I can create an InputEvent class that handles the execute, with an InputManager class creating each event, for example:
InputEvent powerButton = InputManager.createKeyEvent(Keys.KEYCODE_POWER);
InputEvent powerButtonLongPress = InputManager.createKeyEvent(Keys.KEYCODE_POWER, true);
InputEvent mouseLeftClick = InputManager.createMouseEvent(Mouse.LEFT_CLICK);

This way, the input events can be passed and changed in one location vs many if the same event is called multiple times (power button for example) or passed into a function that batches them.

Yeah, alright. I guess my main concern is I would like some class to act a bit like the PropertManager, ActivityManager or PackageManager already in jadb, whose job is to know how to execute a binary on the device. I would not like this logic to be inside some small class representing what key to press. Does this make sense? E.g. you can build up your events and then pass that to the EventManager (name just an example) that would know how to execute commands on the device.
Secondly I don't think the interface has to be too generic, it will just make it hard to use. I think we can have both things though, so that there can be a simple press method for convenience that would just build an event under the hood.

So I updated the input event handling as follows:
    InputManager inputManager = new InputManager(any);
    inputManager.sendEvent(KeyEvent.press(KeyCode.KEYCODE_POWER));

The manager takes a type of InputEvent, with KeyEvent as a subclass, in case someone decides to write a SwipeEvent class or TapEvent class to handle these other input types.

I will hopefully have unit tests done this weekend.

Sweet, no stress. Just ping me here and I'll merge if everything looks good. Double check whitespace, variable names, etc in unit tests for smooth merge. :+1:
Thanks again for this awesome contribution.

Closing this for now as we also go merge conflict :-/


Team member design enhancement

What would you like to share or ask?
In teams section  ui can be more attractive by hiding the social media handles of every member without hover and on hovering the name will be uplifted and the handles will appear.
I think this enhancement will make it better.
Please assign this issue to me under GSSoC'23.
Additional information
No response

please assign me this issue i will solve under GSSOC'23

@I-shika can you share some example or design on how do you plan on changing the UI

@karantec, Please look for any other issue. Thank you for contributing.

yes @prnvtripathi  the following image shows the ui in which first image is without hover and second one is on hover.
I want to do it in same way.


Cant vote, stake or withdraw rewards

Hi, I can't do anything on terra station wallet except of viewing ballance. Every action like voting, staking or rewards withdraw ends with error like below.

Is it something with network update and I have to wait for new station?

Hi, I was having a similar issue, I was getting a { "code" : 3 }.
What fixed the issue for me was disconnecting the wallet and connecting again.

In the top right corner of https://station.terra.money click on your wallet name and press 'Disconnect'
Click again in the same icon (this time it says 'Connect', instead of your wallet name) and choose your preferred wallet


Update repo README.md

Update Repository Readme
As a part of maintaining and improving the repository, I propose updating the README.md file with the newly added readme. This new readme includes the following updates:
Table of Contents added with links to each section
Detailed information about each semester with a table of programs
Information about contribution and contact
GitHub cards with License, Issues and Stargazers count
By updating the README.md file, it will help new users to easily understand the repository structure and its contents. Additionally, it will make the repository look professional and well-maintained.

Yeah sure @SarthakSKumar you can work on this issue


Update gdpr.md

I believe you mean, "EU" and not "UE".

@just-peteking Nice catch! Thank you for the PR.


Newbie question on how to setup splash landing page

I have setup basic remote_theme for my github pages
https://github.com/ilabs-llc/ilabs-llc.github.io
I added https://github.com/ilabs-llc/ilabs-llc.github.io/blob/master/_pages/splash-page.md
And then in my index.html specified the layout as splash. I was expecting now my landing page would be based on splash-page.md
Am I doing this correct ?. It still only shows my index.html
I am attempting to have my landing page look like https://mmistakes.github.io/minimal-mistakes/docs/layouts/#splash-page-layout

Okay found the answer myself.
I had to set the permalink: / in the splash-page.md file


[Service Bus] Remove dependency on ms-rest-nodeauth

With https://github.com/Azure/azure-sdk-for-js/issues/4508, we are now adding a dependency on @azure/core-http. The Service Bus library already pulls in @azure/ms-rest-js as a dependency. Since the two serve the same purpose, it took us down the road of trying to understand if we really need the @azure/ms-rest-js dependency.
Turns out the dependency on @azure/ms-rest-js dependency got introduced due to our need to type check the aad credentials via the @azure/ms-rest-nodeauth.
This issue is to track the work needed to remove the dependency on @azure/ms-rest-nodeauth which will result in avoiding the increase in the bundle size of the Service Bus library when we add core-http as part of #4508

done with #5010


'DeprecationWarning' for the use of 'Buffer without new'

The warning is as follows:

(node:18403) DeprecationWarning: Using Buffer without new will soon stop working. Use new Buffer(), or preferably Buffer.from(), Buffer.allocUnsafe() or Buffer.alloc() instead.

Caused by using fromFileWithPath and fromBufferWithName. I have not tested the other functions.

What node are you using?

Version 7.2.

Same issue.  I downgraded to the LTS version of node 6.9.1 and the message doesn't show up

I get the same warning. Node v7.2.0 Awesome lib, by the way, dbashford. Was about to begrudgingly write my own - lucky I found yours!

Node team has been tinkering with Buffer and decided to push this deprecation warning.  For more context, see https://github.com/nodejs/node/issues/9531
Many modules have been affected by this.  Supposedly it will be removed in 7.2.1: https://github.com/nodejs/node/pull/9529 so I think we can just wait it out

I'll take a look at this over the xmas break. Been slammed at work and had a 3rd kid a few months ago so my OSS time has been chopped to critical work related stuff.  I do want to jump back into this and get a worthy 2.0 out soon.

@dbashford  Congrats on the kid! you may need a new profile photo :D

I've verified this happens with 7.2.0 but does not with 7.2.1.
I ran the tests after having commented out every last bit of buffer stuff textract did and still got the error. And anyway, textract doesn't create buffers, it just uses the ones it is given.
I have updated all the dependencies to the latest, with the exception of got. I bumped that from 3.3.1 to 5.7.1 but not to 6+ because of its lack of lower node version support.  Can tackle that down the road a bit.
And I still get the deprecation. I suspect either a got update or some updates to downstream dependencies are necessary to remove the deprecation notice entirely.
Going to close this out as there isn't much I can do now, and what it is that I could do (hunt through the dependencies looking for the offender) isn't worth the effort, at least until this is a real problem and not just a now-deprecated deprecation. =)
Thanks for reporting it though! Gave me a reason to take a peek at how textract is doing in the 7s.


fix: apply transitions to the update selection

Contributes towards fixing https://github.com/d3fc/d3fc-series/issues/28
Also, the logic for transitionHasNonZeroDuration was incorrect - if transition was null this constant was evaluated to true.

I think the behavior of transitionHasNonZeroDuration was correct (at least that's how it's documented). I am a bit concerned as to why your change didn't break any unit tests though...
After looking at the other PRs, I would have expected an implementation along these lines -
        if (container.selection) {
            update = update.transition(container);
            enter.style('opacity', effectivelyZero)
                .transition(container)
                .style('opacity', 1);
            exit.transition(container)
                .style('opacity', effectivelyZero)
                .remove();
        } else {
            exit.remove();
        }

I assume I'm missing something though... :confused:


Implement filters and backend pagination on tables

After #136 is migrated, filter and backend pagination can be implemented.


Failed to start Dreamview

I am trying to run the Apollo on my system without any hardware. Therefore, I followed exact instructions as given in software installation guide.
Steps:

clone apollo repository
install docker.
Build and run apollo with following commands:
$ bash docker/scripts/dev_start.sh
$ bash docker/scripts/dev_into.sh
$ bash apollo.sh build_cpu
$ bash scripts/bootstrap.sh
My build for apollo got successful but after running bash scripts/bootstrap.sh I am getting the the error that apollo is failed to load. I tried to check logs but didn't found anything useful. I tried troubleshooting the problem as instructed by this link: https://github.com/ApolloAuto/apollo/blob/master/docs/howto/how_to_debug_dreamview_start_problem.md
But none of the solutions is working.
Whenever I am trying to open apollo in the browser it is giving an error that localhost refused to connect.

can someone provide me solution for the same. Am I missing something?
System information

**OS Platform and Distribution : Ubtuntu 14.04.6
Apollo Verison: 3.5

Supporting materials (screenshots, command lines, code/script snippets):

this what my logs looks like:

I also found this when I executed bash scripts/dreamview start_fe

Hi，AyushiRathore
I think I have a similar issue like you, and I did the following steps to fix it, I hope it can help you.
PC: intel i5-7500, 8G DDR4, integrated video card
OS: ubuntu 16.04
Version: apollo_5.0

open a teminal(named a) input:
$ bash docker/scripts/dev_start.sh
$ bash docker/scripts/dev_into.sh
$ bash apollo.sh build_cpu
$ bash scripts/dreamview.sh start_fe
input the ctrl+c into the teminal to stop the process when the teminal output stoped, shown in the figure。

open another teminal(named b), and input:
$ sudo apt-get install psmisc
$ sudo lsof -i :8888
in this step I have no result shown。
return to the teminal a, input:
$ bash scripts/dreamview.sh
I only got “Launched module dreamview”, but not the “Dreamview is running at http://localhost:8888”

$ cyber_recorder play -f docs/demo_guide/demo_3.5.record --loop
open Chrome and input the localhost:8888, then I got the Offline Demo.

Hi，I think I found the problem from https://github.com/ApolloAuto/apollo/issues/7228.
After I run the “git lfs fetch --all” , the Dreamview can start with no problem.

Hi Audier0879, could you give me some more information how you fixed the issue ?
I am having exactly the same issue,
I did
$ 'git lfs fetch --all'  on host
inside container
$ bash apollo.sh build_cpu
INFO: (07-12 16:43:43.421) Elapsed time: 8.771s, Critical Path: 0.01s
1============================
[ OK ] Build passed!
[INFO] Took 643 seconds
============================
seunghan@in_dev_docker:/apollo$ #
seunghan@in_dev_docker:/apollo$
seunghan@in_dev_docker:/apollo$ ls
BUILD            CPPLINT.cfg  README.md   WORKSPACE     apollo.doxygen  apollo_docker.sh  bazel-bin       bazel-out       cyber  docker  modules    py_proto         scripts      tools
CONTRIBUTING.md  LICENSE      RELEASE.md  WORKSPACE.in  apollo.sh       bazel-apollo      bazel-genfiles  bazel-testlogs  data   docs    nohup.out  readthedocs.yml  third_party
seunghan@in_dev_docker:/apollo$ bash scripts/bootstrap.sh
Module monitor is already running - skipping.
nohup: appending output to 'nohup.out'
Launched module dreamview.
Failed to start Dreamview. Please check /apollo/data/log or /apollo/data/core for more information
seunghan@in_dev_docker:/apollo$ bash scripts/dreamview.sh stop
[cyber_launch_24023] INFO Stop cyber launch finished.
[cyber_launch_24023] INFO cyber_launch exit.
Successfully stopped module dreamview.
seunghan@in_dev_docker:/apollo$ bash scripts/dreamview.sh start_fe
[cyber_launch_24393] INFO Launch file [/apollo/modules/dreamview/launch/dreamview.launch]
[cyber_launch_24393] INFO ========================================================================================================================
[cyber_launch_24393] INFO Load module [dreamview] binary: [/apollo/bazel-bin/modules/dreamview/dreamview --flagfile=/apollo/modules/common/data/global_flagfile.txt] [CYBER_DEFAULT] conf: [] exception_handler: [respawn]
[cyber_launch_24393] INFO Start process [/apollo/bazel-bin/modules/dreamview/dreamview --flagfile=/apollo/modules/common/data/global_flagfile.txt] successfully. pid: 24425
[cyber_launch_24393] INFO ------------------------------------------------------------------------------------------------------------------------

But I can not see anything on localhost:8888
System information
**OS Platform and Distribution : Ubtuntu 18.04
Apollo Verison: 3.5

I failed just because I didn't run the "git lfs fetch --all", so after run the command, everything is ok.
And do you have a try in ubuntu16.04?

Thanks @audier0879 ,
It seems that it was due to FMA/FMA3 instruction issue. My CPU is a Xeon E5-2650v2 which doesn't support FMA/FMA3 maybe..
xxxx@in_dev_docker:/apollo$ source scripts/apollo_base.sh;
xxxx@in_dev_docker:/apollo$ start_gdb dreamview
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /apollo/bazel-bin/modules/dreamview/dreamview...done.
(gdb) r
Starting program: /home/xxxx/.cache/bazel/_bazel_xxxx/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-dbg/bin/modules/dreamview/dreamview --flagfile=modules/dreamview/conf/dreamview.conf --log_dir=/apollo/data/log
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fff8deb0700 (LWP 22641)]
[New Thread 0x7fff8d6af700 (LWP 22642)]
[New Thread 0x7fff8aeae700 (LWP 22643)]
[New Thread 0x7fff886ad700 (LWP 22644)]
 :
Program received signal SIGILL, Illegal instruction.
0x00007fffe0073bec in double boost::math::detail::erf_inv_imp<double, boost::math::policies::policy<boost::math::policies::promote_float<false>, boost::math::policies::promote_double<false>, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy> >(double const&, double const&, boost::math::policies::policy<boost::math::policies::promote_float<false>, boost::math::policies::promote_double<false>, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy> const&, mpl_::int_<64> const*) () from /usr/local/lib/libpcl_sample_consensus.so.1.7
(gdb)

Thanks to the trouble shooting guide on FMA/FMA3 issue, now dreamview starts and I can see the UI.
https://github.com/ApolloAuto/apollo/blob/master/docs/howto/how_to_debug_dreamview_start_problem.md

Hi，AyushiRathore
I think I have a similar issue like you, and I did the following steps to fix it, I hope it can help you.
PC: intel i5-7500, 8G DDR4, integrated video card
OS: ubuntu 16.04
Version: apollo_5.0

open a teminal(named a) input:
$ bash docker/scripts/dev_start.sh
$ bash docker/scripts/dev_into.sh
$ bash apollo.sh build_cpu
$ bash scripts/dreamview.sh start_fe
input the ctrl+c into the teminal to stop the process when the teminal output stoped, shown in the figure。

open another teminal(named b), and input:
$ sudo apt-get install psmisc
$ sudo lsof -i :8888
in this step I have no result shown。
return to the teminal a, input:
$ bash scripts/dreamview.sh
I only got “Launched module dreamview”, but not the “Dreamview is running at http://localhost:8888”

$ cyber_recorder play -f docs/demo_guide/demo_3.5.record --loop
open Chrome and input the localhost:8888, then I got the Offline Demo.

Hello @audier0879  I followed your steps but got the following error:

@audier0879  I tried the solutions you suggested both the cyber_recorder command and by performing git lfs fetch --all but it is giving the following error:

Do you think that there can be issue with the PCL?

嗨，AyushiRathore
我想我有类似你的问题，我做了以下步骤来解决它，我希望它可以帮到你。
PC：intel i5-7500,8G DDR4，集成显卡
操作系统：ubuntu 16.04
版本：apollo_5.0

打开一个teminal（命名为a）输入：
$ bash docker
/ scripts / dev_start.sh
$ bash docker / scripts / dev_into.sh $ bash apollo.sh build_cpu
$ bash scripts / dreamview.sh start_fe
将ctrl + c输入到teminal 中当终端输出停止时停止该过程，如图所示。

打开另一个终端（名为b），并输入：
$ sudo apt-get install psmisc
$ sudo lsof -i：8888
在此步骤中我没有显示结果。
返回到终端a，输入：
$ bash scripts / dreamview.sh
我只有“推出模块dreamview”，但不是“Dreamview运行在http：// localhost：8888”
$ cyber_recorder play -f docs / demo_guide / demo_3 .5。记录 - 循环

打开Chrome并输入localhost：8888，然后我获得了离线演示。

Hello, have you installed Apollo 5.0? I have a question for you to help me.The docker compiled successfully and dreamview started successfully, but when localhost: 8888 was turned on, there was no response.

@audier0879 I tried the solutions you suggested both the cyber_recorder command and by performing git lfs fetch --all but nothing has changed it is still not opening and cyber_recorder is giving the following error:

Do you think that there can be issue with the PCL?

I think you can search the problem "cyber_recorder: command not found" in the issues search bar.

嗨，AyushiRathore
我想我有类似你的问题，我做了以下步骤来解决它，我希望它可以帮到你。
PC：intel i5-7500,8G DDR4，集成显卡
操作系统：ubuntu 16.04
版本：apollo_5.0

打开一个teminal（命名为a）输入：
$ bash docker
/ scripts / dev_start.sh
$ bash docker / scripts / dev_into.sh $ bash apollo.sh build_cpu
$ bash scripts / dreamview.sh start_fe
将ctrl + c输入到teminal 中当终端输出停止时停止该过程，如图所示。

打开另一个终端（名为b），并输入：
$ sudo apt-get install psmisc
$ sudo lsof -i：8888
在此步骤中我没有显示结果。
返回到终端a，输入：
$ bash scripts / dreamview.sh
我只有“推出模块dreamview”，但不是“Dreamview运行在http：// localhost：8888”
$ cyber_recorder play -f docs / demo_guide / demo_3 .5。记录 - 循环

打开Chrome并输入localhost：8888，然后我获得了离线演示。

Hello, have you installed Apollo 5.0? I have a question for you to help me.The docker compiled successfully and dreamview started successfully, but when localhost: 8888 was turned on, there was no response.

what is your browser，Microsoft IE or google chrome？

嗨，AyushiRathore
我想我有类似你的问题，我做了以下步骤来解决它，我希望它可以帮到你。
PC：intel i5-7500,8G DDR4，集成显卡
操作系统：ubuntu 16.04
版本：apollo_5.0

打开一个teminal（命名为a）输入：
$ bash docker
/ scripts / dev_start.sh
$ bash docker / scripts / dev_into.sh $ bash apollo.sh build_cpu
$ bash scripts / dreamview.sh start_fe
将ctrl + c输入到teminal 中当终端输出停止时停止该过程，如图所示。

打开另一个终端（名为b），并输入：
$ sudo apt-get install psmisc
$ sudo lsof -i：8888
在此步骤中我没有显示结果。
返回到终端a，输入：
$ bash scripts / dreamview.sh
我只有“推出模块dreamview”，但不是“Dreamview运行在http：// localhost：8888”
$ cyber_recorder play -f docs / demo_guide / demo_3 .5。记录 - 循环

打开Chrome并输入localhost：8888，然后我获得了离线演示。

Hello, have you installed Apollo 5.0? I have a question for you to help me.The docker compiled successfully and dreamview started successfully, but when localhost: 8888 was turned on, there was no response.

Google chrome

嗨，AyushiRathore
我想我有类似你的问题，我做了以下步骤来解决它，我希望它可以帮到你。
PC：intel i5-7500,8G DDR4，集成显卡
操作系统：ubuntu 16.04
版本：apollo_5.0

打开一个teminal（命名为a）输入：
$ bash docker
/ scripts / dev_start.sh
$ bash docker / scripts / dev_into.sh $ bash apollo.sh build_cpu
$ bash scripts / dreamview.sh start_fe
将ctrl + c输入到teminal 中当终端输出停止时停止该过程，如图所示。

打开另一个终端（名为b），并输入：
$ sudo apt-get install psmisc
$ sudo lsof -i：8888
在此步骤中我没有显示结果。
返回到终端a，输入：
$ bash scripts / dreamview.sh
我只有“推出模块dreamview”，但不是“Dreamview运行在http：// localhost：8888”
$ cyber_recorder play -f docs / demo_guide / demo_3 .5。记录 - 循环

打开Chrome并输入localhost：8888，然后我获得了离线演示。

Hello, have you installed Apollo 5.0? I have a question for you to help me.The docker compiled successfully and dreamview started successfully, but when localhost: 8888 was turned on, there was no response.

what is your browser，Microsoft IE or google chrome？

Google chrome

My dreamview has launched successfully after following the solution:
I installed PCL library and CPU does not support AVX instructions solution as given in the link below:
https://github.com/ApolloAuto/apollo/blob/master/docs/howto/how_to_debug_dreamview_start_problem.md
after this, my dreamview has been launched successfully !!

I also have the same problem, I tried the suggested solution to build pcl version 1.7.2 but inside docker I get error about boost library.
CMake Error at /usr/share/cmake-3.10/Modules/FindBoost.cmake:1947 (message):
  Unable to find the requested Boost libraries.

  Boost version: 1.65.1

  Boost include path: /usr/include

  Could not find the following Boost libraries:

          boost_system
          boost_filesystem
          boost_thread

I also have the same problem, I tried the suggested solution to build pcl version 1.7.2 but inside docker I get error about boost library.
CMake Error at /usr/share/cmake-3.10/Modules/FindBoost.cmake:1947 (message):
  Unable to find the requested Boost libraries.

  Boost version: 1.65.1

  Boost include path: /usr/include

  Could not find the following Boost libraries:

          boost_system
          boost_filesystem
          boost_thread

Have you tried updating your cmake. Because what I understood is that its not error of PCL its from cmake. This problem can also be there due to cmake version, in my case I used cmake 2.7

@AyushiRathore I updated the cmake and it works.


Unable to use scrollInto() method with bufferAmount prop

If i use a non-default value for bufferAmount, the scrollTo() doesn't work properly.
This code snippet return a wrong value:
var scrollTop = (Math.floor(index / d.itemsPerRow) * d.childHeight)
            - (d.childHeight * Math.min(index, this.bufferAmount));

I tested with 25 as bufferAmount and scrollTopwas equal zero
My this.calculateDimensions() returns this:
{
  "itemCount": 53,
  "viewWidth": 412,
  "viewHeight": 660,
  "childWidth": 360,
  "childHeight": 125,
  "itemsPerRow": 1,
  "itemsPerCol": 5,
  "itemsPerRowByCalc": 1,
  "scrollHeight": 6625
}

I've submitted a new version to npm with various bug fixes. Could you try that & see if it resolves your issue? If not, could you submit a code sample or create a stackblitz to help me troubleshoot it for you? Thanks.

Closing this since I haven't received a response from the original poster. Please re-open if you continue to experience this issue.