Add Windows Support

Inspired by https://github.com/bazelbuild/bazel-integration-testing/pull/96, I also gave it a try.
I enabled all tests but BazelBaseTestCaseTest because it tries to run Bazel from a directory path longer than 260 characters, which caused the following error:
Executing tests from //:IntegrationTestSuiteTest/bazel0.23.2
-----------------------------------------------------------------------------
Error: Current working directory has a path longer than allowed for a
Win32 working directory.
Can't start native Windows application from here.

external/bazel_tools/tools/test/test-setup.sh: line 232: C:/src/tmp/l7b3czla/execroot/build_bazel_integration_testing/_tmp/b8fc8754c3be87e0fe08dc8ef9e1fd51/ajlaysar/execroot/build_bazel_integration_testing/bazel-out/x64_windows-fastbuild/bin/IntegrationTestSuiteTest/bazel0.23.2.exe: File name too long
/c/src/tmp/l7b3czla/execroot/build_bazel_integration_testing/_tmp/b8fc8754c3be87e0fe08dc8ef9e1fd51/ajlaysar/execroot/build_bazel_integration_testing/bazel-out/x64_windows-fastbuild/testlogs/IntegrationTestSuiteTest/bazel0.23.2/test.log (END)

@laszlocsomor Does the native test wrapper supports running Bazel from a long path? Maybe it could help fix this issue.
Another test case testRepositoryCacheIsFrozen in WorkspaceDriverIntegrationTest.java depends on the WorkspaceDriver.freeze(). The freeze() function doesn't work on Windows, and there is basically no way to prevent other process writing to a directory. So I cannot find any other way to freeze the cache. I worked around this by changing the url to a non-existing host which caused a "Unknown host" error to be caught. @ittaiz @hchauvin Is this ok with you?

@laszlocsomor Does the native test wrapper supports running Bazel from a long path? Maybe it could help fix this issue.

No. CreateProcessW fails with 208 if the program's path in lpCommandLine is long, or with 267 if the lpCurrentDirectory is long.

@ittaiz @hchauvin This change is ready for review, the tests are passing on Windows.
One question, do we actually need the freeze function in WorkspaceDriver? Because I cannot find any way to implement that on Windows.

To me this is good to merge. I'm going to give @ittaiz 24 hours (March 15th at 1pm PDT, 4pm EDT) then I'll submit this. After that I'll update the iBazel binary to the latest version and push out a 0.10 release that theoretically works with windows :smile:
GREAT work!

Turns out I have a bunch of stuff going on that would prevent me from doing this until tomorrow afternoon unless I do it now and we are pretty close to the deadline I prescribed. If there is an issue with this then I think we should do a follow up pr. Thanks so much for sending this in! Merging

Finally taking a look. I think we will have a few issues. I'll mention them here even though it's merged

Update- we have one main issue with the repositoryCache.freeze and the test.

another update- this PR introduced a significant issue in the form of downloading remote_jdk.
Since 0.21 Bazel will try by default to download a remote jdk unless instructed otherwise. When @meteorcloudy changed (and effectively removed) the frozen repository cache test they actually removed the one test that verified this library works with network isolation.
This issue happened because this PR did a couple of things since a PR that only updated the versions surfaced this issue PR, log.
I'm working on a solution but it's not baked in yet.
@cushon @lberki,
If I need to run bazel in a test with network isolation would you recommend passing JavaRuntimeInfo.java_home and then using --host_javabase=@bazel_tools//tools/jdk:absolute_javabase with a --define=ABSOLUTE_JAVABASE= which will point to the path I pass from the outside (dir in runfiles)?
Is there a simpler solution?
Thanks!

@ittaiz Thanks for looking into the issues, sorry I didn't consider it in advance, please tell me if I can help with anything!

Sure.
I think the main takeaway is to be super careful when changing existing
tests.
I'm waiting for a bit of input from Irina/Cushon about my take (
https://groups.google.com/forum/#!topic/bazel-sig-jvm/JrJldaI40PM) and
hopefully I will be able to continue
On Mon, Mar 18, 2019 at 11:14 AM Yun Peng<EMAIL_ADDRESS>wrote:

@ittaiz https://github.com/ittaiz Thanks for looking into the issues,
sorry I didn't consider it in advance, please tell me if I can help with
anything!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/bazel-integration-testing/pull/117#issuecomment-473828428,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF1FeBRtXmkFPztmdm0EGfg99Lk8Xks5vX1kOgaJpZM4brWBO
.


Permission to use this project in a video

Hey @angelguzmaning, I couldn't find your contact info so I figured I'd just open an issue.
I teach engineers how to do DevOps (setting up CI/CD pipelines, on-call rotations, monitoring, etc). I'm putting together a free video to show engineers the modern way of deploying and monitoring software. Instead of making my own example app I'd love to use this as a demo. I couldn't find the code license anywhere, are you ok with me doing this?
If you're not, that's cool! I was just really impressed with all the modern best practices you've done here.

Hey @jamsea, you are totally welcome to use this project as a demo, good luck with your video!


operator [O] seldon-operator (1.16.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

Hey @J0zi @mvala @mporrato @Allda ,
Just realised after publishing this one in #2697 that the OpenShift range didn't get updated to include 4.12. This PR extends the supported to range to include 4.12.
Would it be possible to accept this one?

/hold cancel

/merge possible

/merge possible


[bug] I/O sidebar toggles back and forth with the official side button

Describe the bug
我电脑上 mac ，comfyui是源码本地配置，在使用最新的comfy_mtb插件执行MTB: Browse inputsand outputs directories.时，一直出现TypeError: unsupported operand type(s) for +: 'int' and 'NoneType'报错。### （好像新版本已经给予了修复）
但是现在又出现一个新问题：就是comfy_mtb插件的侧边按钮【浏览输入和输出目录】与官方侧边按钮来回切换的错误：比如我热点放在（MTB: Browse inputsand outputs directories.）上，但我想切换到（管理节点组）或者（工作流）上，就要点击两次。但是如果是（管理节点组）与（工作流）之间切换就很丝滑。这一定是一个问题？还望解决。谢谢！

DEEPL TRANSLATION:

I have mac on my computer, comfyui is source local configuration, and when using the latest comfy_mtb plugin to execute MTB: Browse inputsand outputs directories. it keeps getting TypeError: unsupported operand type(s) for +: 'int ' and 'NoneType' error. ### (seems like the new version has given a fix)

But now there's a new problem: it's the error of switching back and forth between the comfy_mtb plugin's side button [Browse inputs and outputs directories] and the official side button: e.g. if I have the hotspot placed on (MTB: Browse inputsand outputs directories.) but I want to switch to (Manage Node Groups) or (Workflows), I have to click twice. But switching between (Manage Node Groups) and (Workflow) is silky smooth. This must be a problem? I hope this can be solved. Thank you for your help!

Reproduction
No response
Expected behavior
No response
Operating System
Windows (Default)
Comfy Mode
Comfy Portable (embed) (Default)
Console output
No response
Additional context
No response

how to use ?  there is nothing

@cardenluo can you open a dedicated issue with some logs? I can't do much with only a screenshot
@BannyLon please translate your tickets even if using automatic tools

@BannyLon After translating your issue I'm not sure to understand it! But I did not try it on mac yet, I usually test on mac before pushing but did not for the I/O sidebar

I have created a GIF that should clearly show the problem. When switching functions on the sidebar, once you want to switch from (MTB: Browse inputs and outputs directories.) to (Management node group) or (Workflow), you need to click twice in a row.

@BannyLon After translating your issue I'm not sure to understand it! But I did not try it on mac yet, I usually test on mac before pushing but did not for the I/O sidebar翻译完你的问题后，我不确定能不能理解它！但我还没有在 mac 上尝试过，我通常在推送之前在 mac 上测试，但没有为 I/O 侧边栏进行测试

I understand, (management node group) is a third-party plugin, so there is a problem when switching functions between the two, which means that one must be closed before the other can be opened. If you switch to the official side functions, there will be no problem.

@cardenluo can you open a dedicated issue with some logs? I can't do much with only a screenshot
@BannyLon please translate your tickets even if using automatic tools

I donot know what happen ,after updated all core and plugin , it run ok now.

@BannyLon After translating your issue I'm not sure to understand it! But I did not try it on mac yet, I usually test on mac before pushing but did not for the I/O sidebar翻译完你的问题后，我不确定能不能理解它！但我还没有在 mac 上尝试过，我通常在推送之前在 mac 上测试，但没有为 I/O 侧边栏进行测试

I understand, (management node group) is a third-party plugin, so there is a problem when switching functions between the two, which means that one must be closed before the other can be opened. If you switch to the official side functions, there will be no problem.

I think I see what you mean after trying in a more stressful setup! I need to properly handle "abort" (when the panel close) currently requests are sent in bulk without any tracking so they all resolve even if you close the panel, opening it and closing it quickly show the issue more clearly!
I'll close this issue once fixed (today or next week)


[Feature Request] Add support for expand/collapse text option in menu bar

Hi, I am a big fan of using the expand/collapse option in my text, to make it more easy to read. Can you add the option in the menu bar to add this section more easily? BrMarkus

Hello
  World!

Hi,
The purpose of this plugin is to improve rendering of notes in the editor. So this request does not fit in with the features of this plugin.
Maybe you will find the template plugin useful.


clarify basic usage

Starting with this package was confusing, so here's how I would clarify the tutorial.
also helps understand issue #58

Thanks for the PR.  Sorry, I didn't notice this pull request earlier.
I kept the warning but reverted the changes to the example to maintain consistency with the rest of the docs, which refer back to those lines.  If you feel those changes are necessary, lets discuss it further.
Cheers.

ok.


[Docs] Need to update latest api.yaml files, github release tag locations and postman collections in the docs after release

Need to :

[x] Update github url for the swagger location in the api.yaml files with the public GitHub release tag (4.3.0 ref [1])
[x] Update postman collection URLs (4.3.0 ref [2])
[x] Update the api.yaml files in the docs after all feature PRs are merged / 4.3.0 release

Originally posted in https://github.com/wso2/api-manager/issues/2410#issuecomment-1932124723
[1] https://github.com/wso2/docs-apim/issues/6781
[2] https://github.com/wso2/api-manager/issues/1076

Closing since the API docs are updated.


Add tutorial for Write activity

Added the tutorial for Write activity

Nice work.
Could you add also description for new features subscript/superscript, see https://github.com/llaske/sugarizer/pull/497


Fixed min css broken link issue.

Did they really change the domain without a proper redirect? :-(
If you are part of the project, please make sure that minfwk.com redirects to mincss.com, probably with a permanent redirect.

Well yes, minfwk.com appears quite implicit, as compared to mincss.com. In any case, I am not part of the project, I was just passing by, so to speak.

Hey - I'm the creator of Min. The domain was changed a while back (1.5 years ago) and originally it was a 301 redirect but somehow that broke a while back. I've changed it back to a 301 which should hopefully work. Thanks for the heads-up!

No problem! :smile:


Control over whitespace after components

This is sort of a general HTML problem I face all the time, but is exacerbated by component libraries like this and I was wondering if there is an elegant way to fix this.
Imagine you want to render a comma separated list of links ( tags). So, simplified:
foo, bar, baz

This works, because you can directly put the comma after the tag, without any whitespace.  But if you're using a component library (such as this one), the link component usually ends up outputting extra whitespace or a newline after the component. Example:
<.link to="/" label="foo" />, <.link to="/" label="bar" />, <.link to="/" label="baz" />

This doesn't render correctly, there's a space between the end of the link and the comma.
The only recourse I generally have is to just manually construct the HTML, which sticks out like a sore thumb. Is it possible to remove the trailing space/newline from the link component?

Hi @doughsay ,
Thanks for this - I pushed a fix - can you try out version 0.10.8.
Code: https://github.com/petalframework/petal_components/commit/1e5c21b84094de99cb119cf369426b75e8a871af

Beautiful!  And so fast!  Thanks!  Works perfectly!


creat windows store button

Issue #40
Created a windows store button. Used tailwindcss.

Good job @madmaxWMFU
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


Using Mixins to add common fields to a model doesn't work

I tried using a mixin with some common fields, but it doesn't work:
class CeleryTaskMixin:
    celery_status = models.CharField()  # last known status, call update_status
    celery_id = models.CharField()      # celery uuid
    f_name = models.CharField(indexed=True)

class RunningTask(CeleryTaskMixin, models.Model):
    def __init__(self, t=None, *args, **kwargs):
        CeleryTaskMixin.__init__(self)
        models.Model.__init__(self)

    task_type = models.CharField()
    start_time = models.DateTimeField(auto_now=True)
    end_time = models.DateTimeField()

Then when I try and do
models.RunningTask.objects.filter(f_name="blah")

It says
  File "/home/stu/.virtualenvs/ng/src/redisco/redisco/models/modelset.py", line 52, in __iter__
    for id in self._set:
  File "/home/stu/.virtualenvs/ng/src/redisco/redisco/models/modelset.py", line 294, in _set
    s = self._add_set_filter(s)
  File "/home/stu/.virtualenvs/ng/src/redisco/redisco/models/modelset.py", line 317, in _add_set_filter
    (k, self.model_class.__name__))
redisco.models.exceptions.AttributeNotIndexed: Attribute f_name is not indexed in RunningTask class.

This seems like something that should work... (?)

Ah, I made the baseclass extend the Model as well and things seem to work ...  but does that mean I now have two classes ?

DOH - I was initializing the Model constructor like models.Model.__init__(self) not models.Model.__init__(self, *args, **kwargs)


add cni plugin config file max num config

Make cni plugin config file num configurable， let containerd can make mutil network card
#1154

/ok-to-test

Waiting for document change, otherwise LGTM

@Random-Liu I'm fine with merging this and doing a follow up for the text descriptions. The code is fine!

/lgtm
@mikebrow Can you send a doc update? Thanks!

sure first thing in the morn...


Open story after downloading?

How do I open a story after downloading ti to view the actual content (images/videos)?

@DummyAccount12345 once you have downloaded the snap/story you have the media saved in /stories and /snaps folders
Regards

Yes I know that, but what is the way to view the content of the story? What is it's file type? How do I view all the images/videos in it?

@DummyAccount12345 basically .jpg images and .mov or .avi filetypes


*: bump the Go compiler version to 1.13

For the 3.0 branch.
See also https://github.com/pingcap/parser/pull/593

PTAL @zimulala @pingcap/co-parser


Allanime WebWiew error

Source information
AllAnime 14.31
Source language
English
Steps to reproduce

View an anime page
Press on webview
Shows "Error Page" on allanime (allanimenews.com) website

Expected behavior
Showing webview of the anime
Actual behavior
Directing to "Error Page" of Allanime
Aniyomi version
Preview r7509
Android version
Android 14
Other details
Adding that with edit, there is also another problem. "Remember and switch to the last used volume" function doesn't work properly. Even though the last volume is 5 for example, it's stuck at 6 and always opens anime with 6 volume
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Actual behavior
Directing to "Error Page" of Allanime

That's a cloudfare issue, which you might resolve on your own - or maybe not.
Have you tried the troubleshooting yet, as described in the wiki?

"Remember and switch to the last used volume" function doesn't work properly. Even though the last volume is 5 for example, it's stuck at 6 and always opens anime with 6 volume
That's a issue for the main repo

No, it's not about cloudflare

Actual behavior
Directing to "Error Page" of Allanime

Error-Screenshot

That's a cloudfare issue, which you might resolve on your own - or maybe not. Have you tried the troubleshooting yet, as described in the documentation?

"Remember and switch to the last used volume" function doesn't work properly. Even though the last volume is 5 for example, it's stuck at 6 and always opens anime with 6 volume

That's a issue for the main repo, not here in the extensions

For other problem, looks like I edited it in wrong place


[Usersnap] Incorrect information box. Abstain shows a no-confidence definition.

Add a comment: Incorrect information box. Abstain shows a no-confidence definition.
Screen size: 1920 x 1080
Browser: Chrome 119 (Windows 10)
Referer: SanchoNet Govtool
Open #17 in Usersnap

Text for Abstain needs to be written. This is issue #1139
Closing this in deference to above issue


Adding Skid Steer to Rover Airframe

Feature Request
I'd really like a skid steer option for driving my tank-style rover. Is it possible?

@bb028114 I guess it is. But most of the maintainers and developers are overwhelmed with other todo's and duties, so you probably have to adventure your self in it.

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Reject-slashes-in-ids

267
Description
Add validation + tests so ids of some objects are rejected if they contain forward slashes.
PR Checklist

[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My code follows the code style of this project.
[ ] I ran the lint checks which produced no new errors nor warnings for my changes.
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change.

Does this introduce a breaking change?

[ ] Yes
[x] No

Testing
Run project/package tests.

@agarwal-navin if you have a chance, I'd appreciate any thoughts. The main things I'm unsure about is if there's anywhere else that needs similar checks, and/or if I put them somewhere where they aren't necessary / don't make sense? 😄 I tried to cover both tasks in ADO here (data store and dds/channel).

@agarwal-navin I think I managed to cover the scenarios you mentioned. I've not been able to set up end-to-end tests with a full container actually running, just unit tests, but based on my understanding so far they seem sufficient; if there's a particular scenario that you or @anthony-murphy can think of and isn't covered yet, let's discuss, otherwise I think I'll call this PR ready.
Overall, I tried to stick to "if there's a way to create X directly outside of its package (either instantiating or through a method that's part of the public API of the package), validate with a UsageError, otherwise assert". So:

UsageError for:

SharedObject/SharedObjectCore constructors
createRootDataStore and createDetachedRootDataStore methods of container runtime
FluidDataStoreRuntime constructor and its createChannel method

assert for:

createDetachedDataStoreCore method of DataStores (the plural one, not DataStore)
LocalChannelContextBase and RemoteChannelContext constructors
generateHandleContextPath function in runtime-utils. Seems like this is the very "bottom" of creating an id/path where slashes mess things up?

Looking into the failed tests, apparently one of the asserts was hit in the CI build but I'm not seeing errors locally:

Can you please update the title and description to reflect that this is for data store and DDS ids. Also, add link to the task for DDS.


[SPARK-45882][SQL][3.5] BroadcastHashJoinExec propagate partitioning should respect CoalescedHashPartitioning

This pr backport https://github.com/apache/spark/pull/43753 to branch-3.5

What changes were proposed in this pull request?

Add HashPartitioningLike trait and make HashPartitioning and CoalescedHashPartitioning extend it. When we propagate output partiitoning, we should handle HashPartitioningLike instead of HashPartitioning. This pr also changes the BroadcastHashJoinExec to use HashPartitioningLike to avoid regression.
Why are the changes needed?

Avoid unnecessary shuffle exchange.
Does this PR introduce any user-facing change?

yes, avoid regression
How was this patch tested?

add test
Was this patch authored or co-authored using generative AI tooling?

no

thanks for review, merging to branch-3.5

Hi, @ulysses-you and @cloud-fan .
If you don't mind, please adjust the JIRA type properly before backporting.


[FEATURE] Data Insert Logic - Officer

Extend the Flask API to read from a .jsonl file of scraped Officers data and insert it into the Postgres DB.
Is your feature request related to a problem? Please describe.
As part of our data ETL pipeline, we need to transform data that has been scraped and loaded into an S3 bucket and load it into our database. This feature focuses on loading officer data.
Describe the solution you'd like

Read data from the attached officers.jsonl file
Transform the data so that it conforms to our officer data schema
Verify that the officer data is not a duplicate of some data that was previously loaded (and update if changed)
Load the officer data into the database

Additional context
Data from a scraper is a requirement for this task.

50a.jsonl.zip


Can't open on High Sierra

As per READ.ME, this app will work on Sierra and newer, but my Hackintosh can't run it and crash with following details below.

AboutThisHackError.txt
Send me <IP_ADDRESS>.zip

can you try this latest build? I made a ton of changes since that release:
https://drive.google.com/file/d/1Yq_M2M6xOI0SOXwh1JlagsrzdC6XGxk0/view?usp=sharing

can you try this latest build? I made a ton of changes since that release: https://drive.google.com/file/d/1Yq_M2M6xOI0SOXwh1JlagsrzdC6XGxk0/view?usp=sharing

Still crashing.

interesting. You seem to have the same issue as #39, so I will close this one and move over there.


Site performed redirection too many times

Example URL(s)
https://voensklad24.ru/
Actual Behavior
Hi. Yesterday connected the site to cloudflare and it stopped working for me. Here is the text of the error: "Site voensklad24.ru performed redirection too many times." On the tracker to the site go visitors, in the volume that usually, but we can not get to the site. How to solve the problem? Thanks in advance.
Expected Behavior
Hi. Yesterday connected the site to cloudflare and it stopped working for me. Here is the text of the error: "Site voensklad24.ru performed redirection too many times." On the tracker to the site go visitors, in the volume that usually, but we can not get to the site. How to solve the problem? Thanks in advance.
Additional information
No response

Hi @ultraPHP
This is a documentation repository and we do not provide direct support for customer issues.
You should check the ERR_TOO_MANY_REDIRECTS page for possible reasons for this problem and how to address them, or reach out to the Cloudflare Community if your issue persists. Depending on your Cloudflare plan, you could also contact support.


Add separate list for hosts that needs to be removed

If any hostname needs to be removed, add it to the removed_hosts list.
Old entries can be removed. This makes the task faster and avoids
missing hostnames during the run of playbook

hi, i don't like the concept of having a removed_hosts variable. The regular convention would be the mark a hosts entry as sth like state: absent ie:
hosts:
  - { ip: '<IP_ADDRESS>', domain:'foobar.com', state: absent }

Since if your using only this role to manage your hosts entries I figured it would be more convenient to just remove all hosts first and add all the given ones again. Don't know how many entries you have but I don't think that's much of a performance issue...
What exactly do you mean by "avoids
missing hostnames during the run of playbook"

My idea was to add new hosts to the hosts list and when any of them needs to be removed, then just move the line to the removed_hosts which is very simple task. Later on it can be removed completely but it doesn't harm if it stays in this list (only makes task runtime longer).
Right now I see that the problem is even bigger and I actually didn't fix that properly (I'll prepare change later on). tasks/reset.yml removes always all existing hosts and does it as many times as many are hosts in the list (with_items: hosts). During this time there will be no hosts in /etc/hosts file. With long list of hosts, this takes also long time. This is why I saw big win because my removed_hosts list was very short.
After that tasks/add.yml adds them back one by one. All hosts will be back after this task finishes.
In my case the link between management station and server is not very fast. I see noticeable delay and the whole process takes sometimes up to minute. Half of this time the /etc/hosts file is completely empty (ie doesn't have entries added by Ansible) and then some systems start failing with the name lookup.
https://github.com/mivok/ansible-users works similar way (lists users and users_deleted)

Ah, now I see what you mean.
The iteration shouldn't have been there for the reset of cause! Missed that one, THX.
I added a hosts_reset variable to control the role's behavior and the state variable on each host item.
That should work for you now.
NOTE: I renamed the tags so your comment on galaxy with "--skip-tags=reset" doesn't apply any more! Use the hosts_reset: no way.
Cheers

Thanks! This is even better :+1:


Cocoapod?

Please? ;-)
Seriously, this would be a great pod.

Would you be willing to contribute one?  I don't use pods myself and have done it very wrong in the past.

I might be able to do that... Let me look into it. We have a need of integrating a good check library into our project, and a strong preference for Cocoapods where possible...

I'd appreciate anything you could do.

Started looking into this – but I'm having trouble with a few things. Would be nice to have the docs improved to include information on how to build and install into other projects, etc.
Right now – seem to be a bit stuck on how to generate a framework for inclusion in an iOS Project.
Also running into some build problems during podding... will come back to those. If you can give a little advice on your build setup / install instructions that could prove helpful.

You're right in that the README should definitely have installation instructions.  As for the failing pod builds, can you be more specific?

Yep... here's the error I'm trying to figure out. The build works fine in Xcode, but during podding I get this...
/Users/zbeckman/Projects/SwiftCheck/SwiftCheck/TestOperators.swift:120:13: error: cannot load underlying module for 'XCTest'
import func XCTest.XCTFail
^
** BUILD FAILED **
The following build commands failed:
CompileSwift normal x86_64 /Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Arbitrary.swift
CompileSwift normal x86_64 /Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Check.swift
CompileSwift normal x86_64 /Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Equatable.swift
CompileSwift normal x86_64 /Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Gen.swift
CompileSwift normal x86_64 /Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Lattice.swift
CompileSwift normal x86_64 /Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Modifiers.swift
CompileSwift normal x86_64 /Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Property.swift
CompileSwift normal x86_64 /Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Random.swift
CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
(9 failures)
-> SwiftCheck (1.0.0b)
- ERROR | [iOS] Returned an unsuccessful exit code.
- ERROR |  /Users/zbeckman/Projects/SwiftCheck/SwiftCheck/TestOperators.swift:120:13: error: cannot load underlying module for 'XCTest'

Ah!  Take a look at how other frameworks that need to link XCTest get around that.  We use header search paths to trick Xcode; I'm not sure how to do that with Pods tho.

Here's Quick

Aha! Thanks that helps...

Alright, this is a bit frustrating – not sure if you are more familiar with the command line compiler than I am. I don't use it...
Running into a problem where overloaded operators (such as <^>) are throwing errors during compile:
/Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Gen.swift:205:13: error: operator implementation without matching operator declaration
public func <^> <A, B>(f : A -> B, g : Gen) -> Gen {
/Users/zbeckman/Projects/SwiftCheck/SwiftCheck/Rose.swift:30:12: error: operator is not a known binary operator
return f <^> self
Now, obviously these are declared in Operators.swift. My first thought was to try and import the SwiftCheck package – but that doesn't work ("can't import package being compiled"). If you have any ideas please do holler... will research more, but I have to get back to a few other things for this afternoon...

They come from another TypeLift package called Operadics.

You're gonna want to enable submodules and let the pod see External/Operadics

With the merging of #83 SwiftCheck is now registered with Cocoapods and includes a podspec on the 1.2 side.
I believe that is the end of this issue, then.  Closing.

Awesome! Looking forward to seeing it pop into the swift 2 branch.

Hm... Just tried (on my own fork) adding the podspec to swift-develop – The pod downloads and integrates just fine, but during compile I get a lot of compiler errors re: "not a legal operator." Looks like Operadics is not getting pulled into the project. So, it would seem that if you are using a purely Cocoapod setup a piece is still missing...?

Operadics was added post-1.2 as we split Swiftz into a bunch of other frameworks.  If you want it you have to add the Operadics directory to the source locations pods will search.


Wrong URL in install.sh for install of13

If trying install CPqD by
$./mininet/util/install.sh -n3f
An error will be occurred as fllow:
--2017-10-18 16:56:28--  http://www.nbee.org/download/nbeesrc-feb-24-2015.zip Resolving www.nbee.org (www.nbee.org)... <IP_ADDRESS> Connecting to www.nbee.org (www.nbee.org)|<IP_ADDRESS>|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2017-10-18 16:56:29 ERROR 404: Not Found.
That's because nbee.org no more provide thire source code in www.nbee.org. They move thier things to github which is https://github.com/netgroup-polito/netbee.git. So please change it.
By the way, this install.sh is very not friendly for Ubuntu 16.10, some library like libxerces-c2-dev is no more in the new version. Ofsoftswitch13 changes thier README and use new libxerces which is libxerces-c3.1.

this is fixed i think, at least i can install the tools by using the install script


[cli] MySQL Diesel only supports tables with primary keys.

Setup
set DATABASE_UR with DB server URL.
Make new migration which contents:
CREATE TABLE junk (
    id BIGINT(20) UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY,
    something VARCHAR(20)
);

-- OR --
CREATE TABLE junk (
    id BIGINT(20) UNSIGNED AUTO_INCREMENT NOT NULL,
    something VARCHAR(20),
    PRIMARY KEY (id)
);

-- OR --
Any other valid SQL syntax to make a table with a PRIMARY KEY
Versions

Rust: rustc 1.52.1 (9bc8c42bb 2021-05-09)
Diesel CLI: v1.4.1
Database: mysql  Ver 8.0.25 for Win64 on x86_64 (MySQL Community Server - GPL)
Windows 10

Problem Description
do:
diesel migration run
What is the expected output?
Running migration 2021-05-18-193949_junk
What is the actual output?
Running migration 2021-05-18-193949_junk
Diesel only supports tables with primary keys. Table junk has no primary key

Checklist

[x ] I have already looked over the issue tracker  and the disussion forum  for similar possible closed issues.
[ x] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)
[x ] This issue can be reproduced without requiring a third party crate

I cannot reproduce this behaviour with both migrations you've provided. Feel free to add additional information that may help reproducing this problem, like:

Running the following query and provide the output:

USE information_schema;

select column_name, table_name
from key_column_usage
where table_name = 'junk' and constraint_name IN (
    select constraint_name from table_constraints where constraint_type = 'PRIMARY KEY'
)

Provide a complete dump of your schema after the table was created.

Closed as cannot reproduce. (We will reopen this issue if there is any way to reproduce it)

+-------------+------------+
| COLUMN_NAME | TABLE_NAME |
+-------------+------------+
| id          | junk       |
+-------------+------------+

I've also now try testing it with Ubuntu thru WSL2 as well as from other Linux machine on the same network and getting the same error so not sure why you can't reproduce.

Just something else I noticed the generated schema.rs file is completely empty but the junk and __diesel_schema_migrations tables are create correctly as I would expect from past use of the cli.

Hmm, that's strange. That result looks correct. We have tests for this as well, so it's quite surprising to hear that it does not work. It might be useful to run those tests locally to see if they are working as expected for your installation. If that's the case the error would be somehow related to your table definition, if that's not the case we would know that this is a general issue. You can run the tests by doing the following steps:

Clone the diesel repo and checkout the 1.4.x branch
change into the diesel_cli folder
run DATABASE_URL=mysql://some/url/to/test_db cargo test --no-default-features --features "mysql"

These test cases contain several similar table constructions, so it seems unlikely that this is not catched there.

I've also looked at and tries some migrations from an old project where I was using diesel where I know I don't have any problems and they are also showing the same error now with the new cli version so looks like it's some kind of strange regression going on.
I'll take a look at try out the tests I'm also looking at a fork I seem to have made around the same time to see if there's something I did there that fixed any issues I might have been having at the time and I just forgot to do a PR for them ;) Once I remember how to bring in the upstream changes I'll see what I find on that front as well.

The tests panic because you've likely used a connection with insufficient permissions. Those tests need to be able to create and drop databases.

CI workflows are great but they don't always show things that can crop up when running stuff directly on a local machine without being very careful to make sure they use the same environment etc. Docket images can lead to the same kind of issues as well plus their own special flakiness.

I'm happy to get suggestions on how to improve our testing story, but I feel there is really not much we can do to ever test all potential environments.

SELECT * FROM information_schema.USER_PRIVILEGES WHERE GRANTEE = '''rocket_test''@''localhost''';
+---------------------------+---------------+----------------------------+--------------+
| GRANTEE                   | TABLE_CATALOG | PRIVILEGE_TYPE             | IS_GRANTABLE |
+---------------------------+---------------+----------------------------+--------------+
| 'rocket_test'@'localhost' | def           | SELECT                     | NO           |
| 'rocket_test'@'localhost' | def           | INSERT                     | NO           |
| 'rocket_test'@'localhost' | def           | UPDATE                     | NO           |
| 'rocket_test'@'localhost' | def           | DELETE                     | NO           |
| 'rocket_test'@'localhost' | def           | CREATE                     | NO           |
| 'rocket_test'@'localhost' | def           | DROP                       | NO           |
| 'rocket_test'@'localhost' | def           | RELOAD                     | NO           |
| 'rocket_test'@'localhost' | def           | SHUTDOWN                   | NO           |
| 'rocket_test'@'localhost' | def           | PROCESS                    | NO           |
| 'rocket_test'@'localhost' | def           | FILE                       | NO           |
| 'rocket_test'@'localhost' | def           | REFERENCES                 | NO           |
| 'rocket_test'@'localhost' | def           | INDEX                      | NO           |
| 'rocket_test'@'localhost' | def           | ALTER                      | NO           |
| 'rocket_test'@'localhost' | def           | SHOW DATABASES             | NO           |
| 'rocket_test'@'localhost' | def           | SUPER                      | NO           |
| 'rocket_test'@'localhost' | def           | CREATE TEMPORARY TABLES    | NO           |
| 'rocket_test'@'localhost' | def           | LOCK TABLES                | NO           |
| 'rocket_test'@'localhost' | def           | EXECUTE                    | NO           |
| 'rocket_test'@'localhost' | def           | REPLICATION SLAVE          | NO           |
| 'rocket_test'@'localhost' | def           | REPLICATION CLIENT         | NO           |
| 'rocket_test'@'localhost' | def           | CREATE VIEW                | NO           |
| 'rocket_test'@'localhost' | def           | SHOW VIEW                  | NO           |
| 'rocket_test'@'localhost' | def           | CREATE ROUTINE             | NO           |
| 'rocket_test'@'localhost' | def           | ALTER ROUTINE              | NO           |
| 'rocket_test'@'localhost' | def           | CREATE USER                | NO           |
| 'rocket_test'@'localhost' | def           | EVENT                      | NO           |
| 'rocket_test'@'localhost' | def           | TRIGGER                    | NO           |
| 'rocket_test'@'localhost' | def           | CREATE TABLESPACE          | NO           |
| 'rocket_test'@'localhost' | def           | CREATE ROLE                | NO           |
| 'rocket_test'@'localhost' | def           | DROP ROLE                  | NO           |
| 'rocket_test'@'localhost' | def           | APPLICATION_PASSWORD_ADMIN | NO           |
| 'rocket_test'@'localhost' | def           | AUDIT_ADMIN                | NO           |
| 'rocket_test'@'localhost' | def           | BACKUP_ADMIN               | NO           |
| 'rocket_test'@'localhost' | def           | BINLOG_ADMIN               | NO           |
| 'rocket_test'@'localhost' | def           | BINLOG_ENCRYPTION_ADMIN    | NO           |
| 'rocket_test'@'localhost' | def           | CLONE_ADMIN                | NO           |
| 'rocket_test'@'localhost' | def           | CONNECTION_ADMIN           | NO           |
| 'rocket_test'@'localhost' | def           | ENCRYPTION_KEY_ADMIN       | NO           |
| 'rocket_test'@'localhost' | def           | FLUSH_OPTIMIZER_COSTS      | NO           |
| 'rocket_test'@'localhost' | def           | FLUSH_STATUS               | NO           |
| 'rocket_test'@'localhost' | def           | FLUSH_TABLES               | NO           |
| 'rocket_test'@'localhost' | def           | FLUSH_USER_RESOURCES       | NO           |
| 'rocket_test'@'localhost' | def           | GROUP_REPLICATION_ADMIN    | NO           |
| 'rocket_test'@'localhost' | def           | INNODB_REDO_LOG_ARCHIVE    | NO           |
| 'rocket_test'@'localhost' | def           | INNODB_REDO_LOG_ENABLE     | NO           |
| 'rocket_test'@'localhost' | def           | PERSIST_RO_VARIABLES_ADMIN | NO           |
| 'rocket_test'@'localhost' | def           | REPLICATION_APPLIER        | NO           |
| 'rocket_test'@'localhost' | def           | REPLICATION_SLAVE_ADMIN    | NO           |
| 'rocket_test'@'localhost' | def           | RESOURCE_GROUP_ADMIN       | NO           |
| 'rocket_test'@'localhost' | def           | RESOURCE_GROUP_USER        | NO           |
| 'rocket_test'@'localhost' | def           | ROLE_ADMIN                 | NO           |
| 'rocket_test'@'localhost' | def           | SERVICE_CONNECTION_ADMIN   | NO           |
| 'rocket_test'@'localhost' | def           | SESSION_VARIABLES_ADMIN    | NO           |
| 'rocket_test'@'localhost' | def           | SET_USER_ID                | NO           |
| 'rocket_test'@'localhost' | def           | SHOW_ROUTINE               | NO           |
| 'rocket_test'@'localhost' | def           | SYSTEM_USER                | NO           |
| 'rocket_test'@'localhost' | def           | SYSTEM_VARIABLES_ADMIN     | NO           |
| 'rocket_test'@'localhost' | def           | TABLE_ENCRYPTION_ADMIN     | NO           |
| 'rocket_test'@'localhost' | def           | XA_RECOVER_ADMIN           | NO           |
+---------------------------+---------------+----------------------------+--------------+
59 rows in set (0.00 sec)

So now the user is effectively root and tests still fail as before with panicked while panicking. Other ideas?

The panic while panicing is very likely coming from this Drop impl, which means either you cannot connect to the database using the provided url, or the database cannot be droped. You can verify both cases by commenting out the corresponding code.

I know for regular use DATABASE_URL includes a actual DB part but on the tests should it have one or does it matter?
mysql://rocket_test:xxx@localhost/rocket_test OR mysql://rocket_test:xxx@localhost/?

Did cleanup of some stuff I was trying and switched back to master and I'm getting some other interesting errors now.
error: unused import: `bigdecimal::FromPrimitive`
   --> diesel\src\mysql\connection\bind.rs:602:9
    |
602 |     use bigdecimal::FromPrimitive;
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^
    |
note: the lint level is defined here
   --> diesel\src\lib.rs:98:9
    |
98  | #![deny(warnings)]
    |         ^^^^^^^^
    = note: `#[deny(unused_imports)]` implied by `#[deny(warnings)]`

error[E0308]: mismatched types
    --> diesel\src\mysql\connection\bind.rs:1152:37
     |
1152 |         let conn: MysqlConnection = crate::test_helpers::connection();
     |                   ---------------   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `mysql::connection::MysqlConnection`, found
struct `sqlite::connection::SqliteConnection`
     |                   |
     |                   expected due to this

error[E0308]: mismatched types
    --> diesel\src\mysql\connection\bind.rs:1299:37
     |
1299 |         let conn: MysqlConnection = crate::test_helpers::connection();
     |                   ---------------   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `mysql::connection::MysqlConnection`, found
struct `sqlite::connection::SqliteConnection`
     |                   |
     |                   expected due to this

error[E0308]: mismatched types
    --> diesel\src\mysql\connection\bind.rs:1468:37
     |
1468 |         let conn: MysqlConnection = crate::test_helpers::connection();
     |                   ---------------   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `mysql::connection::MysqlConnection`, found
struct `sqlite::connection::SqliteConnection`
     |                   |
     |                   expected due to this

error: aborting due to 4 previous errors

For more information about this error, try `rustc --explain E0308`.
error: could not compile `diesel`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed

running cargo test --no-default-features --features mysql
I seem to be finding all kinds of interesting stuff which is really not helping track down the root cause here for us of why my setup breaks vs CI etc.

Tried commenting out the drop in diesel_cli/tests/support/mysql_database.rs and I'm still getting:
running 104 tests
thread panicked while panicking. aborting.
thread panicked while panicking. aborting.
thread panicked while panicking. aborting.
thread panicked while panicking. aborting.
thread panicked while panicking. aborting.
thread panicked while panicking. aborting.
thread panicked while panicking. aborting.
thread panicked while panicking. aborting.
error: test failed, to rerun pass '--test tests'

Caused by:
  process didn't exit successfully: `C:\repos\github\diesel\target\debug\deps\tests-022e4ebaed8c79ea.exe` (exit code: 0x
c000001d, STATUS_ILLEGAL_INSTRUCTION)

So that doesn't seem to help. Other ideas I can try?

Could you grab a stack trace via gdb and provide exact steps how to trigger this? Otherwise its not possible to say much about this error.
Just to be sure: You followed the general setup described in the contributing documentation? Otherwise the CI configuration may also contain information about how to get things to work, as this is the way tests work.

This was the original problem that I was trying to describe in my issue (then I got very busy for a week so I wasn't able to follow up on it). I am also having this issue.

@SpBills Just commenting that you have the same issue will not magically fix it. Please provide any details that can help us reproducing the problem. The best approach for this is probably bundling together your migration with some docker container where you can reproduce the issue.

@weiznich I have now tested it with a MariaDB instance in a docker container. It works correctly. Below are some details.
Docker version 20.10.6, build 370c289
diesel 1.4.6
Ubuntu 20.04

@weiznich I have met the same problem when I used mysql:8.0 docker image，but it works correctly when I used mysql:5.7 docker image。

@bigtree9307 Please provide a exact version. 8.0 is quite a large version range.

@weiznich I think it is 8.0.26. The docker image is here https://hub.docker.com/_/mysql?tab=description&page=1&ordering=last_updated

@bigtree9307 Can you additionally provide the following information:

Rust version used to compile diesel-cli
Exact version of diesel-cli
A migration to reproduce the problem

@weiznich
Rust：1.54.0
diesel：1.4.4
diesel-cli：1.4.1
You can just follow the document with mysql 5.7 and 8.0: http://diesel.rs/guides/getting-started

I recently ran into this using Mysql 8.0.26. The curious thing is that the exact same migration sql, and exact same diesel_cli was previously working correctly with Mysql 5.7. I noticed this particular error only after upgrading my database in place to 8.0.26.
Some info first:
MySQL [information_schema]> select VERSION();
+-----------+
| VERSION() |
+-----------+
| 8.0.26    |
+-----------+

[ec2-user@ip-REDACTED ~]$ diesel --version
diesel 1.4.1

Tracing backwards from the error location, I see that it uses this to determine the primary keys for each table. After running diesel migration run, and seeing Table goals has no primary key, I decided to open up mysql and re-trace the queries to see what might be different:
Corresponding to lines 149-151, we query from table_constraints looking for constraint_type of PRIMARY KEY.
MySQL [information_schema]>
select * from table_constraints
where
  table_name = 'goals'
  and constraint_type = 'PRIMARY KEY';
+--------------------+-------------------+-----------------+--------------+------------+-----------------+----------+
| CONSTRAINT_CATALOG | CONSTRAINT_SCHEMA | CONSTRAINT_NAME | TABLE_SCHEMA | TABLE_NAME | CONSTRAINT_TYPE | ENFORCED |
+--------------------+-------------------+-----------------+--------------+------------+-----------------+----------+
| def                | iremono           | PRIMARY         | iremono      | goals      | PRIMARY KEY     | YES      |
+--------------------+-------------------+-----------------+--------------+------------+-----------------+----------+
1 row in set (0.00 sec)

So far, so good. Note that the rust code is only selecting constraint_name, so we get the value PRIMARY out of that row.

Next, lines 153-156 are fairly straightforward, it's just copying the schema name.

Finally, tracing the final query of key_column_usage:
MySQL [information_schema]>
select column_name
from key_column_usage
where
  constraint_name in (select constraint_name from table_constraints where table_name = 'goals')
  and table_name = 'goals'
  and table_schema = 'iremono'
order by ordinal_position;
+-------------+
| COLUMN_NAME |
+-------------+
| id          |
+-------------+

So, as far as I can tell, all of the data is there! (Even after the CLI printed that error, FWIW.)

At this point, my top candidate place to verify is to check that the match table.schema expression is working as intended, so I will go ahead and triple check that. (Also might end up enabling query history logs and dumping what exact queries diesel was running.)

I now believe this is possibly a race condition of some sort, potentially with the information_schema being populated?
See here how it is not deterministic:
[ec2-user@ip-REDACTED]$ diesel migration redo
Rolling back migration 2021-11-28-110249_initial
Running migration 2021-11-28-110249_initial
Diesel only supports tables with primary keys. Table goals has no primary key

[ec2-user@ip-REDACTED]$ diesel migration redo
Rolling back migration 2021-11-28-110249_initial
Running migration 2021-11-28-110249_initial

One thing I should note: I'm on ARM.

@jmqd Thanks for your debugging work :tada:
I think an easy easy way to verify that it is some kind of race condition is to just try using diesel print-schema after diesel emitted the error about the missing primary key.
If that turns to be the issue we should raise a bug at the upstream issue tracker. We could try to workaround this issue by inserting a small sleep period so that mysql could update the information_schema behind the scene.

I seem to be running into this issue.  print-schema blows up with primary key issue.  I did not have any issues on my dev and staging environment.  I created my production database this morning which came up as 8.0.26.  (It appears that previous migrations on daily and staging were done on an earlier version.  They are now also at 8.0.26, but they do not the issue.).   Is there any information I could provide that may help with this issue?

I seem to be running into this issue. print-schema blows up with primary key issue. I did not have any issues on my dev and staging environment. I created my production database this morning which came up as 8.0.26. (It appears that previous migrations on daily and staging were done on an earlier version. They are now also at 8.0.26, but they do not the issue.). Is there any information I could provide that may help with this issue?

I didn't dig any deeper into this issue, as it was not deterministic, and I was able to unblock myself by blowing up the migration and retrying until it went through.
I believe there are three main possibilities, but I have no leads on which is correct:

There's a bug in MySQL 8.0.26, and probably something to do with how information_schema is populated.
There was a change in MySQL 8.0.26 that altered the contract of how diesel uses MySQL during migrations.
There was a performance or other change in 8.0.26 that surfaced a latent bug in how diesel does MySQL migrations (e.g. exposing a race condition or sloppy parallelism).

I seem to be running into this issue. print-schema blows up with primary key issue. I did not have any issues on my dev and staging environment. I created my production database this morning which came up as 8.0.26. (It appears that previous migrations on daily and staging were done on an earlier version. They are now also at 8.0.26, but they do not the issue.). Is there any information I could provide that may help with this issue?

@zdannar Are you also on an ARM machine?

I am not on an ARM machine (Mac Intel and reproducible with linux containers)

My backtrace is produced while it is checking foreign keys.

@zdannar If you have a reproducible container that would be really helpful.
Otherwise, I assume that this is caused by a changed way how mysql updates the information_schema. If it's a purely time based thing, that might be fixable by just adding a small amount of "sleep time" in the right place. Otherwise it could require reopening the connection at all. Testing that would require code modifications and trying out a few variants. If someone is interested in that, this would be a good entry point:
https://github.com/diesel-rs/diesel/blob/4fe987676e7c465f2fdc116fdf11ba4378e64f9a/diesel_cli/src/main.rs#L69-L73
I would probably just start with adding a std::thread::sleep_ms(1000) there between line 72 and 73.
Other than that I can say that variant 3 from @jmqd's list is quite likely not the cause, as there is just no parallelism there. We execute the migrations one by one in order and afterwards the schema file is regenerated.

@weiznich The weird part is that the whole schema is there and looks fine.  Tables, primary keys, foreign keys and such appear to be completely in order.

Just to be sure: Your error happens with diesel migration run, right? Not with diesel print-schema itself.

@weiznich Both.

Can you provide a backtrace for that? This seems like a different kind of issue.

RUST_BACKTRACE=1 diesel print-schema
thread 'main' panicked at 'Error loading primary keys for order_request: "Diesel only supports tables with primary keys. Table order_request has no primary key"', /Users/zack.dannar/.cargo/registry/src/github.com-1ecc6299db9ec823/diesel_cli-1.4.1/src/infer_schema_internals/foreign_keys.rs:34:72
stack backtrace:
0: rust_begin_unwind
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:143:14
2: core::result::unwrap_failed
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/result.rs:1749:5
3: <core::iter::adapters::cloned::Cloned as core::iter::traits::iterator::Iterator>::next
4: <alloc::vec::Vec as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
5: diesel::infer_schema_internals::foreign_keys::remove_unsafe_foreign_keys_for_codegen
6: diesel::print_schema::output_schema
7: diesel::print_schema::run_print_schema
8: diesel::main
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.

So essentially this query is the problem. Can you try to execute the underlying query manually and see what it returns?

I haven't pulled it all apart yet... If you are just looking at the table in question.  ```
select * from table_constraints where   table_name = 'order_request'   and constraint_type = 'PRIMARY KEY';
+--------------------+-------------------+-----------------+--------------+---------------+-----------------+----------+
| CONSTRAINT_CATALOG | CONSTRAINT_SCHEMA | CONSTRAINT_NAME | TABLE_SCHEMA | TABLE_NAME    | CONSTRAINT_TYPE | ENFORCED |
+--------------------+-------------------+-----------------+--------------+---------------+-----------------+----------+
| def                | iod-api           | PRIMARY         | iod-api      | order_request | PRIMARY KEY     | YES      |
+--------------------+-------------------+-----------------+--------------+---------------+-----------------+----------+
1 row in set (0.07 sec)
mysql> select version();
+---------------+
| version()     |
+---------------+
| 8.0.26-google |
+---------------+
1 row in set (0.08 sec)```

A broader look.  SELECT t.table_name, k.column_name, t.constraint_type     -> FROM information_schema.table_constraints t     -> JOIN information_schema.key_column_usage k     -> USING(constraint_name,table_schema,table_name)     -> WHERE t.constraint_type in ('FOREIGN KEY', 'PRIMARY KEY', 'UNIQUE')     ->   AND t.table_schema='SOMEDB'; +----------------------------+-----------------+-----------------+ | TABLE_NAME                 | COLUMN_NAME     | CONSTRAINT_TYPE | +----------------------------+-----------------+-----------------+ | __diesel_schema_migrations | version         | PRIMARY KEY     | | credit                     | id              | PRIMARY KEY     | | order_data                 | id              | PRIMARY KEY     | | order_data                 | id              | FOREIGN KEY     | | order_message              | id              | PRIMARY KEY     | | order_message              | order_status_id | FOREIGN KEY     | | order_metadata             | id              | PRIMARY KEY     | | order_metadata             | id              | FOREIGN KEY     | | order_request              | id              | PRIMARY KEY     | | order_status               | id              | PRIMARY KEY     | | order_status               | id              | FOREIGN KEY     | | vendor                     | id              | PRIMARY KEY     | | vendor_product             | id              | PRIMARY KEY     | | vendor_product             | vendor_id       | FOREIGN KEY     | +----------------------------+-----------------+-----------------+

I started trying to compile a local cli and add some statements, but haven't gotten very far on the compilation.

Can you also provide some content of key_column_usage?

*************************** 1. row ***************************
                   TABLE_NAME: __diesel_schema_migrations
                  COLUMN_NAME: version
              CONSTRAINT_TYPE: PRIMARY KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: PRIMARY
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: __diesel_schema_migrations
                  COLUMN_NAME: version
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: NULL
      REFERENCED_TABLE_SCHEMA: NULL
        REFERENCED_TABLE_NAME: NULL
       REFERENCED_COLUMN_NAME: NULL
*************************** 2. row ***************************
                   TABLE_NAME: credit
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: PRIMARY KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: PRIMARY
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: credit
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: NULL
      REFERENCED_TABLE_SCHEMA: NULL
        REFERENCED_TABLE_NAME: NULL
       REFERENCED_COLUMN_NAME: NULL
*************************** 3. row ***************************
                   TABLE_NAME: order_data
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: PRIMARY KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: PRIMARY
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: order_data
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: NULL
      REFERENCED_TABLE_SCHEMA: NULL
        REFERENCED_TABLE_NAME: NULL
       REFERENCED_COLUMN_NAME: NULL
*************************** 4. row ***************************
                   TABLE_NAME: order_data
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: FOREIGN KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: order_data_ibfk_1
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: order_data
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: 1
      REFERENCED_TABLE_SCHEMA: somedb
        REFERENCED_TABLE_NAME: order_request
       REFERENCED_COLUMN_NAME: id
*************************** 5. row ***************************
                   TABLE_NAME: order_message
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: PRIMARY KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: PRIMARY
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: order_message
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: NULL
      REFERENCED_TABLE_SCHEMA: NULL
        REFERENCED_TABLE_NAME: NULL
       REFERENCED_COLUMN_NAME: NULL
*************************** 6. row ***************************
                   TABLE_NAME: order_message
                  COLUMN_NAME: order_status_id
              CONSTRAINT_TYPE: FOREIGN KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: order_message_ibfk_1
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: order_message
                  COLUMN_NAME: order_status_id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: 1
      REFERENCED_TABLE_SCHEMA: somedb
        REFERENCED_TABLE_NAME: order_status
       REFERENCED_COLUMN_NAME: id
*************************** 7. row ***************************
                   TABLE_NAME: order_metadata
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: PRIMARY KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: PRIMARY
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: order_metadata
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: NULL
      REFERENCED_TABLE_SCHEMA: NULL
        REFERENCED_TABLE_NAME: NULL
       REFERENCED_COLUMN_NAME: NULL
*************************** 8. row ***************************
                   TABLE_NAME: order_metadata
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: FOREIGN KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: order_metadata_ibfk_1
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: order_metadata
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: 1
      REFERENCED_TABLE_SCHEMA: somedb
        REFERENCED_TABLE_NAME: order_request
       REFERENCED_COLUMN_NAME: id
*************************** 9. row ***************************
                   TABLE_NAME: order_request
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: PRIMARY KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: PRIMARY
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: order_request
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: NULL
      REFERENCED_TABLE_SCHEMA: NULL
        REFERENCED_TABLE_NAME: NULL
       REFERENCED_COLUMN_NAME: NULL
*************************** 10. row ***************************
                   TABLE_NAME: order_status
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: PRIMARY KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: PRIMARY
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: order_status
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: NULL
      REFERENCED_TABLE_SCHEMA: NULL
        REFERENCED_TABLE_NAME: NULL
       REFERENCED_COLUMN_NAME: NULL
*************************** 11. row ***************************
                   TABLE_NAME: order_status
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: FOREIGN KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: order_status_ibfk_1
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: order_status
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: 1
      REFERENCED_TABLE_SCHEMA: somedb
        REFERENCED_TABLE_NAME: order_request
       REFERENCED_COLUMN_NAME: id
*************************** 12. row ***************************
                   TABLE_NAME: vendor
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: PRIMARY KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: PRIMARY
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: vendor
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: NULL
      REFERENCED_TABLE_SCHEMA: NULL
        REFERENCED_TABLE_NAME: NULL
       REFERENCED_COLUMN_NAME: NULL
*************************** 13. row ***************************
                   TABLE_NAME: vendor_product
                  COLUMN_NAME: id
              CONSTRAINT_TYPE: PRIMARY KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: PRIMARY
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: vendor_product
                  COLUMN_NAME: id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: NULL
      REFERENCED_TABLE_SCHEMA: NULL
        REFERENCED_TABLE_NAME: NULL
       REFERENCED_COLUMN_NAME: NULL
*************************** 14. row ***************************
                   TABLE_NAME: vendor_product
                  COLUMN_NAME: vendor_id
              CONSTRAINT_TYPE: FOREIGN KEY
           CONSTRAINT_CATALOG: def
            CONSTRAINT_SCHEMA: somedb
              CONSTRAINT_NAME: vendor_product_ibfk_1
                TABLE_CATALOG: def
                 TABLE_SCHEMA: somedb
                   TABLE_NAME: vendor_product
                  COLUMN_NAME: vendor_id
             ORDINAL_POSITION: 1
POSITION_IN_UNIQUE_CONSTRAINT: 1
      REFERENCED_TABLE_SCHEMA: somedb
        REFERENCED_TABLE_NAME: vendor
       REFERENCED_COLUMN_NAME: id
14 rows in set (0.09 sec)

Sorry, I should have included the select statement for reference.
SELECT t.table_name, k.column_name, t.constraint_type, k.* FROM information_schema.table_constraints t JOIN information_schema.key_column_usage k USING(constraint_name,table_schema,table_name) WHERE t.constraint_type in ('FOREIGN KEY', 'PRIMARY KEY', 'UNIQUE')   AND t.table_schema='somedb'\G

I checked this output against the same schema in my dev/staging databases.. no difference.  I have no idea what is going on.

I turned on the general_log and got exactly what was being sent.  It appears that this is a mysql IN clause issue.   (I could have made a mistake though).
SELECT
    `information_schema`.`key_column_usage`.`column_name`
FROM
    `information_schema`.`key_column_usage`
WHERE
    `information_schema`.`key_column_usage`.`constraint_name` IN (
        SELECT
            `information_schema`.`table_constraints`.`constraint_name`
        FROM
            `information_schema`.`table_constraints`
        WHERE
            `information_schema`.`table_constraints`.`constraint_type` = 'PRIMARY KEY'
    )

    AND `information_schema`.`key_column_usage`.`table_name` = 'order_request'
    AND `information_schema`.`key_column_usage`.`table_schema` = 'iod-api'
    ORDER BY `information_schema`.`key_column_usage`.`ordinal_position`;

mysql> SELECT
    ->     `information_schema`.`key_column_usage`.`column_name`
    -> FROM
    ->     `information_schema`.`key_column_usage`
    -> WHERE
    ->     `information_schema`.`key_column_usage`.`constraint_name` IN (
    ->         SELECT
    ->             `information_schema`.`table_constraints`.`constraint_name`
    ->         FROM
    ->             `information_schema`.`table_constraints`
    ->         WHERE
    ->             `information_schema`.`table_constraints`.`constraint_type` = 'PRIMARY KEY'
    ->     )
    ->
    ->     AND `information_schema`.`key_column_usage`.`table_name` = 'order_request'
    ->     AND `information_schema`.`key_column_usage`.`table_schema` = 'iod-api'
    ->     ORDER BY `information_schema`.`key_column_usage`.`ordinal_position`;
Empty set (0.07 sec)

# Decomposing the subselect
mysql> SELECT
    ->             `information_schema`.`table_constraints`.`constraint_name`
    ->         FROM
    ->             `information_schema`.`table_constraints`
    ->         WHERE
    ->             `information_schema`.`table_constraints`.`constraint_type` = 'PRIMARY KEY';
+-----------------+
| CONSTRAINT_NAME |
+-----------------+
| PRIMARY         |
| PRIMARY         |
| PRIMARY         |
| PRIMARY         |
| .......         | // 111 rows of 'PRIMARY'
| PRIMARY         |
+-----------------+
111 rows in set (0.07 sec)

# Ripping out the subselect and doing a direct replacement.

SELECT
    `information_schema`.`key_column_usage`.`column_name`
FROM
    `information_schema`.`key_column_usage`
WHERE
    `information_schema`.`key_column_usage`.`constraint_name` = "PRIMARY"
    AND `information_schema`.`key_column_usage`.`table_name` = 'order_request'
    AND `information_schema`.`key_column_usage`.`table_schema` = 'iod-api'
    ORDER BY `information_schema`.`key_column_usage`.`ordinal_position`;

mysql> SELECT
    ->     `information_schema`.`key_column_usage`.`column_name`
    -> FROM
    ->     `information_schema`.`key_column_usage`
    -> WHERE
    ->     `information_schema`.`key_column_usage`.`constraint_name` = "PRIMARY"
    ->     AND `information_schema`.`key_column_usage`.`table_name` = 'order_request'
    ->     AND `information_schema`.`key_column_usage`.`table_schema` = 'iod-api'
    ->     ORDER BY `information_schema`.`key_column_usage`.`ordinal_position`;
+-------------+
| COLUMN_NAME |
+-------------+
| id          |
+-------------+

I actually run into this issue a couple of years ago.  Trying to find reference to the issue.

I am not sure how to change information_schema.rs.::get_primary_keys to execute the query like this.

This would require to change this section: https://github.com/diesel-rs/diesel/blob/4fe987676e7c465f2fdc116fdf11ba4378e64f9a/diesel_cli/src/infer_schema_internals/information_schema.rs#L262-L277
to something like this:
key_column_usage::table.inner_join(table_constraints::table.on(table_constraints::constraint_name.eq(key_column_usage::constraint_name)))
    .filter(key_column_usage::table_name.eq(&table.sql_name))
    .filter(key_column_usage::table_schema.eq(schema_name))
    .filter(table_constraints::constraint_type.eq("PRIMARY KEY"))
    .select(key_column_usage::column_name)

(Additionally it is required to adjust the where clause above to make this compile.)

I rebuilt the database completely and still have the issue.  I am having to convert all of my code over to postgres but want to see if I can fix this later tonight.

I was able to recreate this with existing pg db. You just need to login as a user who lacks privileges.
User: reader
Role: pg_read_all_data
Fixed this by giving him superuser, but will see what minimal requirements can be made.

@COREjake This issue is about a mysql specific problem. Your comment about postgres specific problems seems to be not right here. Please do not add these off-topic comments to existing issues.

Your comment about postgres specific problems seems to be not right here.
Sorry if it's like that, but this is the only thread on this I found. My finding was that error is too vague and ambiguous. Without the necessary privilege you can still get the same error and wording will be misleading to say the least.
I'm discontinuing any further discussion as it's indeed not the right place, furthermore I solved my issue.


xbindkeys-config: add -fcommon workaround

Description of changes

Workaround build failure on -fno-common toolchains, otherwise the build fails.
See #110571 for additional context
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)
[x] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 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 175779 run on x86_64-linux 1

1 package built:

xbindkeys-config


Rancher-NFS [v0.5.0] (rancher/storage-nfs:v0.9.1) socket file not found at /var/run/rancher/storage/rancher-nfs.sock

Rancher versions:
rancher/server: 1.6.17
rancher/agent: 1.2.10
Infrastructure Stack versions:
healthcheck:  v0.3.6
ipsec: v0.2.3
network-services: v0.2.9
scheduler:v0.8.3-1
Docker version: (docker version,docker info preferred)
17.03.1-ce
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
CentOS Linux release 7.3.1611 (Core)
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS and VM
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Rancher HA, RDS DB
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Create a Rancher Environment
Create an EFS host in AWS
Deploy an EC2 instances into the Rancher Environment with Access to the EFS Share
Deploy NFS Stack with the default host pointing to the EFS host
Create an NFS share in a different network outside AWS.
Create a Volume (VolumeX)  through the Rancher UI  that points to the new NFS share
Create a VM that has access to the newly create NFS share and deploy the server to the Rancher Env
Wait for all cattle stacks and NFS stack to start
Deploy a container using Volume (VolumeX) with  driver rancher-nfs

Results:
Container will fail at startup because of missing nfs socket.
Expected Results:
Once the NFS stack is loaded for the first time on that server the nfs socket needs to be created/initialized regardless if the default storage host is reachable or not.  Once initialized, containers should be able to mount volumes that are reachable from that server.
This has been working fine since rancher 1.6.5 and its currently working on rancher 1.6.10. Upgrading to Rancher 1.6.17 broke the expected behavior.

I'm getting the same issue over Rancher OS.
The nfs-driver shares the volume /var/run with the host, but when I check the folder in the host

but when I look for the file inside the host it just list rancher-ebs.sock file

Rancher version is v1.6.15

I'm getting same issue
environment version 1 <==connection fail
server :1.6.16
rancher/agent:v1.2.10
rancher/storage-nfs:v0.9.1
environment  version 2 <==NFS connection is success
server: 1.6.14
rancher/agent:v1.2.9
rancher/storage-nfs:v0.8.5
and firewall setting same, are close firewall service test

@khcjump my error was because I was using AWS EFS as file system and the hosts where unable to access de NSF because the security group rules wasen't set correctly. The issues was basicly with open port rules over the VPC.

Thanks for your report!
With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.
If you think we should keep this issue open, please let me know.

I'm having the same issue. v2.1 is, IMHO, completely useless. From confusing UI to weird intermittent bugs i.e. socket issues to unstable deploys. I was looking forward to using monitoring, alarms, etc. but returned back to 1.6

For me this was caused because the security group on my rancher NFS AWS EFS mount wasn't allowing traffic from the rancher EC2 instance and thus threw this error.
It was obvious after reviewing logs of container rancher/storage-nfs

good in production time xD


Select chain v2 - proof of concept

This is a prototype, docs are not changed, tests pass (there should be no changes).

I finished.
Please do a final review.

Review fixes are done.

Yes, interdependent fields are permitted.
Behaviour has some UI feature:
When you have strong parent-child relation, selecting a child forces select2 to render only single parent corresponded to this child.
So our example of City/Country (how we construct our models) is not illustrative.
If we suppose that Cities in interface are only names (not ids), and suppose that several Countries can have a city with same name
we could let the user select either country either city first, and then reduce option set for second select2.
But coming back, this is not issue of interdepended select2s it’s an issue of UI.
С уважением, (Best regards)
Алексей Рузин, (Alexey Ruzin)
<EMAIL_ADDRESS>
3 апр. 2017 г., в 15:59, Johannes Hoppe<EMAIL_ADDRESS>написал(а):
@codingjoe approved this pull request.
Code seems good. Regarding documentation: Is the interdependent fields thing actually implemented. I don't know how this is supposed to work... Maybe I'm just understanding it wrong. Than it would need more clarification.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/applegrew/django-select2/pull/321#pullrequestreview-30508714, or mute the thread https://github.com/notifications/unsubscribe-auth/AEDXHOniDwFYLUy3YVpUlMf42FSZfhEIks5rsO00gaJpZM4MOJZX.

docs test failed, but can't figure out is this misspelling of mine (it does not print a cite from my text)

Ok, feel free to fix the documentation.
Let's put this to the test: @ibnbay99 @thinkwelltwd
Do you think you can work with it? Is there anything missing?
I think we need a fresh pair of eyes here. But it looks good from my perspective.

I can't claim full competence to be a fresh pair of eyes. But I would say that it looks good to me, and that I'll be using it as soon as it's merged.

@codingjoe I'm not sure we should wait for @ibnbay99 reaction. Last message from him was at 31 Oct 2016.

@codingjoe what are you waiting for? https://www.youtube.com/watch?v=ttvytBoHEG0 ;-)

hahaha, ok ok ok, I have vacation now. I'll try to test it out and then I'll merge it ;)

If this would make interdependent fields impossible. I'd rather not have interdependent fields. I also don't see the use case for interdependencies. Let's please only support linear or tree dependencies no graphs.
Meaning if a parent value changes, all children should be cleared.

Ok there still is a problem. Lets take the city, country example.
If you select a country and then the city, you can no longer switch countries unless the city is clearable.
I think if you select a new parent the child needs to be cleared.

In fact this not a problem. It's only a problem with interdependent fields when a set of options is not Nullable (e.g. you not able to select empty value, so parent-child row be able show full set of options).
In my point of view this conflict should be resolved by an UI designer. There is several ways to do it:

button to reset all dependent controls
allow to select an empty value, releasing filters in dependent select2s (this may conflict with form validation, which may deny empty values, but checks are made before post, not on selecting an option)
another suitable solution...

Later you wrote:

Let's please only support linear or tree dependencies no graphs.

Yes, we can punch developer for creating interdependent fields, but only at runtime (and at very specific time - rendering a form, because developer still can use hacks to inject dependency after init). But it looks like an advice of BIG BROTHER that tells: "You may do wrong, this is dangerous! Believe us, we know for sure."
I prefer wrote it in documentation, that developer be warned, but be able do what he wants.
Probably they tell us elegant solution for interdependency it the future.
So, what we decide:

let it be as it is (my point of view)
restrict interdependency (you point of view, suggest right place where to check for it)
remove cautions from documentations (not documented - not obligated) :)

Ok, than lets finish this up. Please make sure to fix the doc test. Queryset (capital Q) should work.
Please also add a note about the problem with the interdependent fields.

Check this out: https://gist.github.com/32d2a254c176ed7f74a1afcbad12bc8d
This should fix your doc tests. You can simply do: hub apply https://gist.github.com/32d2a254c176ed7f74a1afcbad12bc8d

Yahoo!

@a-ruzin please rebase on the latest version, to ensure that your changes are 1.11 compatible.

Should I rebase after you merge?

@a-ruzin yes please rebase and fix your the tests you added. They are failing.

I did my best, but test failed at random conditions.
On local machine I have no errors. In Travis it mostly has no errors, but sometimes they are...

@codingjoe, check, please.

@a-ruzin thanks, I fixed the master test and merged. Thank you so much for all your sweat and tears!
Merged in 1931a98
Released in 5.10.0

Great!
Thanks!
@thinkwelltwd, come on, I hope you are still with us :)

@thinkwelltwd, come on, I hope you are still with us :)

Yes, I'm still here; almost despaired of this ever getting done. I'm just super-glad it is. Was using another library, and don't want to disparage it, but django_select2 is nicer.
I've now incorporated it into my project and the other library is fully removed. Thanks again for the excellent work!


Err when running single_index.py

Firstly, thank you for sharing your work.
When I run "python3 main/single_index.py -cfg configs/caltech.yaml" according to GETTING_STARTED.md, some errors occur.
FileNotFoundError: [Errno 2] No such file or directory: '/data/caltech101/query/airplanes/image_0004.jpg'
And I find that the variable(path) is fixed in single_index.py line 5:
    path = '/data/caltech101/query/airplanes/image_0004.jpg'

You need to check if "/data/caltech101/query/airplanes/image_0004.jpg" file exists in your computer or not.


Schema Upgrade Support

This PR includes the following changes:

Updated the submodule reference for the jpo-geojsonconverter to the latest commit on the develop branch
Changed the jpo-deduplicator to use the DateJsonMapper.java class for its object mapper. This object mapper will not error out when there are unknown properties.

All tests still pass and everything seems to work when running with the updated ODE metadata schema.

Deduplication algorithms run in the same way as before. This PR should be good to merge.


Put preview of messages into email

See FreeREG1404
Reported Issue:
In the same way as we have for Contact messages, we should include the message content in the email from the SC to their syndicate members via the Syndicate Messages action so they don't have to login to read it.
We should also do this for general message emails from the Message System action so they only need to login if they want to reply.
Consider limiting the amount shown.
Attachments - add or not?

E0 U3 S8 C5: P16

Tweak code implemented for FreeREG when that is done

Tweak code implemented for FreeREG when that is done

Being done as part of reg will apply automatically


Fix switch locale

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 54.90196% with 23 lines in your changes missing coverage. Please review.

Project coverage is 59.10%. Comparing base (cf6e728) to head (4cf8d6b).

Files with missing lines
Patch %
Lines

transx/api/mo.py
55.17%
9 Missing and 4 partials :warning:

transx/core.py
57.14%
6 Missing and 3 partials :warning:

transx/cli.py
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
- Coverage   59.36%   59.10%   -0.26%
==========================================
  Files          19       19
  Lines        2269     2284      +15
  Branches      457      462       +5
==========================================
+ Hits         1347     1350       +3
- Misses        746      755       +9
- Partials      176      179       +3

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


Get directory of VSCode for Portable Setup

Hi,
i try to create a portable bundle of VSCode with Arduino.
I try to set a relative arduino.path within the VSCode Arduino extension but i do not find any way to get a placeholder for the vscode-directors (in the example below:   C:\basedir\vscode).
I want the config "arduino.path":"${vscodepath}/../arduino".
${execPath} does not do the job, because it returns $C:\basedir\vscode\code.exe"
C:\basedir
> vscode
>code.exe
> ....
> arduino
> arduino.exe
> ....
Please give me an advice.
Thx. Klaus

I don't understand what you are looking for exactly, what is vscodepath supposed to be?

As mentioned above.
${execPath}  is C:\basedir\vscode\code.exe
but i ned something like
${vscodepath} with C:\basedir\vscode

Does this assume that arduino is installed next to vscode? I am not sure we should do this because I don't think extensions should make assumptions about the install location of vscode.

Yes, arduino is installed next to VSCode and it will be a portable bundle for our students.
Everything works fine except the relaive path to arduino relative to the vscode path.
Can you give me any advice to fix this?
Thx, Klaus

You can use an absolute path to where Arduino is installed, or you can ask the Arduino extension for some support, for example if Arduino is installed in different places, they can detect the install directory.

Hi,we build a portable bundle that contains arduino, vscode and maybe some other tools in future and so i have to use relative pathes for the configuration. So arduino is not installed. It's just in the same parent directory as vscode.So there exists ${execPath}but the Code.exe at the end of the string makes it unusable for my usecase.I think this is a feature that may be required for a lot of usecases. Is there no way to get the directory path within the configs?Any advice?Klaus-------- Ursprüngliche Nachricht --------Betreff: Re: [microsoft/vscode] Get directory of VSCode for Portable Setup (#82602)Von: Rob Lourens An: microsoft/vscode Cc: weingaunity ,Author You can use an absolute path to where Arduino is installed, or you can ask the Arduino extension for some support, for example if Arduino is installed in different places, they can detect the install directory.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Hi,
we build a portable bundle that contains arduino, vscode and maybe some other tools in future and so i have to use relative pathes for the configuration.
So arduino is not installed. It's just in the same parent directory as vscode.
So there exists ${execPath} but the Code.exe at the end of the string makes it unusable for my usecase.
I think this is a feature that may be required for a lot of usecases. Is there no way to get the directory path within the configs like
"arduino.path":"${vscodedir}/../arduino"
Any advice?
Klaus


wip on coupling CloudMicrophysics.jl

This PR couples KiD to CloudMicrophysics.jl. It also fixes the surface boundary condition for q_tot.
We already discussed the review comments during the meeting and opened a bunch of issues related to it.
The first thing to do would be to just add a test that runs the different moisture and precipitation options.

Closes #46

Closes #47


Feature Suggestion: Skin Changer, Skin Search Bar.

I have seen this done in other cheats and I think it would be cool to add a toggle-able search bar for finding certain skins within the skin changer.
EDIT: Please add label "Enhancement"

A good idea


Upgrade to the Material design

App should be updated to the Material design - http://developer.android.com/design/material/index.html.
What it exactly mean for the app?:

hide action bar when scrolling list of notifications on phones to get a bit bigger area for list
change overlay action icons (from square dots to rounded dots one)
change navigation drawer related indicators and it's behaviour (animation)
change list of notifications to use card view instead of list view (I'm really not sure about this due space limitation and two column view on tablets)?
widget design to match material design ones, but should allow to stay with old design also

ToDo something other?

The cards list is discouraged by material design specifications, better a list control.

Yeah, a cards view would also just be strange there. It’s a list of issues, so no real use for cards since the only real content is the title (no big image except the repo icon).

Does this also mean there will be a dark version available? I mean usually you don't spend that much time on the apps main screen or settings but the flash can really annoy all the time :o

@Bluscream I created separate issue #90 for the dark theme. I want to release Material design ASAP to get some feedback, then I can play with the dark theme.

Looks like I'm done with the coding, we will see from the users feedback. I have to prepare Play Store listing refresh (new images) before release.


[Feature Request]: Add Confirm Password Field in register Form

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Objective: Implement a "Confirm Password" field in the registration form to enhance user experience and security during account creation.
Use Case
Details:

Currently, the registration form only requires users to input their password once, which increases the likelihood of errors and frustration if the password is mistyped.
Adding a "Confirm Password" field will require users to re-enter their password, ensuring that they remember it correctly before submission.
This feature will help reduce registration errors and improve the overall integrity of user accounts by ensuring that both password entries match.

Benefits
Adding a "Confirm Password" field will enhance user confidence during the registration process and improve the overall security of user accounts.
Hey @Trisha-tech Please assign me this issue with label "gssoc-ext", "hacktoberfest-accepted" and "level2"
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Is there an existing issue for this?

[x]  I have searched the existing issues

Feature Description
Objective: Implement a "Confirm Password" field in the registration form to enhance user experience and security during account creation.
Use Case
Details:

Currently, the registration form only requires users to input their password once, which increases the likelihood of errors and frustration if the password is mistyped.
Adding a "Confirm Password" field will require users to re-enter their password, ensuring that they remember it correctly before submission.
This feature will help reduce registration errors and improve the overall integrity of user accounts by ensuring that both password entries match.

Benefits
Adding a "Confirm Password" field will enhance user confidence during the registration process and improve the overall security of user accounts.
Hey @Trisha-tech Please assign me this issue with label "gssoc-ext", "hacktoberfest-accepted" and "level2"
Add ScreenShots
No response
Priority
High
Record

[x]  I have read the Contributing Guidelines
[x]  I'm a GSSOC'24 contributor
[x]  I have starred the repository

This issue is already assigned to someone @samyak-aditya .


Python stdlib xml API

I am not familiar with the Python standard library's xml module, but do you plan on following its API? It would be helpful for codon-xml to have the same API so that other libraries that use the Python xml module can also make use of it.

Yeah. There are some incompatibilities right now but my intention is for the outer API to function nearly the same if not the same to the standard XML API. I had planned to work on a compatibility layer after we managed to get it running in Codon rather than before.

Closing due to inactivity. Feel free to reopen if you have any questions or issues!


Fix /api/repos/move documentation in api.md

Related to https://github.com/huggingface/huggingface_hub/issues/1813.
In /api/repos/move, we (I? :smile:) forgot to mention the type parameter to specify the repo type.
cc @enzostvs you would have to update the API Playground as well to add this parameter. Thanks in advance!

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Great, thanks for reviewing :)


Support 2016-07-01 version of resources API spec.

Hi @TianoMS, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

@TianoMS it would really help speed up future reviews of new versions if the first commit that you make is just an exact copy of the existing version in the new location and then follow that with additional commits for any changes you're making for the new version. This will really help identify what has changed.

@John-Hart Thanks John for the advice. I'll improve the process next time. Also, I have addressed the other comments on descriptions.

LGTM

No modification for NodeJS

No modification for Python


DMIunipgAI-VacuumCleaner2016-trivelle

versione "Trivelle" del Vacuum Cleaner, file della competition 2016

https://github.com/DMIunipg/AI-Project-VacuumEnvironment/pull/2.patch
Step 1: From your project repository, check out a new branch and test the changes.
git checkout -b valefranz-master master
git pull git://github.com/valefranz/AI-Project-VacuumEnvironment.git master
Step 2: Merge the changes and update on GitHub.
git checkout master
git merge --no-ff valefranz-master
git push origin master


Improve WMCore framework metrics

Impact of the new feature
To setup better monitoring of WMCore service process it is desired to improve its metrics. This may include but not limited to the following items:

total HTTP request time
time spend on DB
process metrics like cpu/mem, etc.

Is your feature request related to a problem? Please describe.
It will provide better way to monitor WMCore processes
Describe the solution you'd like
Improve metrics in WMCore logging and feed them to monitoring infrastructure
Describe alternatives you've considered
Additional context

Yes, we may close this issue.

Closed by https://github.com/dmwm/WMCore/pull/9940. Thanks!


docs: integrate pouch with dragonfly

add docs to describe how to run pouch with dragonfly
Fixes: #103

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #828 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #828   +/-   ##
=======================================
  Coverage   14.49%   14.49%
=======================================
  Files         112      112
  Lines        6728     6728
=======================================
  Hits          975      975
  Misses       5675     5675
  Partials       78       78

Continue to review full report at Codecov.

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

@allencloud , updated.

LGTM