METRON-1465:Support for Elasticsearch X-pack

Contributor Comments
This commit supports x-pack enabled and vanilla elasticsearch clusters. As there is no known way to create a x-pack enabled test node for the integration test, authentication cannot be verified during integration tests.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[ ] Have you included steps or a guide to how the change may be verified and tested manually?

[ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[ ] Have you written or updated unit tests and or integration tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

Should we consider a dual client in the same project similar to the approach in https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-5-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearch5TransportClientProcessor.java ?
We can then switch based on the presence of the es.xpack.user setting in the ambari.

@simonellistonball It looks like they are not explicitly bundling the X-Pack client. Rather, they're expecting the user to provide the jar file manually on the classpath and then dynamically instantiating with reflection. That would seem to solve our license issues.
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-5-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearch5TransportClientProcessor.java#L71
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-5-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearch5TransportClientProcessor.java#L225

@mmiklavc  I agree, as long as the user themselves is setting it up, I believe that would solve the license problem.  At least from my understanding of things.

@mmiklavc Yeah, I think that's the approach, however, there's a snag.  Storm requires us to create uber jars, so probably what we want to do is have users actually put the xpath transport client on the storm.library.path.

We could probably leverage this guy here

ah, crap, looked at the wrong setting.  That's what I meant instead of storm.library.path

I knew what you meant :)

Steps to test:

build centos vagrant dev build box
vagrant ssh
sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install x-pack
sudo /usr/share/elasticsearch/bin/x-pack/users useradd transport_client_user -p changeme -r superuser
restart ES via ambari
verify 401 status: curl http://localhost:9200
verify new documents are indexed in ES: http://node1:9200/_cat/indices?v

@wardbekker Did you test this with Kibana by chance? I'm seeing authentication exceptions in the Kibana UI. Looks like we need additional steps for it to work - https://www.elastic.co/guide/en/kibana/5.6/installing-xpack-kb.html

@mmiklavc yes, correct, like with ES you need to install x-pack for Kibana. You will be prompted for username password after restart of Kibana.

wait, does this PR mean we require x-pack from now on?

@ottobackwards in it's current state, sort of, but you're not required to turn it on. In the desired (reflection based nifi style state) no, it should load it and use it if present, but otherwise just use the vanilla transport client. Of course someday they're going to force us to REST, which will bring all this up again no doubt.

would this have any effect on people using x-pack alternatives?

@cestella " Yeah, I think that's the approach, however, there's a snag. Storm requires us to create uber jars, so probably what we want to do is have users actually put the xpath transport client on the storm.library.path."  If only there was a way to load things into storm with classloader isolation and dependency inclusion.....

@ottobackwards - I have some open changes in a PR against this PR. Just to confirm, the expected result of this PR should be that users can choose

Which client they want to instantiate
Whether they want X-Pack enabled or not

The default ootb functionality should be the same as what we currently do. X-Pack is a special case.

thanks @mmiklavc

@wardbekker I have a PR against your PR. Can you please review when you have a moment?

@mmiklavc great stuff. merged!

Now that I've participated/contributed to the PR, I must recuse myself voting. Would appreciate other feedback or requests for change for @wardbekker.

Shout out to @basvdl for helping with testing the REST api fixes

@wardbekker and @basvdl nice additions on the REST api!

Thanks for the updates @wardbekker. Pending Travis, I'm +1 by inspection on the recent changes. Look ok to you @nickwallen?

The CI build failed here due to what has been fixed in #977.  If we can get #977 reviewed and in, this should no longer be a problem.

+1 by inspection, pending a clean CI build.


Add community info and purpose info to the README

/ok-to-test
/approve (after fixing rob's comments)

/lgtm


ensure yml files use LF for EOL

references: https://stackoverflow.com/a/10855862/10548020, https://docs.github.com/en/github/using-git/configuring-git-to-handle-line-endings

let me try this again :(


Error in version 0.1.0 (typst/packages)

https://github.com/tingerrr/anti-matter/blob/ebdf1a8207cd4c256775b1e279fe35febc5ad4bb/src/lib.typ#L18
Above line is from this repo (tingerrr/anti-mater)
Below line is from typst/packages
https://github.com/typst/packages/blob/3e450dcd3dcf23e74b10b3e557acb223928ce308/packages/preview/anti-matter/0.1.0/src/lib.typ#L18
Maybe a small update that doesn't increment semver to fix?

Yeah, that happens when you rewrite the package while being tired, I've lined up a fix already here: packages#268.

Fixed in v0.1.1.


Support for Multiple Keyboards & Mice

This request asks for a way to distinguish the sources for Mouse & Keyboard input (similar to how Joysticks currently are distinguished). Such distinction would allow for multiple persons to work on the same physical computer, each with their own set of mouse & keyboard.
This would (inter alia) allow for the following things:

multi-seat support for same-computer coop games
multi-user collaboration tools to be run on one physical machine

A project which can possibly be used to add this and further functionality regarding input:

http://www.signal11.us/oss/hidapi/
HIDAPI is a multi-platform library which allows an application to interface with USB and Bluetooth HID-Class devices on Windows, Linux, and Mac OS X. While it can be used to communicate with standard HID devices like keyboards, mice, and Joysticks, it is most useful when used with custom (Vendor-Defined) HID devices. Many devices do this in order to not require a custom driver to be written for each platform. HIDAPI is easy to integrate with the client application, just requiring a single source file to be dropped into the application.

Regarding HIAPI: Windows doesn't allow polling hid mice and keyboards for security reasons AFAIK. Raw input can also handle multiple devices though

no updates? :/

I just googled this and ended up here.
Please support this!

I have been working on an implementation of this feature in my fork: https://github.com/hnOsmium0001/glfw/tree/multikeyboard
Events for connecting/disconnecting keyboards, as well as fetching which keyboard generated the key event is implemented. However due to the need to use different APIs (RawInput and XInput2 for win32 and X11 respectively), the keycode reporting behavior for keys such as Pause, Ctrl+Pause, and ScrollLock are still buggy.
Currently it's written for my own project, I may submit a PR if I ever end up making it complete & bug-free enough. The list of problems:
(I don't have a machine that runs macOS or wayland to test them yet)

[x] win32 keyboards
[ ] win32 mice
[ ] macOS keyboard
[ ] macOS mice
[x] X11
[ ] X11 mice
[ ] Wayland keyboards
[ ] Wayland mice
[ ] Better API
In order to not break existing code, I decided to add keyboard that generated a key event as a global variable, fetched by calling glfwGetLastActiveKeyboard() in GLFWkeyfun. I will definitely switch to a better solution if I find one.

I have been working on an implementation of this feature in my fork: https://github.com/hnOsmium0001/glfw/tree/multikeyboard

Hi. What is its status? Is it complete? Did you ever submit this?

Potentially an easier way to handle keyboard events on Linux would be through evdev, though you'd have to manually figure out which devices are keyboards.


Fix input history down button

This PR closes #316. It disables the looping around down button after the last input history.
Test plan
I tested it manually.
To test, start the extension and press the Down Button. After it reaches the end, it won't loop around the first history input.

@philipp-spiess @vdavid Can I have a review, please?


CookieMatcher throws ArrayIndexOutOfBoundsException

From<EMAIL_ADDRESS>on February 10, 2012 16:54:38
What steps will reproduce the problem? 1. When the server returns a cookie with no value, which is common when deleting cookies, CookieMatcher.grovy throws ArrayIndexOutOfBoundsException. (GroovyMatcher.groovy, line 55)
What is the expected output?
One of (may require discussion):
a) simply not include the cookie in the returned map
b) include the cookie, with an empty string value
What do you see instead?
ArrayIndexOutOfBoundsException What version of the product are you using? On what operating system? 1.5 on Linux Please provide any additional information below.
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=158

From<EMAIL_ADDRESS>on February 11, 2012 03:30:12
It may have been resolved in trunk already (thanks to the changes made in issue #159 ). Could you please try it out by depending on 1.6-SNAPHOT using the following repo:
<repositories>
<repository>
<id>sonatype
<url> https://oss.sonatype.org/content/repositories/snapshots/ <snapshots />
</repository>
</repositories>
If not, can you give me an example of how the cookie sent from the server looks like?
Status: Accepted

From<EMAIL_ADDRESS>on February 11, 2012 03:33:07
Status: New

From<EMAIL_ADDRESS>on February 14, 2012 07:46:21
Yes, the issues appears fixed in 1.6-SNAPSHOT. Thank you.
Do you have an ETA for an official release with the fix?

From<EMAIL_ADDRESS>on February 15, 2012 06:17:32
Thanks for verifying.
I can't make any promises but I struggle to have it released "soon". I think most features are included now but I need to update the documentation, release notes and stuff.
Status: Duplicate
Mergedinto: 159


Pipenv fails badly when installing with --deploy with an outdated lockfile.

Issue description
When installing using "--deploy" with an outdated Pipfile, Pipenv fails with an exception.
Expected result
Pipenv should notify the lockfile is outdated and exit gracefully.
Actual result
Your Pipfile.lock (ee5679) is out of date. Expected: (c5ad03).
Traceback (most recent call last):
  File "/usr/local/bin/pipenv", line 8, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.8/site-packages/pipenv/vendor/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/pipenv/vendor/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.8/site-packages/pipenv/vendor/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/pipenv/vendor/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.8/site-packages/pipenv/vendor/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/pipenv/vendor/click/decorators.py", line 64, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/pipenv/vendor/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/pipenv/vendor/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/pipenv/cli/command.py", line 235, in install
    retcode = do_install(
  File "/usr/local/lib/python3.8/site-packages/pipenv/core.py", line 1863, in do_install
    do_init(
  File "/usr/local/lib/python3.8/site-packages/pipenv/core.py", line 1192, in do_init
    raise exceptions.DeployException
  File "/usr/local/lib/python3.8/site-packages/pipenv/exceptions.py", line 168, in __init__
    PipenvUsageError.__init__(message=fix_utf8(message), extra=extra, **kwargs)
TypeError: __init__() missing 1 required positional argument: 'self'

Steps to replicate

pipenv --three
edit Pipfile and add a dependency. Ex: pycodestyle = "==2.4.0"
pipenv lock
edit Pipfile:  Ex: pycodestyle = "==2.5.0"
pipenv install --deploy

Please run $ pipenv --support, and paste the results here. Don't put backticks (`) around it! The output already contains Markdown formatting.
$ pipenv --support
Pipenv version: '2018.11.26'
Pipenv location: '/usr/local/lib/python3.8/site-packages/pipenv'
Python location: '/usr/local/bin/python'
Python installations found:

3.8.0: /usr/local/bin/python
3.7.3: /usr/bin/python3.7
3.7.3: /usr/bin/python3.7m
2.7.16: /usr/bin/python

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.8.0',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '5.2.21-1-MANJARO',
 'platform_system': 'Linux',
 'platform_version': '#1 SMP PREEMPT Sat Oct 12 11:09:56 UTC 2019',
 'python_full_version': '3.8.0',
 'python_version': '3.8',
 'sys_platform': 'linux'}

System environment variables:

HOSTNAME
PYTHON_PIP_VERSION
HOME
GPG_KEY
PYTHON_GET_PIP_URL
PATH
LANG
PYTHON_VERSION
PWD
PYTHON_GET_PIP_SHA256
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG: C.UTF-8
PWD: /

Contents of Pipfile ('/Pipfile'):
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[dev-packages]

[packages]
pycodestyle = "==2.5.0"

[requires]
python_version = "3.8"

Contents of Pipfile.lock ('/Pipfile.lock'):
{
    "_meta": {
        "hash": {
            "sha256": "ec2f93366a5196a3e49f40dd0b76f7163aa82c379ea6bc56a6687d3ef1ee5679"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.8"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "pycodestyle": {
            "hashes": [
                "sha256:cbc619d09254895b0d12c2c691e237b2e91e9b2ecf5e84c26b35400f93dcfb83",
                "sha256:cbfca99bd594a10f674d0cd97a3d802a1fdef635d4361e1a2658de47ed261e3a"
            ],
            "index": "pypi",
            "version": "==2.4.0"
        }
    },
    "develop": {}
}

Duplicate of https://github.com/pypa/pipenv/issues/3560 and is likely fixed in master.

Duplicate of #3560 and is likely fixed in master.

Gread. But not released, yet? I see the same error in pipenv-2018.11.2
Hope https://github.com/pypa/pipenv/issues/3369 is coming, soon.


Uint16 not supported in clickhouse plugin

Describe the issue
Hi , im getting this error while using the clickhouse jdbc query :
Data of type 'class com.clickhouse.data.value.UnsignedShort' for column 'source_id' is not supported
the column is Uint16
Environment

Kestra Version: develop

Hello, can you share a full flow and data sample please ?

- id: query_clickhouse     type: io.kestra.plugin.jdbc.clickhouse.Query     url: jdbc:clickhouse://host/     username:      password:      sql: select * from pikastream.outlet_products limit 2     fetch: true


Clean up error position handling in go-runtime/schema

Currently the position is added as a prefix to the error willy nilly, often ending up with multiple positions stacked in the message. Introduce a custom error type that includes a position, and wrapping function that only adds a position if there isn't already one.

Going to take this one as it's super annoying.


[IZPACK-1241] Builds using custom packaging type izpack-jar sometimes fail after fresh IzPack snapshot deployments

This affects https://jira.codehaus.org/browse/IZPACK-1241:
Mostly a short time after fresh IzPack snapshot deployments I've noticed build failures when using the special packaing type {{izpack-jar}} in the POM.
There are appearing errors like this:
10:04:58 [ERROR] Failed to execute goal org.codehaus.izpack:izpack-maven-plugin:5.0.0-rc5-SNAPSHOT:izpack (default-izpack) on project my-app: Execution default-izpack of goal org.codehaus.izpack:izpack-maven-plugin:5.0.0-rc5-SNAPSHOT:izpack failed: A required class was missing while executing org.codehaus.izpack:izpack-maven-plugin:5.0.0-rc5-SNAPSHOT:izpack: com/izforge/izpack/api/data/Info
10:04:58 [ERROR] -----------------------------------------------------
10:04:58 [ERROR] realm =    plugin>org.codehaus.izpack:izpack-maven-plugin:5.0.0-rc5-SNAPSHOT
10:04:58 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
10:04:58 [ERROR] urls[0] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-maven-plugin/5.0.0-rc5-SNAPSHOT/izpack-maven-plugin-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[1] = file:/var/lib/hudson-slave/maven-repositories/0/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
10:04:58 [ERROR] urls[2] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar
10:04:58 [ERROR] urls[3] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
10:04:58 [ERROR] urls[4] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-compiler/5.0.0-rc5-SNAPSHOT/izpack-compiler-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[5] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-native/5.0.0-rc5-SNAPSHOT/izpack-native-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[6] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-panel/5.0.0-rc5-SNAPSHOT/izpack-panel-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[7] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-util/5.0.0-rc5-SNAPSHOT/izpack-util-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[8] = file:/var/lib/hudson-slave/maven-repositories/0/org/jdom/jdom2/2.0.5/jdom2-2.0.5.jar
10:04:58 [ERROR] urls[9] = file:/var/lib/hudson-slave/maven-repositories/0/org/apache/maven/shared/maven-shared-jar/1.1/maven-shared-jar-1.1.jar
10:04:58 [ERROR] urls[10] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/plexus/plexus-digest/1.0/plexus-digest-1.0.jar
10:04:58 [ERROR] urls[11] = file:/var/lib/hudson-slave/maven-repositories/0/org/apache/bcel/bcel/5.2/bcel-5.2.jar
10:04:58 [ERROR] urls[12] = file:/var/lib/hudson-slave/maven-repositories/0/jakarta-regexp/jakarta-regexp/1.4/jakarta-regexp-1.4.jar
10:04:58 [ERROR] urls[13] = file:/var/lib/hudson-slave/maven-repositories/0/commons-collections/commons-collections/3.1/commons-collections-3.1.jar
10:04:58 [ERROR] urls[14] = file:/var/lib/hudson-slave/maven-repositories/0/org/picocontainer/picocontainer/2.14.1/picocontainer-2.14.1.jar
10:04:58 [ERROR] urls[15] = file:/var/lib/hudson-slave/maven-repositories/0/commons-lang/commons-lang/2.6/commons-lang-2.6.jar
10:04:58 [ERROR] urls[16] = file:/var/lib/hudson-slave/maven-repositories/0/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
10:04:58 [ERROR] urls[17] = file:/var/lib/hudson-slave/maven-repositories/0/org/apache/commons/commons-compress/1.3/commons-compress-1.3.jar
10:04:58 [ERROR] urls[18] = file:/var/lib/hudson-slave/maven-repositories/0/jline/jline/2.12/jline-2.12.jar
10:04:58 [ERROR] urls[19] = file:/var/lib/hudson-slave/maven-repositories/0/xpp3/xpp3/1.1.4c/xpp3-1.1.4c.jar
10:04:58 [ERROR] urls[20] = file:/var/lib/hudson-slave/maven-repositories/0/org/java/net/substance/substance/6.0/substance-6.0.jar
10:04:58 [ERROR] urls[21] = file:/var/lib/hudson-slave/maven-repositories/0/org/pushing-pixels/trident/1.2/trident-1.2.jar
10:04:58 [ERROR] urls[22] = file:/var/lib/hudson-slave/maven-repositories/0/org/eclipse/swt/win32/win32/x86/3.3.0-v3346/x86-3.3.0-v3346.jar
10:04:58 [ERROR] urls[23] = file:/var/lib/hudson-slave/maven-repositories/0/net/java/dev/laf-widget/laf-widget/5.0/laf-widget-5.0.jar
10:04:58 [ERROR] urls[24] = file:/var/lib/hudson-slave/maven-repositories/0/asm/asm-all/2.2.3/asm-all-2.2.3.jar
10:04:58 [ERROR] urls[25] = file:/var/lib/hudson-slave/maven-repositories/0/net/java/dev/laf-plugin/laf-plugin/1.1/laf-plugin-1.1.jar
10:04:58 [ERROR] urls[26] = file:/var/lib/hudson-slave/maven-repositories/0/be/cyberelf/nanoxml/lite/2.2.3/lite-2.2.3.jar
10:04:58 [ERROR] urls[27] = file:/var/lib/hudson-slave/maven-repositories/0/com/incors/kunstoff-laf/2.0.2/kunstoff-laf-2.0.2.jar
10:04:58 [ERROR] urls[28] = file:/var/lib/hudson-slave/maven-repositories/0/com/jgoodies/looks/2.2.2/looks-2.2.2.jar
10:04:58 [ERROR] urls[29] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-core/5.0.0-rc5-SNAPSHOT/izpack-core-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[30] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-tools/5.0.0-rc5-SNAPSHOT/izpack-tools-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[31] = file:/var/lib/hudson-slave/maven-repositories/0/org/apache/ant/ant/1.9.4/ant-1.9.4.jar
10:04:58 [ERROR] urls[32] = file:/var/lib/hudson-slave/maven-repositories/0/org/apache/ant/ant-launcher/1.9.4/ant-launcher-1.9.4.jar
10:04:58 [ERROR] urls[33] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-uninstaller/5.0.0-rc5-SNAPSHOT/izpack-uninstaller-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[34] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-gui/5.0.0-rc5-SNAPSHOT/izpack-gui-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[35] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-installer/5.0.0-rc5-SNAPSHOT/izpack-installer-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[36] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-event/5.0.0-rc5-SNAPSHOT/izpack-event-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[37] = file:/var/lib/hudson-slave/maven-repositories/0/org/codehaus/izpack/izpack-api/5.0.0-rc5-SNAPSHOT/izpack-api-5.0.0-rc5-SNAPSHOT.jar
10:04:58 [ERROR] urls[38] = file:/var/lib/hudson-slave/maven-repositories/0/commons-io/commons-io/2.4/commons-io-2.4.jar
10:04:58 [ERROR] Number of foreign imports: 1
10:04:58 [ERROR] import: Entry[import  from realm ClassRealm[project>com.mycompany:my-app:01.02.00-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
10:04:58 [ERROR]
10:04:58 [ERROR] -----------------------------------------------------: com.izforge.izpack.api.data.Info
10:04:58 [ERROR] -> [Help 1]
10:04:58 [ERROR]
10:04:58 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
10:04:58 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
10:04:58 [ERROR]
10:04:58 [ERROR] For more information about the errors and possible solutions, please read the following articles:
10:04:58 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
10:04:58 [ERROR]

This happens on CI buildsystems like Hudson and during local builds accessing a repository manager as well.

IzPack project » izpack #753 SUCCESS
This pull request looks good
(what's this?)


Make the navbar stick through the scroll through the landing page and improve styling

The current navbar does not remain fixed when scrolling through the landing page, which can make navigation challenging for users. Implementing a sticky or fixed navbar will enhance user experience by keeping the navigation options accessible at all times, allowing users to easily access different sections of the page without needing to scroll back to the top. This improvement will help in maintaining a seamless browsing experience and improve overall usability.

work is being done on that


New Website Logo: DIMDATA

Hi TypeScript

Name: DIMDATA
Homepage url: https://www.dimdata.com
Brand Guidelines/Licensing: https://www.dimdata.com/terms.html
Logo: https://www.dimdata.com/logo_l1.zip

Thanks

Any updates?

We do them in patches. should be in the website when we do the next update.

Thanks @mhegazy
Can i request to update the logo?
New logo with fixed: https://www.dimdata.com/logo_t_m.png


[Almayer] Medical needs power and crematoriums

Description
For the past playtests, admins have been giving medical power and crematoriums every round. This should be default if possible.
Also, pretty much all vends/disposal units do not have power.

its on the second deck of the almayer https://webmap.affectedarc07.co.uk/maps/cm/almayer/


Fix possible dll conflict on windows

Following a user bug report (support ticket 2649), this fix guarantees that we use the correct version of libssl on Windows.

👍


Add/environment token and documentation of functions

This PR will address #30 by giving the user the option to export an environment variable instead of (or in addition to, overwriting) the default $HOME/kaggle/kaggle.json, closing #30. I'm not sure any testing / CI is in place, and I'd like to offer to start writing tests and add to test this PR, @rysteboe if you want to discuss where you would like them (and connect the webhook!) - See https://github.com/Kaggle/kaggle-api/issues/58u. In addition, the PR contains the following changes:
Commenting
I added a lot of comments, and adjusted the spacing to be 4. This obviously has no
functional change, but is mostly for programming dinosaurs like me that need
a little more verbosity and space to better read the code.
Environment Loading
This is the main reason for the PR (initially) and it will close #30.
There was an issue to load configuration values from the environment, so this
is now done, with first read (and second preference) going to a config file, and
then to the environment (first preference since it overrides the config).
This would mean that a user doesn't need to have a
config file, but if there is no config or environment, we of course exit with error
(the username/password is minimally required!). It also means that if a user wants
to temporarily tweak something (but not change the config file) the environment
export will take preference, and this is easy to do. For the variable names,
I decided to have them be the same as the client defaults (e.g., if
self.CONFIG_NAME_USER == "user" then the environment variable would be the
uppercase of that prefixed with KAGGLE_ --> export KAGGLE_USER=potatoman. The prefix
KAGGLE_ is added simply to maintain a separate namespace, and all caps is just
a convention.
Consolidated Functions
I noticed some operations that were done a few times, and consolidated to new
functions, and this is useful so if we make a change to the operation, we only
need to do it in one place!
Print Results
The first is for printing. Instead of having this repeated in the function
to list files, competitions, submissions:
        if listing:
            if csv_display:
                self.print_csv(listing, fields)
            else:
                self.print_table(listing, fields)
        else:
            print('No %s found' % name)

It's called as a function, for example:
self.print_result(files, fields, 'files', csv_display)

Get Competition (or Exit)
The second thing that was done a few times was checking if a competition came in
as None, if it didn't getting it from the config, and then exiting if it still wasn't
defined. That's now called like this:
competition = self._competition_get_or_exit(competition)

Download Path
This was another operation done a few times, reduced to a function that is shared.
effective_path = _get_download_path(path, competition)

Prepare Dataset Request
the function to create a dataset and create a dataset version had a lot of overlap, so there is a new function for that:
request= _dataset_prepare_create_request(folder)

Questions
I have a few more questions I'd like to discuss with the developer team, some ideas, and
some of these "I want to double check to make sure I didn't break something :) "

Testing! omg, we need testing. There is no way this is perfect and ready to go!
What's the difference between the kaggle_api.py and kaggle_api_extended.py?  The first looks like it was generated by swagger? I've used that in the past and usually wound up having preference for not using the auto-generation tool, but I'm not sure if we are using it here.
For the config copying, for the function that removed a config value, it set it to None instead of just using del on the dictionary. I wrote this function to use del instead (so the key is no longer in the dictionary). Will this muck something up?
Should we add a logger proper, instead of using if quiet==True? We could then add different levels of logging. I can offer to do this.
maybe the setup.py and client version string can come from the same place?
Is there any reason to put all the functions in one file? I definitely like the realization that we don't need to do extra imports, but I'm not sure if there is another way to organize so it's easier to find things (I added comment headers to help).

Looking forward to discussion! @rysteboe I know you were on vacation so definitely no rush to look here! I'll take a look at some of the other issues and see if they are easy to grab, and when you get a chance and we can discuss, I can definitely start on some tests (but I suspect we will need either to put an encrypted token in the CI environment or have a dummy one with limited permissions just for it)

@rysteboe I'm just seeing you self assigned a lot of the other issues - let me know if I can help :)

I think this is a decently substantial change so you should move out #30 to another PR and have this PR block that.
Also, please don't use sys.exit, raise some sort of error unless that's necessary for the CLI. Sometimes I'm not submitting but I have the import and the program exits.
I think this is taking care of some of that concern:
+        # Step 3: load into configuration!
-	+        self._load_config(config_data)

The refactoring breaks the functions into a more modular flow, so i#30 is sort of dependent on it. It would be very artificial to try and separate them at this point. I'd like to suggest that we instead write complete tests here and review the PR fully, because (I think?) the changes are pretty clean!

Yeah it's just a pain that's it's such a large change but some unit testing should solve that.

The majority of sys.exit with a message commands were not mine - they were previously in the code. All of the sys,exit that I added are sys.exit(1). I think raising an error is appropriate if the intended audience (the people to receive it) are developers. In this case (with the client) the audience won't find it meaningful, they will just see an ugly print to the command line.  Thus for these cases it's appropriate to exit with an error code, and also provide a meaningful message to the user. If it's the case that you've had it exit without a meaningful message, then perhaps this is something we should address?

And @exp0nge I did see that issue, and I think making the config file optional should fix it up! But yes we need tests, haha, Maybe I can start writing something locally even if we don't have it set up on Travis or Circle.

Sorry that was unrelated to this PR but we can fix it here anyway which
would address #51.
I strongly believe we should not be exiting a script at least until the
call to submit is made. If logging gets implemented then we can do warning
in the initialization.
On Fri, Jun 22, 2018, 3:58 PM Vanessa Sochat<EMAIL_ADDRESS>wrote:

And @exp0nge https://github.com/exp0nge I did see that issue, and I
think making the config file optional should fix it up! But yes we need
tests, haha, Maybe I can start writing something locally even if we don't
have it set up on Travis or Circle.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Kaggle/kaggle-api/pull/57#issuecomment-399564806, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALM_rUfwpc9GD7wHCka9HMdov5AEiyl4ks5t_UxQgaJpZM4U0U8U
.

Couple of initial comments:

2 space tabs were deliberate due to internal Google style guides.  However, I'm looking now and apparently there are a couple of differences between our public and private styles (sigh) and one of those is indentation.  So yeah, let's switch this over, but in a different PR to make it easier to evaluate the functional changes.
I just merged in https://github.com/Kaggle/kaggle-api/pull/56, which has some overlap.  (Note - I haven't looked at the code very much in this PR yet.)
Tests are a huge priority for me, and will come post kernels integration (soon TM).  One part of them will be sanity tests for the Kaggle backend (this will be worked on first), but more granular tests that also validate the API logic would also be useful.
sys.exit() calls are bad and will be going away soon.  They're included my WIP 1.4.0 version and will be replaced with raise ValueError (or whatever the best error is for the situation).  The CLI layer will catch API errors (there's a specific class that I don't remember the name of, maybe just ApiError?  It's defined by Swagger) and ValueError's and just print those messages.  Other errors I'm leaving uncaught at that layer for now and will adjust as needed.
Proper logging is also something that I have a bug to do but it's not super high on my list since most people aren't using the API programatically right now.  It's definitely important for enabling people to make that step, though.
The other big thing that I'm working on right now (along with kernels integration) is documentation.  This is going to be focused on the endpoints, but it will also include docstrings within the API code.  You're more than welcome to keep the documentation here, but it will likely be revised soon.  (Additional note - this change will include more defined classes within KaggleSwagger.yamlfor responses rather than dynamically generating them in kaggle_models_extended.py.  This is to allow for Swagger's documentation generator to give more useful information, as well as to make it way more clear to people who aren't me and can't see the definitions of what we're sending back what you're actually getting.)

really hope this gets in, I'd like to use this package to load kaggle datasets into sagemaker

+1!

Yeah sorry, finally circling back around to this after the madness that has been kernels.
Updates:

Style overall was updated (though not in the generated classes).  It matches the Google open source Python style, rather than PEP-8.  Previously, I was using our internal formatting tools.  The open source guidelines do have the four space tabs.
Due to other priorities within Kaggle, I will not be jumping straight to tests as I had hoped.  I'll be slowly working on that, but it's not going to be an immediate thing.
sys.exit() calls are gone
The documentation changes that I was hoping to make wound up being too extensive by necessity, and would have broken anyone using the API from a non-CLI context.  The endpoints are all better documented, but the return values are rather less so.
Logging is something that is needed, but is a lower priority on my end than tests.  That said, it's an easier problem for someone external to Kaggle to tackle than the tests would be.

My request for this PR would be to rework it with the updated formatting.  I would also suggest breaking out the consolidated functions to a separate PR that could get merged in quickly.  I like the idea behind the PR, but the diff right now is crazy because of the sheer level of changes that went in with 1.4.0.

I am traveling but will try to take a look when I get back! Thanks for your hard work on this, and much apology that the changes I did were too many. I'll do my best to see what I can do to get the feature in.


Any example?

Do you have any examples or documentation of how to work with the voyager-frontend?

Hi @bonzinho
All the documentation is in the README https://github.com/pvtl/voyager-frontend
It's not going to be perfect - so love to receive any PRs to improve.


feat: landing page

:tada: This PR is included in version 1.48.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


recorders module loading issue

getting below error even I have installed sox:
Error: No such recorder found: sox
recorder module path is getting wrong on below line:
https://github.com/gillesdemey/node-record-lpcm16/blob/9f27f0985e3c4c045c382f3697b49211e4403dad/recorders/index.js#L5
fix:
const recoderPath = path.resolve(__dirname, recorderName)

Thanks for reporting! Fixed in https://github.com/gillesdemey/node-record-lpcm16/commit/69be9ba2245eda74fbfa742e882921a0dc8e51f3 and released as v1.0.1


Add option to confirm close tab on close button clicks

Description of the new feature/enhancement

Running on a 4k screen with lots of tabs open, and it gets crowded. But the same can be easily reproduced by having a tab title that's very short like 2 characters. When you try to activate a tab, you inadvertently click the close button. And that it's it, game over. Doesn't matter what you were running inside, it's gone. I can't tell you how many times I wanted to reproduce the youtube guy who was bashing his monitor with the keyboard.
Proposed technical implementation details (optional)

Add an option to confirm closing a tab
make the closing button area smaller
make the tabs HUGE
let me place tabs on the side of a window rather than top (you know, more width than height in all modern monitors...)
just do away with the close button altogether, I wouldn't mind that either.

I don't know what's useful but probably the least annoying to everyone might be to just add an option to confirm closing a tab.

Thanks for the suggestions! These are actually already being tracked by other issues on our repo - please refer to:

/dup #2976 / /dup  #6549
Not specifically tracked anywhere, but sorta sounds like a #3327 kind of thing
/dup #597
/dup #835
/dup #3335


[webview_flutter] Support setting useWideViewPort

Some websites (e.g. those built with the wix website builder) don't really work without useWideViewPort on Android. If you don't use wide view port you will have a weird white bar on one or both sides.
As an example, here are 2 screenshots from wix.com:
How it should look (screenshot taken from Firefox):

How it looks in webview_flutter without wideviewport:

Therefore it would be nice if the webview supported setting useWideViewPort.

The fix for #70731 added unconditionally enabling useWideViewPort. Can you explain in more detail what you are requesting here that is different than that?

How it looks in webview_flutter without wideviewport

What version of webview_flutter and webview_flutter_android is that screenshot taken with?

Never mind then - my mistake. I checked https://github.com/flutter/plugins/pull/3325/files and didn't see any change that showed adding useWideViewPort.
It was also crossed out in the PR, so I thought it was undone:

Sorry for wasting your time. I've confirmed that wix websites work with webview_flutter 2.3.0


Does not work with Flutter 0.6.0

When upgrading the library to flutter 0.6.0, the library fails to solve versions:
The current Dart SDK version is 2.1.0-dev.0.0.flutter-be6309690f.

Because flutter_circular_chart 0.0.3 requires SDK version >=1.19.0 <2.0.0 and no versions of flutter_circular_chart match >0.0.3 <0.1.0, flutter_circular_chart ^0.0.3 is forbidden.
So, because flutter_example depends on flutter_circular_chart ^0.0.3, version solving failed.
pub get failed (1)

Added a merge request to fix this issue:
https://github.com/xqwzts/flutter_circular_chart/pull/15


Stableswap price quantity graph

Task linked: CU-86bw05zwu Make stableswap price vs reserves graph with 4 assets


Version 4 is more accurate but much slower than version 3?

Hi,
I benchmarked on same data with v4.1.0 and v3.5.0.
I can see some improvements on peptide recall with same massive-kb trained model, while the inference speed is much slower (same machine,GPU, same beam number). Does the same happen on your side?
If not, is it because I did not config the environment for Casanovo v4.1.0 correctly? I see something like this:
"You are using a CUDA device ('NVIDIA GeForce RTX 3080 Ti Laptop GPU') that has Tensor Cores. To properly utilize them, you should set torch.set_float32_matmul_precision('medium' | 'high') which will trade-off precision for performance. For more details, read https://pytorch.org/docs/stable/generated/torch.set_float32_matmul_precision.html#torch.set_float32_matmul_precision"
Best regards

Normally there should not be significant performance reductions between v4 and v3. There was a non-neligible slowdown when beam search was introduced, but that already stems from v3.2.0.
Nevertheless, performance is indeed an important point of attention. We are optimizing the beam search decoding code, which is the most time-consuming step, but this is currently still work in progress (#269).
The notification is just for informational purposes and now occurs because of newer versions of the PyTorch and PyTorch Lightning dependencies, but it doesn't have an impact on performance.
Can you give an estimate of the amount of slowdown you're experience? Is this for inference or for training? How many spectra are you processing and how long does it take?

With same 743 spectra, beam number of 5, prediction batch size of 512, also same machine, GPU and pretrained model:
v4.1.0:
Predicting DataLoader 0: 100%|███████████████████████████████████████████████████████████| 2/2 [05:24<00:00,  0.01it/s]
v3.5.0:
Predicting DataLoader 0: 100%|██████████████████████████████████████████████████████████| 2/2 [04:02<00:00, 121.11s/it]
Best regards

I didn't observe any significant difference in speed when I ran v4.1.0 and v3.5.0 with the same configurations (5 beams) on the same set of 14,257 spectra on this Colab GPU runtime.
v4.1.0:
Predicting DataLoader 0: 100% 14/14 [29:52<00:00, 128.04s/it]
v3.5.0:
Predicting DataLoader 0: 100% 14/14 [29:47<00:00, 127.67s/it]

So because of the small number of spectra in the first test, fluctuations in the start-up time might dominate. There doesn't seem to be a regression issue leading to a significant slowdown in v4. Nevertheless, computational efficiency is something we're actively investigating, and hopefully we'll be able to release some speed-ups soon.


Rename ots-parser-xml project to ots-xml

There will be more parser projects, but the ots-xml project is the central one for OTS. It might do more with other parsers and translators, such as writing XML or making transformations. Therefore, the more generic name ots-xml will be used for the project from now on.

In my head is was mostly just a more concise name. Suppose we have ots-opendrive. Then I would assume any importing/exporting code from/to OpenDRIVE is within the ots-opendrive project. Then, ots-xml can just remain focused on our own xml. Dependency would then be one-way: ots-opendrive depends on ots-xml.
The same would hold for any other parser that allows translation to/from ots-xml.

Good point. Will do.

Completed and working in Eclipse.


Add text to index page, include translations

References #350

Coverage remained the same at 100.0% when pulling c53db9c053700621515d6e162310eaf31f26fc07 on 350_about_hpi into e5112cac089720a2b41fcd4ff7d40cad908c8cdd on dev.

Coverage remained the same at 100.0% when pulling 72f04cb35052cec6364a3bd4d95d7c05c57f3c20 on 350_about_hpi into 55e5de5e3d06a37726ce762d4a419a176932b5fa on dev.

Coverage remained the same at 100.0% when pulling 520f2cc283e7ae41d03db638a9d01eb21d4336bd on 350_about_hpi into 55e5de5e3d06a37726ce762d4a419a176932b5fa on dev.

Coverage remained the same at 100.0% when pulling 70d3527ba8dcca264bf2984058fb1e08de7b0e70 on 350_about_hpi into deda02c78cc9cb9b03a7b52d3344cb7caaf572cd on dev.

Coverage remained the same at 100.0% when pulling b19548a17b95fd207a47ac38784d6bd0c747383e on 350_about_hpi into 67cbce082d97cde7db589ea9828d364366d5449a on dev.


processing extension

Update https://github.com/stac-extensions/processing with https://github.com/radiantearth/stac-spec/tree/3a83d75aec7f16ae597ee9779777a97e83ff46a4/extensions/processing

Review complete


[BUG] It should ignore backslashes

Hi,
Langman currently doesn't ignore backslashes. It scans if you\'re not the one and cannot recognize "if you're not the one" in strings.

What if you want to have a backslash in your text? 'Hello \World' for whatever reason that would be. Why not just fix your string?

cannot recognize "if you're not the one" in strings

Please explain this, can't get what you mean.

He wants this package to strip slashes from strings, but then laravels language parser wouldn't find the translation

@danijelk I know Hello \World doesn't right! Please attention the provided example above. I use single quotation in PHP most of the time, especially for strings (i.e. __('I don\'t like it')). JSON supports double quotation, well, you would find that string in language files as "{ I don't like it": "خوشم نمیاد" }. So I didn't use a backslash in JSON files but Langman scans and searches for exact strings, I mean it exactly search for "I don\'t like it" which doesn't exist.

I do see the point, one might need to use both ' and " in a string such as _('hello " world ' "'). It's Saids call though, but you could always do a pull request to show a solution.


Add an API to reload the workspace state from workspace-state.json

This will be used by sourcekit-lsp to reload the package state when it detects changes to workspace-state.json.

@swift-ci Please test

@swift-ci Please smoke test

closing in favor of #5510


Simplify the signatures for Parser.parse()

The new parser doesn't throw, and doesn't use several of the parameters that the old one used. Drop the extraneous parameters and throws.

@swift-ci please test

I thought this was safe to merge and I could rebase my diagnostics changes on top of this change but it broke CI, so I’m reverting it again.
https://github.com/apple/swift-syntax/pull/911


A new feature in tf.roll

Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information

TensorFlow version (you are using):
Tensorflow 2.1.0
Are you willing to contribute it (Yes/No):
Yes

Describe the feature and the current behavior/state.
Currently, tensorflow only allows for same shift in the same dimension. I want different shift ability
[[1,2,3,4],
[1,2,3,4],
[1,2,3,4]]
can be only turned into
[[2,3,4,1],
[2,3,4,1],
[2,3,4,1]] in the current iteration.
I need a roll function that can get this without using any for loop, I also need it for any dimension tensor , i.e. 4 dimension that I work on.
[[2,3,4,1],
[3,4,1,2],
[4,1,2,3]]
Will this change the current api? How?
Yes by adding a property.
Who will benefit with this feature?
People who work on system biology using tensorflow for transcription data. A great deal of this will be used in this paper which I authored. I want to expand it to make it more flexible.
https://academic.oup.com/bioinformatics/article/36/Supplement_1/i499/5870526?itm_content=bioinformatics&itm_source=trendmd-widget&itm_campaign=trendmd-pilot&itm_medium=sidebar
Any Other info.
Last time, it was closed using a replace method but it only solve the example problem I give, not the full problem.

@yiliu9090,
tf.roll now provides a facility to specify Multiple Axes. Can you PTAL? Thanks!

Sorry about the delay.
This is not what I really wanted for tf.roll. What I mean is that if there are multiple
Currently, tensorflow only allows for same shift in the same dimension. I want different shift for the same axis just different roll.
For Example
[[1,2,3,4],
[1,2,3,4],
[1,2,3,4]]
can be only turned into
[[2,3,4,1],
[2,3,4,1],
[2,3,4,1]] in the current iteration.
I need a roll function that can get this without using any for loop, I also need it for any dimension tensor , i.e. 4 dimension that I work on.
[[2,3,4,1],
[3,4,1,2],
[4,1,2,3]]
Here note that shift all happens at dimension 1, but the shift is 1,2,3 for different rows.
So this works a little differently from the what I initial thought.
What you have is still same axis same level, so it is impossible to do this. (If I am wrong please tell me how to do this in current iteration)
Thanks so much.

I could use this feature too, and I am happy to contribute to it.
Given a tensor of shape (n, y, x)
My current solution is to break the matrix into a list:
list = [list[item] for item in range(n)]
and then use another loop to pad/roll each list tensor:
for iter in range(len(list)):             xShift = (iter % xShift)             yShift = int(iter / yShift)             list[iter] = tf.roll(list[iter], shift= [yShift, xShift], axis= [0, 1])
the list can then be converted back to a tensor using:
list = tf.convert_to_tensor(list)
This is inefficient, but it works for my usecase.

if you don't want to loop, use map_fn as follows:
test=tf.repeat(tf.expand_dims(tf.range(5),0),4,0);
out = tf.map_fn(lambda arr: tf.roll(arr, tf.random.uniform( [1], 0, 6, dtype=tf.int32 ), 0), test);

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


Fixed build on clang on macOS

Because of that, the error happens on macOS:
In file included from scenes/level/lvl_quad_tree.cpp:3:
In file included from ./common_features/QuadTree/LooseQuadtree.h:116:
In file included from ./common_features/QuadTree/LooseQuadtree-impl.h:14:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/unordered_map:760:5: error: static_assert failed "Invalid allocator::value_type"
    static_assert((is_same<value_type, typename allocator_type::value_type>::value),
    ^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./common_features/QuadTree/LooseQuadtree-impl.h:482:25: note: in instantiation of template class 'std::__1::unordered_map<PGE_Phys_Object *, PGE_Phys_Object **, std::__1::hash<PGE_Phys_Object *>, std::__1::equal_to<PGE_Phys_Object *>, loose_quadtree::detail::BlocksAllocatorAdaptor<std::__1::pair<const PGE_Phys_Object *, PGE_Phys_Object **> > >' requested here
        ObjectPointerContainer object_pointers_;
                               ^
./common_features/QuadTree/LooseQuadtree.h:109:7: note: in instantiation of member class 'loose_quadtree::LooseQuadtree<double, PGE_Phys_Object, QTreePGE_Phys_ObjectExtractor>::Impl' requested here
        Impl impl_;
             ^
scenes/level/lvl_quad_tree.cpp:20:16: note: in instantiation of template class 'loose_quadtree::LooseQuadtree<double, PGE_Phys_Object, QTreePGE_Phys_ObjectExtractor>' requested here
    IndexTreeQ tree;

https://travis-ci.org/WohlSoft/PGE-Project/jobs/218300920
The solution for this error is here: http://stackoverflow.com/questions/27336941/eigenaligned-allocator-fails-with-stdunordered-multimap
Then, it has successfully built:
https://travis-ci.org/WohlSoft/PGE-Project/jobs/218412207

Thank you Vitaly, nice catch.


CNCF Cloud Native Sustainability Week

Is there a way to enter multiple authors in the presentation submission form? Only one name is provided.

Thanks for bringing this up!
I have updated the form. It now says "Full name(s)" to clarify that it is possible to enter multiple speakers.


[PORT] Move QnAMaker Dialog/Recognizer out of Adaptive and into QnA assembly

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/3775

#3719

Merge QnAMakerDialog2 => QnAMakerDialog
Move QnAMakerDialog and QnAMakerRecognizer into QnA assembly
Move schema definitions int QnA assembly
Move ComponentRegistration into QnA Assembly
remove dependencies between Adaptive and QnA
NOTE: Needed to move ITemplate<> into a shared location as that was only dependency on Adaptive, so moved it into BotBuilder which is where IRecognizer lives.

Changed projects

AdaptiveExpressions
Microsoft.Bot.Builder.AI.QnA
Microsoft.Bot.Builder.Dialogs.Adaptive
Microsoft.Bot.Builder
Microsoft.Bot.Builder.AI.QnA.Tests
Microsoft.Bot.Builder.Dialogs.Declarative.Tests

I'll start working on this after PR #2347 being merged as there are some pending changes regarding QnAMakerRecognizer.

As mentioned in PR #2235 , this change requires introducing dependency to adaptive-expressions to botbuilder-ai, @stevengum shall we need to move this to R11 as well?


40232527 - Remove this unused method parameter "trackStatistics"

A typical code smell known as unused function parameters refers to parameters declared in a function but not used anywhere within the function’s body. While this might seem harmless at first glance, it can lead to confusion and potential errors in your code. Disregarding the values passed to such parameters, the function’s behavior will be the same, but the programmer’s intention won’t be clearly expressed anymore. Therefore, removing function parameters that are not being utilized is considered best practice.

Removed the parameter and merged the code. Closing the issue


php-curl post no response

I'm trying to use php-curl-class to send POST to the server (service in Java).
With following php code (php 5.6)  run in browser, it has no any response, no reply at all. i.e. wait for the reply all the time.
In browser to test "http://<IP_ADDRESS>:8000/CommonOrderModeBPlusServlet.action", and get "success".
When I use Java to connect  to the server, it works fine without problem. But I have to use php.
Here is the code:
";
$string  .= "".$clientId."";
$string  .= "YTO";
$string  .= "".$customerId."";
$string  .= "";
//echo "$string.$parternId:";
//print_r($string.$parternId);

$clientId = "K21000119";
$customerId = "K21000119";
$parternId = 'u2Z1F7Fh';

$data_digest= "";//base64_encode(Bytes::toStr(Bytes::getBytes(md5($string.$parternId,true))));

$data=array();
$data['logistics_interface']=$string;//urlencode();
$data['data_digest']=($data_digest);
$data['clientId']=$clientId;

$curl = curl_init();
curl_setopt($curl, CURLOPT_URL, 'http://<IP_ADDRESS>:8000/CommonOrderModeBPlusServlet.action');
 curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
 curl_setopt($curl, CURLOPT_POST, 1 );
 curl_setopt($curl, CURLOPT_POSTFIELDS, $data);
  curl_setopt($curl, CURLOPT_HEADER, 0);

//var_dump($curl);

$tmpInfo = curl_exec ($curl);
curl_close ($curl);
echo $tmpInfo;
?>
Can any one help me ?

I have been working on the problem several day, and no any progress.  I tried even other way to send POST: "file_get_contents()", and got the same problem: no response. This service on the server-side should be working correctly. What is the problem in my code?
Here is my code:
";
$string  .= "".$clientId."";
$string  .= "YTO";
$string  .= "".$customerId."";
$string  .= "";
//echo "$string.$parternId:";
//print_r($string.$parternId);

$clientId = "K21000119";
$customerId = "K21000119";
$parternId = 'u2Z1F7Fh';

$data_digest= "";//base64_encode(Bytes::toStr(Bytes::getBytes(md5($string.$parternId,true))));

$data=array();
$data['logistics_interface']=$string;//urlencode();
$data['data_digest']=($data_digest);
$data['clientId']=$clientId;

$curl = curl_init();
curl_setopt($curl, CURLOPT_URL, 'http://<IP_ADDRESS>:8000/CommonOrderModeBPlusServlet.action');
 curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
 curl_setopt($curl, CURLOPT_POST, 1 );
 curl_setopt($curl, CURLOPT_POSTFIELDS, $data);
  curl_setopt($curl, CURLOPT_HEADER, 0);

//var_dump($curl);

$tmpInfo = curl_exec ($curl);
curl_close ($curl);
echo $tmpInfo;

?>


Restructure gitserver and idpbuilder to allow for pluggable images of argo apps

Create a GitServerImageUrl field on the localbuild resource so users can pass in a prebuilt gitserverimage. Also create a ImageUrl field on the gitserver resource so we can set it below. If gitserverimage is set on this localbuildresource, just pass it through to the gitserver resource via it's gitserverimageurl in the spec below. If gitserverimage is not set on this resource we should assume that folks want us to create an image with the default embedded argo apps so we should build the image here and then pass in the url via the gitserverimageurl field in the spec below. We can move the image.go file from the gitserver controller folder to this folder and reuse that logic.
https://github.com/cnoe-io/idpbuilder/blob/4d2048155151a98c9f13472d7f9cbb6ae6483298/pkg/controllers/localbuild/controller.go#L140-L145

Why do you install a git server using a project forked 6 years ago https://github.com/cirocosta/gitserver-http/ instead of a project which is maintained as gitea and that we could install/configure more easily as described here using a helm chart: https://inlets.dev/blog/2023/01/27/self-hosting-gitea-kubernetes.html ?

Closing this in favor of a full RFC on packaging See: #5


RFC: Add Model Schemas to OpenApi Docs

First, I'm loving the project so far and I really appreciate all the work you've done already.
I honestly don't mind the output requirement on a query/mutation, however, it would be nice to be able to define Model Schema's and reference those for the outputs inside the docs.  (ex. Pet Model from Redoc).

Hi @chuckstock. I have added this feature as a Maybe in our v1.0.0 roadmap (https://github.com/jlalmes/trpc-openapi/issues/91). Any idea how you would like this API to look?

Hi @chuckstock. I have added this feature as a "Maybe" in our v1.0.0 roadmap (https://github.com/jlalmes/trpc-openapi/issues/91). Any ideas how you would like this API to look/behave?
Initial thoughts 👇
// models.ts
export const User = z.object({
  id: z.string().uuid(),
  name: z.string(),
});

// router.ts
import { User } from './model';
export const appRouter = trpc.router().query('getUsers', {
  meta: { openapi: { ... } },
  input: ...,
  output: z.array(User),
  resolve: ...
});

// openapi.json.ts
import { User } from './model';
import { appRouter } from './router';

const openapi = generateOpenApiDocument(appRouter, {
  ...,
  models: [User]
});

cc @StefanTerdell.

Yeah this is almost exactly what I was thinking and was potentially expecting to find when reviewing the documentation. I think that makes a lot of sense without adding really any extra boilerplate or overhead.
Another package allows you to extend ZodObjects and turn them into openapi components, here is an example from their npm packaage:
import { extendApi, generateSchema } from '@anatine/zod-openapi';
const aZodExtendedSchema = extendApi(
      z.object({
        uid: extendApi(z.string().nonempty(), {
          title: 'Unique ID',
          description: 'A UUID generated by the server',
        }),
        firstName: z.string().min(2),
        lastName: z.string().optional(),
        email: z.string().email(),
        phoneNumber: extendApi(z.string().min(10), {
          description: 'US Phone numbers only',
          example: '555-555-5555',
        }),
      }),
      {
        title: 'User',
        description: 'A user schema',
      }
    );
const myOpenApiSchema = generateSchema(aZodExtendedSchema);

This is another suggestion, although I think I prefer your original suggestion for the API.

Hi, any updates on this?

I am also very interested in this, its the only open issue on the previous roadmap. Can this still be looked at for a future release?

I'm a bit late on the ball here haha. GHs UI sure is one of the UIs of all time
Dont know much about open api but I believe it moves the reused schemas out of what would be the idiomatic JSON schema position ("#/definitions" or "#/$defs"). But that's what the definitionPath option is for. It still presumes the root path to be the schema root though, but you can get around that with basePath.
Here's a basic example:
const baz = z.object({})

zodToJsonSchema(z.object({ x: baz }), {
  basePath: ["foo"],
  definitionPath: "bar",
  definitions: { baz },
})

>
{
  type: 'object',
  properties: { x: { '$ref': 'foo/bar/baz' } },
  required: [ 'x' ],
  additionalProperties: false,
  bar: {
    baz: { type: 'object', properties: {}, additionalProperties: false }
  }
}

You should be able to just move out the definitions object ("bar" in the example) from the resulting schema to put wherever you want in the open api doc as long as you can know the path beforehand and point at it with definitionsPath

I needed support for this also, published a quick implementation: https://www.npmjs.com/package/@devidw/trpc-openapi
Source-Code: https://github.com/devidw/trpc-openapi
All you need to do is pass a object with your model schemas when you generate the document:
import { generateOpenApiDocument } from "trpc-openapi";
import { z } from "zod";

const SomeSchema = z.object({
  a: z.literal(69),
});

generateOpenApiDocument(appRouter, {
  // ...
  defs: {
    SomeSchema,
  },
});


[mmlspark] Fix cached predictor causing bad values for predicted probabilities

In mmlspark, the predictied probabilities column was appearing the same as raw predicted values when both columns were computed from the model.  This is due to a caching bug in the native code logic that was recently added.  I added an array of predictors, one for each type, to fix the caching bug - and also added some additional checks in case the cached predictor needs to be reinitialized (not used by mmlspark directly).

adding @eisber

I remember the single row prediction is added by @eisber
ping @eisber to review.

@imatiach-msft Thanks! much cleaner now.


fix prestop in juicefs-plugin.

mv reg.sock prestop in node-driver-registar container

Codecov Report

Merging #397 (9132c71) into master (96ca368) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #397   +/-   ##
=======================================
  Coverage   46.62%   46.62%
=======================================
  Files          27       27
  Lines        2741     2741
=======================================
  Hits         1278     1278
  Misses       1372     1372
  Partials       91       91

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


Add new section in settings - "Visual representation"

Background
Just introducing all necessary settings that are needed to comply with ACS style is not enough. We should introduce a user-friendly way for the user to select ACS style.
A new section in the settings "Visual representation" should be added for that purpose.
Requirements

A new section in setting should be added called "Visual representation"
.....1.1. The section should be placed bellow the "General" and above "Stereochemistry".
.....1.2. The user can choose one of three options: "ACS style", "Ketcher Default" and "Custom".
.....1.3. "Ketcher Default" option is default.
If "ACS style" or "Ketcher default" is selected certain settings are disabled, and default values are chosen:

Setting
Setting position
ACS style
Ketcher Default

Atom coloring
General
OFF
ON

Font
General
Arial
Arial

Font size
General
10pt
10 pt

Sub font size
General
10pt
10 pt

Margin size (new setting)
General
1,6 pt
TBD

PNG resolution (new setting)
General
High
Low

Bond length (new setting)
Bonds
14,4 pt
TBD

Bond spacing (old name: Double bond width)
Bonds
18%
TBD

Bond thickness
Bonds
0,6 pt
2 pt ??

Stereo (Wedge) bond width
Bonds
2,0 pt
5 pt

Hash spacing (new setting)
Bonds
2,5 pt
TBD

If "Custom" is selected all settings are available.

UX
TBD

To solve this task, it is necessary to implement https://github.com/epam/ketcher/issues/5175 and https://github.com/epam/ketcher/issues/5176

Verified - a new option is added and all settings are with right parameters.
Environment
https://rc.test.lifescience.opensource.epam.com/KetcherDemoSA/index.html
Ketcher Version 2.26.0-rc.1 Build at 2024-10-04; 18:45:04
Indigo Version 1.25.0-rc.1.0-g704673fcb-wasm32-wasm-clang-19.0.0
MacOs
Chrome 129.0.6668.71 (Official Build) (arm64)


window.location.href stopped working recently on Excel for Mac?

Opening bug based on a Stackoverflow thread: https://stackoverflow.com/questions/48681380/window-location-href-stopped-working-recently-on-excel-for-mac
In a Javascript based Excel add-in, it navigates to a third party oauth sign-in page using the following code:
window.location.href = "https://app.hubspot.com/oauth/authorize";
It has been working well on Excel rich client on Mac (version 16.9 (180116)) until recently. Now it won't navigate to the 3rd party sign-in page anymore. There is no change in add-in manifest XML file and the 3rd party domain is whitelisted in the manifest as below too. The same code and manifest is still working well on PC Excel and Excel Online.
<AppDomain>https://app.hubspot.com/</AppDomain>

I think the way Excel for Mac supports the the window.location.href was changed recently? Thanks for your help!

The reference topic for <AppDomain> has been updated to add a note about not putting "/" on the end.


is there a library with the same features, but for react native ?

is there a library with the same features, but for react native ?
or I can use that library in react native expo app too ?

https://www.google.com/search?q=react-native-masked-text&oq=react+native+text&aqs=chrome.2.69i57j35i39l2j0i67l2j0j69i60l2.5949j0j7&sourceid=chrome&ie=UTF-8

https://github.com/benhurott/react-native-masked-text
this one is good!

thanks!!!

thanks for research!!!


SPARK-11326: Split networking in standalone mode

Merged build triggered.

jenkins, test this please

Merged build started.

@vanzin could you take a look?

Test build #44379 has started for PR 9287 at commit f3b2d9f.

Merged build triggered.

Merged build started.

Test build #44380 has started for PR 9287 at commit f3b2d9f.

Test build #44379 has finished for PR 9287 at commit f3b2d9f.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n

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

Merged build finished. Test PASSed.

Test build #44380 has finished for PR 9287 at commit f3b2d9f.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n

Merged build finished. Test PASSed.

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

Merged build triggered.

Merged build started.

jenkins, test this please

Test build #44594 has started for PR 9287 at commit 281d4f4.

Merged build triggered.

Merged build started.

Test build #44594 has finished for PR 9287 at commit 281d4f4.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n

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

Merged build finished. Test FAILed.

Test build #44596 has started for PR 9287 at commit 281d4f4.

Test build #44596 has finished for PR 9287 at commit 281d4f4.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #44657 has started for PR 9287 at commit 62bf841.

Test build #44657 has finished for PR 9287 at commit 62bf841.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #44999 has started for PR 9287 at commit 84baafc.

Test build #44999 has finished for PR 9287 at commit 84baafc.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #45119 has started for PR 9287 at commit 3c1467a.

Test build #45119 has finished for PR 9287 at commit 3c1467a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n

Merged build finished. Test PASSed.

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

@vanzin thanks a lot for your review. Of course, I'll apply all those rename/import/style changes. But the thing about env variable needs explanation - actually the user is supposed to provide a secret key in env variable. Especially, it is much more secure than providing it in a command line of spark-submit (as you know). Now that the network communication layers are separated, the user would have to provide "credentials" in order to submit the application.

But the thing about env variable needs explanation - actually the user is supposed to provide a secret key in env variable.

I haven't finished my review yet, but I was going to get to that. That change is really not necessary.
For the secret needed to connect to the Spark Master, that can be in the configuration file. Everybody needs to share the same secret, so there's no problem in it being there. Until the Master can do proper authentication, we'll have to live with that fact.
For the per-app secret, it should be auto-generated, like in YARN. The user should not need to provide their own secret every time they launch their app.
So you don't really have to set any env variables. The env variable is just a way to get the secret from the Worker to the executor without using the command line.
BTW, I think this is a step in the right direction, but because of the above, this is not really adding any extra security. Because all Spark-launched processes will run as the same user, it's possible for any malicious executor to just read other app's secrets from the Worker's memory (or directly from other running executors' environment in /proc).

Please see my JIRA comment.

I stopped when I got to the tests; overall, I share the same concerns Mark mentioned on the bug. I don't really know what the goals of standalone mode are in the long run, but if your concern is security, there's a lot of much harder work needed to get that working.

Build triggered.

Build started.

Test build #45217 has started for PR 9287 at commit b83ab2c.

Test build #45217 has finished for PR 9287 at commit b83ab2c.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):\n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n

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

Build finished. Test FAILed.

BTW you probably want @andrewor14 to take a look at this stuff.

Build triggered. sha1 is original commit.

Build started sha1 is original commit.

@vanzin I've changed it a little bit. The master doesn't create two endpoints now but different users can be used with a single endpoint. So basically the user can plug his own password authenticator if he wants to which will be used to authenticate Spark users with the master.
To authenticate workers with the master, and clients when no special password authenticator is plugged in, the default SASL user is used (as it was used so far). When the user wants to enable more sophisticated authentication, he simply needs to provide some authenticator or just set different secrets for the default user {{sparkSaslUser}} (which is used by the workers) and other users (the default authenticator allows to set multiple secrets like {{spark.authenticate.secrets.=password}} while the default password is set as usual with {{spark.authenticate.secret}}). In this case, the users should just do not need to know the default user password. Obviously, this only works for Netty RPC. The whole original behaviour when no-secret or a single shared secret is provided remains unchanged.
The last PR is not polished, but it removes most of the changes from the master. The remaining thing is authorisation - determining who is communicating with the master and authorising the requests (for example, only a default user can exchange worker messages, or only the application owner can remove his application).

Test build #45230 has started for PR 9287 at commit df542fc.

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

Build finished. No test results found.

Merged build triggered.

Merged build started.

Test build #45373 has started for PR 9287 at commit f604a6d.

Test build #45373 has finished for PR 9287 at commit f604a6d.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class DefaultPasswordAuthenticator(sparkConf: SparkConf)\n  * trait PasswordAuthenticator \n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n  * public class ClientAddress implements Serializable \n

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #45379 has started for PR 9287 at commit 508c97d.

Test build #45379 has finished for PR 9287 at commit 508c97d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class DefaultPasswordAuthenticator(sparkConf: SparkConf)\n  * trait PasswordAuthenticator \n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n  * public class ClientAddress implements Serializable \n

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #45411 has started for PR 9287 at commit 8b8121c.

Test build #45411 has finished for PR 9287 at commit 8b8121c.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * trait PasswordAuthenticator \n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n  * public class ClientAddress implements Serializable \n

Merged build finished. Test FAILed.

jenkins, test this please

Merged build triggered.

Merged build started.

Test build #45420 has started for PR 9287 at commit 8b8121c.

Test build #45420 has finished for PR 9287 at commit 8b8121c.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * final class ShuffleSortDataFormat extends SortDataFormat<PackedRecordPointer, LongArray> \n  * final class UnsafeSortDataFormat extends SortDataFormat<RecordPointerAndKeyPrefix, LongArray> \n  * trait PasswordAuthenticator \n  * class ExternalShuffleService(\n  *   case class BoundPortsResponse(\n  * class ExecutionMemoryPool(\n  * abstract class MemoryPool(lock: Object) \n  * class StorageMemoryPool(lock: Object) extends MemoryPool(lock) with Logging \n  * abstract class Writer extends BaseReadWrite \n  * trait Writable \n  * abstract class Reader[T] extends BaseReadWrite \n  * trait Readable[T] \n  * public class ClientAddress implements Serializable \n  * class LDAModel(JavaModelWrapper, JavaSaveable, Loader):\n  * case class DropAnyNull(child: Expression) extends UnaryExpression with ExpectsInputTypes \n  * case class GetInternalRowField(child: Expression, ordinal: Int, dataType: DataType)\n  * case class Expand(\n

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #45502 has started for PR 9287 at commit fe9de83.

Test build #45502 has finished for PR 9287 at commit fe9de83.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * trait PasswordAuthenticator \n  * class ExternalShuffleService(\n  * public class ClientAddress implements Serializable \n

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Test build #45512 has started for PR 9287 at commit 784cbca.

Test build #45512 has finished for PR 9287 at commit 784cbca.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * trait PasswordAuthenticator \n  * class ClientAddress implements Serializable \n

Merged build finished. Test PASSed.

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

Merged build triggered.

Merged build started.

Test build #45630 has started for PR 9287 at commit 9f6bb88.

Rebased and more reasonably split into commits.

Test build #45630 has finished for PR 9287 at commit 9f6bb88.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * trait PasswordAuthenticator \n  * class ClientAddress implements Serializable \n

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

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

jenkins, test this please

Merged build triggered.

Merged build started.

Test build #45661 has started for PR 9287 at commit 40df523.

Test build #45661 has finished for PR 9287 at commit 40df523.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * trait PasswordAuthenticator \n  * class ClientAddress implements Serializable \n

Merged build finished. Test FAILed.

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

Maybe we might have to correct the title just like the others, [SPARK-XXXX][SQL] (this is described in https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark).
Also, it would be better if the description of this PR is updated, It is empty.

This has been stale for a while, we should close this if there is no update here.

+1 for closing.

Closing, although I don't really understand the reason why it wasn't accepted.

I ~guess~ the reason it wasn't accepted and reviewed due to the lack of man power of committers or the lack of appealing or because it simply just got stale. At least, I said +1 for this reason.
I ~think~ it is okay to reopen, fix the codes to pass the tests, then keep pining reviewers after filling the PR description with a proper title according to the glide lines and an email to dev mailing list, yelling to the public to explain why this fix is right and nedded. Usually, it is really hard for a lot of changes to be merged quickly because it is hard to review. For this reason, I also have several old PRs but I am trying to explain and keep pinging with rebasing everytime they get conflicts
This one is not really in my area but if you strongly think this is the right fix and the important change,  I'd keep open this and then try to persuade reviwers with keeping pininging.


Add 'Using PBFT Consensus' section to PBFT doc

Summarize PBFT requirements and helpful tips

Link to procedures in the Sawtooth App Dev and Sys Admin Guide

Signed-off-by: Anne Chenette<EMAIL_ADDRESS>

Note: The PBFT-specific changes for the Sawtooth App Dev Guide are in a separate PR.


feat: provide link to angularlogos.com

closes #4

Hey @d-koppenhagen! Thanks for the PR 🙏
I had recently moved this project to a separate repo for ease of deployment. If able could you reopen this PR in blog-aleksanderbodurri so that you can get the contribution? The files you're targeting are in projects/shield-maker/src/app.
If not I can make the change there myself, but would rather have you listed as a contributor since you took the time to help out. Either way works. Once again, thank you for the PR. I didn't know about that website until now 😄

Okay, I will apply my changes in the other repo :)


9265 add published event

Fixes #9265
Please CR, @javitonino
cc/ @jmartinter

If there is no need to run this on the initial visualization creation (which is kind of like a publish), :ship: it.

Nah, it's cool. Just publish for now 😄
We have another event for created map already, and that contains info about the privacy.


New feature: Directive legend for tags

Feature request
As a user I want to dump a legend of used tags with meaning into the documentation so readers of the documentation know what my tags mean.
Implementation proposal
New directive needs_legend_tags prints a sphinx table with 2 columns 'tag' and 'description'.

See #6. Same arguments...

See #2
Closed.


Add "DECIMAL_CONSTRAINTS" to allow field constraints on "Optional[Decimal]"

Change Summary
This PR adds a new constant DECIMAL_CONSTRAINTS into pydantic/_internal/_known_annotated_metadata.py, allowing field constraints to be automatically applied to the inner Decimal types of an Optional[Decimal] type, e.g. Annotated[Decimal | None, Field(max_digits=3)].
Related issue number

fix #9748
and other related issues
Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[x] Unit tests for the changes exist
[x] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

The PR is ready, @sydney-runkle please review, thanks a lot!


Unable to stream audio by fetching partial content of the audio

Describe the bug
I have been trying to set initial Range in the header and an auto fetch property to stream audio data instead of downloading the whole file from the provided url.
To Reproduce
Try to setup Range headers in the Tone.Player method.
Expected behavior
Would be great to have a method to auto fetch the bytes range as per the configurations
What I've tried
I have been trying to handle it all outside by fetching the audio and setting the buffer of the tone.player

The way that the Web Audio API converts audio files into AudioBuffers (decodeAudioData), it's not currently possible to stream. decideAudioData requires the entire buffer be available. I'm going to close this issue for now, if this changes or new approaches come to light, we can reopen.