Http client support

Support for testing rest endpoint via sniprun
Following http file syntax

At least the basics works:

Nice idea! Thank for contributing!
I'll do a more in-depth review asap

Thanks!  I'll keep this in draft status until I get some of the other http verbs implemented but I'd love feedback, especially on other trait functions and dependency/feature related stuff

The http parser doesn't curently implement variable substitution, so we will need to upgrade the dependency version once https://github.com/Laeri/http-rest-file/pull/1 gets merged if we want that feature

Hi @reavessm , I 'fixed' a modification you made due to an incorrect comment of mine (error_truncate stuff, sorry). Do you agree with the latest commit on the 'http' branch I just pushed ?

Oh, I like that!  Thank  you!  That really cleans it up.  I'll add that to this PR.  I'm going to reopen this for review.
I also think we shouldn't rerun anything in case somethings fails.  I can see a situation where you have three REST calls that you want to execute sequentially and if the second one fails, you don't want the third to run.  Especially considering this isn't naming any of the requests, I think sequential order is important

I also think we shouldn't rerun anything in case somethings fails.

Fair enough

@reavessm Are you satisfied with the state of your contribution ?
As for me, this is good :-)
However, I'd like to do my own dev merge and add some cosmetics (add to readme and doc) about HTTP support, so I can't give you permission to merge into master anytime you want via the review system. (Because of how most vim plugin manager works, the master branch has to be carefully synchronized with sniprun's binary releases)

@michaelb Yep!  I can change this to be based on the dev branch.  And if you need any help with docs I don't mind helping


Settings button does not work in ubuntu 17.10

Clicking the settings button does nothing in Ubuntu 17.10 beta at 1.0.0 alpha 33 (when installed via the deb file)

I've just released Alpha 34 - please try it. If it still doesn't work, try pressing Ctrl-Shift-I or F12 to bring up the debug console.

Alpha 34 is having the same results. Ctrl-Shift-I & F12 don't work either. Thanks for the quick reply!

You need to purge the old installation and install it again, this should fix, but the release 35 lost the autocomplete when you press tab. Roll-backing to the 34 release for now.


Black window shown instead of volume slidebar in Wolvic

This was initially reported in Wolvic.
The issue is that from inside Wolvic when the user clicks on the volume buttons in the 3DoF controller then a black opaque window is shown instead of the volume buttons. That slider is shown by the system not by Wolvic.
Actually we tried with the same version of Wolvic (1.2) in a Harmony 2.0 device and there is no issue. This must be a regression in Harmony 3.0.

some feedback from HVR SDK：we have test the XR demo on our side, no black window,and huawei vr screen app which use native openxr sdk that do not also happened.
so we need more information, maybe  you can reproduction this bug in the xr demo on your side, please share the xr demo project for us. or some configuration on wolvic.
maybe be it cause by the opengl configuration , hvr sdk get the texture from the apps, and texImage2D add the volume bitmap, when the apps and the sdk both use GLES20, this bitmap does not cause the black windows in xr demo app.
我们验证我们的XRdemo在混合模式下，透明混合没有产生黑框，并且VR投屏应用也未出现黑色方框问题，问题出现的根因可能与wolvic app的一些opengl配置相关，sdk 是获取当前应用送入的纹理，texImage2D添加了一张音量的bitmap，在大家都使用GLES20的情况下，这张bitmap并未在demo内引起黑框现象 ，能否告知我们wolvic app的相关配置，或者demo在什么情况下也会产生黑框，我们好进一步定位问题；

@dingsing2021 We configure GL in the method BrowserEGLContext::Initialize (BrowserEGLContext.cpp line 27).
These are our EGL requirements for selecting a configuration:

EGL_RED_SIZE is 8
EGL_GREEN_SIZE is 8
EGL_BLUE_SIZE is 8
EGL_ALPHA_SIZE is 8
EGL_DEPTH_SIZE is 24
EGL_STENCIL_SIZE is 0
EGL_SAMPLES is 0
EGL_RENDERABLE_TYPE includes EGL_OPENGL_ES3_BIT_KHR
EGL_SURFACE_TYPE includes EGL_WINDOW_BIT or EGL_PBUFFER_BIT

We configure our textures with:
glTexParameteri(GL_TEXTURE_EXTERNAL_OES, GL_TEXTURE_MIN_FILTER, GL_LINEAR));
glTexParameteri(GL_TEXTURE_EXTERNAL_OES, GL_TEXTURE_MAG_FILTER, GL_LINEAR));
glTexParameteri(GL_TEXTURE_EXTERNAL_OES, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE));
glTexParameteri(GL_TEXTURE_EXTERNAL_OES, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE));

Please let me know if there is any other information that could be useful.
/CC @svillar

feedback from HVR SDK：
here is a way to workaround ,set the target_sdk to 30. we have tested in the demo project.
build_versions.target_sdk = 30
build_versions.target_sdk_wave = 30
https://github.com/Igalia/wolvic/blob/95470dbcb0e74f02c28cc7613c0b5c1d1b91b44f/versions.gradle

feedback from HVR SDK： here is a way to workaround ,set the target_sdk to 30. we have tested in the demo project.
build_versions.target_sdk = 30 build_versions.target_sdk_wave = 30
https://github.com/Igalia/wolvic/blob/95470dbcb0e74f02c28cc7613c0b5c1d1b91b44f/versions.gradle

Thanks. We'll verify that it works and upload a patch soon.

I can confirm that solves the issue for us. We should still identify why v31 causes that issue, but in the meantime it's a good workaround.


Update Build Notes. Add Steps for compilation via VS2015

Hi,
I have updated Build Notes to add compilation steps using VS2015 and have successfully tested it.

Continuous Integration build is failing because of the following error
"Error uploading artifact the storage: Remote server returned 500: Operation could not be completed within the specified time". It has nothing to do with my PR.

Thank you for your contribution.
This would make Captura buildable by a larger number of users. 👍


Refactor test settings and access rights

Fixes Issue
Fixes https://github.com/Hyperfoil/Horreum/issues/1674
Changes proposed
In order to properly fix the issue, I had to slightly refactor the UI for Test settings and access rights.
This is the list of changes I did:

[x] Moved the Access rights tab into the Settings one, this way you can set the proper permissions during the Test creation
[x] Kept Test Tokens creation/deletion in a separate tab (which will replace the Access one, now called Tokens)
[x] Refactored the Tokens management to be consistent with other UI screens
[x] Moreover, once tokens are update the changes are automatically reflected in the UI without any reload page
[x] The new Tokens tab is NOT visible during Test creation as the backend API requires an existing Test to properly add/delete tokens.

With this new UI, users are able to create a new Test with custom permissions, either Public or Protected (which is something not working before)
Here a brief summary of UI changes in the form of before/after:
Settings
Before:

After:

Tokens
Before:

After:

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.

@lampajr when I am testing this with a backup of production, have you seen these when you have tested this change?

Mmmh I do not remember any error like that, especially because I did not touch the backend :thinking: but let me check if I can reproduce the same.

I can see the request is performed, but it looks working on my side:

Are you experiencing in some specific situation? On my side I tried creating new test and updating those settings and tokens,

@lampajr when I am testing this with a backup of production, have you seen these when you have tested this change?

Mmmh I do not remember any error like that, especially because I did not touch the backend 🤔 but let me check if I can reproduce the same.

I see the same issue in master, please ignore the exception


Improve delete file

Updated to latest version all dependencies.
Improve and fix the method to remove a file
If someone of the community could try this PR and give me feedback about it ?
Thanks :)

@clorichel // @jopmiddelkamp // @Rekhyt
Could you confirm this update on your site ?
Thanks for your contribution :)

Hey @Lith 👋 thanks for the ping! Good idea 🤓
Sadly though, we've moved to the strapi-provider-upload-aws-s3 plugin so we don't have a setup anymore to test this update. Nothing related to this very plugin, but to some additional features we need which are on AWS and not on GCP (yet).
Hosting files is obviously key to a CMS: be aware I've recommended the Strapi team to take ownership of this plugin and/or hire you to help them do so (and so much more 🤗)! Actually recommended them to maintain an upload plugin for at least the big 3 (AWS they do, GCP and Azure is missing) so they get a larger potential user base, and everyone is safer with Strapi fixed versioning (aka non-independent versioning) lerna strategy.

Hi @clorichel and thank you for your message and your help :)
I understand your mind, it will be simplest when this plugin will be provided by Strapi himself. I've take back this plugin because the previous developer has abandoned the maintenance, and my business need it, so I decided to share to the community my version, and the success was bigger than I expect ^^
I will make a PR on Strapi directory directly, maybe this will integrated quickly.
If you want share with me some fonctionnality missing on the plugin, I will try to implement it.
Thanks


Why this line of code arose in?

CUBEMAP_PATH = "./assets/images/cubemap/"
Forgive me i dont use go language, but by roughly seeing, this line  has no use, and there is no cubemap Folder. perhapse is my miss.

Hi fuzexin, you are right, it's not in use. I started this project by copying the code of another project of mine. This line is simply a copy-paste artifact that I haven't deleted yet.


el8: replacements are not restored after a test case finishes

Packit's recording tests. When I run them in this order, they fail because git interaction is still being recorded - the two test cases have different expectations about the state of the repo (fetch is being run and it does not fetch the thing that is needed):
tests_recording/test_api.py::ProposeUpdate::test_changelog_sync PASSED
tests_recording/test_api.py::ProposeUpdate::test_comment_in_spec PASSED
tests_recording/test_api.py::ProposeUpdate::test_version_change_exception PASSED
tests_recording/test_local_project.py::TestLocalProject::test_checkout_pr FAILED
tests_recording/test_local_project.py::TestLocalProject::test_checkout_pr_no_merge FAILED

When I run only the local_project tests, they pass just fine.
So either we need to explicitly restore gitpython replacements or figure out why they not being restored before starting new test cases.

Hi @TomasTomecek
I have to look at it, deepely.
But in generic, I know about similar issues, causes by various chaching inside projects. E.g. if git uses some @functools.lru_cache cache decorators, or projects uses some chaching of data, (I've met it whne mocking nitrate library it caches all objects what was already readed) -> causes that it is dependent on order of tests, untill you disable these functions what caches data, between tests,
This sounds to me as similar issue. It is also why I try to use tmt to run each tests searatery, so that then tests itself cannot be influenced by python, but sideeffect is that it is slow, because of calling pytest for every tests.
So solution here is that I try to find these caching functions and disable/clear caches or make it tests order independent.


webpack devServer configuration : "‘Access-Control-Allow-Origin

Hi all
i'm try to "play" with Webix Jet (https://www.gitbook.com/book/webix/webix-jet/details) that use webpack; now i have the problem with "Access-Control-Allow-Origin " and i was trying to set the "Access-Control-Allow-Origin'" on Headers
below my webpack.config.js file where i have added
  devtool: 'cheap-module-eval-source-map',     devServer: {         headers: {             'Access-Control-Allow-Origin' : '*',             'Access-Control-Allow-Headers': 'Origin, X-Requested-With, Content-Type, Accept'         }
also with this add, i receive always error :  CORS header ‘Access-Control-Allow-Origin’ missing
this my webpack.config.js
`var path = require("path");
var webpack = require("webpack");
module.exports = function(env) {
var pack = require("./package.json");
var ExtractTextPlugin = require("extract-text-webpack-plugin");
var production = !!(env && env.production === "true");
var babelSettings = {
	extends: path.join(__dirname, '/.babelrc')
};

var config = {
	entry: "./sources/myapp.js",
	output: {
		path: path.join(__dirname, "codebase"),
		publicPath:"/codebase/",
		filename: "myapp.js"
	},
	devtool: "inline-source-map",
	module: {
		rules: [
			{
				test: /\.js$/,
				loader: "babel-loader?" + JSON.stringify(babelSettings)
			},
			{
				test: /\.(svg|png|jpg|gif)$/,
				loader: "url-loader?limit=25000"
			},
			{
				test: /\.(less|css)$/,
				loader: ExtractTextPlugin.extract("css-loader!less-loader")
			}
		]
	},
	resolve: {
		extensions: [".js"],
		modules: ["./sources", "node_modules"],
		alias:{
			"jet-views":path.resolve(__dirname, "sources/views"),
			"jet-locales":path.resolve(__dirname, "sources/locales")
		}
	},
	plugins: [

new webpack.HotModuleReplacementPlugin(),
new ExtractTextPlugin("./myapp.css"),
new webpack.DefinePlugin({
VERSION: "${pack.version}",
APPNAME: "${pack.name}",
PRODUCTION : production
})
],
devtool: 'cheap-module-eval-source-map',
devServer: {
headers: {
'Access-Control-Allow-Origin' : '*',
'Access-Control-Allow-Headers': 'Origin, X-Requested-With, Content-Type, Accept'
}
}
};

if (production) {
	config.plugins.push(
		new  webpack.optimize.UglifyJsPlugin({
			test: /\.js$/
		})
	);
}

return config;

}
`

I'm not sure I understand in your example where you are using this module, though. Can you point it out?

Hi dougwilson
thanks for your interest. Premise that i not expert in NodeJs,  I will try to explain what i did:

I downloaded webix jet from  https://github.com/webix-hub/jet-start/archive/master.zip
unpacked and installed webix jet in Ibm i (As400) via npm install (in Ibm i we run  NodeJs V6.9.1)
As Dependencies of webix Jet, there is  webpack i think that in installing step also webpack has been installed.
Now if in the Webix Jet app i try to call a web service that run in another domain different from where run Webix Jet, i receive the error :
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://dom.com:10003/jsondemo/wcont.pgm. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing)
i looked for this error and the workaround seems to enable the  server to "Access-Control-Allow-Origin".

i tried to insert in the webpack.config.js  file
this lines in black  .. but the error  Cross-Origin Request Blocked, remains
hope now is more clear
thanks in advance
see also here https://forum.webix.com/discussion/31880/webix-jet-and-cross-origin-resource-sharing#latest
                plugins: [    new webpack.HotModuleReplacementPlugin(),                         new ExtractTextPlugin("./myapp.css"),                         new webpack.DefinePlugin({                                VERSION:"${pack.version}",                                APPNAME: "${pack.name}"`,
PRODUCTION : production
})
],
devtool: 'cheap-module-eval-source-map',
devServer: {
headers: {
'Access-Control-Allow-Origin' : '*',
'Access-Control-Allow-Headers': 'Origin, X-Requested-With, Content-Type, Accept'
}
}
    };

`

I'm not familiar with webpack or any of those things, so not sure how to help. I xan help with using this module if you're having trouble using it, but I don't see you using it so there isn't anything I can really help with in those examples.


[Java] Checker Framework annotations for AutoCloseables in arrow-memory-core are incorrect

Describe the enhancement requested
AutoCloseables.close works with nulls and collections of nulls, but isn't annotated appropriately, making downstream usage harder.
Component(s)
Java

take

In particular, this is due to the fact that the class org/apache/arrow/util/AutoCloseables.java is not referenced inside the memory core, which means that nullables cannot be de-referenced in those close methods.

Let me add that manually.

Also, see https://github.com/apache/arrow-adbc/pull/1495 where I have added type stubs to override annotations in some Arrow Java libraries.


[PDI-19777] Bug fixes by integrating Rest.java changes submitted by r…

…eporter

:warning: Build finished in 26m 30s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 1 test(s) failed:
org.pentaho.di.trans.steps.metainject.MetaInjectMigrationTest.testMigration (click to expand)
after the migration names that need migration should change to the new ones and all other should be kept the same expected:<DAT[ABASE_FIELD_NAME]> but was:<DAT[E_RANGE_START_FIELD]>

Tests run: 4082, Failures: 1, Skipped: 14    Test Results

:information_source:  This is an automatic message

:warning: Build finished in 25m 7s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 1 test(s) failed:
org.pentaho.di.trans.steps.metainject.MetaInjectMigrationTest.testMigration (click to expand)
after the migration names that need migration should change to the new ones and all other should be kept the same expected:<DAT[ABASE_FIELD_NAME]> but was:<DAT[E_RANGE_START_FIELD]>

Tests run: 4082, Failures: 1, Skipped: 13    Test Results

:information_source:  This is an automatic message

:warning: Build finished in 22m 57s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 1 test(s) failed:
org.pentaho.di.trans.steps.metainject.MetaInjectMigrationTest.testMigration (click to expand)
after the migration names that need migration should change to the new ones and all other should be kept the same expected:<DAT[ABASE_FIELD_NAME]> but was:<DAT[E_RANGE_START_FIELD]>

Tests run: 4082, Failures: 1, Skipped: 13    Test Results

:information_source:  This is an automatic message

:warning: Build finished in 24m 35s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 1 test(s) failed:
org.pentaho.di.trans.steps.metainject.MetaInjectMigrationTest.testMigration (click to expand)
after the migration names that need migration should change to the new ones and all other should be kept the same expected:<DAT[ABASE_FIELD_NAME]> but was:<DAT[E_RANGE_START_FIELD]>

Tests run: 4082, Failures: 1, Skipped: 13    Test Results

:information_source:  This is an automatic message

:warning: Build finished in 23m 55s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 1 test(s) failed:
org.pentaho.di.trans.steps.metainject.MetaInjectMigrationTest.testMigration (click to expand)
after the migration names that need migration should change to the new ones and all other should be kept the same expected:<DAT[ABASE_FIELD_NAME]> but was:<DAT[E_RANGE_START_FIELD]>

Tests run: 4082, Failures: 1, Skipped: 13    Test Results

:information_source:  This is an automatic message

:warning: Build finished in 23m 11s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 1 test(s) failed:
org.pentaho.di.trans.steps.metainject.MetaInjectMigrationTest.testMigration (click to expand)
after the migration names that need migration should change to the new ones and all other should be kept the same expected:<DAT[ABASE_FIELD_NAME]> but was:<DAT[E_RANGE_START_FIELD]>

Tests run: 3971, Failures: 1, Skipped: 12    Test Results

:information_source:  This is an automatic message


Automatic publishing of Helidon CLI to SDKMAN

SDKMAN is a popular JDK and SDK version manager, it would be very convenient to be able install the Helidon CLI with it as most of competitors are available there.
Installing Helidon CLI would be like:
sdk install helidon

Instead of:
sudo curl -LJ -o /usr/local/bin/helidon \
https://github.com/oracle/helidon-build-tools/releases/latest/download/helidon-cli-linux-amd64 && \
sudo chmod +x /usr/local/bin/helidon

Also switching the versions:
sdk default helidon 2.1.2

Moved to oracle/helidon-build-tools/issues/352


Fix the go module name/path.

@ringods It appears I can't merge this.  Should I be able to do that?

@ringods Sorry to keep pinging you, but could you merge this & then release 1.0.0?  We have it working against a cluster & would like to go into production against this code if possible.


@jit hangs on lambda with "large number" of conditional statements

I have some lambda functions of arithmetic expressions (including piecewise implemented with if/else) which are auto-generated using sympy. On some of those functions, jit and vectorize work great. On others, they hang indefinitely. I'm not sure why and I'm hoping to get some guidance or perhaps help to diagnose a bug. The functions are simple arithmetic but have lots of small operations.
lambda_fast_liquid.txt
lambda_slow_bcc.txt
The first one works without issues.
import numpy as np
import numba
with open('lambda_fast_liquid.txt') as file_:
    fast_func = eval(file_.read(), np.__dict__)
jitted_fast_func = numba.jit(fast_func)
assert jitted_fast_func(0., 0., 0.) == 0.

The second one hangs (numba 0.22.1).
import numpy as np
import numba
with open('lambda_slow_bcc.txt') as file_:
    slow_func = eval(file_.read(), np.__dict__)
jitted_slow_func = numba.jit(slow_func) # hangs
assert jitted_slow_func(0., 0., 0., 0., 0.) == 0.

The hanging function is spending a lot of time here: https://github.com/numba/numba/blob/1902d7f0cfdab11ec75aab0b5adbc8f8ab2d8740/numba/dataflow.py#L675

Thanks to @shoyer I tried replacing my nested if/else statements with this function:
@numba.vectorize
def where(condition, x, y):
    if condition:
        return x
    else:
        return y

This works very well and seems to work around this issue. (See #1530 for why I don't just use numpy.where.)

I'm glad you were able to find a workaround, but this definitely looks like a problem for us when dealing with extremely complex expressions.  Reopening so we can track solution of this.

I let this run for 7 hours, and it never completed.  When I finally killed it, the backtrace looked like this:
Traceback (most recent call last):
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/compiler.py", line 243, in run
    res = stage()
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/compiler.py", line 385, in stage_analyze_bytecode
    self.interp = translate_stage(self.bc)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/compiler.py", line 716, in translate_stage
    interp = interpreter.Interpreter(bytecode=bytecode)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/interpreter.py", line 103, in __init__
    self.dfa.run()
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 27, in run
    self.infos[blk.offset] = self.run_on_block(blk)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 71, in run_on_block
    self.dispatch(info, inst)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 81, in dispatch
    fn(info, inst)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 321, in _binaryop
    lhs = info.pop()
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 657, in pop
    return self.make_incoming()
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 672, in make_incoming
    ib.request_outgoing(self, ret, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 687, in request_outgoing
    ib.request_outgoing(self, phiname, stack_index)
  File "/Users/stan/anaconda/envs/numba_dev/lib/python2.7/site-packages/numba-0.22.1+13.g1902d7f-py2.7-macosx-10.5-x86_64.egg/numba/dataflow.py", line 685, in request_outgoing
    assert self.incoming_blocks

Verified that this is still a problem with Numba 0.26.0.

This works on Numba 0.43.1, takes a minute or so but does it. Closing.


Reproducible build on 1.6.0

exports.js from the 1.6.0 npm package differs greatly when compared to exports.js built from the 1.6.0 repo commit.

(left is from npm, right is built from repo)
To build from repo (tested with Node 14/16/18):

Clone the repo
npm install
npm run prepare

This might be related to #28 as I don't know what npm/node versions should be used.
1.6.0 from npm does work for fixing authentication for user's cookies but the version built from the repo does not. Is this due to not having correct dependency versions (due to npm/node), is there something else that should be done to reproduce the prod build, or is there work missing in the npm version that is not in the repo?

exports.js is built using Node 18.16.1. You need to make sure you have no local changes and you have the version of the npm dependencies as defined in the package.json file (not any versions compatible with those versions).

I have re-ran the npm run prepare locally and produced the same result as uploaded to npm. Closing as not an issue.


Add the ability to convert nodes to dot

Just using this for my RubyConf talk but I figured I'd upstream it anyway.

Good idea! I've added some documentation for it.


Move tokens impl to the new transaction model

Also, incorporate changes described in https://github.com/MinaProtocol/mina/issues/9182

closing in favor of #9744


Makes log overlay configurable

Foillowup to #84 to allow the log overlay behavior to be modified via the config file.

(Marking as a draft until the underlying PR is merged to avoid reviewing twice)

Needs a rebase, I'll merge once done. Great work, thanks!

Rebased!


Release new gem version with argument matching

This is a good testing suite, but I have a need for the broadcast argument matchers from pull request #1. The current version of the gem is 0.0.1 and this behavior isn't included yet.
I can refer to this Github repo in my Gemfile of course, but I prefer not to do that with any library for very long. Would you be willing to release a new version of this gem with the new behavior?

done :)


Store protocol filed in dependencies

Storing protocol fields in dependencies would allow us how service communicate and for example highlight when inter-service communication happen via HTTP (potential perf improvement).
Related to https://github.com/jaegertracing/spark-dependencies/issues/67

it would be useful to store a general k-v map with each link. It would allow extensions like this without hacking the db schema every time

Another use-case is to show failed transactions per service https://github.com/jaegertracing/spark-dependencies/issues/77.
This could be represented by aggregated error-tag with a number of instances.


[Regression] Unable to use between to filter date range in a search route

as of 0.12.3 i am unable to filter a date range using a between operator whereas it used to work before

hi @chihabhajji
Thank you for your sharing.
I fixed it in MR#554 and released 0.12.4.


Specify ruby 1.9 or greater required for gem.

Ran into an issue that cost me a few minutes using pry-rails, so I figured it wouldn't be bad to make it more explicit in the gemspec that Ruby 1.9 or greater is required, and shows up as a dependency in ruby gems.  I was able to use version 0.2.2 just fine with a Ruby 1.8.7/ Rails 3.2 app.  We're almost done upgrading to Ruby 2.2 for that app, but I figure there's plenty of sites still on 1.8.7 or earlier.  Great gem by the way.

Sure, can't hurt I guess. Thanks for the PR.


source:deploy not respecting wait flag

I am having trouble getting the waittime option to work when using "sfdx sfpowerscripts:source:deploy" in the CLI. I have tried -w 90, --waittime 90, and --waittime=90, but I keep getting this message "The deploy request did not complete within the specified wait time [0 minutes]."
We would definitely want devs to be able to see validation results directly from our CI/CD tool rather than needing to login to the Salesforce environment, or ideally without running the sfdx force:mdapi:deploy:report command.
Any ideas? Thanks!
Originally posted by @wedaft in https://github.com/Accenture/sfpowerscripts/discussions/305

This issue is fixed in  the following releases
cli: 1.6.6
azurepipelines: 18.0.57

This issue is fixed in  the following releases
cli: 1.6.6
azurepipelines: 18.0.57


Single text edits never go into UndoRedoService

@alexdima thanks, DEBUG helps me figure out why these edits are in two different groups. The bulk edit (https://github.com/microsoft/vscode/issues/101789#issuecomment-699063512) includes a text edit and a notebook edit, and we pass in the same undoRedo group. However when applying the text edit, since tasks.length === 1, it does not use the undoRedo group passed in (if there are more than one text edit, they then are put in the same group).
https://github.com/microsoft/vscode/blob/4aa873b4d18136dc5bd6622b1b2eb3335c99ebbc/src/vs/workbench/contrib/bulkEdit/browser/bulkTextEdits.ts#L215-L239
I'm wondering if we should allow pass in undoRedoGroup in task.model.pushStackElement() (and all its inner pushStackElement call)
Originally posted by @rebornix in https://github.com/microsoft/vscode/issues/101789#issuecomment-700122151

Possible fix:
--- a/src/vs/workbench/contrib/bulkEdit/browser/bulkTextEdits.ts
+++ b/src/vs/workbench/contrib/bulkEdit/browser/bulkTextEdits.ts
@@ -217,13 +217,13 @@ export class BulkTextEdits {
                                throw new Error(`${validation.reason.toString()} has changed in the meantime`);
                        }
                        if (tasks.length === 1) {
+                               const task = tasks[0];
                                // This edit touches a single model => keep things simple
-                               for (const task of tasks) {
-                                       task.model.pushStackElement();
-                                       task.apply();
-                                       task.model.pushStackElement();
-                                       this._progress.report(undefined);
-                               }
+                               const singleModelEditStackElement = new SingleModelEditStackElement(task.model, task.getBeforeCursorState());
+                               this._undoRedoService.pushElement(singleModelEditStackElement);
+                               task.apply();
+                               singleModelEditStackElement.close();
+                               this._progress.report(undefined);
                        } else {
                                // prepare multi model undo element
                                const multiModelEditStackElement = new MultiModelEditStackElement(

This also comes up in #107739

Thanks!


Make a direct link / button to iOS App Settings

Feature description
Right now we need to go to iOS Settings > WebSSH in order to change parameters.
Some other parameters are always inside the app...

Keep an unified way to set parameters!
Give a way to access iOS App Settings from a link / button
#38

https://stackoverflow.com/a/58821331
guard let url = URL(string: UIApplication.openSettingsURLString) else {
    return
 }
 if UIApplication.shared.canOpenURL(url) {
    UIApplication.shared.open(url, options: [:])
 }

https://jeffstechtutorial.blogspot.com/2014/06/ios-settings-bundle-with-extra-child.html


Iox #27 add client and server examples [stacked PR #6]

Pre-Review Checklist for the PR Author

[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-#123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit messages are signed (git commit -s)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[x] All checks have passed (except task-list-completed)
[x] Assign PR to reviewer

Notes for Reviewer

This PR add examples for the typed and untyped API for the Client and Server
Checklist for the PR Reviewer

[x] Commits are properly organized and messages are according to the guideline
[x] Code according to our coding style and naming conventions
[x] Unit tests have been written for new behavior

[x] Each unit test case has a unique UUID

[x] Public API changes are documented via doxygen
[x] Copyright owner are updated in the changed files
[x] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Relates to #27

Please add a new doc/website/examples/request_response.md.


Add DelegatedManager system Optimism kovan and staging deployment [SIM-194]

Staging Mainnet Deployment

[x] ManagerCore: 0xe3Ebf3788Fab3de919da7332e7b72899414d3E80
[x] DelegatedManagerFactory: 0x4E86bd25eac00812243295d7Ad7Cb59cee3f79D8
[x] IssuanceExtension: 0xD59D7CcCdcAacb4c283bA6FeC950eDf7D087dAd5
[x] StreamingFeeSplitExtension: 0xFfA0B13283B76e1278Fa5072b2da04cb9534b937
[x] TradeExtension: 0x9a7671DB5d28DD85f05D67ac18ba38F4B3862904

Staging Mainnet Transactions

Initialize ManagerCore with DelegatedManagerFactory, IssuanceExtension, StreamingFeeSplitExtension, and TradeExtension: 0xf395144faa0ae7c246f70d693e1ff7efba17bac100b2902cf9a4f1b873f0d19d

Kovan Deployment

[x] ManagerCore: 0x13C5A1444CC7cF0bCae366ed5BDe13d46dba3311
[x] DelegatedManagerFactory: 0x6C9A0eAE685a454Edf1f74B027e8910a5A72A6A0
[x] IssuanceExtension: 0x96956b695177C8C33Db01635378E008aC5E5EEC0
[x] StreamingFeeSplitExtension: 0x06Ed895C81d252FFe693f4A15ce7292b4cAb5612
[x] TradeExtension: 0xC4300E01c37020bcF471aefA16Ca8eFE1618E939

Kovan Transactions

Initialize ManagerCore with DelegatedManagerFactory, IssuanceExtension, StreamingFeeSplitExtension, and TradeExtension: 0xf015fccf819b6fccdf28184bd009d36d2b04ba7bbc7b2f215bc14d2f92b22276

:tada: This PR is included in version 1.0.0-t1.1 :tada:
The release is available on:

npm package (@test dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


5PM event title change

@edlu77 if further changes, make a new PR and ping us when its ready. We need quick turnaround on these website changes.


Support IE11

This doesn't run on browsers that need native support of template literals. Can it be transpiled?

@mhluska yeah man it's transpiled check the dist folder

@4r7d3c0 @z-vr the dist folder is not included in the package.json. Also looks like the build folder is just a copy of the src folder, not transpiled.


Docker build 失败

Docker Version:  23.0.1
System: Debian GNU/Linux 11
[+] Building 15.6s (12/19)
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 855B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/node:18-alpine                                                                                0.2s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 5.66kB                                                                                0.0s
 => [base 1/1] FROM docker.io/library/node:18-alpine@sha256:ffc770cdc09c9e83cccd99d663bb6ed56cfaa1bab94baf1b12b626aebeca9c10                                                                                0.0s
 => CACHED [runner 1/5] WORKDIR /app                                                                                0.0s
 => CACHED [builder 1/5] RUN apk update && apk add --no-cache git                                                                                0.0s
 => CACHED [builder 2/5] WORKDIR /app                                                                                0.0s
 => CACHED [deps 1/4] RUN apk add --no-cache libc6-compat                                                                                0.0s
 => CACHED [deps 2/4] WORKDIR /app                                                                                0.0s
 => CACHED [deps 3/4] COPY package.json yarn.lock* package-lock.json* ./                                                                                0.0s
 => ERROR [deps 4/4] RUN   if [ -f yarn.lock ]; then yarn --frozen-lockfile;   elif [ -f package-lock.json ]; then npm ci;   else echo "Lockfile not found." && exit 1;   fi                                                            15.3s
------
 > [deps 4/4] RUN   if [ -f yarn.lock ]; then yarn --frozen-lockfile;   elif [ -f package-lock.json ]; then npm ci;   else echo "Lockfile not found." && exit 1;   fi:
#0 0.647 yarn install v1.22.19
#0 0.678 warning package.json: License should be a valid SPDX license expression
#0 0.803 warning<EMAIL_ADDRESS>License should be a valid SPDX license expression
#0 0.806 [1/4] Resolving packages...
#0 2.351 warning @svgr/webpack > @svgr/plugin-svgo > svgo ><EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
#0 15.22 error Your lockfile needs to be updated, but yarn was run with `--frozen-lockfile`.
#0 15.22 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
------
Dockerfile:11
--------------------
  10 |
  11 | >>> RUN \
  12 | >>>   if [ -f yarn.lock ]; then yarn --frozen-lockfile; \
  13 | >>>   elif [ -f package-lock.json ]; then npm ci; \
  14 | >>>   else echo "Lockfile not found." && exit 1; \
  15 | >>>   fi
  16 |
--------------------
ERROR: failed to solve: process "/bin/sh -c if [ -f yarn.lock ]; then yarn --frozen-lockfile;   elif [ -f package-lock.json ]; then npm ci;   else echo \"Lockfile not found.\" && exit 1;   fi" did not complete successfully: exit code: 1

mistake


Add types declaration file

Resolves #1. I left some types marked as unknown since I couldn't work out what they are, would be much appreciated if you can let me know. Let me know if you have any other issues. :+1:

I amended the file as per your suggestions, hopefully having interpreted it correctly since this is quite a intertwining library. In the classes like Hook, Harness and so on I've used a 'utility type' named Pick, which just specifies the properties that are exposed in an object. I got what properties to expose from here. Let me know if you have any more questions / issues.

I amended the file as per your suggestions, hopefully having interpreted it correctly since this is quite a intertwining library. In the classes like Hook, Harness and so on I've used a 'utility type' named Pick, which just specifies the properties that are exposed in an object. I got what properties to expose from here. Let me know if you have any more questions / issues.

Thanks @geopic, I'll review in as soon as I can. It may be a few days as I have an assignment due in next week.

Thanks @geopic, I'll review in as soon as I can. It may be a few days as I have an assignment due in next week.


[Bug]: Error with Pydantic 2.6 when using open source models

Describe the bug
I get an error
"pydantic_core._pydantic_core.PydanticSerializationError: Unable to serialize unknown type: <class 'method'>"
when trying to test an open source model.
Using the latest versions:

autogenstudio             0.0.42a0
pyautogen                 0.2.10
pydatinc 2.6.0

But works when downgrading to pydantic 1.10.14!
Screenshots and logs

ERROR:    Exception in ASGI application
Traceback (most recent call last):
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/uvicorn/protocols/http/h11_impl.py", line 408, in run_asgi
result = await app(  # type: ignore[func-returns-value]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 84, in call
return await self.app(scope, receive, send)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/applications.py", line 1106, in call
await super().call(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/applications.py", line 122, in call
await self.middleware_stack(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/errors.py", line 184, in call
raise exc
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/errors.py", line 162, in call
await self.app(scope, receive, _send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/cors.py", line 91, in call
await self.simple_response(scope, receive, send, request_headers=headers)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/cors.py", line 146, in simple_response
await self.app(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 79, in call
raise exc
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 68, in call
await self.app(scope, receive, sender)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py", line 20, in call
raise e
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py", line 17, in call
await self.app(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/routing.py", line 718, in call
await route.handle(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/routing.py", line 443, in handle
await self.app(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/applications.py", line 1106, in call
await super().call(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/applications.py", line 122, in call
await self.middleware_stack(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/errors.py", line 184, in call
raise exc
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/errors.py", line 162, in call
await self.app(scope, receive, _send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 79, in call
raise exc
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 68, in call
await self.app(scope, receive, sender)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py", line 20, in call
raise e
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py", line 17, in call
await self.app(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/routing.py", line 718, in call
await route.handle(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/routing.py", line 276, in handle
await self.app(scope, receive, send)
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/starlette/routing.py", line 66, in app
response = await func(request)
^^^^^^^^^^^^^^^^^^^
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/routing.py", line 292, in app
content = await serialize_response(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/routing.py", line 180, in serialize_response
return jsonable_encoder(response_content)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/encoders.py", line 287, in jsonable_encoder
encoded_value = jsonable_encoder(
^^^^^^^^^^^^^^^^^
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/encoders.py", line 223, in jsonable_encoder
obj_dict = _model_dump(
^^^^^^^^^^^^
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/fastapi/_compat.py", line 177, in _model_dump
return model.model_dump(mode=mode, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/ale/anaconda3/envs/python311/lib/python3.11/site-packages/pydantic/main.py", line 308, in model_dump
return self.pydantic_serializer.to_python(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pydantic_core._pydantic_core.PydanticSerializationError: Unable to serialize unknown type: <class 'method'>
Additional Information
No response

Hi @alew3 ,
Thanks for adding this. The error seems to be related to pydantic not being able to correctly serialize response object from the model endpoint (when in strict mode)
I just pushed a fix that simplifies the returned object. Please upgrade you autogenstudio and let me know if you are still facing that issue.
pip install -U autogenstudio

Thanks @victordibia , just tested and it is working fine!

@alew3
Thanks for following up and closing this out!


Adding instruction for zsh for bazel build mixer

As titled :)

Hi @linsun. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/ok-to-test

@ldemailly I'll make the change you suggested.  I had thought of that too when making the patch. :)

@linsun: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
40166b6488279ed7889c4a2694c3721edfbcfa16
link
@istio-testing bazel test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[BUG] libunwind-dev missing for alpine build instructions

Describe the bug
debug.cpp:56:10: fatal error: libunwind.h: No such file or directory
56 | #include <libunwind.h>
To reproduce
Following the instructions on https://docs.keydb.dev/docs/build/
apk add --no-cache coreutils gcc linux-headers make musl-dev util-linux-dev openssl-dev curl-dev g++ bash git perl
git clone https://github.com/EQ-Alpha/KeyDB.git
cd KeyDB
make
....  libunwind.h: No such file or directory
apk add libunwind-dev
=> all ok

Hi @dbpaul,
I've put in a PR to fix the documentation to include the libunwind dependency for alpine.

Thanks, this is published here: https://docs.keydb.dev/docs/build#alpine


handleDocumentClick not being fired in Menu on Safari Mobile

As title states, the callback is not being fired on iOS9/Safari Mobile when clicking off the an open menu item. This prevents the menu from closing without clicking on another button/menu item.
Is this a known issue?

Note that this can be reproduced the example here - from http://react-toolbox.com/#/components/menu

Adding the touchstart listener resolves this issue:
events.addEventsToDocument({     click: this.handleDocumentClick,         touchstart: this.handleDocumentClick  })
Also adding touchstart to the relevant removeEventsFromDocument calls.
Should I make a PR for this (provided this is fine with some more testing) or is there a preferred way to approach this?

Thanks!


[Feature] Add a hamburger menu for small screen sizes

Description
I wanted to add new features to the project: a responsive hamburger menu for small screen sizes, to enhance the user experience.
Please assign me this task with hacktoberfest and gssoc-ext tag
Thanks You!
Best regards,
Screenshots
No hamburger menu

Checklist

[X] I have checked the existing issues.
[X] I have read the Code Of Conduct
[X] The changes don't break the code
[X] Please attach the screenshots and video of the development work once it is done

Hi @swaraj-das ,
I wanted to let you know that I’ve successfully implemented the hamburger menu functionality! It’s working as expected, and I’m excited to continue refining the project further. Let me know if there’s anything specific you’d like me to focus on.
Thank you for your guidance!
Best regards,
SRISHTI


Adding a logging event in case password validation fails.

[x ] Tick here to confirm that you have run RunCodeFormatter.ps1

Description:
Added a simple logging entry in case password validation failed.
Test:
Try logging in, with an invalid password. The log event should show up in the configured log.

Closing as @avodovnik will reopen from a new branch


Improve the error messages displayed alongside stack traces

Example:

I feel like bringing this closer to a stock Lua experience might be beneficial. While better documentation could help people understand what a "bundle" is and why the errors look the way they do, I remember being very confused when facing luvi(t)'s stack traces initially.

I randomly decided to look into this after getting annoyed by obscure error messages. There are a few separate concerns here:

The runtime's entry point (main.c) loads an unnamed Lua chunk, prompting LuaJIT to display the loaded string instead
The compiled bytecode objects don't include debug information, so "string " is the best that LuaJIT can do
Scripts are loaded as "bundle" via loadstring (this is how luvi does it internally), but the name may not be assigned correctly?
Files that are loaded via import similarly use loadstring with (probably) an incorrect or even no file name assigned?

The first two are easily fixed, but the latter two may need more investigation (this is from memory and I haven't checked the code).

Just for comparison, a typical error traceback in NodeJS:


pub: command not found

I just updated my flutter SDK (which includes Dart) and I'm now running into this error when I try to run Stagehand:
/home/nailuj29/.pub-cache/bin/stagehand: 7: pub: not found

You'll want to re-activate stagehand to update it:
$ dart pub global deactivate stagehand
$ dart pub global activate stagehand

That fixed my problem, thank you


How do I update columns from a given entity on Purview?

What is your desired outcome
I was successful by updating description for a given entity on Purview (in my case is a Kusto table). I am also trying to update each column description also, that way I could have all information in place for our users.
What have you tried so far
The way I did was:

Used the get_by_guid() function to retrieve all information I have and understand the response. So I saw that every column description is under the referredEntities dict.
Same query I used to update the entity description, I tried with create_or_update() function but despite the message is not retrieving any error, the descriptions is not being updated also.
My query:

# Define the keywords and updated description
updated_description = "New description for the asset"

# Create the entity input with the updated description
entity_input = {
  "referredEntities": {
        "typeName": "azure_data_explorer_column",
        "attributes": {
                "qualifiedName": "https://cluster.eastus.kusto.windows.net/database/DimensionDevicesTest#ID_VM",
                "name": "ID_VM",
                "description": updated_description,
                "userDescription": "
VM Id
",
            },
      },
  "entity": {
    "typeName": "azure_data_explorer_table",
    "attributes": {
      'qualifiedName': 'https://cluster.eastus.kusto.windows.net/database/DimensionDevicesTest',
      'name': 'DimensionDevicesTest',
    }
  }
}

try:
    # Call create_or_update to update the asset
    response = client_catalog.entity.create_or_update(entity=entity_input)
    print("Asset updated successfully:", response)
except HttpResponseError as e:
    print("Error updating asset:", e)

This the output of query above:
Asset updated successfully: {'guidAssignments': {'-271567942211068': 'f31eeb6a-d9b0-48d3-a461-f9f6f6f60000'}}
Desktop (please complete the following information):

OS: Windows 11 Enterprise, version 22H2, build 22621.2134
I am not using PyApacheAtlas library, I am using azure-purview-catalog to update my data

Additional context
The query that is working and that I am using to update my entity description is this one:
# Define the keywords and updated description
updated_description = "New description for the asset"

# Create the entity input with the updated description
entity_input = {
  "referredEntities": {},
  "entity": {
    "typeName": "azure_data_explorer_table",
    "attributes": {
      'qualifiedName': 'https://cluster.eastus.kusto.windows.net/database/DimensionDevicesTest',
      'name': 'DimensionDevicesTest',
      "userDescription": updated_description,
    }
  }
}

try:
    # Call create_or_update to update the asset
    response = client_catalog.entity.create_or_update(entity=entity_input)
    print("Asset updated successfully:", response)
except HttpResponseError as e:
    print("Error updating asset:", e)

HI, @guimatheus92  just to be clear, this is the Github repo for PyApacheAtlas, and not the Azure-Purview-Catalog package.
I'd encourage you to use PyApacheAtlas instead ;-)
However, to answer your question, you should create an array/list of column entities you want to update.  You should not place any updates in the referred entities section.  Your end result should look like your second block of code just with the azure_data_explorer_column instead.
# Define the keywords and updated description
updated_description = "New description for the asset"

# Create the entity input with the updated description
entity_input = {
  "referredEntities": {},
  "entity": {
    "typeName": "azure_data_explorer_column",
        "attributes": {
                "qualifiedName": "https://cluster.eastus.kusto.windows.net/database/DimensionDevicesTest#ID_VM",
                "name": "ID_VM",
                "description": updated_description,
                "userDescription": "
VM Id
",
            }
  }
}

try:
    # Call create_or_update to update the asset
    response = client_catalog.entity.create_or_update(entity=entity_input)
    print("Asset updated successfully:", response)
except HttpResponseError as e:
    print("Error updating asset:", e)

Sometimes you have to specify a required attribute or relationship attribute.  In this case, it looks like the table relationship attribute is required and the data_type attribute is required.  Your entity_input payload may have to look like this instead.
entity_input = {
  "referredEntities": {},
  "entity": {
    "typeName": "azure_data_explorer_column",
        "attributes": {
                "qualifiedName": "https://cluster.eastus.kusto.windows.net/database/DimensionDevicesTest#ID_VM",
                "name": "ID_VM",
                "data_type": "string",
                "description": updated_description,
                "userDescription": "
VM Id
",
            },
        "relationshipAttributes": {
                "table": {
                    "typeName": "azure_data_explorer_table",
                    "uniqueAttributes": {
                        'qualifiedName': 'https://cluster.eastus.kusto.windows.net/database/DimensionDevicesTest'
                }
            },
    }
}

I hope this helps.  You may have to go through Microsoft official channels to get a more complete answer if this isn't what you're looking for.

Closing this out but please feel free to reopen if you need additional guidance!


password encryption-decryption

First i would like to express my thanks for this awesome degiro-api. I'm new to using this package, so please forgive me if I ask a stupid question. Do you use an encryptor-decryptor for user name and password with the login module ? Or are they just visible in the login script, or stored in a readable file ?

Hello @AureliusMarcusHu,
it depends on what you need.
If it's just for testing, a quick way is to put the credentials into a file config/config.json:
{
    "user_token":123,
    "int_account":123,
    "username":"YOUR_USERNAME",
    "password":"YOUR_PASSWORD",
    "totp_secret_key":"OPTIONAL_TOTP_SECRET_KEY"
}

You might want to ignore this file from your project .gitignore.
I hope that helps you and other people that might read this.
Thanks


define a way to add interpreters

Now if I need a new interpreter but the scale basic one, i need to make a new image with the installation of the interpretation.
I should define a way to hook up interpreters from fuel files maybe, and define dynamically what's possible.

Can you give an example of what you want?
1st) Will the separate interpreter be already loaded or downloaded?
If it is loaded on demand, I would expect it would be cached somewhere.
2nd) Maybe we can change the interpreter just by changing the shebang:
#! /usr/local/bin/scale
=>
#! /usr/bin/env scale
or even better =>
#! /usr/bin/env pharo scale
=>
#! /usr/bin/env pharo scale --interpreter InterpreterClass

Dynamic magical variables that relies in code that may not be in the image. In the end is the import we were talking at the lab:
import file: 'myModule.st' into: #myMagicalVariable.
Or even also
import repository: 'github://whatever/project/bashFacade.st' into: #bash.
bash chmod: '+x' to: myFileRef.
The only thing we need to add is a nice way to define this kind-of-functions and persist this code in a more pharo way, so for developing this modules we can use pharo it self.

#! /usr/bin/env pharo scale --interpreter InterpreterClass
Beware, there are limitations on how many words after the shebang will be taken into account (depending on OS and shell versions, of course, because POSIX is a well-defined cough standard)


Select inside form does not update state on first change

Description
When using a 'select' field type inside a form with a<SubmitButton disableIfUntouched disableIfInvalid>{'Update'}</SubmitButton> , changing the select doesn't change the form state the first time you do it. You have to change the select again before the submit button is enabled.
Link to Reproduction
https://codesandbox.io/p/sandbox/gracious-sky-4xfg92?layout=%257B%2522sidebarPanel%2522%253A%2522EXPLORER%2522%252C%2522rootPanelGroup%2522%253A%257B%2522direction%2522%253A%2522horizontal%2522%252C%2522contentType%2522%253A%2522UNKNOWN%2522%252C%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522id%2522%253A%2522ROOT_LAYOUT%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522UNKNOWN%2522%252C%2522direction%2522%253A%2522vertical%2522%252C%2522id%2522%253A%2522clxdk04xv00063b6gkopidutx%2522%252C%2522sizes%2522%253A%255Bnull%252Cnull%255D%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522EDITOR%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522EDITOR%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522EDITOR%2522%252C%2522id%2522%253A%2522clxdk04xv00023b6gm793p8ke%2522%257D%255D%257D%252C%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522SHELLS%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522SHELLS%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522SHELLS%2522%252C%2522id%2522%253A%2522clxdk04xv00033b6glod3kexh%2522%257D%255D%252C%2522sizes%2522%253A%255B100%255D%257D%255D%257D%252C%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522DEVTOOLS%2522%252C%2522direction%2522%253A%2522vertical%2522%252C%2522id%2522%253A%2522DEVTOOLS%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522DEVTOOLS%2522%252C%2522id%2522%253A%2522clxdk04xv00053b6gncopdkw5%2522%257D%255D%252C%2522sizes%2522%253A%255B100%255D%257D%255D%252C%2522sizes%2522%253A%255B50%252C50%255D%257D%252C%2522tabbedPanels%2522%253A%257B%2522clxdk04xv00023b6gm793p8ke%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clxdk04xv00013b6gc979nb7k%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522FILE%2522%252C%2522filepath%2522%253A%2522%252Fsrc%252Findex.tsx%2522%252C%2522state%2522%253A%2522IDLE%2522%257D%255D%252C%2522id%2522%253A%2522clxdk04xv00023b6gm793p8ke%2522%252C%2522activeTabId%2522%253A%2522clxdk04xv00013b6gc979nb7k%2522%257D%252C%2522clxdk04xv00053b6gncopdkw5%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clxdk04xv00043b6gigpazbyw%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522UNASSIGNED_PORT%2522%252C%2522port%2522%253A0%252C%2522path%2522%253A%2522%252F%2522%257D%255D%252C%2522id%2522%253A%2522clxdk04xv00053b6gncopdkw5%2522%252C%2522activeTabId%2522%253A%2522clxdk04xv00043b6gigpazbyw%2522%257D%252C%2522clxdk04xv00033b6glod3kexh%2522%253A%257B%2522tabs%2522%253A%255B%255D%252C%2522id%2522%253A%2522clxdk04xv00033b6glod3kexh%2522%257D%257D%252C%2522showDevtools%2522%253Atrue%252C%2522showShells%2522%253Afalse%252C%2522showSidebar%2522%253Atrue%252C%2522sidebarPanelSize%2522%253A15%257D
Steps to reproduce

Change the Select to another value
See that the submit button is still disabled
change the select value again
see that the submit button is now enabled

Saas UI Version
2.5.8
Chakra UI Version
2.8.2
Browser
Google Chrome 125
Operating System

[X] macOS
[ ] Windows
[ ] Linux

Additional Information
No response

Weird, onChange is triggered, but it seems like the field stays untouched.
The touched state isn't updated in your example, but i can't reproduce it in the storybooks.


Standard Commons Logging discovery in action with spring-jcl

using docker image urlaubsverwaltung/urlaubsverwaltung:5.0.0-M6 running the application i receive this issue:
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts

Not that easy, liquibase brings opencsv that brings common-logging.
We do also directly use opencsv, which could/should be replaced with fastcsv I think.


Add tests for executeSystemTasks

Pull Request Test Coverage Report for Build 3479

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 70.142%

Totals

Change from base Build 3477:
0.04%

Covered Lines:
11154

Relevant Lines:
15902

💛  - Coveralls


Remove unnecessary dependencies from released NPM package

These dependencies are injected by generator spec.
However they are unnecessary for released react-on-rails package.
Even if the dependencies section is removed, it will back after $ rspec spec/react_on_rails/generators/install_generator_spec.rb is run.
I think it is unexpected behavior.
So I removed these dependencies and fix specs.
@Judahmeek @justin808
Can you review this PR? It this a correct way?

This change is

@tricknotes Can you please rebase on top of master. Then let's see the CI results.

rebased

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

https://travis-ci.org/shakacode/react_on_rails/jobs/294304640
hmm..., some tests are timeouted :<

@justin808
Now all tests are passed on Travis CI.
Could you review this PR?

This looks solid to me. @Judahmeek?

Nice work. However, I think that react-redux should at least be a peer dependency since it is referenced in ReactOnRails source code.

Thanks for your review, @Judahmeek !
Yes, react-redux is referenced by ReactOnRails.
However it seems from specs, generators and docs, not from production code.
Additionally, the ReactOnRails users who use react without redux don't need react-redux.
I think it may be a optional dependencies. Or I've misunderstand?

You're correct that it is an optional dependency.


Remove all default features

I know you juuuust published a breaking change. So this request is a bit too late. But I guess there might be a 0.8.0 release at some point in the future. That means you might not want to merge this just now. Unless you really agree with my argument here and go ahead with 0.8.0 very soon.
Would you consider making all features opt-in instead of on by default? There are people (including me) considering "default features" to be a design mistake in Cargo. They make it too easy to pull in stuff you don't need. Worst is when I directly depend on crate foo and I really want its feature some-feature to be disabled. But a transitive dependency also pulls in foo and they have not set default-features = false and involuntarily pull in some-feature in my dependency tree even though that transitive dependency is not even using it!

A related question is what the unstable feature really means? What does it mean in the context of this crate? It does not depend on nightly Rust. Do you intend to make API breaking changes under unstable without releasing a semver incompatible version of this crate? I personally have mixed feelings about that. Also again partially because transitive dependencies can enable it and suddenly cause semver breakage anywhere in the dependency tree. The documentation around unstable could be a bit better. And I can add it if you describe it.

It is currently unclear why Ws2812Esp32RmtDriver::write is unstable. The documentation for the method does not mention anything about it, or caveats there might be.

Note to self: some modification of README.md lacking, follow in #46.


[RO-3268] Bootstrap rpco without breaking artifacts

Because APT artifacts can not be used at kick time it's possible that
the basic installation of OSA can bring an environment ahead of our
current artifacted release. This change makes it possible for APT
artifacts to be present when bootstrapping the environment. When a
deployer runs a basic installation of RPC-OpenStack they have the choice
to enable or disable artifacts however if they chose to enable them all
package installations should come from our artifacted repo assuming
they're available.
This change ensures only the minimum requirements are installed on the system
prior to setting up the release and configuring our artifacted solutions.
To keep everything as idempotent as possible and to ensure we're using
playbooks to configure the deployment, the initial install will create an
rpc-ansible virtual environment in "/opt" using a cached version of ansible
from [ rpc-repo.rackspace.com ]. This simple ansible installation runs only
the required playbooks to get the deployment online. Once OSA has been
bootstrapped all future interactions can be run through the
openstack-ansible cli tool.
Non-Idempotent commands in scripts were have been moved into
playbooks where possible. Modules have replaced most of the
functions and if no suitable module was available the command module
was used but in the most idempotent way possible by leveraging local
facts.
Signed-off-by: Kevin Carter<EMAIL_ADDRESS>Issue: RO-3268

@prometheanfire this would not help the release distro version issues. starting from a .3 release with updates installed when the artifacts only support .2 would still result in a broken build. This change simply ensures we're not actively installing things that are known to break artifacts prior to the repos getting into place. We're now ONLY installing the three packages [python, python-yaml, python-virtualenv] which are the minimal requirements for anything else to run within RPC-OpenStack. While the argument could be made that even those three packages could break the build, they're necessary when starting from a fresh, minimal, system. If we want 100% chain of custody for package installs we're going to need to have the ability to preseed from rpc-repo, but we're not there yet.

I'm not sure what to say. Instead of a simple, low tech debt approach as done in https://github.com/rcbops/rpc-openstack/pull/2731 you would rather implement this. Personally, I think this is madness.

@odyssey4me it's not madness at all and address all of the concerns we had with idempotency and package chain of custody. The other patch is implementing techdebt by forcing users to consume artifacts and rewrite sources in a way that is irreversible. This solution identifies exactly what we need and only installs those components.

@cloudnull Suit yourself, I think this is madness. This does not help us implement a properly repeatable build and is a massive amount of tech debt to carry in comparison. This is over 300 lines added, plus a new venv, plus a wholly different way of doing the setup. The point of this rewrite was to reduce the wrappers and flatten the build. This is just adding layers, adding more possibilities for variation in our builds and making it harder to debug what's going on.
If this merges, I will work with it only because I have to. But, this is not an approach that I support.

@cloudnull Sure, as mentioned before - how this all goes ahead is not my call. All I'm looking for is resolution to the issue at hand, which is that the initial bootstrap of configuration currently does not cater for and does not respect the use of artifacts. This is causing downstream breakage in the artifact builds. So as long as this implements the use of apt artifacts immediately after executing install.sh then that helps. If it doesn't, then please let me know what must be executed afterwards so that I can adjust the artifact build process accordingly. Right now, this issue is a blocker for getting the builds to produce the correct artifacts as they're being polluted with non-artifacted apt packages when building.
So, if this is the way the team wants to go, that's fine. I just need a solution implemented to unblock the downstream work.

Now that this is reducing what we install to a KNOWN set of packages, can we just force install the same versions from the artifacted repo when that's set up?  AKA, go through known remediation steps to get artifacting working?

Rebased to pull in the latest changes from master.


Formidable V2 Filter issue

Support plan

Which support plan is this issue covered by? (Community, Sponsor, Enterprise): Free
Currently blocking your project/work? (yes/no): Yes
Affecting a production system? (yes/no): no

Context

Node.js version:16.20.0
Release Line of Formidable (Legacy, Current, Next): https://www.npmjs.com/package/formidable/v/2.1.2
Formidable exact version:2.1.2
Environment (node, browser, native, OS): node
Used with (popular names of modules): NextJS13

What are you trying to achieve or the steps to reproduce?

When I attached a file as png or another type. The formidable filter option returns false. In this false case formidable.parse() method does not give the form error invalid file type. variable formError always return null or undefined even if filter is  false.
 const allowedMimeTypes = ['application/pdf', 'application/msword', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document'];

                const formData = new formidable.IncomingForm({
                    keepExtensions: true,
                    allowEmptyFiles: false,
                    multiples: false,
                    filter(part) {
                        if (part && part.mimetype) {
                            return allowedMimeTypes.includes(part.mimetype);
                        }
                        return false;
                    },
                    uploadDir: "uploads/resume",
                    filename(name, ext, part, form) {
                        var currentTimeStamp = Math.floor(Date.now() / 1000);
                        return `resume_${currentTimeStamp}${ext}`;
                    },
                });

return new Promise((accept, reject) => {

                    formData.parse(req, (fromError, fields, files) => {
                        try {
                            if (fromError) {
                                const { resume } = files;

                                if ((resume as unknown as PersistentFile)) {
                                    const fileDetail = JSON.parse(JSON.stringify(resume));
                                    if (fileDetail) {
                                        fs.rmSync(fileDetail.filepath, { force: true });
                                    }
                                }

                                const response: ApiResponse<undefined | null> = { status: false, message: fromError, data: null };
                                return reject(res.status(500).json(response));
                            }

                            const response: ApiResponse<undefined | null> = { status: true, message: "Success", data: null };
                            return accept(res.status(200).json(response));

                        } catch (exception) {
                            const { resume } = files;
                            if ((resume as unknown as PersistentFile)) {
                                const fileDetails = JSON.parse(JSON.stringify(resume));
                                if (fileDetails.lenght > 0) {
                                    fs.rmSync(fileDetails[0].filepath, { force: true });
                                }
                            }
                            // console.error(exception);
                            const response: ApiResponse<undefined | null> = { status: false, message: `${exception}`, data: null };
                            return reject(res.status(500).json(response));
                        }

                    });
                });

What was the result you got?
formData.parse(req, (fromError, fields, files) => {})
fromError always return null or undefined even if formData filter option returns false.
What result did you expect?
fromError returns a valid file type filter error.

Behaves like Array.filter: Returning false will simply ignore the file and go to the next.
use form.emit('error') inside filter to make form.parse error (formData.emit('error') in your case)

I also recommend you to slugify ext as it is user input and may contain invalid characters
                    return `resume_${currentTimeStamp}${slugify(ext)}`;


Provide a i386 package for Ubuntu

I can only download amd64 from release. I need an i386 package(deb).

You're free to compile it yourself. Installing Rust applications is painless. The provided deb is ancient compared to git head.

@mmstick Compiling a application after every update is not what I intend to do. Do you have any plans to create a Ubuntu-PPA?

I do not use Ubuntu or Debian, and therefore I do not intend to create an Ubuntu PPA at this time. I do not particularly like Ubuntu's PPAs or the Debian packaging format, which are both convoluted processes. I will leave it up to someone else to offer a PPA if they choose to do so. I would have provided a Snappy package, but Canonical's Snappy format is a complete mess, doesn't support Rust, and will not work with applications that require PolicyKit. Likewise, as I do not use Fedora or any other RPM-based distributions, I will not be providing any RPMs or RPM repositories any time soon.
At the very least, I have been long providing an option in my Makefile that will automatically compile, package for Debian systems, and install it into the system, just by executing make ubuntu. All platforms supported by both Rust and GTK3 should be able to generate the packages, and do so in a matter of mere seconds. Then, you can choose to either never update the application, or occasionally execute git pull && make ubuntu to automatically update it.
There is no need to update the application unless you decide you want any updates that I push. Any updates that I push are not for the purpose of fixing errors but improving the quality of the source code or adding new features. By improving the quality of the source code, I primarily mean that I am always actively working on improving the readability of the code so that others may have a practical example to learn Rust from, or improving the performance the performance of the existing code with a few optimizations here and there, such as the following change:
// Initialize a String with the capacity of the file obtained from
// the file's metadata, and then read the contents of the file
// into the string. Return an empty String if it fails.
let capacity = file.metadata().map(|x| x.len()).unwrap_or(0) as usize;
let mut output = String::with_capacity(capacity);
file.read_to_string(&mut output).map(|_| output).ok().unwrap_or_default()

As this is a Rust application developed safely, there will never be any 'dealing with errors' that are common with software written in other languages. I always execute cargo test and cargo clippy before pushing any changes to the master, in addition to testing it out in practice. The Rust compiler has very power static code analysis that makes it incredibly hard to offer software that has errors, and so I doubt you'll ever find an error that isn't intended behaviour.
With each update, I have eliminated more and more instances of unwrap() in the source code and thus have eliminated practically all usage of unwrap(). The only places that still have unwrap() are used in places that cannot fail within reason, such as assuming that all systems running this application have systemd installed. You would be far more likely to have bugs in your distribution's version of GTK3 that causes errors than you would with this Rust software.

I don't think rust is entirely that immune to bugs - one of the main things to consider is dependency updates, which may be using unsafe code and/or rustc updates. It won't be as common, no, but important security updates do happen.
I don't use ubuntu or debian myself, but I'm 90% sure I can build deb packages successfully on this computer and I can do that for release versions if that would be helpful! I don't know much about maintaining a PPA though.

Dependency updates aren't a concern because they are statically linked into the binary at compile time, and because I am shipping the Cargo.lock file as well, anyone who builds this application will build with the exact same dependency versions. I do not push commits to update the Cargo.lock and Cargo.toml files without thoroughly testing every codepath anyway. The Cargo.lock file not only ensures that everyone who compiles the software is locked to the same version from Crates.io, but that even Git repositories are locked to the same commit.
Updates to rustc don't cause errors or bugs. Any breaking changes to the standard library API are reported as warnings by the compiler two or three releases in advance before making them compiler errors, which gives me plenty of time to update the code in advance. I develop with Rust Nightly so I have at least 24 weeks in advance to make changes to the code if there is an API breakage, which has happened effectively never ever since Rust 1.0 released. I also will not update a dependency without fixing any breakage in the API of those libraries.
Unsafe code isn't a bad thing, as it's useful to take advantage of the unsafe aspect of Rust to gain performance benefits when you can guarantee that it will not cause any issues. I used a few unsafe blocks to escape bounds checking of a few indexes and I can stand behind their usage as being safe. The only thing you have to worry about is bugs and security issues in C libraries that are being linked to, which in this case is GTK3 specifically. Rust applications do not need to be updated every time a C library updates, because C libraries are linked dynamically. If you get an update for GTK in your distribution, then this application will be using the updated version you installed without needing a recompile.
And finally, as for security bugs related to Rust software specifically, that is a non-issue because Rust does not allow any of the unsafe behaviour that security bugs exploit, at least not without using unsafe to start writing Assembly and linking to external C libraries. There has yet to be an incident where a Rust library was found to be vulnerable to a security bug, and the Crates website is capable of automatically sending an email out to all the developers who are using a vulnerable version, if that ever happens.

@mmstick With dependencies, that is literally what I'm talking about - all dependency versions are frozen when compiled. If there's an exploit discovered in a dependency which uses unsafe code, the only way to fix it is to get a new version of systemd-manager.
Rust is less prone to security bugs, but memory-safety isn't the only thing that causes exploits. Also, systemd-manager has dependencies (gtk-rs, etc.), which literally do use unsafe code and link to external C libraries in this program. It's not likely, but it's a complete possibility that an upgrade to systemd-manager will be required for security purposes.
I'm not really trying to refute your point entirely, but rust isn't a magic bullet. I use it, and love it, but I don't think it's reasonable to say that the only reason you'd ever upgrade is for new features.

@daboross gtk-rs isn't a concern because C libraries are dynamically linked. Any update to GTK does not require an update to a GTK-dependent application.

@mmstick Yes, but if there's a bug in unsafe gtk-rs code which causes a security concern, that would require an upgrade. I'm just trying to say that it's possible for any program, even ones written in rust, to have bugs which would require upgrading.

@mmstick I can help creating a PPA. But first we need to create a proper debian packaging. I noticed there is a single control file under debian/debian in your source tree. It would make things easy for me if you can create those other files....specially debian/copyright.
https://www.debian.org/doc/manuals/debmake-doc/ch04.en.html

I have added the copyright file.


⚠ Bofrost.lu has degraded performance

In 326aafe, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1760 ms

Resolved: Bofrost.lu performance has improved in 3a5e96e after 22 minutes.


Preparing for no files key when magnetizing

Motivation for changes:

I had torrent adding exceptions when waiting on magnetization. Torrent was actually added, so it's not showstopping, but feature is still defective.

Detailed changes:

Will supply default value of [] when trying to access status['files'], which might not exist.
Also made line a bit more Pythonic

Addressed issues:
This is the error I had.
2017-03-24 10:23 INFO     deluge        download_tv     REDACTED was not added to deluge! [Failure instance: Traceback: <type 'exceptions.KeyError'>: u'files'\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:393:callback\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:501:_startRunCallbacks\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:588:_runCallbacks\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:1184:gotResult\n--- <exception caught here> ---\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:1128:_inlineCallbacks\n/srv/seedbox/flexget-venv/local/lib/python2.7/site-packages/flexget/plugins/clients/deluge.py:744:_wait_for_metadata\n]

TODO
Line can also be:
if ('files' in status) and len(status['files']):

I have no strong opinion in either way.

Sure why not


How can I use 'setKeyMap'?

Hello,
I want to use the remote control's 'back' button with a keycode of 10009.
How can I use 'setKeyMap' to configure it?
Where should this 'setKeyMap' be placed to make it work?
Can you provide a simple example?

Hi.
This method can be called as soon as you initialize the navigation with init.
Documentation: https://github.com/NoriginMedia/Norigin-Spatial-Navigation#setkeymap
You can assign one or multiple key codes to the directions or enter handlers.


Video: Demo Inventory Management and Maintenance App

Make a video demoing the Inventory Management and Maintenance App! There is a good guided tour documented in these docs that you could work through on video. Do not need to show the install/code/underlying files but do show all the great features
Can do without sound or with audio narration (if with audio narration please check & fix the automatic captioning).
Context: ODK-X has started a youtube channel to share videos of how to do key tasks in ODK-X. Although these tasks are often explained in the documentation, we frequently get requests for videos and some things are easier to learn watching a video than reading documentation. We are working on getting videos in English & Spanish but also welcome contributions in other languages!

Please can I work on this??

@chinenyelilian thanks for helping with this documentation work! I have assigned to you! Let us know any questions.

@elmps2018 Please is there an existing demo server URL and login details for the the cold chain application?

Hi @chinenyelilian great question! There is not a demo server but there is a demo app you can download and push to your tablet. Details: https://docs.odk-x.org/cold-chain-intro/#installing-cold-chain . This one does require setting up a demo server to test the group permissions and things, if you are able to do that.

@elmps2018  Yes, I already have the app on my mobile device. I was setting up the sync endpoint and just wanted to clarify.
Thanks.

I have set up Sync Endpoint on Azure cloud service and created 2 users A and B on phpLDAPadmin and granted all permissions to user A. I've set the admin password and allowed non-encrypted connections on my mobile device. With User A, I have reset the App Server and synchronized from the server.
Everything looks fine but the Cold Chain Management app still displays "User is Not Authorized. Please Log In". I've synchronized as user A and B
@elmps2018 @wbrunette Please guide me.
I got the copy of the application from the app folder in the cold-chain-demo branch of the App Designer repository.

_

@chinenyelilian awesome work getting this all set up so far! Were you able to set up the different groups as well? https://docs.odk-x.org/cold-chain-intro/#installing-cold-chain has a warning about the groups.

@elmps2018 I used the groups created when the LDAP server was brought up.

@chinenyelilian using the groups created when following the default setup instructions is likely causing the problem since there are specific regional groups built into the app that are needed to access the data.

Okay, Thanks

@elmps2018  Please see link to the demo video and kindly review.
https://drive.google.com/file/d/1onYMGg3Fi785jJOyGAPdR3aggrYorlnI/view?usp=drivesdk

@chinenyelilian this is great glad you got it working! The one thing I wanted to check before posting to Youtube was whether you had changed or wanted to edit out the password/address if it's a server you have, don't want anyone messing that up!

@elmps2018, Please go ahead. I have changed the login parameters.

@chinenyelilian Great! Uploading next! Thanks for your help!


build: bump angular

@angular/cdk         18.1.4 -> 18.2.0
@angular/cli           18.1.4 -> 18.2.0
@angular/core       18.1.4 -> 18.2.0
@angular/material 18.1.4 -> 18.2.0
PR Checklist

[ ] Unit Tests have been added for new changes
[ ] API tests have been updated if applicable
[ ] All commented code has been removed
[ ] If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. open-amt-cloud-toolkit/repo#365 )

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

GitHub release
v3.16.0

Your semantic-release bot :package::rocket: