[iOS] Missing target for iOSX64 for 4.1.0

Describe the bug
It's not possible to download the library for projects containing the target iOSX64
To Reproduce
Try to update the library with the 4.1.0 version.

Logs 🪵
Caused by: org.gradle.internal.component.NoMatchingConfigurationSelectionException: No matching variant of io.github.g0dkar:qrcode-kotlin:4.1.0 was found. The consumer was configured to find a library for use during 'kotlin-metadata', preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native', attribute 'org.jetbrains.kotlin.native.target' with value 'ios_x64' but:

Variant 'iosArm64ApiElements-published' capability io.github.g0dkar:qrcode-kotlin:4.1.0 declares a library for use during 'kotlin-api', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native':

Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'ios_arm64' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'ios_x64'
Other compatible attribute:

Doesn't say anything about its target Java environment (preferred optimized for non-jvm)

Additional context
This might be related with the last changes made on build.gradle.kts, given that the iOSX64 target was deleted and not added again to the list.
Thanks!

Already solved 😉


Change min_payment from Uint8 to Uint64

Description
current min_payment calculation is 10^x to match a same implementation in Omnilock and ACP, but since our proxy and mutant cells are located in Celldep field so that there's no need to consider DDos issue, besides, 10^x would introduce an issue that to be unable with a concrete CKB price for those cells creators.
we can just use a specific CKB price value to indicate this min_payment option, which type is Uint64.

@Flouse what do you think that we should still keep min_payment in args or it should be place in data?

I think putting min_payment in ClusterProxy's data is more flexible,
because changing min_payment doesn't change type_script_hash.

If I understand correctly, the issue with storing min_payment in the type args of ClusterProxy and Mutant is that we cannot query or compare them using their type hash. Instead, we should only query or compare them with their first 32 bytes of the type args, like this:
cluster_proxy.type_args.as_ref()[..32]

From my perspective, the position may not be a significant issue if we can resolve the problem mentioned above.
However, I have another question: should the min_payment be modifiable? (since ClusterData and SporeData are immutable)

question: should the min_payment be modifiable? (since ClusterData and SporeData are immutable)

question: should the min_payment be modifiable? (since ClusterData and SporeData are immutable)

There may be no standard answer to this question.
IMO, the cluster data should be immutable, but the value of a cluster can change over time.
A cluster owner may want to set a low min_payment at the beginning, and increase it later when the cluster is hot or more valuable.


Made parsing of .cup files more generic regarding headers

I had problems parsing a cup file downloaded from SeeYou cloud as the header rwwidth was included. Parsing now ignores columns that are not specified instead of throwing an error.
Sorry for the double quotes, this is due to auto formatting with black.

looks like CI is unhappy about these changes 🙀

btw I'm fine with dropping support for older Python versions under a few minor conditions:

it should be done in a dedicated PR
we should mention it in the changelog
it should be released as a new major version since it's a breaking change

Okay, I have started to add type annotations to parts of the code base so requiring python 3.6 would certainly be beneficial.

I think #217 tries to also implement rwwidth.

Could you please change this PR, so that all changes of black are removed? Otherwise it is very hard to see, what you really have changed. Thanks!

closed by https://github.com/Turbo87/aerofiles/pull/255


Make it easier to swap out the loader, to allow for a custom loader

Small PR which just moves the loader to a place where it can be easily overwritten to allow for custom loaders and adds a LoadedInterface
My particular use-case for this concerns some additional pre-processing steps necessary to allow the .env file to be readable, therefore requiring a custom loader with a minor addition to the existing loader, this would make it easier/cleaner to overwrite the loader in the Dotenv class.

  It just adjusts the abstraction a bit to call a method rather than directly construct anything inline.

That's correct the idea was to remove the double instantiation so the get loader method could be overwritten in a single place, this appears to have been addressed in another PR vlucas/phpdotenv#215.


[Feature request] On reset add clicked element

Any chance that onReset Function will get also the clicked element ?
In that way i'll could indicate where the user clicked to close the tour and improve my use in the driver for the end user.
Thanks

We just released v1.0 of driver.js which has been rewritten from the ground up. There are more simplified hooks which give you more control over the popover and the whole lifecycle. Please have a look at the docs and do let me know if you face any issues.


{ed,gzip,gawk,gnugrep}: Add bash to buildInputs

Description of changes
part of https://github.com/NixOS/nixpkgs/pull/296581
These packages distribute shell scripts in /bin. Their shebangs are always patched to a /nix/store bash, but by default, they are patched to use the stdenv's shell, which during bootstrap is build in the previous stdenv. By using bash from the current stdenv, we can shorten the FreeBSD bootstrap process significantly.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

You are modifying four different packages kept by different people.
Please, do one commit per package (no need for a new PR), so we can know what to bisect in a future bisection adventure.

I've split up the commit. Do you need me to take ownership of any of these packages?

For now there is no need to keep maintainership of them. I will create a Nixpkgs team later this week to formalize this.

I didn't know about runtimeShell! I've changed it.


Add mountinfo unit tests

What this PR does / why we need it:
The PR adds unit-tests for various mountinfo usage scenarios. Additionaly it introduces some small refactoring needed for better testability. Basing on the testdata it also fixes btrfs subvolumes handling.
New test cases:

detect the root mount info of the test suite - checks if mountinfo is parsed correctly and MountInfoRoot method returns the expected root entry /.
detect the full path of the mount on a node - checks that the full path of the mount is composed correctly and includes all the parts from the host perspective. This test uses the data from nodes with different filesystem settings: overlayfs, devicemapper and btrfs.

The refactoring includes:

moving the logic of composing the full path for containerdisks to isolation package
cleanup of duplicated code (Detect method of socketBasedIsolationDetector)

Btrfs subvolumes fix:

handle the prefix /@
do not perform the parent mount info search basing on the device number as it will lilkely find the wrong entry

Fixes #4590
Special notes for your reviewer:
Follow-up of the PR https://github.com/kubevirt/kubevirt/pull/4671. The PR looks huge because it includes the test data from /proc/<pid>/mountinfo. The actual modifications to the code base are pretty compact.
The fix for btrfs subvolumes is based on a single host configuration which is reflected in the corresponding testdata. Not sure that it covers all the possible filesystem layouts hence comments and suggesetions are welcome.
Release note:

NONE

/lgtm
/approve
Great!

The fix for btrfs subvolumes is based on a single host configuration which is reflected in the corresponding testdata. Not sure that it covers all the possible filesystem layouts hence comments and suggesetions are welcome.

This is a great start. If it does not cover all scenarios, we can extend it based on provided mount tables from people with btrfs, if that is fine for you.


Show tile highlight on the tile your character is standing on in the "tile indicator" plugin

useful for olm running, hunter xbow pking, vorkath xbow woox walk, knowing where u are when in a animation stall like vengeance cast

This will be solved in #1747

This was added in the external Player Tile plugin.


Add srnEnableDevelopmentalVersions to StdRunNodeArgs

Fixes #2938.
The interpretation of this new flag within stdLowLevelRunNodeArgsIO determines what the highest NTN and NTC version will be when the flag is disabled. When the flag is enabled, those bounds are ignored, and the relevant instance of Ouroboros.Consensus.Node.NetworkProtocolVersion.SupportedNetworkProtocolVersion is used unfiltered.

Thanks, Marcin! I rebased (automatic, no conflicts) and will now bors.

bors r+


Inconsistency of naming convention

Here are a few examples in class ReferenceLineInfo:
class ReferenceLineInfo {
...

  // How about IsInitialized()?
  bool IsInited() const;

...
  // Try to follow protobuf style for accessors?
  PathDecision* path_decision();
  const PathDecision& path_decision() const;
  const ReferenceLine& reference_line() const;
  const common::TrajectoryPoint& AdcPlanningPoint() const;

  // if IsInited(), should this one be declared as IsDestinationReached()?
  bool ReachedDestination() const;
...

  // If follow google protobuf style, should this accessor be declared as cost()?
  double Cost() const { return cost_; }
  void AddCost(double cost) { cost_ += cost; }
  void SetCost(double cost) { cost_ = cost; }
...

  // should it be IsIrrelevantObstacle()?
  bool IsUnrelaventObstacle(PathObstacle* path_obstacle);

...

}

@jilinzhou we follow Google C++ coding style. According to it, "Accessors and mutators (get and set functions) may be named like variables."
Please refer to : https://google.github.io/styleguide/cppguide.html#Function_Names
We will close the issue for now.
Thank you for supporting Apollo!


fix: scan dotfiles in source paths

resolves https://github.com/nuxt/module-builder/issues/400
Might be worth more discussion about whether this is desired, or a breaking change.
(Nevertheless it should be possible to override by using an array pattern syntax to exclude files matching a dot pattern. Alternatively, we could allow configuring glob options more specifically - but it feels like the pattern syntax is a safer API.)

I would suggest add gitignore for some of the known dot files. Or ideally parse .gitignore to avoid unwanted behavior or at least reduce them.


Add Chinese translation for 'Hosts File Editor'

Microsoft PowerToys version
0.69.1
Utility with translation issue
Hosts File Editor
🌐 Language affected
Chinese
❌ Actual phrase(s)
Hosts File Editor
✔ Expected phrase(s)
Hosts编辑器
ℹ Why is the current translation wrong
Not translated from English to Chinese

It takes a while for the localisations to appear, they should appear with the next release.

https://microsoft.visualstudio.com/OS/_workitems/edit/44976533 /loc

this should be fixed in .71, can you please verify?  /needinfo


fixes broken links to oci-scope-table

The oci-scope-table moved from governance/ to about/
Signed-off-by: Mike Brown<EMAIL_ADDRESS>

LGTM

LGTM


opendf.exceptions.python_exception.ParserException: Syntax error at LexToken(OPEN_ARGUMENTS,'(',1,15)

Dear authors,
I found this very common bug that occurs in many many dialogs. So I'm wishing for a fix such that a lot of dialogs can benefit.
Expressions:
CreateEvent(
    AND(
       has_subject(
          swimming ) ,
       starts_at(
          NextDOW(
             FRIDAY ) ) ) )

AcceptSuggestion()

First expression executes fine, but the second AcceptSuggestion() raises:
Traceback (most recent call last):
File "OpenDF/opendf/applications/smcalflow/nodes/functions.py", line 1409, in exec
d = Event.create_suggestion(cp, self)
File "OpenDF/opendf/applications/smcalflow/nodes/objects.py", line 904, in create_suggestion
return Event.get_event_factory().create_event_suggestion(root, parent, avoid_id)
File "OpenDF/opendf/applications/smcalflow/nodes/event_factory.py", line 784, in create_event_suggestion
self.get_suggestions_from_database(root, root.context, subj, atts, avoid_id)
File "OpenDF/opendf/applications/smcalflow/nodes/event_factory.py", line 860, in get_suggestions_from_database
selection = self.create_database_selection(root, d_context, subject, attendees_ids, ignore_event_id)
File "OpenDF/opendf/applications/smcalflow/nodes/event_factory.py", line 928, in create_database_selection
cstart = Node.get_truncated_constraint_tree(ttree, 'TimeSlot', 'DateTime', 'start')
File "OpenDF/opendf/graph/nodes/node.py", line 2504, in get_truncated_constraint_tree
r, e = Node.call_construct(sexp, d_context)
File "OpenDF/opendf/graph/nodes/node.py", line 1857, in call_construct
g, ex = construct_graph(sexp, d_context, register=register, top_only=top_only, constr_tag=constr_tag,
File "OpenDF/opendf/graph/constr_graph.py", line 91, in construct_graph
raise ex
File "OpenDF/opendf/graph/constr_graph.py", line 86, in construct_graph
prs = parse_p_expressions(sexp)
File "OpenDF/opendf/parser/pexp_parser.py", line 460, in parse_p_expressions
return parser.parse(expressions)
File "OpenDF/opendf/parser/pexp_parser.py", line 351, in parse
self.parser.parse(input=expressions, lexer=self.lexer)
File "OpenDF/venv/lib/python3.8/site-packages/ply/yacc.py", line 333, in parse
return self.parseopt_notrack(input, lexer, debug, tracking, tokenfunc)
File "OpenDF/venv/lib/python3.8/site-packages/ply/yacc.py", line 1201, in parseopt_notrack
tok = call_errorfunc(self.errorfunc, errtoken, self)
File "OpenDF/venv/lib/python3.8/site-packages/ply/yacc.py", line 192, in call_errorfunc
r = errorfunc(token)
File "OpenDF/opendf/parser/pexp_parser.py", line 443, in p_error
raise ParserException(p)
opendf.exceptions.python_exception.ParserException: Syntax error at `LexToken(OPEN_ARGUMENTS,'(',1,15)`

Not sure about this - does this work for you? (when you put it in main_examples, dialogs[0])
'CreateEvent(AND(has_subject(swimming ) ,starts_at(NextDOW(FRIDAY ) ) ) )', 'AcceptSuggestion()'

Thanks, this one worked. After some debugging, I found d_context.inc_turn_num() is required before AcceptSuggestion.

As a rule, to have multiple expression in one turn, they should be inside a 'do' expression. Otherwise, each expression should be a separate turn.
In this example, it makes sense to have the two expressions in separate turns.

Thanks for you clarification. Closing this now.


⚠ Avatar API Endpoint has degraded performance

In 0c6d53c, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 5272 ms

Resolved: Avatar API Endpoint performance has improved in d743aa5 after 19 minutes.


docs.data-indexers.md

Description
Added Traceye, data indexing solution to the List
Linked Issues

Additional context

added pre-fix


Safari issues & ToneAudioBuffer loader question

Hi, I also had the issues regarding Safari updates, which has broken my project that was built in r13.8.32.
Following the advice in #754 I have upgraded the project to r14.7.60 but now I've run into some conflicts with the new ToneAudioBuffer.. previously I had a loading screen something like
Tone.Buffer.on('load' ()=>{
			console.log("loaded music!")
});

Tone.Buffer.on('progress', (prog) => {

		fill.style.width = `${(prog * 100).toFixed(2)}%`

})

but according to the docs we are required to use  Tone.loaded ( ) => Promise.
apologies for my lack of knowledge for typescript & promises but could someone give an example of how to write this in javascript?
I also noticed there is now no 'progress' method, how would I go about creating a loading screen as above using the new ToneAudioBuffer?
Sorry for the question, not issue. please let me know if you would like me to remove and ask elsewhere.
Thanks

Here's an example of how to use the new loaded() API
// create all your samples before calling 'loaded'
Tone.loaded().then(() => {
  // all your samples are loaded
})

"progress" events was removed in version 14 with no replacement for now


Convert Diagnostic Test Models to incremental models

@ian-r-rose and @kengodleskidot will confirm which models still need to be converted to incremental and update this issue with what is remaining.

@ian-r-rose @kengodleskidot
When you have time could you edit the description above and list out the models that still need to be converted to incremental models as a checklist? Just so we have a sense of how much work is left on this item.


Empower LUA contributors to have a better experience

https://plugins.jetbrains.com/plugin/5055?pr=
http://www.eclipse.org/ldt/
Maybe local tools to make this easy..

LDT
This is in basebox 1.0.0 now.


Removing inner-scope-resource (Fixing #618)

This looks to be a valid test case are we sure it should be removed?

Conversation recap:
We don't seem to be checking the location property for resources - probably missed this since this is one of the oldest tests.
For the location property on each resource, the property value must be one of the following:

global
any expression

Note that resourceGroup().location, is an expression but we have tests in place to check for that.


Improvement of input/output dictionary for retrofit

Previously, it was necessary to specify the co2_proxy resource in the output and input dictionaries of  NetworkNodeWithRetrofit and CCSRetroFit, respectively. The exact value did not matter, but it was necessary for the declaration of the flow variables.
This PR is providing a new approach in which we utilize dispatch on the functions EMB.inputs and EMB.outputsto automatically add the co2_proxy` resource.

Force push due to local rebase.


[Bug] Huge performance bug when selecting multiples images.

On my dataset, selecting multiples images freeze the interface. If I select 5 images it will freeze for 5 seconds, and if I select 10 images it will freeze for 10 seconds.

Fixed in 1.6.6

thx !


Ghidra Installation on Ubuntu 22.04.3 is totally confusing

I downloaded the release edition from Github.
Unzipped the source.tar.gz.
cd ghidra-Ghidra_10.4_build/Ghidra/RuntimeScripts/Linux
./ghidraRun
But it isn't working and shows following.
Cannot launch from repo because Ghidra has not been compiled with Eclipse or Gradle.

Just to clarify, you downloaded the link labelled "Source code (tar.gz)" but not link labelled "ghidra_10.4_PUBLIC_20230928.zip"?   If so, you probably (?) should have used the other link:
[https://github.com/NationalSecurityAgency/ghidra/releases/download/Ghidra_10.4_build/ghidra_10.4_PUBLIC_20230928.zip]
The second two links in each are really archives of the source code, i.e. C and Java files, not executables, and cannot be launched without first using, well, gradle or Eclipse to compile them.

Closing, as @d-millar has provided the correct explanation for your issue.

Thank you people 💯

It would be really helpful it it was made crystal clear in the installation instructions (both README.md and in the htmlversion
https://htmlpreview.github.io/?https://github.com/NationalSecurityAgency/ghidra/blob/stable/GhidraDocs/InstallationGuide.html
that when you say "Download a Ghidra release file", you mean specifically the ghidra_10.4_PUBLIC_20230928.zip and NOT  any of the tar.gz files.
It gets confusing because we read the InstallationGuide.html, where it talks about native binaries, which makes us think "oh that zip file is the windows version" and then we download the tar.gz and end up wasting time.
Summary: Please be super clear everywhere that the ghidra_10.4_PUBLIC_20230928.zip file is the installation file both for linux and windows. Best if it can be noted also on the download page itself.

Yes, I was confused because tar file type predates zip file type. Mostly Unix based system use tar.* and Microsoft uses zip. tar deals with file ownership, permissions, links, special files and zip is a compressing archiver works very with windows but can not deal with file permissions.

GitHub automatically sticks those tar'ed up source downloads there...I wish they would isolate them a little better.


Extension functions vs SQLite Math Functions

The upcoming version 3.35.0 of SQLite will provide a new official extension implementing many built-in mathematical SQL functions.
Unfortunately, this new SQLite extension is not equivalent to the Extension Functions extension which is included in SQLite3 Multiple Ciphers.
This issue lists all provided SQL functions and the discrepancies compared to the official SQLite.
Mathematical functions

Function
Description
SQLite Math Extension (SME)
Extension Functions (EF)
Remarks

acos(X)
arccosine of X
:heavy_check_mark:
:heavy_check_mark:

acosh(X)
hyperbolic arccosine of X
:heavy_check_mark:
:heavy_check_mark:

asin(X)
arcsine of X
:heavy_check_mark:
:heavy_check_mark:

asinh(X)
hyperbolic arcsine of X
:heavy_check_mark:
:heavy_check_mark:

atan(X)
arctangent of X
:heavy_check_mark:
:heavy_check_mark:

atanh(X)
hyperbolic arctangent of X
:heavy_check_mark:
:heavy_check_mark:

atan2(X,Y)
arctangent of Y/X
:heavy_check_mark:
:heavy_check_mark:

atn2(X,Y)
alias for atan2
:x:
:heavy_check_mark:

ceil(X)
next larger integer value above X
:heavy_check_mark:
:heavy_check_mark:

ceiling(X)
alias for ceil
:heavy_check_mark:
:heavy_check_mark:

cos(X)
cosine of X
:heavy_check_mark:
:heavy_check_mark:

cosh(X)
hyperbolic cosine of X
:heavy_check_mark:
:heavy_check_mark:

cot(X)
cotangent of X
:x:
:heavy_check_mark:

coth(X)
hyperbolic cotangent of X
:x:
:heavy_check_mark:

degrees(X)
convert X from radians to degrees
:heavy_check_mark:
:heavy_check_mark:

exp(X)
e raised to the power X
:heavy_check_mark:
:heavy_check_mark:

floor(X)
next integer value less than X
:heavy_check_mark:
:heavy_check_mark:

ln(X)
natural logarithm of X
:heavy_check_mark:
:heavy_check_mark:

log(B,X)
base-B logarithm of X
:heavy_check_mark:
:x:

log(X)
base-10 logarithm of X
:heavy_check_mark:
:exclamation:
EF calculates natural logarithm.

log10(X)
base-10 logarithm of X
:heavy_check_mark:
:heavy_check_mark:

log2(X)
base-2 logarithm of X
:heavy_check_mark:
:x:

mod(X,Y)
remainder after dividing X by Y
:heavy_check_mark:
:x:

pi()
approximation for π
:heavy_check_mark:
:heavy_check_mark:

pow(X,Y)
X raised to Y-th power
:heavy_check_mark:
:x:

power(X,Y)
alias for pow
:heavy_check_mark:
:heavy_check_mark:

radians(X)
convert X from degrees into radians
:heavy_check_mark:
:heavy_check_mark:

sign(X)
sign of X
:heavy_check_mark:
:heavy_check_mark:

sin(X)
sine of X
:heavy_check_mark:
:heavy_check_mark:

sinh(X)
hyperbolic sine of X
:heavy_check_mark:
:heavy_check_mark:

sqrt(X)
square root of X
:heavy_check_mark:
:heavy_check_mark:

square(X)
square of X
:x:
:heavy_check_mark:

tan(X)
tangent of X
:heavy_check_mark:
:heavy_check_mark:

tanh(X)
hyperbolic tangent of X
:heavy_check_mark:
:heavy_check_mark:

trunc(X)
truncate X to an integer value
:heavy_check_mark:
:x:

The Extension Functions extension already provides most functions included in the upcoming SQLite Math Extension.
Options to handle math functions in the future:

Activate the new SQLite Math Extension, and remove duplicates from the Extension Functions extension.
Implement missing functions in the Extension Functions extension, and do NOT activate the new SQLite Math Extension.

🛑  At the moment I prefer the first variant, but there may be criteria to prefer the second variant over the first. Please give feedback, if you are aware of any such criteria.
Unfortunately, there is one hard conflict regarding the log function. While the Extension Functions extension calculates the natural logarithm, the new SQLite Math Extension calculates the base-10 logarithm. The conflict cannot be resolved without breaking compatibility.
🛑 At the moment I intend to switch the implementation in the Extension Functions extension from natural logarithm to base-10 logarithm for the sake of future compatibility with SQLite. Please let me know, if there are reasons to keep the current definition.
String functions

Function
Description
SQLite
Extension Functions (EF)

charindex(S1,S2)
find position of S1 in S2
:x:
:heavy_check_mark:

charindex(S1,S2,N)
find position of S1 in S2 starting at position N
:x:
:heavy_check_mark:

leftstr(S,N)
N leftmost characters of S
:x:
:heavy_check_mark:

padc(S,N)
center pad S to length N
:x:
:heavy_check_mark:

padl(S,N)
left pad S to length N
:x:
:heavy_check_mark:

padr(S,N)
right pad S to length N
:x:
:heavy_check_mark:

proper(S)
capitalize all words in S
:x:
:heavy_check_mark:

replicate(S,N)
replicate S N times
:x:
:heavy_check_mark:

reverse(S)
reverse S
:x:
:heavy_check_mark:

rightstr(S,N)
N rightmost characters of S
:x:
:heavy_check_mark:

strfilter(S1,S2)
remove from S1 all characters not in S2
:x:
:heavy_check_mark:

No string function of the Extension Functions extension is currently in conflict with SQLite.
Aggregate functions

Function
Description
SQLite
Extension Functions (EF)

lower_quartile(X)
25% quartile of X
:x:
:heavy_check_mark:

median(X)
median of X
:x:
:heavy_check_mark:

mode(X)
most frequent value of X
:x:
:heavy_check_mark:

stdev(X)
standard deviation of X
:x:
:heavy_check_mark:

upper_quartile(X)
75% quartile of X
:x:
:heavy_check_mark:

variance(X)
variance of X
:x:
:heavy_check_mark:

No aggregate function of the Extension Functions extension is currently in conflict with SQLite.

Here is my opinion on that subject:

Activate SME as soon as possible and remove duplicates from the EF implementation.
I personally think that switching log(x) from natural logarithm to base 10 logarithms is a good thing, even if it breaks compatibility

Here is my opinion on that subject:

Activate SME as soon as possible and remove duplicates from the EF implementation.
I personally think that switching log(x) from natural logarithm to base 10 logarithms is a good thing, even if it breaks compatibility

@Willena thanks for your feedback.

Activate SME as soon as possible and remove duplicates from the EF implementation.

The estimated release date for SQLite 3.35.0 (which includes the new math functions) is end of March 2021. Shortly after the release I will make it available in SQLite3 Multiple Ciphers.

I personally think that switching log(x) from natural logarithm to base 10 logarithms is a good thing, even if it breaks compatibility

Well, for mathematicians the only natural logarithm is that to the base e and they tend to call it log; on the other hand for computer scientists the only natural logarithm is that to the base 2. :smile:
Therefore, the best approach seems to be compatible with the official SQLite distribution.

@Willena thanks for your feedback.

Activate SME as soon as possible and remove duplicates from the EF implementation.

The estimated release date for SQLite 3.35.0 (which includes the new math functions) is end of March 2021. Shortly after the release I will make it available in SQLite3 Multiple Ciphers.

I personally think that switching log(x) from natural logarithm to base 10 logarithms is a good thing, even if it breaks compatibility

Well, for mathematicians the only natural logarithm is that to the base e and they tend to call it log; on the other hand for computer scientists the only natural logarithm is that to the base 2. :smile:
Therefore, the best approach seems to be compatible with the official SQLite distribution.

+1 for official SME.
As for the compatibility issues - there could a solution to that, but I guess it would require significant effort. The solution would be to register additional pragma (or custom SQL function) like prefer_mc_functions(true) that would make Sqlite3MC register its own log(X) function. As we know, whenever a SQL function with same name and number of arguments is registered, it replaces (covers) the previous version of the same signature, thus making the MC function to be fired from that point of time.

IMHO it is not worth the effort to implement a dedicated pragma for this purpose. I suppose that only a small minority of database applications actually use the log function. And if a developer decides to upgrade to a newer SQLite version, he/she is free to decide which extension to use. The default will be now the official math extension, but setting the appropriate compile time symbols the developer can override this.

Release of SQLite3 Multiple Ciphers version 1.2.0 (based on SQLite version 3.35.0) now includes the new SQLite Math Extension.


git branching model

First of all, we need to decide how we are going to use git. There are many ways, the most simple one is that everybody has a clone of this repo, with only one branch named master. And all work is done on this branch, and the changes are sent as a pull request to the organization repo. However, there are other models.
For instance, one of the most used models is the feature-branching model. http://nvie.com/posts/a-successful-git-branching-model/ I suggest following this model. Let's discuss.

We use feature-branching model at work. It is very convenient. It categorizes your development into features by both physically and conceptually. Multiple features can be developed simultaneously. And each deployment you know what features are included. It is also useful for deployment documentation.

The branching structure defined in the link you have provided is what we are using at my workplace. I find it very useful as it allows the code to be more manageable in smaller scales.

Since both the group name and repository name have been decided, should we fork this repo? From now own, we should not make any changes on this repo directly, except issues and wiki pages.
If you have not yet read the url I provided, please give priority to it. It explains how we are going to use git system. If you have any question, do not hesitate to ask.

@muatik should we create a separate branch for mobile-frontend-backend or use a dev branch for all?

we can use dev branch for all. since they share nothing, any conflict will not occur.

On 25th March we've talked about forking the main repo in our own repositories. I was trying to setup my development environment according to wiki contribution page. I've had forked the repo very very long time ago and I've realized that my version of repo is outdated. So I had to synchronize it with the main repo. I've found this walk through in github's help page.
Is this the right way to keep our copy of repo  updated?

The final decision was to have a fork of "dev" branch from main project repo for everyone. And everyone works on their "dev" branch then sends a pull request to the main project repo's "dev" branch for merging.


Error was: Error: Server error code 500
{
  "error": {
    "code": 500,
    "message": "Internal error encountered.",
    "status": "INTERNAL"
  }
}

file:///Users/raz1ner/Downloads/google-indexing-script/src/shared/utils.mjs:17
      throw new Error(`Server error code ${response.status}\n${body}`);
            ^

Error: Server error code 500
{
  "error": {
    "code": 500,
    "message": "Internal error encountered.",
    "status": "INTERNAL"
  }
}

Sometimes unexpected errors occur during usage, so I have to start over and run it again. It would be great if, when an unexpected error occurs, the request causing the error could be resubmitted instead of stopping directly.

There’s a 3 retries per request already, but it seems like they all failed.
we could try using increasing to 5 and adding an exponential back off delay. Would you like to send a PR?


Second Contribution by Pamela Ropafadzo Pfunye

Name: Pamela Ropafadzo Pfunye
The projects you analyzed : InterpretML| PyTorch

Links:
Pytorch:
https://pytorch.org/docs/master/community/governance.html
https://ai.facebook.com/blog/pytorch-foundation/
InterpretML:
https://github.com/interpretml/interpret/blob/develop/GOVERNANCE.md
https://github.com/interpretml/governance/blob/master/org-governance.md
https://github.com/interpretml/governance
PyTorch and InterpretML are two popular open-source frameworks that offer tools to make it easier to create and train machine learning models.
SIMILARITIES

Ownership: Facebook owns PyTorch, while Microsoft owns InterpretML. The fact that these businesses own the libraries does not imply that they have influence over how the software is developed. To guarantee that the libraries are created and maintained in a sustainable way, they instead give resources and assistance to the development teams.
Governance body: Determines the project's course, evaluates and accepts community contributions, and monitors the library's security and quality. PyTorch has a Technical Steering Committee, whereas InterpretML has a Core development team
Development processes: all code modifications, problem complaints, and feature requests are accessible to everyone on GitHub. Regular community meetings are held at both libraries to talk about the project's direction and solicit user feedback

The libraries similarities demonstrate their commitment to openness, transparency, and community involvement, which are essential principles for the development of open-source software and sustainability.
DIFFERENCES

Governance structures: InterpretML has a more centralized governance structure, with decisions about the direction of the library being made by a small group of developers responsible for the core components of the library. In contrast, PyTorch has a more decentralized governance structure, with the PyTorch Technical Steering Committee providing oversight and guidance but leaving many decisions to the community of contributors and users.
Development Process: InterpretML has a more structured and formalized development process, while PyTorch has a more informal development process. InterpretML places more emphasis on formal review processes and clear guidelines for contributions, while PyTorch places more emphasis on community involvement and collaboration.
Community Involvement: PyTorch has a larger and more active community of users and contributors than InterpretML. This reflects the fact that PyTorch is a more general-purpose library with a wider range of use cases and applications, while InterpretML is a more specialized library focused on interpretability for machine learning models.

MY OPINION
Both governance models are successful and I believe the best model will depend on the size, scope, and goals of the project, as well as the culture and values of the community involved. InterpretML's more centralized governance structure may be more effective for a smaller and more specialized library focused on interpretability for machine learning models, while PyTorch's more decentralized governance structure may be more effective for a larger and more general-purpose library that provides tools for building and training deep neural networks.

@arliss-NF Looking forward to hearing your thoughts on my second contribution

@PamelaRopafadzo - excellent work.  Very well-organized and easy to read.  good level of content and use of bolding and indentation.  Very easy to read and is invaluable when one needs to review a lot of content.  Thank you.
Your "My Opinion" section is well written, and it's important to decide which one you prefer when you have a strong analysis to back up the decision.  Well done.


[Feature][Sort] Add timestamp startup mode to postgres source

Description
postgres source needs to start from a given checkpoint when task failure occurs. So these three options needs to be added to pg source and adapted.
'scan.startup.timestamp-millis' = '1691392566473',
'scan.startup.mode' = 'timestamp'
'server-time-zone' = 'Asia/Shanghai'
Use case
No response
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

this proves to be a huge change, implements pg split fetcher rn, should be done this week.


Added logic to parse Docker Registry URLs.

Ready for merge.
Signed-off-by: Jon Poler<EMAIL_ADDRESS>

@alextoombs Will you go over this briefly to discern if there are any glaring problems here?

@alextoombs Hopefully that is a little bit more readable. Let me know what you think. I will be changing the tests to table-driven tests as soon as I get a chance.

@alextoombs I'd like to merge this if you find that agreeable.

@olegshaldybin This needs to be merged before the continuum PR.

LGTM


can't search for-statement which use class member variable as threshold

I tried to use weggli on hexray C output and found some useful cases recently.
But I encounter a problem today and I think I need some help.
the problem is, I tried to find some function like below:
struct StructName *__fastcall ClassName::MethodName(ClassName *this, int a2)
{
  __int64 i; // r8
  struct StructName *result; // rax

  for ( i = 0i64; i < this->dword_80; ++i )
  {
    result = *(this->qword_88 + 8 * i);
    if ( a2 == *(result + 112) )
      return result;
  }
..
}

I could found above function with query below:
./target/release/weggli --cpp 'for(_; _ < this->dword_80; _) { _; }' ~/hexray_output.cpp

But, above query is using fixed member variable name so I couldn't exapand it to find another variant.
I tried following queries but none of them working as I want.
Queries with no-output
./target/release/weggli --cpp '_ $func(_* $thisptr) { for(_; _ < $thisptr->_; _) { _; } }' ~/hexray_output.cpp
./target/release/weggli --cpp '_ $func(_* $thisptr) { for(_; _ < $thisptr->dword_80; _) { _; } }' ~/hexray_output.cpp

./target/release/weggli -R 'thisptr=this|a1' --cpp '_ $func(_) { for(_; _ < $thisptr->dword_80; _) { _; } }' ~/hexray_output.cpp

./target/release/weggli --cpp '_ $func(_* $thisptr) { for(_; _ < _($thisptr)->_; _) { _; } }' ~/hexray_output.cpp

Queries with output
./target/release/weggli --cpp '_ $func(_* $thisptr) { for(_; _ < _($thisptr); _) { _; } }' ~/hexray_output.cpp

Output example:

__int64 __fastcall Func1(..., struct Struct1 *a2, ...)
{
  int v4; // er14
  int v7; // eax
  int v8; // ebx
  int v9; // ebx

// ...
    if ( v8 >= 0 )
    {
      if ( *(*(this + 932) + 112i64) )
      {
        for ( i = 0; i < *(a2 + 10); ++i ) // <- here
        {
         // ...

__int64 __fastcall Func2(
        struct Struct2 *a1,
        ....)
{
  __int64 v4; // rdi
...

  v4 = *(a1 + 5);
  v6 = a3;
  v7 = a2;
  updated = 0;
  for ( i = 0; i < *(*(a1 + 3) + 6i64); ++i ) // <- here
  {
    ...
}

only found i < (a1 + ...) , no output like i < a1->dword_80
./target/release/weggli -R 'thisptr=this|a1' --cpp '_ $func(_) { for(_; _ < _($thisptr); _) { _; } }' ~/hexray_output.cpp

This one found i < a1->dword_80 and similar member variable reference. But as you can see, it just use regex match instead of using this argument of class method. I want to find data flow from this argument  to for-loop.
If you have any free time, I will really appreciate to let me know what I am doing wrong.

FYI, my host OS is macOS BigSur.
> sw_vers
ProductName:	macOS
ProductVersion:	11.4
BuildVersion:	20F71

Thanks for the detailed bug report. I'll take a look! :)

tree-sitter returns a special AST node for 'this' so variable matching did not work correctly.
Commit 8e6d7a3 fixes the issue.
Thanks again for the report.

Thanks!


dep ensure -update

tion about a command.
socks-cli kelvin@gnux:~/gocode/src/zhtj$ dep ensure -update
ensure Solve(): No versions of gopkg.in/vmihailenco/msgpack.v2 met constraints:
v2.9.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.9.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.6.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.6.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.13: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.12: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.11: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.3.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.3.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2: Could not introduce gopkg.in/vmihailenco/msgpack.v2@v2, as it is not allowed by constraint master from project zhtj.

Could you please fill the issue template:

What version of Go (go version) and dep (git describe --tags) are you using?
What dep command did you run?
What did you expect to see?
What did you see instead?

And please add Gopkg.toml and Gopkg.lock content to give more insights to the issue.

go version: go version go1.9beta2 windows/amd64
windows: 10
i run dep ensure -update, then tips the errror
 kelvin@gnux:~/gocode/src/zhtj$ dep ensure -update
ensure Solve(): No versions of gopkg.in/vmihailenco/msgpack.v2 met constraints:
v2.9.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.9.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.8.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.7.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.6.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.6.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.5.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.13: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.12: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.11: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.3.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.3.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint master from project zhtj.
v2: Could not introduce gopkg.in/vmihailenco/msgpack.v2@v2, as it is not allowed by constraint master from project zhtj.

Gopkg.toml
## Gopkg.toml example (these lines may be deleted)

## "metadata" defines metadata about the project that could be used by other independent
## systems. The metadata defined here will be ignored by dep.
# [metadata]
# key1 = "value that convey data to other systems"
# system1-data = "value that is used by a system"
# system2-data = "value that is used by another system"

## "required" lists a set of packages (not projects) that must be included in
## Gopkg.lock. This list is merged with the set of packages imported by the current
## project. Use it when your project needs a package it doesn't explicitly import -
## including "main" packages.
# required = ["github.com/user/thing/cmd/thing"]

## "ignored" lists a set of packages (not projects) that are ignored when
## dep statically analyzes source code. Ignored packages can be in this project,
## or in a dependency.
# ignored = ["github.com/user/project/badpkg"]

## Constraints are rules for how directly imported projects
## may be incorporated into the depgraph. They are respected by
## dep whether coming from the Gopkg.toml of the current project or a dependency.
# [[constraint]]
## Required: the root import path of the project being constrained.
# name = "github.com/user/project"
#
## Recommended: the version constraint to enforce for the project.
## Only one of "branch", "version" or "revision" can be specified.
# version = "1.0.0"
# branch = "master"
# revision = "abc123"
#
## Optional: an alternate location (URL or import path) for the project's source.
# source = "https://github.com/myfork/package.git"
#
## "metadata" defines metadata about the dependency or override that could be used
## by other independent systems. The metadata defined here will be ignored by dep.
# [metadata]
# key1 = "value that convey data to other systems"
# system1-data = "value that is used by a system"
# system2-data = "value that is used by another system"

## Overrides have the same structure as [[constraint]], but supersede all
## [[constraint]] declarations from all projects. Only [[override]] from
## the current project's are applied.
##
## Overrides are a sledgehammer. Use them only as a last resort.
# [[override]]
## Required: the root import path of the project being constrained.
# name = "github.com/user/project"
#
## Optional: specifying a version constraint override will cause all other
## constraints on this project to be ignored; only the overridden constraint
## need be satisfied.
## Again, only one of "branch", "version" or "revision" can be specified.
# version = "1.0.0"
# branch = "master"
# revision = "abc123"
#
## Optional: specifying an alternate source location as an override will
## enforce that the alternate location is used for that project, regardless of
## what source location any dependent projects specify.
# source = "https://github.com/myfork/package.git"

[[constraint]]
  branch = "master"
  name = "github.com/labstack/echo"

[[constraint]]
  branch = "master"
  name = "github.com/labstack/gommon"

[[constraint]]
  branch = "master"
  name = "github.com/lestrrat/go-file-rotatelogs"

[[constraint]]
  branch = "master"
  name = "github.com/microcosm-cc/bluemonday"

[[constraint]]
  branch = "master"
  name = "golang.org/x/net"

[[constraint]]
  branch = "v2.0.0"
  name = "gopkg.in/fatih/pool.v2"

[[constraint]]
  name = "gopkg.in/go-playground/validator.v9"
  version = "9.3.6"

[[constraint]]
  branch = "master"
  name = "gopkg.in/vmihailenco/msgpack.v2"

Gopkg.lock
# This file is autogenerated, do not edit; changes may be undone by the next 'dep ensure'.

[[projects]]
  name = "github.com/Shopify/sarama"
  packages = ["."]
  revision = "c01858abb625b73a3af51d0798e4ad42c8147093"
  version = "v1.12.0"

[[projects]]
  name = "github.com/caarlos0/env"
  packages = ["."]
  revision = "0cf029d5748c52beb2c9d20c81880cb4bdf8f788"
  version = "v3.0"

[[projects]]
  name = "github.com/davecgh/go-spew"
  packages = ["spew"]
  revision = "346938d642f2ec3594ed81d874461961cd0faa76"
  version = "v1.1.0"

[[projects]]
  name = "github.com/dchest/captcha"
  packages = ["."]
  revision = "9e952142169c3cd6268c6482a3a61c121536aca2"

[[projects]]
  name = "github.com/dgrijalva/jwt-go"
  packages = ["."]
  revision = "d2709f9f1f31ebcda9651b03077758c1f3a0018c"
  version = "v3.0.0"

[[projects]]
  name = "github.com/eapache/go-resiliency"
  packages = ["breaker"]
  revision = "6800482f2c813e689c88b7ed3282262385011890"
  version = "v1.0.0"

[[projects]]
  branch = "master"
  name = "github.com/eapache/go-xerial-snappy"
  packages = ["."]
  revision = "bb955e01b9346ac19dc29eb16586c90ded99a98c"

[[projects]]
  name = "github.com/eapache/queue"
  packages = ["."]
  revision = "ded5959c0d4e360646dc9e9908cff48666781367"
  version = "v1.0.2"

[[projects]]
  name = "github.com/go-playground/locales"
  packages = [".","currency"]
  revision = "084b0226cf88d891a2bdeccac01d592af13a8f7b"

[[projects]]
  name = "github.com/go-playground/universal-translator"
  packages = ["."]
  revision = "b32fa301c9fe55953584134cb6853a13c87ec0a1"
  version = "v0.16.0"

[[projects]]
  name = "github.com/go-sql-driver/mysql"
  packages = ["."]
  revision = "a0583e0143b1624142adab07e0e97fe106d99561"
  version = "v1.3"

[[projects]]
  name = "github.com/gogo/protobuf"
  packages = ["io","proto"]
  revision = "100ba4e885062801d56799d78530b73b178a78f3"
  version = "v0.4"

[[projects]]
  branch = "master"
  name = "github.com/golang/protobuf"
  packages = ["proto"]
  revision = "c9c7427a2a70d2eb3bafa0ab2dc163e45f143317"

[[projects]]
  branch = "master"
  name = "github.com/golang/snappy"
  packages = ["."]
  revision = "553a641470496b2327abcac10b36396bd98e45c9"

[[projects]]
  name = "github.com/gorilla/context"
  packages = ["."]
  revision = "1ea25387ff6f684839d82767c1733ff4d4d15d0a"
  version = "v1.1"

[[projects]]
  name = "github.com/gorilla/mux"
  packages = ["."]
  revision = "bcd8bc72b08df0f70df986b97f95590779502d31"
  version = "v1.4.0"

[[projects]]
  branch = "master"
  name = "github.com/labstack/echo"
  packages = [".","middleware"]
  revision = "3673d7fb445de8bdfd7112097228fe7d77b0593b"

[[projects]]
  name = "github.com/labstack/gommon"
  packages = ["bytes","color","log","random"]
  revision = "779b8a8b9850a97acba6a3fe20feb628c39e17c1"
  version = "0.2.2"

[[projects]]
  branch = "master"
  name = "github.com/mattn/go-colorable"
  packages = ["."]
  revision = "ded68f7a9561c023e790de24279db7ebf473ea80"

[[projects]]
  branch = "master"
  name = "github.com/mattn/go-isatty"
  packages = ["."]
  revision = "fc9e8d8ef48496124e79ae0df75490096eccf6fe"

[[projects]]
  name = "github.com/micro/go-micro"
  packages = ["metadata"]
  revision = "8264e90bce1a035666c12f3cf136ce30757843ff"
  version = "v0.1.2"

[[projects]]
  branch = "master"
  name = "github.com/microcosm-cc/bluemonday"
  packages = ["."]
  revision = "e79763773ab6222ca1d5a7cbd9d62d83c1f77081"

[[projects]]
  branch = "master"
  name = "github.com/opentracing-contrib/go-stdlib"
  packages = ["nethttp"]
  revision = "48e4d763b2fbcd10e666e6a1742acdf8cc2286ef"

[[projects]]
  branch = "master"
  name = "github.com/opentracing/basictracer-go"
  packages = [".","wire"]
  revision = "1b32af207119a14b1b231d451df3ed04a72efebf"

[[projects]]
  name = "github.com/opentracing/opentracing-go"
  packages = [".","ext","log"]
  revision = "1949ddbfd147afd4d964a9f00b24eb291e0e7c38"
  version = "v1.0.2"

[[projects]]
  name = "github.com/pierrec/lz4"
  packages = ["."]
  revision = "5c9560bfa9ace2bf86080bf40d46b34ae44604df"
  version = "v1.0"

[[projects]]
  name = "github.com/pierrec/xxHash"
  packages = ["xxHash32"]
  revision = "f051bb7f1d1aaf1b5a665d74fb6b0217712c69f7"
  version = "v0.1.1"

[[projects]]
  branch = "master"
  name = "github.com/pkg/errors"
  packages = ["."]
  revision = "c605e284fe17294bda444b34710735b29d1a9d90"

[[projects]]
  branch = "master"
  name = "github.com/rcrowley/go-metrics"
  packages = ["."]
  revision = "1f30fe9094a513ce4c700b9a54458bbb0c96996c"

[[projects]]
  branch = "master"
  name = "github.com/shurcooL/httpfs"
  packages = ["vfsutil"]
  revision = "bc35257962c2dea93e81c976b72c7c6eac45fd8a"

[[projects]]
  branch = "master"
  name = "github.com/shurcooL/vfsgen"
  packages = ["."]
  revision = "385e5833a54aaba5860ca26036b8e8b72135ab96"

[[projects]]
  name = "github.com/urfave/cli"
  packages = ["."]
  revision = "d70f47eeca3afd795160003bc6e28b001d60c67c"

[[projects]]
  name = "github.com/valyala/bytebufferpool"
  packages = ["."]
  revision = "e746df99fe4a3986f4d4f79e13c1e0117ce9c2f7"

[[projects]]
  branch = "master"
  name = "github.com/valyala/fasttemplate"
  packages = ["."]
  revision = "dcecefd839c4193db0d35b88ec65b4c12d360ab0"

[[projects]]
  name = "github.com/wayn3h0/go-uuid"
  packages = [".","internal/dcesecurity","internal/layout","internal/namebased","internal/namebased/md5","internal/namebased/sha1","internal/random","internal/timebased","internal/version"]
  revision = "71e8f6f01226f577139a7b4f9c8161f7311d3bac"

[[projects]]
  name = "go.uber.org/atomic"
  packages = ["."]
  revision = "4e336646b2ef9fc6e47be8e21594178f98e5ebcf"
  version = "v1.2.0"

[[projects]]
  name = "go.uber.org/multierr"
  packages = ["."]
  revision = "3c4937480c32f4c13a875a1829af76c98ca3d40a"
  version = "v1.1.0"

[[projects]]
  name = "go.uber.org/zap"
  packages = [".","buffer","internal/bufferpool","internal/color","internal/exit","zapcore"]
  revision = "9d9d6135afe89b6fc4a05e9a8552526caba38048"
  version = "v1.5.0"

[[projects]]
  branch = "master"
  name = "golang.org/x/crypto"
  packages = ["acme","acme/autocert","blowfish"]
  revision = "e7ba82683099cae71475961448ab8f903ea77c26"

[[projects]]
  branch = "master"
  name = "golang.org/x/net"
  packages = ["context","html","html/atom"]
  revision = "59a0b19b5533c7977ddeb86b017bf507ed407b12"

[[projects]]
  branch = "master"
  name = "golang.org/x/sys"
  packages = ["unix"]
  revision = "b90f89a1e7a9c1f6b918820b3daa7f08488c8594"

[[projects]]
  branch = "master"
  name = "golang.org/x/tools"
  packages = ["godoc/vfs"]
  revision = "fcc44a6330868f7bdb7285effa1a0666eede46ac"

[[projects]]
  branch = "master"
  name = "google.golang.org/appengine"
  packages = [".","datastore","internal","internal/app_identity","internal/base","internal/datastore","internal/log","internal/modules","internal/remote_api"]
  revision = "170382fa85b10b94728989dfcf6cc818b335c952"

[[projects]]
  branch = "v2.0.0"
  name = "gopkg.in/fatih/pool.v2"
  packages = ["."]
  revision = "6e328e67893eb46323ad06f0e92cb9536babbabc"

[[projects]]
  name = "gopkg.in/go-playground/validator.v9"
  packages = ["."]
  revision = "6d8c18553ea1ac493d049edd6f102f52e618f085"
  version = "v9.3.6"

[[projects]]
  name = "gopkg.in/ini.v1"
  packages = ["."]
  revision = "d3de07a94d22b4a0972deb4b96d790c2c0ce8333"
  version = "v1.28.0"

[[projects]]
  name = "gopkg.in/natefinch/lumberjack.v2"
  packages = ["."]
  revision = "a96e63847dc3c67d17befa69c303767e2f84e54f"
  version = "v2.1"

[[projects]]
  name = "gopkg.in/olivere/elastic.v5"
  packages = [".","config","uritemplates"]
  revision = "edbef41beaacc2ee95e61af8faff04e67c01e268"
  version = "v5.0.45"

[[projects]]
  name = "gopkg.in/redis.v5"
  packages = [".","internal","internal/consistenthash","internal/hashtag","internal/pool","internal/proto"]
  revision = "a16aeec10ff407b1e7be6dd35797ccf5426ef0f0"
  version = "v5.2.9"

[[projects]]
  branch = "master"
  name = "gopkg.in/vmihailenco/msgpack.v2"
  packages = [".","codes"]
  revision = "f4f8982de4ef0de18be76456617cc3f5d8d8141e"

[[projects]]
  branch = "master"
  name = "sourcegraph.com/sourcegraph/appdash"
  packages = [".","httptrace","internal/wire","opentracing","sqltrace","traceapp","traceapp/tmpl"]
  revision = "5b9b70908c0e32b53e17215ee6e9515b02ad08b2"

[[projects]]
  branch = "master"
  name = "sourcegraph.com/sourcegraph/appdash-data"
  packages = ["."]
  revision = "73f23eafcf67cad684fba328dd545a116ac273ff"

[solve-meta]
  analyzer-name = "dep"
  analyzer-version = 1
  inputs-digest = "b7bb98aba5a6fbd4747d5a79b9fc4300832cfcd4fc3c9cb5f4948769687adf07"
  solver-name = "gps-cdcl"
  solver-version = 1

The errors are telling you the problem here, albeit with a fair bit of spam:

No versions of gopkg.in/vmihailenco/msgpack.v2 met constraints:

And your constraint is:

[[constraint]]
 branch = "master"
 name = "gopkg.in/vmihailenco/msgpack.v2"

gopkg.in is expressly designed to not allow the master branch through. it's not clear to me why it worked in the past (which it appears it did, as that's what's in your Gopkg.lock), but if you change your constraint to allow any of the 50+ versions that that project has published, then your problem should go away.

sir, i change constraint to the here
[[constraint]]
 branch = "master"
 name = "gopkg.in/vmihailenco/msgpack.v2"

to
[[constraint]]
  name = "gopkg.in/vmihailenco/msgpack.v2"
  version = "2"

then  use dep ensure update
dep ensure -update
ensure Solve(): No versions of gopkg.in/redis.v5 met constraints:
	v5.2.9: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 282.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.8: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly46.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.7: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly37.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.6: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 241.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.5: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly31.00 KiB/s
fatal: 过早的文件结束符（EOF）1.38 MiB | 231.00 KiB/s
fatal: index-pack failed

	v5.2.4: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly64.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.3: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly56.00 KiB/s
fatal: 过早的文件结束符（EOF）1.03 MiB | 256.00 KiB/s
fatal: index-pack failed

	v5.2.2: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly42.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.1: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly20.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.0: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly65.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.7: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly03.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.6: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly15.00 KiB/s
fatal: 过早的文件结束符（EOF）1.08 MiB | 415.00 KiB/s
fatal: index-pack failed

	v5.1.5: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 305.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.4: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 296.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.3: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 242.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.2: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 269.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.1: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly68.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.0: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly42.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.0.2: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly17.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.0.1: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly49.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.0.0: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly24.00 KiB/s
fatal: 过早的文件结束符（EOF）1.36 MiB | 324.00 KiB/s
fatal: index-pack failed

	v5: git://github.com/go-redis/redis does not exist in the local cache and fetching failed: unable to get repository: 正克隆到 '/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly15.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

thanks ,the problem is solved

The soft connection is so deep

that is unrelated, please open a new issue when you have a new problem.

"2" is not a valid semver constraint. it would match only a literal "2" git tag.
On August 3, 2017 5:12:21 AM EDT, sed<EMAIL_ADDRESS>wrote:

sir, i change constraint to the here
[[constraint]]
branch = "master"
name = "gopkg.in/vmihailenco/msgpack.v2"

to
[[constraint]]
 name = "gopkg.in/vmihailenco/msgpack.v2"
 version = "2"

then  use dep ensure update
dep ensure -update
ensure Solve(): No versions of gopkg.in/redis.v5 met constraints:
	v5.2.9: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 282.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.8: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly46.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.7: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly37.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.6: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 241.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.5: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly31.00 KiB/s
fatal: 过早的文件结束符（EOF）1.38 MiB | 231.00 KiB/s
fatal: index-pack failed

	v5.2.4: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly64.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.3: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly56.00 KiB/s
fatal: 过早的文件结束符（EOF）1.03 MiB | 256.00 KiB/s
fatal: index-pack failed

	v5.2.2: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly42.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.1: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly20.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.2.0: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly65.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.7: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly03.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.6: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly15.00 KiB/s
fatal: 过早的文件结束符（EOF）1.08 MiB | 415.00 KiB/s
fatal: index-pack failed

	v5.1.5: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 305.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.4: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 296.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.3: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 242.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.2: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly 269.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.1: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly68.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.1.0: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly42.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.0.2: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly17.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.0.1: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly49.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

	v5.0.0: git://github.com/go-redis/redis does not exist in the local
cache and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly24.00 KiB/s
fatal: 过早的文件结束符（EOF）1.36 MiB | 324.00 KiB/s
fatal: index-pack failed

	v5: git://github.com/go-redis/redis does not exist in the local cache
and fetching failed: unable to get repository: 正克隆到
'/home/kelvin/gocode/pkg/dep/sources/git-gopkg.in-redis.v5'...
remote: Counting objects: 3805, done.
remote: Compressing objects: 100% (7/7), done.
fatal: The remote end hung up unexpectedly15.00 KiB/s
fatal: 过早的文件结束符（EOF）
fatal: index-pack failed

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/golang/dep/issues/932#issuecomment-319913974


Support changing color mode at runtime

That TOML11_COLORIZE_ERROR_MESSAGE cannot change color mode at runtime is not useful when we want to accept arguments from users. Considering supporting the --color option on my command line application, I would implement it like:
std::vector<std::string> args(argv + 1, argv + argc);
auto result = std::find(args.begin(), args.end(), "--color");
if (result != args.end()) {
    // enable colorization
} else {
    // disable colorization
}

For such cases, I implemented functions that allow users to control the color mode by just calling these functions.
toml::color::enable();  // enable colorization
toml::color::disable(); // disable colorization

When we want to know the current color mode, call the should_color function:
if (toml::color::should_color()) {
    // ...
}

When we use user-defined error message, we can manage the setting as follows:
toml::color::enable();
std::cerr << toml::format_error("[error] value should be positive",
                                data.at("num"), "positive number required",
                                hints) << std::endl; // colorized
toml::color::disable();
std::cerr << toml::format_error("[error] value should be positive",
                                data.at("num"), "positive number required",
                                hints) << std::endl; // NOT colorized

The value of toml::color::should_color() is set to TOML11_COLORIZE_ERROR_MESSAGE by default so as not to break existing software using toml11.

Sorry for having not been able to follow your coding style, but I fixed the code as reviewed.

@ToruNiina, Could you please re-review this PR when you have enough time?

Thank you for your review! :)


Better variables scoping

And some minor indentation fixes,
see https://github.com/openlayers/openlayers/pull/7697#issuecomment-357170584

I'll merge this now so we can base other work on it.


Improve peer send queue management:

Disconnect peers on sustained large send queues
Disconnect peers on sustained failure to pong
Refuse some queries if send queue is at target
Allow latency to exceed ping timer interval

This fixes two bugs in the existing peer timer handling code. One was the incorrect logic to determine whether the timer was being set for the first time which could result in peers timing out too quickly. The other was the incorrect ping sequence reset logic which would cause the latency measuring to fail if the latency was greater than the timer interval.
There are two key bits of new behavior. One is the disconnection of peers that don't respond to our pings in a timely way. This catches cases where there's excessive queue lengths on the peer-to-peer connections.
The biggest is the dropping of ledger queries when our send queue is large. Without this change, large queues can result in slow responses, leading to timeouts, leading to more aggressive querying, leading to larger queues, causing a meltdown resulting in the connection being dropped. By dropping the queries (rather than replying when we know the other side will get the reply late), the other side still times out, but the queue shrinks because we didn't reply, leading to the problem resolving rather than getting worse.

I had a non-essential const suggestion, but other than that the code looks fine as far as I can tell.  :+1:

:+1:


Add more maintainers

It seems that you don't have time to maintain this repository. This crate is a "core" with a big count of downloads. Please consider adding more maintainers.
I sent two PRs modernizing the code:

https://github.com/chyh1990/yaml-rust/pull/159
https://github.com/chyh1990/yaml-rust/pull/158

cc @dtolnay

Hi @XVilka, thanks for the PRs!
If you are interested in maintaining, I would recommend publishing your fork under a different crate name. I think the community would appreciate having a maintained fork; it doesn't have to be this repo.

We would use the fork in clap v2 if our security PR gets merged.

@pksunkara No, we wouldn't. Switching to a fork would mean that Yaml types became different, exactly the reason we can't just bump it to yaml-rust 0.4.
I suggested to switch to a fork of yaml-rust clap 3.0 was because depending on something that's being maintained is way better than depending on something unmaintained.
@XVilka Are you looking forward to forking and maintaining the repo on you own? If not, I would go ahead and do that myself.

@CreepySkeleton sadly no time for this, I am already scattered among many projects.

@XVilka did you get any updates on this issue? I see that your 2 PRs ended up being merged.

Is this project still maintained?  @chyh1990 @XVilka  or is there a maintained fork?

@olalonde not that I am aware of. Maybe @dtolnay could suggest an alternative.

I am not aware of a maintained fork.

My (previously) maintained fork (yaml-rust-davvid` @ crates.io) has merged efforts with @Ethiraric's fork as of https://github.com/Ethiraric/yaml-rust2/pull/2.
yaml-rust users should switch over to the actively maintained yaml-rust2 project ~ https://github.com/Ethiraric/yaml-rust2 (yaml-rust2 @ crates.io).
Upgrading from yaml-rust
Use this Cargo.toml snippet to use yaml-rust2 as a drop-in replacement for yaml-rust:
[dependencies]
yaml-rust = { version = "0.6", package = "yaml-rust2" }

This allows you to switch to yaml-rust2 while continuing referring to yaml_rust in your code (e.g. use yaml_rust::YamlLoader; will continue to work so that no Rust code changes are required).

My (previously) maintained fork (yaml-rust-davvid` @ crates.io) has merged efforts with @Ethiraric's fork as of Ethiraric#2.
yaml-rust users should switch over to the actively maintained yaml-rust2 project ~ https://github.com/Ethiraric/yaml-rust2 (yaml-rust2 @ crates.io).
Upgrading from yaml-rust
Use this Cargo.toml snippet to use yaml-rust2 as a drop-in replacement for yaml-rust:
[dependencies]
yaml-rust = { version = "0.6", package = "yaml-rust2" }

This allows you to switch to yaml-rust2 while continuing to refer to yaml_rust in your code (e.g. use yaml_rust::YamlLoader; will continue to work so that no Rust code changes are required).

I have a direct dependency on config v0.13 in my project, so I have a transient dependency on yaml-rust v0.4.5.
I am using cargo deny check advisories to check for any advisories (including unmaintained advisories) in my CI. Since yaml-rust is unmaintained, that step in the CI fails.
I want to replace the transient dependency on yaml-rust with yaml-rust2 v0.7.0
I have tried the following 2 things but they both fail to replace yaml-rust.
1.
[patch.'https://github.com/chyh1990/yaml-rust']
yaml-rust2 = { git = 'https://github.com/Ethiraric/yaml-rust2.git' }

[patch.crates-io]
yaml-rust = { git = 'https://github.com/Ethiraric/yaml-rust2.git' }

Am I doing something wrong?
My Cargo.toml is here


Decode a transaction from binary/string

Not sure if there is an available method to parse it from a string. But we could implement from_bytes() method, which would correspond to the read() one in librustzcash.

Okay, the from_bytes() was implemented here Moving this for review now :fast_forward:


add IRISZOOM

SteamDB app page links to a few games using this

Act of Aggression
R.U.S.E.
Steel Division 2
Steel Division: Normandy 44
Wargame: Airland Battle
Wargame: European Escalation
Wargame: Red Dragon
WARNO

Brief explanation of the change
should be the last pr for a while

After running changed rules in this pull request (this bot only tests rules.ini changes):
Changed technologies: Engine.IRISZOOM
These apps now match: (11) 21970 33310 58610<PHONE_NUMBER>30<PHONE_NUMBER>20<PHONE_NUMBER>10<PHONE_NUMBER>600
Please confirm that all these changed apps are correct.

sorry, didnt get the notification for the change request


check to see if any tests touch these funcs

Describe your changes and provide context
Testing performed to validate your change

Codecov Report
Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 61.50%. Comparing base (cbe2957) to head (ef39226).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1574      +/-   ##
==========================================
+ Coverage   60.94%   61.50%   +0.55%
==========================================
  Files         366      366
  Lines       26020    26021       +1
==========================================
+ Hits        15858    16003     +145
+ Misses       9159     8952     -207
- Partials     1003     1066      +63

Files
Coverage Δ

x/evm/client/wasm/query.go
41.00% <0.00%> (+25.93%)
:arrow_up:

... and 2 files with indirect coverage changes


image overlay

How I can add image overlay in GStreamer application to pipeline ? Thanks in advance.
var image = ElementFactory.Make("gdkpixbufoverlay");
image["location"] = @"D:\camera.png";
image["overlay-height"] = 200;
image["overlay-width"] = 200;
image["offset-x"] = 100;
image["offset-y"] = 100;
pipeline.Add(image);
What is missing?
StackOverflow can't help. Maybe you can.

Did you get this working? I think you need a call to SyncStateWithParent(). I'm assuming you're linking things properly.
This works for me:
            var img = ElementFactory.Make("gdkpixbufoverlay");
            img["location"] = @"C:\gstreamer\1.0\x86\bin\test.png";
            img["overlay-height"] = 200;
            pipeline.Add(img);
            var ret = tPrev.Link(img.GetStaticPad("sink"));
            if(ret != PadLinkReturn.Ok)
            {
                sysDbg.WriteLine("Error linking image overlay.");
            }
            img.SyncStateWithParent();
            tPrev = img.GetStaticPad("src");


Changing a feed's charset not being reflected in data preview pane

Import this file into a feed that is set with a charset of ISO8859-1.
It should display correctly in data preview.
In the feed settings set the charset to utf8 then refresh the data preview.
It should now correctly show the orange banner saying it can't decode it.
Change the feed settings back to ISO8859-1 and refresh the data preview.
It still says it can't decode it as utf8.
It should pick up the change of charset.
iso8859-1.txt

Fixed in >7.0.1


Required Arguments

> az ad app create --display-name my-nativ
leaves me with '--identifier-uris' is required for creating an application although the documentation states that only --display_name is required.

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

ID: 921aa920-c25f-5227-aabb-49116da38fa7
Version Independent ID: 9b5a53ad-edf8-4d89-f8e6-cde01b7866f6
Content: az ad app
Content Source: src/command_modules/azure-cli-role/azure/cli/command_modules/role/_help.py
Service: active-directory
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

--display-name is required in all cases.  Depending on the option you provide, --identifier-uris may or may not be required.


[Accessibility] For easier code navigation, add jump to next/previous param within a function

CC @isidorn
When a function gets nested or contains many params, it is challenging for screen reader users to navigate the code structure.
could you please consider adding a feature allowing users to quickly jump to next and previous param within a function? It would be also great if we had a feature to go to the first and last param within a function.
In the following example, I would like to jump between params when my cursor is at anywhere in the function bar definition:
function foo(a = 1; b = "something", function(x) {...}, c = NULL) {
  print("Hello world!");
}

@jooyoungseo thanks for filling this feature request. Even though it would benefit accessibility, I think it is a general feature request towards parameter navigation. Thus for starts assigning to @mjbvz and @jrieken to hear their thoughts.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


fix(opentrons-ai-client): backtick is properly rendered

Currently backtick was rendered as a new line rather than inline
Please see the attached which shows the correct one

Closes AUTH-432

Overview

Test Plan
Choose examples and send to ChatDisplay and verify.

Changelog

Review requests

Risk assessment
Low

Closed since it is related to https://github.com/Opentrons/opentrons/pull/15324


test: remove LTP

LTP binaries and scripts can be added in the deriving container. This
container should only include fiotest utilities and a simple test script
example.
Signed-off-by: Milosz Wasilewski<EMAIL_ADDRESS>

@doanac I removed the kernel tests and added a simple script that executes some commands as 'tests'. Let's use this as reference. Also README was updated with example on how to extend the container.

no. i'd approved the changes. i'll just merge it now.


Add application context

This context allows the LLM to understand context relevant questions
For example, when you use 'model ask' in slack, it knows that you might be asking about slack messages. When you use it inside of Jira, it knows that you might be interested in jira tickets

I think it helps the LLM understand that each of these is a different topic.


Looking to address MetroEast MVP project issues #2 and #3, ability to run via AutoPkgr without external launchd scripts

This is our first go at changes to the Processors.  We aimed to retain the original functionality, while adding optional arguments which allow for scheduling of patch and production processing.
MVP-2: Remove dependence on LaunchDaemons (use AutoPkgr)
MVP-3: Integrate 'Move' recipe into Production.py

This PR is just too big to swallow. I'm going to go through and add parts of it one by one over the next week or so.

Thanks or giving it a go…  I've now merged this into the master branch of our fork, it's working for us, so far.  The small salt mine for that, is that we've only got 3 titles in our system.  another 40+ to go.


How to get error information before link is closed?

Hi,
We are experiencing issues trying to support users using the link flow due to a flow on-effect of issue #139.
Periodically, users will experience errors when trying to link their accounts, particularly when using microdeposits which some people find confusing.
In order to assist these users we would like to be able to collect any information they experienced during their link flow, however, the error events are only fired once link is closed - the problem being is that users will often just not close link at all (especially on mobile devices), they will just close the entire tab/browser or just navigate away from their browser and contact us for support.
This leaves us somewhat in the dark. To compound this, Plaid support will not assist unless we provide a link or request id, but again AFAIK, these are obtained on the client side from the events as well.
Is there any other method to get Plaid error information if the user never gets through the flow to the point where they would send requests to our servers?
Alternatively, if there is no other way to get this information, I understand there might be some business reasons behind delaying link events, but would it possible to make an exception for errors events?

Hi @ls-smock-recruit. Link always immediately fires the onEvent callback with the OPEN event when it first initializes. This event contains a link_session_id so you can capture that no matter what the user does within Link.
If a user abandons the page before exiting Link (thus onSuccess or onExit never fire), you can search the link_session_id in the dashboard under the Logs page, and all the logs for that session will appear there. You can also search the Logs page by client_user_id that was supplied to the /link/token/create call so you don't even need to know the link_session_id if you fail to capture it. Here is an example of an error I triggered an then closed the tab without exiting Link:

If this does not solve your use case feel free to chat with Plaid support!

@skylarmb Thanks for getting back to me on this, appreciated - will forward this info on.


[SPARK-41936][CONNECT][PYTHON] Make withMetadata reuse the withColumns proto

What changes were proposed in this pull request?
https://github.com/apache/spark/pull/39432 added a new proto WithMetadata, which is not necessary, since we can reuse WithColumns which also can carry the metadata.
This PR enhance withColumns to also support withMetadata
Why are the changes needed?
to remove unnecessary proto
Does this PR introduce any user-facing change?
no, dev-only
How was this patch tested?
existing UT

merged into master


overnight tests are failing: bst-experimantal-plugins doesn't include collect_manifest required version

See original issue on GitLab
In GitLab by [Gitlab user @jjardon] on Dec 15, 2019, 17:43
Job #379530820 failed for 2fc5a5cfbcf5c16407914849ea1a99bfdb71cb0e:

In GitLab by [Gitlab user @jjardon] on Feb 1, 2020, 14:28
mentioned in merge request !1811

In GitLab by [Gitlab user @jjardon] on Feb 1, 2020, 14:28
mentioned in merge request !1811

In GitLab by [Gitlab user @jjardon] on Feb 1, 2020, 14:28
Fixed by !1811

In GitLab by [Gitlab user @jjardon] on Feb 1, 2020, 14:28
Fixed by !1811

In GitLab by [Gitlab user @jjardon] on Feb 1, 2020, 14:28
closed

In GitLab by [Gitlab user @jjardon] on Feb 1, 2020, 14:28
closed