Error when linking against libraptor.a on nightly test machines

= Description =

The following error is returned when building the project on MPI3:
{{{
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../lib/libraptor.a(raptor_parse.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC
}}}
A similar error is returned when linking libexpat.a; linker should link against dynamic libraries instead of static.

= Success criteria =

No more linking errors on all machines.

= Expected issues =

Portability issues.

Imported from trac issue 55.  Created by bmoreau on 2014-09-17T14:19:55, last modified: 2015-01-20T17:20:28


Support for QuantumRegister in gates supporing qubits

This PR adds support to gates which support qubits to also accept full register, as the spec defines.
Description
The gates that take one or more qubit as args, should also support the full QuantumRegister as argument. For example: circuit.h(self.qr). The PR also extends the tests for the added code (and more).
Motivation and Context
Trying to write a test for #352 (and #362) I ended up falling the rabbit hole of supporting QuantumRegisters as arguments in the gates that operate over qubits. I noticed that many of the gates had this feature broken.
The most notable cases are:

The type of arguments in barrier are extended, in order to behave more similarly to other gates. In addition to the previous *list, now QuantumRegister are supported, also in combination with qubits. Also, if None is passed, it applied the barrier to every QuantumRegister of the circuit (this was a TODO in the code).
The specification the semantics of cx when is called with register and bits (Fig 2, page 4). This semantic is now supported.
The gates cx_base and swap are analogue to cx.
The specification do not define the semantics for ccx when called with registers. Therefore, I only included the intuitive case in which all the arguments are registers (with the same length): ccx q,r,s => ccx q[0],r[0],s[0];ccx q[1],r[1],s[1]; when length is 2.
The cswap case is analogue to ccx.

BTW, this PR closes #352.
How Has This Been Tested?
make test
The added tests extend the coverage with respect the existing tests:

file
previous stms
previously covered
new stms
now covered

qiskit/extensions/standard/init.py
28
100%
28
100%

qiskit/extensions/standard/barrier.py
45
78%
40
98%

qiskit/extensions/standard/ccx.py
25
100%
32
100%

qiskit/extensions/standard/ch.py
30
87%
40
100%

qiskit/extensions/standard/crz.py
32
88%
42
100%

qiskit/extensions/standard/cswap.py
20
100%
27
100%

qiskit/extensions/standard/cu1.py
32
88%
42
100%

qiskit/extensions/standard/cu3.py
37
89%
47
100%

qiskit/extensions/standard/cx.py
30
87%
40
100%

qiskit/extensions/standard/cxbase.py
23
100%
40
100%

qiskit/extensions/standard/cy.py
30
87%
40
100%

qiskit/extensions/standard/cz.py
30
87%
40
100%

qiskit/extensions/standard/gatestools.py
12
0%
12
0%

qiskit/extensions/standard/h.py
27
85%
32
88%

qiskit/extensions/standard/header.py
5
100%
5
100%

qiskit/extensions/standard/iden.py
27
85%
27
100%

qiskit/extensions/standard/rx.py
29
86%
29
100%

qiskit/extensions/standard/ry.py
29
86%
29
100%

qiskit/extensions/standard/rz.py
29
86%
29
100%

qiskit/extensions/standard/s.py
33
88%
33
100%

qiskit/extensions/standard/swap.py
23
100%
40
100%

qiskit/extensions/standard/t.py
33
88%
33
100%

qiskit/extensions/standard/u0.py
27
52%
27

qiskit/extensions/standard/u1.py
29
86%
29
100%

qiskit/extensions/standard/u2.py
33
88%
33
100%

qiskit/extensions/standard/u3.py
34
88%
34
100%

qiskit/extensions/standard/ubase.py
27
100%
34
100%

qiskit/extensions/standard/x.py
27
85%
27
100%

qiskit/extensions/standard/y.py
27
85%
27
100%

qiskit/extensions/standard/z.py
27
85%
27
100%

None of the changes brake backward compatibility.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Can you revise the test that is failing in Appveyor? It seems the order of the parameters for barrier is different depending on the os or the version:
AssertionError: 'barrier q[0],q[1],q[2],r[0],r[1],r[2],s[0],s[1],s[2];' not found in 'OPENQASM 2.0;\ninclude "qelib1.inc";\nqreg q[3];\nqreg r[3];\nqreg s[3];\ncreg c[3];\nbarrier q[0],q[1],q[2],s[0],s[1],s[2],r[0],r[1],r[2];\n'

Thanks @1ucian0 !


Refactoring the base project.

All commits are grouped in this PR.
This is WIP version, the build won't be successful. Tests should be updated, and will be addressed in the next PR.

Updates for unit and integration tests added to this PR.


Syntax error for DANA payment

Hi, my DANA e-Wallet has been activated by Xendit today. However, I tried to request payment with DANA e-Wallet and got another
syntax error, unexpected '='
[$rbody, $rcode, $rheaders] = $this->_httpClient()->sendRequest(
as encountered in a previous issue. I am using PHP 7.3 and xendit-php 2.3.1. I have also tried to update to xendit-php 2.4.1 but encountered another error as shown below.

Here is a small reproducible snippet of my code:
Xendit::setApiKey("xnd_production_ShitO****");
        $danaParams = [
            'external_id' => '020'.time(),
            'amount' => 10000,
            'phone' => '082112884647',
            'expiration_date' => '2020-05-14T00:00:00.000Z',
            'callback_url' => 'https://devtake.holywings.id/callbacks',
            'redirect_url' => 'https://devtake.holywings.id/',
            'ewallet_type' => 'DANA'
        ];

        $createDana = \Xendit\EWallets::create($danaParams);
        var_dump($createDana);

I have asked one of the developers in our team to have a look at the issue, and he made a pull request for this issue as a temporary fix. Please have a look.


Question about fine tuning

Sorry for disturbing. I have some problem on fine tuning with pretrained parameters.
I tried to fine tune the ShapeNet55 PoinTr on a specific "Bench" subset of ShapeNet. What I do it extracting the subset data, use the pretrained PoinTr model that you have provided and rename it as weight.pth. Then run:
bash ./scripts/train.sh 0     --config ./cfgs/ShapeNet55_models/PoinTr.yaml     --exp_name example --start_ckpts ./weight.pth
however, the loss does not goes down and the value of prediction after training ranges from ~10e-5 to 10e5, which is non-sense.
Did I do anything wrong? If not, is there any other method that I can fine tune the pretrained model on a specific dataset?

Hi, how do you construct the "bench" subset? And if all the problems come from the training phase, i think the discussion (https://github.com/yuxumin/PoinTr/issues/51) will help.

I construct the bench subset by getting the .npy files with corresponding object id from the training/testing data that download from google drive. Do you think it is fine?
I set the batch size to 16 since I am training on a local computer with GTX 1050Ti. I go through the previous discussion and it seems that the LR has to be changed too? Do you think multiplying the original LR by (original BS)/(new BS) works?

Have you taken a look at the tensorboard? I guess you encounter the problem as the issue i mentioned above (losses blow up).


Dev add agdarsec

Motivation for this change
Add the https://github.com/gallais/agdarsec/ library to nixpkgs
u
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@alexarice

I'm currently having trouble to build:
nix-repl> :b agdaPackages.agdarsec
builder for '/nix/store/bwfq8fswhs2l9a65zkh9yranhpv331q5-agdarsec-v0.3.0.drv' failed with exit code 1; last 10 log lines:
  building
  Checking index (/build/source/index.agda).
   Checking Text.Parser.Types (/build/source/src/Text/Parser/Types.agda).
   Checking Text.Parser.Combinators (/build/source/src/Text/Parser/Combinators.agda).
    Checking Induction.Nat.Strong (/build/source/src/Induction/Nat/Strong.agda).
    Checking Data.List.Any (/nix/store/vrr50yf58l2k36vw9clm43hfahn7msfh-standard-library-1.3/src/Data/List/Any.agda).
  Failed to write interface /nix/store/vrr50yf58l2k36vw9clm43hfahn7msfh-standard-library-1.3/src/Data/List/Any.agdai.
  /build/source/src/Text/Parser/Combinators.agda:17,8-28
  /nix/store/vrr50yf58l2k36vw9clm43hfahn7msfh-standard-library-1.3/src/Data/List/Any.agdai:
  openBinaryFile: permission denied (Permission denied)
[0 built (1 failed)]
error: build of '/nix/store/bwfq8fswhs2l9a65zkh9yranhpv331q5-agdarsec-v0.3.0.drv' failed

Strangely, it wants to recheck standard library files. Any idea why it might want to do that? Maybe agdarsec changes some build flag in a way that causes recompilation?

I think this suggests that something in standard library is not being compiled

@alexarice You're right!
$ ls /nix/store/vrr50yf58l2k36vw9clm43hfahn7msfh-standard-library-1.3/src/Data/List/Any.*
/nix/store/vrr50yf58l2k36vw9clm43hfahn7msfh-standard-library-1.3/src/Data/List/Any.agda
$ cat /nix/store/vrr50yf58l2k36vw9clm43hfahn7msfh-standard-library-1.3/Everything.agda | grep List.Any
-- Data.List.Any.Membership instantiated with propositional equality,

It seems the everything file is generated incorrectly.

See https://github.com/agda/agda-stdlib/blob/master/src/Data/List/Any.agda.
The issue is that agdarsec relies on a deprecated module in standard library, and deprecated modules aren't built. Likely agdarsec needs updating to use the undeprecated module

Hah. After monkey-patching Data.List.Any into the everything file, I get:
$ nix repl .
Welcome to Nix version 2.3.7. Type :? for help.

Loading '.'...
Added 12573 variables.

nix-repl> :b agdaPackages.agdarsec
builder for '/nix/store/qa9hmr88h2ib9zc5qf06kb909a1mqibd-standard-library-1.3.drv' failed with exit code 1; last 10 log lines:
    Checking Text.Tabular.Vec (/build/source/src/Text/Tabular/Vec.agda).
   Checking Text.Tree.Linear (/build/source/src/Text/Tree/Linear.agda).
   Checking Data.List.Any (/build/source/src/Data/List/Any.agda).
  /build/source/Everything.agda:1985,1-21
  Data.List.Any was deprecated in v1.0.
  Use Data.List.Relation.Unary.Any instead.
  when scope checking the declaration
    import Data.List.Any

So it's actually a deprecation warning.

@alexarice Yes, right. This is fixed on master I think.

@turion do you think it is a good idea to use master, then?

@AndersonTorres It would be ok in principle until the next release, but unfortunately master doesn't work out of the box either because of version mismatches. I'm working on a workaround.

I'm currently stuck on this error:
nix-repl> :b agdaPackages.agdarsec
builder for '/nix/store/djhsxg2av3g3wdvbcimq29dj0j602hkf-agdarsec-v0.3.0.drv' failed with exit code 1; last 10 log lines:
    /nix/store/1b7jp08xlcbvankbf8aml162zmid00la-standard-library-1.4/src/Expr.agda
    /nix/store/1b7jp08xlcbvankbf8aml162zmid00la-standard-library-1.4/src/Expr.lagda
    /build/source/src/Expr.agda
    /build/source/src/Expr.lagda
    /build/source/Expr.agda
    /build/source/Expr.lagda
    /nix/store/vkm07q5a493h356zmlqzvn7sxc4r0wwv-Agda-<IP_ADDRESS>-data/share/ghc-8.10.2/x86_64-linux-ghc-8.10.2/Agda-<IP_ADDRESS>/lib/prim/Expr.agda
    /nix/store/vkm07q5a493h356zmlqzvn7sxc4r0wwv-Agda-<IP_ADDRESS>-data/share/ghc-8.10.2/x86_64-linux-ghc-8.10.2/Agda-<IP_ADDRESS>/lib/prim/Expr.lagda
  when scope checking the declaration
    import Expr
[1 built (1 failed), 0.0 MiB DL]
error: build of '/nix/store/djhsxg2av3g3wdvbcimq29dj0j602hkf-agdarsec-v0.3.0.drv' failed

See https://github.com/gallais/agdarsec/issues/21.

@alexarice @neosimsim do you want to have a look? I also extended the build support a little. Now you can add the -i option (include paths) through nix.

@ofborg build agdaPackages.agdarsec
@ofborg test agdaPackages.standard-library.passthru.tests

@ofborg build agdaPackages.agdarsec
@ofborg test agdaPackages.standard-library.passthru.tests

@ofborg build agdaPackages.agdarsec
@ofborg test agdaPackages.standard-library.passthru.tests

@alexarice @SuperSandro2000 fine like this?

Looks fine to me. I'm surprised we haven't hit the include path problem before. Maybe we should do things like include the stdlib readmes? (this an be a separate pr)


Display Issue in detail grid in panel

I have a panel showing data from a dialog.
the detail grid does not shows data correctly as show below

but if we try and adjust column width it starts showing data.

can someone please guide me what might be causing this problem.

Try to refresh grid after data loading.  yourGrid.refresh()

If refreshing doesn't work, as this is a slickgrid rendering related issue due to how elements are first created... Try to use
this.yourDetailGrid.slickGrid.invalidateAllRows();
this.yourDetailGrid.slickGrid.render();
Best Regards

problem can be seen in
http://serenity.is/demo/BasicSamples/EntityDialogAsPanel/11077
also.
I have tried both suggestions by @edson  and @Estrusco  in afterLoadEntity but without any success.

I see.
Use
this.form.DetailList.element.triggerHandler('layout');

Best Regards

Thanks @edson it worked for me as well.


[SPARK-11871] Add save/load for MLPC

https://issues.apache.org/jira/browse/SPARK-11871
Here is a problem. Unlike other models in ML package extend from XXXParams as with their estimators, the MultilayerPerceptronClassificationModel does not extend from the MultilayerPerceptronParams. So we cannot test all parameters in the test suite because the MultilayerPerceptronClassificationModel plains for not finding the parameters such as maxIter, layers.
However, it is reasonable because users do not need to set those parameters in a MLPC model. But the inconsistency with other models makes the test suite different. Maybe I can split the testEstimatorAndModelReadWrite  into two parts in the test suite. I.e. test the estimator and model seperately. @mengxr

Test build #46389 has started for PR 9854 at commit 949db73.

Test build #46389 has finished for PR 9854 at commit 949db73.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  *   class MultilayerPerceptronClassificationModelWriter(\n

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46389/
Test PASSed.

Pls ignore my first comment, I have splited the test of model and classifier separately.

Test build #46478 has started for PR 9854 at commit 881428f.

Test build #46478 has finished for PR 9854 at commit 881428f.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  *   class MultilayerPerceptronClassificationModelWriter(\n

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46478/
Test PASSed.

Test build #46606 has started for PR 9854 at commit 5b852cd.

Test build #46606 has finished for PR 9854 at commit 5b852cd.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  *   class MultilayerPerceptronClassificationModelWriter(\n

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46606/
Test PASSed.

Merged build finished. Test PASSed.

cc @avulanov

LGTM

@mengxr @jkbradley I change the version code. Does it looks good to you?

Test build #48935 has started for PR 9854 at commit d0e517f.

Test build #48935 has finished for PR 9854 at commit d0e517f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48935/
Test PASSed.

I'll take a look now!

Test build #2624 has started for PR 9854 at commit d0e517f.

In the meantime, could you please update the description (to be a reasonable commit message)?  Thanks

Test build #2624 has finished for PR 9854 at commit d0e517f.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

The style issue & those little comments are the only items I see.  Thanks!

test it please

Test build #52802 has started for PR 9854 at commit 9352e77.

Test build #52802 has finished for PR 9854 at commit 9352e77.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52802/
Test FAILed.

test it please

Test build #52804 has started for PR 9854 at commit 68570e9.

Test build #52804 has finished for PR 9854 at commit 68570e9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52804/
Test PASSed.

Merged build finished. Test PASSed.

@jkbradley Fixed.

@jkbradley Is this looks good now?

test this please

Test build #54091 has started for PR 9854 at commit 68570e9.

Test build #54091 has finished for PR 9854 at commit 68570e9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54091/
Test PASSed.

LGTM. Merged into master. Thanks!

Thanks!

Send #11952 for Python API.


Is it possible to register custom shortcodes?

I see a registerShortcodes method in the code but I don't see a registerShortcodes hook?
Is there a way to register a custom shortcode from another plugin?

Shortcode registration is event driven and not hook driven. This allows Doxter to wait until the last second to load shortcodes. Instead of defining a method in your plugin, you listen for the before shortcode parsing event and then call doxter()->registerShortcodes()
You can see DoxterPlugin::init() for an example.


[v6 rc4] props are not passed from  to native input

props like "placeholder" and "type" are not passed to ...field.input
Eg.:
const InputText = field =>

        <input {...field.input} />
        {field.meta.touched && field.meta.error &&  {field.meta.error}}

<Field name="foo" placeholder="my placeholder" type="password"  component={InputText} />
produces:
<input name="foo" />

According to the RC4 release notes, the `placeholder

For additional reading on what is passed in props.input, check out the most recent docs on input props.

Interesting decision here. Why wouldn't extra props just be merged in with the input props? Now we have to explicitly pass props or use both { ...field } and { ...field.input }. I assume the tradeoff is that you don't have to destructure props if you're rendering more than a single input?
How I'm doing it now:

@echenley  or you can use https://github.com/erikras/redux-form-material-ui

sorry guys, I don't RTFM :/
So @echenley , it's boring make this treatment, everything should be a single place.
I was using V6RC3 and work, but now...
So, thanks @raygesualdo  and everyone!
(sorry for my bad english)


cmd/compile/ssa: conditional select instructions

Consider: (from https://go-review.googlesource.com/c/54656)
	if B > 15 {
		B = 15
	}

Right now, the best the amd64 backend could do for this basic block is generate a conditional branch forward over the B = 15 statement. Ideally, though, we'd have it generate a CMOV instead.
EDIT (after some experimentation):
Here's my proposal:
Introduce a new family of generic SSA instructions. For now, let's say it's just CondSelect64, CondSelect32, CondSelect16, and CondSelect8, all with the form (CondSelectXX a b bool) and the semantics bool ? a : b. (It doesn't appear FPU conditional moves are widely supported, so let's forget about that for now.)
Then, we add an additional pass to the SSA backend to recognize CFGs with the following form:
bb0
 | \
 |  bb1
 | /
bb2

where bb1 is "trivial" (for some definition of trivial). We can combine all three basic blocks into a single basic block where bb2's Phi instructions are replaced with the appropriate conditional moves.
I wrote the pass to detect this particular CFG arrangement and limited it to the case in which bb1 has two or fewer instructions and all of those instructions have no side-effects. When building the toolchain and stdlib, I recorded 3755 such cases.
On the architectures with which I am familiar (arm64, amd64, arm), the rewrite rules for the CondSelect instruction are trivial. However, I don't think I can implement the backend rewrite rules on all architectures (I don't have access to the hardware), so the pass that introduces those instructions will have to be gated to just those architectures for which the lowering rules are implemented.
CC @josharian @randall77

It will be a bit tricky to represent in SSA.  You will need additional args to any conditionally executed Value.  You'll certainly need a flags value to direct the conditionality.  And possibly also the old values of all the registers that get conditionally overwritten.  So it isn't as simple as adding a few bits to a Value and reusing already existing opcodes.
Another option is to do it in SSA->Prog.  We could detect & rewrite there more cleanly.  It would mean duplicating the logic for each arch, though.

I'm okay with doing it in SSA->Prog. I had some hope that maybe the logic for detecting these opportunities could be made portable, but I guess we'll see how realistic that is once I start writing the code. Perhaps it can work cleanly as a phase that runs after register allocation.

Alternatively, we do what LLVM does and introduce a "select" instruction in the portable SSA (we'd have to name it something different, I guess, since we already have one), and then lower that to the right conditional moves later.

Do we have a good way to find unpredictable branches?
For well predicated (especially not-taken) branches using predicated mov may be a pessimization.

I updated the issue description and issue title to reflect the work I've been doing on this. I have a better idea about how this will work now.
Re: performance, replacing a test-and-branch with a test-and-cmov on is still two instructions on amd64. Why would that be slower, even when the branch is never taken? I'd expect both to be retired in one cycle in the ordinary case. Let's see what the benchmarks say.

Different instructions take different amounts of time.  On some old Intel processors, the conditional move instruction is very slow.  That is just an example--conditional moves are fast enough on modern processors.  But I think the real win is when you can use them for unpredictable conditionals, to avoid branch mispredictions.  Even today I don't think they are a win if the conditional branch is very predictable.

Different instructions take different amounts of time.

I agree!

On some old Intel processors, the conditional move instruction is very slow. That is just an example--conditional moves are fast enough on modern processors.

Yes; I seem to remember a Torvalds rant about that re: Pentium III and IV. I assume that it's fixed by now. On an ARM64 chip, a CSEL costs exactly the same amount as a regular MOV, and the same amount as a perfectly-predicted branch. The same is true for ARM (unexecuted predicated instructions burn one cycle.) I think the old x86 hardware is the exception rather than the rule. We can always not do this optimization for x86 if it turns out this is still the case.

But I think the real win is when you can use them for unpredictable conditionals, to avoid branch mispredictions. Even today I don't think they are a win if the conditional branch is very predictable.

This I'm not entirely sure about that, for a couple of reasons:

If the (un-taken) basic block (bb1, in the diagram up top) is laid out between bb0 and bb2, then not only is the jump taken (forwards!), but the effective code density is lower. If the compiler happens to lay things out such that bb1 is a forward branch and bb0 falls through to bb2, then you emit an extra unconditional jump at the bottom of bb1 to get back to bb2. Emitting a conditional move has the same effective code density as the best case.

This is purely anecdotal, but the real-world Go programs that I've had to tune have had profiles that were flat and slow (i.e., 60%+ of the execution time was spent outside the top 5 function calls.) I think that's a natural state for many (bloated) programs after they've had obvious hot spots optimized. Those programs aren't going to get much help from dynamic branch prediction in the first place; branch caches aren't that big. But, code size reductions do help the program counter trudge through all that bloat a bit quicker.

Let's see what the benchmarks say once I've run them.

branch caches aren't that big

Also, the discussion in #18977 around branch cache collisions (search for "hash(IP")) makes me suspect that there is non-local, stochastic value in removing branches outside of hot code.
It's sometimes also instructive to see what gcc/llvm does with similar C code. Also, some conditional calculations can be translated into branchless code with arithmetic tricks; not sure whether those are common enough to worth encoding into rules. cc @martisch on the last front.

I think if we try this we should start only with simple cases like:
if cond {
		B = 15
}

and
if cond {
                B = 15
} else {
                B = 1
}

since these do not have data dependencies.
Bool to int conversions of the form if cond { b = 1 } else { b = 0 } should be left to SETcc on amd64.
I am less worried that cmov itself is slow on modern amd64 but instead would be careful instead if the assignment to B is something that is not immediately available and introduces a stall waiting for that data which would have been avoided in a correctly predicated branch.
We could also survey what LLVM and gcc have opted to optimize with cmov to collect more information about trade offs.

Re: performance, replacing a test-and-branch with a test-and-cmov on is still two instructions on amd64.

Many test-branch pairs are macro-op fused to one internal op on modern amd64.
 When looking at https://github.com/golang/go/issues/16141 case, maxsd (which is the best case for conditional move) was ~2x slower than branch, because it introduced data dependency.
@philhofer  does your change work on code like this:
if bit == 0xffff {
     nodeIndex = node.left
} else {
     nodeIndex = node.right
}

Were left/right/nodeindex are uint16?

Not yet. Right now only 'if' blocks are collapsed, but it should be simple
to recognize and collapse if+else, too.
On Mon, Aug 14, 2017 at 9:21 AM, Ilya Tocar<EMAIL_ADDRESS>wrote:

I was mainly worried about things like search for max in array. When
looking at #16141 https://github.com/golang/go/issues/16141 case, maxsd
(which is the best case for conditional move) was ~2x slower than branch,
because it introduced data dependency.
@philhofer https://github.com/philhofer does your change work on code
like this:
if bit == 0xffff {
nodeIndex = node.left
} else {
nodeIndex = node.right
}
Were left/right/nodeindex are uint16?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/21391#issuecomment-322236520, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACzf5jz2VFEh0TE9ZfIkLsmyeMcDRCycks5sYHQAgaJpZM4OztOA
.

Above patch merged: 2d0172c3.

This has been implemented and merged, the CL was missing the issue reference to close it.


Figure out why or if precacheImage works on Flutter for Web

See the discussion in https://github.com/flutter/flutter/pull/51656#issuecomment-610555698

Not sure if it makes sense for the HTML case, but it makes sense for CanvasKit

@hterkelsen feel free to adjust the milestone as you see fit. I optimistically chose near-term just to get it out of the triage queue.

Does this still a valid issue?

This should work already. Feel free to reopen or file a new issue if it doesn't.


Add k8s versions 1.13.10, 1.14.6, 1.15.3

What kind of request is this (question/bug/enhancement/feature request):
Add k8s 1.13.10, 1.14.6, 1.15.3

Tested with master - 797db23c2
During cluster creation , we are are not presented with 1.13.10. We still see 1.13.9 version.

Able to create cluster with K8s version 1.14.6 and  1.15.3 successfully.
Reopening to make K8s 1.13.10 available.

Bug on rancher metadata feature, the PR is fine.

Tested with latest master build - c3eece0ca
Able to create cluster with K8s version 1.13.10 is presented in UI as expected .
Able to get a cluster up and running with this version successfully.


[release-1.22] Update packaged containerd and etcd

containerd 1.5.9 - fix (previously patched in our fork) for CVE: GHSA-mvff-h3cj-wj9c
etcd 3.5.1 - fix for https://github.com/etcd-io/etcd/issues/13196

Validated containerd and etcd version on k3s version v1.22.6-rc1+k3s1
$ kubectl get nodes -o wide
NAME              STATUS   ROLES                       AGE   VERSION            INTERNAL-IP    EXTERNAL-IP   OS-IMAGE           KERNEL-VERSION   CONTAINER-RUNTIME
ip-172-31-4-186   Ready    control-plane,etcd,master   34s   v1.22.6-rc1+k3s1   <IP_ADDRESS>   <none>        Ubuntu 20.04 LTS   5.4.0-1009-aws   containerd://1.5.9-k3s1

go.etcd.io/etcd/server/v3 => github.com/k3s-io/etcd/server/v3 v3.5.1-k3s1


Selective Traffic Routing with tun2proxy

Hey @blechschmidt  :)
I’m curious if tun2proxy can be used similarly to Proxifier. Specifically, I’m looking to route traffic for a specific list of domains through a SOCKS proxy. The domains I want to route through the tun interface can only be resolved internally through a private DNS server that isn’t exposed to the internet, so basic iptables rules won’t work. My goal is to ensure these domains are resolved via the SOCKS proxy and that only their associated traffic is routed through the tun interface. All other traffic should flow normally without passing through the tun interface.
Would this be feasible with tun2proxy as it currently stands, or would it require additional functionality? Any guidance or suggestions you can provide would be greatly appreciated.
Thank you for your hard work on this project. It’s made a significant difference in my networking toolkit.
Best regards,
Dvir

Hi @dvir101,
currently, that would not be feasible. However, implementing that feature would be relatively straightforward regarding the logic.
DNS handling logic is implemented here: https://github.com/tun2proxy/tun2proxy/blob/3f76ccec97340392acc595057e10ac0895f3b834/src/lib.rs#L276-L311
So you can see that we already support DNS over TCP and virtual DNS. For DNS over TCP, UDP packets are intercepted and forwarded to the desired DNS resolver, i.e. the response returns the real IP address of the destination domain. For virtual DNS, whenever we see a query for a DNS name, an IP address from <IP_ADDRESS>/15 (currently hardcoded) is returned and we remember that in an IP to name mapping. Whenever we see connection to one of the remembered IP addresses, we ask the proxy to connect to the name instead of the destination IP.
Given this explanation, the logic for implementing that feature is relatively straightforward.

Build a data structure to determine whether a target name should be resolved through the proxy (e.g. a domain trie or a hash set).
If that is the case, behave like virtual DNS, i.e. return an address from <IP_ADDRESS>/15.
Otherwise, forward the DNS query to the system's DNS resolver, which needs to be read from the corresponding configuration location (e.g. /etc/resolv.conf on Linux).

What is important here would be to only set up a route to the tunnel interface for <IP_ADDRESS>/15 instead of <IP_ADDRESS>/0 as it is done in the setup mode. Then, connections resolved through virtual DNS would go through the proxy.
Kind regards,
Birk

Hi @dvir101,
thank you for your kind words. Unfortunately, this is not possible with the current feature set. To resolve DNS names through the proxy, tun2proxy's built-in DNS resolver has to be used. This is what virtual DNS does. Whenever it sees a DNS query, it replies with an IP address from <IP_ADDRESS>/15 (currently hardcoded) and remembers an IP address to name mapping for the queried DNS name. Whenever we see a connection to that IP address, we then ask the proxy to connect to the DNS name instead of the IP address.
However, we currently lack the functionality to forward DNS queries to the configured system resolver (which could be obtained by reading the corresponding system configuration, e.g. /etc/resolv.conf on Linux) and we lack the functionality to tell the DNS proxy to differentiate between specific domains.
Logically, implementing that functionality would be quite straightforward:

Implement some data structure (e.g. a domain trie or hash set) that is filled with the domains that should be resolved through the proxy.
If a domain should be resolved through the proxy, just use virtual DNS.
Otherwise, forward the query to the system's DNS resolver.

What would be crucial here is to not make use of --setup which would automatically set up a route for <IP_ADDRESS>/0 through the tunnel interface. Instead, only <IP_ADDRESS>/15 should be configured to be routed through the tunnel interface. Then, virtual DNS would return IP address from that space and connections would always go through the tunnel. Other connections not destined to an IP from that space would not be routed through the tunnel.
Kind regads,
Birk

Perhaps this script can help. https://github.com/tun2proxy/tun2proxy/blob/master/scripts/iperf3.sh


MSYS2 logo

OS
paste content of /etc/os-release here. If this file doesn't exist, describe a way to identify the distro.

ascii-art.zip P.S converted icon to ASCII
Ascii
paste ascii art here. If you leave this empty, i will try to find the logo myself.

os-release.zip

Implemented. I've created a logo by myself, because yours was a bit big, and set the background instead of the text. Feel free to criticize it.


DBeaver crashes when connecting to a PC via RDP (window resize bug?)

Greetings,
I upgraded from dbeaver-ee-5.3.3-x86_64-setup to dbeaver-ee-6.0.0-x86_64-setup and have since
upgraded to dbeaver-ee-6.1.0-x86_64-setup.
Starting with version 6.0.0 I started having issues when I RDP into my desktop from my laptop. Upon connecting dbeaver will occasionally crash. I am suspicious that this issue is related to resizing the DBeaver window from a very large resolution to a much smaller resolution. I suspect the intermittent nature may be related to if DBeaver is in full screen mode or not.
I generally like to get more information for bug reports, but I'm not really sure where to go from here. The crash info is not terribly useful, but here it is:
Faulting application name: dbeaver.exe, version: <IP_ADDRESS>, time stamp: 0x5b995959
Faulting module name: MSCTF.dll, version: 10.0.17763.348, time stamp: 0x6fda36d1
Exception code: 0xc0000005
Fault offset: 0x000000000004a06e
Faulting process id: 0x2230
Faulting application start time: 0x01d546693449ef06
Faulting application path: C:\Program Files\DBeaverEE\dbeaver.exe
Faulting module path: C:\WINDOWS\System32\MSCTF.dll
Report Id: b2cc5c89-00cf-4b05-a4a5-d6934b7e5344
Faulting package full name:
Faulting package-relative application ID:
Looking at the DBeaver logs, I don't see much.
!SESSION 2019-08-01 10:04:05.831 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_77
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en
Command-line arguments:  -os win32 -ws win32 -arch x86_64
!ENTRY org.eclipse.core.resources 2 10035 2019-08-01 10:04:44.288
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
I'm happy to spend some time getting more actionable information. Any idea what that might be?
I'm running Windows 10 1809. Not using any extensions. Using the pre-packaged version of Java.
Thanks

Please try recent DBeaver version. It is bundled with Java 11, perhaps this problem was solved there.

dbeaver-ee-6.1.0-x86_64-setup was the most recent version as of this posting. Is There a newer version somewhere else?
Thanks

There is Early Access version (https://dbeaver.com/files/ea/)
You could try it and if it will solve the problem with RDP then you can install Java 11 manually and keep using 6.1 version till 6.2 release (planned on early September)

Just installed 6.2 and still have the same problem. What can I provide that would help get to the bottom of this?
Thank you

Any update on this issue?  This is nearly 6 months old now.  Fabian mentioned this workaround that might work, but I don't think it will with me
https://stackoverflow.com/questions/1411829#59526421?

Same problem here.  Using Windows 10 (1903) and dbeaver version <IP_ADDRESS>910211155.
any updates on this issue?

I, too, am having the same issue.  I'm currently on 7.0 EE, but it has been happening for with several previous versions too.  Windows Event Viewer shows it going back until at least January, but I'm pretty sure it was happening before then too based on the age of this ticket.
For me, I've noticed that it doesn't happen every time I RDP.  I suspect it is happening the first time my system detects a monitor change and/or a resolution change.  For example, if I'm home working on my dual-monitor setup, and then later RDP in remotely (with a single monitor), the first time I RDP, DBeaver crashes.  But if I disconnect from RDP and connect again a second time, DBeaver is fine because I don't think Windows resets the screens/resolution until I'm back home again.
Interestingly enough, when I do return home and the screens/resolution are restored back to the original setup, DBeaver does not crash.  So I think it's something specific to the way RDP is handling the screen/resolution changes.
I'm not able to find any DBeaver or JVM logs for the crash.  I just see the entry in Windows Event Viewer.
I am on Windows 10 Pro, Build 1909.
Faulting application name: dbeaver.exe, version: <IP_ADDRESS>, time stamp: 0x5d2c4a8f
Faulting module name: MSCTF.dll, version: 10.0.18362.535, time stamp: 0x6581a05f
Exception code: 0xc0000005
Fault offset: 0x000000000005af34
Faulting process id: 0x5a2c
Faulting application start time: 0x01d5f0c6ac5ad9ab
Faulting application path: C:\Program Files\DBeaverEE\dbeaver.exe
Faulting module path: C:\WINDOWS\System32\MSCTF.dll
Report Id: 2bf80588-1050-41c1-88fc-0fa4c97bd3c2
Faulting package full name:
Faulting package-relative application ID:

The same happens to me to (with several latest versions including 7.0.0).
PC: 2x 19201200 + 1x 10801920 (FHD vertical)
RDC resolutions: FHD, 1440p

This is still happening to me, in fact it just occurred a moment ago.
Unhandled exception at 0x00007FF9A94E2503 (ntdll.dll) in dbeaver.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF. occurred
The stack
ntdll.dll!RtlFreeHeap()
rpcrt4.dll!00007ff9a693c2ef()
rpcrt4.dll!00007ff9a693c584()
rpcrt4.dll!00007ff9a691482b()
msctf.dll!00007ff9a82db470()
msctf.dll!00007ff9a82b74f0()
msctf.dll!00007ff9a828e31d()
msctf.dll!00007ff9a828bf39()
msctf.dll!00007ff9a82b8d2e()
msctf.dll!00007ff9a828ae0e()
msctf.dll!00007ff9a828acbb()
msctf.dll!00007ff9a83391b9()
msctf.dll!00007ff9a82b7d35()
msctf.dll!00007ff9a82b7954()
TextInputFramework.dll!00007ff995fc1ed6()
TextInputFramework.dll!00007ff995fc1657()
TextInputFramework.dll!00007ff995fd84ec()
TextInputFramework.dll!00007ff995fe46fa()
TextInputFramework.dll!00007ff995fceb81()
TextInputFramework.dll!00007ff995fcea65()
TextInputFramework.dll!00007ff995fcea14()
CoreMessaging.dll!00007ff9a32d72bc()
CoreMessaging.dll!00007ff9a32f863d()
CoreMessaging.dll!00007ff9a32dc150()
CoreMessaging.dll!00007ff9a32db270()
CoreMessaging.dll!00007ff9a32da175()
CoreMessaging.dll!00007ff9a32d9fac()
user32.dll!00007ff9a9037446()
user32.dll!00007ff9a9036f62()
swt-win32-4930r6.dll!00007ff9628dc714()
000000000cf12cae()
0000000000000007()
00000000008fde70()
0000000000000001()
0000000083b03010()
0000000083b03010()
00000000033ec000()
0000000080cf48e0()
jvm.dll!00007ff9462957b9()
000000000d50ff18()
0000000080d381d0()
0000000080743ba0()
00000000033ec000()
000000000cfb3616()
0000000100002070()
0000000080cf48e0()
0000000000000007()
00000000033ec000()
000000008072c9c0()
0000000083a58628()
0000000080d32270()
0000000080d37f18()
0000000080d37f18()
0000000080cf48e0()
0000000000000003()
0000000080cf48e0()

Well, look at this...
[win32] JVM crash after connecting Windows Remote Desktop
https://bugs.eclipse.org/bugs/show_bug.cgi?id=543747

There is temporary workaround with minimizing after logout: https://github.com/dbeaver/dbeaver/issues/5872#issuecomment-599225575

duplicates #5872


General fixes to install script

installing empire as non-root user will fail where sudo is not used.

supersedes #1211

@bisack thanks for the comment, i will fix it later.

@bisack fixed. can you please check and change your review status? thanks.

@phra -- While the current version is indeed deb8u9 - that url is incorrect and results in a 404 error. I found 8u8 DOES work, and resolves some of the issues I ran into.
In order to unblock my own workflow, I created a fork so I could re-enable my environment auto-builds. That change and two others (to fix the powershell installation failure and the urllib3 version issue) make up my pull request.
See #1268 for the changes I made.

@bisack i am going to close this PR in favor of #1268. thanks for your contribution.


Add 'extends' syntax for settings file

From Slack, the idea is that we would be able to do something like:
{
   "common":{
      "s3_bucket":"lmbda",
      "app_function":"tests.test_app.hello_world",
      "callbacks":{
         "settings":"test_settings.callback",
         "post":"test_settings.callback",
         "zip":"test_settings.callback"
      },
      "delete_local_zip":true,
      "debug":true,
      "parameter_depth":2,
      "prebuild_script":"test_settings.prebuild_me"
   },
   "ttt888":{
      "extends":"common",
      "touch":false,
      "events":[
         {
            "function":"tests.test_app.schedule_me",
            "expression":"rate(1 minute)"
         },
         {
            "function":"test.test_app.method",
            "event_source":{
               "arn":"arn:aws:sns:::1",
               "events":[
                  "sns:Publish"
               ]
            }
         }
      ]
   },
   "devor":{
      "extends":"common",
      "events":[
         {
            "function":"tests.test_app.schedule_me",
            "expression":"rate(1 minute)"
         }
      ]
   }
}

To avoid duplication of settings.
The problem here is circular imports, but that might be so obscure to not be a huge issue.

Properly taken care of now, thanks all.


Fix typos and json sample code in documentation

This PR fixes:

some typos (also removes some unneeded whitespace characters)
consistency issues with quotes in json samples (now everything uses double quotes)
one minor issue where serviceName was incorrectly capitalized in the json sample

Coverage remained the same at 95.253% when pulling f65a794aae4954f3243b52a731076217f1ccbafb on quantus:master into d71bc5428f3b7962d8fdc91d76093bb1cfa981cd on onelogin:master.


Reanimated 3.15 Warning

Having lots of warnings in console starting from reanimated 3.15.
Here is the warning:
[Reanimated] Reading from valueduring component render. Please ensure that you do not access thevalueproperty or useget` method of a shared value while React is rendering a component.
If you don't want to see this message, you can disable the strict mode. Refer to:
https://docs.swmansion.com/react-native-reanimated/docs/debugging/logger-configuration for more details.`

Here is my patch which fixes warnings
react-native-collapsible-tab-view-npm-8.0.0-d940cdc0a3.patch

@pavelbabenko when applying this fix I had TypeError: Cannot read property '__internalInstanceHandle' of undefined, I'm using version 0.76 of RN and 3.16.3 of reanimated


Removed the gambling link.

Since the repo is public I think it would be better to not have a link to a gambling website. Just in case.

Huh, I guess I put that in there by mistake. Thanks for deleting it.


Feat: improve CI

Here's a small but mighty change to the CI piepline!  We're further parallelizing, tidying and adding codecov!
Closes #5

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


SpringCloud gateway integration SkyWalking.Link monitoring collection request address problem.

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ✅  ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question
I hope that after skywalking collects the gateway endpoint, the UI will display the specific request address. However, it seems that the current display will always be 'spring cloudgateway / routingfilter'. Is this my configuration problem? Or design?

At present, the apm-spring-cloud-gateway-2.1.x-plugin-8.1.0-SNAPSHOT.jar under the optional plugins package is moved to the plugins package.

8.1.0-SNAPSHOT plugin has been changed. How it works base on its contributor :)


Add: Two decimals lb acc UwU

lgtm!! but what the git code detetion in {% endblock %} lmao
Thanks for contributing!


Hitting ESC twice clears all placeholders

If a user enters a textfield and then hits ESC twice, all placeholder text will be cleared.

Seems like it also occurs in IE7 as mentioned in https://github.com/mathiasbynens/jquery-placeholder/issues/251


Use of @MainActor throwing warnings when initializing outside of Swift concurrency

Hi, RE: #24, in cases where an app is not entirely using async await, these warnings are appearing when (for example) this is already being initialized statically from the main queue.
There should probably be a way to initialize this outside of the singleton without requiring this configuration.

@JPToroDev do you know if this is still an issue (or perhaps more of an issue) with your recent changes?

I suspect this issue has more to do with the concurrency coexistence approach than with SyncMonitor’s @MainActor status, but I'd need to do some tests to be sure. @benguild If you're still encountering this issue, could you share a small example?

Hmm, seems resolved with the changes— I'll close for now and respond back later if anything comes up. Thanks for your reply back.


Upgrade packages from latest bundle doesn't activate bundle

What happened:
 $eksctl anywhere upgrade packages --bundle-version "" --cluster ivyjin-worker-1-1017
packagebundlecontroller.packages.eks.amazonaws.com/ivyjin-worker-1-1017 configured

 $eksctl anywhere get pbc
NAME                   ACTIVEBUNDLE   STATE               DETAIL
ivyjin-mgmt-1-1017     v1-21-83       active
ivyjin-worker-1-1017                  upgrade available   v1-21-568 available

What you expected to happen: The latest bundle gets activated
How to reproduce it (as minimally and precisely as possible): See above
Anything else we need to know?:
Environment:

EKS Anywhere Release: release-0.12 commit 00e4995ea86f37b072a823b665c6d58d75dccd7d
EKS Distro Release:

Looks like you didn't provide the --bundle-version flag and provided it as empty. Currently that needs to have a value. I guess we can add a validation to it or we can pull the latest bundle if no --bundle-version is provided.

it would be nice if a blank version caused the reconciler to get the latest.

We should leave this until after the dust settles on CLI v0.12 This is basically user error, but I'd like to see it work anyway and kind of a big impact


Fix dangling semicolon

I've been made aware of it twice now. I'm not sure if I want this semicolon to become my modding legacy.

Sorry it was just too funny


Fix 404 for revalidating signature email

The previous retrieve_petition method that was called before the signed controller method was scoped to only OPEN and REJECTED petitions, so would not find any other petition.

QA'd - good to merge when reviewed

Thanks for the comments and help, have recommitted this with a different approach, by just rendering the signed view from the verify controller method

Seems fine to me, but it might be worth floating this new approach past @yahoopete - I know there were some concerns about not being able to track user journeys properly in GA unless the urls actually changed.

Rebased. Still need to check with @yahoopete about new routing approach

@davidbasalla, do you need any help with this PR?

Hey, I pushed this up last night. Please have a look and see what you think. Has the revised routing approach where the verify action redirects to an URL such as /petitions/1/signatures/#{signature.perishable_token}/signed. This is to ensure that noone can enter guessable signature id's and see infos about the signature's constituency

@yahoopete, are you ok with this new approach? Seems fine. Murray had a question re: GA above

If this provides the following URL structure (which it looks to) "https://petition.parliament.uk/petitions/#{signature.petition_id}/signatures/#{signature.perishable_token}/signed" then we are gold....
We can do a thing in GA, which aggregates and anonymises bits of the path (not that it needs anonymising, but it does need aggregating, so we'd see something like
/petitions/100123//signed
This will then let me keep tracking journeys etc in GA.
So :+1:


Add a pacemaker validation

This validation runs pcs status and fails if any of the actions
failed.
This is useful as a post-deployment validation as well as something we
ought to check before upgrading the deployment.
The output of pcs status is parsed only partially -- we gather all the
top-level sections, but do not process the underlying data further. This
is something that could be useful to add in the future but not necessary
for this validation.

Switched to pacemaker status xml. The code is teeny tiny bit simpler :-). Thanks for the suggestion, @mandre!

@mandre addressed your comments.

Awesome! thanks.


[Feature Request] Regex ignore tokens + ignore tokens in strings/comments/etc.

Hi! Really liking this extension :) Full token highlight is very useful to me, I just had two things bothering me:

Token ignoring is a static list, so ex. I cannot filter out all numbers from token highlighting. It would be very useful to be able to add something like "\\d+": null to backgroundPhiColors.tokenColorMap to fix this. I do understand that it might be a performance thing, so no worries if it's not possible ^^
Token highlight also happens inside of comments, strings, etc. This is extra visual noise and I'd like to be able to turn it off if possible.

If I have time later this week, I can try putting together a PR; no promises though. Thank you for the extension!

I think this is a good idea. However, I don't start on this task right away because I have other priorities.

:+1: Thank you! I look forward to it :heart:

Hi! It's been about 6 months, so I just wanted to check if there's any updates on this ^^


select which libffi (6|7) to install for s390 support.

Additional entry required: libatomic1 [armhf]
Then there's a more complex one: OpenJDK's s390x port requires libffi6 because Zero needs libffi. Ubuntu 18.04 and Debian Buster are the last ones that ship libffi6. The upcoming Debian Bullseye, Ubuntu 20.04 and newer only include libffi7. So adding libffi6 [s390x] would be required for Ubuntu 18.04 and Debian Buster and earlier but that makes the package not installable on more recent Debian/Ubuntu versions. The only way out of this mess would be to split the packages and see if OpenJDK 8 can work with libffi7. But considering that s390x only supports Zero, I'd just drop support for s390x.
For future reference, how to compile this list: Download the JDK of each platform, run a script like https://github.com/adoptium/installer/blob/master/linux/required_libs.sh (works on any architecture, so you can even do this on a Mac) and resolve the name of the libraries with the function "Search the contents of packages" on https://packages.debian.org and https://packages.ubuntu.com.
Originally posted by @aahlenst in https://github.com/adoptium/installer/pull/332#discussion_r684623237

Closing - we don't ship a zero build of s390x and libatomic1 has been addressed via https://github.com/adoptium/installer/pull/414


Update ansible to reflect new zopen

Changed region from tokyo to toronto (doesn't experience the curl timeout issues we saw with Tokyo based instances)
Updates to the latest wazi images
Adds fixes for using python 11 which is now available on the wazi images (adds /lib to LIBPATH for libzz64)
Modifies the code to extra meta pax and install zopen, including git and bash (implicit from git)
Copies a working private key so that git clone on the ssh protocol work on the system

/run tests

/run tests

/run tests

/run tests


Feat: Client Reports

:scroll: Description

Feature branch collecting all sub-branches for the client reports implementation.
:bulb: Motivation and Context

[x] Feat: Record & Send Client Reports #813
[x] Feat: Client Report Envelope Item #810
[x] Feat: Client Report Recorder #809
[x] Client Reports: Record Network Errors #830
[x] Client Reports: Bump iOS SDK & Pass Options #836
[x] Client Reports: Bump and Pass Options (Android) #846

Closes #812
:green_heart: How did you test it?
Unit tests.
:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[ ] I updated the docs if needed
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

[x] Set sendClientReports on native Android options when Java Client Reports are merged
[ ] Test End-To-End on iOS, Android and Web

Closes #735

Codecov Report

Merging #829 (2518bca) into main (8fd364e) will increase coverage by 5.71%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #829      +/-   ##
==========================================
+ Coverage   89.84%   95.55%   +5.71%
==========================================
  Files         114        2     -112
  Lines        3672       45    -3627
==========================================
- Hits         3299       43    -3256
+ Misses        373        2     -371

Impacted Files
Coverage Δ

dart/lib/src/hub.dart

dart/lib/src/sentry_client.dart

dart/lib/src/sentry_envelope.dart

dart/lib/src/sentry_envelope_item.dart

dart/lib/src/sentry_options.dart

dart/lib/src/transport/rate_limit.dart

dart/lib/src/transport/rate_limit_parser.dart

dart/lib/src/transport/rate_limiter.dart

dart/lib/src/noop_hub.dart

dart/lib/src/sentry_stack_trace_factory.dart

... and 101 more

Continue to review full report at Codecov.

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

It needs testing with the iOS and Android bridges, but codewise looks good.

@marandaneto Client reports are being send with the HttpTransport and we get a 200 response from the backend.


wire: improve color output to term by using fatih/color

Fixes #183.
This addresses a TODO, and also ensures that the coloring works on Windows, and is disabled when appropriate (e.g., TERM=dumb, wire show | less).

FWIW personally I'd rather remove color support than incur a significant external dependency like this.
I'd like to be able to use wire code in low level packages with strict dependency requirements, but pulling in github.com/fatih/color also pulls in github.com/mattn/go-colorable, github.com/mattn/go-isatty and golang.org/x/sys.
Are the colors really worth it? Perhaps we can make the layout clearer without using color?

I filed https://github.com/google/wire/issues/189 to discuss dropping colors.


kafka(ticdc): topic manager return the partition number specified in the sink-uri

What problem does this PR solve?

Issue Number: close #9952
What is changed and how it works?

adjust the partition number to user specified value in the kafka topic manager.

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
fix the partition number specified in the sink-uri is not correctly used

/test cdc-integration-mysql-test

/test verify

/test verify


Add extensions publish command

Public-Facing Changes
Adds support for extension publishing.
foxglove extensions publish ./me.package.foxe

Description
Opening as draft; the public API endpoint for this does not yet exist.
We may want to add extension listing at the same time; it feels a little weird not to be able to list your uploads. Edit: see #64.
Resolves #59.

👍


Expand api tests

Description
The PR expands the tests of the orchest-api service. Some bugs that have been found during the implementation are also fixed.
The orchest-api tests will now be run against a real database. Setup of the test database is done by invoking docker, which is a requirement for running those tests.
Checklist

[x] The documentation reflects the changes.
[x] I have manually tested the application to make sure the changes don’t cause any downstream issues.
[x] In case I changed one of the services’ models.py I have performed the appropriate database migrations.

Quite the test cases. What stood out to me it the amount of state that needs to be pre-configured before a particular functionality can be tested.
@fruttasecca How extensible do you think the current test suite is? Extensible when it comes to adding more tests and not having to change tests when changes (in particular additions) are made to the orchest-api.

Quite the test cases. What stood out to me it the amount of state that needs to be pre-configured before a particular functionality can be tested.

Indeed some state needs to be there, e.g. the project or a pipeline, but I think fixtures are covering that properly.

@fruttasecca How extensible do you think the current test suite is? Extensible when it comes to adding more tests and not having to change tests when changes (in particular additions) are made to the orchest-api.

The project, pipeline and other "setup" fixtures help with encapsulation to a nice extent. The fact that we make use of the concept of "two phase" functions should also help in that regard. Of course, a change in the semantics of an end point will probably lead to a change in the tests, that's not really avoidable I suppose. Adding features in the orchest-api should bring fewer issues than changing already existing functionality imo, but only time will tell.


VS Code project settings are tied to rlewis.

VS Code is somehow translating generic tags for project etc to my username.

Looks like the c_cpp_properties.json file is auto-generated from PlatformIO.ini so I've removed it and the launch.json from GitHub.  Also updated the .ini file to force the include path.  Source path hasn't been an issue.

Verified on Windows machine (different username) that the properties file is correct. Closing as fixed.


Design pattern to use to loop over a series of pages?

This is not a bug but a request for advice. What design pattern do you suggest to use phantomjs-node to interpret multiple pages within the same session, e.g. in the classic case where the results of a search are split over several pages, and I would lose the "session" if I instantiated a new phantomjs for each page?
The promises-based syntax is confusing me, and I would welcome your suggestions.

It depends how scalable you want it to be. If this is a small project and you are just trying to get results then you have two options.

Create multiple phantom processes and then call async.parallel to wait for all. This obviously heavy and it might take a lot of memory depending how many pages you have. This has been tested so I know it works. Look in the example directory cluster.js
Create one instance of phantom and then open each page sequentially or in parallel. I haven't tested this, but given that it uses unique ids for different pages, it should work. Theoretically. :)

The above is the easy way of course.
The more scalable way which I would recommend if you plan to do this a lot is to have a simple queuing system. Something like this:

Have a consumer batching process which looks for items on a queue and process each one.
Wait a new session opens, put all these pages on to the queue
You can return immediately and then use AJAX to check the status of the jobs. You can show progress bar and whatever.
Is your load going to triple? Just create more batch process machines to consume the queue faster.

Hopefully this all makes sense. You also might want to try stackoverflow.

Thanks @amir20 .
Why do you say (1) would work? Wouldn't the different phantomjs instances be independent? I could not share the session created by the very first search.
(2) is what I was thinking of, too, but how do you make a loop of .then()_?
Load is not going to be massive in my case, but I would like to design the thing properly anyway.

I thought you meant the session of the user who is requesting. I am guessing you mean the session in phantomjs. You are right that the different process would be independent. You would have to use cookies like this example if you want to really share sessions. I am just not sure how to get the first page's cookies out.
For (2), you wouldn't loop and look for all promises. You can either block for all promises using Promise.all which I wouldn't recommend because it could take a while. Or return immediately and then in your front-end (or whatever UI) use AJAX requests to update status on progress.

Thanks a lot. I guess I am still too new to promises to understand your advice on (2), unfortunately. If you have no time to give me more hints, just close the issue and I'll study what is needed. Thanks!
My script is silent, so no need to care to the front-end, just need to go through ~40 results pages, collect the results and write them somewhere for post-processing.

Unfortunately, I don't have any sample code to share. The idea behind promises are that you can join them all and block. Here is a good example https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all.
I am going to close the issue but will try to respond if you respond. Good luck.


Add au wifi connect

Add a new Cask.
Please check this.

Thank you for the contribution. It needed some fixes, so they were made in 4efa41bb9f73c69e43706df584a184f3222146dd. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Allow passing custom configuration to parse_headers

There are several protocols that look almost identical to HTTP (in my case, it is SIP). Often the only difference is the request-line and/or the response-line. In SIP in particular, multiline headers are the norm (allow_obsolete_multiline_headers_in_responses).
Being able to parse the request/response-line by myself and then using parse_headers with a custom configuration would be very convenient.

Friendly ping! :)
If you're unable to review for the time being, that's totally fine of course. Only making sure this isn't forgotten.

@seanmonstar Apologies for pinging again. Do you mind having a look at this PR? This is a small, backward-compatible change. Having this merged would be really great, if possible.
If there's something that needs to be changed, such as documentation, tests, etc -- please let me know.


[Rendering] Iphone cuts text in adaptive cards on Microsoft Teams

Target Platforms
iOS
SDK Version
1.5
Application Name
Microsoft Teams
Problem Description
Over the last year we have quite frequently problems with the iOS rendering of adaptive cards on MS Teams. At the moment text is just cut instead of a proper wrap (multiple letters are missing, see screenshots). The screenshots were made on a iPhone 13, IOS 17.5.1.
Screenshots

Card JSON
{
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "type": "AdaptiveCard",
  "version": "1.5",
  "body": [
    {
      "type": "ColumnSet",
      "columns": [
        {
          "type": "Column",
          "width": "stretch",
          "items": [
            {
              "type": "TextBlock",
              "text": "Learning Package...",
              "wrap": true,
              "fontType": "Default",
              "size": "Small"
            }
          ]
        },
        {
          "type": "Column",
          "width": "auto",
          "items": [
            {
              "type": "TextBlock",
              "text": "2/5",
              "fontType": "Default",
              "size": "Small",
              "horizontalAlignment": "Right"
            }
          ]
        }
      ]
    },
    {
      "type": "TextBlock",
      "text": "QUESTION",
      "height": "stretch",
      "wrap": true
    },
    {
      "type": "Input.ChoiceSet",
      "id": "sendText",
      "style": "expanded",
      "choices": [
        {
          "title": "A)",
          "value": "ANSWER"
        },
        {
          "title": "B)",
          "value": "ANSWER"
        },
        {
          "title": "C)",
          "value": "ANSWER"
        }
      ],
      "isMultiSelect": true,
      "wrap": true
    },
    {
      "type": "Container",
      "items": [
        {
          "type": "ActionSet",
          "actions": [
            {
              "type": "Action.Submit",
              "title": "Send",
              "data": {
                "msteams": {
                  "type": "messageBack",
                  "displayText": "Send",
                  "value": {
                    "sendText": ""
                  }
                }
              },
              "msteams": {
                "feedback": {
                  "hide": true
                }
              }
            }
          ]
        }
      ]
    }
  ]
}

Sample Code Language
No response
Sample Code
No response

Adaptive Cards is now a semi private repo

Pull requests and issue creations will no longer be accepted and will be closed. Please send all issues with Adaptive Cards to Microsoft Teams docs repo (msteams-docs)
Issues will be reviewed and prioritized from there
Source code will still be available to the public.
Packages will still be posted to the public.

@ardlank should we reopen all the closed ones in the other repo?

Hi @ardlank, since nobody cares about the issues we report, it's probably a good idea to close that repository. The problem is, that the other repo is as useless as this one. There are so many bugs we are reporting and customers are complaining about, but nobody is taking care. Since you are taking some action right now, are you also improving the way your work in the other repository, or should we stop reporting stuff? At least some transparency would be fair... thank you.


feat: add heated steering wheel select

Adds Heated steering wheel select entity.
Disables old heat steering switch for new installs
created in Draft, as we need to wait for a new release of teslajsonpy
https://github.com/zabuldon/teslajsonpy/pull/408

alright, after a bit of GIT hell cause dumb me didn't pull from the upstream dev branch, we should be all good.
Ready for review


Celery Flower is not configured for Traefik

What happened?
Even though production.yml has Flower configured, traefik.toml doesn't contain anything related.
What should've happened instead?
Flower should be working with Docker.

You can access the Flower service on your domain on port 5555. If you need Flower on a subdomain with SSL you can update the trafeik.toml file accordingly and add another frontend and baackend.

It's possible this isn't configured properly depending on options chose when setting up - I also can't use flower on a prod site over HTTPS and theres nothing in the Traefik config that mentions it.


ROX-16865: Add traits to notifier.proto

Description
Add traits to notifier proto message so we could distinguish between declarative and imperative ones.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed

CI is sufficient

Current dependencies on/for this PR:

master

PR #5979   👈

This comment was auto-generated by Graphite.

/test gke-qa-e2e-tests
/test ocp-4-10-qa-e2e-tests

/test ocp-4-13-operator-e2e-tests

/test ocp-4-10-qa-e2e-tests

/test gke-postgres-nongroovy-e2e-tests
/test gke-nongroovy-e2e-tests


Fix various issues in ockam_ffi.

I had some computer issues this morning that I fixed by updating the OS, which meant that I wasn't on my primary dev machine for the day (I forgot to switch back after the update completed).
As a result of this, I decided to do my audit of the FFI code, which I had been meaning to do for a while (since at Mozilla, this kind of FFI code was my responsibility, so I know some non-obvious pitfalls to watch out for, and the solutions to them).
Fixes #1562, as well as the fact that we unwind from extern "C" fns, which is UB (fixing this robustly is a bit tricky, but not too bad — doing this correctly is a bit involved, but the implementation here should be robust.
I also cleaned up a use of #[cfg(feature = "bls")] when there's no bls feature, which is not that important, but caused a false positive error in my editor.

[x] All commits in this Pull Request are signed.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor Licence Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the ockam-network/contributors repository.

Merged as #2138 - thanks!


Update sbt-sonatype to 3.9.6

Updates org.xerial.sbt:sbt-sonatype from 3.8.1 to 3.9.6.
GitHub Release Notes - Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.xerial.sbt", artifactId = "sbt-sonatype" } ]

labels: sbt-plugin-update, semver-minor

Superseded by #231.


fix: correct base dataframe

Fixup for #256

Codecov Report

Merging #257 (e3b68dd) into master (6fcc2b4) will decrease coverage by 6.22%.
The diff coverage is 23.77%.

@@            Coverage Diff             @@
##           master     #257      +/-   ##
==========================================
- Coverage   70.78%   64.55%   -6.23%
==========================================
  Files          68       74       +6
  Lines        5945     5519     -426
==========================================
- Hits         4208     3563     -645
- Misses       1392     1612     +220
+ Partials      345      344       -1

Impacted Files
Coverage Δ

base/dataframe_go.go
0.00% <0.00%> (ø)

linear_models/linearsvc.go
70.06% <0.00%> (-2.29%)
:arrow_down:

trees/isolation.go
21.15% <21.15%> (ø)

trees/cart_classifier.go
24.37% <24.37%> (ø)

trees/cart_regressor.go
24.46% <24.46%> (ø)

trees/cart_utils.go
37.50% <37.50%> (ø)

trees/sorter.go
100.00% <100.00%> (ø)

filters/disc.go
29.16% <0.00%> (-5.32%)
:arrow_down:

base/util.go
55.17% <0.00%> (-4.29%)
:arrow_down:

base/filewrapper.go
62.50% <0.00%> (-4.17%)
:arrow_down:

... and 70 more

Continue to review full report at Codecov.

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


Change subscript CLI flag to -B

-D conflicts with definition lists
I considered adding a test so this doesn't keep happening, but getopts doesn't allow any kind of introspection on the flags, and a separate array might be a little overkill. https://github.com/rust-lang/getopts/pull/116 is the ideal solution but unclear if it's getting merged :(

Thanks!


[GHSA-7vx2-5349-qj99] ConcreteCMS vulnerable to Xpath injection attacks

Updates

Affected products
CVSS
Description
Severity

Comments
This CVE has been refuted by the founders/maintainers of Concrete CMS. It has been found invalid. MITRE and NIST concurred. Reporter created his/her own public advisory (this one) and then used it to obtain a CVE without informing the open source project Concrete CMS.

Hi @LisaCISO, the GitHub Security Advisory is now withdrawn and you have credit for alerting us to the CVE being rejected. Thank you for your contribution! https://github.com/advisories/GHSA-7vx2-5349-qj99


GTK 4.0 Support

Hi,
I tried using this theme with Fedora 36, running Gnome 42, but apps such as the Settings app, and Nautilus, do not adopt this theme, instead sticking to Adwaita. When will this theme get GTK 4.0 support?

Related to https://github.com/rtlewis88/rtl88-Themes/issues/59, will look into an alternative base theme i can modify with Tokyo Nights colour scheme

On hold until GTK4 becomes more mature


BUG || Submit Response not shown in View Case

Response Submitted by Accused Advocate is not shown in Complaint Tab in view case tab.

Hi @nitish-beehyv please look into this issue

Resolved in UAT


docs: create docstring for all methods

I uploaded the PR in case you want to make some clarifications/modifications during the process. I will update this PR until ready, then convert from draft PR to PR ready to review.
 I receive an empty list.

@jasondilworth56 do you have any idea of what lookup_get() does? I receive an empty list.

I'm not sure to be honest – looks like a simple implementation of what's in /data/docs/ just to tick it off. The docs for that endpoint are not particularly useful either.

I'm not sure to be honest – looks like a simple implementation of what's in /data/docs/ just to tick it off. The docs for that endpoint are not particularly useful either.

I'm going to leave it without doc then

This PR is ready to review. By creating the pull request, I've seen several things that probably I would create an issue to discuss later on, but I think this is a good start for documentation.
I have not english native language so please feel free to suggest any modifications.

Yea I think that's the way to go, let's go with just removing them from everything for now for consistency.

Done!


Rewrite the Pipelines tutorial for clarity and flow.

Improves the clarity and flow of the Tekton Pipelines tutorial.

/retest
On Tue, Feb 18, 2020 at 3:53 PM Serge Pomorski<EMAIL_ADDRESS>wrote:

@spomorski commented on this pull request.
In docs/tutorial.md
https://github.com/tektoncd/pipeline/pull/2068#discussion_r380928465:

-PipelineResources are used to define the artifacts that can be
-passed in and out of a Task. There are a few system defined resource types ready
-to use, and the following are two examples of the resources commonly needed.
+Use one or more PipelineResources to define the artifacts you'd like to pass in
In this particular case, the two sentences convey the same exact technical
information. The only difference is the passive vs. active voice: "X are
used to do Y" vs "use X to do Y". I think the double passive ("X are used
to define artifacts to be passed") voice is harder to parse, IMHO.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tektoncd/pipeline/pull/2068?email_source=notifications&email_token=AG3UR4X2CA65VIHV5M7E7RDRDRDFFA5CNFSM4KXKP7X2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCV7U2TQ#discussion_r380928465,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG3UR4VVVEC2AWQG265UD5TRDRDFFANCNFSM4KXKP7XQ
.

Oops, Mistakenly closed. We should merge this!

/approve
/lgtm
/meow space


Built in support for multi-res training?

Does it exist? If not should attempt to add.

you mean res bucket? kohyass did support that?


SimplifyCFG: fix crash in case an enum payload is an enum

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

fixes rdar://problem/26251856

@swift-ci test

@eeckstein looks like this won't merge cleanly.  GitHub says "this branch is out of sync with the base branch.

This is strange. I'll try to push again

@tkremenek It seems it can merge now


Optimistic UI

The Apollo-Client supports Optimistic UI. It would be nice when this plugin would support that too.
We have to think about what this means and how this support could look like.

I found myself wanting this today. Basically I want to insert a record, then do a API call, and on success update that record, or delete it on API error.  Would love VuexORM to make it more "Vue" like.
Perhaps something like this:
let optimistic = User.create({
  data: { id: 1, name: 'John Doe ' }
})

// Update API
this.$axios.doSomething()
.then((result)=>{
     optimistic.success(result) // updates record with any extra server data
})
.error(()=>{
     optimistic.fail() // deletes record
})

That pattern is basically what I do using create() then update() then delete() methods and tracking the record ID, so not sure if this is any better than that approach. Maybe just having a suggested approach in the docs would be enough?


ASB-750: Set First Accordion Section Open by Default

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

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


Server is not responding

Please check out the video....
https://www.loom.com/share/15db54a6b2c54903b0f57b608ef35fe6

is this happening only to us or someone else too?

I’ve been having this problem all morning. My error logs are saying there is a timeout waiting for cUrl to get TLS.

The problem is that the library is using https://www.howsmyssl.com/a/check to check your TLS version. It's currently down and not responding. I hacked around this by commenting out lines 148-152 in src/Core/HttpClients/CurlHttpClient.php

@onlinecheckwriter @lcnervick @fr8train-homebase What version of the SDK are you on? This was a problem before, we fixed the SDK to not use this a TLS checker. Here is the fix: https://github.com/intuit/QuickBooks-V3-PHP-SDK/commit/91050cbdc0e82e5f6df8bacc40bfe6e1b232a30e#diff-7c7999b6354f6c110c0dd868941595d1 this was as part of release 5.3.5.

@onlinecheckwriter I see that you are running into issues with connecting to the app, I will check with the App Connections team. Can you please share with us your app information?

@fr8train-homebase Thanks for the work around. I got new error after commenting out those 4 lines:
SyncRestHandler.php
Line 213
"throw new ServiceException("Request is not made successful. Response Code:[" . $faultHandler->getHttpStatusCode() . "] with body: [" . $faultHandler->getResponseBody() . "].", $faultHandler->getHttpStatusCode());"
Using the API to post data back to an invoice when I got this error

what do you want from us : @bsivalingam
We are also using old sdk, we didn't even change sdk

@onlinecheckwriter the issue you are experiencing for connection is different from the what others are referring to. Sorry I jumped the gun there. But if you can share more information from the network tab of the UI that is hung up, we will be able to triage it faster. We haven't had reports on connection error from other apps so we would need specifics for triaging. This could be a browser issue or something more specific to the app. If you can send us your app id and if possible the intuit_tid from the network tag for the app connection call that will help us.
For the TLS error please upgrade the version of SDK.

Let me update the sdk version and try it.

We moved this new SDK . I think it fix the issue


Precommit hook

/hold
issue: https://github.com/stolostron/backlog/issues/19778

/unhold

/cc @robinbobbitt

/cc @robinbobbitt @chrisahl

@leena-jawale @chrisahl we should probably rename CATALOG_IMAGE_VERSION to PREVIOUS_CATALOG_IMAGE_VERSION  in a future PR for clarity.


Fix init-env.sh error in non ocp clusters.

The NUM variable does not exist for non ocp clusters so it was showing
this error:
[2022-05-11T07:34:16.603Z] ++ '[' '' -ge 0 ']'
[2022-05-11T07:34:16.603Z] ./scripts/init-env.sh: line 83: [: : integer
expression expected

 Problem: conflicting requests
  - nothing provides libsubid.so.3()(64bit) needed by podman-2:4.0.2-6.module+el8.6.0+14877+f643d2d6.x86_64
The command '/bin/sh -c yum install -y wget make hostname iproute iputils openssh openssh-clients podman psmisc' returned a non-zero code: 1

????

Blocked waiting on: https://bugzilla.redhat.com/show_bug.cgi?id=2084179


High memory usage

We have a 100 GB collection. Sometimes even for a simple query(query by id filter), it uses lot of memory. Maximum memory I have seen was around 18GB.

How many documents do you retrieve? And how large are they?

sometimes it is just 1 document but mostly it will be lesser than 20 documents. max document size is 2KB

same problem here, max items 20, boom 6 GB memory usage after few minutes
When I check network bandwidth usage, download doesn't stop even after results are displayed and memory usage keeps raising.


Reinstate "AllocBoxToStack: Improve alloc_stack/dealloc_stack scoping"

And fix a wrong assert in StackNesting

@swift-ci Please smoke test and merge


fix(archive): redirect previous MEI versions to schema page

This PR contributes to #131 by redirecting the archive's "Previous versions of MEI" section to the schema and namespace subpage (previous versions are listed there now).

Thanks, @musicEnfanthen!

perfect, thanks!


feature: add Tor relay nostr-ts-relay

Hey @Cameri I have merged this. I didn't do it through github so manually closing this PR.
sorry if I did this in a confusing way (wanted to rename it). let me know if there is a better way to do this...

Its all good @monlovesmango thanks for merging ❤


Support for Training Negative Samples

Hi,
Is this repository allow considering negative images as well for training? For example, while training a cat detector, one may have some images containing cats (+ve images) and some images do not containing cats (-ve images). I noticed that the training script only considers the positive images for training and discard others.
What would be the good way to add support for Negative Samples in training in this repository?
Best Regards,
Maaz

Hi,
Negative examples mean you have no label on the image, so none of the categories are present (I am not sure if you just want to add specific categorie(s)).
Either way, you can do it by opening the script of your dataset class under dataset folder (for example coco2017_animal.py) and modifying the init function:
remove line 90: if len(annotation) > 0: if you want to add negative examples
At line 107 annotation.objects the code is monitoring for specific categories so you can add arbitrary classes there.
Hope this helps


Broken Project link in README

Describe the bug
In README.md, this link 404's for me:

Look at the Qatt Project

Expected behavior
Not sure what the link is supposed to be, in one of these?

https://github.com/sytone/obsidian-queryallthethings/projects
https://github.com/sytone?tab=projects

Both these look empty to me, but maybe the Project isn't set to public visibility:
Additional context
Your plugin looks cool :)

Fixed visibility, thanks for reporting it and thinking the plugin looks cool! :)


Issue/2 add code

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@10e0ca4). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main        #4   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         4
  Lines           ?       118
  Branches        ?        25
========================================
  Hits            ?       118
  Misses          ?         0
  Partials        ?         0

Flag
Coverage Δ

server
100.00% <0.00%> (?)

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


Force the "scrollToIndex" when using setValue

Hello, I have a doubt,... I am using the control in list mode, with the option "keepAlwaysOpen", but I have a problem that I don't know how to solve: when I set the value that I need to see selected, the list does not scroll to it.
Here is a visual example (as you can see, when I set the value 023, the list does not scroll to its position to make it visible)

Is there any way to force the "scrollToIndex" when using setValue?
The behavior I expect is the same as observed when the list is opened, in "Select" mode, and positioned:

Is there any way to force the "scrollToIndex" when using setValue?
Thx.

I have updated to the latest version, 1.0.39. I have seen two new options: alwaysShowSelectedOptionsLabel and focusSelectedOptionOnOpen; I have activated them but I see no difference in the behavior, using keepAlwaysOpen should these options solve my problem?
Thx.


Log LSP Specification issue with message $/setTrace. VSCODE sends $/setTraceNotification instead!

Logged as LSP issue number #1370

https://github.com/microsoft/vscode-languageserver-node/issues/846

Identified as issue with libraries in vscode extension. Hezkore has updated the extension and resolved the issue.
I have closed down issue 846 on the vscode-languageserver-node.


Add support for recorded tests

To record:

Set environment variable AZURE_TEST_MODE to Record
Run tests
Copy TestRecords from a bin folder (azure\azure-sdk-for-net\artifacts\bin\Azure.ApplicationModel.Configuration.Tests\Debug\netcoreapp2.1\) to SessionRecords in test project folder

To playback:

Set environment variable AZURE_TEST_MODE to Playback

By default runs tests live
Entries are matched in order using method, uri and headers (excluding Date, x-ms-client-request-id and sanitized headers)
Two interesting extensibility points are RecordedTestSanitizer that allows removing different parts of requests before saving it to file and RecordMatcher that allows changing matching rules (e.g. exclude more headers)
Fixes: https://github.com/Azure/azure-sdk-for-net/issues/5951

By default runs tests live

Is this the right default? I've never been a fan of running tests locally and they all start failing so I'd prefer the default to be reversed. For the same reason we also have issue https://github.com/Azure/azure-sdk-for-net/issues/5767 to try and not require a category to be passed at the command line in order to get passing tests by default.

I'm merging this but plan to continue iterating on features/improvements as we start using recorded tests in storage and KeyVault


Add a Gitter chat badge to README.md

justinwp/cs399-band now has a Chat Room on Gitter
@yourbuddyconner has just created a chat room. You can visit it here: https://gitter.im/justinwp/cs399-band.
This pull-request adds this badge to your README.md:

Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

@yourbuddyconner We should merge this markdown readme into the rst readme or the other way around.

Coverage remained the same when pulling 26ae8a6a41f086bdca339560c1055ca4f255eae3 on gitter-badger:gitter-badge into 54b8ae443f9657bea9e2b81953cebe8e867fde96 on justinwp:master.

This was actually Gitter's pull request, but since we're talking about it I think that we should go with Markdown. Have a preference?

Might as well use markdown.


[SPARK-6405] Limiting the maximum Kryo buffer size to be 2GB.

Kryo buffers are backed by byte arrays, but primitive arrays can only be
up to 2GB in size. It is misleading to allow users to set buffers past
this size.

Test build #29260 has started for   PR 5218 at commit 60634f9.

This patch merges cleanly.

Test build #29262 has started for   PR 5218 at commit 09fd80b.

This patch merges cleanly.

Test build #29260 has finished for   PR 5218 at commit 60634f9.

This patch passes all tests.

This patch merges cleanly.

This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29260/
Test PASSed.

Test build #29262 has finished for   PR 5218 at commit 09fd80b.

This patch passes all tests.

This patch merges cleanly.

This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29262/
Test PASSed.

LGTM

Test build #29273 has started for   PR 5218 at commit e2e30ce.

This patch merges cleanly.

Test build #29277 has started for   PR 5218 at commit 1d6d1be.

This patch merges cleanly.

LGTM pending jenkins

Test build #29273 has finished for   PR 5218 at commit e2e30ce.

This patch passes all tests.

This patch merges cleanly.

This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29273/
Test PASSed.

Test build #29277 has finished for   PR 5218 at commit 1d6d1be.

This patch passes all tests.

This patch merges cleanly.

This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29277/
Test PASSed.

LGTM - merged into master.


Remove mention of internal telemetry that does not exist

What needs to be changed?
The "Values observable with internal metrics" section in the Collector "Internal telemetry" page (docs/collector/internal-telemetry) mentions a number of metrics which (as far as I know) are not actually implemented, or listed in the detailed table of metrics below. To list some: data reception / export rates in bytes, data drop rates caused by throttling / invalid data, incoming connection rate, queue size in bytes, end-to-end and per-component latency, etc.
It looks like this list was taken from an old "Observability Vision" document added to the core repo years ago, and the wording somehow changed from "these values need to be observable" to "these values are observable" along the way. (Thank you to @mx-psi for finding this PR.)
The simplest solution would be to delete the section, and let people rely on the table below it. A more involved solution would be to rewrite the section to only include things that actually ended up being implemented. We may want to keep the current contents around somewhere to serve as a roadmap for future new internal metrics.

@open-telemetry/collector-approvers ptal

@jade-guiton-dd, you probably have the best context right now about what we actually have there available at the moment. Would you be open to adjusting this page?

Sure, I can do the change.


Fix122logg

Logging Module Implemented. Logger class created in Logger.py file and logs.log are saved in folder wplay/log. Instances are added which are working successfully.

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- wplay/onlinetracker.py  1
- wplay/utils/Logger.py  1

Clones added
============
- wplay/messageblast.py  1
- wplay/messagetimer.py  1
- wplay/wchat.py  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- wplay/onlinetracker.py  1
- wplay/utils/Logger.py  1

Clones added
============
- wplay/wchat.py  1
- wplay/messageblast.py  1
- wplay/messagetimer.py  1

See the complete overview on Codacy


DataIter.Next what is the exact datastructure that must be returned ?

Hello I'm trying to make a DataIter for segmentation.
Based on this https://github.com/tornadomeet/mxnet/blob/seg/example/fcn-xs/data.py I was able to make something work for batchsize 1. Now I wanted to increase the batchsize but cannot make it work.
I have
def next(self):
    ..
    return DataBatch(data=DATA label=LABEL, pad=self.getpad(), index=None)

When I have batchsize 1 DATA = an mx.nd.array of shape 1,1,128,128 wrapped in [].
So a python array with 1 element of type mx.nd.array of shape 1,1,128,128
Now for bigger batch  sizes I tried (batchsize 10):
DATA is an mx.nd.array of shape 10,1,128,128. wrapped in []
So a python array with 1 element of type mx.nd.array of shape 10,1,128,128
Now I get the error:
Check failed: (shape_[0]) >= (end) Slice end index out of range
Then I thought I should put 10 elements in the python array of shape 1,1,128,128
But then I got the error : ndarray has not method copyto.
The error is in this piece of code:
def _load_general(data, targets):
    """Load a list of arrays into a list of arrays specified by slices"""
    for d_src, d_targets in zip(data, targets):
    if isinstance(d_targets, nd.NDArray):
        d_src.copyto(d_targets)
    else:
        for slice_idx, d_dst in d_targets:
        d_src[slice_idx].copyto(d_dst)

What is the expected datastructure ?
Thanks.. mxnet looks very promising.

The shape here should be consistent with what provide_data and provide_label return.

Got it! it. Copied too much code and provide_data and provide_label where fixed at batchsize 1.
It works now !
I tried the same idea with caffe and cxxnet with disappointing results without finding out why.
With mxnet I could write my own iterator and solver and really (easily) look what was going on in the net. Now I got it working in 2 days.
Great stuff !


Upgrade 0.51.0->0.56.1-rc1->0.56.1 - Not able to restore inter host connectivity even after network agent restart/reboot.

Server version - > Upgrade 0.51.0->0.56.1-rc1->0.56.1
Fresh install of 0.51.0 with 9 Ubuntu hosts having global Lb service with targets as 2 global services.
Upgraded to rancher-server version - 0.56.1-rc1
After upgrade 2 of the 9 instances lost connectivity with other hosts on managed network.
Trying to reboot hosts/ restarting network did not restore connectivity.
The issue was because of rancher-net process within the network agent running with gsm=false when it should have been launched with gsm=true.
Upgraded to rancher-server version - 0.56.1
The hosts that did not have connectivity on managed network with other hosts continues to not have connectivity.
Restarting network agent/rebooting host did not help restore connectivity.
When I attempt kill rancher-net process in the network agent using the command below then new  rancher-net process is launched with gsm=true and network connectivity is restored.
killall -9 rancher-net

When I attempt to restart network agent on this host , I see the host looses  connectivity with other hosts on managed network because the rancher-net process is launched again with gsm=false.

Closed as obsolete.


Why ReadMe.md haven't mention the doc's url and No install instructions?

Hi, as the title.
I know the doc url is http://deep-qa.readthedocs.io/en/latest/models/about_models.html, but I suggest place it in the ReadMe.
To use the liabrary , I must add project path to PYTHONPATH manully?

Thanks, that's a good suggestion.  You can get to the docs by clicking on the docs badge at the top, but a more explicit link would be a good idea.  Care to submit a PR to add one?
As for installing this, we've started the process to get this on pip, but haven't quite thought this is totally ready for a public release yet, so we haven't actually done it, or announced this project anywhere.  So, yes, you'll need to put this on your PYTHONPATH somehow for now.