[FEATURE]: Create Train and Test Datasets from User-Uploaded Dataset in S3 for /training

Feature Name
Create Train and Test Datasets from S3 for /training
Your Name
Daniel Wu
Description
As of right now, the training backend can only handle default datasets for /tabular. Allow user-uploaded datasets to be used for tabular training by implementing a dataset creator in training/dataset.py to allow the /tabular endpoint route to read a file from s3 given the filename and split it into train and test datasets.
Right now, datasets are stored in s3 in the dlp-upload-bucket in the location {uid}/{trainspace_type}/{filename}.
You can upload files to the bucket with https://em9iri9g4j.execute-api.us-west-2.amazonaws.com/ SST prod endpoint and /datasets/user/{type}/{filename}/presigned_upload_url route.
You will need a bearer token also, which can be obtained using the backend cli. For more info, cd training && poetry run python cli.py --help.

@NMBridges youre doing this task

@NMBridges My bad, this task should deal with reading the dataset files from s3 into training, not writing files to s3.

https://github.com/DSGT-DLP/Deep-Learning-Playground/blob/nextjs/training/training/core/dataset.py
should be the file to implement this endpoint in @NMBridges

@NMBridges also, assume the scope of this use case to be for tabular (so reading CSV from S3 and then building train/test dataset). See example dataset creator class in the linked file


i18n(fr): Update astro-components.md to follow changes from #522

What kind of changes does this PR include?

[x] New or updated content
[x] Translated content

Description

What does this PR change? Update the current french translation with latest change on this page

Oops, why it was closed


SA1101 wrongly triggers on local generic functions

Summary
SA1101 (prefix local calls with this) is wrongly triggered when making a call to a generic local function from within an instance method of a class.  It is not triggered when making a call to a generic local function from within a static method, or a non-generic local function.
Expected Behaviour
SA1101 is not triggered when making calls to a generic local function from within an instance method.
Observed Behaviour
SA1101 is triggered.
Library versions tested:

StyleCop.Analysers v1.1.118
StyleCop.Analysers.Unstable v<IP_ADDRESS>

Steps to Reproduce
Try the following minimal program:
//------------------------------------------------------------------------------
// <copyright file="Program.cs" company="PlaceholderCompany">
// Copyright (c) PlaceholderCompany. All rights reserved.
// </copyright>
//------------------------------------------------------------------------------

namespace UsesLocalFunction
{
    using System;

    /// <summary>
    /// The <see cref="Program" /> class holds the entry-point of the application.
    /// </summary>
    internal class Program
    {
        /// <summary>
        /// Entry-point of the application.
        /// </summary>
        /// <param name="args">Command-line arguments.</param>
        public static void Main(string[] args)
        {
            SayStaticGenericThings();

            var app = new Program();
            app.SayThings();
            app.SayGenericThings();
        }

        private static void SayStaticGenericThings()
        {
            var narrator = "Static Generic Simon";
            void Say<T>(T phrase) => Console.WriteLine($"{narrator} says, \"{phrase}\"");
            Say("Hello, world!"); // Does not trigger SA1101
        }

        private void SayThings()
        {
            var narrator = "Simon";
            void Say(string phrase) => Console.WriteLine($"{narrator} says, \"{phrase}\"");
            Say("Hello, world!"); // Does not trigger SA1101
        }

        private void SayGenericThings()
        {
            var narrator = "Generic Simon";
            void Say<T>(T phrase) => Console.WriteLine($"{narrator} says, \"{phrase}\"");
            Say("Hello, world!"); // Triggers SA1101!
        }
    }
}

Duplicate of #3018


Add support for extra buttons on the landing page

I got a need for extra buttons on the landing page besides the View Documentation and View on Github buttons, with configurable destination URLs. The use case is to have the landing page as the main entrypoint for an application, with both "View Documentation" and "Get Started" buttons in the same place.
This PR adds another config option called "buttons" (modeled after "links"), as a String => URL hash for extra buttons to the right of the default View Documentation button. Tested and works as expected for static page generation ("php generate.php").

Interesting, I will give it a more in-depth look in the following days.


not working on osx 10.12.3 ?

Environment

Operating System: osx 10.12.3
IDE Version : 2016.3.2
Cppcheck executable version (cppcheck --version): 1.77
Cppcheck plugin version: 1.07
Exact strings used in cppcheck plugin options:

cppcheck path: /usr/local/bin/cppcheck
cppcheck options: --enable=warning,performance,portability,style, --language=c++

Expected behaviour
report an error for this
int main() {
  int x[1];
  x[2] = 1;
}

Actual behaviour
didn't get any error msg
Steps to reproduce the behaviour

Just tested on OSX 10.11.6 and CLion 2016.3.3 and it worked as expected.
I installed Cppcheck with Homebrew.
$ brew update
$ brew install cppcheck

Installed the Cppcheck CLion plugin and configured the path for cppcheck in Settings > Other Settings > cppcheck configuration.
Did you configure the plugin after installing it?

Yes, i did. Here is my configuration.

And the result.

Oh, i know what's wrong. I got an extra comma in the options.
with --enable=warning,performance,portability,style --language=c++, it works fine.
Thanks, amazing plugin!

Great, glad it's working out for you.


Added returns to code examples

Forgive me if I'm wrong, but I'm pretty sure you need these!

ahah nice catch, thanks


Create VideoAdScripter

📝 Description
Add a brief description.
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information
lol

Dear user, thank you for your contribution. Our Hacktoberfest event will officially begin on 10.01. To facilitate the event calculations, we will merge your pull request once the event starts. Additionally, ILLA offers various gifts that you can earn by contributing to the AI Agent or ILLA App and accumulating points. For more information about the event, please visit: https://www.illacloud.com/hacktoberfest2023.


Nifi 2829

Implemented fix for JIRA
https://issues.apache.org/jira/browse/NIFI-2829
Provided logic that will attempt to string parse Dates and Time values if they do not match LONG_PATTERN.
The parameter sql.args.#.format may be used to provide the Date, Time or Timestamp parsing string.

@paulgibeault would you mind squashing this PR?
I thank you in advance

Yes I can squash this, as soon as I learn how.  I am new to this.

I accidentally polluted this branch.  I will re-open when I have cleaned it up.


How do I switch php version on vccw3 ?

Do you need to add any software?

phpenv is no longer supported on VCCW v3.


Fix plugin startup

Still WIP to fix startup

Interesting. Thank you for your help. At the end, I think the editable install for development will be the best.
And if you’re thinking what bare plugin this is 😄 , I already have something implemented locally without a inventree connection which I’m excited to share if it’s working.

@wolflu05 there are some improvments coming to inventree/inventree/master soon that will help with some anoyances.
Excited to see what you are cooking up, please feel free to share it in inventree/inventree once you want to show it off - we are happy to link to projects in the community.

Thank you very much for your help and time. I'll come back if something is showable or I have further questions.


LearnSidebar macro: Fix spelling of "Object building practise"

The title of the article "Object building practice" is listed in LearnSidebar using the British spelling "Object building practise". This needs to be corrected to match the style guide usage of American spellings.

Done: https://github.com/mdn/kumascript/pull/1138
Can I get a review, please?

@a2sheppy


Add an example using the cluster registry

/sig multicluster
Idea: a document plus a simple controller that accesses a cluster registry. Ideally something that someone can run by copy/pasting commands to get up and running as quickly as possible.

@pmorie and I are going to sync up on this today.


Upgraded geocoder gem.

Upgraded geocoder gem. Fixed #1115.

new pull request

Thanks @jasnow :snowboarder:


Update gitstream.cm

In this version, we've:
Removed the label_from_branch automation
Added the label_unresolved_threads automation
Added the flag_deleted_files automation
Included the has.deleted_files custom expression used by flag_deleted_files
If this configuration works, we can then focus on troubleshooting the label_from_branch automation. We'll try to identify what part of that automation is causing the parsing error.

Clearly appears that the issue is with the new label from branch automation we were trying to create


runtime/pprof: StopCPUProfile occasionally stuck with 100% CPU and process hang

What version of Go are you using (go version)?

go1.18.0

Does this issue reproduce with the latest release?
Not sure.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/breezewish/Library/Caches/go-build"
GOENV="/Users/breezewish/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/breezewish/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/breezewish/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/homebrew/Cellar/go/1.18.1/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/homebrew/Cellar/go/1.18.1/libexec/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.18.1"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/6m/phy2_frd0vd1hb7g1py32qz40000gn/T/go-build2219610054=/tmp/go-build -gno-record-gcc-switches -fno-common"
GOROOT/bin/go version: go version go1.18.1 darwin/arm64
GOROOT/bin/go tool compile -V: compile version go1.18.1
uname -v: Darwin Kernel Version 21.4.0: Fri Mar 18 00:46:32 PDT 2022; root:xnu-8020.101.4~15/RELEASE_ARM64_T6000
ProductName:	macOS
ProductVersion:	12.3.1
BuildVersion:	21E258
lldb --version: lldb-13<IP_ADDRESS>
Apple Swift version 5.6 (swiftlang-<IP_ADDRESS>3.62 clang-13<IP_ADDRESS>)

What did you do?

In tidb-server there is a feature with a pattern that repeatedly run pprof CPU profiler for 1 second (StartCPUProfile -> wait 1 sec -> StopCPUProfile -> StartCPUProfile -> wait 1 sec -> ...).
Recently in my MacOS M1 with this feature enabled, I observed that the tidb-server process was hang with 100% (1 core) CPU and it cannot process any requests.
According to the CPU profiling data provided by Instruments, looks like StopCPUProfile was looping infinitely at https://github.com/golang/go/blob/016d7552138077741a9c3fdadc73c0179f5d3ff7/src/runtime/proc.go#L4641:

I have no idea how this issue can be reliably reproduced. Hope the stack provided by the Instruments helps.
What did you expect to see?
StopCPUProfile should not cause process hang.
What did you see instead?
Process was hanging.

try killing it with SIGABRT and see what it's doing?

@seankhliao Not reproduced recent days, will try with SIGABRT when it happened. Meanwhile do you have other ideas or suggested measurements I can take to keep some necessary information when it reproduce the next time?

Could this be a memory-order / weakness problem with M1 / ARM64? The defense against this deadlock is setting m.profilehz = 0 (in https://github.com/golang/go/blob/go1.18/src/runtime/proc.go#L4569 / https://github.com/golang/go/blob/go1.18/src/runtime/signal_unix.go#L328), which gets checked at the top of the SIGPROF handler (at https://github.com/golang/go/blob/go1.18/src/runtime/proc.go#L4450).
The store and load of m.profilehz are non-atomic, which seems like it could be a problem on ARM64. But those take place on the same thread (store on the curg and load on the gsignal of a particular M), which seems like it could mitigate that problem. @ianlancetaylor , do you know if there's something to that, or would brokenness there show up as even bigger problems? Thanks.

If you reproduce this again (or still have the profile), could you expand the _sigtramp part of the profile? That is probably holding signalLock and does seem to be stuck somewhere.

@rhysh I see where you are coming from, but if we hit that race, shouldn't we be stuck spinning in the signal handler when the deadlock occurs, not setcpuprofilerate? To also get stuck there I think we would need a second concurrent caller to StopCPUProfile.

sigprofNonGoPC takes prof.signalLock via cpuprof.addNonGo, and is only protected by a check of prof.hz, which (1) is non-atomic, and (2) we don't modify in setcpuprofilerate until after taking signalLock.
Thus I believe it would be possible to get a deadlock in the signal handler if we go down the addNonGo path.
That said, we are in fact running Go code, so we should avoid that path. setProcessCPUProfilerTimer makes a few libc calls. Perhaps if those get interrupted at just the right point we are unable to get the G?
There would also need to be a second call to StopCPUProfile on another thread to have the stuckness in both StopCPUProfile and sigtramp that is shown in the profile.

https://go.dev/cl/420196 makes prof.hz atomic. It is part of a general atomics cleanup and I don't think it will make a difference here, but if this is easily reproducible then it may be worth testing.

FWIW, I have been unable to trivially reproduce this on darwin-arm64 calling StartCPUProfile/StopCPUProfile in a loop (with some extra work to ensure we get SIGPROFs).

I don't expect it to make a difference, but it is possible.
@breezewish can you reproduce this at tip?

It seems to be hard to reproduce in my M1 in recent days. We have some production env using this Go version now and I will ping back when encountering more deadlocks like this. Thanks a lot for the dig!


Added support for function in field dataClass

Now we can use function to format cells according to rowData and/or rowIndex. The function accepts the rowData and the rowIndex as arguments.
Ex:
{
        name: 'price',
        title: 'Price',
        dataClass: function(rowData, rowIndex){
            if(rowData.change < 0){
                return 'bg-red'
            } else {
                return 'bg-green'
            }
        }
 }

@topclaudy Thanks for the contribution. It's look useful and I might incorporate this idea into the next version of Vuetable. However, I might not pass item and item index into the function.

@ratiw Thanks for the feedback. How would we access the row data if we don't pass item into the function?

@topclaudy Logically, dataClass is the attribute of a column. It should not has access to the "row" data.
I would instead pass the field definition and "value" of that field to the function.
If you would like to change the background of the row, you should instead use row-class prop, which has access to row data and row index. See example here.

@ratiw Good point! In my situation, I needed to set the class based on the value of another column (see example). Hence the reason I passrowData as parameter.

+1 for the feature request

+1

+1

@ratiw doesn't seem open to the idea.

That's a pity. It would make things much more powerful. I'm starting to find some alternate table plugin already...
@ratiw can you consider it, please? Or perhaps give an alternate option where user can modify the output value of a single table cell? Scoped slots perhaps?

Well, it's not that I'm not open to the idea. Whenever I have time to update the library, I'm always thinking about this specific issue. I'm more incline implement this into Vuetable, but most of my time
has been focusing on update the documentation for the next version of Vuetable. Then, it will be
other pending stuffs, both PRs and issues.
The recommended solution is to use Field Component in v2.0 of Vuetable, which is available in the next branch. With Field Component, you'll have complete control over the th and td element. It is much more powerful and can easily be reused.
Unfortunately, time is not always on my side. There is so much I can do with the time that I can work on Vuetable.

@ratiw thanks for your response!
Field Component sounds like a great idea. Can't want to start using it. I'm implementing Vue Table on a large cryptocurrency site currently and it would be super cool if you can give a rough timeline for the next release? This way I can perhaps use the next branch and later update to the stable release.
Thanks already for this great plugin btw. After the documentation is officially released, it would be super awesome. Similar to how Bootstrap Vue is: https://bootstrap-vue.js.org/

@zeshanshani You can start using them now, just follow the instruction in the documentation here. It has been in the alpha stage for quite sometime already. The beta is quite stable in my opinion. I push it out so that people can try and give me some feedbacks. A few more features need to be added when I have time.

@ratiw that's awesome! I'll give it a try then. Thank you! :)

@ratiw feedback:
I used the next release and this is working really well. So here's what I've loved so far:

Simplicity in importing as ES6 module. I just had to use this line to pull both table as well as pagination: import {Vuetable, VuetablePagination} from 'vuetable-2'

Each and every row cell's value can be changed and even put custom HTML to it by simply using field slots (THIS IS HUGE): https://upbeat-montalcini-9fc063.netlify.com/guide/special-field.html#field-slot

Documentation - this is one of the best things happened to Vuetables-2 plugin.

So a big thank you for making these updates 🙏


timeout creating large repos

Looks like the default timeout for the rsync operation is 600s which isn't long enough to rsync a big repo (like epel) for the first time.  shell_out() does allow a timeout parameter, but that isn't currently set by this cookbook.
What do you think is the best way to set this timeout?  We could add another property to rsync_mirror.rb which would allow the timeout to be set in yumserver_rsync_mirror.  Does this seem like a useful enhancement?  If so I could look at adding a PR.

BTW, I found a commit that looks like it addresses this problem in one of the forks: https://github.com/mwiczynski-cartera/yumserver-cookbook/commit/6d4a2c6daad13091f136b37dca978a97241b52a6

I had actually intended to do something like this at some point as it would also satisfy #8 with a greater degree of flexibility.
I'll see about cherry picking in the changes later and adding some documentation.

Cool, thanks!


Adopt multiapps 2.7.0

Adopt 2.7.0 version of multiapps plugin for CF.

Hi @a-b,
Could you please review and merge this PR?
Thanks and best regards,
Ivan

Hi @jdgonzaleza,
Could you please review and merge this PR?
Thanks and best regards,
Ivan


Run/Debug/Coverage buttons appear on swift-testing argument TestItems

Describe the bug
Run/Debug/Coverage buttons appear on swift-testing argument TestItems and nothing happens when you click on them
Expected behavior
Run/Debug/Coverage buttons do not appear. Although ideally they should be there and run the test with that argument.
Environment

OS: macOS 15
Swift version: 6
Visual Studio Code version: 1.94.2
vscode-swift version: 1.11.3

Verified on e7f81c930e752bb049fc7c5fae8e98684bd8b54d
Snippet below will no longer display Run/Debug/Coverage buttons
import Testing

struct Day01Tests {
    @Test(arguments: [1,3,2]) func part1(_ x: Int){}
}


 elements render on its own line in .epub files

I may be missing an option that I'm supposed to pass here to get <kbd> elements to correctly render inline. Thoughts?
# book.toml
[book]
title = "The Rust Programming Language"
authors = ["Steve Klabnik", "Carol Nichols", "Contributions from the Rust Community"]

[rust]
edition = "2021"

[output.pandoc]
hosted-html = "https://doc.rust-lang.org/book"

[output.pandoc.profile.epub]
output-file = "rust-book.epub"
table-of-contents = false

[output.pandoc.profile.epub.variables]
epub-cover-image = "cover.png"
epub-title-page = false

This seems to be the result of a preprocessing pass that inserts divs to make sure Pandoc generates valid EPUB. It shouldn't be touching inline HTML like this, so I'll look into a fix

#112 should fix this issue, thanks for reporting! I'll publish a new release shortly

I released 0.7.2 which should fix this


Add server nickname to internet network ssid

We see  now that it's very often that we have more than one server up during the setup, so it would be great to avoid ssid conflicts, and thus using the server hostname instead of hardcode Ideasbox, imho.
Of course, when we will be able to change the ssid name from within the ideascube admin UI this would be easier to do, but as default I think having unique ssid still makes sense.

This has been updated in ansiblecube/roles/hostapd/templates/hostapd.conf.j2
It would be easy then to change the hotspot when the pull request https://github.com/ideascube/ideascube/pull/221 will be done

done.


Add main command

Created a command that checks the contents of a given Google DNS A record using http healthchecks to it updating it if necessary
Signed-off-by: Rafael Porres Molina<EMAIL_ADDRESS>

@rporres if it's not to hard to do now: can you push your vendor in a separate commit? that way I can filter it our while writing my GitHub code review

addressed comments :)


Unexpected HELM validation manifests behaviour

I've faced strange behavior of the HELM validation chart despite wrong fields and the structure of templates a chart deployed with success but with warnings. In comparison, a kubectl command fails when we have a wrong manifest etc.
(k8s: dp-dev-2-eks-eu-west-1 | ns: karpenter | ~/temp/chart-test)$ helm install --generate-name ./
W0516 18:19:14.688590   53980 warnings.go:70] unknown field "spec.someFake"
W0516 18:19:14.843096   53980 warnings.go:70] unknown field "spec.template.spec.disruption"
W0516 18:19:14.843114   53980 warnings.go:70] unknown field "spec.template.spec.kubeletConfiguration"
W0516 18:19:14.843119   53980 warnings.go:70] unknown field "spec.template.spec.limits"
W0516 18:19:14.843123   53980 warnings.go:70] unknown field "spec.template.spec.someFake"
NAME: chart-1715872751
LAST DEPLOYED: Thu May 16 18:19:13 2024
NAMESPACE: karpenter
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
  export POD_NAME=$(kubectl get pods --namespace karpenter -l "app.kubernetes.io/name=chart-test,app.kubernetes.io/instance=chart-1715872751" -o jsonpath="{.items[0].metadata.name}")
  export CONTAINER_PORT=$(kubectl get pod --namespace karpenter $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
  echo "Visit http://<IP_ADDRESS>:8080 to use your application"
  kubectl --namespace karpenter port-forward $POD_NAME 8080:$CONTAINER_PORT
(k8s: dp-dev-2-eks-eu-west-1 | ns: karpenter | ~/temp/chart-test)$

How to reproduce:

create chart with command: helm create chart-test
add some fake fields in the manifest template of Service

apiVersion: v1
kind: Service
metadata:
  name: {{ include "chart-test.fullname" . }}
  labels:
    {{- include "chart-test.labels" . | nindent 4 }}
spec:
  someFake:
    ttl: 300
  type: {{ .Values.service.type }}
  ports:
    - port: {{ .Values.service.port }}
      targetPort: http
      protocol: TCP
      name: http
  selector:
    {{- include "chart-test.selectorLabels" . | nindent 4 }}

add manifest for Karpenter NodePool with fake and wron fields:

apiVersion: karpenter.sh/v1beta1
kind: NodePool
metadata:
  name: default
  namespace: karpenter
spec:
  template:
    metadata:
      labels:
        workload: default
    spec:
      someFake:
        ttl: 300
      disruption:
        consolidationPolicy: WhenUnderutilized
        expireAfter: 30d
      kubeletConfiguration:
        containerRuntime: containerd
        maxPods: 110
      limits:
        resources:
          cpu: 3200
      nodeClassRef:
        apiVersion: karpenter.k8s.aws/v1beta1
        kind: EC2NodeClass
        name: default
      requirements:
      - key: karpenter.k8s.aws/instance-category
        operator: In
        values:
        - c
        - m
        - r
      - key: karpenter.k8s.aws/instance-cpu
        operator: In
        values:
        - "4"
        - "8"
        - "16"
        - "32"
      - key: karpenter.k8s.aws/instance-hypervisor
        operator: In
        values:
        - nitro
      - key: topology.kubernetes.io/zone
        operator: In
        values:
        - eu-west-1a
        - eu-west-1b
        - eu-west-1c
      - key: kubernetes.io/arch
        operator: In
        values:
        - arm64
        - amd64
      - key: karpenter.sh/capacity-type
        operator: In
        values:
        - spot
      - key: karpenter.k8s.aws/instance-generation
        operator: Gt
        values:
        - "6"

Run command: helm install --generate-name ./

Expected behavior: when we have templates/manifests with wrong structure and fake/wrong fields HELM should fail and not deploy.  It seems HELM should act like kubectl  - a message about an error with manifest and stop any activities. The command echo $? should not output "0".
Additional information: test HELM chart was tested with various scenarios and params eg: '--dry-run=server' etc.
helm version:
version.BuildInfo{Version:"v3.15.0", GitCommit:"c4e37b39dbb341cb3f716220df9f9d306d123a58", GitTreeState:"clean", GoVersion:"go1.22.3"}

kubectl version:
Client Version: v1.29.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3

Cloud Provider/Platform (AKS, GKE, Minikube etc.): AWS/EKS

We are also facing the same issue. @mattfarina has this behaviour changed in newer helm versions ?

I can confirm, and I'm not sure why the client-side validation implementation has stopped working:
https://github.com/helm/helm/blob/main/pkg/kube/client.go#L344-L352
What I think happened, is Kubernetes introduced service side validation. And somehow (speculating, I didn't track down how) the openapi validation done client side is no longer reporting errors. Server-side validation blog:
https://kubernetes.io/blog/2023/04/24/openapi-v3-field-validation-ga/
Helm also should to update to use server side validation, but likely compatibity concerns need to be considered.  Updating  is simplish implementation-wise., just needs to be determined how to pass the validation flag through to the Kubernetes API object helper. Like e.g. kubectl:
WithFieldValidation(o.ValidationDirective)

https://github.com/kubernetes/kubectl/blob/master/pkg/cmd/apply/apply.go#L568
Debugging why the client-side validation is not working should also be done (at least for the standard Service object. Karpenter nodeclass being a custom resource, it might not be possible).
This was also noticed back in this issue: https://github.com/helm/helm/issues/12470 . But I think work from here, as that issue started from a different question. And the PR there has languished.

The PR to introduce server-side validation looks something like: https://github.com/helm/helm/pull/13123
I don't think this can easily be implemented in Helm v3, due to the way Helm manages this Kubernetes client (schema validation is "per-operation". This client is constructed early and shared across operations (in the SDK)
Onwards to figuring out why the client side validation has failed I guess.

Hello everyone. I was looking for a way to contribute to Helm and this ticket looked interesting so I started diving into it.
I can confirm what @gjenkins8 stated about this being related to the switch in Kubectl to support server-side validation. I used git bisect to narrow down the commit where this was introduced (bd7c97f786f59b993dc34884f3d44ca0297f13e8), which bumped the kubectl version and updated client.go to utilize the new Kubectl Factory interface.
From here, I dove into what changed in Kubectl that broke client-side validation in Helm. I traced it down to the new Schema Validator function used. Specifically, https://github.com/kubernetes/kubectl/blob/b315eb8455a7d5c11ed788d1592b4afeca85771d/pkg/validation/schema.go#L140 appears to only run client-side validation if it detects that server-side validation is not supported for the resource. This can be verified by going back to a Kubernetes version before server-side validation was introduced (<1.25), where Helm commands error as expected when manifests contain invalid fields.
I tried to figure out a way to resolve this on the Helm side, but I came up short. Admittedly, my Go skills need some work. I was not able to come up with a clean way of resolving this that didn't involve updates on the Kubectl side. Perhaps this is worth a ticket with kubectl to add better support for explicitly running client-side validation?

I created a branch for kubectl that has a potential solution for this. It adds a preferredStrategy argument to the Validator function and the newParamVerifyingSchema struct. It's still a WIP, but I wanted to see if it would actually resolve the issue and it does.
I opened an issue with kubectl in case this is something that should be resolved on their end.

thanks @james-mchugh for the find

It looks like Kubectl confirmed that this is the removal of client-side validation from kubectl was a breaking change and they have no plans to add support back for it (outside of support for clusters that do not support server-side validation). The path forward appears to be to switch to server-side validation.

Yes, I also encountered this issue while my deployment pipeline showed errors in the Helm lint command. Despite all the error charts installed and deployment successful. It was a bit strange and I was hoping the pipeline would fail.


Returned Obj missing keys.

Expected behaviour
Returned object is missing fields.  Plugin docs state the return object should also have these keys - whether the values can be extracted or not (I think) is a different issue.  but i should at least see the entire Object (as stated in the docs) correct?
  "phoneNumber": "",
  "deviceId": "",
  "simSerialNumber": "",
  "subscriberId": "",

Actual behaviour
My result object is as follows, though it is returning carrierName, seems the actual carrier can't be extracted from my phone.
Object {
   callState:0
   carrierName:""
   countryCode:"us"
   dataActivity:0
   isNetworkRoaming:false
   mcc:"310"
   mnc:"260"
   networkType:13
   phoneCount:1
   phoneType:1
   simState:5
}

I'm seeing this behaviour on

[ ] iOS device
[ ] iOS simulator
[x] Android device
[ ] Android emulator

I am using

[x] cordova
[x] ionic
[ ] PhoneGap
[ ] PhoneGap Developer App
[ ] Intel XDK
[ ] Intel App Preview
[ ] Telerik
[ ] Other:

Hardware models
Samsung Galaxy 5S
OS versions
Android 6
I've checked these

[ ] It happens on a fresh Cordova CLI project as well.
[ ] I'm waiting for deviceready to fire.
[ ] My JavaScript has no errors (window.onerror catches nothing).
[x] I'm using the latest cordova library, Android SDK, Xcode, etc.

So how can we reproduce this?
Provide the used components versions (cordova, ionic, etc).
Cordova 6.0
Ionic 1.7.14 (intentionally not upgrading to 2.0 yet)
cordova-plugin-sim 1.3.0
Provide the steps to reproduce the issue.
Provide files, sources if available.

Check permissions
https://github.com/pbakondy/cordova-plugin-sim#android-60-permissions

yup...it was a permissions issue.  got it resolved.  Last question: is there away to set sim permissions in the config.xml/AndroidManifest.xml file?  I am using the cordova-plugin-diagnostics to add a bunch of permission for device settings but don't readily see an option for accessing the sim.
ie:
    <config-file target="AndroidManifest.xml" parent="/*">
        <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    </config-file>

Sure, check this:
https://github.com/pbakondy/cordova-plugin-sim/blob/master/plugin.xml#L31

sweet....great plugin.  and excellent support for it.  much appreciated.


chrome-remote-headless broken...

https://github.com/golemhq/golem/blob/71d4da2929423137bde436de71faf256d1607756/golem/browser.py#L101
should read:
with validate_remote_url(settings['remote_url']) as remote_url:

Thanks for reporting this issue @testjenk
Created a PR with your suggested fix: https://github.com/golemhq/golem/pull/154


Moved: Vivaldi.Vivaldi version 3.6.2165.40

This pull request is automatically generated by 🥟 Dumplings
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

/AzurePipelines run


Bump pallet-contracts version to 3.0.0-rc1

This bump is performed in expectation of a new substrate release soon(TM). There are already breaking changes in master [1, 2] and more are expected [1, 2] before 3.0.0 can be released.
The rcX suffix is a workaround to not be forced to bump the major version in rapid succession in this phase of applying breaking changes before  we go over to a more stable period (after 3.0.0 release).
@Robbepop @seanyoung

After talking to @gnunicorn I realized that this workaround is not necessary. By simply not bumping the version of pallet-contracts we can prevent the release of a new version during the next release cycle. This is what I prefer to do until we are ready to release 3.0.0-rcX.


Option to Hide Chart Line between certain points?

I'm working on a chart that has a few values that begin at 0 until the first point that is above 0.  I need the 0 points there to preserve proper spacing, but I also need a line between my points.  So my chart has a line at zero until the first point (see below)  I don't think there's a way to handle this currently?  It would be nice to be able to control the points the line begins and ends etc.

It might be best to be able to change the color of the line between certain points, that was you can use .clear if you want to hide it, but also gives the option to make the chart more dynamic by changing the color of the line above or below certain thresholds.

Try setting ignoreZero to true in LineStyle and see if that helps.  It worked well for me in a multi-line chart where the sets of data points did not have the same number of values.  I padded the shorter set with zeros and presented a chart line that stopped sooner than its counterpart.

@fredeiden thanks I've used ignoreZero to solve other issues but here particularly I was looking to keep the zero values so that they took up a space on the X Axis (yet not color the line above them)

Here is another idea.  This is cheating, but it looks right to an observer.  How about a MultiLineChart with two LineDataSet elements.  One is your set of numbers greater than zero, but padded with zeros at the front to push it to the right.  This has a LineStyle with ignoreZero set to true. The second LineDataSet has leading values of 0.01 and then trailing zeros.  This uses a LineStyle with a strokeStyle of Stroke(lineWidth: 0.0) and ignoreZero true.  In short, use a line of zero thickness when you only want to see the points.
Here is my test code and the chart it generates:
`
import SwiftUI
import SwiftUICharts
struct Chart: View {
var body: some View {

    let data = lineData()

    HStack {
        MultiLineChart(chartData: data)
            .pointMarkers(chartData: data)
            .xAxisGrid(chartData: data)
            .yAxisGrid(chartData: data)
            .padding()
    }

}

func lineData() -> MultiLineChartData {

    let lineStyleOne = LineStyle(lineType: .line,
                                 strokeStyle: Stroke(lineWidth: 1.0),
                                 ignoreZero: true)

    let lineStyleTwo = LineStyle(lineType: .line,
                                 strokeStyle: Stroke(lineWidth: 0.0),
                                 ignoreZero: true)

    let dataSets = [
        LineDataSet(dataPoints: [0,0,2,5,3,4,5,6,7,8].map { LineChartDataPoint(value: $0) },
                    style: lineStyleOne),
        LineDataSet(dataPoints: [0.01,0.01,0,0,0,0,0,0,0,0].map { LineChartDataPoint(value: $0) },
                    style: lineStyleTwo)
    ]

    return MultiLineChartData(dataSets: MultiLineDataSet(dataSets: dataSets))
}

}
`

@fredeiden good thought and very clever!


Feature request: task/debugger variables for current module.class.method

Environment data

VS Code version: 1.29.1
Extension version: 2018.11.0
OS and version: macOS 10.13.6
Python version: 2.7.15
Type of virtual environment used: virtualenv

This is related to #73, because in absence of a configuration option for discovering and running specific Django tests via manage.py test, I just run them from the command line, by typing or pasting something like my_app.tests.ModelTestCase.test_model_method.
To run a test in the debugger, I edit launch.json each time I switch tests, e.g.:
        {
            "name": "Django Test",
            "type": "python",
            "request": "launch",
            "program": "${workspaceFolder}/manage.py",
            "args": [
                "test",
                "--keepdb",
                "--failfast",
                "my_app.tests.ModelTestCase.test_model_method"
            ],
            "django": true
        },

I was thinking variable substition might allow me to write generic tasks and debugger configs for testing.
See also #3551.
Thanks for considering this, and your work on this extension.

What you're proposing is a work around for #73.
Let's focus on fixing that as opposed to adding work around.
Hence closing in favour of #73


Extension works fine in Firefox but have scrolling issue

I am able to access bing chat in firefox, but I couldnt scroll up to see my previous conversations. Can you please take a look.

I confirmed this problem is happening. Will investigate it soon.

Solution is simple, just set layout.css.overflow-overlay.enabled to true in about:config.

@amazingpaddy definitely working for me, probably you need to be on the beta (it works for me on developer edition)

Actually it does work with layout.css.overflow-overlay.enabled set to true on Firefox Stable (version 110.0) as well.

Yes I confirm now its worked after I updated my version to 110.0, earlier I was using Firefox version 109 and it didnt work..

@amazingpaddy Could you keep this open? I think this extension should set this config for the user (an extension is capable of setting about:config options on the user's behalf)

Sure. Reopened

@amazingpaddy Could you keep this open? I think this extension should set this config for the user (an extension is capable of setting about:config options on the user's behalf)

Hey, I've done some research and need help finding a reference to such documentation. On this website:

Does the WebExtensions API provide access to preferences?
No. Direct access to preferences in the past has caused many problems. Multiple extensions would try to change them and conflict, and the lack of security limitations meant malicious extensions could take advantage of users. Instead, WebExtensions focus on higher-level APIs that implement specific tasks.

Can you kindly provide any resources I am missing?

@anaclumos Sorry, but I am sure this used to be the case. uBlock Origin used to be able to set prefs.

Working on it!

Released v1.0.1. Please take a look!


python3Packages.python-http-client: 3.3.5 -> 3.3.6

Motivation for this change
https://github.com/sendgrid/python-http-client/blob/main/CHANGELOG.md#2022-02-09-version-336
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 159197 run on x86_64-linux 1

4 packages built:

python310Packages.python-http-client
python310Packages.sendgrid
python39Packages.python-http-client
python39Packages.sendgrid


fixed issue #270

[x] done reducing speed of element
[x] visible and readable
[x] fixed issue
[x] improved

please merge pr under gssoc label


Parititioned step additional attributes get dropped if SWF throttles activity creation

There is a bug that happens when the following conditions are true:
a) The step is partitioned
b) The @PartitionIdGenerator method returns a PartitionIdGeneratorResult object that contains at least one additional attribute.
c) SWF fails scheduling one or more of the partitions (i.e. scheduled activity task rate exceed)
In this case, the additional attributes in the original PartitionIdGeneratorResult are lost for any partition attempt that was throttled. I haven't checked but it may also drop the attributes from earlier steps.
I've found comments in the code indicating that I had previously known this edge case existed, except it didn't matter because there was previously no way to add additional attributes from the partition id generator. This changed when I added PartitionIdGeneratorResult.
I'm working to confirm whether SWF handles the list of decisions from RespondDecisionTaskCompleted atomically; I suspect they don't. On that assumption, we'll need a solution that doesn't assume the first attempt of a partitioned step will always schedule all partitions together.

After some discussion with @joeymarylander, we think we do need to go with that last "split the content across multiple markers" solution, for two main reasons.
First, creating a thousand markers feels wrong, and results in a lot of redundant data being stored in the workflow history, and potentially uses up a large chunk of the 25000 events-per-workflow maximum limit.
Second, splitting the data across multiple markers will not be necessary most of the time. 100 partitions each with 100-character partition IDs uses 10k total. Most of the use cases I'm aware of use either a small number of partitions (<10), or a very large number of partitions but with a very short partition id (e.g. 1000 partitions with a two-character prefix as the partition id).
We also considered compressing the list of partition IDs, but I'm not sure the extra complexity is worth the space savings. (A list of random alphanumeric strings compresses by about 25% with gzip.)
So the solution will look like this:
When the next step to be scheduled is a partitioned step, if there is not already a partition id generator result marker, we run the partition id generator, and put its output in a marker event. We respond to the decision task with that marker along with a decision indicating we want to send a "do another decision" signal to the workflow. (This is necessary because adding a marker event does not trigger a new decision by itself.)
If instead there is already a partition id generator result marker, we make a list of partitions that have not been successfully scheduled at least once. For each of those, we generate ScheduleActivityTask decisions, using the data from the marker as the source of partition IDs and additional attributes. For all other partitions, we follow the normal retry logic.
Additionally, we should change the existing logic for how to handle the "schedule activity task failed" state for a partition; instead of extracting the partition ID from the most recent attempt and retrying without input attributes, we determine the input (both the partition ID and the other attributes) based on the most recent successfully-executed attempt of the partition. Combined with the above logic for scheduling the first attempt of a partition, this should cover all of the cases where scheduling an activity execution has failed.

We also discussed backward compatibility; specifically, what happens if an application encounters this issue while also deploying an update to Flux that includes this bugfix.
Currently, a workflow in this bad state needs to be terminated and restarted. While it would be ideal if deploying this fix could automatically resolve the issue in all cases, we do not believe we can safely assume that the partition id generation logic can be re-run unless none of the partitions were successfully scheduled. As such, this fix will include the following logic:

If the marker is missing but there is at least one successful scheduling attempt for every partition, proceed without the marker, using the first attempt of each partition as the source of truth. (This is the same as the logic called out in the "Additionally" section above.)
If the marker is missing but one or more partitions only has failed scheduling attempts (that is, there has never been a successfully-scheduled first attempt), record a marker indicating that the workflow is broken and needs to be restarted, then avoid making more decisions for the workflow.
If the marker is missing, and there are failed scheduling attempts for one or more partitions, but no successful scheduling attempts for any partitions, create a new partition id generator result marker and follow the normal process from there.

This minimizes the impacted users to only those who are affected by this bug during the deployment of this fix.

well said.

I merged the main fix, now I just need to add the marker splitting logic for when the partition ID list is too big. My thought is to split the partition id list itself into chunks, with each marker containing a subset of the partition ids, such that each marker contains valid JSON on its own. I'd also add an extra field to the json indicating how many markers there are for validation purposes.
When reading the markers back from the history, I'd merge together the partition id lists from each of the markers. The additional attributes map would only be included in the first marker.

This is fixed, and will be included in the next release.


Create a global error handling middleware

I noticed there isn't a central place for handling or sending errors that happens in the controller, I can create a global error handling controller that sends different error messages based on if the app is running in development mode or production mode

@vishalverma9572 Can I go ahead and implement this?

@ugz-man . Yes go ahead!


[BUG] ARIMA handles missing data but tag states otherwise

The tag in ARIMA model indicates that it does not handle missing data ('handles-missing-data': False), but it is able to produce forecasts. Should the tag be changed?
from sktime.datasets import load_airline
y = load_airline()

y_missing = y.copy()
y_missing[2] = np.nan # Just 1 missing value

from sktime.forecasting.arima import ARIMA
forecaster = ARIMA(
    order=(1, 1, 0),
    seasonal_order=(0, 1, 0, 12),
    suppress_warnings=True)
print(forecaster.get_tags())
forecaster.fit(y_missing)
y_pred = forecaster.predict(fh=[1,2,3])
y_pred

{'scitype:y': 'univariate', 'ignores-exogeneous-X': False, 'capability:pred_int': True, 'handles-missing-data': False, 'y_inner_mtype': 'pd.Series', 'X_inner_mtype': 'pd.DataFrame', 'requires-fh-in-fit': False, 'X-y-must-have-same-index': True, 'enforce_index_type': None}
1961-01    444.541344
1961-02    418.603889
1961-03    446.815167
Freq: M, dtype: float64

Hm - may be an oversight.
I just wanted to test this systematically, but found that there is no test case with nans in it.
I added one here https://github.com/alan-turing-institute/sktime/pull/2207 to check this tag, in general.

Thanks @fkiraly . Will you also fix the tag for this model?

Will this fix go into the 0.11.0 release?

Probably not - a lot of other estimators are breaking with the nan testing scenario, and I haven´t fully understood whether the problem is with the testing scenario or with the tags...
https://github.com/alan-turing-institute/sktime/pull/2207


[#299] improvement: Make config type of RSS_STORAGE_TYPE as enum

Hi @zuston  @jerqi @xianjingfeng
Any comments and suggestions would be appreciated if you are available, thank you.
What changes were proposed in this pull request?
improvement: Make config type of RSS_STORAGE_TYPE in RssBaseConf as enum
Why are the changes needed?
Fix: #299
Does this PR introduce any user-facing change?
No.
How was this patch tested?
current UT and integration testing

Hi @zuston  @jerqi  @xianjingfeng
I'd like to learn more about your thought on this PR if you are available and any comments and suggestions would be appreciated.
I'm sorry for any inconvenience that I may have caused.

Master CI failed. I revert this pr. Could you rebase the latest master and raise a new pr?

Hi @jerqi
Thanks for the notification. I will submit the PR again based on latest master branch. BTW, do we have any ideas that why the Master CI failed?

You can see https://github.com/apache/incubator-uniffle/actions/runs/5780765916/


Update README.md

Added a note about Project resource name to be unique and also to check if project was deleted recently.

Hi @KPRepos, can you sign the CLA?


More Maths!

Finish up all of the maths classes, and add some more specialized stuff!

There are probably a million bugs, but this is done?


Muting someone for negative time causes bad bug

E.g. =mute @Kyra -1s buggy code
Skyra replies with an error, the person is muted, but nothing is logged, so not sure if it's an actual mute or what, but yea

Fixed in 403dc1f, will close once the moderation rework lands.

I'm not sure the cause here, but probably a good idea to check every other command handles negative numbers okay as well. Perhaps the Arg/usage could fix it

You're right, I wasn't taking negative durations in the timespan argument. Fixed in 6dff856, which has been cherrypicked to production and deployed.


[Feature][UI] Add crontab management page in Project level.

Search before asking

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

Description
Now if we want to check and manage cron task, we need to click the workflow defintion one by one.
But if there are huge workflow in one project, and user want to know how many cron task will be will difficult.

Could we add a cron manage page below Task Instance menu? Which can manage all cron task in same project.
Use case
User all cron task in same project.
Related issues
N/A
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

Add a cron manage page in the security center?

Add a cron manage page in the security center?

I suggest add it in the Project Management, just below Workflow Definition

How about add a  configuration menu  under the first level menu?

How about add a configuration menu under the first level menu?

That's great. But I think this is another improvement. Because i think Cluster, Worker Group, Environment should not belong to Security. These should belong to Confihration Center.
But cron tasks should same as task and workflow, same belong to a special project. WDYT


update packages

:white_check_mark: Build TheIdServer 7.4.7-fix-dependencies1-0181 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/19dd01351f by @invalid-email-address)


Where to disable pokestops

Does anyone know where to locate the json file to stop it from searching pokestops?

I don't know how to stop it via editing json file
but you can disable it via config

add '----no-pokestops', as a line/option under var cmdLine = [ in main.js

Couldnt figure out the main.js
How do you disable via config?

main.js is the only config on mchristopher wrapper. just need to change
 var cmdLine = [       './run_map.py',       ....
to
 var cmdLine = [       './run_map.py',       '--no-pokestops', ....

works great todd! also added in '--no-gyms' to make it even less data going to the database.


Fix CI APKs Upload

Is there any context for this? Maybe mention the issue you're fixing or add a description

Closing due to likely unneeded now


Following PyCon2016 tutorial

Coverage increased (+2.3%) to 39.08% when pulling ece72481459e90298e5c5d9b34b2cca51c30d096 on ETLJ:tutorial_wip into d5fd52c818b07dcac4abe7eb852a216c80b6fde2 on keeppythonweird:master.


Use no hash oracle attestation

Update the signature scheme to use @llfourn proposal
Also removed the requirement for NFC standardization of UTF8 as it does not seem strictly necessary since we are not hashing strings anymore. If anybody can think of a reason that we should keep it please comment.

Also removed the requirement for NFC standardization of UTF8 as it does not seem strictly necessary since we are not hashing strings anymore. If anybody can think of a reason that we should keep it please comment.

This still is needed for things like the eventid and for enum outcomes. We hash the entire event_tlv when signing the announcement so these need to be standardized.

This still is needed for things like the eventid and for enum outcomes. We hash the entire event_tlv when signing the announcement so these need to be standardized.

Good point. Though thinking about it a bit more, I'm actually not sure why we are using canonical encoding in the first place. Looking at it more closely, it seems that it is useful when trying to compare or search strings, which is not what we are doing. The only reason we would need it is if the codes would somehow be automatically changed based on implementations if they were not canonical, but AFAICT it is not the case.
So can someone give a good reason for using it in the first place? Then at least I could add it as a rational to the document.

So can someone give a good reason for using it in the first place? Then at least I could add it as a rational to the document.

Imo there should at least be one standard so people know how to correctly interpret these bytes to display to the user.

Imo there should at least be one standard so people know how to correctly interpret these bytes to display to the user.

So that's the job of utf8. From my understanding, what NFC or NFD provide is a guarantee that two strings that "display" the same will have the same encoding, and it seems to be mainly useful for comparing or searching strings. But for our context I can't really figure out what is the benefit.

Also removed the requirement for NFC standardization of UTF8 as it does not seem strictly necessary since we are not hashing strings anymore. If anybody can think of a reason that we should keep it please comment.

This still is needed for things like the eventid and for enum outcomes. We hash the entire event_tlv when signing the announcement so these need to be standardized.

Why does this mean it needs to be standardized in the case of event ids and enum outcomes?

Imo there should at least be one standard so people know how to correctly interpret these bytes to display to the user.

They are just strings so why can't they be displayed to the user normalized or not?


chore(gcp): remove unnecessary default project id

Description
Remove unnecessary GCP default project id.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

No backport needed since this is done in this PR https://github.com/prowler-cloud/prowler/pull/3587


Removes mountds in favour of mounts

Description
This PR removes mountds in favor of mounts which is an enhancement, since it checks not only for /var/run/docker.sock, but also other sensitive paths that are mounted, much like in Falco.
For more context, see https://github.com/Shopify/kubeaudit/pull/322
After this is merged, we can then release a new version of kubeaudit.
Fixes #328
Type of change

[ ] Bug fix :bug:
[x] New feature :sparkles:
[ ] This change requires a documentation update :book:
[ ] Breaking changes :warning:

How Has This Been Tested?

[x] unit tests

Checklist:

[x] I have :tophat: my changes (A 🎩 specifically includes pulling down changes, setting them up, and manually testing the changed features and potential side effects to make sure nothing is broken)
[ ] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] The test coverage did not decrease
[x] I have signed the appropriate Contributor License Agreement

Oh, interesting point. I thought we just wanted to remove the command. But the idea of sending a warning first about the deprecation is definitely more subtle/considerate for the users. Thanks! 🙏🏽


Concern regarding the unused import diagnostic message

Description:
Need to revisit the error message being displayed when there's no usages of an module import. We might need to revisit showing this as an error since the Ballerina spec doesn't emphasize such a thing.

Affected Versions:
2.0.0-alpha1

The "Import declaration" section of the spec says

It is an error for a source-part to import a module using a module-prefix and then not to use that module-prefix.

Related spec discussion - https://github.com/ballerina-platform/ballerina-spec/issues/241#issuecomment-505237301

For the shell as well, this check is very problematic. Bacause in the shell following is a valid session,
=$ import ballerina/io
=$ int v = 100
=$ io:println(v)

We have to selectively include imports to stop errors that can come from situations like this. This currently is an added complexity. If there is a flag on the compiler to toggle whether it gives an errors on imports or not, all those can be simplified.

Closing this issue since the current behaviour is in-line with the current spec. However there is a spec issue to track the possibility of making this a warning instead, please see https://github.com/ballerina-platform/ballerina-spec/issues/738.
@kdsuneraavinash, let's create a separate issue for the shell requirement since this is a common requirement for certain other errors too (e.g., unused variable with inferred type including error).


feat: copy to clipboard code snippet

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/scullyio/scully/blob/main/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Other... Please describe:

What is the current behavior?
Copy to clipboard button is not available for code snippets.
Issue Number: N/A
What is the new behavior?
Copy to clipboard feature is added for the code snippet. This feature is included in markdown plugin.

To use this feature follow the below steps :

The way we have enableSyntaxHighlighting: true flag for highlighting code, another flag is added enableCopyToClipboard, the default value of this flag is false.
If you want to enable copy to clipboard feature, set plugin config as below
setPluginConfig('md', { enableSyntaxHighlighting: true, enableCopyToClipboard: true });

When enableCopyToClipboard is true, it will add Copy button, it's script and style while transforming markdown to html.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@SanderElias, while implementing this PR, I have also found one issue,
pre with position: relative will not work properly, currently in our code snippets when we do horizontal scroll, language heading move with it. generally, it should not move.
Also when I added a copy button on the right-top corner with an absolute position. it was also moving on the horizontal scroll.
So to fix such issue I have added one parent div.scully-code-snippet with position relative.
So it fixes both the issue. This behavior is inspired by the gatsby docs.
Please confirm if it is correct or not.  If it is correct then I will update the test case snapshot in sample-blog app where it is getting failed now. If you have any suggestion and want me to update anything please let me know.

Hi @SanderElias, I have created a separate plugin and committed the code. please review it.


Bug report: malformed URL returned

[x] I've verified and I assure that I'm running youtube-dl 2016.08.13
[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

Version
youtube-dl -v
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.08.13
[debug] Python version 2.7.10 - Darwin-15.6.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
Usage: youtube-dl [OPTIONS] URL [URL...]
This affects at least 2016.08.13 (brew install --HEAD youtube-dl) & 2016.08.10 (brew install youtube-dl).
Bug Report
The output of youtube-dl -g http://vidto.me/3u9q0f3awai7.html is

http://<IP_ADDRESS>/gjjhpi5jhyqwws4phx5dun6hwxoawrinoy5pt7drztqqo7rccmfwyuvtyjna/video.mp4"},{label:"360p

The correct URL is obviously

http://<IP_ADDRESS>/gjjhpi5jhyqwws4phx5dun6hwxoawrinoy5pt7drztqqo7rccmfwyuvtyjna/video.mp4

Note
I am aware of #7032, but I am also aware that VidTo is XFileShare based and actually supported.

This movie is a copyrighted product of Village Roadshow Pictures (Wikipedia). Do you have another example?

Do not worry and sorry for the hassle, I'll look into it.


Wrong Content-Type when POST with FormData + File

At the moment the Content-Type header defaults to application/json
When a user submits a FormData, the Content-Type header should not be manually added.
When using a FormData* as body the browser will pick the right Content-Type header
When the form does not contain any File/Blob the header is set to application/x-www-form-urlencoded
When the form contains at least one File/Blob the header is set to multipart/form-data with the correct form boundary
* - this is not the case only for FormData, user can have different types as body
body?: null | ReadableStream | Blob | BufferSource | FormData | URLSearchParams | string

I suppose that Content-Type as application/json should be used only when body is string or missing, for other types usually the browser will set the correct header (FormData for sure, for other types need to be checked).
This is my temporary workaround with patch-package (does not cover all cases)
patches/make-service+2.1.2.patch
diff --git a/node_modules/make-service/dist/index.mjs b/node_modules/make-service/dist/index.mjs
index 486302c..87efd56 100644
--- a/node_modules/make-service/dist/index.mjs
+++ b/node_modules/make-service/dist/index.mjs
@@ -96,10 +96,9 @@ function typedResponse(response, options) {
 async function enhancedFetch(url, requestInit) {
   var _a, _b;
   const { query, trace, ...reqInit } = requestInit != null ? requestInit : {};
+  const tmpHeaders = reqInit.body instanceof FormData ? {} : { "content-type": "application/json" };
   const headers = mergeHeaders(
-    {
-      "content-type": "application/json"
-    },
+    tmpHeaders,
     (_a = reqInit.headers) != null ? _a : {}
   );
   const withParams = replaceURLParams(url, (_b = reqInit.params) != null ? _b : {});

Hi @iamandrewluca , thanks for reporting it!
I'm kind of regretting to add that default at this point, but to avoid a breaking change your solution seems to be good.
Do you feel like making a PR for it?
https://github.com/gustavoguichard/make-service/blob/main/src/api.ts#L78
You are more than welcome to do so and to add a test case, otherwise I'll be doing it, but probably after all the holidays and few more days to catch up on other work load.
LMK
Cheers

PS: @iamandrewluca , I'd probably add that default instead of removing it, and for that we need to call ensureBodyString before that line:
const body = ensureStringBody(reqInit.body)
const tmpHeaders = body === null || typeof body === 'string' ? { "content-type": "application/json" } : {};

Hey @gustavoguichard I can do a PR, will look into it at the end of this week, or maybe after new year.


Font Awesome Issue <The 'Font Awesome' library has been updated to v6>

Description

Screenshots
No response
Do you want to work on this issue?
None
Additional information
No response

I don't understand the bug?

I don't understand this issue, so I will close


make some BuildContext methods generics

Description
Several methods in BuildContext were using Type to search for ancestor.

inheritFromWidgetOfExactType
ancestorInheritedElementForWidgetOfExactType
ancestorWidgetOfExactType
ancestorStateOfType
rootAncestorStateOfType
ancestorRenderObjectOfType

Most of those methods implied a cast at call site because their return type was a parent type. Moreover the type provided was not checked at analysis time even if the type is actually constrainted.
Making those methods generics improves type safety and need less code.
// before
ComplexLayoutState state = context.ancestorStateOfType(const TypeMatcher<ComplexLayoutState>()) as ComplexLayoutState;
// after
ComplexLayoutState state = context.ancestorStateOfType<ComplexLayoutState>();

Related Issues
None
Tests
None because it's a refactoring.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[x] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[ ] No, this is not a breaking change.

I really like this clean-up. However, this looks like a rather big breaking change that will also break many users of flutter (see current cirrus failures as an example). I wonder if we can somehow do this change with a softer transition where we deprecate the existing API, but it continuous to work until our dependencies had a chance to upgrade to the new API.

I really like this clean-up and the extra type safety it gives us.

Me too :)

this looks like a rather big breaking change that will also break many users of flutter

Yes :( but the upcoming NNBD will be way more breaking.

see current cirrus failures as an example

I planned to update scoped_model but I was wondering how to deal with that (flutter repo depends on scoped_model and scoped_model depends on flutter - perhaps make a git ref dependency on a fork of scoped_model until a new flutter version is out)

I wonder if we can somehow do this change with a softer transition where we deprecate the existing API, but it continuous to work until our dependencies had a chance to upgrade to the new API.

I thought about it and I didn't see a good solution:

make Type parameter optional could break overrides and is not possible with inheritFromWidgetOfExactType that already have an optional named parameter.
duplicate methods needs to have new method names (the current method names are good IMO) and deprecates old methods

I don't really know how often those methods are used outside of flutter but if someone has access to a corpus of code on pub it could be really interesting to grab some datas on the usage of those methods.
WDYT?

It's now green with a patched version of scoped_model.

Can we make this less breaking by deprecating these versions and instead adding new methods with different (more uniform?) names that use the new style?
e.g. we could add "find" to those that are O(N), to make it clearer that they're more expensive.
I'm not sure exactly what to do with the O(1) ones...

Old
New

inheritFromWidgetOfExactType
?

ancestorInheritedElementForWidgetOfExactType
?

ancestorWidgetOfExactType
findAncestorWidgetOfExactType

ancestorStateOfType
findAncestorStateOfType

rootAncestorStateOfType
findRootAncestorStateOfType

ancestorRenderObjectOfType
findAncestorRenderObjectOfType

I like the suggestion regarding the "find".
Here are my suggestions for the other two. I am hoping that "depend" makes it more clearer than "inherit" that you're adding a dependency on the InheritedWidget and get rebuild whenever it changes. The other method's name is just adopted to that naming scheme.
inheritFromWidgetOfExactType  -> dependOnInheritedWidgetOfExactType
ancestorInheritedElementForWidgetOfExactType  -> ancestorElementForInheritedWidgetOfExactType

find* looks good to me.
Let me know what the other 2 methods should become.

@goderbauer's proposals LGTM.

I believe you may have to pull in the latest master to turn the tests green.

This looks good modulo the breaking change announcement.

I've sent an email but I don't see it appear on https://groups.google.com/forum/#!forum/flutter-announce .

The name "dependOn*" feels weird IMO (although it does match with the vocabulary of InheritedWidgets).
Some suggestions:

bindTo*
listenTo*
get*
addDependencyOn*
linkWith
subscribeTo

@rrousselGit thanks for your suggestions. I'll let @Hixie and @goderbauer comment on them (all the prefixes looks good to me except get*)

@a14n Looks like the announcement is showing up here now: https://groups.google.com/forum/#!topic/flutter-announce/RS82mg9iK24

(PR triage): @a14n Is this one good to go?

Is this one good to go?

Yes. I'm only waiting for a green tree.


ng is not recognized as an internal or external command

I installed angular-cli via command prompt. And then  I write ng new my-first-app, it doesn't work:  'ng' is not recognized as an internal or external command, operable program or batch file. How can I fix it?

Did you install it globally?
CHeck out the wiki here: https://github.com/angular/angular-cli/wiki#getting-started

Yeap. I found solution. Comman Prompt should be runned as adminstrator. After that it recognized ng.

It does not require administrative rights, so there might have been something with your install (e.g. did you install CLI using administrative prompt?).
Closing this in any case as solved. Thanks!

Please try to use Node.js command prompt in your windows. It will work.


Current documentation doesn't mention the default port used by dat

Default port is 3282

Documented, thanks!


Is there any "dark mode" for the frame?

Like many apps now, dark mode is essentially everywhere. Is there any way to implement a forced dark mode for websites through your HTMLFrame widget in any way?
PS: I saw your HTMLFrame documentation too, no mentions about themes at all, so I ask this question.
And also, good initiative too! In spite of this being a "lightweight" web viewer, I am actually trying to create a full blown browser in python with this! Keep going with this bro :)

Hi!
It is possible to use add_css to manually set custom CSS into the frame after the site loads in order to modify the site or change the theme. However, it sounds like you are looking for a built-in option to automatically translate all document colours to a dark theme.
TkinterWeb does not have this functionality. Honestly, it's a great idea but I never thought to implement it. I'll see what I can do!

Any possible updates on this issue @Andereoo?

Hi!
Some updates...
I've added a basic dark theme. You can toggle it via yourhtmlframe.enable_dark_theme(True, True) .

The first True will allow the dark theme for the document. When enabled, a regular expression will scan stylesheets prior to loading and detect colours. Any light background colours and dark foreground colours will then be inverted, making a 'dark mode' effect.
The second True will cause images to also be inverted.

This is pretty preliminary and causes some websites to hang, but it seems to work decently. I'll look into some future improvements, and feedback is certainly welcome. Once I can solve the compatibility issues some other users are pointing out, I'll look into a way to manipulate colours without directly scanning stylesheets, which has some performance impacts.
Try updating TkinterWeb and let me know what you think!

Yeah It's great! Working good for me
Here are the results from my web browser (like MY webbrowser)

As you can see, it does make the images look abominal, but I will change the second bool to false to fix this, not a hard thing to do, You can improve it more though, good try bro.

A followup on the previous comment: I tried some more websites other than google. like normal links, and some of them take so long to respond or outright crash out. this IS an issue still. good try again.

Hello bro, an update on this method, this does crash on some websites and consumes a lot of memory.

I hope you have time to fix this issue then.
Still great try though.


Arbitary paths on secondary redirect domains

today we have two fields:

Site Url is a domain, and gotrue will allow redirects on any path that is on that primary domain
Additional Urls are exact Urls (including path, query param etc.) that do not have to be on the primary domain. The primary use case for these was mobile deep links that look like: com.mydomain.sub://customscheme, hence why they have to be exact, because they are difficult to verify securely
Now it appears that a new use case has developed for these Additional URLs: multiple environments
people may wish to use the same backend for multiple environments and therefore require arbitrary paths on a secondary domain
options here seem to be:

figure out a way to securely parse Additional URLs - supporting reverse URLs with custom schemes
introduce "Additional Site URLs" that are restricted to standard  scheme://sub.domain.com
make use of gotrue's multi-tenancy (you can dynamically load configs in and out, but thus far we haven't dug into this capability)
other?

Another use case for this is requiring a user to login to perform a certain action on a specific page.
For example, if you had a blog with a comment section, reading a post would not require logging in but commenting would. If the user goes to comment, you would prompt them to login. If they login with an email link, you would want it to redirect to that same blog post page instead of to the main page. Redirecting to a specific blog post would require having a dynamic segment in the path.
Also, this behavior should work on both the Site URL and the Additional Redirect URLs.

Wondering if this would resolve the use-case of preview environments such as Netlify and Vercel expose in Pull Requests? These all have a similar base domain with a dynamic sub-domain. Something like *.vercel.app wildcard support would be very helpful as we can't figure out the exact URL until build time.

FWIW, for the preview environment use case, you can create branch based
subdomains and add those to supabase. It's not quite as flexible as
supporting every build domain but it's pretty close.

Another use case for this is requiring a user to login to perform a certain action on a specific page.

For anyone else trying to do this, I got around the current limitation by adding a query string ?redirect=/path/after/login to the redirectTo parameter and handled the redirect in my app.

Did something about the handling of these URLs change in the past 2 weeks? It looks like query strings are now being stripped from the URLs.

Hey,
Think might be mostly resolved by #334 . Or, at least the use case  for something *.vercel.app
Feel free to re-open if there are still pressing use cases that you'd need.
Thanks!


#23 - added year to the conference title

Issue title -
Set the title to [CONFERENCE]  and the Year

Great work on this! I'll get it added right away!


⚠ Bofrost.de has degraded performance

In 88d4f82, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1466 ms

Resolved: Bofrost.de performance has improved in 9661fe1 after 1 hour, 25 minutes.


Jeff Schaller: Watch nlighton.com

Jeff Schaller requests the watch of the watch_keyword nlighton\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

nlighton\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Rename profile page to details page

Details
Currently in E.cash there are two profile pages: The page you get when you click on the chat header avatar of a chat you have with someone, and the page you get when navigating to Settings > Profile.
The non-settings profile page displays a header of Details while the settings profile page displays Profile.
There's no reason for these pages to be named the same thing, and from the description above you can see how much more difficult to describe which page is which.
Fixed Issues
Fixes N/A, was brought up in conversation and is an easy fix.
Tests

Log into E.cash
Create a chat with one person
Click on their chat header avatar and confirm you can see the Details page for that user.

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots
Web

Mobile Web

Desktop

iOS

Android

Updated and resolved conflicts


A bug in PneumoniaMNIST loading

In line 298 and line 299 of data.py, train data are used for testing.

Thank you for your reminder! fixed.


Setup Kanban Board

Setup Kanban Board
Link to project
There are three members on the team.

Hi @piero-vic, @eapenzacharias, and @lu-jim,
Status: Approved ✔
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Fix #1070, patch PSP include directory reference

Describe the contribution
The PSP header files are located in fsw/shared/inc, not fsw/shared.
This corrects the reference.
Fixes #1070
Testing performed
Modify local config to use "eeprom_stub" PSP module to implement eeprom functions, which reproduces the build failure - I confirmed the error with respect to #include "cfe_psp.h"
With this patch applied, the build succeeds again.
Expected behavior changes
None
System(s) tested on
Ubuntu 20.04
Additional context
This PR is based on Bootes RC2 as the bug exists there, recommend to patch it in prior to final release.
Should also merge this forward to main as the bug exists there too and this is the easiest short term fix.
Longer term fix should be #626 to prevent this type of issue from recurring.
Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

CCB:2021-01-13

CCB:2021-01-13

@astrogeco Is there something preventing this one from merge?

@astrogeco Is there something preventing this one from merge?

@astrogeco Is there something preventing this one from merge?

Just time to sit down and update the Bootes bundle and tag stuff. I guess I should merge it and deal with that later

@astrogeco Is there something preventing this one from merge?

Just time to sit down and update the Bootes bundle and tag stuff. I guess I should merge it and deal with that later

@astrogeco Is there something preventing this one from merge?

Just time to sit down and update the Bootes bundle and tag stuff. I guess I should merge it and deal with that later

Getting it into main is the higher priority on my side, it's broken in main which is being evaluated by numerous stakeholders.

@astrogeco Is there something preventing this one from merge?

Just time to sit down and update the Bootes bundle and tag stuff. I guess I should merge it and deal with that later

Getting it into main is the higher priority on my side, it's broken in main which is being evaluated by numerous stakeholders.


examples: fix crash after resize

Changing target (resizing) should enforce canvas update.

https://github.com/thorvg/thorvg/pull/2485/commits/70711311c43e82fc0f9ecf589c5050cd954dac94


Possibility to change the visibility of headers in case of a framework

Add the possibility to specify the visibility of the header in case of a framework target.
You can use the headers property for that:
name: TestProj
targets:
  MyTarget:
    type: framework
    platform: iOS
    sources:
      - path: some_path
    headers:
      public:
        - generated-src/objc/*.h
      private:
        - somefile.hpp

If a non framework target uses this property, a invalidHeaderMapForTarget error is thrown during the validation pass.
If one of the provided files does not exist, an invalidHeaderPathForTarget error is thrown during the validation pass.
Some basics tests have been added for the parsing.
The default behaviour for headers has changed: all headers will be considerated as Project by default, unless headers tells something else.

Is there a reason to have another section for headers vs an attribute in sources? We already have support for compilation flags, etc that are applied on a subset of files in sources which could be leveraged here.
I think we could make this change by adding a "visibility" option (public, private) to sources. The default option value would be public.

I wanted to be as closed as possible to Xcode. Visually, you change it inside the "Build Phases" by choosing which header is either"Project", "Public" or "Private". I wanted to be closed to this.

Currently sources represent a lot of things that aren't in the Build Sources section of build phases. It can be a bit ambiguous but if we're going down this route we should probably separate other things like resources to be consistent.
The current schema seems friendly for users at the expense of not matching Xcode explicitly.
@yonaskolb - thoughts here?

Hi guys. Sorry I haven't had time to look at this.
Yes I agree with @rahul-malik, in that keeping everything in our TargetSources is the best. It could even be a simple headerVisibility enum that defaults to public.
@yageek I can see the advantage of the current way you've implemented it though in that you can seperate the types via glob patterns, and are not limited to a single visibility type per source declaration. To achieve something similar, the path itself could handle glob patterns (quite a bit of work), or the whole headers structure could be moved down into TargetSources and the patterns be relative to the path. The later is probably the best approach for now. Thoughts?

Do you mean having something like this?:
name: TestProj
targets:
  MyTarget:
    type: framework
    platform: iOS
    sources:
      headers:
        public:
          - generated-src/objc/*.h
        private:
          - somefile.hpp
      - path: some_path

Yeah. What do you think?

From the user points of view, I think it is equivalent to the previous implementation :)
By relative to the path,  Are you still speaking about the path of the project.yaml?
Regarding the default visibility to public, I guess teh answer depends on the habbits/type of projects: In general, I have less public headers than "project" or "private" headers. This means, in my case, I would have to write more rules to hide elements than rules to make elements public.
I guess some people encounter the opposite case 🤔
In case we stay with a default visibility to "public", I would suggest to add also the "project" type inside the enum to give the possibility to the user to fully configured his project.

@yageek I've had a think about this.
I think at the moment it would be best to just have a single headerVisibility: HeaderVisibility property on TargetSource which defaults to .public.
As @rahul-malik points out all our source options are currently within a single controlled place with options for the different types. Maybe in the future we could break this out into a sourceFiles, headers, resources, (any maybe infoPlist) which have dedicated options, but that would be a larger piece of breaking work and would come later. For now we should adapt to the structure that is already there.
This means you would create a seperate source entry for each header visibility type, but with excludes and #152 (which I want to add in now) it should give you the same control.
sources:
   - path: sources/obj
      headerVisibility: private

In terms of the default, no matter the structure, I think it has to be public. The aim is for the spec to be as simple as possible for simple cases. That means if you don't touch anything to do with headers, things should "just work" and things will compile (unless you import multiple headers with the same name). It also avoids breaking many current projects.
Let me know if you'd like to work on this. If so, I would say leave this PR here and perhaps create a new one.

@yageek I've made an alternative PR #252. Let me know what you think there. Can something that simple in addition to the exclude feature meet your needs?

I would say that this is a step to the right direction :) It will be possible to configure the different headers as private or public in my case.

Having worked on this now and seen it in action, I do also like the approach you've taken here


KSQL image using Confluent deb packages

https://docs.confluent.io/current/installation/available_packages.html#confluent-ksql
https://docs.confluent.io/current/installation/installing_cp.html#debian-and-ubuntu

Built solsson/kafka-ksql:v4.1@sha256:a6f7d046c330054d86b2c14df3c24da9af2841dbc1f1c132576e5abe7f4fade7. The image has no WORKDIR or ENTRYPOINT. Such things will have to be in the kubernetes manifests for now.

https://www.confluent.io/blog/introducing-confluent-platform-preview-releases/ says "We encourage developers to build applications against the API shipped in this preview because it’s closer to the future API, which we plan on keeping stable." so I've built solsson/kafka-ksql:v5.0@sha256:e03ece8cb149569430b28406345b68fda359ae25f2b893c39aa5b740974db348


New subscription -> Group (Interests, Sex)

Hello,
In my ML I have two groups Interests-> Cars, Bikes, Boats and Sex-> Male,Female
How do I make a call to subscribe to 1or more interests ?? and only 1 Sex.
Sample:
$result = $MailChimp->post('lists/'.$listID.'/members', array(
'email_address'     => $email,
'status'            => 'pending',
'merge_fields'      => array(
'USERID' => $user_id,
'FNAME'=> $first,
'LNAME'=> $last,
'EMAIL' => $email,
'BDAY' => $bday,
'SEX' => $sex
), // merge_fields array end
'interests'         => array( 'Cars' => true, 'Bikes' => true, 'Boats' => false ), // interests is name of group
'sex'               => array('male' => true, 'female' => false) // sex is name of group
));

Rather than using the name like 'Cars', you need to get the ID of that interest and use that instead.

I have something similar issue. This is my data being submitted to API at
post('lists/my-list-id/members',$postData);
This is my post data
Array
(
    [email_type] => html
    [email_address] =><EMAIL_ADDRESS>    [status] => subscribed
    [merge_fields] => Array
        (
            [FNAME] => test
            [LNAME] => test
        )

    [interests] => Array
        (
            [0] => "5130692954"=>true,"84c9981***"=>true,"d02d767***"=>true,"f05d368***"=>true,"474db4e***"=>true,"e9945af***"=>true,"605a592***"=>true
        )

)

But I get this error
Array
(
    [type] => http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/
    [title] => Invalid Resource
    [status] => 400
    [detail] => The resource submitted could not be validated. For field-specific details, see the 'errors' array.
    [instance] =>
    [errors] => Array
        (
            [0] => Array
                (
                    [field] => interests
                    [message] => Schema describes object, array found instead
                )

        )
)

Can you help me solving this issue?


meta: ensure galaxy_info.author field is a valid github username

As v1 roles (standalone) used the author field as a github username and all documentation examples uses it as a username, we require it to match their requirements.
We also document the fact that galaxy_info field is not needed for roles inside collections and that it can be removed.
Reasoning
While Galaxy metadata official page does not mention any limitations for the author field, we can see on multiple examples from https://docs.ansible.com/ansible/latest/galaxy/user_guide.html#finding-roles-on-galaxy that this is expected to be the github username. That is also in sync with behavior of other tools like ansible-lint and navigator which would use this field to build the fully qualified role name, as old standalone (v1) roles do not have a specific field for namespace.
Shortly, to avoid problems, just use a github compatible username or don't use the field at all.

We also document the fact that galaxy_info field is not needed for roles inside collections and that it can be removed.

A not too long time ago it was impossible to upload collections to Galaxy which contained roles without galaxy_info. Does this mean that this restriction has finally been removed? (Would be great news!)

We also document the fact that galaxy_info field is not needed for roles inside collections and that it can be removed.

A not too long time ago it was impossible to upload collections to Galaxy which contained roles without galaxy_info. Does this mean that this restriction has finally been removed? (Would be great news!)

Hmm... time to check manually. I know that the info is not really loaded or exposed to the user but not sure if upload is allowed or not. The more people I ask the more confusing it gets and the docs do not help at all.

I updated the change and mentioned that author field itself is not needed for roles inside collections.


HDDS-10751. Detect missing EC padding blocks

What changes were proposed in this pull request?
Create a CLI tool to find EC keys whose blocks are missing from some of the replicas due to having been reconstructed before HDDS-10681 was fixed.
The tool prints keys affected in a tab-separated list, showing key name, size, replication.  This information can be used to recreate the keys (if enough replicas are still available) using existing tools (ozone sh key get/put).
https://issues.apache.org/jira/browse/HDDS-10751
How was this patch tested?
Configured Ozone's restart Docker Compose environment with some additional datanodes.  Set 8MB block size, so EC 3-2 would use 1 block on each datanode hosting the EC container for each 24MB of total key size.
Created a set of EC keys spread out in 4 containers:

container 1 had a key of 1MB, 25MB, 49MB, 73MB each (thus 2 padding blocks)
container 2 had a key of 2MB, 26MB, 50MB, 74MB each (1 padding block)
container 3 had a key of 3MB, 27MB, 51MB, 75MB each (no padding)
container 4 had a key of 4MB, 28MB, 52MB, 76MB each (no padding)

Reproduced HDDS-10681 by stopping nodes hosting replica 2 of container 1 and replica 3 of container 2, and letting Ozone reconstruct all containers.
$ ozone debug fmp
Key	Size	Replication
vol1/bucket2/50mb	52428800	rs-3-2-1024k
vol1/bucket1/1mb	1048576	rs-3-2-1024k
vol1/bucket2/26mb	27262976	rs-3-2-1024k
vol1/bucket2/2mb	2097152	rs-3-2-1024k
vol1/bucket1/73mb	76546048	rs-3-2-1024k
vol1/bucket2/74mb	77594624	rs-3-2-1024k
vol1/bucket1/49mb	51380224	rs-3-2-1024k
vol1/bucket1/25mb	26214400	rs-3-2-1024k

By setting OZONE_LOGLEVEL, additional details are logged about the process:
$ OZONE_LOGLEVEL=INFO ozone debug fmp
...
[main] INFO shell.Handler: Found 4 blocks missing from container 1 on replica 2 at a9c3b585-23bc-4180-85e4-0180cb1e6054(restart_dn7_1.restart_net/<IP_ADDRESS>)
[main] INFO shell.Handler: Found 4 blocks missing from container 2 on replica 3 at a9c3b585-23bc-4180-85e4-0180cb1e6054(restart_dn7_1.restart_net/<IP_ADDRESS>)
...

(To filter unrelated log messages, set level specifically for log4j.logger.org.apache.hadoop.ozone.shell in log4j.properties, and use OZONE_LOGLEVEL=WARN to enable logging for the CLI command.)
Keys recreated using get/put are no longer reported:
$ ozone debug fmp
Key	Size	Replication
vol1/bucket2/50mb	52428800	rs-3-2-1024k
vol1/bucket2/2mb	2097152	rs-3-2-1024k
vol1/bucket2/74mb	77594624	rs-3-2-1024k
vol1/bucket2/26mb	27262976	rs-3-2-1024k

@siddhantsangwan would you like to take a look?

@siddhantsangwan would you like to take a look?
I haven't followed last week's developments on this, so we don't need to wait for my review. Thanks for asking!


VDP exit records (210) for Format Exits missing

The new Java RCA is not producing VDP records for Format Exits when reading from DB2.

Java RCA now producing the Format Exit records with RC6.


"node-wit": "^2.0.0" uses deprecated API

Hey there,
I noticed an issue where confidence score is not being returned when using botkit-middleware-witai. This is because it is using an old version on node-wit as a dependency.
Would it be possible to get this updated or is there a work around/something else I should be doing?
var VERSION = "20150306" is now deprecated. The latest is '20160516'
Thanks in advance for everything!

Looks like theres a PR which may address this actually - Feature new wit #8

node-wit version is updated.


Events: Event summary overflows horizontally

What happened?
The elements within the event summary are causing an undesired effect on the horizontal overflow on certain screen sizes.

Initially brought to my attention by anonymous club member.

Can't replicate. 🚀


Fix : Problem with webpack 4 : Object prototype may only be an Object or null: undefined

fixes issue: https://github.com/isaacs/node-graceful-fs/issues/222
https://github.com/isaacs/node-graceful-fs/commit/c55c1b8cb32510f92bd33d7c833364ecd3964dea  does not support browser environment, so this PR fixed this issue.
This error occurs in version v4.2.5 or higher versions

ref
Comparison of v4.2.4 and v4.2.5: https://github.com/isaacs/node-graceful-fs/compare/v4.2.4...v4.2.5

@isaacs
Hey! Thank you for maintaining this package. I added patch, please check it!


3943 reduce redis commands

This PR closes #3943 by reducing Redis usage in three ways:

Public map visualization adapter don’t request visualization stats (daily map views).
Public map page don’t request user stats (api calls).
ApiCalls now uses one ZSCAN per month instead of 30 ZRANGE for mapviews. The "per month" is because Redis gem doesn't support multiple MATCH arguments, I'll try to push a PR that accepts an array of matches, but it's not important for the moment.

Some data on the impact on my development environment (only two maps):
Dashboard: ~190 requests to ~18. Mostly because of replacing 180 zscore with 12 zscan.
Editor map view: ~690 to ~90. Mostly because of replacing 600 zscore with 32 zscan. Probably still too many.
Public dashboard: ~120 to ~10. Same.
@rochoa , @rafatower  could you take a look?
I still have to test this in staging, any hint on the impact of this, other that dashboard mapview charts?

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

:+1: you'll probably have to speak with clinker about the version of redis-server package...

Yep, in progress (that's why tests are failing).

LGTM :+1:

Ok, I'll deploy when Clinker passes tests.

do we know why opening a visualization launch more commands than the dashboard?

Yes, although dashboard requests mapviews from many visualizations, editor requests other information, especially geometry types and user database information. We can continue improving this later if needed, because many requests are duplicated some might be cached.

got it, those are not only stats related. Yep, will improve that

Retest this, please.

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)


is it possible to have JNI bridge just like arrow-cpp

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

JNI bridge would increase arrow-rs usage from JAVA ecosystem.
Describe the solution you'd like

JNI bridge just like arrow-cpp
Describe alternatives you've considered

arrow-cpp JNI bridge
Additional context

We provide C FFI bindings under the ffi feature flag, at least in theory these should be callable using JNI

We are using C FFI implementation from this crate to communicate between Rust and Java without issue.

@viirya  @tustvold  thanks for the information. I am currently using arrow java dataset jni API to calling into arrow parquet functionalities. when you say JNI are you talking about the same set of API or are there more details or examples on your usage scenarios ? thanks

I don't know the Arrow Java dataset JNI API you mentioned. What we do is to pass Arrow arrays between JVM (Java/Scala) and Rust (this crate) using the C FFI implementation.
You can look at ffi module of this crate. There are some public APIs we use, e.g., from_ffi, to_ffi, FFI_ArrowArray, FFI_ArrowSchema. The module also has some document and examples.

Hi, I might be dumb here, but would you mind sharing some specific code sample that passes array and schema between java and rust? Thanks!


Fix rustic-compilation-panic regex

Fix rustic-compilation-panic regex by removing  '[^']+',
Closes #573

I added the test in a separate commit, so the regression is easier. Unfortunately I cannot figure out why compilation-num-errors-found jumps from 0 to 2.

I added the test in a separate commit, so the regression is easier. Unfortunately I cannot figure out why compilation-num-errors-found jumps from 0 to 2.

I suspected rustic-panic to be in compilation-error-regexp-alist twice, but that not the case
(rustic-panic rustic-info rustic-warning rustic-error)

Note about https://github.com/brotzeit/rustic/issues/566

Note about #566

Oh my goodness. I totally missed that. Thanks for pointing that out @psibi

Closed in favor of emacs-rustic/rustic#31