app crashed randomly

My app was running in another tab when it crashed. I am the only user. and there were no changes to my slack team (no new messages or activity of any kind).
it looks like something happened on line 178 of client.js which caused async.js to throw an error
/var/sentora/hostdata/zadmin/public_html/node_modules/@slack/client/node_modules/async/lib/async.js:43
        if (fn === null) throw new Error("Callback was already called.");
                         ^

Error: Callback was already called.
at        /var/sentora/hostdata/zadmin/public_html/node_modules/@slack/client/node_modules/async/lib/async.js:43:36
at handleTransportResponse (/var/sentora/hostdata/zadmin/public_html/node_modules/@slack/client/lib/clients/client.js:178:5)
at Request.handleRequestTranportRes (/var/sentora/hostdata/zadmin/public_html/node_modules/@slack/client/lib/clients/transports/request.js:20:5)
at Request.wrapper [as _callback] (/var/sentora/hostdata/zadmin/public_html/node_modules/@slack/client/node_modules/lodash/index.js:3592:19)
at Request.self.callback (/var/sentora/hostdata/zadmin/public_html/node_modules/@slack/client/node_modules/request/request.js:199:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.<anonymous> (/var/sentora/hostdata/zadmin/public_html/node_modules/@slack/client/node_modules/request/request.js:1036:10)
at emitOne (events.js:82:20)
at Request.emit (events.js:169:7)
[root@panel ~]# node /var/sentora/hostdata/zadmin/public_html/private_js/N.yt.js

here is my code (one instance per user)
    var ⵌ={//slack per user
            RtmClient:require('@slack/client').RtmClient
        ,   RTM_EVENTS:require('@slack/client').RTM_EVENTS
		,	WebClient:require('@slack/client/lib/clients/web/client')
		,	t:'xoxp-xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx'
		,	rtm:undefined
		,	web:undefined
		,	cid:undefined
		,	find:function(){
				ⵌ.rtm=new ⵌ.RtmClient(ⵌ.t,{logLevel:'none'});
				ⵌ.web=new ⵌ.WebClient(ⵌ.t);
				ⵌ.rtm.start();
				ⵌ.web.channels.list(function(e,l){
					if(!e&&l.ok){
						for(var i=0;i<l.channels.length;++i){
							if(l.channels[i].name=='?-'+U.username){
								ⵌ.cid=l.channels[i].id;break;//found the users channel
								}}}
					if(ⵌ.cid){
						ⵌ.web.channels.history(ⵌ.cid,{},function(e,h){
							h=h.messages.reverse();
							var history=[];
							for(var i=0;i<h.length;++i){
								if((h[i].subtype=='bot_message'||!h[i].subtype)&&h[i].type=='message'){
									history.push({
										username:h[i].username.replace('?-','')||'yt'
									,	text:h[i].text
										});}}
							s[1][NULL].WIRE('svr:slack:uzr',history);//give the client the history of chat
							G.SLACK[ⵌ.cid]={uid:U.id,'suid':s[1].uid};//save the client stuff
							s[1][NULL].WHEN['uzr:slack:svr']=function(d){//client wants to post a message
								ⵌ.msg=d;//there is a message so it will post
								ⵌ.say();
								};
							});}});}
		,	say:function(){//console.log('posing');
				function created(ch){
					if(ch.name=='?-'+U.username){
						ⵌ.cid=ch.channel.id;
						ⵌ.rtm.on(ⵌ.RTM_EVENTS.CHANNEL_CREATED,null);
						}
					return;
					}
				function post(){
					ⵌ.web.chat.postMessage(ⵌ.cid,ⵌ.msg,{username:U.username,icon_url:ⵌ.profileimg,account_id:U.id},function(){//console.log('posted!!');
						ⵌ.msg=undefined;
						});}
				if(ⵌ.msg){
					if(!ⵌ.cid){
						ⵌ.rtm.on(ⵌ.RTM_EVENTS.CHANNEL_CREATED,created);
						ⵌ.web.channels.create('?-'+U.username,function(){post();});}
					else{post();}
					}
				return;
				}
		,	profileimg:'defaultuser.png'//todo get real image
		,	msg:undefined//'my awsome message!'
			};

here is my code (only one instance to listen for all messages for my team)
var ⵌ={//slack globally listening
	RtmClient:require('@slack/client').RtmClient
,	RTM_EVENTS:require('@slack/client').RTM_EVENTS
,	t:'xoxp-xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx'
,	rtm:undefined
,	route:function(){
		ⵌ.rtm=new ⵌ.RtmClient(ⵌ.t,{logLevel:'none'});
		ⵌ.rtm.start();
		ⵌ.rtm.on(ⵌ.RTM_EVENTS.MESSAGE,function(m){// Listens to all `message` events from the team
			console.log('G slack',m);
			if((m.subtype=='bot_message'||!m.subtype)&&m.type=='message'){
				var msg={username:m.username||'yt',text:m.text};
				for(var k in G.R[G.SLACK[m.channel].uid]){//find the user they are some where in the saved G global object
					if(G.R[G.SLACK[m.channel].uid][k].readyState==1){
						try{
						G.R[G.SLACK[m.channel].uid][k].send('ʲ'+JSON.stringify({f:'glb:slack:uzr',d:msg}));//relay the message to the user
						}
					catch(e){
						console.log(e);
						}}}
			}});
	    return;
	    }};
ⵌ.route();

my code works nice plugged into slack but, why did that random crash happen?

Just to add some info to this issue, it seems that queueCb (in /lib/clients/client.js, the _callTransport function) is being called twice (at least). The error being thrown is automatically thrown by the async module.

Thanks, I'll take a look at what's happening this evening. I've seen this issue before with the way the requeue logic works, so it maybe a bug in the way that works.

Ok, I'm fairly sure that you hit a retry limit with the number of calls that you were making and that there's a bug in the way the current request retry logic works. I'm tweaking the way the retry logic works now.

Try using the 2.0.6 version and see if this still happens.


Are you looking for a mantainer?

I've noticed this library hasn't been updated for over a year now. If you'd like, I could become a maintainer and keep get the project up to date.

@RebeccaStevens @ninevra @lazarljubenovic @forivall you all created forks. As the original maintainer apparently is not interested/able to continue this, could we declare one of your forks as "official" and publish from there (maybe a new name(space)) to keep this going?
I could support a little if needed.

Iterator helpers seem to be coming to JS (https://github.com/tc39/proposal-iterator-helpers). There's a polyfill available on npm: https://www.npmjs.com/package/iterator-helpers-polyfill
Otherwise, I'd recommend this library: https://github.com/vitaly-t/iter-ops

In addition, i suggest looking at the npm.im/obliterator library


paket install fails with KeyNotFound exception if paket.references refers to unknown reference

this patch wraps safe access around the packages map in order not to throw boring key not found exception

wow I just fixed this one minute before you send this.

Apparently not only I had same problem :D

Anyways. I'm really happy that you took the time to fix this. It was just a
really strange coincidence that I fix it in the very same moment.
Thanks again
On Jun 23, 2015 11:07 AM, "Krzysztof Cieślak"<EMAIL_ADDRESS>wrote:

Apparently not only I had same problem :D
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/pull/897#issuecomment-114414300.


nixos/netdata: fix working with disabled ipmi plugin

Motivation for this change
Fix working netdata with disabled ipmi plugin after this update - https://github.com/NixOS/nixpkgs/pull/126289
cc @Mic92
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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.

@ofborg test netdata

This variant of the code doesn't want to work. But without this patch the service netdata it works fine.
diff --git a/nixos/modules/services/monitoring/netdata.nix b/nixos/modules/services/monitoring/netdata.nix
index 3ea84ca815f..68d6b606a0f 100644
--- a/nixos/modules/services/monitoring/netdata.nix
+++ b/nixos/modules/services/monitoring/netdata.nix
@@ -11,6 +11,7 @@ let
     ln -s /run/wrappers/bin/cgroup-network $out/libexec/netdata/plugins.d/cgroup-network
     ln -s /run/wrappers/bin/perf.plugin $out/libexec/netdata/plugins.d/perf.plugin
     ln -s /run/wrappers/bin/slabinfo.plugin $out/libexec/netdata/plugins.d/slabinfo.plugin
+  '' ++ optionalString (cfg.package.withIpmi) ''
     ln -s /run/wrappers/bin/freeipmi.plugin $out/libexec/netdata/plugins.d/freeipmi.plugin
   '';


bazel issue when deploying to app engine

I'm having issues following the steps to deploy
Deploying to App Engine...
Deploying to App Engine...
+ bazel run upvote/gae:monolith_binary.deploy -- rv3-upvote app.yaml santa_api.yaml
INFO: Invocation ID: 2f292a57-d043-40cf-9751-1c9266c84dcb
Loading:
Loading: 0 packages loaded
ERROR: error loading package '': Encountered error while reading extension file 'appengine/py_appengine.bzl': no such package '@io_bazel_rules_appengine//appengine': The native git_repository rule is deprecated. load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository") for a replacement.
Use --incompatible_remove_native_git_repository=false to temporarily continue using the native rule.
ERROR: error loading package '': Encountered error while reading extension file 'appengine/py_appengine.bzl': no such package '@io_bazel_rules_appengine//appengine': The native git_repository rule is deprecated. load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository") for a replacement.
Use --incompatible_remove_native_git_repository=false to temporarily continue using the native rule.
INFO: Elapsed time: 0.186s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
ERROR: Build failed. Not running target
FAILED: Build did NOT complete successfully (0 packages loaded)

Any ideas?
Thanks!

Looks like the push just went off. Does the deployment work now?

after the latest package, it still no luck
+ echo Deploying to App Engine...
Deploying to App Engine...
+ bazel run upvote/gae:monolith_binary.deploy -- rv3-upvote app.yaml santa_api.yaml
INFO: Invocation ID: 3b653dd6-5934-4d49-aae3-1af652a4cf63
Loading:
Loading: 0 packages loaded
DEBUG: C:/users/win/_bazel_win/bfjoahu7/external/bazel_tools/tools/cpp/lib_cc_configure.bzl:115:5:
Auto-Configuration Warning: 'PROGRAMFILES(X86)' environment variable is not set, using 'C:\Program Files (x86)' as default
Analyzing: target //upvote/gae:monolith_binary.deploy (0 packages loaded, 0 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (0 packages loaded, 128 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (0 packages loaded, 130 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (0 packages loaded, 130 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (0 packages loaded, 130 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (2 packages loaded, 174 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (2 packages loaded, 174 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (2 packages loaded, 174 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (2 packages loaded, 174 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (2 packages loaded, 174 targets configured)
Analyzing: target //upvote/gae:monolith_binary.deploy (3 packages loaded, 174 targets configured)
INFO: Repository rule 'certifi_git' returned: {"remote": "https://github.com/certifi/python-certifi.git", "commit": "4f35e3529c78ced74040cf5d80bf8ec4aac9a190", "shallow_since": "2017-04-17", "init_submodules": False, "verbose": False, "strip_prefix": "", "patches": [], "patch_tool": "patch", "patch_args": ["-p0"], "patch_cmds": [], "build_file": Label("//third_party:certifi.BUILD"), "build_file_content": "", "workspace_file_content": "", "name": "certifi_git"}
Analyzing: target //upvote/gae:monolith_binary.deploy (6 packages loaded, 190 targets configured)
ERROR: C:/users/win/desktop/upvote/upvote-master/upvote/gae/modules/upvote_app/frontend/BUILD:77:1: no such package '@npm_html2js//': no such package '@yarn//': The native new_http_archive rule is deprecated. load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") for a drop-in replacement.
Use --incompatible_remove_native_http_archive=false to temporarily continue using the native rule. and referenced by '//upvote/gae/modules/upvote_app/frontend:ui_templates_genrule'
ERROR: C:/users/win/desktop/upvote/upvote-master/upvote/gae/modules/upvote_app/frontend/BUILD:77:1: no such package '@npm_html2js//': no such package '@yarn//': The native new_http_archive rule is deprecated. load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") for a drop-in replacement.
Use --incompatible_remove_native_http_archive=false to temporarily continue using the native rule. and referenced by '//upvote/gae/modules/upvote_app/frontend:ui_templates_genrule'
ERROR: Analysis of target '//upvote/gae:monolith_binary.deploy' failed; build aborted: no such package '@npm_html2js//': no such package '@yarn//': The native new_http_archive rule is deprecated. load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") for a drop-in replacement.
Use --incompatible_remove_native_http_archive=false to temporarily continue using the native rule.
INFO: Elapsed time: 40.176s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (6 packages loaded, 190 targets configured)
ERROR: Build failed. Not running target
FAILED: Build did NOT complete successfully (6 packages loaded, 190 targets configured)


Ability to exclude remote references (local files)

Is your feature request related to a problem? Please describe.
Hi, we use oasdiff pretty heavily and it's been super super useful.
I have a situation where there is an OpenAPI spec - specifically, this one - which has fields like this:
        "responses": {
          "200": {
            "description": "A list of the newly reserved CVE IDs",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "../schemas/cve-id/create-cve-ids-response.json"
                }
              }
            }
          },

These are references to local files, which are covered in the Swagger Smartbear docs here.
In our situation, will have a single OpenAPI file, but will not have access to those other local files.
Steps to reproduce

Run these commands:

curl https://raw.githubusercontent.com/CVEProject/cve-services/dev/api-docs/openapi.json -o base.json
cat <<EOF >revision.yml
openapi: 3.0.0
paths: {}
EOF

oasdiff diff ./base.json ./revision.yml

Observe that the output indicates a failure to load the reference to another local file:

Text:
Error: failed to load base spec from "./base.json" with open ../schemas/user/get-user-response.json: no such file or directory

Describe the solution you'd like
It would be super helpful if we could exclude remote references to avoid failure.
Describe alternatives you've considered
Currently, I have this ugly parsing and replacement workaround in my python code. It parses the oasdiff output and deletes items that are clearly local refs.
def remove_local_refs(data):
    """Workaround for: https://github.com/Tufin/oasdiff/issues/438"""
    if isinstance(data, dict):
        keys_to_delete = []
        for key, value in data.items():
            if key == "$ref" and isinstance(value, str) and not value.startswith(("http://", "https://", "#")):
                return None  # Return None to indicate this item should be removed
            result = remove_local_refs(value)
            if result is None:
                keys_to_delete.append(key)
            else:
                data[key] = result
        for key in keys_to_delete:
            del data[key]
        return data
    elif isinstance(data, list):
        return [remove_local_refs(item) for item in data if remove_local_refs(item) is not None]
    else:
        return data

def remove_local_refs_from_file(file_path: str):
    with open(file_path, 'r') as base_file:
        base_data = yaml.safe_load(base_file)
    base_data = remove_local_refs(base_data)
    with open(file_path, 'w') as base_file:
        yaml.dump(base_data, base_file)

Additional context
As mentioned, we will have a single OpenAPI file, but will not have access to those other local files.
Happy to answer any questions that I can. Thank you for making such a great tool!

Hi @kmcquade
I did some research to find a solution to this requirement and I was able to get it to work but I think it is beyond the scope of this project since it has to do with loading the specs rather than comparing them.
Let's discuss it offline.
Could you please message me on slack: https://join.slack.com/t/oasdiff/shared_invite/zt-1wvo7wois-ttncNBmyjyRXqBzyg~P6oA

Hi @kmcquade
Here's a solution to remove external references from the json spec before doing the diff, using the jq command.
The credit goes to @tcdsv.
jq 'walk(
  if type == "object" then
    with_entries(
      if .key == "$ref" and (.value | type == "string" and (test("^#") | not)) then
        {key: "type", value: "string"}
      else
        .
      end
    )
  else
    .
  end
)' openapi.json


Introduce shared capability claim checking utilities

In https://github.com/wasmCloud/wasmCloud/pull/289 capability claim checking was removed due to the fact that in general case, the host does not have enough context to perform that check. It would be great to introduce some sharing capability checking functionality to this crate

Particularly, to add a little more detail, this crate has enough information to check the target of the invocation is allowed based on the capability claims of the actor making the request, but only that much. For example we can, today, deny an actor from invoking a capability that it doesn't have the proper claims for. We can also early return if the target is an actor public key to allow an actor call.
The only scenario (that I know of) that we can't account for is invoking via call alias. Since call aliases are claims that are present in the lattice and not in this crate we can't check it.
I think one way we could enforce this is by having actors declare the call aliases they wish to use in their capability claims, then we would have enough context. It feels a little clunky, since we wouldn't in turn require you to declare actor IDs (unless we wanted to) but it would lead to a nice level of visibility into everything an actor may try to call external. Thoughts @autodidaddict ?

The correct issue is it can't tell the difference between a call alias and contract id so it can't reliably determine whether the target of an invocation requires a claims check.

The correct issue is it can't tell the difference between a call alias and contract id so it can't reliably determine whether the target of an invocation requires a claims check.
Embedding the call aliases needed in claims actually prevents the number one use case for call aliases: determining which actor to call at runtime

Embedding the call aliases needed in claims actually prevents the number one use case for call aliases: determining which actor to call at runtime

Well, you have to compile that call alias in anyways, the only thing that changes is the public key behind the call alias. But if you just signed your actor with the call alias, e.g.
wash claims sign pinger.wasm -c wasmcloud:httpserver -c wasmcloud/ponger

Essentially just declaring what you've already hardcoded as a constant

Actually the call alias isn't compiled. The same way you can choose a link name at runtime you need to be able to choose a call alias at runtime. There are a couple of scenarios that require this.

Duplicate of #483


Function executes double

Examples code

<?php

require_once "vendor/autoload.php";

$i = 0;

/**
 * @param \React\Http\Request $request
 * @param \React\Http\Response $response
 */
$app = function ($request, $response) use (&$i) {
    $i++;

    var_dump($i);

    $text = "This is request number $i.\n";
    $headers = array('Content-Type' => 'text/plain');

    $response->writeHead(200, $headers);
    $response->write($text);
    $response->end();
};

$loop = React\EventLoop\Factory::create();
$socket = new React\Socket\Server($loop);
$http = new React\Http\Server($socket);

$http->on('request', $app);

$socket->listen(10201, '<IP_ADDRESS>');
$loop->run();

In web browser I see 1 and on second request I see 3.
Console var_dump result:
int(1)
int(2)
This is the first page load.

This is because your web browser tries to fetch the /favicon.ico as well. Try to simply do this in your $app function:
echo $request->getPath()."\n";
You'll see :+1:

It works. Thanks!


Do not print a warning when loading an image from res:// path

Closes #24222.
Alternative to #39396.
See rationale at https://github.com/godotengine/godot/pull/39396#issuecomment-705482583.
See documentation changes at #42412 instead. I strongly believe this should be part of documentation rather than a warning (which doesn't even apply to all use cases), and the verbosity of the message suggests so. 🙂
There's no need to cherry-pick this to 3.2 if you feel like this warning (deprecation?) has informational value to let people update their projects to use imported resources over loading files dynamically.
As a bonus, removes ResourceLoader dependency from the Image class.

I've reopened this pull request because I'm currently maintaining a patch for this in https://github.com/goostengine/goost, see https://github.com/goostengine/goost/blob/00138700714784b431da532a4676e33eb7e83555/misc/patches/remove_warning_image_load.patch.

Closing for now as this is not the exact solution we'd want to use for this issue.
We put https://github.com/godotengine/godot/issues/24222 on the roadmap for 4.0 so that we properly assess and solve it.


Vcpkg fails to bootstrap on macOS High Sierra

I am trying to setup vcpkg but apparently there is an issue with clang: it detects the correct compiler version > 9 (version <IP_ADDRESS>20039 is > 9), but fails to recognize it as valid: "Apple clang versions 9 and below do not have support for it".
This is the log:
% git clone https://github.com/Microsoft/vcpkg
Cloning into 'vcpkg'...
remote: Counting objects: 39971, done.
remote: Compressing objects: 100% (36/36), done.
remote: Total 39971 (delta 19), reused 32 (delta 11), pack-reused 39924
Receiving objects: 100% (39971/39971), 8.52 MiB | 4.07 MiB/s, done.
Resolving deltas: 100% (26162/26162), done.

% cd vcpkg

% ./bootstrap-vcpkg.sh
Downloading cmake...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 25.8M  100 25.8M    0     0  1752k      0  0:00:15  0:00:15 --:--:--  726k
Downloading cmake... done.
Extracting cmake...
Extracting cmake... done.
Downloading ninja...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   602    0   602    0     0   1036      0 --:--:-- --:--:-- --:--:--  1036
100 77284  100 77284    0     0  52008      0  0:00:01  0:00:01 --:--:--  352k
Downloading ninja... done.
Extracting ninja...
Extracting ninja... done.
/Users/sensei/Documents/Projects/libraries/vcpkg/scripts/bootstrap.sh: line 171: [: Configured with: --prefix=/Applications/Xcode: integer expression expected
-- The C compiler identification is AppleClang <IP_ADDRESS>20039
-- The CXX compiler identification is AppleClang <IP_ADDRESS>20039
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/usr/bin/g++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/usr/bin/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:8 (message):
  Building the vcpkg tool requires support for the C++ Filesystem TS.

  Apple clang versions 9 and below do not have support for it.

  Please install gcc6 or newer from homebrew (brew install gcc6).

  If you would like to try anyway, set VCPKG_ALLOW_APPLE_CLANG.

-- Configuring incomplete, errors occurred!
See also "/Users/sensei/Documents/Projects/libraries/vcpkg/toolsrc/build.rel/CMakeFiles/CMakeOutput.log".
ninja: error: loading 'build.ninja': No such file or directory
cp: /Users/sensei/Documents/Projects/libraries/vcpkg/toolsrc/build.rel/vcpkg: No such file or directory

Any possible fix to this issue?

@fmilicchio Fix this is simple: brew install gcc
Let the bootstrap script use the gcc compiler to build.

I've been using vcpkg with clang on macOS for a while and now  I can't.
It used to work fine! I was very satisfied with this tool and I even adopted this solution for my projects.
Everything was fine until you decided to limit vcpkg to work with gcc only, my question is why?
Maybe I don't want to be limited to gcc toolchain and use clang. I really don't understand...

@xcodeassociated There's no such limitation of only gcc, It's just that you have to use gcc to compile the vcpkg source code to get a vcpkg binary in macOS. After that, you're free to install packages with clang. It's just the bootstrap process that have to use gcc, since vcpkg source is not portable in clang.

@ryancheung Interesting. Do you happen to know what functionalities vcpkg does need from the <filesystem>? I would very much like to avoid installing another compiler, as I use also Intel's icpc and it also does not support the TS.

@fmilicchio   Is the problem solved?How

@baby2nana @fmilicchio @ryancheung
Seems like oclint was the problem. I've tried uninstall of oclint like this.
brew update > /dev/null 2>&1;
brew cask uninstall oclint;  # <---
brew install gcc;
gcc-8 --version;

But I encountered another issue with #include <_stdio.h>... :(
$ ./bootstrap-vcpkg.sh;
Downloading cmake...
Downloading cmake... done.
Extracting cmake...
Extracting cmake... done.
Downloading ninja...
Downloading ninja... done.
Extracting ninja...
Extracting ninja... done.
-- The C compiler identification is AppleClang <IP_ADDRESS>20039
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /Applications/Xcode-9.4.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
-- Check for working C compiler: /Applications/Xcode-9.4.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Checking whether CXX compiler has -isysroot
-- Checking whether CXX compiler has -isysroot - yes
-- Checking whether CXX compiler supports OSX deployment target flag
-- Checking whether CXX compiler supports OSX deployment target flag - yes
-- Check for working CXX compiler: /usr/local/bin/gcc-8
-- Check for working CXX compiler: /usr/local/bin/gcc-8 -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/travis/build/AlcheraInc/AlImage/vcpkg/toolsrc/build.rel
[0/63] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o
[0/63] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg/archives.cpp.o
[0/63] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg/base/checks.cpp.o
[1/63] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o
FAILED: CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o
/usr/local/bin/gcc-8  -DDISABLE_METRICS=0 -I../include -O3 -DNDEBUG   -std=c++1z -MD -MT CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o -MF CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o.d -o CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o -c ../src/vcpkg.cpp
In file included from /usr/include/wchar.h:90,
                 from /usr/local/Cellar/gcc/8.2.0/include/c++/8.2.0/cwchar:44,
                 from /usr/local/Cellar/gcc/8.2.0/include/c++/8.2.0/bits/postypes.h:40,
                 from /usr/local/Cellar/gcc/8.2.0/include/c++/8.2.0/bits/char_traits.h:40,
                 from /usr/local/Cellar/gcc/8.2.0/include/c++/8.2.0/string:40,
                 from ../include/vcpkg/base/chrono.h:4,
                 from ../src/vcpkg.cpp:13:
/usr/local/Cellar/gcc/8.2.0/lib/gcc/8/gcc/x86_64-apple-darwin17.7.0/8.2.0/include-fixed/stdio.h:78:10: fatal error: _stdio.h: No such file or directory
 #include <_stdio.h>
          ^~~~~~~~~~
compilation terminated.

@fmilicchio Did you resolved problem after merged #5915 ?

@soroshsabz No, I've moved to Mojave in the meantime, but a clean clone/bootstrap fails, as Apple's clang does not provide yet the <filesystem> headers:
% ./bootstrap-vcpkg.sh --help
Usage: ./bootstrap-vcpkg.sh [options]

Options:
    -help                Display usage help
    -disableMetrics      Do not build metrics reporting into the executable
    -useSystemBinaries   Force use of the system utilities for building vcpkg
    -allowAppleClang     Set VCPKG_ALLOW_APPLE_CLANG to build vcpkg in apple with clang anyway

% ./bootstrap-vcpkg.sh -allowAppleClang
Downloading cmake...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   621    0   621    0     0   1904      0 --:--:-- --:--:-- --:--:--  1910
100 31.9M  100 31.9M    0     0  7135k      0  0:00:04  0:00:04 --:--:-- 8530k
Downloading cmake... done.
Extracting cmake...
Extracting cmake... done.
Downloading ninja...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   602    0   602    0     0   1967      0 --:--:-- --:--:-- --:--:--  1960
100 77284  100 77284    0     0  65550      0  0:00:01  0:00:01 --:--:-- 65550
Downloading ninja... done.
Extracting ninja...
Extracting ninja... done.
/Users/sensei/Downloads/vcpkg/scripts/bootstrap.sh: line 208: [: Configured with: --prefix=/Applications/Xcode: integer expression expected
-- The C compiler identification is AppleClang <IP_ADDRESS>10046
-- The CXX compiler identification is AppleClang <IP_ADDRESS>10046
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/usr/bin/g++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/usr/bin/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test USES_LIBSTDCXX
-- Performing Test USES_LIBSTDCXX - Failed
-- Performing Test USES_LIBCXX
-- Performing Test USES_LIBCXX - Success
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/sensei/Downloads/vcpkg/toolsrc/build.rel
[1/64] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o
FAILED: CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o
/Applications/Xcode.app/Contents/Developer/usr/bin/g++  -DDISABLE_METRICS=0 -I../include -O3 -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk   -std=c++1z -MD -MT CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o -MF CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o.d -o CMakeFiles/vcpkg.dir/src/vcpkg.cpp.o -c ../src/vcpkg.cpp
In file included from ../src/vcpkg.cpp:24:
../include/vcpkg/base/files.h:8:10: fatal error: 'experimental/filesystem' file not found
#include <experimental/filesystem>
         ^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[2/64] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg/base/cofffilereader.cpp.o
FAILED: CMakeFiles/vcpkg.dir/src/vcpkg/base/cofffilereader.cpp.o
/Applications/Xcode.app/Contents/Developer/usr/bin/g++  -DDISABLE_METRICS=0 -I../include -O3 -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk   -std=c++1z -MD -MT CMakeFiles/vcpkg.dir/src/vcpkg/base/cofffilereader.cpp.o -MF CMakeFiles/vcpkg.dir/src/vcpkg/base/cofffilereader.cpp.o.d -o CMakeFiles/vcpkg.dir/src/vcpkg/base/cofffilereader.cpp.o -c ../src/vcpkg/base/cofffilereader.cpp
In file included from ../src/vcpkg/base/cofffilereader.cpp:1:
../include/pch.h:43:10: fatal error: 'experimental/filesystem' file not found
#include <experimental/filesystem>
         ^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[3/64] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg/base/checks.cpp.o
FAILED: CMakeFiles/vcpkg.dir/src/vcpkg/base/checks.cpp.o
/Applications/Xcode.app/Contents/Developer/usr/bin/g++  -DDISABLE_METRICS=0 -I../include -O3 -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk   -std=c++1z -MD -MT CMakeFiles/vcpkg.dir/src/vcpkg/base/checks.cpp.o -MF CMakeFiles/vcpkg.dir/src/vcpkg/base/checks.cpp.o.d -o CMakeFiles/vcpkg.dir/src/vcpkg/base/checks.cpp.o -c ../src/vcpkg/base/checks.cpp
In file included from ../src/vcpkg/base/checks.cpp:1:
../include/pch.h:43:10: fatal error: 'experimental/filesystem' file not found
#include <experimental/filesystem>
         ^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[4/64] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg/base/downloads.cpp.o
FAILED: CMakeFiles/vcpkg.dir/src/vcpkg/base/downloads.cpp.o
/Applications/Xcode.app/Contents/Developer/usr/bin/g++  -DDISABLE_METRICS=0 -I../include -O3 -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk   -std=c++1z -MD -MT CMakeFiles/vcpkg.dir/src/vcpkg/base/downloads.cpp.o -MF CMakeFiles/vcpkg.dir/src/vcpkg/base/downloads.cpp.o.d -o CMakeFiles/vcpkg.dir/src/vcpkg/base/downloads.cpp.o -c ../src/vcpkg/base/downloads.cpp
In file included from ../src/vcpkg/base/downloads.cpp:1:
../include/pch.h:43:10: fatal error: 'experimental/filesystem' file not found
#include <experimental/filesystem>
         ^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[5/64] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg/base/chrono.cpp.o
FAILED: CMakeFiles/vcpkg.dir/src/vcpkg/base/chrono.cpp.o
/Applications/Xcode.app/Contents/Developer/usr/bin/g++  -DDISABLE_METRICS=0 -I../include -O3 -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk   -std=c++1z -MD -MT CMakeFiles/vcpkg.dir/src/vcpkg/base/chrono.cpp.o -MF CMakeFiles/vcpkg.dir/src/vcpkg/base/chrono.cpp.o.d -o CMakeFiles/vcpkg.dir/src/vcpkg/base/chrono.cpp.o -c ../src/vcpkg/base/chrono.cpp
In file included from ../src/vcpkg/base/chrono.cpp:1:
../include/pch.h:43:10: fatal error: 'experimental/filesystem' file not found
#include <experimental/filesystem>
         ^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[6/64] Building CXX object CMakeFiles/vcpkg.dir/src/vcpkg/archives.cpp.o
FAILED: CMakeFiles/vcpkg.dir/src/vcpkg/archives.cpp.o
/Applications/Xcode.app/Contents/Developer/usr/bin/g++  -DDISABLE_METRICS=0 -I../include -O3 -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk   -std=c++1z -MD -MT CMakeFiles/vcpkg.dir/src/vcpkg/archives.cpp.o -MF CMakeFiles/vcpkg.dir/src/vcpkg/archives.cpp.o.d -o CMakeFiles/vcpkg.dir/src/vcpkg/archives.cpp.o -c ../src/vcpkg/archives.cpp
In file included from ../src/vcpkg/archives.cpp:1:
../include/pch.h:43:10: fatal error: 'experimental/filesystem' file not found
#include <experimental/filesystem>
         ^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
ninja: build stopped: subcommand failed.

@fmilicchio your problem have a solution that describe in https://github.com/Microsoft/vcpkg/issues/6068#issuecomment-482707688

@luncliff I have exactly the same problem as you. On travis, on macOS, I am always stuck with
In file included from /usr/include/wchar.h:90:0,
                 from /usr/local/Cellar/gcc@7/7.4.0_2/include/c++/7.4.0/cwchar:44,
                 from /usr/local/Cellar/gcc@7/7.4.0_2/include/c++/7.4.0/bits/postypes.h:40,
                 from /usr/local/Cellar/gcc@7/7.4.0_2/include/c++/7.4.0/bits/char_traits.h:40,
                 from /usr/local/Cellar/gcc@7/7.4.0_2/include/c++/7.4.0/string:40,
                 from ../include/vcpkg/base/cstringview.h:4,
                 from ../include/vcpkg/base/chrono.h:3,
                 from ../src/vcpkg.cpp:23:
/usr/local/Cellar/gcc@7/7.4.0_2/lib/gcc/7/gcc/x86_64-apple-darwin17.7.0/7.4.0/include-fixed/stdio.h:78:10: fatal error: _stdio.h: No such file or directory
 #include <_stdio.h>
          ^~~~~~~~~~
compilation terminated.

I tried with gcc@8 and gcc@7, without any luck. Did you manage to solve your problem? if yes, how??

fixed changing base image.
Now using osx_image: xcode10.1and vcpkg builds fine

@cenit I couldn't solve the issue at the moment, so I've moved to Azure Pipelines and maintaining my own fork. Sounds good that it's fixed. I'm gonna try that.

@luncliff I want to try Azure Pipelines, but for now I have to deal with the classic travis & appveyor config.
Yes just changing base image fixed, apparently it's a known issue that Homebrew's gcc does not work on travis on default image (Xcode 9.4) due to some missing command line tools (impossible to fix because Apple does not distribute them anymore for that version). Luckily, newer images look fixed :)

We don't support compiling the vcpkg binary with apple-clang, thought that may change in the future.

sudo ./bootstrap-vcpkg.sh --allowAppleClang


Make generate_workspace visible

Can we set visibility to public on the generate_workspace? I'd love to be able to automatically pull the tool into some of my bazel projects so I can use it more easily, but the target is currently private.

Hi Chris,
Thanks for the feedback. Can you explain your general workflow with generate_workspace? I saw your prior comments on #26 and #24, and I do acknowledge it is somewhat awkward that it cannot be called from within an existing project.
For this specific issue, I'll let @kchodorow answer whether this is an appropriate move. However, for the time being, you can modify migration-tooling/generate_workspace/BUILD file so that it reads:
package(default_visibility = ["//visibility:public"]) #<-- new line to add

java_binary(
    name = "generate_workspace",
    main_class = "com.google.devtools.build.workspace.GenerateWorkspace",
    runtime_deps = ["//generate_workspace/src/main/java/com/google/devtools/build/workspace"],
)

Thanks; the temporary fix I was using was to just build directly from the external package, i.e. bazel build @io_bazel_migration_tooling//generate_workspace;
As far as I can tell the intended use-case for generate_workspace is that it should be used once when converting from one project type to another; we're using it every time that we need to add a new maven dependency.
The reason for this is that oftentimes maven dependencies have transitive dependencies and unifying and hunting them down is a large pain with a good chance of making mistakes.  Here's an example of how we're using it:

Start new project
Realize we need lib 'X', so generate a workspace with generate_workspace -a com.X:X:1.0
Work some more...
Realize we need lib 'Y' so generate a new workspace containing X AND Y via generate_workspace -a com.Y:Y:1.0 -a com.X:Y:1.0

In this way we know we never have duplicates and don't need to figure out transitive dependencies manually.
In order to ease this process we have a shell script which calls generate_workspace for us; something like:
/bin/sh
bazel run @io_bazel_migration_tooling//generate_workspace -- -a X:X:1.0 -a Y:Y:1.0 -o /project/dir

By including generate_workspace in our workspace or build file we guarantee that our build scripts and scripts to add libraries "just work" when other team members clone the repo. We don't need to ensure that they've installed the generate_workspace repo somewhere on their machine.
If you need more clarification or have any suggestions on how to improve our workflow then I'm very interested to hear them! Thanks for your work on this!
@jguenther-va, @cede-va

Yeah, it absolutely should be public. Stand by.


itemRenderer implementation

Hey, guys, I tried implementing this code piece to my code to get custom layout:
itemRenderer = ({ item }) => {   return (
       {item.title}
{item.tip}

   ) }
But I am not sure, where I should put it?
In  component as prop?
can you give an example?

@irmantasp have a look at https://github.com/namespace-ee/react-calendar-timeline/blob/5017c49efdd9f47ae33d040f3f1632f0e00d5b11/demo/app/demo-main/index.js

@irmantasp the example @LucidityDesign is commented but there you see it. You find it on L111-L118
I close the Issue but feel free if you need any further assistance. ok?
@LucidityDesign thx for your help! Good to see new people coming in!


Use correct ffmpeg video filters when using hardware encoding

Should fix #148. Previous filter resulted in bad color format conversion.
https://trac.ffmpeg.org/wiki/Hardware/VAAPI#Encoding

But with this we make the conversion on the CPU, don't we? How does CPU usage compare between the two versions, have you tried looking at that? Maybe there are also other options we need to set to the VAAPI filter, but of course, if this doesn't have a noticeable impact on CPU usage we can use this variant as well.

Closing in favor of #208


Module RCTLog is not a registered callable module when set dev mode to false on 0.29.0

encounter this red box error on iOS if set dev to false in AppDelegate.m of UIExplorer sample project.
env: React Native 0.29.0 + iphone 6 (9.3) simulator and device.

I solve this tmp. in index.ios.js, add
var RCTLog = require('RCTLog');

+1

+1

+1

+1

+1

same error to me. finally i found i had build my app in Debug mode working with --dev false react native bundle.
the following code tells us all the things:
- (void)logMessage:(NSString *)message level:(NSString *)level {   if (RCT_DEBUG && [_javaScriptExecutor isValid]) {     [self<EMAIL_ADDRESS>                  args:@[level, message]];   } }

I added: var RCTLog = require('RCTLog');
And with --dev false, I get the following, been struggling for couple of days now I hope you can help guys :/

+1

This happens when:

passing the --dev false option to the packager, which seems to exclude the RCTLog module
and building/running an app with the Xcode Debug configuration, which (by default) defines the DEBUG macro
this in turn enables the RCT_DEBUG macro
which finally leads to RN expecting the RCTLog module to be available

Seeing as all of this happens at compile time and it’s a bit of an edge-case I’m not sure if there’s a simple/good way to detect this in the codebase.
I suggest that, if you do in fact want to test code that is packaged with --dev false, you build your app with the Release configuration instead. From Xcode, hold down the alt key while clicking the run button and select the Release configuration (remember to set it back afterwards).
@ide @javache Any other thoughts?

I think we should make it so that you can test dev JS with Debug native code. It's a pretty reasonable thing to want to do, especially if you encounter bugs that are only in dev JS and want to debug from the native side.

@ide by dev JS, did you mean production JS ? Otherwise I’m confused.

Sorry, yes, I meant production / dev=false JS.

If this is really a common issue, we should revert https://github.com/facebook/react-native/commit/5db4aad347ad8aec754e227e9afd3f5b4922c120 and always provide RCTLog.
cc @lexs

Yeah I think it's common enough to warrant that and the RCTLog source seems small enough.

Reverted: https://github.com/facebook/react-native/commit/4b8688926b93a5b41f191cdba78f0f4335a62111

Yeah~I have the same question,and i add "let RCTLog = require('RCTLog')" in the code,hope to solve this issue.


Added note to heatmap collector code about integrated solution in Tag manager for PPAS version >= 16.8.0

Why? https://piwikpro.slack.com/archives/C9L12C8HX/p1640075331131000
Preview:

looks nice, can we add a note about html5 videos too?

Added as "consider to use" but I'm still not conviced if we should also try to migrate hmmm 🤔  I'm not sure if tag covers all custom cases also, like for heatmaps it do (expect filtering given classnames but lets call it very margin case) .

@rezik007 it does, the only exception is the number of decimal places for timestamps (e.g. user paused at 00:05.334) but we found it not so useful - we weren't able to find a case for any user to want to track split seconds.


Can't handle two endpoints

I'm using Apollo library to get data from GraphQl server in android app. But I need to call several endpoints with different schemas. For example "testserver.com/api/auth" and "testserver.com/api/logic". How can I do that?
My apolloClients:
@Provides @Named("authClient")
fun provideApolloLoginClient(): ApolloClient = ApolloClient.builder()
    .serverUrl("http://testserver.com/api/auth/")
    .build()

@Provides @Named("logicClient")
fun provideApolloMainClient(): ApolloClient = ApolloClient.builder()
        .serverUrl("http://testserver.com/api/logic/")
        .build()

My build.gradle(app) file:
apollo {
   generateKotlinModels = true

    service("auth") {
        sourceFolder = "app/src/main/graphql/auth"
        rootPackageName = "app.src.main.graphql.auth"
        schemaFile = file("app/src/main/graphql/auth/schema.json")
    }

    service("logic") {
        sourceFolder = "app/src/main/graphql/logic"
        rootPackageName = "app.src.main.graphql.logic"
        schemaFile = file("app/src/main/graphql/logic/schema.json")
    }
}

If I working only with one of those endpoints everything fine. But when I add second schema.json and describe services in gradleFile models stop generating and I can't build the app.

Hi 👋 Can you try the following?
apollo {
   generateKotlinModels = true

    service("auth") {
        sourceFolder = "auth"
        rootPackageName = "app.src.main.graphql.auth"
        schemaFile = file("app/src/main/graphql/auth/schema.json")
    }

    service("logic") {
        sourceFolder = "logic"
        rootPackageName = "app.src.main.graphql.logic"
        schemaFile = file("app/src/main/graphql/logic/schema.json")
    }
}

sourceFolder is relative to src/main/graphql and the plugin will look into src/main/graphql/$sourceFolder by default.

Hi @san92der 👋  Anything else I can help with here?

Closing for now, let me know if you want me to reopen


Does not work

Environment

zsh (zplug)

Image

Nice to meet you. I'm a Japanese developer too. I found a bug.
I also try to install via zplug NOT manually. But, it does not work correct too. 😢

Thank you for your report.
It occurs because of your alias of pwd or cd.
Please tell me your aliases for pwd or cd.

@sh-tech


add NltkSentenceSplitter

This PR adds pie_modules.document.processing.NltkSentenceSplitter. From its docstring:
A document processor that adds sentence partitions to a TextDocumentWithLabeledPartitions document.
It uses the NLTK Punkt tokenizer to split the text of the document into sentences. See
https://www.nltk.org/api/nltk.tokenize.html#nltk.tokenize.punkt.PunktSentenceTokenizer for more information.

Args:
    partition_layer_name: The name of the partition layer to add the sentence partitions to. This layer
        must be an AnnotationLayer of LabeledSpan annotations.
    text_field_name: The name of the text field in the document to split into sentences.
    sentencizer_url: The URL to the NLTK Punkt tokenizer model.

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

Project coverage is 95.89%. Comparing base (0f8296b) to head (9f357ee).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #84      +/-   ##
==========================================
+ Coverage   95.86%   95.89%   +0.02%
==========================================
  Files          54       55       +1
  Lines        3897     3921      +24
==========================================
+ Hits         3736     3760      +24
  Misses        161      161

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


Failing w/  Unable to create node:   on openshift (running topology adds 1st node, fails subsequent nodes)

Unable to deploy on openshift cluster.
I'm running with cluster-admin priv and also privileged privileged scc
running topology adds 1st node, fails subsequent nodes
[Y]es, [N]o? [Default: Y]: y
Using OpenShift CLI.
NAME       STATUS    AGE
xfc-prod   Active    5h
Using namespace "xfc-prod".
Checking that heketi pod is not running ... OK
template "deploy-heketi" created
serviceaccount "heketi-service-account" created
template "heketi" created
template "glusterfs" created
node "master1.c.silver-pen-163919.internal" labeled
node "master2.c.silver-pen-163919.internal" labeled
node "master3.c.silver-pen-163919.internal" labeled
daemonset "glusterfs" created
Waiting for GlusterFS pods to start ... OK
service "deploy-heketi" created
route "deploy-heketi" created
deploymentconfig "deploy-heketi" created
Waiting for deploy-heketi pod to start ... OK
Creating cluster ... ID: b7f7e7f782fd78039850508d60d84464
Creating node master1.c.silver-pen-163919.internal ... ID: bf5798bc557d8db30a9248afc736d3e2
Adding device /dev/sdb ... OK
Creating node master2.c.silver-pen-163919.internal ... Unable to create node: Unable to execute command on glusterfs-kk4ex: peer probe: failed: Probe returned with Transport endpoint is not connected
Creating node master3.c.silver-pen-163919.internal ... Unable to create node: Unable to execute command on glusterfs-kk4ex: peer probe: failed: Probe returned with Transport endpoint is not connected
Error loading the cluster topology.
Please check the failed node or device and rerun this script using the --load option.

@debianmaster Did you mention -g in the gk-deploy command? also can you paste the topology file here? Is all the required ports open?
Looks like something wrong in topology file.
master2.c.silver-pen-163919.internal is second node and pod name is glusterfs-kk4ex.
master3.c.silver-pen-163919.internal is third node and pod name is glusterfs-kk4ex.
Both pods are same. This looks fishy.

{
  "clusters": [
    {
      "nodes": [
        {
          "node": {
            "hostnames": {
              "manage": [
                "master1.c.silver-pen-163919.internal"
              ],
              "storage": [
                "<IP_ADDRESS>"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/sdb"
          ]
        },
        {
          "node": {
            "hostnames": {
              "manage": [
                "master2.c.silver-pen-163919.internal"
              ],
              "storage": [
                "<IP_ADDRESS>"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/sdb"
          ]
        },
        {
          "node": {
            "hostnames": {
              "manage": [
                "master3.c.silver-pen-163919.internal"
              ],
              "storage": [
                "<IP_ADDRESS>"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/sdb"
          ]
        }
      ]
    }
  ]
}

topology seems ok to me.    i did see pods having same name but topology has diff names.   does zone  needs to be different?

tried changing zone to diff values still same issue

@debianmaster Looks like there's a networking issue somewhere. Can you oc rsh into one of the gluster pods and see if you can ping the other nodes?

@jarrpa  i'm able to rsh to daemon set pod and ping other nodes in cluster
any other pointers?

[heketi] ERROR 2017/04/15 03:43:02 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:38: Minimum brick size limit reached.  Out of space.
[asynchttp] INFO 2017/04/15 03:43:02 Completed job e436b1f75ff1f8f567b9272217782ceb in 12.281471ms
[heketi] ERROR 2017/04/15 03:43:02 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: No space
[negroni] Started GET /queue/e436b1f75ff1f8f567b9272217782ceb
[negroni] Completed 500 Internal Server Error in 115.658µs
i'm spending crazy time on this!    is there a updated video for deploying on k8s?   video seems to be old

@debianmaster The No Space error is something which we have gotten some criticism about but have not come up with a good solution for. It can stand for a number of error scenarios that are difficult to isolate at this time.
Two things to consider:

Did you go through the pre-req steps to open all the required ports for the GlusterFS pods?
Are the devices you're adding clean (no filesystem AND not marked as LVM PVs) and at least 1 GB in size?

If these are true, then I suggest starting over from scratch, get to the error state, then check (and post if needed) what look like relevant portions of the oc logs for the deploy-heketi pod and the one GlusterFS pod that is listed in the error output of gk-deploy.

I am also facing this No space error same as @debianmaster. Logs while executing gk-deploy:
[root@m1 deploy]# ./gk-deploy -c oc -g  topology.json
Welcome to the deployment tool for GlusterFS on Kubernetes and OpenShift.
Before getting started, this script has some requirements of the execution
environment and of the container platform that you should verify.
The client machine that will run this script must have:

Administrative access to an existing Kubernetes or OpenShift cluster
Access to a python interpreter 'python'
Access to the heketi client 'heketi-cli'

Each of the nodes that will host GlusterFS must also have appropriate firewall
rules for the required GlusterFS ports:

2222  - sshd (if running GlusterFS in a pod)
24007 - GlusterFS Daemon
24008 - GlusterFS Management
49152 to 49251 - Each brick for every volume on the host requires its own
port. For every new brick, one new port will be used starting at 49152. We
recommend a default range of 49152-49251 on each host, though you can adjust
this to fit your needs.

In addition, for an OpenShift deployment you must:

Have 'cluster_admin' role on the administrative account doing the deployment
Add the 'default' and 'router' Service Accounts to the 'privileged' SCC
Have a router deployed that is configured to allow apps to access services
running in the cluster

Do you wish to proceed with deployment?
[Y]es, [N]o? [Default: Y]: Y
Using OpenShift CLI.
NAME           STATUS    AGE
glusterstore   Active    9h
Using namespace "glusterstore".
Checking that heketi pod is not running ... OK
template "deploy-heketi" created
serviceaccount "heketi-service-account" created
template "heketi" created
template "glusterfs" created
node "m1" labeled
node "c1" labeled
node "c2" labeled
daemonset "glusterfs" created
Waiting for GlusterFS pods to start ... OK
service "deploy-heketi" created
route "deploy-heketi" created
deploymentconfig "deploy-heketi" created
Waiting for deploy-heketi pod to start ... OK
Creating cluster ... ID: fc74e4ee3cd42c127b3d45adbdc1f8aa
Creating node m1 ... ID: 8ac07a8c8dbbdd392c1f8dab81dd4395
Adding device /dev/vdb ... OK
Creating node c1 ... ID: eccf5f908572dff94886e9b7d505efb2
Adding device /dev/vdb ... OK
Creating node c2 ... ID: 9a4953c772e57555d4dbb14c23609fcf
Adding device /dev/vdb ... OK
heketi topology loaded.
Error: No space
Failed on setup openshift heketi storage

@SaravanaPunith Your error is different from @debianmaster's, please open a new Issue.

running this command on all nodes fixed issue sudo iptables -I INPUT -p all -j ACCEPT

@debianmaster oh... I suppose that's a valid question: did you open the requisite firewall ports on all the nodes that would be running GlusterFS pods?

@jarrpa  i opened on cloud level, but looks like i need to open at host level too.    not a networking pro :P    thanks for the quick help.   everything seems to work now!

@debianmaster Happy to hear! :D Best of luck.


Update kpt-functions-ci go version to 1.15

Fixes https://github.com/GoogleContainerTools/kpt/issues/2089
This update kpt-functions-sdk go version to 1.15. This should help address CI failures.

Thanks for working on this!
The CI is still failing, it looks like we need to remove the vendor directory: https://github.com/GoogleContainerTools/kpt-functions-sdk/tree/master/go/vendor

Not sure what's going on here, this error does not occur locally for me. I'll continue to poke at this as my time allows. Recreating the vendor directory with rm -rf vendor; go mod tidy; go mod vendor did not make any significant changes.

Any update on this?
It seems our CI is failing. This has a higher priority. We should fix this soon. Otherwise, we can't merge PRs.

If you need help, please let me know.

I can experiment, I can't reproduce locally though.

Removing the vendor directory has resolved the issues with upgrading to go 1.15.

Thanks for fixing the CI!


Load the plugin twice and change name

Hi! I'm starting to use the plugin and it's awesome to create custom reports for my monthly expenses, etc.
I'd like to be able to load the plugin twice, as to have two tabs in Fava. In my case, I have to track most things twice, in my home currency, which is very volatile, and in dollars. This would allow me to duplicate most dashboards but changing the currency.
Maybe this is better suited for the Fava repo, but also I think, doing something like this would work perfectly and be very flexible:
2023-01-02 custom "fava-extension" "fava_dashboards" "[
    {'config': 'plugins/fava_dashboards/example01.yaml', name: "Dashboards 01"},
    {'config': 'plugins/fava_dashboards/example02.yaml', name: "Dashboards 02"}
]"

afaics that's currently not possible, because each Fava extension has only one entry in the navigation bar and the name of the navigation entry is static. You can open an issue in the Fava repo, or alternatively add multiple dashboards in the same file and for example prefix them with the currency.

Mhmm. Reading a bit about other plugins, I think you are right about it not being possible. Bummer.
About your workaround, could you show me a little example on what you mean?

About your workaround, could you show me a little example on what you mean?

You can add multiple pages/dashboards to a dashboards.yaml file, i.e. this example: https://github.com/andreasgerstmayr/fava-dashboards/blob/main/example/dashboards.yaml contains the following dashboards: Overview, Assets, Income and Expenses, Travelling and Sankey. You can copy them and call them Overview (USD), Overview (EUR), etc.

I've been doing that. I feel like been able to have many custom dashboard pages in Fava could be cool to separate some things. I'll close this now as I think this is the closest I'll get to that. Thanks for the amazing plugins!


Tests broken after CMOR table update.

The ece2cmor3 tests are broken after CMOR table update. The update solved issue #111. The checvars.py works fine.

Rev. 0de74968437724647f29df18af22cb03e364c380


Mark some more functions as const fn

Should I keep or remove the const stuff in src/image.rs ?

If it being const is not actually true, I think removing it would be right

If it being const is not actually true, I think removing it would be right

Yeah, I'm unclear if they are or not. :)


cannot import name 'newfig' from 'plotting'

...

I also come across this problem. And I take a look at the help(plotting), there is no attribute newfig.

ValueError: Key pgf.preamble: Could not convert ['\usepackage[utf8x]{inputenc}', '\usepackage[T1]{fontenc}'] to str出现了这个问题

@zhengshichao1991 @wanghongyue-echo 我已经成功解决这个问题了，只需要在Utilities的plotting文件中将
"pgf.preamble": [
r"\usepackage[utf8x]{inputenc}",    # use utf8 fonts becasue your computer can handle it :)
r"\usepackage[T1]{fontenc}",        # plots will be generated using this preamble
]
更改为
"pgf.preamble": "\usepackage[utf8x]{inputenc}\n\usepackage[T1]{fontenc}",

@zhengshichao1991 @wanghongyue-echo I have already solve this problem with the help of Chat GPT.我已经成功解决这个问题了，只需要在Utilities的plotting文件中将 "pgf.preamble": [ r"\usepackage[utf8x]{inputenc}", # use utf8 fonts becasue your computer can handle it :) r"\usepackage[T1]{fontenc}", # plots will be generated using this preamble ] 更改为 "pgf.preamble": "\usepackage[utf8x]{inputenc}\n\usepackage[T1]{fontenc}",

In matplotlib 3.x, you can replace as
"pgf.preamble": "\n".join([
    r"\usepackage[utf8x]{inputenc}",    # use utf8 fonts becasue your computer can handle it :)
    r"\usepackage[T1]{fontenc}",        # plots will be generated using this preamble
    ])

@zhengshichao1991 @wanghongyue-echo I have already solve this problem with the help of Chat GPT.我已经成功解决这个问题了，只需要在Utilities的plotting文件中将 "pgf.preamble": [ r"\usepackage[utf8x]{inputenc}", # use utf8 fonts becasue your computer can handle it :) r"\usepackage[T1]{fontenc}", # plots will be generated using this preamble ] 更改为 "pgf.preamble": "\usepackage[utf8x]{inputenc}\n\usepackage[T1]{fontenc}",

In matplotlib 3.x, you can replace these as
"pgf.preamble": "\n".join([
    r"\usepackage[utf8x]{inputenc}",    # use utf8 fonts becasue your computer can handle it :)
    r"\usepackage[T1]{fontenc}",        # plots will be generated using this preamble
    ])

This works for me. :)


7.4.0 Invoking pwsh -Command with stdout redirection from within PowerShell results in CLIXML instead of actual output

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
I ran across this by accident while trying to workaround issue #20747.
If I'm using PowerShell 7.4.0 and I invoke pwsh with -Command and I redirect the output of pwsh to a file, that file ends up containing CLIXML with an encoded version of the output rather than the actual output, as happens in 7.3.10
When doing this with a script and pwsh -File things work as expected.
This appears to be related to the PR: Support byte stream piping between native commands and file redirection by @SeeminglyScience that was added in preview 4.
Expected behavior
PS> pwsh >x.txt -Command { Write-Output "Hello" }

PS> Get-Content x.txt
Hello

Actual behavior
PS> pwsh >x.txt -Command { Write-Output "Hello" }

PS> Get-Content x.txt
#< CLIXML
<Objs Version="<IP_ADDRESS>" xmlns="http://schemas.microsoft.com/powershell/2004/04"><S S="Output">Hello</S></Objs>

Error details
No error invovled.

Environment data
Name                           Value
----                           -----
PSVersion                      7.4.0
PSEdition                      Core
GitCommitId                    7.4.0
OS                             Microsoft Windows 10.0.19044
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
7.3.10

7.4.0

Note that as in #20747 if you adding writing an error and then redirect stderr to a file, that file ends up empty rather than containing the error.

When I'm in PowerShell 7.4.0 and use powershell(.exe) instead of pwsh in the command line I get the same behavior.
PS> powershell.exe >x.txt -Command { Write-Output "Hello" }

PS> Get-Content x.txt
#< CLIXML
<Objs Version="<IP_ADDRESS>" xmlns="http://schemas.microsoft.com/powershell/2004/04"><S S="Output">Hello</S></Objs>


[DOC]Update the instructions to build the docs

Update the instructions to build the docs in here. https://github.com/NVIDIA-Merlin/systems/tree/main/docs
Looks like it was copy pasted from models?
Impact: L

I happened to update the docs/README.md file while adding the docs build.
https://github.com/NVIDIA-Merlin/systems/pull/77/files#diff-0b5ca119d2be595aa307d34512d9679e49186307ef94201e4b3dfa079aa89938
Closing.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/25054

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/25418

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26226

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27472

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27472

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27562

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27562

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/29623

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/29697

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/29958

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/33012

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/34836

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/56894

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67945

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/68189

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/69517

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/78128

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87964


Add support for wallet-selector and further methods.

Currently, this library supports signing transactions by inputting account credentials to sign with or by using this library inside of a wallet so the wallet can sign transactions and display transaction details of the payload to the user even if it's on another chain.
Whilst it is preferable for a user to be able to see the transaction details before signing and we should recommend that wallets integrate this, any NEAR wallet should be able to sign multichain transactions with this library without supporting it in the wallet (they just won't be able to display the transaction details properly to the user).
Additionally, when setting up a chain object (EVM, bitcoin, etc.) the user must input a provider which isn't the best DevEx. Getting balance also requires this provider.
Here is a suggested list of methods for EVM, (note that other chains will likely have to be different, especially bitcoin). Optional arguments are given in square brackets.
Construct chain object
Initiates the chain object, sets the near network (mainnet/testnet), chain ID, key version, RPC URL, and the MPC contract. If not provided, the key version and MPC contract will be set to default values. If an RPC URL is not provided then they will not be able to use many methods here but the user may want to just derive addresses and public keys.
new EVM(nearNetwork, chainId, [keyVerion], [rpcUrl], [mpcContract])

Derive address
Derives an address on the target chain from a provided path and NEAR account.
deriveAddress(path, nearAccount)

Returns address.
Derive public key
Derives a public key on the target chain from a provided path and NEAR account. This is especially useful in the NEAR case.
derviePublicKey(path, nearAccount)

Returns public key.
Get account balance
Gets the native token balance of an account on the target chain.
getBalance(address)

Returns balance.
Construct transaction
This will allow the user to create any type of transaction for the target chain. This will include things like a simple transfer of funds, a contract call, contract deployment, etc.
I really like the way this is done in omni-transaction-rs and think a similar approach should be taken here. It would be good to be able to build specific data for each chain like is done for NEAR in the omni-transaction-rs library but this will take a fair bit of work.
Returns a transaction object.
Store transaction
Stores a transaction object in session storage as the object will be lost upon wallet redirect. A prefix is specified as the user may want to store multiple transactions.
storeTransaction(transaction, prefix)

Get stored transaction
Gets the stored transaction object from session storage.
getStoredTransaction(prefix)

Returns a transaction object.
Sign a transaction and reconstruct signature
Sign a transaction object by making a call to the MPC contract. The signature is then reconstructed and added to the transaction object. The user can either pass in a NEAR account object, wallet-selector wallet object, or a credentials object (if used inside of a wallet) to sign the transaction.
signTransaction(transaction, path, [object])

Returns a signed transaction object.
Reconstruct signature
Adds a signature to a transaction. This will be used when a web wallet is used or in an indexer to fetch transactions and signatures and relay them. The signature object will have the same structure as the return type of the MPC.
reconstructSignature(transaction, signature)

Returns a signed transaction object.
Broadcast transaction
Relays a signed transaction object to the target chain.
broadcastTransaction(signedTransaction)

Returns a transaction hash on the target chain.
Make a view call to a contract
Makes a view call to a contract on the target chain.
viewCall(contractAddress, methodName, [args])

Returns the result of the view call.

Additional methods that could be useful:
Sign with mtx relayer
Sign the transaction with a NEAR meta-transactions relayer.
Sign and send transaction
A single method to sign and broadcast a transaction.
Transfer funds
A single method to transfer the native token of the chain to another address.

Thoughts:

Upon wallet redirect, the path being used would be lost, and the user would likely want to retain this. Maybe we should have a method to store the path in local storage also, this could be implemented as an option in store transaction.
We may want to have a simplified method for reconstructing the signature in the case of a web wallet where the method just takes a transaction and fetches the tx hash from the URL, gets the signature, and then reconstructs.

This all looks good to me and I think provide the basics that we want from this library.
A couple of things:

let's strive for consistency and shortness when naming e.g. setTx, getTx (I can't imagine having names similar).
let's explain the approach of constructing a transaction using a transaction builder in more detail.
I think a transaction builder should be constructing a transaction from unsigned JSON e.g. ethers uses the concept of a "base transaction" which is pure JSON, not a javascript instance or anything.
distinguish between what methods are chain specific and what methods are global to the library e.g. broadcastTx would be a method of each chain object or would it be a global method that takes a hash produced by a method from a chain object?
rename additional methods to a "Future Work" section, so it's clear we are not going to work on or discuss these now.

All methods here are chain specific, I don't believe any could be made as general utils.


Liquid hardener accept 1 type of forms

How to automate that mech with many forms, if fluid bus accept only liquids? Or idk - it have different inputs option?

uh, have 2 machines?

uh, have 2 machines?

Sorry, Big Liquid hardener*

No comments.


Chapter 5 b - suggestions

5.17 - Computing Bounding Rectangles

and uses an infix operator alias \/ to compute the union of the two bounding rectangles.

I ended up trying to find that \/ infix operator on pursuit here but I don't think this is the right operator for it's use here.

I'll move this into a comment on the other thread, thanks!

@paf31 it's cool I'll do it if you want wasn't sure what would be easier for you, I'll just keep adding them to that issue


allow customizing access point details

Added access_points variable
Changes

Changed module efs to have a customizable access_points parameter

Why :pleading_face:

Fix bug on latest AMI where mongod UID/GID has changed, breaking bootstrapping.

Hmm, I'm sorry, I didn't realize the additional changes I was adding would automatically get added here. Still though, I think the changes are worthwhile, I'll just update the PR details.


Modified state logging of the execution.

Added migration

I ran the test in my local machine and we are up to a 87% of coverage. I am going to add some unittest to cover some of the new funtionalities of this PR

I ran the test in my local machine and we are up to a 87% of coverage. I am going to add some unittest to cover some of the new funtionalities of this PR


Remove Journal default ctor

The pull request has two commits so far.

The first commit removes the default constructor of beast::Journal.  This constructor provided a Journal that would not write anything.  I believe that choice is a dangerous default.  There were places in the code using a default constructed Journal where it was not obvious that the Journal would not write.  A non-writing Journal has a place in the world, but it should be asked for explicitly.  The bulk of the commit is simply fixing up the places that were relying on the default constructor.

The second commit makes it easier for unit tests to use a Journal intended for unit testing.  Previously this kind of a Journal was only available from an Env.  Now they can create these Journals independent of Env.  The bulk of the commit is converting those unit tests that used Env for its Journal to construct their own Journal directly.

Jenkins Build Summary
Built from this commit
Built at 20180920 - 23:00:01
Test Results

Build Type
Log
Result
Status

rpm
logfile
1035 cases, 0 failed, t: n/a
PASS :white_check_mark:

msvc.Debug
logfile
1033 cases, 0 failed, t: 757s
PASS :white_check_mark:

msvc.Debug, NINJA_BUILD=true
logfile
1033 cases, 0 failed, t: 630s
PASS :white_check_mark:

msvc.Debug -Dunity=OFF
logfile
1033 cases, 0 failed, t: 1194s
PASS :white_check_mark:

msvc.Release
logfile
1032 cases, 0 failed, t: 414s
PASS :white_check_mark:

gcc.Release -Dassert=ON, MANUAL_TESTS=true
logfile
1101 cases, 0 failed, t: 933s
PASS :white_check_mark:

docs
logfile
1 cases, 0 failed, t: 2s
PASS :white_check_mark:

clang.Debug
logfile
1036 cases, 0 failed, t: 281s
PASS :white_check_mark:

gcc.Debug -Dcoverage=ON
logfile
1036 cases, 0 failed, t: 853s
PASS :white_check_mark:

gcc.Debug
logfile
1036 cases, 0 failed, t: 289s
PASS :white_check_mark:

clang.Debug -Dunity=OFF
logfile
1036 cases, 0 failed, t: 669s
PASS :white_check_mark:

clang.Release -Dassert=ON
logfile
1035 cases, 0 failed, t: 403s
PASS :white_check_mark:

gcc.Debug -Dunity=OFF
logfile
1036 cases, 0 failed, t: 727s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF
logfile
1036 cases, 0 failed, t: 292s
PASS :white_check_mark:

gcc.Release -Dassert=ON
logfile
1035 cases, 0 failed, t: 424s
PASS :white_check_mark:

gcc.Debug, NINJA_BUILD=true
logfile
1036 cases, 0 failed, t: 275s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF -DBUILD_SHARED_LIBS=ON
logfile
1036 cases, 0 failed, t: 294s
PASS :white_check_mark:

clang.Debug -Dunity=OFF -Dsan=address, PARALLEL_TESTS=false, DEBUGGER=false
logfile
1036 cases, 0 failed, t: 827s
PASS :white_check_mark:

clang.Debug -Dunity=OFF -Dsan=undefined, PARALLEL_TESTS=false
logfile
1036 cases, 0 failed, t: 1189s
PASS :white_check_mark:

Codecov Report

Merging #2691 into develop will increase coverage by 0.16%.
The diff coverage is 89.47%.

@@             Coverage Diff             @@
##           develop    #2691      +/-   ##
===========================================
+ Coverage    70.01%   70.18%   +0.16%
===========================================
  Files          704      704
  Lines        55262    55266       +4
===========================================
+ Hits         38694    38790      +96
+ Misses       16568    16476      -92

Impacted Files
Coverage Δ

src/ripple/app/tx/impl/Taker.h
96.55% <ø> (ø)
:arrow_up:

src/ripple/app/tx/impl/Transactor.h
100% <ø> (ø)
:arrow_up:

src/ripple/app/tx/impl/ApplyContext.h
100% <ø> (ø)
:arrow_up:

src/ripple/beast/utility/Journal.h
96.87% <ø> (-0.14%)
:arrow_down:

src/ripple/app/ledger/impl/LedgerToJson.cpp
88.7% <0%> (ø)
:arrow_up:

src/ripple/net/AutoSocket.h
44.82% <100%> (+0.64%)
:arrow_up:

src/ripple/resource/impl/ResourceManager.cpp
69.56% <100%> (+0.67%)
:arrow_up:

src/ripple/ledger/impl/View.cpp
91.21% <100%> (+0.77%)
:arrow_up:

src/ripple/core/Config.h
100% <100%> (ø)
:arrow_up:

src/ripple/app/misc/SHAMapStoreImp.h
97.22% <100%> (+0.16%)
:arrow_up:

... and 25 more

Continue to review full report at Codecov.

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

Removing the default constructor does make some code more verbose, but using a null sink is strange enough that I'm in favor of calling attention to it. I do think this chage is a net positive and I'd vote to merge it.
@nbougalis I also agree our logging framework is awkward.

@mellery, nice change with the SuiteJournal!  Excellent use of aggregation plus a conversion operator.  I wish I'd thought of that.  I cherry-picked your change, but I also changed the name of the new include file to SuiteJournal.h, since that's what is typically used.

In 1.2.0-b3


ci: use strict range of peerDependencies for yarn

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows Conventional Commits
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Refactoring
[ ] Code style update
[x] Build or CI related changes
[ ] Documentation content changes

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Codecov Report

Merging #1295 (ffa536c) into main (f29f878) will increase coverage by 0.64%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1295      +/-   ##
==========================================
+ Coverage   64.91%   65.56%   +0.64%
==========================================
  Files         746      642     -104
  Lines        8643     7493    -1150
  Branches     1733     1514     -219
==========================================
- Hits         5611     4913     -698
+ Misses       2614     2210     -404
+ Partials      418      370      -48

Flag
Coverage Δ

addon-charts
?

addon-doc
26.89% <ø> (ø)

addon-editor
?

addon-mobile
?

addon-table
?

addon-tablebars
∅ <ø> (∅)

cdk
82.33% <ø> (ø)

core
68.93% <ø> (ø)

kit
64.07% <ø> (ø)

summary
65.56% <ø> (+0.64%)
:arrow_up:

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

Impacted Files
Coverage Δ

...ditor/components/input-color/input-color.module.ts

projects/addon-table/tokens/i18n.ts

projects/addon-editor/utils/is-selection-in.ts

...-commerce/components/input-CVC/input-CVC.module.ts

...charts/components/pie-chart/pie-chart.directive.ts

projects/addon-commerce/utils/format-currency.ts

...jects/addon-commerce/constants/card-holder-mask.ts

.../addon-charts/components/bar-set/bar-set.module.ts

...jects/addon-charts/components/bar/bar.component.ts

...nts/table-pagination/table-pagination.component.ts

... and 94 more

Continue to review full report at Codecov.

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


feat(Text): add font weight prop

Created from https://github.com/stardust-ui/react/pull/109.  That PR was on a fork and we don't share API keys with forks.  Screener could not run on that branch.
/cc @bcalvery

Merging, see #109 for the review.


Error: Resource temporarily unavailable Cannot lock port

SerialPort version: 4.0.7
NodeJS Version: 7.0.4
Operating System and Hardware Platform:

macOS Sierra 10.12.2
MacBook Pro (15-inch, Late 2016)
Arduino Due, Arduino Uno

Are you using an alternative NodeJS runtime? (eg Electron):
I'm using Electron v1.4.14.
Summary of Problem
I'm able to list the serial devices, but when I try to connect to them I get the following error:
Resource temporarily unavailable Cannot lock port

Steps and Code to Reproduce the Issue
I have 3 arduinos connected to my machine. I'm using SerialPort.list to get their comName values, then creating a new SerialPort instance using the comName as the id value shown below. The comName is usually something like /dev/cu.usbmodem14541.
This is the code I'm using to open the port:
    const port = new SerialPort(id, {
      baudRate: 9600,
      parser: SerialPort.parsers.readline(),
    }, (error) => {
      if (error) {
        emit({ type: CONNECT_DEVICE_ERROR, id, error });
      }

      if (port.isOpen()) {
        emit({ type: CONNECT_DEVICE_OPEN, id });
      }

      console.log({
        id,
        port,
        isOpen: port.isOpen(),
        path: port.path,
        baudRate: port.baudRate,
        binding: port.binding,
      });
    });

    emit({ type: CONNECT_DEVICE_START, id, port });
    port.on('data', data => emit({ type: CONNECT_DEVICE_DATA, id, data }));
    port.on('disconnect', () => emit({ type: DEVICE_DISCONNECTED, id }));
    port.on('close', () => emit({ type: CONNECT_DEVICE_CLOSE, id }));
    port.on('error', error => emit({ type: CONNECT_DEVICE_ERROR, id, error }));

Instead of opening the ports, this emits the error shown above.
I am able to connect to the devices using platformio device monitor, which uses the same values that serialport is using:

baudRate: 9600
parity: none
dataBits: 8
stopBits: 1

The following image shows that platformio device monitor is connected:

Update: I tried connecting using the cli interface. I get the same result.
https://gist.github.com/lynndylanhurley/c2edf304a21db760a02120a6fd856491

Also tried updating to the latest beta (5.0.0-beta3). I get the same result.

@reconbot - for some reason when I run SerialPort.list I only see cu.xxx entries, not the tty.xxx entries.
For example, this is the result of ls -al /dev | grep usbmodem:
❯ ls -al /dev | grep usbmodem
crw-rw-rw-   1 root        wheel           20,  11 Jan 29 14:31 cu.usbmodem14511
crw-rw-rw-   1 root        wheel           20,   7 Jan 29 14:31 cu.usbmodem14531
crw-rw-rw-   1 root        wheel           20,   9 Jan 29 14:31 cu.usbmodem14541
crw-rw-rw-   1 root        wheel           20,  10 Jan 29 14:31 tty.usbmodem14511
crw-rw-rw-   1 root        wheel           20,   6 Jan 29 14:31 tty.usbmodem14531
crw-rw-rw-   1 root        wheel           20,   8 Jan 29 14:31 tty.usbmodem14541

But this is all I see from 'SerialPort.list`:
{
  "list": [
    {
      "comName": "\/dev\/cu.lpss-serial1"
    },
    {
      "comName": "\/dev\/cu.lpss-serial2"
    },
    {
      "comName": "\/dev\/cu.Bluetooth-Incoming-Port"
    },
    {
      "comName": "\/dev\/cu.usbmodem14531",
      "locationId": "0x14530000",
      "manufacturer": "Arduino (www.arduino.org)",
      "productId": "0x003d",
      "serialNumber": "85438333036351F0C1E0",
      "vendorId": "0x2a03"
    },
    {
      "comName": "\/dev\/cu.usbmodem14541",
      "locationId": "0x14540000",
      "manufacturer": "Arduino (www.arduino.org)",
      "productId": "0x003d",
      "serialNumber": "85438333036351110211",
      "vendorId": "0x2a03"
    },
    {
      "comName": "\/dev\/cu.usbmodem14511",
      "locationId": "0x14510000",
      "manufacturer": "Arduino (www.arduino.cc)",
      "productId": "0x0043",
      "serialNumber": "95538333535351601162",
      "vendorId": "0x2341"
    }
  ]
}

Can you think of a reason why I can't see the tty.xxx devices from SerialPort.list?

Thanks @reconbot, opening the port without locking worked 🥇
Should I close this out, or should I leave it open until the new title issue is resolved?


include utils folder into the copied folders list

[x] Fix ejecting problem

closes #23

Hi thanks for your MR. I will check it this weekend (at the latest) and get this merged in and released. Thanks for investigating and resolving the issue yourself :)

@VasilyShelkov Please merge this, it's been past the "this weekend" of March 30th ʕ•ᴥ•ʔ

@VasilyShelkov I second that. After ejecting some scripts are missing :(


Fix service broker plan updates requiring strict ordering

Includes work done for https://www.pivotaltracker.com/story/show/160603176 and https://www.pivotaltracker.com/story/show/160957250.
This fixes issues arising from service broker plan updates requiring the service broker catalog having the plans in a specific order.
cc @Samze

[x] I have reviewed the contributing guide

[x] I have viewed, signed, and submitted the Contributor License Agreement

[x] I have made this pull request to the master branch

[x] I have run all the unit tests using bundle exec rake

[x] I have run CF Acceptance Tests

[finishes #161013348]


implemented Asc() and Chr() global string functions

There are probably several edge cases I'm missing to match Roku's implementation.

I tested these functions on the Roku.  I noticed Chr() returns an empty string for negative numbers, so I updated the implementation.  I also added some UTF-16 symbols based on my Roku tests.
Roku test code:
    ?asc("a")
    ?asc("\n")
    ?asc("ぇ")
    ?"-----"
    ?chr(12359)
    ?chr(-1)
    ?chr(0)
    ?chr(17)

Output:
 97
 92
 12359

-----
ぇ

?


Fixes issue #2626

Validation of email
Validation of email using firebase, that ensures user to register if the entered email is valid email.
Verification is done by sending a verification email.
Prevent from unauthorized access.
Fixes:  #2626
Type of PR

[X] Bug fix
[X] Feature enhancement

Screenshots / videos (if applicable)
https://drive.google.com/file/d/1tnfg5IKbvVBKC21CqrVjr6G0S2whp6Fl/view?usp=drive_link
https://drive.google.com/file/d/1E13-ARQJYc4noBjr1LNsONdm0cv4G-9q/view?usp=drive_link
Checklist:

[X] I have made this change from my own.
[X] I have taken help from some online resources.
[X] My code follows the style guidelines of this project.
[X] I have performed a self-review of my own code.
[X] My changes generate no new warnings.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers and screenshots after making the changes.

@huamanraj @anuragverma108
Kindly review this PR, also assign labels.
Thank you.

good work @Bhattu-Anitha-07 !!

Thankyou @huamanraj
Will contribute more.


Further clarify proofs of invalid erasure coding

Summary
The node types section only states who (which node type) is able to generate proofs of invalid erasure coding. Nowhere is explained what happens after generating them. This leaves a lot of room for interpretation. Who should care about those proofs and how will they be propagated (to who)?

Consumers of fraud proofs would be anyone that just does DAS. I guess that could be made more explicit.

Also, do they trigger slashable events? If yes, who will be slashed?

In terms of what penalities fraud proofs are associated with, that's more of a consensus/evidence concern.

Action Items
These should be separate issues that should be handled successively:

[ ] specify the data structure for these fraud proofs
[ ] specify the flow of events and the underlying assumptions

[ ] clarify grace period to light clients to wait for erasure coding fraud proofs and implications for light clients (wait for fraud proofs?)
[ ] specify penalties / slashing (if any)

related issue about evidence types: https://github.com/lazyledger/lazyledger-specs/issues/23
also related: celestiaorg/celestia-specs#110

Do I understand correctly that this is just a spec/docs issue?

yes


Remove adobe/brackets since it is deprecated

Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/main/CONTRIBUTING.md.
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[x] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288, size <= 75 kB)
[x] Content (and my changes are in index.md)

Explanation
Remove adobe/brackets since it is deprecated and not recommended to use.

I think we'll pass on this since we don't usually remove entries for these reasons. Moreover, while adobe/brackets is indeed archived, it is still a valuable resource and has over 33.5k stars and 8k forks.

I think we'll pass on this since we don't usually remove entries for these reasons. Moreover, while adobe/brackets is indeed archived, it is still a valuable resource and has over 33.5k stars and 8k forks.

Makes sense to me, thanks for the review!


Dynamiclly setup diagnostic settings to support standard app-service SKU

Resolves #2396
What is being addressed
Some of the diagnostic settings we're turning on weren't compatible with the standard app service plan SKU
How is this addressed

Read the application diagnostic options in runtime and turn on what is available.

/test-extended

/test-extended

/test-extended


feat(runtests, tests/, verification/): create view for sending verifi…

…cation and tests

LGTM ⚓


move the doc from containerd/contaienrd to contaienrd/containerd.io

Can I move the doc from containerd/contaienrd to contaienrd/containerd.io？I find some docs can be shared.

Yes, appreciated.
This was also discussed in https://github.com/containerd/containerd.io/issues/80 but got stall

I actually want to have docs in containerd/containerd to keep them versioned, like https://www.envoyproxy.io/docs.

Closing as a duplicate of #80


Using WebEncoders' Base64Url encode/decode functionality

@kichalla,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

bf685de16be9949d67e93cc058ef4393f005756b


[front] chore: Add managed folders in nav sidebar

fixes: https://github.com/dust-tt/tasks/issues/1243
Description
Add managed folders in nav sidebar.

Update message for empty folders.
Risk
None
Deploy Plan
front

What's the behavior if we overflow the width?

It definitely has to work for all connections properly to be shippable.
Does it support databases and pages with children?

It definitely has to work for all connections properly to be shippable.
Does it support databases and pages with children?

It works the same way, we just have to define which type can have children - for now i did only "folders" but we'll needto add pages (and databases ?) for notion.

What's the behavior if we overflow the width?

There's no scrollbar, and an ellipsis. If the indentation is too important, the title can get unreadable. But you need to have a lot of depth. This could be improved in sparkle in another pr imo.

It definitely has to work for all connections properly to be shippable.
Does it support databases and pages with children?

It works the same way, we just have to define which type can have children - for now i did only "folders" but we'll needto add pages (and databases ?) for notion.

Fixed to support all expandable nodes

updates :

don't preload children for all items in tree
allows to pass swr params
simplified/unified swr key format for content-nodes


Instability in 3D diffusion Model training

We are training a 3D diffusion model on medical data using this library and facing some instabilities during training. More in detail: The image quality stagnates/decreases after 80+ hours of training and the images are still noisy, the loss curve doesn’t decrease anymore. Now taking the assumption that the model is stuck in a local minima, we started to increase the learning rate as soon as we encounter this behavior. However, we are wondering if other people encountered similar instabilities and/or if you have ideas on how to deal with it? We’re also experimenting with batch size (max 2 due to 3D), channel size (96 or lower due to 3D), the Unet Architecture itself, with or without Variance, and testing different learning rates (currently starting at lr-6). Any suggestions or ideas are very much appreciated!

I'm also working on 3D diffusion models, can you add a contact? My email address is<EMAIL_ADDRESS>


Give possibility to select CSV columns

There is a great Birthday Reminder app (https://birthday-calendar.app/) but it expects data to be in the format of:
Name,Date where Date could be either yyyy-MM-dd or MM-dd (when the year is null), while on the other hand - your Plugin exports CSV in the format of:
"Name","Year","Month","Day","Link to Profile" (where the missing year is explicitly represened as string "null").
It would be great if you allow to select which coulumns to output in the CSV

You can always update the downloaded CSV the way you like.


Additional data validation for Rack model

Adds additional validation and testing for the Rack model.

These were written with #1136 and #1579 in mind but does not fix them.