api-server-rest gave up after five tries to connect to CDH

Even though there no retry limit set in the service file, the service gives up after five tries:
# systemctl cat  api-server-rest.service
# /etc/systemd/system/api-server-rest.service
[Unit]
Description=CDH API Server Rest Service
<EMAIL_ADDRESS>After=network.target kata-agent.service<EMAIL_ADDRESS>
[Service]
Type=simple
NetworkNamespacePath=/run/netns/podns
ExecStart=/usr/local/bin/api-server-rest --features all
RestartSec=1
Restart=always

[Install]
WantedBy=multi-user.target

Failure log:
# journalctl -u api-server-rest.service
Feb 07 22:52:43 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Started CDH API Server Rest Service.
Feb 07 22:52:44 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[925]: Starting API server on <IP_ADDRESS>:8006 with features all
Feb 07 22:52:44 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[925]: Error: ttrpc connect to CDH addr: unix:///run/confidential-containers/cdh.sock failed!
Feb 07 22:52:44 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[925]: Caused by:
Feb 07 22:52:44 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[925]:     0: Nix error: ENOENT: No such file or directory
Feb 07 22:52:44 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[925]:     1: ENOENT: No such file or directory
Feb 07 22:52:44 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 22:52:44 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Failed with result 'exit-code'.
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Scheduled restart job, restart counter is at 1.
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Stopped CDH API Server Rest Service.
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Started CDH API Server Rest Service.
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[965]: Starting API server on <IP_ADDRESS>:8006 with features all
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[965]: Error: ttrpc connect to CDH addr: unix:///run/confidential-containers/cdh.sock failed!
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[965]: Caused by:
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[965]:     0: Nix error: ENOENT: No such file or directory
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[965]:     1: ENOENT: No such file or directory
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 22:52:45 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Failed with result 'exit-code'.
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Scheduled restart job, restart counter is at 2.
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Stopped CDH API Server Rest Service.
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Started CDH API Server Rest Service.
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1022]: Starting API server on <IP_ADDRESS>:8006 with features all
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1022]: Error: ttrpc connect to CDH addr: unix:///run/confidential-containers/cdh.sock failed!
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1022]: Caused by:
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1022]:     0: Nix error: ENOENT: No such file or directory
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1022]:     1: ENOENT: No such file or directory
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 22:52:47 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Failed with result 'exit-code'.
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Scheduled restart job, restart counter is at 3.
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Stopped CDH API Server Rest Service.
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Started CDH API Server Rest Service.
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1026]: Starting API server on <IP_ADDRESS>:8006 with features all
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1026]: Error: ttrpc connect to CDH addr: unix:///run/confidential-containers/cdh.sock failed!
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1026]: Caused by:
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1026]:     0: Nix error: ENOENT: No such file or directory
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1026]:     1: ENOENT: No such file or directory
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 22:52:48 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Failed with result 'exit-code'.
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Scheduled restart job, restart counter is at 4.
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Stopped CDH API Server Rest Service.
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Started CDH API Server Rest Service.
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1032]: Starting API server on <IP_ADDRESS>:8006 with features all
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1032]: Error: ttrpc connect to CDH addr: unix:///run/confidential-containers/cdh.sock failed!
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1032]: Caused by:
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1032]:     0: Nix error: ENOENT: No such file or directory
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 api-server-rest[1032]:     1: ENOENT: No such file or directory
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 22:52:49 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Failed with result 'exit-code'.
Feb 07 22:52:50 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Scheduled restart job, restart counter is at 5.
Feb 07 22:52:50 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Stopped CDH API Server Rest Service.
Feb 07 22:52:50 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Start request repeated too quickly.
Feb 07 22:52:50 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: api-server-rest.service: Failed with result 'exit-code'.
Feb 07 22:52:50 podvm-nginx-587b496d6c-nqw6s-347fd878 systemd[1]: Failed to start CDH API Server Rest Service.

I think that's desired behaviour, no? systemd will give up eventually if a service doesn't come up to not thrash the system.

How do we then give the CDH some more time? Or can we say that only start when the domain socket is available?

yeah, it would be nice to use those but even the mkosi builds don't have v254 yet:

The kata-agent unit reports success immediately after launch (10:15:11), but until CDH listens on a socket some time will pass (10:15:17).
sudo systemctl status kata-agent | grep Active
     Active: active (running) since Mon 2024-03-18 10:15:11 UTC; 47min ago

sudo journalctl -u kata-agent | grep cdh.sock
Mar 18 10:15:16 podvm-nginx-caa-84f67fc7d6-kjp24-a94e6691 kata-agent[915]: {"msg":"waiting for /run/confidential-containers/cdh.sock to exist (attempts=1)","level":"INFO","ts":"2024-03-18T10:15:16.551438634Z","pid":"915","subsystem":"root","version":"0.1.0","source":"agent","name":"kata-agent"}
Mar 18 10:15:17 podvm-nginx-caa-84f67fc7d6-kjp24-a94e6691 kata-agent[1019]: [2024-03-18T10:15:17Z INFO  confidential_data_hub] Confidential Data Hub starts to listen to request: unix:///run/confidential-containers/cdh.sock

meanwhile api-server-rest, depending on kata-agent will start and give up before cdh.sock is up:
sudo journalctl -u api-server-rest | grep Started
Mar 18 10:15:11 podvm-nginx-caa-84f67fc7d6-kjp24-a94e6691 systemd[1]: Started CDH API Server Rest Service.
Mar 18 10:15:12 podvm-nginx-caa-84f67fc7d6-kjp24-a94e6691 systemd[1]: Started CDH API Server Rest Service.
Mar 18 10:15:13 podvm-nginx-caa-84f67fc7d6-kjp24-a94e6691 systemd[1]: Started CDH API Server Rest Service.
Mar 18 10:15:14 podvm-nginx-caa-84f67fc7d6-kjp24-a94e6691 systemd[1]: Started CDH API Server Rest Service.
Mar 18 10:15:16 podvm-nginx-caa-84f67fc7d6-kjp24-a94e6691 systemd[1]: Started CDH API Server Rest Service.

so, we can assume the unit needs ~5s to finish CDH initialization


[BUG] interferes with other Twitter addons?

Info (please complete the following information):

Browser Firefox
Platform Windows 10
Extension Version 1.5
Location UK
Twitter English

What happened
Steps to reproduce the behavior:
Have https://addons.mozilla.org/en-GB/firefox/addon/tweak-new-twitter/ installed and options not work right. Disabling Eight Dollars fixes it.
Expected behavior
I expect these 2 addons to work together.

This would be challenging to do - Twitter Web App doesn't expose an extensible API we can hook into to add our modifications, so we have to resort to hacks with the DOM mutations. Those are not very composable on top of other code that may do the same.
We would have to do a proper integration with Tweak New Twitter extension or come up with some sort of set of extensibility standards that is followed across all extensions (not just ours) that modify Twitter to make all extensions work well together.
@privacyguy123 please share your thoughts also on what's the best way forward you think might be here. As of moment, I am leaning on the side of closing this as WONTFIX.
Cheers.


feat[test_utils]: new macro for unit testing with no boilerplate.

Introduce an optional macro with name "context_generator" that allows unit-testing to be smaller, easier to learn and faster to implement. Details in documentation.

I'm really not convinced this is a better direction. Using the builder pattern is better in most cases because users don't have to read the macro to understand which syntax is available. I don't believe this way is any more succinct for developers, either, so I'm having a hard time rationalizing adding this macro to the API.
@ChaoticTempest @itegulov wdyt?

When we search for testing_env! macro in the documentation, this is what we get 'https://docs.rs/near-sdk/latest/near_sdk/macro.testing_env.html'. I understand the concern, but when users have to call the builder and build for every single test, we end up with boilerplate that takes 4 to 5 lines and actual test implementation that takes 1 to 3 lines. In other words, code gets harder to read and slower to implement.
Why not have both options available? A high level option for users that only want to write code fast, and a low level option for users that want to be more specific with their tests.

This macro already creates a linter warning when there's an odd number of arguments. What if I implemented the macro in a way that it also warns what types of arguments it accepts?  Something like 'Invalid arg for method_name. Accepted args can be: "current_account_id", "signer_account_id", "signer_account_pk", "predecessor_account_id", "block_index" or "block_height", "block_timestamp", "epoch_height", "account_balance", "account_locked_balance", "storage_usage", "attached_deposit", "prepaid_gas", "random_seed" and "is_view".' .

Instead of a macro, maybe it would be better to just have a snippet then. Thanks for reviewing.

I understand the concern, but when users have to call the builder and build for every single test, we end up with boilerplate that takes 4 to 5 lines and actual test implementation that takes 1 to 3 lines.

You don't actually need the boilerplate

Why not have both options available? A high level option for users that only want to write code fast, and a low level option for users that want to be more specific with their tests.

Because more surface area on the API makes it harder to maintain and improve in the future.

Instead of a macro, maybe it would be better to just have a snippet then. Thanks for reviewing.

Will look into better docs/examples or maybe the current API can be improved in a backwards compatible way :)


pointer-events style ignored on Android

Description
Hi,
I would like to have a lottie view which covers the entire screen and allow touches underneath. To allow touches underneath, I would pass pointer-events: none which works nicely on iOS, but not on Android.

Sample code, also available in linked repo:
import LottieView from 'lottie-react-native';
import {Alert, Button, SafeAreaView, StyleSheet, View} from 'react-native';

function App() {
  return (
    <SafeAreaView style={styles.screen}>
      <Button title="Press Me" onPress={() => Alert.alert('Hey!')} />
      <LottieView
        style={styles.lottie}
        source={require('./assets/Animation -<PHONE_NUMBER>569.json')}
        autoPlay
        loop
      />
    </SafeAreaView>
  );
}

const styles = StyleSheet.create({
  screen: {
    flex: 1,
    backgroundColor: '#fff',
  },
  lottie: {
    ...StyleSheet.absoluteFillObject,
    pointerEvents: 'none',
  },
});

export default App;

Note that the workaround is easy and that is to wrap the lottie view in another view and set the pointer events there to none which is what I do for now, but I would like the lottie view to work on its own too
Steps to reproduce

Clone repo
Run on Android
Try clicking on the button behind the lottie view

Snack or a link to a repository
https://github.com/itsramiel/AndroidLottie
Lottie React Native version
7.0.0
React Native version
0.75.4
Platforms
Android
Workflow
React Native
Architecture
Paper (Old Architecture)
Build type
Debug app & dev bundle
Device
Android emulator
Acknowledgements
Yes

Yes, same for us. Had to use a wrapping View.

I am gonna investigate it this weekend.

I am gonna investigate it this weekend.

Hi, any news?

I'm having the same issue but wrapping in a view didn't fix, any ideas?


fix(buffer): use safe-buffer polyfill to maintain compatibility

Hi,
The fix of NODE-1461 ( commit 7c71e199190a53017b921e88200cdba3889ca23c) break compatibility with node.js < 4.5 and node.js < 5.9 and  and start to affect downstream packages like Automattic/mongoose#6884
This pull request uses safe-buffer to polyfill and it is suggested by official node.js
The polyfill won't change any existing behavior and will call native method directly if it is supported.

Hi @Fonger, thanks for this. We are indeed deprecating node v4 in the upcoming months, but in the meantime should in fact be using this. Thanks for the contribution!


[Bug] We can't define a $schema on the Model

Bug report
Background: In https://github.com/Laravel-Backpack/CRUD/pull/4649 something slipped by me. We define a $schema property on the Model, through CrudTrait: https://github.com/Laravel-Backpack/CRUD/pull/4649/files#diff-8e4ec65e1ce9bdbd6a49577959d111a04c231c3ffe02826e118f5c2895a7de4bR15
We can't actually do that, that already exists in Elqouent / is used by other packages like Sushi.
What I did
in DevTools, went to Operations List.
What I expected to happen
Work, like previously.
What happened

What I've already tried to fix it
Nothing, I'm letting @pxpm find a proper solution for it.
Is it a bug in the latest version of Backpack?
The bug is on main but fortunately it hasn't been released yet. Will wait to fix this before I tag a new version of Backpack.

Does it really make sense to store this information on the Model, @pxpm ? Since the information is already stored in a Singleton... isn't it enough for the Model to just have a getter for it, which would get it from there?


Add CITATION.bib file referring to Classiq's paper

Follow Qiskit's format:
https://github.com/Qiskit/qiskit/blob/main/CITATION.bib
This is the relevant paper:
https://arxiv.org/abs/2412.07372

Hi, can I be assigned this issue ?

This is my first time contributing to open source, any feedback is appreciated :)


Implement microbit_dal_version() and set MICROBIT_DAL_VERSION.

To properly get the CODAL version this PR  also needs:

~~https://github.com/lancaster-university/microbit-v2-samples/pull/87~~
https://github.com/lancaster-university/codal-core/pull/169#issuecomment-2056825233

Without that PR it should still work, but the version will still be set to "unknown".
int main() {
    uBit.init();

    uBit.serial.printf("CODAL_VERSION: %s\n", CODAL_VERSION);
    uBit.serial.printf("CODAL_VERSION_LONG: %s\n", CODAL_VERSION_LONG);
    uBit.serial.printf("DEVICE_DAL_VERSION: %s\n", DEVICE_DAL_VERSION);
    uBit.serial.printf("MICROBIT_DAL_VERSION: %s\n", MICROBIT_DAL_VERSION);
    uBit.serial.printf("microbit_dal_version(): %s\n", microbit_dal_version());
    uBit.serial.printf("uBit.getVersion(): %s\n", uBit.getVersion());

    while (true);
}

Once this comment has been implemented in to PR https://github.com/lancaster-university/codal-core/pull/169, then this PR should be ready to be merged as it is.

https://github.com/lancaster-university/codal-core/pull/169#issuecomment-2056825233

Superseded by:

https://github.com/lancaster-university/codal-microbit-v2/pull/434


Input field default focus outline

When I'm install the tailwind elements library that time every input field getting default outline of library, I can't remove this default outline of input field. Please give me solution of this?

Thanks!

We've just release the new v1.0.0-beta1 version and after update you will be able to change the color of the border in two ways:

Customizing primary color
Customizing classes from this page that contains primary color to any other.


[error] TypeError: Cannot read properties of undefined (reading 'executor')

Please provide the environment you discovered this bug in.
$ uname -a
Linux work 5.15.0-84-generic #93-Ubuntu SMP Tue Sep 5 17:16:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Which area/package is the issue in?
create-analog
Description
Steps to reproduce:
$ npm create analog@latest
$ cd analog-project
$ npm install
$ npm run start
Please provide the exception or error you saw
$ npm run start

><EMAIL_ADDRESS>start
> npm run dev

><EMAIL_ADDRESS>dev
> ng serve

An unhandled exception occurred: Cannot read properties of undefined (reading 'executor')
See "/tmp/ng-238Xg8/angular-errors.log" for further details.

$ cat /tmp/ng-238Xg8/angular-errors.log
[error] TypeError: Cannot read properties of undefined (reading 'executor')
    at readTargetOptions (/home/dev/proj/analog-site/analog-project/node_modules/@nx/devkit/src/executors/read-target-options.js:24:60)
    at getNxTargetOptions (/home/dev/proj/analog-site/analog-project/node_modules/@nx/vite/src/utils/options-utils.js:137:42)
    at viteDevServerExecutor (/home/dev/proj/analog-site/analog-project/node_modules/@nx/vite/src/executors/dev-server/dev-server.impl.js:24:69)
    at viteDevServerExecutor.next (<anonymous>)
    at recurse (/home/dev/proj/analog-site/analog-project/node_modules/@nx/devkit/src/utils/convert-nx-executor.js:61:26)
    at /home/dev/proj/analog-site/analog-project/node_modules/@nx/devkit/src/utils/convert-nx-executor.js:78:17

Other information
$ npm --version
9.6.7
$ node -v
v18.17.1
$ ng version
Angular CLI: 16.2.4
Node: 18.17.1
Package Manager: npm 9.6.7
OS: linux x64
Angular: 16.2.7
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router
Package                         Version
@angular-devkit/architect       0.1602.4
@angular-devkit/build-angular   16.2.4
@angular-devkit/core            16.2.4
@angular-devkit/schematics      16.2.4
@angular/cli                    16.2.4
@schematics/angular             16.2.4
rxjs                            7.5.7
typescript                      5.0.4
zone.js                         0.13.3
I would be willing to submit a PR to fix this issue

[ ] Yes
[ ] No

Closing as a duplicate of https://github.com/analogjs/analog/issues/667


Add Dapr Docs contributor video

https://www.youtube.com/watch?v=60cda2U3GKc

/assign

Closing. Merged


fix(ui): use primary colour for dialog buttons

Description:

use primary colour for primary button
use primary colour for close button

Motivation and Context:
Fix funky looking dialog button (seen when lnd crashes)
How Has This Been Tested?
Storybook
Screenshots (if appropriate):
Before:

After:

Types of changes:
UI fix
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 20.085% when pulling d2a230e20f5d5b44fae1a786fc87c1865c47c2c1 on mrfelton:fix/dialog-button into 77621c2ab1bda099d7a19dd4fafb149dc4793dfc on LN-Zap:next.


Error SQLITE_ERROR: near ",": syntax error

Following error message is outputed when running a very simple config (identical to the example, just different names)
{ [Error: Cannot find module '../build/Release/bson'] code: 'MODULE_NOT_FOUND' }
js-bson: Failed to load c++ bson extension, using pure JS version
/home/martin/migration/node_modules/sqlite-to-mongo/lib/SqliteToMongo.js:146
      if (err) throw new Error(err);
               ^

Error: Error: SQLITE_ERROR: near ",": syntax error
    at completeCallback (/home/martin/migration/node_modules/sqlite-to-mongo/lib/SqliteToMongo.js:146:22)
    at Statement.errBack (/home/martin/migration/node_modules/sqlite3/lib/sqlite3.js:16:21)

I have tried it on several systems, same issue occurs

Hey @mdunaiski,
Could you share the sql string you are using? Or is it just a map between column name mongo field name?

It is just a simple mapping
const SqliteToMongo = require('sqlite-to-mongo');

var importer = new SqliteToMongo('sqlitedb.db', 'mongodb://localhost:3001/db');

importer.importCollection('test', {
  tableName : "sqltable,
  columns: {
    'ID': '_id',
    'SURNAME': 'surname',
    'NAME': 'name'
  }
});

Does this typo exists in your codebase?
 tableName : "sqltable,

Even if not, this line looks suspicious:
https://github.com/davidyaha/sqlite-to-mongo/blob/master/lib/SqliteToMongo.js#L139
Would you mind changing that to -2 and check if that works for you?
This is really old code and I would just use join today.. :/

might even be something that requires parenthesis...

yes sorry, the typo was from me anonymising the code. The actual code does have the proper syntax (I have editied the comment)
Changing said line to -2 did not help, same error.

Could you console.log the query variable just after the line 142?

Hi, the issue is that it never connects to mongo. I've gotten that same error when I didn't put in a query.
importer.importCollection('users', {   query:  'SELECT * FROM CurrencyUser ',   columns: {     name: 'Name',     rank: 'Rank',     points : 'Points', }, });
Adding the query solved that issue but instead brought about another.
\node_modules\sqlite-to-mongo\lib\SqliteToMongo.js:55   var collection = this.mongoDb.collection(collectionName);
I console logged a few things and noticed this.mongoDb is undefined because it doesn't seem to connect to mongo my guess is that something is up with:
  this.sqliteDb.once('open', mongo.connect.bind(this, mongoUrl, this._connected.bind(this, cb)));

@davidyaha I confirm, that line requires parenthesis to work properly.
error--> query += column + (index < columnNames.length - 1) ? ', ' : ' ';
right--> query += column + ((index < columnNames.length - 1) ? ', ' : ' ');


Deploy xgql v0.1.3

Description of your changes

https://github.com/upbound/xgql/pull/73
This patch release contains only the above PR, which enables support for gzip compressed HTTP responses. See https://github.com/upbound/xgql/releases/tag/v0.1.3.
I have:

[x] Read and followed Upbound's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested

I'm hoping CI and the e2e tests will do that for me. :) The upstream change was tested per https://github.com/upbound/xgql/pull/73.

/backport


Incorporate kvhash changes in merk PR

Incorporates changes from https://github.com/liftedinit/merk/pull/13

Codecov Report

Merging #319 (a091a3d) into main (166c690) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #319   +/-   ##
=======================================
  Coverage   76.05%   76.05%
=======================================
  Files          68       68
  Lines        9538     9538
=======================================
  Hits         7254     7254
  Misses       2284     2284

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add API support for displaying all evidence for a dataObject

A dataObject such as a neuron may have a variety of properties.  Currently, in order to look up what evidence is associated with a given object, you will have to ask for each property in turn, and look up if there is evidence associated with that property.
If dataObjects supported a .get_evidence() method that took all properties registered with that dataObject and returned a list of evidence associated with whichever property there was, this would make for an easier time interrogating the data.

Something like this is very doable. The contexts which make statements about an object will have a statement object rdf:type object_type.
A more precise implementation is also possible by encapsulating queries for each statement and then getting the contexts in which those statements are made. The query_context.py example shows how this can be done.

hey @mwatts15 , please help me out with this issue.
q1) How can i retrieve Evidence without accessing Context() or Evidence() in the BaseDataObject Class ?
q2) What will the assert look like in the pytest for retrieving evidence?

The idea is basically to retrieve the contexts for each statement and then to retrieve the evidence for each of those contexts.
I would test what happens when there is no evidence attached to any of the contexts (should return no evidence), test that no evidence object is returned more than once (edited)
Also test what happens when there is no context associated with the object you are querying
Here's an example for an evidence_for function:
>>> c1 = Context(key='c1')
>>> c2 = Context(key='c2')
>>> c3 = Context(key='c3')
>>> evc = Context(key='evc')

>>> c1(Apple)('red-delicious').color('red')
PyOpenWorm.statement.Statement(...)

>>> c1(Apple)('red-delicious').sweetness(7)
PyOpenWorm.statement.Statement(...)

>>> c2(Apple)('red-delicious').sweetness(2)
PyOpenWorm.statement.Statement(...)

>>> ev1 = evc(Evidence)(key='mw2019')
>>> ev1.supports(c1)
PyOpenWorm.statement.Statement(...)

>>> ev2 = evc(Evidence)(key='mw2020')
>>> ev2.supports(c2)
PyOpenWorm.statement.Statement(...)

>>> c3.add_import(c1)
>>> c3.add_import(c2)
>>> c3.add_import(evc)
>>> c3.save()

Get evidence about the Apple 'red-delicious':
>>> for x in evidence_for(Apple('red-delicious'), context=c3.stored):
...     print(x)
Evidence(http://openworm.org/entities/Evidence/mw2019)
Evidence(http://openworm.org/entities/Evidence/mw2020)

Should get the union of contexts for each of the statements for which the
given argument is in subject position (at the head of the statement) and then
the union of the evidence supporting each of these contexts. Should return an
iterable of Evidence objects that support any one of the statements.
I don't care what the function is called as long as it makes sense. I'm against
the idea of putting something like a get_evidence on DataObject -- I don't
think, for arbitrary DataObject subclasses, that Evidence makes sense since
arbitrary objects don't have a scholarly reference which is mainly what Evidence is for.

Thank you for the explanation @mwatts15 , please could you also tell me what a base_namespace is?
Exception: If 'key' is given, then 'base_namespace' must also be given to Context

@mwatts15, please help me out with this!

The type of connection i create, PyOpenWorm.connect('readme.conf') vs PyOpenWorm.connect(configFile='tests/data_integrity_test.conf')

Hi, @jaideep-seth .
For the integrity test you will use the integrity test conf, but the setUp method will take care of that for you. readme.conf is just for the sake of the README.md doctests.
Also, just some operational stuff:

Generally, you should make comments about code within a pull request on the pull request itself rather than on the issue so we can tie the conversation to the related code and keep the issue comments to progress on the issue as a whole.
Please keep to one pull request at a time for a single issue until the work is complete on that part of the solution.

@mwatts15 ,could you please assign me to this issue?

[x] querying evidence_for with Contexts for statements having/not having an associated Evidence object.
[ ] adding support for querying evidence_for for DataObjects other than Contexts holding statements.
[ ] adding support for querying evidence_for for Contexts that do have an identifier.

hello @mwatts15, Is this how evidence_for could be queried for Evidence of DataObjects(2nd Checkpoint)?
`

from PyOpenWorm.neuron import Neuron
neuron = Neuron('AVAL')
neuron
Neuron(ident=rdflib.term.URIRef('http://openworm.org/entities/Neuron/AVAL'))
for x in evidence_for(neuron):
...     print(x)
Evidence(http://openworm.org/entities/Evidence/js2019)
`

Like evidence_for in evidence.py should the above shown form of evidence_for be added to dataObject.py?
-Thanks!

I would say that's what it should look like.


Feat/bulma 1.0

Fix: https://github.com/oruga-ui/theme-bulma/issues/100

@messenjer does It already completed?

@jtommy, I fixed all the conflicts.
This branch works with bulma v1, but the following remains to be done:

[ ] update the docs, with Dart Sass's new @use and @forward keywords instead of import. --> https://bulma.io/documentation/start/migrating-to-v1/
[ ] convert the oruga/theme-bulma sass variables to css variables, ie: $carousel-arrow-background <-- --oruga-carousel-arrow-background
[ ] remove the migrate variables --> src/assets/scss/components/utils/_variables-to-migrate.scss

Regards
Mathieu

Are you going to work on theese points?

@jtommy At the moment, I don't have much time again.
We're using oruga 0.7 for a project that's already in production, and for the moment there's no new development planned.
So it's not easy for me to find the time to work on it.
I'm just trying to keep things moving forward so that the day we develop new features, I can plan a migration to oruga 0.8 and bulma 1.0.

Hi @messenjer and @jtommy . I'm entering a phase in a project where will take a relative long time to release a new version and I'm willing to help in this adaptation, but I'm a bit lost in how to develop the theme. Which commands show I use? Can I use Yarn or I need to use NPM.
I hope I can be helpful.

You can use npm, free to review it and fix/improve it

@messenjer I would like to bring this theme up to date.
Do you want to finish this bulma 1.x update yourself? Or should I clone your changes and make my own MR to finish it?

@messenjer I would like to bring this theme up to date with oruga changes. Do you want to finish this bulma 1.x update yourself? Or should I clone your changes and make my own MR to finish it?

Yes, you can. Unfortunately, I didn't work anymore on my previous project using oruga. I moved to another company.

Yes, you can. Unfortunately, I didn't work anymore on my previous project using oruga. I moved to another company.

Alright, thanks for your work.
I hope you will have the chance to come back to Oruga with future projects. We are moving forward :)


chore: attempt to fix plugin wrapper deps

Summary
An attempt to fix the "npm ERR! Cannot set properties of null (setting 'dev')" error
Test plan

Visit the Deploy Preview (insert link to specific page) ...

Relevant links (GitHub issues, Notion docs, etc.) or a picture of cute animal
Standard checks:

[ ] Check the Deploy Preview's Demo site for your PR's functionality
[ ] Add docs when necessary

🧪 Once merged, make sure to update the version if needed and that it was published correctly.

This PR seems to have gotten stale and we don't seem to actively use that demo page anyways. If we run into problems into the future, we can revisit fixing this later.


Fix CI for OTP macOS build

I'm going to start porting over stuff piecemeal from this PR into develop, but I don't think there is any way to merge this PR without a mess, but that's fine since there is not only a considerable gap between how BIFs should be implemented now and how they were when the original BIFs were written, but a number of BIFs are implemented already, so there will necessarily be some cherry-picking anyway.
I think one of the most important things in this code is going to be the tests, but that's going to be a very manual porting process, because the entire runtime was rewritten. In any case, I'm going to prioritize this above other work (other than a few bugs I'm tracking) because I'd like to have all of these BIFs back in the fold, so to speak.


Recommend deleting IE8 to IE7 rendering

This line:
https://github.com/zurb/foundation/blob/master/public/src/includes/_doc_head.php#L12

Ideally this should be addressed on the server. This is what we recommend on H5BP as well. Using it with meta keyword causes too many inconsistencies to handle. http://h5bp.com/b/378

I have no idea why anyone would want IE 8 to "render in IE7". What problem does that solve?

We had kept this in to illustrate the practice, but after some discussion we agree it's confusing and should probably be done elsewhere. It has been removed and committed.


Fix shasums to be usable by shasum and sha256sum applications

When #7277 was merged is was intended to create shasums accessible
in a way shasum -c or sha256sum could use to verify the files the
Helm project ships. The solution created a new file named
shasums.txt. This setup contained a few problems:

The new file file was not uploaded to get.helm.sh for someone
to download and use.
The file had not version in the naming or path. This means that
each new release of Helm will overwrite it. Downloading and
validating an old file is impossible.
If one downloads a single file, the shasums.txt file, and uses
shasum -c it will return an exit code that is 1. This is because
of missing files as it is looking for all the files from the
release.
The shasums.txt file is not signed for verification like the
other files.

This change fixes these problems with the following changes:

Instead of a shasums.txt file there is a .sha256sum file for
each package. For example, helm-3.1.0-linux-amd64.zip.sha256sum.
This file will can be used with shasum -a 256 -c to verify
the single file helm-3.1.0-linux-amd64.zip. The exit code of
checking a single file is 0 if the file passes.
This new .sha256sum file is signed just like the .tar.gz, .zip,
and .sha256 files. The provenance can be verified.
The file name starts with helm- meaning the existing upload
script in the deploy.sh file will move it to get.helm.sh.

Note, the existing .sha256 file can be deprecated and removed
in Helm v4 with the new .sha256sum file taking over. But,
for backwards compatibility with scripts it needs to be kept
during v3.
Closes #7567

It was argued that --ignore-missing could be used with shasums.txt, but the upload/override issue with each subsequent Helm release is real. LGTM


Global variables are miscategorized as static

OS: Windows 11 22H2
VSCode version: 1.18.1
CodeLLDB version: v1.9.2
Compiler: clang++
Debuggee: x86_64-windows / dwarf, both C++ and Swift
LLDB version: From the Swift toolchain
lldb version 16.0.0
compnerd.org Swift version 5.9-dev (LLVM c8ca153def6029d, Swift 1381d9a7b2555c6)

In both C++ and Swift, global variables get miscategorized as static. It's not clear what appears in static.

The problem is likely in:

(or is it an lldb issue that it's not reporting the expected ValueType enumerant?)

or is it an lldb issue that it's not reporting the expected ValueType enumerant?

Yes.  Or at least that I don't understand correctly what these variants are supposed to mean.
If you can come up with a better statics vs globals filter, I'll be happy incorporate that.

On second look, I've concluded that I did mess up filter conditions for locals and globals.   Should be fixed in 1.10.


Mention foundation-global-styles in the JavaScript section

Description
At work we spent quite a lot of time to debug why something as simple as getting the current media query, i.e:
Foundation.MediaQuery.current

was not working for us.
Possible Solution
After debugging a lot, what we noticed was that the <meta class="foundation-mq"> was not properly initialized, which pointed us to SCSS, and indeed there was the problem.
We were missing:
@include foundation-global-styles;

in our main app.scss.
After that was done, .foundation-mq had all the media queries.
Still there was a small thing to change: rather than calling Foundation.MediaQuery.current we had to do:
import {MediaQuery} from 'foundation-sites/js/foundation.util.mediaQuery';
MediaQuery.current;

The equivalent
import {Foundation} from 'foundation-sites/js/foundation.core';
MediaQuery.current;

was also not working.
In general, the JavaScript setup section needs some love, as I guess we are not the only ones that are not importing the full Foundation CSS, but just the small subset that we are need.
Checklist (all required):

[x] I have read and follow the CONTRIBUTING.md document.
[x] There are no other issues similar to this one.
[x] The issue title is descriptive.
[x] The template is correctly filled.

Hi @gforcada,
I agree that we could add some explantations in the Media Query documentation about .foundation-mq and foundation-global-styles (this is unrelated to the Javascript installation).
I think we should also move the .foundation-mq into its own mixin to let folks like you that are "are not importing the full Foundation CSS" importing just the necessary CSS and not having to deal with additonal global styles.
About MediaQuery.current vs Foundation.MediaQuery.current and import paths, we switched in v6.5.0 (RC1 for now) to UMD bundling and now expose ready-to-use plugins for ES6 imports (like import { Dropdown } from 'foundation-sites';). This should resolve your issue.

I think we should also move the .foundation-mq into its own mixin

Would introduce a breaking change for for those that are importing Foundation plugins themselves in Sass. Delaying this for v6.6.0

See https://github.com/zurb/foundation-sites/pull/11382

@ncoden thanks!


trigger preview https://github.com/KittyCAD/PetStore/issues/92

https://github.com/KittyCAD/PetStore/issues/92

LGTM!


Is there an easy way to move vcpkg to a new "identical" machine?

I've got two "identical" (same OS, Visual Studio, etc.) machines. One has vcpkg with a number of installed packages ('older' versions), and I'd like an identical copy on the new machine that is integrated with Visual Studio. There seem to be a number of relatively complicated methods of accomplishing this: export/import, manifest versioning and binary caching. But what I'd really like to do is run a command on the new machine like "vcpkg installfrompath path" or copy the vcpkg folder to the new machine and run "vcpkg restore". I really feel like this must exist and I'm just not seeing it.

Simply copy the vcpkg folder and run vcpkg integrate install

Fantastic, thanks!


Using own data, how to convert?

Hi, and thank you for making this code available. I am trying to get my own data in and run it live, could you clear up a question for me?
to push data in, I use:
void BAInterface::PushKeyframeFeatures(const EIBA::Camera &initial_camera,
                                       const std::vector<float> &initial_depths,
                                       const std::vector<Feature> &source_features,
                                       const std::vector<Measurement> &measured_features)

What I have is:
the camera pose.
3d points, which are:
3d position as Eigen::Vector3d;
A std::vector of 'Observations', each made up of a keyframe and Point2d.
How can convert this data to what is needed by EIBA?
How can I get the inverse depth that is needed?
Any help is much appreciated.
Thanks!

EIBA use inverse depth parameterization for 3D points and do not directly optimize 3D position.  All the feature points are parameterized in the form of inverse depth and the corresponding camera location from which they were first observed. You can decompose 3D position into inverse depth at the first observation and its corresponding camera pose.
The inverse depth is obtained by a depth camera(e.g. Asus Xtion or Kinect).


Only set options if they exist

This makes flake-utils-plus even more general, while still keeping the sane defaults.

This assumes that no builder deviates from NixOS/nixpkgs in the interpretation of its options namespace.

True, I think this is a safe assumption for nixpkgs and networking, perhaps not system.

I don't think examples here is possible, since it doesn't actually change any systemFlake usage. I'll add good example to #17 which should get darwin/home-manager with this merged.
I also switch the options ? lines to be more specific, so this isn't assuming any namespaces except for nixpkgs - which has to be assumed.


CI Updates

This PR brings two changes to our CI:

It abstracts the commitlint task from the lint task and allows it to run in parallel. It's going to be a tiny win, but it should shave a couple seconds off of CI.
It runs the build step on every branch. This is mostly because @BcRikko added the build step as a requirement for PRs to pass, but also because verifying that the project still builds successfully is actually a really good thing. 🤣

Oh snap! Abstracting commitlint actually saved us like 8 seconds. 😎

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Hive Engine Spec] Fix latest partition logic

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

When the Presto db engine spec was changed to support multiple partition columns, it broke Hive because it extends Presto. Table previews and copy select star broke because they wouldn't add partition filters. This PR updates the functions that the Hive spec extends to return and accept the same data types
TEST PLAN

Test copy select statement and ensure it has a partition
Test table preview
Test jinja latest partition function

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
@michellethomas @villebro @betodealmeida @serenajiang

Codecov Report

Merging #8098 into master will decrease coverage by <.01%.
The diff coverage is 22.22%.

@@            Coverage Diff             @@
##           master    #8098      +/-   ##
==========================================
- Coverage   65.93%   65.92%   -0.01%
==========================================
  Files         485      485
  Lines       22890    22895       +5
  Branches     2521     2521
==========================================
+ Hits        15092    15094       +2
- Misses       7667     7670       +3
  Partials      131      131

Impacted Files
Coverage Δ

superset/db_engine_specs/hive.py
40.55% <20%> (-0.3%)
:arrow_down:

superset/db_engine_specs/presto.py
77.98% <33.33%> (+0.05%)
:arrow_up:

Continue to review full report at Codecov.

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


Default to using critical-section

I'm concerned about the soundness of this library (#26). I get letting the user have some control, but I think that the default behavior should opt for safety over speed. Therefore, consider making critical-section a default feature - at least until the safety can really be vetted.

As discussed in #26 lets make critical-section the default - it's still possible to opt-out


Difference in externalDocs description causes Autorest to fail while generating composite client.

doc1 & doc2
Composite Swagger is a mechanism to compose/package multiple swaggers into one client. Hence certain things needs to be same across all the swaggers that need to be packaged into one client.
However, I am not sure if Autorest needs to be so strict on the top level externalDocs. How does that translate to the client documentation?
/cc @samirsolanki @fearthecowboy @olydis
------------------------------------------------------------
autorest -Modeler CompositeSwagger -CodeGenerator Azure.NodeJS -Input https://raw.githubusercontent.com/Azure/azure-rest-api-specs/master/arm-apimanagement/compositeApiManagementClient.json  -outputDirectory lib/services/apiManagement/lib -Header MICROSOFT_MIT_NO_VERSION --version=1.0.1-20170324-2300-nightly
------------------------------------------------------------
FATAL: Error generating client model: System.Exception: $.externalDocs.description has incomaptible values (How to authorize developer accounts using OAuth 2.0 in Azure API Management., How to secure an API configured in API Management).
   at AutoRest.Core.Parsing.YamlExtensions.MergeYamlObjects[T](T a, T b, ObjectPath path) in /Users/amarz/sdk/AutoRest/src/core/AutoRest.Core/Parsing/YamlExtensions.cs:line 170
   at AutoRest.Core.Parsing.YamlExtensions.MergeYamlObjects[T](T a, T b, ObjectPath path) in /Users/amarz/sdk/AutoRest/src/core/AutoRest.Core/Parsing/YamlExtensions.cs:line 155
   at AutoRest.Core.Parsing.YamlExtensions.MergeYamlObjects[T](T a, T b, ObjectPath path) in /Users/amarz/sdk/AutoRest/src/core/AutoRest.Core/Parsing/YamlExtensions.cs:line 155
   at AutoRest.Core.Parsing.YamlExtensions.MergeWith(YamlMappingNode self, YamlMappingNode other) in /Users/amarz/sdk/AutoRest/src/core/AutoRest.Core/Parsing/YamlExtensions.cs:line 173
   at AutoRest.CompositeSwagger.CompositeSwaggerModeler.Build() in /Users/amarz/sdk/AutoRest/src/modeler/AutoRest.CompositeSwagger/CompositeSwaggerModeler.cs:line 110
   at AutoRest.Core.AutoRestController.Generate() in /Users/amarz/sdk/AutoRest/src/core/AutoRest.Core/AutoRestController.cs:line 56

Since these are separate entities in API Management, we wanted our documentation to be like doc1 and doc2

Will take a look and respond soon, apologize for the delay.

So it seems like any top level property (externalDocs/info) objects would cause the same issue, which happens here @fearthecowboy any thoughts on how we should merge such top level property objects

The trouble is, what is the expected behavior?
You can't possibly merge them; in the composed swagger document there can only be one.

@solankisamir CompositeSwagger is a functionality that simply merges individual semantically similar swagger specs under the hood before generating the client. We ensure top level properties are the same to ensure this. The best solution here would be to have externalDocs point to both the links you have mentioned in all of the swagger specs so the top level properties look exactly the same.
P.S.: This should have failed the Travis CI builds

@amarzavery can you close this issue after verifying

@dsgouda - Can we close this issue?

Yes, we (AutoRest and linter folks) have provided a workaround for the issue.


Tsan error fix.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

It is possible that the first point touching the lock is at remove_fd_from_all_epoll_sets, and another once_init is added there. Also unlock the lock before an early return.

Fixes #4681.

It is hard to get jenkins green. Do we need to wait for one?


Add log of the different deployment/build/run events

This should include the date for each event - e.g.:
State transition
Termination (manual)
First abort call (with reason)
This is linked to the UI part fo this feature (https://github.com/slipstream/SlipStreamUI/issues/88)

Demo done.


Jest not able to add .ts extension to fuzzyfy

Getting the below error

@ad1992 I have a fix for this. I will fix it along with this PR.
The issue is:
Generally node_modules are precompiled to common.js (non-modular )versions of js i.e. not es6. In Fuzzify it's expected to bundle and take care by the consumer package. Hence we need to tell jest how to handle this.

Hey @ad1992 👋
I have a fix for this. I will fix it along with this PR.
The issue is: Generally node_modules are precompiled to common.js (non-modular )versions of js i.e. not es6. In Fuzzify it's expected to bundle and take care by the consumer package. Hence we need to tell jest how to handle this.

@shrilakshmishastry awesome, just link this issue as well in your PR


Please add InvertedSoftware.PLogger.Core the the third party logging provider list

Please add InvertedSoftware.PLogger.Core the the third party logging provider list.
Nuget:
https://www.nuget.org/packages/InvertedSoftware.PLogger.Core/1.0.0
GitHub
https://github.com/invertedsoftware/InvertedSoftware.PLogger.Core

Can you create an issue from the doc page? That will connect the doc to the issue. Go to the bottom of the page and select This page .


Update cloud-services-sizes-specs.md

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


Dispose services in order

Services should be disposed in the reverse order that they were created.
If service A depends on service B, B will be created first, then A. Now when Dispose() is called on A, it could have to use B. Unfortunately B might already be disposed as the order is not deterministic and based on a dictionary entry. I suggest we enforce the disposal order to be both logical and deterministic as far as the dependency order is defined.

I have a branch that implements this in our container and adds specification tests but I have couple of concerns:

We are not requiring IServiceProvider to be IDisposable in specification but adding this tests forces it. Neither Autofac not StructureMap implementation of IServiceProvider is IDisposable
Autofac does this in correct order but StructureMap disposes services in the order of creation.

@khellang @nblumhardt what are your thought on this?

Thanks for the loop-in! This sounds like another case where making assumptions in the framework could cause issues for some container integrations.
Reverse-order disposal is necessary to correctly tear down some component graphs, e.g. where A : IDisposable "registers" itself with B : IDisposable on creation, and "un-registers" on disposal, but:

The framework could avoid these kinds of object graphs, or
Some additional code could be added, e.g. mediator objects, to make the scenarios work independently of disposal order.

If users want forward-order disposal they should be free to depend on it by selecting a container that implements it - and vice-versa. Personally, I feel reverse-order is the right way to do it, but it's highly unlikely everyone agrees with me ;-)
#433 is a discussion along these lines - disposal order would be a good item to add to the summary on that ticket, I think.

Fixed by https://github.com/aspnet/DependencyInjection/pull/505


precip variability across time scale

Implement @msahn's work into PMP

Branch: 731_msa_precip_benchmark
Directory to start: https://github.com/PCMDI/pcmdi_metrics/tree/731_msa_precip_benchmark/pcmdi_metrics/precip_variability
Draft PR for tracking changes: https://github.com/PCMDI/pcmdi_metrics/pull/732

The branch name is changed to "731_msa_precip_variability".


DPS instructions missing critical steps (Add enrollment group and do the certificate dance)

The DPS instructions have changed in the last week.  I followed these instructions on Friday 10/12/18 and I was walked through the process of setting up DPS, downloading certificates, proving ownership, and uploading certificates.  Without the certificate dance, you can't setup an enrollment group within DPS and without the enrollment group, DPS does not provision devices.
Has this functionality changed?  If so, can you add documentation to this quickstart walking the user through the new process.
I discovered these changes while conducting an Azure Sphere Bootcamp and the students were not able to use DPS.  This is a critical lab that helps the students understand the DPS subsystem and how to set it up.  We were able to get past the roadblock by adding the student devices to the Hub using the hub  connection string.
Please advise,
Brian

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

ID: 9a75512f-47db-ecee-70d3-9e2e5f470e1c
Version Independent ID: 74f13239-66c4-dd09-68d4-a77a6c65fcba
Content: Set up Device Provisioning in the Azure portal
Content Source: articles/iot-dps/quick-setup-auto-provision.md
Service: iot-dps
GitHub Login: @wesmc7777
Microsoft Alias: wesmc

You can provisioning devices to an IoT hub through DPS using certificate or symmetric key attestation with enrollment groups. These are the only two methods supported at this time for enrollment groups. Symmetric key attestation is a bit new. It was introduced in the Sept. Anniversary update. However, certificate attestation has been supported for enrollment groups for quite some time.
I'm not sure which instructions you are having problems with. Is it only Azure Sphere specific instructions you are referring to?

There used to be instructions to download a cert, maybe the IoT hub cert, you then used it to sign a challenge string. Then you could setup an enrollment group on the DPS. My above steps are not correct but they may be close.
What happened to the step to create the enrollment group. That’s not there anymore.
Brian
Sent with BlackBerry Work
(www.blackberry.com)
From: Wesley McSwain <notifications<EMAIL_ADDRESS>Date: Wednesday, Oct 17, 2018, 11:07 AM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Willess, Brian <Brian.Willess<EMAIL_ADDRESS>Author <author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] DPS instructions missing critical steps (Add enrollment group and do the certificate dance) (#17043)
You can provisioning devices to an IoT hub through DPS using certificate or symmetric key attestation with enrollment groups. These are the only two methods supported at this time for enrollment groups. Symmetric key attestation is a bit new. It was introduced in the Sept. Anniversary update. However, certificate attestation has been supported for enrollment groups for quite some time.
I'm not sure which instructions you are having problems with. Is it only Azure Sphere specific instructions you are referring to?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/17043#issuecomment-430689670, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AnsoW_a09KWqekHRCxmApxpjVgZQqTFqks5ul1XDgaJpZM4Xjxu5.

The quickstarts in this section use certificate attestation with enrollment groups.  However, these create the enrollment group programmatically instead of manually in the portal.
There is also the Configure verified CA certs How-to that describes doing proof of possession etc.

Hi  Westly,
Last week there were instructions on how to download the initial certificate to use for the proof-of-possession for the DPS.  I’ve done this a couple of times before where we downloaded the X.509 certificate that was used for the proof-of-possession exercise.
It looks like now, I need to have the tools to generate this certificate myself and upload it to Azure.  Is this the case?
Thanks,
Brian
Brian Willess
<EMAIL_ADDRESS><EMAIL_ADDRESS>Technical Solutions Engineer
Engineering & Technology
[http://digital.avnet.com/signature/images/Avnet_logo_tagline_rgb.png]
1672 W. Flintlock Way
Chandler AZ, 85286
O<PHONE_NUMBER>
avnet.comhttp://www.avnet.com/
From: Wesley McSwain<EMAIL_ADDRESS>Sent: Wednesday, October 17, 2018 9:51 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Willess, Brian<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] DPS instructions missing critical steps (Add enrollment group and do the certificate dance) (#17043)
The quickstarts in this sectionhttps://docs.microsoft.com/azure/iot-dps/quick-enroll-device-x509-java use certificate attestation with enrollment groups. However, these create the enrollment group programmatically instead of manually in the portal.
There is also the Configure verified CA certs How-tohttps://docs.microsoft.com/en-us/azure/iot-dps/how-to-verify-certificates that describes doing proof of possession etc.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/17043#issuecomment-430704497, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AnsoW2YwLWQjZqtRd2BbmJPhRmvD6-K2ks5ul1_bgaJpZM4Xjxu5.

I'm not aware of those instructions for DPS. Perhaps it was a specific Azure Sphere test lab instructions?

Brian,
Is this the doc you are looking for?
https://docs.microsoft.com/en-us/azure-sphere/app-development/setup-iot-hub

Yes that’s it.  I’ll update the lab to use that link.
Thank you,
Brian
Brian Willess
<EMAIL_ADDRESS><EMAIL_ADDRESS>Technical Solutions Engineer
Engineering & Technology
[http://digital.avnet.com/signature/images/Avnet_logo_tagline_rgb.png]
1672 W. Flintlock Way
Chandler AZ, 85286
O<PHONE_NUMBER>
avnet.comhttp://www.avnet.com/
From: Wesley McSwain<EMAIL_ADDRESS>Sent: Wednesday, October 17, 2018 2:46 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Willess, Brian<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] DPS instructions missing critical steps (Add enrollment group and do the certificate dance) (#17043)
Brian,
Is this the doc you are looking for?
https://docs.microsoft.com/en-us/azure-sphere/app-development/setup-iot-hub
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/17043#issuecomment-430800922, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AnsoWydaar0SkA5HBBAaqQf4lz0VIjr5ks5ul6UcgaJpZM4Xjxu5.

You are welcome. Thanks for letting us know.

#please-close

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


2016-03-24 21:54:37,575 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstanceNicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Running pre listener [AgentInstanceNicActivate]
2016-03-24 21:54:37,599 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstanceNicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Finished pre listener [AgentInstanceNicActivate]
2016-03-24 21:54:37,613 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstanceIpsecNicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Running pre listener [AgentInstanceIpsecNicActivate]
2016-03-24 21:54:37,620 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstanceIpsecNicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Finished pre listener [AgentInstanceIpsecNicActivate]
2016-03-24 21:54:37,620 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(HostOnlyNicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Running pre listener [HostOnlyNicActivate]
2016-03-24 21:54:37,646 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(HostOnlyNicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Attempting to run process [vnet.create:null] on resource [5]
2016-03-24 21:54:37,646 INFO  [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->vnet:5] [instance.start->(InstanceStart)->nic.activate->(HostOnlyNicActivate)->vnet.create] [] [erviceReplay-19] [i.c.p.e.p.i.ResourceStatesDefinition] State [active] is not a valid state
2016-03-24 21:54:37,648 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(HostOnlyNicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Exiting [ALREADY_DONE] process [vnet.activate:null] on resource [5]
2016-03-24 21:54:37,650 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(HostOnlyNicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Finished pre listener [HostOnlyNicActivate]
2016-03-24 21:54:37,657 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Running handler [NicActivate]
2016-03-24 21:54:37,659 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Attempting to run process [network.activate:null] on resource [1]
2016-03-24 21:54:37,659 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Exiting [ALREADY_DONE] process [network.activate:null] on resource [1]
2016-03-24 21:54:37,661 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Attempting to run process [vnet.activate:null] on resource [5]
2016-03-24 21:54:37,661 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Exiting [ALREADY_DONE] process [vnet.activate:null] on resource [5]
2016-03-24 21:54:37,666 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Attempting to run process [ipaddressnicmap.create:null] on resource [1125286]
2016-03-24 21:54:37,666 INFO  [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->ipAddressNicMap:1125286] [instance.start->(InstanceStart)->nic.activate->(NicActivate)->ipaddressnicmap.create] [] [erviceReplay-19] [i.c.p.e.p.i.ResourceStatesDefinition] State [active] is not a valid state
2016-03-24 21:54:37,668 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Exiting [ALREADY_DONE] process [ipaddressnicmap.activate:null] on resource [1125286]
2016-03-24 21:54:37,669 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Attempting to run process [ipaddress.create:null] on resource [1125295]
2016-03-24 21:54:37,669 INFO  [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->ipAddress:1125295] [instance.start->(InstanceStart)->nic.activate->(NicActivate)->ipaddress.create] [] [erviceReplay-19] [i.c.p.e.p.i.ResourceStatesDefinition] State [active] is not a valid state
2016-03-24 21:54:37,671 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Exiting [ALREADY_DONE] process [ipaddress.activate:null] on resource [1125295]
2016-03-24 21:54:37,672 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Attempting to run process [ipaddress.activate:null] on resource [1125295]
2016-03-24 21:54:37,672 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Exiting [ALREADY_DONE] process [ipaddress.activate:null] on resource [1125295]
2016-03-24 21:54:37,673 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(NicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Finished handler [NicActivate]
2016-03-24 21:54:37,678 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(CreateInstanceAssociatePublicIpAddress)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Running post listener [CreateInstanceAssociatePublicIpAddress]
2016-03-24 21:54:37,680 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(CreateInstanceAssociatePublicIpAddress)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Finished post listener [CreateInstanceAssociatePublicIpAddress]
2016-03-24 21:54:37,680 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(VirtualMachineMetadata)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Running post listener [VirtualMachineMetadata]
2016-03-24 21:54:37,682 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(VirtualMachineMetadata)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Finished post listener [VirtualMachineMetadata]
2016-03-24 21:54:37,682 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstanceApplyItems)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Running post listener [AgentInstanceApplyItems]
2016-03-24 21:54:37,690 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstanceApplyItems)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Finished post listener [AgentInstanceApplyItems]
2016-03-24 21:54:37,690 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(InstanceHealthcheckRegister)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Running post listener [InstanceHealthcheckRegister]
2016-03-24 21:54:37,697 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(InstanceHealthcheckRegister)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Finished post listener [InstanceHealthcheckRegister]
2016-03-24 21:54:37,697 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstancePostNicActivate)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Running post listener [AgentInstancePostNicActivate]
2016-03-24 21:54:37,698 INFO  [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstancePostNicActivate)] [] [erviceReplay-19] [.p.c.v.i.ConfigItemStatusManagerImpl] Waiting on [agent:4138] on [ipsec-hosts], not applied requested [1370771] > applied [1369940]
2016-03-24 21:54:37,699 INFO  [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstancePostNicActivate)] [] [erviceReplay-19] [.p.c.v.i.ConfigItemStatusManagerImpl] Waiting on [agent:4138] on [hosts], not applied requested [5132338] > applied [5127935]
2016-03-24 21:54:37,699 INFO  [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstancePostNicActivate)] [] [erviceReplay-19] [.p.c.v.i.ConfigItemStatusManagerImpl] Waiting on [agent:4138] on [iptables], not applied requested [1388924] > applied [1388095]
2016-03-24 21:54:37,699 INFO  [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279->nic:655417] [instance.start->(InstanceStart)->nic.activate->(AgentInstancePostNicActivate)] [] [erviceReplay-19] [.p.c.v.i.ConfigItemStatusManagerImpl] Waiting on [agent:4138] on [healthcheck], not applied requested [3115691] > applied [3111121]
2016-03-24 21:54:47,211 DEBUG [3bb4c24a-a93d-40d8-a9aa-2157a592dc1d:26499806] [instance:651279] [instance.start->(InstanceStart)] [] [erviceReplay-19] [c.p.e.p.i.DefaultProcessInstanceImpl] Exiting [TIMEOUT] process [nic.activate:null] on resource [655417

Happens because one of the agents fails to process config update requests:
Following errors are seen on the agent side:
Config update failure:
2016-03-24 22:16:05,611 INFO agent [140349412117232] [utils.py:430] Response: {"name": "reply.5259761756235177251", "transitioningProgress": null, "resourceType": null, "resourceId": null, "id": "4a8c170e-60ea-45b6-84e8-45958f4204b9", "transitioningMessage": "Update failed", "time":<PHONE_NUMBER>000, "previousNames": ["delegate.request"], "transitioning": "yes", "data": {"name": "config.update.reply", "transitioningProgress": null, "resourceType": "agent", "resourceId": "4139", "id": "3d617247-d399-4399-8b8b-13f19ff96a75", "transitioningMessage": "Update failed", "time":<PHONE_NUMBER>000, "previousNames": ["config.update"], "transitioning": "yes", "data": {"output": "Lock failed", "exitCode": 122}, "previousIds": ["717bf6d8-7fe1-40c5-861b-b6ab283d81eb"]}, "previousIds": ["9ef82ceb-e7fc-458a-8282-236026887d8d"]} [0.0126748085022] seconds

Instance stop failure:
2016-03-24 22:16:17,115 ERROR agent [140349412137552] [event.py:112] Error in request : 73d7f625-6a27-41e7-9788-3c30d88563e9
Traceback (most recent call last):
  File "/var/lib/cattle/pyagent/cattle/agent/event.py", line 95, in _worker_main
    resp = agent.execute(req)
  File "/var/lib/cattle/pyagent/cattle/agent/__init__.py", line 15, in execute
    return self._router.route(req)
  File "/var/lib/cattle/pyagent/cattle/plugins/core/event_router.py", line 13, in route
    resp = handler.execute(req)
  File "/var/lib/cattle/pyagent/cattle/agent/handler.py", line 34, in execute
    return method(req=req, **req.data.__dict__)
  File "/var/lib/cattle/pyagent/cattle/compute/__init__.py", line 71, in instance_force_stop
    self._do_instance_force_stop(instanceForceStop)
  File "/var/lib/cattle/pyagent/cattle/plugins/docker/compute.py", line 833, in _do_instance_force_stop
    docker_client().stop(instanceForceStop['id'])
  File "/var/lib/cattle/pyagent/dist/docker/utils/decorators.py", line 21, in wrapped
    return f(self, resource_id, *args, **kwargs)
  File "/var/lib/cattle/pyagent/dist/docker/api/container.py", line 382, in stop
    timeout=(timeout + (self.timeout or 0)))
  File "/var/lib/cattle/pyagent/dist/docker/utils/decorators.py", line 47, in inner
    return f(self, *args, **kwargs)
  File "/var/lib/cattle/pyagent/dist/docker/client.py", line 108, in _post
    return self.post(url, **self._set_request_timeout(kwargs))
  File "/var/lib/cattle/pyagent/dist/requests/sessions.py", line 511, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/var/lib/cattle/pyagent/dist/requests/sessions.py", line 468, in request
    resp = self.send(prep, **send_kwargs)
  File "/var/lib/cattle/pyagent/dist/requests/sessions.py", line 576, in send
    r = adapter.send(request, **kwargs)
  File "/var/lib/cattle/pyagent/dist/requests/adapters.py", line 449, in send
    raise ReadTimeout(e, request=request)

I've been monitoring this table, and the value stays the same for like 10 mins already:
mysql> select name, requested_version, applied_version from config_item_status where agent_id=4139 and applied_version < requested_version;
+-------------+-------------------+-----------------+
| name        | requested_version | applied_version |
+-------------+-------------------+-----------------+
| healthcheck |           3148381 |         3116389 |
| ipsec-hosts |           1340426 |         1340424 |
| hosts       |           5066525 |         5065241 |
| iptables    |           1357270 |         1357268 |
+-------------+-------------------+-----------------+

The python-agent's infstance_force_stop is timing out. We should probably add a timeout=5 to that function. The cause of the container not stopping is probably inside the container itself and not being able to terminate its process

Per @ibuildthecloud this occurred in latest when the environment was completely sideways. The entire host was hung up in a number of ways. Closing.


Out of the box support for symbols in font (ie. oh-my-zsh default prompt)

On my normal terminal, there are symbols within my prompt (the default oh my zsh theme):

However, these symbols don't display properly on Lapce with the default font (and also with other fonts like Consolas):

There may be a way to get this to work (maybe by adding a custom font patched with powerline), but I know it works by default in vscode and all other system terminals so there must be something that can be done to support this out of the box.
In case this is an abnormality rather than a lack of support, I am running Lapce 1.3.2 and running on Linux Wayland.

Is this specific to the terminal or does it apply to the rest of the editor? I'm also experiencing this with my powerline prompt.


Fix bug so string values actually convert to the correct timezone

String values aren't being converted to the correct timezone so they show up at UTC. This fixes that. It also replaces the use of a function that just returns the value of date_formatter with date_formatter.
@rosskarchner @kave

:+1:


Deleting a product was not sync in Firestore

Bug report
Describe the bug
Deleting a product does not delete the data in Firestore nor it change the status to active = false
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to Stripe > Products
Create test products
Delete test products
check Firestore if the data is deleted

Expected behavior
The data should be deleted or active status change to false
Screenshots
Created a test product

Screenshot from firestore that proves the data is added

Delete the test product

Screenshot from firestore that proves the data is still not deleted nor changed active status to false. also price data has active status to true

System information

OS: Windows 10
Browser (if applies): Edge

Additional context
Please apply a fix asap as I will be needed it sooner.

Once a product has been used for a transaction it can't be deleted anymore in Stripe, that's why we didn't implement this sync. Rather it is recommended to archive the product/price which will update the active parameter to false.


Machine mac-10 lost external connection from iPhone device.

Machine mac-10 lost external connection from iPhone device.

External connection has been restored by rebooting machine.


Passing --version-number=X.X.X doesn't update during Xcode build (gym)

I am trying to upload a testflight build with fastlane. When I pass
fastlane testflight --version-number=3.3.1
It correctly gets the latest TestFlight build number, increments it, but doesn't set that as the version number when building the project in Xcode, so the upload fails because version 3.3 (currently set in Xcode) is already released in iTunes Connect.
Am I misunderstanding the purpose of the action or have I got something misconfigured in my project/lane perhaps?
lane :testflight
  increment_build_number({
    build_number: latest_testflight_build_number + 1
  })
  gym(scheme: "TrilbyTV", workspace: "../TrilbyTV.xcworkspace")
  # snapshot
  sigh
  pilot(
    skip_submission: false,
    distribute_external: false,
    changelog: release_notes
  )

[Transporter Error Output]: ERROR ITMS-90186: "Invalid Pre-Release Train. The train version '3.3' is closed for new build submissions"
[16:46:48]: [Transporter Error Output]: ERROR ITMS-90062: "This bundle is invalid. The value for key CFBundleShortVersionString [3.3] in the Info.plist file must contain a higher version than that of the previously approved version [3.3]."

Sentry: e3ce0a5c0342e1c41a18418ac3dcd7d6

@dombarnes Is this still an issue for you?

I also have problem

@phpmaple Could you fill in some details per https://github.com/fastlane/fastlane/blob/master/ISSUE_TEMPLATE.md? Thanks.


Crouton doesn't work after upgrade

This is my third time I end up with a broken crouton after an update.  It seems no matter what I do and which directions i follow to upgrade chroot, I end up with the same result (see below).  Thankfully, I keep a backup of an old version (circa May) that I revert to keep working.
System

Chromebook Pixel 2
Ubuntu trusty
Gnome 3
Xiwi
Chrome Extension

What I have tried

I have update crouton with sudo sh ~/Downloads/crouton -u -n <chroot>
I have downloaded directly from the provided link on project page
I also have done the sudo enter-chroot then update from that within the chroot as documented on homepage.

Result
None of these approach work or fix my issue.  After I successfully update my chroot, when I start it using sudo startgnome, I always get disconnected from the X server immediately as shown in the output below.
Output
The xiwi window launches black goes away after a few seconds with result
$ sudo startgnome -n gnome-trusty
Entering /mnt/stateful_partition/crouton/chroots/gnome-trusty...

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-76-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.14.0 #1 SMP Mon Jul 13 22:32:37 PDT 2015 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=8f7f09fd-3fa9-c04b-8582-dd9473131ef9/PARTNROFF=1 hashtree=PARTUUID=8f7f09fd-3fa9-c04b-8582-dd9473131ef9/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=0a61dc61b59537ad616e7cae0d7c72fb9fcfcd0c salt=94f7d0efb4a4b2249fefb8384a4bdef37ba4a09908efaa9068f7d03a32a0fe23" noinitrd vt.global_cursor_default=0 kern_guid=8f7f09fd-3fa9-c04b-8582-dd9473131ef9 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic i915.enable_psr=1
Build Date: 12 February 2015  02:49:29PM
xorg-server 2:1.15.1-0ubuntu2.7 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.30.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Thu Jul 23 17:04:02 2015
(++) Using config file: "/etc/X11/xorg-dummy.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
xf86: found device 0
xf86: found device 0
/usr/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
crouton: version 1-20150716185530~master:aba2c948
release: trusty
architecture: amd64
xmethod: xiwi
targets: gnome,xiwi,touch,gnome-desktop
host: version 6946.86.0 (Official Build) stable-channel samus
kernel: Linux localhost 3.14.0 #1 SMP Mon Jul 13 22:32:37 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Error: not connected.
Cannot connect to extension, retrying...
Connected to extension, launched crouton in a window.
Error: target STRING not available
Running exit commands...
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down Hangup
Hangup
(EE) Server terminated successfully (0). Closing log file.

Not unmounting /mnt/stateful_partition/crouton/chroots/gnome-trusty as another instance is using it.

@vladimirvivien,
I don't have a Pixel2 (I wish, I wish) to experiment on but I have had similar problems with Chrome OS updates causing problems and, like you, I would do a crouton update to try to fix it.
In all but a few cases, it worked and I was back in business.
Being on the stable channel like you are, I would think this problem would be rare, I haven't heard of that many others running into this constantly.
This is the place to seek help though, from others and the experts.
The one thing I would recommend you to try is using xmethod 'xorg' instead of 'xiwi', you wouldn't have the convenience of your chroot in a tab/window/full-screen and you would have to revert to the Ctrl+Alt+Shift+<-/-> key combo to get back and forth but it might cause less problems and give you the added advantage of hardware acceleration.
You can add it to your existing chroot using:
sudo sh ~/Downloads/crouton -t xorg -n gnome-trusty -u
Doing this, however, will make 'xorg' your default xmethod so to use 'xiwi' instead when launcing yu'd use:
sudo startgnome -n gnome-trusty -X xiwi.
If 'xorg' just doesn't work or isn't for you, you can change the xmethod back to 'xiwi' using:
sudo sh ~/Downloads/crouton -t xiwi -n gnome-trusty -u
-DennisL

@DennisLfromGA
Thank you for taking your time and help with this.  (sidenote: the pixel 2 is a great machine, if you ever get a chance to update).
I use xiwi because of the convenience of windowed environment. Luckily, my last chroot install still works though i get a warning of it being out of date.  So I will continue to use an old chroot for now until I get this figured out.  If all fails maybe I will go full xorg.
Thanks again for the help.

Anyone else who may be able to help is welcome to chime in.
Thanks.

@DennisLfromGA
Thanks again.  I think Xorg will ok for me with Gnome.
My first stint was with Ubuntu-desktop unity and was slow, but Gnome feels more responsive.
Thanks for the help.

@vladimirvivien - You're welcome, sorry there's no real solution for 'xiwi' yet...

My first stint was with Ubuntu-desktop unity and was slow, but Gnome feels more responsive.

I like gnome better than unity also but, lately, I've been stuck on the lxde-desktop since it's light and quick.


Select elements are cropping descenders

See:
https://dl.dropboxusercontent.com/spa/jfyjetktfp495r1/tk-_qo-1.png

@boutell @stuartromanek I'm having a hard time reproducing this. Any thoughts?

Runaway project level CSS?
On Tue, Oct 25, 2016 at 8:14 AM, Austin Starin<EMAIL_ADDRESS>wrote:

@boutell https://github.com/boutell @stuartromanek
https://github.com/stuartromanek I'm having a hard time reproducing
this. Any thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/punkave/apostrophe/issues/719#issuecomment-256017861,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fbnOBk-pPkDP2OoNPYriJiYDoTP4ks5q3fKUgaJpZM4KfSNz
.

--
*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

I think it is. I will verify.

It happens in the sandbox project:
https://dl.dropboxusercontent.com/spa/jfyjetktfp495r1/7fg__tn9.png
On Tue, Oct 25, 2016 at 5:57 PM, Austin Starin<EMAIL_ADDRESS>wrote:

I think it is. I will verify.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/punkave/apostrophe/issues/719#issuecomment-256189022,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fQE2uQfAv2CSmhS2G-seG7GXHdltks5q3ntOgaJpZM4KfSNz
.

--
*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

can't reproduce this

I can't either. Double checked.

OK, I'll close, it'll recur if it's meant to.


Updating Architecture Document

Atualização das informações do documento de arquitetura.

Pull Request Test Coverage Report for Build 390222188

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.855%

Totals

Change from base Build 389949151:
0.0%

Covered Lines:
616

Relevant Lines:
636

💛  - Coveralls


Versioning Error When Submitting to Google Play

I prevously submitted a standalone app built with Exponent to Google Play. Now when I am submitting an updated version, I see the following error.

I have updated exp.json file from "version": "1.0.1" to "version": "1.1.0", and I am wondering why am I still having this error?

Hey sorry just saw this. You need to use this key https://docs.expo.io/versions/v14.0.0/guides/configuration.html#versioncodeversion-number-required-by-google-play-increment-by-one-for-each-release-httpsdeveloperandroidcomstudiopublishversioninghtml in exp.json.

@jesseruder Perfect, thank you!


create CLI

Follow the core functions ready for review

Why do you have two PR with the same feature? You could add the cobra thing here as a new commit without problem.


udate welcome page

Please review this welcome page updated according to new design.

Thx for your PR @Amutha37 :bow:
Nice work! :raised_hands:
A couple of suggestions:

can we stick to using double-quotes (") for strings please rather than single quotes (')? We use double quotes everywhere else in the codebase, so let's keep that consistent. I suspect that it is your IDE's lint settings that is making the changes for you. You may want to update your lint settings for this project
In your PR description, can you link the trello card's url to this PR?

Your PR should be ready to merge once the above points have been addressed :+1:
@batteries76 , @ymloh , any suggestions?

 DEV: update welcome page

Thank you for the highlights. I have to reinstall and change all my sett In
VSCode. I just reinstalled my VSCode that must be the cause. I will get
that settings done today.
Amutha
On Wed, 2 Mar 2022 at 7:27 am, hqtan @.***> wrote:

Thx for your PR @Amutha37 https://github.com/Amutha37 🙇
Nice work! 🙌
A couple of suggestions:

can we stick to using double-quotes (") for strings please rather
than single quotes (')? We use double quotes everywhere else in the
codebase, so let's keep that consistent. I suspect that it is your IDE's
lint settings that is making the changes for you. You may want to update
your lint settings for this project
In your PR description, can you link the trello card's url to this
PR?

Your PR should be ready to merge once the above points have been addressed
👍
@batteries76 https://github.com/batteries76 , @ymloh
https://github.com/ymloh , any suggestions?
—
Reply to this email directly, view it on GitHub
https://github.com/CodeforAustralia/council-emissions-calculator/pull/64#issuecomment-1055829788,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKV7DNDU73BTZMAVEOMYJZLU5Z4TDANCNFSM5PTB4IGQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***
com>

Hi Qing, You can review the quotation mark I have update to double quote now.
Trello card  :  https://trello.com/c/UJMBoS1t/284-dev-update-welcome-page


Add a docker configuration for running with Kafka 2.4.2

This is cherry-picked from https://github.com/figma/kafkajs/commit/f1a090999f078fcb16f24a40d589e39aebd112d8,
and then I adjusted for the recent changes in master as well as updated to Confluent Kafka 5.4.2.

Mostly for the record: This also links to #713.

Rebased, and added https://github.com/tulios/kafkajs/pull/763/commits/df97b785e3ad00e280fdbdcef67fa31c34f6b754 to fix a problem in the describe configs test.

It seems the errors in the listgroups/deletegroups tests are persistent with this version of Kafka, and not just flakiness. Every run I've seen now has failed due to those tests, so there may be a bug somewhere (either in KafkaJS or the tests)

True that:
kafka1 [2020-06-25 18:08:07,144] ERROR Exception while processing request from <IP_ADDRESS>:9092-<IP_ADDRESS>:51474-126 (kafka.network.Processor)
kafka1 org.apache.kafka.common.errors.InvalidRequestException: Error parsing request header. Our best guess of the apiKey is: 16
kafka1 Caused by: java.nio.BufferUnderflowException
kafka1 	at java.nio.Buffer.nextGetIndex(Buffer.java:500)
kafka1 	at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:135)
kafka1 	at org.apache.kafka.common.utils.ByteUtils.readUnsignedVarint(ByteUtils.java:144)
kafka1 	at org.apache.kafka.common.protocol.ByteBufferAccessor.readUnsignedVarint(ByteBufferAccessor.java:58)
kafka1 	at org.apache.kafka.common.message.RequestHeaderData.read(RequestHeaderData.java:132)
kafka1 	at org.apache.kafka.common.message.RequestHeaderData.<init>(RequestHeaderData.java:83)
kafka1 	at org.apache.kafka.common.requests.RequestHeader.parse(RequestHeader.java:93)
kafka1 	at kafka.network.Processor.$anonfun$processCompletedReceives$1(SocketServer.scala:904)
kafka1 	at kafka.network.Processor.$anonfun$processCompletedReceives$1$adapted(SocketServer.scala:900)
kafka1 	at scala.collection.Iterator.foreach(Iterator.scala:941)
kafka1 	at scala.collection.Iterator.foreach$(Iterator.scala:941)
kafka1 	at scala.collection.AbstractIterator.foreach(Iterator.scala:1429)
kafka1 	at scala.collection.IterableLike.foreach(IterableLike.scala:74)
kafka1 	at scala.collection.IterableLike.foreach$(IterableLike.scala:73)
kafka1 	at scala.collection.AbstractIterable.foreach(Iterable.scala:56)
kafka1 	at kafka.network.Processor.processCompletedReceives(SocketServer.scala:900)
kafka1 	at kafka.network.Processor.run(SocketServer.scala:790)
kafka1 	at java.lang.Thread.run(Thread.java:748)

... let's see :)

So, the thing here is that Kafka 2.4.0 supports "tagged fields (KIP-86)", which introduce a new encoding scheme for unsigned varints, and new messages that contain these.
The listGroups v2 and deleteGroups v3 requests that KafkaJS uses should have a tag buffer field at the end, and similarly the responses need to handle these as well. In principle the writing of these tag buffers isn't hard:
diff --git a/src/admin/index.js b/src/admin/index.js
index c1d65db..44e4979 100644
--- a/src/admin/index.js
+++ b/src/admin/index.js
@@ -44,6 +44,9 @@ const findTopicPartitions = async (cluster, topic) => {
     .sort()
 }

+/**
+ * @returns {import("../..").Admin}
+ */
 module.exports = ({
   logger: rootLogger,
   instrumentationEmitter: rootInstrumentationEmitter,
diff --git a/src/protocol/encoder.js b/src/protocol/encoder.js
index 6275879..5d00245 100644
--- a/src/protocol/encoder.js
+++ b/src/protocol/encoder.js
@@ -280,6 +280,17 @@ module.exports = class Encoder {
     return this
   }

+  writeVarUInt(value) {
+    const byteArray = []
+    while ((value & UNSIGNED_INT32_MAX_NUMBER) !== 0) {
+      byteArray.push((value & OTHER_BITS) | MOST_SIGNIFICANT_BIT)
+      value >>>= 7
+    }
+    byteArray.push(value & OTHER_BITS)
+    this.buffer = Buffer.concat([this.buffer, Buffer.from(byteArray)])
+    return this
+  }
+
   writeVarLong(value) {
     const byteArray = []
     let longValue = Encoder.encodeZigZag64(value)
diff --git a/src/protocol/requests/deleteGroups/v2/request.js b/src/protocol/requests/deleteGroups/v2/request.js
index 60a1eea..fbcff07 100644
--- a/src/protocol/requests/deleteGroups/v2/request.js
+++ b/src/protocol/requests/deleteGroups/v2/request.js
@@ -13,7 +13,7 @@ module.exports = groupIds => ({
   apiVersion: 2,
   apiName: 'DeleteGroups',
   encode: async () => {
-    return new Encoder().writeArray(groupIds.map(encodeGroups))
+    return new Encoder().writeArray(groupIds.map(encodeGroups)).writeVarUInt(0)
   },
 })

diff --git a/src/protocol/requests/listGroups/v3/request.js b/src/protocol/requests/listGroups/v3/request.js
index 5001f49..895b8ee 100644
--- a/src/protocol/requests/listGroups/v3/request.js
+++ b/src/protocol/requests/listGroups/v3/request.js
@@ -1,7 +1,15 @@
-const requestV2 = require('../v2/request')
+const Encoder = require('../../../encoder')
+const { ListGroups: apiKey } = require('../../apiKeys')

 /**
  * ListGroups Request (Version: 3)
  */

-module.exports = () => Object.assign(requestV2(), { apiVersion: 3 })
+module.exports = () => ({
+  apiKey,
+  apiVersion: 3,
+  apiName: 'ListGroups',
+  encode: async () => {
+    return new Encoder().writeVarUInt(0)
+  },
+})

(rough, don't commit this!)
The problem is that tagged fields are a huge can of worms, and the point of having a Kafka 2.4 docker-compose setup isn't to bring support for all and any 2.4 feature, but just to provide a test bed. So, I'll add a commit here to remove these two requests, and simply use the older versions that do not have a tag buffer.

.... and that works and makes Azure happy! :)

Great work figuring that out. Just reading the KIP gave me a headache. 😅 If you fix the conflict in the package.json, we can merge this.

Rebased on master for the last time, ready to go :)

Rebased on master for the last time, ready to go :)

😅 Until I merged your other PR and caused you to have to update your branch again.

That's a very nice problem to have :)

FIY kafka 2.4 introduced https://issues.apache.org/jira/browse/KAFKA-9478 this causes quite abit of headache in our production even though this issue is quite rare.
Symptoms:
Kafka consume group stop rebalancing so when you try to connect with the same consumer group kafkajs stuck in waiting for JoinGroup request as kafka does not respond anything.
I don't think it affects this PR in any way though 😄


Long time for request

Hello guys! I need a help, I have a server up and running, but it's taking a long time to respond to requests, 30/40 seconds. Another problem is that Qrcode is often not shown. Can someone give me a tip?
Thanks

usinadeideia,
Can you explain your problem in detail like server configuration, OS, application you are trying to run?

Hi
O use AWS Instance, 2GB. RAM, Ubuntu 17.
Error: update your Chrome
Use: Chatbot (https://www.sacplus.com.br)
Em 11 de dez de 2018 2:19 AM, "geek4teck"<EMAIL_ADDRESS>escreveu:
usinadeideia,
Can you explain your problem in detail like server configuration, OS,
application you are trying to run?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mukulhase/WebWhatsapp-Wrapper/issues/514#issuecomment-446067054,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALHNzBjGlSF_D5yw9Lq2bWWqN5uR3clfks5u3zI9gaJpZM4Y9lnT
.