dbt seed --show fails

Issue
Issue description
dbt seed --show command fails with 2 exit code.
Results
❯ dbt seed --show
Found 25 models, 8 tests, 0 archives, 0 analyses, 109 macros, 2 operations, 1 seed files

15:12:45 | Concurrency: 1 threads (target='default')
15:12:45 |
15:12:45 | 1 of 1 START seed file ANALYTICS_PROD.cancellation_coeff............. [RUN]
15:12:47 | 1 of 1 OK loaded seed file ANALYTICS_PROD.cancellation_coeff......... [INSERT 14 in 1.74s]
15:12:47 |
15:12:47 | Finished running 1 seeds in 5.03s.
Encountered an error:
'agate_table'

❯ echo $status
2

In the logs I see this:
2019-02-12 10:58:28,566 (MainThread): Sending event: {'category': 'dbt', 'action': 'invocation', 'label': 'end', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x10bcc7e48>, <snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x108697518>, <snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x10bca7358>]}
2019-02-12 10:58:29,028 (MainThread): Flushing usage events
2019-02-12 10:58:29,028 (MainThread): Encountered an error:
2019-02-12 10:58:29,029 (MainThread): 'agate_table'
2019-02-12 10:58:29,029 (MainThread): Traceback (most recent call last):
  File "/usr/local/Cellar/dbt/0.12.2/libexec/lib/python3.7/site-packages/dbt/main.py", line 77, in main
    results, succeeded = handle_and_check(args)
  File "/usr/local/Cellar/dbt/0.12.2/libexec/lib/python3.7/site-packages/dbt/main.py", line 151, in handle_and_check
    task, res = run_from_args(parsed)
  File "/usr/local/Cellar/dbt/0.12.2/libexec/lib/python3.7/site-packages/dbt/main.py", line 207, in run_from_args
    results = run_from_task(task, cfg, parsed)
  File "/usr/local/Cellar/dbt/0.12.2/libexec/lib/python3.7/site-packages/dbt/main.py", line 215, in run_from_task
    result = task.run()
  File "/usr/local/Cellar/dbt/0.12.2/libexec/lib/python3.7/site-packages/dbt/task/seed.py", line 20, in run
    self.show_tables(results)
  File "/usr/local/Cellar/dbt/0.12.2/libexec/lib/python3.7/site-packages/dbt/task/seed.py", line 42, in show_tables
    self.show_table(result)
  File "/usr/local/Cellar/dbt/0.12.2/libexec/lib/python3.7/site-packages/dbt/task/seed.py", line 26, in show_table
    table = result.node['agate_table']
  File "/usr/local/Cellar/dbt/0.12.2/libexec/lib/python3.7/site-packages/dbt/api/object.py", line 93, in __getitem__
    return self._contents[key]
KeyError: 'agate_table'

System information
The output of dbt --version:
installed version: 0.12.2
   latest version: 0.12.2

Up to date!

The operating system you're running on:
macOS 10.13
The python version you're using (probably the output of python --version)
❯ python --version
Python 3.6.4

Steps to reproduce
I have added a csv file and tried to load it into Snowflake using dbt seed --show command and it failed. dbt seed completes without errors. In dbt_project.yml the configuration looks like this:
data-paths: ["dbt/data"]

Thanks @pavel-popov - you're totally right - just reproduced this locally. Should be a quick fix - I'll add this in for 0.13.0!


Update request

Update request from Allan:
Sonia or Nan, when you get back can you add to essentials sections about releasing modules early (In prep for next year more than anything) and also an exclamation on copying course content that when copying Ultra-Ultra to NOT select the 'Content' second level folder as this will copy assignments too, just reinforce what you already say about copying folder/LM by folder/LM to prevent this from happening

[x] releasing modules early
[x]  an exclamation on copying course content that when copying Ultra-Ultra to NOT select the 'Content' second level folder as this will copy assignments too, just reinforce what you already say about copying folder/LM by folder/LM to prevent this from happening

These had been updated by Sonia


integration: enable client debug logging on CLIENT_DEBUG

Found out gRPC master branch breaks our keepalive...
Also need debugging lines for stabilizing client balancer.

@xiang90 PTAL. Made it optional with env var CLIENT_DEBUG.

lgtm


Add support for completion on zsh with homebrew installation

Is your feature request related to a problem? Please describe.
I would like to have ZSH shell completion for options of gitlab-ci-local
Describe the solution you'd like
when I do a brew install gitlab-ci-local I get gitlab-ci-local installed with completion file installed in default shell completion folder.
Describe alternatives you've considered
Install it manually, the problem is that I would have to do it everytime for each new version.

Can you please explain, why you have to do it everytime a new version is release @remyleone

Maybe the completion mechanisms within gitlab-ci-local would change from one version to the next, having it installed automatically when the formula is installed ensure that the completion feature will stay up to date


WIP on Toolbox refactor to make view configurable

This still needs cleanup and bugfixing, but is ready for a high level
review.

This change is

Please also do a high level review of the design and API changes.

Broadly (and per offline discussion)...

Separate the Toolbox category selector / tabs from the flyout.
Make a some base classes / interfaces that defines how BlocklyController will inform the toolbox views to update the category list and update the current block list. This will allow  the particular view to be replaced.
Demonstrate different layout patterns (toolbox left fly, toolbox top always open, etc) with a small number of alternatives to the blockly_unified_layout.
Towards this, the fragments should use a small number of fragment arguments, such that the arguments declare only relationship within the assigned fragment. label rotation is okay, but flyout edge has too many implications.

Reviewed 3 of 18 files at r1.
Review status: 3 of 18 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

#486 replaces this pull request.


Are PDF's or MP4's retrieved from wordpress media items?

Hi guys,
All my jpegs and pngs etc are downloaded using Gatsby source wordpress experimental but I also want to pull mp4 videos and PDF files from the media in Wordpress.
I'm sure this was working when I used the Rest API version, but I can't locate them anywhere using this version.
Am I missing something?
Thanks,
Jamie

I also have this problem.
Images are fetched fine from WPGraphql using the WpMediaItem type. PDFs however, are missing some important fields. For me its the sourceUrl that is the biggest issue right now.

Do either of you have some code I can see or more specific logs?
Some possibilities:

non image items in WordPress don't have sourceUrl the use mediaItemUrl if memory serves (images also have meduaItemUrl so it's probably better to use that).
I believe images are only downloaded into Gatsby if they are referenced by something in WP. meaning they're in a post/page, linked in a menu, etc. If it's just free floating in the media library it's not accessible for now from Gatsby.

Sure! Here are som additional information about my case.
I am creating pages for my PDF files so my initial query that is used in gatsby-node is the following:
{
        allWpMediaItem(filter: {mimeType: {regex: "/(pdf)/"}}) {
            nodes {
                id
                slug
                mimeType
                type: nodeType
                status
            }
        }
    }

On each specific PDF page I am using the following fragment query:
fragment singleWpPDFFragment on WpMediaItem {
    id
    slug
    sourceUrl
    status
    localFile {
      prettySize
      name
      ext
      publicURL
    }
  }

The error I get right now does not seem to be connected to the mediaItem type. Ill get back to you with more information when I get the time to debug and test. Should be in a couple of hours.
Im gonna try your first suggestion @moonmeister!
This is a huge issue for my project that is highly reliant on having PDFs as their own pages 😬
I will post an update shortly 😄

Sure! Here are som additional information about my case.
I am creating pages for my PDF files so my initial query that is used in gatsby-node is the following:
{
        allWpMediaItem(filter: {mimeType: {regex: "/(pdf)/"}}) {
            nodes {
                id
                slug
                mimeType
                type: nodeType
                status
            }
        }
    }

On each specific PDF page I am using the following fragment query:
fragment singleWpPDFFragment on WpMediaItem {
    id
    slug
    sourceUrl
    status
    localFile {
      prettySize
      name
      ext
      publicURL
    }
  }

The error I get right now does not seem to be connected to the mediaItem type. Ill get back to you with more information when I get the time to debug and test. Should be in a couple of hours.
Im gonna try your first suggestion @moonmeister!
This is a huge issue for my project that is highly reliant on having PDFs as their own pages 😬
I will post an update shortly 😄

This was the issue I had Phil, I tried a whole manner of different ways to test if the PDF's were indeed included in the allWpMediaItem, but came up sort every time, I just could not find them in graphql at all.
The only way I could resolve temporarily was to pull down manually the pdf's from wordpress, and then filter the post content to serve files the local gatsby source file system if a name matched. This has helped me use local pdf's for now, but it only works if they match a file name in the local system, so obviously isn't future proof for additional pdf's uploaded.
Therefore, I'd love to hear if you do find a solution to this!

I am using a combination of gatsby-source-wordpress-experimental and and the plugin called gatsby-source-filesystem. This worked perfectly in V3 but now when I have tried to port my project to V4 the issue occurred. The PDF page uses this query:
  query($id: String!) {
    wpMediaItem(id: { eq: $id }) {
      ...singleWpPDFFragment
    }
  }

The fragment used in this query can be found in my previous comment. This is the error I get when trying to render my PDF page for a pdf called sample:

From this error it looks like the field mediaItemUrl does not exist on the media item that is of the mimetype: "mimeType": "application/pdf".
It works fine on develop but something is wrong when using SSR I guess (when using develop)? 🤔
Any ideas @moonmeister

2\. If it's just free floating in the media library it's not accessible for now from Gatsby

will this stay that way or is it likely to change?
related to this: how would a dev have to craft a new/custom gutenberg block in order to ensure the images that were added with that block get recognized?

@nerdess I'm working on shipping support for files linked to in html fields right now. I'm 99% of the way there.
As far as free floating media items that aren't referenced anywhere in a connection field or in html fields, a plugin option will need to be added to enable that. For now media items need to be attached directly to a field (as in an ACF file field) or within html (an anchor tag to download a file or a video).
Gutenberg isn't currently supported directly until WPGraphQL adds core support. If you use Gutenberg via the post content field, any images added there will become Gatsby images, any files linked there will soon become static Gatsby files.

Support for this was added in<EMAIL_ADDRESS>A new plugin option options.html.createStaticFiles was added. When this is true (it's true by default), any url's which are wrapped in "", '', or () and which contain /wp-content/uploads will be transformed into static files and the url's will be rewritten. This adds support for , , and tags which point at WP media item uploads as well as inline-html css like background-image: url(). It will also transform any plain text like "https://yoursite.com/wp-content/uploads/image.png" as long as it's wrapped in "", '', or ().


Check for empty document in the finding flyout

Description
If the document for a finding is not found, it crashes the app since JSON parser throws an exception. Adding check to fix the issue
Issues Resolved
#839
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

can we add tests?

can we add tests?

Done


Mixed line endings error in OD

Consider the following .dme in CRLF
// Hand crafted DME, will not work if saved with DreamMaker

// BEGIN_INTERNALS
// END_INTERNALS

// BEGIN_FILE_DIR
#define FILE_DIR .
// END_FILE_DIR

// BEGIN_PREFERENCES
// END_PREFERENCES

// BEGIN_INCLUDE
#include "Config.dm"
#include "../test_prelude.dm"
#include "Test.dm"
// END_INCLUDE

Adding the following two lines (13 and 17) breaks OD (Notice no \r)

This works fine in BYOND.

See my comment in linked PR the issue was lines like asdf\r\r\n


Auth issues - call to /tokenreviews fails

Environment:
AKS (K8s version 1.12.6)
With ingress (Nginx):
Login page is loaded (GET) but any POST fails because endpoint returns 404.
Error message: Error occured attempting to login.
Instead of contacting API, request is routed back to web.

Request URL: http://localhost:4654/apis/authentication.k8s.io/v1/tokenreviews
Request Method: POST
Status Code: 404 Not Found

Thanks for reporting the issue. A couple quick questions to help me track this down...

Are you logging in with a service token or do you have OIDC setup?
Using port forwarding, could you try doing a get on http://localhost:4654/openapi/v2 and sending me the response JSON (it'll be quite large).
Depending on the results of #2, I think I have a quick/easy fix. If so, would you be able to test an updated build? It would simply involve modifying the image in your k8dash deployment yaml to point at a different label (i can send you an example if you need).

Thanks for helping me track this down :)

service token, thus your log line OIDC_URL:  None is correct
unfortunately response is quite short 😳

default backend - 404

sure. I'm 100% ready to test whatever you need. I'm quite curious since I'm not a big fan of default dashboard. I was thinking about writing my own but you may save me a lots of work and become my hero 😁

Thanks @frohikey. I pushed an update to the herbrandson/k8dash:dev label. This includes two things

A slight change to the way tokens are validated
Some additional server logging at startup to verify which API's are available for your cluster

My suspicion is that number 1 won't solve the issue, but that number 2 will point us in the right direction. Let me know when you've had a chance to check it out.
Thanks!

Here comes my report using image herbrandson/k8dash:dev
Client side:
Request URL: https://xxx.tld/apis/authorization.k8s.io/v1/selfsubjectaccessreviews
Request Method: POST
Status Code: 404

Logs:
OIDC_URL:  None
[HPM] Proxy created: /  ->  https://---.hcp.westeurope.azmk8s.io:443
Server started
Version Info:  {
    "major": "1",
    "minor": "12",
    "gitVersion": "v1.12.6",
    "gitCommit": "ab91afd7062d4240e95e51ac00a18bd58fddd365",
    "gitTreeState": "clean",
    "buildDate": "2019-02-26T12:49:28Z",
    "goVersion": "go1.10.8",
    "compiler": "gc",
    "platform": "linux/amd64"
}
Available APIs: [
    "admission.certmanager.k8s.io/v1beta1",
    "admissionregistration.k8s.io/v1beta1",
    "apiextensions.k8s.io/v1beta1",
    "apiregistration.k8s.io/v1",
    "apps/v1",
    "authentication.k8s.io/v1",
    "authorization.k8s.io/v1",
    "autoscaling/v1",
    "batch/v1",
    "certificates.k8s.io/v1beta1",
    "certmanager.k8s.io/v1alpha1",
    "coordination.k8s.io/v1beta1",
    "events.k8s.io/v1beta1",
    "extensions/v1beta1",
    "metrics.k8s.io/v1beta1",
    "monitoring.coreos.com/v1",
    "networking.k8s.io/v1",
    "policy/v1beta1",
    "rbac.authorization.k8s.io/v1",
    "scheduling.k8s.io/v1beta1",
    "storage.k8s.io/v1"
]
...
GET /oidc
...
POST /apis/authorization.k8s.io/v1/selfsubjectaccessreviews

Thanks for the info. Really sorry you're still having this issue. I'm not sure why you'd be getting a 404 on that call. The logs clearly show that the api exists. I've posted some questions about it and will let you know when I know more. Thanks for your patience.

@frohikey I've been working with a couple people from the k8s team and the general consensus is that this is happening because the provided token is failing to authenticate. Now, why that's returning a 404 seems strange. I hate to ask, but would you mind double checking that the token you're providing is valid?

I'm 100% positive. I decided to test API call directly. Here's token:
Name:         k8dash-sa-token-nlx2m
Namespace:    default
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: k8dash-sa
              kubernetes.io/service-account.uid: 941a7698-5776-11e9-9f0e-b2722922aabd

Type:  kubernetes.io/service-account-token

Data
====
ca.crt:     1716 bytes
namespace:  7 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9...

Client side request:
Request URL: https://mydomain/apis/authorization.k8s.io/v1/selfsubjectaccessreviews
Request Method: POST
Status Code: 404
...
authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9...

JS log:
log.js:11 10:06:23 AM Login Failed Error: Api request error:
    at apiProxy.js:50
    at x (runtime.js:62)
    at Generator._invoke (runtime.js:288)
    at Generator.e.(/anonymous function) [as next] (https://dash.goto10.cz/static/js/2.00060ec4.chunk.js:1:583991)
    at r (asyncToGenerator.js:3)
    at a (asyncToGenerator.js:25)

Testing REST API call in Insomnia:

It works great with the same token.
I may have some free time this weekend I will try to make a fork. I think there's a bad endpoint for API calling used and since there's no exact logging what's called in request() function, logs didn't help much at this point.

Thanks for the info. I'm also hoping to have some time to investigate this weekend. Feel free to hit me up in the Kubernetes slack channel if you have any questions. My username is "Eric Herbrandson"

I know why I'm not a big fan of proxies.
I fixed it by adding changeOrigin: true for proxy in the server.
Thus now it looks like this:
const proxySettings = {target, agent, secure: false, ws: true, changeOrigin: true, onError};
It works for me perfectly. Of course question is... how it runs in other environments.
When port-forwarded it still fails. Could you test it with this option?
tldr: But I finally logged in and found other bugs inside 😊

Thanks for tracking that down. I'll test with the changeOrigin: true setting.
Let me know what other bugs you find. I'll take a look asap.

@frohikey I've tested the changeOrigin: true setting and it doesn't seem to cause any issues for any of my clusters. I am really curious what could be different between our environments that makes this necessary for you but not for me (or others). Crazy.
Anyhow, thanks a TON for your help in tracking this down. When you've got a second, would you mind grabbing the latest herbrandson/k8dash:dev docker image and verifying that it resolves the issue for you?
Thanks

Hello,
Just try the :dev tag and I got the same issue : Error occured attempting to login when using token to log ( token is working fine )
Logs are :
GET /static/js/main.74ddf54b.chunk.js 304
GET /oidc 304
GET / 200
[HPM] POST /apis/authorization.k8s.io/v1/selfsubjectaccessreviews -> https://<IP_ADDRESS>:443
POST /apis/authorization.k8s.io/v1/selfsubjectaccessreviews 201
Any  idea of what I can test ?

@herbrandson The latest dev image works great.
Well, I got 3 thumbs up with the issue so I was probably not alone 😁 I guess if it runs with ingress w/ controller there's one "extra hop" and original source is being lost. This option just forces using "x-http-headers" to keep it routed properly.
@adi90x It's probably another issue. You logs looks fine. It'd follow with redirect to root /. Post request to API returned 201 so the token entered was ok. Any errors in JS console in browser?

@frohikey  my bad I think my account service was not setup properly.

@frohikey Yeah, totally didn't to mean to imply that there wasn't a real issue there. Re-reading my last comment, it does come off as defensive. Sorry about that. That wasn't my intent. Thanks so much for your help tracking this down. I really appreciate the effort you put in!
@adi90x Sounds like you've got your issue resolved?
I think everything is resolved on this ticket at this point. I'll close it if I don't hear anything in the next day or two.

@herbrandson No problem. That idea didn't even pop in my mind. And moreover I am no snowflake 😋 I know that hell trying to fix some issues when you can't reproduce it in your own env.  So I was happy to resolve it.
Keep up the good work!


Reference Maven Publish plugin docs by Android.

I think it would be nice to point fellow users to the Maven Publish plugin documentation provided by Android.

Coverage remained the same at 73.404% when pulling aa8acd3598e423f48cf7a52e31f2ee2b2e0c068b on johnjohndoe:patch-1 into 64c833a270c12b859d2c2d99b86180c3677d0830 on wupdigital:master.


MAINT: clearer error messages for refguide check.

As suggested here https://github.com/scipy/scipy/pull/6763#issuecomment-258679685

LGTM after addressing @ev-br's comments

all fixed

Merging, thanks Ralf


Temperature reading stops working after a while

First of all, thank you for this plugin. Great work.
Describe The Bug:
I have installed the plugin a couple of days ago and I noticed a few inconsistencies so I will try to explain them. First of all, I realized that the temperatures measured by my thermostats are not reflected in Apple’s Home app. Setting the temperature from there works, but the current temperatures are the ones when I start my Homebridge server and do not move afterwards. But I can access the actual temperatures from other apps (I have tried with Eve and Controller apps).
After a while, I do not know if something triggers it or not, even Eve and Controller apps stopped updating the current temperatures. Setting a new temperature still works though.
To Reproduce:
Sadly I am not sure at this point. I will try to observe if there is a particular event that put it in this state. It just occurs after a while. If I restart the homebridge server, all temperatures are correct again. I will try to make more tests and I will report anything I can find.
Expected behavior:
It should always work, obviously.
Logs:
The only weird thing I see in the logs is the following error:
“Disconnect due to red disconnection” (written in red in the logs). It is always followed by “Websocket connected” right after (in the same second, or 1 or 2 seconds after at the most).
Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.

Environment:

Plugin Version: v0.2.1
Homebridge Version: v1.3.9
Node.js Version: v16.13.1
NPM Version: v6.14.11
Operating System: Synology DSM 7

I have enabled debug mode to see if I had more information. Here what I have at the first “red disconnection” occurrence:
[1/14/2022, 10:57:39 AM] [AirzoneCloud] Disconnect: "transport close"
[1/14/2022, 10:57:39 AM] [AirzoneCloud] Disconnect due to red disconnection
[1/14/2022, 10:57:41 AM] [AirzoneCloud] Websocket connected
[1/14/2022, 10:57:41 AM] [AirzoneCloud] [Websocket] ⬆ ["clear_listeners"]

Hello, please check it on v0.2.2

Hello. I have upgraded. It works! Awesome. Thank you for your reactivity.
In the native HomeKit app all temperatures are rounded to 0.5 (probably not your fault) but in 3rd-party apps the accurate temperatures are visible and are updated. So your fix did the job. Thank you.

Thanks for the update and yes homekit requires round temperatures.


On step timeout neither the onError hook nor the step retries work

When step times out, onError hook nor the step retries work. The time is happening because of selenium not able to find the element. Below is the error captured, but we want to capture screenshots and also do a step retry
Error: function timed out, ensure the promise resolves within 90000 milliseconds
    at Timeout._onTimeout (/build/node_modules/wdio-cucumber-framework/node_modules/cucumber/src/user_code_runner.js:61:18)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

Did you find a way to workaround this problem? I would like to retry a scenario, or even a feature file, if such a timeout happens.

Hi, workaround for this problem is pretty easy - make cucumberOpts.timeout greater than any wait\sleep timeouts in your tests - it will help to avoid cucumber timeouts and retries will work.


add regex search for subscriptions

aos-ci-test

Hello - I am wondering if this PR still has utility...  Thanks!


Problems with January AWS CLI Components

Unsatisfied in EL7:

aws-cfn-bootstrap — wants python-pystache (EL7 has pystache - fix spec file?)
aws-cli-plugin-cloudwatch-logs — wants python-dateutil >= 2.1 (may not be satisfiable)
awslogs — wants aws-cli-plugin-cloudwatch-logs (may not be satisfiable)
aws-vpc-nat — wants upstart  (may not be satisfiable)

Commit 619baf3439e9a75a2c99353a70407c49d26cf0fe fixes the problem with aws-cfn-bootstrap's dependency-declaration.

Compatibility issues are not resolveable:

Adding skip-logic for aws-cli-plugin-cloudwatch-logs, awslogs  and aws-vpc-nat RPMs to the EL7 template.
Adding skip-logic for aws-cli-plugin-cloudwatch-logs, awslogs  and aws-scripts-ses RPMs to the EL6 template.

Closing with commit 5c2f03e372fbc6a12865a43e24f7ebd3798261d0


Consolidate style attributes in JS files into LESS files

There were multiple methods of defining styles used in the application.
This PR continues the work started in PR #71 of consolidating all of the various styles into Ant Design's LESS mechanism, doing so for the style attributes within individual JS files.


ffmpeg: fix an occasional crash during seek operation

During seek operation, the video and audio queues can sometimes get out
of sync (one is almost empty, the other has no space). This triggers the
low level check, which would crash because of assert in such cases.
This fix will only attempt to fill the queues if both audio and video
queues have enough space. It might cause a short video/audio stutter in
cases where it'd previously crash.
The bug above would frequently appear when using player.loop = True with
ffmpeg source.

Just in case someone else has a better understanding of what's going on, here's the traceback:
Traceback (most recent call last):
  File "./play.py", line 134, in <module>
    main()
  File "./play.py", line 130, in main
    pyglet.app.run()
  File "/usr/lib/python3.7/site-packages/pyglet/app/__init__.py", line 144, in run
    event_loop.run()
  File "/usr/lib/python3.7/site-packages/pyglet/app/base.py", line 175, in run
    self._run()
  File "/usr/lib/python3.7/site-packages/pyglet/app/base.py", line 187, in _run
    timeout = self.idle()
  File "/usr/lib/python3.7/site-packages/pyglet/app/base.py", line 308, in idle
    redraw_all = self.clock.call_scheduled_functions(dt)
  File "/usr/lib/python3.7/site-packages/pyglet/clock.py", line 333, in call_scheduled_functions
    item.func(now - item.last_ts, *item.args, **item.kwargs)
  File "/usr/lib/python3.7/site-packages/pyglet/media/drivers/openal/adaptation.py", line 231, in _check_refill
    self.refill(write_size)
  File "/usr/lib/python3.7/site-packages/pyglet/media/drivers/openal/adaptation.py", line 289, in refill
    audio_data = self._get_audiodata()
  File "/usr/lib/python3.7/site-packages/pyglet/media/drivers/openal/adaptation.py", line 310, in _get_audiodata
    self._get_new_audiodata()
  File "/usr/lib/python3.7/site-packages/pyglet/media/drivers/openal/adaptation.py", line 317, in _get_new_audiodata
    self._audiodata_buffer= self.source.get_audio_data(self.ideal_buffer_size, compensation_time)
  File "/usr/lib/python3.7/site-packages/pyglet/media/codecs/ffmpeg.py", line 742, in get_audio_data
    audio_packet = self._get_audio_packet()
  File "/usr/lib/python3.7/site-packages/pyglet/media/codecs/ffmpeg.py", line 654, in _get_audio_packet
    low_lvl = self._check_low_level()
  File "/usr/lib/python3.7/site-packages/pyglet/media/codecs/ffmpeg.py", line 704, in _check_low_level
    assert len(self.videoq) < self._max_len_videoq
AssertionError

Thank you for the pull request. This looks more reasonable.

@benmoran56 Could you please backport this to 1.4 as well?

Thanks for mentioning that @tomaskrizek. I've backported it, and it will be in the upcoming point release.
If anyone reading this wants to update via pip immediately, you can use the following command:
pip install --upgrade --user<EMAIL_ADDRESS>

Great, thanks!


refactor: standardize indentation for e2e test scripts

Description
We have some e2e test scripts that use 4-space indentation, and others that have 2-space indentation.  Within some e2e test script files, we have some tests that use 4-space indentation and others that use 2-space indentation.
This PR changes all e2e test scripts to use 2-space indentation, for consistency and not having to wonder what to use when adding a new test.
How Has This Been Tested?
CI will cover it

I'm down with the consistency, but is there any way we could enforce this rule going forward with linting?

How do you format these bats scripts?
I just tried shfmt which doesn't work.

I'm down with the consistency, but is there any way we could enforce this rule going forward with linting?

We could with super-linter if shfmt worked here, but it doesn't.  (And see draft PR https://github.com/dfinity/sdk/pull/3293 to add super-linter)
$ shfmt -i 2 e2e/tests-dfx/assetscanister.bash
e2e/tests-dfx/assetscanister.bash:57:1: "}" can only be used to close a block

It would be nice, but it's beyond the scope of this PR to add CI enforcement.

Found a possible solution:
https://github.com/bats-core/bats-core/blob/f7defb94362f2053a3e73d13086a167448ea9133/docs/source/writing-tests.md#comment-syntax
bats has valid bash alternative syntax. Should we consider using it?

Found a possible solution: https://github.com/bats-core/bats-core/blob/f7defb94362f2053a3e73d13086a167448ea9133/docs/source/writing-tests.md#comment-syntax
bats has valid bash alternative syntax. Should we consider using it?

Sure, but not as part of this PR.


static check resolved

Signed-off-by: gunjanmimo<EMAIL_ADDRESS>

@girishranganathan @leecalcote sir, All the errors are gone.  😃😃

Like when we call
defer yamlDecoder.Close()

For example in https://github.com/layer5io/meshery-istio/blob/master/istio/istio.go#L754
We are using yamlDecoder.Close(), that may result in an error, you can resolve these error checks using this guide:-
https://blog.learngoprogramming.com/5-gotchas-of-defer-in-go-golang-part-iii-36a1ab3d6ef1

@gunjanmimo Ping when you've had a chance to revisit here. 👍

@leecacote , I guess this issue got resolved in #65

@nveenjain Oh, ok. I'll go ahead and close this issue.


add further architecture support

BSD uses amd64 for x86_64
add a helpful error message for future architectures

Finished in 59.5 seconds
282 tests, 2 zigtests, 0 failures

thanks for the pr!


ci: Update the access token in ci script.

Update the integration-tests-command workflow to use PAT.
Fixes #16025

/ok-to-test sha=3990162


Bump dependencies again

We no longer depend on old versions of syn et al, which should reduce
our compile-times substantially.

@tomaka Polkadot won’t build unless I replace BitVec with something else.


How can PhantomJS JavaScript issues best be debugged?

I'm trying to test a part of my site with the phantomjs driver that requires JavaScript, and I can't see any evidence that JavaScript is being run at all. I've modified my code so that an alert box is opened on a jQuery document.ready(), and then taken a screenshot programmatically. The screenshot creates fine, the page looks OK, but there is no alert box.
I'm looking at very basic Phantom logs and am not seeing anything of interest:
port 4725
Recieved command  POST /url http://localhost:8090/auth?provider=test
  Executing command  POST /url http://localhost:8090/auth?provider=test
http://localhost:8090/auth?provider=test success
Recieved command  POST /elements .//descendant-or-self::*[@id = 'auth-status']
  Executing command  POST /elements .//descendant-or-self::*[@id = 'auth-status']
Recieved command  GET /element/0/text
  Executing command  GET /element/0/text
Recieved command  POST /url http://localhost:8090/report/new
  Executing command  POST /url http://localhost:8090/report/new
http://localhost:8090/report/new success
Recieved command  POST /screenshot /home/jon/Development/Personal/Awooga/webapp/screen.png
  Executing command  POST /screenshot /home/jon/Development/Personal/Awooga/webapp/screen.png
Recieved command  POST /url http://localhost:8090/report/new
  Executing command  POST /url http://localhost:8090/report/new
http://localhost:8090/report/new success
Recieved command  POST /elements .//*[((self::input and @type = 'submit') or self::button) and (contains(@title, 'Save') or @id = 'Save' or contains(normalize-space(), 'Save') or descendant::img[contains(@alt, 'Save')] or contains(@value, 'Save') or @name = 'Save')]
  Executing command  POST /elements .//*[((self::input and @type = 'submit') or self::button) and (contains(@title, 'Save') or @id = 'Save' or contains(normalize-space(), 'Save') or descendant::img[contains(@alt, 'Save')] or contains(@value, 'Save') or @name = 'Save')]
Recieved command  POST /element/0/click undefined
  Executing command  POST /element/0/click undefined

I've tried opening the alert() outside of jQuery, and that makes no difference.
I've also checked to see if there are any JS issues after the initial opening, thus:
	print_r($this->driver()->javascript_messages());
	print_r($this->driver()->javascript_errors());

However I get an empty array in each case.
Next thing to try, assuming PhantomJs is run in 'GhostDriver' mode, is to see if a custom --webdriver-loglevel setting can be provided. Turning this up to 'DEBUG' might yield something. I don't think it runs in GhostDriver mode.
I tried adding --debug to the PhantomJS command, it does add a lot of extra lines to the debug output, but nothing obviously of relevance.
I've used this:
	print_r($this->driver()->connection()->get('settings'));

to confirm JavaScript is enabled:
Array
(
    [XSSAuditingEnabled] =>
    [javascriptCanCloseWindows] => 1
    [javascriptCanOpenWindows] => 1
    [javascriptEnabled] => 1
    [loadImages] => 1
    [localToRemoteUrlAccessEnabled] =>
    [userAgent] => Mozilla/5.0 (Unknown; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) PhantomJS/1.9.7 Safari/534.34
    [webSecurityEnabled] => 1
)

So it ought to be working!
If you have any other suggestions, I'd appreciate them.

@halfer As far as I know alert() and confirm() dialogs do not work in PhantomJS.

Aha, thanks, that will save me a wild goose chase! I will try another simple test. This may be just an environment thing I'm missing, will update.

The problem was on my side - an incorrect selector resulting from an incorrect understanding of nth-child compounded by a bug causing something not to show in Webkit. The screenshot feature of Phantom was great in helping to track it down.


[FEATURE/DISCUSSION] Start working on "userlog" feature for admins

Is your feature request related to a problem? Please describe.
Currently moderation on the discord server doesn't provide any way to make "notes" or save references about a user's behavior.
Describe the solution you'd like
Add a new userlog command based off the following examples:
fCC userlog @bradtaniguchi User was suspended for advertising (bot saves link to this message)
fCC userlog @bradtaniguchi User was suspended again, this time for disruptive behavior (bot saves link to this message)

so:
fCC userlog <user> <...rich text message>

This will require updates to the database to save the userId mentioned, and their current username, along with other meta data. (we can talk about the database schema) Any discord links should be saved as-is to be displayed later
Describe alternatives you've considered
We could add another command that can be used to "read" this information later, or use the same command without the third argument. Regardless of how the "read" is called, it should show these logs, previous suspensions and their username (as these can be changed)
Additional context
This feature will require the usage of the mongodb database, and probably some database updates overall so user's are changed.

So here's what I'm thinking:
If we are using the user mention to call the command, we can store just the ID in the database (as my ID doesn't change even if I change my username). Then as a second field we can have a string[] to hold the reasons, and return them if the lookup command is called.
Alternatively, we could have an array of objects (to track the reason and the date).

I'm trying to think if we should normalize user's into its own collection, or don't do :thinking:
Since both suspend + userlog commands will reference userIds. Both could end up updating the user-names in the DB when the user changes their username to further keep a log of those changes over time.
I can think of the following schemas with the following properties:

user

userId - could be used instead of the mongoId?
currentUserName - could be an array of previous names? Saved on the document with a date?

suspensions

userId - the user affected
reason
date
modId - the id of the mod who reported it (we can also save the mods username at the time here aswell)
status - either suspended, or "removed" or similar? This way we can know who is suspended/unsuspended over time. Could also be used to "re-consider" a user who has been suspended for a long period of time, if we close the room maybe?

logs

userId - the user affected

modId - the id of the mod who reported it (also username maybe?)

date

Any thoughts on this setup?

This one won't be "completed" by the merge of #157 right?

This one won't be "completed" by the merge of #157 right?

No, #157 was only part of the changes. This issue will need to leverage the changes to the schema and database

not going to do this due to #202 .


Non declared dependencies throwing errors in Yarn v2 (berry)

🐛 Bug Report
Attempting to use Docusaurus v2 with Yarn v2 (berry).
As soon as i run yarn build the build explodes with dependency errors from yarn v2.
Lots of peer dependencies aren't specified and yarn v2 doesn't know what to do.
Example error
Error: @docusaurus/core tried to access @docusaurus/plugin-content-blog, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

Interesting that this doesn't happen in yarn v1, but it seems to be due to no dependencies/peer dependencies being specified for the various docusaurus packages.
Steps to reproduce

Install/have yarn v2 as the package manager for project
Install docusaurus v2
run yarn build.

I've tried to install every dependency yarn says it can't find, but it's an endless process, and i still haven't managed to get a build to work.
Basically, right now, docusaurus v2 is not compatible with yarn v2 😢

This is a little tricky. Docusaurus v2 runs on a plugin system, so @docusaurus/core should not even know about the existence of @docusaurus/plugin-content-blog and should not declare plugin-specific stuff as its peer dependencies.
Right now Docusaurus relies on @docusaurus/theme-classic's dependencies (including @docusaurus/plugin-content-blog) to be hoisted to the root of node_modules. This assumption is usually true, so right now things just happen to work. To be really strict, users might need to declare dependencies on things like @docusaurus/plugin-content-blog explicitly to make it work with Yarn v2.

Me too, I try out everything but it's still hopless. Even I try to change pnpMode to loose. :(

I'm running into a sim issue with @vue/cli due to its plugin system. Yarn docs invite us to ping @arcanis so they can track these issues..

I made an example to show how you can use some hacks to make docusaurus v2 work with pnp: https://github.com/SamChou19815/docusaurus-yarn-v2-example
I'm trying to add some fixes upstream.

The latest release would fix most of the problems. However, you still need pnpMode: loose. See https://github.com/SamChou19815/docusaurus-yarn-v2-example for latest instructions.

It's possible to use yarn without enabling loose mode if you add the Webpack PNP plugin and patch a few of the missing dependencies. The PNP plugin won't be required with webpack5
https://github.com/jgeschwendt/repro-docusaurus-yarn2/commits/patch

@jgeschwendt PNP plugin is already added: https://github.com/facebook/docusaurus/pull/2796
We still need pnp loose because theme-classic has a bunch of dependencies that doesn't properly dependencies, and it will inject import '@mdx-js/react' on user's behalf for docs page.

Awesome, didn't know that, I pushed up a new commit removing the plugin. Is there something wrong with resolving those extra dependencies in the .yarnrc.yml file? It seems like the alpha.56 release fixed a lot of the extension I had to help along.
packageExtensions:
  "@docusaurus/preset-classic@*":
    dependencies:
      "@docusaurus/utils": ^2.0.0-alpha.56
  "@docusaurus/mdx-loader@*":
    dependencies:
      react: "*"
  "@docusaurus/theme-classic@*":
    dependencies:
      core-js: "*"

yarnPath: .yarn/releases/yarn-2.0.0-rc.33.js

I just tried to use Docusaurus for one of my projects so I investigated a bit. I think there are two things at play. The first is the following error:
Error: @docusaurus/core tried to access @docusaurus/preset-classic, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

Required package: @docusaurus/preset-classic (via "@docusaurus/preset-classic")
Required by: @docusaurus/core

This is because @docusaurus/core calls importFresh (here) in order to load the plugin. This third-party in turns calls resolveFrom based on a flawed heuristic, but essentially it's the equivalent of require.resolve with no paths option. As a result, the resolution is done against the dependencies declared by @docusaurus/core, not the top-level package, and the error is correct (Docusaurus is at risk of problems caused by incorrect hoisting, regardless of the package manager).
To fix that, simply process presetModuleImport as such:
const resolvedModuleImport = createRequire(context.siteDir).resolve(presetModuleImport);
const presetModule: any = importFresh(resolvedModuleImport);

This will ensure that the preset is resolved against the dependencies declared by the site directory, which is likely what you intend to do. Note that this doesn't use any non-standard API - createRequire is standard since Node 12, and polyfills exist before that.
A second problem (but really, not that much of a problem if it works for you) is that @docusaurus/core is defined as a regular dependency of the plugins (rather than a peer dependency). In general this can be source of troubles since you can't ensure that you'll get the exact same version in every plugin. Perhaps that's something you may want to look into, but that's more of an advice than anything 🙂

Thanks @arcanis, not very familiar with these problems but trying to figure this out 😅

A second problem (but really, not that much of a problem if it works for you) is that @docusaurus/core is defined as a regular dependency of the plugins (rather than a peer dependency). In general this can be source of troubles since you can't ensure that you'll get the exact same version in every plugin. Perhaps that's something you may want to look into, but that's more of an advice than anything 🙂

Due to issues in the past, we actually have a runtime check to ensure all versions are the same, as using different versions often lead to unexpected failures.

We are going to release very soon, let me know tomorrow afternoon if you still have issues with latest version, or if we can close this issue

@arcanis fix released in 2.0.0-alpha.69

closing, assuming it's fixed, but let me know if it's not

@slorber this is an old issue but I just came across it.

Error: @docusaurus/core tried to access @docusaurus/mdx-loader, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
Required package: @docusaurus/mdx-loader

Agree @arrowplum , going to re-open
We now have CI tests for Yarn 1 + Yarn 3 (node+pnp linkers) in lose mode but the non-lose mode doesn't work due to some deps graph issues.
Last time I investigated we had some kind of cyclic dependency that will likely need to create a new Docusaurus package

I was having some issues with this in my testing of migrating to Yarn v3. It's been a little tricky, and I ran out of time to debug the issues. If I get some more time, I'll report back with any thoughts on it.
If you have a second to dig into this, it would be much appreciated! Thank you :pray:


Old graceful-fs version in gulp 3.x

Opening this as a separate issue, as #1571 got comments closed (and describes a slightly different issue), and my comment in #1604 got moderated without a notice.
graceful-fs below version 4.0 (well, technically only 2.x and 3.x) is going to break on Node.js 7.x (which is going to happen in about 5 months from now).
If you are sure that everything is covered and understood correctly — just close this, please :-) (and excuse me for opening a new issue), I am just making sure that nothing is missed here.
Your assessment of this issue in #1571 is not precise:

There is nothing wrong with the dependency, especially since it is only used in development. We will be updating or removing it in gulp 4 and the message will go away.

There are two warnings there — a warning on installation of graceful-fs lower than 3.x and a warning in runtime when an old graceful-fs version does unsupported stuff (which it does upon require).
I am only talking about the runtime warning here that comes from Node.js. That runtime warning is emitted only in those situations which would be turned into throws on Node.js 7.0 and above.
Now, just running gulp even  with an empty gulpfile.js file emits this runtime warning:
(node:25661) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.

which is going to turn into a throw in Node.js 7.0.
The dependency tree to graceful-fs looks like this:
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    ├─┬<EMAIL_ADDRESS>    │ └─┬<EMAIL_ADDRESS>    │   └─┬<EMAIL_ADDRESS>    │     └─┬<EMAIL_ADDRESS>    │       └──<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>
<EMAIL_ADDRESS>is not reevalating native module sources, so it doesn't trigger that warning and would not be affected by that throw in Node.js 7.0.
Only<EMAIL_ADDRESS>causes that warning here, which is required only by<EMAIL_ADDRESS>(apart from being a devDependency<EMAIL_ADDRESS>is loaded both by orchestrator (which is loaded only by gulp) and directly by gulp.
To my knowledge, there shouldn't be breaking changes in graceful-fs update between 3.x and 4.0 and that should be a clean update.
A straightforward fix for to this would be to release a vinyl-fs 0.3.x with graceful-fs@4, perhaps.

If you don't want to take this path — just close this, please :-).

Thank you for opening a new issue about this.  I understand what you are saying about an error in node 7, but gulp 4 will be out before that time which has a new version of vinyl-fs with a new version of graceful-fs.  We aren't going to upgrade to graceful-fs 4 in vinyl-fs 0.3.x because that is a breaking version number in graceful-fs and we don't want to propagate those assumptions to end users.  Vinyl-fs has had an insane amount of versions released since 0.3.x that is included with gulp 3.x and we are not focusing efforts on it.

@phated Ok, thanks! I was just making sure that nothing is misunderstood here.

@phated Would I be correct in saying that all gulp users will have to transition to v4, which means making significant gulpfile modifications, between the moment it is released and the moment Node 7 is released, otherwise they will be stuck in Node <7?
May I also ask what do you mean be "we don't want to propagate those assumptions to end users"? Are you referring to the assumption that "there shouldn't be breaking changes in graceful-fs update between 3.0 and 4.0"? Do you mean that you don't want gulp ^3 users to be automatically upgraded to graceful-fs 4 because that would be automatically propagating a potential breaking change?
Simply trying to understand. :)

@phated

but gulp 4 will be out before that time

Just to confirm — that's still the case, correct? I'm not hurrying or anything, just asking, as three months have passed and we have less than one month to land that change. So any additional data points would be useful here.

I confirmed with a member of the node foundation that node 7 will never reach LTS, so it's not really a problem. People should not be using odd releases (they are insanely buggy) and if they are comfortable with that, they should be comfortable enough using our branch. This project is worked on in everyone's spare time, so it'll take however long it takes.

@phated Thanks for the response! I had no intention in causing any pressure here, and I understand the spare time argument perfectly well, everything I do here is also done in my spare time.
I just wanted some clarifications to better plan my further actions, that's why I asked you about the plans on your side again today, as my previous info was from https://github.com/gulpjs/gulp/issues/1640#issuecomment-217247072.
Thanks! :smile:

Note: gulp could be even fixed in a way that would not affect existing vinyl-fs users, except for gulp — fork vinyl-fs@0 as vinyl-fs-0 (a separate module), fix it there, and make gulp use that module. Not sure if that makes sense, though.

@ChALkeR fwiw, I think that the scenario described in https://github.com/nodejs/node/issues/8149#issuecomment-240547322 likely exists in >0 user's gulpfles.  These are the types of unquantifiable problems we must avoid.  graceful-fs even recommends doing a major bump when changing versions.  This problem is not going to be solvable on our end.

@phated, that could be true, but I can't come up with a combination of  re-evaluating module (graceful-fs) + a monkey-patching module that would actually break in a way that is worse than they already are. Could you?
Btw, I could quickly look up the list of packages that depends on any module combinations, if you name me some.
Perhaps running the tests for various ecosystem modules with this fix could help?

For example, exactly one module depends on both gulp and mock-fs, it's http://npmjs.com/live.
I could look up all the other combinations that you suppose could explode together.

@ChALkeR looking up dependent modules doesn't help because I know companies have private 3000+ line gulpfiles.  This is why I've already stated that it's more than a gulp ecosystem problem and trickles down to consumers (people that are making gulpfiles) and cannot be quantified.  Gulp 3.x is frozen because every tiny change I've tried to make in the past has broken people so we stopped.  We cannot safely change this.

@phated if we did a call for open projects and could smoke test a non trivial number of complicated projects would that ease your concern at all?

@TheAlphaNerd somewhat, but probably not enough (especially given the amount of feedback I usually receive)

@phated we are going to discuss a number of potential solutions, including a new externally managed fs module similar to readable-stream
One thing that I would like to examine is if there is a way that we can create a smoke test environment you can use to make more informed decisions about breaking changes on the various architectures that node supports. Considering the amount of users that are relying on gulp, and that many of them are not writing node full time, I think it could be a very valuable testing tool for gulp.
Perhaps the results show that we can't do this, or perhaps we cannot get enough information. Even in that situation the tool could potentially help you to make better decisions regarding gulp 4.
Would you be interested in collaborating on this?

@TheAlphaNerd yeah, definitely.  I want to utilize the time I have to finish gulp 4 but the tool you describe is something I've wanted for a long time.

@phated, ok, another proposal, semver-minor this time.
What about adding an option to gulp@3, which should be explicitly specified when requiring gulp, and which instructs gulp@3 to use graceful-fs@4?
E.g. const gulp = require('gulp/compat');, which if and only if it's the first require of gulp (i.e. if gulp is not loaded by nested deps) would force this and all the following require('gulp') to use graceful-fs@4?
The restriction for the first only is required so that deps won't misuse it and change the behavour of everything, — this option would be available only to the top-level gulpfile itself.
Another way — add a command-line flag, but that's less ideal for some cases as it could require changes in the tooling.
This way, nothing could possibly break without top user consent, and gulp@3 will still be compatible with everything through and opt-in.
If we don't do this, then even when gulp@4 would be released, users of gulp@3 would have issues becase they would not update immediately.

@phated

@ChALkeR looking up dependent modules doesn't help because I know companies have private 3000+ line gulpfiles.

Btw, point taken. This makes the devdeps checks not needed at this point, I suppose.

POC: https://github.com/gulpjs/gulp/pull/1760


merge LocationGossipStoneHint and ItemGossipStoneHint

add more precise types for location hints to json spoiler output
fix formatting bugs caused by not treating locations without a name override correctly
unify in game appearance of item and location hints

will make a new PR to fix conflicts


Changed np.arange to np.linspace for the generation of egrid inside o…

Changed np.arange to np.linspace for the generation of egrid inside occ_dependent_alpha and generate_tas from generator.py. The np.arange can create e_grid arrays with sizes different from NEDOS.

This looks good to me @LucasGVerga!
When we merge to main with PyTASER the GitHub workflows try to make a new release, which requires the version number to be updated. Can you bump the version number to 2.1.3 in setup.py and add a sentence to the CHANGELOG.rst explaining the change (basically a summary of what you said in Slack!)? Thanks!

Hi @kavanase thanks for that!
OK. I updated the setup.py and CHANGELOG.rst. If we need, I can add more details for the change explanation.

Great, thanks!


abstract method shows wrong parameter info

Abstract methods show up like this in docs:
addPath(arg0)

Specified by: myphysicslab.lab.engine2D.Edge

Parameters
arg0...?

instead of showing the correct parameter information from the Edge interface:
addPath(context)

Add this Edge to the currently open path of the JavaScript canvas context. The Edge should be rendered in local body coordinates.

Parameters
contextCanvasRenderingContext2D
the JavaScript canvas context to draw this object into

Here is some of the code involved:
/**
* @interface
*/
myphysicslab.lab.engine2D.Edge = function() {};

/** Add this {Edge} to the currently open path of the JavaScript canvas context.
The {Edge} should be rendered in local body coordinates.
@method
@param {!CanvasRenderingContext2D} context the JavaScript canvas context to draw this
object into
*/
Edge.prototype.addPath

/**
* @param {!myphysicslab.lab.engine2D.Polygon} body
* @param {!myphysicslab.lab.engine2D.Vertex} vertex1 the previous vertex, in body
  coords; matches the next (second) vertex of the previous edge
* @param {!myphysicslab.lab.engine2D.Vertex} vertex2 the next vertex, in body coords
* @constructor
* @struct
* @implements {myphysicslab.lab.engine2D.Edge}
*/
myphysicslab.lab.engine2D.AbstractEdge = function(body, vertex1, vertex2) {
  // code omitted...
};

/** @inheritDoc */
AbstractEdge.prototype.addPath = goog.abstractMethod;

I've run into some ambiguity over when to use the documentation from a super type.  Suppose we have:
/** @constructor */
var Greeter = function() {};

/**
 * Generates a greeting.
 * @param {string} name Name of the person to greet.
 * @return {string} The greeting.
 */
Greeter.prototype.greet = goog.abstractMethod;

/**
 * @constructor
 * @extends {Greeter}
 */
var CustomGreeter = function() {};

/**
 * Generates a custom greeting.
 * @override
 */
CustomGreeter.prototype.greet = function() {};

If CustomGreeter.prototype.greet simply had /** @override */, we can easily grab the docs from the super type. But above, there is a block description. Do we

Use the block comment and inherit the documentation for the annotations. The docs will also include an "Overrides: Greeter#greet" link.
Use the block comment, but leave everything else empty with an "Overrides: Greeter#greet" link.

What if the comment overrides the documentation just for the @param:
/**
 * @param {string} name The name of a funny person.
 * @override
 */
CustomGreeter.prototype.greet = function() {};

Here, do we use the @param and inherit everything else, or just include the "Overrides..." link?

I've been assuming that I cannot modify the documentation when I'm using @inheritDoc (or @override which I guess is the same thing).  So this wouldn't be much of an issue for me.
I've noticed that I can provide a duplicate of the type information, which can have different documentation, but I assume it should have the same signature (same parameter and return types).  That's a closure-compiler question which I don't know the answer to.  Seems like the compiler should object if the types are different.
If there is a way to provide a warning when you notice this happening, that would be good enough for now I would think.

This is included in the v0.7.0 release

Confirmed this case is fixed, however see issue #35 for a similar case that is still wrong.


Fix issues with packager | Competing with PR #422

Merge with #443 #440
Type of Change

[x] Bug fix
[x] Refactoring

Description
#422 is rushed, does not include all of the packagers, and includes an incomplete fix. Merging this would fix every issue with #422 and packager
Checklist

[x] My code adheres to the coding and style guidelines of the project.
[x] I have performed a self-review of my own code.
[x] My changes generate no errors/warnings/merge conflicts.

Are you serious ?? You could have asked me to do those stuff in my PR itself !!!
Please close the new 2 competing PRs I am implementing these changes in the my PR itself

Are you serious ?? You could have asked me to make these changes in my PR itself !!!
Please close the new 2 competing PRs I am implementing these changes in the my PR itself

No thanks.

@jeevithakannan2 and do not steal my ideas, I correctly implemented where you failed, and as such maybe you should close your pr??

Then what about the PR https://github.com/ChrisTitusTech/linutil/pull/443

And you have missed many places in this PR too

And you have missed many places in this PR too

No? I implemented it correctly, also about #443 it was made because if he accepts my versions he can't merge yours or else it will conflict so thats why it was made. I can close that PR if you want the credit for that.

You'll have to close your old pull request and make a new one though.

Bruh you also didn't fully finish this PR !! Maybe you should close this one

Bruh you also didn't fully finish this PR !! Maybe you should close this one

This PR is finished maybe you should tell me where its not !!

gaming-setup was intentionally left out due to a rewrite in #380 if thats what you're referring to !!

Bruh you also didn't fully finish this PR !! Maybe you should close this one

This PR is finished maybe you should tell me where its not !!

You could have done that to me told me where I have not finished it

@jeevithakannan2 Not going to argue with you any longer; You're implementing the fix in areas where it does not need implemented. Such as Aurhelper, #382 . I have implemented the fix properly in these 3 PRs and yours is no longer needed, please close it.


returned data of oembed is limited

Maybe it is the whole idea of oembed, but the call
twitter_api.statuses.oembed(_id=item_id)

returns a limited number of keys:
{
	"_id" : ObjectId("56656ee656180c7bbb84866b"),
	"provider_url" : "https://twitter.com",
	"version" : "1.0",
	"url" : "https://twitter.com/FlikFluimsnor/statuses/670014207656620032",
	"author_name" : "FlikFluimsnor",
	"height" : null,
	"width" : 550,
	"html" : "

Opvang 100 vluchtelingen voor 10 dagen kost gemeente een ton https://t.co/jPtYBytZRA Betaald van uw onroerendezaakbelasting
— René Dercksen (@ReneDercksen) November 26, 2015
\n",
	"author_url" : "https://twitter.com/FlikFluimsnor",
	"provider_name" : "Twitter",
	"cache_age" : "3153600000",
	"type" : "rich"
}

It this the expected reponse? If so, I do I get the full twitter reponse as mentioned in the docs

Don't understand your question:

if you want all fields from the API, why do you call the oembed route instead of the "show" one which you are giving the link to? twitter_api.statuses.show(_id=item_id) seems to be what you're looking for
otherwise if you want to adjust what oembed returns, see the list of arguments of the statuses/oembed function on the related documentation here: https://dev.twitter.com/rest/reference/get/statuses/oembed

Thanks. I misunderstood oembed. I thought it was doing what show does.


4.1: fix link to old manual

fixes a link to the DAGMan section of the manual

Fair. Looks like its 8.9.2. Will update in a moment.


Fix keypad arming delay.

Currently the delay only applies to the SHM status change, it should apply to both running the chosen routine and settings the SHM status. As I had posted on the community thread, the flow should be something like: Arm Keypad -> Send "setExitDelay" command to keypad -> Wait for "delay" seconds -> Run desired routine and change SHM status.

https://github.com/ethayer/lock-manager/pull/9


Appstudio update test-custom-default-branch-vxkn

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-mqfw-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wadk-on-pull-request-
creating pipelinerun test-simple-build-wadk-on-pull-request- in namespace build-e2e-mqfw-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-mqfw-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-mqfw-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-uqzm-on-pull-request-
creating pipelinerun test-simple-build-uqzm-on-pull-request- in namespace build-e2e-mqfw-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-mqfw-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-mqfw-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-mqfw-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


Added sampler2D input support to FlxRuntimeShader

FlxRuntimeShader currently doesn't seem to have a method to set sampler2D inputs on the run-time shaders. This pr adds support for sampler2D inputs as well. It also adds a corresponding lua function to set/manipulate these inputs as well.
Usage in lua:
initLuaShader('your-shader-name')
setSpriteShader('your-sprite', 'your-shader-name')
setShaderSampler2D('your-sprite', 'my_tex_input', 'path-to-image-to-use-as-sampler2d')

In the shader:
uniform sampler2D my_tex_input;
void main()
{
    // stuff you wanna do with the texture input
}

please merge @ShadowMario

He has notifications off

damn


Feature Request: Quba-viewer as a Nextcloud files app?

Quba is a very nice/interesting tool (based on Electron) that can only be used in the local (Windows, Linux and Mac) desktop environment.
Nowadays more and more people work in the cloud.
Is it also possible to realize or transform the Quba Electron app into a web application?
My intention is then to try, with some (your? ;-) ) help, to integrate the Quba web app into a Nextcloud Files app.
Or are there plans in the near future to make a Nextcloud Files app version of the Quba viewer?

no plans , you can use the XSLTs, they are based on the  kosit xslts, if you use saxon he the command line calls to practise would be

 .\saxon.bat .\corpus\corpus-master\XML-Rechnung\CII\EN16931_AbweichenderZahlungsempf.cii.xml .\xrechnung-3.0.1-xrechnung-visualization-2023-11-15\xsl\cii-xr.xsl > xr.out

.\saxon.bat .\xr.out .\xrechnung-3.0.1-xrechnung-visualization-2023-11-15\xsl\xrechnung-html.xsl >xr.html


Open sourcing anilist

I tried asking in one of my old threads on anilist but it's hard to reach to other people there, so I'm going to ask here.
As it turns out, the last update on this is 5 months ago. I know that Uni is still a priority so won’t pester you much, but any update? A hint would be nice, are you on schedule or will there be delays?

Probably not until after APIv2 is out and stable, as I want to make sure everything has tests and documentation, a lot of stuff does at the moment but theres a fair amount of older code without them. As I'm basically rewriting everything for v2 currently I figure I may as well not bother going back to the older code and improve tests and add docs when its going to be removed soon.

I've been following #63 and there's a lot of good ideas (as well as issues), so is the progress on V2 good or are you being delayed because of problems?
One more thing, it makes sense to have a comfortable base before opening it up but I don't feel like having everything perfect or even complete (especially docs and api for example) beforehand is worth it. That's the point of open source. When anilist gets open sourced I believe the community will be a major help in patching those up, and maybe also driving how the api should look like and reporting the issues early on (it's the foundation of the site after all).

Progress with v2 is good but just a little slow with Christmas and now exams but should be getting into it full swing again in a couple weeks.
I plan on having quite a few pre-releases of v2 before its stable release so we can get feedback on it before anything is concrete.
Yeah I know what you mean but I would really rather the community work on new things that they find interesting and less so adding tests and docs, I know its something that will happen as well but if anyone wants to change code that doesn't have tests then its going to be really hard to manage those prs, and those changes will be pretty redundant with v2 replacing it all a couple months after.

I totally understand. Great work on anilist 👍
(It'd be super cool if you can maybe create a thread on anilist and keep us developers updated on the state of things from time to time so that nobody has to explicitly ask the questions)


Add missing native functions

This pull request adds some missing native CSS functions. In addition, the list of built-in module functions of Sass has been supplemented.

Very nice, thanks @jhae-de !


Used DFI bridge and was not able to complete. Please help me to refund that DFI.

I sent 1535.8504 DFI from my Kucoin wallet to the DFI bridge and DFI (BSC) were supposed to be deposited in my Metamask. The DFI were sent but nothing happened after I clicked the button to send to BSC chain. No window popped up from Metamask asking for BNB as gas. Tried the Restore method and same result - click the button and no Metamask window. It didn't go to the BSC chain wallet like before.
That DFI went to another wallet that is not mine.
Here is the TxID from my Kucoin wallet: https://defiscan.live/transactions/33fc5eae5ffb97725339a3858f0096a4b55ad7d7ed1bffec0560ba26342c5644
Here is the TxID DFI transferred to another DFI wallet, not to the BSC chain wallet: https://defiscan.live/transactions/9c7bf57ff093c2849e159274ca6800aa6da87d3f6586c920e1ab815fbf9bf850
Please help me to refund that DFI.

No worries, let’s fix this!
Can you check if you get any errors in the “development console” when you try to use the recovery function?
Sent from my iPhone
On 14 Jun 2022, at 8:27 pm, NegativeIQVN @.***> wrote:

I sent 1535.8504 DFI from my Kucoin wallet to the DFI bridge and DFI (BSC) were supposed to be deposited in my Metamask. The DFI were sent but nothing happened after I clicked the button to send to BSC chain. No window popped up from Metamask asking for BNB as gas. Tried the Restore method and same result - click the button and no Metamask window. It didn't go to the BSC chain wallet like before.
That DFI went to another wallet that is not mine.
Here is the TxID from my Kucoin wallet: https://defiscan.live/transactions/33fc5eae5ffb97725339a3858f0096a4b55ad7d7ed1bffec0560ba26342c5644
Here is the TxID DFI transferred to another DFI wallet, not to the BSC chain wallet: https://defiscan.live/transactions/9c7bf57ff093c2849e159274ca6800aa6da87d3f6586c920e1ab815fbf9bf850
Please help me to refund that DFI.
—
Reply to this email directly, view it on GitHubhttps://github.com/muirglacier/bridge-ui/issues/27, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQVPOW64FYC7AUNF4MDOBGDVPBNCRANCNFSM5YXFXPZQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

At that time no window popped up from Metamask asking for BNB as gas. So i can't claim the dfi (bep-20). Then the DFI was moved to another wallet and I couldn't recovery it.

Can you let me know your binance chain address and I will have it sorted out for you immediately.
We have identified the little bug that affects a small portion of the transactions and will have it fixed once and for all :-)

Can you let me know your binance chain address and I will have it sorted out for you immediately.
We have identified the little bug that affects a small portion of the transactions and will have it fixed once and for all :-)

My BSC chain address: 0xB3c1A0019D332DD6EE125972d40594564F877679
Thanks for your support!

https://bscscan.com/tx/0x75e750fc8863f8689916c039a8edd2b8f807ec6d9ac92469eb8b85f40ab1838d


Getting wrong .CSV file while converting .XLSX to .CSV

Hi @DaSpawn ,
For a particular file I am getting  wrong data for CSV  after converting .xlsx to .csv.  May I know the reason ,Why my module takes wrong column data for while converting the xlsx file.I have attached the .xlsx file as well as the out put .csv file in the Zip file. After debugging I have observed that at line no 10 of the excell sheet the  2nd coumn value is coming from the 3rd column value of line no 9 of excel . May I know the reason for this issue.
one.xlsx
one.zip

Sorry ..I observed the file was a corrupted file..Now its working as expected..

If I use your xlsx sheet with the example the columns are returned properly as indexed:
RowNum 10 colNum 1 rowValLen 3 rowVal '900'
RowNum 10 colNum 2 rowValLen 21 rowVal 'Tiered Royalty Band 3'
RowNum 10 colNum 4 rowValLen 6 rowVal '804100'
RowNum 10 colNum 5 rowValLen 15 rowVal 'IP Cost Sharing'
RowNum 10 colNum 6 rowValLen 0 rowVal ''
RowNum 10 colNum 12 rowValLen 3 rowVal 'TPR'
RowNum 10 colNum 13 rowValLen 24 rowVal 'MIPCS (not recorded yet)'
RowNum 10 colNum 14 rowValLen 9 rowVal 'Principal'
rows are sparse arrays, you need to be sure to use the element index and not just blindly itterate through the rows as any empty cells will not be set in the array (see https://github.com/DaSpawn/xlsx-stream-reader/blob/master/example/example1.js#L31 the colNum variable)


Disable MCR completions in airgap clouds

Once this PR is checked in, we need to disable MCR completions in airgap clouds:
https://github.com/Azure/bicep/pull/9913
See https://github.com/Azure/bicep/pull/9913#issuecomment-1449163693

Which milestone?  I assume 0.16?

Decision:  Nothing to do, we can just let the call fail.


Updates to use broccoli-merge-trees.

This switches to using broccoli-merge-trees directly instead of the deprecated this.mergeTrees. I also added broccoli-funnel.

Thanks Will! Could you add
var mergeTrees = require('mergeTrees');
var Funnel = require('broccoli-funnel');

to the top of index.js? I think that will get the tests passing.

Yep, just realised this issue. I'll fix it up now.


Include geoparquet download links as assets in collection metadata

Currently for a certain collection_id the download links of the raw and sampled geoparquet files are found at https://ewoc-rdm-api.iiasa.ac.at/collections/<collection_id>/download and https://ewoc-rdm-api.iiasa.ac.at/collections/<collection_id>/sample/download respectively.
Is it possible to include both datasets as assets in the collection metadata? This way both dataset download links can be found immediately at https://ewoc-rdm-api.iiasa.ac.at/collections/<collection_id>
Here is an example of collection metadata with assets: https://github.com/fiboa/fiboa.github.io/blob/main/stac/datasets/ukfields.json

This API already exists.  Example https://ewoc-rdm-api.iiasa.ac.at/collections/2017afoneacrefundmelpoint110/metadata/items

To be checked with @jdries if this is still needed.

@santoshkaranam If I'm correct, this is a custom API right?
The idea in the original request was to follow the STAC standard. By doing that, we could more easily work with existing tools, and integrate in openEO in a standardized manner.
Of course, WorldCereal toolbox is able to write custom code that handles this API as well if needed.

Yes, We have an issue for this tracked. STAC will be mainly to expose datasets. For uploading and for signed URLs for private dataset, we will still use this API

#16


Remove build task im ci command

What is this bug about?
When running carna ci, the build task must not be executed. The type check takes place in the analysis task.
https://github.com/kettil/carna/blob/a20d6919e3cc5f96844f16741d53c68f97e53b44/src/lib/tasks/ciTask.ts#L16
It is a breaking change.

:tada: This issue has been resolved in version 6.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


prepared for execution on bears dataset repositories

Hi @martinezmatias & @monperrus
Here, some minor bugs are fixed before running the experiment on BEARS dataset repositories.
Also, there seems to be a bug in Operation.toString() function (from gum-tree-ast-diff project) that sometimes causes NullPointerException. For the moment, I added a try & catch to skip using this function so that we can run our experiment. I will add an issue to the project later.

Hi @khaes-kth

there seems to be a bug in Operation.toString() function (from gum-tree-ast-diff project) that sometimes causes NullPointerException.

Thanks, could you create an issue on gum-tree-ast-diff  describing the problem?


I used the northern hemisphere data, and I got a slice number y that was in the southern hemisphere, and it looked like something was wrong.

gdal2tiles version:
GDAL version:
Python version:
Operating System:

Description
Describe what you were trying to get done.
Tell us what happened, what went wrong, and what you expected to happen.
What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

The northern and southern hemispheres were sliced in opposite directions.

why ,  sb can help me?

@kuaiqushangzixiba It could be an issue related to coordinate reference system of your data.
Have you tried specifiying the correct s_srs value? I mean something like gdal2tiles.generate_tiles(input_file, output_folder, s_srs="<YOUR_SRS>").
What happens when you directly use the gdal2tile.py utility script available from the GDAL project?

Closing this issue because it seems inactive. Feel free to re open if the issue still exists.


Example without Keycloak adapters

Hello, this is a great project!  I was wondering if you would be so kind to do a new blog/tutorial/sample on a Spring Boot/React solution that doesn't use the Keycloak Adapter as it is now deprecated.  See https://www.keycloak.org/2022/02/adapter-deprecation.html

Hi @ccaspanello ,
Thanks for the feedback.
This isn't currently on our TODO list. But this doesn't mean of course we won't do this in the future.
Glad you like the project!
Cheers