Function wrongly identified as only used within its scope if also referenced in another scope

Problem
Input:
let g;
const f = (() => {
  const ext = 1;
  const f = (0, () => ext);
  g = (0, () => f);
  return f;
})();

export default (f => {
  const h = (0, () => f);
  return { g, h };
)(f);

Output:
export default {
  g: ((ext, f) => (f = (0, () => ext), () => f))(1),
  h: (f => () => f)(x)
};

The output code is invalid - x is not defined.
Cause
This fault introduced in 3fbfa84 (which is included in v0.5.2).
Problem is that functions are considered as only used internally within their scope if they have no dependents or assignments.
https://github.com/overlookmotel/livepack/blob/a4b3aedf71b05cd259a365d4777eef89f27216a5/lib/serialize/blocks.js#L173
In above example, f is used outside its scope, but because it's only used within scope of another function (h) it has no dependents. The dependencies of a scope are only added when the scope is constructed. Because g is exported first, the scope for the first closure is processed first. At this point f has no dependents, so it is incorrectly deduced to be used only within its own scope.
Possible solutions
Two solutions I can see:
Solution 1
Create records for scopes earlier, when a first function in that scope is serialized. The scope record could have all the values in that scope added to it as dependencies.
Then later on the scope record could be fleshed out when blocks are processed.
This would be pretty complicated. Circular references would need to be recorded as assignments instead of dependencies. If on first encounter it's not circular, but then when serializing another function later it becomes circular, the dependency would need to be changed to an assignment.
Solution 2
Record on fnDef objects all blocks in which a function is referenced.
Then current order of operations could remain the same as it is. When constructing blocks + scopes, the list of blocks can be consulted and function is only identified as scope-internal if all those blocks are within the block in which function is defined.
This requires less changes and is simpler to implement, but has disadvantage of introducing another property on fnDef whose only purpose is to fix this bug.

Example above shows this problem where occurs in sibling blocks.
Same problem occurs when function defined in one scope is referenced in a child scope:
Input:
const ext = 1,
  f = (0, () => ext),
  getF = (0, () => f),
  getG = (g => () => g)(f);
export default { getF, getG };

Output:
export default {
  getF: ((ext, f) => (
    f = (0, () => ext),
    () => f
  ))(1),
  getG: (g => () => g)(x) // <-- `x` is undefined
};

Also same problem when function defined in one scope is referenced in another scope in same block:
Input:
function outer(g) {
  const ext = 1,
    f = (0, () => ext);
  return {
    f,
    getF: (0, () => f),
    getG: (0, () => g)
  };
}

const { f, getF } = outer(),
  { getG } = outer(f);
export default { getF, getG };

Output:
const createScopeOuter = (ext, f, g) => (
    f = (0, () => ext),
    [
      _g => g = _g,
      () => f,
      () => g
    ]
  ),
  scopeOuter = createScopeOuter();
scopeOuter[0](x); // <-- `x` is undefined
export default {
  getF: createScopeOuter(1)[1],
  getG: scopeOuter[2]
};

Solution 1 above I think is the better one.
Scope records are already created when serializing functions in that scope.
Also when serializing the function, would need to create dependencies between scope record and all values in that scope (except undefined which is a special case because may be omitted from the createScope() call).
A function is only considered as used only within its scope if all the function record's dependents are the record for the scope in which it's created. NB function could have its own scope depend on it more than once if it is used in more than one scope var e.g.:
const ext = 1,
  f = () => ext,
  g = f;
export default [ () => f, () => g ];

In above case, scope record would depend on function f twice as vars f and g in that scope both = function f.
The scope to scope value dependencies would be created initially with no node or key. When blocks are constructed in processBlock() the dependency objects would be fleshed out by defining node and key referring to the createScope() function call.
As noted above, the complication is circular references. Where value is circular, would need to remove the dependency and replace it with an assignment in processBlock(). This is doable, however.


Bazel build targets dependent on v3 APIs from go-control-plane fail to build

Title: Bazel build targets dependent on v3 APIs from go-control-plane fail to build
Description:
I have a custom ext-authz server implementation that is dependant/imports envoy's go-control-plane module and that generates a custom jwt based of the information present on a given header.
On this server I have implementations for both of Envoy's v2 and v3 API.
Recently, due to the removal of zlib 1.2.11, I was forced to update my Bazel rules, Gazelle and Bazel versions.
At the same time I also updated my go modules to the latest available versions, including go-control-plane:
module github.com/celsosantos/edge-proxy

go 1.16

require (
	github.com/dgrijalva/jwt-go v3.2.0+incompatible
	github.com/envoyproxy/go-control-plane v0.10.1
	github.com/golang/protobuf v1.5.2
	github.com/lestrrat-go/jwx v1.0.5
	golang.org/x/net v0.0.0-20220403103023-749bd193bc2b // indirect
	golang.org/x/sys v0.0.0-20220403205710-6acee93ad0eb // indirect
	google.golang.org/genproto v0.0.0-20210226172003-ab064af71705
	google.golang.org/grpc v1.36.0
	google.golang.org/protobuf v1.28.0 // indirect
)

While targets that implement/depend on the v2 API are working and building just fine, any targets that are dependent on the v3 API are failing to build with the following message:
ERROR: /workspace/api/v3/BUILD.bazel:5:11:
no such package '@com_github_envoyproxy_go_control_plane//envoy/service/auth/v3':
BUILD file not found in directory 'envoy/service/auth/v3' of external repository @com_github_envoyproxy_go_control_plane.
Add a BUILD file to a directory to mark it as a package. and referenced by '//api/v3:api'

I have a reproduction of the issue at CelsoSantos/edge-proxy as well as further information on the repo's README Issue #2
What is going on? Why would targets that implement the v2 API work just fine while the ones that depend on v3 implementation fail? I see the sources in the correct place, so I don't understand why this would break.
Did something change on Envoy's API or build that would trigger this issue?
Thanks

cc @keith

cc @kyessenov

I don't know much about golang dep management, but based on the go.sum file in that repo I think you are somehow pointing at an old version of the go-control-plane repo. Here are the related entries:
github.com/envoyproxy/go-control-plane v0.9.0/go.mod h1:YTl/9mNaCwkRvm6d1a2C3ymFceY/DCBVvsKhRF0iEA4=
github.com/envoyproxy/go-control-plane v0.9.1-0.20191026205805-5f8ba28d4473/go.mod h1:YTl/9mNaCwkRvm6d1a2C3ymFceY/DCBVvsKhRF0iEA4=
github.com/envoyproxy/go-control-plane v0.9.4/go.mod h1:6rpuAdCZL397s3pYoYcLgu1mIlRU8Am5FuJP05cCM98=
github.com/envoyproxy/go-control-plane v0.9.9-0.20201210154907-fd9021fe5dad/go.mod h1:cXg6YxExXjJnVBQHBLXeUAgxn2UodCpnH306RInaBQk=
github.com/envoyproxy/go-control-plane v0.10.1 h1:cgDRLG7bs59Zd+apAWuzLQL95obVYAymNJek76W3mgw=
github.com/envoyproxy/go-control-plane v0.10.1/go.mod h1:AY7fTTXNdv/aJ2O5jwpxAPOWUZ7hQAEvzN5Pf27BkQQ=

I see that the v3 directory doesn't exist when I peek into bazel's internal checkout of that repo as well:
% ls bazel-out/../../../external/com_github_envoyproxy_go_control_plane/envoy/service/auth
v2      v2alpha v3alpha

even though it's clearly in the tag you're trying to specify https://github.com/envoyproxy/go-control-plane/tree/v0.10.1/envoy/service/auth

Also if I look in bazel-out/../external/bazel_gazelle/deps.bzl I see the old version being loaded as well:
    _maybe(
        go_repository,
        name = "com_github_envoyproxy_go_control_plane",
        importpath = "github.com/envoyproxy/go-control-plane",
        sum = "h1:4cmBvAEBNJaGARUEs3/suWRyfyBfhf7I60WBZq+bv2w=",
        version = "v0.9.1-0.20191026205805-5f8ba28d4473",
    )

Well, somehow, somewhere, I managed to fix this. I think (though not 100% certain) that it was actually go mod tidy that was calling back previous versions of envoy (I don't know from where or why, though), so much so that they are still there and I can't remove them..
But this PR, fixes whatever issue was present before: CelsoSantos/edge-proxy#1.
I'm closing the issue.
Thank you everyone for the help, especially @keith which helped to guide a starting point for a fix/investigation into the issue.

Glad you fixed it!


DNN library is not found

Python version：3.9.12
CUDA version：11.3.109
CUDNN version：8.2.4
jax version: 0.3.15
jaxlib version: 0.3.15+cuda11.cudann82
GPU: RTX 3070

I ran into the same issue and solved it by installing CUDNN.

I have installed CUDNN ，version：8.2.4

I ran into the same issue and solved it by installing CUDNN.

I have installed CUDNN ，version：8.2.4

I ran into the same issue and solved it by installing CUDNN.

I have installed CUDNN ，version：8.2.4

It works with cudnn 8.2 only


BasicPublishArguments: deprecate immediate field

RabbitMQ versions starting with 3.0.0 do not support it.
Closes #82

the build failed due to clippy error, please check

Clippy warns of deprecated field usage in the library itself. Disabling it for individual expressions is considered experimental.
I guess I'll just leave it as is since any user of this field will get a visible connection error from RabbitMQ.


Making signature-pad stay put?

Am I missing something? I know I will need to create a pop-up on mobile devices to enter the signature in, but how do I stop it sliding around ...
AH it's dependent on the browser being used. Seems I can't use 'Dolphin' and have to switch back to the generic browser and all is good ...
SO the question becomes what browsers work best on android when trying to use signature_pad?

I have never used Dolphin browser before, but if you create a popup that takes up the whole screen then it shouldn't be scrollable... If it's still a problem, please reopen it. Some demo on jsfiddle, jsbin, etc. that shows this issue together with a version of Dolphin browser you're using would be really helpful.


[W5.7][T16-3]Rahul Rajesh

Added Update Command
Still a work in progress

CI fails because you did not update your I/O tests. Please check again.

LGTM

Thanks for the feedback!


No animation on firefox

Hi,
I build application using your Foundation for Apps. Your new grid is totally awesome, but I found out that is very slow on firefox. Every reflow of application takes about 200ms. This cause animation lag even in your example apps.
Check out this: http://foundation.zurb.com/apps/app-templates/travel/#!/photos. When I click on Reviews or Listing in chrome there is nice animation, in firefox there is lag, flash and new screen :(
I use 36.0.1 version of firefox for ubuntu, but I checked on mac and found out same issue.
According to this: http://updates.html5rocks.com/2013/10/Flexbox-layout-isn-t-slow the slowest part is align-items: stretch, which is default value for every .grid-block element.

View animation recently got an overhaul (#386), and it's now way more robust and stable. We were able to pretty thoroughly test it in all of the browsers we support as well. It'll be in version 1.1, which we're trying to get out on Friday.
The align-items: stretch thing is interesting. We use that to ensure that columns in a horizontal grid are all equal-height, since height: 100% tends to not cut it. But we could give it another look, also, if it's a performance hit.

Hi,
that's good news :) I pulled newest master but I'm afraid that reflow action on my Firefox fell into some neverending loop. Maybe I did something wrong - I will wait for stable 1.1 version. Thanks!


Compares' to hashcat

Please let me which better in between hashcat or HashPlusPlus..

Hi.
Hashcat has superior performance to Hash++ due to its included OpenCL and CUDA parallel-processing features which perform massively parallel calculations on the GPU rather than the CPU. Hash++ runs solely on the CPU and, as a result, does not have these parallel capabilities implemented nor do I plan on doing it anytime soon.
If you'd like to benchmark Hashcat on your system, you can run the command hashcat -b. You can also supply a custom device via the -d option.

Thanks


F1: Reserved names not respected when reference includes whitespace

For example {{my_dimension._value}} is correctly exempted from F1, but {{ my_dimension._value }} with the trailing whitespace is not due to a failed comparison to a list of reserved names.
The capture groups in this regex should not capture any surrounding whitespace for subsequent reserved name checks to work correctly

Fixed in 2.1.3


docs: mention how to remove old venv in ~/.cache

Description
Mention how to remove old venv
Changes

editor_setup.md

Related Issues
None
Checklist

[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings

Codecov Report

Merging #453 into development will increase coverage by 0.07%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development     #453      +/-   ##
===============================================
+ Coverage        67.49%   67.57%   +0.07%
===============================================
  Files               81       81
  Lines             3775     3775
===============================================
+ Hits              2548     2551       +3
+ Misses            1227     1224       -3

Impacted Files
Coverage Δ

jumpscale/tools/startupcmd/startupcmd.py
87.01% <0.00%> (+1.29%)
:arrow_up:

jumpscale/core/exceptions/exceptions.py
100.00% <0.00%> (+3.03%)
:arrow_up:

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 c692e37...8f5669e. Read the comment docs.


Group member limbo?

on dev in the group "the cook"
I am a member but I dont see the controls to leave the group. There should be either a 'apply' button, 'leave' or 'edit'/'delete' depending on what role I have. I think I am a regular member but I cannot leave the group?!?!

We figured that this can happen if someone creates a group (= automatically is admin), but then passes on the ‘admin’ role. In that case the creator becomes a regular group member. But still cannot leave the group, because they stay the ‘creator’ (or owner). This is not the expected behaviour. One should become a regular member and be able to leave the group. The role of ‘owner’ or ‘creator’ for groups is not necessary. There should only be ‘admin’ and ‘non-admin’ group members.

So far nothing broke and I am now able to leave the group like a normal member. Looks good!


Semantic representations question

👋Hi there, I have another question about how the predicates work in your system.
I noticed for this sentence:
λx(cat(x) ∧ ¬∃y(like(x, y) ∧ dog(y))) is the set of all cats that do not like a dog, etc.
That the like() predicate takes in 2 args that are not events...just straight up boolean variables. I'm wondering how you reconcile a parse like this with a parse for a sentence like "I like cats." which I think would produce the event based parse of:
∃e(like(e) ∧ arg1(e)="I" ∧ arg2(e)=λxcat(x))
In this case are you storing 2 different "like" predicates for downstream axiom resolution, or are you somehow resolving the event parameterized representation with the strongly parameterized representation?
I saw this example in your thesis actually, so sorry if the answer was in there and I missed it!

The real world conflict might come from the 2 sentences "All cats like fish. The bird likes fish." and the query being "Does the bird and the cat like fish?" The system would need to have the same predicate for the 2 sentences to resolve the query to True correctly.

Hello! This is a good question. Actually, "cats that do not like a dog" would be represented as something more similar to:
λx(cat(x) ∧ ¬∃e(like(e) ∧ arg1(e)=x ∧ ∃d(dog(d) ∧ arg2(e)=d)))
And so "like" would have the same meaning as in "I like cats."
Did I use the like(x,y) example in the thesis after introducing event/neo-Davidsonian semantics? If so, that's either a mistake, or it was written for the sake of conciseness.

Ah gotcha thanks! Yeah it was on page 94 so it was right before you talk about the event semantics. I think I was just jumping around the thesis trying to see how it all fits together.
So when you are doing set semantics, is the existence event for cats just assumed by the system? Or do you have code that inserts the cat predicate if it isn't in the theory by the time you are doing the λx(cat(x) ... )
BTW, do you have time to hop on a quick zoom call? I would love to ask you more questions about the thesis and your take on semantics in general. I'm actually friends with Dan and he offered to introduce me but I wanted to take some more time to understand your work 😆

So any set that can be expressed in higher-order logic exists, but whether or not that set is empty is not known apriori. So the set of "cats that don't like a dog" always exists, but usually, sentences will also express whether the set is empty: "I saw a cat that doesn't like a dog." This would be parsed into something like:
∃C(C=λx(cat(x) ∧ ...) ∧ ∃c(C(c) ∧ ∃s(see(s) ∧ past(s) ∧ arg1(s)=me ∧ arg2(s)=c)))
where C is the set of cats that don't like a dog. So ∃c(C(c) ∧ ...) states that there exists a c which is an element of the set C.
Sure, I'd be happy to talk! Perhaps send me an email and we can arrange a time sometime this week?

Ah gotcha, so in the improbable case of higher order logic parses that contain sets that are empty, I'm assuming your code just gracefully simplifies the expression to False?
Sounds good thanks, will send you an email!

The code will attempt to simplify the expression to false, if it is invalid (there are no possible worlds in which the expression is true). So for example λx(cat(x) ∧ ¬cat(x)) would be simplified to λx.⊥. But λx(cat(x) ∧ dog(x)) would not be simplified, since there is a possible world in which an object exists that is both a cat and a dog.


(PUP-7282) Fix acceptance test to work with manifest

👍

:+1:

@LuvCurves Can you provide some detail in the commit message about what was broken previously, and how the changes fix those issues?

@johnduarte
Test Suite: tests @ 2017-02-28 20:04:11 +0000
  - Host Configuration Summary -

          - Test Case Summary for suite 'tests' -
   Total Suite Time: 64.62 seconds
  Average Test Time: 21.54 seconds
          Attempted: 3
             Passed: 3
             Failed: 0
            Errored: 0
            Skipped: 0
            Pending: 0
              Total: 3

  - Specific Test Case Status -

Failed Tests Cases:
Errored Tests Cases:
Skipped Tests Cases:
Pending Tests Cases:

Looking more closely at the issue, this does not adequately solve this actual problem.  The issue is that the pool 'tstpool' does not exist.  I will push a better fix on to this soon.

tests/resource/zone/ticket_4840_should_create_zone_with_zpool.rb passed in 282.82 seconds
Test Suite: tests @ 2017-03-01 18:37:25 +0000
  - Host Configuration Summary -

          - Test Case Summary for suite 'tests' -
   Total Suite Time: 282.82 seconds
  Average Test Time: 282.82 seconds
          Attempted: 1
             Passed: 1
             Failed: 0
            Errored: 0
            Skipped: 0
            Pending: 0
              Total: 1

  - Specific Test Case Status -

Failed Tests Cases:
Errored Tests Cases:
Skipped Tests Cases:
Pending Tests Cases:

A fresh look at the original issue was helpful in clarifying this.
https://projects.puppetlabs.com/issues/4840

@joshcooper Did you want to take a quick look before we merged

@LuvCurves Sorry but I'm still not sure what the test is fixing by reading the commit message, e.g. why are we changing to ip => net1, did the test fail sometimes because previous runs didn't clean up after themselves leaving zpools behind?

@joshcooper The manifest is an example from a customer.  So I didn't want to modify it unless it was necessary for the environment.  I'm not sure this test ever worked, but if it did, the previous environment had an unplumbed interface that could be referenced as "ip.if.1". That is not the case with the LDom we are using. The available unplumbed interface is net1. It does not work if I try to use the old interface reference:

Begin tests/resource/zone/ticket_4840_should_create_zone_with_zpool.rb
Zone: ticket #4840 - verify that the given manifest works.
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) 21:16:19$ mkdir /tstzones
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) executed in 0.28 seconds
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) 21:16:19$ mkfile 2500m /tstzones/dsk
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) executed in 17.60 seconds
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) 21:16:37$ zpool create tstpool /tstzones/dsk
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) executed in 0.66 seconds
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) 21:16:37$ mktemp -t apply_manifest.pp.XXXXXX
/tmp/apply_manifest.pp.INayXc
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) executed in 0.26 seconds
localhost $ scp /tmp/beaker20170301-4932-hv2pmk solaris-11-sparc:/tmp/apply_manifest.pp.INayXc {:ignore => }
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) 21:16:38$ puppet apply --verbose /tmp/apply_manifest.pp.INayXc
Notice: Compiled catalog for sol11-1.delivery.puppetlabs.net in environment production in 0.18 seconds
Info: Applying configuration version '1488403000'
Notice: /Stage[main]/Main/Zfs[tstpool/tstfs]/ensure: created
Notice: /Stage[main]/Main/File[/ztstpool/mnt]/mode: mode changed '0755' to '0700'
Error: Could not boot zone: Execution of '/usr/sbin/zoneadm -z tstzone boot' returned 1: zoneadm: zone tstzone: WARNING: Skipping network interface: net resource for 'ip.if.1': unable to find physical 'ip.if.1': object not found.
zone 'tstzone': error: failed to find network device:
zoneadm: zone tstzone: call to zoneadmd(1M) failed: zoneadmd(1M) returned an error 9 (zone state change failed)
Error: /Stage[main]/Main/Zone[tstzone]/ensure: change from absent to running failed: Could not boot zone: Execution of '/usr/sbin/zoneadm -z tstzone boot' returned 1: zoneadm: zone tstzone: WARNING: Skipping network interface: net resource for 'ip.if.1': unable to find physical 'ip.if.1': object not found.
zone 'tstzone': error: failed to find network device:
zoneadm: zone tstzone: call to zoneadmd(1M) failed: zoneadmd(1M) returned an error 9 (zone state change failed)
Info: Class[Main]: Unscheduling all events on Class[Main]
Notice: Applied catalog in 215.68 seconds
sol11-1.delivery.puppetlabs.net (solaris-11-sparc) executed in 220.65 seconds
Begin teardown


Hyperion cannot serialize/deserialize UnconfirmedWarning message

It tries to cast Akka.Actor.ActorPath.Surrogate type to ActorPath
System.InvalidCastException: Unable to cast object of type 'Surrogate' to type 'Akka.Actor.ActorPath'.
   at lambda_method(Closure , Stream , DeserializerSession )
   at Hyperion.ValueSerializers.ObjectSerializer.ReadValue(Stream stream, DeserializerSession session)

I can't reproduce this bug, outside of AtLeastOnceDelivery specs

Related bug
https://github.com/rogeralsing/Wire/issues/75


Use distroless multi-arch image for proxyv2

Address https://github.com/istio/istio/issues/26652 by using a multi-arch distorless images and making the COPY architecture agnostic. Doesn't fully solve the issue of multi-arch building, but it's a start.
A similar patch was used to build multi-arche amd64/arm64 images here: https://github.com/istio/istio/issues/21094#issuecomment-702429990
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[X ] Test and Release
[ ] User Experience
[X ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X ] Does not have any changes that may affect Istio users.

Hi @ecliptik. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@googlebot I signed it!

@ecliptik: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
cc5e76b510c756da394578a230b91bb28de35079
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ecliptik: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
cc5e76b510c756da394578a230b91bb28de35079
link
/test integ-distroless-k8s-tests_istio

unit-tests_istio
1cc5005ad7ed4f2187f0edfc75996cfb39f0af39
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ecliptik: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
1cc5005ad7ed4f2187f0edfc75996cfb39f0af39
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
1cc5005ad7ed4f2187f0edfc75996cfb39f0af39
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Test integ-distroless-k8s-tests_istio is failing with an error iptables-restore v1.6.1: unknown option "--dport" in the istio-init container in the  a-v1, b-v1, multiversion-vistio, and headless-v1 pods.
Prow logs,

https://storage.googleapis.com/istio-prow/pr-logs/pull/istio_istio/27700/integ-distroless-k8s-tests_istio/13979/artifacts/security-ee4974ea08f94bf3a637c0/TestReachability/_test_context/reachability-1-94171-state201945898/cluster-0/a-v1-dcc9ffc75-xbcgk_istio-init.log
https://storage.googleapis.com/istio-prow/pr-logs/pull/istio_istio/27700/integ-distroless-k8s-tests_istio/13979/artifacts/security-ee4974ea08f94bf3a637c0/TestReachability/_test_context/reachability-1-94171-state201945898/cluster-0/multiversion-vistio-c4c7f77d7-dvqzs_istio-init.log
https://storage.googleapis.com/istio-prow/pr-logs/pull/istio_istio/27700/integ-distroless-k8s-tests_istio/13979/artifacts/security-ee4974ea08f94bf3a637c0/TestReachability/_test_context/reachability-1-94171-state201945898/cluster-0/headless-v1-6cd9d784f5-l98hr_istio-init.log

Looking into the reason why this would happen as the changes a minor and comparing a container build from master and one from this PR show the same files under /usr/lib/x86_64-linux-gnu/. The version of iptables is the same (1.6.1-2ubuntu2) as well. Seems like it may be related to Docker networking after some initial searches.
Example error from an istio-init container log.
iptables-restore --noflush /tmp/iptables-rules-1601680477199687860.txt343480718
iptables-restore v1.6.1: unknown option "--dport"
Error occurred at line: 6
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-save
# Generated by iptables-save v1.6.1 on Fri Oct  2 23:14:37 2020
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed on Fri Oct  2 23:14:37 2020
panic: exit status 2

goroutine 1 [running]:
istio.io/istio/tools/istio-iptables/pkg/dependencies.(*RealDependencies).RunOrFail(0x4a7f020, 0x2ca983d, 0x10, 0xc00129ee60, 0x2, 0x2)
	istio.io/istio/tools/istio-iptables/pkg/dependencies/implementation.go:44 +0x96
istio.io/istio/tools/istio-iptables/pkg/cmd.(*IptablesConfigurator).executeIptablesRestoreCommand(0xc00183fd70, 0x7fa636ff2e01, 0x0, 0x0)
	istio.io/istio/tools/istio-iptables/pkg/cmd/run.go:554 +0x38a
istio.io/istio/tools/istio-iptables/pkg/cmd.(*IptablesConfigurator).executeCommands(0xc00183fd70)
	istio.io/istio/tools/istio-iptables/pkg/cmd/run.go:561 +0x45
istio.io/istio/tools/istio-iptables/pkg/cmd.(*IptablesConfigurator).run(0xc00183fd70)
	istio.io/istio/tools/istio-iptables/pkg/cmd/run.go:499 +0x2b7b
istio.io/istio/tools/istio-iptables/pkg/cmd.glob..func1(0x4a1f3a0, 0xc0007a8c00, 0x0, 0x10)
	istio.io/istio/tools/istio-iptables/pkg/cmd/root.go:58 +0x150
github.com/spf13/cobra.(*Command).execute(0x4a1f3a0, 0xc0007a8b00, 0x10, 0x10, 0x4a1f3a0, 0xc0007a8b00)
	github.com/spf13/cobra@v1.0.0/command.go:846 +0x2c2
github.com/spf13/cobra.(*Command).ExecuteC(0x4a1f640, 0x0, 0x0, 0x0)
	github.com/spf13/cobra@v1.0.0/command.go:950 +0x375
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.0.0/command.go:887
main.main()
	istio.io/istio/pilot/cmd/pilot-agent/main.go:497 +0x31

Closing out bad rebase for PR.


bug(tekla): Saved Streams are not preserved

Description
When a stream is Saved via Tekla connector, saved streams are not preserved when file/project is restarted.
Expected Behaviour
Kaydettiğim stream’i görmek isterdim.
Steps to reproduce

Open tekla connector
Save a stream
Close Tekla Structures
Reopen Tekla Structures
Enable Speckle connector

Streams/Commits Used
https://speckle.xyz/streams/c1f59d8484
Screenshots
Stream saved 👇

Restarted Tekla, saved stream is not preserved.

do we do this with other connectors ?

do we do this with other connectors ?

yes we do with revit and rhino afaik

@Reynold-Chan is there a PR associated with this issue? The status is set to Needs Testing, but I don't see where the issue has been referenced in a PR.


support Bedrock

hi @JackHopkins
WIP for bedrock support
I'm testing at my side, working. But need align with you to make a good progress for the MR.
How can I can contact you ...etc (discord invite is invalid)
thanks

Hey Kevin -
You can join here: https://discord.gg/ymmV6FKg
LMK if you can't and I can add you via email!
Daniel Kwak, CEO
Paperplane ( https://www.paperplane.ai/ )
404-704-2999
On Tue, Nov 21, 2023 at 6:01 PM, Kevin Truong < @.*** > wrote:

hi @ JackHopkins ( https://github.com/JackHopkins )
WIP for bedrock support
I'm testing at my side, working. But need align with you to make a good
progress for the MR.
How can I can contact you ...etc (discord invite is invalid)
thanks
—
Reply to this email directly, view it on GitHub (
https://github.com/monkeypatch/monkeypatch.py/pull/81#issuecomment-1821832804
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AHVPE5SGIJAPRSL24LSID7LYFUXDDAVCNFSM6AAAAAA7VKKPTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRRHAZTEOBQGQ
).
You are receiving this because you are subscribed to this thread. Message
ID: <monkeypatch/monkeypatch. py/pull/81/c1821832804 @ github. com>


Access Requests to MacOS Document/Desktop Folders

Godot version
4.0 dev alpha 8
System information
MacOS 12.3.1 Arm64
Issue description
My Godot 4.app has full access to my drive in my Security and Privacy settings.  Yet if my Godot project is located in my Desktop or Documents folder, when I start Godot, it prompts me for access to the folder.  When I run the project, it prompts me multiple times before it will start.  Even if I choose OK, it continues to prompt me every time.
If I move the project to a normal folder location, then it works fine.
Steps to reproduce
Create a new project in your Documents folder.
Save the new scene with Node2D as the root.
Run the scene.
Minimal reproduction project
No response

cc @bruvzg

No.  I've never had this problem on 3.4.4 or 3.5 but then again I've never compiled Godot before.  I will give it a try.
J

Try removing it from the Privacy Settings (with a - button), this is not specific to Godot, and sometimes happens when you update the app or have multiple copies.

My Godot 4 app is named "Godot 4.app" so it shows as different from my Godot 3.x in the security list.  I removed all references to all versions of Godot in the Full Disk and the Folders permissions.    But it keeps asking me multiple times.  And I verified that the Godot 4.app is listed in the Folders security for the Desktop.   So the request for permission was stored but it doesn't seem to be verifying against it properly.
When I compiled and bundled the app, I followed the compile instructions except that the final universal file name was different than the one listed in the instructions.  Other than that, the compile of Godot 4 was uneventful.


upgrade lxml

Coverage remained the same at 86.098% when pulling 3b3299b2c8c01be6d319e52ef3f151f4aea14851 on peterbe:upgrade-lxml into 7d9bbcbc35bf4c5040ead559f175b73bf6d7843e on mozilla:master.


head method not needed

I think the head method for the handler is not needed.
https://github.com/hadim/jupyter-archive/blob/55fbf191ab3b055e304de05e8b4b9e7af6583afa/jupyter_archive/handlers.py#L48
It's useful only for file to get some information on them without their content.

Closed by 7ac9295cd05eea2b9ea00eb41248ef14582e0641


Changes to stored_procedure with oracle

We had a trouble with the stored procedure, first the function was
strict with the package name, with this implementation the package is
optional, and the second is that the bind_by_name was failt, because it
was assigning two ids of connection, one time at binding and other when
the query excecute.

I just pushed a bugfix for the binding bug (you can see the commit linked above). Yours was based on CI2 and because of that, it actually made more breaks.
However, the package parameter is a larger issue than it seems and allowing an empty string to be passed would be a band-aid on a bullet wound. See #3981 for more details.


Problem with building complex translations

I have a problem with building complex translations.
Let's assume I want to use multiline translations and some html inside...
So for test purposes  I have this declaration in one of my lang files:
 'test'      => <<<'TEXT'
Test </br>
Test
TEXT
,

@rmariuzzo any idea on how to solve this?

@chilio what about using multiline string in PHP as follow:
 'test'      => "TEXT
Test </br>
Test
TEXT"
,

Note where the opening and closing " are.

@rmariuzzo this is solved for now, but wouldn't you think of integrating all php arrays types in your package to cover this scenario?

@chilio indeed we should cover it. We can take a look together and see how to implement it properly.

@rmariuzzo great to hear that, but as said before I'm pretty new to javascript modules, therefore I could help more on testing or php side.
For the moment it seems that your php parsers should be able to follow HEREDOC and NOWDOC convention to make it work.
BTW In php 7 and upwards there is no limitation in strings on 64-bit systems (which I believe are the most used cases for latest laravel, but for sure not all), so therefore it might not get much of usage. So my conclusion is, if you can provide this functionality with small effort , please do,
Anyway let me know, if you decided to make this package more cross-versions compatible and especially if you have any build to test that out....


MailboxProcessor.Receive() does not terminate when cancelled

If a mailbox processor started with a cancellation token invokes Receive() with no timeout, cancellation of the token does not cause it to terminate.
In the following code example, the message "Terminated" is never printed:
open System.Threading
let c = new CancellationTokenSource()
let m = MailboxProcessor.Start((fun inbox -> async {
    try
        printfn "Started"
        while true do
            let! s = inbox.Receive()
            printfn "Received %s" s
    finally
        printfn "Terminated"
  }), c.Token)

Thread.Sleep 100
c.Cancel()
Thread.Sleep 1000

Some changes that do cause the agent to terminate are:

Making a dummy post to the mailbox after cancelling the token.
Ensuring the token is cancelled before Receive() is invoked.
Passing any timeout value >= 0 to Receive().

I haven't investigated in-depth, but the last point suggests that the problem is in Mailbox.waitOneNoTimeout() in control.fs, as this method of waiting is only used when the timeout is unspecified. I note that other asynchronous primitives contain code to register actions with their given cancellation tokens, whereas this function does not.
This bug is present in the F# open-source repository as of commit 9f24461f0d1097235b75a09d473f375e707fad0a (8 Feb 2016), but it appears to have always been there.

This seems to have been fixed in FSharp.Core 4.3.1.. it prints "Started" + "Terminated". Previous versions (4.2.3) only prints "Started".

@stmax82 thanks!


Can't localize strings with HTML

Describe the bug
I have a string that contains HTML. Whenever I try to render it, it just outputs the key rather than the string.
Occurs in next-i18next version
<EMAIL_ADDRESS>Steps to reproduce
public/static/locales/en/signup.json
{
"accept-terms": "By clicking below to create your account, you are agreeing to our Terms of Service"
}

src/pages/signup.tsx
import { TFunction } from 'next-i18next';
import { withTranslation } from '../../i18n';
const Signup = ({ t }: { t: TFunction; i18n: I18n }) => {
  return (

{t('accept-terms')}

  );
}
Signup.getInitialProps = async () => ({ namespacesRequired: ['signup', 'common'] });
export default withTranslation(['signup', 'common'])(Signup);

I also tried this as an alternative (I tried both with and without passing i18n={i18n} to the Trans component:
import { I18n } from 'next-i18next';
import { withTranslation, Trans } from '../../i18n';
const Signup = ({ i18n }: { i18n: I18n }) => {
  return (

      <Trans i18n={i18n} i18nKey="accept-terms" />

  );
}
Signup.getInitialProps = async () => ({ namespacesRequired: ['signup', 'common'] });
export default withTranslation(['signup', 'common'])(Signup);

Expected behaviour
In all cases, it outputted: accept-terms onto the screen rather than By clicking below to create your account, you are agreeing to our Terms of Service.
OS (please complete the following information)

Device: MacBook Pro (16-inch, 2019)
Browser: Brave Version 1.15.76 Chromium: 86.0.4240.111 (Official Build) (x86_64)

next-i18next uses i18next packages under the hood to handle actual translation/interpolation/etc. This sounds like an issue with an upstream package – please have a look at the i18next docs. Good luck!


BUG: np.bool_

I think np.bool_ is pretty common and should be supported:
write_hdf5(fname, np.bool_(1))
currently returns the following error
`
/home/jrking/src/h5io/h5io/_h5io.pyc in write_hdf5(fname, data, overwrite, compression, title)
    103         _triage_write(title, data, fid, comp_kw,
    104                       str(type(data)),
--> 105                       cleanup_data=cleanup_data)
    106
    107     # Will not be empty if any extra data to be written

/home/jrking/src/h5io/h5io/_h5io.pyc in _triage_write(key, value, root, comp_kw, where, cleanup_data)
    166         else:
    167             err_str = 'unsupported type %s (in %s)' % (type(value), where)
--> 168             raise TypeError(err_str)
    169
    170 ##############################################################################

TypeError: unsupported type <type 'numpy.bool_'> (in <type 'numpy.bool_'>)

Note that np.bool is supported.

Probably related to https://github.com/numpy/numpy/issues/3530
Not sure we want to address this here

We could support it, it should only be two more lines in the read and write functions.

Ok, I wasn't sure this was suppose to be changed at some point in numpy. Let me try a quick PR

The last activity on that issue is from over two years ago so I wouldn't hold your breath :)

right


feat(main): :sparkles: cryptographically strong license key

@all-contributors please add @mcnaveen for code


WIP: experiment - see what latency histogram looks like when weighting by # of edits

WIP: experiment - see what latency histogram looks like when weighting by # of edits. Pushing so I can test before deciding if it is a good change.

Motivation

Goal: Surface user pain more clearly. Without this change, 50 edits that dogpile after a slow path are only counted with 1 data point.
Test plan

N/A

I started a new branch with what I believe should be the final shape of this metric.


RFC: A Split HAL

I've been mulling this over for awhile now, and really I'm starting to think...
We should have a HAL crate per chip, that depends on a common HAL (imxrt-hal) still.
My reasoning really comes back to the documentation part of the HAL, along with perhaps not wanting to rely too much on conditional compiles after all, at least at the end user supplied HAL crate.
So imagine the current HAL crate remains, but the Peripherals object that is built ends up in its own imxrt1062-hal crate which hides the need to set the feature flags up from end users.

How granular should the new HAL crates be? Today's RAL and HAL have a feature-flag per chip variant; "imxrt1061" and "imxrt1062" specify unique targets. But, they're nearly identical, and they share a reference manual. Should we consider an imxrt106x-hal crate that can be used by both variants? We could handle discrepancies with HAL-specific feature flags. On a quick-pass through the datasheet, the 61 doesn't have the display and camera components (LCD, CSI, PXP) that the 62 supports. Those could be gated behind an optional feature-flag in the imxrt106x-hal crate. The approach still needs feature-flags, but they're truly for optional features, rather than a required flag for a hardware target.
Alternatively, we could do something similar to the stm32-rs project. The team has a HAL per family and Cortex-M types. Then, they require feature-flags to describe the specific chip they're using. The approach is similar to our current approach in that they require feature-flags to describe devices. But, they have smaller, more granular HAL crates for different chip lines. It might translate to imxrt101x-hal and imxrt106x-hal crates in our project. We could reach out to the team to see if they like their current approach, or if they have any regrets.
Any thoughts on project organization? Regardless on how we require feature-flags, I'm partial to a single repo with a top-level workspace, rather than multiple repos. The HAL crates will probably be developed together, so having them in the one repo will help us coordinate changes.

I like the idea of grouping things together when possible. The 1064 is seemingly a different beast than the 1061/1062, its probably the oddest duck in th the 106x set. There's also the really odd one part that has a DSP alongside it, which I don't really intend on supporting myself. The RAL script does some family segmentation already, but it could probably be changed to be more specific to the imxrt series as we know better what the splits are.
I'm all for the mono-repo with workspace as well. I think it helps really keep things in sync, especially since I believe we will continue to create common drivers for all these chips, with different instances per chip. I still want to try to maximize code sharing.

I think a first step is making the current imxrt-hal crate the imxrt106x-hal crate with feature flag gates for the mentioned components when/if they get added. The second step would be creating a imxrt102x-hal (my task) and moving various common macros/drivers/etc to a common imxrt-hal which they both would depend on.

Seeing how the new new is to have drivers in crates ala imxrt-iomuxc, I'm thinking it makes sense to have a driver per crate, which inevitably all depend on the associated Pin types provided by iomuxc. I really like the new direction @mciantyre has pushed this!

I started this since I finally got probe-rs working with my imxrt101x board, $10 for 500MHz is hard to beat!

So my first goal is to have a imxrt101x-hal and imxrt106x-hal, where the only things I care about for imxt101x-hal are iomuxc, ccm, and lpuart working.
In looking at the lpuart driver, and how imxrt-ral work, I'm starting to think we don't any conditional feature compilation for imxrt-ral at all for the drivers, only the device specific hals that need to know about chip specific peripheral instances.
When I change the ral family base to imxrt, there's very few duplicate devices and a few are suspiciously similar like lpuart.rs and lpuart_v2.rs, with a single bit flag difference between them.
Things like that make me wonder if the SVD is wrong in some cases or if I can change the imxrt-ral to conditional compile that bitflag in the field. I really want to avoid what we have now with conditional compilation if possible in a shared imxrt-hal crate as it makes the build in a single repo impossible.
So I think I'll try hacking imxrt-ral to add a common peripheral refactoring for all families where if the only differences are additive those additive pieces are added on a feature.
At that point then an imxrt_ral::peripheral::lpuart::Instance type can be considered set in stone and work even without a feature flag to imxrt-ral. Meaning an imxrt-lpuart driver can be written and used in device family hal's without a lot of difficulties.

Sounds reasonable! With goals for common register blocks and optional feature flags, it sounds like we're moving away from a "split HAL," and more towards a "unified RAL." Is that the thinking?
Not requiring feature-flags would be a boon for library development. Then, when users are ready to compile their binaries for their system, they can enable a chip-specific feature without too much effort.

A single bitflag difference in LPUART, RIDMA, exists for some but not all chips in the ixmrt line, with no real rhyme or reason.

Looks like it's missing from the 1021 SVD. I confirmed that the RIDMAE bit exists in the LPUART BAUD register, offset 20, in each 1010, 1015, 1020, 1050, 1060, and 1064 reference manual.

I'm still thinking the end hal is a split, but the end hal effectively needs to do only a few things, define the number and kind of peripherals into a struct Peripherals and possibly deal with some of the clocking diffences. We'll see though!

Reason for the Split

Simpler end user crates (include the appropriate hal, most drivers would conditional compile against the imxrt-ral)
Requiring a feature for the end user crate or BSP crate seems questionable
Some chips vary enough to warrant it, when unifying the imxrt-ral to one family there are some significant differences between peripherals that need to be accounted for somehow

TODO

[ ] Fixup workspace to match https://github.com/nrf-rs/nrf-hal layout, with HAL per chip and a common hal (#89)
[ ] Move most code from imxrt1062-hal to imxrt-hal-common or perhaps peripheral driver crates (see imxrt-iomuxc) when sensible.
[ ] Create a imxrt1011-hal

Questions and Answers

Should we change imxrt-ral so there's only one device family, but multiple RegisterBlock types when differening devices exist?

One of the previously stated values of a spit HAL was to support documentation, so I'd like to get your thoughts on how that will work.
In #89, we're changing documentation examples from imxrt_hal to imxrt106x_hal. As we consolidate drivers into something like imxrt_hal_common, we'll re-export those drivers from the imxrt106x_hal and other chip-specific HALs. I see documentation working a few different ways:

When we move the driver code into the common HAL, we also move the driver documentation. Those imxrt106x_hal namespaces become something like imxrt_hal_common. Since the chip-specific HAL's re-export the driver as-is, the end-user sees namespaces with imxrt_hal_common in the imxrt106x_hal documentation. This is inconsistent for the end-user, but can be taught by a top-level statement resembling "assume that all documentation implicitly includes use imxrt106x_hal as imxrt_hal_common."
When we move the driver code into the common HAL, we do not move the driver documentation. Instead, we only document the re-exported driver in the chip-specific HAL. This requires us to apply documentation examples across all chip-specific HALs. However, the documentation for the imxrt106x_hal is consistent with its name. We're OK with having little documentation on the common HAL.

Are there other approaches we could take that don't have these trade-offs? It doesn't look like the nrf-hal has an approach for documentation examples, as the crates do not yet have documentation examples.

Supposed I'm a user who wants to design a higher-level crate that works across multiple i.MX RT chips. The imxrt-uart-log crate falls into this category (let's pretend that it's maintained outside of the imxrt-rs project). What will be our policy for supporting users who want to design these libraries?

We'll let users consume the imxrt_hal_common crate, so that their API works easily for all chip-specific HALs. This is similar to where we are today. To support this, we need to keep maintaining the feature-flag documentation. This goes against the nrf-hal approach, which says "Don't use this directly.".
We adopt the same approach as nrf-hal: the imxrt_hal_common is an implementation detail, and we're free to break users to satisfy our chip-specific HALs. As an imxrt-uart-log developer, I need to either mimic the structure of the public HALs, and implement imxrt106x-uart-log, imxrt101x-uart-log, etc. crates; or, I need to adopt feature flags that selectively choose a chip-specific HAL.

Is there another way to support external users who want to create libraries for multiple chips?

Should we change imxrt-ral so there's only one device family, but multiple RegisterBlock types when differening devices exist?

Concretely, this would mean imxrt-ral has a feature called "imxrt106x" which consolidates the two "imxrt1061"1 and "imxrt1062"` features? If so, I'd say no, we don't need to have multiple register blocks. In some previous studies, it looked like the 1061 and 1062 chips were so similar they wouldn't warrant different register blocks. If we need to support multiple register blocks, they should be behind a different RAL feature.
Semi-related: we may want to change our chip naming schema to more closely match the reference manuals and product identifiers. I proposed the "x" suffix back when we started discussing split HAL, and then I used it in the imxrt-iomuxc crate. I'm concerned that was the wrong call, since the "x" suffix doesn't distinguish common support for the 1010 and 1015 families, which seem to be pretty different.

After better understanding the differences, I'm with you on ditching "x" suffix, as each chip really is different enough to warrant its own feature flag I believe.

[...] simply refer to those examples (with links hopefully) [...]

Links back to examples works for me. We lose the benefit of documentation tests that make sure our examples are relevant. It's on us to make sure these links don't point to stale or unreleased examples; a crate release from 5 years ago will need to keep pointing to 5 year old examples.

I would recommend we select the correct hal with a feature flag for each variant supported.

We've cited reasons why required, narrowly-scoped feature flags aren't the best. This sounds like we're putting our current problem on users who want to do the same thing we're doing: create drivers that work across chips. If we're all trying to build drivers that work across these systems, shouldn't we help the community figure this out, without having them adopt an approach that tried and didn't like?

If we expose the common crate as a published crate, does that solve most of the issues?
imxrt-uart-log would depend on imxrt-hal-common, and a feature flag would need to be set so the types match those in whatever chip hal your using.
Is that workable?

I think it would be workable.
Sorry, I might be confused about the goals of the common HAL. When I see a reason for splitting up our crates, like

Some conditional compiling needed in imxrt-hal-common, specified by the chip crate on behalf of the end crate user

I'm interpreting that as "we only need conditional compiles when there's a drastic difference between chips." For UART and DMA HAL drivers -- the peripherals needed by imxrt-uart-log -- I'm not expecting to need feature flags in the common HAL.

and a feature flag would need to be set so the types match those in whatever chip hal your using.

Can you clarify why I need feature flags when designing against the common HAL, particularly when consuming a UART and DMA driver API?

You would need a feature flag because currently the RAL types change for each chip, which is partially why i want to unify the RAL crate types

the concrete types depend on RAL types which vary over the chips.

It sounded like a unified RAL could solve that.
I want to make sure we're on the same page with what a unified RAL, and the common HAL, might look like. I linked to my experiments below.
https://github.com/mciantyre/proto-hal
Could you let me know if this meets your thoughts on how this could work? The experiment seems to show that, with some restructuring to our dependencies, we should be able to create general crates, like imxrt-uart-log, that use the common HAL without required feature selection.

A unified ral can solve most of the problem I agree, in looking at the proto-hal you have, that is indeed what I was hoping to accomplish!


Gcmon 354 investigate various timeouts for gcmrc

Increased the UI timeout from 10 minutes to 20 minutes, since this is the complete start of completed/all data received time.  We know we have some requests that run as long as 15 minutes.  Also improved the reporting of errors so that it would be obvious if the error was a UI timeout.

:+1:


Add Fazaia college of education for women

Kindly merge it on master branch so i our staff can use jetbrain product
University website: https://fcoe.edu.pk/
Course: https://fcoe.edu.pk/bscs/

@rubiya10 First stage of verification passed, official domain for Fazaia college of education for women is fcoe.edu.pk as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@rubiya10 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


🍒 Cherry pick PR #5770 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/5770 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.1.7-14 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @AndrewGable in version: 1.1.7-24 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Cannot connect to my remote MySQL from docker

I have a java application which has a connection to remote MySQL DB:

The url, port, username, password of remote MySQL is clear.
The connection is JDBC and program use c3p0 pool in code.
The application is a JAR, it has all packages and CONFIG file inside.
I had already ran it in some LINUX system successfully.

However, it just failed to connect to MySQL when i run it into docker.

The docker has the whole java environment.
Other parts of program is fine(port mapping, receiving socket data, etc)
No exception about DB connection
It just stopped before the connection work(the first SQL execution).

No DB exception at all, so weird.
Could you guys help me?

The GitHub issue tracker is for reporting bugs and feature requests, and not intended as a general support forum for using docker. For other questions, consider using

The Docker Support Forums - https://forums.docker.com
The Docker Community Slack Channel - https://blog.docker.com/2016/11/introducing-docker-community-directory-docker-community-slack/
Post a question on StackOverflow, using the Docker tag

When asking the question there, I suggest to provide some more information, as it's not clear from your question what exactly fails, what IP-address/host your application is trying to connect to, etc.
Try to write down a minimal way to reproduce the situation, so that others can help answering your questions.
I'll close this issue here, because this is a support question on using docker, not a bug report or feature request


Auto nong not working sometimes

Geode : updated
Jukebox and auto nong : updated
Playing on Android
Issue : the auto nong logo is appearing half of the times on levels where there are supposed to be

it's a bug on android. I'm not sure what's causing it yet but you can workaround it for now by:
going into settings -> view indexes -> press plus button -> apply settings.
this will force the indexes to be refetched


AWS S3 remote cache

Add support for using AWS S3 as online cache for scan results.
Provides a S3FileStorage class which extends FileStorage and uses official Amazon's  AWS Java SDK to store scan results.
Issue oss-review-toolkit/ort#730

@carlos-ardila2 is there any interest from your side to move this forward?

@sschuberth I'm back in. I apologize for taking this long to get back to this task. The AWS requirement to use an alpha version for the Kotlin S3 library was a set-back. I've addressed most of the issues and squash in a single commit. I know it is not the best way to do it, but I thought it would be best to start fresh for the refactor. Regards.

@sschuberth I'm back in. I apologize for taking this long to get back to this task. The AWS requirement to use an alpha version for the Kotlin S3 library was a set-back. I've addressed most of the issues and squash in a single commit. I know it is not the best way to do it, but I thought it would be best to start fresh for the refactor. Regards.

@carlos-ardila2 please rebase this once more onto latest main to get rid of some unrelated code changes ("afterwards" -> "afterward") and to address unrelated test failures.

Done

Test failures are unrelated.


Fix 668

For iOS, when a project is using pods (if the cordova push plugin is installed for example), npm run xcode should open the .xcworkspace file instead of the .xcodeproj file, otherwise the build will fail.

Thank you for the fix, I will integrate it manually

@webmass - Why did you close this pull request?


Failing to restore from snapshot "stat /backup/c-mwdrm-ml-cbfbm: no such file or directory"

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Rancher server 2.2.2 (single node, host mounted folder), 3 etcd nodes, snapshot the cluster, shutdown the 3 etcd nodes, wait for etcd nodes to be marked unavailable, shut down rancher, tar the data dir, bring up rancher again on a new host with same data dir, bring up another (fourth) node and add to cluster, try and restore the snapshot.
Result:

2019/12/27 04:15:51 [INFO] Provisioning cluster [c-mwdrm]
2019/12/27 04:15:51 [INFO] Restoring cluster [c-mwdrm] from backup
2019/12/27 04:15:54 http: TLS handshake error from <IP_ADDRESS>:49872: EOF
2019/12/27 04:15:56 [INFO] kontainerdriver rancherkubernetesengine listening on address <IP_ADDRESS>:43421
2019/12/27 04:15:56 [INFO] Restoring etcd snapshot c-mwdrm-rl-bk4nc
2019/12/27 04:15:56 [INFO] Successfully Deployed state file at [management-state/rke/rke-909977729/cluster.rkestate]
2019/12/27 04:15:56 [INFO] [dialer] Setup tunnel for host [<IP_ADDRESS>]
2019/12/27 04:15:56 [INFO] [dialer] Setup tunnel for host [<IP_ADDRESS>]
2019/12/27 04:15:56 [WARNING] Failed to set up SSH tunneling for host [<IP_ADDRESS>]: Can't establish dialer connection: can not build dialer to [c-mwdrm:m-4648cd9672a0]
2019/12/27 04:15:56 [INFO] [dialer] Setup tunnel for host [<IP_ADDRESS>]
2019/12/27 04:15:56 [WARNING] Failed to set up SSH tunneling for host [<IP_ADDRESS>]: Can't establish dialer connection: can not build dialer to [c-mwdrm:m-9c5139608457]
2019/12/27 04:15:56 [INFO] [dialer] Setup tunnel for host [<IP_ADDRESS>]
2019/12/27 04:15:56 [WARNING] Failed to set up SSH tunneling for host [<IP_ADDRESS>]: Can't establish dialer connection: can not build dialer to [c-mwdrm:m-b3d734dd55b9]
2019/12/27 04:15:56 [WARNING] Removing host [<IP_ADDRESS>] from node lists
2019/12/27 04:15:56 [WARNING] Removing host [<IP_ADDRESS>] from node lists
2019/12/27 04:15:56 [WARNING] Removing host [<IP_ADDRESS>] from node lists
2019/12/27 04:15:56 [INFO] Checking if container [cert-deployer] is running on host [<IP_ADDRESS>], try #1
2019/12/27 04:15:56 [INFO] Image [rancher/rke-tools:v0.1.28] exists on host [<IP_ADDRESS>]
2019/12/27 04:15:56 [INFO] Starting container [cert-deployer] on host [<IP_ADDRESS>], try #1
2019/12/27 04:15:56 [INFO] Checking if container [cert-deployer] is running on host [<IP_ADDRESS>], try #1
2019/12/27 04:16:02 [INFO] Checking if container [cert-deployer] is running on host [<IP_ADDRESS>], try #1
2019/12/27 04:16:02 [INFO] Removing container [cert-deployer] on host [<IP_ADDRESS>], try #1
2019/12/27 04:16:02 [INFO] Stopping container [etcd] on host [<IP_ADDRESS>] with stopTimeoutDuration [5s], try #1
2019/12/27 04:16:02 [WARNING] Can't stop Docker container [etcd] for host [<IP_ADDRESS>]: Error response from daemon: No such container: etcd
2019/12/27 04:16:02 [INFO] Stopping container [etcd] on host [<IP_ADDRESS>] with stopTimeoutDuration [5s], try #2
2019/12/27 04:16:02 [WARNING] Can't stop Docker container [etcd] for host [<IP_ADDRESS>]: Error response from daemon: No such container: etcd
2019/12/27 04:16:02 [INFO] Stopping container [etcd] on host [<IP_ADDRESS>] with stopTimeoutDuration [5s], try #3
2019/12/27 04:16:02 [WARNING] Can't stop Docker container [etcd] for host [<IP_ADDRESS>]: Error response from daemon: No such container: etcd
2019/12/27 04:16:02 [INFO] [etcd] starting backup server on host [<IP_ADDRESS>]
2019/12/27 04:16:02 [INFO] Image [rancher/rke-tools:v0.1.51] exists on host [<IP_ADDRESS>]
2019/12/27 04:16:02 [INFO] Starting container [etcd-Serve-backup] on host [<IP_ADDRESS>], try #1
2019/12/27 04:16:02 [INFO] [etcd] Successfully started [etcd-Serve-backup] container on host [<IP_ADDRESS>]
2019/12/27 04:16:07 [INFO] Removing container [etcd-Serve-backup] on host [<IP_ADDRESS>], try #1
2019/12/27 04:16:07 [WARNING] failed to start backup server on host [<IP_ADDRESS>]: Failed to run backup server container, container logs: time="2019-12-27T04:16:02Z" level=fatal msg="stat /backup/c-mwdrm-rl-bk4nc: no such file or directory"

.51, .52, .53 are the first 3 nodes that are gone.
.42 is the new fourth node. c-mwdm-rl-bk4nc is a manual persisted snapshot.
Other details that may be helpful:
Tried several rancher versions from 2.2.2 to 2.3.3. The .42 node hangs at "Registering" while the other three hang at "Unavailable". The error message repeats periodically. I also get errors like

unable to recognize "management-state/tmp/yaml-426531530": the server is currently unable to handle the request

which I think is related to the first three nodes being unavailable.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.3.3
Installation option (single install/HA): single install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom

Machine type (cloud/VM/metal) and specifications (CPU/memory): Proxmox VMs, debian 10.2, all nodes 2 vcpu, 15 GB memory, 50 GB ssd.

Kubernetes version (use kubectl version): v1.16.3-rancher1-1

Docker version (use docker version): 18.09.9

Tried a few more things to recover from my snapshot:

Created a new cluster with single etcd node
Copied etcd/member/snap/db to the etcd node
Used assaflavie/runlike to get the etcd's run command
Stopped the etcd container, installed etcdctl, and ran etcdctl restore with the copied db and all paths found from #3. Restore said it rebuilt something... seems fine?
Started etcd again
Rancher then reports... "Failed to communicate with API server: Unauthorized"
Tried rotating certificates; ended up at the same error.

Also tried creating a 4th node in the same cluster (and hung at registering) so that mounted folders are correct. No etcd container is started in this case, so I repeated steps 2-4. Also tried repeating this with --force-new-cluster. No difference, existing cluster has all of the dead nodes still listed and the new node waiting.


Is this detection method a white-box setting?

Hello, I have learned your work on backdoor detection of neural network. I want to confirm if your method are under white-box condition(because the mask and reversed trigger generation require the gradient of the model). But there is a paper says that your method are under black-box condition (https://arxiv.org/pdf/2007.10760.pdf    Page. 22, Table II). I think the authors are wrong, what do you think?

Without too much context into the paper, I can't comment on whether authors are wrong or not. But I can try clarify our assumptions in Neural Cleanse. We design the system from the defender's perspective, meaning people owning the model trying to detect, analyze, and remove potential backdoors. This means the defender already has the model and a small clean dataset.

OK, thank you very much.


Add PowerToys Logo on Azure Pipelines

Add in the profil of Azure Pipelines the logo from PowerToys as profile picture.

Because now it's looking very unprofessional.


Improve Dialogs to allow Keyboard input

Is your feature request related to a problem? Please describe.
When ever I try to delete a container in OrbStack, it promts a dialog "data will be permanently lost.". I like this check, but I am really annoyed that I have to use my mouse to confirm. This is especially painful when you want to delete multiple containers in a row, where you could click through the containers and use your keyboard to confirm the dialogs.
Describe the solution you'd like
I would like to be able to confirm dialogs with the ENTER key on my keyboard.

Additional context

Hmm, it's standard macOS behavior that destructive confirmation prompts can't be confirmed with "Return".

@siemendev How I do it? TAB (to get the focus on the right button) and then Space to confirm. You need to enable keyboard navigation for this:

Even though I would hope that we could do this in orbstack itself, this helped me lots. Thank you, @tisba!

AFAIK OrbStack does behave like a good, native macOS application and adheres to system defaults. IMO that's a rather good thing (compared to non-native Browser-based applications e.g.).


Create a WiKi page about installing OrientDB using different ways

We should create new pages for:

[ ] Install with wget
[ ] Install with MacOSX homebrew
[x] Install with Dockers
[ ] Start OrientDB server on Amazon AWS
[ ] Start OrientDB server on Jelastic (we're waiting for the Jelastic post about it)

We already have this in docs.


What is reason to use hackney directly instead of use httpoison library?

I am new to elixir. I am sorry if my question is trivial
I wonder what is the benefit of using hackney directly instead of use httpoison?

First of all, HTTPoison is built on top of hackney (which is thus a dependency of HTTPoison). The reasons we didn't go with HTTPoison are:

hackney introduces one less level of dependency (e.g., what if hackney updates but HTTPoison doesn't update that); this is especially important given this is a library other projects/people will depend on, so introducing one less dependency for them is important (and as far as I'm concerned, this is the main reason)
HTTPoison is a bit less tweakable than hackney in favour of an easier interface


feat(chat): Link list element and source attribution

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

Testing / Reviewing
{{ Add descriptions, steps or a checklist for how reviewers can verify this PR works or not }}

i'm also seeing a big gap here from the last chart to the message Anna mentioned with "hellloooo"


fix exception message for "categories" error

When I copied "_translate" function for categories, I changed filter strings, but overlooked the exception messages, so now it's valid. I'm sorry for this, but I discovered it only when wrote some tests for the api ><
Perhaps it makes sense to put all exception messages in separate constant variables to avoid such situations and make code more compact, but this is up to you, of course.

By the way, speaking of tests, I write them for my other project, they test the whole WallHavenAPI class, if you don't mind, I can share them in the next pull request when they are done.


feat(muta): link up metadata service with muta

What type of PR is this?
feat
What this PR does / why we need it:
link up metadata with muta.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Missing code to read the metadata after each block execution and update it in consensus.status.

Missing code to read the metadata after each block execution and update it in consensus.status.

plan to do it in next PR


Using python and test plugin fails to recognise pixi environment

Hi vscode-python folks,
I have been using the Python plugin with pytest and the test plugin for a long time with conda/mamba environments, but I have recently switched to Pixi for python environment management. Using the Python plugin, I have pointed the interpreter to my pixi environment path, and have been able to run notebooks and the like using the interpreter.
However, the test plugin does not recognise the pixi environment as a pixi environment, showing the following output error when searching for the tests:

It appears like it can't find pixi, so is trying to run it as a mamba environment.
I am running vscode using the "remote" plugin on WSL 2 Debian
vscode version:

Python plugin version:
v2024.12.3
Any help would be great, as I can't wait to use all of these new tools together!

Is the .pixi directory at the root of your active workspace? I'm using a multi-root workspace and Vscode can't find Pix envs properly if there isn't a .pixi at the root of each project. In my case, I am using symlinks to the single .pixi I have.

hi, @PanTheDev. Thank you very much for the advice, the pixi directory is in the project root (in this case ~/repos/vision-suite-2024/forecasting/. However, the pixi utility is installed in another location ~/.pixi/bin/pixi does that need to be in the active directory of the vscode project as well?

@PanTheDev  Your advice set me on the right track actually, apparently I was typing in the full path when setting the python interpreter in the "enter interpreter path.." field:

however, if I use the relative path to the workspace root, the test extension works!
One thing that could be a bug or improvement to the vs code-python package is that the listed interpreter file path shows up as the relative path, even if you have typed in the full path. Therefore, I needed to find out that I had typed it incorrectly.

if I enter the full path here as an interpreter environment:

It will show up as the relative path:

and cause the no interpreter drama:

Great note! Would be important to fix - thanks!

@karthiknadig what are your thoughts on this issue here regarding relative vs absolute paths and how they are displayed with the environments?

This should be looked at by pixi owners. /cc @baszalmstra @wolfv
@anthonykim1 in case you have some context on this.

I think the assumption is we pretty much expect and calculate only starting from projectDir/workspaceDir from https://github.com/microsoft/vscode-python/blob/7ccf01ebe33624a7dbb7b69abe5e0c3db11d3735/src/client/pythonEnvironments/common/environmentManagers/pixi.ts#L294
Wondering if making this prefix more generic to cover absolute path will resolve this issue.

Yeah it makes sense that that would help!


Create rough layout structure of TAS Builder Feature

A rough outline of the UI - like it is in the current tool

Obsolete


Openshift installer tarball for rhel 9 extracts to openshift-install-fips

From OCP 4.16 onwards a new separate installer tarball is added for rhel 9 (openshift-install-rhel9-s390x.tar.gz).
The normal binary is for rhel 8.
Downloading this and extracting it results in installer binary called openshift-install-fips instead of openshift-install.
This will cause AOP install to fail as it wont find openshift-install binary.
❯ wget https://mirror.openshift.com/pub/openshift-v4/s390x/clients/ocp/4.16.5/openshift-install-rhel9-s390x.tar.gz
❯ tar -xzf openshift-install-rhel9-s390x.tar.gz
❯ ls
 openshift-install-fips   openshift-install-rhel9-s390x.tar.gz

A possible work around for this is to mirror the installer and oc client tarballs
You download, extract, rename the installer binary, host it in a location on a file server and provide that URL to clients_download_url
A possible fix would be to detect the binary name after extraction and rename it
in shell this can be done as below
FN=`ls openshift-install*`
if [[ $FN != "openshift-install" ]]; then
    mv $FN openshift-install
fi

Of course we would do similar thing in ansible.

I think this affects any rhel 9 bastion based install

@mohammedzee1000 With this PR you are able to use fips to install OCP using ABI.


onloadwff.js: Uncaught TypeError: Cannot read property 'type' of undefined

Describe the bug
When I press Enter in the compose body, the js console in Chrome shows the following error:
onloadwff.js:71 _Uncaught TypeError: Cannot read property 'type' of undefined_
    at e.setFieldValue (onloadwff.js:71)
    at HTMLFormElement.formKeydownListener (onloadwff.js:71)

To Reproduce
Steps to reproduce the behavior:

Go to Inbox
Click on Compose
Open the JS Console
Type in the message body field and press Enter
See error

Expected behavior
There should be no errors
Screenshots

Desktop (please complete the following information):

OS: iOS
Browser: chrome
Version N/A

This appears to be related to the Lastpass extension receiving propagated events.
We can add a workaround so extensions don't receive the enter key event info.

fixed in #40


how to integrate it with zkteco k14?

how do i link machine with my php file and how will it submit me the finger print id/number?
can you please guide me and let me know about the api in action or a sample.

Have you been able to connect to the zkteco k14?

I developed the library using a Q2i and iclock580 both of them using
firmware zem 800 and 600
Be sure your device meets the requirements described in README.md file.
Due I don't have any devices to develop on, the development of the library
has been stopped.
Sorry,
El 30/06/2017 12:56, "aries288"<EMAIL_ADDRESS>escribió:

Have you been able to connect to the zkteco k14?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cobisja/tad-php/issues/25#issuecomment-312319497, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJzLMkxY7JChPXLLQLVokUPsSyyW9QMWks5sJSirgaJpZM4NiOU6
.


Allow modification of replace property in Builder

This feature will be added to the Plugin info modal, and allow people to specify the plugins that their plugin intends to replace, including the plugin code and version constraints.

Ready for review.


Scrolling when nearing top/bottom of droppable container / sortable container.

Are there any plans on implementing this?
Here is an example from dnd-kit:
https://master--5fc05e08a4a65d0021ae0bf2.chromatic.com/?path=/story/presets-sortable-vertical--basic-setup

Closed as duplicate of https://github.com/thisbeyond/solid-dnd/issues/57


Demo available

Hello, is there a demo of this available anywhere that I could try out before diving in?

Yes, there's a github pages for this repository :-)

https://swimmingkiim.github.io/react-image-editor

Export All Frame and Export Selected Frame are not working. Nothing happen when click on the export options.


Switch from short var names to longer in one test file

This changes 2 variable names in one test file such that they do not violate the WPS111 rule as reported by the wemake style guide being vetted.
This should help users of tox -e lint-vetting identity errors related to the changes they may be proposing instead of needing to sift through errors unrelated to their changes.
Before:
1     C812 missing trailing comma
1     RST304 Unknown interpreted text role "mod".
13    S101 Use of assert detected. The enclosed code will be removed when compiling to optimised byte code.
1     S404 Consider possible security implications associated with the subprocess module.
1     S603 subprocess call - check for execution of untrusted input.
2     S604 Function call with shell=True parameter identified, possible security issue.
2     WPS111 Found too short name: p < 2
2     WPS115 Found upper-case constant in a class: KEGEX
3     WPS201 Found module with too many imports: 13 > 12
6     WPS210 Found too many local variables: 6 > 5
3     WPS220 Found too deep nesting: 24 > 20
2     WPS221 Found line with high Jones Complexity: 16 > 14
3     WPS226 Found string literal over-use: test_option > 3
9     WPS305 Found `f` string
1     WPS316 Found context manager with too many assignments
6     WPS317 Found incorrect multi-line parameters
2     WPS323 Found `%` string formatting
4     WPS324 Found inconsistent `return` statement
2     WPS414 Found incorrect unpacking target
1     WPS430 Found nested function: getcwd
14    WPS436 Found protected module import: _curses
3     WPS450 Found protected object import: _CursesWindow
1     WPS602 Found using `@staticmethod`

After:
1     C812 missing trailing comma
1     RST304 Unknown interpreted text role "mod".
13    S101 Use of assert detected. The enclosed code will be removed when compiling to optimised byte code.
1     S404 Consider possible security implications associated with the subprocess module.
1     S603 subprocess call - check for execution of untrusted input.
2     S604 Function call with shell=True parameter identified, possible security issue.
2     WPS115 Found upper-case constant in a class: KEGEX
3     WPS201 Found module with too many imports: 13 > 12
6     WPS210 Found too many local variables: 6 > 5
3     WPS220 Found too deep nesting: 24 > 20
2     WPS221 Found line with high Jones Complexity: 16 > 14
3     WPS226 Found string literal over-use: test_option > 3
9     WPS305 Found `f` string
1     WPS316 Found context manager with too many assignments
6     WPS317 Found incorrect multi-line parameters
2     WPS323 Found `%` string formatting
4     WPS324 Found inconsistent `return` statement
2     WPS414 Found incorrect unpacking target
1     WPS430 Found nested function: getcwd
14    WPS436 Found protected module import: _curses
3     WPS450 Found protected object import: _CursesWindow
1     WPS602 Found using `@staticmethod`

@cidrblock I find the message from zuul with fatal: -L invalid line number: 0' very annoying. I was hoping @webknjaz would fix it as he is the major promoter of the vetting job.

@ssbarnea what are you talking about? FWIW I don't think it is related to WPS.

Ah, you may be talking about the new GitHub App that nobody seems to know who added. That's not something that I can fix, we need to find who did that.

@cidrblock FYI markdown code blocks support diffs in syntax highlighting. Using that is better than separate before/after because it's more visual.

recheck

@cidrblock FYI markdown code blocks support diffs in syntax highlighting. Using that is better than separate before/after because it's more visual.

Cool, I'll try that next time! Good idea, TY


Adds Dependabot yml config file

Automatic dependencies update by Dependabot
Dependabot is a Github service that scans opensource projects and create a pull request each time a dependence is updated.
The pull request is tested informing if the change will pass against your pipelines.
You can also see if other projects have failed with the new version before accept or reject the pull request.

I don't see the need for this, as there's nothing wrong with an end user using a slightly older version of a dependency. This would also likely include breaking versions of dependencies, which is not desired — they would require matching breaking versions of time. Dependabot is better suited to binaries, not libraries.

I have some considerations bout your comment

I don't see the need for this
To be warned when a security fix is available

there's nothing wrong with an end user using a slightly older version of a dependency
Perfect. But the point of be analyzed is to informed and to have automatic tests running on different versions so you can update your documentation when some update breaks the code

Dependabot is better suited to binaries, not libraries
Dependabot only warns you about the update by opening a pull request. You don't have to update. Just keep informed.

To be warned when a security fix is available

I'm already running a RUSTSEC check three times a week, which will notify me of any potential security issues. An issue will be opened automatically if any exist (this has never happened).

Perfect. But the point of be analyzed is to informed and to have automatic tests running on different versions so you can update your documentation when some update breaks the code

Updates won't break code because the few dependencies I have all follow semver. Since Cargo.lock isn't committed (as is standard for libraries), the latest semver-compatible release is used by default (excluding cache).

Dependabot only warns you about the update by opening a pull request. You don't have to update. Just keep informed.

It's unnecessary noise. As I noted above, security vulnerabilities are already automatically caught, Any other patch upgrades are simply not necessary, and breaking upgrades are unwelcome in general as they would amount to a breaking change in the time crate.

I'm gonna search about RUSTSEC. But do you have any link to how to add this to some pipeline?

As with a few other things, I have a job that runs on GitHub Actions.
security-audit:
  name: Security audit
  runs-on: ubuntu-20.04
  steps:
    - name: Checkout sources
      uses: actions/checkout@v2

    - name: Audit dependencies
      uses: actions-rs/audit-check@v1
      with:
        token: ${{ secrets.GITHUB_TOKEN }}


wings: 2.2.4 -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/wings/versions.
meta.description for wings is: "Subdivision modeler inspired by Nendo and Mirai from Izware"
meta.homepage for wings is: "http://www.wings3d.com/"
meta.changelog for wings is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found <IP_ADDRESS> with grep in /nix/store/1l0dcrzfx1phpmy0mi01mjbwh00xf9hq-wings-<IP_ADDRESS>

directory tree listing: https://gist.github.com/372298024c1b2b7491409e1587ff0cc7

du listing: https://gist.github.com/2973a02474c58f3f964796c613d0cfc3

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
wings

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1l0dcrzfx1phpmy0mi01mjbwh00xf9hq-wings-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wings https://github.com/r-ryantm/nixpkgs/archive/fa8c371bfeaa4b7d54fcc8c58cc0851b46820b8d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1l0dcrzfx1phpmy0mi01mjbwh00xf9hq-wings-<IP_ADDRESS>
ls -la /nix/store/1l0dcrzfx1phpmy0mi01mjbwh00xf9hq-wings-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

wings

Maintainer pings
cc @viric for testing.

new release available


Monitor Google map creation

This hits a new logging endpoint most times we create a Google Map instance so we can investigate ways to cut down on use. This should monitor almost every Google Map on the site that goes through our custom createMap method in map3.js.erb, which means it's ignoring the location choose in the Uploader since that's using a third-party React component. The node endpoint is filtering by origin, which means it's denying all requests that don't come from inaturalist.org, so if the source of our extreme usage is on one of the partner sites we're going to miss that, but I figure this will at least get us started.

This all looks good to me. I think we could add a call to iNaturalist.log in the componentDidMount method of the uploader location chooser if we wanted. Also, why are you authenticating these log calls with the application JWT when the node API isn't checking authentication? Seems like we could remove the auth part of the call, or we should be checking it on the API end. We probably don't need to authenticate these calls unless problems arise

This all looks good to me. I think we could add a call to iNaturalist.log in the componentDidMount method of the uploader location chooser if we wanted. Also, why are you authenticating these log calls with the application JWT when the node API isn't checking authentication? Seems like we could remove the auth part of the call, or we should be checking it on the API end. We probably don't need to authenticate these calls unless problems arise

I think we could add a call to iNaturalist.log in the componentDidMount method of the uploader location chooser if we wanted

Done.

Also, why are you authenticating these log calls with the application JWT when the node API isn't checking authentication?

Correct me if I'm wrong, but I was trying to authenticate the calls with the user's JWT, not the application JWT. I'm doing that because I want to be able to discriminate between sign-in and signed-out map loads. If we're getting a lot of map loads from signed out people or from bots that might demand a different remedy.

I think we could add a call to iNaturalist.log in the componentDidMount method of the uploader location chooser if we wanted

Done.

Also, why are you authenticating these log calls with the application JWT when the node API isn't checking authentication?

Correct me if I'm wrong, but I was trying to authenticate the calls with the user's JWT, not the application JWT. I'm doing that because I want to be able to discriminate between sign-in and signed-out map loads. If we're getting a lot of map loads from signed out people or from bots that might demand a different remedy.

yep you're right. I wasn't looking closely and thought inaturalist-api-token was the app token, but it's a user token. I did see the API and logstash properly mark requests as signed in, so makes sense to leave it as you have it

yep you're right. I wasn't looking closely and thought inaturalist-api-token was the app token, but it's a user token. I did see the API and logstash properly mark requests as signed in, so makes sense to leave it as you have it


Optimized some functions and made them descriptive

Hello, thanks for this repo! I have been using this repo since a couple of months (mainly on segmented nuclei from H&E slides), and thought of contributing to it to make it a bit better.  If you are interested, I can also add a StarDist2D backend, in addition to CellPose.

Thanks for your contribution!


Cannot open circ files correctly.

It seems that circ files cannot be opened correctly with Logisim. either there are missing components in circuit design, or error raised for missing library (CPUForSnake: The built-in library BFH-Praktika is not available in this version.).
Could you please clarify for which version of Logisim these files were designed to be run?
I have tested on Logisim v2.7.2 and Logisim Evolution v3.8.0

Thanks a lot in advance.
Regards,
Panagiotis.

Hi, thank you for posting your issue, I didn't think about that when posting my video and I don't have my pc near, but I opened the .circ with my phone and it says the version is 2.7.2. You can open any .circ woth any text editor to see qhat version it is intended for. I am going to edit my repository.

Well, you didn't reply, but I am pretty sure this will solve your issue so I am closing it.


More configuration updates in preparation for pentest

Description
More configuration changes requested in preparation for setting these environments up.
Acceptance Criteria

[x] remove nginx, postgres lines from install.sh;
[x] give OK to remove shellcheck;
[x] set Same-Site cookie attribute to "Strict", rather than "Lax";
[x] remove HSTS, other X-headers from nginx / application;
[x] give OK to remove SendGrid credentials from SSM parameter;
[x] advise re:

[x] DB schema updates: corruption if two instances are being deployed at the same time?
[x] scheduler handling multiple AWS instances?

[x] remove nvm from configs;
[x] switch over to unprivileged app-specific service user;
[x] deploy and test changes.

Marking as closed for now - if there are additional small changes, those will likely be merged directly to master.


MGI ids are non-standard CURIE's, eg. MGI:MGI:1890761

expected:

this link should be fine: http://amigo.geneontology.org/amigo/gene_product/MGI:1890761

actual:

received a 404 with the above link
this was the "correct" link: http://amigo.geneontology.org/amigo/gene_product/MGI:MGI:1890761

I tested additional organisms, and didn't see it with anything else.

Also, this is consistent within the GO (MGI:MGI).   If I need to change the way I do link-ins, that is fine, but this seems like it is just incorrect upstream.

Duplicate of
https://github.com/geneontology/go-site/issues/91


Dynamic json parsing

I'm working with an endpoint that is subject to dynamic updates in key and value pairs. What is the most efficient way to parse a nested json object in a json array without knowing the exact key, but knowing potential value characters? I had in mind to iterate over values and simply use switch / if clauses to match contained characters by key value until reaching the nested object. Is that the ideal solution?

if the key is not fixed, you have to parse it into a map, and iterate the keys in runtime


Embroider preparation Tests

Reference Blog:

https://medium.com/@kiwiupover/embroider-preparation-14d59edafc0b

hey thanks for the contribution 🎉  sorry for not getting back to you in such a long time, it's been a bit of an odd year 🙈
We have updated our CI to be using GitHub actions now because Travis has pretty much given up on Open Source communities. I'm wondering if it would be possible to migrate this to the new CI system? Also, do you happen to know how to solve the "allowed failure" issue with GitHub actions?

This PR is outdated, we should use @embroider/test-setup
https://github.com/embroider-build/embroider/tree/master/packages/test-setup

just closing this since you say it's superseded 👍


Cleanup scripts

Removed some logic to reuse what is already provided by kubevirtci
Signed-off-by: Bartosz Rybacki<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/test pull-kvp-functional-test

/lgtm

/approve

/override pull-kvp-functional-test


Bump up woodstox-core to 5.4.0 due to security concerns

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
18m 43s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
45m 13s

trunk passed

+1 :green_heart:
compile
0m 27s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 26s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
mvnsite
0m 33s

trunk passed

+1 :green_heart:
javadoc
0m 34s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 28s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
shadedclient
70m 29s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 17s

the patch passed

+1 :green_heart:
compile
0m 15s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 15s

the patch passed

+1 :green_heart:
compile
0m 15s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 17s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
shadedclient
24m  6s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 20s

hadoop-project in the patch passed.

+1 :green_heart:
asflicense
0m 40s

The patch does not generate ASF License warnings.

117m  4s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5075/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5075

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint

uname
Linux 9be705115b3e 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / fab51604a3a20c3b04cb37fb387cad1857182a0b

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5075/1/testReport/

Max. process+thread count
538 (vs. ulimit of 5500)

modules
C: hadoop-project U: hadoop-project

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5075/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Also the PR title should start with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?


Suggest opening an issue for usage questions

Based on the interaction at #31, this seems like a good iteration on the solution to answering user-type questions.

@chreekat thanks!


Corrected grammatical errors and added hyphens

Nice reading those beautiful codes

@lamberta do we need these changes ?

Thanks, but I think the README copy is pretty set now. But please feel free to fix tensorflow.org docs in the tensorflow/docs repo 😀https://github.com/tensorflow/docs/tree/master/site/en

@lamberta thank you


Example with zebrafish and overlapping histology

Another example illustrating the use that the slicer can have for showing raw imaging data together with region annotation.
Result should look like:

.

That's beautiful!
Only recomendation I would make: add an outline to the text (e.g. black text + white outline) to make it more readable.
Code: https://github.com/FedeClaudi/mathplotlib/blob/255848e767006e60bf1b61585b04812c128d3270/mathplotlib/base.py?_pjax=%23js-repo-pjax-container%2C div[itemtype%3D"http%3A%2F%2Fschema.org%2FSoftwareSourceCode"] main%2C [data-pjax-container]#L34
Example: https://github.com/FedeClaudi/Slam


fix: replying to email fails after sorting a large grid

Switch to Grid-View, select first entry. Then sort after date. In a large grid, selecting "reply To" fails with an error message.