NotBeforeError: jwt not active when processing activity

Github issues for C# /JS / Java/ Python should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Describe the bug
I have a bot that has been working well for years, starting it up locally every few months. Today I am getting a new error, which I have no idea how to resolve:
I have a Nest backend with an endpoint api/messages which handles the incoming message requests:
@Post('api/messages')
async handleBotMessage(@Req() request: Request, @Res() response: Response): Promise<void> {
    try {
      return await this.botService.adapter.process(request, response, this.botService.run);
    } catch (err) {
      this.logger.error('Error processing activity: ', err.stack);
      throw new InternalServerErrorException('Cannot handle request...');
    }
 }

The code for creating the botService.adapter:
const botFrameworkAuthentication = new ConfigurationBotFrameworkAuthentication({
      MicrosoftAppId: process.env.BOT_APP_ID,
      MicrosoftAppPassword: process.env.BOT_APP_PASSWORD,
      MicrosoftAppType: 'SingleTenant',
      MicrosoftAppTenantId: process.env.TENANT_ID,
} as ConfigurationBotFrameworkAuthenticationOptions);

/** create adapter, which is used by the bot framework to send messages */
this._adapter = new CloudAdapter(botFrameworkAuthentication);

I have my .env variables set as what I believe to be correct values. Never changed anything and it worked well for at least 2 years.
Behaviour
[Nest] 7743  - 09/28/2022, 9:41:12 AM     LOG [LoggingInterceptor] [/api/messages] --> BotController.handleBotMessage
Error finding key for token. Available keys: -----BEGIN RSA PUBLIC KEY-----
// some key here which I omitted, if needed I can provide it
-----END RSA PUBLIC KEY-----

JwtTokenExtractor.getIdentity:err! NotBeforeError: jwt not active
    at /home/node_modules/jsonwebtoken/verify.js:143:21
    at getSecret (/home/node_modules/jsonwebtoken/verify.js:90:14)
    at Object.module.exports [as verify] (/home/node_modules/jsonwebtoken/verify.js:94:10)
    at JwtTokenExtractor.<anonymous> (/home/node_modules/botframework-connector/src/auth/jwtTokenExtractor.ts:158:35)
    at Generator.next (<anonymous>)
    at fulfilled (/home/node_modules/botframework-connector/lib/auth/jwtTokenExtractor.js:12:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  date: 2022-09-29T15:22:24.000Z
}
And nothing happens with the bot response... I searched documentation and issues and did not find anything related to where this issue might be coming from.

Expected behavior
bot.run() function should execute with the respective handlers

Thank you @bmutafov, we are investigating.

Hi @bmutafov,
Are you facing the same issue if using the bot samples from the official typescript_nodejs repository?
In sample 05.multi-turn-prompt, the bot.run() method seems to looks different from your code:
https://github.com/microsoft/BotBuilder-Samples/blob/b750e9eaf99c0f612c49cfa42e523ad2fc4e6b24/samples/typescript_nodejs/05.multi-turn-prompt/src/index.ts#L78-L82

closing due to inactivity.

It actually got fixed by itself, so my best guess it was a Microsoft-related issue, rather than a framework one

@ramfattah Sorry for the lack of updates before, was on a holiday.
Anyways, today I have the same issue. Nothing has changed since yesterday, when it was working. I downloaded the 05.multi-turn-prompt sample and ran it with the same BotId and TenantId and still getting the same error:
Error finding key for token. Available keys: -----BEGIN RSA PUBLIC KEY-----
MIIBCgKCAQEAubfEYu04rUbOZmJj2c8eYHvtsmV6ttGbrvrvCrEJ6mgFpdZACCOJ
EUI7ISZl9Ov97jV/C3JYtOArxGPXbx3cdLIMk7H1Vf/taA6vD0ozDWOPrGOTfaOm
+wEZjq9fNv9Spd7FXo2YKYOmlGSYxweJC7+ZzUoY/zmqd+9QHha9jvVkZ9HfYXuW
aZiEHZSg20cJ+IRMWU6c4sLJgil4J4K3A7UoNwi9VptliGEhzTX5Dft4hYKEnuuz
UioJaZ/54Cq+wctYrnNzSuY7p9tS9vO11JbQxpJNzte6gkREELaOKTOF8TzTW/QC
EcaiqlaTJyELwApS2CehHFUpdQCVrznMPQIDAQAB
-----END RSA PUBLIC KEY-----

JwtTokenExtractor.getIdentity:err! NotBeforeError: jwt not active
    at /home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/jsonwebtoken/verify.js:143:21
    at getSecret (/home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/jsonwebtoken/verify.js:90:14)
    at Object.module.exports [as verify] (/home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/jsonwebtoken/verify.js:94:10)
    at JwtTokenExtractor.<anonymous> (/home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/botframework-connector/lib/auth/jwtTokenExtractor.js:137:54)
    at Generator.next (<anonymous>)
    at fulfilled (/home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/botframework-connector/lib/auth/jwtTokenExtractor.js:12:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  date: 2022-10-11T13:01:23.000Z
}
Error finding key for token. Available keys: -----BEGIN RSA PUBLIC KEY-----
MIIBCgKCAQEAubfEYu04rUbOZmJj2c8eYHvtsmV6ttGbrvrvCrEJ6mgFpdZACCOJ
EUI7ISZl9Ov97jV/C3JYtOArxGPXbx3cdLIMk7H1Vf/taA6vD0ozDWOPrGOTfaOm
+wEZjq9fNv9Spd7FXo2YKYOmlGSYxweJC7+ZzUoY/zmqd+9QHha9jvVkZ9HfYXuW
aZiEHZSg20cJ+IRMWU6c4sLJgil4J4K3A7UoNwi9VptliGEhzTX5Dft4hYKEnuuz
UioJaZ/54Cq+wctYrnNzSuY7p9tS9vO11JbQxpJNzte6gkREELaOKTOF8TzTW/QC
EcaiqlaTJyELwApS2CehHFUpdQCVrznMPQIDAQAB
-----END RSA PUBLIC KEY-----

JwtTokenExtractor.getIdentity:err! NotBeforeError: jwt not active
    at /home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/jsonwebtoken/verify.js:143:21
    at getSecret (/home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/jsonwebtoken/verify.js:90:14)
    at Object.module.exports [as verify] (/home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/jsonwebtoken/verify.js:94:10)
    at JwtTokenExtractor.<anonymous> (/home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/botframework-connector/lib/auth/jwtTokenExtractor.js:137:54)
    at Generator.next (<anonymous>)
    at fulfilled (/home/Work/botbuilder-samples/samples/typescript_nodejs/05.multi-turn-prompt/node_modules/botframework-connector/lib/auth/jwtTokenExtractor.js:12:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  date: 2022-10-11T13:01:23.000Z
}

Should we reopen this ticket?


Unused variables not greying out properly

Hi, I installed this theme but had to reinstall vscode on my mac and after reinstalling, the unused variable greying out doesn't seem to work properly. I'm using the recommended settings and the language type is Babel Javascript. Any advice on what might be causing this or how I can debug?

Ok thanks for pointing that issue to our attention we will fix the issue promptly.

Yup sure! Let me know if you need any further information

Unused source code:
editorUnnecessaryCode.border: Border color of unnecessary (unused) source code in the editor.
editorUnnecessaryCode.opacity: Opacity of unnecessary (unused) source code in the editor. For example, "#000000c0" will render the code with 75% opacity. For high contrast themes, use the "editorUnnecessaryCode.border" theme color to underline unnecessary code instead of fading it out.

Theses are the values used :
"editorUnnecessaryCode.border": "#95B4",
"editorUnnecessaryCode.opacity": "#FFF5",
are you sure you have set the option in your settings to :   "editor.showUnused": true

VS Code ships with built-in support for fading out unused locals/parameters/imports in JavaScript and TypeScript. You can enable/disable this feature by setting:
// For all languages (it is enabled the default)
"editor.showUnused": true

// Or just for a specific language
"[typescript]": {
   "editor.showUnused": true
}

Extensions can also add support for other languages.
You can additionally mark unused variables as warnings by setting noUnusedLocals and/or noUnusedParameters in your jsconfig or tsconfig:
{
  "compilerOptions": {
    "noUnusedLocals": true,
    "noUnusedParameters": true
  },
  "exclude": [
    "node_modules",
    "**/node_modules"
  ]
}

This adds a squiggly and error for unused variables in addition to graying them out

{
  "editor.formatOnSave": true,
  "gitlens.views.repositories.location": "scm",
  "gitlens.views.fileHistory.location": "scm",
  "gitlens.views.lineHistory.location": "scm",
  "gitlens.views.compare.location": "scm",
  "gitlens.views.search.location": "scm",
  "terminal.external.osxExec": "iTerm.app",
  "terminal.integrated.fontFamily": "Fira Mono for Powerline",
  "editor.showUnused": true,
  "terminal.integrated.fontSize": 14,
  "workbench.iconTheme": "material-icon-theme",
  "workbench.colorTheme": "Pop N' Lock Theme by Luxcium ✨",
  "files.encoding": "utf8",
  "files.autoGuessEncoding": false,
  "workbench.editor.highlightModifiedTabs": true,
  "material-icon-theme.showReloadMessage": true,
  "editor.fontFamily": "Fira Code iScript, Fira Code",
  "editor.fontLigatures": true,
  "editor.fontSize": 16,
  "editor.suggestFontSize": 16
}

This is my settings.json file right now - VSCode doesn't seem to support the following settings:
"editorUnnecessaryCode.border": "#95B4",
"editorUnnecessaryCode.opacity": "#FFF5",

This is my settings.json file right now - VSCode doesn't seem to support the following settings:
"editorUnnecessaryCode.border": "#95B4",
"editorUnnecessaryCode.opacity": "#FFF5",

No these are the setting used inside the theme to configure it uses only the last value (here 4 or 5) to determine the opacity …

should have been fixed let me know if probleme persist


Implement artichoke_backend::module:: Registry::shrink_to

module::Registry in the artichoke-backend crate implements several APIs for manipulating the underlying allocations such as module::Registry::reserve and module::Registry::shrink_to_fit.
Artichoke depends on the most recent stable Rust compiler and Rust 1.56.0 stabilized HashMap::shrink_to. module::Registry is built on HashMap, so we can add a corresponding module::Registry::shrink_to API.
The code we'll want to add should be placed below the definition of module::Registry::shrink_to_fit:
https://github.com/artichoke/artichoke/blob/11ba967aee3d3527482c12658bcf70edd62055cb/artichoke-backend/src/module/registry.rs#L225-L227
See a similar PR in artichoke/intaglio for inspiration around how to structure the doc comments:

https://github.com/artichoke/intaglio/pull/107
https://github.com/artichoke/intaglio/commit/592b41622a2b136ce3d106b2ebb15bfe28a2642b

Similar Tickets
If you're interested in working on this, you might also consider taking:

https://github.com/artichoke/artichoke/issues/1502

@lopopolo This is an issue that I'd like to take up. Is it up for grabs?

@kolharsam go for it.

@lopopolo The difference between this issue and #1502 is not apparent to me. Could you provide me with some context for the same?

The class registry and module registry are two implementations of the same datastructure with different value types in the inner hashmap.
The change that needs to be made to each is the same. These two data structures live in different source files.
These are the main differences between them:
Spec type
https://github.com/artichoke/artichoke/blob/11ba967aee3d3527482c12658bcf70edd62055cb/artichoke-backend/src/module/registry.rs#L29
https://github.com/artichoke/artichoke/blob/11ba967aee3d3527482c12658bcf70edd62055cb/artichoke-backend/src/class/registry.rs#L29
Iterator over specs
https://github.com/artichoke/artichoke/blob/11ba967aee3d3527482c12658bcf70edd62055cb/artichoke-backend/src/module/registry.rs#L137-L142
https://github.com/artichoke/artichoke/blob/11ba967aee3d3527482c12658bcf70edd62055cb/artichoke-backend/src/class/registry.rs#L137-L142

Apologies for making it confusing splitting these tickets in two.


chore: add config option for allowing bounded use of sort-preserving operators

Which issue does this PR close?

Closes #7163.
Rationale for this change
This lets client code that uses bounded queries also make use of SortPreservingRepartitionExec, which can be very helpful for removing SortExec nodes from plans.

What changes are included in this PR?
This PR adds a new config option, bounded_order_preserving_variants to control when SortPreservingRepartitionExec is produced.

Are these changes tested?

Yes, I added a test that shows this option works as expected.
Are there any user-facing changes?

Yes, I updated the docs to include a description the new option.

cc @mustafasrepo @alamb

Thanks @wolffcm  and @mustafasrepo  for the review!


[WIP] floresta-chain: new optimized chainstore

The current chainstore is based on kv, but it has a few problems:

When we flush, we get a huge heap spike
We are getting a 2 or 3 times overhead on headers
It gets kinda slow to retrieve headers during IBD if we flush early

This commit introduces a bare-bones, ad-hock store that consists in two parts:

A open addressing, file backed and memory-mapped hash map to keep the relation block_hash -> block_height
A flat file that contains block headers serialized, in ascending order

To recover a header, given the block height, we simply use pointer arithmetic inside the flat file. If we need to get from the block hash, use the map first, then find it inside the flat file. This has the advantage of not needing explicit flushes (the os will flush it in fixed intervals), flushes are async (the os will do it), we get caching for free (mmap-ed pages will stay in memory if we need) and our cache can react to system constraints, because the kernel will always know how much memory we sill have

My understanding is that kv buckets also don't need explicit flushes. The data saved in a bucket is flushed to disk by the OS periodically, and it's kept in the inner sled pagecache (so we should have fast access), which is configured with a capacity of 100MB in KvChainStore::new.

That was my understanding too, but for some reason, even before using the cache (second part of #169) it didn't really flush on its own, and if we had an unclean shutdown, we would lose our progress (or a good part of it). It would also become increasingly more CPU and IO heavy as we made progress, I suspect it's due to the block locator getting bigger as our chain grows.
But the biggest problem for me, that I couldn't find an alternative, was the heap spike. It would always crash on my phone, before or after #169. With this PR, it runs fine!

It would also become increasingly more CPU and IO heavy as we made progress, I suspect it's due to the block locator getting bigger as our chain grows.

Isn't that the expected behavior of a node in IBD, as it moves from old empty blocks to more recent ones?

Isn't that the expected behavior of a node in IBD, as it moves from old empty blocks to more recent ones?

Not this much, at least not for headers. They are small and have constant-size

Also was the OS not flushing on its own on desktop or on mobile?

Both. At least on my setup.


FACT-1592 fact admin fix fortify issues

JIRA link
https://tools.hmcts.net/jira/browse/FACT-1592
Change description
fix fortify issues by changing the flagged up sections within fortify
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

thought not including a change would fix branch but didn't so can ignore this branch


Error launching application on iPhone 12 Pro Max

I can launch my app from Xcode, but I cannot launch it using flutter run.
Same as here: https://github.com/flutter/flutter/issues/69632
I tried all possible options: cleaning the report, removing files, pub get, update - you name it. Nothing works. The app launches and hangs on the launch screen.
I only have this issues on my 12 Pro Max. I also tried on a 6s, but the app works on the 6s without problems.
My 12 Pro Max is on iOS 14.4.1 and 6s on 14.4 (updating to see if this breaks it).
I see this in the logs:
[        ] Application launched on the device. Waiting for observatory port.
[+30015 ms] Error launching application on iPhone.
Exited (sigterm)
[   +6 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:550:9)
           <asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1157:12)
           <asynchronous suspension>
#3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1009:27)
           <asynchronous suspension>
#4      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
#5      AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
           <asynchronous suspension>
#6      CommandRunner.runCommand
package:args/command_runner.dart:197
           <asynchronous suspension>
#7      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:278:9)

This is what flutter doctor shows when the app hangs:
[✓] Flutter (Channel stable, 2.0.2, on macOS 11.1 20C69 darwin-x64, locale
    en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio
[✓] Android Studio (version 4.1)
[✓] IntelliJ IDEA Community Edition (version 2020.3.2)
[✓] VS Code (version 1.54.3)
[✓] Connected device (4 available)
    ! Error: iPhone is busy: Copying cache files from device. Xcode will
      continue when iPhone is finished. (code -10)

• No issues found!

@lukaszciastko
There's similar open issue describing your case, https://github.com/flutter/flutter/issues/78193
Please follow-up there for updates. Closing this as duplicate.

This is unlikely to be a duplicate, this is a crash after installation (Exited (sigterm)) and #78193 is the app never installing.  @darshankawar Can you re-triage?  We need verbose logging.

That's my bad @jmagman. Thanks for notifying.
@lukaszciastko Can you provide flutter run --verbose ? If the log is huge, put that in a text file and share it here.
Are you running that command from AS or VScode ?
Does the same error occur if you create a new Project and execute flutter run ?

I don't get this error when I try to run a new project. I was running the app using VS Code. I just noticed, when I try to run it from the command, everything is almost the same, but, after about 10 seconds, the app displays the main screen and the logs end different. I attached the logs from VS Code. And this is what I see when I try to launch the app from the terminal:
[ +212 ms] success
[        ] Application launched on the device. Waiting for observatory port.
[+30014 ms] Installing and launching... (completed in 58.8s)
[        ] Error launching application on iPhone.
[   +4 ms] "flutter run" took 361,828ms.
[   +4 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:644:9)
           <asynchronous suspension>
           #2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1157:12)
           <asynchronous suspension>
           #3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1009:27)
           <asynchronous suspension>
           #4      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #5      AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
           <asynchronous suspension>
           #6      CommandRunner.runCommand (package:args/command_runner.dart:197:13)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:278:9)
           <asynchronous suspension>
           #8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #9      AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
           <asynchronous suspension>
           #10     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:234:5)
           <asynchronous suspension>
           #11     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:64:9)
           <asynchronous suspension>
           #12     run.<anonymous closure> (package:flutter_tools/runner.dart:62:12)
           <asynchronous suspension>
           #13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #14     AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
           <asynchronous suspension>
           #15     runInContext (package:flutter_tools/src/context_runner.dart:73:10)
           <asynchronous suspension>
           #16     main (package:flutter_tools/executable.dart:90:3)
           <asynchronous suspension>

[   +3 ms] (lldb) process detach
[  +96 ms] ensureAnalyticsSent: 98ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hook priority 4
[   +1 ms] Shutdown hooks complete
[        ] exiting with code 1

flutter-run-vs-code-logs.txt
I wonder, is there any timeouts that could cause this? It takes a few seconds for the last step where it says it's waiting for observatory port and the app actually launching.

I have the same exact issue, I have been searching/trying for days now and nothing seems to work, the odd thing that my head can't get around it is when I create a new project that runs as supposed to with Vscode or flutters run command.
this problem only occurs on old projects.

My terminal output.
[        ] Application launched on the device. Waiting for observatory port.
[+30013 ms] Installing and launching... (completed in 52.7s)
[        ] Error launching application on mohamed’s iPhone.
[   +4 ms] "flutter run" took 127,874ms.
[   +4 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:644:9)
           <asynchronous suspension>
           #2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1157:12)
           <asynchronous suspension>
           #3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1009:27)
           <asynchronous suspension>
           #4      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #5      AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
           <asynchronous suspension>
           #6      CommandRunner.runCommand (package:args/command_runner.dart:197:13)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand.<anonymous closure>
(package:flutter_tools/src/runner/flutter_command_runner.dart:278:9)
           <asynchronous suspension>
           #8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #9      AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
           <asynchronous suspension>
           #10     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:234:5)
           <asynchronous suspension>
           #11     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:64:9)
           <asynchronous suspension>
           #12     run.<anonymous closure> (package:flutter_tools/runner.dart:62:12)
           <asynchronous suspension>
           #13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #14     AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
           <asynchronous suspension>
           #15     runInContext (package:flutter_tools/src/context_runner.dart:73:10)
           <asynchronous suspension>
           #16     main (package:flutter_tools/executable.dart:90:3)
           <asynchronous suspension>

[   +2 ms] (lldb) process detach
[ +255 ms] ensureAnalyticsSent: 256ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hook priority 4
[   +1 ms] Shutdown hooks complete
[        ] exiting with code 1

I have exactly the same issue and have been struggling all day to solve it.

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.

@ziyuw @moesaid Can either of you provide flutter run --verbose along with flutter doctor -v ?


feat(tutorial): complete step 5

Closes #
mybluemix.net URL for my deployed app:
https://carbon-tutorial-cassandratait.mybluemix.net/
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

Hi @alisonjoseph !
Thanks for your review. I've edited the pull request description with my bluemix url of the deployed app. here it is again: https://carbon-tutorial-cassandratait.mybluemix.net/
Sorry for forgetting to add it.
Thanks again.


[SPARK-22807] [Scheduler] Remove config that says docker and replace with container

What changes were proposed in this pull request?
Changes discussed in https://github.com/apache/spark/pull/19946#discussion_r157063535
docker -> container, since with CRI, we are not limited to running only docker images.
How was this patch tested?
Manual testing

cc/ @vanzin @ueshin @jiangxb1987 @erikerlandson @liyinan926

Can one of the admins verify this patch?

Can one of the admins verify this patch?

LGTM.

I'm picking up a few stragglers from git grep
resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/k8s/submit/steps/BaseDriverConfigurationStep.scala
33=private[spark] class BaseDriverConfigurationStep(
49:  private val driverDockerImage = submissionSparkConf
51:    .getOrElse(throw new SparkException("Must specify the driver Docker image"))
113:      .withImage(driverDockerImage)

core/src/test/scala/org/apache/spark/deploy/SparkSubmitSuite.scala
95=class SparkSubmitSuite
399:      "--conf", "spark.kubernetes.driver.docker.image=bar",
415:    conf.get("spark.kubernetes.driver.docker.image") should be ("bar")

Done, did another pass over them. Thanks @erikerlandson

LGTM

add to whitelist

Please cleanup the PR description.

ok to test

Test build #84979 has started for PR 19995 at commit b3e1af3.

LGTM pending tests.

LGTM pending tests.

Test build #84979 has finished for PR 19995 at commit b3e1af3.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84979/
Test FAILed.

@ueshin @vanzin SparkR failure seems unrelated to me. Any ideas?

retest this please

Test build #84986 has started for PR 19995 at commit b3e1af3.

The R tests are pretty flaky recently, any ideas @HyukjinKwon ?

Seems it's related with https://github.com/apache/spark/commit/e58f275678fb4f904124a4a2a1762f04c835eb0e somehow and then fine back now. I am not yet entirely sure how this change relates to CRAN check. Will take a look soon.
Some related discussions - https://github.com/apache/spark/pull/19721, https://github.com/apache/spark/pull/19944, https://github.com/apache/spark/pull/19957 and https://github.com/apache/spark/pull/19961 in an order.

Test build #84986 has finished for PR 19995 at commit b3e1af3.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84986/
Test FAILed.

retest this please

Test build #85004 has started for PR 19995 at commit b3e1af3.

Test build #85004 has finished for PR 19995 at commit b3e1af3.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/85004/
Test FAILed.

FYI, AppVeyor failure is fixed separately in #20003.

Test build #4013 has started for PR 19995 at commit b3e1af3.

Test build #4013 has finished for PR 19995 at commit b3e1af3.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

retest this please

retest this please

Test build #85053 has started for PR 19995 at commit b3e1af3.

@foxish rebasing and pushing it will make the AppVeyor test passed for sure.

@HyukjinKwon done. Thanks!

Test build #85055 has started for PR 19995 at commit ace4b19.

Test build #85053 has finished for PR 19995 at commit b3e1af3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/85053/
Test PASSed.

Test build #85055 has finished for PR 19995 at commit ace4b19.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/85055/
Test PASSed.

LGTM

@ueshin, can this and https://github.com/apache/spark/pull/20007 be merged now?

Merging to master.


Improve layout of packages page

What feature would you like to be added?
currently requires too much scrolling -- do the cards need to be page width?
https://microsoft.github.io/autogen/dev/packages/index.html
Why is this needed?
improve readability of docs

cc @diegolescano

Page has been removed


feature Implement spill to disk for hash join, aggregation and sort for pipelineX

Proposed changes
Support spill to disk for pipelinex engine, support operator sort, hash join and aggregation.


It is better to add 'elevation' where has 'zIndex'

Hello, I suggest to add 'elevation' where has 'zIndex'. If only has 'zIndex', Android device may display under other component.
<Animated.View
  style={{
    width: '100%',
    position: 'absolute',
    zIndex: 100,
    // Add elevation to support Android
    elevation: 100,
    opacity: cond(this.height, 1, 0),
    transform: [
      {
        translateY: this.translateMaster,
      },
      {
        translateY: sub(this.height, this.state.initSnap) as any,
      },
    ],
  }}
>

<Animated.View
  style={{
    zIndex: 101,
    // Add elevation to support Android
    elevation: 101,
  }}
  onLayout={this.handleLayoutHeader}
>

Is this why for example, my react-native-paper buttons are displaying on top of the bottom sheet?

waiting to approve the pull request. 😞

any solution?

any solution?


Roman/feature/store

#45

Travis automatic deployment: https://46-pr-ching.surge.sh

Travis automatic deployment: https://46-pr-ching.surge.sh


Update azure-deploy.json

Modified the ARM template to parameterize the current hardcoded storage endpoint (blob.core.windows.net). Other Azure clouds (Germany, China, Gov) have different end points. Users will need to change this for the chosen cloud in the azure-deploy-parameters.json file.
The default value in the parameter file is blob.core.windows.net since this is expected to be the most common value.
Current endpoints are:
Azure China: blob.core.chinacloudapi.cn (https://msdn.microsoft.com/en-us/library/azure/dn578439.aspx)
Azure Gov: blob.core.usgovcloudapi.net (https://docs.microsoft.com/en-us/azure/azure-government/documentation-government-services-storage)
Azure Germany: blob.core.cloudapi.de (https://docs.microsoft.com/en-us/azure/germany/germany-developer-guide)

Confirmed parameterization of storage endpoint works with default value for Azure Commercial cloud.


build package failed

Hello!
I'm trying to build a package using build.sh script and getting following error:
➜  package git:(master) ✗ ./build.sh
Building project...
User defaults from command line:
IDEArchivePathOverride = /tmp/build.xcarchive
xcodebuild: error: The project named "NVDAEGPUSupport" does not contain a scheme named "NVDAEGPUSupport". The "-list" option can be used to find the names of the schemes in the project.
Building package...
pkgbuild: Inferring bundle components from contents of /tmp/build.xcarchive/Products/
pkgbuild: Writing new component property list to /tmp/build.plist
pkgbuild: error: Specified root path "/tmp/build.xcarchive/Products/" does not exist.
Building distribution...
productbuild: warning: No package found for distribution URL
Using Xcode 8.2.1
Mac OS 10.13.1
Please advice!

obviously I need to upgrade my xcode first=)


Weighted enrichment

Make use of the "score" column in the FOI files. A score should represent "strength", or "significance" of any given FOI. If FOIs overlapping with GFs have high score, their overlaps should be up-weighted in the enrichment calculations.

GenomeRunner_statistics_weight.xlsx


Detect if fs.rmSync is available to avoid the runtime deprecation warning

Description
Detect if fs.rmSync is available to avoid the runtime deprecation warning triggered for using fs.rmdirSync with { recursive: true } in Node.js v16, or the recursive property removing completely in the future Node.js version.
The  runtime deprecation warning image is shown blow, please check this doc.
Type of change
Please delete any options that are not relevant.

User interface (UI) (Maybe? Since the deprecation warning is shown in the update progress)
Other

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

@Computroniks THX for advises, I've keep the space. The spaces was removed by eslint's auto-fix :(

@Computroniks Oh I see, I removed the inproperly conflict resolving.


Aeotec Multisensor 6 incorrectly becomes Asleep when USB powered

Aeotec Multisensor 6 (ZW100) can be either battery or USB powered. When it is USB powered, it should always be awake as per:
https://aeotec.freshdesk.com/support/solutions/articles/6000115071-difference-between-usb-and-battery-power-and-recommendations-multisensor-6-zw100-
However, the device appears as Asleep in Zwavejs2mqtt control panel. This causes delays when changing zwave configuration parameters, as you have to manually wake up the device via action button to reflect any changes. Expected behaviour when USB powered is for the device to appear as Alive.
Device information
Aeotec Multisensor 6 (ZW100)
Node id 35
Previously working device - Home Assistant 2021.1.5 with default zwave integration allowed to change settings without needing to manually wakeup the device first. The device also worked as a repeater.
Installation information
Portainer installation 1.0.0-rc.1 ZwaveJS 6.0.2
Additional context

zwavejs.log

Hoping to reopen this issue except with the Aeotec Water Sensor 6 using the dock and connected to USB power. I am seeing that it is showing as asleep even when connected just like the Multisensors were.

Please make a zwave-js log, loglevel debug or silly and attach it here as a file.
While the log is running, re-interview the node (refreshInfo) or however that is called on zwavejs2mqtt.

Pretty long and I have a couple of reinterviews in this log but node 96 is the water sensor that is showing as asleep.
zwavejs_1.log

@Nixon506E according to the log, Node 96 thinks it can sleep:
17:08:46.713 CNTRLR « [Node 096] received response for protocol info:
                      basic device class:    Routing Slave
                      generic device class:  Notification Sensor
                      specific device class: Notification Sensor
                      is a listening device: false <== HERE
                      is frequent listening: false <== and HERE

Could it be that you included it on battery power and then switched to USB?

I didnt think I did but I’ll try a repair and see if that solves it

I didnt think I did but I’ll try a repair and see if that solves it

I tried multiple times and always got the node to report as sleepy. I am seeing that the configuration value that is read only for powersource is showing 2 which should be bit 0 reading usb power and bit 1 reading as not sleepy so somewhere it is being read incorrectly, aeotec has been known to not follow standards all the time...

Just to be sure, did you also hard reset the node between exclusion and inclusion?

I factory reset the node, yes

can you re-interview it again and make another log?

I have tried to re-include this node multiple times now with no luck. I am getting a sleepy state even though the config values are telling me the device is USB powered.
Maybe you can take a look at what was done in this driver for hubitat.
https://community.hubitat.com/t/release-aeotec-water-sensor-6-w-dock/39292
It looks like that driver uses the config value so maybe they also were having issues with the interview states:
if (cmd.parameterNumber==9) {             Map evt=[name:"powerSource"]             switch (cmd.configurationValue[0]) {                 case 0:                     evt.value="mains"                     evt.descriptionText = "${device.displayName} USB powered"                     if (txtEnable) log.info evt.descriptionText                     eventProcess(evt)                     break                 case 1:                     evt.value="battery"                     evt.descriptionText = "${device.displayName} Battery powered"                     if (txtEnable) log.info evt.descriptionText                     eventProcess(evt)                     break             }             switch (cmd.configurationValue[1]) {                 case 0:                     state.sleepy=true                     break                 case 1:                     state.sleepy=true                     break                 case 2:                     state.sleepy=false                     break             }     }

I'm not going to hard-code driver behavior based on a configuration parameter of a single device that is only available later. The protocol info listening: true/false is meant exactly for that, because it is available to the controller without having to communicate with the node.
I really need to see that log from your re-interview.

I definitely can understand that, like I said, aeotec has been known to not adhere to standards sometimes, I am just wondering if maybe that is what is going on and maybe you can confirm. Attached is the latest log with the re-inclusion and reinterview.
zwavejs.log

Am I correct in assuming the node got ID 101 and 102 in the meantime? If so, both think they are battery-powered and still send wakeup notifications (right until the end of the log):
11:34:43.484 CNTRLR « [Node 102] received wakeup notification

We have another issue where the opposite was true. The device thought it was USB powered and only became non-listening after a couple of resets: https://github.com/zwave-js/node-zwave-js/issues/1578#issuecomment-774773130
I'm pretty sure that this sensor works, because I have a couple of them myself - all USB powered.

Yes, it is node 101 then 102. Sounds like I am correct in assuming that aeotec did not properly setup the interview process to change based on if it is in the dock or not, only a config value.

When changing between battery and USB, you have to exclude and hard-reset every device that can do this. Seems like the reset didn't go through in your case 🤷🏻♂

I did a successful hard reset according to the lights on the sensor every time, not sure what do think as the device knows its usb powered in the configuration params...

Your firmware is quite old, maybe that changes with an update, which is possible through zwave-js (zwavejs2mqtt) without excluding again:
https://aeotec.freshdesk.com/support/solutions/articles/6000036562-how-to-update-multisensor-6-z-wave-firmware-

Yup, this could be it:
1.07 2016/3/4 2.Fixed the issue that the Listen Flag in the NIF will be changed after inclusion

It is not a multisensor but rather the water sensor, so no new firmware...
https://aeotec.freshdesk.com/support/solutions/folders/6000186005

Oh damn I missed that. Might be worth asking the support what the hell is going on with that thing.

Looks like we can close this one as Aeotec officially said that the water sensor in a dock is still a sleepy device that is always awake and they don't plan on changing it. Thanks for the help, guess I should have reached out to them first.


Image tokens dimension mismatch with the layernorm bias dimension

File "/home/usr/anaconda3/envs/varpt13/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/home/usr/anaconda3/envs/varpt13/lib/python3.8/site-packages/coca_pytorch/coca_pytorch.py", line 246, in forward
context = self.context_norm(context)
File "/home/usr/anaconda3/envs/varpt13/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/home/usr/anaconda3/envs/varpt13/lib/python3.8/site-packages/coca_pytorch/coca_pytorch.py", line 25, in forward
return F.layer_norm(x, x.shape[-1:], self.gamma, self.beta)
File "/home/usr/anaconda3/envs/varpt13/lib/python3.8/site-packages/torch/nn/functional.py", line 2515, in layer_norm
return torch.layer_norm(input, normalized_shape, weight, bias, eps, torch.backends.cudnn.enabled)
RuntimeError: Expected weight to be of same shape as normalized_shape, but got weight of shape [1024] and normalized_shape = [1000]

does your image_dim on CoCa init match up with the dim of the vit?

could you post a simple reproducible script?

could you post a simple reproducible script?

I just ran the code that you provide in the README.md
import torch
import vision transformer
from vit_pytorch.simple_vit_with_patch_dropout import SimpleViT
from vit_pytorch.extractor import Extractor
vit = SimpleViT(
image_size = 256,
patch_size = 32,
num_classes = 1000,
dim = 1024,
depth = 6,
heads = 16,
mlp_dim = 2048,
patch_dropout = 0.5  # https://arxiv.org/abs/2212.00794
)
vit = Extractor(vit, return_embeddings_only = True, detach = False)
extractor will enable it so the vision transformer returns its embeddings
import CoCa and instantiate it
from coca_pytorch.coca_pytorch import CoCa
coca = CoCa(
dim = 512,                     # model dimension
img_encoder = vit,             # vision transformer - image encoder, returning image embeddings as (batch, seq, dim)
image_dim = 1024,              # image embedding dimension, if not the same as model dimensions
num_tokens = 20000,            # number of text tokens
unimodal_depth = 6,            # depth of the unimodal transformer
multimodal_depth = 6,          # depth of the multimodal transformer
dim_head = 64,                 # dimension per attention head
heads = 8,                     # number of attention heads
caption_loss_weight = 1.,      # weight on the autoregressive caption loss
contrastive_loss_weight = 1.,  # weight on the contrastive loss between image and text CLS embeddings
).cuda()
mock text and images
text = torch.randint(0, 20000, (4, 512)).cuda()
images = torch.randn(4, 3, 256, 256).cuda()
train by giving CoCa your text and images with return_loss = True
loss = coca(
text = text,
images = images,
return_loss = True  # set this to True to get the full caption + contrastive loss
)
loss.backward()

@szxuhongye it runs for me
which version of coca-pytorch are you on? and are you on the latest vit-pytorch?

coca-pytorch 0.07 and vit-pytorch 0.40.2

@szxuhongye it runs for me
which version of coca-pytorch are you on? and are you on the latest vit-pytorch?

coca-pytorch 0.07 and vit-pytorch 0.40.2

@szxuhongye hmm, that looks ok
which version of pytorch?

@szxuhongye also, can you give the full trace?
torch  1.13.1 and the following is the full trace：

Traceback (most recent call last):
File "playground.py", line 39, in
loss = coca(
File "/home/usr/anaconda3/envs/coca/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/home/usr/anaconda3/envs/coca/lib/python3.8/site-packages/coca_pytorch/coca_pytorch.py", line 433, in forward
image_embeds, image_tokens = self.embed_image(images=images, image_tokens=image_tokens)
File "/home/usr/anaconda3/envs/coca/lib/python3.8/site-packages/coca_pytorch/coca_pytorch.py", line 412, in embed_image
img_queries = self.img_attn_pool(img_queries, image_tokens)
File "/home/usr/anaconda3/envs/coca/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/home/usr/anaconda3/envs/coca/lib/python3.8/site-packages/coca_pytorch/coca_pytorch.py", line 245, in forward
context = self.context_norm(context)
File "/home/usr/anaconda3/envs/coca/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/home/usr/anaconda3/envs/coca/lib/python3.8/site-packages/coca_pytorch/coca_pytorch.py", line 25, in forward
return F.layer_norm(x, x.shape[-1:], self.gamma, self.beta)
File "/home/usr/anaconda3/envs/coca/lib/python3.8/site-packages/torch/nn/functional.py", line 2515, in layer_norm
return torch.layer_norm(input, normalized_shape, weight, bias, eps, torch.backends.cudnn.enabled)
RuntimeError: Expected weight to be of same shape as normalized_shape, but got weight of shape [1024] and normalized_shape = [1000]

@szxuhongye i see, the Extractor may be broken in pytorch 1.13.1 and not returning the embeddings, and instead, returning the logits

@szxuhongye hmm no, it still works for me try running all the cells in that colab

@szxuhongye hmm no, it still works for me try running all the cells in that colab. it is also on pytorch 1.13.0

It is truly wired that it works after I uninstall and reinstall the entire environment. Thank you for your response.

glad it is working now 😁


Fix flake in TestChatSearchInbox, fix don't query for aliases

i think this will address the flake people were seeing, if not the extra logging should help track it down

added the fix for correctly parsing the query so we don't also search for aliases of the search query


服务注册可选不注册自己

service discovery register with self configuration by yoyogo.cloud.discovery.register-enable: false | true


Ubuntu binaries: error while loading shared libraries: libfreeimage.so.3

Hello, I'm on Ubuntu 18.04 and I downloaded the binary from:
https://github.com/DLR-SC/tigl/releases/download/v3.2.2/TIGL-3.2.2-ubuntu_18.04-x86_64.tar.gz
When I tried to run the binary I got the following error.
error while loading shared libraries: libfreeimage.so.3: cannot open shared object file: No such file or directory

Let me know if you need more information! Thanks!

As expected, this solved the issue
sudo apt-get install libfreeimage-dev

But I didn't see requirements anywhere and though the binaries included everything required.

Thanks for opening an issue here, @iiwolf!
The recommended way to install TiGL on Linux is by following the instructions in our wiki: https://github.com/DLR-SC/tigl/wiki/Downloads#linux. Here you will find a link to the OpenBuildService with installation instructions for your distribution, or - if you restricted rights - you can use the provided shell script. This will make sure all requirements are met.
Another option would be to install tigl using Anaconda/Miniconda/Miniforge, though this installation only includes the library and not the TiGL Viewer:
conda install tigl3 -c dlr-sc

I think what @iiwolf  is trying to say is, that freeimage is probably not downloaded via the get_tixi_tigl.sh script. Otherwise, it would be part of the ubuntu package (i suppose)


did youtube banned you?

did anyone use this package, did youtube find it out? anyone banned?

Having this 2 years now in my app and nothing has happened. I wouldn't worry that much, there's no way youtube can ban you trough this. This app doesn't use any key or anything. They would have to ban every single user that is using app with this lib. Very unlikely


DeprecationWarnings when used with Webpack 4

(node:13928) DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead
(node:13928) DeprecationWarning: Tapable.apply is deprecated. Call apply on the plugin directly instead

Fixed by #3

Perhaps also publish to NPM?

Ran into a snag with npm permissions, then forgot 😅 Now published!


Add the abilitty to easily specify per-CE tokens

To reduce the strength of any given token used to submit to a CE, frontend operators should be generating tokens with aud` fields restricted to the targeted CE. GlideinWMS should support simple configuration for per-CE tokens.

Solved with PR #108.


All .lein-* files should be ignored.

It seems that commonly, all .lein-* artifacts are ignored while committing to repository.

Thanks, but are arbitrary files with this prefix ever actually created? Are there specific files that are missing?

If there are any specific files missing from the rules, we can add them, but I'm reluctant to add a wildcard without it being documented that all such files should be ignored.


Fix Development environment

The development environment currently does not work in Pycharm, when running or debugging it would appear that the command from the dockerfile is not run therefore the container starts but dJango isnt running.


test

Type: Other
Summary:
test
Details:
test
Resolution:
test
Affected definitions:

SoftButton 0.1.0

You can review the change introduced to the full definition at ClearlyDefined.


zmanage info error on macOS

Please check the existing issues to make sure you're not duplicating a report.
For bug reports, please provide the following information:

Zim commit ref: 071ddaf
Zsh version: zsh 5.2 (x86_64-apple-darwin15.2.0)
$(uname -msr): Darwin 15.6.0 x86_64

Description
On macOS the uname command does not accept the option -o; which is called from  ~/.zim/tools/zim_info.
$ zmanage info
Zim commit ref:   071ddaf
Zsh version:      zsh 5.2 (x86_64-apple-darwin15.2.0)
uname: illegal option -- o
usage: uname [-amnprsv]
System info:

Steps to reproduce
$ uname -msr
Darwin 15.6.0 x86_64

Seem ZIM is not tested on latest macOS versions (not beta). the ls command does not understand options beginning with -- as well.

Yes, I primarily use Linux and not BSD machines, so there may be some differences in command arguments that may cause things to unexpectedly break. It seems that the uname command on Darwin systems use a different command syntax. I will remediate this issue shortly. Thanks for the report and sorry it's taken me so long to reply and fix such a trivial issue. :+1: :)


feat: support strongly typed dva model[WIP]

Checklist

[ ] npm test passes
[x] tests are included
[ ] documentation is changed or added
[ ] commit message follows commit guidelines

Description of change

Add watchers to accommodate non-trivial saga. It is supposed to move old watcher effect under the new watchers key.
Add strongly typed model definition
Add new package dva-action to describe action shape, which is essential to strongly typed model definition and dispatching.
Bump redux-saga dependency version to 1.x for better typing and new effect descriptor and effect helper( i.e. delay, debounce, etc)

try this https://github.com/DiamondYuan/dva-model-creator


Significantly slower when enabling "-i" option

I found that for some reason IERC oracle among with flashloan leading to interpretator memory growth.
E.g without these flags memory is ~1000, but with them turned on -> length is close to u64 MAX.
flashloan.rs : line 479
 // if a program counter can transfer any token, with value > 0 & dst = caller
        // then we give maximum rewards to trigger the bug
        {
            let call_target: EVMAddress = convert_u256_to_h160(interp.stack.peek(1).unwrap());
            let offset = interp.stack.peek(offset_of_arg_offset).unwrap();
            let size = interp.stack.peek(offset_of_arg_offset + 1).unwrap();
            if size >= EVMU256::from(4) {
                let data = interp.memory.get_slice(as_u64(offset) as usize, as_u64(size) as usize);


Doubt regarding facebook integration for windows phone 8.1 silverlight app?

Hi,
I am developing a windows phone 8.1 silverlight application . For my application I integrated the facebook login. For this facebook integration I used the login with facebook app method.
My doubt is after getting the app id from the dev center , I updated the appid at developers.facebook.com , wmmanifest.xml (In extensions protocol (msft-appid without dashes)) . Or do I need to change the product id in the place holder also , I tried to change the productid also but I am getting error like some signature is wrong try with different signature. I am confused how to do it .
Any help,
Thanks...

Look at the documentation for silverlight apps or load the Facebook-WP8.sln from the github repository which has a full sample. Closing since this is not a bug. If you need help coding this up, please open a discussion on stackoverflow.


[BEAM-2861] Fix tests which fail with google credential

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

A workaround way to fix tests in utils_test.py which fail if GCP dependencies are installed but no GOOGLE_APPLICATION_CREDENTIAL.

cc: @charlesccychen

+R: @peihe

Coverage increased (+0.007%) to 69.683% when pulling e1c822c4fd9628ea112a54f7227725a2cdc21efc on markflyhigh:fix-unit-test into e9d3a4a799a43a3a9d73527d83ead143b7a66fda on apache:master.

Verified this fixed the python build on my machine.
R: @charlesccychen


Programmatically migrate templates

Summary

Relevant Technical Choices
Uses Rollup to create an ES bundle for use with the CLI script, as webpack does not support ES module output.
To-do

[x] Tests for bin/utils/updateTemplates.js

User-facing changes

Testing Instructions

Build the migration script by running npx rollup --config bin/rollup.config.js
Manually lower the version number of one of the templates
Run npm run workflow:templates
Verify that templatee has been migrated to the current version
Verify that the version key of the template object is at the top of the file.

See #2120

@dvoytenko @mariano-formidable Would love to get your feedback on this (again).Is it worthwhile?


Support multiple hosts.xml files in application package

While the pre-process directives in services.xml allows you a lot of flexibility when configuring Vespa, it fails to easily address a common use-case for many applications; having the exact same setup in two different regions where only hostnames differ.
While this possibly could be modeled using pre-process directives, it becomes unnecessarily complex given the straight-forward use-case. We should support multiple hosts.xml files in the application package (e.g. hosts-east.xml and hosts-west.xml) and then have deployment API (and vespa-deploy) take a parameter indicating appropriate file to use.

client side ...


enhancement: relaxed shortcut key support

Currently the accelerator doesn't accept more than one main key:
https://github.com/tauri-apps/tao/blob/dev/src/accelerator.rs#L281
I'm curious what the reasoning is behind this? As a user of the type of app I'm building, I'd love to be able to assign more than one main key to my shortcut.

What is the key combination you'd want to use? I never saw an app with more than one main key so I am a bit curious.

In this instance, it's a omnibar task-runner type app and I'd love to leave it fully up to the user. I know some folks like to keep it simple, and some people have a lot of bindings they're trying to work around.
Something like ctrl + space + x or alt + space + a  or shift+alt+space doesn't seem unreasonable for a keyboard shortcut.

You can have multiple modifiers (Shift, Alt, Ctrl) but only one main Key is supported.

ctrl+space+x is not supported.
alt+space+a is not supported.
shift+alt+space is supported.

Doing multiple keys is really unusual. For instance, VSCode requires you to press a sequence for shortcuts. For example, if you have ctrl+space+x shortcut, users need to press Ctrl+Space then Ctrl+X within a short period of time.

I can recreate the described functionality in several of the task launchers I'm using as inspiration. Would you say this is a stylistic choice, not a technical limitation?

Our current implementation of GlobalShortcuts (Which might be removed soon btw) has a limitation on Windows, that it can have multiple modifiers but only one main key. See https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-registerhotkey

Totally understand and appreciate the head's up on the deprecation, thanks!


Crowdfunding and crowdsourcing AndStatus project

@rodneyrod asked in #329 :

does this project have some sort of bountysource presence or something similar to donate to?

@rodneyrod We have only generic donation way now: http://andstatus.org/donate.html
But reading on https://en.m.wikipedia.org/wiki/Bountysource I just realised that addition of something like that for crowdfunding specific features may allow to attract new developers to the project, who would be payed for implementation of that specific features in a case funders agree with implementation and the code was merged into the main project source code repository... I.e. to crowdsouce the project.
Should we do this and if yes, how?

I would give it a try. Thus you can get a rough estimation what users really want if they're willing to donate some money for specific enhancements.


Create .service files for both services

Already created but not tested

Works but has an open issue #10


improve timeout Idle View styling

my current naive styling (reusing ModalTextRevealer) could do with a bit of love:

critical for V1: currently the background cover doesn't fill the full height of the about page:

done in #159


new modern and minimal UI

Update current app ui to more modern and clean UI following Material3 guidelines.

Hi @SidharthMudgil ,
it's good to meet you and this wonderful project. I personally loved the concept of Personalised recommendations on music. I would like to work on this first UI issue and later work on the other issues. I would like to know if you have any specific design in your mind or any file. So we can go for that. Please let me know.
Thank You 🤝

Thanks, @Ashok-Kumar-dharanikota, I do not have any specific design in my mind but I am thinking of more cleaner and modern UI. If you have any design in your mind share it with me by mail. I you want to work on this issue I will assign it

Okay no problem 😊, I will go through some design inspirations and I will let you know.

Hi @SidharthMudgil ,
I updated the UI background and the item's color code. Replaced with colors that would create much eye-catching, and applied bold style to text to make it easily readable.  A few designs first inspired me. But in order to give complete justification. The app needs more advancements. I think it is good to split big work into smaller parts and work on it, rather than bulky operation.
I noticed that you forgot to add the hacktoberfest tag to this.  Kindly please add it and I will raise a PR for this issue.
Thank you 😊

The Repository is marked hactoberfest so don't worry... please provide apk and screenshots or demo for the update

This three screenshots refers to three changes I made which turns into more simplified UI.

Background:

From the user perspective, I felt the background and the UI items don't have a matching color pattern. It is difficult to view two irrelevant colors in the screen. I read an article about how colors lead to different emotions for a person.
And from Login layout to on-boarding layout. the most covered color is white. When the user moved to the chat layout. It gives a different color or background that covers the entire screen. So, for simplicity, I used a white background.

Stroke Color and readability of text

When the chat is started. i felt the stroke of the option item was stressful for the eyes. I replaced it with gray color. and text also in normal size. By applying bold style. It wont take much stress for person to read it.

Song item
Instead of dark_black. i used dark blue. Just felt it feels much better.

🤔 it looks same also I preferred the previous background more... Can you share side by side ss of both

Hi @SidharthMudgil , sorry for the late response. Okay sure i will give old and new UI side by side. So you can find out the difference. I'm not claiming the background is bad. It is actually different from the colour codes we used for buttons and textviews. That's only the difference.

UI difference
I actually forgot to bold the textview_bot text. If its applied. You may find it more readable.


testing

Issue #, if available:
Description of changes:
Check points: (check or cross out if not relevant)

[ ] Added new tests to cover change, if needed
[ ] Build succeeds with all target using Swift Package Manager
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1816 (ded3567) into ameter/test-release-clean (6c9a405) will increase coverage by 0.00%.
The diff coverage is 68.42%.

:exclamation: Current head ded3567 differs from pull request most recent head 1a3cc46. Consider uploading reports for the commit 1a3cc46 to get more accurate results

@@                    Coverage Diff                     @@
##           ameter/test-release-clean    #1816   +/-   ##
==========================================================
  Coverage                      59.22%   59.22%
==========================================================
  Files                            716      716
  Lines                          21966    22002   +36
==========================================================
+ Hits                           13009    13031   +22
- Misses                          8957     8971   +14

Flag
Coverage Δ

API_plugin_unit_test
62.51% <ø> (ø)

AWSPluginsCore
71.22% <ø> (ø)

Amplify
46.85% <ø> (-0.02%)
:arrow_down:

Analytics_plugin_unit_test
71.09% <ø> (ø)

Auth_plugin_unit_test
78.67% <68.42%> (-0.18%)
:arrow_down:

DataStore_plugin_unit_test
75.81% <ø> (-0.02%)
:arrow_down:

Geo_plugin_unit_test
52.12% <ø> (ø)

Predictions_plugin_unit_test
26.81% <ø> (ø)

Storage_plugin_unit_test
58.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...th/AWSCognitoAuthPlugin/AWSCognitoAuthPlugin.swift
37.50% <ø> (ø)

...Configuration/AmplifyAWSServiceConfiguration.swift
73.91% <ø> (ø)

...AuthPlugin/Operations/AWSAuthSignInOperation.swift
74.57% <58.62%> (-15.75%)
:arrow_down:

...itoAuthPlugin/AWSCognitoAuthPlugin+Configure.swift
82.52% <100.00%> (+0.34%)
:arrow_up:

...Behavior/AWSCognitoAuthPlugin+ClientBehavior.swift
100.00% <100.00%> (ø)

...endency/AuthenticationProviderAdapter+SignIn.swift
71.50% <100.00%> (+0.62%)
:arrow_up:

...thPlugin/Models/Options/AWSAuthSignInOptions.swift
100.00% <100.00%> (ø)

.../DataStore/Model/Internal/Schema/ModelSchema.swift
64.00% <0.00%> (-2.00%)
:arrow_down:

...gin/Sync/InitialSync/ModelSyncedEventEmitter.swift
89.58% <0.00%> (-1.05%)
:arrow_down:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Selecting some objects with left click does not highlight them

I'm using laptop with 2 Graphics Cards - Nvidia and Intel. OS is Archlinux, drivers are nouveau and mesa. When hovering over face of an object it changes color from grey to slightly brighter grey, but after left clicking face its color is indistinguishable from non-clicked variant. The object is selected, because I can freely move it and change its attributes, but it is not highlighted in blue as it would be in Windows. The same applies to lines in sketches - after left clicking them, they won't become highlighted, but program selects them properly.
Attaching photos below:
Sketch line not selected:

Sketch line selected:

Object face hovered over:

Object face clicked:

Object face not selected:

Surprisingly, it works on some things (circular faces):

No errors show up in terminal when clicking objects. On windows after clicking objects they turn slightly blue.Also, when selecting operations in timeline, bodies created by those operations won't highlight.
Edit:
After some digging, I can confirm the problem does not occur when switching OpenGL to DirectX9. However, after changing window size on DX9 the toolbar becomes unreadable(full of artifacts instead of icons)

@blazej222 Thank you very much for this information. I'll take a look at it later.

I can confirm this issue. Ubuntu 21.04 with Intel HD 620, driver is:
/lib/modules/5.11.0-31-generic/kernel/drivers/gpu/drm/i915/i915.ko

I've tested multiple configurations, and this problem occurs only on Intel GPU and only with OpenGL as renderer - after switching to DX9 I was able to run Fusion without any issues (I fixed crashes on DX9 with Intel GPU by removing xf86-video-intel and other xf86- related packages, btw. those cause a lot of problems with Fusion so use modesetting driver instead if you encounter any issues).
My card is also Intel HD 620.
So, looks like it has something to do with Intel OpenGL implementation?

Ok, did some more testing and was able to reproduce this issue on Nvidia card (with DRI_PRIME=1) on nouveau drivers. Same case as Intel GPU, no highlighting on OpenGL renderer, works perfectly fine on DX9 renderer.
glxinfo -B on nouveau:
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: nouveau (0x10de)
    Device: NV118 (0x134d)
    Version: 21.2.1
    Accelerated: yes
    Video memory: 2047MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.3
    Max compat profile version: 4.3
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: nouveau
OpenGL renderer string: NV118
OpenGL core profile version string: 4.3 (Core Profile) Mesa 21.2.1
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.3 (Compatibility Profile) Mesa 21.2.1
OpenGL shading language version string: 4.30
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

glxinfo -B on Intel:
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) HD Graphics 620 (KBL GT2) (0x5916)
    Version: 21.2.1
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 620 (KBL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.2.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.2.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Both use Mesa OpenGL, so that could be the problem.

I was able to fix this by using DXVK and DX9. See #78


docs: publish Stencil JsonDocs types with @ionic/docs

This adds a copy task to the Stencil config that copies Stencil's JsonDocs types to the docs package directory as types.d.ts and adds that to the files array in package.json so it can be published.
{
  type: 'copy',
  dir: '../docs',
  copy: [
    {
      src<EMAIL_ADDRESS>      dest: 'types.d.ts'
    }
  ]
}

The idea is to bundle the types as they were when the package was published so they can be used alongside the JSON data.

@brandyscarney @liamdebeasi I'm not sure how to test that this change works with the release process. Any ideas? My desired outcome is that types.d.ts is published alongside core.json in the docs package.

How are the types supposed to be used?
types.d.ts does not have a default export, like you would expect in a json file.

I think we can solve this problem much better at the stencil level, i would say not merge.

Great idea! We'll be able to do essentially the same thing, but from within the stencil build, since rebuilds may change types, and then others would be able take advantage of this. Thanks


gcd(1,0) return 0

Description

Type: Bug
Priority: Major

Bug
gcd(1, 0) = 1
but
mbedtls_mpi_gcd(1, 0) return 0 !!!
test
mbedtls_mpi A,B,X;
mbedtls_mpi_init( &A ); mbedtls_mpi_init( &B ); mbedtls_mpi_init( &X );
mbedtls_mpi_lset(&A, 1);
mbedtls_mpi_lset(&B, 0);
mbedtls_mpi_gcd(&X,&A,&B);
return X == 0 !!!.
to fix add check:
if (mbedtls_mpi_cmp_int(B, 0) == 0)
return mbedtls_mpi_copy(G, A);

@abc34 THank you for reporting this issue!
We will look into this

@abc34 Thank you for your fix suggestion!
Will you be willing to accept our CLA and contribute your fix as a PR?
Unfortunately, we cannot  accept the fix without a CLA being accepted.
If this is a personal contribution, the easiest way to do this is if you create an mbed account and accept this click through agreement. Alternatively, you can find a slightly different agreement to sign here, which can be signed and returned to us, and is applicable if you don't want to create an mbed account or alternatively if this is a corporate contribution.
Thanks for your understanding and again, thanks for the contribution!

Mbed account created and accept this click through agreement.Message: You accepted the Contributor Agreement on Fri 04 Jan 2<IP_ADDRESS>9, 13:03, "Ron Eldor" notifications@github.com:@abc34 Thank you for your fix suggestion!
Will you be willing to accept our CLA and contribute your fix as a PR?
Unfortunately, we cannot  accept the fix without a CLA being accepted.
If this is a personal contribution, the easiest way to do this is if you create an mbed account and accept this click through agreement. Alternatively, you can find a slightly different agreement to sign here, which can be signed and returned to us, and is applicable if you don't want to create an mbed account or alternatively if this is a corporate contribution.
Thanks for your understanding and again, thanks for the contribution!
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.


user retcode-passthrough by default for salt_version latest

Hi, seems salt-call --retcode-passthrough is no longer un-documented feature, so we should use it by default if latest keyword is used.
https://docs.saltstack.com/en/latest/ref/cli/salt-call.html

Hi @simonmcc, are you about to merge or too busy? I am asking as I am about to bring some features to kitchen-salt but prior I was about to merge the couple of interesting PR on this repo. What would work for you the best - are you going to merge PRs in a queue or you would rather if I would provide a one PR with most waiting PR already merged?

@epcim just looking into why the CI check is failing, looks like some of the key decryption failed

This was fixed by #48

As noted by @jbussdieker this was collected into #48


Create configure-tls.md

Proposed changes

Unreleased project version (optional)

Related issues (optional)

I'll kick Netlify. In the meantime, please correct the title and add something into the PR description, following the template. Thanks!


There are no diversity metrics in eval_diversity.py

Hi,
Thank you for your source code!
I wonder what the role of eval_diversity.py is, since there are no diversity metrics, like novel words, new sentences in the file. So what is the difference between eval.py and eval_diversity.py?
Thank you
Ryan.

Hi Ryan,
eval_diversity.py creates a numpy file for consensus reranking.
See point 3 under pretrained models and evaluation.
Thanks,
Shweta

Many thanks. I got it!


Implement production gRPC healthcheck

This PR refactors gRPC init checks to use the server-side healthcheck
It also moves all I/O code within the __init__ method of Connection to a dedicated connect() function that must be called before the client works correctly. The motivation for this is due to the impending async implementation wherein the I/O checks will have to be performed using async/await syntax which is forbidden inside __init__ methods
This method is still called by the __init__ method of the Client and WeaviateClient classes. However, in future, this should be changed also so that client.connect() must always be called (and thus await client.connect() for async)

Codecov Report
Attention: 127 lines in your changes are missing coverage. Please review.

Comparison is base (0224f0a) 89.43% compared to head (879d1a9) 89.19%.
Report is 32 commits behind head on beta/v4.0.

Files
Patch %
Lines

weaviate/proto/v1/search_get_pb2.py
0.00%
63 Missing :warning:

integration/test_collection_rerank.py
33.33%
24 Missing :warning:

integration/test_batch_v4.py
91.09%
13 Missing :warning:

integration/test_collection_filter.py
84.00%
8 Missing :warning:

integration/conftest.py
86.27%
7 Missing :warning:

integration/test_collection_geo.py
78.57%
3 Missing :warning:

weaviate/connect/connection.py
90.62%
3 Missing :warning:

weaviate/collections/grpc/query.py
80.00%
2 Missing :warning:

integration/test_collection_aggregate.py
96.66%
1 Missing :warning:

integration/test_collection_batch.py
96.55%
1 Missing :warning:

... and 2 more

Additional details and impacted files
@@              Coverage Diff              @@
##           beta/v4.0     #683      +/-   ##
=============================================
- Coverage      89.43%   89.19%   -0.25%
=============================================
  Files            142      151       +9
  Lines          16551    16519      -32
=============================================
- Hits           14803    14734      -69
- Misses          1748     1785      +37

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


create nfs-client-provisioner with RBAC, still Got  cannot list persistentvolumeclaims error

k8s vision: 1.8.1
I have adapted yaml to k8s 1.8.1,but still got error like that,after i create pvc.

github.com/kubernetes-incubator/external-storage/lib/controller/controller.go:411: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:serviceaccount:kube-system:nfs-provisioner" cannot list persistentvolumeclaims at the cluster scope

here is my yamls
---
kind: Deployment
apiVersion: extensions/v1beta1
metadata:
  name: nfs-client-provisioner
spec:
  replicas: 1
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: nfs-client-provisioner
    spec:
      serviceAccount: nfs-provisioner
      containers:
        - name: nfs-client-provisioner
          image: registry.cn-hangzhou.aliyuncs.com/szss_quay_io/nfs-client-provisioner:v2.0.1
          volumeMounts:
            - name: nfs-client-root
              mountPath: /persistentvolumes
          env:
            - name: PROVISIONER_NAME
              value: fuseim.pri/ifs
            - name: NFS_SERVER
              value: <IP_ADDRESS>
            - name: NFS_PATH
              value: /opt/k8s
      volumes:
        - name: nfs-client-root
          nfs:
            server: <IP_ADDRESS>
            path: /opt/k8s
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: nfs-provisioner

---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: nfs-client-provisioner-runner
rules:
  - apiGroups: [""]
    resources: ["persistentvolumes"]
    verbs: ["get", "list", "watch", "create", "delete"]
  - apiGroups: [""]
    resources: ["persistentvolumeclaims"]
    verbs: ["get", "list", "watch", "update"]
  - apiGroups: ["storage.k8s.io"]
    resources: ["storageclasses"]
    verbs: ["get", "list", "watch"]
  - apiGroups: [""]
    resources: ["events"]
    verbs: ["list", "watch", "create", "update", "patch"]

---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: run-nfs-client-provisioner
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner
    namespace: default
roleRef:
  kind: ClusterRole
  name: nfs-client-provisioner-runner
  apiGroup: rbac.authorization.k8s.io
---

I'm getting this too despite following the auth guide :( any ideas?

@deerjoe @cdrage I solved the problem. I think it is a compatibility issue.
Change ClusterRole.apiVersion to rbac.authorization.k8s.io/v1beta1

谢了兄弟，我试试。@JinsYin

@JinsYin 可否贴出rbac.yaml，我修改成v1beta1，还是出错。

@JinsYin @deerjoe I pushed a fix here: https://github.com/kubernetes-incubator/external-storage/pull/653

thx a lot @cdrage it help，i use the wrong sa name in deployment。


linera-service: collect and make available build version info

Motivation
https://github.com/linera-io/linera-protocol/issues/1555

Proposal
Add a build script that collects the version info required, and uses it to populate a static struct available inside linera-service.

Test Plan
Run the script directly to see the generated versions.

Release Plan
This PR is invisible to users — no version bump required.
Links

reviewer checklist

Closing in favour of https://github.com/linera-io/linera-protocol/pull/1560.


Troubles Subclassing Sprite with TypeScript - game is not instance of Phaser.Game

Hello, having issues subclassing Sprite with TypeScript.  From searching and reading documentation it seemed the preferred method was to subclass, instantiate the subclass, then use game.add.existing() to tie it to the game.
Trying to do that but encountering an instanceof error based on the code that seems to have been added to a recent point release.  (Phaser.Component.Core.init checks types of the game, x, and y arguments).
For some reason (I'm new to TypeScript), setting a breakpoint in chrome console and issuing the typeof call does return "object" for the Phaser.Game but it is clearly an instance of Phaser.Game
console
From the class extending Phaser.State:
this.game.add.existing(
  new Turret(this.game, x, y));

From the Phaser.Sprite:
export default class Turret extends Phaser.Sprite {

    constructor(game : Phaser.Game, x: number, y: number) {
        super(game, x, y, 'turret');
   }
}

Uncaught Error: The value passed as the game argument ([object Object]) is not an instance of Phaser.Game.
at Turret.Phaser.Component.Core.init (phaser-split.js?2ffb:23760)
at Turret.Phaser.Sprite [as constructor] (phaser-split.js?2ffb:27188)
at new Turret (Turret.ts?348e:7)
at eval (Setup.ts?60fe:43)
at Array.forEach ()
at Setup.create (Setup.ts?60fe:40)
at Phaser.StateManager.loadComplete (phaser.js?b1d1:28696)
at Phaser.StateManager.preUpdate (phaser.js?b1d1:28462)
at Phaser.Game.updateLogic (phaser.js?b1d1:35260)
at Phaser.Game.update (phaser.js?b1d1:35207)
Phaser.Component.Core.init @ phaser-split.js?2ffb:23760
Phaser.Sprite @ phaser-split.js?2ffb:27188
Turret @ Turret.ts?348e:7
(anonymous) @ Setup.ts?60fe:43
Setup.create @ Setup.ts?60fe:40
loadComplete @ phaser.js?b1d1:28696
preUpdate @ phaser.js?b1d1:28462
updateLogic @ phaser.js?b1d1:35260
update @ phaser.js?b1d1:35207
updateRAF @ phaser.js?b1d1:63029
_onLoop @ phaser.js?b1d1:63012

Perhaps I am missing something or doing it wrong.  Thanks!

Try setting a breakpoint on https://github.com/photonstorm/phaser-ce/blob/v2.8.3/src/gameobjects/components/Core.js#L65 and examining the value of game there.

Still the same.  I'm tempted to set skipTypeChecks to true but can't quite figure if that is a property I can set either.  Is this something the end user can set?

What value does it show in the Scope pane at that breakpoint?
You can set Phaser.Component.Core.skipTypeChecks = false.

Have you already tried out this?
this.turret = new Turret(this.game, x, y);
export default class Turret extends Phaser.Sprite {

    constructor(game : Phaser.Game, x: number, y: number) {
        super(game, x, y, 'turret');

        game.add.existing(this);
   }
}

@samme intriguingly it shows a Phaser.Game
@digitsensitive just so I understand, your suggestion is to still call the same super constructor, then use the call to add an existing sprite?  I think the problem is the super constructor, so I never made it to any other lines in the constructor.  Just gave it a shot to make sure - and yeah, can't get past the Phaser.Sprite(game, x, y) constructor.
Also TypeScript doesn't like Phaser.Component.Core.skipTypeChecks = true; -
(15,16): error TS2339: Property 'Component' does not exist on type 'typeof Phaser'.

Finally trying Phaser['Component'].Core.skipTypeChecks = true; sidestepped TypeScript and also the type safety of the Sprite constructor and I'm back in business here.  But I don't really want to be skipping type checks!

It's fine to use skipTypeChecks = true, it's a bit redundant if you're already using TypeScript. It won't affect any of your TypeScript checks.
Indeed Phaser.Component isn't in the definitions at all, sorry about that.
It's still strange that your game argument is failing instanceof Phaser.Game. Are you extending Phaser.Game in any way? All the same, if the game is running fine, it's probably not important.

not sure if it helps you, but have a look at one of my small projects and have a look at my configurations:
https://github.com/digitsensitive/phaser-machine-learning/tree/master/experiments/atari-pong
maybe it would help to send the github link to your project, so I can have a look?

Just chipping in to say that I'm having the exact same issue.

Logging typeof game says that it's just an object, and not Phaser.Game

That's normal, but try (game instanceof Phaser.Game).

Ah, got it mixed up.
However I found the solution for my setup, I was just importing Phaser the wrong way.
In my project's main file, phaser is imported as import 'phaser' at the top level, and in my Player class I did import * as Phaser from 'phaser-ce', as that's what the IDE suggests. Nothing seemed off in the type suggestions.
Before game instanceof Phaser.Game returned false, now it's true.
Is this not relevant on your end, @lucasgray?

Ha, that fixed my issue as well.  I would be interested to know how the difference in import statement resolves the instanceof issue

Property 'Component' does not exist on type 'typeof Phaser'.

Fixed in dc149ab, thanks.

confirm that while I hadnt checked imports and replace all phaser with phaser-ce nothing work. Some joke was in that thing instanceof checking show that this.game was instance of Game.

i do it in a  similar case:
lean/phaser-es6-webpack#64


Filezilla: removed hash url

I removed the hash url from the autoupdate section.

What's the reason for this change?

I heard, that it is not necessary to provide an url to the hash values. But I may be wrong.
Sorry, I am very new to this.

It's not necessary, that's right but it should be preferred. It reduces traffic on my server and the download servers. Scoop auto-update server will download the files and calculate the hashes if no URL is provided.


Backend: PostProcessor: combine annotations

I was also thinking of ignoring the score of tests that errored so that if a microservice gives 100 by default even if it errors, or 0 we don't screw up everything


InsufficientPrivilegesForManagedServiceResource

I get "InsufficientPrivilegesForManagedServiceResource" error when I run the template. Is linking partner ID a mandatory step? Can I deploy the template without a partner ID?

Can you point me to the template you are deploying?
From an RBAC perspective, we require the customer (who onboard) to be Owner.

Thanks for a quick reply @krnese
This is the template I'm using:
https://github.com/Azure/Azure-Lighthouse-samples/blob/master/Azure-Delegated-Resource-Management/templates/delegated-resource-management/delegatedResourceManagement.json

And you are:

Deploying this as a user in the customer tenant?
The user has Owner permission at the subscription?
You deploy it as a subscription level template (New-AzDeployment / az deployment create)?

I'm deploying it in the customer tenant using New-AzDeployment. I'm the GA in the customer tenant and owner on the subscription.
I created a TemplateParameterFile by including my Principal ID and Reader Role Def ID in the authorizations section of the file.

Are you deploying it as a guest account, or a user belonging to the customer AAD?
Can you pls deploy it as a user originating from the customer AAD with Owner permission at scope?

I followed the Powershell steps mentioned in this document
https://docs.microsoft.com/en-us/azure/lighthouse/how-to/onboard-customer
I'm a user in customer AAD and I have owner permission at the subscription

Thanks. Can you please open a support ticket so we can investigate further?

I experienced exactly the same issue.
i was connect with azure ad only (connect-azureAD).
When i connected to the azure account it worked (Connect-AzAccount).
Good Luck!

Let me try that
Thanks @dorankerkhofs

Did it work?


⚠ Turnos 24x7 has degraded performance

In d109f2a, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 894 ms

Resolved: Turnos 24x7 performance has improved in 49a78db.


Flake8 rule 'W292' reported an invalid point

Flake8 reported an invalid point for the rule W292, with the messge no newline at end of file.
Code below:
class TestDutch(unittest.TestCase):
    def setUp(self):
        self.epi = epitran.Epitran(u'nld-Latn')

    def _derivation(self, orth, correct):
        attempt = assemble_ipa(self.epi.word_to_tuples(orth))
        # logging.debug(u'{} ?= {}'.format(attempt, correct).encode('utf-8'))
        self.assertEqual(attempt, correct)

    def test_bernhard(self):
        self._derivation(u'Bernhard', u'bɛrnhɑrt')

    def test_utrecht(self):
        self._derivation(u'Utrecht', u'ʏtrɛxt')

    def test_lodewijk(self):
        self._derivation(u'Lodewijk', u'loːdeːʋɛjk')

    def test_random(self):
        self._derivation(u'ertogenbosch', u'ɛrtoːɣɛnbɔs')

Debug information:
Atom version: 1.16.0
Flake8 version: 3.2.1 (pyflakes: 1.3.0, pycodestyle: 2.2.0, mccabe: 0.5.3) CPython 2.7.6 on Linux

This is almost certainly the unicode bug (pycqa/flake8#306) which has been fixed on flake9's master branch and is just waiting on a new release over there.
Unfortunately until they release the fix there nothing can be done about it here.


JavaScript code for processing student input in editor is visible

Challenge http://www.freecodecamp.com/challenges/waypoint-comment-your-javascript-code has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
The JS instructions for processing the lesson are visible in the instructions.

Thanks for posting this issue!
That should be showing up there. It's part of all the javascript based challenges that you are able to see the tests that are running against your code. See #2231 for a similar issue/explanation.

You're welcome and I was interested in what I was seeing....the test code that is.  It does make the test instructions difficult to read though.  Just an opinion, but nothing that deters me. :)


feat(CommandHandler/onlyNsfw)

After looking at a comment in Akairo Discord of a user wanting to add a onlyNsfw: true property to the Command class I decided it was a nice feature to have and since it didn't look too hard I got my hands into it.
basically if onlyNsfw: true but the channel is not NSFW the CommandHandler will emit the notNsfw event and pass the message object and the command ran so the user can listen to it and send custom messages, log it etc
I decided to Pull Request it to your fork as it is more updated than Akairo official repo and since I myself use it. If you need anything changed lmk, tested everything except listening for the event (It's late, will do tomorrow if I remember) and it worked, results are in Akairo discord General chatroom.

looks good


is it possible to use permitAll access with using ClientAuthenticationFilter?

Since ClientAuthenticationFilter redirects the user to the login page before AccessDecisionManager, it seems to be impossible to use permitAll access. If I want to allow anonymous users to certain url, how should it be done?

Closing. URLs protected by the ClientAuthenticationFilter are intentionally protected. Do not see an issue nor feature request in this issue.


Pretrained model not downloadable?

Hi,
Thanks for this awesome work. It looks like the pretrained models don't seem to be available to download? I tried to download all 4 of them (e.g. http://public.vinai.io/models/blur-kernel-space-exploring/REDS_woVAE.pth) They don't seem to be downloadable... Is it possible to provide a public google drive link?
Thank you so much,

I'm using Google Chrome browser on a Mac. It looks like using Safari I was able to access and download.  Thank you! :)


zoomAnim event firing

The zoomAnim event is not being fired after the map has loaded, and an area is being zoomed to using leaflet-control-boxzoom...
Even if an area is scroll-zoomed to, then BoxZoomed, the zoomAnim event is not fired for the BoxZoom zoom.

Can you publish a fiddle/codepen/playground that displays this behaviour?

My apologies, I am unable to create a test at this time, as it would require tons of retyping/manual copying from a  non-connected system.
Basically, adding in the BoxZoom control to an existing LeafLet map causes this behavior. This happens on the FIRST time the BoxZoom is used.

@scgrant327 when you say "BoxZoom control", do you mean the built-in box zoom that is enabled by holding down Shift and dragging a rectangle on the map, or are you using a plugin control?
If this is a behaviour you're seeing in a plugin, you should file an issue with that plugin instead.

Yeah, it's a plugin:
https://github.com/gregallensworth/L.Control.BoxZoom
I'll post an issue to GitHub and update here when I get a response.

Ok, closing for now.


weechatScripts.weechat-matrix: fix matrix_sso_helper path

server.py tries to launch a matrix_sso_helper binary when connecting to
a homeserver that uses some SSO mechanism instead of plain login and
password, but doesn't have $out/bin in $PATH.
Using substituteInPlace to patch server.py so that the helper process is
started by using its actual filesystem location instead of relying on
$PATH.
Fixes: https://github.com/NixOS/nixpkgs/issues/124186
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 124265 at f7ccc5f3 run on x86_64-linux 1

1 package built successfully:

weechatScripts.weechat-matrix

1 suggestion:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/applications/networking/irc/weechat/scripts/weechat-matrix/default.nix:80:0:
   |
80 |     description = "A Python plugin for Weechat that lets Weechat communicate over the Matrix protocol";
   | ^

FWIW: I don't think the backport action works yet, please open a pr to backport this to release-21.05.


Add merge functionality on Directory object

What changes were proposed in this pull request?
Add support for mergeing two com.microsoft.hyperspace.index.Directory objects. Pre-requisite for #163
Feature Description
We need a functionality to merge two directory trees in order to support future functionalities like Append and Optimize. When we create index only on partially unindexed data, we need to make sure to log the latest snapshot of the index as the combination of previously created index files and newly created index files. This can be done through the suggested merge api on index Directory.
Example Usecase: Merge contents of partially created indexes in case of append:

User creates index on original data. This index is stored in index directory (say) index/v__=0. This will be stored in metadata as

content = Content(
  root: Directory(
     ..
     ..
             Directory(
                name = "v__=0"
                files = ...
                ...
            )
   )
)

User adds new data and calls refreshIndex(mode = "quick"). This will create another intermediate Content object similar to above, with name = "v__=1".

We can now call content.root.merge(content2.root) to deduplicate the directory structure.

Does this PR introduce any user-facing change?
no

How was this patch tested?
unit tests

Could you add the merge result of "v__=0" and "v__=1" simply in description?

Also, please update the PR description to indicate which uber-issue this is part of.

Could you add the merge result of "v__=0" and "v__=1" simply in description?

thanks @sezruby , added

Also, please update the PR description to indicate which uber-issue this is part of.

Thanks! I saw you updated the PR description. Can you link to the uber-issue please?

Also, please update the PR description to indicate which uber-issue this is part of.

thanks @rapoth , updated the PR description

I rebased your branch, so make sure to run git pull.

Merging to master! @sezruby / @rapoth, feel free to review this and leave any comments if needed.

LGTM. All my comments have been resolved. Thanks a lot @apoorvedave1!


Resurrector Serum breaks the game when administered to a Pokémon

Just tested using the DEV command to "resurrect" and it nuked the game/UI. I would post code but my log like is a GIG long, due to the PW_Legendary error happening 800 times a second.

It may probably be due to the way the mod handle Pokémon feature (CompPokemon & subcomponents) after their death. I believe the mod simply destroys the data and the game cant find them again if the Pokémon is resurrected.

Fixed, it was indeed a problem of setting stuff to null after death when i shouldn't have


Beautiful README

Really nice to read through, great idea to list out the issues you faced throughout the project 👍
The only thing I would add would be instructions to run the project locally. (See the How section [here](https://github.com/dwyl/hapi-login-example-postgres#how for an example of this).

We'll be sure to add that in! Thanks 😊


Laravel 11.16.0 Shift

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v11.16.0 branch.
Before merging, you need to:

Checkout the shift-ci-v11.16.0 branch
Review all pull request comments for additional changes
Run composer update
Thoroughly test your application (no tests?, no CI?)

:warning: The Shift build servers run PHP 8.2. If you are running a different version of PHP you should run composer update locally to ensure you have the proper versions of your dependencies to reflect your PHP environment.


Added siimple to Gabo's Awesome CSS Frameworks

Added siimple to Gabo's Awesome CSS Frameworks in the General Purpose section.

Hello @gabrielizalo thank you!
I wonder if it could be added to the lightweight frameworks section, because the latest version it's 9.4Kb gzipped (https://bundlephobia.com/result?p=siimple@3.3.0).
Anyway, thanks for adding it :smile:

Perfect.. It's done.
;)