Implement a possibility to create multiple logger objects

Suggested by @chrisspiegl
Basically, the behavior of other plugins nowadays seems to be to provide a createLogger function as a named export.
This createLogger then builds the logger and also has a key install which would be used by the app.use to call with the app and possible options.
All this could then be used by the user in a plugins/logger.js to build their own logger which has the same preferences inside components and outside.
In the mean time, I basically did the same for myself with a bit of a workaround (wrapping the vuejs3-logger in it's own plugin createLogger 🙈.
Maybe the code below will be helpful (it's workaround):
import VueLogger from 'vuejs3-logger'

const isProduction = process.env.NODE_ENV === 'production'

export const options = {
  isEnabled: true,
  logLevel: isProduction ? 'error' : 'debug',
  stringifyArguments: false,
  showLogLevel: true,
  showMethodName: true,
  separator: ':',
  showConsoleColors: true,
}

function createLogger(options) {
  return {
    install (app, installOptions = {}) {
      options = {...options, ...installOptions }
      app.use(VueLogger, options)
      console.log(`INSTALLING THE LOGGER`)
      Object.assign(this, app.$log)
    }
  }
}

const loggerCreated = createLogger(options)

// outputs only the `{ install: … }` because at this point the logger is not installed and thus the `Object.assign` was not run. This however is also not possible to do any different way without going into the guts of the `vuejs3-logger` because the necessary function (`initLoggerInstance `) is currently `private`.
// console.log(`loggerCreated:`, loggerCreated)

export const logger = loggerCreated
export const log = loggerCreated

The improvement with official support of a createLogger function would solve all the issues and would make the logger available upon first call and not just after it actually was initiated with app.use.
Again, hope this helps and am looking forward to an update to this plugin 🌸.
Oh… and P.S.: hi from Germany 👍  just a few hundred km north from you 🚗 .
Originally posted by @chrisspiegl in https://github.com/MarcSchaetz/vuejs3-logger/issues/1#issuecomment-817264400

Originally posted: https://github.com/MarcSchaetz/vuejs3-logger/issues/1#issuecomment-817270130
Further findings: This time it actually worked 🙈. The logger is now accessible outside of components and can be loaded by simply doing import { log } from '@/plugins/logger' in my project.
Please note again, I am not proficient in Typescript so this is probably "ugly" for some 🙈.
Here is the function I added to the vue3-logger.ts file:
public createLogger(options: ILoggerOptions) {
    options = Object.assign(this.getDefaultOptions(), options);

    if (this.isValidOptions(options, this.logLevels)) {
      const $log = this.initLoggerInstance(options, this.logLevels);
      $log.install = function (Vue: any, options: ILoggerOptions) {
        Vue.provide('vuejs3-logger', $log);
        Vue.config.globalProperties.$log = $log;
      }
      return $log
    } else {
        throw new Error(this.errorMessage);
    }
}

And below is my plugins/logger.js file which loads and creates the logger.
I have not found a way to directly export the createLogger so that I can simply do a import { createLogger } from 'vuejs3-logger' for now. But maybe a official release will fix that and someone with more understanding can get that done 🥇 .
import VueLogger from 'vuejs3-logger/src'

const isProduction = process.env.NODE_ENV === 'production'

export const options = {
  isEnabled: true,
  logLevel: isProduction ? 'error' : 'debug',
  stringifyArguments: false,
  showLogLevel: true,
  showMethodName: true,
  separator: ':',
  showConsoleColors: true,
}

const loggerCreated = VueLogger.createLogger(options)

export const logger = loggerCreated
export const log = loggerCreated

@chrisspiegl As you mentioned, the feature of adding different loggers is very common in programming.
The implementation would be easy if I just added another loggerinstance with a different key.
For example:
createLogger(key: string, options: ILoggerOptions) {
  // Create logger instance
  Vue.provide(key, loggerInstance);
}

It then is possible to inject the logger into different components, classes, etc.
However the question is if this is desirable.
It needs to be checked if the performance suffers from to many loggers managed by the dependency injection system of Vue.
Another approach would be a createLogger-function which returns a local logger instance without providing it to the application.
class SomeClass {
  logger: Log

  constructor() {
    this.logger = createLogger({});
  }
]

Hi @MarcSchaetz, I think there are two separate things going on:

Multiple Loggers
Getting the Logger Instance globally simply by importing the plugin/logger where it got first initialized like the Vuex Store or the Vue Router.

1: Multiple Loggers
This would indeed be something that could be of interest as well, despite being my goal. Specifically for the purpose of namespacing loggers so they show more than just the function they were invoked out of.
2: Getting the Logger Instance
This is what I am after and what I think I achieved with the code shared above. The createLogger creates one logger, and provides the install function for the Vue app.use component. But at the same time it provides the already initiated logger and thus can be returned many times and with that bringing it into all kinds of systems (like the vuex store etc.)
I hope my description is good and understandable?
I am currently only after the 'injecting the one and only logger into all kinds of files 👍 .

Thank for you all :+1:! I've been working on providing a logger instance to an external js file for a couple of days. This really helps me a lot.
I'm also looking forward to an official release to provide these desired features.

@54mu3l Yes. Due to me not really working with Vue in the past, I simply forgot about the logger. I looked at it again and I'm optimistic on providing some update at the weekend.

@54mu3l @chrisspiegl  Please checkout commit 5b2dfd1 and give me your opinion on it.

Hi @MarcSchaetz, I saw the change however at this point in time I am not actively coding on any of my projects where I am using VUE. When I get back to that (I do not have a timeline at this point) I will also check this out.

@MarcSchaetz Thank you so much for your great work!
I had a look at your commit and checked out the project. At a first glance this looks good to me...
I think the best way for me to test this, would be within my vue project. Could you publish this branch as a next-version?
This would be a great help for me, since I simply could add (npm install vuejs3-logger@next) this change to my project.
Thank you!

Hi @54mu3l I just released the next tag on npm.

Hi @MarcSchaetz
Great, thank you!
I just did some tests:
First of all there seems to be a problem with the types in this release. I needed to manually move index.d.ts from the dist-folder to the types-folder. To be able to use import { createLogger } from 'vuejs3-logger';
After fixing this, I tried to use vuejs3-logger the same way I use vue-i18n (see code below).
Until now my code looked like this (in case you're wondering, I'm using quasar = just ignore the boot-stuff):
import { boot } from 'quasar/wrappers';
import { VueLogger } from 'vuejs3-logger';

const isProduction = process.env.NODE_ENV !== 'development';

const options = {
  isEnabled: true,
  logLevel: isProduction ? 'error' : 'debug',
  stringifyArguments: false,
  showLogLevel: false,
  showMethodName: false,
  separator: '|',
  showConsoleColors: false,
};

export default boot(({ app }) => {
  app.use(VueLogger, options);
});

Now my new code looks like this:
import { boot } from 'quasar/wrappers';
import { createLogger } from 'vuejs3-logger';

const isProduction = process.env.NODE_ENV !== 'development';

const options = {
  isEnabled: true,
  logLevel: isProduction ? 'error' : 'debug',
  stringifyArguments: false,
  showLogLevel: false,
  showMethodName: false,
  separator: '|',
  showConsoleColors: false,
};

const logger = createLogger(options);

export default boot(({ app }) => {
  app.use(logger);
});

export { logger };

The last line enables me to import the logger instance into other non-vue-js-files. (= exactly what I want 🥳)
==> There is only one big problem (using the code above): within a vue component $log is not defined
I used this temporary workaround to get it to work:
import { boot } from 'quasar/wrappers';
import { createLogger } from 'vuejs3-logger';

const isProduction = process.env.NODE_ENV !== 'development';

const options = {
  isEnabled: true,
  logLevel: isProduction ? 'error' : 'debug',
  stringifyArguments: false,
  showLogLevel: false,
  showMethodName: false,
  separator: '|',
  showConsoleColors: false,
};

const logger = createLogger(options);

export default boot(({ app }) => {
  // app.use(logger);

  app.use(VueLogger, options);
});

export { logger };

With this example I used two logger instances. One for within vue (with $log) and another one for the non-vue-stuff...

Btw this is how I'm doing the same thing with i18n:
import { boot } from 'quasar/wrappers';
import { createI18n } from 'vue-i18n';

import messages from 'src/i18n';

const i18n = createI18n({
  legacy: false,
  locale: 'en',
  messages,
});

export default boot(({ app }) => {
  // Set i18n instance on app
  app.use(i18n);
});

export { i18n };

Hey @54mu3l
Your workaround is actually the preferred way to use it as far as I implemented it.
const options = {
  isEnabled: true,
  logLevel: isProduction ? 'error' : 'debug',
  stringifyArguments: false,
  showLogLevel: false,
  showMethodName: false,
  separator: '|',
  showConsoleColors: false,
};

export default boot(({ app }) => {
  // This line internally calls createLogger(options) but also registers
  // the logger with the key "vuejs3-logger" inside the Vue instance
  app.use(VueLogger, options);
});

// This line creates a whole new local logger object which is not
// registered in the Vue instance
const logger = createLogger(options);

export { logger };

What you however can do is use the new static register function to register create a logger and register it in the Vue instance with a user defined key.
app.use(VueLogger.register("your-key"), options);

It must be called inside the app.use function to get a hold of the Vue instance.

Hi @MarcSchaetz
Alright, thank you!
I just did some more testing and this works perfectly for me.
I guess you can publish this change, as soon as you fixed the types-problem (as mentioned above).
It would probably make sense to add 1-2 lines to the readme, though.
Thanks ☺

ciao, any news on the release of this new features? i see version 2.0.0 on the repository that is not yet release on master


mat-tab

What is the use-case existing behavior?
How can i disable mat-tab content transition?

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.


fix(runtime-core):flushPostFlushCbs recursively flush until it drains

flushPostFlushCbs is the same with flushPreFlushCbs

What problem does this PR want to solve?

If I've understood correctly, then I don't think flushing the post jobs would be what we'd want. If a post job is triggered by another post job then it needs to wait until after the next rendering run. Recursive flushing would potentially cause the new job to run before the relevant DOM updates are performed.


Segmentation not performed when running RegionGrowingAlgorithm

When running the 4D-OBC segmentation, the workflow always stops before the actual region growing, i.e. after or during the sorting of seeds. Observing the memory load of the computer, it should not be a problem of working memory. At the moment, I have no other clue what to check.
Log output:
[2022-06-19 11:44:18][INFO] Removing intermediate results from the analysis file kijkduin_4dobc.zip
[2022-06-19 11:44:18][INFO] Starting: Smoothing temporal data
[2022-06-19 11:44:52][INFO] Finished in 33.2689s: Smoothing temporal data
[2022-06-19 11:44:52][INFO] Starting: Find seed candidates in time series
[2022-06-19 11:45:23][INFO] Finished in 31.7365s: Find seed candidates in time series
[2022-06-19 11:45:23][INFO] Starting: Sort seed candidates by priority
[2022-06-19 11:45:57][INFO] Finished in 34.0351s: Sort seed candidates by priority

Solved in private communication - no actual seeds were found, potentially due to missing configuration for seed detection.


ToArray() and ToList() with length

I created a PR (#70) about simple overload for ToArray() and ToList() with lenght parameter. With lenght we can avoid multiple creations of array/list when rewriting IEnumerable to these collections.

Closing as duplicate to the PR, since the PR already exists.


Only allow inline and style origins if browser-policy-content exists

From https://github.com/meteortesting/meteor-mocha/issues/67
We only use the browser-policy-framing package, which makes the check for Package['browser-policy-common'] pass, but since we don't use browser-policy-content we get the following error on test runs now:
W20180608-17:13:06.473(0)? (STDERR) TypeError: Cannot read property 'allowInlineStyles' of undefined
W20180608-17:13:06.473(0)? (STDERR)     at server.js (packages/meteortesting:mocha/server.js:13:25)

It happens because the check here assumes we're also using browser-policy-content though we're not.
This should avoid the issue by not modifying content policy if you only include 1 of the browser-policy packages.

@aldeed Did you get a chance to review this. Unfortunately it makes the update to Meteor 1.7 more painful than it needs to be.


Created Merge sort C++ #178.cpp

C++ program for the implementation of merge sort

Thanks for your contribution!

PR has been merged under Hacktoberfest!

Happy contribution!


added an Example using pytorch lightning

This is an example application of the scsl fashion mnist example with PyTorch lightning.
Lightning removes a lot of the boilerplate of PyTorch and helps to focus on the network.
Furthermore, lightning makes training on GPUs very simple.

This is cool Phil, thanks for putting it together. I don't actually have any GPUs, so I can't run it myself, but I'll merge it since it runs for you. I appreciate that your changes are limited to this one file - it makes the merge clean.


Change client-side mutations to reflect the ones created on the server-side

completed in commit 53b174ca1a13d28b827eae4da337347f49b0c3f5


From private repo

@itechedit : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.


OpenSSL3.0 and Ubuntu 22.04 Support...

Looking forward to the support of
OpenSSL3 and Ubuntu 22.04.
Thanks...

+1

For ubuntu 22.04, you can download k4a-tools_1.4.1_amd64.deb, libk4a1.4-dev_1.4.1_amd64.deb and libk4a1.4_1.4.1_amd64.deb for 18.04. Before installing this three .deb file, you need to temporarily switch the source list of apt to 20.04 and then install libsoundio1 (sudo apt install libsoundio1, which is  not avaliable in the source list  of 22.04.
This method works for me.

Before installing this three .deb file, you need to temporarily switch the source list of apt to 20.04 and then install libsoundio1 (sudo apt install libsoundio1, which is not available in the source list of 22.04.

Does anyone happen to have a recipe/example to do this, especially on the github actions ci/cd?

Answering my own request:

Does anyone happen to have a recipe/example to do this, especially on the github actions ci/cd?

Here is a code snippet I use in my github actions to install k4a and k4abt on Ubuntu 22.04. It also has the code to pre-accept the EULAs.
sudo apt-add-repository -y -n 'deb http://archive.ubuntu.com/ubuntu focal main'
sudo apt-add-repository -y 'deb http://archive.ubuntu.com/ubuntu focal universe'
sudo apt-get install -y libsoundio1
sudo apt-add-repository -r -y -n 'deb http://archive.ubuntu.com/ubuntu focal universe'
sudo apt-add-repository -r -y 'deb http://archive.ubuntu.com/ubuntu focal main'

if ! dpkg -s libk4a1.3 > /dev/null; then
	curl -sSL https://packages.microsoft.com/ubuntu/18.04/prod/pool/main/libk/libk4a1.3/libk4a1.3_1.3.0_amd64.deb > /tmp/libk4a1.3_1.3.0_amd64.deb
	echo 'libk4a1.3 libk4a1.3/accepted-eula-hash string 0f5d5c5de396e4fee4c0753a21fee0c1ed726cf0316204edda484f08cb266d76' | sudo debconf-set-selections
	sudo dpkg -i /tmp/libk4a1.3_1.3.0_amd64.deb
fi
if ! dpkg -s libk4a1.3-dev > /dev/null; then
	curl -sSL https://packages.microsoft.com/ubuntu/18.04/prod/pool/main/libk/libk4a1.3-dev/libk4a1.3-dev_1.3.0_amd64.deb > /tmp/libk4a1.3-dev_1.3.0_amd64.deb
	sudo dpkg -i /tmp/libk4a1.3-dev_1.3.0_amd64.deb
fi
if ! dpkg -s libk4abt1.0 > /dev/null; then
	curl -sSL https://packages.microsoft.com/ubuntu/18.04/prod/pool/main/libk/libk4abt1.0/libk4abt1.0_1.0.0_amd64.deb > /tmp/libk4abt1.0_1.0.0_amd64.deb
	echo 'libk4abt1.0	libk4abt1.0/accepted-eula-hash	string	03a13b63730639eeb6626d24fd45cf25131ee8e8e0df3f1b63f552269b176e38' | sudo debconf-set-selections
	sudo dpkg -i /tmp/libk4abt1.0_1.0.0_amd64.deb
fi
if ! dpkg -s libk4abt1.0-dev > /dev/null; then
	curl -sSL https://packages.microsoft.com/ubuntu/18.04/prod/pool/main/libk/libk4abt1.0-dev/libk4abt1.0-dev_1.0.0_amd64.deb > /tmp/libk4abt1.0-dev_1.0.0_amd64.deb
	sudo dpkg -i /tmp/libk4abt1.0-dev_1.0.0_amd64.deb
fi
if ! dpkg -s k4a-tools > /dev/null; then
	curl -sSL https://packages.microsoft.com/ubuntu/18.04/prod/pool/main/k/k4a-tools/k4a-tools_1.3.0_amd64.deb > /tmp/k4a-tools_1.3.0_amd64.deb
	sudo dpkg -i /tmp/k4a-tools_1.3.0_amd64.deb
fi

@jackjansen is there a reason you are not using last version (k4a-tools1.4 libk4a1.4-dev libk4abt1.1-dev) ?

Sorry @remmel I hadn't seen your message until just now. There was a historic reason for sticking with 1.3 for our application, but I must admit that I don't remember anymore what the problem was with 1.4. I vaguely remember that it had to do with the fact that k4abt 1.1 didn't work for us, and therefore we reverted to k4abt 1.0, and that required us to revert to k4a 1.3.
I will try to find the time to investigate, but I can't promise anything.


Single quotes don't work?

Of the following two lines, the first line fails, the second line works:
alias ll='ls -la'
alias ll="ls -la"

I tried it twice, with the same results:

Running PowerShell inside ConEmu, then typing cash
Running cmd.exe inside its own window, then typing cash

The error I get is this:
$ alias ll='ls -la'

  Invalid option: 'l'. Showing Help:

  Usage: alias [options] [name...]

  Options:

    --help  output usage information
    -p  print all defined aliases in a reusable format

Okay traced this back to a bug in Vorpal's argument parsing. Thanks for pointing out.

Fixed in Vorpal v1.10.2, Cash v0.4.0.
https://github.com/dthree/vorpal/commit/c2036c9830b88bb2c74b762258122731e65f1017

Fixed in Vorpal v1.10.2, Cash v0.4.0.
https://github.com/dthree/vorpal/commit/c2036c9830b88bb2c74b762258122731e65f1017


Make matches tab always active

The matches tab is a special case. If it is inactive, users do not know if there is anything they can do, like submitting it to a matcher.
Therefore, they need to see that no matches have been found so far, and that matching is actually taking place.
Maybe the empty matches view should explain the process a bit.

As long as we do not have a nice graphical way of explaining, we can just write:
Matching for your published needs is in progress, but has been found yet. You'll be notified as soon as something comes up!


Social media posts

Please add below any links to information you'd like to share on the OpenFeature social media profiles (Twitter & Linkedin).
Don't forget to add your social media handles for tagging.

Kubecon talk about OpenFeature is available now on YT -> https://youtu.be/zS6Abop1RJY

Alex Jones has joined our Governance board

We have a tutorial on using the cloud native components (OpenFeature operator + flagd) here: https://docs.openfeature.dev/docs/tutorials/ofo.
It will likely be updated soon with helm installation instructions, but there's no reason we can't promote it independently of that.

For Go, the maintainers of flipt recently added a flipt provider. For JS, the community added a PostHog provider, which can be seen in our catalog at the respective places.

https://thenewstack.io/ebay-betting-on-open-source-is-great-for-your-business/ - This mentions openfeature which you may want to link to somewhere. Twitter link: https://twitter.com/thenewstack/status/1592220608133500928

Announce Alois as governance committee member

We have 2 new tutorials: getting started with Java and JS

Thanks to @tcarrio, OpenFeature now has a PHP SDK!
https://docs.openfeature.dev/docs/reference/technologies/server/php

GO Feature Flag has now a .NET provider available.
Some associated links:
provider link: https://www.nuget.org/packages/OpenFeature.Contrib.GOFeatureFlag
repository: https://github.com/thomaspoignant/go-feature-flag
Website: https://gofeatureflag.org/
Doc: https://docs.gofeatureflag.org/
Twitter: @gofeatureflag

OpenTelemetry added feature flag semantic conventions to their spec.
https://github.com/open-telemetry/opentelemetry-specification/pull/2529

Reminder that the meeting on the 23rd is not a typical one.

OpenFeature Happy Holidays post

Closing this issue for 2022 - will reopen after the holidays.


Add RAII to DSP Kernel

Adding RAII to the DSP Kernel so we can
initialise all resources when instantiating subclasses.
ping @aure

Hmm, so this affects only two nodes for some reason.  I will check them out to see if they still sound about the same and the precision tests can be updated.

@aure I didnt know we had tests on AK so I never ran them. I can also look into it. (And worst case force the reinitialising of sp from the init() call - which im right now not doing if theres already an instance).

Its just AKPinkNoise and AKPluckedString

PinkNoiseTests
✗ testAmplitude, XCTAssertTrue failed - fe160cb0de91109574515f9bef8e3286
✗ testDefault, XCTAssertTrue failed - f5032eb3fc926f68a73fec67e29c6ac7
✗ testParameterSweep, XCTAssertTrue failed - db9904288c8872a06a87a6d4913eb942
PluckedStringTests
✗ testDefault, XCTAssertTrue failed - 382cdbd27558fed9c8723ba435cdb4cf

Actually its just the operation versions which is weird.

Yeah, and the root cause is
            sp_create(&sp);
        }```
as in repeated calls to init. Mhmmmm.


Security vulnerability in lodash dev dependency

Security Vulnerability
Description
There is a low severity security vulnerability in lodash versions before 4.17.11: CVE-2018-16487. The lodash package is a transitive dependency that is included indirectly from multiple development dependencies (e.g. babel, jshint) in package.json, so it does not affect a client's Node.js package when synctos is used as a dependency. Upgrade lodash and any other affected dependencies.

Addressed by https://github.com/Kashoo/synctos/pull/342.


Trying to create existing repo fails with ParseError

I noticed that when trying to call createOrganizationRepo' for the repo that already exists I get
ParseError "Error in $: key "description" not present
Description field for the repo is provided together with the rest of the needed data so this error is misleading. I can provide more details if it is hard to pinpoint why this fails.

Might be a duplicate of https://github.com/phadej/github/issues/352 as current 0.21 version fails to check error codes.


What is scale factor used for?

Hi, in the NSGkittiDataParserConfig, there is a parameter named scale_factor, what is this param used for? Should I change it according to different datasets? Thanks!

The scale factor is used to scale the scene. Basically, you want to make sure all the scene contents are in [-1,1].

Thanks for your reply. If I want to train a model on a custom dataset, how should I change it? Can I just set it to 1? Thanks.

you can manually adjust the scale based on experimental results, as it is vital for the performances.

ok, thanks a lot.

you can manually adjust the scale based on experimental results, as it is vital for the performances.

@wuzirui Should the objects' pose also be in [-1,1]?


preview button alongside browse button?

In 2.1 we had a preview button alongside the browse for media button to quickly preview the currently selected media. I know that's not needed inside the wysiwyg editor itself but can/should we still have this alongside the browse for media button e.g. the graphics and sound page etc?

Well yes, it would be good to have that. It's also a pre-requisite to be able to implement the 'synching'feature, wich would be most welcom to the mediaLesson.
I simply don't have the time to implement it now.


Lab-10-isolate-problem-areas-poor-performing-queries: query syntax error due to auto-type option

Module: 05
Lab/Demo: 10
Task: Generate actual execution plan
Step: 01
Description of issue
Error:

Module: 05
Lab/Demo: 10
Task: Use Query Store to detect and handle regression
Step: 07
Description of issue
Error:

Module: 05
Lab/Demo: 10
Task: Use query hints to impact performance
Step: 02-03
Description of issue
Error:

Module: 05
Lab/Demo: 10
Task: Change the query to use a variable and use a Query Hint
Step: 02-03
Description of issue
Error:

Suggestion to fix all those syntax errors: install SSMS and disable the IntelliSense option in the VM image. Alternatively, provide the script as an asset in the GitHub repository.

Thanks for your comment.
Before initiating the labs, we have the following alert note part of the instruction: When copying code from the lab exercises into the lab virtual machine, occasionally line breaks will not come across properly. Please verify that the code is correctly copied before executing it.
We also think the IntelliSense is an important tool for students during the lab.
For now we will keep this issue closed, and we can reevaluate it later on if needed.


[HOLISTIC SOLUTION] Info about the visibility/confidence of keypoints from the hands is not available.

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
No
OS Platform and Distribution
Ubuntu
MediaPipe Tasks SDK version
Holistic
Task name (e.g. Image classification, Gesture recognition etc.)
Holistic
Programming Language and version (e.g. C++, Python, Java)
Python
Describe the actual behavior
In the actual version: Info about the visibility/confidence of keypoints from the hands is not available.
Describe the expected behaviour
Give information about the confidence of the keypoints of the hands extracted
Standalone code/steps you may have used to try to get what you need
In the current holistic solution, the visibility and presence fields for the hands are always 0.
And contrary to the hand solution which has a field called Handedness where the confidence or score for the hand is indicated, in the case of the holistic solution there is no output indicating the quality or confidence of the keypoints obtained.
Is this a bug? Or am I missing something?
Thank you very much.

Other info / Complete Logs
HolisticLandmarkerResult(face_landmarks=[
 NormalizedLandmark(x=0.4745168089866638, y=0.36261075735092163, z=-0.0224269051104784, visibility=0.0, presence=0.0),
 ....
 NormalizedLandmark(x=0.5119104385375977, y=0.2810891270637512, z=0.005499151535332203, visibility=0.0, presence=0.0)],

 pose_landmarks=[
 NormalizedLandmark(x=0.47517403960227966, y=0.3143022358417511, z=-0.9151485562324524, visibility=0.9999208450317383, presence=0.9995543360710144),
 ....
 NormalizedLandmark(x=0.41832780838012695, y=1.8102238178253174, z=0.12485508620738983, visibility=0.005907772108912468, presence=0.001108874916099012)],

 pose_world_landmarks=[

 Landmark(x=-0.046613965183496475, y=-0.5604096055030823, z=-0.3200050890445709, visibility=0.9999208450317383, presence=0.9995543360710144),
 ...
 Landmark(x=-0.12133946269750595, y=0.5424543023109436, z=0.04660561680793762, visibility=0.005907772108912468, presence=0.001108874916099012)],

 left_hand_landmarks=[
 NormalizedLandmark(x=0.5576450228691101, y=0.7599831819534302, z=4.721105995031394e-07, visibility=0.0, presence=0.0),
 ....
 NormalizedLandmark(x=0.6063085794448853, y=0.5707101821899414, z=-0.08902209997177124, visibility=0.0, presence=0.0)],

 left_hand_world_landmarks=[
 Landmark(x=0.019411759451031685, y=-0.2692203223705292, z=-0.36530426144599915, visibility=0.0, presence=0.0),
 .....
 Landmark(x=0.017838725820183754, y=-0.3276180922985077, z=-0.42397379875183105, visibility=0.0, presence=0.0)],

 right_hand_landmarks=[
 NormalizedLandmark(x=0.3994499146938324, y=0.7287973761558533, z=3.09612943283355e-07, visibility=0.0, presence=0.0),
 .....
 NormalizedLandmark(x=0.3777098059654236, y=0.6123549938201904, z=-0.02483273483812809, visibility=0.0, presence=0.0)],

 right_hand_world_landmarks=[
 Landmark(x=-0.1434965282678604, y=-0.22600455582141876, z=-0.3554910123348236, visibility=0.0, presence=0.0),
 .....
 Landmark(x=-0.14976395666599274, y=-0.30362075567245483, z=-0.39388307929039, visibility=0.0, presence=0.0)],

 face_blendshapes=None, segmentation_mask=None)

Hi @mvazquezgts,
Could you please provide additional information about the problem. Include the following details:

Outline the steps you are following to implement  based on the documentation.
Specify the Ubuntu version you are using.
Provide the version of MediaPipe is being used Along with Python Version.

Providing this information will help us better understand and address the issue.
Thank you!!

OS: Ubuntu
Programming Language: Python
Version de Mediapipe: 0.10.11
Solution: Holistic

Given an input image/frame the output of the model is:
HolisticLandmarkerResult(face_landmarks=[
NormalizedLandmark(x=0.4745168089866638, y=0.36261075735092163, z=-0.0224269051104784, visibility=0.0, presence=0.0),
....
NormalizedLandmark(x=0.5119104385375977, y=0.2810891270637512, z=0.005499151535332203, visibility=0.0, presence=0.0)],
pose_landmarks=[
NormalizedLandmark(x=0.47517403960227966, y=0.3143022358417511, z=-0.9151485562324524, visibility=0.9999208450317383, presence=0.9995543360710144),
....
NormalizedLandmark(x=0.41832780838012695, y=1.8102238178253174, z=0.12485508620738983, visibility=0.005907772108912468, presence=0.001108874916099012)],
pose_world_landmarks=[
Landmark(x=-0.046613965183496475, y=-0.5604096055030823, z=-0.3200050890445709, visibility=0.9999208450317383, presence=0.9995543360710144),
...
Landmark(x=-0.12133946269750595, y=0.5424543023109436, z=0.04660561680793762, visibility=0.005907772108912468, presence=0.001108874916099012)],
left_hand_landmarks=[
NormalizedLandmark(x=0.5576450228691101, y=0.7599831819534302, z=4.721105995031394e-07, visibility=0.0, presence=0.0),
....
NormalizedLandmark(x=0.6063085794448853, y=0.5707101821899414, z=-0.08902209997177124, visibility=0.0, presence=0.0)],
left_hand_world_landmarks=[
Landmark(x=0.019411759451031685, y=-0.2692203223705292, z=-0.36530426144599915, visibility=0.0, presence=0.0),
.....
Landmark(x=0.017838725820183754, y=-0.3276180922985077, z=-0.42397379875183105, visibility=0.0, presence=0.0)],
right_hand_landmarks=[
NormalizedLandmark(x=0.3994499146938324, y=0.7287973761558533, z=3.09612943283355e-07, visibility=0.0, presence=0.0),
.....
NormalizedLandmark(x=0.3777098059654236, y=0.6123549938201904, z=-0.02483273483812809, visibility=0.0, presence=0.0)],
right_hand_world_landmarks=[
Landmark(x=-0.1434965282678604, y=-0.22600455582141876, z=-0.3554910123348236, visibility=0.0, presence=0.0),
.....
Landmark(x=-0.14976395666599274, y=-0.30362075567245483, z=-0.39388307929039, visibility=0.0, presence=0.0)],
face_blendshapes=None, segmentation_mask=None)

The available data/fields are:

face_landmarks  [ x, y , z, visibility, presence]
pose_landmarks & pose_world_landmarks [ x, y , z, visibility, presence]
left_hand_landmarks & left_hand_world_landmarks [ x, y , z, visibility, presence]
right_hand_landmarks & right_hand_world_landmarks [ x, y , z, visibility, presence]
face_blendshapes
segmentation_mask

Both hand and face visibility and presence always gives 0, regardless of the configuration with which you set up/initialise the model.
It only gives some information in pose_landmarks & pose_world_landmarks.

So, my question is whether this is a bug or if it is possible to get the confidence/visibility of the hand points in another way.
In the hands model (documentation: https://developers.google.com/mediapipe/solutions/vision/hand_landmarker/python) I see that there is a 'Handedness' field that contains this information.
HandLandmarkerResult:
Handedness:
Categories #0:
index        : 0
score        : 0.98396
categoryName : Left
Landmarks:
Landmark #0:
x            : 0.638852
y            : 0.671197
z            : -3.41E-7
Landmark #1:
x            : 0.634599
y            : 0.536441
z            : -0.06984
... (21 landmarks for a hand)
WorldLandmarks:
Landmark #0:
x            : 0.067485
y            : 0.031084
z            : 0.055223
Landmark #1:
x            : 0.063209
y            : -0.00382
z            : 0.020920
But it seems that in this version of Holistic there is no way to get a score for hand points.

Thank you for raising this. As this is our newest Task, we likely need to invest a bit more time here.

Its an old issue:
#3505

I am experiencing the same issue (holistic task on web), any updates on this?

I am experiencing the same issue (holistic task on web), any updates on this?

wow this is really unprofessional from you guys... there are multiple issues about this. Can someone make a proper explanation about the state of visibility/confidence of pose, face and hand landmark detection @schmidt-sebastian @kuaashish

can you at least please confirm that every landmark will be predicted even if it is not present in the image. If so, can it ever be out of bounds of the base image? @schmidt-sebastian @kuaashish
https://github.com/google-ai-edge/mediapipe/issues/3159


How to 'play nicely' on FreeBSD?

I'm currently running the proxy on FreeBSD (actually in a chroot jail in FreeNAS) so I don't have the ability to install the 'run as a service' option.
I can start the dnscrypt-proxy binary in various ways, but could anyone tell me some way that I can control it "properly". For example once the binary is running (and has written it's PID to a file - thank you!) I can't seem to stop it nicely. It doesn't seem to respond to SIGHUP, and SIGTERM causes it to exit with nothing written to the logs and with the PID file left behind.
I'm wanting to use 'monit' to handle unexpected exits or stalls by restarting, but that needs to be able to stop and start the process (using a custom-defined command such as 'service xyz stop' or 'etc/init.d/xyz start') in response to events such as it failing to respond to a dns query or to the pidfile disappearing, which I can't currently figure out how to do. I'm happy to tinker with init scripts etc. but I still need to figure out how to interface to the dnscrypt binary.
I'd normally try to answer this myself by reading through the sources, but I'm not at all familiar with Go.
Any help or suggestions welcome :-)

Looks like this is the same as jedisct1/dnscrypt-proxy#154 and jedisct1/dnscrypt-proxy#157 saying its an issue with another package which would lead us to kardianos/service#98. To solve it still requires Go knowledge, but it's a start.


Log - Configuring calendars trough configuration.yaml has been deprecated

I'm seeing this message in my log from the o365 component:
Configuring calendars trough configuration.yaml has been deprecated, and will be removed in a future release. Please see the docs for how to proceed
First of all, I looked in the docs and there doesn't seem to be anything that explains what exactly was deprecated and what you should do.  Since you're saying to go to the docs to figure out how to proceed please put something in the docs that specifically references this and tells me how to proceed.
Second, I think I figured out what you mean by this although I'm not totally sure.  I noticed that there's now an o365_calendars.yaml file in my config that I don't remember adding before.  So I believe what this is telling me is to remove this part in my configuration.yaml:
o365:
  client_secret: "xx.xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  client_id: "xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx"
- calendars:
- - name: Mike work calendar
-   start_offset: -8
-   end_offset: 336
-   calendar_name: default_calendar

If so, please remove that part from your example for sure.
Final point, I'm not sure deprecation is the right word here.  If you notice in my configuration above I had one calendar listed that I called 'Mike work calendar'.  At the time I wrote that this component generated one calendar entity with the id calendar.mike_work_calendar that shows the list of events from 8 hours ago until 14 days from now.  But thats not what I have now.  There is no calendar.mike_work_calendar, instead I have 3 calendar entities called calendar.o365_calendar, calendar.o365_birthdays and calendar.o365_united_states_holidays which all list events from now to 24 hours from now.  Which is exactly what's in this new o365_calendars.yaml file.
So is this option actually deprecated or just completely unsupported ? Because it seems like configuring calendars in configuration.yaml just flat out doesn't work anymore.
As an aside I actually really like your component, I was looking for this forever and am so glad I can connect to my work calendar now.  And this all isn't a big deal to me now that I think I know what is going on I just was really confused by this message.

Hello
If you are receiving that log message you are currently running the unsupported beta version.
Due to it being a beta I have deliberately not updated the documentation, and will not be doing so until it's released as a final non-beta version.
But the short story is that the calendar configuration has been moved to its own file, o365_calendars.yaml, to align this component closer with the Google Calendar integration.

But I will hopefully have the time to release the final version early next week 😊

Oh!  Well that makes more sense but I'm not entirely sure how I got on the beta version then.  This is what I see in my HACS right now:

Is 2.1.4 beta?  I thought the beta releases were labeled with beta in the release ID.

Well that is strange. That log should no be present in anything before v2.1.5-beta.1
This might be my fault. For a short while some of the beta version were missing the pre-release tag.
If you reinstall v2.1.4 from HACS the warning should not appear. Or you can ignore it until I release the final version

It's all good now that I know what's going on.  I stripped out that config and tweaked the other file so its all working the way I want it to now and no errors.  Although I guess I should probably turn on beta updates to make sure I'm on the latest and not on like beta v1.  Thanks for the help!

Final v2.1.5 has been released and i have added a section to the documentation pertaining to the calendar configuration
https://github.com/PTST/O365-HomeAssistant#calendar-configuration


handle dependencies for python scripts

Use docker images.

pros:

don't need to care about the environment, call docker build & run
docker is a well-known technology, and most people can use it
a lot of times, the Python scripts already need a docker

cons:

you need to make a docker image every time you want to run a script
it might be easier to download dependencies only once globally

make an init script that holds all the pip installs, and call that in the processor_server's init

For now on, I will make an init logic, that will create a python environment with venv and install the modules from requirements.txt

I'm closing this, I want to use a docker image to handle this problem.


Model update callback never triggered

I am trying to update a model but the callback in the exec() is never fired:
console.log('----------------START----------------', existingModel.id);
MyModel.update({ id: existingModel.id }, modelUpdates).exec(function(e, updatedModel) {
      console.log('----------------FIN----------------', updatedModel.id);
      callback();
});

The above is essentially what I am doing, but FIN is never logged. Where am I going wrong?
modelUpdates is an object containing values to update.
_UPDATE_
The records ARE being updated, but the callback just doesn't fire!

+1 Have you figured out a solution yet?


The newly created blob isn't highlighted in Azure view after it's created

OS: All
Build Version: 20210604.34
Repro Steps:

Right click one blob container -> Create Empty blob... -> Enter a name for it to create a blob.
Check whether the cursor focus on this new created blob in Azure view.

Expect:
The cursor focus on this new created blob in Azure view.

Actual:
The cursor doesn't focus on this new created blob in Azure view.

More Info:
This issue also reproduces for new created file/blob container/file shares.

Hi @v-ruizh
Both @wwlorey and I couldn't reproduce this.  Are there any other steps that we should be aware of to make this behavior happen?

@nturinski There is no other steps for this issue.
Create an empty blob, the blob file will be opened and the cursor focus on it. The new created blob should be selected in Azure View. That means the new opened blob should be selected(highlighted).
The actual result is that the new blob is opened but it isn't selected(highlighted) in Azure view.

This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!


LusciousRipper non existing method test removed

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[x] a bug fix (Fix #154 )
[ ] a new Ripper
[x] a refactoring
[ ] a style change/fix
[ ] a new feature

Description
Second PR for #154 as the last one (#156) blocked the release build

I did not understand what you mean. The previous PR #156 is merged right? I saw you reverted it and then reverted the revert. So the only changes needed were to the test as it was trying to call a method that does not exist, which this PR fixes. Is there anything else I need to do?

ah, no, all good, i guess. it built red for other tests. of course, if you ask, it would be cool if you fix such tests as well or mark them flaky :) facilitates release ...


[BUG] - conda-store-server silently exits when port is already in use

Describe the bug
If you start conda-store-server when the configured port is already in use (e.g., because conda-store-server is already running), the process just silently exits.
Expected behavior
It should at least give an error message.
Actually, it should probably do one of the following:

Automatically find a free port.
If it doesn't actually make sense for multiple conda-store servers to be running simultaneously, automatically check if an existing conda-store server is running somewhere and fail if it is.

Even if the latter is the case, finding a free port could be useful in case some other application is using port 5000.
How to Reproduce the problem?
Run conda-store-server then run conda-store-server again in a different terminal.
Output
This is the only output that appears
$ conda-store-server
INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.

However, you can tell what the real problem is if you make the following patch
diff --git a/conda-store-server/conda_store_server/server/app.py b/conda-store-server/conda_store_server/server/app.py
index 741a31d..8f2dde7 100644
--- a/conda-store-server/conda_store_server/server/app.py
+++ b/conda-store-server/conda_store_server/server/app.py
@@ -363,6 +363,10 @@ class CondaStoreServer(Application):
                     else []
                 ),
             )
+        except:
+            import traceback
+            traceback.print_exc()
+            raise
         finally:
             if self.standalone:
                 process.join()

Then you get the error in the additional printed traceback:
$ conda-store-server
INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
Traceback (most recent call last):
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/site-packages/uvicorn/server.py", line 160, in startup
    server = await loop.create_server(
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/asyncio/base_events.py", line 1493, in create_server
    raise OSError(err.errno, 'error while attempting '
OSError: [Errno 48] error while attempting to bind on address ('<IP_ADDRESS>', 5000): address already in use

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/aaronmeurer/Documents/conda-store/conda-store-server/conda_store_server/server/app.py", line 352, in start
    uvicorn.run(
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/site-packages/uvicorn/main.py", line 587, in run
    server.run()
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/site-packages/uvicorn/server.py", line 61, in run
    return asyncio.run(self.serve(sockets=sockets))
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/asyncio/base_events.py", line 628, in run_until_complete
    self.run_forever()
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/asyncio/base_events.py", line 595, in run_forever
    self._run_once()
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/asyncio/base_events.py", line 1881, in _run_once
    handle._run()
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/site-packages/uvicorn/server.py", line 78, in serve
    await self.startup(sockets=sockets)
  File "/Users/aaronmeurer/anaconda3/envs/conda-store-server-dev/lib/python3.10/site-packages/uvicorn/server.py", line 170, in startup
    sys.exit(1)
SystemExit: 1

Versions and dependencies used.
No response
Anything else?
No response

From today's meeting, we should have a helpful error message here. Also, as a sidenote, we should change the default port to something other than 5000 (because 5000 doesn't work on Mac machines).

For developers, it makes total sense to have two simultaneously running instances of conda-store, for instance to compare behaviors after a modification. Note that in this context, we're talking of two different versions running simultaneously, or twice the same version from two different directories.
For the users, I don't see any scenario requiring two instances running simultaneously but I'd rather not limit what users can do.
So I think multiple instances running should be supported.
Now, two cases :

Either the user asks explicitly for a given port, and if it is in use, it should fail and ask to use a different port
Or the user didn't ask for a specific port, and then we can just set port 0 as default - uvicorn will pick a random free port instead.

We'll discuss the prefered behavior during our meeting.

Status as of 5e4e2e5:

[x] we've already moved the default port to 8080 (from 5000), so it no longer clashes with AirPlay Receiver on macOS
[x] address and port are user-configurable options, via traitlets
[ ] we need to print what address and port are used before the server is started
[ ] we need to warn users if address and port are already in use - the except block by Aaron will do that.


feat: Onboard Austin Waste dataset

Description
Based on #
Note: It's recommended to open an issue first for context and discussion.
Checklist
Note: Delete items below that aren't applicable to your pull request.

[x] Please merge this PR for me once it is approved.

[x] If this PR adds or edits a dataset or pipeline, it was reviewed and approved by the Google Cloud Public Datasets team beforehand.

[ ] If this PR adds or edits a dataset or pipeline, I put all my code inside  datasets/austin_waste and nothing outside of that directory.

[x] This PR is appropriately labeled.

Just FYI, one of the checklist items is
If this PR adds or edits a dataset or pipeline, I put all my code inside datasets/austin_waste and nothing outside of that directory.

but datasets/bls was edited.


[5.4] Allow Artisan::queue() to accept --queue options.

This allow artisan command to be queued on specific tube instead of
using the "default" tube.
Artisan::queue('send-email', ['--queue' => 'notifications']);

Signed-off-by: crynobone<EMAIL_ADDRESS>

In 5.5 release, we may include a 3rd parameter options to allow passing $queue instead of just relaying on --queue command option.
Artisan::queue('send-email', [], 'notifications');

I think this will give a more robust option: https://github.com/laravel/framework/commit/51647eb701307e7682f7489b605a146e750abf0f
Can now do ->onQueue, ->onConnection(), ->delay(), etc from Artisan::queue()


Extension causes high cpu load

Issue Type: Performance
Extension Name: vscode-kubernetes-tools
Extension Version: 0.1.16
OS Version: Darwin x64 18.2.0
VSCode version: 1.31.0

:warning: Make sure to attach this file from your home-directory: /Users/chope2/ms-kubernetes-tools.vscode-kubernetes-tools-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

@chuckstar76 Is it okay to close this as a duplicate of #479 which has the cpuprofile file attached?  Thanks!

Hi - yes please close, I realised the attachment was missing and added to #479 - as indicated.


Getting WebSocket Connection to failed error

I am trying to connect my javascript file to my deepstreamIO server but i get the error WebSocket connection to 'wss://localhost:6020/deepstream' failed
This is my js file:
var client = deepstream("wss://localhost:6020");
client.login({}, function(success, data) {
    print(succes+" "+data)
    if (success) {
        console.log("Connected to deepstreamm!!!")
    } else {
        console.log("failed: "+data)
    }
});

I am using a https server and the deepstreamIO server is on the same machine as the https server

Hi, try deepstream("localhost:6020/deepstream"); thats the default connection url


Network Condition: UI #1

Description
It's time to support the Network Conditioner Tool
UI

Reuse what we've done of the Map Local or Breakpoint List View
Implement new UI:

Update requirement 1

[ ] Add a new menu for Network conditions with a shortcut

[ ] When the Network Condition is activated -> Show the Badge

[ ] Click on the Network Condition badge will open the Network Condition Tool Windows

Main View

[ ] Reuse the same TableView + Logic from the Map Local or Breakpoint.
[ ] Only 1 rule can be activated -> Show the ✅
[ ] Other rules will be disabled with gray color
[ ] Implement the Right Menu Context with all actions: New, Duplicate, Edit, ... with shortcuts

Edit View

[ ] Reuse the same Edit View from Breakpoint Edit View
[ ] Show the Preset Dropdown
[ ] Show the preset network data (Upload/Download)
[ ] Make sure we don't hard code these data, it should be define in the Enum or class (See the next ticket)


Ver. 1.4.0 NoSuchMethodError: com.google.cloud.datastore.DatastoreOptions$Builder.setConnectTimeout

I tried to ver 1.4.0 latest version in Maven but I get the below error but when I downgraded to 1.3.1 the library works fine
java.lang.NoSuchMethodError: com.google.cloud.datastore.DatastoreOptions$Builder.setConnectTimeout(I)Lcom/google/cloud/HttpServiceOptions$Builder;
     com.jmethods.catatumbo.EntityManagerFactory.createEntityManager(EntityManagerFactory.java:265)
     com.jmethods.catatumbo.EntityManagerFactory.createEntityManager(EntityManagerFactory.java:187)
     com.jmethods.catatumbo.EntityManagerFactory.createEntityManager(EntityManagerFactory.java:162)
     com.jmethods.catatumbo.EntityManagerFactory.createEntityManager(EntityManagerFactory.java:142)
     com.jmethods.catatumbo.EntityManagerFactory.createEntityManager(EntityManagerFactory.java:92)

I'm unable to reproduce this issue. My Maven POM has the following dependency and was able to interact with the Datastore without any issues. My guess is that your Runtime Class Path has an incompatible version of Google Cloud Java API, than what Catatumbo 1.4.0 requires. Catatumbo 1.4.0 requires 0.9.4-beta version of Google Cloud Java API. Newer versions of the Google Cloud API have a breaking change (not backward compatible) for setting the timeouts.
Please double check your runtime class path and try again.
    <dependency>
      <groupId>com.jmethods</groupId>
      <artifactId>catatumbo</artifactId>
      <version>1.4.0</version>
    </dependency>

I'm using Google Cloud Datastore  v. 0.13.0-beta
I've not tried to downgrade my google cloud datastore api but catatumbo v1.3.1 and older works fine.

That explains it. Newer versions of Google Cloud Java API use TransportOptions to set the timeouts. The reason why Catatumbo 1.3.1 works is because versions prior to 1.4.0 did not attempt to set any timeouts and left it up to the Google Cloud Java API to use the defaults. So, the timeout methods are never called explicitly. Anyhow, I recommend using the compatible versions of Catatumbo and Google Cloud Java. I will be releasing a new version soon, hopefully this weekend, that will use the latest Google Cloud Java API.

Not an issue, closing this.


typescript should be a devDependency and not a regular dependency

Describe the bug
typescript should be a devDependency and not a regular dependency, being a dependency causes it to force the library version in projects which uses a devDependency for typescript (as it should be)
please move the typescript dependency to devDependency

Hi @toter3 👋
Thanks for pointing it out. typescript is now a devDependency version 1.3.0 onwards. 🎉


Google Sheets source UI problem

## Environment

Deploy method: docker-compose.yml
Jitsu version:  for instance 1.44.1
OS: KDE Plasma 5 (Linux)

Description
I am trying to configure Google Sheets source through service account but I cannot setup due to an UI problem ( selector does not show this option in "Authorization Type" field.
Steps to reproduce

Setup Jitsu project v.1.44.1 in local with docker-compose.yml
Select google-sheets source.
Try to change "Authorization type" from "OAuth" to "Service account".

Expected behavior
We should be able to select from OAuth or service account in UI.
Actual behavior
Cannot select service account config.type in UI.

Good morning.
I have configured it using OAuth, after setting up all correct, we get an error.
I paste the error for you:
`Error: Error singer --discover: exit status 1. CRITICAL HTTP-error-code: 400 invalid_request: Could not determine client ID from request.
Traceback (most recent call last):
File "/home/eventnative/data/venv/tap-google-sheets/lib/python3.9/site-packages/tap_google_sheets/client.py", line 111, in raise_for_error
response.raise_for_status()
File "/home/eventnative/data/venv/tap-google-sheets/lib/python3.9/site-packages/requests/models.py", line 940, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://oauth2.googleapis.com/token
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/eventnative/data/venv/tap-google-sheets/bin/tap-google-sheets", line 11, in
load_entry_point('tap-google-sheets==2.0.0', 'console_scripts', 'tap-google-sheets')()
File "/home/eventnative/data/venv/tap-google-sheets/lib/python3.9/site-packages/singer/utils.py", line 229, in wrapped
return fnc(*args, **kwargs)
File "/home/eventnative/data/venv/tap-google-sheets/lib/python3.9/site-packages/tap_google_sheets/init.py", line 36, in main
with GoogleClient(parsed_args.config['client_id'],
File "/home/eventnative/data/venv/tap-google-sheets/lib/python3.9/site-packages/backoff/_sync.py", line 94, in retry
ret = target(*args, **kwargs)
File "/home/eventnative/data/venv/tap-google-sheets/lib/python3.9/site-packages/tap_google_sheets/client.py", line 163, in enter
self.get_access_token()
File "/home/eventnative/data/venv/tap-google-sheets/lib/python3.9/site-packages/backoff/_sync.py", line 94, in retry
ret = target(*args, **kwargs)
File "/home/eventnative/data/venv/tap-google-sheets/lib/python3.9/site-packages/tap_google_sheets/client.py", line 198, in get_access_token
raise_for_error(response)
File "/home/eventnative/data/venv/tap-google-sheets/lib/python3.9/site-packages/tap_google_sheets/client.py", line 128, in raise_for_error
raise ex(message)
tap_google_sheets.client.GoogleBadRequestError: HTTP-error-code: 400 invalid_request: Could not determine client ID from request.
(#400)
at http://localhost:8000/static/js/main~213b07df.6b29e63b.chunk.js:264:2358`
Setup configuration is right because it's working in other tests.

In beta image we have replaced Google Sheets source with airbyte version.
It also supports "Service account" authorization.
Can you please check it

Good morning!Seems to work fine, thank you very much


Undocumented field 'selfApikey'

The PDF document doesn't reference this key, but it is in the tool implementation (dummy data by the looks of it ('123').
The eWeLink iOS app also send this field, but a more real looking one in GUID format
What is this field for given that it is not the apiKey of the device itself?

When the device is in DIY mode, we don't have to worry too much about this field and the encrypted field.
Because we're in DIY mode, we don't have encrypted information.

Understood, I can get it working simply by using a dummy value, but the API shouldn't really need it if it is not needed

YES


📝 Improve documentation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

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

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
344

Relevant Lines:
374

💛  - Coveralls


Extract Inventory data prepare to ShardingScalingPreparer

For #5106 .
Changes proposed in this pull request:

Extract Inventory data prepare to ShardingScalingPreparer

Codecov Report

Merging #5197 into master will increase coverage by 0.00%.
The diff coverage is 80.51%.

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

Pull Request Test Coverage Report for Build 11071

65 of 77 (84.42%)  changed or added relevant lines in 7 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.03%) to 57.491%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-scaling/sharding-scaling-core/src/main/java/org/apache/shardingsphere/shardingscaling/core/preparer/splitter/InventoryDataTaskSplitter.java
61
62
98.39%

sharding-scaling/sharding-scaling-core/src/main/java/org/apache/shardingsphere/shardingscaling/core/synctask/DefaultSyncTaskFactory.java
0
1
0.0%

sharding-scaling/sharding-scaling-core/src/main/java/org/apache/shardingsphere/shardingscaling/core/controller/ScalingJobController.java
0
2
0.0%

sharding-scaling/sharding-scaling-core/src/main/java/org/apache/shardingsphere/shardingscaling/core/controller/task/SyncTaskController.java
0
2
0.0%

sharding-scaling/sharding-scaling-core/src/main/java/org/apache/shardingsphere/shardingscaling/core/preparer/ShardingScalingJobPreparer.java
0
6
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-scaling/sharding-scaling-core/src/main/java/org/apache/shardingsphere/shardingscaling/core/synctask/inventory/InventoryDataSyncTaskGroup.java
1
51.28%

sharding-scaling/sharding-scaling-core/src/main/java/org/apache/shardingsphere/shardingscaling/core/synctask/inventory/InventoryDataSyncTask.java
1
75.47%

sharding-scaling/sharding-scaling-core/src/main/java/org/apache/shardingsphere/shardingscaling/core/synctask/DefaultSyncTaskFactory.java
2
0%

Totals

Change from base Build 11069:
-0.03%

Covered Lines:
11835

Relevant Lines:
20586

💛  - Coveralls


Sync to Dropbox is using the wrong directory in Dropbox

@FWest98 It is linking to the wrong folder in Dropbox, which explains the error.

Is this fixed now?

If I am not mistaken, Yes.


virtual cluster with chinese name ,how to delete it

unfortunately i create a virtual cluster with chinese name  in privious version of openpai and the virtual cluster exist after seveal upgrade of openpai, i have tried many method to delete it ,but the virtual cluster in yarn maybe  is in a xml file ,so i cann't delete it like traditional database method  and we have many training job running in openpai ,i can't completely clean openpai.So i need your help,i have no idea ,thanks a lot ,emergency

What's your version?

0.11.0 thanks mzmssg

@zhaojizhuang4
The name checker is added in 0.10, as a workaround, could you try to roll back some service to 0.9 to solve it.
Here is the process:

Change your configuration to v0.9.y
Push it to configmap
./paictl.py service stop -n rest-server
./paictl.py service start -n rest-server
delete vc

Then recover to current version similarly. We will consider add a compartibility.

thanks mzmssg ,if i use zookeeper tools to delete /confstore/CONF_STORE and restart hadoop resource manager ,could this method possible?

@zhaojizhuang4
What's the error message?
If you want access hadoop directly, resource manager api is better
https://hadoop.apache.org/docs/r2.9.0/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Scheduler_Configuration_Mutation_API

i will try your suggestion to use RM API,  i forget the error i don't  know where  the vc name encoding problem webportal  or rest api server or RM api  ,neverthereless this problem have been solved from v0.11.0 ,i will try your suggestion

friend mzmssg, just now ,follow your last surgestion   i have successfully deleted 智慧畜牧,
i first use tcpdump to catch the vc create/update/delete op on webportal caused http flow  on 8088 port of hadoop rm , and use rested plugin of firefox  to simlate the http flow   and finally ,i get 3 gpu back , and my leader deep wang will be happy
thanks a lot


NoMethodError: undefined method `email' when registering user

Encountering error when registering user

app[web.1]: #<NoMethodError: undefined method `email' for #<Spaceship::Tunes::Member:0x007f76809e0a90>>
app[web.1]: /app/app/services/boarding_service.rb:121:in `find_app_tester'
app[web.1]: /app/app/services/boarding_service.rb:42:in `add_tester'
app[web.1]: /app/app/controllers/invite_controller.rb:91:in `create_and_add_tester'
app[web.1]: /app/app/controllers/invite_controller.rb:74:in `submit'

Same error here :/

Your ITC user should have admin privileges, if not, the app won't work properly :/
There's a conversation about this here and we all arrived to the same point https://github.com/fastlane/boarding/issues/53

We recently made an update so that you need either Admin or App Manager 🎉

Thanks guys, I've now seen #137. My bad in misreading the permissions in iTC.


False Positive on jersey-client-2.22.1.jar

False positive on library jersey-client-2.22.1.jar - reported as cpe:/a:oracle:oracle_client:2.22.1
<dependency>
   <groupId>org.glassfish.jersey.core</groupId>
   <artifactId>jersey-client</artifactId>
   <version>2.22.1</version>
</dependency>

Note: While I was seeing this reported previously, I've since added a it to my false positives xml to suppress it, but it no longer shows up in the list of suppressed vulnerabilities.

The 2.0.0 release added this as one of the "base" suppression rules. These do not show up in the list of suppressed vulnerabilities.


replaced opensplice with eclipse cyclonedds

@dirk-thomas @kscottz replaced opensplice with eclipse cyclonedds, thanks!

Same comments as on your already pending PR #581.

Took care of this (along with some other DDS related things) in #648


refactor: extract out all constants being used as hardcoded values or to mock realdata in a single file 🚀

There are multiple places where we are using hardcoded values to mock real data, the pr assembles all such constants in a single mock_evm_data module, inside constants.rs.
The name of the module comes from the fact that we are using these constants in place of mock values.
As we keep changing these values with real data, we can keep removing these constants as well from the module + now change in their values will also be atomic.
Closes #154
Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Testing
[ ] Other (please describe):

What is the current behavior?
Currently, we are using hardcoded values in place of constants, whereas we extract them to a single source so that a change to their values is atomic.
Issue Number: #154
What is the new behavior?

All mocked hardcoded values have been extracted to constants.

Does this introduce a breaking change?

[ ] Yes
[X] No

Other information
The heuristic used to find these values were:

Search for 0_0 pattern throughout the codebase
Look for TODO comments stating the value to be replaced with real value in future.

@Eikix I guess we can boil it down to this:

We have some data we mocking, when we get real data, we can remove those constants.
There are some values that after the merge don't make sense, and should always be None: Like, difficulty, nonce, etc.

We can limit this PR to extracting all constants to one place, then work on the second point of this comment in a separate issue!
wdyt?

That works for me.
Then before approving, can we investigate how doable it is to use lazy_static! instead of pure consts?
My understanding -> you cannot use reth_rpc_types in the constant.rs file as their type is not "const" compatible (correct me if im wrong), but it's not so elegant to declare them as u64 etc. and then do the conversion in the applicative code.

@Eikix here is a new commit, with lazy_static! approach.
For anyone else reading outdated conversations, those commits were discarded because of complex conflicts during rebase with #159, hence a new commit was simply applied on top of it.

@Eikix also opened an issue as per our discussion here.


update readme

sorry, just saw some minor tweaks I didn't see on first glance!

No worries. I will open up a follow up. Thanks for taking a look!


ISPN-14957 Allow to get internal cache info using rest

https://issues.redhat.com/browse/ISPN-14957

Merged, thanks


[release-2.8] donot delete addon if cluster is not found

issue:  https://issues.redhat.com/browse/ACM-6997

/lgtm


Self closing tags

I am having a hard time in the grammar getting self closing tags to style properly.
Here is what they send up looking like:

Checking the inspector, it appears that the closing tag just gets treated like raw text:

Could we get the grammar to create a span for that self-closing end of the tag?

Should be fixed. Can you let me know what the theme you are using is so I can add it to my tests. Thanks.


Updated sendgrid documentation for issue #2452 related to dapr/compon…

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[X] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[X] Read the contribution guide
[X] Commands include options for Linux, MacOS, and Windows within codetabs
[X] New file and folder names are globally unique
[X] Page references use shortcodes instead of markdown or URL links
[X] Images use HTML style and have alternative text
[X] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
Updated SendGrid Dapr Component Documentation related to dapr/components-contrib#1749
Issue reference
Please reference the issue this PR will close: #2452

@arahja - Could you also update the metadata spec at the start of the document to add the following fields
emailFromName
emailToName
emailCc
emailBcc
Add them into this below as an example.
metadata:

name: emailFrom
value<EMAIL_ADDRESS># optional
name: emailTo
value<EMAIL_ADDRESS># optional
name: subject
value: "Hello!" # optional
name: apiKey
value: "YOUR_API_KEY"

I made the requested changes.

I made the requested changes.

Excellent. One more question. Can the email addresses be a list of addresses? For example can I have 2 or more emails on the To, CC and BCC fields?  I was asked this questions yesterday and the docs are not clear, if these can be a list. If so, can you update the text and provide a list example. If not, just say that one one email address is allowed for these.

I will make the change in the documentation to state that only one email address can be used. I have been contemplating making a change to allow multiple email addresses. However, that is a breaking change so I haven't attempted that yet. I need figure out the v2 process.

I will make the change in the documentation to state that only one email address can be used. I have been contemplating making a change to allow multiple email addresses. However, that is a breaking change so I haven't attempted that yet. I need figure out the v2 process.

I suggested a simple sentence to add to the description. PTAL.

Yes, sorry. Thanks for the help.

@arahja - Thanks for the contribution. Really appreciate this.


Only produce one version of the runtime store, templates packages, and installers

Resolves https://github.com/aspnet/Universe/issues/655

Even if you're going to delete the archive and installer targets, I'm still going to merge so we can work out any other bugs we may have introduced in this change....separate from the upcoming "platforms" work.


proposal: add ed25519 to curve25519 conversion functions

As per this comment:
https://github.com/agl/ed25519/issues/24#issuecomment-531072744
It would be much appreciated if the original functions that were hosted at (now gone in favour of crypto/ed25519 package):
https://github.com/agl/blob/master/ed25519/extra25519/extra25519.go
for converting ed25519 keys into curve15519 keys to be hosted in here, or somewhere in /x/crypto/ed25519 (or x/crypto/extra25519) if they are not suitable for the core library.
Namely, these functions are needed:
// PrivateKeyToCurve25519 converts an ed25519 private key into a corresponding
// curve25519 private key such that the resulting curve25519 public key will
// equal the result from PublicKeyToCurve25519.
func PrivateKeyToCurve25519(curve25519Private *[32]byte, privateKey *[64]byte) {
	h := sha512.New()
	h.Write(privateKey[:32])
	digest := h.Sum(nil)

	digest[0] &= 248
	digest[31] &= 127
	digest[31] |= 64

	copy(curve25519Private[:], digest)
}

and
// PublicKeyToCurve25519 converts an Ed25519 public key into the curve25519
// public key that would be generated from the same private key.
func PublicKeyToCurve25519(curve25519Public *[32]byte, publicKey *[32]byte) bool {
	var A edwards25519.ExtendedGroupElement
	if !A.FromBytes(publicKey) {
		return false
	}

	// A.Z = 1 as a postcondition of FromBytes.
	var x edwards25519.FieldElement
	edwardsToMontgomeryX(&x, &A.Y)
	edwards25519.FeToBytes(curve25519Public, &x)
	return true
}

I think many projects are currently using these functions and now hit a wall because the original repo has been removed.

Duplicate of #20504.


OpenEF: new project to create Code Generation layer for EF Core providers

I would like to announce a new project I am starting to and ask the Entity Framework Core development team and Provider community for feedback.
OpenEF is a proposal to improve the provider experience by introducing a Code Generation layer to translate a Microsoft developed provider into a base implementation for third-party providers. The primary goal is for the code generation layer to do the heavy lifting when a provider updates to a new major, minor, or patch version of Entity Framework Core Upstream.
For detailed information please read and comment on the OpenEF Abstract
cc @ajcvickers @roji @ErikEJ please add anyone else in the community that you may think may be interested as well!

/cc @divega

@caleblloyd: @ajcvickers and I had a conversations about this and here are some observations we wanted to share with you:

We agree that the there was a lot of churn in the provider model between 1.x and 2.0. We however don’t expect the same level of churn to happen again in the foreseeable future.
We agree that despite sharing a lot of common implementation code in the base relational provider, there is some boilerplate code that essentially all providers need to have a copy of. However it is hard to generalize because where any two given providers may implement the same behavior, a third provider may need to do something completely different.
Some of the new features that we have added in minor releases (for example, value converters in 2.1) require changes on providers, but we have tried to add them in such a way that existing providers degrade gracefully (that is the the feature just isn't enabled, but the rest of the provider continues to work, barring the issue with usage of internal APIs that we have already discussed).

Given all of that, we believe that the general approach you describe could have some benefits, but the net gain is going to depend on several factors, e.g.:

Churn in boilerplate/copied implementation code in future releases being higher than we anticipate
Applicability of the SQL Server implementation to multiple providers

In the shorter term, we are still thinking that other means can yield higher benefits, for example:

Setting up spec tests on the existing Pomelo MySQL provider and fixing issues found
Trying to identify more opportunities for promoting repeated implementation code to the base Core or Relational implementation
Trying to identify gaps in spec tests so that they can help inform all providers writers of what is the complete set of behaviors they need to implement.

I also wanted to share a personal opinion on the name in your proposal: To me OpenEF is confusing, because it conveys an open source flavor of EF, only that EF and EF Core are already open source! As a matter of fact, we used OpenEF to talk internally about EF6 for a while :smile:

Agree with Diego! (Link to #11305 is broken, btw)

Thanks for the feedback @divega and @ajcvickers!

[net gain will depend on] Churn in boilerplate/copied implementation code in future releases being higher than we anticipate

True.  I think it will still be helpful to automatically pick up small changes though.   It will still help the root issue of changes getting into Upstream EF that a provider misses.

[net gain will depend on] Applicability of the SQL Server implementation to multiple providers

SQL Server will be the base for OLTP providers.  The Abstract talks about "feature gates" that will be put in place to optionally strip specific functionalist (memory optimized tables, HiLo sequence, etc.).  This should allow providers to pick features that they want in their base.
Once Upstream provides CosmosDB #8443 that could likely be used as the base for NoSQL providers.

[short term benefit] Setting up spec tests on the existing Pomelo MySQL provider and fixing issues found

I've begun investigating Code Generation and Tests are very difficult to pull out of EF Upstream to use as a template.  The test projects are not published as packages (would be helpful if they were in a MyGet feed), have a lot of dependencies on each other, and reference internal code.
It'd be nice for OLTP providers to be able to copy EFCore.SqlServer.FunctionalTests and EFCore.SqlServer.Tests as a starting point.  AutoEF will provide that, but there are things we could change Upstream to make it easier.

To me OpenEF is confusing, because it conveys an open source flavor of EF, only that EF and EF Core are already open source!

This thought crossed my mind initially as well.  I've changed the name of the project to AutoEF, hopefully that is more clear!

Just wanted to drop my 2 cents here as well...
I've been playing catch-up with EF Core (and .NET Core) since the early days of beta6 (or even beta5), so I'm very familiar with the pain of having to resynchronize. @caleblloyd I understand very well where you're coming from.
At the same time, the situation has changed quite a lot, and the EF Core universe seems to be stabilizing more and more. I rarely find myself having having to deal with dramatic breaking changes, and what does happen is relatively easy to grasp and adapt.
In addition, as has been mentioned above, EF Core do publish the specification test suite. This is an invaluable resource for keeping up to date with EF Core and making sure your provider behaves properly. Fully implementing the suite is no easy task, but it can be done very incrementally, skipping test suites which you haven't gotten around to yet.
At the very least, I'd argue that implementing the specification test suite should happen anyway and should come before a code generation effort - which may still make sense after significant specification coverage is achieved (or it may not).
Finally, I'm a bit skeptical about a code generation approach here because some provider-specific code does need to be mixed into the generated classes, and it's not easy to manage this kind of thing. For services where no MySQL-specific behavior is needed, you can simply use the Relational base class (this is the default), so in any case you're only required to implement services where you have your own logic. And for those services my hunch is that you'd spend more time working on a code-generation which successfully mixes boilerplate and MySQL-specific code than you would on normal maintenance. But I may be wrong on this (or not understanding exactly what you're planning).

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


Is there a way to convert a command line to API commands?

I've been using this command line, which is pretty gnarly:
-c:v:0 libx264 -crf 23 -x264-params keyint=50:min-keyint=25:scenecut=-1 -maxrate:0 1300k      #-bufsize:0 2600k -preset faster -tune zerolatency -profile:v Main -level 3.1 -c:a:0 aac      #-ar:0 44100 -b:a:0 128k -flags +global_header -f flv rtmp://<IP_ADDRESS>:1935/live/abc123
Is there a simple way to convert this to ffmpeg-python syntax?

you should be able to just use the parameters as kwargs.
stream = ffmpeg.input("input.mp4")
stream = ffmpeg.output(stream, 'rtmp://<IP_ADDRESS>:1935/live/abc123', **{'c:v:0': 'libx264', 'crf': 23, 'x264-params': 'keyint=50:min-keyint=25:scenecut=-1', 'maxrate:0': '1300k' , 'bufsize:0': '2600k', 'preset': 'faster', 'tune': 'zerolatency', 'profile:v': 'Main', 'level': '3.1', 'c:a:0': 'aac', 'ar:0': '44100', 'b:a:0': '128k', 'flags': '+global_header', 'f': 'flv'})
stream.run()

this would turn into
ffmpeg -i input.mp4 -f flv -ar:0 44100 -b:a:0 128k -bufsize:0 2600k -c:a:0 aac -c:v:0 libx264 -crf 23 -flags +global_header -level 3.1 -maxrate:0 1300k -preset faster -profile:v Main -tune zerolatency -x264-params keyint=50:min-keyint=25:scenecut=-1 rtmp://<IP_ADDRESS>:1935/live/abc123

Thanks! This connected right up and started streaming.
I'm getting weird pauses, and the stream drops between files, I'll still have to sort those issues. I've been using ffplayout to feed owncast for a few weeks now, so I know my platform is stable, I just need to figure out why the stuttering is happening and how to better switch between files.


Add ignore_deprecated flag to APIClient

The API client currently ignores any endpoints with a deprecation warning. This means that endpoints effectively cannot be deprecated-- once they are tagged deprecated, they are inaccessible from the client.
One option would be to automatically pull in these endpoints, which would allow for deprecation, but would make deprecated endpoints visible to new users, which may not be desirable.
The alternative I'd propose is to add an ignore_deprecated flag when instantiating the client, which defaults to True. This means that existing code based on newly deprecated endpoints would still break, but could be updated to work until the endpoint is removed entirely.

H/t @mheilman for raising this issue


Fix remote-window sizing

@keybase/react-hackers
Commit cdad99c21 removed globalStyles.windowBorder, but it was still being used by desktop/renderer/remote-component-helper.js to set window height, with the result that we crash while trying to set height.  On Linux this gave me an updater dialog that wasn't tall enough to contain the update buttons, and couldn't be resized to include them.
Because of this I paused the build bot, but I think this actually went out to users already yesterday.
This PR fixes it by cherry-picking in a fix (to just not use windowBorder anymore) from @chrisnojima's  #2428 PR.

:+1:

Any thoughts on a good way to get an updater popup from master?

You can run an old version and run your daemon in prod mode and do a
keybase update check I think
On Thursday, March 24, 2016, Chris Ball<EMAIL_ADDRESS>wrote:

Any thoughts on a good way to get an updater popup from master?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/keybase/client/pull/2444#issuecomment-200916027

and use $EDITOR "$(keybase config info)" to remove auto update if you had set it

and you can use keybase update check --force to force the update (even if you are already running latest, I think)


For...In Loop Converts keyof T to string

TypeScript Version:  2.8.3, 2.9.0-dev.20180405

Search Terms: for in keyof string
Code
interface Something {
    a: string,
    b: number,
}

function doSomething<T extends Something> (obj : T, keys : (keyof T)[]) {
    //For some reason, `k` is resolved to `string`
    for (let k in keys) {
        //Type 'string' is not assignable to type 'keyof T'.
        //Type 'string' is not assignable to type '"a" | "b"'.
        const key : keyof T = k;
        console.log(obj[key]);
    }
}

Expected behavior:
k should be of type keyof T
Actual behavior:
k is string
Playground Link: Link here
Related Issues:

Try it in the node.js console:
for (let k in ["a", "b", "c"]) console.log(typeof k, k)

Prints: string 0, string 1, string 2. A for-in lop loops over the keys of an object; to iterate over an array use a for-of loop.

Ugh, I knew I was forgetting something. My bad. I figured this out 12 seconds after you posted this. Sorry!


readme -- with space for community examples

ooops, did I miss this one? Would be happy to merge but might need to be refactored now?


RFC - Implementing alloying recipes in json

Hello folks. I'm very excited that EnderIO is coming back. I personally had been working on an EnderIO re-write (though I wasn't very far). However, I discovered this project and I want to help contribute here instead. :)
I found #54 , and I thought that would be a nice starting point. However, in looking at the current recipe implementation, recipes are registered in an event hook.
This works fine. But I'm wondering if you all would be interested in instead defining them as json in data instead. This would allow modpack developers to more easily change recipes to better fit their pack.
Is your feature request related to a problem? Please describe.
As described above, the recipes are described in code, rather than as data. This makes it harder for non-coders to modify / tweak recipes. Both for people wanting to help with the project, as well as modpack creators.
Describe the solution you'd like
Alloying recipes are defined as json, similar to other recipes in Minecraft.
I did this in EnderIO-Reforged, and it should be fairly straightforward to implement here as well.
Example recipe
Recipe registration
Describe alternatives you've considered
An alternative is to keep it as is :)

Howdy! Thanks for coming along and wanting to contribute over here, and nice work so far on your own rewrite!
We do actually have JSON recipes :) The event hook you've found is actually where we register the data generator which will create all of our builtin JSON recipes. You can still use a JSON file to add custom recipes with datapacks.
Thanks a lot for coming along and having a look though!


SpellIDs not converting on latest version

Have been testing new BFA macro's example import code:
dqJSbaWsuuVveTnGMnrUjQYVaCBjStb7LA3kSFjnmuXVfAGqLmurYGLYWffheL4yQ64qvAHOuwkuPwmuflxQEOi8uslduphYefvnvqMSO00rEMI66e1gHQQTcvyZOK2ourpMWLvAAs0Hv5BOsNgkJgfmEOQCsuOxJICnuvNxrwhkv3vKACIk73qo8wtmvKFlIoaBiRqN0oiK1h(N)h2A(L1twIC4TYImXqSBnXubwFsGlwgzLXgw1mRGX8oadcAL3j6rCSDewCGmKdVHC4TcioevBAuwQ2uQJX06aSvaXHOA75uo)GomBfqCiQ2aZb6qPvaXHOA75W)5w6aFRaIdr12ZH)ZT0bqRaIdr1gmy5pZXkZ7eUxP9qRHmzvPnd(LhccloSQlEL3bHDswzENs1xeYqo8wbehIQTKfXSSJyaJvkDTbdw(CZ5aSvaXHOAlzrml7cQlLU2Gb5)546WSvGmlDeDcMQTKl(WqekTjRPIiI3j6rdzYAQ(Y7e9OHmznrSaphz2mzYkVBiFsmoOTJZDqyXHzZKjBa
When doing so, the code imports as follows: https://imgur.com/a/uxvjkLk
When working with the creator of the macro, this is how it should import: https://imgur.com/a/0bDups0
No SpellID macro's are converting on my client. Current BFA build, and latest version of GSE: https://wow.curseforge.com/projects/gse-gnome-sequencer-enhanced-advanced-macros/files/2564701

That macro works for me and is built into beta11 as SAM_DEMO
TimothyLuke

On 27 May 2018, at 10:17 am, Respect1767<EMAIL_ADDRESS>wrote:
Have been testing new BFA macro's example import code:
dqJSbaWsuuVveTnGMnrUjQYVaCBjStb7LA3kSFjnmuXVfAGqLmurYGLYWffheL4yQ64qvAHOuwkuPwmuflxQEOi8uslduphYefvnvqMSO00rEMI66e1gHQQTcvyZOK2ourpMWLvAAs0Hv5BOsNgkJgfmEOQCsuOxJICnuvNxrwhkv3vKACIk73qo8wtmvKFlIoaBiRqN0oiK1h(N)h2A(L1twIC4TYImXqSBnXubwFsGlwgzLXgw1mRGX8oadcAL3j6rCSDewCGmKdVHC4TcioevBAuwQ2uQJX06aSvaXHOA75uo)GomBfqCiQ2aZb6qPvaXHOA75W)5w6aFRaIdr12ZH)ZT0bqRaIdr1gmy5pZXkZ7eUxP9qRHmzvPnd(LhccloSQlEL3bHDswzENs1xeYqo8wbehIQTKfXSSJyaJvkDTbdw(CZ5aSvaXHOAlzrml7cQlLU2Gb5)546WSvGmlDeDcMQTKl(WqekTjRPIiI3j6rdzYAQ(Y7e9OHmznrSaphz2mzYkVBiFsmoOTJZDqyXHzZKjBa
When doing so, the code imports as follows: https://imgur.com/a/uxvjkLk
When working with the creator of the macro, this is how it should import: https://imgur.com/a/0bDups0
No SpellID macro's are converting on my client. Current BFA build, and latest version of GSE: https://wow.curseforge.com/projects/gse-gnome-sequencer-enhanced-advanced-macros/files/2564701
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

It is not so much the macro, it is the same for me with any coded macro like the example. The code imports fine, however it does not convert the SpellID's as per the screenshots.

Does your character know those spells?
TimothyLuke

On 27 May 2018, at 1:12 pm, Respect1767<EMAIL_ADDRESS>wrote:
It is not so much the macro, it is the same for me with any coded macro like the example. The code imports fine, however it does not convert the SpellID's as per the screenshots.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I just can’t replicate it.  I can’t cause this to happen.
TimothyLuke

On 27 May 2018, at 2:49 pm, Respect1767<EMAIL_ADDRESS>wrote:
Yeah. This is across several characters and various macros. It's not
converting the spell IDs.
That's why I raised the bug.
On Sun, May 27, 2018, 2:59 PM Timothy Minahan<EMAIL_ADDRESS>wrote:

Does your character know those spells?
TimothyLuke

On 27 May 2018, at 1:12 pm, Respect1767<EMAIL_ADDRESS>wrote:
It is not so much the macro, it is the same for me with any coded macro
like the example. The code imports fine, however it does not convert the
SpellID's as per the screenshots.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TimothyLuke/GnomeSequencer-Enhanced/issues/408#issuecomment-392305406,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Al0tcNd59GfobK1W2llA7149fIU-laBpks5t2jKsgaJpZM4UPGlS
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Don't know what to tell you, happy to screenshare the issue via discord so you can see for yourself what's going on if you want?

So have no idea why, but deleted my WTF and Interface folders, did a single install of GSE by itself. Works fine.
No different the previous revision of my attempt before, however third attempt at this and it worked so not sure why. Same install of GSE and all.

There were some fixes between the Betas that would work from 2.2.08 -> 2.3.00 but they may have had some left over stuff between the Betas.  I will keep an eye on it though.
TimothyLuke

On 27 May 2018, at 3:35 pm, Respect1767<EMAIL_ADDRESS>wrote:
So have no idea why, but deleted my WTF and Interface folders, did a single install of GSE by itself. Works fine.
No different the previous revision of my attempt before, however third attempt at this and it worked so not sure why. Same install of GSE and all.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Subaru: Add FW for 2020 Subaru Forester

Car
2019 Subaru Forester, thanks to Puttputt7!
Route
7120a7c40c69302b/2024-03-06--04-49-59

Can you check with the bot?

only 2 segments uploaded

Dongle, platform, VIN
Name from VIN 🆚 CarInfo
Segments
Bad seg tags
Good seg tags

7120a7c40c69302bSUBARU FORESTER 2019JF2SKADC9........
None 🆚None
1 routes, 2 segments

- all lat active: 0

Dongles to re-run category: 7120a7c40c69302b

@jyoung8607 can you get the user to drive a bit more? The lateral accel factor is 3.0 instead of our offline 2.0


[TESTING] mobile: Switch to IPv6 for the test server

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest


[Bug]: Export result set in Excel format, there is no content in the exported file

ODC version
odc423
OB version

What happened?

What did you expect to happen?
There is data in the exported result set
How can we reproduce it (as minimally and precisely as possible)?
Export result set in Excel format, export
Anything else we need to know?
No response
Cloud
No response

pass


In case of begin create we should return result

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[x] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

This change is

 https://github.com/Azure/azure-sdk-for-python/pull/873

 https://github.com/Azure/azure-sdk-for-node/pull/1973

 https://github.com/Azure/azure-sdk-for-ruby/pull/570


Support Python 3

What does this PR do?
This Supports Python 3 for the Process Check.
Motivation
We have to hop onto the 🐍3⃣🚂
Review checklist

[x] PR has a meaningful title or PR has the no-changelog label attached
[x] Feature or bugfix has tests
[x] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
[ ] If PR adds a configuration option, it has been added to the configuration file.

Additional Notes
This is a very complex check. I tested it as best I could and looked over the logic, but someone else should make sure I didn't miss anything. It would have been very easy to miss something.

Codecov Report

Merging #2812 into master will decrease coverage by 5.46%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2812      +/-   ##
==========================================
- Coverage   84.75%   79.28%   -5.47%
==========================================
  Files         655        5     -650
  Lines       37618      478   -37140
  Branches     4523       82    -4441
==========================================
- Hits        31883      379   -31504
+ Misses       4403       69    -4334
+ Partials     1332       30    -1302


Support named exports in esm modules

Description
This PR adds the ability to use named exports in type: module node environments:
import { sign } from "jsonwebtoken";

It accomplishes this via https://github.com/nodejs/cjs-module-lexer
Testing
I added a test for this - unfortunately it will fail the lint parsing because it still supports node versions < 12.
Once the linting is updated, the tests will pass in all node >= 12.

[x] This change adds test coverage for new/changed/fixed functionality

Checklist

[ ] I have added documentation for new/changed functionality in this PR or in auth0.com/docs
[ ] All active GitHub checks for tests, formatting, and security are passing
[ ] The correct base branch is being used, if not master

@jakelacey2012 any chance you can take a look at this?


⚠ GTru has degraded performance

In f5c5442, GTru ($GTRU) experienced degraded performance:

HTTP code: 200
Response time: 12512 ms

Resolved: GTru performance has improved in ea2e199 after 20 minutes.


Selection requires double click if onClick method provided

Hello,
If I provide an onClick method to get the selected rating, it requires another click to the same value although it gets the rating in the first click. You can check it from this link:
https://stackblitz.com/edit/react-buosnw
In summary, if you click a rating, it is not turning to a full symbol. If you click the same rating again, then it turns to a full symbol. This is not happening if there is no onClick method.
Thanks

For the people who are looking for a solution to this problem, my workaround is setting the initialRating in onClick.

I have the same issue, would you share some sample code because in onClick we can't access to event

@amastaneh  Here is the code:
`
const [selectedRating, setSelectedRating] = useState();
const onRatingSelected = selectedValue => {
setSelectedRating(selectedValue);
};
`


[Question] How do I specify a custom SSH port?

Absolutely fantastic tool, thanks for investing all the time into this it takes to keep something like this afloat.
My server uses a non-standard SSH port.  Currently my config looks like:
    'connections'      => [
        'production' => [
            'host'      => 'xx.xx.xxx.xx',
            'username'  => 'myUser',
            'password'  => '',
            'key'       => '/path/to/key',
            'keyphrase' => '',
            'agent'     => '',
            'db_role'   => true,
        ],
    ],

I've tried adding a port entry to this array and also tried changing the host to be xx.xx.xxx.xx:324 with no luck.  Searching the source code for port I'm not able to find much.  Any advice on how I can accomplish this?

The solution is to go the route of xx.xx.xxx.xx:324... something else was incorrect with my authentication credentials.


Add Ray cluster REST API support in test support package

Issue link
Part of https://github.com/opendatahub-io/distributed-workloads/issues/63
What changes have been made
Adjustments in e2e test support package to provide support for new ODH integration test - https://github.com/opendatahub-io/distributed-workloads/pull/71
Verification steps
The changes can be verified by running ODH integration test, see instructions in https://github.com/opendatahub-io/distributed-workloads/pull/71
Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[x] Testing is not required for this change

It is enough to run the local e2e tests (part of the PR check) to make sure nothing is broken.

seems that k8s api upgrade is too big change for a codebase, need to find compatible OpenShift client versions (dependency hell strikes back)

/lgtm
/approve


Admittance with filters

Re-introduced filters to the admittance_controller as originally done in https://github.com/ros-controls/ros2_controllers/pull/382. Improved testing, variable names and comments.
Depends on https://github.com/ros-controls/control_toolbox/pull/152 and https://github.com/ros-controls/control_toolbox/pull/153

@please open this PR upstream and not here

closed in favor of https://github.com/ros-controls/ros2_controllers/pull/560