Must use import to load ES Module: swiper.esm.js

Platform

JavaScript

Author or host
Yes
Version of SDK
"adaptive-expressions": "^4.19.1",
"adaptivecards": "^2.11.2",
"adaptivecards-templating": "^2.3.1",
"swiper": "^9.0.5"

Issue
I am trying for adaptivecards templates to work consistently and I get really strange issues with some cards. So I just tried to make a very simple js script to test different templates with data. Unfortunately I get problems with carousel.js trying to use swiper which for some reason I had to add manually.
internal/process/esm_loader.js:74
internalBinding('errors').triggerUncaughtException(
^
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: = ./adaptivetemplating/node_modules/swiper/swiper.esm.js
require() of ES modules is not supported.
require() of ./adaptivetemplating/node_modules/swiper/swiper.esm.js from ./adaptivetemplating/node_modules/adaptivecards/lib/carousel.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename swiper.esm.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from ./adaptivetemplating/node_modules/swiper/package.json.
at new NodeError (internal/errors.js:322:7)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1131:13)
at Module.load (internal/modules/cjs/loader.js:979:32)
at Function.Module._load (internal/modules/cjs/loader.js:819:12)
at Module.require (internal/modules/cjs/loader.js:1003:19)
at require (internal/modules/cjs/helpers.js:107:18)
at Object.<anonymous> (./adaptivetemplating/node_modules/adaptivecards/lib/carousel.js:42:16)
at Module._compile (internal/modules/cjs/loader.js:1114:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
at Module.load (internal/modules/cjs/loader.js:979:32) {

code: 'ERR_REQUIRE_ESM'
}
The code is simple and although not fully tested always gives the swiper error:
import * as ACData from "adaptivecards-templating";
import * as Adaptive from "adaptivecards";
var fs = require("fs");
console.log("template:",process.argv[2])
console.log("data:",process.argv[3])
const cardtemplate = fs.readFileSync(process.argv[2]);
const carddata  = fs.readFileSync(process.argv[3]);
var adaptiveCard = new Adaptive.AdaptiveCard();
var template = new ACData.Template(cardtemplate);
console.log("ctemplate:",template)
var context = {
}
context.$root = JSON.parse(carddata);
var cardPayload = template.expand(context);
console.log("card2:",cardPayload)
adaptiveCard.parse(cardPayload);
console.log(adaptiveCard.render());
A general comment on the actual usage of Adaptive Cards Templates [which I got working in a browser but not consistently takes all example files] is the
var context: ACData.IEvaluationContext = {
$root = {
"name": "Adaptive Cards"
}
};
where ACData.IEvaluationContext is not easy to get to work on javascript / nodejs / typescript.
It would be easier to have a ACData.Context(somejson)?

I have the exactly same problem :(

+1 also encountered this issue. Thanks for the workaround.

I'm facing a similar issue while running jest unit tests when using "adaptivecards": 2.11.2 version. Error is:
/node_modules/swiper/swiper.esm.js:13
    export { default as Swiper, default } from './core/core.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1350:14)
      at Object.<anonymous> (node_modules/adaptivecards/src/carousel.ts:26:1)

It works when we downgrades the version to 2.11.1 as suggested above but is there any fix coming up for latest version? Or is there any code workaround we can do while using latest?

@jwoo-msft any updates on this?

@jwoo-msft @anna-dingler,
I was also getting similar error while running jest unit tests when using "adaptivecards": 2.11.2 version. So I have degraded and using below versions, and jest seems to work fine, But I am noticing issues with drag and drop feature. Getting below attached error, do we have any solution for that.
    "adaptive-expressions": "4.19.3",
    "adaptivecards": "2.11.1",
    "adaptivecards-designer": "2.4.3",
    "adaptivecards-templating": "2.3.1",

@jwoo-msft @anna-dingler, @proxy-hatch @MUCZ I was also getting similar error while running jest unit tests when using "adaptivecards": 2.11.2 version. So I have degraded and using below versions, and jest seems to work fine, But I am noticing issues with drag and drop feature. Getting below attached error, do we have any solution for that.
    "adaptive-expressions": "4.19.3",
    "adaptivecards": "2.11.1",
    "adaptivecards-designer": "2.4.3",
    "adaptivecards-templating": "2.3.1",

These versions are compatible ? When we have downgraded the adaptivecards version, should we downgrade the versions for other packages as well. Please confirm. Thanks..

@anna-dingler, @jwoo-msft Could you please suggest something.. Thanks..

Hi @Neeraj-swarnkar,
I don't have a direct solution to this problem. The issue stems from swiper because it is an ES module. I created an issue related to this for our unit test project that includes some resources: https://github.com/microsoft/AdaptiveCards/issues/7983
I believe there should be some options for configuring your project to allow ES modules. Downgrading swiper to version 6 would also solve this.
I will speak with @jwoo-msft about bandwidth for this issue - thanks!

Hi @Neeraj-swarnkar,
I don't have a direct solution to this problem. The issue stems from swiper because it is an ES module. I created an issue related to this for our unit test project that includes some resources: #7983
I believe there should be some options for configuring your project to allow ES modules. Downgrading swiper to version 6 would also solve this.
I will speak with @jwoo-msft about bandwidth for this issue - thanks!

Thanks @anna-dingler, UT issue is not coming with the swiper version 6.8.1.

The Swiper module we are currently dependent on only supports ESM (ECMAScript modules). To address this issue, you'll need to update your environment and source code to accommodate ESM modules.
This will be the quickest solution to the problem at hand. Meanwhile, we are working on an alternate resolution for developers who aren't yet able to utilize ESM. We plan to internally integrate Swiper into the AdaptiveCards and implement tree shaking.
As a result, developers will no longer need to directly depend on Swiper. However, this process will take some time. Therefore, we strongly recommend updating your environment and source code to support ESM in the interim.

Unfortunately that's not really a viable solution for everyone. For my use-case I'm only using the library for card-generation, and with this development I'm leaning more towards abandoning the library entirely and making a proprietary JSON generation utility 😶
Will stay subscribed in the hopes for some pivot from this stance..

any news?

Hey @jwoo-msft, @anna-dingler
Any news on this?

I believe the core of the problem is how the library is being packaged as a commonjs package via webpack that is referencing swiper using require. You can look at the published library built output at node_modules/adaptivecards/lib/carousel.js
var card_elements_1 = require("./card-elements");
var Enums = require("./enums");
var serialization_1 = require("./serialization");
var registry_1 = require("./registry");
var enums_1 = require("./enums");
var strings_1 = require("./strings");
var swiper_1 = require("swiper");
var Utils = require("./utils");
var shared_1 = require("./shared");

There isn't much that any consuming application will be able to do to solve this. This is something that needs to be solved by the package owner.
One solution consumers can use is to use the package.json overrides property to downgrade swiper to ^6, you can do this with the following snippet added to your package.json.
{
  "dependencies": {
    "adaptivecards": "^3.0.2"
    // other dependencies
  },
  "overrides": {
      "adaptivecards": {
          "swiper": "^6.0.0"
      }
  }
}


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit df8715d:
:clock10: Pending: waiting for processors (26 builds ahead of you)
:warning: Docs Build is busy, currently there are 26 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit df8715d:
:clock10: Full build: the average full build time is 7 min(s) 23 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit df8715d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


set correct valid fee range from 0 to 50

https://app.clubhouse.io/augur/story/11333/creating-markets-allows-user-to-specify-50-fee-causing-market-creation-failure

Coverage remained the same at 66.502% when pulling a07741f89f7923ab748758ea1933678e9a636fff on tomhaile/ch11333/creating-markets-allows-user-to-specify-50 into 59cb784aa5ae747864d819e77361c0e7a8ec5536 on master.


It can't support  "nan", "inf", "-inf" for float type

Description
when use PCL library, I need write some data to json.
my code is some like:
"write special float value to json file":
float userFilterValue = std::numeric_limits<float>::quiet_NaN();
nlohmann::ordered_json ser;
ser["userFilterValue“] = userFilterValue;
std::ofstream("test.json") << ser.dump(2);

"read special float value to json file":
float userFilterValue2 = 0;
nlohmann::ordered_json ser2;
std::ifstream("test.json") >> ser2;
userFilterValue2 = (float) ser["userFilterValue“];

I found that the "test.json" file data:
{
 "userFilterValue": null
}

Reproduction steps
I just want to serialize some  special float value, such as "nan", "inf", "-inf"
but it throws exception wiht tips "type must be number, but is null"
Expected vs. actual results
when I write "nan", "inf" as float value, but it got "null"
Minimal code example
float userFilterValue = std::numeric_limits<float>::quiet_NaN();
nlohmann::ordered_json ser;
ser["userFilterValue“] = userFilterValue;
std::ofstream("test.json") << ser.dump(2);

nlohmann::ordered_json ser2;
std::ifstream("test.json") >> ser2;
float userFilterValue2 = (float) ser["userFilterValue“];

Error messages
type must be number, but is null

Compiler and operating system
visual studio 2019
Library version
3.10.4
Validation

[ ] The bug also occurs if the latest version from the develop branch is used.
[ ] I can successfully compile and run the unit tests.

This is expected behavior, see https://json.nlohmann.me/features/types/number_handling/.


DoS attack doesn't work. Cowrie does not crash!

Hey @RudareanuLeonard, I want to better understand the situation, could you please provide some additional details?

Hey @RudareanuLeonard, I want to better understand the situation, could you please provide some additional details like logs? Is the DoS attack not connecting to your Cowire docker instance?

It connects, it send packages,  but I can still connect to the honeypot after the attack end. And it shouldn't be possible... I could provide a video if needed.

Anyone? @Swangeon @adepasquale @glaslos @stricaud

It would be great if you could provide the command you are running.

 What is your base OS?
I am using a MacOS host and I run cowrie from a terminal window like this:
docker run -p 2222:2222/tcp cowrie/cowrie
more information here https://hub.docker.com/r/cowrie/cowrie.
Get the latest version of honeyscanner and try again.
If the problem persists there might be an issue with the paramiko library on your system. Try various fixes in order to understand where the problem is, is it on honeyscanner, or is it on the honeypot running on the docker?
Best of luck!


Fixed missing argument in SettingsProvider

not all items in the Mixed Reality Toolkit menue have been there as shown in the How-To: https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/GettingStartedWithTheMRTK.html#4-configure-your-first-mixed-reality-toolkit-scene

 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: frankotastico sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for contributing!
Quick note - our mrtk_release branch is somewhat of a 'golden' current release branch - we don't usually merge things directly in there unless it's doc changes.
Can you please retarget this change at the mrtk_development branch?


.babelrc ignored in Storybook HTML?

I'm trying out Storybook HTML with hyperHTML-Element. To make sure Babel will be able to transpile Custom Elements correctly I need to load a couple of plugins.
I've added a .babelrc file in the root (I tried the .strorybook folder as well) but it seems to be ignored.
Here the versions of my devDependencies:
"devDependencies": {
    "@storybook/html": "^4.0.0-alpha.14",
    "babel-core": "^6.26.3",
    "babel-plugin-transform-builtin-classes": "^0.6.1",
    "babel-plugin-transform-es2015-classes": "^6.24.1",
    "babel-runtime": "^6.26.0"
  }

Do you have a reproduction repo?

Here we go: https://github.com/Granze/test-storybook

I am seeing this: Super expression must either be null or a function, not object error when running storybook.
That is because of this line:
const HyperHTMLElement = require('hyperhtml-element');
It should be
const HyperHTMLElement = require('hyperhtml-element').default;
or
import HyperHTMLElement from 'hyperhtml-element'
After that I am getting this error: Class constructor HyperHTMLElement cannot be invoked without 'new'
Which is already IMO related to how this framewrok should be rendered

After removing babel-plugin-transform-es2015-classes your example worked for me (in chrome).

oh, you are right. :)
Thanks for helping me!


No support for paths

I just wanted to find the shortest path between nodes, but unfortunately neo4j-core doesn't map the results in this case.
p = Person.where(email: 'me@example.com').first
p.query_as(:u).match("path=shortestPath(u-[:knows*]-(p: Person)), p-[:COMPANY]-(c: Company)").where("c.name = 'Company Inc.'").pluck(:path)

The result looks so:
[{:relationships=>["http://localhost:7474/db/data/relationship/313", "http://localhost:7474/db/data/relationship/327", "http://localhost:7474/db/data/relationship/329"], :nodes=>["http://localhost:7474/db/data/node/132", "http://localhost:7474/db/data/node/133", "http://localhost:7474/db/data/node/138", "http://localhost:7474/db/data/node/139"], :directions=>["<-", "<-", "->"], :length=>3, :start=>"http://localhost:7474/db/data/node/132", :end=>"http://localhost:7474/db/data/node/139"}]

Hrmm, I think we've seen this a couple of times.  Definitely should be fixed, thanks!

On May 11, 2015, at 09:33, Dieter Pisarewski<EMAIL_ADDRESS>wrote:
I just wanted to find the shortest path between nodes, but unfortunately neo4j-core doesn't map the results in this case.
p = Person.where(email: 'me@example.com').first
p.query_as(:u).match("path=shortestPath(u-[:knows*]-(p: Person)), p-[:COMPANY]-(c: Company)").where("c.name = 'Company Inc.'").pluck(:path)
The result looks so:
[{:relationships=>["http://localhost:7474/db/data/relationship/313", "http://localhost:7474/db/data/relationship/327", "http://localhost:7474/db/data/relationship/329"], :nodes=>["http://localhost:7474/db/data/node/132", "http://localhost:7474/db/data/node/133", "http://localhost:7474/db/data/node/138", "http://localhost:7474/db/data/node/139"], :directions=>["<-", "<-", "->"], :length=>3, :start=>"http://localhost:7474/db/data/node/132", :end=>"http://localhost:7474/db/data/node/139"}]
—
Reply to this email directly or view it on GitHub.

It can use NODES(path) to get all nodes from the path. I'm curious if it's better to implement a Path class which could return nodes or relationships.

Yeah, I think that makes a lot of sense

On May 11, 2015, at 09:47, Dieter Pisarewski<EMAIL_ADDRESS>wrote:
It can use NODES(path) to get all nodes from the path. I'm curious if it's better to implement a Path class which could return nodes or relationships.
—
Reply to this email directly or view it on GitHub.

I imagine this class could also have "nodes" and "rels" methods which return just the nodes and the relationship object.  Also it would be good if at least some of the code was shared between server and embedded modes.  I'm currently re-implementing some functionality in embedded because I had implemented it in the server mode but didn't think about the embedded side.

I like the idea of a Path class. @dpisarewski, what kind of behavior would you expect from it? At the least, I think we can expose each of the keys that every response provides as methods. Does it immediately load the linked nodes/rels or do they just return the IDs? Does it have an enumerator built in that lets you loop through the entire path?

One thing to also note is the resultDataContents key for transactional statements (see: http://neo4j.com/docs/stable/rest-api-transactional.html ).  We specify "row" and "REST" to get the full data out of nodes and relationships.  Maybe playing with this will yield more data for paths

@subvertallchris, @cheerfulstoic Yes, I would expect methods like node, rels which return nodes and relationships, and each method which will iterate over nodes and relationships together, so I would get them all by calling to_a. I guess, it could load them immediately since I can't imagine a use case with a very long path where this could be an issue.

I've been building a new CypherSession API in the cypher_session_reboot branch.  It's a much simpler set of modules/classes dedicated to making just cypher queries via either HTTP or Embedded (and eventually the new protocol, Bolt).  This implementation has a Path object, though the nodes/relationships, unfortunately, aren't fully populated because Neo4j doesn't give us all that data

...at least for the REST API.  Embedded might be a different story


Add non-x86 support

If you rebase against master the travis issue with pip should be resolved!

Fixed!

Thanks!


FIX: fix runtime warning in RAPS

Fix runtime warning using RAPS. The problem was due to the use to a np.inf which was multiplied by a boolean, return a nan value. By correcting this error, the result of a test changed (as it led to an unseen error for computation of RAPS)

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (2d7fecb) 99.85% compared to head (a9ef792) 99.85%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #292   +/-   ##
=======================================
  Coverage   99.85%   99.85%
=======================================
  Files          28       28
  Lines        3339     3340    +1
  Branches      346      346
=======================================
+ Hits         3334     3335    +1
  Misses          4        4
  Partials        1        1

Impacted Files
Coverage Δ

mapie/classification.py
99.23% <100.00%> (+<0.01%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


add tag statistics notebook

This adds a notebook for visualizing tag statistics - this might be useful for #99 . We can for example see that a tag "NFDI4BioImage" exists 20 times, and those exist too:
NFDI4BIOIMAGE: 1
NFDI4Bioimage: 1
nfdi4bioimage: 1
Hence, forcing all tags lower case could be a solution for example.

after the Data cleaning, this should be finished

after the Data cleaning, this should be finished

If something is not finished, I would have prefered to not merging it ;-)
I will create a github issue for this so that we don't forget this.


[border-agent] connection timeout with ephemeral key

This commit enhances how connection timeouts are applied when using an ephemeral key. If the timeout expires while a commissioner or commissioner candidate is connected, the session will be terminated. The Border Agent (BA) will then stop using the ephemeral key and revert to using PSKc.
The ephemeral key timeout timer starts when the ephemeral key is set on the BA. During this timeout interval, the ephemeral key can be used only once by an external commissioner to establish a secure connection. The ephemeral key timeout cannot be extended by the commissioner sending keep-alive messages (COMM_KA.req).
Regardless of whether the connection uses an ephemeral key or PSKc, the general timeout mechanism, using TIMEOUT_COMM_PET (50 seconds) to disconnect from stale sessions, still applies and remains unchanged. This 50-second timeout can still be extended by the commissioner sending keep-alive messages.

Related to SPEC-1310

(review in progress: raised a question on SPEC-1310 for relation to spec)

The PR has been updated with the following changes:

Rebased on the main branch, (conflicts have been resolved).
The commit message now includes more details about the ephemeral key timeout behavior.
A note has been added to clarify that the ephemeral key timeout is applied in addition to the general connection timeout.

mTimer (50s) is started when connected, the connection will forcibly close when HandleTimeout, and the session time for using epskc is not respected if longer

the const lifetime for secure session established with epskc should be different from the timeout for epskc code which is the valid period that it can be used to establish DTLS session.

@librasungirl, I believe this implementation aligns with the latest discussions in SPEC-1310. The concept is straightforward: start the e-PSKc timeout when e-PSK is set. When it expires, stop using e-PSK, and close any existing connection. We maintain all other connection timeout mechanisms unchanged (regardless of whether PSKc or an ephemeral key is used).
We had extensive discussion on this in the recent Thread TC call (IMHO, frankly more than what this topic deserves).

A bit related but beyond this PR, for external candidate established DTLS session with pskc, if it doesn't attempt to petition, its session will be forcibly closed after 50s with current implementation as there are no keep-alive mechanism, which should be discussed.

This is existing behavior implemented by OT, and I assume/expect it to be the intended behavior in the spec as well. Feel free to file a JIRA ticket if you think it needs clarification or changes.

@abtink @librasungirl I agree that the proposed code change now matches the discussion on SPEC-1310 we had. Using the same 50 sec timeout (regardless of credential type) keeps the code simple and also helps to limit the ePSKc session to its purpose. For the ePSKc case, there is on purpose no way to extend the session lifetime, based on that discussion.

This is existing behavior implemented by OT, and I assume/expect it to be the intended behavior in the spec as well. Feel free to file a JIRA ticket if you think it needs clarification or changes.

Yes, for the PSKc case, we have today only "becoming Commissioner" as the one way to be able to extend the session lifetime with keepalives. Other keepalive use cases (e.g. for a monitoring agent that connects to read diagnostic data only during multiple days) should be separately discussed in related SPEC JIRAs.  Because we haven't approved any use cases yet of staying connected and not becoming the Commissioner, the best thing to do for now is close the connection relatively quickly to give others a chance to connect.  I can imagine new functions here also like requesting a long-lived diagnostics monitoring session and staying connected, while the BA enables then a second device to connect again to become Commissioner.

After second thought, I think it might still be valuable to directly callout the DTLS session can't be extended by the candidate once established, along with the EphemeralKey APIs as the suggestions.

@librasungirl as I mentioned above, this does not seem to be what the BA implementation does today. Candidate can extend the timeout by sending Keep Alive. There is no check here:
https://github.com/openthread/openthread/blob/d015004a74d8386f74894783c7e662c8d892e73e/src/core/meshcop/border_agent.cpp#L493-L503

@librasungirl as I mentioned above, this does not seem to be what the BA implementation does today. Candidate can extend the timeout by sending Keep Alive. There is no check here:

@abtink There is nothing in the existing spec text (prior to SPEC-1310) about keepalive for the DTLS connection. Then an implementation could either do as OT does now (favors robustness) or alternatively only reset the time if the LEAD_PET.rsp gets back from the Leader with an "ok"/accepted status (favors security).
In the new proposed text it says the BA MUST NOT extend the DTLS session lifetime based on a keepalive sent by the Candidate. So we could soften this text (given that the total session is anyhow limited to 10 minutes), or else start a new PR later on to address this aspect.


TensorRT-LLM backend bump to latest version + misc fixes

This PR bumps some dependencies related to TensorRT-LLM alongside rebasing Docker container against ubuntu24.04 instead of ubuntu22.04.
To support this, we need to use latest TensorRT-LLM main due to a missing import in one of the file on Nvidia side leading to gcc failure for gcc > 12 (more info here).
It also reimplement the backbone of the backend for simplicity and alow easier testing which is actively WIP as for now but will land in its own PR as it will involve some additional changes on GA side.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


New RNA-seq tutorial: de novo transcriptome reconstruction

Mo and I have put together a tutorial for de novo reconstruction of a transcriptome from RNA-seq data with a reference genome for alignment. The data used in this tutorial are from the same study we used for the ChIP-seq tutorial, so the tutorials are complementary. We are still working on slides and a Dockerfile, but the major tutorial items are ready. Please let us know if we're missing anything from the tutorial or metadata files.

This satisfies issue #197 so feel free to close that issue if this gets merged.

@bgruening I have double-checked the images and we had replaced 2 of them accidentally for the ref_based tutorial (DESeq2_PCA.png and DESeq2_heatmap.png). I have returned the original images, renamed the images for the de_novo tutorial (DESeq2_PCAplot.png and DESeq2_heatmap_G1E_mega.png), and everything looks good to me. Note that I believe the PCA and heatmap for the ref_based tutorial is no longer embedded in the current ref_bsed.md file, but they are embedded correctly in our older version of ref_based.md.

@malloryfreeberg There are a few broken links to zenodo, can you please check that. Otherwise, I'm fine with merging! Thanks a lot!

Nice! Great work @malloryfreeberg and @MoHeydarian!


Example usd-materialx files

This PR introduces a few simple usd files that use MaterialX
Example 1: Basic
Use a built-in USD Sphere with usd_preview_surface_plastic.mtlx
Example 2: Basic Textured with variants
Use a teapot model referring 2 MaterialX files usd_preview_surface_plastic.mtlx and standard_surface_brass_tiled.mtlx
Also see readme for details.

Double checking, where's the teapot from? Do we have the rights to have it in here? If so, it would be useful to have it in the _common folder so that other tests can use it.

I converted the teapot from teapot.obj from MaterialX repo here
I'll move it to common, if we can reuse.

Do you have screenshots of all files you can add to the readme?


[Feature] Ability to show upcoming

The ability to show upcoming track.

I hadn't notices that pianobar had a -u command.  If I can (or anyone else) this would be nice.  It is most all Javascript which I've only dabbled at but we will see..

Yes, it displays the next two Tracks.

@bonelifer Yes, I just did an experiment.  However to get this information one would have to be screen-scraping the output of pianobar and I don't think Patiobar is doing that.  I think thy do as my mqtt interface does and passes keystrokes and watches the config for the four files of information kept there.  I haven't done screen scraping since the 80s but it is possible.  One would I presume have to run pianobar inside a shell or pipe the output to a program.

I may add a feature request to pianobar's repo.

I just had a brain flash.  I will try it but one should be able to use pianobar > myprog.py and have myprog.py either

write to a ,config file as pianobar does, over writing previous send a mosquitto message of the new line from Pianobar.  Then any other person's app could read line.  I fear returns from pianobar that are multi-line might be missed so...
Send a mosquitto message of the line than anyone else's app could process that line.  One could also monitor that mqtt for one of Pianobar's failures to connect errors

Ok, quick and dirty check on feasibility shows the added benefit of mqtt as it will chirp once a second showing the time remaining on the song:
`import subprocess.
Define your command (e.g., 'ls' to list files)
my_cmd = 'pianobar'
Run the command and capture the output in real time
with subprocess.Popen(my_cmd, shell=True, stdout=subprocess.PIPE, text=True) as process:
for line in process.stdout:
# Process each line (for demonstration, just printing them)
print(f"Received: {line.strip()}")
`

I have the following so far.  I am going to formalize it a bit and make a repository for it.
There are probably a lot better ways to parse out the info and hints are welcome:
`import subprocess
my_cmd = 'pianobar'
with subprocess.Popen(my_cmd, shell=True, stdout=subprocess.PIPE, text=True) as process:
for line in process.stdout:
line = line[4:]
if line[0:1] == "#":
print("TIME: " + line[4:], end = "\r")
elif line[0:19] == "(i) Control fifo at":
print("*** cmd location: " + line[19:len(line) -7])
elif line[0:2] == "|>":
print("Song Info: " + line[4:])
elif line.find("0)") > -1:
print("Upcoming: " + line[2:])
elif line.find("1)") > -1 :
print("Upcoming1: " + line[2:])
elif line.find("2)") > -1 :
print("Upcoming2: " + line[2:])
else:
print(f"Received: {line[2:]}")
`

@kylejohnson  I've published my MQTT Pianobar https://github.com/Doug-Wyman/MQTT_Pianobar I hope I have given you the credit you deserve


[sharktank] Unpin numpy

This is blocked by #495, as the underlying issue on Windows was fixed was fixed with torch 2.4.1 (see https://github.com/pytorch/pytorch/issues/131668#issuecomment-2307447045).


[EventRequest] Codeunit::Price List Management, OnAfterActivateDraftLines

Hi,
Is it possible to add an event after prices are "verified"? From what I read in the base code, it seems the "Verify Lines" function ends up calling a function named "ActivateDraftLines" on Codeunit 7017 "Price List Management".
Having this event OnAfterActivateDraftLines (or OnAfterVerifyLines) would be helpful to make additional checks, or maybe, even renumbering the Sales Price Lines that eventually get clogged up if users split lines multiple times.
Thanks in advance.

Hi,
Please always put the full detailed signature of the requested events and the parameters passed in the call.
You help us implementing the requests faster when your request contains AL code copied from VSCode instead of screenshots.

Hi, Please always put the full detailed signature of the requested events and the parameters passed in the call. You help us implementing the requests faster when your request contains AL code copied from VSCode instead of screenshots.

Noted! Thanks for the info. Please see the details below:
codeunit 7017 "Price List Management"

procedure ActivateDraftLines(PriceListHeader: Record "Price List Header"): Boolean;
    var
        PriceListLine: Record "Price List Line";
    begin
        if not PriceListHeader.HasDraftLines(PriceListLine) then
            exit;

        VerifyLines(PriceListLine);
        if not ResolveDuplicatePrices(PriceListHeader) then
            exit(false);

        PriceListLine.ModifyAll(Status, "Price Status"::Active);

        OnAfterActivateDraftLines();  //<---------- NEW
        Message(AllLinesVerifiedMsg);
        exit(true);
    end;

    // NEW
    [IntegrationEvent(false, false)]
    local procedure OnAfterActivateDraftLines(var PriceListHeader: Record "Price List Header")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Add Rkyv deserialization/serialization for RPC method requests/responses

Motivation
Providing a rkyv RPC interface should offer better performance than JSON-serialization and some additional type-safety.

[rkyv](http://github.com/rkyv/rkyv) (archive) is a zero-copy deserialization framework for rust.

Request and response types can be exported from zebra-rpc so that the validity of RPC requests can be checked by rustc.
Possible Design

Add a rkyv_serialization feature to zebrad, zebra-rpc and zebra-chain

When the feature is enabled:

Add a rkyv_listen_addr field to the config
Listen for requests with hyper or axum
Map deserialized requests to RpcImpl or GetBlockTemplateRpcImpl methods
Serialize responses with rkyv
Export request/response types from zebra-rpc

Optional:

Add a subscribe-getblocktemplate method that opens a WebSocket for sending new block templates

Testing

Add  rkyv_serialization feature to CI coverage matrix
Add the new config to test configs
Snapshot tests

Benchmarks

Add benchmarks to measure performance differences for key RPC methods

@arya2 is this for Sprint 5? :) just so I can add it in if so


ISSUE-592: Security changes to enable Trusted Proxy in SPNEGO authentication

@guruchai: Can you create an issue for this?

@raju-saravanan Created the issue. Can you merge it if nothing else is pending?


chore: update cypress mock data

Description
Updates Cypress mock data to match our current array of requests.
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[x] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A - maintenance
Risk
Minimal if CI passes.
Testing
CI should pass.
Screenshots (if applicable)
N/A

Closing in favor of one atomic PR: https://github.com/shapeshift/web/pull/2383


bug: vec_multiple_sel at least has one src

Describe the bug/ 问题描述 (Mandatory / 必填)
A clear and concise description of what the bug is.

Ascend Error Message:

E40021: Failed to compile Op [Select121]. (oppath: [Compile /usr/local/Ascend/ascend-toolkit/7.0.1/opp/built-in/op_impl/ai_core/tbe/impl/select.py failed with errormsg/stack: File "/usr/local/Ascend/ascend-toolkit/latest/python/site-packages/tbe/dsl/instrinsic/cce_intrin_md.py", line 5772, in vec_multiple_sel
raise RuntimeError("vec_multiple_sel at least has one src")
RuntimeError: [EB9999] vec_multiple_sel at least has one src', 'errPcause': ' ', 'errSolution': ' '}
], optype: [Select])
Solution: See the host log for details, and then check the Python stack where the error log is reported.
TraceBack (most recent call last):
Compile op[Select121] failed, oppath[/usr/local/Ascend/ascend-toolkit/7.0.1/opp/built-in/op_impl/ai_core/tbe/impl/select.py], optype[Select], taskID[243]. Please check op's compilation error message.[FUNC:ReportBuildErrMessage][FILE:fusion_manager.cc][LINE:771]
[SubGraphOpt][Compile][ProcFailedCompTask] Thread[281460682519008] recompile single op[Select121] failed[FUNC:ProcessAllFailedCompileTasks][FILE:tbe_op_store_adapter.cc][LINE:954]
[SubGraphOpt][Compile][ParalCompOp] Thread[281460682519008] process fail task failed[FUNC:ParallelCompileOp][FILE:tbe_op_store_adapter.cc][LINE:1001]
[SubGraphOpt][Compile][CompOpOnly] CompileOp failed.[FUNC:CompileOpOnly][FILE:op_compiler.cc][LINE:1127]
[GraphOpt][FusedGraph][RunCompile] Failed to compile graph with compiler Normal mode Op Compiler[FUNC:SubGraphCompile][FILE:fe_graph_optimizer.cc][LINE:1292]
Call OptimizeFusedGraph failed, ret:-1, engine_name:AIcoreEngine, graph_name:partition0_rank1_new_sub_graph3[FUNC:OptimizeSubGraph][FILE:graph_optimize.cc][LINE:131]
subgraph 0 optimize failed[FUNC:OptimizeSubGraphWithMultiThreads][FILE:graph_manager.cc][LINE:996]
build graph failed, graph id:120, ret:-1[FUNC:BuildModelWithGraphId][FILE:ge_generator.cc][LINE:1615]
[Build][SingleOpModel]call ge interface generator.BuildSingleOpModel failed. ge result =<PHONE_NUMBER>[FUNC:ReportCallError][FILE:log_inner.cpp][LINE:161]
[Build][Op]Fail to build op model[FUNC:ReportInnerError][FILE:log_inner.cpp][LINE:145]
build op model failed, result = 500002[FUNC:ReportInnerError][FILE:log_inner.cpp][LINE:145]
(Please search "Ascend Error Message" at https://www.mindspore.cn for error code description)

Ascend Warning Message:

W11001: Op [Cast2] does not hit the high-priority operator information library, which might result in compromised performance.
W49999: If want to reuse binary file, please donwload binary file and install first![FUNC:BuildFusionOp][FILE:fusion_manager.cc][LINE:3763]
W11001: Op [ReduceSum17] does not hit the high-priority operator information library, which might result in compromised performance.
W11001: Op [Cast22] does not hit the high-priority operator information library, which might result in compromised performance.
W11001: Op [Cast31] does not hit the high-priority operator information library, which might result in compromised performance.
W11001: Op [ReduceProd117] does not hit the high-priority operator information library, which might result in compromised performance.
W11001: Op [ReduceMax119] does not hit the high-priority operator information library, which might result in compromised performance.
W49999: Compile error message is:[File "/usr/local/Ascend/ascend-toolkit/latest/python/site-packages/tbe/dsl/instrinsic/cce_intrin_md.py", line 5772, in vec_multiple_sel
raise RuntimeError("vec_multiple_sel at least has one src")
RuntimeError: [EB9999] vec_multiple_sel at least has one src', 'errPcause': ' ', 'errSolution': ' '}
].
[FUNC:ReportBuildErrMessage][FILE:fusion_manager.cc][LINE:763]
W49999: Open  failed, file is already open[FUNC:GetJsonValueFromJsonFile][FILE:fusion_util.cc][LINE:1516]

Hardware Environment(Ascend/GPU/CPU)  / 硬件环境:

Please delete the backend not involved / 请删除不涉及的后端:
/device ascend/GPU/CPU/kirin/等其他芯片
华为910b

Software Environment / 软件环境 (Mandatory / 必填):
-- MindSpore version 2.2.14
-- Python version 3.9.2
-- OS platform and distribution ubuntu 20.04

Excute Mode / 执行模式 (Mandatory / 必填)(PyNative/Graph):

Please delete the mode not involved / 请删除不涉及的模式:
/mode pynative
/mode graph

To Reproduce / 重现步骤 (Mandatory / 必填)
Steps to reproduce the behavior:
import mindspore;mindspore.set_context(device_target='Ascend');

from mindnlp.transformers import AutoTokenizer, Qwen2Config
from mindnlp.transformers import (
        Qwen2ForCausalLM,
        Qwen2ForSequenceClassification,
        Qwen2Model,
    )

EXPECTED_TEXT_COMPLETION = """My favourite condiment is 100% ketchup. I love it on everything. I’m not a big"""
prompt = "My favourite condiment is "
model_name_or_path = "/models"
tokenizer = AutoTokenizer.from_pretrained(model_name_or_path, use_fast=False)
model = Qwen2ForCausalLM.from_pretrained(model_name_or_path)
input_ids = tokenizer.encode(prompt, return_tensors="ms")

# greedy generation outputs
generated_ids = model.generate(input_ids, max_new_tokens=20, temperature=0.1)

Expected behavior / 预期结果 (Mandatory / 必填)
A clear and concise description of what you expected to happen.
模型正常推理
Screenshots/ 日志 / 截图 (Mandatory / 必填)
If applicable, add screenshots to help explain your problem.
Additional context / 备注 (Optional / 选填)
Add any other context about the problem here.

910b建议升级MindSpore2.3

cann升级8.0


feat(device-registration): migrate to GetAuthenticationMethodsForDevice endpoint

This should fix #41 .
I was able to login using an email token, as well as OTP1.
Note that the behaviour for email_token device registration seems to have changed from the previous endpoint, and we now need to explicitly request the server to send an email token.
Also, I was unable to login using OTP2. But this is repro on master. I'll try to investigate and open a bugfix.

Thanks @ni0ki, and you just put the finger on the issue #44, if OTP2 is not working that's the bug the user is having.

Seems to me OTP2 requires a concatenation of MP + ServerKey to be used for deciphering, which is not supported yet.
Also, I don't have write access to this repo, I'll let you merge this PR when you want :- )

Seems to me OTP2 requires a concatenation of MP + ServerKey to be used for deciphering, which is not supported yet. Also, I don't have write access to this repo, I'll let you merge this PR :- )

Yep, we can add support for it 👍
Oh ok i'll do it


External CSS Styling Limitation

Some things like buttons cannot be edited using traditional CSS. A manual "Theme change" on the 3rd party design website or another workaround is needed.

For everything that is related to colors, there is a theme file: twitchy-desktop-lite\src\theme\theme.js
You can define key-pair values of colors:
primary: '#6441a5',
To use it in html, just add a class like this: class="primary" and the backgrnoud color will be of the same colored you defined in the config file. If you want to apply the color to the text, use class="primary--text"
If you want to vary tones, you can use the following: class="text--{lighten|darken}-{n}" (ex: class="text--darken-3")
For more information: https://vuetifyjs.com/en/style/colors

I did some really dirty CSS workarounds. I managed to edit the buttons but the text coloring inside the textarea + labels is impossible to change.
Any suggestions?

Implemented textarea coloring workaround using CSS filters.
Menu design work is done for now. Closing.


debtRepayments, Round #s

I like how getResultAsArray() debtRepayments doesn't round the numbers... but it sometimes would be nice. So I am thinking we add another array to getresults... debtRepaymentsRounded

#6


Clean up APIs that take both SKContext and ILogger/CancellationToken

Some APIs, e.g. Plan.InvokeAsync, accept optional SKContext, ILogger, and CancellationToken instances, e.g.
public async Task<SKContext> InvokeAsync(SKContext? context = null, CompleteRequestSettings? settings = null, ILogger? log = null, CancellationToken cancellationToken = default);

but SKContext includes both an ILogger and a CancellationToken.  That means it's possible to pass in multiple loggers and multiple cancellation tokens, and as currently implemented, in some cases if the SKContext is supplied, the separately provided logger and token will be ignored, even if they're different from the ones inside of the SKContext.  That's a reliability and data loss problem if a developer was expecting their separately-supplied logger and token to be respected.
We can fix this by either:

Ensuring that if the supplied logger / token are non-default and different from the ones in the SKContext that they're also respected.  This could mean, for example, creating and passing along a new SKContext that includes a combined token / logger.
Avoiding this trap by design by ensuring you can only pass an SKContext or a logger/cancellationToken, but not both.

I'd suggest we do (2).
cc: @shawncal

@shawncal, @dluc, if you agree, once https://github.com/microsoft/semantic-kernel/pull/612 is merged I'd be happy to do this.


While Dragging widgets, some already placed widgets transgress the boundaries of a container widget they are placed in

https://www.loom.com/share/9ea942bc6790408b92a4475233bf7dc4

This issue is resolved.


Formula input: commandify

We need to make the formula input (i key) undoable. I'm thinking make the command after returning from the PolishInputWidget into the main window's slot; because in there we know we have a valid set of TreeNode's to add into the currentTree. We can make the command save which nodes were added, and undo can simply detach them again.
The issue I see is with repeat() - the command should probably copy the nodes it gets from the PolishInputWidget and not just move directly. Without this, repeat() would try and move the same nodes as before, so we wouldn't actually add any new ones. Copying in the command's constructor is probably the way to go, and if we do that, the slot in mainwindow will probably have to delete the originals after copied into the command.

https://github.com/casey-c/egg/commit/248af6114ff91bf3a9668f4dd6f6ace6ac756020


Tailscale_VPN CP: user does not have permissions to operate Tailscale

The desktop icon Activate Tailscale doesn't seem to work, at least with Tailscale 1.36.0. A terminal is started but exits immediately.
Running 'tailscale up' manually in a terminal, as user, gives an error:
Access denied: denied
Use 'sudo tailscale up' or 'tailscale up --operator=$USER' to not require root.
I experimented by first running 'tailscale up --operator=user' and/or 'tailscale set --operator=user' as root, and than run 'tailscale up' as user. This seems to work, however only once. After user runs 'tailscale down', user cannot run 'tailscale up' anymore until root again sets the operator to user.
Tailscale also provides 'tailscale web' which starts a local web server on port 8088 for controlling Tailscale. If I run 'tailscale web' as root, I can connect to Tailscale, as user, through this web server/web interface. This seems a nicer solution than through the terminal.
Perhaps we should consider changing the Tailscale VPN CP to use 'tailscale web' instead of 'tailscale up' in a terminal?

Reviewing your comments.

Items should be addressed now. Please rebuild.
https://github.com/IGEL-Community/IGEL-Custom-Partitions/tree/master/CP_Source/Network/Tailscale_VPN
Change history is here:
https://github.com/IGEL-Community/IGEL-Custom-Partitions/commits/master/CP_Source/Network/Tailscale_VPN

Thank you!
https://github.com/IGEL-Community/IGEL-Custom-Partitions/commit/77548714541750d33e18f2432fd080f4a6a3c013 :
pkexec -u root env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY

The above causes an authentication window/popup, which askes for the root password. (If I enter the root password it works fine.)
This is how I got this working in my test lab (without the need for root password):
UMS profile:
"System" > "Firmware Customization" > "Custom Commands" > "Desktop" > "Final desktop command" :
nohup tailscale web >/root/tailscale-web.log 2>&1 &

https://github.com/IGEL-Community/IGEL-Custom-Partitions/commit/e40ab97bfbbd49d2ffe558ac3b42d6cd81250884 :
You ended up removing 'tailscale web' from the tailscale-cp-init-script.sh script, but I think it's needed to start tailscale web the first time/after installing the CP?

Updated profile as noted in link below...
https://github.com/IGEL-Community/IGEL-Custom-Partitions/commit/eecf588ee5b6e26b166f3a094525c9035beb18bd


add iOS native libraries linking

Ah. Forgot to update this piece of doc. Thanks for the catch!

thanks @TheRogue76, keep it up!


Console output (windows) for start and stop different - just not consistent output

when stopping via command line dnscrypt-proxy.exe -service stop you get on console
[2018-11-16 09:55:18] [NOTICE] dnscrypt-proxy 2.0.18
[2018-11-16 09:55:18] [NOTICE] Service stopped
starting however shows just dnscrypt-proxy.exe -service start
NOTHING
so just for the sake of being consistent i would expect something as
[2018-11-16 09:55:18] [NOTICE] dnscrypt-proxy 2.0.18
[2018-11-16 09:55:18] [NOTICE] Service started

what is strange as this is coded in main.go ?????
	} else if *svcFlag == "start" {
		dlog.Notice("Service started")
	} else if *svcFlag == "stop" {
                   dlog.Notice("Service stopped")

No idea why :/


feat: New view template

Updated view template with some animated elements

GitHub link in the top right
Changes to buttons (added SCA)
footer added with scrolly message

LGTM!

tested on Windows and all working as expected :)


generate and publish osg-cpu-hours metrics (SOFTWARE-4437)

@bbockelm.

pull in scripts used to generate osg-cpu-hours metrics
add to nightly GHA run

May as well make this completely Python 3

I don't understand the request.  Is there something you would like changed?

May as well make this completely Python 3

I don't understand the request.  Is there something you would like changed?

I guess i see no reason to mark them explicitly as python3 as long as they continue to work with python2.
As seen in the github workflow, all of the nightly metrics scripts will run under the same python(3) virtualenv.  That python will be python3, yes.  But if the same requirements are installed in a python2 virtualenv (eg outside of the github workflow environment), the #!/usr/bin/env python scripts will run fine there also.
If you have python3-specific features you want to use for some reason, fine - then i would agree with making the python3 explicit.  But for the moment i don't see a good reason to introduce python2-breaking changes.

I guess i see no reason to mark them explicitly as python3 as long as they continue to work with python2.
As seen in the github workflow, all of the nightly metrics scripts will run under the same python(3) virtualenv.  That python will be python3, yes.  But if the same requirements are installed in a python2 virtualenv (eg outside of the github workflow environment), the #!/usr/bin/env python scripts will run fine there also.
If you have python3-specific features you want to use for some reason, fine - then i would agree with making the python3 explicit.  But for the moment i don't see a good reason to introduce python2-breaking changes.

But for the moment i don't see a good reason to introduce python2-breaking changes.

Because I don't want to support Python 2 wherever possible.

But for the moment i don't see a good reason to introduce python2-breaking changes.

Because I don't want to support Python 2 wherever possible.

I know you're fond of the bumbly.py

Well you are right about that.  I don't know if i've ever given a program a more apt, descriptive name.
I'll see what i can do.

I know you're fond of the bumbly.py

Well you are right about that.  I don't know if i've ever given a program a more apt, descriptive name.
I'll see what i can do.

I want us to go out of our way to introduce python2-breaking changes in order to make it clear to the world that we do not support python2

Very well then!  I will dutifully state my difference in opinion here.  Seems to me there is a difference between "not supporting" and "breaking compatibility".  I think it feels kinda lame to go out of our way to do the latter.
To adapt the words of Treebeard, "That doesn't make sense to me; but then, you are in charge."  :)

I want us to go out of our way to introduce python2-breaking changes in order to make it clear to the world that we do not support python2

Very well then!  I will dutifully state my difference in opinion here.  Seems to me there is a difference between "not supporting" and "breaking compatibility".  I think it feels kinda lame to go out of our way to do the latter.
To adapt the words of Treebeard, "That doesn't make sense to me; but then, you are in charge."  :)

LGTM!

LGTM!


Some integration tests failed on local kube environment

I am using kube cluster installed by docker desktop, edge version <IP_ADDRESS>.
After I launched the kube cluster, I install Istio and knative with the following commands:
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.5.0/istio-crds.yaml && \
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.5.0/istio.yaml

kubectl label namespace default istio-injection=enabled

kubectl apply --filename https://github.com/knative/serving/releases/download/v0.5.0/serving.yaml \
--filename https://github.com/knative/build/releases/download/v0.5.0/build.yaml \
--filename https://github.com/knative/eventing/releases/download/v0.5.0/release.yaml \
--filename https://github.com/knative/eventing-sources/releases/download/v0.5.0/eventing-sources.yaml \
--filename https://github.com/knative/serving/releases/download/v0.5.0/monitoring.yaml \
--filename https://raw.githubusercontent.com/knative/serving/v0.5.0/third_party/config/build/clusterrole.yaml

Then, I went the directory of tektoncd pipeline and ran the test command:
go test -v -count=1 -tags=e2e ./test

I got quite some warning and error messages:
=== RUN   TestTaskRunPipelineRunCancel
2019-04-09T11:21:43.868-0400	info	logging/config.go:39	Successfully created the logger.	{"knative.dev/jsonconfig": "{\n\t  \"level\": \"info\",\n\t  \"encoding\": \"console\",\n\t  \"outputPaths\": [\"stdout\"],\n\t  \"errorOutputPaths\": [\"stderr\"],\n\t  \"encoderConfig\": {\n\t    \"timeKey\": \"ts\",\n\t    \"messageKey\": \"message\",\n\t    \"levelKey\": \"level\",\n\t    \"nameKey\": \"logger\",\n\t    \"callerKey\": \"caller\",\n\t    \"messageKey\": \"msg\",\n\t    \"stacktraceKey\": \"stacktrace\",\n\t    \"lineEnding\": \"\",\n\t    \"levelEncoder\": \"\",\n\t    \"timeEncoder\": \"iso8601\",\n\t    \"durationEncoder\": \"\",\n\t    \"callerEncoder\": \"\"\n\t  }\n\t}"}
2019-04-09T11:21:43.868-0400	info	logging/config.go:39	Logging level set to info
2019-04-09T11:21:43.868-0400	warn	logging/config.go:41	Fetch GitHub commit ID from kodata failed: "KO_DATA_PATH" does not exist or is empty
=== PAUSE TestTaskRunPipelineRunCancel

--- FAIL: TestHelmDeployPipelineRun (404.33s)
    init_test.go:100: Create namespace arendelle-whgmf to deploy to
    init_test.go:112: Verify SA "default" is created in namespace "arendelle-whgmf"
    helm_task_test.go:229: Creating tiller service account
    helm_task_test.go:285: Creating Cluster Role binding tiller-vzkfw for helm
    helm_task_test.go:285: Creating Cluster Role binding default-tiller-nqjmp for helm
    helm_task_test.go:285: Creating Cluster Role binding default-tiller-qjrk7 for helm
    helm_task_test.go:61: Creating Git PipelineResource go-helloworld-git
    helm_task_test.go:66: Creating Image PipelineResource go-helloworld-image
    helm_task_test.go:71: Creating Task create-image-task
    helm_task_test.go:76: Creating Task helm-deploy-task
    helm_task_test.go:81: Creating Pipeline helm-deploy-pipeline
    helm_task_test.go:86: Creating PipelineRun helm-deploy-pipeline-run
    helm_task_test.go:93: Error waiting for PipelineRun helm-deploy-pipeline-run to finish: pipeline run helm-deploy-pipeline-run failed!
    build_logs.go:35: build logs {"level":"warn","ts":1554823392.837772,"logger":"fallback-logger","caller":"logging/config.go:65","msg":"Fetch GitHub commit ID from kodata failed: \"ref: refs/heads/master\" is not a valid GitHub commit ID"}
        {"level":"info","ts":1554823392.879035,"logger":"fallback-logger","caller":"creds-init/main.go:40","msg":"Credentials initialized."}
    helm_task_test.go:103: PipelineRun execution failed; helm may or may not have been installed :(
    init_test.go:61: ############################################
    init_test.go:62: ### Dumping objects from arendelle-whgmf ###
    init_test.go:63: ############################################
    panic.go:406:
        ---
        apiVersion: tekton.dev/v1alpha1
        kind: Pipeline
        metadata:
          creationTimestamp: "2019-04-09T15:22:43Z"
          generation: 1
          name: helm-deploy-pipeline
          namespace: arendelle-whgmf
          resourceVersion: "11011"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-whgmf/pipelines/helm-deploy-pipeline
          uid: 52608200-5adb-11e9-90b7-025000000001
        spec:
          params:
          - name: chartname
          resources:
          - name: git-repo
            type: git
          - name: the-image
            type: image
          tasks:
          - name: push-image
            resources:
              inputs:
              - name: gitsource
                resource: git-repo
              outputs:
              - name: builtimage
                resource: the-image
            taskRef:
              name: create-image-task
          - name: helm-deploy
            params:
            - name: pathToHelmCharts
              value: /workspace/gitsource/test/gohelloworld/gohelloworld-chart
            - name: chartname
              value: ${params.chartname}
            resources:
              inputs:
              - name: gitsource
                resource: git-repo
              - from:
                - push-image
                name: image
                resource: the-image
              outputs: null
            taskRef:
              name: helm-deploy-task
        status: {}

        ---
        apiVersion: tekton.dev/v1alpha1
        kind: PipelineResource
        metadata:
          creationTimestamp: "2019-04-09T15:22:43Z"
          generation: 1
          name: go-helloworld-git
          namespace: arendelle-whgmf
          resourceVersion: "11000"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-whgmf/pipelineresources/go-helloworld-git
          uid: 51ff2602-5adb-11e9-90b7-025000000001
        spec:
          params:
          - name: url
            value: https://github.com/tektoncd/pipeline
          type: git
        status: {}

        ---
        apiVersion: tekton.dev/v1alpha1
        kind: PipelineResource
        metadata:
          creationTimestamp: "2019-04-09T15:22:43Z"
          generation: 1
          name: go-helloworld-image
          namespace: arendelle-whgmf
          resourceVersion: "11004"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-whgmf/pipelineresources/go-helloworld-image
          uid: 5227194c-5adb-11e9-90b7-025000000001
        spec:
          params:
          - name: url
            value: localhost:5000/test/kanikotasktest/go-helloworld-image-s4r6g
          type: image
        status: {}

        ---
        apiVersion: tekton.dev/v1alpha1
        kind: PipelineRun
        metadata:
          creationTimestamp: "2019-04-09T15:22:43Z"
          generation: 1
          labels:
            tekton.dev/pipeline: helm-deploy-pipeline
          name: helm-deploy-pipeline-run
          namespace: arendelle-whgmf
          resourceVersion: "13947"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-whgmf/pipelineruns/helm-deploy-pipeline-run
          uid: 52773d82-5adb-11e9-90b7-025000000001
        spec:
          Status: ""
          params:
          - name: chartname
            value: gohelloworld
          pipelineRef:
            name: helm-deploy-pipeline
          resources:
          - name: git-repo
            resourceRef:
              name: go-helloworld-git
          - name: the-image
            resourceRef:
              name: go-helloworld-image
          serviceAccount: ""
          trigger:
            type: manual
        status:
          conditions:
          - lastTransitionTime: "2019-04-09T15:29:25Z"
            message: TaskRun helm-deploy-pipeline-run-push-image-l6mrg has failed
            reason: Failed
            status: "False"
            type: Succeeded
          startTime: "2019-04-09T15:22:44Z"
          taskRuns:
            helm-deploy-pipeline-run-push-image-l6mrg:
              pipelineTaskName: push-image
              status:
                completionTime: "2019-04-09T15:29:25Z"
                conditions:
                - lastTransitionTime: "2019-04-09T15:29:25Z"
                  message: 'build step "build-step-kaniko" exited with code 1 (image: "docker-pullable://gcr.io/kaniko-project/executor@sha256:d9fe474f80b73808dc12b54f45f5fc90f7856d9fc699d4a5e79d968a1aef1a72");
                    for logs run: kubectl -n arendelle-whgmf logs helm-deploy-pipeline-run-push-image-l6mrg-pod-45c3d5
                    -c build-step-kaniko'
                  status: "False"
                  type: Succeeded
                podName: helm-deploy-pipeline-run-push-image-l6mrg-pod-45c3d5
                startTime: "2019-04-09T15:23:00Z"
                steps:
                - terminated:
                    containerID: docker://c1e20c12467d8fa30169f4a9ef9eb8d3c59e360cb9c3fa9ebe7a2b21e3d32c2d
                    exitCode: 0
                    finishedAt: "2019-04-09T15:23:41Z"
                    reason: Completed
                    startedAt: "2019-04-09T15:23:22Z"
                - terminated:
                    containerID: docker://240ca42ca102187eef9f89d59ea1ebba7cfdb558a3ab48251b9c89452788c6d1
                    exitCode: 1
                    finishedAt: "2019-04-09T15:29:24Z"
                    reason: Error
                    startedAt: "2019-04-09T15:23:24Z"
                - terminated:
                    containerID: docker://8f4918f973219d7ec26a223b1c8982b70c39791720e60a38a888201713843aaa
                    exitCode: 0
                    finishedAt: "2019-04-09T15:23:26Z"
                    reason: Completed
                    startedAt: "2019-04-09T15:23:26Z"

        ---
        apiVersion: tekton.dev/v1alpha1
        kind: Task
        metadata:
          creationTimestamp: "2019-04-09T15:22:43Z"
          generation: 1
          name: create-image-task
          namespace: arendelle-whgmf
          resourceVersion: "11006"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-whgmf/tasks/create-image-task
          uid: 52392b54-5adb-11e9-90b7-025000000001
        spec:
          inputs:
            resources:
            - name: gitsource
              targetPath: ""
              type: git
          outputs:
            resources:
            - name: builtimage
              targetPath: ""
              type: image
          steps:
          - args:
            - --dockerfile=/workspace/gitsource/test/gohelloworld/Dockerfile
            - --context=/workspace/gitsource/
            - --destination=${outputs.resources.builtimage.url}
            image: gcr.io/kaniko-project/executor
            name: kaniko
            resources: {}

        ---
        apiVersion: tekton.dev/v1alpha1
        kind: Task
        metadata:
          creationTimestamp: "2019-04-09T15:22:43Z"
          generation: 1
          name: helm-deploy-task
          namespace: arendelle-whgmf
          resourceVersion: "11010"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-whgmf/tasks/helm-deploy-task
          uid: 525172cf-5adb-11e9-90b7-025000000001
        spec:
          inputs:
            params:
            - description: Path to the helm charts
              name: pathToHelmCharts
            - name: chartname
            resources:
            - name: gitsource
              targetPath: ""
              type: git
            - name: image
              targetPath: ""
              type: image
          steps:
          - args:
            - init
            - --wait
            image: alpine/helm
            name: helm-init
            resources: {}
          - args:
            - install
            - --debug
            - --name=${inputs.params.chartname}
            - ${inputs.params.pathToHelmCharts}
            - --set
            - image.repository=${inputs.resources.image.url}
            image: alpine/helm
            name: helm-deploy
            resources: {}

        ---
        apiVersion: tekton.dev/v1alpha1
        kind: TaskRun
        metadata:
          creationTimestamp: "2019-04-09T15:22:46Z"
          generation: 1
          labels:
            tekton.dev/pipeline: helm-deploy-pipeline
            tekton.dev/pipelineRun: helm-deploy-pipeline-run
            tekton.dev/task: create-image-task
          name: helm-deploy-pipeline-run-push-image-l6mrg
          namespace: arendelle-whgmf
          ownerReferences:
          - apiVersion: tekton.dev/v1alpha1
            blockOwnerDeletion: true
            controller: true
            kind: PipelineRun
            name: helm-deploy-pipeline-run
            uid: 52773d82-5adb-11e9-90b7-025000000001
          resourceVersion: "13945"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-whgmf/taskruns/helm-deploy-pipeline-run-push-image-l6mrg
          uid: 5412200a-5adb-11e9-90b7-025000000001
        spec:
          Status: ""
          inputs:
            resources:
            - name: gitsource
              paths: null
              resourceRef:
                name: go-helloworld-git
              resourceSpec: null
          outputs:
            resources:
            - name: builtimage
              paths:
              - /pvc/push-image/builtimage
              resourceRef:
                name: go-helloworld-image
              resourceSpec: null
          taskRef:
            kind: Task
            name: create-image-task
          trigger:
            type: ""
        status:
          completionTime: "2019-04-09T15:29:25Z"
          conditions:
          - lastTransitionTime: "2019-04-09T15:29:25Z"
            message: 'build step "build-step-kaniko" exited with code 1 (image: "docker-pullable://gcr.io/kaniko-project/executor@sha256:d9fe474f80b73808dc12b54f45f5fc90f7856d9fc699d4a5e79d968a1aef1a72");
              for logs run: kubectl -n arendelle-whgmf logs helm-deploy-pipeline-run-push-image-l6mrg-pod-45c3d5
              -c build-step-kaniko'
            status: "False"
            type: Succeeded
          podName: helm-deploy-pipeline-run-push-image-l6mrg-pod-45c3d5
          startTime: "2019-04-09T15:23:00Z"
          steps:
          - terminated:
              containerID: docker://c1e20c12467d8fa30169f4a9ef9eb8d3c59e360cb9c3fa9ebe7a2b21e3d32c2d
              exitCode: 0
              finishedAt: "2019-04-09T15:23:41Z"
              reason: Completed
              startedAt: "2019-04-09T15:23:22Z"
          - terminated:
              containerID: docker://240ca42ca102187eef9f89d59ea1ebba7cfdb558a3ab48251b9c89452788c6d1
              exitCode: 1
              finishedAt: "2019-04-09T15:29:24Z"
              reason: Error
              startedAt: "2019-04-09T15:23:24Z"
          - terminated:
              containerID: docker://8f4918f973219d7ec26a223b1c8982b70c39791720e60a38a888201713843aaa
              exitCode: 0
              finishedAt: "2019-04-09T15:23:26Z"
              reason: Completed
              startedAt: "2019-04-09T15:23:26Z"

        ---
        metadata:
          annotations:
            sidecar.istio.io/inject: "false"
          creationTimestamp: "2019-04-09T15:23:00Z"
          labels:
            tekton.dev/pipeline: helm-deploy-pipeline
            tekton.dev/pipelineRun: helm-deploy-pipeline-run
            tekton.dev/task: create-image-task
            tekton.dev/taskRun: helm-deploy-pipeline-run-push-image-l6mrg
          name: helm-deploy-pipeline-run-push-image-l6mrg-pod-45c3d5
          namespace: arendelle-whgmf
          ownerReferences:
          - apiVersion: tekton.dev/v1alpha1
            blockOwnerDeletion: true
            controller: true
            kind: TaskRun
            name: helm-deploy-pipeline-run-push-image-l6mrg
            uid: 5412200a-5adb-11e9-90b7-025000000001
          resourceVersion: "13944"
          selfLink: /api/v1/namespaces/arendelle-whgmf/pods/helm-deploy-pipeline-run-push-image-l6mrg-pod-45c3d5
          uid: 5c2e1f14-5adb-11e9-90b7-025000000001
        spec:
          containers:
          - args:
            - -wait_file
            - ""
            - -post_file
            - /builder/tools/0
            - -entrypoint
            - /ko-app/git-init
            - --
            - -url
            - https://github.com/tektoncd/pipeline
            - -revision
            - master
            - -path
            - /workspace/gitsource
            command:
            - /builder/tools/entrypoint
            env:
            - name: HOME
              value: /builder/home
            image: localhost:5000/test/git-init-4874978a9786b6625dd8b6ef2a21aa70@sha256:065288da67059e6b510be5074ce96188da6971168725039148ae52bf0480984b
            imagePullPolicy: IfNotPresent
            name: build-step-git-source-go-helloworld-git-vkkdf
            resources: {}
            terminationMessagePath: /dev/termination-log
            terminationMessagePolicy: File
            volumeMounts:
            - mountPath: /builder/tools
              name: tools
            - mountPath: /workspace
              name: workspace
            - mountPath: /builder/home
              name: home
            - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
              name: default-token-8mkwk
              readOnly: true
            workingDir: /workspace
          - args:
            - -wait_file
            - /builder/tools/0
            - -post_file
            - /builder/tools/1
            - -entrypoint
            - /kaniko/executor
            - --
            - --dockerfile=/workspace/gitsource/test/gohelloworld/Dockerfile
            - --context=/workspace/gitsource/
            - --destination=localhost:5000/test/kanikotasktest/go-helloworld-image-s4r6g
            command:
            - /builder/tools/entrypoint
            env:
            - name: HOME
              value: /builder/home
            image: gcr.io/kaniko-project/executor
            imagePullPolicy: Always
            name: build-step-kaniko
            resources: {}
            terminationMessagePath: /dev/termination-log
            terminationMessagePolicy: File
            volumeMounts:
            - mountPath: /builder/tools
              name: tools
            - mountPath: /workspace
              name: workspace
            - mountPath: /builder/home
              name: home
            - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
              name: default-token-8mkwk
              readOnly: true
            workingDir: /workspace
          - command:
            - /ko-app/nop
            image: localhost:5000/test/nop-8eac7c133edad5df719dc37b36b62482@sha256:30e162a972330a541addf391e3861c9735e7db700a9c642e04b3e085d44e9633
            imagePullPolicy: IfNotPresent
            name: nop
            resources: {}
            terminationMessagePath: /dev/termination-log
            terminationMessagePolicy: File
            volumeMounts:
            - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
              name: default-token-8mkwk
              readOnly: true
          dnsPolicy: ClusterFirst
          initContainers:
          - command:
            - /ko-app/creds-init
            env:
            - name: HOME
              value: /builder/home
            image: localhost:5000/test/creds-init-c761f275af7b3d8bea9d50cc6cb0106f@sha256:63db28a2f95f7b7d4ac88ac6958a67861df16487ad418432c4c3a00d4c035303
            imagePullPolicy: IfNotPresent
            name: build-step-credential-initializer-vk4sp
            resources: {}
            terminationMessagePath: /dev/termination-log
            terminationMessagePolicy: File
            volumeMounts:
            - mountPath: /workspace
              name: workspace
            - mountPath: /builder/home
              name: home
            - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
              name: default-token-8mkwk
              readOnly: true
            workingDir: /workspace
          - args:
            - -c
            - cp /ko-app/entrypoint /builder/tools/entrypoint
            command:
            - /bin/sh
            env:
            - name: HOME
              value: /builder/home
            image: localhost:5000/test/entrypoint-bff0a22da108bc2f16c818c97641a296@sha256:b9662e95d427b28e5367e27220556c4c5647c5fbdec90c72819345374b4bc15c
            imagePullPolicy: IfNotPresent
            name: build-step-place-tools
            resources: {}
            terminationMessagePath: /dev/termination-log
            terminationMessagePolicy: File
            volumeMounts:
            - mountPath: /builder/tools
              name: tools
            - mountPath: /workspace
              name: workspace
            - mountPath: /builder/home
              name: home
            - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
              name: default-token-8mkwk
              readOnly: true
            workingDir: /workspace
          nodeName: docker-desktop
          priority: 0
          restartPolicy: Never
          schedulerName: default-scheduler
          securityContext: {}
          serviceAccount: default
          serviceAccountName: default
          terminationGracePeriodSeconds: 30
          tolerations:
          - effect: NoExecute
            key: node.kubernetes.io/not-ready
            operator: Exists
            tolerationSeconds: 300
          - effect: NoExecute
            key: node.kubernetes.io/unreachable
            operator: Exists
            tolerationSeconds: 300
          volumes:
          - name: helm-deploy-pipeline-run-pvc
            persistentVolumeClaim:
              claimName: helm-deploy-pipeline-run-pvc
          - emptyDir: {}
            name: tools
          - emptyDir: {}
            name: workspace
          - emptyDir: {}
            name: home
          - name: default-token-8mkwk
            secret:
              defaultMode: 420
              secretName: default-token-8mkwk
        status:
          conditions:
          - lastProbeTime: null
            lastTransitionTime: "2019-04-09T15:23:21Z"
            status: "True"
            type: Initialized
          - lastProbeTime: null
            lastTransitionTime: "2019-04-09T15:23:04Z"
            message: 'containers with unready status: [build-step-git-source-go-helloworld-git-vkkdf
              build-step-kaniko nop]'
            reason: ContainersNotReady
            status: "False"
            type: Ready
          - lastProbeTime: null
            lastTransitionTime: "2019-04-09T15:23:04Z"
            message: 'containers with unready status: [build-step-git-source-go-helloworld-git-vkkdf
              build-step-kaniko nop]'
            reason: ContainersNotReady
            status: "False"
            type: ContainersReady
          - lastProbeTime: null
            lastTransitionTime: "2019-04-09T15:23:04Z"
            status: "True"
            type: PodScheduled
          containerStatuses:
          - containerID: docker://c1e20c12467d8fa30169f4a9ef9eb8d3c59e360cb9c3fa9ebe7a2b21e3d32c2d
            image: sha256:9a9a722a7a90ecf82cf6dd158bb551824ca3923b6376fbcb84d5308005b511df
            imageID: docker-pullable://localhost:5000/test/git-init-4874978a9786b6625dd8b6ef2a21aa70@sha256:065288da67059e6b510be5074ce96188da6971168725039148ae52bf0480984b
            lastState: {}
            name: build-step-git-source-go-helloworld-git-vkkdf
            ready: false
            restartCount: 0
            state:
              terminated:
                containerID: docker://c1e20c12467d8fa30169f4a9ef9eb8d3c59e360cb9c3fa9ebe7a2b21e3d32c2d
                exitCode: 0
                finishedAt: "2019-04-09T15:23:41Z"
                reason: Completed
                startedAt: "2019-04-09T15:23:22Z"
          - containerID: docker://240ca42ca102187eef9f89d59ea1ebba7cfdb558a3ab48251b9c89452788c6d1
            image: gcr.io/kaniko-project/executor:latest
            imageID: docker-pullable://gcr.io/kaniko-project/executor@sha256:d9fe474f80b73808dc12b54f45f5fc90f7856d9fc699d4a5e79d968a1aef1a72
            lastState: {}
            name: build-step-kaniko
            ready: false
            restartCount: 0
            state:
              terminated:
                containerID: docker://240ca42ca102187eef9f89d59ea1ebba7cfdb558a3ab48251b9c89452788c6d1
                exitCode: 1
                finishedAt: "2019-04-09T15:29:24Z"
                reason: Error
                startedAt: "2019-04-09T15:23:24Z"
          - containerID: docker://8f4918f973219d7ec26a223b1c8982b70c39791720e60a38a888201713843aaa
            image: sha256:549e07763ddc5b69f8fd21cce484b833261d15966f53ef6490a32f583b8b62c8
            imageID: docker-pullable://localhost:5000/test/nop-8eac7c133edad5df719dc37b36b62482@sha256:30e162a972330a541addf391e3861c9735e7db700a9c642e04b3e085d44e9633
            lastState: {}
            name: nop
            ready: false
            restartCount: 0
            state:
              terminated:
                containerID: docker://8f4918f973219d7ec26a223b1c8982b70c39791720e60a38a888201713843aaa
                exitCode: 0
                finishedAt: "2019-04-09T15:23:26Z"
                reason: Completed
                startedAt: "2019-04-09T15:23:26Z"
          hostIP: <IP_ADDRESS>
          initContainerStatuses:
          - containerID: docker://1bbfe60dc7f5ba0e5df9c6454b57dbb0cc1973a92d4d487e8b73e5bd65277102
            image: sha256:333621da134f7ac0f3d73dbe44faca90bfb7e89eb06f13ed79b6c1b948162f40
            imageID: docker-pullable://localhost:5000/test/creds-init-c761f275af7b3d8bea9d50cc6cb0106f@sha256:63db28a2f95f7b7d4ac88ac6958a67861df16487ad418432c4c3a00d4c035303
            lastState: {}
            name: build-step-credential-initializer-vk4sp
            ready: true
            restartCount: 0
            state:
              terminated:
                containerID: docker://1bbfe60dc7f5ba0e5df9c6454b57dbb0cc1973a92d4d487e8b73e5bd65277102
                exitCode: 0
                finishedAt: "2019-04-09T15:23:12Z"
                reason: Completed
                startedAt: "2019-04-09T15:23:12Z"
          - containerID: docker://3277fe2d58bd676edaafea8731992e5ae8daa119cb4cc5c46d76775688900015
            image: sha256:4db4e293b1fde7600e1b4cbcd7c25d88c94050ebfe07a8334e92f7c57dd38cae
            imageID: docker-pullable://localhost:5000/test/entrypoint-bff0a22da108bc2f16c818c97641a296@sha256:b9662e95d427b28e5367e27220556c4c5647c5fbdec90c72819345374b4bc15c
            lastState: {}
            name: build-step-place-tools
            ready: true
            restartCount: 0
            state:
              terminated:
                containerID: docker://3277fe2d58bd676edaafea8731992e5ae8daa119cb4cc5c46d76775688900015
                exitCode: 0
                finishedAt: "2019-04-09T15:23:18Z"
                reason: Completed
                startedAt: "2019-04-09T15:23:18Z"
          phase: Failed
          podIP: <IP_ADDRESS>
          qosClass: BestEffort
          startTime: "2019-04-09T15:23:04Z"

    panic.go:406: Deleting namespace arendelle-whgmf
--- FAIL: TestKanikoTaskRun (432.75s)
    init_test.go:100: Create namespace arendelle-7bx94 to deploy to
    init_test.go:112: Verify SA "default" is created in namespace "arendelle-7bx94"
    kaniko_task_test.go:129: Not creating service account secret. This could cause the test to fail locally!
    kaniko_task_test.go:132: Creating Git PipelineResource go-example-git
    kaniko_task_test.go:137: Creating Task kanikotask
    kaniko_task_test.go:142: Creating TaskRun kanikotask-run
    kaniko_task_test.go:153: Error waiting for TaskRun kanikotask-run to finish: task run kanikotask-run failed!
    kaniko_task_test.go:158: Error getting build pod: pods "kanikotask-run-pod-9624c0" not found
    init_test.go:61: ############################################
    init_test.go:62: ### Dumping objects from arendelle-7bx94 ###
    init_test.go:63: ############################################
    panic.go:406:
        ---
        apiVersion: tekton.dev/v1alpha1
        kind: PipelineResource
        metadata:
          creationTimestamp: "2019-04-09T15:22:41Z"
          generation: 1
          name: go-example-git
          namespace: arendelle-7bx94
          resourceVersion: "10958"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-7bx94/pipelineresources/go-example-git
          uid: 512a3051-5adb-11e9-90b7-025000000001
        spec:
          params:
          - name: Url
            value: https://github.com/pivotal-nader-ziada/gohelloworld
          type: git
        status: {}

        ---
        apiVersion: tekton.dev/v1alpha1
        kind: Task
        metadata:
          creationTimestamp: "2019-04-09T15:22:41Z"
          generation: 1
          name: kanikotask
          namespace: arendelle-7bx94
          resourceVersion: "10961"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-7bx94/tasks/kanikotask
          uid: 5140cd62-5adb-11e9-90b7-025000000001
        spec:
          inputs:
            resources:
            - name: gitsource
              targetPath: ""
              type: git
          steps:
          - args:
            - --dockerfile=/workspace/gitsource/Dockerfile
            - --destination=localhost:5000/test/kanikotasktest
            - --context=/workspace/gitsource
            image: gcr.io/kaniko-project/executor
            name: kaniko
            resources: {}

        ---
        apiVersion: tekton.dev/v1alpha1
        kind: TaskRun
        metadata:
          creationTimestamp: "2019-04-09T15:22:42Z"
          generation: 1
          labels:
            tekton.dev/task: kanikotask
          name: kanikotask-run
          namespace: arendelle-7bx94
          resourceVersion: "14041"
          selfLink: /apis/tekton.dev/v1alpha1/namespaces/arendelle-7bx94/taskruns/kanikotask-run
          uid: 51531626-5adb-11e9-90b7-025000000001
        spec:
          Status: ""
          inputs:
            resources:
            - name: gitsource
              paths: null
              resourceRef:
                name: go-example-git
              resourceSpec: null
          outputs: {}
          taskRef:
            kind: Task
            name: kanikotask
          timeout: 2m0s
          trigger:
            type: ""
        status:
          completionTime: "2019-04-09T15:29:52Z"
          conditions:
          - lastTransitionTime: "2019-04-09T15:29:52Z"
            message: TaskRun "kanikotask-run" failed to finish within "2m0s"
            reason: TaskRunTimeout
            status: "False"
            type: Succeeded
          podName: kanikotask-run-pod-9624c0
          startTime: "2019-04-09T15:22:54Z"
          steps:
          - terminated:
              containerID: docker://431cbd39341fd219b44f19117bc37e35805786af6b0a81a3ce8a9c522e4d7340
              exitCode: 0
              finishedAt: "2019-04-09T15:23:08Z"
              reason: Completed
              startedAt: "2019-04-09T15:23:06Z"
          - running:
              startedAt: "2019-04-09T15:23:08Z"
          - terminated:
              containerID: docker://578ea1a39b1b181b966fad7d76dbf2f0e6ddb69f40dac0ccf3fb0bdb1d482893
              exitCode: 0
              finishedAt: "2019-04-09T15:23:13Z"
              reason: Completed
              startedAt: "2019-04-09T15:23:13Z"

    panic.go:406: Deleting namespace arendelle-7bx94
--- PASS: TestPipelineRun (0.00s)
    --- PASS: TestPipelineRun/service_account_propagation (52.95s)
        init_test.go:100: Create namespace arendelle-npgxb to deploy to
        init_test.go:112: Verify SA "default" is created in namespace "arendelle-npgxb"
        pipelinerun_test.go:124: Setting up test resources for "service account propagation" test in namespace arendelle-npgxb
        pipelinerun_test.go:133: Waiting for PipelineRun pipelinerun1 in namespace arendelle-npgxb to complete
        pipelinerun_test.go:138: Making sure the expected TaskRuns [task1] were created
        pipelinerun_test.go:161: Checking that labels were propagated correctly for TaskRun pipelinerun1-task1-dsn9v
        pipelinerun_test.go:167: Making sure 2 events were created from taskrun and pipelinerun with kinds map[PipelineRun:[pipelinerun1] TaskRun:[pipelinerun1-task1-dsn9v]]
        pipelinerun_test.go:176: Successfully finished test "service account propagation"
        pipelinerun_test.go:177: Deleting namespace arendelle-npgxb
    --- PASS: TestPipelineRun/fan-in_and_fan-out (414.33s)
        init_test.go:100: Create namespace arendelle-scxcc to deploy to
        init_test.go:112: Verify SA "default" is created in namespace "arendelle-scxcc"
        pipelinerun_test.go:124: Setting up test resources for "fan-in and fan-out" test in namespace arendelle-scxcc
        pipelinerun_test.go:133: Waiting for PipelineRun pipelinerun1 in namespace arendelle-scxcc to complete
        pipelinerun_test.go:138: Making sure the expected TaskRuns [create-file-kritis create-fan-out-1 create-fan-out-2 check-fan-in] were created
        pipelinerun_test.go:161: Checking that labels were propagated correctly for TaskRun pipelinerun1-create-file-kritis-dmtvj
        pipelinerun_test.go:161: Checking that labels were propagated correctly for TaskRun pipelinerun1-create-fan-out-1-4w2k2
        pipelinerun_test.go:161: Checking that labels were propagated correctly for TaskRun pipelinerun1-create-fan-out-2-q4rhc
        pipelinerun_test.go:161: Checking that labels were propagated correctly for TaskRun pipelinerun1-check-fan-in-2smrw
        pipelinerun_test.go:167: Making sure 5 events were created from taskrun and pipelinerun with kinds map[PipelineRun:[pipelinerun1] TaskRun:[pipelinerun1-create-file-kritis-dmtvj pipelinerun1-create-fan-out-1-4w2k2 pipelinerun1-create-fan-out-2-q4rhc pipelinerun1-check-fan-in-2smrw]]
        pipelinerun_test.go:176: Successfully finished test "fan-in and fan-out"
        pipelinerun_test.go:177: Deleting namespace arendelle-scxcc
FAIL
FAIL	github.com/tektoncd/pipeline/test	503.557s

I was kindly wondering what are missing and what could be the reasons for them.

Hey @houshengbo !! Sorry you're running into trouble here - I'm not sure what's going wrong but one thing that stands out is:
                - lastTransitionTime: "2019-04-09T15:29:25Z"
                  message: 'build step "build-step-kaniko" exited with code 1 (image: "docker-pullable://gcr.io/kaniko-project/executor@sha256:d9fe474f80b73808dc12b54f45f5fc90f7856d9fc699d4a5e79d968a1aef1a72");
                    for logs run: kubectl -n arendelle-whgmf logs helm-deploy-pipeline-run-push-image-l6mrg-pod-45c3d5
                    -c build-step-kaniko'
                  status: "False"
                  type: Succeeded
                podName: helm-deploy-pipeline-run-push-image-l6mrg-pod-45c3d5
                startTime: "2019-04-09T15:23:00Z"

So it looks like the kaniko build step is failing - if we could get at those logs we could probably figure out what's going wrong (I'm gonna take a wild guess that it might be permissions related but I'm not sure!).
If you want to take a look at the logs, you'll need to get at them before the test tearsdown the namespace, i.e.:
https://github.com/tektoncd/pipeline/blob/28cf0ea39924f0930cf26712f933a1f60f7a0a3f/test/kaniko_task_test.go#L119-L120
You could do that by deleting / commenting out those lines, then the namespace will stick around after the test and you can look at the test output, find the name of the pod and look at the logs.
Hope that helps!

@bobcatfish yes, some end-to-end tests may fails locally as they required some "temporarly" changes (ex is https://github.com/tektoncd/pipeline/blob/master/test/e2e-common.sh#L95) or with KO_DOCKER_REPO. I think we may need a simple conditional run setup or something when we detect something is missing, but didn't took to much time to think about it yet

Ah kk so it sounds like the work here is for us to make sure we support local running of integration tests! (And part of that is surfacing errors better if the setup isn't correct...)

https://github.com/tektoncd/pipeline/pull/1516 should fix at least that test (need to get a full run on kind or something to make sure)


No Done jobs

Hi
I test apalis (mysql backend)  with 2 workers and consistently add new jobs.
Tens of jobs is done but in database jobs table  is 2 jobs only.
Their id is changing - but no one job saved as done.
Why?

Mysql uses FOR UPDATE which might have locked some rows.

No one of 100 jobs is stated as done in db.
So this is the Apalis bug?
Or it is must be stated in Apalis docs: " "with mysql cant to work normal"?

Hi, I'm very late to the conversation but I think the problem is the ON DELETE CASCADE on the jobs table. https://github.com/geofmureithi/apalis/blob/master/packages/apalis-sql/migrations/mysql/20220530084123_jobs_workers.sql#L29
Getting rid of that would list the done jobs but it will require some cleanup at some point.

Hey I think the problem is related with this line: https://github.com/geofmureithi/apalis/blob/master/packages/apalis-sql/src/mysql.rs#L180
Using replace with a foreign key in mysql will force the deletion of all the child rows.  I have a simple fork with a fix based on INSERT with UPDATE ON DUPLICATE that is working for me. I can send a PR if you want it. https://github.com/dlen/apalis/blob/master/packages/apalis-sql/src/mysql.rs#L180

@dlen Please do!


Update CI.yml

This adds x86 (32-bit) and aarch64 systems to the test targets.
The test fails on 32-bit systems.
One of the problems is that Inflate.jl (for DEFLATE images) may not work on 32-bit systems. (It seems to pass the TiffImages.jl's test, though.) Edit: Fixed by https://github.com/GunnarFarneback/Inflate.jl/pull/21.
Another problem is the LZW handling of TiffImages.jl, as the test results show. (see PR #169)
┌ Warning: LZW: expected 27648 bytes, got 3571 bytes
└ @ TiffImages ~/work/TiffImages.jl/TiffImages.jl/src/compression.jl:202
LZW: Test Failed at /home/runner/work/TiffImages.jl/TiffImages.jl/test/runtests.jl:219
  Expression: TiffImages.load(uncompressed) == TiffImages.load(compressed)
   Evaluated: RGB{N0f8}[RGB{N0f8}(1.0,1.0,1.0) RGB{N0f8}(1.0,1.0,1.0) … RGB{N0f8}(1.0,1.0,1.0) RGB{N0f8}(1.0,1.0,1.0); RGB{N0f8}(1.0,1.0,1.0) RGB{N0f8}(1.0,1.0,1.0) … RGB{N0f8}(1.0,1.0,1.0) RGB{N0f8}(1.0,1.0,1.0); … ; RGB{N0f8}(1.0,1.0,1.0) RGB{N0f8}(1.0,1.0,1.0) … RGB{N0f8}(1.0,1.0,1.0) RGB{N0f8}(1.0,1.0,1.0); RGB{N0f8}(1.0,1.0,1.0) RGB{N0f8}(1.0,1.0,1.0) … RGB{N0f8}(1.0,1.0,1.0) RGB{N0f8}(1.0,1.0,1.0)] == RGB{N0f8}[RGB{N0f8}(1.0,0.0,0.0) RGB{N0f8}(1.0,0.0,0.0) … RGB{N0f8}(0.043,0.553,0.039) RGB{N0f8}(0.361,0.757,0.125); RGB{N0f8}(0.506,0.329,0.133) RGB{N0f8}(0.525,0.286,0.0) … RGB{N0f8}(0.996,0.376,0.184) RGB{N0f8}(0.98,0.357,0.306); … ; RGB{N0f8}(0.0,0.0,0.0) RGB{N0f8}(0.0,0.125,0.0) … RGB{N0f8}(0.863,0.396,0.42) RGB{N0f8}(0.863,0.396,0.42); RGB{N0f8}(0.125,0.0,0.0) RGB{N0f8}(0.125,1.0,1.0) … RGB{N0f8}(0.345,0.725,0.059) RGB{N0f8}(0.282,0.722,0.055)]

The last problem I am aware of is "Arbitrary Bit Depth" (recode()). (See PR #170)
codecov/codecov-action@v4 requires CODECOV_TOKEN.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.31%. Comparing base (ee4852f) to head (6a3e738).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #168      +/-   ##
==========================================
- Coverage   93.58%   93.31%   -0.27%
==========================================
  Files          13       13
  Lines        1169     1122      -47
==========================================
- Hits         1094     1047      -47
  Misses         75       75

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


TwitterKit provides Application-only authentication?

How can I make an Application-only authentication?
My app there is no user session, I only need to show a hashtag search timeline, but I'm limited of 180 request por 15 minutes, I noticed that I can obtain 450 request per 15 minutes if I use Application-only authentication, how can I do it using TwitterKit?

Twitter Kit does not support application-only authentication.
Per https://github.com/twitter/twitter-kit-ios/wiki/Log-In-With-Twitter you can either have a user session, or use guest authentication, but in both cases you'll be rate limited at the 180/15 min level.


Screenshots of UI

Hi
Any chance someone can post some screenshots of the UI ?  I'm curious what the UI looks like.
Thanks
Dave

@dekhaus Sorry for the late reply and thanks for reaching out. Yes, I think this is a great idea. We'll make sure to add this with the new updated readme.

Fixed in #133


Copy-DbaDatabase fix for cleanup

Fixes #1248
Changes proposed in this pull request:

No cleans up after itself
Not sure whats happened, but backup type wasn't coming through, now there.

How to test this code:

[ ]
[ ]

Has been tested on minimum requirements:

[ ]  Powershell 3
[ ]  Windows 7
[ ]  SQL Server 2000

Has been tested on maximum requirements:

[ ]  SQL Server vNext
[ ]  Windows 10
[ ]  Azure Database

Tests for tester:

[ ] Working/useful help content, including link to command on dbatools web site
[ ] All examples work as advertised
[ ] Does not contain template content
[ ] Does not contain excessive/unnecessary amounts of comments
[ ] Works remotely
[ ] Works locally
[ ] Works on lower versions or throws error specifying version not supported
[ ] Works with named instances
[ ] Works with clustered instances
[ ] Handles offline/read only databases
[ ] Supports multiple servers (at the command line or piped from Get-SqlRegisteredServerName)
[ ] No un-handled errors which stop the command working with multiple servers

Thank you so very very much, @Stuart-Moore!


Update aks-hci-evaluation-guide-2a.md

Section name is Tools.

Learn Build status updates of commit 667e49d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AKS-Hybrid/aks-hci-evaluation-guide-2a.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@mustafakaya Thank you for catching that, we really appreciate it. Merging soon.
#sign-off


Start building the basic parts of GUI

[x] Start a main class

[x] Have tree loaded when the tool starts

[x] Look into FXML and Scene Builder

[x] continue building a basic GUI

[ ] fix saveAndQuit

[ ] fix fileNotFound triggering when closing Alert

[x] fix optionsFXML loader

[ ] correlation coefficient and p-value should be togglable for the data

[ ] load samples -> multiple files

[ ] loading files -> dropdown menu and user chooses file format

[ ] change bottom left and bottom right status to something useful

[ ] export stuff as image/PDF

[ ] put analysis into tab pane

[ ] possibly add a legend to the view

[ ] hovering over nodes should display a tooltip

[ ] add some useful stuff to the options scene

[ ] beautify the GUI

[ ] preload files using concurrent programming (service class)

Which Scene Builder are we gonna use? The gluon scene builder?

IntelliJ supports Oracle Scene Builder 2. I'd suggest that.
https://www.jetbrains.com/help/idea/2017.1/opening-fxml-files-in-javafx-scene-builder.html

All right, seems like gluon is also maintaining this one now. Oracle did not provide installers for their own scene builder for a long time.
https://www.quora.com/Is-Gluons-Scene-Builder-the-same-as-the-Oracle-JavaFX-Scene-Builder

If you are more comfortable with that or think it is better, fine for me.

some of the tasks here are redundant with Network Visualization. That's fine, but just make sure you communicate and don't implement the same functionality in two different places. :)

Noticed that as well ;)
We have a discord chat for communication, maybe I'll update the list again and remove the redundant things.

alright, everything seems to be on track. :)


should we specify HTTP Public Key Pinning (HPKP)?

https://scotthelme.co.uk/hpkp-http-public-key-pinning/

I don't think this should be in the specification at this time.

Agree.


Translate docs/tasks/job/coarse-parallel-processing-work-queue.md into Korean

This is a Feature Request

What would you like to be added

Translate docs/tasks/job/coarse-parallel-processing-work-queue.md into Korean
Why is this needed
Cannot find docs/tasks/job/coarse-parallel-processing-work-queue.md in Korean
Comments

The page to update:
https://kubernetes.io/docs/tasks/job/coarse-parallel-processing-work-queue/

/language ko
/assign

Fixed in #24218
/close


Invoke-DcnRepairClone: Drop broken clones

Is your feature request related to a problem? Please describe.
Add a flag/feature to allow cleanup of the metadata when clones cannot be repaired.
Describe the solution you'd like
Being able to run Invoke-DcnRepairClone -RemoveBroken and have any clones that are stuck in 'Recovery Pending' dropped and removed from the metadata.
Latest version of dbaclone as of writing
0.10.68
Additional context
I can put up a PR for this

@sanderstad Any thoughts?