Works as standalone but crashes as plugin on Ableton [BUG]

Serious error occured
I run the installer to have the full install (vst3 + standalone). The standalone runs just fine, but once I open the VST3 on Ableton 11 Lite, Ableton crashes with "serious error occured".
Any way around that ?

Can you fill out the rest of the info requested in a Bug Report? Thanks!

Continuing in #473


Callback when all rows appear in the DOM

I'm trying to execute some JQuery actions on all the table rows after the component has fully rendered/updated by placing logic in componentDidUpdate(). However, this is executed before some rows have appeared in the DOM, causing my JQuery procedure to query nodes that don't exist yet. It is not until
this.setState({         rowsToRender: this._rowBuffer.getRowsWithUpdatedBuffer()       }); is called that the remaining rows appear in the DOM.
How can I execute my procedure once all the buffered rows are rendered in the DOM?

I was able to resolve this by delaying the calls on the current stack by using setTimeout(function() { //Some JQ },0);


Can't get all values from query params

First of all, I simply loved the idea of the project! Congrats!
Usually I create a similar structure for my personal projects and it was really fun seen it here, so I'll try to contib with my experiences :)
So, going to the suggestion:
I noticed that the interfaces fuego.ContextWithBody[Body] and of couse, fuego.ContextNoBody doesn't have a method to grab all Query params from the request, insted of it, you only have those methods to handle with query params:
QueryParam(name string) string
QueryParamInt(name string, defaultValue int) int // If the query parameter does not exist or is not an int, it returns the default given value. Use [Ctx.QueryParamIntErr] if you want to know if the query parameter is erroneous.
QueryParamIntErr(name string) (int, error)
QueryParamBool(name string, defaultValue bool) bool // If the query parameter does not exist or is not a bool, it returns the default given value. Use [Ctx.QueryParamBoolErr] if you want to know if the query parameter is erroneous.
QueryParamBoolErr(name string) (bool, error)
QueryParams() map[string]string

Non of them can handle with multiple values, so my suggestions is to add a new method like QueryParamArr(name string) []string to handle with this type of things.
Also, for the QueryParams() map[string]string I would not recoment you guys to treat the query params as an map[string]string because it will suffer by the same problem which I mentioned just above. So, my seconde suggestion is to change it for url.Values. It is an standard type for query params in go and it's a map[string][]string.
So, as I said in another issue, I already know how to fix thos problems, if you want I can open a PR with the fix :)
Take care :D

Yes very good idea!
Happy to review a PR if you have time. I'll do it next monday otherwise, I'm pretty busy this weekend.
Thank you for reporting this, feedback is always valuable 🙏🏼

@EwenQuim It's should be fuego.ContextWithParams[T] there to automatic format incoming GET request parameters, which should be use like:
fuego.Get(api, "/test", func(c fuego.ContextWithParams[types.TestRequest] (*types.TestResponse, error) {
		req := c.Params()
		// handle this req params
                _ = req
		return &types.TestResponse{
			hello: "world",
		}, nil
	})

The parameters parsing can be use inside fuego (from *http.Request:
func ParseFormValues[T any](r *http.Request) (*T, error) {
	if err := r.ParseForm(); err != nil {
		return nil, fmt.Errorf("parseform: %w", err)
	}

	params := make(map[string]any, len(r.Form))
	for key, value := range r.Form {
		switch len(value) {
		case 0:
			continue
		case 1:
			params[key] = value[0]
		default:
			v := make([]string, len(value))
			copy(v, value)
			params[key] = v
		}
	}

	res := new(T)
	decoder, err := mapstructure.NewDecoder(&mapstructure.DecoderConfig{
		DecodeHook: DecodeHook,
		Result:     res,
	})

	if err != nil {
		log.Fatal("failed to get a new decoder: ", err)
	}
	if err := decoder.Decode(params); err != nil {
		return nil, err
	}

	return res, nil
}

The DecodeHook is a function to parse Go type like time.Time, e.g. my types.Request should like:
type CentralServerTopoServerServerRequest struct {
	CreatedAt netip.Addr `json:"from" validate:"required"`
}

@EwenQuim  It's should be fuego.ContextWithParams[T] there to automatic format incoming GET request parameters, which should be use like:
fuego.Get(api, "/test", func(c fuego.ContextWithParams[types.TestRequest] (*types.TestResponse, error) {
		req := c.Params()
		// handle this req params
                _ = req
		return &types.TestResponse{
			hello: "world",
		}, nil
	})

The parameters parsing can be use inside fuego (from *http.Request:
func ParseFormValues[T any](r *http.Request) (*T, error) {
	if err := r.ParseForm(); err != nil {
		return nil, fmt.Errorf("parseform: %w", err)
	}

	params := make(map[string]any, len(r.Form))
	for key, value := range r.Form {
		switch len(value) {
		case 0:
			continue
		case 1:
			params[key] = value[0]
		default:
			v := make([]string, len(value))
			copy(v, value)
			params[key] = v
		}
	}

	res := new(T)
	decoder, err := mapstructure.NewDecoder(&mapstructure.DecoderConfig{
		DecodeHook: DecodeHook,
		Result:     res,
	})

	if err != nil {
		log.Fatal("failed to get a new decoder: ", err)
	}
	if err := decoder.Decode(params); err != nil {
		return nil, err
	}

	return res, nil
}

The DecodeHook is a function to parse Go type like time.Time, e.g. my types.TestRequest should like:
type TestRequest struct {
	CreatedAt netip.Addr `json:"from" validate:"required"`
}

The validation process can be accomplished the same way like using InTransform like ContextWithBody

We're more likely to support #174 instead of the proposed syntax, for the reasons enumerated above


1.20.1 invalid mod file error

Only this mod is loaded
here's the latest.log https://mclo.gs/3cQTZsi

Minecraft version: 1.20.1
Forge version: 47.0.35

still not working?

still brokey

You messed up "Implementation-Version:" in MANIFEST.MF something with your buildscript seems to be brokey in 1.20.1, it runs fine when changing it to "Implementation-Version: 1.20.1-5.0.0"

fixed in new version


[string] dump and load

Took me some time to understand how stream works. The end() method is the key. May worse to add this to the documentation

@nolanlawson Here is the same test extended with the reverse function: load.

Any feedbacks?

Sorry for the late reply - yes, this looks like a great change, and very helpful. :) I'm happy to merge, but I would kinda prefer to have an additional test rather than change an existing test. (Yes I know you added test behavior, but... paranoia. :wink:)
Anyway I will merge and then add the old test back in as well. I'm seeing a green run in Travis, which means that the test passed. Thanks a bunch!

294b8aa8a6c0f2d1262af280427ca68fe78bda77

Make senses! Cool :+1:


[FEATURE REQUEST] footer of Great People

Description
we can add a quote at the footer or some design.

please assign me this issue

there's a quote section for quotes.


8.x

This is a full rewrite based on the bugs, shortcomings, unintuitive behavior, and popular features I've noticed after a couple years of maintaining and triaging issues and pull requests in this library.
There are several docs added in this branch in the docs/ folder. They contain instructions and notes on how everything works. This rewrite is not 100% backwards compatible. There is a high-degree of backwards compatibility, but some features were not implemented because of their susceptibility to bugs, complexity, and lack of diligent testing.
Issues taken into consideration during this rewrite
Changes
The most notable (breaking) changes and fixes are:

Always run middleware regardless of route match — see issues with the always call middleware label
Deprecate use('/path', ...) — nesting routers has been a long-time bug in that it modifies the router which was nested, tainting that router for future usage. Routers are not modified when nesting now and can be recursively nested in any order and in many contexts. See issues with with the nested routes bug
Add .nest method for nesting routers — when .use exists for nesting, it has a hard time keeping its greedy prefix for middleware matching from affecting the paths of the router its nesting. Passing a router directly See issues with the greedy ending wildcard label and prefix label
Snapshot routes when calling .routes() — so router modifications after that point have no effect on previously exported routes — context
Run parameter middleware in order of declared param handlers — see issues with param ordering label
Router#redirect() no longer accepts a route name for the first argument — It must be a path
Params are available at the start of the execution stack (including middleware) — see issues with param ordering label
Param handlers are added to middleware stack, not called during param parsing from the path — see issues with param ordering label
Nested routers' middleware, param handlers, routes are ordered and composed during the routes() snapshot phase. see readme for execution order.
Switch to ava for testing
Rewrite test suite based on existing
Only compatible with node.js >= 8

Execution order
The order in which you call .use, .nest, and .param dictates the execution order. Nested routers middleware, param handlers, and routes are inserted relative to the parent router's other middleware, param handlers, and routes. The ordering of .nest calls is recorded to insert their middleware, param handlers, and routes in the correct order as declared.
Here's an example:
const parent = new Router();
const child1 = new Router();
const grandchild = new Router();
const child2 = new Router();

parent.use(middlwareA);
parent.use(middlwareB);
parent.param('foo', ...);
parent.use(middlwareC);
parent.param('bar', ...);

child1.param('corge', ...);
child1.use(middlewareD);
child1.use(middlewareE);
child1.use(middlewareF);

child2.use(middlewareG);
child2.param('baz', ...);
child2.param('quz', ...);
child2.use(middlewareH);
child2.use(middlewareI);

grandchild.use(middlewareJ);
grandchild.param('grault', ...);

child1.nest(grandchild);
parent.nest(child1);
parent.nest(child2);

The ordering of execution is as follows:
=== stage I
dispatch -> find matching route, set to context
matching order (FIFO)

routes from parent router
routes from child1
routes from grandchild
routes from child2

=== stage II
invoke middleware

parent router (receiver of .routes())

middleware a
middleware b
foo param middleware
middleware c
bar param middleware

child1 (nested first)

corge param middleware
middleware d
middleware e
middleware f

grandchild

middleware j
grault param middleware

child2 (nested second)

middleware g
baz param middleware
quz param middleware
middleware h
middleware i

=== stage III
Invoke matched route

A troubleshooting utility has also been introduced to visually inspect router state:
Troubleshooting
You can visually inspect a router's current state with inspect.
const router = new Router();
const v1Router = new Router();
const v2Router = new Router();
const healthRouter = new Router();
healthRouter
  .use((ctx, next) => {
    // A
    return next();
  })
  .get('/_health', (ctx, next) => {
    // B
  });
router.get('/version', () => {
  // C
});
v1Router.post('/post', () => {
  // D
});
v2Router
  .use((ctx, next) => {
    // E
  })
  .post('/post', () => {
    // F
  });
router.nest(healthRouter);
router.nest('/v1', v1Router);
router.nest('/v2', v2Router);

After the setup above, we can use inspect to turn the router into a string showing its middleware, routes, nested routers, and route details.
const { inspect } = require('koa-router/utils');

console.log(inspect(router));
// =>
// * Router
// ├── middleware
// │   ├── anonymous
// │   └── anonymous
// ├── routes
// │   ├──     GET  /version            /^\/version(?:\/(?=$))?$/i
// │   ├──     GET  /_health            /^\/_health(?:\/(?=$))?$/i
// │   ├──    POST  /v1/post            /^\/v1\/post(?:\/(?=$))?$/i
// │   └──    POST  /v2/post            /^\/v2\/post(?:\/(?=$))?$/i
// └── nested
//     * Router
//     ├── middleware
//     │   └── anonymous
//     ├── routes
//     │   └──     GET  /_health            /^\/_health(?:\/(?=$))?$/i
//     └── nested
//     * /v1 prefix
//     └── nested
//         * Router
//         ├── middleware
//         ├── routes
//         │   └──    POST  /post         /^\/post(?:\/(?=$))?$/i
//         └── nested
//     * /v2 prefix
//     └── nested
//         * Router
//         ├── middleware
//         │   └── anonymous
//         ├── routes
//         │   └──    POST  /post         /^\/post(?:\/(?=$))?$/i
//         └── nested

Opening this PR for visibility and comments. Next steps are to publish an alpha, get feedback from developers, make changes, add more docs, publish beta as next tag, wait for issues, and release 8.0.

v8.0.0-alpha.1 is now tagged and published @next on npm.
npm install koa-router@next to try it out


Add ignoreCorruptFiles feature for Parquet reader

To close https://github.com/NVIDIA/spark-rapids/issues/4727.
GPU parquet reader will throw an exception when reading some corrupt parquet files even if the user has set "spark.sql.files.ignoreCorruptFiles" to true for coalescing or multi-threaded reading. While PERFILE reading is ok since it is in the wrapper of FilePartitionReader which has handled the exceptions. see https://github.com/apache/spark/blob/branch-3.2/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/v2/FilePartitionReader.scala#L39-L59
For multi-threaded reading, when detecting the wrong footer or failing to copy the files into the HostMemoryBuffer, it will totally ignore the whole file. For example, assuming there are 3 row groups, and multi-threaded reader has successfully copied the first 2 row groups into the HostMemoryBuffer, and it failed to copy the 3rd row group caused by IOException, then the multi-threaded reader will ignore the loaded first 2 row group and return empty HostMemoryBuffer. But for CPU, it may have returned the first 2 row groups to users.
For coalescing reading, we have first calculated the offset and size for each file and launched multi-threads to copy the row groups into the fixed location of the HostMemoryBuffer. Assuming we're coalescing 1.parquet, 2.parquet and 3.parquet files. First, we have allocated a total HostMemoryBuffer for 1.parquet, 2.parquet and 3.parquet and launched 3 threads to copy 1.parquet, 2.parquet and 3.parquet separately. If we failed to copy 2.parquet. Then the re-generated parquet file will only contain 1.parquet, empty hole (for 2.parquet, but failed to copy, we just left the empty hole), 3.parquet
This PR only considers the exceptions that happened in reading footer and copying row groups. It didn't catch the exception when decoding in GPU. So, even if ignoreCorruptFiles is enabled, it will throw an exception when cudf failed to decode the host buffer.

build

We still need to do the same thing for text-based file formats like ORC/JSON

build

CI failed on Databricks env. will check it

There's quite a bit missing from this PR. It currently only addresses Parquet, but there are many other readers that need to support this config setting (or preclude being on the GPU if it is set). In addition, the error handling only covers the small section of the read where we are examining the footer, but we could get I/O errors or other exceptions when trying to read the row group data, decode it on the GPU, etc.

Thx Jason. The new commits have considered the situation reading footer and copying row group, but it didn't catch the exception when CUDF failed to decode the buffer. The exception CUDF failed to decode may caused by CUDF code itself, so I tend to throw this exception.
And as to other readers like ORC/JSON, I'd like to have some follow ups.

The exception CUDF failed to decode may be caused by CUDF code itself, so I tend to throw this exception.

The same "but it might be a bug in the code" logic applies whether we're talking about cudf or the Spark/Parquet code.  I'm OK with addressing this in a followup because it's a bit tricky to do (and may require some assistance within cudf), but we need to file a tracking issue for it since this isn't completely covered.

And as to other readers like ORC/JSON, I'd like to have some follow ups.

That's fine, but then please file the tracking issues and link to the original issue (or a new epic issue per discussion below).
This PR is marked as closing the original issue, so please either unlink the issue as we will not properly support ignoring corrupt files with just this PR or file a separate issue (maybe an epic) to track fully implementing this feature.

Yeah, It's kind of tricky, but I don' have more ideas on how to do that. I think it's really not reasonable to consider a "correct" file into a corrupted file caused by cudf/spark-rapids code itself.
Hi @jlowe, I'd like to hear your opinions.

build

After discussion with @GaryShen2008, we think we should fall back coalescing reading to cloud reading when ignoreCorruptedFile is set.
Coalescing reading is trying hard to coalesce many parquet files at a time. If one row group of one file is corrupted, we will ignore the whole coalesced files if we decide to try-catch cudf decoding. While PERFILE/Multithread readings only ignore the corrupted file.

build

build

Overall the code looks OK for Parquet, but there still needs to be followup issues for ORC, CSV, JSON, etc. Also it looks like Databricks may not support ignoreCorruptFiles, as the test failed on the CPU, not the GPU. We may need to skip that test on Databricks.

Yeah, just tested on databricks env, which will throw exception on CPU. But with this PR, the corrupt files will be ignored when ignoreCorruptFiles is set to true.

build

build


Update insider-risk-management-solution-overview.md

Updated licensing information for Insider Risk Management
Per issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/9538

@JohanFreelancer9 Please copy review

Docs Build status updates of commit 40de157:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/compliance/insider-risk-management-solution-overview.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@msbemba

@msbemba Gentle reminder

Docs Build status updates of commit a0a84aa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/compliance/insider-risk-management-solution-overview.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@JohanFreelancer9

@robmazz Please merge this PR. Thanks


Add undefined to Symbol.declarations' type

Symbol.declarations now has type Declaration[] | undefined.

While you are at it, could you fix the rest of #24706 as well?

@ajaff I'm going to see how easy it is to fix valueDeclaration too.


feat: add solidity test coverage

This PR adds tests for solidity contracts.

Re-organize development dependencies
Add solidity-coverage plugin and add to hardhat config
Add test script to package.json

Will merge this in after #28


Issue/108 update

Hi a @quockhanh ,
Please help me review this PR

Personally, I think we may need a better solution, such as ListFormData  (not only contains Values but also other properies like Errors)
I would keep this PR open until we have better solution

Close to find better solution


When creating template you can specify name but when listing sandboxes and templates it is referred to as alias

null
E2B-467

It is fixed in the new beta SDK.


Octave PSD in Welchs Method

In endaq.calc.psd.welch(df, bin_width=1, **kwargs) we could add parameters:

fstart=None
octave_bins=None

for example (or a better way!), that if specified we do the initial linear PSD calculation, convert it to octave, and return the octave PSD right away instead of making them call the to_octave function.

I'll close this, this is possible in batch: https://docs.endaq.com/en/latest/endaq/batch.html#endaq.batch.GetDataBuilder.add_psd


Show error message if user details fail to load

Summary
If fetching the user details failed (e.g. due to server / network error), the user settings page continued to display a loading spinner. Now it correctly shows an error message.
Also shows an error message toast if fetching any of the main data (zones, user, teams, orgs) fails.
Fixes https://github.com/appuio/cloud-portal/issues/226
Checklist

[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking,
as they show up in the changelog
[x] Update tests.
[x] Link this PR to related issues.

above build steps are failing due to npm being unavailable because CloudFlare is down. I will re-run as soon as these are up again


Governable Block Size

### Tasks
- [ ] https://github.com/celo-org/celo-blockchain-planning/issues/314
- [ ] https://github.com/celo-org/optimism/issues/132
- [ ] https://github.com/celo-org/celo-blockchain-planning/issues/192

Right now the L2 gas limit is set in the SystemConfig contract, its an Ownable contract. Curious if this works for you? We could consider adding a more RBAC based solution where different accounts can modify different variables, or this could be done via an external contract that owns the SystemConfig

Currently works as is. We don't really have anything that would depend on this and consider it purely informational.


Can't differentiate click v.s. dragend

I have a path within my svg that I'd like to register click event handler.
                path.addEventListener("click", e=>{
                    //do things
                });

If I need to differentiate between normal click event v.s. dragend event, I can normally do something like this.
                path.addEventListener("click", e=>{
                    if (e.defaultPrevented) return; // dragged!
                    //do things
                });

However, if I use svg-pan-zoom, the e.defaultPrevented is always set to false, so I can not differentiate between clitck v.s. dragend (dragging the svg canvas to pan it around). Is this a bug with svg-pan-zoom, or is there a workaround?
UPDATE..
The click event will not fire if I release the mouse button while I am still moving my mouse. I am not sure why it makes a difference, but maybe pausing my mouse before releasing a button screw something up?

I have this problem too... probably the best solution is to flag somehow that we are dragging, and ignore the click event until the dragend.

I am having this problem too :( any solutions?


New package: LGElectronics.webOSEmulator.3 version 3.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/111892&drop=dogfoodAlpha

/AzurePipelines run

Close with reason: Stale pull request;


Progress Bars

Let make the lower block with Colorful Progress Bars 100% filled from the very beginning. That will be only the upper part where progress bars will be animated one by one.

Moved https://github.com/epicmaxco/vuestic-admin/issues/199


Would be nice to implement setLineDash()

Not vital, of course, but this method is currently missing: https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/setLineDash

Just seen this. Thanks!


tfdbg and tf.data API:  Inconsistency with handling dataset iterators' OutOfRangeError

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):  Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Mac OS Mojave v10.14.4
TensorFlow installed from (source or binary):  Binary (PIP)
TensorFlow version (use command below):  pip install tensorflow==1.13.1
Python version:  3.6.2
CUDA/cuDNN version:  N/A (found bug on CPU version)

print(tf.GIT_VERSION, tf.VERSION):  ==>  'v1.13.0-rc2-5-g6612da8951' 1.13.1
Describe the current behavior
Different behavior while using tfbdg responding to catching OutOfRangeError required for iteratively looping on dataset iterators from the tf.data API.  Using tfdbg command  'run -t 100', we get execution as normally expected.  Using tfbdg command 'run -f has_inf_or_nan', we get a cascade of errors.
Describe the expected behavior
Running tfbdg with a filter vs running without a filter produces the same code errors when dealing with catching OutOfRangeErrors.
Code to reproduce the issue
import tensorflow as tf
from tensorflow.python import debug as tf_debug

dataset = tf.data.Dataset.range(3)
iterator = dataset.make_initializable_iterator()
next_element = iterator.get_next()
result = tf.add(next_element, next_element)

with tf.Session() as sess:

  sess = tf_debug.LocalCLIDebugWrapperSession(sess)

  sess.run(iterator.initializer)
  while(True):
    try:
      output = sess.run(result)
      print(output)
    except tf.errors.OutOfRangeError:
      print("End of dataset")
      break

Other info / logs
FYI: This code snippit is a condensed version of a similarly-structured larger project I am working with; in that larger project (which I am unable to condensely reproduce at this time) the difference between running with tfbdg with a filter produces error 'OutOfRangeError is not iterable' and halts execution whereas tfdbg running without a filter does not and executes normally as intended (ie. slightly different than the discrepency displayed in the code snippet above).

I was able to reproduce the reported behavior in TF 1.13.1

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.

It is no longer needed. Thanks,
Daniel ReMine

On Feb 19, 2021, at 2:10 PM, Alfred Sorten Wolf<EMAIL_ADDRESS>wrote:

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Invalid 2fa Key

Now before you mark this as a dupe, I get the error when putting in the long 2fa app key, the one that has repeats of 4 digits, not the key from the authenticator app. Forgive me if an issue has been raised about this, but the issues section is so flooded with people who put the code from the authenticator app in the field...
I'm not going to reveal the 2fa app key but its in there and its correct so im unsure why im getting this error...

Same for me

Please search. Dupe #1617

Please search. Dupe #1617

If you read my post again, you'd know that's not the issue I'm having...
I am NOT inputting the code from my authenticator app in there. I am inputting the code given by Amazon when attempting to add a new authenticator...

Please fill out the template and provide logs. It should obfuscate the key, but double check before posting.

Please confirm you are following this. An example key is included. The code checks the code to make sure it's cryptographically valid. That is the error you're likely seeing but can't figure it out without logs.

Please confirm you are following this. An example key is included. The code checks the code to make sure it's cryptographically valid. That is the error you're likely seeing but can't figure it out without logs.

I have follow that, but not success.....If I would mannage with logs, I will be able to post them....

Ok so upon not touching it for 2 weeks (exams), it seems to now be in the mood to work? So atleast from my end all is well now, though I'm not sure how long that will last...

The other cause could be your system time wasn't updated so the key generation wouldn't sync, but who knows.
Glad it resolved itself.


[AIRFLOW-2860] Update tests for druid hook

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

This pull request updates the tests for airflow/hooks/druid_hook.py and also adds an assert so that timeout must be greater than or equal to 1 second. This should fix the failing build in #3707.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
I ran nosetests /tests/hooks/test_druid_hook.py

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3710 into master will increase coverage by 59.86%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           master    #3710       +/-   ##
===========================================
+ Coverage   17.69%   77.56%   +59.86%
===========================================
  Files         204      204
  Lines       15766    15767        +1
===========================================
+ Hits         2790    12229     +9439
+ Misses      12976     3538     -9438

Impacted Files
Coverage Δ

airflow/hooks/druid_hook.py
88.88% <100%> (+88.88%)
:arrow_up:

airflow/utils/operator_resources.py
86.95% <0%> (+4.34%)
:arrow_up:

airflow/settings.py
79.33% <0%> (+4.95%)
:arrow_up:

airflow/executors/__init__.py
63.46% <0%> (+5.76%)
:arrow_up:

airflow/utils/sqlalchemy.py
73.91% <0%> (+10.86%)
:arrow_up:

airflow/utils/decorators.py
91.66% <0%> (+14.58%)
:arrow_up:

airflow/__init__.py
80.43% <0%> (+15.21%)
:arrow_up:

airflow/hooks/oracle_hook.py
15.47% <0%> (+15.47%)
:arrow_up:

airflow/task/task_runner/__init__.py
63.63% <0%> (+18.18%)
:arrow_up:

airflow/utils/db.py
33.33% <0%> (+18.25%)
:arrow_up:

... and 162 more

Continue to review full report at Codecov.

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

I think this pr is blocking (as in it is required for) https://github.com/apache/incubator-airflow/pull/3708 I cannot get beyond the submit timeout test.


How to set 3d voice in pma and change the radio sound

how can i change my voice on radio to 3D and how can i change radio speaking sound to other

All of this information can be found in the README


Apireference link bug

Dynamically created link to apireference is hardcoded to index.html which causes reloading of the page.

https://github.com/YaaS/chewie/pull/85


[DocumentIntelligence] Re-enable GetAnalyzeResultPdf once service issue is fixed

We get the following error when calling GetAnalyzeResultPdf in our unit test:
{
    "code": "NotFound",
    "message": "Analyze result does not exist."
}

This error was reproduced with the REST API, so it does not seem to be an SDK issue. The service team is currently investigating it and we must re-enable the GetAnalyzeResultPdf test once it's fixed.

Closing this as we were able to obtain a file that does not trigger this issue. The error with the first file is still being investigated by the service team, but it does not block testing in the SDK anymore.


#1851 - Enable File Upload for Public Institution User

The following tasks were completed as a part of this task:

Remove upload file button for Public Institution User.
Disable links to download/view the file for Public Institution User.
Wrote E2E test - This included writing test for inserting fake file upload data into the database and retrieving it using the API endpoint and validating the retrieved data with the inserted data.

Screenshot showing the removed upload file button and disabled links to download/view the file:

Thanks for making the changes. Added more comments.


connectTimeoutMS seemingly has no effect on migrate

Bug description
When running prisma db push command agains non-existing server, connection seems to always timeout after 30s. Docs suggest connectTimeoutMS query parameter can be used for changing this timeout, but actually, it does not seem to be the case.
How to reproduce

Copy provided schema
Ensure mongo is NOT running on provided host/port.
Run time prisma db push against the schema
Command will timeout after 30s:

Prisma schema loaded from prisma/schema.prisma
Datasource "db"
Error: MongoDB error
Server selection timeout: No available servers. Topology: { Type: Unknown, Servers: [ { Address: nothere:12345, Type: Unknown, Error: failed to lookup address information: nodename nor servname provided, or not known }, ] }
   0: migration_core::state::SchemaPush
             at migration-engine/core/src/state.rs:349

pnpm prisma db push  0.69s user 0.18s system 2% cpu 30.557 total

Expected behavior
Same timeout error, but after 1 second as specified by connection string.
Prisma information
Prisma schema:
generator client {
  provider        = "prisma-client-js"
}

datasource db {
  provider = "mongodb"
  url      = "mongodb://nothere:12345/db?connectTimeoutMS=1000"
}

model User {
  id String @id @map("_id")
}

Environment & setup

OS: macOS
Database: MongoDB
Node.js version: 16.15.1

Prisma Version
4.2.0-dev

I can reproduce: (see Executed in   31.60 secs)
time npx prisma db push
Environment variables loaded from prisma/.env
Prisma schema loaded from prisma/schema.prisma
Datasource "db"
Error: MongoDB error
Server selection timeout: No available servers. Topology: { Type: Unknown, Servers: [ { Address: nothere:12345, Type: Unknown, Error: failed to lookup address information: nodename nor servname provided, or not known }, ] }
   0: migration_core::state::SchemaPush
             at migration-engine/core/src/state.rs:349

________________________________________________________
Executed in   31.60 secs    fish           external
   usr time    1.57 secs  137.00 micros    1.57 secs
   sys time    0.35 secs  801.00 micros    0.34 secs

But... if instead I use the parameter we document for the other databases like MySQL, connect_timeout, it works like expected: (Executed in    1.78 secs)
https://www.prisma.io/docs/concepts/database-connectors/mysql
time npx prisma db push
Environment variables loaded from prisma/.env
Prisma schema loaded from prisma/schema.prisma
Datasource "db"
Error: P1013

The provided database string is invalid. An invalid argument was provided: connect_timeout is an invalid option. An option with a similar name exists: connecttimeoutms in database URL. Please refer to the documentation in https://www.prisma.io/docs/reference/database-reference/connection-urls for constructing a correct connection string. In some cases, certain characters must be escaped. Please check the string for any illegal characters.

________________________________________________________
Executed in    1.78 secs    fish           external
   usr time    1.37 secs  131.00 micros    1.37 secs
   sys time    0.39 secs  684.00 micros    0.39 secs

We document it in docs like this for a 5 sec timeout:
&connectTimeoutMS=5000

From https://www.prisma.io/docs/concepts/database-connectors/mongodb

Copying my reaction from slack: Hmm, first time I read about this param. When I grep for it in prisma-engines, I have 0 matches, so either it's implemented in the mongo driver or we documented something that doesn't exist.

They do seem to have tests about this in the driver: https://github.com/mongodb/mongo-rust-driver/search?q=connecttimeoutms
One way to try to constrain the problem would be to see if the query engine behaves the same.

@tomhoule I also get something close to 30s when doing time ts-node main.ts with a Prisma Client query.

Can reproduce in our internal dev version ``
For Client here is the script
import { PrismaClient } from '@prisma/client'

async function main() {
  const prisma = new PrismaClient()

  const data = await prisma.user.findMany()
  console.log(data)
  prisma.$disconnect()
}

main()

and output shows 30s timeout
time ts-node main.ts
/Users/j42/Repros/14607/node_modules/@prisma/client/runtime/index.js:30856
      throw new PrismaClientInitializationError(message, this.client._clientVersion);
            ^
PrismaClientInitializationError:
Invalid `prisma.user.findMany()` invocation in
/Users/j42/Repros/14607/main.ts:6:34

  3 async function main() {
  4   const prisma = new PrismaClient()
  5
→ 6   const data = await prisma.user.findMany(
Database error. error code: unknown, error message: Server selection timeout: No available servers. Topology: { Type: Unknown, Servers: [ { Address: nothere:12345, Type: Unknown, Error: failed to lookup address information: nodename nor servname provided, or not known }, ] }
    at RequestHandler.handleRequestError (/Users/j42/Repros/14607/node_modules/@prisma/client/runtime/index.js:30856:13)
    at RequestHandler.request (/Users/j42/Repros/14607/node_modules/@prisma/client/runtime/index.js:30833:12)
    at async PrismaClient._request (/Users/j42/Repros/14607/node_modules/@prisma/client/runtime/index.js:31805:16)
    at async main (/Users/j42/Repros/14607/main.ts:6:16) {
  clientVersion: '4.4.0-dev.30',
  errorCode: undefined
}
ts-node main.ts  1.35s user 0.11s system 4% cpu 30.611 total

The timeout being hit here is serverSelectionTimeoutMS, which has a default value of 30 seconds. This timeout governs how long the MongoDB driver will wait until a suitable server is discovered when attempting an operation, which seems closer to what you intended. connectTimeoutMS, on the other hand, governs only how long connection establishment takes (i.e. it specifies how long we can wait for establishment to take before we can confidently say the server is down).
What's going on here is likely that the monitor task is attempting and failing to establish a connection the non-existent server quickly and repeatedly while the operation waits for the server to be discovered, with connectTimeoutMS never actually coming into play.
To make this speedier, you can specify a lower serverSelectionTimeoutMS.

Same problem
------
 > [nextjs build 2/4] RUN dotenv -e .env.dev -- pnpm exec prisma db pull --force:
1.566 Prisma schema loaded from prisma/schema.prisma
1.567 Environment variables loaded from .env
1.571 Datasource "db": MongoDB database "my_db" at "mongodb:27017"
1.574
1.577 - Introspecting based on datasource defined in prisma/schema.prisma
31.59 ✖ Introspecting based on datasource defined in prisma/schema.prisma
31.59
31.59 Error: MongoDB error
31.59 Kind: Server selection timeout: No available servers. Topology: { Type: Unknown, Servers: [ { Address: mongodb:27017, Type: Unknown, Error: Kind: I/O error: failed to lookup address information: Name does not resolve, labels: {} } ] }, labels: {}
31.59
31.59
------

MacOSX, M1
Docker container: Node20, Alpine 3.17, Prisma 5.4.1

@dejurin The problem reported here is that a customization of the timeout is not observed, not the problem itself. You should open a new discussion and provide more information about what you are doing exactly. Thanks.

@dejurin The problem reported here is that a customization of the timeout is not observed, not the problem itself. You should open a new discussion and provide more information about what you are doing exactly. Thanks.

Thank you for the answer. I initially thought that was the problem.


Goreleaser version, date, commit should be supported

In other words when somebody types
$influxdb-router -version
the version, date, commit should be displayed. Right now the version and buildtime gets displayed but only if some one builds the binary using the make command

Fixed by https://github.com/samitpal/influxdb-router/pull/11


File upload bug

SIZE_LIMIT is 250MiB
File I'm trying to upload is 39.8MiB
But it's throwing:
thread 'actix-rt:worker:3' panicked at 'called `Result::unwrap()` on an `Err` value: CommandError(ValueTooLarge)', src/store.rs:20:42
I'm using nginx:
server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    server_name note.website.com;

    include /config/nginx/ssl.conf;

    client_max_body_size 500m;

    location / {
        include /config/nginx/proxy.conf;
           proxy_pass http://<IP_ADDRESS>:13791/;
           proxy_set_header Host $host;
           proxy_set_header X-Real-IP $remote_addr;
           proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
           proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Can confirm.

Same issue for me as well.

So I found the culprit, and it's probably a misconfigured memcached. Could you share your memcached config?

Should be memcached -m 256M -I 128M Where -I <SIZE_LIMIT> and -m <SIZE_LIMIT * 2>.
-m is the total memory and has to be at least double the -I (single item size).

@cupcakearmy Yes I did, but only -m. -I doesn't work. I think -I doesnt exist in newer versions

@IsusVonBier it exists in the latest official docker image (1.6  think)

This is a screenshot I've sent on Discord before. It's same output still

Could you check what version this is?

Sorry for late reply. memcached 1.6.14

Don't know tbh. Seems to be some weird unraid docker version then?
Could you run the command below somehow? i mean --help. The official docker image does have -I in it's latest version. It defaults to 1m so everything above that should fail on your setup.
docker run --rm memcached:alpine memcached --help

memcached 1.6.14
-p, --port=<num>          TCP port to listen on (default: 11211)
-U, --udp-port=<num>      UDP port to listen on (default: 0, off)
-s, --unix-socket=<file>  UNIX socket to listen on (disables network support)
-a, --unix-mask=<mask>    access mask for UNIX socket, in octal (default: 700)
-A, --enable-shutdown     enable ascii "shutdown" command
-l, --listen=<addr>       interface to listen on (default: INADDR_ANY)
                          if TLS/SSL is enabled, 'notls' prefix can be used to
                          disable for specific listeners (-l notls:<ip>:<port>)
-d, --daemon              run as a daemon
-r, --enable-coredumps    maximize core file limit
-u, --user=<user>         assume identity of <username> (only when run as root)
-m, --memory-limit=<num>  item memory in megabytes (default: 64)
-M, --disable-evictions   return error on memory exhausted instead of evicting
-c, --conn-limit=<num>    max simultaneous connections (default: 1024)
-k, --lock-memory         lock down all paged memory
-v, --verbose             verbose (print errors/warnings while in event loop)
-vv                       very verbose (also print client commands/responses)
-vvv                      extremely verbose (internal state transitions)
-h, --help                print this help and exit
-i, --license             print memcached and libevent license
-V, --version             print version and exit
-P, --pidfile=<file>      save PID in <file>, only used with -d option
-f, --slab-growth-factor=<num> chunk size growth factor (default: 1.25)
-n, --slab-min-size=<bytes> min space used for key+value+flags (default: 48)
-L, --enable-largepages  try to use large memory pages (if available)
-D <char>     Use <char> as the delimiter between key prefixes and IDs.
              This is used for per-prefix stats reporting. The default is
              ":" (colon). If this option is specified, stats collection
              is turned on automatically; if not, then it may be turned on
              by sending the "stats detail on" command to the server.
-t, --threads=<num>       number of threads to use (default: 4)
-R, --max-reqs-per-event  maximum number of requests per event, limits the
                          requests processed per connection to prevent
                          starvation (default: 20)
-C, --disable-cas         disable use of CAS
-b, --listen-backlog=<num> set the backlog queue limit (default: 1024)
-B, --protocol=<name>     protocol - one of ascii, binary, or auto (default: auto-negotiate)
-I, --max-item-size=<num> adjusts max item size
                          (default: 1m, min: 1k, max: 1024m)
-S, --enable-sasl         turn on Sasl authentication
-F, --disable-flush-all   disable flush_all command
-X, --disable-dumping     disable stats cachedump and lru_crawler metadump
-W  --disable-watch       disable watch commands (live logging)
-Y, --auth-file=<file>    (EXPERIMENTAL) enable ASCII protocol authentication. format:
                          user:pass\nuser2:pass2\n
-e, --memory-file=<file>  (EXPERIMENTAL) mmap a file for item memory.
                          use only in ram disks or persistent memory mounts!
                          enables restartable cache (stop with SIGUSR1)
-Z, --enable-ssl          enable TLS/SSL
-o, --extended            comma separated list of extended options
                          most options have a 'no_' prefix to disable
   - maxconns_fast:       immediately close new connections after limit (default: enabled)
   - hashpower:           an integer multiplier for how large the hash
                          table should be. normally grows at runtime. (default starts at: 0)
                          set based on "STAT hash_power_level"
   - tail_repair_time:    time in seconds for how long to wait before
                          forcefully killing LRU tail item.
                          disabled by default; very dangerous option.
   - hash_algorithm:      the hash table algorithm
                          default is murmur3 hash. options: jenkins, murmur3, xxh3
   - no_lru_crawler:      disable LRU Crawler background thread.
   - lru_crawler_sleep:   microseconds to sleep between items
                          default is 100.
   - lru_crawler_tocrawl: max items to crawl per slab per run
                          default is 0 (unlimited)
   - read_buf_mem_limit:  limit in megabytes for connection read/response buffers.
                          do not adjust unless you have high (20k+) conn. limits.
                          0 means unlimited (default: 0)
   - no_lru_maintainer:   disable new LRU system + background thread.
   - hot_lru_pct:         pct of slab memory to reserve for hot lru.
                          (requires lru_maintainer, default pct: 20)
   - warm_lru_pct:        pct of slab memory to reserve for warm lru.
                          (requires lru_maintainer, default pct: 40)
   - hot_max_factor:      items idle > cold lru age * drop from hot lru. (default: 0.20)
   - warm_max_factor:     items idle > cold lru age * this drop from warm. (default: 2.00)
   - temporary_ttl:       TTL's below get separate LRU, can't be evicted.
                          (requires lru_maintainer, default: 61)
   - idle_timeout:        timeout for idle connections. (default: 0, no timeout)
   - slab_chunk_max:      (EXPERIMENTAL) maximum slab size in kilobytes. use extreme care. (default: 512)
   - watcher_logbuf_size: size in kilobytes of per-watcher write buffer. (default: 256)
   - worker_logbuf_size:  size in kilobytes of per-worker-thread buffer
                          read by background thread, then written to watchers. (default: 64)
   - track_sizes:         enable dynamic reports for 'stats sizes' command.
   - no_hashexpand:       disables hash table expansion (dangerous)
   - modern:              enables options which will be default in future.
                          currently: nothing
   - no_modern:           uses defaults of previous major version (1.4.x)

   - External storage (ext_*) related options (see: https://memcached.org/extstore)
   - ext_path:            file to write to for external storage.
                          ie: ext_path=/mnt/d1/extstore:1G
   - ext_page_size:       size in megabytes of storage pages. (default: 64)
   - ext_wbuf_size:       size in megabytes of page write buffers. (default: 4)
   - ext_threads:         number of IO threads to run. (default: 1)
   - ext_item_size:       store items larger than this (bytes, default 512)
   - ext_item_age:        store items idle at least this long (seconds, default: no age limit)
   - ext_low_ttl:         consider TTLs lower than this specially (default: 0)
   - ext_drop_unread:     don't re-write unread values during compaction (default: disabled)
   - ext_recache_rate:    recache an item every N accesses (default: 2000)
   - ext_compact_under:   compact when fewer than this many free pages
                          (default: 1/4th of the assigned storage)
   - ext_drop_under:      drop COLD items when fewer than this many free pages
                          (default: 1/4th of the assigned storage)
   - ext_max_frag:        max page fragmentation to tolerate (default: 0.80)
   - slab_automove_freeratio: ratio of memory to hold free as buffer.
                          (see doc/storage.txt for more info, default: 0.010)
   - ssl_chain_cert:      certificate chain file in PEM format
   - ssl_key:             private key, if not part of the -ssl_chain_cert
   - ssl_keyformat:       private key format (PEM, DER or ENGINE) (default: PEM)
   - ssl_verify_mode:     peer certificate verification mode, default is 0(None).
                          valid values are 0(None), 1(Request), 2(Require)
                          or 3(Once)
   - ssl_ciphers:         specify cipher list to be used
   - ssl_ca_cert:         PEM format file of acceptable client CA's
   - ssl_wbuf_size:       size in kilobytes of per-connection SSL output buffer
                          (default: 16)
   - ssl_session_cache:   enable server-side SSL session cache, to support session
                          resumption
   - ssl_min_version:     minimum protocol version to accept (default: tlsv1.2)
                          valid values are 0(tlsv1.0), 1(tlsv1.1), 2(tlsv1.2), or 3(tlsv1.3).
-N, --napi_ids            number of napi ids. see doc/napi_ids.txt for more details

Yes, I have that output when I type memcached -h inside container, but can't configure it:

You need to set them both. with, -m being at least double what -I is :)

No, having memcached inside of the docker image is not the way to go. Thats not what containers are for :)
It looks good, only another instance running already. try another port. or shut down the currently running memecached.

That's the thing. I can't do anything. It's memcached docker image and I can only input extra parameters. Inside image I can't do anything because superuser is locked with password for some reason, and no mention of password anywhere


ReactWrapper.update() after setState() on ReactWrapper doesn't update ReactWrapper.instance().state

Current behavior
Wrapper is from shallow(<SuggestedTags />) and component is wrapper.instance()
it('should not remove tag when tagIndex is invalid', () => {
  wrapper.setState({ suggestedTags: ['Mozart'] })
  wrapper.update()
  component.handleClick(-1)
  expect(component.state.suggestedTags).toEqual(['Mozart'])
})

setState is properly rerendering but for whatever reason component which is wrapper.instance() is not having its state change.
Expected behavior
Component.state.suggestedTags is equal to ['Mozart'] because -1 is an invalid array index
API

[x] shallow
[ ] mount
[ ] render

Version

library
version

Enzyme
22.4.2

React
16.2.0

Adapter

[x] enzyme-adapter-react-16

It seems as if this works.
it('should not remove tag when tagIndex is invalid', () => {
	component.state = { suggestedTags: ['Mozart'] }
	component = wrapper.instance()
	component.handleClick(-1)
	expect(component.state.suggestedTags).toEqual(['Mozart'])
})

Even though this is my beforeEach why does the component reference not hold?
beforeEach(() => {
  component = wrapper.instance()
})

@GarrettGeorge I'm not sure the handleClick implementation but what about calling wrapper.update() after component.handleClick(-1)?

Also try ``wrapper.state()instead ofcomponent.state`

@GarrettGeorge did you figure this out?

@ljharb Closed because isn't an issue from a dead codebase from a uni project. I was just cleaning out issues I created and were no longer necessary to be open.


Create new team page

created "CreateNewTeam.vue" in /pages
added content
added to router.js
- path: /CreateTeam
- unauthenticated
imported & used <HomeLayout>
fixed styling
added flex rows/cols
fixed input box sizes

Outdated


optimize docker

Summary of Changes
Optimize docker - see https://github.com/lyft/amundsen/issues/109
Tests
Manually tested locally with docker build ...
Documentation
Should be on par with the Search service now
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes make test

Codecov Report

Merging #80 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #80   +/-   ##
======================================
  Coverage    74.8%   74.8%
======================================
  Files          19      19
  Lines        1008    1008
  Branches       88      88
======================================
  Hits          754     754
  Misses        231     231
  Partials       23      23

Continue to review full report at Codecov.

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


Add test case for bootstrapper

I added it at the beginning so you don't have to wait that much, as this test is currently failing.
Not sure if I should add the teardown or is it ok as it is?

Adding the host argument works but in @hyperswarm/dht there are multiple examples using it without host:
https://github.com/hyperswarm/dht#node--dhtbootstrapperport-options
https://github.com/hyperswarm/dht/blob/master/examples/bootstrap.js#L3
The bin.js from @hyperswarm/dht actually enforces passing --host, so the new way would it be to require the host or would it be a good assumption to default <IP_ADDRESS>?

If an example doesn’t pass host that’s a bug (we changed this to be required recently)

We need to update the hyperswarm docs to reflect this I see

@LuKks good to go?

Not sure if clientSocket has to have the host, as it didn't use the port

client needs the be passed bind(0, this._host)

Then I guess it's all good, the README might be sensitive

Nice, good job

6.3.0 since you added the feature :)


Docs: Add TOC sidebar for PDF readers

The PDF file does not have a TOC(table of content) on the side in any given PDF viewer, which makes it hard to navigate. Could you add that?

Sure, happy to have one added if that's something the chromium PDF renderer can do 👍🏻


[Nuget] Rename Ressources?

Hello,
I am using your package and I needed to create a private/internal Nuget package from it but I encounter a problem:
UCWA.Net.Ressources.dll will be never loaded/refered as Nuget treats assemblies that end with .Resources.dll as language resource assemblies.
If you think to use Nuget in the future, I think you need to rename the project or the output name.
Herve-M

I'll look into this to see if there is a good workaround as that seems like a strange limitation that Nuget is enforcing.

Yes, you can learn more in the Note section here

Would it be easiest if I go through the process of packaging it for nuget?  I have seen the process of manually including assembly files into a package.

I tried some solution for including this dll and it never run (references, files). The dll is included into the Nuget package but never referenced in the project.
I didn't use the Powershell solution, because I think it's very heavy just for this problem.
After I am really new to creating Nuget package.


ConnectButton cannot be found in module

Describe the bug
After installing the ao-wallet-kit dependency and wrapping my app with it I noticed that the ConnectBotton could not be used in my Dapp.
To Reproduce
To reproduce the issues make sure that you install ao-wallet-kit, then wrap you app with , after in your App.tsx file try to import the ConnectButton (like so import { ConnectButton } from '@project-kardeshev/ao-wallet-kit'
)

import { ConnectButton } from '@project-kardeshev/ao-wallet-kit''
See error: Module '"@project-kardeshev/ao-wallet-kit"' has no exported member 'ConnectButton'.ts(2305) import ConnectButton

Expected behavior
Once ConnectButton is imported it should be found in the module, used in your App.tsx file.
Screenshots

Environment (please complete the following information):

Environment: Node
SDK Version 1.0.2
Node Version: v22.6.0
Browser Chrome

Additional context
You're welcome

addressed in https://github.com/project-kardeshev/ao-wallet-kit/pull/24


lib/pmu_pebs: PEBS (Precise Event Based Samping) [sketch]

This does not work yet but it is an implementation of the CPU "PEBS" profiling feature. I am not sure whether it is easy or hard to complete this: the hardware is simple but can this really be used from Linux userspace?
The basic idea is to take samples for profiling directly in the CPU (with extra information available) instead of via a signal handler.
More details from the comments in pmu_pebs.lua:
PEBS is a hardware feature where the CPU collects its own samples
and writes them into memory. The samples collected by the CPU can
include interesting details such as the data address that is being
referenced when a cache miss occurs. Events can be triggered based
on a subset of performance events (cache misses, etc).

This module sets up PEBS and enables event logging into memory.

Refer to Intel's system programming manual (vol.3) for details:
http://www.intel.com/content/www/us/en/processors/architectures-software-developer-manuals.html

Encouraging: this seems to be a working example running in userspace on Linux: https://github.com/pyrovski/powertools/blob/master/msr_pebs.c

Closing PR: I am not actively developing this branch.


[Bug] [datax task] datax task error  on version 3.1.0

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

As shown in the figure above, an error occurred while calling a datax task with the parameter $[yyyy-MM-dd HH:mm:ss]

Failed to call with parameter   $[yyyy-MM-dd HH:MM:ss].
Successful call with parameter $[yyyy-MM-ddHH:MM:ss].
The guess is that the argument is passed to the datax without single quotes.
What you expected to happen
It can be called normally with $[yyyy-MM-dd HH:mm:ss]
How to reproduce
The guess is that the argument is passed to the datax without single quotes.
Test a guess.
Operating steps:

Run the command. The parameter contains Spaces. Without a single quotes . /usr/bin/python /home/tools/datax/bin/datax.py -p "-Dlast=2021-1-1 00:00:00" /home/tools/datax/bin/stream2stream.json
Error!!

Run the command without Spaces. Without a single quotes.  /usr/bin/python /home/tools/datax/bin/datax.py -p "-Dlast=2021-1-100:00:00" /home/tools/datax/bin/stream2stream.json
Success!!

Run the command. The parameter contains Spaces. With single quotes . /usr/bin/python /home/tools/datax/bin/datax.py -p "-Dlast='2021-1-1 00:00:00'" /home/tools/datax/bin/stream2stream.json
Success ！！！！

Conclusion
Compare 1 and 3 to check whether $[yyyy-MM-dd HH:mm:ss] is not supported or there is an error in my operation.
I am currently using dolphinscheduler version 3.1.0
Anything else
No response
Version
3.1.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@SbloodyS    if nobody interested  this issue, i  want to fix it

@SbloodyS if nobody interested this issue, i want to fix it

Sure.

@SbloodyS  plz close this issue


Boss mode

Problem: User needs to run a script, test or even compile the project they are working on without leaving the editor.
Solution: Boss mode.

Ctrl+B opens a shell, type command and press ENTER and it runs.
Any output is displayed just like ctrl+g help window.

For example:
^S , ^B , type "go build", ^O other.go, << type things >>, ^S, ^B, type "go build", etc

This PR may need some more work.

Looks good! Any reason why it's called Boss mode?

Will be used by bosses

and ^S ^B ^O ^S spells boss kind of

I think its ready for merge

Here are binaries with boss mode (built with make cross && make pkg)
micro-54f00cb-freebsd-amd64.zip
micro-54f00cb-freebsd-x86.zip
micro-54f00cb-linux-amd64.zip
micro-54f00cb-linux-arm.zip
micro-54f00cb-linux-x86.zip
micro-54f00cb-netbsd-amd64.zip
micro-54f00cb-netbsd-x86.zip
micro-54f00cb-openbsd-amd64.zip
micro-54f00cb-openbsd-x86.zip
micro-54f00cb-OSX-amd64.zip
micro-54f00cb-OSX-x86.zip
micro-54f00cb-WIN32.exe.zip
micro-54f00cb-WIN64.exe.zip

is there anything left to do before merge

We should probably make some changes in the future to run the shell command as a goroutine so the execution doesn't block the whole editor. Also it would be good to capture stderr as well as stdout. I'll merge this now because its a good starting point.
It would also probably be good to use a buffer instead of blocking the view (same issue as #24).

See commit 65745a6b4310f8d51910d8220c9cfa94797b8b9e for an updated version of this.


Example in Readme broken

in the example in the README.md in line StringRendererConfig.builder().useQuotes().build(); the useQuotes() method does not exist.

looks like the method was renamed to quoteIdentifiers()

there seems to be some more things broken in this example...

Closed with #73


Fixed lack of space between executable construction icon and the start of file name

Makes executable files go from looking like this:

To this:

Notice in the original image there's no spacing between the construction crane icon and the file's name.

TODO

[X] Use cargo fmt
[X] Add necessary tests
[X] Update default config/theme in README (if applicable)
[X] Update man page at lsd/doc/lsd.md (if applicable)

hi @Mersid, thanks for the PR, but this is related to the icons, can we should not fixed it like this, because when the icon sits with other icons of the same size, it will have extra space.
maybe we should try to detect the width of icons, but it would be much more complicated

Heya @zwpaper! Probably. I can't say for certain what the issue is, but if you try using unicode-width, it appears that the construction icon is marked as having a width of 1, but others like the file and folder icons have a width of 2. However, when rendering, this is obviously not the case, so thus the construction icons are rendered too close together. Just adding the space may be a viable option until we find something better. For now, having some stuff being misaligned does look quite odd.

Hi @Mersid, thanks for the info on unicode-width, it helps!
it seems reasonable for the default unicode theme to add this space, but we should calculate the width and handle the icon width dynamically.
can you create a issue for use unicode-width to handle this, and add as TODO comment here, so that we can fix this when we have unicode-width


Sm/dash-h

prevent using -h on flags to protect sf's help behavior
@W-11486833@
warns user to add a default if using min/max

QA Notes

🟡 https://github.com/salesforcecli/eslint-plugin-sf-plugin doesn't have any tags?
🟡 eslint-plugin-sf-plugin is missing from https://github.com/salesforcecli/plugin-template-sf/blob/main/package.json

Will need to be added to .eslintrc.js as well
Was throwing some other type errors until I updated other deps in my generated plugin
Audit sf plugins to make sure they all have eslint-plugin-sf-plugin configured
At the very lest, create a work item for this ^

🟢 shows error about -h 🎉
🟢 having a min OR max value suggests adding a default
🟢 adding a default appeases the linter

https://github.com/salesforcecli/plugin-template-sf/pull/148 now includes the linter rules.

moved version to 1.0 so the release isn't always halted.


chore: Fix typo in README.md

@cserino the readme is generated from https://github.com/jdxcode/rtx/blob/main/src/cli/render_help.rs, would you mind making the change there as well? Otherwise this will just get overridden the next time a commit is made

I should probably add a comment in the readme stating this

thanks for this!

also clarified the generation: https://github.com/jdxcode/rtx/commit/a4647015ed0b00826d310eb7b5458e4f5646bad4


Create a Accordion v2

One need to make this component using HTML and Tailwind CSS. I would suggest to use Tailwind Playgrounds to make things faster and quicker.
Here is a reference to the component.

After building the component please raise a PR with a screenshot of the component and add the component in path of the file.
If you need to use any icon please use it from Hero Icons
Good luck.

Hey can you assign this to me


fix: do not ignore allExcludedRuleIDs params

I believe this line has been forgotten in https://github.com/aquasecurity/tfsec/pull/1053
Resolves #1055

Thanks for this @p9f


straight-bug-report: nil-bind print level/length limits

Prevent truncation of printed lisp forms.

Yep, that one always bites me eventually too.

Same, luckily I hit it quickly when testing out the el-get integration.


Improve documentation

Reformat based on the TransactionService apigen page and add html pages with meta refresh for the examples.

Coverage remained the same at 100.0% when pulling 4a30c235efd406546ff00bdcf51fc3ec397e978c on Trimnosh:improve_documentation into f5270ce7027398181eab6fe1fdc835bd8481d7bd on wirecard:master.

Coverage remained the same at 100.0% when pulling 4a30c235efd406546ff00bdcf51fc3ec397e978c on Trimnosh:improve_documentation into f5270ce7027398181eab6fe1fdc835bd8481d7bd on wirecard:master.

Coverage remained the same at 100.0% when pulling b48fa4d6b90aaf2a9c47889a4edd8d4ca23ccf1c on Trimnosh:improve_documentation into f5270ce7027398181eab6fe1fdc835bd8481d7bd on wirecard:master.


[openal-soft:x86-windows] build failure

Host Environment

OS: Windows
Compiler: 19.26.28806 or 19.16.27040 (2017 installed, recently installed 2019)
To Reproduce
Steps to reproduce the behavior:
./vcpkg install sfml:x64-windows
or
./vcpkg upgrade --no-dry-run (with SFML x86 installed)

Failure logs
For x64-windows
Error: Building package openal-soft:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: openal-soft:x64-windows
  Vcpkg version: 2020.06.15-nohash

For vcpkg ugrade --no-dry-run
Error: Building package openal-soft:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: openal-soft:x86-windows
  Vcpkg version: 2020.06.15-nohash

Relevant sections from the log files above.
For x64-windows
Building package openal-soft[core]:x64-windows...
-- Downloading https://github.com/kcat/openal-soft/archive/a01dbeb09f0a6cdb1f2946b9fdf6c16c8b979066.tar.gz...
-- Extracting source C:/Users/TheFl/Programs/vcpkg/vcpkg/downloads/kcat-openal-soft-a01dbeb09f0a6cdb1f2946b9fdf6c16c8b979066.tar.gz
-- Applying patch dont-export-symbols-in-static-build.patch
-- Using source at C:/Users/TheFl/Programs/vcpkg/vcpkg/buildtrees/openal-soft/src/6c8b979066-d69ae4cc2c.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
    Command failed: C:/Users/TheFl/Programs/vcpkg/vcpkg/downloads/tools/cmake-3.17.2-windows/cmake-3.17.2-win32-x86/bin/cmake.exe --build . --config Debug --target install -- /p:VCPkgLocalAppDataDisabled=true /p:UseIntelMKL=No /m
    Working Directory: C:/Users/TheFl/Programs/vcpkg/vcpkg/buildtrees/openal-soft/x64-windows-dbg
    See logs for more information:
      C:\Users\TheFl\Programs\vcpkg\vcpkg\buildtrees\openal-soft\install-x64-windows-dbg-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
  scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
  ports/openal-soft/portfile.cmake:61 (vcpkg_install_cmake)
  scripts/ports.cmake:76 (include)

For vcpkg ugrade --no-dry-run
Building package openal-soft[core]:x86-windows...
-- Using cached C:/Users/TheFl/Programs/vcpkg/vcpkg/downloads/kcat-openal-soft-a01dbeb09f0a6cdb1f2946b9fdf6c16c8b979066.tar.gz
-- Cleaning sources at C:/Users/TheFl/Programs/vcpkg/vcpkg/buildtrees/openal-soft/src/6c8b979066-d69ae4cc2c.clean. Pass --editable to vcpkg to reuse sources.
-- Extracting source C:/Users/TheFl/Programs/vcpkg/vcpkg/downloads/kcat-openal-soft-a01dbeb09f0a6cdb1f2946b9fdf6c16c8b979066.tar.gz
-- Applying patch dont-export-symbols-in-static-build.patch
-- Using source at C:/Users/TheFl/Programs/vcpkg/vcpkg/buildtrees/openal-soft/src/6c8b979066-d69ae4cc2c.clean
-- Configuring x86-windows
-- Building x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
    Command failed: C:/Users/TheFl/Programs/vcpkg/vcpkg/downloads/tools/cmake-3.17.2-windows/cmake-3.17.2-win32-x86/bin/cmake.exe --build . --config Debug --target install -- /p:VCPkgLocalAppDataDisabled=true /p:UseIntelMKL=No /m
    Working Directory: C:/Users/TheFl/Programs/vcpkg/vcpkg/buildtrees/openal-soft/x86-windows-dbg
    See logs for more information:
      C:\Users\TheFl\Programs\vcpkg\vcpkg\buildtrees\openal-soft\install-x86-windows-dbg-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
  scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
  ports/openal-soft/portfile.cmake:61 (vcpkg_install_cmake)
  scripts/ports.cmake:76 (include)

Did a quick google and noticed this similar issue (failed at the same line in the same script) I did not uninstall vs2017 (though I did install 2019) however restarting did not work.

I just took a look at the logs, here I can see that there seems to be some sort of issue regarding a windows kit being used, the first error being:
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapifromapp.h(32,1): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int (compiling source file ... \vcpkg\buildtrees\openal-soft\src\6c8b979066-d69ae4cc2c.clean\al\error.cpp) [... \vcpkg\buildtrees\openal-soft\x64-windows-dbg\OpenAL.vcxproj]

I see a few "redefinition" errors mixed in there somewhere:
4>C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um\fileapifromapp.h(40,1): error C2086: 'int WINSTORAGEAPI': redefinition (compiling source file C:\Users\TheFl\Programs\vcpkg\vcpkg\buildtrees\openal-soft\src\6c8b979066-d69ae4cc2c.clean\al\error.cpp) [C:\Users\TheFl\Programs\vcpkg\vcpkg\buildtrees\openal-soft\x64-windows-dbg\OpenAL.vcxproj]

Could there be some issue with double consumption of the dependancy?
install-x86-windows-dbg-out.log
install-x64-windows-dbg-out.log

Thanks for posting this issue. Closed as duplicate of #10825.

@LilyWangL Thank you, is there an official fix/resolution?

@LilyWangL Thank you, is there an official fix/resolution?

Can you try #12318 changes work for you?

Attempted vcpkg.exe install --head openal-soft:x64-windows no go :(

Waiting for #12318 merged, you can try to install openal-soft:x64-windows again.

Same issue


backports.pbkdf2?

any particular reason for requiring backports.pbkdf2 to provide pbkdf2_hmac rather than using hashlib.pbkdf2_hmac? Is there a subtle compatibility issue or something?

not that i think! this was introduced in a PR. I'll get on removing this dependency later :)

Oh! I see @oliviacrain has a fork with this implemented. I'll wait for a PR to come in from her 😄
https://github.com/oliviacrain/Cohost.py/tree/oliviacrain/fix/remove-backport-pbkdf2


cmd/go: improper validation of cgo flags can lead to remote code execution at build time

The go command may execute arbitrary code at build time when cgo is in use. This may occur when running go get on a malicious package, or any other command that builds untrusted code.
This can be caused by a malicious gcc flags specified via a #cgo directive.
Thanks to Imre Rad for reporting this issue.
This issue is CVE-2020-28367.

Fixed by CL 269658.

Fixed by CL 269658.


[FLINK-17646][python] Reduce the package size of PyFlink.

What is the purpose of the change
This pull request reduces the the python package size of PyFlink.
Brief change log

Remove the jars in the deps/opt folder of the PyFlink python package file except flink-python.jar and flink-sql-client.jar.
Regenerate the licenses directory and NOTICE file of the PyFlink python package file.

Verifying this change
This change added tests and can be verified as follows:

run mvn clean install -DskipTests on the flink source root directory.
run cd flink-python;python setup.py sdist to pack a python package.
check the package size in flink-python/dist, make sure it is less than 300MB.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@dianfu Thanks for your review! I have addressed your comments.

The test failure is not related to PR. Merging...


Gets blockchain storage info.

Gets blockchain storage info.

Pull Request Test Coverage Report for Build 62

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

Totals

Change from base Build 60:
0.0%

Covered Lines:
51

Relevant Lines:
59

💛  - Coveralls

Pull Request Test Coverage Report for Build 62

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

Totals

Change from base Build 60:
0.0%

Covered Lines:
51

Relevant Lines:
59

💛  - Coveralls

Hi @NemTechCN , the code looks nice! To follow the API approach, I would prefer if you could move the command either to nem2-cli diagnostic or nem2-cli node instead of nem2-cli blockchain. Thanks!

@NemTechCN This PR is almost valid, do you want to continue it? Thanks!

@evias I have fixed the command and did some reorganization with the latest. Please, check the PR is okay,  and I proceed to merge it.


set the return type of the raster agg

[ ] I added an entry to CHANGELOG.md if knowledge of this change could be valuable to users.

Here is a brief summary of what I did:

 ResultDescriptor des TemporalAggregationOperator beachtet geänderten Rückgabetyp nicht


Issue#28 - Changed edib version to match docker edib tool commit.

Breaking Change
Needs Distillery 1.0+ to work
Notes
This PR needs to be approved after the docker image edib/edib-tool:1.6.0 has been published
https://github.com/edib-tool/docker-edib-tool/pull/10
*I guessed at the versioning since the above PR has a breaking change. Let me know if this is wrong! :+1: *

This PR depends on @luckynum7 PR https://github.com/edib-tool/docker-edib-tool/pull/9
I closed the other PR that I created erroneously

I also added a .gitattributes file that will enforce line endings. Please let me know if this needs to be removed :)

I also added a .gitattributes file that will enforce line endings. Please let me know if this needs to be removed :)

Since the proposed changes are basically the default for Linux, MacOS and other unixoid systems I don't see anything harmful in adding this file if it makes your life easier. :man_shrugging:

Could you also rebase onto current master? I have updated the codebase a bit, so I'd like to make sure there are no conflicts. (edib version in master changed)

Conflicts resolved.

Thanks for updating the branch! :+1:


added —-build option to artifacts download

Added option to specify the build id for artifact downloads.

Awesome, thanks @mgoodings!

Any chance on getting this merged?


Fixed InputRule deletes the next unrelated char that should not be deleted.

Can I reproduce the bug somehow? (before your fix)


CSVReaderHeaderAware readmap issue

The CSVReaderHeaderAware reader.readmap() function when reading a CSV file seems to have issues when the header names have either longer text or something related to it.
Here are the details.
Below is the CSV reader code snippet I am using
String file_path = <local csv path >;
String csv_path = file_path_train.replace("\\", "/");
Map<String, FieldProcessor> regexMappingProcessors = new HashMap<>();
var reader = new CSVReaderHeaderAware(new FileReader(csv_path));
var record = reader.readMap();

For the HDBSCAN model training, I used two csv files . Both the files are attached herewith.
When I read the 1st CSV file "synthetic_data_training.csv" that has 113 columns, using the above cited code info, I could read the file and build the hdbscan model without any issues.
Then when I used another training dataset attached herewith "synthetic_data_training_resptime_70_30_derived.csv"  which has 54 columns with all data entries, I got the following error. As you can see , all the header columns are present in the file. I suspect the reader perhaps did not consider some of the header text and therefore reports that the expected is 48 , but in actual the column size in dataset is 54 ?.
Could this be due to any considerations in the pattern or length of the header text?
Exception in thread "main" java.io.IOException: Error on record number 2: The number of data elements is not the same as the number of header elements. Expected 48, found 54.
	at com.opencsv.CSVReaderHeaderAware.readMap(CSVReaderHeaderAware.java:117)
	at org.tribuo.clustering.hdbscan.NewTest.main(NewTest.java:345)

The issue is pointing to var record = reader.readMap();  line
[synthetic_data_training.csv
synthetic_data_training_resptime_70_30_derived.csv
](https://github.com/oracle/tribuo/files/9301349/synthetic_data_training.csv)
Thanks in advance.

@Craigacp  Got it. I realized that CSVReaderHeaderAware is from OpenCSV. The reason I had used it if you see the code block below is to read all the headers by looping the readMap.
(i.e. instead of manually inserting all the columns like
regexMappingProcessors.put("Feature1", new DoubleFieldProcessor("Feature1"));)
After this, I used the CSVDataSource.
Now, Instead of the above, How can I read the CSV file - i.e.  all its headers using a Tribuo class and then iteratively add it to the regexMappingProcessors.put() ?
your guidance with an example / snippet will help.
String csv_path = <local file path>;
Map<String, FieldProcessor> regexMappingProcessors = new HashMap<>();
reader = new CSVReaderHeaderAware(new FileReader(csv_path));
Map<String, String> record = reader.readMap();
for (Map.Entry<String, String> e : record.entrySet())
	        	regexMappingProcessors.put(e.getKey().toString(), new DoubleFieldProcessor(e.getKey().toString()));

RowProcessor<ClusterID> rowProcessor = new RowProcessor<>(new EmptyResponseProcessor<>(new ClusteringFactory()), regexMappingProcessors);
CSVDataSource<ClusterID> csvSource = new CSVDataSource<>(Paths.get(csv_path), rowProcessor, false);
Dataset<ClusterID> dataset = new MutableDataset<>(csvSource);

Thank you.

@Craigacp  There seems to be a problem when I tried the following
I created a  method call getHeaders that will read a CSV file and output the list of the  csv headers (features..) . Then I am looping through this list and add it to the regexMappingProcessors as below.
The trainingHeaderSize list size output is correct. which is 54 (column names / features ) from the attached CSV file.
But when I check the features from the dataset created using the CSVDataSource as below using dataset.getFeatureMap().size() , it  is showing only 48 instead of 54?
List<String> headerItems = test.getHeaders(training_file_path, training_file_name);
		int trainingHeaderSize = headerItems.size();
		System.out.println("trainingHeaderSize: " + trainingHeaderSize);
		for (int h=0; h<trainingHeaderSize; h++) {

			String hLabel = headerItems.get(h);
			regexMappingProcessors.put(hLabel, new DoubleFieldProcessor(hLabel));
		}

		System.out.println("Loading Training data ........");
   	   	RowProcessor<ClusterID> rowProcessor = new RowProcessor<>(new EmptyResponseProcessor<>(new ClusteringFactory()), regexMappingProcessors);
		CSVDataSource<ClusterID> csvSource = new CSVDataSource<>(Paths.get(csv_path), rowProcessor, false);
		// DATASET from CSV
		Dataset<ClusterID> dataset = new MutableDataset<>(csvSource);
		System.out.println("Train dataset info start........");

Ah ok. The map named regexMappingProcessors is being fed into the RowProcessor where it's expecting a map with concrete column names. To use the regex expansion you need to use the constructor mentioned here - https://github.com/oracle/tribuo/issues/251#issuecomment-1185129446, and then you should be able to build a map like this:
Map<String, FieldProcessor> regexMappingProcessors = Collections.singletonMap("*", new DoubleFieldProcessor("*"));

Given that's the second issue this month with confusion around the use of regexMappingProcessors we'll bump adding the builder to RowProcessor up the list and make sure it gets in for the next release, which should hopefully make it a bit clearer what's going on.

Got it. Thanks @Craigacp


's shadow disappear when it's ancestor  has onLayout in Android

Description
<Button>'s shadow disappear when it's ancestor <View> has onLayout in Android.
But If the <View> is the most outside element of this component, the <Buttonn>'s shadow will appear again.
Reproduction Steps and Sample Code
import React, { Component } from 'react'
import { View, Button } from 'react-native'

// shadow disappear
class Example1 extends Component {
    render() {
        return <View style={{padding: 50}}>
            <View onLayout={() => {}}>
                <Button title="Example1" onPress={() => {}} />
            </View>
        </View>
    }
}

// shadow disappear too
class Example2 extends Component {
    render() {
        return <View style={{padding: 50}}>
            <View onLayout={() => {}}>
                <View><View>
                    <Button title="Example2" onPress={() => {}} />
                </View></View>
            </View>
        </View>
    }
}

// shadow *appear*
class Example3 extends Component {
    render() {
        return <View style={{padding: 50}} onLayout={() => {}}>
            <View>
                <View><View>
                    <Button title="Example3" onPress={() => {}} />
                </View></View>
            </View>
        </View>
    }
}

Additional Information

React Native version: 0.44.2
Platform: Android
Development Operating System: macOS

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

Hi - I think this is worth re-opening. onLayout seems to ignore shadowRadius props of the view on iOS - such that if the content of a view changes and that view has a shadow, onLayout returns a nativeEvent where the height value does not include the aforementioned shadow


App Not available

as per step 3 In the SharePoint Store, search for Office 365 Project Portfolio Dashboard.
app is not available please help in getting that

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

ID: ecd3a37e-4d30-4f74-4b9a-1e1ed95b0a0b
Version Independent ID: 6e104a98-accf-f86e-54e1-77f224e07af3
Content: Configure Office 365 Project Portfolio Dashboard
Content Source: ProjectOnline/configure-office-365-project-portfolio-dashboard.md
Service: o365-administration
GitHub Login: @efrene
Microsoft Alias: efrene

@Online24x7 Thank you for this feedback
I am not sure why the Office 365 Project Portfolio Dashboard isn't in the SharePoint Store. I want to make sure this is documented and addressed promptly. Support can handle this to resolution and in a quick manner.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.

The Office 365 Project Portfolio Dashboard is still not available in the SharePoint store


Difficult to open go4cache info when using OSM

When I try to click on a go4cache icon (red dot) on the live-map while using OSM it is very difficult to get the info-window open.
Doing the same while Google Maps is active is much easier (as it should be).
It is like the accepted radius for tapping on the screen is much lower when OSM is displayed.
Happens with OSM:Mapnik and OSM:Offline. Works OK with Google:Map. Others not tested.
Regards,
Lineflyer

I retested this one today, it seems to be gone.
The respsonse is OK now with every map. I wil close this one for now.


Add ClouDNS DNS-01 support

Add support for cloudns DNS-01 challenge
They have an API and the acme.sh script already has implemented cloudns, so I don't think it would be that much work to implement it in cert-manager
An alternative could be te implement acme.sh into cert-manager, but this would require something like environmental variables/secrets to be added to an cluster-issuer. So the API keys etc. could be passed through.
/kind feature

At this point, due to our inability to test all DNS01 providers that we currently have in our codebase, we are requiring all new DNS01 implementations to be implemented as external DNS01 webhooks, following the example here: https://github.com/jetstack/cert-manager-webhook-example/
We are currently not accepting new DNS01 providers into the core codebase as we don't have a good way to test them reliably - we've not determined an exact process for 'upstreaming' these DNS01 providers into the core codebase yet, but if a provider demonstrates it passes tests, and we are able to find a way to run these tests in our own environment, we'd definitely like to explore defining this process 😄
Hope that makes sense, and hopefully it'll allow for you to develop on your own provider with more confidence (as you can actually configure some end-to-end tests!)


Don't enable OCSP stapling if not available

On BoringSSL OCSP stapling is not available, however, it can still be
added to the configuration via s2n_config_set_check_stapled_ocsp_response.
The docs suggest that if this feature cannot be enabled, the return code
should be -1 instead.
Signed-off-by: Petre Eftime<EMAIL_ADDRESS>Description
Fixes documentation mismatch here: https://github.com/awslabs/s2n/blob/main/docs/USAGE-GUIDE.md#s2n_config_set_check_stapled_ocsp_response.
Testing:
Local build + unit tests.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2253 into main will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2253      +/-   ##
==========================================
- Coverage   80.73%   80.72%   -0.02%
==========================================
  Files         265      265
  Lines       17831    17832       +1
==========================================
- Hits        14395    14394       -1
- Misses       3436     3438       +2

I added a test that checks the new behavior of the function, but let me know if you had something else in mind.


Memory leak when redrawing curves.

There is a visible memory leak anytime a curve is redrawn

Issue resolved, was caused by a virtual subclass not having a virtual destructor


Intermittent C# gRPC client issue: (Status(StatusCode=Unknown, Detail="Stream removed"))

What version of gRPC and what language are you using?
C# with gRPC 2.28.1 and Protobuf 3.11.4 (gRPC server is Python at 1.31.0)
What operating system (Linux, Windows,...) and version?
Server Linux 3.10.0-1160.6.1.el7.x86_64
Client Window 10
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.8.3
What did you do?
Made unary stream call to a Python gRPC server
What did you expect to see?
Expect to see stream of protobuf message
What did you see instead?
Exception at the client end

System.AggregateException: One or more errors occurred. (Status(StatusCode=Unknown, Detail="Stream removed")) ---> Grpc.Core.RpcException: Status(StatusCode=Unknown, Detail="Stream removed")
at Grpc.Core.Internal.ClientResponseStream '2.MoveNext(CancellationToken token) in T:\src\github\grpc\src\csharp\Grpc.Core\Internal\ClientResponseStream.cs:line 60`

We enabled the GRPC_TRACE, GRPC_VERBOSITY and got the following exception

D1221 23:12:30.290411779    5758 call.cc:739]                set_final_status SVR
D1221 23:12:30.290500880    5758 call.cc:740]
{
"created"<EMAIL_ADDRESS>"description": "Error received from peer ipv4:<IP_ADDRESS>:65415",
"file": "src/core/lib/surface/call.cc",
"file_line": 1062,
"grpc_message": "Connection timed out",
"grpc_status": 14
}`

Anything else we should know about your project / environment?
I am unable to  reproduce this issue if both server and client are running in same server or same region.
This problem occurs always when Service running in U.S server and Client from India trying to connect. We don't see this problem often for non-streaming api calls

You seem to be running into connection timeout issues. gRPC has a default initial connection timeout of 20seconds which can be increased if needed. More information on the connection algorithm can be found here https://grpc.github.io/grpc/core/md_doc_connection-backoff.html
These are the corresponding channel args to be set.
/** The minimum time between subsequent connection attempts, in ms */
#define GRPC_ARG_MIN_RECONNECT_BACKOFF_MS "grpc.min_reconnect_backoff_ms"
/** The maximum time between subsequent connection attempts, in ms */
#define GRPC_ARG_MAX_RECONNECT_BACKOFF_MS "grpc.max_reconnect_backoff_ms"
/** The time between the first and second connection attempts, in ms */
#define GRPC_ARG_INITIAL_RECONNECT_BACKOFF_MS \
  "grpc.initial_reconnect_backoff_ms"

I would normally assume that 20 seconds is enough for connections to be established but there are scenarios where a different initial timeout value might be better. I hope this helps.


wave viewer - wait for all ports in sync mode

When in synchronous alignment mode, the wave plotter should ensure that the entire display is only refreshed after all N channels have arrived. Otherwise we are not necessarily looking at curves from the same time.

moved to plotters toolkit: https://github.com/pothosware/pothos-plotters/issues/2


Auto-routing through Consul [Question]

I'm using Zuul gateway and I'd like to migrate to this solution but I'd need to know if it's possible that SCG can auto-routing services registered (without edit any configuration file) in a Consul service discovery as Zuul does.

If I understand your question correctly, the answer is yes
http://cloud.spring.io/spring-cloud-static/Finchley.RELEASE/single/spring-cloud.html#_discoveryclient_route_definition_locator

Thanks for your response @ryanjbaxter. Given that chapter of the documentation, I supposed the same and I've made a project as POC. When I run it, SCG doesn't declare any route for my services which are registered in Consul. I'm using "Finchley" version of Spring Cloud. I attach my pom.xml, application.yml and bootstrap.yml, maybe I made a mistake.
pom.xml
<parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.0.3.RELEASE</version>
</parent>
<properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
        <maven.compiler.source>1.8</maven.compiler.source>
        <maven.compiler.target>1.8</maven.compiler.target>
        <java.version>1.8</java.version>
        <spring-cloud.version>Finchley.RELEASE</spring-cloud.version>
</properties>
<dependencies>
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-gateway</artifactId>
        </dependency>

        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-test</artifactId>
            <scope>test</scope>
        </dependency>

        <!-- Consul -->
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-consul-all</artifactId>
        </dependency>
</dependencies>

<dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>org.springframework.cloud</groupId>
                <artifactId>spring-cloud-dependencies</artifactId>
                <version>${spring-cloud.version}</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
</dependencyManagement>

application.yml
server:
  port: 8080

logging:
  level:
    org: DEBUG
    com.epgpay: INFO, ERROR

spring:
  cloud:
    gateway:
      discovery:
        locator:
          enabled: true

bootstrap.yml
spring:
  application:
    name: spring-cloud-gateway
  cloud:
    consul:
      enabled: true
      host: localhost
      port: 8500
      discovery:
        register: false
        enabled: true

@spencergibb is defining a DiscoveryClientRouteDefinitionLocator bean necessary?  If so we should add it to the documentation I think.

No it isn't

Hi @ryanjbaxter and @spencergibb, running the project in debug mode I could see the following:
GatewayDiscoveryClientAutoConfiguration#discoveryClientRouteDefinitionLocator:
      Did not match:
         - @ConditionalOnBean (types: org.springframework.cloud.client.discovery.DiscoveryClient; SearchStrategy: all) did not find any beans of type org.springframework.cloud.client.discovery.DiscoveryClient (OnBeanCondition)
      Matched:
         - @ConditionalOnProperty (spring.cloud.gateway.discovery.locator.enabled) matched (OnPropertyCondition)

GatewayDiscoveryClientAutoConfiguration class is the unique point where DiscoveryClientRouteDefinitionLocator is referenced and as you can see at the previous log, the bean is not created due a validation error. Searching through the web I could see other developer with the same issue as me.

This works fine for me without adding the bean to my application using Finchley.BUILD-SNAPSHOT.
By default routes are added with the service id in uppercase, so the service id in the path needs to be uppercase.  You can change this by setting spring.cloud.gateway.discovery.locator.lower-case-service-id to false.

Only eureka upper cases the service ids

@ryanjbaxter , have you tested with Eureka or Consul? I've re-created the project following this tutorial from spring's youtube channel: tutorial, but the issue still appearing.
I've created a github's repository where you can check my project's configuration if you want.
Thanks for the support :+1:

Yes, for sure: repository (sorry, I forget the link)

I think the problem is that GatewayDiscoveryClientAutoConfiguration is being configured before CompositeDiscoveryClientAutoConfiguration, therefore the DiscoveryClient bean is not present.  It seems to be fine when using Eureka but with Consul the ordering is different.

That is my suspicion. For curiosity, I'll check the difference between eureka and consul clients :nerd_face:  Thanks for your support!