Built-in OSSL_STORE loader fails to open PEM files that have explanatory text longer than 4096 bytes

As mentioned in RFC 7468, section 5.2, PEM files are allowed to have explanatory text before their BEGIN headers. OpenSSL's built-in store loader supports that, but with a (rather small, hard-coded and undocumented) limit of 4096 characters before the header. This seems an arbitrary number and the fact that this limit exists seems incorrect in the first place.
The code responsible for this can be found here: https://github.com/openssl/openssl/blob/e2e09d9fba1187f8d6aafaa34d4172f56f1ffb72/crypto/store/loader_file.c#L873

The reason for this is so that we can try to find out what the contents are by peeking, so the actual reading is done from the same starting position.  So what the code does is to place the BIO_f_buffer() filter in top of the input BIO, and peek.  The buffer size is what BIO_f_buffer() uses as default size, see here:
https://github.com/openssl/openssl/blob/c5b356d5d6cfca1128b35f235dfdb893f2888027/crypto/bio/bf_buff.c#L23
Why not use BIO_tell() or BIO_seek()?  We have an alternative to OSSL_STORE_open(); OSSL_STORE_attach() lets you pass a BIO directly, and have that represent whatever scheme the caller finds fitting.  This means that the input BIO could be standard input, for which there is no BIO_tell() or BIO_seek() support, so we need to treat the BIO carefully.
There are two ways to solve the issue:

Increase the buffer size, but the question is to what.  We can't resize it on the fly, that currently clears the BIO_f_buffer() internal buffer
Create a dynamic caching filter BIO, which becomes a kind of resizeble window on top of the input BIO, and has internal support for BIO_tell(), BIO_seek() and whatever else is expected from a "normal" file.

The latter is on my wish list...  so is huge amounts of time :wink:

Thanks for explaining @levitte .
The/A problem is that this limit is easily exceeded for certain types of certificates, for example those containing a DSA public key of 2 kbits (or larger). The failing open() function makes it hard to rely on the store functionality.
I was not aware of the attach() functionality. From grep-ing around, it seems to be an (unused?) internal function?

It's not unused as far as I recall. Also, it has become public in master.
The quick fix is a larger buffer. By how much, would you recon?

Another, or an additional, option is to limit the length (by default) of the explanatory text when a PEM file is produced by any of the OpenSSL tools, to align it with the store limitation. That way, the problem will at least not be hit when working within the OpenSSL ecosystem only.
I took the 4096 bit DSA cert example from here and used OpenSSL's x509 tool to convert it to text, resulting in 8094 bytes. So for the quick fix you mentioned, maybe doubling the current buffer size would be a good choice, if 8K is considered acceptable for a variable on the stack.

Marking as inactive, to be closed at the end of 3.4 dev barring further input


Compile folder of .css files at once

It will be handy to have such possibility, smth like:
cssnext --folder ./folder --output-folder ./output

Maybe we can just accept a glob for the input filename ?
Like
$ cssnext "folder/*.js" ./out/

Not sure if it's a good idea since some shell (eg: zsh) might resolve the glob as multiple filenames.

Not relevant anymore. cssnext is now postcss-cssnext. cssnext is deprecated. See postcss-cssnext migration guide http://cssnext.io/postcss/


Raise the minimum supported version of Java to 11

Apache CXF 4.0.0 requires Java 11 as a baseline: https://issues.apache.org/jira/browse/CXF-8660.
Therefore, this plugin will also require a Java 11 baseline.

Hello,
But in fact the plugin is not working using version > 11 (Version 17) has javax.xml.ws.Service is no more part of JDK.
Do you have upgraded the tool ?
Regards

@loicdesguin This is covered in the docs: https://ciscoo.github.io/cxf-codegen-gradle/docs/current/user-guide/#java-9
and is unrelated to this issue.
This issue is about building this plugin with Java 11 which is different from the tool itself.

There is no benefit at the moment to making the plugin require Java 11.

The request is not to have the tool requiring java 11 but having the tool working wirth recent version of Java what's a logical request: forcing people to keep working with java 8 is a non sens.
Marking my comment of topics will not solve the fact you tool is out of date.

Regards


Feature/original request headers

Closes #33

Codecov Report

Merging #34 into master will increase coverage by 4.56%.
The diff coverage is 97.01%.

@@            Coverage Diff             @@
##           master      #34      +/-   ##
==========================================
+ Coverage   82.96%   87.53%   +4.56%
==========================================
  Files           6        6
  Lines         364      353      -11
==========================================
+ Hits          302      309       +7
+ Misses         61       42      -19
- Partials        1        2       +1

Impacted Files
Coverage Δ

main.go
33.33% <71.42%> (-6.07%)
:arrow_down:

services/authenticator.go
100.00% <100.00%> (ø)

services/config_parser.go
100.00% <100.00%> (ø)

services/server.go
100.00% <100.00%> (ø)

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 7d58a95...a8cd5ac. Read the comment docs.


imagenet 32 x 32 is gone, any tips?

Hi Authors
Thanks for sharing your code!
Do you have any tips for where to find an imagenet 32x32 dataset as used in your work?
The link stored by tensorflow_datasets is broken (so tfds and jax do not load the data successfully). More generally, https://image-net.org/small/download.php is also broken, which is a parent url to the one tfds stores.
I have heard there are several versions of the dataset floating around online.
Some researchers in the field express concern that the 32x32 that is currently available (at https://image-net.org/download-images.php) "is wrong for generative modeling publications" for some reason. So I would like the use the version you have used.
Thanks!!!
Mark

I made an issue on tfds (https://github.com/tensorflow/datasets/issues/4662) but still commenting to here to find out if there is some way to reproduce your research on the data that you used.
Thanks!

You can find an academic torrent that allows you to provide the data needed for TFDS to generate the dataset. For example here: https://academictorrents.com/details/96816a530ee002254d29bf7a61c0c158d3dedc3b


Ongoing collection of quantitative data on search sessions

[ ] Setup a structure for the mappings in the reporting API for search events
[ ] Setup naming conventions for events sent through
[ ] Use λ to process / cleanse segment data
[x] Start collecting the position
[ ] Get catalogue λs into a universal type state
[ ] ...TBC

I could open another issue, or start the conversation here, but here's what I was thinking re: structure of tracking logs:
The shape of the client event is:
{
  service: string,
  name: string,
  data: Object
}

Currently we have two services with the following events:

search

Search : someone made a search. Has properties:  query, page, workType, _queryType
Select Result : someone chose a result. Has properties: query, page, workType, _queryType, position

relevance_rating

Rate Result Relevance : someone gave us a rating on relevance. Has Properties: query, page, workType, _queryType, position, id, rating

In elastic search it will create a document with these fields with anonymousId, toggles, event, network, and data as the above fields.
TODO

Example

Looks mostly good to me. Two things that I want to check:

Is the network there to allow us to distinguish internal requests? What are the possible values? Ie, I'm assuming we're not recording user's WiFi network names?
Should the search result selected doc have the position of the result in the result list?

At the moment the only two we specify are StaffCorporateDevices and Wellcome-WiFi.
We could just say something like internal but the separation seems useful. We could also rename them to things like WellcomeInternal and WellcomeWifi, but also feels like an unnecessary step away from what we are actually measuring.

Should the search result selected doc have the position of the result in the result list?

Yip, sorry, just omitted it.

Thanks - makes sense to keep the networks split. Wellcome-Wifi is used for both staff personal and public devices. So I can see us wanting to look at that separately.


Error: Apparent recursion within a with_prototype action: 25000 context sanity limit hit

On sublime 3.1.1 build 3176
With this plugin installed I get:
Error loading syntax file "Packages/PHP/PHP.sublime-syntax": Apparent recursion within a with_prototype action: 25000 context sanity limit hit
If removed it goes away and everything works (except for css, of course)
Edit: reference https://github.com/sublimehq/Packages/issues/1665

I have this same problem too, I don't know why it appeared yesterday, before that I didn't have problems with this package

I can confirm that this issue just started 2 days ago as well

Any news on this?

No responses from maintainer, I'm just going to keep the package disabled on my sublime text
Weirdest part is that sublime text and the css3 packages have not changed/updated, but this problem suddenly appeared out of nowhere
reinstalling everything from a fresh sublime text install didn't help either until disabling css3

I just had the same problem (not yesterday nor three days before). Disabling CSS3 didn't help me out.
For me it was JavaScriptNext - ES6 Syntax. I've disable it and enable CSS3.
The problem was solved after restarting ST3.

Sorry for taking so long to fix this, but it should be fixed now in #108. Version 2.1.18 should be out on Package Control shortly. Please reopen if you continue to see the sanity limit error.

It seems that the error it's still there.
I've tried wiping cache files, and the plugin it's updated to version 2.1.18

Very sorry, guys. I'll investigate tonight.

Any news? I really like this plugin, I don't want to remove it...

Hmm, I'm not able to reproduce this. I tried several large PHP programs and didn't get any errors. This may be caused by an interaction of plugins.
Can someone please provide some sample code where the issue occurs for them, along with their list of installed packages? Thank you!

This happens to me too. Same error and no syntax highlighting of PHP files when CSS3 package is installed. When i remove the CSS3 package the problem disappears.
Installed packages:
[
"Alignment",
"ArcticTypescript",
"AutoFileName",
"Autoprefixer",
"BracketHighlighter",
"BufferScroll",
"CSS3",
"CSScomb",
"DocBlockr",
"EditorConfig",
"Emmet",
"Go To Definition",
"HTML-CSS-JS Prettify",
"JavaScriptNext - ES6 Syntax",
"jQuery",
"LESS",
"Origami",
"Package Control",
"PackageResourceViewer",
"PHP Syntax Checker",
"Phpcs",
"Sass",
"SCSS",
"SideBarEnhancements",
"SublimeLinter-phpcs",
"Terminal",
"Twig",
"TypeScript",
"WordPress"
]

@y0ssar1an So strangely, I tried to do a little trouble shooting and disabled all 3rd party plugins that I had installed and turned them back on one by one to see if I could suss out the conflict. This apparently cleared the problem for me. There was some weirdness when I disabled 'Jade' but I cant confirm that this was the source of the conflict.
the plugins I have in common with @KristoferN are:
'CSS3',
'JavaScriptNext - ES6 Syntax',
'Package Control',
'SCSS'

Thank you for debugging this package! I think that submitting the issue of increasing the context is a good idea.

I opened an issue to discuss raising the context limit. It's not gonna happen, for the very good reason that it shouldn't take gigabytes of RAM to edit kilobytes of text. It looks like I made a bad call when I decided to make CSS3 function like a linter by writing regexes for every CSS property. Reversing that design decision would require an extensive rewrite. I don't have time for that, unfortunately.
As a short-term mitigation, I think I will disable CSS3 highlighting inside languages like HTML and PHP. I will no longer recommend disabling the default CSS package in the install notes. Users will have to switch back and forth between CSS and CSS3. That's annoying, but less annoying than this awful error.

This bug it's still present. Even if I don't disable the native CSS plugin, just the fact that this CSS3 plugin is installed pops up the error. What should I do?

I'm so sorry. It must be hitting the limit in a way that I don't understand. I don't have time to work on CSS3 at the moment. If anybody wants to help debug this, you can 1) remove CSS3, 2) clone this repo to your Sublime Packages directory, and 3) comment-out parts of CSS3.sublime-syntax until the error goes away. Then shrink the number of commented-out lines until you can identify the problem context (syntax highlighting rule). It's almost certainly the properties context. I thought I'd fixed the source of errors from that context.

Still present - breaks PHP.sublime-syntax.
Only by removing CSS3 is everything ok again
Seems there is still  a problem with this package

Since I haven't been able to reproduce the bug, and haven't been able to confirm that the problem occurs on the latest Sublime Text build, I will close this issue. I will reopen if anyone out there is still experiencing the issue.

Weirdest part is that sublime text and the css3 packages have not changed/updated, but this problem suddenly appeared out of nowhere

If the problem is indeed resolved, I wonder if the issue was fixed or worked around in Sublime Text itself 🤔


Local Video option

Hi Guys,
This is a wonderful project and I have helped set this up for my friend who runs a small store. I am planning to add offline video playback capability to this with a new video option. Thinking of using https://www.npmjs.com/package/video-react. Any suggestions otherwise?

@shankar-balachandran Hey, I am trying to set this up. Do you have any guide on the steps you did and did you manage to get offline video working ?


fix(extension) Fix the extension compilation on Linux

Fix #23.
@spasius Can you confirm it fixes your issue please?

Confirm compilation on CentOS 7.

:+1:


Fix bug where table data wasn't being updated

Also remove unused state initializations.
Problem
The state of TabbedMetricsTable wasn't being updated when the metrics were updated.
Cause
State doesn't update with props update in the constructor
(https://reactjs.org/docs/react-component.html#constructor)
Solution
Don't use the state set in the constructor.
Fixes #236

The UpstreamDownstream tables receive metrics as props and pass those down to TabbedMetricsTables, also as props. Each component can decide whether to set its own state upon construction based on the props it receives (or even update the state based on new props, using componentWillReceiveProps). We don't actually change any of the data in the TabbedMetricsTable, so there's no need for it to communicate any changes back to its parents. So we can get away with it being rendered solely on its props. The rollup field doesn't get updated because once the component is constructed with constructor it doesn't take into account new Props. It doesn't get overridden with empty data, it just decides not to do anything with the new data.


Stack traces logged during benign non-200 returns

Stack traces catch the eye when developing or reviewing logs, and right now we sometimes dump a stack in cases that are expected and benign:
2016-03-16 15:53:27      scitran.api                  base.py   189:ERRO Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/webapp2.py", line 570, in dispatch
    return method(*args, **kwargs)
  File "./api/jobs.py", line 292, in next
    self.abort(400, 'No jobs to process')
  File "./api/base.py", line 254, in abort
    webapp2.abort(code, detail=detail, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/webapp2.py", line 1830, in abort
    raise cls(*args, **kwargs)
HTTPBadRequest: No jobs to process

This is partially blocked by #66 for the reasons mentioned in that thread, but we might be able to solve this sooner by changing our usage of self.abort. Filed as part of an ops conversation with @ryansanford. Update: @lmperry just ran into this in prod as well.

Just a side note that the above stack trace is printed on (to my knowledge) every production deployment into the api log, every 5 seconds. I'd really love to get rid of this...

+1 on that. It drives me just a little crazy.


ci: deserialization fuzz testing

This adds basic deserialization fuzz testing to CI via quickcheck. Because it uses a limited number of randomized test runs, it is not particularly thorough, and should not be considered a replacement for the fuzz testing added in #79. That being said, it's a reasonable sanity check and runs quickly.
Closes #80.

Nice


Add ES7 :: Bind syntax

Hi Guys, I just wanted to touch bases, are there any other changes you would like to see in this PR?

These changes look good to me. I'm not sure what's up with the failing test though. @zackify?

Ignore the fail, it will work. Need to fix the script. But you can merge
On Sat, Jun 13, 2015 at 10:17 Jimmy Jia<EMAIL_ADDRESS>wrote:

These changes look good to me. I'm not sure what's up with the failing
test though. @zackify https://github.com/zackify?
—
Reply to this email directly or view it on GitHub
https://github.com/Legitcode/ReactJSNews/pull/5#issuecomment-111732866.


Cache for GET requests?

What about cache for GET requests?
Request is an HTTP Client, but for now, as I understand, it doesn't cache any GET requests, even if the appropriate headers are set.
Should we add cache logic to the request module? May be, it would be better to create other module for that?

take a look at oniyi-requestor. It implements rfc 2616 compliant caching on top of request

Well, I think that the caching logic should be definitely in separate module.
@benkroeger your requestor looks interesting, thanks.


fix documentation comment of flatMap

Helllo, I'm Masa, Swift lover.
I noticed that one documentation comment remained old and doesn't change since 2 years ago, so I fixed it.
Is this PR acceptable?
This PR only includes a fixed single file.
I really appreciate it if you would tell me if this there is a defect in this PR.
I'm deeply grateful to you for all your passionate work.
Thank you,
Masa

Resolves SR-NNNN.

Good catch, @creaaa! This LGTM, but I want @natecook1000 to spot-check it if he has time.

@swift-ci please smoke test

@creaaa Thanks so much!

Thanks too, @harlanhaskins, @natecook1000 !
This made my love to Swift unwavering. I'll keep learning to contribute more!


cgroups: pre-mount on pure-cgroup2 systems with cgroup namespaces

We only do force-premounting if we are on a cgroup2-only system.
While it's paranoid to check for both since cgroup2-only should imply cgroupns
but let's not rely on that.
Closes #6587.
Signed-off-by: Christian Brauner<EMAIL_ADDRESS>

lxd/cgroup/init.go:21:27: invalid operation: st.Type == cgCgroup2SuperMagic (mismatched types int32 and int64)

lxd/cgroup/init.go:21:27: invalid operation: st.Type == cgCgroup2SuperMagic (mismatched types int32 and int64)

So they seriously change to a 32bit int on i386...

In any case. Fixed.

Technically fine, but as cgroup is a shiny new clean package, we should put some more thought on how to do this cleanly, the suggestion above should give us a good starting point for further improvements.

Oh and make sure that golint lxd/cgroup is clean. It should be added to test/suites/static_analysis.sh too, that would have reported two errors with your change.

Reading through the cgroup detection logic you sent yesterday. That seems broken. The code doesn't seem to be able to detect a pure cgroup2 layout.

Oh and make sure that golint lxd/cgroup is clean. It should be added to test/suites/static_analysis.sh too, that would have reported two errors with your change.

We ended up adding this since this is useful for us too: https://github.com/lxc/lxd/pull/6602

Oh and make sure that golint lxd/cgroup is clean. It should be added to test/suites/static_analysis.sh too, that would have reported two errors with your change.

We ended up adding this since this is useful for us too: #6602

Thank you! I missed this. :)


Sending event to edges ?

Is it possible, when the system trigger an overNode event to send a OverEdges event  or even clickNode event ? Basically, what I want is that when the user pass the mousse over a node that it illuminates the nodes but also all edges adjacent to that nodes.
I try the following codes. I did receive the overnode event, I did yrçgger the overdegs event that I can also received but nothing appear on the plot/canvas.  My feeling is that the event is nit dispatched to the good layers (sigma and not the low rendering....) So your help is welcome....
// Ajouter une méthode qui donne tous les edgeId d'un noeud donné
sigma.classes.graph.addMethod('edges2neighbors', function(srcId) {
var k,
edges = {},
index = this.allNeighborsIndex[srcId] || {};
for (k in index) {
  //console.log(srcId, k)
  var index2 = this.allNeighborsIndex[srcId][k] || {};
  for (edge in index2) {
    //console.log(edge, this.edgesIndex[edge]);
    edges[edge] = this.edgesIndex[edge];
  }
}
//console.log(edges);
return edges;

});
sigInst.bind('overkNode', function(e) {
console.log(e);
var data = [];
for (var edgeId in sigInst.graph.edges2neighbors(e.data.node.label)) {
data.push(sigInst.graph.edges(edgeId));
}
console.log({nodes:data, captor: e.data.captor});
sigInst.renderers[0].dispatchEvent('overEdges', {nodes:data, captor: e.data.captor});
});

What you need to do here is basically the same thing as you do if you want to highlight a particular node & its neighbors. When you click on the node, iterate over the edges to change their color to the highlighted one if adjacent to the node, or to a muted color if not and refresh the view to highlight the adjacent edges.

Is this working for you?

doing like this, i.e., looping on all neighbours and changing the colour of the edges  and doing a refresh is very slow compare to the over edge functionality, so I wanted to just propagate the signal overdone to the adjacent edges… but I did not succeed.
eric

Eric FLEURY, Professor at ENS de Lyon / Chaire Inria
Leader of DANTE INRIA TEAM
Deputy Scientific Delegate  for Inria Grenoble Rhône Alpes
TEL: +33 (0)4 26 23 3818  +33 (0)672 162 974
WEB: http://perso.ens-lyon.fr/eric.fleury/
WEB: https://team.inria.fr/dante/
Assistant<EMAIL_ADDRESS>
Le 7 mars 2017 à 11:15, Guillaume Plique<EMAIL_ADDRESS>a écrit :
Is this working for you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/jacomyal/sigma.js/issues/834#issuecomment-284679407, or mute the thread https://github.com/notifications/unsubscribe-auth/ABWTXqvY5BGez1hB3EPTaMpTPXbcuL9Dks5rjS4ogaJpZM4MLl_u.

Oh, I see what you mean. You want to trigger the hover method to paint over the canvas to avoid the full refresh. Unfortunately this always has been tricky with sigma. But there should be a way to implement it. Let me check that with @jacomyal.

I'm also interested in this functionality, currently, iterating through the edges is way more slower than the edgehover functionality...

+1

Any example on this?

is there anyone who managed to achieve this?

I've recently implemented this for a project I'm working on and am happy to share it here. Having to call s.refresh() just for highlighting a small subset of edges is overkill indeed, especially with larger graphs. This solution only draws/highlights adjacent nodes/edges to a focal node, and allows a very performant way to show neighborhoods on hover.
Solution
The solution boils down to getting a node's adjacent edges on an overNode event and then using code from https://github.com/jacomyal/sigma.js/blob/master/src/misc/sigma.misc.drawHovers.js#L169 to highlight multiple edges at the same time.
Make sure to include the adjacentEdges (https://github.com/jacomyal/sigma.js/blob/master/plugins/sigma.plugins.filter/sigma.plugins.filter.js#L37) method for this to work properly. Assuming s is your sigma instance:
// Helper variables for hover renderers and contexts
var nodeHoverRenderers = sigma.canvas.hovers;
var edgeHoverRenderers = sigma.canvas.edgehovers;
var hoverContext = s.renderers[0].contexts.hover;
var hoverContextCanvas = hoverContext.canvas;

// Get the renderer prefix
var options = s.renderers[0].options;
var embedSettings = s.settings.embedObjects(options, {
	prefix: s.renderers[0] instanceof sigma.renderers.webgl ? 'cam0:' : options.prefix
});

// Highlight adjacent nodes and edges on node hover
s.bind('overNode', function(event) {
	var node = event.data.node;
	// Get the adjacent edges
	var adjacentEdges = s.graph.adjacentEdges(node.id);

	// Loop through the edges and highlight each of them
	// Also highlight all corresponding nodes, else edges will be drawn in front of them
	var nodesToHighlight = {};
	adjacentEdges.forEach(function(e, i) {
		var source = s.graph.nodes(e.source);
		var target = s.graph.nodes(e.target);
		nodesToHighlight[source.id] = source;
		nodesToHighlight[target.id] = target;

		if (!e.hidden) {
			// Highlight edge
			(
			  edgeHoverRenderers[e.type] ||
			  edgeHoverRenderers[embedSettings('defaultEdgeType')] ||
			  edgeHoverRenderers.def
			) (
			  e,
			  source,
			  target,
			  hoverContext,
			  embedSettings
			);
		}
	});

	// Remove the focal node from the highlight object to not highlight it twice
	delete nodesToHighlight[node.id];

	// Draw neighbors in front of highlighted edges
	for (n in nodesToHighlight) {
		(
			sigma.canvas.nodes[nodesToHighlight[n].type] ||
			sigma.canvas.nodes.def
		) (
			nodesToHighlight[n],
			hoverContext,
			embedSettings
		);
	}

	// Finally, draw the focal node hover on top of the rendered edges
	(
		nodeHoverRenderers[node.type] ||
		nodeHoverRenderers.def
	) (
		node,
		hoverContext,
		embedSettings
	);
});

Highlight color and size
You can change these using these settings:
// 'edge' for the original edge's color, or any other color, e.g. 'red'
s.settings('edgeHoverColor', 'red');
s.settings('defaultEdgeHoverColor', 'red');
s.settings('edgeHoverSizeRatio', 2);

Limitation
The only downside is that this does not play well when enableEdgeHovering is turned on, since the outEdge events are then often emitted on node hover as well, effectively hiding the highlighted edges again.
WebGL
When using the WebGL renderer, highlighted edges with a source or target outside the viewport will be drawn incorrectly because of missing camera coordinates. This can be fixed by adapting https://github.com/jacomyal/sigma.js/blob/master/src/classes/sigma.classes.camera.js#L94 and https://github.com/jacomyal/sigma.js/blob/master/src/classes/sigma.classes.camera.js#L95 to this.graph.nodes() and this.graph.edges(), which makes sure that the applyView function always calculates these coordinates for all nodes.
Hope this is of use to anyone :-)

@AVermeij This is great, thank you so much!
For a layman, please could you suggest how to augment this so that anything that is not highlighted becomes less opaque/a different colour? I've been trying for days now!

Additionally, is there anyway to control the amount by which the adjacent NODES increase in size when highlighted?

@jwscot, to give everything which is not highlighted a different colour, in the overNode event you'd have to get the adjacent nodes and edges for the hovered node (using the adjacentNodes and adjacentEdges methods), then loop through the full nodes and edges arrays to set anything which is not adjacent to another color, and then refresh the graph.
This gets expensive pretty quickly though, since it would mean looping arrays and a full sigma refresh every time a node is hovered. I think you might be better off binding this to a clickNode event instead?
To increase the size of adjacent nodes, you could set nodesToHighlight[n].size in the code above to any value when looping the object:
// Draw neighbors in front of highlighted edges
for (n in nodesToHighlight) {
  nodesToHighlight[n].size = 10;
  ... etc.
}


Move functionality for TransformFactory inside CryptoProviderFactory and remove TransformFactory

We need to abstract the obtaining XMLTransforms, the natural place for that is CryptoProviderFactory.

We may not be able to move the TransformFactory into M.IM.Tokens as the transforms need Xml support in M.IM.Xml. We may just have to leave it in M.IM.Xml

For release 5.2.0, we are going to hide extensibility for transforms. We will move things around a bit so that in the future we can add extensibility here, but not for 5.2.0.

For now we are going to just put classes in correct ns.


Nf/modal closing issue

updated the closing modal related function names and logics, also the "go" button issue also fixed, it no longer asks for confirmation.

🚢


Unable to render an i18n translation

Done as doc, but it posts an error:
bootstrap-wysihtml5.zh-CN.js:5
Uncaught TypeError: Cannot set property 'zh-CN' of undefined

The error lines are:
(function($){
    $.fn.wysihtml5.locale["zh-CN"] = {
        font_styles: {
        normal: "正文",
        h1: "标题 1",
        h2: "标题 2",
        h3: "标题 3"
        },

Hey @serser please take a look at this issue #322
It may help you with the error you get.


Fixed MessageQueue and callers

+1 nice, thanks

+1, fixes https://github.com/FreeRDP/FreeRDP/issues/2282 for me!

@freerdp-bot test

I have been really bad on my last changes, fortunately @nfedera kept his eyes opened ! Thank you Norbert.

@freerdp-bot test

test this

@freerdp-bot test

@freerdp-bot test

ok to test.

@hardening nice! +1

This PR may break shadow server.
commit c75ba04d727e1e58477c6cd1f302892cbad05e28
Merge: 4586450 84ae1d1
Author: Hardening<EMAIL_ADDRESS>Date:   Fri May 29 14:38:58 2015 +0200
Merge pull request #2647 from hardening/fix_message_queue

Fixed MessageQueue and callers

It works at 4586450 but is broken in c75ba04d727e1e58477c6cd1f302892cbad05e28
I may need to look into it to figure out what is wrong. Maybe it's just existing bug in shadow server exposed by this PR

@realjiangms could you open an issue and give more details about "break shadow server" ? I think the suppress_output cb would be a good candidate...

It could be. I'll open issue and handle it after work (maybe 6 hours later, my timezone is UTC+8)I find the PR which breaks it yesterday evening but I can't post message in github so I post it at lunch time
I can't access my computer at home since I'm in office. I'll track it down when I arrive home. It should be easy to find the root cause and fix.
ThanksZihao
 Hardening<EMAIL_ADDRESS>于 2015年6月8日, 星期一, 下午 1:24 写道：

@realjiangms could you open an issue and give more details about "break shadow server" ? I think the suppress_output cb would be a good candidate...—
Reply to this email directly or view it on GitHub.

@hardening Just had a quick look: This is the erroneous change:
https://github.com/FreeRDP/FreeRDP/commit/c75ba04d727e1e58477c6cd1f302892cbad05e28#diff-ef96aaa15084e45264f6fd50008f2365R261
shadow_client_refresh_rect() may be (and actually is) called with count == 0 which means to refresh everything. Thus the combination count == 0 and areas == NULL are valid parameters. I'd suggest to change the "if (!areas)" to "if (count && !areas)" before returning FALSE.

@hardening @realjiangms here's the (unmerged) fix: https://github.com/FreeRDP/FreeRDP/pull/2683

Thanks. I just arrive home, too much work in office.That's also what I got from code review. This looks an original existing issue which exposed by the PR
The hardening's PR itself is correct
 Norbert Federa<EMAIL_ADDRESS>于 2015年6月8日, 星期一, 下午 10:00 写道：

@hardening @realjiangms here's the (unmerged) fix: #2683—
Reply to this email directly or view it on GitHub.


Update Helm release mimir-distributed to v4

This PR contains the following updates:

Package
Update
Change

mimir-distributed (source)
major
3.0.0 -> 4.2.0

Release Notes

grafana/helm-charts
v4.2.0
Compare Source
Grafana Mimir
Source commit: https://github.com/grafana/mimir/commit/f76cdf4491b9838377a382cb7204f1ef987de275
Tag on source: https://github.com/grafana/mimir/releases/tag/mimir-distributed-4.2.0
v4.1.0
Compare Source
Grafana Mimir
Source commit: https://github.com/grafana/mimir/commit/d9726f9d449633471355fee67c98ea6bc1e513dd
Tag on source: https://github.com/grafana/mimir/releases/tag/mimir-distributed-4.1.0
v4.0.1
Compare Source
Grafana Mimir
Source commit: https://github.com/grafana/mimir/commit/1852e09b0065bfe4a8fd16352c174f77661275ff
Tag on source: https://github.com/grafana/mimir/releases/tag/mimir-distributed-4.0.1
v4.0.0
Compare Source
Grafana Mimir
Source commit: https://github.com/grafana/mimir/commit/09c887f80c392eca9b70adc407a3a02395d3ecaf
Tag on source: https://github.com/grafana/mimir/releases/tag/mimir-distributed-4.0.0
v3.3.0
Compare Source
Grafana Mimir
Source commit: https://github.com/grafana/mimir/commit/65c4cc3cb1e19a2fefb4bed340bfc5165b739dc5
Tag on source: https://github.com/grafana/mimir/releases/tag/mimir-distributed-3.3.0
v3.2.0
Compare Source
Grafana Mimir
Source commit: https://github.com/grafana/mimir/commit/fb376c5eee844990da26feb262c318a49d7aeae0
Tag on source: https://github.com/grafana/mimir/releases/tag/mimir-distributed-3.2.0
v3.1.0
Compare Source
Grafana Mimir
Source commit: https://github.com/grafana/mimir/commit/c8be0e3a3a8c72854f7a7008bf8de182d96b7150
Tag on source: https://github.com/grafana/mimir/releases/tag/mimir-distributed-3.1.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

There are 3 breaking changes.
Only one of them affects us:

[CHANGE] breaking change Data loss without action. Enables zone-aware replication for ingesters and store-gateways by default. grafana/mimir#2778

We would need to write a migration guide. All required steps are documented https://grafana.com/docs/helm-charts/mimir-distributed/latest/migration-guides/migrate-from-single-zone-with-helm/ we just need to translate them to the commodore rendering way.
Do not affect us:

[CHANGE] breaking change Reduce the number of ingesters in small.yaml form 4 to 3. This should be more accurate size for the scale of 1M AS. Before upgrading refer to Scaling down ingesters to scale down ingester-3. Alternatively override the number of ingesters to 4. grafana/mimir#3035

We set the replicas ourselves already https://github.com/projectsyn/component-mimir/blob/e7ea9ed17d12999091657f1bca2914527e46838e/class/defaults.yml#L73
We could argue that we should implement the smaller value as the component will include a breaking change anyways.

[CHANGE] breaking change Update minio subchart from 4.0.12 to 5.0.0, which inherits the breaking change of minio gateway mode being removed.

We never used gateway mode.


Remove devfile integration test dependency on git clone

What type of PR is this?
/kind cleanup
/kind flake
What does does this PR do / why we need it:

Removes external dependency on git clone for integration tests, PR now has sample project in the examples dir, and copies it for performing the integration test
update .gitignore to list DS_Store

Which issue(s) this PR fixes:
#3020
How to test changes / Special notes to the reviewer:
make

@cdrage can you pls add the approved label as well? thx

Will need another maintainer review, ping @openshift/odo-maintainers-1

Will need another maintainer review, ping @girishramnani @kadel @dharmit @mik-dass

I don't have the approval rights. Sorry.

/retest

/approve

/test v4.4-integration-e2e

@cdrage could you pls rer-eview/re-add lgtm label?

/lgtm

/retest

/test v4.4-integration-e2e

/retest

/test v4.2-integration-e2e


add menu item to open chipmunk logfile

since we do a logviewer, it would be nice to make it possible to open our own logfile easily

I am not sure it would be needed for users as soon as we have a button "Get Chipmunk Logs" in "About" tab. Please someone reopen if I'm wrong.


Add multi-arch support to docker image

I recently migrated my metrics server to a Raspberry Pi and discovered that my I could no longer run this image. I've added arm64 support to my own fork and figured I might as well submit a PR.
I've added a copy of the build script that handles multi-arch docker builds while trying to make as few changes as possible. It handles building for both linux/amd64 and linux/arm64. A couple notes on the build script:

The target architectures are hardcoded right now.
The easiest way to push docker buildx images is to use a single build call which include all of the desired tags and pushes the built images. That's what the odd bash array of image tag arguments is for (relevant commit).

The original (unmodified) build script continues to work fine with the Dockerfile changes i've made.
I've pushed an image made with these changes to my own docker hub repo as an example result.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (cb323ff) 74.53% compared to head (8824983) 74.53%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #23   +/-   ##
=======================================
  Coverage   74.53%   74.53%
=======================================
  Files           7        7
  Lines         644      644
=======================================
  Hits          480      480
  Misses        131      131
  Partials       33       33

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Hi @kylekingcdn thanks for the PR!
Upon further investigation, I realized that ./hack/push-docker.sh is not actually used by the GitHub Action for Docker release (the manual push-docker.sh script was added first, before the GitHub release.yml action was added later in #9).
As such, it does seem like we should be updating the release.yml action to automatically release a multi-arch image, rather than adding a new push-docker-multiarch.sh Bash script (which would only be useful for doing a manual release).
I'll look into updating the release.yml shortly in a separate PR. Nevertheless, thanks for your input!

For sure, that makes sense.
And yes thank you, adding support for arm64 docker support would be great.


Padding constructors

I got way too excited about the idea of convenient Padding constructors.

Container has an assert to verify non-negative padding:
https://github.com/flutter/flutter/blob/32cb866d3a617a108774761cbe9a1265bd25dc2d/packages/flutter/lib/src/widgets/container.dart#L269
But this currently isn't used in the actual Padding class, since it won't work in a constant context.
Fortunately, these new constructors can all be const with the relevant asserts.

Will un-draft this once there's an issue for it 🙂

Closing for now… will reopen once we have more information about upcoming language features!


Cherry-pick PR #6642 into release-1.0: ci: stop using set-env

What this affects:
LBT workflow in GH Actions.
Why is this critical:
It addresses the vulnerability found by Google's project-zero (see details in PR landed in master #6642). The set-env cmd will be deprecated soon (https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).
What is the workaround:
Disable LBT workflow.
Testing:
Canary.

/canary

:sunny: Canary successful

/land


Connection error

Hi
I'm wondering if the server is up. Because I'm getting connection error meanwhile trying to get it working.
Command:
curl -v -H "Content-type: application/pdf" --data-binary 45601881.pdf "http://scienceparse.allenai.org/v1"
Error:
curl: (7) Failed to connect to scienceparse.allenai.org port 80: Connection refused

same


Allow stale_bq_datasets_cleaner.sh to run to completion, even when there are failures to grab a dataset

Also, add a little more logging on failed commands.
Right now, its common for a dataset to be present at the start of the run and then to disappear by the time the cleaner gets to it (for ephemeral test datasets). This will allow those to be skipped.
This was permared before this change - https://github.com/apache/beam/actions/workflows/beam_CleanUpGCPResources.yml
Example run with this change - https://github.com/apache/beam/actions/runs/7731108048

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @Abacn


Observability White Paper Review

Awesome job
Few tiny corrections.
Addition of SL* examples.
Few extra comments

"Three in four teams have yet to begin or are early in their observability journeys" and that "There is momentum behind the shift toward achieving more observable systems"

This statement is contradictory?

https://github.com/cncf/tag-observability/blob/main/whitepaper.md#profiles

There is no mention of

standardization
transport - how is it egested/ingested?

Thanks for taking a look at the paper!
The problem is that I'm not a member of the CNCF org, so I can't merge your changes 😬. Do you mind opening this PR against my fork?
https://github.com/ArthurSens/sig-observability/tree/public-review

https://github.com/ArthurSens/sig-observability/pull/3


Can't set secret and its value using Azure.Security.KeyVault.Secrets SDK

I'm using Azure.Security.KeyVault.Secrets v4.3.0 and the method SetSecretAsync of SecretClient. It's failing with following error:
System.TypeInitializationException: "The type initializer for 'Azure.Security.KeyVault.Secrets.KeyVaultSecret' threw an exception." ---> System.IO.FileNotFoundException: "Could not load file or assembly 'System.Text.Encodings.Web, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.\n"
  --- End of inner exception stack trace ---
  at at Azure.Security.KeyVault.Secrets.KeyVaultSecret.WriteProperties(Utf8JsonWriter json)

I'm using Visual Studio Community 2019 for Mac, Version 8.10.22 (build 11).
The project is Azure Functions application. I'm debugging it locally using Azure Functions tools.
I cleared up the NuGet cache, removed all stalled System.Text.Encodings.Web assemblies on my Mac.
Here is the list of references across 4 different projects within the solution that reference each other:
project 1:
<ItemGroup>
    <PackageReference Include="Azure.Core" Version="1.24.0" />
    <PackageReference Include="Azure.Security.KeyVault.Certificates" Version="4.3.0" />
    <PackageReference Include="Azure.Security.KeyVault.Keys" Version="4.3.0" />
    <PackageReference Include="Azure.Security.KeyVault.Secrets" Version="4.3.0" />
    <PackageReference Include="FluentValidation" Version="10.4.0" />
    <PackageReference Include="FluentValidation.DependencyInjectionExtensions" Version="10.4.0" />
    <PackageReference Include="Microsoft.FeatureManagement" Version="2.5.1" />
    <PackageReference Include="Newtonsoft.Json" Version="13.0.1" />
    <PackageReference Include="Microsoft.Extensions.Logging.Abstractions" Version="3.1.24" />
    <PackageReference Include="Azure.ResourceManager.KeyVault" Version="1.0.0-beta.6" />
    <PackageReference Include="MediatR.Extensions.Microsoft.DependencyInjection" Version="9.0.0" />
    <PackageReference Include="AutoMapper.Extensions.Microsoft.DependencyInjection" Version="8.1.1" />
    <PackageReference Include="AutoMapper" Version="10.1.1" />
  </ItemGroup>

project 2:
<ItemGroup>
    <PackageReference Include="Microsoft.Extensions.Configuration.AzureKeyVault" Version="3.1.23" />
    <PackageReference Include="Microsoft.Azure.Functions.Extensions" Version="1.0.0" />
    <PackageReference Include="Microsoft.Azure.WebJobs.Extensions.Storage" Version="4.0.5" />
    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="3.1.13" />
    <PackageReference Include="Microsoft.FeatureManagement.AspNetCore" Version="2.4.0" />
    <PackageReference Include="Microsoft.NET.Sdk.Functions" Version="3.1.0" />
  </ItemGroup>

project 3:
<ItemGroup>
    <PackageReference Include="Azure.Data.Tables" Version="12.5.0" />
    <PackageReference Include="Azure.Storage.Queues" Version="12.9.0" />
  </ItemGroup>

project 4:
<ItemGroup>
    <PackageReference Include="Microsoft.Azure.Management.Fluent" Version="1.38.1" />
    <PackageReference Include="Microsoft.Extensions.Logging" Version="3.1.6" />
    <PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="3.1.20" />
    <PackageReference Include="Microsoft.Extensions.Options" Version="3.1.20" />
    <PackageReference Include="Azure.Identity" Version="1.6.0" />
    <PackageReference Include="Azure.ResourceManager" Version="1.0.0-beta.8" />
  </ItemGroup>

Project 4 from the list above has the code that is failing. It references project 1. Project 1 references project 3.
Project 2 (main project) references project 4 and project 1.
Looks like some package is messing everything up or this is the bug in Azure.Security.KeyVault.Secrets.
Do you have any guidance about Azure SDK on which versions of mentioned packages can be used together?
Thanks in advance.

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

This is likely due to an older copy the Azure Functions SDK copied to output. Update to the latest Microsoft.NET.Sdk.Functions and, if that still repos, find and delete any copies of System.Text.Encodings.Web, then build again and deploy.
For more information, please see #23902.

Thanks for replying back.
Yeah, I did that many times: removed bin & obj, cleared NuGet caches, I also removed all assemblies I could find on my machine.
As for SDK, I'm using Microsoft.NET.Sdk.Functions, Version="3.1.0". Are you saying that this SDK is not valid anymore and I have to switch to version 4?
I also tried setting the property you mentioned - it didn't work. Same issue.

After multiple tries to pick up a correct combination of versions I found that it's working without TypeInitializationException with "Microsoft.NET.Sdk.Functions" Version="3.0.11".
I'll stick with this old version for now.

I've started a thread with the Azure Functions SDK team and we'll work to resolve this. Could you tell me the file version of System.Text.Encodings.Web you found that is getting loaded?

Thanks for working on this.
I saw 4.7.2 version of System.Text.Encodings.Web and it was referenced by multiple packages including "Azure.Security.KeyVault.Secrets" one.
Btw, it's not that easy to investigate this type of issues with Visual Studio for Mac :)

@heaths was there any follow-up with the function team here?

Sorry, but this seems to have slipped through the cracks. Was this still a problem? Dependencies across the Azure Functions runtime, PowerShell support, etc., have all since been updated so I'm hopeful this is no longer a problem.

yeah, this was more than a year ago :)
I bet we already migrated to a newer .NET version and newer runtime since then. I haven't heard about such issues tbh. Let's consider this as addressed. I will reach out if it is not.


Setup Travis CI (add .travis.yml)

I recently picked this repo back up ... and spent a lot of wasted time trying to get specs to pass, because I was assuming that they had been passing when I left off with this repo. False assumption! Apparently I hadn't run tests after making some changes.
By having CI, I'll be sure to not make that mistake again. :)
I expect the tests to actually fail (since that's the state in which I had left them), but I'm going to merge despite that failure and fix the specs in a subsequent PR.

Actually, it looks like specs pass. So the above recriminations of myself apparently weren't justified. 😛  But I think that tests will fail after I do a bundle update (specifically maybe because of a change to Capybara where elements that are not visible to the browser are now default ignored, whereas before they were default acknowledged.)
Anyway, merging.


[Support] unattended install on an EC2 instance fails with "no such file or directory"

In raising this issue, I confirm the following:

[X] I have read and understood the contributors guide.
[X] The issue I am reporting can be replicated.
[X] The issue I am reporting can be is directly related to the pivpn installer script.
[X] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Issue
I have an install script in user-data which will do an unattended install of PiVPN on an EC2 instance running Ubuntu 20.04:
When I run this script from the command prompt everything's fine. When it runs from user-data it fails.
The script:
# Create options file
cat << EOF > /root/options.conf
USING_UFW=0
IPv4dev=ens5
install_user=ubuntu
install_home=/home/ubuntu
VPN=openvpn
pivpnPROTO=udp
pivpnPORT=1194
pivpnDNS1=<IP_ADDRESS>
pivpnDNS2=<IP_ADDRESS>
pivpnSEARCHDOMAIN=
TWO_POINT_FOUR=1
pivpnENCRYPT=521
USE_PREDEFINED_DH_PARAM=0
INPUT_CHAIN_EDITED=0
FORWARD_CHAIN_EDITED=0
pivpnDEV=tun0
pivpnNET=<IP_ADDRESS>
subnetClass=24
UNATTUPG=1
EOF
# Install PiVPN from options.conf
cd /root
curl -L https://install.pivpn.io > install.sh
chmod +x install.sh
./install.sh --unattended options.conf

Error:
Checking /usr/local/src/pivpn is a repo...:::    Cloning https://github.com/pivpn/pivpn.git into /usr/local/src/pivpn...    #010#010#010#010./install.sh: line 1035: cd: /usr/local/src/pivpn: No such file or directory

The directory is created however:
/usr/local/src/pivpn# ls -la
total 152
drwxr-xr-x 8 root root  4096 Dec 24 14:20 .
drwxr-xr-x 3 root root  4096 Dec 24 14:20 ..
drwxr-xr-x 2 root root  4096 Dec 24 14:20 auto_install
-rw-r--r-- 1 root root  3253 Dec 24 14:20 CODE_OF_CONDUCT.md
-rw-r--r-- 1 root root  1281 Dec 24 14:20 CONTRIBUTING.md
drwxr-xr-x 2 root root  4096 Dec 24 14:20 examples
drwxr-xr-x 3 root root  4096 Dec 24 14:20 files
drwxr-xr-x 8 root root  4096 Dec 24 14:20 .git
drwxr-xr-x 3 root root  4096 Dec 24 14:20 .github
-rw-r--r-- 1 root root     7 Dec 24 14:20 .gitignore
-rw-r--r-- 1 root root 15410 Dec 24 14:20 LatestUpdate.md
-rw-r--r-- 1 root root  1075 Dec 24 14:20 LICENSE
-rw-r--r-- 1 root root 74614 Dec 24 14:20 logos.jpg
-rw-r--r-- 1 root root  9379 Dec 24 14:20 README.md
drwxr-xr-x 4 root root  4096 Dec 24 14:20 scripts

I'm out of ideas. I've been looking at the installer script but I can't seem to figure out a workaround for this. It does seem to be some kind of race condition in which the directory isn't yet available when the check is done.
Have you searched for similar issues and solutions?
Searched, found a few, but not about EC2.
Console output of      curl -L install.pivpn.dev | bash
Not relevant since only the unattended install fails.

Console output of      pivpn add or pivpn add nopass
None, since the installer fails.

Console output of      pivpn debug
None, since the installer fails.

Have you taken any steps towards solving your issue?
I tried running it from a different directory and using a different shell, to no avail.

User data runs quite early in the boot process, that might be why, will try to investigate a bit more about this

I had a look at this, I now execute the commands 5 minutes after the EC2 instance had launched. The same error occurs however.
Cloning https://github.com/pivpn/pivpn.git into /usr/local/src/pivpn..../install.sh: line 1035: cd: /usr/local/src/pivpn: No such file or directory

It still looks like a race condition somewhere, I'll try some more things...

I had a look at this, I now execute the commands 5 minutes after the EC2 instance had launched. The same error occurs however.
Cloning https://github.com/pivpn/pivpn.git into /usr/local/src/pivpn..../install.sh: line 1035: cd: /usr/local/src/pivpn: No such file or directory

It still looks like a race condition somewhere, I'll try some more things...

Haven't dived into this one yet, but seems pivpn is also lacking some checks for directories ...

Playing around a bit with this ...

Hetzner: Was able to run unattended  during user-data and verified running

OS: debian 11

AWS: Was able to run unattended during user-data and verified running

OS: Debian 11
AMI-ID: ami-045c4a673232682a2
region: eu-north-1

How I did it:
I mostly use terraform to spin up infrastructure, and rarely interact with aws console, and provided the following script as user data:
$cat pivpnuserdatatest.sh
#!/bin/bash

apt update && apt install -y git
git clone https://github.com/pivpn/pivpn /tmp/pivpn
cd /tmp/pivpn || exit
bash ciscripts/startup.sh -o
bash auto_install/install.sh --unattended ciscripts/ci_openvpn.conf

will add this to docs.

Here's another variation of the OP script:
#!/bin/bash
# Create options file
cat << EOF > /tmp/options.conf
USING_UFW=0
IPv4dev=ens5
install_user=admin
install_home=/home/admin
VPN=openvpn
pivpnPROTO=udp
pivpnPORT=1194
pivpnDNS1=<IP_ADDRESS>
pivpnDNS2=<IP_ADDRESS>
TWO_POINT_FOUR=1
pivpnENCRYPT=256
USE_PREDEFINED_DH_PARAM=1
INPUT_CHAIN_EDITED=0
FORWARD_CHAIN_EDITED=0
pivpnDEV=tun0
pivpnNET=<IP_ADDRESS>
subnetClass=24
UNATTUPG=1
EOF
# Install PiVPN from options.conf
apt update && apt install -y git
git clone https://github.com/pivpn/pivpn /tmp/pivpn
cd /tmp/ || exit
bash pivpn/auto_install/install.sh --unattended /tmp/options.conf

committed to docs: https://github.com/pivpn/docs/commit/ed83004f04248132740393fdb0e36971c98302bd
Available at: https://docs.pivpn.io/guides/user-data/
closing...


Expose Stat Send Interval to Config

Have been playing with this tool and it's pretty handy. Worked out of the box on most devices. I've turned off most of the stats for most client devices, as it's pretty noisy. I had a brief look at the timer and the interval is 5 seconds, is it possible to expose this as an optional setting in the config?
Plenty of functions in linux to get CPU averages over X period as well, I didn't dig to see if the CPU usage now is instantaneous or average.

That's a good idea to make it configurable.
I am going to change this on the first change I get.
This is the code that is responsible for the timer:
https://github.com/bkbilly/lnxlink/blob/master/lnxlink/__main__.py#L72

I've exposed it to the config as an update_interval.
The default is 5 seconds if it doesn't exist on the config file, which means that you have to write it yourself.


simplify emacs-setup instructions

https://github.com/leanprover/lean/pull/423#issuecomment-72707904
@leodemoura, could you run the following elisp code in windows environments (Native Emacs and msys2 Emacs)?
(message "%S" system-type)

On native Emacs for Windows:  "windows-nt"
On msys2 terminal Emacs for Windows: I will have to give you a "rain check".
I only have msys2 in my office at MSR. I will try it next Monday.

I didn't go to the office today.

Thank you. No rush please :-)

msys2 does seem to provide a precompiled emacs. I tried to find instructions on the web, and all-of-them were about how to compile emacs from sources.
On cygwin, the result of (message "%S" system-type) is cygwin.


previews: Fix memory leak in DRM preview

"bo_handles" need to be closed, and although I can't find a "regular"
API call there does appear to be a DRM ioctl that does this.
Signed-off-by: David Plowman<EMAIL_ADDRESS>

This seems to fix https://github.com/raspberrypi/libcamera-apps/issues/303 for me. I think it's the correct solution, though I can't claim any great expertise on DRM...

Good enough for me.


Adding initial changelog with sprint66 data

@miq-bot add_label documentation

@Fryguy updated as per our conversation. Please merge.


docs: add langchain integration docs

The package.json needs to be updated in these docs once the langchain integration is released, will leave it in draft for now because its not merge-able yet.

@SocketSecurity ignore<EMAIL_ADDRESS>@SocketSecurity ignore<EMAIL_ADDRESS>


Change internal graphql authentication to oauth2-lib package

Codecov Report

Merging #259 (5d6a021) into main (947769e) will increase coverage by 0.26%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #259      +/-   ##
==========================================
+ Coverage   78.02%   78.29%   +0.26%
==========================================
  Files         130      129       -1
  Lines        7523     7468      -55
  Branches     1235     1230       -5
==========================================
- Hits         5870     5847      -23
+ Misses       1468     1437      -31
+ Partials      185      184       -1

Impacted Files
Coverage Δ

orchestrator/settings.py
100.00% <ø> (ø)

orchestrator/graphql/__init__.py
87.03% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Remove unused sections from drawer for first app release

Hide behind a feature toggle?
Use https://pub.dev/packages/firebase_remote_config?
Use https://pub.dev/packages/feature_flag?

I will use local feature toggle for handling this

Add Release Toggles. These are feature flags used to enable branch based development for us practicing continuous enhancment.


Configurable WHO IS ON-CALL list

Currently, the behavior of the WHO IS ON-CALL tab is to show six cards at a time. It'd be really valuable to have a property accessible that allowed to customize how many cards are shown per page. Also perhaps a boolean to simply disable pagination altogether.

Duplicate of #76


plugins/aerial: init

Add support for aerial.nvim, a plugin for a code outline window.
Fixes #2514

Yeah, if we're going to document this many options it'd be nice to have rawLua support for everything, in case we don't map things up properly.

@mergifyio queue


chore: update module checks workflow

Describe your changes

updated get-modules workflow to only run tests against changed files in modules/**
adds workflow specific to changes for requirements-dev.txt so all static checks are run

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: b676b324e24565841dd043840defff83175a78a9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


As an AST holder I want to be able to stake my tokens within the AirSwap web app

Requirements:

View how many tokens I'm able to stake (wallet balance)
Have a open input to specify amount
Put in how much % of wallet balance I want to stake
Know how much time it takes to unstake tokens that you're about to stake: info in Figma > rewrite it and add to UI
Have a quick link to buy $AST

Idea:
Put in example amount, to see how much and when the tokens will unlock > in a visual


Master.refine import path

Description

Linked issue(s)/Pull request(s)

issue_number

Type of Change

[ ] Non-breaking bug fix
[ ] Breaking bug fix
[ ] New feature
[ ] Test
[ ] Doc update
[ ] Docker update

Related Component

[ ] Simulation toolkit
[ ] RL toolkit
[ ] Distributed toolkit

Has Been Tested

OS:

[ ] Windows
[ ] Mac OS
[ ] Linux

Python version:

[ ] 3.6
[ ] 3.7

Key information snapshot(s):

Needs Follow Up Actions

[ ] New release package
[ ] New docker image

Checklist

[ ] Add/update the related comments
[ ] Add/update the related tests
[ ] Add/update the related documentations
[ ] Update the dependent downstream modules usage

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8c800d7). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   72.06%
=========================================
  Files             ?       86
  Lines             ?     4066
  Branches          ?        0
=========================================
  Hits              ?     2930
  Misses            ?     1136
  Partials          ?        0

Flag
Coverage Δ

unittests
72.06% <0.00%> (?)

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

Continue to review full report at Codecov.

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


Add cookie secure flag.

At the moment, skymarshal sets the secure cookie flag if the atc is terminating tls connections. But operators may terminate tls at a proxy in front of the atc, like elb, nginx, etc. In this case, operators should still be able to set secure on cookies. This patch adds a CookieSecure flag that forces secure cookies.
cc @wjwoodson

Thanks!
@pivotal-jwinters Are there tests to be added here?

Added some tests.

thanks!


Disable MemoryReserveLockedToMax

An option was added in vSphere 5.0 called MemoryReservationLockedToMax which ensures all memory is reserved for the guest as the guest memory size changes.  Some VCs fail the reconfigure task setting the memoryAllocation.reservation to be less than the total if memoryReservationLockedToMax is set.  The fix is to explicitly disable this value if the memory reservation is less than total guest memory.
Depends on: https://github.com/ManageIQ/manageiq-gems-pending/pull/8
https://bugzilla.redhat.com/show_bug.cgi?id=1384122

:+1: LGTM

Euwe backport details:
$ git log -1
commit bf6afbd3ae4f99c561f90f5b617283a5c1b28f2a
Author: Greg Blomquist<EMAIL_ADDRESS>Date:   Wed Nov 30 10:16:16 2016 -0500

    Merge pull request #12450 from agrare/vmware/infra/bz_1384122_vm_memory_reservation

    Disable MemoryReserveLockedToMax
    (cherry picked from commit df363f1bde88d5c9850e3a7a67b343924b5df96b)

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


permission role not added when creating bread

Laravel Version: 5.3
Voyager Version: 0.10.8
PHP Version: 5.6.20
Database Driver & Version: mySQL - 5.6.20

Permissions not generated when submitting new bread. I have to run php artisan db:seed --class=PermissionRoleTableSeeder to complete table permission_role.
Is this normal?
I followed the installation in the docs.

Try upgrade Voyager and see if this still happens for you.

I have the same problem described above. Just upgraded to version 0.10.16 and the permissions are still not generated when creating bread. :-(

v0.10.x is no longer being developed.
I recommend upgrading to v0.11.

installing a fresh Laravel and Voyager project give same error. Using "tcg/voyager": "^0.11.3"

Did you have any errors or warnings when running the installation first time?

I am also still running into this problem in 0.11.4 after a flawless installation. Running php artisan db:seed --class=PermissionRoleTableSeeder fixes the issue.

Have the same issue. Please add this to the documentation. I'm a new to voyager and it costs me a few hours to find out what's wrong!

@Iphoning, this has been closed for 6 months.  Please open your own issue if needed


(depends on good sell shares estimate) sell shares tx fails, cuz minAmount is zero

Issue is that min amount is zero.  It's zero because slippage from estimate sell is wrong.
temporary work-around: By setting min amount to 0.01 USDC the transaction is confirmed.
params used to call sellForCollateral:
0x397018eFcC4780921D932ef67455E8Af0eCC4efA
marketId 11
outcome 0
amount<PHONE_NUMBER>000000000
min amount 0

sell shares estimate is successful but tx fails. MM gas estimate fails as well
https://kovan.etherscan.io/tx/0x238b0b3229e0ba542b19c58afaa98bbed4abba1579856c80f0dc9778d2747ae4

balancer pool contract isn't verified so tenderly isn't helpful.

This is due to the changes @justinbarry made. Now there's no longer a min amount.  To add potential slippage you would increase the amount, so you have more wiggle room.

we'll need to do testing and changes if we need to address failed transactions because min amount complete sets is too optimistic.


Remove dotenv

Dotenv has caused some errors in downstream projects; probably not a mechanism we want to use in a library

Codecov Report

:exclamation: No coverage uploaded for pull request base (trunk@7879616). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             trunk       #57   +/-   ##
=========================================
  Coverage         ?   100.00%
=========================================
  Files            ?         9
  Lines            ?       213
  Branches         ?         0
=========================================
  Hits             ?       213
  Misses           ?         0
  Partials         ?         0

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 7879616...b826339. Read the comment docs.


Db connection pooling

 You should sign our Contributor License Agreement in order to get your pull request merged.

All is well.


BUG: rsync issue with artifact synchronization (ubuntu-latest)

The issue
After building an artifact (tested with 250MB artifact), Github Action fails with the following error:
[Symfony\Component\Process\Exception\ProcessFailedException]
  The command "rsync -azP -e 'ssh -A -p *** -o UserKnownHostsFile=/dev/null
   -o StrictHostKeyChecking=no' 'artifacts/artifact.tar.gz' 'deploy@ssh.XXX.io:/srv/releases/2009076181'" failed.

  Exit Code: 255(Unknown error)

  Working directory: /__w/XXX-magento2/XXX-magento2

  Output:
  ================
  sending incremental file list
  artifact.tar.gz
         32,768   0%    0.00kB/s    0:00:00

  Error Output:
  ================
  client_loop: send disconnect: Broken pipe

  rsync: [sender] write error: Broken pipe (32)
  rsync error: unexplained error (code 2[55](https://github.com/XXX/XXX-magento2/runs/5612222340?check_suite_focus=true#step:7:55)) at io.c(823) [sender=3.2.3]

Conditions

Usually, the failure happens after the first 3MB.
The issue does not happen on self-hosted runner

Solution
The issue is caused by an invalid rsync configuration. In order to mitigate the issue, you need to add an extra option --bwlimit=... to rsync configuration:
Example:
task('artifact:upload', function () {
    upload(get('artifact_path'), '{{release_path}}', ['options' => ['--bwlimit=4096']]);
});

Awesome! Can you add this to deployphp/deployer docs section?

@antonmedv Done.


Add anonevents

🔹 Jira Ticket(s)

MOB-XXXX

✏ Description

Please provide a brief description of what this pull request does.

this is the video showing functionality: https://drive.google.com/file/d/18L_f-0CqL6onjHLcMMPVmNHRgrQxIzeO/view?usp=sharing


Error loading config.json. Please check your config.json file: ReferenceError: Headers is not defined

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: MacOS
- Continue: pre-released version and latest version
- IDE: VsCode

Description
While adding a localmodel of ollama it throws error

{
  "models": [
    {
      "title": "GPT-4 (Free Trial)",
      "provider": "free-trial",
      "model": "gpt-4"
    },
    {
      "title": "GPT-4 Vision (Free Trial)",
      "provider": "free-trial",
      "model": "gpt-4-vision-preview"
    },
    {
      "title": "Gemini Pro (Free Trial)",
      "provider": "free-trial",
      "model": "gemini-pro"
    },
    {
      "title": "Codellama 70b (Free Trial)",
      "provider": "free-trial",
      "model": "codellama-70b"
    },
    {
      "title": "Code Llama",
      "provider": "ollama",
      "model": "codellama-7b"
    }
  ],
  "slashCommands": [
    {
      "name": "edit",
      "description": "Edit selected code"
    },
    {
      "name": "comment",
      "description": "Write comments for the selected code"
    },
    {
      "name": "share",
      "description": "Download and share this session"
    },
    {
      "name": "cmd",
      "description": "Generate a shell command"
    }
  ],
  "customCommands": [
    {
      "name": "test",
      "prompt": "Write a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
      "description": "Write unit tests for highlighted code"
    }
  ],
  "contextProviders": [
    {
      "name": "diff",
      "params": {}
    },
    {
      "name": "open",
      "params": {}
    },
    {
      "name": "terminal",
      "params": {}
    },
    {
      "name": "problems",
      "params": {}
    },
    {
      "name": "codebase",
      "params": {}
    }
  ]
}

To reproduce
No response
Log output
No response

@slice-sarthakd I've seen this in situations where the node version used to run VS Code is out-of-date. If you click the about menu, can you share what Node version it lists? You might have luck by installing the latest of VS Code, but if not let me know!

Upgrading to latest vscode version solved it. Thanks!

I'm using the latest visual studio code and I'm having this problem

@slice-sarthakd I've seen this in situations where the node version used to run VS Code is out-of-date. If you click the about menu, can you share what Node version it lists? You might have luck by installing the latest of VS Code, but if not let me know!

Yes, I have to use a customized VSCode, which is based on 1.81.3, with Node.JS 16.17.1. Any suggestion to solve this?


ReferenceError: exports is not defined in ES module scope

I've just tired to updated to 2.1.1 of vue3-dropzone, which I use in a nuxt3 app (3.7.0) and got this error:
ReferenceError: exports is not defined in ES module scope This file is being treated as an ES module because it has a '.js' file extension and '..../node_modules/vue3-dropzone/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.
I think it is caused by these changes: https://github.com/Yaxian/vue3-dropzone/commit/6ca201ca947a801ad3a9a5ccd5f1e360adab8aca#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519
I can't figure out how to solve this, so I went back to 2.0.1
Is it because of my nuxt/typescript settings?

Thanks for this case.
It maybe have wrong with my package.json setting. I wanna support esm.
I will test with nuxt3 and try fix it.


Oops; flutter has exited unexpectedly.

Whenever I try to run flutter command, I get this issue.

Oops; flutter has exited unexpectedly.
Sending crash report to Google.
Crash report sent (report ID: d47fa39ff302d5a3)
Crash report written to C:\Program Files (x86)\Microsoft Visual Studio\2019\Com
unity\flutter_01.log;
please let us know at https://github.com/flutter/flutter/issues.

This is the flutter_01.log content.

Flutter crash report; please file at https://github.com/flutter/flutter/issues.
command
flutter doctor
exception
VersionCheckError: VersionCheckError: Command exited with code 128: git log -n 1 --pretty=format:%ad --date=iso
Standard error: error: packfile .git/objects/pack/pack-68b6600584298f0f9ed8673f8235c973f20b25ac.pack does not match index
error: packfile .git/objects/pack/pack-68b6600584298f0f9ed8673f8235c973f20b25ac.pack does not match index
error: packfile .git/objects/pack/pack-68b6600584298f0f9ed8673f8235c973f20b25ac.pack does not match index
error: packfile .git/objects/pack/pack-68b6600584298f0f9ed8673f8235c973f20b25ac.pack does not match index
fatal: bad object HEAD
#0      _runSync (package:flutter_tools/src/version.dart:522:5)
#1      FlutterVersion._latestGitCommitDate (package:flutter_tools/src/version.dart:142:12)
#2      FlutterVersion.frameworkCommitDate (package:flutter_tools/src/version.dart:133:37)
#3      FlutterVersion.checkFlutterVersionFreshness (package:flutter_tools/src/version.dart:289:62)
<asynchronous suspension>
#4      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:372:41)
<asynchronous suspension>
#5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#6      _rootRun (dart:async/zone.dart:1124:13)
#7      _CustomZone.run (dart:async/zone.dart:1021:19)
#8      _runZoned (dart:async/zone.dart:1516:10)
#9      runZoned (dart:async/zone.dart:1463:12)
#10     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:356:19)
<asynchronous suspension>
#12     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:112:25)
#13     new Future.sync (dart:async/future.dart:224:31)
#14     CommandRunner.run (package:args/command_runner.dart:112:14)
#15     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:242:18)
#16     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:22)
<asynchronous suspension>
#17     _rootRun (dart:async/zone.dart:1124:13)
#18     _CustomZone.run (dart:async/zone.dart:1021:19)
#19     _runZoned (dart:async/zone.dart:1516:10)
#20     runZoned (dart:async/zone.dart:1500:12)
#21     run.<anonymous closure> (package:flutter_tools/runner.dart:60:18)
<asynchronous suspension>
#22     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#23     _rootRun (dart:async/zone.dart:1124:13)
#24     _CustomZone.run (dart:async/zone.dart:1021:19)
#25     _runZoned (dart:async/zone.dart:1516:10)
#26     runZoned (dart:async/zone.dart:1463:12)
#27     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#28     runInContext (package:flutter_tools/src/context_runner.dart:56:24)
<asynchronous suspension>
#29     run (package:flutter_tools/runner.dart:51:10)
#30     main (package:flutter_tools/executable.dart:62:9)
<asynchronous suspension>
#31     main (file:///C:/b/s/w/ir/k/archive/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#32     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:299:32)
#33     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

flutter doctor
encountered exception: VersionCheckError: Command exited with code 128: git log -n 1 --pretty=format:%ad --date=iso
Standard error: error: packfile .git/objects/pack/pack-68b6600584298f0f9ed8673f8235c973f20b25ac.pack does not match index
error: packfile .git/objects/pack/pack-68b6600584298f0f9ed8673f8235c973f20b25ac.pack does not match index
error: packfile .git/objects/pack/pack-68b6600584298f0f9ed8673f8235c973f20b25ac.pack does not match index
error: packfile .git/objects/pack/pack-68b6600584298f0f9ed8673f8235c973f20b25ac.pack does not match index
fatal: bad object HEAD

#0      _runSync (package:flutter_tools/src/version.dart:522:5)
#1      FlutterVersion._latestGitCommitDate (package:flutter_tools/src/version.dart:142:12)
#2      FlutterVersion.frameworkCommitDate (package:flutter_tools/src/version.dart:133:37)
#3      FlutterVersion.frameworkDate (package:flutter_tools/src/version.dart:95:31)
#4      FlutterValidator.validate (package:flutter_tools/src/doctor.dart:501:127)
<asynchronous suspension>
#5      Doctor.startValidatorTasks (package:flutter_tools/src/doctor.dart:152:52)
#6      Doctor.diagnose (package:flutter_tools/src/doctor.dart:223:41)
<asynchronous suspension>
#7      _doctorText.<anonymous closure> (package:flutter_tools/runner.dart:193:26)
#8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#9      _rootRun (dart:async/zone.dart:1124:13)
#10     _CustomZone.run (dart:async/zone.dart:1021:19)
#11     _runZoned (dart:async/zone.dart:1516:10)
#12     runZoned (dart:async/zone.dart:1463:12)
#13     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#14     _doctorText (package:flutter_tools/runner.dart:192:19)
<asynchronous suspension>
#15     _createLocalCrashReport (package:flutter_tools/runner.dart:170:32)
<asynchronous suspension>
#16     _handleToolError (package:flutter_tools/runner.dart:125:33)
<asynchronous suspension>
#17     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:65:22)
<asynchronous suspension>
#18     _rootRun (dart:async/zone.dart:1124:13)
#19     _CustomZone.run (dart:async/zone.dart:1021:19)
#20     _runZoned (dart:async/zone.dart:1516:10)
#21     runZoned (dart:async/zone.dart:1500:12)
#22     run.<anonymous closure> (package:flutter_tools/runner.dart:60:18)
<asynchronous suspension>
#23     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#24     _rootRun (dart:async/zone.dart:1124:13)
#25     _CustomZone.run (dart:async/zone.dart:1021:19)
#26     _runZoned (dart:async/zone.dart:1516:10)
#27     runZoned (dart:async/zone.dart:1463:12)
#28     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#29     runInContext (package:flutter_tools/src/context_runner.dart:56:24)
<asynchronous suspension>
#30     run (package:flutter_tools/runner.dart:51:10)
#31     main (package:flutter_tools/executable.dart:62:9)
<asynchronous suspension>
#32     main (file:///C:/b/s/w/ir/k/archive/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#33     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:299:32)
#34     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

@yassineakermi
It seems resulted from a bad flutter build which is expected to be a valid git repo.
You can get a new copy of the flutter repo, I think the issue would be resolved.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of ' flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.

same
Sending crash report to Google.
Crash report sent (report ID: 171de65440438788)
Oops; flutter has exited unexpectedly.
Crash report written to C:\Users\david\flutter_03.log;
please let us know at https://github.com/flutter/flutter/issues.


Removing object mode fallback from @jit.

This removes the long deprecated "object mode fallback" behaviour found in the numba.jit decorator (and other similar decorators). The removal attempts to be "minimal" in case there are unknown issues with making this change with view of making it easy to revert.

Besides the CI failure on test_globals_jit, my only comment is below:

Hopefully fixed in 774dc75.

Note: the documentation/deprecation notices need updating to reflect this change.

The CI failure is showing more test failures. Many seems to be resolvable by adding forceobj=True. Some looplifting tests may no longer be valid since (esp the "reject" ones since they are testing fallback behavior).
In addition, we might need to remove Flags.enable_pyobject.

gpuci run tests


Git initialize action should not be repair

It will most likely confuse first time users; and on top of that, nothing is broken, it’s just not initialized.

The action is now called "Initialize"


stageConfig url ignored

build 2016.8.1 is ignoring the stage config file when calling swarm.withStageConfig(url)

Can one of the admins verify this patch?

The presence check is like that so that setting a system property for the staging file will overwrite any other means of setting it.
You may even find that without calling swarm.withStageConfig() it's picked up your stages file off the classpath anyway.
If we incorporate this change, then doing swarm.withStageConfig() wins every time, which is not what is intended.
Maybe you could raise an issue https://issues.jboss.org/browse/SWARM about your use case and we can discuss if the original loading logic needs to be altered

I removed the whole withStageConfig() call and the file is indeed picked up off the classpath, solving my issue.
Thanks!

No problem, glad its working


Upload image with Uint8List in FormData sent string instead of binary

New Issue Checklist

[x] I have searched for a similar issue in the project and found one related issue #371 but not worked.

Issue Info

Info
Value

Platform Name
flutter

Platform Version
Not specific

Dio Version
3.0.0

Android Studio / Xcode Version
Android Studio 3.5

Repro rate
all the time (100%)

Repro with our demo prj
demo does not including related content

Demo project link
can't provided

Issue Description and Steps
First congratulate with the brand new version of Dio released.
首先恭喜Dio的新版本发布~
In my case, Uint8List image data will be converted to str instead of binary according to PyCharm's log.
在我的业务中，根据PyCharm的日志，Uint8List形式的图片数据被转化成了字符串而不是二进制数据。
As I proceed with the same method, adding a transformer, etc. It just post a string, still.
在我使用了与相关方法后，添加了数据转换等，问题依旧。
Some of my code provided below:
下面提供部分上传实现代码：
static Future updateUserAvatar(Uint8List avatar) async {
    FormData formData = FormData.fromMap({
        "avatar": MultipartFile.fromBytes(avatar),
    });
    return NetUtils.post(
        API.saveUserInfo,
        data: formData,
    );
}

static Future post(String url, {data, headers}) async {
    Dio _dio = Dio();
    return await _dio.post(
        url,
        data: data,
        options: Options(
            headers: headers ?? buildAuthHeader(),
        )
    );
}

Please help me with this when you have spare time, thx a lot.
若您有时间，请帮助我解决这个问题，非常感谢！

FormData所有的内容最终都是以2进制上传的，你说“完整log中显示我传出的是string”，这个是根据什么判断的？如果是根据content-type，那么你可以指定一下MultipartFile的contentType

后端的PyCharm显示我传出的内容是str，正常接收应该为binary。稍后我附上截图。

不用重新定义Transformer,把你的transformer删了，很可能你的transformer就写
把你的requestEncoder也删了，干扰，formdata本身就是以二进制流上传的。
Formdata上传的示例example目录中有，请仔细查看。Formdata是经过严格测试的，上传二进制文件是没有问题的，
另外Formdata上传时content-type是multipart/form-data，#371 并不是说以Formdata方式上传，你这个QueryDict看起来貌似是query参数，你要确认一下后端是以哪种方式接受的。另外和后端调试建议使用抓包工具去排查问题。

恰逢国庆，只能节后再继续调试了，国庆快乐！

1、在formdata example中，并没有使用fromBytes构造FormData的示例，还麻烦进一步补充；
2、在使用fromBytes时，根据业务代码转换出来的Uint8List发送一直被接收为str (PyCharm)，为MultipartFile指定contentType为MediaType("image", "png")无效；
3、最终将数据存至File后构建上传成功。
仍认为其中存在部分问题。

同样的问题

根据群友做的大量测试，目前已定位问题，解决方法：

根据群友做的大量测试，目前已定位问题，fromBytes方法指定filename可解决。请考虑将文档及example完善。此原因由何导致？

我都是指定filename的，反正不行

Having same kind of issue in dio, As in our back-end they are accepting only binary data for file, I would like to have option to pass binary in body instead string,
I'm trying to pass byte[] in body but automatically converting into string and the content-type:application/octet-stream  which I'm not sure it's doing anything with that, please help or suggest any solution

@wendux Please take a look.

Still, it's an issue.

@wendux

Having same kind of issue in dio, As in our back-end they are accepting only binary data for file, I would like to have option to pass binary in body instead string,
I'm trying to pass byte[] in body but automatically converting into string and the content-type:application/octet-stream which I'm not sure it's doing anything with that, please help or suggest any solution.
Solution:
What I have done is converting bytes into stream and passing in the body
  List<int> imageBytes = File(path).readAsBytesSync();
  var file = MultipartFile.fromBytes(imageBytes).finalize();

  Dio().post('api/', data: file);

Thanks! It works :)

Having same kind of issue in dio, As in our back-end they are accepting only binary data for file, I would like to have option to pass binary in body instead string,
I'm trying to pass byte[] in body but automatically converting into string and the content-type:application/octet-stream which I'm not sure it's doing anything with that, please help or suggest any solution.
Solution:
What I have done is converting bytes into stream and passing in the body
  List<int> imageBytes = File(path).readAsBytesSync();
  var file = MultipartFile.fromBytes(imageBytes).finalize();

  Dio().post('api/', data: file);

Thanks! It works :)

这样怎么指定上传的文件的key呢？
dio在文件上传这里确实有问题，试了很多办法都不行

Again.

Eww, another library waiting for abandon...


apollo-server throws error on setting custom response

My application requires response with http status codes like 500, 401 besides the graphql error.
I'm using something like this in my resolvers:
try {
    const data = getStuffFromDB()
    if(data===null)
        throw new Error("null returned from db");

    return {
        data
    }
}
catch (err) {
    context.response.status(500).send('Internal Server Error, ' + err.toString())
    console.error(err)
}

Now express sends the response here from resolver function but it seems like apollo-server in graphql-yoga still tries to send response later throwing this error:
UnhandledPromiseRejectionWarning: Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at ServerResponse.setHeader (_http_outgoing.js:467:11)
    at /home/tsingha02/todo/node_modules/apollo-server-express/dist/expressApollo.js:19:17

What's the right way to send custom response codes without the server throwing unnecessary errors?

Can someone open this issue? Looking for a solution too on this same issue.

@Purus
My bad on this issue. I forgot to close it.
Actually graphql specifications say that the endpoint should always return 200. http://facebook.github.io/graphql/October2016/#sec-Errors
You can open a new issue but this one is a bad issue. You shouldn't manually return http status codes.


Add regression benchmark

@weixuanfu2016 is working on adding regression datasets to PMLB. Please report on your progress here, @weixuanfu2016.

Ok will do:-)

I tried to convert those regression data to tsv file in pmlb But I did not merge them into pmlb repo yet. I found a few dataset is very huge, like >200Mb in tsv format. You can check them in the LPC path I sent over in slack. Should we exclude them?
Another issue with pmlb. The target name of all current classification benchmarks in pmlb is class, I think it is not good for regression benchmark so I used pmlb_reg_target instead, is it OK?

How big are the files when gzipped?
Let's call the class equivalent as target.

Even gzip file is more than 110Mb
target sounds good

We might end up changing the PMLB standard such that all target columns are named target.

if you want i can add a collection of benchmark problems used in GP (mostly synthetic).

@lacava sounds good.

Sure @lacava, send over a PR and describe them for us. 👍

i was thinking it would also be nice to have a notebook for generating the synthetic datasets, for example for the korns / keijzer / pagie problems. where should that go?

Maybe that would be a separate project, unless we were explicitly creating datasets to upload to PMLB.

yea, they would correspond to datasets in the archive.

Cool, send a separate PR for it and we'll take a look. :-)

@weixuanfu, can you please re-send the PR with the regression benchmarks? Please take care when moving the existing classification datasets around.

OK, will do

Please check PR #15


Continuous integration

Set up continous integration using Github Actions in order to run tests, build a JAR file, create a Github release, etc. whenever a change is pushed.

When this is done, create a new issue for the Continous Integration report.

Now auto-generates testing report for the website.


Add syntax support for duplicating input file descriptors

This PR extends the parser to support the n<&m Bash syntax for duplicating input file descriptors, i.e.:
echo "hello" > file.txt  # create a file named "file.txt"
exec 3<file.txt          # assign file descriptor 3 to "file.txt"
wc -l <&3                # redirect stdin to fd 3, i.e. read it from "file.txt"

This syntax is posix, not just bash, isn't it?

This syntax is posix, not just bash, isn't it?

Ah, yes it is.


Fix json_test.py imports

https://github.com/NVIDIA/spark-rapids/pull/7494#discussion_r1069036133
Signed-off-by: Gera Shegalov<EMAIL_ADDRESS>

build

build


HIVE-23965: Improve plan regression tests using TPCDS30TB metastore dump and custom configs

What changes were proposed in this pull request and why?

Use Dockerized postgres metastore with TPC-DS 30TB dump
Use Hive config properties obtained and curated from real-life usages
Allow AbstractCliConfig to override metastore DB type
Rework CorePerfCliDriver to allow pre-initialized metastores

Extract TPCDS specific code to subclass and document appropriately
clarifying inaccuracies regarding the size of the tables in the javadoc.
Remove system property settings in the initialization of the driver and
leave in the configuration to set it up if needed. This is necessary to
be able to use the driver with a preinitialised metastore.
Remove redundant logs in System.err. Logging and throwing an exception
is an anti-pattern.
Replace assertions with exceptions and improve the messages.

Give more meaningful names to TPCDS related CLI configurations
Disable queries 30, 74, 84 with appropriate JIRA reference
Add TPC-DS query plans for the new driver (TestTezTPCDS30TBCliDriver)
Consider hive.current.database property when returning the session's
current db to avoid prefixing every query with the name of the database
Upgrade postgres JDBC driver to version 42.2.14 to be compatible
with the docker image used.

Does this PR introduce any user-facing change?
No
How was this patch tested?
mvn test -Dtest=TestTezTPCDS30TBPerfCliDriver  -Dtest.output.overwrite

Closed and reopened to trigger tests.

this patch also fully removes TestTezPerfConstraints driver - is that because from now on we will run with constraints all the time?

this patch also fully removes TestTezPerfConstraints driver - is that because from now on we will run with constraints all the time?

That's right. If we want to run with and without constraints then I guess we can truncate the respective table ("KEY_CONSTRAITS") didn't try it though.


allow scaling windows

BlizzMove does ctrl+mouse wheel. Could also do a "resizer" mover in bottom right corner?

+1 on this request. I was actually coming here to request this exact thing. I'm sticking with BlizzMove for the time being but only because of the scaling/zooming.

+1
BlizzMove doesnt need to exist as this addon does everything better
Only scale is not a feature


Add Support for Import Aliasing

While #94 provided support for typing.overload, and #98 to add similar functionality for single dispatch, it came with a caveat that import aliasing is not supported.
For example, with this snippet:
from typing import overload as ovrld

@ovrld
def foo(a: int) -> int:
    ...

def foo(a):
    ...

The linter will not recognize the closing foo statement as part of the overload series:
$ flake8 ./asdf.py
./asdf.py:8:9: ANN001 Missing type annotation for function argument 'a'
./asdf.py:8:12: ANN201 Missing return type annotation for public function

The classification is currently made by explicitly matching "overload", either as it's own decorator (@overload) or as an attribute (@typing.overload). While functional, this approach is pretty brittle.
Even though we're lacking the ease of checking this in a linting environment that exists at runtime, we can likely still do a better job at identifying decorators in a more generic manner by adding an import visitor to the AST parsing to keep track of aliasing within the file being linted. This won't be perfect, but it can help broaden the current caveat.

Thinking about this some more recently, I think I'd rather implement this via a configuration option rather than coming up with some new scope tracking AST import walker that, even at its most clever, still has a lot of ways to be wrong at runtime.
For some prior art, I'm thinking something along the lines of how pep8-naming handles @classmethod and staticmethod decorators. This turns the error emitting for decorated functions into a generic True/False check without needing complicated AST machinery behind it.