Expose all Vaadin plugin Maven goals

Now that we create the Hilla Maven Plugin in our repo, only the Vaadin Plugin goals that are explicitly extended are availabe.
Let's support all the Vaadin goals, not only the most important ones.

At the moment, there are five goals in Vaadin plugin:

prepare-frontend
build-frontend
clean-frontend
convert-polymer
dance

and vaadinPrepareFrontend and vaadinBuildFrontend are already adopted in the hilla-maven-plugin.
Since, vaadinConvertPolymer does not seem to be relevant for Hilla projects explicitly, it is not a candidate to be exposed under hilla-maven-plugin IMO.
Then, the dance and clean-frontend tasks are also up for debate IMO, as they delete package-lock.json and also clearing out the content of package.json while these two files are not disposable similar to a Vaadin project. Even though, not having them in v24.1 in comparison to v24.0 looks like a breaking change in a minor release, I couldn't convince myself that the have an actual use for Hilla users. We might consider implementing goals with similar names, but a functionality more relevant to Hilla projects. However, technically, it would be a behavioral breaking change anyway.

Couldn't agree more. But I don't think that it's a good idea to introduce breaking changes on this, so I propose to expose those goald, but when overriding the execute() we could add a log warning to explain what are the consequences of running that goal in Hilla.

A log warning is not preventing the disaster anyway :)
But, they where available for a while now, and users have already adapted to the fact that they are not for use with Hilla.
If we want to keep our releases based on the semantic versioning practices, deprecation and a warning log is the best we can offer until v3.0.


Feature: diff against sha

Support for running a diff against a particular commit-sha provided by user, in addition to diff-ing against a particular branch name provided by user.

Breaks at runtime, maybe binding redirects are needed:
From ActivityLog.xml:
<description>SetSite failed for package [GitBranchDifferPackage]Source: 'BranchDiffer.VS' Description: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.Threading, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at BranchDiffer.VS.Shared.GitBranchDifferPackage.InitializeAsync(CancellationToken cancellationToken, IProgress`1 progress)
   at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass20_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Threading.JoinableTask.<JoinAsync>d__76.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)
   at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
</description>

Fixes #38


Can i get the file local path? i dont want to show it instead i want it to upload via php

hi, i see this is an example where i can upload in the same time i want to use it to get the local path for example: c://filename.png
thanks

?

@EnoxSoftware

right now it saves temporarily but i want to make it permanent is it possible?
thanks

Unfortunately, there is no such function.
And I do not have any plan to update it.

Hi, ThankYOU for replying.
Can i even save this file as png or jpg into my current path?
please help thanks
On Tue, Mar 5, 2019 at 2:55 PM Enox Software<EMAIL_ADDRESS>wrote:

Unfortunately, there is no such function.
And I do not have any plan to update it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EnoxSoftware/WebGLFileUploader/issues/1#issuecomment-469615881,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AebNejYGrTOx8Y1-oAFfZ8EImH-JmUiAks5vTj8RgaJpZM4bT5WB
.


Fix link

Hello 👍 proposing to fix a link that is currently going to a 404.
Thanks

Docs Build status updates of commit 8448687:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-1.0/MSOnline/AzureActiveDirectory.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 609a70e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-1.0/MSOnline/AzureActiveDirectory.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Failed to find any matching files for models/weights/vnect_tf

Hi,
I couldn't run the demo becouse I don't have the vnect_tf.
Readme.md say: "1.Download model, put them in folder models/weights", but can not find the link to download.
Yuri
<EMAIL_ADDRESS>

I contacted the author and received access to the file, but I still don't understand. The demo expects a file called vnect_tf with no extension, so presumably I need to do something with the university's caffemodel file before your program can use it. What am I missing?


[FIXED] Guitar mode should have a hit window for fretting after strumming

Discussed in https://github.com/TeamRizu/OutFox/discussions/239

Originally posted by shockdude February 21, 2021
Give an example of what is wrong
In Guitar mode, you have to strictly hold a fret before strumming a note in order to hit the note. If you strum & fret at the "same time", chances are you might hit the fret slightly after strumming, resulting in a miss.
Given an example of what it should look like
Other guitar engines (Clone Hero, Gitadora PC) have a window to allow fretting after strumming to still hit notes. The leniency of other engines makes SM's strict engine more frustrating to play in comparison, imo.
Edit: oops, original nitpick was backwards, it should be "fretting after strumming".

fixed in 4.9.8


Wrong content type

When calling the API, the content-type header returns content-type: application/octet-stream instead of content-type: application/json.
The issue happens when using curl without extra headers and also when specifying -H "Accept: application/json".

Hi @jadolg thanks for reporting this. I had not realized since the response included the type application/json and the content type was correct locally because it was functioning as SSR, but when the deployment was static this was modified and this problem occurred.
This has already been solved in v2.
Thanks again!


Changes made by Posten (again??!)

The module is not returning any values. It just states that it is "Loading.."

The module is not returning any values. It just states that it is "Loading.."

I have the same here. Tried to delete the module and download it again, it still says "Loading..".

Posten has started using a new API with a token that changes quite often
Example:
curl -X GET -H "Content-type: application/json" -H "kp-api-token: f3508ef9MTY4MjY4NjMyMw" https://www.posten.no/levering-av-post/_/service/no.posten. website/delivery-days?postalCode=7033
I will see if it is possible to calculate what this token is at any given time, when I find the time.

I fixed it now.
They had a similar problem in the Home Assistant integration:
https://github.com/BobTheShoplifter/HomeAssistant-Posten/issues/9
Then we can hope that Posten's API will stay like this


#managed-service-identity-authentication location doesnt exist on the page

The link points to a location on the page that doesn't exist.
https://docs.microsoft.com/en-us/azure/data-factory/connector-azure-sql-database#managed-service-identity-authentication

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 09dd1d03-ae28-c5a2-7c64-2f51675f6b09
Version Independent ID: dac74d68-2105-a029-1f49-d444c0a252f4
Content: Copy data to or from Azure SQL Database by using Data Factory
Content Source: articles/data-factory/connector-azure-sql-database.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@Appjunkie
Thanks for the feedback! We are currently investigating and will update you shortly.

The hyper link has now changed from
#managed-service-identity-authentication  to #managed-identity
it was broken when I reported it.
Thanks for fixing it


Support dots in model names

Make the extension work with models that contain dots, as suggested in this dbt post

Great work! Thanks, I'll merge it and will make a new release shortly.


fix: change input type in error_boundary example

Chrome (mac) doesn't allow type non-digits in numeric inputs, so I removed type=number from input to make example more correct in this case.

First: I very much appreciate the spirit of the PR, which I think is that the example is unrealistic, and it is much better to enforce constraints like this by doing them in built-in HTML rather than in user-land code, for many reasons. I 100% agree with that.
But I also notice that while you refer to Chrome, this constraint is not the same in other browsers. Firefox and Safari, at least in the versions I have installed, both display type="number" chrome (up and down arrows to change number, etc.) but don't enforce the validation; if I type or paste foo into them, foo appears in the input and the failed parsing triggers the <ErrorBoundary/>
In fact in Chrome, on an invalid copy and paste the input event still fires and tries to set the signal to a number, and fails to parse it, leaving a blank space in the UI and a blank value. In this case triggering the <ErrorBoundary/> is actually the only indication of an invalid input other than the browser just doing nothing!
So ironically assuming that the browser will enforce these pretty obvious constraints has the potential to make your UX worse because the behavior is incosistent across browsers.
I'd be open to either

adding an explanatory comment along those lines, saying that this is ensuring a consistent validation experience across browsers
creating a more realistic example if you can think of one: i.e., rather than loosening the browser constraint, creating a more realistic situation where we might have an error on the Rust side

Ok, let's stick with an exisiting example, I don't think it is a big deal.
I'll make a new pr if I come up with more realistic example :)


How to reference/cite?

How should a researcher reference or cite this package? Are the methods used here published?

according to the PR of this method into skimage the main two references are:

faisal et. al.
tward et. al.


where is the default model path ?

hi,dear
python chat.py --path  ${PATH-to-your-actor-model}
if I want use opt-1.3b model, how ?

After running step 1 or step 3, you will have an output path for the fine-tuned model: ./output/{actor|step3}-models/1.3b/
Provide this path to chat.py


Feat/model train

Related Issue(s)
Fixes #
Resolves #
Closes #
Proposed Changes

[x]

Checklist

[x] I have followed the repository's contribution guidelines.
[x] I have added necessary documentation or updated existing documentation.
[x] My code follows the established code style and formatting of the project.
[x] I have tested my changes and they function as expected.
[ ] I have added suitable unit tests (if applicable).

Screenshots

To-Do

[ ]

Additional Information

@techyNonso do merge main branch and request a review

@techyNonso do merge main branch and request a review

I don't understand

@techyNonso verel deployment and build is failing, kindly fix

@techyNonso verel deployment and build is failing, kindly fix

IT has been fixed, please review and merge


Disabling diagnostics doesn’t work

Issue
I am unable to disable ts-jest diagnostics.
I’m using the following jest.config.js:
module.exports = {
  preset: 'ts-jest',
  globals: {
    'ts-jest': {
      diagnostics: false,
    },
  },
};

This outputs
ts-jest[config] (WARN) TypeScript diagnostics (customize using `[jest-config].globals.ts-jest.diagnostics` option):
message TS151001: If you have issues related to imports, you should consider setting `esModuleInterop` to `true` in your TypeScript configuration file (usually `tsconfig.json`). See https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability for more information.

Expected behavior
Diagnostics are disabled
Debug log:

log file content
{"context":{"allowJs":false,"logLevel":20,"namespace":"jest-preset","package":"ts-jest","version":"24.0.2"},"message":"creating jest presets not handling JavaScript files","sequence":1,"time":"2019-08-14T08:16:41.987Z"}
{"context":{"logLevel":20,"namespace":"Importer","package":"ts-jest","version":"24.0.2"},"message":"creating Importer singleton","sequence":2,"time":"2019-08-14T08:16:43.034Z"}
{"context":{"allowJs":false,"logLevel":20,"namespace":"jest-preset","package":"ts-jest","version":"24.0.2"},"message":"creating jest presets not handling JavaScript files","sequence":3,"time":"2019-08-14T08:16:43.037Z"}
{"context":{"actualVersion":"24.8.0","expectedVersion":">=24 <25","logLevel":20,"namespace":"versions","package":"ts-jest","version":"24.0.2"},"message":"checking version of jest: OK","sequence":4,"time":"2019-08-14T08:16:43.038Z"}
{"context":{"baseOptions":{},"logLevel":20,"namespace":"jest-transformer","package":"ts-jest","transformerId":1,"version":"24.0.2"},"message":"created new transformer","sequence":5,"time":"2019-08-14T08:16:43.038Z"}
{"context":{"fileName":"/home/remco/Projects/tiny-jsx/h.test.tsx","logLevel":20,"namespace":"jest-transformer","package":"ts-jest","transformOptions":{"config":{"automock":false,"browser":false,"cache":true,"cacheDirectory":"/tmp/jest_rs","clearMocks":false,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/home/remco/Projects/tiny-jsx","dependencyExtractor":null,"detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"filter":null,"forceCoverageMatch":[],"globalSetup":null,"globalTeardown":null,"globals":{},"haste":{"computeSha1":false,"providesModuleNodeModules":[],"throwOnModuleCollision":false},"moduleDirectories":["node_modules"],"moduleFileExtensions":["js","json","jsx","ts","tsx","node"],"moduleNameMapper":{},"modulePathIgnorePatterns":[],"name":"888496d3960f5be6df23c5f8d712e230","prettierPath":"prettier","resetMocks":false,"resetModules":false,"resolver":null,"restoreMocks":false,"rootDir":"/home/remco/Projects/tiny-jsx","roots":["/home/remco/Projects/tiny-jsx"],"runner":"jest-runner","setupFiles":[],"setupFilesAfterEnv":[],"skipFilter":false,"snapshotSerializers":[],"testEnvironment":"/home/remco/Projects/tiny-jsx/node_modules/jest-environment-jsdom/build/index.js","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":["**/__tests__/**/*.[jt]s?(x)","**/?(*.)+(spec|test).[tj]s?(x)"],"testPathIgnorePatterns":["/node_modules/"],"testRegex":[],"testRunner":"/home/remco/Projects/tiny-jsx/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.tsx?$","/home/remco/Projects/tiny-jsx/node_modules/ts-jest/dist/index.js"]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"instrument":false,"rootDir":"/home/remco/Projects/tiny-jsx"},"transformerId":1,"version":"24.0.2"},"message":"computing cache key for /home/remco/Projects/tiny-jsx/h.test.tsx","sequence":6,"time":"2019-08-14T08:16:43.038Z"}
{"context":{"logLevel":30,"namespace":"jest-transformer","package":"ts-jest","transformerId":1,"version":"24.0.2"},"message":"no matching config-set found, creating a new one","sequence":7,"time":"2019-08-14T08:16:43.039Z"}
{"context":{"config":{"automock":false,"browser":false,"cache":true,"cacheDirectory":"/tmp/jest_rs","clearMocks":false,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/home/remco/Projects/tiny-jsx","dependencyExtractor":null,"detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"filter":null,"forceCoverageMatch":[],"globalSetup":null,"globalTeardown":null,"globals":{},"haste":{"computeSha1":false,"providesModuleNodeModules":[],"throwOnModuleCollision":false},"moduleDirectories":["node_modules"],"moduleFileExtensions":["js","json","jsx","ts","tsx","node"],"moduleNameMapper":{},"modulePathIgnorePatterns":[],"name":"888496d3960f5be6df23c5f8d712e230","prettierPath":"prettier","resetMocks":false,"resetModules":false,"resolver":null,"restoreMocks":false,"rootDir":"/home/remco/Projects/tiny-jsx","roots":["/home/remco/Projects/tiny-jsx"],"runner":"jest-runner","setupFiles":[],"setupFilesAfterEnv":[],"skipFilter":false,"snapshotSerializers":[],"testEnvironment":"/home/remco/Projects/tiny-jsx/node_modules/jest-environment-jsdom/build/index.js","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":["**/__tests__/**/*.[jt]s?(x)","**/?(*.)+(spec|test).[tj]s?(x)"],"testPathIgnorePatterns":["/node_modules/"],"testRegex":[],"testRunner":"/home/remco/Projects/tiny-jsx/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.tsx?$","/home/remco/Projects/tiny-jsx/node_modules/ts-jest/dist/index.js"]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"logLevel":20,"namespace":"backports","package":"ts-jest","transformerId":1,"version":"24.0.2"},"message":"backporting config","sequence":8,"time":"2019-08-14T08:16:43.039Z"}
{"context":{"jestConfig":{"automock":false,"browser":false,"cache":true,"cacheDirectory":"/tmp/jest_rs","clearMocks":false,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/home/remco/Projects/tiny-jsx","dependencyExtractor":null,"detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"filter":null,"forceCoverageMatch":[],"globalSetup":null,"globalTeardown":null,"globals":{"ts-jest":{}},"haste":{"computeSha1":false,"providesModuleNodeModules":[],"throwOnModuleCollision":false},"moduleDirectories":["node_modules"],"moduleFileExtensions":["js","json","jsx","ts","tsx","node"],"moduleNameMapper":{},"modulePathIgnorePatterns":[],"name":"888496d3960f5be6df23c5f8d712e230","prettierPath":"prettier","resetMocks":false,"resetModules":false,"resolver":null,"restoreMocks":false,"rootDir":"/home/remco/Projects/tiny-jsx","roots":["/home/remco/Projects/tiny-jsx"],"runner":"jest-runner","setupFiles":[],"setupFilesAfterEnv":[],"skipFilter":false,"snapshotSerializers":[],"testEnvironment":"/home/remco/Projects/tiny-jsx/node_modules/jest-environment-jsdom/build/index.js","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":["**/__tests__/**/*.[jt]s?(x)","**/?(*.)+(spec|test).[tj]s?(x)"],"testPathIgnorePatterns":["/node_modules/"],"testRegex":[],"testRunner":"/home/remco/Projects/tiny-jsx/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.tsx?$","/home/remco/Projects/tiny-jsx/node_modules/ts-jest/dist/index.js"]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"version":"24.0.2"},"message":"normalized jest config","sequence":9,"time":"2019-08-14T08:16:43.040Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"tsJestConfig":{"compiler":"typescript","diagnostics":{"ignoreCodes":[6059,18002,18003],"pretty":true,"throws":true},"isolatedModules":false,"packageJson":{"kind":"file"},"transformers":[],"tsConfig":{"kind":"file"}},"version":"24.0.2"},"message":"normalized ts-jest config","sequence":10,"time":"2019-08-14T08:16:43.040Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"version":"24.0.2"},"message":"babel is disabled","sequence":11,"time":"2019-08-14T08:16:43.042Z"}
{"context":{"logLevel":20,"namespace":"Importer","package":"ts-jest","requireResult":{"exists":true,"given":"typescript","path":"/home/remco/Projects/tiny-jsx/node_modules/typescript/lib/typescript.js"},"version":"24.0.2"},"message":"loaded module typescript","sequence":12,"time":"2019-08-14T08:16:43.240Z"}
{"context":{"logLevel":20,"namespace":"Importer","package":"ts-jest","version":"24.0.2"},"message":"patching typescript","sequence":13,"time":"2019-08-14T08:16:43.240Z"}
{"context":{"actualVersion":"3.5.3","expectedVersion":">=2.7 <4","logLevel":20,"namespace":"versions","package":"ts-jest","version":"24.0.2"},"message":"checking version of typescript: OK","sequence":14,"time":"2019-08-14T08:16:43.241Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"tsConfigFileName":"/home/remco/Projects/tiny-jsx/tsconfig.json","version":"24.0.2"},"message":"readTsConfig(): reading /home/remco/Projects/tiny-jsx/tsconfig.json","sequence":15,"time":"2019-08-14T08:16:43.241Z"}
{"context":{"diagnosticCodes":[151001],"diagnosticText":"\u001b[94mmessage\u001b[0m\u001b[90m TS151001: \u001b[0mIf you have issues related to imports, you should consider setting `esModuleInterop` to `true` in your TypeScript configuration file (usually `tsconfig.json`). See https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability for more information.\n","logLevel":20,"namespace":"TSError","package":"ts-jest","version":"24.0.2"},"message":"created new TSError","sequence":16,"time":"2019-08-14T08:16:43.251Z"}
{"context":{"error":{"diagnosticCodes":[151001],"diagnosticText":"\u001b[94mmessage\u001b[0m\u001b[90m TS151001: \u001b[0mIf you have issues related to imports, you should consider setting `esModuleInterop` to `true` in your TypeScript configuration file (usually `tsconfig.json`). See https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability for more information.\n"},"logLevel":40,"namespace":"config","package":"ts-jest","transformerId":1,"version":"24.0.2"},"message":"TypeScript diagnostics (customize using `[jest-config].globals.ts-jest.diagnostics` option):\n\u001b[94mmessage\u001b[0m\u001b[90m TS151001: \u001b[0mIf you have issues related to imports, you should consider setting `esModuleInterop` to `true` in your TypeScript configuration file (usually `tsconfig.json`). See https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability for more information.","sequence":17,"time":"2019-08-14T08:16:43.252Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"tsconfig":{"input":{"compilerOptions":{"inlineSourceMap":true,"jsx":"react","jsxFactory":"h","lib":["dom","esnext"],"noEmit":true,"noUnusedLocals":true,"noUnusedParameters":true,"strict":true,"target":"esnext","types":["jest"]}},"resolved":{"compileOnSave":false,"configFileSpecs":{"includeSpecs":["**/*"],"validatedIncludeSpecs":["**/*"],"wildcardDirectories":{"/home/remco/Projects/tiny-jsx":1}},"errors":[{"category":3,"code":151001,"messageText":"If you have issues related to imports, you should consider setting `esModuleInterop` to `true` in your TypeScript configuration file (usually `tsconfig.json`). See https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability for more information."}],"fileNames":["/home/remco/Projects/tiny-jsx/h.test.tsx","/home/remco/Projects/tiny-jsx/h.ts"],"options":{"allowSyntheticDefaultImports":true,"configFilePath":"/home/remco/Projects/tiny-jsx/tsconfig.json","declaration":false,"inlineSourceMap":false,"inlineSources":true,"jsx":2,"jsxFactory":"h","lib":["lib.dom.d.ts","lib.esnext.d.ts"],"module":1,"noEmit":false,"noUnusedLocals":true,"noUnusedParameters":true,"outDir":"$$ts-jest$$","removeComments":false,"sourceMap":true,"strict":true,"target":8,"types":["jest"]},"raw":{"compileOnSave":false,"compilerOptions":{"inlineSourceMap":true,"jsx":"react","jsxFactory":"h","lib":["dom","esnext"],"noEmit":true,"noUnusedLocals":true,"noUnusedParameters":true,"strict":true,"target":"esnext","types":["jest"]}},"typeAcquisition":{"enable":false,"exclude":[],"include":[]},"wildcardDirectories":{"/home/remco/Projects/tiny-jsx":1}}},"version":"24.0.2"},"message":"normalized typescript config","sequence":18,"time":"2019-08-14T08:16:43.252Z"}
{"context":{"fileName":"/home/remco/Projects/tiny-jsx/h.ts","logLevel":20,"namespace":"jest-transformer","package":"ts-jest","transformOptions":{"config":{"automock":false,"browser":false,"cache":true,"cacheDirectory":"/tmp/jest_rs","clearMocks":false,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/home/remco/Projects/tiny-jsx","dependencyExtractor":null,"detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"filter":null,"forceCoverageMatch":[],"globalSetup":null,"globalTeardown":null,"globals":{},"haste":{"computeSha1":false,"providesModuleNodeModules":[],"throwOnModuleCollision":false},"moduleDirectories":["node_modules"],"moduleFileExtensions":["js","json","jsx","ts","tsx","node"],"moduleNameMapper":{},"modulePathIgnorePatterns":[],"name":"888496d3960f5be6df23c5f8d712e230","prettierPath":"prettier","resetMocks":false,"resetModules":false,"resolver":null,"restoreMocks":false,"rootDir":"/home/remco/Projects/tiny-jsx","roots":["/home/remco/Projects/tiny-jsx"],"runner":"jest-runner","setupFiles":[],"setupFilesAfterEnv":[],"skipFilter":false,"snapshotSerializers":[],"testEnvironment":"/home/remco/Projects/tiny-jsx/node_modules/jest-environment-jsdom/build/index.js","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":["**/__tests__/**/*.[jt]s?(x)","**/?(*.)+(spec|test).[tj]s?(x)"],"testPathIgnorePatterns":["/node_modules/"],"testRegex":[],"testRunner":"/home/remco/Projects/tiny-jsx/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.tsx?$","/home/remco/Projects/tiny-jsx/node_modules/ts-jest/dist/index.js"]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"instrument":false,"rootDir":"/home/remco/Projects/tiny-jsx"},"transformerId":1,"version":"24.0.2"},"message":"computing cache key for /home/remco/Projects/tiny-jsx/h.ts","sequence":19,"time":"2019-08-14T08:16:43.254Z"}

hi @remcohaszing , is this issue still occurred in ts-jest 24.1.0 ? If yes, would you please provide us a minimum reproduce repo ?

Yep. I encountered this in a fairly small repository, mini-jsx. I just upgraded everything to their latest versions and the warning is still logged.
The latest build output can be seen here.

Same here. I can't disable the diagnostic messages. Not all or by message code.
jest.config.js:
module.exports = {
  preset: 'ts-jest',
  testEnvironment: 'node',
  globals: {
    'ts-jest': {
      diagnostics: false
    }
  }
};

package.json (Snippet)
{
  "devDependencies": {
    "@types/jest": "^24.0.23",
    "jest": "^24.9.0",
    "ts-jest": "^24.1.0",
    "typescript": "^3.7.2",
  }
}

hi, the log you saw actually came from this logger line. This logging is more like a warning, disabling diagnostics means if there is a compilation issue, ts-jest won't throw error.
Disabling diagnostics itself work, just the logging is misunderstood. I will close this issue as it's not broken functionality. ts-jest can adjust the documentation to make clear about this diagnostic logging or you can submit a PR to adjust the documentation.

Glad it's not a bug, but how do I tell the logger to stop putting "message TS151001" on the output?

It seems this warning can be turned off in jest.config.js:
module.exports = {
  // ...
  globals: {
    'ts-jest': {
      diagnostics: {
        ignoreCodes: [ 'TS151001' ],
      },
    },
  },
  // ...
};

I think this is what's happening to me. I see those in Github Actions and they seem to fail my tests:
ts-jest[ts-compiler] (WARN) tests/state/definition.test.ts:82:30 - error TS2345: Argument of type '{ variables: sinon.SinonStub<any[], any>; getById: sinon.SinonStub<any[], any>; preview: sinon.SinonStub<any[], any>; }' is not assignable to parameter of type 'DefinitionRepository'.
  Type '{ variables: SinonStub<any[], any>; getById: SinonStub<any[], any>; preview: SinonStub<any[], any>; }' is missing the following properties from type 'DefinitionRepository': n, validate, isNameUnique, getChain, and 18 more.

It's a legacy project and there are quite enough of them to make those error tedious to fix. So I just wanted them to be warnings (and not completely ignored as previously suggested, since we might get around and fix them, some time).
Anyway, this is my jest.config.js file:
module.exports = {
  modulePaths: [
    '<rootDir>/src/',
    '<rootDir>/node_modules'
  ],
  transform: {
    '^.+\\.(ts|tsx)$': 'ts-jest',
    '^.+\\.(js|jsx)$': 'babel-jest',
    '^.+\\.(scss|ico|css)$': '<rootDir>/tests/importStub.js'
  },
  setupFiles: [
    '<rootDir>/tests/jest-aurelia.config.ts'
  ],
  setupFilesAfterEnv: ['<rootDir>/tests/jest-framework.config.ts'],
  // https://stackoverflow.com/questions/62699108/aurelia-testing-failed-to-execute-replacechild-on-node-parameter-1-is-not
  testEnvironment: 'node',
  testRegex: '\\.(test|spec)\\.(ts|js)x?$',
  globals: {
    'ts-jest': {
      diagnostics: {
        warnOnly: true
      }
    },
    CURRENT_APPLICATION: null
  }
};

I have just set warnOnly instead of diagnostics: false, but in both cases I think I was getting the diagnostics? Anyway I still see the errors and my test step does not pass.
Relevant information:
"jest": "^27.2.0",
"ts-jest": "^27.0.5",

Node: 14.17.6 as setup by Github Actions.
It looks like locally I may or may not see them (the behaviour was not consistent).

@alexkunin 's solution works. (From June 28 2021).

Yes, TS151001 is suppressed, but the solution yields another warning:
ts-jest[ts-jest-transformer] (WARN) Define `ts-jest` config under `globals` is deprecated. Please do
transform: {
    <transform_regex>: ['ts-jest', { /* ts-jest config goes here in Jest */ }],
}

and doing what is suggested, in turn yields TS151001 again

@alexkunin 's solution works. (From June 28 2021).

Yes, TS151001 is suppressed, but the solution yields another warning:
ts-jest[ts-jest-transformer] (WARN) Define `ts-jest` config under `globals` is deprecated. Please do
transform: {
    <transform_regex>: ['ts-jest', { /* ts-jest config goes here in Jest */ }],
}

and doing what is suggested, in turn yields TS151001 again

It works if you remove the preset: 'ts-jest' from the jest config.

@alexkunin 's solution works. (From June 28 2021).

Yes, TS151001 is suppressed, but the solution yields another warning:
ts-jest[ts-jest-transformer] (WARN) Define `ts-jest` config under `globals` is deprecated. Please do
transform: {
    <transform_regex>: ['ts-jest', { /* ts-jest config goes here in Jest */ }],
}

and doing what is suggested, in turn yields TS151001 again

It works if you remove the preset: 'ts-jest' from the jest config.

so jest just handles typescript out of the box now?

In my case, I just put this code into jest.config.js
export default default {
.....
   transform: {
      '^.+\\.tsx?$': [
        'ts-jest',
        { tsconfig: '<rootDir>/packages/api/tsconfig.json'  }, // <rootDir>/packages/api is the path navigate to tsconfig.json
      ]
    }
  }

Tried using the globals approach, but got the deprecation error. This worked instead.
module.exports = {
  preset: 'ts-jest',
  transform: {
    '^.+\\.(ts|tsx)?$': ['ts-jest', {diagnostics: {ignoreCodes: ['TS151001']}}],
    "^.+\\.(js|jsx)$": "babel-jest",
  }
};


Frontend JAMStack integration

This PR integrates a working Okta login flow, REST calls to OpenAPI-based mock backend, and CI/CD build automation.
Changes

integration of login page with Okta
prototype JWT body unpacking
integration of REST api calls to mock server
prototype REST api calls
adds CI/CD build automation: docker and github workflow

builds static website assets
builds docker image of Ngnix server for static website

Checklist

[x] Tested locally?
[x] Added new dependencies?
[ ] Updated the docs?
[x] Did you check for sensitive data, and remove any?

While integrating the Okta login auth flow, I was driven to use port 7071 to make it work.
Port 7071 is the port used by prime-router, making it difficult to run the frontend against the backend without jumping through hoops. I'd like to make this easier.
Can we add an Okta config for port 7079 with a redirect tohttp://localhost:7079/authorize.html to enable both to work in parallel?
Then whomever is working on the frontend can run against the api mock or the prime-router by simply running the desired backend.


Fix for "cannot convert int[] to int" compile-time error

Fix for "cannot convert int[] to int" compile-time error occurring inside d4j-backends/nd4j-tests/src/test/java/org/nd4j/linalg/Nd4jTestsC.java.
Problem was line 1939:
INDArray repeated = x.repeat(new int[] {2});
which should be
INDArray repeated = x.repeat(1, new int[] {2});
FTFY.

Build triggered. sha1 is original commit.

Build started sha1 is original commit.

Already fixed on master.

Build finished. 1982 tests run, 51 skipped, 12 failed.

Refer to this link for build results (access rights to CI server needed):
/job/nd4j_PR/324/Build result: FAILURE[...truncated 4.68 MB...]	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544)	at hudson.model.ResourceController.execute(ResourceController.java:98)	at hudson.model.Executor.run(Executor.java:405)Caused by: java.io.FileNotFoundException: https://api.github.com/repos/deeplearning4j/nd4j/statuses/cc977fe4aedf08fe171f420723d8f458125aca32	at sun.reflect.GeneratedConstructorAccessor50.newInstance(Unknown Source)	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)	at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1890)	at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1885)	at java.security.AccessController.doPrivileged(Native Method)	at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1884)	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1457)	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)	at org.kohsuke.github.Requester.parse(Requester.java:535)	at org.kohsuke.github.Requester._to(Requester.java:262)	... 12 moreCaused by: java.io.FileNotFoundException: https://api.github.com/repos/deeplearning4j/nd4j/statuses/cc977fe4aedf08fe171f420723d8f458125aca32	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836)	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)	at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)	at org.kohsuke.github.Requester.parse(Requester.java:525)	... 13 more


Extracting diode_iv data and adding new regression for it for ngspice models

Extracting diode_iv data and adding new regression for it for ngspice models

@atorkmabrains Ready to review

@atorkmabrains Solved


IPQoS requires "either" value

It can be a pair of: one of typed or an integer value.
Currently there is no way to represent this with the parser.

ListenAddress also could use a typed pair.


What Features are Used in the Geometric Pre-training Tasks in GeoLayoutLM?

I appreciate the work done with GeoLayoutLM, but I find that the explanation about the geometric pre-training tasks in the paper is not very clear. The paper mentions "The input of these tasks are text-segments feature {Bi} which can be either of the five features:{Hi},{Mvi},{Fvi},{Mt,b(i)},{Fi,b,(i)}, and then there pre-training tasks such as P = Softmax(Linear[Bi,Bj])) (Direction and Distance Modeling) are set up. However, it's not specified which of the five features is the Bi used in this task. Could you please provide more clarity on this matter?

The geometric pre-training objective is exerted to the 5 features respectively. The final objective is the sum of them, plus a mvlm loss.

Thank you very much for the prompt reply

By the way, do the features of the mask tokens not participate in these geometric pre-training tasks?

By the way, do the features of the mask tokens not participate in these geometric pre-training tasks?

They still probably participate in geometric pre-training tasks, since their coordinates are not masked.

Thank you very much for the prompt reply


Fix Unreferenced Formal Parameter warning

There's this compiler warning reported for the FormatStr parameter (if JB_DEBUG_MODE is 0, which is the default) under MSVC 14: Unreferenced Formal Parameter.
Marking it as maybe_unused resolves this.

Hello @KristofMorva
Let me double check first that we don't have UE4 C++14 users first :)

Should be available in the next public build. Thank you for the PR :)

@DecoyRS When is the next public build - We're hitting this as well and currently don't submit the plugin into Perforce as some may use Visual Studio or have older versions of Rider etc...


How to predict the class label of a new text in LSTM (which is not in training and testing set)?

How can I make use of the built model from imdb_lstm.py to predict the class label of a new input text which has no value corresponding to y_test ? Thanks in advance..

Using model.predict(X) method.

@qzshadow Thanks..Is there no need of save and restore of the built model?

sure you have to save both the model and weights after training the networks, then when you use it, let's say you are giving samples X to get the predicts y, you need restore the model and load the weights into the model, then use this model to predict. but once the model is loaded into the memory, you could use different Xs to get different ys, no need to restore the model for each X.

Thanks..But actually I am new to this field. If you get time, can you please help me regarding this save and restore of the model?

See http://keras.io/faq/#how-can-i-save-a-keras-model for details

Be sure that your vocabulary includes the new words as well. Otherwise you may have OOV (out of vocabulary) when you present your unseen data to your data processing layer before your LSTM crunches it.

@qzshadow Thanks.. I will try
@philipperemy Thank you for the insight provided..


Enforce hexadecimal encoding of 'PasswordHash'

fixes #98

@RaoulHC does this look good?

I don't think you want to get rid of the original version of this, encoding doesn't matter for ByteStrings and leaving a non hex version allows users to encode it how they want. I see Sel.Hashing.SHA2.SHA512 has both hashToBinary and hashToHexByteString so perhaps something along those lines makes the most sense.
I also notice in both SHA2 modules the HexText functions aren't encoding the binary into base16 and appear to be faulty, so probably makes sense to fix them in this PR too.

@RaoulHC Great, thank you!

@RaoulHC Hopefully this should be good now

@RaoulHC Thanks for the report and the review btw, it's highly appreciated. Don't hesitate to point out other inconsistencies if you see them (or ping on Matrix)


Duplicate transaction error

When I attempt to do the following twice it throws up a duplicate transaction error:
./eosc --wallet-port 7777 transfer inita currency 10000
If I run the same command with a different amount it works fine but only once.
./eosc --wallet-port 7777 transfer inita currency 10001
The error output is as below:
2274982ms thread-0   main.cpp:768                  main                 ] Failed with error: 10 assert_exception: Assert Exception
status_code == 200: Error
: 3030011 tx_duplicate: duplicate transaction
Transaction is not unique
{}
thread-0  chain_controller.cpp:828 validate_uniqueness

You have to enter the commands quickly to reproduce error.

Approve, that’s weird.>>> eosapi.transfer('inita','eos',100,'abc',0)b'{"transaction_id":"eae5e2659fbdf3a5d410b3f94b5e1aca189c8c320eff710bb9de58b683a9d88f","processed":{"refBlockNum":0,"refBlockPrefix":0,"expiration":"2017-09-08T13:03:04","scope":["eos","inita"],"signatures":[],"messages":[{"code":"eos","type":"transfer","authorization":[{"account":"inita","permission":"active"}],"data":{"from":"inita","to":"eos","amount":100,"memo":"abc"},"hex_data":"000000008040934b000000000000e62b640000000000000003616263"}],"output":[{"notify":[{"name":"inita","output":{"notify":[],"sync_transactions":[],"async_transactions":[]}}],"sync_transactions":[],"async_transactions":[]}]}}'>>> eosapi.transfer('inita','eos',100,'abc',0)84733ms thread-1   eosapi.cpp:333                transfer_            ] 3030011 tx_duplicate: duplicate transactionTransaction is not unique    {}    thread-1  chain_controller.cpp:830 validate_uniqueness    {"trx":{"refBlockNum":0,"refBlockPrefix":0,"expiration":"2017-09-08T13:03:04","scope":["eos","inita"],"readscope":[],"messages":[{"code":"eos","type":"transfer","authorization":[{"account":"inita","permission":"active"}],"data":"000000008040934b000000000000e62b640000000000000003616263"}],"signatures":[]}}    thread-1  chain_controller.hpp:319 validate_transaction    {"trx":{"refBlockNum":0,"refBlockPrefix":0,"expiration":"2017-09-08T13:03:04","scope":["eos","inita"],"readscope":[],"messages":[{"code":"eos","type":"transfer","authorization":[{"account":"inita","permission":"active"}],"data":"000000008040934b000000000000e62b640000000000000003616263"}],"signatures":[]}}    thread-1  chain_controller.cpp:959 apply_transaction    {"trx":{"refBlockNum":0,"refBlockPrefix":0,"expiration":"2017-09-08T13:03:04","scope":["eos","inita"],"readscope":[],"messages":[{"code":"eos","type":"transfer","authorization":[{"account":"inita","permission":"active"}],"data":"000000008040934b000000000000e62b640000000000000003616263"}],"signatures":[]}}    thread-1  chain_controller.cpp:265 push_transactionOn 8 Sep 2017, at 6:02 PM, Bezwada Satyapravin<EMAIL_ADDRESS>wrote:You have to enter the commands quickly to reproduce error.—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/EOSIO/eos","title":"EOSIO/eos","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/EOSIO/eos"}},"updates":{"snippets":[{"icon":"PERSON","message":"@pavybez in #384: You have to enter the commands quickly to reproduce error."}],"action":{"name":"View Issue","url":"https://github.com/EOSIO/eos/issues/384#issuecomment-328062094"}}}

I debugged code and found that we generate a digest using transaction details. Hence if we have two similar transactions in the same block the message digest turns out to be the same and the hash function produces the same ID for both transactions. I think we should have a unique identifier for transaction besides just the block reference number.

This isn't a bug per-say, you can resend the transaction after the expiration of the original.
You can update the TAPOS every 3 seconds
You can update the expiration if you really need to
You can add a dummy message to the transaction as well.

Alternatively, you can put multiple transfers in a single transaction.
The wallet could implement the "naggle" algorithm if this double-sending occurs frequently

This issue should be resolved in the following way:

[ ] add a print message explaining why a duplicate was created and indicating ways to fix it
[ ] implement a flag on CLI wallet to specify a longer expiration window
[ ] implement a flag on CLI wallet to add a "random" no-op message to force uniqueness, documentation of flag should warn user that it will consume extra bandwidth

@bytemaster Instead of a "noop" message which would need to be recognized by the producer code so that it doesn't try to load some wasm code account and execute it, how do you feel about pushing 1-4 extraneous bytes to the end of a single messages data?  Currently we are not enforcing that every byte of a message is read and this would ultimately save the overhead of an additional message header.


[Bug]: Conflict modify Items and Quantity in edit

Plugin version
Last
Sylius version
1.13.2
What happened?
Hello,
I installed this plugin on my Sylius project and followed all the installation steps mentioned in the README. However, modifying items and quantities no longer works; only the addresses function as expected (by default).
Relevant log output
No response

Hi, @MedAliAb
Do you have an idea on how to fix it? :)


Path must begin with a leading "/"

After 0.10.0 update, get error for rspec tests:
Failure/Error: expect(response_body).to match_response_schema('users/show')

ArgumentError: Path must begin with a leading "/": #../user.json.

this is schema root path: JsonMatchers.schema_root = 'spec/support/json_schema'

@seanpdoyle plz take a look, if you can)

@Jesterovskiy @mconiglio could you share your schemata?
@Jesterovskiy is #../user.json. a value from spec/support/json_schema/users/show.json?
What is the structure of your spec/support/json_schema directory?

Hello @seanpdoyle, this is my directory tree:
spec/support/api/schemas
├── post.json
└── posts
    └── index.json

I have some schema in the post.json file and then I have the following in the posts/index.json file:
{
  "type": "object",
  "required": [
    "data"
  ],
  "properties": {
    "data": {
      "type": "array",
      "items": {
        "$ref": "../post.json"
      }
    }
  }
}

I tried this using the 0.9.0 version and it works correctly, but I get the ArgumentError: Path must begin with a leading "/" error if I use the 0.10.0 version.

@mconiglio thanks for the extra information!
Could you share a small snippet of post.json?
Also, could you share a JSON snippet that should we valid under the schema?
I'm working on creating a failing test and that data would be really helpful in doing so.

@seanpdoyle thanks to you for the help!
This is post.json
{
  "type": "object",
  "required": [
    "id",
    "type",
    "attributes"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "type": {
      "type": "string"
    },
    "attributes": {
      "type": "object",
      "required": [
        "id",
        "name",
        "kind",
        "species",
        "gender",
        "color",
        "description",
        "location",
        "latitude",
        "longitude",
        "created_at",
        "user"
      ],
      "properties": {
        "id": {
          "type": "integer"
        },
        "name": {
          "type": "string"
        },
        "kind": {
          "type": "string"
        },
        "species": {
          "type": "string"
        },
        "gender": {
          "type": "string"
        },
        "color": {
          "type": "string"
        },
        "description": {
          "type": "string"
        },
        "location": {
          "type": "string"
        },
        "latitude": {
          "type": "float"
        },
        "longitude": {
          "type": "float"
        },
        "created_at": {
          "type": "string",
          "format": "date-time"
        },
        "user": {
          "type": "object",
          "required": [
            "id",
            "phone_number",
            "created_at"
          ],
          "properties": {
            "id": {
              "type": "integer"
            },
            "phone_number": {
              "type": "string"
            },
            "created_at": {
              "type": "string",
              "format": "date-time"
            }
          }
        }
      }
    }
  }
}

And this is a response example of what would should match the posts/index schema:
{
    "data": [
        {
            "id": "1",
            "type": "post",
            "attributes": {
                "id": 1,
                "name": "Roxie",
                "kind": "lost",
                "species": "other",
                "gender": "unknown",
                "color": "Blue",
                "description": "Quia sint sapiente. Impedit velit voluptas. Harum facere suscipit.",
                "location": "Pocitos, Montevideo",
                "latitude": -34.913404,
                "longitude": -56.163182,
                "created_at": "2018-08-30T16:20:32.462Z",
                "user": {
                    "id": 19,
                    "phone_number": "92393459",
                    "created_at": "2018-08-30T16:20:32.448Z"
                }
            }
        },
        {
            "id": "2",
            "type": "post",
            "attributes": {
                "id": 2,
                "name": "Bubba",
                "kind": "lost",
                "species": "other",
                "gender": "male",
                "color": "Fuchsia",
                "description": "Non saepe optio. Nostrum aut doloribus. Ea animi facilis.",
                "location": "Pocitos, Montevideo",
                "latitude": -34.919485,
                "longitude": -56.166446,
                "created_at": "2018-08-30T16:20:35.079Z",
                "user": {
                    "id": 20,
                    "phone_number": "94431512",
                    "created_at": "2018-08-30T16:20:35.076Z"
                }
            }
        }
    ]
}

As a quick update, I'm working through a failing test that exercises this behavior.
As a temporary (hopefully helpful) bit of information, here's how we're building a JSON schema that references a sibling schema in our tests:
https://github.com/thoughtbot/json_matchers/blob/4ee7fac9982d3e1ef5bed349292cb7c18daba0c7/spec/factories.rb#L86-L106
And here's the schema it's referencing:
https://github.com/thoughtbot/json_matchers/blob/4ee7fac9982d3e1ef5bed349292cb7c18daba0c7/spec/factories.rb#L34-L50
To me, we should (do?) already support what you two are trying to do, but our documentation is lacking about what has changed during our switch from json-schema to json_schema as our underlying validator.
Could you try modifying your schemata to more closely resemble the above schemata and report back on what it took to get it working?
My instincts tell me that you'll need to introduce "definitions" keys and test out declaring "id" keys with "file:/ prefixes, but that's just a hunch.

@mconiglio I've opened https://github.com/thoughtbot/json_matchers/pull/89.
I've lifted the JSON you've provided and added a test to exercise it. It's passing off the bat.
Please pull down that PR and modify that test so that it's in-line with your data. If you can produce a failing test, that would help me understand where the disconnect is.
Thanks!

@mconiglio @seanpdoyle thank you for help. In my case, to use 0.10.0 I need change in each plural schema "$ref": "../user.json" -> "$ref": "file:/user.json#"
and add in singular schema "id": "file:/user.json#",


Generating Open Graph code

Early in the article, the author writes: "By using Search Engine Optimization capabilities of SharePoint Server 2016 we can retrieve the information about the page as follows:"
How do you generate the open graph code that follows, using Sharepoints SEO capabilities? I'm particularly interested in finding out how to generate open graph code for a page image. I'm using item display templates with cross-site publishing.
Thanks,
David

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d38de4b6-af0d-bdf3-d875-b623c28549e1
Version Independent ID: 491f608b-207a-3884-2d1d-36ac34834606
Content: Integrating social media with public-facing websites in SharePoint
Content Source: SharePoint/SharePointServer/administration/integrating-social-media-with-public-facing-websites.md
Product: sharepoint-server-itpro
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

@FisherFast Thank you for your feedback.
I want to make sure you are get the information about generating the graph code. The support team will be able to handles this issue to resolution.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.


Fixed typo in starred page_urls

Just a little copy and paste error, it seems!

@jondolan  Thank you!


IRONN-130-Spain-v5-all-orgs

Moves "Instituto Valenciano de Oncologia" (146-146) to v5 effective 2020-10-21T23:00:00Z . This will need a dry-run @pbugni .
Switches "Hospital Universitario Miguel Servet (Zaragoza)" (146-180) to v5, effective for all time (this was a new site added March '22 - they accidentally asked for v3 at that time).
Removes a redundant org config for "Hospital Universitario Virgen de la Victoria". The removed config is at v3, which is incorrect. The remaining config has the valid transition to v5; this config was later in the file, and it appears that it overrode the prior/bad config, fortunately (at least, as I read https://eproms.truenth.org/api/organization?tree_view=true today).

https://jira.movember.com/browse/IRONN-130

Can of worms.  Lots of patients which had previously completed v3 work, will end up with QuestionnaireResponses that do NOT map to v5.  For example, Patient 3735 (170-146-002), or Patient 3734 (170-146-001):

Patient 3734 (170-146-001):
	Modified QNRs (old, new)
		qnr 40047 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['IRONMAN_v5_recurring_3mo_pattern', 2]
		qnr 40048 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['none of the above', None]
		qnr 40049 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['none of the above', None]
		qnr 40050 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['none of the above', None]
		qnr 40051 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['none of the above', None]
		qnr 59506 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['IRONMAN_v5_recurring_annual_pattern', 1]
		qnr 59507 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['none of the above', None]
		qnr 59508 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['IRONMAN_v5_recurring_annual_pattern', 1]
		qnr 59509 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['IRONMAN_v5_recurring_annual_pattern', 1]
		qnr 59510 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['IRONMAN_v5_recurring_annual_pattern', 1]

We can't just retroactively alter the protocol, as 5 patients have timeline data in v3.  Furthermore, similar problems to the previous case, for example on patients 5685, 5687, 5724, and 5725.
Thank you for removing the duplicate entry for 146103 - I concur that it already had the correct values.

@pbugni  are you able to quantify (without too much work) the level of impact, i.e., what proportion (numerator and denominator would be good to) of total QR's would be abandoned with this change for each site? They'll want to know that...

* We do report QR's in the data reports even if they don't align with a QB, I believe - can you please confirm?

Actually, as I review a QR CSV report from Sept '22, all of the records have timepoint populated with a QB - darn. They'll want confirmation of this, please do check.

@mcjustin after fighting with the complications of a query for such numerator / denominator values as you requested, opted to extend the code so we can see this summary after each preview-site-update run.  anything else you need in this?
for #1 (site 146-146):
Total QuestionnaireResponses for all affected patients in organization: 164
  Number of those QNRs completed before RP change: 164
  Number of those QNRs completed after RP change: 144

for #2 (site 146-180, and again, we MUST retired the v3, can't just insert v5):
Total QuestionnaireResponses for all affected patients in organization: 52
  Number of those QNRs completed before RP change: 52
  Number of those QNRs completed after RP change: 38

@pbugni  my other question was: do we include QR's in the CSV data reports even if they don't align with a QB?

@mcjustin after fighting with the complications of a query for such numerator / denominator values as you requested, opted to extend the code so we can see this summary after each preview-site-update run. anything else you need in this?
...

@pbugni  , along with:
Total QuestionnaireResponses for all affected patients in organization
it would be good to know:
Total QuestionnaireResponses for all patients in organization
Number of affected patients in organization
Number of patients in organization

The one thing this doesn't capture, which might be nice, is to know the number of questionnaire BANKS with altered status (i.e. the number that were completed that are now partial or expired).  Bit more work, but reasonable if you want that?
Here's the current summary report for each:
164 QuestionnaireResponses for all patients in organization 146146
Instituto Valenciano de Oncologia
  Patients in organization: 31
  Patients negatively affected by change: 12
  Number of those QNRs assigned to a QB before RP change: 164
  Number of those QNRs assigned to a QB after RP change: 144

52 QuestionnaireResponses for all patients in organization 146180
Hospital Universitario Miguel Servet (Zaragoza)
  Patients in organization: 5
  Patients negatively affected by change: 5
  Number of those QNRs assigned to a QB before RP change: 52
  Number of those QNRs assigned to a QB after RP change: 38

Now including QB effects:
164 QuestionnaireResponses for all patients in organization 146146
Instituto Valenciano de Oncologia
  Patients in organization: 31
  Patients negatively affected by change: 12
  Number of those QNRs assigned to a QB before RP change: 164
  Number of those QNRs assigned to a QB after RP change: 144
  Number of QuestionnaireBanks completed before RP change: 37
  Number of QuestionnaireBanks completed after RP change: 20

52 QuestionnaireResponses for all patients in organization 146180
Hospital Universitario Miguel Servet (Zaragoza)
  Patients in organization: 5
  Patients negatively affected by change: 5
  Number of those QNRs assigned to a QB before RP change: 52
  Number of those QNRs assigned to a QB after RP change: 38
  Number of QuestionnaireBanks completed before RP change: 14
  Number of QuestionnaireBanks completed after RP change: 0

@mcjustin, I've confirmed there are no other duplicates in the Organization.json file for eproms:
(eproms3) bradly-2 bash ~/uw/truenth-portal 0$  grep '"id":' portal/config/eproms/Organization.json | sort > sorted.master
(eproms3) bradly-2 bash ~/uw/truenth-portal 0$  grep '"id":' portal/config/eproms/Organization.json | sort -u > sorted.unique.master
(eproms3) bradly-2 bash ~/uw/truenth-portal 0$  diff sorted.master sorted.unique.master
22d21
<       "id": 146103,

and double checked, no such duplicates in this branch.

@pbugni  I talked w/ PCCTC about this today. Since the Spanish sites are "all paper", I think they're okay with re-entering the ~40 questionnaires that would be displaced by this v5 change, since they'll gain the proper v5 questionnaire data in the process. But it would be nice to provide them a list of affected patients, QB's and questionnaires, like you provided in the post above https://github.com/uwcirg/truenth-portal/pull/4279#issuecomment-1366993695
, so they wouldn't need to hunt and peck for what needed re-entry (looking at the current adherence report, they already have a lot of 'Expired' timepoints, so the new 'Expired' timepoints would be hard to find) namely:
Patient 3734 (170-146-001):
	Modified QNRs (old, new)
		qnr 40047 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['IRONMAN_v5_recurring_3mo_pattern', 2]
		qnr 40048 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['none of the above', None]
		qnr 40049 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['none of the above', None]
		qnr 40050 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['none of the above', None]
		qnr 40051 ['IRONMAN_v3_recurring_annual_pattern', 0] ==> ['none of the above', None]
		qnr 59506 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['IRONMAN_v5_recurring_annual_pattern', 1]
		qnr 59507 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['none of the above', None]
		qnr 59508 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['IRONMAN_v5_recurring_annual_pattern', 1]
		qnr 59509 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['IRONMAN_v5_recurring_annual_pattern', 1]
		qnr 59510 ['IRONMAN_v3_recurring_annual_pattern', 1] ==> ['IRONMAN_v5_recurring_annual_pattern', 1]

How much work to do that?

Well... re my commit just now:
Switches these two Spanish orgs' v3 retired_as_of date to this coming Monday;
    PCCTC wants this interim state, as once we have the list of affected patients
    and timepoints for the change going farther back, they'll still need to
    discuss w/ the Spanish sites to see what's tolerable there. So this interim
    step allows for collection of future PROs according to v5.

https://github.com/uwcirg/truenth-portal/pull/4279/commits/48d63bc243bdb5fa78abcec25f75560d833609f8

@mcjustin here are the long awaited details - naming the visit and questionnaire needing reentry for each respective patient:
 Details of patients having lost a QuestionnaireResponse association:
  Patient 3733
    visit: Month 3 questionnaire: ironmisc
    visit: Month 6 questionnaire: ironmisc
  Patient 5881
    visit: Baseline questionnaire: ironmisc
  Patient 5783
    visit: Baseline questionnaire: ironmisc
  Patient 5711
    visit: Baseline questionnaire: ironmisc
  Patient 5534
    visit: Baseline questionnaire: ironmisc
  Patient 5481
    visit: Baseline questionnaire: ironmisc
    visit: Month 9 questionnaire: ironmisc
  Patient 5302
    visit: Baseline questionnaire: ironmisc
    visit: Month 3 questionnaire: ironmisc
  Patient 5270
    visit: Month 3 questionnaire: ironmisc
  Patient 4983
    visit: Month 6 questionnaire: ironmisc
    visit: Month 15 questionnaire: ironmisc
  Patient 4229
    visit: Month 9 questionnaire: ironmisc
    visit: Month 21 questionnaire: ironmisc
  Patient 3936
    visit: Month 24 questionnaire: ironmisc
  Patient 3734
    visit: Month 12 questionnaire: ironmisc
    visit: Month 12 questionnaire: factfpsi
    visit: Month 12 questionnaire: epic26
    visit: Month 12 questionnaire: prems
    visit: Month 24 questionnaire: ironmisc
  Patient 3735
    visit: Month 12 questionnaire: ironmisc
    visit: Month 24 questionnaire: ironmisc

@mcjustin here are the long awaited details - naming the visit and questionnaire needing reentry for each respective patient:

@pbugni  thanks, that makes sense. During the meeting earlier today I said that I wasn't certain, but that was based on a notification from github that excluded part of what you wrote there. I've let Marie know via https://jira.movember.com/browse/IRONN-130 , we'll see what they want to do.


support lonelynode ha setup

proposed changes to allow ha setup consisting of lonelynodes only
Note: the step list needs to be changed from the default to this (maybe followed by other steps):
mkcloud cleanup prepare setupadmin addupdaterepo runupdate prepareinstcrowbar bootstrapcrowbar instcrowbar setuplonelynodes crowbar_register setup_aliases proposal

If this commit requires the update of openstack-mkcloud.xml, check this first: https://github.com/SUSE-Cloud/automation/pull/1302

If this commit requires the update of openstack-mkcloud.xml, check this first: #1302

@aplanas: no it does not, same as PR #1317 did not require it. Both PRs only moved files around.
Anyhow the moving was split off of this PR into PR #1317. So its done now and I will rebase this PR.

@jdsn rebase?

@jdsn rebase?


Emphasis vs Link color

I noticed that you are using the same color for links and emphasis. It is a little confusing to have some things with that color be clickable and other things which are not. Especially since "emphasised and clickable" is probably exactly the same as "only emphasised".

Not a huge issue of course

I'm considering whether or not to add an underline to the links, not sure if it will affect the overall feel of it.

given how few websites use underlines for links nowadays I suspect that "it doesn't look good". But given that I am not a designer I don't know if a different color would be better or whether that would make the color palette to excited. You could of course remove the color entirely and let cursive speak for itself.
But given that you actually created a theme which "looks good" without knowing really why, I would trust your instinct better than mine.

I like having more coloured text, but there are already many links in my posts. Some reader might think non-clickable words are dead links. I made the following change:

I suggest not using any color for emphasis, like github and many other editors do. The italic font itself is the best way to "emphasis" the text.
The change can be easily done by removing codes in assets/scss/_fuji-theme/_style.scss.
strong,
em {
  color: var(--color-secondary);
}

Modded in 253850bb1f3b0faae8472f31a28725fec8684ffa


Upgrade rust 1.75.0

https://github.com/paritytech/srtool/pull/80

https://crates.io/crates/staging-xcm-executor/versions
There is no cargo.lock, staging-xcm-executor is upgraded to 7.0.3


Parameter defaults to null doesn't always make sense

https://github.com/hammer-tools/php-hammer/wiki/Inspections#parameter-defaults-to-null
I think in this case it doesn't make much sense to make it nullable. Wouldn't it be better to check that there are multiple variables with a default instead?

@DrowningElysium the idea of this inspection is that methods or functions never define default values (except null). So in your case it could work like this:
public function list(int|null $page = null): array {
    $page ??= 1;
    /** ... */
}

This methodology may not make sense for methods that are not intended to be modified in the future, but imagine the following situation: today your list(int $page = 1) method looks exactly like this, and if you don't specify $page then its value will be 1, which is expected (eg. just ->list()).
So imagine that you've made use of this method over and over by the system (without arguments), and in the future you decide to add a second parameter, like list(int $page = 1, Filter $filter = null). To use it, you will either have to set the value of $page, which is 1, or else you will have to make $page = null, so you can call ->list(null, $filter) like intended.
However, I'm convinced that maybe we can ignore simple situations, like functions that have a single optional argument, like your example, as it would easily be possible to convert them in the future, like in the example above. However, I would like to keep this option as optional. What do you think?

I think case with boolean arguments does not make sense even more
public function someFunction(bool $doSomeExtraThing = false)

This weekend I will try to work on these modifications and put them as optional. :)


Surface a way to provide custom stores

relevant code.
Alternatively, could surface a way for users to provide their own dwn instance

Alternatively, could surface a way for users to provide their own dwn instance

Yup let's do both


pantheon.appcenter: drop packagekit patch again

Motivation for this change
Closes https://github.com/NixOS/nixpkgs/issues/70214 (the third time!)
The dockitem for appcenter will not be displayed if you don't have appcenter installed.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg test pantheon


setOptions made a wrong check against the type of this.options.startDate

In the setOptions method, there's a line of checking if this.options.startDate is an instance of Date; however, it's an instance of the custom DateTime class. Thus this condition will never be true:
https://github.com/wakirin/Litepicker/blob/f29fdcb33916f1a4b60a44787eb556b7089aae3f/src/methods.ts#L314-L317
This bug prevents users from updating the startDate option manually.

Nice catch!
Fixed in v1.3.3


bugfix for issue #2476

Description
Brief Description of the PR:
bugfix for issue #2476
Type of change

[x] Bug fix
[ ] New Tutorial
[ ] Updated or additional documentation
[ ] Additional Testing
[ ] New Activation and the changes conform to the activation contribution guidelines
[ ] New Callback and the changes conform to the callback contribution guidelines
[ ] New Image addition and the changes conform to the image op contribution guidelines
[ ] New Layer and the changes conform to the layer contribution guidelines
[ ] New Loss and the changes conform to the loss contribution guidelines
[ ] New Metric and the changes conform to the metric contribution guidelines
[ ] New Optimizer and the changes conform to the optimizer contribution guidelines
[ ] New RNN Cell and the changes conform to the rnn contribution guidelines
[ ] New Seq2seq addition and the changes conform to the seq2seq contribution guidelines
[ ] New Text addition and the changes conform to the text op contribution guidelines

Checklist:

[ ] I've properly formatted my code according to the guidelines

[ ] By running Black + Flake8
[ ] By running pre-commit hooks

[ ] This PR addresses an already submitted issue for TensorFlow Addons
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] This PR contains modifications to C++ custom-ops

How Has This Been Tested?
If you're adding a bugfix or new feature please describe the tests that you ran to verify your changes:
*

Update: an updated commit is coming soon.

@seanpmorgan Please take a look.

I have summit tensorflow/tensorflow#51846 for solve the CRF issue under TF 2.4.


See references show unrelated results

In my screenshot I'll sepparate this repro into three files so the VSCode UI helps a bit to see the problem.
class A {
  void m1() {}
  void m2() {
    m1();
  }
}

class B extends A {
  @override
  void m2() {
    m1();
  }

  @override
  void m1() {
    print('B.m1');
  }
}

void f1(B m) {
  m
    ..m2()
    ..m1();
}

class C extends A {
  @override
  void m1 () {}
  @override
  void m2() {
    m1();
  }
}

Here you can see that in the above structure B and C are subclasses of A. In this example, m1 is called under A.m2, B.m2, C.m2 and under f1.
If you look for references of A.m1 you get all calls to it in the list.

Now the problem; if you ask for references for B.m1 or C.m1 you get the same unrelated results:

Here you can see that when asking for references of C.m1 I get instance calls that would never be C. Inside B and f1 in this case.
The same happens if you ask for references of B.m1, you get the call under C.m2 which could never be a B instance.

I'd like to ask for this to be worked on so that only B instances (or another subclass instance) would show. For C.m1 for example, I was expecting only the call inside A.m2 and C.m2. Definitelly not the call under f1 or B.m2.

@DanTup

If I'm understanding the example correctly, I think it is possible. Consider
class D extends C implements B {}

An instance of D could be passed to f1 and the methods in C would be invoked.
Because of the ability to implement almost any interface, it's very difficult to prove (in general) that it's impossible to ever invoke any override of an inherited method, so we don't try.
In other words, this is working as intended, and I think we're unlikely to attempt to change it.

I see your point. But this request does make sense for final/sealed classes.
I've just tested the same code and it gives the same results. With either C or B being final there was no possible case similar to what you suggested.
I would still like for it to scan the type hierarchy to try and find a match so that case is possible to show, but my feelings are not that strong and the code where I found this behaviour could easily be changed to final classes.
Just to be clear, I would expect that result of ..m1() to show up in either B or A and there is a way to "go to super" so in C we could get there.

One more thing:
Your example is flawed considering that both B and C could have gotten a method with the same name and signatures that didn't match like int a({required num v}) => v.toInt(); and String a(dynamic v) => v.toString(); (here the named parameter would make them not even be able to use Never).
This would mean that (at least today) it is impossible to have a type that would match both, but the current "See references" would still show the same calls.

... this request does make sense for final/sealed classes.

Yes, certain combinations of final and sealed make sense, and we could consider adding knowledge of those modifiers to the algorithm.

You could also say it could in the future have a subclass ...

True, but a feature like this shouldn't try to reason about possible futures, only about the code that exists today.
The point of the example is that we can't definitively know whether ..m1() might invoke the implementation in C without doing a whole-world analysis, and a whole-world analysis is known to be too expensive (and the analyzer, by design, never assumes that it has the whole world available to it).
We could always find ways to improve the algorithm. Some of them might be performant and some wouldn't be. That then raises the question of whether we'd end up in an uncanny valley where the imprecision was worse than if we don't try to be so precise.

True, but a feature like this shouldn't try to reason about possible futures, only about the code that exists today.

That's more or less what your example and current implementation do here. They assume that C and B don't have conflicting declarations and show every call everywhere.
I know the costs can be high for analysis but this can be really confusing.
I opened this issue after a talk with DanTup on the extension Discord about the following image:

I'm looking for the references for this inuteis getter. It overrides a base Dao class that every other class in the right extends. I was expecting to see this class and others below it (and uses), not its "siblings". In my case, none of these has a subclass and all of the calls for inuteis happen inside this single file so I was really thrown back by the number of resulting references I got until I understood what was happening.

I hadn't considered the point Brian made above when we first discussed this (a class using implements) so I agree, I think it would be wrong to filter these out. If you can possibly construct code that would be called at that location, then not considering it a reference would look like a bug.
There have been requests to VS Code/LSP to allow these kinds of results to be grouped. I don't know if that would really help here (because I'm not sure what the groups would be), but maybe if it's ever implemented we could come up with a way to split/prioritise the results in a way that makes sense? 🤔

we could come up with a way to split/prioritise the results in a way that makes sense?

Even though I like the idea, I don't think it would make much sense. For the splitting to make any difference for this case we would need to have the full analysis anyway so until we decide that is needed/will be implemented, it won't make much sense I don't think.
I'll leave this open for the request to consider final/sealed classes on the analysis at least. Thanks for your thoughts!


vimeo password option is broken

youtube-dl --verbose --video-password bernie2016 'https://vimeo.com/141725998'

[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'--video-password', u'PRIVATE', u'https://vimeo.com/141725998']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.10.09
[debug] Python version 2.7.10 - Linux-3.16.0-4-amd64-x86_64-with-debian-stretch-sid
[debug] exe versions: avconv 2.7.1, avprobe 2.7.1, ffmpeg 2.7.1, ffprobe 2.7.1, rtmpdump 2.4
[debug] Proxy map: {}
[vimeo] 141725998: Downloading webpage
[vimeo] 141725998: Extracting information
[vimeo] 141725998: Verifying the password
ERROR: Wrong password: HTTP Error 401: Unauthorized (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "/home/joe/bin/youtube-dl/youtube_dl/extractor/common.py", line 329, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/home/joe/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1872, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python2.7/urllib2.py", line 437, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 550, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 475, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

It says "Wrong password" but it works in the browser.

This issue is already fixed and will be available in the next version of youtube-dl.


Create CRUD Restful API Calls

As a developer
I need to create CRUD Restful API Calls
So that we can perform various actions on our data sources.
Acceptance Criteria:
I should be able to add, remove, view and edit products in the shopping cart

Should we think about breaking this issue into more manageable chunks? At least one for each of create a shopping cart, view a shopping cart, update a shopping cart, and delete a shopping cart?

@WesPainter @Pratik-Karnik @trc311 I think we can basically reuse the pet flask example program and make some naming change. That can be our starting point, what do you guys think?

@senongtor Thats what I was thinking initially but when we do a GET then do we get all the shopcarts of the customers or do we get all the items in a particular shopcart. We will have to freeze on our functionality first.

Well, it is a hierarchichal structure.  At the top level, we have shopping carts.  Within them we have products, and each product has its own attributes.  So if we do GET /shopcarts, it should return a list of shopping carts.  Then if we do GET /shopcarts/id/products, it will return all products associated with the sopping cart at that ID. Getting shopcarts by user ID would be something like /shopcarts?uid=1234.
Since it is hierarchichal, I figured we could start with shopping carts and work inward.  Start simply by defining a shopping cart object, then allow GET, PUT, and DELETE.  Then we can add products, and implement updates as changes to the products in the cart.

shopcarts - uid1 - product1; unitprice; quantity
- product2; unitprice; quantity
....
- uid2- ....
- ....
@WesPainter @Pratik-Karnik I think it'd be like that
So when we visit /shopcarts it should return every shopchart of each customer i think
then GET should get a shopcart for a user (shopcarts/userid), POST should add a product to a cart for a specific user, and PUT will update a product for a specific user, etc.

@senongtor Wont the each User have just one shopcart though?

@WesPainter I agree with your point. Seems quite logical.

@WesPainter @Pratik-Karnik
Agreed, except I think we shouldn't necessarily restrict each uid to one shopping cart.  It's an artificial restriction, and could hinder future features (like saving a shopping cart)
So for the base url /shopcarts:
GET /shopcarts - returns all shopping carts
POST /shopcarts - creates a new empty shopcart
PUT /shopcarts - update a shopping cart (CRUD a product in that shopcart

@Pratik-Karnik Yes each user will have one shopcart but I am imaging the shopcarts resource will contain all the carts for each user and we have to specify an userid to acess to his cart

@WesPainter ok so PUT will handle all the update cart(update products quantity maybe), add to cart, remove from cart


FYI: ASAP in papers we love

💥  https://github.com/papers-we-love/papers-we-love/pull/446

:raised_hands:


chore: Use validate-semantic-pr workflow from keptn/gh-automation repo

This PR

Updates the validate-semantic-pr workflow to use the action stoerd in the keptn/gh-automation repo

superseeded by #77


Use automasking for seq2seq training

Use automasking to create ragged batches for the seq2seq example. This ends up simplifying especially the Encoder significantly since we do no longer have to keep track of hidden state of all eos_id tokens.
In this PR, I only use automasking during training and evaluation, but we can extend this for decoding. I plan to do this in a follow-up step.
Thanks to @mattjj and @j-towns for making this great technology possible! Especially thanks to @j-towns for guiding me through all the bugs and error messages.

Note: the accuracy is not as good as before yet (it only reaches about 70%), so I am debugging the reason why. I expect there is some bug in padding, or in computing the loss, since the loss doesn't go below 0.2 (before it was 0.005). Moreover, decoding never seems to give a correct answer.
Example output of current run:
I0908 20:25:31.590295<PHONE_NUMBER>81824 train.py:384] train step: 7200, loss: 0.2025, accuracy: 61.72
I0908 20:25:31.604599<PHONE_NUMBER>81824 train.py:345] DECODE: 81+807 = 870 (INCORRECT) correct=888
I0908 20:25:31.604734<PHONE_NUMBER>81824 train.py:345] DECODE: 51+98 = 1006 (INCORRECT) correct=149
I0908 20:25:31.604794<PHONE_NUMBER>81824 train.py:345] DECODE: 50+847 = 878 (INCORRECT) correct=897
I0908 20:25:31.604840<PHONE_NUMBER>81824 train.py:345] DECODE: 6+856 = 648 (INCORRECT) correct=862
I0908 20:25:31.604883<PHONE_NUMBER>81824 train.py:345] DECODE: 53+715 = 746 (INCORRECT) correct=768

Codecov Report

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

@@           Coverage Diff           @@
##           master     #454   +/-   ##
=======================================
  Coverage   74.26%   74.26%
=======================================
  Files          54       54
  Lines        3944     3944
=======================================
  Hits         2929     2929
  Misses       1015     1015

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 e119c9f...9da94fe. Read the comment docs.


⚠ ClamAV has degraded performance

In ee479af, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 173 ms

Resolved: ClamAV performance has improved in fcc54dc.


skipCodeGeneration always inlines HTML templates

Bug Report or Feature Request (mark with an x)
- [X ] bug report -> please search issues before submitting
- [ ] feature request

Versions.
@angular/cli: 1.1.3 (e)
node: 6.10.2
os: win32 x64
@angular/animations: 4.2.4
@angular/common: 4.2.4
@angular/compiler: 4.2.4
@angular/core: 4.2.4
@angular/forms: 4.2.4
@angular/http: 4.2.4
@angular/platform-browser: 4.2.4
@angular/platform-browser-dynamic: 4.2.4
@angular/router: 4.2.4
@angular/cli: 1.1.3
@angular/compiler-cli: 4.2.4
@angular/language-service: 4.2.4
Repro steps.
ng new blat
ng eject
webpack // Build
view code in main.bunde.js verify HTML is inline
edit webpack.config.js set AotPlugin.skipCodeGeneration = false
webpack // Build
view code in main.bundle.js verify that HTML is still inlined but code is drastically different
The log given by the failure.
Unexpected results, I expected one of the settings to leave the templatUrl code intact and replace it with a require('app.component.html').
Desired functionality.
Perhaps this is just my misconception of what skipCodeGeneration does but the documentation says that it replaces templateUrl with template: require().  So I was expecting skipCodeGeneration = true to not replace templateUrl with the template and instead load it from the server.  Possibly this isn't a bug but a clarification point in the documentation if it is expected that HTML assets will always become inlined.

skipCodeGeneration controls whether or not you get AOT compilation. Templates are always inlined.


Support named connection strings when IConfiguration is in the app service provider

Issue #7185
This change allows code like this:
.AddDbContext<MyContect>(
   b => b.UseSqlServer("name=ConnectionStrings:DefaultConnection"))

Assuming the IConfiguration is found in the same service provider as AddDbContext is used on, then this will find "ConnectionStrings:DefaultConnection" and use it as the connection string.
Should work for all relational providers.

Should it also look in App.config on .NET Framework (and other frameworks that support it)? (Or, is there bridge between IConfiguration and ConfigurationManager?)

@bricelam Yes, ideally it should do that. @divega sent a question to Immo about this. My intent was to support IConfiguration now and open a new issue to support app.config as well. I suspect it will require us to start cross-targeting again, but let's see.

@ajcvickers @bricelam re System.Confuguration, I heard we can use https://www.nuget.org/packages/System.Configuration.ConfigurationManager/, but not sure about the details of what this does when the app runs on .NET Core.


fix: prevent refetch after post

Adding the staleTime is the real fix. Adding useMemo to the useDataValueSetQueryKey doesn't really fix anything, but could prevent issues in the future since having a stable query key for a single selection makes sense.

Closing this one in favour of #159


Added assert_passed_params classmethod for luigi.Task

Description
Added a simple classmethod that raises assert error when not all expected kwargs passed on to a luigi.Task.
Motivation and Context
I find it useful when we want to be sure that the upper tasks is passing on all expected/needed parameters to the required subtasks.
I ran my jobs with this code and it works for me.

this should just be a static method in luigi.util or something like that  – no reason to make it a method


Servlet filter for authorization header validation

This PR provides a solution to the issue where an NPE is thrown by CXF transport exposing the stack-trace and server information to the end user for broken authorization headers. AuthorizationHeaderValidationServletFilter validates the authorization headers before it reaches CXF level and sends a proper error response back to the user for invalid header formats.
Fixes https://github.com/wso2/carbon-deployment/issues/274

@emswbandara ,
Since this fix is identity related, I would be good to get this first by the IS Team as well.
WDYT?

@DilanUA this fix was already reviewed and merged in identity-core. https://github.com/wso2/carbon-identity-framework/pull/988/
but we need to move this to carbon-deployment to make sure it's available platform wide across all products without any dependencies to identity-core
https://wso2.org/jira/browse/IDENTITY-6364


sRGB images and hasAlpha

currently getting metadata of an sRGB image returns that it has four channels, and this is maybe why the hasAlpha check here returns true.
here is a log
metadata { format: 'png',
  width: 315,
  height: 315,
  space: 'srgb',
  channels: 4,
  density: 72,
  hasProfile: true,
  hasAlpha: true,
  icc: <Buffer 0 ...
}

Hello, this looks like the output I'd expect for an sRGB PNG image that contains an alpha transparency layer (the four channels are red, green, blue and alpha). Does this match with the image you're using?

after checking it seems that it has an alpha channel, but no transparency. I guess I conflated alpha with transparency. any advice on how to check for transparency besides the obvious loop over each pixel?
here is the output of identify:
identify -verbose /Users/samy/Desktop/H1g9uVzu.png
Image: /Users/samy/Desktop/H1g9uVzu.png
  Format: PNG (Portable Network Graphics)
  Mime type: image/png
  Class: DirectClass
  Geometry: 315x315+0+0
  Resolution: 28.34x28.34
  Print size: 11.115x11.115
  Units: PixelsPerCentimeter
  Type: TrueColorAlpha
  Endianess: Undefined
  Colorspace: sRGB
  Depth: 8-bit
  Channel depth:
    red: 8-bit
    green: 8-bit
    blue: 8-bit
    alpha: 1-bit
  Channel statistics:
    Pixels: 99225
    Red:
      min: 0 (0)
      max: 255 (1)
      mean: 114.721 (0.449885)
      standard deviation: 64.9489 (0.254701)
      kurtosis: -0.733505
      skewness: 0.424506
      entropy: 0.94251
    Green:
      min: 0 (0)
      max: 255 (1)
      mean: 125.446 (0.491944)
      standard deviation: 64.7183 (0.253797)
      kurtosis: -0.719933
      skewness: -0.111517
      entropy: 0.938506
    Blue:
      min: 0 (0)
      max: 255 (1)
      mean: 154.604 (0.606289)
      standard deviation: 73.6238 (0.288721)
      kurtosis: -0.910429
      skewness: -0.650536
      entropy: 0.945023
    Alpha:
      min: 255 (1)
      max: 255 (1)
      mean: 255 (1)
      standard deviation: 0 (0)
      kurtosis: 0
      skewness: 0
      entropy: 0
  Image statistics:
    Overall:
      min: 0 (0)
      max: 255 (1)
      mean: 98.6925 (0.387029)
      standard deviation: 58.7947 (0.230567)
      kurtosis: 3.67942
      skewness: 0.629073
      entropy: 0.70651
  Rendering intent: Perceptual
  Gamma: 0.454545
  Chromaticity:
    red primary: (0.64,0.33)
    green primary: (0.3,0.6)
    blue primary: (0.15,0.06)
    white point: (0.3127,0.329)
  Background color: white
  Border color: srgba(223,223,223,1)
  Matte color: grey74
  Transparent color: none
  Interlace: None
  Intensity: Undefined
  Compose: Over
  Page geometry: 315x315+0+0
  Dispose: Undefined
  Iterations: 0
  Compression: Zip
  Orientation: Undefined
  Properties:
    date:create: 2016-07-24T16:00:50+03:00
    date:modify: 2016-07-24T15:58:38+03:00
    png:iCCP: chunk was found
    png:IHDR.bit-depth-orig: 8
    png:IHDR.bit_depth: 8
    png:IHDR.color-type-orig: 6
    png:IHDR.color_type: 6 (RGBA)
    png:IHDR.interlace_method: 0 (Not interlaced)
    png:IHDR.width,height: 315, 315
    png:pHYs: x_res=2834, y_res=2834, units=1
    signature: 551fda4b6b84eecff094d9b4d22f946e9ef540c0fe85d55679e78fdbb4d073d9
  Profiles:
    Profile-icc: 2428 bytes
  Artifacts:
    filename: /Users/samy/Desktop/H1g9uVzu.png
    verbose: true
  Tainted: False
  Filesize: 145KB
  Number pixels: 99.2K
  Pixels per second: 9.923MB
  User time: 0.000u
  Elapsed time: 0:01.009
  Version: ImageMagick 6.9.3-6 Q16 x86_64 2016-02-28 http://www.imagemagick.org

Looping is probably your best bet, perhaps with the use of extractChannel to make it a little more efficient.

Awesome ... thanks.


Always reporting an error invalidframeexception: bad RSV rsv1: true rsv2: false rsv3: false code:1002 what is the reason?

Describe what you would like to know or do
A clear and concise description of what the problem is.
Describe the solution you'd considered
A clear and concise description of any solutions you've considered.
Additional context
Add any other context or links about the question here.

What library version are you using? This looks like it might have been fixed in #1232 which was released with version 1.5.3.


Fix npm usage

As discussed in both #75 and #91, in particular this comment. We can not use environment variables to reliably access npm configuration settings, instead we must require in the npm module and use its api.
This supercedes other pull requests that were trying to do the same thing.
Fixes #91
Closes #75

Also closes #55

Also fixes #67

Big -1 on requiring npm, its a very heavy dependency. I'd rather drop support for npm configuration altogether and rely on command line flags and environment variables than add more dependencies to this module

@maxogden fair enough.  I actually just dug into this a lot deeper with a co-worker and it turns out there is a bug in npm where false values are always set to an empty string and true values are set to true.  Which means this entire thing can be fixed much easier by comparing npm_config_strict_ssl to the string true.  I'm going to rollback my changes and squash my commit with that single change and it should fix the issue.
Here's the npm code bug if you're curious: https://github.com/npm/npm/blob/94929cf05854886b1aa9b611ad3bbb6dbbb575f3/lib/utils/lifecycle.js#L349 I'm going to open a PR there as well (but my fix for this will continue to work after that).

@maxogden My much simpler and equally correct fix is now in.  Let me know if you still have any concerns.  Thanks.

@mramato haha nice. LGTM :)

it will get published the next time electron gets released

Awesome, thanks.

:+1: good work sir


Install Documentation Update: '--cask' not 'cask'

The more we know about your system and use case, the more easily and likely we can help.
Environment info

OS: Mac OS XI
App Version: N/A

Description of the problem / feature request / question:
GitHub install instructions read:

Install via Homebrew (macOS)

brew cask install lepton
As of brew 2.7.0, per this brew issue

brew cask <command> was deprecated in favor of brew <command> --cask

Install documentation should reflect this change.
Log
==> Tapping homebrew/cask
Cloning into '/usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask'...
remote: Enumerating objects: 35, done.
remote: Counting objects: 100% (35/35), done.
remote: Compressing objects: 100% (25/25), done.
remote: Total 548126 (delta 16), reused 21 (delta 10), pack-reused 548091
Receiving objects: 100% (548126/548126), 241.73 MiB | 1.46 MiB/s, done.
Resolving deltas: 100% (387090/387090), done.
Tapped 3806 casks (3,927 files, 259.3MB).
Error: Calling brew cask install is disabled! Use brew install [--cask] instead.

Looks like this has already been updated: https://github.com/hackjutsu/Lepton#installation


[Constant Evaluator] Improve assertion failure and condfail_message support in constant evaluator

Pass assert configuration option to the constant evaluator in order to precisely evaluate Builtin.assert_configuration.
Unify UnknownReason::Trap and UnknownReason::AssertionFailure error
values in the constant evaluator, now that we have 'condfail_message'
SIL instruction, which provides an error message for the traps.

@swift-ci please test and merge


Output suggestion.

Hi, Pedro! I wold suggest to replace if(mod(istep,iout1d) == 0)  by if(iout1d > 0.and.mod(istep,iout1d) == 0), and also for iout0d, 2d, 3d, save. When no output is needed, we can just set iout1d=0 in input.nml. This should be more user-freindly than setting very large numbers for no output.

Hi Mao,
Great idea! Would you like to submit a PR? Else, I can do it next week.

Sure!

Thanks Mao for your contribution!


Add Back to top Button

Back to top button Improved User Experience: It allows users to easily navigate back to the top of the page, especially on long-scroll pages.

Ok you can add it

can i do this

If @sambedan1 dont want to do @RishabxBhardwaj can do

Can I please try fixing this?

@sambedan1 Are you working

yes

Any updates @sambedan1

Unassigning as you didnt reply!

assign it to me

@kom-senapati  assign this issue to me. Will add in client app

You both try
@RishabxBhardwaj try on html files
@priyanshuverma-dev try on client app


Getting 500 internal for payload validation failure

Hi,
We are using swagger for the code generation for the REST API. We have provided some patterns in the swagger file. If these patterns fail because of wrong value, we get 500 internal server error. This call does not even come inside the POST call in the controller, hence we are not able to provide a custom error.
Will it always throw 500 in case the payload is not valid? We have given the pattern for the date field.
Is it possible to give a custom error in the swagger file?
Thanks,
Neha

Based on the question, it seems like this is not related to swagger-core. Which tool do you use?