⚠ Bofrost.es has degraded performance

In 64449e9, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1432 ms

Resolved: Bofrost.es performance has improved in 3486c8a after 6 minutes.


provider/openstack - Fix edit load balancer issues.

closes https://github.com/spinnaker/spinnaker/issues/1205
closes https://github.com/spinnaker/spinnaker/issues/1189

LGTM


Split langmeta into langmeta-lowlevel and langmeta-highlevel

This pull request builds on https://github.com/scalameta/scalameta/pull/1179 and splits langmeta into lowlevel and highlevel parts. I'll need this split for my performance work, where I plan to downgrade the semanticdbScalacCore -> scalametaJVM dependency to semanticDbScalacCore -> langmetaLowlevelJVM.
Migration instructions:

s/"org.scalameta" %% "langmeta"/"org.scalameta" %% "langmeta-highlevel"/g
s/org.langmeta.io/org.langmeta.highlevel.io/g
s/org.langmeta.inputs/org.langmeta.highlevel.inputs/g
s/org.langmeta.semanticdb/org.langmeta.highlevel.semanticdb/g
s/org.langmeta.internal.semanticdb.schema/org.langmeta.lowlevel.semanticdb/g
s/org.langmeta.internal.semanticdb.{schema => s}/org.langmeta.lowlevel.{schema => s}/g

@olafurpg How do we tell mima that this pull request intentionally breaks backward compatibility?

I am not convinced this refactoring is worth its weight. This breaks close to every application I've written against semanticdb: scalafix, metadoc, doxy, language-server, corpus experiments. Even if we could automigrate it with scalafix then it take a lot of time to get all 3rd party scalafix rules to move to the highlevel package. As I mentioned in #1179, IJ is eager to auto-import org.langmeta modules so there are tons of references to those whether you like it or not 😉
I propose we keep the package layouts unchanged as much as possible, including internal.semanticdb.schema. Let's prioritize performance improvements without moving APIs.

I am btw taking compatibility extra seriously for scalafix because we compile rules from source, breaking changes in the API means that many scalafix rules that is shared via source may no longer compile.

You convinced me with your point about scalafix, so I'll be giving up the highlevel part.
I think we're in agreement that the rest make sense, and I will do just that in a separate PR together with performance changes.


Reaching Noise limit when polling the cosigning server

Right now we exchange the huge Spend PSBT to the Cosigning Server. Since it's not checking managers signatures anymore we have no reason to do so.
I reached the Noise message limit on regtest with 12 stakeholders 4 managers, a dozen of vaults and about 5 outputs. That's unreasonable to have this hard limit.

We are just going to strip the signatures before sending it to the Cosigning Server for now, since we don't require it to check the signatures anymore.


TEST PR: Refactor DeleteBlueprint modal dialog to use Modal from PF react

This backports one commit from master to rhel-8.1. This is a demo PR for testing if this gets picked by tests-scan tool.
If in the end you want to backport this commit feel free to merge, otherwise can be closed.

Works!


automate the git --config setup

after running http://github.com/russellbradley/my-env I change all git configuration user.name + user.email. It would be useful to have this run so when people set up their environments git-hacker will automatically have them set up their git-configuration env.

Done.


Feature/sifo580 Adding Podman to be used for registry access

what
Updating anvil image to install podman utility.

This will allow a daemonless way to perform docker  commands in a container.

why

The first usecase will be to perform a login and push/pull.
There will be other usecases for needing podman.

/test

One small nitpick, then LGTM

/test


Resolve UIDs to package names

Hi! Could you add a feature that resolves UIDs to package names?
To get the list of packages you can run the ADB shell command cmd package list packages -U.
package:com.oneplus.calculator uid:10147

I want to replace UIDs (e.g. 10147) with package names (e.g. com.oneplus.calculator)

Hm. Sounds tricky how to identify if a number in a message is a UID or not. Are there an specific rules you have in mind?

I guess matching the regex = ?\d{5} would be enough, while displaying both the number and potential package name at the same time. When we know which number is an UID (the logcat UID column), it can just be substituted with the package name.


Sdds header Inline menu dropdown functionality

What is your feature request?
The Inline menu in sdds header has dropdown_menu but there isn't a functionality to expand and collapse the menu on click.
So I am requesting to add the click functionality on dropdown menu to expand and collapse the submenus.
Currently we have to write additional javascript code to get the dropdown menu to expand and collapse on click.
Describe the solution you'd like
On click of a dropdown menu the menu should toggle between expanded and collapsed state and also there should be a feature to show another sub-submenu if you hover on the expanded submenu
Additional context
Below is the screenshot of the feature that I am requesting you to add

AB#971

Since this is a html/css component so javascript is shipped. In the upcoming @scania/tegel we will provide this as a web component aswell, which will include the javascript.


"private modifier is redundant" is unbelievable!

According to c# coding style private modifier is not only redundant but also it is necessary! no option for turning it off is really annoying!

https://github.com/icsharpcode/RefactoringEssentials/wiki/Custom-Rule-Sets-for-Analyzers

This is not same as turning it off!, I have more that 60 project in my current solution, should i do it manually for every project and for every new project!

It's not same as turn it off! Should I do it for my current 60+ projects and every new project at future!

How wonderful! Thanks so much.


Add a config option to simplify urls when using a subdirectory for modules

When your course directory is structured as :
course/
|-- materials
   |-- w01
   |-- w02

Then the keys and thus URLs generated for the course will be of form:
.../{course_name}/{course_instance}/materials_w01/w01_ch01/
For conciseness it would be preferred if the URLs would still be of form:
.../{course_name}/{course_instance}/w01/ch01/
My proposition is to add a module_folder = {path_to_folder} config option to conf.py, which automatically ignores the directory when generating keys.
Also slightly related to https://github.com/apluslms/a-plus-rst-tools/issues/146

I'd assume that auto detecting that the modules are all under the same directory is relatively easy. It would make the process less error prone (I'm almost positive that this will cause issues at some point if #146 isn't fixed in any other way), and I don't see a reason why anybody would deliberately want the longer URLs.

I'd assume that auto detecting that the modules are all under the same directory is relatively easy. It would make the process less error prone (I'm almost positive that this will cause issues at some point if #146 isn't fixed in any other way), and I don't see a reason why anybody would deliberately want the longer URLs.

The longer URLs are mainly needed for backwards-compatibility. Changing the exercise url keys in the middle of the course causes a lot of issues. A+ would not connect the new keys to the existing exercises. The submissions are not automatically moved from the old exercise keys to the new ones.
See https://github.com/apluslms/a-plus/issues/773

That would only be a problem if a-plus-rst-tools is updated while a course is already running which is unlikely. AFAIK only a single course actually has an "extra" directory. We could take the risk of forgoing the backward combatibility by just informing them that updating a-plus-rst-tools will break the exercises for the ongoing instance. Even if we don't take the risk, I would still rather have a flag to turn the auto detection on/off instead of having to specify the folder. That should save at least a little headache for course developers.

In case anyone comes across this while looking for a workaround or a solution before an official update, I'm posting my solution.
After trying out alternative methods, I found editing your sphinx-build options in your Makefile to be the most consistent and have the least issues. Changing the target directory of the build command and then adding the -c . option to point to the directory where conf.py is located works great!


Devservices

Refs: https://github.com/quarkiverse/quarkus-amazon-services/issues/253
I opt by lauching a separate container for each services in dev mode for now and it should be trivial to bring sharing support with ContainerLocator. In test mode, it groups as much as services it can in one container.
Latter, it could possible to add better sharing logic if needed.
@stuartwdouglas @gsmet What do you think about this design ? Should I continue that way ?

@scrocquesel let me know when this is ready. It needs a rebase.

@scrocquesel let me know when this is ready. It needs a rebase.

It misses the hot reload support (reuse same RunningDevServices). It is not as easy as I thought, the processor call providers to do the work and do not have access to the service config, so it's a bit tricky to check the conf do not change.

I changed the shared default value to false but I don't have strong opinion on this. Branch has been rebased.


Implement persistent storage of init data in the Arduino Proxy

Since safe state is not zero anymore, I think this probably is important, or at least figuring out what we need to do in that state.


Bug reported in the SpongeCommon issues

@Advancid: Um, what?

Closing because duplicate of SpongePowered/SpongeCommon#651


[zh] Fix typo

en PR https://github.com/kubernetes/website/pull/36566/files

Could you give us some insight about what's the value of this PR?


PD: Interact with and save batch edit Transfer form

User Story
As a PD user, I would like to be able to interact with the batch edit form and save my changes, so that changes are applied to the multiple steps I have selected.
Requirements

User is able to edit enabled fields
User is able to save changes.  Saved changes apply to all selected steps
Cancel - When cancel button is clicked, any unsaved changes to the form revert. No changes to the step selection and the form is still open.
Save - When enabled save button is clicked, (1) changes to the form are applied and (2) the save button becomes disabled because there are no new changes to the form.
Disabled Save Button - When changes are made to the form, the save button is enabled

Acceptance Criteria

"Gross list" considerations have been addressed
Requirements are met
Associated selectors for cancel (update after gross list consideration)

Test Steps (move to smartsheet)

Create a protocol with at least three transfer steps and various form states
Select multiple transfer steps to enter batch edit mode
Open up advanced settings
Check "pre-wet tip"
Check "Mix" in both aspirate and dispense and input acceptable values in the form fields
Hit Save
Validate that changes have been applied to all selected steps

Items here are included in tickets elsewhere. closing

Items here are included in tickets elsewhere. closing


Also support aws provider 3+

what
Set to use the latest version of dependencies and set to accept higher aws provider versions (3+)
why
the latest aws provider now is 3.14.1, for this module to stay relevant it need to start support 3+.
There might be a point in creating 2 separate branches/tracks in the future since some 3+ things are not compatible with some 2+ things and vice versa.. I do not now if this module includes any issues like that, but the included "complete" test is ok with using the latest 3.14.1 provider at least.
references
Direct links to the updated modules if curious what has changed in the versions (I didnt analyze just ran test and it worked
https://github.com/cloudposse/terraform-aws-vpc
https://github.com/cloudposse/terraform-aws-dynamic-subnets
https://github.com/cloudposse/terraform-aws-route53-cluster-hostname
Not for these particular changes Im doing a PR for now, but for reference what has changed between 2 and 3.
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-3-upgrade

And with tested, I mean I ran the example..

Rebased on master

/test all

@tomasbackman Thanks for the contribution! Released as 0.7.0.


protoc_plugin: use protoc like import statements

instead of generating import statements like:
import google.protobuf.empty_pb2

generate
from google.protobuf import empty_pb2 as google_dot_protobuf_dot_empty__pb2

like default protobuf python compiler.
It's convenient for modifing protobuf import path using protobuf-gen like tools.

Hi! Thanks for your contribution. I am going to merge this PR.


Add support for SKXamlCanvas on Uno Platform SkiaSharp backends

Description of Change
Add support for SKXamlCanvas on Uno Platform SkiaSharp backends, by using software rendering onto an off-screen surface.
While the SKSwapChainPanel is present (as it is part of the reference API shared with WebAssembly), it is currently not implemented.
In order to support this change, the SKXamlCanvas which was incorrectly inheriting from FrameworkElement, is now inheriting from Canvas, which exposes the Background property. It is a breaking change, but all the properties of FrameworkElement are also present on Canvas, which will not break existing code.
Note that non-breaking fixes are needed in Uno for this change to work properly (https://github.com/unoplatform/uno/pull/5266), those will be included as part of Uno 3.5.x and 3.6.
API Changes

Changed:

SKXamlCanvas : FrameworkElement -> SKXamlCanvas : Canvas

Behavioral Changes
None.
PR Checklist

[ ] Has tests (if omitted, state reason in description)
[x] Rebased on top of main at time of PR
[x] Changes adhere to coding standard
[x] Updated documentation

Looks like the rebuild passed most of the tests :) The rest is likely azure devops security from forks. @mattleibow Is there something I can help you with ?

Sorry about the incredibly delay, MAUI was a bit of beast :)
Is it possible to add a sample for the Skia backends? Only has to be a basic sample in say samples\Basic\Uno\SkiaSharpSample.Xxx? The WASM sample probably will be the easiest to copy for the targets and props - if they are needed.
I notice there is a targets file to set the UnoRuntimeEnabledPackage property. If one is needed (very likely if I understand), then just move it to the source\SkiaSharp.Views.Uno\SkiaSharp.Views.Uno folder and link both WASM and the skia backends to copy it. That way all the samples can get it instead of having to build a specific one.
Now that I got some time, I hope to merge this and release a preview.

@mattleibow do you know what the build errors are ? I'd guess it's fork-related authorizations :)

@mattleibow Is it possible to approve this pool request? our team are waiting for that!

Closing in favor of https://github.com/mono/SkiaSharp/pull/1704


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/eventing-writers
/assign knative-sandbox/eventing-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/pkg fe26417...38af013:
  > 38af013 Initialize prefix remapping map to avoid panic (# 2459)
  > 2fdd5f2 Update actions (# 2449)
  > 76a28b0 set git user name/email prior to merging upstream (# 2448)
bumping knative.dev/eventing f2045b0...9590bc3:
  > 9590bc3 adding min and max nodes annotation to rekt tests entrypoint (# 6243)
  > 4252411 Increase rekt test timings and reduce concurrency (# 6221)
  > 6fabdd5 Remove a second trigger of the autoscaler (# 6203)
  > 28a968c upgrade to latest dependencies (# 6230)
  > b349443 fixed links to source.md (# 6223)
  > f40fc74 Zero placements for rebalancing (# 6204)
  > 78aae1e Update community files (# 6220)
  > fdaca85 Update actions (# 6218)
  > 7ab1b0e upgrade to latest dependencies (# 6216)

/lgtm
/approve


JS native module

A very lazy way to interface with outside JavaScript to use N in a front end website or a Node/Deno backend would be to have a native module that can access JavaScript variables. To avoid runtime errors, the module may be very strict, verbose, and inconvenient to use, but libraries written in N can abstract it all away.
Of course, the Python implementation can't feasibly implement JavaScript, so
We can also have a similar module for accessing Python variables, but make a separate issue for that.
Behaviour
During runtime, the behaviour of the js module is implementation defined. 😱

For the JavaScript impl, it'll just do JavaScript things
The Python impl isn't expected to be able to match the JavaScript's impl, which is fine. All the types of the exports for this module are made to allow the Python impl to return err or none for everything. This means that an N project using the js module will still run in the Python impl, but all the results will just fail

Types
The exports here are intentionally minimal. If there's any missing functionality, they can be temporarily worked around using globalThis.eval. The names here are based on Reflect.
import js

// js.value is an exported enum type representing a JavaScript value

// Create JavaScript values
assert type js.string : str -> js.value
assert type js.number : float -> js.value
assert type js.boolean : bool -> js.value
assert type js.array : list[js.value] -> js.value
assert type js.object : map[str, js.value] -> js.value
// The first parameter is the `this` argument; the second is a list of arguments given to the function
assert type js.function : (js.value -> list[js.value] -> js.value) -> js.value

// Returns the JavaScript value for globalThis if available
assert type js.globalThis : cmd[option[js.value]]

// Most of these js methods will return a cmd resolving to a result containing a JavaScript value
alias jsResult = cmd[result[js.value, js.value]]

// Calls a function in JS, returning the return value
// Takes the this argument, a list of arguments, then the function value
assert type js.apply : js.value -> list[js.value] -> js.value -> jsResult

// Constructs a constructor, returning the new instance
// Takes a list of arguments then the class
assert type js.construct : list[js.value] -> js.value -> jsResult

// Gets a property from a object
// Takes the property name (a string for convenience, so this doesn't support symbols) then the object
assert type js.get : str -> js.value -> jsResult

// Sets a property of an object
// Takes the property name (no symbols), value, then the object. The result's ok value is ()
assert type js.set : str -> js.value -> js.value -> cmd[result[(), js.value]]

Example: This appends Hello world as a text node to . It does nothing if there was a failure on the way.
import js

let pub main = [] -> cmd[()] {
  if let <yes window> = js.globalThis! {
    if let <ok document> = js.get("document", window)! {
      if let <ok body> = js.get("body", document)! {
        if let <ok append> = js.get("append", body)! {
          // Ignore result
          let _ = js.apply(body, [js.string("Hello world.")], append)!
        }
      }
    }
  }
} |> ()

However, you can imagine that a library could abstract this away to
let { init } = imp "./modules/js-dom.n"

let pub main = [] -> cmd[()] {
  let { document } = if let <ok vars> = init! { vars } else { return () }
  document.body.appendString("Wow")!
}

where document is not a js.value but rather a special record created by a theoretical js-dom.n

This could also work in Node, so the following writes to a file:
import js

let pub main = [] -> cmd[()] {
  if let <yes global> = js.globalThis! {
    if let <ok require> = js.get("require", global)! {
      if let <ok fs> = js.apply(js.null, [js.string("fs")], require)! {
        if let <ok writeFile> = js.get("writeFile", fs)! {
          let _ = js.apply(fs, [
            js.string("hi.txt"),
            js.string("hello"),
            js.function([this:js.value arguments:list[js.value]] -> cmd[js.value] {
              return js.undefined
            }),
          ], writeFile)!
        }
      }
    }
  }
} |> ()


steamtinkerlaunch: 12.12 -> 12.12-unstable-2024-05-03

Description of changes
Upstream didn't tag a release for some time and 12.12 doesn't have a workaround for running MO2, as the latest version is broken on wine.
Also worth noting that upstream actually recommends running the latest git commit instead of releases. -> https://github.com/sonic2kk/steamtinkerlaunch/issues/1018#issuecomment-1893036240

And spread the word for people to STOP using STL v12.12. It really annoys me 😓 Even when v14.0 comes out, if people stick to using it I will lose a lot of hope for this project. There is zero reason to use a "stable" version of a Bash script...

so yeah, let's just switch to the latest commit. Tested it with Cyberpunk 2077 from Steam and it seems to be working fine, including MO2.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Could you check if it fixes #309510?

@Aleksanaa it doesn't. steamtinkerlaunch requires FHS environment to function properly so eg. in Steam.


Add Sprite Fusion, a free, web-based 2D tilemap editor

Why do you think the link is worth adding on this list?
Sprite Fusion is 100% free, run in any modern browser and allow users to export their 2D tilemaps to native Unity packages and Godot Maps.
Does this project has any License?
No

hey @Hugo-Dz can you keep the list alphabetically sorted please?

hey @Hugo-Dz can you keep the list alphabetically sorted please?

Done!


Revert "Python: use 'ProtoFiles.getProtoFiles' to sort enums by filename."

Reverts googleapis/gapic-generator#2418
See: #2429.

Codecov Report

Merging #2442 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #2442      +/-   ##
============================================
- Coverage     86.44%   86.44%   -0.01%
+ Complexity     5278     5277       -1
============================================
  Files           458      458
  Lines         21047    21046       -1
  Branches       2286     2286
============================================
- Hits          18194    18193       -1
  Misses         2036     2036
  Partials        817      817

Impacted Files
Coverage Δ
Complexity Δ

.../transformer/py/PythonGapicSurfaceTransformer.java
98.29% <100%> (-0.01%)
43 <0> (-1)

Continue to review full report at Codecov.

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

Are able to use this change in a local fork of gapic-generator to generate the desired Bigtable's python client?

@andreamlin

Are able to use this change in a local fork of gapic-generator to generate the desired Bigtable's python client?

I don't have enough knowledge of the toolchain to figure that out:  I'm just backing the change out because the bug appeared to occur after the change from #2418 was propagated to the artman image.

@andreamlin Should I close this PR, given your change in #2440?

@tseaver right now i'll generate the python client with and without my change, and see if it the fix fixes this

Verified locally that without this PR (the reverting PR), the StorageType class (from the linked bigtable synth PR) is not generated in the Python client, and with this PR, artman will generate the StorageType class. Therefore, we should check in this PR.
Thanks a lot for opening this reverting PR!


[BUG]

Hello. I have confused with this situation.
Lets have this generic function
import { Response, Request, NextFunction } from "express"

export function endpoint<Body = {}, Params = {}, Query = {}>(
	...fns: ((
		req: Request<Params, any, Body, Query>,
		res: Response,
		next: NextFunction
	) => Promise<any> | any)[]
) {
	const f = fns.pop()!
	const middlewares = fns
	return [
		...middlewares,
		async (
			req: Request<Params, any, Body, Query>,
			res: Response,
			next: NextFunction
		) => {
			try {
				let [body, bodyValidationErrors] = check<Infer<Body>>(req.body)
				if (bodyValidationErrors.length)
					throw new Error(bodyValidationErrors.join(", "))
				await f(req, res, next)
			} catch (e: unknown) {
				next(e)
			}
		},
	]
}

This is how i want use it
/routes/content/[gameId].ts
export const get = endpoint<{}>(authorizedOnly, async (req, res) => {
	res.json(req.params)
})

export const post = endpoint<{ saveDate: string; data: string }>(
	authorizedOnly,
	async (req, res) => {
		res.json(req.params)
	}
)

I expect the post function call will not work without body {saveDate,data} but it works because of in get function body can be empty and after transpilation all validation code is merged it one function endpoint
Is it possible to isolate types for each separate function?

Sadly no, this is currently impossible to do. You can use the Resolve type, but that will return a single error instead of all of them like how it is currently in your code.
I think I'll be adding something that fixes this soon, though!


Error Response payload is not complete

Issue you'd like to raise.
I am using pusher for streaming purpose.
I am getting error as "Response payload is not completed"
async def pusher__cal(new_payload, token):
print(token)
session_id = new_payload["session_id"]
session_id_channel = f"{session_id}_channel"
user_id = new_payload["user_id"]
message_id = new_payload["message_id"]
status = "processing"
await asyncio.sleep(0)  # Allow other async tasks to run
pusher_client.trigger(session_id_channel ,'query_answer_stream', {
"user_id": user_id,
"session_id": session_id,
"message_id": message_id,
"answer": token,
"status": status
},
)
class MyCallbackHandler(AsyncCallbackHandler):
def init(self,new_payload : Dict):
self.new_payload = new_payload
self.user_id = new_payload["user_id"]
self.session_id = new_payload["session_id"]
self.message_id = new_payload["message_id"]
self.session_id_channel = f"{self.session_id}_channel"
self.status = "streaming"
self.list = []
async def on_llm_new_token(self, token, **kwargs) -> None:
if token != "":
    await pusher__cal(self.new_payload,token)

Suggestion:
No response

@Ajaypawar02 Did you fix this? I'm running into the same, and it's causing retries.

https://github.com/openai/openai-python/issues/574


PlenarioETLError: Missing data for column

The Chicago crimes dataset (admin access required) keeps failing update because of a missing data error, for a non-essential field (community area). We may want to have it issue a warning instead, or a silent error, and continue with the update if a non-essential field is missing.

I'm gonna move discussion for this into #184


bug(compiler): diagnostics not linking the code properly

Describe the bug

$ sozo build

warn[E0001]: Unused variable. Consider ignoring by prefixing with `_`.
 --> /path/to/dojo/examples/spawn-and-move/src/actions.cairo:16:1
#[dojo::contract]
^***************^

To Reproduce
simply add a unused variable in the code and build
Expected behavior
should point to the correct line where issue occured.

its working as expected until 0.7.0-alpha.3 and i am seeing this behaviour from 0.7.0-alpha.4 onwards.

did a git bisect on it and the first commit that has the issue is e6146516d91fe5e91dc6ca1259b8699e40828e40

did a git bisect on it and the first commit that has the issue is e6146516d91fe5e91dc6ca1259b8699e40828e40

And to complete this, it is only happening on the #[dojo::contract] attribute. Others like #[dojo::model], #[dojo::interface] and #[dojo::event] are working as expected.

Seems like it is the case with all attributes. It is being investigated by Scarb team.

Closed in #2141.


feat: Central ansible execution host support

Description

Support RHEL 9.2 and SLES 15 SP5
Use **sap_swpm** role from linux system role instead of community role

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[x] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
v2.0.0

Your semantic-release bot :package::rocket:


Android build are failing (elfutils problem again?)

Seems like Android builds started failing again. I'd appreciate someone with access to Android to take a look.
See https://github.com/libbpf/libbpf-bootstrap/actions/runs/10999328127 for failure details.
cc @waruqi

I will look at it in these days.

try it again. https://github.com/xmake-io/xmake-repo/pull/5335

@waruqi seems to be working fine now, thanks a lot for the fix!


failing to upload report to codecov

/dev/fd/63: line 1: html: No such file or directory
/dev/fd/63: line 2: syntax error near unexpected token `<'

By looking at https://github.com/codecov/codecov-bash/issues/59, I suspect this is a codecov issue since nothing has changed on our side.
Source: https://circleci.com/gh/getfider/fider/5068

https://codecov.io/bash returns 503 error page, which starts with <html> obviously.

I am also having the same issue this morning.
I can also confirm that the server is done with a 503.
Just a strange error message. 😅
/dev/fd/63: line 2: syntax error near unexpected token <' /dev/fd/63: line 2: '

Apologies, we are rolling out a fix. You can view the status report here


e5s trigger fixes

show "enrage soon" not "grab an orb" on last cast of Fury's Fourteen.
undefined returns false, so I fixed it to work fine.

Thanks!


Cypress/E2E: Fixed archived channel name

Summary

Renamed archived channel so it appears on top

Note: Cypress run passed
Ticket Link
None -  master only

@prapti Gentle ping


The country in not visible in shipping and billing address

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
Master
Issue Description
if the admin and customer are trying to view the invoice then The country is not visible in the shipping and billing address section.
Preconditions
1 order should be created by the admin.
The billing and shipping address should be selected by the customer while creating the order.
Steps to reproduce
1. Go to the shop
2. Create an order.
3. Select the billing and shipping address.
4. Go to the admin panel
5. Create shipping and invoice for the order.
6. Try to view the country in the billing/shipping address.
7. See an error
Expected Result
The country should be visible in the invoice that they selected while creating the order.
Actual Result
The country is not visible in the voice in the billing and shipping address section.
Screenshots

Additional context
No response

Didn't notice the error

Didn't notice the error

Hi there,
Which version of bagisto are you using?

@jitendra-webkul
Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.


Swarm: Fix to remove context_variables in messages

Why are these changes needed?
Bassil on discord discovered that context_variables are in the chat history.
The context_variables were being added to the messages for execution, but were not being removed again after execution.
This removes them.
Related issue number
N/A
Checks

[ ] I've included any doc changes needed for https://ag2ai.github.io/ag2/. See https://ag2ai.github.io/ag2/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[X] I've made sure all auto checks have passed.

OK as a hotfix. A better approach is to copy the message and not to modify the original message history here. Modifying the message history may have side effect in the tool execution.

Thanks for the note - I've tidied up the code and changed to a deep copy to not affect the original message history.

Nice work! Tested it with several use cases, working perfectly on my end.

Thanks for testing @bassilkhilo, I've tidied up the code a bit and changed to a deep copy, can you test again please :)

All tests passed, except an OpenAI test that triggered the Azure content filter due to content. Merging.


Added new BackgroundAnimations (Flip, SlideFromLeft, etc.)

Added the following transitions to BackgroundAnimation:

Flip
SlideFromLeft
SlideFromRight
SlideFromTop
SlideFromBottom

Example:

@jsuarezruiz thanks for your contributions!
I'm trying this pull request, i'll merge it in a couple of hour or tomorrow.

Awesome!


documentation steps on Parsing and serializing JSON comes with error

I try to follow these steps from Parsing and serializing JSON and I got error about ajv .
The version of Ajv you are using
6 I install with
Operating system and node.js version
Node.js v18.13.0.
Package manager and its version
npm -v
9.6.2
Link to (or contents of) package.json
{
"name": "ajv001",
"version": "1.0.0",
"description": "simple test with ajv and json ",
"main": "index.js",
"scripts": {
"test": "echo "Error: no test specified" && exit 1",
"dev": "node index.js"
},
"keywords": [
"catafest",
"json",
"ajv",
"nodejs"
],
"author": "catafest",
"license": "ISC",
"dependencies": {
"ajv": "^6.12.6"
},
"type": "module"
}
Error messages
node:internal/errors:491
ErrorCaptureStackTrace(err);
^
Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'F:\ajv001\node_modules\ajv\dist\jtd' imported from F:\ajv001\index.js
at new NodeError (node:internal/errors:400:5)
at finalizeResolution (node:internal/modules/esm/resolve:326:11)
at moduleResolve (node:internal/modules/esm/resolve:945:10)
at defaultResolve (node:internal/modules/esm/resolve:1153:11)
at nextResolve (node:internal/modules/esm/loader:163:28)
at ESMLoader.resolve (node:internal/modules/esm/loader:842:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
at ModuleWrap. (node:internal/modules/esm/module_job:77:40)
at link (node:internal/modules/esm/module_job:76:36) {
code: 'ERR_MODULE_NOT_FOUND'
}
Node.js v18.13.0
The output of npm ls

npm ls
<EMAIL_ADDRESS>F:\ajv001
└──<EMAIL_ADDRESS>

Doesn't seem to be a problem anymore in 8.17.1


If I add rule, previous rule that has default backend resets to .xip.io option

Rancher versions: 2.0 master 4/30
Steps to Reproduce:

Go to Add Ingress
In the first rule click on Use as the default backend radio option
Click on Add Rule

Results:  The radio option for the first rule reset to first option instead of staying on default backend option.

Version - 2.0 master 5/8
Verified fixed


Ensure the paths in site.yaml are under the root

Absolute paths, or relative paths that are outside the root of the site will not work with docker. They should be checked and a suitable error should be shown.

This is not technically a bug, but could certainly lead to users getting confused.


Hexadecimal base int

Added test relative to past error #194

LGTM, thanks! Can you keep only the last commit in this PR so we can handle the warnings separately?

Done 👍


⚠ gorzdrav.org has degraded performance

In 1e03d44, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 2197 ms

Resolved: gorzdrav.org performance has improved in 3f9b223 after 5 minutes.


Error getting to run an example

Hello,
I freshly created a conda environment, and install pinocchio, and I wanted to run this example: examples/cassie-simulation.py
However, I'm getting this error:
Traceback (most recent call last):
  File "/home/emrecemal/git_ws/check_cassie/main.py", line 30, in <module>
    robot = pinocchio.RobotWrapper.BuildFromSDF(
  File "/home/emrecemal/git_ws/check_cassie/.venv/lib/python3.10/site-packages/pinocchio/robot_wrapper.py", line 53, in BuildFromSDF
    robot.initFromSDF(
  File "/home/emrecemal/git_ws/check_cassie/.venv/lib/python3.10/site-packages/pinocchio/robot_wrapper.py", line 74, in initFromSDF
    model, constraint_models, collision_model, visual_model = buildModelsFromSdf(
  File "/home/emrecemal/git_ws/check_cassie/.venv/lib/python3.10/site-packages/pinocchio/shortcuts.py", line 113, in buildModelsFromSdf
    model, constraint_models = pin.buildModelFromSdf(
AttributeError: module 'pinocchio.pinocchio_pywrap_default' has no attribute 'buildModelFromSdf'. Did you mean: 'buildModelFromUrdf'?

How can I solve it?

Hello,
If you want Sdf support, you need to compile pinocchio from source, because it's not included in the conda package.

Hello @emrecemal,
Since Pinocchio 3.3.0, the conda package is build with SDF support.


Reland filesystem options support with fix for Windows test.

Submitting TBR as this has only small incremental fix over https://github.com/flutter/flutter/pull/15622.


Fixed Kafka disconnection issue

Signed-off-by: Francesco Guardiani<EMAIL_ADDRESS>Fixes #999

Proposed Changes

Wrapped Consume method invocation in a loop, like explained in the example here: https://godoc.org/github.com/Shopify/sarama#ConsumerGroup

@slinkydeveloper looks like this change (as-is) causes a data race?

@slinkydeveloper looks like this change (as-is) causes a data race?

Yep i'm investigating, doesn't seem a funny one

/retest

Thanks a lot guys! That will really help as otherwise the solution was not reliable enough to work with. :-)


Register valid_numeric as a filter

It is useful to have a function which can typecast an str to a numeric value.

Coverage remained the same at 62.366% when pulling 512ca57609f424bf8394b31d6bc6c3a1e8f60326 on ShipraShalini:master into 7f22f98e906d46bee487ce2d78fb995f74c1d568 on dbrgn:master.

Can you list a few use cases where this would be useful?
I'm a bit sceptical, especially since type casting is out of scope for a filter library providing simple math operations.


Sec-WebSocket-Protocol support

When I use JavaScript to connect, an error occurs when I specify Sec-WebSocket-Protocol, but it works fine with Java and Android clients.
Code:
new WebSocket(url, token)

Error:
Error in websocket connection: Unexpected EOF

I'm using the code from the example:
https://github.com/denoland/fastwebsockets/blob/main/examples/echo_server.rs

Already solved, just append Sec-WebSocket-Protocol to the response


Azure Cosmos DB Emulator - Release notes and download information; missing release notes for latest 2.14.9

Azure Cosmos DB Emulator - Release notes and download information; missing release notes for latest 2.14.7
Latest Microsoft Download Center https://aka.ms/cosmosdb-emulator (as of 2022-07-19) (Signed 2022-07-07 13:31:00Z)
{
"PackageName":  "azure-cosmosdb-emulator-2.14.9-3c8bff92.msi",
"Manufacturer":  "Microsoft® Corporation",
"ProductName":  "Azure Cosmos DB Emulator",
"ProductVersion":  "2.14.9",
"ProductLanguage":  "1033",
"ProductCode":  "{00E2415B-C8F1-4368-ABA6-FB65EF588CB4}"
}

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

ID: 1300a10b-16f3-9185-af2a-67437bf428d2
Version Independent ID: 07fd7c5a-0ad5-a7b4-21ef-768f183076aa
Content: Azure Cosmos DB Emulator download and release notes
Content Source: articles/cosmos-db/local-emulator-release-notes.md
Service: cosmos-db
GitHub Login: @milismsft
Microsoft Alias: adrianmi

@aluty Thank you for the feedback. This is being assigned to the content author to evaluate and update as appropriate.

@milismsft, do you have any release notes for 2.14.9?

Hello @aluty!
#assign:seesharprun
We are updating the doc now with new release notes. The last two versions were mostly maintenance releases to align the emulator with the latest state of Azure Cosmos DB.

The following users don't have valid GitHub IDs, or are not collaborators on this repo: un
we are updati

#assign:seesharprun


Stocks App in the examples throws errors with --preview-dart-2

Running the stocks app in the examples throws the following runtime errors when using --preview-dart-2. The app is fine when not using the preview.
E/flutter (  668): [ERROR:topaz/lib/tonic/logging/dart_error.cc(16)] Unhandled exception:
E/flutter (  668): type 'List' is not a subtype of type 'List<List<String>>' where
E/flutter (  668):   List is from dart:core
E/flutter (  668):   List is from dart:core
E/flutter (  668):   List is from dart:core
E/flutter (  668):   String is from dart:core
E/flutter (  668):
E/flutter (  668): #0      StockData._fetchNextChunk.<anonymous closure> (file:///Volumes/Mojo/flutter/examples/stocks/lib/stock_data.dart:89:19)
E/flutter (  668): #1      _RootZone.runUnary (dart:async/zone.dart:1381:54)
E/flutter (  668): #2      _FutureListener.handleValue (dart:async/future_impl.dart:129:18)
E/flutter (  668): #3      _Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:633:45)
E/flutter (  668): #4      _Future._propagateToListeners (dart:async/future_impl.dart:662:32)
E/flutter (  668): #5      _Future._completeWithValue (dart:async/future_impl.dart:477:5)
E/flutter (  668): #6      _Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:507:7)
E/flutter (  668): #7      _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
E/flutter (  668): #8      _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)

I think this is fixed by @chinmaygarde


How to get a String from complete Body

How can we get a String out of:
       res.body().map_err(|_| ()).fold(vec![], |mut acc, chunk| {
          acc.extend_from_slice(&chunk);
          Ok(acc)
        });

Trying to do:
       println!("Body: \n{}", res.body());

let body = res.body().map_err(|_| ()).fold(vec![], |mut acc, chunk| {
    acc.extend_from_slice(&chunk);
    Ok(acc)
}).and_then(|v| String::from_utf8(v).map_err(|_| ()));
println!("Body: \n{}", body.wait().unwrap());

Well, with the above being said, you could ask stuff like that on Stack Overflow or some such.

As suggested, you just needed to use String::from_utf8(vec) to convert the folded vector into a String.

Got it, thanks

Getting:
233 |               req.body().map_err(|_| ()).fold(vec![], |mut acc, chunk| {
    |               ^^^^^^^^^^ cannot move out of borrowed content

You need to use req.into_body() instead of req.body() in newer versions of Hyper.

Now it just logs the string "Body" when I println!, don't see the body content.

Now, how to write?


make run-all-tests (in dash-pipeline) fails

make run-all-tests (in dash-pipeline) fails with the following error.  I cloned a fresh version and followed the instructions.  Essentially running (successfully) make all && make run-switch in one window and make run-saithrift-server in another window.  When attempting to run make run-all-tests in another window, I get the following error.  I have not modified any code - only followed the instructions in the readme.
GRPC call SetForwardingPipelineConfig <IP_ADDRESS>:9559 => /etc/dash/dash_pipeline.json, /etc/dash/dash_pipeline_p4rt.txt
GRPC ERROR[7]: Not primary, GRPC call Write::INSERT ERROR:
table_id: 41103078 match { field_id: 1 exact { value: "<\000\000" } } action { action { action_id: 21912829 } }Failed to create Direction Lookup Entry
make: *** [Makefile:253: run-libsai-test] Error 1

Update: I re-ran the make command and it succeeded.

Hi @mhanif I suspect you have more than one instance of a P4Runtime client running. This is the clue:
GRPC ERROR[7]: Not primary

Please perform "docker ps" and see if there's another client running.

@mhanif Can we close this? It seems like a transient. With the many recent improvements to the build process, there's a good chance the environment is sufficiently different such as to make this issue somewhat stale. Thanks.

@chrispsommers Yes, we can close this.  Thanks a lot for helping improve the build process.  I will close this issue.


Adding backwards compatibility test for ml-commons plugin

Signed-off-by: Sicheng Song<EMAIL_ADDRESS>Description
This PR should add backwards compatibility test for our ml-commons plugin in order to test the backwards compatibility of the latest minor version of the previous major version of our plugin.
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #681 (219d5fe) into 2.x (04d6864) will decrease coverage by 0.38%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                2.x     #681      +/-   ##
============================================
- Coverage     84.18%   83.79%   -0.39%
+ Complexity     1010     1004       -6
============================================
  Files            93       93
  Lines          3660     3660
  Branches        342      342
============================================
- Hits           3081     3067      -14
- Misses          435      448      +13
- Partials        144      145       +1

Flag
Coverage Δ

ml-commons
83.79% <ø> (-0.39%)
:arrow_down:

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

Impacted Files
Coverage Δ

.../cluster/MLCommonsClusterManagerEventListener.java
65.62% <0.00%> (-12.50%)
:arrow_down:

...va/org/opensearch/ml/task/MLExecuteTaskRunner.java
76.66% <0.00%> (-6.67%)
:arrow_down:

...ain/java/org/opensearch/ml/task/MLTaskManager.java
61.92% <0.00%> (-4.07%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I think we should add Github workflow file like AD https://github.com/opensearch-project/anomaly-detection/blob/main/.github/workflows/test_bwc.yml. So for any PR or code push, it will trigger bwc test automatically.


New IIO C-API to read configuration attributes V2

including 3 C-API to read scale, offset and sampling_frequency attribute
Signed-off-by: guchaojie<EMAIL_ADDRESS>

@ceolin @edersondisouza @fulong82 @laykuanloon This PR is for issue #2117. All thie C-API is to get configuration attribute from device level.

@ceolin Do you have any comments on new PR?  Thanks.

patch is ok, please rebase with upstream and fix these small issues that will be ready to be merged.


Verbose output

I've been using sauce-tunnel and it's been very helpful, however I can't seem to figure out how to print verbose output about the sauce tunnel (not just the sauce lab's selenium servers). The extraArgs array with the flag "--verbose" is for the selenium servers, but I want to see the line by line output from the Sauce Tunnel application. I'm not sure if I'm missing something, but I read through the READMe and still can't figure this out.

Each SauceTunnel instance is an EventEmitter, so you can listen to events that it emits with data, such as is done here in the test file. Is that the sort of thing you were looking for?

@willchen90 Did that answer your question?


fix: completion help info first letters lowercase

Summary
Description
All of subcommands' help information  are starting with uppercase letters, except for completion. cobra 1.3.0 has resolved this issue. I do not know why the version is not automatically updated, so manually update to the latest version 1.4.0.
Related Issues
N/A
Current Behavior
  completion  generate the autocompletion script for the specified shell

New Behavior
  completion  Generate the autocompletion script for the specified shell

Screenshots
N/A
Other Information
N/A

/cc @IronCore864 I've test this pr locally, it works fine. I'd like to merge it quickly.

@imxw Good job!


[red-knot] type inference/checking test framework

Summary
Adds a markdown-based test framework for writing tests of type inference and type checking. Fixes #11664.
Implements the basic required features. A markdown test file is a suite of tests, each test can contain one or more Python files, with optionally specified path/name. The test writes all files to an in-memory file system, runs red-knot, and matches the resulting diagnostics against Type:  and Error:  assertions embedded in the Python source as comments.
We will want to add features like incremental tests, setting custom configuration for tests, writing non-Python files, testing syntax errors, capturing full diagnostic output, etc. There's also plenty of room for improved UX (colored output?).
This is a large PR, but I split the commits carefully for easier review. I'm preferring this over stacked PRs, since the GH UX for stacked PRs is so bad. I encourage reviewers to use the GH feature to narrow review per-commit, for less daunting review.
Test Plan
Lots of tests!
Sample of the current output when a test fails:
     Running tests/inference.rs (target/debug/deps/inference-7c96590aa84de2a4)

running 1 test
test inference::path_1_resources_inference_numbers_md ... FAILED

failures:

---- inference::path_1_resources_inference_numbers_md stdout ----
inference/numbers.md - Numbers - Floats
  /src/test.py
    line 2: unexpected error: [invalid-assignment] "Object of type `Literal["str"]` is not assignable to `int`"

thread 'inference::path_1_resources_inference_numbers_md' panicked at crates/red_knot_test/src/lib.rs:60:5:
Some tests failed.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    inference::path_1_resources_inference_numbers_md

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.19s

error: test failed, to rerun pass `-p red_knot_test --test inference`

I haven't made it through quite all the comments yet, but you're welcome to review the additional commits I've made so far. I haven't modified the initial commits (other than to rebase on main, which was a clean rebase), just added new ones for various review comments. So you should be able to just review the new commits rather than re-reviewing everything.

Ok, now I think all comments are addressed!

Thanks for all the great review comments! Planning to merge once signal is green.


 Calling it on smaller grammars is not that slow, but still far from ideal.

Has been fixed a long time ago.


Flow failed due to missing dependency not referred

I follow instruction and write big sum example. I use python:latest base image and this image doesn't have numpy library. I update to use @conda decorator at the start step. The problem is error occurs in the end step but it doesn't have any reference on numpy.
python3 bigsum.py --environment=conda run
Metaflow 2.0.1 executing BigSum for user:shjiaxin
Validating your flow...
    The graph looks good!
Running pylint...
    Pylint not found, so extra checks are disabled.
2019-12-27 14:56:26.136 Bootstrapping conda environment...(this could take a few minutes)
2019-12-27 14:56:28.141 Workflow starting (run-id 69):
2019-12-27 14:56:28.819 [69/start/254 (pid 35570)] Task is starting.
2019-12-27 14:56:32.973 [69/start/254 (pid 35570)] Task finished successfully.
2019-12-27 14:56:34.065 [69/end/255 (pid 35595)] Task is starting.
2019-12-27 14:56:36.110 [69/end/255 (pid 35595)] <flow BigSum step end> failed:
2019-12-27 14:56:36.114 [69/end/255 (pid 35595)] Internal error
2019-12-27 14:56:36.115 [69/end/255 (pid 35595)] Traceback (most recent call last):
2019-12-27 14:56:36.115 [69/end/255 (pid 35595)] File "/tmp/tmppku_v65f/metaflow/cli.py", line 853, in main
2019-12-27 14:56:36.115 [69/end/255 (pid 35595)] start(auto_envvar_prefix='METAFLOW', obj=state)
2019-12-27 14:56:36.115 [69/end/255 (pid 35595)] File "/Users/shjiaxin/miniconda/envs/metaflow_BigSum_osx-64_3d3fb5f54327676ef9bf2dfb5b4d0a3b8244dc31/lib/python3.7/site-packages/click/core.py", line 764, in __call__
2019-12-27 14:56:36.115 [69/end/255 (pid 35595)] return self.main(args, kwargs)
2019-12-27 14:56:36.116 [69/end/255 (pid 35595)] File "/Users/shjiaxin/miniconda/envs/metaflow_BigSum_osx-64_3d3fb5f54327676ef9bf2dfb5b4d0a3b8244dc31/lib/python3.7/site-packages/click/core.py", line 717, in main
2019-12-27 14:56:36.116 [69/end/255 (pid 35595)] rv = self.invoke(ctx)
2019-12-27 14:56:36.116 [69/end/255 (pid 35595)] File "/Users/shjiaxin/miniconda/envs/metaflow_BigSum_osx-64_3d3fb5f54327676ef9bf2dfb5b4d0a3b8244dc31/lib/python3.7/site-packages/click/core.py", line 1137, in invoke
2019-12-27 14:56:36.116 [69/end/255 (pid 35595)] return _process_result(sub_ctx.command.invoke(sub_ctx))
2019-12-27 14:56:36.116 [69/end/255 (pid 35595)] File "/Users/shjiaxin/miniconda/envs/metaflow_BigSum_osx-64_3d3fb5f54327676ef9bf2dfb5b4d0a3b8244dc31/lib/python3.7/site-packages/click/core.py", line 956, in invoke
2019-12-27 14:56:36.116 [69/end/255 (pid 35595)] return ctx.invoke(self.callback, ctx.params)
2019-12-27 14:56:36.116 [69/end/255 (pid 35595)] File "/Users/shjiaxin/miniconda/envs/metaflow_BigSum_osx-64_3d3fb5f54327676ef9bf2dfb5b4d0a3b8244dc31/lib/python3.7/site-packages/click/core.py", line 555, in invoke
2019-12-27 14:56:36.117 [69/end/255 (pid 35595)] return callback(args, kwargs)
2019-12-27 14:56:36.117 [69/end/255 (pid 35595)] File "/Users/shjiaxin/miniconda/envs/metaflow_BigSum_osx-64_3d3fb5f54327676ef9bf2dfb5b4d0a3b8244dc31/lib/python3.7/site-packages/click/decorators.py", line 27, in new_func
2019-12-27 14:56:36.117 [69/end/255 (pid 35595)] return f(get_current_context().obj, args, kwargs)
2019-12-27 14:56:36.188 [69/end/255 (pid 35595)] File "/tmp/tmppku_v65f/metaflow/cli.py", line 430, in step
2019-12-27 14:56:36.190 [69/end/255 (pid 35595)] max_user_code_retries)
2019-12-27 14:56:36.191 [69/end/255 (pid 35595)] File "/tmp/tmppku_v65f/metaflow/task.py", line 390, in run_step
2019-12-27 14:56:36.191 [69/end/255 (pid 35595)] self._exec_step_function(step_func)
2019-12-27 14:56:36.191 [69/end/255 (pid 35595)] File "/tmp/tmppku_v65f/metaflow/task.py", line 47, in _exec_step_function
2019-12-27 14:56:36.191 [69/end/255 (pid 35595)] step_function()
2019-12-27 14:56:36.191 [69/end/255 (pid 35595)] File "bigsum.py", line 21, in end
2019-12-27 14:56:36.191 [69/end/255 (pid 35595)] print("The sum is %f." % self.sum)
2019-12-27 14:56:36.191 [69/end/255 (pid 35595)] File "/tmp/tmppku_v65f/metaflow/flowspec.py", line 122, in __getattr__
2019-12-27 14:56:36.191 [69/end/255 (pid 35595)] x = self._datastore[name]
2019-12-27 14:56:36.191 [69/end/255 (pid 35595)] File "/tmp/tmppku_v65f/metaflow/datastore/datastore.py", line 571, in __getitem__
2019-12-27 14:56:36.192 [69/end/255 (pid 35595)] return self._load_object(self.objects[var])
2019-12-27 14:56:36.192 [69/end/255 (pid 35595)] File "/tmp/tmppku_v65f/metaflow/datastore/datastore.py", line 453, in _load_object
2019-12-27 14:56:36.192 [69/end/255 (pid 35595)] return pickle.loads(blob)
2019-12-27 14:56:36.192 [69/end/255 (pid 35595)] ModuleNotFoundError: No module named 'numpy'
2019-12-27 14:56:36.192 [69/end/255 (pid 35595)]
2019-12-27 14:56:36.484 [69/end/255 (pid 35595)] Task failed.
2019-12-27 14:56:36.484 Workflow failed.
2019-12-27 14:56:36.484 Terminating 0 active tasks...
2019-12-27 14:56:36.484 Flushing logs...
    Step failure:
    Step end (task-id 255) failed.

metaflow code
from metaflow import FlowSpec, step, resources, batch, conda

class BigSum(FlowSpec):

    @resources(memory=4500, cpu=1)
    @batch
    @conda(libraries={'numpy':'1.17.3'})
    @step
    def start(self):
        import numpy
        import time
        big_matrix = numpy.random.ranf((10000, 10000))
        t = time.time()
        self.sum = numpy.sum(big_matrix)
        self.took = time.time() - t
        self.next(self.end)

    @batch
    @step
    def end(self):
        print("The sum is %f." % self.sum)
        print("Computing it took %dms." % (self.took * 1000))

if __name__ == '__main__':
    BigSum()

self.sum has a dependency on numpy since it can be an ndarray. A quick check would be to comment out the first print statement in the end step and reexecute.


bindCallback incomplete example in docs app

Documentation Related To Component:
bindCallback
Please check those that apply

[ ] typo
[ ] documentation doesn't exist
[x] documentation needs clarification
[x] error(s) in example
[ ] needs example

Description Of The Issue
For example Receive an array of arguments passed to a callback to work  someFunction callback needs to be called at the end at least once.
So the full correct example IMO should be:
import { bindCallback } from 'rxjs';

const someFunction = (a, b, c) => {
  console.log(a); // 5
  console.log(b); // 'some string'
  console.log(c); // {someProperty: 'someValue'}
};

const boundSomeFunction = bindCallback(someFunction);
boundSomeFunction().subscribe(values => {
  console.log(values) // [5, 'some string', {someProperty: 'someValue'}]
});

someFunction(5, 'some string', {someProperty: 'someValue'}); // --> missing line

That particular example seems incorrect, to me. someFunction doesn't even take a callback, so I don't see how it can be used with bindCallback. IMO, the example should be removed.

Interesting enough @cartant, the above example logs the expected values. Then, maybe the example does not depicts the correct usage of bindCallback, or?

Well, it'll log it because the function is called, but there is no callback, so it's pointless and not a good example.

Ah true, then it's pointless. I agree you should just remove it.


Remove customize does not work as expected (remove cutomizer link wont work in intervention 2)

As far as I understand it, one can remove the customizer link by using something like this (roots/bedrock, intervention 2 (master), sage 10 via config/intervention.php, Wordpress 5.6.1):
config/intervention.php
<?php

return [
    'wp-admin.all' => [
        'appearance.customize',
    ],
];

although, this disables the customizer functionality, it does not remove the customizer menu link.
If that is the expected behavior we should update the corresponding readme.md file. if not there might be a bug.
At least the removal of the parent menu works as expected, so I consider my understanding of the mechanism as correct (?) - the following works for me and removes the 'design' (= appearance) menu item completely:
<?php

return [
    'wp-admin.all' => [
        'appearance',
    ],
];

How can I remove the customizer link entirely?
the "plain" vairant without using intervention could look like this example:
add_action( 'admin_menu', function () {
    global $submenu;

    if ( isset( $submenu[ 'themes.php' ] ) ) {
        foreach ( $submenu[ 'themes.php' ] as $index => $menuItem ) {
            if ( in_array( 'customize', $menuItem ) ) {
                unset( $submenu[ 'themes.php' ][ $index ] );
            }
        }
    }
});

Hi @emanueljacob ,
Thanks for reporting. You're correct in your thinking that appearance.customize should remove the submenu item. WordPress throws in a ?return= for the customizer page so I have created a fix to account for that. I have pushed a fix onto dev-master which should resolve, [4189186].(https://github.com/soberwp/intervention/commit/4189186daaebd14e26a2a5cc20d3442bfd92112d)
Please let me know if that works now.

@darrenjacoby
Thank you for your awesomely fast reply! Yes, your changes seems to fix it.
btw: I was confused, seeing composer not updating the master, even after composer clear-cache until I realized that the master is not yet published to packagist in its latest state... when are you usually push the master to packagist (didn't see any automatic action for that)? is there an eta for a stable version 2.0.0, yet?

No problem!
Ah, that's painful, I see I had to re-allow Packagist access to this organisation on GH. Not sure why that had changed, but updates should be syncing again now.
There's still two changes I want to make before tagging a stable 2.0.0, namely renaming application.site to application.general to match the WordPress UI, and address https://github.com/soberwp/intervention/issues/55
I should be able to wrap those changes possibly as soon as next week, no later than early to mid March I imagine.


Add circle CI to build the binary and have artifact to test

We need to have a CI which at least build and have artifact to test for PRs

Done in https://github.com/code-ready/machine-driver-libvirt/pull/8


chore: Fix error returned when resolving nodePool from nodeClaim (utils)

Fixes #N/A
Description
Taking in the change that was suggested in a previous PR - https://github.com/aws/karpenter-provider-aws/pull/6508
How was this change tested?
NA
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.967%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/utils/utils.go
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5852

Relevant Lines:
7318

💛  - Coveralls


scripts/npm.sh install shows very many errors in smoke-test

To reproduce:

clean all node_modules
scripts/npm.sh install

><EMAIL_ADDRESS>postinstall /Users/alex/src/vscode-master/test/smoke
> tsc

node_modules/@types/electron/index.d.ts(11,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'preventDefault' must be of type '() => void', but here has type 'Function'.
node_modules/@types/electron/index.d.ts(12,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'sender' must be of type 'WebContents', but here has type 'EventEmitter'.
node_modules/@types/electron/index.d.ts(15,7): error TS2300: Duplicate identifier 'Point'.
node_modules/@types/electron/index.d.ts(20,7): error TS2300: Duplicate identifier 'Size'.
node_modules/@types/electron/index.d.ts(25,7): error TS2300: Duplicate identifier 'Rectangle'.
node_modules/@types/electron/index.d.ts(476,3): error TS2300: Duplicate identifier 'appendSwitch'.
node_modules/@types/electron/index.d.ts(482,3): error TS2300: Duplicate identifier 'appendArgument'.
node_modules/@types/electron/index.d.ts(497,3): error TS2300: Duplicate identifier 'bounce'.
node_modules/@types/electron/index.d.ts(503,3): error TS2300: Duplicate identifier 'cancelBounce'.
node_modules/@types/electron/index.d.ts(509,3): error TS2300: Duplicate identifier 'downloadFinished'.
node_modules/@types/electron/index.d.ts(515,3): error TS2300: Duplicate identifier 'setBadge'.
node_modules/@types/electron/index.d.ts(521,3): error TS2300: Duplicate identifier 'getBadge'.
node_modules/@types/electron/index.d.ts(527,3): error TS2300: Duplicate identifier 'hide'.
node_modules/@types/electron/index.d.ts(533,3): error TS2300: Duplicate identifier 'show'.
node_modules/@types/electron/index.d.ts(540,3): error TS2300: Duplicate identifier 'isVisible'.
node_modules/@types/electron/index.d.ts(546,3): error TS2300: Duplicate identifier 'setMenu'.
node_modules/@types/electron/index.d.ts(552,3): error TS2300: Duplicate identifier 'setIcon'.
node_modules/@types/electron/index.d.ts(572,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'description' must be of type 'string', but here has type 'string | undefined'.
node_modules/@types/electron/index.d.ts(572,3): error TS2687: All declarations of 'description' must have identical modifiers.
node_modules/@types/electron/index.d.ts(584,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'iconIndex' must be of type 'number', but here has type 'number | undefined'.
node_modules/@types/electron/index.d.ts(584,3): error TS2687: All declarations of 'iconIndex' must have identical modifiers.
node_modules/@types/electron/index.d.ts(634,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'type' must be of type '"task" | "separator" | "file" | undefined', but here has type '"task" | "separator" | "file"'.
node_modules/@types/electron/index.d.ts(634,3): error TS2687: All declarations of 'type' must have identical modifiers.
node_modules/@types/electron/index.d.ts(682,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'wasOpenedAtLogin' must be of type 'boolean', but here has type 'boolean | undefined'.
node_modules/@types/electron/index.d.ts(682,3): error TS2687: All declarations of 'wasOpenedAtLogin' must have identical modifiers.
node_modules/@types/electron/index.d.ts(687,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'wasOpenedAsHidden' must be of type 'boolean', but here has type 'boolean | undefined'.
node_modules/@types/electron/index.d.ts(687,3): error TS2687: All declarations of 'wasOpenedAsHidden' must have identical modifiers.
node_modules/@types/electron/index.d.ts(693,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'restoreState' must be of type 'boolean', but here has type 'boolean | undefined'.
node_modules/@types/electron/index.d.ts(693,3): error TS2687: All declarations of 'restoreState' must have identical modifiers.
node_modules/@types/electron/index.d.ts(773,8): error TS2300: Duplicate identifier 'BrowserWindow'.
node_modules/@types/electron/index.d.ts(1410,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'icon' must be of type 'NativeImage', but here has type 'string | NativeImage'.
node_modules/@types/electron/index.d.ts(1413,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'flags' must be of type 'string[] | undefined', but here has type 'ThumbarButtonFlags[] | undefined'.
node_modules/@types/electron/index.d.ts(1542,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'defaultFontFamily' must be of type 'DefaultFontFamily | undefined', but here has type '{ standard?: string | undefined; serif?: string | undefined; sansSerif?: string | undefined; mono...'.
node_modules/@types/electron/index.d.ts(2041,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'companyName' must be of type 'string | undefined', but here has type 'string'.
node_modules/@types/electron/index.d.ts(2041,3): error TS2687: All declarations of 'companyName' must have identical modifiers.
node_modules/@types/electron/index.d.ts(2059,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'extra' must be of type 'Extra | undefined', but here has type '{ [prop: string]: string; } | undefined'.
node_modules/@types/electron/index.d.ts(2064,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'date' must be of type 'string', but here has type 'Date'.
node_modules/@types/electron/index.d.ts(2194,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'properties' must be of type '("openFile" | "openDirectory" | "multiSelections" | "showHiddenFiles" | "createDirectory" | "prom...', but here has type '("openFile" | "openDirectory" | "multiSelections" | "showHiddenFiles" | "createDirectory" | "prom...'.
node_modules/@types/electron/index.d.ts(2280,12): error TS2320: Interface 'DownloadItem' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(2280,12): error TS2320: Interface 'DownloadItem' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(2280,12): error TS2320: Interface 'DownloadItem' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(2280,12): error TS2320: Interface 'DownloadItem' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(2280,12): error TS2320: Interface 'DownloadItem' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(2280,12): error TS2320: Interface 'DownloadItem' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(2280,12): error TS2320: Interface 'DownloadItem' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'removeAllListeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(2472,8): error TS2300: Duplicate identifier 'MenuItem'.
node_modules/@types/electron/index.d.ts(2622,8): error TS2300: Duplicate identifier 'Menu'.
node_modules/@types/electron/index.d.ts(2680,8): error TS2300: Duplicate identifier 'NativeImage'.
node_modules/@types/electron/index.d.ts(2835,8): error TS2300: Duplicate identifier 'ClientRequest'.
node_modules/@types/electron/index.d.ts(2938,12): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'EventEmitter' and 'ReadableStream'.
  Named property 'emit' of types 'EventEmitter' and 'ReadableStream' are not identical.
node_modules/@types/electron/index.d.ts(2938,12): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'EventEmitter' and 'ReadableStream'.
  Named property 'eventNames' of types 'EventEmitter' and 'ReadableStream' are not identical.
node_modules/@types/electron/index.d.ts(2938,12): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'EventEmitter' and 'ReadableStream'.
  Named property 'listenerCount' of types 'EventEmitter' and 'ReadableStream' are not identical.
node_modules/@types/electron/index.d.ts(2938,12): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'EventEmitter' and 'ReadableStream'.
  Named property 'listeners' of types 'EventEmitter' and 'ReadableStream' are not identical.
node_modules/@types/electron/index.d.ts(2938,12): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'EventEmitter' and 'ReadableStream'.
  Named property 'prependListener' of types 'EventEmitter' and 'ReadableStream' are not identical.
node_modules/@types/electron/index.d.ts(2938,12): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'EventEmitter' and 'ReadableStream'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'ReadableStream' are not identical.
node_modules/@types/electron/index.d.ts(2938,12): error TS2320: Interface 'IncomingMessage' cannot simultaneously extend types 'EventEmitter' and 'ReadableStream'.
  Named property 'removeAllListeners' of types 'EventEmitter' and 'ReadableStream' are not identical.
node_modules/@types/electron/index.d.ts(2973,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'headers' must be of type 'any', but here has type '{ [key: string]: string[]; }'.
node_modules/@types/electron/index.d.ts(3198,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'process' must be of type 'any', but here has type 'Process'.
node_modules/@types/electron/index.d.ts(3198,3): error TS2687: All declarations of 'process' must have identical modifiers.
node_modules/@types/electron/index.d.ts(3276,8): error TS2300: Duplicate identifier 'Session'.
node_modules/@types/electron/index.d.ts(3388,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'cache' must be of type 'boolean', but here has type 'boolean | undefined'.
node_modules/@types/electron/index.d.ts(3388,3): error TS2687: All declarations of 'cache' must have identical modifiers.
node_modules/@types/electron/index.d.ts(3399,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'storages' must be of type 'string[] | undefined', but here has type '("appcache" | "cookies" | "filesystem" | "indexdb" | "localstorage" | "shadercache" | "websql" | ...'.
node_modules/@types/electron/index.d.ts(3403,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'quotas' must be of type 'string[] | undefined', but here has type '("temporary" | "persistent" | "syncable")[] | undefined'.
node_modules/@types/electron/index.d.ts(3488,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'domain' must be of type 'string | undefined', but here has type 'string'.
node_modules/@types/electron/index.d.ts(3488,3): error TS2687: All declarations of 'domain' must have identical modifiers.
node_modules/@types/electron/index.d.ts(3492,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'hostOnly' must be of type 'boolean | undefined', but here has type 'string'.
node_modules/@types/electron/index.d.ts(3492,3): error TS2687: All declarations of 'hostOnly' must have identical modifiers.
node_modules/@types/electron/index.d.ts(3496,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'path' must be of type 'string | undefined', but here has type 'string'.
node_modules/@types/electron/index.d.ts(3496,3): error TS2687: All declarations of 'path' must have identical modifiers.
node_modules/@types/electron/index.d.ts(3500,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'secure' must be of type 'boolean | undefined', but here has type 'boolean'.
node_modules/@types/electron/index.d.ts(3500,3): error TS2687: All declarations of 'secure' must have identical modifiers.
node_modules/@types/electron/index.d.ts(3504,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'httpOnly' must be of type 'boolean | undefined', but here has type 'boolean'.
node_modules/@types/electron/index.d.ts(3504,3): error TS2687: All declarations of 'httpOnly' must have identical modifiers.
node_modules/@types/electron/index.d.ts(3508,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'session' must be of type 'boolean | undefined', but here has type 'boolean'.
node_modules/@types/electron/index.d.ts(3508,3): error TS2687: All declarations of 'session' must have identical modifiers.
node_modules/@types/electron/index.d.ts(3997,8): error TS2300: Duplicate identifier 'Tray'.
node_modules/@types/electron/index.d.ts(4158,12): error TS2320: Interface 'WebContents' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(4158,12): error TS2320: Interface 'WebContents' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(4158,12): error TS2320: Interface 'WebContents' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(4158,12): error TS2320: Interface 'WebContents' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(4158,12): error TS2320: Interface 'WebContents' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(4158,12): error TS2320: Interface 'WebContents' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(4158,12): error TS2320: Interface 'WebContents' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'removeAllListeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(4874,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'inputFieldType' must be of type 'string', but here has type '"none" | "other" | "plainText" | "password"'.
node_modules/@types/electron/index.d.ts(4918,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'postData' must be of type 'UploadRawData[] | UploadFile[] | UploadFileSystem[] | UploadBlob[] | undefined', but here has type '(UploadBlob | UploadFileSystem | UploadRawData)[] | undefined'.
node_modules/@types/electron/index.d.ts(4925,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'type' must be of type 'string', but here has type '"rawData"'.
node_modules/@types/electron/index.d.ts(4936,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'type' must be of type 'string', but here has type '"fileSystem"'.
node_modules/@types/electron/index.d.ts(4959,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'type' must be of type 'string', but here has type '"blob"'.
node_modules/@types/electron/index.d.ts(4992,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'pageSize' must be of type 'string | undefined', but here has type 'Size | "A3" | "A4" | "A5" | "Legal" | "Letter" | "Tabloid" | undefined'.
node_modules/@types/electron/index.d.ts(5128,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'activeMatchOrdinal' must be of type 'number', but here has type 'number | undefined'.
node_modules/@types/electron/index.d.ts(5128,3): error TS2687: All declarations of 'activeMatchOrdinal' must have identical modifiers.
node_modules/@types/electron/index.d.ts(5132,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'matches' must be of type 'number', but here has type 'number | undefined'.
node_modules/@types/electron/index.d.ts(5132,3): error TS2687: All declarations of 'matches' must have identical modifiers.
node_modules/@types/electron/index.d.ts(5136,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'selectionArea' must be of type 'SelectionArea', but here has type 'Rectangle | undefined'.
node_modules/@types/electron/index.d.ts(5136,3): error TS2687: All declarations of 'selectionArea' must have identical modifiers.
node_modules/@types/electron/index.d.ts(5214,12): error TS2320: Interface 'Debugger' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(5214,12): error TS2320: Interface 'Debugger' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(5214,12): error TS2320: Interface 'Debugger' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(5214,12): error TS2320: Interface 'Debugger' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(5214,12): error TS2320: Interface 'Debugger' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(5214,12): error TS2320: Interface 'Debugger' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(5214,12): error TS2320: Interface 'Debugger' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'removeAllListeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/@types/electron/index.d.ts(6050,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'type' must be of type 'string | undefined', but here has type '"browser" | "renderer"'.
node_modules/@types/electron/index.d.ts(6050,3): error TS2687: All declarations of 'type' must have identical modifiers.
node_modules/@types/electron/index.d.ts(6054,3): error TS2403: Subsequent variable declarations must have the same type.  Variable 'resourcesPath' must be of type 'string | undefined', but here has type 'string'.
node_modules/@types/electron/index.d.ts(6054,3): error TS2687: All declarations of 'resourcesPath' must have identical modifiers.
node_modules/@types/electron/index.d.ts(6142,2): error TS2300: Duplicate identifier 'export='.
node_modules/electron/electron.d.ts(126,13): error TS2320: Interface 'App' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(126,13): error TS2320: Interface 'App' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(126,13): error TS2320: Interface 'App' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(126,13): error TS2320: Interface 'App' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(126,13): error TS2320: Interface 'App' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(126,13): error TS2320: Interface 'App' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(126,13): error TS2320: Interface 'App' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'removeAllListeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(711,13): error TS2320: Interface 'AutoUpdater' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(711,13): error TS2320: Interface 'AutoUpdater' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(711,13): error TS2320: Interface 'AutoUpdater' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(711,13): error TS2320: Interface 'AutoUpdater' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(711,13): error TS2320: Interface 'AutoUpdater' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(711,13): error TS2320: Interface 'AutoUpdater' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(711,13): error TS2320: Interface 'AutoUpdater' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'removeAllListeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(812,9): error TS2300: Duplicate identifier 'BrowserWindow'.
node_modules/electron/electron.d.ts(1594,9): error TS2300: Duplicate identifier 'ClientRequest'.
node_modules/electron/electron.d.ts(2595,13): error TS2320: Interface 'IpcMain' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2595,13): error TS2320: Interface 'IpcMain' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2595,13): error TS2320: Interface 'IpcMain' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2595,13): error TS2320: Interface 'IpcMain' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2595,13): error TS2320: Interface 'IpcMain' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2595,13): error TS2320: Interface 'IpcMain' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2620,13): error TS2320: Interface 'IpcRenderer' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2620,13): error TS2320: Interface 'IpcRenderer' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2620,13): error TS2320: Interface 'IpcRenderer' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2620,13): error TS2320: Interface 'IpcRenderer' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2620,13): error TS2320: Interface 'IpcRenderer' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2620,13): error TS2320: Interface 'IpcRenderer' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2769,9): error TS2300: Duplicate identifier 'Menu'.
node_modules/electron/electron.d.ts(2819,9): error TS2300: Duplicate identifier 'MenuItem'.
node_modules/electron/electron.d.ts(2845,9): error TS2300: Duplicate identifier 'NativeImage'.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'addListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'on' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'once' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'removeAllListeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(2905,13): error TS2320: Interface 'Net' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'removeListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3016,13): error TS2300: Duplicate identifier 'Point'.
node_modules/electron/electron.d.ts(3024,13): error TS2320: Interface 'PowerMonitor' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3024,13): error TS2320: Interface 'PowerMonitor' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3024,13): error TS2320: Interface 'PowerMonitor' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3024,13): error TS2320: Interface 'PowerMonitor' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3024,13): error TS2320: Interface 'PowerMonitor' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3024,13): error TS2320: Interface 'PowerMonitor' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3024,13): error TS2320: Interface 'PowerMonitor' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'removeAllListeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3208,13): error TS2300: Duplicate identifier 'Rectangle'.
node_modules/electron/electron.d.ts(3230,13): error TS2320: Interface 'Remote' cannot simultaneously extend types 'MainInterface' and 'CommonElectron'.
  Named property 'webContents' of types 'MainInterface' and 'CommonElectron' are not identical.
node_modules/electron/electron.d.ts(3295,13): error TS2320: Interface 'Screen' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'emit' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3295,13): error TS2320: Interface 'Screen' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'eventNames' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3295,13): error TS2320: Interface 'Screen' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listenerCount' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3295,13): error TS2320: Interface 'Screen' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'listeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3295,13): error TS2320: Interface 'Screen' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3295,13): error TS2320: Interface 'Screen' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'prependOnceListener' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3295,13): error TS2320: Interface 'Screen' cannot simultaneously extend types 'EventEmitter' and 'EventEmitter'.
  Named property 'removeAllListeners' of types 'EventEmitter' and 'EventEmitter' are not identical.
node_modules/electron/electron.d.ts(3381,9): error TS2300: Duplicate identifier 'Session'.
node_modules/electron/electron.d.ts(3583,13): error TS2300: Duplicate identifier 'Size'.
node_modules/electron/electron.d.ts(3855,9): error TS2300: Duplicate identifier 'Tray'.
node_modules/electron/electron.d.ts(6234,5): error TS2300: Duplicate identifier 'appendSwitch'.
node_modules/electron/electron.d.ts(6239,5): error TS2300: Duplicate identifier 'appendArgument'.
node_modules/electron/electron.d.ts(6523,5): error TS2300: Duplicate identifier 'bounce'.
node_modules/electron/electron.d.ts(6527,5): error TS2300: Duplicate identifier 'cancelBounce'.
node_modules/electron/electron.d.ts(6531,5): error TS2300: Duplicate identifier 'downloadFinished'.
node_modules/electron/electron.d.ts(6535,5): error TS2300: Duplicate identifier 'setBadge'.
node_modules/electron/electron.d.ts(6536,5): error TS2300: Duplicate identifier 'getBadge'.
node_modules/electron/electron.d.ts(6540,5): error TS2300: Duplicate identifier 'hide'.
node_modules/electron/electron.d.ts(6544,5): error TS2300: Duplicate identifier 'show'.
node_modules/electron/electron.d.ts(6545,5): error TS2300: Duplicate identifier 'isVisible'.
node_modules/electron/electron.d.ts(6549,5): error TS2300: Duplicate identifier 'setMenu'.
node_modules/electron/electron.d.ts(6553,5): error TS2300: Duplicate identifier 'setIcon'.
node_modules/electron/electron.d.ts(8073,3): error TS2300: Duplicate identifier 'export='.

npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.
npm ERR! Darwin 16.7.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v7.10.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>postinstall: `tsc`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'tsc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the code-oss-dev-smoke-test package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tsc
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs code-oss-dev-smoke-test
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls code-oss-dev-smoke-test
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/alex/.electron-gyp/.npm/_logs/2017-11-16T08_16_48_988Z-debug.log

I can't reproduce this. Neither can I with yarn. @alexandrudima Can you try with yarn?

I cannot repro with yarn.