[WIP] RNN with bucketing and mask - R package

Since there wasn't an API yet for bucketing and masking in the R-package, I started building some functionnalities to address this. Inference from iterator is also provided. Further work remains to render the interface more flexible to different structures (seq-to-seq vs. seq-to-single used to demo). I've tried to stay as close as possible to the current model.R for standard feedforward training.
I've detailed the approach and put the code here:
https://github.com/jeremiedb/mxnet_R_bucketing
I was wondering if there were already plans to develop bucketing utilities in the R package. If not, would you see this approach as a decent one it and worth buildind further on it?
There are some specificities with how I dealt with the iterarators, it assumes that a pre-processing is performed to put the data and label arrays in lists for each bucket. Also noticed that shared module options seems not supported in the symbol_bind operator, not sure if this may result in memory management issues.
In any case I can turn it into an example to add to the docs. CNN examples reaches 89% accuracy on IMDB sentiment in few minutes on laptop CPU.

@thirdwing

@jeremiedb Really thank you for this.
Sorry that I am occupied by thesis right now.

@jeremiedb The first version of refactor can be found in https://github.com/thirdwing/mxnet/tree/r_rnn_refactor1

The RNN bucketing example has been added into https://github.com/apache/incubator-mxnet/tree/master/example/rnn/bucket_R


Shaka 2.5.9 disable skip-forward on live HLS when given multiple new fragments?

What version of Shaka Player are you using?
2.5.9
Please ask your question
In live HLS playback, we noticed that if the player is given multiple new fragments in the HLS sliding window (instead of seeing one new fragment every <fragment duration> seconds), we see the player ends up skipping to more recent fragments in the playlist. Is there a way to not have this behavior, such that the player will continue playback from its current position?
Thanks, Kevin

Please provide a sample manifest URL (not just the text).  You can send it privately to<EMAIL_ADDRESS>if you prefer.  Also, does the content play on Safari?  Which browser are you using?
Also, 2.5.9 is fairly old, we just released 2.5.23 and 3.1.1 you should try instead.

Hi @TheModMaker . Thank you for your help. I have sent an email to the above address with manifest URL and a pre-recorded testing video. Let me know if any additional information is needed.
Thanks, Kevin

I believe this could have to do with the size of the seek window.  By default, this is zero for HLS live, which means that seeking is effectively disabled and playback always happens close to the live edge.  I'm guessing based on the symptoms, though I have not reproduced the issue myself yet.
Please try configuring the player with something like this before playback:
player.configure(
    'manifest.availabilityWindowOverride',
    100 /* seconds */);

This sets how much the user will be allowed to seek during playback.


Error: .../relationshipeditor/relations/isallowedentity (not found)

Hi Lars-erik,
I just integrated your package with my project through nuget manager and I was successful throughout the steps of using it until such one that allows me to finally add a selected node to the "related stories" list. Here is a screenshot of error surfacing right after I selected a node:
(I tried rebuilding, reloading, logging in/out, but to no avail. It looks as though I am missing a file and the one that is specified is not in fact physically present in the project. Is the file in question part of the package? Am I supposed to do something related to Umbraco internally prior to installing any plugin? By the way, this the Umbraco that I currently have: version 7.7.2 assembly: 1.0.6484.21641. Thanks.)

Umbraco 774 solved the problem for me


iOS 17, beta 1: new exceptions in StreamDecoder

Hello!
I'm doing some testing of our app under Xcode 15 beta and iOS 17 beta, and I've noticed some new errors around network response decoding that are resulting in failures to load content across all of our screens. From what I can tell, these new errors are being produced in the underlying j2objc JRE. Here's what I'm seeing:
iOS 16 and below
In current production versions of iOS, this snippet of code is able to handle reading the network response as a stream from the connection, can parse the JSON using the GSON library, and will return a model object of any type Java type T:
protected T parseResponse(HttpURLConnection connection) {
        InputStream stream = connection.getInputStream();
        Reader reader = new InputStreamReader(stream, Charset.forName("utf-8"));

        try {
            T response = gson.fromJson(reader, mResponseType.getType());
            /* ... callback with model object ... */
        } catch {
            /* ... error handling ... */
        }
}

iOS 17, beta 1
Under iOS 17 beta 1, the following error message is now logged from the catch block above during all network requests:
java.lang.AssertionError: sun/nio/cs/StreamDecoder.java:301 condition failed: assert rem > 0;

This appears to be caused within fromJson(...) above when I pass in the reader.
I've double checked and the network response is returning HTTP status code 200 and contains valid JSON, so it does not appear to be a data problem. The models and returned data schema are the same as well.
Summary
There appears to be a possible new error in StreamDecoder as of iOS 17 beta 1 which is causing reading the stream to fail.

Hello!
I've been probing more into this recently and think I have found the root issue.
Here is a minimal test case that will work on iOS 16 and fail on iOS 17 beta, calling into j2objc's JRE emulation:
func testDecodeStream() {
    let testString = "{testtest}"
    let data = testString.data(using: .utf8)
    let byteArray = IOSByteArray(nsData: data)
    let stream: JavaIoInputStream = JavaIoByteArrayInputStream(byteArray: byteArray)
    let reader: JavaIoReader = JavaIoInputStreamReader(javaIoInputStream: stream, with: "UTF-8")

    print("ready? \(reader.ready())")
    while (reader.ready()) {
        let byte = reader.read()
        print(byte)
        print("--")
    }
}

On iOS 16 I see that the reader indicates it is ready, the stream has 10 characters available to read, and the loop executes printing each character out line by line.
With no changes, on iOS 17 I see that the reader indicates it is ready, the first byte is read, but the loop only executes once printing 65533.
Based on what I've been reading GSON is using these functions/classes internally which is why we're seeing the failures in our app.

Just a note I've found that writing to a stream fails on iOS 17 as well. See the test code here:
private func testWriteSteam() {
        let stream = JavaIoByteArrayOutputStream()
        let writer = JavaIoBufferedWriter(javaIoWriter: JavaIoOutputStreamWriter(javaIoOutputStream: stream, with: "UTF-8"))

        let testString = "{testtest}"
        let byteArray = IOSCharArray(nsString: testString)!

        writer.write(with: byteArray, with: 0, with: byteArray.length())
        writer.flush()

        print(stream)
        print("DONE!")
    }

On iOS 16 I see "{testtest}" and on iOS 17 it just prints an empty line.

Hi Cotlin, I apologize for my late reply. Your finding looks real, and thanks for your report and test cases!
The team is sort of under-staffed at the moment, so the response might be a bit slow. But this one is indeed import to us, and we'll look into it.
Thanks again. :)

@litstrong Great, thanks for confirming.
Just a note I've done some further testing on this and interestingly it only appears to be an issue with the simulator, not physical devices running the beta.

Hi Cotlin,
I tested your code snippet under Xcode 15 beta 8 (simulator), and it seems running well.


2.16.2 DO NOT MERGE

fix(agent): fix an issue with irs loading on some platforms (backport of #217) (original commit: 862ce135888767ff2974b2518fb1439cf7d6ee82)
fix(telemetry): fixes and improvements to telemetry (backport of #218) (original commit: 65b41fd07be12c78851d6556661aed49dc9a88dc)
fix: use our own compose binary in the slim-docker image (backport) (original commit: https://github.com/nuvlaedge/nuvlaedge/commit/7322d3f5363e7d340140e2654025080f76548f82)

release created. closing


learning+website: add FlattenWith and Tee to Playground and Transform Catalog [WIP]

Description
Python SDK

[x] Add FlattenWith to Playground
[x] Add FlattenWith to Transform Catalog
[ ] Add Tee to Playground
[ ] Add Tee to Transform Catalog

Java SDK

[ ] Add FlattenWith to Playground
[ ] Add FlattenWith to Transform Catalog
[ ] Add Tee to Playground
[ ] Add Tee to Transform Catalog

Fixes #32840

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Hi @liferoad and @robertwb,
Is there a convenient way to resolve the following java dependency issues that I'm encountering? 🙏
I'm new to Java development and have recently worked with the FlattenWith feature introduced in Apache Beam 2.61.0. However, the current katas learning Java code uses Apache Beam 2.38.0 (link to the code). To align the versions, I compiled a JAR file for Apache Beam Java core from source using gradle build. The following files were generated in build/libs:
beam-sdks-java-core-2.61.0-SNAPSHOT-tests-unshaded.jar
beam-sdks-java-core-2.61.0-SNAPSHOT-tests.jar
beam-sdks-java-core-2.61.0-SNAPSHOT-unshaded.jar
beam-sdks-java-core-2.61.0-SNAPSHOT.jar

Next, I copied beam-sdks-java-core-2.61.0-SNAPSHOT-tests-unshaded.jar into the katas learning Java modules in IntelliJ, and it recognized the FlattenWith operations. However, when I tried to run it, I encountered dependency issues, specifically:
Caused by: java.lang.ClassNotFoundException: org.apache.beam.vendor.guava.v32_1_2_jre.com.google.common.collect.SortedSetMultimap

I would greatly appreciate any help!

Thanks for doing this!
You probably need to update guava (and the other files) to the versions Beam uses, which can be found at https://github.com/apache/beam/blob/release-2.60.0/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L616
I'm not sure how to depend on a pre-release version of beam (other than copying java files as you did for testing). That's a downside for having this be in a separate repository.

Perhaps this'll be easier now that this is in the official release.

Hi @robertwb,
Apologies for the delayed response to this PR. I've been finishing up my current internship but will address the feedback over the weekend. 🙏

Hi @robertwb, I think the PR is now ready for review. I would love to receive any feedback! 🙏


Checked and pre-checked button [GSSOC'23] [NEW]

Hey, @Spyware007 I want to add Checked and prechecked effect button. Please assign it to me under GSSoC'23.


How to use the destination ip of the incoming packet as the packet return source ip

in this img

client ip: *.53
vip ip: *.42
server ip: *.200

and we are using lvs and using tun mode

In QuicheQuicServerCodec.handleServer(), can I append the recipient address to the DatagramPacket that is being written and flushed to the channel? For example, would this code work:
ctx.writeAndFlush(new DatagramPacket(out.writerIndex(outWriterIndex + res), sender, recipient));

No it will not... as far as I know it's not possible as the sender address is the one that the socket is "bound to". What you can do is to explicit bind a socket to a specify address when you bootstrap it.

I'm really sorry, but I didn't quite understand how I was supposed to go about it

Is that right? I did try it, but in my scenario, the destination ip of the packet can't be fixed, so it's harder to fulfill the requirement this way.
I see nginx has this logic:
nginx inside ngx_sendmsg_vec, ngx_set_srcaddr_cmsg, if the server is listening to <IP_ADDRESS>, the socket is not bound to a specific ip address, back to the packet is to be through this interface to specify the destination ip for the packet back to the source ip of the interface, and ultimately sent out through the sendmsg. The receiving packet uses recvmsg to get the source destination ip of the packet. otherwise the kernel sends out the packet by routing to select srcip as the source ip and sends it out.
What I'm trying to say is whether I can find an implementation of this in netty

Can you point me to the nginx impl of it ?

Ok I found it... I suspect we could support it in netty but its not there atm:
https://github.com/nginx/nginx/blob/master/src/os/unix/ngx_udp_sendmsg_chain.c#L246

The relevant code is here
static ssize_t
ngx_sendmsg_vec(ngx_connection_t *c, ngx_iovec_t *vec)
{
    struct msghdr    msg;

#if (NGX_HAVE_ADDRINFO_CMSG)
    struct cmsghdr  *cmsg;
    u_char           msg_control[CMSG_SPACE(sizeof(ngx_addrinfo_t))];
#endif

    // Initializes a 'struct msghdr' structure. This structure is used to control how messages are sent.
    ngx_memzero(&msg, sizeof(struct msghdr));

    // If the connection has an address, set it to the 'msg.msg_name' field.
    if (c->socklen) {
        msg.msg_name = c->sockaddr;
        msg.msg_namelen = c->socklen;
    }

    // The data to be sent is set to the 'msg.msg_iov' field.
    msg.msg_iov = vec->iovs;
    msg.msg_iovlen = vec->count;

    // If the connection is a listening connection and has a wildcard address, set the source address to the 'msg.msg_control' field.
#if (NGX_HAVE_ADDRINFO_CMSG)
    if (c->listening && c->listening->wildcard && c->local_sockaddr) {

        // Assign a control message.
        msg.msg_control = msg_control;
        msg.msg_controllen = sizeof(msg_control);
        ngx_memzero(msg_control, sizeof(msg_control));

        // Get the first control message.
        cmsg = CMSG_FIRSTHDR(&msg);

        // Sets the type and length of the control message.
        msg.msg_controllen = ngx_set_srcaddr_cmsg(cmsg, c->local_sockaddr);
    }
#endif

    // Call the ngx_sendmsg() function to send the message.
    return ngx_sendmsg(c, &msg, 0);
}

Yes, this is the code. Do you have any ideas on how I can help?

I just created https://github.com/netty/netty/issues/13495. This will need to be implemented via JNI for the epoll transport. Not sure yet when I will have time to do so atm, so if you have experience with JNI you might want to work on a PR against netty.

I'm glad you'll be able to support such a feature in the future.
I don't have any JNI-related experience yet, but I guess I could give it a try, although it feels unlikely to be possible to do so


Use cache when building images

https://github.com/docker/build-push-action/blob/master/docs/advanced/cache.md

Done.


[SPARK-20876][SQL][Backport-2.2]If the input parameter is float type for ceil or floor,the result is not we expected

What changes were proposed in this pull request?
This PR is to backport #18103 to Spark 2.2
How was this patch tested?
unit test

Can one of the admins verify this patch?

ok to test

Test build #77573 has started for PR 18155 at commit 5ab4a96.

Merged build finished. Test FAILed.

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

Jenkins, retest this please.

Test build #77579 has started for PR 18155 at commit 6fc66e8.

Test build #77580 has started for PR 18155 at commit 6fc66e8.

Test build #77579 has finished for PR 18155 at commit 6fc66e8.

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

Merged build finished. Test PASSed.

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

LGTM, cc @gatorsmile

Test build #77580 has finished for PR 18155 at commit 6fc66e8.

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

Merged build finished. Test PASSed.

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

Thanks! Merging to 2.0.
Could you manually close this PR? Thanks!

@gatorsmile  OK,thanks


HDDS-8257. RocksIterator not closed properly in LegacyBucketHandler

What changes were proposed in this pull request?
Close RocksIterator in LegacyBucketHandler.
https://issues.apache.org/jira/browse/HDDS-8257
How was this patch tested?
CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/4509913479

Thanks @aswinshakil, @duongkame, @neils-dev for the review.


feat(supersim): configure l1 and l2 genesis state

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#28  👈
#24
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tremarkley and the rest of your teammates on  Graphite


[SPARK-44861][CONNECT] jsonignore SparkListenerConnectOperationStarted.planRequest

What changes were proposed in this pull request?
Add @JsonIgnoreProperties(value = Array("planRequest")) to SparkListenerConnectOperationStarted.planRequest
Why are the changes needed?
SparkListenerConnectOperationStarted was added as part of SPARK-43923.
SparkListenerConnectOperationStarted.planRequest cannot be serialized & deserialized from json as it has recursive objects which causes failures when attempting these operations.
com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Direct self-reference leading to cycle (through reference chain: org.apache.spark.sql.connect.service.SparkListenerConnectOperationStarted["planRequest"]->org.apache.spark.connect.proto.ExecutePlanRequest["unknownFields"]->grpc_shaded.com.google.protobuf.UnknownFieldSet["defaultInstanceForType"])
	at com.fasterxml.jackson.databind.exc.InvalidDefinitionException.from(InvalidDefinitionException.java:77)
	at com.fasterxml.jackson.databind.SerializerProvider.reportBadDefinition(SerializerProvider.java:1308)

Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit

Interesting. For the newly added events for Spark Connect Server, we don't have a test suite of golden files for the expected event logs, so this PR's change didn't affect any golden file updates. It'd be be great if we can have test parity with the other events and have golden file based testing added. 🙏


Autorest Regen Preview to 3.0.0-alpha.20230402.3 by Dapeng Zhang from refs/pull/3175/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3175

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.Orbital


Import Certificate Action Log_Output cannot accept a value

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
There is a problem where the log_output parameter is a boolean, but not specified as such, so it picks up the default parameter type which is string. If one actually tries to use this, you get an error when you try to pass in the default parameter type or the boolean type.
Complete output when running fastlane, including the stack trace and command used
You passed invalid parameters to 'import_certificate'.
[10:18:14]: Check out the error below and available options by running `fastlane action import_certificate`

[!] 'log_output' value must be a String! Found TrueClass instead.

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Not necessary
Environment
fastlane version (run fastlane -v): 1.103.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? Yes
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? No

I have an open PR

@lyndsey-ferguson Thanks for the PR! We'll work with you there. Hope that you have a great weekend coming up!


I want a rectangle to rotate at the end.

I want a rectangle to rotate at the end, and I look at all the issues associated with it, and I find that positionPrev has a high probability of occurrence, but I still don't understand the difference between positionPrev and position. @liabru

I assume you mean you'd like to change the origin (i.e. centre of mass)? In which case you should set both body.position and body.positionPrev at the same time to the desired origin in world space. I've marked this as improve as it would be great to have a function to make this more obvious.

The function Body.setCentre was added to make this more straightforward.


Greenkeeper/sass loader 7.0.1

7.0.0 release notes
7.0.1 release notes

Coverage remained the same at 99.402% when pulling 98e1146011fcac088a055b81310978aed9761b5e on greenkeeper/sass-loader-7.0.1 into a9237f04e12132a6dc18cfd4b811fc8316733ac3 on master.

The coverage drop is a red herring.


Azure Upload states as successful (POST 200 OK), but no file uploaded to container

I am using the following to upload from an AngularJS front end form to Azure Blob Storage via Node/Multiparty. It returns a POST 200 OK with the type of document, however, when I check my Azure Blob Storage with a tool such as Azure Storage Explorer, the file is no where to be found.
Here is my form in the AngularJS view:
<form action="/upload2" method="post" enctype="multipart/form-data">
    <input type="file" name="myfile" />
    <input type="submit" value="Upload" />
</form>

Here is my server.js
var express = require('express');
var azure = require('azure-storage');
// A node.js module for parsing multipart-form data requests which supports streams2    https://github.com/andrewrk/node-multiparty
var multiparty = require('multiparty');

// Initialize Express App
var app = express();
var port = process.env.port || 1337;
app.use(express.static(__dirname + "/public")).listen(port);

var accessKey = 'mykey';
var storageAccount = 'myblob';

var blobSvc = azure.createBlobService(storageAccount, accessKey);

app.post('/upload2', function (req, res) {

var form = new multiparty.Form();

form.on('part', function (part) {
    if (!part.filename) return;

    var size = part.byteCount;
    var name = part.filename;
    var container = 'mycontainer';

    blobSvc.createBlockBlobFromStream(container, name, part, size, function (error) {
        if (error) {
                //res.send(' Blob create: error ');
        }
    });
});
form.parse(req);
res.send('File uploaded successfully');
});

Just found the issue preventing uploads. I was using the azure-storage when it needed azure:
Bad:
var azure = require('azure-storage');

Good:
var azure = require('azure');


MobSF request failed due to unknwon error No such file or directory @ rb_sysopen -

How do I pass a file from a volume as an argument to docker-compose?
I have this coomand TARGET_PATH='configuration:/cfg/bcapp.apk' | docker-compose up --build --exit-code-from scan
The target path is actually a docker volume which holds the apk file as output of the build process. I need to do this as required by circleci; https://circleci.com/docs/2.0/building-docker-images/#mounting-folders
Successfully built 8c08a5eb5d9b
Successfully tagged mobsfci_scan:latest
Creating mobsfci_mobsf_1 ...
Creating mobsfci_mobsf_1 ... doneCreating mobsfci_scan_1  ...
Creating mobsfci_scan_1  ... doneAttaching to mobsfci_mobsf_1, mobsfci_scan_1
mobsf_1  | [2019-11-08 00:16:29 +0000] [1] [INFO] Starting gunicorn 19.9.0
scan_1   | timeout: unrecognized option: t
mobsf_1  | [2019-11-08 00:16:29 +0000] [1] [INFO] Listening at: http://<IP_ADDRESS>:8000 (1)
mobsf_1  | [2019-11-08 00:16:29 +0000] [1] [INFO] Using worker: threads
scan_1   | BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.
scan_1   |
scan_1   | Usage: timeout [-s SIG] SECS PROG ARGS
scan_1   |
scan_1   | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
scan_1   | Default SIG: TERM.
scan_1   | wait-for-it.sh: timeout occurred after waiting 15 seconds for mobsf:8000
scan_1   | Starting to scan ""
scan_1   | MobSF request failed due to unknwon error No such file or directory @ rb_sysopen -
mobsfci_scan_1 exited with code 1

Could you please provide any update on this?

Yes, sorry. Could you please try TARGET_PATH='cfg/bcapp.apk'? It should only be the path inside the docker, without the mounting config.

Hi @omerlh - I have slightly modified docker-compose.yml to provide direct path to apk
version: '3'

services:
  mobsf:
    image: opensecurity/mobile-security-framework-mobsf:latest
    environment:
      - MOBSF_API_KEY=12345
    ports:
     - 8000:8000

  scan:
    build:
      context: ./scan
    environment:
      - MOBSF_URL=http://mobsf:8000/
      - TARGET_PATH=/home/jenkins/mobsf-ci/target/example.apk

    volumes:
      - "/home/jenkins/mobsf-ci/output:/app/output"
      - "/home/jenkins/mobsf-ci/target:/app/target"

    depends_on:
      - mobsf

I'm getting the following error message:
jenkins@jenkins-example:~/mobsf-ci$ sudo docker-compose up --build --exit-code-from scan
[sudo] password for jenkins:
WARNING: The PWD variable is not set. Defaulting to a blank string.
WARNING: using --exit-code-from implies --abort-on-container-exit
Building scan
Step 1/6 : FROM ruby:2.5-alpine
 ---> 4854dd6e8222
Step 2/6 : WORKDIR /app
 ---> Using cache
 ---> c5c5bd293a82
Step 3/6 : COPY Gemfile Gemfile.lock /app/
 ---> Using cache
 ---> f873494b26d0
Step 4/6 : RUN bundle && apk add --update bash
 ---> Using cache
 ---> af1afc606ea1
Step 5/6 : COPY . .
 ---> Using cache
 ---> c06f761a7d4b
Step 6/6 : CMD ./wait-for-it.sh mobsf:8000 -- ruby scan.rb
 ---> Using cache
 ---> 8b04cc36544c
Successfully built 8b04cc36544c
Successfully tagged mobsfci_scan:latest
Starting mobsfci_mobsf_1 ...
Starting mobsfci_mobsf_1 ... done
Recreating mobsfci_scan_1 ...
Recreating mobsfci_scan_1 ... done
Attaching to mobsfci_mobsf_1, mobsfci_scan_1
scan_1   | timeout: unrecognized option: t
scan_1   | BusyBox v1.32.1 () multi-call binary.
scan_1   |
scan_1   | Usage: timeout [-s SIG] SECS PROG ARGS
scan_1   |
scan_1   | Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
scan_1   | Default SIG: TERM.
scan_1   | wait-for-it.sh: timeout occurred after waiting 15 seconds for mobsf:8000
mobsf_1  | [INFO] 06/Feb/2021 14:19:33 -
mobsf_1  |   __  __       _    ____  _____   _____  _____
mobsf_1  |  |  \/  | ___ | |__/ ___||  ___| |___ / |___ /
mobsf_1  |  | |\/| |/ _ \| '_ \___ \| |_      |_ \   |_ \
mobsf_1  |  | |  | | (_) | |_) |__) |  _|    ___) | ___) |
mobsf_1  |  |_|  |_|\___/|_.__/____/|_|     |____(_)____/
mobsf_1  |
mobsf_1  | [INFO] 06/Feb/2021 14:19:33 - Mobile Security Framework v3.3.0 Beta
mobsf_1  | [INFO] 06/Feb/2021 14:19:33 -
mobsf_1  | API Key read from environment variable
mobsf_1  | [INFO] 06/Feb/2021 14:19:33 - OS: Linux
mobsf_1  | [INFO] 06/Feb/2021 14:19:33 - Platform: Linux-4.15.0-135-generic-x86_64-with-glibc2.29
mobsf_1  | [INFO] 06/Feb/2021 14:19:33 - Dist: ubuntu 20.04 focal
mobsf_1  | [INFO] 06/Feb/2021 14:19:33 - MobSF Basic Environment Check
scan_1   | Starting to scan "/home/jenkins/mobsf-ci/target/example.apk"
scan_1   | MobSF request failed due to unknwon error No such file or directory @ rb_sysopen - /home/jenkins/mobsf-ci/                 target/example.apk
mobsf_1  | REST API Key: 12345
mobsf_1  | No changes detected
mobsfci_scan_1 exited with code 1
Aborting on container exit...
Stopping mobsfci_mobsf_1 ... done
jenkins@jenkins-example:~/mobsf-ci$ ^C
jenkins@jenkins-example:~/mobsf-ci$ ^C
jenkins@jenkins-example:~/mobsf-ci$ ^C
jenkins@jenkins-example:~/mobsf-ci$

Look like this is the actual error:
MobSF request failed due to unknwon error No such file or directory @ rb_sysopen - /home/jenkins/mobsf-ci/target/example.apk

Can you ensure the file exist on this path?

Yes. I kept example.apk under the following path: /home/jenkins/mobsf-ci/target

Hi there! The maintainer of this repository left the company some time ago and we archived the repository at that time. I'm closing out some old issues as part of a cleanup to our GitHub repositories.
If you're still using this solution, please migrate to an alternative as soon as possible. Thanks!


Residual ReplicaSets after Helm chart deployment

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
After deploying Cilium, there are 2 ReplicaSets with desired replicas set to 0:
$ kubectl get rs -n kube-system -l name=cilium-operator
NAME                         DESIRED   CURRENT   READY   AGE
cilium-operator-55fcf6b685   0         0         0       46m
cilium-operator-756dfb7cc6   2         2         2       32m
cilium-operator-865f6495f6   0         0         0       48m

$ kubectl get rs cilium-operator-55fcf6b685 -n kube-system
NAME                         DESIRED   CURRENT   READY   AGE
cilium-operator-55fcf6b685   0         0         0       47m
[floren@perses ~]$ kubectl describe rs cilium-operator-55fcf6b685 -n kube-system
Name:           cilium-operator-55fcf6b685
Namespace:      kube-system
Selector:       io.cilium/app=operator,name=cilium-operator,pod-template-hash=55fcf6b685
Labels:         app.kubernetes.io/name=cilium-operator
                app.kubernetes.io/part-of=cilium
                io.cilium/app=operator
                name=cilium-operator
                pod-template-hash=55fcf6b685
Annotations:    deployment.kubernetes.io/desired-replicas: 2
                deployment.kubernetes.io/max-replicas: 3
                deployment.kubernetes.io/revision: 2
                meta.helm.sh/release-name: cilium
                meta.helm.sh/release-namespace: kube-system
Controlled By:  Deployment/cilium-operator
Replicas:       0 current / 0 desired
Pods Status:    0 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:           app.kubernetes.io/name=cilium-operator
                    app.kubernetes.io/part-of=cilium
                    io.cilium/app=operator
                    name=cilium-operator
                    pod-template-hash=55fcf6b685
  Annotations:      cilium.io/cilium-configmap-checksum: 335a4ec1255b9d66ce1d47bfbf9c99c04ed2435dafc2bae542c57d1c32e31036
                    prometheus.io/port: 9963
                    prometheus.io/scrape: true
  Service Account:  cilium-operator
  Containers:
   cilium-operator:
    Image:      quay.io/cilium/operator-generic:v1.15.6@sha256:5789f0935eef96ad571e4f5565a8800d3a8fbb05265cf6909300cd82fd513c3d
    Port:       9963/TCP
    Host Port:  9963/TCP
    Command:
      cilium-operator-generic
    Args:
      --config-dir=/tmp/cilium/config-map
      --debug=$(CILIUM_DEBUG)
    Limits:
      cpu:     400m
      memory:  256Mi
    Requests:
      cpu:      100m
      memory:   64Mi
    Liveness:   http-get http://<IP_ADDRESS>:9234/healthz delay=60s timeout=3s period=10s #success=1 #failure=3
    Readiness:  http-get http://<IP_ADDRESS>:9234/healthz delay=0s timeout=3s period=5s #success=1 #failure=5
    Environment:
      K8S_NODE_NAME:             (v1:spec.nodeName)
      CILIUM_K8S_NAMESPACE:      (v1:metadata.namespace)
      CILIUM_DEBUG:             <set to the key 'debug' of config map 'cilium-config'>  Optional: true
      KUBERNETES_SERVICE_HOST:  <IP_ADDRESS>
      KUBERNETES_SERVICE_PORT:  6444
    Mounts:
      /tmp/cilium/config-map from cilium-config-path (ro)
  Volumes:
   cilium-config-path:
    Type:               ConfigMap (a volume populated by a ConfigMap)
    Name:               cilium-config
    Optional:           false
  Priority Class Name:  system-cluster-critical
  Node-Selectors:       kubernetes.io/os=linux
  Tolerations:          op=Exists
Events:
  Type    Reason            Age   From                   Message
  ----    ------            ----  ----                   -------
  Normal  SuccessfulCreate  47m   replicaset-controller  Created pod: cilium-operator-55fcf6b685-7xqqt
  Normal  SuccessfulCreate  47m   replicaset-controller  Created pod: cilium-operator-55fcf6b685-mvmh4
  Normal  SuccessfulDelete  33m   replicaset-controller  Deleted pod: cilium-operator-55fcf6b685-mvmh4
  Normal  SuccessfulDelete  33m   replicaset-controller  Deleted pod: cilium-operator-55fcf6b685-7xqqt

$ cilium status
    /¯¯\
 /¯¯\__/¯¯\    Cilium:             OK
 \__/¯¯\__/    Operator:           OK
 /¯¯\__/¯¯\    Envoy DaemonSet:    OK
 \__/¯¯\__/    Hubble Relay:       OK
    \__/       ClusterMesh:        disabled

DaemonSet              cilium-envoy       Desired: 8, Ready: 8/8, Available: 8/8
Deployment             hubble-ui          Desired: 1, Ready: 1/1, Available: 1/1
Deployment             cilium-operator    Desired: 2, Ready: 2/2, Available: 2/2
DaemonSet              cilium             Desired: 8, Ready: 8/8, Available: 8/8
Deployment             hubble-relay       Desired: 2, Ready: 2/2, Available: 2/2
Containers:            cilium             Running: 8
                       cilium-operator    Running: 2
                       hubble-relay       Running: 2
                       cilium-envoy       Running: 8
                       hubble-ui          Running: 1
Cluster Pods:          85/85 managed by Cilium
Helm chart version:
Image versions         cilium             quay.io/cilium/cilium:v1.15.6@sha256:6aa840986a3a9722cd967ef63248d675a87add7e1704740902d5d3162f0c0def: 8
                       cilium-operator    quay.io/cilium/operator-generic:v1.15.6@sha256:5789f0935eef96ad571e4f5565a8800d3a8fbb05265cf6909300cd82fd513c3d: 2
                       hubble-relay       quay.io/cilium/hubble-relay:v1.15.6@sha256:a0863dd70d081b273b87b9b7ce7e2d3f99171c2f5e202cd57bc6691e51283e0c: 2
                       cilium-envoy       quay.io/cilium/cilium-envoy:v1.28.4-b35188ffa1bbe54d1720d2e392779f7a48e58f6b@sha256:b528b291561e459024f66414ac3325b88cdd8f9f4854828a155a11e5b10b78a3: 8
                       hubble-ui          quay.io/cilium/hubble-ui:v0.13.0@sha256:7d663dc16538dd6e29061abd1047013a645e6e69c115e008bee9ea9fef9a6666: 1
                       hubble-ui          quay.io/cilium/hubble-ui-backend:v0.13.0@sha256:1e7657d997c5a48253bb8dc91ecee75b63018d16ff5e5797e5af367336bc8803: 1

Cilium Version
cilium-cli: v0.16.10 compiled with go1.22.4 on linux/arm64
cilium image (default): v1.15.5
cilium image (stable): v1.15.6
cilium image (running): 1.15.6

Kernel Version
Linux apollo 6.8.0-1005-raspi #5-Ubuntu SMP PREEMPT_DYNAMIC Wed May 22 15:01:35 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

Kubernetes Version
Client Version: v1.29.4+k3s1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.4+k3s1

Regression
No response
Sysdump
cilium-sysdump-20240613-005208.zip
Relevant log output
$ helm get values cilium -n kube-system
USER-SUPPLIED VALUES:
autoDirectNodeRoutes: true
bandwidthManager:
  enabled: true
dashboards:
  enabled: true
enableCiliumEndpointSlice: true
envoy:
  enabled: true
  prometheus:
    serviceMonitor:
      enabled: true
  resources:
    limits:
      cpu: 400m
      memory: 256Mi
    requests:
      cpu: 100m
      memory: 64Mi
  rollOutPods: true
externalIPs:
  enabled: true
gatewayAPI:
  enabled: true
hubble:
  metrics:
    dashboards:
      enabled: true
    enabled:
    - dns:query;ignoreAAAA
    - drop
    - flow
    - httpV2
    - icmp
    - port-distribution
    - tcp
    serviceMonitor:
      enabled: true
  peerService:
    clusterDomain: cluster.local
  relay:
    enabled: true
    prometheus:
      serviceMonitor:
        enabled: true
    replicas: 2
    resources:
      limits:
        cpu: 400m
        memory: 256Mi
      requests:
        cpu: 100m
        memory: 64Mi
    retryTimeout: 10s
    rollOutPods: true
  tls:
    auto:
      certManagerIssuerRef:
        group: cert-manager.io
        kind: ClusterIssuer
        name: hubble-cluster-issuer
      method: certmanager
  ui:
    enabled: true
    rollOutPods: true
ingressController:
  enabled: true
  service:
    loadBalancerIP: <IP_ADDRESS>
ipam:
  operator:
    clusterPoolIPv4PodCIDRList: <IP_ADDRESS>/16
ipv4NativeRoutingCIDR: <IP_ADDRESS>/16
k8sClientRateLimit:
  burst: 100
  qps: 50
k8sServiceHost: <IP_ADDRESS>
k8sServicePort: 6444
kubeProxyReplacement: true
l2announcements:
  enabled: true
l2podAnnouncements:
  enabled: true
  interface: eth0
operator:
  prometheus:
    enabled: true
    serviceMonitor:
      enabled: true
  resources:
    limits:
      cpu: 400m
      memory: 256Mi
    requests:
      cpu: 100m
      memory: 64Mi
  rollOutPods: true
prometheus:
  enabled: true
  serviceMonitor:
    enabled: true
rollOutCiliumPods: true
routingMode: native

Anything else?
No response
Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

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

This is actually a Kubernetes feature, checkout https://kubernetes.io/docs/concepts/workloads/controllers/deployment/

Each time a new Deployment is observed by the Deployment controller, a ReplicaSet is created to bring up the desired Pods. If the Deployment is updated, the existing ReplicaSet that controls Pods whose labels match .spec.selector but whose template does not match .spec.template are scaled down. Eventually, the new ReplicaSet is scaled to .spec.replicas and all old ReplicaSets is scaled to 0.

Sometimes, you may want to rollback a Deployment; for example, when the Deployment is not stable, such as crash looping. By default, all of the Deployment's rollout history is kept in the system so that you can rollback anytime you want (you can change that by modifying revision history limit).

You can set .spec.revisionHistoryLimit field in a Deployment to specify how many old ReplicaSets for this Deployment you want to retain. The rest will be garbage-collected in the background. By default, it is 10.

Thank you @dylandreimerink for the useful information.


Agent could not initialize properly

Description
Agent could not initialize properly due to an error when loading .ini configuration file.
     newrelic.agent.initialize(
   File "/usr/local/lib/python3.12/site-packages/newrelic/config.py", line 4803, in initialize
     _load_configuration(config_file, environment, ignore_errors, log_file, log_level)
   File "/usr/local/lib/python3.12/site-packages/newrelic/config.py", line 1027, in _load_configuration
     if config_file.endswith(".toml"):
        ^^^^^^^^^^^^^^^^^^^^
 AttributeError: 'PosixPath' object has no attribute 'endswith'

Your Environment
Python 3.12
newrelic 10.3.1

Are you manually calling newrelic.initialize() with a config file set as some PosixPath object? Or is this happening while using the newrelic-admin wrapper script?

After upgrading the New Relic Python Agent from version 10.2.0 to 10.3.1, the application initialization setup in my wsgi.py file no longer works as expected. The same setup works perfectly in version 10.2.0. Here’s the relevant part of my wsgi.py file:
from django.conf import settings
import newrelic.agent
from pathlib import Path

# Get New Relic license key from .env file
NEW_RELIC_LICENSE_KEY = settings.NEW_RELIC_LICENSE_KEY

# Initialize New Relic agent from config file and set environment (staging/prod)
config_file = Path(__file__).resolve().parent.parent.parent / "newrelic.ini"

newrelic.agent.initialize(
    config_file=config_file, environment=settings.NEW_RELIC_ENVIRONMENT
)

# Register New Relic application monitoring
newrelic.agent.register_application()


Contributing to knowledge sports section

Describe the proposed contribution to the taxonomy
The content that I want to contribute is to the knowledge of taxonomy.
I have added cricket in the sports/ and a qna.yaml and attribution files.
While working on instructlab , I downloaded the existing model and asked question -
Who won the 1987 cricket world cup ?
Ans: Yes, India did win the 1987 World Cup, which was the 50-over format of the Cricket World Cup tournament. India defeated the West Indies in the final match to │
│ claim victory. This marked their first World Cup title in cricket after several attempts.
It gave me wrong answer(above), since the information on wikipedia said otherwise.
Later I created qna file and fed in correct information, generated synthetic data, trained the model and tested again.
I asked the question , this time it gave me correct answer.
Hence this contribution.

Corrected answer to 1987 cricket world cup winner.
Gave inputs from wikipedia.
Got correct information about hosting of this year world cup.

Input given at the prompt

   Did India win the 1987 world cup ?

Response from the current model

  Yes, India did win the 1987 World Cup, which was the 50-over format of the Cricket World Cup tournament. India defeated the West Indies in the final match to claim victory. This marked their first World Cup title in cricket after several attempts.

Response that you would expect instead with the contribution

   India did not win any matches in the 1987 cricket world cup, which was held in India and Pakistan.

After training the model, I asked bunch of questions, to which all the answers were correcrt.
Below are some of the questions I tried -

Who won the 1987 cricket world cup ?
Ans:Australia won the championship match against England by 7 runs, securing victory with just 23 balls left to spare.
Did India won the 1987 cricket world cup ?
Ans:No, India did not win the championship in 1987. They were knocked out during the group stage and finished in sixth place overall
Did Australia won the 1987 world cup ?
Ans: Australia won the championship match against England by a margin of just 7 runs, with both teams putting up an exceptional fight that came down to the final overs.
Who hosted the 1987 cricket world cup ?
Ans: India and Pakistan jointly hosted the 1987 tournament, marking the first time that the event was held outside England.

I created a fork and tried to check in got error.
Below is the cmds I tried along with the error -
(venv) vainakil@Vaibhavs-MacBook-Pro taxonomy % git push --set-upstream origin knowledge_cricket
Username for 'https://github.com': nvaibhav
Password for<EMAIL_ADDRESS>remote: Permission to instructlab/taxonomy.git denied to nvaibhav.
fatal: unable to access 'https://github.com/instructlab/taxonomy.git/': The requested URL returned error: 403

Yep, you need to create a fork in your namespace of nvaibhav so github.com/navibhav/taxonomy. If you look at the top of the taxonomy github page on the right hand side there is a "fork" button.
You can look through the GitHub workflow for more detailed explainations.

Forked here - https://github.com/nvaibhav/taxonomy

I would suggest going to the #users channel in the slack team, or joining one of the office hours, debugging this via a github issue will be difficult.


[GitHub Sync]: Introduce branch switch

It would be great to have a branch switch like VSCode has. When user has tokens that haven't been pushed ask if they want to discard. The branch switcher should show all available branches and give an option to create a new branch.

We'd love this so we can be more pragmatic about working in a dev/staging branch, and have a stable/main branch for the prod app. It'd be awesome to easily switch between the two.

Will be part of the next release 🙏


Develop a new page to keep track of (and point to) preview features

Starting with C# 10, some features are will be enabled by using <LangVersion>preview</LangVersion>.
This article should catalog the current features that are turned on by previews. When those features have more content, this new page will refer to further exploration of those features.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c36588d0-6bdf-1740-220c-10b20bb88730
Version Independent ID: 587ed47f-f532-e018-9b0d-6ee76afd20e4
Content: What's new in C# 10 - C# Guide
Content Source: docs/csharp/whats-new/csharp-10.md
Product: dotnet-csharp
Technology: csharp-whats-new
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

/cc @KathleenDollard @MadsTorgersen

Discussed today:

We'll add a new page in the "What's new" section that describes the current features that are enabled by <LangVersion>preview</LangVersion>. Where these features are sufficient in scope that separate tutorials are available, we'll link to those.
During the preview period we won't update generally update the language reference or other areas. When the feature is "frozen" and won't be modified based on customer feedback, then that work will begin. (Frozen probably is too strong a word, but should express the intent).

Decisions:

[X] The Roslyn feature merge checklist includes notifying the docs team to help us get features documented quicker.
[ ] The csharplang feature template will include a task for documenting hte new feature.
[ ] Create the C# 11 project, with the following tasks already defined:

New breaking changes page (updated through 17.1 & 17.2)
Feature docs issues for 17.1 and 17.2.

The planning work here is done. On to the docs changes.


TF GRID DEMO - payment - Rewrite instruction

Please scan the QR Code below for the payment details if you missed it from the previous screen

Fixed:
Branch
development_payment_qr_code
commit id
56fa99988f78d62380c8ecc3b36c09f61fe35cea

Commit_ID  a35fb9f8b278a8ed396b24d725e3f78d7024270f, Branch development_payment_qr_code


Splits up clients into separate features for wasm-compatibility

Modifies API to conform to client-side API
Splits up clients into separate features for wasm-compatibility (should be fixed later)

Some context copied from the comment below:
Currently fedimint-wallet-client uses an esplora client directly and not through an interface, which makes mocking it out impossible.
Originally I wanted to create a separate bitcoin client interface for fedimint-wallet-client than used in fedimint-wallet-server, but @jkitman convinced me that it's not too bad to use the same one, even though not every implementor of IBitcoindRpc will support both client and server side usage.
To be able to select which implementations of IBitcoindRpc should be included when depending on the bitcoin RPC crate (not all impls support WASM) this PR separates them into different modules and adds feature flags.

Removes blocking and let retry client log errors

Is this part of the description stale now?
I'm confused what is going on in this PR (or rather why). "Add client functionality" - which kind of client? Fedimint client libraries? Why do they need anything to do with bitcoind (or alternative node backends)?
Anyway - left some comments.

@dpc Yes the PR is missing some context. Currently fedimint-wallet-client uses an esplora client directly and not through an interface, which makes mocking it out impossible.
Originally I wanted to create a separate bitcoin client interface for fedimint-wallet-client than used in fedimint-wallet-server, but @jkitman convinced me that it's not too bad to use the same one, even though not every implementor of IBitcoindRpc will support both client and server side usage.
To be able to select which implementations of IBitcoindRpc should be included when depending on the bitcoin RPC crate (not all impls support WASM) this PR separates them into different modules and adds feature flags.
There's a bunch of unrelated stuff going on, which I'm less sure about.

Also, could you reorder and squash the first and last commit please @jkitman? Undoing changes from an earlier commit in a later one is annoying to review and bad style imo.

Oh. I wasn't aware the wallet's client side needs rpc to bitcoind. Does it mean I won't need to manually fetch tx inclusion proofs etc. now(/soon)?

Does it mean I won't need to manually fetch tx inclusion proofs etc. now(/soon)?

Yep, I'll be adding that to the interface soon, so we'll have a standard way of communicating with bitcoin RPCs (as well as the ability to mock them out entirely).

Oh. I wasn't aware the wallet's client side needs rpc to bitcoind. Does it mean I won't need to manually fetch tx inclusion proofs etc. now(/soon)?

Yes, that's how client-NG deposits already work, this PR moves towards making this functionality more testable.


Add a docs page mentioning deployment (SRE) best practices

Chaos Engineering is about controlled experimentation, typically on staging OR production environments
It is also a way to enforce deployment/infrastructure best practices
The litmus-docs can consist of a dedicated page explaining the principles of chaos engg in a K8s context & list standard practices.

Some pointers, for example:

Expose app-specific health endpoints that can be consumed by external health checkers.
Err on the side of adding more readiness and liveness probes.
Tune your resource limits to ensure that apps fall under the “guaranteed” list when push comes to shove (that is, eviction occurs on account of overall resource exhaustions on the node).
Use namespace-level quotas as another method for resource management.
Use topology-aware scheduling and anti-affinity policies to ensure that apps survive node-level failures across nodes and availability zones.
Use cloud native and container-attached storage solutions, so that each stateful workload is provided with its own storage controller in order to persist data. This ensures that the storage is better aligned with Kubernetes operating principles and allows smoother upgrades while minimizing the potential blast radius.
Use application and storage affinity, if possible (solutions like OpenEBS enable this) so that application replicas can consume storage locally without having to go through the network.
Use specific labels for different roles/replicas, enabling operators and admins to know exactly what a replica does in the context of the app.
Set up the right termination policies; you may want to tolerate certain taints, define node stickiness, and so on.
Configure pre-stop and post-start hooks where applicable, to ensure failovers are more meaningful and are well-handled.
Select the right upgrade strategies (on-delete, rolling, and so forth) based on the nature of the application.
Pod and node level auto-scaling enabled, but with storage provisioning and app considerations so that you avoid situations where a data rebalance can go on forever and introduce further issues.
Monitoring and alerting hooks built into the app deployments.

Hey @ksatchit I want to work on this. However, I know quite a little about kubernetes (I'm learning GKE), so can you guide me a bit along this. Thanks :tada:

There is a WG started in CNCF to discuss best practices for chaos testing environments/SRE tips.
Closing this issue to keep the litmus repo focused on the chaos experimentation aspects.


Read Chargelevel of Aerial Turbines from Base (reminder for notnotmelon) 😆

Mod source
Factorio Mod Portal
Which mod are you having an issue with?

[ ] pyalienlife
[X] pyalternativeenergy
[ ] pycoalprocessing
[ ] pyfusionenergy
[ ] pyhightech
[ ] pyindustry
[ ] pypetroleumhandling
[ ] pypostprocessing
[ ] pyrawores

Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[X] Balance
[ ] Pypostprocessing failure
[ ] Other

What is the problem?
Already discussed :)
Steps to reproduce
No response
Additional context
No response
Log file
No response

Fixed. Thanks for the report.

https://github.com/pyanodon/pyalternativeenergy/commit/a8837deb78237fbbf7f82a2b7f62be022344da9c


EditProposal action

We should strongly consider not doing this -- it's unclear how big the benefit is, and adds an enormous amount of complexity, both in the implementation (the fact that we have to implement it at all, how it interacts with other parts of the system, how do we correctly track updates to proposal states, etc), and in the social dynamics (what does it mean that it's possible to edit a proposal while voting is ongoing, what happens if someone completely rewrites the proposal right before the vote closes, etc).

I had meant to close this issue after previous discussion; it's already been removed from the tracking issues, I just missed closing the issue itself.


Help me with smartcontract.

I have some problem with my project.
There are some bugs in my project.
Specially python part.

Please learn the python smart contract tutorial.

Thx.


How to handle strict adapter with test?

this is related to: #763
What is the expected way to handle the strict adapter in tests?
Should I add all the flipper features in a fixture or in an initializer file?
It mentions this in the docs:

Adding feature flags to your app is as simple as adding conditionals
...
<% if Flipper.enabled? :new_feature, current_user %>
 <%= link_to "New Feature", new_feature_path %>
<% end %>

https://www.flippercloud.io/docs/guides/launch#add-feature-flags-to-your-app
It makes it seem like just adding the conditionals like Flipper.enabled? :new_feature is all you need to add a flipper feature, but in tests this warns:
Could not find feature "deep_search". Call `Flipper.add("deep_search")` to create it.

Hey @iseth, this is a good question and something we're still personally experimenting with since the strict adapter is so new. Our testing docs actually recommend overwriting Flipper's config.default, which does not use the Strict adapter at all. This is the setup we're currently using in our apps.
However, I would like to move to a setup where we're using the Strict adapter in tests, with it configured to :raise, and being more explicit about what features are in the code base and their state. With that, I would probably add some test-setup to add the features that are expected in the tests:
class ActiveSupport::TestCase
  setup do
    Flipper.instance = nil
    Flipper.add :feature_1
    Flipper.add :feature_2
  end
end


Fix the max psk len for TLSv1.3

If using an old style TLSv1.2 PSK callback then the maximum possible PSK
len is PSK_MAX_PSK_LEN (256) - not 64.
Fixes #7261

This is obviously also for 1.1.1. I'm going to press ahead on the assumption that the approval stands for that branch too.

Pushed to master and 1.1.1


⚠ SceneTime has degraded performance

In e60ab32, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 10602 ms

Resolved: SceneTime performance has improved in 3c94c45 after 4 minutes.


Add CD

Using GitHub actions:
https://github.com/google-github-actions/deploy-appengine

Or Cloud Run, to define later.


fix(ui): match card styles with PF5

Description
Cards, main section, sidebar background color, etc.
Which issue(s) does this PR fix

Fixes RHIDP-1301: Add MUI theme config so that Cards looks similar to PF5

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[x] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer
Screen record
https://github.com/janus-idp/backstage-showcase/assets/26255262/3d0d974c-7afc-4d35-9cd8-240176ded633

/cc @jerolimov
/cc @gashcrumb

Hey there @ciiay had a chance to pull this down and have a look, it's looking nice!  I think the card background on the catalog page could use some further adjusting.
in Light mode the card appears to have a darker background than the table element in the header area and below the table.  Also I seem to recall there being a title over the table on this page:

Not sure on the empty state, but the background for this seems darker than it should to me.  Maybe this is the way the table behaves though:

The dark theme seems to follow suit, where the table appears to have picked up the card background, but the header portion hasn't.  I checked some other views and it seems the header portion of the card should be the lighter color.:

Below the table it seems should be the darker color so that part is fine.  I used this page as reference:

I think also the empty state background here is darker than it should be (ignore the scrollbar in this screenshot), but this may just be the way the table behaves:

Maybe the background I'm seeing in those screenshots is due to that page control.

Hi @gashcrumb , thanks for the review. In this PR I only focused on Cards style, following this design guide. Let me create a story for Tables style and work on it 🤝

@ciiay looks good to me, thank you!

@invincibleJai Thanks for the review. I have updated this PR to fix the topology display issue. Please confirm. Also I wasn't able to figure out the SonarCloud Code Analysis failure, can you take a look? Thanks in advance.

@invincibleJai Thanks for the review. I have updated this PR to fix the topology display issue. Please confirm. Also I wasn't able to figure out the SonarCloud Code Analysis failure, can you take a look? Thanks in advance.

SonarCloud Code Analysis failure doesn't seem related to this PR to me

/lgtm
/approve

@invincibleJai Thanks for the review. I have updated this PR to fix the topology display issue. Please confirm. Also I wasn't able to figure out the SonarCloud Code Analysis failure, can you take a look? Thanks in advance.

SonarCloud Code Analysis failure doesn't seem related to this PR to me

The test failure doesn't seem related to this PR
@kadel / @josephca any suggestion on what shall we do?

/lgtm

/lgtm

/approve
verified the changes locally, this works as expected

/lgtm


bowtie2: 2.4.4 -> 2.4.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/BenLangmead/bowtie2/releases.
meta.description for bowtie2 is: "An ultrafast and memory-efficient tool for aligning sequencing reads to long reference sequences"
meta.homepage for bowtie2 is: "http://bowtie-bio.sf.net/bowtie2"
meta.changelog for bowtie2 is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin/bowtie2-build had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin/bowtie2-build-l had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin/bowtie2-inspect-l had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin/bowtie2-align-s had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin/bowtie2-inspect-s had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin/bowtie2-align-l had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin/bowtie2-build-s had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin/bowtie2 had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin/bowtie2-inspect had a zero exit code or showed the expected version
0 of 9 passed binary check by having a zero exit code.
0 of 9 passed binary check by having the new version present in output.
found 2.4.5 with grep in /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5
found 2.4.5 in filename of file in /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5

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

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
bowtie2

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5
ls -la /nix/store/1hcybmprbaipymq72nq0lj5z573gfbv5-bowtie2-2.4.5/bin

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

1 package built:

bowtie2

Maintainer pings
cc @rybern for testing.


Run make run-kube-local failed

Description:

What issue is being seen? Describe what should be happening instead of
the bug, for example: Envoy should not crash, the expected value isn't
returned, etc.

make run-kube-local starts EG locally, but failed for couple of reasons:

Cannot find EG binary if we did not run make build manually before this:

multicluster kube-config will break the script:

/assign

@Xunzhuo even with https://github.com/envoyproxy/gateway/pull/388, this Make target will fail until https://github.com/envoyproxy/gateway/issues/256 is fixed, PTAL.


Back-incompatible changes

cat test.go
package test
import (
	"context"
	url "net/url"
	"reflect"
	gomock "github.com/golang/mock/gomock"
	inner_client "go.go.go/libs/inner_client"
	"go.go.go/services/service1/domain/subject/domain"
	model "go.go.go/services/service1/domain/subject/domain"
	common "go.go.go/services/service1/internal/common"
	"go.go.go/services/service1/domain/subject/domain"
)

Let's assume I want 4 groups:

Standard # go libs
Default # 3rd party libs
Prefix(go.go.go/libs) # inner libs
Prefix(go.go.go/) # another inner deps

Let's try:
gci write . -s "Standard,Default,Prefix(go.go.go/libs),Prefix(go.go.go)"
v.0.4.1 - Seems like good!
package test
import (
	"context"
	url "net/url"
	"reflect"

	gomock "github.com/golang/mock/gomock"

	inner_client "go.go.go/libs/inner_client"

	"go.go.go/services/service1/domain/subject/domain"
	"go.go.go/services/service1/domain/subject/domain"
	model "go.go.go/services/service1/domain/subject/domain"
	common "go.go.go/services/service1/internal/common"
)

...but run again ... and the order of the duplicate dependencies changed:
package test
import (
	"context"
	url "net/url"
	"reflect"

	gomock "github.com/golang/mock/gomock"

	inner_client "go.go.go/libs/inner_client"

	model "go.go.go/services/service1/domain/subject/domain"
	"go.go.go/services/service1/domain/subject/domain"
	"go.go.go/services/service1/domain/subject/domain"
	common "go.go.go/services/service1/internal/common"
)

v0.4.2, v0.4.3, v0.4.4, v0.5.0 - Prefix-blocks order changed
package test
import (
	"context"
	url "net/url"
	"reflect"

	gomock "github.com/golang/mock/gomock"

	"go.go.go/services/service1/domain/subject/domain"
	model "go.go.go/services/service1/domain/subject/domain"
	"go.go.go/services/service1/domain/subject/domain"
	common "go.go.go/services/service1/internal/common"

	inner_client "go.go.go/libs/inner_client"
)

v0.6.0 - works OK again, but still random sort duplicate entries:
package test
import (
	"context"
	url "net/url"
	"reflect"

	gomock "github.com/golang/mock/gomock"

	inner_client "go.go.go/libs/inner_client"

	model "go.go.go/services/service1/domain/subject/domain"
	"go.go.go/services/service1/domain/subject/domain"
	"go.go.go/services/service1/domain/subject/domain"
	common "go.go.go/services/service1/internal/common"
)

v0.6.1, v0.6.2, v0.6.3 - breaks the order again =(
package test
import (
	"context"
	url "net/url"
	"reflect"

	gomock "github.com/golang/mock/gomock"

	"go.go.go/services/service1/domain/subject/domain"
	model "go.go.go/services/service1/domain/subject/domain"
	"go.go.go/services/service1/domain/subject/domain"
	common "go.go.go/services/service1/internal/common"

	inner_client "go.go.go/libs/inner_client"
)

If you do not specify --custom-order, the result is as expected.
I can not ensure backward compatibility since no bug-fixes backport.


Fix concurrent merge bugs

Two concurrent merges occurred which broke the build.
Merges
https://github.com/microsoft/FluidFramework/pull/18185 & https://github.com/microsoft/FluidFramework/pull/18135
https://github.com/microsoft/FluidFramework/pull/18180 & https://github.com/microsoft/FluidFramework/pull/18177

Looks like there was another merge added the fix


stripes data: au.nem.*.fuel_tech.solar_rooftop.energy missing data before 2018-03-01

this is very evident in stripes:

ready to validate
https://dev.opennem.org.au/stripes/nem/?metric=solarProportion

nope, still missing:

this is from monthly.json on dev

#182 is the same fix on dev now

good that we now have from 2015-03 to 2018-03 loaded, but we're still missing rooftop solar before 2015-03.
it's in the energy view, but not stripes view:
<!-- Uploading "image.png"... -→

@simonhac consisted daily/monthly buckets between stripes/energy/fac out on dev rn
merging #182 into here

This doesn't look right to me @nc9
Price data and stripes goes back to June 09 but the energy graph has no data til 2015

hmmmm… TIL the price chart does not respond to the selection. emissions does, price doesn't.
https://user-images.githubusercontent.com/20500649/230286059-a1260ac4-b2ef-4094-b326-003a12b62e22.mov
this is really a front end issue.

…and a bit tricky. for accurate VWP i believe we use *. au.nem.demand.energy for the denominator.
so i think we need two modes:
• if any series is deselected: sum the generation
• otherwise, use *. au.nem.demand.energy.

I'll create a new FE issue for that.
Back to the issue at hand, in Simon's comment above (https://github.com/opennem/opennem/issues/206#issuecomment-1477157893) there looks to be energy data back to 2009 but I now see energy data only going back to 2013. Is this intentional?

ondev

Still seeing some issues here. EG - in All Regions view I see data for this fuel tech in Queensland in June 2011. In Queensland view, I see no data.

This is by design, no daily bucket data going back that far.


DTrack Score: Failed to get project: invalid character '<'

Hello,
I'm trying to tag a Dtrack project with sbomqs score.
The command I am running is:
sbomqs dtrackScore -D -t true -u https://dependency-track-host-url-of-my-company.com -k $DTRACK_API_KEY $DTRACK_PROJECT_UUID

The output is:
2023-08-24T18:39:24.329-0400	DEBUG	engine/dtrack.go:46	engine.DtrackScore()
2023-08-24T18:39:24.331-0400	DEBUG	engine/dtrack.go:48	Config: &{Url:https://dependency-track-host-url-of-my-company.com ApiKey:********* ProjectIds:[de46d3c2-f650-4ea3-a15b-db3bc38c02da] Json:false Basic:false Detailed:false TagProjectWithScore:true}
2023-08-24T18:39:24.331-0400	DEBUG	engine/dtrack.go:58	Processing project de46d3c2-f650-4ea3-a15b-db3bc38c02da
2023-08-24T18:39:24.736-0400	FATAL	engine/dtrack.go:62	Failed to get project: invalid character '<' looking for beginning of value
github.com/interlynk-io/sbomqs/pkg/engine.DtrackScore
	github.com/interlynk-io/sbomqs@v0.0.19/pkg/engine/dtrack.go:62
github.com/interlynk-io/sbomqs/cmd.glob..func1
	github.com/interlynk-io/sbomqs@v0.0.19/cmd/dtrackScore.go:48
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.7.0/command.go:940
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.7.0/command.go:1068
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.7.0/command.go:992
github.com/interlynk-io/sbomqs/cmd.Execute
	github.com/interlynk-io/sbomqs@v0.0.19/cmd/root.go:42
main.main
	github.com/interlynk-io/sbomqs@v0.0.19/main.go:20
runtime.main
	runtime/proc.go:250

Tried from:

My local M2 MacBook Pro
Bitbucket Pipelines Cloud Runner, as part of our CI

~ sbomqs version
  ____    ____     ___    __  __    ___    ____
 / ___|  | __ )   / _ \  |  \/  |  / _ \  / ___|
 \___ \  |  _ \  | | | | | |\/| | | | | | \___ \
  ___) | | |_) | | |_| | | |  | | | |_| |  ___) |
 |____/  |____/   \___/  |_|  |_|  \__\_\ |____/
sbomqs: sbomqs application provides sbom quality scores.

GitVersion:    v0.0.19
GitCommit:     6744ad2ecf54ea0e22fb406db6bb56f8d1957871
GitTreeState:  clean
BuildDate:     '2023-07-13T20:56:47Z'
GoVersion:     go1.20.6
Compiler:      gc
Platform:      darwin/arm64

I have also tried with and without the -t option but to no avail.
Any idea on why this error is happening? I did confirm that the Project ID is accurate (copied from the URL after navigating to the project within Dependency Track)
Thank you!

@aravindparappil46 what is the name of your project ? Can u post a screenshot, maybe there are some special characters

Hi @riteshnoronha ,
Yes, the project name does contain / and - in it.
It looks like:
someprefix/service-name-separated-by-hyphens
Would that be the culprit?
Here's a screenshot.

Ok testing it locally will let u know

Looks like something is broken with either DT or sbomqs. Will take a look tomorrow and fix it.

Ok. Thanks a lot!

@aravindparappil46  two issues

If you are running DT using the docker-compose file, it starts the api-server on port 8081. Hence your command should reflect it.

sbomqs dtrackScore -D -t true -u "https://dependency-track-host-url-of-my-company.com:8081" -k $DTRACK_API_KEY $DTRACK_PROJECT_UUID

Found a bug in sbomqs, have fixed it with https://github.com/interlynk-io/sbomqs/pull/182. We have another fix we are working on, so we will release a new version 0.0.20 tomorrow.

Again please feel free for providing feedback or feature requests.

Thanks for the quick turnaround, @riteshnoronha ! ⚡
We are not using the docker-compose approach for DT, so should be good. But that's good info to know!

@aravindparappil46 so is your api-server running on a diff port?

We have separated the frontend and backend of DT into different repos (basically, two repos with just a Dockerfile that pulls either from dependencytrack/apiserver or dependencytrack/frontend and then EXPOSE 8080) and have deployed them independently (I believe behind a load balancer, but just one container each for now). Had to go this route due to some restrictions

The error you are getting  invalid character '<' looking means we cannot access the api-server, that is the main problem. So whenever u see this error in sbomqs, its because the port or url is incorrect.

Ahh I see. That makes sense because the URL I provided in the command above was for the DT UI and not the API server. Trying with the API server URL gives a few different errors:
~ sbomqs dtrackScore -D -t -u https://dependency-track-api.myorg.com:8080 -k $DTRACK_API_KEY $DTRACK_PROJECT_UUID

2023-08-25T00:41:23.587-0400	DEBUG	engine/dtrack.go:46	engine.DtrackScore()
2023-08-25T00:41:23.587-0400	DEBUG	engine/dtrack.go:48	Config: &{Url:https://dependency-track-api.myorg.com:8080 ApiKey:**** ProjectIds:[de46d3c2-f650-4ea3-a15b-db3bc38c02da] Json:false Basic:false Detailed:false TagProjectWithScore:true}
2023-08-25T00:41:23.587-0400	DEBUG	engine/dtrack.go:58	Processing project de46d3c2-f650-4ea3-a15b-db3bc38c02da
2023-08-25T00:41:33.588-0400	FATAL	engine/dtrack.go:62	Failed to get project: Get "https://dependency-track-api.myorg.com:8080/api/v1/project/de46d3c2-f650-4ea3-a15b-db3bc38c02da": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
github.com/interlynk-io/sbomqs/pkg/engine.DtrackScore
	github.com/interlynk-io/sbomqs@v0.0.19/pkg/engine/dtrack.go:62
github.com/interlynk-io/sbomqs/cmd.glob..func1
	github.com/interlynk-io/sbomqs@v0.0.19/cmd/dtrackScore.go:48
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.7.0/command.go:940
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.7.0/command.go:1068
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.7.0/command.go:992
github.com/interlynk-io/sbomqs/cmd.Execute
	github.com/interlynk-io/sbomqs@v0.0.19/cmd/root.go:42
main.main
	github.com/interlynk-io/sbomqs@v0.0.19/main.go:20
runtime.main
	runtime/proc.go:250

Without the 8080 port:
~ sbomqs dtrackScore -D -t -u https://dependency-track-api.myorg.com -k $DTRACK_API_KEY $DTRACK_PROJECT_UUID

2023-08-25T00:45:13.205-0400	DEBUG	engine/dtrack.go:46	engine.DtrackScore()
2023-08-25T00:45:13.207-0400	DEBUG	engine/dtrack.go:48	Config: &{Url:https://dependency-track-api.myorg.com ApiKey:**** ProjectIds:[de46d3c2-f650-4ea3-a15b-db3bc38c02da] Json:false Basic:false Detailed:false TagProjectWithScore:true}
2023-08-25T00:45:13.207-0400	DEBUG	engine/dtrack.go:58	Processing project de46d3c2-f650-4ea3-a15b-db3bc38c02da
2023-08-25T00:45:13.808-0400	DEBUG	engine/score.go:126	Processing file :

2023-08-25T00:45:13.808-0400	DEBUG	engine/score.go:129	os.Stat failed for file :

failed to stat
Error: stat : no such file or directory

Looks like it might be a connectivity issue on my end, most likely.

Yes, and failed to stat  Error: stat : no such file or directory is an sbomqs bug, which i have fixed, and will release tomorrow.

@aravindparappil46 v0.0.20 has been released, i have attached a success log, and how it looks like it. Please feel free to reach out if you have any other suggestions or feedback.
sbomqs dtrackScore -D -u "http://localhost:8081/" -k "bAjCEERhYfm0gqi6GLzcu5FwuQgdcp5p" 7b381c1c-a7d2-4f49-a643-fc005cbe8260 -b -t
2023-08-24T23:01:29.047-0700    DEBUG   engine/dtrack.go:46     engine.DtrackScore()
2023-08-24T23:01:29.048-0700    DEBUG   engine/dtrack.go:48     Config: &{Url:http://localhost:8081/ ApiKey:bAjCEERhYfm0gqi6GLzcu5FwuQgdcp5p ProjectIds:[7b381c1c-a7d2-4f49-a643-fc005cbe8260] Json:false Basic:true Detailed:false TagProjectWithScore:true}
2023-08-24T23:01:29.048-0700    DEBUG   engine/dtrack.go:58     Processing project 7b381c1c-a7d2-4f49-a643-fc005cbe8260
2023-08-24T23:01:29.176-0700    DEBUG   engine/score.go:126     Processing file :/tmp/tmpfile-7b381c1c-a7d2-4f49-a643-fc005cbe82603568878701

2023-08-24T23:01:29.180-0700    DEBUG   sbom/sbom.go:151        SBOM detect spec:cyclonedx format:json
2023-08-24T23:01:29.194-0700    DEBUG   engine/dtrack.go:91     Project: []
2023-08-24T23:01:29.194-0700    DEBUG   engine/dtrack.go:100    Tagging project with sbomqs=8.3
2023-08-24T23:01:29.194-0700    DEBUG   engine/dtrack.go:101    Project: [{Name:sbomqs=8.3}]
8.3     ID: 7b381c1c-a7d2-4f49-a643-fc005cbe8260, Name: TestProject, Version: 1

Thank you @riteshnoronha ! It works perfectly now 🥳

@aravindparappil46 hope the integration is going fine. Wondering if you guys have any feedback or feature requests.

@riteshnoronha Yes, all good so far.
One of the things we are pondering about is the installation mechanism, specifically the need for go in the build environment. We use elastic Bitbucket Cloud runners and currently have to install go (or use a base Docker image that has go) before installing sbomqs on the CI runner. Would be nice to just yum install or apt-get install sbomqs. Not a big issue, of course. Just a good-to-have

Good suggestion. Will add it, at a later point. https://github.com/interlynk-io/sbomqs/issues/189


feat: ✨ syn-copy-button

Story

As a user of the Synergy Design System, I would like to use a copy-button for copy of text into the clipboard.
See https://shoelace.style/components/copy-button
Acceptance criteria

[ ] All DoD items successfully completed

blocked by https://github.com/synergy-design-system/design/issues/150


Build fails with Rust 1.24

Not sure why, but the generated bindings have changed.
Fix here: https://github.com/glyn/jvmkill/tree/rust-1.24
Need to confirm with earlier version of Rust. Check that bindgen version hasn't changed too.

@nebhale Please note this issue.

Build also fails with Rust 1.23.

The machine I'm running on picks up bindgen 0.24.0 whereas CI is using bindgen v0.33.1.

Turned out it was necessary to issue cargo update to get the latest dependencies. Updated README to document this.


Screen rotates on plugin initialisation

Whenever we call openLoginActivity, SumUp forces portrait orientation, which is inconvenient for our users, especially if it's lying flat on a table. They're forced to pick the tablet up and wiggle it a bit, to get it back in to landscape.
Please consider fixing this. It's a pretty old issue at this point, but I can only see https://github.com/sumup/sumup-android-sdk/issues/72 which is about the payment flow.
Thanks.

You can change screen orientation settings in your manifest file. Just override the library manifest in your project. Add this code to app manifest file and will be ok:

You must do this for all SumUp activities.

Thanks, we need to support both orientations though.

Just change in the manifest to android:screenOrientation="sensor"

This works great for the login activity. What activity would one need to change for the payment screen to have the landscape orientation?

I think I found all of them and so I want to share it. Here is the needed configuration, just put your needed screenOrientation:
<activity android:name="com.sumup.merchant.ui.Activities.BtTroubleshootingActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.BtTroubleshootingActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.CheckoutAPIDrivenPageActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.DashboardActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.LoginActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.PaymentSettingsActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.PinPlusSetupActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.ResendReceiptActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.SendSmsActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.SumUpBaseActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.SupportActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.ui.Activities.TransactionStateActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.api.LoadSumUpPaymentsActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>
<activity android:name="com.sumup.merchant.api.LoadSumUpPaymentSettingsActivity"
  android:screenOrientation="sensorLandscape"
  tools:node="replace"
  tools:replace="android:screenOrientation"/>

Sounds like a great workaround until SUMUP gets around to no longer force the orientation in it's SDK Manifest.xml .

about me this dont, work


Corrected dns_sync to create proper srv records:

do not use treadmill dns zone, it is implied (otherwise records are
created with dns domain concatenated.)
remove stale srv records pointing to hosts no longer in DNS.

Codecov Report

Merging #114 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #114      +/-   ##
==========================================
- Coverage   17.37%   17.36%   -0.02%
==========================================
  Files          60       60
  Lines        2878     2880       +2
  Branches      322      320       -2
==========================================
  Hits          500      500
- Misses       2340     2342       +2
  Partials       38       38

Impacted Files
Coverage Δ

lib/python/treadmill_aws/dns_sync.py
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Fixes

Was trying to fix a crash i encountered on the world map, but OCD got in the way.
Hope some of it will be useful.
BTW, i had half an idea to add some kind of button to the characters screen to edit the backstory, kind of like the "edit appearance" button of detailed character creation. would you be interested in that kind of feature?

I'm waiting for Bannerlord to release version 1.2.X for the stable branch, and then I'll delve into the code to address the version issues.
Unfortunately, I don't see much of a fix here (aside from one in the behavior.cs) Also combining your fix with the indentation fixes might make it a bit harder to read.
Additionally, some of the code in this repository is outdated because I've pushed several patches since the last update (to accommodate certain features), so it's possible that your fix has already been addressed.

yeah, the crash fix was strictly in the first commit, (behavior.cs), so you could cherry-pick it easily. where can i find those patches? can you push them on a dev branch?


Add accessor method to extract the "client" from an MLFlowLogger object

As discussed on a call.
I know we have been calling this client but I wonder if this is really the correct word, since it is on a server most (all?) of the time. I see that MLFlowClient.jl documentation calls an instance of MLFlow an "MLFlow API service", so maybe "service" is a better work for this.

You're completely right. service is a better naming for this kind of instance.


Create indexes on User locator ids and Journal issns

User locator ids and Journal issns are both lists of string that have to be indexed appropriately in order for searches on them to be fast. This pr adds indexes on the tables which handle those properties.

Upgrade script for the database. I tested against a database  generated from previous version of pass-core and then was able to successfully use this version of pass-core. Also removed the index annotations so it just does the table name change.
ALTER TABLE journal_issns RENAME TO pass_journal_issns;
ALTER TABLE user_locatorids RENAME TO pass_user_locatorids;

CREATE INDEX pass_journal_issns_id_ix ON pass_journal_issns (journal_id);
CREATE INDEX pass_journal_issns_issn_ix ON pass_journal_issns (issns);

CREATE INDEX pass_user_locatorids_id_ix ON pass_user_locatorids (user_id);
CREATE INDEX pass_user_locatorids_locator_ix ON pass_user_locatorids (locatorids);

ALTER TABLE user_locatorids RENAME TO pass_user_locatorids;

One change to executed script for the statement above, it changed to:
ALTER TABLE pass_user_locatorids RENAME TO pass_user_locators;

To match name in java


Switch to use vmlinux header and update libbpf to v1.2

- What this PR does and why is it needed

- Special notes for reviewers

- How to verify it

- Description for the changelog

/test ingress-node-firewall-e2e-metal-ipi


Bug: Stuck on Token FE loading screen

Bug report
Describe the bug
The Token FE is stuck on the initial loading screen and is failing to connect to a wss endpoint in the developer tools. Metamask keeps popping open and prompting user to re-authenticate. Authenticating with metamask (enter my password) cleared the loading and shows the Token FE correctly/immediately. Also had reports of getting stuck on loading screen when switching networks in MM.
Environement
token.vega.xyz / chrome / macOSX
Had been previously logged in to metamask and token FE in same tab, around 24 hours ago.
Expected behavior
To not be stuck at a loading screen but show me the Token FE with a need to connect to my Ethereum wallet etc.
Screenshots

Browser:
You’re using Chrome 96.
Additional context
Matt: "Basically the issue is that if you have previously connected, but then if Metamask requires permissions again we aren’t handling what happens if the user rejects MM at this point"
This thread 👉 https://vegaprotocol.slack.com/archives/C8WS7M50E/p1637612247356500

I left my TFE open overnight was on Governance tab and then moved to withdraw page and now see the chunk load errors   and a blank screen. I am unable to revive it without refreshing the page.
@mattrussell36 @campbellssource - Are we happy with this behavior as we no longer are getting websocket connection errors ? Please advise.

I thought this bug was something else and so the PR reference above is not the fix. This still needs to be done. My bad!

Looks like there have been at least 2 different causes of this.

1 a release while a user has the site open
memory leak
ssl cors

Action: Test by leaving a tab open overnight

Closing this as it has not been seen for a while


[ALLUXIO-628] Fixed Style checker failed to find an indent problem

https://alluxio.atlassian.net/browse/ALLUXIO-628
This one prepares the change in the configuration in Checkstyle.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9509/
Test PASSed.

Merged build finished. Test PASSed.

What is the style used here? The IntelliJ formatter recommended for the Alluxio project uses the original formatting.


Remove useless condition

Maybe the code is leaves for easy understanding ？

Maybe the code is leaves for easy understanding ？

Actually I thin its a mistake because it was manually translated from https://github.com/eclipse/paho.mqtt.java/blob/master/org.eclipse.paho.client.mqttv3/src/main/java/org/eclipse/paho/client/mqttv3/MqttTopic.java#L253-L319
The main thing to be careful is that whether this inspection is correct (from first glance this does appear to be the case).

Let me merge this PR myself, since we are dealing with mqtt I need to re-run the tests until the pass (just to make sure) and I will also wait for one more reviewer just to be safe.

Okay all tests pass, lets wait for another review incase any one of us missed something.


Integration tests for Playground CLI requests

Description
DiceDB Playground is an interactive platform that allows users to experiment with DiceDB commands in a live environment, similar to the Go Playground. Users will be able to submit and execute commands directly through a web interface. The initial implementation will focus on enabling users to search for and trigger commands.
For more details about DiceDB playground you can check here.
As part of this task we need to enhance unit tests and integration tests for /cli API.
This task would be extension of https://github.com/DiceDB/dice/issues/727
Details
Validation:

Validate the incoming request to ensure required parameters (key, value, COMMAND_NAME) are provided.
Ensure appropriate HTTP response codes are returned based on success or failure scenarios.

Testing:

Unit tests for the new /cli handler to cover success and failure scenarios.
Integration tests that send various DiceDB commands via the CLI endpoint and check for correct responses.

Dependent on https://github.com/DiceDB/dice/issues/727

Can I Take this up once it is implemented?

@karandixit10 assigned, thanks for contributing. Please let me know if any other details required. Also you can collaborate with assignee of other issue.

@karandixit10 please let us know if you require any help with this.

@karandixit10 please let us know if you require any help with this.

I'll try to add this by EOD

Hi @lucifercr07  Do I have to create a mock DiceDB client to isolate the HTTP handler for Unit tests?

And will the folder structure for integration_tests be same as DiceDB tests?

@karandixit10 we can keep the same.

Hi @lucifercr07 for integration test I have to run DiceDB server in the terminal so will it fail in the CI when pushed?

Hello @karandixit10,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

@lucifercr07 @karandixit10 please assign me this issue, i'll be working on it


Add helm install to e2e test framework

Please describe the Improvement and/or Feature Request

In addition to installation via the osm cli, helm install needs to be added as another installation process to the e2e test framework regardless of specific scenarios we are testing.
Scope (please mark with X where applicable)

New Functionality          [ ]
Install                    [ ]
SMI Traffic Access Policy  [ ]
SMI Traffic Specs Policy   [ ]
SMI Traffic Split Policy   [ ]
Permissive Traffic Policy  [ ]
Ingress                    [ ]
Egress                     [ ]
Envoy Control Plane        [ ]
CLI Tool                   [ ]
Metrics                    [ ]
Certificate Management     [ ]
Sidecar Injection          [ ]
Logging                    [ ]
Debugging                  [ ]
Tests                      [X]
CI System                  [ ]
Project Release            [ ]

Possible use cases

@ritazh How were you thinking this should work? The ways I can think of:

Configure the installation method directly in each test's code
Add a new command line flag to make all the tests run with a particular installation method
Start building a matrix and always run all the tests with both methods

@nojnhuh Ideally we should have every test run against a cluster with helm install and against a cluster with the osm cli to ensure both deployment methods have full coverage.

@ritazh If we do the same thing for all the other install parameters like cert manager, egress enabled/disabled, permissive traffic policy, etc., I worry that every combination of different parameters would make the suite way too big. And since osm install is essentially a thin wrapper over helm install with some custom validation, I'm not optimistic we would find any issues in the e2e suite that are neither unique to one method nor can be replicated with a unit test for the osm install command.
I would suggest we add one or two tests that use Helm directly, but not run every single test with both methods.

I worry that every combination of different parameters would make the suite way too big

@nojnhuh This is definitely a valid concern. I think at a minimum, we need to test if the installation via helm install installed all the components with the default values provided in the values.yaml and that they are running successfully. We want to catch issues like https://github.com/openservicemesh/osm/issues/1829 before a PR is merged or before a release is cut.

@ritazh I don't disagree with anything you're saying, but I think the mechanics of testing that are a little tricky.

We want to catch issues like #1829 before a PR is merged or before a release is cut.

I'm just thinking out loud here, but isn't this kind of a chicken-egg problem? Since helm install with no value overrides will use the last tagged osm-controller image, even if an osm-controller bug like that is fixed in a PR, the test will use an older osm-controller image without the fix, so the test will still fail. To update the osm-controller, we would need to make a release, but we shouldn't make a release if tests are failing.

I think at a minimum, we need to test if the installation via helm install installed all the components with the default values provided in the values.yaml and that they are running successfully.

I think if we want to ensure installing with the default values works for a tagged release, we need to override at least the image.tag value in CI to simulate the behavior of the default values for a tagged release. Testing without any overrides would need to be done only after the tagged images have been pushed.

The test will use an older osm-controller image without the fix

To test the binary changes in a PR, the CI can build an image from the PR, load it to the kind cluster, then set the image value to the local image we just built for helm

Yeah, that's the flow we have implemented right now for the other tests. To test with the default values though (i.e. not overriding the image) we could really only do that on the tagged commits or else we'll get version skew.

To test with the default values though (i.e. not overriding the image) we could really only do that on the tagged commits or else we'll get version skew.

Can you please expand on this? Why do we not want to override the image? I was suggesting that we could build the image locally in the pipeline, load the image to the kind cluster, then override the image in the chart to test the PR.

Perhaps I wasn't fully understanding your earlier comment:

I think at a minimum, we need to test if the installation via helm install installed all the components with the default values provided in the values.yaml and that they are running successfully.

I think I was reading that as "We should test that a plain helm install osm ./charts/osm without any overrides works for each PR.
But yes, I agree we should override the image tag to use one built with the source from the particular PR we're testing.


Support headers for accessing the Remote Services

The problem faced currently?
It's great that we can convert RESTful Web API to GraphQL. However, when accessing the Remote Services, quite often we need to provide some security secrets along with our requests. In my case, I need to include a couple of HTTP headers, but I couldn't find any way to do it.
How can we solve it?
Please allow specifying HTTP headers as part of the Remote Service setting or Per Endpoint setting, just like what we can do on Postman. Thanks.

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important to you.
👍

Hey, @waynesi Thanks for the feature request! That's actually a very valid use case. Implemented this in the v0.18.0 (about to be released in a day).

To be clear, we will be allowing this on a per endpoint level. @waynesi

That's really great news. Thanks a lot for the update and super quick turnaround. Much appreciated!

Done. Coming in 0.18.0

Sorry. I've just pulled down 0.18.0 but I can't see where to add the headers?

Head over to remote services. Open up an endpoint. You should be able to see the headers config in the advanced config.
If you can't see it there, make sure you delete mission-control from $HOME/.space-cloud directory or refresh with cache disabled to see the latest mission control

Thanks a lot. After destroying the environment and deleting the .space-cloud folder, I can see the new options now. Brilliant. Thanks.

We'll update the docs soon enough for this. Meanwhile, feel free to reach out on Discord if you need help.