Scatter over Image

Hi,
I'm currently trying to do a scatter over an image. But my image is not interactive, i can scatter plot around it and drag the point plotted over the image but whenever i try to plot over it directly nothing happen and I can't even have a callback when my image is clicked. Ideally I would like to update my scatter plot with the x and y position  clicked over the image.
Do you have any idea of how to proceed? In fact if the image worked as a background, everything would work fine.
Thank you in advance
from bqplot import *
from IPython.display import display

import ipywidgets as widgets
import os

image_path = os.path.abspath("Path to the image")

with open(image_path, 'rb') as f:
    raw_image = f.read()
ipyimage = widgets.Image(value=raw_image, format='jpg', disabled=True)
scales = {'x': LinearScale(min=-1, max=2), 'y': LinearScale(min=-0.5, max=2)}
image = Image(image=ipyimage, scales=scales)
size = 100
np.random.seed(0)
x_data = range(size)
y_data = np.cumsum(np.random.randn(size) * 100.0)

sc_x = LinearScale()
sc_y = LinearScale()

scat = Scatter(x=x_data[:10], y=y_data[:10], scales={'x': sc_x, 'y': sc_y}, default_colors=['blue'],
               enable_move=True)

ax_x = Axis(scale=sc_x)
ax_y = Axis(scale=sc_y, tick_format='0.2f', orientation='vertical')
scat.interactions = {'click': 'add'}

def callback(_, target):
    print(target)

image.on_click(callback)
image.interactions= {'click': 'add'}

fig = Figure(marks=[image, scat], axes=[ax_x, ax_y])

with scat.hold_sync():
    scat.enable_move = True
    scat.update_on_move = True
    scat.enable_add = True

image.x = [-1, 2]
image.y = [-.5, 2]

display(fig)

Hi @ifollowbenoit. This feature has been very recently added in master (PR #692). You can pull from master and take a look at the Image example notebook to check out how it works.

Thank you very much. I tried to run the following examples with the last version and it doesn't seems to be working anymore.
https://github.com/bloomberg/bqplot/blob/master/examples/Marks/Object Model/Image.ipynb
In fact every kind plots work fine except for the  marks=[image] plot, could you fix this issue please?
Thank you

Yes indeed that is a bug. I've issued a fix in #792 it should be merged soon.

Hi @ifollowbenoit. This feature has been very recently added in master (PR #692). You can pull from master and take a look at the Image example notebook to check out how it works.

Can you link the example notebook?

Hi @ifollowbenoit. This feature has been very recently added in master (PR #692). You can pull from master and take a look at the Image example notebook to check out how it works.

Can you link the example notebook?

Nvm I guess it's here:
https://github.com/bloomberg/bqplot/blob/master/examples/Marks/Object Model/Image.ipynb
Also, would anyone happen to know the easiest way to just plot a draggble point on an image with a callback whenever it's moved? I'd like to be able to update another plot as the point is moved... if there's an example in a notebook somewhere that would be greatly appreciated...


Technical Documentation

The documentation and architecture on fimd and fim-controller repos (just in a README for now?):

[ ] prerequisites

[ ] permission to watch procfs, docker.sock, docker.pid, cgroups
[x] multi-tenancy environment will not work due to permissions needed

[x] configuration params and how they work

[x] selector
[x] subjects array (events/paths as single/multiple, recursive, ignore, onlyDir flags)
[x] logFormat

[x] how the controller interacts with the k8s lifecycle, system
[ ] how the daemon spawns child processes for inotify, mqueue, etc.
[ ] how the daemon finds PID given a containerID
[x] how the controller<-->daemon interacts with each other
[x] running, stopping these components
[ ] what permissions (scc in openshift, etc.) they require
[x] creating a FimWatcher for an app deployment, other kinds; and what syntax it expects; using multiple events/paths different ways
[x] caveats around symlinks, and other procfs gotchas we haven't quite mastered yet (see details of findings and examples at: https://github.com/clustergarage/fimd/issues/9)
[x] running controller with an out-of-cluster -fimd <IP_ADDRESS>:50051 flag locally on minikube or other vm-based solutions, will act differently since it find the pid via cgroups on the host
[ ] logging, examples around sending logging somewhere like ELK, splunk
[ ] specific usage on cloud providers, EKS/GKE, etc.

EKS requires security group, subnet, etc. to be set up a certain way; also, logging needs to be done specifically for this, as the CloudTrail automatic logs only does K8s API calls by default -- use an EFK stack

[x] fimcontroller replicas should be 1 generally; if having >1 it will cause the same event to be fired to the daemon multiple times, which should be idempotent already-- you may just get a create followed by an update
[ ] fimd should schedule out to all nodes that can handle compute -- if it has a taint then an explicit toleration will need to be added to the fimd demonset to schedule them out on these; this will not be an option that we provide, it will be up to the user based on their use-case
[x] cleaning up CRDs manually since delete all --all doesnt delete  custom types in namespace

Let's step through this tomorrow, especially sections around defining a watcher.


8 idle bots but test not running

This test isn't being run, but it looks like there are many idle bots.
https://ci.chromium.org/p/flutter/builders/prod/Mac_ios new_gallery_impeller_ios__transition_perf

This can happen when the bots don't have the right caches to run the tests.

These bots have run tests since this issue was created.

Closing as not an issue.


Error at tutorial visualization step

When I enter the command:
[path-to-pysb]/pysb/tools/render_reactions.py [path-to-pysb-model-file]/mymodel.py > mymodel.dot
Replacing with appropriate path names as instructed, I get the following error:
NameError: name 'mymodel' is not defined
What may cause this? Thank you

Could you provide the entire stack trace from your terminal? It would be helpful to see the exact line that's failing as well as everything leading up to it.

Thank you for your reply, here is the entire error message:
'C:/Users/.../anaconda3/pkgs/pysb-1.14.0-py_0/site-packages/pysb/tools/render_reactions.py' 'C:/Users/.../anaconda3/Scripts/PySB/mymodel.py' > mymodel.dot
Traceback (most recent call last):
Input In [14] in <cell line: 1>
'C:/Users/.../anaconda3/pkgs/pysb-1.14.0-py_0/site-packages/pysb/tools/render_reactions.py' 'C:/Users/.../anaconda3/Scripts/PySB/mymodel.py' > mymodel.dot
NameError: name 'mymodel' is not defined

It looks like you are entering the command as a cell in a Jupyter notebook. That command as written must be run from the shell instead. If you want to run the visualization from a notebook you'll need Python code:
First, delete the line import mymodel as m. The Model object is already available under the variable model. Next you will need to add the following import lines:
from IPython.display import SVG
import pygraphviz
import pysb.tools.render_reactions

Then we call the pysb render_reactions tool and store the result as a GraphViz graph object in g:
g = pygraphviz.AGraph(string=pysb.tools.render_reactions.run(model))

Finally we call graphviz to perform layout and SVG rendering, displaying the SVG inline in the notebook:
SVG(g.draw(prog="dot", format="svg"))


⚙ Need a Change Log

Discussed in https://github.com/SamErde/PSPreworkout/discussions/10

Originally posted by jdhitsolutions September 11, 2024
I don't see that your module has a changelog. I suggest installing and using the ChangeLogManagement module.

Added a changelog and still reviewing the ChangeLogManagement module.

I have created a change log, and for now have opted for a manual approach to updating it. My workflow for publishing the module and new GitHub releases is triggered whenever I tag a commit that matches a version header in the changelog file. (Now that I think about it, I may update that GitHub action and filter the trigger to specifically look for changes to the CHANGELOG.md file.)


Support select * from ... where schema is not known at compile time

(originally asked on discord: https://discord.com/channels/632277896739946517/839844929877704785/977322704363479050)
I need to query a table where the schema is not known at compile time. That means I'd like to do a select * from dynamicTable and get
an Array[String | null] for every row, which I can further process according to the types I know at runtime.
Low-level types in the array would also be ok, since I can cast them accordingly. But I need to know if a field is null or not.
So far in ScalaJS, it seems like I'm stuck with with pg-node and use their rowmode: 'array' feature (https://node-postgres.com/features/queries)

The low-level protocol produces a List[Option[String]] which is what you want, but there's no way to get to it through the provided interfaces. It could be done by modifying Query to know that the result is dynamic in order to selectively bypass arity/type checking.

That sounds sufficient, thank you!

I think I'll approach this soon. What would be the rough steps to implement it?


Consider moving jupyterlab out of install_requires

Description of the feature
Jupyter Lab and its dependencies add significant download and install weight.
Steps for implementing the feature
If Jupyter Lab is not required except for the example ipynb files, consider moving this dependency out of setup.py install_requires and into a new requirements file like requirements-examples.txt.
Useful links and references
No response

@isaacansys I agree. I'm implementing it. I leave in pyvista, matplotlib and numpy as they are actively used in different methods


Why "Use hardware DCC control" is greyed out on iMac 27" Monterey and MBP 15" Big Sur?

Before opening the issue, have you...?

[X] Searched for existing issues

Question
I want to reset the DCC value of the  "Use hardware DCC control" but this is greyed out on both iMac 27" Monterey and MBP 15" Big Sur.
I am using them with a 27" Thunderbold Cinema Display, can not change the max brightness settings.
Any idea what might be wrong?

Can you provide a screenshot?


Ziya has copied/modified Rails code - will this work with Rails 4?

Ziya has been not maintained outside our fork since 2010: https://github.com/derailed/ziya/network, we resurrected it to get it to work with ruby 1.9 and rspec 2 (was last supported at rspec 1).
Ziya has code that code that was taken from Rails so who knows if this code will work going forward towards rails 4:
https://github.com/ManageIQ/ziya/blob/a7f0baf4cee6347aedd850d1b7e75d84632facb1/lib/ziya/html_helpers/base.rb#L43

@dclarizio If this issue is resolved, please close with comment.

I am not sure.  Since we now have Rails 4 upstream, we will need to verify that the Ziya code paths still work downstream.  @gtanzillo and I will have to look into this.

@jrafanie Now that we're on Rails 5 and rspec 3, still relevant?

Closed by #12122


fix increase JVM memory of BE

Because test_trino_hive_tpch_sf1_parquet case may cause BE JVM OOM, we increase JVM memory of BE.

run buildall

run buildall


fix: 4]. Projects/Web Development/JavaScript Projects/02]. Blog Page …

Have you read the Contributing Guidelines?

[x] YES

PHP 7.2 has reached its end-of-life (EOL) and no longer receives security updates.
faster execution times and reduced resource consumption.
7.4 has deprecated several features and functions, upgrading helps future-proof your codebase.
Upgrading to a newer version of PHP ensures better compatibility with modern libraries and frameworks, which may no longer support older versions of PHP.


gha: Rename ConformanceKind1.19 to ConformanceKind

After #22325 is merged, this job is no longer using k8s 1.19, so it's better to rename the job to just ConformanceKind to avoid any potential confusion.
Signed-off-by: Tam Mach<EMAIL_ADDRESS>

@sayboras Why are we backporting this all the way to v1.11? It seems fairly minor.

yup, we can skip backport for older releases 💯


Problem when showing WebView in drawer (maybe also in tab)

Version
react-native-router-flux v3.36.0
react-native v0.34.0
Actual behaviour
When one of the tabs in drewer-wrapped tab set is or contains a WebView, after switching to that tab the WebView stays on top even when drawer then switches to different tab. Logically (touches, events, etc.) the new screen is active; but what is actually shown, is the old one with the WebView.

I have same issue which is something like this issue.
Would you please help me?


Cannot download Ego-Exo4D dataset

Hi there. Thank you very much for your great work!
I got the approval of the dataset access, and got started downloading the dataset.
However no matter how many times I tried with different options, e.g. --parts metadata, annotations, I ended up failing to download those data like below.
It seems that some fetch errors happen at some point early.
I would be glad if you could share how to download safely.

egoexo -o ./egoexo --parts annotations --s3_profile egoexo4d
Determining what to download ...
100%|██████████████████████████████████████████████████████████████████████| 11/11 [00:04<00:00,  2.43it/s]
Checking current download status ...
100%|██████████████████████████████████████████████████████████████████████| 11/11 [00:01<00:00,  6.66it/s]
Downloaded: 0.000% = 0.000GiB / 1.035GiB (0 / 11 files) downloaded
Expected size of downloaded files is 1.0 GiB (11 files). Do you want to start the download? ([y]/n): y
Preparing output directories ...
100%|██████████████████████████████████████████████████████████████████████| 1/1 [00:00<00:00,  7.18it/s]
Downloading ...
Fetching: 1.035GiB
5%|████▊                                                                                | 56.0M/1.03G [00:08<01:20, 13.0MiB/s]WARN: failed to fetch 11 files [integrity=0, exceptions=11]
Please retry the download (... returning with error code 2)
6%|█████                                                                                | 58.4M/1.03G [00:09<02:43, 6.44MiB/s]

Sorry about this post. This was because of my aws storage setting.
Resolved.


Update version: Transmission.Transmission version 4.0.5

Pull request has been created with WinGet Automation 🪟📦🤖
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335226 2024-01-16 15:28:33.094 [CLI ] ShellExecute installer failed: 1603 MSI (s) (9C:EC) [15:28:12:796]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (9C:80) [15:28:13:749]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [1630:0B98][2024-01-16T15:28:10]w363: Could not create system restore point, error: 0x80070422. Continuing... Property(S): ErrorDialog = ErrorDlg MSI (s) (9C:C8) [15:28:32:906]: Product: Transmission 4.0.5 (a6fe2a64aa) (x64) -- Installation failed. MSI (s) (9C:C8) [15:28:32:906]: Windows Installer installed the product. Product Name: Transmission 4.0.5 (a6fe2a64aa) (x64). Product Version: 4.0.5. Product Language: 1033. Manufacturer: Transmission Project. Installation success or error status: 1603.

(Automated response - build 575.)

Automatic Validation ended with:

Automatic Validation ended with:

Installation failed with exit code -1978335226 2024-01-16 15:28:33.094 [CLI ] ShellExecute installer failed: 1603 MSI (s) (9C:EC) [15:28:12:796]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (9C:80) [15:28:13:749]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [1630:0B98][2024-01-16T15:28:10]w363: Could not create system restore point, error: 0x80070422. Continuing... Property(S): ErrorDialog = ErrorDlg MSI (s) (9C:C8) [15:28:32:906]: Product: Transmission 4.0.5 (a6fe2a64aa) (x64) -- Installation failed. MSI (s) (9C:C8) [15:28:32:906]: Windows Installer installed the product. Product Name: Transmission 4.0.5 (a6fe2a64aa) (x64). Product Version: 4.0.5. Product Language: 1033. Manufacturer: Transmission Project. Installation success or error status: 1603.

(Automated response - build 582.)

1603 might indicate that "a reboot is required".


Getting data from PodcastIndex

See https://github.com/EngineeringKiosk/GermanTechPodcasts/pull/5

Done already <3


Convert Array to ReadonlyArray/Push in commandLineParser.ts

Definitely makes it easier to read and follow the logic. Thanks for that!


How to set a proxy

Summary
The "apiEndpoint" option does not appear to be working for setting a proxy. Is there a new way to do this with the typescript SDK?

Hi @davidbergso  thanks for submitting this question.
To set a proxy, you can set the option serverUrl when you initialize amplitude.
amplitude.init('API_KEY', 'USER_ID', { serverUrl: "proxy url" });

Hello, thanks for the response on this. Just a question, is there any reason why in the typescript API it is called serverUrl and in the JS one it is apiEndpoint? It seems a bit inconsistent.


http://./ is a valid url

http://./ as an input is valid for both safari & chrome, but it's invalid for us.

I'm reopening this because we were skipping this URL in the input, but we shouldn't have.

Why? The standard is clear on this. Labels must be between 1 and 63 bytes. If we misread the standard, can you quote the relevant section?

I've not looked into the spec for this, but: there is a particular section in WPT labeled "domains with empty labels": https://github.com/web-platform-tests/wpt/blob/master/url/resources/urltestdata.json#L3889

RFC 1034: Internally, programs that manipulate domain names should represent them
as sequences of labels, where each label is a length octet followed by
an octet string.  Because all domain names end at the root, which has a
null string for a label, these internal representations can use a length
byte of zero to terminate a domain name.

One label is reserved, and that is
the null (i.e., zero length) label used for the root.

A label may contain zero to 63 characters. The null label, of length zero, is reserved for the root zone. https://en.m.wikipedia.org/wiki/Domain_Name_System

Can you open an issue to the web-platform-tests repository? Even though you're right, removing this test from the Node repository without changing the WPT won't be possible.

"The hierarchy of domains descends from the right to the left label in the name; each label to the left specifies a subdivision, or subdomain of the domain to the right. For example: the label example specifies a node example.com as a subdomain of the com domain, and www is a label to create www.example.com, a subdomain of example.com. Each label may contain from 1 to 63 octets. The empty label is reserved for the root node and when fully qualified is expressed as the empty label terminated by a dot. The full domain name may not exceed a total length of 253 ASCII characters in its textual representation.” https://en.m.wikipedia.org/wiki/Domain_name

Seems related to this: https://github.com/servo/rust-url/issues/554
So something can be an invalid URL, but still pass through the algorithm.

About the link that Yagiz provided (WPT tests),
All the tests/examples of the section mentioned (domains with empty labels) are not FQDN (fully qualified domain names)
To be considered FQDN, the domain name must include a Second-Level Domain (SLD) and a Top-Level Domain (TLD).
An example of FQDN is www.example.com, where "www" is the hostname (not required), "example" is the second-level domain (SLD), and ".com" is the top-level domain (TLD).

I'm looking for references that state these limits/sizes/rules only apply to FQDNs.

I'm looking for references that state these limits/sizes/rules only apply to FQDNs.

I couldn't find anything

@miguelteixeiraa  I think we should add a method to the URL struct such as bool is_fully_qualified_domain_name() const and that method would check that it is indeed a Fully qualified domain name, possibly adding other checks.

I'm looking for references that state these limits/sizes/rules only apply to FQDNs.

I don't think they do.

apply the rules only when there is the basic structure to be a fqdn (at least 2 non-zero labels) )

My proposal is rather to parse successfully the URL, irrespective of label lengths and so forth, but to have a method like is_valid_domain() const that does additional checks.

@anonrig I don't think that http://./  is a valid URL. To prove me wrong, please register it. I don't think you can.
It is a valid URL string as per https://url.spec.whatwg.org/ But that link mentions RFC 1034 only once, in passing, and does not appear to try to abide by it at all.

To be clear, I still think it is fine to accept to parse it…

@anonrig
Is this resolved?

We can close this for now 👍


Makefile: install manpages via install-docs target

This lets users install binaries without installing the docs, which will help e.g. users who don't have a new enough Asciidoc: https://github.com/newsboat/newsboat/issues/829
Reviews welcome! Will merge in three days.

Coverage remained the same at 54.201% when pulling 7c3a0eddb6c070511c05cea83a158ce768fc44b0 on feature/move-manpages-to-install-docs into 1bc5d4a805a323d5f8c144e5fccc9c6c7332c439 on master.

Updated the docs as well. Too lazy to create a separate PR just for that, hope reviewers cut me some slack on that one :)


Why toga.MultilineTextInput does not work?

I tried to write a MultilineTextInput demo, however nothing appeared

My platform: Mac OS X 10.11.5
My code:
import toga

def build(app):
    container = toga.Container()
    msg = toga.MultilineTextInput('initialize')
    container.add(msg)
    container.constrain(msg.TOP == container.TOP + 50)
    container.constrain(msg.LEADING + 50 == container.LEADING)
    container.constrain(msg.TRAILING + 50 == container.TRAILING)
    container.constrain(msg.BOTTOM + 50 < container.BOTTOM)

    return container

if __name__ == '__main__':
    app = toga.App('MultilineTextInput', 'com.identifier.app', startup=build)
    app.main_loop()

You're assigning your constraints incorrectly. The arithmetic should be on the right side of the == evaluation. Try this:
import toga

def build(app):
    container = toga.Container()
    msg = toga.MultilineTextInput('initialize')
    container.add(msg)
    container.constrain(msg.TOP == container.TOP + 10)
    container.constrain(msg.LEADING == container.LEADING + 10)
    container.constrain(msg.TRAILING == container.TRAILING - 10)
    container.constrain(msg.BOTTOM == container.BOTTOM - 10)
    return container

if __name__ == '__main__':
    app = toga.App('My App', 'com.identifier.app', startup=build)
    app.main_loop()

Thanks @elstob , but it works if I replace < with == whether the arithmetic is on the right or on the left.
However, the same constrains work with a Button ! what a confusing issue...
def build(app):
    container = toga.Container()
    msg = toga.MultilineTextInput('initialize')
    container.add(msg)
    container.constrain(msg.TOP == container.TOP + 10)
    container.constrain(msg.TOP == container.TOP + 50)
    container.constrain(msg.LEADING == container.LEADING + 50)
    container.constrain(msg.TRAILING + 50 == container.TRAILING)
    container.constrain(msg.BOTTOM + 50 < container.BOTTOM)
    return container

def build_btn(app):
    container = toga.Container()
    button = toga.Button('Hello world')
    container.add(button)
    container.constrain(button.TOP == container.TOP + 50)
    container.constrain(button.LEADING == container.LEADING + 50)
    container.constrain(button.TRAILING + 50 == container.TRAILING)
    container.constrain(button.BOTTOM + 50 < container.BOTTOM)
    return container

@tangshi Sorry to hear you're having problems. It's entirely possible you're hitting a bug in Toga itself. There are some situations where Apple's default constraint rules kick in and override the behavior you've specified manually. Multiline text widgets are one of the most affected, because there are several underlying widgets involved.
It's because of problems like this one that I'm in the process of replacing the constraint-based layout system with a new approach based on CSS. Constraints are lovely... when they work. When they don't, they're almost impossible to debug. To make matters worse, there are some subtle differences in the implementation of Cassowary between platforms that make a consistent layout very difficult to coordinate.
You can see the work in progress on the "colosseum" branch of this repository; it's not quite ready for public use, but if you're feeling adventurous, you can experiment a bit.

@freakboy3742 So sad, I just need a simple gui framework to create a demo

@tangshi Totally understandable. Hopefully Toga will be able to fill that role in the near future.
I'll close this ticket on the basis that there's nothing specific that can be (or is going to be) addressed.


Elevation data view

Hi,
I want to after right-click and see elevation data like below link?
"https://esri.github.io/esri-leaflet/examples/identifying-imagery.html"
Thanks.

You can look at the code for the demo app, which does more or less this: http://www.liedman.net/elevation-service/

I'm currently working on a project leaflet.
If possible, can you make it like leaflet plugin?
Thanks.


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installer hash mismatch.
Brief description of your issue
Tried installing Vencord using winget in PowerShell 7.4.3. Came up with an error "Installer hash does not match."
Did not run winget using administrative privileges.
Steps to reproduce

Open Windows Terminal.
Run winget install Vendicated.Vencord

Actual behavior
After finished downloading the package, an error came up "Installer hash does not match."
Expected behavior
Install the package normally like any other packages.
Environment
Windows Package Manager v1.8.1791
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.3810
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.23.1791.0

Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
DefaultProxy                              Disabled

Screenshots and Logs
WinGet-2024-06-30-22-52-52.444.log

That is a really old version, will update


Update to Grafana 10.2.1

Update to Grafana 10.2.1
Update ESLint configuration using @volkovlabs/eslint-config

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

Comparison is base (864d617) 98.17% compared to head (5f8374f) 98.17%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #98   +/-   ##
=======================================
  Coverage   98.17%   98.17%
=======================================
  Files          52       52
  Lines         877      877
  Branches      187      188    +1
=======================================
  Hits          861      861
  Misses          2        2
  Partials       14       14

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


Intel Edison arduino edition + I2C Motor Driver + Base Shield V2 (

(i2cdetect)

I2C motor driver is contact to I2C on the Base Shield V2
it does not detect the I2C Motor Driver.
any suggestions?

Do you have an Arduino board? Could you try scan the I2C motor driver under Arduino?
// --------------------------------------
// i2c_scanner
//
// Version 1
//    This program (or code that looks like it)
//    can be found in many places.
//    For example on the Arduino.cc forum.
//    The original author is not know.
// Version 2, Juni 2012, Using Arduino 1.0.1
//     Adapted to be as simple as possible by Arduino.cc user Krodal
// Version 3, Feb 26  2013
//    V3 by louarnold
// Version 4, March 3, 2013, Using Arduino 1.0.3
//    by Arduino.cc user Krodal.
//    Changes by louarnold removed.
//    Scanning addresses changed from 0...127 to 1...119,
//    according to the i2c scanner by Nick Gammon
//    http://www.gammon.com.au/forum/?id=10896
// Version 5, March 28, 2013
//    As version 4, but address scans now to 127.
//    A sensor seems to use address 120.
//
//
// This sketch tests the standard 7-bit addresses
// Devices with higher bit address might not be seen properly.
//

#include <Wire.h>

void setup()
{
  Wire.begin();

  Serial.begin(9600);
  Serial.println("\nI2C Scanner");
}

void loop()
{
  byte error, address;
  int nDevices;

  Serial.println("Scanning...");

  nDevices = 0;
  for(address = 1; address < 127; address++ )
  {
    // The i2c_scanner uses the return value of
    // the Write.endTransmisstion to see if
    // a device did acknowledge to the address.
    Wire.beginTransmission(address);
    error = Wire.endTransmission();

    if (error == 0)
    {
      Serial.print("I2C device found at address 0x");
      if (address<16)
        Serial.print("0");
      Serial.print(address,HEX);
      Serial.println("  !");

      nDevices++;
    }
    else if (error==4)
    {
      Serial.print("Unknow error at address 0x");
      if (address<16)
        Serial.print("0");
      Serial.println(address,HEX);
    }
  }
  if (nDevices == 0)
    Serial.println("No I2C devices found\n");
  else
    Serial.println("done\n");

  delay(5000);           // wait 5 seconds for next scan
}

Sure,
Here is the result:

Also tried with and Grove 6Axis accelerometer & Gyroscope v1.0
here is the result:

As you can see the I2C motor driver cant be find.
The Motor Driver works because I can run it with UPM.

Have a look by this issue https://github.com/Seeed-Studio/Grove_I2C_Motor_Driver/issues/1
The new firmware has fixed this problem.


K-9 Keeps loosing my account settings

This is the second time this has happened. I open K-9 and I'm greeted with the account setup screen. As far as I can tell my account and all settings are gone. I suspect this may have happened during an app update, but I don't know when an update may have occurred or when it broke.
Environment
K-9 Mail version: 5.010
Android version: 7.0
Account type (IMAP, POP3, WebDAV/Exchange): IMAP, Dovecot

See #750. Nothing we can do without more information.


Minor code refactoring in redis_connection.py

https://github.com/walker76/stackoversight/blob/e9255c687662c16469d9b8f3fb5df4cf9a180eb8/stackoversight/taskqueue/redis_connection.py#L31
Can be written as:
redis_host = os.getenv("REDIS_HOST", "localhost")

This will be resolved in branch testing_pipe when the PR is merged


Add React-TextArea-Autosize AI Bot in Readme

This Gen AI chatbot will help Developers understand this repository better. You can ask for code examples, installation guide, debugging help and much more.

I think this is a form of an unsolicited advertisement.


Allow message components to be selectable from the UI

For citizen integrators, a great feature available in Azure LogicApps, is the ability to construct message schemas visually, as shown here https://docs.microsoft.com/en-us/azure/logic-apps/media/logic-apps-perform-data-operations/send-email-parse-json-action.png
I would be happy to work on this, is there a starting guide?

It is not that simple, because Camel keep data in the message container (Exchange).
Exchange contains message body, headers, etc.
Body and header values are Java objects and might contain data in various formats (XML, JSON, YAML, binary, etc)
Visual Constructor for them is a huge project.
I don't even know where to start

Data mapping is in RoadMap for 2023 https://camel.apache.org/blog/2022/10/camel-karavan-roadmap/


Program Crash with Name Edits

During the event, when editing the rider name SilverSprints would crash. Any ideas on why/how to prevent and allow for name edits to not do this?

Sorry to hear it! Could you tell me which version of Silversprints you were running, and what operating system?  If you have more detailed instructions on how to replicate that would help me too.  For example: "Run a race, click the gear, and then try to type a different name. It crashes as soon as you click in the box"  or however it happened.

Running latest release 1.7.1 on macOS 10.13.6 I've been getting random crashing mid-race, moreso, although app did crash (once) while editting name in the roster view after modifying player count to 2.
Here's the relevant line from Apple's crash report:
Application Specific Information:
terminating with uncaught exception of type boost::filesystem::filesystem_error: boost::filesystem::create_directory: Read-only file system: "/private/var/folders/b2/d5s5m5952j1gt7yfrl5t6pfm0000gn/T/AppTranslocation/0795BA62-8680-49C6-9276-5C990AD5BB22/d/logs"
abort() called

..Based on this, looks like it may be dying when attempting to log, so perhaps it's occurring at race end, when the victor animations start. I have the full crashlog saved if you're like me to share
I've had much more stable usage when running the executable from my command line, with the addition of helpful terminal output.
cd ./SilverSprint.app/Contents/MacOS
./SilverSprint

Crashing issues are seemingly nonexistant when executed this way, or when building from my latest (dev branch) source in Xcode.. although I have not been successful packaging build as an .app. Archive is created but it crashes on launch due to resources not getting bundled properly:
|fatal  | void cinder::app::AppBase::executeLaunch()[197] Uncaught exception, type: cinder::app::AssetLoadExc, what: Failed to load asset with relative path: fonts/UbuntuMono-R.ttf
libc++abi.dylib: terminating with uncaught exception of type cinder::app::AssetLoadExc: Failed to load asset with relative path: fonts/UbuntuMono-R.ttf
Abort trap: 6

If you have any tips 'n' tricks in bundling all req'd assets into the .app archive, that'd be super helpful!


fix api doc for setWebpackOptimizationSplitChunks

fix api doc for setWebpackOptimizationSplitChunks method. BTW, this method does not publish on the latest release, but it appear in the api doc of master branch. This makes me confused when I call setWebpackOptimizationSplitChunks method.

Thanks for fixing that, and pointing out the docs issue! I will get all the recent changes published asap so code reflects the docs.

Also added you to our contributors list, thanks for taking part :)


Feature: Commands API support.

This PR adds support for the Commands API.

@xxuejie  Ready for review.

Sorry for the delay, this is looking good to me. Merging now, thanks a lot!


Unable to resolve outputs.result variable

Summary
Once upgraded to v3.0.0, on some workflows we have started getting "Unabe to resolve: " error.
I have managed to reproduce something somewhat simpler (attached below).
Notice that this is triggered by submitting outer wf template argo submit --from wftmpl/greet-many --entrypoint=greet, but not if submitting any inner template (argo submit --from wftmpl/greet-script --entrypoint=runme or argo submit --from wftmpl/greet-pipeline --entrypoint=greet -p name=test).
Diagnostics
What Kubernetes provider are you using?
GKE
What version of Argo Workflows are you running?
v3.0.0
kubectl get wf -o yaml ${workflow}
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  creationTimestamp: "2021-04-06T13:54:24Z"
  generateName: greet-many-
  generation: 5
  labels:
    workflows.argoproj.io/completed: "true"
    workflows.argoproj.io/phase: Error
    workflows.argoproj.io/workflow-template: greet-many
  name: greet-many-n546s
  namespace: argo
  resourceVersion: "1462800323"
  selfLink: /apis/argoproj.io/v1alpha1/namespaces/argo/workflows/greet-many-n546s
  uid: 84198879-0361-4c56-b150-40852f089fdf
spec:
  arguments: {}
  entrypoint: greet
  workflowTemplateRef:
    name: greet-many
status:
  artifactRepositoryRef:
    configMap: artifact-repositories
    key: docker-images-v1
    namespace: argo
  conditions:
  - status: "False"
    type: PodRunning
  - status: "True"
    type: Completed
  estimatedDuration: 20
  finishedAt: "2021-04-06T13:54:54Z"
  nodes:
    greet-many-n546s:
      children:
      - greet-many-n546s-4131247613
      displayName: greet-many-n546s
      estimatedDuration: 20
      finishedAt: "2021-04-06T13:54:54Z"
      id: greet-many-n546s
      name: greet-many-n546s
      phase: Error
      progress: 7/7
      resourcesDuration:
        cpu: 7
        memory: 7
      startedAt: "2021-04-06T13:54:24Z"
      templateName: greet
      templateScope: local/
      type: DAG
    greet-many-n546s-322302338:
      boundaryID: greet-many-n546s-1466455155
      displayName: hello-hello-mate
      finishedAt: "2021-04-06T13:54:47Z"
      id: greet-many-n546s-322302338
      inputs:
        parameters:
        - name: name
          value: '{{tasks.hello-mate.outputs.result}}'
      name: greet-many-n546s.greet-many(2:3).greet.hello-hello-mate
      outputs:
        exitCode: "0"
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2021-04-06T13:54:44Z"
      templateRef:
        name: greetings
        template: hello
      templateScope: namespaced/greet-script
      type: Pod
    greet-many-n546s-659425408:
      boundaryID: greet-many-n546s-1677791073
      displayName: hello-hello-mate
      finishedAt: "2021-04-06T13:54:47Z"
      id: greet-many-n546s-659425408
      inputs:
        parameters:
        - name: name
          value: '{{tasks.hello-mate.outputs.result}}'
      name: greet-many-n546s.greet-many(1:2).greet.hello-hello-mate
      outputs:
        exitCode: "0"
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2021-04-06T13:54:44Z"
      templateRef:
        name: greetings
        template: hello
      templateScope: namespaced/greet-script
      type: Pod
    greet-many-n546s-900412106:
      boundaryID: greet-many-n546s-3996515851
      displayName: hello-hello-mate
      finishedAt: "2021-04-06T13:54:47Z"
      id: greet-many-n546s-900412106
      inputs:
        parameters:
        - name: name
          value: '{{tasks.hello-mate.outputs.result}}'
      name: greet-many-n546s.greet-many(0:1).greet.hello-hello-mate
      outputs:
        exitCode: "0"
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2021-04-06T13:54:44Z"
      templateRef:
        name: greetings
        template: hello
      templateScope: namespaced/greet-script
      type: Pod
    greet-many-n546s-1466455155:
      boundaryID: greet-many-n546s-1705868220
      children:
      - greet-many-n546s-3765256469
      displayName: greet
      estimatedDuration: 10
      finishedAt: "2021-04-06T13:54:54Z"
      id: greet-many-n546s-1466455155
      message: 'task ''greet-many-n546s.greet-many(2:3).greet'' errored: Unable to
        resolve: {{tasks.hello-mate.outputs.result}}'
      name: greet-many-n546s.greet-many(2:3).greet
      phase: Error
      progress: 2/2
      resourcesDuration:
        cpu: 2
        memory: 2
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greet-script
        template: runme
      templateScope: namespaced/greet-pipeline
      type: DAG
    greet-many-n546s-1677791073:
      boundaryID: greet-many-n546s-3505501614
      children:
      - greet-many-n546s-2182697927
      displayName: greet
      estimatedDuration: 10
      finishedAt: "2021-04-06T13:54:54Z"
      id: greet-many-n546s-1677791073
      message: 'task ''greet-many-n546s.greet-many(1:2).greet'' errored: Unable to
        resolve: {{tasks.hello-mate.outputs.result}}'
      name: greet-many-n546s.greet-many(1:2).greet
      phase: Error
      progress: 2/2
      resourcesDuration:
        cpu: 2
        memory: 2
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greet-script
        template: runme
      templateScope: namespaced/greet-pipeline
      type: DAG
    greet-many-n546s-1705868220:
      boundaryID: greet-many-n546s
      children:
      - greet-many-n546s-1466455155
      displayName: greet-many(2:3)
      estimatedDuration: 10
      finishedAt: "2021-04-06T13:54:54Z"
      id: greet-many-n546s-1705868220
      inputs:
        parameters:
        - name: name
          value: "3"
      name: greet-many-n546s.greet-many(2:3)
      phase: Error
      progress: 2/2
      resourcesDuration:
        cpu: 2
        memory: 2
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greet-pipeline
        template: greet
      templateScope: local/
      type: DAG
    greet-many-n546s-1962886413:
      boundaryID: greet-many-n546s-3996515851
      children:
      - greet-many-n546s-900412106
      displayName: hello-mate
      estimatedDuration: 2
      finishedAt: "2021-04-06T13:54:37Z"
      id: greet-many-n546s-1962886413
      inputs:
        parameters:
        - name: name
          value: mate
      name: greet-many-n546s.greet-many(0:1).greet.hello-mate
      outputs:
        exitCode: "0"
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greetings
        template: hello
      templateScope: namespaced/greet-script
      type: Pod
    greet-many-n546s-2182697927:
      boundaryID: greet-many-n546s-1677791073
      children:
      - greet-many-n546s-659425408
      displayName: hello-mate
      estimatedDuration: 2
      finishedAt: "2021-04-06T13:54:37Z"
      id: greet-many-n546s-2182697927
      inputs:
        parameters:
        - name: name
          value: mate
      name: greet-many-n546s.greet-many(1:2).greet.hello-mate
      outputs:
        exitCode: "0"
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greetings
        template: hello
      templateScope: namespaced/greet-script
      type: Pod
    greet-many-n546s-2981425008:
      boundaryID: greet-many-n546s
      children:
      - greet-many-n546s-3409845348
      - greet-many-n546s-3505501614
      - greet-many-n546s-1705868220
      displayName: greet-many
      estimatedDuration: 10
      finishedAt: "2021-04-06T13:54:54Z"
      id: greet-many-n546s-2981425008
      name: greet-many-n546s.greet-many
      phase: Error
      progress: 6/6
      resourcesDuration:
        cpu: 6
        memory: 6
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greet-pipeline
        template: greet
      templateScope: local/
      type: TaskGroup
    greet-many-n546s-3409845348:
      boundaryID: greet-many-n546s
      children:
      - greet-many-n546s-3996515851
      displayName: greet-many(0:1)
      estimatedDuration: 10
      finishedAt: "2021-04-06T13:54:54Z"
      id: greet-many-n546s-3409845348
      inputs:
        parameters:
        - name: name
          value: "1"
      name: greet-many-n546s.greet-many(0:1)
      phase: Error
      progress: 2/2
      resourcesDuration:
        cpu: 2
        memory: 2
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greet-pipeline
        template: greet
      templateScope: local/
      type: DAG
    greet-many-n546s-3505501614:
      boundaryID: greet-many-n546s
      children:
      - greet-many-n546s-1677791073
      displayName: greet-many(1:2)
      estimatedDuration: 10
      finishedAt: "2021-04-06T13:54:54Z"
      id: greet-many-n546s-3505501614
      inputs:
        parameters:
        - name: name
          value: "2"
      name: greet-many-n546s.greet-many(1:2)
      phase: Error
      progress: 2/2
      resourcesDuration:
        cpu: 2
        memory: 2
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greet-pipeline
        template: greet
      templateScope: local/
      type: DAG
    greet-many-n546s-3765256469:
      boundaryID: greet-many-n546s-1466455155
      children:
      - greet-many-n546s-322302338
      displayName: hello-mate
      estimatedDuration: 2
      finishedAt: "2021-04-06T13:54:37Z"
      id: greet-many-n546s-3765256469
      inputs:
        parameters:
        - name: name
          value: mate
      name: greet-many-n546s.greet-many(2:3).greet.hello-mate
      outputs:
        exitCode: "0"
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greetings
        template: hello
      templateScope: namespaced/greet-script
      type: Pod
    greet-many-n546s-3996515851:
      boundaryID: greet-many-n546s-3409845348
      children:
      - greet-many-n546s-1962886413
      displayName: greet
      estimatedDuration: 10
      finishedAt: "2021-04-06T13:54:54Z"
      id: greet-many-n546s-3996515851
      message: 'task ''greet-many-n546s.greet-many(0:1).greet'' errored: Unable to
        resolve: {{tasks.hello-mate.outputs.result}}'
      name: greet-many-n546s.greet-many(0:1).greet
      phase: Error
      progress: 2/2
      resourcesDuration:
        cpu: 2
        memory: 2
      startedAt: "2021-04-06T13:54:34Z"
      templateRef:
        name: greet-script
        template: runme
      templateScope: namespaced/greet-pipeline
      type: DAG
    greet-many-n546s-4131247613:
      boundaryID: greet-many-n546s
      children:
      - greet-many-n546s-2981425008
      displayName: iterator
      estimatedDuration: 2
      finishedAt: "2021-04-06T13:54:27Z"
      id: greet-many-n546s-4131247613
      name: greet-many-n546s.iterator
      outputs:
        exitCode: "0"
        result: '["1","2","3"]'
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 1
        memory: 1
      startedAt: "2021-04-06T13:54:24Z"
      templateName: iterator
      templateScope: local/
      type: Pod
  phase: Error
  progress: 7/7
  resourcesDuration:
    cpu: 7
    memory: 7
  startedAt: "2021-04-06T13:54:24Z"
  storedTemplates:
    namespaced/greet-many/greet:
      dag:
        tasks:
        - arguments: {}
          name: iterator
          template: iterator
        - arguments:
            parameters:
            - name: name
              value: '{{item}}'
          depends: iterator
          name: greet-many
          templateRef:
            name: greet-pipeline
            template: greet
          withParam: '{{tasks.iterator.outputs.result}}'
      inputs: {}
      metadata: {}
      name: greet
      outputs: {}
    namespaced/greet-many/iterator:
      inputs: {}
      metadata: {}
      name: iterator
      outputs: {}
      script:
        command:
        - bash
        image: bash:5.1
        name: ""
        resources: {}
        source: |
          echo '["1","2","3"]'
    namespaced/greet-pipeline/greet:
      dag:
        tasks:
        - arguments:
            parameters:
            - name: name
              value: '{{inputs.parameters.name}}'
          name: greet
          templateRef:
            name: greet-script
            template: runme
      inputs:
        parameters:
        - name: name
      metadata: {}
      name: greet
      outputs: {}
    namespaced/greet-script/runme:
      dag:
        tasks:
        - arguments:
            parameters:
            - name: name
              value: mate
          name: hello-mate
          templateRef:
            name: greetings
            template: hello
        - arguments:
            parameters:
            - name: name
              value: '{{tasks.hello-mate.outputs.result}}'
          depends: hello-mate
          name: hello-hello-mate
          templateRef:
            name: greetings
            template: hello
      inputs: {}
      metadata: {}
      name: runme
      outputs:
        parameters:
        - name: greeted
          valueFrom:
            parameter: '{{tasks.hello-mate.outputs.result}}'
    namespaced/greetings/hello:
      inputs:
        parameters:
        - name: name
      metadata: {}
      name: hello
      outputs: {}
      script:
        command:
        - bash
        image: bash:5.1
        name: ""
        resources: {}
        source: |
          echo "Hello {{inputs.parameters.name}}"
  storedWorkflowTemplateSpec:
    arguments: {}
    entrypoint: greet
    templates:
    - dag:
        tasks:
        - arguments: {}
          name: iterator
          template: iterator
        - arguments:
            parameters:
            - name: name
              value: '{{item}}'
          depends: iterator
          name: greet-many
          templateRef:
            name: greet-pipeline
            template: greet
          withParam: '{{tasks.iterator.outputs.result}}'
      inputs: {}
      metadata: {}
      name: greet
      outputs: {}
    - inputs: {}
      metadata: {}
      name: iterator
      outputs: {}
      script:
        command:
        - bash
        image: bash:5.1
        name: ""
        resources: {}
        source: |
          echo '["1","2","3"]'
    workflowTemplateRef:
      name: greet-many

kubectl logs -n argo $(kubectl get pods -l app=argo-workflow-controller -n argo -o name) | grep ${workflow}
time="2021-04-06T13:54:24.322Z" level=info msg="Processing workflow" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:24.331Z" level=info msg="Updated phase  -> Running" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:24.349Z" level=info msg="DAG node greet-many-n546s initialized Running" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:24.349Z" level=info msg="All of node greet-many-n546s.iterator dependencies [] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:24.350Z" level=info msg="Pod node greet-many-n546s-4131247613 initialized Pending" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:24.396Z" level=info msg="Created pod: greet-many-n546s.iterator (greet-many-n546s-4131247613)" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:24.408Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=1462799378 workflow=greet-many-n546s
time="2021-04-06T13:54:34.398Z" level=info msg="Processing workflow" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.403Z" level=info msg="Setting node greet-many-n546s-4131247613 outputs" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.403Z" level=info msg="Updating node greet-many-n546s-4131247613 status Pending -> Succeeded" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.404Z" level=info msg="TaskGroup node greet-many-n546s-2981425008 initialized Running (message: )" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.404Z" level=info msg="All of node greet-many-n546s.greet-many(0:1) dependencies [iterator] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.405Z" level=info msg="DAG node greet-many-n546s-3409845348 initialized Running" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.405Z" level=info msg="All of node greet-many-n546s.greet-many(0:1).greet dependencies [] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.405Z" level=info msg="DAG node greet-many-n546s-3996515851 initialized Running" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.405Z" level=info msg="All of node greet-many-n546s.greet-many(0:1).greet.hello-mate dependencies [] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.406Z" level=info msg="Pod node greet-many-n546s-1962886413 initialized Pending" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.448Z" level=info msg="Created pod: greet-many-n546s.greet-many(0:1).greet.hello-mate (greet-many-n546s-1962886413)" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.448Z" level=info msg="All of node greet-many-n546s.greet-many(1:2) dependencies [iterator] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.449Z" level=info msg="DAG node greet-many-n546s-3505501614 initialized Running" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.449Z" level=info msg="All of node greet-many-n546s.greet-many(1:2).greet dependencies [] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.449Z" level=info msg="DAG node greet-many-n546s-1677791073 initialized Running" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.449Z" level=info msg="All of node greet-many-n546s.greet-many(1:2).greet.hello-mate dependencies [] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.450Z" level=info msg="Pod node greet-many-n546s-2182697927 initialized Pending" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.482Z" level=info msg="Created pod: greet-many-n546s.greet-many(1:2).greet.hello-mate (greet-many-n546s-2182697927)" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.482Z" level=info msg="All of node greet-many-n546s.greet-many(2:3) dependencies [iterator] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.483Z" level=info msg="DAG node greet-many-n546s-1705868220 initialized Running" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.483Z" level=info msg="All of node greet-many-n546s.greet-many(2:3).greet dependencies [] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.483Z" level=info msg="DAG node greet-many-n546s-1466455155 initialized Running" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.483Z" level=info msg="All of node greet-many-n546s.greet-many(2:3).greet.hello-mate dependencies [] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.484Z" level=info msg="Pod node greet-many-n546s-3765256469 initialized Pending" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.520Z" level=info msg="Created pod: greet-many-n546s.greet-many(2:3).greet.hello-mate (greet-many-n546s-3765256469)" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:34.543Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=1462799691 workflow=greet-many-n546s
time="2021-04-06T13:54:34.551Z" level=info msg="cleaning up pod" action=labelPodCompleted key=argo/greet-many-n546s-4131247613/labelPodCompleted
time="2021-04-06T13:54:44.451Z" level=info msg="Processing workflow" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.455Z" level=info msg="Setting node greet-many-n546s-2182697927 outputs" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.455Z" level=info msg="Updating node greet-many-n546s-2182697927 status Pending -> Succeeded" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.455Z" level=info msg="Setting node greet-many-n546s-3765256469 outputs" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.455Z" level=info msg="Updating node greet-many-n546s-3765256469 status Pending -> Succeeded" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.455Z" level=info msg="Setting node greet-many-n546s-1962886413 outputs" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.455Z" level=info msg="Updating node greet-many-n546s-1962886413 status Pending -> Succeeded" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.457Z" level=info msg="All of node greet-many-n546s.greet-many(0:1).greet.hello-hello-mate dependencies [hello-mate] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.458Z" level=info msg="Pod node greet-many-n546s-900412106 initialized Pending" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.508Z" level=info msg="Created pod: greet-many-n546s.greet-many(0:1).greet.hello-hello-mate (greet-many-n546s-900412106)" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.509Z" level=info msg="All of node greet-many-n546s.greet-many(1:2).greet.hello-hello-mate dependencies [hello-mate] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.509Z" level=info msg="Pod node greet-many-n546s-659425408 initialized Pending" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.550Z" level=info msg="Created pod: greet-many-n546s.greet-many(1:2).greet.hello-hello-mate (greet-many-n546s-659425408)" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.551Z" level=info msg="All of node greet-many-n546s.greet-many(2:3).greet.hello-hello-mate dependencies [hello-mate] completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.552Z" level=info msg="Pod node greet-many-n546s-322302338 initialized Pending" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.584Z" level=info msg="Created pod: greet-many-n546s.greet-many(2:3).greet.hello-hello-mate (greet-many-n546s-322302338)" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:44.617Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=1462800003 workflow=greet-many-n546s
time="2021-04-06T13:54:44.625Z" level=info msg="cleaning up pod" action=labelPodCompleted key=argo/greet-many-n546s-2182697927/labelPodCompleted
time="2021-04-06T13:54:44.625Z" level=info msg="cleaning up pod" action=labelPodCompleted key=argo/greet-many-n546s-3765256469/labelPodCompleted
time="2021-04-06T13:54:44.625Z" level=info msg="cleaning up pod" action=labelPodCompleted key=argo/greet-many-n546s-1962886413/labelPodCompleted
time="2021-04-06T13:54:54.510Z" level=info msg="Processing workflow" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.514Z" level=info msg="Setting node greet-many-n546s-322302338 outputs" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.514Z" level=info msg="Updating node greet-many-n546s-322302338 status Pending -> Succeeded" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.514Z" level=info msg="Setting node greet-many-n546s-900412106 outputs" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.514Z" level=info msg="Updating node greet-many-n546s-900412106 status Pending -> Succeeded" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.514Z" level=info msg="Setting node greet-many-n546s-659425408 outputs" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.514Z" level=info msg="Updating node greet-many-n546s-659425408 status Pending -> Succeeded" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.515Z" level=error msg="Mark error node" error="Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo nodeName="greet-many-n546s.greet-many(0:1).greet" workflow=greet-many-n546s
time="2021-04-06T13:54:54.515Z" level=info msg="node greet-many-n546s-3996515851 phase Running -> Error" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.515Z" level=info msg="node greet-many-n546s-3996515851 message: Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.515Z" level=info msg="node greet-many-n546s-3996515851 finished: 2021-04-06 13:54:54.515849192 +0000 UTC" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.515Z" level=error msg="Mark error node" error="task 'greet-many-n546s.greet-many(0:1).greet' errored: Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo nodeName="greet-many-n546s.greet-many(0:1).greet" workflow=greet-many-n546s
time="2021-04-06T13:54:54.515Z" level=info msg="node greet-many-n546s-3996515851 message: task 'greet-many-n546s.greet-many(0:1).greet' errored: Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.515Z" level=info msg="Outbound nodes of greet-many-n546s-3409845348 set to []" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.516Z" level=info msg="node greet-many-n546s-3409845348 phase Running -> Error" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.516Z" level=info msg="node greet-many-n546s-3409845348 finished: 2021-04-06 13:54:54.516012262 +0000 UTC" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.516Z" level=info msg="Checking daemoned children of greet-many-n546s-3409845348" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.516Z" level=error msg="Mark error node" error="Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo nodeName="greet-many-n546s.greet-many(1:2).greet" workflow=greet-many-n546s
time="2021-04-06T13:54:54.516Z" level=info msg="node greet-many-n546s-1677791073 phase Running -> Error" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.516Z" level=info msg="node greet-many-n546s-1677791073 message: Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.516Z" level=info msg="node greet-many-n546s-1677791073 finished: 2021-04-06 13:54:54.516845595 +0000 UTC" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.516Z" level=error msg="Mark error node" error="task 'greet-many-n546s.greet-many(1:2).greet' errored: Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo nodeName="greet-many-n546s.greet-many(1:2).greet" workflow=greet-many-n546s
time="2021-04-06T13:54:54.516Z" level=info msg="node greet-many-n546s-1677791073 message: task 'greet-many-n546s.greet-many(1:2).greet' errored: Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="Outbound nodes of greet-many-n546s-3505501614 set to []" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-3505501614 phase Running -> Error" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-3505501614 finished: 2021-04-06 13:54:54.517030575 +0000 UTC" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="Checking daemoned children of greet-many-n546s-3505501614" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=error msg="Mark error node" error="Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo nodeName="greet-many-n546s.greet-many(2:3).greet" workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-1466455155 phase Running -> Error" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-1466455155 message: Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-1466455155 finished: 2021-04-06 13:54:54.517660981 +0000 UTC" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=error msg="Mark error node" error="task 'greet-many-n546s.greet-many(2:3).greet' errored: Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo nodeName="greet-many-n546s.greet-many(2:3).greet" workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-1466455155 message: task 'greet-many-n546s.greet-many(2:3).greet' errored: Unable to resolve: {{tasks.hello-mate.outputs.result}}" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="Outbound nodes of greet-many-n546s-1705868220 set to []" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-1705868220 phase Running -> Error" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-1705868220 finished: 2021-04-06 13:54:54.517807216 +0000 UTC" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="Checking daemoned children of greet-many-n546s-1705868220" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-2981425008 phase Running -> Error" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s-2981425008 finished: 2021-04-06 13:54:54.517885098 +0000 UTC" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="Outbound nodes of greet-many-n546s set to []" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s phase Running -> Error" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.517Z" level=info msg="node greet-many-n546s finished: 2021-04-06 13:54:54.517981156 +0000 UTC" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.518Z" level=info msg="Checking daemoned children of greet-many-n546s" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.518Z" level=info msg="Updated phase Running -> Error" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.518Z" level=info msg="Marking workflow completed" namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.518Z" level=info msg="Checking daemoned children of " namespace=argo workflow=greet-many-n546s
time="2021-04-06T13:54:54.551Z" level=info msg="Workflow update successful" namespace=argo phase=Error resourceVersion=1462800323 workflow=greet-many-n546s
time="2021-04-06T13:54:54.561Z" level=info msg="cleaning up pod" action=labelPodCompleted key=argo/greet-many-n546s-322302338/labelPodCompleted
time="2021-04-06T13:54:54.561Z" level=info msg="cleaning up pod" action=labelPodCompleted key=argo/greet-many-n546s-900412106/labelPodCompleted
time="2021-04-06T13:54:54.561Z" level=info msg="cleaning up pod" action=labelPodCompleted key=argo/greet-many-n546s-659425408/labelPodCompleted

apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: greet-many
spec:
  templates:
  - name: greet
    dag:
      tasks:
      - name: iterator
        template: iterator
      - name: greet-many
        depends: "iterator"
        templateRef:
          name: greet-pipeline
          template: greet
        arguments:
          parameters:
            - name: name
              value: "{{item}}"
        withParam: "{{tasks.iterator.outputs.result}}"
  - name: iterator
    script:
      image: bash:5.1
      command: [bash]
      source: |
        echo '["1","2","3"]'
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: greet-script
spec:
  templates:
  - name: runme
    outputs:
      parameters:
        - name: greeted
          valueFrom:
            parameter: "{{tasks.hello-mate.outputs.result}}"
    dag:
      tasks:
      - name: hello-mate
        templateRef:
          name: greetings
          template: hello
        arguments:
          parameters:
          - name: name
            value: "mate"
      - name: hello-hello-mate
        depends: "hello-mate"
        templateRef:
          name: greetings
          template: hello
        arguments:
          parameters:
          - name: name
            value: "{{tasks.hello-mate.outputs.result}}"
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: greet-pipeline
spec:
  templates:
  - name: greet
    inputs:
      parameters:
        - name: name
    dag:
      tasks:
      - name: greet
        templateRef:
          name: greet-script
          template: runme
        arguments:
          parameters:
            - name: name
              value: "{{inputs.parameters.name}}"
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: greetings
spec:
  templates:
  - name: hello
    inputs:
      parameters:
      - name: name
    script:
      image: bash:5.1
      command: [bash]
      source: |
        echo "Hello {{inputs.parameters.name}}"

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Potentially fixed by https://github.com/argoproj/argo-workflows/pull/5594

Will make sure

Update: not fixed by #5594

@rccrdpccl can you confirm if this is a regression? If so, what is the latest version that this does in fact work on

@simster7 I confirm this was working fine on v2.12.10


CI azure-sdk-for-python-track2 fails with npm version error?

https://github.com/Azure/azure-rest-api-specs-pr/pull/15061/checks?check_run_id=17055799343
❌Code Generator Failed [Logs] Generate from 02d7c2df491cbf7d1f61b58743d0002be9091978. SDK Automation 14.0.0
command	sh scripts/automation_init.sh ../azure-sdk-for-python-pr_tmp/initInput.json ../azure-sdk-for-python-pr_tmp/initOutput.json
cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
command	sh scripts/automation_generate.sh ../azure-sdk-for-python-pr_tmp/generateInput.json ../azure-sdk-for-python-pr_tmp/generateOutput.json
cmderr	[automation_generate.sh]  notice
cmderr	[automation_generate.sh] npm notice New major version of npm available! 9.6.7 -> 10.1.0
cmderr	[automation_generate.sh] npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.1.0
cmderr	[automation_generate.sh] npm notice Run npm install -g<EMAIL_ADDRESS>to update!
cmderr	[automation_generate.sh] npm notice
cmdout	[automation_generate.sh] [Autorest]/mnt/vss/_work/1/s/azure-sdk-for-python-pr_tmp/venv-sdk/auto_temp.json does not exist!!!Error happened during codegen
error	Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-python-pr]: sh scripts/automation_generate.sh
warn	Skip package processing as generation is failed

@DevArjun23 closing because the npm issue has been mitigated


Dockerfile: update cilium-builder to 2018-03-29

hub.docker.com is currently failing for cilium/cilium. This PR should fix it
Signed-off-by: André Martins<EMAIL_ADDRESS>

test-me-please


is it possible to install Ubuntu with "UEFI Environment only" option?

Hey,
I was thinking on testing this new technology out. I want to install ubuntu instead of arch linux and i think using the uefi environment option would make it work. however, i need to know how to boot into it and check if it is possible with m1 macbook pro architecture. Could you guys help me out here?

Someone already posted a Asahi Installer w/ Debian installer, and I successfully change my Debian installation to Kali afterwards. This is possible because Kali is just based on Debian. You could try to do similar thing to convert Debian to Ubuntu, but since these two systems are more different than Debian v.s. Kali, you might encounter unrecoverable failure.

How did you install Kali?

Someone already posted a Asahi Installer w/ Debian installer, and I successfully change my Debian installation to Kali afterwards. This is possible because Kali is just based on Debian. You could try to do similar thing to convert Debian to Ubuntu, but since these two systems are more different than Debian v.s. Kali, you might encounter unrecoverable failure.

Do you have a tutorial for kali?


Fix checker class comments

This PR should be self-explanatory 😊
Currently, some comments were copy-pasted from other files and don't reflect what the class does.

Hi, @toydestroyer!
I'm sorry it took me so long to look at it. I'm pretty busy with many other things, but I'm slowly returning to the project.


Added Unit Tests

Added Unit Tests to increase code coverage.

Can one of the admins verify this patch?

Hi @TheRealHaui
The pr is not passed by style check, for "Using the '.*' form of import should be avoided"

Hi,
thanks for the advice.
I know.
Already fixed it but oversaw that my IDE integrated a star import for JUnit assert statements on saving.
Going to fix it again.
After trying to teach my IDE to not integrate star imports in the background on saving again.

Pull Request Test Coverage Report for Build 4442

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.05%) to 27.865%

Files with Coverage Reduction
New Missed Lines
%

core-dictionary/src/main/java/org/apache/kylin/dict/lookup/cache/RocksDBLookupTable.java
1
81.08%

stream-core/src/main/java/org/apache/kylin/stream/core/storage/CheckPointStore.java
2
73.74%

Totals

Change from base Build 4432:
0.05%

Covered Lines:
22796

Relevant Lines:
81808

💛  - Coveralls

Codecov Report

Merging #625 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #625      +/-   ##
============================================
+ Coverage     25.33%   25.38%   +0.05%
- Complexity     5840     5863      +23
============================================
  Files          1379     1379
  Lines         81808    81808
  Branches      11465    11465
============================================
+ Hits          20724    20769      +45
+ Misses        59060    59016      -44
+ Partials       2024     2023       -1

Impacted Files
Coverage Δ
Complexity Δ

...he/kylin/dict/lookup/cache/RocksDBLookupTable.java
72.97% <0%> (-5.41%)
6% <0%> (-1%)

...che/kylin/stream/core/storage/CheckPointStore.java
63.63% <0%> (-3.04%)
21% <0%> (-1%)

...a/org/apache/kylin/dict/Number2BytesConverter.java
82.53% <0%> (+0.79%)
18% <0%> (+1%)
:arrow_up:

...org/apache/kylin/common/restclient/RestClient.java
18.35% <0%> (+4.83%)
6% <0%> (+3%)
:arrow_up:

...main/java/org/apache/kylin/common/KylinConfig.java
41.12% <0%> (+5.24%)
27% <0%> (+4%)
:arrow_up:

.../java/org/apache/kylin/common/util/StringUtil.java
41.23% <0%> (+26.8%)
22% <0%> (+17%)
:arrow_up:

Continue to review full report at Codecov.

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

@nichunen,
now it is passing.


Non-blocking loading of large databases

With a large JSON database, it loads the file asynchronously but blocks the process in the JSON.parse step, blocking on the order of 10s of seconds.
https://github.com/techfort/LokiJS/blob/master/src/lokijs.js#L2515
https://github.com/techfort/LokiJS/blob/master/src/lokijs.js#L1622
Could we move to a non-blocking JSON parser, like yieldable-json?

our (node-based) es6 loki-fs-structured-adapter uses a generator iterator approach with individual JSON.parse calls for each object which sounds similar to what you describe.
I had thought about bringing our iterator approach internal to loki but decided against it as it has always been es5 and we are shifting development focus to lokidb which will likely see such a feature.
So if loki-fs-structured-adapter does not fit your needs, you should be able to create your own "reference mode" persistence adapter to utilize any method such as you describe, even if that requires your dependencies.


selectize multiselect option selected for edit page

My javascript is
$('#cust_id').selectize({
persist: false,
plugins: ['remove_button'],
maxItems: 1, /* if you want only one item either comment it completely or mention 1, if you want unlimited mention null */
valueField: 'id',
labelField: 'custname',
searchField: ['id', 'custname', 'so_name', 'address', 'city'],
options: [],
create: false,
    render: {
        item: function(item, escape) {
            return '
' +
				(item.custname ? '' + escape(item.custname) + '' : '') +
				' (Support Office: ' +
				(item.so_name ? '' + escape(item.so_name) + '' : '') +
				')'+
			'
';
        },
		option: function(item, escape) {
			return '
' +
				'' +
					'' + escape(item.custname) + '' +
					'support office: ' + escape(item.so_name) + '' +
                '' +
                '' + escape(item.address) + ' ' + escape(item.city) + '' +
			'
';
		}
    },

    load: function(query, callback) {
    	if (!query.length) return callback();
        $.ajax({
            url: siteurl + '/support/ajaxGetCustomers/',
            type: 'GET',
            dataType: 'json',
            data: {
                term: query
            },
            error: function() {
                callback();
            },
            success: function(res) {
            	callback(res.custnames);
            }
        });
    }
});

My HTML page is

Customer Name

cust_name; ?>

The already selected item is appearing properly. But the drop down is not loading with all components properly, it is only loading one portion.
While in adding page... the drop down is properly populating

After selecting in the adding page it is displaying properly

The problem is mentioned below
While in edit page it is not loading properly

I also tried this data-data that is spoken a lot in internet, but no clarity...
data-data="{'id':'cust_id; ?>','email':'so_name; ?>'}"

I did a lot of permutations and combinations on data-data attribute. I tried the value for data-data attribute in the following way and it worked for me. I wish the document for selectize is improved a lot and more examples are given, otherwise its a pain in the neck using this.
data-data="{"cust_name":"cust_name; ?>","so_name":"so_name; ?>","address":"address; ?>","city":"city; ?>"}"


[Bug]: Figure out why TREFHT regridded reference variable is not regridding on main with ESMF bilinear

What happened?
In PR #815:

This PR validates the replication of the slice flag feature added in PR #750 to fix #759.
I re-ran ex1.py and found that all .nc files produced are now within the relative tolerance.
For metrics, all but one is within the relative tolerance. This single metric is related to the regridded reference data for "TREFHT" with the land region. In trefht.py, I compare the .nc file for the regridded reference data between xCDAT/xESMF and CDAT/ESMF. I found that CDAT/ESMF doesn't seem to actually regrid the data since the original and regridded reference variables are the same, as noted in this PR review comment. I think this is leading to the large diffs along the coast lines, as shown below.

xCDAT
CDAT
Diff

In PR #794, I noticed how bilinear regridding with xCDAT/xESMF produces nan location mismatches when comparing land sea masks to CDAT/ESMF. I think we should move forward for now and debug this more later on in a separate PR.

What did you expect to happen? Are there are possible answers you came across?
The reference TREFHT variable should be regridded since the mv2.regrid is called below:
https://github.com/E3SM-Project/e3sm_diags/blob/c8404ab0f5523fee80cda396357f307b7ad1ff5b/e3sm_diags/driver/utils/general.py#L246-L254
Minimal Complete Verifiable Example (MVCE)
No response
Relevant log output
No response
Anything else we need to know?
No response
Environment
main branch

This will be a non-issue after #902.


Calculate stat summary

Add new test cases and modify calculate_stat_summary() function

I'm not sure why data_type is being used as an argument for the calculate_stat_summary since that should have already been specified at the data acquisition step. The concern is that the 'data_type' specified by the user of the calculate_stat_summary function might not actually exist in the dataframe which is being passed into the function.

Only with the dataframe itself,  I can't figure out this is a cases data or mortality data. There are different columns in these different dataframes to summarize information. I need to read the data_type information from somewhere.

The data_type does not match the dataframe, the function will raise an error.

The function doesn't need to know which data_type was used, it just needs to work with the columns that are in the given dataframe. For example, no matter what data type was used, there will be a column that starts with 'date_' and cumulative column will start with 'cumulative_ ' and you can use string matching to identify those columns

I think it's not just df.describe() things. I need to know what I need to summarize. The people who call this function just pass the same data_type parameter as they call get_covid_data() function.

If I have the date_type parameter passed, it's easier for me to do the summary.

The easiest way would be to just specify the column to summarize as an input function.  The function right now wouldn't work if they user passes in a data_type different from the one that was actually used in get_covid_data, and it doesn't defensively program against it either

I have checked the validity of the input parameter in the function. It will raise an error with the corresponding error message if the parameter does not match.

Just one final comment, your test coverage is only 62% while the other functions are all 90% plus, would be nice to have better coverage for your function if possible, but we can update that later. I'll merge the PR and make a new issue about test coverage.


Company Communicator not working after the Secret key got expired

Company Communicator not working after the Secret key got expired.
Create and updated new secret keys but still error is same.
The Error message says "Sorry, an error occurred while trying to access this service".
Checked it from Client and same isue

Hi @Nadeem-hussain-mafgs
Please cross verify once again w.r.t secrets renewal with the below steps.

Go to Azure Portal
Go to App registration
Create a new secret value for app registration and grab secret value. Here is the reference.

Then go to resource group. Select key vault from list of resources.

Click on secrets under object section.

If the secrets are not visible, Go to Access Policy--> Click on Create

Select Key, secret and certificate management

Give the Id through which one can view the secrets

3rd step is optional

Go for Review+Create

Then go to Secrets. Open author/user/graph app password

Click new version

Grab the new secret identifier

Paste it in the configuration sections of app service, 3-function apps. Here is the reference of updating the author app password in app service configuration.

Follow the same procedure for the user app password and graph app password updating.

For graph app, please dont forget to update the password in AzureAd Client Secret as well. here is the reference

Hi @Nadeem-hussain-mafgs
connected internally Let us know if you still have any problems; otherwise, please close the ticket.


Mezzanine works on unsupported version of Django

Hi,
I notice that setup.py states that Django 2.0 is currently the highest version supported by Mezzanine. However that version of Django is no longer receives extended support (https://www.djangoproject.com/download/).
https://github.com/stephenmcd/mezzanine/blob/master/setup.py#L54
Your automated tests show that it can work on Django 2.1 though. When are you planning to release a version compatible with Django 2.1+? I'm particularly interested in Django 2.2 support as it's an LTS. What's your schedule?

I wrote a message about this on the Google Group message board but it never became public...
Basically I need to upgrade several legacy website based on Mezzanine in the coming months. After that we are planning to make only minor updates of the stack and minor maintenance work but no upgrade for a few years. Ideally we'd put the app on Django 2.2 Long Term Support and be good for the next three years.
Is this project still being maintained and is there any roadmap for a Django 2.2-compatible release? If not how far is the development branch from being compatible with 2.2? I could consider contributing pull requests but I need an idea of how much work is left (is it a matter of days, weeks?) to get there.
Without clearer information my only remaining option is to migrate all my content to another Django CMS. I wish I could avoid that as it would be a lot of work and a shame as our users really likes Mezzanine and it has been the best suited CMS for our web app.

I did some work on this on my own mezzanine fork (and cartridge fork but haven't really had the time to finish what I started with it.
There are certainly some issues still with it (some JS stuff if I remember correctly) but it might give someone at least a starting point to see what else needs to be done.

Hi @petedermott thanks for sharing that. That's really useful and I might start from that. I see that some of your changes have already been pulled into the main repo.

See also this thread on the mailing list: https://groups.google.com/d/topic/mezzanine-users/zOO9K5_9PMo/discussion

Hi, also working on that. I've made a pull request for two changes that were also in Peters fork, but made it a non breaking change for django 1.11. So not everybody has to analyze and change the same things again.
Maybe somone can do a short review on the chages.
There's more to come, i.e. a change in filebrowser_safe where the widget.render signature changed (Support for Widget.render() methods without the renderer argument is removed in django 2.1).
I'm not sure, if anybody is more confident with Peters keyword_fields change (https://github.com/fermorltd/mezzanine/commit/f6da0a2219fa4d1b7bce4cac4e47d864dab08844). Maybe Peter can put that in pull request.

There are some minor css issues in the grappelli app:

the horizontal filter widget css makes the widget too small
there's no css for the new autocomplete widgets (select2)

Another issue I've spotted with my current branch is that sortable inlines don't currently work due to an issue flagged as TypeError: $(...).sortable is not a function in the console.
The jQuery UI file seems to be loading but a check for it with console.log($.ui ? $.ui.version || "pre 1.6" : 'jQuery-UI not detected'); in the dyanmic_inlnes.js file says that it isn't.
I think this is because newer versions of Django includes jQuery 3.3.1 whilst older versions used jQuery 2.2.3 but I'm not 100% sure.

Hi all, I am looking for 2.2 support as well. I am happy to jump in and help here as I have some time, but I don't want to duplicate work... it sounds like there are a few different forks floating around with 2.2 changes in progress, that haven't been pulled yet?

Hi! Feel free to take my fork and make modifications to get it into a usable state. As mentioned the issue with the inlines was what was stopping me going any further with it.

Django 3.0 is also now available so I guess any work that is done going forward should also really try to take this into account.

I also would like to help finish off people's forks, although it's a little bit hard to know which I should start from. I suspect @stephenmcd is probably too busy with his work at Google to maintain this package any more. Probably the nicest solution would be to see if we could get @stephenmcd to move the project (and associated projects such as grapelli-safe, filebrowser-safe, cartridge) to one of https://jazzband.co/ or https://www.codeshelter.co/ ?

This works for me (with python-3.6.9 / sqlite-3.30.1 / django-2.2.8)...
venv=".venv"
virtualenv "$venv"
source "$venv"/bin/activate
pip install \
	git+https://github.com/stephenmcd/filebrowser-safe \
	git+https://github.com/stephenmcd/mezzanine@refs/pull/1934/head \
	django==2.2.*
perl -pi -e \
	's/([ ]+"django\.contrib\.)(contenttypes)(",\n)/\1\2\3\1messages\3/','s/(MEDIA_URL = )STATIC_URL \+ ("media\/")/\1\2/' \
	"$(find "$venv" -ipath '*mezzanine*' -iname 'settings.py')"
mezzanine-project foo
python ./foo/manage.py createdb
python ./foo/manage.py runserver

...so pull request https://github.com/stephenmcd/mezzanine/pull/1934 might be a good start.
(Apologies if anybody else has a further along branch or pull request.)
Should probably also change #1749 to aim for Django 2.2 instead of 2.0.

I've started a discussion regarding a possible migration to jazzband / code shelter over on the mailing list if people want to contribute.

Hi. I am interested in any progress on this? I am planning on starting a Django based project and am keen to make use of Mezzanine for related sites. If there is a working, or almost working version of Mezzanine on Django2.2 then I would like to be kept in the loop so am subscribing to this issue.

There are pull request open and currently being evaluated for Django 2.2 compatibility for mezzanine, filebrowser-safe and grappelli-safe. See  #1956

#1956 has been merged!

mezzanine with Django 2.2 support (until release v.5 will be ready)
you can use the following line in your requirements
-e git+git://github.com/stephenmcd/mezzanine.git@9768b46f8377796d5d51d74db54589c9d3669a47#egg=Mezzanine  # feat: Add Django 2.2 compatability (#1956)
or for pip
 pip install -e git+git://github.com/stephenmcd/mezzanine.git@9768b46f8377796d5d51d74db54589c9d3669a47#egg=Mezzanine

You can also install the alpha from pip: pip install Mezzanine==5.0.0a1

Hello, tell me how to install mezzanine with Django 3,1 support?
Best regards, Sergei

Hi! Mezzanine only works with Django 2.2. Contributions are welcome to add support for 3.0+

This messed up my dev sqlite database. Would this ruin my production mysql databse? How would I migrate a production site to upgrade from Mezzanine + Django 1.11 to Django 2.2?


Update container/containers-environment.md in Korean

This is a Feature Request

What would you like to be added

Update concepts/containers/Container Environment view in Korean.
Why is this needed
There is an changes to concepts/containers/container-environment in Korean.
Comments

Page to Update:
https://kubernetes.io/docs/concepts/containers/container-environment/

/language ko
/assign

안녕하세요.
container-environment.md 문서는 쿠버네티스 1.18 릴리스가 되며 container-environment-variables.md 문서의 이름이 변경된 이름입니다.
변경된 것에 대한 업데이트는 #19886 을 통해 반영될 예정에 있습니다.
참고 부탁드립니다.

Thanks. I'll close this issue. :D


test:add TestBlockReadFullAndBlockWriteFull

What type of PR is this?
test:add TestBlockReadFullAndBlockWriteFull

What this PR does / why we need it (en: English/zh: Chinese):

en: Improve test cases
zh: 完善测试用例
Which issue(s) this PR fixes:

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

LGTM thanks


Apply size methods to String

Describe the feature you request
giveMeBuilder#size methods not applied to String class.
For example, folowing code produces arbitrary size of string.
data class A(val a: String)

val value = fixtureMonkey.giveMeBuilder<A>()
    .size(A::a, 10)
    .sample()
println(value.a.length)

(Optional): Suggest A Solution
If would be nice to produce string with the size i provided.
If the feature request is approved, would you be willing to submit a PR?
Yes

I think this is a good feature to keep consistency with the `@Size' annotation.
@Target(value={METHOD,FIELD,ANNOTATION_TYPE,CONSTRUCTOR,PARAMETER})
 @Retention(value=RUNTIME)
 @Documented
 @Constraint(validatedBy={})
public @interface Size
The annotated element size must be between the specified boundaries (included).
Supported types are:

CharSequence (length of character sequence is evaluated)
Collection (collection size is evaluated)
Map (map size is evaluated)
Array (array length is evaluated)
null elements are considered valid.

It would be nice to work on the CharSequence interface.


[Blazor] Accessibility and keyboard navigation for complex component

As far as i understood, the whole idea of Blazor is to reduce the usage of JavaScript and leverage C# to create components.
When the JavaScript usage is limited, what is the recommended way to implement keyboard navigation in complex components like menu, slider, list, gridview etc?
https://www.w3.org/TR/wai-aria-practices/#kbd_general_within
The above link describes keyboard navigation standard for complex components, this involves listening to events and adding tabIndex to the elements. Is this possible in Blazor?  How the DOM can be accessed and focused?

Thanks for contacting us, @Madhust.
It's easy in Blazor to set html attributes and listen to DOM events. Is there anything else specific you have in mind?
As for the need for focus, we'll track that work as part of https://github.com/aspnet/AspNetCore/issues/10521

@mkArtakMSFT Thanks for the update. Details looks good. If i face any problems or questions during implementation, i will put a new issue.

@mkArtakMSFT, What is the equivalent of querySelector in Blazor. What if i want to query the children of the element. Is this possible with Blazor?

@Madhust for querySelector you should still use JSInterop.


Change "Project maintained by" to something custom?

In the footer, the theme writes the line "Project maintained by {GithubUsername}".
Would be cool if i could change this line to something like "website maintained by" or something entirely different.

Editing the text between the <footer></footer> tags in /_layouts/index.html works for me...
Take a look at: https://andy-abtec.github.io/tvrename - its a work in progress!

Yup i realized it in the meantime. Thanks for the info! The documentation is, let's say, very decentralized.


vaapi h264 filter issue

Hi !
I'm using 0.7.0-d2040eaa-docker-vaapi (cpu : i5-9500T) and I'm having issue with qsv and vaapi and format h264.
my settings
Some videos work, some won't.
If i'm using VAAPI - IHD, I have :
HLS process for channel 6 has terminated unsuccessfully with exit code 1: Impossible to convert between the formats supported by the filter 'Parsed_colorspace_5' and the filter 'auto_scale_1' Error reinitializing filters! Failed to inject frame into filter network: Function not implemented Error while processing the decoded data for stream #0:0

full log ihd.txt
If i'm using VAAPI - i965, I have :
HLS process for channel 6 has terminated unsuccessfully with exit code 1: [AVHWDeviceContext @ 0x55b77c3ad940] Failed to initialise VAAPI connection: -1 (unknown libva error). Device creation failed: -5. Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Input/output error Error parsing global options: Input/output error

full log i965.txt
Finally, if i'm using QSV :
HLS process for channel 6 has terminated unsuccessfully with exit code 1: [hwdownload @ 0x5590e78711c0] Invalid output format yuv420p for hwframe download. [Parsed_hwdownload_4 @ 0x5590e78715c0] Failed to configure output pad on Parsed_hwdownload_4 Error reinitializing filters! Failed to inject frame into filter network: Invalid argument Error while processing the decoded data for stream #0:0

full log qsv.txt
Thank you a lot ! Don't know if I should submit a new issue for each case.

I think this has been fixed with #1072 - please pull the latest image and confirm.

Tried a few problematic files : VAAPI - iHD seems to work. Need to test more but sounds good for me 👍
But ... i965 same issue (Device creation failed: -5) and for QSV, the logs seem OK, I don't see errors, but Plex throw me an error (can't retrieve channels). The only things I see in logs :
ffmpeg hls arguments -threads 1 -nostdin -hide_banner -nostats -loglevel error -fflags +genpts+discardcorrupt+igndts -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -ss 00:10:36.3663915 -hwaccel_output_format vaapi -re -i "/media/HDD/Plex/HDD2/Emissions TV/Le monde de Jamy/Season 01/Le Monde de Jamy - S01E03 - Au cœur de la faune sauvage.mkv" -ss 00:10:36.3663915 -re -i "/media/HDD/Plex/HDD2/Emissions TV/Le monde de Jamy/Season 01/Le Monde de Jamy - S01E03 - Au cœur de la faune sauvage.mkv" -filter_complex [1:1]loudnorm=I=-16:TP=-1.5:LRA=11,apad=whole_dur=7293840ms[a];[0:0]scale_vaapi=1920:1080:force_divisible_by=2:force_original_aspect_ratio=decrease,setsar=1,hwdownload,format=yuv420p,pad=1920:1080:-1:-1:color=black[v];[v]setparams=range=tv:colorspace=bt709:color_trc=bt709:color_primaries=bt709,format=nv12|p010le|vaapi,hwupload[vpf] -map [a] -map [vpf] -muxdelay 0 -muxpreload 0 -movflags +faststart -flags cgop -sc_threshold 0 -t 01:50:57.4736085 -video_track_timescale 90000 -b:v 2000k -maxrate:v 2000k -bufsize:v 4000k -c:v h264_vaapi -c:a ac3 -b:a 192k -maxrate:a 192k -bufsize:a 384k -ar 48k -map_metadata -1 -metadata "service_provider=\"ErsatzTV\"" -metadata "service_name=\"Documentaires\"" -g 100 -keyint_min 100 -force_key_frames expr:gte(t,n_forced*4) -f hls -hls_time 4 -hls_list_size 0 -segment_list_flags +live -hls_segment_filename /root/.local/share/etv-transcode/6/live%06d.ts -hls_flags program_date_time+append_list+discont_start+omit_endlist+independent_segments -mpegts_flags +initial_discontinuity /root/.local/share/etv-transcode/6/live.m3u8

Using 0.7.0-0fc1e15c-docker-vaapi

Will keeping looking at QSV.
I wouldn't worry about i965 driver - it's only included as an option because some old iGPUs are not supported by the new iHD driver.

The i965 driver was actually missing from docker and it should now be available in develop images again.

Hello,
Thank you for your work !
I wasn't able to start a stream with i965 :
[09:37:40 ERR] HLS process for channel 3 has terminated unsuccessfully with exit code 1: [Parsed_scale_vaapi_2 @ 0x55a16b996e80] Hardware does not support output format p010le.
[Parsed_scale_vaapi_2 @ 0x55a16b996e80] Failed to configure output pad on Parsed_scale_vaapi_2
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:0

I don't plan to use the i965 but maybe it will affect other peoples.
0.7.1-beta-docker-vaapi