Update cb/simple_cb for upstream mantle changes

There's now a distinct interface for synchronous and asynchronous resets.
I removed the explicit reset=... because the reset signal is automatically wired in the backend, so you don't need to specify it unless you want something different than the default behavior.

gold file updated

Also changed it to not remove the output .json if the test fails (so we can easily inspect the difference and update the gold file if needed)

Nevermind, that change for the output .json was not necessary

Pull Request Test Coverage Report for Build 323

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.035%

Totals

Change from base Build 313:
0.0%

Covered Lines:
134

Relevant Lines:
141

💛  - Coveralls


Date Tracking

Rasa Core version: 0.9.6
Python version: 3.6.5
Operating system (windows, osx, ...): OSX
Issue:
My chatbot is supposed to help the user set weekly goals so I want it to perform certain actions only once a week (ideally on Sundays) that creates the upcoming week's goals. Is there some way to track what day of the week it is and, if it is a Sunday, to trigger that action?
Content of domain file (if used & relevant):

You could check this in a custom action, using datetime and then set e.g. a boolean slot to true/false dependent on what day it is. Then add a story where if it's set to true, trigger the specific action you want to trigger

How would I ensure that the boolean slot is checked/updated at the start of each new day?

You would probably only do this when the user interacts with your bot right? So when the user asks something like "what are my goals", you can have a custom action that sets the slot


Streamline Tuple, make prev inherit from current.

Two major changes:

Simplify the Tuple class for smaller, more efficient code.
Make Tuple _prev object inherit from the current tuple. This will allow the _prev object to act as a proper tuple in its own right, simplifying downstream management (e.g., by aggregators).

Open question: does adding the Object.create call for _prev inheritance cause any of our benchmarks to suffer? (It should actually help with aggregation, but not sure about other cases.)

Unfortunately, it does. Object.create appears to be very expensive (perhaps due to wiring up the prototype chains?).
Early versions of Tuple had _prev as a full fledged tuple via Object.create, as in this PR, and it was one of the things I had to undo after benchmarking.
Except for the Aggregator, I can't think of any other operators that require _prev to function as a tuple unto itself. This is why tuple-spoofing was isolated within the Aggregator, and again avoided Object.create calls.

Though, I guess by isolating it within Aggregator, we actually run the risk of performing more Object.create calls because prev tuple instances aren't shared anymore. Perhaps we should run our benchmarks again with this PR.

In a couple of experiments I am indeed seeing noticeably larger interactive delays and the profiler attributes to them to Object.create calls. So, we might want to look into your "promotion" idea as an alternative.

One thing to keep in mind: currently, _prev is cleared out at the end of
every propagation cycle. This avoids onerous timestamp checks within
operators.
As a result, naive "promotion" (promoting _prev in situ) would continue
to result in poor performance. The Aggregator got around this situation by
stashing prev tuples. Object.create was called only once (per aggregator)
per tuple.
(Side note: if we were to revert to the tuple spoofing within Aggregators,
we should ensure that Object.create is only called once per tuple rather
than per aggr per tuple).
On Tuesday, August 18, 2015, Jeffrey Heer<EMAIL_ADDRESS>wrote:

In a couple of experiments I am indeed seeing noticeably larger
interactive delays and the profiler attributes to them to Object.create
calls. So, we might want to look into your "promotion" idea as an
alternative.
—
Reply to this email directly or view it on GitHub
https://github.com/vega/vega-dataflow/pull/3#issuecomment-132322149.

--
-Arvind
Arvind Satyanarayan http://arvindsatya.com/


How to change service URL in Android Studio plugin

Question
Hello 👋 we've change our introspection.endpointUrl but are seemingly unable to change the service URL used by the plugin. Where is this URL defined if it's not read from the introspection settings?]

Hi! This does come from the introspection URL. This is read after a gradle sync, did you try that? Also note that retrieving this configuration from Gradle may take a few seconds or even minutes if you have many modules.

@BoD it hasn't updated after a gradle sync 😣

Sorry to hear. What if you close/re-open the project?
Also, this config is actually cached - maybe there is an issue with this. I will try to repro and see if I have the issue.
In the meantime, the cache is in your project's .idea/workspace.xml in the <component name="com.apollographql.ijplugin.settings.ProjectSettingsState"> block. I am guessing you see the old value in there? If yes you can remove the whole block, and this should fix the issue (should be done while the project is closed, otherwise the IDE will re-write its in-memory version to the disk when quitting).

Closing and reopening didn't help unfortunately.
Deleting the component block has sort of worked, navigation from the .graphql file to the schema now works but the URL dropdown is now empty 🤔 syncing and close/reopen hasn't helped

Hey @jvanderwee, was wondering if you still have the issue with the latest snapshot version?


TypeError: init() got an unexpected keyword argument 'syntax'

C02QH2D7G8WM:char-rnn-tensorflow userone$ python train.py
Traceback (most recent call last):
File "train.py", line 3, in
import tensorflow as tf
File "/usr/local/lib/python2.7/site-packages/tensorflow/init.py", line 23, in
from tensorflow.python import *
File "/usr/local/lib/python2.7/site-packages/tensorflow/python/init.py", line 35, in
from tensorflow.core.framework.graph_pb2 import *
File "/usr/local/lib/python2.7/site-packages/tensorflow/core/framework/graph_pb2.py", line 16, in
from tensorflow.core.framework import attr_value_pb2 as tensorflow_dot_core_dot_framework_dot_attr__value__pb2
File "/usr/local/lib/python2.7/site-packages/tensorflow/core/framework/attr_value_pb2.py", line 16, in
from tensorflow.core.framework import tensor_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__pb2
File "/usr/local/lib/python2.7/site-packages/tensorflow/core/framework/tensor_pb2.py", line 16, in
from tensorflow.core.framework import tensor_shape_pb2 as tensorflow_dot_core_dot_framework_dot_tensor__shape__pb2
File "/usr/local/lib/python2.7/site-packages/tensorflow/core/framework/tensor_shape_pb2.py", line 22, in
serialized_pb=_b('\n,tensorflow/core/framework/tensor_shape.proto\x12\ntensorflow"z\n\x10TensorShapeProto\x12-\n\x03\x64im\x18\x02 \x03(\x0b\x32 .tensorflow.TensorShapeProto.Dim\x12\x14\n\x0cunknown_rank\x18\x03 \x01(\x08\x1a!\n\x03\x44im\x12\x0c\n\x04size\x18\x01 \x01(\x03\x12\x0c\n\x04name\x18\x02 \x01(\tB/\n\x18org.tensorflow.frameworkB\x11TensorShapeProtosP\x01\x62\x06proto3')
TypeError: init() got an unexpected keyword argument 'syntax'

It seems your tensorflow installation is broken. I recommend the tensorflow github: github.com/tensorflow/tensorflow


Update to RxSwift 2.0.0

Fixes #360

Current coverage is 91.30%

Merging #361 into master will not affect coverage as of c972fdd

@@            master   #361   diff @@
=====================================
  Files           13     13
  Stmts          437    437
  Branches         0      0
  Methods
=====================================
  Hit            399    399
  Partial          0      0
  Missed          38     38

Review entire Coverage Diff as of c972fdd

Uncovered Suggestions

+1.37% via ...ource/Response.swift#76...81
+1.14% via ...+ReactiveCocoa.swift#54...58
+1.14% via Source/Moya.swift#177...181
See 7 more...

Powered by Codecov. Updated on successful CI builds.

Looks awesome, thanks! 🎉

I've invited you to the Moya contributors list – no pressure to accept! If you're curious about what being a contributor means, check out their docs.


Support for struct attributes with reserved names

This fixes #37 but slows struct initialization a bit (actually 1.5x difference), see https://gist.github.com/flash-gordon/f9b99f8c28f0a0d65902cae18035a45f for details. I also added more friendly errors on missing or unknown keys.

@solnic wdyt?

👍

:+1: Nice one


Clarify deps and clean up

Use deps from npm
Clarify peer dependencies for usage in wfm
Remove old deps
Fix missing locale error

Why is the angular-i18n package downgraded to >=1.4.5 from >=1.5.8 ?

@shoobah Because that is what WFM is using atm


Can't perform binary operation on &mut Field and Field

This isn't blocking anything, so not a high priority. It's just something I stumbled upon.
fn my_mutating_fn(a: &mut Field) {
    a += 10;
}

fn main(mut a: Field) -> pub Field {
    my_mutating_fn(&mut a);
    a
}

I'd have expected + to work here.
Compiled using the latest master, from source.

looks like you forgot to deref, but still get error in noir
fn my_mutating_fn(a: &mut Field) {
    *a += 10;
}

fn main(mut x: Field) -> pub Field {
    my_mutating_fn(&mut a);
    a
}

$ nargo execute --show-ssa --experimental-ssa
The application panicked (crashed).
Message:  index out of bounds: the len is 1254 but the index is<PHONE_NUMBER>3709551615
Location: crates/noirc_frontend/src/node_interner.rs:482

This is a bug. We may have already fixed this in newer versions of Nargo so try searching for similar issues at https://github.com/noir-lang/noir/issues/.
If there isn't an open issue for this bug, consider opening one at https://github.com/noir-lang/noir/issues/new?labels=bug&template=bug_report.yml

Doh! Good catch.
Your error is even better!

Thanks for the crash report, I've fixed it locally and will have a PR up soon. The issue is that in main you're using a which was not declared and the mutable reference code did not have a check for this case. Since it needs to check a variable's definition to see if it is mutable and a had no definition. Here's the new error messages with the fix:
error: cannot find `a` in this scope
  ┌─ /.../src/main.nr:8:25
  │
8 │     my_mutating_fn(&mut a);
  │                         - not found in this scope

error: cannot find `a` in this scope
  ┌─ /.../src/main.nr:9:5
  │
9 │     a
  │     - not found in this scope

warning: unused variable x
  ┌─ /.../src/main.nr:7:13
  │
7 │ fn main(mut x: Field) -> pub Field {
  │             - unused variable

Looking at the original code again, it uses a everywhere and doesn't have the x parameter. So it was an uncaught mistake while copying that lead to catching a compiler bug.
@iAmMichaelConnor I would expect your code to work then with only adding the one dereference. Note that you need this dereference because, like in rust, references are separate from their element types. So you cannot add together a &mut Field and a Field. You also cannot assign to a &mut Field directly, oddly enough. You have to dereference it to signal that you're storing the Field in that reference, rather than mutating that reference to be a different reference.


Add ProGuard Rules to Documentation for clickTakePictureButtonCallback

When testing the app in debug mode, I added the following code in the initState method to handle the button tap for taking a photo:
@override
void initState() {
  super.initState();
  cameraController = UVCCameraController();
  cameraController?.clickTakePictureButtonCallback = (String path) {
    // Perform some method
  };
}

This worked perfectly in debug mode, but in release mode, the clickTakePictureButtonCallback did not seem to work.
After some investigation and reviewing the documentation provided about ProGuard rules, I added IButtonCallback and related rules to the proguard-rules.pro file, and it worked!

-keep interface com.jiangdg.uvc.IButtonCallback {
    *;
    }

Could you please consider adding these ProGuard rules to the README?

Okay. Thank you.


Remove Art Appreciation

The update makes it fundamentally incompatible with Twitch Plays, especially so when we block interactions with solved modules for good reason.

Would it be possible to, instead of removing it, having the module recognize when a module that needs to be appreciated is zoomed? I think displaying the name of the module on the module for TP only would make it a lot easier as well, although it isn't necessary.

The !zoom 60 still solves it, even it depends on other module

Closed in favor of b70edd094d34055d0075c23dc4f13fb2ac396e0c


Add link to bookmark in bookmark detailed view

Similar to how you have the @username@domain on the about page, it might be useful to add in a path to the bookmark that someone can look up in order to comment
it looks like they're stored in the format: "https://{{domain}}/m/{{activity_id}}" but doing a search for that url doesn't seem to bring up the post so I'm not certain what would be needed for that

Hmm, yeah. I would expect that pasting the "/m/a-{guid}" format would work right now, so we'll have to see what we're returning there vs what Mastodon is expecting. But also we don't really expose those URLs right now, and we should make sure that the "/bookmark/{incremental id}" canonical URL redirects properly as well so that once we've fixed both halves, it comes up correctly in Mastodon.
Thanks for reporting!

it looks like they're stored in the format: "https://{{domain}}/m/{{activity_id}}" but doing a search for that url doesn't seem to bring up the post so I'm not certain what would be needed for that

Hm, I still can't search for a post in that format from mastodon.social. But I have a takahe server setup and it has no issue searching for posts setup like that


No loader is configured for ".svg" (esbuild)

Command
build
Description
Please add the ability to import .svg in .ts with esbuild.
Example of use case:
import icons from "../assets/icons/icons.svg";

export class IconModule {
  constructor(iconRegistry: MatIconRegistry, sanitizer: DomSanitizer) {
    iconRegistry.addSvgIconSetLiteral(sanitizer.bypassSecurityTrustHtml(icons))
  }
}

In this specific use case we could use addSvgIconSetLiteral and an URL but the svg won't be part of the build anymore.
When it's part of the build we can have  size stats about svg in our bundle and possibly get the .svg files hashed (cache busting), useful when you set multiple svg files inside a single svg using symbols (which angular component icon supports btw).
We could also import it directly in a template without having to create a svg component
Describe the solution you'd like
No response
Describe alternatives you've considered
As an alternative you can rename the .svg to .txt, it will be loaded using the esbuild text loader.

Can't believe new build system has been released without having the option to at least configure this.
Like custom-webpack, ...

This is working as expected since SVG is not a valid ESM Module.

This is working as expected since SVG is not a valid ESM Module.

It's not about "working as designed".
It's about missing functionality making angular competitive compared to other SPA-Framework providing.
By the way, esbuild could be configured to deal with SVG. But in the way angular is integrating esbuild, this configuration option seems to be blocked.


Release vutils-testing 2.0.3

ssia

coverage: 100.0%. remained the same
when pulling 95ce47910888214d0e29afaddb7196e34e76a282 on release-2.0.3
into 544e1db97859b73421b557567bc7622ed959d212 on main.


Fixed ordering issues and re factored code to make it easier to edit

I re-factored the code to make it easier for new users to understand. I created a TodoistConnection object which holds all functions which are needed to perform any actions on the connection.
Also:
Resolved issue #1
Resolved issue #2

Tim, sorry I never got around to reviewing this PR in a timely manner. The development branch has since diverged from the master due to the API updates, and also my own work on resolving this issue. So i'll close this PR, but thank you for taking the time to contribute!


PackageId:CPython39.Exe.x64;PackageAction:Install;ReturnCode:1603;

This issue has been moved from a ticket on Developer Community.

Sorununuzu burada açıklayın
===BU SATIRIN ALTINI DÜZENLEMEYİN===
PackageId:CPython39.Exe.x64;PackageAction:Install;ReturnCode:1603;

Original Comments
Feedback Bot on 12/11/2022, 06:40 PM:
(private comment, text removed)

Original Solutions
(no solutions)

duplicate of https://github.com/microsoft/PTVS/issues/7238


Expunge old facets: license, genres, subjects, contributors

Tidying up after https://github.com/wellcomecollection/catalogue/pull/1518 and https://github.com/wellcomecollection/wellcomecollection.org/pull/6318

Going to merge & deploy this on Tuesday 6th April


fix: incorrect output in logs when starting service

I think we need to construct the string so that when both are present we can show both of them. The revision should always be present while provided in my opinion.

Fixes #83

Close #83


Number of active days is wrong if time is set to a past date

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x] Bug is not already reported in another issue

Technical details

Device name: iPhone 6s
iOS Version: iOS 14.4 Public Beta RC 1 (could somebody who is not on a beta version please check if the behavior is the same?)
App Version: 1.10.1

Describe the bug
If you set the system time of your iPhone back (f.e. a month - but one day is also enough), CWA will show an unrealistic high number of active days.

Steps to reproduce the issue

Close CWA completetly
Open the iOS-Settings: General -> Date & Time -> Set  Automatically OFF -> Change to any date in the past
Open CWA
See unexpected long number of days

Expected behaviour
The quote "Exposure logging was active for 0 of the past 14 days." should be shown
or
(how it is done if the user's time is in the future) the "Exposure check failed" card and this pop up should be shown.
Additional context
@MikeMcC399 could you maybe check the behavior under Android?

@Ein-Tim
This is similar to https://github.com/corona-warn-app/cwa-app-android/issues/1786 where a negative number was being displayed as a large positive number.
4.294.967.268 = 0xFFFF FFE4 or -28 in DWORD
I couldn't reproduce it with CWA Android 1.10.1.
For Android there is a related PR https://github.com/corona-warn-app/cwa-app-android/pull/2019 related to "time travel" however it hasn't been merged into a released version yet.

@Ein-Tim
This is similar to https://github.com/corona-warn-app/cwa-app-android/issues/1786 where a negative number was being displayed as a large positive number.
4.294.967.268 = 0xFFFF FFE4 or -28 in DWORD
I couldn't reproduce it with CWA Android 1.10.1.
For Android there is a related PR https://github.com/corona-warn-app/cwa-app-android/pull/2019 related to "time travel" however it hasn't been merged into a released version yet.

Okay thanks @MikeMcC399.
I know about the Android Issue, and since this was a bug in Googles ENS, I fear that this is the same bug but for Apples ENF.
I will leave this Issue here since you could not reproduce it and according to @dsarkar in https://github.com/corona-warn-app/cwa-app-android/issues/1786 this should be fixed in version 1.8.

Okay thanks @MikeMcC399.
I know about the Android Issue, and since this was a bug in Googles ENS, I fear that this is the same bug but for Apples ENF.
I will leave this Issue here since you could not reproduce it and according to @dsarkar in https://github.com/corona-warn-app/cwa-app-android/issues/1786 this should be fixed in version 1.8.

@Ein-Tim I can reproduce this on iOS 14.3.

@Ein-Tim I can reproduce this on iOS 14.3.

Any updates will be reported here.
Internal Tracking ID: EXPOSUREAPP-4755

Any updates will be reported here.
Internal Tracking ID: EXPOSUREAPP-4755

@MikeMcC399 Thanks for your comments, which have been added to the ticket as additional remarks.

@MikeMcC399 Thanks for your comments, which have been added to the ticket as additional remarks.

@Ein-Tim
CWA 1.11 / iOS 14.4 / iPhone6s -  I set date to 1.12.2020 and I get this:

@Ein-Tim
CWA 1.11 / iOS 14.4 / iPhone6s -  I set date to 1.12.2020 and I get this:

Yes, looks definitely better than before.
I have different behaviors, either the screen that you have is shown or the quote "Exposure logging was active for 0 of the past 14 days."
will close this now

Yes, looks definitely better than before.
I have different behaviors, either the screen that you have is shown or the quote "Exposure logging was active for 0 of the past 14 days."
will close this now

@Ein-Tim Thanks!

@Ein-Tim Thanks!


Multi-count expectations on any instance of a class

Subject of the issue
I am using the following pattern:

    expect_any_instance_of(C).to receive(:meth).exactly(3).times.and_call_original

It seems that all 3 invocations are required by rspec-mocks to happen on the same instance of C, where in my application there are 3 instances of C and each gets meth invoked on it once.

class C
  def meth
  end
end

describe 'Foo' do
  it 'calls C.meth three times' do
    expect_any_instance_of(C).to receive(:meth).exactly(3).times.and_call_original

    C.new.meth
    C.new.meth
    C.new.meth
  end
end

Result:

Failures:

  1) Foo calls C.meth three times
     Failure/Error: C.new.meth
       The message 'meth' was received by # but has already been received by #
     # ./spec/foo_spec.rb:13:in `block (2 levels) in '

How can I assert that the method is invoked 3 times, either with or without asserting the distinctiveness of instances of C on which it is invoked?

Your environment

Ruby version: 2.5.1
rspec-mocks version: 3.8.0

Steps to reproduce
Repro: https://github.com/p-mongo/tests/tree/master/rspec-multi-instance-expectations

Expected behavior

I should be able to assert that the method is called the required number of times even if invocations are on different class instances.
Note that using allow_any_instance_of instead of expect_any_instance_of does pass, and I can pass a block to it to do my own counting, however I don't know how to invoke the original method from the block and specifying and_call_original makes my block not get called:

WARNING: You're overriding a previous stub implementation of `scan!`. Called from /home/w/apps/ruby-driver/lib/mongo/server/monitor.rb:130:in `block (2 levels) in run!'.. Called from /home/w/apps/ruby-driver/lib/mongo/server/monitor.rb:130:in `block (2 levels) in run!'.

(message from the actual ruby driver project)
Actual behavior

I am not able to enforce that my method is called a specific number of times while also calling the original implementation of the method.

Sure it is:
e.g.

instances = (1..3).to_a.map do
  klass.new.tap do |instance|
    expect(instance).to receive(:msg).once
  end
end
expect(klass).to receive(:new).extactly(3).times.and_return { instances.shift }

Theres nothing that prevents you from returning a real instance in a stub, you can even use and_call_original to provide real behaviour, the important thing is you control whats happening, in order to be unambigious.

I see, I confused instance_double with double. However, the class in question's initialize looks like this:
https://github.com/mongodb/mongo-ruby-driver/blob/master/lib/mongo/server/monitor.rb#L58
... and is invoked by Server's constructor which builds those needed objects. Hence it is still not at all clear to me how to make this all work.
In this case, any instance expectations are exactly what I want. There is a complex process that results in an object hierarchy being constructed, and it is convenient to assert that a certain method is called (or not called) in addition to other assertions verifying user-visible behavior.

The second code snippet I require will allow 3 instances to receive msg once, if you need a random 3 instances from a much greater set thats trickier, but can still be achieved:
instances_allocated = []
n = 0
expect(klass).to receive(:new).and_wrap_original do |o, *args
  instance = o.call(*args)
  instances_allocated << instance
  allow(instance).to receive(:msg).and_wrap_original do |m, *args|
    n += 1
    m.call(*args)
  end
end
expect(n).to eq 3

This is more complicated of course, but so is what you're trying to do, it's still a lot simpler than the existing any instance functionality, and a lot simpler than our implementation trying to do either behaviour would be.

I am not sure what you mean by "existing any instance functionality", but I had this written (which doesn't work):

        expect_any_instance_of(Mongo::Server::Monitor).to receive(:scan!).
          exactly(SpecConfig.instance.addresses.length).times.and_call_original

I am not claiming this is easy to implement in rspec-mocks but isn't the job of a mocking library to implement functionality like this so that the application does not need to?

A possible solution API-wise is to keep expect_any_instance_of as it is and add a plural version which will allow different instances to receive the calls:

        expect_any_instances_of(Mongo::Server::Monitor).to receive(:scan!).
          exactly(SpecConfig.instance.addresses.length).times.and_call_original

It will work, provided you don't mean multiple instances

Is there a discussion one can read somewhere about ceasing development of any instance functionality? I am curious how this decision was reached.

Not exactly what you asked for (I'm not sure we have a canonical source for discussion), but some context here: https://relishapp.com/rspec/rspec-mocks/docs/working-with-legacy-code/any-instance

The relevant paragraph from those docs:

This feature is sometimes useful when working with legacy code, though in general we
discourage its use for a number of reasons:

The rspec-mocks API is designed for individual object instances, but this feature operates on entire classes of objects. As a result there are some semantically confusing edge cases. For example, in expect_any_instance_of(Widget).to receive(:name).twice it isn't clear whether a specific instance is expected to receive name twice, or if two receives total are expected. (It's the former.)
Using this feature is often a design smell. It may be that your test is trying to do too much or that the object under test is too complex.
It is the most complicated feature of rspec-mocks, and has historically received the most bug reports. (None of the core team actively use it, which doesn't help.)

The consensus amongst the team was that it wasn't worth expanding the feature set either, for those same reasons.

Thanks for finding those docs @xaviershay I'd totally forgotten we'd written this behaviour up!

is that a typo? shouldn't extactly be exactly instead?


Use ncc compile source file as a single file

Use @zeit/ncc compile source file as a single file.
This can make git repo clean.

I don't think we want this - IMO this actually makes it less clear what is going on in the repo. I think the real solution here is to move to the workflow described here, where node_modules are only included on release branches

Why this make less clear ? This solution can ignore node_modules even in release repo. Do you think current the current compiled lib still readable or more clear than this ?

I think the current lib is more readable. It maintains the separation of concerns of different files, and maps to the TypeScript well. This is important so that a reviewer can verify that changes to the TS files match changes in the JS files.

The compiled files in other static languages such like golang mean the binary file. Does a reviewer need review the binary file changes?


How do I exclude files with a pattern?

Summary
How do I exclude files with a pattern? I want to run stryker against a Xamarin .netstandard 2.0 library, I'm using stryker with in the console with the following command:
dotnet stryker -cp stryker-config.json
In the config file I'm specifying files to be excluded but it seems to only allow specific file names rather than using a pattern to exclude them. I've tried a few different ways of specifying a pattern, see the config file below.
Stryker config

  "stryker-config": {
    "files-to-exclude": [
      "pattern": "/Views/*",
      "pattern": "**/*.xaml.cs",
      "pattern": "**/*.xaml",
      "/**.xaml.cs",
      "/**.xaml",
      {
        pattern: "**/*.xaml.cs"
      }
      {
        pattern: "**/*.xaml"
      }
    ]
  }
}

Test runner
xUnit

Environment
Windows 10
.NET Command Line Tools (2.2.203)

Thanks for opening this issue! I believe this is related to Stryker.NET which is located here: https://github.com/stryker-mutator/stryker-net
I took the liberty of opening an issue for you there: https://github.com/stryker-mutator/stryker-net/issues/464
For now I'll close this issue.


[FUZZ] OOM in lodestar_enr

I've identified a fuzzer crash and am contributing to the security of Ethereum 2!
I've done and provided the following:

[x] Checked to see if any other [FUZZ] issue already refers to that crasher
[x] Attached the crashing input (either attached to the issue as a .zip or .gz, or as a link to a file sharing service)
[x] Noted the beacon-fuzz version or commit used.
[x] Provided crash output
[x] Noted the command or fuzzer used to generate the crash
[x] Name of the original crash file
[ ] (Optional but optimal) Checked if the crash can be consistently replicated by re-running the input.

Info to Reproduce

Command run: e.g. make fuzz-all
Crasher file name: crash-333c4abf56a03bb10a790ecf860a8dd41557849c8c635bf1e66d9f2c8a80f3d6
crash-333c4abf56a03bb10a790ecf860a8dd41557849c8c635bf1e66d9f2c8a80f3d6.zip
Client exercised: lodestar
Fuzzing engine used (if applicable): jsfuzz

Crash output and stacktrace
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 24 rss: 159.9 MB
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 0 rss: 412.4 MB
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 0 rss: 663.46 MB
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 0 rss: 965.88 MB
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 0 rss: 1050.84 MB
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 0 rss: 1356.09 MB
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 0 rss: 1562.6 MB
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 0 rss: 1775.48 MB
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 0 rss: 2004.07 MB
#22477 PULSE     cov: 6738 corp: 3562 exec/s: 0 rss: 2005.75 MB
MEMORY OOM: exceeded 2048 MB.
Nevertheless I prefer to keep this issue open until it is fixed.


[Feature] Support the InjectedIdentity credential source in terraform-controller

Support the InjectedIdentity credential source in terraform-controller, to enable use workload identity like IRSA -  iam-roles for service accounts on AWS and Workload Identity on Google Cloud.
Part of this implementation has been done by crossplane-runtime -
https://github.com/oam-dev/terraform-controller/blob/3b4fde8230fb1bf4c840e6b9691e37a291367731/api/types/crossplane-runtime/resource.go#L36
The CRD providers.terraform.core.oam.dev already support this - https://github.com/oam-dev/terraform-controller/blob/d89c4c2507e99add0afcfac6eb3539c0f88fc86b/config/crd/bases/terraform.core.oam.dev_providers.yaml#L62

Related to https://github.com/oam-dev/kubevela/issues/3677.


[WIP] [#118] add a new view for job + log data

WIP
This PR is an alternative way of structuring Kashti's user flow; changing the app to open each job (and its log content) individually. After discussion with @seanknox  on how to move #176 forward, I think this approach makes the most sense:

ui flow better matches the brigade-api structure
bypasses the blocker from #176; that individual jobIds are hard to fetch at the build level
build pages show summaries, rather than full job logs
each job now has a distinct, sharable urls

preview screenshot of changes to flow:

If this method is to used, a couple of small additions required:

[ ] breadcrumb links/states need tidying up
[ ] some logic needed to link back from a Job to a Build
(currently a Job does not know it's parent)

Closes #176, #118.

One thing noticeable in the jobs / logs view is how the part of the job / build name gets hidden while you scroll behind the main component - see below.

Changes incorporated into this PR will close #87 #113 #118 #159 #165.


Zipkin json encoding via HTTP

Fixes https://github.com/uber/jaeger/issues/225
Zipkin API definition: https://github.com/openzipkin/zipkin-api/blob/master/zipkin-api.yaml
Docker Image to try it: https://hub.docker.com/r/pavolloffay/tmp-jaeger-zipkin-json/

Coverage remained the same at 100.0% when pulling a152d1d0c8423d47e8722001a506970e4ee87f6b on pavolloffay:zipkin-json into db9f152d4238f7fc60fd52121cda5a461ce7aa6c on uber:master.

How are we going to write integration tests for this? zipkin-go-opentracing supports only thrift. We could use brave but it's in java.  I think we have two options:

modify xdock-java to use brave
crate new xdock-zipkin which would verify zipkin related stuff.

How are we going to write integration tests for this?

I think we might be able to use the same xdock driver, but a different "client" that's implemented with Zipkin's JSON and Thrift official senders (two clients, really)
@black-adder - can we come up with a unified end-to-end testing framework? Ultimately it boils down to two parts

running some configuration of the backend (could be all-in-one, or docker-compose, or k8s)
having the driver his some sort of client that can report spans to the backend (either via agent or via direct POST)

Coverage remained the same at 100.0% when pulling 990f4993173f22a5d59a5d43ec78a1e7fc31438c on pavolloffay:zipkin-json into 79fba1278743840dff6b84aa059ec58f7ec21a0a on uber:master.

Coverage remained the same at 100.0% when pulling 6a839682c017da3cedd3e13d89411afcd5850521 on pavolloffay:zipkin-json into 79fba1278743840dff6b84aa059ec58f7ec21a0a on uber:master.

running some configuration of the backend (could be all-in-one, or docker-compose, or k8s)
having the driver hit some sort of client that can report spans to the backend (either via agent or via direct POST)

This can be easily done with in the all-in-one integration test, however doing it via crossdock tests does seem more semantically correct. The all-in-one integration test is supposed to be a simple test that ensures the pipeline works, I don't want to conflate the test with zipkin testing logic.
Creating a test zipkin client which sends http and thrift spans to the collectors and making this run with the xdock tests seems the best approach. But I'm not entirely sure how to get this to work without creating another docker image just for the zipkin client, I'll have to experiment a bit.

btw, their new format with Go: https://github.com/openzipkin/zipkin-api-example/tree/master/go

Coverage remained the same at 100.0% when pulling 2ada3b2034ad390e29a9f7813a9612df1ff89cd0 on pavolloffay:zipkin-json into 9bfab15c69d7a8097ba9fe256253b5016053ed25 on uber:master.

Coverage remained the same at 100.0% when pulling eafd168df7a53fc7481f1eba4e0e3e0551b6e719 on pavolloffay:zipkin-json into 9bfab15c69d7a8097ba9fe256253b5016053ed25 on uber:master.

Coverage remained the same at 100.0% when pulling 1879f5e5a0c3f57d569c8e84658a378ead67f9c2 on pavolloffay:zipkin-json into 9bfab15c69d7a8097ba9fe256253b5016053ed25 on uber:master.

Coverage remained the same at 100.0% when pulling cce519b723a41b0598d65bd9deadce63e9b6e154 on pavolloffay:zipkin-json into 5e5a361babba385bd0b9868bace1e10c75fc0829 on uber:master.

Coverage remained the same at 100.0% when pulling 26031655c4b552700f5da7c3bbe4433cb7cebb36 on pavolloffay:zipkin-json into 5e5a361babba385bd0b9868bace1e10c75fc0829 on uber:master.

Coverage remained the same at 100.0% when pulling 64499c289e8cea96cb3c992be1442b9b4e60ca73 on pavolloffay:zipkin-json into 5e5a361babba385bd0b9868bace1e10c75fc0829 on uber:master.

Coverage remained the same at 100.0% when pulling 2b406ae846510f87bf699ec1eb48b6aff8df7ab9 on pavolloffay:zipkin-json into 5e5a361babba385bd0b9868bace1e10c75fc0829 on uber:master.

This is updated and should be ready for re-review.

Coverage remained the same at 100.0% when pulling 3211e3dafb258f5b5e43529e46426cac48c78fb7 on pavolloffay:zipkin-json into 5e5a361babba385bd0b9868bace1e10c75fc0829 on uber:master.

@yurishkuro I am on PTO until 28th. I don't want to block other people.. If there are no serious blockers I can submit fix PR to address latest comments:

IP parsing
reuse functions from model to handle 128 bit trace ids
minor improvements in http handler

Once this is in #342 could be merged (if it's ok).


fix(ipfs-coord): Updating bootstrap peers. v6.6.8

:tada: This PR is included in version 1.9.1 :tada:
Your semantic-release bot :package::rocket:


[operator] Expose kube-apiserver via Istio

How to categorize this PR?

/area scalability
/kind enhancement
What this PR does / why we need it:
This PR creates the necessary SNI component in order to expose the virtual-garden-kube-apiserver via the available Istio-Ingress gateway.
Which issue(s) this PR fixes:
Part of #7016
Release note:

`gardener-operator` configures SNI components in order to expose the `virtual-garden-kube-apiserver` via the `istio-ingressgateway` in the Garden cluster.
With this change, operators can start to switch DNS records from the `virtual-garden-kube-apiserver` service to the `istio-ingress` service endpoint. The type of the `virtual-garden-kube-apiserver` service will soon be switched from `LoadBalancer` to `ClusterIP`.

/assign

/test pull-gardener-integration

/test pull-gardener-e2e-kind

/milestone v1.72


Popular links for programming books

Thanks for your contribution! Would you mind adding these links to the existing files instead of creating a new file?


Fix newest additions to keepnick module and write the test for it.

Fix the documentation.
See #1324 and #1325
@Zarthus

that's better, thanks! I agree an enumeration of params is better than rather than statically explaining which one is which with ambiguous words like "maybe contains this".
The keepnick getparam() worked for me when I tested it on freenode, I will check if this is still the case with your fix.


Added Kevins resolution to fix undefined sortFields in discovery context

Resolved the undefined value for sortFields in DiscoveryContext Controller.

Coverage increased (+0.004%) to 45.653% when pulling cfeddaa7c2038bda868848860712c818eba01747 on DAME-Aug-Sept-sprint-undefined-sortField-fix into 27d1080b4e4f920bc1e99007f71128b12725e36b on DAME-Aug-Sept-sprint-staging.


Remove symlink that breaks release deployment

Fix errors that prevent 1.0.0 from being consumed

Ignoring the TravisCI build for now.


Create a READ ONLY role on Publishing API database

The intention of this role is to allow the creation of a user that will be assigned this role, with the sole purpose of being used in Finding Things Migration Checker
Please let me know what I missed, I'm not used to Puppet at all, thank you.
For more information please read here

I think this should be named something other than govuk::apps::publishing_api::postgresql_role, otherwise it could be confused with the more generic govuk_postgresql module that sets up the user publishing api uses.
Maybe something like govuk::apps::finding_things_migration_checker::publishing_api_role?
You probably also need to set up hieradata to override $db per environment.

There are a few other things you'll need to add to make this work - perhaps not everything in the existing bouncer role but much of it, and also a pg_hba.conf rule to allow this role to authenticate. I'm happy to talk through those examples with you to explain why each part is needed - I regret now not writing a fuller commit message when I added it originally.


Move package-dependencies related code to separate SpeziLicense package

Move package-dependencies related code to separate SpeziLicense package
:recycle: Current situation & Problem
As described in issue #42 the current TemplateApplication features a view that shows all used packages of the project. This requires one to manually set-up or copy code around when implementing this feature in a new app.
:gear: Release Notes

Upgrade the swift-package-list dependency to newer version 4 (previously 3)
Move all code that related to showing the package list view in the TemplateApplication into this new SpeziLicense package

:books: Documentation

Documentation same as the code in the TemplateApplication

:white_check_mark: Testing

Slightly adjust tests compared to the existing ones in the TemplateApplication, now also UI testing if the SpeziViews is in the ContributionsView (using the SpeziViews package in the TestApp)

:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

@PSchmiedmayer Hope everything is resolved now :) Also thought about refactoring the LicenseType struct as we now also have the public License interface and merge them together somehow.
Could also be something for the future tho - What do you think?


Fix setup-java step of blossom-ci [skip ci]

Signed-off-by: Peixin Li<EMAIL_ADDRESS>to fix the java versions with in the V3 setup-java action

NOTE: This is also relying on corresponding internal blossom-ci integrity check update
Going to force merge this one to unblock premerge CI. I will update status later


New icons in production environments

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

SPFx version 1.14.1, 1.15

Describe the bug / error
It seems that SharePoint is changing its icons from Fluent UI to segoe-fluent-icons-font overnight, or maybe I missed the announcement?
Our product uses SPFx and has been using icons from Fluent UI in production environments for a while now and suddenly these icons have changed. We are having many complaints from clients as this was unexpected. We didn't have the time to test the new icons and of course, there are many problems like StockDown and StockUp which seem to be the other way around. We use them in production environments to indicate the direction of the stock so imagine how confusing and frustrating this is.

Steps to reproduce
Go to https://docs.microsoft.com/en-us/windows/apps/design/style/segoe-fluent-icons-font and find StockDown and StockUp

[ ]

Expected behavior
StockDown should point down
StockUp should point up
We expect more information on changes that are drastically changing the look and feel of SharePoint.

This requires higher attention, our users are frustrated as well (we have same use case for these 2 icons).
We observed that on SPFx webpart instantiated on classic site collections we have old (correct) icons.
Seems like redesign happened on modern sites only, it is not visible on Fluent UI Icons page either.
Do we have any control on which version of icons is used in our SPFx components?
A side note: we see our users focusing too much on 'Group' icon (based on comments they perceive it as below, it seems frustrating and annoying for most, on the left previous version):

This may break the principle that interface elements should not receive more attention than is necessary for functional purposes.

@Rafaelki - thank you for reporting this one.
It is definitely messed up on our side of the house.
We will be updating the font to fix that issue.
I would expect hotfix in the next couple of days.

Thank you very much @AJIXuMuK
Is there an estimated date we can tell our clients? My team needs to evaluate if it is worth creating a patch in our product (the share prices have high visibility in our product - it is in an app customizer at the top)

@Rafaelki - the fix is merged and usually it takes around 2 weeks to roll out WW.

Thank you @AJIXuMuK I can see the correct icons in my dev environment now and hopefully very soon in our client environments. Closing the issue.


[Discussion: Timers] Background execution and ordering semantics

I wanted to start a discussion about the timers and an API that exposes the capabilities of the system timers. A couple of things I noticed were that the timers use CADisplayLink on the main thread and also listen to the UIApplication state notifications. To my knowledge this works well for timers that are coupled to the UI (requestAnimationFrame comes to mind, there may be other uses). I'd like to discuss timers that do other work e.g. interact with the event loop or schedule background tasks, and how they co-interact.
Event loop timers seem to fall into two categories - those that run at the end of the current loop and those that run right after. This is like process.nextTick and setImmediate. These aren't too hard to implement though there are a couple of gotchas like warning if a process.nextTick handler endlessly schedules itself before blowing the stack. I would also expect both of these timers to run even if the app is inactive or backgrounded (e.g. say you get a network response while the app is backgrounded and schedule some work to run soon after - it should run in the background).
Background task timers (setTimeout, setInterval) raise a couple of questions like the semantics of a zero-ms timeout. I would also propose that these run in the background as well to address the use of running code that does not need the app to be foregrounded. And, if the app is backgrounded there is little harm in running UI code anyway -- in cases where it does matter, the timer handler can check the UIApplication state.
Background task timers that repeat are also good candidates for energy optimization. One thing that OS X systems do is coalesce timers where possible, partly aided by the programmer providing a tolerance value. If many running apps schedule timers that can overlap within their respective tolerance windows, the system may wake the CPU just once to run all of those tasks together.
There is also a question of the ordering of all of these timers. My strawman proposal is:

End of event loop: nextTick
ASAP after end of prior event loop: setImmediate, followed by setTimeout(0)
A short while later (using NSTimer): setTimeout(n + [0-tolerance]) up until the next frame begins
Start of next frame (CADisplayLink): requestAnimationFrame. However, this will wait till later if the app is foregrounded or inactive. Also I believe CADisplayLink may not fire if momentum scrolling is active (not verified).
Some time later (again using NSTimer): setTimeout(n + [0-tolerance]) where n is big enough that a frame has elapsed

Additionally, setTimeout(delay = 9, threshold = 2) should run before setTimeout(delay = 10, threshold = 0), and two setTimeouts with the same delay should run in the order that they were scheduled even if they have different thresholds. But to keep things simple at first I would recommend we go with whatever the system timer (NSTimer) does. There's an argument to be made that the timer handlers should use promises or semaphores, etc if they need to coordinate and not rely on the timer system.

@sahrens @ide
Any updates here?

I haven't had a need for this yet but sense that a more comprehensive timer API is going to be necessary once apps act as background services that need to do scheduling.

@jordwalke, I know you've been thinking about these problems, want to make sure you've seen this

@ide have you seen requestIdleFrame? That's a great way to use remaining frame time to do cleanup work that shouldn't block the UI - it should also tell you how much frame time remains.
BTW: Our JS timers should be fired from a display link on the JS thread. The only reason why they're not, is because I didn't know you could run display links from a non-Main thread! It would clean up so much complexity if every frame, on the JS thread, it just called into JS and asked "so, do you have any timers ready"? Feel free to send a PR, I know that @tadeuzagallo has been working towards this but hasn't gotten to actually moving the timers to the JS thread.

@jordwalke requestIdleCallback is implemented, I just haven't landed because there were no use-cases so far, but I can do.
As for timers, our timers do run on the JS thread, for quite a while now, they are not implemented in JS though. TBC, everything runs based on a CADisplayLink on the JS thread, the only thing the displayLink on the main does right now is put VSync markers and count FPS.

Any update on background timers? I'm working on a fleet tracking app, and if I can't track GPS or fetch data in the background I'm going to have to abandon react-native.

@danielsandrewm no updates from my side. In the past when I've needed background tasks I wrote that code in Obj-C and then called into it from RN.

@danielsandrewm , yes the runloop currently is suspended by the OS when the application is backgrounded.  I wrote my background tasks in ObjC, like @ide did, which will fire an update event with state information when the application was brought o the foreground.
The reality is that React Native doesn't entirely replace all classes of native applications.

Moving this to ProductPains @ide - https://productpains.com/post/react-native/background-timer-execution/
I really want to see this but I think it'll have to be something that the community builds, in the short term at least.

@brentvatne @ide Could either of you give code example or perhaps implement the fix for Pomodoro app to make it work 100% proper?

@andrews is also thinking about timers and event ordering. We have some ideas floating around for hi-pri event precedence, and maybe even changing the JS runloop model to poll native rather than native always calling into it, which could give us more flexibility to do re-ordering and other queue processing in JS, and is probably more performant than calling in from native on every event like we are doing now.

On Mar 10, 2016, at 5:04 PM, niftylettuce<EMAIL_ADDRESS>wrote:
@brentvatne @ide Could either of you give code example or perhaps implement the fix for Pomodoro app to make it work 100% proper?
—
Reply to this email directly or view it on GitHub.

Would it be possible to write a Swift module that runs whatever JavaScript it receives in a separate JavaScriptCore thread? Basically just a module that runs a separate thread in the background?

@ide So what is the ultimate way for iOS?
I am really clueless, bcs iOS does not allow this timer to work when the app goes in background. I need to track GPS with some other important data every 5 minutes. As of now, I collect the data every 5 minutes in local async data and then push it to the server every 15 minutes. But on iOS, when the app goes background (Even screen is on or off), its no running this timer thread.
Now, what could be the options here?

My App is not musical app, and also the usecase does not have changing GPS every momeny most of the time.
Thinking of using heartbeat based tracking - https://github.com/transistorsoft/react-native-background-geolocation - This seems to work in iOS as per the issues and docs.
Any other way, like Android's IntentService or BroadcastReceiver.

@danielsandrewm no updates from my side. In the past when I've needed background tasks I wrote that code in Obj-C and then called into it from RN.


Docker ingestion not working

docker.errors.APIError: 400 Client Error for http+docker://localhost/v1.41/containers/create: Bad Request ("invalid mount config for type "bind": bind source path does not exist: /tmp/openmetadata/examples/")
[2022-01-18, 10:17:24 UTC] {taskinstance.py:1270} INFO - Marking task as FAILED. dag_id=sample_data, task_id=ingest_using_docker, execution_date=20220117T101639, start_date=20220118T101724, end_date=20220118T101724
[2022-01-18, 10:17:24 UTC] {standard_task_runner.py:88} ERROR - Failed to execute job 10 for task ingest_using_docker
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/docker/api/client.py", line 268, in _raise_for_status
response.raise_for_status()
File "/usr/local/lib/python3.9/site-packages/requests/models.py", line 953, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http+docker://localhost/v1.41/containers/create

To simplify the sample data workflow I'll revert the DockerOperator changes on the example DAG and just use the usual workflow approach.
I have it pending to work on the DockerOperator docs for the ingestions so I can have some examples there, sorry for the noise!

@akash-jain-10 what was the command again that produces this error?


Feat/appeal model dto

add appeal model and dto

Solve conflict, please kindly accept PR

why is this PR only have the migration changes?

It because the create appeal PR which include the model and dto already merged, should I drop this PR?

It because the create appeal PR which include the model and dto already merged, should I drop this PR?

So, this migration should have been included in the previously merged PR?
Ok, I'll approve this and you can merge it afterwards.  Make sure to include db migrations version in the same PR of your code changes in the next PRs.


Be more precise about what six.class_types

Avoids the need for users to look this up by experimentation or code inspection.

Added the intersphinx link.


Add EMF UPD TCP Logs CA Bundle Tests

Description of the issue
emf upd/tcp has no ca bundle tests
Description of changes
Add tests for emf udp/tcp ca bundle
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Integration test

Does https://github.com/aws/amazon-cloudwatch-agent-test/pull/321 need to be closed?


Moved: Add Liquid State Machine (LSM) from Synaptic

This suggestion has been moved from Neataptic.
https://github.com/wagenaartje/neataptic/issues/76

I'd love to see the Liquid State Machine implemented in Neataptic.
I noticed there was a similar functionality in the Random network but it's not really a Liquid network.
( Great paper on LSM from Utrecht University, http://www.ai.rug.nl/~mwiering/thesis_kok.pdf, see page 18)

Looks like Synaptic has done the hard work with this one show it should be easy to port over.
https://github.com/cazala/synaptic/wiki/Architect
Code:
https://github.com/cazala/synaptic/blob/master/src/architectures/Liquid.js


Code quality fix - Try-with-resources should be used.

This pull request is focused on resolving occurrences of Sonar rule
squid:S2093 -  Try-with-resources should be used.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S2093
Please let me know if you have any questions.
Faisal Hameed

Hi,
This looks good to me, thanks!


Add HTTP::Client logging and basic instrumentation

This adds protected methods HTTP::Client#before_exec and #after_exec that can be used to hook into the lifecycle of the http client.
A first utility for this is adding a http.client log source to know a request is starting.
This enables some basic instrumentation to monitor the activity of the application without monkey patching sensitive parts of the http client.

As an example if one wants to log also when a request is completed and measure the elapsed time the app could define
class HTTP::Client
  protected def before_exec(request)
    previous_def
    @start = Time.monotonic
  end

  protected def after_exec(request)
    previous_def
    elapsed = Time.monotonic - @start.not_nil!
    Log.debug &.emit("Finished request",
      method: request.method,
      host: host,
      port: port,
      resource: request.resource,
      elapsed: "#{elapsed.total_seconds.humanize(precision: 2, significant: false)}s"
    )
  end
end

I think it's simpler to do something like around_request. That way for measuring time you don't need to add an instance variable.

Also, using previous_def seems like a smell to me, but maybe it's the most efficient way to do something like AOP or event callbacks without having to add to a list, keep that list in memory, iterate it and call each processor, etc. So maybe it's fine.

around_exec can also work, I found before/after simpler.
Would it be better to have only around? or around + before + after?

Something like this: (I'm surprised it works with just yield, which is nice)
class Foo
  def foo
    around_foo do
      1
    end
  end

  protected def around_foo
    yield
  end

  macro def_around_foo
    protected def around_foo
      previous_def do
        {{yield}}
      end
    end
  end
end

class Foo
  def_around_foo do
    time = Time.local
    value = yield
    puts Time.local - time
    value
  end
end

p 1
Foo.new.foo
p 2

Also with a macro it's simpler, the internal protected name doesn't matter anymore, and the way hooks are defined could be changed later on if needed. And the macro can be documented.

I think it's simpler to have just around. In fact, this is already pretty much https://github.com/crystal-lang/crystal/issues/6011 which begs for handlers, similar to how you can add handlers to an http client.
In this way, you could create an http client, enable logging, or introduce a proxy, whatever, without affecting other clients. So instead of just adding logging I would try to focus on the general solution (if there's time, and someone wants to do it).

The around macro has as a drawback that the block argument is an ast node and hence it must be {{-ed.
The example to measure the elapsed time can be done in either way after the last commit
class HTTP::Client
  def_around_exec do |request|
    start = Time.monotonic
    begin
      yield
    ensure
      elapsed = Time.monotonic - start.not_nil!

      Log.debug &.emit("Finished request",
        method: {{request}}.method,
        host: host,
        port: port,
        resource: {{request}}.resource,
        elapsed: "#{elapsed.total_seconds.humanize(precision: 2, significant: false)}s"
      )
    end
  end
end

or
class HTTP::Client
  def_around_exec do |request|
    start = Time.monotonic
    res = yield
    elapsed = Time.monotonic - start

    Log.debug &.emit("Finished request",
      method: {{request}}.method,
      host: host,
      port: port,
      resource: {{request}}.resource,
      elapsed: "#{elapsed.total_seconds.humanize(precision: 2, significant: false)}s"
    )
    res
  end
end

The other alternative is to move the around method to HTTP::Request instead of the client.

Yeah, I agree it's ugly. Another alternative is to continue using around but not using a macro for it.
Also, how do I try this out? I can't setup logging...

@asterite by default only info severity is advertised. You can do
Log.setup_from_env

HTTP::Client.get("https://google.com")
HTTP::Client.get("http://example.org") do |resp|
end

$ LOG_LEVEL=DEBUG bin/crystal foo.cr

It's possible to do it like this:
  macro def_around_exec(&block)
    protected def around_exec(%request)
      previous_def do
        {% if block.args.size > 1 %}
          {% raise "wrong number of block arguments (given #{block.args.size}, expected: 1)" %}
        {% end %}

        {{ block.args.first.id }} = %request
        {{block.body}}
      end
    end
  end

Then you can use whatever name you want in the block.

I have this, I'm not seeing any logs in stdout:
require "http/client"

class HTTP::Client
  def_around_exec do |request|
    start = Time.monotonic
    value = yield request
    elapsed = Time.monotonic - start.not_nil!
    Log.error &.emit("Finished request",
      method: request.method,
      host: host,
      port: port,
      resource: request.resource,
      elapsed: "#{elapsed.total_seconds.humanize(precision: 2, significant: false)}s"
    )
    value
  end
end

Log.setup_from_env

HTTP::Client.get("https://www.example.com").to_io(STDOUT)

@asterite it's example.org not example.com. $ curl -v https://www.example.com never ends for me.
I sent that patch. It can work that way I think 👍

example.com works for me
I changed it to example.org but I can't see any logging in stdout

Rebased on master. Ready for review.

The final state of this PR is
This adds the macro HTTP::Client.def_around_exec that can be used to hook into the lifecycle of the http client.
A first utility for this is adding a http.client log source to know a request is starting.
This enables some basic instrumentation to monitor the activity of the application without monkey patching sensitive parts of the http client.

As an example if one wants to log also when a request is completed and measure the elapsed time the app could define
class HTTP::Client
  def_around_exec do |request|
    start = Time.monotonic

    res = yield

    elapsed = Time.monotonic - start
    Log.debug &.emit("Finished request",
      method: request.method,
      host: host,
      port: port,
      resource: request.resource,
      elapsed: "#{elapsed.total_seconds.humanize(precision: 2, significant: false)}s"
    )

    res
  end
end


Make sure all packages are updated in the base image

Addresses https://github.com/CybercentreCanada/assemblyline-base/issues/947


panResponder inside ScrollView

Description
I've got horizontal ScrollView with some thumbnails. I defined panResponder to my thumbnails in order to drag them on the screen. The problem is that I can't drag them outside the ScrollView - the thumbnail is become hidden when my finger is exceeds the borders of the ScrollView.
There is a way to make this work?
Additional Information

React Native version: 0.35
Platform: both
Operating System: MacOS

Maybe you can add a invisible thumbnails out of scrollview.
when you start to drag thumbnails in scorllview, you just need to set the outside thumbanail visible and move it!
hope it can do the effect as you want.

@ronzilca Any updates?

@christopherdro Unfortunately no, for my knowledge you can make it work on iOS but not on Android..

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


Enhancement: url creation from component array, method createFromArray

Fix: typos
Fix: exception type, code vs phpdoc mismatch
?: change scheme validation regex to RFC compliant

Hi @mleko Thanks for the PR. But I'm in the middle of reviewing the v4 of league/uri which already contains the modifications your are submitting for v3.
TBH, the v3 branch is on security fix maintenance right now and will be EOL as soon as the v4 will be out.
What I could suggest you is to look at the v4 code on league.uri and read the documentation to see if there's something else you would like to see added.


MainController: Neovim exited with code: 1

I installed the plug in VScode and setup following the guidance (win32). However, the warning "MainController: Neovim exited with code: 1" and the Neovim plugin shut down. showed when I restart VScode. How can I fix this? Thanks!!

same


Version 0.5.0 release

Version 0.5.0 release. Besides bumping the version this PR also includes the following changes:

Separate the ansible-lint license.
Update changelog to include all changes for v0.5.0.
Remove duplicate documentation (code of conduct).
Add already existing documentation to the Sphinx documentation.
Add additional badges to the README.md.
Simplify and update the GitHub Workflow to release to PyPi.
Updated the version_added in all new rules.

Note: before the actual release the GitHub secretes for PyPi will need to be updated!

I've just updated to GitHub actions secrets to include the new PyPi tokens.

I've just updated to GitHub actions secrets to include the new PyPi tokens.


docs: ADR for format and lint tooling

- What I did
We have some inconsistencies with our formatting and linting policies mainly occurring in less used file formats like markdown and yaml. This ADR is opened as a discussion for us to address that.
- How I did it
- How to verify it
- Description for the changelog
docs: ADR for format and lint tooling

@cpswan I pushed what should be the least cumbersome approach to linting (that plays nice with formatters) that I could come up with in efe018f
opened an issue related to this weird behaviour as well: https://github.com/jackdewinter/pymarkdown/issues/1208


feat: allow picking from easy access methods

Description
Allow picking directly from component or body... this requires modifications in visualization tool.
Issue linked
Closes #1498
Checklist

[ ] I have tested my changes locally.
[ ] I have added necessary documentation or updated existing documentation.
[x] I have followed the coding style guidelines of this project.
[ ] I have added appropriate unit tests.
[x] I have reviewed my changes before submitting this pull request.
[x] I have linked the issue or issues that are solved to the PR if any.
[x] I have assigned this PR to myself.
[x] I have added the minimum version decorator to any new backend method implemented.
[x] I have made sure that the title of my PR follows Conventional commits style (e.g. feat: extrude circle to cylinder)

Just a small consideration, is the picker example still up to date after these changes? I assume that it is but just in case 🙂

Good point - I also included in the docs the fact that a user could now just say design.plot(allow_picking=True) if they wanted. Also, the example was working fine buuuut... only for Windows. The Linux service was crashing since it does not allow for multiple designs, so I had to change the location of the multi_colors section. Thanks @AlejandroFernandezLuces for the review!


'Recents' section shows a deleted dashboard on the welcome screen

After deleting a dashboard from Superset welcome screen's Dashboard section, 'Recents' section still shows that dashboard which leads to an on-click error page.
NOTE: 'Recents' section shows the deleted dashboard until the screen is refreshed.
Expected results
After deleting a dashboard from Welcome screen's Dashboard section, that dashboard details should also be removed from the 'Recents' section.
Actual results
After deleting a dashboard from Welcome screen's Dashboard section, 'Recents' sections shows the details about that deleted dashboard until the screen is refreshed.
Screenshots

On clicking the deleted dashboard from the 'Recents' section leads to the below error-screen.

How to reproduce the bug

Go to Superset's Welcome screen
Scroll to the 'Dashboard' section
Delete an already existing dashboard from the 'Dashboard' section which is also present in 'Recents' section
If no dashboard is present, add a new dashboard by clicking on '+ Dashboard' button in 'Dashboard' section and delete it
Scroll up to the 'Recents' section
Click on the recently deleted dashboard from the 'Recents' section
You should see an error page in a new tab
Close the error-page
Navigate to the previous tab of Superset Welcome screen
Refresh the page
The deleted dashboard should disappear from the 'Recents' section

Environment
(please complete the following information):

superset version: commit#  c9a755f25
python version: Python 2.7.16
node.js version: v13.11.0

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

This no longer seems to be the case in current Superset


nodejs: define APPSODY_DEBUG_PORT

Checklist:

[x] Read the Code of Conduct and Contributing Guidelines.

[x] Followed the commit message guidelines.

[x] Stack adheres to Appsody stack structure.

Modifying an existing stack:

[x] Updated the stack version in stack.yaml

Defines the APPSODY_DEBUG_PORT environment variable in the stack. This information will be used by other projects such as Codewind.

Sure, but note that there is no way to enable the debug port in a generic nodejs app (generic meaning, started with npm start).


Secure flag for the X-Uaa-Csrf cookie

What version of UAA are you running?
UAA version: 4.12.1
How are you deploying the UAA?
I am deploying the UAA using cf-deployment.
What did you do?
curl -I <uaa url>/login
[...]
Set-Cookie: X-Uaa-Csrf=Ohd4coh4ceilucheengo0u; Max-Age=86400; Expires=Fri, 25-May-2018 09:39:20 GMT; Path=/; HttpOnly
[...]

This came up during our latest pentest as a low severity issue. If there is no specific reason to not to have the secure flag then it might be worth adding it as this could regularly come up in any pentest.
To my understanding this doesn't pose any security risk.
What did you expect to see? What goal are you trying to achieve with the UAA?
I expected to have the secure flag set on the X-Uaa-Csrf cookie.

I was able to get this working in Tomcat by setting this Valve in server.xml and setting require_https: true in login.yml. I'm not using cf-deployment though.
 <Valve className="org.apache.catalina.valves.RemoteIpValve"
        internalProxies="{{ id_api_proxy_ip }}"
        remoteIpHeader="x-forwarded-for"
        proxiesHeader="x-forwarded-by"
        protocolHeader="x-forwarded-proto"
        requestAttributesEnabled="true"
        httpsServerPort="{{ id_api_external_port }}"
        protocolHeaderHttpsValue="https" />

@c4milo thanks for the response, you're right, the secure flag is added when we enabled uaa.require_https in UAA release.
I'm closing this issue.


Pentaho Data Integration server (PDI) version requirement question

The current version available on Pentaho website is 9.0. Can I use it instead of 7.1 as it is mentioned in documentation?

Yes, you should be able to use the latest available pentaho version


Add descriptive logs to starter kits

[ ] Any “throw new exception” (ex: line 95 in wes) should have an "error" log that prints the exception stack trace/ message before throwing the generic exception (like “Could not load WES run log”)
[ ] Add "debug" level logs to commonly/ most used pieces of code. I would start with controllers. The idea is to be able to figure out the point/ region of code where an error might happen & for which object_id or input parameters, so that it's easier to reproduce this error while debugging.
[ ] This is totally optional and I would leave it to the very end. I have implemented struct logs that direct all the logs into a file. (Feel free to implement/ignore this as it is not a priority feature for the logs issue you are working on) - https://github.com/ga4gh/ga4gh-testbed-api/blob/develop/src/main/java/org/ga4gh/testbed/api/utils/logging/TestbedLoggingUtil.java

@yash-puligundla can i take up this issue??


Upgrade bleve from v2.0.6 to v2.3.0

Possible fix #18118

@lunny we have to migrate code ...
modules/indexer/code/bleve.go:427:17: cannot range over languagesFacet.Terms (type *search.TermFacets)

Possible fix #18118

Unless some package is using bleve v2.3.0 whereby the compiled code is using that version instead of the vendored v2.0.6, then their isn't anything to fix. V2.3.0 introduces some breaking changes(which we are impacted by), but they shouldn't be happening on our current version. So it's rather how the question that it comes someone is using v2.3.0 instead of the vendored one. I'm not against this change, I'd just feel that it kind of works around a problem that shouldn't be happening.

@lunny we have to migrate code ...
modules/indexer/code/bleve.go:427:17: cannot range over languagesFacet.Terms (type *search.TermFacets)

done.

Looks like some performance optimization https://github.com/blevesearch/bleve/pull/1404

My only question is that whether bleve 2.3.0 can read/write the data of 2.0.6.
If yes, it's good to follow the latest vendor package.
If no .... well, it's still fine to me but we need to tell users (or re-generate the indexers).

There is no break changelog from 2.0.6 to 2.3.0 and I have a simple test, the upgrade is smooth.

My only question is that whether bleve 2.3.0 can read/write the data of 2.0.6.
If yes, it's good to follow the latest vendor package.
If no .... well, it's still fine to me but we need to tell users (or re-generate the indexers).

There is no break changelog from 2.0.6 to 2.3.0 and I have a simple test, the upgrade is smooth.

Codecov Report

Merging #18132 (84909da) into main (1a4e2bf) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main   #18132   +/-   ##
=======================================
  Coverage   45.01%   45.01%
=======================================
  Files         825      825
  Lines       91538    91538
=======================================
+ Hits        41207    41208    +1
+ Misses      43745    43743    -2
- Partials     6586     6587    +1

Impacted Files
Coverage Δ

modules/indexer/code/bleve.go
66.52% <100.00%> (ø)

modules/queue/queue_channel.go
95.00% <0.00%> (-1.67%)
:arrow_down:

modules/queue/queue_bytefifo.go
59.28% <0.00%> (-0.60%)
:arrow_down:

routers/api/v1/repo/pull.go
28.69% <0.00%> (-0.51%)
:arrow_down:

modules/queue/workerpool.go
49.23% <0.00%> (+2.29%)
: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 1a4e2bf...84909da. Read the comment docs.

Codecov Report

Merging #18132 (84909da) into main (1a4e2bf) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main   #18132   +/-   ##
=======================================
  Coverage   45.01%   45.01%
=======================================
  Files         825      825
  Lines       91538    91538
=======================================
+ Hits        41207    41208    +1
+ Misses      43745    43743    -2
- Partials     6586     6587    +1

Impacted Files
Coverage Δ

modules/indexer/code/bleve.go
66.52% <100.00%> (ø)

modules/queue/queue_channel.go
95.00% <0.00%> (-1.67%)
:arrow_down:

modules/queue/queue_bytefifo.go
59.28% <0.00%> (-0.60%)
:arrow_down:

routers/api/v1/repo/pull.go
28.69% <0.00%> (-0.51%)
:arrow_down:

modules/queue/workerpool.go
49.23% <0.00%> (+2.29%)
: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 1a4e2bf...84909da. Read the comment docs.


fix: MD047/single-trailing-newline

Files should end with a single newline character

This is a new rule, so the VS Code extension doesn't flag it yet https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md047---files-should-end-with-a-single-newline-character
I used ECLint to fix most of the files https://github.com/jedmao/eclint#insert_final_newline, although there were 3 that didn't seem to pick up and needed manual change


Do the rebase on all rebaseable pull request

Fix #39

See #52. I've chosen to be a bit more careful in allowing all states to pass.


#238 multiple datasets

Description
Towards implementing multiple models and multiple datasets. fitting_problem now evaluates to give a list of solutions, one per model/dataset pair. Cost functions weight each error-set to get an overall error score, which is then optimised against. Draft PR, not fully tested and with open todos.
Issue reference
#238
Type of change

[ x ] New Feature: A non-breaking change that adds new functionality.
[ ] Optimization: A code change that improves performance.
[ ] Examples: A change to existing or additional examples.
[ ] Bug Fix: A non-breaking change that addresses an issue.
[ ] Documentation: Updates to documentation or new documentation for new features.
[ ] Refactoring: Non-functional changes that improve the codebase.
[ ] Style: Non-functional changes related to code style (formatting, naming, etc).
[ ] Testing: Additional tests to improve coverage or confirm functionality.
[ ] Other: (Insert description of change)

Key checklist:

[ ] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All unit tests pass: $ nox -s tests
[ ] The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.
Further checks:

[x ] Code is well-commented, especially in complex or unclear areas.
[ ] Added tests that prove my fix is effective or that my feature works.
[ ] Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

Thank you for contributing to our project! Your efforts help us to deliver great software.

Hi @MarkBlyth, thanks for this! I'll try to take a look through this afternoon or Monday morning 👍

Hi @MarkBlyth, I made a start on developing a cost wrapper for multiple cost objects to demonstrate what I meant in point (2) above - see issue #327 and the draft PR #329. I'd be happy to discuss pros/cons of different approaches.

@NicolaCourtier yep sounds good! I won't be able to put too much time into it until after the FI conference, but I'm keen to do some work on it.


Fix: centos8 reached EOL and ovn 21.03 tarball unmatch with ovs 2.15 tarball issue

Pull Request

[x] Make sure you have followed Kube-OVN Code Style.

What type of this PR
Examples of user facing changes:

Bug fixes

dpdk build failed because of base image centos8 reached End Of Life
ovn 21.03 tarball unmatch with ovs 2.15 tarball, like the inet_parse_active  function.
renaming to right name of image

Which issue(s) this PR fixes
Fixes #3545
WHAT
copilot:summary
copilot:poem
HOW
copilot:walkthrough

@singchia Thanks for your contribution to the DPDK stuff. It hasn't been actively maintained for a while, your efforts are particularly appreciated!

with pleasure.


Use git submodules for the protobufs

Although we've put in some work into making the task of updating protobuf simple, we still have the issue that the SDK has all the protobuf files committed. Besides the fact that we really shouldn't need to commit all the protobuf files, it also makes reviewing PRs more of a hassle since all the protobuf modifications are committed as well. If we can somehow update the SDK to use git sub-modules for the protobufs it would make updating the protobufs and reviewing PRs easier.

For Java, would suggest using the existing maven dependency, if possible. There are snapshot artifacts available for unreleased changes via a custom maven repository.

My concern is that the current artifacts being published use grpc-protobuf instead of grpc-protobuf-lite which is an issue when it comes to android.


Rochester draft broken

Just tried to simulate a two-player game. No success, picking doesn't work.

Fixed by 66a6bc5f3c891bdb60b8b63d2f2f04af1870853b


cf files gives " Service Unavailable" error

Hello,
My app has pushed successfully, and works well.
But, when using cf files, it gives " Service Unavailable" error.
Command
cf files business logs/
CLI Version
e.g. 6.13.0-e68ce0f  / linux
Error

Getting files for app business in org DevBox / space sp_yu as admin...
FAILED
Error performing request: Get https://acd2aeaba9b141f4a70fb3708fe83<IP_ADDRESS>.48.xip.io/instance_paths/f514a7a45b184966bba86628f6a562c7?hmac=7e5c8e1fcba90b8e0c26a06ad5eb81c291c9a055c3ac6df30a810bfe148d32f511617a55292dc5da3b6ad453542efe935ca779f12b50e463f7bea474602cf27b&path=logs%!F(MISSING)&timestamp=1462265966: Service Unavailable

Stack Trace
CC API Endpoint Version
API version: 2.40.0
CF Trace

REQUEST: [2016-05-03T17:00:59+08:00]
GET /v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/apps?q=name%3Abusiness&inline-relations-depth=1 HTTP/1.1
Host: api.<IP_ADDRESS>.xip.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.13.0-e68ce0f / linux
RESPONSE: [2016-05-03T17:00:59+08:00]
HTTP/1.1 200 OK
Content-Length: 5386
Content-Type: application/json;charset=utf-8
Date: Tue, 03 May 2016 09:00:59 GMT
Server: nginx
X-Cf-Requestid: c30cc32c-14e5-4b85-42f6-fe0b1d64f79d
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: d68abbf3-2d2c-4381-5abe-ff0c18cbe8b8::d969ecdc-6f31-4fa4-93cf-89c99fdff168
{
"total_results": 1,
"total_pages": 1,
"prev_url": null,
"next_url": null,
"resources": [
{
"metadata": {
"guid": "c0144c15-ab0d-4702-918b-34b1c500002c",
"url": "/v2/apps/c0144c15-ab0d-4702-918b-34b1c500002c",
"created_at": "2016-05-03T03:26:27Z",
"updated_at": "2016-05-03T08:35:17Z"
},
"entity": {
"name": "business",
"production": false,
"space_guid": "ea3d4dcc-a360-4210-9802-9683add1d814",
"stack_guid": "5f96409b-7259-47cb-9558-fcbe0623eb7d",
"buildpack": "java_buildpack_offline",
"detected_buildpack": null,
"environment_json": {
"no_proxy": "<IP_ADDRESS>,api.<IP_ADDRESS>.xip.io,doppler.<IP_ADDRESS>.xip.io,hm9<IP_ADDRESS>.48.xip.io,uaa.<IP_ADDRESS>.xip.io,loggregator.<IP_ADDRESS>.xip.io,business.<IP_ADDRESS>.xip.io"
},
"memory": 256,
"instances": 1,
"disk_quota": 1024,
"state": "STARTED",
"version": "e4731227-e113-4891-aca3-7d1a7fbc8af1",
"command": null,
"console": false,
"debug": null,
"staging_task_id": "e2197d302e7641c6ae73273682740617",
"package_state": "STAGED",
"health_check_type": "port",
"health_check_timeout": null,
"staging_failed_reason": null,
"staging_failed_description": null,
"diego": false,
"docker_image": null,
"package_updated_at": "2016-05-03T03:26:33Z",
"detected_start_command": "CALCULATED_MEMORY=$($PWD/.java-buildpack/open_jdk_jre/bin/java-buildpack-memory-calculator-2.0.0_RELEASE -memorySizes=metaspace:64m.. -memoryWeights=heap:75,metaspace:10,native:10,stack:5 -memoryInitials=heap:100%,metaspace:100% -totMemory=$MEMORY_LIMIT) &&  JAVA_HOME=$PWD/.java-buildpack/open_jdk_jre JAVA_OPTS="-Djava.io.tmpdir=$TMPDIR -XX:OnOutOfMemoryError=$PWD/.java-buildpack/open_jdk_jre/bin/killjava.sh $CALCULATED_MEMORY -Daccess.logging.enabled=false -Dhttp.port=$PORT" $PWD/.java-buildpack/tomcat/bin/catalina.sh run",
"enable_ssh": true,
"docker_credentials_json": {
"redacted_message": "[PRIVATE DATA HIDDEN]"
},
"space_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814",
"space": {
"metadata": {
"guid": "ea3d4dcc-a360-4210-9802-9683add1d814",
"url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814",
"created_at": "2016-05-03T03:04:21Z",
"updated_at": null
},
"entity": {
"name": "sp_yu",
"organization_guid": "e9479108-596b-4ec2-b9ee-5ff21a2d11e0",
"space_quota_definition_guid": null,
"allow_ssh": true,
"organization_url": "/v2/organizations/e9479108-596b-4ec2-b9ee-5ff21a2d11e0",
"developers_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/developers",
"managers_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/managers",
"auditors_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/auditors",
"apps_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/apps",
"routes_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/routes",
"domains_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/domains",
"service_instances_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/service_instances",
"app_events_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/app_events",
"events_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/events",
"security_groups_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814/security_groups"
}
},
"stack_url": "/v2/stacks/5f96409b-7259-47cb-9558-fcbe0623eb7d",
"stack": {
"metadata": {
"guid": "5f96409b-7259-47cb-9558-fcbe0623eb7d",
"url": "/v2/stacks/5f96409b-7259-47cb-9558-fcbe0623eb7d",
"created_at": "2015-11-09T01:50:12Z",
"updated_at": null
},
"entity": {
"name": "cflinuxfs2",
"description": "Cloud Foundry Linux-based filesystem"
}
},
"events_url": "/v2/apps/c0144c15-ab0d-4702-918b-34b1c500002c/events",
"service_bindings_url": "/v2/apps/c0144c15-ab0d-4702-918b-34b1c500002c/service_bindings",
"service_bindings": [
    ],
    "routes_url": "/v2/apps/c0144c15-ab0d-4702-918b-34b1c500002c/routes",
    "routes": [
      {
        "metadata": {
          "guid": "ccbb9c64-3e8a-4fd3-a123-be816203d580",
          "url": "/v2/routes/ccbb9c64-3e8a-4fd3-a123-be816203d580",
          "created_at": "2016-05-03T03:26:27Z",
          "updated_at": null
        },
        "entity": {
          "host": "business",
          "path": "",
          "domain_guid": "290918c3-4a43-4f2f-a795-572a02c8dec9",
          "space_guid": "ea3d4dcc-a360-4210-9802-9683add1d814",
          "service_instance_guid": null,
          "port": 0,
          "domain_url": "/v2/domains/290918c3-4a43-4f2f-a795-572a02c8dec9",
          "space_url": "/v2/spaces/ea3d4dcc-a360-4210-9802-9683add1d814",
          "apps_url": "/v2/routes/ccbb9c64-3e8a-4fd3-a123-be816203d580/apps"
        }
      }
    ]
  }
}

]
}
Getting files for app business in org DevBox / space sp_yu as admin...
REQUEST: [2016-05-03T17:00:59+08:00]
GET /v2/apps/c0144c15-ab0d-4702-918b-34b1c500002c/instances/0/files/logs/ HTTP/1.1
Host: api.<IP_ADDRESS>.xip.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.13.0-e68ce0f / linux
REQUEST: [2016-05-03T17:00:59+08:00]
GET /instance_paths/f514a7a45b184966bba86628f6a562c7?hmac=35e907e0e7bae7b48e2ffdffaac99b58c4c3f3b6247beb2f822db443f070099ab535f107806bc4afca803914c35dd63410bc07ca4e9cd9046809afdde8e9983b&path=logs%2F&timestamp=1462266059 HTTP/0.0
Host: acd2aeaba9b141f4a70fb3708fe83<IP_ADDRESS>.48.xip.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Referer: https://api.<IP_ADDRESS>.xip.io/v2/apps/c0144c15-ab0d-4702-918b-34b1c500002c/instances/0/files/logs/
User-Agent: go-cli 6.13.0-e68ce0f / linux
REQUEST: [2016-05-03T17:01:20+08:00]
GET /instance_paths/f514a7a45b184966bba86628f6a562c7?hmac=13fd777fa8c8c94512e1c9cd94a7606e1902d895ad1fec3c5a59a7fc1996b8fa0d49a40104b7c034a360635b9c7576a69e8fc2188c4f90379b76ba2597514891&path=logs%2F&timestamp=1462266080 HTTP/0.0
Host: acd2aeaba9b141f4a70fb3708fe83<IP_ADDRESS>.48.xip.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Referer: https://api.<IP_ADDRESS>.xip.io/v2/apps/c0144c15-ab0d-4702-918b-34b1c500002c/instances/0/files/logs/
User-Agent: go-cli 6.13.0-e68ce0f / linux
REQUEST: [2016-05-03T17:01:41+08:00]
GET /instance_paths/f514a7a45b184966bba86628f6a562c7?hmac=5d3062624c322e2db108                                                       d1d84d8d3b68cf384319be4b6f91dd8432b4bbeeb6f9078ef7216&path=logs%2F&timestamp=1
Host: acd2aeaba9b141f4a70fb3708fe83<IP_ADDRESS>.48.xip.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Referer: https://api.<IP_ADDRESS>.xip.io/v2/apps/c0144c15-ab0d-4702-918b-34b1
User-Agent: go-cli 6.13.0-e68ce0f / linux
FAILED
Error performing request: Get https://acd2aeaba9b141f4a70fb3708fe83249.10.167.                                                       a562c7?hmac=5d3062624c322e2db1089c4987cc041edc7e3a94a14d1752ed2d6bb89c873ee1ef                                                       8ef7216&path=logs%!F(MISSING)&timestamp=1462266101: Service Unavailable

Platform Details
Ubuntu 14.04.3 64-bit
Shell
Terminal(putty)
I tried send the same request with curl command like this, but it also failed.

$ CF_TRACE=true curl -k --get https://api.<IP_ADDRESS>.xip.io//instance_paths/ --header "HOST:acd2aeaba9b141f4a70fb3708fe83<IP_ADDRESS>.48.xip.io"  --header "Accept: application/json" --header "User-Agent: go-cli 6.13.0-e68ce0f / linux" --data "hmac=35e907e0e7bae7b48e2ffdffaac99b58c4c3f3b6247beb2f822db443f070099ab535f107806bc4afca803914c35dd63410bc07ca4e9cd9046809afdde8e9983b&path=logs%2F&timestamp=1462266059"
DEA is unreachable

We've seen issues with xip.io not being a stable DNS service. Can you change to use bosh-lite.com instead?

The <IP_ADDRESS>.xip.io is mapped to the localhost in the hosts file,  so I don't think it will use xip.io DNS service.
And if xip.io was unstable "business.<IP_ADDRESS>.xip.io" should not be accessed, but actually it can be accessed.
So it doesn't seem to be caused by the  xip.io.
I don't know why the host of the second request has became "acd2aeaba9b141f4a70fb3708fe83<IP_ADDRESS>.48.xip.io.",
although I think it should be business.<IP_ADDRESS>.xip.io.
It seems that the "acd2aeaba9b141f4a70fb3708fe83<IP_ADDRESS>.48.xip.io." doesn't appear in the hosts file, so when the second request  was sent to the web server on the container,  it can't  reach to that container.

Getting files for app business in org DevBox / space sp_yu as admin...
REQUEST: [2016-05-03T17:00:59+08:00]
GET /v2/apps/c0144c15-ab0d-4702-918b-34b1c500002c/instances/0/files/logs/ HTTP/1.1
Host: api.<IP_ADDRESS>.xip.io
...
REQUEST: [2016-05-03T17:00:59+08:00]
GET /instance_paths/f514a7a45b184966bba86628f6a562c7?hmac=35e907e0e7bae7b48e2ffdffaac99b58c4c3f3b6247beb2f822db443f070099ab535f107806bc4afca803914c35dd63410bc07ca4e9cd9046809afdde8e9983b&path=logs%2F&timestamp=1462266059 HTTP/0.0
Host: acd2aeaba9b141f4a70fb3708fe83<IP_ADDRESS>.48.xip.io
...

You'd have to ask the Cloud Controller team to confirm, but possibly the Files API redirects to another hostname that serves the file to you. I don't know if this hostname is always the same - you may not be able to get it to work reliably by adding it to /etc/hosts.
Also, I'm not sure why the trace is not displaying the responses, which could help understand where that host name comes from. The CLI version you use is over 6 months old. You could try on the latest version.

Closing. I have confirmed in my local bosh-lite environment that the Files API redirects to a generated hostname, ad that works for me (using bosh-lite.com, not xip.io). Why it is that way is a question for the CAPI team.


 This causes us to try to avoid Docker for build performance reasons (see #280, for example).
I don't see anything inherent in what we're doing with our Docker builds that would make them necessarily slower than equivalent non-Docker builds. My hypothesis is that we can eliminate waste in the Docker builds and get them to be about the same performance as non-Docker builds. I'm experimenting with that now.

See #293.
I'm also experimenting with precompiling some of the Go dependencies, similar to how we precompile Rust dependencies now.

I didn't have success getting builds faster in Travis CI, beyond the trivial win in #297.
I experimented with doing the proxy build + test (the slowest part of the build) in Docker on Google Clould Container Builder.
Using a 32-cpu machine dropped the release build + test time from >18 minutes to just over 7 minutes: https://console.cloud.google.com/gcr/builds/563ce218-c6f1-47fa-87e3-75b16bb419af?project=runconduit (Travis CI runtime was over 15 minutes.)
I rewrote some of the stuff to enable more incremental caching of the proxy build stage. Initial results show that the full build got ~2 minutes slower. I think we need to do a few iterations of the ">7 minute" build above and this ">9 minute" build to figure out what the real performance is.
With the incremental caching logic in place, I was able to do a <2min no-op (nothing in the proxy changed) rebuild using a cached proxy build image: https://console.cloud.google.com/gcr/builds/97ee2230-878b-4d39-8cd8-05fce409e0c7?project=runconduit
I also did a rebuild where one proxy Rust source file was changed, showing that the initial (deps) layers from the previous run were used: https://console.cloud.google.com/gcr/builds/1f12a1ec-d95b-4432-889a-a2cba370ac1a?project=runconduit. The intermediate layer caching saves about 2.5 minutes over the ">9 minute" build above. Again, we need to do a bunch of iterations to see if this caching is a significant win or not.
Regardless, all of these timings from Google Cloud Container Builder are significantly faster than the timings I got from doing the build on Travis CI. Thus, I think we should change the "Docker Deploy" stage of the Travis CI to do the image building in Google Cloud Container Builder.
/cc @olix0r @klingerf

I rewrote some of the stuff to enable more incremental caching of the proxy build stage. Initial results show that the full build got ~2 minutes slower. I think we need to do a few iterations of the ">7 minute" build above and this ">9 minute" build to figure out what the real performance is.

I see that the Container Builder has two different fields for showing the build time, which are about 2 minutes apart. Thus the ">7 minute" build and the ">9 minute" build took about the same amount of time.

Also, sadly, the 8-CPU builds weren't significantly faster than the 32-CPU builds. The 8-CPU builds were significantly faster than the default (1? 2?) CPU builds though.

#332, #331, #329, #327, and #325 are incremental improvements on this that speed up incremental docker builds of the controller by over 50% on my machine.
Further, on Monday I'm expecting to have a change ready that I expect to massively improves things.


Install instruction

It would be really helpful (for those at the bottom of the learning curve) if there were a couple of lines in the README on how to install this software.
"See bimmerconnected for usage instruction" is not very helpful.  What does it mean?

Basically it means you're supposed to execute python -m bimmer_connected.cli on the command line and you'll get the available available options.
You of course need python 3.5+ installed and either install this library via pip or git clone.
Is this the kind of help you would expect?

Yes, if that does the trick. Or pip install ...


Merge, tests

Extraction from AST work.
@jdegoes I don’t think that merge needs to return Either.
At least in my mind in a merge operation the RHS always takes precedence,
so merging a top-level true with null -> null.
The strongest case for merging disparate types is in objects where we could nulling a field
when updating it is pretty common. The case for single-node documents is weaker.
LMK what you think.

Getting this in.

@fsvehla Looks good to me!


[AWS Lambda] Unable to Use Test Console

Description:
After creating the Lambda in APIM, unable to test in publisher. Seems the call hasn't reached lambda

Duplicate of https://github.com/wso2/product-apim/issues/10478 hence closing the issue


Fix e2e tests by using a different entities loading mechanism

At the moment, e2e tests fail because of errors like this:
ERROR [ExceptionsHandler] No metadata for "ServiceDocOrm" was found.

This PR uses a different mechanism for loading entities in order to (temporarily) fix this. Unfortunately, I don't know enough about NestJS so I cannot say if the mechanism has any singificant downsides. According to the documentation on https://docs.nestjs.com/techniques/database, it has the following problem:
Note that entities that aren't registered through the forFeature() method, but are only referenced from the entity (via a relationship), won't be included by way of the autoLoadEntities setting.

I simply don't know if that is something we care about at the moment. So my suggestion is that we:

use the new loading mechanism for now, so that we aren't blocked
look for the actual reason why tests failed
remove the new loading mechanism and properly fix the tests

CI failing because of:
Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF

I assume this is a temporary thing. But I don't have the permission to manually trigger the pipeline again.

Awesome, thx!


Create bn.json

Translated into Bangla.
Bengali language: Bengali Bangla, a member of the Indo-Aryan group of the Indo-Iranian branch of the Indo-European language family. It is spoken by more than 210 million people as a first or second language.

Thank you!