Installing issues

Hi,
I've tried installing nanopolish through conda and when I try to call it I get this error:
nanopolish: error while loading shared libraries: libhdf5.so.10: cannot open shared object file: No such file or directory
I uninstalled that and then tried to install through github, however when I used the make command in the directory it went a bit mad.
make[1]: Entering directory '/home/hlrpenri/nanopolish/hdf5-1.8.14' Making all in src make[2]: Entering directory '/home/hlrpenri/nanopolish/hdf5-1.8.14/src' make  all-am make[3]: Entering directory '/home/hlrpenri/nanopolish/hdf5-1.8.14/src'   CC       H5.lo In file included from H5.c:27:0: H5Eprivate.h:35:32: warning: anonymous variadic macros were introduced in C99 [-Wvariadic-macros]  #define HERROR(maj_id, min_id, ...) H5E_printf_stack(NULL, __FILE__, FUNC, __LINE__, H5E_ERR_CLS_g, maj_id, min_id, __VA_ARGS__)                                 ^~~ In file included from H5.c:27:0: H5Eprivate.h:41:33: warning: anonymous variadic macros were introduced in C99 [-Wvariadic-macros]  #define HCOMMON_ERROR(maj, min, ...)                    \                                  ^~~ H5Eprivate.h:55:40: warning: anonymous variadic macros were introduced in C99 [-Wvariadic-macros]  #define HDONE_ERROR(maj, min, ret_val, ...) {          \                                         ^~~ H5Eprivate.h:67:40: warning: anonymous variadic macros were introduced in C99 [-Wvariadic-macros]  #define HGOTO_ERROR(maj, min, ret_val, ...) {          \                                         ^~~ In file included from H5.c:24:0: H5.c: In function 'H5_init_library': H5private.h:1539:14: warning: ISO C90 does not support '__func__' predefined identifier [-Wpedantic]  #define FUNC __func__               ^ H5Eprivate.h:35:70: note: in expansion of macro 'FUNC'  #define HERROR(maj_id, min_id, ...) H5E_printf_stack(NULL, __FILE__, FUNC, __LINE__, H5E_ERR_CLS_g, maj_id, min_id, __VA_ARGS__)                                                                       ^~~~ H5Eprivate.h:42:4: note: in expansion of macro 'HERROR'     HERROR(maj, min, __VA_ARGS__);           \     ^~~~~~ H5Eprivate.h:68:4: note: in expansion of macro 'HCOMMON_ERROR'     HCOMMON_ERROR(maj, min, __VA_ARGS__);           \     ^~~~~~~~~~~~~ H5.c:181:9: note: in expansion of macro 'HGOTO_ERROR'          HGOTO_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, "unable to initialize error interface")          ^~~~~~~~~~~ H5private.h:1539:14: warning: ISO C90 does not support '__func__' predefined identifier [-Wpedantic]  #define FUNC __func__               ^ H5Eprivate.h:35:70: note: in expansion of macro 'FUNC'  #define HERROR(maj_id, min_id, ...) H5E_printf_stack(NULL, __FILE__, FUNC, __LINE__, H5E_ERR_CLS_g, maj_id, min_id, __VA_ARGS__)                                                                       ^~~~ H5Eprivate.h:42:4: note: in expansion of macro 'HERROR'     HERROR(maj, min, __VA_ARGS__);           \     ^~~~~~ H5Eprivate.h:68:4: note: in expansion of macro 'HCOMMON_ERROR'     HCOMMON_ERROR(maj, min, __VA_ARGS__);           \     ^~~~~~~~~~~~~ H5.c:183:9: note: in expansion of macro 'HGOTO_ERROR'          HGOTO_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, "unable to initialize property list interface")          ^~~~~~~~~~~ H5private.h:1539:14: warning: ISO C90 does not support '__func__' predefined identifier [-Wpedantic]  #define FUNC __func__               ^ H5Eprivate.h:35:70: note: in expansion of macro 'FUNC'  #define HERROR(maj_id, min_id, ...) H5E_printf_stack(NULL, __FILE__, FUNC, __LINE__, H5E_ERR_CLS_g, maj_id, min_id, __VA_ARGS__)                                                                       ^~~~ H5Eprivate.h:42:4: note: in expansion of macro 'HERROR'     HERROR(maj, min, __VA_ARGS__);           \     ^~~~~~ H5Eprivate.h:68:4: note: in expansion of macro 'HCOMMON_ERROR'     HCOMMON_ERROR(maj, min, __VA_ARGS__);           \     ^~~~~~~~~~~~~ H5.c:185:9: note: in expansion of macro 'HGOTO_ERROR'          HGOTO_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, "unable to initialize datatype interface")          ^~~~~~~~~~~ H5private.h:1539:14: warning: ISO C90 does not support '__func__' predefined identifier [-Wpedantic]  #define FUNC __func__               ^ H5Eprivate.h:35:70: note: in expansion of macro 'FUNC'  #define HERROR(maj_id, min_id, ...) H5E_printf_stack(NULL, __FILE__, FUNC, __LINE__, H5E_ERR_CLS_g, maj_id, min_id, __VA_ARGS__)                                                                       ^~~~ H5Eprivate.h:42:4: note: in expansion of macro 'HERROR'     HERROR(maj, min, __VA_ARGS__);           \     ^~~~~~ H5Eprivate.h:68:4: note: in expansion of macro 'HCOMMON_ERROR'     HCOMMON_ERROR(maj, min, __VA_ARGS__);           \     ^~~~~~~~~~~~~ H5.c:187:9: note: in expansion of macro 'HGOTO_ERROR'          HGOTO_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, "unable to initialize dataset interface")          ^~~~~~~~~~~ H5private.h:1539:14: warning: ISO C90 does not support '__func__' predefined identifier [-Wpedantic]  #define FUNC __func__               ^ H5Eprivate.h:35:70: note: in expansion of macro 'FUNC'  #define HERROR(maj_id, min_id, ...) H5E_printf_stack(NULL, __FILE__, FUNC, __LINE__, H5E_ERR_CLS_g, maj_id, min_id, __VA_ARGS__)                                                                       ^~~~ H5Eprivate.h:42:4: note: in expansion of macro 'HERROR'     HERROR(maj, min, __VA_ARGS__);           \     ^~~~~~ H5Eprivate.h:68:4: note: in expansion of macro 'HCOMMON_ERROR'     HCOMMON_ERROR(maj, min, __VA_ARGS__);           \     ^~~~~~~~~~~~~ H5.c:189:9: note: in expansion of macro 'HGOTO_ERROR'          HGOTO_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, "unable to initialize metadata caching interface")          ^~~~~~~~~~~ H5private.h:1539:14: warning: ISO C90 does not support '__func__' predefined identifier [-Wpedantic]  #define FUNC __func__               ^ H5Eprivate.h:35:70: note: in expansion of macro 'FUNC'  #define HERROR(maj_id, min_id, ...) H5E_printf_stack(NULL, __FILE__, FUNC, __LINE__, H5E_ERR_CLS_g, maj_id, min_id, __VA_ARGS__)                                                                       ^~~~ H5Eprivate.h:42:4: note: in expansion of macro 'HERROR'     HERROR(maj, min, __VA_ARGS__);           \     ^~~~~~ H5Eprivate.h:68:4: note: in expansion of macro 'HCOMMON_ERROR'     HCOMMON_ERROR(maj, min, __VA_ARGS__);           \     ^~~~~~~~~~~~~ H5.c:191:9: note: in expansion of macro 'HGOTO_ERROR'          HGOTO_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, "unable to initialize link interface")          ^~~~~~~~~~~  . etc.
Thanks in advance for your support!
Rebekah

Hi @rebeelouise,
Sorry for the slow response, I was on holiday. Is this still an issue? If so can you copy the entire compile log into a text file and attach it to this issue?
Thanks,
Jared

Hi,
I am also running into this exact issue.
Background: I'm using Ubuntu on my Windows 10 machine. until this morning, my indexing using Nanopolish indexing wouldn't work completely- error being that fast5 files could not be found and so no readdb file was created
I checked the nanopolish version - 0.9.0.
So I tried to update in multiple ways - conda, sudo apt upgrade and GitHub repo.
Ran into the SAME problems mentioned here - even the version check command won't work now
Please let me know how I could fix this? Thanks for your support!

Hi all,
I am having the same issue.
Any solution to that ?
best,
Nic

Did this get solved?


Enable landscape

Is it possibile to see video in landscaepe, only when it is full screen? (app i portrait only)
Thanks

Ok so i need to override the getLayoutId?
wha about this issue:

Thanks

@digitalx-dev This image mean video in a wrong state, click to restart

I will translate the words

I just want to know how to remove or customize the chinese views...
Thanks

https://github.com/lipangit/JiaoZiVideoPlayer/commit/fee0ccd508521919825cbf9c231d9daf7d13dc1f


Symbol `vkDeviceWaitIdle' causes overflow in R_X86_64_PC32 relocation

I'm having these output, but the app still runs.
Is this important?
./ShadowMapping: Symbol `vkDeviceWaitIdle' causes overflow in R_X86_64_PC32 relocation
./ShadowMapping: Symbol `vkDeviceWaitIdle' causes overflow in R_X86_64_PC32 relocation
./ShadowMapping: Symbol `vkDestroySurfaceKHR' causes overflow in R_X86_64_PC32 relocation
./ShadowMapping: Symbol `vkDestroySurfaceKHR' causes overflow in R_X86_64_PC32 relocation

Interesting - I don't know off the top of my head what this indicates. What OS/compiler is this on? Is this a sample that I can try to build myself?

Closing this since no additional information is available; this is hopefully a build issue of some sort, e.g. trying to compile volk without -fPIC and linking it into a relocatable module.


Feat/add react native expo client

LGTM

Super cool. Thanks for adding! Is it expected that I see this after authorizing the test payment on for the 3155 SCA card? Guessing it's related to redirecting back into the app or something.

Fixed via https://github.com/stripe-samples/accept-a-payment/pull/123/commits/150b7e7dceccd9d7c151b2ac89a9c7e257f09c7c


Add documentation for configuration and privilege requirements

A Pull Request should be associated with an Issue.
Fixes https://github.com/cashapp/spirit/issues/219
Documents https://github.com/cashapp/spirit/issues/221
Also fixes a broken link and clarifies what read-replica support is.

Lgtm


Component Field Not Syncing to SQL Issue Table after Jira-DevLake Integration

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
I have successfully established a connection between my Jira instance and Apache DevLake. However, upon updating the 'component' field in an issue within Jira, the updated value does not reflect in the corresponding SQL table of issues in DevLake. The expected behavior is that any updates made in Jira should synchronize across to DevLake and be visible in the database. Attached are the screenshots displaying the configuration and the issue update in Jira.
What do you expect to happen
The 'component' field value in the DevLake SQL 'issues' table should be updated to match the value in Jira after synchronization.
How to reproduce
Steps to Reproduce:
Establish a connection between Jira and Apache DevLake.
Ensure that the 'Issue Tracking' and 'Cross Domain' data entities are selected in the DevLake configuration.
Update the 'component' field in a Jira issue.
Execute the synchronization process in DevLake to update the SQL tables.
Check the 'issues' SQL table in DevLake for the updated 'component' field value.
Notice that the 'component' field value is not updated in the SQL table.
Expected Result:
The 'component' field value in the DevLake SQL 'issues' table should be updated to match the value in Jira after synchronization.
Actual Result:
The 'component' field value is not present in the SQL 'issues' table after synchronization.
Please refer to the attached screenshots for a visual representation of the problem.
Anything else
No response
Version
v0.18.0
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

@klesh The component field is a jira standard field

@Startrekzky i think this is a bug

Will fix it in v0.21 if it is reproduced.


WIP: use distinct filename for debug builds

Using a distinct file for debug builds would simplify some things imho. There are a bunch of cases where it makes sense to have both files side by side.
If you also see value in this, I'd finish it here.

I already taught about adding the debug version to the CI build output. Good that you bright this on.
Is dist/webui-2.dll and dist/debug/webui-2.dll can solve the issue?

I mean, yes, it's good to continue, but I suggest keeping the file name the same, but simply add a debug folder inside the dist folder. dist/debug. If it's not possible then we can add -debug to the output file name.

I see. That's good. And it should work!

What do you think about shipping both in then in the releases and artifacts instead of separating them there
webui-linux-gcc-x64.zip
├── debug
│   ├── libwebui-2-static.a
│   └── webui-2.so
├── include
│   ├── webui.h
│   └── webui.hpp
├── libwebui-2-static.a
└── webui-2.so

something like this?
Maybe this is event what you mean by saying

I already taught about adding the debug version to the CI build output.

because we actually already have Debug builds in the CI output.

What do you think about shipping both in then in the releases and artifacts

Yes, that what I meant 👍
one archive for both release and debug

Testing the changes during the integration already feels like this change makes a lot of things simpler. So I feel reinforced that this is a good step to take.
The commits could have been split more fine grained, as they contain some other small fixes. But I hope until we have arrived at a new stable version some crammed up commits are okay, mainly due to time reasons.


TypeError: Cannot read property 'title' of undefined

i did exactly wat u did but it shows this error when i try to add book

This is a collection of codelabs. Which codelab exactly are you referring to?

cloud-nodejs


build: setup build for cjs/esm

BREAKING CHANGE: build tooling for both esm and cjs imports.
This should fix issues where the applications building esm modules receive an error saying the default expression is not callable.
The adjustments accomplish this by explicitly exporting an esm module AND a cjs module. Additionally, by using only a default function export we prevent the issue of the IDE incorrectly inferring that the default module is not callable. This will break backwards compatibility and force users who are not importing the library as a default import to import it as such.
Additionally, because we are explicitly exporting an esm module where before we were relying on esmodule interoperability this will require a major version bump.

Superseded by #345


Update getting started Gradle snippets

This is a follow-up from a discussion on Slack: https://kotlinlang.slack.com/archives/C88E12QH4/p1593875942190700
Seems like our getting started documentation is not properly working:

The plugins {} block was placed after a repository {} which is not allowed by Gradle
The Kotlin DSL syntax was invalid: includeGroup "org.jetbrains.kotlinx" without parentesis.
For some reason the Android setup was applying the Detekt plugin twice (with the apply: and the plugins{} syntax).

I've fixed all of them, plus I'm providing snippets for setting up using Plugin DSL and Legacy plugin application both for Groovy and Kotlin flavors.

(Not approving it because I have no authority in this repo)

I think that you should not hestiate about approving a PR if you think that it deserves it. In this project or any other open source project. We are looking for all the feedback from the comminity so if you think that this PR should be merged I encorege you to approve it.
For example, in this PR I think that your point of view is much more valuable than mine or any other contributor. We know how to setup detekt so we have a lot of bias in this area. So thank you to take the time to review the PR and give the feedback :)


As a user, I want to mass import multiple cards at the same time from a single file.

So that I can tag large amount of questions and answers at once.

Completed in release v1.4


Migrate flowcontrol.apiserver.k8s.io/v1beta3 to v1

What would you like to be added:
As we discussed here we should migrate flowcontrol.apiserver.k8s.io/v1beta3 to v1 once we drop the 1.28 supporting.
Why is this needed:
flowcontrol.apiserver.k8s.io/v1beta3 FlowSchema is deprecated in v1.29+ and unavailable in v1.32+.
Completion requirements:
This enhancement requires the following artifacts:

[ ] Design doc
[ ] API change
[ ] Docs update

The artifacts should be linked in subsequent comments.

Question regarding the support: https://github.com/kubernetes-sigs/kueue/pull/3043#discussion_r1760626660. I'm wondering what happens if 1.32 is released, so we release 0.10 Kueue according to the plan. IIUC this will complicate deployment of the latest Kueue on 1.31 which will be still used by majority of clusters at that point.

@mbobrovskyi Could you update this issue to align with the latest decision?

/remove-lifecycle stale


No connection to the guest device. Please ensure the WebRTCprocess on the host machine is active.

I am launching the cuttlefish virtual device on the VM and even on the host machine especially in a restricted network environment but gettng this kind of issue, not able to get the display of the device

Please need an immediate solution because of an important task


Add Nav header to the Examples site.

It's not perfect, but good enough!
This adds the navigation bar in the examples page so that users can navigate to
Examples, Playground, Reference.. etc.
What would be perfect is to use proper HTML template files for all examples instead of repeating boilerplate HTML documents. Also, maybe build the whole thing into a shell page. Anyway, this works for now :)

Hi, thank you for your submission I think it's good idea to add it. Can you provide a screenshot?

@CezCz added screenshot


Modal goes up from pressing a TextInput on Android

Hey people.
I have a modal which contains a TextInput. When I press on the TextInput, the whole Modal goes up (I didn't use the AvoidKeyboard property when defining the modal, and I also tried to explicitly set it to false.
Here is the code of the render function of my component.
`
    return (
        <Modal isVisible={this.state.isVisible} backdropOpacity={0.4} onBackdropPress={() => this.setState({ isVisible: false })} onBackButtonPress={() => this.setState({ isVisible: false })} >
            <View style={styles.container}>
                <View style={styles.divider}>
                    ...
                </View>
                <TextInput style={{backgroundColor: 'white'}}/>
            </View>
        </Modal>
    );
}`

And when I press on the TextInput, the whole Modal goes up.
Here's what My modal looks like before

And here's how to looks like when I press on the textinput

I also should mention that when I used the regular react-native's Modal component instead of the react-native-modal component this problem didn't occur and when I pressed on the textinput, the modal stayed the same and didn't move (well, react-native's Modal component has its own problems which is why I tried to use this component instead, but at least it proved me that the problem is not in some of my other code around my modal component).
The device I worked on is Android Samsung J7, and I use the react-native-modal version 7.0.2
Thanks for the help! :)

Hi!
Did you already tried changing the Android softInputMode in the manifest?

Hi!
Did you already tried changing the Android softInputMode in the manifest?
This might help you as well.

Thanks! Currently my app is still in early stages so I'm working with Expo, from which it seems there is no easy way to change the manifest file because to my understanding Expo manages these files internally.
Is there any other way/hack to do it through the code?

@Pazamozaurus not sure on that honestly 🤔Do you know if you're having the issue on standard RN as well?

Did you figure it out?

I have the same issue, @mmazzarolo did you solve it?

I have the same issue, how to deal with it ? please help

I have the same issue

I have the same issue.


Matching separated arrays for Realm Object

I’m stuck with some problem. I have a json response from server:
{
  "days" : [
    {
      "id" : 1,
      "name" : "Day 1 - first day",
      "url": "http://example.com/days/1"
    },
    {
      "id" : 2,
      "name" : "Day 2 - second day",
      "url": "http://example.com/days/2"
    },
    ...
  ],
  "week" : [
    {
       "id" : 1,
       "dayIds" : [1, 2, 6, 9, 23, 44, 2345],
       "name" : "Rest week"
    },
    {
       "id" : 35,
       "dayIds" : [34,77,23,67,126,224],
       "name" : "Educational week"
    },
  ],
  "plan" : {
    "weekIds: [1, 6, 23, 74]
  }
}

My data models (without mapping):
class Day: Object {
	@objc dynamic var id: Int = -1
	@objc dynamic var name: String = ""
	@objc dynamic var url: String = ""
}

class Week: Object {
	var dayIds = List<String>()
	@objc dynamic var name: String = ""
	@objc dynamic var id: Int = -1
	var days: List<Week>? = nil
}

class Plan: Object {
	var weekDays = List<String>()
	var weeks: List<Week>? = nil
}

Mapping code:
let json: [String: Any] = try! JSONSerialization.jsonObject(with: data, options: .allowFragments) as! [String: Any]

let plans: [Plan] = Mapper<Plan>().mapArray(JSONArray: json["plans"] as! [[String: Any]])
let days: [Day] = Mapper<Day>().mapArray(JSONArray: json["days"] as! [[String: Any]])
let weeks: [Week] = Mapper<Week>().mapArray(JSONArray: json["weeks"] as! [[String: Any]])

So, I need to tell realm that array weeks belong to plan.weeks and array days belong to object week.days and related by theirs id’s. How can I do this more simply? Do you have any ideas?
Alternative solution is in-head brutforce like this.
for week in weeks {
	for dayId in week.dayIds {
		for day in days {
			if day.id == dayId {
				week.days.append(day)
			}
		}
	}
}
for plan in plans {
	for week in weeks {
		for weekId in plans.weekIds {
			if weekId == week.id {
				plan.weeks.append(week)
			}
		}
	}
}

I believe that somewhere exist more pure and simple solution :)
Thanks.

The way the data is coupled doesn't lend itself well to the way realm structures data.
If you cannot alter the data model, I would recommend you decode and map the data structures similarly to how I've done below:
import UIKit
import RealmSwift

// ==== Realm Objects ==== //
class Day: Object, Decodable {
    @objc dynamic var id: Int = 0
    @objc dynamic var name: String = ""
    @objc dynamic var url: String = ""
}

class Week: Object {
    @objc dynamic var id = 0
    @objc dynamic var name: String = ""
    let days = List<Day>()
}

class Plan: Object {
    let weeks = List<Week>()
}

// ==== Mapper Objects ==== //
struct Schedule: Decodable {
    private enum CodingKeys: CodingKey {
        case plan, week, days
    }

    private struct JSONWeek: Decodable {
        let id: Int
        let name: String
        let dayIds: [Int]
    }

    private struct JSONPlan: Decodable {
        let weekIds: [Int]
    }

    let plan: Plan

    init(from decoder: Decoder) {
        let container = try! decoder.container(keyedBy: CodingKeys.self)

        let days = try! container.decode([Day].self, forKey: .days)
        let daysMap = days.reduce(into: [Int:Day](), { (result: inout [Int: Day], day: Day) in
            result[day.id] = day
        })

        let weeks: [Week] = try! container.decode([JSONWeek].self, forKey: .week).map {
            let week = Week.init()
            week.id = $0.id
            week.name = $0.name
            week.days.append(objectsIn: $0.dayIds.compactMap { daysMap[$0] })
            return week
        }

        let weeksMap = weeks.reduce(into: [Int:Week](), { (result, week) in
            result[week.id] = week
        })

        self.plan = Plan()
        plan.weeks.append(objectsIn: try! container.decode(JSONPlan.self, forKey: .plan).weekIds.compactMap {
            weeksMap[$0]
        })
    }
}

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    let json = """
    {
      "days" : [
        {
          "id" : 1,
          "name" : "Day 1 - first day",
          "url": "http://example.com/days/1"
        },
        {
          "id" : 2,
          "name" : "Day 2 - second day",
          "url": "http://example.com/days/2"
        }
      ],
      "week" : [
        {
           "id" : 1,
           "dayIds" : [1, 2, 6, 9, 23, 44, 2345],
           "name" : "Rest week"
        },
        {
           "id" : 35,
           "dayIds" : [34,77,23,67,126,224],
           "name" : "Educational week"
        }
      ],
      "plan" : {
        "weekIds": [1, 6, 35, 23, 74]
      }
    }
    """

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {

        let schedule = try! JSONDecoder().decode(Schedule.self, from: json.data(using: .utf8)!)

        return true
    }
}

This effectively maps your JSON to their realm counterparts.


Making a subplot figure with umap.plot objects

I know that umap.plot return matplotlib.pyplot axes but I cannot get my head around making a subplot (as in a 2D array of umap.plots)
I am trying:
import matplotlib.pyplot as plt
import umap.plot
import umap
import sklearn.datasets

pendigits = sklearn.datasets.load_digits()

fig, axs = plt.subplots(2,2,figsize = (10,10))
for r in range(1):
    for c in range(1):
        mapper = umap.UMAP(n_neighbors = ((r+c) + 1)*5, spread = ((r+c)+1)*2).fit(pendigits.data)
        axs[r,c] = umap.plot.points(mapper, labels = pendigits.target)

plt.show()
fig.savefig('fig.png')

I am simply getting one umap.plot and an empty 2x2 grid, what am I doing wrong?

I just forked the repository planning to add this functionality (I was using an older version) -- but I discovered it was already done in 050b73766959a6c1ef591b3142fef01d6f3139f3.
So, I guess you can already close this one! :)
Thanks for all you do!


Updated script/parse_log to work on new log file format.

coverage: 94.421%. remained the same
when pulling 1cb96fd63b0dea5c8938f478814ca197a24d81ab on fix-parse-log
into de66010fb89b216edfe1db003fc8eca213b4c243 on main.


Where does the files end up on macOS?

Weird question, but I extracted the executable from the DMG into a new folder and ran it there, and it completed fine, but where are the files now? The folder where I ran it from is still empty :')

https://github.com/ShaneBeeStudios/McDeob/wiki/macOS#output-files

Thanks!

you're welcome :)


Develop

The first iteration of hotkeys

I think this directive should be simple and clear with the following API:
<div hotkeys="meta.a" hotkeysDescription="" hotkeysGroup="" hotkeysOptions={the rest as object} (hotkey)="doSomething($event)">

Are you suggesting a single hotkey per element?

@flatstadt yes, let's start simple. We can add support later if someone requests it.

@flatstadt You can make the final changes, and finish with docs and specs. Great work.

We can proceed to write the documentation, and release the library.

ctrl should be control, please take care.

ctrl should be control, please take care.

Yeah. I noticed that too, sorry. I pushed a fix as soon as I did.

Merged and publish. Great work!  Subscribe to any issues or PRs.


Add support for doppler firehost logs

Addresses #17
Doppler firehose logs look like this:
<6>2015-03-17T01:24:23Z jumpbox.xxxxxxx.com doppler[6375]: {"cf_app_id":"b732c465-0536-4014-b922-165eb38857b2","level":"info","message_type":"OUT","msg":"Stopped app instance (index 0) with guid b732c465-0536-4014-b922-165eb38857b2","source_instance":"7","source_type":"DEA","time":"2015-03-17T01:24:23Z"}
<6>2015-03-17T01:22:43Z jumpbox.xxxxxxx.com doppler[6375]: {"cf_app_id":"ec2d33f6-fd1c-49a5-9a90-031454d1f1ac","level":"info","message_type":"OUT","msg":"cf-env-test.xxxxxxx.com - [17/03/2015:01:21:42 +0000] \"GET / HTTP/1.1\" 200 5087 \"-\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89 Safari/537.36\" <IP_ADDRESS>:45298 x_forwarded_for:\"<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>\" vcap_request_id:c66716aa-fef1-482f-55c3-133be3ed8de7 response_time:0.003644458 app_id:ec2d33f6-fd1c-49a5-9a90-031454d1f1ac\n","source_instance":"0","source_type":"RTR","time":"2015-03-17T01:22:43Z"}
<6>2015-03-17T01:22:43Z jumpbox.xxxxxxx.com doppler[6375]: {"cf_app_id":"ec2d33f6-fd1c-49a5-9a90-031454d1f1ac","level":"info","message_type":"ERR","msg":"<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS> - - [17/Mar/2015 01:21:42] \"GET / HTTP/1.1\" 200 5087 0.0022","source_instance":"0","source_type":"App","time":"2015-03-17T01:22:43Z"}
<6>2015-03-17T01:22:40Z jumpbox.xxxxxxx.com doppler[6375]: {"cf_app_id":"ec2d33f6-fd1c-49a5-9a90-031454d1f1ac","level":"info","message_type":"ERR","msg":"W, [2015-03-17T01:21:39.739322 #31] WARN -- : attack prevented by Rack::Protection::IPSpoofing","source_instance":"0","source_type":"App","time":"2015-03-17T01:22:40Z"}

Parse them!

@longnguyen11288, based on a helpful pointer from @simonjohansson, I have added filters for these 4 sample doppler messages.
Specifically:

source_type=DEA
<6>2015-03-17T01:24:23Z jumpbox.xxxxxxx.com doppler[6375]: {"cf_app_id":"b732c465-0536-4014-b922-165eb38857b2","level":"info","message_type":"OUT","msg":"Stopped app instance (index 0) with guid b732c465-0536-4014-b922-165eb38857b2","source_instance":"7","source_type":"DEA","time":"2015-03-17T01:24:23Z"}

becomes
'@message': '{"cf_app_id":"ec2d33f6-fd1c-49a5-9a90-031454d1f1ac","level":"info","message_type":"ERR","msg":"<IP_ADDRESS>,  <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS> - - [17/Mar/2015 01:21:42] \"GET / HTTP/1.1\"  200 5087 0.0022","source_instance":"0","source_type":"App","time":"2015-03-17T01:22:43Z"}'
'@timestamp': !ruby/object:LogStash::Timestamp
  time: 2015-03-17 01:22:43.000000000 Z
tags:
- syslog_standard
- cloudfoundry_doppler
<EMAIL_ADDRESS>jumpbox.xxxxxxx.com
cf_app_id: ec2d33f6-fd1c-49a5-9a90-031454d1f1ac
level: info
message_type: ERR
msg: <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS> - - [17/Mar/2015 01:21:42] "GET / HTTP/1.1" 200 5087 0.0022
source_instance: '0'
source_type: App
'@type': cloudfoundry_doppler

source_type=RTR
 <6>2015-03-17T01:22:43Z jumpbox.xxxxxxx.com doppler[6375]: {"cf_app_id":"ec2d33f6-fd1c-49a5-9a90-031454d1f1ac","level":"info","message_type":"OUT","msg":"cf-env-test.xxxxxxx.com - [17/03/2015:01:21:42 +0000] \"GET / HTTP/1.1\" 200 5087 \"-\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89 Safari/537.36\" <IP_ADDRESS>:45298 x_forwarded_for:\"<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>\" vcap_request_id:c66716aa-fef1-482f-55c3-133be3ed8de7 response_time:0.003644458 app_id:ec2d33f6-fd1c-49a5-9a90-031454d1f1ac\n","source_instance":"0","source_type":"RTR","time":"2015-03-17T01:22:43Z"}

becomes
 '@message': '{"cf_app_id":"ec2d33f6-fd1c-49a5-9a90-031454d1f1ac","level":"info","message_type":"OUT","msg":"cf-env-test.xxxxxxx.com  - [17/03/2015:01:21:42 +0000] \"GET / HTTP/1.1\" 200 5087 \"-\" \"Mozilla/5.0 (Macintosh;  Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89  Safari/537.36\" <IP_ADDRESS>:45298 x_forwarded_for:\"<IP_ADDRESS>, <IP_ADDRESS>,  <IP_ADDRESS>, <IP_ADDRESS>\" vcap_request_id:c66716aa-fef1-482f-55c3-133be3ed8de7 response_time:0.003644458 app_id:ec2d33f6-fd1c-49a5-9a90-031454d1f1ac\n","source_instance":"0","source_type":"RTR","time":"2015-03-17T01:22:43Z"}'
 '@timestamp': !ruby/object:LogStash::Timestamp
   time: 2015-03-17 01:21:42.000000000 Z
 tags:
 - syslog_standard
 - cloudfoundry_doppler
<EMAIL_ADDRESS>jumpbox.xxxxxxx.com
 cf_app_id: ec2d33f6-fd1c-49a5-9a90-031454d1f1ac
 level: info
 message_type: OUT
 source_instance: '0'
 source_type: RTR
 hostname: cf-env-test.xxxxxxx.com
 verb: GET
 path: /
 http_spec: HTTP/1.1
 status: 200
 body_bytes_sent: 5087
 referer: '-'
 http_user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89 Safari/537.36
 x_forwarded_for:
 - <IP_ADDRESS>
 - <IP_ADDRESS>
 - <IP_ADDRESS>
 - <IP_ADDRESS>
 vcap_request_id: c66716aa-fef1-482f-55c3-133be3ed8de7
 response_time: 0.003644458
 remote_addr: <IP_ADDRESS>
 geoip:
   ip: <IP_ADDRESS>
   country_code2: US
   country_code3: USA
   country_name: United States
   continent_code: NA
   region_name: CA
   city_name: Westlake Village
   postal_code: '91361'
   latitude: 34.14439999999999
   longitude: -118.8935
   dma_code: 803
   area_code: 805
   timezone: America/Los_Angeles
   real_region_name: California
   location:
   - -118.8935
   - 34.14439999999999
 '@type': cloudfoundry_doppler

message_type=ERR
 <6>2015-03-17T01:22:43Z jumpbox.xxxxxxx.com doppler[6375]: {"cf_app_id":"ec2d33f6-fd1c-49a5-9a90-031454d1f1ac","level":"info","message_type":"ERR","msg":"<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS> - - [17/Mar/2015 01:21:42] \"GET / HTTP/1.1\" 200 5087 0.0022","source_instance":"0","source_type":"App","time":"2015-03-17T01:22:43Z"}

becomes
 '@message': '{"cf_app_id":"ec2d33f6-fd1c-49a5-9a90-031454d1f1ac","level":"info","message_type":"ERR","msg":"W, [2015-03-17T01:21:39.739322 #31] WARN -- : attack prevented by Rack::Protection::IPSpoofing","source_instance":"0","source_type":"App","time":"2015-03-17T01:22:40Z"}'
 '@version': '1'
 '@timestamp': !ruby/object:LogStash::Timestamp
   time: 2015-03-17 01:22:40.000000000 Z
 received_at: '2015-03-18T10:27:20.308Z'
 received_from: '%{host}'
 tags:
 - syslog_standard
 - cloudfoundry_doppler
<EMAIL_ADDRESS>jumpbox.xxxxxxx.com
 cf_app_id: ec2d33f6-fd1c-49a5-9a90-031454d1f1ac
 level: info
 message_type: ERR
 msg: 'W, [2015-03-17T01:21:39.739322 #31] WARN -- : attack prevented by Rack::Protection::IPSpoofing'
 source_instance: '0'
 source_type: App
 '@type': cloudfoundry_doppler

Thoughts?

Nice one!

@longnguyen11288, @drnic - Doesn't doppler also give us some metrics logs?
If so, could you give me some sample metrics logs and I'll add parsing for them to this PR

David they do but the firehose to syslog doesn't support it yet. I want to
boshify that app and deploy it with your changes as first mvp. Then slowly
start adding more firehose data.
On 19 Mar 2015 01:36, "David Laing"<EMAIL_ADDRESS>wrote:

@longnguyen11288 https://github.com/longnguyen11288, @drnic
https://github.com/drnic - Doesn't doppler also give us some metrics
logs?
If so, could you give me some sample metrics logs and I'll add parsing for
them to this PR
—
Reply to this email directly or view it on GitHub
https://github.com/logsearch/logsearch-for-cloudfoundry/pull/18#issuecomment-83419152
.

I could add support to firehose to syslog for metrics data if this is something you would want to consume!

@simonjohansson - That would be great, thank you!

Hey all.
https://github.com/SpringerPE/firehose-to-syslog/pull/3
So I added initial scaffolding to support this, just wanted a sanity check before going further.

I'm not very familiar with Go, if anyone has any critique about my code please give me feedback as I'm sure this is not idiomatic.
From logsearch perspective, would you rather get the data in format of

{
   "event_type":"ValueMetric",
   "level":"info",
   "msg":"",
   "origin":"syslog_drain_binder",
   "name": "memoryStats.numFrees",
   "time":"2015-03-19T15:40:11+01:00",
   "unit":"count",
   "value":3.853421e+06
}

or (.Info(valueMetric.String()) in LogValueMetric)
{
   "event_type":"ValueMetric",
   "level":"info",
   "msg":"name:\"memoryStats.numFrees\" value:3.853421e+06 unit:\"count\" ",
   "origin":"syslog_drain_binder",
   "time":"2015-03-19T15:40:11+01:00"
}

Currently I am not sure how to get exact host data for an event, we know that the event is for memoryStats.numFrees, but on which host? I might be missing something.

@simonjohansson - I can't comment on whether your Go is idiomatic, sorry :(
As for which format - the first
{
   "event_type":"ValueMetric",
   "level":"info",
   "msg":"",
   "origin":"syslog_drain_binder",
   "name": "memoryStats.numFrees",
   "time":"2015-03-19T15:40:11+01:00",
   "unit":"count",
   "value":3.853421e+06
}

is much easier to parse (its just a json filter).
As for host data - would this not be attached to a cf_app_id + instance #, rather than a host?

@mrdavidlaing

is much easier to parse (its just a json filter).

Yep, the downside is that we need to keep firehose-to-syslog closely up to date in case of new fields being introduced(as opposed to  valueMetric.String() where we would just get extra data for free).
Also we might end up killing backwards comparability. If a new field is introduced in say cf 205, we update f-to-s to cater for that we would end up having runtime exceptions for people using < 205, this would easily be fixed with some branching, but then the risk is big that f-to-s become a big if then else clusterfuck. :)
But yeah, I'm in favor to keep as much logic as possible out of grok patterns as it tends to be quirky at best to debug and write.

As for host data - would this not be attached to a cf_app_id + instance #, rather than a host?

AppId and SourceInstance is only defined for LogMessage, and LogMessage in the envelope is nil for ValueMetric. I must be missing something, but Ill have a closer look tomorrow.
https://github.com/cloudfoundry/noaa/blob/master/events/log.pb.go#L49
https://github.com/cloudfoundry/noaa/blob/master/events/metric.pb.go#L15

Ehm, git push -f gone wrong. I accidentally removed all the scaffolding in SpringerPE/firehose-to-syslog#3 . Oh well. Tomorrow is a new day.

@simonjohansson - naughty!  That will teach you to playing with sharp tools at the end of a work day :grinning:

Thank you @simonjohansson for adding metrics!

On Mar 19, 2015, at 2:00 PM, David Laing<EMAIL_ADDRESS>wrote:
@simonjohansson

naughty! That will teach you to playing with sharp tools at the end of a work day

—
Reply to this email directly or view it on GitHub
.

@longnguyen11288 no worries.
I quickly added the lost code back.

@simonjohansson - I've been playing with a dashboards to visualise the LogMessage and ValueMetric values based on cf v205.

As you can see, the data in LogMessage is quite rich; you can drill down by cf_app_id and analyse the data from each component quite nicely
ValueMetric doesn't seem as interesting - as far as I can tell this currently only has data for system components (eg, router, LoggregatorTrafficController etc)
I was kind hopeing to be able to get my hands on some "container level host metrics" for each app's container; eg CPU / RAM usage for a specific app / instance.
Any luck finding those?

@mrdavidlaing aren't those "container level host metrics" only exposed in diego?

@rkoster - Aha - thanks for pointing that out.
Guess I'd better spin up a diego-release and have a look at what those look like

@mrdavidlaing sorry, have had no time to look further into the extra events.
And currently Im waiting for the diego team to create working templates for vSphere so I can play with it.

@mrdavidlaing this is exciting! does the firehose to syslog ingestor still need to be written? do you need any help on this effort?

@longnguyen11288 the firehose to syslog ingestor probably needs lots of changes to support the new metrics exposed by diego. Currently the "stable" release only sends RTR and APP logs for applications.
I happely accept PRs :)

Should we start off with RTR and App logs so we have initial bosh job written then update when we figure out diego.

Long,
Simon has already done the initial firehost to syslog work in
https://github.com/SpringerPE/firehose-to-syslog/pull/3 - the dashboards
above are using data piped through the current version of same.
My plan for tomorrow is to wrap firehost-to-syslog in its own bosh release
so it can easily be added to an existing CF / Logsearch cluster.
Is there any chance you could host an integration environment for us to
test/share links to?  Perhaps based on Logsearch-boshworkspace?
Extra points if you could include Diego in the mix, since it seems that it
has much richer firehost events.
On Monday, March 30, 2015, Long Nguyen<EMAIL_ADDRESS>wrote:

Should we start off with RTR and App logs so we have initial bosh job
written then update when we figure out diego.
—
Reply to this email directly or view it on GitHub
https://github.com/logsearch/logsearch-for-cloudfoundry/pull/18#issuecomment-87689826
.

--
David Laing
logsearch.io - build your own open source cloud logging cluster
http://davidlaing.com

@mrdavidlaing if you want to pack up something that is known to work(and in master)
https://github.com/SpringerPE/firehose-to-syslog/releases/tag/0.0.1
Might be a good candidate for a first release whilst we are looking at adding more events + trying with diego?

Good idea
On Monday, March 30, 2015, Simon Johansson<EMAIL_ADDRESS>wrote:

@mrdavidlaing https://github.com/mrdavidlaing if you want to pack up
something that is known to work(and in master)
https://github.com/SpringerPE/firehose-to-syslog/releases/tag/0.0.1
Might be a good candidate for a first release whilst we are looking at
adding more events + trying with diego?
—
Reply to this email directly or view it on GitHub
https://github.com/logsearch/logsearch-for-cloudfoundry/pull/18#issuecomment-87724968
.

--
David Laing
logsearch.io - build your own open source cloud logging cluster
http://davidlaing.com

Will look into it, I havent tried to run diego in a while and it was only in bosh-lite so I'll try getting it on AWS

Great!
On Monday, March 30, 2015, Long Nguyen<EMAIL_ADDRESS>wrote:

Will look into it, I havent tried to run diego in a while and it was only
in bosh-lite so I'll try getting it on AWS
—
Reply to this email directly or view it on GitHub
https://github.com/logsearch/logsearch-for-cloudfoundry/pull/18#issuecomment-87769313
.

--
David Laing
logsearch.io - build your own open source cloud logging cluster
http://davidlaing.com

Would extending the logsearch-boshworkspace with diego support not be enough for integration purposes?

I think having a shares test environment we can all see with common data
would be helpful.
On Monday, March 30, 2015, Ruben Koster<EMAIL_ADDRESS>wrote:

Would extending the logsearch-boshworkspace
https://github.com/cloudfoundry-community/logsearch-boshworkspace with
diego support not be enough for integration purposes?
—
Reply to this email directly or view it on GitHub
https://github.com/logsearch/logsearch-for-cloudfoundry/pull/18#issuecomment-87773403
.

--
David Laing
logsearch.io - build your own open source cloud logging cluster
http://davidlaing.com

Bosh-lite can be shared. Just saying using bosh-lite would mean we can move quickly otherwise we might get blocked by waiting on a integration environment.

A shared bosh-lite would work fine too

https://github.com/SpringerPE/firehose-to-syslog/pull/4
PR from malston to support all the events in a much nicer way.

@simonjohansson - https://github.com/SpringerPE/firehose-to-syslog/pull/4 looks like it fixes the problem I was having with missing Godeps during when compiling firehose-to-syslog in the logsearch-for-cloudfoundry-boshrelease too.
Do you have a timeline for merging PR#4?

@mrdavidlaing currently not as there seems to be some issue with missing(?) events.
As soon as that is ironed out I will merge.

Great.  It isn't a blocker for me; just a bit of hackiness in the logsearch-for-cloudfoundry-boshrelease I'd like to clean up after you merge

Indeed. Im looking at this atm, I dont fully understand how this could happen.
But as soon as I find out I will publish a 0.0.2 which fixes this so you dont have to have evil hacks in the relase :)

@mrdavidlaing https://github.com/SpringerPE/firehose-to-syslog/releases/tag/0.0.2

@longnguyen11288, @simonjohansson, @rkoster, @drnic
I've created a custom bosh-release that deploys firehost-to-syslog to "connect" a CF deployment (v205) to a Logsearch cluster.  Installation instructions as below.
Feedback welcomed!

Adding to an existing Cloud Foundry + Logsearch deployments
This has been tested on cf-release v205 and logsearch-boshrelease v19.

Deploy the ingestor_cloudfoundry job to your existing logsearch deployment.

bosh upload release https://logsearch-for-cloudfoundry-boshrelease.s3.amazonaws.com/boshrelease-logsearch-for-cloudfoundry-0%2Bdev.3.tgz

Add and configure the ingestor_cloudfoundry job to your logsearch deploy manifest:
releases:
- name: logsearch-for-cloudfoundry
version: latest
   jobs:
     - name: ingestor_cloudfoundry
       release: logsearch-for-cloudfoundry
       templates:
       - name: ingestor_cloudfoundry-firehose
       instances: 1
       resource_pool: small_z1
       networks: z1
       persistent_disk: 0

   properties:
       ingestor_cloudfoundry-firehose:
         debug: true
         uua-endpoint: "https://uaa.<IP_ADDRESS>.xip.io/oauth/authorize"
         doppler-endpoint: "wss://doppler.<IP_ADDRESS>.xip.io"
         skip-ssl-validation: true
         firehose-user: admin
         firehose-password: admin
         syslog-server: "<IP_ADDRESS>:514"

Include logsearch-for-cloudfoundry/logstash-filters-default.conf log_parsing rules
    properties:
      logstash_parser:
      <% filtersconf = File.join(File.dirname(File.expand_path(__FILE__)), 'path/to/logsearch-for-  cloudfoundry/logstash-filters-default.conf') %>
         filters: |
               <%= File.read(filtersconf).gsub(/^/, '            ').strip %>

bosh deploy

All app logs from your CF deployment should now be forwarded into your logsearch cluster.  Find them by searching for @type:cloudfoundry_doppler.  Make useful dashboards like the below:

@mrdavidlaing cool! Ill give it a go,
about the logsearch release for warden, https://github.com/logsearch/logsearch-boshrelease/blob/develop/examples/bosh-lite.yml have not been updated for 2 months, is it still valid?

Gimme a sec, I'll grab you a copy of my working manifest
On Tuesday, March 31, 2015, Simon Johansson<EMAIL_ADDRESS>wrote:

@mrdavidlaing https://github.com/mrdavidlaing cool! Ill give it a go,
about the logsearch release for warden,
https://github.com/logsearch/logsearch-boshrelease/blob/develop/examples/bosh-lite.yml
have not been updated for 2 months, is it still valid?
—
Reply to this email directly or view it on GitHub
https://github.com/logsearch/logsearch-for-cloudfoundry/pull/18#issuecomment-88083112
.

--
David Laing
logsearch.io - build your own open source cloud logging cluster
http://davidlaing.com

Thanks, also, I might be silly, but I cannot find logsearch 19. Did you forget to push the 19 release to the repo?

@simonjohansson - My bad; I'm working from dev versions that haven't been officially published (due to a performance issue with logstash 1.5.rc2)
Here is a gist that should give you enough to replicate my bosh-lite dev environment:
https://gist.github.com/mrdavidlaing/ccbe48657b8cfcf6b3eb

@mrdavidlaing do you want me to try to deploy this on shared cf?

Long,
If you're up for it (and can follow my total lack of instructions)
If you get stuck just let me know, and I'll do it tomorrow - the
installation process is definitely still touch around the edges.
On Tuesday, March 31, 2015, Long Nguyen<EMAIL_ADDRESS>wrote:

@mrdavidlaing https://github.com/mrdavidlaing do you want me to try to
deploy this on shared cf?
—
Reply to this email directly or view it on GitHub
https://github.com/logsearch/logsearch-for-cloudfoundry/pull/18#issuecomment-88100553
.

--
David Laing
logsearch.io - build your own open source cloud logging cluster
http://davidlaing.com

It all works over here, super smooth! (Well, I had a issue with ipv6 in the ingestor node, dunno if that is related to my setup yet..)

Ill leave it up to you, let me know if you need any help

Now that we have a "working" shared test setup; I'm going to merge this PR and call what we have v1


Filetree rework complete

The filetree rework should be finished. Code has been updated on the side, complete with LF line endings, newer data, removed double-files, etc.

Big update for undertaker; scripts and documentation has been sorted, code has been upgraded, and numerous fixed have occurred. This should be a stable release but is yet to be tested, so another update must follow to cement this progress.


feat: Onboarding improvements (country picker + Authorize buttons)

Hi everyone,
In the onboarding, there are two visuals issues:

The country picker doesn't have any padding any more (+ the dialog doesn't have any Scrollbar, nor correct padding)
The Authorize button have an invisible InkWell (white on white)

Here is a video of the country picker:
CountryPicker.webm
(I've there is no regression on other screens)

Codecov Report

Merging #4291 (7302787) into develop (965ee71) will increase coverage by 0.00%.
The diff coverage is 8.57%.

@@           Coverage Diff            @@
##           develop    #4291   +/-   ##
========================================
  Coverage    10.87%   10.88%
========================================
  Files          285      285
  Lines        14172    14181    +9
========================================
+ Hits          1541     1543    +2
- Misses       12631    12638    +7

Impacted Files
Coverage Δ

...oth_app/lib/pages/onboarding/country_selector.dart
0.82% <0.00%> (-0.03%)
:arrow_down:

...pp/lib/pages/onboarding/onboarding_bottom_bar.dart
0.00% <0.00%> (ø)

.../smooth_app/lib/pages/onboarding/welcome_page.dart
0.00% <ø> (ø)

...p/lib/generic_lib/dialogs/smooth_alert_dialog.dart
88.37% <100.00%> (+0.18%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks for your review @monsieurtanuki.
Let's merge this and decrease the number of pending PRs 🤓


Bump utils-java dependency.

LGTM

Coverage remained the same at 19.841% when pulling 946cd3b045d8474370c8d174a59ab93ac813cfd6 on deflaux:master into ccf9ce40120ea397a76694a2401a66bef75b1f62 on googlegenomics:master.

Coverage remained the same at 19.841% when pulling 946cd3b045d8474370c8d174a59ab93ac813cfd6 on deflaux:master into ccf9ce40120ea397a76694a2401a66bef75b1f62 on googlegenomics:master.


Hotfix for #188

Should fix #188

This worked for me. 😄
changed to
with open(path, 'rb') as f:

thanks!


The nether and end use the bed will not explode properly

minecraft version:1.12.2
mod version:1.12.5
forge version:<IP_ADDRESS>60
Running this mod alone found that the bed doesn't explode in the above two worlds, and the config file doesn't see the switch about this event?
It's so strange that no one has ever found out about the problem

1.12 is not supported


Added Vector Calculator Files

Description
Added Vector Calculator Python app Files
Issue
Fixes #50
PR made under GSSoC'22 contributions

@heet-kumar Done.

@XZANATOL make that change which i have mentioned in other PR in these to also.

@heet-kumar Done.

@heet-kumar Markdown doesn't support embedding local videos, maybe online ones but not locals. the last commint you commented on was working on my local machine as I was using an HTML tag & I thought it would work. See this image for more details

I'm going to revert back to the commit where I had the video uploaded online, and don't worry it won't be removed anyways as this GDrive is made mainly for my opensource projects.

@heet-kumar Gonna make the same with the other PR.

@XZANATOL it is possible adding video if you want some refrence that there are some already PR there they have added videos. See in this PR #93 .

@heet-kumar Done.


🏀  Baller maintenance page 🏀

Adding a maintenance page template that looks like our 404 page.
Started with the 404 page HTML and then made a bunch of small changes.  Second commit is probably the most interesting one. Also did some magic behind the scenes to crunch down all that CSS, but it's still gonna weigh in at ~2000 lines.  (aside: our reset CSS rules are repeated 8(!) times in our compiled application.css. 😱 )
@tracy-content's had a look at this, so I've removed the WIP.
current screenshot

Note
I've created a repository that does all of the CSS munging.  If you want to update the maintenance page or create more static pages with our Digital Marketplace styles, it's a good place to start.  Find it here: https://github.com/alphagov/digitalmarketplace-maintenance

Is there a separate page for when we take things down for a long time?

Nope. This is it, Kev.

Could there be a script which generates this based on some template plus the shared CSS? Seems like it would be nice if this could update automatically if we change our styles.

Should we drop the word "short" then? Or are we optimistic about being able to recover quickly from any unforseen disaster?

@galund, I have a local repo that automates some of the process of getting the styles into the page but not all of it. Happy to share it more widely.
Specifically, the steps are:

Copy + paste the compiled CSS from the buyer app
Run a script to cut down all the CSS rules
Copy + paste the compiled CSS into the  page<head>

Changing the words and the links to gov.uk assets is all manual.

As to your specific point, my feeling is that this page probably will rarely change because it will even less rarely be used. I would assume it's probably less time to do the manual steps once in a blue moon than to write more code to automate creating more of this page.

Yeah, if you've got code, then add a note to the readme file here, and put some more detail into the readme for your new repo? Seems like a worthwhile thing to have exist, even if it's only a partial solution and some of the steps are manual.

@galund, Hey, I've pushed up my repo. Look for it here: https://github.com/alphagov/digitalmarketplace-maintenance
@TheDoubleK, Hey Kev, Alexey says that the "shortly" is fine because we're not expecting to have this page up for more than a day at any point.

Think you could do with adding a more current screenshot with the new content.

 Maintenance page html file

I think this is probably ready to go 👍


Error undefined reference to unhexlify

Hello,
I got an error when using the library.
Here my environment:

Ubuntu 18.04
cmake version 3.10.2
g++ (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0

cpp test file:
#include <iostream>
#include "OpenPGP.h"
int main()
{
  std::cout << "Hello, \n";
  return 1;
}

Then build the test.cpp :
g++ -Wall -g -std=c++11 test.cpp
Finally, i got the error:

/tmp/cccmQHCv.o: In function __static_initialization_and_destruction_0(int, int)': /usr/local/include/Encryptions/Camellia_Const.h:33: undefined reference to unhexlify(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)'
/usr/local/include/Encryptions/Camellia_Const.h:33: undefined reference to unhexlify(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /usr/local/include/Encryptions/Camellia_Const.h:33: undefined reference to unhexlify(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)'
/usr/local/include/Encryptions/Camellia_Const.h:33: undefined reference to unhexlify(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /usr/local/include/Encryptions/Camellia_Const.h:33: undefined reference to unhexlify(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)'
/tmp/cccmQHCv.o:/usr/local/include/Encryptions/Camellia_Const.h:33: more undefined references to `unhexlify(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)' follow
collect2: error: ld returned 1 exit status

Any help?

Hi. You have to link against the library. Assuming your build is in <OpenPGP>/build, you have to compile with g++ -Wall -g -std=c++11 test.cpp -L<OpenPGP>/build -lOpenPGP.

Thank you @calccrypto ,
You save my life :)


AzureDNS Provider Issue - 'ServicePrincipalCredentials' object has no attribute 'get_token'

Hi,
I have an old working octodns 9.10 install on a python27 env - that manages a zone on a split-auth dns across aws and azure
I have now built a new platform to replace the above with octodns 9.14 on a python39 env and ported the config files across from the old env.
Have updated the setup for the new octodns_azure.AzureProvider provider (old setup is using octodns.provider.azuredns.AzureProvider)
Octodns read type actions on the new setup appear to work ok (eg on say an octodns-sync dry run etc)
But write actions (eg on an octodns-sync --doit to update a zone) ends up with a failure on the azure target (works fine on the route53 target) - the Azure failure is flagged with the following: -
   AttributeError: 'ServicePrincipalCredentials' object has no attribute 'get_token'

I know the Azure libraries for Python have undergone rework in the past couple of years
Where ServicePrincipalCredentials in the azure.common lib was used for authentication previously but that's been replaced with the azure-identity library (?)
Has anyone got any pointers on what the problem is here / where it may lay ?
My ~config.yaml file is: -
manager:
  max_workers: 2

providers:
  config:
    class: octodns.provider.yaml.YamlProvider
    directory: .\test-zone
    default_ttl: 3600
    enforce_order: True
  azuredns:
    class: octodns_azure.AzureProvider
    client_id:  env/AZURE_CLIENT_ID
    key: env/AZURE_KEY
    directory_id: env/AZURE_DIRECTORY_ID
    sub_id: env/AZURE_SUB_ID
    resource_group: env/AZURE_RESOURCE_GROUP
  route53:
    class: octodns_route53.Route53Provider
    access_key_id: env/AWS_ACCESS_KEY_ID
    secret_access_key: env/AWS_SECRET_ACCESS_KEY

zones:
  abcdefg.net.:
    sources:
      - config
    targets:
      - azuredns
      - route53

What is seen when doing a octodns-sync --doit that will involve a zone change, is as follows: -

2022-01-29T12:26:58  [9364] INFO  Manager __init__: config_file=abcdefg-test-config.yaml
2022-01-29T12:26:58  [9364] INFO  Manager __init__:   max_workers=2
2022-01-29T12:26:58  [9364] INFO  Manager __init__:   include_meta=False
2022-01-29T12:26:59  [9364] INFO  Manager sync: eligible_zones=[], eligible_targets=[], dry_run=False, force=False, plan_output_fh=<stdout>
2022-01-29T12:26:59  [9364] INFO  Manager sync:   zone=abcdefg.net.
2022-01-29T12:26:59  [9364] INFO  Manager sync:   sources=['config'] -> targets=['azuredns', 'route53']
2022-01-29T12:26:59  [5208] INFO  YamlProvider[config] populate:   found 125 records, exists=False

2022-01-29T12:26:59  [5208] INFO  AzureProvider[azuredns] plan: desired=abcdefg.net.
2022-01-29T12:26:59  [5208] INFO  azure.identity._internal.get_token_mixin ClientSecretCredential.get_token succeeded
2022-01-29T12:27:01  [5208] INFO  AzureProvider[azuredns] populate: found 126 records, exists=True
2022-01-29T12:27:01  [5208] INFO  AzureProvider[azuredns] plan:   Creates=0, Updates=1, Deletes=0, Existing Records=126

2022-01-29T12:27:01  [5208] INFO  Route53Provider[route53] plan: desired=abcdefg.net.
2022-01-29T12:27:03  [5208] INFO  Route53Provider[route53] populate:   found 126 records, exists=True
2022-01-29T12:27:03  [5208] INFO  Route53Provider[route53] plan:   Creates=0, Updates=1, Deletes=0, Existing Records=126

2022-01-29T12:27:03  [9364] INFO  Manager
********************************************************************************
* abcdefg.net.
********************************************************************************
* azuredns (AzureProvider)
*   Update
*     <ARecord A 300, tell.abcdefg.net., ['<IP_ADDRESS>']> ->
*     <ARecord A 300, tell.abcdefg.net., ['<IP_ADDRESS>']> (config)
*   Summary: Creates=0, Updates=1, Deletes=0, Existing Records=126

* route53 (Route53Provider)
*   Update
*     <ARecord A 300, tell.abcdefg.net., ['<IP_ADDRESS>']> ->
*     <ARecord A 300, tell.abcdefg.net., ['<IP_ADDRESS>']> (config)
*   Summary: Creates=0, Updates=1, Deletes=0, Existing Records=126
********************************************************************************

2022-01-29T12:27:03  [9364] INFO  AzureProvider[azuredns] apply: making 1 changes to abcdefg.net.
Traceback (most recent call last):
  File "C:\Program Files\Python39\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Program Files\Python39\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Program Files\Python39\Scripts\octodns-sync.exe\__main__.py", line 7, in <module>
  File "C:\Program Files\Python39\lib\site-packages\octodns\cmds\sync.py", line 38, in main
    manager.sync(eligible_zones=args.zone, eligible_sources=args.source,
  File "C:\Program Files\Python39\lib\site-packages\octodns\manager.py", line 468, in sync
    total_changes += target.apply(plan)
  File "C:\Program Files\Python39\lib\site-packages\octodns\provider\base.py", line 181, in apply
    self._apply(plan)
  File "C:\Program Files\Python39\lib\site-packages\octodns_azure\__init__.py", line 1513, in _apply
    getattr(self, f'_apply_{class_name}')(change)
  File "C:\Program Files\Python39\lib\site-packages\octodns_azure\__init__.py", line 1437, in _apply_Update
    profile = self._get_tm_for_dynamic_record(new)
  File "C:\Program Files\Python39\lib\site-packages\octodns_azure\__init__.py", line 636, in _get_tm_for_dynamic_record
    return self._get_tm_profile_by_name(name)
  File "C:\Program Files\Python39\lib\site-packages\octodns_azure\__init__.py", line 632, in _get_tm_profile_by_name
    return self._get_tm_profile_by_id(profile_id)
  File "C:\Program Files\Python39\lib\site-packages\octodns_azure\__init__.py", line 621, in _get_tm_profile_by_id
    self._populate_traffic_managers()
  File "C:\Program Files\Python39\lib\site-packages\octodns_azure\__init__.py", line 605, in _populate_traffic_managers
    for profile in list_profiles(self._resource_group):
  File "C:\Program Files\Python39\lib\site-packages\azure\core\paging.py", line 129, in __next__
    return next(self._page_iterator)
  File "C:\Program Files\Python39\lib\site-packages\azure\core\paging.py", line 76, in __next__
    self._response = self._get_next(self.continuation_token)
  File "C:\Program Files\Python39\lib\site-packages\azure\mgmt\trafficmanager\operations\_profiles_operations.py", line 413, in get_next
    pipeline_response = self._client._pipeline.run(request, stream=False, **kwargs)
  File "C:\Program Files\Python39\lib\site-packages\azure\core\pipeline\_base.py", line 211, in run
    return first_node.send(pipeline_request)  # type: ignore
  File "C:\Program Files\Python39\lib\site-packages\azure\core\pipeline\_base.py", line 71, in send
    response = self.next.send(request)
  File "C:\Program Files\Python39\lib\site-packages\azure\core\pipeline\_base.py", line 71, in send
    response = self.next.send(request)
  File "C:\Program Files\Python39\lib\site-packages\azure\core\pipeline\_base.py", line 71, in send
    response = self.next.send(request)
  [Previous line repeated 2 more times]
  File "C:\Program Files\Python39\lib\site-packages\azure\mgmt\core\policies\_base.py", line 47, in send
    response = self.next.send(request)
  File "C:\Program Files\Python39\lib\site-packages\azure\core\pipeline\policies\_redirect.py", line 158, in send
    response = self.next.send(request)
  File "C:\Program Files\Python39\lib\site-packages\azure\core\pipeline\policies\_retry.py", line 445, in send
    response = self.next.send(request)
  File "C:\Program Files\Python39\lib\site-packages\azure\core\pipeline\policies\_authentication.py", line 117, in send
    self.on_request(request)
  File "C:\Program Files\Python39\lib\site-packages\azure\core\pipeline\policies\_authentication.py", line 94, in on_request
    self._token = self._credential.get_token(*self._scopes)
AttributeError: 'ServicePrincipalCredentials' object has no attribute 'get_token'

thanks in advance,
Chris

I can reproduce this. This is likely because azure-identity was bumped when the provider was extracted to separate repo in https://github.com/octodns/octodns/pull/833 (2nd commit in this repo had a newer version https://github.com/octodns/octodns-azure/blob/f4274f1a4c3ccb910ad5b101a35fe0f2b5841fa1/requirements.txt#L7).
I'll work on a fix for this.


Add some examples

#3
Add some examples.
Not sure if it can meet the requirement as a beginner，just try to help.
Notice that some red log output appeared when I call those function, like create an address will print a array contains binary nums  thought it is bad for examples so I removed those print statement。
Remove the .vscode directory. Cause I am using golang, so I add the “.idea” in .gitignore.
PS: I dont’ know the convention of golang file name, so I follow your name rule, but it looks bad to me to not use the camel case or the snake case.
Thanks!

Hi @lunaticf,
Thanks for your contribution!!!! Bonus point on removing .vscode, you can take it a step further by adding it to .gitignore, I should have added it to .gitignore from day one.
I'm sure it will get us in the right direction and any help at all is welcome!. Once I review it I will let you know if anything needs to be adjusted.
Thanks again for your contribution.

Hi @Lunaticf,
I have reviewed and approve the PR. The examples were neat and straight forward.
Currently working on Transactions History and Get Transaction Details by Sequence. I will let you know once I'm done if you will be kind enough to also write examples for it :).
Thanks so much for your contribution. Hope to see more PR from you.

@codemaveric
Thanks，This is encouragement to me. Will continue to contribute，hope to help more than examples.

You're welcome @Lunaticf
Yeah, there are other things you can contribute aside examples.
List of things in my pipeline

Get Transaction History
Get Transaction Details with Seq No
Test - It's bad that we don't have any test at all
Code Documentation using GoDoc

I'm already working on 1 and 2. It will be nice if you can pick either the testing or documentation. If you have anything else you feel we should implement, lemme know and we can decide to add it.
Regards

@codemaveric ok, I will implement some stuff in my spare time and check what else we can do


HotFix for bug with new users without subscription.json

https://community.smartthings.com/t/mqtt-bridge-device-app/37466/10?u=stjohn
Created https://github.com/stjohnjohnson/smartthings-mqtt-bridge/issues/14 as a remediation to prevent this stuff

Merging to fix broken users


BLD: unify c_args for Cython-generated code, silence %zd warnings

xref gh-118

Okay, this worked - all %zd warnings are gone. And it also adds a simple way to add another build flag for Cython-generated C code if needed.
FYI @matthew-brett.


chore: custom layout order example notebook

Example notebook to visualise and reorder the elements in a DocumentLayout. This solves the problem for Federal Regulation documents but is far from being a general solution. It works as an example of customisation for order and visualisation of the elements in a page layout.pages[i].elements of a DocumentLayout object in unstructured_inference.inference.layout and as a base for further work into a general solution for reordering elements in multiple-column textual-images.

Seems very good, will open a PR implementing this strategy.


Add thread size filter to search command

there are some cases I've bumped into, where having something like
search --thread-size=1 or --thread-size=1-2 would be useful.

May also want a way to specify (same or different option) that there are multiple messages in the thread, sent by separate addresses.
This helps find messages sent by a bot, but then replied to by someone else manually.

Resolving with c769485672eb38b8053f536b1a4d7e864f4f477a
Does not support specific message lengths, just 1 or greater than 1, but that should be fine in most use cases.


Fix: Wrong link in online readme

Oops, looks like I forgot a hardcoded href in the landing page:
https://github.com/maormagori/wizdom-stremio-v2/blob/e86faf562216773aa02a899d8b025e3b43e7a053/landingTemplate.js#L268
I guess it's fine to keep it hardcoded but switch it to the correct one.

Fixed in #25 and #26


Jump 021

This closes #52 and removes all associated deprecation warnings

Note for reviews: ignore the changes in notebooks, only script and src changes matter


Browser Support Error

Hello! Today I got this error although I have enabled less secure apps in google account:
"You're using a browser that Google doesn't recognize or that's set up in a way we don't support."

Same error

I'm having the same issue, using Windows 10.

For the past week the client has been hanging at launch - maybe this is a different manifestation of the same error?

This is still a problem, unable to sign in on Windows 10 after a google password change.

I'm also still having this issue

This issue still exists.

I believe this was solved in one of the previous version. Closing it.
Please open a new one if it still persists. Better yet would be a pull request.


Cassandra-12937 sstable compression

Added code to set sstable compression option in the conf.yaml file.
Original static CompressionParms.DEFAULT configuration moved to CompressionParams.defaultCompression()
Added DatabaseDescriptor.getSstableCompression() and called it in place of the original CompressionParams.DEFAULT
Added test to verify that CompressionParams is properly constructed from the Config.sstable_compressor
Fixes: CASSANDRA-12937
Associated pull: https://github.com/apache/cassandra/pull/2254

please remove the unrelated code formatting first

@michaelsembwever requested changed made

@michaelsembwever do you have any further comments on this pull request?

thank you @Claudenw , I will take a look shortly.

No longer current


Update maragung.toml

Previous PR:
https://github.com/anoma/namada-testnets/pull/1715
https://github.com/anoma/namada-testnets/blob/main/namada-public-testnet-14/maragung.toml
https://github.com/anoma/namada-testnets/blob/main/namada-public-testnet-15_legacy/maragung.toml
Description
All previous genesis validators should name their PRs "Update {validator_alias}.toml for tesntet-15" and provide links to previous PRs merged.
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present
[ ] The email, discord, elements telegram, and twitter fields are present and valid

Successfully validated transactions.toml file for commit hash c09c669


Handling S3 connection drops

There are some operations where S3 streams data to us to keep a connection alive while waiting for a long running operation to complete. In cases where the client drops the connection or has other intermittent network connection issues, we need to be more resilient.
This patch will attempt to retry these cases where they're recoverable, and prompt the client application to retry the operation again if we're unable to recover. This will also avoid leaking exceptions from the underlying xml library which we'd been doing before in these rare cases.

Codecov Report

Merging #2033 into develop will decrease coverage by 0.10%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop    #2033      +/-   ##
===========================================
- Coverage    92.99%   92.88%   -0.11%
===========================================
  Files           60       60
  Lines        10797    10673     -124
===========================================
- Hits         10041     9914     -127
- Misses         756      759       +3

Impacted Files
Coverage Δ

botocore/parsers.py
99.79% <ø> (-0.01%)
:arrow_down:

botocore/compat.py
95.32% <100.00%> (-0.06%)
:arrow_down:

botocore/handlers.py
96.53% <100.00%> (+0.02%)
:arrow_up:

botocore/credentials.py
98.52% <0.00%> (-0.36%)
:arrow_down:

botocore/model.py
97.82% <0.00%> (-0.25%)
:arrow_down:

botocore/docs/bcdoc/restdoc.py
96.26% <0.00%> (-0.17%)
:arrow_down:

botocore/retries/bucket.py
98.48% <0.00%> (-0.09%)
:arrow_down:

botocore/validate.py
98.74% <0.00%> (-0.07%)
:arrow_down:

botocore/loaders.py
99.24% <0.00%> (-0.04%)
:arrow_down:

... and 13 more

Continue to review full report at Codecov.

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


PostGIS manual page for Studio docs

[updated with edits]
@heyitsgarrett @ajashton - Guide to PostGIS Manual ready for review. Edits welcome, @katydecorah @geografa would love your :eyes: as well.

cc @yhahn @ian29

This is fabulous.

This looks great, @amyleew - is it linked to from anywhere within the Studio docs? It's worth considering how it fits into the Source Manual, Source Quickstart space - @katydecorah I'd love your opinion on organization here.

Yes @heyitsgarrett, I planned for it to be linked alongside other Studio docs in the manual and quickstart format, as PostGIS Manual. A color + icon treatment can be added as well. @katydecorah thoughts?
I plan to write a follow-up PostGIS Quickstart in the coming weeks.

@amyleew @heyitsgarrett Since this topic is dealing with data sources and PostGIS is mentioned in the Source manual, I recommend that it should fall under the same color/category as the Source quickstart and manual:

Also, a link to the PostGIS guide would be great in this section: https://www.mapbox.com/mapbox-studio/source-manual/#postgis

@heyitsgarrett @katydecorah That's a fantastic idea! Do you guys think a PostGIS quickstart would be helpful here as well?

@amyleew I think it a PostGIS quickstart would be great. As I read through the manual (which is fantastic!), I started to wish I had sample data to follow along with. That's what I like about the Style and Source quickstarts -- they give sample data and walk you through it. I think it would be a great companion piece to the manual.


Add big-jump-loop-nonrect-collapse test

Test for collapse of non-rectangular OpenMP loops on the "big jump loop" path.

Thanks for the review! I don't have write access to AOMP though, so could somebody commit it for me please?


[Enhancement | Suggestion] better color for statusbar entry

Hey,
thanks for your very useful extensions.
But I've a small enhancement in mind:
May be it's better to use statusBar.foreground as default color, which is used by every other entry in the statusbar,  instead of statusBarItem.errorForeground.
statusBarItem.errorForeground interferes in some cases with the used theme, and the workspace is show in a different color, than all other items.

Statusbar with Atom One Dark Theme
In this case it's a prominent white color, I've seen other themes or color configurations where this entry is barely visible. Such as black on dark gray.
Unfortunately it's not possible to set workspaceInStatusBar.text to "statusBar.foreground" as i requires a hard coded RGB value.
I'm using multiple color themes to differentiate multiple workspaces, and therefore it would be much easier not to configure Workspace In Statusbar for each workspace. And before find out the foreground color that is currently used.
Currently I've hacked the package.json:
"colors": [
	{
		"id": "workspaceInStatusBar.text",
		"description": "Color for the label in the status bar.",
		"defaults": {
			"dark": "statusBar.foreground",
			"light": "statusBar.foreground",
			"highContrast": "statusBar.foreground"
		}
	}
]

kind regards
Frank

Hello,
The different color for the workspace name in the status bar is intentional but since there was no other predefined status bar related highlight color available for this purpose, errorForeground was used. I'm not inclined to change this, sorry.
There is however an easy way to set the right custom color for multiple themes, using theme dependent config blocks in your settings.json instead of a single color definition. For example for Monokai it would look like this:
"workbench.colorCustomizations": {
  "[Monokai]": {
    "workspaceInStatusBar.text": "#7cd5f1"

I hope this helps!

I hope, my response did actually help.
Closing this issue.

Sorry for the very late feedback.
Thanks for your tip with colorCustomizations, but it doesn't fit what I have in mind. My attempt is to not have a hardwired color.
In any case, thanks for your support.


Update Contributing.md file with build instructions

Looks like we are using the wiki for building instructions can we instead move those to the contributing.md in the repo. That will make it more consistent with other repos and more importantly will enable the instructions to version with the source so we have a hope of being able to build the repo at various points in source history.
@JonathanGiles @srnagar
cc @JimSuplizio @mitchdenny

This has been resolved with https://github.com/Azure/azure-sdk-for-java/blob/master/CONTRIBUTING.md#building-and-testing


Create PCAP loader to retrieve data based on specific filenames

Retrieve specific data from datastore
Send to visualizations

By specific data, do you mean the data for different use cases like Geo tagging, Bad IPs etc.? According to the original design each of these should be a separate service that reads raw data and processes everytime (optionally caching). So would not recommend storing processed data itself in the primary data store, it can be more like an LRU cache.

Specific data would be retrieving all data in datastore that's tagged under one filename entity -- I think we'll have to fix this to when we separate the parsing and processing but I just needed something to retrieve data for my network visualization for the MVP for now


Support for CAN Connection

Currently I do not have access to the automotive Ethernet connector for the UMRR-96 Type 153 Radar. Does the driver support a CAN USB connection? I have been running the launch file, with some modifications to the radar.template.yaml file, but the node crashes with 'Initialization failed'. Likewise, I was curious if there is any documentation for the Smart Access C++ API? I'd be interested to learn how to set IP addresses for different sensors using this interface.
Thanks in advance!

The driver in it's current state does not support CAN communication. Following the update #4 this is planned to be added as a feature.
If you could tell me as to what modifications you have made, I could tell the possible reasons for the initialization failures? On a general note, there is not much modifications that you could possibly do other than the numbering and the naming of the interface name. The IP addresses and client ID of the sensors should be unique!
Yes, there certainly is. You would need to contact our busdev as I cannot provide it here. There are two possibilities for setting the ip addresses of the sensors either using the drive recorder or using a smart access API. I have included option two in the driver #1, this has been put to a halt for some internal issues but you could set the IP address following this PR.

Thank you for clarifying. Is there an expected release date for the CAN communication update?
Regarding modifications to the parameter file, I have currently removed the second sensor, sensor_1, from the sensors 'block' of the .yaml file and had been playing around with the interface name given my current lack of Ethernet connector. I had changed "hw_iface_name" and "iface_name" both to CAN0 (after setting up a CAN port on my local machine). Likewise, I had tried to set both of the aforementioned parameters to 'lo' to match the default interface name as listed in smartmicro_radar_node.cpp (line 63). The latter attempt works in a sense, but does not actually interface with the radar so all ROS output topics are either empty or meaningless. The standard template with an 'eth0' connection also fails, but this makes sense given that I am not using an Ethernet connection.
Are there any workarounds to getting the wrapper up and running without the automotive Ethernet connector? My setup is identical to the one shown in Picutre 4 of the Smartmicro Project Documentation (i.e. Getting Started User Guide for Automotive and Industrial Radar Sensors). I believe the ROS1 wrapper for the Smartmicro radar supports CAN communication, but if possible, I would like to avoid migrating this project over to ROS2.
Thanks again for both your help and the fast response!

As for the moment there is no planned date for release. There are certain underlying issues which are preventing from integrating CAN.
Yes, that would not work! The driver is designed for only ethernet. It would not work with CAN.
I believe the best possible solution would be to have an Ethernet connector.


Inline markup not respected in tables

Hi,
An example table :
======= ==============================================================
01      **This Markup** does not translate to bold in my docx
======= ==============================================================

I did not find a workaround with table styles. In general I find docx table styles to be very confusing but that's an issue for microsoft. Some options like centered cells don't seem to do anything...
I did not try defining a character style for Bold and applying it my section like so:
:bold:`This Markup`

This could be a workaround if it works.
Thank you very much for this great project.

Actually this problem was not restricted to tables, I had it even on body text.
Fortunately I found where the problem came from. I did not have the right Styles in my template.docx.
I figured it out thanks to the reStructuredText documentation.
It turns out that *this* is actually a disguised version of :emphasis:`this`.
Looking at docxbuilder's documentation Chapter 6.1.2 User defined styles, I thought that :emphasis:`this` would look for a "Emphasis" Word Style.
It turns out there is a built-in "Emphasis" Style, that appears in the Word Home>Styles.
But if you actually look at the implemented Styles (Alt+Ctrl+Maj+S) it does not appear in the list (at least not in my case).
The Fixing Operation:

Open my template.docx
Apply "Emphasis" to a chunk of text
Check that "Emphasis" now appears in the Styles list
Save

And then would my generated documents implement *this* as emphasis.
To be clear, you don't even have to define :
docx_style_names = {
   'emphasis': 'Emphasis'
}

The same can be done for  **this**. Since it translates to :strong:`this`, you just have to repeat the Fixing Operation with the "Strong" Style.
Side Note:
Because I am French working with a french Word interface, my built-in Styles are translated, so "Emphasis" is called "Accentuation". But i guess the OpenXML backend treats it the same way. I did the Fixing Operation with "Accentuation" and it solved the problem the same way. So I guess, if you also have a translated version of Word, all you need is to find out what "Emphasis" and "Strong" translate to in your language.


Integrate with codecov

nose2 is run with --with-coverage to report coverage information which
is then uploaded to codecov.
Fixes #21

Codecov Report

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

@@           Coverage Diff           @@
##             master    #23   +/-   ##
=======================================
  Coverage          ?    69%
=======================================
  Files             ?      6
  Lines             ?   2000
  Branches          ?      0
=======================================
  Hits              ?   1380
  Misses            ?    620
  Partials          ?      0

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 e31115e...cc17dd0. Read the comment docs.


Separate prod/dev build

if (
  typeof process.env.NODE_ENV === 'undefined' ||
  process.env.NODE_ENV === 'development' ||
  process.env.REDUXIBLE_ENV === 'development'
) {
  module.exports = require('./(StoreFactory|ReduxibleRouter).dev');
} else {
  module.exports = require('./(StoreFactory|ReduxibleRouter).base');
}

Changes Unknown when pulling 8124e9585d72203321d38ff05bf694794259d8db on arkist:1.0.0-env-bundle into ** on reduxible:1.0.0**.

please do not merge until more coverage up.
I'll attach tests about my codes soon.

Thanks for the works. I agree with this concept. But could I suggest several requirements?

I want to leave 1.x for legacy environments like old browsers. And 2.x will be the version for evergreen browsers. So please back a version of the React to 0.14.8 for this time. And you can also make a new branch to 2.x and can apply 15.x to there.

Please rename inherited classes to using a prefix. Like ReduxibleRouterDev > DevReduxibleRouter. This is the common naming convention for implementation and inherited classes. You can see the information of it from this links.

https://power2build.wordpress.com/2012/12/01/java-whats-up-with-impl-in-class-names/
http://geekswithblogs.net/brian.johnston.blog/archive/2006/07/04/84054.aspx
http://stackoverflow.com/questions/2814805/java-interfaces-implementation-naming-convention
http://programmers.stackexchange.com/questions/75956/default-vs-impl-when-implementing-interfaces-in-java

Please sync file names with export default. (ReduxibleRouter.dev > DevReduxibleRouter.) It could be confused when developers who don't use IDE finds files.

That's all.
Thanks :)

Changes Unknown when pulling 0a4cc2d0e27f84f281ad610cc6cee7e0b707b600 on arkist:1.0.0-env-bundle into ** on reduxible:1.0.0**.

Okay, I followed your suggestion. :smiley:
inherit naming is now XImpl->(X|XDev) & put React back to 0.14.8.
Coverage rate seems not enough this time but I think we need to change a behavior of router a little before improving rate. it may be in next task.


Check all costs fields for relevancy for the report

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1567254
If a user asks only for some of the fields (memory cost) in a chargeback report
and they didn't request specific ones (memory allocated cost), we would skip
calculating the memory cost because we thought it wasn't relevant.  We need to
check all cost fields to see if they're relevant for the requested fields in the
report.

I believe this will require a manual backport to the different branches. I'll check that on Monday.

I believe this will require a manual backport to the different branches. I'll check that on Monday.

most likely caused by this:
https://github.com/ManageIQ/manageiq/pull/12885

Note: this change is also fixing general total_cost column, so maybe it would be beneficial to add other it case when only column
subject.total_cost is requested.
expect(subject.total_cost).to eq(_)..

@lpichler I need to test various combinations:

memory cost and total cost in a report (total cost should equal memory cost)
memory cost, cpu cost and total cost in a report(total cost should equal memory cost + cpu cost)
total cost by itself (should be blank)

@miq-bot add_label gaprindashvili/yes

It isn't a clean cherry-pick to Fine, in fact some might even say it's not Fine.  I'll open a PR for Fine.

Here is the very Fine PR: https://github.com/ManageIQ/manageiq/pull/17395

Backported to Fine via https://github.com/ManageIQ/manageiq/pull/17395

Gaprindashvili backport details:
$ git log -1
commit b89536b6567eb9b9493679440b3beae5ca00c252
Author: Gregg Tanzillo<EMAIL_ADDRESS>Date:   Tue May 8 09:27:10 2018 -0400

    Merge pull request #17387 from jrafanie/bring_in_relevant_fields_needed_for_charge_calculation

    Check all costs fields for relevancy for the report
    (cherry picked from commit 15886369d79890b9e780a6ff80b084d214f8167b)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1576099


Feature/employee UI iap setup

Added IAP setup script for employee ui service.

merged with https://github.com/momander/cymbal-eats/pull/20


Template #3: The "classic PMA2020 template"

Description
I received some feedback from our staff:

Where I think the PPP can be improved, and this feedback comes from Kenya, Ethiopia and Uganda, is to (if possible) keep the formatting as similar to the old paper questionnaire as possible. The concern from these three teams, all of which submitted the old version of the paper questionnaires to the local IRBs this round was that the local IRB would delay the review process because the PPP version of the questionnaires looked so visually different to what they had submitted for 5 prior rounds. All three country teams asked for this, without knowing that others had requested the same.
I think it would be best to mimic, as much as possible, the visuals of the old paper format – fonts, question formatting etc. Not sure how much of a big ask that is.

So... originally I had planned to have us implement that "classic" template simply for what I thought were aesthetic/preference reasons. Then I realized that none of our staff really cared about that. However, now we are seeing that there are other reasons. For some of our countries, the IRBs (Institutional Review Board)s who review our surveys and give us permission to do them in their respective countries, seem to be very opinionated on what they will accept. They do not want the template to look different from what was used in the past. Therefore, we should revive this issue.
Additional Notes
At the moment, we do not have an easy way to add the question number by itself on the left-hand side. I can participate to help with this.
Tasks
Vitaly @tulvit

[ ] Create a new template which mimics, as much as possible, the visuals of the classic PMA2020 paper format – fonts, question formatting etc.
[ ] Update template to render question numbers after Joe adds that functionality.

Joe @joeflack4

[x] Add the ability to render question numbers: Look for a "question_number" field. If it doesn't exist, use regular expressions to extract the question number from the label.

Attachments
Classic template example - FQ-UGR4v7-2016.03.19.sed.docx

I added in the question_number functionality to OdkPrompt just now https://github.com/PMA-2020/ppp/pull/24.
In the Jinja2 templates, I believe you can access the question number via, for example: <div>{{ question.question_number }}</div>


Grafana dashboard update to support multiple instances

Hello,
this PR is essentially providing two changes:

fix: change nginx_upstream_response to nginx_upstream_responseMsec in Upstream Backend Reposnse section.
feat: introduce Instance variable when you have multiple servers reporting via vts.

Essentially dashboard was prepared to support single nginx instance and changes I'm providing with this PR are switching the behavior to make use of the instance that Prometheus provides by default.
Regards,
Filip

nice job!


Migrate to typescript

Hey! So I know this is a large PR, and you might not use typescript, so that's possibly annoying. I wanted to do this mostly for practice (didn't take long with a migrate tool) and just in case you keep working on this site, I believe types will be very useful. I didn't use to but now I love TS for projects of every size.
Other changes besides typescript:

Pass searchInput state to SearchBar. Technically you were re-rendering the whole app when typing.
keyCode is deprecated, and key === 'Enter' is way more legible
Separated theme to its own file, also due to TS's complaining when adding mobileCard.

Hope it's useful, and if it's not, then at least I hope it's good for checking out some TS!

Thanks for this! ♥
I do use TypeScript at work and probably should've started this project out with it. I just bootstrapped this with Create React App and just started developing. I generally like the freedom of being able to just code freely in JavaScript, but do agree that TypeScript can be helpful.
I'll review this more thoroughly in the future and decide whether I want to go forward with it or not.
I appreciate the other non-TypeScript call outs as well. I'll definitely look into those too.

Thanks for this! ♥
I do use TypeScript at work and probably should've started this project out with it. I just bootstrapped this with Create React App and just started developing. I generally like the freedom of being able to just code freely in JavaScript, but do agree that TypeScript can be helpful.
I'll review this more thoroughly in the future and decide whether I want to go forward with it or not.
I appreciate the other non-TypeScript call outs as well. I'll definitely look into those too.

Sure! There's definitely an easy case to make that at this point it might be overkill, so I completely getcha.

Sure! There's definitely an easy case to make that at this point it might be overkill, so I completely getcha.

Hey, thanks again for this PR.
I added the fixes regarding the re-rendering bug and deprecated keyCode.
I'm not sure I fully understand the use of useCallback() in SearchBar.js though. Removing them seems to work fine too. Do you mind explaining? 😁
The React compiler also throws the following warning.
WARNING in src\components\navbar\SearchBar.js
  Line 50:6:  React Hook useEffect has missing dependencies: 'handleSearch' and 'searchInput'. Either include them or remove the dependency array. If 'handleSearch' changes too often, find the parent component that defines it and wrap that definition in useCallback

So I'm not sure if wrapping handleSearch in App.js makes sense or not. And what the dependencies would be in this case.

I'm not sure I fully understand the use of useCallback() in SearchBar.js though. Removing them seems to work fine too. Do you mind explaining? 😁

Sure. Thinking about it twice, it may be unnecessary. We're not too concerned with re-renderings on OutlinedInput and ´IconButton, and even with the callback it'll change every time searchInput` state changes. Feel free to remove.
WARNING in src\components\navbar\SearchBar.js
  Line 50:6:  React Hook useEffect has missing dependencies: 'handleSearch' and 'searchInput'. Either include them or remove the dependency array. If 'handleSearch' changes too often, find the parent component that defines it and wrap that definition in useCallback

That's because you specifically did that on mount useState to set a default searchInput. The missing dependencies can sometimes be ignored if you're intentionally doing things on mount only. But this comment does lead to something I missed, which is handleSearch in a callback. Otherwise, when App re-renders, handleSearch is re-defined and passed as a prop, making a re-render in SearchBar.

So I'm not sure if wrapping handleSearch in App.js makes sense or not. And what the dependencies would be in this case.

As it is, it should be fine. Though not sure what you mean by wrapping, do you mean to just have it in App.js? SearchBar will handle it's own state and it or any other component can call that function with a string and trigger search. So it should be fine for a small app.

Ah, that makes sense. Well, just like this warning  about the dependencies, the compiler should tell you what it needs. In this case I don't think it needs any dependency,(setSearchResults and setLoadingTime are available on mount)  so you can leave it empty. You're just making sure it won't be redefined on re-rendering the app.
With callback:
https://user-images.githubusercontent.com/11283573/148274451-59b2ea22-0a50-4f07-8703-18b31be8932f.mp4
Without callback:
https://user-images.githubusercontent.com/11283573/148274472-d8883dbc-8ee2-48c2-82c6-c5cbdef3c009.mp4
(profiler tab from the react devtools extension)
In this tiny example the render times are pretty identical, it's not a big component so it might be early optimization. That's also because there's a hook re-rendering it anyway. But whenever you pass a function without callback to another app, it's going to be redeclared and it's going to make the component receive it as a new prop.


Revert ServiceIteraror in Security provider voters

Reverts https://github.com/silexphp/Silex/pull/1614.
Reopens https://github.com/silexphp/Silex/issues/1530.
See problems and discussed solutions in https://github.com/silexphp/Silex/pull/1619.

Thank you @hkdobrev.


Why is min_activated_stake a fixed value of 150'000'000'0000 instead of 15%?

Why is min_activated_stake a fixed value of 150'000'000'0000 instead of 15%? In order to limit the system token SYS circulation is 1 billion?（.../constracts/eosio.system/producer_pay.cpp ）

This is hardcoded value and it was only used to activate the blockchain. It would basically equal to 15% of the overall circulation at the time it was activated. It will be no longer used after activation.

If the initial token (SYS) is less than or much larger than this value（150'000'000'0000）, will it cause the system to fail to activate properly?@taokayan

If the token supply is less than that value, yes, the system will fail to activate properly.  If the token supply is much larger, it will not affect activation.

Thank you ！@jgiszczak


Empty log file after update

I've just updated my node.js from v0.4.10 to v0.6.5, since it is not compatible, I need to install forever again.
However, after updating, I cannot see anything appended in the log files (which works before updating)
May I know how could I solve this problem?
Thanks very much.

pretty sure this is related to #175

Please test the master branch if it's convenient for you to do so - 0.6 should finally be supported.  After a little more testing, it will be published to npm.

This should be fixed in<EMAIL_ADDRESS>


Michael tims/authentication view

Assign to @nandinirao and @ldanzinger
Please review and merge new Authentication views.

Rest looks good.

Looks good now.


Support for output of github actions in annotation format

Proposal
I want to display an error message on the code if there is an error when incorporating runn into Github actions.
Allow errors to be output in the following format
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-error-message
As the development cycle of the product is to create a scenario that will end successfully locally and then push to git, the priority seems to be quite low.
The idea is to have a simple error output that can be used in various ways, not limited to Github actions.

Great !!
I thought it would be good to implement the switching of output by env GITHUB_ACTION directly into runn.

I thought it would be good to implement the switching of output by env GITHUB_ACTION directly into runn.

looking good.
I think phpstan and others behaved like that.


[Rag and the Bone Man 2] Canifis werewolves doesn't mention Wolfbane

The text for the quest says:

Kill the citizens/ werewolves in Canifis

I killed about 30 of them with Wolfbane before opening the wiki to see in bold that you cannot use Wolfbane lol.
Perhaps adding the same text as the wiki would be helpful to others.

The werewolves has an open PR #823 which fixes that part. With regards to the vultures, they don't necessarily need to be, if you have high enough melee stats you can kill it before it flies away. Some clarification could maybe be good tho.

Oh, okay. I searched for it in issues, but not PRs.
re:vultures, I wasn't even able to click on them with melee. I have base 90s, not super high, but the game wouldn't even let me click on any of them. I must have been doing it wrong, but yeah a short helper would be cool.

Merged in the fix, will be available for the next update!


feat(automation): generate code based on latest API changes

Automated Pull Request
The following packages have been added or updated: accountmanagement.
The following new mutations will be added to the codebase:
'accountManagementCreateAccount'
Please perform the following actions before merging:

[ ] If package is new, export and initialize it in newrelic/newrelic.go
[ ] Review the changes to the generated code
[ ] Add new integration tests as necessary
[ ] Update applicable tests as necessary
[ ] Double check the .tutone.yml config file for accuracy

Note: If something looks off or you have questions, please reach out to an Observability as Code team member for assistance.

@nr-developer-toolkit 🫡