feat(report-portal): add report portal plugin

Hey, I just made a Pull Request!

This PR contains a new plugin Report Portal.

A global page to show overview of all instances

A page to show details for each instance such as projects and launches

Statistics card showing overview of launch results on entity page

closes #573

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@awanlin do I need to rebase to fix pipeline?

rebased branch and commits

Hi @yashoswalyo, I've triggered the build for you, looks like the API Reports need to be updated details on that are here: https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md#api-reports (this goes to the main Backstage repo as we don't have these details in the Community Plugins's guide yet, I have a PR open to add them). Also, I won't have time till this Friday to do a full review of this.

Forgot to run prettier, I'll update the MR in a while

Hey @awanlin looks like CI is passing now, can you do the further review?

Separate side note on the naming: what do you think about "Report Hub" instead? Feeling there's a big risk of confusion with the Backstage app itself being the "Developer Portal"

never mind, as mentioned the name of the tool itself is "Report Portal", so we don't have that many options 😅

Hi @yashoswalyo, there are two open comments still, can you take a look at those, please?

Hi @yashoswalyo, there are two open comments still, can you take a look at those, please?

Done


backup/restore: Allow to handle absolute and relative paths

(inspired by https://github.com/restic/restic/pull/3200)
Currently, rustic always converts the backup target into an absolute path. There is the --as-path (#280) option to change that path, but still all is done for absolute paths.
We could change the behavior to allow relative paths and distinguish between absolute and relative paths

backup: if a relative path is given, save the exact relative path in the paths field of the snapshot and only save the relative path tree. Allow to use --as-path to convert absolute paths to relative ones and vice versa.
restore: restore currently already works as if all paths are relative w.r.t. to the restore target. This could be enhanced for saved absolute paths: In this case, allow to omit the restore target and use the saved absolute path.

Relevant matching issue for Restic


ImportError: cannot import name 'kibana'

I run elastalert.py in the elastalert source directory, but it fails.

+1

look
https://my.oschina.net/u/4262664/blog/3326907

Did you contact the plugin developer?

I tried the source code installation and encountered the same problem
Solved with pip installation

look
https://stackoverflow.com/questions/59014095/elastalert-deployment-failed

@wajika
Did you solve? Or unsolved

@wajika
Did you solve? Or unsolved

I haven't succeeded, I still don't understand why the prompt.

@wajika
What command are you executing in relation to ElastAlert before the error occurs?

@wajika

OS version you are using
Python version you are using
Commands executed during ElastAlert installation

@wajika
ImportError: cannot import name kibana #2417

I'm not sorry about this anymore. goodbye

Please close it already.

Sorry, I'm working on other projects now

I'm sorry it didn't help


Do not double encrypt a protected password dialog text field

When passing in an already encrypted value to a protected field in some back end methods, there was an issue where it would encrypt it again. Whoops.
Related to https://bugzilla.redhat.com/show_bug.cgi?id=1602883
@miq-bot assign @gmcculloug
/cc @mkanoor

@lfu Please review this is needed for your BZ to prevent double encryption

Hammer backport details:
$ git log -1
commit 0a94e25b14fd8534e45b32518d1e841a17ef44a4
Author: Greg McCullough<EMAIL_ADDRESS>Date:   Fri Sep 28 12:04:02 2018 -0400

    Merge pull request #18031 from eclarizio/BZ1602883-Related

    Do not double encrypt a protected password dialog text field

    (cherry picked from commit 27c9fe355f36d372ec30ccd0eb26495421db1aa8)

    https://bugzilla.redhat.com/show_bug.cgi?id=1602883


New Command: Add-DbaAgReplica

Command to add replicas to the Availability Group, this one will assume the AG is already created.
The initial thought is to have the New AG-Group command handle adding the initial primary replica (just initial). It will all be based and updated on how SMO handles it.
Original issue: #1712

done a rama


Migrate to unified core

There is currently no track for when building without --unified-core will be obsolete, but since it is deprecated, it is worth taking a look at building Sodalite with this flag. Historically this caused problems with Sodalite and hasn't been tried since, but its worth looking at now.
Related:

https://github.com/coreos/rpm-ostree/issues/729
https://github.com/fedora-silverblue/issue-tracker/issues/333

It seems to work properly. Can't see any problems in the OS itself. 🤔

This is now vital for Sodalite 5 (f38) to build, otherwise it just segfaults. build.sh has been modified in 4dade7bac0b4e6c5bf448d7de8dfcc4f1a53a903 to use --unified-core by default, with --ex-no-unified-core added to disable building with this.


Links are referring to the wrong page

Under the section For more information about running N-tier applications on Azure:
The links are messed up together:
This link: Run Windows VMs for an N-tier application >> leads to Windows N-tier application on Azure with SQL Server
This link: Windows N-tier application on Azure with SQL Server >> leads to Linux N-tier application in Azure with Apache Cassandra
This link:

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

ID: 5e5ad897-88ad-5298-b9ff-4d988af52466
Version Independent ID: 8a3904d9-17ed-0ac0-f006-6997095c86bb
Content: N-tier architecture style - Azure Application Architecture Guide
Content Source: docs/guide/architecture-styles/n-tier.md
Service: architecture-center
Sub-service: cloud-fundamentals
GitHub Login: @adamboeglin
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#235164


resolve an issue identified by cppcheck:

[channels/urbdrc/client/libusb/libusb_udevice.c:1666] -> [channels/urbdrc/client/libusb/libusb_udevice.c:1661]: (warning) Either the condition 'request' is redundant or there is possible null pointer dereference: request.

@freerdp-bot test

@freerdp-bot I know it is monday, but could you test nontheless?


ggplot2() crashes R after using lgb.cv() / lgb.train()

R crashes on me whenever I attempt to do a simple geom_point() plot after having trained a lgbm model. Details below.  Note that ggplot(iris, aes(x = Sepal.Length, y = Petal.Length)) works just fine, but ggplot(iris, aes(x = Sepal.Length, y = Petal.Length))+geom_point() causes the crash. Not sure if this issue belongs here or in ggplot2 issues, but I use ggplot2 a lot and I've only seen this behavior in the presence of lightgbm.
Thanks!
Environment info
Operating System: OS X 10.13.6
CPU: 3.1 GHz Intel Core i7
R version: 3.5.1
Error message
R Session Aborted. R encountered a fatal error.

Reproducible example
library(lightgbm)  # version 1.2.1
library(ggplot2)  # version 3.0.0

data(agaricus.train, package='lightgbm')
train <- agaricus.train
dtrain <- lgb.Dataset(train$data, label=train$label)
params <- list(objective="regression", metric="l2")
model <- lgb.cv(params, dtrain, 10, nfold=5, min_data=1, learning_rate=1, early_stopping_rounds=10)

# Attempt simple plot
ggplot(iris, aes(x = Sepal.Length, y = Petal.Length))+geom_point()

Note that placing the ggplot() call at the top results in the same behavior (R crashing). That is,
library(lightgbm)  # version 1.2.1
library(ggplot2)  # version 3.0.0

# Attempt simple plot
ggplot(iris, aes(x = Sepal.Length, y = Petal.Length))+geom_point()

# Simple lightgbm snippet
data(agaricus.train, package='lightgbm')
train <- agaricus.train
dtrain <- lgb.Dataset(train$data, label=train$label)
params <- list(objective="regression", metric="l2")
model <- lgb.cv(params, dtrain, 10, nfold=5, min_data=1, learning_rate=1, early_stopping_rounds=10)

also crashes R

UPDATE
I initially installed lightgbm using Apple Clang, following the instructions here.  After re-installing using gcc7, the above code works as I'd expect it to.

Glad that you've managed to make LightGBM work.
I suppose this is connected to the conflict between shared libraries.
Possibly related issues: #1444, Question 10 in our FAQ.


Fixes an issue with the Image_lib class not clearing properties completely

Encountered an issue in the Image_lib class when processing multiple images: Despite calling the clear() method between image operations, some settings were being persisted between calls, namely width, height and create_thumb. This update adds them to the list of properties reset in the clear() method.

Can this be merged?

It looks ok to me. I can't test it tonight but I should be able to tomorrow. Also missing changelog item.

I tested the original issue and I am not having any issues with it not clearing. Am I missing something?
public function index()
{
	$this->load->library('image_lib');
	$this->_resize(250, 250);
	$this->image_lib->clear();
	$this->_resize(150, 150);
}

private function _resize($width = 75, $height = 75)
{
	$path = FCPATH.'/img/';
	$config['image_library'] = 'gd2';
	$config['source_image']	= $path.'1.jpg';
	$config['new_image']	= $path.'mypic-'.$height.'x'.$width.'.jpg';
	$config['create_thumb'] = FALSE;
	$config['maintain_ratio'] = TRUE;
	$config['width']	 = $width;
	$config['height']	= $height;

	$this->image_lib->initialize($config);
	if ( ! $this->image_lib->resize())
	{
		echo $this->image_lib->display_errors().'
';
	}
}

This gives me two new images with the size I specified.

Hi Eric,
I also found this issue (I think it's a duplicate of this one)...
https://github.com/EllisLab/CodeIgniter/pull/226
This pull links to these issues: https://github.com/EllisLab/CodeIgniter/issues/157 and https://github.com/EllisLab/CodeIgniter/issues/174

Hi Eric,
The issue occurs when only one dimension is specified. I don't have my original test-case to hand, but something like the following should exhibit the issue:
public function index()
{
    $this->load->library('image_lib');
    $this->_resize(250, "1");
    $this->image_lib->clear();
    $this->_resize(250, "2");
}

private function _resize($width = 75, $name="1")
{
    $path = FCPATH.'/img/';
    $config['image_library'] = 'gd2';
    $config['source_image'] = $path.'1.jpg';
    $config['new_image']    = $path.'mypic-'.$name.'.jpg';
    $config['create_thumb'] = FALSE;
    $config['maintain_ratio'] = TRUE;
    $config['width']     = $width;

    $this->image_lib->initialize($config);
    if ( ! $this->image_lib->resize())
    {
        echo $this->image_lib->display_errors().'
';
    }
}

Despite performing the same resize operation on the same file, the two resulting files are different dimensions (in this instance height) because the internal variables aren't fully reset between function calls. This update makes both files come out like the first does currently. (Although the second may be the 'more correct' result of the operation when maintain_ratio is set to true I feel that's a separate issue)

Thanks guys for the clarification. :thumbsup:

Hi Eric,
Take a look at this. Is this a better fix? https://github.com/michaeljdennis/CodeIgniter/commit/cb07a322bee5c5b0a551ab959c7475a1a702ad03

Sorry I see you also merged the other patches. Thanks Eric!


Updated authType to authtype

Options appear to be case sensitive - updating readme.

I think we'll just change the code to not be case sensitive :)  good catch


[Segment Replication] Allocation changes to distribute primaries - Benchmark & document improvements using opensearch-benchmark.

https://github.com/opensearch-project/OpenSearch/pull/6017 Introduced a new weight factor to attempt to evenly distribute primary shards.  We need to document this change including benchmarks to 1) find a reasonable default for SR enabled indices and 2) prove when using the setting is beneficial.
Related https://github.com/opensearch-project/documentation-website/issues/2663

Looking into this.

Copied @shwetathareja's comment from PR https://github.com/opensearch-project/OpenSearch/pull/6325

My initial thoughts:

Have you looked into adding an AllocationConstraint similar to isIndexShardsPerNodeBreached which essentially adds constraint to ensure each node shouldn't have more than avg. no.of shards per index even if a node has overall less shards compared to other nodes. This helps in preventing un-necessary rebalances later. More details are here - https://github.com/opensearch-project/OpenSearch/issues/487
I feel you can simply add a constraint for segrep indices to ensure a node shouldn't have more than avg. no. of expected primaries for an index. Lets say it is 5 node cluster and segrep index has 5 primaries + 2 replicas. So no node should have more than 1 primary. This wouldn't require coming up with magic value for weight factor. Later, we can evaluate if we want to extend this to balancing sum of primaries across all indices across all nodes as well. e.g. 1 segrep index has 3 primaries while other has 2 primaries and it is 5 node cluster, then each node shouldn't have more than 1 primary across indices as well.

@shwetathareja's comment from PR #6325

My initial thoughts:

Have you looked into adding an AllocationConstraint similar to isIndexShardsPerNodeBreached which essentially adds constraint to ensure each node shouldn't have more than avg. no.of shards per index even if a node has overall less shards compared to other nodes. This helps in preventing un-necessary rebalances later. More details are here - #487
I feel you can simply add a constraint for segrep indices to ensure a node shouldn't have more than avg. no. of expected primaries for an index. Lets say it is 5 node cluster and segrep index has 5 primaries + 2 replicas. So no node should have more than 1 primary. This wouldn't require coming up with magic value for weight factor. Later, we can evaluate if we want to extend this to balancing sum of primaries across all indices across all nodes as well. e.g. 1 segrep index has 3 primaries while other has 2 primaries and it is 5 node cluster, then each node shouldn't have more than 1 primary across indices as well.

Yes, I think having a constraint (here, avg primary shard count/node) supplements the existing weight function and provides more flexibility and get rid of primary balancing factor. Also, it will be more useful in solving uneven primary shard distribution from failover and the balancing logic which works at index level.

Later, we can evaluate if we want to extend this to balancing sum of primaries across all indices across all nodes as well. e.g. 1 segrep index has 3 primaries while other has 2 primaries and it is 5 node cluster, then each node shouldn't have more than 1 primary across indices as well.

Can you please share more details around this from balancing perspective ?
The existing balancer performs balancing withing single index i.e. it balance shards of one index across all nodes, repeat for others. We can introduce a new balancing logic which works across all indices and across all nodes. A simple algorithm can be:
Constants
Allocation constraint weight when node contains more than avg primary shards, lets say Wa = 1000
Threshold, say t = 2 * Wa. When node weight differ more than threshold, it is considered unbalanced. We use twice of Wa to avoid repeatitive shard movements.
Steps

Calculate weight on all nodes using weight with constraint above. E.g. 2 nodes, say N1, N2 and 5 shards. N1 contains 2 shard, N2 contains 3. With avg shard count/ node as 2.5, N1 will have 0 weight while N2 have 1000.
Sort nodes based on constraint weight.
while(true)

Pick light node and heavy node
If weight diff > t, move random primary from heavy -> light node

update weight of both nodes
sort and continue // repeat to attain more balance

else break // no more unbalanced

With above algo, we can use below approaches for solving the primary shard allocation.
Approach 1.
Have additional round of balancing based on avg primary shard/node constraint. First balance on individual indices (existing) and then balance across all nodes.
Pros.

Have better per index shard distribution
Cons.
Additional relocations from second round.
Problems such as

Both round negating effect of other.

Example, there are 2 Nodes, say N1, N2, 3 indices (I1, I2, I3) with total 4 primary shards.
I1 has 2 primary I1P1, I1P2; while I2, I3 have one primary I2P1, I3P1 respectively
N1 -> I1P1, I1P2 while N2 contains I2P1, I3P1.
Index level balancing moves I1P1 from N1 to N2. Node level balancing moves it back

Endless loop of balancing actions.

Approach 2.
Balancer performs balancing across all indices and nodes once using algorithm above for segrep specific shards.
Pros.

Minimal shard relocations.

Cons.

Chances of skewed per index shard distribution that cause hot spot.

Based on above, approach 1 seems better as approach 2 can have problem of hot spots.

Thanks @dreamer-89 for exploring the AllocationConstraint approach.
Couple of comments on different approaches
Approach 1

While calculating extra weight, the current logic can result in -ve weight as well
int extraPrimaryCount = (int)(node.numPrimaryShards(index) - balancer.avgPrimaryShardsPerNode(index));
Instead you can choose to not add extra weight unless the constraint is breached.
Why do you think there will be extra re-balances. This will ensure primaries are balanced across shards even though the over all shard count is lower on that node compared to others.
Yes agreed, we will need to define different constraint (or same constraint handling both conditions) for balancing overall primaries across all indices if desired which you have discussed in Approach 2 & 3.
Yes, you are right, if i remember right re-balancing was not taking care of constraint. We can evolve the Allocation algorithm for re-balances as well. I will check that part of the code again.

Approach 2
As you mentioned, it is only balancing across all indices and wont be effective per index and that would be important from log analytics customer perspective where only the latest index will be taking writes after rollover.
Approach 3
For segrep, I feel this would certainly add value considering resource usage across primary and replica is very skewed. I think we need to re-look at the rebalancing algo to tune the constraint calculation logic and prevent un-necessary movements.
Overall, I am aligned to start with per index primaries to be evenly distributed and iterate over to make it evenly distribute across indices primaries as well later.

Thank you so much @shwetathareja for the feedback!  As you mentioned, the actual implementation uses constraints based weight calculation. PR #6422 (request you to review as well).

Approach 1

While calculating extra weight, the current logic can result in -ve weight as well
int extraPrimaryCount = (int)(node.numPrimaryShards(index) - balancer.avgPrimaryShardsPerNode(index));
Instead you can choose to not add extra weight unless the constraint is breached.
Why do you think there will be extra re-balances. This will ensure primaries are balanced across shards even though the over all shard count is lower on that node compared to others.
Yes agreed, we will need to define different constraint (or same constraint handling both conditions) for balancing overall primaries across all indices if desired which you have discussed in Approach 2 & 3.
Yes, you are right, if i remember right re-balancing was not taking care of constraint. We can evolve the Allocation algorithm for re-balances as well. I will check that part of the code again.

The extraPrimaryCount calculation is guarded by if condition so it should not result in negative weight contribution. This logic was just for POC to verify if it works.

if(node.numPrimaryShards(index) - balancer.avgPrimaryShardsPerNode(index) > 0)

An extra relocation is needed to attain primary balance. This is done by first offloading extra primary on heavier node due to breached avg. primary shard count per node constraint; which may result in target node to have extra shard count and violating the threshold based of shard counts; needing another relocation (probably a replica shard).
During rebalancing, the primaries are relocated first (link - from PR above) from heavier to light node. This is needed to converge delta b/w heavy & light node and to prevent never ending shard relocations. Once primary is moved, it may result shard count imbalance (weight diff higher than threshold default 1.0f) which results in one more shard relocation. Consider this with example below, there are 3 nodes with one index (3 shards, 1 replica).
State 1

Node 1
Node 2
Node 3

P1
P2
P3

R3
R1
R2

Node 3 is restarted, coordinator promotes R3 as primary resulting in below state. Node 3 joins back cluster containing R3, R2
State 2

Node 1
Node 2
Node 3

P1
P2
R3

P3
R1
R2

Node 1 breaches average primary shard count per node constraint 2 primary shards > 1 allowed average primary shards, thus rebalancer moves P1 from Node 1 -> Node 3 (and not Node 2 because 1) Not allowed due to (primary count diff 2) SameShardAllocator allocation decider filter). This results in below state
State 3

Node 1
Node 2
Node 3

P2
R3

P3
R1
R2

P1

Node 3 now have more number of shards which still breaches 1.0f default threshold. Rebalancer moves R2 back to Node 1 resulting in eventual balance. If fine tune balance is not desired, a higher threshold can be set which stops at step 3 above.
State 4

Node 1
Node 2
Node 3

P3
P2
P1

R2
R1
R3

Yes, let's continue disucussion here (and on PR) and come up use cases where global balancing is necessary.
Yes, rebalancing doesn't use any constraint today. With PR, I added the average primary shard count based constraint to be used during allocation and rebalancing.

Approach 2
As you mentioned, it is only balancing across all indices and wont be effective per index and that would be important from log analytics customer perspective where only the latest index will be taking writes after rollover.

👍

Approach 3
For segrep, I feel this would certainly add value considering resource usage across primary and replica is very skewed. I think we need to re-look at the rebalancing algo to tune the constraint calculation logic and prevent un-necessary movements.

Let's continue discussion here on use cases, which warrants global level balancing.

Overall, I am aligned to start with per index primaries to be evenly distributed and later iterate over to make it evenly distribute across indices primaries as well.

Thank you! Yes, per index primary balancing is implemented in https://github.com/opensearch-project/OpenSearch/pull/6422; we can implement global balancing based on discussion here.

Great discussion here, @dreamer-89 and @shwetathareja. This is a tricky, but important problem to solve. Happy to see the original Constraint Based Shard Allocation idea continue to find utility over the years!
I think we are on the right track here. I like the option of adding two constraints, one for "primaries per index per node", and another one for "total primary shards per node".
...

Existing constraints are predicates which return yes/no based on whether node has breached constraint or not. It would be better if constraint returns a degree by which a constraint is breached

I would strongly suggest thinking hard about how to keep the shard weight algorithm as simple as possible. It is tempting to add more capabilities, but it quickly becomes exponentially complex to reason and debug shard allocation in a production cluster. This was why, in the original impl., I had made each constraint add a fixed high value weight, and modeled constraints as boolean predicates.
As we add multiple constraints, there are no clear answers to whether breach of a particular constraint, is worse than the breach of a different constraint. (e.g. is it worse to breach the primariesPerIndexPerNode constraint, or totalPrimariesPerNode constraint?)
If only a single primary had recoveries, the former can be bad. If multiple primaries have recoveries, and target shard for 2 different indexes is on the same target node, the latter can be worse.
The point is, both are bad, and engineering around which is worse adds complexity with diminishing returns.
...

Consider this with an example, with avg primary shards count per node as 2 and two contender nodes (N1, N2) where N1 contains 3 primary shards (breach threshold by 1) while N2 contains 5 primary shards (breach threshold by 3), here N2 should not be preferred.

Constraint framework today is simple - it adds numConstraintsBreached * CONSTRAINT_WEIGHT to the weight returned by default weight function. In the example above, N2 will already have a high value from default weight function. So even with the same CONSTRAINT_WEIGHT values, it will not be preferred.
That is the central idea. Let a simple default weight function do its work. Then all eligible nodes with no constraints breached are better than ones with 1 constraint breached, who are better than nodes with 2 constraints breached and so on..
This works in tandem with the "Allocation Decider" Framework; which already rules out nodes which should not even be considered for allocation or rebalance. Deciders filter out ineligible nodes. Constraints deprioritize less preferred nodes.
Finally, I think it makes sense to extend the framework to handle rebalances. I did play around with it at the time, but threw it away, since allocation was the only problem we were solving then. Looks like now is a good time to add it.
If you add constraint handling to rebalances, would it take care of the extra rebalances you pointed out @dreamer-89 ?

Re: imbalances that emerge from replica -> primary promotions.. I think you need the pri-rep swap capability to truly be able to solve it. There is no other way (I know of), to solve that problem for a 2 node cluster.

Thank you @vigyasharma for the feedback.

Consider this with an example, with avg primary shards count per node as 2 and two contender nodes (N1, N2) where N1 contains 3 primary shards (breach threshold by 1) while N2 contains 5 primary shards (breach threshold by 3), here N2 should not be preferred.

Constraint framework today is simple - it adds numConstraintsBreached * CONSTRAINT_WEIGHT to the weight returned by default weight function. In the example above, N2 will already have a high value from default weight function. So even with the same CONSTRAINT_WEIGHT values, it will not be preferred.

Sorry, I was not clear enough in the example. I meant to have a state where N1, N2 have unequal primary shard count but still balanced on weight calculation. Updated the example and copy pasting below as well. I agree, let's keep the constraint as predicate and not change until it is really needed.

Existing constraints are predicates which return yes/no based on whether node has breached constraint or not. It would be better if constraint returns a degree by which a constraint was breached. The quantity can then be incorporated into node's weight calculation. Consider this with example of 4 node (N1, N2, N3, N4) and 1 index (8 shard, 1 replica) with 2 as C1 value. Nodes N3, N4 are excluded from allocation. Node N1 contains 3 primary 5 replica (breach primary threshold by 1) while Node N2 contains 5 primary 3 replica (breach threshold by 3). Here, as both nodes have unequal primary and breaching C1 and also they are balanced (equal weight because all shards belong to same index and both nodes have same number of shards). For shard allocation (increase replica count) and rebalancing, both nodes can be picked as target while it is prefera

That is the central idea. Let a simple default weight function do its work. Then all eligible nodes with no constraints breached are better than ones with 1 constraint breached, who are better than nodes with 2 constraints breached and so on..
This works in tandem with the "Allocation Decider" Framework; which already rules out nodes which should not even be considered for allocation or rebalance. Deciders filter out ineligible nodes. Constraints deprioritize less preferred nodes.

Yes, I agree. Also, defining priority of multiple constraint will be difficult and need more brainstorming.

Finally, I think it makes sense to extend the framework to handle rebalances. I did play around with it at the time, but threw it away, since allocation was the only problem we were solving then. Looks like now is a good time to add it.
If you add constraint handling to rebalances, would it take care of the extra rebalances you pointed out @dreamer-89 ?

Yes, I added the constraint in weight calculation during rebalancing. Sorry, I was not clear. With extra rebalances - I meant extra relocations compared to existing world where primary and replicas are equal. With proposal here, we need to move primary to attain primary balance followed by another relocation such that weight diff b/w any two nodes is within threshold (default 1.0f).


naked truth

We have written the needed data into your clipboard because it was too large to send. Please paste.

We have written the needed data into your clipboard because it was too large to send. Please paste.

what do you mean by "naked truth"? 😦


Add International Mobile Equipment Identity (IMEI)

Removed from other PR #574 and create a new PR for Provider IMEI

I @acfreitas, thanks a lot for your contribution!
IMEI generation/validation uses Luhn check algorithm: I suggest to use the  src/Faker/Calculator/Luhn calcultor instead.
Unit tests should be appreciated too!

@ronanguilloux, I created the tests and edited the code to use src/Faker/Calculator/Luhn. Thanks for your suggestion.

Merged using the command line in 54e105fedd5715fb8070afb88334f212b6f2a84a. Thanks!


Rename SymfonyApp to Functional

To keep with best practices SymfonyApp should be renamed Functional and AppKernel should not have any namespace.

Closed via #261


Incognito tabs not maintaining breakpoints

Quite sorry if this is the wrong place for this, not sure where to report this as a Chrome dev tools bug.
For incognito tabs, breakpoints are not saved when you close and reopen them. Incognito mode is quite helpful for developers as it saves us having to clear cookies after each look at the page, but the fact that it removes break points anytime you close the tab is a major impediment.
This may be by design, in which case I would like to hear the argument for this "feature." Thank you!

If the bug is not specific to the application-shell project, could you file a new devtools bug at crbug.com and close this one please? :) It sounds like it's unrelated but if I've misread do let us know.


GOSA6 - Contact us form

Description
GeeksforGeeks student chapter contacts us section. Create a form with name, email, phone number, and message to the student chapter and update it to the firebase in the contact_us field.

I can work on it

can work on it. assign it to me

Please assign this to me

@ankittripathi31 you can work on this issue

Up for this one

This issue is free now!

I can do it

@rithik-dev you can work on this issue

@rithik-dev Thank you for the contribution we have successfully merged your Pull request.
You have received 10 points for the contribution keep it up


Typescript kit not working after installing aurelia-dialog 0.5.4

After downloading the typescript kit and adding in aurelia-dialog 0.5.4, the kit doesn't fire up correctly anymore. The aurelia-bootstrapper is not being loaded; even if I don't use the aurelia-dialog in the configuration setup. I tried the es-2016 kit and it is working fine with aurelia-dialog 0.5.4.

Can you give an idea of any errors you are encountering?

I don't see any errors from the browser console and dos prompt. I use http-server for the web server and after the loading of the config.js and favorite icon, nothing else loads. It looks like the Aurelia-bootstrapper is never called.

@dli04 I've just confirmed using the steps above that this is working as expected in the TypeScript skeleton.  Are you sure you have the latest of all of the releases?  Closing for now, please join our gitter channel if you need additional help.  I know that the TypeScript compiler will fail if you don't have the .d.ts file but that is distributed properly at the moment.

Thanks. I've downloaded the typescript skeleton and is now working properly.
However, the typescript kit from the http://aurelia.io/docs.html#/aurelia/framework/1.0.0-beta.1.1.2/doc/article/getting-started still doesn't work for me and I'm giving up on it. I did jspm clean and jspm update multiple times and below was as far as the loading could get to. No errors pop up in the shell or browser console.
shell>
http-server -o -p8091
Starting up http-server, serving ./


Modify some fees in realistic configs

Change the snark worker, account creation, and transaction fees in the realistic configs, per the document Finalize default Fees in Notion.
The realistic configs are imported by testnet_postake_medium_curves, exclusively, so these new values will be used for the upcoming testnet.
Create a new config, account_creation_fee/low.mlh and use it in dev, which would otherwise use the new value in realistic.
Closes #7916.

!approved-for-mainnet


Which n-best decoding algorithm do you use?

Are there any paper for reference?

It is hard to explain, but you can refer my talk http://jaylab.cn/papers/201811WestlakeUniv.pdf at Page 20, 21 which simply shows the algorithm.


Help out a dummie?

Hello guys,
Was wondering if you could provide a screencast/guide on how to setup duckling as a server, adding new entities, etc; allá wit.ai style?
I've recorded screencasts before and more than happy to record one for everyone's benefit as long as someone with a bette grasp of the project feels free to help me out 😄

Hey @mariogintili,
We don't provide this right now. If somebody can record screencasts that prove useful to the community, we might add pointers to those.
I'm happy to help regarding specific issues on spinning up a server running Duckling. To setup new dimensions, you can look at the commit history on how to do that. We can definitely do a better job regarding the documentation.
Closing this, feel free to reopen or open new tickets to address specific issues you run against. :)


Merge pull request #2 from BhekieRoots/My-First-Branch

My first main pull request

have managed to pulled from a branch


Flutter App Can't Be Scrolled While Mirroring With New MacOS 15 (Sequoia) Feature

Steps to reproduce

Use New Mirroring Feature From MacOS 15 and iOS 18
Open Built App
Try Scrolling Vertical With Mouse or Trackpad

Expected results
App can be scroll vertically
Actual results
https://github.com/user-attachments/assets/6fc218fc-7771-4aa2-b914-ff02afd7a14a
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Flutter is already up to date on channel stable
Flutter 3.24.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 2663184aa7 (8 days ago) • 2024-09-11 16:27:48 -0500
Engine • revision 36335019a8
Tools • Dart 3.5.3 • DevTools 2.37.3

App on video built with flutter 3.24.0

I verified  this with Google Pay in India, flutter apps are not able to scroll

This was initially reported in https://github.com/flutter/flutter/issues/153897 and has been fixed by https://github.com/flutter/engine/pull/55285. The fix is on the master channel.
Closing since this has already been fixed.
Thank you


build: slight updates/de-dups in setupcfg

small updates, deduplications, and sorting in setup.cfg

REbased to fix conflicts.

All good, merging.


Update/icon

Change icon and version

Codecov Report

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

@@           Coverage Diff           @@
##           master      #12   +/-   ##
=======================================
  Coverage   85.62%   85.62%
=======================================
  Files           3        3
  Lines         153      153
  Branches       46       46
=======================================
  Hits          131      131
  Misses         22       22

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 f7548b9...bcd6dc3. Read the comment docs.


Add images: Android Basics with Compose

https://developer.android.com/codelabs/basic-android-kotlin-compose-add-images?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-1-pathway-3%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-add-images#6
The issue is found on the 7th task of add images
There is a small mistake in the function call .
It is shown as:  modifier = modifier.fillMaxSize()
while the correct one would be modifier = Modifier.fillMaxSize()

Duplicate of #207

Hello @Osiris9999,
Thank you for reaching out to us.
It is a best practice to use the passed in Modifier argument in the root layout of the composable.
Instructions are updated and to be published


VQA: Limitations in questions and answers

I want my Finetuned VQA model to be able to answer questions is was not trained on before and similarly provides answers that does not exist in the original answer list (test json file answers in a list).
Is there a limitation to the kind of questions i can the model? If yes, how can I tweak the code to meet my needs?

Hi,
you need to modify the inference process of the VQA model.
do not use this to rank the candidate answers: https://github.com/zengyan-97/X-VLM/blob/master/models/model_vqa.py#L144
instead, you should make it a real generation. for example, you can refer to: https://github.com/zengyan-97/X-VLM/blob/master/models/model_captioning.py#L75

Traceback (most recent call last):
File "/home/czh/.pycharm_helpers/pydev/pydevd.py", line 1534, in _exec
pydev_imports.execfile(file, globals, locals)  # execute the script
File "/home/czh/.pycharm_helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
exec(compile(contents+"\n", file, 'exec'), glob, loc)
File "/home/czh/BLIP-main/Eval_VQA.py", line 261, in
main(args, config)
File "/home/czh/BLIP-main/Eval_VQA.py", line 180, in main
model.load_pretrained(ckpt, config, is_eval=True)
File "/home/czh/BLIP-main/models/XVLM/model_vqa.py", line 89, in load_pretrained
msg = self.load_state_dict(state_dict, strict=False)
File "/home/czh/.conda/envs/czh/lib/python3.9/site-packages/torch/nn/modules/module.py", line 2215, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for XVLM:
size mismatch for vision_encoder.layers.0.blocks.0.attn.relative_position_bias_table: copying a param with shape torch.Size([841, 4]) from checkpoint, the shape in current model is torch.Size([529, 4]).


[ownership] Convert a few small visitor methods to be const.

@swift-ci smoke test and merge

@swift-ci smoke test and merge

@swift-ci smoke test linux platform


not able to start the project

Please check your node version, nodejs version require 16.13.1

yes, it is same . i have start the project by my  own now i got this issue that is didn't see the list of coins:


Fix logout

This PR fixes the logout functionality, related to:
https://github.com/ueberauth/ueberauth_example/issues/49
https://github.com/ueberauth/ueberauth_example/issues/29

Use a form to include all the required data and action to do a delete
Update the delete function on the controller to use clear_session instead of configure_session [1]

Also, updates config/test  adding username and password fields that needed to be passed to the GitHub Actions container for testing.
[1] https://stackoverflow.com/questions/42910224/put-flash-not-works-with-configure-sessiondrop-true

Thank you thank you @ramortegui :pray:


Duplicate class org.webrtc.AddIceObserver in flutter_webrtc and com.amazonaws:ivs-broadcast:1.9.0:stages@aar

I've encountered a problem with duplicate classes when using the flutter_webrtc and com.amazonaws:ivs-broadcast:1.9.0:stages@aar libraries together in my Flutter project.
In my pubspec.yaml I have:
flutter_webrtc: ^0.9.33
And in my build.gradle for Android, I have:
implementation('com.amazonaws:ivs-broadcast:1.9.0:stages@aar')
When I attempt to build, I encounter the following error:
Duplicate class org.webrtc.AddIceObserver found in modules jetified-android-104.5112.06-runtime (com.github.webrtc-sdk:android:104.5112.06) and jetified-ivs-broadcast-1.9-stages.0-stages-runtime (com.amazonaws:ivs-broadcast:1.9.0)
I've tried to exclude the org.webrtc module from ivs-broadcast library in build.gradle, but the error persists.
:implementation('com.amazonaws:ivs-broadcast:1.9.0:stages@aar'){
exclude group: 'org.webrtc', module: 'webrtc'
}
Could you please provide any guidance or potential solutions to address this issue?

Hi @weekend8394, sorry for the late response. We don't currently have a workaround for duplicate WebRTC classes, but we are planning to try to fix this issue in the future. Until that work is done, for now the only solution is to use only one of the two libraries. Sorry for the inconvenience.

This was fixed a few months ago in version 1.14, and has stayed the same (fix is there) in more recent releases including the 1.16.0 we just published today.
You can now use the IVS Broadcast SDK in the same app with other SDKs which use Google's WebRTC library.

Are the problem is solved ?
I have the same issue and I have resolved. Just exclude the webrtc on jitsi meet .

Are the problem is solved ? I have the same issue and I have resolved. Just exclude the webrtc on jitsi meet .

Later, we suspended this function first , so we didn’t use it for the time being , LOL

The naming conflict was solved in IVS Broadcast SDK 1.14
Since that version, you can use the IVS Broadcast SDK + any other SDK which uses Google's WebRTC such as Live Kit


Is it possible check that Kafka client is successfully connected?

For health check status checking purposes for example?

Just checking that the client is connected isn't really enough to say that it's healthy, but there are events that you can listen to in order to know the state of your consumer. https://kafka.js.org/docs/instrumentation-events#a-name-consumer-a-consumer
What we do for our applications is to check if the consumer has done a heartbeat within the configured sessionTimeout. However, this means that the consumer is considered "unhealthy" during rebalances, which happen during deploys, among other things. This could be considered healthy or unhealthy, depending on what the purpose of your healthcheck is, but you can get the state of the group if needed. Something like this:
const SESSION_TIMEOUT = 30000

const consumer = kafka.consumer({
  groupId,
  sessionTimeout: SESSION_TIMEOUT
})

const { HEARTBEAT } = consumer.events
let lastHeartbeat
consumer.on(HEARTBEAT, ({ timestamp }) => lastHeartbeat = timestamp)

const isHealthy = async () => {
  const hasHeartbeated = Date.now() - lastHeartbeat < SESSION_TIMEOUT

  // Consumer has heartbeat within the session timeout,
  // so it is healthy
  if (hasHeartbeated) {
    return true
  }

  // Consumer has not heartbeat, but maybe it's because the group is currently rebalancing
  try {
    const { state } = await consumer.describeGroup()

    return ['CompletingRebalance', 'PreparingRebalance'].includes(state)
  }
}

Now, I'm not sure I would recommend relying on this kind of thing for alerting, but it can be good for an at-a-glance indication of health. One problem with this is that if your consumers are always rebalancing, because they're crashing and restarting over and over, this would still report healthy. But if we don't have that exception, it'll instead report unhealthy when you are deploying, which can be annoying if it triggers alerts.
My recommendation would be to base alerting primarily on metrics, like queue depth and such.

@Nevon Thanks for explanations! Sounds very useful.
This check just needed as very basic health check for an internal dashboard.
More complex health checks will be done with Kafka JMX exporter on the Kafka server side.

@Nevon Above you said,

One problem with this is that if your consumers are always rebalancing, because they're crashing and restarting over and over, this would still report healthy.

How so? I don't think this will return healthy in such cases.

How so? I don't think this will return healthy in such cases.

It will because the health check is returning true if the state is CompletingRebalance or PreparingRebalance, so even if it is rebalancing over and over, it will still be considered healthy.

Got it.
That can be avoided by keeping track of firstHeartbeat = true/false and then doing something like,
return firstHeartbeat && ['CompletingRebalance', 'PreparingRebalance'].includes(state)

Right?

I'm not sure what you mean by firstHeartbeat, but assuming that it is just a record of the consumer having heartbeat at some point, it doesn't solve the fundamental problem.
One workaround could be to keep track of how long the consumer has been rebalancing, and then tuning a limit for that to how long your deployments usually take, but again, that's just papering over the fundamental problem which is that this is not the right way to monitor the health of a Kafka consumer. Doing that will just mean that your dashboard is lying to you for X minutes until it finally gives up and admits that there is a problem.
The real solution is to monitor your consumer based on the work it is supposed to be doing. If it is not consuming messages fast enough from the queue, it is not healthy. If it is consuming at the rate you need it to, it is healthy. Simple as that.

Got it. Thanks.
I was using firstHeartbeat as keeping track of when it becomes healthy for first time. But yes, it doesn't solve problem as it can go in crash loop (PreparingRebalance/CompletingRebalance) after becoming healthy.

It seems like by running kafka.consumer(..., you are connecting another consumer to the group.  Is there a way to check without connecting an additional consumer?

You don't need to create a new consumer instance in your healthcheck. Just pass in a reference to your existing consumer instance and use that.

Can we use this concept o

Just checking that the client is connected isn't really enough to say that it's healthy, but there are events that you can listen to in order to know the state of your consumer. https://kafka.js.org/docs/instrumentation-events#a-name-consumer-a-consumer
What we do for our applications is to check if the consumer has done a heartbeat within the configured sessionTimeout. However, this means that the consumer is considered "unhealthy" during rebalances, which happen during deploys, among other things. This could be considered healthy or unhealthy, depending on what the purpose of your healthcheck is, but you can get the state of the group if needed. Something like this:
const SESSION_TIMEOUT = 30000

const consumer = kafka.consumer({
  groupId,
  sessionTimeout: SESSION_TIMEOUT
})

const { HEARTBEAT } = consumer.events
let lastHeartbeat
consumer.on(HEARTBEAT, ({ timestamp }) => lastHeartbeat = timestamp)

const isHealthy = async () => {
  // Consumer has heartbeat within the session timeout,
  // so it is healthy
  if (Date.now() - lastHeartbeat < SESSION_TIMEOUT) {
    return true
  }

  // Consumer has not heartbeat, but maybe it's because the group is currently rebalancing
  try {
    const { state } = await consumer.describeGroup()

    return ['CompletingRebalance', 'PreparingRebalance'].includes(state)
  } catch () {
    return false
  }
}

Now, I'm not sure I would recommend relying on this kind of thing for alerting, but it can be good for an at-a-glance indication of health. One problem with this is that if your consumers are always rebalancing, because they're crashing and restarting over and over, this would still report healthy. But if we don't have that exception, it'll instead report unhealthy when you are deploying, which can be annoying if it triggers alerts.
My recommendation would be to base alerting primarily on metrics, like queue depth and such.

Would it be sound to use this concept of healthiness to the setup the corresponding healthiness probe for a consumer running on the top of kubernetes (let's take into account the fact that, at deploy time, we can ask kubernetes to wait some time before checking healthiness probes, so that all the transient rebalancing events do not interfere with the healthiness of a consumer).
Other approaches that we have considered consist of:

Using a specific topic to check the consumer's ability to dequeue: part of the application, dedicated to the healthiness check, might enqueue a message and then try to dequeue it. If this end2end test at runtime breaks, the consumer is considered unhealthy.
Listening for STOP, DISCONNECT and CRASH (and maybe REQUEST_TIMEOUT) events to decide whether the consumer is healthy or not.

Can we use this concept o

Just checking that the client is connected isn't really enough to say that it's healthy, but there are events that you can listen to in order to know the state of your consumer. https://kafka.js.org/docs/instrumentation-events#a-name-consumer-a-consumer
What we do for our applications is to check if the consumer has done a heartbeat within the configured sessionTimeout. However, this means that the consumer is considered "unhealthy" during rebalances, which happen during deploys, among other things. This could be considered healthy or unhealthy, depending on what the purpose of your healthcheck is, but you can get the state of the group if needed. Something like this:
const SESSION_TIMEOUT = 30000

const consumer = kafka.consumer({
  groupId,
  sessionTimeout: SESSION_TIMEOUT
})

const { HEARTBEAT } = consumer.events
let lastHeartbeat
consumer.on(HEARTBEAT, ({ timestamp }) => lastHeartbeat = timestamp)

const isHealthy = async () => {
  // Consumer has heartbeat within the session timeout,
  // so it is healthy
  if (Date.now() - lastHeartbeat < SESSION_TIMEOUT) {
    return true
  }

  // Consumer has not heartbeat, but maybe it's because the group is currently rebalancing
  try {
    const { state } = await consumer.describeGroup()

    return ['CompletingRebalance', 'PreparingRebalance'].includes(state)
  } catch () {
    return false
  }
}

Now, I'm not sure I would recommend relying on this kind of thing for alerting, but it can be good for an at-a-glance indication of health. One problem with this is that if your consumers are always rebalancing, because they're crashing and restarting over and over, this would still report healthy. But if we don't have that exception, it'll instead report unhealthy when you are deploying, which can be annoying if it triggers alerts.
My recommendation would be to base alerting primarily on metrics, like queue depth and such.

Would it be sound to use this concept of healthiness to the setup the corresponding healthiness probe for a consumer running on the top of kubernetes (let's take into account the fact that, at deploy time, we can ask kubernetes to wait some time before checking healthiness probes, so that all the transient rebalancing events do not interfere with the healthiness of a consumer).
Other approaches that we have considered consist of:

Using a specific topic to check the consumer's ability to dequeue: part of the application, dedicated to the healthiness check, might enqueue a message and then try to dequeue it. If this end2end test at runtime breaks, the consumer is considered unhealthy.
Listening for STOP, DISCONNECT and CRASH (and maybe REQUEST_TIMEOUT) events to decide whether the consumer is healthy or not.

If the consumer keeps failing on request timeouts, then the lastHeartbeat would be outdated right?
I.e we would not be able to send heartbeats and receive acknowledgments if we are getting requestTimeouts, correct?

The real solution is to monitor your consumer based on the work it is supposed to be doing. If it is not consuming messages fast enough from the queue, it is not healthy. If it is consuming at the rate you need it to, it is healthy. Simple as that.

I guess this won't be enough, because there could be a period of time when there is no message for that consumer based on the user usage. In such case, it will be considered unhealthy.


Update calicoctl role to manage kubecontrollersconfigurations

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 57a1933942ef8acd296ad52c8278b0a39f73ca1c
https://deploy-preview-3421--calico.netlify.com


fix: fix profile not saving

Description
Fix profile saving and editing issue in publish page.
Task Item
refs #3550 #3525
Screenshots

Coverage increased (+0.009%) to 53.244% when pulling 218eedb671f10edac5451db78444125384ccd82a on wenyluo/fixProfileSave into 9bd3ecd67772bda4ec508c92cff9e43d8d17af34 on master.

@VanyLaw can you state more about the root cause here? I thought  #3550 fixed the adding publish profile page failed to render, is this PR fixing something #3550 was missing, or a new regression after we take #3550 ?

OK, i get it, If i understand correctly, #3550 only fix the page is not rendering issue, but after 3550, the profile is not actually serialized to disk, which is fixed in this PR, right?

This one looks good and works for me, but as we can see, we have several issues related to publishing, just between the time windows of 1.0.1 to 1.0.2. @VanyLaw how can we improve and guarantee the overall quality of this part? Please re-think about this and create a plan for this.

Close this dup to #3556 have merged this.

OK, i get it, If i understand correctly, #3550 only fix the page is not rendering issue, but after 3550, the profile is not actually serialized to disk, which is fixed in this PR, right?

Yes, #3550 fix the render broken issue, but not exactly save it to settings file. And I will add more unit test and e2e test about the settings and deploy stuff later.


Add sequence post processor

Adds support for updated Llama 3 tokenizer.
Closes #739

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


crunchy tiger 0.0.1

Here it is!
Crunchy tiger is the first ever OMGX release - more of an alpha release process test - but a release nevertheless!
Onward and Upward!


[graphiql] incorrect Sec-WebSocket-Protocol when using graphql-ws OR a bug where the legacy graphql-transport-ws is being used despite configuration

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
In trying to diagnore a failing connection, I was looking closely at the Websocket info and noticed the "header" data
Sec-WebSocket-Protocol: graphql-transport-ws

Which is odd because I'm using the new graphql-ws config, so I'd expect this to read:
Sec-WebSocket-Protocol: graphql-ws

Here is my config:
Tried with graphiql version 2.0.9 AND 2.0.13
const fetcher = useMemo(
    () =>
      createGraphiQLFetcher({
        url,
        headers: {
          authorization: 'Basic dsfdsfdsfdsfsd=='
        },
        subscriptionUrl: url.replace('http', 'ws'), // also works for https->wss
        wsConnectionParams: {
          authorization: 'Basic dsfdsfdsfdsfsd=='
        },
        fetch: async (input, opts) => {
          const data = await fetch(input, opts);
          // only set query on success
          if (data.status === 200) {
            // do things
          } else {
            // dont do things
          }
          return data;
        }
      }),
    [onPlay, queryRef, url, variablesRef]
  );

<GraphiQLProvider
  fetcher={fetcher}
  storage={storage}
  // @Note in 2.x.x the defaultQuery controls what loads initially and doesn't
  // add new tabs which can sometimes happen if the new/old queries don't evaluate
  // equals
  defaultQuery={query}
  variables={JSON.stringify(variables, null, 2)}
>
  <InsideContext />
</GraphiQLProvider>;

Expected Behavior
As you can see I'm using subscriptionUrl and my understanding the default behavior in this case should be to use graphql-ws. In this case I'd expect the header information in the socket to reflect this, instead of reflecting the legacy protocol.
Additionally it does not appear that wsConnectionParams are being sent, either. But I suspect this is because the connection is closing first due to the mismatch in legacy client and graphql-ws server I'm using.
Steps To Reproduce
1. Create a new create react project or similar
2. Create a new fetcher using code snipped above
3. Inspect the WS network request using browser debug tools like this:

Module pattern

[ ] graphiql-umd
[ ] graphiql-esm
[ ] graphiql-commonjs

Environment
- GraphiQL Version: 2.0.9 AND 2.0.13
- OS: Windows
- Browser: Chrome
- Bundler:
- `react` Version: 18

"graphql": "^16.0.0",
"graphql-ws": "^5.11.2",

Anything else?
No response

Looking into this a little more, it does appear the graphql-ws library is being used based on this error source:

But the "header" information is still wrong...

Maybe this is a bug with graphql-ws?

Ok, so I managed to get this issue fixed but along the way there are a few bugs / observations to make note of

It seems that graphql-ws does indeed add Sec-WebSocket-Protocol: graphql-transport-ws - I'm not sure if this is expected but it sure is misleading... I'll open a bug over there.
The GraphiQL results pane (right panel) shows an obscure message which is a little misleading:

{
  "errors": [
    {
      "isTrusted": true
    }
  ]
}

I think what's happening is websocket error event has event.type === "error" so I think GraphiQL thinks its an error response from a graphQL server, and its grabbing the fist key, which is isTrusted, and displaying it. I've seen users asking about this in a few other stack overflows and such. I wonder if some better error handling could be implemented, or if there's a way to distinguish graphql errors from the websocket error events.
But perhaps the biggest issue giving me trouble was:

graphql-ws does not send authorization header if using a non-secure (so ws: instead of wss: ) connection. Which I guess makes sense but its not clear that's happening. A warning or something would be helpful for users debugging this. I think my previous testing was using wss so I didn't notice this. Of course in production wss is required but for local development, using ws://localhost AND still sending headers seems reasonable.

Hey @cramatt 👋
Regarding the Sec-WebSocket-Protocol header, graphq-ws specifies this to be graphql-transport-ws, see here. graphql-ws was the subprotocol used by the deprecated subscriptions-transport-ws package.
Regarding the error message you're seeing, events with type error should be handled properly. If the payload is not an Error, it should just be printed as it is. What's the exact payload you're receiving from the server that leads to the error message?
Regarding authorization, when using websockets it's common to send the authorization information with the payload of the connection_init event as setting HTTP headers on websocket connections is not supported by browsers. You're already correctly using the wsConnectionParams option when creating your fetcher for that purpose.

one solution i found with @amantham20 is to extend from the constructor

        webSocketImpl: class extends WebSocket {
            constructor(url: any, protocols: any) {
              super(url, 'graphql-ws');
            }
          },
        ```

closing this for now, as the outdated header is an issue for graphql-ws project

Hello,
I am getting below error. I am using the correct transport. What am I missing here?
[ WARN] (reactor-http-nio-2) [bb3bfcd9-1, L:/<IP_ADDRESS>:60817 - R:localhost/<IP_ADDRESS>:8081] The connection observed an error - io.netty.handler.codec.http.websocketx.WebSocketClientHandshakeException: Invalid subprotocol. Actual: graphql-transport-ws. Expected one of: null
io.netty.handler.codec.http.websocketx.WebSocketClientHandshakeException: Invalid subprotocol. Actual: graphql-transport-ws. Expected one of: null
using the below code
public static void main(String[] args) throws InterruptedException {

    WebSocketClient client = new ReactorNettyWebSocketClient();
    HttpHeaders headers = new HttpHeaders();
    headers.set("Sec-WebSocket-Protocol", "graphql-transport-ws");
    client.execute(
                    URI.create("ws://localhost:8081/subscriptions"),
                    headers,
                    session -> session.send(Flux.just(session.textMessage("{\"type\":\"connection_init\",\"payload\":{}}")))
                            .then(session.send(Flux.just(session.textMessage("{\"id\":\"66334929-b242-4d2c-a001-181e6e15e532\",\"type\":\"subscribe\",\"payload\":{\"query\":\"subscription {\\n  streamAccountsByCycleDayFromFlux(cycleDay: 100) {\\n    accountNumber\\n  }\\n}\"}}"))))
                            .thenMany(
                                    session.receive().map(WebSocketMessage::getPayloadAsText).
                                            doOnNext(System.out::println)

        )
        .then())
            .block(Duration.ofSeconds(10L));

}


add FLIP for storage API improvements in Cadence

This adds a FLIP proposing a change to the account storage API in Cadence to disambiguate the cases where values are not present in storage vs. when they have an unexpected type. The implementation of this change can be found in https://github.com/onflow/cadence/pull/1286.

For contributor use:

[X] Targeted PR against master branch
[X] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Updated relevant documentation
[X] Re-reviewed Files changed in the Github PR explorer
[X] Added appropriate labels

Seems very good proposal 👍


tqdm clear

What does this PR do?
Fixes # (issue).
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

outdated after new progress bar...


break on 'this' type in hasConstraintReferenceTo

fix proposal for #6592, //cc @ahejlsberg

CI build failed because of some random lint errors in files that were not even affected by this PR, looking into this:
src/compiler/types.ts[2497, 14]: missing semicolon
src/compiler/types.ts[2507, 14]: missing semicolon
src/compiler/types.ts[2498, 19]: missing whitespace
src/compiler/types.ts[2498, 20]: missing whitespace
src/compiler/types.ts[2499, 18]: missing whitespace
src/compiler/types.ts[2499, 19]: missing whitespace
src/compiler/types.ts[2500, 20]: missing whitespace
src/compiler/types.ts[2500, 21]: missing whitespace
src/compiler/types.ts[2501, 18]: missing whitespace
src/compiler/types.ts[2501, 19]: missing whitespace
src/compiler/types.ts[2502, 21]: missing whitespace
src/compiler/types.ts[2502, 22]: missing whitespace

pinging @JKillian: it seems that tslint@next has a peer dependency >=1.7.3 || >=1.7.0-dev.20151003 || >=1.8.0-dev which no longer works after version of TypeScript nightly builds was bumped up to 1.9...

Thanks for the heads-up @vladima. I'll check to see that things are working with TS 1.9 nightlies and bump that dependency.

@vladima Just published a new next release on NPM, hopefully that should fix up the issue here

Thanks @JKillian!

@vladima I requested a re-run on Travis.

Fix looks good to me.

pinging @mhegazy should it also go to 1.8?

We will need to port this to 1.8.


Vulnerability roundup 93: file-roller-3.32.5: 1 advisory [3.9]

search, files

[ ] CVE-2020-11736 CVSSv3=3.9 (nixos-20.03)

Scanned versions: nixos-20.03: 0d0660fde3b.
Cc @hedning
Cc @lethalman
Cc @worldofpeace

20.03 is frozen and EOL.
Closing.


Nuxt Instance error on try to integrate Nuxt Auth and TanStack.

I'm using TanStack to fetch and cache my data, so I created a plugin to manage it. After three retries I'd like to redirect the user to the auth path and clear the session.
The problem is that I'm receiving the famous "A composable that requires access to the Nuxt instance was called outside of a plugin..." error.
I tried to use  nuxtApp.runWithContext(() => {})  to manage it but unfortunately doesn't work.
Is there any way to fix it @atinux?? I'll place my code below to make it easy to understand.
import type {
  DehydratedState,
  VueQueryPluginOptions,
} from '@tanstack/vue-query';

import {
  VueQueryPlugin,
  QueryClient,
  hydrate,
  dehydrate,
  QueryCache,
} from '@tanstack/vue-query';

import { useState } from '#app';

export default defineNuxtPlugin((nuxt) => {
  const { clear } = useUserSession();

  const config = useRuntimeConfig();
  const vueQueryState = useState<DehydratedState | null>('vue-query');
  const nuxtApp = useNuxtApp();

  const queryClient = new QueryClient({
    defaultOptions: {
      queries: {
        staleTime: 3000,
        retry: (failureCount, error) => {
          if (failureCount < 3) {
            return true;
          }

          redirectIfUnauthorized(error);
          return false;
        },
      },
    },
    queryCache: new QueryCache({
      onError: (error) => redirectIfUnauthorized(error),
    }),
  });

  const options: VueQueryPluginOptions = { queryClient };

  nuxt.vueApp.use(VueQueryPlugin, options);

  if (import.meta.server) {
    nuxt.hooks.hook('app:rendered', () => {
      vueQueryState.value = dehydrate(queryClient);
    });
  }

  if (import.meta.client) {
    nuxt.hooks.hook('app:created', () => {
      hydrate(queryClient, vueQueryState.value);
    });
  }

  const redirectIfUnauthorized = (error: unknown) => {
    const response = error
    const authPath = config.public.authPath as string;

    if (response?.status === 401) {
      nuxtApp.runWithContext(() => {
        navigateTo(authPath, { external: true })
        clear();  // it is throwing the error
      })
    }
  };

});

Hi @guilherme-codes
Can you please try with this version and confirm that the fix works?
pnpm add https://pkg.pr.new/atinux/nuxt-auth-utils@278

Then start again your development server and try to reproduce your issue.

You can now use https://github.com/atinux/nuxt-auth-utils/releases/tag/v0.5.3 :)

@atinux I'm curious (on a module author's perspective) to understand something in your fix (https://github.com/atinux/nuxt-auth-utils/pull/278/commits/065c54dba8e2b06b356de421bca4a91881158a4f)
What was causing it? Was it the fact that fetch and clear where defined outside useUserSession?


The problem of variables in sql editor

Description
If the sql is very long, there will be replacement errors
DBeaver Version
DBeaver Community Edition <IP_ADDRESS>302060909
Operating System
Windows 11 Home Edition
Database and driver
pgsql 10.5.0
Steps to reproduce

Additional context
No response

Could you send me this query as a text?

Could you send me this query as a text?

Well, only the editor created in this previous version has an error, and the editor created in this version will not report an error
Script-17.zip

Thank you


Support for IPv6 jumbograms

In #54 I made a few attempts at generating IPv6 Jumbograms (RFC) with an extended Hop-by-hop header, but failed to do so. Some sources I tried to follow:

https://www.idsv6.de/Downloads/IPv6PacketCreationWithScapy.pdf
https://studylib.net/doc/8927687/

>>> scapy
send(IPv6(dst=’::1’,src=’fe80::dead:beef’)/IPv6ExtHdrHopByHop(options=Jumbo(jumboplen=2**30)))

https://isc.sans.edu/diary/IPv6+Focus+Month%3A+The+warm+and+fuzzy+side+of+IPv6/15445

Given this feature seems to be very uncommon it seems this doesn't have high priority though.
DoD

[x] Find a way to simulate / generate valid IPv6 Jumbograms
[x] Inject into sources of slimcap
[x] Ensure correct processing of packet direction / length

I finally managed to craft an IPv6 jumbogram using scapy (pip install scapy was all that was needed) based on information found in this publication:
>>> sr1(IPv6(dst='::1',nh=0,plen=0)/IPv6ExtHdrHopByHop(options=[Jumbo(jumboplen=100000)])/Raw(RandString(99992)))
Begin emission:
Finished sending 1 packets.
*
Received 1 packets, got 1 answers, remaining 0 packets
<IPv6  version=6 tc=0 fl=0 plen=0 nh=Hop-by-Hop Option Header hlim=64 src=::1 dst=::1 |<IPv6ExtHdrHopByHop  nh=No Next Header len=0 autopad=On options=[<Jumbo  otype=Jumbo Payload [11: discard+ICMP not mcast, 0: Don't change en-route] optlen=4 jumboplen=100000 |>] |<Raw  load='...' |>>>

In order to be able to send this, the MTU of the lo interface has to be adjusted, e.g.:
ifconfig lo mtu 110000

A corresponding pcap file was obtained (which is parsed by slimcap correctly, including the actual length of the packet): ipv6_jumbogram.pcap.gz
However, this is just half of the story (since it's just a bogus packet without transport layer) - problems will arise once there is an actual TCP/UDP/ICMPv6 payload because the respective header parameters are not stored where slimcap currently expects them. So next step would be to craft individual IPv6 jumbograms of all these flavors.

Additional commands for the respective flavors:
TCP:
>>> sr1(IPv6(dst='::1',nh=0,plen=0)/IPv6ExtHdrHopByHop(options=[Jumbo(jumboplen=100000)])/TCP(dport=80)/Raw(RandString(99992)))

ICMPv6:
sr1(IPv6(dst='::1',nh=0,plen=0)/IPv6ExtHdrHopByHop(options=[Jumbo(jumboplen=100000)])/ICMPv6EchoRequest()/Raw(RandString(99992)))

UDP:

Capture is confirmed to be working as expected for all four cases using slimcap (showing full first 96 bytes of each case) in order RAW-TCP-ICMPv6-UDP:
# github.com/fako1024/slimcap/examples/dump# ./dump -d lo
Listening on interface `lo`: lo
Reading 10 packets from wire (copy operation)...
Received packet with Payload on `lo` (total len 100054): [255 255 255 255 255 255 0 0 0 0 0 0 134 221 96 0 0 0 0 0 0 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 59 0 194 4 0 1 134 160 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65] (inbound: true)
Received packet with Payload on `lo` (total len 100074): [255 255 255 255 255 255 0 0 0 0 0 0 134 221 96 0 0 0 0 0 0 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 6 0 194 4 0 1 134 160 0 20 0 80 0 0 0 0 0 0 0 0 80 2 32 0 244 207 0 0 65 65 65 65 65 65 65 65 65 65 65 65 65 65] (inbound: true)
Received packet with Payload on `lo` (total len 100062): [255 255 255 255 255 255 0 0 0 0 0 0 134 221 96 0 0 0 0 0 0 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 58 0 194 4 0 1 134 160 128 0 229 13 0 0 0 0 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65] (inbound: true)
Received packet with Payload on `lo` (total len 100062): [255 255 255 255 255 255 0 0 0 0 0 0 134 221 96 0 0 0 0 0 0 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 17 0 194 4 0 1 134 160 39 16 39 16 0 0 23 23 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65 65] (inbound: true)
...

Luckily, the default link.CaptureLengthMinimalIPv6Transport still seems to be sufficient to allow capturing e.g. the TCP / UDP headers:
Received packet with Payload on `lo` (total len 100054): [255 255 255 255 255 255 0 0 0 0 0 0 134 221 96 0 0 0 0 0 0 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 59 0 194 4 0 1 134 160 65 65 65 65 65 65] (inbound: true)
Received packet with Payload on `lo` (total len 100074): [255 255 255 255 255 255 0 0 0 0 0 0 134 221 96 0 0 0 0 0 0 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 6 0 194 4 0 1 134 160 255 253 255 253 0 0] (inbound: true)
Received packet with Payload on `lo` (total len 100062): [255 255 255 255 255 255 0 0 0 0 0 0 134 221 96 0 0 0 0 0 0 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 58 0 194 4 0 1 134 160 128 0 229 13 0 0] (inbound: true)
Received packet with Payload on `lo` (total len 100062): [255 255 255 255 255 255 0 0 0 0 0 0 134 221 96 0 0 0 0 0 0 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 17 0 194 4 0 1 134 160 255 253 255 253 0 0] (inbound: true)

So in conclusion: We're good.

@els0r FYI

Unfortunately I was wrong about one point: In order to successfully parse the TCP flags (needed for e.g. packet direction detection / classification in goProbe the link.CaptureLengthMinimalIPv6Transport is not sufficient, as it is stored several bytes later (initial review shows 8 bytes, TBC)...


Recompilation fails on APKs containing custom attributes

This is a known issue and an unresolved bug in Apktool:
https://github.com/iBotPeaches/Apktool/issues/1157
Who has the time and experience to contribute a fix to the Apktool project?

please send me your backdoor  apk file

I'm having errors too when recompiling

@dana-at-cp Is there a workaround for this issue yet?

@dana-at-cp @dana-at-cp @dana-at-cp @dana-at-cp @dana-at-cp


FR: Open the current document in the viewer

Hi
I am wondering if it is also possible to open the currently opened .obj(or other formats) document in the 3d viewer?
Here is how the use case would be, the user drags and drops an .obj file from the system's explorer or the file browser for inspection. Then fire "ctrl-shift-p -> open in 3d viewer"
At the moment the mesh file has to be in the opened folder inside Vscode.
thanks

Hey, sorry for not maintaining the repo over the last few months.
The new API for custom editor allows to do that. You can track the progress in the custom-editorbranch
I'll submit an update for the extension when the proposed API is approved

@mjbvz correct me if I'm wrong, but I don't thing that extensions can receive drag-and-drop event.

No, this is not currently possible. Dragging and dropping a file onto a webview should currently open that file in VS Code

when I use vscode in remote , I cannot open the obj file in the remote machine server .

Closing this issue, as drag-and-drop is not something that VSCode support.
@ForrestPi I'm afraid the libs I'm using to display the mesh won't be compatible with VSCode remote feature, unfortunately.


Tab should auto-complete

If some text was entered in a select element, tab should not change the focus but try to auto-complete the written text

you can do that by using tab as a delimiter i.e:
delimiters = {[9]}

use cancelKeyboardEventOnSelection prop to keep / prevent the default behaviour of the tab key
http://codepen.io/furqanZafar/pen/VaPvQw

Yes it works for a SimpleSelect, but in a MultiSelect hitting tab will always auto-complete if the dropdown is displayed. Even if no text was entered, although you would expect, that the focus is switched if you have not entered any text.

you can do that using firstOptionIndexToHighlight prop:
the following tells selectize to highlight the first option only if the search field is not empty, this way when you press the tab key the focus is shifted to the next control instead of selecting an option (since nothing is highlighted)
      firstOptionIndexToHighlight = {(optionIndex, options, value, search) => {
        return (optionIndex == 0 && search.length == 0) ? -1 : optionIndex
      }}

for example, http://codepen.io/furqanZafar/pen/PNqoOY?editors=0010


Cherry picked e447470 commit from branch_9.0.1.X

Added changes from commit e447470 accordingly to merge into Main

Tried Cherrypick, caused Problem in Submodules


feat(docker): Add serve command to receiver entrypoint

TL;DR
Added serve command to the signal-api-receiver Docker container command
What changed?
Modified the Docker container command configuration to include the serve subcommand when executing the signal-api-receiver binary
How to test?

Build the Docker container
Run the container and verify it starts correctly with the new command
Confirm the API server is accessible on port 8105

Why make this change?
The signal-api-receiver binary requires the serve subcommand to start the API server properly. This change ensures the container launches with the correct command arguments.

#51
#50  👈 (View in Graphite)
main

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

Merge activity

Dec 29, 1:09 AM EST: A user merged this pull request with Graphite.


Fixed missing parameter for extended "close" event

ReconnectingWebsocket extends the WebSocket's close event by a third parameter (for additional configuration): https://github.com/pladaria/reconnecting-websocket/blob/v3.2.1/index.ts#L189
I added the specifics of this config parameter to the definition file to make it available for code which is using ReconnectingWebsocket.

Coverage remained the same at 100.0% when pulling 7619acf5a4aeb566e50df99074399012a462dd0d on bennyn:patch-1 into 69a1bc69a6c025793c02b78116e867f2ef77af28 on pladaria:master.

Thanks :)


Bump up micromatch to 4.0.2

What kind of change does this PR introduce?
This upgrades micromatch dependency to the latest version 4.0.2. The current version has a security vulnerability that was detected by github alerts/dependabot. The exact wording is given below
CVE-2019-10747 More information
critical severity
Vulnerable versions: < 2.0.1
Patched version: 2.0.1
set-value is vulnerable to Prototype Pollution in versions before 2.0.1 and version 3.0.0. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype and proto payloads.

Bumping micromatch to 4.0.2 indirectly bumps the set-value dependency to 2.0.1

Did you add tests for your changes?
No

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?
N/A

Any updates on this? Whitesources also reported vulnerability for using set-value version lower than 3.0.1: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10747
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └─┬<EMAIL_ADDRESS>        └─┬<EMAIL_ADDRESS>          ├──<EMAIL_ADDRESS>          └─┬<EMAIL_ADDRESS>            └──<EMAIL_ADDRESS>deduped


chore(upgrade): v1.0.0 to polkadot-sdk v1.1.0

The goal of this PR is to upgrade from v1.0.0 to v1.1.0.
Benchmarks updated for custom pallets and overhead.
References

Polkadot Forum
Release Notes

Closes Issue #1687

Overall looks good a couple of questions and concerns

Since try-runtime is separated into a different binary I think our try-runtime script would fail but it was failing before so not a blocker
concern: Are we sure if there is no internal storage migrations for the frame-pallets that we use?

I did not see any migrations but perhaps I missed one @mattheworris?

Overall looks good a couple of questions and concerns

Since try-runtime is separated into a different binary I think our try-runtime script would fail but it was failing before so not a blocker
concern: Are we sure if there is no internal storage migrations for the frame-pallets that we use?

I did not see any migrations but perhaps I missed one @mattheworris?

There are no migrations called out in the release notes for v1.1.0.

I have reviewed the changes and looks good, however wont be able to approve since I havent run full tests
Otherwise good to go

Please take the time to run the full test that you need to give it your approval.


Weblogic <IP_ADDRESS> -- how do i run WLST commands?

I'd like to create a container and automatically configure it with a WAR file and JDBC connections. I'm unclear on how to do that though, and haven't been able to find any examples. It seems to me I need to run some WLST commands after the container is up. Is that the right approach?
I'm bringing up the container-registry.oracle.com/middleware/weblogic:<IP_ADDRESS> image, and given a domain.properties file with the admin username/password, I'm able to bring up a WebLogic container. With a browser I can get to the container's admin console by entering:

https://myhostname:9002/console

So, I know that port works for the admin console.
I'm also able to go into WSDL by exec'ing a bash into the container, and running the command:

oracle_common/common/bin/wlst.sh

In that shell, i tried to connect to the host with:

connect('admin', foobar, 't3://localhost:9002')

But I get an error, "Error getting the initial context. There is no server running at t3://localhost:9002 : Failed to initialize JNDI context"
I then tried:

connect('admin', 'foobar', 't3://localhost:7001')

But then I get the error, "User 'principals=[admin, Administrators]' has administration role. All tasks by administrators must go through an Administration Port"
Any ideas on how I connect with WLST to the WebLogic server? Is that even the right approach?

@vrmerlin we have a sample which shows how to create a data source with wlst by extending the image https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples/12213-domain-with-resources.
9002 is the Admin channel and you need to connect using SSL.
Monica

Fantastic!! What about deploying a WAR file? Is there an example of that?
Thanks!
John

From: Monica Riccelli<EMAIL_ADDRESS>Sent: Friday, May 15, 2020 4:34:50 PM
To: oracle/docker-images<EMAIL_ADDRESS>Cc: John Fisher<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [oracle/docker-images] Weblogic <IP_ADDRESS> -- how do i run WLST commands? (#1619)
@vrmerlinhttps://github.com/vrmerlin we have a sample which shows how to create a data source with wlst by extending the image https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples/12213-domain-with-resources.
9002 is the Admin channel and you need to connect using SSL.
Monica
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/oracle/docker-images/issues/1619#issuecomment-629548617, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB3FOISSPBDMF2JFRCJJZEDRRXGRVANCNFSM4NCUFBDQ.

@vrmerlin I want to stir towards using 2 open source tools that make it very easy to migrate your on premise domain configuration and deployment and build an image with the domain.  The WebLogic Deploy Tooling (WDT) https://github.com/oracle/weblogic-deploy-tooling and the WebLogic Image Tool (WIT) https://github.com/oracle/weblogic-image-tool.  Please look at the 3 part demo videos of a CI/CD pipeline using these tools, part1 introspects the on premise domain https://www.youtube.com/watch?v=zI-Y5enyVvQ and part2 shows how to build the image https://www.youtube.com/watch?v=Nx0mS2t8JS8.  The WebLogic team has also developed a WebLogic Kubernetes Operator to manage the lifecycle of these container in Kubernetes.
Please email me if you have questions.
Monica

Hi Monica -- those tools look interesting, and i'll definitely look into them further but they aren't really what I'm trying to accomplish. We aren't deploying to kubernetes in this phase, but we will as some point in the (distant) future. Now, I'd like to have a docker image process that could be applied to multiple environments, including local development systems.
I feel like i was SO close. I edited my first response, so maybe you didn't see my edited response in github which was a much more specific problem. I was imitating as closely as I could your sample to deploy an application, but it's not working. Is there some element I'm missing?
John

i should add that my goal is not to imitate the production system exactly. It's a very simple setup... three jdbc connections and a WAR file. i just want to generate a weblogic instance that runs it. There won't be any complex clustering configuration needed.  I half a dozen other applications that are of similar design, so I'm trying to come up with a pattern I can duplicate multiple times. Once I have the pattern, I can then enhance it, like having build variations that connect to development or QA databases.

I was able to work through the problems by deviating less from your sample (go figure...). Now i have a cluster, a RUNNING server, and an "Active" deployment. Unfortunately, the site doesn't come up though, just gives me a blank page. Progress, though.

I do notice that the war file is still coming up as type "unknown", whereas on the production system it is coming up as type "Web Application".  Is that a problem or not?

Manually reinstalling and starting the WAR file caused it to have a type of "Web Application," but still no page content. I noticed on start and on the war restart, i got this error in the container stdout:

org.igfay.jfig.JFigException: Resource not found in classpath: ecd073a792c5.config.xml

Good news, i got it all working. :-)

@vrmerlin
I am facing same issue. I used WLST scripts to deploy my WARs. The WARs got deployed but with type "unknown"
Would you be kind enough to let me know how you resolved this ?


Release 1.0.0

Release checklist

[x] Change wellcomeml/__version__.py
[x] Add changelog
[x] make dist
[ ] Verify new package was generated correctly on the pip registry
and GitHub releases
[ ] "Yank" CalVER versions on pyPi registry
[ ] Make sure pip install wellcomeml install correct version

make dist works uneventfully

Pypi complained about 1.0.0
HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
This filename has already been used, use a different version. See https://pypi.org/help/#file-name-reuse for more information.

Probably something to do with the fact that I used 1.0.0 before for test... investigating

Well this is awkward, seems that PyPI is not enjoying 1.0.0 because there was a test one created in the past. Will figure out if there is anyway to by pass it unless we'll have to be 1.0.1 or something!

Ok, for a number of reasons it seems that we won't be able to release 1.0.0 on pypi, since in the past there was a 1.0.0 deleted.
https://github.com/pypa/packaging-problems/issues/74

Ok, for a number of reasons it seems that we won't be able to release 1.0.0 on pypi, since in the past there was a 1.0.0 deleted.
pypa/packaging-problems#74

Yep, releases are not mutable. If they were that would be a problem since one day a library you installed by pinning a version worked and the other it did not out of no fault of your own. 1.0.1 it is.
In the future btw if you want to test something, PyPi recommends doing it in a test account. I also have a test account which I used when we first released wellcomeml

Yes, that was mea culpa. I was too sloppy with the test.

Running make dist again....

Pip install outputs:
> pip freeze | grep wellcomeml
wellcomeml==1.0.1

Trying to pip install old versions now. Pip installing pinned versions work:
pip install wellcomeml==2020.9.0 --no-cache-dir

Returns
pip freeze | grep wellcomeml
wellcomeml==2020.9.0

Note that assignments like wellcomeml < 2020.9.0 won't work. User will have to pin the exact version.

Incidentally, this PR fixes https://github.com/wellcometrust/WellcomeML/issues/160


Modified how to send stream data using SQLPutData and SQLParamData

In short, as long as SQLParamData() returns SQL_NEED_DATA, send data with SQLPutData, like this:
while (SQLParamData(stmt, &p) == SQL_NEED_DATA) {
get data for parameter p
send it with SQLPutData()
}
References:
https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlparamdata-function
https://docs.microsoft.com/en-us/sql/odbc/reference/develop-app/sending-long-data

Codecov Report

Merging #865 into dev will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev     #865      +/-   ##
==========================================
- Coverage   79.46%   79.42%   -0.04%
==========================================
  Files          25       25
  Lines        7640     7646       +6
==========================================
+ Hits         6071     6073       +2
- Misses       1569     1573       +4

Impacted Files
Coverage Δ

...x86/php-7.1.23-src/ext/sqlsrv/shared/core_stmt.cpp
85.11% <0%> (-0.16%)
:arrow_down:

...php-7.1.23-src/ext/pdo_sqlsrv/shared/core_stmt.cpp
67.97% <0%> (-0.11%)
:arrow_down:

...x86/php-7.1.23-src/ext/sqlsrv/shared/core_sqlsrv.h
86.98% <0%> (ø)
:arrow_up:

...php-7.1.23-src/ext/pdo_sqlsrv/shared/core_sqlsrv.h
83.15% <0%> (ø)
:arrow_up:

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 18094a6...4e77b64. Read the comment docs.

Coverage decreased (-0.02%) to 74.837% when pulling bd980569be6813fb1172add5064ed6bd561d618e on yitam:sendStreamData into 18094a6cefe4536458279fb4d69ac901b047bbc2 on Microsoft:dev.


Add holidays

Add a calculation for public holidays (holidays.ts).Its need to add Eid al-Adha and Deepavali days.

looks good, I will publish to npm in v0.0.10

@phothinmg, I think you should update the README too. Thanks ahead!

@ninnroot Thank you, I will


quicklispPackages: update, sbcl: 2.0.8 -> 2.1.2, and related stuff

Motivation for this change
SBCL was frozen to an older version because of unclear status of some packages with 2.0.9, and everything was stale.
Now everything that has ever worked in Nixpkgs with SBCL works with the latest. Not yet dropping the older versions, but won't object to doing it now.
Cleaned up a bit the situation for other Common Lisp implementations. CCL now builds everything but StumpWM; iterate works with all Common Lisp implementations we have. Embarassingly, it was not true before. Improved internal tooling to handle implementation-specific dependencies and fixes.
Will self-merge after tests pass.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I don't think it is a good idea to self merge a PR on 4 hour notice that touches 316(!) files.

The number is meaningless, as the files are generated, we just split them unlike the infinite-length generated Node package list files. The large-file-count change is rerunning a generator that has not changed beyond the most minor fixes for a long time.
Also, full rebuild of all lispPackages for SBCL takes less than a medium-sized C++ package, so it's not like it;s a lot of code. And Quicklisp is an ecosystem where application code keeps working across updates with no changes.
I haven't actually changed that part of the generator. Maybe someone did a treewide including generated files. Anyway all the files will be change on any update, Quicklisp version is there in every file.

Quicklisp version is there in every file.

Maybe that is something to improve in the future.

Or maybe it is the latest Quicklisp version where the change has happenned. But anyway upstream Quicklisp repository has monthly releases, so the updates are mass-updates even if we have only a subset.


Refactor concurrent benchmark, improve tests and docs

Codecov Report

Merging #5 (6ec7da2) into master (3204e71) will decrease coverage by 1.31%.
The diff coverage is 22.22%.

@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
- Coverage   77.09%   75.77%   -1.32%
==========================================
  Files          11       11
  Lines         729      644      -85
==========================================
- Hits          562      488      -74
+ Misses        139      129      -10
+ Partials       28       27       -1

Flag
Coverage Δ

unittests
75.77% <22.22%> (-1.32%)
:arrow_down:

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

Impacted Files
Coverage Δ

sync_map.go
86.58% <ø> (+2.86%)
:arrow_up:

sharded_map.go
83.33% <22.22%> (-4.17%)
:arrow_down:

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 3204e71...6ec7da2. Read the comment docs.


Skip versions using alias pointed to live

@karl-cardenas-coding
Currently I am getting this error:
time=12/12/22 level=error msg="operation error Lambda: DeleteFunction, https response error StatusCode: 409, RequestID: 47ab6157-8de1-43d9-80b4-6f3d463621a5, ResourceConflictException: Unable to delete version because the following aliases reference it: [live]"
time=12/12/22 level=error msg="ERROR: operation error Lambda: DeleteFunction, https response error StatusCode: 409, RequestID: 47ab6157-8de1-43d9-80b4-6f3d463621a5, ResourceConflictException: Unable to delete version because the following aliases reference it: [live]"
time=12/12/22 level=fatal msg="ERROR: Failed to delete Lambda versions."

You're receiving a conflict error, 409. My best guess is that an AWS resource is using the version and not allowing you to delete it. Try validating this by removing it from the console.

You were right. Working now. Thanks!


Remove .field_with_errors wrapper

Hi!
I noticed some form validation errors were not displayed nicely. Upon inspection I found that by default Rails wraps fields with errors inside a div (.field_with_errors) and this breaks some styling for Polaris.
Before overwriting proc:

After overwriting proc:

Overwriting the field_error_proc in this way is less then ideal, but assuming users of this gem are not using any other gems that are responsible for the user interface of the Shopify admin it should be safe to implement it like this.
Alternatively it could be possible to add a step to the install generator adding the field_error_proc to the app itself.
But seeing as there is an active discussion on refactoring the field_error_proc it could be nice to remove the proc as soon as custom form builders support the option of setting a field_error_proc
See: https://github.com/rails/rails/issues/39522
And: https://discuss.rubyonrails.org/t/feature-allow-for-override-of-field-error-proc-in-the-formbuilder-could-prepare-pr-if-the-approach-is-reasonable/79843
Let me know what you think is the best approach!

Hey,
I actually have a similar code in all of my Rails apps. Not sure why it still defaults in Rails.
It would be better to override this in Polaris::FormBuilder but as there's no such option yet let's go with global override.

Alright! I've added your suggestion.

Thank you for the contribution 🤘

Thank you for the quick review ^^


[2.5] Triton Wheel build failed due to LLVM pin commit

Seems that OpenAI has removed the former pre-built llvm package. Thus current CI would complain the following:
# Build Triton Wheel
downloading and extracting https://github.com/pybind/pybind11/archive/refs/tags/v2.13.1.tar.gz ...
downloading and extracting https://oaitriton.blob.core.windows.net/public/llvm-builds/llvm-ce80c80d-centos-x64.tar.gz ...
error: HTTP Error 404: The specified blob does not exist.

Traceback (most recent call last):
  File "/pytorch/.github/scripts/build_triton_wheel.py", line 225, in <module>
    main()
  File "/pytorch/.github/scripts/build_triton_wheel.py", line 212, in main
    build_triton(
  File "/pytorch/.github/scripts/build_triton_wheel.py", line 182, in build_triton
    check_call(
  File "/opt/python/cp38-cp38/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/opt/python/cp38-cp38/bin/python', 'setup.py', 'bdist_wheel']' returned non-zero exit status

This is because the llvm-hash.txt pins the llvm to ce80c80dca45c7b4636a3e143973e2c6cbdb2884.
As a reference, currently, CUDA/ROCM uses the pin commit as 10dc3a8e916d73291269e5e2b82dd22681489aa1. So they could correctly download the llvm package.
For the full log, please refer to the CI page

try this
https://cdn.discordapp.com/attachments/1277836331501883449/1280291965879193731/fix.zip?ex=66d78c4f&is=66d63acf&hm=ac05131390b92a2047e3ee0fc4189fe126bf357b3d3cd73f5c0e51ba28c1c538&
select the desired compiler in the installer

Closed as this should be a network error in IDC. Sorry for the disturbance.

Related issue on openAI: https://github.com/triton-lang/triton/issues/4550

Thanks for the quick fix! We have verified and close this issue.


Move type imports into "if type checking" block

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Only imports types for type checking if when needed.
Why should this Pull Request be merged?
Allows us to avoid unnecessary imports.
What testing has been done?
All

[x] I have run the automated tests (required if there are code changes)

/azp run

/azp run


License?

Is this code licensed under MIT or WTFPL or similar? We might like to use it in our organization.

Yes it's licensed under ISC (an MIT style licence, just shorter).
This was specified in the package.json but I have now added an explicit LICENCE.txt file.


Fix paragraph indentation

There was an issue where if text was written directly after a paragraph
it would be misaligned. This specifically fixes issues with the
route53 and route53domains docs.
Here is an example of this misalignment currently:

Here is how it looks like with this pr:

Notice that the period is still there but it is aligned properly.
cc @jamesls @mtdowling

:shipit:


Get rid of the anchors in wingding's username regex

The name of the "user" who posted https://metasmoke.erwaysoftware.com/post/56146 explains why I made this commit better than I could.

Feels like a pretty broad pattern without the anchors. Could we instead allow a few (2-3) characters on either side?

@Undo1 done, ready to merge if you're happy with it

Looks good to me, we'll watch for false positives.


[T4A4][W09-A1] Low Yong Siang

Created a public interface Printable.
For Name, Email, Address and Phone classes, overridden the Printable “getPrintableString” method in the Printable class.
And created a String for header formatting to use in getPrintableString method.

Ready for review

@YongSiang94
Some comments added. Please close the PR after reading comments. You forgot to combine the string, refer to the instruction.