[GOBBLIN-693] Add ORC hive serde manager

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[X] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-693

Description

[X] Here are some details about my PR, including screenshots (if applicable):
Created an ORC serde manager for hive registration.

Tests

[X] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@autumnust, please take a look.

@htran1  LGTM


[CCAP-452] - create new providerresponse paid by ccap screen

🔗 Jira ticket
CCAP-452
✍ Description
Add paid-for-ccap screen and tests with element id's for each button and/or link on the page.
📷 Design reference
Figma
✅ Completion tasks

[ ] Added relevant tests
[ ] Meets acceptance criteria

Tested it and it looks great!


Children connection are "hard" to read

Describe the bug
See the screenshot below. The connection between Carlos and Sven make it hard to read the tree. It require extra thinking to know that Carlos and Sven are children of Leverling. Is it possible to have 2 direct connections from Leverling: 1 for Carlos and 1 for Sven.
To Reproduce
Steps to reproduce the behavior:

Go to futuristic example and expand all: https://web-platform-o5t1ha.stackblitz.io/

Expected behavior
See screenshot.

@xuanngo2001 Just set .compact(false) and you'll get the org chart in your desired form


[SPARK-6226][MLLIB] add save/load in PySpark's KMeansModel

Use _py2java and _java2py to convert Python model to/from Java model. @yinxusen

Test build #28659 has started for   PR 5049 at commit b10b911.

This patch merges cleanly.

Test build #28659 has finished for   PR 5049 at commit b10b911.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KMeansModel(Saveable, Loader):

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

Test build #28665 has started for   PR 5049 at commit 570ba81.

This patch merges cleanly.

Test build #28665 has finished for   PR 5049 at commit 570ba81.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KMeansModel(Saveable, Loader):

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

test this please

Test build #28672 has started for   PR 5049 at commit 570ba81.

This patch merges cleanly.

Test build #28672 has finished for   PR 5049 at commit 570ba81.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KMeansModel(Saveable, Loader):

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

@mengxr Don't we need extra unittest? Does doctest well enough?

Not necessary. doctests are examples+unittests.

Merged into master.


Add a feature for linking to proc_macro.

This feature is enabled by default for backwards compatibility, but
it can be disabled in order to break the runtime dependency on the
dynamic library libproc_macro in the rustc toolchain.
This PR assumes that there is a version 0.5.0 or higher of quote on crates.io that includes dtolnay/quote#62. That is not yet the case (see https://github.com/dtolnay/quote/pull/62#issuecomment-368087621)

I wasn't sure what travis.yml changes you wanted here, since it looks like it builds in some subset of possible configurations but only tests the configuration with all the features.

Thank you! I filed #369 to reopen and merge this PR during the next round of breaking changes.


CRS not set for some of the concatenation inputs.

there is always a warning when i run the the training script and evaluate script：
UserWarning: CRS not set for some of the concatenation inputs. Setting output's CRS as unknown (the single non-null crs provided).

Will this warning have a negative impact on the final result?
How can I avoid this warning?

库版本问题，大概是geopandas库，改成0.11.1 就行。或者命令行 -w ignore 去掉

这样处理使用高版本库终究是一个问题，最好能在代码层面处理掉

找到了，在 plan_client.py的restore_plan里设置crs即可


Fix issue : start_word_key is set to next_key even in the presence of start_key

This is in reference to the issue brought up in the thread on issue #138 .

LGTM

Thanks @junkmechanic, thanks @eapache for reviewing


Add a fix to work with shorthand multiple floats such as 1.2.3

This is introduced by some editors, see
http://lists.runrev.com/pipermail/use-livecode/2015-November/221100.html

This was tracking the wrong branch


Include make.bat for building Sphinx docs on Windows

Include make.bat file to allow for building documentation via Sphinx on
Windows. This file is directly modelled from the make.bat generated by
sphinx-quickstart.

Okay, sorry if you got a bunch of annoying notifications on this. I was experimenting on the best way to switch the branch to derive from master instead of next.
A rebase wasn't so simple because there was conflicts and I would have to manually merge them. Instead, I just created a patch, created a new branch and applied the patch to the branch.

The pull requests are merged with the stage repo, which does some additional validation, and management of a topic so that is can be merged into next, then master as needed. So it does not matter too much where the pull request is targeted to.
In this case I am merging the topic into next now, and Github will close the issue when its merged into master.


Allow text renderer

Having a text renderer can help to add more functionnalities (issue #61)

This looks great! Could you add some tests to ensure it doesn't break the default text renderer, and that future changes won't break custom text renderer support?

I'm not sure I did the tests right (first time using jest), don't hesitate to tell me what I can do better!

Is there a chance to see this PR merged over the weekend :smiley: ?

I'll do a PR on the readme to add an example on how to user it with emoji-mart.

Released as 3.2.0, thanks a bunch!


Add friendly error pages

This should include:
404 for page not found
500 for unexpected errors
Service unavailable (in case we need to take the service down temporarily)
Notify error (special case of the 500 error with some extra text about the submission failing)

I've run into an issue here:

forms-runner uses /form_id routes to navigate to a form, where form_id is an integer
Rails wants to use /404 and /500 for error pages
So there will be a conflict if/when form_id is 404 or 500.

I can try writing some more custom logic for handling the error, or we can change the path where forms are hosted, but since we already have a task in the current sprint to look at the URLs forms live at, it might be easier and more opportune to change the form route instead.

Yes saving the / might make our lives easier in the future if we ever want to add more pages in there.

For now at least I'll remove the path: "/" from the forms entry in routes.rb, so forms will now be at /form/1 and pages will now be at /form/1/1.


Only child exception when using react-boostrap tooltip inside Form

(...)
<Form>
    <OverlayTrigger placement="right" overlay={tooltip}>
        <Button bsStyle="default">Holy guacamole!</Button>
     </OverlayTrigger>
    (...)
</Form>

Uncaught Error: Invariant Violation: onlyChild must be passed a children with exactly one child.
Works when OverlayTrigger is placed outside of <Form> component. My guess is that it has something to do with Form cloning its children when rendering, but can't pinpoint the exact location of the issue. Any idea ?

Thanks for the report. I'll look into it.


🐛 Config with knip.js doesn't work correctly.

Prerequisites

[X] I'm using the latest version
[X] I've read the relevant documentation
[X] I've searched for existing issues
[X] I've checked the list of known issues
[X] I've read the issue reproduction guide

Reproduction url
https://github.com/grubinstein/knip-js-error
Reproduction access

[X] I've made sure the reproduction is publicly accessible

Description of the issue
Problem occurs when using knip.js for configuration instead of knip.json. Please see minimal reproduction at https://github.com/grubinstein/knip-js-error .
When running "npm run knip", expected behaviour is that the file "unimported.js" should be reported as unused. In reality, the behaviour is unpredictable, either "nothing happens", ie the output is:
><EMAIL_ADDRESS>knip
> knip

or an error is thrown:
><EMAIL_ADDRESS>knip
> knip

[15264:0930/113216.239:ERROR:cache_util_win.cc(20)] Unable to move the cache: Access is denied. (0x5)
[15264:0930/113216.239:ERROR:disk_cache.cc(208)] Unable to create cache

Replacing knip.js with an equivalent knip.json resolves this issue, however knip.js is needed if dynamic config is desired.
Converting the project to commonJS doesn't seem to solve the problem.

Can't seem to reproduce. Changing knip.ts and converting it to knip.json gives the same result.
I don't know where that error comes from. You might be hitting some issue on your machine? Knip doesn't try to cache anything by default (there is a --cache flag which you don't seem to be using and still I'd say those error messages seem unrelated). I can try to reproduce it on a Windows machine if you'd like.

Thanks for getting back to me. I should have said I'm running Windows, if you have access to a Windows box to try and reproduce I'd be very curious.
So this config works fine for you? On Linux?

Just to add to this. Typically the first time I run the command I don't get the error, there's just no output. On subsequent attempts I get the error. This is making me wonder if an error that occurs the first time I run the command is causing the process to terminate improperly, leaving some files locked. Then when I run the command again it errors out when trying to use those files somehow? I could be way off-base, just wanted to add that there is a pattern as to which result I get.

One more observation, I hadn't noticed this before because knip,.js was already open in my editor, but when I run "npm run knip" it opens the knip.js file for editing.

I can't reproduce this on a Windows machine either. Not seeing other similar reports, so I'm going to close this one, sorry.


Update package for ROS 2 Jazzy

Overview
Author:  @ruffsl
Issue
Related:

https://github.com/luxonis/depthai-ros/issues/457

Changes
ROS distro: jazzy
List of changes:

Fix missing ament_index_cpp depends in cmake and package manifest
Add target_compile_definitions for IS_JAZZY

Testing
Hardware used:
Depthai library version:
Visuals from testing
Add screenshots/gifs/videos from RVIZ or other visualizers demonstrating the effect of the changes when applicable.

Thanks for PR. Any thoughts when PR will be merged?

I think this has been superseded by this commit added to the jazzy branch:

https://github.com/luxonis/depthai-ros/commit/00dc57f


feat: add insecure option to name options

Signed-off-by: Batuhan Apaydın<EMAIL_ADDRESS>
Fixes #2290
Summary

This PR will add an insecure option to the name options and use it while parsing the reference of the image name to set the HTTP scheme.
Release Note

adds an insecure option to sign & verify commands' name options to set the HTTP scheme for insecure registries properly

Documentation

Codecov Report

Merging #2316 (280cb4c) into main (7978172) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2316      +/-   ##
==========================================
- Coverage   30.06%   30.04%   -0.03%
==========================================
  Files         131      131
  Lines        8062     8069       +7
==========================================
  Hits         2424     2424
- Misses       5314     5321       +7
  Partials      324      324

Impacted Files
Coverage Δ

cmd/cosign/cli/sign/sign.go
14.28% <0.00%> (-0.17%)
:arrow_down:

cmd/cosign/cli/verify.go
0.00% <0.00%> (ø)

cmd/cosign/cli/verify/verify.go
19.34% <0.00%> (ø)

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

There are some other places that we need to do the same thing, I guess 🤔

kindly ping @hectorj2f @dlorenc

I'd vote for (2) over (3). We have a similar problem in crane and ko, and just saying there should be a separate flag if you want http seems the best option. This also gives us a go option for http-but-not-also-bad-https.
Do we think we need a warning for a release or two before we change the semantics of "insecure registry"

@jonjohnsonjr

spec-noncompliant

I'm 90% sure there's no spec 🙃
Is there prior art for other clients that need to do this?

Do we think we need a warning for a release or two before we change the semantics of "insecure registry"

Are we proposing that (for Cosign)? I think we can introduce a new flag without changing existing behavior, we just probably want better docs. Or are you talking GGCR?

Sorry I misunderstood, you're right.

kindly ping. What has to be done before merging this? 🙋🏻♂

I think we want to separate this behavior into a distinct flag. So --allow-insecure-registry should continue to work exactly as it does before this PR, and the new flag (--allow-http-registry maybe?) would enable this behavior.

that should be okay now @znewman01

I think we want to separate this behavior into a distinct flag. So --allow-insecure-registry should continue to work exactly as it does before this PR, and the new flag (--allow-http-registry maybe?) would enable this behavior.

Hi All,
I have tried to test new flag  '--allow-http-registry' with insecure harbor registry with cosign prerelease cosign_2.0.0.rc.0 . images are getting signed and pushed to insecure registry as expected with this flag.
but i see a P3 bug on cosign_2.0.0.rc.0  version.
Issue:  --allow-http-registry flag is added under consig help
Expected Behaviour:  --allow-http-registry flag should be added under cosign help
example:
cosign version
______   ______        . __    _______ . .
/      | /  __  \      /       ||  |  /  ||  \ |  |
|  ,----'|  |  |  |    |   (----|  | |  |  __  |   \|  | |  |     |  |  |  |     \   \    |  | |  | |_ | |  .   |
|  ----.|  --'  | .----)   |   |  | |  || | |  |\   |
_| ______/  |_/    ||  __| || _|
cosign: A tool for Container Signing, Verification and Storage in an OCI registry.
GitVersion:    v2.0.0-rc.0
GitCommit:     a827922053c48283fb458b7b6bc51be3f477ec4d
GitTreeState:  clean
BuildDate:     2022-12-15T00:07:35Z
GoVersion:     go1.19.4
Compiler:      gc
Platform:      linux/amd64
# cosign help
A tool for Container Signing, Verification and Storage in an OCI registry.
Usage:
cosign [command]
Available Commands:
attach                  Provides utilities for attaching artifacts to other artifacts in a registry
attest                  Attest the supplied container image.
attest-blob             Attest the supplied blob.
clean                   Remove all signatures from an image.
completion              Generate completion script
copy                    Copy the supplied container image and signatures.
dockerfile              Provides utilities for discovering images in and performing operations on Dockerfiles
download                Provides utilities for downloading artifacts and attached artifacts in a registry
env                     Prints Cosign environment variables
generate                Generates (unsigned) signature payloads from the supplied container image.
generate-key-pair       Generates a key-pair.
help                    Help about any command
import-key-pair         Imports a PEM-encoded RSA or EC private key.
initialize              Initializes SigStore root to retrieve trusted certificate and key targets for verification.
load                    Load a signed image on disk to a remote registry
login                   Log in to a registry
manifest                Provides utilities for discovering images in and performing operations on Kubernetes manifests
policy                  subcommand to manage a keyless policy.
public-key              Gets a public key from the key-pair.
save                    Save the container image and associated signatures to disk at the specified directory.
sign                    Sign the supplied container image.
sign-blob               Sign the supplied blob, outputting the base64-encoded signature to stdout.
tree                    Display supply chain security related artifacts for an image such as signatures, SBOMs and attestations
triangulate             Outputs the located cosign image reference. This is the location cosign stores the specified artifact type.
upload                  Provides utilities for uploading artifacts to a registry
verify                  Verify a signature on the supplied container image
verify-attestation      Verify an attestation on the supplied container image
verify-blob             Verify a signature on the supplied blob
verify-blob-attestation Verify an attestation on the supplied blob
version                 Prints the version
Flags:
-h, --help                 help for cosign
--output-file string   log output to a file
-t, --timeout duration     timeout for commands (default 3m0s)
-d, --verbose              log debug output
Additional help topics:
cosign piv-tool                This cosign was not built with piv-tool support!
cosign pkcs11-tool             This cosign was not built with pkcs11-tool support!
Use "cosign [command] --help" for more information about a command.
"--allow-http-registry" flag is not listed in above output.
Do we need create any bug to get address this issue. if yes then let me know will P3 bug for same.
Thanks !

It doesn't appear on the top-level cosign help output because not every command supports this flag.
If you check cosign sign --help for instance it should appear


fix: Deleting State Overwrite in Manifest Reconciler

Closes #868

/retest

Notes
I closed this PR by mistake, the code changes here will break put manifest CR into deleting state.
The implementation of this PR is not done properly, @LeelaChacha if you need further clarification, feel free to reach me.

follow up PR https://github.com/kyma-project/lifecycle-manager/pull/956


Unexpected fill between dots

Hi, thanks for clearing up issue #1 .
I noticed that there's a difference between turtle and svgturtle.
Running:
t = SvgTurtle(1000,1000)
t.penup()
t.hideturtle()
t.forward(200)
t.dot(30,(17/255, 103/255, 45/255))
t.forward(50)
t.dot(30,(17/255,232/255,122/255))
t.save_as('example.svg')

Gives the right color, but between dots there's also color:

Whereas running:
k = Turtle()
k.penup()
k.hideturtle()
k.forward(200)
k.speed('fastest')
k.dot(20,(27/255,223/255,45/255))
k.forward(50)
k.dot(20,(27/255,223/255,45/255))
screen = Screen()
screen.exitonclick()

Produces just the dots:

Looks like you've found more details about donkirkby/live-py-plugin#362. I guess several pieces of the pen state get messed up.
As a workaround, use a clone of the turtle to draw the dot:
from svg_turtle import SvgTurtle

t = SvgTurtle(1000,1000)
t.penup()
t.hideturtle()
t.forward(200)
t.clone().dot(30,(17/255, 103/255, 45/255))
t.forward(50)
t.dot(30,(17/255,232/255,122/255))
t.save_as('example.svg')


chore: update st_role.py

Other
occuring -> occurring

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 62.56%. Comparing base (bdba23e) to head (d8a5a9c).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1490   +/-   ##
=======================================
  Coverage   62.56%   62.56%
=======================================
  Files         287      287
  Lines       17602    17602
=======================================
  Hits        11012    11012
  Misses       6590     6590

Flag
Coverage Δ

?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Does easeprobe supports schedule in every minute?

Currently, the schedule only supports daily, weekly (Sunday), monthly (Last Day), none.
If this schedule can set minutely, meas easeprobe can support Real-time monitoring.

do you mean the SLA report?  I‘d like to understand the reason why you want it every minute.

do you mean the SLA report? I‘d like to understand the reason why you want it every minute. And what does the 'real-time monitoring' mean?

I'd like to set a standard to alert by dingding or other notifications. For example, if the google website returns 500, easeprobe will send alerts. Schedule in every minute give us timely feedback. I beleive if easeprobe supports this function, easeprobe will be more popular.
Just personal opinion! 😉

OK, I see. you want the level trigger instead of the edge trigger, currently, the EaseProbe only supports the edge trigger.  In practice, the level trigger is quite annoying, that's why most probe monitoring software use the edge trigger.  but I am open to supporting the level trigger and different customers can have different choices.
You are welcome to contribute a PR to do this.
And I still don't understand what you mean by "Schedule in every minute"? do you mean probe every minute? or send the SLA report every minute?

Thanks. I'd like to contribute a PR to do this. I mean  probe every minute but SLA report sent by some standards. Only send the SLA report(dingding alerts e.g.) when services reach the standard. For example, if http probe returns 500, SLA report will be sent.

Only send the SLA report(dingding alerts e.g.) when services reach the standard. For example, if http probe returns 500, SLA report will be sent.

may I know why? what's the purpose of this? SLA is a kind of report, the report is a kind of statistics, and it should be sent within the same period, otherwise, how can we know if the SLA getting better or worse?

@EasonAssassin I close this issue as there hasn't response. please feel free open it if you have further ideas.

PR#236 addresses this issued


_ebpf_epoch_release_free_list should re-arm the flush timer if needed

_ebpf_epoch_release_free_list should re-arm the flush timer if needed.
ebpf_epoch_exit currently rearms the flush timer if the per-CPU free list is not empty, but _ebpf_epoch_update_cpu_entry does not. If the logic to rearm the timer is moved to _ebpf_epoch_release_free_list, it will be hit from both paths.

Code no longer exists.


MDC-102 ProductGridFragment.java imports wrong Toolbar library

The instructions clearly state "When importing the Toolbar class, make sure you import androidx.appcompat.widget.Toolbar and not android.widget.Toolbar"
Yet the code shows:
import android.widget.Toolbar;
The finished-codelab code is correct.

Note: I'm a beginner to java and android dev as well as github, so let me know if said anything wrong or posted in the wrong format.
I was getting an error "error: incompatible types: android.widget.Toolbar cannot be converted to androidx.appcompat.widget.Toolbar" while building the app.
The code snippet where the error was shown is here:
private void setUpToolbar(View view) {
Toolbar toolbar = view.findViewById(R.id.app_bar);
AppCompatActivity activity = (AppCompatActivity) getActivity();
if (activity != null) {
activity.setSupportActionBar(toolbar);
}
}
"Toolbar toolbar = view.findViewById(R.id.app_bar);" seems to call the android.widget.Toolbar library which cannot be type casted to the androidx.appcompat.widget.Toolbar library in the "activity.setSupportActionBar(toolbar);" line.
I fixed it by initiating the toolbar as "androidx.appcompat.widget.Toolbar toolbar = view.findViewById(R.id.app_bar)" but this seems to cause the toolbar to turn white instead of blue as shown in the picture. Is this a possible fix and what can be done about the color?

It is now November 7, 2020 --- why hasn't this mistake been corrected.
Should I even trust the rest of these tutorials .
We should not have to be learning by finding mistakes in "tutorials" meant to teach us capabilities.
Very disappointing!


Mobile navigation menu without javascript

@geekplux
I recently stumbled upon https://github.com/paulcarl/skelepico-theme, what intrigued me is the theme's mobile navigation menu is implemented without javascript (preview https://paulcarl.com/skelepico/).
I ported it to this theme, and if you're interested, I can submit a PR. I didn't implement the 'sticky' menu (always shows up on top of page) as I don't like it.
Otherwise, you may close this.

Preview:

Mobile menu

Menu clicked (current)

Menu clicked (my implementation)

welcome PRs. I implemented this mobile menu in a hurry before, you can make a better one.

Cool. I added border to the menu. We need to decide the css values:

[ ] border thickness = 2px

[ ] border color (dark theme) = #999

[ ] border color (light theme) =

[ ] display = block or grid (see below).

display:block;

display:grid;

you can play around with the css values here (look for #menu): https://weyusi.github.io/hexo-testing/2018/10/05/hello-world/
The preview is currently dark theme; once we okay with most of values, we can then decide on light theme's border color.
let me know if margin or padding need to change too, I don't have any preference. Except for text-alight, which I prefer it to be center for nav menu.

some config I prefer:
{
    border: 2px solid #999;
    border-radius: 3px;
    display: grid;
    margin-top: 5px;
    text-align: right;
    padding: 5px 20px;
}

make text-align be right because alignment is important.
what do you think?

yeah, center text-align does look weird when the text is long. FB, GitHub and GitLab use left though, what do you think?

lol, ok, follow your advice

I think #999 may be better. and could you please set position: absolute ? 😆

added absolute.

After https://github.com/geekplux/hexo-theme-typing/pull/35, I notice when hovering the Menu button, it underlines in post, but not in archives page.
I think the appearance of Menu button should be consistent. Underline or not?

Initially, I remember the links in article-entry are with underlined when it hovered, and the links in menu are not.

got it, no underline in menu then.


How to document react compound components using JSDoc?

The way ive gotten it to work is something like this:
`
/**

Component for short texts with colored background. The background color will be a lighter version of the content's color.

@param {Object} props
@param {string} [props.baseColor] - Provide a color in hex. Defaults to black.
@param {React.ReactElement} [props.icon] - Icon element.
@param {Object} [props.sx] - The system prop that allows defining system overrides as well as additional CSS styles.
@param {React.ReactNode} props.label - The content of the component. What goes inside the badge

*/
function Badge(props) {
...
}
`


Docs enhancement (Wiki)

Hi Lukas,
thank you for making this great plugin.
While following the docs, I noticed that for someone who is a beginner with git, this instruction might be confusing:

Important: Please now verify using the search function of your terminal (Ctrl/Cmd F) that no .lock file was added,

I suggest the following edit:

Important: Please now verify that no .lock file was added by listing the added files. Enter git status in your terminal and then use the search function of your terminal (Ctrl/Cmd F) to be sure no .lockfiles were added, since that would break the plugin's behavior later.

(I would have made a PR, but Wikis don't get forked...)

Thanks for your feedback. 👍
Running git status should not be necessary though because git add also lists the files it adds. Or didn't it do that for you?

Or didn't it do that for you?

No, it didn't and doesn't in general when I use git in terminal. But now that you mention it, it totally makes sense...
Although I never (consciously) changed any git settings in that regard...


Mention react-envs in the documentation.

Hello,
As part of my work for INSEE, I worked on a module, react-envs, which aims to abstract away the burden of bundling server environment variables into the app.

I thought it could be a useful mention.
Thank you for your great work.
Best regards

Hi,
I force pushed to try rerunning the CI.


After building the frameworks for the different platforms, I was unable to import the libraries after dragging-and-dropping the frameworks into the Xcode MacOS project

The Xcode project for MacOS AppKit says it cannot find the AudioKit and AudioKitUI frameworks even though they are in my Frameworks folder.  Do I have to go the carthage or cocoapod route?

No, you're just doing something wrong.  Ask this question on StackOverflow please.


Existing values lost when applying Element Template

Describe the Bug
When I select an Element Template, existing values of input or output parameters that the template works with are lost.
Steps to Reproduce
Steps to reproduce the behavior:

Create a Service Task and apply the Mail Task example template.
Fill in sender and receiver.
Deselect the template in the Element Template select box. => Note how the sender and receiver input parameters remain configured as expected on the Input/Output tab.
Apply the Mail Task template again on the same task.

Expected Behavior
Existing values of input/output parameters and other properties are kept and displayed in the fields of the Element Template especially if no default values are defined in the template.
Environment

OS: Ubuntu 18.04.2 LTS
Camunda Modeler Version: 3.0.1 nightly of 2019-04-24

This has been discovered in a customer workshop.

I was able to reproduce it, also with another element template (gzip).

I've re-flagged this as an enhancement, as we never intended to implement that functionality.


deploy failed when run ansible-playbook using openwhisk.yml

I tried the methods of deployment on Ubuntu , ubuntu 18.04
When i run ansible-playbook -i environments/local openwhisk.yml
I deploy agagin but face the same problem,could you please help me find what's wrong,thank you so much!
errors as follow:
TASK [controller : warm up activation path] *********************************************************************************************************************************************************************************************
Saturday 20 April 2024  02:58:17 -0700 (0:00:10.731)       0:01:13.617 ********
fatal: [controller0]: FAILED! => {"access_control_allow_headers": "Authorization, Origin, X-Requested-With, Content-Type,
Accept, User-Agent", "access_control_allow_methods": "GET, DELETE, POST, PUT, HEAD", "access_control_allow_origin": "*",
"changed": false, "connection": "close", "content": "{\"code\":\"FJgvfXLBQbxrTNajxJZ1gWexHd7VN8HI\",\"error\":\"The
requested resource does not exist.\"}", "content_length": "92", "content_type": "application/json", "date": "Sat, 20 Apr 2024
09:58:18 GMT", "json": {"code": "FJgvfXLBQbxrTNajxJZ1gWexHd7VN8HI", "error": "The requested resource does not exist."},
"msg": "Status code was 404 and not [200]: HTTP Error 404: Not Found", "redirected": false, "server": "akka-http/10.2.4",
"status": 404, "url": "https://789c46b1-71f6-4ed5-8c54-816aa4f8c502:abczO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP@<IP_ADDRESS>:10001/api/v1/namespaces/_/actions/invokerHealthTestAction0?blocking=false&result=false", "x_request_id": "FJgvfXLBQbxrTNajxJZ1gWexHd7VN8HI"}
...ignoring

Status code was 404 and not [200]: HTTP Error 404: Not Found

TASK [schedulers : wait until the Scheduler in this host is up and running] ****
Saturday 20 April 2024  03:17:31 -0700 (0:00:00.812)       0:01:54.732 ********
FAILED - RETRYING: wait until the Scheduler in this host is up and running (12 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (11 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (10 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (9 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (8 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (7 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (6 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (5 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (4 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (3 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (2 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running (1 retries left).
fatal: [scheduler0]: FAILED! => {"attempts": 12, "changed": false, "content": "", "msg": "Status code was -1 and not [200]:
Request failed: <urlopen error [Errno 111] 拒绝连接>", "redirected": false, "status": -1, "url": "http://<IP_ADDRESS>:14001/ping"}

Status code was -1 and not [200]: Request failed: <urlopen error [Errno
111] 拒绝连接>

the logs in container scheduler0 as follow:
[2024-04-20T08:24:39.305Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Starting up, Akka version [2.6.12] ...
[2024-04-20T08:24:39.336Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Registered cluster JMX MBean [akka:type=Cluster]
[2024-04-20T08:24:39.336Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Started up successfully
[2024-04-20T08:24:39.350Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - No downing-provider-class configured, manual cluster downing required, see https://doc.akka.io/docs/akka/current/typed/cluster.html#downing
[2024-04-20T08:24:39.382Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] is JOINING itself (with roles [dc-default], version [0.0.0]) and forming new cluster
[2024-04-20T08:24:39.383Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - is the new leader among reachable nodes (more leaders may exist)
[2024-04-20T08:24:39.389Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Leader is moving node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] to [Up]
[2024-04-20T08:24:39.769Z] [INFO] [#tid_sid_unknown] [Config] environment set value for whisk.scheduler.endpoints.host
[2024-04-20T08:24:39.769Z] [INFO] [#tid_sid_unknown] [Config] environment set value for limits.actions.invokes.concurrent
[2024-04-20T08:24:39.769Z] [INFO] [#tid_sid_unknown] [Config] environment set value for whisk.scheduler.endpoints.rpcPort
[2024-04-20T08:24:39.770Z] [INFO] [#tid_sid_unknown] [Config] environment set value for whisk.scheduler.endpoints.akkaPort
[2024-04-20T08:24:39.770Z] [INFO] [#tid_sid_unknown] [Config] environment set value for runtimes.manifest
[2024-04-20T08:24:39.772Z] [INFO] [#tid_sid_unknown] [Config] environment set value for kafka.hosts
[2024-04-20T08:24:39.772Z] [INFO] [#tid_sid_unknown] [Config] environment set value for port
[2024-04-20T08:24:39.872Z] [WARN] Failed to attach the instrumentation because the Kamon Bundle is not present on the classpath
[2024-04-20T08:24:39.959Z] [INFO] Started the Kamon StatsD reporter
[2024-04-20T08:24:40.571Z] [INFO] [#tid_sid_unknown] [KafkaMessagingProvider] created topic scheduler0
[2024-04-20T08:24:40.690Z] [INFO] [#tid_sid_unknown] [KafkaMessagingProvider] created topic creationAck0
[2024-04-20T08:24:41.809Z] [INFO] [#tid_sid_unknown] [LeaseKeepAliveService] Granted a new lease Lease(7802925036371667984,10)
[2024-04-20T08:24:41.824Z] [INFO] [#tid_sid_unknown] [WatcherService] watch endpoint: WatchEndpoint(whisk/instance/scheduler0/lease,7802925036371667984,false,lease-service,Set(DeleteEvent))
Exception in thread "main" java.lang.ExceptionInInitializerError
	at java.base/java.lang.J9VMInternals.ensureError(J9VMInternals.java:184)
	at java.base/java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:173)
	at org.apache.openwhisk.core.scheduler.queue.ElasticSearchDurationCheckerProvider$.instance(ElasticSearchDurationChecker.scala:121)
	at org.apache.openwhisk.core.scheduler.queue.ElasticSearchDurationCheckerProvider$.instance(ElasticSearchDurationChecker.scala:112)
	at org.apache.openwhisk.core.scheduler.Scheduler.<init>(Scheduler.scala:97)
	at org.apache.openwhisk.core.scheduler.Scheduler$.main(Scheduler.scala:350)
	at org.apache.openwhisk.core.scheduler.Scheduler.main(Scheduler.scala)
Caused by: pureconfig.error.ConfigReaderException: Cannot convert configuration to a org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStoreConfig. Failures are:
  at 'whisk.activation-store.elasticsearch':
    - (jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368) Key not found: 'protocol'.
    - (jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368) Key not found: 'hosts'.
    - (jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368) Key not found: 'index-pattern'.
    - (jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368) Key not found: 'username'.
    - (jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368) Key not found: 'password'.

	at pureconfig.package$.getResultOrThrow(package.scala:139)
	at pureconfig.package$.loadConfigOrThrow(package.scala:161)
	at org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore$.<init>(ElasticSearchActivationStore.scala:441)
	at org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore$.<clinit>(ElasticSearchActivationStore.scala)
	... 5 more
[2024-04-20T08:26:33.563Z] [WARN] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Scheduled sending of heartbeat was delayed. Previous heartbeat was sent [7139] ms ago, expected interval is [1000] ms. This may cause failure detection to mark members as unreachable. The reason can be thread starvation, e.g. by running blocking tasks on the default dispatcher, CPU overload, or GC.
bash-5.1$ S

docker ps
root@ubuntu:/home/re/openwhisk/ansible# docker ps
CONTAINER ID   IMAGE                           COMMAND                   CREATED         STATUS         PORTS                                                                                NAMES
f5ce0ffc7d10   whisk/scheduler:latest          "/bin/sh -c 'exec /i…"   8 minutes ago   Up 8 minutes   <IP_ADDRESS>:13001->13001/tcp, <IP_ADDRESS>:21000->21000/tcp, <IP_ADDRESS>:22000->22000/tcp, <IP_ADDRESS>:25520->3551/tcp, <IP_ADDRESS>:14001->8080/tcp   scheduler0
53e1e6089e0f   whisk/controller:latest         "/bin/sh -c 'exec /i…"   8 minutes ago   Up 8 minutes   <IP_ADDRESS>:15000->15000/tcp, <IP_ADDRESS>:16000->16000/tcp, <IP_ADDRESS>:8000->2551/tcp, <IP_ADDRESS>:10001->8080/tcp                              controller0
349459c3d6ed   wurstmeister/kafka:2.13-2.7.0   "start-kafka.sh"          8 minutes ago   Up 8 minutes   <IP_ADDRESS>:9072->9072/tcp, <IP_ADDRESS>:9093->9093/tcp                                                                                kafka0
10f1a16afad4   zookeeper:3.4                   "/docker-entrypoint.…"   9 minutes ago   Up 9 minutes   <IP_ADDRESS>:2181->2181/tcp, <IP_ADDRESS>:2888->2888/tcp, <IP_ADDRESS>:3888->3888/tcp                                                           zookeeper0
0dbbe02d025d   quay.io/coreos/etcd:v3.4.0      "/usr/local/bin/etcd…"   9 minutes ago   Up 9 minutes   <IP_ADDRESS>:2379->2379/tcp, <IP_ADDRESS>:2480->2480/tcp, 2380/tcp                                                                         etcd0
bdd6e9d4619a   apache/couchdb:2.3              "tini -- /docker-ent…"   2 hours ago     Up 2 hours     <IP_ADDRESS>:4369->4369/tcp, <IP_ADDRESS>:5984->5984/tcp, <IP_ADDRESS>:9100->9100/tcp                                                           couchdb

Hi there, I came up with the same problem as you said. Could you tell me how to fix this issue? @re-xmyl

That's generally because the elasticsearch activation store is configured, but no relevant configuration exists.
You can add the following configurations
db_activation_backend: ElasticSearch
elastic_cluster_name: <your elasticsearch cluster name>
elastic_protocol: <your elasticsearch protocol>
elastic_index_pattern: <your elasticsearch index pattern>
elastic_base_volume: <your elasticsearch volume directory>
elastic_username: <your elasticsearch username>
elastic_password: <your elasticsearch username>

https://github.com/apache/openwhisk/tree/master/ansible#optional-enable-elasticsearch-activation-store

Thanks for @style95  kindness, but I haven't configured elasticsearch as the db_activation_store, and after change the configuration in ansible/group_vars/all as follows
  artifact_store:
    backend: "CouchDB"
    #backend: "{{ db_artifact_backend | default('CouchDB') }}"

or specify as follows when deploying ansible-playbook -i environments/$ENVIRONMENT openwhisk.yml -e db_activation_backend=CouchDB
it still ran into the same error and address <IP_ADDRESS>:14001 still refused connections...

If you don't want to deploy elasticsearch, could you try with NoopDurationCheckerProvider?
You can replace ElasticSearchDurationCheckerProvider in common/scala/src/main/resources/reference.conf.
https://github.com/apache/openwhisk/tree/master/ansible#configure-service-providers-for-the-scheduler

Thanks @style95 ! Well, I tried it. But the Connection refused error still persists and the log showed different content
[2024-05-13T08:50:34.531Z] [INFO] Slf4jLogger started
[2024-05-13T08:50:34.985Z] [INFO] Remoting started with transport [Artery tcp]; listening on address [akka://scheduler-actor-system@<IP_ADDRESS>:25520] and bound to [akka://scheduler-actor-system@<IP_ADDRESS>:3551] with UID [2047018891666814238]
[2024-05-13T08:50:35.010Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Starting up, Akka version [2.6.12] ...
[2024-05-13T08:50:35.083Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Registered cluster JMX MBean [akka:type=Cluster]
[2024-05-13T08:50:35.083Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Started up successfully
[2024-05-13T08:50:35.119Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - No downing-provider-class configured, manual cluster downing required, see https://doc.akka.io/docs/akka/current/typed/cluster.html#downing
[2024-05-13T08:50:35.161Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] is JOINING itself (with roles [dc-default], version [0.0.0]) and forming new cluster
[2024-05-13T08:50:35.163Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - is the new leader among reachable nodes (more leaders may exist)
[2024-05-13T08:50:35.175Z] [INFO] Cluster Node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] - Leader is moving node [akka://scheduler-actor-system@<IP_ADDRESS>:25520] to [Up]
[2024-05-13T08:50:35.962Z] [INFO] [#tid_sid_unknown] [Config] environment set value for whisk.scheduler.endpoints.host
[2024-05-13T08:50:35.963Z] [INFO] [#tid_sid_unknown] [Config] environment set value for limits.actions.invokes.concurrent
[2024-05-13T08:50:35.963Z] [INFO] [#tid_sid_unknown] [Config] environment set value for whisk.scheduler.endpoints.rpcPort
[2024-05-13T08:50:35.963Z] [INFO] [#tid_sid_unknown] [Config] environment set value for whisk.scheduler.endpoints.akkaPort
[2024-05-13T08:50:35.963Z] [INFO] [#tid_sid_unknown] [Config] environment set value for runtimes.manifest
[2024-05-13T08:50:35.963Z] [INFO] [#tid_sid_unknown] [Config] environment set value for kafka.hosts
[2024-05-13T08:50:35.963Z] [INFO] [#tid_sid_unknown] [Config] environment set value for port
[2024-05-13T08:50:36.157Z] [WARN] Failed to attach the instrumentation because the Kamon Bundle is not present on the classpath
[2024-05-13T08:50:36.355Z] [INFO] Started the Kamon StatsD reporter
[2024-05-13T08:50:37.697Z] [INFO] [#tid_sid_unknown] [KafkaMessagingProvider] created topic scheduler0
[2024-05-13T08:50:38.122Z] [INFO] [#tid_sid_unknown] [KafkaMessagingProvider] created topic creationAck0
[2024-05-13T08:50:40.444Z] [INFO] [#tid_sid_unknown] [LeaseKeepAliveService] Granted a new lease Lease(7802925545492717579,10)
[2024-05-13T08:50:40.457Z] [INFO] [#tid_sid_unknown] [WatcherService] watch endpoint: WatchEndpoint(whisk/instance/scheduler0/lease,780
2925545492717579,false,lease-service,Set(DeleteEvent))
Exception in thread "main" java.lang.ClassCastException: org.apache.openwhisk.core.scheduler.queue.NoopDurationChecker$ incompatible with org.apache.openwhisk.spi.Spi
        at org.apache.openwhisk.spi.SpiLoader$.get(SpiLoader.scala:41)
        at org.apache.openwhisk.core.scheduler.Scheduler.<init>(Scheduler.scala:96)
        at org.apache.openwhisk.core.scheduler.Scheduler$.main(Scheduler.scala:350)
        at org.apache.openwhisk.core.scheduler.Scheduler.main(Scheduler.scala)

seems another issue...

@SCDESPERTATE
How did you configure your reference.conf?

My apology, I made a mistake. I messed up the NoopDurationCheckerProvider and NoopDurationChecker.
Sorry for wasting @style95 's time. Appreciate your patience!
After replacing ElasticSearchDurationCheckerProvider, the set up went well and the result was as follows
PLAY RECAP ************************************************************************************************************
<IP_ADDRESS>                 : ok=17   changed=6    unreachable=0    failed=0    skipped=9    rescued=0    ignored=0
ansible                    : ok=2    changed=1    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
controller0                : ok=29   changed=3    unreachable=0    failed=0    skipped=23   rescued=0    ignored=1
etcd0                      : ok=5    changed=1    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0
invoker0                   : ok=31   changed=7    unreachable=0    failed=0    skipped=40   rescued=0    ignored=0
kafka0                     : ok=10   changed=4    unreachable=0    failed=0    skipped=7    rescued=0    ignored=0
scheduler0                 : ok=20   changed=3    unreachable=0    failed=0    skipped=14   rescued=0    ignored=0

星期一 13 五月 2024  18:13:06 +0800 (0:00:00.167)       0:04:10.413 ****************
===============================================================================
invoker : pull runtime action images per manifest ------------------------------------------------------------- 36.14s
controller : wait until the Controller in this host is up and running ----------------------------------------- 22.66s
invoker : wait until Invoker is up and running ---------------------------------------------------------------- 12.54s
schedulers : wait until the Scheduler in this host is up and running ------------------------------------------ 11.96s
kafka : wait until the kafka server started up ----------------------------------------------------------------- 8.00s
zookeeper : wait until the Zookeeper in this host is up and running -------------------------------------------- 7.88s
cli : Unarchive the individual tarballs ------------------------------------------------------------------------ 7.77s
etcd : (re)start etcd ------------------------------------------------------------------------------------------ 6.83s
schedulers : populate environment variables for scheduler ------------------------------------------------------ 5.79s
kafka : (re)start kafka using 'bitnami/kafka:latest'  ---------------------------------------------------------- 5.26s
controller : warm up activation path --------------------------------------------------------------------------- 5.16s
zookeeper : (re)start zookeeper -------------------------------------------------------------------------------- 4.88s
invoker : copy keystore, key and cert -------------------------------------------------------------------------- 4.85s
invoker : populate environment variables for invoker ----------------------------------------------------------- 3.69s
controller : populate environment variables for controller ----------------------------------------------------- 3.58s
controller : copy certificates --------------------------------------------------------------------------------- 3.48s
cli : Unarchive the individual zipfiles into binaries ---------------------------------------------------------- 3.33s
nginx : copy cert files from local to remote in nginx config directory ----------------------------------------- 3.16s
Gathering Facts ------------------------------------------------------------------------------------------------ 3.09s
nginx : pull the nginx:1.21.1 image ---------------------------------------------------------------------------- 2.93s

I have exported the wsk cli as the environment variable, and configure the CLI as
wsk property set \
  --apihost 'http://localhost:3233' \
  --auth '23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP'

it returned as expected
ok: whisk auth set. Run 'wsk property get --auth' to see the new value.
ok: whisk API host set to http://localhost:3233

but when I tried wsk action create hello ./tests/dat/actions/hello.js, it still returned error😟
error: Unable to create action 'hello': Put "http://localhost:3233/api/v1/namespaces/_/actions/hello?overwrite=false": dial tcp <IP_ADDRESS>:3233: connect: connection refused

It seems you are using a deployment deployed with the ansible commands but your endpoint looks like the one of standalone mode.
If you deploy OW with ansible, the endpoint is generally https://localhost.
You may want to use -i option if you use a self-signed certificate for HTTPS which is the default.
wsk list -i

I'm encountering an issue after replacing ElasticSearchDurationCheckerProvider. Could you please let me know if you've faced this problem and how you resolved it?fatal: [controller0]: FAILED! => {"cache_control": "must-revalidate", "changed": false, "connection": "close", "content": "", "content_length": "58", "content_type": "application/json", "date": "Wed, 02 Oct 2024 11:08:35 GMT", "msg": "Status code was 404 and not [200]: HTTP Error 404: Object Not Found", "redirected": false, "server": "CouchDB/2.3.1 (Erlang OTP/19)", "status": 404, "url": "http://<IP_ADDRESS>:5984/whisk_local_subjects", "x_couch_request_id": "fcb33f3516", "x_couchdb_body_time": "0"}
Status code was 404 and not [200]: HTTP Error 404: Object Not Found
PLAY RECAP ******************************************************************************************************************************************************************************************************************************
controller0                : ok=12   changed=4    unreachable=0    failed=1

I'm encountering an issue after replacing ElasticSearchDurationCheckerProvider. Could you please let me know if you've faced this problem and how you resolved it?fatal: [controller0]: FAILED! => {"cache_control": "must-revalidate", "changed": false, "connection": "close", "content": "", "content_length": "58", "content_type": "application/json", "date": "Wed, 02 Oct 2024 11:08:35 GMT", "msg": "Status code was 404 and not [200]: HTTP Error 404: Object Not Found", "redirected": false, "server": "CouchDB/2.3.1 (Erlang OTP/19)", "status": 404, "url": "http://<IP_ADDRESS>:5984/whisk_local_subjects", "x_couch_request_id": "fcb33f3516", "x_couchdb_body_time": "0"}
Status code was 404 and not [200]: HTTP Error 404: Object Not Found
PLAY RECAP ****************************************************************************************************************************************************************************************************************************** controller0 : ok=12 changed=4 unreachable=0 failed=1

You need to go to go to/openwhisk/ansible/environments/local/group_vars/all and add this:
db_activation_backend: ElasticSearch


test github action ci without permission

as titile
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@frankvicky could you please remove develocity-access-key: ${{ secrets.GE_ACCESS_TOKEN }} to file another PR?

FYI @chia7712 and @frankvicky the ASF github runners are having trouble this morning

the ASF github runners are having trouble this morning

I wish this bad news does not extinguish our love for github CI :)

BTW, I'm surprised this PR was able to trigger the actions. I was under the impression that this setting is turned off for apache/kafka

I checked with Infra and they say apache/kafka is currently configured to require approval for PRs from non-committers to trigger workflows.
@chia7712 did you have to manually approve @frankvicky's PRs to run?

close as #16936 is almost completed

did you have to manually approve @frankvicky's PRs to run?

no, I did not do that (sorry that I missed your comment). Actually, I expected to see the "Approve" button also...


ModelFactory.php - Naming Convention like Class but it is no class?

This is an improvement Idea or at least thought, as laravel is highly based on  conventions (what I really appreciate): I was quite confused (also being quite new in PHP), that the database\factories\ModelFactory.php File is named as according Class-Conventions (CamelCase) but actually contains "only"
$factory->define(App\User::class, function (Faker\Generator $faker) {       return [             'name' => $faker->name,             'email' => $faker->email,             'password' => bcrypt(str_random(10)),           'remember_token' => str_random(10),       ];   });
would maybe the naming "factory.php" might be more correct as filename?
Background: For a newbie this is not easy to understand where the $factory variable magically appears. More clear to understand is for example the routes.php file with Facades like Route::group() so you know exactly the "callpath" and can easyly understand the logic/callpath. Maybe here something like Faker::define() would be more clear?
Thanks.

There is no class in that file.

So, we can name it what we like. ;)

Yes you are correct its not a Class and as you stated/argumented it the other way round, please let me clarify what I mean:
I meant only name Classes CamelCase, everything else (config files, functional helpers) lowercase. And I think this is followed (what I really appreciate) everywhere I have encountered (like route files and configfiles) in the framework so far.  And the FactoryModel.php seems to be a configuration of a Model-Factory (but not a Model Factory itself!). So to be in line with for example route.php I think it would be more correctly named lowercase (factory.php).
Just want to prevent someone later writing "Laravel - A Fractal of Bad Design" if too many inconsistencies are introduced.
But thanks for the answer, appreciate it. I only want to make larvel better.


KWP Slow init with v1 != v2

Hi,
I was trying to communicate with ODB2 with my 206 1.1cc auto peugeot which should have the KWB2000 slow protocol.
I built the optoisolated hardware interface and it works properly with perfect signal ascent and descent fronts.
I started testing examples of read_softserial.ino library and modified readerKWP.ino for AltSoftSerial.
The first example with debug enabled has this log :
"
Looping
Before magic 5 baud.
Before setting port.
After setting port.
First read is: 85
read v1: 233
read v2: 143
v1: 233
v2: 143
init_success: 0
"
The problem is that the numbers V1 and V2 are different and initialization fails.
With the second example it fails without log.
I don't understand why V1 values other than V2.
Some suggestions?

I did it ;-)
The protocol is KWP2000 slow.
With the initKWP function, initialization was unsuccessful.
So I modified it this way :
bool OBD9141::initKWP(){
    use_kwp_ = true;
    // this function performs the ISO9141 5-baud 'slow' init.
    this->set_port(false); // disable the port.
    this->kline(true);

    delay(OBD9141_INIT_IDLE_BUS_BEFORE); // no traffic on bus for 3 seconds.
    OBD9141println("Before magic 5 baud.");
    // next, send the startup 5 baud init..
    this->kline(false); //digitalWrite(7,LOW);
    delay(200); // start

    this->kline(true); //digitalWrite(7,HIGH);
    delay(400);  // first two bits

    this->kline(false); //digitalWrite(7,LOW);
    delay(400); // second pair

    this->kline(true); //digitalWrite(7,HIGH);
    delay(400);  // third pair

    this->kline(false); //digitalWrite(7,LOW);
    delay(400); // last pair

    this->kline(true); //digitalWrite(7,HIGH);
    delay(200);  // stop bit

    // this last 200 ms delay could also be put in the setTimeout below.
    // But the spec says we have a stop bit.

    // done, from now on it the bus can be treated ad a 10400 baud serial port.

    OBD9141println("Before setting port.");
    this->set_port(true);
    OBD9141println("After setting port.");
    uint8_t mess[1];

    this->serial->setTimeout(300+200);
    // wait should be between 20 and 300 ms long

    // read first value into buffer, should be 0x55
    if (this->serial->readBytes(mess, 1)){
        OBD9141print("First read is: "); OBD9141println(mess[0]);
        if (mess[0] != 0x55){
            return false;
        }
    } else {
        OBD9141println("Timeout on read 0x55.");
        return false;
    }
    // we get here after we have passed receiving the first 0x55 from ecu.

    this->serial->setTimeout(20); // w2 and w3 are pauses between 5 and 20 ms

    uint8_t v1=0, v2=0; // sent by car:  (either 0x08 or 0x94)

    // read v1
    if (!this->serial->readBytes(mess, 1)){
        OBD9141println("Timeout on read v1.");
        return false;
    } else {
        v1 = mess[0];
        OBD9141print("read v1: "); OBD9141println(v1);
    }

    // read v2
    if (!this->serial->readBytes(mess, 1)){
        OBD9141println("Timeout on read v2.");
        return false;
    } else {
        v2 = mess[0];
        OBD9141print("read v2: "); OBD9141println(v2);
    }

    OBD9141print("v1: "); OBD9141println(v1);
    OBD9141print("v2: "); OBD9141println(v2);

    // these two should be identical according to the spec.
    //if (v1 != v2){
    //    return false;
    //}

    // we obtained w1 and w2, now invert and send it back.
    // tester waits w4 between 25 and 50 ms:
    delay(30);
    this->write(~v2);
    this->serial->setTimeout(50); // w5 is same as w4...  max 50 ms

    // finally, attempt to read 0xCC from the ECU, indicating succesful init.
    if (!this->serial->readBytes(mess, 1)){
        OBD9141println("Timeout on 0xCC read.");
        return false;
    } else {
        OBD9141print("read 0xCC?: "); OBD9141println(mess[0]);
        if ((mess[0] == 0xCC)){
            delay(OBD9141_INIT_POST_INIT_DELAY);
            // this delay is not in the spec, but prevents requests immediately
            // after the finishing of the init sequency.
        } else {
            return false;
        }
    }

    this->serial->setTimeout(300+200);
    // wait should be between 20 and 300 ms long

    // startCommunicationRequest message:
    uint8_t message[4] = {0xC1, 0x33, 0xF1, 0x81};
    // checksum (0x66) is calculated by request method.

    // Send this request and read the response
    if (this->requestKWP(&message, 4) == 6) {
        // check positive response service ID, should be 0x7F.
        OBD9141print("read 0x7F?: "); OBD9141println(buffer[3]);
        if (this->buffer[3] == 0x7F) {
            // Not necessary to do anything with this data?
            return true;
        } else {
            return false;
        }
    }
    return false;
}

The readKWP.ino file modified for arduino one :
#include "Arduino.h"
#include "AltSoftSerial.h"
#include "OBD9141.h"

#define TXL_PIN 7     // connect to transceiver TxL
#define RX_PIN 8
#define TX_PIN 9
#define EN_PIN 2

AltSoftSerial altSerial;
OBD9141 obd;

void setup(){
    Serial.begin(9600);
    delay(2000);

    pinMode(EN_PIN, OUTPUT);
    digitalWrite(EN_PIN, HIGH);

    obd.begin(altSerial, RX_PIN, TX_PIN);

}

void loop(){
    Serial.println("Looping");

    // only change from reader is the init method here.
    uint8_t init_success =  obd.initKWP();
    Serial.print("init_success:");
    Serial.println(init_success);
    delay(50);

    //init_success = true;
    // Uncomment this line if you use the simulator to force the init to be
    // interpreted as successful. With an actual ECU; be sure that the init is
    // succesful before trying to request PID's.

    if (init_success){
        bool res;
        while(1){
            res = obd.getCurrentPID(0x11, 1);
            if (res){
                Serial.print("Result 0x11 (throttle): ");
                Serial.println(obd.readUint8());
            }
            delay(50);

            res = obd.getCurrentPID(0x0C, 2);
            if (res){
                Serial.print("Result 0x0C (RPM): ");
                Serial.println(obd.readUint16()/4);
            }
            delay(50);

            res = obd.getCurrentPID(0x0D, 1);
            if (res){
                Serial.print("Result 0x0D (speed): ");
                Serial.println(obd.readUint8());
            }
            Serial.println();

            delay(200);
        }
        delay(200);
    }
    delay(3000);
}

TXL didn't help me.
In the hardware interface I also made the L-Line, but it is not needed with my car.
Serial Monitor:
Looping
Before magic 5 baud.
Before setting port.
After setting port.
First read is: 85
read v1: 233
read v2: 143
v1: 233
v2: 143
read 0xCC?: 204
Rem: 6
ret_len: 7
R: 131 241 16 127 129 17 149 0
calc cs: 149
buf cs: 149
ok
6
read 0x7F?: 127
init_success:1

With car on but stopped:
Result 0x11 (throttle): 63
Rem: 7
ret_len: 8
R: 132 241 16 65 12 22 108 84 0
calc cs: 84
buf cs: 84
ok
7
Result 0x0C (RPM): 1435
Rem: 6
ret_len: 7
R: 131 241 16 65 13 0 210 0
calc cs: 210
buf cs: 210
ok
6
Result 0x0D (speed): 0

Optoisolated interface scheme :

Hey,
Hmm, I've never seen v1 and v2 not being identical, I think the spec says they should be... The values you get (233 and 143) as not even bitwise inverts of each other or something that could perhaps make sense... What is good to see is that your updated initialization code still sends ~v2 and then we get the 0xCC back from the ECU that confirms the initialization succeeded.
I wonder if the slow part of your initKWP function is somehow just acting as a wakeup signal or something and the end of the KWP init still takes care of the actual initialization :thinking: Regardless, it is working, that's what matters!
I'm glad you got it working :) Thanks for reporting the problem you encountered and the resolution.

I left this information to initialize odb2 kwp2000 :
https://m0agx.eu/2018/01/02/reading-obd2-data-without-elm327-part-2-k-line/

I never got back to this, nor did I read the link you sent. But when answering on #41, I realised that the 233 and 143 looked familiar and looked this issue back up.
I've just filed https://github.com/iwanders/OBD9141/pull/42 which implements the same discoveries we had in #41 as you had to make this work.


Creation of publisher failed: rosserial_tivac_tutorials/buttons

Hello,
I tried running all tutorial examples, and all work except rgb_srv and buttons. After flashing the tiva-c launchpad with the buttons_flash, I get the following error when I run rosserial. It is unable to create  the publisher. All the other publishers in other examples are created without problem.
Best regards,
C.
can@rose:~$ rosrun rosserial_python serial_node.py _port:=/dev/ttyACM0 _baud:=57600 [INFO] [1542288895.635277]: ROS Serial Python Node [INFO] [1542288895.638645]: Connecting to /dev/ttyACM0 at 57600 baud [INFO] [1542288897.742894]: Requesting topics... [ERROR] [1542288897.834147]: Creation of publisher failed: rosserial_tivac_tutorials ROS path [0]=/opt/ros/melodic/share/ros ROS path [1]=/opt/ros/melodic/share [ERROR] [1542288897.899475]: Tried to publish before configured, topic id 125 [INFO] [1542288897.900779]: Requesting topics... [ERROR] [1542288898.010139]: Tried to publish before configured, topic id 125 [INFO] [1542288898.011351]: Requesting topics... [ERROR] [1542288898.030703]: Creation of publisher failed: rosserial_tivac_tutorials ROS path [0]=/opt/ros/melodic/share/ros ROS path [1]=/opt/ros/melodic/share [ERROR] [1542288898.120896]: Tried to publish before configured, topic id 125 [INFO] [1542288898.122196]: Requesting topics... [ERROR] [1542288898.141507]: Creation of publisher failed: rosserial_tivac_tutorials ROS path [0]=/opt/ros/melodic/share/ros ROS path [1]=/opt/ros/melodic/share [ERROR] [1542288898.231571]: Tried to publish before configured, topic id 125

This error happens because the message files are not in path.

cd ~/catkin_ws
source devel/setup.bash

solves the problem.


Suppress warnings about "already initialized constant"s in bundle update spec

For the bundle update --ruby spec in commands/update_spec.rb, the double execution of install_gemfile causes the following warnings for each context: warning: already initialized constant RUBY_VERSION and warning: already initialized constant RUBY_PATCHLEVEL. This PR suppresses these extraneous warnings and cleans up the RSpec test suite output.

What's wrong with expect_err?

@segiddins Ah, oversight on my part. Basically reinvented the expect_err wheel there. All the existing spec support/helper infrastructure for suppressing these warnings is already there so switched the PR to simply utilize the expect_err option.

On further inspection, I think we can get rid of those warnings just by using the spec helper for simulating a ruby version?

Which spec helper are you referring to? The only one I found that can simulate a ruby version seems to be simulate_ruby_engine(engine, version = "1.6.0"). This could simulate changing the ruby version through the ENV and the BUNDLER_SPEC_RUBY_ENGINE_VERSION value in particular, but I don't see how this affects these specific tests as they're primarily working with Gemfile creation with particular information and Gemfile.lock creation/updating (via bundle update) with particular information?

Also, a quick note on the design of these specs, it seems that they're asserting/setting up the scenarios incorrectly?
  it "removes the Ruby from the Gemfile.lock" do
      install_gemfile <<-G
          ::RUBY_VERSION = '2.1.3'
          ::RUBY_PATCHLEVEL = 100
          ruby '~> 2.1.0'
      G

      install_gemfile <<-G
          ::RUBY_VERSION = '2.1.4'
          ::RUBY_PATCHLEVEL = 222
      G

      bundle "update --ruby"

      lockfile_should_be <<-L
       GEM
         specs:

       PLATFORMS
         ruby

       DEPENDENCIES

       BUNDLED WITH
          #{Bundler::VERSION}
      L
    end

In the following code, the Gemfile is getting created with the first configuration, then overwritten with the second configuration, then the bundle update --ruby command is being executed which actually creates the Gemfile.lock file I believe. Then, the assertion is made that the Gemfile.lock file should be a certain configuration but there was no Gemfile.lock file that was created with the first Gemfile configuration. The Gemfile.lock that exists (if one does) in the tmp/bundled_app directory before bundle update --ruby is a polluted one from some other spec that did not clean up the file.
This seems incorrect as it seems that the assertion is supposed to test that the Gemfile.lock internals that are created from the first Gemfile configuration are different in some manner (missing ruby 2.1.3p100) from the Gemfile.lock internals set by calling bundle update --ruby on the second configured Gemfile.
I think we should be running bundle update --ruby after the first install_gemfile call as well to generate the Gemfile.lock file with that first Gemfile configuration. Additionally, we should cleaning up tmp/bundled_app/Gemfile.lock and tmp/bundled_app/Gemfile before (or after?) each of these specs.

Something like:
before do
  clear_gemfile
  clear_gemfile_lock
end
context "when the Gemfile removes the ruby" do
  it "removes the Ruby from the Gemfile.lock" do
    #No Gemfile or Gemfile.lock exists in tmp/bundled_app
    install_gemfile <<-G, :expect_err => true
        ::RUBY_VERSION = '2.1.3'
        ::RUBY_PATCHLEVEL = 100
        ruby '~> 2.1.0'
    G
    #Gemfile with first config created, no Gemfile.lock

    bundle "update --ruby"

    #Gemfile with first config created, Gemfile.lock created off first config

=begin
    Gemfile.lock should be at this state right now
    lockfile_should_be <<-L
     GEM
       specs:

     PLATFORMS
       ruby

     DEPENDENCIES

     RUBY VERSION
        ruby 2.1.3p100

     BUNDLED WITH
        #{Bundler::VERSION}
    L
=end

    install_gemfile <<-G, :expect_err => true
        ::RUBY_VERSION = '2.1.4'
        ::RUBY_PATCHLEVEL = 222
    G

    #Gemfile with second config created, Gemfile.lock off first config still there

    bundle "update --ruby"

    #Gemfile with second config still there, Gemfile.lock off created off second config
    #If bundle update --ruby wasn't working right, Gemfile.lock should not have changed

    #Below assertion checks that Gemfile.lock has indeed changed

    lockfile_should_be <<-L
     GEM
       specs:

     PLATFORMS
       ruby

     DEPENDENCIES

     BUNDLED WITH
        #{Bundler::VERSION}
    L
  end
end

Apologize if it's a bit hard to read with the unhelpful way the Ruby comments are displayed/rendered on Github.

Updated the PR with these corrections in test setup.

Renamed clear_gemfile and clear_gemfile_lock to delete_gemfile and delete_gemfile_lock. Not sure if we want to use these more aggressively to prevent test pollution or in a global before/after way.

@RochesterinNYC the bundled app directory is blown away between tests already.

@segiddins Oh okay, gotcha. Does that also apply for running a single test as well? I was encountering issues with inconsistent results with running the same test a few times in a row and it seemed as if the Gemfile and Gemfile.lock were persisting. If it does apply, then I'll remove delete_gemfile and delete_gemfile_lock.

That would be a separate issue, bundled app should be deleted before every test.

@segiddins Okay, removed any mention of delete_gemfile*.
Okay, dug around a bit and noticed that it's reset! that deletes the tmp/bundled_app directory along with some other stuff and reset! gets called before each spec so my flakiness must have been a personal system issue or something. The reason I was confused by that was because reset! isn't called after specs so my tmp files including bundled_app were still there after any specs were run, but now I see that it won't interfere with the validity of any actual specs. All clear now :+1:

@RochesterinNYC lingering tmp files are actually a plus when debugging single specs :)

Gotcha, valid point :+1:

Anything else needed on this PR?

Looks good to me :)
Just want @indirect to approve it

@homu r+

:pushpin: Commit 6065616 has been approved by indirect

:hourglass: Testing commit 6065616 with merge 69b87ac...

:sunny: Test successful - status


fix: fixed missing css vars

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 81.851%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5849

Relevant Lines:
6577

💛  - Coveralls


🌱 Use upstream repo instead of forked in e2e testing

What this PR does / why we need it:
Point to upstream repo instead of forked one in e2e testing
Special notes for your reviewer:
@Danil-Grigorev I found this commit https://github.com/richardcase/fleet-clusters/compare/main...Danil-Grigorev:fleet-clusters:main on top of the https://github.com/rancher-sandbox/rancher-turtles-fleet-example repo commits. Does the latter need to be synced with your fork or can be dropped?
Checklist:

[X] squashed commits into logical changes
[ ] includes documentation
[ ] adds unit tests
[ ] adds or updates e2e tests

Let’s try this first to make sure that kindnet CNI works, previous configuration was using calico, as kindnet had some issues with pulling rancher agent image inside the cluster

Let’s try this first to make sure that kindnet CNI works, previous configuration was using calico, as kindnet had some issues with pulling rancher agent image inside the cluster

Tried it locally, https://github.com/rancher-sandbox/rancher-turtles/blob/36b2e7730d142420f2332be305b964db895b7d72/test/e2e/import_test.go#L61-L72 is timing out with this change and moving on without. What is the compromise if we backport the changes to use calico instead of kindnet?
/cc @richardcase

I don't have a strong opionion on whether we use Kindnet or Calico...whatever works. Although, if Kindnet wasn't working then it would be good to at least know the root cause

With kindnet this is how the agent pod looks like when it attempts to deploy in the cluster:
cattle-system  cattle-cluster-agent-6f879ddc7-fnqt6                  ●  0/1          0 ImagePullBackOff  <IP_ADDRESS>

Basically no rancher images could be pulled from inside the cluster with default configuration: Back-off pulling image "rancher/rancher-agent:v2.7.5"
No errors are shown in any other pods.


⚠ ClamAV has degraded performance

In 612d878, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 91 ms

Resolved: ClamAV performance has improved in cdffa10.


Showing navbar menu only if user authenticated.

Hello there! I am developing an angularJS web application using ng-token-auth and an API using devise-token-auth in two separate apps. My main problem is that I want to hide (not really hide, but avoid rendering it) some html if there is no session started (So this html is not visible using 'inspect element') . Is this possible using angularJS?  I also think my problem here is about angularJS and not about this library in particular, but since I am using ng-token-auth and its "helpers" for managing sessions, I found appropriate to ask this question here.
Thanks.

Hello!
I think ng-if="user.signedIn" will help you


Max Memory Error - 10MB Max

I am trying to open and parse large word documents (50-100 Megabytes).  I consistently get an AttValue length too long error and I believe it is from the maximum xml parsing size referenced https://stackoverflow.com/questions/33828728/what-is-the-maximum-size-of-an-xml-file-when-using-pythons-lxml-etree
I wanted to confirm that my beliefs of the cause of the error are correct and if would be possible to increase the maximum size that python-docx can parse?
The trace back is listed below:
self.doc = Document(self.path)
File "C:\Python310\lib\site-packages\docx\api.py", line 25, in Document
document_part = Package.open(docx).main_document_part
File "C:\Python310\lib\site-packages\docx\opc\package.py", line 130, in open
Unmarshaller.unmarshal(pkg_reader, package, PartFactory)
File "C:\Python310\lib\site-packages\docx\opc\package.py", line 198, in unmarshal
parts = Unmarshaller._unmarshal_parts(
File "C:\Python310\lib\site-packages\docx\opc\package.py", line 215, in unmarshal_parts
parts[partname] = part_factory(
File "C:\Python310\lib\site-packages\docx\opc\part.py", line 191, in new
return PartClass.load(partname, content_type, blob, package)
File "C:\Python310\lib\site-packages\docx\opc\part.py", line 231, in load
element = parse_xml(blob)
File "C:\Python310\lib\site-packages\docx\oxml_init.py", line 28, in parse_xml
root_element = etree.fromstring(xml, oxml_parser)
File "src\lxml\etree.pyx", line 3252, in lxml.etree.fromstring
File "src\lxml\parser.pxi", line 1913, in lxml.etree._parseMemoryDocument
File "src\lxml\parser.pxi", line 1800, in lxml.etree._parseDoc
File "src\lxml\parser.pxi", line 1141, in lxml.etree._BaseParser._parseDoc
File "src\lxml\parser.pxi", line 615, in lxml.etree._ParserContext._handleParseResultDoc
File "src\lxml\parser.pxi", line 725, in lxml.etree._handleParseResult
File "src\lxml\parser.pxi", line 654, in lxml.etree._raiseParseError
File "", line 2
lxml.etree.XMLSyntaxError: AttValue length too long, line 2, column 11006082

i have this question as yours .
Traceback (most recent call last):
File "3wordgetjpg_error1.py", line 84, in
get_pictures(row[0],row[0][0:-5])
File "3wordgetjpg_error1.py", line 52, in get_pictures
doc = docx.Document(word_path)
File "e:\Anaconda3\lib\site-packages\docx\api.py", line 25, in Document
document_part = Package.open(docx).main_document_part
File "e:\Anaconda3\lib\site-packages\docx\opc\package.py", line 130, in open
Unmarshaller.unmarshal(pkg_reader, package, PartFactory)
File "e:\Anaconda3\lib\site-packages\docx\opc\package.py", line 199, in unmarshal
pkg_reader, package, part_factory
File "e:\Anaconda3\lib\site-packages\docx\opc\package.py", line 216, in unmarshal_parts
partname, content_type, reltype, blob, package
File "e:\Anaconda3\lib\site-packages\docx\opc\part.py", line 191, in new
return PartClass.load(partname, content_type, blob, package)
File "e:\Anaconda3\lib\site-packages\docx\opc\part.py", line 231, in load
element = parse_xml(blob)
File "e:\Anaconda3\lib\site-packages\docx\oxml_init.py", line 28, in parse_xml
root_element = etree.fromstring(xml, oxml_parser)
File "src\lxml\etree.pyx", line 3237, in lxml.etree.fromstring
File "src\lxml\parser.pxi", line 1896, in lxml.etree._parseMemoryDocument
File "src\lxml\parser.pxi", line 1784, in lxml.etree._parseDoc
File "src\lxml\parser.pxi", line 1141, in lxml.etree._BaseParser._parseDoc
File "src\lxml\parser.pxi", line 615, in lxml.etree._ParserContext._handleParseResultDoc
File "src\lxml\parser.pxi", line 725, in lxml.etree._handleParseResult
File "src\lxml\parser.pxi", line 654, in lxml.etree._raiseParseError
File "", line 2
lxml.etree.XMLSyntaxError: AttValue length too long, line 2, column 13284651


[FEATURE] QianfanChatModel does not support http proxy setting

Is your feature request related to a problem? Please describe.
While QianfanClient has proxy setting, QianfanChatModel which uses the client does not have proxy setting parameters, which makes it impossible to use under certain network condition.
Describe the solution you'd like
Add proxy setting parameters in QianfanChatModel / QianfanStreamingChatModel / QianfanEmbeddingModel
Describe alternatives you've considered
Any alternative methods for setting proxy for service based AI models will do.
Additional context

LangChain4j version: 0.29.1

Implemented in https://github.com/langchain4j/langchain4j/pull/1159


Runtime option for limiting optimistic lookahead

New option for restricting optimistic lookahead.

If this merge represents a feature addition to ROSS, the following items must be completed before the branch will be merged:

[ ] Document the feature on the blog (See the Contributing guide in the gh-pages branch).
Include a link to your blog post in the Pull Request.
[x] One or more TravisCI tests should be created (and they should pass)
[x] Through the TravisCI tests, coverage should increase
[ ] Test with CODES to ensure everything continues to work

In irregular simulations, runtime crashes are caused due to memory overflow.
This often happens because some LPs over-optimisitcally explore events in
virtual time and are repeatedly rolled back. One user-defined way of avoiding
these crashes is to restrict the optimistic lookahead in terms of virtual time.
Option added: max-opt-lookahead
Unit: virtual time
If max-opt-lookahead is set, a PE repeatedly computes GVT till
(LVT - GVT) > max-opt-lookahead.
Change-Id: I0f81b75628125e1fd2e71eddaa4116025c00a1c6

@laprej For some reason Travis didn't test this merge. Looking at the TravisCI settings, it appears we have "Build Pull Requests" off. I assume this wasn't an issue before because all of the PRs were from carothersc/ROSS branches (which are travis tested). I'm betting this issue should really be on. How, then, do we trigger a re-test of this PR?

@gonsie I don't know that we can this time -- I was unable to find any way to initiate the tests.  But I've toggled that setting to be on in the future.  In this case, the changes are small enough that we can probably just merge it see if it breaks anything?  Or possibly make a small change to the PR and see if that triggers the tests to run.

I think closing and re-opening should trigger it ... ??

Ping.

After some basic testing of this mechanism on phold and pcs, it seems to have be working just fine. There is no impact to simulations.
I'll create a blog post for this in the next few days.

Thanks Elsa!!
Chris
On Wed, Mar 1, 2017 at 12:28 PM, Elsa Gonsiorowski<EMAIL_ADDRESS>
wrote:

After some basic testing of this mechanism on phold and pcs, it seems to
have be working just fine. There is no impact to simulations.
I'll create a blog post for this in the next few days.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/carothersc/ROSS/pull/107#issuecomment-283409578, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA9Uk5c2RNxdA9NcI-fKDnJVR55IuWuJks5rhaqxgaJpZM4LOsP2
.

--
Christopher D. Carothers
Director, Center for Computational Innovations
Professor, Department of Computer Science
Rensselaer Polytechnic Institute
110 8th Street
Troy, New York 12180-3590
e-mail<EMAIL_ADDRESS>web page: www.cs.rpi.edu/~chrisc http://www.cs.rpi.edu/~chrisc
phone:<PHONE_NUMBER>
fax:<PHONE_NUMBER>


Safe place to get PxPlus IBM VGA8.

This page calls out that it's not included in Terminal, but wondering where we can get it.  I don't want to download some sketchy file and risk a virus or anything.  Do you know of any safe places to get the font?  Thanks.

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

ID: 432143ce-1eca-3975-b7cf-73deb57cc0e0
Version Independent ID: 8573964d-6f4c-c79d-9c54-cd75efd03ae7
Content: Windows Terminal Retro Command Prompt
Content Source: TerminalDocs/custom-terminal-gallery/retro-command-prompt.md
Product: dev-environment
Technology: windows-terminal
GitHub Login: @cinnamon-msft
Microsoft Alias: cinnamon

Thanks for the suggestion! This is actually already discussed in another issue on our repo - please refer to #70 for more discussion.
/dup #70


Hi @gaomd, i see that you fixed it.. I Plan make something great for that project.. But i dont have coding skills for it, i see that you fixed code fast.. For me main problem is to know if not smart devices like tv, windows blind, etc real state, if them are on or off.. The problem is if you use both tv remote and homekit.. Homekit doesnt know if state changed by tv remote..  I see on code to change that, just put setSwitchState to true or false.. I would like to aways listen ir receiver, once received determined ir HEX (like tv power remote), it will invert setSwitchState to true or false, so, it will aways be sync with homekit, i could with this use both remote tv and homekit.. This is valid for too many devices.. What you think? How dificult would be that?!

Hi @felipesalomao, it's really hard.
When learning remote codes, I got different codes from same remote button every time, we were managed to record the remote code then resend again, the device recognizes the code, but in reverse, it's impossible to tell which remote button was pressed, because it's different from the previously recorded one.
On the Broadlink side, the code learner must always in learning mode, would that be in conflict with code send action?
Even if these preconditions are met, we could tell the exact remote button pressed and we are always in leaning mode, Broadlink may receive the code sent by the remote, but it's unable to confirm the codes was received by the target device, leaving them in the unsynchronized state.
One way to manage this properly is to rewrite the plugin, incorporate it with a smart power plug which monitors the power usage,  combine them as a HomeKit switch, then the power state could be reflected in the Home app properly. But it only works for power state, other remote states are still hard to monitor.

Fixed during refactor - thanks for the PR though!


语音识别失败, On-device recognition is not supported for locale

The problem seems to be caused by the "hear" module, which is discussed at https://github.com/sveinbjornt/hear/issues/20. (I tried other time zones and languages, same problem) Switch to whisper can be a solution? Any ideas?

You might need to add support for us-en in your Mac settings. You could refer to the following instruction page:
https://support.apple.com/en-hk/HT208316

You might need to add support for us-en in your Mac settings. You could refer to the following instruction page: https://support.apple.com/en-hk/HT208316

Oh, The problem was the Region. Thanks!


[@material-ui] Bump @material-ui version

-Fixes issues with crashing on refs to makeStyles in @material-ui/styles
-Moves makeStyles ref from @material-ui/styles to @material-ui/core

These changes transition to the new makeStyles importing that references @material-ui/core instead of @material-ui/styles that is intended to reduce duplicate dependencies.
Details can be seen here: https://github.com/mui-org/material-ui/releases/tag/v4.5.1
The release notes makeStyles being imported from @material-ui/core/styles, but it can be imported directly from @material-ui/core with no downsides.


Determine which indices are needed for efficient execution of a query

What do you want to change?
Currently using SQL databases generally operate in the mode that every query is possible and they create an execution plan at runtime, based on data statistics and available indices. You have prepared statement you can use, but they are generally still done per-connection.
But in many cases, the set of queries one uses in apps is limited. sqlc is realizing that as well and takes an advantage to build client-side type-safe code to interface with SQL. In a way it compiles SQL into target code (e.g., Go) and abstracts SQL away.
I would like to suggest that sqlc could go a step further. During compilation time it could use data statistics to a) optimize the query itself b) create a SQL migration to add/remove indices to effectively execute those queries.
I know that doing this would be huge effort, but I think it is also very powerful. In this way I would bundle with a version of my app not just (compiled and optimized) queries, but also the set of indices (and data schema as well) those queries need for performant execution.
One approach to do this would be that during compilation time the sqlc would connect to a database with data, install hypothetical indices, and EXPLAIN all queries available (maybe a developer should provide test parameters), determine which indices are needed, and then create also a migration to install (or optionally remove) indices.
What database engines need to be changed?
PostgreSQL
What programming language backends need to be changed?
Go

There seems to exist something similar: https://github.com/ankane/dexter But it is not built-in into a compilation step.

@lyda An interesting proposal. In a way it makes sense, it is like the benchmarks you would have in a test suite where tests would fail if expected performance would get too low.
It would mean that developers would have to manually add indices and then during testing you could check:

Are there indices which are missing and do not exist.
Are there indices where are there but are not ever used.

This could also be something similar to "coverage" - do all your tests at the end cover the indices you have and are there indices they could over but are missing. So you would run whole test suite and check that (instead of having an explicit tests to validate indices - I worry that then calls you might be doing would be repeated with calls you do during regular tests).
Which brings me then to the final point:
This might best live outside of a particular program/test suite/sqlc. You have test cases to test your code (which can include running against a realistic dump of data). Then you:

Create database instance. Instrument it with extensions to store all queries made.
You run your test suite.
You check all queries - where there slow queries, where there queries which used scans, are there indices no query ever used.
You repeat, this time creating all possible hypothetical queries.
Now you check if any query would use any of the hypothetical queries.

Sqlc would then only have to support some hook to be able to give you information about the schema to create all the hypothetical queries. But one could probably find a way to parse schema from sql also without sqlc to figure that out.

Exactly.  sqlc will provide the Explain* functions but then it's up to you to run one or more of them in whatever environment you see fit.  I think the real win here is if we can parse the response to EXPLAIN and provide meaningful feedback to the developer.
I might try and do it for cockroachdb if I get some time.  Bank holiday coming up in a few weeks.

Note: This could even be run in production systems to track how certain statements are being optimised over time.


Styling of the info

I was looking through the issues whether there was something about styling the content generated by the add-on, but couldn't find any previous info.
I did see this post of @mnmtanish that showed a styled version of the info.
What would be the best and contained way of styling the add-on?

Related PR: https://github.com/storybooks/react-storybook-addon-info/pull/135
cc: @jbellsey


Add hashes for deployment ConfigMaps and Secrets to NodeSet

Add hashes for deployment ConfigMaps and Secrets to NodeSet
Update Secrets in kuttl test to match real values

recheck

recheck
baremetal job failing with:
TASK [osp.edpm.edpm_users : Ensure user is present on the host [ openvswitch ]] *** Monday 22 January 2024  23:02:34 +0000 (0:00:01.967)       0:00:05.960 ********  fatal: [edpm-compute-0]: FAILED! => {"changed": false, "msg": "usermod: user openvswitch is currently used by process 1192\n", "name": "openvswitch", "rc": 8}
should be fixed by https://github.com/openstack-k8s-operators/edpm-ansible/pull/540/

/retest
error: build error: Failed to push image: trying to reuse blob sha256:07a64a71e01156f8f99039bc246149925c6d1480d3957de78510bbec6ec68f7a at destination: pinging container registry quay.rdoproject.org: Get "https://quay.rdoproject.org/v2/": net/http: TLS handshake timeout

recheck
"https://api.crc.testing:6443/api?timeout=32s\\\": dial tcp <IP_ADDRESS>:6443: connect: connection refused\\nThe connection to the server api.crc.testing:6443 was refused -

recheck

Last rdo failure was:
{"msg": "'ctlplane_subnet_cidr' is undefined. 'ctlplane_subnet_cidr' is undefined"}
so perhaps there is a misconfiguration somewhere.

recheck
looks like it just took too long
timed out at 15:33:06:
2024-01-23 15:33:06.146270 | controller | fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["oc", "wait", "--timeout=30m", "--for=condition=Ready", "openstackdataplanenodeset", "openstack-edpm-ipam", "-n", "openstack"], "delta": "0:30:00.143601", "end": "2024-01-23 15:33:06.113730", "msg": "non-zero return code", "rc": 1, "start": "2024-01-23 15:03:05.970129", "stderr": "error: timed out waiting for the condition on openstackdataplanenodesets/openstack-edpm-ipam", "stderr_lines": ["error: timed out waiting for the condition on openstackdataplanenodesets/openstack-edpm-ipam"], "stdout": "", "stdout_lines": []}
but by 20:33:50Z the NodeSet was ready:
    - lastTransitionTime: "2024-01-23T20:33:50Z"       message: Deployment completed       reason: Ready       status: "True"       type: Deployment ready for NodeSet

recheck
putting node onhold for troubleshooting

recheck
(putting node onhold for troubleshooting)

recheck


Multiple assets emit different content to the same filename css/common.css

Bug report

What is the current behavior?
development mode , only modify css file trigger webpack hot reload, will follow error:
<e> [webpack-dev-middleware] assets by status 40.6 KiB [cached] 1 asset
<e> assets by info 4.22 KiB [hmr]
<e>   assets by chunk 3.3 KiB (name: common)
<e>     asset css/common.css 1.8 KiB [emitted] [hmr] (name: common) (id hint: styles, vendors)
<e>     asset common.3dda70a80101f291712e.hot-update.js 1.5 KiB [emitted] [immutable] [hmr] (name: common) (id hint: styles, vendors)
<e>   asset runtime.3dda70a80101f291712e.hot-update.js 902 bytes [emitted] [immutable] [hmr] (name: runtime)
<e>   asset 3dda70a80101f291712e.hot-update.json 40 bytes [emitted] [immutable] [hmr]
<e> assets by path js/ 3.64 MiB
<e>   asset js/common.js 3.6 MiB [emitted] (name: common) (id hint: styles, vendors)
<e>   asset js/runtime.js 42.3 KiB [emitted] (name: runtime)
<e>
<e> ERROR in Conflict: Multiple assets emit different content to the same filename css/common.css
<e>
<e> webpack 5.0.0-beta.32 compiled with 1 error in 303 ms

If the current behavior is a bug, please provide the steps to reproduce.
- git clone git@github.com:easy-team/awesome.git
- git checkout webpack5
- cd boilerplate/react
- yarn
- npm run dev

The demo can run depends on another issue(https://github.com/webpack-contrib/mini-css-extract-plugin/pull/590 ) to be resolved and merged for release.
Modify src/router/component/home.css  file, trigger webpack hot reload, will above error.   If only modify javascript file , can works.

What is the expected behavior?

Other relevant information:
webpack version:  webpack 5.0.0-beta.32
Node.js version:  v12.14.0
Operating System:  Mac
Additional tools:

Please do not duplicate issues, it is traced in mini-css-extract-plugin repo https://github.com/webpack-contrib/mini-css-extract-plugin/issues/487


(re)Spec and implement command set

In the original spec, the committee elected to aim for explicit commands and an entirely CLI-driven UI for dep. However, after some discussion and getting our hands dirty, we decided (https://github.com/golang/dep/issues/213#issuecomment-278831924) to change course and focus instead on a workflow that presumes hand-edited manifest files and a more minimal command set.
This meta-issue is to track the writing of a new spec (WIP here), and then implementing it.
While we of course expect these commands will continue to evolve in the future, this issue specifically aims to track implementation with the goal of having a command set that could reasonably be merged directly into the go toolchain. Basic completeness per the spec (not bug free-ness), is the rubric for completion of this issue.
Related/sub-issues:

[ ] #186 - alternate init modes
[ ] #145 - no-op on ensure should actually be no-op
[ ] #161 - dep status, memo

With regards to this WIP flag for init
-no-tools: skip searching for metadata files from legacy tools
Shouldn't the default be to skip and the flag to actually search for legacy tools ?
Eventually there will be no legacy and you'd still need to pass the flag.

@jbrodriguez i was gonna say that that seems like a good comment to make in the doc...then realized i had comments disabled 😛
It shouldn't be necessary to pass -no-tools, even if there's no tool metadata available. It should fall through just fine on its own. Might be better if the flag is -skip-tools, though; I've updated accordingly.

I made considerable progress on the WIP spec last night; a new approach to dep ensure is now at least mostly sketched out. It's certainly in a place where folks could start iterating on it, though we'll doubtless need to take it over the course of a few PRs. I'd prefer to avoid it, but we could also use a long-running feature branch if need be.

This issue is linked on the Roadmap page as "Stable command set" but doesn't have a strike-through like "Stable manifest and lock files". Is this considered closed? If so, is there some way to edit that page (e.g. via a pull request)?


Adjust create_and_populate_list.py and googleads_yaml.config to account for latest Google Ads API changes

Modified create_and_populate_list.py to use enums where string / int values where no longer accepted, along with extending instead of assigning OfflineUserDataJob operations.
This change also includes adding the use_proto_plus: False configuration key-value pair, as the API has been changed to support proto-plus messaging by default, which is discouraged for performance-sensitive jobs such as customer match uploads (source: https://developers.google.com/google-ads/api/docs/client-libs/python/protobuf-messages#use_cases_for_proto-plus_and_protobuf_messages).

Fixes #1