Global scope / overrides?

Thanks for making this library! I've been testing it out for some use cases with anywidget. I'm trying to understand the importmap "scope"  that users have access to if allowing them to declare an import map. At the moment, it seems that if an import for a bare specifier has been declared, subsequent dynamic imports with an alternative import map are ignored.
In this example, I would expect foo1 to be { yay: "it works" } and foo2 to be the actual React, but foo is resolved to ./react.js in either case. If I flip the imports (e.g., load foo2 first), the both are resolved to React.
<!DOCTYPE html>
<script type="module">
  import { importWithMap } from<EMAIL_ADDRESS>  const foo1 = await importWithMap("./foo.js", {
    imports: { react: "./react.js" },
  });
  console.log({ ...foo1 });
  // { yay: "it works!" }

  const foo2 = await importWithMap("./foo.js", {
    imports: { react: "https://esm.sh/react@latest" },
  });
  console.log({ ...foo2 });
   // { yay: "it works!" }
</script>

// ./foo.js
export * from "react";

// ./react.js
export const yay = "it works!";

Do you know if it is possible (or within scope) to manage this type of use case? I think it would be quite powerful for "bits" of an application to define their own dependencies (without polluting others).
For anywidget, I'm imaging a use case where each widget can define an importMap, and then I can load the widget ESM with something like:
const anywidget_importmap = { ... };
const widget = await importWithMap(esm, merge(anywidget_importmap, widget_importmap))

Side note, I just learned that importmaps work for data urls! Really cool.
<!DOCTYPE html>
<script type="importmap">
  {
    "imports": {
      "bar": "data:text/javascript,export const BAR = \"BAR\";"
    }
  }
</script>
<script type="module">
  import * as bar from "bar";
  console.log(bar.BAR);
  // "BAR"
</script>

It seems like this is a bug. es-module-shims supports this with a mapOverrides option https://github.com/guybedford/es-module-shims#overriding-import-map-entries which I modified to always be true here https://github.com/keller-mark/dynamic-importmap/blob/05543cf1a26f32ed0951b84ea808851b8e337ab7/src/index.js#L54
I think it should first be fixed, but ideally it could also be configured as an option like
const options = { mapOverrides: true };
const foo1 = await importWithMap("./foo.js", importMap, options);


Deactivating / reactivating spfJS

Hello!
Thank you for the great spfJS!
I would like to use spfJS for my main navigation and at the same time have the ability opening/closing a modal window (that update the URL) on any page without triggering spfJS requests.
Here is what I am doing when opening the modal :
function open() {
     spf.dispose();
     // update DOM
     history.pushState({panel: true, },"Open modal", "/" + new_url);
     spf.init();
}

I also added a popstate event as follow :
window.addEventListener("popstate", function(event) {
     console.log("adress: " + document.location + ", state: " + JSON.stringify(event.state));

     if(event.state.hasOwnProperty('panel')) {
          spf.dispose();
          // open or close the panel based on the event.state
          open();
          spf.init();
     }
});

Is there a better way to momentary disable the spf postate event ?
Is there a way to test if spf is active ?
(Sorry for filling a bug but I could not find any solutions based on the doc.)

+1 to this issue want to deactivate the popstate listener in spf because have written one in my modal to behave differently

I want to avoid scenarios where we disable the popstate listener entirely, but we could certainly make it more specific to only handle SPF events. There's already some logic which ignores history events if they don't have a state object, so what if we extend that to ignore any event without a specific spf state field such as spf-timestamp? Would that suit your needs?

I managed to do what I want at the end without touching SPF code at the end and without disabling the popstate listener.
The pushState function is like that :
    function _pushState(panel_id, title, url) {
        spf.dispose();
        history.pushState({panel: true, panel_id: panel_id}, title, url);
        spf.init();
    }

And I have redefined a popstate event to capture the panel requests :
        window.addEventListener("popstate", function(event) {
            if(event.state) {
                if(event.state.hasOwnProperty('panel')) {
                    spf.dispose();

                    // do the pushState in open();
                    if(event.state.panel_id != "") open(event.state.panel_id);
                    else close();

                    spf.init();
                }
            }
        });


Cannot import the library with CocoaPods in Swift 4

After doing a pod install I get an unresolved identifier error no matter what I do. I have tried:

re-integrate the Pod
cleaning Derived data
Cleaning Build directory

Ok it was a simple mistake.
import paper_onboarding should be used instead of import PaperOnboarding
also the syntax in the sample code should be updated (enum spelled differently in Swift 4):
// create and configure view
        let onboarding = PaperOnboarding(itemsCount: 3)
        onboarding.dataSource = self
        onboarding.translatesAutoresizingMaskIntoConstraints = false
        view.addSubview(onboarding)

        // add constraints
        for attribute: NSLayoutAttribute in [.left, .right, .top, .bottom] {
            let constraint = NSLayoutConstraint(item: onboarding,
                                                attribute: attribute,
                                                relatedBy: .equal,
                                                toItem: view,
                                                attribute: attribute,
                                                multiplier: 1,
                                                constant: 0)
            view.addConstraint(constraint)
        }


[Tech Debt]: document cypress testing

Type
Quality (eg. tests)
Source
main
Description
Add documentation for cypress to the front end docs:

Running cypress as it pertains to local dev env and ci
Testing expectations for developers
Test structure
Best practices

Note that there exist some documentation for testing already in the architecture.md doc.
Why?
New devs should use our docs to understand how to add and maintain cypress tests.
Anything else?
No response

Already in jira


Implement template changes to enable native modules auto linking

Summary
Implements the template changes required to enable native modules auto-linking for both Android & iOS.
Requires the following to be merged first and an updated CLI to be published:

https://github.com/react-native-community/react-native-cli/pull/254
https://github.com/react-native-community/react-native-cli/pull/256
https://github.com/react-native-community/react-native-cli/pull/258

Changelog

[TEMPLATE] [FEATURE] - Enable auto-initialization/linking of react native modules for new projects
Test Plan

Superseded by https://github.com/facebook/react-native/pull/24506


Trying to open a Docker snippet hangs the image, memory leak

I was able to stop with user interrupt eventually but garbage collector has not reclaimed ~10Gb of memory leak created in a couple of seconds. Restarting Gt now.

Thank you very much for testing so thoroughly!


Code workflow

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Kalyansarkar123 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


updating crd for ripsaw-upstream

Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Has you operator nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

@aakarshg, please check PR form you posted and check what is needed.

hi @J0zi , thanks for the review. I've reviewed the checklist and checked off most of the tasks but one. I'd like to not use replaces property yet as we're planning to get a new release out soon at which point we'll use the replaces property.

@J0zi thanks for merging #860 , can you please merge this as well? The failure on operator-catalog-initialization isn't related to the pr.

closing and reopening due to operator-catalog-initialization test restart

/retest CVP

@J0zi the operator-catalog-initialization job failed and the error was:
time="2019-11-08T15:56:07Z" level=fatal msg="error loading package into db: service-binding-operator.v0.0.23 specifies replacement that couldn't be found"

Which seems to be no way related to the pr or ripsaw, can you please re-review and merge it soon, I plan on showing a demo about this at kubecon NA which is in around 24 hours :) thanks

@aakarshg, operator is not ready at the moment. We have to wait for @aneeshkp to push it to Quay. He is the only person who has appropriate rights at the moment.


Use pipeline run name as Bitbucket build status key

Multiple runs for the same commit now create multiple build status records
Re-runs of pipeline runs update the build status corrresponding to the original pipeline run

Closes #736.
Tasks:

[x] Updated design documents in docs/design directory or not applicable
[x] Updated user-facing documentation in docs directory or not applicable
[x] Ran tests (e.g. make test) or not applicable
[x] Updated changelog or not applicable

I find https://developer.atlassian.com/server/bitbucket/how-tos/updating-build-status-for-commits/ helpful. My understanding is:

The build status is associated with a commit even across repositories (and it appears projects even).
One can distinguish multiple build results by associating them with different keys. For example branch builds could have key 'branch' and integration builds 'integration'. The key could also be used to separate build results for different repositories.
Multiple builds with the same commit/key are not distinguished.

Number 1 appears troubling to me at first glance. On the other hand in practice this could be useful to connect a build status when a commit is deployed for example by a helm umbrella repo when it deploys a commit. Key could be 'DeployTest'. Perhaps I could be convinced that this is desirable.
When shown in summary spots in the UI the build results for a commit with different keys are combined:

Case A:  3 builds ✓ If all builds are green, and 3 is the number of unique keys.
Case B: 1 build failed if one build is red. Here the other builds are not mentioned. Only when one looks at the build status one would see all builds.
Case C Not sure what happens if multiple builds are red.

Having a single red build taint the overall (summarized) status feels strange to me (so perhaps I am misunderstanding the bitbucket behavior). Assuming the above is correct and deletes a pipeline run for a failed build, because perhaps it is stuck, a new build would have a new PipelineRuns derived key and this could never turn the build summary green.
Perhaps it would make sense to allow the key to be specified in ods.yaml. So that branch builds use an empty key (or git commit-sha) and integration build can use a different key.

We had a side conversation.

Creating a new pipeline after deleting a pipeline run is most frequently done by adding a new empty commit to trigger the new pipeline. Because of the new commit the problem of an ever-red status can be considered unproblematic.
The ever-red status for a commit could still happen when creating  a new pipeline by creating a new branch with the same commit. However simply adding an empty commit can fix the issue here.

This PR will be helpful for distinguishing pipeline runs in umbrella repositories where the same commit triggers different builds depending on the (target) branch.


Add programmatic login to Cypress

IMPORTANT: NO BOUNTIES WILL BE PAID FROM 2/5 - 2/14 - IF YOU COMPLETE THIS BOUNTY DURING THIS TIMEFRAME WE WILL REMIT PAYMENT ON 2/14
Background
The initial implementation of Cypress was designed to implement a minimal, best practice approach.
One known gap to meeting best practices is that the current login command uses the UI to login. This is fine for a small number of tests, but it is slow and so not a scalable solution as we begin to flesh out our testing suite.
Other considerations

The programmatic command will need to get from the Splash page (/connect-wallet?returnUrl=/dashboard) to the Dashboard page (/dashboard) without using the UI
Using ShapeShift's native login is preferred over MetaMask, Portis etc, though we are open to alternative approaches
At the end of the login, we'll have an indexedDB entry for the connected wallet similar to the one in cypress/fixtures/wallet.ts - you can use this wallet's data, if that helps

Acceptance Criteria

Replace the existing, UI based login command with a programmatic version, i.e. do the same thing, without clicking through the UI
At the end of the command we should be connected to the test wallet, which has testPublicKey = 0xfDCa77f9dBBc6D29970E9E0b0Ef5e5Bc45C8fCde, as defined in cypress.json. The corresponding testSeed and testPassword is also in this file.

Bounty Documentation

Please check out our docs for how to get in touch with us or ask questions.

I can work on this one

This is likely a blocker to https://github.com/shapeshift/web/issues/946, as CI builds will break until we have programmatic login.

@0xApotheosis @0xdef1cafe
I have been investigating / trying a lot of things for this item, and the only way I could see to programmatically login for cypress, is to expose the store via window object (https://stackoverflow.com/questions/66646336/how-to-access-redux-store-in-cypress-if-the-application-is-running-outside-of-cy). Then we could call some dispatch method or initiate the state in a way to automatically have the wallet connected.
This is clearly unsatisfactory for me for production code, also I could not succeed in making this unsatisfactory solution work (cypress object keeps getting undefined for a reason unclear to me).
That's why I prefer to hand over this item to someone else, hence I am stopping working on this bounty, before blocking it for too much time.
Hopefully someone will find a more satisfactory solution or make this solution work !

wow, appreciate the transparency and communication here.
i discussed this with @0xApotheosis yesterday and believe this is the approach he was willing to take. i'll let him respond but i think this is the best we can do right now and you may be able to pick this back up.
i won't reassign another bounty hunter until we figure out a path forward.

Thanks @chxash, appreciate the update.
I'm comfortable with the dispatch method approach to set the Redux State. It sounds like we just need to overcome the issue of accessing the Cypress context programmatically.
As discussed via DM, I'll take a parse at finding a solution for this, and then you can pick it back up from there.

@0xdef1cafe @0xApotheosis thank you for the feedback and DMs, I will gladly try to finish this once we find a solution

@0xdef1cafe - @Soptq has put together a nice PR for this, please accept his work request for the bounty and I'll work with him through to completion.


PyTorch 1.11 Docker Image

Adds PyTorch 1.11 + CUDA 11.3 and CPU Docker images to build matrix
Updates README
Fixes #847

@bandish-shah Do we need the MMCV_TORCH_VERSION specified too? Sounded like @Landanjs may have had some issue with that?

Could I test the image mosaicml/pytorch:1.11.0_cu113-python3.9-ubuntu20.04? I can see if mmcv installs

@bandish-shah Do we need the MMCV_TORCH_VERSION specified too? Sounded like @Landanjs may have had some issue with that?

I'm only adding Torch 1.11 in the mosaicml/pytorch image at the moment.  We only specify MMCV_TORCH_VERSION for the mosaicml/pytorch_vision image.  Does this mean you want a version of that image with Torch 1.11 as well?


[EXP-79-279] added tempus partner wrappers

While testing this PR, I found an issue with batch calls on Fantom.
I've implemented a quick fix for this issue in #281.
Placing this on hold until 281 is merged.


all.bat: tests fails in windows 10 at tip

all.bat in windows 10 fails with following errors.
I am using go 1.9.2 to build go tip.
Link to all.bat full output: http://text-share.com/view/cc0f79eb

The size of this issue is massive - please try to put most of the copy-pasted text into a file and link to it. Otherwise it's unmanageable.

Please provide your go env output. Also, does all.bat work fine if you're building 1.9.2?
Also note that you don't need to run the tests to build tip - you could use make.bat instead, skipping the tests.

C:\Users\rajender\go-contrib\go\src>go env
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\rajender\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\rajender\AppData\Local\Temp\go-build488734623=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config

building go1.9.2 also have same errors and some more.
Full output:  http://text-share.com/view/c8ae4745

@rajender quite a few tests fail.
I am not surprised that runtime.TestGdb* tests are not working. I have never tested them myself - I could not make gdb / pyhon runtime working. I suspect these are also skipped on all out builders.
runtime and cmd/go run out of time. I wonder if your computer is slow. You can test my theory by running these tests individually. You should also have -v flag so you can see progress as each test will print "PASS" as they go. For example, run
go test -v -short cmd/go

and see if it is still going just before 3 minutes elapses. Some for runtime package.
If your computer is slow, try and stop antivirus program temporarily - it helps for me a little.
Not sure about net/http.TestTransportBodyReadError failure.
Alex

I am not surprised that runtime.TestGdb* tests are not working. […] I suspect these are also skipped on all out builders.

They aren't skipped during racebuild (#24354). They're failing under gomote for me.

--- FAIL: TestGdbBacktrace (2.43s)
        runtime-gdb_test.go:59: gdb version 7.10
        runtime-gdb_test.go:346: could not find '#0.*main\.eee' in backtrace
        runtime-gdb_test.go:347: gdb output:
                Excess command line arguments ignored. (off ...)
                Directory argument required.
                Use 'set auto-load safe-path /' for disabling the auto-load safe-path security.
                C:\workdir\go\src\runtime: No such file or directory.
                C:\workdir\go\src\runtime/startup-with-shell: No such file or directory.
                Argument required (expression to compute).
                No default breakpoint address now.
                No executable specified, use `target exec'.
                No stack.
                The program is not being run.
--- FAIL: TestGdbPanic (7.21s)
        runtime-gdb_test.go:59: gdb version 7.10
        runtime-gdb_test.go:542: could not find '#.* .* in main\.crash' in backtrace
        runtime-gdb_test.go:543: gdb output:
                Excess command line arguments ignored. (off ...)
                Directory argument required.
                Use 'set auto-load safe-path /' for disabling the auto-load safe-path security.
                C:\workdir\go\src\runtime: No such file or directory.
                C:\workdir\go\src\runtime/startup-with-shell: No such file or directory.
                Argument required (expression to compute).
                No executable specified, use `target exec'.
                No stack.
--- FAIL: TestGdbConst (6.69s)
        runtime-gdb_test.go:59: gdb version 7.10
        runtime-gdb_test.go:475: output "Excess command line arguments ignored. (off ...)\nDirectory argument required.\nUse 'set auto-load safe-path /' for disabling the auto-load safe-path security.\nC:\\workdir\\go\\src\\runtime: No such file or directory.\nC:\\workdir\\go\\src\\runtime/startup-with-shell: No such file or directory.\nArgument required (expression to compute).\nNo default breakpoint address now.\nNo executable specified, use `target exec'.\nThe history is empty.\nThe history is empty.\nThe history is empty.\nThe history is empty.\nThe history is empty.\n"
        runtime-gdb_test.go:478: output mismatch
--- FAIL: TestGdbAutotmpTypes (6.00s)
        runtime-gdb_test.go:59: gdb version 7.10
        runtime-gdb_test.go:416: could not find struct []main.astruct; in 'info typrs astruct' output
        runtime-gdb_test.go:417: gdb output:
                Excess command line arguments ignored. (off ...)
                Directory argument required.
                Use 'set auto-load safe-path /' for disabling the auto-load safe-path security.
                C:\workdir\go\src\runtime: No such file or directory.
                C:\workdir\go\src\runtime/startup-with-shell: No such file or directory.
                Argument required (expression to compute).
                No default breakpoint address now.
                No executable specified, use `target exec'.
                The program is not being run.
                "info" must be followed by the name of an info command.
                List of info subcommands:

                info address -- Describe where symbol SYM is stored
                info all-registers -- List of all registers and their contents
                info args -- Argument variables of current stack frame
                info auto-load -- Print current status of auto-loaded files
                info auto-load-scripts -- Print the list of automatically loaded Python scripts
                info auxv -- Display the inferior's auxiliary vector
                info bookmarks -- Status of user-settable bookmarks
                info breakpoints -- Status of specified breakpoints (all user-settable breakpoints if no argument)
                info classes -- All Objective-C classes
                info common -- Print out the values contained in a Fortran COMMON block
                info copying -- Conditions for redistributing copies of GDB
                info dcache -- Print information on the dcache performance
                info display -- Expressions to display when program stops
                info exceptions -- List all Ada exception names
                info extensions -- All filename extensions associated with a source language
                info files -- Names of targets and files being debugged
                info float -- Print the status of the floating point unit
                info frame -- All about selected stack frame
                info frame-filter -- List all registered Python frame-filters
                info functions -- All function names
                info guile -- Prefix command for Guile info displays
                info handle -- What debugger does when program gets various signals
                info inferiors -- IDs of specified inferiors (all inferiors if no argument)
                info line -- Core addresses of the code for a source line
                info locals -- Local variables of current stack frame
                info macro -- Show the definition of MACRO
                info macros -- Show the definitions of all macros at LINESPEC
                info mem -- Memory region attributes
                info os -- Show OS data ARG
                info pretty-printer -- GDB command to list all registered pretty-printers
                info probes -- Show available static probes
                info proc -- Show /proc process information about any running process
                info program -- Execution status of the program
                info record -- Info record options
                info registers -- List of integer registers and their contents
                info scope -- List the variables local to a scope
                info selectors -- All Objective-C selectors
                info set -- Show all GDB settings
                info sharedlibrary -- Status of loaded shared object libraries
                info signals -- What debugger does when program gets various signals
                info skip -- Display the status of skips
                info source -- Information about the current source file
                info sources -- Source files in the program
                info stack -- Backtrace of the stack
                info static-tracepoint-markers -- List target static tracepoints markers
                info symbol -- Describe what symbol is at location ADDR
                info target -- Names of targets and files being debugged
                info tasks -- Provide information about all known Ada tasks
                info terminal -- Print inferior's saved terminal status
                info threads -- Display currently known threads
                info tracepoints -- Status of specified tracepoints (all tracepoints if no argument)
                info tvariables -- Status of trace state variables and their values
                info type-printers -- GDB command to list all registered type-printers
                info types -- All type names
                info unwinder -- GDB command to list unwinders
                info variables -- All global and static variable names
                info vector -- Print the status of the vector unit
                info vtbl -- Show the virtual function table for a C++ object
                info w32 -- Print information specific to Win32 debugging
                info warranty -- Various kinds of warranty you do not have
                info watchpoints -- Status of specified watchpoints (all watchpoints if no argument)
                info xmethod -- GDB command to list registered xmethod matchers

                Type "help info" followed by info subcommand name for full documentation.
                Type "apropos word" to search for commands related to "word".
                Command name abbreviations are allowed if unambiguous.
FAIL
FAIL    runtime 76.955s

Is there anything more to do here for 1.11?  Thanks.

No response to question as to whether there is anything else to do, so closing.


checkbashism: <IP_ADDRESS> -> 2.18.1

Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/checkbashisms/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
directory tree listing: https://gist.github.com/6e3ce06d60c67525f1f11df0822e6b36

Yep that is probably best.

Reverted in https://github.com/NixOS/nixpkgs/commit/18e4125b8873419308944e7adb805d6ad8b5da95.


DataException when using the JSONFilter type with an empty array.

Hi! Thank you for a great connector! But has this fix been released - https://github.com/streamthoughts/kafka-connect-file-pulse/issues/109? I see that even in the latest version i.e 2.6.0 I get the error -
io.streamthoughts.kafka.connect.filepulse.data.DataException: Failed to merge schemas for field 'field3'. at io.streamthoughts.kafka.connect.filepulse.data.StructSchema$StructSchemaMerger.apply(StructSchema.java:341) at io.streamthoughts.kafka.connect.filepulse.data.StructSchema.merge(StructSchema.java:260) at io.streamthoughts.kafka.connect.filepulse.data.LazyArraySchema.valueSchema(LazyArraySchema.java:55) at io.streamthoughts.kafka.connect.filepulse.filter.JSONFilter.apply(JSONFilter.java:90) at io.streamthoughts.kafka.connect.filepulse.filter.AbstractMergeRecordFilter.apply(AbstractMergeRecordFilter.java:43) at io.streamthoughts.kafka.connect.filepulse.filter.DefaultRecordFilterPipeline$FilterNode.apply(DefaultRecordFilterPipeline.java:162) at io.streamthoughts.kafka.connect.filepulse.filter.DefaultRecordFilterPipeline.apply(DefaultRecordFilterPipeline.java:134) at io.streamthoughts.kafka.connect.filepulse.filter.DefaultRecordFilterPipeline.apply(DefaultRecordFilterPipeline.java:102) at io.streamthoughts.kafka.connect.filepulse.source.DefaultFileRecordsPollingConsumer.next(DefaultFileRecordsPollingConsumer.java:176) at io.streamthoughts.kafka.connect.filepulse.source.FilePulseSourceTask.poll(FilePulseSourceTask.java:199) at org.apache.kafka.connect.runtime.WorkerSourceTask.poll(WorkerSourceTask.java:304) at org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:248) at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:188) at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:243) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: io.streamthoughts.kafka.connect.filepulse.data.DataException: Cannot infer value type because LIST is empty at io.streamthoughts.kafka.connect.filepulse.data.LazyArraySchema.valueSchema(LazyArraySchema.java:49) at io.streamthoughts.kafka.connect.filepulse.data.ArraySchema.merge(ArraySchema.java:89) at io.streamthoughts.kafka.connect.filepulse.data.StructSchema.merge(StructSchema.java:255) at io.streamthoughts.kafka.connect.filepulse.data.ArraySchema.merge(ArraySchema.java:86) at io.streamthoughts.kafka.connect.filepulse.data.StructSchema$StructSchemaMerger.apply(StructSchema.java:338)
My configuration:
fs.scan.interval.ms: "10000"     fs.scan.filters: "io.streamthoughts.kafka.connect.filepulse.scanner.local.filter.RegexFileListFilter"     file.filter.regex.pattern: ".*\\.json$"     tasks.reader.class: "io.streamthoughts.kafka.connect.filepulse.fs.reader.LocalBytesArrayInputReader"     topic: "filepulse-avro-v3"     internal.kafka.reporter.topic: "connect-file-pulse-status"     fs.cleanup.policy.class: "io.streamthoughts.kafka.connect.filepulse.fs.clean.LogCleanupPolicy"     fs.listing.class: "io.streamthoughts.kafka.connect.filepulse.fs.LocalFSDirectoryListing"     fs.listing.directory.path: "/tmp/jsonexamples/"     filters: "ParseJSON, ExcludeFieldMessage"     filters.ParseJSON.type: "io.streamthoughts.kafka.connect.filepulse.filter.JSONFilter"     filters.ParseJSON.source: "message"     filters.ParseJSON.merge: "true"     filters.ParseJSON.explode.array: "true"     filters.ExcludeFieldMessage.type: "io.streamthoughts.kafka.connect.filepulse.filter.ExcludeFilter"     filters.ExcludeFieldMessage.fields: "message"
Json Example:
[   {     "field1": "test1",     "field2" : "test5",     "field3": [       {         "field3_a": "test",         "field3_b": "test2",         "field3_c": "test3"       }     ],     "field4": {       "field4a": "",       "field4b": "",       "field4c": "",       "field4d": "",       "field4e": "",       "field4f": "",       "field4g": "",       "field4h": [         {           "field4ha": "",           "field4hb": "",           "field4hc": ""         }       ]     }   },   {     "field1": "test1",     "field2" : "test5",     "field3": [],     "field4": {       "field4a": "",       "field4b": "",       "field4c": "",       "field4d": "",       "field4e": "",       "field4f": "",       "field4g": "",       "field4h": [         {           "field4ha": "",           "field4hb": "",           "field4hc": ""         }       ]     }   } ]
Thanks!

Hi @pri-naik5, thank your for reporting this issue. I will investigate to try to reproduce your error.

Hi @fhussonnois, thanks. Is there a possible workaround I could do for this without needing to preprocess the files externally? We have a host of files which can have such empty arrays.

Hi @pri-naik5, sorry for the late reply. Could you try the version from the master branch ?  I pushed a commit(https://github.com/streamthoughts/kafka-connect-file-pulse/commit/82c3597bf02666f903312c78384c340722241e72) that should fix this issue. You should be able to test it using the docker image :
 docker pull streamthoughts/kafka-connect-file-pulse:master

Hi @fhussonnois Thanks! I think I need a zip file as I am running this on Strimzi and I need to add all the dependencies to a docker file


Fix naming of Aragon components in images

Aragon has changed the names of certain components recently:

Aragon Package Manager ==> aragonPM
Aragon CLI ==> aragonCLI
Aragon Core ==> Aragon client
aragon.js ==> aragonAPI
Aragon UI ==> aragonUI
Aragon ID ==> aragonID

Make the same changes for images and diagrams on hack.aragon.org.  These need fixing:

header image
main diagram
header image
header image

Adri made these originally and it'd probably be easiest for him to change them.

Ok, cool.  I don't see him in the assignees list.  What's the best way to get it on his todo list?

@cjyabraham I think he's mostly on our internal task board and not on Github; pinged him there!

Additional items to complete list of images that need to be changed related to this:
https://github.com/aragon/design/blob/master/logos/export/aragon-package-manager-horizontal.png
https://github.com/aragon/design/blob/master/logos/export/aragon-package-manager-vertical.png
https://github.com/aragon/design/blob/master/logos/export/aragoncli-horizontal.png
https://github.com/aragon/design/blob/master/logos/export/aragoncli-vertical.png
https://github.com/aragon/design/blob/master/logos/export/aragonjs-horizontal.png
https://github.com/aragon/design/blob/master/logos/export/aragonjs-vertical.png

These images have been updated to use their new names.


refactor(operator): refactor factory for configmap

Type of change:

[ ] Bugfix
[ ] New feature provided
[ ] Improve performance
[ ] Backport patches
[x] Refactor

What this PR does / why we need it:

Pre-submission checklist:

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[x] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?

Codecov Report

Merging #336 (ef4026f) into main (f7509f1) will decrease coverage by 5.92%.
The diff coverage is 40.45%.

@@            Coverage Diff             @@
##             main     #336      +/-   ##
==========================================
- Coverage   45.80%   39.89%   -5.92%
==========================================
  Files          21       44      +23
  Lines        1692     4650    +2958
==========================================
+ Hits          775     1855    +1080
- Misses        832     2668    +1836
- Partials       85      127      +42

Impacted Files
Coverage Δ

...ator/cmd/shardingsphere-operator/manager/option.go
51.68% <ø> (ø)

...pkg/controllers/shardingsphere_chaos_controller.go
0.00% <0.00%> (ø)

...here-operator/pkg/kubernetes/configmap/builders.go
40.28% <40.28%> (ø)

...here-operator/pkg/kubernetes/deployment/builder.go
83.33% <50.00%> (ø)

...phere-operator/pkg/kubernetes/configmap/factory.go
50.90% <50.90%> (ø)

...ere-operator/pkg/kubernetes/configmap/configmap.go
46.15% <100.00%> (ø)

... and 17 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Dev

done the work, need to fix why its always predicting 3 but its alr ill do it tmrw its fine its fine its fine

LGTM!


fix: set content type

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 28.472%

Totals

Change from base Build<PHONE_NUMBER>5:
0.04%

Covered Lines:
570

Relevant Lines:
2002

💛  - Coveralls


binary safe session persistence

FIX AWS SDK PHP DynamoDb StandardSessionConnection handles serialized sessions as strings, which is not binary safe
fixes #32

ready for a review

Works as advertised :) Was particularly interested in the transition of existing sessions once the new functionality is used. Tested with DynamoDB Local, see https://github.com/silverstripe/silverstripe-dynamodb/pull/34.
Add the following code to PageController->init():
$this->getRequest()->getSession()->set('foo', 'bar');

Use master branch. Visit /?flush=1. Observe session being created with string values:
aws dynamodb scan --table-name mysession --endpoint-url http://localhost:8000
{
    "Count": 1,
    "Items": [
        {
            "expires": {
                "N": "1562024548"
            },
            "data": {
                "S": "foo|s:3:\"bar\";HTTP_USER_AGENT|s:121:\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36\";"
            },
            "id": {
                "S": "PHPSESSID_7r6bcvrbb1cu8anch8img3lerp"
            }
        }
    ],
    "ScannedCount": 1,
    "ConsumedCapacity": null
}

Switch to PR branch. Visit /?flush=1 (in same browser session). Observe session data in DynamoDB hasn't changed.
Read out existing session value (in controller or elsewhere):
var_dump($this->getRequest()->getSession()->get('foo'));die();

Change the PageController->init() to a different session value:
$this->getRequest()->getSession()->set('foo', 'baz');

Visit /?flush=1. Observe session data changed to binary:
{
    "Count": 1,
    "Items": [
        {
            "expires": {
                "N": "1562024689"
            },
            "data": {
                "B": "Zm9vfHM6MzoiYmF6IjtIVFRQX1VTRVJfQUdFTlR8czoxMjE6Ik1vemlsbGEvNS4wIChNYWNpbnRvc2g7IEludGVsIE1hYyBPUyBYIDEwXzE0XzUpIEFwcGxlV2ViS2l0LzUzNy4zNiAoS0hUTUwsIGxpa2UgR2Vja28pIENocm9tZS83NS4wLjM3NzAuMTAwIFNhZmFyaS81MzcuMzYiOw=="
            },
            "id": {
                "S": "PHPSESSID_7r6bcvrbb1cu8anch8img3lerp"
            }
        }
    ],
    "ScannedCount": 1,
    "ConsumedCapacity": null
}

Read out session value, observe new value:
var_dump($this->getRequest()->getSession()->get('foo'));die();


BuiltIn Keyword 'Run Process' does not respect the globally set loglevel.

I'm trying to have as clean HTML log as possible so anyone can understand what is going on during my test execution by reading the log. I'm executing a lot of commands from robot via the builtin Run Process keyword. The issue is that this keyword is very talkative - at least to my standards, hence it fills up my HTML log with a lot of messages like these:
Starting process: XYZ
Waiting for process to complete.
Process completed.

I have tried to suppress this by issuing the "Set Log Level    NONE" keyword before calling Run Process, but after checking the code of Process.py I realised that logging inside this class is directly tied to loglevels (see: https://github.com/robotframework/robotframework/blob/master/src/robot/libraries/Process.py#L418C23-L418C23).
I have seen other builtin classes where the globally set loglevel is respected by using logger.log(level, msg) instead of logger.info(msg). I'd really welcome this in Process.py as well.

Setting log level before Run Process is executed to NONE or DEBUG ought to disable INFO level logging. Setting and then resetting the level isn't that convenient, though, and Run Process certainly could get a separate log_level=INFO argument. Anyone interested to implement it?

When I set LogLevel to NONE before Run Process, I only got the message "Log level changed from INFO to NONE." logged, then INFO logs still appeared from Run Process like usual, unfortunately.

That should not happen.

Here is my output:

I have tried a few different things and it turned out that if I add the "robot:flatten" tag to the keyword in which I execute the Run Process, then the --RemoveKeywords 'name:* = BuiltIn.Run Process' gets ignored and logs from the Run Process will exist in the HTML log.
Is this the intended behaviour that removed keywords appear when a parent keyword is flattened?
I'm using Robot Framework v6.1

I noticed you asked about this on Slack as well and there you mentioned you were flattering keywords. That is important information, because if you use the robot:flatten tag then the actual XML writer is different than normally and it could be buggy in this regard. I couldn't reproduce the issue even that way, though, but I noticed some odd behavior and need to investigate this further.
Could you create a simple example demonstrating the issue that I could run? The command you run with Run Process shouldn't matter and in fact using just Log ought to work the same way. Tell also what command line options you are use and what Robot version you have.

Also, robot:flatten effectively removes the executed keywords, other than their messages, so there's nothing --removekeywords can remove. Because --flattenkeywords affects output.xml processing, it has a huge performance effect, using that and --removekeywords at the same time doesn't work either. Using Rebot first with --removekeywords and then again with --flattenkeywords could work, though. That gets somewhat complicated, so creating a custom --pre-rebot-modifier could be a simpler solution and it would also allow full control on that's there in the log file. You could even add new messages or keywords if you wanted to.

I'm executing Robot with this additional argument: "--removekeywords tag:kwtoremove"
My keywords look like this:
Run Process Without Logging
    [Tags]    kwtoremove
    [Arguments]    ${command}    ${timeout}=0    ${on_timeout}=Terminate
    ${result} =    Run Process
    ...    ${command}
    ...    shell=yes
    ...    timeout=${timeout}
    ...    on_timeout=${on_timeout}
    RETURN    ${result}

Execute shell command
    [Tags]    robot:flatten
    [Documentation]
    ...    Executes a command in a shell with arguments.
    ...    Returns a result object which contains (rc, stderr, stdout).
    ...    Optionally the return code check can be disabled by setting "ret_check" parameter to False
    [Arguments]    ${command}    ${timeout}=0    ${on_timeout}=Terminate    ${msg_on_fail}=""    ${ret_check}=True
    Log    Run command: ${command}    level=INFO
    ${result} =    Run Process Without Logging
    ...    ${command}
    ...    timeout=${timeout}
    ...    on_timeout=${on_timeout}
    Log    Returned output:\n${result.stdout}   level=INFO
    Log    Returned error:\n${result.stderr}     level=DEBUG
    Log    Returned RC: ${result.rc}    level=DEBUG
    IF    ${ret_check} != False
        Should Be Equal As Integers    ${result.rc}    ${0}    msg="${msg_on_fail}"
    ELSE
        Log    Return check is disabled for this execution    level=DEBUG
    END
    RETURN    ${result}

I get this result:

But according to your latest comment, this makes sense that it's not working. Then I see that my options are to add the loglevel option to the builtin Run Process keyword, or to write my own keyword in python as an external library where I can specify my own loglevels for the process execution.

That example doesn't seem to use Set Log Level but instead the idea is to remove the whole Run Process Without Logging, right? That's a clever idea, but unfortunately doesn't work, because flattening already removes that keyword but leaves messages.
The recommended way to temporarily disable logging is using something like this:
Run Process Without Logging
    [Arguments]    ...
    ${old} =    Set Log Level    NONE
    ${result} =    Run Process    ...
    RETURN    ${result}
    [Teardown]    Set Log Level    ${old}

The problem with the above is that unfortunately robot:flatten doesn't work properly with log levels. As I mentioned in an earlier comment, there's a different XML logger in use when flattening and I was right that there's a bug. That logger has TRACE as the default level instead of INFO or whatever is set from the command line. That means that after running the above example the level would be TRACE. An easy fix is using
    [Teardown]    Set Log Level    INFO

but that then overrides whatever was from from the cli.If you are only using INFO, that shouldn't matter.
I'll submit a separate issue about robot:flatten and log levels and that issue will be fixed in RF 7.0. After that also the recommended approach will work.

Temporarily altering log levels with Set Log Level is somewhat inconvenient. We could consider adding a tag like robot:log-level=<level> that could be used to control that. If you'd find it useful, please submit an issue. Unless you or someone else is interested to provide a PR, there's no time to get it done before RF 7.0, though.

Yeah what I pasted above is a next iteration where I tried to solve the issue.
So you could reproduce the Set Log Level not affecting the keywords when using flatten? Is this what you're fixing?
My problem with that is even if that would work, then I'd see a lot of "Log level changed from X to Y" messages in the log, which will cause it to be a pain to read between the command executions.

Yes, I was able to reproduce the problem with levels and robot:flatten. I'll submit a separate issue about that. Setting level first to NONE and then INFO ought to mostly workaround the problem.
I agree that the level changing message is somewhat annoying in this context. I don't want to remove it altogether, but we could change its level to DEBUG. Having some more convenient way than Set Log Level to alter the level would be nice but lot more work.

The issue with robot:flatten and log levels is now fixed and I also changed Set Log Level message level to DEBUG.
I think you should change your keyword to use Set Log Level to disable logging before Run Process and then set the level to INFO afterwards. You shouldn't even need to have a separate keyword for that, you could do all this directly in Execute shell command. This ought to work now and with RF 7.0 it will work even better.
If using hard-code INFO when resetting the level is a problem, you could store the original log level to a variable and use that:
*** Varibles ***
${ORIG LOG LEVEL}    ${LOG LEVEL}

${LOG LEVEL} is a built-in variable that is set based on the --logleve option and changed automatically when Set Log Level is used.

Is there still something unclear regarding to this issue? If not, I guess it can be closed. If you'd want Run Process to have log_level argument to control its logging, please submit a new issue.

Thanks I have submitted the feature request: https://github.com/robotframework/robotframework/issues/4929
Sorry for my late reply, and many thanks for your assistance!

Another related idea I got is adding a new keyword Reset Log Level that would always reset the level to the level set with --loglevel or to INFO if not set. That would simplify setting and resetting the level, because you didn't need to store rhe original level to a variable.

Hmm yeah, that would be cool! I really welcome this idea!

Can you submit an issue about that as well? Even better if you are interested to create a PR.


[SPARK-10001] [CORE] Allow Ctrl-C in spark-shell to kill running job

This patch attaches a signal handler for SIGINT to JobWaiter when a job is running and detaches it as soon as the job is finished. When ctrl-c is pressed during this time, spark-shell cancels the running job.
It's worth noting that signal handler is only overridden when job is running. So if ctrl-c is pressed when spark-shell is idle, it will still interrupt JVM and exit the shell (same as now).
In addition, if ctrl-c is pressed multiple times when job is running, it will interrupt JVM and exit the shell. This is to avoid any case that the shell becomes unresponsive. For eg, consider this scenario. User submits a job in the shell. But since the job lists a lot of files before running, it might be hanging in the driver. In this case, user can interrupt JVM and exit the shell by ctrl-c'ing twice.
Here is summary-

#
case
before
after

1
shell is idle
ctrl-c will exit the shell
ctrl-c will exit the shell

2
job is submitted but not yet running (e.g. driver listing input files)
ctrl-c will exit the shell
ctrl-c will exit the shell [a]

3
job is submitted and running on cluster
ctrl-c will exit the shell
ctrl-c will not exit the shell but cancel the job [b]

This patch basically improves case 3 by allowing the user to cancel a running job on cluster w/o exiting the shell.
[a] 1st ctrl-c will print a log message saying Cancelling running job.. This might take some time, so be patient.  Press Ctrl-C again to kill JVM. 2nd ctrl-c will exit the shell.
[b] when job is running, ctrl-c immediately cancels the job, and the prompt is returned to user.

Merged build triggered.

Merged build started.

Test build #40927 has started for   PR 8216 at commit 7342f1b.

For some reason, this PR didn't get sync'ed with jira and spark-prs.appspot.com. I'll close and create it again.

Merged build triggered.

Merged build started.

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

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

Merged build finished. Test FAILed.

Strange error in jenkins. Build doesn't start for some reason.

Test build #1614 has started for   PR 8216 at commit c8a3ba8.

Test build #40927 timed out     for PR 8216 at commit 7342f1b     after a configured wait of 175m.

Merged build finished. Test FAILed.

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

Test build #1614 has finished for   PR 8216 at commit c8a3ba8.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class StringIndexerModel (

Jenkins, test this please

Merged build triggered.

Merged build started.

Test build #40955 has started for   PR 8216 at commit c8a3ba8.

Test build #40955 has finished for   PR 8216 at commit c8a3ba8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

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

Merged build finished. Test FAILed.

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #41011 has started for   PR 8216 at commit 1cae5da.

Test build #41011 timed out     for PR 8216 at commit 1cae5da     after a configured wait of 175m.

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #41025 has started for   PR 8216 at commit 9f6507c.

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

Merged build finished. Test FAILed.

Test build #41025 has finished for   PR 8216 at commit 9f6507c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Test build #41037 has started for   PR 8216 at commit 166e9f6.

Test build #41037 has finished for   PR 8216 at commit 166e9f6.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Exception encountered when attempting to run a suite with class name: org.apache.spark.deploy.yarn.YarnClusterSuite *** ABORTED *** (1 second, 891 milliseconds)
  org.apache.hadoop.yarn.exceptions.YarnRuntimeException: java.io.IOException: ResourceManager failed to start. Final state is STOPPED

The test failure is because mini YARN cluster failed to start the RM. I'll trigger another run of tests.

Merged build triggered.

Merged build started.

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #41083 has started for   PR 8216 at commit c03bf07.

Test build #41083 has finished for   PR 8216 at commit c03bf07.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class StringIndexerModel (
class ElementwiseProduct(JavaTransformer, HasInputCol, HasOutputCol):
 implicit class StringToColumn(val sc: StringContext)
case class FilterNode(condition: Expression, child: LocalNode) extends UnaryLocalNode
abstract class LocalNode extends TreeNode[LocalNode]
abstract class LeafLocalNode extends LocalNode
abstract class UnaryLocalNode extends LocalNode
case class ProjectNode(projectList: Seq[NamedExpression], child: LocalNode) extends UnaryLocalNode
case class SeqScanNode(output: Seq[Attribute], data: Seq[InternalRow]) extends LeafLocalNode
public final class UTF8String implements Comparable<UTF8String>, Externalizable

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

Merged build finished. Test FAILed.

Hmm, not sure why a test case fails in YarnClusterSuite, but it seems failing constantly. I'll investigate it.

I believe the YarnClusterSuite failure is fixed by SPARK-10059 because I see the same error message (java.lang.NoClassDefFoundError: javax/servlet/jsp/JspFactory) in the log.
I'll rebase my patch to trigger another run of unit tests.

Merged build triggered.

Merged build started.

Test build #41148 has started for   PR 8216 at commit d3eabf0.

Test build #41148 has finished for   PR 8216 at commit d3eabf0.

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

Merged build finished. Test PASSed.

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

Merged build triggered.

Merged build started.

Test build #41991 has started for   PR 8216 at commit d3eabf0.

Test build #41991 has finished for   PR 8216 at commit d3eabf0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Test build #42012 has started for   PR 8216 at commit cb3b73f.

Test build #42012 has finished for   PR 8216 at commit cb3b73f.

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

Merged build finished. Test PASSed.

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

@piaozhexiu This is cool, thanks! I also want this for Python for a long time (could be a separate PR).

Created https://issues.apache.org/jira/browse/SPARK-10553

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Test build #42373 has started for   PR 8216 at commit 1ba208a.

Test build #42373 has finished for   PR 8216 at commit 1ba208a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class IntersectNode(conf: SQLConf, left: LocalNode, right: LocalNode)
case class SampleNode(
case class TakeOrderedAndProjectNode(

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

Merged build finished. Test PASSed.

retest this please
@davies we still want this right?

@andrewor14 @davies guys any plans to get this in?

@piaozhexiu could you update this PR?

@hvanhovell @nezihyigitbasi Looks like JobWaiter has changed since. I haven't actively followed Spark recently. Can you guys take over from here? Thanks!

cc @jodersky would this be something you would be interested in continuing on with?

That would indeed be a cool feature to have! I'll give it a shot

Should signal handling really be implemented in a JobWaiter? I'm afraid that implementing it there could have unwanted consequences for non-shell operation: Imagine implementing a custom program that uses a spark context, in that case it should terminate on reveption of SIGINT by default, regardless of current job execution.
IMO signal handling is best implemented on the shell level. Any thoughts?


/ORCL: Permission denied - when host directory is mapped to /ORCL

I have referred issues #439, #736, #783 and also the FAQ. But even after changing the ownership of the host directory to 54321:54321, the /ORCL cannot be accessed:
$ sudo mkdir -p /oradata/db8
$ sudo chown -R 54321:54321 /oradata
$ sudo chmod 777 /oradata/db8
$ sudo docker run -it --name testdb8 -v /oradata/db8:/ORCL store/oracle/database-enterprise:<IP_ADDRESS> ls -al /ORCL
ls: cannot open directory /ORCL: Permission denied
I can create the docker volume with a local directory and run the image without any issue. But wanted to clarify on this one. Anything I am missing here?

Can it be that SELinux is blocking you accessing /ORCL?

Yes! chcon -Rt svirt_sandbox_file_t /oradata/db8 resolves it. Thank you!


Does not detect mixed content in @import rules in CSS

e.g. when loading webfonts from inside a CSS file like this
@import url(http://fonts.googleapis.com/css?family=Open+Sans:400,700,300);

will not be detected.

sorry, just realized that this is a "known issue"...


Move functions F2-F9 & A2-A9 outside conditional

Using a function statement inside a conditional is non-standard (most browers other than Firefox will declare the function anyways). Since the only point of having these inside the conditional seems to be to prevent them from being redefined to the same thing if Runtime.js is included twice on the same page, it seems safe to move them out from the conditional.
The benefit to doing this is that it allows the Closure Compiler to be used on the generated elm.js (at least in WHITESPACE_ONLY and possibly on SIMPLE_OPTIMIZATIONS). A simple "Hello World" app:
module Main (..) where

import Graphics.Element exposing (show)

main =
    show "Hello World!"

When compiled is 147K.
Minimized on WHITESPACE_ONLY it is 96K (and works fine).
Minimized on SIMPLE_OPTIMIZATIONS is 61K (and works fine).
On a somewhat larger project of mine that compiles to 562K, making this change also allows WHITESPACE_ONLY compilation to 292K (works) and SIMPLE_OPTIMIZATIONS compilation to 202K (also works).
It's possible there's something I'm missing, but I don't think there's any downside to moving these outside the conditional.

I'm not sure. It is going to just work different in the next release such that Closure Compiler has a much easier time with things. I've also verified that everything works with simple optimizations in the new version of things.


chore: release 1.2.300

:robot: I have created a release *beep* *boop*
1.2.300 (2024-03-21)
Features

make werf root command embeddable (2e1c9d3)

Bug Fixes

nelm: Jobs not failing on errors /2 (96793f0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v1.2.300 :sunflower:


changed event type

Signed-off-by: Jonathan Holloway<EMAIL_ADDRESS>Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] I run go fmt ./... to check that my code is properly formatted
[x] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #851 (c2b476c) into main (7e84f07) will increase coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #851      +/-   ##
==========================================
+ Coverage   30.66%   30.69%   +0.03%
==========================================
  Files          44       44
  Lines        4980     4974       -6
==========================================
  Hits         1527     1527
+ Misses       3249     3243       -6
  Partials      204      204

Impacted Files
Coverage Δ

pkg/services/consumers.go
25.35% <0.00%> (+1.02%)
:arrow_up:

Continue to review full report at Codecov.

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


[FEATURE] Export API docs

Is it possible to have a method to extract or export the auto generated docs to a static set of pages? (This may already be possible, and I've missed it)
Thinking of separate docs subdomain and separating API and docs HTTP request traffic, etc.

It's a matter of copying the openapi.json and setting up which ever Doc System you wanna use, Swagger, Redoc. They both are just static one page websites.

Is it that easy? That's pretty cool. Thanks - closing this issue.

@jaddison This section of the docs may also be of interest to you: https://fastapi.tiangolo.com/tutorial/extending-openapi/#self-hosting-javascript-and-css-for-docs

Thanks for the help here everyone! :cake: :bowing_man:
And thanks @jaddison for reporting back and closing the issue :+1:

I posted a Python script here to export the ReDoc docs into a standalone HTML file, if anyone is interested :wink:


[Enhancement] Stereoscopic rendering

I know it's a long-shot, but it would be incredibly cool if DXVK supported stereoscopic rendering in the manner of Nvidia's (now unsupported) 3D Vision, or using the techniques deployed by Tridef's Ignition driver.  At a minimum, support for anaglyph (with any combination of color channels) and horizontal interlacing would be amazing.  Side-by-side, above-below, frame-sequential, and rendering each image to a separate output (for dual projector setups) would also be useful, once the basics are implemented.

No.

To give a more detailed explanation: stereoscopic rendering has nothing to do with the graphics API at all, but is a game engine thing. You can of course write somethig like a D3D11 wrapper library to support this in a specific game, but that's the thing, you need exact knowledge of how the game engine you're working with works, and have to basically redo everything from scratch if you want to support a different game.


case on Sum types

It would be nice to also generate a case macro for a sum type that can validate that all options are tested for (so if we extend it later we do not forget a place to update), such as with an example of:
defmodule Light do
  defsum do
    defdata Red    :: none()
    defdata Yellow :: none()
    defdata Green  :: none()
  end
end

And could use it as:
def myfunc(light) do
  Light.case light do
    %Red{} -> "red"
    %Yellow{} -> "yellow"
    %Green{} -> "green"
  end
end

Then if I changed the original sum type to be:
defmodule Light do
  defsum do
    defdata Red    :: none()
    defdata Yellow :: none()
    defdata Green  :: none()
    defdata Custom do
      red   :: non_neg_integer()
      green :: non_neg_integer()
      blue  :: non_neg_integer()
    end
  end
end

Then the prior Light.case would throw a compile-time error stating that not all branches are taken, of which it could be fixed by either adding a:
    %Custom{red: r, green: g, blue: b} -> "custom<#{r}:#{g}:#{b}>"

Or (though this form would swallow all future modifications as well, thus not recommended, but allowed, maybe to allow this an option has to be passed to the Light.case to allow a default case?):
    _ -> "unknown"

I'm just wanting anything that forces me to handle modified sum types instead of just silently ignoring them thus allowing me to forget about them.  :-)
P.S.  Love the design!  I might toss this into my MLElixir playground (definitely will with the above change!) as it would simplify my manually created sum/prod types.  ^.^;
Also, I notice the prod types are structs, if they were matched on in, say, the Light.case example above then I'd definitely want it to error if not all subtypes are handled, thus if Custom was changed to have an alpha with a default value, then in the Light.case the alpha has to be matched as well or it will fail compilation (at least one case should check 'all' values, even if earlier cases only match a couple), or perhaps (maybe via an option on the case as well) allow an empty matcher for the type like %Custom{} = custom so that it assumes the user will access it properly internally or so, unsure on exact semantics that I think would be best, would have to play with it...

Hm, yeah, I definitely agree that's a useful feature! I was under the impression that Dialyzer does missing cases analysis, no?

Hm, yeah, I definitely agree that's a useful feature! I was under the impression that Dialyzer does missing cases analysis, no?

It misses a whole ton of cases.  Dialyzer is only a success typer, so if it tells you something is wrong then it is definitely wrong, but if it is quiet then something 'might' be wrong or it 'might' be right, and in regards to cases it does not get everything.  >.>
/me wishes Elixir had Hindley-Milner Typing...

/me wishes Elixir had Hindley-Milner Typing...

Yup, me too! (Actually, I wish that I could work in a dependently typed language, but le sigh). With luck, Alpaca will save us all (and add explicit type signatures) 😉

I'm actually more partial to OCaml style typing, it is easier to compile, faster to resolve, plus if you bring in the module system (which is entirely doable on the BEAM) then it becomes more powerful than what you can do in Haskell style.  :-)
I'd been playing with seeing how I can stretch the Elixir AST in macro's and as I get time I've been screwing around with an HM-typing mini-macro-language, can see the tests at (you get type unification failures and all properly if something is mis-typed, and as you can see you can 'type' a normal elixir call on an elixir module so the system understands and can use, it adds the right guards and all to make sure normal elixir cannot mis-call something):
https://github.com/OvermindDL1/typed_elixir/blob/master/test/ml_elixir_test.exs
https://github.com/OvermindDL1/typed_elixir/blob/master/test/ml_elixir/ml_module_test.exs
In general you can do this and it generates valid, fully typed elixir (notice even can 'type' modules as in SML/OCaml ;-) ):
import MLElixir

defmlmodule MLModuleTest do

  type type_declaration

  type type_definition = integer

  type record_emb_0 = %{a: %{b: %{c: type_definition}}}

  type testering_enum
  | none
  | one
  | integer integer
  | two
  | float float
  | float2 float

  def test_int_untyped = 42
  def test_int_typed | integer = 42
  def test_float_untyped = 6.28
  def test_float_typed | float = 6.28
  def test_defined | type_definition = 42
  def identity_untyped(a) = a
  def identity_typed(b | !id_type) | !id_type = b
  def identity_int(c | integer, f | float) | integer = c
  def identity_float(x | integer, f | float) | float = f
  def test_block0 do 42 end
  def test_blockN0() do 42 end
  def test_blockT0() | integer do 42 end
  def test_blockN1(x) do x end
  def test_blockT1(x | !id_type) | !id_type do x end
  def test_noblockT1(x | !id_type) | !id_type = x
  def test_record | record_emb_0 = %{a: %{b: %{c: 42}}}
  def test_record_sub(r | record_emb_0) = r.a

end

defmlmodule MLModuleTest_Generalized do
  type t

  def blah(t | t) | t, do: t
  def bloo(t | t) | t = t
end

  defmlmodule MLModuleTest_Specific, debug: [:_resolving, :module_pretty_output] do
    type t = MLModuleTest.type_definition
    type Specific = MLModuleTest_Generalized.(t: float)
    type st = Specific.t
    type a(t) = t
    type b(c) = c
    type ra = a(integer)
    type rb = b(integer)

    type testering_enum
    | none
    | one
    | integer integer
    | two
    | float float
    | float2 float
    # | t integer # Single value?
    # | t_f0 integer, float # multiple value?
    # | i_f1(integer, float) # Hmm, what for...
    # | t_f2{integer, float} # Hmm... default tuple?
    # | t_f3[i: integer, f: float] # Keyword list version maybe?  Or just make a normal list?
    # | %t_f4{t: integer, f: float} # Map version?
    | tuple_enum0{}
    | tuple_enum1{integer}
    | tuple_enum2{integer, float}
    | tuple_recurception{{integer, float}}
    # | record_enum %{integer: integer}
    # | map_enum %{integer => float}
    # | gadt_enum = (integer | float)

    def testering0 | t = 42
    def testering1 | st = 6.28
    def testering2 | ra = 42
    def testering3 | rb = 42
    def testering4 | a(integer) = 42
    def testering5 | a(float) = 6.28
    def testering6 | testering_enum = none() # Just testing that it works with 0-args too, elixir ast oddness reasons
    def testering7 | testering_enum = one
    def testering8 | testering_enum = two
    def testering9 | testering_enum = integer # Curried!
    def testering9x(x) | testering_enum = integer x # Not-Curried!
    def testering10 | testering_enum = integer 42
    def testering11(x) | testering_enum = integer x
    def testering12 = MLModuleTest.test_int_untyped
    def testering13 = MLModuleTest.test_int_typed
    def testering14 = MLModuleTest.test_record.a.b.c
    def testering15(r) = MLModuleTest.test_record_sub(r).b.c
    # def testering16 = MLModuleTest.testering_enum # Should fail
    def testering17 = MLModuleTest.testering_enum.one
    def testering18 = MLModuleTest.testering_enum.integer # auto-curry gadt head test
    def testering19(i) = MLModuleTest.testering_enum.integer i
    def testering20 = tuple_enum0
    def testering21 = tuple_enum1 42
    def testering22 = tuple_enum2
    def testering23 = tuple_enum2 42
    def testering24(f) = tuple_enum2 42, f
    def testering25 = tuple_enum2 42, 6.28
    def testering26 = testering0
    def testering27 = tuple_recurception {42, 6.28}

    # Functions
    def testering_func0 = 42
    def testering_func1(a, b, c) | {integer, integer, integer} = {a, b, c}
    def testering_func2(a | integer, b | integer, c | integer) = {a, b, c}
    def testering_func3(a | integer, b | integer, c | integer) | {integer, integer, integer} = {a, b, c}
    def testering_func4 = testering_func0
    def testering_func5 = testering_func1 1, 2, 3
    def testering_func6(a, b, c) = testering_func1 a, b, c
    def testering_func7(a) = testering_func1 1, a, 3
    def testering_func8 = testering_func1
    def testering_func9(a) = testering_func1 a
    def testering_func10(a) = testering_func1 1, a
    def testering_func11(a) = testering_func1 a, 2
    def testering_func12(a, b) = testering_func1 a, b
    def testering_func13(a) = testering_func1 a, _, _
    def testering_func14(a) = testering_func1 _, a, _
    def testering_func15(a) = testering_func1 _, _, a
    def testering_func16(a) = testering_func1 _, a
    def testering_func17(a) = testering_func1 a, _0, _1
    def testering_func18(a) = testering_func1 a, _1, _0
    def testering_func19(a) = testering_func1 a, _1
    def testering_func20 = testering_func8 1, 2, 3
    def testering_func21 = testering_func9 1, 2, 3
    def testering_func22 = testering_func12 1, 2, 3
    def testering_func23 = testering_func9 1
    def testering_func24 = testering_func9 1, _
    def testering_func25 = testering_func9 _, 2
    def testering_func26a(a, b, c, d, e) = {a, b, c, d, e}
    def testering_func26b(b) = testering_func26a 1, b
    def testering_func26c(c) = testering_func26b 2, c
    def testering_func26d(d) = testering_func26c 3, d
    def testering_func26(e) = testering_func26d 4, e
    def testering_func27(e) = testering_func26a _, _, _, _, e
    def testering_func28(e) = testering_func26b _, _, _, e
    def testering_func29(e) = testering_func26a _3, _2, _1, _0, e
    def testering_func30(f) = f(2)
    def testering_func31(value, f) = f(value)
    def testering_func32(value | integer, f) = f(value)
    def testering_func33 = testering_func31(3, testering_func1(1, 2))

    # Bindings
    def testering_binding0(i) = i
    def testering_binding1(i | integer) = i
    def testering_binding2(42) = 42
    def testering_binding3(42 | integer) = 42
    def testering_binding4(42 = i) = i
    def testering_binding5(i = 42) = i
    def testering_binding6({i}) = i
    def testering_binding7({42}) = 42
    def testering_binding8({i | integer}) = i
    def testering_binding9({i | integer} | {integer}) = i
    def testering_binding10({i} | {integer}) = i
    def testering_binding11({i}=t) = {i, t}
    def testering_binding12(%{a: i | integer}) = i
    def testering_binding13(%{a: i | integer}=r) = %{b: r}

    # Records (I.E. Erlang/Elixir atom() keyed maps, like structs)
    type record0 = %{} # Empty record
    type record1 = %{
      x: integer,
      y: float,
    }
    type record2(t) = %{t: t}
    type record_ex_0 = %{+: record0, z: integer}
    type record_ex_1 = %{+: record1, +: record0, z: integer}
    type record_ex_2(t) = %{+: record2(t), z: integer}
    type record_ex_2_float = %{+: record2(float), z: integer}
    # type record_ex_sub(t) = %{+: t, z: integer} # Need to support unbound's perhaps? # Unsure if I want to support this...
    type record_rem_0 = %{+: record1, -: x}
    type record_emb_0 = %{a: %{b: %{c: integer}}}

    def testering_record0 | record0 = %{}
    def testering_record1 | record1 = %{x: 42, y: 6.28}
    def testering_record2(i) | record1 = %{x: i, y: 6.28}
    def testering_record3(t | !t) | record2(!t) = %{t: t}
    def testering_record4 | record_ex_0 = %{z: 42}
    def testering_record5 | record_ex_1 = %{x: 42, y: 6.28, z: 42}
    def testering_record6 | record_ex_2(integer) = %{t: 42, z: 42}
    def testering_record7(t | !t) | record_ex_2(!t) = %{t: t, z: 42}
    def testering_record8 | record_ex_2_float = %{t: 6.28, z: 42}
    # def testering_record9 | record_ex_sub(record2(float)) = %{t: 6.28, z: 42} # Unsure if I want to support this...
    def testering_record10 | record_rem_0 = %{y: 6.28}
    def testering_record11(r | record_emb_0) = r.a.b.c

    # Tuples
    type tuple0 = {}
    type tuple1 = {integer}
    type tuple2 = {integer, float}
    type tuple3 = {integer, {float, integer}}

    def testering_tuple0 | tuple0 = {}
    def testering_tuple1(t) | tuple0 = t
    def testering_tuple2 = {}
    def testering_tuple3 = {42}
    def testering_tuple4 | tuple1 = {42}
    def testering_tuple5(i) | tuple1 = {i}
    def testering_tuple6(t) | tuple1 = t
    def testering_tuple7 | tuple1 = testering_tuple3
    def testering_tuple8 = {42, 6.28}
    def testering_tuple9(i|!t) = {i, 6.28}
    def testering_tuple10(i) | tuple2 = testering_tuple9 i
    def testering_tuple11 | tuple2 = testering_tuple9 42
    def testering_tuple12 | tuple3 = {42, {6.28, 42}}

    # FFI
    external addi(integer, integer) | integer = Kernel.+
    def testering_ffi_addi_0 = addi(1, 2)
    def testering_ffi_addi_1(i) = addi(1, i)
    def testering_ffi_addi_2(a, b) = addi(a, b)

    def value |> fun = fun(value)
    # let value |> fun = fun(value) # Both work as always
    # def testering_op_pipe0 = 42 |> testering_tuple5
    def identity(i) = i
    def testering_op_pipe1(i) =
      42
      |> identity
      |> testering_func1(1, _, i)
    # def testering_op_pipe2(i) =
    #   42
    #   |> identity
    #   |> testering_func1(1) # partial currying not yet implemented, see:  :make_function_wrapper_of_proper_length
    # def testering_op_pipe2() =
    #   42
    #   |> identity
    #   |> testering_func1
  end

I'm not intending on that to be a real language, just me screwing around for fun, if I were to make a real language in it then it would not be constrained by the Elixir AST for sure.  ^.^;


No webviews can load

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:

$ code --version
1.60.2
7f6ab5485bbc008386c4386d08766667e155244e
x64

OS Version:

$ cat /etc/os-release
NAME="Pop!_OS"
VERSION="20.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
LOGO=distributor-logo-pop-os

Steps to Reproduce:

Install VS Code 1.60.2 from the website
Open Release Notes (Ctrl + Shift + P, "Show Release Notes")
See error message :

Error loading webview: Error: Could not register service workers: InvalidStateError: Failed to register a ServiceWorker: The document is in an invalid state..

If this issue is duplicated, there should be a link for the original one. I have looked over three issues and still didn't find where it was solved.


unix: Fix build when using tflm in microlite

Find a way to detect if we are in the stm32 build or the unix port build:
./../../micropython-modules/microlite/openmv-libtf.h:18:10: fatal error: tensorflow/lite/c/common.h: No such file or directory
 #include "tensorflow/lite/c/common.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
../../../micropython-modules/microlite/bare-metal-gc-heap.c:5:10: fatal error: sys/reent.h: No such file or directory
 #include <sys/reent.h>
          ^~~~~~~~~~~~~
compilation terminated.

The unix port is failing because its using gnu make which was modified for stm32.

I confirmed from the latest build that the unix port can be downloaded and runs ok.  I will merge the feature branch back to main soon.


[Feature] Adding tooltips in cells

Without the presentation, some categories are not super obvious. We may add tooltips in cells (ALT+D, then L, in Excel)
Something like this:

What do you think ?

I think it's relevant to detail the sub-themes addressed in each of the major themes.
But, I would think it's more relevant to add a column, to make the information more readable:

Theme
Sub-theme
Question(s)
Initial state
Desired state

Hardware Core Infra
Container Ready
Is the application containerized ready? Does it have manifests such as YAML manifests for Kubernetes?

Now the PR https://github.com/frkim/ApplicationAssessment/pull/4 is merged, I propose you to add your column Question(s) (in the file src/Application Assessment.md) detailing the sub-themes subjects. And maybe renaming the other columns like described on https://github.com/frkim/ApplicationAssessment/issues/2#issuecomment-1367974202?

agree


apply OS label style to H4 in addition to H3

These styles regressed when we updated the styleguide and docs to use H4-level headings for things like Events and Instance Methods.

👀  @kevinsawicki

👍 Looks good, thanks for fixing this 👍


ThemeStyle auto not detecting dark mode?

Describe the bug
With the most recent update https://github.com/victoriadrake/hugo-theme-introduction/commit/2932037152a30e5542e947122ece0a26f148091b, themeStyle set to auto doesn't detect dark mode on my computer anymore.
To Reproduce
Steps to reproduce the behavior:

Use the included exampleSite
Make sure computer dark mode is on (MacOS 10.15.7)
Theme is light, not dark

Expected behavior
Theme should match computer dark mode.
Desktop (please complete the following information):

OS: MACOS 10.15.7
Browser: Chrome, Edge

Thank you Linh! Pushed a fix.

Thank you Linh! Pushed a fix.

Thanks for the quick fix! I don't quite get it either, why the "drier" code doesn't work—if you ever find out, please let me know!
One thing though, the Github Actions tests didn't seem to pass?

Thanks for the quick fix! I don't quite get it either, why the "drier" code doesn't work—if you ever find out, please let me know!
One thing though, the Github Actions tests didn't seem to pass?

I noticed, even though it builds fine locally... 🤷 sorting that out now

I noticed, even though it builds fine locally... 🤷 sorting that out now

Seems to be coming from Bulma. I wonder if it's something that would be fixed by the update you started in #274?
https://github.com/victoriadrake/hugo-theme-introduction/runs/1633601928?check_suite_focus=true#step:6:7

Seems to be coming from Bulma. I wonder if it's something that would be fixed by the update you started in #274?
https://github.com/victoriadrake/hugo-theme-introduction/runs/1633601928?check_suite_focus=true#step:6:7

I doubt it. The bulma upgrade would just be from 0.9.0 to 0.9.1 and the changelog doesn't indicate anything likely to help.

I doubt it. The bulma upgrade would just be from 0.9.0 to 0.9.1 and the changelog doesn't indicate anything likely to help.

I have the problem the other way round: I did setup the light mode and whilst MS Edge is following, Chrome / Safari are not.


[BUG] VST display

My (open source) DAW of choice is BespokeSynth,  and using NeuralAmpModelerPlugin VST the interface looks like this

...which is a shame because it's probably a dead easy fix. M2 Mac (Ventura) and also an ole mac with Monterey on.
Thank you...
p.s the buttons still work at the "correct" position, it's just the graphic that is half-sized. Thanks.

this seems to be a bug with the JUCE VST3 hosting used by bespoke synth... so better to report the issue to the author of either Bespoke of JUCE.

Ah thanks. I have.

Thanks, Oli!
Closing for now; feel free to open if there's an action item over here.


License ?

Hello, under what license is this project released under ? Thank-you.

It is now under the MIT license. I just added a LICENSE file.


WIP: feat(sonar): Enable sonar during master builds

Requires https://gitlab.cee.redhat.com/dtsd/housekeeping/issues/1547


Develop 1.8.2

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@e0f038e). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff             @@
##             develop    #2115   +/-   ##
==========================================
  Coverage           ?   66.21%
  Complexity         ?     2243
==========================================
  Files              ?      890
  Lines              ?    29305
  Branches           ?     3660
==========================================
  Hits               ?    19403
  Misses             ?     8410
  Partials           ?     1492

Impacted Files
Coverage Δ
Complexity Δ

.../src/main/java/uk/gov/gchq/gaffer/graph/Graph.java
60.27% <100%> (ø)
0 <0> (?)

Continue to review full report at Codecov.

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


Turn on logging

Hi all,
So I've got Gitbucket (gitbucket.war) running on IIS with Jetty 8. I've turned on Jetty logging, but I cannot find any information how to log stuff from GiBucket. What am I missing?
Thanks

GitBucket uses LogBack via SLF4J and outputs all logs to stdout in default.
You can give LogBack configuration from outside of GitBucket.
See details about LogBack configuration at: http://logback.qos.ch/manual/configuration.html
But unfortunately, I don't know how to give arguments to the application on Jetty8 on IIS.

Thanks for the response @takezoe , I will look into this.


Minor: Split physical_plan/parquet/mod.rs into smaller modules

Which issue does this PR close?
Part of https://github.com/apache/datafusion/issues/9929
Rationale for this change
While working on #9929 I am finding the code in the mod.rs file to be a bit hard to follow. I think it would be easier to understand if it was broken up into smaller files
What changes are included in this PR?

Split physical_plan/parquet/mod.rs into smaller modules

Are these changes tested?
Existing CI
Are there any user-facing changes?
No, all structs are re-exported as ndded

@Ted-Jiang  or @waynexia  I wonder if you would have time for what is hopefully a quick review?

Thank you very much for the careful review @waynexia


Archivista Guide

This issue is about creating the initial Archivista Guide.
We should keep the README.md more for developers and contributors
We should provide the user with clear information about the following (not limited to).

What is Archivista
How to deploy Archivista
How to configure the Archivista
How to use Archivista

Parent issue

[ ] #108

Some initial suggestions

We should maintain the documentation as a code
We should provide information focused on the audience of Arquivista, from IT Architects to DevOps and DevSecOps.

Hey 👋
Interesting that you take the perspective of keeping the README strictly for developers and contributors.
For me at least, having some simple user Quick Starts / getting going guides in the README (as long as they're short), is a very useful thing. When I want to start using a project, the Github README is actually the first place I go (e.g., https://github.com/anchore/syft and https://github.com/sigstore/cosign both have quick getting started guides).
It would be good to synchronise the discussions on this between https://github.com/in-toto/archivista and https://github.com/in-toto/witness, so the experience is the same 😄 and also not a duplicated effort

I would like to assist with this issue. I believe it would be beneficial to keep the README.md file focused on developers and contributors, while creating a separate file for users. Consolidating all information into a single document might overwhelm users and diminish their experience. Though, the README.md file could have a reference to the user doc e.g. USER-GUIDE.md.


allowing user to modify chrome options.

This feature is already supported in the lasted version 2.3.2


ionic build ios in windows does not update the files in the platforms/ios folder.

Short description of the problem:
When Building for IOS with ionic build ios, the modified files of the build are not copied again into platforms/ios, in Windows 10
What behavior are you expecting?
That they are updated.
Steps to reproduce:

ionic start myapp --v2
ionic platform add ios
ionic build ios
Test the platform (with a Mac). Ok. It works.
Modify something in your project
ionic build ios
Boom. No files updated.

insert any relevant code between the above and below backticks

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Which Ionic Version? 2.x
Run ionic info from terminal/cmd prompt: (paste output below)
Your system information:
Cordova CLI: 6.4.0
Gulp version:  CLI version 3.9.1
Gulp local:
Ionic Framework Version: 2.0.0-rc.1
Ionic CLI Version: 2.1.4
Ionic App Lib Version: 2.1.2
Ionic App Scripts Version: 0.0.39
OS: WINDOWS 10
Node Version: v6.4.0

This issue was moved to driftyco/ionic-cli#1626


How to add custom webpack alias ?

How to add custom webpack alias using "preact.config.js" ?

https://ant.design/docs/react/use-with-create-react-app
I dont know how to add config to modify less-loader ? pleace help me

@cuduy197
To add a alias you need to create a preact.config.js and do something like this:
export default (config, env, helpers) => {
  const alias =  config.resolve.alias;

  alias['your-alias'] = 'pathtoyourFile.js';
};

@SaraVieira  Thanks you 👍 , how can i config less-loader ?

Trying to check that now :)

Here you go man
export default (config, env, helpers) => {
  const loaders = config.module.loaders;
  const lessloader = helpers
    .getLoadersByName(config, 'proxy-loader')
    .filter(loader => loader.loader.options.loader === 'less-loader')[0].loader
    .options;

  lessloader.options['youroption'] = 'stuff';
};

Just place that after all in the first one and you can change both :)

@SaraVieira  WOW, Thanks you alot <3

@cuduy197 Worked fine ? :)

Yeah 😄

Awesome !
@reznord @developit can you guys close this issue ? :)

Thanks @SaraVieira


[Docs] Update all documentation

I need complete documentation of current features before proceeding with a release.

Moved to Jira


Grammar and types in JavaScript

Learn about Grammar and types in JavaScript and implement a sample programs based on your understanding.

Explored Grammar and types in JavaScript and implemented the sample script.

I gone through the Grammar and types in JavaScript and implemented the sample script.

I gone through the Grammar and types in JavaScript and implemented the sample script


Haxe template

Based on http://old.haxe.org/doc/cross/template
@Merelleya Can you double check grammar/spelling? :+1:
Would it also be an idea to mention other template libs?

Maybe a lazy suggestion but cant we replace \t with \s\s?

We could but it's nicer to see the actual print margin (80) in the editor directly.

ok ok ok :smile:

I thought this was reviewed already. @markknol: Could you send another PR with the fixes?

Ah I thought I did a near-perfect job.. :stuck_out_tongue_winking_eye: Oh well..
Yes, Ill PR soon :+1:

I'm so sorry...I just didn't get around to it >.<


sensei does not run the spec with -XUnicodeSyntax enabled

With that extenstion being on, GHC likes to show ∷ in place of :: in type signatures;  normalizeTypeSignatures is woefully unprepared for that, which results in hasSpec returning False.
:frowning:

Damn, I think the right thing would really be to make sure that ~/.ghci is not read.  But we still want ./.ghci, and there is no way to tell ghci to do exactly that.


Has anyone got this working in LibreELEC?

Anyone using Plexdrive with LibreElec?

If you "outsource" the mongodb database, I don't see why it wouldn't work with the default linux-amd64 build.


Activity feed

Show recent sales.
Turn gallery mode to show recent first ones?

I guess, its done, perfect work @vikiival


Get keyboard Height on mobile devices

Hello is there a way to get keyboard height on mobile devices to adjust ui above keyboard


Base analysis layer endpoint

Analysis base model required attributes: id: UUID, visualization_id: UUID, params: JSON.
Endpoint: /api/v3/viz/:visualization_id/analysis(/:id).
JSON format example:
{
  id: ‘a1’,
  type: ‘trade-area’,
  params: {
    id: ‘a0’,
    type: 'source',
    params: {
      query: 'select * from subway_stops'
    }
}

cc @viddo @gfiorav @javitonino @xavijam

@viddo I'm adding an analysis.id UUID surrogate column as usual for convenience. The :id in the url will accept both that "internal" UUID and the first level params.id. Does it sound ok for you?

If I understand you correctly you mean first level id" (not what's inside params), right? I.e. /api/v3/viz/:visualization_id/analysis/a1 and /api/v3/viz/:visualization_id/analysis/generated-uuid-for-a1 would yield the same result?

No with "first level id" I meant "first level id _inside the json". Since analysis is scoped to the visualization, it's enough, and I guess you'll use it as a "natural id".

PD: and yes, those urls will return the same result.

:ok: :+1:


[REQUEST] Compatibility with Thingamajigs' LockableDoor functionality

Currently, Dramatic Doors is incompatible with the mod Thingamajigs (causes exit code -1, and disabling waterlogging doesn't help). The mod owner of Thingamajigs has determined that the incompatibility is specifically due to this mixin conflicting with Thingamajig's LockableDoor functionality (see discussion here):
https://github.com/Kitteh6660/DramaticDoors/blob/1.20.1-quifabrge/forge/src/main/java/com/fizzware/dramaticdoors/forge/mixin/DoorBlockMixin.java
Is there any possibility of a patch to allow the two to work alongside each other? No worries if not, I just thought I'd bring it up as a suggestion! :)

Thank you!
You'll never guess what though...I double checked and saw that I was using version 3.1.3_2 of Dramatic Doors for 1.20.1 (released on 3 November). After your comment, I decided to try v3.1.5 which was released just a couple of weeks later...and lo and behold, no more crash with Thingamajigs! Apologies, I have to admit I feel a little silly for not having tried the slightly newer version of your mod, lol. I still have the config set so that waterlogging is false, and I imagine it may crash again if I changed that, but yeah, I'm happy with this solution so I'll close this one up. 👍


Delete requirements.txt

We don't use this anywhere (the ones we actually care about are in /requirements), so we can safely nuke it

Codecov Report

Merging #922 (8ef61f5) into main (540c7a9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #922   +/-   ##
=======================================
  Coverage   88.30%   88.30%
=======================================
  Files          35       35
  Lines        1394     1394
  Branches       51       51
=======================================
  Hits         1231     1231
  Misses        147      147
  Partials       16       16

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


badIndex in Native/Json.js defined twice

The function badIndex is defined twice in the file Native/Json.js:
line 166
line 176
The definitions are identical.
This isn't a problem for JavaScript, but causes Closure Compiler to barf:
JSC_BLOCK_SCOPED_DECL_MULTIPLY_DECLARED_ERROR: Duplicate let / const / class / function declaration in the same scope is not allowed. at line 6664 character 9
function badIndex(index, nestedProblems)

It is cool that this bug has been fixed for Elm 0.19, but there are a lot of people still using Elm 0.18 because 0.19 has not been released yet! Is there a process for backporting the fix to the 5.1 version of this library (I will do all the work)? Looking at the git history, it does not look like release branches are being used, is there opposition to creating one from the 5.1.1 tag? I could then cherry pick the badIndex fix onto it, and a member could release a 5.1.2 bugfix for all Elm users in ~5 minutes.


feature: Capability to use commits, PRs, or tags instead of branches to build from

The current structure of the building repositories takes only a branch argument. Other determinant arguments are valuable for various workflow situations, e.g. using the "last good SHA" in a branch build failure scenario.
I would like to contribute a non-breaking update where branch behavior is default, but optional arguments can override the default branch.

The import statement already supports pointing to a specific tag since branch is the same as the git clone --branch option (see here). Allowing any commit or a PR number would require some code changes.

You're right, I wrote my issue title clumsily! I meant that it would be good to have options between the four; I'll tweak the issue.
What kinds of changes in this vein would you welcome? I'd obviously like to avoid heavy restructures wherever possible and don't want to change the repo against your vision, but having a fallback SHA would be really valuable for my project. I was thinking about adding an optional commit arg, for example, which would be leveraged to checkout the SHA in sparse_clone.sh. (I included PR as well for this issue, primarily for the sake of completeness, but could break that out.) Would this be feasible?


enable linter for module.ts

I had to force push. I added dom as the library to tsconfig to enable types for URL. This come with a caveat (or a benefit depending on your pov.), where webcrypto types are also implemented.