Query CommitsByAuthor gets 502 error in Github response when using large maxNumber

I was trying this tool out for the first time and I seem to have found a case that can pretty easily trigger a timeout from Github's servers when querying for a conflict. Unfortunately it's on a private repo so I can't share all the details, but I've managed to track down what I think is the cause. Here is the problematic query, from the logs, which I think is only used when there is a merge conflict:
{
  "query": "query CommitsByAuthor($authorId: ID, $commitPath: String, $dateSince: GitTimestamp, $dateUntil: GitTimestamp, $maxNumber: Int!, $repoName: String!, $repoOwner: String!, $sourceBranch: String!) {\n  repository(owner: $repoOwner, name: $repoName) {\n    ref(qualifiedName: $sourceBranch) {\n      target {\n        ... on Commit {\n          history(\n            first: $maxNumber\n            author: {id: $authorId}\n            path: $commitPath\n            since: $dateSince\n            until: $dateUntil\n          ) {\n            edges {\n              node {\n                ...SourceCommitWithTargetPullRequestFragment\n              }\n            }\n          }\n        }\n      }\n    }\n  }\n}\n\nfragment SourceCommitWithTargetPullRequestFragment on Commit {\n  repository {\n    name\n    owner {\n      login\n    }\n  }\n  sha: oid\n  message\n  committedDate\n  author {\n    name\n    email\n  }\n  associatedPullRequests(first: 1) {\n    edges {\n      node {\n        title\n        url\n        number\n        labels(first: 50) {\n          nodes {\n            name\n          }\n        }\n        baseRefName\n        mergeCommit {\n          ...RemoteConfigHistoryFragment\n          sha: oid\n          message\n        }\n        timelineItems(last: 20, itemTypes: CROSS_REFERENCED_EVENT) {\n          edges {\n            node {\n              ... on CrossReferencedEvent {\n                targetPullRequest: source {\n                  __typename\n                  ... on PullRequest {\n                    targetMergeCommit: mergeCommit {\n                      sha: oid\n                      message\n                    }\n                    repository {\n                      name\n                      owner {\n                        login\n                      }\n                    }\n                    url\n                    title\n                    state\n                    baseRefName\n                    number\n                    commits(first: 20) {\n                      edges {\n                        node {\n                          targetCommit: commit {\n                            message\n                            sha: oid\n                          }\n                        }\n                      }\n                    }\n                  }\n                }\n              }\n            }\n          }\n        }\n      }\n    }\n  }\n}\n\nfragment RemoteConfigHistoryFragment on Commit {\n  remoteConfigHistory: history(first: 1, path: \".backportrc.json\") {\n    edges {\n      remoteConfig: node {\n        committedDate\n        file(path: \".backportrc.json\") {\n          ... on TreeEntry {\n            object {\n              ... on Blob {\n                text\n              }\n            }\n          }\n        }\n      }\n    }\n  }\n}",
  "variables": {
    "repoOwner": "[redacted]",
    "repoName": "[redacted]",
    "sourceBranch": "develop",
    "maxNumber": 50,
    "authorId": null,
    "commitPath": "[redacted]",
    "dateSince": null,
    "dateUntil": "2023-10-13T01:54:32Z"
  }
}

and the response:
{
  "data": {
    "data": null,
    "errors": [
      {
        "message": "Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug. Please include `0B60:297D:1890481:32291DB:652961CA` when reporting this issue."
      }
    ]
  },
  "headers": {
    "access-control-allow-origin": "*",
    "access-control-expose-headers": "ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset",
    "content-type": "application/json",
    "date": "Fri, 13 Oct 2023 15:27:18 GMT",
    "server": "GitHub.com",
    "transfer-encoding": "chunked",
    "vary": "Accept-Encoding, Accept, X-Requested-With",
    "x-github-request-id": "0B60:297D:1890481:32291DB:652961CA"
  },
  "status": 502,
  "statusText": "Bad Gateway"
}

From reading a few sources online, it seems like this is mostly caused by the response taking too long (> 10s) and Github servers timing out. There might be a few things that could help address this:

Respect dateSince in this particular query. Even if set from the CLI or config file, this query still uses null which can result in a large response. I'm not sure if this might impact user experience if some commits got omitted because of using dateSince but I think that's sort of expected
For 502 errors like this in general, especially if the message contains "may be the result of a timeout" or something like that, maybe suggest to the user to decrease maxNumber or add date filters? It took me a bit to figure out the root cause of the problem at all
Consider using graphQL pagination or something similar to break the results into multiple pieces. This is probably a lot more work than the other options

Thank you for the thorough writeup.  I agree, this could be handled much more smoothly.

Respect dateSince in this particular query. Even if set from the CLI or config file, this query still uses null which can result in a large response. I'm not sure if this might impact user experience if some commits got omitted because of using dateSince but I think that's sort of expected

I was not able to reproduce this. I run this command, and I see the commits are being filtered as expected:
backport --author sqren --repo elastic/kibana --maxNumber 100 --date-since "10 Oct 2023"

Can you try re-running the above command and see if you get all commits or only commits after 10th of October.

Ah, thanks for the example, that helps me reproduce it more easily without using private repos. The filtering via the command you mentioned seems to work correctly, but that wasn't the original problem I ran into.
The issue seems to be occur when there is a merge conflict while backporting, so I was able to trigger by backporting a recent PR of yours to an older branch:
$ backport --dryRun --author sqren --repo elastic/kibana --maxNumber 100 --date-since "10 Oct 2023" --pr 167828
? Select pull request [APM] Add API test for multiple APM Servers (#167828)
? Select branch 5.6
✔ 100% Cloning repository from github.com (one-time operation)

Backporting to 5.6:
✔ Pulling latest changes
✖ Cherry-picking: [APM] Add API test for multiple APM Servers (#167828)
An unhandled error occurred while backporting commit. Please see the logs for details: /Users/ichamberlain/.backport/backport.info.log

Here's the last few lines of the full log, which I think includes the query that's requesting too much data:
{"level":"info","message":"POST https://api.github.com/graphql (name:CommitsByAuthor, status: 502, EXCEPTION THROWN)","metadata":{},"timestamp":"2023-10-16 13:33:12"}
{"level":"error","message":"runSequentially failed Request failed with status code 502 (Github API v4)","metadata":{"githubResponse":{"config":{"adapter":["xhr","http"],"data":"{\"query\":\"query CommitsByAuthor($authorId: ID, $commitPath: String, $dateSince: GitTimestamp, $dateUntil: GitTimestamp, $maxNumber: Int!, $repoName: String!, $repoOwner: String!, $sourceBranch: String!) {\\n  repository(owner: $repoOwner, name: $repoName) {\\n    ref(qualifiedName: $sourceBranch) {\\n      target {\\n        ... on Commit {\\n          history(\\n            first: $maxNumber\\n            author: {id: $authorId}\\n            path: $commitPath\\n            since: $dateSince\\n            until: $dateUntil\\n          ) {\\n            edges {\\n              node {\\n                ...SourceCommitWithTargetPullRequestFragment\\n              }\\n            }\\n          }\\n        }\\n      }\\n    }\\n  }\\n}\\n\\nfragment SourceCommitWithTargetPullRequestFragment on Commit {\\n  repository {\\n    name\\n    owner {\\n      login\\n    }\\n  }\\n  sha: oid\\n  message\\n  committedDate\\n  author {\\n    name\\n    email\\n  }\\n  associatedPullRequests(first: 1) {\\n    edges {\\n      node {\\n        title\\n        url\\n        number\\n        labels(first: 50) {\\n          nodes {\\n            name\\n          }\\n        }\\n        baseRefName\\n        mergeCommit {\\n          ...RemoteConfigHistoryFragment\\n          sha: oid\\n          message\\n        }\\n        timelineItems(last: 20, itemTypes: CROSS_REFERENCED_EVENT) {\\n          edges {\\n            node {\\n              ... on CrossReferencedEvent {\\n                targetPullRequest: source {\\n                  __typename\\n                  ... on PullRequest {\\n                    targetMergeCommit: mergeCommit {\\n                      sha: oid\\n                      message\\n                    }\\n                    repository {\\n                      name\\n                      owner {\\n                        login\\n                      }\\n                    }\\n                    url\\n                    title\\n                    state\\n                    baseRefName\\n                    number\\n                    commits(first: 20) {\\n                      edges {\\n                        node {\\n                          targetCommit: commit {\\n                            message\\n                            sha: oid\\n                          }\\n                        }\\n                      }\\n                    }\\n                  }\\n                }\\n              }\\n            }\\n          }\\n        }\\n      }\\n    }\\n  }\\n}\\n\\nfragment RemoteConfigHistoryFragment on Commit {\\n  remoteConfigHistory: history(first: 1, path: \\\".backportrc.json\\\") {\\n    edges {\\n      remoteConfig: node {\\n        committedDate\\n        file(path: \\\".backportrc.json\\\") {\\n          ... on TreeEntry {\\n            object {\\n              ... on Blob {\\n                text\\n              }\\n            }\\n          }\\n        }\\n      }\\n    }\\n  }\\n}\",\"variables\":{\"repoOwner\":\"elastic\",\"repoName\":\"kibana\",\"sourceBranch\":\"main\",\"maxNumber\":100,\"authorId\":null,\"commitPath\":null,\"dateSince\":null,\"dateUntil\":\"2023-10-13T08:24:23Z\"}}","env":{},"headers":{"Accept":"application/json, text/plain, */*","Accept-Encoding":"gzip, compress, deflate, br","Authorization":"bearer <REDACTED>","Content-Length":"3034","Content-Type":"application/json","User-Agent":"axios/1.5.1"},"maxBodyLength":-1,"maxContentLength":-1,"method":"post","timeout":0,"transformRequest":[null],"transformResponse":[null],"transitional":{"clarifyTimeoutError":false,"forcedJSONParsing":true,"silentJSONParsing":true},"url":"https://api.github.com/graphql","xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN"},"data":{"data":null,"errors":[{"message":"Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug. Please include `C318:5862:1A4A0BC:35D9657:652D73C9` when reporting this issue."}]},"headers":{"access-control-allow-origin":"*","access-control-expose-headers":"ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset","content-type":"application/json","date":"Mon, 16 Oct 2023 17:33:12 GMT","server":"GitHub.com","transfer-encoding":"chunked","vary":"Accept-Encoding, Accept, X-Requested-With","x-github-request-id":"C318:5862:1A4A0BC:35D9657:652D73C9"},"status":502,"statusText":"Bad Gateway"},"name":"GithubV4Exception","stack":"GithubV4Exception: Request failed with status code 502 (Github API v4)"},"timestamp":"2023-10-16 13:33:12"}
{"level":"info","message":"Results","metadata":{"0":{"error":{"githubResponse":{"config":{"adapter":["xhr","http"],"data":"{\"query\":\"query CommitsByAuthor($authorId: ID, $commitPath: String, $dateSince: GitTimestamp, $dateUntil: GitTimestamp, $maxNumber: Int!, $repoName: String!, $repoOwner: String!, $sourceBranch: String!) {\\n  repository(owner: $repoOwner, name: $repoName) {\\n    ref(qualifiedName: $sourceBranch) {\\n      target {\\n        ... on Commit {\\n          history(\\n            first: $maxNumber\\n            author: {id: $authorId}\\n            path: $commitPath\\n            since: $dateSince\\n            until: $dateUntil\\n          ) {\\n            edges {\\n              node {\\n                ...SourceCommitWithTargetPullRequestFragment\\n              }\\n            }\\n          }\\n        }\\n      }\\n    }\\n  }\\n}\\n\\nfragment SourceCommitWithTargetPullRequestFragment on Commit {\\n  repository {\\n    name\\n    owner {\\n      login\\n    }\\n  }\\n  sha: oid\\n  message\\n  committedDate\\n  author {\\n    name\\n    email\\n  }\\n  associatedPullRequests(first: 1) {\\n    edges {\\n      node {\\n        title\\n        url\\n        number\\n        labels(first: 50) {\\n          nodes {\\n            name\\n          }\\n        }\\n        baseRefName\\n        mergeCommit {\\n          ...RemoteConfigHistoryFragment\\n          sha: oid\\n          message\\n        }\\n        timelineItems(last: 20, itemTypes: CROSS_REFERENCED_EVENT) {\\n          edges {\\n            node {\\n              ... on CrossReferencedEvent {\\n                targetPullRequest: source {\\n                  __typename\\n                  ... on PullRequest {\\n                    targetMergeCommit: mergeCommit {\\n                      sha: oid\\n                      message\\n                    }\\n                    repository {\\n                      name\\n                      owner {\\n                        login\\n                      }\\n                    }\\n                    url\\n                    title\\n                    state\\n                    baseRefName\\n                    number\\n                    commits(first: 20) {\\n                      edges {\\n                        node {\\n                          targetCommit: commit {\\n                            message\\n                            sha: oid\\n                          }\\n                        }\\n                      }\\n                    }\\n                  }\\n                }\\n              }\\n            }\\n          }\\n        }\\n      }\\n    }\\n  }\\n}\\n\\nfragment RemoteConfigHistoryFragment on Commit {\\n  remoteConfigHistory: history(first: 1, path: \\\".backportrc.json\\\") {\\n    edges {\\n      remoteConfig: node {\\n        committedDate\\n        file(path: \\\".backportrc.json\\\") {\\n          ... on TreeEntry {\\n            object {\\n              ... on Blob {\\n                text\\n              }\\n            }\\n          }\\n        }\\n      }\\n    }\\n  }\\n}\",\"variables\":{\"repoOwner\":\"elastic\",\"repoName\":\"kibana\",\"sourceBranch\":\"main\",\"maxNumber\":100,\"authorId\":null,\"commitPath\":null,\"dateSince\":null,\"dateUntil\":\"2023-10-13T08:24:23Z\"}}","env":{},"headers":{"Accept":"application/json, text/plain, */*","Accept-Encoding":"gzip, compress, deflate, br","Authorization":"bearer <REDACTED>","Content-Length":"3034","Content-Type":"application/json","User-Agent":"axios/1.5.1"},"maxBodyLength":-1,"maxContentLength":-1,"method":"post","timeout":0,"transformRequest":[null],"transformResponse":[null],"transitional":{"clarifyTimeoutError":false,"forcedJSONParsing":true,"silentJSONParsing":true},"url":"https://api.github.com/graphql","xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN"},"data":{"data":null,"errors":[{"message":"Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug. Please include `C318:5862:1A4A0BC:35D9657:652D73C9` when reporting this issue."}]},"headers":{"access-control-allow-origin":"*","access-control-expose-headers":"ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset","content-type":"application/json","date":"Mon, 16 Oct 2023 17:33:12 GMT","server":"GitHub.com","transfer-encoding":"chunked","vary":"Accept-Encoding, Accept, X-Requested-With","x-github-request-id":"C318:5862:1A4A0BC:35D9657:652D73C9"},"status":502,"statusText":"Bad Gateway"},"name":"GithubV4Exception"},"status":"unhandled-error","targetBranch":"5.6"}},"timestamp":"2023-10-16 13:33:12"}

Setting --maxNumber 20 seems to reduce the size of the query enough for it to work, but the precise number probably depends on the server load, size of the query contents, etc.
Hopefully that helps with the details — if you need more info, let me know and I can provide full logs from a different computer (assuming I can reproduce there as well).
Thanks!

I've published some improvements in 9.4.1. Would be great if you can give it a try, thanks!

Thanks for the quick fix! It looks like your changes helped, I can no longer reproduce with the original command that I first ran into problems on.

Yes, specifically I added this:
https://github.com/sqren/backport/blob/993d2801b032d5321bca5c47bb3d8c853671a500/src/lib/cherrypickAndCreateTargetPullRequest/getCommitsWithoutBackports.ts#L30
It's because when encountering a conflict the tool automatically get related commits to figure out if one of them caused the conflict.


Unable to download webpage from youtube user

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2<IP_ADDRESS>. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[X] I've verified and I assure that I'm running youtube-dl 2<IP_ADDRESS>

Before submitting an issue make sure you have:

[X] At least skimmed through README and most notably FAQ and BUGS sections
[X] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[X] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v ytuser:UC8gjB1PSXv_oAUSAQ16S0fA
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-v', 'ytuser:UC8gjB1PSXv_oAUSAQ16S0fA']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.10.21
[debug] Python version 3.5.2 - Linux-4.7.6-1-ARCH-x86_64-with-arch
[debug] exe versions: ffmpeg 3.1.4, ffprobe 3.1.4, rtmpdump 2.4
[debug] Proxy map: {}
[youtube:user] UC8gjB1PSXv_oAUSAQ16S0fA: Downloading channel page
WARNING: Unable to download webpage: HTTP Error 404: Not Found
[youtube:user] UC8gjB1PSXv_oAUSAQ16S0fA: Downloading page #1
ERROR: Unable to download webpage: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/lib/python3.5/site-packages/youtube_dl/extractor/common.py", line 403, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/lib/python3.5/site-packages/youtube_dl/YoutubeDL.py", line 2001, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python3.5/urllib/request.py", line 472, in open
    response = meth(req, response)
  File "/usr/lib/python3.5/urllib/request.py", line 582, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python3.5/urllib/request.py", line 510, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.5/urllib/request.py", line 444, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.5/urllib/request.py", line 590, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
<end of log>

### Description of your *issue*, suggested solution and other information

I'm trying to download the videos from a user channel `UC8gjB1PSXv_oAUSAQ16S0fA` but I'm met with `Unable to download webpage: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>); please report`

[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-v', 'ytuser:UC8gjB1PSXv_oAUSAQ16S0fA']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.10.21
[debug] Python version 3.5.2 - Linux-4.7.6-1-ARCH-x86_64-with-arch
[debug] exe versions: ffmpeg 3.1.4, ffprobe 3.1.4, rtmpdump 2.4
[debug] Proxy map: {}

Why are the messages appearing twice?

It's not a /user/ URL:
youtube-dl https://www.youtube.com/channel/UC8gjB1PSXv_oAUSAQ16S0fA


Tag field changes height when you add a tag to it

When I add a tag to this field it gets slightly bigger vertically:

It should be the same height in both scenarios.

See https://github.com/chec/dashboard/issues/714


Run in a single test, create custom TMT results.yaml with useful logs/artifacts

We are going to call rpminspect_runner.sh just once for a package update. All the extra result parsing and splitting is obsolete, it will be replaced with making rpminspect's new builtin viewer [1] easily accessible from TF results.
[1] https://github.com/rpminspect/rpminspect/tree/main/contrib

This needs to go along with a change to rpminspect-pipeline.
I tested this locally as much as possible, replicating a recent real-life run:
git clone -b custom-results-yaml https://github.com/martinpitt/rpminspect-pipeline
cd rpminspect-pipeline
curl -LO https://artifacts.dev.testing-farm.io/32eccead-7105-4edb-bab3-4660fe895061/workdir-repository-None-6b3gVS/tmt-environment-rpminspect.yaml

git fetch; git reset --hard origin/custom-results-yaml
rm -rf /var/tmp/tmt/*; tmt run --all --verbose -e @tmt-environment-rpminspect.yaml

this ran, and as expected failed a few inspections. This has two initial custom logs:
$ cat /var/tmp/tmt/run-001/rpminspect/execute/data/rpminspect/data/results.yaml
- name: /rpminspect
  result: fail
  log:
    - verbose.log
    - results.json

Now I want to test this end-to-end via TF, to see how that ends up in results.xml, results-junit.xml, and how we can connect oculus and rpminspect's viewer.html. I hope/think that CI on this PR will do that.
I configured https://quay.io/repository/rhn_engineering_mpitt/rpminspect?tab=tags to auto-build on pushes to my fork.

[x] Wait for Testing Farm to get tmt 1.18.0 to support custom results.yaml (@thrix working on it)
[x] Teach gluetool-modules to consider all log: entries from results.yaml and expose them in results.xml: https://gitlab.com/testing-farm/gluetool-modules/-/merge_requests/282
[x] rebase the above to testing-farm branch
[x] deploy current testing-farm branch (@thrix working on it)
[ ] Corresponding pipeline changes: https://github.com/fedora-ci/rpminspect-pipeline/pull/64 . Get this reviewed, and end-to-end tested
[ ] Add rpminspect viewer.html as log artifact
[ ] Rework rpminspect_zuul_runner.sh, this would be completely broken right now.
[ ] Clean up $RPMINSPECT_WORKDIR. Not really used any more, but rpminspect_zuul_runner.sh scripts are full of it still

I sent a testing farm PR to plumb through the additional artifacts to results.xml and thus to the UI: https://gitlab.com/testing-farm/gluetool-modules/-/merge_requests/282 . This needs to land and get rolled out before we can make any progress here.

@msrb, @thrix : Hmm, it seems the environment files disappeared? My original reference test run as well as a recent one still exist, but the tmt-environment-rpminspect.yaml file mentioned in the reproducer does not exist any more.
It's plausible that the recent rpminspect-runner changes around workdir may have accidentally dropped this file from the artifacts, but why did it also actively disappear from an old result?
I'll try to guess how they should look like, so that I can locally run an rpminspect pipeline. This PR is finally unblocked after last Friday's TF release. :tada:

Ah, one can see the environment in the tmt log, thus a working file looks like this:
PREVIOUS_TAG: f37-updates
TASK_ID: 93912669
RPMINSPECT_PROFILE_NAME: rawhide
REPOSITORY_URL: https://src.fedoraproject.org/rpms/cockpit
CONFIG_BRANCH: rawhide
DEFAULT_RELEASE_STRING: fc37
GIT_COMMIT: 9fa3d64b44d624a37ab30ff25c56117cb31e86a9

Unfortunately that old cockpit test cannot be run any more, as rpminspect crashes: rpminspect: libannocheck_init error: version number too small. So I ran a pipeline for this recent successful cockpit-podman bodhi result through jenkins, and it ended up producing this result. This is almost good, it does have the new attachments, they are just in the wrong directory.

As discussed on IRC, we don't use the Zuul scripts for anything right now. So I would leave those alone -- no need to update them in this PR.

Removing so many lines of code -- amazing! :)
I'd say let's merge this and test the changes end-to-end in the pipeline.


docs: ✏ fleek network managing the key store

Description
Fleek network managing the key store

Looks great! Nitpicked some typos.

Looks great! Nitpicked some typos. Btw sorry for the commit, I was trying to suggest the changes.

Np! thanks!


Add kctrl to the list of apps installed as part of the action

Add kctrl (kapp-controller's native cli) to the list of apps installed as part of the action.
kctrl has been part of kapp-controller releases since v0.34.0

Hi @praveenrewar! Thanks for the issue. I created a draft PR here: #203.
I notice that the format of the checksums in the release notes for kctrl is a little different from the other Carvel repos. They all provide the output of md5sum (which always has two spaces between the hash and the filename) and prefix the binary name with the relative path signifier ./. For example:
5fd3afbe09a66fc9e91252c57448045eeeab1ee3f6d305da6f9885186b744e67  ./kbld-darwin-amd64
2962cd78c6c45cf3f03ca76c52ca7517ed5f2ceba6ed1b3d594a16d516ef05a2  ./kbld-darwin-arm64
67c86ece94a3747b2e011a5b72044b69f2594ca807621b1e1e4c805f6abcaeef  ./kbld-linux-amd64
658725c5dab5349dd4cb826ff9278749f093ed2275aadf51dc994265e6599b2c  ./kbld-linux-arm64
9dcb4d6db2901257f8f23059c13b41d37ef8b8b36f27d909cceb81934fc9e862  ./kbld-windows-amd64.exe
04c51f4aa92d117d22513727ee37cda1b5ae18bf94a223093f11727d0ba878b4  ./kbld-windows-arm64.exe

However, per the failing tests in the PR, the release notes for kctrl are sometimes in a different format (with variations in the number of spaces between the hash and the binary, and not all binaries prefixed with the relative path signifier).
Would you be up for amending the release notes in kapp-controller to match the format of other Carvel repos? There's something to be said for consistency, and I would prefer to avoid adding regexes or conditionals to the security check if possible, as that introduces a new bug surface area.

Thank you so much for the quick turn around @jbrunton. Sure, I will add the ./ with the filenames in the release notes.

Hi @jbrunton! We are planning to make a kapp-controller release next week (which will have the release notes in the correct format), is it okay to merge the PR after that?
We are okay with supporting kctrl from the next release in the Github action (just trying to avoid updating the release notes as much as possible)

Hi @jbrunton! kapp-controller v0.38.4 is released and the tests on the PR seem to be passing now (after I re-triggered them) 🚀

@praveenrewar: Thanks for making those changes! I've merged the PR and released a new version of the action, so I'll close this issue now.


[Bug] apiVersion cannot be empty when applying add-Rolebinding policy

Kyverno Version
1.10.x
Kubernetes Version
1.27.x
Kubernetes Platform
Minikube
Description
When trying to apply the add-rolebinding.yaml policy via kubectl apply -f add-rolebinding.yaml I get the error
Error from server: error when creating "add-rolebinding.yaml": admission webhook "validate-policy.kyverno.svc" denied the request: path: spec.rules[0].generate.apiVersion.: apiVersion cannot be empty.
Kyverno was installed in standalone mode with: helm install kyverno kyverno/kyverno -n kyverno --create-namespace
Yaml configuration of the policy (same as in the github repo):
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: add-rolebinding
  annotations:
    policies.kyverno.io/title: Add RoleBinding
    policies.kyverno.io/category: Multi-Tenancy
    policies.kyverno.io/subject: RoleBinding
    policies.kyverno.io/minversion: 1.6.0
    policies.kyverno.io/description: >-
      Typically in multi-tenancy and other use cases, when a new Namespace is created,
      users and other principals must be given some permissions to create and interact
      with resources in the Namespace. Very commonly, Roles and RoleBindings are used to
      grant permissions at the Namespace level. This policy generates a RoleBinding
      called `<userName>-admin-binding` in the new Namespace which binds to the ClusterRole
      `admin` as long as a `cluster-admin` did not create the Namespace. Additionally, an annotation
      named `kyverno.io/user` is added to the RoleBinding recording the name of the user responsible
      for the Namespace's creation.
spec:
  background: false
  rules:
    - name: generate-admin-binding
      match:
        any:
        - resources:
            kinds:
              - Namespace
      exclude:
        any:
        - clusterRoles:
          - cluster-admin
      generate:
        synchronize: true
        kind: RoleBinding
        name: "{{request.userInfo.username}}-admin-binding"
        namespace: "{{request.object.metadata.name}}"
        data:
          metadata:
            annotations:
              kyverno.io/user: "{{request.userInfo.username}}"
          roleRef:
            apiGroup: rbac.authorization.k8s.io
            kind: ClusterRole
            name: admin
          subjects:
            - kind: User
              name: "{{request.userInfo.username}}"

Steps to reproduce

Install kyverno as standalone into minikube
Try to apply add-rolebinding policy with kubectl apply -f add-rolebinding.yaml

Expected behavior
Add-roleBinding cluster policy get applied successfully
Screenshots
No response
Kyverno logs
E0818 09:07:27.375898       1 handlers.go:38] webhooks/policy/validate "msg"="policy validation errors" "error"="path: spec.rules[0].generate.apiVersion.: apiVersion cannot be empty" "gvk"={"group":"kyverno.io","version":"v1","kind":"ClusterPolicy"} "gvr"={"group":"kyverno.io","version":"v1","resource":"clusterpolicies"} "name"="add-rolebinding" "namespace"="" "operation"="CREATE" "uid"="87f43cd7-5b8b-44d3-bea5-878d4843bf98" "user"={"username":"minikube-user","groups":["system:masters","system:authenticated"]}

Slack discussion
No response
Troubleshooting

[X] I have read and followed the documentation AND the troubleshooting guide.
[X] I have searched other issues in this repository and mine is not recorded.

@mintbomb27, I'm not sure how we missed this, or how the current kuttl tests are passing. Let's get this fixed, please, making sure to update the Artifact Hub metadata as well.

Sure! This change was introduced recently in Kyverno, which required the apiVersion, and kind mentioned separately and we had faced a similar issue for another policy as well, but that was fixed.
The policy mentioned is currently not covered in test(Skipped). Will cover it in the upcoming PRs.


5.1 Opus channels are wrong

Unfortunaly the channels are wrong when playing 5.1 opus on my sony google tv.
Center channel is playing on the right box
Right channel is playing on the left box
Left channel is playing on the center box
the other 3 channels are played back correctly

Looks like a platform issue: https://github.com/google/ExoPlayer/issues/8396


Stack Overflow brand

Matt from Stack here, I corrected the logo and the company name, hope this helps.

I signed it! @googlebot

Thanks, Matt. Wow, you're on top of things. Even matched the pixel dimensions of the icon! Much appreciated.

Cheers @johndmulhausen.


add support for before_schedule and after_schedule hooks

Behaves very much like the before_enqueue and after_enqueue hooks in Resque 1.19.1 (still not tagged):

before hooks can block scheduling of the job by returning false
after hooks are only run if the job was scheduled

Interesting.
A couple things:

Can you port the test to a context like the other ones?
Remove the puts in the tests.
Instead of hitting redis directly in the test, it might be cleaner to use the existing Resque interface to the delayed queue.
Update the README (under the Delayed Jobs section) to describe the hooks.

I'll respond in order:

Only one of the others uses context (scheduler_args_test.rb), the rest use the format I used. I'll gladly port it if you wish, but I was attempting to adhere to the project's existing tests.
Done.
Done.
Done.

Yeah.  I just ported the rest yesterday :).  I totally understand why you did it the way you did it.  You might want to merge from master.

Ah! No wonder I didn't catch that :)
I ported my tests to use context
Anything else?

No, I think it looks good.


example fails to launch

Running the robot launch example fails with:
ros2 launch rmcl_example start_robot_launch.py
[INFO] [launch]: All log files can be found below /home/iliabara/.ros/log/2024-07-07-14-12-59-307095-Brigid-Framework16-90676
[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch]: Caught exception in launch (see debug for traceback): Caught multiple exceptions when trying to load file of format [py]:
 - ModuleNotFoundError: No module named 'scripts'
 - InvalidFrontendLaunchFileError: The launch file may have a syntax error, or its format is unknown

This seems to be related to:
https://github.com/aock/rmcl_example/blob/main/launch/start_robot_launch.py#L8

Interesting problem. I have tested it on several computers without having this problem. Just now I updated my ROS-humble and it still works. So I am not able to reproduce the problem. However, I have two guesses that might fix your problem:

Maybe something is wrong with your Gazebo installation: https://robotics.stackexchange.com/questions/103799/importerror-cannot-import-name-gazeborospaths-from-scripts

Or maybe you have another "scripts" package somewhere that hides Gazebo's scripts package: https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1050#issuecomment-651126179

Let me know if one of these solves your issue. Nevertheless, I don't like that there is a package-include called "scripts" in my python script anyways. So in the meantime I will try to find a workaround to avoid that.

I think I have found a workaround. It is in the "avoid-gazebo-scripts" branch. You may try this solution first before you change anything on your system.

@iliabaranov  have you tried it?


contact form not working

On form Contact US , the action it's calling just displays the same page again instead of sending the email
   <form action="@Url.Action("Contact", "Home" )" id="form0" method="post" role="form" ...

I am also not able to send emails!

Was this ever resolved? I am having trouble setting external SMTP. Contact form does not work and neither does the other email options (forgot password, confirmation link, etc)


Add support for extras tollways, waycategory, traildifficulty and roadaccessrestrictions

Add the support for the following extras in app settings:

tollways
waycategory
traildifficulty
roadaccessrestrictions

Done


WIP: stats.mstats consistency with stats.stats

make the signatures of common functions between stats
and mstats as similar as possible.

Extending the test for tmax so this change is covered would be useful. Can be completely analogous to the tmin test.

I assume this is a WIP PR and you want to add a few more functions? Would be good to signal when it's ready to merge, and change the PR title to be a bit more specific.

@rgommers, you beat me to it. Yes, this is a WIP, I just added the most trivial function to have this PR as a placeholder.
I am writing up the list of functions along with my observations. All in all I found 13 functions that need to be addressed. Will post them presently for discussion.

Here is the list of common functions that have some differences coupled with some of my observations:
ttest_ind:
This one is addessed in gh-5007. So nothing to do here.
describe:
Also (partially) addressed in gh-5007. ddof default is different so it must be decided if it should be changed to make them identical.
tmax:
upperlimit in mstats had no default. Fixed. Test pending.
tmean, tvar and tsem:
These functions (in mstats) use a helper function called trima which doesn't implement axis, so none of these functions do, either. tvar and tsem are also missing the ddof keyword.
mannwhitneyu:
Missing alternative keyword. This function is scheduled for deprecation so I'm not sure whether to change it or not.
kendalltau: initial_lexsort keyword is missing in mstats. use_ties and use_missing keywords are missing in stats
trimboth: proportiontocut has no default value in stats. axis keyword has a different default value (0 and 1). inclusive keyword missing from stats. Same input with different names (a and data).
linregress: In mstats the input params are *args but the implementation assumes just one or two params (equivalent to the stats version: x, y=None) and then it defers to calculation to the stats.linregress so the function signature should be changed accordingly.
scoreatpercentile: interpolation_method keyword missing from mstats. alphap and betap keywords missing from stats. Same input parameter with different names (i.e. a and data).
signaltonoise: ddof keyword missing from mstats. Same input parameter with different names (i.e. a and data).
spearmanr: axis keyword missing from mstats. use_ties keyword missing from stats. Same input parameter with different names (i.e. a, b and x, y).

General considerations:

What to do when an input is implemented in both stats and mstats but with different names? Should the difference be allowed or should we risk breaking some code for the sake of similarity? **note: these are index input values, not keyword input values.
What about when one input has different default values? These changes are bound to break some code.
Should mannwhitneyu be ignored due to being scheduled for deprecation?
Missing keywords should be reviewed on a case to case basis IMO so I will not comment on those yet.

Notes:

Added a test for tmax.
Added a default value of 0.2 to keyword proportiontocut in stats.trimboth.
Changed (*args) for (x, y=None) in mstats.linregress and removed some code that didn't seem to make sense (e.g. if args.size == 2 nested inside if args.size == 1).

I'm afraid for all of the other changes that I outlined, there will need to be a discussion on a case to case basis. I wonder if it would be best to treat those in separate PRs.

Fot completeness, here's https://github.com/scipy/scipy/issues/3328 whoch is also dealing with stats/mstats inconsistency

I'd say add to this PR only the changes that require no discussion or backwards compat issues. I think the only ones in addition to the changes you already have are:

tmean, tvar and tsem: can add axis and ddof keywords to all of them.

For signaltonoise and mannwhitneyu, those are deprecated and about to be deprecated respectively, so don't bother with those.

So then there are exactly 5 (if I counted correctly) functions left where we'd have to make a backwards incompatible change:

describe
kendalltau
trimboth
scoreatpercentile
spearmanr

I'd say open a new issue for those; it'll get lost in this PR. I'd be tempted to just break backwards compat for all of them in the mstats versions.

The stats version of tmean, tvar and tsem already supports masked arrays so reimplementing seems redundant.
Also, the mstats version all do their work through a helper function trima. It would be easier to have mstats functions delegate to statsI think.

The stats version of tmean, tvar and tsem already supports masked arrays so reimplementing seems redundant.

I don't think so. The first line is a = asarray(a), so the mask simply gets thrown away in the stats version. To check that that's indeed the case:
In [10]: x = np.ma.arange(3)

In [11]: stats.tmean(x)
Out[11]: 1.0

In [12]: x.mask = [0, 0, 1]

In [13]: stats.tmean(x)
Out[13]: 1.0

In [14]: stats.mstats.tmean(x)
Out[14]: 0.5

Latest changes:

Addition of axis keyword to tmean, tsem and tvar.
Addition of ddof keyword to tsemand tvar.
Removed default value for proportiontocut in stats.trimboth.
Eliminated the change flatten x in linregress.

Notes:

The implementation of tvar was changed because the previous implementation lost precision when adding the axis and ddof keywords.
The implementation of flatten x and y in linregress had to be changed because of the modification of its signature (see gh-5168)

If there are any comments or changes I will try to address them as soon as possible, but I am officially signing off. I am moving to Canada in less than 24 hours and I have some serious packing to do and documents to organise.

@aeklant have a good flight!

okay, this all looks good. merging. thanks @aeklant


correct error where "yarn" is prepended and doubled

We are accidentally prepending 'yarn' to the value here where we instead mean to replace it

/gcbrun


Polyfilled console is empty

Using the default plugin configuration, console appears to be polyfilled as an empty object.
One of my dependencies uses uuid which uses util.deprecate - but in util the console is simply an empty object so errors when it tries to call console.error
new NodePolyfillPlugin({
			excludeAliases: ["console"]
		}),

Appears to fix it.

Errors with polyfilling the console have been popping up a lot. I'm considering no longer polyfilling it by default any more. Thoughts?

Please do not polyfill it anymore. I still have issues with it presently


Instance for Data.Lazy

Hi!
It would be nice if there was an instance for Data.Lazy. I was thinking maybe just use D.opaque_ "function" as the Repr? What do you think?
P.S: Willing to make a PR, and thanks for this lib it's really cool.  I am playing/learning lazy streams and this library helps a lot with visualization.

Glad to hear it! Yeah, I think adding that instance would be good. I feel like having it force the contained value and display that, deferring to its Debug instance, could be a bit more useful?

In general I think forcing things during debugging is reasonable. If you really need to debug something that contains a Lazy without forcing it, you could always extract the relevant information from it first, and just display that.

Oh, yes. I thought that debug would be acting as our toString type of function. I was comparing it a bit too much with the Rust version. I guess that if one wants to see it normally in the repl they can just use the show function.
Because I want to be able to see how the values get evaluated one by one I prefer to see the <function>. My current solution should work for other people though, what I did is just wrap the Data.Lazy in a newtype and defined my own Debug instance.
Anyhow, I can add the instance for Lazy forcing the evaluation, if you will accept PR?

Sounds good! Come to think of it, another option would be to actually show whether the thing is forced or not, and only display it if it has been forced. That's very dodgy under normal circumstances, but for debugging it's probably acceptable.

I don't really mind which, actually, we can always change it later.

Great!
How can I tell if a lazy value has been evaluated or not? For example,
https://github.com/purescript/purescript-lists/blob/62900a56f6864638c952575dfd211a1cc55be7da/src/Data/List/Lazy/Types.purs#L30-L35.
The Cons needs a List which accepts a Lazy (Step a). Would we need another data constructor in data List a = ...  say Evaluated a? Or should we extend the Lazy data type?

Looking at the implementation: https://github.com/purescript/purescript-lazy/blob/master/src/Data/Lazy.js it seems like a Lazy value is just a function which, when evaluated, forces the value if necessary and then returns it. So it looks like there's no way of asking a Lazy value whether or not it has been evaluated. I'm not sure if this would be considered a good addition to the API; in general it should probably not be possible to ask a Lazy value whether it has been forced yet.


Can't change Content-Disposition name "file"

At the current version, it's not possible to change the Content-Disposition property "name". See line 87.
Here's an example of the header:
Content-Disposition: form-data; name="file"; filename="filename.jpg"
Content-Type: image/jpeg

It would be good if we could change it :-)

Is config param "fileFormDataName" available?
I set

Upload.setDefaults({ fileFormDataName: "uploadDialog$ctl00$ctl00$fileUpload$ctl00$ctl00$uploadInput" });

and still is sends

Content-Disposition: form-data; name="file";

I tried to insert it to different places of Upload.upload({..}) and it didn't work.
Please help.

@v-andrew that option was deprecated and removed while ago, look at the data option in the readme file: data: {newFileKey: myFile}


Won't play nice with concealing

I was just trying https://github.com/enomsg/vim-haskellConcealPlus and notice vim-operator-highlight was completely blocking it from working. I believe it should be mentioned in readme/docs at last.

This issue also should be the reason for turning jedi-vim broken:
https://github.com/davidhalter/jedi-vim/issues/415

For reference, here's what jedi-vim does to setup the concealing / syntax highlighting: https://github.com/davidhalter/jedi-vim/blob/master/after/syntax/python.vim
Maybe vim-operator-highlight could use containedin=ALL?
(here: https://github.com/Valloric/vim-operator-highlight/blob/master/plugin/operator_highlight.vim#L72)
@oblitum
Can you test if that fixes the issue, please?

yes, for sure.

@blueyed Putting containedin=ALL at the end of the line didn't have any effect.


CSV: Error: getting Column numbers, aborting

Hi it's me again,
Thanks for fixing #71 so quickly. I tried the updated version of csv-vim just now, but I am receiving the error CSV: Error: getting Column numbers, aborting when trying to open csv files now.
I previously had version 0.31 installed from the homepage. I uninstalled it by doing :RmVimball csv.vmb and then installed by cloning the git repo, opening csv.vmb and running :so %.  also tried installing by running make in the downloaded git-directory, which gives the same result. When I uninstall the updated plugin from Github and install the old version 0.31 again,  opening csv-files works fine.
Any idea of what the issue is?

Are you using a plugin manager? I think, you should not mix using vimball and plugin manager.  I just updated the vimball version. Please try that.
What i did for testing: I used your testfile:
# This file contains this and that
# Some more comments

Col1,Col2,Col3
row1,row1,row1,
row2,row2,row2

Then I added some empty lines at the top and restarted vim. This correctly adapted the highlighting. Can you try this?

Sorry for the late reply, I got busy at work. I am using VimPlug for a few other plugins, but that never caused any conflicts with VimBall back when I was using csv.vim-0.31, so I don't think that is the culprit.
I tried reinstalling the updated vimball, but I am getting the same error as before. I have been able to pinpoint it to ArrangeColumn. I have this set up automatically in my .vimrc so I forgot about it earlier. When I commented it out, everything works as expected and the correct line is highlighted as the header line when opening the testfile.
When I try to run ArrangeColumn with the testfile from inside vim, the same buggy behavior repeats itself, so it seems like that function is not playing well with the edits you made regarding #71 .
More info regarding the error:

In addition to the error message, the processor spins up, vim freezes for about  10 seconds and then renders the file with the columns in incorrect positions, some lines folded, and

Hi joelostblom!
On So, 29 Nov 2015, joelostblom wrote:

Sorry for the late reply, I got busy at work. I am using VimPlug for a few other plugins, but that never caused any conflicts with VimBall back when I was using csv.vim-0.31, so I don't think that is the culprit.
I tried reinstalling the updated vimball, but I am getting the same error as before. I have been able to pinpoint it to ArrangeColumn. I have this set up automatically in my .vimrc so I forgot about it earlier. When I commented it out, everything works as expected and the correct line is highlighted as the header line when opening the testfile.
When I try to run ArrangeColumn with the testfile from inside vim, the same buggy behavior repeats itself, so it seems like that function is not playing well with the edits you made regarding #71 .
More info regarding the error:

In addition to the error message, the processor spins up, vim freezes for about  10 seconds and then renders the file with the columns in incorrect positions, some lines folded, and

Thanks for pointing it out. I'll look into fixing this next week.
Best,
Christian
Ich hatte gehofft, daß das durch je höher der Kirchturm desto
bim aufgefangen wird.  lautdenk
-- banshee auf #LinuxGER

please check again with the latest commit. I fixed an issue with :ArrangeCol command.

Thanks for the update, unfortunately it does not seem to fix the problem for me.
To illustrate the problem, when opening the a csv-file without any automatic arrangement of columns, the comments and the header line are identified correctly and everything looks like expected:

After :ArrangeColumn, vim freezes for ten seconds and then renders the columns disorganized and spits out the same error message as earlier:

Okay, I think I found the problem. It is not obvious, because the :ArrangeColumn command behaves correctly. If you want to rearrange the complete file, please use :%ArrangeColumn. I have added some more sanitizer checks, that it does not try to arrange the header comments or the empty lines. That should work now. Please test again.

Ok, sorry for the command confusion. :ArrangeColumn was initially giving me the same result as let g:csv_autocmd_arrange = 1 in my .vimrc, so I thought they were the same command. I also apologize for all the extra work this has created...
With the new version, there are a few different issues that occurs after running :%ArrangeColumn or setting let g:csv_autocmd_arrange = 1 in .vimrc:
csv-files starting with a comment followed by either the header line or a blank line and then the header line.
:%ArrangeColumn
The warning message is displayed, but vim does not freeze and the columns are nicely arranged. With the old version, this exact behavior occurred when all rows did not have the same number of columns.
let g:csv_autocmd_arrange = 1
The warning message is displayed, but vim does not freeze and the columns are nicely arranged.
csv-files starting with the header line
:%ArrangeColumn
I now receive a new error:

Vim then arranges the columns correctly and there is no freezing.
let g:csv_autocmd_arrange = 1

The files opens but the columns are not arranged. When I try %ArrangeColumns, the above error message shows up again and the columns do not arrange.
csv-files starting with a blank line followed by the header line
Everything works as expected.

On Mi, 02 Dez 2015, joelostblom wrote:

Ok, sorry for the command confusion. :ArrangeColumn was initially giving me the same result as let g:csv_autocmd_arrange = 1 in my .vimrc, so I thought they were the same command. I also apologize for all the extra work this has created...
With the new version, there are a few different issues that occurs after running :%ArrangeColumn or setting let g:csv_autocmd_arrange = 1 in .vimrc:
csv-files starting with a comment followed by either the header line or a blank line and then the header line.
:%ArrangeColumn
The warning message is displayed, but vim does not freeze and the columns are nicely arranged. With the old version, this exact behavior occurred when all rows did not have the same number of columns.
let g:csv_autocmd_arrange = 1
The warning message is displayed, but vim does not freeze and the columns are nicely arranged.
csv-files starting with the header line
:%ArrangeColumn
I now receive a new error:

Vim then arranges the columns correctly and there is no freezing.
let g:csv_autocmd_arrange = 1

The files opens but the columns are not arranged. When I try %ArrangeColumns, the above error message shows up again and the columns do not arrange.
csv-files starting with a blank line followed by the header line
Everything works as expected.

Okay, this is getting ridiculous and i apologize for introducing new
errors.
I think the problem was, that the b:csv_headerline was not always
defined, so I made some more changes to make sure that variable is only
used when it also exists.

I just tested the newest version, but I am still receiving the same error patterns as described in my last post.

I think the culprit for the persistent b:csv_headerline errors is line 720. In addition to your added check for if the variable exists, I split that if-expression into a nested expression and it seems to help.
I am still getting the warning message CSV: Error: getting Column numbers, aborting!, but vim nicely arrange the columns.

I believe I just created a pull request... Not sure if I did it correctly, first time, haha. Please check it out so I don't mess things up =)

So the only remaining minor annoyance is that I am getting the column number error message every time I try to arrange columns in a file starting with a comment (or opening a file if autoarrange is set in .vimrc).
I was looking at the MaxColumns-function at line 524 that throws the error, but I couldn't really figure out what to do. Maybe replace "a:1" with "a:" . b:csv_headerline somewhere? But you already filter out comments so I couldn't figure out exactly what to do...

okay, I have a suspicion. Please use latest version and do :set verbose=1. Then run the :%ArrangeCol command as before. After it finished with the error, use :mes command and look at the line
 ArrangeCol Start: 8, End: 10

That should start at the first line or your data and end at the last line. I suspect it starts before (e.g. where the comment is) and it obviously can't calculate the optimal column width for that line, therefore it complains.

I installed the new version and set the verbose variable inside vim with the test-file open. However, this is all the output after using :mes.

okay i moved it a little higher. Please try again.

I am getting the same output from :mes as previously. Are you seeing something different on your system?

Sorry can't reproduce it currently. Have you configured the plugin and set some variables?

Sorry, I don't understand. Which plugin should I configure (mes or csv.vim) and how? And what variables should I set (I set verbose=1 as per your post above)?

Ok, here we go. I missed that I needed to make the .vmb-file myself every time, I was using the prepackaged one from Dec 3rd. With the latest version (pulled just now), I am still getting the column number error message. Step by step:
Opening the file without autoarrange in .vimrc, the comment line is now highlighted as the header line instead of in grey for comments:

However, after :set verbose=1 and :%ArrangeColumn, the correct region is specified (line 3-5) and columns are arranged, but the error message is still displayed (:mes shows the same output).

If I type :%ArrangeColumn a second time, there is no error message and columns stay arranged. Interestingly, if I append a line to the file before arranging the columns, the error message is not displayed! The start position is still 3, but the end position is now 6. The comment is still highlighted as a header line.

Hi @joelostblom,
I have a .vim directory in ~/ and in that I have a bundle. In the bundle directory (~/.vim/bundle), I have csv.vim. I simply git clone https://github.com/chrisbra/csv.vim in the bundle directory and when an update is ready, git pull.
You could download the zip from master and move into your bundle directory, but when I download it, I need to change the name from csv.vim-master to csv.vim.

Thanks for the suggestion. In this case, the latest update to csv.vmb on master was 6 days ago, but there has been updates to some of the scripts ~ 2 days ago. So if I git pull the entire directory and make the csv.vmb myself, wouldn't I be more up to date than with your approach? Your might be more convenient though as soon as we have figured out the issues I am having.

I think in the end mine is more straight forward as you just git pull from a single directory.
As far as resolving your issue, have you shared the exact file that has a problem? You can use gist.github.com to share it.

Yeah, the source file is shared above. It is quite simple, just:
# This file contains this and that
# Some more comments

Col1,Col2,Col3
row1,row1,row1,
row2,row2,row2

In the latest test I did, I only have one commented line. But I don't think it is the specific file as I am having the same issue with all my csv-files.

Hi joelostblom!
On Di, 08 Dez 2015, joelostblom wrote:

Yeah, the source file is shared above. It is quite simple, just:
# This file contains this and that
# Some more comments

Col1,Col2,Col3
row1,row1,row1,
row2,row2,row2

In the latest test I did, I only have one commented line. But I don't think it is the specific file as I am having the same issue with all my csv-files.

I think I found the error. Please update and test again. Thanks for
being so patient.
Best,
Christian
Bürokommunikation? Schreibtischgelaber!

You did find the error! There are now no warning messages and the columns arrange correctly. Thanks for spending so much time on it!
I noticed that the comment lines are now highlighted as header lines rather than comments. I can open a new issue if you want, but I imagined it was just a small fix since everything else is working now. Thanks again!
Currently:

Previously:

Hi joelostblom!
On Di, 08 Dez 2015, joelostblom wrote:

You did find the error! There are now no warning messages and the columns arrange correctly. Thanks for spending so much time on it!
I noticed that the comment lines are now highlighted as header lines rather than comments. I can open a new issue if you want, but I imagined it was just a small fix since everything else is working now. Thanks again!

Can you show me the output of :syn
Best,
Christian
Er lobt mit Vergnügen die Tugenden des andern und rügt mit Vergnügen
seine Fehler.
-- Jean Paul (eig. Johann Paul Friedrich Richter)

Please set :let g:csv_comment='#' in your .vimrc, the default comes from the commentstring setting and is /*%s*/ and therefore the plugins expects /* as comment string by default

I already have that line in my .vimrc. Overall my .vimrc is the same as
when the comments were highlighted correctly in the screenshot above, the
only thing that changed are the new updates to csv.vmb.
I think comments are detected correctly, just highlighted incorrectly. I
did a test where I switched # to /* and now only the first comment is in
bold red, instead of both the comments and the first following line as
shown previously.

On Thu, Dec 10, 2015 at 12:14 PM, Christian Brabandt <
<EMAIL_ADDRESS>wrote:

Please set :let g:csv_comment='#' in your .vimrc, the default comes from
the commentstring setting and is /%s/ and therefore the plugins expects
/* as comment string by default
—
Reply to this email directly or view it on GitHub
https://github.com/chrisbra/csv.vim/issues/72#issuecomment-163690942.

Are you sure, that is correct in your .vimrc? The syntax file should pick it up and I don't see, why it shouldn't. Can you show me the vimrc?

Yes I'm pretty sure it is correct. Here is a minimal version of my .vimc,
which I tested with and it reproduced the highlighting problem:
call plug#begin()
Plug 'tpope/vim-sensible'
Plug 'vim-pandoc/vim-pandoc'
Plug 'vim-pandoc/vim-pandoc-syntax'
Plug 'ervandew/supertab'
Plug 'morhetz/gruvbox'
call plug#end()

" Set colorscheme
colorscheme gruvbox
set background=dark

" Enable pandoc spellcheck
let g:pandoc#spell#enabled = 1

" Enable recognition of file types >> syntax highlighting (required for
csv-plugin)
:filetype plugin indent on

" Calculate and auto arange column width in csv-files under a certain size
let g:csv_autocmd_arrange = 1
let g:csv_autocmd_arrange_size = 2048*2048

" Enable comments in csv files, this plugin is genious!
:let g:csv_comment = '#'

" Set the default vim clipboard to be the same as the system clipboard
set clipboard=unnamedplus

" Remap command key not to have to press shift
nore ; :

On Thu, Dec 10, 2015 at 5:16 PM, Christian Brabandt <
<EMAIL_ADDRESS>wrote:

Are you sure, that is correct in your .vimrc? The syntax file should pick
it up and I don't see, why it shouldn't. Can you show me the vimrc?
—
Reply to this email directly or view it on GitHub
https://github.com/chrisbra/csv.vim/issues/72#issuecomment-163765307.

and you installed the csv plugin as vimball, right?

Joy! I just pulled the newest csv.vmb changes from 20 h ago and comments are highlighted correctly now!
Again, thank you so much for creating this plugin and being so responsive in sorting out the issues I was having =)


Creation date handling

Creation dates are wrongly handled on the website, for instance here
This date comes from stats.json.
It is then processed here, and finally displayed there

Fixed issues and migrated the repo there: https://github.com/datagouv/table-schema-to-markdown


Test hero midflight reversals

Test two similar hero scenarios:

A navigator pop occurs while a push hero transition is underway.
A navigator push occurs while a pop hero transition is underway.

Also revised the doc for the descendant finder a little.


Can't understand how to train, and fill the data?

I created a bot with rasa in backend and now iam using rasa ui and got confused how to pass the nlu data, stories, configurations, and fill domains and how to write actions. Can any one show me how to do it.

Hey check this link hope it will help you out .. https://forum.rasa.com/t/regarding-rasa-multibots/27722


Alternatives to Shiny

While programming our own platform would provide a great degree of customization, we should also explore some alternative platforms:

MapsCorps
Google Maps

We've moved the app over to Javascript/Leaflet.


Placeholder does not re-appear if field value is set to undefined

I have a dropdown dependent on a value that can be reset (changed to undefined) from outside the dropdown.  I've observed that the value can be reset just fine, and that reflects in my component's state, but the value displayed by the dropdown does not return to the placeholder prop.
The dropdown works fine after this reset; I can still open it and choose a new value, but until I choose a new value, the invalid value shows.
I logged the field the dropdown is dependent on as I reset it from outside the dropdown so you can see the value is reset:
 LOG  subcategory: fruit (type: string)
 LOG  subcategory: fruit (type: string)
 LOG  subcategory: undefined (type: undefined)

<DropDown
  mode={"outlined"}
  visible={subcatDropdownVisible}
  showDropDown={() => dispatch(...my reducer action...)}
  onDismiss={() => dispatch(...my reducer action...)}
  value={form.subcategory}
  setValue={value => dispatch(...my reducer action...)}
  list={subcategoryList}
  placeholder='subcategory'
  />

TLDR: I have two dropdowns, one dependent on category and the other subcategory (both in local state).  When category changes, I reset subcategory in the local state to undefined.  The subcategory dropdown does not display the placeholder as it did before subcategory was chosen in the first place; it still shows the previous value, but functions otherwise.

There is a minor bug that is fixed here #79 but it is not merged yet,
You can avoid that issue by adding your list a default value like
<DropDown
  mode={"outlined"}
  visible={subcatDropdownVisible}
  showDropDown={() => dispatch(...my reducer action...)}
  onDismiss={() => dispatch(...my reducer action...)}
  value={form.subcategory}
  setValue={value => dispatch(...my reducer action...)}
  list={[subcategoryList, { label: 'Please select a subcategory, value: 0}]}
  placeholder='subcategory'
/>

And update form.subcategory = 0,
You are going to see Please select a subcategory on your dropdown as a selected value.


island medals not saving (NL)

whenever i put in a number of medals (like 100) and save, it dosen't save it, it's still the number of medals i had before.

same with MEOW coupons.


[BUG]: How to render SharePoint People Picker Columns DisplayName Value

Describe the bug
How to render SharePoint People Picker Columns DisplayName Value. i always get the whole OData-PeoplePicker-Object
To Reproduce
please see screenshot
Expected behavior
Want to show only the DisplayName of the User
Screenshots

Desktop (please complete the following information):

OS: Windows 10/11
Browser. Edhe Chromium
Version [e.g. 22]

I am having the same issue on my side.

Hi @schneika,
One possible solution to this would be to use AddColumns.
Imagine if you had a sharepoint datasource Items with a column Owner

Change the DetailsList Items datasource to be: AddColumns('Items',"OwnerName",Owner.DisplayName)
Add the new OwnerName column to the Datasource Fields in the DetailsList properties
Update the Columns definition to use the new OwnerName column

Would this work for you?
Thank you for helping with the Creator Kit!

@scottdurow Ahhh! Very good idea! I have tried ClearCollect-Collection-Variables with AddColumns but this doesnt work.
Your suggestion is fine, i must AddColumns the Columns-Values directly to the SharePoint Datasource (Colelction not working for me) and have to restart the App because of a "Control not loading".
After App Restart all Columns Working
Example:
Items=
SortByColumns(Filter(AddColumns(Datasource,"UserDisplayName", ensUser.DisplayName,"ManagerDisplayName", ensManager.DisplayName,"BusinessUnitValue", ensBusinessUnit.Value,"DivisionValue", ensDivision.Value,"StatusValue", ensStatus.Value,"State", ensState,"IDValue", ID,"JobRoleValue", ensJobRole.Value,"CountryValue", ensCountry.Value),StartsWith(Title, SearchBoxTestForm.SearchText)), "Title", If(varSortFilesAsc, Descending, Ascending))_

Hi @schneika - That's great.
I've created an enhancement in the backlog to make this easier in future releases.
If this is a workable solution for you at this time - could I ask that you close this issue as resolved?
Thank you!

Just a note about this - to ensure that your queries are delegable, when you use AddColumns - do it on the outside of the Sort and Filter - that way, the sorting and filtering will be done on the server (if possible) and then the data will be added after it is retrieved.


Fix Travis

I think I broke in https://github.com/facebookincubator/create-react-app/commit/c43b249258bbd482733b6d314c2c658ab13c34e1. My change was correct for release script but it broke something in e2e. I'm going on a vacation so I'd appreciate someone taking a look.

I can take a look.

I think I fixed it in #561


New client

Because _role=service isnt working with dynamic schemas. So this is needed or I could fix the dynamic schema thing. Didn't know how _role worked and it wasnt so just did this. I can investigate further and fix _role if you would like.

LGTM. will hold off on corrdinating merge


Update digging for 4th edition

https://asmadigames.com/innovation/PatchNotes_Ultimate.pdf

Duplicate of https://github.com/micahstairs/bga-innovation/issues/1342.


feat(STONEINTG-975): e2e tests for IntegrationTestScenarios contexts

Description

Add IntegrationTestScenarios with different contexts to e2e tests
Check that the new IntegrationTestScenarios are skipped as part of testing
Check that the existing integrationTestScenarios have PLR triggered according to their context

Signed-off-by: dirgim<EMAIL_ADDRESS>Issue ticket number and link
STONEINTG-975
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

The golangci-lint check seems to be failing for issues in unchanged files, should that be fixed separately?

/retest

@dirgim yes you can ignore the error for now, it will be fixed in a separate PR
https://issues.redhat.com/browse/KFLUXBUGS-1538


Update delegate-it

Trying https://github.com/fregante/delegate-it/pull/25 out. Unfortunately it doesn't help us at all since almost none of our listeners is inlined in the delegate call, so we still need to specify the callback parameter types.
WIP. Blocked by #4115

Unblocked


iterating wreduce enters infinite loop

From my understanding of the documentation, wreduce is supposed to reduce the width of cells and wires.  It would expect that after one run (or perhaps a few), the width would be minimal, and wreduce would cease to change the design.
If you try the test code used in the documentation with wreduce
module test(input [3:0] a, b, c, output [7:0] y);
        assign y = a + b + c + 1;
    endmodule

running wreduce repeatedly does not converge, but rather it enters an infinite loop of "removing top bits" from wires.  I originally encountered this bug because it seemed wreduce was not removing unused bits in width 2 wires, or at least was introducing new wires with unused bits.

It is not really doing anything here. The "removing top bits" does not actually remove the bits. It changes the wiring around and lets a later "clean" actually get rid of them. When you call "clean" between two calls to "wreduce" then the loop will stop. When you just call "wreduce" in a loop it will prepare this wires in a way that "clean" can get rid of them over and over again.. (It renames the wires, thus it looks like its a different wire in each iteration.)
I have now fixed this in commit 0748ef638d34bb5dd125271abc4fe051f95a790d. Now wreduce recognizes the already-prepared-for-deletion wires and does not touch them a second time.

Ah, I understand.  Perhaps a note about this could be added to the wreduce documentation/output that it needs to be run in conjunction with clean?
while you're at it there is a typo in the title of this page as well (is->if)
http://www.clifford.at/yosys/cmd_wreduce.html
I am under the impression that you are looking for bug reports/typos etc for even minor things, but if you are not, feel free to let me know so you can focus on higher priorities.

Perhaps a note about this could be added to the wreduce documentation

This is a general theme in Yosys, not specific to the wreduce command. (The help message to opt_clean has something on it and I've now added some additional explanations to the CodingReadme file.)

while you're at it there is a typo in the title of this page as well

fixed. (webpage will be updated when I release yosys 0.6)

I am under the impression that you are looking for bug reports/typos etc for even minor things, ...

Yes. A steady flow of easy to fix bug reports is very welcome..  ;)

Let me just add a more detailed explanation of what was going on with wreduce (for the record):
Say you have a signal a[5:0] and only the lower 4 bits of it are used, so "wreduce" tries to "remove" the top two bits. I cannot remove a Wire object (or make it shorter, see the explanation in CodingReadme I mentioned above). So I instead create a new wire $temp42[3:0] and essentially add assign $temp42[3:0] = a[3:0] to the design. Finally I rename $temp42 to a and a to $temp42. The next call to "clean" will remove the wire $temp42.
Before my bugfix, if you called "wreduce" a 2nd time it looked at the $temp42[5:0] wire and said "hay - I can remove the two top bits from it", create a  $temp43[3:0], assign $temp43[3:0] = $temp42[5:0] and flip the names. Now after the bugfix "wreduce" understands that it is operating on wires that "clean" would throw away anyways and simply skips them.


getVMs() of regionInstanceGroup

Environment details

OS: Ubuntu 14.04.5 LTS
Node.js version: v8.11.3
npm version: 5.5.1
@google-cloud/compute version: 0.10.0

Steps to reproduce
'use strict';
const Compute = require('@google-cloud/compute');
const compute = new Compute();

async function main() {
   const [res] = await compute.getInstanceGroups({filter: "name = region-instance-group"});
   const instanceGroup = res[0];
   const vms = await instanceGroup.getVMs();
   console.log(vms);
}

main();

Expected:

a list of virtual machines

Actual:
(node:16874) UnhandledPromiseRejectionWarning: ApiError: Error during request.
    at Object.parseHttpRespBody (/home/coordinator/test_compute/node_modules/@google-cloud/common/src/util.js:193:32)
    at Object.handleResp (/home/coordinator/test_compute/node_modules/@google-cloud/common/src/util.js:137:18)
    at /home/coordinator/test_compute/node_modules/@google-cloud/common/src/util.js:502:12
    at Request.onResponse [as _callback] (/home/coordinator/test_compute/node_modules/retry-request/index.js:198:7)
    at Request.self.callback (/home/coordinator/test_compute/node_modules/request/request.js:185:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)
    at Request.<anonymous> (/home/coordinator/test_compute/node_modules/request/request.js:1161:10)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)

This happens with region instance groups only (e.g. regions/europe-west1). I suspect this lib needs to implement regionInstanceGroups class: https://cloud.google.com/compute/docs/reference/rest/v1/regionInstanceGroups

Managed instance groups will be supported through this PR: #104. There are still a few things left to do-- feel free to contribute, if you can! https://github.com/googleapis/nodejs-compute/pull/104#issuecomment-420629331

Closing as duplicate of #103.


Support for games with different titles.

For example, @liamdawson said in issue #7 that they own the game Absolute Balderdash. BoardGameGeek here suggests that the game is more commonly known as Beyond Balderdash. I am sure there are many more examples.
How should we handle this? Have an optional field on the games that specified additional names? Multiple entires on the selection screen that point to the same description? Some other solution?

Opened #22, which should cover this. The solution might lie with storing the BGG ID in game entries, and looking them up via BGG. Will have to give it some thought.

Too old


Create checkout session with custom id doesn't correspond to a firebase auth user

When checkout session is created under a customer/{id}/checkout_sessions where the {id} doesn't correspond to a firebase auth uid, the following error message is generated in the document.
"There is no user record corresponding to the provided identifier."
My thought was to create a "customer" that was independent from a single firebase auth user which would represent a company/team/organization... however the extension appears to require the customer to have the same key as a auth uid. Is this by design, or is there some workaround so that the stripe customer and customer document in firestore can be independent of a single user.

@RodanoJ I'm afraid this is by design. We need a 1-1 mapping of Firebase UID to stripe customer ID to facilitate authentication for access to the Stripe customer portal.
What you can do is track your teams in a separate collection and only allow one team admin. The team admin is a user in the customers collection. You then write an additional Cloud Function that triggers anytime a subscription on a customer changes and then check if they are a team admin and if so set access for all team members in your separate teams collection etc.


Remove AEP-128 rules

Fixes #9
This removes all rules for AIP-128 (Declarative-friendly). None of these are in use for the AEPs.

I haven't stated this directly, but I was kind of wondering if we wanted to keep the "declarative-friendly" annotation around?
I never liked the fact that we had good guidance move into other AEPs, but OTOH I don't think we can get all the good declarative-friendly guidance as MUST. We may need to conditionally enable some rules, and we'll need some flag to detect that we want those rules on.
WDYT?

Couple thoughts:

Some of these PRs are old, but the goal is to annotate every lint rule with Should/Must, where Must rules cannot be disabled. We should keep Should rules around in the linter. I'll make sure all of this gets backported to past PRs.
I don't think any of these rules - annotations, reconciling - will impact our definition of declarative-friendly, but I may be mistaken.
The DECLARATIVE_FRIENDLY annotation would be a stronger version of AEP-compliant, right? You can be AEP-compliant, but not DECLARATIVE_FRIENDLY if you follow all of the must rules and none of the shoulds?


100% CPU

Hello there,
Something got wrong ^^

VSCode is closed but this extension is still running and making my fans crazy.
Didn't know how to provide you more infos... so I simply killed the process.
By the way, nice work ! It does the job, thanks :-)

I'm also seeing this several times per day, with this extension spawning node.exe processes which never exit, even days later, and keep spawning more of them, each of which takes up 100% of a CPU core.
I sometimes see up to 8 node.exe processes leftover using 100% of a CPU core each even several days later after having closed VSCode.
This is for node.exe processes with command line args like the following:
node  C:\Users\Dan.vscode\extensions\jrieken.fuzzy-definitions-0.0.3\node_modules\nak\bin\nak --ackmate -G ".js" -d "node_modules" "(let|const|var|function|class)\s+if|if\s:"<EMAIL_ADDRESS>node  C:\Users\Dan.vscode\extensions\jrieken.fuzzy-definitions-0.0.3\node_modules\nak\bin\nak --ackmate -G ".js" -d "node_modules" "(let|const|var|function|class)\s+var|var\s:"<EMAIL_ADDRESS>It seems to happen most often if use Go To Definition for something common like "if" or "var" (though occurs in other cases too) which is really easy to do unintentionally when trying to Ctrl+Click on keywords. But even then
One of the last commits, f65c5765122516796df6b57facc2334694f44ebf, says it was supposed to "kill nak after 2secs" (where nak is the NPM module used for searching through files) but node.exe remains running longer than 2 seconds all the time, so doesn't seem to actually be working.
@jrieken
Can you please fix this and publish it for VSCode so can get this critical issue fixed?
Thanks for developing this. Fuzzy Definitions is an indispensable VSCode extension. Without it, VSCode usually can't find definitions even when have exact math for some reason for JavaScript & TypeScript (anyone found a way around that btw?). However, I can't use it or have to suffer slowing down PC all the time and constantly checking processes, without this getting fixed.
And for all the thousands of users out there, they probably aren't even aware how it is slowing down their PC.
@ Any other JS developer?,
Otherwise, since haven't gotten response from developer for this critical issue outstanding for over a year now, and there's been no commits since 2016, can someone fork this, fix and release as a new fixed extension for VSCode?

@PowerAccess How about you doing a PR this?

I implemented a fix for this for this as PR.
Please test and approve my PR #3 "Fix for Critical Issue #2: Spawning 100% CPU Processes that Never Exit"
Needs further testing first to ensure doesn't break spawning the node.exe for nak file search process and that always exits even if Ctrl-Click / Go to Definition for If or Var keywords in large projects with many node modules, for example.
Fixes & Enhancements

Fix for critical bug #2 "100% CPU" - No longer spawns many node.exe processes which use 100% of a CPU core each and never terminate, even days later.
Added options (which can change hard-coded or expose as user settings ideally) for reducing CPU priority
Git ignored package-lock.json
Changed extension category to new "Programming Languages" instead of "Programming" to fix warning for that
Updated version, bumped to 1.0.0 since is fairly stable and unlikely to change much further soon.
Mentioned TypeScript in extension/package description as well.

Notes

I added a dependency package, so be sure to run npm install after pulling

To-Do Suggestions

Expose settings under //Settings: section in search.js as extension settings to control timeout, CPU priority, etc.

so what's the status with this? I have to kill this node process 20 times a day :(


Bounding Sphere from Dynamics 365 Guides

Describe the solution you'd like
Our end users are very happy with using the bounding sphere of Dynamics 365 Guides to get a comfortable usability for rotating and scaling the icons precisely e.g. arrow, marks, etc, instead of using the classic bounding box of the MRTK. With the bounding sphere, they can rotate dynamically around the X- and Y-Axis, and also use the free axis rotation. Also they can scale with a dynamic scale bar.
Describe alternatives you've considered
Our end users still have problems with using the classic bounding box of the MRTK. Sometimes, they can't catch the corners and edges precisely and couldn't do a proper rotation.
Additional context
We would look forward to the bounding sphere feature for the next MRTK release. :)

Closing as stale.


Download locations

Describe the bug
Probably not a Bug, I just don't figure out how to.
To Reproduce
I can't create a folder for download locations because I can't see the drives.
What am I ruining?
Thank you very much for your help!
Screenshots
http://gofile.me/5pdzC/jILw0lErd
Desktop

Browser: [Google Chrome]
Build:   [Windows]
Version: [1.16.1]

Sorry, my question is irrelevant. I downloaded it again and now it's good :)
Just one more question, can you view the folders on an existing drive?

Hi, that folder view is not the complete picture. All of those folders are populated based on the torrents you have downloaded.
So as you download more torrents, and in more unique places, those folders will begin to show up. Hope that clears things up.

Closing as it seems to be resolved.


jinja2.exceptions.TemplateNotFound: errors/server_error.html

jinja2.exceptions.TemplateNotFound: errors/server_error.html

The template is there: https://github.com/quokkaproject/quokka/blob/development/quokka/themes/pure/templates/errors/server_error.html
Can you give more information? which theme are you using?

[root@ctos errors]# pwd
/data/quokka/quokka/themes/pure/templates/errors
[root@ctos errors]# ls
access_forbidden.html  method_not_allowed.html  page_not_found.html  server_error.html

thank you !
why I meet this error?
because I have deployed a previous version of quokka , calmops.com, I just want to update code to
the latest version, so I encountered the error.
I deployed the latest version from scratch this morning, it works well.
so the next step is how to update it to the latest version.

@Chaniel , Do you check your configuration of  'DEFAULT_THEME'?
Check the database also, the config table. I used to encounter such error, and found out one document set the DEFAULT_THEME to some value other than pure.

when DEFAULT_THEME = 'admin'

No, keep DEFAULT_THEME to pure. Can you connect to your mongodb database? If you can, you can check if there is one entry that sets the DEFAULT_THEME like this:
{
"content_format" : "html",
"available_at" : ISODate("2015-07-13T16:24:08.798Z"),
"created_at" : ISODate("2015-07-13T16:24:08.798Z"),
"updated_at" : ISODate("2015-07-13T16:24:08.798Z"),
"published" : false,
"values" : [
	{
		"name" : "DEFAULT_THEME",
		"rawvalue" : "default",
		"formatter" : "text"
	},
	{
		"name" : "ADMIN_THEME",
		"rawvalue" : "cosmo",
		"formatter" : "text"
	}
],
"group" : "settings",
"description" : "App settings override CAUTION!!!"
}

I cant find  THEME like content in config collection.
{
"_id": ObjectId("561943e700e5ab2a83f68cd2"),
"values": [
{
"name": "EXAMPLE",
"rawvalue": "this_overwrite_the_value_in_settings",
"formatter": "text"
}
],
"content_format": "html",
"available_at": ISODate("2015-10-11T00:59:19.577Z"),
"created_at": ISODate("2015-10-11T00:59:19.577Z"),
"updated_at": ISODate("2015-10-11T00:59:19.577Z"),
"authors": [
],
"published": false,
"group": "settings",
"description": "App settings override CAUTION!!!"

}

can you paste the full page of this error?

I also meet a seemed problem :8ball: TemplateNotFound: content/default_list.html.
I want to change some detail and test why.

@rochacbruno I can find my detail_list.html file at pure /.../default_list,but when i run server and open html file,the bug also at there.
@realli I also have no results by the way your discuss


Persisting and restoring the Log: user level functions would be nice

Hello Alberto,
shouldn't there be user level functions in the Logged module to allow fetching and setting the log?
I wan't to persist the log to disk. Currently I would have to use Log from the internal package together with getData and setData.
Do I need to to persist all components of Log?
I am also not sure how to set all the variables of Log correctly when setting the restored log I have retrieved from the disk before starting the computation.
Rene.

Hi,
For what purpose you need it? Probably to save state and continue execution later.
I have to create a basic save-stop-recovery-continue execution functionality.
The structure is:
Log (recovery mode or not) (pointer to the remaining elements not read)  (all elements in reverse order)
Really only is necessary to persist the last element since it has all the log (reversed)
to save the state:
save file= do
Log _ _ log <- getData
writeFile file log
load file= do
log <- readFile file
setData True (reverse log) log
But I have to test it. Tomorrow I will try to make it work.

Hi Alberto,
Thankyou for the speed response.
Yes to stop and continue execution later. Basically suspend and resume.
No hurry though. I am just playing around.
I would have thought that when we have
f = do
logged f1
logged f2
logged f3
suspend
later steps
That there would be three entries in the log, and that we need all three, as I will be running f again and each logged statement will read one of the log entries each?
Rene.

Yes the file will have three entries.
In a general suspend primitive for the TransIO monad,  the file may have different many logs. For example :
f = do
r <-  logged $ choose [1.. 100]
logged $ print r
suspend
later steps
then the file will have 100 logs!!! of two elements each.
Then the restart would need to re execute the 100 logs

Hi Rene:
I solved the single threaded case that may be useful for you:
suspend, checkpoint and restore defined here, with an example:
{-# LANGUAGE   CPP, ScopedTypeVariables #-}
import Transient.Base
import Control.Applicative
import Control.Monad.IO.Class
import Transient.Internals
import Transient.Logged
import Control.Exception

suspend :: String -> a -> TransIO a
suspend file x= do
   Log recovery _ log <- getData `onNothing` return (Log False [] [])
   if recovery then return x else do
        liftIO $ writeFile file $ show log
        exit x

checkpoint :: String -> TransIO ()
checkpoint file= do
   Log recovery _ log <- getData  `onNothing` return (Log False [] [])
   if recovery then return () else do
        liftIO $ writeFile file  $ show log
        return ()

restore :: String -> TransIO a -> TransIO a
restore file  proc= do
     log <- liftIO $ (readFile file >>= return . read) `catch` (\(e ::SomeException) -> return [])
     setData $ Log True (reverse log) log
     proc

main= keep $ restore "file" $ do
     logged $ liftIO $ print "hello"
     suspend "file" ()
     logged $ liftIO $ print "world"

Thankyou!

Added restore, suspend and checkpoint for the general case:


open-source-explained

https://github.com/nhs-pycom/open-source-explained
We are commissioning a physical booklet summarising everything open-source into an easy-to-read format with pictures and infographics, that introduces the idea to NHS staff.
Inspiration drawn from the NHS England "Making Data Count" team: https://www.england.nhs.uk/publication/making-data-count/
Chapters

What is open-source?
Open-source Tools
Git and GitHub/GitLab
Reproducible Analytical Pipelines
Open NHS Datasets
Communities of Practice
NHS Policy
Professional Development

Features

NHS App
Digital Service Manual
NHSR plot the dots
openSAFELY

11th Aug Update:

Met with design company and outlined basic idea.
Sent outline of content: https://github.com/nhs-pycom/open-source-explained


is it possible to runknex,js queries in models?

hai im planning to run knes.js queries in model? is that possible?

Yes
User.query().where('').fetch()

Just make sure to call fetch at the end

So ill instantiate a const Database = use (''Database")
and the class model will be extended in Lucid, then query like that?
On Fri, May 27, 2016 at 9:01 PM, Harminder Virk<EMAIL_ADDRESS>wrote:

Closed #172 https://github.com/adonisjs/adonis-framework/issues/172.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adonisjs/adonis-framework/issues/172#event-674423880,
or mute the thread
https://github.com/notifications/unsubscribe/ALxWpfNm_vE47QBL67EwWTbX8NKsxpBAks5qFusQgaJpZM4IocYY
.

No, you can use the QueryBuilder by using the Database class but you can also directly use your model.
You only need to call the query() method to have back the QueryBuilder without doing something special.
Not that Lucid wrap the QueryBuilder to have a pretty API. :)

Hi, I am a beginer with AdonisJs. How Can I to do this with my Model ?
const query = Database.table('users')

if (username) {
  query.where('username', username)
}

I am trying something like this:
'use strict'
const User = use('App/Model/User')

class UsersController {

  * index(request, response) {
    const Users = yield User.where('active', true)

    if (username) {
      Users.where('username', username)
    }
 }
}

but I recive this messagem: users.where is not a function
thanks


Add clarity around merge job usage

What are you changing in this pull request and why?
The first commit is to make it clearer that merge jobs can be triggered by merges to custom branches (not only the main branch).
The second commit adds a section to clarify that customers must first run dbt compile on their merge job in order to generate a manifest for future runs to defer to.
Checklist

[X] Review the Content style guide so my content adheres to these guidelines.
[ ] For docs versioning, review how to version a whole page and version a block of content.
[ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

per slack convo, batching this update with this sprint's changes and tracking it with the docs issue mentioned in this pr.


Impelement Indonesia details API

we will provide information about Indonesia data from this api https://indonesia-covid-19-api.now.sh/api. there are basically 2 options here:

Transform the API and combine it with existing API
Create another Country Detail Page that has more information about the country, in case of Indonesia, we can make it special by fetching data from the API and provides more insight, this can be the continuation from issue #18

I think as the data has a lot of differences with the existing API, option 2 is more viable with more effort

What about create new entry point? like Country Detail for now it's only indonesia, but we can add another for next.

yes, that's like second option, where do you want to put the entry point?

I will try to implement this


Mesh : check case mesh was provided with no .material or .geometry set.

"this will most probably never happen" or "it can / will never happen" ?
If in both cases three.js throws an Error (I'm pretty sure it will) at some point, we don't need to do it -> simplify.
https://github.com/vatro/svelthree/blob/8fb54d28b52b43532b15600bd01d4712f2032ed6/src/components/Mesh.svelte#L121-L148

resolved, see 3478ee6ff0266af9696035ec9a2d54edc3ac6676


[all] Setup GitHub Dependabot or Renovate to automated dependency updates

Let's consider using GitHub Dependabot or Renovate for regular dependency updates in the new mono-repo.

GitHub Dependabot: https://docs.github.com/en/code-security/supply-chain-security/about-dependabot-version-updates
Renovate: https://github.com/marketplace/renovate

We could run the bot on a weekly basis and get PRs, that we would review and merge manually.
An example Renovate config can be found here.

Hi @abdonrd! I worked with the Modern Web team to create their Renovate configuration. I'd be happy to help set up a Renovate config for the Lit repo.
I prefer Renovate over Dependabot because Renovate is more customizable. You can change almost every aspect of how Renovate works in your repository. For example, you could do any of these:

Updates tested on a new branch. If they pass CI, they are automatically merged into the main branch. If not, Renovate opens a PR.
Minor and patch updates automatically merged if they pass CI, and major updates opened as PRs.
Group certain packages together into one PR (for example, all packages whose names contain "eslint").
Run only on certain days of the week or only during certain times of day.
Customize any setting only for certain updates (based on package name, dependency type, semver type, etc).

In the Modern Web repo, the team opted not to update minor and patch releases. They tried it for a couple weeks but I presume they found it to be too noisy. Their configuration now does not automerge anything and does not update minor or patch versions. It opens PRs for major version releases immediately and for lock file updates once per week.
How would you like your updates to work?

Dependabot is set up


NTR: galactose in cell wall decreased

PMID:9839953
standard def (have "absent")

We added FYPO:0006807 decreased galactose level in cell surface glycoprotein glycan
for the same paper in #3406. Is this any different?

no, I already used that but forgot to remove my placeholder annotations


fixes adding unnecessary blank lines

fixes adding unnecessary blank lines everytime user clicks save wildcard button

Thanks for the PR. White space is actually necessary, especially if you're heavily annotating your wildcard files, e.g.
# Black and white
# Sourced from https://www.bhphotovideo.com/explora/photography/hands-review/black-and-white-film-roundup

# Kodak
Tri-X 320       # Lower contrast profile than Tri-X 400. Smoother grain structure.
Tri-X 400       # Classic. Grainy
T-Max 100       # Similar to T-Max 100
T-Max 400       # Contemporary. Fine grain, Smooth
T-Max 3200      # Low-light. salt and pepper look of high speed film

# Ilford

Pan F Plus      # 50 Iso, very slow, no grain, broad tonal range
FP4 Plus	# Medium speed, fine grain, normal constrast, wide exposure latitude
HP5 Plus	# Classic, versitile
Delta 100	# Fine grain
Delta 400	# Fine grain
Delta 3200	# Fine grain, low light also daytime
SFX 200         # Extended red sensitivity - infrared effects with red filter
XP2 Super       # Chromogenic film
Ortho Plus      # Orthochromatic film. Sensitive to blue and green light.

# Rollei
Infrared 400    # Infrared film
Retro 80S       # Extended red sensitivity, reduce haze or fog. Smooth blemishes.
Retro 400S      # Extended red sensitivity, reduce haze or fog. Smooth blemishes.
RPX 25	        # Solid
RPX 100	        # Solid
RPX 400	        # Solid
Superpan 200	# Extended red sensitivity, technical film appearance, high contrast and moderate grain
Ortho 25	# Blue and green sensitive. Slow film, fine grain, high sharpness.
Copex Rapid	# Extremely high sharpness and resolution. High contrast and full-range tones.

# Lomography
Earl Grey 100	# Smooth grain, broad tonal ranges. Simple
Earl Grey 400	# Smooth grain, broad tonal ranges. Simple
Potsdam Kino 100 # Classic, historic look.
Berlin Kino 400 # Similar to Potsdam Kino 100

# Adox
Silvermax 100	# Wide tonal range
Scala 160	# Meant for black and white transparencies. Deep tonal range.
HR-50		# Extended red sensitivity, unique infrared effects. High sharpness, little grain.
CMS 20 II	# High sharpness, fine resolution, little grain.

# Foma
100 Classic	# Finely grained
200 Creative	# Finely grained
400 Action	# Finely grained
Fomapan R100	# intended for slides
Retropan 320 soft # Low contrast, high grain structure

# Agfa
APX 100
APX 400

# Arista
EDU Ultra 100
EDU Ultra 200
EDU Ultra 400

Bergger Pancro 400 # Fine grain and high resolution, medium contrast

# CatLABS
X Film 800
X Film 320

# Cinestill
BwXX Double-X 500T # Subtle tonality, fine grain, high sharpness

# Japan Camera Hunter
StreetPan 400

# Shanghai Film
GP3 100