Add support for asdf-vm installed via MacPorts

I have checked that this feature is not already implemented

[x] This feature does not exist

Use case
Currently asdf-vm is supported for various install methods including HomeBrew but not via the MacPorts https://www.macports.org/ system.
Description
Ruby installs from asdf-vm should be detected if asdf-vm was installed via MacPorts.
Implementation
In src/ruby/asdf.ts various search paths are present, e.g. for Homebrew https://github.com/Shopify/ruby-lsp/blob/bbc1ccb4a047040c9c09a32ce5ae19b66aa10157/vscode/src/ruby/asdf.ts#L60-L68.
Support for MacPorts can be added by adding the additional default path for asdf-vm from MacPorts in the following way:
      vscode.Uri.joinPath(
        vscode.Uri.file("/"),
        "opt",
        "local",
        "share",
        "asdf",
        scriptName,
      ),

Thank for you for the suggestion.
If we were to implemented this, then we'd probably want MacPorts supported for all version managers on Mac, to avoid inconsistency. It may be helpful to introduce some abstraction for Homebrew/MacPorts to reduce duplication.
In the meantime, you can set a custom path for MacPort's adsf installation:
https://shopify.github.io/ruby-lsp/version-managers.html#custom-activation
(If anyone is interested in implementing this, please reach out to discuss your approach first).


 I've read issues regarding:

Images turning black
Checkboxes converted to numbers...

But not checkboxes turned black.
This issue occurs in Chrome 40,
This is not in an issue in FF 35, Safari 8.
FF & Safari

Chrome

When reporting an issue, please make sure that you read (especially the first paragraph) https://github.com/mozilla/pdf.js/blob/master/CONTRIBUTING.md. I'm also quoting the most relevant part:

[...] provide more details about the issue: link to the PDF, location in the PDF, screenshot, browser version, operating system, PDF.js version and JavaScript console warning/error messages.

I cannot link to the PDF in question as that would violate the FERPA law governing the document in question. Other details I can provide:

Location in PDF all pages
Screenshots included in original comments
Browser versions included in original comment
Console messages:
PDF 6eec7551c2b48bd34b8bf48e9d2a5 [1.6 Mac OS X 10.9.5 Quartz PDFContext / FileMaker Pro] (PDF.js: 1.0.712)

If you render the PDFs yourself, can't you create one with dummy content so we can use that as a test? Otherwise there is not much we can do about this issue I'm afraid...

Here is a heavily redacted version of the original file. All meta-data has been kept, and the sections containing the offending checkboxes have been kept.
https://www.dropbox.com/s/euwvi3jrxl03ctf/pdf-js-issue-redacted-2.pdf?dl=0

@asinner That PDF is just a set of images (bitmaps), and useless for debugging.
Could you share the tool that was used to create this PDF or find/create a similar PDF?
An alternative way to help is to debug the issue yourself (about 20 - 60 minutes, depending on whether you follow through to the last step):

Enable the debugging tools: https://github.com/mozilla/pdf.js/wiki/Debugging-PDF.js (set pdfBugEnabled to true, and append #pdfBug=all to the URL, then press Enter, focus the URL and press Enter again (or perhaps #pdfBug=all&disableWorker=true to make sure that the whole application is single-threaded).
When the stepper shows up, try to find the operator range that paints the checkbox. A binary search is quite effective.
After identifying the operator list, try to match the operator with code in PDF.js, e.g. by searching for the operator name in src/. Once you've found the relevant area, put JavaScript breakpoints (via Chrome's developer tools), and check whether the logic in PDF.js looks fine.
If PDF.js seems to be ok, this might be a bug in Chrome (canvas). Try to create a minimal test case and report the bug at https://crbug.com/new. See https://github.com/mozilla/pdf.js/issues/5043#issuecomment-48972506 for instructions on debugging canvas.

If you don't want to debug yourself and cannot share any PDF, send me a mail to see how we can proceed further (e.g. a remote debugging session).

Since this issue appears to be identical to #5932, and given that the "test-case" provided here is just an image of the problematic PDF file (compared to #5932, which has working test-case), I'm closing this issue as a duplicate.


Readability and branching Improvements

Description
There are several commits in this PR that improve code readability and reduce branching done by the CPU.
I would suggest going through each commit individually and then looking at the entire file as a whole.
Local test steps
I have run the test suite using "pytest tests" and they all pass. I have not altered the functionality of any code.
PR Acceptance Checklist

[✅] Unit tests passing.
[ ] Integration testing
[ ] CHANGELOG.md updated
[ ] Documentation updated (if needed).

@danielfromearth I read the contributor guidelines thoroughly and I am not sure if I actually need to add new tests or modify the changelog. I am using the standard test suite since I am not changing the input/output of the code. If anything should be added to the changelog, I'd be happy to do it :)

📚 Documentation preview 📚: https://ncompare--264.org.readthedocs.build/en/264/

Hi @kokroo, this looks great!
Adding to the changelog would be helpful, like this:
- Readability and branching improvements ([#264](https://github.com/nasa/ncompare/pull/264)) ([**@kokroo**](https://github.com/kokroo))

Hi @kokroo, if you can update the changelog soon, then we can merge this and get it in the next, 1.12.0, release!

@danielfromearth Hey Daniel,
I am sorry I did not respond sooner. Somehow GitHub notifications don't get to my e-mail reliably.
I added a line in the changelog under "changes". The tests are still passing even after merging the latest changes.
I have another PR in the works :)
Cheers and happy holidays!


metrics setup

Setting up a few basic app metrics
Setting web metric port to 9000 and worker metric port to 9001. Refer PR

should an env label be also added? eg stage, prod etc?

Add GRPC request metrics with latency and kafka, consul request metrics with latency


feat: added doc name to doc dropdown selection

Fixes: #360
Changes:
added the navigated doc page name to docs dropdown
Screenshots of the change:

live url: https://apisix-website-navigation.netlify.app/

cc @Yiyiyimu @juzhiyuan

@iamayushdas Cool! Thanks a lot!!! 🚀
Found one problem is that APISIX and dashboard page still got their own links on the sidebar, others are good to me

@iamayushdas Cool! Thanks a lot!!! 🚀
Found one problem is that APISIX and dashboard page still got their own links on the sidebar, others are good to me

Your wlcm,
Yes that will be removed by there origin repo. Will do it

That's a good feature!!


Message size on mobile

There are a few problems with message sizes on mobile:

The time is too small to read
The first few messages are very small, but then it corrects itself after a few.

If you rotate the device, all of them show with the same (big) font size.

Duplicate of #15


Using Distance and Bearing method of creating a line with Mils will not accept values over 360 - ArcGIS Pro

When creating a line from distance and bearing and using mils, you should be able to enter a value up to 6400. Currently it only accepts values 0-360.

@pHill5136  i found this specifically on 1.4.1, let me know if you need me to start reaching back and seeing if it happens elsewhere (i'm assuming it does). Also, i felt like the undesirable behavior, and how to reproduce is pretty straight forward, let me know if you want more description or specific repro steps

please verify pr: https://github.com/Esri/distance-direction-addin-dotnet/pull/380

you can now enter a value over 360 for mils, checked to make sure that you are still limited to 360 with degrees


test webhook. Update README.md

/run-pull-e2e-kind-basic
/run-pull-e2e-kind-across-kubernetes

/close just a pull request for testing purpose.

/close
just a pull request for testing purpose.


Improve matmul perfomance (x3 faster)

The test code
before
% python matmul.py
matmul_cupy,     1, 0.094999, 0.092819
matmul_cupy,     2, 0.088792, 0.086078
matmul_cupy,     4, 0.090728, 0.088081
matmul_cupy,     8, 0.092195, 0.089526
matmul_cupy,    16, 0.089893, 0.087249
matmul_cupy,    32, 0.091620, 0.088820
matmul_cupy,    64, 0.091853, 0.088415
matmul_cupy,   128, 0.094509, 0.088805
matmul_cupy,   256, 0.099513, 0.088722
matmul_cupy,   512, 0.126376, 0.089967
matmul_cupy,  1024, 0.217337, 0.090513

after
% python matmul.py
matmul_cupy,     1, 0.028923, 0.027409
matmul_cupy,     2, 0.031349, 0.027895
matmul_cupy,     4, 0.031553, 0.028089
matmul_cupy,     8, 0.031442, 0.027990
matmul_cupy,    16, 0.031346, 0.027880
matmul_cupy,    32, 0.031649, 0.028074
matmul_cupy,    64, 0.032772, 0.028425
matmul_cupy,   128, 0.040503, 0.028247
matmul_cupy,   256, 0.065268, 0.028831
matmul_cupy,   512, 0.108619, 0.028902
matmul_cupy,  1024, 0.192309, 0.028819

Jenkins, test this please.

Jenkins CI test (for commit bb5cb66a3526b905ed4bf779510716f96dd2be96, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit bb5cb66a3526b905ed4bf779510716f96dd2be96, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit bb5cb66a3526b905ed4bf779510716f96dd2be96, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

jenkins, test this please.

Jenkins CI test (for commit bb5cb66a3526b905ed4bf779510716f96dd2be96, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

jenkins, test this please.

Jenkins CI test (for commit bb5cb66a3526b905ed4bf779510716f96dd2be96, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit bb5cb66a3526b905ed4bf779510716f96dd2be96, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit ebdc87bfb538fc88dca2e8725ff2925cae8ca1e1, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit c41eb8d45c90d39209d4350002bb86f400b7a660, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

jenkins, test this please.

Jenkins CI test (for commit c41eb8d45c90d39209d4350002bb86f400b7a660, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

jenkins, test this please.

Jenkins CI test (for commit c41eb8d45c90d39209d4350002bb86f400b7a660, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

jenkins, test this please.

Jenkins CI test (for commit c41eb8d45c90d39209d4350002bb86f400b7a660, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Please merge #1894 first.

jenkins, test this please.

jenkins, test this please.

Jenkins CI test (for commit 9765490fe3647eb3352e165e6109049d64dc34e9, target branch master) succeeded!


Improved test support

Support creation of log markers.
Split from PR #66, part 3

Oh, I can't do it using the GH interface. Can you squash those @theseion ?

Damn, you're fast 😄. Sure, squash ahead.

Apparently, I don't have write access to the repo, so no, I can't perform the merge / squash, sorry.

 The last one fbca174 can be squashed with bdfb4b7.


Wrong transpile when class extends Object

This doesn't compile correctly when transpiling to ES3
const ClassA = (baseClass) => class extends baseClass {
	constructor() {
		super();
	}

	methodTest() {
		alert("Works! :)");
	}
}

let instanceA = new ClassA(Object);
instanceA.methodTest();

closure-compiler --language_out=ECMASCRIPT3 --js=bug.js

instanceA loses it's class methods.
instanceA.methodTest is not a function

See compiled output https://closure-compiler-debugger.appspot.com/#input0%3Dconst%2520ClassA%2520%253D%2520(baseClass)%2520%253D%253E%2520class%2520extends%2520baseClass%2520%257B%250A%2509constructor()%2520%257B%250A%2509%2509super()%253B%250A%2509%257D%250A%250A%2509methodTest()%2520%257B%250A%2509%2509alert(%2522Works!%2520%253A)%2522)%253B%250A%2509%257D%250A%257D%250A%250Alet%2520instanceA%2520%253D%2520new%2520ClassA(Object)%253B%250AinstanceA.methodTest()%253B%26input1%26conformanceConfig%26externs%26refasterjs-template%26CHECK_TYPES%3Dtrue%26TRANSPILE%3Dtrue%26CLOSURE_PASS%3Dtrue%26PRESERVE_TYPE_ANNOTATIONS%3Dtrue%26PRETTY_PRINT%3Dtrue
  var input0$classdecl$var0 = function() {
    return baseClass.call(this) || this;
  };
  $jscomp.inherits(input0$classdecl$var0, baseClass);
  input0$classdecl$var0.prototype.methodTest = function() {
    alert("Works! :)");
  };

Created Google internal issue http://b/139671578

@davispuh the repro you sent does not work uncompiled either, as arrow functions like ClassA cannot be used with new. The compiler also warns about this.
In the Chrome DevTools:
const ClassA = (baseClass) => class extends baseClass {
        constructor() {
                super();
        }

        methodTest() {
                alert("Works! :)");
        }
}

let instanceA = new ClassA(Object);
instanceA.methodTest();

VM36:11 Uncaught TypeError: ClassA is not a constructor
    at <anonymous>:11:17

Closing this issue for now, unless you have an example that works uncompiled then fails compiled.

Opps, trying to reduce example code I made mistake.
This code works in browser but not with transpile.
const ClassFactoryA = (baseClass) => class extends baseClass {
	constructor() {
		super();
	}

	methodTest() {
		alert("Works! :)");
	}
}

let ClassA = ClassFactoryA(Object);
let instanceA = new ClassA();
instanceA.methodTest();

https://closure-compiler-debugger.appspot.com/#input0%3Dconst%2520ClassFactoryA%2520%253D%2520(baseClass)%2520%253D%253E%2520class%2520extends%2520baseClass%2520%257B%250A%2509constructor()%2520%257B%250A%2509%2509super()%253B%250A%2509%257D%250A%250A%2509methodTest()%2520%257B%250A%2509%2509alert(%2522Works!%2520%253A)%2522)%253B%250A%2509%257D%250A%257D%250A%250Alet%2520ClassA%2520%253D%2520ClassFactoryA(Object)%253B%250Alet%2520instanceA%2520%253D%2520new%2520ClassA()%253B%250AinstanceA.methodTest()%253B%26input1%26conformanceConfig%26externs%26refasterjs-template%26CHECK_TYPES%3Dtrue%26TRANSPILE%3Dtrue%26CLOSURE_PASS%3Dtrue%26PRETTY_PRINT%3Dtrue

Ok, thanks for the report!
The compiler has special logic here to handle transpiling extends Object, but it fails in cases like yours when the extends clause is not the literal name Object.
Working example: https://closure-compiler-debugger.appspot.com/#input0%3Dclass%2520ClassB%2520extends%2520Object%2520%257B%250A%2520%2520constructor()%2520%257B%250A%2520%2520%2520%2520super()%253B%250A%2520%2520%257D%250A%250A%2520%2520methodTest()%2520%257B%250A%2520%2520%2520%2520alert(%2522Works!%2520%253A)%2522)%253B%250A%2520%2520%257D%250A%257D%250Anew%2520ClassB().methodTest()%253B%26input1%26conformanceConfig%26externs%26refasterjs-template%26CHECK_TYPES%3Dtrue%26TRANSPILE%3Dtrue%26CLOSURE_PASS%3Dtrue%26PRESERVE_TYPE_ANNOTATIONS%3Dtrue%26PRETTY_PRINT%3Dtrue
Failing example: https://closure-compiler-debugger.appspot.com/#input0%3Dconst%2520baseClass%2520%253D%2520Object%253B%250Aclass%2520ClassA%2520extends%2520baseClass%2520%257B%250A%2520%2520constructor()%2520%257B%250A%2520%2520%2520%2520super()%253B%250A%2520%2520%257D%250A%250A%2520%2520methodTest()%2520%257B%250A%2520%2520%2520%2520alert(%2522Works!%2520%253A)%2522)%253B%250A%2520%2520%257D%250A%257D%250A%250Anew%2520instanceA().methodTest()%253B%250A%250A%250A%26input1%26conformanceConfig%26externs%26refasterjs-template%26CHECK_TYPES%3Dtrue%26TRANSPILE%3Dtrue%26CLOSURE_PASS%3Dtrue%26PRETTY_PRINT%3Dtrue

The issue with the failing example is that calling Object.call(this) inside an ES5 constructor doesn't return an object of the subclass (like this is), but rather a newly constructed Object instance.  Maybe this is yet another case of ES5 classes extending an ES6 class not working correctly?

@blickly Thanks for the reminder of why we had to special-case things for Object.
This bug is just infeasible to fix.
Since Object.call(this) doesn't behave like a normal constructor would, the compiler must
know that the superclass is Object in order to transpile the call to super() correctly.
Unfortunately, it's not possible for the compiler to know this for all possible cases.
If you really must indirectly extend Object like this, the workaround is to instead extend an empty class.
let ClassA = ClassFactoryA(class {});


ReferenceError: url is not defined

Running linux ubuntu node:
alfred@alfred-SATELLITE-C55-A-1ND:~/centritest/server$ node -v
v4.1.1

I created test.js:
Client = require("jscent")

var options = {
    url: "http://localhost:8000",
    secret: "e2199fe7-ebad-4124-a8fa-d6c95653bcd8"
}

var c = new Client(options)

c.publish("alfred", "test", function (err, resp) {
    console.log(err, resp)
})

when I ran node test.js I got an error that url is not defined.
/home/alfred/centritest/server/node_modules/jscent/lib/requests.js:16
    handleResponse(err, url, res, callback);
                        ^
ReferenceError: url is not defined

in jscent/lib at line 16 I modified url to config.url
request["post"](params, function(err, res) {
    handleResponse(err, config.url, res, callback);
  });

Now I get:
alfred@alfred-SATELLITE-C55-A-1ND:~/centritest/server$ node test.js
null { body: null, error: null, method: 'publish' }

Hello! Thank you very much for opening this, seems you are first using Centrifugo with NodeJS:)
Pushed a fix, made new release 0.1.1 - should work now.

Hi Fzambia. I updated dependency and know I can run the code. Thanks for fixing so quick.


rad resource list lists resources that failed to deploy

Bug information
I tried to do two deployments with two different names for a resource. The first one failed and the second one succeeded. Probably the first one had Failed provisioning state in the data store.
When I run rad resource list extenders -a demo-app I get both resources even though one of them doesn't exist on the cluster. Please see the screenshot below.
Steps to reproduce (required)

Deploy the same bicep file with two different names for the same resource
One of them MUST fail
See that the rad resource list lists both of them

Observed behavior (required)

Desired behavior (required)
The resources that failed to deploy shouldn't be listed. We need a Provisioning State check in the CLI.
OR we need to have the State of the resource shown as another column of the list table.
Workaround (optional)
System information
rad Version (required)
Operating system (required)
Additional context
AB#9302

Should we have state just in the rad resource * commands? @rynowak

That sounds like a big improvement. I'm in favor


cargo fmt

Does this also work with cargo fmt ? Like this:
cargo fmt --all -- --check
If so, maybe adding an example of that also might be helpful, since this seems to require special JSON arguments.

I updated the README to indicate that cargo fmt is not supported currently. cargo +nightly fmt -- --emit=json can emit JSON-formatted output (only on nightly), but deviates significantly from the rest of the cargo JSON scheme, so that won't work without further changes.


Secrets in ecosystem.json

I'm currently working on deployments with pm2, and so far I really like how it works. There is one thing I don't get though. Generally, you keep application secrets out of your source control (api keys, database passwords, etc), and inject them into the application with environment variables. Cool, that makes sense.
The ecosystem.json file is a nice way to define the application,environments and variables to go with each for deployments. However, when I run the deploy command, I get this error: Configuration file ecosystem.json is missing. Action canceled. I presume this is because my ecosystem.json file is not on the remote server, as I haven't committed it into git.
How is this reconciled? Am I missing something? Are most people just committing their ecosystem.js and not worrying about any potential security issues with their secrets being included, or is there another way to inject the ecosystem file into the remote system? It'd be nice if the deploy command just pushed the file up or something.

I'm also highly interested in others's opinions about this matter, mostly because I'm also having this problem.

Quote!

Commit your ecosystem file but store your sensitive data elsewhere (either ENV or in a file somewhere else on the machine, like the /etc folder)
I use https://github.com/indexzero/nconf to accomplish this. This example is a bit overly complex because I'm also using cson (coffee style json). But the gist is...

load from defaults file (commited into git)
load from locals file if exists (not committed into git)
load from /etc file if exists (only for deployments)
load from ENV vars if exist (currently not using them as I find the files easier, but you could)

nconf = require 'nconf'
CSON = require 'cson'
fs = require 'fs'
_ = require 'lodash'

CONFIG_FILE = '/etc/my-app-config.cson'

loadCsonConfig = (path) ->
  if fs.existsSync( path )

    # throw the error if config is bad!
    # nconf doesnt throw it so we do this first
    file_config = CSON.parseFileSync path
    if file_config instanceof Error
      throw file_config

    nconf.file
      file: path
      format:
        stringify: CSON.stringifySync
        parse: CSON.parseSync

# use nconf's in-memory store
nconf.use 'memory'

# args take precedence, then env vars
nconf.argv().env()

# Load overrides and sensitive config values
loadCsonConfig( "#{__dirname}/local.cson" ) # for dev
loadCsonConfig( CONFIG_FILE )               # for deployments

if process.env.NODE_ENV == 'test'
  loadCsonConfig( "#{__dirname}/test.cson" ) # for testing

# loads default values, dev tokens, local urls, etc
# we must load defaults last due to a bug in nconf
nconf.defaults( CSON.parseFileSync("#{__dirname}/defaults.cson") )

There are a few other modules out there that would let you accomplish something similar.

So that means that you environment variables are always on a file somewhere on the machine?
Doesn't that defeat the purpose? (Honest question)

Maybe I'm missing something, but the important thing seems to me that your sensitive info isnt committed into version control.
To me, storing the production tokens in ENV or a file buried somewhere on the machine seem about equivalent, as long as your machine is secure (the file isnt accessible).

While that makes sense, it seems to me, then, that using the ecosystem.json other than a place to state hosts for deployment, is pretty useless then, and that's because you need to add the ecosystem.json to git to be able to make deployments, but at the same time, you can't use it to declare env variables because those should not go into git... it's kinda conflicting...
I keep thinking that I'm missing something about this...

That makes sense to me @theoephraim, and I agree that is the important thing...But @Couto's point is why I opened this issue. I can easily find a way around this to get my configuration onto the server, but it seemed like the point behind the ecosystem.json file was to make deployments super easy, where you can just add servers and other config details, type one command, and all of the servers will receive the deployment quickly and easily.
If I have to login to each machine to update the environment variables, the ecosystem file isn't really helping me very much.

You can create private git repo with ecosystem.json and instance_key and add it to optionalDependencies

I'm posting this to future users, or to help with the discussing and solutions.
I had some luck with git-crypt, to encrypt the ecosystem.json and post a binary blob into the repository.
Since all developers have GPG keys, all I had to do was to create an extra key for the server (without passphrase to avoid complications and make scripting a bit easier... although that comes with a weaker security obviously) and set the post-deploy command to unlock the ecosystem.json
so my ecosystem.json deploy section becomes something like:
"development" : {
  "user" : "deploy",
  "host" : "[REDACTED URL]",
  "ref"  : "origin/develop",
  "repo" : "git@[REDACT REPOSITORY URL]",
  "path" : "/srv/[REDACTED PROJECT NAME]/api",
  "post-deploy" : "source ~/.profile && npm install && npm run db:migrate:up && git crypt unlock && pm2 startOrRestart ecosystem.json --env development"
}

I have no idea if this is most correct solution or not, but at least allows me deploy with pm2, and I don't have to leave API keys in plain sight.

Any news on this? How to pass environment variables to the server without simply adding them to the commited ecosystem.json?

If you really want to have your secure config values within your repo but keep them safe, you could use something like https://github.com/jed/config-leaf

It would be nice to have some kind of solution for being able to use env vars with keys while not keeping them in git repo.

So far I just create a ecosystem.sample.json and just clear the critical parts.
After the deployment I just copy/rename the sample file to ecosystem.json and fill the important sections local and on the server by hand. Maybe not the best solution but For me the easiest and fastest.
{
      "name" : "AY-Bot",
      "script" : "dist/server/index.js",
      "env" : {
        "NODE_ENV" : "development",
        "COMMON_VARIABLE" : "true",
        "SESSION_SECRET": "",
        "WIT_ACCESS_TOKEN": "",
        "VERIFY_TOKEN": "",
        "PAGE_TOKEN": ""
      },
      "env_production" : {
        "NODE_ENV" : "production",
        "SESSION_SECRET": "",
        "WIT_ACCESS_TOKEN": "",
        "VERIFY_TOKEN": "",
        "PAGE_TOKEN": ""
      }
    }

We're currently following a two-repo approach. One repo for code, and another private one just for deployment. The 'ugly' thing here is that all maintenance tasks must be launched from the deployment repo, as all running settings and env vars are stored there.
Still, having two separated repos has helped us maintaining a cleaner repo for our main app, as well as giving us the option to transform the deployment repo into a microservice, easy to scale and integrate with our CI tools.

Hi guys, I am concerned with the matter as well. Thanks for sharing to everyone.
Thinking of using http://pm2.keymetrics.io/docs/tutorials/capistrano-like-deployments but haven't much time to explore, if someone has achieved something tidy please share 👍
@theoephraim approach seems too complicated for my simple mind 😅  , @vitorbaptista is simpler but I don't wanna mess up with encription.
For now what I do is to have dedicated "deploy" repo and do stuff like this: (just assuming the deploy repo is cloned and up to date on the deployment machine ofc, you might add a git pull anyway)
      "post-deploy": "ln -s ~/git/infraestructure/parse/* .; source ./mongo_auth.sh; npm install; pm2 startOrRestart ecosystem.json --env production",
On my development machine I have a ln -s ../infraestructure/ecosystem.json . as well.

I found this thread after reading about the Serverless Framework and how that allows you to keep variables ready for deployment in an encrypted file.  You provide the password to that encrypted file as a parameter to the serverless deploy command.  I thought this would be nice to have when launching our apps with PM2.

Also running into this exact question. It seems weird to me that the config file couldn't be copied up when you run a deploy setup, via scp or something?
Like, it's a whole deployment orchestration tool, I'm confused why there's not a way to deploy secrets without committing to github, made me feel like I'm just missing something. Glad to see I'm not alone?

 This seems super weird to me, I think I am not gonna use it.

Agree that could be absolutely easier to have a way to avoid commit the fileecosystem with its secrets to the version control.
For now I solved with a separated file in another location in the server and calling it when post-deploy .

Is there a solution to this? I too thought my deployment was going to be painless until I got the 'ecosystem.config.js not found' error.

A good solution I've found is to combine pre-deploy-local and post-deploy to copy over the full ecosystem file (with secrets) and then remove it afterward:
`
...
"pre-deploy-local" : "scp ecosystem.json user@server:'/home/node' ",
"post-deploy" : "git checkout dev && npm install --silent && pm2 startOrRestart ~/ecosystem.json --env development && rm ~/ecosystem.json
...
`

Do it like this:
'post-deploy': 'source .env && npm install --production && pm2 reload ecosystem.config.js --env production --update-env'
And put your vars in .env with the format: VAR=VALUE

If using something like nconf:

You can specify a config file to parse through command line args or env vars.

  nconf.argv()
   .env()
   .file({ file: nconf.get('config') });

# And start it like:
node app.js --config /etc/my-app/config.json

Encrypt your configuration.
Export environment variables from a file local to your deploy server, just like what was mentioned above.
Use a remote config repository/datasource like redis or etcd.

The easiest solution I came up with is to use dotenv (https://github.com/motdotla/dotenv/).

Store a file named .env somewhere on your server containing your env variables. Edit or deploy this file however you like, the point being it's not part of your repo or ecosystem.json.
Add a step to your post-deploy command in scosystem.json to copy this file into the current deployment folder. Here is mine:

...
"post-deploy": "npm install; cp ~/.env .env; pm2 startOrRestart ecosystem.json"
...

At the top of your main app file, require dotenv with a relative path

const path = require('path')
require('dotenv').config({path: path.join(__dirname, '.env')})

and boom, all your variables defined in your .env file are now available in process.env

@skylarmb I'm doing something similar to this.
Just skipping the step of having to make an env file in the server, by using ssh to copy the local env file to the remote host in the pre-deploy-local command.
Something like :
scp ~/.env ${user}@${host}:~/.env
Or use rsync.
But it would be nice if pm2 had some way to copy different secrets files depending on different hosts and envs. I have a workaround for that, but it complicates the ecosystem file with too much logic.

@rohit-smpx I like that solution! In our case the .env file does not exist on the machine we deploy from (a transient container in a CI/CD system), so having the file persist on the server is still best for us. If you are deploying from a machine that has access to the .env file your solution is definitely ideal

This is ridiculous.
If I have to copy the file myself before launching the pm2 command I can just log into the server and send the pm2 command there. Without this feature, pm2 deploy is absolutely useless.
Some people has suggested some smart solutions by using scp on the pre-deploy hook. This is nice if you want to copy the file to the remote server, but that is not my case.
To be honest, I don't understand why this is as it is, it is a limitation. If PM2 is able to run commands on a remote machine (which is basically what this deploy thing is all about) I don't understand why it can't just read the env variables locally, and launch a command with those env variables set as if you were typing them. Something like this:
NODE_ENV=production SECRET_KEY=asdffsdfsd pm2 start

Is that impossible?

@danielo515 I am not an expert on pm2, but what you are suggesting is that you pass all your local environment variables to the remote machine when you run a pm2 command? That seems like recipe for complete disaster and is probably not what you actually want if you really think about it.
Having your environment variable management decoupled from your process / log manager is a good thing. For example the machine that initiates the pm2 command may not have access to the appropriate environment variables in order to pass to the server (like in a CI/CD pipeline or deploying from a local machine). Also the way environment variables are managed is highly dependent on the setup of the application and infrastructure. Are you using Chef / Puppet? How are your env variables stored? Are your env variables in your Docker image? In an encrypted git repo or a KMS? In a third party tool? How are permissions granted for access to environment variables? etc.
I think overall the decision to have pm2 by default not be responsible for setting any environment variables encourages proper application architecture and doesn't break existing deployment processes. Whatever method you use for managing environment variables, just use pre-deploy hooks to set them up before pm2 runs. If you don't have an actual method of managing your environment variables, then persisting the .env file on the server or using scp like @rohit-smpx did is your easiest option.

@danielo515 I am not an expert on pm2, but what you are suggesting is that you pass all your local environment variables to the remote machine when you run a pm2 command? That seems like recipe for complete disaster and is probably not what you actually want if you really think about it.

Nope, that is not what I'm saying. Let me explain it with an example. Imagine an ecosystem.json like this:
module.exports = {
  apps: [{
    name: "myApp",
    script: "src/start.js",
    env: {
      PORT: 8080,
    }
  }]
}

then pm2 can read this file and execute the following on the server:
PORT=8080 node src/start.js

So my suggestion is to just use the variables defined on the ecosystem.json file and set them explicitly.
Probably there are way better ways of doing this, but for simple cases having this as an extra option will save someone's day.

Also the way environment variables are managed is highly dependent on the setup of the application and infrastructure.

O sure, but in my case I'm using just PM2, and I don't want to use anything else

@danielo515 I'm not entirely sure what you are asking for here but you can already define env vars before starting an application. Your "hypothetical" ecosystem file would work just fine.
You can even define them by deploy environment. Here's an example configuration.
{
  "apps": [
    {
      "name": "my-api",
      "script": "app.js",
      "max_memory_restart": "512M",
      "exp_backoff_restart_delay": 100,
      "wait_ready": true
    }
  ],
  "deploy": {
    "production": {
      "user": "myuser",
      "host": "prod.myapi.com",
      "ref": "origin/master",
      "repo": "git@gitlab.intra.net:group/my-api.git",
      "path": "/opt/group/my-api",
      "post-deploy": "npm ci --production && pm2 reload deployment.json --env production",
      "env": {
        "NODE_ENV": "production",
        "PORT": "8080",
		"DB_URI": "mssql://prod.db.uri:7878/db"
      }
    },
    "qa": {
      "user": "myuser",
      "host": "qa.myapi.com",
      "ref": "origin/develop",
      "repo": "git@gitlab.intra.net:group/my-api.git",
      "path": "/opt/group/my-api",
      "post-deploy": "npm ci --production && pm2 reload deployment.json --update-env --env qa",
      "env": {
        "NODE_ENV": "qa",
        "PORT": "8070",
		"DB_URI": "mssql://localhost:1234/db"
      }
    }
  }
}

thanks, @nfantone, that is exactly what I was looking for!
Now, this is not an issue anymore for me, thanks again.

I've read about security issues with having a .env file on your production server, with 3rd party packages gaining access to it.
Also, what about nefarious server admins or developers seeing all your secret/private keys? I'm not sure the best way to handle this. I've been Googling all morning too.
Any thoughts on this stuff?

@nfantone According to your solution, we need to push deployment.json file into git repository. Right?

@kavishatalsania Not really, no. My answer was directly related to @danielo515 problem and not addressing security concerns - or anything but the topic in question, to be honest.
In terms of your own question, what I would typically do is, depending on the project's complexity and requirements, set a config file with default values and push it along with everything else to the repository (defaults would typically point to a "local" or "dev" environment, aimed at enhancing DX and nothing else) - then either:

Have a config file per environment, locally in your server. You don't check in this file into your repository, you rely on it existing under some known path (like /etc/yourapp/app.conf).

This has the disadvantage that @imkane pointed out regarding "malicious" admins, developers and third-party modules being able to read your config. It's a very valid concern, but to be honest, this also applies to anything else. If you encrypt your settings and store "secrets", whoever/whatever holds the super-secret-key can pretty much manipulate your config the way they want. We rely on so much third-party, open source software nowadays, that these vulnerabilities are really hard to control. This is specially true for JS projects.
No solution is perfect: your security is only as good as the people handling it.

Have some sort of external config repository. There are many known services that handle this pretty well: etcd, ZooKeeper, AWS SSM Keystore or even Redis. You then inject these configuration dependencies when starting the application (if they are runtime config values) or building it in whatever your deployment/build pipeline is.

If you are using some kind of serverless or clustered setup (AWS, GCP, Azure, Kubernetes, et al.), chances are you already have one these systems at your disposal.

@nfantone Thank you for your response. Yeah, I can create config file per environment locally in my server and use some external config repository. But is there no way PM2 read secrets from my local ecosystem.config.js file before deploying project and read from there?

Would it possible to do something like $ PM2_ENV='SECRET="xyzzy"; OTHER_SECRET="quux"' pm2 deploy production?
As someone mentioned here, one wouldn't want pm2 to copy the entire environment from the local machine to the remote machine on deployment. So instead, I propose a specific pm2 environment variable for the local machine which contains a list of environment variables to be set and used upon running pm2 on the remote machine.

thanks, @nfantone, that is exactly what I was looking for!
Now, this is not an issue anymore for me, thanks again.

Hey, this might be a bit random because I am in a similar situation. This worked for you in the sense that you put your keys in your config file (in the git/vcs) and it deployed using that. Or that you managed to inject the keys in your config (on the computer you are using to deploy something remotely) into the remote deployment build? I'm trying to do the latter and well no success.

thanks, @nfantone, that is exactly what I was looking for!
Now, this is not an issue anymore for me, thanks again.

Hey, this might be a bit random because I am in a similar situation. This worked for you in the sense that you put your keys in your config file (in the git/vcs) and it deployed using that. Or that you managed to inject the keys in your config (on the computer you are using to deploy something remotely) into the remote deployment build? I'm trying to do the latter and well no success.

The first one. I just wanted to not have to put the env variables on the target machine, or a config file on the target machine.
What I would do nowadays is either:

Use ansible to deploy
Use a template to generate the config before deploying with pm2 (you can also use ansible for this)

@danielo515 is on the right track. An even simpler approach that I have used in the past is, if you trust your app server and users, just place something like an .env file in your project's root directory and enable/read it after deploying.
This obviously doesn't scale, but for simple setups it solves the problem without hassle.

@danielo515 thanks for mentioning ansible, didn't know about this technology @nfantone I'll most likely do a temporary fetch and delete instead of keeping the file. I also see some justification in a repo with encrypted blobs (John Resig brought this up in a blog) until it's worth setting something up like Jenkins.

On the same issue, no matter how we encrypt our passwords and keys if we end up passing them with env variables, everything is written in plain text at ~/.pm2/dump.pm2.
Is there any way to truly hide all this sensitive information?

On the same issue, no matter how we encrypt our passwords and keys if we end up passing them with env variables, everything is written in plain text at ~/.pm2/dump.pm2.
Is there any way to truly hide all this sensitive information?

Well, at the end the information needs to live in plain text at some place. I mean, sure you can encrypt it, but then where do you store the decrypt key? In plain text somewhere, or in memory somewhere. The correct thing to do is to set proper permissions of that file, so only admins can read it.
The only way to not have the info at some place is to start the process manually providing the required credentials as options and make sure the command is not registered in bash history.

This definitely complicates the deployment, it would be very nice to have this functionality built-in without having to use .env files.

after going through the discussion above the conclusion is instead of using pm2 save , for the time being the workaround could be as follows:
on Linux cron, on Windows scheduler/service to run the command manually when the system restarts
pm2 start ecosystem.js --env prod
a quick fix should be made instead of storing the secrets as plain text in  ~/.pm2/dump.pm2 reading from .env file, a way to provide the envFile


Add VEP

VEP functions, pretty much the same code as in AIP.

Add jobs to run VEP in parallel,
Add Job to gather VEP results into a hail Table using Query Batch backend,
Add Vep pipeline stage.

I'm planning to remove that and just import from AIP.

Without thinking about it too much, I quite like the idea of removing the annotation code from AIP and importing from cpg-utils 🙃


error with latest firmware for CC1352P_2

after flashing the CC1352P_2_20201026.zip, i cant controll any devices and after a reboot zigbee2mqtt was not starting anymoe.
Got the error:
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: Zigbee2MQTT:error 2020-11-01 17:07:19: Error while starting zigbee-herdsman
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: Zigbee2MQTT:error 2020-11-01 17:07:19: Failed to start zigbee
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: Zigbee2MQTT:error 2020-11-01 17:07:19: Exiting...
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: Zigbee2MQTT:error 2020-11-01 17:07:19: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: at ZStackAdapter. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: at Generator.throw ()
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: at rejected (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: npm ERR! code ELIFECYCLE
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: npm ERR! errno 1
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: npm ERR<EMAIL_ADDRESS>start: node index.js
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: npm ERR! Exit status 1
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: npm ERR!
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: npm ERR! Failed at the<EMAIL_ADDRESS>start script.
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: npm ERR! A complete log of this run can be found in:
Nov 01 17:07:19 zigbee2mqttpi01 npm[635]: npm ERR!     /home/pi/.npm/_logs/2020-11-01T16_07_19_329Z-debug.log
Nov 01 17:07:19 zigbee2mqttpi01 systemd[1]: zigbee2mqtt.service: main process exited, code=exited, status=1/FAILURE
Nov 01 17:07:19 zigbee2mqttpi01 systemd[1]: Unit zigbee2mqtt.service entered failed state.
Nov 01 17:07:19 zigbee2mqttpi01 systemd[1]: zigbee2mqtt.service holdoff time over, scheduling restart.
Nov 01 17:07:19 zigbee2mqttpi01 systemd[1]: Stopping zigbee2mqtt...

I could flash mine without a problem.

Probably a port/usb communication problem not related to the firmware. Check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start (the issue probably occurred because you have to disconnected the adapter).

I might have the same issue. I can flash the "source routing" firmware (which I'm currently using) no problem but if I try this new firmware I just get a red flashing light and no adapter detected. Is that what you are experiencing @mpuff


Do not squeeze depth dim

#12 : I included z_c, z_l and z in the dimensions not to squeeze in trim_and_squeeze(). I also had to remove a .squeeze() in load_xorca_dataset (l 383) because that basically made trim_and_squeeze() ineffective for aux_files. I am not sure whether it has other effects...

Codecov Report

Merging #13 into master will increase coverage by 0.14%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
+ Coverage   78.47%   78.62%   +0.14%
==========================================
  Files           3        3
  Lines         144      145       +1
  Branches       24       24
==========================================
+ Hits          113      114       +1
  Misses         30       30
  Partials        1        1

Impacted Files
Coverage Δ

xorca/lib.py
98.23% <100%> (+0.01%)
: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 5cfec90...c0022ee. Read the comment docs.

E       AttributeError: module 'xorca.orca_names' has no attribute 't_dims'

Travis errors read like there is some non-scalar object returned by the new functions we defined.

Thanks @jk-rieck !


Prototype of new architecture, without work manager API.

Starts the server inside the application process.
Defers only task workers to a foregrounded service.

This looks pretty good to me and I have a branch merging it with some of the stuff we've glued together downstream: endlessm/kolibri-installer-android#20. I also add a bit of refactoring, and my thought is I'll split that into a different pull request once we have this sorted out.
Using the newest build of Kolibri from the develop branch, the workers service seems to be doing its thing: worker-related stuff appears in logcat without any obvious errors. With that said, it does run into an error importing content, but I think that's just a problem in Kolibri, not here. (It gets a 404 requesting /device/api/device_channel/000409f81dbe5d1ba67101cb9fed4530/?include_fields=total_resources%2Ctotal_file_size%2Con_device_resources%2Con_device_file_size%2Cnew_resource_count%2Cnew_resource_total_size&1652997798744=1652997798744, and then throws an exception here: https://github.com/learningequality/kolibri/blob/1fd1fc08c92eae64634126a757c9e1af442870c2/kolibri/core/assets/src/api-resources/task.js#L14-L16).

Oh yes, absolute latest develop is completely broken on the frontend for tasks - because of some of the Task API refactoring that I alluded to earlier. I am fixing it as we speak.

Going to merge this for now, we can make more updates as we go.


Run PHPStan with several versions of PrestaShop

In order to detect potiental backward compatibility issues with PrestaShop in the future, we run PHPStan with several versions of PS.
This PR contains 2 commits reverting changes, which is expected as proof.

Regarding the error reported with PHPStan, I decided to not check older version that <IP_ADDRESS>. These were the first 1.7 versions, which we're ready for production use.

Thanks for review


Resizing windows with a mouse

Will try to do that later this week! Would it be possible to make it so mouse-resizing updates the tree as well? (Just curious if that's even possible)
Originally posted by @eramdam in https://github.com/LGUG2Z/yatta/issues/3#issuecomment-807343951

@eramdam I think this should be possible by listening and reacting to the right WinEvents, I'll take some time soon to read through the MSDN and windows-rs docs to see which events could be used to trigger the same handlers as the yattac resize commands.

@eramdam https://github.com/LGUG2Z/yatta/commit/ba1e3f3e192d685fcab9215451af6c50159c90a8 a build with both the yattac resizing commands (and some bugfixes) and mouse-driven resizing for you to try out.

@eramdam ba1e3f3 a build with both the yattac resizing commands (and some bugfixes) and mouse-driven resizing for you to try out.

Works great! I did notice some issues with the manual resize but I'll post them in the related issue

Closed with #9.


Licence key not recived

Describe the question
Hi Mike,
I haven't received the  license key from
could you please send it to me?
thanks!

license server went down randomly for some reason, should be all good now! thanks <3


allow installing slurm without all of osg-tested-internal (SOFTWARE-3…

…347)

One of the tests appear to have timed out when setting up the initial docker container. Merging.


[v1.2] Auto-completion for application keywords

Complete auto-completion for application keywords.
TO DO: Support other user inputs.

Pull Request Test Coverage Report for Build 85

84 of 88 (95.45%) changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 92.316%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/recipe/ui/SuggestionsPopUp.java
32
33
96.97%

src/main/java/seedu/recipe/ui/util/AutoCompletionUtil.java
5
6
83.33%

src/main/java/seedu/recipe/ui/util/TextInputProcessorUtil.java
31
33
93.94%

Totals

Change from base Build 72:
0.1%

Covered Lines:
1682

Relevant Lines:
1822

💛  - Coveralls


Build datarobot v3.1.0:

version increased and sha256 updated.
skipping for python 3.11 as there is no typing-extensions support for it.
build script updated.
host dependencies updated.
run dependencies updated.
test section updated.
dev_url added.

abs.yaml will be added after review to upload this package to the Snowflake channel.

Closing this PR. The upstream license does not permit us to (re)distribute this package.


Add MIT license to package.json

Allows license to be read programatically.

:+1:, we use this to check licenses in our Atom Shell-based app

Integrated in bf004e141b0fa42e3d75c32971a117508a4135c6


unsupported version 0x01. If possible, set the switch to use one of the versions [4]

Hello, just wanted to let you know that this looks extremely promising for issuing bandwidth control on physical networks as well.  For right now, I am just trying to make it through your README but am encountering an OpenFlow protocol problem.  When I try
ryu-manager Switch.py
or
ryu-manager Rest.py
I encounter the error that the title of this issue shows.  Do you have any idea how I may resolve this issue?  I am a little perplexed because I thought Ryu adapted to any OpenFlow version and when I run these files without opening mininet first I still get this error.  Any insights on how to get past this?

Hello,
I think the problem is that you are using a switch which doesn't support OpenFlow 1.3. The error log says that you are using OpenFlow 1.0.
In the example topology I use CPqD Switch, which support both: OpenFlow 1.3 and meter tables.
I recommend you checking the switch that you are using to run the script.
Regards.

Isn't the switch in theory whatever the mininet topology [topo.py] says it
is?  [Isn't this tutorial entirely virtual networking?]  So if I am using
this topology then why am I getting the error?
-Jason
On Thu, Aug 25, 2016 at 11:50 AM, Rene Delgado<EMAIL_ADDRESS>wrote:

Hello,
I think the problem is that you are using a switch which doesn't support
OpenFlow 1.3. The error log says that you are using OpenFlow 1.0.
In the example topology I use CPqD Switch, which support both: OpenFlow
1.3 and meter tables.
I recommend you checking the switch that you are using to run the script.
Regards.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RDelg/OF-BW-Control/issues/5#issuecomment-242437615,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUMgy1eboW-D-sEdqW3CK6D8bByGrhaeks5qjbm_gaJpZM4JtM_d
.

Did you use the CPdQ switch instead of mininet's virtual OpenFlow switches
because you were unable to get them to perform the tasks you wanted?
On Thu, Aug 25, 2016 at 1:06 PM, Jason Palmer Loux<EMAIL_ADDRESS>wrote:

Isn't the switch in theory whatever the mininet topology [topo.py] says it
is?  [Isn't this tutorial entirely virtual networking?]  So if I am using
this topology then why am I getting the error?
-Jason
On Thu, Aug 25, 2016 at 11:50 AM, Rene Delgado<EMAIL_ADDRESS>wrote:

Hello,
I think the problem is that you are using a switch which doesn't support
OpenFlow 1.3. The error log says that you are using OpenFlow 1.0.
In the example topology I use CPqD Switch, which support both: OpenFlow
1.3 and meter tables.
I recommend you checking the switch that you are using to run the script.
Regards.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RDelg/OF-BW-Control/issues/5#issuecomment-242437615,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUMgy1eboW-D-sEdqW3CK6D8bByGrhaeks5qjbm_gaJpZM4JtM_d
.

I used cpqd because it has the meter table implemented, which I use to control the bw.
If you are using the topo.py to create the topology,  I don't know why this error happen, maybe the UserSwitch implemented in mininet is not cpqd anymore (this project is about 1 year ago), so check that. (Ovs doesn't support meter tables)
Regards.


--only-log-changed

Related to #1805
Output of restic version
restic 0.12.1 compiled with go1.16.6 on linux/arm
What should restic do differently? Which functionality do you think we should add?
Only log changed files. When doing restic backup --verbose=2, i'd like to be able to add --only-log-changed to it so it does not log unchanged.
What are you trying to do? What problem would this solve?
Currently my logs are filled with a slurry of unchanged, this is not very helpful when disseminating what files were actually stored, at a later date.
Note: i know that #1805 is supposed to fix this, but i have not seen much change in it, and i think that this opt-in logging exclusion would help my use-case quicker.

You could probably use restic [...] | grep -v "^unchanged " to filter out these log lines. Or use the json output and filter it using jq.
Isn't the --only-log-changed option exactly what has been suggested as log level 2 in #1805?

That's harder to do when using restic in a systemd service file, i'm trying to clean up some of my logs with this.

The cleanest solution there would be to use a wrapper script for restic to filter the log output.
I'm closing this as duplicate of #1805 as it is necessary to do some planning on how to control the log output to avoid creating a mess of command-line options.


Unit test for DarkThemeToggle

Is your feature request related to a problem? Please describe.
The component is missing its unit test.
Describe the solution you'd like
Implement the unit test to the component.
Describe alternatives you've considered
n/a
Additional context
n/a

Ill take this


Grammar: Remove hack detecting options after filter expressions

The removed hack was intended to improve error messages in programs where the author used an option after a filter expression in read, which is illegal:
read file level = 'error' -file '~/my-data.json'

In these cases, the -file part was originally mistakenly considered a full-text term, parsed as such, and the compiler later produced an error like this:
Error: file is not defined

The hack improved such messages. However, it also lead to many wrong error messages in cases of options used in legal position but with syntactically invalid values (such as unterminated strings):
read file -file '~/my-data.json

In these cases, the parser produced a message:
Options must be specified before filter expressions.

This is clearly wrong because there are no filter expressions in play here.
The hack was triggered in cases like this because the thing (-file '~/my-data.json) couldn’t be parsed as an option with a value, so the parser tried to parse it as a filter expression, but at that moment the
hack was triggered because the thing looked like a beginning of an option.
Rather than “hack the hack” against situations like this I chose to remove the hack completely, which changes the message in the last example to:
Expected ";", "|" or expression but "\"" found.

This makes much more sense.
The swapped options and filter expression case now produces the original, less than ideal error message. I think this trade-off is worth it because this case occurs much less often than the case of invalid option values.
Ultimately, this will get properly resolved by either of (a) allowing mixing options and filter expressions freely and (b) changing free-text search syntax to be less implicit (to that -file wouldn't be a legal
full-text term syntactically).

@bkutil
@dmehra This should resolve your (rightful) complaint that “these days i get this error for pretty much any typo”.

This is clearly an improvement, as the 'original' error, together with error location info gives much better context.
+1, let's wait for @dmehra to review and give her ACK.

I'm good with this as described, but haven't been able to repro my original problem, I'm getting a different issue when I try - for unterminated quotes, we seem to keep going very far down the flowgraph before emitting the error. Example:
juttle -e "read -file file '/tmp/github_data_from_es.json | reduce events = count(), actors = count_unique('actor_login') by repo_name | sort events -desc | head 10 | put activity_per_actor = Math.round(events/actors)"

<input>:1:6:
   1:read -file file '/tmp/github_data_from_es.json | reduce events = count(), actors = count_unique('actor_login') by repo_name | sort events -desc | head 10 | put activity_per_actor = Math.round(events/actors)
          ^
Expected identifier but "-" found. code (JUTTLE-SYNTAX-ERROR-WITH-EXPECTED)

Since missing quote termination is a common typo, is it possible to have special logic for it in the syntax checker, that will emit a specific error "unterminated quotes"? I cannot think of a valid Juttle that would contain those. I briefly thought that we could check for quotes closing before the next pipe symbol, but no, that breaks in cases like juttle-powered input; but surely quotes need to close by the end of the program.
This is not related to the current PR - I can't find a way to test what you've fixed, leaving the merge decision to you. (Should there be a new unit test?)

@dmehra I don’t think new unit tests are warranted, this is more like a removal of a feature. (To be more precise: No new unit tests are warranted when considering the current level of parser testing, which is almost zero. We should probably increate parser test coverage, but it has some opportunity cost, plus the parser is exercised a lot by other tests and users. It also wasn’t a source of too much bugs historically. So maybe the current state is OK for the time being.)
The other things are unrelated to this PR, but mostly fixable and certainly worth filing separate issues.


Update - project_filter Component

tasks - 2024.01.28

Update project_filter_v0.1.0

update the project_filter component
@output :package: project_filter_v0.1.1

worklog

feedback
Initialized the issue

proposals


web-multi-logger doesn't work

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

Electron Forge Version:

6.0.0-beta.47

Electron Version:

v7.1.10

Operating System:

MacOS 10.15.2

Last Known Working Electron Forge version::

Any version released prior to the upgrade of xterm to 4.x

Expected Behavior
web-multi-logger works
Actual Behavior
web-multi-logger fails to load, unable to resolve resources mapped under /xterm/*
To Reproduce
Install the latest version of electron-forge from clean, and attempt to view the logger
Additional Information
Looks like this was broken with this PR from dependabot
https://github.com/electron-userland/electron-forge/pull/1151
xterm did a package restructure and built out a plugin system so we'll need to fixup the way we resolve xterm assets for express and probably add a test validating those assets are present
The following workaround works for folks with yarn
  "resolutions": {
    "@electron-forge/**/xterm": "3.14.5"
  }

I've released beta 48. Thanks for your patience!


[Deploy] Zalo

Service
Plugin for Zalo, a popular messenger and video call platform in Vietnam
Link to your repository
https://github.com/JohnnyBui/franz-zalo-plugin
Additional Information
Working

@JohnnyBui : Just did it by my own and ready for submitting to Franz but you already did that for over a month. Good work :D

@quangpdt lol but it's never merged

You need to fix the styling for small window size and the badge count of muted chats

@stanleynguyen: You need to check the abilities of Franz first before asking to fix something.

@quangpdt I did it myself before cos I made a recipe for Zalo 🙄

@quangpdt since they are pretty simple to fix, I dont want to fork his repo and make a PR. That would be too troublesome

There is also one issued in 2017 https://github.com/meetfranz/plugins/issues/98


⚠ API Platform (ETU) has degraded performance

In 9ab091c, API Platform (ETU) (https://api-etu.six-group.com/healthcheck) experienced degraded performance:

HTTP code: 503
Response time: 15517 ms

Resolved: API Platform (ETU) performance has improved in 24fdcb9.


MAUI Blazor Hybrid support

Is it possible to get this working on .net maui blazor hybrid?
I tried it and desktop seems to be just fine, though mobile support isn't that good.
Is this a Monaco issue or do you think it could be fixed with css? (Because I think most of the issues are actually positioning and styling related)

Unfortunately, Microsoft does not support mobile browsers for Monaco Editor. See here.


Some minor issues

Firstly, thanks for creating this which is a useful adjunct for those of us who like to program in Go :)
Just three minor issues I've encountered so far.
Firstly, when I'm using Wren-cli, if I import a library module like this:
import "/someModule" for SomeClass

then Wren-cli would look for the file "./someModule.wren" and find it because I always copy such modules to the same directory as the startup script.
However, that's not happening with WrenGo. Either I have to use the library's full name (which is awkward if that in turn imports other modules) or I need to change the configuration like so:
cfg := wren.NewConfig()
cfg.LoadModuleFn = func(vm *wren.VM, name string) (string, bool) {
    if !strings.HasPrefix(name, ".") {
        name = "." + name
    }
    if !strings.HasSuffix(name, ".wren") {
        name += ".wren"
    }
    return wren.DefaultModuleLoader(vm, name)
}
vm := cfg.NewVM()

Although this is not a big problem, it would be nice if the DefaultModuleLoader function could do it for us.
Secondly, I've noticed that when I set up a Go function to represent a static foreign method in Wren, 'parameters' includes an extra parameter (the first one) which is a *wren.Handle and is possibly a meta-class reference or similar. This had me puzzled for a while and it would be useful if there could be a mention in the docs about the extra parameter being passed.
Finally, I couldn't figure out how to wire up a foreign property in Wren i.e. one with no following parentheses. Again no big problem as I can always add the parentheses but if there is a way to do it perhaps you could elucidate.

Ok sorry for not responding to this sooner.
For the first issue, I guess I find this more of a matter of personal preference. I think I like having module names without a precededing directory or a ".wren" to refer to built-in modules (that would be bundled into the executable) while actual paths can load external files.
There was a problem with your solution (at least while using WrenGo at the time this issue was probably opened).
import "/someModule" for SomeClass
import "./someModule" for SomeClass
import "/someModule.wren" for SomeClass
import "./someModule.wren" for SomeClass

Since each of these import module names are all different, they would all be treated differently and each class would not match. To solve this I added functionality for the WrenResolveModuleFn function just now which allows you to modify the module name before it is passed to LoadModuleFn. I decided not to create a DefaultModuleResolver though because I still don't think it will work as nice as I want it to, at least without importing more librarys from go like "strings" or "filepath".
As for the other two issues, I finally added a more comprehensive example to the README.md on how to do more complex stuff with foreign functions.


fix: typo in 10_install_ubuntu.md

fixing typo in 10_install_ubuntu.md
Testing Instructions
no testing requiered

now it should work :-)

now it should work :-)

Yep, the commit message passes, but the DCO is failing because the commit isn't signed off.
You can fix it with this command and the force push:
git commit --amend --no-edit --signoff


[general api | usage reports] Disabled metrics, not part of the plan, are included in the response

Metrics with a max_value of 0 (aka. disabled / no limit) that are not part of the plan, are included in the response.
No limit metrics that actually are part of the plan are filtered out correctly.
RESPONSE
<?xml version="1.0" encoding="UTF-8"?>
<status>
	<authorized>true</authorized>
	<plan>API Dev Sandbox</plan>
	<usage_reports>
		<usage_report metric="hits" period="day">
			<period_start>2016-03-30 00:00:00 +0000</period_start>
			<period_end>2016-03-31 00:00:00 +0000</period_end>
			<max_value>500</max_value>
			<current_value>0</current_value>
		</usage_report>
		<usage_report metric="customMetric" period="minute">
			<period_start>2016-03-30 04:53:00 +0000</period_start>
			<period_end>2016-03-30 04:54:00 +0000</period_end>
			<max_value>0</max_value>
			<current_value>0</current_value>
		</usage_report>
		<usage_report metric="customMetric2" period="minute">
			<period_start>2016-03-30 04:53:00 +0000</period_start>
			<period_end>2016-03-30 04:54:00 +0000</period_end>
			<max_value>0</max_value>
			<current_value>0</current_value>
		</usage_report>
		…
	</usage_reports>
</status>

Is there actually a more appropriate place to submit these kind of API bugs?

@g10 yes, the usage_reports field in the response to authorize or authrep calls always contains all the metrics or methods for which there are any limits.
The reasoning is that usage_reports contains all the possible rate limits that a request could trigger. That way it is easy for you to check which one or which ones have been reached whenever authorization is denied for a request.
Metrics that are disabled are considered internally as having a limit of 0 requests, that is why you see them there. It is useful to have them there since
The best way to reach us for any product related questions or bug reports is to send us an email at<EMAIL_ADDRESS>Feel free to send us any questions to that address.

tnx for the feedback, I'll take it to support


unknown error: ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.

Hi Team,
I have updated the GitHub ssh key but still edp tool is failing to import project in Applications.
I am using same key from my local and I am not facing any issue with GitHub pull/clone.
Command used to generate the ssh-key
ssh-keygen -t rsa-sha2-512
output
Generating public/private rsa-sha2-512 key pair.
ERROR
unknown error: ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.
EDP version: 2.6.8
Impact:
All applications are failing to provide branch names and also the integration to vcs and status is shown as red.
In pipeline section, I am not able to see any of the pipelines and displaying as no applications available.
Do let me know if I am missing any changes.
Thanks in advance.

Resolved


Ring and Motion does not work

Hi, i've fresh installed this plugin and tested for a while but i do not get any ring or motion feedback.
I've also tested the info function and this gives me the expected output in the debugging view.
What i try to do is to give me a debugging message when i press the ring button or use the motion sensor. Do you know what i'm doing wrong? Maybe it's a bug because of the authentication is working because of i do get feedback from the info function.

Fond the issue. It's about the docker container where node red is running. It seems that it does not pass through the needed ports.

Yep, would have been my first question. Docker bridge networks do not allow UDP broadcasts to go through. I have plans to move the whole communication on http (register a http event in Doorbird). But nothing scheduled yet.


Add volume management

Add volume management - API to change volume of playback outside Nuvola Player, e.g. MPRIS interface and command-line interface.
+1 from @fecosnippets (a Nuvola Patron)
+1 from @zepp (a Nuvola Patron)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

All required APIs have been added to the master branch (Nuvola 4.4.15). Remaining tasks:

[ ] Write documentation for maintainers.
[ ] Integrate volume management in my streaming services
[ ] Ask maintainers of the other services to integrate volume management.

Closing in favor of #424.


cgutils.py error:  TypeError: 'IntType' object is not callable

When I try and import Librosa, the traceback I get shows there's an error happening with Numba. I've looked over the other issues but I can't seem to find this exact issue so I'm opening this as a new issue. Please let me know what I can try to solve the problem.
I'm running this on a Google Cloud Platform Ubuntu 16.04 VM.
/home/nscozzaro/librosa/librosa/util/decorators.py in ()
7 from decorator import decorator
8 import six
----> 9 from numba.decorators import jit as optional_jit
10
11 all = ['moved', 'deprecated', 'optional_jit']
/home/nscozzaro/anaconda3/lib/python3.5/site-packages/numba/init.py in ()
10
11 # Re-export typeof
---> 12 from .special import typeof, prange
13
14 # Re-export error classes
/home/nscozzaro/anaconda3/lib/python3.5/site-packages/numba/special.py in ()
2
3 from .typing.typeof import typeof
----> 4 from .parfor import prange
5
6 all = ['typeof', 'prange']
/home/nscozzaro/anaconda3/lib/python3.5/site-packages/numba/parfor.py in ()
20
21 import numba
---> 22 from numba import ir, ir_utils, types, typing, rewrites, config, analysis
23 from numba import array_analysis, postproc, typeinfer
24 from numba.typing.templates import infer_global, AbstractTemplate
/home/nscozzaro/anaconda3/lib/python3.5/site-packages/numba/ir_utils.py in ()
10 import numba
11 from numba.six import exec_
---> 12 from numba import ir, types, typing, config, analysis, utils, cgutils
13 from numba.typing.templates import signature, infer_global, AbstractTemplate
14 from numba.targets.imputils import impl_ret_untracked
/home/nscozzaro/anaconda3/lib/python3.5/site-packages/numba/cgutils.py in ()
20 voidptr_t = int8_t.as_pointer()
21
---> 22 true_bit = bool_t(1)
23 false_bit = bool_t(0)
24 true_byte = int8_t(1)
TypeError: 'IntType' object is not callable

Thanks for the report. Please could you post some precise steps to replicate what you are seeing?
Many thanks.

The only step I did was "import librosa" in jupyter notebook.
I solved the problem by pip installing librosa=0.4.3
I'm not sure why it's throwing that error with the librosa 0.5.1 version

@pajevic thanks for posting too.
I'm struggling to reproduce this. I have an OSX machine, Anaconda python, and have pip installed librosa==0.4.3 and Numba 0.36.2, and I also have a clean env with just Numba 0.36.2, both of which import numba fine. Please could one of you or @nscozzaro provide the exact steps to reproduce?
I also wonder if there is something problematic in the pip dependency resolution, do you know which combinations of Numba and llvmlite you have installed? These packages are released in lock-step and so Numba 0.36.2 should have llvmlite version 0.21.0.
Many thanks.

I ended up just using an older version of librosa which worked, I completed
my project, and now I've moved on so I unfortunately won't be able to
assist in the steps to reproduce this any more. Thank you for your help
though.
On Feb 7, 2018 4:32 AM, "stuartarchibald"<EMAIL_ADDRESS>wrote:

@pajevic https://github.com/pajevic thanks for posting too.
I'm struggling to reproduce this. I have an OSX machine, Anaconda python,
and have pip installed librosa==0.4.3 and Numba 0.36.2, and I also have a
clean env with just Numba 0.36.2, both of which import numba fine. Please
could one of you or @nscozzaro https://github.com/nscozzaro provide the
exact steps to reproduce?
I also wonder if there is something problematic in the pip dependency
resolution, do you know which combinations of Numba and llvmlite you have
installed? These packages are released in lock-step and so Numba 0.36.2
should have llvmlite version 0.21.0.
Many thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/numba/numba/issues/2658#issuecomment-363709801, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AOe00ehAkZd-Irc-CdsRYnK9TQ-PcXZQks5tSW2ygaJpZM4RJ1rN
.

Reproducing the error on my system is simple, just “import numba” will do it!
I tried pretty much all the versions of numba (and librosa) and only when I pip install numba with: pip install 'numba<=0.19'
does the error go away! Specifically, the latest version of numba that works on my system:
numba.version
'0.18.2'
but then it does not have jitclass, so it would be nice to resolve this problem.
This numba version works also with the latest librosa version (0.5.1, as well as 0.4.3, as was suggested to resolve this problem).
I will soon be installing anaconda and everything else from scratch on another Mac OSX computer, and will post if the problem there still persists.
From: stuartarchibald<EMAIL_ADDRESS>Reply-To: numba/numba<EMAIL_ADDRESS>Date: Wednesday, February 7, 2018 at 4:33 AM
To: numba/numba<EMAIL_ADDRESS>Cc: "Pajevic, Sinisa (NIH/CIT) [E]"<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [numba/numba] cgutils.py error: TypeError: 'IntType' object is not callable (#2658)
@pajevichttps://github.com/pajevic thanks for posting too.
I'm struggling to reproduce this. I have an OSX machine, Anaconda python, and have pip installed librosa==0.4.3 and Numba 0.36.2, and I also have a clean env with just Numba 0.36.2, both of which import numba fine. Please could one of you or @nscozzarohttps://github.com/nscozzaro provide the exact steps to reproduce?
I also wonder if there is something problematic in the pip dependency resolution, do you know which combinations of Numba and llvmlite you have installed? These packages are released in lock-step and so Numba 0.36.2 should have llvmlite version 0.21.0.
Many thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/numba/numba/issues/2658#issuecomment-363709801, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AExLCl43LzQIAhDungvl6Ixv_BtRc_4Gks5tSW2ygaJpZM4RJ1rN.

Just ran into this on armv7 where conda install -c numba llvmlite gets an ancient llvmlite version 0.7:
>>> import llvmlite
>>> llvmlite.__version__
'0.7.0.dev+21.gcda19bd.dirty'

(This is also confirmed on the website: https://anaconda.org/numba/llvmlite.) In particular, this is before https://github.com/numba/llvmlite/commit/eb745f3f4b9d1340b4fabed754e53b9f787b0816 was added (in 0.10), which leads to these errors when importing Numba.
Might be sensible to take down the old version of llvmlite for arm?

I need to push my more recent builds of llvmlite and numba for ARMv7 to the channel.  (At conference, so I can't get to my Raspberry Pi.)  They pass most unit tests, except for the handful of failing SVD-related linear algebra tests that Stuart is trying to figure out.

Observed this error again in a Debian Jessie machine with Python 3.4, will try to provide more details in a couple of days (hence leaving this as a self-reminder)

@Juanlu001 any update? thanks.

I tried to reproduce this again with no luck... In general installing numba on Debian Jessie + Python 3.4 is a bit tricky, because it requires the perfect combination of

llvm, llvmlite<0.6, numba<0.21, or
llvm-4.0, llvmlite<0.20, and numba<0.36.

However, despite my best efforts I could not go back to our previous failing state. Perhaps it was a bad pip version, an unfortunate pinning somewhere, or something else.

@Juanlu001 thanks, unless you object, I'm inclined to close this. It's seemingly hard to reproduce and is almost certainly down to using ancient packages. Numba now ships both linux-aarch64 and linux-armv7l conda packages which can also be pip installed.

is almost certainly down to using ancient packages

Definitely. +1 for closing

@Juanlu001 thanks. Closing.


sendKeys to TEXTAREA loses '/' and reverts string chunks

Running Protractor 1.4.0 on Ubuntu 14, Chrome 37 (Jenkins job).
When I send URL into <textarea></textarea> it seems like every 1st forward slash / encountered is causing the cursor to jump to the beginning of the line:
myElement.sendKeys("http://google.com");
myElement.getAttribute("value").then(function(val) {
  console.log(val);
});

I see in log:
 $ /google.comhttp:

I tried to sendKeys one by one while replacing the '/' with protractor.Key.DIVIDE:
$ http:google.com

It does not occur on <input type="text"/>, only on <textarea></textarea>.
Thank you.
Update 1
It is working correctly in Firefox (v31)

I'm going to close this as it It looks like this was fixed in Chromedriver 2.16, and protractor is on 2.20.
Please feel free to reopen if this is still an issue.

This issue still exists on chromedriver 2.32.

The bug also exists on chromedriver 2.26 on Mac Sierra 10.12.6 on Chrome 61.0.3163.100.


Moving NodeElement::press into waitFor.

The pressing of the node element when pressing a button should also be
surrounded by the waitFor method.
There is a scenario that is attempting to scroll to the bottom where a button is and then press it. What's happening is that at times the scroll is triggered, and the button is attempted to be pressed before the browser has gotten to the desired scroll area. This causes an exception to be thrown but since the $button->press() is outside the waitFor lambda, the button pressing is not re-tried.
The pressing of the button should also be included in a waitFor to try and recover from an error when this happens.
Issue: Medology/stdcheck.com#7989

Testing file changes were not found.
Paging @juanmrad to review the back-end work in this pull request!
Paging @Chekote to review the testing work in this pull request!

Is there not a way that we can more explicitly ensure the button is ready to be pressed, rather than brute force pressing it?

Please check your failing test. also just realized there is no testing on this.

I've gone ahead and fixed the test that failed.
There was no testing added on this since there's already an existing behat test that asserts the pressButton method passes whenever an item is interacted with outside of the viewport.  This change would just prevent that from intermittently failing if the button was interacted with before the scrolling finished which was what happened in the issue referenced:
Medology/stdcheck.com#7989

I've gone ahead and fixed the failing test.  Originally there was no testing since the issue is to resolve a possible intermittent failure that happened in the issue mentioned in the description.  I've now added a unit test to asserts that failure of the assertion added, doesn't allow the code to try and press the button found.


some resolution makes-Help Board Feed has issue to display on header links-icons.

All for 100% Zoom.  User need to Zoom out to see the unseen links/icons as work-around
Resolution	OS	                                                Browser	                                  Help Board Feed page
1024X768	Winddown 10/Mac 11.0                  Chrome 85/Firefox/Safari 	   Unable to see on see Join now , rating and global icon ..
1280X800	Winddown 10/Mac 11.0                  Chrome 85/Firefox/Safari	           no issue in English  but issue with other language such as Spanish
1366X765 or 1440X900 issue with Spanish language
Seem Resolution is mainly the issue, we don't have horizontal scroll so can't click on unseen header links/icons ==>use Zoom out as work-around

closed by mistake


shardingSphere 分片失败 读写分离失败

Cause: org.h2.jdbc.JdbcSQLSyntaxErrorException: Table "t_order" not found; SQL statement:
select * from t_order [42102-210]
; bad SQL grammar []; nested exception is org.h2.jdbc.JdbcSQLSyntaxErrorException: Table "t_order" not found; SQL statement:
select * from t_order [42102-210]] with root cause
org.h2.jdbc.JdbcSQLSyntaxErrorException: Table "t_order" not found; SQL statement:
select * from t_order [42102-210]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:521) ~[h2-2.1.210.jar:2.1.210]

I fixed your example at https://github.com/dynamic-datasource/dynamic-datasource-samples/pull/20 .


Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (64)

Hi Guys,
This happens when I try to run npm start. Any ideas? Tried to update gulp, npm and node.js.
Thanks!
Code:
$ npm start
><EMAIL_ADDRESS>start /Applications/MAMP/htdocs/ot5/wp-content/themes/OT_1.6
> gulp

[17:40:45] Requiring external module babel-register
[17:40:46] Loading config file...
[17:40:46] config.yml exists, loading config.yml
[17:40:46] Using gulpfile /Applications/MAMP/htdocs/ot5/wp-content/themes/OT_1.6/gulpfile.babel.js
[17:40:46] Starting 'default'...
[17:40:46] Starting 'build'...
[17:40:46] Starting 'clean'...
[17:40:46] Finished 'clean' after 2.16 ms
[17:40:46] Starting 'sass'...
[17:40:46] Starting 'webpack:build'...
[17:40:46] Starting 'images'...
[17:40:46] Starting 'copy'...
[17:40:46] 'sass' errored after 37 ms
[17:40:46] Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (64)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.7.2
    at module.exports (/Applications/MAMP/htdocs/ot5/wp-content/themes/OT_1.6/node_modules/gulp-sass/node_modules/node-sass/lib/binding.js:13:13)
    at Object.<anonymous> (/Applications/MAMP/htdocs/ot5/wp-content/themes/OT_1.6/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:14:35)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Object.require.extensions.(anonymous function) [as .js] (/Applications/MAMP/htdocs/ot5/wp-content/themes/OT_1.6/node_modules/babel-register/lib/node.js:152:7)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18)
[17:40:46] 'build' errored after 41 ms
[17:40:46] 'default' errored after 43 ms
[17:40:46] The following tasks did not complete: webpack:build, images, copy
[17:40:46] Did you forget to signal async completion?
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `gulp`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

OS & version: macOS 10.14
Node version (node -v) [Node v4+ is required] : v10.12.0
FoundationPress version (see line 3 in package.json): 2.10.4

Reinstalling git helped solve this.


certificate signed by unknown authority error

I'm having certificate problems using this tool. Guessing it is because it's not loading local ca-bundle or something like that?
$ k tree app pt-sak-consumer
Error: failed to fetch api groups from kubernetes: Get https://apiserver.xxx.no:14125/api?timeout=32s: x509: certificate signed by unknown authority

We use Kubernetes client-go, so I suspect it’s a problem with that. Does kubectl work?
Most clusters that have self signed certs gave their CA data in KUBECONFIG file (either hardcoded as a file ref).

kubectl works, had problems with helm 2, but helm 3 works.
No CA-data in the kubeconfig file, which I guess is the reason why tree doesn't work. It's a corporate computer.

I’ll keep this open, but my suspicion is that this is something client-go needs to fix since they set the tls.Config on the REST API client.

It may also be a problem with my computer/certificates, a colleague of mine tried, and it worked.


Allow Usage in Family Document

Added an If/Else statement to allow this node to work in a project
document or in a family document. This was by request of a user on the
Dynamo forums.
http://dynamobim.org/forums/topic/using-dynamo-in-family-templates/#post-39076

Nice catch @sixtysecondrevit  - I'll merge this in and add it to the next release.

You could try to further streamline it like so:

if doc.IsFamilyDocument : doc_create = doc.FamilyCreate
else : doc_create = doc.Create
for curve in curves:

detcurve = doc_create.NewDetailCurve(view, curve.ToRevitType())
elementlist.append(detcurve)

Will do, @dimven - thanks!

You both are truly the python masters. I gotta say, I'm learning a lot from
the both of you! Thank you!
On Thursday, February 18, 2016, Andreas Dieckmann<EMAIL_ADDRESS>wrote:

Will do, @dimven https://github.com/dimven - thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/CAAD-RWTH/ClockworkForDynamo/pull/90#issuecomment-185643186
.

--
-john p
http://sixtysecondrevit.blogspot.com/
https://github.com/sixtysecondrevit/RhythmForDynamo


Stored procedure results in invalid code-gen of primary key columns where not identity

The code-gen is invalid where the table contains a primary key column that is not considered identity (being self-generating). Also, always outputting RowVersion logic even where the table does not support.

Fixed. NuGet package Beef.CodeGen.Core version v4.1.18 published.


Doesn't work on Android devices anymore

Unfortunately this script doesn't appear to work anymore on Android devices. I've had reports from people on Android phones that they aren't able to swipe left or right to move to next image, and don't see any captions under the image anymore.

Android swiping works for me on https://feimosi.github.io/baguetteBox.js/ and I can see the captions too.
The amount of information you provide is staggeringly low. What browser are they using? Which Android version? What is an example url on which it's broken? Is it at all possible the problem is caused by your other JavaScript and not by this library?

It's been a year since I posted that, so, I don't know the exact version of Android they were using except that it was the "current" version for whatever phone they had at the time. They were using the default browser for Android which I believe is Chrome. A sample URL is this: https://www.makostudio.com/gallery/3028 I don't have an Android phone, so, can't test it out to find out what the problem is. There are a few other javascripts being loaded on this page, one being the Bootstrap 5.0 JS file, plus Masonry. The page works just fine on an iPhone and on a desktop browser (including in Chrome), it's only on Android that I'm told you can't scroll to the next photo by swiping, and the captions don't show. I'll try finding out what versions of Android and Chrome they are using and post that info because I reached out again and was told the problem still exists.


DataCollections cannot be converted to arrays due to incompatible constructor

Constructor must be compatible with base class.
TypeError : Hyde\Framework\Features\DataCollections\DataCollection::__construct(): Argument #1 ($key) must be of type string, array given, called in H:\monorepo\vendor\illuminate\collections\Collection.php on line 768

Proposed fix is to protect the constructor like in BaseFoundationCollection and add a static create method.

That adds a lot of complexity and confusion, might just be easier to override the toArray method...

Actually this breaks a lot of collection methods, but honestly, during my refactors this is becoming more of a facade, and the key is not read, so I think the constructor can be removed.


Realtime energy unavailable in b7 or  b8

Version of the custom_component
Version 0.1.0b8
Configuration
Realtime interval left blank or set to 3.
Debug Logger set as follows:
logger:
  default: info
  logs:
    custom_components.duke_energy_gateway: debug
    pyduke_energy.client: debug
    pyduke_energy.realtime: debug

Describe the bug
I had noticed this issue on b7 and had opted to continue running b6 where realtime energy usage was working at the time. I updated to b8 this morning after the patch for the API change. I'm seeing the same behavior in b8 as I observed in b7 where sensor.duke_energy_current_usage_w shows 'unavailable' and has not updated at the specified interval. I have tried leaving interval blank and also setting it to 3 (seconds), but it does not change. I do see two entries in the debug log for the realtime sensor, but I do not see any realtime updates as was in previous versions, only for today's usage. Rolling back to b6 restores realtime usage, but has the now outdated API references.
Debug log
2021-12-16 08:48:31 INFO (MainThread) [homeassistant.setup] Setting up duke_energy_gateway
2021-12-16 08:48:31 INFO (MainThread) [homeassistant.setup] Setup of domain duke_energy_gateway took 0.0 seconds
2021-12-16 08:48:31 INFO (MainThread) [custom_components.duke_energy_gateway]
-------------------------------------------------------------------
Duke Energy Gateway
This is a custom integration!
If you have any issues with this you need to open an issue here:
https://github.com/mjmeli/ha-duke-energy-gateway/issues
-------------------------------------------------------------------
2021-12-16 08:48:31 DEBUG (MainThread) [custom_components.duke_energy_gateway] Set up Duke Energy API clients
2021-12-16 08:48:31 DEBUG (MainThread) [pyduke_energy.client] Getting new OAuth auth
2021-12-16 08:48:34 DEBUG (MainThread) [pyduke_energy.client] Accounts to check for gateway (1): 'XXXXXXXX'
2021-12-16 08:48:34 DEBUG (MainThread) [pyduke_energy.client] Checking account XXXXXXXX' for gateway
2021-12-16 08:48:41 DEBUG (MainThread) [pyduke_energy.client] Meters to check for gateway (1): 'XXXXXXXX'
2021-12-16 08:48:41 DEBUG (MainThread) [pyduke_energy.client] Checking meter 'XXXXXXXX' for gateway [meter_type=ELECTRIC, is_certified_smart_meter=True]
2021-12-16 08:48:41 DEBUG (MainThread) [pyduke_energy.client] Getting new gateway auth
2021-12-16 08:48:42 DEBUG (MainThread) [pyduke_energy.client] Found meter 'XXXXXXXX' with gateway 'XXXXXXXX'
2021-12-16 08:48:42 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:48:42 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.297 seconds (success: True)
2021-12-16 08:48:42 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.duke_energy_gateway
2021-12-16 08:48:42 DEBUG (MainThread) [custom_components.duke_energy_gateway] Subscribed target for _RealtimeUsageSensor to dispatcher
2021-12-16 08:48:42 DEBUG (MainThread) [custom_components.duke_energy_gateway] Triggered real-time connect/subscribe async task
2021-12-16 08:49:12 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:49:13 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.765 seconds (success: True)
2021-12-16 08:49:42 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:49:43 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.886 seconds (success: True)
2021-12-16 08:50:12 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:50:13 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 1.087 seconds (success: True)
2021-12-16 08:50:42 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:50:43 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 1.082 seconds (success: True)
2021-12-16 08:51:12 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:51:13 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.611 seconds (success: True)
2021-12-16 08:51:42 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:51:43 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.896 seconds (success: True)
2021-12-16 08:52:12 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:52:13 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.761 seconds (success: True)
2021-12-16 08:52:42 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:52:43 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.719 seconds (success: True)
2021-12-16 08:53:12 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:53:13 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.467 seconds (success: True)
2021-12-16 08:53:42 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:53:43 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.485 seconds (success: True)
2021-12-16 08:54:12 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:54:13 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.838 seconds (success: True)
2021-12-16 08:54:42 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:54:43 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.910 seconds (success: True)
2021-12-16 08:55:12 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:55:13 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.865 seconds (success: True)
2021-12-16 08:55:42 DEBUG (MainThread) [pyduke_energy.client] Requesting usage between 2021-12-16T05:00 UTC and 2021-12-17T05:00 UTC
2021-12-16 08:55:43 DEBUG (MainThread) [custom_components.duke_energy_gateway] Finished fetching homeassistant data in 0.771 seconds (success: True)

b6 -> b7 brought in a new version of pyduke-energy that made sure connections were being made in an async safe manner, since the MQTT library's connect function blocks and I was seeing it take down the HA instance completely if the connect failed.
I'm surprised this caused it to totally break though. My best guess is that the connect is failing.
I'm actively working on trying to fix #39 which will have some improvements to this to detect stuck connects in the event of network outages. Perhaps this might also address this issue. I'll try to see if I can figure out what's going on in this case.

those changes I mentioned are in now for version v0.1.0b9. can you check that version and see if it is working for you?

It seems like there's a version issue in the MQTT library. That's provided by Home Assistant itself. What version of HA are you running?

Ah. That might explain it. I’m running Home Assistant 2021.10.0. I’ll check for updates and reply back here.

Updating HA fixed my issue. Thanks for your help diagnosing that. Everything’s looking good.

Good to hear, I didn't think about that being an issue. I'll update the min version of HA required shortly, probably 2021.11 is enough since it was working for me.