IDEAStatica.Plugin missing entry points

Hello, I'm creating an IOM bridge (based on webinar https://www.youtube.com/watch?v=tl1SeyPxjQY) from our FE system to IDEA Statica using IDEA Statica OpenModel + IDEAStatica.Plugin, both downloaded from NuGet.
I run Win10 with .Net Framework 4.8, using Visual Studio 2019
The IOM part works fine (using IDEA Statica OpenModel).
However, the following entry points are not found in IDEAStatica.Plugin:
a) ConnHiddenClientFactory
b) ConnectionHiddenCheckClient
When I look in the IDEAStatica.Plugin version located in the IDEAStatica install dir (22.1) using Object Browser, the entry points are there, however it's linked to
System.ServiceModel, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089
which is not on my system.

Please advise.

System.ServiceModel belongs to .NET Framework 4.8
Try to get a better log using Fuslogvw.exe - see :
https://learn.microsoft.com/en-us/dotnet/framework/tools/fuslogvw-exe-assembly-binding-log-viewer

The app builds correctly (no errors), hence binds. The error message appears during run-time.
When using Fusion logger I can't set the custom log path (I'm running as Admin). But would FusionLog catch run-time errors?

I will uninstall/reinstall VS and start fresh. This is too weird!
I looked in the NuGet installation folder (C:\Users\osl.nuget\packages\ideastatica.plugin\<IP_ADDRESS>5\lib\net48) and the dll DOES contain the missing entry points, however, VS (2019) must stir up things during NuGet installation of this package, because those two entry points are missing (when using ObjectBrowser)...

try to run fuslog as Administrator
directory must exist on your disk

Hello again. Uninstalling/reinstalling VS 2019 fixed it!
Inexplicably...
Thanks for all help - so far:)


UNOMI-225: implement ssl communication support with ES7

Thanks for the contribution looks good to me

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/unomi-pr/84/


Conversion Lit GPT (Llama-2-7b-chat-hf) to original model

Hi! Thanks for the new commits on the issue #340 . I ran the code as you suggested, but got this error.
TypeError: copy_weights_llama() got multiple values for argument 'saver'
I tried with another checkpoint files but it is still the same. Please let me know what I should do. Thank you!

Thank you for raising this issue @solablue. This will be fixed in the linked PR.

Hi, thanks for the update. But still facing the error below.
Traceback (most recent call last):
  File "/content/lit-parrot/scripts/convert_lit_checkpoint.py", line 237, in <module>
    CLI(convert_lit_checkpoint, as_positional=False)
  File "/usr/local/lib/python3.10/dist-packages/jsonargparse/_cli.py", line 85, in CLI
    return _run_component(component, cfg_init)
  File "/usr/local/lib/python3.10/dist-packages/jsonargparse/_cli.py", line 147, in _run_component
    return component(**cfg)
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/content/lit-parrot/scripts/convert_lit_checkpoint.py", line 229, in convert_lit_checkpoint
    copy_fn(sd, lit_weights, saver=saver)
  File "/content/lit-parrot/scripts/convert_lit_checkpoint.py", line 135, in copy_weights_llama
    to_name = weight_map[from_name]
KeyError: 'transformer.h.{}.attn.gating_factor'

I think someone else on Discord is also facing the same issue.

Hi @solablue have you updated to the most recent commit on main?
I ask because I retrieved Llama-2-7b-chat-hf, converted it to Lit-GPT format, and then ran the following on the fix-347 branch and it was okay.
python3 scripts/convert_lit_checkpoint.py \
    --checkpoint_name lit_model.pth \
    --checkpoint_dir checkpoints/meta-llama/Llama-2-7b-chat-hf

opening a new issue for this

Hi, thanks for the update. But still facing the error below.
Traceback (most recent call last):
  File "/content/lit-parrot/scripts/convert_lit_checkpoint.py", line 237, in <module>
    CLI(convert_lit_checkpoint, as_positional=False)
  File "/usr/local/lib/python3.10/dist-packages/jsonargparse/_cli.py", line 85, in CLI
    return _run_component(component, cfg_init)
  File "/usr/local/lib/python3.10/dist-packages/jsonargparse/_cli.py", line 147, in _run_component
    return component(**cfg)
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/content/lit-parrot/scripts/convert_lit_checkpoint.py", line 229, in convert_lit_checkpoint
    copy_fn(sd, lit_weights, saver=saver)
  File "/content/lit-parrot/scripts/convert_lit_checkpoint.py", line 135, in copy_weights_llama
    to_name = weight_map[from_name]
KeyError: 'transformer.h.{}.attn.gating_factor'

I think someone else on Discord is also facing the same issue.


[QA] Control cookies directly from Cookie Analysis extension

🔎 QA
UI/UX 🐞  - Clear All Cookies and Delete cookie

[x] Improve the UX with Single cookie deletion in comparison to Application Tab

Expected Behavior
Actual Behavior

The expected behavior for the clear single cookie icon is that it should become active only when the user selects a specific row.Once a row is selected, subsequent clicks on the 'x' button should clear cookies sequentially
The current behavior of the clear single cookie icon does not align with the expected user experience.Currently, the user is required to click on a row first before the selected row can be cleared.

Please refer to the screencast below
https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/8bcb45c8-1be1-43d7-9424-614557c2848b

[ ] Please consider increasing the size of the icons for 'Clear Cookie' and 'Delete All Cookies'.

Expected Size -

[x] Please consider implementing a hover effect for the icons associated with 'Clear Cookie' and 'Delete All Cookies'.

https://github.com/rtCamp/ps-analysis-tool/assets/15173772/db1b68c3-25a1-473c-bb3a-06f087639749

[x] In the Application Tab, there is no pipe icon(|). Based on this observation, I believe we can replicate a similar UI for PS Tab as well.

[x] Update the tooltip text from 'Delete cookie' to 'Delete selected cookie' to provide users with a clear indication that they need to select a row before initiating the deletion process.

[x] Clear All Cookies Icon - This icon needs a visual indicator to show its functionality. At present, it may appear as if the icon is inactive or disabled.

Application Tab
PS Tab

Functional 🐞

[x] Clear All cookies - The extension throws an error when attempting to delete cookies, and the page is still loading.

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/4331ff7b-505b-4105-b448-f77ea03f3ed6

[ ] Inconsistency in Cookie Deletion Functionality

Removing a cookie from one table results in the removal of cookies from all tables.
Cookie Landing Page - displays 0 cookies, and the number of frames linked to cookies also shows 0.
Cookies Popup - The Cookie Jar count does not update after deleting a cookie, and clicking on the popup does not reveal the matrix with a count of 0.
The delete operation is not smooth enough in terms of UX. The multiple click on "Delete All cookies" are required to perform an operation.

Please refer to the visual attached below.

Screencast
Screenshot

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/e0f6af91-ec5c-4bc6-b178-0c22bdc4b306

[X] Unable to modify the cookie. It only allow to tap on the cookie but does not allow to modify the cookie.

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/6b05b933-91ca-4a73-9bba-7c90bc491571

[ ] Tab key accessibility for cookie modification is currently not working. This functionality should be implemented to enhance user experience.

[x] Issue with Search functionality - With the current branch (feat/cookie-modification), there seems to be an issue with the functionality of the cookie search. Kindly review the visual attached below for a comparison of the expected behavior versus the actual behavior.

PS: Left side window shows output from (feat/cookie-modification) and right side window shows latest stable V0.3.2
https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/a02ad68d-a8bf-443c-b6f4-105308d5b9a0

[x] Now, able to modify the cookie but 'Enter Key' is not allowed

[x] The hover effect show white color.

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/6714128b-4329-4b15-ae20-8cbde600c45b

[ ] There colors of the icons are not matching with Application Tab

[ ] Esc key is not working.

[ ] Discrepancies in single cookie deletion workflow in PSAT Extension compared to standard Application Tab

[!NOTE]
This feature is tested with codebase from feat/cookie-modification branch

The process of deleting a single cookie in the PSAT differs from the expected behavior outlined in the Application tab.

To delete a single cookie, the user should first select a specific row, at which point the delete single cookie icon becomes highlighted. By default the single delete cookie icon should be disabled.

Upon clicking the delete cookie icon, the targeted cookie is removed, and the subsequent cookie row is automatically selected. The selection of the next cookie depends on the user's previous choice.

For instance, if the user initially selected the very first cookie, after deletion, the second cookie is automatically chosen. The single cookie delete button remains in an enabled state.

Conversely, if the user selected the last cookie, the row automatically shifts to the second-to-last row after deletion, maintaining an enabled state for the single cookie delete button.

However, in the PSAT, none of the above criteria functions as described above. Notably, the row being deleted does not get highlighted, causing confusion for users as to which cookie was deleted.
Please refer to this visual -
https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/fbd88c73-e1e4-48a5-9008-1a58c14180f7

[ ] Single cookie delete - UX needs improvment - No clear distinction about the button is disabled by default. Needs UI/U improvement

Tab
Screenshot

Application Tan

PSAT Tab

[ ] For the frames which does not have any cookie - both delete buttons should be disabled

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/b7495b4a-2dd9-481b-965f-7d8074dbbe7d

[ ] Once all the cookies are deleted from any selected frame then single delete cookie and bulk delete cookie icons should get disabled

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/0247624c-7730-42ba-9e31-e920809ae02c

[ ] Selecting the blank row should disable the single cookie delete icon.

Tab
Screenshot

Application Tan

PSAT Tab

[ ] If the user keeps clicking on single cookie delete icon even after all the rows are deleted then clicking on empty row will throw an errors in console

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/602aa985-aae3-424b-9365-630095337031

[ ] Again the hover effect on enabled state is missing for single delete cookie

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/5eff1880-54c3-45a8-9393-fcf422303c69

@amovar18 Cookie Modification has been tested and will be able to test more scenarios once the edit cookie issue will be fixed.

@amovar18 There is a broken UI after the latest pull.

Screen case
Screenshot

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/742fd13c-f00f-4ae4-b989-ff432f3f4845

@amovar18

Discrepancies in single cookie deletion workflow in PSAT Extension compared to standard Application Tab

This is not completely fixed. The focus of the selected row is shifted to the last row.
https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/e64a8b1f-f4fd-4968-9f31-68fe093b2a60

If the user keeps clicking on single cookie delete icon even after all the rows are deleted then clicking on empty row will throw an errors in console

The error thrown is not related if you check the console properly. Its a past error I would suggest that if you were to report an error you clear the console and check if the error is being thrown.

Yes, I had cleared the console and it only generated after I click on empty table. I guess this would be automatically handled when we will disable the single cookie delete when there is no more rows to delete.

@amovar18

[ ]  Esc key is working now but PSAT Tab opens the DevTools' Console Tab also. The same behaviour is working smoothly with Application Tab.

https://github.com/GoogleChromeLabs/ps-analysis-tool/assets/15173772/7112d3ca-928d-4543-b467-1a712dec418b

@amovar18 Any update on subtask 2 under this?

As we are anticipating further updates to the implementation of https://github.com/GoogleChromeLabs/ps-analysis-tool/issues/20 feature, the issues reported here will not be valid. Closing this issue for now, and a new one will be created when https://github.com/GoogleChromeLabs/ps-analysis-tool/issues/20 is again ready for QA.


Override update branch with settings.yaml

Resolves #153.
You can now simply override or switch from the defined branch with your own by setting ~/.workspacer/settings.yaml with:
branch: stable
# or
branch: unstable

Edit:
Added none  as an option to disable auto-update. This would be useful for installing from scoop.

We already have an optional config file where you can write custom C# to change settings. Would it make more sense to just allow you to write a line of code in that file that overrides the update branch?

We already have an optional config file where you can write custom C# to change settings. Would it make more sense to just allow you to write a line of code in that file that overrides the update branch?

Makes sense.

Now you could do:
context.Branch = Branch.Stable;
// or
context.Branch = Branch.Unstable;
// or disable updates
context.Branch = Branch.None;

Closing this in favor of #156.


Experiment with different quickstarter structure

I think that the whole repo should be structured differently than it is right now. A lot of the repo should be moved to ods-core, and what is left should be really decoupled from opendevstack. In addition, users should have an easy way to add their own quickstarters.
To make some progress in this direction, I want to try out the following:
Create a new Rundeck job that is usable for all quickstarters. This Rundeck job requires a quickstarter_repository, a boilerplate_path and a ocp_template_path param (the last two being relative paths inside the repo). Since the provisioning app cannot set this at the moment, I will - for the sake of the experiment - not integrate this Rundeck job with the provisioning app.
This new Rundeck job will execute a predefined set of steps, as sketched below:

Clone the quickstarter_repository
Create a new folder and set correct permissions on it
Initialise (which is either the init.sh in boilerplate_path or, if that does not exist, a default one provided by ods-core/quickstarters-steps/init.sh)
Generate (which is either the generate.sh in boilerplate_path or, if that does not exist, a default one provided by ods-core/quickstarters-steps/generate.sh)
Copy files (which copies all files in boilerplate_path/files to the new folder
Render Jenkinsfile and sonar-project.properties if present
Process (which is either the process.sh in boilerplate_path or, if that does not exist, a default one provided by ods-core/quickstarters-steps/process.sh)
Create OCP resources (by applying the templates in ocp_template_path)
Initialise the git repository and push it

Each file such as init.sh, generate.sh, etc. will be called with a predefined set of environment variables (to ease writing custom scripts).
Advantages:

Quickstarters can be sourced from multiple repos, allowing orgs to point to their own
No Rundeck job needs to be created when new quickstarters are created. As a consequence, the Rundeck config can be moved to ods-core, along with all the default scripts and project templates etc.

When I have some time, I will experiment with an example Rundeck job that does this ...
FYI @rattermeyer @tjaeschke @clemensutschig @stitakis

The proposal sounds good to me. The de-coupling really makes sense.
The convention makes sense with respect to what we currently have learned about different project flavours.

massively related to opendevstack/ods-provisioning-app#98
my thought would be

to have the "main" CD project contain 1 master pipeline to create/delete a project - largely reusing what's done in
https://github.com/opendevstack/ods-project-quickstarters/blob/master/rundeck-jobs/openshift/create-projects.yaml - that requires a jenkins instance in CD - including a SA with self provisioner rights

have a pipeline "provision new components" in every project *-cd project - in order to piggy back on the *-cd jenkins SA's rights .. which would allow you to pass the quickstarter name, or a github.. location which contains a jenkins file to provision quickstarter specifics.

The open question for me is where to get the quickstarter list from ... (today it's a query against rundeck, namely in
https://github.com/opendevstack/ods-provisioning-app/blob/master/src/main/java/org/opendevstack/provision/services/RundeckAdapter.java#L226 which uses the group configured in https://github.com/opendevstack/ods-provisioning-app/blob/master/src/main/resources/application.properties#L74
The easiest way I guess is to create pipelines with a naming convention e.g. Quickstarter-* in the main CD project that the prov app could read... (oc get pipelines | grep ... ) or you configure it in the prov app - with paths?
@gerardcl  / @michaelsauter  @stitakis  - thoughts?

Very cool!
As dicussed, the quickstarter list needs to be known in some form or other by the provisioning app. However, this is something we want anyway, in order to point to e.g. private quickstarter repos.
The provisioning app would then give the Git repo and the Jenkinsfile path to the webhook proxy, which would create a pipeline, and run the steps defined in the Jenkinsfile. The prov-app also needs to pass the component name (to create the OCP resources and the BitBucket repo), and this is doable via args in the Jenkins strategy (webhook proxy needs to be extended, but is a simple addition).

Excellent!
The prov app could get the configuration of quickstarters location, etc... from:

from config file (ie. json file) added to the prov-app project as mentioned above
or from default config file located in a default git repo url
or something similar :-)

@kiwo Assigning you on this since you are working on it - even if the implementation might slightly differ from what was in here originally.


⚠ API - Lens has degraded performance

In 0ec4874, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 579 ms

Resolved: API - Lens performance has improved in acfcdb7 after 8 minutes.


docker 1.6.2: pull race condition eats dependent layers

Description of problem:
Multiple simultaneous docker pulls that depend on the same underlying layers will corrupt them.
I've created a simplified test case and steps to reproduce.
Both VirtualBox and EC2
How reproducible:
Reliably on the environments I've tested.  You may need a slower net connection, as the images must take enough to time to download that they overlap.
Steps to Reproduce:
docker ps -aq | xargs docker rm -f
docker images -q | xargs docker rmi
seq 1 25 | awk '{print "aaron42net/dockertest:app-"$0}' | xargs -n 1 -P 25 docker run

Actual Results:
FATA[0084] Error pulling image (app-15) from aaron42net/dockertest, Driver overlay failed to create image rootfs e8d7ddc9a499bd28ecdd5c12bf0b38ed3f247b46b10673fc5061f659f73740cc: lstat /var/lib/docker/overe8d7ddc9a499: Error downloading dependent layers

Expected Results:
Test apps running 25 times and printing "Hello, World!"
Additional info:
If you do them sequentially (change the "-P 25" to "-P 1"), it works fine.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

ping @stevvooe this looks very much like what you were describing in https://github.com/docker/docker/issues/9718#issuecomment-112518555. Possibly a dup of that one, but perhaps the repro case here can help you resolving the cause.
Thanks for reporting this, and providing a repro-case @aaron42net!

I see https://github.com/docker/docker/issues/9718 mentions DeviceMapper, which I don't use.  But I've hit this issue with both overlayfs and btrfs atop CoreOS 681.0.0, so I don't think it is specific to a filesystem.
I've worked around the issue by wrapping flock around my docker pulls to serialize them by adding the following to my Fleet units, which is suboptimal:
ExecStartPre=-/usr/bin/flock /home/core/pull.lock /usr/bin/timeout 5m /usr/bin/docker pull ...

It took me a few days of experimenting to reproduce cleanly, so I hope this helps.

Going by https://github.com/docker/docker/issues/9718#issuecomment-68762458 it's not related to a specific graph driver, so this issue could well be the same.

It took me a few days of experimenting to reproduce cleanly, so I hope this helps.

It sure doesn't hurt having a reproducible case :-), thanks so much :+1:

@aaron42net Thank you! This looks like a duplicate of #9718. Here is me "whining" about getting a reproduction: https://github.com/docker/docker/issues/9718#issuecomment-112518555. Now, we have no excuse but to fix this. ;)
A few questions:

How did you create the image originally? Was this created initially with 1.6.2?
If you recreate the image, can you reproduce this? (trying to eliminate v1/v2 cross-over problems).
Does it only happen with docker run or can you reproduce with docker push?

They were built on docker 1.6.2 on CoreOS 681.0.0 this morning, but I just noticed that I had a typo in the one of my layers that was depending on a private repo that might've been a few weeks old and built on docker 1.5.0.
After fixing the typo and re-pushing-the images all built on docker 1.6.2, I can no longer reproduce using the above steps.
I'm going to try building the base image again on 1.5.0 and pushing those, then building the upper layers on 1.6.2 and see if the problem comes back.

@aaron42net Interesting. I will be excited to hear your result. Thank you for the continuing thorough investigation.

Okay, so building on 1.6.2 is fine.  It's just that on my faster Mac on a faster 'net connection at work, I can't seem to reproduce the pull bug.
I updated the README.md in https://github.com/aaron42net/dockertest to match what I just did to build on Docker 1.6.2 on my work machine.  All of the Dockerfiles and such are in that repo, if you want to play with building your own. After doing that, I can reproduce on my home machine running Docker 1.6.2.
I have previously tried pull instead of run.  All of the pulls may finish, but trying to run them will often claim that /bin/bash is missing or similar.  The last time I looked at the list of missing files, the whole debian:jessie layer was missing.
Do you know how debian:jessie is built?  Is that on 1.5.0 or 1.6.2?

@aaron42net Actually, debian:jessie was the same image we had seen this issue with. We were not able reproduce the error when only pulling, but would generally encounter it on a run on a corrupt image without a pull.
debian:jessie was built with the automated builder for the official repositories. @cpuguy83 @tianon any idea here? If you're having trouble reproducing the issue now, I suspect the image has been updated and no longer has whatever conflict caused the original corruption.

The most recent build of debian:jessie was built on 1.6.0, and would've happened roughly 4 days ago (latest commit on https://github.com/docker-library/official-images/blob/master/library/debian).  This information should also be able to be scraped from the layer itself:
$ docker inspect -f '{{.Created}} - Docker {{.DockerVersion}}' debian:jessie
2015-06-15 22:44:39.555142548 +0000 UTC - Docker 1.6.0

What's reported here definitely sounds like a strange bug, though. :confused:

@tianon Oddly, that is around the time when this was no longer reproducible...

I am absolutely encountering this bug. I have a number of images built from the same base image, which is built from upstream ubuntu:12.04.
When my Mesos slaves start, they may pull several images, depending on the jobs they are handling. With newly-booted Mesos slaves (i.e. they have no images), I encounter this bug 100% of the time.
My internal registry is v2. No idea if the Ubuntu images are coming from v2, but I would expect so. I'm encountering this on 1.6.0, 1.6.2 and 1.7.0, and it is actually a complete showstopper bug.

@stevvooe I just rebuilt the aaron42net/dockertest images with the latest debian:jessie and I can still reproduce.

A dirty hack you can use is to "shim" Docker to do a lock before pulling. This is what I'm doing.
I create a shell script called docker earlier in $PATH (so it will be called before the actual Docker binary), with the following contents:
if [ "$1" == "pull" ]; then
  (
    flock 9 || exit 1
    /usr/bin/docker "$@"
  ) 9>/tmp/docker_pull_shim_lock
else
  exec /usr/bin/docker "$@"
fi

Now this will be invoked before the Docker binary. If the first argument is pull, then it takes a lock and does the pull; otherwise it simply replaces itself with the actual Docker binary.
A hack, yes, but necessary until this bug is triaged and fixed.

@andytinycat We know this is a nasty issue. We've added the 1.7.1 milestone and are working towards a fix.

@andytinycat @aaron42net
I have a patch that replicates the flock solution at an image granularity. This should prevent the image from getting corrupted but won't correct existing corrupted images. Inspection of that code shows a few other issues we need to address in that function (there is come variable shadowing @vbatts).
@aaron42net If you could build my branch and give it a try, it would be a big help. We are having trouble reliably reproducing and would feel better if we could get some validation on your end.
@dmcgowan PTAL

I've spun up an EC2 instance that's detached from the rest of my infrastructure, has ssh available globally, and has a new SSH key.  I'm happy to share it with you if you can tell me how to get you the key privately.
Alternatively, you can spin up an m3.large EC2 instance in us-east-1a using AMI ami-79ad4712, attach the 32G instance storage to /dev/xvdb and use this for user-data: https://www.die.net/tmp/82ffab2a7418a7b4/coreos-test.userdata
I did that and logged in and ran the following and it broke right away:
seq 1 25 | awk '{print "aaron42net/dockertest:app-"$0}' | xargs -n 1 -P 25 docker run

The patch posted by @stevvooe solved the issue in my testing. I used the testing process described by @aaron42net

@aaron42net We've built you a version with the patch. Please give it a try:
https://docs.google.com/a/docker.com/uc?authuser=0&id=0BxIgF_yUbnRkdjNCZXV2eWU0V1k&export=download

@stevvooe: I've dropped that image on to my test instance, written a replacement systemd unit to /etc/systemd/system/docker.service and run systemctl daemon-reload and systemctl restart docker and see the new one running in ps:
root       809 12.7  0.5 1307056 44796 ?       Ssl  20:21   0:58 /home/core/docker-1.7.1-pr14193 --daemon --host=fd://

I then ran seq 1 25 | awk '{print "aaron42net/dockertest:app-"$0}' | xargs -n 1 -P 25 docker run again and had the same result:
c7044d50a3f3: Error pulling image (app-16) from aaron42net/dockertest, endpoint: https://registry-1.docker.io/v1/, Driver overlay failed to create image rootfs a9dc0db39add6e28f009a128fe5efa4bdc021ee3b14dec3e6590b879ad339950: write /var/lib/docker/ovc
7044d50a3f3: Error pulling image (app-16) from aaron42net/dockertest, Driver overlay failed to create image rootfs a9dc0db39add6e28f009a128fe5efa4bdc021ee3b14dec3e6590b879ad339950: write /var/lib/docker/overlay/a9dc0db39add6e28f009a128fe5efa4bdc021ec1eb8b260132: Error downloading dependent layers

@aaron42net Did you clear out the images from /var/lib/docker before running the test? The PR does not correct existing corruption.

On Mon, 29 Jun 2015, Stephen Day wrote:

@aaron42net Did you clear out the images from /var/lib/docker before running the test? The PR does not correct existing corruption.

I did.  I also terminated the instance and re-created from a fresh instance.
Would running docker in debug mode help? How do I get you more information?
This is running on the instance that I can share the key to, if you want to
mess with it yourself.  If so, how do I get an ssh private key to you?
                                -- Aaron

(one race cleanup here -->  #14413 )

@aaron42net Not sure if this will change anything but give the 1.7.1 rc a try: https://test.docker.com/builds/Linux/x86_64/docker-1.7.1-rc1.
We may have a completely different root cause if this isn't working.


chore: Updated dev dependencies

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
282

Relevant Lines:
282

💛  - Coveralls


Add OSX builds

Fixes https://github.com/kinvolk/inspektor-gadget/issues/65

Hi @alban
I tried it and the make operation failled with the following logs:

Hi @fredleger,
According to your output, you are trying to build the Inspektor Gadget container image, to generate only the executable you run in your machine, you can use make kubectl-gadget-darwin-amd64. Please let me know if this works for you.

Maybe we could get make -C gadget-container build to run in docker containers, so that it would also be possible to build the "gadget" container image on OSX. I don't know how that works.
@fredleger could you also try to download the build artifact from this PR (https://github.com/kinvolk/inspektor-gadget/pull/73/checks) to check if the binary works on OSX?

Hello,
The build itself seems to be working (i don't have a Gadget daemon or pod running so i should test further).
2 things though:

The binary is unsigned which oblige to "hack" the osx security prefs. but i guess you can live with it
in my experience if you want to distribute it as a plugin integrating it in krew is a simple and good choice : https://github.com/kubernetes-sigs/krew

Thanks for building this i will give it a deeper try starting from now

@fredleger  thanks for testing.
@mauriciovasquezbernal ok for merging?
I think the issue with make -C gadget-container build on osx could be done later, at least the next release would have a binary for osx.
I agree about krew, there is an issue about it: https://github.com/kinvolk/inspektor-gadget/issues/30


show IP address in windows tile

display IP address of session along with session name in window title.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 12 May 2010 at 6:06

Closing this issue but all hope is not lost! We still want to help.
See: https://github.com/jimradford/superputty/wiki/Legacy-Imported-Issues on how to help us to help you!


Changing default export value type resets every inherited instance

Godot version:
3.2.3 stable
OS/device including version:
Linux
Issue description:
I imagine you are going to say this is as expected as it's changing internal data types, but it ends up losing all data without any warning.
Pretend you have a scene with a default export:
export var life_span:=10

You have created many inherited scenes using this node,e.g.

For many of these instances you have changed the export value of this instance (as you see by the icon changed) and the value:

You then go into the code of the master node and change the default from the inferred int as you realised it should have been a float:
export var life_span:=10.0

What happens, without warning, is every single instance in your scenes that have an override are reset to the default value you just changed it to, and you might not even realised. But you've just wiped out over 100 nodes custom data despite the change not being an invalid cast or a loss of precision. The least I would expect would be a warning, but given the change hasn't affected the data there should be a bit more intelligence...
Steps to reproduce:

create export int
add some instances and override
change to float

I'm fairly sure this has been reported in another issue already, but I can't find it right now.

I feel the same principle should also apply to renaming exported variables; when instanced scenes are opened, the old value is discarded (although an error is printed to the console).
Likewise, think I've seen this in a GIP somewhere but can't find it at the moment

I'm fairly sure this has been reported in another issue already, but I can't find it right now.

Other than the one snoopdouglas mentioned, could you be thinking one I raised last year where renaming a node loses all editable children and their data?
Oddly enough, this bug I mentioned has happened to me half a dozen times and I thought I'd done something wrong until I realised the steps to do it :)

Haha, yeah for that kind of refactoring you pretty much have to get familiar with the .tscn format (and have a text editor on hand to do a global find+replace).
It feels a bit dodgy to have Godot automatically refactoring instanced scenes based on changes that'd just been saved to a script, though I'm unsure whether this is just my bad intuition. Perhaps a dedicated 'refactor' menu would be a good idea for tasks like these?


Add Quickstart to Docs

Just started putting this into one of my apps, and the guides look really good - but also they seem exhaustive from first glance. The intro & guides contain a lot of information, which I do need to read anyway, but it felt like I was reading more about what a resource is instead of how to use this in my app.
Is it possible we could add a snippet to the README and the docs that are just like "here are the 2 things you need to do to get started with the simplest examples"?

Great idea. I'll add this soon.


Updating storybook dependencies

Fixes #xxx
This PR does the following:

Upgrades the storybook addons so that they're not causing security errors

Front End Review:

[ ] View the example in Storybook

@hokei are the failing checks above related to the github action issues we've been facing?

I've been able to repro the failure locally.  I've had issues with my local environment for a bit though so if you can pull and build properly feel free to push to this branch and we can get on with having it merge.

@kaplanmichael should all work now.


Call parent::setup in stub

I think parent::setup() could be called?
I am using a third intemediate Controllet between final CrudController and BaseCrudController where I do some setup. Actually I am setting access array values according to spatie/permission package.
https://github.com/Laravel-Backpack/Generators/blob/5b35eb7e16b205edbae0ec052592f4a6d4990f8f/src/Console/stubs/crud-controller.stub#L21

Hi @mserralta ,
Indeed - in your case it would be parent::store(), not parent::storeCrud().
But since most people don't have that third intemediate BaseCrudController, for them only parent::storeCrud() would work.
Cheers!


ci: add 'take' bot like main Arrow repo

Also, possibly have a bot edit in or comment to make it clear how this works to people landing in the repo

Related to today's biweekly discussion topic that generated this issue:
Could I try my hand at resolving this?
(cc @lidavidm , unless I should be tagging anyone else?)

Please go for it


Remove DialogExtensions.cs file no more valid.

Describe the solution you'd like
DialogExtensions.cs file is no more required in the project samples. path ....\csharp_dotnetcore\adaptive-dialog..
will remove this file.
@EricDahlvang is that fine ? shall I create PR.

@rvinothrajendran you are correct, that class is no longer needed in the sample as it is now provided in the sdk.  However, I believe we are moving the adaptive-dialog folder to experimental at some point.

@rvinothrajendran you are correct, that class is no longer needed in the sample as it is now provided in the sdk.  However, I believe we are moving the adaptive-dialog folder to experimental at some point.

@EricDahlvang I removed those files If you like it merge the changes 😎

@EricDahlvang I removed those files If you like it merge the changes 😎

Thanks @rvinothrajendran

Thanks @rvinothrajendran


connectivity: add egress-gateway-with-l7-policy test

egress-gateway-with-l7-policy checks if traffic from Pods that are selected by both Egress Gateway Policy and L7 Network Policy is properly SNATed with an Egress IP.
https://github.com/cilium/cilium/pull/32828

All tests have passed with cilium-cli-ci:1e249fd50f82d08ad0f60720417648b373420b02
https://github.com/cilium/cilium/pull/32898

Looks like multicluster is flaky
https://github.com/cilium/cilium-cli/issues/2518


Settings are not applied when expanding video from a queue built on the front page

Open youtube.com in a new tab
Add any video to the queue using "add to queue" hover button
click "expand" button in the upper left of the mini player

Result:
Nova settings fail to manifest.  At minimum: any additional player buttons and the playlist autoplay toggle fail to appear.  Refreshing the page fixes the issue.

Nova 0.46.1

What prevents you from opening a window with a player in the background or next to it? and switch to it if necessary

I don't care about the miniplayer at all but when queuing a video, the default behaviour is to show the miniplayer (it doesn't seem like the "disable miniplayer" setting stops this either) with the queue beneath it.   I see no way to open the first video of the queue without using the "expand" button.  It's the queuing feature I'm interested in.
Building a queue from a non-video page and having Nova settings applied when the first video loads is the desired behaviour.
The use case is:

open youtube front page to see what is recommended OR open a channel page to the video archive
queue preferred videos
start playing queue

Is there a possibility of replacing the "expand" button with a direct link to the queue, forcing a page refresh?

Hhmm, I get the same behaviour as before: settings not applied.  No page refresh took place either...

OK, it's working but it gets stuck in a refresh loop.

&index keeps incrementing.  You need to add at least 2 videos to queue to reproduce.

Works great now!  Thank you for doing this for me, I appreciate it.

Actually a slight modification needed.  Once Nova applies its settings to a video, subsequent queues from non-video pages work fine and a reload is NOT needed.
For example.

new tab, youtube.com
load a video
return to front page by click logo in upper left
queue videos
click expand

Result: Nova settings are applied and behave as expected.
Currently we are refreshing for every non-video page queue but it is only necessary in the case where a video page has not yet been loaded that session.


[firebase_crashlytics] runZoned with onError is deprecated in version v1.17.0

Describe the bug
Updating flutter to v1.17.0 (beta channel at the moment of writing) cause flutter analyze to trigger an error:
   info • 'onError' is deprecated and shouldn't be used. Use runZonedGuarded instead • lib/main.dart:73:6 • deprecated_member_use

To Reproduce
Steps to reproduce the behavior:

run flutter channel
select the channel beta
run flutter analyze
see the error in the console

Expected behavior
The example code in the documentation should not cause any deprecation warning.

related to https://github.com/flutter/flutter/issues/53185

A possible fix would be to change the documentation into something like this:
  runZonedGuarded(() {
    runApp(
      MyApp(),
    );
  }, (Object error, StackTrace stack) {
    Crashlytics.instance.recordError(error, stack);
  });

The documentation now recommends runZoneGuarded so I'm going to go ahead and close this.
https://firebase.flutter.dev/docs/crashlytics/usage#zoned-errors


Update documentation on how to use Powershell module on Linux

The current Powershell documentation appears to be very Windows focused.
From what I understand, the PowerCommander module is supported on Linux to some extend.
It would be great to have the documentation updated, so it becomes easier and faster to get started with the module on Linux.
Hopefully there is a business case for this. Many Windows shops are migrating to Linux and will appreciate being able to use Powershell on Linux. That is certainly the case in our case.
Thanks!

For instance here:
https://github.com/Keeper-Security/keeper-sdk-dotnet/tree/master/PowerCommander
https://docs.keeper.io/en/secrets-manager/commander-cli/commander-installation-setup/installation-on-powershell


Stop overriding Host and User-Agent headers

Vapor's HTTPClient implementation would previously always override the
Host and User-Agent headers when sending a request to the server. At
best this was undesired behaviour, at worst it would result in
HTTP 400 Bad Request responses.
Now, default values will only be provided if Host or User-Agent headers
were not already set.

Nice! Could you add some tests?

We use https://github.com/swift-server/swift-nio-http-client now on master. I'm not sure if that repo has the same problem, but it's worth checking.
This repo will likely be deprecated soon.

@tanner0101 I am aware of this and I'll fix it there too. For now I am using Vapor 3.

@OnlyForF1 ah, sorry, I didn't see that this was merging into 3.

I've refactored the tests to use httpbin, and reverted the visibility changes.

Hey @OnlyForF1, you just merged a pull request, have a coin!
You now have 1 coins.


Python38 and refactor tests to use pytest-asyncio

rebased version of https://github.com/beerfactory/hbmqtt/pull/226
depends on https://github.com/Yakifo/aio-hbmqtt/pull/17

I love where this is going! Thanks for addressing the tests @FlorianLudwig!

@FlorianLudwig do we want to squash commits? I could squash all of mine into a single python3 refactor I guess. But I don't want to do that without coordinating with you to avoid conflicts. If you consider squashing any of your feel free to do the same for mine. But after all it's just cosmetic. So, what do you think about squashing?

tl;dr
pragmatic, i would just leave it as is.
squashing commits
It is on my TODO list to write my thoughts about squashing - a complicated topic indeed. So let me have a take on it :) Just to make a simple question a discussion about principles.
The git history is part of the work of a developer and not a backup. It should tell a story, each commit is one scene. Jumping to much between them and you lose your reader (that might be yourself in a few month, trying to understand why the code ended up the way it did or some psychopath).
Some rules of thumb:

One commits should not never include unrelated changes

Generally, try to keep commits small, making it easier to review each commit on it's own

Automated changes to files that do not change the meaning (e.g. reformatting) must be a separate commit with the tools used clearly stated in the commit message

Often before doing the change you actually want to do, there is some refactoring involved, in that case:
Move refactoring into its own commit.
A refactoring should keep the same end result of the software, while changing the code.
Having a refactoring separated into a separate commit from other changes keeps them comprehensible and reviewable.


GRIP recovery IEEE37 simulation doesn't complete

I ran the IEEE37 simulation, which is being used for the Recovery phase of GRIP.  The simulation never completes, even though the JSON dump was created.  The compile flag was set.
GridLAB-D Docker Image:
REPOSITORY             TAG                 IMAGE ID            CREATED             SIZE
gridlabd/slac-master   latest              24eaf77a3c56        3 days ago          1.37

Command:
docker run --rm --name ieee37 -v $(pwd):/model -w /model gridlabd/slac-master:latest  gridlabd -C --debug --version -W /model recovery_ieee37.glm -o recovery_ieee37.json
Files in attachment:
recovery_ieee37.glm (Model)
recovery_ieee37.json (JSON dump)
gridlabd_output.txt (GridLAB-D standard out)

recovery_ieee37.zip
Note that the output didn't include the GridLAB-D version even though I used the --version command line option.

The above mentioned ieee37 feeder originates from the tools folder in the original gridlab-d repository:
https://github.com/gridlab-d/tools/blob/master/IEEE Test Models/37node/IEEE_37node.glm
I just saw now that there is already an issue request in the repository folder regarding this, but it seems like nobody fixed it:
https://github.com/gridlab-d/tools/issues/1

@Joscha90, PNNL should keep their models up to date, but on the other hand, a bad model shouldn't cause GridLAB-D to hang, so I'm leaving this issue open for now.

Bear in mind that there are some important differences between 4.1 (PNNL version) and 4.2 (SLAC version).  There is no guarantee that a model from 4.1 will work correctly under 4.2 especially if one of them is development. If you want to run the IEEE 37 bus model you must run the model from the same branch.

@dchassin , I should mention that I opened this ticket before we found the newer IEEE37 from PNNL's autotest directory.  That new one does work with SLAC GridLAB-D and is the one we'll be working with going forward.  So this issue here isn't really blocking us in GRIP, as it's based on a model we won't be using in GRIP.  It's up to you if you want to keep it open as something worth investigating.

SLAC is planning to tie off the project on 12/31/2019.  This is because PNNL cannot easily accept PRs from this fork anymore--the difference is simply too great to handle without significant effort on their part. PNNL recently started their own version 4.2, and therefore cannot recognize the SLAC version 4.2 that has been under development for CEC since last year.  We are currently reviewing the commercialization plan with the CEC, and in the interim the plan is to transfer the project to slacgismo and tie off the fork.

@jcald1 @Joscha90 Is this still an issue?

@jcald1 @Joscha90 Is this still an issue?

Not from our side, because we don't use the model anymore like Jorge mentioned in an earlier comment.


Chart id added to mouse callback events args

@erossini Sorry to spam you repository with this PR, it was intended for my personal fork :(

No problem at all. If you think I can improve something, please let me know.


[Lab 3.2] Twitter: Content

33.md

Add a card 33.md that expains how to parse the tweets from the cursor object
Add a visual

card 33.md has already been created, but is filled with info on how to create sentiment analysis for airlines instead of democratic candidates


Phone input country code no working

Describe the bug
the phone input country code feature does not work as it does not let the user selects a country code and remains opened with no way to close it.
To Reproduce
Steps to reproduce the behavior:

Go to https://flowbite.com/docs/forms/phone-input/#phone-input-country-code
Click on any phone country code
Nothing happens
The dropdown does not close and the phone country code does not change. Once opened, this dropdown does not close or let the user select the proper country code.

Expected behavior
when a user selects a country code from the list the dropdown should close and the country code should be selected
when a user clicks outside of the list the dropdown should close and the country code should remain the same
Desktop (please complete the following information):

OS: OS X (but I wouldn't be surprised if this is also the case on Windows and Linux)
Browser safari, chrome, firefox
Latest versions for the 3 of them

+1 for this issue, I'm currently handling this using Javascript

@davidmir I eventually developed the code as a Rails Stimulus controller and consider this as a template more than a component you can use out of the box.

It seems like that the JavaScript event listeners aren't set up right, I might have a try.


Improve RNG performance

In your code, every time a random thing is picked, it uses the OS entropy pool (std::random_device) to seed a new Mersenne Twister (std::mt19937) to generate a random number. This is very inefficient. Drawing from the system entropy pool is relatively expensive, and can decrease the amount of entropy available to other processes. Additionally, the Mersenne Twister is completely overkill for this application; according to Wikipedia, its "state buffer" is "almost 2.5 kB," which is necessary if you require a very long period but just reduces performance otherwise. The std::default_random_engine is plenty random for picking one of six emojis, and seeding one at application startup to share to every RNG call means that the bot isn't constantly drawing on system entropy.
(can you guess what the lecture in Computer Simulation was about today)

Thank you so much for finding that! I didnt know that at all in c++!

LGTM


Adding readme with template and files in gitignore

I added information to the Readme file.
Please look at it and show the information listed.

Adding Readme file to main project


issue about Installation

Update the Host inventory, setting it to manual to include the array serial number
hello
this statement is in the document ,what does this mean ,I can't understan clearly . thank you very much

When you create the host, there is a tab for "Host Inventory"   Clicking on this tab will bring up options to set for Automatic or Manual.  You need to set this to manual and put the serial number in for the Name.
The current integration does not autopopulate this Host Inventory information, which is why you must manually add it.


IWebApiEndpointDispatcher - resolve as scoped, remove special resolvi…

…ng of dependencies

Coveralls coverage acting up on this PR

Close PR as Coveralls coverage acting up on this PR


Fix circlePixelID to return all points within circle including those at the end of the range

circlePixelID doesn't go until the end of each range (we never actually make it to xCoordCirc + radiusCirc or yCoordCirc + radiusCirc) because in Python we never iterate to the end of the range. Need to add +1 to each of these so that we do iterate to the end of the range.

Fixed via #61


npm audit throwing severe vulnerabilities for mjml 4.15.3

Describe the bug
When using mjml 4.15.3, npm audit is throwing severe vulnerabilities for mjml-core.
To Reproduce
Steps to reproduce the behavior:

Run npm audit

Expected behavior
MJML wouldn't have severe vulnerabilities.
MJML environment (please complete the following information):

OS: MacOS
MJML Version 4.15.3
MJML tool used MJML NPM Package

Email sending environment(for rendering issues):

Sendgrid

Affected email clients (for rendering issues):

Email Client All
OS: All
Browser All

Screenshots
N/A
Additional context
The alpha 5.0.0 works, but breaks all mjml functionality.

MJML 5 don't break anything it's just now promise based. There's already an open issue about this, stop opening new one please.


MD034 false positive for links with whitespaces enclosed in angle brackets

Here's an example that should be completely valid, yet gets a warning for MD034 (no-bare-urls): [blue jay](<https://en.wikipedia.org/wiki/Blue jay>).
The quick fix recommended by the VSCode plugin is also wrong, it would turn it into this: [blue jay](<<https://en.wikipedia.org/wiki/Blue> jay>)

It is a bad fix/error, but the actual URL should have an underscore instead of space, because that is what Wikipedia actually servers https://en.wikipedia.org/wiki/Blue_jay
Unescaped spaces generally aren't actually valid URLs, and should be replaced with %20 if they're actually needed

I know that's not what Wikipedia serves, and about the %20 replacement. I made the link up for easy demonstration, and my version should still be valid, as Markdown implementations (such as CommonMark) and browsers support it.

When can I expect this to make it into the VSCode plugin too?

In a few weeks, thanks!


[BEAM-1543] Updated TestPipeline's javadoc.

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @ssisk @kennknowles
Hope this makes things clearer, sorry for the late update.

Coverage decreased (-0.01%) to 69.303% when pulling 109f1f09ce78fc886f03c556d32dac6d0a6ee84e on staslev:BEAM-1543-TestPipeline-javadoc-update into a1e8ac4fa2828edd68002b4d1053b447c5e987a1 on apache:master.

Great, glad to hear you found it helpful.
Will merge once we get the LGTM (@kennknowles ).

Taking a peek

So, LGTM. (remember to squash the fixups)

Enter BEAM-1557.


cleanup: update github.com/rabbitmq/amqp091-go from 1.3.0 to 1.8.1

Changes

🧹 cleanup: update github.com/rabbitmq/amqp091-go from 1.3.0 to 1.8.1

1.3.0 was released on jan 13, 2022
1.8.1 was released on may 4, 2023

/kind cleanup

Fixes #

Release Note

cleanup: update github.com/rabbitmq/amqp091-go from 1.3.0 to 1.8.1

Docs

just the style error and it's good to go!

just the style error and it's good to go!

thanks, the style is all in the vendor path, which i cant modify
not sure why it is not ignoring those files

/override "Code Style / style / suggester / shell"

/override "style / suggester / shell"


Print multiple labels for pdf output

Allow the user to print a file with multiple labels when using pdf as output.

@parannoide fixed in upcoming 2.0.0 release. Sorry for the delay.


Stopped 3bot does not restart

When you stop a 3bot and restart it - a payment is required to start the 3bot.
3bot account: weynandkuijpers.3bot
net: testnet
3botname:  jetserjetuno

data and time when 3bot is stopped: 09:39 - 1 feb 2021
start 3bot and give is a life to 00:00 8 Feb 2021
payment as follows:

deployment failed.
tried again (deployment 1048)
3bot started with new lifetime up to 8th Feb  2021

verified, stopped 3bot then restarted it and payed and deployment was successful


permission denied | Error response from daemon: Cannot start container

Description of problem:
I can't start any containers with the command docker run [...], even really simple one like:
# docker run busybox
Produce the following output:
permission denied Error response from daemon: Cannot start container beb4524b4f8a372d5eacdf6111d17053df0099d51f0824677fd137a97d277965: [8] System error: permission denied
docker version:
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.5.1
 Git commit:   a34a1d5-dirty
 Built:        Sun Nov 22 00:15:15 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.5.1
 Git commit:   a34a1d5-dirty
 Built:        Sun Nov 22 00:15:15 UTC 2015
 OS/Arch:      linux/amd64

docker info:
Containers: 5
Images: 21
Server Version: 1.9.1
Storage Driver: btrfs
 Build Version: Btrfs v4.3.1
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.2.5-1-ARCH
Operating System: Arch Linux (containerized)
CPUs: 4
Total Memory: 7.679 GiB
Name: J3XYZ
ID: 7AQW:SMAM:NRQM:UU3P:FLJ2:XYUM:E66X:RPBS:BISE:4CDP:2NKB:GPBK

uname -a:
Linux J3XYZ 4.2.5-1-ARCH #1 SMP PREEMPT Tue Oct 27 08:13:28 CET 2015 x86_64 GNU/Linux
Environment details (AWS, VirtualBox, physical, etc.):
Lenovo X250
How reproducible:
docker run xyz
Steps to Reproduce:

sudo yaourt docker (->community/docker)
systemctl start docker
sudo docker run busybox

Actual Results:
permission denied
Error response from daemon: Cannot start container 03ffb7da4d1f0e5fa04d6e254d2aa67f0d36e31cab858a01c1f56f2bb165b97d: [8] System error: permission denied

Expected Results:
A running container, obviously :)
Additional info:
Arch, btrfs, luks filesystem

The same here. Only the underlying hardware is different. I also run Arch Linux, BTRFS on USB-HDDs.
Command
docker run -it feduxorg/centos

Information
$ docker version
Client:
Version:      1.9.1
API version:  1.21
Go version:   go1.5.1
Git commit:   a34a1d5-dirty
Built:        Sun Nov 22 00:15:15 UTC 2015
OS/Arch:      linux/amd64

Server:
Version:      1.9.1
API version:  1.21
Go version:   go1.5.1
Git commit:   a34a1d5-dirty
Built:        Sun Nov 22 00:15:15 UTC 2015
OS/Arch:      linux/amd64

$ docker info
Containers: 1
Images: 63
Server Version: 1.9.1
Storage Driver: btrfs
Build Version: Btrfs v4.3.1
Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.3.3-2-ARCH
Operating System: Arch Linux (containerized)
CPUs: 4
Total Memory: 3.853 GiB
Name: hostname
ID: RDOC:QWIJ:4BXZ:PLAG:Z2PQ:RA2L:NPLD:OYK7:A2L5:3BKD:OJXG:DDYA

$ uname -a
Linux idefix.in.fedux.org 4.2.5-1-ARCH #1 SMP PREEMPT Tue Oct 27 08:13:28 CET 2015 x86_64 GNU/Linux

Output
  Jan 02 19:42:28 hostname docker[454]: time="2016-01-02T19:42:28.956221642+01:00" level=warning msg="failed to cleanup ipc mounts:\nfailed to umount /var/lib/docker/containers/b6abf4900b722556e7e2582119ebd61454564c1e2224a0634d3ad2ea066ecd38/shm: invalid argument\nfailed to umount /var/lib/docker/containers/b6abf4900b722556e7e2582119ebd61454564c1e2224a0634d3ad2ea066ecd38/mqueue: invalid argument"
Jan 02 19:42:28 hostname docker[454]: time="2016-01-02T19:42:28.956808309+01:00" level=error msg="Handler for POST /v1.21/containers/b6abf4900b722556e7e2582119ebd61454564c1e2224a0634d3ad2ea066ecd38/start returned error: Cannot start container b6abf4900b722556e7e2582119ebd61454564c1e2224a0634d3ad2ea066ecd38: [8] System error: permission denied"

It helps. I started docker daemon manually. Here's the output.
INFO[0144] POST /v1.21/containers/create
DEBU[0146] Registering new volume reference: driver , name 258b2d337cb32804f5f19a5804496ce34e2056ba639c2c3549398b6958d11205
DEBU[0146] Incrementing volume reference: driver local, name 258b2d337cb32804f5f19a5804496ce34e2056ba639c2c3549398b6958d11205
DEBU[0146] Creating dest directory: /var/lib/docker/volumes/258b2d337cb32804f5f19a5804496ce34e2056ba639c2c3549398b6958d11205/_data
DEBU[0146] Calling TarUntar(/var/lib/docker/btrfs/subvolumes/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/var/ssh, /var/lib/docker/volumes/258b2d337cb32804f5f19a5804496ce34e2056ba639c2c3549398b6958d11205/_data)
DEBU[0146] TarUntar(/var/lib/docker/btrfs/subvolumes/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/var/ssh /var/lib/docker/volumes/258b2d337cb32804f5f19a5804496ce34e2056ba639c2c3549398b6958d11205/_data)
DEBU[0146] Registering new volume reference: driver local, name 2fb4efde15f7b00701911c4cf141d57b5bb2bf8e26deb521e6d91b5f3dc2794a
DEBU[0146] Incrementing volume reference: driver local, name 2fb4efde15f7b00701911c4cf141d57b5bb2bf8e26deb521e6d91b5f3dc2794a
DEBU[0146] Creating dest directory: /var/lib/docker/volumes/2fb4efde15f7b00701911c4cf141d57b5bb2bf8e26deb521e6d91b5f3dc2794a/_data
DEBU[0146] Calling TarUntar(/var/lib/docker/btrfs/subvolumes/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/run, /var/lib/docker/volumes/2fb4efde15f7b00701911c4cf141d57b5bb2bf8e26deb521e6d91b5f3dc2794a/_data)
DEBU[0146] TarUntar(/var/lib/docker/btrfs/subvolumes/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/run /var/lib/docker/volumes/2fb4efde15f7b00701911c4cf141d57b5bb2bf8e26deb521e6d91b5f3dc2794a/_data)
DEBU[0146] Registering new volume reference: driver local, name bc30f933b8c7f07d49027072389a14558111048fa590f975f71ef71098bdd426
DEBU[0146] Incrementing volume reference: driver local, name bc30f933b8c7f07d49027072389a14558111048fa590f975f71ef71098bdd426
DEBU[0146] Registering new volume reference: driver local, name e7413e6e150aa837cefb57828c987a1234a930ecaf9e630c7b5d1d6c3c699359
DEBU[0146] Incrementing volume reference: driver local, name e7413e6e150aa837cefb57828c987a1234a930ecaf9e630c7b5d1d6c3c699359
DEBU[0146] Creating dest directory: /var/lib/docker/volumes/e7413e6e150aa837cefb57828c987a1234a930ecaf9e630c7b5d1d6c3c699359/_data
DEBU[0146] Calling TarUntar(/var/lib/docker/btrfs/subvolumes/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/tmp, /var/lib/docker/volumes/e7413e6e150aa837cefb57828c987a1234a930ecaf9e630c7b5d1d6c3c699359/_data)
DEBU[0146] TarUntar(/var/lib/docker/btrfs/subvolumes/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/tmp /var/lib/docker/volumes/e7413e6e150aa837cefb57828c987a1234a930ecaf9e630c7b5d1d6c3c699359/_data)
DEBU[0146] Registering new volume reference: driver local, name 7b5b05b017767d51e16b12e1b8335f18e93d3678c3e24178f1bb61f99c024a7a
DEBU[0146] Incrementing volume reference: driver local, name 7b5b05b017767d51e16b12e1b8335f18e93d3678c3e24178f1bb61f99c024a7a
DEBU[0146] Calling POST /v1.21/containers/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/attach
INFO[0146] POST /v1.21/containers/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/attach?stderr=1&stdin=1&stdout=1&stream=1
DEBU[0146] attach: stdin: begin
DEBU[0146] attach: stdout: begin
DEBU[0146] attach: stderr: begin
DEBU[0146] Calling POST /v1.21/containers/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/start
INFO[0146] POST /v1.21/containers/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/start
DEBU[0146] Assigning addresses for endpoint berserk_mcclintock's interface on network bridge
DEBU[0146] RequestAddress(LocalDefault/<IP_ADDRESS>/16, <nil>, map[])
DEBU[0146] Assigning addresses for endpoint berserk_mcclintock's interface on network bridge
WARN[0146] exit status 1
DEBU[0146] attach: stdout: end
DEBU[0146] attach: stdin: end
DEBU[0146] attach: stderr: end
DEBU[0146] Closing buffered stdin pipe
DEBU[0146] Releasing addresses for endpoint berserk_mcclintock's interface on network bridge
DEBU[0146] ReleaseAddress(LocalDefault/<IP_ADDRESS>/16, <IP_ADDRESS>)
WARN[0146] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/containers/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/shm: invalid argument
failed to umount /var/lib/docker/containers/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/mqueue: invalid argument
ERRO[0146] Handler for POST /v1.21/containers/50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879/start returned error: Cannot start container 50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879: [8] System error: permission denied
ERRO[0146] HTTP Error                                    err=Cannot start container 50d48d724880757d8ea971b142d74c706557f9c4e2711e6d3b7c22a14efc5879: [8] System error: permission denied statusCode=500

After switching the storage driver to -s devicemapper the container started. How can @Brandl and I help to find the underlying problem?
Sorry @thaJeztah to involving you directly, but that error was driving me crazy. Now I have a workaround using the devicemapper storage driver, but that does not really look like a solution for people using docker in production. Can you help us getting in touch with somebody who has the time/knowledge to dig deeper?

I think @vbatts runs on btrfs, perhaps he has some suggestions here

Thanks!

@maxmeyer for the sake of information, can you paste the output from running https://github.com/docker/docker/blob/master/contrib/check-config.sh ?
I'm not precisely sure where this EPERM or 'invalid argument' is bubbling up from

Here you are
info: reading kernel config from /proc/config.gz ...

Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_MACVLAN: enabled (as module)
- CONFIG_VETH: enabled (as module)
- CONFIG_BRIDGE: enabled (as module)
- CONFIG_BRIDGE_NETFILTER: enabled (as module)
- CONFIG_NF_NAT_IPV4: enabled (as module)
- CONFIG_IP_NF_FILTER: enabled (as module)
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
- CONFIG_NF_NAT: enabled (as module)
- CONFIG_NF_NAT_NEEDED: enabled
- CONFIG_POSIX_MQUEUE: enabled

Optional Features:
- CONFIG_USER_NS: missing
- CONFIG_SECCOMP: enabled
- CONFIG_MEMCG_KMEM: enabled
- CONFIG_MEMCG_SWAP: enabled
- CONFIG_MEMCG_SWAP_ENABLED: enabled
- CONFIG_BLK_CGROUP: enabled
- CONFIG_IOSCHED_CFQ: enabled
- CONFIG_BLK_DEV_THROTTLING: enabled
- CONFIG_CGROUP_PERF: missing
- CONFIG_CGROUP_HUGETLB: missing
- CONFIG_NET_CLS_CGROUP: enabled (as module)
- CONFIG_CGROUP_NET_PRIO: missing
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: missing
- CONFIG_EXT3_FS: missing
- CONFIG_EXT3_FS_XATTR: missing
- CONFIG_EXT3_FS_POSIX_ACL: missing
- CONFIG_EXT3_FS_SECURITY: missing
    (enable these ext3 configs if you are using ext3 as backing filesystem)
- CONFIG_EXT4_FS: enabled (as module)
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Storage Drivers:
  - "aufs":
    - CONFIG_AUFS_FS: missing
  - "btrfs":
    - CONFIG_BTRFS_FS: enabled (as module)
  - "devicemapper":
    - CONFIG_BLK_DEV_DM: enabled (as module)
    - CONFIG_DM_THIN_PROVISIONING: enabled (as module)
  - "overlay":
    - CONFIG_OVERLAY_FS: enabled (as module)
  - "zfs":
    - /dev/zfs: missing
    - zfs command: missing
    - zpool command: missing

I believe I am seeing the same issue.
Arch linux. btrfs all the way down.
[root@TheBeast subvolumes]# docker info                                                                                │··············································
Containers: 1                                                                                │··············································
 Running: 0                                                                                │··············································
 Paused: 0                                                                                │··············································
 Stopped: 1                                                                                │··············································
Images: 2                                                                                │··············································
Server Version: 1.10.1                                                                                │··············································
Storage Driver: btrfs                                                                                │··············································
 Build Version: Btrfs v4.4                                                                                │··············································
 Library Version: 101                                                                                │··············································
Execution Driver: native-0.2                                                                                │··············································
Logging Driver: json-file                                                                                │··············································
Plugins:                                                                                │··············································
 Volume: local                                                                                │··············································
 Network: bridge null host                                                                                │··············································
Kernel Version: 4.4.1-2-ARCH                                                                                │··············································
Operating System: Arch Linux                                                                                │··············································
OSType: linux                                                                                │··············································
Architecture: x86_64                                                                                │··············································
CPUs: 4                                                                                │··············································
Total Memory: 15.37 GiB                                                                                │··············································
Name: TheBeast                                                                                │··············································
ID: LAWN:HW5J:LSV6:T5Z4:7IK6:JOIS:T7WR:DQW7:36XT:KPOM:ZAHR:LSCW                                                                                │··············································
Debug mode (server): true                                                                                │··············································
 File Descriptors: 11                                                                                │··············································
 Goroutines: 27                                                                                │··············································
 System Time: 2016-02-19T00:43:39.740323983-06:00                                                                                │··············································
 EventsListeners: 0                                                                                │··············································
 Init SHA1: f00b84100ee66b5f583bbc59f9359ec4492fb6b5                                                                                │··············································
 Init Path: /usr/lib/docker/dockerinit                                                                                │··············································
 Docker Root Dir: /var/lib/docker                                                                                │··············································
[root@TheBeast subvolumes]# docker run hello-world                                                                                │··············································
permission denied                                                                                │··············································
docker: Error response from daemon: Container command could not be invoked..

It seems we are all running arch linux on btrfs with 4.x kernels.
Can anyone confirm the absence or presence of this issue on any of those variables in isolation?
ie kernel 4.x, btrfs filesystems, or arch linux?

I just ran with
docker daemon -D -s devicemapper

and it seems to be working. Thanks @maxmeyer . That's good enough for me right now.
I am still interested in helping or at least learning more about this issue however.

Same configuration, same issue and same solution here. If you need more information, just ask.

I'm getting the same issue on Fedora 23.
[14rcole@fedora docker] $ sudo docker info [sudo] password for rycole:  Containers: 10 Images: 15 Server Version: 1.9.1 Storage Driver: devicemapper  Pool Name: docker-253:1-293966-pool  Pool Blocksize: 65.54 kB  Base Device Size: 107.4 GB  Backing Filesystem:   Data file: /dev/loop0  Metadata file: /dev/loop1  Data Space Used: 1.667 GB  Data Space Total: 107.4 GB  Data Space Available: 44.98 GB  Metadata Space Used: 2.064 MB  Metadata Space Total: 2.147 GB  Metadata Space Available: 2.145 GB  Udev Sync Supported: true  Deferred Removal Enabled: false  Deferred Deletion Enabled: false  Deferred Deleted Device Count: 0  Data loop file: /var/lib/docker/devicemapper/devicemapper/data  Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata  Library Version: 1.02.107 (2015-09-05) Execution Driver: native-0.2 Logging Driver: json-file Kernel Version: 4.2.3-300.fc23.x86_64 Operating System: Fedora 23 (Workstation Edition) CPUs: 4 Total Memory: 11.44 GiB Name: 14rcole.fedora ID: MXHU:25N2:RHTF:6EKP:JITG:BYBR:BTOV:G56F:CKBT:IQQJ:OCQ2:WCE2 Debug mode (server): true  File Descriptors: 21  Goroutines: 40  System Time: 2016-05-26T20:46:47.774142101-04:00  EventsListeners: 0  Init SHA1: aedd0c57159cf055ee19eb48fb00402562460078  Init Path: /usr/libexec/docker/dockerinit  Docker Root Dir: /var/lib/docker
So I'm kernel 4.x but not arch or btrfs
The command
docker daemon -D -s devicemapper
solves the issue but I see it more as a temporary workaround than a fix

@14rcole your regular graph driver is also btrfs?

I'm trying to use docker on CentOS 7 and get the same question. It seems I have to disable seLinux in host os. Can I do something else to let my docker work without disable my seLinux?

Getting the same issue with btrfs, Arch Linux, and kernel 4.6.2-1-ARCH.
─── docker info
Containers: 8
 Running: 0
 Paused: 0
 Stopped: 8
Images: 4
Server Version: 1.11.2
Storage Driver: btrfs
 Build Version: Btrfs v4.5.3
 Library Version: 101
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.6.2-1-ARCH
Operating System: Arch Linux
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 2.795 GiB
Name: pirate
ID: OWEL:KLST:3UQR:QISO:KOUT:36DM:72DQ:ZNNV:CONF:REX4:JVDE:QGEB
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/

I'm having this same issue in Fedora 24 (RUN apt-get update -y - Permission denied). Following @14rcole's suggestion to run the daemon with allows it to work for now:
 docker daemon -D -s devicemapper

Docker started working for me a few days ago again. Not sure what I did to fix it. I re-installed it a few times and wiped /var/lib/docker, and it appears to have resolved itself.

try close SELinux by:
setenforce 0

The same to me,i fixed it by the common:
ls -aZ /usr/bin/docker*
-rwxr-xr-x. root root system_u:object_r:docker_exec_t:s0 /usr/bin/docker
-rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/bin/docker-current
-rwxr-xr-x. root root system_u:object_r:bin_t:s0 /usr/bin/docker-storage-setup
sudo chcon -t docker_exec_t /usr/bin/docker*
sudo systemctl restart docker

@aker's chcon -t docker_exec_t fixed it for my VM which was cloned from another one. Maybe that's why this type was gone.
I'm not using btrfs. It's likely some people in this issue simply have SELinux problems.
I also tried running the docker daemon from outside the docker systemd unit which made it work prior to the SELinux fix. Got this from the likely very related issue #17475 here. But since this wasn't a permant fix, I'm very happy to have found @aker's fix. May I ask where you got this from? Especially since you're saying it's common.

@aCandidMind How did you install docker?
The docker RPM's include an selinux policy that does exactly what you have done with the chcon. This should not be an issue with the official packages.

I see all these problems seem related to packaging with arch, which is non-official. This is not something that can be fixed here.
Docker supplies a policy here: https://github.com/docker/docker/tree/master/contrib/selinux/docker-engine-selinux
This is packaged as docker-engine-selinux on our yum repos for each supported platform.
Specifically with changes in 1.11, it was required to set docker_exec_t on /usr/bin/dockerd which was a new binary introduced by splitting the docker client (docker) and the docker daemon (dockerd).
Going to go ahead and close as this is not an issue that we can deal with here, but feel free to discuss.
Thanks all! 👼

Sorry for responding so late @cpuguy83.
I installed docker on my CentOS VM via yum install docker-engine*-1.9.1* from yum.dockerproject.org. yum list installed docker* yields:
docker-engine.x86_64                   1.9.1-1.el7.centos            @dockerrepo
docker-engine-selinux.noarch           1.9.1-1.el7.centos            @dockerrepo

So the 1.11 split of binaries wasn't the cause in my case.
As I said above, I guess some people in this issue here had problems with the systemd/SELinux  co-operation with docker rather than Arch or btrfs problems (because they said they're not using Arch) which makes this issue have two groups of setups. On the one hand Arch and/or btrfs and on the other hand systemd and/or SELinux not using Arch or btrfs (including me). See that @14rcole's comment and @sevagh's comment mention that they are using Fedora and not Arch. And you could read into their comments that running the daemon on their own without systemd resolved their problems. Same as the related issue #17475 I mentioned above. Another CentOS user pointing in the SELinux direction can be found in our current thread here. My cloned CentOS VM (cloned from an existing VirtualBox CentOS VM, maybe that caused my SELinux problem) is also not Arch.
Just putting this here for completeness for the next user that runs into that error response.

@aCandidMind I really can't speak for the 1.9 policies, it is very likely those policies failed to load and the rpm installation itself would not fail itself and only give a warning since the base packages, selinux-policy, have changed so much and centos is a rolling release.


Error use leading app bar

Hello. First, i have to say thank you to contributors for develop this package. Its great.
Let me show my issue to build an app bar with leading inside that.

Is that correct to create leading in app bar? coz i can't found sample code with leading from the example project. I just think that leading is a widget type, so i put the object to leading map. But, i got this error

I have read the schema, but the leading are support type of string, number, and boolean. Even though the leading is a widget object in material.
Thanks in advance

Can you post a full example of a JSON file with the issue you're having?  It doesn't have to be the exact one you're trying, just any JSON showing the issue.  With that, I can try to help.

Does it work for you in profile or release mode?  I actually think I might know the issue.  If it works in one of those that confirms my theory.

I'm using a lot of custom widgets in my project. Maybe its example from a simple JSON widget from my issue.
{
  "type": "scaffold",
  "args": {
    "appBar": {
      "type": "app_bar",
      "args": {
        "backgroundColor": "#000000",
        "title": {
          "type": "text",
          "args": {
            "text": "Leading Example"
          }
        },
        "elevation": 0,
        "automaticallyImplyLeading": false,
        "leading": {
          "type": "icon_button",
          "args": {
            "icon": {
              "type": "icon",
              "args": {
                "icon": {
                  "codePoint": 58712,
                  "fontFamily": "MaterialIcons",
                  "color": "#FFFFFF"
                }
              }
            }
          }
        }
      }
    }
  }
}

I think it should build the widget, cause I see the code in the library especially in app_bar_builder. And I found the leading param and should to build by another widget.

And the issue when I want to use automaticallyImplyLeading with false value, but it throws to exception.
I can't debug the code of the library coz it from another package.
Thanks a lot.

Thanks a lot for both the report and the JSON.  I published v2.2.0 today which includes your example in working form now.
I'm going to close this issue as I believe it is resolved.  Please feel free to re-open it if you disagree and believe it still needs more work.

Thanks a lot for both the report and the JSON. I published v2.2.0 today which includes your example in working form now.
I'm going to close this issue as I believe it is resolved. Please feel free to re-open it if you disagree and believe it still needs more work.

I've tried it with v2.2.0 and now it works like a charm. Thanks in advance.


Streaming timeline printer

Demo to print the user timeline in real time and cherry pick of some refactors from the previous PR https://github.com/DanielaSfregola/twitter4s-demo/pull/18

Changes are ready!


Confusing Log: Task ended for DenomUpsertTask

I feel like we can make this more informative.

I think it's weird that it says the Task ended, but it never says the task started
I don't think its clear what DenomUpsert means.

I would like to have the following changes made.

Add INF log for Updating Denom Metadata from {base.api}
Change Task ended for DenomUpsertTask to `Denom Metadata Update Complete

This one should be pretty easy.
The "task started" log is in the Debug output while "task ended" is in the Info output, thus you can't see the first.
Should be pretty simple to update the log output.

They should probably both be at the same log level.  I'd say make them both INFO.


swtpm: 0.7.2 -> 0.7.3

Description of changes
https://github.com/stefanberger/swtpm/releases/tag/v0.7.3
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 170868 run on x86_64-linux 1

2 packages built:

quickemu
swtpm


[8.x] Add flush handler to output buffer for streamed test response (bugfix)

This PR fixes a bug which may lead to missed content for a streamed test response.
Typically, code which wants to ensure that its output is really streamed to browser contains code lines like these
if (ob_get_level() > 0) {
  ob_flush();
}
flush();

This is the recommended best practice to ensure that all buffers are flushed and the content is sent to the browser:

PHP Manual:

This means ob_flush() should be called before flush() to flush the output buffers if they are in use.

Symfony Manual:

The flush() function does not flush buffering. If ob_start() has been called before or the output_buffering php.ini option is enabled, you must call ob_flush() before flush().

The current implementation of the test response does not work if one follows this practice. In particular, ob_flush sends all content of the output buffer to stdout in test mode and clears the buffer. The method ob_get_clean() as used by the current implementation will always return the empty string. This means TestResponse misses all output.
The correct way is to register a handler with ob_start which is called whenever the buffer is flushed. PHP Manual:

An optional callback function may be specified. This function takes a string as a parameter and should return a string. The function will be called when the output buffer is flushed (sent) or cleaned (with ob_flush(), [...] or similar function) or when the output buffer is flushed to the browser at the end of the request. [...]. When callback is called, it will receive the contents of the output buffer as its parameter and is expected to return a new output buffer as a result, which will be sent to the browser.

Note, the bugfix always returns the empty string. During tests there is on browser and the output would be sent to stdout, if we were not returning the empty string.

Fixes #42482

The bugfix also needs to be merged into the 9.x branch.

@nagmat84 we merge 8.x changes into 9.x 👍


Pictures in a subfolder don't show

When a markdown document references a picture in a subfolder:
![my picture](images/picture.jpg)

The picture is properly uploaded as attachment to the confluence page. But it is not displayed.
When looking at the attachment in confluence (which is named images/picture.jpg, I cannot display the picture either.
This is a common use case, so documenting this as limitation is not very friendly.

This appears to have been a regression.
Changes have been pushed to the branch master to substitute any character outside the allowed set of characters with the placeholder _ (underscore). Normally, Confluence would only allow alphanumeric characters (0-9, a-z and A-Z) and special characters _ (underscore), - (hyphen) and . (dot) in attachment names but this is not strictly enforced for all API calls. Any characters that don't match these are now replaced with _, including the path separator /.
Once these changes are applied, images display in published Markdown documents as expected, including those with non-trivial relative paths w.r.t. the base folder.

Great, thanks!


Feature packet improvements

This PR contains a number of commits with small bugfixes and an improved interface:

CMake: avoid building pybind11 targets by default. [Feature]
Packet interface: add new helper functions to simplify creating CRTP packets [Feature]
Statistics: Proper update of enqueued_count [Bugfix]

See also https://github.com/IMRCLab/crazyswarm2/issues/5.

I've looked at the changes and tried out the code so to me it all looks good. I also haven't helped setting up this code, so bit unsure if I have the right eye on to really evaluate this PR.
I've just tried the example_scan and example_console but is there anything I should look out for to make sure that this PR is doing it's purpose? The most important one is to see if enqueued_count is fixed right?

I don't think you would see any functional changes here, because enqueued_count was simply not used in the example applications.
There is no really good reviewer - Arnaud helped a lot with the CI infrastructure, but otherwise the code wasn't reviewed much.

Yeah true. And the changes you have implement would not have a major impact on the functionality, mostly statistic related.
I've just added the next release milestone on it, but if you want you can go ahead and merge it.

Or I'll merge it:) here you go!

Thanks! I'll update the other projects recursively.


accept full URIs into service parameters

use case:
prefix prov:   <http://www.w3.org/ns/prov-o/>
prefix select: <http://sparql.tw.rpi.edu/services/datafaqs/core/select-faqts/>

select distinct ?input
where {
  []
     prov:wasAttributedTo {{base.args.arg0}};
     prov:used            ?input;
  .
}

where the param is some unknown URI (so it is a hassle to find a qname for it.)

 Example: {{base.args.arg0|urldecode}}
A problem I found was that you need to encode three times in order to pass an actually encoded value. The first two are converted automatically by Apache+PHP (or so it seems) before LODSPeaKr can take a look at it.
For example http://logd.tw.rpi.edu must be converted into http%25253A%25252F%25252Flogd.tw.rpi.edu (%25 is the encoding for %). In order to encode a string, you can use the urlencode filter.
I will try to find a better solution but for now this should work.

javascript to thrice-encode:
encodeURIComponent(encodeURIComponent(encodeURIComponent(service)));

I've gotten this to work.


LCFS - Add Liveness Probe Health Checks

As a developer, I want to know when LCFS is down so we can take action if needed.
https://docs.openshift.com/container-platform/4.15/applications/application-health.html
Health check is available at /api/health on the backend
We want to add a health check to the Python API that can ensure it is up and available. This will auto restart failing pods and give us better oversight of our uptime.

This is done.
Received the health check through livenessProb, here is the backend log:
INFO: <IP_ADDRESS>:41548 - "GET /api/health HTTP/1.1" 200 OK


New version: GMT v0.9.0

Registering package: GMT
Repository: https://github.com/GenericMappingTools/GMT.jl
Created by: @joa-quim
Version: v0.9.0
Commit: 6f7d71ac368a28fc1bc869974bd1bfbd4862279d
Reviewed by: @joa-quim
Reference: https://github.com/GenericMappingTools/GMT.jl/issues/254#issuecomment-494759237

Can you add (at least)
[compat]
julia = "1"

to the project file and retrigger the bot?

OK, done.

Consider enabling TagBot to make sure the release is persistent in your repo, see https://discourse.julialang.org/t/ann-tagbot-creates-tags-and-releases-for-your-julia-packages-when-theyre-registered/23084


DNBSEQ-T7 platform demultiplexing

Hello.
I have 4 snATAC-seq samples from the DNBSEQ-T7 platform, and for each sample, they are mixed with multiple cell lines. For R1, the read length is 50bp, and for R2, the read length is 70bp.
I used PISA to add 51-60 (10bp), 61-70 (10bp) of R2, a total of 20bp, as barcodes to R1 and R2, and extracted the original R1 (50bp), R2 (1-50bp in 70bp) as paired fastq and further used bwa for alignment.
Strangely, the alignment rates of the 4 samples are only close to 50% (46, 48, 53, 54%). I would like to ask if I have misunderstood the position of the barcode?
I also used dnbc4atac for alignment, the command is as follows
dnbc4atac run --fastq1 /my_disk/public/Data/scATAC_RNA/CNS0798658/snATAC_pool4_read_1.fq.gz
--fastq2 /my_disk/public/Data/scATAC_RNA/CNS0798658/snATAC_pool4_read_2.fq.gz
--name CNS0798658
--genomeDir /home/jiangr/reference/GRch38/dnbc4tools
--outdir /mnt/data1/jiangr/CL_scATAC/CNS0798658/dnbc4_result
--threads 20
Error log in 01.data/alignment_report.tsv
Less than 5% barcodes can be found or corrected based on the barcode whitelist.
It seems that dnbc4atac cannot handle such data.
Thank you for your help.

The sequencing length you have does not align with MGI's single-cell ATAC reagents.
MGI's cell barcode should reside within the first 20bp of R1, with a sequencing length of R1 70bp + R2 50bp.
You can initially BLAST a few paired-end reads to verify the barcode's exact position based on alignment information.
If the barcode is indeed located in the last 20bp of R2, use
dnbc4tools atac run
   --fastq1 snATAC_pool4_read_2.fq.gz
   --fastq2 snATAC_pool4_read_1.fq.gz
   --customize bc:50:69,r1:0:49,r2:0:49

If it's in the first 20bp of R1, you might need to re-split and trim your data to ensure a sequencing length of R1 70bp + R2 50bp.

Thanks for your suggestions. I made more attempts to extract the barcode, details are as follows.
check structure of R1(70bp? read_2)/R2(50bp? read_1)?
zcat /my_disk/public/Data/scATAC_RNA/CNS0798659/snATAC_pool5_read_2.fq.gz|head -n 8
@DP8400011418BRL1C001R0030000004/2
ATATTAGTTCATATTGTTTTTATAGTAATGTTAATAGTGATTAACGCCGTACCATACAATAAGTTGGTGG
+
D;CEE'6@<AD;A;=)CF'3<.?FB>6??@C=FEFCEC?DEAEFE)FCE7FBFGDFGFEFEEDC?'C4
@DP8400011418BRL1C001R0030000016/2
TACTAGGCCTACTAACCAACACACTAACCATATACCAATGATGGCGCGATGAGACTATAGTCACGAATCC
+
IIHGHIHHHIIGGHGHIIIGIIIIIIHHHHHHHIHIHGGI:HIHIIIHGIH<IGH?I4IHHIIIIGIIIG
zcat /my_disk/public/Data/scATAC_RNA/CNS0798659/snATAC_pool5_read_1.fq.gz|head -n 8
@DP8400011418BRL1C001R0030000004/1
CGTTAATCACTATTAAAATTACTATAAAAACAATATGAACTAATATCTGG
+
CE>BDCECEDCEEDDEDD=DFADEEFDDDEBEEAE:GCD@BGE>D@E?E&
@DP8400011418BRL1C001R0030000016/1
GGTGGTGTGTGGTGGCCTTGGTATGTGCTTTCTCGTGTTACATCGCGCCA
+
FGCGEIIFHFIGGGAFGIFGFHIIIFHHHFIIGHHEIFGIGEIIHHGIHI
The fq file name provided in the article does not seem to be correct, since R1=50bp and R2=70bp? However, the fq header is consistent with the fq file name.
Use PISA to extract barcode but fail.
PISA parse2  -t 10 -rule 'CR,R1:1-10,/home/jiangr/tools/PISA-1.0b/config/DNBelabC4_barcodes.txt,CB,1;CR,R1:11-20,/home/jiangr/tools/PISA-1.0b/config/DNBelabC4_barcodes.txt,CB,1;R1,R2:1-100' -1 /mnt/data2/jiangr/CL_scATAC3/CNS0798659/clean/CNS0798659_demultiplex.fq /my_disk/public/Data/scATAC_RNA/CNS0798659/snATAC_pool5_read_2.fq.gz /my_disk/public/Data/scATAC_RNA/CNS0798659/snATAC_pool5_read_1.fq.gz
DNBelabC4_barcodes.txt contains 10bp barcode list (n=1536). However, the size of CNS0798659_demultiplex.fq is only 177MB.
/my_disk/public/Data/scATAC_RNA/CNS0798659/snATAC_pool5_read_2.fq.gz (40G); /my_disk/public/Data/scATAC_RNA/CNS0798659/snATAC_pool5_read_1.fq.gz (27G).
re-run dnbc4atac but fail
dnbc4atac run --fastq1 /my_disk/public/Data/scATAC_RNA/CNS0798658/snATAC_pool4_read_2.fq.gz \
        --fastq2  /my_disk/public/Data/scATAC_RNA/CNS0798658/snATAC_pool4_read_1.fq.gz \
        --name CNS0798658 \
        --genomeDir /home/jiangr/reference/GRch38/dnbc4tools \
        --outdir /mnt/data1/jiangr/CL_scATAC/CNS0798658/dnbc4_result \
        --threads 20

When running dnbc4atac, I changed the R1/R2 files. Originally R1(read_1=50bp), R2(read_2=70bp), now R1(read_2=70bp), R2(read_1=50bp), but still not enough barcodes are detected?
Error log in 01.data/alignment_report.tsv
Less than 5% barcodes can be found or corrected based on the barcode whitelist.
I think this R1=50; R2=70bp library is very strange.
In summary, I tested two different processing methods.
Case 1, 1-20 of 70bp fastq as barcode; PISA only retained a few reads in R1/R2 (fq=177MB).
Case 2, 51-70 of 70bp fastq as barcode; CNS0798658_demultiplex.trimed.R1.fq.gz (originally 40G, now 14G)
CNS0798658_demultiplex.trimed.R2.fq.gz (originally 27G, now 14G), but the mapping rate of the bwa tool is only 50%.
Could you provide some suggestions or code? Thanks.

PISA parse2  -t 10 \
  -rule 'CR,R2:51-60,/home/jiangr/tools/PISA-1.0b/config/DNBelabC4_barcodes.txt,CB,1;CR,R2:61-70,/home/jiangr/tools/PISA-1.0b/config/DNBelabC4_barcodes.txt,CB,1;R1,R1:1-50;R2,R2:1:50'  \
  -report /mnt/data2/jiangr/CL_scATAC3/CNS0798659/clean/fastq.csv \
  -1 /mnt/data2/jiangr/CL_scATAC3/CNS0798659/clean/snATAC_pool5_read_1.fq  \
  -2 /mnt/data2/jiangr/CL_scATAC3/CNS0798659/clean/snATAC_pool5_read_2.fq \
  /my_disk/public/Data/scATAC_RNA/CNS0798659/snATAC_pool5_read_1.fq.gz  \
  /my_disk/public/Data/scATAC_RNA/CNS0798659/snATAC_pool5_read_2.fq.gz

I suggest you try to analyze it in this way. I remember you posted an issue about the article data before.
I said at that time that the data was a very early version. You see if this analysis is feasible.

dnbc4tools need add --customize bc:50:69,r1:0:49,r2:0:49


Write a Julia program to convert hours to weeks

Description
Write a Julia program to convert hours to weeks
1 week = 7 days = 168 hours
Input  : 840
Output : 5

How to contribute

Save the solution in convert-hours-to-weeks.jl file
Add convert-hours-to-weeks.jl file in convert-hours-to-weeks folder

!assign


chore: fix dd-trace-cpp API usage

Changes:

Use rapidjson instead of nlohmann::json.
Temporarily disabled test_configuration.py:test_in_http

Codecov Report
Attention: Patch coverage is 94.11765% with 1 line in your changes missing coverage. Please review.

Project coverage is 67.28%. Comparing base (27795ac) to head (c4ff758).
Report is 2 commits behind head on master.

Files
Patch %
Lines

src/datadog_variable.cpp
0.00%
1 Missing :warning:

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #106      +/-   ##
==========================================
- Coverage   67.64%   67.28%   -0.36%
==========================================
  Files          36       36
  Lines        3533     3540       +7
  Branches      615      615
==========================================
- Hits         2390     2382       -8
- Misses        818      832      +14
- Partials      325      326       +1

Files
Coverage Δ

src/datadog_directive.cpp
52.71% <ø> (ø)

src/ngx_event_scheduler.cpp
74.07% <100.00%> (-15.22%)
:arrow_down:

src/request_tracing.cpp
71.19% <100.00%> (+2.88%)
:arrow_up:

src/security/context.cpp
68.63% <ø> (ø)

src/tracing_library.cpp
82.75% <100.00%> (-7.12%)
:arrow_down:

src/datadog_variable.cpp
73.18% <0.00%> (-6.67%)
:arrow_down:


Create a command to add a user to the repo

This was finished in the latest master commit (0fc4a1f2f9e0560faa4f8ce2c01b9ae92a28c313)