odata-cli docs

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

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:bulb:Suggestion
View
Details

Odata-docs/odatacli/getting-started.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 21b80ba:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:warning:Warning
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 71, Column 21: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/odata/connectedservice/getting-started#using-the-generated-code' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.
Line 71, Column 21: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/odata/connectedservice/getting-started#using-the-generated-code' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f0a5d16:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:warning:Warning
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 71, Column 21: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/odata/connectedservice/getting-started#using-the-generated-code' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.
Line 71, Column 21: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/odata/connectedservice/getting-started#using-the-generated-code' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit de7281e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:warning:Warning
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 5, Column 9: [Warning: author-not-found - See documentation] Invalid value for author: 'elokerio' is not a valid GitHub ID.
Line 71, Column 21: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/odata/connectedservice/getting-started#using-the-generated-code' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 71, Column 21: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/odata/connectedservice/getting-started#using-the-generated-code' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit fe91f64:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:warning:Warning
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 71, Column 21: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/odata/connectedservice/getting-started#using-the-generated-code' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.
Line 71, Column 21: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/odata/connectedservice/getting-started#using-the-generated-code' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6536be7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:bulb:Suggestion
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:bulb:Suggestion
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:bulb:Suggestion
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 72b8d4d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:bulb:Suggestion
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 89def4a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:bulb:Suggestion
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6b36ff4:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Odata-docs/odatacli/getting-started.md
:warning:Warning
View
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md

Line 20, Column 130: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-tool-install' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 30, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Synopsis''. Each second level heading (H2) in an article must be unique.
Line 40, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Options''. Each second level heading (H2) in an article must be unique.
Line 56, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Synopsis''. Each second level heading (H2) in an article must be unique.
Line 65, Column 1: [Warning: duplicate-h2s - See documentation] Duplicate heading: 'H2 'Options''. Each second level heading (H2) in an article must be unique.
Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ElizabethOkerio' is not a valid Microsoft alias.
Line 20, Column 130: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-tool-install' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 86423b6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 4f5189f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1af65af:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 500def7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

Odata-docs/odatacli/getting-started.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Failed to start app in Android

Hi, I've followed the guide to try to init AwesomeProject, however, it failed to start with the error
/Users/raymond/workspace/AwesomeProject/node_modules/react-native/packager/transformer.js:32
    filename,
            ^
SyntaxError: Unexpected token ,
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:411:25)
    at Object.Module._extensions..js (module.js:446:10)
    at Module.load (module.js:353:32)
    at Function.Module._load (module.js:308:12)
    at Module.require (module.js:363:17)
    at require (module.js:382:17)
    at process.<anonymous> (/Users/raymond/workspace/AwesomeProject/node_modules/react-native/node_modules/worker-farm/lib/child/index.js:45:34)
    at emitTwo (events.js:87:13)
    at process.emit (events.js:169:7)

When I check the file transformer.js
  const result = babel.transform(src, {
    retainLines: true,
    compact: true,
    comments: false,
    filename,
    whitelist: [
      // Keep in sync with packager/react-packager/.babelrc
      'es6.arrowFunctions',
      'es6.blockScoping',
      'es6.classes',
      'es6.destructuring',
      'es6.parameters',
      'es6.properties.computed',
      'es6.properties.shorthand',
      'es6.spread',
      'es6.templateLiterals',
      'es7.asyncFunctions',
      'es7.trailingFunctionCommas',
      'es7.objectRestSpread',
      'flow',
      'react',
      'react.displayName',
      'regenerator',
    ],
    plugins,
    sourceFileName: filename,
    sourceMaps: false,
    extra: options || {},
  });

It seems that this json is kinder broken, 'filename' and 'plugins' with nothing?
 System Darwin 14.4.0
gyp ERR! command "/usr/local/Cellar/iojs/1.8.1/bin/iojs" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/raymond/workspace/AwesomeProject/node_modules/react-native/node_modules/ws/node_modules/bufferutil
gyp ERR! node -v v1.8.1
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>
Thanks!

It seems that this json is kinder broken, 'filename' and 'plugins' with nothing?

It's the ES2015 object shorthand notation. Basically, when both the key and value have the same name, you can just write the name.
Have you tried removing your node_modules folder and running npm install again?

This is most likely caused by the error that occurred during your init. Please try:
$ rm -rf node_modules/
$ npm install

Hopefully this time there won't be an error. Looks like there was a 404 the first time which sounds like an issue with npmjs.com. If all goes well try running this again:
$ react-native run-android

And let us know if it works.

If that doesn't work, try upgrading to Node 4 and installing via nvm, n, etc.

If a request fails to npmjs.org, we should abort the install process and display an appropriate message instead of just continuing on.

In iOS, I meet the same problem. Now, I try to remove the node_modules and  Install angry.

@foghina No luck, my workaround right now is to explicitly setting filename and plugins to
filename: filename
plugins: plugins

Same issue on IOS
$ rm -rf node_modules/
$ npm install
gives no joy. I'll go with am5a02 for now

Finally, I update & upgrade everything by:
'brew update && upgrade'
then rebuild the project, Now everything seems OK, perhaps this is the bug for some version.


Add AdminKit

Please run the screenshots through https://kraken.io/web-interface (lossless) or lossy if it still looks good.

Also @jdorfman is there any discussion I'm missing about this?

The images are bigger now :P

@paullaros I squashed your patches, so make sure you don't overwrite the changes.
I wait for @jdorfman to chime in.

@XhmikosR Thanks!

Sure! Thanks 👍

@paullaros please squash all the patches :)

@XhmikosR merge whenever thanks @paullaros


google acc enable insecure access not possible anymore

In the "How to setup the insta360-auto-converter config file", step 4 is to enable insecure access, which is not possible anymore.
Does it also work with (enabling 2 factor authentification and then) adding an app password? If yes, this would be the solution for the tutorial. If no, is there any [solution?

Hi @tiemes did you manage to get around this?
If not I fancy taking a look into this.

Hi @Robsodd , I'd still be interested in a solution. I created an app password instead but got stuck in the process somewhere later. I never managed to realize a successfull transcode.


[0.2.4] wire up 2.7 in CI

Either replace 2.6 or add a new job, possibly begin using the Pipelines runners rather than Travis

They've fucked compatibility as usual, this isn't being done for 0.2.4


Store Smesher log on fs

Rationale
The smesher log should show relevant log messages, such as:

start time
pause/resume events
rewards
errors

Most of these events can't be retrieved from the Node by the current GRPC API and maybe never will be.
Smapp should create the log on his own and keep it actual.
In case post data deletion or changing Smesher ID the log should be dropped.
In other cases, it should be updated with proper messages.
User story

[ ] Run Smapp
[ ] Setup smeshing
[ ] The log should have a message with time when the creation of Pos data started
[ ] Then there should be a message when it is done and started smeshing
[ ] If User paused/resumed smeshing it should be there
[ ] If some error occurred in the Smeshing process, it should be there
[ ] If User got a reward for smeshing — it should be there
[ ] If the User cleaned up all app data on his PC and runs Smapp (from scratch) — the log should be empty (@avive ?)
[ ] If the User removed only key.bin file — the log should be empty (@avive ?)

Acceptance criteria

[ ] The smesher log should be stored in the persistent store
[ ] The log should be updated by the main process (not components)

Out of scope
Encryption of the log. Probably we don't need it all, since we're not encrypting smesher-coinbase in the node-config.json.
How to implement

Store the log file on fs, instead of localStorage
Manipulate the log file from the separate service (SmesherLogService)
SmesherManager is a consumer of SmesherLogService
SmesherManager will put the log through IPC

How to test
We can test SmesherLogService for:

it adds lines to the log,
read the log,
cleans it up if needed.

Low-priority feature which is a left-over from an old design.

I still think we shouldn't build this feature in Smapp yet. I think it is much more important to allow users to submit an error report that will include the node and smapp logs as uploads. We should compress the huge node logs file before uploading and have a centralized place to review such errors and logs.

I think that this log should go into the Smapp log file and that we should add some of the info you include in the issue in a more concise way to users in the smesher screen.

Smesher log is back and it changed a look: https://github.com/spacemeshos/smapp/pull/925
But implementing of proper smesher log (and logging rewards as well) is still actual.

Not actual anymore.


Create a parent child view

Hi,
I need help to create a view like https://support.content.office.net/en-us/media/8d712f52-0c4e-4a04-9ffa-7c04cfd75905.jpg
The main form has the parent and the subform has the child records.
Where do I begin?

The image is not available!!
Feel free to create your own blade layouts, check laravel docs (Blade template)


:+1: Add isNonNullable

Add a predicate function that corresponds to Typescript's NonNullable utility type.
As you know, the argument of this function is generic type and is not unknown. So I'm not sure if it's allowed to include this in unknownutil.
I also considered adding the isNonNullableOf() function. However, I am concerned that it may be confusing with the isUnwrapOptionalOf() function.

The anguish of both contributors and owners is understandable.
First, given the concept of unknownutils, one would expect isNonNullable to inspect uknown except nullish. However, it is not possible to obtain the type complement in an informative way. In other words, it is not possible to construct a type that is unknown except nullish. Therefore, the contributors attempt to realise non-nullable on the condition that the argument is a type that is not unknown. I understand that this is a limitation of the current typescript.
By the way, this isNonNullable has a bug. It means that the condition "non-nullable types as arguments", which is implicitly assumed by the contributors, cannot be written in typescript. In other words, it is not possible to prohibit passing unknown as an argument to isNonNullable. So, if we are to be honest, this change makes unknownutils an incomplete library, as it is intended to mechanically validate types, but it also means that the user has to be conscious of the restrictions in order to get it to work properly.

I reconsidered that it is better not to add isNonNullable() since it does not give a useful type in combination with isXOf(pred).
const strOrNullArray: (string | null)[] = ["a"];
if (isArrayOf(isNonNullable)(strOrNullArray)) {
  // Expect strOrNullArray is narrowed to string[], but it resolves `(string | null)[] & {}[]`
  const _: string[] = strOrNullArray;
}


Add status

Che crudeltà

On 23 Nov 2019, at 11:38, Giulio Canti<EMAIL_ADDRESS>wrote:
Closed #975.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


integrate DCAP SgxStatus change in pallets

no state migration needed as there is no love solo network

done. releasing integritee-node 1.1.3


Not minifying when @import file has timestamp

When there is a query param on a css file (in this case a timestamp), clean-css-cli will not minify the current file. As soon as I remove the query param, it minifies the file. My goal is to ignore the @import statement but still minify the file.
I tried passing every conceivable option to prevent the clean css from processing this line:
@import url(font_awesome.css?t=1554926691456);

But it throws the error:
Ignoring local @import of "font_awesome.css?t=1554926691456" as resource is missing

Closing as 'won't fix' as clean-css-cli is going into maintenance mode. If anyone wants to bring it back up, please submit a PR.


How to rebase a binary dump to enable pointer traversal?

Is there any way to rebase a binary dump so that the pointers in the dump can be resolved correctly?

Isn't there a way to LoadLibraryEx the dump to let Windows rebase it? The same as the DllHelper application of OllyDbg to load dll files.

I'm not on Windows. I'm analysing an Android memory dump (32 bit) on ReClass x86. I managed to get it running partially thorugh wine (though it crashes very often, unless I uncheck show pointers).  It's pretty unusable as any kind of nesting is impossible and causes the program to crash instantly.
Rebasing should be a matter of shifting address in the main application view, and would be immensely helpful as it would enable traversing pointers that are in the same memory dump.


exp

10s to compute
i guess we should implement a scheduler which compute embeddings when user is sleeping
https://huggingface.co/google/siglip-large-patch16-256
@m13v

10s for one frame?


Text Field with resize css

https://try.mudblazor.com/snippet/cEmburGBKeyNOlHx

Please make a suggestion how the API could look like. I guess it would be primitively easy to add

@henon @StephenOTT  I think its not as easy as in this example. This example only allows to resize the box, but lines are same and align centered.
All examples with autosize built with js, i don't see any no-js solution.

TextField got an AutoGrow property semi recently
https://mudblazor.com/components/textfield#multiline-auto-grow


pythonPackages.redis: 3.1.0 -> 3.3.4

Motivation for this change
out of date on repology.
Added license.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@GrahamcOfBorg build python3Packages.redis

Thanks!


Layout fix of choose parent page

Placed radiobuttons below each other instead of next to each other,
Changed > to Wagtail's arrow-right icon.

:+1:

Thanks for this. Always good to have a bit of help to spot/fix these little
things. I'll get in merged in soon.


Editor agnostic configuration

Is your feature request related to a problem? Please describe.
Currently, Contextive heavily relies on the .vscode folder to exist in order to manage the path location for Contextive definitions files. However, this approach does not work well, if at all, with other editors.
Describe the solution you'd like
I think to solve this, one must approach this problem in an agnostic way. One option could be to have a separate contextive.json file stored in the repository root. This file would contain the behavior-altering configurations, such as where to look for the definitions path for the Contextive language server. Instead of setting up language server client settings, the Contextive configuration would be handled separately.
Additional context
It may not be feasible to configure this within the language server client options, considering that many people use editors that don't rely on the .vscode directory. Moreover, it becomes impractical when working across multiple repositories with different path locations. In practical terms, this would require me to adjust my editor configuration every time I switch to a repository with a distinct Contextive path location.

Hi @erikjuhani - in theory, the language server should already be agnostic - it does rely on the LSP configuration methods, which may have mixed support in different IDEs.  Specifically, https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_configuration.
The intention is that the setting is stored in the repository using whatever the standard IDE's configuration mechanism is.  In VSCode it's a settings.json file in the .vscode folder, but in other IDEs it could be in another file - as long as the IDE supports storing a level of config in the repo it should work.
e.g. in neovim, as far as I can tell according to https://neovim.io/doc/user/lsp.html#vim.lsp.start_client(), there is a parameter called settings that:

settings: Map with language server specific settings. These are returned to the language server if requested via workspace/configuration. Keys are case-sensitive.

When working across different repositories, each repository should have it's own configuration pointing to the location of the file in that repository.
One issue with this approach is that if there are a mix of IDEs being used within a team, then each IDE would have it's own config storage... but I'm not sure yet how common a scenario that would be, or how bothersome teams would find it given that all other LSPs use this same approach for config.
Hope that clarifies the intended approach?

Thanks @chrissimon-au for clarification!
In our environment, we have a diverse group of individuals using various IDEs, including both those we are familiar with and those we may not be aware of. The current approach necessitates configuring each repository in advance, requiring us to be well-informed about the editors developers are using and create multiple configurations for each editor, depending on their support. This can pose a significant challenge, particularly in larger mono-repositories with over 40 developers working on them.
I believe that it would be more efficient if we adopt a separation of concerns approach. Many other tools manage their configurations through runtime config files, as an example eslint.

The approach of utilizing a separate configuration file aligns with the Project Local Config solution. This method is generally more developer-friendly, as the alternative options introduce additional tooling or personal settings configuration.

Hi @erikjuhani , ok, I can see the rationale now.  That Project Local Config page seems to offer 4 options, one of which is Use native server file configs, which is the approach you're requesting here, right?
If I understand correctly the other options don't align well with the goal of having the settings stored in the repo and having them apply without needing to do anything special for each developer with respect to how neovim manages settings?
And I agree, a native server file config would help with teams that are not all using the same tooling.
However, one of the biggest challenges with having a 'well-known file location' for a config file is you do have to support a number of options for finding it - e.g. in a multi-root workspace, which workspace should hold the file? You have to scan all workspaces? If each workspace has it's own file, that works fine because you could apply the settings per workspace, but if only one workspace has the file, is it intuitive that those settings should apply across all workspaces?
The LSP configuration mechanism includes a scope field that delegates the resolution of scope and settings location to the IDE to manage, as it is responsible for the multi-root workspace management.
There is some discussion on #38 about this challenge.
This whole conversation has further made me even question of having the path setting... if we have a fixed known location for a settings file, why not just make the definitions file in a fixed known location and remove all the configuration complexity?  At this time there are no other settings, and this extra indirection wouldn't add much value other than allowing you to put the definitions file in an arbitrary location (but at the expense of requiring a separate settings file in a fixed known location)...
I'll continue to ponder this.  I'm also currently working on the intellij platform extension, so I'll investigate further how that manages config to ensure we have a solution that works across all IDEs.

Hi @erikjuhani , ok, I can see the rationale now. That Project Local Config page seems to offer 4 options, one of which is Use native server file configs, which is the approach you're requesting here, right?

Yes exactly. The first option would be the most favorable out of the other ones presented there.

If I understand correctly the other options don't align well with the goal of having the settings stored in the repo and having them apply without needing to do anything special for each developer with respect to how neovim manages settings?

Yeah that is the problem. It's not really feasible to manage multiple editors / IDE for every repository separately. Instead it would be easier and more developer friendly to just have a "contextive" specific runtime configuration file.

And I agree, a native server file config would help with teams that are not all using the same tooling.
However, one of the biggest challenges with having a 'well-known file location' for a config file is you do have to support a number of options for finding it - e.g. in a multi-root workspace, which workspace should hold the file? You have to scan all workspaces? If each workspace has it's own file, that works fine because you could apply the settings per workspace, but if only one workspace has the file, is it intuitive that those settings should apply across all workspaces?

Yes it has challenges for sure, but I don't think it would add that much complexity. For exampleeslint prioritizes the closest runtime configuration file and uses "extends" to merge configurations.
So how it would work in theory:

Check if contextive.json is found in the current working directory

If yes stop and read configuration file

Traverse directory upwards until next contextive.json is found and repeat step 1
Stop traversal when root uri is hit

The LSP configuration mechanism includes a scope field that delegates the resolution of scope and settings location to the IDE to manage, as it is responsible for the multi-root workspace management.
There is some discussion on #38 about this challenge.
This whole conversation has further made me even question of having the path setting... if we have a fixed known location for a settings file, why not just make the definitions file in a fixed known location and remove all the configuration complexity? At this time there are no other settings, and this extra indirection wouldn't add much value other than allowing you to put the definitions file in an arbitrary location (but at the expense of requiring a separate settings file in a fixed known location)...
I'll continue to ponder this. I'm also currently working on the intellij platform extension, so I'll investigate further how that manages config to ensure we have a solution that works across all IDEs.

How would it work if the project is using some centralized contextive definitions solution and want to change the "default" location e.g. previously using the path setting? I think it's a great thing to have configurability as different projects have very different needs.

@erikjuhani, thanks again for this suggestion - having thought about this further, I do like this idea of a file in each folder that effectively contains a 'pointer' to the definitions file that applies to files in that folder (and subfolder).
However, we need to consider it carefully in relation to a variety of bounded context <-> repository/disk mapping layouts that exist and the current definitions.yml file paths setting.  These are:

Monorepo - all contexts in a single repo, usually separated by paths, but some paths needing to using definitions from multiple contexts
Repo per context
Multiple Repos per context

Current Approach Recap
Repo per context is probably the 'recommended' approach', but I do also like to support the monorepo approach as I think it's very valid in many scenarios.  Option 3 is strongly not recommended but is unfortunately very common.
The current definitions file includes a list of contexts, and each context has a list of paths it applies to.  This is to support option 1. Because the definition of which paths each context applies to is independent, multiple contexts can be easily applied to the same path (which supports the overlapping contexts scenario).
Option 2 is generally applied by just having a single context in the list, and each repo gets its own definitions file.
Option 3 is a struggle - I don't like the idea of encoding in one repo a relative or fixed path of a definitions file outside the repo - it presupposes an unmanaged disk layout that could be different on every machine.
So, the current support is via the suggestion that the canonical file is in a repo that houses a shared library or some common code that is distributed to the code in other repos via packages.  The definitions file should be included in the package and the consuming repos can configure their settings to indicate the location of the definitions file in the local packages folder (e.g. node_modules, or nuget packages or whatever).  This is the purpose of the go example repository, to illustrate this pattern.
Settings file in subfolders
Considering option 1, the monorepo, if we had a contextive.json file in an arbitrary folder, with a setting pointing at a definitions file, how should this work when the definitions file has multiple contexts in it?
Should we still only use contexts that have a paths field that includes the current path?  This could get very confusing if contextive.json pointed at a definitions file where none of the contexts included the current path.
Should the fact that a contextive.json file points at that definitions file make it implicity part of the paths setting?  If so, for which contexts in the file? Is it only meaningful for a single-context definitions file?
I'm kind of ok with this - we could move towards a structure where each context is in a separate file, and the contextive.json is present in the folders that point to that file.  This would make it even simpler for option 2, as there would only ever be a single context in a file.
How then to handle overlapping contexts?  perhaps contextive.json needs to contain a list of files, not just a single file.
Considering option 2, in theory every file in the repo should have the same definitions file - so there is limited value in allowing contextive.json to exist in subfolders, as there should be no subfolders that point to different definitions files.
Considering option 3, again, if the context is distributed across multiple repos, at least a single repo should belong to just that context - so in theory, limited value in allowing contextive.json to exist in subfolders.
Next steps
Given the above, it's not yet clear to me what will be the simplest approach.  Now that we can offer a custom definitions file location with neovim (see #58), I think this buys some time to consider the correct approach here.
So for now, I won't be making any immediate changes, but will continue to consider how to better handle the scenario where teams have mixed tooling/IDEs but need consistent configuration and may have a custom definitions file location.  Will leave this issue open until further decisions made.

Thinking further about the above, I'd like to propose the following approach:

Any folder can contain one or more %contextName%.contextive.yml definitions files which will contain only one context
The definitions automatically apply to any file in that folder or subfolders
If there is another *.contextive.yml file in a parent folder, then they merge (or the child-most folder takes precedence? TBD)
The file may include an import statement with the location of another definitions file - absolute, relative or even URL path

Examples
MonoRepo
.
├── ContextA/
│   ├── src/
│   └── contextA.contextive.yml
├── ContextB/
│   ├── src/
│   │   ├── antiCorruptionLayer/
│   │   │   ├── aclWithContextA.cs
│   │   │   └── importContextA.contextive.yml # contains an import with relative path to ../../../ContextA/contextA.contextive.yml
│   │   └── file.cs
│   └── contextB.contextive.yml
└── README.md

Repo per Context
ContextA repo
.
├── src/
├── contextA.contextive.yml
└── README.md

ContextB repo
.
├── src/
│   ├── antiCorruptionLayer/
│   │   ├── aclWithContextA.cs
|   │   └── importContextA.contextive.yml # contains an import with url to hosted contextA definitions
│   └── file.cs
├── contextB.contextive.yml
└── README.md

Distributed Context
Defintions Repo - contents need to get published to a url somehow
.
├── contextA.contextive.yml
└── README.md

Component 1 in Context A repo
.
├── src/
├── contextA.contextive.yml # contains an import to the url that the definitions are published to
└── README.md

Component 2 in Context A repo
.
├── src/
├── contextA.contextive.yml # contains an import to the url that the definitions are published to
└── README.md

Backwards compatibility
Contextive is currently major version 1.
I'd propose to implement this within major version 1 but retain support for existing .contextive/definitions.yml file as the priority, with a fallback to looking for files that look like the above approach if that file can't be found.
I'd also propose an automated approach to migrate the old definitions file structure to the new one, which should be fairly straight forward for the monorepo and repo-per context approach, but will likely need to be tackled manually for the distributed context approach.
We'd remove support for the original configuration approach with a major version bump to version 2.
Feedback welcome
Feedback welcome from any interested parties :)


Index creation support specify partition

During the online scenario, we found that current index create only support all table partition and each creation cost too much resources. Also we may only need to keep a nearest 7 days data indexed instead of all partitions indexed. The index create and drop command change to:
CREATE SINDEX [IF NOT EXISTS] indexName ON tableName (col1 [ASC | DESC], col2, ...)
[USING (BTREE | BLOOM | BITMAP)] [PARTITION (partcol1=val1, partcol2=val2 ...)]

DROP INDEX [IF EXISTS] indexName on tableName [PARTITION (partcol1=val1, partcol2=val2 ...)]

fixed in #247


Add a base 1rst model for a playable character

[ ] Base model added for tests

Sub related - Import

[x] Import Asset Textures
[x] Import Asset 3D Model
[x] Verify/Fix broken material on Import

Sub related - Character

[ ] Character custom blueprint created (should inherit from at least ThirdCharacter or a custom child)

[ ] Emergency Fix of third person character feature if needed to make this work

[ ] Custom blueprint uses imported mesh and materials
[ ] Create a custom Player Controller BP to be used with this specific test character BP
[ ] Create a custom GameMode to be used with this specific test character map (see created map in development folder)

Merged to main

[ ] Final and fixed asset files are accessible from main branch

Migrated Forest Huntress Character model (Paid on CGTrader)


Refs #20461 -- Dropped runtests' message about parallel processes.

(EDITED)
The actual number of processes isn't known until test_runner.run_tests() loads tests and determines how many TestCases will run.

It's good that I didn't merge my first attempt because it doesn't work....
I think we have to remove the message. The commit message explains why.

Alternatively the message could say "with up to X processes." (knowing that the number could be reduced if there are less test cases). I don't have a strong feeling either way.

"up to X processes" is smart. Let me try again :-)

I just pushed a new version. I did some manual testing. It appears to work.

Looks good.


Port to Azure Container Instance for Managed FaaS with True Pay Per Use

After using Fn Project on EC2 I looked into running Fn on the container services offered by the clouds I am working with...
Oracle's OCCS is not serverless, but Azure has a service preview of Container Instances that allows to start containers for €0.0022 per instance created. Currently this is only possible using the Azure command line with custom commands IMHO.
Not sure how Fn is starting deployed functions at the moment (I guess it must be via "docker run ..." ), but I could imagine that creating a connector for Container Instances (using "az container create --image ... " instead of docker run image) could almost be a quick win.

Fn API server could be easily started as a container on Azure CI (or even somewhere else?).
effort in porting the function/container invocation inside Fn to be compatible Azure CI would be low
Doing this, first time in history we had an open source serverless framework running 1:1 in a public cloud but still offering serverless characteristics of fully managed FaaS like Lambda, such as true pay per function invocation.

tempting?

If you're saying that the fn server could run it's function containers using Azure CI, that might be possible, but I there's a lot of things to figure out. How fast can it spin up containers?  How would you do routing? And probably a bunch of other things, not sure it would be worth the effort.
That said, I think it would be interesting to support a container instances type of functionality on Fn.


teamWaitingKey refactor to use teamID

I'll rebase to get the new conflict.

Resolved conflict with recent master changes.

Not currently.  Generator is to be used rarely if possible


Add a token limit flat to the command.

Add token limit flag and file limit, so output can be split by tokens
Update docs to support
Add requirements file.

This gives a solution for #35, #37. Perhaps #26

Tested with a huge repo using the following params and output:
-t 62000000 -m 20

Writing to file output_1.txt
Written 61963289 tokens to file.
Writing to file output_2.txt
Written 61914604 tokens to file.
Writing to file output_3.txt
Written 23705417 tokens to file.
Writing to file output_4.txt
Written<PHONE_NUMBER> tokens to file.
Writing to file output_5.txt
Repository contents written to 5 file(s).

output_4.txt is<PHONE_NUMBER> tokens which is greater than the specified 62000000 tokens.

If a source file is larger than the given output token limit, there are only a few options.

Ignore the token limit, and output the complete file (This is the current method chosen. That's why you might be seeing a file going above the token limit)
Split input file to multiple output files
Ignore that file


Starting construction on a dirwindow and then moving makes you unable to construct that window.

Description
What it says on the tin.

Additional context
Discovered during a round on Wizard's Den Lizard

Fixed by #14609


Transition argument in toNamed

Is it possible to add transition property to toNamed method as it is in to?

Hi, I think that, at least logically, the transition on named routes should be inserted into GetPage statically.
It would not be difficult to implement this, but it would certainly bring unnecessary computational logic involved, basically before toNamed would have to copy the current route to a variable, remove the route from the list, give Get.addRoute (route with new transition)) and only then push the route. This is likely to have performance implications for larger applications, as well as evading an already established structure pattern. If someone else should take a project that you’re currently doing, they’ll know they’ll have to change the transition on the directions page. If you define this in your Get.toNamed, it will not know where to define the transition. I think it would mess up the code a bit, and it would make no sense (at least for me), to use Get.toNamed() in this situation, if Get.to() would have exactly the same behavior. I think that if you want to delegate the responsibility of defining transitions when pushing a route, you should use Get.to instead of Get.toNamed, because it was made for that and will have no performance implications. Named routes were created precisely to centralize and configure the behavior of the route in one place.
Therefore, my vote is not to implement this feature, first for structural reasons, and second for the cost benefit related to performance. This is not something that causes an application to freeze, but it is something that will clearly make ram consumption go up when pushing a route, especially in larger applications.
This may change in the future with navigator 2.0. But for now, this is my opinion on.

Ok, no issues. Just wanted to know why it is not there. Thanks for explaining. Closing the issue.


Presentation Exchange Context: JSON-LD Frame

This PR adds language describing a frame property to be added to a presentation definition so that this spec properly supports selective disclosure of attributes in the same way it is supported in other protocols.

What sort of considerations were made around making sure the frame matches the input descriptors? For example, if a requestor messes up the frame the holder may return a different VC response when relying upon the input descriptors rather than the frame. Is there anything that we should be including to make sure these are matching?

@kdenhartog  I've added text to address this in 96bd4cc


Only sync a single provider on Heroku review apps

This is to stop the deluge of daily emails that warn about us reaching the database row limit.

This brings a new database to 6.100 records:

👍


Doesn't run Docker inside when top level build invoked using BuildKit

Same image, with and without export DOCKER_BUILDKIT=1 produces different results. Legacy builder runs Docker inside just fine with Sysbox, while BuildKit builds fail to connect to the Docker:
Ubuntu 20.04.05 LTS with 5.4.0-122-generic kernel

@XVilka, looks like docker is simply unable to initialize in the failing scenario.
 Can you please describe how you reproduce this issue? Which instruction are you executing to launch the sysbox container in the working and non-working scenario? Also, how are you building your image within the sysbox container when relying on dockerd and builtkit?

@rodnymolina, I have a Dockerfile that somewhere inside calls docker run .... Currently, sysbox is the default runtime on my server, so I don't need to supply any additional parameters. I build the same image using either default docker build or export DOCKER_BUILDKIT=1 && docker build. In the first case docker inside docker runs just fine (during the build stage), while in the second I observe the error.
FROM ubuntu:20.04

# Non-interactive installation requirements
ARG DEBIAN_FRONTEND=noninteractive

# Set installation options
RUN echo 'debconf debconf/frontend select Noninteractive' > /debconf-seed.txt && \
    echo 'tzdata tzdata/Areas select Etc' >> /debconf-seed.txt && \
    echo 'tzdata tzdata/Zones/Etc select UTC' >> /debconf-seed.txt && \
    echo 'locales locales/locales_to_be_generated multiselect en_US.UTF-8 UTF-8' >> /debconf-seed.txt && \
    echo 'locales locales/default_environment_locale select en_US.UTF-8' >> /debconf-seed.txt && \
    debconf-set-selections /debconf-seed.txt

RUN apt-get update -qq && apt-get install -y docker.io

COPY inside.sh /inside.sh
RUN /inside.sh

where inside.sh is this script:
#!/bin/sh

# Start Docker daemon (only works with Sysbox runtime)
nohup dockerd 2>&1 | tee "dockerd.log" &
sleep 15
cat "dockerd.log"
docker info

docker run alpine:3.16 cat /etc/os-release

Then I run it with a following simple script
#!/bin/sh
echo "Building container..."
docker build --tag sysbox-test . || exit 1

If I do ./run - it prints the Alpine /etc/os-release contents - if I do DOCKER_BUILDKIT=1 ./run - it has this error.

@rodnymolina was my information sufficient on reproducing the issue?


Discuss about the state pass into Link or navigate

Maybe we also need another way to pass parameters.
just like this:
const [, navigator] = useLocation();
navigate(path: string, replace?: boolean, state?: object);

// and
<Link to='/app' state={state}/>

@omgovich @molefrog

I've been thinking about adding a more generic prop called navigate with navigation options that can be passed down to the navigation method. The motivation is simple: it might be possible that you're using a different location hook (like hash-based location) where settings like this don't make sense. And that could also allow us to specify replace option as well. Basically wouter will know nothing about the format of options that the current location hook is using:
<Link to='/app' navigate={{ replace: true, state: { animated: true } }} />
// calls navigate({ replace: true, state: { .. })

This will, however, require us to change the interface of the navigate method to keep the backward compat, but we could of course process true/false as an edge case and convert it to options internally:
const navigate = (to, options = {}) => {
  if (typeof options === 'boolean') options = { replace: options }
  const { replace = false, state = null } = options

  ...
}

But of course, that's a bit size-consuming.

But the biggest question here is how are we going to return current history.state back to the user? One of the ideas I had is when useRoute is called merge this state in params.
const [match, params] = useRoute("/users/:id")

// when called with /users/1 and navigation performed with `history.state` = { animated: true }
// the result is:
match // true
params // { id: 1, animated: true }

Which of course a bit hacky and conventional, but on the other hand will allow us to also merge query params later on. And it allow us to keep the semantics. I would rather have this than:
const [match, params, state, query] = useRoute("/users/:id")
// looks complicated...

For scalability and compatibility, I should think of a way to replace history.state, I will do a search.

Just my opinion, but in terms of the Link component from a usage perspective, I think I prefer @soulchainer’s idea of replace being a bool with an optional state object prop, e.g.
<Link to="/" replace state={{ animate: true }} />

As for the hooks API the state and params would be seperate use cases no? So something like:
const [match, params] = useRoute("/users/:id")

const [location, setLocation, state] = useLocation()

And then possibly just leave a search params hook in its own file, as it’s generally not going to be associated with "matching" a route, and it’s not part of the history API that useLocation wraps.
import useSearchParams from 'wouter/search-params'

const search = useSearchParams()

With search ideally being a plain object.
Off the top of my head those seem like okay trade offs, and more closely match up with their respective browser APIs?

<Link to="/" replace state={{ animate: true }} /> 👍

The approach by @destructobeam in https://github.com/molefrog/wouter/issues/102#issuecomment-557118408 sounds like a really good path forward.

I think wouter shouldn't do any state management.
Users of this library could already:

optionally handle state using any state manager of their choice in the familiar to them pattern

@o-alexandrov Thanks, I absolutely agree with the point!
I do however think that the state support (as well as the search support) can be added through extensions. I already expressed my ideas in https://github.com/molefrog/wouter/issues/108#issuecomment-652380720

@cbbfcd There isn't a huge list of new features I'd like to add to wouter. The main reason is it would be nice to maintain the > current state of the library size and its capabilities.

There are things however, that our users request quite a lot: like query params etc. For me that was especially tricky to
decide if I want to just stop adding new things, or start extending the library heavily.

After giving it some thoughts while I was recovering from my burn out last year (which was the main reason I stopped
working actively on it), I've decided that wouter should support new features through external extendability. I really like
that you can currently specify your custom useLocation hook, though not a lot of people are aware of that. But I really
want to develop this idea further: wouter is minimalistic by default, but it's extendable, so if you need an extra feature, you
can require a separate package for that.

I was already able to implement most of the ideas here: https://github.com/molefrog/wouter/pull/121
With the update above the state support could be as simple as following:
import useLocationWithState from '@wouter/use-location-state';

const App = () => (
  <Router hook={useLocationWithState}>
    <Link to="/app" state={{ foo: 'bar' }}>Click Me</Link>
  </Router>
);

@o-alexandrov The suggestion wasn’t for wouter to manage state, but it already is an interface to the history API which itself has state, so the idea was to read/write to that.
That said, a hook that would provide that seems like a good approach.

i will try to make a pr for it

@cbbfcd Ok!
Can we just discuss one thing beforehand? Here is the list of ideas/questions I have regarding this feature:

Should this live in the same repo as wouter or be a standalone repo or package?
Should the new location also support other requested features like search? I mean we could create a package called wouter-location that exports a useLocation function but on steroids: with search, state and other features if needed. The whole thing could be written in TS to simplify the type export.

@molefrog Thanks for your reply.
Fully agree to implement related functions in a new repo. similar to the plug-in mechanism to enhance wouter,  cool!!
🆒 👇
import useLocation from '@wouter/location'

so, the first features we need to implement in a beta version:

support state
support search

any supplement ?

may be we can support hash router too.
import useLocation from '@wouter/location'

// e.g. history default true, but if the browser does not support hash or set history false, we use hash router
useLocation({ history: true })

maybe an interceptor should be supported too in new useLocation.
const interceptor = (currentPath, nextPath) => {
    if(confirm('Do you want to leave?')){
        return nextPath;
    }
    return currentPath;
}

useLocation({ interceptor })

Should we maybe find a way to allow multiple "patching"?
I mean something like high order functions:
import { withState, withSearch } from '@wouter/addonds'

const useAdvancedLocation = withState(withSearch(useLocation))

Just curious if this is still planned. My project uses it with react-router and it's the only thing I haven't figured out how to convert to let us switch to wouter.
Does anyone have a good pattern for a workaround?

@tony-scio hi, 👋 ~
There is currently no best way to convince everyone. I think the simplest implementation is to pass the state through navigate
const navigate = useCallback(
    (to, { replace = false, state = {} } = {}) =>
      history[replace ? eventReplaceState : eventPushState](
       { state, key: createKey() },
        "",
        // handle nested routers and absolute paths
        to[0] === "~" ? to.slice(1) : base + to
      ),
    [base]
  );

and then mix it into the props in the Route component.
// ...
const state = getStateFromHistory();
if (component) return h(component, { params, state });

  // support render prop or plain children
  return typeof children === "function" ? children({...params, ...state}) : children;

as a workaround, you can control the history state in a store, like context, it's not the best way, but should work well.

Just my opinion, but in terms of the Link component from a usage perspective, I think I prefer @soulchainer’s idea of replace being a bool with an optional state object prop, e.g.
<Link to="/" replace state={{ animate: true }} />

As for the hooks API the state and params would be seperate use cases no? So something like:
// Matching path params
const [match, params] = useRoute("/users/:id")

// Get state
const [location, setLocation, state] = useLocation()

// With setLocation signature something like:
setLocation(to: String, replace: Bool = false, state?: Object)

And then possibly just leave a search params hook in its own file, as it’s generally not going to be associated with "matching" a route, and it’s not really part of history API that useLocation wraps.
import useSearchParams from 'wouter/search-params'

// Minimal implementation
const search = useSearchParams()

// With setSearch convenience method
const [search, setSearch] = useSearchParams()

With search ideally being a plain object. Could also possibly allow passing down a custom parser function in context if needed? setSearch here being just a potential shortcut to update the search params in the address bar, could be left out if out of scope.
Off the top of my head those seem like okay trade offs, and more closely match up with their respective browser APIs?
Edits: Fleshed out some ideas/examples.

There is no wouter-search yet...

I've been busy lately, I'll try to provide an available

Fyi, we added a full support for state navigation in v3.0.0 (see #346 and #349), you can now use v3.0.0-rc.1 to test it out.
Usage:
const [,navigate] = useLocation();

navigate("/", { state: "string" }) // state can be anything
navigate("/", { state: { foo: bar }})

<Link to="/" state={{ modal: true }} />
<Redirect to="/" state={{ modal: true }} />

Also, we have added a hook for hash navigation, and it does support state too:
import { useHashLocation } from "wouter/use-hash-location"

<Router hook={useHashLocation}>
  <Link to="/" state={{ modal: true }} />
</Router>


m3u8 not working properly

There was an issue  #https://github.com/flutter/flutter/issues/18328 and the current solution is not working as it should.
I have an url in format: http:://mypage.com/1234556 which redirects to http::/x.y.z/somestream.m3u8 and as there is no "m3u8" in the link before redirect C.TYPE_OTHER is launched >  ExtractorMediaSource insetad of HlsMediaSource which leads to
Player error:
 com.google.android.exoplayer2.ExoPlaybackException
     at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:360)
     at android.os.Handler.dispatchMessage(Handler.java:98)
     at android.os.Looper.loop(Looper.java:154)
     at android.os.HandlerThread.run(HandlerThread.java:61)
     at com.google.android.exoplayer2.util.PriorityHandlerThread.run(PriorityHandlerThread.java:40)
  Caused by: com.google.android.exoplayer2.source.ExtractorMediaSource$UnrecognizedInputFormatException: None of the available extractors (MatroskaExtractor, FragmentedMp4Extractor, Mp4Extractor, Mp3Extractor, AdtsExtractor, Ac3Extractor, TsExtractor, FlvExtractor, OggExtractor, PsExtractor, WavExtractor) could read the stream.
     at com.google.android.exoplayer2.source.ExtractorMediaPeriod$ExtractorHolder.selectExtractor(ExtractorMediaPeriod.java:699)
     at com.google.android.exoplayer2.source.ExtractorMediaPeriod$ExtractingLoadable.load(ExtractorMediaPeriod.java:623)
     at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:295)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
     at java.util.concurrent.FutureTask.run(FutureTask.java:237)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
     at

There should be manual way of setting the Type

Guys any improvement on this issue? still hls streams are not playing on exoplayer2

Hi @winqoo
m3u8 is a playlist rather than a video file
you may want to look at this stack overflow question
Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you
https://github.com/flutter/flutter/issues/46778 closed
https://github.com/flutter/flutter/issues/53011 web

Is there any way to reproduce http links?

Hi @winqoo
I'm not able to reproduce the issue with video_player 1.0.1 and this m3u8 file . can you try in your side please ?
Flutter (Channel dev, 1.24.0-10.2.pre, on Microsoft Windows [version 10.0.19042.630], locale fr-FR)
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.

I have facing the same problem


grant 70000 when trying to login as user

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[X]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Framework

[ ] Angular
[X] React
[ ] Other

Description
I'm trying to sign in as an Outlook user and have my backend do the OAuth handshake to store the access token and refresh token for future uses. My use case is that signed-in users allow our service to send emails on their behalf.
Error Message
stack:"ServerError: invalid_grant: 70000 - [2021-03-25 15:11:26Z]: AADSTS70000: The request was denied because one or more scopes requested are unauthorized or expired. The user must first sign in and grant the client application access to the requested scope.
T
MSAL Configuration
Frontend:
window.open(`https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=${clientId}&response_mode=query&response_type=code&redirect_uri=${redirectUri}&scope=Mail.Send%20Mail.Read%20offline_access`, "Popup","toolbar=no, location=no, statusbar=no, menubar=no, scrollbars=1, resizable=0, width=580, height=600, top=30")}>
                        Login with MS
                        </a>
Backend:
const config = {
    auth: {
        clientId: process.env.MICROSOFT_CLIENT_ID,
        authority: process.env.MICROSOFT_REDIRECT_URL,
        clientSecret: process.env.MICROSOFT_CLIENT_SECRET
    },
    system: {
        loggerOptions: {
            loggerCallback(loglevel, message, containsPii) {
                console.log(message);
            },
            piiLoggingEnabled: false,
            logLevel: msal.LogLevel.Verbose,
        }
    }
};

const cca = new msal.ConfidentialClientApplication(config);

  const redirectUri = `${process.env.BASE_URL}/api/users/callback/microsoft`
  const tokenRequest = {
    code: req.query.code,
    scopes: ["Mail.Send", "Mail.Read", "offline_access"],
    redirectUri: redirectUri,
  };

  cca.acquireTokenByCode(tokenRequest).then((response) => {
      console.log("\nResponse: \n:", response);
      res.send("<script>window.close();</script> ")
  }).catch((error) => {
      console.log(error);
      res.send("<script>window.close();</script> ")
  });

Reproduction steps
Run the frontend code with the backend as the redirect URI.
Authorize as user
Backend will be triggered with the access code.
Call cca.acquireTokenByCode with the same Scopes and with the received access code.

Expected behavior
Access token and Refresh token are generated and sent
Identity Provider

[X] Azure AD
[ ] Azure B2C Basic Policy
[ ] Azure B2C Custom Policy
[ ] ADFS
[ ] Other

Browsers/Environment

[X] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari
[ ] IE
[ ] Other (Please add browser name here)

Regression

[ ] Did this behavior work before? No
Version:
"@azure/ms-rest-azure-js": "^2.0.1",
"@azure/msal-node": "^1.0.0",

Security

[ ] Is this issue security related? No

Source

[ ] Internal (Microsoft)
[X] Customer request

@DanielGorlo What is your app registered as?  We currently do not support a hybrid flow where code can be accessed at front end and token retrieved at the backend.

The problem is that you're not requesting openid and profile. Your msal code on the backend is silently adding it to the requested scopes, causing the front end and backend to be misaligned in what is requested. Add openid and profile to the front-end and it should work.

Thanks @hpsin! @DanielGorlo let us know how this goes.

@DanielGorlo What is your app registered as? We currently do not support a hybrid flow where code can be accessed at front end and token retrieved at the backend.

So my next step would be to store the tokens on the backend and refresh the token occasionally.
I see there's no refreshToken, which doesn't allow me to authenticate as the user silently, without asking them to log in with MS again.
Is there anything I'm missing?
I've been trying the following 2 approaches:
`  cca.acquireTokenByRefreshToken(user.microsoft_token).then(async (response) => {
console.log('Microsoft token and refresh token exist. Refreshing token...')
}).catch((error) => {
console.log(JSON.stringify(error))
console.log(error)
});
cca.acquireTokenSilent(user.microsoft_token).then(async (response) => {
console.log('Microsoft token and refresh token exist. Refreshing token...')
}).catch((error) => {
console.log(JSON.stringify(error))
console.log(error)
});
`

@DanielGorlo We do not return the refresh_token to the user, but they are indeed cached by the library, either InMemory which is the default or persisted in the filesystem. We provide a persistence solution with our msal-node-extensions library which is currently in Private Preview
You can either choose our solution, or write a custom persistence and a discussion in this regard can be referred to here.
Hope this clairifies.

Closing due to inactivity. Please let us know if you still have this issue.


[SU-214] Add feedback links for data table feature previews

Add feedback links to the feature previews page (https://app.terra.bio/#feature-preview).

And add a banner requesting feedback to the data table. This is only shown when one or both of the relevant feature previews is enabled.

Changed the banner's background color to white to improve contrast.


It installs but doesn't work in Pycharm 2022.2

Plugin installs but doesn't work on Pycharm version Build #PY-222.3345.131, built on July 27, 2022

Duplicate of https://github.com/ashald/EnvFile/issues/185

Seeing the same thing on IntelliJ IDEA version Build #IU-222.3345.118, built on July 26, 2022

Same here 😢

The workaround for now is:

Copy your env file contents to clipboard
Edit your run configuration's environment variables
Click the small paste button

Same here :(

I just updated to RC 2022.2.2 Build #PY-222.4167.4, built on August 31, 2022 and the plugin works there, so no need to downgrade, just opt in EAP

Follow #185 for updates.


TriggerActions to use strings as flow and trigger types

As a administrator, I want to use the terraform provider to manage trigger actions with the respective flow types as strings, not integers, so that it's self-explanatory what it means when you look at the terraform files.
Acceptance criteria

[x] I can manage the trigger actions through terraform
[x] I can use either integers or strings which get validated in the logic as flow types
[x] I can use either integers or strings which get validated in the logic as trigger types

As a workaround for the moment the enum number can be sent

closed as functionality is included in v1.0.0-alpha.14


feat: added lora/qlora support

close #222
close #223
close #97

Nice work! Can you put more documentation in this pull request?

Thank you @mmirman, more documentation added!

Sorry I meant here, in the discussion :-)

@us I pulled in a few PRs that you took a look at.  I'm inclined to merge this today - could you maybe take a look at the errors?

@us I pulled in a few PRs that you took a look at. I'm inclined to merge this today - could you maybe take a look at the errors?

According to my understanding peft library only supports Nvidia gpus meaning this specific implementation wouldn't work on other hardware even with automated hardware detection.

The PR looks great and seems to close out #222. I'd only request @us to add support for 8 bit QLora

@us I pulled in a few PRs that you took a look at. I'm inclined to merge this today - could you maybe take a look at the errors?

According to my understanding peft library only supports Nvidia gpus meaning this specific implementation wouldn't work on other hardware even with automated hardware detection.

According to the releases page of the PEFT repository, the model also supports XPU and NPU devices. XPU is a generic term for any kind of processing unit, such as CPU, GPU, TPU, etc. NPU is a neural processing unit, which is a specialized hardware accelerator for deep learning applications.
As for AMD GPUs, I could not find any official information about their support for PEFT model. However, I found a GitHub repository called AutoGPTQ, which claims to integrate with PEFT to use GPTQ quantized model to train adapters. It also provides some performance comparison charts that include AMD GPUs.

Great! The main goal it to support fine-tuning on all consumer devices so this is great news. I guess this should enable Lora on all devices. On the other hand, Qlora might not work for non-Nvidia devices since quantization config uses bitsandbytes which is essentially a cuda wrapper. This will probably be solved once we implement #225.

Other than that I think the PR looks great and should be ready to merge. @mmirman @cartazio Kindly confirm. @us Do you mind adding a test file for this?

My main concern is what Vic said, that this will only be testable on cuda devices, but thats fine i guess

we should try to have some informative error message or exit/exception to handle that case I think

shoot, forgot we were wanting a test, @us can you do a followup pr with that machinery? :)

Hey @us I'm reverting this merge because it it currently breaking the BaseOnsiteLLM class. Kindly complete the 8 bit quantization implementation to avoid adding bugs to the codebase.

@VictorOdede hey, can you explain the error more, please?
where is it breaking?
should I add less kwargs? or shouldn't I add to kwargs?
or should I add separate kwargs like that?
    def __init__(self,model_uri=None,tokenizer_kw_args={},model_kw_args={}, quantization_kw_args={}):

or should I add as separete function in class?
def model_quantizater(self):
	......

Thank you!

@VictorOdede hey, can you explain the error more, please?
where is it breaking? should I add less kwargs? or shouldn't I add to kwargs? or should I add separate kwargs like that?
    def __init__(self,model_uri=None,tokenizer_kw_args={},model_kw_args={}, quantization_kw_args={}):

or should I add as separete function in class?
def model_quantizater(self):
	......

Thank you!

You need to fix the unresolved conditional branch on line 106. You should also package the logic into it's own method, the init method is reserved for initializing the BaseOnsiteLLM class.


Change docker headers to OCI format

Headers removed:

Docker-Distribution-Api-Version
Docker-Content-Digest
Docker-Upload-ID

Headers added:

OCI-Distribution-Version
OCI-Content-Digest
OCI-Upload-ID

Signed-off-by: Atlas Kerr<EMAIL_ADDRESS>

there is a few breaking things here, and the changes might best be split into a couple of PRs.


cannot build on windows with latest verisons of yarn

C:\Users\toms\outline-client>yarn do src/electron/build
yarn run v1.12.3
$ bash ./scripts/do_action.sh src/electron/build
++ git rev-parse --show-toplevel

export ROOT_DIR=/mnt/c/Users/toms/outline-client
ROOT_DIR=/mnt/c/Users/toms/outline-client
export BUILD_DIR=/mnt/c/Users/toms/outline-client/build
BUILD_DIR=/mnt/c/Users/toms/outline-client/build
export -f do_action
do_action src/electron/build
local action=src/electron/build
echo '[Running src/electron/build]'
[Running src/electron/build]
shift
/mnt/c/Users/toms/outline-client/src/electron/build_action.sh
yarn do src/www/build
/mnt/c/Temp/yarn--1546159424275-0.23207095948173206/yarn: 3: /mnt/c/Temp/yarn--1546159424275-0.23207095948173206/yarn: C:\Program Files\nodejs\node.exe: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

version of Windows: Windows 10 10.0.17134.472
version of Node: v10.15.0
version of yarn: 1.12.3
which command you ran: yarn do src/electron/build

@Sean-Wang Sorry you've been having trouble compiling Outline. I see the same error when I install the latest versions of Yarn. As a workaround, if you install version 1.10.1 it should compile normally.

@Sean-Wang Sorry you've been having trouble compiling Outline. I see the same error when I install the latest versions of Yarn. As a workaround, if you install version 1.10.1 it should compile normally:
https://github.com/yarnpkg/yarn/releases/tag/v1.10.1

Thank you for your reply. I'll try it with yarn 1.10.1, and with more feedback.

Release with yarn 1.10.1, not prompted C:\Program Files\nodejs\node.exe: not found, but prompted:

which command you ran : yarn do src/electron/release
Use git clone download project.


[Sidebar] - Sidebar transition using wrong transition

Steps to Reproduce

Click back and forth between the two buttons on the right of the page, several times at a quick rate.
Stop clicking, see that the buttons get pushed across an extra amount, the yellow main segment div becomes visible as the grey pusher div is pushed across.

The pusher is being moved as if it has the "push" transition and not the "overlay" transition that is set in the JS.
Expected
The Sidebar should always use the overlay transition
Result
The Sidebar does not always use the overlay transition
Testcase
http://jsfiddle.net/tmyler/rduvhn8u/334/

I can't seem to reproduce this issue, what browser are you using?

It occurs in both:
Firefox Quantum 61.0.1 (64 bit)
Chrome Version 68.0.3440.84 (Official Build) (64-bit)
My PC is running Windows 10 Pro Version 1809 Build 17134.165
Here is quick video of the bug occurring for me in Firefox.
Edit fiddle - JSFiddle - Mozilla Firefox 03_08_2018 08_50_07.zip

Ok I see now, that is a weird one. It's as if the transitions are queued and because the buttons are spammed it can't keep up therefore it leads to running the transitions incorrectly.

Yes it is definitely some sort of strange issue with queued inputs. It may be something that cannot be fixed but is an interesting bug either way.

Has there been any developments in investigating or solving this issue?

@tmyler you may or may not know that SUI development has slowed down recently so this issue will probably not be resolved for quite some time.


Update file headers and version numbers

Update file headers and version numbers
This work item was migrated from CodePlex
CodePlex work item ID: '9086'
Assigned to: 'tfabraham'
Vote count: '1'

[UnknownUser@1/3/2012]
Associated with changeset 64667.

[UnknownUser@1/3/2012]
Resolved with changeset 64668.

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]


change default aliases to be more like node's subpath aliases

Describe the problem
I want to run a node test runner to test parts of my application, but it doesn't understand the "$lib" type aliases.
I tried the node package module-alias but it appears difficult to use with es6.
Node already has support for subpath aliases, but they must begin with "#", so currently I am changing the sveltekit to use "#lib" via :
vite: {
			resolve: {
				alias: {
					'#lib': path.resolve('./src/lib')
				}
			}
		}

which is not a bad solution, but perhaps parity with node should be the default?
Describe the proposed solution
"$lib" changed to "#lib"
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response

I think this should be supported via https://github.com/vitejs/vite/issues/7385 first so we don't mix Vite's aliases with Node's aliases.

Looks like there's a PR for that one, but it's in need of a review: https://github.com/vitejs/vite/pull/7770

Vite aliases are very nice because you can override them to provide no-ops or your own behavior for $app/navigation, $app/stores, etc. when doing things like using Storybook, testing, etc. I'm not sure whether you'd be able to do that with #app. Perhaps you could still override with a Vite alias, but I'd want to make sure.

I'm hesitant to make this change, because it only really makes sense for $lib — not $env or $app — and it would feel weird to have #lib alongside $app/....
In general, Vite apps are going to contain stuff that isn't Node-compatible — import.meta.glob, .css imports, and all sorts of other things — so I'm not sure if there's all that much value in making a change that makes it possible for Node test runners to run in a slightly larger subset of cases (those involving $lib) than is currently the case, given that it's always going to be much less than 100%.
I think a combination of these strategies is likely to yield better results:

Using Vitest, or another Vite-aware test runner
Only unit-testing code inside lib, rather than trying to unit test code that relies on lib
Leaning more on integration tests than unit tests

Makes sense !
Perhaps using vitest is the way to go.
Much of code inside lib at least for me but imagine many others will refer
to $lib simply because of the convenience.
I’ve seen you (RH) strongly advise against using jest. Given the api is
similar what do you say of vitest.
!
On Thu, 25 Aug 2022 at 22:31, Rich Harris @.***> wrote:

I'm hesitant to make this change, because it only really makes sense for
$lib — not $env or $app — and it would feel weird to have #lib alongside
$app/....
In general, Vite apps are going to contain stuff that isn't
Node-compatible — import.meta.glob, .css imports, and all sorts of other
things — so I'm not sure if there's all that much value in making a change
that makes it possible for Node test runners to run in a slightly larger
subset of cases (those involving $lib) than is currently the case, given
that it's always going to be much less than 100%.
I think a combination of these strategies is likely to yield better
results:

Using Vitest, or another Vite-aware test runner
Only unit-testing code inside lib, rather than trying to unit test
code that relies on lib
Leaning more on integration tests than unit tests

—
Reply to this email directly, view it on GitHub
https://github.com/sveltejs/kit/issues/5847#issuecomment-1227731420, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAGNEU65M4YRHIU7G6CX3V27J3ZANCNFSM5533CMRQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I haven't really put it through its paces, but I'm very impressed with what I've seen so far of Vitest. We're considering adding it as an option when you create a new app: #5708
Will close this issue then — thanks


[PR] The proj files have been updated to enable SourceLink

CSProj files have been updated to enable SourceLink in your nuget
[This pull request was created with an automated workflow]
I noticed that your repository and Nuget package are important for our .NET community, but you still haven't enabled SourceLink.
We have to take 2 steps:

Please approve this pull request and make .NET a better place for .NET developers and their debugging.
Then just upload the .snupkg file to https://www.nuget.org/ (now you can find the snupkg file along with the .nuget file)

You can find more information about SourceLine at the following links
https://github.com/dotnet/sourcelink
https://www.hanselman.com/blog/ExploringNETCoresSourceLinkSteppingIntoTheSourceCodeOfNuGetPackagesYouDontOwn.aspx
If you are interesting about this automated workflow and how it works
https://github.com/JTOne123/GitHubMassUpdater
If you notice any flaws, please comment and I will try to make fixes manually

Thank you for the PR! After careful consideration we decided not to accept it at this time. We already have SourceLink enabled for the projects where this makes sense, and certain functionality relies on the particular way it is set up.


Redirect Submit Talk view to Session List view

After a user successfully submits a talk (the form validates) they should be redirected to the Session List page, rather than simply reloading the same page again.

I'll handle this and send the PR when done. Do it right this time


[IF/Plugins] timestamp and duration are not validated

Describe the bug
Timestamp and duration fields from input are not validated.
To Reproduce
Steps to reproduce the behavior:

Create valid manifest.
Set inappropriate values for timestamp and duration(negative, string, etc.)
Run the IF framework with that manifest.

Expected behavior
To show error message about invalid input data.
Actual behavior
Finished execution with crushed values.
Screenshots

Connected to https://github.com/Green-Software-Foundation/if/issues/602
Need to define the best practices we want to implement, document them in #602 and apply them to our own plugins - this will resolve this bug.

closing as not planned


Pagination schemes

Hey, awesome work on orbit.
I'm trying migrate from ember-data to ember-orbit and I've hit a road block regarding pagination.
I managed to adapt the filtering by overrriding buildFilterParam in a custom URLBuilder, but I've got a page size/number based paginator on the server and it seems there is no way for parameters other than offset and limit to be passed to buildPageParam. Reading the code it appears offset/limit pagination is hardcoded in QueryTerm.pageParamToSpecifier.
Could this be handled in the same way as filtering, letting the query builder decide how to build the query? This behaviour is not mandated by JSONAPI and I see no easy way out, am I missing something?

@lucacorti welcome!
It's true that the builder support for pagination options is quite narrow, but you can still pass any custom settings you want as an option for your request. If your JSON:API source is named remote, you could pass custom pagination params like this:
let results = store.findRecords('planet', {
  sources: {
    remote: {
      settings: { params: { 'page[offset]': 'abcdef' } }
    }
  }
})

This example works in v0.16 or  v0.17 beta, but there will be a more streamlined way to do this in v0.17.

@dgeb I see, works, looking forward to 0.17 then. Thanks!


Can't start pyprime instance due to Ansys License Manager Error

🔍 Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

🐞 Description of the bug
When I start a pyprime session, sometimes I get this error and then I have to restart my computer.
prime_session= prime.launch_prime()
Restarting the pykernel, restarting the IDE does not seem to work.

📝 Steps to reproduce
Launch prime_session= prime.launch_prime()
💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
23r1
🐍 Which Python version are you using?
3.10
📦 Installed packages
NA

What is happening is pyprime is 1. not returning licenses and 2. continuing to check them out.
my licsense log:
11:27:58 (ansyslmd) (@ansyslmd-SLOG@) Running on Hypervisor: Not determined - treat as Physical
11:27:58 (ansyslmd) (@ansyslmd-SLOG@) ===============================================
11:28:02 (ansyslmd) TCP_NODELAY NOT enabled
11:28:03 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[17944]
11:28:06 (ansyslmd) OUT: "disco_level1"<EMAIL_ADDRESS>[21364]
11:28:17 (ansyslmd) IN: "disco_level1"<EMAIL_ADDRESS>[21364]
11:28:53 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[7300]
11:28:59 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[13508]
11:29:05 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[22292]
11:29:15 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[12024]
11:29:19 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[13492]
11:29:19 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[7996]
11:29:29 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[14396]
11:29:32 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[8908]
11:29:33 (ansyslmd) OUT: "preppost"<EMAIL_ADDRESS>[7928]
11:29:33 (ansyslmd) DENIED: "preppost"<EMAIL_ADDRESS>[9720] (Licensed number of users already reached. (-4,342))
11:29:33 (ansyslmd) UNSUPPORTED: "cfd-preppost" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[9720] (No such feature exists. (-5,346))
11:29:33 (ansyslmd) UNSUPPORTED: "advanced-meshing" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[9720] (No such feature exists. (-5,346))
11:29:35 (ansyslmd) DENIED: "preppost"<EMAIL_ADDRESS>[6080] (Licensed number of users already reached. (-4,342))
11:29:35 (ansyslmd) DENIED: "preppost"<EMAIL_ADDRESS>[6080] (Licensed number of users already reached. (-4,342))
11:31:34 (ansyslmd) DENIED: "preppost"<EMAIL_ADDRESS>[9720] (Licensed number of users already reached. (-4,342))
11:31:34 (ansyslmd) UNSUPPORTED: "cfd-preppost" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[9720] (No such feature exists. (-5,346))
11:31:34 (ansyslmd) UNSUPPORTED: "advanced-meshing" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[9720] (No such feature exists. (-5,346))
11:31:35 (ansyslmd) DENIED: "preppost"<EMAIL_ADDRESS>[6080] (Licensed number of users already reached. (-4,342))
11:31:35 (ansyslmd) UNSUPPORTED: "cfd-preppost" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[6080] (No such feature exists. (-5,346))
11:31:35 (ansyslmd) UNSUPPORTED: "advanced-meshing" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[6080] (No such feature exists. (-5,346))
11:33:33 (ansyslmd) DENIED: "preppost"<EMAIL_ADDRESS>[9720] (Licensed number of users already reached. (-4,342))
11:33:33 (ansyslmd) UNSUPPORTED: "cfd-preppost" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[9720] (No such feature exists. (-5,346))
11:33:33 (ansyslmd) UNSUPPORTED: "advanced-meshing" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[9720] (No such feature exists. (-5,346))
11:33:34 (ansyslmd) DENIED: "preppost"<EMAIL_ADDRESS>[6080] (Licensed number of users already reached. (-4,342))
11:33:34 (ansyslmd) UNSUPPORTED: "cfd-preppost" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[6080] (No such feature exists. (-5,346))
11:33:34 (ansyslmd) UNSUPPORTED: "advanced-meshing" (PORT_AT_HOST_PLUS<EMAIL_ADDRESS>[6080] (No such feature exists. (-5,346))

Solution: use python
At the end of your script or if you get the out of license message, you can use os. taskill to kill ALL of the .exe that are holding the licenses. This will kill them all. caveat sciptor.

import os
os.system("taskkill /f /im  AnsysPrimeServer.exe")

Closing this issue as we are working on a solution to provide licensing errors as part of addressing #2 .


enh: docs/guide/intro-yii add id to link

Because translators must translate anchor text, it's better to use id for reference,
so they shouldn't translate it twice. Also not all translators puts same text in this case.

Thanks!


ERROR in compiler_1.StaticSymbolCache is not a constructor webpack: Failed to compile

Please provide us with the following information:

OS?
Windows 10
Versions.
ng --version
@angular/cli: 1.0.0-beta.32.3 [1.0.0-beta.31]
node: 6.9.5
os: win32 x64
@angular/common: 2.2.1
@angular/compiler: 2.2.1
@angular/core: 2.4.7
@angular/forms: 2.2.1
@angular/http: 2.2.1
@angular/platform-browser: 2.2.1
@angular/platform-browser-dynamic: 2.2.1
@angular/router: 3.2.1
@angular/cli: 1.0.0-beta.32.3
@angular/compiler-cli: 2.4.7
Repro steps.
Initially created with CLI under beta 16. And run.
Initially stopped working because Node version was incorrect (I assume something got updated in the background without my knowledge). Then upgraded CLI to beta 31 and got problem. Moving to beat 32 did not solve problem.
And the problem is ...

ng serve
** NG Live Development Server is running on http://localhost:4200. **
Hash: e0d3674f7d03f30ffc2f
Time: 13016ms
chunk    {0} main.bundle.js, main.bundle.js.map (main) 51.1 kB {2} [initial] [rendered]
chunk    {1} styles.bundle.js, styles.bundle.js.map (styles) 11.7 kB {3} [initial] [rendered]
chunk    {2} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.67 MB [initial] [rendered]
chunk    {3} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]
ERROR in compiler_1.StaticSymbolCache is not a constructor
webpack: Failed to compile.

The log given by the failure.
Mention any other details that might be useful.
It has been raised at https://github.com/angular/angular-cli/issues/4464 but solution does not apply to my situation.
I can create a new project that runs with no problems.
But if then copy the code over into the new project, I get an error in typescript.js in node_modules\typescript\lib and a problem with the code
function createSourceFile(fileName, languageVersion, scriptKind) {
// code from createNode is inlined here so createNode won't have to deal with special case of creating source files
// this is quite rare comparing to other nodes and createNode should be as fast as possible
var sourceFile = new SourceFileConstructor(256 /* SourceFile /, /pos/ 0, / end */ sourceText.length);
giving an error of

ng serve
Cannot read property 'length' of undefined
TypeError: Cannot read property 'length' of undefined
at createSourceFile (C:\Temp\angularjs_example\angular2\updated-app\node_modules\typescript\lib\typescript.js:8980:109)

So I possibly fixed it.
I created a new project and used the package.json file values in the existing project's json file.
Then I removed node_modules and dist folders, rerun npm install --save-dev @angular/cli@latest and npm install
and now ng serve works.