Cannot read property 'Symbol(Symbol.iterator)' of undefined

Running code-gen gives me this error message:
  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate src/generated/apolloComponents.tsx
      ✖ Load GraphQL schemas
        → Cannot read property 'Symbol(Symbol.iterator)' of undefined
        Load GraphQL documents
        Generate

I guess i miss a package, but which one?
This is my package.json:
  "devDependencies": {
    "@types/faker": "4.1.5",
    "@types/jest": "23.3.13",
    "@types/react": "16.7.21",
    "@types/react-dom": "16.0.11",
    "faker": "4.1.0",
    "graphql-code-generator": "^0.16.0",
    "jest": "23.6.0",
    "node-fetch": "2.3.0",
    "ts-jest": "23.10.5",
    "tslint": "5.12.1",
    "typeorm": "0.2.11",
    "typescript": "3.2.2",
    "graphql-codegen-typescript-common": "0.16.0",
    "graphql-codegen-typescript-client": "0.16.0",
    "graphql-codegen-typescript-react-apollo": "0.16.0"
  },
  "dependencies": {
    "apollo-cache-inmemory": "^1.4.2",
    "apollo-client": "^2.5.0-alpha.10",
    "apollo-link-context": "^1.0.12",
    "apollo-link-error": "^1.1.5",
    "apollo-link-http": "^1.5.9",
    "graphql": "^14.1.1",
    "graphql-tag": "^2.10.1",
    "ioredis": "^4.5.1",
    "postmark": "^2.2.4",
    "react": "^16.7.0",
    "react-apollo": "^2.4.0",
    "react-dom": "^16.7.0",
    "rxjs": "^6.3.3"
  }
}

Additional context
Add any other context about the problem here.

@uwinkler what do you mean not part of the workspace? anyway, I think it's better to put the codegen as a dependency in the root package.json if you are using Yarn workspaces.

@uwinkler Closing for now. Feel free to re-open if you still having an issue.


[Web] Add Material Card Infinite Scroll benchmark

Description
Adds a benchmark that makes an infinite list of Material cards and scrolls it. This benchmark exercises more heavyweight rendering like shadows and clipping and paths.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change.

I'm not sure if there are other files I need to touch to get this benchmark on our dashboard


Generic interface cause error in openapi3 emitter

When defining an interface with a template parameter it cause an error
interface Adoptable<TResource> {
  @Cadl.Http.post adpot(
    ...ResourceParameters<TResource>
  ): TResource | PetStoreError;
}
interface Dogs mixes ResourceOperations<Dog, PetStoreError>, Adoptable<Dog> {}
interface Cats mixes ResourceOperations<Cat, PetStoreError>, Adoptable<Cat> {}

model Cat {}
model Dog {}

error:
C:\dev\azsdk\cadl-dogfood\main.cadl:25:23 - error @cadl-lang/openapi3/invalid-schema: Couldn't get schema for type TemplateParameter

This eror doesn't happen if Adoptable is moved to another file and imported
Solution might just be making sure the emitter doesn't pull template interfaces

I get different errors now:
C:/Src/cadl/packages/rest/lib/resource.cadl:36:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "get" routed at "get /".
C:/Src/cadl/packages/rest/lib/resource.cadl:102:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "list" routed at "get /".
C:/Src/cadl/packages/rest/lib/resource.cadl:36:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "get" routed at "get /".
C:/Src/cadl/packages/rest/lib/resource.cadl:102:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "list" routed at "get /".
C:/Src/cadl/packages/rest/lib/resource.cadl:69:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "update" routed at "patch /".
C:/Src/cadl/packages/rest/lib/resource.cadl:69:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "update" routed at "patch /".
C:/Src/cadl/packages/rest/lib/resource.cadl:86:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "delete" routed at "delete /".
C:/Src/cadl/packages/rest/lib/resource.cadl:86:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "delete" routed at "delete /".
C:/Src/cadl/packages/rest/lib/resource.cadl:59:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "create" routed at "post /".
C:/Src/cadl/packages/samples/scratch/main.cadl:9:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "adpot" routed at "post /".
C:/Src/cadl/packages/rest/lib/resource.cadl:59:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "create" routed at "post /".
C:/Src/cadl/packages/samples/scratch/main.cadl:9:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "adpot" routed at "post /".
C:/Src/cadl/packages/samples/scratch/main.cadl:17:1 - error @cadl-lang/openapi3/duplicate-response: Multiple return types for status code 204
C:/Src/cadl/packages/samples/scratch/main.cadl:17:1 - error @cadl-lang/openapi3/duplicate-response: Multiple return types for status code 204
C:/Src/cadl/packages/samples/scratch/main.cadl:17:1 - error @cadl-lang/openapi3/duplicate-response: Multiple return types for status code 204
C:/Src/cadl/packages/samples/scratch/main.cadl:17:1 - error @cadl-lang/openapi3/duplicate-response: Multiple return types for status code 204
C:/Src/cadl/packages/samples/scratch/main.cadl:17:1 - error @cadl-lang/openapi3/duplicate-response: Multiple return types for status code 204
C:/Src/cadl/packages/samples/scratch/main.cadl:17:1 - error @cadl-lang/openapi3/duplicate-response: Multiple return types for status code 204
C:/Src/cadl/packages/samples/scratch/main.cadl:17:1 - error @cadl-lang/openapi3/duplicate-response: Multiple return types for status code 204
C:/Src/cadl/packages/samples/scratch/main.cadl:17:1 - error @cadl-lang/openapi3/duplicate-response: Multiple return types for status code 204

With the following complete example, I can trim the errors down:
import "@cadl-lang/rest";
import "@cadl-lang/openapi3";

using Cadl.Rest;
using Cadl.Rest.Resource;
using Cadl.Http;

interface Adoptable<TResource> {
  @Cadl.Http.post adopt(...ResourceParameters<TResource>): TResource | PetStoreError;
}
interface Dogs mixes ResourceOperations<Dog, PetStoreError>, Adoptable<Dog> {}

model Cat {}
model Dog {}

model PetStoreError {
  @statusCode code: "default";
}

C:/Src/cadl/packages/rest/lib/resource.cadl:36:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "get" routed at "get /".
C:/Src/cadl/packages/rest/lib/resource.cadl:102:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "list" routed at "get /".
C:/Src/cadl/packages/rest/lib/resource.cadl:59:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "create" routed at "post /".
C:/Src/cadl/packages/samples/scratch/main.cadl:9:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "adopt" routed at "post /".

Hmm, this seems to be something unrelated:
import "@cadl-lang/rest";
import "@cadl-lang/openapi3";

using Cadl.Rest;
using Cadl.Rest.Resource;
using Cadl.Http;

interface Dogs mixes ResourceOperations<Dog, PetStoreError> {}

model Dog {}

model PetStoreError {
  @statusCode code: "default";
}

C:/Src/cadl/packages/rest/lib/resource.cadl:36:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "get" routed at "get /".
C:/Src/cadl/packages/rest/lib/resource.cadl:102:3 - error @cadl-lang/rest/duplicate-operation: Duplicate operation "list" routed at "get /".

Yeah, this happens when you have no @key :( Different bug, we should have a better error for that.

I think the original issue may be fixed. This complete example compiles fine:
import "@cadl-lang/rest";
import "@cadl-lang/openapi3";

using Cadl.Rest;
using Cadl.Rest.Resource;
using Cadl.Http;

interface Adoptable<TResource> {
  @post adopt(...ResourceParameters<TResource>): TResource | PetStoreError;
}

@route("/dogs")
interface Dogs mixes ResourceOperations<Dog, PetStoreError>, Adoptable<Dog> {}

@route("/cats")
interface Cats mixes ResourceOperations<Cat, PetStoreError>, Adoptable<Cat> {}

model Dog {
  @key id: string;
  name: string;
  breed: string;
}

model Cat {
  @key id: string;
  name: string;
  favoriteToy: string;
}

model PetStoreError {
  @statusCode code: "default";
  message: string;
}

I've been unable to repro this across a bunch of commits going back to the date opened. I'm closing as I assume it was fixed but I can't be 100% sure. It could be that the repro steps were not complete and the bug remains. If you have full repro steps (I had to edit the code to get it past other errors), please reopen with them.

I filed #220 to look at the problem I did encounter while trying to repro.

I also filed #221 that might help prevent creating bugs like this one in the future.


library package uber jar by dafault without maven shade, so conflict with aerospike-client

Library is packaged as uber jar by dafault without maven shade, so there is conflict when include aerospike-client as dependency
Generally there should be two artifacts:

regular one
uber jar with shaded dependencies
Thanks.

This library has been moved to QueryEngine as one of java client extensions, try to have a look at:
https://github.com/aerospike/aerospike-client-java/tree/master/extensions/query-engine
Thanks,

I have found this. I removed aerospike-client from my dependencies to make it works.
Not sure that there is a need to change something in project build.
Thanks.


mesh: Check if ack is pending in trans_seg

Before scheduling ack it was checked if previous ack reached it's
timeout. If it did, it was assumed it was sent, where in fact,
timeout could be not reached and work could be canceled. Now,
check if work is pending at all, and if not, schedule next one.
This affects MESH/NODE/TNPT/BV-11-C

This is no longer needed (https://github.com/apache/mynewt-nimble/pull/1062)


Bash script update to add function support automation in the framework

This also addresses issue #17 (https://github.com/datastax/pulsar_workshop/issues/17)
Maven build support is added via the following deployment script parameter:
deployScenario.sh [-rebuildApp] ...


WebDriverWait does not respect 0s wait

Due to the coalesce operator here, WebDriverWait overwrites a requested wait of 0s with the default 30s. That behavior is both non-obvious and not well documented, and pass-throughs of wait arguments are common enough in packages that include the Facebook WebDriver that it's not unreasonable to expected an argument of 0 intended to disable a wait call.
This could be solved if that line were an isset() instead of a coalesce.

Interested in sending in a PR to alter this behavior?    Thanks.

I don't have a Facebook account and thus can sign the licensing agreement
apparently required of a pull request, otherwise I would have led with that.
On Tuesday, December 8, 2015, Fosco Marotto<EMAIL_ADDRESS>wrote:

Interested in sending in a PR to alter this behavior?  Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/php-webdriver/issues/265#issuecomment-162885078
.

*cannot
On Tuesday, December 8, 2015, Aaron Oehlschlaeger<EMAIL_ADDRESS>wrote:

I don't have a Facebook account and thus can sign the licensing agreement
apparently required of a pull request, otherwise I would have led with
that.
On Tuesday, December 8, 2015, Fosco Marotto<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

Interested in sending in a PR to alter this behavior?  Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/php-webdriver/issues/265#issuecomment-162885078
.

Ok, please review #267 for me.


Add Rails 5x support

Hello, @teohm! This is your first Pull Request that will be reviewed by Ebert, an automatic Code Review service. It will leave comments on this diff with potential issues and style violations found in the code as you push new commits. You can also see all the issues found on this Pull Request on its review page. Please check our documentation for more information.

Ebert has finished reviewing this Pull Request and has found:

1 possible new issue (including those that may have been commented here).

You can see more details about this review at https://ebertapp.io/github/blacktangent/attributes_for/pulls/10.


Fix: delete context when patch outputs in trait

Signed-off-by: FogDong<EMAIL_ADDRESS>Description of your changes

Fixes #1851
I have:

[x] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[x] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

/cc @wonderflow

No effect.

ping @oiar, Will this changes affect the patch trait that we use?

No effect.

Details

It may affect the users who're using context: outputs: resource to patch traits in trait definition, but those users are also affected by this bug: the context is overridden.

please make sure it won't break any existing use case

It may affect the users who're using context: outputs: resource to patch traits in trait definition, but those users are also affected by this bug: the context is overridden.

Can you make some clarification about this bug fix and change? I think users will refer to this PR in release not.

I'll leave this feature in v1.4 and not backport to 1.3. Because it may cause some incompatible.

Though this PR fixes the override context problem raised by #1704 , still, if we want to patch outputs and output at the same time, we'll patch outputs into the output.
We may need to change the code here to avoid it:

We can delete the outputs part in patch when patching to workload. But if we do so, users can not patch the outputs in the workload struct.
Or we can delete the original code and add some new field like patchTrait to patch traits.

/cc @wonderflow @leejanee @fourierr

@FogDong Please give some examples

@FogDong Please give some examples

For example, if we patch trait and workload at the same time in trait, the definition will like:
  patch: {
      outputs: {
        service: {
          spec: {
            // +patchKey=port
            // +patchStrategy=retainKeys
            ports: [{
              port: 2333
              targetPort: 2333
              name: "test"
            }]
          }
        }
      }
      spec: template: spec: {
          containers: [{
              name: context.name
              // +patchKey=configMapRef.name,secretRef.name
              // +patchStrategy=retainKeys
              envFrom: [
                  {
                    configMapRef: {
                      name: parameter.cmname
                    }
                  },
                  {
                    secretRef: {
                      name: parameter.sename
                    }
                  }
              ]
          }]
      }
  }

After patching, the workload will like:
// original workload struct
...

outputs: {
....
}

We can delete the outputs part when trying to patch the worload, but it'll make outputs our built-in field in the workload and users can not use them.
We can also change it to:
patch: {
// patch to workload
}

patchTraits: {
// patch to traits
}

Yes, use a separate keyword can make the things easier:
patch: {
// patch to workload
}

patchOutputs: {
// patch to traits or outputs from workload
}

lgtm


External Subtitle File Download

Not reporting any bug just wanted to know is there any way to get the subtitle file as well or do we need to extract it from the merged mp4 file ourselves? tried -c 0 option but it downloads the subtitles and merges it to the video and audio file. Was wondering if there was a way for the program to leave a copy of the subtitle file also

Hi,
there is the option
-k             Keep video, audio and subtitles. Don't merge using ffmpeg
If you use it the subtitle should be kept a separate file and not be merged. Please try it and let me know if it worked for you.

Hi,
there is the option -k Keep video, audio and subtitles. Don't merge using ffmpeg If you use it the subtitle should be kept a separate file and not be merged. Please try it and let me know if it worked for you.

yep it works, thanks a lot


Issue 153 Proposal - Adding headers to intent handlers on smarthome

Never written TypeScript before, so I hope I updated the interface correctly.

This has been resolved in 6a5820edbc52aea730195e43f5c61f5164fdc2bc.


Show all exercises and their status in the 'solved exercises' page

Right now in the /exercitii-rezolvate page we see just submissions awaiting our feedback.
Let's add all submissions no matter their status. This way we can get a better idea of how many exercises are in progress, done, etc

Done!


Mozilla Firefox edit with row clickable

Hi Scott,
when i set i want row clickable and also i want to have editable some columns like this:
        contactGridDataBinder.BindCommitEdit(vm);
        contactGridDataBinder.BindClickHandler(contactsGrid);

it's working perfect in all browsers except Mozilla Firefox there is row clickable and I can open a detail but I can't edit a column.
Adam

if you override doubleClick method on grid line with your's owne edit feature works in FF as well. Just a hint where to look for.


MinGW compilation warning in pedantic mode #306

Coverage remained the same at 100.0% when pulling 9dd42b45779319fec591f57d032c167be2ab602a on chronoxor:master into adb7e7c489b0574a6c2f354ab14213bfb9dd4e49 on SRombauts:master.

@chronoxor If you're interested, I proposed a fix for this in #308 which doesn't change the build flags.

Thanks, but I have merged the fix for string truncation instead.


feat: add badges to README

Add status badges to README file
/1 /clear /ci
/giphy peanuts

/giphy peanuts


Bump snapshot version

Build triggered. sha1 is merged.

Build started sha1 is merged.

Build finished.

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@89c028e). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev      #71   +/-   ##
======================================
  Coverage       ?   88.61%
======================================
  Files          ?       22
  Lines          ?      281
  Branches       ?       22
======================================
  Hits           ?      249
  Misses         ?       23
  Partials       ?        9

Continue to review full report at Codecov.

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


Add Armenia mobile number (+37444 xx xx xx)

Armenian mobile operator Ucom started to sell numbers with prefix +374 44 since  9 november.
Some news sites have written about it

geek.am

newsarmenia.am

Also new numbers are specified in Wikipedia article about Ucom.

Hi,
Thanks for providing all the details we need! We've accepted this issue and will fix this in an upcoming release.
Please note that you have submitted this information with the knowledge that we may use, modify, reproduce, publicly display, and distribute the information in accordance with our open source policies. Please let us know if you did not intend to submit the information for such use.

Fixed in release 7.7.5.


Major overhaul- Work In Progress

Created standard GitHub project stucture. Included in this was an MIT License file
with a copyright of Codecov and contributors.
Switched to using xUnit.
Cleaned up code.
Cleaned up readme.
Fixed solution name.

@stevepeak,
Your suggestions and comments especially on the README file would be appreciated...Thanks!

I think the OpenCover filters where wrong/missing too, which is why the coverage changed so much.

@stevepeak
The example C# project StyleCopAnalyzers is now using Codecov-exe. I've updated the overhauled readme with that info. Would you mind taking a look at this PR when you get a chance? Thanks!

Thank you @larzw 👍


Enable RenderPassLoadOpTests on Vulkan back-ends

RenderPassLoadOpTests can pass on Vulkan back-ends now.

We have verified this test can pass on the following Vulkan drivers:
Linux/Intel(HD630), Windows/Intel(HD630), Linux/Nvidia(GTX970), Windows/Nvidia(GTX950, GTX1060)

Fantastic, thanks for verifying!
Leaving for @kangz to do second review and merge.
On Fri, Aug 17, 2018, 12:08 AM Jiawei Shao<EMAIL_ADDRESS>wrote:

We have verified this test can pass on the following Vulkan drivers:
Linux/Intel(HD630), Windows/Intel(HD630), Linux/Nvidia(GTX970),
Windows/Nvidia(GTX950, GTX1060)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/nxt-standalone/pull/245#issuecomment-413777976,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlAk9VtBgwrPsIOVP8Otlvu78JisTsWks5uRmvmgaJpZM4WA4hH
.

LGTM!


[gha][toolchain-size] Pin external GitHub actions to specific commits

This prevents potentially breaking changes upstream from automatically rolling into our workflows, and ensures that builds are reproducible.
Changes
Pin these actions

compnerd/gha-setup-swift
compnerd/gha-setup-vsdevenv
thebrowsercompany/gha-google-bloaty

It might make sense to pin to a specific release as we are pinning to a version.

It might make sense to pin to a specific release as we are pinning to a version.

😭 We should probably come up with a cross-repo standard for BCNY and write it down somewhere.


[Godot 4rc5] Error in Initialize

Godot version
v4.0.rc5.official [6296b4600]
System information
Debian 11
Issue description
When  I run the project I have this error in tab errors:
E 0:00:01:0281   initialize: Condition "err != OK" is true.
  <C++ Source>   servers/rendering/renderer_rd/shader_rd.cpp:675 @ initialize()

Steps to reproduce
run the example from https://godotengine.org/storage/blog/multiplayer-in-godot-4-0-scene-replication/project.zip
Got from https://godotengine.org/article/multiplayer-in-godot-4-0-scene-replication/
Minimal reproduction project
https://godotengine.org/storage/blog/multiplayer-in-godot-4-0-scene-replication/project.zip

I can't reproduce on PopOS 22.04 intel integrated graphics.
Despite the error message, does the demo still render correctly?

Yes, it does.


NetworkError when attempting to fetch resource.

Describe the bug
NetworkError when attempting to fetch resource.
To Reproduce
Steps to reproduce the behavior. For example:

Go to 'https://determined-aryabhata-ec886e.netlify.app/admin/'
Click on 'Login with Netlify Identity'
Scroll down to '....'
See error

Expected behavior
NetworkError when attempting to fetch resource.
Screenshots

Applicable Versions:

netlify-cms 2.10.50
Git provider:GitHub
OS: Ubuntu Xenial 16.04
Browser version [e.g. chrome 22, safari 11]

Node.JS version:

CMS configuration
backend:
  name: git-gateway
  branch: master
publish_mode: editorial_workflow
media_folder: "assets/img/uploads"
collections:
  - label: "Categories"
    name: "categories"
    folder: "category"
    create: true
    editor:
      preview: false
    slug: "{{slug}}"
    preview_path: "category/{{slug}}"
    extension: "md"
    fields:
      - label: "Layout"
        name: "layout"
        widget: "hidden"
        default: "category"
      - label: "Title"
        name: "title"
        widget: "string"
      - label: "Slug"
        name: "slug"
        widget: "hidden"
        default: "{{slug}}"
      - label: "Description"
        name: "description"
        widget: "string"
        required: false
  - label: "Posts"
    name: "posts"
    folder: "_posts"
    create: true
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    preview_path: "{{title}}"
    extension: "md"
    fields:
      - label: "Publish Date"
        name: "date"
        widget: "datetime"
        format: "YYYY-MM-DD HH:mm:ss"
      - label: "Layout"
        name: "layout"
        widget: "hidden"
        default: "post"
      - label: "Title"
        name: "title"
        widget: "string"
      - label: "Subtitle"
        name: "subtitle"
        widget: "string"
        required: false
      - label: "Description"
        name: "description"
        hint: "This will be used across the pages and for search engines."
        widget: "string"
      - label: "Featured Image"
        name: "image"
        widget: "image"
        allow_multiple: false
        required: false
      - label: "Optimized Image"
        name: "optimized_image"
        widget: "image"
        allow_multiple: false
        required: false
        hint: "You can set an optimized image version to show on the home page"
      - label: "Category"
        name: "category"
        widget: "relation"
        collection: "categories"
        searchFields: ["title"]
        valueField: "slug"
        displayFields: ["title"]
      - label: "Tags"
        name: "tags"
        hint: "Separate with commas. These will also be used as keywords for search engines."
        widget: "list"
      - label: "Author"
        name: "author"
        widget: "relation"
        collection: "authors"
        displayFields: [display_name]
        searchFields: [display_name]
        valueField: "name"
      - label: "Paginate"
        name: "paginate"
        widget: "boolean"
        default: false
      - label: "Body"
        name: "body"
        widget: "markdown"
  - label: "Pages"
    name: "pages"
    folder: "pages"
    create: true
    slug: "{{slug}}"
    preview_path: "{{slug}}"
    extension: "md"
    fields:
      - label: "Layout"
        name: "layout"
        widget: "hidden"
        default: "page"
      - label: "Show in menu"
        name: "menu"
        widget: "boolean"
        default: true
      - label: "Publish Date"
        name: "date"
        widget: "datetime"
        format: "YYYY-MM-DD HH:mm:ss"
      - label: "Title"
        name: "title"
        widget: "string"
      - label: "Permalink"
        name: "permalink"
        widget: "hidden"
        default: "/{{slug}}/"
      - label: "Description"
        name: "description"
        hint: "This will be used as description for search engines."
        widget: "string"
        required: false
      - label: "Keywords"
        name: "tags"
        hint: "Separate with commas. These will also be used as keywords for search engines."

          - label: "Keywords"
            name: "tags"
            hint: "Separate with commas. These will also be used as keywords for search engines."

                    required: false
                  - label: "Text"
                    name: "message"
                    widget: "string"
                    hint: "Ex: Thank you for reaching us."
                    required: false
      - label: "Advanced"
        name: "advanced"
        file: "src/yml/advanced.yml"
        fields:
          - label: "Base URL"
            name: "baseurl"
            widget: "string"
            hint: "The subpath of your site, e.g. /blog"
          - label: "URL"
            name: "url"
            widget: "string"
            hint: "The base hostname and protocol for your site, e.g. https://rossener.com"
          - label: "Google Analytics ID"
            name: "google_analytics"
            widget: "string"
            required: false
          - label: "Language"
            name: "language"
            widget: "string"
            hint: "Content language, ex: pt-BR, en, fr"
          - label: "Categories folder"
            name: "categories_folder"
            widget: "string"
            hint: "Folder where all the categories pages are. Ex: category"
            required: false
          - label: "Contact Feedback URL"
            name: "sent_message_url"
            hint: "URL where the user will be redirected for after submit the contact form. Ex: /contact/message-sent/"
            required: false

Additional context

Hi @rokib-rajon thank you for reporting the issue.
I'm getting 404 when trying to access the link you provider or even https://determined-aryabhata-ec886e.netlify.app/

It's working now !

@rokib-rajon what did you change to get it working? I'm getting the same error "NetworkError when attempting to fetch resource."

@siweizzz
I did nothing, after few hours it started to work. I think the problem is from netilfy end.

Thanks for the reply, it's also working for me now. I did some reading on this yesterday, I think it's because I changed the site name and the DNS needs time to propagate.


idea: Include Changes to Outputs in Pull Request Comments

Hi,
I've noticed that changes to outputs from the terraform plan are not being reflected in the pull request comments generated by this action.
Could you clarify if this is a design choice or a potential enhancement? It would be really helpful to have these output changes listed along with other modifications in the plan for better visibility during code reviews.
Thanks for the great work on this action! I’m looking forward to your feedback.
Comment in PR indicates there are no changes:

Terraform plan in workflow indicates the following:

Good catch, I think that would be a great addition to this action! Unfortunately, it is currently unsupported.
I'd be happy to review a PR for this, it would take me a some time until I'd find the time to see through the implementation myself :eyes:


Keract for non convolutional models

Hi there,
Is there possibly an example/tutorial of how to use keract when you have a model that does not process images. As example a simple LSTM with soft max function.
I would like to see how one could use the functions keract offers in that way. Will be very useful to help explain predictions.

@Lecia321 well keract gives you the outputs of each of your layers. So you can adapt it to your problem. At the moment, there's no example dealing with visualisation for LSTM. But there's a very good tutorial about it (for text generation):

http://karpathy.github.io/2015/05/21/rnn-effectiveness/
http://blog.echen.me/
https://stats.stackexchange.com/questions/323782/how-to-visualize-char-rnn-model

Thank you @philipperemy for the reference to the tutorials. They will definitely help since I am very new to keract.

@Lecia321 welcome! That would be great if you can share some of your code after that others can re-use for visualizing non conv layers. Good luck!

Kinda related to visualizing layers:
Extract a layers output, then write it to file. Load the file into TensorBoard (or projector.tensorflow.org), then visualize it using tSNE or PCA.
Sample code, x is a batch to be profiled, y are the according labels.
import io

class LayerOutputCallback(keras.callbacks.Callback):
    __slots__=["x", "y", "layer_name", "counter", "frequency"]
    def __init__(self, x, y, layer_name, frequency):
      super(LayerOutputCallback, self).__init__()
      self.x = x
      self.y = y
      print(self.y.shape)
      self.layer_name = layer_name
      self.counter = 0
      self.frequency = frequency

    def on_epoch_end(self, epoch, logs=None):
      self.counter += 1
      if self.counter == self.frequency: #calculate intermediate ouput every frequency epochs
        self.counter = 0 #reset the counter
        self.get_layer_output()

    def get_layer_output(self):
      intermediate_model = tf.keras.Model(inputs = self.model.inputs, outputs=self.model.get_layer(name=self.layer_name).output)
      layer_output = intermediate_model(self.x)
      print("\n Now outputing layer features")
      #print(layer_output.shape)

      #for i in range(5):
      #  print(self.y[i], layer_output[i])

      out_v = io.open('vectors.tsv', 'a', encoding='utf-8')
      out_m = io.open('metadata.tsv', 'a', encoding='utf-8')

      for index in range(len(self.y)):
        vec = layer_output[index]
        out_v.write('\t'.join([str(x) for x in vec.numpy()]) + "\n")
        out_m.write(str(self.y[index]) + "\n")
      out_v.close()
      out_m.close()
      print("\n")


Fix function clause in couch_replicator_scheduler_job

ibrowse responses may crash the job process with a function clause in handle_info/2. Ignore those with a note that aliases should hopefully fix this issue in the future.

Example of a crash:
couch_replicator_scheduler_job:handle_info({#Ref<0.199527780.840171523.212239>,{ok,"200",[{"Cache-Control","must-revalidate"},...

From https://couchdb.slack.com/archives/C49LEE7NW/p1646318130239849


Where is the implementation of the the API's

HI everyone,
Whenever i fill the form to join the community, it constantly sends me an alert that  Improper data. Please Re-check the data, So I cloned the repo and started to dig into code to find out what leads to this message and found out that https://api.realdevsquad.com/users/self/intro API is responsible for this, but I couldn't find where is it's implementation.
Therefore I request for help in this

Can you attach the screenshot?

so, i have found out the issue @chirag35847
We have recently introduced a new field in the form you are filling, now what happened is, the validation for the new field is already merged in the backend, but at the frontend the field is still not visible as the PR is still under review.
Meanwhile, i will suggest you contact Ankush directly on twitter if you want to join the community.
Thank you.

Ok got it, I will contact Ankush on twitter.
Thank you so much for your time


Remove hefty analysis meta

Slack: https://centrepopgen.slack.com/archives/C018KFBCR1C/p1714624645731339
TL; DR
We're shoving a lot of stuff into analysis entry meta, and it's making metamist really unhappy
Hefty Analyses
@illusional has identified some MASSIVE analysis entries. Part of the reason appears to be sections of code where we transcribe entire QC reports into the analysis meta:

https://github.com/populationgenomics/production-pipelines/blob/7a3a1c1349b236a6df64f42c3b0ffb4dca1a910c/cpg_workflows/stages/joint_genotyping_qc.py#L113-L120
https://github.com/populationgenomics/production-pipelines/blob/7a3a1c1349b236a6df64f42c3b0ffb4dca1a910c/cpg_workflows/stages/cram_qc.py#L216-L223
https://github.com/populationgenomics/production-pipelines/blob/7a3a1c1349b236a6df64f42c3b0ffb4dca1a910c/cpg_workflows/stages/gvcf_qc.py#L99

So... we should stop doing that...
SG IDs
We take all the SG IDs relevant to an analysis and write them into the analysis meta. This is done for all Cohort and Dataset stages:

Cohort Stage
Dataset Stage

These methods are called as part of the analysis entry creation process: here
So... stop doing that as well. If we need SG IDs to be present, there is already a top-level field sequencing_group_ids designed to hold that information. Once we fully adopt custom cohorts we can accomplish this using the Custom Cohort ID/Name, so that these will be super lightweight. The Analysis entry already has an attribute ready for cohort_ids: here

FWIW, the analysis object can already be linked against multiple cohort_ids, so also best to avoid putting these in the meta:
https://github.com/populationgenomics/metamist/blob/4ae0883d5031f9d49d3edecce24e4f887e1d431e/models/models/analysis.py#L98-L106

@MattWellie thanks for the writeup. Although it's convenient to access the sequencing groups associated with an analysis by looking at analysis.meta.sequencing_groups - which is usually just a list of strings - this field is mutable and risks not being accurate when compared to retrieving the sequencing groups associated with an analysis directly via the analysis_sequencing_group table.
The difference can be seen in some GraphQL queries.
First method is reading the sequencing groups from the analysis meta:
query MyQuery {
  project(name: "my-dataset") {
    analyses {
      id
      type
      meta
    }
  }
}

...
        {
          "id": 123,
          "type": "qc",
          "meta": {
            "sequencing_groups": [
              "CPG12345",
              "CPG23456",
              "CPG34567",
            ]
          }
        },
...

Compared to directly accessing the sequencing groups associated with the analysis, instead of reading them from the meta:
query MyQuery {
  project(name: "my-dataset") {
    analyses {
      id
      type
      sequencingGroups {
        id
      }
    }
  }
}

...
        {
          "id": 123,
          "type": "qc",
           "sequencingGroups": [
              {"id": "CPG12345"},
              {"id": "CPG23456"},
              {"id": "CPG34567"},
            ]
          }
        },
...

The second way is more reliable and true, although sadly you have to parse out the IDs rather than getting a nice list. If we plan to totally do away with the first method, i.e. no more sg IDs in meta, then some scripts & modules across the codebases will need to be updated to get IDs via the second method.

I think that from a 'no longer generate huge clunky data' perspective this is solved. @illusional was planning to discard all the previous weighty meta from existing analyses, but that's not directly relevant to this issue.


lnwire: adjusted coop close messages to comply with spec

Removed close_request and close_complete and replaced with shutdown and
closing_signed. Addresses the initial part of issue #49.

Coverage decreased (-0.3%) to 68.635% when pulling e3daceface1f4279d3aebe5aafdf74e2d3cadaa9 on bryanvu:channelclose into d2b4f143b958a33002286572533dcbe7e06aae5c on lightningnetwork:master.

Updated with support for shutdown messages and additional coop close workflow steps.

Updated with requested changes. Previous version can be found at: https://github.com/bryanvu/lnd/tree/channelclose1

Updated. Previous version at: https://github.com/bryanvu/lnd/tree/channelclose2

Coverage decreased (-0.1%) to 73.438% when pulling 131f3adee00065b1c682c8858fe5c6b28b77ea1f on bryanvu:channelclose into 1124b4556f61c9ee3199e885319a6e775f14e44d on lightningnetwork:master.

Rebased and added a commit. Previous version at: https://github.com/bryanvu/lnd/tree/channelclose3

Coverage decreased (-0.09%) to 73.526% when pulling 9f39bac22307125472f57d40b338ec1ed13bd51e on bryanvu:channelclose into a5616a3c84bba538c0f190212e3b807b1794f832 on lightningnetwork:master.

Coverage decreased (-0.09%) to 73.529% when pulling edbf0b8999338de178537cac56d83cc1c7f76939 on bryanvu:channelclose into 570c0e55088d66b07eabc3a5ea74134274f050c3 on lightningnetwork:master.

Coverage decreased (-0.09%) to 73.529% when pulling 4660ddfdeb6a785b547c48788041a21a726ebd97 on bryanvu:channelclose into 570c0e55088d66b07eabc3a5ea74134274f050c3 on lightningnetwork:master.


Oracle Cloudworld

Will any of the team be at cloud world? Also is there any talks using oci-landing-zones?

Good Morning Mike, thank for your message. Our team will not be present at Cloud World but there should be a team we worked with that will present the SCCA LZ (https://github.com/oracle-quickstart/oci-scca-landingzone). In case you would like to have a dedicated chat with us we are happy to organise it, just let us know.
Kind regards,
Fabio


User not logged in after email confirmation

After registering a new user, and clicking on the confirmation link, the user is not logged in and the events  'auth:email-confirmation-success' , 'auth:email-confirmation-error' don't work.
The server does confirm the user and I can log in manually after this.
There are no visible js errors. Here's the rails output.
Started GET "/api/auth/confirmation?confirmation_token=abAsBkDwUYW8K6zDPV2k" for <IP_ADDRESS> at 2014-08-23 17:13:52 -0300
Processing by DeviseTokenAuth::ConfirmationsController#show as HTML
  Parameters: {"confirmation_token"=>"abAsBkDwUYW8K6zDPV2k"}
  User Load (0.2ms)  SELECT  "users".* FROM "users"  WHERE "users"."confirmation_token" = '58c57c0679304e4feec4e3aab44aef773bb5dc4cba577e3e05281120ea7f1e1c'  ORDER BY "users"."id" ASC LIMIT 1
   (0.1ms)  begin transaction
  SQL (0.5ms)  UPDATE "users" SET "confirmation_token" = ?, "confirmed_at" = ?, "tokens" = ?, "updated_at" = ?  WHERE "users"."id" = 7  [["confirmation_token", "abAsBkDwUYW8K6zDPV2k"], ["tokens", "{\"rqqUfUebi27nfkms1Q95gg\":{\"token\":\"$2a$10$M7MLatfE53/oTzlAku7Z/.a8SKEZowRc0w3FIUnv1.4OeGKtDuHB.\",\"expiry\":1410034433}}"], ["updated_at", "2014-08-23 20:13:53.082659"]]
   (161.1ms)  commit transaction
Redirected to http://localhost:9000/?account_confirmation_success=true&client_id=rqqUfUebi27nfkms1Q95gg&expiry=1410034433&token=3soO5-IWmiuQEFXqPv96dQ&uid=xxx%40gmail.com#/users/new
Completed 302 Found in 415ms (ActiveRecord: 337.0ms)

Hi @lynndylanhurley , I used the devise_token_auth, but when I click the link from my mailbox, it cannot work. The confirmation is not finished.


How to start showing git branch only while in repository's root

As far as I understand, it's core of oh-my-zsh (not git plugin) which showing current git branch as part of terminal prompt?
I want to change this behavior and see branch in prompt only while current directory is repository's root (has .git folder). When I'll go deeper in folder structrure I want more shorter prompt.
How can I achieve this? Can I override something and not break oh-my-zsh update mechanism?

Ok, I realized that it's theme responsible for that prompt, so I can override it, I suppose.

Will leave it here just in case.
In my case it is agnoster theme. There is prompt_git() function in it. So to achieve what I want I've changed first condition inside this function to:
  if [ "$(find ./ -maxdepth 1 -name '.git' | wc -l)" = 0 ] || [ "$(git config --get oh-my-zsh.hide-status 2>/dev/null)" = 1 ] ; then
    return
  fi

You can use -d .git which checks if there's a .git folder in the current directory. In your case, negated with !.
  if [ ! -d .git ] || [ "$(git config --get oh-my-zsh.hide-status 2>/dev/null)" = 1 ] ; then
    return
  fi

Whoa! It's much simpler :)
On Tue, 22 Oct 2019, 11:45 Marc Cornellà<EMAIL_ADDRESS>wrote:

You can use -d .git which checks if there's a .git folder in the current
directory. In your case, negated with !.
if [ ! -d .git ] || [ "$(git config --get oh-my-zsh.hide-status 2>/dev/null)" = 1 ] ; then
return
fi
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/robbyrussell/oh-my-zsh/issues/8300?email_source=notifications&email_token=AAGSAMAIOXLRNUUDS3GU4VDQP24RXA5CNFSM4JDLG2V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB47E2Y#issuecomment-544862827,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGSAME5555U5UMG6DWQVQTQP24RXANCNFSM4JDLG2VQ
.


[Low]  While the extension is running error appear in console

JDN v 3.1.157
Back-end v 2022-03-30-06.47.33
Chrome 100.0.4896.75(64 bit)

Open any page.
Open DevTools and select JDN
Create new page object.
Geberate
Select Console in DevTools

AR:
In the console: "Uncaught (in promise) Error: The message port closed before a response was received".
In the extension log:

ER: No errors.
P.S. Errors do not visually affect using of the extension, or I have not found it yet.

3.1.180


Screenshots when a test failed?

This feature is really important please so we can get screenshots on the report when a test fails
I had this with detox:
const Allure = require('allure-js-commons'); // version "1.3.2",
const fs = require('fs');
const stripAnsi = require('strip-ansi');

class AllureReporterCircus {

  constructor({ detox }) {
    this.allure = new Allure();
    this.detox = detox;
  }

  run_describe_start(event) {
    if (event.describeBlock.parent !== undefined) {
      this.allure.startSuite(event.describeBlock.name);
    }
  }

  run_describe_finish(event) {
    if (event.describeBlock.parent !== undefined) {
      this.allure.endSuite();
    }
  }

  test_start(event) {
    const { test } = event;
    this.allure.startCase(test.name)
  }

  async test_done(event) {
    if (event.test.errors.length > 0) {
      const { test } = event;
      const screenshotPath = await this.detox.device.takeScreenshot(`${test.startedAt}-failed`);
      const buffer = fs.readFileSync(`${screenshotPath}`);
      this.allure.addAttachment('Screenshot test failue', Buffer.from(buffer, 'base64'), 'image/png');

      const err = test.errors[0][0];
      err.message = stripAnsi(err.message);
      err.stack = stripAnsi(err.stack);

      this.allure.endCase('failed', err);
    }
    else {
      this.allure.endCase('passed')
    }
  }

  test_skip(event) {
    const { test } = event;
    this.allure.startCase(test.name);
    this.allure.pendingCase(test.name);
  }
}

module.exports = AllureReporterCircus;

Is there a way I could have this with jest-allure2-reporter?

Sure, I realize the importance of this feature.
This is blocked currenly by #4, and I plan to renew works on it very soon.
This is exactly the reason why https://github.com/wix/Detox/issues/2337 is still open.
I'll leave your issue open for other people looking at this repo so they don't create duplicates.
Thanks for checking out this repo. I hope it brings you joy soon.

I think that ETA for Detox+Allure is likely to be around December 2023.
Today I released the alpha v2 of jest-allure2-reporter, but it will take some time to rewrite the artifacts subsystem in Detox so it can be easily integrated with it.
The rewrite is mostly about simplification of the source code of Detox, but since there's a huge piece of it (around 10k lines of code, AFAIR), it is not that trivial. 🫠

@noomorph any new ETA on this? thank you

Have you checked this adapter, just in case?
https://github.com/wix-incubator/detox-allure2-adapter


Add option to suppress stdout log messages in API

Right now, if I use sfizz's C++ API and load a sfz file with loadSfzFile(), then sfizz may print out lot of stuff on stdout, e.g.:
Changing default sample path to masonhamlin-a samples/
Updating masonhamlin-a samples/MH AT2035 f A#3.wav to "MasonHamlin-A Samples/MH AT2035 f A#3.wav"
...

It would be great if there was an option to turn off this logging, as I am writing a CLI application and this verbose output is really distracting (sfizz shouldn't print something to stdout).
This option should take precendence over the compile time options defined in https://github.com/sfztools/sfizz/blob/acd866fd3d247d2fc659593cac96e88e801c29e2/src/sfizz/utility/Debug.h#L68

Thanks for the report, I'll look into it!

@paulfd what do you think about https://github.com/gabime/spdlog?

Last I checked it wasn't real-time safe (that said, writing to stdout isn't either). I had in mind at some point to find some way to log important things in RT.

I found gabime/spdlog#1873, but I'm not sure if it's relevant for our use case


cleaned up xc schemes, and updated swift version to 5.0 for build errors

@googlebot I signed it!

@googlebot I signed it!


Upgrading from version 0.7.3 to 0.9.2 fails.

Spiderpool Version
v0.9.2
Bug Type
Installation Issue
Main CNI
macvlan
What happened?
Upgrading from version 0.7.3 to 0.9.2 fails.

After the upgrade, multus is lost and network-attachment-definitions.k8s.cni.cncf.io cannot be found.

{"level":"ERROR","ts":"2024-04-11T09:18:28.161Z","logger":"MultusConfig-Informer","caller":"multuscniconfig/multusconfig_informer.go:230","msg":"encountered  MultusConfig informer error 'failed to get API group resources: unable to retrieve the complete list of server APIs: k8s.cni.cncf.io/v1: the server could not find the requested resource', requeue it after '5s'"}
{"level":"INFO","ts":"2024-04-11T09:18:28.212Z","logger":"Coordinator-Informer","caller":"coordinatormanager/coordinator_informer.go:322","msg":"status have no changes, ignore add it to workqueue","CoordinatorName":"default","Operation":"UPDATE"}
{"level":"ERROR","ts":"2024-04-11T09:18:28.555Z","logger":"MultusConfig-Informer","caller":"multuscniconfig/multusconfig_informer.go:230","msg":"encountered  MultusConfig informer error 'failed to get API group resources: unable to retrieve the complete list of server APIs: k8s.cni.cncf.io/v1: the server could not find the requested resource', requeue it after '5s'"}
{"level":"ERROR","ts":"2024-04-11T09:18:28.556Z","logger":"MultusConfig-Informer","caller":"multuscniconfig/multusconfig_informer.go:230","msg":"encountered  MultusConfig informer error 'failed to get API group resources: unable to retrieve the complete list of server APIs: k8s.cni.cncf.io/v1: the server could not find the requested resource', requeue it after '5s'"}
{"level":"ERROR","ts":"2024-04-11T09:18:28.558Z","logger":"MultusConfig-Informer","caller":"multuscniconfig/multusconfig_informer.go:230","msg":"encountered  MultusConfig informer error 'failed to get API group resources: unable to retrieve the complete list of server APIs: k8s.cni.cncf.io/v1: the server could not find the requested resource', requeue it after '5s'"}

[root@controller-node-1 net.d]# kubectl get network-attachment-definitions.k8s.cni.cncf.io -A
error: the server doesn't have a resource type "network-attachment-definitions"

What did you expect to happen?
succeeded to update
How to reproduce it (as minimally and precisely as possible)

Install spiderpool version 0.7.3
Create a pod for use.
Apply all crds of version 0.9.2
helm upgrade --version=0.9.2

Additional Context
No response

CRDs should be apply manually.

Before upgrading
kube-system   spiderpool-agent-29t57                                  1/1     Running             0               15m
kube-system   spiderpool-agent-n5btp                                  1/1     Running             2 (15m ago)     15m
kube-system   spiderpool-controller-f48c5b69d-6749b                   1/1     Running             0               15m
kube-system   spiderpool-init                                         0/1     Completed           0               15m
kube-system   spiderpool-multus-2tfsr                                 1/1     Running             0               15m
kube-system   spiderpool-multus-k754w                                 1/1     Running             0               15m

After upgrade
kube-system   spiderpool-agent-nd6mm                                  1/1     Running             0               95s
kube-system   spiderpool-agent-xgzdr                                  1/1     Running             0               98s
kube-system   spiderpool-controller-5769cc7776-7z2s4                  1/1     Running             0               98s
kube-system   spiderpool-init                                         0/1     Running             0               108s

升级前手动安装了所有的 CRDs,看起来像是升级前是通过 spiderpool-multus 安装了 network-attachment-definitions.k8s.cni.cncf.io，但是在升级到新版的时候观测到 network-attachment-definitions 被移除了。
也许：helm upgrade 会删除 spiderpool-multus ，这个 Pod 中会去移除 CRDs ？或者 helm uograde 升级到新版本时，在新版本中有 multus.uninstall，且默认值是 true，upgrade 前，执行了卸载的命令？
禁用与启用 multus.install 均尝试过，该 network-attachment-definitions 都会被删除，当前是先 apply 所有的 crds yaml，然后再执行的 helm upgrade。看起来应该更改一下升级的步骤，先执行  helm upgrade，等所有组件起来后，再 apply 所有的 crds yaml


chore: Rename CONTRIBUTE.md to CONTRIBUTING.md

GitHub has a nice little community-page with recommended community
standards here.
They seem to prefer this file being named CONTRIBUTING so this
is low hanging fruit for scoring better in that respect.
Also, standards are nice.

@gbrownlee Du har kanskje lyst til å merge #8 først, så kan jeg oppdatere denne om det blir conflicts?


Frontend Connection Status

The front end should indicate if the back-end is running.
Right now it shows the file-drop area if neo4j/the backend is connected but there should be a clearer indication.

They are not the same, the 6 is about sending connection information for neo4j to the backend.
5 is about - is the front-end able to connect to the backend.

@jexp , Sharing a screenshot for reference. Please let us know if the connection information is ok in this way.

Handled Previously


Need internal jump menu

For QC purposes, we need an "internal" menu to jump to the screens/states that are otherwise inaccessible, such as proximity alerts, positive cases, error conditions, etc.

@mboskin the debug menu allows access to the Exposure UI flows now including the alert (I tested build 22 on iOS). Is this enough for NYS? Currently you can't get to the error conditions directly. If you need this for QA, bump up the priority accordingly.

Kevin,
This is your decision, not mine. Issue #49 (filed by Fahd) is:
“For QC purposes, we need an "internal" menu to jump to the screens/states that are otherwise inaccessible, such as proximity alerts, positive cases, error conditions, etc.”
Their response is:
“the debug menu allows access to the Exposure UI flows now including the alert (I tested build 22 on iOS). Is this enough for NYS? Currently you can't get to the error conditions directly. If you need this for QA, bump up the priority accordingly.”

Michael Boskin
Senior Consultant, NYSTEC
(518) 496-7667 – Mobile
mboskin<EMAIL_ADDRESS>www.nystec.comhttp://www.nystec.com/
From: fahd-arshad<EMAIL_ADDRESS>Sent: Tuesday, September 1, 2020 11:15 AM
To: project-vagabond/covid-green-app<EMAIL_ADDRESS>Cc: Michael Boskin<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [project-vagabond/covid-green-app] Need internal jump menu (#49)
[External Email]
Assigned #49https://github.com/project-vagabond/covid-green-app/issues/49 to @mboskinhttps://github.com/mboskin.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/project-vagabond/covid-green-app/issues/49#event-3715461463, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQYJBUFQLNDP6ZZ5YIFZJX3SDUFV5ANCNFSM4QJAVZWQ.

Removing from Launch until we have a business decision on whether this is needed for launch or not. I suspect not at this poitn.

Closing since this is of limited value at this point.


test: upgrade cri e2e test to v1.12

Signed-off-by: zhuangqh<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
The interface of pouch-cri has upgraded to kubernetes 1.12. we upgrade the e2e test together.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

The latest version is already 1.13, and we support it already, so shall we upgrade to version 1.13? WDYT?

The latest version is already 1.13, and we support it already, so shall
we upgrade to version 1.13? WDYT?

We just updated to the 1.12. I think we can make upgrade plan like
golang’s. I mean that we don’t need to chase the fresh latest version. We
can run 1.12 for a while. Then we upgrade to 1.13 when it becomes more
stable.

The latest version is already 1.13, and we support it already, so shall
we upgrade to version 1.13? WDYT? We just updated to the 1.12. I think we can make upgrade plan like golang’s. I mean that we don’t need to chase the fresh latest version. We can run 1.12 for a while. Then we upgrade to 1.13 when it becomes more stable.

agree with you. track with the stable version is enough.

• Failure [25.464 seconds]
[k8s.io] Variable Expansion
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:694
should allow substituting values in a volume subpath [Feature:VolumeSubpathEnvExpansion][NodeAlphaFeature:VolumeSubpathEnvExpansion] [It]
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/expansion.go:157
Expected error:
<*errors.errorString | 0xc4202a7720>: {
s: "expected "0" in container output: Expected\n    : 1\n    \nto contain substring\n    : 0",
}
expected "0" in container output: Expected
: 1
  to contain substring
      <string>: 0

not to have occurred
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2350

• [SLOW TEST:309.867 seconds]
[k8s.io] Container Runtime
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:694
blackbox test
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/runtime.go:37
when running a container with a new image
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/runtime.go:235
should not be able to pull from private registry without secret [NodeConformance]
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/runtime.go:299
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

• [SLOW TEST:309.867 seconds]
[k8s.io] Container Runtime
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:694
blackbox test
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/runtime.go:37
when running a container with a new image
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/runtime.go:235
should not be able to pull from private registry without secret [NodeConformance]
/home/travis/gopath/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/runtime.go:299
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

any update?


Partner Rentality: info update

Partner Rentality: changed link, icon, tag  and description

Is there anything else required on our part? Or just wait?


this.http.post() requires data to be JSON.stringified?

Is this correct or am I doing something wrong?
If I call this.http.post(path, data) it does not send as application/json, I have to instead do this.http.post(path, JSON.stringify(data))

    this.http = http.configure(x => {
      x.withHeader('Content-Type', 'application/json');
      //x.withCredentials(true);
    });

This fixes, wasn't sure if that was standard or a bug. It seems #39 is already open so I'm closing this.


Fix Qiskit BibTeX link in README

Summary
Follows qiskit-community/qiskit-optimization#555
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2649

Relevant Lines:
2851

💛  - Coveralls


iOS: setCollectionEnabled() and setSessionTimeoutDuration() never resolve

Describe the bug
The setCollectionEnabled() and setSessionTimeoutDuration() iOS functions never resolve, and using them with await effectively halts further typescript code execution.
To Reproduce
Steps to reproduce the behavior:
When enabling firebase analytics collection in your app, use await to trigger this issue:
...
await FirebaseAnalytics.setCollectionEnabled({ enabled: true });
...

Expected behavior
FirebaseAnalytics.setCollectionEnabled() should either resolve or reject.
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
iOS
Additional context
Currently working on a PR for this

Looks like this is an issue for setUserId() in android as well... updating PR


Add small note on cache.clear + testing in the Readme

I know this is a newer feature but it took me some digging to find it. cache.clear() works like a charm!

@sergiodxa yep, thanks for mentioning that I actually had to go back to my app and add that as well

Updated!

Ran into this again! Would love to see it in the readme, anything left for me to do?

Hi there, I'm facing the same issue.
However cache.clear() isn't fixing the problem at least with SWR 0.2.2
I create an example here: https://codesandbox.io/s/frosty-butterfly-y295j?file=/src/swr.spec.js
The only current workaround is using different keys between the tests. Which is actually what it's done in SWR itself: https://github.com/vercel/swr/blob/master/test/use-swr.test.tsx
Is this a known issue?
btw. I love this lib thank you for your hard work.

@aboutlo you need to also wrap your rendered component in SWRConfig and set the dedupingInterval to zero, otherwise SWR will reuse the promises of the previous test and refill the cache with the same data.

@sergiodxa gotcha! this has fixed the problem and helped me to understand another bit of SWR magic 🙏
For anyone else who could have a similar issue dedupingInterval:0 can be passed directly to useSWR without having SWRConfig as a wrapper.
const { data } = useSWR(["/something"], {
    fetcher,
    dedupingInterval:0
});

I don’t recommend you to pass it to useSWR directly, in production you want to have it enabled, that is why SWRConfig allow you to replace it in the test.

Of course, not for production, I was stuck just with a test :)

Is there a way to allow setting dedupingInterval globally in tests?
The example in readme won't work if AppComponent renders SWRConfig internally (which happens in the component I wish to test).
Let me know if you want me to open a new issue for it.
BTW - love your work! It's super helpful :pray:

Thanks for all your discussions and contributions here! With 1.0 we finalized the new cache API, and a better way to test: https://swr.vercel.app/docs/advanced/cache#reset-cache-between-test-cases.

Thanks for following up!
I use Cypress to do black-box testing rather than shallow mounting, so I'll still need to import + call cache.clear(). Should this be okay in concurrent React? Maybe worth mentioning as lots of folks use Cypress or something like it.

Thanks for the feedback! Yeah, in that case it makes sense to clear the global cache from outside of the React tree. I think we will need a dedicated “Testing” page in the docs soon, and currently it can be achieved by this (since the exported cache was gone):
import { SWRConfig } from 'swr'

SWRConfig.default.cache.clear()

We will make sure to put this in the docs (we also removed all the docs in the readme so we don’t have to maintain two places) :)


Adds SNES core with ALTTP

This adds a SNES 9x core and the WIP game-data for Zelda: alttp

Sorry, but we're not accepting this type of PR at the time.

Could you be more specific, please?
Is the issue the SNES core, the LTTP data, or both?


Add stable API version for Azure Policy to support non-compliance messages

Feature Request
Please can we add either of the following stable API versions for services/resources/mgmt to support Azure Policy non-compliance messages. Currently these only exist in the SDK as preview.
For use in the Terraform provider, where the preference is to use stable API versions as opposed to preview.
Stable policy versions supporting non-compliance messages are:

2020-09-01
2021-06-01

Related issues

#16109

@matt-FFFFFF package-2020-09-01 and package-2021-06-01 are both preview versions, I did not find a stable version about them

Thanks for looking. Those API versions work when I do a GET request to the RPs. Is there another dependency that you need that isn't available?

@matt-FFFFFF, the reason we release preview SDK is that the package definition contains preview freatures https://github.com/Azure/azure-rest-api-specs/blob/main/specification/resources/resource-manager/readme.md#tag-package-policy-2021-06
We will release stable version when the APIs defined in Microsoft.Authorization/preview/2020-07-01-preview/policyExemptions.json become stable.

No problem. Thanks for looking into it!

Close this item as there is no further action on the SDK side. We are waiting for a stable api version for SDK generation

@lirenhe where is that request tracked?

I created https://github.com/Azure/azure-rest-api-specs/issues/17376 to track the request.


Support NPM 7 and later and upgrade NodeJS in the Docker image from 14 to 17

Address #916:

Update NodeJS to version 17 (the last one supported on Ubuntu 18.04 - once you upgrade to 22.04 we can bump this to 18 to be on an LTS version again)
Add support for the --all flag that is needed to list transitive dependencies on NPM version 7 and later

Unfortunately, this needs more work. With NPM 7 and later, the output of npm list no longer includes the entire package.json information for the dependencies, in particular not the license field. This can be observed with e.g. the package<EMAIL_ADDRESS>This means that the activations_from_spec is empty and only activations_from_files could fill in the license.
We'll probably have to read the spec information from the package.json file that dependencies.entities.path points to.
For reference, here is what we get from npm list --json --long --all (hand-edited the output to remove other dependencies):
NPM 8.5.5, detected as entities, 4.4.0, unknown, output:
{
  "name": "my_app",
  "extraneous": false,
  "path": "/tmp/projects/my_app",
  "_dependencies": {
    "http-server": "0.11.1",
    "entities": "4.4.0"
  },
  "devDependencies": {},
  "peerDependencies": {},
  "dependencies": {
    "entities": {
      "version": "4.4.0",
      "resolved": "https://registry.npmjs.org/entities/-/entities-4.4.0.tgz",
      "name": "entities",
      "integrity": "sha512-oYp7156SP8LkeGD0GF85ad1X9Ai79WtRsZ2gxJqtBuzH+98YUV6jkHEKlZkMbcrjJjIVJNIDP/3WL9wQkoPbWA==",
      "engines": {
        "node": ">=0.12"
      },
      "funding": {
        "url": "https://github.com/fb55/entities?sponsor=1"
      },
      "_id"<EMAIL_ADDRESS>      "extraneous": false,
      "path": "/tmp/projects/my_app/node_modules/entities",
      "_dependencies": {},
      "devDependencies": {},
      "peerDependencies": {}
    }
  }
}

NPM 6.4.17, detected as entities, 4.4.0, "Simplified BSD", output:
{
  "dependencies": {
    "entities": {
      "_from"<EMAIL_ADDRESS>      "_id"<EMAIL_ADDRESS>      "_integrity": "sha512-oYp7156SP8LkeGD0GF85ad1X9Ai79WtRsZ2gxJqtBuzH+98YUV6jkHEKlZkMbcrjJjIVJNIDP/3WL9wQkoPbWA==",
      "_location": "/entities",
      "_phantomChildren": {},
      "_requested": {
        "type": "version",
        "registry": true,
        "raw"<EMAIL_ADDRESS>        "name": "entities",
        "escapedName": "entities",
        "rawSpec": "4.4.0",
        "saveSpec": null,
        "fetchSpec": "4.4.0"
      },
      "_requiredBy": [
        "/"
      ],
      "_resolved": "https://registry.npmjs.org/entities/-/entities-4.4.0.tgz",
      "_shasum": "97bdaba170339446495e653cfd2db78962900174",
      "_spec": "4.4.0",
      "_where": "/tmp/projects/my_app",
      "author": {
        "name": "Felix Boehm",
        "email"<EMAIL_ADDRESS>      },
      "bugs": {
        "url": "https://github.com/fb55/entities/issues"
      },
      "deprecated": false,
      "description": "Encode & decode XML and HTML entities with ease & speed",
      "devDependencies": {
        "@types/jest": "^28.1.8",
        "@types/node": "^18.7.14",
        "@typescript-eslint/eslint-plugin": "^5.36.1",
        "@typescript-eslint/parser": "^5.36.1",
        "eslint": "^8.23.0",
        "eslint-config-prettier": "^8.5.0",
        "eslint-plugin-node": "^11.1.0",
        "jest": "^28.1.3",
        "prettier": "^2.7.1",
        "ts-jest": "^28.0.8",
        "typedoc": "^0.23.12",
        "typescript": "^4.8.2"
      },
      "directories": {
        "lib": "lib/"
      },
      "engines": {
        "node": ">=0.12"
      },
      "exports": {
        ".": {
          "require": "./lib/index.js",
          "import": "./lib/esm/index.js"
        },
        "./lib/decode.js": {
          "require": "./lib/decode.js",
          "import": "./lib/esm/decode.js"
        },
        "./lib/escape.js": {
          "require": "./lib/escape.js",
          "import": "./lib/esm/escape.js"
        }
      },
      "files": [
        "lib/**/*"
      ],
      "funding": "https://github.com/fb55/entities?sponsor=1",
      "homepage": "https://github.com/fb55/entities#readme",
      "jest": {
        "preset": "ts-jest",
        "coverageProvider": "v8",
        "moduleNameMapper": {
          "^(.*)\\.js$": "$1"
        }
      },
      "keywords": [
        "entity",
        "decoding",
        "encoding",
        "html",
        "xml",
        "html entities"
      ],
      "license": "BSD-2-Clause",
      "main": "lib/index.js",
      "module": "lib/esm/index.js",
      "name": "entities",
      "prettier": {
        "tabWidth": 4,
        "proseWrap": "always"
      },
      "repository": {
        "type": "git",
        "url": "git://github.com/fb55/entities.git"
      },
      "scripts": {
        "build": "npm run build:cjs && npm run build:esm",
        "build:cjs": "tsc --sourceRoot https://raw.githubusercontent.com/fb55/entities/$(git rev-parse HEAD)/src/",
        "build:docs": "typedoc --hideGenerator src/index.ts",
        "build:encode-trie": "ts-node scripts/write-encode-map.ts",
        "build:esm": "npm run build:cjs -- --module esnext --target es2019 --outDir lib/esm && echo '{\"type\":\"module\"}' > lib/esm/package.json",
        "build:trie": "ts-node scripts/write-decode-map.ts",
        "format": "npm run format:es && npm run format:prettier",
        "format:es": "npm run lint:es -- --fix",
        "format:prettier": "npm run prettier -- --write",
        "lint": "npm run lint:es && npm run lint:prettier",
        "lint:es": "eslint .",
        "lint:prettier": "npm run prettier -- --check",
        "prepare": "npm run build",
        "prettier": "prettier '**/*.{ts,md,json,yml}'",
        "test": "npm run test:jest && npm run lint",
        "test:jest": "jest"
      },
      "sideEffects": false,
      "types": "lib/index.d.ts",
      "version": "4.4.0",
      "readme": "# entities [![NPM version](http://img.shields.io/npm/v/entities.svg)](https://npmjs.org/package/entities) [![Downloads](https://img.shields.io/npm/dm/entities.svg)](https://npmjs.org/package/entities) [![Build Status](http://img.shields.io/travis/fb55/entities.svg)](http://travis-ci.org/fb55/entities) [![Coverage](http://img.shields.io/coveralls/fb55/entities.svg)](https://coveralls.io/r/fb55/entities)\n\nEncode & decode HTML & XML entities with ease & speed.\n\n## Features\n\n-   😇 Tried and true: `entities` is used by many popular libraries; eg.\n    [`htmlparser2`](https://github.com/fb55/htmlparser2), the official\n    [AWS SDK](https://github.com/aws/aws-sdk-js-v3) and\n    [`commonmark`](https://github.com/commonmark/commonmark.js) use it to\n    process HTML entities.\n-   ⚡ Fast: `entities` is the fastes library for decoding HTML entities (as of\n    April 2022); see [performance](#performance).\n-   🎛 Configurable: Get an output tailored for your needs. You are fine with\n    UTF8? That'll safe you some bytes. Prefer to only have ASCII characters? We\n    can do that as well!\n\n## How to…\n\n### …install `entities`\n\n    npm install entities\n\n### …use `entities`\n\n```javascript\nconst entities = require(\"entities\");\n\n// Encoding\nentities.escapeUTF8(\"& ü\"); // \"&#38; ü\"\nentities.encodeXML(\"& ü\"); // \"&#38; ü\"\nentities.encodeHTML(\"& ü\"); // \"&#38; ü\"\n\n// Decoding\nentities.decodeXML(\"asdf & ÿ ü '\"); // \"asdf & ÿ ü '\"\nentities.decodeHTML(\"asdf & ÿ ü '\"); // \"asdf & ÿ ü '\"\n```\n\n## Performance\n\nThis is how `entities` compares to other libraries on a very basic benchmark\n(see `scripts/benchmark.ts`, for 10,000,000 iterations; **lower is better**):\n\n| Library        | Version | `decode` perf | `encode` perf | `escape` perf |\n| -------------- | ------- | ------------- | ------------- | ------------- |\n| entities       | `3.0.1` | 1.418s        | 6.786s        | 2.196s        |\n| html-entities  | `2.3.2` | 2.530s        | 6.829s        | 2.415s        |\n| he             | `1.2.0` | 5.800s        | 24.237s       | 3.624s        |\n| parse-entities | `3.0.0` | 9.660s        | N/A           | N/A           |\n\n---\n\n## FAQ\n\n> What methods should I actually use to encode my documents?\n\nIf your target supports UTF-8, the `escapeUTF8` method is going to be your best\nchoice. Otherwise, use either `encodeHTML` or `encodeXML` based on whether\nyou're dealing with an HTML or an XML document.\n\nYou can have a look at the options for the `encode` and `decode` methods to see\neverything you can configure.\n\n> When should I use strict decoding?\n\nWhen strict decoding, entities not terminated with a semicolon will be ignored.\nThis is helpful for decoding entities in legacy environments.\n\n> Why should I use `entities` instead of alternative modules?\n\nAs of April 2022, `entities` is a bit faster than other modules. Still, this is\nnot a very differentiated space and other modules can catch up.\n\n**More importantly**, you might already have `entities` in your dependency graph\n(as a dependency of eg. `cheerio`, or `htmlparser2`), and including it directly\nmight not even increase your bundle size. The same is true for other entity\nlibraries, so have a look through your `node_modules` directory!\n\n> Does `entities` support tree shaking?\n\nYes! `entities` ships as both a CommonJS and a ES module. Note that for best\nresults, you should not use the `encode` and `decode` functions, as they wrap\naround a number of other functions, all of which will remain in the bundle.\nInstead, use the functions that you need directly.\n\n---\n\n## Acknowledgements\n\nThis libary wouldn't be possible without the work of these individuals. Thanks\nto\n\n-   [@mathiasbynens](https://github.com/mathiasbynens) for his explanations\n    about character encodings, and his library `he`, which was one of the\n    inspirations for `entities`\n-   [@inikulin](https://github.com/inikulin) for his work on optimized tries for\n    decoding HTML entities for the `parse5` project\n-   [@mdevils](https://github.com/mdevils) for taking on the challenge of\n    producing a quick entity library with his `html-entities` library.\n    `entities` would be quite a bit slower if there wasn't any competition.\n    Right now `entities` is on top, but we'll see how long that lasts!\n\n---\n\nLicense: BSD-2-Clause\n\n## Security contact information\n\nTo report a security vulnerability, please use the\n[Tidelift security contact](https://tidelift.com/security). Tidelift will\ncoordinate the fix and disclosure.\n\n## `entities` for enterprise\n\nAvailable as part of the Tidelift Subscription\n\nThe maintainers of `entities` and thousands of other packages are working with\nTidelift to deliver commercial support and maintenance for the open source\ndependencies you use to build your applications. Save time, reduce risk, and\nimprove code health, while paying the maintainers of the exact dependencies you\nuse.\n[Learn more.](https://tidelift.com/subscription/pkg/npm-entities?utm_source=npm-entities&utm_medium=referral&utm_campaign=enterprise&utm_term=repo)\n",
      "readmeFilename": "readme.md",
      "_args": [
        [
<EMAIL_ADDRESS>          "/tmp/projects/my_app"
        ]
      ],
      "dependencies": {},
      "optionalDependencies": {},
      "_dependencies": {},
      "path": "/tmp/projects/my_app/node_modules/entities",
      "error": "[Circular]",
      "extraneous": false
    }
  },
  "name": "",
  "version": "",
  "readme": "ERROR: No README data found!",
  "_shrinkwrap": {
    "requires": true,
    "lockfileVersion": 1,
    "dependencies": {
      "entities": {
        "version": "4.4.0",
        "resolved": "https://registry.npmjs.org/entities/-/entities-4.4.0.tgz",
        "integrity": "sha512-oYp7156SP8LkeGD0GF85ad1X9Ai79WtRsZ2gxJqtBuzH+98YUV6jkHEKlZkMbcrjJjIVJNIDP/3WL9wQkoPbWA=="
      }
    }
  },
  "devDependencies": {},
  "optionalDependencies": {},
  "_dependencies": {
    "entities": "4.4.0"
  },
  "path": "/tmp/projects/my_app",
  "error": "[Circular]",
  "extraneous": false
}

The latest version should fix the issue I mentioned above by also reading a dependency's package.json file. We actually use both sources now because:

npm list has both the runtime and the development dependencies combined, whereas package.json would require extra code to read both dependencies and devDependencies.
npm list has the path property that tells us where to find a dependency's package.json.
package.json has all the other information that is missing in npm list since version 7.

With this image, it looks like I get the same information extracted as before with NPM 6 (I will do a more thorough comparison soon).
With one caveat. Now the homepage field is missing for many packages. I don't know what NPM was doing, I suspect it was building these package.json files in node_modules by adding in information from the NPM registry, because for the packages where it's missing, the package.json file simply does not contain the URL.
The package<EMAIL_ADDRESS>is an example for this.
[1] https://github.com/brianloveswords/base64url/blob/v3.0.1/package.json does not contain the homepage URL.
[2] https://www.npmjs.com/package/base64url has the URL on the right.
With this package.json
{
  "name": "test",
  "version": "1.0.0",
  "dependencies": {
    "base64url": "3.0.1"
  }
}

and Node 18 / NPM 8 we don't get the field in the npm list output, and the file node_modules/base64url/package.json is the one from [1], unchanged:
❯ docker run -v $(pwd)/package.json:/scan/package.json -it node:18 bash -cl 'cd /scan && npm install && npm list --json --long --all --production'
{
  "version": "1.0.0",
  "name": "test",
  "_id"<EMAIL_ADDRESS>  "extraneous": false,
  "path": "/scan",
  "_dependencies": {
    "base64url": "3.0.1"
  },
  "devDependencies": {},
  "peerDependencies": {},
  "dependencies": {
    "base64url": {
      "version": "3.0.1",
      "resolved": "https://registry.npmjs.org/base64url/-/base64url-3.0.1.tgz",
      "overridden": false,
      "name": "base64url",
      "integrity": "sha512-ir1UPr3dkwexU7FdV8qBBbNDRUhMmIekYMFZfi+C/sLNnRESKPl23nB9b2pltqfOQNnGzsDdId90AEtG5tCx4A==",
      "engines": {
        "node": ">=6.0.0"
      },
      "_id"<EMAIL_ADDRESS>      "extraneous": false,
      "path": "/scan/node_modules/base64url",
      "_dependencies": {},
      "devDependencies": {},
      "peerDependencies": {}
    }
  }
}

With Node 14 / NPM 6, on the other hand, we get the homepage field in the npm list output, and node_modules/base64url/package.json is very different from [1], and also includes the homepage.
docker run -v $(pwd)/package.json:/scan/package.json -it node:14 bash -cl 'cd /scan && npm install && npm list --json --long --all --production'
{
  "name": "test",
  "version": "1.0.0",
  "dependencies": {
    "base64url": {
      ...
      "homepage": "https://github.com/brianloveswords/base64url#readme",
      ...
    }
  },
  ...
}

Does anybody know how to get the homepage field? Does it work with yarn? Does it change the package.json files like NPM 6 did?

Should we maybe extract the repository.url in addition to the homepage? For some licenses that require you to make the source code available, the repository URL would be even better - but it's not necessarily one that you can open in a web browser. E.g. it will be like git://github.com/brianloveswords/base64url.git.

Sorry, why do you  need the homepage? Are you planning to use it for something? In pnpm package manager we read each package.json to extract this data. Only not all packages have this field populated

I don't really need it. I was just trying to avoid a regression in functionality when updating NodeJS. But it seems the other package manager implementations don't extract these fields, either, so we should be fine. If the maintainers are fine with this pull request, we can merge it as it is.
Here's the comparison of the three NPM flavors:
NPM 6 / Node 14
docker run -t licensefinder/license_finder /bin/bash -lc 'mkdir /scan && cd /scan && npm init -y && npm i<EMAIL_ADDRESS>&& license_finder --columns name license homepage authors --format json'

{
	"dependencies": [{
		"name": "base64url",
		"homepage": "https://github.com/brianloveswords/base64url#readme",
		"authors": "Brian J Brennan"
	}, {
		"name": "scan",
		"homepage": "",
		"authors": ""
	}]
}

New NPM (this PR):
{
	"dependencies": [{
		"name": "base64url",
		"homepage": "",
		"authors": "Brian J Brennan"
	}, {
		"name": "scan",
		"homepage": "",
		"authors": ""
	}]
}

PNPM
docker run -t licensefinder/license_finder /bin/bash -lc 'mkdir /scan && cd /scan && pnpm init && pnpm add<EMAIL_ADDRESS>&& license_finder --columns name license homepage authors --format json'

{
	"dependencies": [{
		"name": "base64url",
		"homepage": "",
		"authors": ""
	}]
}

YARN
docker run -t licensefinder/license_finder /bin/bash -lc 'mkdir /scan && cd /scan && yarn init -y && yarn add<EMAIL_ADDRESS>&& license_finder --columns name license homepage authors --format json'

{
	"dependencies": [{
		"name": "base64url",
		"homepage": "Unknown",
		"authors": "Brian J Brennan"
	}]
}

I thought I was extracting those fields for pnpm but maybe I am imagining it. I will have a look and revisit it on the pnpm side of things.
But this PR looks fine to me and great that it resolves some of the v7+ issues I was experiencing over the weekend

@xtreme-shane-lattanzio it's been a while without a release, and I was wondering if we can move this forward :-)

Hey @rhuitl ! My attention has been diverted from this for a while but I am looking to catch up on things over this month. Thanks for the PRs. I will work look things over soon and let you know if there are any issues!

@rhuitl It looks like the homepage missing is less of an issue than the docker image now failing due to npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":">=16.14"} (current: {"node":"14.21.3","npm":"6.14.18"}) so I am inclined to merge this. However, we do use the homepage to populate information that can be sent to a legal team to double check dependencies. Is there no way to get it?
I also merged another dockerfile PR so there are now some conflicts here that need to be cleaned up. Thanks again!

Hey @rhuitl Thanks for rebasing this. Tests are good now. Do you think it is better to just merge this with blank homepages in later versions? Is there no way to get the homepage?

I did a quick check if --legacy-* options (found only two) would change this behavior but they do not. I don't know where older NPM versions pulled the homepage field from, I assume it must have been the NPM registry.
Maybe we can fill in missing info like this by querying the registry ourself, but I have not looked into this. Or, because we regularly encounter packages where some detail is missing  (e.g. license text) I was wondering if LicenseFinder has or could have a generic way to provide additional information (e.g. in dependency_decisions.yml).
I suggest to merge it as it is, and if you only have a handful of packages that are missing the "homepage" field, the authors could be contacted to put this information into their package.json files.


Fix npm use webpack

Hello @RSO @martijnrusschen
This a big PR to make the lib compatible with module loaders, like in CommonJS in node. (Should fix https://github.com/Hacker0x01/react-datepicker/issues/88)
Notables changes

Builded files are now in /dist directory (updated paths references in package.json and bower.json)
Added minified builds too (react-datepicker.min.css and react-datepicker.min.js)
Changed the whole build process with webpack (http://webpack.github.io/)

All changes

Use of webpack instead of browserify (http://webpack.github.io/)
Use of babel-jest for preprocessor into tests
Use of babel-loader for JSX preprocessor into build
Remove browserify, reactify, browserify-shim...
Remove /** @jsx React.DOM **/ since it's deprecated (dups of PR https://github.com/Hacker0x01/react-datepicker/pull/86)
Fix global var leak (dups of PR https://github.com/Hacker0x01/react-datepicker/pull/87)
Add $ grunt webpack:(min | unmin | example) for JSX building files
Add $ grunt sass:(min | unmin) for building styles files

Next?
Remove Tether dep to make the lib isomorphic, at this state we can't run it on the server.
Best regards, Maxime.

Thanks for this, it's a lot to take in at once, but I hope to do a first run through the PR's today, and get some real work done in this repository tomorrow!

Could you elaborate as to why we need webpack in favour of browserify to solve this issue? (a link/whatever would be fine as well)

I've tried to have a same build for browser and node with browserify, couldn't achieve it. Mainly because of this:
With webpack, you can define externals namespaces for every use (amd, commonjs & browser):
{
      'react/addons': {
        root: 'React',
        commonjs2: 'react',
        commonjs: 'react',
        amd: 'react'
      }
    },
    {
      'moment': {
        root: 'moment',
        commonjs2: 'moment',
        commonjs: 'moment',
        amd: 'moment'
      }
    },
    {
      'react-onclickoutside': {
          root: 'OnClickOutside',
          commonjs2: 'react-onclickoutside',
          commonjs: 'react-onclickoutside',
          amd: 'react-onclickoutside'
      }
    }

With browserify and browserify-shim it wasn't enough, since react/addons and react-onclickoutside have different namespaces depending on environment. Actual:
"browserify-shim": {
    "react/addons": "global:React",
    "moment": "global:moment",
    "react-onclickoutside": "global:OnClickOutside"
  },

If you find something for browserify, I'm happy to give it another shot but I lost almost a day wrapping my head around this issue :)

Cool! Yeah, this is my first project with both browserify and webpack, so I just wasn't sure about all the pros/cons. Thanks again for taking the time to fix this, I'll check it out and see what I can do. Would you mind if I'd try to split this PR up in multiple PRs? I'm unsure if it's needed, but it might help me get an understanding of the whole situation and fixing #88 sooner.

Sure,
First you can merge https://github.com/Hacker0x01/react-datepicker/pull/86 and https://github.com/Hacker0x01/react-datepicker/pull/87 which are included into my PR, I needed them.
Then I will rebase and try to breakdown things.

I just tested this and everything looks good. I landed the other PR's, so you should be able to rebase this PR.
When I run grunt build my react-datepicker.min.js file changes, is it outdated, or are we running different versions of the dependencies?
Webpack seems interesting, shouldn't we also be able to drop SCSS compilation out of the gruntfile and let webpack handle it?

@iam4x any idea when this can be merged?

I'll see if I can find the time to continue work on this later this week. Sorry for the delay!

No pressure, but I'd also love to see this PR merged. =)

Damn, dat pressure ;) I'm feeling confident that I'll have time to work on this tonight! Just sit tight!

We :heart: you @RSO ! We're on your time.

I'll have some time tomorrow to review and rebase my branch :+1:

What is the status of this merge? As well as updating the package to work with React 0.13? Can these PRs be merged?

Merged through #93. Thank you so much for the help! And the patience ;-). I'll get a new release out today!

:heart:


Shortcut Guide Update: Move Active Window (multi screen only)

Summary of the new feature/enhancement
Adding the function Windows Key + Shift + Left/Right Arrow key to the shortcut list. This moves the active window between each screen in a multi-screen setup

Proposed technical implementation details (optional)'

This is tracked in #607. We have a pull request that enables this but it still have things that need to be shifted to work correctly. Namely the taskbar icons.


Wireframe for 2D meshes

What problem does this solve or what need does it fill?
It could be useful to debug the mesh generation for 2D objects.
What solution would you like?
Support the same interface as 3D.
What alternative(s) have you considered?
Just draw the triangles yourself with bevy_prototype_lyon or some other vector framework.
Additional context
I've been looking over the code of the wireframe plugin, and yolo replaced the Opaque3D with Transparent2d but that just crashes with a long error. My knowledge of the rendering framework is very limited so don't know what else to try.

I've had a working implementation of this since last year, here's a gist: https://gist.github.com/SludgePhD/e26753b9fbcb9b9d274f5dad3e3f662a


SPICE Amino Acid Ligand v1.0 54X VAL has no coordinates

While trying to extract the conformations of molecules from the Amino Acid Ligand subset for training, I found that 54X_VAL has empty coordinates. Is this expected?
import h5py

with h5py.File("./SPICE-2.0.1.hdf5", "r") as f:
    for key, val in f.items():
        molecule_name = key.replace(" ", "_")
        if molecule_name == "54X_VAL":
            coordinates = val["conformations"][:]
            print(coordinates.shape)

(0,)

Yes, that's an artifact of how the downloader script is written.  There was only one conformation for that dimer, and it was excluded due to a force being above the cutoff, leaving a record with no conformations at all.


very small change

Just append a new empty line at the end of the file. This is just for testing.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Get Canvas' font size

no need to use our own font size...
We can just get the actual canvas' font size
for investigating, here's dialog_font.tcl
    if {[winfo exists ${mytoplevel}.text]} {
        set font [lindex [${mytoplevel}.text.internal cget -font] 0]
        if { ${font} eq {} } {
            set font $::font_family
        }
        ${mytoplevel}.text.internal configure -font [list $font $myfontsize]
    }

but don;t get pdwindow's size and the actual patch size

i cannot parse this sentence.

I see "patcherize" comes with compiled objects, is it for a similar reason?

what similar reasons? patcherize does heavy work on the Pd-core side. the GUI plugin is just a minimal shim to add the menu entry and to auto-load the patcherize external.

@umlaeute,  there's a setting for the font size in the completion-plugin, but it could just use the canvas' fontsize - with "glist_getfont()".
This information doesn't seem to be retrievable on the tcl/tk side of Pd, I wonder if I have to do something like patcherize and offer an external just to get the font size...

there currently is no way to directly query the font-size or a patch on the GUI side. (just check out the code for the font-dialog (or even simpler: the messages that go between Pd-core and Pd-GUI).
do you really need to know the font-size? or is it just eye-candy?
because an architecture-independent external is significantly better than a compiled external.

I think I need it. Otherwise the settings need to be manually changed whenever you change font size or work on vc a patch of different font size...

but what for? so that things align nicely? is this something "nice-to-have" or something without which the completion-plugin will not work?

The plug-in offers this font size In-N-Out's settings , but is kinda meaningless to me as you can't know what will work. It's like if pd had a font size settings for objects that needed to be changed to match patch font size.
This is surely nice to have and we use font size for added gui boxes and iemguis...
Right now it's just bad design and user experience

Right now it's just bad design and user experience

what? having the drop-down displayed at a font-size of 12 when the patch uses a font-size of 14?
in any case, what I find it much worse UX, that there are weird suggestions like plugin::rescan and plugin::debug which i have never heard about. (obviously they are no autocompletion suggestions at all, but instead allow me to access some settings of the completion-plugin; but they look identical to ordinary suggestions even though they are not). and that right between /~ and < there are some numbers (they obviously got there because of string sorting; but they look strangely out of place).
for the first issue you might just want to add a menu-entry rather than have it in the suggestions.
(this is with 0.48.0, as 0.49.0 is broken for me (see #22).

I agree and had already removed rescan/debug

sorry, I was on the phone...

what? having the drop-down displayed at a font-size of 12 when the patch uses a font-size of 14?

yup, and not only this, but specially having to adapt and set it accordingly to something that is set somewhere else that you shouldn't have to set, just grab the information from the canvas...
but I see it isn't easily available from the tcl/tk side, unless we include changes to the core.

right between /~ and < there are some numbers (they obviously got there because of string sorting; but they look strangely out of place).

sorry, i did not understand what you meant by this

but I see it isn't easily available from the tcl/tk side, unless we include changes to the core.

Just to make sure: I think it if course desirable that the completion plugin users the same don't suppose as the surrounding patch.
However, as you discovered, there is currently no way to get this font-size without writing an external.
And I think the drawbacks of introducing a arch-dependent binary to get this functionality heavily outweighs the nicety of having automatic font sizes

I wonder if one could use some kind of search to get the font metrics of some existing text in a canvas..
course, it wouldn't work w/ canvasses without any text yet..

there already is a text object: the one you want to autocomplete (it's empty, but it is there)

the drawbacks of introducing a arch-dependent binary to get this functionality heavily outweighs the nicety of having automatic font sizes

I see, well, I wonder then how crazy would it be to change the Pd core a bit so this easily obtainable...

I wonder if one could use some kind of search to get the font metrics of some existing text in a canvas...

or this or some other magic.

right between /~ and < there are some numbers (they obviously got there because of string sorting; but they look strangely out of place).

sorry, i did not understand what you meant by this

but i now see that this came from custom_completions/custom_completions.txt https://github.com/porres/completion-plugin/blob/f4d58722238a95d32108b48f8c61ffff2e13f788/custom_completions/custom_completions.txt#L27-L33 and has been removed from the 0.49 release (which i wasn't able to test, due to #22; as of 0.49.1 thus problem has been solved)

I wonder if one could use some kind of search to get the font metrics of some existing text in a canvas...

or this or some other magic.

that looks actually pretty trivial to me.
you already get the current text with https://github.com/porres/completion-plugin/blob/38fe89fc33242c6de604fac58497793640aeecc6/completion-plugin.tcl#L722
you can also get the exact font specification with a very similar command:
set font [$::current_canvas itemcget $::current_tag -font]

then you don't need to hard-code "Menlo" or "12" or discard the "bold" face

thanks, works like a charm :)

you're welcome.
however , https://github.com/porres/completion-plugin/commit/5f21936813d388a28a4d2aed93314063dc7daa0c ignores any -font-face and -font-weight options.
why?

well, it's not like the plugin did allow us to set font face and weight before :)  but I get it, we can retrieve them as well and use it --> https://github.com/porres/completion-plugin/issues/26

well, it's not like the plugin did allow us to set font face and weight before

i didn't say it was a regression.
but i said:

then you don't need to hard-code "Menlo" or "12" or discard the "bold" face

:-)

question, when someone changes pd's font to something funny or whatever, do all menus follow suit? Should I query which font is Pd running on to adopt into the 'completion' settings entry?

No I don't think so. TCL/tk generally leaves that stuff too the window manager I believe

Imo it would be cool if this were an option - the user either chooses a font size or you can 'use patch font'

question, when someone changes pd's font to something funny or whatever, do all menus follow suit?

No they don't.
Instead, they are governed by font setting of the Pd-console.

Should I query which font is Pd running on to adopt into the 'completion' settings entry?

Maybe, but...
this issue was about getting the font-size of the current canvas, in order for the completion pulldown to adjust to it.
Now the only reason I can see why you want this is, because you want the pulldown to appear consistent with the other objects in the patch, rather than with the menu or the Pd-console.
In this vein I suggested, that you should not only ensure that the font size matches the current canvas, but also the other font properties, like weight and face.
If you want to match the general menus instead, you should use the font specs of the menus (as found eg in the Pd-console text field. there's probably a variable for that, but I'm currently afk)
I don't think you should ever hardcode a specific font (or worse: two) if you want to have a consistent appearance with Pd.

Imo it would be cool if this were an option - the user either chooses a font size or you can 'use patch font'

Out of interest: what would be the use case? (We could of course add options for the font colour and the spacing and the number of colons and what not, but is this a service to the user?)

i wouldn't be a Pd guy if I wasn't fond of the KISS principle (Keep it Simple, Stupid)

Well I agree w/ KISS design in the core but idk about plugins..
Perhaps in this case it would be best to put the 'get font properties' in a separate function that a user could easily overwrite in a personal *-plugin.tcl file. That way the plugin is simple but easily modifiable

Perhaps in this case it would be best to put the 'get font properties' in a separate proc that a user could easily overwrite in a personal *-plugin.tcl file.

send me a PR
as for the properties, they're almost completely vanished, now that I see that a shortcut for adding the library prefix is already implemented (did I proposed the that years ago? what a coincidence), we're left with the hotkey only... which could be hardcoded and documented...