pkg/sensors: expose policy status through metrics and tetra

This changes the behavior of the agent relatively to "impossible to load" tracing polices.
First of all, we apply a first validation on the TracingPolicy custom resource, using YAML kubebuilder validation fields and defaults, those are applied whether Tetragon runs along the Kubernetes API or without, in standalone. In the case it runs along the Kubernetes API, it never sees the malformed custom resource as it is parsed by the Kubernetes API. In the case it runs without the Kubernetes API, we import the code that does the parsing and do the same at an early stage in our gRPC API.
The issue is, that the validation we can perform on the YAML is limited and there are more situations in which a syntactically valid TracingPolicy cannot load on any Tetragon agents or just some nodes (in case the underlying kernel is different and Tetragon cannot provide the same functionalities). This step is performed after we load the new policy and is deeply tied to the loading of the BPF collections.
Before this PR, the only way to realize an applied (as in kubectl apply) TracingPolicy failed to load was to watch for all the Tetragon agent logs and search for error messages. Now a user could aggregate the metrics and check for new gauges:
# HELP tetragon_tracingpolicy_loaded The number of loaded tracing policy by status.
# TYPE tetragon_tracingpolicy_loaded gauge
tetragon_tracingpolicy_loaded{status="disabled"} 0
tetragon_tracingpolicy_loaded{status="enabled"} 1
tetragon_tracingpolicy_loaded{status="error"} 0
tetragon_tracingpolicy_loaded{status="load_error"} 1

Or use tetra tracingpolicy list (or short tetra tp list), with text output revamped from this PR:
ID   NAME           ENABLED   FILTERID   NAMESPACE   SENSORS        LOADERROR   ERROR
1    invalid        false     0          (global)                   true        false
2    block-binary   true      0          (global)    gkp-sensor-1   false       false

And maybe use tetra tp list -o json for full error message:
{"policies":[{"id":"1","name":"invalid","load_error":"policy handler 'tracing' failed loading policy 'invalid': tracing policies with both kprobes and tracepoints are not currently supported"},{"id":"2","name":"block-binary","sensors":["gkp-sensor-1"],"enabled":true}]}

So using tetra on concerned hosts, or checking the aggregated metrics and seeking for the error message in the logs should help to troubleshoot a bad TracingPolicy. The next step would be to standardize the error messages in the logs to make them easy to search.

Quick review from the UI stuff first:
ID   NAME           ENABLED   FILTERID   NAMESPACE   SENSORS        LOADERROR   ERROR
1    invalid        false     0          (global)                   true        false
2    block-binary   true      0          (global)    gkp-sensor-1   false       false

The ID is ok maybe! why do you have to print it? is this useful or used somewhere?

I just kept the fields that were printed before, but indeed for now it's only used internally but I think it could be useful, it would be nice to keep a map[int]string to let the user use the name or the id indifferently. Most of the time it's just easier to type 1 instead the name and that would be a nice QoL feature for tetra. Not a huge deal, but that could be a good-first-issue.
Similarly, I'm not sure displaying the filterID is extremely useful, but it was there so not sure I should remove it. We can discuss that but this can be part of another PR I think as I just wanted to make the human output readable and add the status thingie (see next answer paragraph).
We should also document those fields in tetra, maybe replicating the doc from the gRPC.

Also the LOADERROR and ERROR for users are the same, what's the difference? then also they are boolean, are we sure we may not have many errors of the same tracing policy 'block-binary'? after load unload during the uptime of Tetragon? I would just not use boolean here, and have it as a string at least in the doc, this way we can extend later! I would remove LOADERROR and ERROR and put something like ACTIVE.
So that ACTIVE then can be: active, failed or what ever state in the future. Then if you want more details about the tracing policy in question you have to do tetra tp $command $tracingpolicy_name in question.

I think I agree and I will just replicate what we have in the metrics with the STATUS={enabled,disabled,load_error,error}. This presentation is not great you are right!

tetra must present a good summary that tells users everything and should not follow gRPC that is developer oriented.
Also keep in mind we will certainly have more fields in the future, like was this autoloaded or was it insert during runtime? etc, so would try to keep some space as mush as possible and just put what we think is really useful ;-)

I would say for this it's not a huge deal if we later break -o text by removing/adding fields as people should use -o json if they want something consistent for scripting but I understand the argument.

All right I completely rewrote this PR and lost myself in the rebases. I'll add some unit tests tomorrow, fix the linter issue and potential test break, and ship this. I now integrated the state field in the TracingPolicyStatus to have an explicit state machine. I noticed that in theory, the error state is impossible (only load error).

would love to get an ack before I rebase to avoid multiple rebases :)


Provide scaladoc in inspections

@kiendang Thanks to you for having brought the idea and worked on it in a first time! I’m really glad I’ve finally been able to have time to push it over the finish line

May I know how to try this out?
I tried a launcher both from source
./mill launcher

and release
coursier bootstrap --standalone almond:0.13.4 --scala 2.13 --default=true --sources -o almond213 -f

(without metabrowse)
but scaladoc didn't show. With the release launcher the kernel also crashed when I tried shift-tabbing.


how can i validate positive integers including 0?

I can't get 0 to pass.

never mind, forgot to parseInt it.

I think that we need that feature and also negative rule.
For example;
import { validations } from 'indicative/validator'

const rules = {
  amount: 'number|positive',
  expense: 'number|negative'
}

They can be very cool features. What do you think, @thetutlage?


Add some missing options to merge

There are a few handy merge flags that were not covered by the options.

Thanks!


[Defect] Memory leak in memcached.c:7757

Our tool Pinpoint has found a memory leak defect in memcachd.c. The screenshots illustrate the detailed program steps that can trigger this memory leak defect.
Description:
The memory allocated on line 7676 is stored to pointer temp_portnumber_filename. If the fopen call fails on line 7681, which makes the pointer portnumber_file to be nullptr. In this case, the free call on line 7713 will be skipped and the memory leaked.

Gang
Sourcebrella & HKUST

y

fixed in next. another non-issue, since that code is only executed from a specific test or two, and executes once in startup.

went out in 1.5.6


Don't create an issue for issues that are already merged

Currently, chetsumi creates an issue for every item in the RSS feed, even those that are already merged in. For example: https://github.com/reactjs/ja.reactjs.org/issues?q=is%3Aissue+is%3Aclosed
All the [Doc] issues generated by che-tsumi are for commits that already existed when the repo was branched.
You can check that a commit already exists like I did here in my fork: https://github.com/tesseralis/che-tsumi/blob/master/lib/repository.js#L80

Nice feature😍
I'm thinking abount separating lib folder from che-tsumi and creating che-tsumi core.
After I do that, feel free to make a PR when you add a  new feature!

Will do! ^_^


Support rust code in folder within repo root

I went to see if I could grab a deps.rs badge for a project of mine (https://github.com/Cldfire/minecraft-status) and it appears that currently there's no way for me to tell deps.rs that the rust code is inside of the rust folder, and not at the repo root.
(See https://deps.rs/repo/github/cldfire/minecraft-status)

Yes, this is something that we cannot handle at the moment. I could imagine that we add a configuration file that gets placed in the repository root to define things like the path to the crate root. Alternatively we could tweak the URL to have something like https://deps.rs/repo/github/cldfire/minecraft-status/path/[...], which is probably the more elegant solution.

Yes, this is something that we cannot handle at the moment. I could imagine that we add a configuration file that gets placed in the repository root to define things like the path to the crate root. Alternatively we could tweak the URL to have something like https://deps.rs/repo/github/cldfire/minecraft-status/path/[...], which is probably the more elegant solution.


Bubble up exit codes from run_with_retcodes instead of exiting directly

…d of calling sys.exit inside run_with_retcodes

Description

See here for background https://groups.google.com/d/msg/luigi-user/Q2VxlBEFt2o/122V3R1lAQAJ
Changes retcodes.run_with_retcodes() and cmdline.luigi_run() such that the exit code determined in run_with_retcodes() is returned to luigi_run(), and then returned by luigi_run() to its caller (typically the "luigi" script file). As a result, the "luigi" script should return the same values it does today, but that value is now recoverable from luigi_run() if a user has written their own invocation wrapper rather than use the provided "luigi" script.
The net result for luigi programs that are invoked with the "luigi" script should be no change, the same codes will be returned.
Motivation and Context

I'm currently working on several large (thousands of tasks) luigi-based workflows which need to perform setup (teardown) steps before (after) luigi runs their tasks. The need for setup code means I can't make use of the "luigi" script, and because the current implementation of run_with_retcodes calls sys.exit() directly, running teardown code is difficult, and mapping luigi's return codes to a set of return codes that work for me and my calling environment is very-difficult-bordering-on-impossible.
Also, calling sys.exit() from multiple locations deep in the call stack is, I believe, not generally regarded as a good practice.
Have you tested this? If so, how?

I've been running one large job with this change applied to luigi 2.7.1 and haven't had any issues.
The flake8 and py27-nonhdfs tox suites fail, but they also fail on master, so I don't know what to make of that. I ran test/cmdline_test.py by itself and it runs the same (18 failed, 15 passed) as before my change, but it's worth noting that while several tests in that file check for a return code of 0, none check for return codes other than 0.

Can you also update documentation as well as the tests?
Come to think about it, sys.exit() isn't as bad as it would be in other languages as you can easily capture the exception. However, given that we're talking about a scheduler, I guess we shouldn't consider failures to be exceptional. :)


Mono lib is not found while compiling html build

Godot version
3.5.1 stable
System information
win 10 gtx1650 ryzen5 3550h
Issue description

I can build windows mono editor and export template however it is not possible to build html template with mono.

It wants to reach  mono-2.0-sgen.a but I'm on windows10

I print the file it wants, you can see on above powershell screenshot
Steps to reproduce
To console:
emsdk active latest
emsdk_env.bat
scons p=javascript tools=no module_mono_enabled=yes mono_glue=yes -j 7 mono_prefix="C:/Program Files/Mono"
I can already build windows mono edition without any issue even without mono_prefix
Minimal reproduction project
No response

sorry it was my mistake. I had not included mono libs to c/program files/mono. now I can compile html with mono
the lib: https://github.com/godotengine/godot-mono-builds/releases


Serverside Version

Hello,
I'm loving the potential of this library, but I'm finding it difficult to use only on the client side.  Do you have plans to release a server side version?

The generate function should already work on the server, if that's all you're interested in. If you want to generate SVGs server side, that is not supported now. You could try using jsdom to render it to a fake <svg> element and extract it from that... I'm not sure if that would work.
I could also imagine another API like renderToSVGString(face) that just returns the actual SVG file. I don't have any plans to work on that because I don't need it personally, but I'd be open to a PR if you or anyone else wants to work on it :)

Hey @dumbmatter - I decided to give this a shot, and might have a working POC. It's still not "done", and would love some of your thoughts in my PR below. I did this as a fork from yours, and would need to think about how to merge it into your repo (if you like it)
https://github.com/tomkennedy22/facesjs/pull/2

Hey @dumbmatter - I decided to give this a shot, and might have a working POC. It's still not "done", and would love some of your thoughts in my PR below. I did this as a fork from yours, and would need to think about how to merge it into your repo (if you like it)
tomkennedy22#2

JK - I figured out how to PR directly to your repo. Feel free to give feedback, changes, etc. Thanks!

@tomkennedy22 there is also another PR #28 which was actually updated a few weeks ago (sorry I didn't notice @gurushida but thanks for replying to my comments!). Can you take a look at that and see if it would work for you too, or if you have any comments on it? The main advantage of #28 compares to yours is it has no changes to the current client-side code (such as display.js), meaning that the bundle size in the browser will not be increased by adding this feature.

Version 4 includes a faceToSvgString function you can use to export faces as SVGs from a Node.js script, as well as a CLI program you can use for the same purpose. The README has more details.


[SPARK-42585][CONNECT] Streaming of local relations

What changes were proposed in this pull request?
In the PR, I propose to transfer a local relation to the server in streaming way when it exceeds some size which is defined by the SQL config spark.sql.session.localRelationCacheThreshold. The config value is 64MB by default. In particular:

The client applies the sha256 function over the arrow form of the local relation;
It checks presents of the relation at the server side by sending the relation hash to the server;
If the server doesn't have the local relation, the client transfers the local relation as an artefact with the name cache/<sha256>;
As soon as the relation has presented at the server already, or transferred recently, the client transform the logical plan by replacing the LocalRelation node by CachedLocalRelation with the hash.
On another hand, the server converts CachedLocalRelation back to LocalRelation by retrieving the relation body from the local cache.

Details of the implementation
The client sends new command ArtifactStatusesRequest to check either the local relation is cached at the server or not. New command comes via new RPC endpoint ArtifactStatus. And the server answers by new message ArtifactStatusesResponse, see base.proto.
The client transfers serialized (in avro) body of local relation and its schema via the RPC endpoint AddArtifacts. On another hand, the server stores the received artifact in the block manager using the id CacheId. The last one has 3 parts:

userId - the identifier of the user that created the local relation,
sessionId - the identifier of the session which the relation belongs to,
hash - a sha-256 hash over relation body.

See SparkConnectArtifactManager.addArtifact().
The current query is blocked till the local relation is cached at the server side.
When the server receives the query, it retrieves userId, sessionId and hash from CachedLocalRelation, and gets the local relation data from the block manager. See SparkConnectPlanner.transformCachedLocalRelation().
The occupied blocks at the block manager are removed when an user session is invalidated in userSessionMapping. See SparkConnectService.RemoveSessionListener and BlockManager.removeCache()`.
Why are the changes needed?
To allow creating a dataframe from a large local collection. spark.createDataFrame(...) fails with the following error w/o the changes:
23/04/21 20:32:20 WARN NettyServerStream: Exception processing message
org.sparkproject.connect.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: gRPC message exceeds maximum size 134217728: 268435456
	at org.sparkproject.connect.grpc.Status.asRuntimeException(Status.java:526)

Does this PR introduce any user-facing change?
No. The changes extend the existing proto API.
How was this patch tested?
By running the new tests:
$ build/sbt "test:testOnly *.ArtifactManagerSuite"
$ build/sbt "test:testOnly *.ClientE2ETestSuite"
$ build/sbt "test:testOnly *.ArtifactStatusesHandlerSuite"

@grundprinzip @hvanhovell @zhengruifeng @HyukjinKwon Could you review this PR, please.

Are the Python changes done in a follow up?

Are the Python changes done in a follow up?

Yep, in a separate PR.

Merged to master.


request

Can you add windows functionality or just straight up port to windows?

Actually we use <sys/socket.h> for all the methods. But the core of the communication for the http request was made with sys/socket and with <winsock2.h>. So actually we can't make a windows version because the attack methods wasn't compatible with windows. The first real problem with windows is windows defender.

Actually we use <sys/socket.h> for all the methods. But the core of the communication for the http request was made with sys/socket and with <winsock2.h>. So actually we can't make a windows version because the attack methods wasn't compatible with windows. The first real problem with windows is windows defender.

You could re-write them to support windows or make a port to windows also for windows defender you would just have to encrypt your payload

I haven't really the time to make a windows version actually. But maybe in the futur


No typescript definitions for version 2

Typescript definitions were present for version 1 (as of https://github.com/react-tools/react-move/pull/8) but are now gone.
Originally called out in https://github.com/react-tools/react-move/issues/5. But I'd like to re-open for the new version.

Hey.  I don't use typescript but it would be nice to support it.  You want to do a PR for this?

I don’t know when I will get around to it, but I’ll leave the issue open and someone else can pick it up if they beat me to it.

Released Typescript support in 2.4.0!  Let me know if there are any issues.

seeing from the example code provided on the site TS issues with the jsx style attribute. had to break out the any escape hatch. any ideas?


Fix xrdp incompatible Ubuntu 18.04.2 clean install

Intro
I installed Ubuntu 18.04.2 minimal in Windows 10 Pro 1903 Hyper-V, but can't connect to enhanced session mode.
Thanks @RainCat1998, this issue solved the problem. https://github.com/Microsoft/linux-vm-tools/issues/76#issuecomment-481502084
I just copied ubuntu/18.04/install.sh into ubuntu/18.04.2/install.sh and fixed it.
Tested

Ubuntu 18.04.2 minimal

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Wind4 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Maybe use apt install -y xorg-video-abi-23 xserver-xorg-core better.


image previews

The only thing keeping me from switching from fff to shfm is image previews. Is this possible?

Image previews are bloat

I have doubts that this can be accomplished with POSIX shell, but I think this can be implemented using tmux, a special tmux.conf and a wrapper script. I'll give it a shot and reply to this issue in case anyone is interested.

I've noticed that w3mimagedisplay doesn't play very nice with allacritty anyway, so I've actually requested that fff use ueberzug for image previews instead. I wonder if it can be implemented in shfm ? I suppose it is a dependency that some people may not want but it can be optional i guess

Outta scope.

I have doubts that this can be accomplished with POSIX shell, but I think this can be implemented using tmux, a special tmux.conf and a wrapper script. I'll give it a shot and reply to this issue in case anyone is interested.

Did you have any luck?

Outta scope.

No worries. What about for fff though?


Issue not found when destructuring props in stateles React components

I don't know if it is an issue or it is working as expected.
But I wonder why in some cases flow shows issue for no annotation in destructured objects in stateless React components. There's an example of a component where the annotation is needed. Otherwise flow shows an issue:
const DataRow = ({
  data,
  columns,
  onClick,
  onDelete
}) => (...);

Flow displays the error:
app/components/ui/DataRow.js:29
 29: const DataRow = ({
                      ^ destructuring. Missing annotation

It's okay for this case. But in certain components flow does not throw the error. An example:
const HomeButton  = ({
  text,
  onClick
}) => (...);

For this component flow does not display errors.
Anyone knows why? For me, apparently, its exactly the same case.
Thank you.

Can you provide an example that reproduces on https://flowtype.org/try/? Your first example shows no error when I copy and paste it there.

Hmm. I tried the code in the try it editor and the first example shows no errors as well. Well, I'm not sure what to show you. But I will fill you in some screenshots. Look:
Here's my terminal in my project folder when I have no annotation:

In atom my linter screams as well:

If I put the decorator:

In atom it disappears too:

In the case of the HomeButton, no issues are found with no decorator.

My .flowconfig is okay too:
[ignore]
.*/node_modules/fbjs/.*
.*/app/main.js
.*/app/dist/.*
.*/release/.*
.*/git/.*

[include]

[libs]

[options]
esproposal.class_static_fields=enable
esproposal.class_instance_fields=enable
esproposal.export_star_as=enable
module.name_mapper.extension='css' -> '<PROJECT_ROOT>/flow/CSSModule.js.flow'
module.name_mapper.extension='styl' -> '<PROJECT_ROOT>/flow/CSSModule.js.flow'
module.name_mapper.extension='png' -> '<PROJECT_ROOT>/flow/WebpackAsset.js.flow'
module.name_mapper.extension='jpg' -> '<PROJECT_ROOT>/flow/WebpackAsset.js.flow'
suppress_comment=\\(.\\|\n\\)*\\$FlowFixMe
suppress_comment=\\(.\\|\n\\)*\\$FlowIssue

I know we could not simulate it, but I still wonder why this is happening in my case.

It happens when I export a functional component.

The type annotation is needed for the argument of any exported function. Pretty sure that's the only issue here and looks like flow is working as exoected. Let me know if that isn't the case and we can discuss further.


Rippled response causes failed forward

Rippled responds slowly for the request
{
    "method": "ledger",
    "params": [
        {
            "ledger_index": "validated",
            "accounts": false,
            "full": true,
            "transactions": false,
            "expand": false,
            "owner_funds": false
        }
    ]
}

which causes failed forward.
Do we need to increase the timeout or give warning for this scenario? @godexsoft

@ximinez @Bronek Any recommendation from your side on this one? 🙇

From https://xrpl.org/ledger.html#request-format

The ledger field is deprecated and may be removed without further notice. The full, accounts, and type fields (admin-only) are also deprecated; the Clio server does not implement these parameters.

The ledger (on Mainnet) is so big that there is no reasonable way to build the full json response before the connection times out, or rippled runs out of memory, or whatever. For that reason, even though full still exists, it is restricted to admin connections - the idea is that it might be useful for testing, or for someone to run on their own server for their own purposes, but it is strongly discouraged.
ledger_data is the replacement, which uses paging markers so that it's not trying to build the whole thing at once.
tl;dr - It's a known issue. Don't try to use it on mainnet.

The previous version of that page included:

| full         | Boolean          | No        | Admin only If true, return full information on the entire ledger. Ignored if you did not specify a ledger version. The default is false. (Equivalent to enabling transactions, accounts, and expand.) The Clio server does not support this field. Caution: On Mainnet, this can be gigabytes worth of data, so the request is likely to time out. |

@ximinez If it's deprecated - that's great. We should remove all mentions of it from Clio and be done. Currently (and in 2.1.0 that just got released), specifying full for the request will forward to rippled. We should remove this by next release. Thanks 🙇

@godexsoft You're welcome!
Though I am curious if clio would have any more success building the full ledger locally. I don't expect it will be, because despite its efficiencies, we're still talking about gigs of json being built in memory.

Please also check that forwarding got some timeout setting.


Crash when trying to reword or amend

Description of the bug
Running git reword or git amend produces the following error output:
The application panicked (crashed).
Message:  A fatal error occurred:
   0: could not create commit signature: failed to parse signature - Signature cannot have an empty name or email; class=Invalid (3)
   1: failed to parse signature - Signature cannot have an empty name or email; class=Invalid (3)

Location:
   git-branchless-lib/src/core/rewrite/execute.rs:728

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Location: git-branchless/src/commands/mod.rs:221

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

For reference, my git config --global user.name is set, but my git config --global user.email is empty. However, even when I set the latter to<EMAIL_ADDRESS>the crash above persisted when calling git amend or git reword as before.
I'm using git-branchless v0.7.1 on top of git v2.30.1, on a mac running OSX 12.1 Monterey.
Expected behavior
I expect git amend|reword to succeed without crashing.
Actual behavior
The program crashed, with the error output provided above.
Version of rustc
This is not a build issue, but 1.69.0-nightly
Automated bug report
Software version
git-branchless 0.7.1
Operating system
macOS 12.1 (Darwin 21.2.0)
Command-line
/usr/local/bin/git-branchless bug-report

Environment variables
SHELL=/bin/bash
EDITOR=vim

Git version
> git version
git version 2.30.1 (Apple Git-130)

Hooks

Show 7 hooks
Hook post-applypatch
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-applypatch "$@"

## END BRANCHLESS CONFIG

Hook post-checkout
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-checkout "$@"

## END BRANCHLESS CONFIG

Hook post-commit
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-commit "$@"

## END BRANCHLESS CONFIG

Hook post-merge
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-merge "$@"

## END BRANCHLESS CONFIG

Hook post-rewrite
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook post-rewrite "$@"

## END BRANCHLESS CONFIG

Hook pre-auto-gc
#!/bin/sh
## START BRANCHLESS CONFIG

git branchless hook pre-auto-gc "$@"

## END BRANCHLESS CONFIG

Hook reference-transaction
#!/bin/sh
## START BRANCHLESS CONFIG

# Avoid canceling the reference transaction in the case that `branchless` fails
# for whatever reason.
git branchless hook reference-transaction "$@" || (
echo 'branchless: Failed to process reference transaction!'
echo 'branchless: Some events (e.g. branch updates) may have been lost.'
echo 'branchless: This is a bug. Please report it.'

O 08c4dfe 7m (main) xxxxxx xxxxxxxxxx
|
@ 9f2f932 6m (redacted-ref-0) xxxxxx xxx xxxx xxxxxx xxxxxx

There are no previous available events.
O 08c4dfe 7m (main) xxxxxx xxxxxxxxxx
|
@ 9f2f932 6m (redacted-ref-0) xxxxxx xxx xxxx xxxxxx xxxxxx

Version of git-branchless
0.7.1
Version of git
2.30.1

Hi @azaslavsky, thanks for reporting. I think this is a limitation in the git2 crate, and arguably in libgit2 itself. In libgit2, it claims that an empty email is invalid:
https://github.com/libgit2/libgit2/blob/abb0b313172d1b4477fe0c6e88102ce4bb8db90c/src/libgit2/signature.c#L93-L96
However, it's obviously possible to create signatures with empty emails. If we were using libgit2 directly, it would probably be possible to bypass the constructor and set the email string ourselves, or perhaps use the function to parse a signature from a buffer. However, the git2 Rust wrappers don't seem to have any workaround (without unsafely interfacing with libgit2 itself).
As a workaround, I recommend that you use git commit --amend to assign a non-empty signature to the commit in question, after which you should be able to use git amend or git reword as desired. I would also recommend that you check out Jujutsu, which has first-class support for empty names and emails and even commit messages, and can be used in a Git repository.
For my own future reference, while I was able to reproduce the issue with manual testing, the following patch did not expose the issue (it somehow successfully amended the commit?):

Patch
From 53affaae2d670f82364c01d4477a0f9ba64f1d0c Mon Sep 17 00:00:00 2001
From: Waleed Khan<EMAIL_ADDRESS>Date: Sat, 22 Apr 2023 14:25:29 -0700
Subject: [PATCH] temp: attempt to create test exposing empty email issue

---
 git-branchless-testing/src/lib.rs  | 23 ++++++++--
 git-branchless/tests/test_amend.rs | 71 +++++++++++++++++++++++++++++-
 2 files changed, 89 insertions(+), 5 deletions(-)

diff --git a/git-branchless-testing/src/lib.rs b/git-branchless-testing/src/lib.rs
index c011cb2f..5f135a48 100644
--- a/git-branchless-testing/src/lib.rs
+++ b/git-branchless-testing/src/lib.rs
@@ -55,6 +55,8 @@ pub struct GitInitOptions {

     /// If `true`, run `git branchless init` as part of initialization process.
     pub run_branchless_init: bool,
+
+    pub configure_signature: bool,
 }

 impl Default for GitInitOptions {
@@ -62,6 +64,7 @@ impl Default for GitInitOptions {
         GitInitOptions {
             make_initial_commit: true,
             run_branchless_init: true,
+            configure_signature: true,
         }
     }
 }
@@ -171,6 +174,9 @@ impl Git {
         let new_path = self.get_path_for_env();
         let envs = vec![
             ("GIT_CONFIG_NOSYSTEM", OsString::from("1")),
+            ("GIT_CONFIG_SYSTEM", OsString::new()), // since Git v2.32.0 https://stackoverflow.com/a/67512433
+            ("GIT_CONFIG_GLOBAL", OsString::new()), // since Git v2.32.0 https://stackoverflow.com/a/67512433
+            ("GIT_ATTR_NOSYSTEM", OsString::from("1")), // mysterious undocumented config option?  https://stackoverflow.com/questions/43881807/how-to-tell-git-to-ignore-global-config/67512433#comment74799506_43882168
             ("GIT_AUTHOR_DATE", date.clone()),
             ("GIT_COMMITTER_DATE", date),
             ("GIT_EDITOR", git_editor),
@@ -390,12 +396,21 @@ then you can only run tests in the main `git-branchless` and \
     /// with it.
     #[instrument]
     pub fn init_repo_with_options(&self, options: &GitInitOptions) -> eyre::Result<()> {
+        let GitInitOptions {
+            make_initial_commit,
+            run_branchless_init,
+            configure_signature,
+        } = options;
+
         self.run(&["init"])?;
-        self.run(&["config", "user.name", DUMMY_NAME])?;
-        self.run(&["config", "user.email", DUMMY_EMAIL])?;
         self.run(&["config", "core.abbrev", "7"])?;

-        if options.make_initial_commit {
+        if *configure_signature {
+            self.run(&["config", "user.name", DUMMY_NAME])?;
+            self.run(&["config", "user.email", DUMMY_EMAIL])?;
+        }
+
+        if *make_initial_commit {
             self.commit_file("initial", 0)?;
         }

@@ -415,7 +430,7 @@ then you can only run tests in the main `git-branchless` and \
         // ```
         self.run(&["config", "core.autocrlf", "false"])?;

-        if options.run_branchless_init {
+        if *run_branchless_init {
             self.branchless("init", &[])?;
         }

diff --git a/git-branchless/tests/test_amend.rs b/git-branchless/tests/test_amend.rs
index 8c8b6fc6..608f0a24 100644
--- a/git-branchless/tests/test_amend.rs
+++ b/git-branchless/tests/test_amend.rs
@@ -1,4 +1,6 @@
-use git_branchless_testing::{make_git, remove_rebase_lines, trim_lines, GitRunOptions};
+use git_branchless_testing::{
+    make_git, remove_rebase_lines, trim_lines, GitInitOptions, GitRunOptions,
+};

 #[test]
 fn test_amend_with_children() -> eyre::Result<()> {
@@ -1135,3 +1137,70 @@ fn test_amend_move_detached_branch() -> eyre::Result<()> {

     Ok(())
 }
+
+#[test]
+fn test_amend_empty_email() -> eyre::Result<()> {
+    let git = make_git()?;
+    git.init_repo_with_options(&GitInitOptions {
+        configure_signature: false,
+        ..Default::default()
+    })?;
+
+    git.run(&["config", "user.name", "Foo Bar"])?;
+    git.run(&["config", "user.email", ""])?;
+    git.detach_head()?;
+    git.commit_file("test1", 1)?;
+
+    {
+        let (stdout, _stderr) = git.run(&["show"])?;
+        insta::assert_snapshot!(stdout, @r###"
+        commit 2823d3098a992b872a6fd551eeb10fc743e8e39d
+        Author: Foo Bar <>
+        Date:   Thu Oct 29 12:34:56 2020 -0100
+
+            create test1.txt
+
+        diff --git a/test1.txt b/test1.txt
+        new file mode 100644
+        index 0000000..7432a8f
+        --- /dev/null
+        +++ b/test1.txt
+        @@ -0,0 +1 @@
+        +test1 contents
+        "###);
+    }
+
+    git.write_file_txt("test1", "updated contents\n")?;
+    {
+        let (stdout, stderr) = git.branchless("amend", &[])?;
+        insta::assert_snapshot!(stderr, @r###"
+        branchless: creating working copy snapshot
+        branchless: processing 1 update: ref HEAD
+        "###);
+        insta::assert_snapshot!(stdout, @r###"
+        branchless: running command: <git-executable> reset 937a25b6ca80c7dc92a179befb36e39a8ecfa8bf
+        Amended with 1 uncommitted change.
+        "###);
+    }
+
+    {
+        let (stdout, _stderr) = git.run(&["show"])?;
+        insta::assert_snapshot!(stdout, @r###"
+        commit 937a25b6ca80c7dc92a179befb36e39a8ecfa8bf
+        Author: Foo Bar <>
+        Date:   Thu Oct 29 12:34:56 2020 -0100
+
+            create test1.txt
+
+        diff --git a/test1.txt b/test1.txt
+        new file mode 100644
+        index 0000000..27e2fc9
+        --- /dev/null
+        +++ b/test1.txt
+        @@ -0,0 +1 @@
+        +updated contents
+        "###);
+    }
+
+    Ok(())
+}
--
2.40.0

Hmm, I tried your suggestion (first commit using the old-school git commit --amend, then try git amend/reword, but the latter commands till fail in the same way they did before? It seems like the issue is with trying to generate a new signature when the commit message or contents change, though this is just me speculating. I'll try to build git-branchless from source with some print debug statements to see what could be the issue on my end.

You may also need to pass --reset-author or similar to fully reset the signature. Make sure both the author and committer signatures have been updated.


Add weightlessness status effect.

Fixes https://github.com/space-wizards/space-station-14/issues/2378
placeholder texture, obv

Huh, it's more complicated than I thought, but yeah it should probably be done through an event.

yeah, i figured. i assumed an event  like 'OnWeightlessChanged' already  existed or something, but it didn't.

@PaulRitter i implemented your changes and am getting a key not found error when the client connects to server and presumably tries to handle the weightlesscomponent
An unhandled exception of type 'System.Collections.Generic.KeyNotFoundException' occurred in System.Private.CoreLib.dll: 'The given key 'Content.Shared.GameObjects.Components.Mobs.SharedWeightlessStatusComponent' was not present in the dictionary.'
   at System.ThrowHelper.ThrowKeyNotFoundException[T](T key)
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Robust.Shared.GameObjects.ComponentManager.TryGetComponent(EntityUid uid, Type type, IComponent& component) in E:\edev\ss14\RobustToolbox\Robust.Shared\GameObjects\ComponentManager.cs:line 397
   at Robust.Shared.GameObjects.ComponentManager.TryGetComponent[T](EntityUid uid, T& component) in E:\edev\ss14\RobustToolbox\Robust.Shared\GameObjects\ComponentManager.cs:line 381
   at Robust.Shared.GameObjects.Entity.TryGetComponent[T](T& component) in E:\edev\ss14\RobustToolbox\Robust.Shared\GameObjects\Entity.cs:line 298
   at Content.Shared.GameObjects.Components.Movement.GravityExtensions.IsWeightless(IEntity entity, IPhysicsManager physicsManager) in E:\edev\ss14\Content.Shared\GameObjects\Components\Movement\MovementIgnoreGravityComponent.cs:line 25
   at Content.Shared.GameObjects.EntitySystems.SharedMoverSystem.UpdateKinematics(ITransformComponent transform, IMoverComponent mover, IPhysicsComponent physics) in E:\edev\ss14\Content.Shared\GameObjects\EntitySystems\SharedMoverSystem.cs:line 59
   at Content.Client.GameObjects.EntitySystems.MoverSystem.FrameUpdate(Single frameTime) in E:\edev\ss14\Content.Client\GameObjects\EntitySystems\MoverSystem.cs:line 35
   at Content.Client.GameObjects.EntitySystems.MoverSystem.Update(Single frameTime) in E:\edev\ss14\Content.Client\GameObjects\EntitySystems\MoverSystem.cs:line 40
   at Robust.Shared.GameObjects.EntitySystemManager.Update(Single frameTime) in E:\edev\ss14\RobustToolbox\Robust.Shared\GameObjects\EntitySystemManager.cs:line 250
   at Robust.Client.GameStates.ClientGameStateManager.ApplyGameState() in E:\edev\ss14\RobustToolbox\Robust.Client\GameStates\ClientGameStateManager.cs:line 301
   at Robust.Client.GameController.Tick(FrameEventArgs frameEventArgs) in E:\edev\ss14\RobustToolbox\Robust.Client\GameController.cs:line 272
   at Robust.Client.GameController.<MainLoop>b__65_0(Object sender, FrameEventArgs args) in E:\edev\ss14\RobustToolbox\Robust.Client\GameController\GameController.Standalone.cs:line 84
   at Robust.Shared.Timing.GameLoop.Run() in E:\edev\ss14\RobustToolbox\Robust.Shared\Timing\GameLoop.cs:line 200
   at Robust.Client.GameController.MainLoop(DisplayMode mode) in E:\edev\ss14\RobustToolbox\Robust.Client\GameController\GameController.Standalone.cs:line 113
   at Robust.Client.GameController.ParsedMain(CommandLineArgs args, Boolean contentStart) in E:\edev\ss14\RobustToolbox\Robust.Client\GameController\GameController.Standalone.cs:line 59
   at Robust.Client.GameController.Start(String[] args, Boolean contentStart) in E:\edev\ss14\RobustToolbox\Robust.Client\GameController\GameController.Standalone.cs:line 35
   at Robust.Client.GameController.Main(String[] args) in E:\edev\ss14\RobustToolbox\Robust.Client\GameController\GameController.Standalone.cs:line 21```

Maybe due to a missing [Serializable, NetSerializable] somewhere?

You used a ComponentReference if you're trying to get the shared one right?

You used a ComponentReference if you're trying to get the shared one right?

in the derived content.server class? yes.

And the shared class is abstract?

And the shared class is abstract?

namespace Content.Shared.GameObjects.Components.Mobs
{
    public abstract class SharedWeightlessStatusComponent : Component
    {

I just had a look and there's no component on the client, only on the server.

I just had a look and there's no component on the client, only on the server.

Yeah i tried adding it to the ignore list, and also tried making a clientside one and it still threw the error. I'll try again though.

You'll need to make a client-side one and componentreference shared for it to not throw.

You'll need to make a client-side one and componentreference shared for it to not throw.

alright thankya

Looking at what you've done so far it'd be better if instead of calling UpdateStatus directly it either sent a message over the EventBus or called the entity's SendMessage method (probably the former?) so that way if anything else also needed to check for Weightlessness they could do it.
This would also mean you could just make a system for weightlessness that subscribes to the message and updates the entity's StatusEffect is applicable which would mean less memory usage (fewer components in use).

well, it works and i dont really feel like doing all that.

nah just kidding lol

message over the EventBu

how will i do that from Content.Shared ?

If you already have the entity you can do like Owner.EntityManager.EventBus.RaiseEvent(EventSource.Local, new WeightlessChangeMessage(value)) or the likes (you'd need to make a WeightlessChangeMessage : EntitySystemMessage)
Then on the system you could do SubscribeLocalEvent(Method that handles it here) and just have that check if the entity has a status effect and if it does update it.

@metalgearsloth thank you for the guidance on this!

@metalgearsloth tell me what you think now. thankya again

@metalgearsloth tell me what you think now. thankya again

Looks mostly good, still has the sharedweightless component which can be removed (same with on the entity), rest looks good!

@metalgearsloth tell me what you think now. thankya again

Looks mostly good, still has the sharedweightless component which can be removed (same with on the entity), rest looks good!

oh damn. i keep thinking i need the components 🤦

also @metalgearsloth. what do you mean by

(same with on the entity),

?

Under human.yml it still has the reference to WeightlessStatus

gotchya


Delete old example

Difficult to maintain a simple example for now. New Relations example notebook can be written later.

Makes sense


fix: Add cron trigger

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


Error and xmake freeze during project configuration with glfw package: cannot remove directory Unknown Error (145)

Xmake Version
2.9.5
Operating System Version and Architecture
Windows 11 23H2 22631.4037
Describe Bug
5/5 reproduce:

Remove .xamke directory: C:\Users\Y\AppData\Local\.xmake
Configure the project xmake f -p mingw -y and see error:

checking for architecture ... x86_64
checking for mingw directory ... C:\Program Files\mydevtools\MinGW-w64
updating repositories .. ok
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.40.33812
  => download https://github.com/glfw/glfw/archive/refs/tags/3.4.tar.gz .. ok
  => download https://github.com/glfw/glfw/archive/refs/tags/3.4.tar.gz .. ok
  => install glfw#1 3.4 .. failed

cannot remove directory C:\Users\Y\AppData\Local\Temp\.xmake\240915.dir\glfw\release Unknown Error (145)
if you want to get more verbose errors, please see:
  -> C:\Users\Y\AppData\Local\.xmake\cache\packages\2409\g\glfw_1\3.4\installdir.failed\logs\install.txt
  => install glfw 3.4 .. failed

cannot remove directory C:\Users\Y\AppData\Local\Temp\.xmake\240915.dir\glfw\release Unknown Error (145)
if you want to get more verbose errors, please see:
  -> C:\Users\Y\AppData\Local\.xmake\cache\packages\2409\g\glfw\3.4\installdir.failed\logs\install.txt
  => download https://github.com/xmake-mirror/python-windows/releases/download/3.12.3/python-3.12.3.win64.zip .. ok
  => install python 3.12.3 .. ok
  => download https://github.com/Dav1dde/glad/archive/v0.1.36.tar.gz .. ok
  => install glad v0.1.36 .. ok
error: install failed!

Very often the xmake f -p mingw -f hangs in the end at line => install python 3.12.3 .. ok. So, the only way to exit is to press Ctrl+C. It hangs even GitHub Actions for hours, so I need to cancel workflow manually.
Content of C:\Users\Y\AppData\Local\.xmake\cache\packages\2409\g\glfw\3.4\installdir.failed\logs\install.txt:
cannot remove directory C:\Users\Y\AppData\Local\Temp\.xmake\240915.dir\glfw\release Unknown Error (145)

Sometimes I see duplicated error messages. Maybe there is problem with multithreading?
  => install glfw#1 3.4 .. failed

cannot remove directory C:\Users\Y\AppData\Local\Temp\.xmake\240915.dir\glfw\release Unknown Error (145)
if you want to get more verbose errors, please see:
  -> C:\Users\Y\AppData\Local\.xmake\cache\packages\2409\g\glfw_1\3.4\installdir.failed\logs\install.txt
  => install glfw 3.4 .. failed

cannot remove directory C:\Users\Y\AppData\Local\Temp\.xmake\240915.dir\glfw\release Unknown Error (145)
if you want to get more verbose errors, please see:
  -> C:\Users\Y\AppData\Local\.xmake\cache\packages\2409\g\glfw\3.4\installdir.failed\logs\install.txt

Important notes:

If I run xmake f -p mingw -y for the second time - error is gone and configuration finished successfully
Issue is never reproduced if I add -vD or -v or -D options
Issue is reproduced only with mingw profile. With windows profile (msvc) - everything is fine
Sometimes I saw this issue on xmake 2.9.4 too

Expected Behavior
xmake f -p mingw -y finishes successfully.
Project Configuration
add_rules("mode.debug", "mode.release", "plugin.compile_commands.autoupdate", {outputdir = "build"})
set_defaultmode("debug")
set_targetdir("$(buildir)")

add_requires("glfw 3.4", "glad", "imgui v1.91.0", {configs = {glfw_opengl3 = true}})

target("opengl-app")
    add_packages("glfw", "glad", "imgui")
    add_files("main.cpp")

Additional Information and Error Logs
Issue is never reproduced if I add -vD options

try it again. xmake update -s dev

Fixed. Thank you.
Just in case, I still see duplicated  download ... glfw, install glfw#1 3.4 .. ok and install glfw 3.4 .. ok messages, but no errors anymore.
checking for architecture ... x86_64
checking for mingw directory ... C:\Program Files\mydevtools\MinGW-w64
updating repositories .. ok
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.40.33812
  => download https://github.com/glfw/glfw/archive/refs/tags/3.4.tar.gz .. ok
  => download https://github.com/glfw/glfw/archive/refs/tags/3.4.tar.gz .. ok
  => download https://github.com/xmake-mirror/python-windows/releases/download/3.12.3/python-3.12.3.win64.zip .. ok
  => install glfw#1 3.4 .. ok
  => download https://github.com/ocornut/imgui/archive/refs/tags/v1.91.0.tar.gz .. ok
  => install glfw 3.4 .. ok
  => install imgui v1.91.0 .. ok
  => install python 3.12.3 .. ok
  => download https://github.com/Dav1dde/glad/archive/v0.1.36.tar.gz .. ok
  => install glad v0.1.36 .. ok

This is not a bug, you have two different configurations of glfw packages that need to be installed in your project.
add_requires("glfw 3.4", "glad", "imgui v1.91.0", {configs = {glfw_opengl3 = true}})

  -> glfw 3.4 [glfw_opengl3:y]

and from imgui.glfw
  -> glfw#1 3.4 [from:imgui]


Heroku

Please add deploy to heroku

Already added, app.json not added. But you can deploy to heroku.
Steps:

Login to Heroku Account
Create new app
Fork this repository
Connect forked repository to heroku
Add variables


VideoItem/AudioItem startDate

Hold On - still writing this...
Is there an existing similar feature request?

[X] I have searched existing features and found no similar request.

[X] I have browsed the available API and found no way to achieve the use case I described.

Use case description
As a developer integrating Pillarbox I would like to know when a livestream VideoItem and/or AudioItem is going to start.
Background: We would like to create a CountdownView for livestreams that are not available yet.

Acceptance criteria

VideoItem and AudioItem have a new property public let startDate: Date containing the date
`

Proposed solution
No response
Alternatives considered
No response

As discussed with @NicolasBrunnerSRF who closed this issue, SRF apps already have the info. I still added a backlog entry for us to improve the demo and show how we can integrate a countdown or availability date.


[FEATURE REQ] Support single-container access in azure-storage-blob-nio

Is your feature request related to a problem? Please describe.
We are trying to extend an existing NIO-using software product to run in Azure, including using Blob storage as a backing filesystem. Due to the architecture of our larger environment, our application only has access to a single Blob container, not an entire storage account. As far as we can tell we are unable to use the Azure Blob NIO library at all, since we do not have an account-level SAS token.
Describe the solution you'd like
I would like to be able to create an NIO filesystem by passing in a container-level SAS token. This would result in a filesystem that could not perform container-level operations in the storage account.
Describe alternatives you've considered
We considered obtaining access to a storage account rather than a container, but due to the limit on number of storage accounts per region per subscription, this doesn't meet our organization's needs.
Additional context
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Description Added
[x] Expected solution specified

@jgainerdewar Thank you for opening this issue! I think this should be possible as we have in the past enabled support for accessing even a single file. If you have a sas token to a container and use that as your authentication method, do you get an error back?

Thanks for the quick response! I saw single-blob access described in the docs as a possible future feature and assumed it wasn't working yet.
Yes, currently we get a 403 error the says "This request is not authorized to perform this operation." with initial cause "java.io.IOException: There was an error in establishing the existence of container: '". The same SAS token works when connecting to the container in the desktop Storage Explorer app, so I believe the token itself is correct. Maybe there's a different permission that needs to be set on the token when creating it?

Interesting. So when the FileSystem is being loaded, we try to do a head request, and if there's nothing there, a createContainer. If either of those fail, we'll throw with the exception message you're seeing. Since you're getting an auth failure, I suspect you don't have permissions for one of those actions. You'll need read permission for the head request, and, if you're specifying a container that doesn't already exist, you'll need create permissions to create the container

Alright, we know the container already exists (and in our case we can assume it always will), so we'll look into whether we have permission for the head request. We don't expect to have permission to do things like list the blob containers in the storage account, since we only have access to a single container. My colleague @kraefrei will follow up!

@rickle-msft following up from last week, I have verified that we are getting this error even with the read (and create) permission are there through a provided BlobContainerSasPermission object. We are working with an existing container, however I also tried requesting a new container that would need to be created for completeness and we observe the same error. Does this error usually indicate an issue with the permissions on the BlobContainerSasPermission object alone or could this indicate that there are other signature values we are missing?

Can you share a sample sas token you are using (but redact the signature and the names of any resources)? With that I can make some requests on my end and see what's going on.

Sure thing! Here is an example: sv=2021-06-08&spr=https&st=2022-08-09T12%3A42%3A38Z&se=2022-08-09T13%3A57%3A38Z&sr=c&sp=racwdl&sig={signature}

Hi, @kraefrei. Thank you for providing the sample. I was able to verify the behavior you're seeing. It looks like it's because a service sas can't actually grant permission to read properties on a container, which is required for our validation step. There is a way around this, which is to specify the AzureStorageSkipInitialContainerCheck option in your config map. As long as you're confident the container exists, there shouldn't be any issue with skipping the connection check. Please let me know if you have any issues with this

That worked for us! For our use case we should be able to guarantee that the container exists, so we'll use this work around for now.

Glad to hear it! In this case, that option was specifically added to support sas tokens that don't have permissions to perform this check, so it is a supported feature that you should be able to rely on :)


Catch and raise error for incorrectly formatted unit strings (Issue #57)

This addresses https://github.com/Unidata/cftime/issues/57
Previous behaviour:
>>> cftime._cftime._dateparse('days_since_1900-01-01')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "cftime/_cftime.pyx", line 56, in cftime._cftime._dateparse
IndexError: list index out of range

Now
>>> cftime._cftime._dateparse('days_since_1900-01-01')
Traceback (most recent call last):
  File "cftime/_cftime.pyx", line 53, in cftime._cftime._datesplit
    (units, sincestring, remainder) = timestr.split(maxsplit=2)
ValueError: need more than 1 value to unpack

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "cftime/_cftime.pyx", line 68, in cftime._cftime._dateparse
    (units, isostring) = _datesplit(timestr)
  File "cftime/_cftime.pyx", line 55, in cftime._cftime._datesplit
    raise ValueError('Incorrectly formatted CF date-time unit_string')
ValueError: Incorrectly formatted CF date-time unit_string

All instances of using split in the code have been changed to use _datesplit which checks the status of the split and throws the above exception. It also checks for a correct "since" string.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Much more informative error message, thanks @aidanheerdegen


Exclude a package from react-native link

See: https://stackoverflow.com/questions/49851602/how-do-i-exclude-a-package-from-react-native-link
I think this will be useful (and maybe even necessary if some libraries break).

Yes IMHO libraries should defined whether they can be react-native link'ed or not.

Closing in favour of #48


fix change Susucoin Webpages.

I changed the official page to the correct one.

It may be better to return the items of translation to those of bitcoin.

Thank you!


Crash in HTTPMetrics : Attempted to dereference garbage pointer

Bug Report

Q
A

BC Break
no

Version
1.5.2

Summary
It seems that there is still something going on with HTTPMetrics in the 1.5.2 version.
I can't reproduce it since I don't really know what's going on, but our crash report shows a considerable amount of these issues...
FYI, we use the Sentry and NewRelic SDKs and I am not sure if they could interfere with RealHTTP somehow 🤔
OS Version: iOS 15.5 (19F77)
Report Version: 104

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: BUS_NOOP at 0x0000000000000419
Crashed Thread: 1

Application Specific Information:
addObject: > countByEnumeratingWithState:objects:count: > transactionMetrics >
Attempted to dereference garbage pointer 0x419.

Thread 1 Crashed:
0   libobjc.A.dylib                 0x33045f118         objc_retain
1   CFNetwork                       0x302374644         CFURLRequestSetShouldStartSynchronously
2   CFNetwork                       0x30237a400         CFURLCacheCurrentDiskUsage
3   CFNetwork                       0x3023783c8         CFURLRequestSetHTTPRequestBodyParts
4   ZVVOneApp                       0x203193e1c         HTTPMetrics.init (HTTPMetrics.swift:61)
5   ZVVOneApp                       0x203165858         HTTPResponse.init (HTTPResponse.swift:126)
6   ZVVOneApp                       0x203174368         [inlined] HTTPResponse.__allocating_init (HTTPResponse.swift:120)
7   ZVVOneApp                       0x203174368         HTTPDataLoader.completeTask (HTTPDataLoader.swift:434)
8   ZVVOneApp                       0x2031745cc         [inlined] HTTPDataLoader.urlSession (HTTPDataLoader.swift:268)
9   ZVVOneApp                       0x2031745cc         HTTPDataLoader.urlSession (<compiler-generated>:266)
10  NewRelic                        0x107941e28         -[NRURLSessionTaskDelegateBase URLSession:task:didCompleteWithError:] (NRMAURLSessionTaskDelegateBase.m:55)
11  CFNetwork                       0x30234fa74         CFURLRequestCopyHTTPRequestMethod
12  Foundation                      0x3041f43e8         __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__
13  Foundation                      0x304205a9c         -[NSBlockOperation main]
14  Foundation                      0x3041dfad8         __NSOPERATION_IS_INVOKING_MAIN__
15  Foundation                      0x3041f0018         -[NSOperation start]
16  Foundation                      0x3041f34e4         __NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__
17  Foundation                      0x304200cf8         __NSOQSchedule_f
18  libdispatch.dylib               0x300da2044         _dispatch_block_async_invoke2
19  libdispatch.dylib               0x300dc0090         _dispatch_client_callout
20  libdispatch.dylib               0x300d97ab4         _dispatch_continuation_pop$VARIANT$armv81
21  libdispatch.dylib               0x300d971f0         _dispatch_async_redirect_invoke
22  libdispatch.dylib               0x300da462c         _dispatch_root_queue_drain
23  libdispatch.dylib               0x300da4de8         _dispatch_worker_thread2
24  libsystem_pthread.dylib         0x3b7a29dd0         _pthread_wqthread

Metrics may fire after URLSession:task:didCompleteWithError: is called, the delegate may be nil, so it may cause the error.
I've centralized the way HTTPMetrics object is created for a response so it may solve the issue.
Have you tried to reproduce the issue?

@malcommac thanks for your feedback! Unfortunately I can't reproduce it.. The trace is from Sentry and it has been triggered somehow by one of our users.. I couldn't reproduce or trigger any crash during development and testing... but nothing beats real-usage made by daily users apparently...

I'm inviting you to try 1.7 when it will be out. I'll check in our products too but I'm confident it's gone with the latest changes. Thank you again for your feedback!

@malcommac do you have an ETA for the 1.7 release? Should I switch to the main branch in the meantime so my users can benefit from the fix ?

Hi! We'll release 1.7 the upcoming week. After the release we also plan to move the HTTPStubber as separate package too.

released


How to run the code

Dear author:
can you explain how to run the code on my computer? since I do not know how to run omnet++ and python at the same time?

On Ubuntu 16

install omnet++4.6
2.create a virtualenv for python
3.run make in omnet/router
4.in your virtual env, install other necessary compotent listed in Readme

Please refer to Readme first！

I have analyze the source code, but I cannot understand how to describe the demand, the traffic is the described by what?

e

why cant I make in omnet/router

If someone face simtime_t out of range error, here is the solution to make changes under omnet/router/Application.cc at handleMessage function
if (lambda > 0) {
// Add a minimum threshold for lambda to avoid division by extremely small values
double effectiveLambda = std::max(lambda, 1e-6); // Set a lower bound
double etime_val = exponential(1.0 / effectiveLambda);
EV << "Calculated inter-arrival time (etime): " << etime_val << " seconds" << endl;
        // Check if the calculated time is within bounds
        if (etime_val > 0 && etime_val < (MAXSIM - simTime()).dbl()) {
            EV << "Scheduling next event at: " << simTime() + etime_val << endl;
            scheduleAt(simTime() + etime_val, msg);
        } else {
            EV << "Skipping scheduling due to excessive or invalid time: " << etime_val << endl;
            cancelAndDelete(msg);
        }
    } else {
        EV << "Invalid lambda value: " << lambda << ". Skipping scheduling." << endl;
        cancelAndDelete(msg);
    }


 I cannot think of anything else that they need?

master nodes

whatever kubernetes requires
should be able to set tags on compute nodes as part of the same cluster

Makes sense to me , we definitely should limit the compute nodes. Would be good to limit the master but less of a security risk to a degree but probably worth investing the effort in both


[WFRP4e System] Sad boi

I would like to speak to the manager as this WebGL thing is making me sad.From: A sad boiwfrp4e: 3.5.1wfrp4e-core: 1.3.3wfrp4e-eis: 1.2.2wfrp4e-rnhd: 1.4.1wfrp4e-starter-set: 1.4.3

If you gave me any contact details whatsoever I might be able to help, or anyone on the Foundry discord can also provide assistance.


Getting false errors in VScode! Please help!

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.66.0
OS Version: Ubuntu 20.04
I have a CSS file with 2 margins and the second one is causing 2 problems.
However, the errors are fake!
it is expecting a semicolon
it is expecting a selector

/needsMoreInfo
Please post a a minimal code sample.

Going to edit

Wait... I DON'T REMEMBER THE CODE!!!


Add support for spdx SBOM in east build and east release

Description

As the title says.
This PR does not close the related #44 issue, as I think that there is probably still some work left to make the generated files useful for the intended audience (which is unknown at the moment).
Areas of interest

Added code.
Checklist

[x] Source code documentation for all newly added or changed functions was added/updated.
[x] All customer facing technical documentation was updated.

Related issues

Related to #44
After-review steps

Code author will merge the PR by himself/herself.

Current dependencies on/for this PR:

dev

PR #90

PR #91

PR #92   👈

This comment was auto-generated by Graphite.

Merge Activity

Sep 25, 2:42 AM: @MarkoSagadin started a stack merge that includes this pull request via Graphite.


How to define a directory for bundled .woff

Hi there!
I'm using multiple woff fonts in my project. They are loaded with the url-loader, which (afaik) bundle all these files into a single one. This new woff file is located in config.output.publicPath.
Is there a way to change the target directory of these files?  Like config.output.publicPath + fonts/
Thanks a lot!
edit:
Okay, it's just one wofffont (material icon font) which get transformed in a new woff file with an hash filename. Nevertheless I would love to define the directory for this new file.

Found the answer...


Setup instructions?

Not sure if it was just my experience but there were a couple of snags that I hit during setup:

I had to manually place the forecastio.json file in ~/.cache/tmux-weather/forecastio.json instead of just putting it in ~/.config/forecastio.json
It seems to require the whereami command, which OSX doesn't have and isn't in homebrew as far as I can tell.
The status line refers to a path called ~/bin/tmux-weather, where the instructions just say to add to path. Would it be able to just be tmux-weather without ~/bin/?

I have devised a ansiweather approach to this that might be a little simpler. I definitely imagine a forecast.io setup could be pretty sweet though, just adding this in case anyone stumbles across it...
My tmux.conf
set -g status-bg colour32
set -g status-fg colour253
set -g status-interval 100
set -g status-left '#(ansiweather -a false)'
set -g status-left-length 100

to add on to cmdcolin's solution, i made a wrapper script to make a nice concise format
ansiweather -l 75214 -u imperial -a false -w false -h false -p false -d f    alse | awk -F" " '{ print  $8 $6 $7}' | sed -e "s/F//"


move sections in do_parse to functions; prepare for handling old style IANA domain

do_parse:

no functional changes just moving parts of code to their own functions to unclutter do_parse
this prepares for the later handling of IANA domains like example.com and exmple.net which will introduce changed behaviour

test2:

changed test2 to show the variable type and highlight empty strings as return value when no data is present

excellent thanks


Nuke: render instance with subset name filtered overrides

Brief description
Adding ability to override Anatomy imagio required nodes with subset filtering.
Description
Some studios were requesting overriding per subset name regex filtering. This will allow to have different colorspace on subset renderCompMain then on renderCompMask for example. Overrides and also adding missing knob values if they are not found in the original Required Plugin nodes.
Additional info

if override knob is having the same name but different value, value is overriten
if override knob is not having its equivalent in original knobs, it is added
if override knob is having matching equivalent in original knobs and having empty value, it is removed from original knobs.

Testing notes:

Start testing workfile in nuke
go to Studio settings project_anatomy/imageio/nuke/nodes/overrideNodes at your project
configure new override similary to the image, and save settings

in nuke go to openpype/create/Create Write Render, set Subset to Boho and Create
Select the node and CTRL+Enter to see content of render group. Double click at write node and see properties bin. It should look similar to following image, if your colorspace was originaly defined as ACES

now try to create again but Subset name as Main and repeate step 5 and look to project_anatomy/imageio/nuke/nodes/requiredNodes/0/knobs and compare. It shold be set exactly as it is in settings.

Works nicely for string knob overrides. It ignores boolean settings, and fails on integer settings.
It expects first character to be uppercase in the settings, to match to the Subset in the Instance Creator.


Update validation message if rbenv_ruby is not set

Hi,
I use new capistrano/rbenv feature that allows not to define rbenv_ruby in config file.
But the warning message wasn't updated and now it seems a little bit confusing to me.
If I intentionally removed rbenv_ruby from capistrano config "rbenv: rbenv_ruby is not set" looks like I still do something wrong.
It is already said in README

Alternatively, allow the remote host's rbenv to determine the appropriate Ruby version by omitting :rbenv_ruby. This approach is useful if you have a .ruby-version file in your project.

So I think it would be better to add this notice directly to the message.
P. S.
I am not sure about words in the message. Is remote hosts better than deployed hosts?

@ivanovaleksey Good point! Thanks for the PR.
@spikeheap Do you have an suggestion for if/how we should change the warning? It seems weird to warn the user when they are doing nothing wrong.

I have updated the message a little bit:

use info instead of warn
use remote hosts instead of deployed hosts

Hi @ivanovaleksey, this PR looks good, particularly downgrading the message to info. @mattbrictson is spot on about warning users when they're doing the 'right' thing.
This does alter the initial behaviour, which required rbenv_ruby  to be set, but IMHO this is more intuitive behaviour for the uses of rbenv I've seen.
👍

@spikeheap thank you,
but should I use on or by? And should I use definite article?
Syrvey time 🎉

[ ] rbenv: rbenv_ruby is not set; ruby version will be defined by the remote hosts via rbenv
[ ] rbenv: rbenv_ruby is not set; ruby version will be defined on the remote hosts via rbenv

Hi @ivanovaleksey, I do love to bikeshed, so...
IMHO your 'by' option above reads slightly better than the others, and highlights that rbenv is picked up on each host. They all make sense though :).

Looks good! Thanks for contribution ✨


Isolation window changes?

Hi, I looked through the issues and didn't see this discussed, so just want to be sure I understand:
I was just comparing a file that we converted using TRFP 1.3.2 and with 1.4.2, and one substantial difference I notice is:
1.3.2:
                <cvParam cvRef="MS" accession="MS:1000828" value="0.5" name="isolation window lower offset" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
                <cvParam cvRef="MS" accession="MS:1000829" value="0.5" name="isolation window upper offset" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />

vs. with 1.4.2:
                <cvParam cvRef="MS" accession="MS:1000828" value="1" name="isolation window lower offset" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
                <cvParam cvRef="MS" accession="MS:1000829" value="1" name="isolation window upper offset" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />

So it looks like the isolation offsets have doubled.
Comparing with msconvert, it also has 1 as the value, so it appears that the new values match msconvert.
So is it true to say that for all TRFP conversions performed prior to v1.4.1, the isolation windows were too small by a factor of 2? Or is it more nuanced than that? The release notes say "Fixed a bug in handling isolation offset in mzML output". Can this be documented more specifically? It will be important to know if thousands of our previously converted data files have incorrect information.
thanks!

Hi @edeutsch, the error that has been fixed in 1.4.1 is only relevant if isolation offset is used in the raw file, i.e. the center of the isolation window is shifted from the isolated mass. The support for that feature has been introduced in 1.4.0 (4e3b469).
The implementation in 1.4.0 (code below) had an error - the shifted offset was used both for upper and lower offset values in mzML.
                var offset = isolationWidth.Value / 2 + reaction.IsolationWidthOffset;
                precursor.isolationWindow.cvParam[1] =
                    new CVParamType
                    {
                        accession = "MS:1000828",
                        name = "isolation window lower offset",
                        value = offset.ToString(CultureInfo.InvariantCulture),
                        cvRef = "MS",
                        unitCvRef = "MS",
                        unitAccession = "MS:1000040",
                        unitName = "m/z"
                    };
                precursor.isolationWindow.cvParam[2] =
                    new CVParamType
                    {
                        accession = "MS:1000829",
                        name = "isolation window upper offset",
                        value = offset.ToString(CultureInfo.InvariantCulture),
                        cvRef = "MS",
                        unitCvRef = "MS",
                        unitAccession = "MS:1000040",
                        unitName = "m/z"
                    };
}

The error has been corrected in 1.4.1 by 3d899ea

It has been a while since 1.3.2, i.e. it is hard to say what is the reason for the different output. After a quick (and, honestly, rather shallow) dissection I can pinpoint ae7b0b087 (included in 1.3.3). The change prioritizes isolation window information from scan trailer (if it is present) over the information stored in the Reaction object provided by the API. To the best of my knowledge, the trailer was used to store isolation information in older (LTQ-XXX generation) instruments, more modern instruments (QE and Fusion generation) do not use the trailer method anymore. Thus, it could be that the trailer and Reaction were reporting different values on older instruments.
It would help if we can dissect (at least) the version when the change had happened. Would it be possible to share a representative raw file and (preferably) scan?

Thanks for the response, but then that seems like it wouldn't account for what I'm seeing. There seems to be no offset in my file. I'm seeing this:
v1.3.2:
              <isolationWindow>
                <cvParam cvRef="MS" accession="MS:1000827" value="441.297119140625" name="isolation window target m/z" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
                <cvParam cvRef="MS" accession="MS:1000828" value="0.5" name="isolation window lower offset" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
                <cvParam cvRef="MS" accession="MS:1000829" value="0.5" name="isolation window upper offset" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
              </isolationWindow>
              <selectedIonList count="1">
                <selectedIon>
                  <cvParam cvRef="MS" accession="MS:1000744" value="441.297119140625" name="selected ion m/z" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
                  <cvParam cvRef="MS" accession="MS:1000041" value="2" name="charge state" />
                </selectedIon>
              </selectedIonList>

and v1.4.2:
              <isolationWindow>
                <cvParam cvRef="MS" accession="MS:1000827" value="441.297119140625" name="isolation window target m/z" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
                <cvParam cvRef="MS" accession="MS:1000828" value="1" name="isolation window lower offset" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
                <cvParam cvRef="MS" accession="MS:1000829" value="1" name="isolation window upper offset" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
              </isolationWindow>
              <selectedIonList count="1">
                <selectedIon>
                  <cvParam cvRef="MS" accession="MS:1000744" value="441.297119140625" name="selected ion m/z" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
                  <cvParam cvRef="MS" accession="MS:1000041" value="2" name="charge state" />
                  <cvParam cvRef="MS" accession="MS:1000042" value="8781.63757324219" name="peak intensity" unitAccession="MS:1000131" unitName="number of detector counts" unitCvRef="MS" />
                </selectedIon>
              </selectedIonList>

ah, I now see more in your edited post. The file is from an LTQ Orbitrap, it is:
mzspec:PXD0001168:20070625_03_Ti1
This seems to happen in all scans in the file.

So the high-level summary seems to be:
For LTQ Orbitrap type instruments, prior to TRFP v1.3.3, if there is conflicting information in the trailer and Reaction data in the RAW file, then the recorded isolation width might be incorrect in the mzML file (too small by a factor of 2 in one example)
?

I processed the file in all versions starting from 1.3.2 and can confirm that the change has been introduced in 1.3.3. I can also confirm that (at least for this specific file), an isolation width should be 2 Th. It is the one used in the stored MS method and matches the value provided in the trailer. Thus, my initial guess was likely correct. It is, however, unclear where the value stored in Reaction is coming from (Is 1 Th the fallback value?).
High-level summary
The recorded isolation width can be incorrect for TRFP < 1.3.3 and older generation instruments (the ones using trailer for isolation width information). I cannot, however, say if it will be smaller or larger and to what extent.

Excellent, thank you for the helping me understand the issue. Closing.


#395: Created a C++ file and updated readme for Shortest Common Super-sequence

Related Issue

Given two strings str1 and str2, the task is to find the length of the shortest string that has both str1 and str2 as subsequences. (please mention issue number #395  )
Added the code implementation of Shortest Common Super-sequence Problem using dp.
Added the explanation of Shortest Common Super-sequence Problem in the README.md file.

Proposed Changes

Added the code of Shortest Common Super-sequence Problem using dp.
Added README.md file of Shortest Common Super-sequence Problem with time and space complexity.

Additional Info

This code uses dynamic programming.
This problem is a variation of LCS problem.
This is one of the commonly asked interview questions and the concept of this question helps us to solve many more problems.
This code solves an open issue #395
I have tested these changes on VS code using multiple inputs and matched the output with the expected output.
This change will not affect or create conflict with any other code
Time Complexity : O(m*n)
Space Complexity: O(m*n)

Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the README.
[x] 🎀 I have updated the README accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[x] 🌟 ed the repo

Issue: #395

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1
Screenshot #2

Readme preview
Code Snippet

please review my pr @iamgunjan @miraj0507

Resolve the conflicts manually

I have resolved the conflict so please review my pr and tell if anything needs to be done @siddhi-244 @Lakhankumawat

@siddhi-244 @miraj0507 @Lakhankumawat plz review it

Hey, kindly take an user input in the main function

@miraj0507 I have made the changes

LGTM

If everything is fine then please merge this pr @Lakhankumawat

@Lakhankumawat Please check now.

@all-contributors please add @AastikSharma05 code

Looking at your contribution type , contribution  efforts and 2 merged prs  i am increasing the level of PR
CGC= Continuous Good Contribution

Thanks a lot @Lakhankumawat .


Same target built twice? How is this possible?

I'm looking at a build log file where TargetStarted is called twice, the project and target names are the same, and the only difference is targetId and start time:

Is this normal/expected?

Team Triage:
We'd need more information or ideally a minimal repro to figure this out. Do you have a way to get that?

Well, this is during the build of Roslyn and the full log is here:
https://www.dropbox.com/s/9sa6dgi31m6sb1d/roslyn.binlog?dl=0
This build happens nightly so I'll see if it happens again.
But, to confirm, this is not expected behavior, even with cross-targeting and such? Note that these are coming from different threads and slightly different time (2 seconds apart), but the same node, submission, etc.
Also note that the targets in question are relatively new (added recently for cross-targeting?). Maybe CallTarget can result in this?

I have an isolated repro for the case of 2 target frameworks - the project+target is build twice (once for each target framework) even though MSBuild task does not include the TargetFramework as input to the project. Note that the project being built twice is a plain MSBuild project (not a C# project) with a custom target. I would expect that MSBuild handles these in a generic way.
This is the sample solution that reproduces this:
ReproDoubleBuild.zip

I think this is because this target does batching:
https://github.com/Microsoft/msbuild/blob/master/src/Tasks/Microsoft.Common.CurrentVersion.targets#L1525-L1526
So it ends up getting run three times:

cc @nguerrera is this the expected behavior? (just checking)

Yes. Target batching is expected if that's how it's represented in the log.


Added back changelog entry for #509.

Added changelog entry for #509.
TODO:

[ ] Update CHANGELOG.md with your change
[ ] Make sure all of the significant new logic is covered by tests
[ ] Rebase your changes on master so that they can be merged easily
[ ] Make sure all tests and linter rules pass

LGTM


[Bugfix] Fix thread name and log (#290)

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes https://github.com/StarRocks/starrocks-connector-for-apache-flink/issues/290
Problem Summary(Required) ：

When using spark operate starrocks, log and thread is error. I don’t think it’s necessary to show in the thread whether spark or flink is used.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)
[ ] I have added documentation for my new feature or new function

@banmoy Can you help me review?

@Jin-H merged. Thanks for your contribution.


vevo.com: 'Unable to download info: HTTP Error 500'

youtube-dl -v http://www.vevo.com/watch/m.i.a./Borders/USUMV1500545
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.vevo.com/watch/m.i.a./Borders/USUMV1500545']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.03.18
[debug] Python version 2.7.10 - Darwin-15.3.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 2.8.6, ffprobe 2.8.6, rtmpdump 2.4
[debug] Proxy map: {}
[Vevo] USUMV1500545: Downloading video info
ERROR: Unable to download info: HTTP Error 500: Internal Server Error (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 365, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1929, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 437, in open
    response = meth(req, response)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 550, in http_response
    'http', request, response, code, msg, hdrs)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 475, in error
    return self._call_chain(*args)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 409, in _call_chain
    result = func(*args)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 558, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

Duplicate of #8900.


[mtl] lock Device with Mutex. Force Private memory for tiled textures.

Addresses a major part of #1984 but doesn't resolve it completely.
PR checklist:

[x] make succeeds (on *nix)
[x] make reftests succeeds
[x] tested examples with the following backends: metal

@grovesNL yeah, I'm not a fan of those locks either, but that's the reality today we live in. Let's keep an eye on them. Thanks for the review!
bors r=grovesNL


Compass security fixes

Attempt to fix the security issues in #3227 by escaping the arguments to prevent appending commands. Also, removing the ability to send in absolute paths in the log-viewer and only use the check if the file is present in the log-directory.
Fixes #3032
Fixes #3227

Does this fix all of the issues in #3227?

I hope so, at least on *nix environments. Wrote some tests to prove the case. Even if testing with Orchestral/TestBench and Artisan commands are not friends. Mocking base_path() seems not to be trivial.

I hope so.
Saw that I made a mistake and escaping empty arguments, fixed this now.
Wrote some tests to prove the case. Even if testing with Orchestral and Artisan commands are not that easy.

this is not fixed yet?


May I ask about the path 'network_surgery' and the function "insert_conv_layers" ?

Hello! I am doing the reproducing experiment on your code and I met  problems.

In cnn_ucf101_fusion.m:
addpath('network_surgery');   %% line 20
[ netB ] = insert_conv_layers( netB, fusionLayerB(end), 'initMethod', opts.initMethod ); %% line 160

However, I cannot find the path 'network_surgery' and the function "insert_conv_layers" in your folder. May ask if I missed something?
Thank you very much.

Thanks for mentioning this, the file has been added.


Using axios error

Hi I have a rest api and I want to use a library called Axios to do ajax requests on my api but when I tried adding the package npm install axios --save and import it into one of my component import axios from 'axios' it gives me this error
ERROR in ./~/axios/package.json
Module parse failed: /Users/alleoindong/Public/projects/restoko/restoko-desktop-app/node_modules/axios/package.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
|   "_args": [
|     [
|<EMAIL_ADDRESS> @ ./~/axios/lib/adapters/http.js 11:10-41

any work around or hints of the problem? Thank you so much for helping!

right now what I did is I added it into the externals to make the webpack build successful

The axios module load .json file, so you should add json-loader to webpack config. :)

after adding json-loader I got this
ERROR in ./app/index.js
Module build failed: SyntaxError: Unexpected token i
    at Object.parse (native)
    at Object.module.exports (/Users/alleoindong/Public/projects/restoko/restoko-desktop-app/node_modules/json-loader/index.js:7:48)
 @ multi main

putting it into the externals is working.

axios package has http(for node) and xhr(for browser) adapters, and electron renderer can run both or two. Notice that, http adapter can't be packed by webpack.
You can list axios in externals as a quick work around. Or try to replace "./lib/adapters/http.js" to "./lib/adapters/xhr.js" via webpack, see also https://github.com/mzabriskie/axios/blob/master/package.json#L61

i have exactly the same problem.
| { |   "_args": [ |     [ |<EMAIL_ADDRESS> @ ./~/axios/lib/adapters/http.js 10:10-41
and when i try with externals.
ReferenceError: axios is not defined

None of the solutions mentioned above solved it for me. Could someone guide me to an example of this boilerplate using axios or any other HTTP library? Would be much appreciated! Thanks

The axios module load .json file, so you should add json-loader to webpack config. :)

This is real... see this branch, it work.
@chentsulin is right, but it just problem of json file.

@jhen0409 thank you for this.
One mistake I was also making is saving json-loader to devDependencies. After looking at @jhen0409 's example, when saving json-loader to dependencies it worked.

@jhen0409 Should we support json-loader as default loaders?

Should we support json-loader as default loaders?

I think yes, because node require json file is natural, but it was broken by webpack.


I want LSTM to learn with newer data. It needs to update itself depending on the trend in the new data and I wish to save this say in a file. Then I wish to call this pre-fed training  file into any other X,Y,Z fresh files where testing is done. So I wish to 're-fit' [update NOT re-train] the model with new data such that model parameters are just updated and not re-initialized. I understand this is online learning but how to implement it through Keras? Can someone please advise?

@phdrsch In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here. Thanks!

Closing this issue due to lack of recent activity  .Please feel free to reopen if you still have concern.Thanks!


Remove randomized algorithms from the package

Part of #179 if it were to be accepted. I'll try if I can use some git subtree / split magic to move the randomized algorithms into a separate repository without losing the commit history.

The package https://github.com/haampie/RandomizedAlgorithms.jl has all the randomized algorithms and preserves commit history :).


Fix StandardChip padding

WHAT
Fix StandardChip padding.

WHY
In order to align with Figma redlines.
HOW
Decrease default content padding when using large icon instead of adding space when using small icon.
Checklist :clipboard:

[N/A] Add explicit visibility modifier and explicit return types for public declarations
[x] Run spotless check
[x] Run tests
[N/A] Update metalava's signature text files

Merging red as failed flaky test was ignored in https://github.com/google/horologist/pull/408


Support operation coallescing

Add a generic operation coallescing mechanism and use it to fix #135.

@garrettmoon @appleguy: Appreciate a review here :)

I am soooo excited by this BTW.


Pass vttest

http://www.columbia.edu/kermit/vttest.html

[ ] Cursor movements. https://github.com/black-screen/black-screen/pull/67

Passing vttest is a big deal. You would have to implement most of the DEC primitives the right way and the documentation of those is lousy. Best source would be http://vt100.net and source code of popular emulators like xterm or rxvt.
I tried to set up test cases for the primitives based upon xterm output. You can find them here https://github.com/netzkolchose/node-ansiterminal/tree/master/test. The test cases are still work in progress, tough you might find them useful somehow.

Thank you @jerch. If only there was a test suite failing with a message like CUB should not wrap at the edge of the screen. Instead, you can see that the output looks different, but have no idea why.

Yeah esp. the last column handling is awkward. I started to support unicode with fullwidth characters in node-ansiterminal - it is a total mess at the last column. No clue yet how to solve this in a clean way but it needs refactoring -.-

We could create an independent suite which would work for any terminal implementation (maybe the requirement would be to render to a 2d array of characters for the suite, but I'm not sure).

Hmm, separate the frontend stuff (user events and output) from the low level vt stuff - thats the reason why I splitted the whole stuff in node-ansiterminal and the jquery.browserterminal as the frontend (while the latter is still quick&dirty "can I get this run"-code).
Not sure if a separation like this will do for your needs since you have much more functionality in mind (my goal is to get a full featured classical vt emulation in the browser, which comes with some restrictions like no node types etc). But if you are cool with that we could try to build something like "libvt" for node/browser as a basic vt drop-in stack (tested of course :D).

I was thinking of something like https://github.com/karlcow/markdown-testsuite, which provides an independent set of tests for every MarkDown implementation in the world.
I would like the suite to be able to test xterm, iTerm 2, and others. It would give us an immediate benefit of having a reference implementation (if it works in xterm, it should work in whatever-terminal) and a delayed benefit of simplifying the lives of other people who want to create a new terminal.

Ah got you. Well it should be possible but would require a well crafted testsuite with adapters to other languages (as test drop-ins into xterm source etc). Biggest problem would be to get all the right definitions of all (or at first most common) modi a terminal can switch to (xterm has tons of different emulation modi).

Hooray, the first screen looks perfect!

vttest looks like a worthy (and ambitious goal).
The node-ansiterminal test looks like a great start. Very easy to catch regressions. Seems it may be difficult hook into the right portion of the terminal emulator though.
Looks like the xterm faq is moslty focused on the number of supported functions and visual differences of the various implementation. If you wanted to create a test suite to be used across multiple terminal emulators, probably would be best to stick to that. Maybe standardize on screen size, font, font size, and compare screen shots?
Very cool project. Thanks all


can you add manually vendorid and productid of unknown devices?

i have some usb devices which are not listed in the database for vid and pid pairs. so where can i find these vid and pid list and are these values stored in a file and can you add your own entries for unknown vids and pids? from where usbip is getting these values (from server)?

http://www.linux-usb.org/usb-ids.html

thanks i found it:
userspace/usbip/usb.ids

This file was downloaded from the site, it is never updated manually.

ok, then i will append some lines manually.


Doctrine adapter composer

Hello,
I wanted to test portphp but I can't find portphp/doctrine or protphp/doctrine-adapter on composer.
Is that normal ?
Thank you

Whoops, you’re completely right! I added the package to Packagist.

so is it doctrine or doctrine-adapter ?

It’s portphp/doctrine (also mentioned in the docs).

so this readme is wrong https://github.com/portphp/doctrine

Fixed!


[Release] Vote email number of issues is querying JIRA and producing a wrong number

Describe the bug, including details regarding any error messages, version, and platform.
When generating the vote email for RC 0 on 11.0.0 I've realised that the vote email generated contains the following:
This is a release consisting of 274 resolved JIRA issues[1].

This number is extracted from:
jira_url="https://issues.apache.org/jira"
  jql="project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%20${version}"
  n_resolved_issues=$(curl "${jira_url}/rest/api/2/search/?jql=${jql}" | jq ".total")

This is wrong now, we should extract this from the GitHub milestone:
https://github.com/apache/arrow/milestone/1?closed=1
I've updated this manually for the current email vote but we should fix it on the dev/release/02-source.sh script.
Component(s)
Release

GraphQL API is another option:
curl -H 'Content-Type: application/json' -H "Authorization: bearer GITHUB_TOKEN" -X POST -d '{"query": "query {search(query: \"repo:apache/arrow is:issue is:closed milestone:11.0.0\", type: ISSUE) {issueCount}}"}' https://api.github.com/graphql | jq ".data.search.issueCount"


Uncaught Error: ENOENT: no such file or directory, uv_chdir

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.19
System: Microsoft Windows 10 Home Single Language
Thrown From: atom-beautify package, v0.28.14
Stack Trace
Uncaught Error: ENOENT: no such file or directory, uv_chdir
At /C:/Users/rohan/.atom/packages/jshint/index.js:245

Error: ENOENT: no such file or directory, uv_chdir
    at Error (native)
    at lint (C:/Users/rohan/.atom/packages/jshint/index.js:226:10)
    at complete (C:\Users\rohan\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\babel-core\node_modules\lodash\index.js:7697:25)
    at delayed (C:\Users\rohan\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\babel-core\node_modules\lodash\index.js:7707:11)

Commands
     -6:31.1.0 fuzzy-finder:toggle-file-finder (atom-text-editor.editor.is-focused)
  2x -6:29.8.0 core:confirm (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ],
    "destroyEmptyPanes": false
  },
  "atom-beautify": {
    "_analyticsUserId": "53a5ef3d-81e7-4d23-abe1-00e83a0dddb9"
  }
}

Installed Packages
# User
atom-handlebars, v1.2.0
atom-jshint, v2.0.0
color-tabs, v0.1.8
css-color-underline, v1.0.1
file-types, v0.5.1
jshint, v1.8.0
language-spacebars, v0.2.2
linter, v1.7.0
linter-handlebars, v2.1.0
meteor-api, v2.20.0
webbox-color, v0.5.8

# Dev
No dev packages

At /C:/Users/rohan/.atom/packages/jshint/index.js:245
Error: ENOENT: no such file or directory, uv_chdir
at Error (native)
at lint (C:/Users/rohan/.atom/packages/jshint/index.js:226:10)

Looks like a jshint issue.


Add multi selection tools in Manager to select multiple features from Map

Describe requirements
Right now, Editor widget now only exposes single select tool, but we would like to support multi selection tools like lasso or rectangle in Manager so users can select multiple features from map.
Alternatives
No response
Other Relevant Info
No response
Impact
No response

cc @sarahmcdonald7

@azizaparveen I wonder if we should also consider adding in a way to to select multiple features in the map. We have a selection tool like this in Attachment Viewer and Chart viewer templates.

@azizaparveen I think in the table we should consider updating the app to have the typical selection behavior. So when clicking on multiple check boxes in the table, rather than only selecting one feature at a time multiple features would be selected if you keep checking boxes in the table. If we do this, we should consider adding a Close(X) in the pop-up panel to clear the selection.

@azizaparveen I think in the table we should consider updating the app to have the typical selection behavior. So when clicking on multiple check boxes in the table, rather than only selecting one feature at a time multiple features would be selected if you keep checking boxes in the table. If we do this, we should consider adding a Close(X) in the pop-up panel to clear the selection.

@sarahmcdonald7 can we discuss this on Monday? We used to have the typical selection behavior but we changed it because this creates unintended multiple selection where in most cases user just wants to select a single record at a time (#437) , even if we add a close button, we will have to manually click on the close button to unselect it.

Tracking change of multi selection behavior of the Table to sync with Map Viewer https://github.com/Esri/solutions-components/issues/1051