Custom AttributeCompatibilityRule breaks dependency resolution for composite build

Current Behavior
It is not possible to share files across subprojects and composite builds.
Gradle does resolves random files when sharing files across subprojects using Variant-aware sharing of artifacts between projects.
Gradle does not provide useful tools to debug and investigate issues relating to share files across subprojects (the current tasks are confusing and weird, and don't work when Gradle build script can't load, and don't show traceable information).
Gradle includes files from one configuration with different attributes into another
It is not possible to designate attributes as required.
Expected Behavior
It is possible to share files across subprojects and composite builds.
Gradle does not resolve random files when sharing files across subprojects using Variant-aware sharing of artifacts between projects.
Gradle provides useful tools to debug and investigate issues relating to share files across subprojects (the current tasks are confusing and weird, and don't work when Gradle build script can't load, and don't show traceable information).
Gradle does not include files from one configuration with different attributes into another
It is possible to designate attributes as required.
Steps to Reproduce
project.zip

run ./gradlew :test-project:help -q
ERROR Unresolved reference: MyAnnotation
run ./gradlew :test-project:help -PdisableHacks=true
Success BUILD SUCCESSFUL in 3s
But now run ./gradlew :test-plugin:aggregator:logCustomJars -q -PdisableHacks=true
ERROR Could not resolve all task dependencies for configuration ':test-plugin:aggregator:customJarsResolver'.
Now run ./gradlew :test-plugin:aggregator:logCustomJars -q -PnoTestProject=true
The customJars are correctly downloaded

Gradle version
8.7
Build scan URL (optional)
No response
Your Environment (optional)
No response

From a quick look at the reproducer, this might be caused by the custom compatibility rules being applied in a single project only.
You will need to apply them everywhere.

Can you please explain what you are trying to achieve?

Included build ':test-plugin' is an included build with multiple subprojects. One of the subprojects has a Gradle plugin.
Included build ':test-project' is an included build that has one root project, that uses the Gradle plugin.

When the project uses a custom AttributeCompatibilityRule, it breaks dependency resolution for composite build, causing Unresolved reference errors.
The custom AttributeCompatibilityRules are required, otherwise it causes Could not resolve all task dependencies for configuration when running ./gradlew :test-plugin:aggregator:logCustomJars.
I suspect that the reproducer doesn't make much sense in isolation. I would like to provide reproducers that are more complete and provide more context, however, Gradle's contribution rules require these minimal, abstract reproducers, that I think make it harder to understand the context.

From a quick look at the reproducer, this might be caused by the custom compatibility rules being applied in a single project only. You will need to apply them everywhere.

Thanks for looking into it. I tried adding the compatibility rules everywhere (even inside buildscript { dependencies {} }, but the issue remained.

The issue is in the backlog of the relevant team and is prioritized by them.

@aSemy could you share the updated reproducer with the compatibility rules applied everywhere, please?


Add "forward or backward" next to "Jump to Cursor"

This idea comes from Nina. "Jump to Cursor" doesn't make it clear that you can jump backward in your code. If we add "(forward or backward)" next to "Jump to Cursor", we may enhance discoverability of this awesome feature 😊

I have to disagree with adding "forward" or "backward". IMO, adding these descriptors doesn't help remove the implication that the command is doing more than setting the current instruction pointer to a different place. It implies that code will either be executed up to the cursor (i.e. run to cursor) or reversed (the functionality Karthik said in the demo that is is planned but really hard).
Instead, if we truly have total control over what this command is called, I would highly recommend using the same verbiage that Visual Studio uses for this scenario: "Set next statement".

@greazer I understand the concern. The reason why I wasn't so worried about that is because this feature usage is not known nor widely used, so I didn't think it would cause any bad reactions/implications.
But you did raise a good point, so I'm flipping "needs PR" to "needs decision", so I can talk to the team about this and discuss if we want to change it to "Set next statement" instead, or even some other option. And because of that I'm also putting a "type-enhancement" back to keep consistency ("needs decision" is applicable only for "type-enhancement" issues, which we basically consider as feature requests. We usually consider bugs anything that is working differently from the expected and/or designed. Sorry, I know it seems like nitpicking but since we keep track of open issues with type-bug on every sprint planning, I usually try to keep it consistent as much as I can 🙈)

BTW I see zero value in running the code backward, and I would not waste any time on ever implementing that. How much code is actually valid when run in reverse order?

This might just be a good thing to test out on some users, in terms of wordsmithing. Options could include "Reset execution to cursor" or "Go to cursor". I think for a lot of people, "Go to" would convey the right meaning because a number of programming languages have goto statements that are effectively doing the same thing.

Ah, I see. PyCharm calls it Jump To Cursor. Since we're directly competing with them, it's completely understandable why we might want to copy. However, given that the Visual Studio debugger has been considered the gold standard and crown jewel of Visual Studio for decades, I'm really hesitant to call this command something different than what Visual Studio has used all that time. There's really not much that has changed since this command was first named in VS, and I'm 100% sure that options such as "Jump to cursor" and "Go to cursor" were considered way back then. Heck I may have been part of the conversations. Given the strength of the arguments for the two going options right now, I, personally, don't think we'd really need to user study this.
I would argue strongly against adding "forward" or "backward" as it doesn't mean anything in this context. The user is simply changing the next statement that will be executed.
@gramster, I'm not sure what you're thinking running code backward is implying, but in my head, it means that you can set the process being debugged back to the exact state it was in at some point before. It's often referred to as historical debugging. This can be highly useful, if not the holy grail, in many debugging scenarios. It's the basic idea behind IntelliTrace (C# and other .NET languages) and C++'s Time Travel Debugging. It's a very hard problem to solve and get right, but when it works, it's amazing.

Ah, I would call that "undoing" rather than "running backward". It depends if you think in space or time :-). I was primed by reading your "executed up to the cursor" to think in space.
The time travel debugging is something I have wanted too, along with visualization a la http://pythontutor.com/

Closing in favour of https://github.com/microsoft/vscode/issues/92585


Alignment of the picker

The picker does not seem to stick to the bottom of the screen and doesn't adjust its size to the number of items that are in there.

Also the background slides in (instead of fading in), but that seems to be an issue of the Modal component.

I also don't think a ScrollView should be used when the height of the items does not exceed the height of the container.


Image rename while npm build

Description
Images are getting rename while npm build .
Example:
import Banner from './banner.png';
< img src={Banner} className="header" alt="Banner" / >
When I look  through the debugger on browser the src image shown as "21718c1a5a04ed25da78c1d39f88abec.png"
< img alt="Banner" class="header" src="/21718c1a5a04ed25da78c1d39f88abec.png" >

@bhushanscholastic
It's not an issue. it is a feature. It'll not affect your SEO even because you're anyway having an alt and title tags for that.


(PUP-10640) setup github actions for main branch

I cherrypicked commit https://github.com/puppetlabs/puppet/pull/8352/commits/9c60d3e232cf61fb9d6578b1912ad1664d80cbae and resolved conflicts. It's a bit clearer that 2.3/2.4 are removed, 2.7 is added on windows, and the branch names changed.

I'm going to merge this so that both master & main are on GH Actions, and then I'll rekick open PRs.


StepIn, StepInto and StepOut don't work

Hi, i was looking for this a long time ago and i'm very thankful, but i found a bug when i try to use the stepin, stepinto or stepout, nothing happens when click on one of these actions, everything works except the actions that i mentioned.
I'm using vscode 1.1.0 in windows 10, firefox 46.0.1 and the latest version of this pluging. I hope help

Hi, I tried to reproduce this but stepping worked for me. I tested this with VS Code 1.1.1 on Windows 7 and Firefox 45.0.1 - that's the closest I could get to your setup but I doubt that this has anything to do with the versions of Windows or Firefox.
Could you please make a test page available together with the exact steps how to reproduce (e.g. the location of your breakpoint, what to click on the page to trigger the breakpoint ...).

These is the image.

Sorry, that's still not enough information for me to reproduce the problem.
Could you make a zip file containing your web application and attach it to this thread?

Hi again, sorry but i can't give you a copy of the project because isn't permitted for me, but i have made an tiny example that doesn't work too. I omitted that the continue button doesn't work neither. I tried this
index.html

<!DOCTYPE html>

	<meta charset="UTF-8">
	<title>Sample</title>

and
script.js

(function () {
	var sample = document.getElementById('sample');
	var tag = sample.tagName;
	console.log(tag);
})();

Put a breakpoint wherever you want and try to debug.

Thanks, now I could reproduce the bug and fix it. Please update your plugin and confirm if it works in your web application as well.

Everything works fine now, thank you for be so faster.

Great. Thanks for the bugreport.


Building application for different targets

Prepare workflows (when possible) for building dmntk for multiple targets like:

Linux
MacOS
Windows MSVC
Windows GNU

Prepared workflows on GitHub for building for targets:

Linux: Ubuntu-latest,
Windows: windows-latest
MacOs: macos-latest


[OSDEV-1429] Block list uploading during release process

OSDEV-1429 The list upload switcher has been created to disable the Submit button on the List Contribute page through the Switch page in the Django admin panel during the release process and implemented a check on the list upload endpoint.

Please fix linter error.


Move discussion button next to paste button

Same idea as it is visible when in the context of that snippet.

Fixed in https://github.com/microsoft/z3guide/pull/95/commits/466ec061499d033dc68b98e8ed003de5c192d719


Error: Invalid public key input

Im using Windows. Im using true .env file. How can i fix this?

I have this same problem.

Check if you put a valid address in your json files metadata. In the creators section:
	"creators": [
		{
			"address": "YOUR ADDRESS",
			"share": 100
		}

Check if you put a valid address in your json files metadata. In the creators section:
	"creators": [
		{
			"address": "YOUR ADDRESS",
			"share": 100
		}

I was put bro. Thank you

Check if you put a valid address in your json files metadata. In the creators section:
	"creators": [
		{
			"address": "YOUR ADDRESS",
			"share": 100
		}

Where do you find this?

Has anyone found a solution to this issue?
Creator address matches REACT_APP_TREASUR_ADDRESS & the error persists. Also working on Devnet. Should the address be shorter than 32 characters?


CSS Nesting with BEM

I’m not sure if it works as intended?
Here’s a minimal example where there are two buttons, and one is rendered bigger than the other.
Notice the “parent” class is .button, and in the HTML the actual class I added was .foo--prim. But it still gets the primary style added, in this case an even larger font size, but could be anything:
<!DOCTYPE html>

    <title>CSS Nesting</title>

      <button
        type="button"
        class="button"
      >
        Save
      </button>

      <button
        type="button"
        class="button foo--prim"
      >
        Update
      </button>

Hi @jonnybarnes ! Thank you for your comment! It works as you described! The button size will be 3 rem.
Yes, using class attributes to describe modifiers is quite risky if you are unaware of all the intricacies, for example as you mentioned. I am sure there are many others.
But honestly, using two modifiers from different blocks with the same name is a rather rare occurrence. At least, it hasn't happened in my practice.
Overall, the point of the article is to share my experience and possibly inspire someone to try something new. However, I definitely wouldn't want it to become a standard for anyone. People need to understand all the risks.


Unable to create custom widgets in Mapsui.Forms

In dotnet standard projects, it is currently impossible to create custom widgets since the required ISkiaWidgetRenderer is not available in the Mapsui.Forms NuGet package. This can be solved by referencing the Mapsui.Rendering.Skia dll in the NuGet package.
For reference this was discussed with @pauldendulk in gitter. A quote about how to solve the problem:

I think I understand the problem. In our nuspec we define which dlls belong to which project type.
Currently only Mapsui en Mapsui.Geometries are added there. The Forms core project is of type netstandard, so only those dlls were added. Originally this made sense because nothing else was needed, but with the introduction of widgets with possible custom implementations in skia it makes sense to add Mapsui.Rendering.Skia to the netstandard list.

Thanks for reporting this.

No further reports. Assumed fixed.


No module named 'transformers.models.cohere.configuration_cohere'

ComfyUI Error Report
Error Details

Node Type: Miaoshouai_Tagger
Exception Type: RuntimeError
Exception Message: Failed to import transformers.models.cohere.configuration_cohere because of the following error (look up to see its traceback):
No module named 'transformers.models.cohere.configuration_cohere'

Stack Trace
  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\custom_nodes\ComfyUI-Miaoshouai-Tagger\nodes.py", line 123, in start_tag
    model = AutoModelForCausalLM.from_pretrained(model_path, attn_implementation=attention, device_map=device,

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\venv\lib\site-packages\transformers\models\auto\auto_factory.py", line 541, in from_pretrained
    )

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\venv\lib\site-packages\transformers\models\auto\auto_factory.py", line 752, in keys
    if key in self._model_mapping.keys()

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\venv\lib\site-packages\transformers\models\auto\auto_factory.py", line 753, in <listcomp>
    ]

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\venv\lib\site-packages\transformers\models\auto\auto_factory.py", line 749, in _load_attr_from_module
    mapping_keys = [

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\venv\lib\site-packages\transformers\models\auto\auto_factory.py", line 693, in getattribute_from_module
    # object at the top level.

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\venv\lib\site-packages\transformers\utils\import_utils.py", line 1593, in __getattr__

  File "F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\venv\lib\site-packages\transformers\utils\import_utils.py", line 1605, in _get_module

System Information

ComfyUI Version: v0.2.2-1-gc27ebeb
Arguments: F:\StabilityMatrix-win-x64\Data\Packages\ComfyUI3\main.py --preview-method auto --auto-launch
OS: nt
Python Version: 3.10.11 (tags/v3.10.11:7d4cc5a, Apr  5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)]
Embedded Python: false
PyTorch Version: 2.1.2+cu121

Devices

Name: cuda:0 NVIDIA GeForce RTX 4090 : cudaMallocAsync

Type: cuda
VRAM Total:<PHONE_NUMBER>4
VRAM Free:<PHONE_NUMBER>8
Torch VRAM Total: 33554432
Torch VRAM Free: 12254312

check your transformer version


Fixed #51 Aligned Number of Enrolled

Issue: #51

fixed: Alignment

Please review and let me know if it fine

please check the color of text and also I don't think its required to set the .env path, what do you think @aavishkarmishra ?

Please review and let me know if it fine

please check the color of text and also I don't think its required to set the .env path, what do you think @aavishkarmishra ?

just place the .env at root of server

just place the .env at root of server

Yes Actually I already placed the .env in the root folder that's why I changed the Path

Please review and let me know if it fine

please check the color of text and also I don't think its required to set the .env path, what do you think @aavishkarmishra ?

Sorry for the Color will be done soon

Done: I guess

just place the .env at root of server

I think so as .env file is related to server, so it will be better to place it in root of server.

make a fresh PR with only the required changes(dont change .env path) and we can merge also check the merge conflict


Unable to login to your DC/OS cluster. Clusters must be connected to the internet.

SETUP:

Using just the CLI on an ubuntu VM
dcos-docker doctor comes back clean with following output:

cades@michael-b-dcos:~$ dcos-docker doctor

Note: Docker has approximately 62.9 GB of memory available. The amount of memory required depends on the workload. For example, creating large clusters or multiple clusters requires a lot of memory.
A four node cluster seems to work well on a machine with 9 GB of memory available to Docker.
2018-07-27 15:27:02 WARNING  dcos_e2e._common | ['docker', 'exec', '--user', 'root', '0753eae86187eb76f2758a48debd2076e37f4a7a2d2aa940b196d75bd69b4483', 'docker', 'run', '-v', '/foo', 'alpine']
2018-07-27 15:27:02 WARNING  dcos_e2e._common | Unable to find image 'alpine:latest' locally
2018-07-27 15:27:02 WARNING  dcos_e2e._common | latest: Pulling from library/alpine
2018-07-27 15:27:02 WARNING  dcos_e2e._common | 8e3ba11ec2a2: Pulling fs layer
2018-07-27 15:27:02 WARNING  dcos_e2e._common | 8e3ba11ec2a2: Download complete
2018-07-27 15:27:02 WARNING  dcos_e2e._common | 8e3ba11ec2a2: Pull complete
2018-07-27 15:27:02 WARNING  dcos_e2e._common | Digest: sha256:7043076348bf5040220df6ad703798fd8593a0918d06d3ce30c6c93be117e430
2018-07-27 15:27:02 WARNING  dcos_e2e._common | Status: Downloaded newer image for alpine:latest

Note: If you continue to experience problems, more information is available at http://dcos-e2e.readthedocs.io/en/latest/docker-backend.html#troubleshooting.

double checked that all ingress ports are open, TCP and ICMP is enabled
ran dcos-docker create /tmp/dcos_generate_config.sh --one-master-host-port-map 80:80 in order to make the web UI accessible to a web-browser inside the network.
waited 10-15 minutes and used browser to go to http://xxx.xx.xx.99. This is where docs-docker is installed and where the previous command was ran.

BEHAVIOR:

Directed to login screen on the web UI.
Click GitHub or google to login.

Sometimes it will actually have the GitHub/google login screens pop up and even walk me through the two factor authorization (if click on google)
Sometimes it will just pop up an empty box and then disappear.
In both cases, after 5-10 seconds the following error will appear: Unable to login to your DC/OS cluster. Clusters must be connected to the internet.

I am able to use ping/curl inside the node, successfully connecting to the internet. So, it does have access to the internet. When I ran the dcos-docker on my local machine (MacOS), everything worked perfectly; however, when I switched to using a cli only on ubuntu, I keep running into this issue...
Also, one more hint.... anytime I run the wait command after creating the cluster, I eventually run into this error as well: raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http://xxx.17.0.2/acs/api/v1/auth/login.. which I noted was a different url then the node I'm using.
Any pointers in the right direction?
Possibly relevant issues:

https://groups.google.com/a/dcos.io/forum/#!topic/users/hjE27TwBxVk
https://dcosjira.atlassian.net/browse/DCOS-545

Thank you for the thorough issue.
A few initial routes of investigation:

Please can you run dcos-docker wait -vvv and post the full output.
Please can you try this on a new DC/OS Docker cluster without the wait command, but instead waiting 15 minutes.
Please can you try without the --one-master-host-port-map 80:80 and see if the wait command works.

which I noted was a different url then the node I'm using

Can you please run dcos-docker inspect and then compare the IP addresses there to the one in the error message.

$dcos-docker inspect
{
    "Cluster ID": "default",
    "Nodes": {
        "agents": [
            {
                "docker_container_id": "f3d4584f43d19269c92e19cf7dd6f2f528b6f608ac4487138cc53b2823d4d080",
                "docker_container_name": "dcos-e2e-8c6fcf53-3ecf-4e62-a4ea-0fa21b88add5-agent-0",
                "e2e_reference": "agent_0",
                "ip_address": "xxx.17.0.3"
            }
        ],
        "masters": [
            {
                "docker_container_id": "05db7a3f891cc2519a7876422d2f67bf54a6cfc8e44176b19f6234bbe05166a5",
                "docker_container_name": "dcos-e2e-8c6fcf53-3ecf-4e62-a4ea-0fa21b88add5-master-0",
                "e2e_reference": "master_0",
                "ip_address": "xxx.17.0.2"
            }
        ],
        "public_agents": [
            {
                "docker_container_id": "28b0b88296bdbec22b04757acd19ab45045cc9a2eb4d6f76b776436fe6f39ae4",
                "docker_container_name": "dcos-e2e-8c6fcf53-3ecf-4e62-a4ea-0fa21b88add5-public-agent-0",
                "e2e_reference": "public_agent_0",
                "ip_address": "xxx.17.0.4"
            }
        ]
    },
    "SSH key": "/tmp/8e26c921242e4761bafc8f5ccb6a5d18/ssh/id_rsa",
    "Web UI": "http://xxx.17.0.2"
}

The "web ui" IP address is different than the IP address I'm running docs-docker on.. we mapped the web UI to port 80 on xxx.xx.11.99. May be the issue?

The web UI is meant to be the IP address of the node.
With the option you used, I'd expect node_ip:80 to be equivalent to localhost:80 on the host.

Still running the commands for your previous questions...
I'm not sure where the xxx.17.0.2 is coming from.. The IP address of my "node", or the VM that I'm using, is xxx.22.11.99. Thus, localhost is also xxx.22.11.99

$ dcos-docker wait -vvv
A cluster may take some time to be ready.
The amount of time it takes to start a cluster depends on a variety of factors.
If you are concerned that this is hanging, try "dcos-docker doctor" to diagnose common issues.
If you cancel this command while it is running, you may not be able to log in. To resolve that, run this command again.
/2018-07-27 15:59:29 DEBUG    dcos_e2e._common | sudo: /opt/mesosphere/bin/dcos-check-runner: command not found
|2018-07-27 15:59:30 DEBUG    dcos_e2e._common | {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |   "status": 0,
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |   "checks": {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     "components_master": {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "output": "",
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "status": 0
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     },
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     "curl": {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "output": "",
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "status": 0
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     },
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     "ip_detect_script": {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "output": "xxx.17.0.2 is a valid IPV4 address\n",
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "status": 0
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     },
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     "journald_dir_permissions": {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "output": "directory /run/log/journal has the group owner `systemd-journal` and group permissons r-x\n",
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "status": 0
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     },
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     "mesos_master_replog_synchronized": {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "output": "",
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "status": 0
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     },
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     "tar": {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "output": "",
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "status": 0
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     },
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     "unzip": {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "output": "",
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "status": 0
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     },
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     "xz": {
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "output": "",
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |       "status": 0
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |     }
2018-07-27 15:59:30 DEBUG    dcos_e2e._common |   }
2018-07-27 15:59:30 DEBUG    dcos_e2e._common | }
\2018-07-27 15:59:31 DEBUG    dcos_e2e._common | Connecting to zk-1.zk:2181,zk-2.zk:2181,zk-3.zk:2181,zk-4.zk:2181,zk-5.zk:2181
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,638] INFO Client environment:zookeeper.version=3.5.0-alpha-1615249, built on 08/01/2014 22:13 GMT (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,641] INFO Client environment:host.name=dcos-e2e-8c6fcf53-3ecf-4e62-a4ea-0fa21b88add5-master-0 (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:java.version=1.8.0_152 (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:java.vendor=Oracle Corporation (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:java.home=/opt/mesosphere/packages/java--5e8781ced77cfcbada2912e209374e96a9edc2db/usr/java/jre (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:java.class.path=/opt/mesosphere/bin/../build/classes:/opt/mesosphere/bin/../build/lib/*.jar:/opt/mesosphere/bin/../lib/xml-apis.xml-apis-1.4.01.jar:/opt/mesosphere/bin/../lib/xerces.xercesImpl-2.11.0.jar:/opt/mesosphere/bin/../lib/org.yaml.snakeyaml-1.16.jar:/opt/mesosphere/bin/../lib/org.threeten.threetenbp-1.3.3.jar:/opt/mesosphere/bin/../lib/org.slf4j.slf4j-api-1.7.25.jar:/opt/mesosphere/bin/../lib/org.slf4j.log4j-over-slf4j-1.7.21.jar:/opt/mesosphere/bin/../lib/org.slf4j.jul-to-slf4j-1.7.21.jar:/opt/mesosphere/bin/../lib/org.slf4j.jcl-over-slf4j-1.7.21.jar:/opt/mesosphere/bin/../lib/org.scalaz.scalaz-core_2.11-7.2.0.jar:/opt/mesosphere/bin/../lib/org.scalatest.scalatest_2.11-2.2.5.jar:/opt/mesosphere/bin/../lib/org.scala-stm.scala-stm_2.11-0.7.jar:/opt/mesosphere/bin/../lib/org.scalamacros.resetallattrs_2.11-1.0.0.jar:/opt/mesosphere/bin/../lib/org.scala-lang.scala-reflect-2.11.8.jar:/opt/mesosphere/bin/../lib/org.scala-lang.scala-library-2.11.8.jar:/opt/mesosphere/bin/../lib/org.scala-lang.modules.scala-xml_2.11-1.0.3.jar:/opt/mesosphere/bin/../lib/org.scala-lang.modules.scala-parser-combinators_2.11-1.0.4.jar:/opt/mesosphere/bin/../lib/org.scala-lang.modules.scala-java8-compat_2.11-0.8.0-RC1.jar:/opt/mesosphere/bin/../lib/org.scala-lang.modules.scala-async_2.11-0.9.7.jar:/opt/mesosphere/bin/../lib/org.rogach.scallop_2.11-1.0.0.jar:/opt/mesosphere/bin/../lib/org.reactivestreams.reactive-streams-1.0.0.jar:/opt/mesosphere/bin/../lib/org.parboiled.parboiled-scala_2.11-1.1.7.jar:/opt/mesosphere/bin/../lib/org.parboiled.parboiled-core-1.1.7.jar:/opt/mesosphere/bin/../lib/org.mozilla.rhino-1.7R4.jar:/opt/mesosphere/bin/../lib/org.jvnet.mimepull.mimepull-1.9.5.jar:/opt/mesosphere/bin/../lib/org.joda.joda-convert-1.8.1.jar:/opt/mesosphere/bin/../lib/org.jboss.logging.jboss-logging-3.2.1.Final.jar:/opt/mesosphere/bin/../lib/org.javassist.javassist-3.20.0-GA.jar:/opt/mesosphere/bin/../lib/org.javabits.jgrapht.jgrapht-core-0.9.3.jar:/opt/mesosphere/bin/../lib/org.hibernate.hibernate-validator-5.2.2.Final.jar:/opt/mesosphere/bin/../lib/org.glassfish.javax.el-3.0.0.jar:/opt/mesosphere/bin/../lib/org.coursera.metrics-datadog-1.1.5.jar:/opt/mesosphere/bin/../lib/org.coursera.dropwizard-metrics-datadog-1.1.5.jar:/opt/mesosphere/bin/../lib/org.asynchttpclient.netty-resolver-dns-2.0.36.jar:/opt/mesosphere/bin/../lib/org.asynchttpclient.netty-resolver-2.0.36.jar:/opt/mesosphere/bin/../lib/org.asynchttpclient.netty-codec-dns-2.0.36.jar:/opt/mesosphere/bin/../lib/org.asynchttpclient.async-http-client-netty-utils-2.0.36.jar:/opt/mesosphere/bin/../lib/org.asynchttpclient.async-http-client-2.0.36.jar:/opt/mesosphere/bin/../lib/org.apache.zookeeper.zookeeper-3.5.0-alpha.jar:/opt/mesosphere/bin/../lib/org.apache.mesos.mesos-1.0.2.jar:/opt/mesosphere/bin/../lib/org.apache.httpcomponents.httpcore-4.4.4.jar:/opt/mesosphere/bin/../lib/org.apache.httpcomponents.httpclient-4.5.2.jar:/opt/mesosphere/bin/../lib/org.apache.httpcomponents.fluent-hc-4.3.6.jar:/opt/mesosphere/bin/../lib/org.apache.curator.curator-recipes-2.10.0.jar:/opt/mesosphere/bin/../lib/org.apache.curator.curator-framework-2.10.0.jar:/opt/mesosphere/bin/../lib/org.apache.curator.curator-client-2.10.0.jar:/opt/mesosphere/bin/../lib/org.apache.commons.commons-lang3-3.4.jar:/opt/mesosphere/bin/../lib/oauth.signpost.signpost-core-<IP_ADDRESS>.jar:/opt/mesosphere/bin/../lib/oauth.signpost.signpost-commonshttp4-<IP_ADDRESS>.jar:/opt/mesosphere/bin/../lib/nl.grons.metrics-scala_2.11-3.5.4_a2.3.jar:/opt/mesosphere/bin/../lib/net.sf.jopt-simple.jopt-simple-4.6.jar:/opt/mesosphere/bin/../lib/net.logstash.logback.logstash-logback-encoder-4.7.jar:/opt/mesosphere/bin/../lib/net.liftweb.lift-markdown_2.11-2.6.2.jar:/opt/mesosphere/bin/../lib/net.jcazevedo.moultingyaml_2.11-0.2.jar:/opt/mesosphere/bin/../lib/net.java.dev.javacc.javacc-5.0.jar:/opt/mesosphere/bin/../lib/mesosphere.mesos-utils_2.11-1.0.2.jar:/opt/mesosphere/bin/../lib/mesosphere.marathon.plugin-interface_2.11-1.3.13.jar:/opt/mesosphere/bin/../lib/mesosphere.marathon.marathon_2.11-1.3.13.jar:/opt/mesosphere/bin/../lib/mesosphere.marathon.api-console-0.1.1.jar:/opt/mesosphere/bin/../lib/mesosphere.chaos_2.11-0.8.7.jar:/opt/mesosphere/bin/../lib/mesos-1.5.1-sources.jar:/opt/mesosphere/bin/../lib/mesos-1.5.1-shaded-protobuf.jar:/opt/mesosphere/bin/../lib/mesos-1.5.1-javadoc.jar:/opt/mesosphere/bin/../lib/mesos-1.5.1.jar:/opt/mesosphere/bin/../lib/log4j.log4j-1.2.16.jar:/opt/mesosphere/bin/../lib/joda-time.joda-time-2.9.6.jar:/opt/mesosphere/bin/../lib/javax.validation.validation-api-1.1.0.Final.jar:/opt/mesosphere/bin/../lib/javax.transaction.jta-1.1.jar:/opt/mesosphere/bin/../lib/javax.mail.mailapi-1.4.3.jar:/opt/mesosphere/bin/../lib/javax.inject.javax.inject-1.jar:/opt/mesosphere/bin/../lib/javax.activation.activation-1.1.jar:/opt/mesosphere/bin/../lib/io.spray.spray-util_2.11-1.3.3.jar:/opt/mesosphere/bin/../lib/io.spray.spray-io_2.11-1.3.3.jar:/opt/mesosphere/bin/../lib/io.spray.spray-httpx_2.11-1.3.3.jar:/opt/mesosphere/bin/../lib/io.spray.spray-http_2.11-1.3.3.jar:/opt/mesosphere/bin/../lib/io.spray.spray-client_2.11-1.3.3.jar:/opt/mesosphere/bin/../lib/io.spray.spray-can_2.11-1.3.3.jar:/opt/mesosphere/bin/../lib/io.reactivex.rxscala_2.11-0.26.2.jar:/opt/mesosphere/bin/../lib/io.reactivex.rxjava-1.1.6.jar:/opt/mesosphere/bin/../lib/io.netty.netty-transport-native-epoll-4.0.51.Final-linux-x86_64.jar:/opt/mesosphere/bin/../lib/io.netty.netty-transport-4.0.51.Final.jar:/opt/mesosphere/bin/../lib/io.netty.netty-handler-4.0.51.Final.jar:/opt/mesosphere/bin/../lib/io.netty.netty-common-4.0.51.Final.jar:/opt/mesosphere/bin/../lib/io.netty.netty-codec-http-4.0.51.Final.jar:/opt/mesosphere/bin/../lib/io.netty.netty-codec-4.0.51.Final.jar:/opt/mesosphere/bin/../lib/io.netty.netty-buffer-4.0.51.Final.jar:/opt/mesosphere/bin/../lib/io.netty.netty-3.7.0.Final.jar:/opt/mesosphere/bin/../lib/io.dropwizard.metrics.metrics-servlets-3.1.2.jar:/opt/mesosphere/bin/../lib/io.dropwizard.metrics.metrics-jvm-3.1.2.jar:/opt/mesosphere/bin/../lib/io.dropwizard.metrics.metrics-json-3.1.2.jar:/opt/mesosphere/bin/../lib/io.dropwizard.metrics.metrics-jetty9-3.1.2.jar:/opt/mesosphere/bin/../lib/io.dropwizard.metrics.metrics-jersey-3.1.2.jar:/opt/mesosphere/bin/../lib/io.dropwizard.metrics.metrics-healthchecks-3.1.2.jar:/opt/mesosphere/bin/../lib/io.dropwizard.metrics.metrics-graphite-3.1.2.jar:/opt/mesosphere/bin/../lib/io.dropwizard.metrics.metrics-core-3.1.2.jar:/opt/mesosphere/bin/../lib/io.dropwizard.metrics.metrics-annotation-3.1.2.jar:/opt/mesosphere/bin/../lib/io.dropwizard.dropwizard-validation-0.9.1.jar:/opt/mesosphere/bin/../lib/io.dropwizard.dropwizard-util-0.9.1.jar:/opt/mesosphere/bin/../lib/io.dropwizard.dropwizard-metrics-0.9.1.jar:/opt/mesosphere/bin/../lib/io.dropwizard.dropwizard-lifecycle-0.9.1.jar:/opt/mesosphere/bin/../lib/io.dropwizard.dropwizard-jackson-0.9.1.jar:/opt/mesosphere/bin/../lib/dcos.metronome-0.4.2-sans-externalized.jar:/opt/mesosphere/bin/../lib/dcos.metronome-0.4.2-assets.jar:/opt/mesosphere/bin/../lib/dcos.jobs-0.4.2.jar:/opt/mesosphere/bin/../lib/dcos.api-0.4.2.jar:/opt/mesosphere/bin/../lib/com.wix.accord-core_2.11-0.5.jar:/opt/mesosphere/bin/../lib/com.wix.accord-api_2.11-0.5.jar:/opt/mesosphere/bin/../lib/com.typesafe.ssl-config-core_2.11-0.2.1.jar:/opt/mesosphere/bin/../lib/com.typesafe.scala-logging.scala-logging_2.11-3.4.0.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.twirl-api_2.11-1.1.1.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-ws_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-streams_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-server_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-netty-utils-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-netty-server_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-logback_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-json_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-iteratees_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-functional_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-exceptions-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play-datacommons_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.play_2.11-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.play.build-link-2.5.18.jar:/opt/mesosphere/bin/../lib/com.typesafe.netty.netty-reactive-streams-http-1.0.8.jar:/opt/mesosphere/bin/../lib/com.typesafe.netty.netty-reactive-streams-1.0.8.jar:/opt/mesosphere/bin/../lib/com.typesafe.config-1.3.1.jar:/opt/mesosphere/bin/../lib/com.typesafe.akka.akka-stream_2.11-2.4.20.jar:/opt/mesosphere/bin/../lib/com.typesafe.akka.akka-slf4j_2.11-2.4.20.jar:/opt/mesosphere/bin/../lib/com.typesafe.akka.akka-actor_2.11-2.4.20.jar:/opt/mesosphere/bin/../lib/com.twitter.util-zk_2.11-6.34.0.jar:/opt/mesosphere/bin/../lib/com.twitter.util-stats_2.11-6.34.0.jar:/opt/mesosphere/bin/../lib/com.twitter.util-registry_2.11-6.34.0.jar:/opt/mesosphere/bin/../lib/com.twitter.util-logging_2.11-6.34.0.jar:/opt/mesosphere/bin/../lib/com.twitter.util-lint_2.11-6.34.0.jar:/opt/mesosphere/bin/../lib/com.twitter.util-function_2.11-6.34.0.jar:/opt/mesosphere/bin/../lib/com.twitter.util-core_2.11-6.34.0.jar:/opt/mesosphere/bin/../lib/com.twitter.util-collection_2.11-6.34.0.jar:/opt/mesosphere/bin/../lib/com.twitter.util-app_2.11-6.34.0.jar:/opt/mesosphere/bin/../lib/com.twitter.jsr166e-1.0.0.jar:/opt/mesosphere/bin/../lib/com.twitter.common.zookeeper.group-0.0.82.jar:/opt/mesosphere/bin/../lib/com.twitter.common.zookeeper.client-0.0.70.jar:/opt/mesosphere/bin/../lib/com.twitter.common.zookeeper.candidate-0.0.76.jar:/opt/mesosphere/bin/../lib/com.twitter.common.util-system-mocks-0.0.89.jar:/opt/mesosphere/bin/../lib/com.twitter.common.util-sampler-0.0.67.jar:/opt/mesosphere/bin/../lib/com.twitter.common.util-executor-service-shutdown-0.0.58.jar:/opt/mesosphere/bin/../lib/com.twitter.common.util-0.0.110.jar:/opt/mesosphere/bin/../lib/com.twitter.common.stats-provider-0.0.78.jar:/opt/mesosphere/bin/../lib/com.twitter.common.stats-0.0.104.jar:/opt/mesosphere/bin/../lib/com.twitter.common.stat-registry-0.0.44.jar:/opt/mesosphere/bin/../lib/com.twitter.common.stat-0.0.56.jar:/opt/mesosphere/bin/../lib/com.twitter.common.quantity-0.0.86.jar:/opt/mesosphere/bin/../lib/com.twitter.common.net-util-0.0.89.jar:/opt/mesosphere/bin/../lib/com.twitter.common.jdk-logging-0.0.68.jar:/opt/mesosphere/bin/../lib/com.twitter.common.collections-0.0.90.jar:/opt/mesosphere/bin/../lib/com.twitter.common.base-0.0.101.jar:/opt/mesosphere/bin/../lib/com.twitter.common.application-action-0.0.81.jar:/opt/mesosphere/bin/../lib/com.thoughtworks.paranamer.paranamer-2.8.jar:/opt/mesosphere/bin/../lib/com.sun.jersey.jersey-servlet-1.18.1.jar:/opt/mesosphere/bin/../lib/com.sun.jersey.jersey-server-1.18.1.jar:/opt/mesosphere/bin/../lib/com.sun.jersey.jersey-core-1.18.1.jar:/opt/mesosphere/bin/../lib/com.sun.jersey.contribs.jersey-multipart-1.18.1.jar:/opt/mesosphere/bin/../lib/com.sun.jersey.contribs.jersey-guice-1.18.1.jar:/opt/mesosphere/bin/../lib/com.softwaremill.macwire.util_2.11-2.2.2.jar:/opt/mesosphere/bin/../lib/com.softwaremill.macwire.proxy_2.11-2.2.2.jar:/opt/mesosphere/bin/../lib/com.softwaremill.common.tagging_2.11-1.0.0.jar:/opt/mesosphere/bin/../lib/commons-logging.commons-logging-1.2.jar:/opt/mesosphere/bin/../lib/commons-lang.commons-lang-2.6.jar:/opt/mesosphere/bin/../lib/commons-collections.commons-collections-3.2.2.jar:/opt/mesosphere/bin/../lib/commons-codec.commons-codec-1.10.jar:/opt/mesosphere/bin/../lib/commons-cli.commons-cli-1.4.jar:/opt/mesosphere/bin/../lib/commons-beanutils.commons-beanutils-1.9.2.jar:/opt/mesosphere/bin/../lib/com.google.protobuf.protobuf-java-3.3.0.jar:/opt/mesosphere/bin/../lib/com.google.inject.guice-4.0.jar:/opt/mesosphere/bin/../lib/com.google.inject.extensions.guice-servlet-3.0.jar:/opt/mesosphere/bin/../lib/com.google.inject.extensions.guice-assistedinject-4.0.jar:/opt/mesosphere/bin/../lib/com.google.guava.guava-19.0.jar:/opt/mesosphere/bin/../lib/com.googlecode.libphonenumber.libphonenumber-6.2.jar:/opt/mesosphere/bin/../lib/com.google.code.findbugs.jsr305-3.0.1.jar:/opt/mesosphere/bin/../lib/com.github.spullara.mustache.java.compiler-0.9.0.jar:/opt/mesosphere/bin/../lib/com.github.nscala-time.nscala-time_2.11-2.2.0.jar:/opt/mesosphere/bin/../lib/com.github.fge.uri-template-0.9.jar:/opt/mesosphere/bin/../lib/com.github.fge.msg-simple-1.1.jar:/opt/mesosphere/bin/../lib/com.github.fge.json-schema-validator-2.2.6.jar:/opt/mesosphere/bin/../lib/com.github.fge.json-schema-core-1.2.5.jar:/opt/mesosphere/bin/../lib/com.github.fge.jackson-coreutils-1.8.jar:/opt/mesosphere/bin/../lib/com.github.fge.btf-1.2.jar:/opt/mesosphere/bin/../lib/com.getsentry.raven.raven-logback-7.7.0.jar:/opt/mesosphere/bin/../lib/com.getsentry.raven.raven-7.7.0.jar:/opt/mesosphere/bin/../lib/com.fasterxml.uuid.java-uuid-generator-3.1.4.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.module.jackson-module-scala_2.11-2.7.2.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.module.jackson-module-paranamer-2.7.2.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.module.jackson-module-jaxb-annotations-2.7.2.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.module.jackson-module-afterburner-2.6.3.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider-2.7.2.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.jaxrs.jackson-jaxrs-base-2.7.2.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.datatype.jackson-datatype-jsr310-2.7.8.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.datatype.jackson-datatype-joda-2.6.3.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.datatype.jackson-datatype-jdk8-2.7.8.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.datatype.jackson-datatype-jdk7-2.6.3.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.datatype.jackson-datatype-guava-2.6.3.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.core.jackson-databind-2.7.8.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.core.jackson-core-2.7.8.jar:/opt/mesosphere/bin/../lib/com.fasterxml.jackson.core.jackson-annotations-2.7.8.jar:/opt/mesosphere/bin/../lib/com.fasterxml.classmate-1.1.0.jar:/opt/mesosphere/bin/../lib/com.eclipsesource.play-json-schema-validator_2.11-0.7.0.jar:/opt/mesosphere/bin/../lib/com.datadoghq.java-dogstatsd-client-2.1.1.jar:/opt/mesosphere/bin/../lib/com.cronutils.cron-utils-6.0.4.jar:/opt/mesosphere/bin/../lib/ch.qos.logback.logback-core-1.2.3.jar:/opt/mesosphere/bin/../lib/ch.qos.logback.logback-classic-1.2.3.jar:/opt/mesosphere/bin/../lib/aopalliance.aopalliance-1.0.jar:/opt/mesosphere/bin/../zookeeper-*.jar:/opt/mesosphere/bin/../src/java/lib/*.jar:/opt/mesosphere/bin/../etc/zookeeper: (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:java.library.path=/opt/mesosphere/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:java.io.tmpdir=/tmp (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:java.compiler=<NA> (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:os.name=Linux (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:os.arch=amd64 (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:os.version=4.4.0-130-generic (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:user.name=root (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:user.home=/root (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:user.dir=/ (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:os.memory.free=900MB (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:os.memory.max=14318MB (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,642] INFO Client environment:os.memory.total=966MB (org.apache.zookeeper.ZooKeeper:main)
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,643] INFO Initiating client connection, connectString=zk-1.zk:2181,zk-2.zk:2181,zk-3.zk:2181,zk-4.zk:2181,zk-5.zk:2181 sessionTimeout=30000 watcher=org.apache.zookeeper.ZooKeeperMain$MyWatcher@1a3869f4 (org.apache.zookeeper.ZooKeeper:main)
-2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,701] INFO Opening socket connection to server zk-3.zk/xxx.17.0.2:2181. Will not attempt to authenticate using SASL (unknown error) (org.apache.zookeeper.ClientCnxn:main-SendThread(zk-3.zk:2181))
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,842] INFO Socket connection established to zk-3.zk/xxx.17.0.2:2181, initiating session (org.apache.zookeeper.ClientCnxn:main-SendThread(zk-3.zk:2181))
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | [2018-07-27 19:59:31,862] INFO Session establishment complete on server zk-3.zk/xxx.17.0.2:2181, sessionid = 0x164dd26d3880024, negotiated timeout = 30000 (org.apache.zookeeper.ClientCnxn:main-SendThread(zk-3.zk:2181))
2018-07-27 15:59:31 DEBUG    dcos_e2e._common |
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | WATCHER::
2018-07-27 15:59:31 DEBUG    dcos_e2e._common |
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | WatchedEvent state:SyncConnected type:None path:null
2018-07-27 15:59:31 DEBUG    dcos_e2e._common | Node already exists<EMAIL_ADDRESS>Traceback (most recent call last):
  File "/home/linuxbrew/.linuxbrew/bin/dcos-docker", line 11, in <module>
    load_entry_point('DCOS-E2E==2<IP_ADDRESS>', 'console_scripts', 'dcos-docker')()
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/cli/dcos_docker/commands/wait.py", line 91, in wait
    cluster_containers.cluster.wait_for_dcos_oss(http_checks=http_checks)
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/dcos_e2e/cluster.py", line 228, in wait_for_dcos_oss
    api_session.wait_for_dcos()  # type: ignore
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/dcos_e2e/_vendor/dcos_test_utils/dcos_api.py", line 430, in wait_for_dcos
    self.login_default_user()
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/retrying.py", line 49, in wrapped_f
    return Retrying(*dargs, **dkw).call(f, *args, **kw)
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/retrying.py", line 212, in call
    raise attempt.get()
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/six.py", line 693, in reraise
    raise value
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/dcos_e2e/_vendor/dcos_test_utils/dcos_api.py", line 225, in login_default_user
    r.raise_for_status()
  File "/home/linuxbrew/.linuxbrew/Cellar/dcose2e/2<IP_ADDRESS>/libexec/lib/python3.7/site-packages/requests/models.py", line 939, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http://xxx.17.0.2/acs/api/v1/auth/login

Please can you try this on a new DC/OS Docker cluster without the wait command, but instead waiting 15 minutes.

Yes, I have already tried this.

Please can you try without the --one-master-host-port-map 80:80 and see if the wait command works.

I get the same error as previously posted.

I'm not sure where the xxx.17.0.2 is coming from.. The IP address of my "node", or the VM that I'm using, is xxx.22.11.99. Thus, localhost is also xxx.22.11.99

This is just overloaded terminology.
The "node" I refer to is a DC/OS node.
That means that the node IP address is the IP address of a Docker container, by default on the docker0 network.
This is <IP_ADDRESS> in this case (no need to xxxthe 172 out, it is the same for everybody).
The "host" I referred to is the VM on xxx.22.11.99.
When everything is working well, by default, you should be able to access http://<IP_ADDRESS> from the host in a browser.
When everything is working well, once you have used --one-master-host-port-map 80:80, you should be able to access localhost:80 from the host in a browser.

Thank you for the updated information - it will help me to dig further into this.

Update: So, I tried using xQuartz and ssh'ing with ssh -Y to enable graphical forwarding. This way I was able to get to the login page through the <IP_ADDRESS> in Firefox when I ran dcos-docker web -c default.... I was fully expecting this to work; however, I'm still running into Unable to login to your DC/OS cluster. Clusters must be connected to the internet.

At that point, the only difference has been running on a Mac versus linux and the linux is behind firewalls... but everything we've checked is open.

@timaa2k Thank you! So, the first command you gave got me into the web UI; however, maybe there is possible an internet issue because the services in the catalog are not displaying.

Let me dig into your second command and other questions...

I am able to use ping/curl inside the node, successfully connecting to the internet.

We have now discovered that we had a different understanding of "node".
I was talking about the DC/OS node, not the host VM.
To test this, please try to ping from a node with: dcos-docker run "ping -c 3 www.google.com".

My bad. Yes, there does seem to be an issue with internet connectivity inside the node.
$ dcos-docker run "ping -c 3 www.google.com"
ping: www.google.com: Name or service not known

@timaa2k I'll try your second command later today; however to answer your questions:

Which version of DC/OS and Ubuntu are you using, what kind of VM is it?
Are your running this on a cloud provider?

I'm using DC/OS docker, so whichever version is in this latest master branch.
Ubuntu 16.04.3 LTS
I'm not sure what you mean on the kind..It's a full virtualization VM created by OpenStack.
On-premise OpenStack

Interesting.
I will consider how to best narrow down the issue.
In summary we have:

Start an alpine container <- Internet works inside the container
Start a DC/OS E2E CentOS container + Install DC/OS < Internet does not work inside the container

What I'd like to do is rule DC/OS out of the equation.
If I'm right, DC/OS has nothing to do with this, and then we can look into what it is about the base containers that is causing the issue.
Please give us some time to consider how best to do that.
@timaa2k has suggested that ping: www.google.com: Name or service not known may be a DNS issue. We will look further into this.

@adamtheturtle @timaa2k Thank you all so much! You have no idea how excited we are to put this to use.

Start a DC/OS E2E CentOS container + Install DC/OS < Internet does not work inside the container

Except, I am able to run through the Google/Github logins. I would be surprised that I was able to go through the entire google authentication process (they even texted me a code) without internet connection. Or, does this internet connection come from the host instead of the node?

Hey @Bowiemb, I suspect that the output ping: www.google.com: Name or service not known indicates a DNS issue. dcos-docker configures DC/OS by default so that it uses the <IP_ADDRESS> DNS resolver provided by Google. It may very well be that your operator doesn't allow this e.g. it uses a custom DNS resolver. In order to make sure whether that's the case please run the following command:
dig @<IP_ADDRESS> -p 53 www.google.com

@timaa2k Maybe that's the issue... We had to use our own DNS resolvers when we were using the ansible playbook based on the advanced custom install guide.
cades@michael-b-dcos:~$ dig @<IP_ADDRESS> -p 53 www.google.com

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @<IP_ADDRESS> -p 53 www.google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

Jackpot! You can supply your custom DNS server e.g. <IP_ADDRESS> into the --extra-config like so:
dcos-docker create /tmp/dcos_generate_config.sh --extra-config <(echo "resolvers: ['<IP_ADDRESS>']")

What if we have two? Can I supply, e.g ... "resolvers: ['<IP_ADDRESS>', '<IP_ADDRESS>']")

@Bowiemb Yes

Yes that should work. However the safest way is to create a custom-config.yaml file:
resolvers:
- <IP_ADDRESS>
- <IP_ADDRESS>

This could then be passed as --extra-config=./custom-config.yaml
For all the configuration parameters please refer to the documentation:
https://docs.mesosphere.com/1.11/installing/oss/custom/configuration/configuration-parameters/#resolvers

@timaa2k I ran your second command sudo ssh -fNL <IP_ADDRESS>:80:<IP_ADDRESS>:80<EMAIL_ADDRESS>however, I'm still running into the original error.
Also, I've tried dcos-docker create /tmp/dcos_generate_config.sh --extra-config <(echo "resolvers: ['xxx.xx.xx.xx']")
However, I'm still running into the same issue, Unable to connect ... clusters must be connected to the internet.
Maybe we need to trouble shoot this DNS issue internally. They've said that Google resolvers are not guaranteed here, so we have to use our resolvers but obviously it's causing some kind of issue.

However... why would it work locally on my laptop? I'm still connected to the same internet with my MacBook machine as I am the linux VM machine... hmmm

I'm not sure about the above.
Please can you try with your internal DNS troubleshooting and let us know what you find?

@adamtheturtle Yes, sir. We're working on that now. Looks like my hostnames were not added to our DNS servers after all. We've put in a request for them to be added. So, I hope that will be today, and that this fixes our issue. I'll keep you updated!

@adamtheturtle Apologies for the delay in posting a brief and closing the issue.
For us, the issue came down to using the correct resolvers. In our environment, we have a few different categories of resolvers varying in security. The resolvers we thought were supposed to work actually didn't work for our specific cluster environment.
In order to trouble shoot this, we tried many commands, but this command is what hits the nail on the head:
dig @[resolver] www.google.com -> If this fails, then your resolver most likely does not work for your specific environment. However, if this does work, then make sure to plug this specific resolver into the extra configs.
Also, 'cat /etc/resolv.confwill tell you what DNS resolver your host is using. This resolver should also work when you plug it into thedig` command.
As a side note: If you're having DNS issues with DCOS proper. Follow this step as well; however, if you've created a cluster, most likely, the hostnames of your clusters won't be added to your internal DNS server. Simply add the hostnames and IP addresses to the /etc/host file of every single node in the cluster. DCOS will read the host file before checking the DNS.

Thank you @Bowiemb and no problem!
We will add a check that would have made this easy to find out.

@adamtheturtle Yes, I didn't know a whole lot about networking when I ran into the issue.. but, hey, at least I learned something. Thanks for all the help!

Hello @alenkacz @Bowiemb having issue suddenly while accesing dcos ui what would be the cause can you pls suggest us

Note:- no made changes any things suddenly that issue got appeare not able to login @adamtheturtle @gpaul


Memory Utilization Concerns in Envoy Router Deployment

Description:
We are deploying Envoy router in Azure AKS cluster with the following memory and CPU requisites
```
resources:
  requests:
    memory: "500Mi"
    cpu: "2000m"
  limits:
    memory: "500Mi"
    cpu: "2000m"
```

As part of our performance validation, which involves subjecting the system to a load of 1000 concurrent users, each transmitting a payload of 100Kib. During this performance test, the router's memory consumption surges beyond the specified limits. Consequently, Kubernetes intervenes by terminating the respective pod, accompanied by an "Out Of Memory (OOM) Killed" message.
This is the config_dump that the router is using: config_dump.txt
Could you please advise on this behavior?

cc: @htuch

Lots of things that are potentially memory intensive going on, including a bunch of route rules with regexes (some used where literals would serve better), ext_authz and medium-large payloads being potentially buffered. Hard to say what is eating the memory without a heap profile. CC @KBaichoo

+1 on the need for a profile. See https://github.com/envoyproxy/envoy/blob/main/bazel/PPROF.md for profiling


Deployment

Deployment
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website using the URL,
THEN I can access my website from any browser

The page is deployed: https://ellysaschottler.github.io/prework-study-guide/


Replace phantomjs with firefox

This gets the liveserver/splinter/selenium based tests working again on TravisCI.
Did add a python 3.6 test run, just to show it can run without failures.
The 3.5 run shows 1 error, looks like dictionary/hash ordering problem in the test itself, so unrelated to this pull requests change (better fixed separately).

Amazing


Fix width when using images within selectlist

My terminal is borked so you'll have to check the solution, but I just did what you suggested in the issue thread #1463

Please ensure that this fix is actual and not probable.  Once you're sure this is the fix, we'll review it.

hold until full validation as suggested by woodward above

Selectlist resizes vertically as well as horizontally. @jamin-hall is this desired? Or should it be vertically static?

Needs some vertical alignment love.


Added tagging

I added support for tags. Tags can can be set the client level, in which case those tags will be applied to all metrics. Alternatively, tags can also be set when recording metrics, in which case the tags will only be added to the metrics being recorded.

Any reason why this was not merged?


fix(docs): npm install instructions

-d is a different flag not related to dev dependency, the proper flag would be -D, but because of this confusion it's better not to use flag shorthands in instructions altogether.

Thanks!


Improve time series data storage options

Originally: "Telemetry db rollups"
@chewbranca:

Storing time series data in CouchDB can incur a lot of overhead when each data point is stored in a doc. One common approach to solving this problem is rolling up data, for instance, if you're storing a doc with metrics data every minute, you could roll up the docs for each minute into a single doc, then do the same for hours, or days, or etc. Right now this is a manual process that needs to be done in the app layer, rather than a core feature of the database.

Might be something a PSE could deal with?

If the doc becomes large let us say 1 GB or more then it could make sense to handle that big doc in a special way such that new data is appended in a way that does not require the whole 1 GB to be read in and written again.
[A perhaps "crazy" idea could be to utilize (allow as an option in configuration) some existing database to handle documents that become big e.g. sqlite3 that includes the whole database in a single file and allows up to 140 terra bytes of data.]

With the move to FoundationDB,

Millions of writes/s
Perhaps that link provides some insights about the time series possibilities with FoundationDB.


Only certain key input combinations are not recognized "shift+cmd+["

Type: Bug
If you type "shift+cmd+[", VSCode will not recognize the input.
By the way, "shift+cmd+[" is recognized." shift+cmd" and "[" are also recognized.
Both Apple's built-in keyboard (Japanese) and external keyboard (English) are not recognized as well.
The environment is as follows.
Software:
System Software Overview:

  System Version: macOS 14.3 (23D56)
  Kernel Version: Darwin 23.3.0
  Boot Volume: Macintosh HD
  Boot Mode: Normal
  Computer Name: MacBook Pro
  User Name: user (user)
  Secure Virtual Memory: Enabled
  System Integrity Protection: Enabled
  Time since boot: 1時間 45分

Hardware:
Hardware Overview:

  Model Name: MacBook Pro
  Model Identifier: MacBookPro16,2
  Processor Name: Quad-Core Intel Core i7
  Processor Speed: 2.3 GHz
  Number of Processors: 1
  Total Number of Cores: 4
  L2 Cache (per Core): 512 KB
  L3 Cache: 8 MB
  Hyper-Threading Technology: Enabled
  Memory: 32 GB
  System Firmware Version: 2<IP_ADDRESS>.1 (iBridge: 21.16.3049.0.0,0)
  OS Loader Version: 580~1337

VS Code version: Code 1.85.2 (Universal) (8b3775030ed1a69b13e4f4c628c612102e30a681, 2024-01-18T06:40:32.531Z)
OS version: Darwin x64 22.6.0
Modes:

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I am using VS Code 1.86.0 and this is happening.
Version: 1.86.0 (Universal)
Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937
Date: 2024-01-31T10:29:15.765Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 23.3.0

When I type "shift+cmd+[" it recognizes it as "shift+cmd".
Here is a video from that time.

Thank you.

What if you instead write cmd+shift+[BracketLeft]?

@starball5

What if you instead write cmd+shift+[BracketLeft]?

The above was identified as cmd+shift+].

cmd+shift+[BracketLeft] -> cmd+shift+]
cmd+shift+] -> cmd+shift+[

I understood.
Also I seem to have missed the following.
https://github.com/microsoft/vscode/issues/136934
Thanks.


Fix encoding UTF-8 by using an actual encoder/decoder

Hopefully this doesn't make performance too much worse but it's definitely more reliable
Bump version to 3.0.9-figura
Bug report (4P5) https://discord.com/channels/1129805506354085959/1321647343925198889

why did luaj even use it's own thing in the first place???


adminService annotations and labels not working

adminService annotation and label are not present on the created service for admin server.
adminServer:
  serverStartState: "RUNNING"
  adminService:
    annotations:
      test: test
    labels:
      test: test

kubectl describe service test-domain-admin-server:
Name:              test-domain-admin-server
Namespace:         default
Labels:            serviceType=SERVER
                   weblogic.createdByOperator=true
                   weblogic.domainName=test-domain
                   weblogic.domainUID=test-domain
                   weblogic.serverName=admin-server
Annotations:       service.alpha.kubernetes.io/tolerate-unready-endpoints: true
                   weblogic.sha256: 7e7e157bb92df685363fea3964bc80f1720094ba7e2796747af844709390c232
Selector:          weblogic.createdByOperator=true,weblogic.domainUID=test-domain,weblogic.serverName=admin-server
Type:              ClusterIP
IP:                None
Port:              default-secure  7002/TCP
TargetPort:        7002/TCP
Endpoints:         <IP_ADDRESS>:7002
Session Affinity:  None
Events:            <none>

serverService and clusterService is ok.
weblogic operator: 3.0.2
wewblogic base image: store/oracle/weblogic:<IP_ADDRESS>-dev-200117

Definitely looks like a bug.
@csegedicsaba Do you know if this is till a problem? (It's certainly OK to respond with "I don't know".)
@rjeberhard Any thoughts?

Assigned to Ryan for triage...

I've verified that this is a bug. I'll get someone to fix it.

[Replacing my original response] The spec.adminServer element has two different children related to services: adminService and serverService. If you want labels on the admin server's ClusterIP service then you need to use spec.adminServer.serverService.labels similarly to what you would do for cluster members. The labels and annotations under adminService are related to the second, optional NodePort service that the operator can create for an admin server channel.

I believed that I had tried this earlier and found that I couldn't reproduce the failure. I just tried it also didn't work for me. I'll have someone take another look.

Fixed in 3.2.2.


[5.2] Use class preloader 2.x

Class preloader 2.x no longer requires us to hackyly run a console command within the code.

This produces the same output as the 1.x version? Did you compare the output files?

This produces the same output as the 1.x version? Did you compare the output files?

It should do. My tests in the class preloader package pass before and after.

Did you compare the output files?

I haven't checked the output within the context of laravel.

Let's try to check the output in regards to Laravel and compare them.

Sure, class preloader 2.x is still a moving target. I'll check back here in 2 days or so once I'm happy with class preloader 2.x.

Will resend this later today. Want to do some other stuff at the same time. :)


Enable pulseaudio device names

Pass the device name to the pulseaudio backend if --device was specified.

Fixes #207
?

@ashthespy: yes, it fixes #207.

I don't have access to a linux box, so can't test - @kaymes if it looks/works fine for you will go ahead and merge it..

It works for me.


chore: template fixes

Pull Request Checklist

[ ] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR
[ ] Pre-Commit Checks were ran and passed
[ ] Tests were ran and passed

Description
Some surface-level fixes for the template project.
Close Issue(s)

Current codespell linter error is coming from https://github.com/pypa/setuptools_scm/issues/905


Replace RawGit URLs

RawGit is dead, there's a similar service. RIP RawGit.

Anyone here?

Oops.. It might be my ISP blocking rawgit's IP addresses in an attempt to ban Telegram. I thought that rawgit was dead 😅


One box: Add search like code snippets

Part of AI-205
This PR

Adds a search file content code snippets block; it later will be used for search results within chat in one-box mode.
Adds preview button to context item link which renders highlighted code snippet block (originally this PR was only about code snippet for one box, but I've found having code snippet preview for link very useful, links are usually very long and you don't remember which file it was, helped me to avoid opening a lot of tabs by checking just preview blocks)

Todo

[x] Add an unhighlighted text block
[x] Add highlights support
[x] Add demo
[x] Align colors for different vscode themes

Test plan

CI is green
Check storybook demo
Run VSCode (or Cody Web) check that you can see preview code blocks next to file context files

Changelog

@thenamankumar I still need to go through colors design tokens but the logic is ready for the review

@thenamankumar I finished the color token work and also supported highlights file fetching in this PR as well. This PR can and probably should go independently from https://github.com/sourcegraph/cody/pull/5199
As soon as this is merged and code blocks will be on main we can easily add them for search mode results.

Update from meeting with @thenamankumar

We will hide the Preview button behind the feature flag for now since we don't won't introduce new unpolished yet feature to the standard context items
We will bring this back as soon as we get more high-fidelity designs  (after one box V0 PR is merged)


[Rocio] Hackathon and Homework Week 01

Hackathon Week 01
Output example:
Static + Dynamic Worlds

Static + Standing point = water (No continent found)

Week01 Homework
Days 1, 3 and 4. I'll submit the completet file through the 1MWTT System
Output example:

You’ve done a fantastic job on this hackathon challenge. I really love that you print out such a cool looking world, that’s so fun for the user!
Your error checking of the user input for the random world generator is very well written. Well done on spotting the potential problem before it occurred.
If you consider the context of this challenge further you’ll see that the goal is to find the 2 largest continents for people to play on, so you could level up your solution by searching for more continents after counting the first one. You could then tell the user which continents are the largest for them to choose from.
Your function using recursion to implement the boundary fill algorithm is very clearly written and you’ve used comments to great effect which will make your code much easier to maintain in the future. It’s obvious how much hard work you’ve put into it so congratulations on doing a great job!

Hey @jesscrees
Thanks so much for your feedback. It feels so good. I did actually spend a lot of time working on this hackathon and I do want to upgrade it. I also would like to discuss with you (if possible) the edges issue. I'll try to find you in Discord. Once again, Thanks!!!


Only getting non-explicit search results

By default, the module seems to only respond with non-explicit search results (SafeSearch: moderate).
Is there a way to change this to SafeSearch: off ?

SafeSearch is a setting item of bing.com, which does not belong to the scope of bing_images module.
Seen more at https://support.microsoft.com/en-us/topic/turn-bing-safesearch-on-or-off-446ebfb8-becf-f035-9eea-b660e8420458

Hey!
I saw that feature in this related module,
https://github.com/gurugaurav/bing_image_downloader
On Tue, Jan 25, 2022, 7:11 AM Catch Zeng @.***> wrote:

SafeSearch is a setting item of bing.com, which does not belong to the
scope of bing_images module.
See more at
https://support.microsoft.com/en-us/topic/turn-bing-safesearch-on-or-off-446ebfb8-becf-f035-9eea-b660e8420458
—
Reply to this email directly, view it on GitHub
https://github.com/CatchZeng/bing_images/issues/4#issuecomment-1020722936,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI5NK46RQYHZV57N4CEY7VLUXX5WLANCNFSM5MV2QLHQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

You can upgrade bing_image to 0.2.2 and try extra_query_params.
from bing_images import bing

urls = bing.fetch_image_urls("cat",
limit=10,
file_type='png',
filters='+filterui:aspect-square+filterui:color2-bw',
extra_query_params='&adlt=off')
print("{} images.".format(len(urls)))
counter = 1
for url in urls:
    print("{}: {}".format(counter, url))
    counter += 1


use MT Broker for tests

Addresses https://github.com/knative/eventing/issues/3139

Proposed Changes

Use MT Channel Based Broker for tests since ChannelBasedBroker is being removed.

Release Note

- 🧽 Update or clean up current behavior
Use MT Channel Based Broker for testing.

Docs

/lgtm
/approve


How to init pictures in preview ?

How to init pictures in preview ? Example for 'edit' some item.

Did you find any solution? I'm also facing this problem. My problem is, I added the image but when I edit those images, I want to preview that.


Draw the annotations differently dependent on their type

You probably have that on your sheet allready but I wanted to add this for completeness.
As for now there are 4 different kind of annotations (rect, template, point, polygon) however as they are drawn on the image they all look very much alike.
I think the following ideas are related to this

Draw a point as a point (not as a small rectangle), also a point annotation should not be resizable
Draw the single nodes of a polygon, not only the bounding box

Greetings!

Done in v2.1.0. Should be added to VoTT 1.x soon.


Change picture on  Android

I recently downloaded the Android version from google-play. I'm using a tablet, Acer Iconia 710. What I could not find out, is how to change the picture? I'm able to rotate the default picture (colour bars) and I'm able to swich the mode and to send the default picture, but there is now function to change the picture. I also couldn't find any hint at the internet.
Thanks for any hint.

SSTVEncoder is not my app - it's my wife's: https://github.com/olgamiller/SSTVEncoder
Please contact her about issues with her app.
Ahmet

Thank you! At the given URL I finally found a solution, how to do it.


TailwindCSS instead Bootstrap?

How can we use TailwndCSS instead using bootsrap?

This is something you have to implement yourself.
For guidance look at the docs for tailwindcss (and I have a fork that uses tailwind that you can copy).


Add Documentation for Terraform 0.14

Description
The provided documentation shows the usage with Terraform Versions older than 0.14
Expected behavior
Add Documentation how to start things with 0.14
Environment
Terraform version:
0.14

Provider version:

OS:
Debian on Win10/WSL1
Configuration Files
terraform {
  required_providers {
    ionoscloud = {
      source = "ionos-cloud/ionoscloud"
      version = "~> 5.0.0"
    }
  }
}

provider "ionoscloud" {
  username = "$removed"
  password = "$removed"
}

How to Reproduce
Example Config results in an error like thios
terraform init

Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/ionoscloud versions matching "~> 5.0.0"...

Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider
hashicorp/ionoscloud: provider registry registry.terraform.io does not have a
provider named registry.terraform.io/hashicorp/ionoscloud

If you have just upgraded directly from Terraform v0.12 to Terraform v0.14
then please upgrade to Terraform v0.13 first and follow the upgrade guide for
that release, which might help you address this problem.

Error and Debug Output
Additional Notes
References

Hello @gewuerzgurke84,
I've tested on debian on win10/wsl2, native linux (ubuntu 20.04) and osx 11.1, with terraform 0.14.4 and 0.14.5 using the same config and it worked fine.
Below you can find the output I got. The main difference is that it looks up the module as ionos-cloud/ionoscloud and not hashicorp/ionoscloud. Perhaps there's some extra configuration or environment vars that are affecting your result?
terraform init

Initializing the backend...

Initializing provider plugins...
- Finding ionos-cloud/ionoscloud versions matching "~> 5.0.0"...
- Installing ionos-cloud/ionoscloud v5.0.4...
- Installed ionos-cloud/ionoscloud v5.0.4 (signed by a HashiCorp partner, key ID 2D2E9201D5B7747D)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/plugins/signing.html

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Hi @mflorin ,
I think you misunderstood:

The software obviously runs with Terraform 0.14
There is no public documentation with a working example how to get things running
There is no special config on my testing machine, fresh terraform 0.14 setup on Win10/WSL1/Debian Buster
This Repo: https://github.com/ionos-cloud/terraform-provider-ionoscloud shows this example:
provider "ionoscloud" { version = "~> 5.0.0" }
which results in

$ terraform init
Initializing the backend...
Initializing provider plugins...
- Finding hashicorp/ionoscloud versions matching "~> 5.0.0"...
Warning: Version constraints inside provider configuration blocks are deprecated
on example.tf line 2, in provider "ionoscloud":
2:   version = "~> 5.0.0"
Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider
hashicorp/ionoscloud: provider registry registry.terraform.io does not have a
provider named registry.terraform.io/hashicorp/ionoscloud
If you have just upgraded directly from Terraform v0.12 to Terraform v0.14
then please upgrade to Terraform v0.13 first and follow the upgrade guide for
that release, which might help you address this problem.

The official documentation page https://registry.terraform.io/providers/ionos-cloud/ionoscloud/latest/docs shows a similiar example as well (on Example Usage)

I think it would be helpful for new users to have a working example that shows them how to start with terraform and ionosCloud API: (I guess the required_providers block points to the correct source and that does the trick :) )
terraform {
required_providers {
ionoscloud = {
source = "ionos-cloud/ionoscloud"
version = "~> 5.0.0"
}
}
}
provider "ionoscloud" {
username = "$removed"
password = "$removed"
}
Best Regards

In the meantime it is fixed and dispplayed correctly in the repo and registry


ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave | Audio buffer has overflowed {} times

ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
I get this error (2 lines) when I start, it works for a while then freezes and I get errors
Audio buffer has overflowed 134452 times

this happened on an Raspberry pi 4, used the same mic on a pi 3b+ and i ran a day with no issue


[Bug] collect_env.py fails due to circular import

Prerequisite

[X] I have searched Issues and Discussions but cannot get the expected help.
[X] I have read the FAQ documentation but cannot get the expected help.
[X] The bug has not been fixed in the latest version (master) or latest version (3.x).

Task
I'm using the official example scripts/configs for the officially supported tasks/models/datasets.
Branch
3.x branch https://github.com/open-mmlab/mmdetection/tree/3.x
Environment
From pip freeze:
addict==2.4.0
certifi==2022.9.24
charset-normalizer==2.1.1
click==8.1.3
colorama==0.4.6
commonmark==0.9.1
contourpy==1.0.6
cycler==0.11.0
fonttools==4.38.0
idna==3.4
kiwisolver==1.4.4
Markdown==3.4.1
matplotlib==3.6.1
mmcv==2.0.0rc2
-e git+https://github.com/open-mmlab/mmdetection.git@3221ecf33885bcf185e1ea63ac72a861403d81b0#egg=mmdet
mmengine==0.2.0
model-index==0.1.11
numpy==1.23.4
opencv-python==<IP_ADDRESS>
openmim==0.3.2
ordered-set==4.1.0
packaging==21.3
pandas==1.5.1
Pillow==9.3.0
pycocotools==2.0.5
Pygments==2.13.0
pyparsing==3.0.9
python-dateutil==2.8.2
pytz==2022.5
PyYAML==6.0
requests==2.28.1
rich==12.6.0
six==1.16.0
tabulate==0.9.0
termcolor==2.1.0
terminaltables==3.1.10
torch==1.13.0+cpu
torchvision==0.14.0+cpu
typing_extensions==4.4.0
urllib3==1.26.12
yapf==0.32.0

Reproduces the problem - code sample
python mmdet/utils/collect_env.py

Reproduces the problem - command or script
python mmdet/utils/collect_env.py

Reproduces the problem - error message
Traceback (most recent call last):
  File "/home/franchesoni/mine/creations/phd/projects/current/iadet/mmdetection/mmdet/utils/collect_env.py", line 2, in <module>
    from mmengine.utils import get_git_hash
  File "/home/franchesoni/mine/creations/phd/projects/current/iadet/env_iadet/lib/python3.10/site-packages/mmengine/__init__.py", line 3, in <module>
    from .config import *
  File "/home/franchesoni/mine/creations/phd/projects/current/iadet/env_iadet/lib/python3.10/site-packages/mmengine/config/__init__.py", line 2, in <module>
    from .config import Config, ConfigDict, DictAction
  File "/home/franchesoni/mine/creations/phd/projects/current/iadet/env_iadet/lib/python3.10/site-packages/mmengine/config/config.py", line 15, in <module>
    from typing import Any, Optional, Sequence, Tuple, Union
  File "/home/franchesoni/mine/creations/phd/projects/current/iadet/mmdetection/mmdet/utils/typing.py", line 3, in <module>
    from typing import List, Optional, Sequence, Tuple, Union
ImportError: cannot import name 'List' from partially initialized module 'typing' (most likely due to a circular import) (/home/franchesoni/mine/creations/phd/projects/current/iadet/mmdetection/mmdet/utils/typing.py)

Additional information
The expected result is the information of the environment, not an error.
Although this might be my fault, I followed a pretty standard installation:
python -m venv env_iadet
source env_iadet/bin/activate
pip install --upgrade pip
pip3 install torch torchvision --extra-index-url https://download.pytorch.org/whl/cpu
pip install -U openmim
mim install mmengine
mim install "mmcv>=2.0.0rc1"
git clone https://github.com/open-mmlab/mmdetection.git -b 3.x
cd mmdetection
pip install -v -e .

resolved in #9265


[Scaling Efficiently: Insights from Pre-training and Finetuning Transformers] Some checkpoints seem to be incomplete or incorrectly uploaded

Hey @vanzytay,
Thanks a lot for uploading all of your newest T5 checkpoints to GCP.
It's really amazing that you guys are taking the time to make the weights available to the community. Especially, the smaller versions {small, mini, tiny} are extremely useful IMO.
I've started an automatic conversion of these checkpoints to Transformers (see: https://huggingface.co/NewT5/) to make them even more available. The idea is to convert them to all frameworks we offer: PyTorch, Tensorflow, and JAX and give them a bit more visibility - hope this is ok for you! Before releasing them we would move them to the Google org on the Hub.
The conversion is going well so far - however I've noticed the that the following checkpoints seem to be incomplete or missing:

https://console.cloud.google.com/storage/browser/scenic-bucket/scaling_explorer/scaling_explorer/bi_v1_lg_h8_l16_law_03-21-23-05 has no checkpoints

https://console.cloud.google.com/storage/browser/scenic-bucket/scaling_explorer/scaling_explorer/bi_v1_lg_h8_l32_law_03-21-23-06

https://console.cloud.google.com/storage/browser/scenic-bucket/scaling_explorer/scaling_explorer/bi_v1_3B_l28_law_04-04-11-05

For 1. there are no checkpoints at all.
For 2. & 3. it seems like only the checkpoints up to step 306000 are available - should I just take those for the conversion or are the 524288 ones available somewhere?

Hi!
First of all, thanks for all the effort! We really appreciate it.
For 1, I've double checked and found that we don't have a checkpoint for that. That folder was perhaps created by accident. So you can ignore (1).
For 2, 3, unfortunately the jobs might have been accidentally killed before they could finish pretraining and was only finished up till 300k steps. At a later time, we could retrain them. For now, it would be awesome if there is a way to mark them as 300k (or something similar).
Thanks a lot!

Awesome - thanks for the quick answer. One question - I'm having some problems with the "shared heads" SH checkpoints when converting them. There is not too much information in the paper about what "shared" means here exactly and how the model architecture differs exactly to the non-shared ones.
Does "shared heads" mean that each transformer block has the same q, v, k projection matrices or does it mean that in each bock, each head projection matrix is the same?

And SKV (tied key-values) means that key and value projection matrices are always tied, no?

Hey! I'll need to revisit how mesh did this again (I can't remember at this moment). Will get back in a bit. But from our results, both shared models didn't move the needle at all in terms of pareto optimality so I think they will also have limited practical utility. But for completeness I will get back to the thread soon.

@vanzytay - we've finalized the port of all model checkpoints except SH and SKV. We've also converted each checkpoint to PyTorch and JAX/Flax besides TF and added a model card. You can see all checkpoints here:
https://huggingface.co/NewT5
Do the model cards look good to you?
Also, do you have a table where one could retrieve the downstream performance of a specific checkpoint and the computational complexity by any chance? The graphs in the paper are super nice, but it's difficult to retrieve the exact numbers of a checkpoint. I think this could be very useful for the users :-)

Hey! @patrickvonplaten sorry for the delayed response. Awesome work! thanks a lot :) Model cards look excellent.
About the last question. Do you mean to release a table or spreadsheet of some sort that reproduce the results on the graphs in the paper? If so I can share that too, along with maybe a colab to play with it. Lmk if that would be helpful.
I didn't really have time to look at the shared configs (i trained them almost a year or so actually) yet. Will ping back when I get the time. Do let me know if there's also any issues along the way or requests that you think could help.

That sounds great - yes exactly I meant a spreadsheet with all the evaluation results and maybe also the computational complexity (speed). Think we could easily extract the important numbers for each model checkpoint and add it to the model card which should be very important information for people wondering which of the 160 checkpoints to use.
If you could share some kind of spreadsheet / table this would be super nice


Add interface to expose the mnemonic checksum

This adds a method Mnemonic::checksum which exposes the encoded checksum of a Mnemonic instance. This is useful for manual validation of mnemonic integrity and for informational purposes.

ACK


Readme update

@HughPH Cool, can we merge this PR?

Sure. I just changes the version number in Known Issues, I think that's all there is.


Small readme improvements for smart accounts

What is the purpose of the change
Doc improvements
Testing and Verifying
not needed
Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[ ] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[ ] Code comments?
[ ] N/A

Summary by CodeRabbit

Documentation

Renamed the module from authenticators to smart-account.
Updated the Track method documentation to reflect the new parameter requirements.
Added new content about the MessageFilter Authenticator and message pattern matching.

close in favour of https://github.com/osmosis-labs/osmosis/pull/8105


Project status - Tested?

Did you ever make/test these?
I have a project that requires a Teensy in Micromod format, just wondering if these could be fabbed cheaper than the 'official' ones?
This is the project: https://github.com/rosmo-robot/smartcar_shield/blob/master/README.md#smartcar-10-current

Yes, I made a couple of them.  The "official" ones are T4 based, mine are T3.1 based. If you want to save money I assume you'd need really high volume to compete with sparkFun's pricing.

Thanks, you are probably correct. Do you happen to remember how much the ones you made worked out to?

There is a link to a live costed BOM in the readme. IIRC it was about 15EUR when I did the build. I did the assmembly myself so I don't know what this would cost these days.

Thanks, will check the BOM


Improve errors with SCSS

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Branched from #26 and requesting merge back into #26.
checka11y.css and checka11y.min.css are autogenerated.
Implemented SCSS to allow for easier maintaining:

Installed stylelint-scss for SCSS linting
Separated each feature into it's own sub file
Udated README & CONTRIBUTING
Moved projects logos into their own logo directory
Created minified version of the stylesheet
Added npm scripts
Installed postcss-cli, autoprefixer and cssnano

Link(s)

https://www.npmjs.com/package/stylelint-scss
https://github.com/browserslist/browserslist

Screenshot(s)

Checklist:

[x] I have thoroughly read the CONTRIBUTING guidelines.
[x] I understand my pull request will be thoroughly reviewed at high detail.
[x] I understand the work in my pull request will only be available in the next version release of Checka11y.css and not in the current version release.
[x] I confirm the work in this pull request is valid according to my findings and is not something for anything personal.
[x] I have updated the README where and if applicable (still put an x if you have considered this but thought there was nothing to add or modify).
[x] I have added myself to the contributors section in package.json (still put an x if you have considered this but decided not to add yourself).
[x] I have checked I have not committed any accidental files.
[x] I have tested all the main modern browsers (I.e. Chrome, Firefox, Edge, Safari - please leave this unchecked if there were any browsers listed you could not test and list them in the help section with details why you couldn't test that browser)
[x] All new and existing a11y checks still work correctly (compare your local test/index.html to the test/index.html in the master branch).

Help

Couldn't install v10.x.x of Autoprefixer because it's not compatible with v8 of PostCSS, so had to downgrade to v9.8.6 of Autoprefixer, until they release a fix.

TODO: Remove styling from the component itself and only apply it to the error message.
@danspratling What's your recommendation with errors on void elements such as <img />?

@danspratling What's your recommendation with errors on void elements such as ?

What do you mean?

@danspratling What's your recommendation with errors on void elements such as ?
What do you mean?

We can't put an error message on an <img />, since you can't use ::after or ::before on it. You mentioned to me it's probably not a good idea putting the error styling (border/background/color/etc) on the component itself as it could conflict with already existing styles. Maybe that's not a better explanation 😅

Wouldn't that get solved by #35 anyway though? I would say it's a moot point given we already have an issue related to it.

I'm not explaining it well 😅

On Twitter, you said the error styling should only go on the content error and not the component itself.
Nevermind, we can change it later if needed 😉

Yeah, so in the above the ERROR text should have a border. This is fine.

But this is a bit much with the error wrapping around the content too, so it should probably be removed, because we can't guarantee that this content won't be styled and therefore other styling may accidentally overwrite this anyway (or just be mistaken as content styling).

I was just updating both branches with master. I'll do the other changes tonight, then we'll see if it's worth merging sooner or later. I'd rather it not mess around or confuse the Hacktoberfesters. 🙂

Hi @danspratling. I have:

Merged master
Added recently merged features to SCSS
Resolved above comments
Raised #52 for another day

😊


FileDialog file_selected signal does not work when exported on Android

Tested versions

Reproducible in 4.4.dev4

System information
Android 13 - Godot 4.4 dev 4 Motorola G 5g 2022
Issue description
My issue is when I use the Native FileDialog and select any file on my phone. The signal that checks if you selected any files never gets called. I doubled check to see if the signal is connected and it is, and on my windows it works perfectly fine.
The signal I'm talking about:

My code:

Steps to reproduce

Create a FileDialog
Check the "Use Native Dialog" to be on
Connect the file_selected signal to your script
Print the "path" parameter
Make sure "File Mode" is on "Open any"
Lastly, "Access" is ony FileSystem

That's it when you export your project to android and select any file it will not print anything.
Minimal reproduction project (MRP)
(https://github.com/ArtinGaming/Godot-4.4.dev4-FileDialog-Issue)

Make sure you have enabled Storage permissions in export settings and requested it in your app using OS.request_permissions().

Thanks a lot! That fixed it! Here is the code I used func _ready(): await OS.request_permissions() Have a great day!


Proposal: Warn for use of a symbol not declared in the same file or an explicitly included header

In C, if A.c #includes B.h, and B.c #includes C.h, then the symbols declared in C.h will be available in A.c. (Nope, this was a misconception. But indirect header dependencies are still a pest for compilation.) Depending on this behaviour makes locating definitions when reading source a potentially recursive process, as well as making compilation inefficient when abused on a large scale^1. My proposal is for a warning that would catch this behaviour, encouraging explicit #includes if a symbol is to be used.
This warning trips if a symbol is used which is not declared in the same file or in a header explicitly #included in the file. The symbol need not be defined in these, only declared; this means C projects written with best practices will compile the same way with no additional warnings.
- "Make headers standalone": over 80 headers don't build standalone and
   depend on various accidental indirect dependencies they gain through
   other headers, especially once headers get their unnecessary dependencies
   removed. So there's over 80 commits changing these headers.

I did not know about this option, I love it!


Initiate error reporting

Error:(4, 27) java: cannot access com.almasb.fxgl.app.GameApplication
Bad class file: /F:/mavenDownloads/com/github/almasb/fxgl/11.6/fxgl-11.6.jar!/com/almasb/fxgl/app/GameApplication.class
Class file has wrong version  55.0, Should be 52.0
Delete the file or make sure it is in the correct classpath subdirectory

@yanzhao77 Hi, it seems you are using 11.6 with Java 8. Either use 0.5.4 with Java 8, or use 11.6 with Java 11+. Class file has wrong version

@AlmasB yes.I`m is java JDK1.8,
but i Add to plugin The same mistake

maven-compiler-plugin
3.8.0

8

release needs to be to set to 11. The release configuration has been added later, so version 8 will not be supported.
Ultimately, if you need to use JDK8, you can only use FXGL 0.5.4.


Play video in reverse

Is there a simple way to play the video in reverse?
thanks

no, not at the moment. i don't think it's planned to add this either.
do you have a compelling reason you need to play 360 video in reverse?
/cc @jwerle

i cannot give away the details, but it would be useful in a game scenario
if you think it's possible, could you point me to the part of the code that would need to be changed?
thanks

@tunic you can emulate reverse playback with an animation frame loop and setting the current time with frame.time(frame.time() - someDeltaValue

Closing as this is not intended to be supported