Update UI of Contact Us page

Hii @ANSHIKA-26 , The current design of the "Contact Us" page can be enhanced to improve its usability and visual appeal.
Currently, it is not visually appealing. We can use this:

Instead of this

The new design will be more appealing. I am wiling to contribute to this project.

Thanks for the response! Could you please assign me this issue @ANSHIKA-26 ? I'm looking forward to working on improving the UI of 'CONTACT US' page

#255 already there


About window

Perhaps an About tab to the settings to allow for checking the version number, a "check for updates" button, and to give yourself some credit? ;)

There is an about window in the menu with the version number. Could probably be improved with some more information though.

On Mac OS X there is the default about menu, and in the next version a PR has already been merged that adds an "About" page to the tray menu


Minor patch version of Java makes Gradle Extension not work

Extension Name: vscode-gradle
Extension Version: 3.8.2
OS Version: Ubuntu 20.04
VSCode version: 1.61.2
Java version: Openjdk 16.0.1
Gradle version: 7.2
Describe the bug
Originally, the combination of Java 16.0.1 and Gradle 7.2 should work, but as shown in the attached screenshot, it is determined to be a version higher than Java 16.
To Reproduce
The combination of Openjdk 16.0.1 and Gradle 7.2 and Gradle for Java Extension 3.8.2.
Screenshots

Output from "Gradle for Java"
[info] Java Home: /usr/lib/jvm/java-16-openjdk-amd64
...
[info] Gradle Version: 7.2
[error] [gradle-server] Could not fetch model of type 'GradleProject' using Gradle distribution 'https://services.gradle.org/distributions/gradle-7.2-bin.zip'.
[error] Error getting build for /home/asano/ideaproject: Could not fetch model of type 'GradleProject' using Gradle distribution 'https://services.gradle.org/distributions/gradle-7.2-bin.zip'.

@marketspider could you share your settings.xml and your project

Don't work

{
  "java.home": "/usr/lib/jvm/java-16-openjdk-amd64",
  "java.import.gradle.jvmArguments": "-XX:+UseParallelGC -Xmx4G",
  "gradle.debug": true
}

Worked fine.

{
  "java.home": "/usr/lib/jvm/java-16-openjdk-amd64",
  "gradle.debug": true
}

Worked fine.

{
  "java.home": "/usr/lib/jvm/java-16-openjdk-amd64",
  "java.import.gradle.jvmArguments": "-Xmx4G",
  "gradle.debug": true
}

Worked fine.

{
  "java.home": "/usr/lib/jvm/java-16-openjdk-amd64",
  "java.import.gradle.jvmArguments": "-XX:+UseParallelGC",
  "gradle.debug": true
}

I apologize, it worked fine when I specified either no jvmArguments or one jvmArguments at a time.
However, when two jvmArguments are specified, it does not work.

My project is a Gradle multiple subproject template.

This is what is generated by the following command.
gradle init -> application -> Java -> multiple subproject -> groovy

Thanks for reporting. Actually, there are two issues:

Should check major Java version only when compatibility checking.
Our extension accepts java.import.gradle.jvmArguments, but there is a bug when parsing the setting: More than one argument is not supported. I have found the root cause of this bug and will fix it in the next release (3.8.3).


[kiali helm  chart] make operator volumes configurable

Signed-off-by: André Bauer<EMAIL_ADDRESS>
make operator volumes in kiali helm  chart configurable

runner volume is configurable so something else like emptyDir can be used
runner mount directory has been change to /ansible-operator/runner
extraVolumes & extraVolumeMounts has been added

Some background:
We want to run all our containers which use an emptyDir volume with a configured sizeLimit and  the scurityContext "readOnlyRootFilesystem: true" should be set.
This was not possible with the kiali operator before, as it trys to write to /tmp. Therfore the volumes are configurable now. Sizelimit can be used or even some real pvc as backing storage.

Before submitting PRs to the Kiali project, please submit a github issue describing the enhancement request in detail so the team can collaborate and determine the best course of action.

It seems i cant create issues here.
Should i do it in the kiali project itself?

It seems i cant create issues here.
Should i do it in the kiali project itself?

Yes. All Kiali issues/discussions take place in the main kiali/kiali repo.
Also refer to the Kiali community contributing document at https://github.com/kiali/kiali/blob/master/CONTRIBUTING.md#making-a-change

Done: https://github.com/kiali/kiali/issues/5810

superceded by https://github.com/kiali/helm-charts/pull/235 - operator now runs with readOnlyRootFilesystem enabled, which was the ultimate purpose of this PR. Closing this PR.


Once you have made a successful pull request, add yourself to the Contributors Panel

Find more instructions in our README.md

Hey, @terrifricker I would like to work on this issue, would you please assign it to me?

You can do this one as soon as I have accepted your first pull request.

Hi, I wanna work on this issue. Can I join to do it? I wanna be a contributor :)

@sonechca Welcome!  You can do this as well as one of the other issues so you will be contributing more than adding yourself to the list. That way you can do two pull requests.

@sonechca Challenge One uses html and css. Adding a couple questions to our quiz by adding the to quizQuestions.js. You just need to follow the JavaScript syntax that is already there and type in your new questions, possible answers (multiple choice), and correct answer.
Please don't hesitate to ask questions here.

hey! can you please assign me?

@Adityachaturvedi2906 Yes!  Thanks for joining in.

Hey, @terrifricker I just submitted my PR kindly review it.


Duplicate artifacts for Javadoc Prettifier

When published, io.spine.tools contain:

javadoc-prettifier
spine-javadoc-prettifier

There should be only spine-javadoc-prettifier.

It could be because of the following code in the build.gradle of javadoc-prettifier module:
test.dependsOn(publishToMavenLocal,
               project(':base').publishToMavenLocal,
               project(':plugin-base').publishToMavenLocal)

Normal publishing goes via publish.gradle in the block projectsToPublish.each { ... }. It prepends spine- prefix to subproject names.

@dmdashenkov, FYI.


[BUG] The problem with sample selection for datasets with 1 attribute.

PR to attract attention. In case of using selectors (for example, FPS), an error is returned for datasets of size (N, 1), the reason for which I indicated in the comment in the code. It requires checking that the dataset has more than 1 feature, although this is only important for selecting features, not samples.

@hurricane642 is this still an issue? If so please update the code to pass tests and re-request review.

Continued in #124


ng-bootstrap button group active state

Button groups don't indicate the currently active button.

Cannot reproduce with examples in the demo app.


add ValueType and allow Object.At  O extends {}

🍩 Feature Request
Is your feature request related to a problem?
import { mapValues } from 'lodash';
import * as querystring from 'querystring';

export type ValueType<T extends {}> = T[keyof T];

export type LoosePropertyType<
  T extends {},
  K extends string
> = K extends keyof T ? T[K] : never;

interface APIs {
  readonly server1: {
    readonly getUserProfile: {
      readonly Parameter: {
        readonly id: string;
      };
      readonly Response: {
        '200': {
          readonly id: string;
          readonly name: string;
          readonly gender: boolean;
        };
      };
    };
  };
}

const ApiData = {
  server1: {
    getUserProfile: {
      url: 'www.foo.com/profile',
    },
  },
};

const myFetch = (mapValues(ApiData, server =>
  mapValues(server, ({ url }) => (requestParams: any) =>
    fetch(url + querystring.stringify(requestParams)).then(x => {
      if (x.status === 200) {
        return x.json();
      }
      throw new Error();
    }),
  ),
) as any) as {
  [namespace in keyof APIs]: {
    [operationId in keyof APIs[namespace]]: (
      param: LoosePropertyType<APIs[namespace][operationId], 'Parameter'>,
    ) => Promise<
      ValueType<LoosePropertyType<APIs[namespace][operationId], 'Response'>>
    >;
  };
};

Describe the solution you'd like

add ValueType
change type AtLoose<O extends object, K extends Key> = O extends unknown ? AtStrict<O, K> : never; to type AtLoose<O extends {}, K extends Key> = O extends unknown ? AtStrict<O, K> : never;

Describe alternatives you've considered

Teachability, Documentation, Adoption, Migration Strategy

Hi there, you can use UnionOf to do this https://pirix-gh.github.io/ts-toolbelt/modules/object_unionof.html

@pirix-gh Sorry, I tried it and it doesn't seem to work.

Sorry, I tried it and it doesn't seem to work.

Oops sorry, I misunderstood your demand. This is kind of strange though. I can't edit At for type safety purposes. It happens that TypeScript does not infer the expected type correctly. In those cases, I invite you to use Cast or &.
Here's your code:
type t = {
  [namespace in keyof APIs]: {
    [operationId in keyof APIs[namespace]]: (
      param: O.At<APIs[namespace][operationId] & {}, 'Parameter'>,
    ) => Promise<
      O.UnionOf<O.At<APIs[namespace][operationId] & {}, 'Response'> & {}>
    >;
  };
};

I used & {} to cast the type to object since we are sure that it is an object. This is an odd error though, maybe it should be reported as a bug to the ts team.

How can I describe this problem and report a bug to TS? I am not very familiar with the mechanism of TS.

The same way you opened an issue here. But you must make your example clearer and ask them why is APIs[namespace][operationId] not inferred as an object. Maybe you should try to simplify your code, just keep the type part. Good luck!

Thank you.


Bug in loading paths - checking ".thrift" extension on Path types

In Loader, when loading paths it filters on .endsWith(".thrift"). Thing is, it's checking this on Path and converting the given parameter to a Path. The result is that this filter always fails to find any .thrift files:
https://github.com/Microsoft/thrifty/blob/103614bd7e5102a69dc87258d5dee657fa4810ad/thrifty-schema/src/main/java/com/microsoft/thrifty/schema/Loader.java#L194

Yep, great catch.  Include-path scanning seems to have been broken since the Java 8 update.  Thanks for the report, and for the fix!


union types within interfaces seem to be interpreted as section

We are using mobx, and we are getting the following error since recently:
Cannot call `configure` with object literal bound to `options` because string [1] is incompatible with boolean [2] in
property `enforceActions`.

   src/Sulu/Bundle/AdminBundle/Resources/js/index.js:45:11
   45| configure({enforceActions: 'strict'});
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^

References:
   src/Sulu/Bundle/AdminBundle/Resources/js/index.js:45:28
   45| configure({enforceActions: 'strict'});
                                  ^^^^^^^^ [1]
   node_modules/mobx/lib/mobx.js.flow:6:22
    6|     enforceActions?: boolean | "strict",
                            ^^^^^^^ [2]

You can also see our CI build for the full output.
IMO everything is correct here, but flow doesn't read that correctly. Have also made a small reproducible example here: https://flow.org/try/#0PTAEAEDMBsHsHcBQBLAdgFwKYCdIEMBjTUAeQAd1lZUBnUAb0VFE1UlmyIEEDLqaAXKABGsWNEx5UoAD6gA5DXTZkveYgC+iRJACuqXlWkFqkZAHNd2TAApYwgFZDyfWgEoGWxCbYWrt+lZ2TkweV0FQZV1MDTcAbiA
The thing is that now nothing works, neither 'strict' nor true are acceptable values now. I would expect for both of them to be valid.
This only seems to occur within interfaces, if this is defined with an object it works without any problems.

Duplicate of https://github.com/facebook/flow/issues/3876


How to prevent triggering renderCalendarInfo on mouseover/mouseout of day?

I am using DayPickerRangeController and passing renderCalendarInfo to show more buttons/info.
I found that renderCalendarInfo is triggering on mouseover and mouseout over a day in the calendar. Is there a way to prevent this?

@majapw Could you please help me?

+1

#1359 #


Add GCEBlockStoreService, GCEVolumeService, GCESnapshotService

Hi @nuwang @afgane @chiniforooshan @mbookman,
This pull request adds GCEBlockStoreService, GCEVolumeService, GCESnapshotService and related classes.
Thank you!

@nuwang - We aren't really sure how the Volume name is used in the API or used by Galaxy - is it okay for it to be just a label? Are lookups by "name" needed?

@mbookman At present, the volume label is mainly used as a display value - cloudbridge/cloudman will internally use the volume ID as primary key, but volume name will be displayed for the users' benefit. Currently, there's no scenario in which lookups by name are needed. However, I would imagine that a search by name may be needed at some point. Do labels support searching? I guess we could always simulate a search within cloudbridge itself - i.e. retrieve all volumes, get their name label, and then filter the ones matching the search criteria  - would that be terribly slow?
Enis and I had a chat about this yesterday and we were going to suggest that perhaps the thing to do for GCE is to autogenerate a UUID for the Volume ID, and then use a label for the volume name. Would that work?

Hi @mbookman and @nuwang ,
Thank you for your review comments. Please take another look. Thanks!

@baizhang @mbookman @afgane Thanks for the changes and suggestions. Looks good. I was just thinking though, that if we use the name instead of label, we will not be able to rename the volume later I'm assuming? That's probably ok, we can just document that as not being an option in GCE.
All in all, based on what you said Matt, I was thinking that perhaps we should consider enforcing RFC1035 for all names in cloudbridge and document it at an interface level. The only thing that bugs me a little is the lack of spaces for a descriptive name. Perhaps it can be "RFC1035+spaces allowed" and GCE can replace spaces with underscores where necessary?

@nuwang - your proposal seems reasonable to me:

Use the disk name field for name (with the specified character and inability to rename restrictions)
Use labels for the disk description field. GCE implementation will convert spaces to underscores

Hi @nuwang @mbookman
Commit 7df11e4 adds GCEVolume description using labels. PTAL.
Thanks!

Thanks @baizhang. Commit 7df11e4 looks good to me so long as the caller is going to be enforcing restrictions on the characters and length of the description. Put another way - what happens if the GCEVolume description has invalid label characters - does the error message raised help the end user or do they get something cryptic?

Hi @afgane @mbookman @nuwang
I updated the this pull request. For @afgane 's comments, please see inline replies. For @mbookman 's comment, I log the error message to cb.log.warning when there are invalid label characters.
PTAL. Thanks!

@baizhang I'd be more inclined to log the message but re-raise the error, rather than failing silently. If it's ok, I'll merge this in and issue a new pull request to fix that.

@afgane @baizhang @mbookman Have included aforementioned fix in: https://github.com/gvlproject/cloudbridge/commit/34ae3bd7b307d3f3f2d5fb1af87a0241f65ede8e


[REQUEST] Allow user to choose the docker build tool

Is your feature request related to a problem? Please describe.
Some users have different image building tools that they need to use. Like docker, podman, singularity, buildah, etc.
Describe the solution you'd like
Allow user to choose the docker build tool.

We have discussed that we would add support for podman alone for now.


Fixes to find_lsn_for_timestamp

This does a bunch of correctness fixes and improvements for the find_lsn_for_timestamp function that serves the get_lsn_by_timestamp endpoint.
It implements points 1 and 2 of #3689, but in an actually working and more correct way (for point 3 there was #5608).
The PR starts out with a very slightly modified version of #3689 and then puts a bunch of improvements on top of it, like addressing reviewer comments. Most importantly, during review of #3689 it was found that it actually didn't implement point 2, the core of the change, as pointed out in this comment.
As I'm not sure about how the underlying data behaves, I am writing down the assumptions I made when I wrote this PR. These assumptions might be wrong, I don't know. There is a map_all_timestamps function, which iterates over SLRU segments, and maybe finds commits with timestamps associated to the queried lsn. My assumptions about this function are:
A) map_all_timestamps is not guaranteed to always find timestamps for some given lsn. My understanding is that this can happen when there is a lot of data inside a commit, then it is split into multiple pages. no clue really.
B) map_all_timestamps can also yield multiple differing timestamps, in whatever order.
C) map_all_timestamps is a monotonic function wrt lsns as inputs and the largest timestamp it outputs for each given lsn. in other words max(all_timestamps(lsn_a)) <= max(all_timestamps(lsn_b)) for lsn_a <= lsn_b.
Note that the current code already assumes C. I think, for being able to do binary search at all, we need to have C, or some weakened form of it. However, even if C is not correct 100% of the time, it will still give us results close enough that we don't care.
The assumptions A and B are rather things we have in place because I'm not 100% sure I can rely on some specific property to be present so it is the source for complexity in the search code.
The things we do in this PR:

rename get_timestamp_for_lsn to get_max_timestamp_for_lsn as it better fits what the function is doing
we get rid of the is_latest_commit_timestamp_ge_than function and replace it with usage of get_max_timestamp_for_lsn. updating the found_smaller value with commit timestamps that are, per assumption B, maybe not the only ones in an lsn, might be dangerous, as the biggest commit in the lsn might end up bigger than search_timestamp: the way we use found_smaller though is that we actually found an entire lsn whose maximum is smaller than search_timestamp. for found_larger it doesn't matter as much but it is weird to update one in one function, one in the other.
we add rustdoc comments to LsnForTimestamp, explaining the behaviour
the implementation for point 1 of #3689 was taken verbatim as it seemed good
for assumption A, the code actually did really bad things: it continued the binary search and updated low, even though the actual commit, found somewhere in a later lsn, might be already too far in the future and the one we looked for might be between the old value of low and mid. Basically, when no timestamps are found, we should first establish some other "mid" point that has a timestamp.
for establishing the mid point, the code does a search over the range mid..max where mid is the average between min and max, the two ends of the current bisection window. the search is done in an exhaustive fashion, so that we can reduce our max to mid if we have exhaustively searched the entire mid..max range and it's all None. it is also done in a fashion where we do an explosive/exponential search to not be stuck processing some singular large (potentially in the gigabytes) commit.
for point 2 of #3689, we looked at the invariants of the binary search: before this PR, the invariant for high was always kept while the invariant of low was maybe violated: a binary search might not always end with equality so if you converge to one item, the question is always whether the invariant of the high or of the low is violated in the end. we updated the code to maybe violate the invariant of high instead, and keeping the invariant of low intact. this manifests in the code in the change to use mid + 1 for the query instead of mid, because high always gets set to mid and low always gets set to mid + 1  (outside of initialization). keeping the mid + 1 around is important to have the binary search terminate after reaching its final state (and not looping infinitely).

closes #3689
fixes #3414

I will try to look into how to make tests, probably the easiest is to factor this search out into a module. It's a bit annoying though that we have async around, so likely it'll end up with an enum solution. Not great, not terrible...

A) map_all_timestamps is not guaranteed to always find timestamps for some given lsn.

Correct.

My understanding is that this can happen when there is a lot of data inside a commit, then it is split into multiple pages. no clue really.

Hmm, no I don't think the amount of data in the transaction makes any difference. I think one scenario where it can happen is if you have imported a backup into neon (which we don't support in the UI yet), and haven't performed any commits since. I don't remember if there are other cases.
B) map_all_timestamps can also yield multiple differing timestamps, in whatever order.
Correct. To be precise, it will call the closure passed as argument in with timestamps in any order.
C) map_all_timestamps is a monotonic function wrt lsns as inputs and the largest timestamp it outputs for each given lsn. in other words max(all_timestamps(lsn_a)) <= max(all_timestamps(lsn_b)) for lsn_a <= lsn_b.
Not true. If two transactions A and B commit concurrently, at roughly the same time, they might read the current time in order A, B, but write the commit records in order B, A.
It is approximately true, however.

I think one scenario where it can happen is if you have imported a backup into neon (which we don't support in the UI yet), and haven't performed any commits since. I don't remember if there are other cases.

I have added a simple loop to the get_lsn_by_timestamp over the entire range from the start to the end and it seems that at least at the start there is a bunch of None's. As in, with the workload from the test_lsn_mapping case, the start LSN is 0/14F5FD0, the max LSN is 0/15498D8, but it is only None's until 0/150E3D0 (inclusively), from when on it is only Some's. Other workloads might have blocks of None's, idk.

It is approximately true, however.

Thanks for confirming, that's all we need :+1: .

I'll try to work through an example, to elaborate point 2. (I'm writing this mostly to make it clear to myself as I review this. Although maybe it would be good to include an example like this in a comment too):
Imagine there are 3 commits, at LSNs 004, 009 and 00D:
LSN			Max timestamp
001			11:22:00
002			11:22:00
003			11:22:00
004			11:22:10
005			11:22:10
006			11:22:10
007			11:22:10
008			11:22:10
009			11:22:20
00A			11:22:20
00B			11:22:20
00C			11:22:20
00D			11:22:30

With current main:
get_lsn_at_timestamp('11:22:15') returns 008

With this patch:
get_lsn_at_timestamp('11:22:15') returns 004

In other words, on main it returns the last LSN for which the max(timestamp) is smaller than the search timestamp. With this PR, it returns the LSN of the last commit record before that LSN.
From a logical point of view, there is no difference because there are no commits between 004 and 009. You see the same logical state of the database. However, it does make a difference at a physical level: there's no point in including the uncommited changes of the transaction that committed at 009. That would be just garbage that
needs to be vacuumed away on the branch.
How does the binary search work in this case? With current main:
LSN			Max timestamp	Binary search
001			11:22:00
002			11:22:00
003			11:22:00
004			11:22:10
005			11:22:10
006			11:22:10		1. greater
007			11:22:10
008			11:22:10		3. greater
009			11:22:20		4. smaller
00A			11:22:20		2. smaller
00B			11:22:20
00C			11:22:20
00D			11:22:30

Looking at this PR, however I don't understand how that works. I think it would return 008, like on main. The binary search works the same as on main. There are some differences in how it deals with the case that get_max_timestamp_for_lsn() returns None, and it calls get_max_timestamp_for_lsn() with Lsn + 1. I don't fully understand those changes, I haven't really tried to grok them yet, but AFAICS they don't affect which LSN the binary search will land on in this example. Or maybe it will be off-by-one, not sure, but I don't see how it could land on LSN 004 like it should.

In preparation for a call that I had earlier today with Heikki, I made a simulator for the binary search on the playground that simulates both the old mode previous to this PR, as well as the new mode after this PR (at least the parts relevant for point 2):

fn binary_search(list: &[u16], needle: u16, old_mode: bool) -> Option<usize> {
    if list.is_empty() {
        return None;
    }
    let mut high = list.len() - 1;
    let mut low = 0;
    println!("\nBinary search. needle: {needle}, old_mode: {old_mode}");
    while low < high {
        let mid = (high + low) / 2;
        let query_val = if old_mode {
            mid
        } else {
            mid + 1
        };

        let val = list[query_val];
        println!("    low: {low:<3} high: {high:<3} mid: {mid:<3} val: {val:<3} smaller: {:<5} \
            list[low]: {:<3} list[high]: {:<3}", val <= needle, list[low], list[high]);
        if val <= needle {
            low = mid + 1;
        } else {
            high = mid;
        }
    }
    println!("    low: {low:<3} high: {high:<3}                                  \
        list[low]: {:<3} list[high]: {:<3}", list[low], list[high]);
    let res = if old_mode {
        low -  1
    } else {
        low
    };
    println!("    -> res: {res}, list[res]: {}", list[res]);
    return Some(res);
}

fn main() {
    let mut list = [0; 40];
    println!("List is:\n    idx   val");
    for (i, v) in list.iter_mut().enumerate() {
        *v = (i as u16 / 4) * 10;
        println!("    {i:<3}   {v}");
    }
    binary_search(&list, 45, true);
    binary_search(&list, 45, false);
    // What we want as result: 16
    // What we get: 19
}

It has the following output:

List is:
    idx   val
    0     0
    1     0
    2     0
    3     0
    4     10
    5     10
    6     10
    7     10
    8     20
    9     20
    10    20
    11    20
    12    30
    13    30
    14    30
    15    30
    16    40
    17    40
    18    40
    19    40
    20    50
    21    50
    22    50
    23    50
    24    60
    25    60
    26    60
    27    60
    28    70
    29    70
    30    70
    31    70
    32    80
    33    80
    34    80
    35    80
    36    90
    37    90
    38    90
    39    90

Binary search. needle: 45, old_mode: true
    low: 0   high: 39  mid: 19  val: 40  smaller: true  list[low]: 0   list[high]: 90
    low: 20  high: 39  mid: 29  val: 70  smaller: false list[low]: 50  list[high]: 90
    low: 20  high: 29  mid: 24  val: 60  smaller: false list[low]: 50  list[high]: 70
    low: 20  high: 24  mid: 22  val: 50  smaller: false list[low]: 50  list[high]: 60
    low: 20  high: 22  mid: 21  val: 50  smaller: false list[low]: 50  list[high]: 50
    low: 20  high: 21  mid: 20  val: 50  smaller: false list[low]: 50  list[high]: 50
    low: 20  high: 20                                   list[low]: 50  list[high]: 50
    -> res: 19, list[res]: 40

Binary search. needle: 45, old_mode: false
    low: 0   high: 39  mid: 19  val: 50  smaller: false list[low]: 0   list[high]: 90
    low: 0   high: 19  mid: 9   val: 20  smaller: true  list[low]: 0   list[high]: 40
    low: 10  high: 19  mid: 14  val: 30  smaller: true  list[low]: 20  list[high]: 40
    low: 15  high: 19  mid: 17  val: 40  smaller: true  list[low]: 30  list[high]: 40
    low: 18  high: 19  mid: 18  val: 40  smaller: true  list[low]: 40  list[high]: 40
    low: 19  high: 19                                   list[low]: 40  list[high]: 40
    -> res: 19, list[res]: 40

you can see that both the old and new modes of the binary search have the same result in the end, even though they arrive at it in a different way. This means that @hlinnaka 's comment right above is right: regarding point 2 we are in the same situation as #3689, the attempt at fixing is proven to not have changed anything. The good news is that I am now more familiar with the problem.
According to Heikki there might be no ways to fix point 2 without a change of the timestamps, or in other words, the on-disk format (we store them; in walredo).
With Heikki we concluded that the fix for 2 might not be the highest priority as it is a performance, not a correctness fix, although I pointed out that I heard statements before suggesting different things.
There is a) the problem that two transactions might have the same timestamps, and then we want to actually return the lsn corresponding to the beginning of the new transaction, and b) the problem that if we perform a search with decreasing lsns, we might hit lsns for later timestamps than the "big transaction" that were in-flight.
As the next steps, I am going to write a test case, and then I will do some printing to understand the way that lsns get mapped to timestamps better. I will also split off the point 1 fix of this PR into a different one which we can hopefully merge very quickly.

I've done the split as announced in my comment, the split PR can be found in #5844  (together with improved tests). This one is blocked right now, converting to WIP.

I think the mergeable parts of this PR have been merged, and for the non-mergeable parts a fundamental change of the approach is needed. Closing.


Adding custom previous property to the $state object

Ability to remember the previous state from which the current state was reached ...
Is there a way to add custom previous property to the $state object in the controller when i am changing the the State...
For ex i am on state A going to state B and i can go to state C from state B also from D i can go to State C ,
i want to remember from which state i jumped to state C ..i.e either B or D
So may be we can have  a construct which takes in the custom properties and which can be used later when going back..
So i will just say $state.goBack()

https://gist.github.com/eddiemonge/f6a58169c2846731a1eb


Uncaught TypeError: Cannot read property 'observe' of null

This occurs after the errors in #303, upon clicking in any pane with editor items.
Reproduction:

Update power-mode plugin to latest
Update Atom to 1.19.2 from 1.19.1
Restart atom to use new atom
Click in any pane with a file in it.
Error occurs.

Atom: 1.19.2 x64
Electron: 1.6.9
OS: Ubuntu 14.04.5
Thrown From: activate-power-mode package 2.4.0
Stack Trace
Uncaught TypeError: Cannot read property 'observe' of null
At /my_home_dir/.atom/packages/activate-power-mode/lib/canvas-renderer.coffee:72

TypeError: Cannot read property 'observe' of null
    at Object.setupCanvas (/packages/activate-power-mode/lib/canvas-renderer.coffee:72:20)
    at Object.onChangePane (/packages/activate-power-mode/lib/plugin/power-canvas.coffee:19:13)
    at /packages/activate-power-mode/lib/plugin-manager.coffee:87:32
    at Object.onEnabled (/packages/activate-power-mode/lib/plugin-registry.coffee:64:19)
    at Object.runOnChangePane (/packages/activate-power-mode/lib/plugin-manager.coffee:86:21)
    at Object.setupPane (/packages/activate-power-mode/lib/power-editor.coffee:40:20)
    at /packages/activate-power-mode/lib/power-editor.coffee:9:8
    at Function.module.exports.Emitter.simpleDispatch (/usr/share/atom/resources/app/node_modules/event-kit/lib/emitter.js:25:20)
    at Emitter.module.exports.Emitter.emit (/usr/share/atom/resources/app/node_modules/event-kit/lib/emitter.js:141:34)
    at /usr/share/atom/resources/app/src/workspace.js:551:30

Commands
     -2:33.9.0 intentions:highlight (input.hidden-input)
     -2:33.3.0 settings-view:open (input.hidden-input)

Non-Core Packages
activate-power-mode 2.4.0
ariake-dark-syntax 0.1.3
atom-material-syntax 1.0.6
autocomplete-python 1.10.2
automate-power-mode 0.2.1
busy-signal 1.4.3
chary-tree-view 0.2.13
double-tag 0.9.0
git-time-machine 1.5.9
gloom 0.6.4
intentions 1.1.5
language-puppet 0.23.0
language-source-cfg 0.3.1
linter 2.2.0
linter-puppet-lint 0.8.2
linter-ui-default 1.6.7
material-monokai-syntax 1.0.1
multirow-tabs 0.3.3
nord-atom-syntax 0.9.1
nord-atom-ui 0.11.0
northem-dark-atom-syntax 2.1.0
platformio-ide-terminal 2.5.5
power-effects 0.3.0
pretty-json 1.6.4
tree-view-copy-relative-path 1.2.0
vim-mode-plus 0.97.2

This only occurs when automate-power-mode is enabled, so this isn't really your problem, but now this case is here in case it happens to others and they're looking for answers

It seems fixed with the new update.


Port to godot 3.x

Just couple of syntax changes.

Please remove the leftover print and resubmit against the godot-3 branch, thanks


Delete unused classes

Summarise the changes this Pull Request makes.
Delete unused classes PoolAwareSocketAsyncEventArgs and SimpleObjectPool
We stopped using these in the last release, but the code is still there
Please include a reference to a GitHub issue if appropriate.

Check away. They are public :( but I doubt it.
In the unlikely case that someone is, they should copy the source into their  app.

Yeah, I do use these. I use them in a alternate IStatsDTransport implementation to pool UdpClient instances.

So is that use just in one place? would you rather have these classes in JustEat.StatsD or with the alternate IStatsDTransport implementation?

I guess it's easy enough for me to copy them over at whatever point I upgrade to StatsD 3, but I thought I'd point it out as it's another breaking change.

See #81, where we might want to at least use SimpleObjectPool.

Will review this later. We might make them internal and/or sealed


Use matcher rather than custom functions for waiting for DV phases

Release note:

NONE

cc @rmohr

/lgtm
/approve
Nice. :+1:


"ActiveRecord::SubclassNotFound" error when running daily cron job

The daily cron job is giving an error that appears to be related to the database:
$ RAILS_ENV=production bundle exec rake cron:daily
rake aborted!
ActiveRecord::SubclassNotFound: The single-table inheritance mechanism failed to locate the subclass: 'ArticleNotUpdatedError'. This error is raised because the column 'type' is reserved for
 storing the class in case of inheritance. Please rename this column if you didn't intend it to be used for storing the inheritance class or overwrite Filter.inheritance_column to use anothe
r column for that information.
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/inheritance.rb:186:in `rescue in find_sti_class'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/inheritance.rb:180:in `find_sti_class'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/inheritance.rb:169:in `discriminate_class_for_record'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/persistence.rb:67:in `instantiate'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/querying.rb:50:in `block (2 levels) in find_by_sql'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/result.rb:51:in `block in each'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/result.rb:51:in `each'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/result.rb:51:in `each'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/querying.rb:50:in `map'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/querying.rb:50:in `block in find_by_sql'
/var/lib/gems/2.1.0/gems/activesupport-4.2.0/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/querying.rb:49:in `find_by_sql'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/relation.rb:638:in `exec_queries'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/relation.rb:514:in `load'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/relation.rb:243:in `to_a'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/relation/delegation.rb:46:in `each'
/srv/lagotto/app/models/filter.rb:43:in `run'
/srv/lagotto/lib/tasks/filter.rake:4:in `block (2 levels) in <top (required)>'
/srv/lagotto/lib/tasks/cron.rake:16:in `block (2 levels) in <top (required)>'
NameError: uninitialized constant ArticleNotUpdatedError
/var/lib/gems/2.1.0/gems/activesupport-4.2.0/lib/active_support/inflector/methods.rb:261:in `const_get'
/var/lib/gems/2.1.0/gems/activesupport-4.2.0/lib/active_support/inflector/methods.rb:261:in `block in constantize'
/var/lib/gems/2.1.0/gems/activesupport-4.2.0/lib/active_support/inflector/methods.rb:259:in `each'
/var/lib/gems/2.1.0/gems/activesupport-4.2.0/lib/active_support/inflector/methods.rb:259:in `inject'
/var/lib/gems/2.1.0/gems/activesupport-4.2.0/lib/active_support/inflector/methods.rb:259:in `constantize'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/inheritance.rb:181:in `find_sti_class'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/inheritance.rb:169:in `discriminate_class_for_record'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/persistence.rb:67:in `instantiate'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/querying.rb:50:in `block (2 levels) in find_by_sql'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/result.rb:51:in `block in each'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/result.rb:51:in `each'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/result.rb:51:in `each'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/querying.rb:50:in `map'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/querying.rb:50:in `block in find_by_sql'
/var/lib/gems/2.1.0/gems/activesupport-4.2.0/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/querying.rb:49:in `find_by_sql'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/relation.rb:638:in `exec_queries'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/relation.rb:514:in `load'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/relation.rb:243:in `to_a'
/var/lib/gems/2.1.0/gems/activerecord-4.2.0/lib/active_record/relation/delegation.rb:46:in `each'
/srv/lagotto/app/models/filter.rb:43:in `run'
/srv/lagotto/lib/tasks/filter.rake:4:in `block (2 levels) in <top (required)>'
/srv/lagotto/lib/tasks/cron.rake:16:in `block (2 levels) in <top (required)>'
Tasks: TOP => filter:all
(See full trace by running task with --trace)

All migrations have been run.

This is (sort of) documented in the 3.10 release. Please run the following to rename the ArticleNotUpdatedError type column to WorksNotUpdatedError. You can of course also manually rename in MySQL.
RAILS_ENV=production bundle exec rake db:seed

no database migration for it?
On Wed, Feb 18, 2015 at 9:17 PM, Martin Fenner<EMAIL_ADDRESS>wrote:

This is (sort of) documented in the 3.10 release. Please run the following
to rename the ArticleNotUpdatedError type column to WorksNotUpdatedError.
You can of course also manually rename in MySQL.
RAILS_ENV=production bundle exec rake db:seed
—
Reply to this email directly or view it on GitHub
https://github.com/articlemetrics/lagotto/issues/250#issuecomment-74949627
.

--
Luke Skibinski
devops - eLife
--
eLife Sciences Publications, Ltd is a limited liability non-profit
non-stock corporation incorporated in the State of Delaware, USA, with
company number 5030732, and is registered in the UK with company number
FC030576 and branch number BR015634 at the address First Floor, 24 Hills
Road, Cambridge CB2 1JP.

No, we only change the data, not the database schema. And I don't like putting data into database migrations.

I've run the command and the daily cron appears to work now. There is a message though:
Both Source and its :state machine have defined a different default for "state". Use only one or the other for defining defaults to avoid unexpected behaviors.

If this is not a problem then close this issue.
Cheers,

This is not a problem, you can ignore that warning.


Key is not used for partitionning

I have added the 'key' to the payload, which is the ID of one of my entities, so that i get the same entity in the same partition. Our topic has 4 partitions. Unfortunately it does not seem to work.
We expect that with the above the message will always go in one of the 4 partitions, but we have seen that the message will be send to all partitions.
Do you have any idea with this is the case?

@lcobucci why do we do this client side? does kafka do this already?

@mantzas nope, that's why I'm asking you to check that particular branch. I'll be reviewing it further this week to integrate, but will be only available in v3.x

@lcobucci yes, this is what's needed from our side. We integrated the current code in our codebase to make this work now. We will wait until v3 to get the library then. Thanks man

@demyanovs done this already based on #218. it's running in production already. thanks.


Web Worker of 'crawler #2' returned an error: unknown

Only "dummy" works, rest of the bots returns error now.
http://jsbattle.jmrlab.com/

I could not reproduce it. Maybe there were some connectivity issues. Can you attach any console log? Does the problem still appear?

It works fine now, maybe due to temporary resource limitations on the server side?


Update wsl-user-msft-kernel-v6.md

Fix typo after upgrade from 6.1 to 6.6 Kernel version guide

@pdebruin There was still this reference to 6.1 missing the update to 6.6

Hi, thanks for reporting. This is fixed in main, we just haven't published yet because of another dependency. I'll close this for now.


All progress lost within certification

I’m currently working my way through the Back End Development Certification. I logged out of my account on FreeCodeCamp, and after logging back in, I’ve lost all of my progress within the Map, and it’s saying that I haven’t completed any of the Back End Development Certification work, however, as of a few days ago, I had completed all the way up to the “Request Header Parser Microservice” section of the API Projects. I've posted on the FreeCodeCamp forum and emailed<EMAIL_ADDRESS>but I haven't heard anything back. Is there any way to restore my progress? Thank you so much!
Browser Information

Both Firefox (Version 50.1.0) and Chrome (Version 56.0.2924.87)
Operating System: OS X El Captain (Version 10.11.6)
Mobile, Desktop, or Tablet: Desktop

@SimplySpoons sorry to here about your issue, we are looking into this.
/cc @BerkeleyTrue @QuincyLarson

@raisedadead Thank you so much! Please let me know if you need any further information from me. Thanks again!

@SimplySpoons Please send a support email to @QuincyLarson at<EMAIL_ADDRESS>Hope we can get this worked out for you soon.
Happy Coding

@BerkeleyTrue I emailed<EMAIL_ADDRESS>last Thursday (2/9/2017,) and I didn't hear back. I'll send along another email. Thanks again! :)

@SimplySpoons that's my fault. I'm behind. I'll get back to you ASAP and help you figure this out :)

@QuincyLarson No worries! Sounds good! Thank you so much :)

@QuincyLarson Did you have a chance to take a look at this? :) Thanks again!


Feature: Shortcut to open selected folder in Secondary Pane

What feature or improvement do you think would benefit Files?
Adding a shortcut to open a folder in the secondary pane would help make the secondary pane more useful, and accelerate its use without having to go into the context menu and selecting the option manually. Similar to the use of Ctrl + Enter to open a folder in a new tab.
Requirements

Add shortcut

Files Version
<IP_ADDRESS>
Windows Version
Version	10.0.22621 Build 22621
Comments
No response

This is very reasonable, which shortcut would be a good default?

Ctrl+Shift+Enter ?

That's already used for opening in a new tab

That's a good one 👍

Looking into it.


Update BingWebSearchV7.py

update key&endpoint

Fixed per latest changes. Kindly reply here or re-open should that be not the case.


Preserve order of URI parameters

Currently, resource.uri_params is not in the order that is defined in the URI path. It looks like right now, it is just in reverse order.

Should be fixed with this patch that I just merged.


Fix documentation for adding items to search results

1. Why is this change necessary?
Former code does not work.
2. What does this change do, exactly?
It fixes the twig syntax for a parent call, so it actually works.
3. Describe each step to reproduce the issue or behaviour.

Follow how-to tutorial for adding a custom entity to the administration search
Find the twig code is not working.
Figure out that it is due to a syntax error.

4. Please link to the relevant issues (if any).
None.
5. Which documentation changes (if any) need to be made because of this PR?
Well, this one is a documentation change itself, sooo...
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

hey @jkrzefski
thanks for your contribution :+1: :tada: :blue_heart:
I imported it, and it will be merged soon


Fix missing includes and have docker reference local repo

Some includes were oddly missing within a bunch of files.
However, while this will allow it to compile, we still fail two tests -- not sure what these tesets are about.

      Start 31: blackbox_ruleset
31/33 Test #31: blackbox_ruleset .................***Failed    0.40 sec
      Start 32: blackbox_rules
32/33 Test #32: blackbox_rules ...................   Passed    3.15 sec
      Start 33: blackbox_instances
33/33 Test #33: blackbox_instances ...............***Failed    0.87 sec

94% tests passed, 2 tests failed out of 33

We'll need this dockerfile working in order for us to run CRS tests against this :)

Thx I'll test this out locally first.

How goes this testing? We'd love to get this building so we can start running CRS testing against this (even if it is failing)

Seems okay I get the same test failures:
Running tests...
Test project /opt/waflz/build
      Start  1: file_util
 1/33 Test  #1: file_util ........................   Passed    0.00 sec
      Start  2: string_util
 2/33 Test  #2: string_util ......................   Passed    0.00 sec
      Start  3: time_util
 3/33 Test  #3: time_util ........................   Passed    0.12 sec
      Start  4: geoip2_mmdb
 4/33 Test  #4: geoip2_mmdb ......................   Passed    0.01 sec
      Start  5: regex
 5/33 Test  #5: regex ............................   Passed    0.01 sec
      Start  6: md5
 6/33 Test  #6: md5 ..............................   Passed    0.00 sec
      Start  7: jspb
 7/33 Test  #7: jspb .............................   Passed    0.00 sec
      Start  8: instances
 8/33 Test  #8: instances ........................   Passed    0.01 sec
      Start  9: matched_data
 9/33 Test  #9: matched_data .....................   Passed    0.00 sec
      Start 10: profile_acl
10/33 Test #10: profile_acl ......................   Passed    0.11 sec
      Start 11: profile_policies
11/33 Test #11: profile_policies .................   Passed    0.01 sec
      Start 12: shell_shock
12/33 Test #12: shell_shock ......................   Passed    0.00 sec
      Start 13: decode
13/33 Test #13: decode ...........................   Passed    0.00 sec
      Start 14: op
14/33 Test #14: op ...............................   Passed    0.01 sec
      Start 15: var
15/33 Test #15: var ..............................   Passed    0.01 sec
      Start 16: tx
16/33 Test #16: tx ...............................   Passed    0.00 sec
      Start 17: render
17/33 Test #17: render ...........................   Passed    0.00 sec
      Start 18: nms
18/33 Test #18: nms ..............................   Passed    0.00 sec
      Start 19: ac
19/33 Test #19: ac ...............................   Passed    0.00 sec
      Start 20: byte_range
20/33 Test #20: byte_range .......................   Passed    0.00 sec
      Start 21: luhn
21/33 Test #21: luhn .............................   Passed    0.00 sec
      Start 22: parser_json
22/33 Test #22: parser_json ......................   Passed    0.00 sec
      Start 23: kycb_db
23/33 Test #23: kycb_db ..........................   Passed    1.20 sec
      Start 24: rl_op
24/33 Test #24: rl_op ............................   Passed    0.01 sec
      Start 25: challenge
25/33 Test #25: challenge ........................   Passed    0.11 sec
      Start 26: enforcer
26/33 Test #26: enforcer .........................   Passed    3.11 sec
      Start 27: config
27/33 Test #27: config ...........................   Passed    9.12 sec
      Start 28: config_bc
28/33 Test #28: config_bc ........................   Passed    6.95 sec
      Start 29: integration
29/33 Test #29: integration ......................   Passed    2.11 sec
      Start 30: blackbox_access_settings
30/33 Test #30: blackbox_access_settings .........***Failed    0.60 sec
      Start 31: blackbox_ruleset
31/33 Test #31: blackbox_ruleset .................***Failed    0.42 sec
      Start 32: blackbox_rules
32/33 Test #32: blackbox_rules ...................***Failed    0.56 sec
      Start 33: blackbox_instances
33/33 Test #33: blackbox_instances ...............***Failed    0.56 sec

88% tests passed, 4 tests failed out of 33

Total Test time (real) =  25.07 sec

The following tests FAILED:
	 30 - blackbox_access_settings (Failed)
	 31 - blackbox_ruleset (Failed)
	 32 - blackbox_rules (Failed)
	 33 - blackbox_instances (Failed)

I'll have to look into why.  The blackbox tests bring up a standalone http server running the waf engine listening on port 12345.

Found the issue -has to do with our "test fixtures"
root@bf8967bdc8eb:/opt/waflz/build# ctest -R blackbox_ruleset
Test project /opt/waflz/build
    Start 31: blackbox_ruleset
1/1 Test #31: blackbox_ruleset .................***Failed    0.36 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =   0.36 sec

The following tests FAILED:
	 31 - blackbox_ruleset (Failed)
Errors while running CTest
root@bf8967bdc8eb:/opt/waflz/build# env CTEST_OUTPUT_ON_FAILURE=1 ctest -R blackbox_ruleset
Test project /opt/waflz/build
    Start 31: blackbox_ruleset
1/1 Test #31: blackbox_ruleset .................***Failed    0.36 sec
============================= test session starts ==============================
platform linux2 -- Python 2.7.12, pytest-4.5.0, py-1.8.0, pluggy-0.12.0 -- /usr/bin/python
cachedir: .pytest_cache
rootdir: /opt/waflz/tests/blackbox, inifile: pytest.ini
plugins: sugar-0.9.2
collecting ... collected 4 items

../../../tests/blackbox/ruleset/test_ruleset.py::test_OWASP_2_2_9_anomaly ERROR [ 25%]
../../../tests/blackbox/ruleset/test_ruleset.py::test_OWASP_2_2_9_anomaly_low ERROR [ 50%]
../../../tests/blackbox/ruleset/test_ruleset.py::test_OWASP_3_2_anomaly ERROR [ 75%]
../../../tests/blackbox/ruleset/test_ruleset.py::test_OWASP_3_2_anomaly_low ERROR [100%]

==================================== ERRORS ====================================
__________________ ERROR at setup of test_OWASP_2_2_9_anomaly __________________
Fixture "setup_func" called directly. Fixtures are not meant to be called directly,
but are created automatically when test functions request them as parameters.
See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and
https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly about how to update your code.
________________ ERROR at setup of test_OWASP_2_2_9_anomaly_low ________________
Fixture "setup_func" called directly. Fixtures are not meant to be called directly,
but are created automatically when test functions request them as parameters.
See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and
https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly about how to update your code.
___________________ ERROR at setup of test_OWASP_3_2_anomaly ___________________
Fixture "setup_func" called directly. Fixtures are not meant to be called directly,
but are created automatically when test functions request them as parameters.
See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and
https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly about how to update your code.
_________________ ERROR at setup of test_OWASP_3_2_anomaly_low _________________
Fixture "setup_func" called directly. Fixtures are not meant to be called directly,
but are created automatically when test functions request them as parameters.
See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and
https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly about how to update your code.
=========================== 4 error in 0.02 seconds ============================

I'll work on fixing these -apparently calling them this way is deprecated in pytest 4.x.

dammit pytest. Well let me know if you need any help with that -- also please do feel free to ping me when you get it and i'll add these to our tests -- even if they fail.

@csanders-git FYI seems to be fixed locally for me with docker with this PR
Let me know if you still get issues

Yeah sorry for the delay -believe it or not I’m trying to come up to speed
a bit on Docker.  I’ll do this today.  Thanks so much for help here -I’ve
followed your work at Trustwave and on Modsecurity, and really appreciate
having a big name in the community checking out our stuff.
Thanks,
Reed
On Thu, May 30, 2019 at 9:14 AM Chaim Sanders<EMAIL_ADDRESS>wrote:

How goes this testing? We'd love to get this building so we can start
running CRS testing against this (even if it is failing)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/VerizonDigital/waflz/pull/57?email_source=notifications&email_token=AA22J2LSP4EJN6GEQ6L7XYLPX74PFA5CNFSM4HOYMUW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWSYS2I#issuecomment-497387881,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA22J2L5ATQHUWMZ5LZHZQ3PX74PFANCNFSM4HOYMUWQ
.


Keystored cross compilation fixes

Using those patches, it becomes possible to compile keystored without installing anything on the compilation host.

ENABLE_CONFIGURATION is the same as what is already available for the server
KEYSTORED_KEYS_DIR for the server can be overridden from outside, even if it is not detected by cmake

Once the compilation is done, everything has to be configured manually before starting netopeer / sysrepo where it was installed. It looks like this.
Server configuration:

sysrepoctl -i --yang /path/to/ietf-ssh-server.yang
sysrepoctl -i --yang /path/to/ietf-tls-server.yang
sysrepoctl -i --yang /path/to/ietf-netconf-server.yang
for feature in listen ssh-listen tls-listen call-home ssh-call-home tls-call-home; do
sysrepoctl -m ietf-netconf-server -e $feature
done
sysrepoctl -i --yang /path/to/ietf-system.yang
for feature in authentication local-users; do
sysrepoctl -m ietf-system -e $feature
done
sysrepocfg -d startup -i /path/to/stock_config.xml ietf-netconf-server

Keystored configuration:

sysrepoctl -i --yang /path/to/ietf-keystore.yang
sysrepoctl -i --yang /path/to/ietf-x509-cert-to-name.yang
sysrepocfg -d startup -i /path/to/stock_key_config.xml ietf-keystore
mkdir -p /etc/keystored/keys
cp /etc/ssh/ssh_host_rsa_key /etc/keystored/keys/ssh_host_rsa_key.pem
openssl rsa -pubout -in /etc/keystored/keys/ssh_host_rsa_key.pem -out /etc/keystored/keys/ssh_host_rsa_key.pub.pem

Thanks for your time!

Hi Jan,
Thanks for taking the time to check this and sharing the way
you are doing cross-builds.
Maybe I miss-used 'cross-compilation' here. We are trying to
build debian packages on our side, which we are going to be
installed later on another machine.
So what we don't have when we build is actually the target
filesystem.
I think we should have separate packages for sysrepo and
netopeer2, because you can use sysrepo without netopeer2.
When the netopeer2 debian package is built, we should not call
sysrepo binaries really, because those binaries will write in the
/etc/sysrepo directory, which "belongs to" the sysrepo package.
So I am using debian install hooks to do the installation, and netopeer2
depends on syrepo so that /etc/sysrepo is ready when netopeer2
install hooks come.
I can not share the patches, because we have our own build system
and it would not make much sense, but I am able to generate deb
packages with those two patches.
I agree that if something changes in the cmake installation
process, and we don't see it, we're screwed, but I can't think of
another way to do it... We have to be careful and follow the
changes on our side.
I am of course open to other ideas.
Samuel

Ah, now I see where you're coming from. Yeah, as a former Gentoo developer, I also see the value of separate packages even though I doubt anyone would use sysrepo without netopeer2-server anytime soon.
When I was working on my patches, I was thinking about just letting CMake create a script and distributing that as a part of a device/target bootstrap. However, the current approach effectively generates a script for CMake which makes it unusable as-is (we don't typically have CMake on the target system, and we do not want that as a dependency). It is however possible to change the code to generate a shell script instead, and use that shell script both from CMake at install time (in the default settings) and from your post-install DEB/RPM hooks. There would be no duplication of code in that case.

@samuel-gauthier
If I understand your patch correctly, it allows to skip installation of all the models and keys needed by keystored and manually setting KEYSTORED_KEYS_DIR. What you could do is not install keystored at all using cmake but simply copy the *.so into the correct path (that is what installation is reduced to when skipping the rest). I have no problem in adding the possibility to define KEYSTORED_KEYS_DIR yourself the way you did in this pull request (so I would merge that small change if in separate pull request). What do you think?
Regards,
Michal

Hi all,
Here is a new version, that splits the installation tasks into bash scripts that can be called or not, depending on the options given to cmake, done for keystored and server.
Regards,
Samuel

Hi Samuel,
very nice, thank you!
Regards,
Michal


[kitty] paste hangs when the permission hasn't been set

When I do osc52 --paste that terminal tab hangs. If I manually kill osc52, the shell in that tab will resume but need reset to display program outputs properly.
Things work correctly if kitty is configured to allow pasting.
It would be good if osc52 displayed an error instead of hanging.

Should be fixed now with v0.2.2


Add support for react-native 0.12.0

Thanks! :smile:

Thank you Kane

No problems at all - thanks for making such a great component! :)
On Thu, Oct 15, 2015 at 6:53 PM Farid from Safi<EMAIL_ADDRESS>wrote:

Thank you Kane
—
Reply to this email directly or view it on GitHub
https://github.com/FaridSafi/react-native-google-places-autocomplete/pull/1#issuecomment-148309459
.


Add 'iss' claim to jwt key proof

According to spec iss claim is optional and MUST be a client_id.
https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-<IP_ADDRESS>-<IP_ADDRESS>
I didn't make it optional, I used the same pattern as for c_nonce, which is also OPTIONAL by spec, but required by the code.
@babisRoutis please check if this PR is valid.

Hi @ydanneg
I understand that this is a fix for #137 .
Is this the case?

@ydanneg Can you please run ./gradlew spotlessApply and then commit & push the formatted code?

Hi @ydanneg
I understand that this is a fix for #137 . Is this the case?

Somehow I missed this issue :) Seems you right, this is the one.

As a first comment (haven't check PR in detail), I notice that clientId has been added to various classes/methods.
Yet clientId is constant known before using the Issuer. That is why this attribute can be found already within OpenId4VCIConfig.
So, perhaps, instead of adding the clientId we could just make available the configuration (if it is not) where we need to use it

As a first comment (haven't check PR in detail), I notice that clientId has been added to various classes/methods. Yet clientId is constant known before using the Issuer. That is why this attribute can be found already within OpenId4VCIConfig.
So, perhaps, instead of adding the clientId we could just make available the configuration (if it is not) where we need to use it

In particular I think that we just need to add clientId as a private property of RequestIssuanceImpl

As a first comment (haven't check PR in detail), I notice that clientId has been added to various classes/methods. Yet clientId is constant known before using the Issuer. That is why this attribute can be found already within OpenId4VCIConfig.
So, perhaps, instead of adding the clientId we could just make available the configuration (if it is not) where we need to use it

thanks for the tip, now it looks much better

Dear @ydanneg
Current PR just reverts the changes that were introduced, which introduces commits not actually needed and in addition there are some clientId(s) introduced that need to be removed.
May I ask you to create a new PR, applying just the change to RequestIssuanceImpl?
I think it would more "clean".
What do you think?
PS : You just removed them :smile:

Dear @ydanneg
Current PR just reverts the changes that were introduced, which introduces commits not actually needed and in addition there are some clientId(s) introduced that need to be removed.
May I ask you to create a new PR, applying just the change to RequestIssuanceImpl? I think it would more "clean". What do you think?
PS : You just removed them 😄

Can't you just squash it?

Dear @ydanneg
Current PR just reverts the changes that were introduced, which introduces commits not actually needed and in addition there are some clientId(s) introduced that need to be removed.
May I ask you to create a new PR, applying just the change to RequestIssuanceImpl? I think it would more "clean". What do you think?
PS : You just removed them 😄

Can't you just squash it?

nevermind.. i will do a new one :)

will do another one, with a single commit


Send back repo content via web socket

Steps:

[ ] create new endpoints ws/stage in back and front (test)
[ ] create backRepoContent struct for marshalling the content
[ ] marshall it on the back
[ ] unmarshall on the front

currently, when a GET is performed, AstructDBs are copied into AstructAPI.
	// slice that will be transmitted to the front
	astructAPIs := make([]orm.AstructAPI, 0)

	// for each astruct, update fields from the database nullable fields
	for idx := range astructDBs {
		astructDB := &astructDBs[idx]
		_ = astructDB
		var astructAPI orm.AstructAPI

		// insertion point for updating fields
		astructAPI.ID = astructDB.ID
		astructDB.CopyBasicFieldsToAstruct_WOP(&astructAPI.Astruct_WOP)
		astructAPI.AstructPointersEncoding = astructDB.AstructPointersEncoding
		astructAPIs = append(astructAPIs, astructAPI)
	}

	c.JSON(http.StatusOK, astructAPIs)

one needs to perform the same thing when web socketing


Support ECEF (earth-centered, earth-fixed) coordinates

Quantised mesh format requires Earth-centered Fixed coordinates, which is also suitable for visualisation of other astronomical bodies then Earth #49

Fixed in https://github.com/heremaps/tin-terrain/tree/ecef-coordinates.fester.

Fixed in #54


Different mouse overlays for right and middle clicks

Would be nice to have those for making video tutorials clearer.

I can't think of a good design. Here's a build of what I've implemented: https://ci.appveyor.com/api/buildjobs/u1rw8blnlkm8vuxp/artifacts/temp%2FCaptura-Portable.zip
Suggestions are welcome

Nice approach! The visuals look somewhat weird, but in general I like it.
In other apps it is usually solved either by depicting the mouse (a bit intrusive imho),
either using two different colours: e.g. yellow for left click, blue for right. This would be my favourite, I guess.

So, I guess we can go for the color approach. Would come up with it ASAP.

Here's the build for testing: https://ci.appveyor.com/api/buildjobs/o5itknb73dgldibm/artifacts/temp%2FCaptura-Portable.zip
Colors can be changed in Configure | Overlays | Mouse Clicks

#187 Merged. This feature is now in master branch.
Would be available in next release.


upgrade to<EMAIL_ADDRESS>

This pull request addresses issue #44.
All tests remain passing after the update.

Coverage remained the same at 100.0% when pulling fdb7215533da15c319d3374f96a0feb855eabe0a on syntactic-salt:upgrade-no-case into c61014e5b9ffd8efa1222bc28a10f7aa64eabbd5 on blakeembrey:master.

@blakeembrey I noticed pull request #41 is trying to resolve the same security vulnerability as I am here. #41 has been sitting around for a couple months. Is this project dead?

Dead seems a bit over the top, it just doesn't really require updates and I have things I needed to be doing instead of OSS. Anyone installing the library would have been getting that latest no-case release either way, so I wasn't in a rush to update. I'll merge #41 now, thanks for the PR!

Oh, the reason I didn't merge his immediately was because he changed the package.json version. If I needed to go in a fix stuff or back and forth when I really didn't have time, I just skipped it.


fix(rejected): add a resolve reference for rejected items

Goal
This makes it so that RejectedCorpus item is a field that can be resolved by reference from the rest of the API.
https://pocket.slack.com/archives/CTLKW5WCF/p1652286052972369
I'd love feedback/perspectives on:

Is this the right idea??

Implementation Decisions

Deployment steps

[ ] Database migrations?
[ ] Secrets?
[ ] FOR POCKET DEVELOPERS ONLY - Post in #changelog:

Write a #changelog message using our best practices if this PR (potentially) impacts users. Describe the 'why' and 'what'. @mention relevant teams. Link to this PR.

References
JIRA ticket:

Link to JIRA ticket

Issue:

Link to GitHub issue

Documentation:

Project doc

so the goal of this query is to make sure the UI calls this, filter out prospects if they exist in this list and display the remaining items that's not in this list?


NotImplementedError raised when using function call as argument of message aggregate

With my current SPDM spec I get the following bugbox:
------------------------------ RecordFlux Bug ------------------------------
RecordFlux 0.6.0-pre
RecordFlux-parser 0.10.0
ruamel.yaml 0.17.21
attrs 21.4.0
pydotplus 2.0.2
z3-solver <IP_ADDRESS>
pydantic 1.9.0
icontract 2.6.1

Optimized: False

Command: /tmp/tmp.9hdAmOjNM5/venv/bin/rflx generate build/specs/CHALLENGE_AUTH=True,KEY_EXCHANGE=True,RESPOND_IF_READY=True/spdm_emu.rflx build/specs/CHALLENGE_AUTH=True,KEY_EXCHANGE=True,RESPOND_IF_READY=True/spdm_proxy.rflx build/specs/CHALLENGE_AUTH=True,KEY_EXCHANGE=True,RESPOND_IF_READY=True/spdm_requester.rflx build/specs/CHALLENGE_AUTH=True,KEY_EXCHANGE=True,RESPOND_IF_READY=True/spdm_responder.rflx build/specs/CHALLENGE_AUTH=True,KEY_EXCHANGE=True,RESPOND_IF_READY=True/spdm.rflx --debug -d build/debug/generated

Traceback (most recent call last):
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/cli.py", line 201, in main
    args.func(args)
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/cli.py", line 259, in generate
    generator = Generator(
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/generator.py", line 141, in __init__
    self.__generate(model, integration)
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/generator.py", line 220, in __generate
    self.__create_session(s, integration)
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/generator.py", line 231, in __create_session
    session_generator = SessionGenerator(
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/session.py", line 219, in __init__
    self._create()
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/session.py", line 249, in _create
    state_machine = self._create_state_machine()
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/session.py", line 357, in _create_state_machine
    unit += self._create_states(self._session, composite_globals, is_global)
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/session.py", line 844, in _create_states
    *[
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/session.py", line 847, in <listcomp>
    for s in self._state_action(
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/session.py", line 1893, in _state_action
    result = self._assign(
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/session.py", line 2123, in _assign
    return self._assign_to_message_aggregate(
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/session.py", line 2352, in _assign_to_message_aggregate
    size = self._message_size(message_aggregate)
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/generator/session.py", line 3190, in _message_size
    return message.size({model.Field(f): v for f, v in message_aggregate.field_values.items()})
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/model/message.py", line 986, in size
    proof = expr.Equal(expr.Size("Message"), message_size).check(
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/expression.py", line 263, in check
    return Proof(self, facts)
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/expression.py", line 60, in __init__
    solver.add(f.z3expr())
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/expression.py", line 1800, in z3expr
    right = self.right.z3expr()
  File "/tmp/tmp.9hdAmOjNM5/venv/lib/python3.9/site-packages/rflx/expression.py", line 1488, in z3expr
    raise NotImplementedError
NotImplementedError

----------------------------------------------------------------------------

Unfortunately I wasn't able to come up with a good reproducer yet. I already created this ticket to track further findings.

It looks like you tried to use a message aggregate with a function call as an argument. When a message aggregate is used, the generator determines the size of the resulting message to check if the serialized message fits into the available buffer. For the size determination, all arguments of the message aggregate are converted to an Z3 expression. This conversion failed for the Call argument. This issue is related to #1019, but it could make sense to improve the error message until #1019 is implemented.

@jklmnn Can you please add a small reproducer for this issue?

I tried to reproduce the issue with the following spec:
package Test is

   type Element is mod 2 ** 8;

   type Message is
      message
         E : Element;
      end message;

   generic
      Channel : Channel with Readable, Writable;
      with function Get_Element return Element;
   session Session with
      Initial => Start,
      Final => Terminated
   is
      Msg : Message;
   begin
      state Start
      is
      begin
         Msg := Message'(E => Get_Element);
      transition
         goto Send
      exception
         goto Terminated
      end Start;

      state Send
      is
      begin
         Channel'Write (Msg);
      transition
         goto Terminated
      end Send;

      state Terminated is null state;
   end Session;

end Test;

Running the generator produces the following error:
Parsing test.rflx
Processing Test
Generating Test::Element
Generating Test::Message
Generating Test::Session
test.rflx:22:31: generator: error: Call with integer type "Test::Element" (0 .. 255) as value of message field not yet supported

As the issue is also handled in #1019 and the error message has been improved I'll close this issue.


[BUG] [v2.10] Failed to install system chart fleet: specified version 105.0.2+up0.11.2-rc.2 doesn't exist in the index

Rancher Server Setup

Rancher version: v2.10-87b97590837835650d045937b669ee0206604758-head
Installation option:

Helm Chart, Kubernetes Cluster and version (k3s): v1.30.5+k3s1

User Information

What is the role of the user logged in? Admin

Describe the bug
After installing Rancher, observing error: Failed to install system chart fleet: specified version 105.0.2+up0.11.2-rc.2 doesn't exist in the index
Probably build.yaml needs to be updated.
Expected Result
Fleet chart should be installed.
Logs
W1213 05:37:14.179888      39 warnings.go:70] v1 ComponentStatus is deprecated in v1.19+
2024/12/13 05:37:14 [INFO] Watching metadata for upgrade.cattle.io/v1, Kind=Plan
2024/12/13 05:37:15 [ERROR] Failed to install system chart fleet: specified version 105.0.2+up0.11.2-rc.2 doesn't exist in the index
2024/12/13 05:37:15 [ERROR] Failed to install system chart fleet-crd: specified version 105.0.2+up0.11.2-rc.2 doesn't exist in the index
2024/12/13 05:37:15 [ERROR] Failed to install system chart fleet: specified version 105.0.2+up0.11.2-rc.2 doesn't exist in the index
2024/12/13 05:37:15 [ERROR] Failed to install system chart fleet-crd: specified version 105.0.2+up0.11.2-rc.2 doesn't exist in the index
2024/12/13 05:37:15 [ERROR] Failed to install system chart fleet-crd: specified version 105.0.2+up0.11.2-rc.2 doesn't exist in the index

Fixed on v2.10-ca82c9717ceb8ad2d0cc54f584d8adbae41a2341-head, closing issue.
NAME        CHART       VERSION            RELEASE NAME   RELEASE VERSION   STATUS
fleet       fleet       105.0.2+up0.11.2   fleet          5                 deployed
fleet-crd   fleet-crd   105.0.2+up0.11.2   fleet-crd      1                 deployed

Verified after Github action process ended and Docker images where built Fleet is correctly deployed:
https://github.com/rancher/fleet-e2e/actions/runs/12313608327

PS: this happens sometimes. If you run a test right in the moment the image is being built nothing is seen.


Update active-directory-passwords-set-expiration-policy.md

Removed the preceding slash in front of the $true or $false values in the PowerShell script. Their presence made no sense, and when I copied and used the scripts they did not work unless I removed them.

Hi @JackUkleja, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@JackUkleja : Thanks for your contribution to the Azure documentation! The author, @curtand, has been notified to review your proposed change.

Thanks @JackUkleja for your contribution. I need to verify the code with my PM, who will return Monday. We'll get this published ASAP!


[BUG]: Fix Kubernetes@1 job to officially accept command rollout.

New issue checklist

[x] I searched for existing GitHub issues
[x] I read pipeline troubleshooting guide
[x] I checked how to collect logs

Task name
Kubernetes
Task version
1
Issue Description
Description
When a command "rollout" is used with Kubernetes@1 job, the extension reports "Value is not accepted" which is completely false: job works as intended.

(reports "not accepted", however it does work)
This was already reported on StackOverflow 4 years by someone else: https://stackoverflow.com/questions/64268770/azure-devops-pipeline-kubectl-task-command-rollout-unavailable
I think this misinformation really needs to get fixed. I almost ended up thinking your Kubernetes job does not accept rollout command and that I'd have to use "delete" on pods found via labels instead of a normal, graceful rollout restart.
Actual code which needs fixing
You can see here (azure-pipelines-tasks/Tasks/KubernetesV1/task.json)(https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/KubernetesV1/task.json#L141-L154) that rollout is not one of the "accepted" commands, despite it being very important and working nonetheless.
I gather it'd be enough to just add the command here in the JSON object.
Environment type (Please select at least one enviroment where you face this issue)

[x] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
MacOS
Relevant log output
There are no logs, it's just an issue with a missing key.
Full task logs with system.debug enabled

 N/A

Repro steps
No response

Hi @mislavmatijevic
Could you please share your yaml pipeline by hiding the unwanted details?

Hi @v-schhabra, thanks for reaching out to me!
This is my YAML pipeline file restart-pod.yml with unwanted details hidden:
parameters:
    - name: productName
      type: string
    - name: namespace
      type: string
    - name: azureSubscription
      type: string
    - name: azureResourceGroup
      type: string
    - name: kubernetesCluster
      type: string

steps:
    - bash: |
          #sets mock 'namespace' variable for this issue comment
          variable="${{ parameters.namespace }}-mock-for-azure-issue"
          echo "##vso[task.setvariable variable=namespace]$variable"
      displayName: Resolve namespace

    - task: Kubernetes@1
      name: RestartPod
      displayName: Restart ${{ parameters.productName }}'s pods on Kubernetes
      inputs:
          connectionType: 'Azure Resource Manager'
          useClusterAdmin: true
          azureSubscriptionEndpoint: ${{ parameters.azureSubscription }}
          azureResourceGroup: ${{ parameters.azureResourceGroup }}
          kubernetesCluster: ${{ parameters.kubernetesCluster }}
          namespace: $(namespace)
          command: rollout
          arguments: restart deployment ${{ parameters.productName }} -n $(namespace)


Spacing issues on event template

Spacing between components on the event template is too big. seems like its accounting for the background colours but we dont have this option on the events. Example here: https://energyvision.app.radix.equinor.com/investors/testing

related to #738

Probably this has been changed already, but we are rendering an empty div on the page still, so we can use this issue to fix it instead:

I did not use a feature flag for this since it is such a tiny change.

lgtm!


Transformation fails if more than one root element exists

I've noticed that if there's more than one rootSelector transformation fails with a Font declaration not found in body. I believe the reason for this is the plugin does not collect and match multiple elements.

Thanks @json-uk — I'll take a look into this.

This should be now working as expected. Let me know if you run into any further issues.

@markgoodyear thanks for turning this around so quickly


[Telink] Cleanup Docker image

Change overview

Cleanup Telink Docker image

Testing
Tested manually.
Steps:

Build image
Run docker
Check if Telink examples able to be built successfully

@andy31415 Could you help to review optimisation of Telink Docker file
Here is PR with switch all builds to new docker version to check if nothing is brocken https://github.com/project-chip/connectedhomeip/pull/29886


dry-run rebase of cep-15-accord on cep-21-tcm [DO NOT MERGE]

CircleCI: https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-17092-rebase-on-trm

https://app.circleci.com/pipelines/github/maedhroz/cassandra/768/workflows/d2c10a30-c256-4192-9947-b73a882ac334

This branch has replaced the cep-15-accord branch (which is now open for development again).


status: ledger crash in CI

https://storage.googleapis.com/istio-prow/logs/integ-security-k8s-tests_istio_postsubmit/1352408471101771776/artifacts/security-f8c21f5b05e944e893d8b0/_suite_context/istio-state-557506131/cluster-0/istiod-6b5db965cc-s2krb_discovery.previous.log
https://prow.istio.io/view/gs/istio-prow/logs/integ-security-k8s-tests_istio_postsubmit/1352408471101771776

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/30288/integ-security-multicluster-tests_istio/1352676133304274944

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/30288/integ-security-multicluster-tests_istio/1352676133304274944

I sent a revert
On Fri, Jan 22, 2021 at 10:23 AM Steven Landow<EMAIL_ADDRESS>wrote:

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/30288/integ-security-multicluster-tests_istio/1352676133304274944
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/30292#issuecomment-765601826, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXM4SOIGYSPSH3HUFUTS3G7D3ANCNFSM4WNXRVBA
.

I sent a revert
On Fri, Jan 22, 2021 at 10:23 AM Steven Landow<EMAIL_ADDRESS>wrote:

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/30288/integ-security-multicluster-tests_istio/1352676133304274944
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/30292#issuecomment-765601826, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXM4SOIGYSPSH3HUFUTS3G7D3ANCNFSM4WNXRVBA
.


Create ptc.txt

Add the domain of Polytechnic College<EMAIL_ADDRESS>to the list of domains

Has<EMAIL_ADDRESS>and @docent.ptc.edu.sr email adresses

@MassiveAtoms Pull request merged. Thank you!


Kargo Integration

Next Steps
Manage the resources in the Quickstart

[x] Credentials - Need to manually create a github app secret as documented here and add to mkcert -CAROOT/kargo.yaml.  Also need to manage the namespace.  Not ideal.
[x] Projects - Managed like namespaces, if the kargo.akuity.io/project: "true" label is set on the namespace.
[x] Warehouse
[x] Stages dev, test, stage, prod
[x] Re-orient to 3 projects: bank-security, bank-backend, bank-web.
[x] Env stages are an aspect of each project.
[x] Kargo Project Namespace for each Project.
[x] ArgoCD Update.

Next step, resolve:
failed to run step "argocd-update": error getting Argo CD Application "dev-bank-web-frontend" in namespace "argocd": Argo CD Application "dev-bank-web-frontend" in namespace "argocd" does not permit mutation by Kargo Stage dev in namespace dev-bank-frontend

Gotchas

GitHub App private key needs to be double base64 encoded.  See https://github.com/akuity/kargo/issues/3055

Summary
With Kargo v1.1.0 integrate by having holos write a kustomization.yaml file artifact.  Integrate with Kargo using:

git-clone
kustomize-set-image
kustomize-build
git-commit
git-push

Need to prototype this out for one of our own internal apps.  Do it with holos server.
The downside is holos no longer produces the final manifests, kargo does, but the fully rendered manifests are still in Git and this integration can occur on a component by component basis.
Custom Promotion Steps
The ideal integration is with the External/Custom Promotion Steps planned for Kargo v1.3.0.
Refer to https://github.com/akuity/kargo/issues/2996
Issues / Discussions
Track work toward custom/external pipeline steps.

ui: support for new steps yaml-update and http
Kargo integration with Holos
Multiple pipelines
File/Directory/Patch based promotion
refactor: promotion mechanisms --> promotion directives

Might be possible to fiddle JSON using CEL, I asked Krancour about this here:
https://github.com/akuity/kargo/issues/1250#issuecomment-2496109066

Got this mostly working up to the argocd-update step.  At this point it became clear we need to create an additional namespace for the project.
A Kargo Project has a special Namespace of the same name to collect all of the kargo resources.  See Working with Projects

Each Kargo project is represented by a cluster-scoped Kubernetes resource of type Project. Reconciliation of such a resource effects all boilerplate project initialization, including the creation of a specially-labeled Namespace with the same name as the Project. All resources belonging to a given Project should be grouped together in that Namespace.

This is close to the current Holos definition of a Project, but not quite the same.  At present, Bank of Holos is split up into 3 projects per each of the 4 environments, for 12 projects total.
If we were to re-orient our model to align with Kargo, then we would create 3 projects with environment stages nested within them:

bank-security
bank-web
bank-backend

This could still fit our alignment with "projects are security boundaries" with the additional consideration that environments may further restrict access, e.g. prod bank web is still part of the bank-web project, but has restricted access compared to dev-bank-web.

Implemented the prod/nonprod split and promotion stages from dev, test, staging and prod east to west in https://github.com/holos-run/bank-of-holos/pull/11
Recorded a quick video about this at https://www.youtube.com/watch?v=m0bpQugSbzA
Tagged in v0.6.2 and documented at https://github.com/holos-run/bank-of-holos/blob/v0.6.2/docs/kargo.md


Pass URLs as SPARQL queries param

Allow to pass URLs instead of only repository path as SPARQL queries

FTP URL
GitHub URL (https://github.com/vemonet/data2services-insert/tree/master/insert-biolink/hgnc)

Iterate over subdirectory to execute all .rq files

Implemented but we don't iterate over subdirectories (not worth the pain)


(ERROR) No ad to show

Hi,
Anyone can help me, pls ?
I am using this library to show ads on my app. BannerAd and InterstitialAd works fine, but RewardedAd and RewardedInterstitialAd don't work for me.
I receive this error and I don't know what to do:
{
	"code": "E_AD_LOAD_FAILED",
	"domain": "com.google.admob",
	"message": "Request Error: No ad to show.",
	"nativeStackIOS": [
"0   Veek                                0x0000000102abc9f7 RCTJSErrorFromCodeMessageAndNSError + 135",
"1   Veek                                0x000000010281e8fc __69-[RNAdMobRewarded requestAd:unitId:requestOptions:resolver:rejecter:]_block_invoke + 252",
"2   Veek                                0x0000000102ff85b4 GAD_GADRewardedAd_x86_64_8_9_0 + 921",
"3   Veek                                0x0000000102f67231 GAD_GADFullScreenAd_x86_64_8_9_0 + 1553",
"4   libdispatch.dylib                   0x00000001178fe578 _dispatch_call_block_and_release + 12",
"5   libdispatch.dylib                   0x00000001178ff74e _dispatch_client_callout + 8",
"6   libdispatch.dylib                   0x000000011790db3f _dispatch_main_queue_callback_4CF + 1152",
"7   CoreFoundation                      0x0000000114b168f8 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ +9",
"8   CoreFoundation                      0x0000000114b11169 __CFRunLoopRun + 2781",
"9   CoreFoundation                      0x0000000114b101a7 CFRunLoopRunSpecific + 567",
"10  GraphicsServices                    0x000000011913fd85 GSEventRunModal + 139",
"11  UIKitCore                           0x000000012408a4df -[UIApplication _run] + 912",
"12  UIKitCore                           0x000000012408f39c UIApplicationMain + 101",
"13  Veek                                0x000000010201e920 main + 112",
"14  libdyld.dylib                       0x000000011798dbbd start + 1",
"15  ???                                 0x0000000000000003 0x0 + 3"
],
	"userInfo": {
		"NSLocalizedDescription": "Request Error: No ad to show.",
		"gad_response_info": null
	}
}

On the same screen I display the banner without any problems, but the RewardedAd gives an error.

Snippet of my code:
import React from 'react';
import {RewardedAd} from '@react-native-admob/admob';

import {AdBanner} from '@~/components/atoms/AdBanner';
import * as Layout from '@~/components/organisms/layout';
import {Minimal} from '@~/components/templates/minimal';

export const CheckIn = ({navigation}: CheckInProps) => {
  const rewardId = Platform.OS === 'android'
     ? 'ca-app-pub-3940256099942544/5224354917'
     : 'ca-app-pub-3940256099942544/1712485313';

  const AdReward = RewardedAd.createAd(rewardId, {requestNonPersonalizedAdsOnly: false});

  useEffect(() => {
    AdReward.load();

    AdReward.addEventListener('adLoaded', (value: any) =>
      console.info('AD LOADED:   ', value),
    );

    AdReward.addEventListener('adFailedToLoad', (value: any) =>
      console.error('ERROR ON AD LOAD:  ', value),
    );

  }, [AdReward]);

  return (
    <Minimal
      theme="dark">
      <View style={styles.banner}>
        <AdBanner
          iosId="ca-app-pub-5125007708919035/8379546411"
          androidId="ca-app-pub-5125007708919035/5833274125"
        />
        <Layout.Padding>
          <Button
            transparent
            dark
            full
            onPress={() => {
              console.info('SHOW ADREWARDED');
              AdReward.show();
            }}>
            <Text>Fazer checkin</Text>
          </Button>
        </Layout.Padding>
      </View>
    </Minimal>
  );
};

I'm creating hook initialize() and running within App.js
My hook initialize:
const config = {
  maxAdContentRating: 'G',
  tagForChildDirectedTreatment: false,
  tagForUnderAgeConsent: false,
};

export const initAdMob = async (callback?: () => void | undefined) => {
  await AdMob.initialize()
    .then(value => {
      AdMob.setRequestConfiguration(config);
      console.info(value);
    })
    .catch(e => console.error(e));

  if (callback) {
    return callback();
  }
};

My execution:
export const App = () => {
  const [loading, setLoading] = useState(true);

  useEffect(() => {
    initAdMob(() => setLoading(false));

  }, [loading]);

...

This is maybe a problem related to your ad unit or your ad account. Find solution here

Perfect! I am now able to load the award-winning ads, but I am having another problem.
The "adLoaded"  event returns that the video was loaded, but it does not display the video, returning the error:
"Possible Unhandled Promise Rejection
Error: Add is not ready."
Only after a while, I am able to view the video.
Is there another way to identify if the video is really ready to be shown or will it be necessary to create a correction for the return of this event?

@RenanNeitzel Hi, sorry for late response. Please open new issue if you have other suggestions or bug to report.


Uncaught ReferenceError: TOUCH_ACTION_COMPUTE is not defined

Simply plug in the script and immediately writes an error

@Valonix could you provide details about the platform and browser in use, hammer version, and whether you are using hammer on it's own or via the jquery plugin?

Chrome
jquery last version
i use ur previos 1.x version and all ok.
via jquery an own

Closing as not could not replicate.  If you provide a jsbin or codepen demonstrating the issue I'll revisit this.

From a Stack Overflow response:

You have probably reference the wrong js file in your webpage. If using the npm package make sure to reference  and NOT


kernel: Clean up mailbox async msg configuration

Remove confusing and duplicate async message configuration switches for mailboxes.

If you want to do #if'ery cleanup and have the time, usually it's preferable to try to remove the big block #if's altogether, replacing them by IS_ENABLED() in regular C syntax wherever possible. You only need the preprocessor to hide things like conditional struct fields (which would be syntax errors), but you could do that in a local place. Unreferenced C functions get dropped from the link automatically (though statics have to have an "inline" also to prevent a warning).
In particular, it looks to me that mailbox code only actually cares about the _async_sem field being conditional, so you could wrap that in a tiny accessor function that returned a compiler-visible NULL if not configured.

Good point and thanks for the input. I will try to solve this in a follow up PR.
With this I wanted to resolve the multiple confusing #if (CONFIG_NUM_MBOX_ASYNC_MSGS > 0)  in between the big #if(CONFIG_NUM_MBOX_ASYNC_MSGS > 0) statments


i'm using bootstrap-vue-3  & getting  error

Uncaught ReferenceError: BToast is not defined
please tell me how to  use bootstrap toast in vue.js

I think Btoast is in development.
check it out: https://cdmoro.github.io/bootstrap-vue-3/reference/parityList.html#toasts

Thankyou
@Mowa-zee

I'm on 0.0.13 and using https://cdmoro.github.io/bootstrap-vue-3/components/Toast.html
Can you try again?

Great, please close the issue


Several Flax Improvements

Now does a better job at running through flax in the order that it's
planted, operates a little faster. Works on a 4x4 planting grid and 6x6
seed grid (reliably with 4 seeds per harvest). Additionally, added an
input box to choose which type of Flax to use at start time.

Thanks for the updates!  My update server that delivers these to Automato is currently down, so this probably won't go out for at least a few hours.


bug auto indent

Hi,
I have discovered that if you start a new bullet underneath another bullet, the new bullet will auto indent. I do not like this behavior as I often want to create lists with no indent. When creating bullets, I use the dash (-).

The auto indent is by design. I will check how to improve it to meet most users' requirement.


pub upgrade hangs indefinitely for status_tool on Mac

Dart 1.9.1 on Mac

Get status tool https://github.com/dart-lang/status_tool
in the package directory
pub install (seems to work)
pub upgrade (hangs forever)

Using 'pub --verbosity all upgrade' We see no output after the HTTP requests complete
Seen on two different macs, using both the python and Dart pub servers – it doesn't seem that this is a server issue

This issue has been moved to dart-lang/pub#1275.


fix: removing circular references before ignoring keys

:tada: This PR is included in version 1.107.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ Samsung has degraded performance

In e1011de, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2164 ms

Resolved: Samsung performance has improved in dfa90ba.


Block Storage Support

For users that are running in K8S, we would like access to a Block Storage device for faster performance rather than using the Cloud Native abstraction layer to the Data Storage. With Block Storage, we can mount the storage to the Pod as a shared file system across numerous pods.

Just to clarify: do you mean you would like to mount this same block device on multiple machines at the same time and have us write data to it from all active servers?  This is model you might see in MS SQL Servers sharing a platter of Fibre Channel disks and with a small 2nd partition that's used to manage the quorum, but on the main storage platters isnt a POSIX like filesystem its a file layout unique to MS SQL.  Is that what you had in mind?
Our current planned JS model is that each machine would have an independent storage and would contribute that resources to a pool of available resources. Rather than any form of shared file system requirement at all, in fact I don't think we will support something like the same NFS mount on all machines - no form of sharing the same storage between 2 JS nodes.
I also don't think we'll be writing to a raw block device - we'd require a POSIXish filesystem for the near storage.
We might support archival quality storage to say S3, but not as a primar store.

Closing this, not sure what the desire is here but feel free to reopen with more information


set button ID from spacebars helper arg

Just like modal component https://github.com/fabienb4/meteor-materialize-components/blob/master/components/basic/modal.html#L2. eventually add support for classes too?

Use options to add any attribute you want, except class and href (these two are on their own).
  options = { id: "my-id" };

I could add a way to add custom classes though. Right now classes are generate automatically depending the arguments you pass to the template (see classes).

I am trying to quickly prototype the app in spacebars templates without using collections or schema validation (yet), but I don't think it's possible to set the id via the options dynamic spacebars attribute. So this means adding the { id: "my-id" } object literal to the template's context in a helper, which feels a little cumbersome, since I can set other parameters via spacebars dynamic attributes. But I understand if this is not the main use case you are building the module library for.