feat(package): add querystring

the querystring module was missing

Merci,  but these dependences are not declared because they are shipped as part of Node.js.
The fs package you referenced is fact just a placeholder so people don't maliciously register the fs module as a replacement for the "real" built-in fs module.
References:

https://nodejs.org/api/fs.html
https://nodejs.org/api/querystring.html


Fixing bug described in #9206

As per Taylor's comments on #9217

Please squash to one commit and send to the correct branhc.


feat(api) add /services/{service}/plugins and /routes/{route}/plugins

Summary
Adds two new Admin API endpoints:

/services/{service}/plugins
/routes/{route}/plugins

These endpoints support GET, PUT, and POST just like /apis/{api}/plugins does.
It is under new-model (routes and services) but uses old model on /plugins because plugins are still in old model. It doesn't add /routes/{route}/plugins/{id} (unlike /apis({api}/plugins/{id} because you can always just use /plugins/{id}.

I'm not sure at which point we started separating the tests for a given feature into a separate commit, but that is most certainly not desired. (Currently working on improving the PR, no worries)

Trying something new here: I added a commit with some proposed modifications :)
I suggest we squash all 3 commits together when merging this (tests written in parallel with a feature definitely belong to the same feat commit).

Yes, I would have exposed if this was going to stay.


running Dexie in a chrome DevTools snippet: error

Hi,
Firstly, Dexie is very valuable.The api is superb and I'm using it in production. Awesome work :pray:
As I haven't found a better way to modify indexedDB DB directly, I'm trying to run Dexie inside a Chrome DevTools snippet. Here's the snippet:
import('https://unpkg.com/dexie@latest/dist/dexie.js').then(m => console.log(m));

And here's the error received in the console:
dexie.js:17 Uncaught (in promise) TypeError: Cannot set property 'Dexie' of undefined
    at dexie.js:17
    at dexie.js:18
(anonymous) @ dexie.js:17
(anonymous) @ dexie.js:18
dexie.js:18 Uncaught (in promise) TypeError: Cannot set property 'Dexie' of undefined TypeError: Cannot set property 'Dexie' of undefined
    at dexie.js:17
    at dexie.js:18

Is there a way to properly import Dexie from CDN and run it in the snippet?
Thanks!

Try import('https://unpkg.com/dexie@next/dist/dexie.mjs').then(m => console.log(m))


Console history and multiline submissions do not work.

This is a regression.

Closed via https://github.com/jupyter/jupyterlab/pull/119


Enum serializer

The serializer Enum attribute to string doesn't work, any options or configuration are necessary?
    [JsonConverter(typeof(StringEnumConverter))]

Closing this, as not relevant, please reopen if needed


fix(motor control): Use FreeRTOS delay instead of hardware delay

We recently started adding a delay between engaging a head motor and starting the execution of a move. We were using a HAL delay to do this, and it turns out that this blocks FreeRTOS's task handling, and in certain edge cases cause a firmware crash.
We should instead use FreeRTOS's built-in vTaskDelay

Whoa, nice find.
How did this cause a firmware crash? Some kind of watchdog timeout?

Whoa, nice find.
How did this cause a firmware crash? Some kind of watchdog timeout?

It seems like a memory fault after the delay blocked the motor interrupt a bunch of times.


CFP: CiliumNetworkPolicy toFQDNs.matchPattern should allow wildcarding of the . character to allow multiple levels of subdomains

CiliumNetworkPolicy toFQDNs.matchPattern should allow wildcarding of the . character to allow multiple levels of subdomains
2022-11-16: Updated issue description after discussions in comments. See the collapsed section in the end for original post
Is your feature request related to a problem?
The current behavior of wildcards (*) in toFQDNs.matchPattern has the limitation that it does not include dots. In order to allow e.g. example.com and all of its subdomains (in multiple "levels"), e.g. australia-east.example.com, api.australia-east.example.com, auth.api.australia-east.example.com, I need to add four separate rules (docs ref);.
  - toFQDNs:
    - matchPattern: "example.com"
    - matchPattern: "*.example.com"
    - matchPattern: "*.*.example.com"
    - matchPattern: "*.*.*.example.com"

Describe the feature you'd like
It should be possible to wildcard multiple level of subdomains for a given domain, i.e. the . character should be possible to wildcard.
Describe your proposed solution
Introduce the option to use double asterixes ** as a more "aggressive" wildcard in addition to the existing single asterix *.
Current behavior

* within a domain allows 0 or more valid DNS characters, except for the . separator.

*.cilium.io will match sub.cilium.io but not sub.sub.cilium.io or  cilium.io.
part*ial.com will match partial.com and part-extra-ial.com.
*cilium.io will match anothercilium.io but not sub.anothercilium.io or sub.cilium.com.

Suggested additional behavior

** within a domain allows 0 or more valid DNS characters, including the . separator. (New)

**.cilium.io will match sub.cilium.io and sub.sub.cilium.io, but not cilium.io.
part**ial.com will match partial.com and part-extra-ial.com.
**cilium.io will match anothercilium.io and sub.anothercilium.io and sub.cilium.com.

This way, to address the problem scenario, I could reduce my toFQDNs items into one matchName (or matchPattern) to allow the exact domain, and another matchPattern to allow all levels of subdomains to that domain:
  - toFQDNs:
    - matchName: "example.com"
    - matchPattern: "**.example.com"

Original issue description
Using * in CiliumNetworkPolicy toFQDNs.matchPattern should include all levels of subdomains
Is your feature request related to a problem?
The current behavior of wildcards (*) in toFQDNs.matchPattern has the limitation that it does not include dots. In order to allow e.g. example.com and all of its subdomains (in multiple "levels"), e.g. australia-east.example.com, api.australia-east.example.com, auth.api.australia-east.example.com, I need to add four separate rules:
  - toFQDNs:
    - matchPattern: "example.com"
    - matchPattern: "*.example.com"
    - matchPattern: "*.*.example.com"
    - matchPattern: "*.*.*.example.com"

From the documentation (https://docs.cilium.io/en/v1.12/policy/language/#dns-based):

* within a domain allows 0 or more valid DNS characters, except for the . separator. *.cilium.io will match sub.cilium.io but not cilium.io.

Describe the feature you'd like
* in toFQDNs.matchPattern should match zero to unlimited characters like regex does with (.*). So that I only need two rules; one that matches the domain, and one that matches any level of subdomain to that domain:
  - toFQDNs:
    - matchPattern: "example.com"
    - matchPattern: "*.example.com"

A couple of notes:

During an early version of the design, this was possible, but then the original author decided it may be safer to avoid this. I vaguely recall some concern that wide-scoped rules could encourage administrators to write unsafe rules, for example by matching all subdomains it could make subdomain hijacking easier. At a glance I couldn't find the original rationale, but you may be able to find it by digging through old PRs related to the toFQDNs policies.
Many users have written their rules against the current semantics, so there is no way that we could change the current matchPattern statements to reinterpret the . or * characters. If this is supported, it would need to be a new field.

Thanks for the notes Joe.

Indeed it is probably safer considering a subdomain takeover scenario, but for administrators who prefer configuration simplicity over maximal safety, it can be considered somewhat limiting. It could be argued that this decision between safety and simplicity should be in the hands of the administrator and not limited by the product itself. Looking at how other types of "firewalls", e.g. Azure Firewall have chosen to do it, * matches any character, allowing for wildcarding multiple levels of subdomains.

Good point regarding the breaking change. Perhaps rather than introducing a completely new field, a less intrusive option could be to introduce another allowed "type" of wildcard character. For example double asterixes:

** matches any character (including the .). Allows wildcarding of multiple levels of subdomains.
* matches any character except . (the way it is now). Allows wildcarding of a single subdomain.

Broadly your arguments make sense to me, this seems like a quality-of-life improvement suggestion for users who are already accepting of the risk of wildcarded FQDN rules. I like the ** suggestion since it is unlikely anyone is specifying this in their rules today, and yet it would provide a more explicit wildcarding option to cover this slightly different use case vs. the current semantics. It's also nice that it shouldn't require a new field like I had previously assumed.

Thank you for the feedback @joestringer. I updated the issue to reflect our discussions.

Can this be reopened @aanm @joestringer? It's a good feature 😃

IMO ** for matching multiple subdomains feels useful, but allowing it to match partial subdomain names seems very dangerous, especially if applied on the top-level domain or the next level down, as domain ownership seems murky. On the other hand, we already allow for *.com for example, so **pple.com is no less safe than that. But the fact that this matches www.bad-apple.com seems troubling.
Would limiting this to just multiple levels of subdomains, as indicated in the CFP name be acceptable?

I think it's a reasonable limitation to require that ** follows with . to indicate that it is only matching subdomains and not performing partial domain matches.

We have been testing the fix described at https://github.com/cilium/cilium/issues/22081#issuecomment-1767811688 for a week now without any issues. Our only concern is an increased memory usage for the CNI due to more IPs being held in memory due to the larger lookups.
Any chance this could get into a proper release?

In reference to #35819, I will add the following

I am also missing a top-level operator, that allows hostnames only, e.g. server1, but doesn't allow server1.com. Using a matchPattern * would have been correct, except that this was programmed as a special case that works as ** would.
Changing this would unfortunately break existing policies.

For this reason, I agree with @joestringer  that perhaps it is better to use a new field, and instead of the special case use of matchPattern: * use matchPattern2: ** for the same behavior (wildcard including .), such that * is strictly a wildcard excluding . for consistency, i.e. matchPattern2: * would match example but not example.com.

I don't think a new field should be necessary if the operator is different, such as **.

@joestringer The problem is the * operator is identical to ** for matchPattern: *, which is logically inconsistent.
And it prevents you from matching against a name without ., e.g. example but not example.com.

Hmm. I agree that it's inconsistent. This is the first I've seen anyone bring up the concern about matching a name without a .. However, even if we introduce a brand new field, we cannot change the behavior of matchPattern: * as that could break existing network policies. So the end result whether we use a new field or not is that it would not be possible to satisfy this specific use case.

It would be possible to keep the current functionality in matchPattern, and new functionality in matchPattern2.
If you're already using regex for this, you could also provide an escape hatch as regexPattern.

I think I'm still missing what functionality we would lose if the ** syntax is added to the existing field. There is currently no ability to match on only a single-segment domain example right? Because * by itself acts as an arbitrary wildcard including the period character.

Correct. Two options:

adding ** to matchPattern

simple

* is inconsistent in that it behaves like ** for matchPattern: *.
it does not allow matching single-level domains like example

using matchPattern2

doesn't affect existing code
clearly communicates a different behavior of the pattern matching
matchPattern2: * will match only single-level domains like example

may require duplicate code
slightly ugly

same as 1) , but also adding regexPattern

allows any custom pattern, e.g. single-level domains [a-zA-Z0-9]+.
regexPattern can be disallowed by strict cluster admins (e.g. using Kyverno) for concerns about regex engine vulnerabilities

Maybe option 3 is the best?

+1 for option 3.

I would encourage option (1). There's a natural expansion of the existing functionality and the "confusing" part is already part of the API.
Option (2) seems like it's introducing a new field without express need for the new field, as I'm not seeing strong signal from users that supporting single-level domains is critical at this time. Exposing some version of regex as per (3) seems error-prone, we deliberately avoided exposing a regex-like interface in the API to keep the API surface simple, including to reduce the concerns around regex misuse.

Any progress here? It’s preventing us from using cilium network policies over a traditional firewall in some scenarios.


Please enable TCP: BBR congestion control algorithm in new kernel

tcp: BBR congestion control algorithm
Please enable it as it can increase the network speed much.
About BBR :
http://queue.acm.org/detail.cfm?id=3022184
https://lwn.net/Articles/701177/
from the kernel patch description:
This patch series implements a new TCP congestion control algorithm:
BBR (Bottleneck Bandwidth and RTT). A paper with a detailed
description of BBR will be published in ACM Queue, September-October
2016, as "BBR: Congestion-Based Congestion Control". BBR is widely
deployed in production at Google.

Thats the reason why i needed to upgrade the kernel as well. You suceeded in upgrading the kernel to 4.16. Did you tried this : https://www.techrepublic.com/article/how-to-enable-tcp-bbr-to-improve-network-speed-on-linux/ ?

In other words, BBR is not in Kernel? Does this link helps you : https://www.cyberciti.biz/cloud-computing/increase-your-linux-server-internet-speed-with-tcp-bbr-congestion-control/

BBR is not in the latest kernel available which is version 4.16.
However you bring a very interesting point with the Arabian kernel, I will try to install it and see if BBR works but so far every time I try to upgrade the kernel with Armbian it fails and I can't boot the rock64...
Obviously we could just compile the kernel ourselves and add BBR in it but I am not advanced enough to do this..
Will let you know if I find anything new!

+1

I just saw a 4.17 kernel version? Did someone tried this to see if it's enabled? I will try this tonight

+1

Somebody knows why this isn't included? It is in mainline Linux, so it was removed for this kernel? Is it not compatible with the rock64?
Some help to understand the situation would be nice :)


Flashing custom partition table & bootloader

The crate has a very nice support for describing custom partition tables. It is just that this functionality is not exposed yet to the outside world, and currently, a partition table with a single factory app is always flashed.
We need a command-line syntax in the form of an option to read a partition table description from a file, so that one can flash their own partition tables. Ideally, the partition table file format should follow the one used in the ESP-IDF CSV format, so that we do not bring more confusion.
Regarding flashing a custom bootloader - this is less of a priority, but same here - we just need a command line option, where the user can provide their own elf or bin image of the bootloader (not sure which one would be more appropriate - perhaps elf, for symmetry with the app image).
Finally, having these two options (a custom bootloader and a custom partition table) brings the question: should it be possible to separately flash each of these (bootloader, partition table, app image), or shall we stick with the "platformio" approach, where all of these are flashed always together. Not sure what is the answer here.

I have begun working on the custom partition table portion of this issue. I have an initial implementation ready and just need to do some testing/verification on hardware, then write some unit tests. Hopefully won't be long, though. Once this is complete I will implement the bootloader feature.
At present I am keeping the flashing process as-is just to minimize my pain while developing these features :grin: I do not feel strongly one way or another regarding the flashing process (it's adequate for my needs), so I would like to hear some other people's opinions.
@MabezDev @icewind1991 @georgik

Finally, having these two options (a custom bootloader and a custom partition table) brings the question: should it be possible to separately flash each of these (bootloader, partition table, app image), or shall we stick with the "platformio" approach, where all of these are flashed always together. Not sure what is the answer here.

Perhaps in the future, we could leverage cargo fingerprinting to only flash the partition table and bootloader if they have changed. I think for now, flashing everything is the simplest way forward.

With #40 and #41 merged this issue can likely be closed. I agree with @MabezDev that just doing everything in one go is the simplest option for now. If there is a need for splitting out this process it can always be done when it's needed.


support signTypedMessage

Add the method signTypedMessage to support EIP-712

@ansoncsh
Sorry for the late reply.
I am currently implementing a test for signTypedMessage
It would be easier to implement the tests if you have sample code using signTypedMessage. Do you have sample code?

@odanado
Sorry for my late response. Please find the sample code below:
const provider = new KmsProvider(rpcUrl, { region, keyIds: [keyId] });
const accounts = await provider.getAccounts();
const digest = "0xbe609aee343fb3c4b28e1df9e632fca64fcfaede20f02e86244efddf30957bd2"
const signature = await provider.signTypedMessage({
    from: accounts[0],
    data: digest
})

The parameter digest refers to this EIP-712 example

@ansoncsh
According to EIP-712, the second argument of eth_signTypedData should be the data before hashing
https://eips.ethereum.org/EIPS/eip-712#specification-of-the-eth_signtypeddata-json-rpc
Have you tried implementing passing hashed data to data in other wallets such as MetaMask?

@ansoncsh According to EIP-712, the second argument of eth_signTypedData should be the data before hashing https://eips.ethereum.org/EIPS/eip-712#specification-of-the-eth_signtypeddata-json-rpc
Have you tried implementing passing hashed data to data in other wallets such as MetaMask?

@odanado  I didn't try it
From my case,

use KMS wallet to sign a meta transaction for Contract A
pass signature to Contract B
execute meta transaction from Contract B

Just notice that it works on my case but not work on MetaMask.

OK.
I tried signTypedMessage with ethers.
https://github.com/odan-sandbox/sign-typed-data-sandbox/blob/34add5f0f8411daf673ea360be1ca3ffcfd2f373/hooks/useSignTypedData.ts#L42-L47
This resulted in the following error.
Error: Cannot convert string to buffer. toBuffer only supports 0x-prefixed hex strings and this string was given: {"types":{"Person":[{"name":"name","type":"string"},{"name":"wallet","type":"address"}],"Mail":[{"name":"from","type":"Person"},{"name":"to","type":"Person"},{"name":"contents","type":"string"}],"EIP712Domain":[{"name":"name","type":"string"},{"name":"version","type":"string"},{"name":"chainId","type":"uint256"},{"name":"verifyingContract","type":"address"}]},"domain":{"name":"Ether Mail","version":"1","chainId":"1","verifyingContract":"0xcccccccccccccccccccccccccccccccccccccccc"},"primaryType":"Mail","message":{"from":{"name":"Cow","wallet":"0xcd2a3d9f938e13cd947ec05abc7fe734df8dd826"},"to":{"name":"Bob","wallet":"0xbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"},"contents":"Hello, Bob!"}}

I am implementing a fix to prevent this error from occurring.

@ansoncsh
Changed eth_signTypedData to pass raw data as the second argument
Can you confirm that this is available for your use case?

@ansoncsh Changed eth_signTypedData to pass raw data as the second argument Can you confirm that this is available for your use case?

Yes, it works for my case too.
Thanks!

@ansoncsh LGTM
Thank you!

This change was released at<EMAIL_ADDRESS>


Server Crashes using Command

People on my server have started abusing a bug and crashing the server. If you type the command to set color but use a color not on the list it crashes the server.

 Just pushed commits fixing this issue and releases on github are deploying now. Will upload to curseforge asap, thanks for the notice

Thank you! that was without a doubt the quickest response and fix I have gotten from any Mod Dev!

I like fixing my mods but people rarely ever open issues unfortunately, this was a serious issue that was an easy fix that's apparently existed since October lol

Well, I love reaching out to help developers. I always report issues when I find them.
I am constantly making Modpacks with my friends and we ALWAYS find bugs!


Any way to close previous modal while opening a new one?

Summary:
I wonder how could I close any existing modal when opening a new one. Any clue? Preferable, not involving global state (like redux or context). I'm thinking about a param or something.
Steps to reproduce:

Open one modal
Inside the modal, click one element that will open a second modal
Second modal overlaps first one

Expected behavior:
I'd like to close any previous modal.

Hi @guille-alibrate, one options is to have a key in the state that can be null | 'modal_1' | 'modal_2'...and have your modals like:
<Modal isOpen={this.state.modal == 'modal_1' } />
<Modal isOpen={this.state.modal == 'modal_2' } />


TypeScript version selector can get into bad state after deleting workspace root

VSCode Version: Code - Insiders 1.17.0-insider (81fc22ec957de26d2bf6aada3f16f04e0164741c, 2017-10-03T22:47:28.178Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

EditorConfig
Edi
0.10.1

vscode-wakatime
Wak
1.1.16

vscode-icontheme-nomo-dark
be5
1.3.2

tslint
eg2
1.0.9

php-debug
fel
1.11.1

php-intellisense
fel
1.5.1

java
red
0.11.0

sourcegraph
sou
1.0.9

(1 theme extensions excluded)

Steps to Reproduce:

Add three roots removed, notremoved and notremoved2 with typescript installed
Select a typescript version installed in the removed folder
Remove the folder removed

My workspace file after that looks like this:
{
	"folders": [
		{
			"path": "removed"
		},
		{
			"path": "notremoved"
		},
		{
			"path": "notremoved2"
		}
	],
	"settings": {
		"typescript.tsdk": "removed/node_modules/typescript/lib"
	}
}

Note how the setting still points to the removed folder.
Now everytime that workspace is opened you get this error:

Notice how it combines removed and notremoved: /Users/felix/notremoved/removed/node_modules/typescript/lib
The same weird path combination now happens in the version selector:

Reproduces without extensions: Yes

I'd take this.

I tried to reproduce the issue, but had no chance. Although I could see the VS Code's error message, but there's no sign of wrong path names. Actually, everything seemed fine. Since it's quite a long time after the issue was first submitted, I guess it was resolved at some point and is not the case anymore.
@felixfbecker However, I listed the steps to make sure I've followed the right way.
Steps
This is what I tried on VS Code v1.36.0-insider, on Windows 10 (x64):

Created three directories: removed, notremoved and notremoved2.
Added empty .ts files, named dummy.ts, below the created directories.
Installed typescript in all three with v2.5.0 in removed and the latest in notremoved and notremoved2.
Opened VS Code with no workspace/working directory.
Added the directories to the clean workspace (using "File" > "Add Folder to Workspace...".)
Opened dummy.ts from removed folder in the editor.
Clicked on the TypeScript version on the statusbar (at bottom-left), which was already set to default,  v3.5.1.
Selected the "Use Workspace Version 2.5.0" from the quick pick, which in turn changed the active TypeScript version to 2.5.0.
Saved workspace in the parent directory (where those three folders reside) and quit the VS Code. The workspace file is saved as follows:

{
	"folders": [
		{
			"path": "notremoved"
		},
		{
			"path": "notremoved2"
		},
		{
			"path": "removed"
		}
	],
  "settings": {
    "typescript.tsdk": "removed\\node_modules\\typescript\\lib"
  }
}

Deleted the removed directory.

Opened the workspace file with VS Code.

Clicked on one of dummy.ts files to open it. The notification below popped up:

Clicked on the TypeScript version on the statusbar (which is now reverted to 3.5.1) to pick another version. This is the quick pick list that was shown:

Chose one of notremoved or notremoved2 and the VS Code correctly switches to the selected version.

Saved the workspace and quit the VS Code. This is how the workspace file looks:

{
	"folders": [
		{
			"path": "notremoved"
		},
		{
			"path": "notremoved2"
		},
		{
			"path": "removed"
		}
	],
  "settings": {
    "typescript.tsdk": "notremoved\\node_modules\\typescript\\lib"
  }
}

@felixfbecker  Can you please let us know if you can still reproduce this issue


Add normal file views too.

add normal code file view to so that this can be used in replacement of Telescope find_files as then it will also preview code and images.

I would love to contribute this change, how would I go about it?

I also hope that when using find_files, I can preview files and media at the same time.
I have tried a few things but have not been successful.
If possible, I hope someone can help continue the implementation to create a PR for this feature.
-- local Job = require("plenary.job")

local previewers = require("telescope.previewers")

local new_maker = function(filepath, bufnr, opts)
  opts = opts or {}
  local isSupportedBinary = true -- TODO: some filetype check

  if isSupportedBinary then
    vim.fn.jobstart({
      -- TODO: path to the vimg in scripts that telescope-media-files.nvim implemented,
      filepath,
      -- TODO: others args for vimg
    }, {
      stdout_buffered = true,
      on_stdout = function(_, data)
        if data then
          vim.api.nvim_buf_set_lines(bufnr, 0, -1, false, data)
        end
      end,
      on_stderr = function(_, data)
        if data then
          vim.api.nvim_err_writeln(table.concat(data, "\n"))
        end
      end,
      on_exit = function()
        vim.api.nvim_buf_call(bufnr, function()
          vim.cmd("filetype detect")
        end)
      end,
    })
  else
    previewers.buffer_previewer_maker(filepath, bufnr, opts)
  end
end

require("telescope").setup({
  defaults = {
    buffer_previewer_maker = new_maker,
  },
})

P.S. I am using vim.fn.jobstart but plenary.job should also work.


Update jitMaker.ts

for an example
const aggressivenessBps = 1; // 1 bps
bestprice.muln(10_000 +/- aggressivenessBps).divn(10_000);
just increasing from before descreminator 1_000.

thanks!


Typo fix for a-msiis-ftproot.md

ms-IID-FTP-Root has to be ms-IIS-FTP-Root

@Digiover : Thanks for your contribution! The author(s) have been notified to review your proposed change.


BUILD_SHARED_LIBS=ON doesn't build the shared library

Version 7.0.4 has this problem.
<IP_ADDRESS> didn't have such problem.

That is a big version difference. Could you check with the latest release?

Fixed


M3-3650 It is 40 bucks now

M3-3650 It is 40 bucks now
Check out that diff
Type of Change

Non breaking change ('update', 'change')

Promotion is expiring too soon, closing...


PhotonLib crashes with other thread models

As mentioned twice now, Photon crashes if I add another thread that is not Photon.
Q1. How can I use other thread models with Photon? More specifically OMP or if I can write my own coroutines. Because so far any other thread that is not Photon, makes your platform crash (as mentioned on your github site)
2023/05/09 06:19:19|INFO |th=0000000000000000|abc.cpp:642
handleSignal - gracefully stop Session
Segmentation fault (core dumped)

As you can see, Photon reports thread as: |th=0000000000000000|

If you are writing new project, just use photon thread, don’t mix with std::thread. photon has its way to utilize multi core.
if dealing with legacy code, you probably need to provide some demo piece. photon has an executor to coordinate with std::thread

@aubi1kenobi
Writing correct parallel programs is an essential hard problem, no matter what thread lib(s) you use. And you need to be more careful when you mix multiple threading models, because it introduces additional issues regarding inter-operation compatibility. You should understand the models before mixing them.
Photon does support mixing, and photon tries to make it easier by providing (1) some basic utilities (e.g. async interface and executor to dispatch async parallel tasks to other CPU cores); and (2) cooperative scheduling of photon threads (tasks) within a same vCPU, so that they are running much more deterministically, thus reducing bugs.
As the old saying goes, there's no silver bullet in the realm of parallel, concurrent and asynchronous programming. If you are absolutely needed to mix them up, try to minimize interaction between them.

I beg to disagree mate. I started by using the 'async' that you provide, but they do not run asynchronously. I reported it here, and you told me they are experimental, and I should use the 'thread_creatX()'.
Why don't you provide simple lines of code to show how to do it. I've exhausted the options in your samples.
Just 3/4 lines of code on how to do async jobs the photon way.  Cheers.

What do you mean by 'async' and "experimental"?


Gallery App has Layout

From https://www.google.com/design/spec/layout/structure.html#

[ ] phone
[ ] tablet
[ ] app bar
[ ] side nav
[ ] right nav
[ ] bottom bar
[ ] FAB
[ ] Content area

(You might be asking, "But, isn't the gallery app itself showing a layout?" to which I might reply "Why yes! But that's not a simplified version, who code we can use to show only the standard layout.")

Gallery app is tested to layout on a phone, and has an app bar and a side drawer, plus FAB. We probably want to add a few more layout examples, especially for tablet.


Feature: Minify HTML templates before run AOT Compiler in Production

A large part of my AOT compiled templates look like this:
this.renderer.createText(this._el_0, "             \n ", null)
Maybe a good option to get ride of this in production is minify the html templates before AOT compilation.

Hi @mbellezi,
This sounds like a great idea sadly for version 1.0 the cli is currently not accepting any new features, but I could see potential in this being implemented as part of the add-on functionality that will be implemented for 2.0

I'm surprised this is not being done.
If this is a case there is huge potential for performance and bundle size gains.

This may make sense as an improvement to Angular itself, benefitting all AOT users rather than only CLI.

Please open this issue in https://github.com/angular/angular itself instead, since that functionality is part of that repo. I think similar improvements are in 4.0 though.


Issue reading .xls file with header information on top

I am trying to read an .xls file with some extra lines of header information on top above the column names and the data. I keep getting the "Input array is longer than the number of columns in this table." error. Is there a way to work around this?

Are you using the AsDataset method? If so a workaround could be to use the IDataReader interface.

So instead of using IExcelDataReader just use IDataReader?

I think IExcelDataReader is an IDataReader. So you can just do something
like
while (excelReader.Read())
{
//excelReader.GetInt32(0);
}
On Wed, Jan 28, 2015 at 3:51 PM, olivegarg<EMAIL_ADDRESS>wrote:

So instead of using IExcelDataReader just use IDataReader?
--
Reply to this email directly or view it on GitHub
https://github.com/ExcelDataReader/ExcelDataReader/issues/52#issuecomment-71857628
.

--
Ian Cox
C.T.O.
Release  Mobile
m:            Matrix Studios, 91 Peterborough Road, London, SW6 3BU
w:            http://www.releasemobile.com
Registered in England.  Number 06323661

Closing because inactivity, and sounds somewhat resolved. Will need sample code and test data to investigate further if still a problem.


Class diagram does not account for internal/external graph inputs

Version 0.1.0 connects Process together but does not account for external inputs and outputs to the graph.

See revisions 1 and 2 in wiki sidebar under the class diagram.  Will be adding these into flatland shortly

Split the domain into two subsystems, Specification and Graph (now in flatland) which define external interfaces.


SQFormScrollableCard -- if isHeaderDisabled is set to true, title should not be required

At the moment, title prop is required, but if isHeaderDisabled is set to true we don't do anything with it, so let's not make it required.
https://www.loom.com/share/8b30454e4beb4555945ab083482ce29d

@laurelbean @20BBrown14 @hvilander Took a look at this issue, and it appears that this work is already done: https://www.loom.com/share/f2fe4aad3cae4fed9523d1d8d02f6a47.

So from what I'm seeing now, title is not required. However, I think want it to be required unless you choose isHeaderDisabled. So I think we could still improve things by implementing something similar to what you did with the Accordion component.
https://bitbucket.org/SelectQuote/scplus-shared-components/pull-requests/282#Lsrc/components/Accordion/Accordion.tsxT5

@laurelbean Sounds good, I'll take a look at implementing that.


Timestream: ExAws: HTTP ERROR: :nxdomain for URL: "https:/"

Environment

Erlang/OTP 25 [erts-13.1.5] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [jit:ns]
Elixir (1.13.4)
{:ex_aws, "~> 2.3.2"},
{:ex_aws_timestream, "~> 0.5.1"},
{:hackney, "~> 1.9"},
{:jason, "~> 1.2"},

Current configuration
config :ex_aws,
  access_key_id: [{:system, "AWS_ACCESS_KEY_ID"}, :instance_role],
  secret_access_key: [{:system, "AWS_SECRET_ACCESS_KEY"}, :instance_role],
  region: "aws-us-gov-west-1",
  debug_requests: true

When I run ExAws.Config.new(:timestream) on production environment, I get (with credentials omitted):
%{
  debug_requests: true,
  host: nil,
  http_client: ExAws.Request.Hackney,
  json_codec: Jason,
  normalize_path: true,
  port: 443,
  region: "aws-us-gov-west-1",
  require_imds_v2: false,
  retries: [max_attempts: 10, base_backoff_in_ms: 10, max_backoff_in_ms: 10000],
  scheme: "https://",
}

I removed the credentials for this post but access_key_id, secret_access_key, and security_token do appear so I am led to think configuration might not be the issue.
Then when I test a simple request
ExAws.Timestream.list_databases() |> ExAws.request()
I see the following:
14:01:19.105 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 1
14:01:19.159 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 2
14:01:19.204 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 3
14:01:19.291 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 4
14:01:19.402 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 5
14:01:19.482 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 6
14:01:20.117 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 7
14:01:20.934 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 8
14:01:21.591 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 9
** (MatchError) no match of right hand side value: {:error, :nxdomain}
    (ex_aws_timestream 0.5.1) lib/ex_aws/operation/endpoint_discovery.ex:32: ExAws.Operation.ExAws.Operation.EndpointDiscovery.handle_endpoint_operation/2
    (ex_aws_timestream 0.5.1) lib/ex_aws/operation/endpoint_discovery.ex:19: ExAws.Operation.ExAws.Operation.EndpointDiscovery.perform/2
14:01:26.490 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 10

Found the problem.
Just need to add timestream to the aws-us-gov partition in endpoints.exs
In the services for…
"partition" => "aws-us-gov",
"partitionName" => "AWS GovCloud (US)",

add…
"ingest.timestream" => %{"endpoints" => %{"us-gov-west-1" => %{}}},
"query.timestream" => %{"endpoints" => %{"us-gov-west-1" => %{}}},

To see your databases then call...
ExAws.Timestream.list_databases() |> ExAws.request(region: "us-gov-west-1")
Opened an issue in exaws to add the endpoint

https://github.com/ex-aws/ex_aws/issues/939


Separate media objects into their own models

Right now, media is only attached as a person's "profile picture". We should pull this out, and create a Media model that can then be linked to the Person, as well as to other models such as Facts, etc.

Closing this. It probably won't be necessary after moving to carrierwave.


Parse frontmatter data in the catalog command

Description

Parsing frontmatter data
Strip Markdown/AsciiDoc tags

Fixes #2832

Overall, this approach may work, but check my comments on some Markdown usage that can sometimes be problematic with regex. If the code handles that OK, then I'm fine with this.

Thank you for the review!  I will comment code in the next PR.


Upgrade RN fork to latest

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Problem
A recent commit in the react-native upstream introduced Fabric support for modals. We don't have that code in our fork yet.
Solution
Two parts:

Upgrade and republish our fork (I will do this)
Then upgrade E/App to the new version of the fork (most likely this will shadow 0.70.4, released two days ago) (I will likely make this part external)

View all open jobs on GitHub

Ran into a snag where this commit has not been included in any upstream release yet

Going to just manually perform that commit in the Expensify-0.70.4-alpha branch, so that we can get it included in the release without me trying to build off a non-stable release

Upgrade helper diff: https://react-native-community.github.io/upgrade-helper/?from=0.70.1&to=0.70.4

PR In review


Spin out joins as elasticsearch plugin

Use case:
To be honest, I would consider using crate.io just for the joins, but there is a lot of overhead (keeping _source, docs enabled everywhere, slq, missing es functionality etc).
Feature description:
Separate the joins into an elasticsearch plugin.
Makes sense ?

This is not really feasible without a huge time investment for which we've little incentive.
We've patched ES in various places and a lot of our functionality assumes that the "ES" parts are in a certain way.
We are further moving in the direction of adapting more ES components to our requirements. Partly to address some of the overhead you mentioned, but also to enable us to build some other features.
It's one of the reasons we've deprecated the possibility to enable the ES API in master already.
Btw., doc-values (column store) can be disabled.
We'd be curious to know which ES functionality you're missing.

https://crate.io/docs/crate/reference/en/latest/general/ddl/storage.html#supported-data-types For all other Primitive Types, it is enabled by default and cannot be disabled. .
keeping _source by default
autocomplete etc.

Thanks for the inputs.
I've put some cards for 1) and 2) into our backlog.


Update ansible example

Fixes #12

I updated the whole Gemfile and threw out every unnecessary gem, thanks @chris-rock !

Perfect @rndmh3ro


Add splunkPlatform.sendingQueue.storage config options to values.yaml

Closing the PR as @aryznar-splunk will not be able to work on this. I'll create a new PR to add this feature.


Use new webView data source in prod

Goal
Track web view urls as span events of the session span instead of breadcrumbs.
Testing
Unit test, Integration test and manual test.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#680  👈
#674
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nelsitoPuglisi and the rest of your teammates on  Graphite

Looks good barring one inline comment. I'd also like to confirm that this has been tested E2E before this gets merged.
It would be good to write an integration test too that checks the feature.

Yes, I tested it manually and checked the json received in the backend, and the dashboard displays it properly.
Besides that, this integration test covers the funcionality https://github.com/embrace-io/embrace-android-sdk/pull/680/files#diff-49417e80327f621fcf052fcad356035ea38339cb3faba2de6bc3242ae5c81e25R120


Incompatible with Twitter Kit 3

It seems that flutter_twitter_login 1.1.0 is only compatible with Twitter Kit v2.x, and fails to compile with Twitter Kit v3.x.
This is a blocker for me because other dependencies require that my iOS project has a minimum deployment target of 10.0, which then enforces Twitter Kit v3.x (I'm not proficient at Xcode/iOS development, but this seems to be the reason).

@eudangeld great, thank you!
I've tried it and it works fine, but I'd like to suggest a few things regarding the doc in README:

you could remove the "IOS SETUP" AppDelegate change section (copied from the official Twitter doc) as it works without the change,
same with the "SETUP YOUR PODFILE" section, the default seems fine,
you could mention the requirement that the minimum deployment target is iOS 10.1.

@deckerst
Thank's for your feedback, i changed the readme .

flutter_twitter_login:
git: git://github.com/eudangeld/flutter_twitter_login.git

If I add the above lines in pubspec, I get the below error.
Error on line 24, column 8 of pubspec.yaml: Invalid version constraint: Could not parse version "git://github.com/eudangeld/flutter_twitter_login.git". Unknown text at "git://github.com/eudangeld/flutter_twitter_login.git".
git: git://github.com/eudangeld/flutter_twitter_login.git
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pub upgrade failed (65)

@devapalanisamy
You have to add and tab (usually, 2 spaces), YAML parsing is strongly relaying on that, like Python.
flutter_twitter_login:
  git: git://github.com/eudangeld/flutter_twitter_login.git

Thanks @leocavalcante
It works

@deckerst
I forked this repo and updated TwitterKit to 3>.
Checkout => https://github.com/eudangeld/flutter_twitter_login
In your pubspec add =>
flutter_twitter_login:
  git: git://github.com/eudangeld/flutter_twitter_login.git

All right, thank you for that, it is compiling as well, but when I try to instantiate the TwitterLogin class the app suddenly closes without any feedback =/

@marcobraghim
Open in my forked repo and i'l try to help you....

@marcobraghim
Open in my forked repo and i'l try to help you....

Thank you, but the issues option does not shows up in your repo.
Anyway, I found another package that works well for me, thank you very much.


fix: crash on EMPageViewController.scrollViewDidScroll(_:) + 631 , mo…

…dify forced unpacking

Hi @zllarry! I just released a new version of Parchment (3.0) that replaces EMPageViewController entirely, so this shouldn't be needed anymore. But thanks a lot for making this PR anyway 🙌


What happened to this?  was this project abandoned? =(

Yup - I changed jobs and no one else wanted to pick it up.  Sorry for the bad news.

Hi @apfejes
Are you interested in continuing the project? or Is there any possibility of doing that?
I would like to be a contributor.

I'd also like to contribute.
I don't have much experience but I'm looking to move into dev work and this project would definitely be a great step in that direction.

Truthfully, I really don't have the time to contribute to this project, but there are likely others who would be interested in mentoring or helping make this happen.  I suggest joining the reddit r/bioinformatics slack group, and we can see if any of the original contributors would be willing to take on that role.

As mentioned in the slack group the other day, folks who are interested might also consider contributing to PyDESeq2.
Repo | Preprint

As far as I can tell, PyDESeq2 does not give users the ability to perform TMM which is what EdgePy was useful for--Did anyone find a good alternative?


Why is there a src/lib.rs file with only comments?

https://github.com/paritytech/polkadot-sdk-minimal-template/blob/master/src/lib.rs
Why does this file exist in the template?

These are the docs following the sentiment to use rustdoc and keep readmes as a light intro.
(The readme has been improved a bit since then, but lib.rs stayed as is).
However it doesn't quite work here because the package gets replaced with a workspace root. And the template crates are not published to any registry, so there is no way to read those rustdocs without cloning the repo (e.g. on mobile).
So for these reasons I think templates should be the exception and avoid rustdocs for introductory documentation, instead have it right in the readme - so we can remove lib.rs (or integrate into the readme file).
@gupnik Do you agree with that?

I agree, if your auto-generation process can remove this, it makes sense to me.

the only place they can be seen is in https://paritytech.github.io/polkadot-sdk/master/minimal_template/index.html
I think these were added when the template had no good readme. Now that it has, they can be removed, or bere a mere duplicate of the readme include_str!("./README.md").


Failure to find resources to continue a crafting/processing chain

Issue description:
When I attempt to use the auto crafting feature to craft steel ingots from Mekanism it refuses to see resources that were just processed (in a batch of 8) to continue the chain to smelt the ingots
What happens:
when processing products are returned to the RS system weather it be one by one are all at once the system does not see that the items are now there
What you expected to happen:
I ask for steel ingots and one compressed carbon and 8 iron enter the Metallurgic Infuser and get processed to be enriched iron then are placed in a chest then into the RS system via an importer.  then one compressed carbon and eight enriched iron enter the Metallurgic Infuser and get processed to be Steel Dust that goes back into the RS system and then the steel dust goes into a smeltery and back into the system.
Steps to reproduce:
1.See above
Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: <IP_ADDRESS>9
Refined Storage: 1.1.3

Does this issue occur on a server? Unknown, probably

fixed in dev

cool, now I have to go bug the Mekanism dev because the thermal evaporation tower locks up my game :/


concurrent_connectivity_test failure in Basic Tests C Linux

concurrent_connectivity_test failure in Basic Tests C https://source.cloud.google.com/results/invocations/22cb4059-6f1a-4de1-9b97-279083f28201/log
Seen on https://github.com/grpc/grpc/pull/15608

Not seen in a while. Closing


Support for tables

Thanks for your amazing work. My documentation almost works with docc2html except for tables. I've seen that the Content enum currently doesn't support tables and wanted to ask how hard it is to implement. Maybe I could create a PR if you could point me in the right direction :)
My table in the json file looks like this
{
  "type": "table",
  "rows": [
    [
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "text",
              "text": "Mode"
            }
          ]
        }
      ],
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "text",
              "text": "Description"
            }
          ]
        }
      ]
    ],
    [
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "codeVoice",
              "code": "buffering"
            }
          ]
        }
      ],
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "text",
              "text": "The mode indicates a buffering state."
            }
          ]
        }
      ]
    ],
    [
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "codeVoice",
              "code": "pause"
            }
          ]
        }
      ],
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "text",
              "text": "The mode indicates a button tap triggers pause (two vertical bars)."
            }
          ]
        }
      ]
    ],
    [
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "codeVoice",
              "code": "play"
            }
          ]
        }
      ],
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "text",
              "text": "The mode indicates a button tap triggers play (triangle)."
            }
          ]
        }
      ]
    ],
    [
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "codeVoice",
              "code": "stop"
            }
          ]
        }
      ],
      [
        {
          "type": "paragraph",
          "inlineContent": [
            {
              "type": "text",
              "text": "The mode indicates a button tap triggers stop (square)."
            }
          ]
        }
      ]
    ]
  ],
  "header": "row"
},
{
  "anchor": "Respond-to-Button-Taps",
  "level": 2,
  "type": "heading",
  "text": "Respond to Button Taps"
},

An example DocCArchive which reproduces that would be helpful.

Will post tomorrow 👍🏻

TableDocC.zip

The export of that doesn't seem to carry any table?

Just noticed it, sorry. I don't get why the DocC catalog seems to be ignored completely (I used the one from my project and just deleted everything that's unnecessary).

OK, should be fixed.


UX and styling improvements to Datetime

First PR here. Attempted to implement input typing but thought I'd at least try
some more basic things first.  I took some time and looked at several other
Datepickers out there including my own ractive-datepicker, Antd, MUI,
react-datepicker, react-date, react-times, etc.
Most of the changes here are cosmetic to improve the UX
of what is already there. There are two minor inline styles that I deliberated
over but couldn't avoid. Without them it looks very lobsided due to Popover's
default padding and the Divider's margin.
There is currently an issue where clicking on hours 5pm - 11pm don't show
the minutes mode after. Any idea about that? I was having trouble finding
the flow after the _.invokeARgs.
Let me know your thoughts.

I also added localization support using navigator.language and the internationalization api (https://caniuse.com/#feat=internationalization good support).
Set your browser to a different language and the months/days of weeks should be changed. Doesn't change any other strings like 'Hour', 'Minutes' that's probably the domain of another localization method.

@JonDum, could this also be place to add some support for edge users? Currently there is no way for them to clear the date field, unless it's a manually added button.
https://stackoverflow.com/questions/32629330/clear-value-of-input-type-date-in-microsoft-edge
might solve quite a few headaches

Ideally I'd like both a little x button inside the input and to be able to manually clear it with Backspace or Delete. The X shouldn't be hard to add though à la antd style.
I'd really like to get feedback from @levithomason before continuing on this though

https://github.com/Semantic-Org/Semantic-UI-React/pull/2821#issuecomment-500816353


[WIP] Fixed #20461 -- Added support for running Django's test suite in parallel

Trac ticket: #20461

a quick FYI on py 3.4: ImportError: No module named 'tblib'

@collinanderson, it's a thid party application.

Indeed you need to pip install tblib. That's the easiest solution I could find to get tracebacks from the multiprocessing pool.

Not bad :)
Ran 9003 tests in 61.995s
FAILED (failures=1, errors=31, skipped=429, expected failures=6)
Destroying test database for alias 'default'...
Destroying test database for alias 'other'...
Command exited with non-zero status 1
289.78user 13.87system 1:32.20elapsed 329%CPU (0avgtext+0avgdata 360600maxresident)k
8296inputs+336464outputs (72major+3018357minor)pagefaults 0swaps

That's a lot of errors... I don't get that many.

https://gist.github.com/collinanderson/55fdb3081f43a1f7636f

We likely need to mark some tests as single-core only. For example, we don't want to run multiple memcached servers on different ports so that each core has its own memcached instance... Similarly for selenium tests, and tests that play with filesystem.

@akaariai I'd rather make these tests independent from one another. We can use different filesystem paths, different key prefixes, etc.

That is of course a better solution.

Well, it turns out that the better solution isn't always viable. I have implemented a SerializeMixin that makes it easy to enforce serial execution of test cases inheriting a common mixin.

The test failure is a fluke: the checkout from GitHub failed.

Closing in favor of some new PRs.


Update golang to 1.22

What type of PR is this?
/kind enhancement
What does this PR do / why we need it:
Bump golang to 1.22

/lgtm
/approve


2 bugs in mirostat sampler

Hi,

The first bug is in the function estimate_s. The function is unstable because the probability in denominator could be 0.0. As result, num below become NaN.

The second bug is in the function compute_k. This function is very unstable, the result is overflow.

n.powf(-eps) = 1 / n.powf(eps) -> for n=65536, it can become overflow easily
powf(1.0 / s) -> s can become 0.0 -> unstable.

A plot of the formula k = (eps * 2.0_f32.powf(tau) / (1.0 - n.powf(-eps))).powf(1.0 / s) using wolframalpha show its stability:

The power in the formula is n^(-eps) so it should be 65536^(1-x), and this is what I get:

Just pushed a fix. would you like to try again?

yes, may bad, I overlook -eps. I tried the fix, it runs now without overflow so far. However, the formula is in my opinion  unstable because k is undefined for s==1.0 and s==0. k is also huge or overflow for -0.5<s<0.


Add Schemathesis

Hi! Thank you for maintaining this list! This PR adds Schemathesis to the list of testing tools.

Thanks! As this couldn't be merged without a rebased, I added the link myself in 7a05e197e085ea5cc8d2c83d0a91d4e4be502be7


Unable to load element js when deployed using aurelia-cli

We're building with Aurelia CLI and it works great locally (au run --watch) but when we bundle our vendor js and deploy, I see an error trying to load element js.
Installed per instructions, using npm.  Version:
➜  selfcare-login git:(master) ✗ cat package.json| grep recaptcha
    "aurelia-plugins-google-recaptcha": "^2.5.2",

And aurelia.json looks like:
{
  "name": "aurelia-plugins-google-recaptcha",
  "path": "../node_modules/aurelia-plugins-google-recaptcha/dist/amd",
  "main": "aurelia-plugins-google-recaptcha"
}

Also updated the prepend section, mine looks like:
"prepend": [
          "node_modules/jquery/dist/jquery.js",
          "node_modules/babel-polyfill/dist/polyfill.min.js",
          "node_modules/bootstrap/dist/js/bootstrap.min.js",
          "node_modules/bluebird/js/browser/bluebird.core.js",
          "node_modules/whatwg-fetch/fetch.js",
          "node_modules/requirejs/require.js"
        ],

But when I try to load my deployed application (nginx in Docker), I see in the logs:
2017/09/25 19:40:48 [error] 5#5: *4 open() "/usr/share/nginx/html/login/node_modules/aurelia-plugins-google-recaptcha/dist/amd/aurelia-plugins-google-recaptcha-element.js" failed (2: No such file or directory), client: <IP_ADDRESS>, server: localhost, request: "GET /login/node_modules/aurelia-plugins-google-recaptcha/dist/amd/aurelia-plugins-google-recaptcha-element.js HTTP/1.1", host: "localhost:8011", referrer: "http://localhost:8011/login/"

I'm sure there's something dumb I've forgotten to do, but at this point feel like I've done the due diligence to read the docs, etc.
Thanks for any help!
Update:

I also tried upgrading to<EMAIL_ADDRESS>And then using:

au import aurelia-plugins-google-recaptcha

But it appears to only have made superficial modifications to my aurelia.json file and the error remains the same.

Latest version of the plugin (v2.6.1) works perfectly with latest version of aurelia-cli (0.33.1).


[FLINK-33628][runtime] Upgrades default ZooKeeper version from 3.7.1 to 3.8.3

What is the purpose of the change
Upgrades Flink's ZK default version from 3.7.1 to 3.8.3 to cover the most-recent stable version again for 1.19.
Brief change log

Upgrades pom.xml and TestContainer

Verifying this change

Trivial change: CI should still pass

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, ZooKeeper: yes
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

@flinkbot run azure


Add footer section

I would like to add footer section in this.

Hello @mansi1309,
Thank you for creating an issue on this! ⭐
So, I'm officially assigning this task to you under SWOC. So feel free to start working on it.
I want you to know that before create any issues, make sure to read the full documentation of this project first. It'll give you a better understanding.
Make sure to follow our Contribution Guidelines & PR Guidelines.

If you have any questions or need clarification, don't hesitate to ask in the comments or on Discord [Find #sql-dev-tools channel].
#Good luck! ✌

Can I contribute in this

Hello @Paarisha1,
Absolutely! If you're interested in working on the footer section for the SQL Dev Tools project, that would be fantastic. So, I'm officially assigning this task to you under SWOC.
Certainly! Before you start contributing, I recommend reviewing the pull request discussion on the related footer issue.
@mansi1309's pull request (#48) has some feedback and concerns regarding the codebase. Take some time to go through the discussion to understand the issues that were identified. This will help you in crafting your contributions more effectively and ensure alignment with the project's standards.
Thank you for understanding. Happy Contribution!!

If you have any questions or need clarification, don't hesitate to ask in the comments or on Discord [Find #sql-dev-tools channel].
#Good luck! ✌

I'll provide you a simple footer design template, you can work on that by adding relevant links of our project in the footer lists.
Here's the design:

Sure

Hello @Shivam250702,
Thanks for your interest in this issue!
As you can see, this task has already been assigned to @Paarisha1 with Easy label.
So, feel free to create another issues.
Thanks for understanding.

If you have any questions or need clarification, don't hesitate to ask in the comments or on Discord [Find #sql-dev-tools channel].
#Good luck! ✌

Hey @Paarisha1,
Thank you for the update on footer design. I appreciate your diligence.
However, upon further review, I've observed that the code changes in your PR might cause conflicts with the main branch. Additionally, there have been some recent feature additions to the main branch.
So, I kindly request you should clone the recent version of the repository and make the necessary changes accordingly.
However, for the time being, I would advise waiting until further updates are provided before making any additional changes.
Thank you for your understanding.

PS: I will provide you with further updates soon. Till then don't do anything.

Sure sir

Sir kindly provide me all the updates soon so that I can start working on this

@Paarisha1, I've merged your PR as it has no conflict in the current situation.
Thank you for the Contribution.✌


Add Ghana public holidays

Proposed change

Adds support for official public holidays observed in Ghana
closes #1191
Type of change

[x] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[ ] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency update (version deprecation/upgrade)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] I've run make pre-commit, it didn't generate any changes
[x] I've run make test, all tests passed locally

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
10296

Relevant Lines:
10296

💛  - Coveralls

Alright great, I'll add in the changes. Cheers 🥂


Add exposure and compression string to Camera Detector

User story
When trying to include some of the settings that we are using to configure the cameras in our rigs, I couldn't find the following:

exposure parameter for Camera
compression codec

Acceptance criteria

[ ] Exposure and compression are added to the Camera settings.

Sprint Ready Checklist

[ ] 1. Acceptance criteria defined
[ ] 2. Team understands acceptance criteria
[ ] 3. Team has defined solution / steps to satisfy acceptance criteria
[ ] 4. Acceptance criteria is verifiable / testable
[ ] 5. External / 3rd Party dependencies identified
[ ] 6. Ticket is prioritized and sized

Notes
Maybe this can be found somewhere, I couldn't locate it.

Adding some detail: for some cameras the raw video is never saved, making the compression settings useful to track. This might be redundant if the information is already in the video file, but if not it would make sense to capture it here (and not e.g. in processing.json)

@tiffanyona Do you know if there's a list of compression codecs that would be used here?  I'm wondering if this can be constrained to some small set of options or if we need to allow people to include generic strings.
If you can give me some examples of the compression strings you're imagining including that would be great.

These are some examples:
"-c:v hevc_nvenc -pix_fmt x2rgb10le -color_range full -tune hq -preset p3 -rc vbr -cq 16 -rc-lookahead 56 -temporal-aq 1 -qmin 0 -qmax 10"
-vf "scale=out_color_matrix=bt709:out_range=full" -c:v h264_nvenc -pix_fmt nv12 -color_range full -colorspace bt709 -color_trc linear -tune hq -preset p4 -rc vbr -cq 12 -b:v 0M -metadata author="Allen Institute for Neural Dynamics" -maxrate 700M -bufsize 350M
I think it might be easier to just have the string there. But I can see it also being a combination of some constrained options and the whole string as notes. Whatever you think makes more sense.

Great I think having the codec separate might make sense, could be useful for re-encoding in the future, and then having the full string as well. I'll close this out later this month.


Information Gathering/Host to IP

It's not a flaw, it's more a design issue. After entering a valid hostname, tool correctly print the IP address , but automatically change to main screen of program and scroll down. By default size (kali terminal) it looks like it didn't show anything. So some pause, or "press key to continue" would be nice :). It's just an idea , or guide for those who are thinking it doesn't work , like me :D .

This has been implemented.


Implement AParser Language Docs

Problem

Users should know what grammars (syntax) are currently (or in the upcoming future) available for coding AParser language

Implemented in #56 #57 #67


feat:add hook feature for transaction form package gdb

The main purpose of adding transaction hooks is to intercept the rabbitmq queue pushed in the transaction.
The Begin hook is used to notify that a transaction is open and start staging all queues under the current transaction ID
The Commit hook notifies rabbitmq to push the queue corresponding to the corresponding transaction ID after the transaction is committed
The Rollback hook tells rabbitmq to remove all queues staged for the corresponding transaction ID when the transaction is rolled back

Codecov Report
Patch coverage: 93.40% and project coverage change: +0.02 :tada:

Comparison is base (4ad508c) 79.15% compared to head (096774e) 79.18%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2794      +/-   ##
==========================================
+ Coverage   79.15%   79.18%   +0.02%
==========================================
  Files         632      633       +1
  Lines       52174    52258      +84
==========================================
+ Hits        41298    41380      +82
- Misses       8830     8831       +1
- Partials     2046     2047       +1

Flag
Coverage Δ

go-1.15-386
?

go-1.15-amd64
?

go-1.16-386
?

go-1.16-amd64
?

go-1.17-386
79.22% <93.40%> (+0.05%)
:arrow_up:

go-1.17-amd64
?

go-1.18-386
78.82% <93.40%> (+0.03%)
:arrow_up:

go-1.18-amd64
78.82% <93.40%> (?)

go-1.19-amd64
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

database/gdb/gdb.go
68.34% <ø> (ø)

util/gutil/gutil.go
92.17% <70.00%> (-2.12%)
:arrow_down:

database/gdb/gdb_core_transaction.go
72.84% <94.44%> (+7.31%)
:arrow_up:

contrib/drivers/clickhouse/clickhouse.go
73.82% <100.00%> (ø)

database/gdb/gdb_core_transaction_hook.go
100.00% <100.00%> (ø)

frame/g/g_func.go
86.66% <100.00%> (+0.95%)
:arrow_up:

... and 2 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

增加事务钩子是为了拦截在事务尚未提交前推送的rabbitmq队列。
Begin钩子是用于通知事务已开启，启动暂存当前事务ID下所有队列
Commit钩子在事务提交后通知rabbitmq统一推送对应事务ID对应的队列
Rollback钩子在当事务回滚后通知rabbitmq移除对应事务ID暂存的所有队列

code-test(1.20,386) test fail，But I didn't modify the code for this block（github.com/gogf/gf/v2/net/ghttp）

@xyqweb It is too complicated adding hook in transaction to fulfil your business purpose. It is suggested using custom driver to fulfil your hook purpose.


[T2A3][W11-A4]Vishnu Prem

@burnflare please name your commit messages in imperative tone.
i believe this is not completed yet, so add a comment "ready for review" when done. I will complete the review after that.

@burnflare you need to update userguide, help and tests when you modify the behavior of the program.
please take a look at the comments. Ack and close the PR once you have read them


MQTT to ROS and get ERROR info unpack(b)  received extra data.

When i try to pub mqtt message and transfer it to ros message

Adding a '/' in front of the topic name in the mqtt pub command solved the issue for me.

mosquitto_pub -t 'echo' -m '{"data" : "hello"}'
This solved the issue for me.

I am still having this issue. As for @grejj you are publishing directly to a ROS topic. The "/" is not meant for the MQTT topic I think.
As for @PrimeshShamilka your method still causes the error.

Can you post your params.yaml file and the command you are using to publish mqtt message to ROS?

@grejj I could solve it by removing the msgpack serialization and just switching to json formatting. I think I needed to publish a msgpack formatted message to the mqtt topic in order to send it to ROS. By switching to json I can just simply publish a json format.
However I would still like to use msgpack, since it seems to be faster.
This is my yaml file:
mqtt:
  client:
    protocol: 4      # MQTTv311
  connection:
    host: <IP_ADDRESS>
    port: 1883
    keepalive: 60
  private_path: device/001
serializer: json:dumps
deserializer: json:loads
bridge:
  # ping pong
  - factory: mqtt_bridge.bridge:RosToMqttBridge
    msg_type: std_msgs.msg:Bool
    topic_from: /ping
    topic_to: ping
  - factory: mqtt_bridge.bridge:MqttToRosBridge
    msg_type: std_msgs.msg:Bool
    topic_from: ping
    topic_to: /pong
  # echo back
  - factory: mqtt_bridge.bridge:RosToMqttBridge
    msg_type: std_msgs.msg:String
    topic_from: /echo
    topic_to: echo
  - factory: mqtt_bridge.bridge:MqttToRosBridge
    msg_type: std_msgs.msg:String
    topic_from: echo
    topic_to: /back
  # private path
  - factory: mqtt_bridge.bridge:RosToMqttBridge
    msg_type: std_msgs.msg:String
    topic_from: /private/echo
    topic_to: ~/echo
  - factory: mqtt_bridge.bridge:MqttToRosBridge
    msg_type: std_msgs.msg:String
    topic_from: ~/echo
    topic_to: /private/back
  # Velocity
  - factory: mqtt_bridge.bridge:RosToMqttBridge
    msg_type: std_msgs.msg:String
    topic_from: /velocity
    topic_to: DCMotorLogic/oPreferredVelocity

And these were the messages I tried to publish:
mosquitto_pub -h <IP_ADDRESS> -t 'ping' -m {"data: true"}
mosquitto_pub -h <IP_ADDRESS> -t 'ping' -m {"data": "true"}

I tried more formats, but somehow couldn't get the right format for msgpack.

The mqtt message you are publishing has to be one long string I believe so I think you have to surround the message in single quotes.
Also the ping topic is of type bool so you shouldn't put " " around true or else it will think it is a string.
Try this:
$ mosquitto_pub -h <IP_ADDRESS> -t 'ping' -m '{"data": true}'

The mqtt message you are publishing has to be one long string I believe so I think you have to surround the message in single quotes.
Also the ping topic is of type bool so you shouldn't put " " around true or else it will think it is a string.
Try this:
$ mosquitto_pub -h <IP_ADDRESS> -t 'ping' -m '{"data": true}'

That still gives me an error.
unpack(b) received extra data.
Atleast, when I try it with msgpack serialization. With Json serialization it works

I am no sure how else I can help. I copied your params.yaml file and tried both json and msgpack serialization with this command:
$ mosquitto_pub -t 'ping' -m '{"data": true}'

And I was able to successfully get the true message when echo:
$  rostopic echo /pong

The only other thing I can think of was that bson package was giving me problems and I am using pymongo instead, but shouldn't affect you since you said that json is working fine. These are the packages I have installed:
Inject==3.5.4
pymongo==3.11.0
paho-mqtt==1.3.1
msgpack-python==0.5.6

Strange. It appeared that I didn't have bson installed at all. As soon as I installed it, it said
BSON installation does not support all necessary features.
So I uninstalled it and installed pymongo. However that still returns the same error
unpack(b) received extra data
Is there a file where I have to replace bson with pymongo or is just installing enough?

I am still having this issue. As for @grejj you are publishing directly to a ROS topic. The "/" is not meant for the MQTT topic I think.
As for @PrimeshShamilka your method still causes the error.

mosquitto_pub -t 'echo' -m '{"data" : "hello"}'
This code snippet only works with JSON as the serializer / deserializer.
In order to use msgpack, first you should  packing data into msgpack format before publishing from the mqtt publisher. This can be easily done in python as follows,
msg = bytearray(msgpack.dumps({'data': "Hello"}))

# or

msg = bytearray(msgpack.packb({'data': "True"}, use_bin_type=True))

When sending from ros to mqtt using mspack, follow the steps below,

Publish from ros

rostopic pub /echo std_msgs/String "data: 'hello'"

Unpack the msgpack message at the mqtt subscriber.

unpacked_msg = msgpack.unpackb(msg.payload, use_list=False, raw=False)
Hope this will help.

Please refer to #34

Please refer to #34

Opening this up again since I'm getting the same error, but I have a different scenario:
Machine 1:

Jetson Nano (Ubuntu 18.04)
ROS Melodic
Python 2.7

Machine 2:

Laptop (Ubuntu 20.04)
ROS Noetic
Python 3

I am trying to send a PointCloud2 message from Machine 1 to Machine 2. Whenever Machine 2 gets a message, I get the following error message in my terminal: unpack(b) received extra data.
I'm curious if there is a breaking change with msgpack-python when going from Python version 2 to version 3. The msgpack project page says the following:

Major breaking changes in msgpack 1.0

Python 2

The extension module does not support Python 2 anymore. The pure Python implementation (msgpack.fallback) is used for Python 2.

Packer

use_bin_type=True by default. bytes are encoded in bin type in msgpack. If you are still using Python 2, you must use unicode for all string types. You can use use_bin_type=False to encode into old msgpack format.
encoding option is removed. UTF-8 is used always.

Unpacker

raw=False by default. It assumes str types are valid UTF-8 string and decode them to Python str (unicode) object.
encoding option is removed. You can use raw=True to support old format.
Default value of max_buffer_size is changed from 0 to 100 MiB.
Default value of strict_map_key is changed to True to avoid hashdos. You need to pass strict_map_key=False if you have data which contain map keys which type is not bytes or str.

Using JSON as the serializer/deserializer works fine, however. I also don't see any msgpack errors when using the bridge between two machines using ROS Noetic.
Here are my config files:
Machine 1:
mqtt:
    client:
        protocol: 4      # MQTTv311
    connection:
        host: <IP_ADDRESS>
        port: 1883
        keepalive: 60
bridge:
    - factory: mqtt_bridge.bridge:RosToMqttBridge
      msg_type: sensor_msgs.msg:PointCloud2
      topic_from: /jackal01/velodyne_points
      topic_to: jackal01/velodyne_points

#serializer: json:dumps
#deserializer: json:loads

Machine 2:
mqtt:
    client:
        protocol: 4      # MQTTv311
    connection:
        host: <IP_ADDRESS>
        port: 1883
        keepalive: 60
bridge:
    - factory: mqtt_bridge.bridge:MqttToRosBridge
      msg_type: sensor_msgs.msg:PointCloud2
      topic_from: /jackal01/velodyne_points
      topic_to: /jackal01/velodyne_points

#serializer: json:dumps
#deserializer: json:loads


Implementation of STAC catalogue/collection definition

STAC catalogue/collection file for each dashboard instance

RACE
Trilateral
GTIF

Instances have been configured, preview can be seen here:
RACE Instance
Trilateral Instance
GTIF Instance
Configuration of all previously available datasets is underway, separate issue added #42
Closing this issue.


Support using existing Auth0Client to improve performance

Checklist

[X] I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
[X] I have looked into the API documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved
Currently, in our react application, authentication is only kicked of after the first react render call (i.e. when the context is instantiated).
To improve bootstrapping of our react app we want to start authentication BEFORE react even starts rendering (or is even loaded). This idea has been uttered before (https://github.com/auth0/auth0-react/pull/278#issuecomment-923053283) and there exists a document with reasoning against it here: https://gist.github.com/adamjmcgrath/0ed6a04047aad16506ca24d85f1b2a5c
In our case we are also NOT interested in having multiple clients but are interested in the ability to immediately start checking the session right after the auth0client code is available and not only when the first react render call is happening?
Is this possible?

If so: how? :)
If not: Are there plans to enable it?

Thanky you for any input!
Describe the ideal solution
Possible solutions:

provide an imperative API to either provide an existing Auth0Client to the context provider
provide a way to configure + trigger authentication before react context+context provider are even created.

Alternatives and current workarounds
No response
Additional context
No response

Thanks for reaching out. As you mention yourself, this has been asked for before and we still have no plans to support this.
I do want to call out the fact that our Auth0-React SDK is a tiny wrapper around Auth0-SPA-JS, that is build around the provider and context API for react.
If this is not what you want (which is the case, as you want to exit the Auth0Provider way of instatiating the client), it's perfectly find to use Auth0-SPA-JS directly and the lack of passing your own Auth0Client shouldn't block you. You can have a look at our Auth0-React SDK and rebuild whatever you want around Auth0-SPA-JS yourself to better suit your needs.
So long story short:

It is not possible using Auth0-React, as this is a thin and opiniated Auth0-SPA-JS implementation for React.
There are no plans to enable support for this, because it is already possible when using Auth0-SPA-JS directly.

Sure, using Auth0-SPA-JS directly can feel a bit complicated, but we encourage that for everyone that has more complicated use-cases as what our Auth0-React SDK offers.

got it, thanks for the explanation!


Add max character counts to textarea input

fixes #200
When input is in box:

When no input is in box:

charararararacters

Known bug:

@pierreTklein do you want to make a separate issue for the checkbox and merge this?

Sure. We merge and then create an issue for it or something.


Add dumpRaw for regression testing with li.

Summary
This dumps raw scraped data to a new report, raw.json, stored in dist.
Sample output:
[
  {
    "_path": "/Users/jeff/Documents/Projects/coronadatascraper/src/shared/scrapers/US/CA/san-diego-county.js",
    "county": "fips:06073",
    "state": "iso2:US-CA",
    "country": "iso1:US",
    "timeseries": false,
    "certValidation": true,
    "priority": 0,
    "cases": 2943,
    "deaths": 111
  }
]

The new routine only includes out a handfull of fields from the raw scraper data in the report, and the resulting file is ~ 3 mb.
With this output, we can work on getting regression testing in place for corresponding sources in li.
Changes

added --dumpRaw to options, eg yarn start --dumpRaw.  The raw report isn't written if that's not set.

Pretty straightforward, biggest thing to note is that if --dumpRaw isn't specified, it doesn't print, so no affect on existing code.  if (!args.options.dumpRaw) return args;


Create layout managers

This would allow a developer to quickly put together an application without having to calculate positioning and could offload some of the resizing logic.
A widget could default to absolute positioning of child widgets if no layout is specified.

Some thoughts  about implementation from some discussion with @stratact

Should a layout be a widget? or should a widget have an optional layout.

if a widget is a layout, then you would still need to specify position and sizing information
if a widget has a layout, the layout would essentially "inherit" the size information of the owning widget, and use that to delegate space to subwidgets

In the case of a window, should it have multiple widgets? or a layout (widget), that contains subwidgets?

TLDR: I think container widgets being layouts would be better.
@LazyOxen by widget having a layout, do you mean the container widget has a layout, like java's Swing, or the contained widgets have layout information and the container has no layout information, like Python's Tkinter?
I hope the former, because tkinter's way is error prone (how do you handle a container with widgets asking for 2 different layouts? tkinter throws an exception).
So, we either have:

(A) a bunch of different container widgets, each being a layout, placing and sizing their children as they see fit

or

(B) a simple Container in which:

widgets could be placed and sized manually by default
could be given a Layout object to compute position and size of the children

I prefer (A).
Different layout might need different layout information for their children. For exemple, say we have a PackLayout (stacks its children one after the other) and a GridLayout (places its children in the cells of a grid). PackLayout might not need any such information but GridLayout would require a X and Y index to specify a cell (plus optionnal cellspanX and cellspanY for exemple, to tell that a certain cell should stretch across many columns or rows).
If going with option (B), you would have to add a child to the container and then also set the layout information on the Layout object for that same child. What if a layout (like GridLayout) absolutely needs that information? In the (B) case, you are not forced to give the information to the Layout object (you could forget to do it). The Layout object could also be given information for a widget that isn't even in the container. Also, what happens if, for a given container, its Layout object is changed? (and if this shouldn't be allowed, then (B) seems pointless and (A) seems like the best choice). I'm not saying it's impossible to get it to work, just that (B) is not the most elegant of the two.
Going with (A), we can require the layout information when adding a child, and know for sure, at compile time, that no child widget is without it's required layout information. The downside of (A) seems that it would be less flexible than (B), but what else than a plain Container would need a Layout object anyway? and is there any value to being able to change the Layout object at runtime without changing the Container itself? No and no, at least from my point of view.
Also, if it's relevant to know:

JavaFX uses (A)
WinForm and WPF use pretty much (A), but encourage to use only the default layout, which uses grouping, docking and anchoring of the children to achieve all sorts of layouts (and it works great with the Visual Studio GUI designer)

As for the case of a Window, it think it should have just one widget, which gets stretched to fill the entirety of the window: if more than one widget is needed, then the window should be given a Container as its sole widget (by the user of OrbTK).

@simondesloges Thanks for the input! I am working on something like what you have suggested


Django Interface (Apache) - Behavioral Analysis Tab Not Functioning Correctly

I have the Django interface being presented via Apache WSGI and everything seems to be working fine with the exception of the Behavioral Analysis tab.
At first load of that tab everything is there (analysis wise). The problem is when you click any of the color coated icons other than the gray default one I receive the following error.
"Error loading data. Please reload the page and if the error persists contact us."
Are you by chance using Apache to serve up the Django interface? Would you mind sharing your  config?

This issue can be closed -- Cuckoo is not affected, it was due to a modification of mine.  If you're submitting bugreports to the unmodified version of Cuckoo, please make sure you're actually testing against their version.  Nobody likes to receive bug reports for bugs that aren't theirs.
Thanks,
-Brad

Thanks Brad, I wasn't sure if it was a core cuckoo/django related issure or not. I'll be sure to validate before submitting issues going forward. Appreciate you keeping me honest :-)

Issue is resolved.


[Program]: Write a Scala program to find average of numbers by recursion

Description
Write a Scala program to find average of numbers by recursion
Average of numbers is the sum of all numbers divided by the number of numbers. For example, the average of 1, 2, 3, 4, 5 is 3. The average of 1, 2, 3, 4, 5, 6 is 3.5.
Average of numbers can be calculated by recursion. The average of numbers is the sum of the first number and the average of the rest of the numbers. The average of the rest of the numbers is the sum of the second number and the average of the rest of the numbers. The average of the rest of the numbers is the sum of the third number and the average of the rest of the numbers. And so on.
Input  : 1 2 3 4 5
Output : 3

How to contribute

Save the solution in program/program/find-average-of-numbers-by-recursion/program/findAverageOfNumbersByRecursion.scala file

!assign