using create-react-app  typescript template app crashes during startup

Describe the bug
I'm attempting to run through a tutorial, so I start a new project with

npx create-react-app --template typescript
wait on install
set workspace typescript version (read solution in pinned issue)
Code shows no errors, I haven't changed anything from the template yet
npm start
wait for build
app crashes with error

Error looks like:
/Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/chokidar.js:17
throw new Error(
^

Error: No version of chokidar is available. Tried chokidar@2 and chokidar@3.
You could try to manually install any chokidar version.
chokidar@3: Error: Cannot find module 'chokidar'
Require stack:
- /Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/chokidar.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/DirectoryWatcher.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/watcherManager.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/watchpack.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/webpack/lib/node/NodeWatchFileSystem.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/webpack/lib/node/NodeEnvironmentPlugin.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/webpack/lib/webpack.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/react-scripts/scripts/start.js
chokidar@2: Error: Cannot find module 'watchpack-chokidar2'
Require stack:
- /Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/chokidar.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/DirectoryWatcher.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/watcherManager.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/watchpack.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/webpack/lib/node/NodeWatchFileSystem.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/webpack/lib/node/NodeEnvironmentPlugin.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/webpack/lib/webpack.js
- /Users/**/**/Learn/React/testing-hooks/node_modules/react-scripts/scripts/start.js

    at Object.<anonymous> (/Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/chokidar.js:17:7)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/Users/**/**/Learn/React/testing-hooks/node_modules/watchpack/lib/DirectoryWatcher.js:9:16)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/**/.npm/_logs/2020-11-25T23_46_23_673Z-debug.log

Did you try recovering your dependencies?

npm version: 6.14.9
Also, when removing and re-installing I got a lot of deprecation warnings, been a while since I spun up a fresh project so not sure if that's normal
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-babel.
npm WARN deprecated<EMAIL_ADDRESS>request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

><EMAIL_ADDRESS>postinstall /Users/**/**/Learn/React/testing-hooks/node_modules/babel-runtime/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /Users/**/**/Learn/React/testing-hooks/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

><EMAIL_ADDRESS>postinstall /Users/**/**/Learn/React/testing-hooks/node_modules/core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"

><EMAIL_ADDRESS>postinstall /Users/**/**/Learn/React/testing-hooks/node_modules/ejs
> node ./postinstall.js

Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)

npm notice created a lockfile as package-lock.json. You should commit this file.
added 1805 packages from 773 contributors and audited 1842 packages in 66.077s

120 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Which terms did you search for in User Guide?

No version of chokidar is available
chokidar
typescript

Environment

Environment Info:
current version of create-react-app: 4.0.1
running from /Users/**/.npm/_npx/19711/lib/node_modules/create-react-app
System:
OS: macOS 10.15.6
CPU: (4) x64 Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz
Binaries:
Node: 14.15.0 - ~/.nvm/versions/node/v14.15.0/bin/node
Yarn: Not Found
npm: 6.14.9 - ~/.nvm/versions/node/v14.15.0/bin/npm
Browsers:
Chrome: 87.0.4280.67
Edge: Not Found
Firefox: Not Found
Safari: 13.1.2
npmPackages:
react: ^17.0.1 => 17.0.1
react-dom: ^17.0.1 => 17.0.1
react-scripts: 4.0.1 => 4.0.1
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce

(Write your steps here:)
Same as description, this is a fresh install

npx create-react-app --template typescript .
npm start

Expected behavior

Template app starts
Actual behavior

Crash with error text from above.
Reproducible demo

Haven't changed a single thing from the template install, no real purpose in creating a repo.

If I npm i -D chokidar and then npm start it will load, so maybe just a missing dependency somewhere?

Yes installing it manually will solve this.
Don't start the server, first install it using
npm i -D chokidar
then
npm start

Yes installing it manually will solve this.
Don't start the server, first install it using
npm i -D chokidar
then
npm start

Yes, but that's not an optimal developer experience for a tool that is supposed to work out of the box. Thus a bug report.

Got the same issue for ubuntu 20.04
`/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/chokidar.js:17
throw new Error(
^
Error: No version of chokidar is available. Tried chokidar@2 and chokidar@3.
You could try to manually install any chokidar version.
chokidar@3: Error: Cannot find module 'chokidar'
Require stack:

/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/chokidar.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/DirectoryWatcher.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/watcherManager.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/watchpack.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/webpack/lib/node/NodeWatchFileSystem.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/webpack/lib/node/NodeEnvironmentPlugin.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/webpack/lib/webpack.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/react-scripts/scripts/start.js
chokidar@2: Error: Cannot find module 'watchpack-chokidar2'
Require stack:
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/chokidar.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/DirectoryWatcher.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/watcherManager.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/watchpack.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/webpack/lib/node/NodeWatchFileSystem.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/webpack/lib/node/NodeEnvironmentPlugin.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/webpack/lib/webpack.js
/home/owner/IdeaProjects/go-insurance/frontend/node_modules/react-scripts/scripts/start.js
at Object. (/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/chokidar.js:17:7)
at Module._compile (node:internal/modules/cjs/loader:1092:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
at Module.load (node:internal/modules/cjs/loader:972:32)
at Function.Module._load (node:internal/modules/cjs/loader:813:14)
at Module.require (node:internal/modules/cjs/loader:996:19)
at require (node:internal/modules/cjs/helpers:92:18)
at Object. (/home/owner/IdeaProjects/go-insurance/frontend/node_modules/watchpack/lib/DirectoryWatcher.js:9:16)
at Module._compile (node:internal/modules/cjs/loader:1092:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
npm ERR! code 1
npm ERR! path /home/owner/IdeaProjects/go-insurance/frontend
npm ERR! command failed
npm ERR! command sh -c react-scripts start
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/owner/.npm/_logs/2021-03-26T18_20_51_174Z-debug.log`

But I can't install chokidar
npm ERR! code EBADPLATFORM npm ERR! notsup Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin"} (current: {"os":"linux","arch":"x64"}) npm ERR! notsup Valid OS:    darwin npm ERR! notsup Valid Arch:  undefined npm ERR! notsup Actual OS:   linux npm ERR! notsup Actual Arch: x64
Please, need some help!

getting the same issue as above.. can anyone please look into of whats the cause ?
Compiled successfully!

You can now view webrms in the browser.

  Local:            http://localhost:3001
  On Your Network:  http://<IP_ADDRESS>:3001

Note that the development build is not optimized.
To create a production build, use npm run build.

/home/murtaza/umai/webrms/node_modules/watchpack/lib/chokidar.js:17
throw new Error(
^

Error: No version of chokidar is available. Tried chokidar@2 and chokidar@3.
You could try to manually install any chokidar version.
chokidar@3: Error: Cannot find module 'chokidar'
Require stack:
- /home/murtaza/umai/webrms/node_modules/watchpack/lib/chokidar.js
- /home/murtaza/umai/webrms/node_modules/watchpack/lib/DirectoryWatcher.js
- /home/murtaza/umai/webrms/node_modules/watchpack/lib/watcherManager.js
- /home/murtaza/umai/webrms/node_modules/watchpack/lib/watchpack.js
- /home/murtaza/umai/webrms/node_modules/webpack/lib/node/NodeWatchFileSystem.js
- /home/murtaza/umai/webrms/node_modules/webpack/lib/node/NodeEnvironmentPlugin.js
- /home/murtaza/umai/webrms/node_modules/webpack/lib/webpack.js
- /home/murtaza/umai/webrms/scripts/start.js
chokidar@2: Error: Cannot find module 'watchpack-chokidar2'
Require stack:
- /home/murtaza/umai/webrms/node_modules/watchpack/lib/chokidar.js
- /home/murtaza/umai/webrms/node_modules/watchpack/lib/DirectoryWatcher.js
- /home/murtaza/umai/webrms/node_modules/watchpack/lib/watcherManager.js
- /home/murtaza/umai/webrms/node_modules/watchpack/lib/watchpack.js
- /home/murtaza/umai/webrms/node_modules/webpack/lib/node/NodeWatchFileSystem.js
- /home/murtaza/umai/webrms/node_modules/webpack/lib/node/NodeEnvironmentPlugin.js
- /home/murtaza/umai/webrms/node_modules/webpack/lib/webpack.js
- /home/murtaza/umai/webrms/scripts/start.js

    at Object.<anonymous> (/home/murtaza/umai/webrms/node_modules/watchpack/lib/chokidar.js:17:7)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/home/murtaza/umai/webrms/node_modules/watchpack/lib/DirectoryWatcher.js:9:16)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)

    ```

Same issue, only difference is that I was actually able to run npm start once, after that, I could not start the development server anymore.

any update here?

bump

If it can help, I used to pack my project with npm v7.7.5 and I got my issue. When I start packing it with npm v6.14.4, I got no issues.

its something definitely wrong with npm 7.*.*  ..  i tried npm i --legacy-peer-deps and it worked for me...
however it should be like this and dependencies could handled.. havent tried removing node_modules and running npm i after it..


Local search box not show [Bug report]

Bug report
Local search box not show
Description
Search box for Local Search Index is not showing in the navbar.  I follow this document

Steps to reproduce

init vuepress 2 project
I am followed this document
add dependency

yarn add -D @vuepress/plugin-search

config search plugin

 plugins: [
        [
            '@vuepress/plugin-search'
        ]
    ]

Expected behavior

can seeing a  search box in navbar.
Screenshots

as you can see , there is no search box show in navbar.

Environment info

node version

v16.4.0

Browser: Firefox 89.0.1 (64-bit)
Output of vuepress info:

# Paste output of `vuepress info` here
System:
    OS: Linux 5.8 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (16) x64 Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz
    Memory: 11.01 GB / 62.73 GB
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 16.4.0 - /usr/bin/node
    Yarn: 1.22.10 - /usr/bin/yarn
    npm: 7.18.1 - /usr/bin/npm
  Utilities:
    Git: 2.32.0 - /usr/bin/git
  Browsers:
    Chrome: 91.0.4472.114
    Firefox: 89.0.1
  npmPackages:
    @vuepress/bundler-vite: Not Found
    @vuepress/bundler-webpack:  2.0.0-beta.19
    @vuepress/cli:  2.0.0-beta.19
    @vuepress/client:  2.0.0-beta.19
    @vuepress/core:  2.0.0-beta.19
    @vuepress/markdown:  2.0.0-beta.19
    @vuepress/plugin-active-header-links:  2.0.0-beta.19
    @vuepress/plugin-back-to-top:  2.0.0-beta.19
    @vuepress/plugin-container:  2.0.0-beta.19
    @vuepress/plugin-debug: Not Found
    @vuepress/plugin-docsearch: Not Found
    @vuepress/plugin-git:  2.0.0-beta.19
    @vuepress/plugin-google-analytics: Not Found
    @vuepress/plugin-medium-zoom:  2.0.0-beta.19
    @vuepress/plugin-nprogress:  2.0.0-beta.19
    @vuepress/plugin-palette:  2.0.0-beta.19
    @vuepress/plugin-prismjs:  2.0.0-beta.19
    @vuepress/plugin-pwa: Not Found
    @vuepress/plugin-pwa-popup: Not Found
    @vuepress/plugin-register-components: Not Found
    @vuepress/plugin-search: ^1.8.2 => 1.8.2
    @vuepress/plugin-shiki: Not Found
    @vuepress/plugin-theme-data:  2.0.0-beta.19
    @vuepress/plugin-toc: Not Found
    @vuepress/shared:  2.0.0-beta.19
    @vuepress/theme-default:  2.0.0-beta.19
    @vuepress/utils:  2.0.0-beta.19
    vue:  3.1.2
    vue-loader:  16.2.0
    vue-router:  4.0.10
    vuepress: ^2.0.0-beta.19 => 2.0.0-beta.19
    vuepress-vite: Not Found

package.json

"devDependencies": {
    "@vue/component-compiler-utils": "^3.2.2",
    "@vuepress/plugin-search": "^1.8.2",
    "@vuepress/shared-utils": "^1.8.2",
    "vuepress": "^2.0.0-beta.19"
  },

Use v2 with next gflag please

you mean yarn add -D vuepress@next ? i

I mean
yarn add -D @vuepress/plugin-search@next

Why do you think a next version plugin should be under the latest tag intead of  the same next flag.

Just a kind reminder, if you are not familiar with node and vue3, I personally do not recommand you to try things which has not yet touched stable.

It's works now. I didn't know the difference between the different tags and thought it should be backward compatible.
I am not familiar with vue3 , and  new to vuepress , so choose the latest version.
Thank you for you remind.

You can try vuepress@v1 (latest), which you would not likely to run in to some issues, and switch to v2 later when it is published as latest.


Bots order disorder

First, my english is not very well, sorry.
After update version <IP_ADDRESS>, i found the bots order changed.
I named the bots 1-9, before update when i doing !redeem, if bot 1 AlreadyOwned, bot 2 will do redeem,
But now, if bot 1 AlreadyOwned, bot 7 will do redeem.
!stautsall also like this.
Can we make the bots order like before? thanks!

ForwardKeysToOtherBots

Keep in mind that there is no fixed order of keys redeeming and it's up to ASF implementation which bot will receive forwarded key

This is not going to be corrected due to being required in much more efficient algorithm that is coming soon. If you expect from ASF to redeem key on bot X, then you should redeem it on bot X and not use ForwardKeysToOtherBots.
https://github.com/JustArchi/ArchiSteamFarm/wiki/Configuration


simplify not removing point that it should

Expected behavior and actual behavior.
simplify is not removing some points that it definitely should
Steps to reproduce the problem.
from shapely.geometry.polygon import Polygon

polygon = [[-156.01, 19.62], [-156.03, 19.66], [-156.05, 19.70], [-156.01, 19.78], [-156.01, 19.70], [-156.01, 19.62]]

before = Polygon(polygon)
after = before.simplify(1e-5)
print(len(before.exterior.coords), len(after.exterior.coords), before.is_valid, after.is_valid)

Expected: 2nd and 5th point should be removed by simplify
Actual: Only 2nd point is removed
Operating system
macOS 10.15.6
Shapely version and provenance
shapely: 1.7.1
python: 3.8.2

This is an upstream bug with GEOS, with the same behavior with JTS.
The issue is that simply does not remove the start/end of a LinearRing. This can be resolved with a function that calls "simplify" twice on LinearRings, shown here (but not rigorously tested):
def simplify2(geom, dist):
    if geom.geom_type == 'LinearRing':
        geom = geom.simplify(dist)
        return LinearRing(geom.coords[1:]).simplify(dist)
    elif geom.geom_type == 'Polygon':
        exterior = simplify2(geom.exterior, dist)
        interiors = [simplify2(interior, dist) for interior in geom.interiors]
        return Polygon(exterior, interiors)
    elif (geom.geom_type.startswith('Multi')
            or geom.geom_type == 'GeometryCollection'):
        return type(geom)([simplify2(part, dist) for part in geom.geoms])
    else:
        return geom.simplify(dist)

after = simplify2(before, 1e-5)
print(after)
# POLYGON ((-156.05 19.7, -156.01 19.78, -156.01 19.62, -156.05 19.7))


ffi: Handle invalid encoded floats in decode_float_var

Description

decode_float_var assumed all eight-byte encoded floats given as input would be valid, but in practice, this is not true if the encoded data was corrupted. This PR adds handling for such values.
Validation performed

Added new unit tests and validated all unit tests passed.

macOS build failure not caused by this change. Will resolve in another PR.


Toolset for experiment 2

This PR updates ITN toolset with the following commands:

slots-won: to query slots won by a node
reset-gating: to reset gating config of a node
isolate: to isolate a set of nodes to form an isolated cluster
allocate-slots: to split block producers into distinct groups of nodes with roughly equal occupation of slot per group (or a desired proportion)

Explain how you tested your changes:

Slot allocation algorithm is covered with test
Tooling was tested manually on a private cluster

Checklist:

[x] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? List them

Closes #12829
Closes #12843

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!approved-for-mainnet


fix(KFLUXBUGS-1614): fbc pipeline should stop passing binaryimage to iib

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Issue ticket number and link
Type of change

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/retest

/retest

/retest

/lgtm

/retest

@jinqi7 I saw your lgtm but not sure why is this still pending for the Tide test. Can you take a look?

/approve

/hold
In case it's merged without being rebased

@jinqi7 should we add /retest then to make sure the latest version was validated?

@jinqi7 should we add /retest then to make sure the latest version was validated?

I am sure I updated the test file recently. The content in the PR was submitted before my recent PR.  I am not sure if the test can pass with adding "/retest". Since the PR is not large, it's better to rebase in case the old version is merged.

@jinqi7 should we add /retest then to make sure the latest version was validated?

I am sure I updated the test file recently. The content in the PR was submitted before my recent PR. I am not sure if the test can pass with adding "/retest". Since the PR is not large, it's better to rebase in case the old version is merged.

we don't need to rebase, the PR gets rebased as a part of the test workflow, so retest should be sufficient IMO

/retest

@jinqi7 should we add /retest then to make sure the latest version was validated?

I am sure I updated the test file recently. The content in the PR was submitted before my recent PR. I am not sure if the test can pass with adding "/retest". Since the PR is not large, it's better to rebase in case the old version is merged.

we don't need to rebase, the PR gets rebased as a part of the test workflow, so retest should be sufficient IMO

You mean the PR get rebased in the test.  When it's merged, will the rebased content be merged?

@jinqi7 should we add /retest then to make sure the latest version was validated?

I am sure I updated the test file recently. The content in the PR was submitted before my recent PR. I am not sure if the test can pass with adding "/retest". Since the PR is not large, it's better to rebase in case the old version is merged.

we don't need to rebase, the PR gets rebased as a part of the test workflow, so retest should be sufficient IMO

You mean the PR get rebased in the test. When it's merged, will the rebased content be merged? I saw the whole test file from the PR, the newly updated content is not there.

it doesn't matter IMO, if there were no conflicts during rebase within the test, we can be sure that the test was using latest code

/unhold
/retest

all passed, can you "lgtm" @jinqi7

/lgtm


Updates for jenkins2, lets avoid using a poststart script now that we can add libraries to a Jenkinsfile with @LIbrary

[merge]


New HelloWorld by Prakher

Please don't change the existing programs to just add text, and please keep the naming consistent if you're adding new programs for existing languages.


Fully implement battery status

Both check for battery status on an interval as well as check for battery status as a result of checking current lock status

Would it be possible to allow configuring to expose just the battery? I'm happy with the lock operation via HomeKit currently and would just need a battery level check via HomeBridge?


Cleaned up some code from gameserver class on bootstrap method.

Split some massiv code into smaller methodes from massiv bootstrap method.
And also add java documentation to the splitted methods.
A rework is planned to the future of 2.2.0/1. This is only a pr for improve legibility of the class.

Please test these changes (including downloading plugins from the master and a url) and add documentation.
After this I am sure we can merge this

Ok, i can do this

Test Passed:

[X] Download Plugin from URL(ProtocolSupport from CI)
[X] Download Master Template
[X] Download URL Template


Add an option to wait for custom startup script to finish before launching the agent

Fixes https://github.com/jenkinsci/google-compute-engine-plugin/issues/338
Adds a new option to the instance configuration that enables waiting to launch the agent until google-startup-scripts has finished running.

Agent log - launcher checks startup status and it's already done

Jul 19, 2022 9:48:14 PM null
FINEST: Instance vl843h is running and ready...
Jul 19, 2022 9:48:14 PM null
INFO: Launching instance: vl843h
Jul 19, 2022 9:48:14 PM null
INFO: bootstrap
Jul 19, 2022 9:48:14 PM null
INFO: Getting keypair...
Jul 19, 2022 9:48:14 PM null
INFO: Using autogenerated keypair
Jul 19, 2022 9:48:14 PM null
INFO: Authenticating as jenkins
Jul 19, 2022 9:48:14 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 9:48:24 PM null
INFO: Failed to connect via ssh: The kexTimeout (10000 ms) expired.
Jul 19, 2022 9:48:24 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 9:48:29 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 9:48:37 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 9:48:37 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 9:48:42 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 9:48:42 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 9:48:42 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 9:48:47 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 9:48:47 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 9:48:47 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 9:48:52 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 9:48:52 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 9:48:52 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 9:48:57 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 9:48:57 PM null
INFO: Connected via SSH.
Jul 19, 2022 9:48:57 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 9:48:58 PM null
INFO: Configured startup script is finished.
Jul 19, 2022 9:48:58 PM null
INFO: Verifying: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -fullversion
openjdk full version "11.0.7+10-post-Ubuntu-2ubuntu218.04"
Jul 19, 2022 9:48:58 PM null
INFO: Copying agent.jar to: /var/lib/jenkins/workspace
Jul 19, 2022 9:48:58 PM null
INFO: Launching Jenkins agent via plugin SSH: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -jar /var/lib/jenkins/workspace/agent.jar
<===[JENKINS REMOTING CAPACITY]===>Remoting version: 4.10.1
This is a Unix agent
Evacuated stdout
Agent successfully connected and online

Agent log - launcher checks startup status and it's sleeping for 60s

Jul 19, 2022 10:46:51 PM null
FINEST: Instance 3pi9fj is running and ready...
Jul 19, 2022 10:46:51 PM null
INFO: Launching instance: 3pi9fj
Jul 19, 2022 10:46:51 PM null
INFO: bootstrap
Jul 19, 2022 10:46:51 PM null
INFO: Getting keypair...
Jul 19, 2022 10:46:51 PM null
INFO: Using autogenerated keypair
Jul 19, 2022 10:46:51 PM null
INFO: Authenticating as jenkins
Jul 19, 2022 10:46:51 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:47:01 PM null
INFO: Failed to connect via ssh: The kexTimeout (10000 ms) expired.
Jul 19, 2022 10:47:01 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:47:06 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:47:07 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 10:47:07 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:47:12 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:47:12 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 10:47:12 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:47:17 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:47:17 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 10:47:17 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:47:22 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:47:22 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 10:47:22 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:47:27 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:47:28 PM null
INFO: Connected via SSH.
Jul 19, 2022 10:47:28 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:47:28 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:47:28 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:47:33 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:47:33 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:47:33 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:47:38 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:47:38 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:47:38 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:47:43 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:47:43 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:47:43 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:47:48 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:47:48 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:47:48 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:47:53 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:47:53 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:47:53 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:47:58 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:47:58 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:47:58 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:48:03 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:48:03 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:48:03 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:48:08 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:48:08 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:48:08 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:48:13 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:48:13 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:48:13 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:48:18 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:48:18 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:48:18 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:48:23 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:48:23 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:48:23 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:48:28 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:48:28 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:48:28 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:48:33 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:48:33 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:48:33 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:48:38 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:48:38 PM null
WARNING: google-startup-scripts has not finished
Jul 19, 2022 10:48:38 PM null
INFO: Waiting for the startup script to finish. Sleeping 5.
Jul 19, 2022 10:48:43 PM null
INFO: Verifying: exit $(systemctl show google-startup-scripts --property ExecMainExitTimestampMonotonic | cut -d "=" -f 2)
Jul 19, 2022 10:48:43 PM null
INFO: Configured startup script is finished.
Jul 19, 2022 10:48:43 PM null
INFO: Verifying: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -fullversion
openjdk full version "11.0.7+10-post-Ubuntu-2ubuntu218.04"
Jul 19, 2022 10:48:43 PM null
INFO: Copying agent.jar to: /var/lib/jenkins/workspace
Jul 19, 2022 10:48:43 PM null
INFO: Launching Jenkins agent via plugin SSH: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -jar /var/lib/jenkins/workspace/agent.jar
<===[JENKINS REMOTING CAPACITY]===>Remoting version: 4.10.1
This is a Unix agent
Evacuated stdout
Agent successfully connected and online

Agent log - option disabled and launcher does not check startup status

Jul 19, 2022 10:54:22 PM null
FINEST: Instance o8pom3 is running and ready...
Jul 19, 2022 10:54:22 PM null
INFO: Launching instance: o8pom3
Jul 19, 2022 10:54:22 PM null
INFO: bootstrap
Jul 19, 2022 10:54:22 PM null
INFO: Getting keypair...
Jul 19, 2022 10:54:22 PM null
INFO: Using autogenerated keypair
Jul 19, 2022 10:54:22 PM null
INFO: Authenticating as jenkins
Jul 19, 2022 10:54:22 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:54:32 PM null
INFO: Failed to connect via ssh: The kexTimeout (10000 ms) expired.
Jul 19, 2022 10:54:32 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:54:37 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:54:38 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 10:54:38 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:54:43 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:54:43 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 10:54:43 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:54:48 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:54:48 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 10:54:48 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:54:53 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:54:54 PM null
INFO: Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Jul 19, 2022 10:54:54 PM null
INFO: Waiting for SSH to come up. Sleeping 5.
Jul 19, 2022 10:54:59 PM null
INFO: Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Jul 19, 2022 10:54:59 PM null
INFO: Connected via SSH.
Jul 19, 2022 10:54:59 PM null
INFO: Verifying: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -fullversion
openjdk full version "11.0.7+10-post-Ubuntu-2ubuntu218.04"
Jul 19, 2022 10:54:59 PM null
INFO: Copying agent.jar to: /var/lib/jenkins/workspace
Jul 19, 2022 10:54:59 PM null
INFO: Launching Jenkins agent via plugin SSH: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -jar /var/lib/jenkins/workspace/agent.jar
<===[JENKINS REMOTING CAPACITY]===>Remoting version: 4.10.1
This is a Unix agent
Evacuated stdout
Agent successfully connected and online

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[x] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Sorry for the direct ping, but @donmccasland or @alecharp do you know who would be best to review this? Thanks

Is this a feature coming any time soon? We'd really love to have this feature as we currently hit a race condition where the pipeline starts building the agent before the startup script finishes logging in and breaks on first execution.

This would be great. Our current workaround is to have the script stop sshd, then start it again at the end.
Thank you!

Any chance we could get codeowners to take a look at this PR? This feature would solve a lot of problems we're facing with setting up Jenkins on GCE


confusion about camera and world coordinates

Thanks for your great work! There is some confusion when I run code:

why would we change the second and first dims of translation when changing object depth and its horizontal position, respectively? What is the relationship between camera and world coordinates?
how do you determine the scale and translation ranges of object to scene, e.g. the face experiments on celebahq? Do we need some prior on that?

Hi @MrTornado24 , thanks for your interest in our project.

I'm not sure what you mean by this? This only means that the third dimension (z-axis) is pointing upwards which is a common choice when defining a coordinate system.
Yes, you need to define the distribution for this. In this work, we just select min and max bounds and apply a uniform distribution over these ranges.


OpenJPEG (and others) file to build on Mac OS Monterey with Intel compilers

Describe the bug
When building spack-stack on Mac OS Monterey with the Intel compilers, compilation (linking specifically) fails for OpenJPEG and other packages that configure/build with cmake. Below is the error. I have added the -w flag to my compilation to suppress hundreds of warnings about pointer alignment before the actual error:
[ 50%] Linking C shared library ../../../bin/libopenjp2.dylib
cd /Users/robertson/roms/svn/git/spack-stack/cache/build_stage/spack-stage-openjpeg-2.3.1-iurwmfwumuetxdkny3ujulzkq4pvt5bb/spack-build-iurwmfw/src/lib/openjp2 && /opt/local/bin/cmake -E cmake_link_script CMakeFiles/openjp2.dir/link.txt --verbose=1
/Users/robertson/roms/svn/git/spack-stack/spack/lib/spack/env/intel/icc -O2 -g -DNDEBUG -dynamiclib -Wl,-headerpad_max_install_names -Wl,-w -compatibility_version 7.0.0 -current_version 2.3.1 -o ../../../bin/libopenjp<IP_ADDRESS>.dylib -install_name @rpath/libopenjp2.7.dylib CMakeFiles/openjp2.dir/thread.c.o CMakeFiles/openjp2.dir/bio.c.o CMakeFiles/openjp2.dir/cio.c.o CMakeFiles/openjp2.dir/dwt.c.o CMakeFiles/openjp2.dir/event.c.o CMakeFiles/openjp2.dir/image.c.o CMakeFiles/openjp2.dir/invert.c.o CMakeFiles/openjp2.dir/j2k.c.o CMakeFiles/openjp2.dir/jp2.c.o CMakeFiles/openjp2.dir/mct.c.o CMakeFiles/openjp2.dir/mqc.c.o CMakeFiles/openjp2.dir/openjpeg.c.o CMakeFiles/openjp2.dir/opj_clock.c.o CMakeFiles/openjp2.dir/pi.c.o CMakeFiles/openjp2.dir/t1.c.o CMakeFiles/openjp2.dir/t2.c.o CMakeFiles/openjp2.dir/tcd.c.o CMakeFiles/openjp2.dir/tgt.c.o CMakeFiles/openjp2.dir/function_list.c.o CMakeFiles/openjp2.dir/opj_malloc.c.o CMakeFiles/openjp2.dir/sparse_array.c.o  -lm
icc: remark #10441: The Intel(R) C++ Compiler Classic (ICC) is deprecated and will be removed from product release in the second half of 2023. The Intel(R) oneAPI DPC++/C++ Compiler (ICX) is the recommended compiler moving forward. Please transition to use this compiler. Use '-diag-disable=10441' to disable this message.
ld: unaligned pointer(s) for architecture x86_64
make[2]: *** [bin/libopenjp<IP_ADDRESS>.dylib] Error 1
make[1]: *** [src/lib/openjp2/CMakeFiles/openjp2.dir/all] Error 2
make: *** [all] Error 2
==> Error: ProcessError: Command exited with status 2:
    'make' '-j1'

I am using the latest Intel C/C++ and Fortran compilers for Mac OS Monterey, as well as the latest Xcode that still contains the Monterey SDK (14.0.1 in this case).
I believe there is something very strange going on here. After the failed build I can go to the directory where it's failing and replace the spack icc script with just icc it will successfully create ../../../bin/libopenjp<IP_ADDRESS>.dylib:
icc -O2 -g -DNDEBUG -dynamiclib -Wl,-headerpad_max_install_names -Wl,-w -compatibility_version 7.0.0 -current_version 2.3.1 -o ../../../bin/libopenjp<IP_ADDRESS>.dylib -install_name @rpath/libopenjp2.7.dylib CMakeFiles/openjp2.dir/thread.c.o CMakeFiles/openjp2.dir/bio.c.o CMakeFiles/openjp2.dir/cio.c.o CMakeFiles/openjp2.dir/dwt.c.o CMakeFiles/openjp2.dir/event.c.o CMakeFiles/openjp2.dir/image.c.o CMakeFiles/openjp2.dir/invert.c.o CMakeFiles/openjp2.dir/j2k.c.o CMakeFiles/openjp2.dir/jp2.c.o CMakeFiles/openjp2.dir/mct.c.o CMakeFiles/openjp2.dir/mqc.c.o CMakeFiles/openjp2.dir/openjpeg.c.o CMakeFiles/openjp2.dir/opj_clock.c.o CMakeFiles/openjp2.dir/pi.c.o CMakeFiles/openjp2.dir/t1.c.o CMakeFiles/openjp2.dir/t2.c.o CMakeFiles/openjp2.dir/tcd.c.o CMakeFiles/openjp2.dir/tgt.c.o CMakeFiles/openjp2.dir/function_list.c.o CMakeFiles/openjp2.dir/opj_malloc.c.o CMakeFiles/openjp2.dir/sparse_array.c.o  -lm

I have also retrieved the PATH environment variable and $full_command_list from spack/lib/spack/env/intel/icc, added spaces in the correct places, set PATH, and successfully built ../../../bin/libopenjp<IP_ADDRESS>.dylib:
/opt/intel/oneapi/compiler/2023.0.0/mac/bin/intel64/icc -march=skylake -mtune=skylake -w -Wl,-headerpad_max_install_names -Wl,-rpath,/opt/spack-stack/sw/intel/2021.8.0/openjpeg-2.3.1-iurwmfw/lib -Wl,-rpath,/opt/spack-stack/sw/intel/2021.8.0/openjpeg-2.3.1-iurwmfw/lib64 -Wl,-rpath,/opt/intel/oneapi/compiler/2023.0.0/mac/compiler/lib -Wl,-rpath,/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/usr/lib -O2 -g -DNDEBUG -dynamiclib -Wl,-headerpad_max_install_names -Wl,-w -compatibility_version 7.0.0 -current_version 2.3.1 -o ../../../bin/libopenjp<IP_ADDRESS>.dylib<EMAIL_ADDRESS>CMakeFiles/openjp2.dir/thread.c.o CMakeFiles/openjp2.dir/bio.c.o CMakeFiles/openjp2.dir/cio.c.o CMakeFiles/openjp2.dir/dwt.c.o CMakeFiles/openjp2.dir/event.c.o CMakeFiles/openjp2.dir/image.c.o CMakeFiles/openjp2.dir/invert.c.o CMakeFiles/openjp2.dir/j2k.c.o CMakeFiles/openjp2.dir/jp2.c.o CMakeFiles/openjp2.dir/mct.c.o CMakeFiles/openjp2.dir/mqc.c.o CMakeFiles/openjp2.dir/openjpeg.c.o CMakeFiles/openjp2.dir/opj_clock.c.o CMakeFiles/openjp2.dir/pi.c.o CMakeFiles/openjp2.dir/t1.c.o CMakeFiles/openjp2.dir/t2.c.o CMakeFiles/openjp2.dir/tcd.c.o CMakeFiles/openjp2.dir/tgt.c.o CMakeFiles/openjp2.dir/function_list.c.o CMakeFiles/openjp2.dir/opj_malloc.c.o CMakeFiles/openjp2.dir/sparse_array.c.o -lm

I would note that in the set of packages I'm actually aiming to build, this is the first package that uses cmake instead of autotools to build. Several packages using autotools build successfully before this failure.
I would also note that the first time I run concretize it creates ~/.spack/bootstrap/store/darwin-bigsur-x86_64/apple-clang-13.0.0 instead of ~/.spack/bootstrap/store/darwin-monterey-x86_64/apple-clang-14.0.0 for clingo, gnupg, etc..
To Reproduce
Build a spack-stack configuration that requests the jedi-base-env (and therefore eccodes which relies on openjpeg) on Mac OS Monterey using the Intel compilers.
Expected behavior
OpenJPEG (and others) build and link successfully
System:
Mac OS Monterey using the Intel compilers.
Additional context
This same basic configuration builds successfully on Mac OS Big Sur. The main differences are OS version and Xcode version.
If I modify eccodes' package.py to allow it use the system supplied version of OpenJPEG then eccodes fails to build with the same unaligned pointer(s) error.

Have you tried using
spack stage<EMAIL_ADDRESS>spack cd<EMAIL_ADDRESS>spack build-env<EMAIL_ADDRESS>
Then set these environment variables in a shell and try to run the command that spack doesn't like.
Let me note, though, and it's already indicated as a warning in your output, that we do not support Intel on macOS. We only support Apple's native clang + gfortran and LLVM clang + gfortran. Intel has clearly said that they will not produce the new LLVM-based Intel compilers for macOS, and the Intel classic C/C++ compilers will be deprecated in the second half of this year. The classic Fortran compiler is supposed to follow later (next year?).

@rjdave Since Intel has decided to stop supporting macOS with its new LLVM-based compilers (icx, icpx, ifx) and since icc and icpc will be deprecated in the second half of 2023 (ifort will follow later), we decided to not support Intel on macOS in spack-stack / spack.
You may want to try seeking help from the spack user community by submitting an issue on their github page (https://github.com/spack/spack) or by joining their slack channel.


Adding Slug functionality to append to URL

Add post slugs for URL design and potential SEO.
We could also make it automatic when someone posts the submission and it will turn the title into a slug.
i.e. First TIL Post
into
til/first-til-post
and extend the functionality within this issue or another to add the ID prior
i.e.
til/45/volcanoes-are-cool or something along those lines

This will also create/change the model as the DB structure will change to allow this in each post.

This will also create/change the model as the DB structure will change to allow this in each post.

Agree, that makes sense.


Initialize FullPathMapper from base struct and sites struct

@acrutt  can you figure out why the test case is failing?

@acrutt  can you figure out why the test case is failing?

@jmmshn I finished making the additional fixes needed but there is one minor conflict that I don't have permission to resolve.

@acrutt  Thanks for all the documentation updates they are really helpful.
I went through the PR more carefully and I now understand why the test case broke and how you fixed it.
It looks like you are fundamentally changing how the sites that can move are defined, which removed the original code's ability to create the only_sites attribute.  I think a better way will be to feed a list of site indices (maybe a subset of the sites that are the migrating species) this will still allow the code to function as it did before for cases where you are just interested in the normal migration graph.
Also, it might make more sense to PR this directly into pymatgen-diffusion since it pull in my fork already.
I would suggest doing a documentation/variable name change update first before the new logic is introduced, and you can use this time to figure out exactly how that new logic should be implemented.

The only_sites attribute is now called the sites_structure attribute. I did some renaming of the attributes to be clearer with the FullPathMapper changes but otherwise my intention was for these two attributes to be the same. Can the conflict be resolved by replacing self.only_sites with self.sites_structure in creating the s_graph attribute? Or is there something preventing this replacement?
I'm not sure I agree that providing the sites as a list of site indices is the way to go. I think it would create an unnecessary additional step, increase the odds of a user error, and makes some helpful functionality more difficult (e.g. if I have all the insertion sites in a separate structure, I can merge similar sites that are very close together). I rather not make this change unless there are other benefits I'm missing.

The only_sites attribute is now called the sites_structure attribute. I did some renaming of the attributes to be clearer with the FullPathMapper changes but otherwise my intention was for these two attributes to be the same. Can the conflict be resolved by replacing self.only_sites with self.sites_structure in creating the s_graph attribute? Or is there something preventing this replacement?

My problem is not with changing the name my problem is with completely getting rid of the ability to generate this graph from the imputer structure and migrating species along. <-- This is the reason the test failed.  The current fix does not seem to actually address the cause of this break but rather changes the test completely to avoid raising an error.

I'm not sure I agree that providing the sites as a list of site indices is the way to go. I think it would create an unnecessary additional step, increase the odds of a user error, and makes some helpful functionality more difficult (e.g. if I have all the insertion sites in a separate structure, I can merge similar sites that are very close together). I rather not make this change unless there are other benefits I'm missing.

The benefit is that if we are not using this selective migration of specific ions. Then the code has lost a very basic capability that it originally had.   And causing upstream things to break for new features is will generally lead to more unforeseen problems down the line.
Either way, this should be a materialsvirtuallab/pymatgen-diffusion PR now so I will close this PR for now.

Now it sounds like there is a qualm with the originally proposed change to how the FullPathMapper is constructed. Are you saying you are not ok with changing the input from one structure that contains both the base and inserted/mobile sites?
If someone wishes to start with a combined structure of both the base and inserted/mobile sites it's just about two lines of code to convert that into two structures if you are able to distinguish the inserted/mobile sites by specie. So this didn't seem like a burdensome change to me.

So using the index was just a suggestion after reading the code.  You can still just use a structure but to make it less invasive you can have the site structure as an optional parameter, so if it provided you use it if it is not provided create the structure using the old method that you deleted.
That will allow the code to do what you need and not break any of the original usage cases.

Ok, I can add that back in and make a new pull request


Fortiweb WAF cloud soar

Required items, please complete
Change(s):

Adding new playbooks for enhancing the security of customer's environment

Reason for Change(s):

addition of new playbooks with custom connectors

Version Updated:

N/A

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

@anki-narravula  : Changes has been made


VMware : Details Information will not be updated

[Build]
docker 17.7 2018/10/17
[Steps to reproduce]
create a VMware instance
goto My Subscrption
stop the Instance
[Expected result]
The Details Information  will be updated
[Observed result]
status is still running
ACCOUNT-> view operations: the stop operation is completed and the Instance has stopped

Same as #152. Apparently caused by missing progress callback from APP. This should be fixed together.

update detail information after start/stop still not work for vmware. Azure and aws work fine

the status tab works fine therefore I close the bug again.


Missing "en" translation

dist folder is missing en translation file.

The English messages are bundled in the validator distribution file.


Added fix for USB init error on machines without USB port

Fix for issue #40
Ark-client tries to initialize a USB port to check if a Ledger is connected, when no USB port can be initialized the app crashes.
I have added error handling for the loading of the modules that manage the Ledger. This prevents a crash when no USB port exists on the system. The user is warned when no support for the Ledger is available and all methods that might use the Ledger have an addtional check if Ledger support is enabled or not.

@wownmedia Please fix the conflicts, will merge this PR then.

Updated the code to remove the conflict.


Feature requests

v8 is awesome! Thanks a ton for putting time into this.
Few feature requests:

expose content, position,etc in selectionTip as props.
i have this use case where i have a text copy button inside the selectionTip, so having access to those values would be nice.

the highlights prop takes value of type "Highlight[]", this isnt ideal imo, cause content type is often expensive to store in db, and not preferred imo. would be cool if youd make it "Omit<Highlight,"content"> [] | Highlight[]>  , or something similar.
same goes for the scrollToHighlight fn

For deleting a highlight itd be better for the popup to appear once the user clicks on the highlight instead of hover.

also maybe a fn to Scroll to specific page no . someone else raised this issue in the other lib

and maybe a toggle button which if turned on, then if any text is selected it gets highlighted. (instead of having to click the popover everytime). => some helper fn to implement this would be cool.

feature to search text

expose content, position,etc in selectionTip as props.
i have this use case where i have a text copy button inside the selectionTip, so having access to those values would be nice.

selectionTip is just of the Tip type and you can access the currently displayed selectionTip with the usePdfHighlighterContext hook or with the PdfHighlighterUtils directly.

the highlights prop takes value of type "Highlight[]", this isnt ideal imo, cause content type is often expensive to store in db, and not preferred imo. would be cool if youd make it "Omit<Highlight,"content"> [] | Highlight[]> , or something similar.
same goes for the scrollToHighlight fn

Very true. I'm not too fond of adding additional accepted types to functions and components since I feel that confuses expected behaviour, but since content isn't actually used anywhere inside the PdfHighlighter, we can just make that property optional. This brings up some side effects, but they're covered in #16 .
Currently position is the position of a highlight which the tip should hover around. You can currently get precise positioning by passing through some fake highlight position. I'm not too fond of just exposing the raw positioning though since it seems the developer could just display an overlay themselves after a selection event in that case. But, if there's good reasoning for exposing offsets or the raw positioning, then I'm more than interested :).

For deleting a highlight itd be better for the popup to appear once the user clicks on the highlight instead of hover.

Not too sure what you mean? This sounds like an example app request though, which would be of low priority.

also maybe a fn to Scroll to specific page no . someone else raised this issue in the https://github.com/agentcooper/react-pdf-highlighter/issues/263

PDF.js actually already exposes this functionality via the PDF Viewer, which you can access yourself. Note: pageNumber is indexed at 1 like usual for PDF.js.
// Using usePdfHighlighterContext hook inside of any child of PdfHighlighter. For example, inside a tip
const { getViewer } = usePdfHighlighterContext();
getViewer()?.scrollPageIntoView({pageNumber: 2});

// Using utils ref outside of the PdfHighlighter component (taken from example app)
const highlighterUtilsRef = useRef<PdfHighlighterUtils>();
highlighterUtilsRef.current?.getViewer()?.scrollPageIntoView({ pageNumber: 2);

You can even add in a destArray,
scrollPageIntoView({ pageNumber: 2, destArray: [null, { name: "XYZ" }, 10, 10, "page-fit"] });

and maybe a toggle button which if turned on, then if any text is selected it gets highlighted. (instead of having to click the popover everytime). => some helper fn to implement this would be cool.

There's a lot of variability here in how a developer might want to implement this (how should highlights be separated, what data should be stored with highlights, etc.). In general though, you could implement this crudely by simply adding creating a highlight on every selection event. This is much simpler with the new selection event in #15 , and I've added this functionality to the example app.

feature to search text

The text layer of each PDF is currently loaded in, so you should be able to Ctrl + F as usual. Exposing the PDFFindService from PDF.js could have its perks though. I'll keep considering it.

sweet, works great! is there a way to use smooth scrolling?

easiest way would be to create a patch passing
{ block: 'end',  behavior: 'smooth' })

at https://github.com/DanielArnould/react-pdf-highlighter-extended/blob/b58a3b387d870a44051a7d032e5f67ecabeb7909/src/components/PdfHighlighter.tsx#L478

@DanielArnould
is there anyway i can do:

select specific text in a given page
get current pdf page in view
scroll to a specific text in a given page


New version: AVSfldIO v0.2.0

Registering package: AVSfldIO
Repository: https://github.com/JeffFessler/AVSfldIO.jl
Created by: @JeffFessler
Version: v0.2.0
Commit: 538a7adbce50a758530eb7ce339b4a20e130c264
Reviewed by: @JeffFessler
Reference: https://github.com/JeffFessler/AVSfldIO.jl/commit/538a7adbce50a758530eb7ce339b4a20e130c264#commitcomment-50861857

See #36555 for 0.1.0 new package registration.  I already had to make more changes so now this is really the one to register...
[noblock]

never mind on this PR.  will try again now that 0.1.0 is officially registered

this seem stuck so abort it

note to self: replaced by #36858, hopefully


trailingSlash has no effect on URLs on blog feeds

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
My deployment (nginx-s3 ingress) requires trailing slashes, so I'm using trailingSlash: true. This works for URLs on the web pages, but the ones in blog feeds (RSS and Atom) do not get a trailing slash and therefore do not work.
Reproducible demo
No response
Steps to reproduce
# create a new site and build
npx create-docusaurus@latest reprex classic
cd reprex
npm run build

# links to an example blog post are without a trailing slash, both in index.html:
grep -o ".......blog/welcome.." build/blog/index.html
# href="/blog/welcome">
# href="/blog/welcome">

# and in the RSS and Atom feeds:
grep -o ".......blog/welcome.." build/blog/rss.xml
# te.com/blog/welcome</
grep -o ".......blog/welcome.." build/blog/atom.xml
# te.com/blog/welcome"/

# add 'trailingSlash: true' to the config and re-build
gsed -i '12 a\  trailingSlash: true,' docusaurus.config.js
npm run build

# now links in index.html are with the trailing slash:
grep -o ".......blog/welcome.." build/blog/index.html
# href="/blog/welcome/"
# href="/blog/welcome/"

# but the RSS and Atom feed ones are still without a trailing slash:
grep -o ".......blog/welcome.." build/blog/rss.xml
# te.com/blog/welcome</
grep -o ".......blog/welcome.." build/blog/atom.xml
# te.com/blog/welcome"/

Expected behavior
URLs on both the web pages and the feeds respect the trailingSlash setting.
Actual behavior
Web pages are affected by trailingSlash but feeds are not.
Your environment

Docusaurus version used: 2.0.0-beta.21
Environment name and version (e.g. Chrome 89, Node.js 16.4): Node v18.3.0
Operating system and version (e.g. Ubuntu 20.04.2 LTS): macOS Big Sur 11.6.5

Self-service

[ ] I'd be willing to fix this bug myself.

we can probably do like in the sitemaps and apply at feed generation?

Yes, I think that's fine.

Not 100% sure we handle blog post feed base URL very well either

Looks correct to me? Do you mean https://docusaurus.io/tests/blog/rss.xml?

Looks correct to me? Do you mean docusaurus.io/tests/blog/rss.xml?

Yes I'm wrong 👍
link: normalizeUrl([siteUrl, permalink]) => forgot permalink contains the baseUrl already


Typo "**Yes, ～ version""→"Yes, ～ version"

https://docs.microsoft.com/en-us/azure/virtual-machines/capture-image-portal
#PingMSFTDocs

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks.

@hyoshioka0128 Thank you for catching that and fixing it! :)


Add custom item tracking list(s)

I think it would be cool to have the option for a customizable panel in the loot logger.
My idea was a tile below the Wilderness category where you could input item ID's and make a "wish list" of sorts shared across all kills. (i.e. a custom collection log/goal list - I think it would also be great for streamers to visualize their goals for their audiences)
I don't know if it would even be possible with the current code. Never mind this, if it requires too much alteration.

This seems like it would be better as a stand-alone plugin as it's not really logging loot and could probably use the config system to store its data instead. This seems like it'd fit a collection log themed plugin but I'm not sure anyone has any interest in making that plugin.


[5.1] [CSDiagnostics] Removes lazy when applying computed property fix-it

Cherry-pick of #24274.

cc @xedin

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - a05b0bdfc938dada0dfa2fab196b6c6a4cca433d

Unrelated OSX failure:
19:51:06 FATAL: Unable to delete script file /var/folders/_8/79jmzf2142z2xydc_01btlx00000gn/T/jenkins3773126030451336711.sh

Infra problem, let’s try again.

@swift-ci please test macOS platform


[Feature] consistency_check concurrency execution control

Fixes #32
Description of the change

Added thread concurrency control execution per switch when executing check_consistency. I ended up using the STATS_INTERVAL / 2 as a reference to skip executions per switch, without using this a reference it could still end up with cases where it would still execute relatively close to previous executions, so this enforces some back pressure.

thanks for your review, Antonio.


Revert "[MRTCore] Sync between WGA.PrimaryLanguageOverride and MWGA.PrimaryLanguageOverride (#4608)"

Unfortunately, Windows.Globalization.ApplicationLanguages.PrimaryLanguageOverride relies on an internal API that throws an exception if no language override has been set. Even though this exception is expected and caught further up the stack, this can cause an incredible amount of noise in the debugger if it's configured to break on thrown exceptions. As a result, it is necessary to revert #4608 (which allows Microsoft.Globalization.ApplicationLanguages.PrimaryLanguageOverride to reflect the value of Windows.Globalization.ApplicationLanguages.PrimaryLanguageOverride if the latter API is used by the app) in order to suppress the noisy exception.
A microsoft employee must use /azp run to validate using the pipelines below.
WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.

/azp run


Errors with Laravel 5.4

Hi,
while trying to reproduce #64 I got the following error while running the following command:
php artisan db:seed --class=\Rinvex\Fort\Seeds\DatabaseSeeder
CLI Output:
Seeding: Rinvex\Fort\Seeds\AbilitiesSeeder

[Symfony\Component\Debug\Exception\FatalErrorException]
Declaration of Rinvex\Cacheable\CacheableEloquent::updated($callback, $priority = 0) must be compatible with Illuminate\Database\Eloquent\Model::updated($callback)

PHP: 7.1.0
MySQL: 5.6.34
Laravel: 5.4
Fort: dev-develop
Composer
** minimum-stability: dev

Also I get the following error message while trying to open the page in the browser...
FatalThrowableError in SessionGuard.php line 183:
Type error: Argument 3 passed to Rinvex\Fort\Guards\SessionGuard::__construct() must be an instance of Illuminate\Session\SessionInterface, instance of Illuminate\Session\Store given, called in /Applications/MAMP/htdocs/rinvex_fort/vendor/rinvex/fort/src/Providers/FortServiceProvider.php on line 147
in SessionGuard.php line 183
at SessionGuard->__construct('web', object(EloquentUserProvider), object(Store), object(Request)) in FortServiceProvider.php line 147
at FortServiceProvider->Rinvex\Fort\Providers\{closure}(object(Application), 'web', array('driver' => 'session', 'provider' => 'users')) in AuthManager.php line 111
at AuthManager->callCustomCreator('web', array('driver' => 'session', 'provider' => 'users')) in AuthManager.php line 90
at AuthManager->resolve('web') in AuthManager.php line 70
at AuthManager->guard() in AuthManager.php line 294
at AuthManager->__call('user', array()) in Facade.php line 221
at Facade::__callStatic('user', array()) in FortServiceProvider.php line 79
at FortServiceProvider->Rinvex\Fort\Providers\{closure}(object(View)) in ManagesEvents.php line 164
at Factory->Illuminate\View\Concerns\{closure}('composing: welcome', array(object(View))) in Dispatcher.php line 332
at Dispatcher->Illuminate\Events\{closure}('composing: welcome', array(object(View))) in Dispatcher.php line 199
at Dispatcher->dispatch('composing: welcome', array(object(View)), false) in Dispatcher.php line 172
at Dispatcher->fire('composing: welcome', array(object(View))) in ManagesEvents.php line 179
at Factory->callComposer(object(View)) in View.php line 118
at View->renderContents() in View.php line 85
at View->render() in Response.php line 38
at Response->setContent(object(View)) in Response.php line 225
at Response->__construct(object(View)) in Router.php line 602
at Router->prepareResponse(object(Request), object(View)) in Router.php line 559
at Router->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 30
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Abilities.php line 49
at Abilities->handle(object(Request), object(Closure)) in Pipeline.php line 148
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in SubstituteBindings.php line 41
at SubstituteBindings->handle(object(Request), object(Closure)) in Pipeline.php line 148
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in VerifyCsrfToken.php line 65
at VerifyCsrfToken->handle(object(Request), object(Closure)) in Pipeline.php line 148
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in ShareErrorsFromSession.php line 49
at ShareErrorsFromSession->handle(object(Request), object(Closure)) in Pipeline.php line 148
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in StartSession.php line 64
at StartSession->handle(object(Request), object(Closure)) in Pipeline.php line 148
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in AddQueuedCookiesToResponse.php line 37
at AddQueuedCookiesToResponse->handle(object(Request), object(Closure)) in Pipeline.php line 148
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in EncryptCookies.php line 59
at EncryptCookies->handle(object(Request), object(Closure)) in Pipeline.php line 148
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 102
at Pipeline->then(object(Closure)) in Router.php line 561
at Router->runRouteWithinStack(object(Route), object(Request)) in Router.php line 520
at Router->dispatchToRoute(object(Request)) in Router.php line 498
at Router->dispatch(object(Request)) in Kernel.php line 174
at Kernel->Illuminate\Foundation\Http\{closure}(object(Request)) in Pipeline.php line 30
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in CheckForMaintenanceMode.php line 46
at CheckForMaintenanceMode->handle(object(Request), object(Closure)) in Pipeline.php line 148
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 102
at Pipeline->then(object(Closure)) in Kernel.php line 149
at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 116
at Kernel->handle(object(Request)) in index.php line 53

Yes, and all of the discovered issues has been fixed in multiple updates this morning 😉  It's currently even way better and more stable after some small refactoring..

Thanks a lot!


Automated cherry pick of #9521: Storage actual size filter

Cherry pick of #9521 on release/3.6.
#9521: Storage actual size filter

Codecov Report

Merging #9524 (e7dd6bb) into release/3.6 (b9d30c0) will increase coverage by 10.63%.
The diff coverage is 4.09%.

@@               Coverage Diff                @@
##           release/3.6    #9524       +/-   ##
================================================
+ Coverage         5.86%   16.50%   +10.63%
================================================
  Files              828       87      -741
  Lines           129133     9120   -120013
================================================
- Hits              7577     1505     -6072
+ Misses          120876     7483   -113393
+ Partials           680      132      -548

Flag
Coverage Δ

aFlag
16.50% <4.09%> (+10.63%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/hostman/diskutils/nbd/driver.go
0.75% <0.75%> (ø)

pkg/hostman/diskutils/nbd/lvmutils.go
4.93% <4.93%> (ø)

pkg/mcclient/modules/monitor/suggestsysrule.go
100.00% <100.00%> (ø)

pkg/monitor/alerting/conditions/nodataquery.go
0.72% <0.00%> (-0.27%)
:arrow_down:

pkg/monitor/alerting/conditions/query.go
0.00% <0.00%> (ø)

pkg/hostman/system_service/ovn_conroller.go

pkg/multicloud/esxi/ip.go

pkg/cloudcommon/validators/validators.go

pkg/util/fileutils2/fileutils.go

... and 643 more

Continue to review full report at Codecov.

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

/lgtm

/lgtm

/lgtm

/lgtm

/approve

/approve

/approve


[FLINK-XXXX] Externalized Declarative Resource Management.

TODO

[ ] Add test for AS releasing idle slots


Unable to copy content from Windows 10 to Google Chrome, Idea, or Gedit

Windows build number:
19045.2965
Your Distribution version:
22.04
Your WSL versions:
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131-1002-220531-1700. rs one core base 2 hyp
Windows version: 10.0.19045.2965

Steps to reproduce:

Copy a large amount of text (over 65536 characters) at once in Windows 10
Paste into Google Chrome, Idea, or Gedit
After this, you will not be able to paste anything from Windows 10 into wslg applications

WSL logs:
pulseaudio.log
W: [pulseaudio] authkey.c: Failed to open cookie file '/home/wslg/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key '/home/wslg/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to open cookie file '/home/wslg/.pulse-cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key '/home/wslg/.pulse-cookie': No such file or directory
E: [pulseaudio] module-console-kit.c: GetSessionsForUnixUser() call failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
E: [pulseaudio] module.c: Failed to load module "module-console-kit" (argument: ""): initialization failed.
E: [rdp-sink] module-rdp-sink.c: RDP Sink - Trying to connect to /mnt/wslg/PulseAudioRDPSink
E: [rdp-sink] module-rdp-sink.c: Connected failed
E: [rdp-sink] module-rdp-sink.c: RDP Sink - Trying to connect to /mnt/wslg/PulseAudioRDPSink
E: [rdp-sink] module-rdp-sink.c: RDP Sink - Connected to fd 12

weston.log
RDP clipboard_data_source_send new (0x7fa268001330:failed:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:28:49.857] read fd:96 0 (available 65536, mask 0x4)
[20:28:49.857] non-incr transfer read complete
[20:29:01.840]

RDP clipboard_data_source_send new (0x7fa268000bf0:published:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:01.841] xfixes selection notify event: owner 2097153
[20:29:01.841] our window, skipping
[20:29:01.841] selection request, CLIPBOARD, target UTF8_STRING, property FCITX_X11_SEL_CLIPBOARD
[20:29:01.841]

RDP clipboard_data_source_send new (0x7fa268000bf0:failed:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:01.841] read fd:96 0 (available 65536, mask 0x4)
[20:29:01.841] non-incr transfer read complete
[20:29:01.841]

RDP clipboard_data_source_send new (0x7fa268001330:published:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:01.841] xfixes selection notify event: owner 2097153
[20:29:01.841] our window, skipping
[20:29:01.841] selection request, CLIPBOARD, target UTF8_STRING, property FCITX_X11_SEL_CLIPBOARD
[20:29:01.841]

RDP clipboard_data_source_send new (0x7fa268001330:failed:fd 106) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:01.841] read fd:105 0 (available 65536, mask 0x4)
[20:29:01.841] non-incr transfer read complete
[20:29:25.346]

RDP clipboard_data_source_send new (0x7fa268000bf0:published:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:25.346] xfixes selection notify event: owner 2097153
[20:29:25.346] our window, skipping
[20:29:25.346] selection request, CLIPBOARD, target UTF8_STRING, property FCITX_X11_SEL_CLIPBOARD
[20:29:25.346]

RDP clipboard_data_source_send new (0x7fa268000bf0:failed:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:25.346] read fd:96 0 (available 65536, mask 0x4)
[20:29:25.346] non-incr transfer read complete
[20:29:30.754]

RDP clipboard_data_source_send new (0x7fa268001330:published:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

[20:29:30.754] xfixes selection notify event: owner 2097153
[20:29:30.754] our window, skipping
[20:29:30.754] selection request, CLIPBOARD, target UTF8_STRING, property FCITX_X11_SEL_CLIPBOARD
[20:29:30.754]

RDP clipboard_data_source_send new (0x7fa268001330:failed:fd 99) vs prev (0x7fa268000d00:cancel pending:fd 104): outstanding RDP data request (client to server)

stderr.log
[19:47:19.942] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts
[19:47:19.942] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11
[19:47:19.943] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11/encodings
[19:47:19.944] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11/encodings/large
[19:47:19.944] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11/util
[19:47:19.944] <5>WSLGd: FontFolder:14: FontMonitor: start monitoring /mnt/wslg/distro/usr/share/fonts/X11/misc
/usr/share/icons/hicolor/scalable/apps/com.gexperts.Tilix.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
/usr/share/icons/hicolor/scalable/apps/org.gnome.Nautilus.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
libpng warning: iCCP: known incorrect sRGB profile
/usr/share/icons/hicolor/scalable/apps/org.gnome.gedit.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
glamor: 'wl_drm' not supported
Missing Wayland requirements for glamor GBM backend
Failed to initialize glamor, falling back to sw
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
[19:47:22.944] <5>WSLGd: ExecuteShellCommand:85: FontMonitor: pid:364 exited with success, /usr/bin/xset +fp /mnt/wslg/distro/usr/share/fonts/X11/misc

[19:47:22.945] <5>WSLGd: ExecuteShellCommand:85: FontMonitor: pid:570 exited with success, /usr/bin/xset fp rehash
[19:47:22.945] <5>WSLGd: FontMonitorThread:228: FontMonitor: monitoring thread started.
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts, and it is *not* added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11, and it is *not* added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11/encodings, and it is *not* added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11/encodings/large, and it is *not* added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11/misc, and it is added to X11 font path
[19:47:22.946] <5>WSLGd: DumpMonitorFolders:125: FontMonitor: monitoring /mnt/wslg/distro/usr/share/fonts/X11/util, and it is *not* added to X11 font path
dbus[574]: Unknown username "pulse" in message bus configuration file
/usr/share/icons/hicolor/scalable/apps/com.gexperts.Tilix.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
/usr/share/icons/hicolor/scalable/apps/org.gnome.Nautilus.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
libpng warning: iCCP: known incorrect sRGB profile
/usr/share/icons/hicolor/scalable/apps/org.gnome.gedit.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 569, clipping.
>                   X11 cannot support keycodes above 255.
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
could not load cursor 'grabbing'
could not load cursor 'dnd-move'
could not load cursor 'dnd-copy'
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server

WSL dumps:
No response
Expected behavior:
I hope to copy and paste between Windows and wslg normally. Now it seems like he's stuck on the RDP transmission
Actual behavior:
When copying a large amount of text from Windows at once to wslg, wslg will not be able to paste any content, and after that, it will not be possible to paste any length of content from Windows into wslg.

I have looked at many issues records and it seems that this issue has existed for a long time, even dating back to 2020. I want to know if anyone is dealing with this issue?

So no one saw or noticed this problem? As long as you copy thousands of characters at once, wslg cannot copy anything from Windows.

anyone help?

I have this problem since 2020 and I just use workaround - save file with copied content on Windows side and open it with anything you want on WSL side. But I'm pretty sure you are doing the same now :)

@gf9276, thanks for reporting the issue, I believe this is the issue reported at https://github.com/microsoft/wslg/issues/743, thanks!

@gf9276, thanks for reporting the issue, I believe this is the issue reported at #743, thanks!

@hideyukn88, I just tried and the problem still exists. This problem has existed for at least two years or more, so why hasn't it been resolved yet?

@gf9276, thanks for reporting the issue, I believe this is the issue reported at #743, thanks!

@hideyukn88, I just tried and the problem still exists. This problem has existed for at least two years or more, so why hasn't it been resolved yet?

It's because this place is abandoned.

No it's not? Just because this issue isn't getting obvious and constant work reported in this exact issue report, you claim its abandoned?

@gf9276, thanks for inquiry. The reason of the delay for that issue, #743, is inherited from upstream branch, which normally doesn't make specific fix at local downstream branch, unless it's coordinated with its upstream maintainer. Let us understand what's going on, and will update here or at #743, thanks!


Installer task fails behind company proxy

Terraform Installer task throws timeout during pipeline execution. All the agents are behind company proxy. Could that be the issue? Regarding the source code, maybe fetch is not able to recognize the proxy settings?
https://github.com/jason-johnson/azure-pipelines-tasks-terraform/blob/c1c99a58f820682edf3b4a095b613059722f46d9/tasks/terraform-installer/src/installer.ts#L17

Hi @KristofKuli
Node-proxy should rely on env variables HTTP_PROXY or HTTPS_PROXY. Have you tried these?

Would you know if the download works directly from example  from https://releases.hashicorp.com/terraform/1.3.7/terraform_1.3.7_linux_arm.zip with wget/curl? Sometimes proxies also block binary download.

Curl returned HTTP 200, so that works.

Update: we checked on Azure Pipelines pool, which hosted by MS and the download work there. Furthermore, the customer also has his own VM scale set in Azure, where the proxy is not set and pipeline is successful.

Is there any update on this? We are still believe the issue is that the fetch is not able to recognize the proxy settings. A similar task (Node Installer) works perfectly fine, so we don't think the issue is with the proxy.

@KristofKuli There is a PR in flight right now that should resolve this issue

Thank you for the fix! Could you please let me know when this will be available on the Marketplace to update?

Any update on this? I have tested the task, but it is still failing with timeout.

@KristofKuli The task has now been released, if you update to the newest version is it still failing?

Possibly related to #19

Specifying the exact version solved the issue. Thank you.


Empty tests in concurrent causes snapshots to be deleted

Describe the bug
When using describe.concurrent, if there is an empty test as well as a test that uses a snapshot, the behaviour becomes inconsistent.
An empty test is something like it('should be tested'). Note that using it.todo does not cause this issue.
If using toMatchSnapshot() the snapshot will show as "obsolete", and then updating the snapshot will delete the snapshot file. The test will pass then, even though there is no snapshot file.
If using toMatchInlineSnapshot() then the text is not updated, the test always fails, even when manually entering the text.
This seems to happen both when using the expect from the test context, as well as importing it from vitest.
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-mggr55?file=test/suite.test.ts
System Info
System:
    OS: macOS 13.3.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 1.53 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 3.1.1 - ~/.nvm/versions/node/v18.12.1/bin/yarn
    npm: 9.6.5 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 107.0.5304.87
    Firefox: 112.0.2
    Safari: 16.4
  npmPackages:
    @vitejs/plugin-vue: ^4.2.1 => 4.2.1
    @vitest/coverage-istanbul: ^0.31.0 => 0.31.0
    @vitest/ui: ^0.31.0 => 0.31.0
    vite: ^4.3.5 => 4.3.5
    vitest: ^0.31.0 => 0.31.0

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

On further inspection, having any test that is not a todo seems to cause this, not just empty ones. Updating the example and issue to reflect this.


FR: Folder Note 2.0

Thank you so much for this amazing plugin! It's what I've been dreaming (yes, dreaming!) about. This has mad potential. It nearly feels like it's a core feature! The performance alone is commendable. I'm happy to be an early adopter!
As for the request, I believe the plugin absolutely must have the option to function like Folder Note or MAKE.MD where the card view for a folder opens when you click on that folder in the file explorer, with the current expand/collapse folder action being relegated to the chevron.
See you at the top of the Obsidian plugin store! 🙌

100% agree, this would be the biggest feature to implement

I tried Folder Note plugin, and I find myself in confused situation, where in few Vaults I would like to have this feature where I will click on the folder and it will open the Card View, but in few vaults I also felt, it's disturbing me. So, please integrate this feature with a setting option so, user can decide whether to have it or not.

Hello guys!
As a skeptic initially, for having the feature like Folder Notes to open all files from a particular folder in the Cards View, I thought that, it will be computationally expensive to integrate this feature. But as I thought more on having this feature in this plugin, and just gave a try to integrating it. I finally have accomplished the functionality.
User can open Cards View for specific folder from the right-click menu or can directly click on the folder name from the file explorer to open the cards view with all those files. Not only that, but I have added a filter on whether to consider all files from sub-directories or not.
Also this feature is completely optional, and wont be loaded at all if not enabled from the setting, so a performance friendly feature.
I have released a new version of my older Beta version, which you can read more here : https://github.com/jillro/obsidian-cards-view-plugin/pull/27#issuecomment-2526272260


Plot object editor: improve ListBox labels

Suggested by @BambOoxX in #1842, if the plottable has a legend label use that, otherwise use the contents of its ToString() method
Labels are currently being populated like this (which uses ToString() for everything):
https://github.com/ScottPlot/ScottPlot/blob/ef520f92bd50654cb30f1a3e51841bb9909a4dda/src/ScottPlot4/ScottPlot.WinForms/PlotObjectEditor.cs#L16-L17

@swharden I'm not sure I was totally clear. I was referring to not only the lable, but the complete legend item. This way, searching for a plot to edit is close to searching something in the legend (in terms of color, line style ...)

@swharden I'm not sure I was totally clear. I was referring to not only the lable, but the complete legend item. This way, searching for a plot to edit is close to searching something in the legend (in terms of color, line style ...)

Thanks for clarifying! I created this issue to address the ToString() text that IPlottable objects provide which is a pretty different topic than the one you raised.
Regarding this issue though, there's not one place where ToString() is defined. In fact, all plottables have the option to customize their own override, so there's not the consistency required to ensure each plottable adds its legend text in its ToString() override.
It may be possible by creating a PlottableBase, making every IPlottable inherit that, then add such functionality there... but that's a pretty extensive refactor for something pretty trivial. I'll close this issue without modification to the code base.


Apple Software Update Failed

Hi everyone,
I have correctly deployed SUPERMAN and the necessary policies via JAMF Pro.
But during my tests, I get the message "apple software update failed" from the notifier.
Do you have any ideas?
Thanks a lot!

A few things to review on your own.

check the super.log: https://github.com/Macjutsu/super/wiki/Troubleshooting#understanding-the-superlog
check the asu-list.log: https://github.com/Macjutsu/super/wiki/Troubleshooting#asu-listlog


Better Error Messages

Right now if I get an error it could take me hours to figure out its cause.
E.g. messages like "{"Value cannot be null.\r\nParameter name: method"}" or just a plain "System.NullReferenceException" are not very helpfull.

Agreed.  I am not sure there is a lot of exception handling currently.  We also might consider having our own exception type, as this is what JSON.NET does for theirs.  Well, theirs and pretty much every serializer out there. :)

I have to admit everything is pretty happy path for v2, but when are error does occur you should get the full stack trace.  What I would be interested in is seeing if you can reproduce an error for v2 and if it seems better for you or the same.  This is definitely an area where I personally could improve, as I do not (and am not a fan of) covering/cascading code with a bunch of try/catches (as I understand it this is bad practice anyways).
I sort of want to cheat and close this issue, but it is sort of important and I do not think this is the last that we will see of it.  I guess the right approach is to see if you encounter issues in v2 and if there errors are same/worse/better than what you got previously.

Going to close this issue now as there has not been a lot of discussion around this.  I think the error bubbling we have now is a good start for v2.  If you encounter a scenario where the messaging could be better (in v2), please open a new issue and we will take it from there.


New Networking Layer

We would like to improve Deku's networking layer such that it is simpler, more reliable, and maintains performance.
Currently a major issue with the networking layer is that if we have some peers, A, B, and C, such that:

A and C are peers
C and B are peers
A and B are not peers

and A broadcasts a message, C will receive it, but B will not. This is incorrect behaviour. The networking layer should be reworked such that so long as there is a path between A and B, regardless of whether or not A and B are peers, any message broadcasted by A should be received by B and vice versa. At the same time, this should be done in a way that avoids sending O(n^2) messages.
In the process of achieving this, there are various sub-goals that will help generally improve the quality of the networking layer, including:

[ ] #441
[x] #442
[x] #443

We fixed the bugs in connectivity but still have O(n^2) communication. Closing this issue - we will address improving gossip separately.


SAK-43144 fix uncaught TypeError by checking for existence of portal user

CC: @profmikegreene

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- library/src/morpheus-master/js/src/sakai.morpheus.usernav.js  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- webcomponents/tool/src/main/frontend/sakai-i18n.js  2
- library/src/morpheus-master/js/src/sakai.morpheus.usernav.js  2

See the complete overview on Codacy


Feature/hyp 113

What
A few tweaks to the timeline components so it pulls real data and renders as per certificates state along with the new route /create to not disturb existing changes.

it does add one extra warning (linting). To be fair a few warnings were already there and logic would need changing

is just insane...


upgrade blueprints to 2.0.0-alpha.47

[ ] package.json needs to be updated (we intentionally bump the version manually each time for now to have control over breaking changes that require blueprints update)
[ ] replace import ... from 'angular2/angular2' with ... from 'angular2/core' (this might still change in the future, see https://github.com/angular/angular/issues/5539, but for now let's switch to core)
[ ] the only exception to the above is bootstrap which should come from import {bootstrap} from 'angular2/platform/browser'

that should be it...
cc: @wardbell for documentation update since that will be affected in similar way

Anyone wants to work on this?

Can I assign to me?

sure
On Tue, Dec 1, 2015 at 5:16 PM Ciro Nunes<EMAIL_ADDRESS>wrote:

Can I assign to me?
—
Reply to this email directly or view it on GitHub
https://github.com/angular/angular-cli/issues/84#issuecomment-161148124.

@cironunes if not you're busy, this is something that I'm more than willing to take on

I'm getting many errors from TypeScript, I think that they are related to typings.
I noticed that there's a breaking change regarding typings. Is it supposed to break?

I mean, aren't we already using typings from the package?

We are. It should work just fine. I tested a generated app locally with 47
and it bootstrapped without errors. I haven't tested anything else though.
On Tue, Dec 1, 2015 at 5:56 PM Ciro Nunes<EMAIL_ADDRESS>wrote:

I mean, aren't we already using typings from the package?
—
Reply to this email directly or view it on GitHub
https://github.com/angular/angular-cli/issues/84#issuecomment-161154966.

@IgorMinar was that a TypeScript project?

Forget about it. It's working fine.


Initial support for x10 in the toolchain

This adds a new flag to the to utils/build-toolchain-tensorflow, --x10 (or -x) which creates a build with support for TPUs using the x10 library. It mainly does two things:

Replaces libtensorflow.so with a superset, libx10.so, which contains the added lazy XLA tensor functionality.
Collects relevant C++ headers to be used by the x10 build to land in swift-apis, setting the X10_INCLUDE_DIR to the folder in which they're collected.

This will need to land after https://github.com/tensorflow/swift-apis/pull/719, at which point we'll be able to set the dependency hash correctly.

@pschuh We don't know yet the hash under which the swift-apis PR would land with and I'd like to do an end-to-end test of this before merging. Thanks for approving!

#define TPU 🍩

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow


[Aspire] Figure out a story for dev time provisioning

Today when an Aspire project references azure resources, when you F5 there's a bunch of code that runs from the Provisioning packages to provision dev time resources.
We'd like to look at a model where instead azd does this provisioning somehow - ideally as just another environment for the project.
This requires close work with the VS folks and Aspire.

@ellismg can you check with @davidfowl @mitchdenny on this?

I can see a few challenges getting this working, but curious what the benefit of doing this is? Consistency?


Meta: Release 0.1

Goals

good enough for live SSB on the GPU
good enough code quality, good enough performance
experimental API

What's still missing:

[x] convenience functions for plotting
[x] convenience functions for running UDFs on live data streams
[x] test infra and some test coverage via integration tests (#10)
[x] updated README
[x] minimal docs: add some keywords for libertem live sim etc.
[x] sample notebook!
[ ] Update override_requirements.txt after LiberTEM 0.7 is released

Maybe

[ ] support for more bit depths of the Merlin Medipix?
[ ] cleanly separate libertem-dependent parts, so this project can be used in a non-LiberTEM context, even without installing LiberTEM at all

@uellue anything I missed?

Discussion with @sk1p: The parts under "Maybe" can be done in 0.2. :-)

[ ] When updating the version to the release and tagging it, we can remove the note from the README about not being released yet.