Error: NormalModuleFactory.beforeResolve is no longer a waterfall hook, but a bailing hook instead. Do not return the passed object, but modify it instead. Returning false will ignore the request and results in no module created. at: node_modules\webpack\lib\NormalModuleFactory.js:644:11

Context
I updated my webpack to 5.0.0.
I get this error in my terminal, when I try to run the build using  command "webpack-dev-server --config (FilePath) --inline --progress --profile".
Error: NormalModuleFactory.beforeResolve is no longer a waterfall hook, but a bailing hook instead. Do not return the passed object, but modify it instead. Returning false will ignore the request and results in no module
Expected behaviour
I want my build to run after upgrading the webpack.
software tools versions
Angular CLI: 8.3.9
Node: 14.17.0
OS: win32 x64
Angular: 5.2.11
my dep and devdep
"dependencies": {
		"@angular/animations": "^5.2.0",
		"@angular/cdk": "^5.2.0",
		"@angular/common": "^5.2.0",
		"@angular/compiler": "^5.2.0",
		"@angular/core": "^5.2.0",
		"@angular/forms": "^5.2.0",
		"@angular/http": "^5.2.0",
		"@angular/material": "^5.2.0",
		"@angular/material-moment-adapter": "^5.2.0",
		"@angular/platform-browser": "^5.2.0",
		"@angular/platform-browser-dynamic": "^5.2.0",
		"@angular/router": "^5.2.0",
		"@microsoft/signalr": "^3.1.4",
		"@ngx-translate/core": "^9.1.1",
		"@ngx-translate/http-loader": "^2.0.1",
		"angular-file": "^0.5.4",
		"angular-mentions": "1.1.3",
		"color-hash": "^1.0.3",
		"hammerjs": "^2.0.8",
		"ng2-pdf-viewer": "5.2.3",
		"ngx-web-worker": "^7.0.0",
		"pusher-js": "^5.0.0",
		"rxjs": "^5.5.10",
		"zone.js": "0.8.19"
	},
	"devDependencies": {
		"@angular/cli": "~1.7.4",
		"@angular/compiler-cli": "^5.2.0",
		"@angular/language-service": "^5.2.0",
		"@ngtools/webpack": "^7.3.2",
		"@types/core-js": "^0.9.46",
		"@types/highcharts": "^5.0.34",
		"@types/jasmine": "2.6.0",
		"@types/jasminewd2": "~2.0.2",
		"@types/lodash": "4.14.108",
		"@types/node": "9.6.57",
		"@types/rx": "^4.1.1",
		"@types/tapable": "^0.2.5",
		"@types/webpack": "^3.8.7",
		"angular2-template-loader": "^0.6.2",
		"autoprefixer": "^9.4.9",
		"awesome-typescript-loader": "^5.0.0",
		"codelyzer": "^4.0.1",
		"compression-webpack-plugin": "^0.4.0",
		"concurrently": "^3.5.1",
		"copy-webpack-plugin": "^4.5.1",
		"core-js": "^2.4.1",
		"css-loader": "^0.28.11",
		"csvtojson": "^2.0.3",
		"enhanced-resolve": "^3.3.0",
		"file-loader": "^1.1.11",
		"highcharts": "^6.2.0",
		"html-loader": "^0.5.5",
		"html-webpack-exclude-assets-plugin": "0.0.7",
		"html-webpack-plugin": "^3.2.0",
		"jasmine": "^3.2.0",
		"jasmine-core": "~2.8.0",
		"jasmine-spec-reporter": "~4.2.1",
		"jquery": "^3.3.1",
		"json-loader": "^0.5.7",
		"karma": "^2.0.5",
		"karma-chrome-launcher": "~2.2.0",
		"karma-cli": "^1.0.1",
		"karma-coverage-istanbul-reporter": "^1.2.1",
		"karma-jasmine": "^1.1.2",
		"karma-jasmine-html-reporter": "^0.2.2",
		"karma-junit-reporter": "^1.2.0",
		"karma-scss-preprocessor": "^3.0.0",
		"karma-sonarqube-reporter": "^1.2.3",
		"karma-sourcemap-loader": "^0.3.7",
		"karma-webpack": "^3.0.5",
		"lodash": "4.17.10",
		"mini-css-extract-plugin": "^0.5.0",
		"ngx-carousel": "^1.3.5",
		"node-sass": "^4.11.0",
		"optimize-css-assets-webpack-plugin": "^4.0.2",
		"path": "^0.12.7",
		"postcss-loader": "^2.1.5",
		"prettier": "^1.16.4",
		"protractor": "~5.1.2",
		"puppeteer-core": "^1.10.0",
		"raw-loader": "^0.5.1",
		"rimraf": "^2.6.2",
		"sass-loader": "^7.1.0",
		"source-map-loader": "^0.2.3",
		"style-loader": "^0.21.0",
		"terser-webpack-plugin": "^1.2.3",
		"to-string-loader": "^1.1.5",
		"ts-loader": "^4.0.0-beta.0",
		"ts-node": "~4.1.0",
		"tslint": "~5.9.1",
		"typescript": "~2.5.3",
		"url-loader": "^1.0.1",
		"webpack": "^4.29.5",
		"webpack-bundle-analyzer": "^3.3.2",
		"webpack-cli": "^3.2.3",
		"webpack-dev-server": "^3.1.14",
		"webpack-merge": "^4.2.1",
		"write-file-webpack-plugin": "^4.3.2",
		"postcss-rtl": "1.7.3"
	}
}

I understand that, that I am getting the error from webpack/lib/NormalModuleFactory.js after resolving the beforeResolve hook in the line where typeof result === object
this.hooks.beforeResolve.callAsync(resolveData, (err, result) => {
			if (err) {
				return callback(err, {
					fileDependencies,
					missingDependencies,
					contextDependencies
				});
			}
			if (result === false) {
				return callback(null, {
					fileDependencies,
					missingDependencies,
					contextDependencies
				});
			}
			if (typeof result === "object") //throws an error
				throw new Error(deprecationChangedHookMessage("beforeResolve"));

			//some lines of codes

			});
		});

I believe that I am getting an error from angular-cli, please provide me a fix

@MohammedAejazAhmed, custom webpack configurations are not supported by the Angular team.
It also appears that you are using a no longer supported version of Angular. Please see: https://angular.io/guide/releases#support-policy-and-schedule


Make the steps diagram honor the theme

Description

public/assets/get_started.svg was an atrocious 18KB asset; cleaned it up to 3.5KB.
Created 2 layers out of get_started.svg.
OSD doesn't provide svgr or anything for inlining SVGs so can't use currentColor; I have put it in the source SVGs anyway in case it is added in the future.
This uses CSS masking.

Issues Resolved
#1527 - Part 1
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Based on this comment, Please don't merge until I can validate it across relevant browsers. I have marked this pull request a draft, please let us know if we can help, thanks!

@peternied are these tests supposed to be failing?

@RyanL1997 I believe you were looking into these failures, what is the issue where we are tracking these failures?

@AMoo-Miki The failing checks now are related to compilation issues in the backend security plugin repo. There's an open PR here: https://github.com/opensearch-project/security/pull/3091
There's potentially another issue with some selenium tests and the latest version of FF: https://github.com/opensearch-project/security-dashboards-plugin/pull/1533#issuecomment-1663142249
Looking into the FF issue now. I will re-run the failed checks when the backend PR is merged and also reply back if any rebasing is needed.
Thank you for the PR. This change looks good to me.

Is there anything more I can do for you on this PR?

Nothing from me. This looks good to merge.


[WIP] Scripts to import borrowed titles and borrowing events from lending card xml

Codecov Report

Merging #82 into develop will increase coverage by 0.03%.
The diff coverage is 98.64%.

@@             Coverage Diff             @@
##           develop      #82      +/-   ##
===========================================
+ Coverage    98.51%   98.55%   +0.03%
===========================================
  Files           78       85       +7
  Lines         3242     3590     +348
===========================================
+ Hits          3194     3538     +344
- Misses          48       52       +4

Impacted Files
Coverage Δ

...grations/0005_people_address_to_account_address.py
62.5% <ø> (ø)
:arrow_up:

mep/settings.py
95.23% <ø> (ø)
:arrow_up:

mep/people/tests/test_xmlmodels.py
100% <ø> (ø)
:arrow_up:

.../accounts/migrations/0015_borrow_event_rel_item.py
100% <100%> (ø)

...ep/accounts/migrations/0018_merge_20180418_1607.py
100% <100%> (ø)

mep/books/views.py
100% <100%> (+100%)
:arrow_up:

...ep/books/migrations/0002_refactor_item_creators.py
100% <100%> (ø)

mep/books/migrations/0003_initial_creator_types.py
100% <100%> (ø)

mep/accounts/admin.py
98.47% <100%> (+0.15%)
:arrow_up:

mep/accounts/models.py
99.58% <100%> (+0.11%)
:arrow_up:

... and 18 more

Continue to review full report at Codecov.

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


Fresnel - possible off-by-one bug in fft_coords()?

I am not totally sure about this one... Here is a slight difference in behavior between the Wavefront.coordinates function and fresnel.Wavefront.fft_coords. I am not sure if this is intentional or accidental?
Compare:
In [9]: wf = fresnel.Wavefront(2.4*u.m, wavelength=675e-9, npix=512, oversample=2)
In [10]: wf.fft_coords()[1][0]
Out[10]: array([-4.8     , -4.790625, -4.78125 , ...,  4.771875,  4.78125 , 4.790625])

versus:
In [11]: wf.coordinates()[1][0]
Out[11]: array([-4.7953125, -4.7859375, -4.7765625, ...,  4.7765625,  4.7859375, 4.7953125])

In the latter case, I took care to make sure that the output coordinates are centered on the optical axis; i.e. the positive and negative values are symmetric. This is not the case for what fft_coords returns.
The difference in code is just 1:
        x -= (shape[1] - 1) / 2.0   # in Wavefront.coordinates
        x-= (self.shape[1])/2.      # in fresnel.Wavefront.fft_coords

I tried changing fft_coords to match the behavior of coordinates. After doing do, the propagation still seems to work. However the test_CircularAperturePropagation() then fails, because the peak value is not as expected. Where did the expected value "3.3633280006866424" come from?
I am worried that it is inconsistent as currently coded, that as a result the center (x,y)=(0,0) for e.g. a CircularAperture is not the same as the center used in calculating the radial phase term in a plane-to-plane propagation.

Digging into this a bit more, with the current fresnel code (without the -1), the output wavefront in the CircularAperturePropagation test case is symmetric around the intersection between 4 pixels at the middle of the array, coordinates (1023.5, 1023.5).  All 4 of those pixels have the same value.
On the other hand, with the -1 included to be similar to Wavefront.Coordinates, then the output wavefront from the test case is not symmetric. One of the pixels is brighter than the others.
So that seems to confirm the code is correct as-is. This only gets used in the PTP and Direct propagations. Having thought about the spatial frequencies as output by the FFT it makes sense to me that this is the case.
Moral of the story? The code is correct, but the comment that ft_coords "Replaces poppy.wavefront.coordinates()" is not. We are going to have to keep these as separate functions.
Thoughts?

Yep, you got to the bottom of it. The docstring comes from the fact that I originally used Wavefront.Coordinates() and only in testing discovered the difference and "replaced" it with the custom function.
The test value should probably be rounded, it's just the value I was getting at the time I wrote the test, and only within +-0.1 of the value in the cited Anderson and Enmark figure.


Support for private registry in templates

No support for local/private registries in templates.
Currently only supports for pulling images from DockerHub. We need to be able to pull image from our custom/private registry.
Technical details:

Portainer version: 1.11.4
Portainer Docker image tag (latest/arm/windows...): latest
Target Docker version (the host/cluster you manage): 17.03.0-ce
Target Swarm version (if applicable): NA
Platform (windows/linux): RPI
Browser: NA

Hi @raulriverouria
Portainer templates supports custom/private registries as long as these are not behind an authentication system.
See: http://portainer.readthedocs.io/en/stable/templates.html#registry
Is that what you were searching for?

Yes :). My apologies because I did not see that field :(.
But now, another question: Any way to map host directories inside docker like -v option? Example:
docker run -v "/host/path:/container/path" ...
If I use the ':' char inside a volume definition, I get an "invalid mode" error. My trials are with:
...     "volumes": [         "/home/docker/data/web/php/etc/php/7.0/apache2:/etc/php/7.0/apache2",         "/home/docker/data/web/php/etc/php/7.0/cli:/etc/php/7.0/cli",         "/home/docker/data/web/nginx/usr/local/nginx/conf:/usr/local/nginx/conf",         "/home/docker/data/web/apache/etc/apache2/apache2.conf:/etc/apache2/apache2.conf",         "/home/docker/data/web/apache/etc/apache2/apache2-editor.conf:/etc/apache2/apache2-editor.conf",         "/home/html:/home/html",         "/usr/local/etc/SSL:/usr/local/etc/SSL",         "/dev/log:/dev/log" ...

@raulriverouria ah sorry, this will be available in 1.12 (it's already merged in the develop branch) but I merged this part of the documentation and it should have been added in the docs for 1.12.
I'll close this issue, stay tuned for the 1.12 release soon.

@deviantony hi, my problem is  the private registries of my company  need an authentication(username&password), how do i use app templates in such condition?

@MagicSong see https://github.com/portainer/portainer/issues/1554 for the related discussion, it's not available yet.


Improve readme

Add initial diagram
WIP

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 42.976%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
569

Relevant Lines:
1324

💛  - Coveralls


pulumi convert: Handle multiple provider definitions

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
When we use pulumi convert for provider documentation, we would like translation to work, even in the case of (slightly) incorrect input.
When generating code for provider examples, if an example has multiple providers defined, pulumi convert currently fails with the following error:
pulumi convert --from terraform --language pcl ## this is the quick&dirty command-line equivalent of what the bridge does here
Converting from terraform...
error: /Users/guin/go/src/github.com/pulumi/terraform-programs/provider-config/main.tf:17,1-19: Duplicate provider configuration; A default (non-aliased) provider configuration for "harness" was already given at /Users/guin/go/src/github.com/pulumi/terraform-programs/provider-config/main.tf:10,1-19. If multiple configurations are required, set the "alias" argument for alternative configurations.
error: conversion failed

TF program:
terraform {
  required_providers {
    harness = {
      source = "harness/harness"
    }
  }
}

#Configure the Harness provider for First Gen resources
provider "harness" {
  endpoint   = "https://app.harness.io/gateway"
  account_id = "...."
  api_key    = "......"
}

#Configure the Harness provider for Next Gen resources
provider "harness" {
  endpoint         = "https://app.harness.io/gateway"
  account_id       = "...."
  platform_api_key = "......"
}

from these upstream docs
The code is technically incorrect and not usable as such; however it would be great if we could enable a docsgen setting where the conversion is done regardless.
Affected area/feature
Provider example translation.

I'm curious if you have a sense or any data of how common this is. Would it help unlock a bunch of missing examples in any of the tier 1 providers, for example?


[New Feature]: High Score Tracking

🎮 feature Request
Optionally, implement a high score feature to keep track of the player's best performances. Display the highest score achieved by the player either on the game screen or in a separate high score table.
Point down the features
assign me under gssoc
Select program in which you are contributing
No response
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

please assign this issue to me under GSSOC24

Please raise any other issue, i'll assign you
If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created separate channals for all projects...
Thank you :)


webpack.config works on Windows & OS X but not on Ubuntu Linux

I'm having this exception only on Linux OS.
The following configuration work on Windows and OS X but not on Ubuntu Linux.
webpack.comfig (as can be seen here: https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/631)
var ExtractTextPlugin = require('extract-text-webpack-plugin');
var blueETP = new ExtractTextPlugin('blue.scss');
var baseETP = new ExtractTextPlugin(''base.scss');
  module: {
    rules: [{
        test: /base.scss$/,
        use: baseETP.extract({
          fallback: 'style-loader',
          use: ['css-loader', 'sass-loader']
        })
      },{
        test: /blue.scss$/,
        use: blueETP.extract({
          fallback: 'style-loader',
          use: ['css-loader', 'sass-loader']
        })
      }],
  plugins: [blueETP,baseETP]
  ....

Exception:

ERROR in ./base.scss
Module build failed:
@import 'main/app-Layout/appLayout';
^
File to import not found or unreadable: main/app-Layout/appLayout.
Parent style sheet: .../css/2-modules/modules-fol.scss
in .../css/2-modules/modules-fol.scss (line 5, column 1)
@ ./app/app.js 3:2-34
@ multi (webpack)-dev-server/client?http://localhost:8081 webpack/hot/dev-server ./app/app.js

As you can see, for some reason it tries to include this file main/app-Layout/appLayout.

OS: 16.04.2-Ubuntu
NPM version: 5.5.1
Node version: 8.9.1
npm node-sass versions: 4.7.2

@Pavel-Durov can you provide minimum reproducible test repo? I use Ubuntu

@evilebottnawi thanks.
I tried to create a minimum reproducible test repo and I failed to reproduce it (although I still have it my major project).
I will investigate this behaviour, probably it has nothing to do with this plugin.
There is nothing that I can put my finger on - let's close this ticket :)

@Pavel-Durov anyway thank for issue!

It's a classic lowercase-uppercase path issue.
Nothing to do with extract-text-webpack-plugin


Rename IAttackBy/IAttackHand/IAfterAttack?

The naming dates back from SS13. I don't think it reflects the intended behavior well though.

I want to pick this up, can I use oranges suggestion it's my preferred one.

Oranges suggestions are fine probably.


Add log information calls

Proposed change

As described in #143, the IDoLogging interface does not contain methods to log informational message. This pull requests adds these methods. Also I fixed up some documentation. I did not find any existing tests, so I didn't add any additional tests.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #143

Checklist

[X] The code change is tested and works locally.
[X] Local tests pass. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[X] I have followed the [development checklist][dev-checklist]
[X] The code compiles without warnings (code quality chek)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

Thanks @BeeHiveJava for your contribution. Appreciates it!


Fixup the raspbian build

The sysroot we're using for raspbian had a bad symlink for the dynamic libm (it was absolute, but our sysroot was re-parented). This started causing problems once we were actually using libm symbols.

This has been merged into 3.14.1


[BUG] Unexpected Access to All Indices When .kibana Index Permission is Removed from Role Configuration

What is the bug?
When the .kibana index permission is removed from an OpenSearch role configuration, the user unexpectedly gains access to all indices rather than being restricted to specific index patterns defined in other permissions. Specifically, when the permission setting for .kibana is present, access is correctly limited to the specified "logstash-*" index patterns and the .kibana index. However, removing this permission unexpectedly broadens the user's access to all indices.
How can one reproduce the bug?
Steps to reproduce the behavior:

Define an OpenSearch role that includes index permissions for "logstash-*" and ".kibana".
Assign this role to a user, verifying that the user's access is correctly limited to "logstash-*" indices and the .kibana index.
Remove the index permission for .kibana from the role.
Observe that the user now has access to all indices, contrary to the intended restriction to "logstash-*" indices.

What is the expected behavior?
The expected behavior is for the user's access to be limited to the "logstash-*" index patterns as defined in the role's index permissions, regardless of whether the .kibana index permission is present or not. Removing the .kibana index permission should not affect access to other indices outside of those explicitly defined in the role.
What is your host/environment?

OS: Ubuntu 22.04 LTS
Version: Docker images 2.11.1
Plugins:

Do you have any additional context?
Here's the role configuration that leads to the described behavior:
resource "opensearch_role" "writer" {
  role_name   = "logs_writer"
  description = "Logs writer role"

  cluster_permissions = ["cluster:monitor/health", "cluster:monitor/state"]

  index_permissions {
    index_patterns  = ["logstash-*"]
    allowed_actions = ["write"]
  }

  // When this permission block is removed, the issue occurs.
  index_permissions {
    index_patterns  = [".kibana"]
    allowed_actions = ["indices:admin/", "indices:monitor/", "indices:data/*"]
  }

  tenant_permissions {
    tenant_patterns = ["global_tenant"]
    allowed_actions = ["kibana_all_write"]
  }
}

Hi @yoicomment, thank you for filing this issue. Based on your description I think you would best be served checking out https://forum.opensearch.org/ where you may be able to get some more specific guidance on how to best define the roles in your cluster. They can be a bit tricky to configure but are additive which is why you are experiencing the behavior you see.
Going to close this issue for now but please feel to reply/or reopen should the forum not be able to resolve your issue.

So, you're saying that is not a bug, but I have misconfigured this specific role?

#3905 i'm having the problem which is explained here


Thingibrowser dialogues do not open on Ubuntu 20.04 Cura 4.8.0

Ultimaker Cura - 4.8.0
Ubuntu - 20.04
Thingibrowser - 2.2.0
I am unable to open any of the dialogues in this plugin using the above versions. I am new to the Cura ecosystem so I might be missing something. Reinstalling and toggling the plugin on or off do not change the behavior.
Starting Cura from a terminal and trying this yeilds the following log:
Browse dialogue
QQmlComponent: Component is not ready
2020-12-06 14:32:32,000 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [578]: file:///home/routhinator/snap/cura-slicer/23/.local/share/cura/4.8/plugins/ThingiBrowser/ThingiBrowser/views/Thingiverse.qml:33:5: Type ThingiMain unavailable
2020-12-06 14:32:32,001 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [578]: file:///home/routhinator/snap/cura-slicer/23/.local/share/cura/4.8/plugins/ThingiBrowser/ThingiBrowser/views/ThingiMain.qml:15:5: Type ThingiHeader unavailable
2020-12-06 14:32:32,002 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [578]: file:///home/routhinator/snap/cura-slicer/23/.local/share/cura/4.8/plugins/ThingiBrowser/ThingiBrowser/views/ThingiHeader.qml:12:5: Type ServiceSelector unavailable
2020-12-06 14:32:32,002 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [578]: file:///home/routhinator/snap/cura-slicer/23/.local/share/cura/4.8/plugins/ThingiBrowser/ThingiBrowser/views/ServiceSelector.qml:4:1: Type EnhancedComboBox unavailable
2020-12-06 14:32:32,002 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [578]: file:///home/routhinator/snap/cura-slicer/23/.local/share/cura/4.8/plugins/ThingiBrowser/ThingiBrowser/views/EnhancedComboBox.qml:11:5: Cannot override FINAL property

Settings dialogue
QQmlComponent: Component is not ready
2020-12-06 14:32:47,054 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [578]: file:///home/routhinator/snap/cura-slicer/23/.local/share/cura/4.8/plugins/ThingiBrowser/ThingiBrowser/views/ThingiSettings.qml:41:13: Type ThingiSettingsItem unavailable
2020-12-06 14:32:47,055 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [578]: file:///home/routhinator/snap/cura-slicer/23/.local/share/cura/4.8/plugins/ThingiBrowser/ThingiBrowser/views/ThingiSettingsItem.qml:60:5: Type EnhancedComboBox unavailable
2020-12-06 14:32:47,055 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [578]: file:///home/routhinator/snap/cura-slicer/23/.local/share/cura/4.8/plugins/ThingiBrowser/ThingiBrowser/views/EnhancedComboBox.qml:11:5: Cannot override FINAL property

It seems that somehow the QML engine cannot deal with a FINAL property, causing a cascading import issue. Which version of Qt is running on your system? Another instance of Qt might interfere with the one shipped with Cura (in which this plugin was tested and should work fine). I am running on Ubuntu 20.04 myself and have not seen this issue with the Qt version that is packaged with Cura.

Might be some extra stuff in this list you don't need but didn't want to miss anything:
❯ dpkg -l | grep qt
'ii  libqt5core5a:amd64                         5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 core module
ii  libqt5dbus5:amd64                          5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 D-Bus module
ii  libqt5gui5:amd64                           5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 GUI module
ii  libqt5keychain1:amd64                      0.10.0-1build1                              amd64        Qt API to store passwords (QT5 version)
ii  libqt5network5:amd64                       5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 network module
ii  libqt5positioning5:amd64                   5.12.8+dfsg-0ubuntu1                        amd64        Qt Positioning module
ii  libqt5printsupport5:amd64                  5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 print support module
ii  libqt5qml5:amd64                           5.12.8-0ubuntu1                             amd64        Qt 5 QML module
ii  libqt5quick5:amd64                         5.12.8-0ubuntu1                             amd64        Qt 5 Quick library
ii  libqt5quickcontrols2-5:amd64               5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 Quick Controls 2 library
ii  libqt5quicktemplates2-5:amd64              5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 Quick Templates 2 library
ii  libqt5quickwidgets5:amd64                  5.12.8-0ubuntu1                             amd64        Qt 5 Quick Widgets library
ii  libqt5sensors5:amd64                       5.12.8-0ubuntu1                             amd64        Qt Sensors module
ii  libqt5sql5:amd64                           5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 SQL module
ii  libqt5sql5-sqlite:amd64                    5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 SQLite 3 database driver
ii  libqt5svg5:amd64                           5.12.8-0ubuntu1                             amd64        Qt 5 SVG module
ii  libqt5webchannel5:amd64                    5.12.8-0ubuntu1                             amd64        Web communication library for Qt
ii  libqt5webengine-data                       5.12.8+dfsg-0ubuntu1.1                      all          Web content engine library for Qt - Data
ii  libqt5webenginecore5:amd64                 5.12.8+dfsg-0ubuntu1.1                      amd64        Web content engine library for Qt - Core
ii  libqt5webenginewidgets5:amd64              5.12.8+dfsg-0ubuntu1.1                      amd64        Web content engine library for Qt - Widget
ii  libqt5webkit5:amd64                        5.212.0~alpha4-1ubuntu2                     amd64        Web content engine library for Qt
ii  libqt5widgets5:amd64                       5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 widgets module
ii  libqt5xml5:amd64                           5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 XML module
ii  qml-module-qt-labs-settings:amd64          5.12.8-0ubuntu1                             amd64        Qt 5 settings QML module
ii  qml-module-qtgraphicaleffects:amd64        5.12.8-0ubuntu1                             amd64        Qt 5 Graphical Effects module
ii  qml-module-qtquick-controls2:amd64         5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 Qt Quick Controls 2 QML module
ii  qml-module-qtquick-layouts:amd64           5.12.8-0ubuntu1                             amd64        Qt 5 Quick Layouts QML module
ii  qml-module-qtquick-templates2:amd64        5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 Qt Quick Templates 2 QML module
ii  qml-module-qtquick-window2:amd64           5.12.8-0ubuntu1                             amd64        Qt 5 window 2 QML module
ii  qml-module-qtquick2:amd64                  5.12.8-0ubuntu1                             amd64        Qt 5 Qt Quick 2 QML module
ii  qt5-gtk-platformtheme:amd64                5.12.8+dfsg-0ubuntu1                        amd64        Qt 5 GTK+ 3 platform theme
ii  qttranslations5-l10n                       5.12.8-0ubuntu1                             all          translations for Qt 5

Seems like Qt 5.12 is installed on your system. The plugin is built and tested with Qt 5.10, because that's what Cura's executable ships with. That Cura build configuration can be found here: https://github.com/Ultimaker/cura-build-environment/blob/master/projects/qt.cmake#L1. Can you try removing Qt 5.12 from your system? Or if you have some coding experience feel free to submit a PR to properly support this version of Qt in the plugin.

I'll have to see about removing 5.12 - I didn't install it manually so it came as a dep with another application, so uninstalling may not be possible if that application is more important than this plugin.
I've never looked at QT code.. so would take me a bit to get up to speed on creating a PR for this.

Checked.. This would require me to remove Nextcloud, which is far more important. So not an option.

Same behavior as @Routhinator.
I have the exact same Cura, Ubuntu and QT versions.
I am not ready to downgrade QT as it was probably upgraded by Ubuntu

This error now also appears in Cura 4.9.0 Beta (which ships with a newer version of Qt). I'll look into this problem myself now that I can reproduce it.

Found several issues that might have contributed to this issue. Please see https://github.com/ChrisTerBeke/ThingiBrowser/pull/66 for code details. I will publish a new version of the plugin in the Marketplace soon. If you want to test before that, you can download/clone the repository and manually install the plugin in Cura (by adding a simlink to the Cura user settings plugin folder, outlined on https://github.com/Ultimaker/Cura/wiki/Cura-Preferences-and-Settings-Locations).


Activator Key

*I have purchased the LiveCharts license but not able to find the Activation Key *
Extra notes
Explain what you expect, feedback, images or anything you consider necessary
I am using

Live-Charts version
*your Live-Charts version here*

.Net Version
*your .net version here*

Windows
*your windows version here*

I am really sorry for this, please to get your activation code you must: login in the site, here is the link lvcharts.net/licensing/manage then access your invoice to get the activator download link.
Once you downloaded the activator, please run it, your key will be shown in your browser, then insert this key in the activator.
The site is about to be updated to explain this better, if you face any issue just let me know I'll help you.

Hello
I am closing this issue since the site was just updated and now it is more friendly to manage your licenses.
Please take a read to https://lvcharts.net/licensing/howto you should receive a mail soon notifying that managing licensing is easier now and has a lot of new features.
Let me know if you face any other issue. btw I am aware of the second issue you are facing with the activator as I'll let you know once it is fixed.


KAFKA-8034: Use automatic RPC generation in DeleteTopics

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

retest this please

@omkreddy @cmccabe If you have some time, can you take a look? Thanks

Thanks, @mimaison!  Looks good overall.  I left one correction

LGTM.  Thanks, @mimaison


Entity Collection Visualizer optimization

We have been running a change to the EntityCollection logic and would like to see if the community wants it in core Cesium.
This code creates a cache of visualizers and detects primitive types in each entity in a collection.  If a new primitive type is detected, the visualizer associated with it is added to the list of visualizers used by the parent EntityCollection.
This keeps unused visualizers from being looped through each tick, and depending on the scene can greatly improve the framerate, especially in high entity count collections.
Changes can be seen here.

@TJKoury Thanks for the interest! It looks like the link in your comment is broken (or maybe the repo is private). We'd be happy to take a look when it's fixed 🙂

Sorry about that, the files were referenced in this pull

Thanks @TJKoury!
@mramato - what do you think of the proposed changes? At a glance they make sense to me but I'm not sure the best way to go add something like that to EntityCollection.


Any chance of adding a BundleCommand stub?

It would be nice to remove this from the vim-update-bundles README.
https://github.com/bronson/vim-update-bundles/commit/b236d7f5755bbc737f70143a7e91fcc5c15dc575#L1R164
Think Vundle will support BundleCommand one day?  If not, maybe I should rethink using it in vim-update-bundles.

Oh, I hoped it'd be a pull request! ;)
So you're saying stub would be enough for ?
That's doable even today.
In the long term though, :BundleCommand belongs to a plugin itself as part of installation process, I believe.

OK, that sounds like more fun than working on my stuff right now.  Let's see if I can remember enough viml to make it work...
Long term I agree.  But that will require setting up some sort of protocol for plugin developers to follow (would probably be related to plugins specifying their own dependencies too).  Short term, having it in .vimrc is better than nothing!


Deploy cpa-k8s+ TESK on 2018-IS Nodes

[x] ELIXIR-DE
[ ] ELIXIR-CH
[x] ELIXIR-IT

Will follow this up with the ELIXIR nodes


If the Chart Data is empty and no limits are provided to axis, it should not throw an exception but it should default to a value.

if no max/min is provided in both axis and if there is no data, I believe it should default to min = 0, max = 1.
In my application I am displaying live RSSI data of BLE devices. When no BLE device is detected horizontal axis (time) is irrelevant. My chart computes X axis values from the x field of FlSpot x values.
Describe the bug
When LineChartData is empty and maxX is null it throws the following exception:
══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following LateError was thrown building RSSIChart(dirty, dependencies:
[_InheritedProviderScope<PlotDataManager?>], state: _RSSIChartState#77d4d):
LateInitializationError: Field 'mostRightSpot' has not been initialized.

The relevant error-causing widget was:
  RSSIChart
  RSSIChart:file:///C:/Users/kutlay.hanli/AndroidStudioProjects/adi_attach/lib/main.dart:52:19

When the exception was thrown, this was the stack:
#0      LineChartBarData.mostRightSpot (package:fl_chart/src/chart/line_chart/line_chart_data.dart)
#1      LineChartHelper.calculateMaxAxisValues (package:fl_chart/src/chart/line_chart/line_chart_helper.dart:49:19)
#2      new LineChartData (package:fl_chart/src/chart/line_chart/line_chart_data.dart:93:31)

To Reproduce
Scaffold(
  body: SafeArea(
    child: LineChart(
      LineChartData(
        lineBarsData: null,
        maxY: -30,
        minY: -150,
      ),
    ),
  ),
);

Versions
Flutter 3.0.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f1875d570e (8 weeks ago) • 2022-07-13 11:24:16 -0700
Engine • revision e85ea0e79c
Tools • Dart 2.17.6 • DevTools 2.12.2

fl_chart: ^0.55.1

https://github.com/imaNNeoFighT/fl_chart/pull/1142

I couldn't reproduce it. There's no exception, and below is the result of your code in my machine (latest fl_chart version, 0.55.1):

Please give me a valid reproducible code (a main.dart file). Or a video shot of what you're facing.

Hi,
To reproduce: https://github.com/imaNNeoFighT/fl_chart/pull/1142#issue-1366216416
Fixed the issue in this PR https://github.com/imaNNeoFighT/fl_chart/pull/1142/commits/36701547c8d86e3172e6c8c66912548f3556b68b
It is awaiting approval to merge.

I followed the contributing steps and it still failed. Can you help me understand why?

@imaNNeoFighT can you guide me?

Hi everyone!
The code checks max position X and Y coordinates by spot elements.
If your spot list is empty or null, use [FlSpot.zero] for the spot list by default.
It helped me.
Don't use [FlSpot.nullSpot]


STOP WORKING! UNABLE TO DEFINE ANY WORD SINCE RECENT UPDATE: JAN 10, 2022.

I truly enjoyed using dictionary plus and I was having a great experience until January 10, 2022 update. The adds-on took long to search for a definition when double-clicked on a word, in which after did not find any definition. This occurred with every word I double-clicked, from the simplest words such as tube, pregnancy, and normal etc. I was enjoying the adds-on very much, as a result, I had to make a account with Github just so I can be able to report this issue, in order for it to be resolved

Hi, I appreciate your effort to report this issue. Thank you.
For future, I'll setup an easier way to send feedback and report bugs.
Please answer the following question:

Your Firefox version
Your Country
Your browser's main language
Can you open https://www.google.com or it blocked in your country or by your internet provider?

Ok, please do make a easier way to communicate.

Firefox version is 95.0,2 (64-bit)
Jamaica
English
Yes I can open the link above.

Hi, I did some tests using Firefox 95.0.2 (and also the newest 96.0), but everything is working fine for me.
I've no idea how it's not working for you.
Anyway, I'll soon release a new version which will give me error reports so I can know exactly what went wrong.
Thank you.

@Luckybritbrit15 I've just released a new version (5.3). It will now display a detailed error message when something goes wrong.
Please update the extension. And if there's still an error, please paste the error message here.
Thank you.

Ok, Thanks much. I will go ahead and update it, as well as  Firefox. I
really appreciate the assistance. I was seeing a improvement recently where
I am about to define few words. It appears it is slowly working back for
me, I hope the update will resolve the issue. Thanks again for your help
and immediate response 👍.
On Wed, Jan 12, 2022, 2:56 PM Bharat Chauhan @.***>
wrote:

@Luckybritbrit15 https://github.com/Luckybritbrit15 I've just released
a new version (5.3). It will now display a detailed error message when
something goes wrong.
Please update the extension. And if there's still an error, please paste
the error message here.
Thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/bhch/dictionary-plus/issues/4#issuecomment-1011400544,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXHZO73DXQEM5SQTQPA5BFLUVXMIDANCNFSM5LVFLLXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

It's really strange that it's not working for you.
I've created a debug mode extension for you.

Download debug mode extension from here: dictionary-plus-debug-mode.zip.
Remove Dictionary Plus add-on from your Firefox.
Then install the package you downloaded above. Follow instructions on this page: https://extensionworkshop.com/documentation/develop/temporary-installation-in-firefox/
Then open a new page and try to double-click on some words.
Copy the error message and paste it here.

)]}'
1b;["2j7jYZ3QCcTCytMP87GfgAo"]3;[1]2;[]

On Sat, Jan 15, 2022 at 8:22 AM Bharat Chauhan @.***>
wrote:

It's really strange that it's not working for you.
I've created a debug mode extension for you.

Download debug mode extension from here:
dictionary-plus-debug-mode.zip
https://github.com/bhch/dictionary-plus/files/7874364/dictionary-plus-debug-mode.zip
.
Remove Dictionary Plus add-on from your Firefox.
Then install the package you downloaded above. Follow instructions
on this page:
https://extensionworkshop.com/documentation/develop/temporary-installation-in-firefox/
Then open a new page and try to double-click on some words.
Copy the error message and paste it here.

—
Reply to this email directly, view it on GitHub
https://github.com/bhch/dictionary-plus/issues/4#issuecomment-1013681627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXHZO734UBNJ55MVQVXQTB3UWFYJLANCNFSM5LVFLLXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

)]}'
1b;["JD_jYcexAr2lytMPwteduA8"]3;[1]2;[]

On Sat, Jan 15, 2022 at 8:22 AM Bharat Chauhan @.***>
wrote:

It's really strange that it's not working for you.
I've created a debug mode extension for you.

Download debug mode extension from here:
dictionary-plus-debug-mode.zip
https://github.com/bhch/dictionary-plus/files/7874364/dictionary-plus-debug-mode.zip
.
Remove Dictionary Plus add-on from your Firefox.
Then install the package you downloaded above. Follow instructions
on this page:
https://extensionworkshop.com/documentation/develop/temporary-installation-in-firefox/
Then open a new page and try to double-click on some words.
Copy the error message and paste it here.

—
Reply to this email directly, view it on GitHub
https://github.com/bhch/dictionary-plus/issues/4#issuecomment-1013681627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXHZO734UBNJ55MVQVXQTB3UWFYJLANCNFSM5LVFLLXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Error Messages:

Defining welcome:

)]}'
1b;["aUDjYfvHM6OkytMP9t-NsAc"]3;[1]2;[]

Defining Nurses:

)]}'
1b;["nUDjYc6YLJC1ytMP-IyI8AI"]3;[1]2;[]

Defining Education:

)]}'
1b;["vEDjYcnUAoHDytMP-b2UoA4"]3;[1]2;[]

Defining school

)]}'
1b;["0UDjYYCoNLvAytMPy-GmuAo"]3;[1]2;[]

These are some of the error messages received when attempted to define the
following words above them.
On Sat, Jan 15, 2022 at 8:22 AM Bharat Chauhan @.***>
wrote:

It's really strange that it's not working for you.
I've created a debug mode extension for you.

Download debug mode extension from here:
dictionary-plus-debug-mode.zip
https://github.com/bhch/dictionary-plus/files/7874364/dictionary-plus-debug-mode.zip
.
Remove Dictionary Plus add-on from your Firefox.
Then install the package you downloaded above. Follow instructions
on this page:
https://extensionworkshop.com/documentation/develop/temporary-installation-in-firefox/
Then open a new page and try to double-click on some words.
Copy the error message and paste it here.

—
Reply to this email directly, view it on GitHub
https://github.com/bhch/dictionary-plus/issues/4#issuecomment-1013681627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXHZO734UBNJ55MVQVXQTB3UWFYJLANCNFSM5LVFLLXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Are you using a VPN? Or maybe you are using an American internet service provider?

Hi, I've just released a new version - 5.4. Hopefully it will resolve your issue. Please install and see if it works.

i don't have an American IP but the update fixed the issue for me as well 🎉

That's great!
Thank you for reporting this issue and for your patience through this.

Thank you, Hun😃
It is working now🤗. I appreciated this alot😇.
You're Welcome🙌
On Sun, Jan 16, 2022 at 6:28 AM Bharat Chauhan @.***>
wrote:

That's great!
Thank you for reporting this issue and for your patience through this.
—
Reply to this email directly, view it on GitHub
https://github.com/bhch/dictionary-plus/issues/4#issuecomment-1013858302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXHZO74DS35NWLWHMS53QBLUWKTXBANCNFSM5LVFLLXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


[YUNIKORN-1059] Add Chinese translation for get started documents

Add Chinese translation for get started documents. This PR contains two contents:

Add core_features.md and get_started.md. Because  the "quick start" chapter in home page is linked to 0.12.1, so 0.12.1 is also added. After the commit comparison, these two files in 0.12.1 is no different from the master. At the same time, several hyperlinks that depend on folders (links to the original file) are added to avoid compile error.
Fix a problem that some links in home page redirect to en.

hi @yuchaoran2011 can you be the main reviewer for this PR? I'll do some cross-check as well. Thanks

@yuchaoran2011
Hi~ For the reason of leaving blank spaces in some english words, I found a problem when translating other articles:
If a phrase is XX YY ZZ,  it may be better translated into 中文 XXX YY ZZ 中文 than 中文XXX YY ZZ中文 in sensory sense. Therefore, when I encounter english words or phrases that no need to be translated, I will add a space between Chinese and English words.
But after your suggestion, I now think it may be better not to add spaces if it is a word. But if it is a phrase, it may be better to add spaces.


Stop tracking .DS_Store files

@tpmcgowan I managed to commit about the same time you approved so it dismissed it 🤦


Error: Cannot find symbol

I am getting the following error while making the debug application
Description
C:\Users\rohit\OneDrive\Desktop\rn-main\android\app\build\generated\rncli\src\main\java\com\facebook\react\PackageList.java:29: error: cannot find symbol
import com.oblador.vectoricons.VectorIconsPackage;
^
symbol:   class VectorIconsPackage
location: package com.oblador.vectoricons
C:\Users\rohit\OneDrive\Desktop\rn-main\android\app\build\generated\rncli\src\main\java\com\facebook\react\PackageList.java:82: error: cannot find symbol
new VectorIconsPackage()
^
symbol:   class VectorIconsPackage
location: class PackageList
2 errors
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.
Environment
OS: Windows 10
Target Platform: Android
Vector Icons Version: 9.2.0

Same issue here but on MacOS Monterey.
Specifically getting this error when attempting to build a signed android app bundle for release. Debug variants work just fine.

Same issue here but on MacOS Monterey. Specifically getting this error when attempting to build a signed android app bundle for release. Debug variants work just fine.

Update: Was able to fix this issue by completely deleting the repo off my PC and recloning it.


Option to disable the tab's index

Not sure if this is possible at this moment. I'm trying to disable the tab's index so that only the name is displayed.
I tried the following approach:
local options = {
	-- index_format = "%d: ",
	index_format = "",
}
require("buftabline").setup(options)

but this didn't work. If this is not possible to do now, then it would be a nice feature to have.

Right, the implementation at the moment doesn't allow for fully disabling the index, but it shouldn't be hard to support.
Not sure if you saw #11, but I've added your suggestions to the to-do list. If you have any more suggestions, let me know – I should have time to sit down and work on this in a couple of weeks.

Thanks Jose. I did see #11 and that's why I suggested a few more potential improvements. Thanks for the plugin.

Closed by #16.


Data of training curves in appendix R and U

Hi @danijar, can you provide the data of training curves of Atari100k/200M (appendix R and U)?

Hi, I've added all training curves to the scores directory of the repository!


Creating an edge from source to target?

Hi there,
I'm relatively new to Sigma.js and I'm trying to be learn how to create single edges that will connect from one node to another.
Adding more detail, say we have two nodes.  I want to designate one as the source, and another as the target node.
How might one try to do this without the neighbors method?
Thank you!
Thank you!

Hello @SmokedEel. To add such an edge, you just need to know the id of both your source and your target and add the edge to the graph:
s.graph.addEdge({
  id: 'arbitraryId',
  source: sourceNodeId,
  target: targetNodeId
});

Perfect! Just one more question, if I wanted to make it so that I can choose which two specific nodes to create an edge between through mouse click and selection, is there a designated sigma function for this?

You can bind event and then retrieve node's data to build your edges:
s.bind('clickNode', function(e) {
  console.log('The clicked node:', e.data.node);
});

Found a way for it to work using the way you mentioned.
Made it so that a click would store data for the source node, and another click on another node would store data for the target node.
Then I used the s.graph.addEdge function to finish it.
Thanks!

Hi, how can edge targeting an other Edge ? it should be possible or not?
Thanks


Parsing error: Unterminated string constant

This triggers a Parsing error: Unterminated string constant
{#           read: "{% url 'api:activity-roles' activity.id %}",#}

Good catch! I didn't anticipate tags inside comments :-) Let me explore.

Please use version 0.5.0


Explore visualization options for inter-columnar relations and knowledge base browsing

Start at http://d3.org/ .
Maybe create a small demo, focus also on the possibility of partially loaded model.

See the e-mails. Additional info will be provided solely upon a personal request.


[PF-283] Initial work on bio.terra.common.iam package.

Janitor, TDR, and WSM have similar UserRequestFactory and UserRequest implementations.
This PR creates a new common iam package, with these classes being the lowest hanging fruit to generalize.
@wchamber raised some concerns around this breaking on-disk format.  The concern was originally driven by the change of Optional<String> to String in API's (which was removed due to adding no value after implementing a builder).  However, the behavior of Jackson with Optional<String> was manually confirmed to produce the same output as with a String, as long as we use the Jdk8Module with our ObjectMapper, which we do.
However, in my manual inspection to discover this, I realized that there may be a different issue that will break on-disk compatibility due to use of enableDefaultTyping, which adds the fully qualified class name to the serialized class:
["bio.terra.common.iam.AuthenticatedUserRequest",{"email":"test@example.com","reqId":"78f84562-c442-49be-951a-a0a56230c35f","subjectId":"Subject","token":"0123.456-789AbCd"}]
It seems like this will lead to a breakage when deserializing for systems with existing on-disk data that serialize as their local impl (i.e. bio.terra.workspace.service.iamAuthenticatedUserRequest) and switch to the common impl.  Thus the downstream PR's to consume this change will have upgrade considerations.
This might present a good opportunity to:

Codify which fields should truly be optional here.
Consider if we need the reqId UUID, as it doesn't seem to be consumed outside of tests.
Consider if there's an opportunity to improve backward compatibility when serializing this class, as this required quite a bit of human intervention via manual inspection, and I'm still not 100% confident of the blast radius.

@wchamber I think I've addressed the outstanding concerns.  If you can give the most recent commit (not the fixup commit) a once over, I will merge this if no show-stoppers.


WebSocket connection to 'wss://domain:6001/app/...?protocol=7&client=js&version=7.0.3&flash=false' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

Hi there, I've been searching for hours through the other threads pertaining to this particular problem - like for other people, it occurs only as an issue on the production server, works fine locally. I'd like to write out the things I've tried and give you some details on the environment as it may be something that I'm missing:
Error
app.js:69927 WebSocket connection to 'wss://domain:6001/app/...?protocol=7&client=js&version=7.0.3&flash=false' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
Server:
Amazon AWS EC2 instance
RHEL 8, using SELinux.
Webserver:
Apache (httpd)
I've opened port 6001 in both the AWS EC2 Security group and in firewall-cmd and iptables.
I'm fairly confident this is a network issue, doing $ nc -v devgiirp.co.uk 6001 gives me:
domain [ip-address] 6001: Connection refused but I simply don't know what else I should check.
Does the port need to be open for both inwards and outward traffic?
I'll dump my config here.
bootstrap.js
window.Echo = new Echo({
    broadcaster: 'pusher',
    key: process.env.MIX_PUSHER_APP_KEY,
    cluster: process.env.MIX_PUSHER_APP_CLUSTER,
    forceTLS : true,
    wsHost: window.location.hostname,
    wsPort: process.env.MIX_WEBSOCKETS_PORT,
    wssPort: process.env.MIX_WEBSOCKETS_PORT,
    disableStats : true,
    enabledTransports: ['ws', 'wss']
});

config/websockets.php
<?php

use BeyondCode\LaravelWebSockets\Dashboard\Http\Middleware\Authorize;

return [
    'dashboard' => [
        'port' => env('LARAVEL_WEBSOCKETS_PORT', 6001),
    ],
    'apps' => [
        [
            'id' => env('PUSHER_APP_ID'),
            'name' => env('APP_NAME'),
            'key' => env('PUSHER_APP_KEY'),
            'secret' => env('PUSHER_APP_SECRET'),
            'path' => env('PUSHER_APP_PATH'),
            'capacity' => null,
            'enable_client_messages' => false,
            'enable_statistics' => false,
        ],
    ],

    'app_provider' => BeyondCode\LaravelWebSockets\Apps\ConfigAppProvider::class,

    'allowed_origins' => [
        //
    ],

    'max_request_size_in_kb' => 250,

    'path' => 'laravel-websockets',

    'middleware' => [
        'web',
        Authorize::class,
    ],

    'statistics' => [

        'model' => \BeyondCode\LaravelWebSockets\Statistics\Models\WebSocketsStatisticsEntry::class,

        'logger' => BeyondCode\LaravelWebSockets\Statistics\Logger\HttpStatisticsLogger::class,

        'interval_in_seconds' => 60,

        'delete_statistics_older_than_days' => 60,

        'perform_dns_lookup' => false,
    ],

    'ssl' => [

        'local_cert' => env('LARAVEL_WEBSOCKETS_SSL_LOCAL_CERT', null),

        'local_pk' => env('LARAVEL_WEBSOCKETS_SSL_LOCAL_PK', null),

        'passphrase' => env('LARAVEL_WEBSOCKETS_SSL_PASSPHRASE', null),

        'verify_peer' => false,
    ],

    'channel_manager' => \BeyondCode\LaravelWebSockets\WebSockets\Channels\ChannelManagers\ArrayChannelManager::class,
];

My SSL keys are sitting in /public and are referenced using the environment variables.
config/broadcasting.php
<?php

return [

    'default' => env('BROADCAST_DRIVER', 'null'),

    'connections' => [

        'pusher' => [
            'driver' => 'pusher',
            'key' => env('PUSHER_APP_KEY'),
            'secret' => env('PUSHER_APP_SECRET'),
            'app_id' => env('PUSHER_APP_ID'),
            'options' => [
                'cluster' => env('PUSHER_APP_CLUSTER'),
                'useTLS' => true,
                'encrypted' => true,
                'host' => '<IP_ADDRESS>',
                'port' => env('WEBSOCKETS_PORT'),
                'scheme' => 'https',
                'curl_options' => [
                    CURLOPT_SSL_VERIFYHOST => 0,
                    CURLOPT_SSL_VERIFYPEER => 0,
                ]
            ],
        ],

        'redis' => [
            'driver' => 'redis',
            'connection' => 'default',
        ],

        'log' => [
            'driver' => 'log',
        ],

        'null' => [
            'driver' => 'null',
        ],

    ],

];

Many thanks for taking a look - if there's anything else you may need to know then feel free to ask, I've tried hundreds of configuration changes, messed around endlessly with the server, I'm quite at a loss, honestly.
UPDATE
I started using the outward facing physical public server IP address in the bootstrap.js file, and now the port is open but I'm getting a new error:
ERR_CERT_AUTHORITY_INVALID
The ball is rolling it seems and I'll look at some other issues to see if others have solved this.
UPDATE
Using the public facing IP address of the server seems like a bad idea, reverse proxy with subdomain for websockets seems sensible perhaps?

for wss connections my settings works;
config/broadcasting.php
    'pusher' => [
        'driver' => 'pusher',
        'key' => env('PUSHER_APP_KEY'),
        'secret' => env('PUSHER_APP_SECRET'),
        'app_id' => env('PUSHER_APP_ID'),
        'options' => [
            'cluster' => env('PUSHER_APP_CLUSTER'),
            'host' => 'domain.com',
            'port' => (int)env('LARAVEL_WEBSOCKETS_PORT',6001),
	'scheme' => 'https',
            'encrypted' => true
        ],
    ],


YNAB Upgraded to Ember 1.13

Hey! We just upgraded Ember to 1.13 and noticed some errors in our logs related to the import-notifications:
TypeError: Cannot read property 'get' of undefined
1
File "chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/res/features/import-notification/import-notification.js" line 7 col 60 in HTMLDivElement.<anonymous>
2
File "../ynab_shared_library/node_modules/jquery/dist/jquery.min.js" line 2 col 2871 in Function.each
!function(a,b){"object"==typeof module&&"object"==typeof module.exports?module.exports=a.document...
3
File "../ynab_shared_library/node_modules/jquery/dist/jquery.min.js" line 2 col 838 in ae.each
!function(a,b){"object"==typeof module&&"object"==typeof module.exports?module.exports=a.document...
4
File "chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/res/features/import-notification/import-notification.js" line 6 col 31 in ynabToolKit.importNotification

I believe it's because Ember.View.views is no longer a valid way to access a view, so this line fails.
I can help look into some fixes but wanted to give you a heads up.

Ultimately a future proof solution like this would be good: https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/182#issuecomment-181981146 but I'm looking into some hot fix recommendations now.

Something like this might work as a hot fix (but it is still using private APIs so it is subject to break on updates):
var id = $(row).attr('id')
var view = Ember.View.create().get('_viewRegistry')[id];
if (view) {
  var account = view.get('data');
}

Although for that specific feature, getting the accounts from the shared library directly might be more future proof (but that API is considered private as well, so is also subject to change):
ynab.YNABSharedLib.getBudgetViewModel_SidebarViewModel().then(function (viewModel) {
  var onBudgetAccounts = viewModel.get('onBudgetAccounts');
  onBudgetAccounts.forEach(function (account) {
     var transactions = ynab.utilities.TransactionImportUtilities.getImportTransactionsForAccount(account);
  });
})

Appreciate the comments! We'll have to look at fixing this.

I've noticed that Toolkit for YNAB on Chrome doesn't function at all with this change.

@CobraA1 - It depends on the features you have enabled, but yes, without a fix in place there is the potential for the Toolkit to not work at all. We're working on it.

I"m sure this has been reported, but since the upgrade to YNAB, I'm asked to refresh my browser after doing any transaction.

I've had to disable the extension in order to continue to work in YNAB without having to refresh after every transaction.

@amswitzer are you able to pull down the branch I just made to see if it resolved your issue?

Sorry - I have no idea how to do that. Can you guide me through it?

@amswitzer - You're just a regular YNAB forum user, not a Toolkit developer, right? Just double checking.
@joshmadewell - We probably should test this internally first, just so we don't need to worry about having non-technical users try to figure out accessing Github, building the plugin, etc.

@joshmadewell - I'll look into testing this later today.

You're just a regular YNAB forum user, not a Toolkit developer, right? Just double checking.

@falkencreative: Yup. I was just trying to be a good user by reporting the bug and when I clicked on the "Report a Bug" option in the extension, it took me here.

@joshmadewell It worked for me, but I didn't do any extensive testing.

@amswitzer You did great :D
Unfortunately, I just switched to nYNAB and I'm not a user of the import feature so I can't actually test that.
@falkencreative I definitely think this needs to go through some thorough testing but I have most feature enabled in YNAB Toolkit and I went from having about 2-3 working to all of the ones enabled working so it definitely passed the eye test ;)

@joshmadewell I had the same problem as @amswitzer, and it wasn't just on import. Any change on an account screen that required a save (import, accept, edit) would give me that refresh warning.
I pulled down and built the latest from main before I realized you meant you'd forked and fixed stuff, but oddly enough whatever's already out there for 0.4.6 seems to have fixed the problem. I even switched back to 0.4.5 to make sure, and was able to reproduce there.

Just to be clear, I experienced this issue with an transaction and not just
importing.
On Thu, Jun 23, 2016, 11:28 PM r-squared<EMAIL_ADDRESS>wrote:

@joshmadewell https://github.com/joshmadewell I had the same problem as
@amswitzer https://github.com/amswitzer, and it wasn't just on import.
Any change on an account screen that required a save (import, accept, edit)
would give me that refresh warning.
I pulled down and built the latest from main before I realized you meant
you'd forked and fixed stuff, but oddly enough whatever's already out there
for 0.4.6 seems to have fixed the problem. I even switched back to 0.4.5 to
make sure, and was able to reproduce there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/349#issuecomment-228250027,
or mute the thread
https://github.com/notifications/unsubscribe/ATLkt4EV9x1yGa2ZpmQcSexeZBguAnhrks5qO07EgaJpZM4I8Ja9
.

@r-squared I was working of master so maybe that's why I'm not seeing the issue, could you provide me steps to reproduce? I tried changing transaction amounts, clearing/unclearing, reconciling the account and I can't seem to reproduce the problem. :(

@joshmadewell, all of those will reproduce the issue for me, but only with the version on the Chrome Web Store. I just pulled down and built 0.4.5 and I can't reproduce there. I'm not sure what the difference would be, other than I have a slightly older version of node.

Well that's inconvenient :(
We might need some Toolkit members to look into that since I'm not able to deploy an actual update. I'll try pulling the version from the Chrome Store and see if the error is related to the fix that I made...

As far as I know @blargity is the only one who can publish a new build of the extension. He's been quite busy with some personal issues but hopefully he'll see this Issue and take care of it.

Note to self, don't try testing just before bed... Going back and being a little more methodical with trying settings, I found I can reproduce in both locally built copies (0.4.5 and latest master) just by turning on the Show Import Notifications in Sidebar setting.
And now that that's out of the way, I can also confirm that @joshmadewell's hotfix-accessingEmberViews branch does indeed fix the problem. :)

I've spent a little time with the hotfix, and as far as I can tell, it fixes at least the biggest issues (the main one I'm worried about is the popup "please refresh your browser" message). Nearly everything seems to be working for me, and I'm not getting any error popups. I did notice an issue with the coloring of reconciled transaction rows, but I think that likely is separate from this specific hotfix, and isn't as big of a deal.
@blargity I know you're busy, but is there any way you can integrate @joshmadewell's fix ASAP, and push out a new version? This looks bad -- both for for YNAB (since they are dealing with people actually complaining about Toolkit related issues), and for the Toolkit. My hope is that if we push out a fix quickly, we won't lose the trust of too many users due to issues. Thanks!

Sorry for the silence everyone, I plan to cut a release tomorrow! Thank you for the hard work on this!

@blargity - Thanks for the follow up -- glad to hear it.

Release 0.4.6 is now out. It looks to me like it fixes this issue, but let me know if I'm wrong. 👍

Alrighty, after a few confirmations that the crashes at least are fixed with the hotfix I'm going to go ahead and close this issue so we can track other issues individually. Thank you again @shama for your help!


Add simple Catboost model

Adds a trivial use of the Catboost model to predict the rs_classification label (from efo_otar_slim_v3.43.0_rs_classification.tsv).
Note: The code isn't intended to be especially useful as of now. Rather, it is meant to serve as a first baseline & anchor for future feature and model developments.

Example of run:
Learning rate set to 0.091517
0:      learn: 1.2655947        total: 74.3ms   remaining: 1m 14s
100:    learn: 0.4192182        total: 1.04s    remaining: 9.3s
200:    learn: 0.3914375        total: 2.02s    remaining: 8.03s
300:    learn: 0.3724496        total: 3s       remaining: 6.98s
400:    learn: 0.3568311        total: 4.1s     remaining: 6.13s
500:    learn: 0.3437438        total: 5.1s     remaining: 5.08s
600:    learn: 0.3304904        total: 6.09s    remaining: 4.04s
700:    learn: 0.3194607        total: 7.26s    remaining: 3.1s
800:    learn: 0.3095234        total: 8.24s    remaining: 2.05s
900:    learn: 0.2992087        total: 9.22s    remaining: 1.01s
999:    learn: 0.2912932        total: 10.2s    remaining: 0us
> Feature importance:
                     Feature Id  Importances
0                        prefix    19.202524
1                       n_roots     8.639185
2                         depth     7.401090
3                   n_ancestors     7.091980
4          intrinsic_ic_sanchez     4.912018
5         xref__orphanet__count     3.976000
6             xref__omim__count     3.860123
7            xref__mondo__count     3.537002
8             xref__doid__count     3.456866
9                  intrinsic_ic     3.426787
10                is_gwas_trait     3.368879
11  intrinsic_ic_sanchez_scaled     3.051188
12            xref__mesh__count     3.047183
13            xref__ncit__count     2.794949
14                    n_parents     2.678225
15                   n_children     2.488526
16           xref__icd10__count     2.159789
17            xref__umls__count     2.104636
18                n_descendants     2.049742
19            xref__gard__count     2.004128
20        xref__snomedct__count     1.991120
21          xref__meddra__count     1.937532
22          intrinsic_ic_scaled     1.443108
23            xref__icd9__count     1.251675
24          xref__omimps__count     1.146293
25                     n_leaves     0.979452

> Classification report:
                    precision    recall  f1-score   support

01-disease-subtype       0.80      0.85      0.82      1123
   02-disease-root       0.72      0.64      0.68       776
   03-disease-area       0.77      0.79      0.78       242
    04-non-disease       0.97      0.99      0.98       918

          accuracy                           0.83      3059
         macro avg       0.82      0.82      0.82      3059
      weighted avg       0.83      0.83      0.83      3059

@dhimmel Updated the PR with the csv and StrEnum changes 🙏


Copy default test container

T/O

Codecov Report

Merging #28 (0704673) into master (07706fc) will increase coverage by 0.29%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
+ Coverage   72.19%   72.49%   +0.29%
==========================================
  Files           4        4
  Lines         651      658       +7
==========================================
+ Hits          470      477       +7
  Misses        106      106
  Partials       75       75


Upload @TudorMagirescu's UnsanitizedFilenameFromContentProvider lint check

As discussed internally, @TudorMagirescu has written a lint check to flag when content provider file names are trusted without proper sanitization. Given that this lint check will be available in the stable version of Android Studio IDE directly in Jan 2025, we are allowing developers to "preview" the lint check here in this IDE-external lint library.
Great job @TudorMagirescu :)

LGTM, thanks!

LGTM, but I have left a comment. Thanks for including UnsafeFilenameDetector in this library!


chore: gh workflows

Next plans: move to Typescript and add eslint+prettier. Agree @ekarak ?

yes, agreed.


read events using Date Ranges

read events using Date Ranges
WHAT DOES THIS PR DO?

[x] From data management microservice, read a Date Range of Events in JSON format

WHAT JIRA STORY/TASK IS RELATED TO THIS PR?
  Otherwise, you will keep on getting the same results and think that the endpoint is not working yet you are getting cached results!
WHICH ENDPOINTS SHOULD BE READY FOR TESTING?:

[x] retrieve device readings

IS THERE ANY JENKINS CONSOLE LINK FOR CODE COVERAGE AND BUILD INFO?
N/A
SCREENSHOTS?

retrieve device readings

Hi @Baalmart , we still need to perform thorough tests. Querying by start and end time has issues.

[ ] Query by start time alone
[ ] Query by end time alone
[ ] Query by both start and end time

For all the above, we need to put into consideration the hours and minutes while testing.

retrieve device readings

Hi @Baalmart , we still need to perform thorough tests. Querying by start and end time has issues.

[ ]  Query by start time alone
[ ]  Query by end time alone
[ ]  Query by both start and end time

For all the above, we need to put into consideration the hours and minutes while testing.

Hi @NoahNsimbe , please provide more details of "the issues" so that I can act accordingly. Use screenshots where need be for me to easily address the issues.
Also, please note that the .env has just been updated so please check it out asap here.

retrieve device readings

Hi @Baalmart , we still need to perform thorough tests. Querying by start and end time has issues.

[ ]   Query by start time alone
[ ]   Query by end time alone
[ ]   Query by both start and end time

For all the above, we need to put into consideration the hours and minutes while testing.

Hi @NoahNsimbe , please provide more details of "the issues" so that I can act accordingly. Use screenshots where need be for me to easily address the issues.
Also, please note that the .env has just been updated so please check it out asap here.

Hi @Baalmart, you just have to make sure querying by date time functions as expected. The last time we checked, it only supported querying by date.  For example. If I specify 2022-01-01T10:00:00Z and 2022-01-01T18:00:00Z as my start date time and end date time resp, the endpoint should return events recorded on 2022-01-01  between 10am and 6pm

Thanks @NoahNsimbe, the env has been updated

Hi @Baalmart, the environment variables in our clusters we updated yesterday. Could there be any more new ones?


Add NVidia Datacenter (V100/A100/H100) GPU assignment to CloudStack guests

ISSUE TYPE

Enhancement Request

COMPONENT NAME
Apache Cloudstack UI, Agent, KVM, API, etc.
CLOUDSTACK VERSION
Apache Cloudstack 4.15.1
CONFIGURATION
Small setup with 1 Zone, 1 Pod, 2 Clusters: One for CPU virtualization purposes and the other for GPU virtualization purposes.
The GPU cluster consists of 2 nodes with 4 Nvidia A100 cards per node.
OS / ENVIRONMENT
Red Hat Enterpise Linux 8.4 with KVM/QEMU/libvirt (Cloudstack Agent) installed on several GPU hosts with several NVidia A100 AI cards and Cloudstack setup and hosts running on RHEL 8.4 as well.
SUMMARY
Currently, support for Nvidia A100 GPU is not available in Cloudstack. Under Service Offerings -> New Service Offering, I can only define the "old" GRID K1 and K2 cards as GPU ressources. GUI and underlying functionality support for A100 and/or V100 cards are missing. Furthermore, no GPU ressources are displayed zone-wide e.g. on the dashboard when adding a host with A100 cards. As far as I know, KVM virtualization with RHEL 8.4 is supported.
STEPS TO REPRODUCE
Adding a host/node with A100 cards to a cluster in Cloudstack. No Zone-wide GPU ressources are displayed on the dashboard as well as no possibilites to define Compute Offerings with A100 capabilities on the Cloudstack GUI.
EXPECTED RESULTS
Add the A100 card as an option in Service Offering > GPU. When chosen, users can define how man vGPUs to pass to the virtual machine. On the dashboard of Cloudstack, the available amount of GPU ressources are displayed.

Very good idea.

The installation of NVIDIA software on the KVM side should be on the Administrator side.
GPU Offering should allow you to define NVIDIA vGPU profile, (this information can be easily retrieved from the appropriate path) e.g .:

nvidia-355 - CUDA - num_heads=4, frl_config=60, framebuffer=1024M, max_resolution=5120x2880, max_instance=32
nvidia-356 - CUDA - num_heads=4, frl_config=60, framebuffer=2048M, max_resolution=7680x4320, max_instance=16
nvidia-357 - CUDA - num_heads=4, frl_config=60, framebuffer=4096M, max_resolution=7680x4320, max_instance=8
nvidia-358 - CUDA - num_heads=4, frl_config=60, framebuffer=8192M, max_resolution=7680x4320, max_instance=4
nvidia-359 - CUDA - num_heads=4, frl_config=60, framebuffer=16384M, max_resolution=7680x4320, max_instance=2
nvidia-360 - CUDA - num_heads=4, frl_config=60, framebuffer=32768M, max_resolution=7680x4320, max_instance=1

The list of generated UUIDs for the vGPU can be passed to the CS or the CS can generate the vGPU
The whole process should allow you to connect a vGPU device as offering (compute type), not as extraconfig.
The dasboard should show the amount of used / max vGPU

The manual vGPU connection process is described here:
https://lab.piszki.pl/cloudstack-kvm-and-running-vm-with-vgpu/
Automation should allow you to use GPU Offering instead of extraconfig, that's enough.

Has this been discussed for priority in a release?  These are common GPU chips and having this implemented directly as a supported service offering would be ideal.

Im sure there are going to be lots of GPU models being released, not only from Nvidia, but AMD as well?
Any plans to support AMD GPUs? Or at least the implementation should be vendor neutral with the option of easily supporting future GPU versions?

@btzq , I am pretty sure it is vendor neutral, just not model neutral yet. sounds like a necessary improvement for the exiting times to come though. (cc @weizhouapache any idea?)

AMD is launching their MI300X end of this month April 2024 , and not going to be a cost effective when compared to Nvidia , and this is going to become viral , we should get a patch created in order to have compatibility with cloud stack offerings

@Dominic46515 @btzq Afaik, the main (and only) reason why many AI developers tend to use Nvidia cards was because of CUDA (and the support by AI frameworks). Is there now enough support for AMD cards?


@graphql-yoga/plugin-response-cache: Support more advanced use cases

Is your feature request related to a problem? Please describe.
I am trying out Yoga as an alternative to Apollo Server 4, and when it comes to response cache plugin the one in Yoga is a more crude version that doesn't have any means to support the following API:

extraCacheKeyData
calculateCacheKey
shouldReadFromCache and shouldWriteToCache

Describe the solution you'd like

extraCacheKeyData(requestContext): any - Ability to give a hook for adding an extra key with value being result of callback, which internally is passed to buildResponseCacheKey({ ...original, extra })
calculateCacheKey(requestContext): string - Ability to alter cache key used for reading and writing to cache, if this is passed use const key = calculateCacheKey ? ${originalKey}:${calculateCacheKey(requestContext)} : originalKey.
shouldReadFromCache abd shouldWriteToCache - Ability to skip response cache altogether, such as based on header (might not need a code change)*

Describe alternatives you've considered

calculateCacheKey might be might be more of a @envelop/response-cache-redis  concern, and as such I might have been able to use buildRedisOperationResultCacheKey, but it is not yielding requestContext. Still we might want to split this feature request to that library instead.
*) I think shouldReadFromCache abd shouldWriteToCache can be combined into simply "skip cache", since we are always using them together and set to the same value. But we might not even need support for these in the plugin itself, as we can just skip adding this plugin altogether instead.

Additional context
N/A

Hi,
I'm sorry we are lacking some documentation on this plugin (it evolved quickly during the last months).
Some of the point's are already possible, or at partially possible at least.

calculateCacheKey(requestContext): string already exists in the Envelop plugin and is named buildResponseCacheKey. But it is a bit limited in the Yoga version where it doesn't give you access to the context or the request. It should be easy to add it :-)
extraCacheKeyData(requestContext): any I'm not sure to see the uses cases of this. How is it different than using calculateCacheKey ?
shouldReadFromCache and shouldWriteToCache are replaced by 2 options :

enabled(request: Request): boolean which allow to entirely skip the cache (reading and righting) based on request
shouldCacheResult(cacheKey: string, result: ExecutionResult): boolean which allow to skip cache (reading and writing) based on the query's result. The default implementation for example skips results if it contains any error.

So to sum things up, i think we have 2 actions that are needed from our parts here:

[ ] Update (Response Cache documentation)[https://the-guild.dev/graphql/yoga-server/docs/features/response-caching]

[ ] List and explain every options
[ ] Add guides and examples for common use cases (like the ones from the (Envelop documentation)[https://the-guild.dev/graphql/envelop/plugins/use-response-cache]

[ ] Give access to the request in the buildResponseCacheKey option.

Agreed, extraCacheKeyData and calculateCacheKey can both be implemented using buildResponseCacheKey.
And using the 2.2.0-rc I can see that having access to request is good enough!
Do you know if there is any good util method to extract operationName from a request: Request? We usually filter out __ApolloGetServiceDefinition__ and IntrospectionQuery by default.


add roles for certain reputation levels

The server_id stuff is not neccesary since self.guild exists in ever extension.
The DB class is also not supposed to do logic, so I'm not really in favor of the callback thing, makes it overly complicated imo.
If you move the check to add_thank or so, everything else seems alright @ichbineinNerd


[Research] Celestial navigation: Location without GPS

Some details can be found here on using a sextant: https://github.com/kylecorry31/Trail-Sense/issues/319
If you can identify several stars, and know their altitude and azimuth, as well as UTC time, it may be possible to calculate location without GPS.
I have no idea if this will work, but what if a photo of the night sky was used along with sensor data on the phone to determine orientation. Then compared to the star positions using #1809, maybe location can be determined? Maybe a similar thing can be done with the sun/moon's position (and it's easier to take a photo of the sun/moon).
As mentioned, I have no idea if this will work or if it will even be practical  - I just thought of it and wanted to document it in case I ever felt like attempting more research and building this in TS.
Not a high priority, and more of a thing to look into for fun - since if you can clearly see the night sky, you will almost certainly have GPS available. This could be used on devices with GPS disabled/unavailable though.
It may be possible to use this to calibrate the compass if determining location isn't the goal - known location, known azimuth of the celestial object will allow you to get a compass calibration.

[x] Extract stars from image
[x] Calculate altitude of stars in the image
[x] Determine which stars are in the image (plate solving)
[x] Determine location using the stars
[ ] Show the stars on an image and let the user confirm that is correct

Plate solving involves the following steps:

Construct observed star quads (normalized distances to each nearby star, not just nearby, several permutations needed)
Construct reference star quads (not just nearby, several permutations needed) - may need to convert these into a standard format
Find the best match for each star using the star quads

https://olegignat.com/how-plate-solving-works/
https://www.hnsky.org/astap_astrometric_solving.htm

Another option if plate solving ends up being infeasible or takes longer than expected to complete could be:

Have user select approximate location on a map (default to last known location / timezone derived location)
Have the user locate a major constellation that should be visible to them
Ask the user to adjust the elevation on the AR tool using a slider until the constellation lines up

But plate solving is definitely the preferred approach

Might also want to look into correcting the error in inclination using multiple star readings, similar to GPS time synchronization

Initial testing results:

When run with perfect data (with perfect biases in azimuth/altitude readings), accuracy is under 2 meters
Real world testing however is only within 50 km, which is not practical. I think this is a combination of shaky hands, imperfect star detection, imperfect pixel to world coordinate math (it only does linear inverse projection), and unaccounted for variables (temperature - though the bias term should pick this up). More experimentation needed. If the plate solving technique works, that has the potential to remove a lot of human error (could ask the user stabalize their phone with a tripod or placing it on the ground).

This was fun to learn about and implement, but unfortunately I couldn't get good accuracy out of a smartphone on this. The errors in sensors, camera readings, and algorithms add up to be too much. And it would see very infrequent use (this was always more of a fun research ticket).
https://github.com/kylecorry31/Trail-Sense/blob/a5e5ee327069dc74c1913427c3e50cb2c44d6cc7/app/src/main/java/com/kylecorry/trail_sense/tools/celestial_navigation/ui/CelestialNavigationFragment.kt


webpack_require(...).map is not a function

Basic info:

Node.js version: v12.14.0
jsdom version: 16.6.0
webpack version: 4.44.2

Minimal reproduction case
https://github.com/yinguangyao/jsdom-webpack
npm i
npm run build
node dist/main.js

problem performance
The error message is as follows:
internals.rules = __webpack_require__(344).map(function (rule) {

TypeError: __webpack_require__(...).map is not a function

The problem looks to be with psl here.

from npm install
Could not resolve dependency:
npm ERR! peer webpack@">=5" from<EMAIL_ADDRESS>npm ERR! node_modules/node-polyfill-webpack-plugin
npm ERR<EMAIL_ADDRESS>from the root project


:geoip2 (maxminddb) private method `data' called for #Geocoder::Result::Geoip2:0x007ff9128eaf18

I was using :telize and :freegeoip but seeing timeouts, so I decided to try :geoip2.
Here's the config:
# database download: http://dev.maxmind.com/geoip/geoip2/geolite2/
ip_lookup: :geoip2,
geoip2: { file: File.expand_path('../../db/geocoder/GeoLite2-City.mmdb', File.dirname(__FILE__)) }

Here's the code that doesn't work for :geoip2 only:
if @@use_geocoder && request.location.present?
      data = request.location.data
      address.country = data['country_code']
      address.state = data['region_code']
      address.postal_code = data['postal_code']

Error is private method data' called for #Geocoder::Result::Geoip2:0x007ff9128eaf18.  [This code](https://github.com/alexreisner/geocoder/blob/master/lib/geocoder/results/geoip2.rb#L59) appears to make data` private, whereas it is an accessor in base.rb.
Any reason why data should be private in this result?

I'm switching to accessors, I see where results differ.


Join DecksListener with CardsListener

This need to be done because Cards loaded from CardsListener cannot be flexibly get along with Decks loaded from DecksListener.

Fixed by c2ff2d6bca806dc76f61bdbb6053766f3f3d9ca7


Restriction on null space exploration

Hi!
I found that fetch_pick_and_place env was realized with mocap which is implemented through the built-in inverse kinematics algorithm.
From the training results of fetch_pick_and_place, the 7-DOF fetch arm did not oscillate significantly by exploring in the null space. As far as I know,  null space exploration could be affected by the initial configuration of the manipulator. fetch_pick_and_place env is initialized with a high-manipulability configuration and there is no significant oscillation during the entire task.
I'm curious if it's possible to control the end-effector via mocap in a way that simultaneously restricts the redundant arm to reduce the exploration of the null space.
Thanks in advance!

You can put springs in the joints? If you want something more elaborate you'd have to implement that seperately.

Take a look at this model see what you can learn from it. BTW, it's not clear to me why you need a mocap body.

Look at the model above. No mocap body required.

That should have any effect.
Define "crash": Falls down of the physics diverges?
Are you using implicitfast integrator?
Do you joints and actuators have damping?

Look at the translation default class. Your gain is 100N/m. That's like the stretchy resistance band you get in Pilates classes. I.e. only after it drops 1m you apply a force equivalent to 10Kg (I guess the robot weighs more than that). How could it possibly hold it up?
You need to tune the translation and rotation default classes for your actuators. These things have units, they are model dependent.
The model in the example above is an abstract example, you can't expect to just copy numbers from it.
PS I think you could have figured this out yourself if you tried a little harder 🙂
As a side note, we really hope to release some general sysID tutorial soon, might be helpful in this context.

It might help to read the implementation of mj_fwdActuation , and then re-read the relevant documentation section


Unable to debug locally- Is need the SSL certificate for local debug ?

We are trying to run the solution locally but we can't achieve this.
We faced the below error.

Which sample are you trying to run locally?  It looks like AV playback bot.  If that is the case you need to ensure that the start up project is the ccproj.

Please keep in mind that while you can get the AV playback bot to work locally, it is not by default configured to run this way.  Some code changes are required.  The only guidance we provide for local runs of samples can be found here and here.

We hosted the  AV playbackbot in azure cloud service and got the site URL as "http://test54321.cloudapp.net/". The next step is create the wildcard  certificate for our service. We confused for which domain we need to create the certificate. Shall we create a certificate for "*.Cloudapp.net" ?. If yes we can't get the no self signed certificate from the CA authority

If you are hosting in Azure Cloud Service, you do not need a wildcard certificate and do not need to follow the guidance for a "local run". Local runs are only meant for testing on dev boxes and not in Azure.
Also, you cannot get a certificate for *.cloudapp.net because that domain is not owned by you. The easiest way would be to create a CNAME entry in your custom domain and point it to the azure cloudapp entry.

We follow the azure deployment steps "https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/master/Samples/V1.0Samples/LocalMediaSamples/AudioVideoPlaybackBot/README.md". Here they mention to create the wildcard certificate.

I stand corrected. You can create the certificate for your custom domain that is pointed to your cloudapp.net site.

Is there more guidance needed here, or can I close the issue?

@subbiah46  were you able to get this working. Can you please get in touch with me at saraswat40 at gmail. Thanks


Changes for adding FinancialGiftDetailsResourceRepresentation

The FinancialGiftsDetails should not be on the FinancialGift itself.  You can imagine 10 gifts, but there will only ever be one FinancialGifts details per case..


Docs: clarify handling of Python references while Rust holds the GIL

The relationship between periods holding the GIL and object reference lifetime is not clearly described in the library documentation, leading to bugs like #1547 and #1556.  The guide makes a mention in "Advanced topics", but this reads like something that isn't important to know, calling it "invisible".
There should be at least mention in the library reference (maybe just on the topmost level in "Ownership and Lifetimes"?) and also in the guide in a more introductory section.

Agreed that better documentation is needed here. I'd held off because I kept thinking #1308 was just around the corner, but then I got sidetracked addressing lots of other bugfixes and cleanups.
The worst part of the current system, in my opinion, is that to make it safe PyO3 can only clear the pool on #[pyfunction] return, or when the Python GIL is actually dropped. (It used to be cleared when every GILGuard was dropped, but then it was super trivial to create use-after-free, see #864.) This leads to the extremely long held-object lifetimes which trip users up in #1547 and #1556.

Right, that means that the advice in https://pyo3.rs/v0.13.2/advanced.html isn't actually accurate anymore?

Closing as the Bound API will replace the GIL Refs discussed here.


[C#]fix：CPG did not correctly match the path to builtin_types.

The 'csharpsrc2cpg/src/main/resources/builtin_types' is not loaded into the classpath after the stage. #4474

cc: @AndreiDreyer @badly-drawn-wizards Note the way the resources are read here, may be important for Ruby

@chengkenyong For formatting, run sbt scalafmt

Think this issue is specifically to the packaged JAR, since I've been struggling with the same issue after pulling in the ruby type-stubs from the joern-type-stubs and getting them read during a joern-parse run. This solution works on the Ruby side too


Store state for an each ActionState explicitly

enum VirtualButtonStatus{
  JustPressed,
  Held(Duration),
  JustReleased,
  Released,
}

This allows users to track things like "press for X seconds" much more naturally, and simplifies the lifecycles in a natural way.

Done!


Can not recognise commands in a chat with multiple bot

Required Information

PHP version:7.0
PHP Telegram Bot version:latest
Using MySQL database: yes
Update Method: Webhook
Self-signed certificate: no
RAW update (if available):

Expected behaviour

Actual behaviour

Steps to reproduce

Extra details

This is related to #337, will continue the discussion there.
@fenghuilee If you feel this is a separate thing, please reopen and elaborate on the issue please.


Presets - API generalization

Issue:
The presets API, in the beginning, was to expose these methods: babel, webpack, preview & manager. Each one is about to extend a relevant part in the SB configuration.
After that, babelDefault was added to solve the babel 6 compatibility problems and remove the complexity of babel-merge.
What I did
From now, the core will expose presets loader that only knows to do the apply. Then core will wrap the apply with babel, webpack, preview & manager. Since presets object is passed deeper to the presets chain, any other preset will be able to extend it with the new functionality.

@igor-dv I still don't get the difference between babelDefault and babel. Is it like babelDefault is for babel@6?

One of the steps in babel config combination is loadCustomBabelConfig.js
export default function(configDir, getDefaultConfig) {
  const babelConfig = loadFromPath(path.resolve(configDir, '.babelrc'));

  if (babelConfig) {
    // If the custom config uses babel's `extends` clause, then replace it with
    // an absolute path. `extends` will not work unless we do this.
    if (babelConfig.extends) {
      babelConfig.extends = path.resolve(configDir, babelConfig.extends);
    }
    return babelConfig;
  }

  return isBabelLoader8() ? getDefaultConfig() : {};
}

it tries to load a custom babelrc from the .storybook dir, if it's not existing, and user is using babe 7, we are providing our default babel configuration.
Default babel config is also located in core (babe.dev.js and babel.prod.js)
There are some apps, (react, mithril and vue) that have to extend the defulat config with their plugins/presets, and we want to extend only our default config, and not the one, user provided in a .storybook dir.
In the beginning, I wanted to merge the defaults anyway with what user provides, and @Hypnosphi mentioned that it could break if user uses babel 6.


[SPARK-20023] [SQL] Output table comment for DESC FORMATTED

What changes were proposed in this pull request?
Currently, DESC FORMATTED did not output the table comment, unlike what DESC EXTENDED does. This PR is to fix it.
Also correct the following displayed names in DESC FORMATTED, for being consistent with DESC EXTENDED

"Create Time:" -> "Created:"
"Last Access Time:" -> "Last Access:"

How was this patch tested?
Added test cases in describe.sql

Test build #75009 has started for PR 17381 at commit 6890bbc.

Test build #75009 has finished for PR 17381 at commit 6890bbc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75009/
Test PASSed.

Merged build finished. Test PASSed.

cc @cloud-fan @wzhfy

Test build #75026 has started for PR 17381 at commit c194c19.

LGTM

Test build #75026 has finished for PR 17381 at commit c194c19.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75026/
Test PASSed.

Merged build finished. Test PASSed.

thanks, merging to master!


File heat names in Script Editor are very hard to read.

Duplicate of #11059

Ups.

Opening again. Deleted editor settings tres and created new project with new .godot file and colors didn't changed.

Can't reproduce. Deleting ~/.godot/editor_settings-3.tres is sufficient for me. Is the engine open while you delete the file?

@Noshyaar
Derp. <(^___^)" Thx. I probably had opened Editor...


Resolve UIWindowScene _keyWindowScene unrecognized selector

Description
Please feel free to edit anything you need to, just would like to get https://github.com/wix/Detox/issues/2895 resolved.

This pull request addresses the issue described here:
https://github.com/wix/Detox/issues/2895

In this pull request, I have
Resolved an iOS 15 issue:

Reference: https://stackoverflow.com/a/58447461/8665723

For features/enhancements:

n/a

For API changes:

n/a

https://user-images.githubusercontent.com/30021449/135011870-cfeb3ea3-f894-4425-99d0-a4aa2d1761ff.mov

detox-android-64-x-pr failing at

not sure if open issue

@alon-ha , this PR would need some of your love and attention soon. 🙏

https://github.com/wix/Detox/issues/2895#issuecomment-929328796

This build also working for my company's app and is able to successfully interact with screens and e2e tests pass.
https://user-images.githubusercontent.com/30021449/135152535-86b38916-03b7-437d-8cd9-989aceff72ba.mov

@calebmackdavenport  Thank you for the PR, I merged and will release a new version of detox.

Yep! Thanks again @mikehardy !! Hopefully this tag works


dns for security advisor

Hi guys,
following the recent PR from @hunchback , in this commit we extend the provided pipeline with custom stages to allow writing DNS packets to the object store. Since Skydive is a protocol analyzer, we utilize this powerful tool to provide the admin with the ability to monitor all the DNS traffic and log it for further use and analysis.

we enable logging all the DNS data via an array and not a single packet in each flow, since using a single packet results in overwriting data. e.g. for a typical DNS question at least two packets are generated, one with the AAAA code (for ipv6) and another with the A code (ipv4) and therefore keeping one packet will discard the others. To not overwhelm the system we keep this feature optional which can now be activated using a new extra layer flag.
also there was a minor bug in the DNS code that is now fixed in this commit.