node run and build take a lot of memory

yarn build on a 2gb VM quickly exhausts the memory and crashes the VM.
yarn run uses 1Gb+ rss in usage.
yarn build produces a 38Mb output.
Need to reduce all.

[dev] [mav@maverick-ubuntuvm ~/code/maverick-web]$ yarn build
yarn run v1.22.4
$ vue-cli-service build

⠋  Building for production...To enable GQL files in ESLint, set the `pluginOptions.apollo.lintGQL` project option to `true` in `vue.config.js`. Put `false` to hide this message.
You also need to install `eslint-plugin-graphql` and enable it in your ESLint configuration.
⠙  Building for production...

 WARNING  Compiled with 3 warnings                                                                                1:42:05 PM

 warning

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  html.worker.js (531 KiB)
  css.worker.js (809 KiB)
  ts.worker.js (3.48 MiB)
  js/app.49dd4eba.js (406 KiB)
  css/chunk-vendors.6ad3efae.css (425 KiB)
  js/chunk-vendors.89771c94.js (2.42 MiB)

 warning

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  app (3.23 MiB)
      css/chunk-vendors.6ad3efae.css
      js/chunk-vendors.89771c94.js
      css/app.25f78e49.css
      js/app.49dd4eba.js

 warning

webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

  File                                   Size              Gzipped

  dist/ts.worker.js                      3560.79 KiB       807.00 KiB
  dist/js/chunk-vendors.89771c94.js      2478.62 KiB       680.47 KiB
  dist/css.worker.js                     808.92 KiB        173.63 KiB
  dist/html.worker.js                    531.22 KiB        131.95 KiB
  dist/js/app.49dd4eba.js                406.37 KiB        78.69 KiB
  dist/json.worker.js                    231.95 KiB        65.83 KiB
  dist/editor.worker.js                  124.35 KiB        39.11 KiB
  dist/css/chunk-vendors.6ad3efae.css    424.82 KiB        48.92 KiB
  dist/css/app.25f78e49.css              1.87 KiB          0.70 KiB

  Images and other types of assets omitted.

 DONE  Build complete. The dist directory is ready to be deployed.
 INFO  Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

Done in 98.28s.

After disabling monaco editor:
[dev] [mav@maverick-ubuntuvm ~/code/maverick-web]$ yarn build
yarn run v1.22.4
$ vue-cli-service build

⠋  Building for production...To enable GQL files in ESLint, set the `pluginOptions.apollo.lintGQL` project option to `true` in `vue.config.js`. Put `false` to hide this message.
You also need to install `eslint-plugin-graphql` and enable it in your ESLint configuration.
⠏  Building for production...

 WARNING  Compiled with 3 warnings                                                                                1:58:57 PM

 warning

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  js/app.e7546c08.js (406 KiB)
  css/chunk-vendors.6ad3efae.css (425 KiB)
  js/chunk-vendors.89771c94.js (2.42 MiB)

 warning

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  app (3.23 MiB)
      css/chunk-vendors.6ad3efae.css
      js/chunk-vendors.89771c94.js
      css/app.25f78e49.css
      js/app.e7546c08.js

 warning

webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

  File                                   Size              Gzipped

  dist/js/chunk-vendors.89771c94.js      2478.62 KiB       680.47 KiB
  dist/js/app.e7546c08.js                406.37 KiB        78.69 KiB
  dist/css/chunk-vendors.6ad3efae.css    424.82 KiB        48.92 KiB
  dist/css/app.25f78e49.css              1.87 KiB          0.70 KiB

  Images and other types of assets omitted.

 DONE  Build complete. The dist directory is ready to be deployed.
 INFO  Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

Done in 60.54s.

Massive difference

Disabling xtermjs, cesium and layers reduces significantly further.
[dev] [mav@maverick-ubuntuvm ~/code/maverick-web]$ yarn build
yarn run v1.22.4
$ vue-cli-service build

⠋  Building for production...To enable GQL files in ESLint, set the `pluginOptions.apollo.lintGQL` project option to `true` in `vue.config.js`. Put `false` to hide this message.
You also need to install `eslint-plugin-graphql` and enable it in your ESLint configuration.
⠸  Building for production...

 WARNING  Compiled with 3 warnings                                                                                2:29:48 PM

 warning

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  js/app.ffeb3ad4.js (391 KiB)
  css/chunk-vendors.e5386d39.css (421 KiB)
  js/chunk-vendors.d5948740.js (1.05 MiB)

 warning

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  app (1.85 MiB)
      css/chunk-vendors.e5386d39.css
      js/chunk-vendors.d5948740.js
      css/app.a4e06123.css
      js/app.ffeb3ad4.js

 warning

webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

  File                                   Size              Gzipped

  dist/js/chunk-vendors.d5948740.js      1078.97 KiB       321.25 KiB
  dist/js/app.ffeb3ad4.js                391.36 KiB        75.21 KiB
  dist/css/chunk-vendors.e5386d39.css    420.99 KiB        47.75 KiB
  dist/css/app.a4e06123.css              1.00 KiB          0.47 KiB

  Images and other types of assets omitted.

 DONE  Build complete. The dist directory is ready to be deployed.
 INFO  Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

Done in 48.60s.

Disabling store/mdoules/schema.js and plugins/mavlink/mavlinkEnumData.json reduces the main app.js a massive amount:
[dev] [mav@maverick-ubuntuvm ~/code/maverick-web]$ yarn build
yarn run v1.22.4
$ vue-cli-service build

⠋  Building for production...To enable GQL files in ESLint, set the `pluginOptions.apollo.lintGQL` project option to `true` in `vue.config.js`. Put `false` to hide this message.
You also need to install `eslint-plugin-graphql` and enable it in your ESLint configuration.
⠼  Building for production...

 WARNING  Compiled with 3 warnings                                                                                2:51:36 PM

 warning

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  css/chunk-vendors.25d3568b.css (421 KiB)
  js/chunk-vendors.d5948740.js (1.05 MiB)

 warning

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  app (1.64 MiB)
      css/chunk-vendors.25d3568b.css
      js/chunk-vendors.d5948740.js
      css/app.a4e06123.css
      js/app.b43587e9.js

 warning

webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

  File                                   Size              Gzipped

  dist/js/chunk-vendors.d5948740.js      1078.97 KiB       321.25 KiB
  dist/js/app.b43587e9.js                182.45 KiB        30.89 KiB
  dist/css/chunk-vendors.25d3568b.css    420.99 KiB        47.75 KiB
  dist/css/app.a4e06123.css              1.00 KiB          0.47 KiB

  Images and other types of assets omitted.

 DONE  Build complete. The dist directory is ready to be deployed.
 INFO  Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

Done in 36.29s.

Removed vuelayers (still being called by Planner2d component)
[dev] [mav@maverick-ubuntuvm ~/code/maverick-web]$ yarn build
yarn run v1.22.4
$ vue-cli-service build

⠋  Building for production...To enable GQL files in ESLint, set the `pluginOptions.apollo.lintGQL` project option to `true` in `vue.config.js`. Put `false` to hide this message.
You also need to install `eslint-plugin-graphql` and enable it in your ESLint configuration.
⠋  Building for production...

 WARNING  Compiled with 3 warnings                                                                                3:01:25 PM

 warning

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  css/chunk-vendors.70c99fb0.css (421 KiB)
  js/chunk-vendors.658436e2.js (920 KiB)

 warning

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  app (1.47 MiB)
      css/chunk-vendors.70c99fb0.css
      js/chunk-vendors.658436e2.js
      css/app.7f98b729.css
      js/app.a6cde628.js

 warning

webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

  File                                   Size              Gzipped

  dist/js/chunk-vendors.658436e2.js      920.08 KiB        275.91 KiB
  dist/js/app.a6cde628.js                163.09 KiB        26.57 KiB
  dist/css/chunk-vendors.70c99fb0.css    420.99 KiB        47.72 KiB
  dist/css/app.7f98b729.css              0.58 KiB          0.32 KiB

  Images and other types of assets omitted.

 DONE  Build complete. The dist directory is ready to be deployed.
 INFO  Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

Done in 36.98s.
[dev] [mav@maverick-ubuntuvm ~/code/maverick-web]$

@SamuelDudley - i'm going to permanently remove monaco from the main vue.config.js because it increases the size of the build by about 10x!
We can put it back by looking at lazy loading or at a vue component eg:
https://github.com/egoist/vue-monaco
The component approach will hopefully automatically include it in a more efficient manner.

@SamuelDudley - i'm going to permanently remove monaco from the main vue.config.js because it increases the size of the build by about 10x!
We can put it back by looking at lazy loading or at a vue component eg:
https://github.com/egoist/vue-monaco
The component approach will hopefully automatically include it in a more efficient manner.

So considering -web will be served mainly over a local network, others are not likely going to use -web-dist and we have a way of reliability building -web-dist from -web do you think the bundle size actually matters?

I should add I'm okay with removing stuff, but I want to maintain a branch with it included so that the hours of work to date are not lost to bitrot.

Example chunking and removal of unused features
https://github.com/microsoft/monaco-editor-webpack-plugin/issues/97

Links to some tools to help with bundle analysis and code splitting https://github.com/kristerkari/awesome-bundle-size

Rollup and parcel both support Vue and tree shaking.

So considering -web will be served mainly over a local network, others are not likely going to use -web rather -web-dist and we have a way of reliability building -web-dist from -web do you think the bundle size actually matters?

When you're talking about a factor of 5-10 then I think it really matters - it's not just that you're loading 8-10mb javascript over the network, it's that your poor browser has to execute that 8-10mb javascript.  It's why the ttfp was so slow.  This is just as much about the size and speed of -web-dist than memory usage of -web.
I'm absolutely not talking about losing any of the work that either of us have done, just disabling it all except for the basics so we can see what is actually necessary.  What's in master now is really the basic core of what we can get away with - vue, vuex, vue-router, vuetify, apollo, and we're down to about 1mb js.  This can be further improved with treeshaking and chunking - certainly vue and vuetify can be improved significantly.
I've disabled the mavlink-related components (cockpit, planner in particular) which then removes the likes of vuelayers/openlayers, pixi.js, cesium, and disabled the more advanced config features like xtermjs and monaco.  All of this is simply disabled btw, none of the code is gone.
Then, we can start to re-enable carefully, watching the bundle size and ttfp as we go along.  I suggest that for the 1.2 release we keep all the mavlink stuff disabled and just concentrate on the config, maverick and video modules.

@cglusky I haven't either before, certainly worth a look.
@fnoop Taking a step back, my thoughts are that -web is very different to a normal webpage, e.g. a web store that is used to sell mountain bikes.
Using the bike store example, loading and execution times are very important as delays in getting pictures rendered might be the difference in a sale vs a user giving up and looking somewhere else. In the case of maverick-web users are much more heavily invested in the whole maverick / autonomous system ecosystem and will happily deal with much longer start-up times.
Additionally many of the use cases are over local networks where throughput is much less of an issue. Lastly, once its all cached in the browser, the network issue is now gone.
I agree with what you are doing and your plan. I just wanted to ensure that we don't limit ourselves for the sake of a small bundle size and super fast ttfp.
On the ttfp: In vue-vanilla-cesium I enabled chunking of cesium (https://github.com/SamuelDudley/vue-vanilla-cesium/blob/master/vue.config.js#L81) and lazy loading of the web endpoint that used cesium in the vue router (https://github.com/SamuelDudley/vue-vanilla-cesium/blob/master/src/router/index.ts#L12)
The combination of those two optimizations means that the application loads the login screen instantly and then starts parallel background requests to pull down the cesium js bundle as they type in the login info.
We could look ad doing something similar for the maverick-web landing page and prioritizing what chunks are loaded based on what a user is likely to first interact with.

Using the bike store example, loading and execution times are very important as delays in getting pictures rendered might be the difference in a sale vs a user giving up and looking somewhere else. In the case of maverick-web users are much more heavily invested in the whole maverick / autonomous system ecosystem and will happily deal with much longer start-up times.

Yes I completely agree.  I just think it had got a bit out of hand and wanted to get back to basics and get that right before going forward!

see https://github.com/goodrobots/maverick-web/tree/ttfp for changes to reduce ttfp

most of the delay in ttfp when viewing the webpage via webdev is the hot reload server itself. When viewing the dist ttfp is quite snappy.

With the lazy loading of modules enabled the javascript behaves as expected.
The js circled in red near the top is all the core stuff + the home module. The other stuff circled in blue lazy loads in after, which is good. The bad thing is that the other media requests don't start until all the lazy loaded js is done.
Need to find a way to move the media requests up the call stack.

looks like we need to make the components async to avoid waiting
https://vuejs.org/v2/guide/components-dynamic-async.html#Async-Components

have a look at https://goodrobots.github.io/maverick-web/ to get a feel for the current page load speed.
With the code splitting in place it would be interesting to re-enable some of the features and see if it has helped.

Some testing with a new vue-cli repo leads me to believe that vuetify is already being tree shaken.

looks like all the css is bundled

Before enabling xterm, a yarn build takes about max 700mb memory, size of build:
app (1.61 MiB)
Built web page definitely much faster to load.  It has now chunked into dozens of files which means lots of http connections.  Also lots of warnings in the build process so needs tidying up a bit.

After xterm, yarn build still takes about 700mb, size of build: app (1.61 MiB).  Odd.

I think my chunking strategy is a bit aggressive currently. We can tweak it to make less, larger chunks.

There is a brilliant report built and pushed to -web-dist:
http://maverick-raspberrylite.local/report.html

The chunking is working great - it's much better than without.  If we can reduce the core chunking in the future that would be great.

Sorry, I thought you were aware of that report feature! As you can see its chunking each npm package individually. We can keep this logic in place and add a few hand crafted rules to merge a lot of the smaller bits of common code.


chore: upgraded to Node.js 20.10.0

Description
Sets the Node.js engine to a minimum of 18.17.0.
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[x] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
Relates to #72
Mobile & Desktop Screenshots/Recordings

Steps to QA

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Maybe I'm reading the failure wrong, but doesn't moving to Node.js 18.17.0 fix the engine issue?
Run npm i -g npm@latest
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Required: {"node":"^18.17.0 || >=20.5.0"}
npm ERR! notsup Actual:   {"npm":"8.19.[4](https://github.com/open-sauced/opengraph/actions/runs/7232618888/job/19765768242#step:4:5)","node":"v1[6](https://github.com/open-sauced/opengraph/actions/runs/7232618888/job/19765768242#step:4:7).20.2"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2023-12-19T00_11_4[7](https://github.com/open-sauced/opengraph/actions/runs/7232618888/job/19765768242#step:4:8)_407Z-debug-0.log
Error: Process completed with exit code 1.

Maybe I'm reading the failure wrong, but doesn't moving to Node.js 18.17.0 fix the engine issue?

I would think so, however it seems like something is quite seeing the npm and node change. Does npm run prebuild && npm run build work locally?

Maybe needs fixing here also https://github.com/open-sauced/opengraph/blob/beta/Dockerfile#L20

The workflow files need to be updated to use the open-sauced/hot workflows instead of open-sauced/open-sauced also
https://github.com/open-sauced/app/blob/beta/.github/workflows/compliance.yml#L15 https://github.com/open-sauced/app/blob/beta/.github/workflows/development.yml#L14C1-L14C1

This was helpful. I fix this PR with this - https://github.com/open-sauced/contributor.info/pull/16/commits/cd6bdc2d9abd2ed3e36b4788057e47bb780b21f0

Not sure why this fails still. All the workflows are updated, the docker file etc. 🫠

The workflows in opensauced/hot are set to use node 18, which would conflict with us trying to use node 20 here

We're using node 18 in the app https://github.com/open-sauced/app/blob/beta/.github/workflows/release.yml#L37

Il revert the node 20 upgrade then and just keep the updated workflows. Originally I thought it required Node 20, but it sounds like just updating workflows should be good.


Suggestion for introduction text

Hello,
I am Anne (they/them), and I am a new intern. Today I was working on ideas for Tweets to promote workshops online, and I found that the description of the workshop leaves a few things unclear to the user.
The description uses a lot of important keywords, and I know the syllabus is provided, but I think it would be nice to have a little more information on what good software practices actually entail. For example, a brief description of each item in the schedule or an overview of some methods and their implementations in the description.
Kind regards

Thanks for your suggestion @theredgeek . Do you feel comfortable opening a PR with suggestions for changes? Otherwise I will try to pick it up in the next few weeks.

And I assume you refer to the description in workshop-metadata? The descriptions in this repo will only be seen by employees of the nlesc.

Fixed with https://github.com/esciencecenter-digital-skills/workshop-metadata/pull/91


Add the ability of saving the conversation in a file and loading it

I've been enjoying using your Chrome extension and find it to be extremely useful. I wanted to take a moment to propose a feature that I believe would significantly enhance the user experience.
Feature Request:
Would you consider adding a feature that enables users to save their conversations to a local file? Additionally, it would be beneficial to have the option to load these saved conversations at a later time.
Implementation Suggestions:

A "Start Recording" button could initiate the process of saving conversations to a local file. Every time the Ollama module responds, we can concatenate the new content to the file.
Users could select which saved conversations to reload via a dropdown menu or list within the extension's interface.

I think this feature offer a convenient way to revisit past conversations.
Thank you in advance

Hi @rsabir - I've just added an option to use localStorage to save and load chats.
https://ollama-ui.github.io/ollama-ui/
Let me know if you still need an option to save and load from a local file instead

Hello!
I have just tested the new update and it seems working pretty well for now. So I would say no need for the local file feature.
Thank you for the quick response!


Use github actions to build wheels.

For now, still use circleci checks before merging to master.  circleci is faster, but doesn't support all platforms for building wheels as easily.
By publishing wheels for many platforms, this should close issues users have with building cython locally.
Closes #1008.
Closes #980.
Closes #964.
Closes #930.
Closes #898.
Closes #892.
Closes #616.

I'm not sure I can completely test this without merging and doing a release, so there may be some churn if I have something wrong.


Unexpected token import

In order to use that package in typescript based project, I use require import statement
const google = require('googleapis')
However when I try to run tests which are written with jest, I am getting that error
Test suite failed to run

    <project_root>/node_modules/googleapis/lib/discovery.ts:14
    import generatorUtils from '../scripts/generator_utils';
    ^^^^^^

    SyntaxError: Unexpected token import

      at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:305:17)
      at Object.<anonymous> (node_modules/googleapis/lib/googleapis.js:17:21)
      at Object.<anonymous> (src/service/gaReport.service.ts:7:16)

It seems try to compile 'googleapis' code under 'node_modules' folder, however I already ignored it.
package.json
 "transform": {
      "^.+\\.tsx?$": "<rootDir>/node_modules/ts-jest/preprocessor.js"
 },
 "testRegex": "(/__tests__/.*|(\\.|/)(test1|spec1|jest))\\.(tsx?)$",
 "testPathIgnorePatterns": [
      "<rootDir>/node_modules"
 ],

tsconfig.json
  "exclude": [
    "build",
    "node_modules",
    "src/shared/ncshared",
    "src/scripts"
  ]

Versions
    "typescript": "~2.5.0"
    "jest": "^21.2.1",
    "ts-jest": "^21.1.4",

I found the problem, it's not about 'googleapis' in fact. When 'googleapis' is required, one of its dependencies ('./discovery') is also been resolving by jest. But in lib directory, there are two files that match 'discovery' name. (.js and .ts files). Module resolution process choose .ts file depend on jest config. At the end, it tries to resolve 'discovery.ts' which is not correct.
To fix it; in 'package.json' change jest config in that order:
"moduleFileExtensions": [
      "js",
      "jsx",
      "ts",
      "tsx",
      "json"
],


Wrap cluster-specific namespace in lookup

Description of changes: Lookup since we keep the namespace and might have it from previous install.
Also fix Secret lookup
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


orange3 requirement

Hi,
Do we still use orange3? I think that could be an artifact from the predecessor of CAVE.
I have troubles to install it in a recent anaconda environment. If possible, consider to remove it.
Cheers,
Marius

We don't need it. Fixed with 38f06998fcffaf1c6caa00028f0f2bf0aaa9609c. Thanks!


[Question] How much faster is Fury compared to Protobuf, and does the measurement include the time taken for Protobuf construction?

Question
How much faster is Fury compared to Protobuf, and does the measurement include the time taken for Protobuf construction?

4~10X faster, you could benchmark yourself.  Protobuf construction is included since most users will use POJO as the data container.


Clicking "Launch Studio" crashes program

Hello! Woke up today and wasn't able to launch studio. Updated to the latest version of mod manager with no luck.
Details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at RobloxDeployHistory.ClientVersionInfo..ctor(DeployLog log) in C:\Users\clone\Documents\GitHub\Roblox-Deploy-History\History\ClientVersionInfo.cs:line 43
   at RobloxStudioModManager.StudioBootstrapper.<GetCurrentVersionInfo>d__76.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at RobloxStudioModManager.StudioBootstrapper.<Bootstrap>d__84.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at RobloxStudioModManager.BootstrapperForm.<Bootstrap>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at RobloxStudioModManager.Launcher.<launchStudio_Click>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

************** Loaded Assemblies **************
mscorlib
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9195.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
RobloxStudioModManager
    Assembly Version: <IP_ADDRESS>
    Win32 Version: <IP_ADDRESS>
    CodeBase: file:///C:/Users/chase/AppData/Local/Roblox%20Studio/RobloxStudioModManager.exe
----------------------------------------
System
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9195.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: <IP_ADDRESS>
    Win32 Version: <IP_ADDRESS>
    CodeBase: file:///C:/Users/chase/AppData/Local/Roblox%20Studio/RobloxStudioModManager.exe
----------------------------------------
System.Core
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9195.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9195.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9037.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Numerics
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9037.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9037.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Data
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9195.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9037.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: <IP_ADDRESS>
    Win32 Version: 4.8.9037.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
RobloxDeployHistory
    Assembly Version: <IP_ADDRESS>
    Win32 Version: <IP_ADDRESS>
    CodeBase: file:///C:/Users/chase/AppData/Local/Roblox%20Studio/RobloxStudioModManager.exe
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Disregard, tried it again just now and it worked fine. Maybe something changed on Roblox's end, or maybe launching RobloxStudioBeta directly fixed something about my installation.


Right-clicking or clicking certain notification icons in the menu doesn't do anything.

Such as Discord or Rainmeter.

This is fixed in the latest build.


Fix some sliders (please)

Fix chorus, distortion, and bitcrush sliders to have 8 divisions and the frequency crush slider with 14 divisions to match the modulator limits

It appears that my bad internet has caused this issue to be duplicated. This issue will now be closed


Big Map PR

Added HomeMap to landing page,
HomeMap allows user to save an event
Added ArtistMap to ArtistProfile page,
ArtistMap allows artist to create a new event
Style changes to the map , more to follow

 User clicks on map to view events , save events

 :warning: User can click/hover over a pin on the map and see details for the performance (busker name, time, location) plus an Add/Save button.

 :warning: User clicks Map link in landing page and navigates to Map view.


Unhandled empty HTTP response content

Using python3.6 and python3.5 with async framework.

When trying to send very long text messages this error occurs:
WARNING:aiohttp.client:Attempt to decode JSON with unexpected mimetype:

ERROR:asyncio:Task exception was never retrieved
future: <Task finished coro=<Answerer.answer.<locals>.compute_and_answer() done, defined at telepot/aio/helper.py:100> exception=TypeError("'NoneType' object is not subscriptable",)>
Traceback (most recent call last):
  File ".. telepot/aio/helper.py", line 107, in compute_and_answer
    await self._bot.answerInlineQuery(query_id, ans)
  File ".. telepot/aio/__init__.py", line 296, in answerInlineQuery
    return await self._api_request('answerInlineQuery', _rectify(p))
  File ".. telepot/aio/__init__.py", line 68, in _api_request
    return await api.request((self._token, method, params, files), **kwargs)
  File ".. telepot/aio/api.py", line 110, in request
    return await _parse(r)
  File ".. telepot/aio/api.py", line 87, in _parse
    if data['ok']:
TypeError: 'NoneType' object is not subscriptable

Long messages
Text length limit sending chat messages are well define,
in fact api.telegram.org return the proper HTTP response error code for code like this:
async def handle(msg):
    text = "".join(["☆" for i in range(5000)])
    await bot.sendMessage(msg["from"]["id"],text)

The bot receive this HTTP response:
HTTP/1.1 400 Bad Request
Server: nginx/1.10.0
Date: Sun, 08 Jan 2017 00:18:49 GMT
Content-Type: application/json
Content-Length: 78
Connection: keep-alive
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Content-Length,Content-Type,Date,Server,Connection

With HTTP response content:
{"ok":false,"error_code":400,"description":"Bad Request: Message is too long"}

It raises a TelegramError and everything is handled fine.
Very long messages
One believe that the error from the server will be the same for text of any length greater than the limit,
but this is not true, if one try to send even more text than before like with the following code, the error is different.
async def handle(msg):
    text = "".join(["1" for i in range(65536)])
    await bot.sendMessage(msg["from"]["id"],text)

This is not so infrequent, in fact when dealing with article inline answers in which each of the 50 result slots available have a lot of text is easy to exceed that limit without exceeding the text limit for the single inline article.
With the above code another telegram server limit is reached(~65kB)[1], in this case the HTTP response is different  (status [413 Request Entity Too Large]), and a 0 length response content is returned.
In telepot this error isn't caught by the exception handling block because aiohttp response.json() successfully return None instead of fail in parsing an empty string as json (not sure why).
And thus it fails later with an unhandled error and a traceback like the one at  the beginning.
The HTTP response received is:
HTTP/1.1 413 Request Entity Too Large
Server: nginx/1.10.0
Date: Sun, 08 Jan 2017 00:19:03 GMT
Content-Length: 0
Connection: keep-alive
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Content-Length,Content-Type,Date,Server,Connection

With empty response content:

Traceback:
Traceback (most recent call last):
  File "simple/skeletona.py", line 22, in handle
    await bot.sendMessage(msg["from"]["id"],text)
  File telepot/aio/__init__.py", line 79, in sendMessage
    return await self._api_request('sendMessage', _rectify(p))
  File telepot/aio/__init__.py", line 68, in _api_request
    return await api.request((self._token, method, params, files), **kwargs)
  File telepot/aio/api.py", line 111, in request
    return await _parse(r)
  File telepot/aio/api.py", line 88, in _parse
    if data['ok']:

[1] See it happen with:
for i in `seq 65500 10 66000`; do echo ""; echo $i; curl -i --data chat_id=<chat_id> --data-urlencode  "text=`printf '1%.s' $(seq 1 $i)`" https://api.telegram.org/bot<TOKEN>/sendMessage; done

Thanks for laying out the entire story and describing it clearly. Telepot should handle the empty response properly and raises an exception. I will fix that in a later version.

Fixed in 10.5. @tmmsartor, thanks for making telepot better.
Curiously, this issue does not occur in the traditional (non-async) version. When I send a very long message, it gives me a normal TelegramError saying Message is too long. Didn't bother to look deeper, though.

How can I solve this issue?
I had this error with my bot: "'Bad Request: message is too long', 400"
Where the text sent from my bot is very long because is a document text of 11000 words.

@Onofrio310817, it seems like Telegram servers returned this error and telepot was simply relaying that error to you. In other words, Telegram servers were refusing your request because the "message is too long". The only way to fix it is to send shorter messages. Telepot cannot help you there :relaxed:

@nickoala thank you for your answer, infact I have to try a new way to send long message because I have just integrated Pocket apps with the bot and so in this case it has to send me message with text of article saved on Pocket.


Issue With Teams PowerShell Module : Get-TeamUser returns 0 values incorrectly

I am using the MicrosoftTeams PowerShell Module version 5.1.0.
When you run the script below (we have approx. 1500 Teams) we get 0 owners sometimes which is wrong.
Connect-MicrosoftTeams -Credential (Get-Credential);
$allActiveTeams = Get-Team -Archived $false;
foreach($team in $allActiveTeams ){
$listOwners = Get-TeamUser -GroupId $team.GroupId -Role Owner | Sort-Object Name;
Write-Host $listOwners.Count;
}
With the previous version 4.2.0 we didn't have this issue.

Hello @inseu
How are you?
As here we are limited to documentation fixes, I tried to see if we needed to update any article, however I wasn't able to reproduce what you have experienced, the best would be to open a support request, if you identified that a team is returning 0 owners but you verified it has.
Thank you,

Thanks for returning and sharing that information.


⚠ ClamAV has degraded performance

In c2b42c9, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 74 ms

Resolved: ClamAV performance has improved in 124b72d.


az wrongly assumes Python executable

Describe the bug
When installing azure-cli on Ubuntu 18.04 LTS with
# apt install python3-pip
# pip3 install azure-cli

the installed CLI does not work with az:
# az --version
/usr/bin/python: No module named azure
#

This is due to the fact that the az script assumes that python is the Python executable that can be used to import azure.cli. Due to PEP 394 – The "python" Command on Unix-Like Systems this may not be the case. (The gist of it is that Python 3 is expected to be installed as python3 in a system-wide context, while python remains Python 2, if installed.)
Running python3 -m azure.cli --version (which is what az should do) does work as expected.
To Reproduce
See above.
Expected behavior
az works without shenanigans.
Environment summary

OS: Ubuntu 18.04 LTS
Install method: See above.
Shell: Bash 4.4.19
python -m azure.cli --version: azure-cli (2.0.45)

Additional context
This problem would probably be fixed by using distutils entrypoints instead of a bespoke az shell script.

Ah, this seems to be a duplicate of #1043 . . . Either way, leaving it open here as it provides further detail.

@yugangw-msft Is this related to Debian or pip? wouldn't the tage Packaging/Pip be more accurate?

Is there any resolution I'm having the same issue

Looking at this issue's history, it's clear that there's been a lot of turbulence with how much of a priority this issue should be. But I think it hints at an internal struggle that we've had, which is answering the questions, "do we support pip install azure-cli?"
We've never officially said that we do, but we also make sure that the latest version is always published to PyPI. We've also changed design decisions to make sure that folks who install using pip have a coherent version of the CLI.
For me personally (not necessarily how my whole team feels), it's never seemed like a priority. I say that because as an application, I would think even which programming language was used should be largely opaque to the customer. I'd rather emphasize platform specific installers, like our MSI installer, and packages made for Linux package managers. It gives us a lot more control to provide idiomatic experiences for people in different environments, especially folks who are not Python developers.
Not saying that it isn't painful, or that it shouldn't be fixed. But hopefully this sheds some light on why this issue has never garnered much attention.

Another update, the team is in the middle of a shuffle. I don't believe I'll have time to work on this issue in the next week before I'm on a different team. For that reason, I'm going to unassign myself.

It doesn't matter if you officially support pip install or not, I bet there is a reason the az script the way it does, but this is easily solvable by using the built-in entrypoints in setup.py, which should use which ever environment the user is using instead of making decisions for the user.
This should not affect the OS packaged installation.

Apparently setuptools has some drawbacks accordingly to this PR  #1042 😳

The perf drawbacks are easily mitigated with https://pypi.org/project/fastentrypoints/ .

fixed by https://github.com/Azure/azure-cli/pull/10516


Add a core end2end test to represent client-side streaming

Please answer these questions before submitting your issue.
Should this be an issue in the gRPC issue tracker?
Yes
What version of gRPC and what language are you using?
C core at master 1.4-dev
What operating system (Linux, Windows, …) and version?
Linux
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc
What did you do?
This is a feature request . There is currently no end2end test that has the same behavior as client-side streaming. Basically, this entails:
Server: recv initial metadata
Client: send initial metadata
Server: send initial metadata, recv trailing metadata
Client: send message
Server: recv message
[repeat the above 0 or more times]
Client: send trailing metadata
Server: recv message
What did you expect to see?
A test with the above characteristics
What did you see instead?
Lots of other awesome tests, but the above test is better captured in test/cpp/end2end/async_end2end_test . It would be nice to have it seen in the core tests itself.
Anything else we should know about your project / environment?
Writing a transport and trying to document the process of writing transports.

This ties in to Nathaniel's suggestions in #7032 . There are a few categories of core end2end tests that could be added.

Thanks for digging this up, Vijay! Should be fixed by https://github.com/grpc/grpc/pull/22668


:name_badge: Please provide a ready-to-use md badge :memo:

:grey_question: About
We tend to use xc on vairous projects and I would like peple to be aware that the reposiotry  uses xc to describe various available tasks.
:point_right: Providing a badge would help a lot :sloth:
:dart: Feature request

[ ] Provide a ready to use markdown badge we could copy/paste on top of our README.md
[ ] Make it clickable so it makes people land to https://xcfile.dev/

:moneybag: Benefits

No need to tell people what the README is capable of... nor how to use it :sloth:

This is a brilliant idea, I have been trying to think of ways to signpost a readme as xc ready, for discoverability reasons as well as so we can easily track uptake in open source!

I hope this is what you had in mind: https://xcfile.dev/getting-started/#let-people-know-you-use-xc

I hope this is what you had in mind: https://xcfile.dev/getting-started/#let-people-know-you-use-xc

Sure it is 🤩

https://github.com/adriens/auptitcafe-data/pull/8

Nice shot and thanks a lot for feedback 🙏


Update README to reflect the latest modules

README has reference to dead link for Spring Integration.
We can maybe replace the current bullet lists w/ the table format that we have prepared in the blog? :)

README's are not blocking for M2. Only the refdoc really matters.


Setting focus on buttons in Dialog doesn't work

use cursive::views::{Dialog, TextView};
use cursive::*;

fn main() {
    let mut siv = cursive::default();

    let mut dlg =
        Dialog::around(
                TextView::new("TextView"),
        ).button("Ok",|s|{}).button("Cancel",|s|{});

    dlg.set_focus(cursive::views::DialogFocus::Button(1));//Want to have focus on Cancel
    siv.add_layer(dlg
    );

    siv.run();
}

Hi, and thanks for the report!
Indeed, the focus for Dialog had a few issues, and (among other things) was getting reset to the first child at the beginning of the event loop. Should be fixed with the latest commit.

Hi,
Indeed, it works now. Thank you.
Is it possible to "mark" button as "focused" during creation of a dialog?


GetTokenAsync race condition

Bug Report
In some cases the task returned by CrossFirebasePushNotification.Current.GetTokenAsync() never gets resolved. When that happens no exception is thrown nor CrossFirebasePushNotification.Current.OnNotificationError is invoked.
This is caused by the way the GetTokenAsync method is implemented
Expected behavior
await GetTokenAsync() must always return token or null and should invoke OnNotificationError in that case.
Reproduction steps
string token = await CrossFirebasePushNotification.Current.GetTokenAsync();
System.Diagnostics.Debug.WriteLine(CrossFirebasePushNotification.Current.Token);

around the same time of calling FirebasePushNotificationManager.Initialize(). You'll notice the WriteLine method is never called.
Configuration
Version: 3.16
Platform:

Android

Proposed solution
This issue can be resolved by encapsulating the TaskCompletionSource (which is used later by OnComplete) rather than using an unsafe reference which will be replaced every time GetTokenAsync is called (even if the previous task has not been resolved yet.)
Example below:
public async Task<string> GetTokenAsync()
{
    using var tokenTaskHandler = new GmsTaskCompletionHanlder();
    Firebase.Iid.FirebaseInstanceId.Instance.GetInstanceId().AddOnCompleteListener(tokenTaskHandler);

    string retVal = null;

    try
    {
        retVal = await tokenTaskHandler.Task;
    }
    catch (Exception ex)
    {
        _onNotificationError?.Invoke(CrossFirebasePushNotification.Current, new FirebasePushNotificationErrorEventArgs(FirebasePushNotificationErrorType.RegistrationFailed, $"{ex}"));
    }

    return retVal;
}

public class GmsTaskCompletionHanlder : Java.Lang.Object, Android.Gms.Tasks.IOnCompleteListener
{
    private readonly TaskCompletionSource<string> taskCompletionSource = new TaskCompletionSource<string>();
    public Task<string> Task => taskCompletionSource.Task;
    public void OnComplete(Android.Gms.Tasks.Task task)
    {
        try
        {
            if (task.IsSuccessful)
            {
                var token = task.Result.JavaCast<Firebase.Iid.IInstanceIdResult>().Token;
                this.taskCompletionSource?.TrySetResult(token);
            }
            else
            {
                throw task.Exception;
            }
        }
        catch (Exception ex)
        {
            this.taskCompletionSource?.TrySetException(ex);
        }
    }
}

GetTokenAsync has a static taskcompletionsource as field behind. This is a very dangerous design. When multiple calls to GetTokenAsync happen, some taskcompletionsources may wait forever.


Permissions for flat file driver

Would be nice to give the FlatFileDriver instructions on what type of permissions we want the job files to have, for example adding group permissions.

Hey @davidsteinsland
Feel free to open a PR


Add support for coredns on fargate

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Describe the Feature
By default EKS sets coredns to run on ec2. There is an operation required to get it to run on fargate as described here: https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html look for the "(Optional) Update CoreDNS" section.
Use Case
Run entirely serverless
Describe Ideal Solution
Perhaps an enable_coredns_on_fargate flag being set true patches CoreDNS to run on fargate?

Closing as wontfix for the following reasons:

This request is beyond the scope of this module. This module provisions Fargate Profiles and a Fargate Pod Execution Role. It has nothing (directly) to do with CoreDNS or Add-Ons.
The requested operation is no longer required, as the CoreDNS Add-On can be configured directly to run on Fargate. See:

EKS Add-Ons Advanced Configuration

Specifically, you can set
--configuration-values '{"computeType": "Fargate"}'

to get CoreDNS to run on Fargate.


add offer expiry ttl to prevent db polution

Merging this so that we can do QA with all changes in. Relatively small change - only 1 index added to mongo to automatically remove offermetadata

Merging this so that we can do QA with all changes in. Relatively small change - only 1 index added to mongo to automatically remove offermetadata


Support option retention in @bufbuild/protoplugin

Our plugin framework @bufbuild/protoplugin supports access to custom Protobuf options (see the documentation here). Currently, it does not support option retention yet (see the docs here, and the comments in plugin.proto).
We need to update @bufbuild/protoplugin to provide the descriptors that include RETENTION_SOURCE options so that users can access them when generating code. For users who do need the descriptors with stripped options (only RETENTION_RUNTIME), we have to provide alternate means.

Also see https://github.com/bufbuild/protobuf-es/issues/701.

This was implemented in https://github.com/bufbuild/protobuf-es/pull/827 for V2.

This is implemented in version 2.
Generated schemas do not include options with retention = RETENTION_SOURCE.
Schema.files from @bufbuild/protoplugin always includes all options.


Support for Non-Standard/Custom Types

It would be nice to be able to use ZenSharp to create members that reference types outside of the basic types referenced in the readme.  I am not sure how you would do that, however. :)  But, it would be handy, as what I am doing now is using "o" for object, and then having to delete it and enter in my own type... hardly efficient. :/

Did you know about t macro? For example, type pmtSomeName and press tab.

Dude.  I am fail!  That is awesome.  Super awesome extension and I am glad I watched that webinar. :)


BF: removing .only in unit tests

Removing .only in unit tests.

E2E: http://ci.ironmann.io/gh/scality/Integration/9551


How to update wallet-core inside docker image

Describe the bug
When I clone the project and run these steps:
./bootstrap.sh
./tools/generate-files
cmake -H. -Bbuild -DCMAKE_BUILD_TYPE=Debug
make -Cbuild

and after that try to run or build my (golang) project then throws lots of errors like:
/wallet-core/build/libTrustWalletCore.a(Entry.cpp.o): In function `__cxx_global_var_init':
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.5.0/../../../../include/c++/7.5.0/iostream:74: undefined reference to `std::ios_base::Init::Init()'
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.5.0/../../../../include/c++/7.5.0/iostream:74: undefined reference to `std::ios_base::Init::~Init()'
/wallet-core/build/libTrustWalletCore.a(Entry.cpp.o): In function `TW::Cosmos::Address::isValid(TWCoinType, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)':
/wallet-core/src/Cosmos/Address.h:40: undefined reference to `std::allocator<char>::allocator()'
/wallet-core/src/Cosmos/Address.h:40: undefined reference to `std::allocator<char>::~allocator()'

while before pulling the new version of codes, everything was ok.
also, I cloned the code and build it on Mac but now how can I use it in my GoLang project?

Fixed
I just build the project by following the document.
And some methods were deprecated, so I changed them. like:

TWHDWalletGetKeyBIP44 -> TWHDWalletGetDerivedKey
TWHDWalletIsValid -> TWMnemonicIsValid
and also change my cgo import path to my latest wallet-core clone

@apm-dev could you please open a pr to fix go sample code? thanks

@hewigovens Yes sure, I'll do that.


Color Themes

Description
Users like to use things if they can do personalizations. It will help them to embrace the app better since it is based on their personal preference. Maybe we can add color themes, it can be a selection of different accent colors or an addition of dark theme
Thank you
Screenshots
No response
Additional information
No response

Great idea 👍
Is this issue similar to this one https://github.com/EddieHubCommunity/LinkFree/issues/2957

#2957 already has an ongoing discussion on themes. Maybe this can be discussed further there?

similar

Yes

Great idea 👍
Is this issue similar to this one #2957

Thank you. Almost and i found some replies there pertaining to this.

#2957 already has an ongoing discussion on themes. Maybe this can be discussed further there?

Yes, my bad

#2957 already has an ongoing discussion on themes. Maybe this can be discussed further there?

Yes, my bad

No worries, if you have any suggestions you can give them in that issue. You can close this one

#2957 already has an ongoing discussion on themes. Maybe this can be discussed further there?

Yes, my bad

No worries, if you have any suggestions you can give them in that issue. You can close this one

Still new here, thank you for reminding me


generate mpeg from aligned mrc file in FIBSEM pipeline.

https://github.com/niaid/image_portal_workflows/tree/create_fibsem_movie
ready to test - note, reporting Asset type in callback as "AlignMovie", will probably need to modify this.

merged to main. https://github.com/niaid/image_portal_workflows/commit/0d49c4c100a666d8c7e88a6c458c4451a0a78a78


What is nextjs-bzyss249z.vercel.app

Hi, I've come across this action from the depreciated wait for vercel action
I'm looking to use this as wait for vercel doesn't seem to wait for the deployed URL
I'm looking at the documentation and it's not really clear what this section is for:
    steps:
      - name:
          Retrieve deployment URL (example on how to set an ENV var)
        run:
          'echo VERCEL_DEPLOYMENT_URL=nextjs-bzyss249z.vercel.app >>
          $GITHUB_ENV'

Is nextjs-bzyss249z.vercel.app the base URL? So if I'm doing this for Google it'd be google.com??
It's confusing because the url looks like a generated on, like one a build would be on before getting pushed to the production URL say, understand?
What I'm trying to say is it looks like that url is a generated temporary url and I don't know where that would come from
This is from my current workflow and that url is generated by vercel, it looks like you want me to pass in the generated url. defeating the purpose of the workflow

Hi @spences10, yes you're right. The nextjs-bzyss249z.vercel.app is the base url, AKA the domain base url. It could be hello.vercel.app, or google.com.
You can use any domain url, whether it's your production url, or a dynamic one.
If I understand correctly, you were using mskelton/wait-for-vercel-action to resolve the dynamic url assigned to your deployment?
There might be some differences between what UnlyEd/github-action-await-vercel and mskelton/wait-for-vercel-action do that we missed?
Here is how we resolve the dynamic Vercel URL in our workflow, by reading the logs generated when running vercel to deploy. See https://github.com/UnlyEd/next-right-now/blob/v2-mst-aptd-at-lcz-sty/.github/workflows/deploy-vercel-staging.yml#L74
But that's probably not something you'd like to do. Could you explain your workflow and what you expect from the Action?
As a side note, you can see our discussion with mskelton at https://github.com/UnlyEd/github-action-await-vercel/discussions/3, he has no plan on removing the action from GitHub at the moment. (and if his action solves a different problem, it might be worth keeping around)

Hey @Vadorequest, thank for the reply, apologies I should have added my use case
It's for e2e testing with Cypress, the current tool I have used to work great but now it doesn't seem to wait so I'm always re-running the action. I'm guessing this is the case because local e2e tests pass but the action fails then when I run it again manually it passes 🙃
Here's my current workflow, the feedback I have is that I tried this action and it didn't get past the first part:
steps:
  - name: Retrieve deployment URL (example on how to set an ENV var)
    run: "echo VERCEL_DEPLOYMENT_URL=nextjs-bzyss249z.vercel.app >> $GITHUB_ENV"

Even when I change the nextjs-bzyss249z.vercel.app url to mine, I have a vercel secret already on the project I'm using for mskelton/wait-for-vercel-action and that's it, right? I don't need any other secrets set up to run this now it should do the thing, but it's not.
Thanks again 👍

Alright, thanks for the explanation.
So, you run<EMAIL_ADDRESS>and wait for the Vercel deployment to be ready. The action returns the url of the latest Vercel deployment, it might not return the url of the deployment you actually want. While your current setup might seem to work fine, it will "fail" if you push too many commits in a short amount of time, as you'll run E2E tests against the wrong domain. (because it resolves the latest deployment, so it gets confused when there are parallel deployments)
Note that you'll need to change your current CYPRESS_BASE_URL: ${{ steps.wait-for-vercel.outputs.url }} by fromJson(steps.await-vercel.outputs.deploymentDetails).url. You have access to all those proeperties: https://github.com/UnlyEd/github-action-await-vercel/blob/main/src/types/VercelDeployment.ts

I run the example and it just resolves with the URL I gave it, so I'm still not sure how to use this.
Do I add the deployment URL to the .yml file each time? Seems a bit redundant if that's the case

Our action doesn't have a token input.
Actions aren't interchangeable, you can't expect keeping the input of an existing action when switching another one, you need to read their documentation.
  e2e:
    runs-on: ubuntu-latest
    steps:
      - name: Wait for Vercel
        uses<EMAIL_ADDRESS>        id: await-vercel
        env:
          VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
        with:
          deployment-url: YOUR_URL # TODO Replace by the domain you want to test
          timeout: 90 # Wait for 90 seconds before failing
      - name: Checkout
        uses: actions/checkout@v1
      - name: Cypress.io
        uses<EMAIL_ADDRESS>        env:
          CYPRESS_BASE_URL: fromJson(steps.await-vercel.outputs.deploymentDetails).url

But I'm not sure if that'll help with your use case, because our action works slightly differently from wait-for-vercel, and wasn't intended to support your case. In our action, the domain you want to test must be known and provided as input. That's because our action awaits for a particular domain to be deployed, while wait-for-vercel awaits the lastest deployment and therefore doesn't need to know which domain/url to await for.

Documentation has been improved following this discussion.
https://github.com/UnlyEd/github-action-await-vercel/commit/4bdc4929055b6902b388e3ebdea72f3e19d42138


Programming Mambo Power

I am looking for the code to run the mambo at a desired power. 100%, 50%, 25%, etc.
Thanks

fly_direct


⚠ Minecraft has degraded performance

In 214cfbd, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 864 ms

Resolved: Minecraft performance has improved in 24c4d13.


Implement functionality to work with multiple databases

Is your feature request related to a problem? Please describe.
Multiple databases like KEGG and BiGG are referenced and used within refineGEMs but sometimes functions overlap or duplicate and the databases are not updated.
Describe the solution you'd like
Something triggered by the user which leads to a one-time download (the MCC tool does that) which can be reused or updated.
Maybe this can be bundled into a submodule databases.py which takes care of downloading and then parsing as well as formatting so that these databases can be used by a refineGEMs user and within the scripts provided by refineGEMs. (see #31, #28)

As the main aim of this issue, namely downloading and maintaining the different databases used within refineGEMs in one place, is already implemented, this issue can be closed. Furthermore, enhancing refineGEMs through the usage of more databases is already handled or mentioned in more detail in issue #36, and the storage question of these databases is already mentioned in more detail in issue #49. Thus, I will close this issue as completed.


Add pypi installation support and update README.md

TODO:

[x] PyPi installation support and check
[ ] Update REAMDE with installation instructions

See comit f3adf5d and b303a27 fox PyPi installation support and check

[ ] Add badges
[ ] Add automated GitHub cheks and automations (optional)


⚠ ClamAV has degraded performance

In 7ff7d67, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 180 ms

Resolved: ClamAV performance has improved in 6454678.


Node.js update breaks Discordie

Here is what I have of an error log.  This occured after the only code change was an update to node.js.
at IAuthenticatedUser.can (/var/lib/openshift/58990b4d0c1e66658a00015c/app-root/runtime/repo/node_modules/discordie/lib/interfaces/IUser.js:231:26)
    at IAuthenticatedUser.can (/var/lib/openshift/58990b4d0c1e66658a00015c/app-root/runtime/repo/node_modules/discordie/lib/interfaces/IAuthenticatedUser.js:289:32)
    at DiscordieDispatcher.client.Dispatcher.on.e (/var/lib/openshift/58990b4d0c1e66658a00015c/app-root/runtime/repo/start.js:344:20)
    at emitOne (events.js:96:13)
    at DiscordieDispatcher.emit (events.js:189:7)
    at DiscordieDispatcher.emit (/var/lib/openshift/58990b4d0c1e66658a00015c/app-root/runtime/repo/node_modules/discordie/lib/core/DiscordieDispatcher.js:37:16)
    at Discordie.handler (/var/lib/openshift/58990b4d0c1e66658a00015c/app-root/runtime/repo/node_modules/discordie/lib/networking/messages/gateway/message_create.js:12:19)
    at Discordie.processMessage (/var/lib/openshift/58990b4d0c1e66658a00015c/app-root/runtime/repo/node_modules/discordie/lib/core/MessageHandlerCache.js:11:55)
    at MessageHandlerCache.processGatewayMessage (/var/lib/openshift/58990b4d0c1e66658a00015c/app-root/runtime/repo/node_modules/discordie/lib/core/MessageHandlerCache.js:53:27)
    at DiscordieDispatcher.Dispatcher.on.e (/var/lib/openshift/58990b4d0c1e66658a00015c/app-root/runtime/repo/node_modules/discordie/lib/index.js:82:19)

Have you tried to install Node.JS 6?

After doing some restarts, the bot is not crashing so perhaps this is some other bug that happened to be triggered during an update.


Line+Stat shows 0

The dashboard example ends up displaying zero as the single stat for Latency and Packet Loss, regardless of the actual last value
I think it might be because of the FILL(null) at the end of the query, as per https://github.com/influxdata/chronograf/issues/1493
Changing it to FILL(none) seems to work for me

Thank you for bringing this to my attention. Do you have screenshots on how these settings differ in the output provided on the dahsboard?

Sure - here's my latest
The packet loss shows 0, I think because that was the most recent value (see highlighted value at the bottom)

Ah. Very well. I see what you mean. I'll draft a PR for it and see to get it changed in the repo by the end of this week 👍

Thanks - and thanks for a great project

Thank you. Feel free to look through the PR and leave a comment if you think something is missing, otherwise I will go ahead an merge it. Closing this issue now


[Proposal] Create a new way to save metadata for all instruments

Hello, i would like to propose a new implementation on the way that we save the currencyPair metadata of instruments.
Right now every instrument has its own Map in which we add the metadata. I think this implementation has the following issues:
It is not possible to search for a specific Metadata on any instrument with just 1 search of a Map, you need to always check the type of the instrument and search on the specific Map. Also, because the DerivateMetadata and CurrencypairMetadata classes do not implement the same class, it is also difficult to make a generic function which searches for the type of instrument, searches to the correct Map and return the correct Metadata.
I propose to create a new interface named InstrumentMetadata which both CurrencyPairMetadata and DerivateMetadata classes will implement and create 1 Map for all instruments, instead of having 3 maps (currencyPair, futures, options).The Map will be of type Map<Instrument, InstrumentMetaData>. If you are ok with this i can implement it asap. I am waiting for your response/feedback. Thank you

Sounds good. Please just make sure to refactor all legacy pas to the new API rather than having a new and a legacy impl.

Great i will start asap. Thanks

Merged


Update Reason
PCF aspect model needs to be adapted in order to ensure compliance with PCF Rulebook V2 and WBCSD/ PACT data model V2.
MS1 Criteria

[ ] The model that should be updated exists
[ ] The referenced use case exists
[ ] The potential updates are discussed with all stakeholders
[ ] The potential update will be either

[ ] backward compatible or
[ ] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

Adaptation of the PCF data model will cover new and updated properties.

Backward compatibility is not necessarily required as the current version of the PCF data model is not used productively yet. However, in compliance with the evolution of the underlying data model from WBCSD/ PACT, we aim for the highest possible level of backward compatibility.

Please check you constraints connection, as they seem to be "wrong" (cli says "ok", but the trait doesn't work with this connection).


Restrict Excessive Diagnostic Printout From test-EXAMPLE-single_cycle

The title says it all.
The excessive printout severely affects execution time of the baseline test program.
There are many lines of diagnostic printed for each cycle.  Perhaps provide a command-line argument affecting verbosity?
The culprit is likely source/TEST/EXAMPLE/single_cycle.h
Tests:

Successful build of test-EXAMPLE-single_cycle.
Limited printout from execution.
Successful execution test-EXAMPLE-single_cycle (all tests pass).

Tested source code changes under Linux.
Test passed successfully with no options.
Test passed successfully with option "-v".

Issue#7 Restrict Excessive Diagnostic Printout From test-EXAMPLE-single_cycle
Work completed  in Linux and Windows as follows:

Successful build of test-EXAMPLE-single_cycle.
Limited printout from execution. ("-v " = full debug and blank = limited)
Successful execution test-EXAMPLE-single_cycle (all tests pass for "do_test_evil").

Merged into branch release-2.0.0.


As a user, I would like to use NPSP Data Importer in a "dry run" mode where it shows which records will be matched vs created, as well as any errors it can already detect, but it wouldn't actually save any changes to the databse (other than the di records).

request from Jon Fine and seconded by Judi Sohn.  hub thread: https://powerofus.force.com/0D58000001aznuJ

**lurch: attach W-007273

**lurch: attach W-007273

Idea here: https://powerofus.force.com/hub-ideas/1023

**lurch: attach W-007273


WIP. Speedup "symbolizeAddress" function

For changelog. Remove if this is non-significant change.
Category (leave one):

Performance Improvement

Short description (up to few sentences):
Better performance of reports on addresses from query profiler.

TODO: open correct file when debugging information is placed separate (in /usr/lib/debug).

Now query profiling looks like this: https://gist.github.com/alexey-milovidov/92758583dd41c24c360fdb8d6a4da194


Error:RuntimeError: cuda runtime error (11)

Hello, I am Chen Longwhen.When I train the model, I get an error.The error like this.
RuntimeError: cuda runtime error (11) : invalid argument at /pytorch/aten/src/THC/THCGeneral.cpp:383
My experiment is:
Pytorch 1.1.0
torchvision 0.3.0

Thanks a lot!

Hi, @TCChenlong, the error information are too short to check. Could you post more logging information about that?

Thanks，I have solved this problem by install torch=1.0.0。
Thanks a lot!

OK, good feedback.


WIP: Add Grpc Interceptor and integration test

Note this depends on the gRPC Interceptor implementation currently in grpc/grpc master. We cannot release this until the grpc release that includes interceptors.
#120

Currently failing due to https://github.com/grpc/grpc/issues/15387

Any update on this?


Bug fixes for Issues filters

Fixes two bugs in the GET :username/:reponame/issues endpoint:

Previously, if there were filters for both assignee and poster (e.g. type="created", assignee=4), the counts (ctx.Data["IssueStats"]) would reflect both filters, but the returned issues (ctx.Data["Issues"]) would only apply the assignee filter.
Previously, if there were two conflicting assignee filters (e.g. type="assigned", assignee=4, and ctx.User.ID=5), only one of the filters would be applied. Now both filters are applied, and 0 issues are returned.

I also took the opportunity to make the IssuesOptions struct less confusing. Previously, there was a misleadingly-named UserID field that only was used for filtering mentioned users, and only if IsMention was set to true. I renamed UserID to MentionedID (which like AssigneeID and ReportedID is ignored if 0), and got rid of IsMention.

For first bug, currently you cannot chose both poster and assignee.
I have tested it simple and it works well. But I think this need more tests, so let's put it on v1.1.

@lunny You can select both an assignee and reporter. From the Issues pages, you can select an assignee under the Assignee dropdown, and select yourself as a reporter under the Type dropdown.

LGTM

LGTM


Unit test errors during release:perform

I tried to release version 1.41 of maven tools. release:prepare ran successfully but unfortunately I got unit test errors for build-scrips during release:perform. Not sure why because the test have been run successfully during release:prepare... Probably something different in the environment of release:perform. Any hint appreciated... I'll probably not be able to work on this before middle of the afternoon...
    [INFO] ------------------------------------------------------------------------
    [INFO] Building build-scripts 1.41
    [INFO] ------------------------------------------------------------------------
    [INFO]
    [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven) @ build-scripts ---
    [INFO]
    [INFO] --- exec-maven-plugin:1.2:exec (prove) @ build-scripts ---
    src/test/perl/component.t ................... ok
    src/test/perl/object-gather_pan.t ........... ok
    src/test/perl/object-new.t .................. ok
    src/test/perl/panc.t ........................ ok
    src/test/perl/pod-syntax.t .................. ok
    # Unable to compile profile profilecache_broken.pan. Minimal panc version is 10.2. Pan compiler called with: panc --formats json --output-dir /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/test/profiles --include-path .:/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan:/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/9vhg9o973e profilecache_broken.pan from directory /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources with output
    # parse error [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/profilecache_broken.pan:1.1-1.1]
    #
    # Encountered: Woohoo
    # Was expecting one of:
    #     "unique" ...
    #     "object" ...
    #     "template" ...
    #     "structure" ...
    #     "declaration" ...
    #
    #
    src/test/perl/profilecache.t ................ ok
    # ERROR: no more guesses for template-library-core path: tlc
    # INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)
    src/test/perl/quattor.t ..................... ok
    src/test/perl/quattor_mock.t ................ ok
    src/test/perl/regexptest-flags.t ............ ok
    src/test/perl/regexptest-tests.t ............ ok
    src/test/perl/regexptest.t .................. ok
    # ERROR: no more guesses for template-library-core path: tlc
    # ERROR: No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)

    #   Failed test 'No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)'
    #   at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Object.pm line 143.
    Use of uninitialized value $dirs[1] in join or string at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Panc.pm line 99.
    # ERROR: no more guesses for template-library-core path: tlc
    # INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)
    # INFO BEGIN test for Base test
    # INFO END test for Base test
    # Looks like you failed 1 test of 44.
    src/test/perl/textrender-component.t ........
    Dubious, test returned 1 (wstat 256, 0x100)
    Failed 1/44 subtests
    src/test/perl/textrender-gather_pan.t ....... ok
    src/test/perl/textrender-gather_tt.t ........ ok
    # INFO TT gather and verification test disabled
    # ERROR: no more guesses for template-library-core path: tlc
    # ERROR: No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)

    #   Failed test 'No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)'
    #   at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Object.pm line 143.
    Use of uninitialized value $dirs[1] in join or string at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Panc.pm line 99.
    # ERROR: no more guesses for template-library-core path: tlc
    # INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)
    Unable to compile profile /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/nottservice/tests/profiles/config.pan. Minimal panc version is 10.2. Pan compiler called with: panc --formats json --output-dir /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/test/profiles --include-path /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan:/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/nottservice/tests/profiles:. /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/nottservice/tests/profiles/config.pan from directory /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/nottservice/tests/profiles with output
    evaluation error [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan/metaconfig/nottservice/schema.pan:3.1-3.20]
    cannot locate template named 'pan/types'
    >>> call stack trace
    >>> [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan/metaconfig/nottservice/schema.pan:3.1-3.20]
    >>> [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan/metaconfig/nottservice/config.pan:3.1-3.40]
    >>> [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/nottservice/tests/profiles/config.pan:3.1-3.40]
    >>> ====================

     at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/ProfileCache.pm line 208
    # Tests were run but no plan was declared and done_testing() was not seen.
    src/test/perl/textrender-metaconfig-nott.t ..
    Dubious, test returned 1 (wstat 256, 0x100)
    Failed 1/26 subtests
    # ERROR: no more guesses for template-library-core path: tlc
    # ERROR: No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)

    #   Failed test 'No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)'
    #   at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Object.pm line 143.
    Use of uninitialized value $dirs[1] in join or string at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Panc.pm line 99.
    # ERROR: no more guesses for template-library-core path: tlc
    # INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)
    # INFO BEGIN test for Nopan
    # INFO END test for Nopan
    # ERROR: no more guesses for template-library-core path: tlc
    # INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)
    Unable to compile profile /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles/simple.pan. Minimal panc version is 10.2. Pan compiler called with: panc --formats json --output-dir /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/test/profiles --include-path /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan:/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles:. /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles/simple.pan from directory /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles with output
    evaluation error [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan/metaconfig/testservice/schema.pan:3.1-3.20]
    cannot locate template named 'pan/types'
    >>> call stack trace
    >>> [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan/metaconfig/testservice/schema.pan:3.1-3.20]
    >>> [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan/metaconfig/testservice/config.pan:3.1-3.40]
    >>> [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles/simple.pan:3.1-3.40]
    >>> ====================

     at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/ProfileCache.pm line 208
    # Tests were run but no plan was declared and done_testing() was not seen.
    src/test/perl/textrender-metaconfig.t .......
    Dubious, test returned 1 (wstat 256, 0x100)
    Failed 1/42 subtests
    # ERROR: no more guesses for template-library-core path: tlc
    # INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)
    src/test/perl/textrender-regexptest.t ....... ok
    # Start actual Suite tests v2.0
    # ERROR: no more guesses for template-library-core path: tlc
    # ERROR: No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)

    #   Failed test 'No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)'
    #   at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Object.pm line 143.
    Use of uninitialized value $dirs[1] in join or string at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Panc.pm line 99.
    # ERROR: no more guesses for template-library-core path: tlc
    # INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)
    # INFO BEGIN test for Ordered test v2.0
    # INFO END test for Ordered test v2.0
    # Looks like you failed 1 test of 65.
    src/test/perl/textrender-suite-2.0.t ........
    Dubious, test returned 1 (wstat 256, 0x100)
    Failed 1/65 subtests
    # Start actual Suite tests
    # ERROR: no more guesses for template-library-core path: tlc
    # ERROR: No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)

    #   Failed test 'No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)'
    #   at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Object.pm line 143.
    Use of uninitialized value $dirs[1] in join or string at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/Panc.pm line 99.
    # ERROR: no more guesses for template-library-core path: tlc
    # INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)
    # INFO BEGIN test for Nopan
    # INFO END test for Nopan
    # ERROR: no more guesses for template-library-core path: tlc
    # INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)
    Unable to compile profile /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles/simple.pan. Minimal panc version is 10.2. Pan compiler called with: panc --formats json --output-dir /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/test/profiles --include-path /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/textrender/namespace/2UjKCZbVWh:/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles:.:/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/pan /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles/simple.pan from directory /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles with output
    evaluation error [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/textrender/namespace/2UjKCZbVWh/metaconfig/testservice/schema.pan:3.1-3.20]
    cannot locate template named 'pan/types'
    >>> call stack trace
    >>> [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/textrender/namespace/2UjKCZbVWh/metaconfig/testservice/schema.pan:3.1-3.20]
    >>> [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/target/textrender/namespace/2UjKCZbVWh/metaconfig/testservice/config.pan:3.1-3.40]
    >>> [/exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/test/resources/metaconfig/testservice/1.0/tests/profiles/simple.pan:3.1-3.40]
    >>> ====================

     at /exp/si/jouvin/GitRepositories/Quattor/maven-tools/target/checkout/build-scripts/src/main/perl/Test/Quattor/ProfileCache.pm line 208
    # Tests were run but no plan was declared and done_testing() was not seen.
    src/test/perl/textrender-suite.t ............
    Dubious, test returned 1 (wstat 256, 0x100)
    Failed 1/41 subtests

    Test Summary Report
    -------------------
    src/test/perl/textrender-component.t      (Wstat: 256 Tests: 44 Failed: 1)
      Failed test:  19
      Non-zero exit status: 1
    src/test/perl/textrender-metaconfig-nott.t (Wstat: 256 Tests: 26 Failed: 1)
      Failed test:  15
      Non-zero exit status: 1
      Parse errors: No plan found in TAP output
    src/test/perl/textrender-metaconfig.t     (Wstat: 256 Tests: 42 Failed: 1)
      Failed test:  17
      Non-zero exit status: 1
      Parse errors: No plan found in TAP output
    src/test/perl/textrender-suite-2.0.t      (Wstat: 256 Tests: 65 Failed: 1)
      Failed test:  14
      Non-zero exit status: 1
    src/test/perl/textrender-suite.t          (Wstat: 256 Tests: 41 Failed: 1)
      Failed test:  14
      Non-zero exit status: 1
      Parse errors: No plan found in TAP output
    Files=19, Tests=385, 36 wallclock secs ( 0.16 usr  0.05 sys + 58.52 cusr  2.80 csys = 61.53 CPU)
    Result: FAIL
    [INFO] ------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO]
    [INFO] quattor maven build tools ......................... SUCCESS [1:31.282s]
    [INFO] assemblies ........................................ SUCCESS [10.824s]
    [INFO] build-scripts ..................................... FAILURE [36.245s]
    [INFO] build-profile ..................................... SKIPPED
    [INFO] quattor cfg. module archetype ..................... SKIPPED
    [INFO] quattor build maven plugin ........................ SKIPPED
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 2:20.059s
    [INFO] Finished at: Fri Mar 13 08:28:03 CET 2015
    [INFO] Final Memory: 20M/430M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2:exec (prove) on project build-scripts: Command execution failed. Process exited with an error: 1(Exit value: 1) -> [Help 1]
    [ERROR]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR]
    [ERROR] For more information about the errors and possible solutions, please read the following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
    [ERROR]
    [ERROR] After correcting the problems, you can resume the build with the command
    [ERROR]   mvn <goals> -rf :build-scripts
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] quattor maven build tools ......................... FAILURE [2:26.908s]
[INFO] assemblies ........................................ SKIPPED
[INFO] build-scripts ..................................... SKIPPED
[INFO] build-profile ..................................... SKIPPED
[INFO] quattor cfg. module archetype ..................... SKIPPED
[INFO] quattor build maven plugin ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:29.128s
[INFO] Finished at: Fri Mar 13 08:28:04 CET 2015
[INFO] Final Memory: 12M/304M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:perform (default-cli) on project maven: Maven execution failed, exit code: '1' -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

@jouvin i thought the message was clear enough?
# ERROR: no more guesses for template-library-core path: tlc
# INFO No template-library-core path found (set QUATTOR_TEST_TEMPLATE_LIBRARY_CORE?)

What should I have done that was not necessary in the previous step?

@jouvin if the variable is not set, it searches for a number of default locations based on working directory. maybe the working dir is different?

@jouvin @jrha had the same issue, see e.g. https://github.com/quattor/release/issues/76

I'll check after my meeting. Certainly worth an addition in the doc!

I certainly have no issues using the updated env.sh generated by build_all_repos.sh.
@jouvin are you happy now?

Yes, sorry I forgot to update the issue. I added the documentation about the need to define this variable in BUILD_INFO (https://github.com/quattor/maven-tools/pull/46`.

Cool, thanks.


CupertinoTextFeild should support handle order swapping like Native iOS

CupertinoTextFeild:
https://user-images.githubusercontent.com/30322203/186804383-0c05d340-ceed-4cc1-8a1d-d9df6882b6fd.mov
Native iOS UITextField:
https://user-images.githubusercontent.com/30322203/186804649-7e8cf3c9-80f8-49e9-b8af-316fbd787b96.mov
can reproduce in any cupertino text field

cc @justinmc

Confirmed that native iOS does allow handle order swapping (iPad iOS 15).


Add support for OpenBSD

A few tweaks were necessary to support OpenBSD:

there is no distinction between client and server package,
it's just a single package. For that reason, a check is added
around client and server package definition, checking if it
might already be defined. Therefore added server_package and
client_package parameters, defaulting to what was there hard-coded.
SPECS still seems to work.

The ruby interpreter is /usr/local/bin/ruby21, named after
the ruby version it's used to run. I made the interpreter configurable
instead of hardcoding another one in.
Therefore added a ruby_interpreter parameter, that defaults to
what was there hardcoded.
SPEC tests added for the interpreter.

I use Hiera, to define all the gory parameters, with that there
was trouble, getting the boolean value of middleware_ssl from there
into the module, so had to add a check around it in the
activemq/hosts_iteration.pp and rabbitmq/hosts_iteration.pp
This is also the reason why I had to bump minimal required stdlib
version from 3.2.0 to 4.2.0

README.md updated to reflect the new parameters

Actually, I think it's unfortunate that you squashed all your changes.

Since two of them were dangling around here for quite a while, I had to catch up with the changes upstream. That's why I ended up now this way ;)
Anyways, it shouldn't be too hard to get them into separate commits, let me see what I can do.

Cool. No need to close the PR, you can just force-push to your branch.


Is LSTM policy in PPO2 working correctly?

I tried on LSTM policy of PPO2 (with default hyper-parameter) in PongNoFrameSkipv4 environment but, it failed to improve the reward. It stuck near the minimum reward -21. I also tried on different nsteps value (4 and 1024) but it failed to.
However, when I  tried on CNN policy of PPO2 (also with default hyper-parameter), it succeeded to converge to the maximum reward of 21.
Is LSTM policy in PPO2 working correctly?

worked perfect for me, on a different task. you can try to adjust network architecture to the task you're trying to solve. try changing the conv layers size rather than just changing the nsteps parameter.

@Guiadan Thanks! I will try it out.

I tried on CNNPolicy in SonicTheHedgehog-Genesis and it works perfectly but when I tried to run LstmPolicy I got the following error:

Traceback (most recent call last):
  File "/Users/david.suarez/Work/i+d/sonic-rl/.venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1567, in _create_c_op
    c_op = c_api.TF_FinishOperation(op_desc)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot reshape a tensor with 262144 elements to shape [0,4096,?] (0 elements) for 'model_1/Reshape_1' (op: 'Reshape') with input shapes: [512,512], [3] and with input tensors computed as partial shapes: input[1] = [0,4096,?].

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/david.suarez/Work/i+d/sonic-rl/ppo/ppo_agent.py", line 41, in <module>
    main()
  File "/Users/david.suarez/Work/i+d/sonic-rl/ppo/ppo_agent.py", line 36, in main
    total_timesteps=int(1e7)
  File "/Users/david.suarez/Work/i+d/sonic-rl/baselines/baselines/ppo2/ppo2.py", line 175, in learn
    model = make_model()
  File "/Users/david.suarez/Work/i+d/sonic-rl/baselines/baselines/ppo2/ppo2.py", line 170, in <lambda>
    max_grad_norm=max_grad_norm)
  File "/Users/david.suarez/Work/i+d/sonic-rl/baselines/baselines/ppo2/ppo2.py", line 18, in __init__
    train_model = policy(sess, ob_space, ac_space, nbatch_train, nsteps, reuse=True)
  File "/Users/david.suarez/Work/i+d/sonic-rl/baselines/baselines/ppo2/policies.py", line 65, in __init__
    xs = batch_to_seq(h, nenv, nsteps)
  File "/Users/david.suarez/Work/i+d/sonic-rl/baselines/baselines/a2c/utils.py", line 74, in batch_to_seq
    h = tf.reshape(h, [nbatch, nsteps, -1])
  File "/Users/david.suarez/Work/i+d/sonic-rl/.venv/lib/python3.6/site-packages/tensorflow/python/ops/gen_array_ops.py", line 6113, in reshape
    "Reshape", tensor=tensor, shape=shape, name=name)
  File "/Users/david.suarez/Work/i+d/sonic-rl/.venv/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
    op_def=op_def)
  File "/Users/david.suarez/Work/i+d/sonic-rl/.venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3392, in create_op
    op_def=op_def)
  File "/Users/david.suarez/Work/i+d/sonic-rl/.venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1734, in __init__
    control_input_ops)
  File "/Users/david.suarez/Work/i+d/sonic-rl/.venv/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1570, in _create_c_op
    raise ValueError(str(e))
ValueError: Cannot reshape a tensor with 262144 elements to shape [0,4096,?] (0 elements) for 'model_1/Reshape_1' (op: 'Reshape') with input shapes: [512,512], [3] and with input tensors computed as partial shapes: input[1] = [0,4096,?].

Here is my main code:

import tensorflow as tf

from baselines.common.vec_env.dummy_vec_env import DummyVecEnv
import baselines.ppo2.ppo2 as ppo2
import baselines.ppo2.policies as policies

from sonic_util import make_env

def main():
    """Run PPO until the environment throws an exception."""
    config = tf.ConfigProto()
    config.gpu_options.allow_growth = True # pylint: disable=E1101
    with tf.Session(config=config):
        # Take more timesteps than we need to be sure that
        # we stop due to an exception.

        env = DummyVecEnv([make_env])

        ppo2.learn(policy=policies.LstmPolicy,
                   env=env,
                   nsteps=4096,
                   nminibatches=8,
                   lam=0.95,
                   gamma=0.99,
                   noptepochs=3,
                   log_interval=1,
                   ent_coef=0.01,
                   lr=lambda _: 2e-4,
                   cliprange=lambda _: 0.1,
                   total_timesteps=int(1e7)
                   )

if __name__ == '__main__':

    main()


Events vague

The events section is rather vague, and doesn't contain any links to more information. For example, the EventHandler type itself is never described, the ?. operator isn't explained in this series at all IIRC, and the EventArgs type isn't described. If nothing else, a link to more information would be handy.

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

ID: 8181f41d-b6ce-ad66-084e-8d2b514b87e2
Version Independent ID: 494c4344-b752-4f86-5b66-1ef4b81c1e75
Content: Classes and Objects in C# - A tour of the C# Language
Content Source: docs/csharp/tour-of-csharp/classes-and-objects.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thank you for opening this issue.
I'll assign this to @BillWagner as he's been revamping the C# language area. I'm not sure what he's going to do with the "Tour of C#" stuff, but a lot of it is duplicate information.
If this article stays around, it should definitely have links to more info under each concept section.


fix: Remove expectations from tree hash test

Issue #
https://github.com/awslabs/aws-sdk-swift/issues/1005
Description of changes
Removes expectations from this test, since they cannot be reliably used on asynchronous tests on Linux.  This particular test does not seem to be causing any problems, but I am nevertheless fixing it because it can potentially cause deadlock.
This code executes in deterministic order, so the callback is guaranteed to have been run before the test ends, but I have also used a completed flag to verify that the test assertions were actually run.
New/existing dependencies impact assessment, if applicable

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

/test


Remove unwanted Github action workflows

What do we use to publish now? Is it always manual?
Not sure what the reason is to remove these.

I think the publish happens here now:
https://github.com/microsoft/vscode-jupyter/blob/5c2cf0c4cb56d16a5f2124a7e5a72ce72b9266b1/.github/workflows/build-test.yml#L1095-L1170


Submitting studio-cli version 24.11.0

Checklist for Pull Requests

[X] Have you signed the Contributor License Agreement?
[X] Is there a linked Issue?

Manifests

[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

@microsoft-github-policy-service agree company="WindRiver"


Firebase zip contents from FirebaseManifest instead of textproto

Built zip candidate for 7.0.0 and reviewed diffs with previous zips.
#no-changelog

Thanks for the review and suggestions!
I'll merge it here to sync with the first M82 zip candidate and address the improvements in the next PR.