Lock to python 3.9

The current set of dependencies does not compile successfully when using the base image pythhon:3, this is most likely because today it resolves to 3.11 while when this project was setup the latest version was python 3.9
While the best solution would be to update the packages to run on Python 3.11, I am only proposing a quick'n'diurty solution that sets the base image to python 3.9.

Error with python 3.10+
#8 20.40       INFO: compile options: '-I/usr/local/lib/python3.10/site-packages/numpy/core/include -Ibuild/src.linux-x86_64-3.10/numpy/distutils/include -I/usr/local/include/python3.10 -c'
#8 20.40       extra options: '-funroll-all-loops -msse -msse2 -msse3'
#8 20.40       INFO: g++: numexpr/interpreter.cpp
#8 20.40       INFO: g++: numexpr/module.cpp
#8 20.40       INFO: g++: numexpr/numexpr_object.cpp
#8 20.40       numexpr/interpreter.cpp: In function ‘PyObject* NumExpr_run(NumExprObject*, PyObject*, PyObject*)’:
#8 20.40       numexpr/interpreter.cpp:1272:59: error: ‘NPY_ARRAY_UPDATEIFCOPY’ was not declared in this scope; did you mean ‘NPY_ITER_UPDATEIFCOPY’?
#8 20.40        1272 |                                         NPY_ARRAY_ALIGNED|NPY_ARRAY_UPDATEIFCOPY);
#8 20.40             |                                                           ^~~~~~~~~~~~~~~~~~~~~~
#8 20.40             |                                                           NPY_ITER_UPDATEIFCOPY
#8 20.40       error: Command "g++ -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/usr/local/lib/python3.10/site-packages/numpy/core/include -Ibuild/src.linux-x86_64-3.10/numpy/distutils/include -I/usr/local/include/python3.10 -c numexpr/interpreter.cpp -o build/temp.linux-x86_64-cpython-310/numexpr/interpreter.o -MMD -MF build/temp.linux-x86_64-cpython-310/numexpr/interpreter.o.d -funroll-all-loops -msse -msse2 -msse3" failed with exit status 1
#8 20.40       INFO:
#8 20.40       ########### EXT COMPILER OPTIMIZATION ###########
#8 20.40       INFO: Platform      :
#8 20.40         Architecture: x64
#8 20.40         Compiler    : gcc
#8 20.40
#8 20.40       CPU baseline  :
#8 20.40         Requested   : 'min'
#8 20.40         Enabled     : SSE SSE2 SSE3
#8 20.40         Flags       : -msse -msse2 -msse3
#8 20.40         Extra checks: none
#8 20.40
#8 20.40       CPU dispatch  :
#8 20.40         Requested   : 'max -xop -fma4'
#8 20.40         Enabled     : SSSE3 SSE41 POPCNT SSE42 AVX F16C FMA3 AVX2 AVX512F AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL
#8 20.40         Generated   : none
#8 20.40       INFO: CCompilerOpt.cache_flush[857] : write cache to path -> /tmp/pip-install-rrxpx96g/numexpr_80e25a429e6948c8a0e830443ee7ef8d/build/temp.linux-x86_64-cpython-310/ccompiler_opt_cache_ext.py
#8 20.40       [end of output]
#8 20.40
#8 20.40   note: This error originates from a subprocess, and is likely not a problem with pip.
#8 20.41 error: legacy-install-failure
#8 20.41
#8 20.41 × Encountered error while trying to install package.
#8 20.41 ╰─> numexpr
#8 20.41

Hi @esolitos , thank you for the PR. I have now merged the eye-tracking branch (where this issue has been resolved) into main. Could you please pull the latest changes? I will now close this PR.


Feat cpdId new

Connection point id. Fill in both id and cpdId. Same value is OK.

[X] Update OpenApi to version 3.4
[X] Fix OSM driver
[ ] Fix ONAP driver

Merging OSM fix. Waiting for ONAP fix.


Linux HidDevices.open() error

Hello, could you please help me with error

flutter: HID Exception: Failed to open hid device. Error: Closure: () => String from Function '_getLastErrorMessage@344186600':.()

example of code

void _connectToDevice() async {
List<HidDevice> devices =
    await Hid.getDevices(vendorId: 0x1234, productId: 0x1234);

devices = devices.where((device) {
  return device.vendorId == 0x1234&& device.productId == 0x1234;
}).toList();
try {
  if (devices.isNotEmpty) {
    openDevice = devices.first;
    await openDevice.open();
    _timer = Timer.periodic(const Duration(milliseconds: 100), (timer) {
      _readFromDevice();
    });
  } else {
    await Future.delayed(const Duration(seconds: 1));
    _connectToDevice();
  }
} catch (e) {
  if (e is HidException) {
    print('HID Exception: ${e.message}');
    await Future.delayed(const Duration(seconds: 1));
    _connectToDevice();
  } else {
    print('Unexpected Exception: $e');
    await Future.delayed(const Duration(seconds: 1));
    _connectToDevice();
  }
}
}

OS: Ubuntu 20.04
Same code on Windows 11 works fine.

Can you please update to 0.1.3? The error message will now give us more information about this issue.
Error: Closure: () => String from Function '_getLastErrorMessage@344186600':.() is not supposed to be printed, I fixed this in #13, it will now show you the real error message that caused you issue.
Also now you don't need to do
devices = devices.where((device) {
  return device.vendorId == 0x1234&& device.productId == 0x1234;
}).toList();

since I've fixed the Hid.getDevices(...) method in #12

@vinsfortunato, sure!

[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Unsupported operation: Operation 'toDartString' not allowed on a 'nullptr'.
#0      CharPointerToString._ensureNotNullptr (package:hid4flutter/src/desktop/extensions.dart:40)
#1      WCharPointerToString.toDartString (package:hid4flutter/src/desktop/extensions.dart:48)
#2      HidDeviceDesktop._getLastErrorMessage (package:hid4flutter/src/desktop/hid_device_desktop.dart:276)
#3      HidDeviceDesktop.open. (package:hid4flutter/src/desktop/hid_device_desktop.dart:94)
#4      using (package:ffi/src/arena.dart:124)
#5      HidDeviceDesktop.open (package:hid4flutter/src/desktop/hid_device_desktop.dart:89)
#6      _MainAppState._connectToDevice (package:testing/main.dart:48)


Running bacground

How do plugin running on background???

Closing this issue. You may ask your questions at the Phonegap forum


Add attributes to PageVersion

was_published: whether this PageVersion was published once
backup_id: using the batch-add to create a 'backup'. If you want to roll back: select all PageVersions by backup (introduce a new backup-model?)
version_owner: the creator of the PageVersion (for the rights management)

version_owner is already an attribute of the PageVersion. The rest seems to be neglectable...


Fail when importing dataset if there are no solved captchas

This means that we cannot validate users on the frontend.

Done, plus all captchas are now solved by default.


fix(ci): :adhesive_bandage: remove duplicate definition of releasenot…

…es-generator
Thie duplicated definition of the release-notes-generator lead to duplicated changelog entries

:tada: This PR is included in version 1.9.0-rc.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.9.1-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.9.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Upgrade to Kubernetes 1.22+

[x] https://github.com/relaycorp/relaynet-pong/issues/762
[ ] Create GCP resources (KMS, Datastore, etc).
[ ] Upgrade cluster.

Superseded by #13


Add #274 Process webhooks in goroutine

@albinpa Since we no longer require the webhook dispatcher we can remove it in main.go  ?


[Network] az network application-gateway rewrite-rule: Add params--request-header-configurations and --response-header-configurations

Related command

colsed: https://github.com/Azure/azure-cli/issues/28684
Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Network


Resetting the Solace Admin Password is causing the passive pods to fail

Description:-
Background:-
we have to rotate our solace admin password  in our production environment regularly so we need a better strategy to reset our
password regularly with no downtime in solace.
we try to reset the password via both CLI and solace web console but ended up with the same result.
Issue Detail:-
we have solace cluster running on 3 pods with redundancy on. We try to reset the password by logging into the solace web
console.
once we hit the apply button with the new password it forcefully logout us and then the page is not accessible.
The pods are failing to be in a ready state due to the liveness and readiness probes failing.
<returnInfo><errorInfo>management host is not responding</errorInfo></returnInfo>   INFO: startup-broker.sh-Waited 170 seconds, Management API not yet accessible
looking for a fix for this.

Hi @vivekcs0114 , the reason for this is that the broker is still using internally the outdated originally configured password to access the Management API. The secret belonging to the deployment is the one storing the outdated password. You'll need to update the secret to the new password immediately before making the password update admin change. A subsequent pod restart will mount the modified secret with the new password. Please ensure to try this in a test environment first.

I just came across this and found that there is no need for pod restarts. The changed secret is mounted automatically for all pods. However two CLI pw change steps are necessary: change admin pw on active broker, this will update the standby. Additionally it is still required to update the admin password on the monitor via direct CLI there.

Isn't this is race condition? as after modifying the password in helm/secret which is updated in pod is outdated and can't be used till updated via cli/console so any restart in between will lead to outage ?

Can we create a less privileged user to be used in scripts and let admin user to be initialised only once ?
Is  ldap an option ?

User management considerations section has now been added to the documentation.
The solution of a less privileged user to be used in scripts is being considered for the Operator-based deployment.
Ldap is an option for user management, however it needs to be configured after the broker deployment so it is out of scope for this quickstart.

Closing this issue.


Use definitionsFullyResolved when lookup up consumes/produces propert…

Use definitionsFullyResolved when lookup up consumes/produces properties - fixes issue when using split definition files - ref Issue 92

It looks harmless but do you mind creating a test?  If not, no biggie.  If you have the time, it would be cool.

Will try to get a test written next week

Any updates on this?

If @CWThomson doesn't post a test by EOD, I will merge the PR and add the test(s) myself.  Sorry for the delay in responding, I was on vacation last week.

No worries, no apology necessary! Thanks for helping unblocking the issue

Any updates on this?

@whitlockjc Can I help with this? I can look into adding tests if it helps with getting this merged 🙂

That would help.  I'm maintaining this project on my own time right now and due to work, I just don't have a lot of time.

A quick question about the Travis CI setup here, is it only running gulp test-node? Because with this change, there is a test failure in gulp test-browser which I also fixed in #117

It should be running gulp test.


Map storytelling with routes

Hi,
Do you know a way to add routes to the storytelling ?
I could be awesome to achieve something like this with your plugin

If pidgeon-maps supports it, it should be possible.
You can also copy the maps-wave component and modify it to use another map provider

It seems like pidgeon-maps does not support it. Mapbox storytelling neither.
I can't find a way to achieve it using a map library.
Do you have ideas?

google maps maybe? sorry I don't know too much about map libraries.

Ok thank


expose the unified diff for PR through the github plugin

          1 Error

:no_entry_sign:
Please provide a summary in the Pull Request description

          1 Message

:book:
@champo is not a contributor yet, would you like to join the Danger org?

  Generated by :no_entry_sign: danger

Yep - perfect, looks 👍


windows runner

support windows

I have tried your pull request locally it is failing with below error:
 Re-running tests , attempt :  1
 Re-running the following test files : C:\Users\tester\workspace\crew-consist-ui-automated-scripts\specs\find_crew_consist_spec.js

The system cannot find the path specified.
[11:00:15] E/launcher - spawn Files\nodejs-12.3.1\node.EXE ENOENT
[11:00:15] E/launcher - Error: spawn Files\nodejs-12.3.1\node.EXE ENOENT
    at notFoundError (C:\Users\tester\workspace\crew-consist-ui-automated-scripts\node_modules\protractor-retry\node_modules\cross-spawn\lib\enoent.js:6:26)
    at verifyENOENT (C:\Users\tester\workspace\crew-consist-ui-automated-scripts\node_modules\protractor-retry\node_modules\cross-spawn\lib\enoent.js:40:16)
    at ChildProcess.cp.emit (C:\Users\tester\workspace\crew-consist-ui-automated-scripts\node_modules\protractor-retry\node_modules\cross-spawn\lib\enoent.js:27:25)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
[11:00:15] E/launcher - Process exited with error code 199
>> The system cannot find the path specified.
Warning: Tests failed, protractor exited with code: 199 Use --force to continue.

Aborted due to warnings.

closed in favor on #84


AutoCryptoMine starts my mining app while I'm coding

At the moment AutoCryptoMine starts when I'm not using my mouse for xx period. This is problematic when writing a long issue to github or coding or writing an email.
So it should probably listen for keypresses too.
I recommend adding complete function for checking if keys have been pressed for xx period.

Thanks for the suggestion! I will add it for the next release

Added keyboardhook


[Segment Anything][WebNN GPU] Failed to execute 'compute' on 'MLContext': Invalid outputs: The type (BigInt64) of the array buffer view

Repro Steps:

Launch latest Chrome Canary on Windows 11
C:\Users\AppData\Local\Google\Chrome SxS\Application\chrome.exe" --enable-features=WebMachineLearningNeuralNetwork

Visit https://microsoft.github.io/webnn-developer-preview/demos/segment-anything/

Move mouse to image when the modesl loading finshed.

Actual Result:
TypeError: Failed to execute 'compute' on 'MLContext': Invalid outputs: The type (BigInt64) of the array buffer view with name "/ArgMax_output_0" doesn't match the expected operand data type (int32).
Environment:
Chrome Canary: 128.0.6600.0 (Official Build)
GPU Driver Version: <IP_ADDRESS>62

Device
OS
CPU
GPU

Laptop
Windows 11 23H2
Ultra 7 155H
Intel Arc Graphics

Caused by argMax change: chromium-review.googlesource.com/c/chromium/src/+/5692538

Breaking change should be addressed once this goes: https://github.com/microsoft/onnxruntime/pull/21385

This issue has been fixed in demo code https://github.com/microsoft/webnn-developer-preview/pull/19 , please close this issue. Thanks!


Merge DevOps into Dev - [closed]

In GitLab by @luotian-github on Apr 2, 2018, 09:13
Merges dev-devops -> dev

In GitLab by @wknet123 on Nov 13, 2019, 10:47
The test coverage for backend is  %   and for frontend is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:47
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:47
closed


Add response trailer feature

Opening this up for discussion, starting out with response trailers. We can attack request trailers later. This addresses the HttpAbstractions part of https://github.com/aspnet/KestrelHttpServer/issues/622...
My current thinking is that you add the trailing header names using the regular Headers dictionary:
response.Headers.Append("Trailer", "Server-Timing");

This would automatically chunk the response, if possible and allowed. You can, of course, also add headers with the same name:
response.Headers.Append("Server-Timing", "db;dur=53");
response.Headers.Append("Server-Timing", "app;dur=47.2");

These are, as expected, flushed together with the rest of the headers. You can then explicitly add trailers:
trailersFeature.OnStarting(() =>
{
    // This would be the very last thing to happen before it's flushe to the client.
    trailersFeature.Trailers.Append("Server-Timing", "total;dur=123.4");
});

The entire response would look something like this:
HTTP/1.1 200 OK
Server-Timing: db;dur=53, app;dur=47.2
Trailer: Server-Timing
(... snip response body ...)
Server-Timing: total;dur=123.4

I'm thinking it's best to keep the feature by itself, as it doesn't make sense to expose such a niche feature on the HttpResponse itself.
There are a couple of open questions, mostly related to implementation behavior:

What happens if expected trailers are missing from the Trailers dictionary (after OnStarting has been called)?
What happens if other (unexpected) trailers are added to the Trailers dictionary?
What kind of validation needs to be in place for Trailer entries? The RFC is pretty strict on which headers are allowed as trailers:

A sender MUST NOT generate a trailer that contains a field necessary
for message framing (e.g., Transfer-Encoding and Content-Length),
routing (e.g., Host), request modifiers (e.g., controls and
conditionals in Section 5 of [RFC7231]), authentication (e.g., see
[RFC7235] and [RFC6265]), response control data (e.g., see Section
7.1 of [RFC7231]), or determining how to process the payload (e.g.,
Content-Encoding, Content-Type, Content-Range, and Trailer).

// @Tratcher @benaadams @Drawaes @NickCraver @serialseb @halter73

I'm not too familiar with the Trailer spec, so I don't know what should be done as far as validation goes. I do like have some sort of callback that get's invoked before writing trailers though.

What happens if expected trailers are missing from the Trailers dictionary (after OnStarting has been called)?

Of interest is the current conversations in http bis and fetch. For example https://github.com/httpwg/http11bis/issues/16
From this, I'd think that if you say "i'll send trailers", the fact that you do in the end or not is not problematic for the client, so I'd assume it's ok to not send them. Plus, if it wasn't, you're way way way down in the response sending, so there's little you can do about it.

What happens if other (unexpected) trailers are added to the Trailers dictionary?

From a dev perspective, magic = bad, so i'd throw immediately if you try and write a trailer you didn't say you would write before the non-trailered headers are sent. Silently erroring out doesn't help anyone in this context.

What kind of validation needs to be in place for Trailer entries? The RFC is pretty strict on which headers are allowed as trailers:

Headers that are forbidden to be sent in trailers from the 1.1 spec could throw, as there is no way anyone could find any use whatsoever for breaking the spec. Knowning that, it means that you'll ever only be able to validate those headers you decided on at that point, as adding more forbidden headers in the future would break compat.
So i'd thnk throw on 1.1 forbidden headers, and if that list gets extended in the future, then add an opt out for people upgrading. It's easier to stop an exclusion than to start an exclusion

Of interest, in go:
https://go-review.googlesource.com/c/go/+/2157
And how they validate in h11 vs h2 https://github.com/golang/go/issues/23908
in nodejs: https://nodejs.org/api/http.html#http_response_addtrailers_headers
May be interesting to have a look at other platforms

Yeah, looks like this is a good list;
https://github.com/golang/go/blob/7662e6588c9433f1219e0a0c46bc563ba3f93f98/src/net/http/h2_bundle.go#L6536-L6569

Hmm. What do you think about just a single method like
void DeclareTrailer(string key, Func<object, Task<StringValues>> callback, object state)

You'd have to call the method to declare all trailer headers before IHttpResponseFeature.OnStarting (when the headers are flushed) is called.
The method would automatically give you the trailers to include in the Trailer header, plus a callback for each trailer to produce a value.
It would also solve the other questions, as there would be no way to add more (or less) trailers than those declared in the header, plus you can validate them all up-front, before the response has started.

That looks good. I'm gonna have a think and see if there are scenarios this wouldn't allow for.

that looks like a higher layer wrapper over the current minimal mechanics.

Maybe. The problem is just that I think these mechanics are too minimal. Hence the questions in the initial post. The DeclareTrailer method answers them all (I think).

Consider if you have one component declaring the trailers and another providing them.

Yeah, that's problematic for many reasons. How do you coordinate between those components? Do you have an example in mind?

The feature interfaces are supposed to be as low level and as flexible as possible. It's only at the HttpContext layer that we try to provide more explicit usage patterns.
A basic example would be that I know all responses will included some set of trailers. It's quite easy and most efficient to declare a flat list up front. However, the code responsible for generating each those values is distributed throughout the response processing. Consider one that gives you database time, one for serialization time, etc.. With DeclareTrailer you'd have to stash that information as it's generated and then retrieve it later when the callback is invoked. I'd much rather be able to add it to the response when it's generated.

Separate question: symmetry important? Are there scenarios we're interested in that require both request and response trailers? Or are response trailers the majority case?
I ask because Http.Sys can't support request trailers, but it can support response trailers. Not sure if you can do response trailers on IIS. Kestrel can do both.

With DeclareTrailer you'd have to stash that information as it's generated and then retrieve it later when the callback is invoked. I'd much rather be able to add it to the response when it's generated.
Ok, I delved a bit more into this. For example, in OpenRasta we have a single tap pipeline that gets auto wired-up at various stages in http processing, one being response coding, which a component can declare to want to execute before of. We don't currently have a separate part of the pipeline for ResponseSending, they're assumed to be one and the same. Trailers would allow me to add an extra KnownStages.IResponseTrailerSending and let the system wire up components at the right time. Without the notification, i have nothing to hang the pipeline off of. So the DeclareTrailer would make it slightly more complicated.
I attach some code that would be what I expect to write:
public class ResponseWriteTimings : IPipelienContributor
{
  StopWatch timer;
  public void Initialize(IPipeline builder) {
    builder.Notify(RegisterTrailer).Before<KnownStage.IResponseCoding();
    builder.NotifyAsync(WriteTrailer).Before<KnownStages.IResponseTrailerSending();
  }
  void RegisterTrailer(ICommunicationContext context) {
    context.Response.Trailer += "Server-Timing";
   // initialise StopWatch
  }
  void WriteTrailer(ICommunicationContext context) {
    context.Response.Headers.ServerTiming += new Timing(stopWatch.ElapsedMilliseconds);
 }
}

Any model that wouldn't break something along those lines would allow us to implement that feature, when the server supports it.
Request trailers would work the same way, so I would need a rather symetric appraoch for the request pipeline.
On a side note, as we don't use the asp.net object model for http headers, i'd rather we had as low level as possible access to headers, so any object model deviating from that would make me less happy.

@serialseb I'm curious how you're planning to tackle the questions mentioned in the top post.
Looking at the example you posted, there's still some unanswered questions:

What happens if you declare a trailer, but forget to actually append it in the WriteTrailer callback?
What happens if you've forgotten to declare a trailer, but still try to append it in WriteTrailer? At that point, it's already too late to change headers, as they've already been flushed to the client.
I see you're using context.Response.Headers to append trailers. How are you planning on validating legal trailers. The RFC is pretty strict on which headers can be sent as trailers.

Are you implementing OpenRasta on top of the ASP.NET Core abstractions?

not a fan of DeclareTrailer, that looks like a higher layer wrapper over the current minimal mechanics. Consider if you have one component declaring the trailers and another providing them.

@Tratcher How do you propose we answer the questions above when you can have some components that declare and some components that provide trailers? How do we make sure they're consistent? Do we need to?

The server's job is to make sure the client gets an intelligible response. Most of these mistakes wouldn't corrupt the response, the client would still be able to read it but it may end up with more or less information than it was expecting. Do we have any clients that actually surface trailers to do some interop testing with?

Chrome 65 supports Server-Timing. I'll see if I can test some of the scenarios.

What happens if you declare a trailer, but forget to actually append it in the WriteTrailer callback?

That shouldn't be a problem, a trailer is just a lose promise, from what i understand of the spec. I may send a Server-Timing but I may not

What happens if you've forgotten to declare a trailer, but still try to append it in WriteTrailer? At that point, it's already too late to change headers, as they've already been flushed to the client.

Well that's a server error but the response, I'd flag / warn about it but I can't really do much about it.

I see you're using context.Response.Headers to append trailers. How are you planning on validating legal trailers. The RFC is pretty strict on which headers can be sent as trailers.

Well, it's pretty strict as to which headers cannot be sent :) So i'd probably make sure i implement the spec as correctly as possible.
That said it's entirely possible that i'd build an api on top of the low level pipeline one above, but at that point I can implement the delegate on top of it, the other way around is not possible.

This was superseded by #1043


Added more homepage sections

What's done

[x] Added news section
[x] Added topics section
[x] Added testimonies section
[x] Added a vertical line between news cards

@billyjason , this was still a draft.


Jc/merge/release 2.0.0/develop

Description
Merge from release/2.0.0 to develop.
I already solved the conflicts in wallet code. Please @KtorZ , double check it.
@iohk-devops : please solve the remaining conflicts:
Here is the list of the remaining conflicts:
both modified:   appveyor.yml
both added:      bors.toml
both modified:   default.nix
both modified:   docs/how-to/build-cardano-sl-and-daedalus-from-source-code.md
both modified:   nix/stack2nix.nix
both modified:   pkgs/default.nix
both modified:   release.nix
both modified:   stack.yaml

Linked issue
N/A
Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

How to merge
Send the message bors r+ to merge this PR. For more information, see
docs/how-to/bors.md.

Here below, the complete list of PR made against release/2.0.0 since the cut-off and, if any and applicable, their equivalent on develop.

YT Ticket
develop
release/2.0.0

??
#3972
#3846

??

#3888

??
#3902
#3892

??
#3722
#3909

??
N/A (newer version on develop)
#3924

CBR-466
#3804
#3742

CBR-470
#3805
#3773

CBR-475
#3873
#3870

CBR-477
#3807
#3810

CBR-495
#146
#3943

CBR-496
#138
#3947

CSL-2526
#3815
#3833

DDW-480
#3834
#3838, #3835

DEVOPS-1094
#3972
#3817

DEVOPS-1099
#3825
#3771

DEVOPS-1112
#3972
#3962, #3936, #3946, #3919, #3879

DEVOPS-1113
PENDING #3982
#3880, #3912, #3913, #3927

DEVOPS-1121
#3972
#3831

DEVOPS-1126

#3852

DEVOPS-1130
#3849
#3848

DEVOPS-1134
#3979
#3856

DEVOPS-1141
#3972
#3867

DEVOPS-1143
N/A (newer version on develop)
#3889, #3907

DEVOPS-1153
N/A (legacy data-layer)
#3911

DEVOPS-1172
#3972
#3934

RCD-37
#3972
#3811

RCD-38
#3813
#3812

RCD-40
#3823
#3819

RCD-42
#3972
#3816

RCD-43
#3973
#3931, #3920

RCD-45, RCD-44
#3875
#3861

RCD-46
#3875
#3855

RCD-47
N/A (feature no-longer exists)
#3876

RCD-48
#3972
#3883

RCD-49
#77
#3886

RCD-52
PENDING #3982
#3926


Rotation issue

I have just opened menu in portrait mode Than I rotated device to landscape and menu get hidden.
and vice versa.
What is the issue @dekatotoro ?

Hi, I am also facing same issue, did u find any solution ?


Unable to end script file with function that only has pass.

Unable to have a placeholder function that just has pass in it as the last line of a script file. Adding an enter to the end of the file makes the invalid error message go away.

It seems to work fine in the current master branch. I made sure to have no newline at the end of the a file in my project, and had no issue:
@@ -92,3 +92,8 @@ func _ready():

        get_node("Settings/NbLives/Slider").set_value(global.nb_lives)
        get_node("Settings/NbLives/Label").set_text("Lives: " + str(global.nb_lives))
+
+       empty()
+
+func empty():
+       pass
\ No newline at end of file


Evaluate UX of Vault Concourse resource

Description/Context
We need to evaluate the usability of the Vault Concourse resource we had built under contract. In particular we need to validate whether or not it can replicate what we're doing with SaltStack configuring complex Heroku applications.
Plan/Design

[x] Identify Heroku application in salt-ops repo with the most complicated configuration
[ ] Create a test pipeline that utilizes the Concourse Vault resource to mimic the Vault secret retrieval side of that configuration
[ ] Validate results

discussions.sls is the largest with 150 lines of heroku config vars/

Concourse Vault Repo / Doc

I'm closing this for now. There may be more testing to come if we end up implementing the dynamic secrets aspect of the Vault concourse resource, but I'll re-open if/when that happens.


reuse AnalysisHost in batch analysis

We do some custom setup in AnalysisHost, like setting up LRU size. I figure it's a good idea to not duplicate this work in batch analysis, if we want to keep batch and non-batch close.
Long-term, I see a value in keeping batch a separate, lighter weight thing. However, because now we use batch to measure performance, keeping them closer makes more sense.
I'd also like to add ability to get completions by using batch analysis, and that will require ra_ide_api as well.
@flodiebold were there some reason why we haven't started with this approach from the start?

I think basically I imagined ra_batch and ra_ide_api as two separate use cases: ra_ide_api is for persistent processes that need to deal with changes, and has an IDE-focused API that mainly deals with files/strings, whereas ra_batch is for tools that just read the project once and perform some analysis, but want the full code model APIs. Maybe the separation isn't necessary, though.

Yeah, I think it's fine to basically expose database from Analysis. And I think you might want some idea things (for example, syntax highglighting) for some batch-processing tasks.
bors r+


kube prometheus stack upgrade to 48.2.0

Upgrade kube prometheus stack to v48.2.0 on all clusters.

Deployed to all envs.


Use the "lang" attribute to identify the language of the page.

Describe the bug
The HTML "lang" attribute is used to identify the language of text content on the web. This information helps search engines return language specific results, and it is also used by screen readers that switch language profiles to provide the correct accent and pronunciation.
To Reproduce
https://circuitverse.org/simulator
Visit CV Simulator Codebase Line No. 2
Are you working on this issue? (Yes/No)
Yes

@CircuitVerse/circuitverse-core-team

Hey @techMonowar, I'm new to the CircuitVerse community. Can I start working on this bug?

How does this fit with our i18n? // @vedant-jain03

Hi @vedant-jain03 and @gr455 hope I am not disturbing you, I think the website i189 is not properly configured and used. Should I open an issue about this and work on it?


Compilation broken on Windows with utp_shutdown changes

utp_internal.cpp: In function 'void utp_shutdown(UTPSocket*, int)':
utp_internal.cpp:3410:13: error: 'SHUT_WR' was not declared in this scope
  if (how != SHUT_WR) {
             ^~~~~~~
utp_internal.cpp:3413:13: error: 'SHUT_RD' was not declared in this scope
  if (how != SHUT_RD) {
             ^~~~~~~

Looks like Windows uses SD_RECEIVE and SD_SEND.


fix: duplicate LanguageCodes from core

As discussed in the group chat

👍👌🫶🎩

deno task backport still failing due to:
src/deps.node.ts:22:5 - error TS2305: Module '"grammy/types"' has no exported member 'LanguageCode'.

22     LanguageCode,
       ~~~~~~~~~~~~

TypeScript 5.1.3
Found 1 errors.


Gestures problem

Hello, do you have only two gestures for this DEMO?

That is correct.
The purpose of this demo is so it can be used as an example to train your own examples by following this tutorial. For example, you could train your own classifier with multiple gestures.


Pull in latest changes

draft PR to pull in latest changes to be able to do local testing for updating sidekiq

closing, was meant to be a pr against a forked version


Explore OpenLLM

Feature request
How can we take advantage of https://github.com/bentoml/OpenLLM ?
Motivation
No response

So from what I've seen, OpenLLM is a library that makes it easier for you to host web apps and whatnot with language models, i.e querying and displaying on a web server and deploying apps that boast this and other generative tasks as a feature. I spoke to the author about the whole CPU and GPU loading conundrum and it seems like they don't do anything especially useful to make huge models load on CPU's like we want with MPT-7B.
What we DO want is quantized versions of these huge models to run on CPU, and to that end I found GGML to be the solution here, more in the direction of LLAMA.cpp.

UPDATE: So I tested MPT-7B 4-bit quantized (https://huggingface.co/TheBloke/MPT-7B-GGML) on my Mac (M2 chip, 8GB CPU RAM) and it generated perfectly. I just used the ctransformer library, and I think we can generate completions for the MPTReplayStrat class in #226 and close it using something like this.. Try it out if you have RAM to spare! (I think you'd need 6+ gigs Free to generate a completion though)
from ctransformers import AutoModelForCausalLM

llm = AutoModelForCausalLM.from_pretrained('TheBloke/MPT-7B-GGML', model_type='mpt', model_file='mpt-7b.ggmlv3.q4_0.bin')

completion = "This is "
print(llm(completion))

Conclusion: implement https://github.com/OpenAdaptAI/OpenAdapt/pull/303


More features!

Hi, I found this useful but saw some things that could be added. By default it works nearly the same as the original, and all options can be turned on or off in the settings.
Search on partial words: sometimes it is useful to search for just part of a word.
Search any character: for instance, allows searching for "[i]"
Highlight in other panes: as it says. I am quite pleased with this one.
Highlight stop: stops highlighting after a given amount have been found. If it goes over the limit the status bar will say "found limit / @count" instead of "found @count" Mostly for when Search any character is on and you selected a single space in a very large file, it can lag a bit.
First time using coffee script so it was neat modifying this. Let me know if there is anything I should do.

Hi! Nice! I'm not using atom any more, I've been a vim user for a few years now, but I'll have a look in a few days or so 😄


Change direction of gravity

Describe the solution you'd like
Is it possible to change the direction of gravity? I would like to have it upside down / rotated by 180 degrees.
Describe alternatives you've considered
I rotated the source element with transform: rotate(180); but it had no effect.

Hi there, sorry for the late response;
you can change the gravity using party.settings.gravity, just set it to an appropriate (negative!) value, see https://party.js.org/docs/ref/configuration.


Number of projects

"Model interpretability/explainability", "Hyperparameter optimization" and "Developer Experience" under transmogrifAI are 3 different projects or just one ?

My best guess is that TransmogrifAI is the project you will be working on and the ones you mentioned are 3 different proposals for TransmogrifAI.
Each proposal targets different things to work for TransmogrifAI 😄

Those are project ideas within one project. A final proposal could be one idea, multiple ideas, etc.


Add runnerConfig option to configure runners

Do you want to request a feature or report a bug?
Enhancement
What is the current behavior?
There is no way of configuring a test runner
What is the expected behavior?
It would be nice to have a way to configure runners. For example: runnerConfig which could be any arbitrary object that is relevant for the runner configuration.
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

@cpojer @aaronabramov If we do decide to move forward with this, what do you think should be the interface here? runnerConfig: Object?

maybe something like what we do with reporters?
runner: 'some_runner.js'

// or

runner: ['some_runner.js', {hey: 'yo'}]

which translates to
// globalConfig.runner
{
  path: 'some_runner.js',
  options: {hey: 'yo'}
}

I actually had something quite different in mind because ProjectConfig is mostly local to the runner. The ideal system would be to have a base ProjectConfig (with a runner option) that can include both the runner configuration as well as any custom configuration for that runner. ProjectConfig is then both the config for the project and the configuration for the runner.
The challenge here is how to make this type safe and how to make the configuration system ultimately configurable.
Most things in Jest would be typed with BaseProjectConfig with the minimal set of options that any runner (even for non-test use cases) would share, which is threaded to most places in Jest. Then there would be a type JestProjectConfig which is threaded to everything from jest-runner onwards to jest-jasmine etc. I think this change is quite involved, but the end-state sounds enticing to me. What do you think?

i'm a little worried about mixing Jest projectConfig with other custom configuration. I really don't like how it worked with global+project configs sharing the same JSON object, most of the bugs we discovered with MPR were super hard to debug and were caused by some values being in the wrong config. But i think if we have a separate typed projectConfig with a custom/possibly untyped projectConfig.runnerConfig it might work well

The GlobalConfig + ProjectConfig issues were a one time cost that the split brought with it, and I think now (as of Jest 21), the system is working quite smoothly. The thing that worries me the most is adding an uncontrollable amount of config and cli options (it's already a bit of a mess) and making ProjectConfig something that is theoretically pluggable would counter that, as people could build their own runners that cut down on the number of configuration options. Also, to build runners for things like prettier/eslint etc., all the test related configuration options don't really make any sense.

I installed the dependencies and ran the tests, many of them break on windows, that needs to be solved first.

We have appveyor running as CI, so developing on windows should be fine... You'll neee mercurial installed for a few tests, but besides that you should be good

It seams most tests are failing because somehow paths are being prepended with ../../../../../Alexandre/AppData/Local/Temp/.
 FAIL  packages/jest-resolve/src/__tests__/resolve.test.js
  ● resolveModule › is possible to resolve node modules by resolving their realpath

    Cannot find module '../../src/__mocks__/bar/node_modules/foo/index.js' from 'resolve.test.js'

      at Resolver.resolveModule (packages/jest-resolve/build/index.js:221:17)

 FAIL  e2e/__tests__/only_changed.test.js (45.124s)
  ● run only changed files

    expect(received).toMatch(expected)

    Expected value to match:
      /PASS __tests__(\/|\\)file1.test.js/
    Received:
      "PASS ../../../../../Alexandre/AppData/Local/Temp/jest_only_changed/__tests__/file1.test.js
      ✓ file1 (3ms)

    Test Suites: 1 passed, 1 total
    Tests:       1 passed, 1 total
    Snapshots:   0 total
    Time:        4.154s
    Ran all test suites related to changed files."

      43 |
      44 |   ({stderr} = runJest(DIR, ['-o', '--lastCommit']));
    > 45 |   expect(stderr).toMatch(/PASS __tests__(\/|\\)file1.test.js/);
         |                  ^
      46 |
      47 |   writeFiles(DIR, {
      48 |     '__tests__/file2.test.js': `require('../file2'); test('file2', () => {});`,

      at Object.<anonymous>.test (e2e/__tests__/only_changed.test.js:45:18)

  ● onlyChanged in config is overwritten by --all or testPathPattern

    expect(received).toMatch(expected)

    Expected value to match:
      /PASS __tests__(\/|\\)file1.test.js/
    Received:
      "PASS ../../../../../Alexandre/AppData/Local/Temp/jest_only_changed/__tests__/file1.test.js
      ✓ file1 (2ms)

    Test Suites: 1 passed, 1 total
    Tests:       1 passed, 1 total
    Snapshots:   0 total
    Time:        3.449s
    Ran all test suites related to changed files."

      143 |
      144 |   ({stderr} = runJest(DIR, ['--lastCommit']));
    > 145 |   expect(stderr).toMatch(/PASS __tests__(\/|\\)file1.test.js/);
          |                  ^
      146 |
      147 |   writeFiles(DIR, {
      148 |     '__tests__/file2.test.js': `require('../file2'); test('file2', () => {});`,

      at Object.<anonymous>.test (e2e/__tests__/only_changed.test.js:145:18)

  ● gets changed files for hg

    Error

      34 |       ERROR: ${result.error}
      35 |     `;
    > 36 |     throw new Error(message);
         |           ^
      37 |   }
      38 |
      39 |   return result;

      Error:
            ORIGINAL CMD: hg --config ui.username=jest_test init
            STDOUT:
            STDERR: 'hg' is not recognized as an internal or external command,
      operable program or batch file.
            STATUS: 1
            ERROR: undefined

      at run (e2e/Utils.js:36:11)
      at Object.<anonymous> (e2e/__tests__/only_changed.test.js:201:3)
      at step (e2e/__tests__/only_changed.test.js:26:191)
      at e2e/__tests__/only_changed.test.js:26:437
      at Object.<anonymous> (e2e/__tests__/only_changed.test.js:26:99)

  ● path on Windows is case-insensitive

    expect(received).toMatch(expected)

    Expected value to match:
      /PASS __tests__(\/|\\)file2.test.js/
    Received:
      "PASS ../../../../../../../Alexandre/AppData/Local/Temp/jest_only_changed/outer_dir/inner_dir/__tests__/file3.test.js
    PASS ../../../../../../../Alexandre/AppData/Local/Temp/jest_only_changed/outer_dir/inner_dir/__tests__/file2.test.js

    Test Suites: 2 passed, 2 total
    Tests:       2 passed, 2 total
    Snapshots:   0 total
    Time:        7.849s
    Ran all test suites related to changed files."

      267 |
      268 |   expect(stderr).not.toMatch(/PASS __tests__(\/|\\)file1.test.js/);
    > 269 |   expect(stderr).toMatch(/PASS __tests__(\/|\\)file2.test.js/);
          |                  ^
      270 |   expect(stderr).toMatch(/PASS __tests__(\/|\\)file3.test.js/);
      271 | });
      272 |

      at Object.<anonymous>.test (e2e/__tests__/only_changed.test.js:269:18)

 FAIL  e2e/__tests__/globals.test.js (35.212s)
  ● basic test constructs

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot "basic test constructs 1".

    - Snapshot
    + Received

    @@ -1,6 +1,6 @@
    - "PASS __tests__/basic.test-constructs.test.js
    + "PASS ../../../../../Alexandre/AppData/Local/Temp/global-variables.test/__tests__/basic.test-constructs.test.js
        ✓ it
        ✓ test
        describe
          ✓ it
          ✓ test

      48 |
      49 |   const {summary, rest} = extractSummary(stderr);
    > 50 |   expect(rest).toMatchSnapshot();
         |                ^
      51 |   expect(summary).toMatchSnapshot();
      52 | });
      53 |

      at Object.<anonymous>.test (e2e/__tests__/globals.test.js:50:16)

  ● skips

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot "skips 1".

    - Snapshot
    + Received

    @@ -1,6 +1,6 @@
    - "PASS __tests__/skips-constructs.test.js
    + "PASS ../../../../../Alexandre/AppData/Local/Temp/global-variables.test/__tests__/skips-constructs.test.js
        ✓ it
        ○ skipped 4 tests
        xdescribe
          ○ skipped 2 tests
        describe.skip

      78 |
      79 |   const {summary, rest} = extractSummary(stderr);
    > 80 |   expect(rest).toMatchSnapshot();
         |                ^
      81 |   expect(summary).toMatchSnapshot();
      82 |   expect(status).toBe(0);
      83 | });

      at Object.<anonymous>.test (e2e/__tests__/globals.test.js:80:16)

  ● only

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot "only 1".

    - Snapshot
    + Received

    @@ -1,6 +1,6 @@
    - "PASS __tests__/only-constructs.test.js
    + "PASS ../../../../../Alexandre/AppData/Local/Temp/global-variables.test/__tests__/only-constructs.test.js
        ✓ test.only
        ✓ it.only
        ✓ fit
        ○ skipped 1 test
        fdescribe

      109 |
      110 |   const {summary, rest} = extractSummary(stderr);
    > 111 |   expect(rest).toMatchSnapshot();
          |                ^
      112 |   expect(summary).toMatchSnapshot();
      113 | });
      114 |

      at Object.<anonymous>.test (e2e/__tests__/globals.test.js:111:16)

  ● cannot test with no implementation

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot "cannot test with no implementation 1".

    - Snapshot
    + Received

    @@ -1,6 +1,6 @@
    - "FAIL __tests__/only-constructs.test.js
    + "FAIL ../../../../../Alexandre/AppData/Local/Temp/global-variables.test/__tests__/only-constructs.test.js
        ● Test suite failed to run

          Missing second argument. It must be a callback function.

            1 |

      126 |
      127 |   const {summary} = extractSummary(stderr);
    > 128 |   expect(cleanStderr(stderr)).toMatchSnapshot();
          |                               ^
      129 |   expect(summary).toMatchSnapshot();
      130 | });
      131 |

      at Object.<anonymous>.test (e2e/__tests__/globals.test.js:128:31)

  ● skips with expand arg

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot "skips with expand arg 1".

    - Snapshot
    + Received

    @@ -1,6 +1,6 @@
    - "PASS __tests__/skips-constructs.test.js
    + "PASS ../../../../../Alexandre/AppData/Local/Temp/global-variables.test/__tests__/skips-constructs.test.js
        ✓ it
        ○ xtest
        ○ xit
        ○ it.skip
        ○ test.skip

      157 |
      158 |   const {summary, rest} = extractSummary(stderr);
    > 159 |   expect(rest).toMatchSnapshot();
          |                ^
      160 |   expect(summary).toMatchSnapshot();
      161 | });
      162 |

      at Object.<anonymous>.test (e2e/__tests__/globals.test.js:159:16)

  ● only with expand arg

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot "only with expand arg 1".

    - Snapshot
    + Received

    @@ -1,6 +1,6 @@
    - "PASS __tests__/only-constructs.test.js
    + "PASS ../../../../../Alexandre/AppData/Local/Temp/global-variables.test/__tests__/only-constructs.test.js
        ○ it
        ✓ test.only
        ✓ it.only
        ✓ fit
        fdescribe

      187 |
      188 |   const {summary, rest} = extractSummary(stderr);
    > 189 |   expect(rest).toMatchSnapshot();
          |                ^
      190 |   expect(summary).toMatchSnapshot();
      191 | });
      192 |

      at Object.<anonymous>.test (e2e/__tests__/globals.test.js:189:16)

Most things in Jest would be typed with BaseProjectConfig with the minimal set of options that any runner (even for non-test use cases) would share, which is threaded to most places in Jest. Then there would be a type JestProjectConfig which is threaded to everything from jest-runner onwards to jest-jasmine etc. I think this change is quite involved, but the end-state sounds enticing to me. What do you think?

That definitely sounds like an ideal solution, but I'm not sure how people would differentiate between project and global config. Do you imagine everything still being in a single flat configuration? Would it be possible at all to check for typos in configuration in normalize then, when we can't limit the keys present? I suppose we could load all global config, then load runners and either query them for schemas to pass config through for validation. I do think that typing out the config might be confusing for consumers though.

I do think @aaronabramov's first suggestion should be the way we go, at least for a first iteration. I do think to properly separate config we'll have to do a breaking change anyways, so why not design something properly at that point, but still solve the very real need of custom runner config with a simple tuple similar to reporters for now?

Just tried to write a runner and was surprised to find that this doesn't exist.  I guess ones like jest-runner-eslint just rely on eslint picking up its own config via the standard ways rather than getting it from Jest (e.g. package.json, .eslintrc.json, etc) and I guess that's the only way to go for now.
I don't entirely understand the interaction between the project config and global config, so can't really comment intelligently on @aaronabramov's original suggestion (it looks like it would only support it in the global config, which isn't very useful if you're using one runner in one project and another in another, e.g. the default runner for tests in one project and the eslint runner for linting in another).

Still no solution? If anyway can guide me a bit from where we can start that would be great.
Otherwise, we should use hacky solutions. And yes, there is a way. And yes, this should land in runners implementations that you want to use, until the official jest support come.
The solution is that runners should try to read from config.haste[runner-name]. Yes, it gives warnings, but the important thing is that it doesn't break the process.
I've tested that solution and it's great for now. I probably will fork the babel and eslint runners for now if they don't accept my PRs.

Please don't contribute hacks to the runners. Either apply the patch locally or maybe spend this time to actually implement the feature in Jest. You can start with normalize.ts file and see how other similar options are configured and pass the parameters down

Yea, agree. Thanks for the starting point.

bump

bump

bump


OSX: paste doesn't work

VSCode Version: 1.1.1
OS Version:  10.11.4

Steps to Reproduce:

copy from any document (cmd-C)
verify paste works in other apps (cmd-V)
attempt to paste into a document open in Code (cmd-V)
observe paste fails

I was not able to reproduce this in OSX 10.11.5 following the steps provided. Are you talking about a specific type of "document" or just anything with highlightable text?

Happens for me

VSCode Version: 1.1.1
OS Version: 10.11.5

Steps to reproduce

Copy some text to clipboard in some other application
Verify it pastes correctly
Select a file in VST, select All (Command + A), select Copy (Command + C)
In another file in VSC do paste (Command + P)
Text from previous copy action will paste instead of text selected and copied in VSC.
If instead of doing Command+A to select all, you explicitly drag across the text and copy, then paste will work.
Select all plus copy doesn't work

I wonder if it is related to an OSX update; I have now noticed it in multiple apps.  Rebooting seems to have fixed it for all apps, including Code (where I first noticed the issue, and apparently wrongly blamed Code.  Sorry Code!).

This was indeed an OSX issue for me. The following worked:
launchctl stop com.apple.pboard
launchctl start com.apple.pboard

See http://apple.stackexchange.com/questions/31866/copy-and-cut-sometimes-dont-work

I have the same issue, consistently. Sometimes it helped to restart VSCode, but in the past two days, not so much. I run 10.12.1 and VSC 1.8.0


Make .dockercfg with json.MarshallIndent

Fixes #10129
Makes the .dockercfg more human parsable.
Also cleaned up the (technically) racey login test.

nice LGTM

Drone is dead, lol

you have a bad rebase or something?

or this new change doesnt work and the first original change did...? idk

@jfrazelle Something with drone, no?

heh, other pr works :)

Works locally.

I literally have no idea other PRs are working

can you try rebasing or something? it's almost like you have michaels libcontainer PR patch which actually is a bug i can reproduce locally

ok im trying one more time

This is NOT drone. It does NOT work for me locally.

do not fret however we think/know this is part of the weird go binary size bug we are looking into ;) keep the faith and have a good weekend

if you rebase on master it will be fixed, sorry!

Rebased

LGTM

LGTM


Arrow Flight and/or API support

Hi @fabrice-etanchaud ,
Has there been any work on arrow flight support? And is there a timeline on it?
We're considering forking and adding the support ourselves but if there is existing work, that seems like the better option.
Thanks!

Hello @mrietveld-leap , Thank you for your interest in the adapter !
No, I had no time to work on the project these last months, sorry.
I am starting a rewriting to keep close to the spark (fishtown maintained) adapter conventions.
As dbt does not process data, and only uses the connection to send server commands, what are your needs for using arrow flight ? getting rid of odbc would be a good thing, for sure.
Looking forward.

As dbt does not process data by itself (the only data flows I can think of are upstream when creating a seed, or downstream when consulting the information_schema), switching to Arrow flight would not bring performance benefits, but would trim the fat of all the odbc required stuff.
Adding API support would bring space/folders management (CREATE SCHEMA), and external tables (creation of sources from scratch).

started implementing a flight connection using :
https://docs.dremio.com/software/client-applications/python/


Endpoint for downloading file/layer data.

Some data can be downloaded from a table. Still for larger datasets an endpoint for downloading layer data is needed.

Related: #57 , #159


Iotaz migration (QScript)

@djspiewak This PR represents my work on migrating qscript/package.scala to iotaz with any dependencies.
It is ready for review. My personal concerns with this code are:

Materializers for instances. They are rather verbose and pretty ugly. They are so repetetive that I even used IntelliJ live templates to generate most of the code.
The issue I opened in iota regarding instances is (here)[https://github.com/frees-io/iota/issues/218]. It seems like there is a plan to implement something better over next few months. I was also pointed to scalaz-deriving but I already had noticable amount of code rewriten with Materalizers and did not understand a bit of that. There are currently 30 of those, rewriting them to anything that the rewriting person understands shouldn't take more than one working day.
The good thing about those, is that they just work. It even covered some complex cyclic dependency case with shapeless.Lazy.
Injectable. I removed Aux from there as it caused compiler errors (like AssertionError inside compiler). I made id implicit as couple of parts of code rely on it. Actually that code previously used inject combined with Inject.reflexiveInstance. I hope this Aux thing was not important.
 Although it is only file move, package still is quasar.qscript. I did it to avoid move refactor back and forth. The move was done because of SubInject macro that injects "subcoproduct" into another coproduct can't be in qscript module as it needs to be in a separate compiler run. It depends on Injectable as it creates it. So I put both of those in foundation as it seemed like reasonable place.
So the question is, what to do with this? Is there a better place to put it, a new module perhaps? If it should stay where it is, should I change package of Injectable to be quasar.fp?

I updated iotaz dependency to 0.3.8-SNAPSHOT as it contains my fix for missing hashCode implementation. I merged with master. The build is passing now.
I have further coproducts migrated in iotaz-migration-2 branch. I will create PR after this one is merged.
I also did some quick compilation performance tests. qscript module compiles ~3.2 times faster. The overall compilation time went down from 21.5 to 16 minutes.
Although those "benchmarks" were not anything special, in all the comparisons compilation was consistently faster for the iotaz version.

I'll take a look at this asap. Nice work! Regarding Injectable, I would say just change the package name and leave it where it is. I'm not too fussed about where it sits. The materializer stuff is more annoying, but there's not a lot of good ways around it right now, and using scalaz-deriving would almost certainly give back all the compilation time gains we just achieved (also likely wouldn't work).

Oh, side-note… I'm really reticent to depend on anything -SNAPSHOT due to the special semantics that maven applies to that version quantifier: it makes the build non-reproducible. I would rather publish a hash version snapshot of iotaz so that things are stable and then depend on that. I can take care of that and submit a PR to you.

Ok, it looks like iotaz's settings are dictated by sbt-freestyle and sbt-org-plugin, which enforce sonatype without any option of bintray, which in turn means that it's not really possible for me to meaningfully publish a stable hash snapshot. sigh

@wemrysi @alissapajer @djspiewak I fixed all the issues.


chore(storybook): Fix toolbar state not updated immediately after an editor state change

Overview

This PR tries to fix #259 by replacing the eventListener on Storybook.
Changes Introduced

onSelectionUpdate changed to onTransation on typist editor toolbar decorator.editor.on('selectionUpdate', handleSelectionUpdate)
// is changed to
editor.on('transaction', handleTransactionUpdate)

Thanks!
PR Checklist

[x] Pull request title follows the Conventional Commits Specification
[ ] Added/updated unit test cases and/or end-to-end test cases
[ ] Added/updated documentation to Storybook or README.md

Test plan
Doesn't change any existing features, just introduces fix for #259.

Demo

Before
After

Keyboard events and editor button clicks did not update the toolbar
Keyboard shortcuts and toolbar clicks correctly re-render editor toolbar.

@ayushanand18 FYI, I changed the PR title from fix to chore because fix would publish a new version (which we don't need for this one), removed the issue number from the title (which is added automatically to the commit message once the PR is merged), and also re-worded the commit message a bit to make it more clear what it's actually doing.

FYI, I changed the PR title from fix to chore because fix would publish a new version [...], removed the issue number from the title [...], and also re-worded the commit message a bit [...]

Thanks a lot @rfgamaral! I'll make sure to follow those guidelines for any future contributions.


Provisioning of centos 7 boxes on virtualbox 6.1.x fails due to unavailable upstream repo

Running vagrant up of a centos 7 VM on a macos 10.14.6 host with virtualbox 6.1.6 fails with:
$ vagrant up --provision admin
Bringing machine 'admin' up with 'virtualbox' provider...
==> admin: Importing base box 'centos/7'...
==> admin: Matching MAC address for NAT networking...
==> admin: Checking if box 'centos/7' version '1905.1' is up to date...
==> admin: Setting the name of the VM: platform-ansible_admin_1588037835907_99480
==> admin: Clearing any previously set network interfaces...
==> admin: Preparing network interfaces based on configuration...
    admin: Adapter 1: nat
==> admin: Forwarding ports...
    admin: 22 (guest) => 2222 (host) (adapter 1)
==> admin: Booting VM...
==> admin: Waiting for machine to boot. This may take a few minutes...
    admin: SSH address: <IP_ADDRESS>:2222
    admin: SSH username: vagrant
    admin: SSH auth method: private key
    admin:
    admin: Vagrant insecure key detected. Vagrant will automatically replace
    admin: this with a newly generated keypair for better security.
    admin:
    admin: Inserting generated public key within guest...
    admin: Removing insecure key from the guest if it's present...
    admin: Key inserted! Disconnecting and reconnecting using new SSH key...
==> admin: Machine booted and ready!
[admin] No Virtualbox Guest Additions installation found.
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.melbourneitmirror.net
 * extras: mirror.intergrid.com.au
 * updates: centos.melbourneitmirror.net
Resolving Dependencies
--> Running transaction check
---> Package centos-release.x86_64 0:7-6.1810.2.el7.centos will be updated
---> Package centos-release.x86_64 0:7-8.2003.0.el7.centos will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package              Arch         Version                     Repository  Size
================================================================================
Updating:
 centos-release       x86_64       7-8.2003.0.el7.centos       base        26 k

Transaction Summary
================================================================================
Upgrade  1 Package

Total download size: 26 k
Downloading packages:
No Presto metadata available for base
Public key for centos-release-7-8.2003.0.el7.centos.x86_64.rpm is not installed
warning: /var/cache/yum/x86_64/7/base/packages/centos-release-7-8.2003.0.el7.centos.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Importing GPG key 0xF4A80EB5:
 Userid     : "CentOS-7 Key (CentOS 7 Official Signing Key<EMAIL_ADDRESS> Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7 f4a8 0eb5
 Package    : centos-release-7-6.1810.2.el7.centos.x86_64 (@anaconda)
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Updating   : centos-release-7-8.2003.0.el7.centos.x86_64                  1/2
  Cleanup    : centos-release-7-6.1810.2.el7.centos.x86_64                  2/2
  Verifying  : centos-release-7-8.2003.0.el7.centos.x86_64                  1/2
  Verifying  : centos-release-7-6.1810.2.el7.centos.x86_64                  2/2

Updated:
  centos-release.x86_64 0:7-8.2003.0.el7.centos

Complete!
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.melbourneitmirror.net
 * extras: mirror.intergrid.com.au
 * updates: centos.melbourneitmirror.net
http://vault.centos.org/7.7.1908/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

 One of the configured repositories failed (CentOS-7.7.1908 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=C7.7.1908-base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable C7.7.1908-base
        or
            subscription-manager repos --disable=C7.7.1908-base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=C7.7.1908-base.skip_if_unavailable=true

failure: repodata/repomd.xml from C7.7.1908-base: [Errno 256] No more mirrors to try.
http://vault.centos.org/7.7.1908/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
==> admin: Checking for guest additions in VM...
    admin: No guest additions were detected on the base box for this VM! Guest
    admin: additions are required for forwarded ports, shared folders, host only
    admin: networking, and more. If SSH fails on this machine, please install
    admin: the guest additions and repackage the box to continue.
    admin:
    admin: This is not an error message; everything may continue to work properly,
    admin: in which case you may ignore this message.
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

yum install -y kernel-devel-`uname -r` --enablerepo=C*-base --enablerepo=C*-updates

Stdout from the command:

Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.melbourneitmirror.net
 * extras: mirror.intergrid.com.au
 * updates: centos.melbourneitmirror.net

Stderr from the command:

http://vault.centos.org/7.7.1908/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

 One of the configured repositories failed (CentOS-7.7.1908 - Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=C7.7.1908-base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable C7.7.1908-base
        or
            subscription-manager repos --disable=C7.7.1908-base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=C7.7.1908-base.skip_if_unavailable=true

failure: repodata/repomd.xml from C7.7.1908-base: [Errno 256] No more mirrors to try.
http://vault.centos.org/7.7.1908/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

Following the indications of the error message I was able to install the virtualbox guest additions after ssh-ing to the box:
yum-config-manager --save --setopt=C7.7.1908-base.skip_if_unavailable=true
yum-config-manager --save --setopt=C7.7.1908-update.skip_if_unavailable=true
yum install -y kernel-devel-`uname -r` --enablerepo=C*-base --enablerepo=C*-updates

And then vagrant vbguest --do install
I have checked http://vault.centos.org/7.7.1908/os/ and it does not indeed contain a x86_64 directory anymore, just Sources.

so when vagrant up a new vm, i must ssh in vm and manually run some scripts above everytime?

Obviously not really a sustainable solution but this could be a workaround if you are not destroying the vm regularly. Naturally, a fix must be found. I am just not too sure what the cleanest solution would be.
Another workaround would be to not use a centos7 box that requires virtualbox extensions to be installed, such as bento/centos-7, so you won't need the vbguest plugin.

But the error not happened before i upgrade VirtualBox from 6.0.x to 6.1.x via brew.
So when i saw the error, my first thought is current virtualbox version not compatible with vagrant 2.2.7

you means that the source removed last month?

I am experiencing this, too. It started happening yesterday morning, somewhere between 9AM and 11:30AM CST. No change of Virtualbox version or anything else. Just rebuilding the VM. I maintain a developer-oriented VM automation project, and the VM does get destroyed and rebuilt regularly.

@johann-koebbe-fidelity I give up box centos/7,  use bentos/7 instead.

@johann-koebbe-fidelity I give up box centos/7, use bentos/centos-7 instead.

I'm using a custom base box directly from a CentOS ISO.

@endemics What is the purpose of using the C7.*-base repos? I was just doing a little poking around and experimenting, and it doesn't look like I actually need to use them.
=> yum search --show-duplicates kernel-devel
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.mi.incx.net
 * epel: mirror.twinlakes.net
 * extras: mirrors.codec-cluster.org
 * updates: ewr.edge.kernel.org
========================================================================= N/S matched: kernel-devel =========================================================================
kernel-devel-3.10.0-1127.el7.x86_64 : Development package for building kernel modules to match the kernel

Which is coming out of /etc/yum.repos.d/CentOS-Base.repo. When I enable C7.*-base, I get a much longer list (due to --show-duplicates), but the last one (most recent) is the same.

Possibly related: https://github.com/dotless-de/vagrant-vbguest/pull/373

@endemics Do you know what is the purpose of using the C7.*-base repos? I was just doing a little poking around and experimenting, and it doesn't look like I actually need to use them.

@johann-koebbe-fidelity  actually no, I was a bit unclear about the whole approach, which is why I haven't proposed a solution.

It was the original attempt to get a matching kernel-devel package for the installed kernel. And it also worked for quite some time

@fnordfish I can report that the fix for #373 present in 0.24.0.beta1 also fix this issue for me.

I've been looking at this for the last couple of days and thought I just add a footnote to this.
When vbguest plugin is installing kernel-devel :
yum install -y kernel-devel-uname -r --enablerepo=C*-base --enablerepo=C*-updates
The wildcards in the enablerepo will pick up definitions from within /etc/yum.repos.d/CentOS-Vault.repo e.g.
[C7.0.1406-base]
name=CentOS-7.0.1406 - Base
baseurl=http://vault.centos.org/7.0.1406/os/$basearch/
During a CentOS upgrade (One started on the 27th April 2020, which aligns with the raising of this ticket), some repos are offline and the yum repo resolving logic falls back to the vault repos.
When the CentOS upgrade process completes (after a few days), this problem will be resolved, but it really shouldn't be a problem in the first place.
As mentioned above, are the enablerepos really needed? I would have though the default enabled repos would be enough for this kind of build process.

The CentOS Installer was introduced in #314 combining ideas from #231, #223
Those discussions are pretty old (dating back to 2016), so chances are centos changed stuff in the meantime.


Error: Invalid escape sequence

Hi Andy, executing the latest code with "./aws2tf.sh -v yes"

│ Error: Invalid escape sequence
│
│   on /Users/kj/Desktop/aws2tf-master/generated/tf.xxxxxxxxxxxx_ap-southeast-1/aws_cloudwatch_event_target__default__SSMOpsItems-Autoscaling-instance-launch-failure__SSMOpsItems-Autoscaling-instance-launch-failureTarget.tf line 22, in resource "aws_cloudwatch_event_target" "default__SSMOpsItems-Autoscaling-instance-launch-failure__SSMOpsItems-Autoscaling-instance-launch-failureTarget":
│   22: input_template = "={ title: Auto Scaling EC2 instance launch failed, description: CloudWatch Event Rule SSMOpsItems-Autoscaling-instance-launch-failure was triggered. Your EC2 instance launch has failed. See below for more details., source: EC2 Auto Scaling, category: Availability, severity:2, resources: , operationalData: { /aws/dedup: {type: SearchableString, value: {\dedupString:\SSMOpsItems-Autoscaling-instance-launch-failure}}, /aws/automations: { value: [ { \automationType: \AWS:SSM:Automation, \automationId: \AWS-ASGEnterStandby\ }, { \automationType: \AWS:SSM:Automation, \automationId: \AWS-ASGExitStandby\ } ] }, autoscaling-group-name: {value: }, status-message: {value: }, start-time: {value: }, end-time: {value: }, cause: {value: }} }"
│
│ The symbol ":" is not a valid escape sequence selector.

The symbol "S" is not a valid escape sequence selector.

The symbol "}" is not a valid escape sequence selector.

The symbol ":" is not a valid escape sequence selector.

The symbol "A" is not a valid escape sequence selector.

The symbol "," is not a valid escape sequence selector.

The symbol ":" is not a valid escape sequence selector.

The symbol "A" is not a valid escape sequence selector.

The symbol "a" is not a valid escape sequence selector.

The symbol ":" is not a valid escape sequence selector.

The symbol "A" is not a valid escape sequence selector.

The symbol "d" is not a valid escape sequence selector.

The symbol ":" is not a valid escape sequence selector.

The symbol "S" is not a valid escape sequence selector.

Hmm - I'm having trouble reproducing this one - could you
delete the file aws_cloudwatch_event_target__default__SSMOpsItems-Autoscaling-instance-launch-failure__SSMOpsItems-Autoscaling-instance-launch-failureTarget.tf
and then do a:
terraform state show aws_cloudwatch_event_target.default__SSMOpsItems-Autoscaling-instance-launch-failure__SSMOpsItems-Autoscaling-instance-launch-failureTarget
(redact what you need to) - and post the output from the above here please.

committed a potential fix - quite hard to reproduce this one.
If it still errors:
delete the offending aws_cloudwatch_event_target__default__SSMOpsItems-Autoscaling-instance-launch-failure__SSMOpsItems-Autoscaling-instance-launch-failureTarget.tf     file

and post the (redacted) output of

terraform state show aws_cloudwatch_event_target.default__SSMOpsItems-Autoscaling-instance-launch-failure__SSMOpsItems-Autoscaling-instance-launch-failureTarget
That should help me track it down.

Rule name:
SSMOpsItems-Autoscaling-instance-launch-failure
Description:
Rule for SSM OpsCenter to create OpsItems when EC2 Auto Scaling instance launch failed

Can I get some more of the error / screen output from this one please.


[Autocomplete] Multi-select pop-up not shown when already focused

Current Behavior 😯
When clicking on the input rendered by the Autocomplete, it pops up with the available selections. The user selects a value, after which the input shows the selected option as a chip. When the user then clicks inside of the input again - the popup does not appear. Instead, the user has to either select the arrow pointing down, or click outside of the select, after which it loses focus, only to then click inside of the input again to trigger the popup.
Video:

Expected Behavior 🤔
After the user selects the first option, the user should be able to click inside the (already) focused input to trigger the popup. The user should not have to lose focus on the input to trigger the popup again.
Steps to Reproduce 🕹
Using the MUI Labs page: https://material-ui.com/components/autocomplete/#multiple-values
Using any of the three multi-selects, I am using the filteredSelectedOptions.
Steps:

Click inside of the input, on the right of the Inception chip.
Select any value inside of the popup.
Click inside of the input again, to the right of your selected option.
You should not see a popup appear.

Context 🔦

My company is using this input for forms. The form allows the user to select multiple values. If the user is not able to select another value after clicking inside the already focused text field, it might lead the user to believe this isn't a multi-select.
Your Environment 🌎
Using the online docs page on  https://material-ui.com/components/autocomplete/#multiple-values with Google Chrome version 78.0.3904.70 official build.

@FlorisWarmenhoven Thank you for the report. What do you think of implementing this toggle behavior when the input is empty, and only?
I have tried something like this to get a sense of the UX it produces
diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
index e60cf0804..28caff93c 100644
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -635,6 +635,12 @@ export default function useAutocomplete(props) {
     }
   };

+  const handleClick = () => {
+    if (inputValue === '') {
+      handlePopupIndicator();
+    }
+  };
+
   let dirty = freeSolo && inputValue.length > 0;
   dirty = dirty || (multiple ? value.length > 0 : value !== null);

@@ -672,6 +678,7 @@ export default function useAutocomplete(props) {
       value: inputValue,
       onBlur: handleBlur,
       onFocus: handleFocus,
+      onClick: handleClick,
       onChange: handleInputChange,
       // if open then this is handled imperativeley so don't let react override
       // only have an opinion about this when closed

I think it's better. Regarding the actual implementation, the above changes are not enough
as the focus event also open the popup.
I think that we would like to look at #18101 at the same time, to make sure we have a global solution.

I might be misunderstanding you - but if you only handle this toggling behavior when the input field is empty - then my initial bug report still stands:
I expect the popup to always toggle when the user clicks inside of the input field. I don't see this as an enhancement, I see this as core functionality.
Googling searchable selects and picking the first option I see:
https://selectize.github.io/selectize.js/
If you scroll down a tiny bit to the email input, you can type and select an email - after which you can immediately click inside the select field to trigger the popup again.

@FlorisWarmenhoven selectize.js seems to rely on the equivalent to our disableCloseOnSelect={true} filterSelectedOptions={true} options.
input value empty != autocomplete empty.

Terribly sorry @oliviertassinari, but I'm not familiar with either code bases. I was purely looking at functionality.
Are you saying that the functionality I expect (where clicking the input after selecting a value, it should open the popup again), is not something you agree with?


Linkerd doesn't work in an EKS cluster with Weave-Net installed

What you expected to happen?
I expected for weave-net to not impact the installation of linkerd.
What happened?
Linkerd injection is unable to function properly because of the network disconnect between the EKS managed masters and the worker nodes, due to the overlay network.
I see the following in my API server logs (note: these are not in order by timestamp):
E0830 16:54:37.736044 8 controller.go:111] loading OpenAPI spec for "v1alpha1.tap.linkerd.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: service unavailable
, Header: map[Content-Type:[text/plain; charset=utf-8] X-Content-Type-Options:[nosniff]]

E0830 16:54:34.740387 8 available_controller.go:316] v1alpha1.tap.linkerd.io failed with: Get https://<IP_ADDRESS>:8089: Address is not allowed

W0830 16:54:15.269939 8 dispatcher.go:68] Failed calling webhook, failing open linkerd-proxy-injector.linkerd.io: failed calling webhook "linkerd-proxy-injector.linkerd.io": Post https://linkerd-proxy-injector.linkerd.svc:443/?timeout=30s: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

E0830 16:54:15.269993 8 dispatcher.go:69] failed calling webhook "linkerd-proxy-injector.linkerd.io": Post https://linkerd-proxy-injector.linkerd.svc:443/?timeout=30s: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

W0830 16:19:45.563890 8 dispatcher.go:68] Failed calling webhook, failing open linkerd-proxy-injector.linkerd.io: failed calling webhook "linkerd-proxy-injector.linkerd.io": Post https://linkerd-proxy-injector.linkerd.svc:443/?timeout=30s: no endpoints available for service "linkerd-proxy-injector"

E0830 16:20:54.693839 8 available_controller.go:316] v1alpha1.tap.linkerd.io failed with: Operation cannot be fulfilled on apiservices.apiregistration.k8s.io "v1alpha1.tap.linkerd.io": the object has been modified; please apply your changes to the latest version and try again

E0830 16:14:33.928098 8 dispatcher.go:69] failed calling webhook "linkerd-proxy-injector.linkerd.io": Post https://linkerd-proxy-injector.linkerd.svc:443/?timeout=30s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

I0830 16:55:19.544246 8 log.go:172] http2: server: error reading preface from client <IP_ADDRESS>:54827: read tcp <IP_ADDRESS>:443-><IP_ADDRESS>:54827: read: connection reset by peer

E0830 16:20:54.693839 8 available_controller.go:316] v1alpha1.tap.linkerd.io failed with: Operation cannot be fulfilled on apiservices.apiregistration.k8s.io "v1alpha1.tap.linkerd.io": the object has been modified; please apply your changes to the latest version and try again

How to reproduce it?
eksctl create cluster
... wait for cluster to be created

# remove default CNI
kubectl delete ds -n kube-system aws-node

# install weave-net CNI
kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')"

# at this point you need to terminate the ec2 worker node instances to
# trigger new ones to be created to make use of weave-net CNI

# install linkerd
linkerd install | kubectl apply -f -

# install a deployment with injection turned on
linkerd inject deployment.yaml | kubectl apply -f -

# Open the linkerd dashboard
linkerd dashboard &

# browse to the deployment that was just installed and
# you will see the 'meshed' status as 0 pods being meshed

Anything else we need to know?
I have also logged this issue here: https://github.com/linkerd/linkerd2/issues/3353
Versions:
Kubernetes Version: 1.13
Cluster Environment: EKS
Host OS: linux, amazon-eks-node-1.13-v20190701 (ami-03a55127c613349a7)
Linkerd version: Client version: stable-2.5.0, Server version: stable-2.5.0
Weave: 2.5.2
kubectl version:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T12:36:28Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.10-eks-5ac0f1", GitCommit:"5ac0f1d9ab2c254ea2b0ce3534fd72932094c6e1", GitTreeState:"clean", BuildDate:"2019-08-20T22:39:46Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}

Logs:
INFO: 2019/08/30 16:19:54.777777 Command line options: map[host-root:/host http-addr:<IP_ADDRESS>:6784 metrics-addr:<IP_ADDRESS>:6782 nickname:ip-192-168-30-8.us-west-2.compute.internal no-dns:true ipalloc-range:<IP_ADDRESS>/12 name:ca:08:a5:0c:69:5d conn-limit:100 datapath:datapath db-prefix:/weavedb/weave-net port:6783 docker-api: expect-npc:true ipalloc-init:consensus=1]
INFO: 2019/08/30 16:19:54.777830 weave  2.5.2
INFO: 2019/08/30 16:19:54.963680 Bridge type is bridged_fastdp
INFO: 2019/08/30 16:19:54.963698 Communication between peers is unencrypted.
INFO: 2019/08/30 16:19:54.970943 Our name is ca:08:a5:0c:69:5d(ip-192-168-30-8.us-west-2.compute.internal)
INFO: 2019/08/30 16:19:54.970976 Launch detected - using supplied peer list: [<IP_ADDRESS>]
INFO: 2019/08/30 16:19:54.998816 Checking for pre-existing addresses on weave bridge
INFO: 2019/08/30 16:19:55.001854 [allocator ca:08:a5:0c:69:5d] No valid persisted data
INFO: 2019/08/30 16:19:55.009880 [allocator ca:08:a5:0c:69:5d] Initialising via deferred consensus
INFO: 2019/08/30 16:19:55.010079 Sniffing traffic on datapath (via ODP)
INFO: 2019/08/30 16:19:55.020029 Listening for HTTP control messages on <IP_ADDRESS>:6784
INFO: 2019/08/30 16:19:55.020406 Listening for metrics requests on <IP_ADDRESS>:6782
INFO: 2019/08/30 16:19:55.040462 ->[<IP_ADDRESS>:6783] attempting connection
INFO: 2019/08/30 16:19:55.040664 ->[<IP_ADDRESS>:37253] connection accepted
INFO: 2019/08/30 16:19:55.041088 ->[<IP_ADDRESS>:6783|ca:08:a5:0c:69:5d(ip-192-168-30-8.us-west-2.compute.internal)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/08/30 16:19:55.041293 ->[<IP_ADDRESS>:37253|ca:08:a5:0c:69:5d(ip-192-168-30-8.us-west-2.compute.internal)]: connection shutting down due to error: cannot connect to ourself
INFO: 2019/08/30 16:19:55.726303 [kube-peers] Added myself to peer list &{[{42:28:60:3b:b0:3e ip-192-168-79-172.us-west-2.compute.internal} {3e:8d:91:9e:41:f1 ip-192-168-28-239.us-west-2.compute.internal} {ca:08:a5:0c:69:5d ip-192-168-30-8.us-west-2.compute.internal}]}
DEBU: 2019/08/30 16:19:55.732879 [kube-peers] Nodes that have disappeared: map[42:28:60:3b:b0:3e:{42:28:60:3b:b0:3e ip-192-168-79-172.us-west-2.compute.internal} 3e:8d:91:9e:41:f1:{3e:8d:91:9e:41:f1 ip-192-168-28-239.us-west-2.compute.internal}]
DEBU: 2019/08/30 16:19:55.732894 [kube-peers] Preparing to remove disappeared peer 42:28:60:3b:b0:3e
DEBU: 2019/08/30 16:19:55.734950 [kube-peers] Noting I plan to remove  42:28:60:3b:b0:3e
DEBU: 2019/08/30 16:19:55.737967 weave DELETE to http://<IP_ADDRESS>:6784/peer/42:28:60:3b:b0:3e with map[]
INFO: 2019/08/30 16:19:55.738530 [kube-peers] rmpeer of 42:28:60:3b:b0:3e: 0 IPs taken over from 42:28:60:3b:b0:3e

DEBU: 2019/08/30 16:19:55.748450 [kube-peers] Preparing to remove disappeared peer 3e:8d:91:9e:41:f1
DEBU: 2019/08/30 16:19:55.919771 [kube-peers] Noting I plan to remove  3e:8d:91:9e:41:f1
DEBU: 2019/08/30 16:19:56.120474 weave DELETE to http://<IP_ADDRESS>:6784/peer/3e:8d:91:9e:41:f1 with map[]
INFO: 2019/08/30 16:19:56.120917 [kube-peers] rmpeer of 3e:8d:91:9e:41:f1: 0 IPs taken over from 3e:8d:91:9e:41:f1

DEBU: 2019/08/30 16:19:57.320578 [kube-peers] Nodes that have disappeared: map[]
<IP_ADDRESS>
<IP_ADDRESS>
DEBU: 2019/08/30 16:19:57.408901 registering for updates for node delete events
INFO: 2019/08/30 16:22:31.021813 ->[<IP_ADDRESS>:36867] connection accepted
INFO: 2019/08/30 16:22:31.023735 ->[<IP_ADDRESS>:36867|2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)]: connection ready; using protocol version 2
INFO: 2019/08/30 16:22:31.023847 overlay_switch ->[2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)] using fastdp
INFO: 2019/08/30 16:22:31.023934 ->[<IP_ADDRESS>:36867|2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)]: connection added (new peer)
INFO: 2019/08/30 16:22:31.025548 ->[<IP_ADDRESS>:36867|2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)]: connection fully established
INFO: 2019/08/30 16:22:31.180258 Discovered remote MAC 52:90:47:46:77:55 at 2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)
INFO: 2019/08/30 16:22:31.524928 EMSGSIZE on send, expecting PMTU update (IP packet was 60028 bytes, payload was 60020 bytes)
INFO: 2019/08/30 16:22:31.525405 sleeve ->[<IP_ADDRESS>:6783|2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)]: Effective MTU verified at 8939
INFO: 2019/08/30 16:22:31.628231 Discovered remote MAC 0a:8c:da:1a:64:9b at 2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)
INFO: 2019/08/30 16:22:31.720215 Discovered remote MAC 2e:f7:64:42:d6:bd at 2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)
INFO: 2019/08/30 16:53:46.701892 Discovered remote MAC 0a:8c:da:1a:64:9b at 2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)
INFO: 2019/08/30 16:54:16.230675 Discovered remote MAC 26:36:3c:99:95:ca at 2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)
INFO: 2019/08/30 16:55:57.772277 Discovered remote MAC 52:90:47:46:77:55 at 2e:f7:64:42:d6:bd(ip-192-168-40-186.us-west-2.compute.internal)

I think this problem is really caused by how EKS works, and I doubt that there is much that can be done by you guys to fix this. But I figured I would post the problem here so it is known.

I have similar issue with EKS+Weavenet+istio
Objective:
To set up weave net CNI in EKS.
Steps Taken:

Create a nodeless cluster using eksctl
delete the default aws CNI ie aws-node.
install weave net CNI using kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$ (kubectl version | base64 | tr -d '\n')"
Opened the following ports on the nodes. - TCP/6783, UDP/6783-6784
scale up the cluster node group.
Create a NS 'api' which label as istio-injection=enabled
Install Istio service mesh in ns istio-system.
Deploy API pods in ns api

Expected Behaviour: Pods should get created successfully in ns api
Actual Behaviour: Error creating the ReplicaSet while creating the deployment. Following events are seen.
Warning   FailedCreate       replicaset/card-blue-6dd8f7f66c        Error creating: Internal error occurred: failed calling webhook "sidecar-injector.istio.io": Post https://istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s:  context deadline exceeded
Observation1: No such error seen when using AWS-NODE CNI. Error Happens only with Weavenet.
Observation2: Pods are scheduled fine even with weave net CNI if I remove the label from NS api ie istio-injection=enabled
K8s version: 1.14.6

Linkerd injection is unable to function properly because of the network disconnect between the EKS managed masters and the worker nodes, due to the overlay network.

As noted by @jwenz723 this is how EKS works.
@aman-sahni While this is not convenient you can use manual injection of proxy


remove jquery dependency or bump version to latest

 Issue by kaviththiranga
Tuesday Jan 23, 2018 at 01:22 GMT
Originally opened as https://github.com/ballerina-lang/composer/issues/4983

AFAIR we currently use jquery in some trivial use cases only. A lot of dependencies of jquery were removed when we revamped the composer as a react app. Find the possibility of getting rid of jquery completely or at least bump the version to a latest one to avoid security issues.

Composer is discontinued hence closing the issue.


Correct Debian for ARMHF installation steps

Proposed changes
My goal is to correct the installation instruction for Debian. The current document mixes up Debian for ARM and Raspbian.
Related issues (optional)
Fixes #2098
I was not entirely satisfied by the changes in the PR which fixed the issue. So here is my first contribution which clarifies the Debian part of this document.

I meant convenience script

Hi @NonCreature0714
I have two Raspberry Pi 2, a Raspbian and Ubuntu variant.
For both, I have been installing the Debian armhf packages. And it works fine.
I could try the convenience script on Ubuntu armhf. Do you think it makes sense? Sadly, I do not have a free SD card at the moment to try and test installing Docker with the convenience script on Debian armhf.

@andrewhsu PTAL


Fix dogstatsd config file path help message

What does this PR do?
Fix the help message of the --cfgpath flag of dogstatsd start, to refer to dogstatsd.yaml instead of datadog.yaml.
Motivation
Show the correct file name.
I lost too much time due to that.
Describe how you validated your changes

Possible Drawbacks / Trade-offs
Additional Notes

/merge


FEATURE: Composer AI helper

This change introduces a new composer button for the group members listed in the ai_helper_allowed_groups site setting.
Users can use chatGPT to review, improve, or translate their posts to English.

Looks great! Let's merge and let people test.
Next, I want to make the list of prompts completely data driven, so we can add / remove prompts from the database instead of hard coding it across various files. That will allow us to iterate quickly on the obscene amount of prompts suggestions we will receive.


cli: fprintf(NULL, ...) since eeb0f09

Since commit eeb0f09, the code sets output to NULL unconditionally, and then if the remote server won't do interleaving, the client attempts to fprintf(output, ...), which is wrong, and the compiler agrees with me:
[73/75] Building C object cli/CMakeFiles/netopeer2-cli.dir/commands.c.o
In file included from /nix/store/bq928ff6m7lvcfyvcdvgvqxhqi5f3ijq-glibc-2.35-224-dev/include/stdio.h:906,
                 from /home/jkt/work/cesnet/gerrit/github/CESNET/Netopeer2/cli/commands.c:26:
In function ‘fprintf’,
    inlined from ‘cmd_subscribe’ at /home/jkt/work/cesnet/gerrit/github/CESNET/Netopeer2/cli/commands.c:4759:9:
/nix/store/bq928ff6m7lvcfyvcdvgvqxhqi5f3ijq-glibc-2.35-224-dev/include/bits/stdio2.h:79:10: warning: argument 1 null where non-null expected [-Wnonnull]
   79 |   return __fprintf_chk (__stream, __USE_FORTIFY_LEVEL - 1, __fmt,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   80 |                         __va_arg_pack ());
      |                         ~~~~~~~~~~~~~~~~~
In file included from /nix/store/bq928ff6m7lvcfyvcdvgvqxhqi5f3ijq-glibc-2.35-224-dev/include/stdio.h:890:
/nix/store/bq928ff6m7lvcfyvcdvgvqxhqi5f3ijq-glibc-2.35-224-dev/include/bits/stdio2-decl.h: In function ‘cmd_subscribe’:
/nix/store/bq928ff6m7lvcfyvcdvgvqxhqi5f3ijq-glibc-2.35-224-dev/include/bits/stdio2-decl.h:49:12: note: in a call to function ‘__fprintf_chk’ declared ‘nonnull’
   49 | extern int __fprintf_chk (FILE *__restrict __stream, int __flag,
      |            ^~~~~~~~~~~~~

Yep, fixed.


Update README.md

pathway correction

Can i join your channel in town?

Can i join your channel in town?

Thank you for contributing to the River protocol. We are in the process of setting up a space for developers and we're talking about granting permissions or minting assets for contributors, but we haven't gotten around to that yet. Please subscribe to our twitter and be on the lookout for the new space https://x.com/buildonriver

already done thank you

Hey ser, anyway to contact you in telegram? I wanna build something and need to talk you

Come join our Friends of Towns town here: https://app.towns.com/t/10a78396e5860f3d4f8e020d40dbd753588f00e17d0000000000000000000000/

Done , thanks a lot