Remove unnecessary async import in hello world example

In Webpack 5, wasm-based imports are now supported, and can be imported directly

FYI - I just did the  Hello World example index.js - I'm happy to do the rest of the examples and update the docs if this seems reasonable. Just getting my feet wet with Rust WASM so I haven't actually looked at the other examples. I was going through the quickstart and thought surely the webpack peeps have resolved their issue (since the issue number was so low) and they did a while ago.

Yeah if Webpack now supports it I think it'd be good to migrate examples to using this new pattern since it's more along-the-lines of what most would expect

Just as a data point to the contrary (which I unfortunately haven't been able to flesh out to a useful bug report to webpack) we had to give up on using experiments.asyncWebassembly in webpack 5 and fall back on experiments.syncWebassembly and explicit dynamic imports that the rest of the codebase has to await before using our WebAssembly module, because with experiments.asyncWebassembly (under Next.js 12) we would see next build and next dev hang for minutes, spinning millions of times through stack frames within webpack and eventually crashing. Did not exactly help assuage my colleagues' worries about ecosystem maturity around WebAssembly. 😁
This was in Next.js 12.0.* versions last month (and they are pulling in pretty fresh webpack 5 versions I believe). I haven't managed to create a clean repro case for this, and can't rule out that it was triggered by something specific to our codebase (beyond just its size) but in any case the behavior was quite inscrutable and it sure didn't seem to us like all issues have been cleared up there.

Ok then, I'll add some commits to the PR to go through all the examples and review the docs to make sure they reflect the code accurately

Sorry been quiet on this. I started to go through the examples, but I couldn't get them running. When I try to build the wasm, it panics:
[INFO]: 🌀  Compiling to Wasm...
    Finished release [optimized] target(s) in 0.10s
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', /Users/billhannah/.cargo/registry/src/github.com-1ecc6299db9ec823/wasm-bindgen-cli-support-0.2.78/src/descriptor.rs:205:15
stack backtrace:
   0:        0x10f734521 - std::backtrace_rs::backtrace::libunwind::trace::h310ac7aacd577bf8
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/../../backtrace/src/backtrace/libunwind.rs:90:5
   1:        0x10f734521 - std::backtrace_rs::backtrace::trace_unsynchronized::had33a05577c9d011
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:        0x10f734521 - std::sys_common::backtrace::_print_fmt::hd9acce3818e5f1bc
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/sys_common/backtrace.rs:67:5
   3:        0x10f734521 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h4edbddd26fc45697
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/sys_common/backtrace.rs:46:22
   4:        0x10f75089b - core::fmt::write::h266c957f12b1655a
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/fmt/mod.rs:1163:17
   5:        0x10f7313ba - std::io::Write::write_fmt::h65d4ee621e8d810d
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/io/mod.rs:1696:15
   6:        0x10f735b85 - std::sys_common::backtrace::_print::h9a5ef67cfa8b031e
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/sys_common/backtrace.rs:49:5
   7:        0x10f735b85 - std::sys_common::backtrace::print::h99dfbbc518768f3b
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/sys_common/backtrace.rs:36:9
   8:        0x10f735b85 - std::panicking::default_hook::{{closure}}::h5b4886cd9f93dfca
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:210:50
   9:        0x10f73576f - std::panicking::default_hook::h986d152c7bd7e732
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:227:9
  10:        0x10f736270 - std::panicking::rust_panic_with_hook::h151f3b3bf37b4f17
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:624:17
  11:        0x10f735d0e - std::panicking::begin_panic_handler::{{closure}}::hf6660086d9ebd48c
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:521:13
  12:        0x10f734997 - std::sys_common::backtrace::__rust_end_short_backtrace::h34152178ea368a9a
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/sys_common/backtrace.rs:139:18
  13:        0x10f735c7a - rust_begin_unwind
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:517:5
  14:        0x10f78609f - core::panicking::panic_fmt::hb64a2db862b4aca0
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/panicking.rs:100:14
  15:        0x10f786066 - core::panicking::panic_bounds_check::h66e87d7dddc1fcf1
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/panicking.rs:76:5
  16:        0x10f4e48b5 - wasm_bindgen_cli_support::descriptor::Descriptor::_decode::he5966b127e1c2a38
  17:        0x10f4e4c19 - wasm_bindgen_cli_support::descriptor::Function::decode::h4d5fd506e450d6d4
  18:        0x10f4e43d1 - wasm_bindgen_cli_support::descriptor::Descriptor::_decode::he5966b127e1c2a38
  19:        0x10f4e55a7 - wasm_bindgen_cli_support::descriptors::execute::h8f61dce6cc2bc06f
  20:        0x10f48c27c - wasm_bindgen_cli_support::Bindgen::generate_output::ha700ab9f4661ea92
  21:        0x10f4522a0 - wasm_bindgen_cli_support::Bindgen::generate::h1957e8ff5cd1ac7e
  22:        0x10f4559ac - wasm_bindgen::main::h5f4ebc172bf6cabf
  23:        0x10f453826 - std::sys_common::backtrace::__rust_begin_short_backtrace::h5373bb0b12f21495
  24:        0x10f45383c - std::rt::lang_start::{{closure}}::h482aa165a155a951
  25:        0x10f73416f - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h042bcf1eeb382749
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/ops/function.rs:259:13
  26:        0x10f73416f - std::panicking::try::do_call::h58aa98b024209748
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:403:40
  27:        0x10f73416f - std::panicking::try::hcfc7bc2af44bc609
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:367:19
  28:        0x10f73416f - std::panic::catch_unwind::h88980c0eb694c110
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panic.rs:133:14
  29:        0x10f73416f - std::rt::lang_start_internal::{{closure}}::hc07a850a9bc371e5
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/rt.rs:128:48
  30:        0x10f73416f - std::panicking::try::do_call::h061d0434866b3d81
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:403:40
  31:        0x10f73416f - std::panicking::try::h8d38c4e20b01fbf0
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:367:19
  32:        0x10f73416f - std::panic::catch_unwind::hc41b36baa54eb12d
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panic.rs:133:14
  33:        0x10f73416f - std::rt::lang_start_internal::h59ad95b3bebc83b2
                               at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/rt.rs:128:20
  34:        0x10f455f09 - _main
Error: Running the wasm-bindgen CLI
Caused by: failed to execute `wasm-bindgen`: exited with exit status: 101
  full command: "/Users/billhannah/.cargo/bin/wasm-bindgen" "/Users/billhannah/personal-work/wasm-bindgen/target/wasm32-unknown-unknown/release/char.wasm" "--out-dir" "/Users/billhannah/personal-work/wasm-bindgen/examples/char/pkg" "--typescript" "--target" "web"

That's likely a mismatch of the globally-installed wasm-bindgen and the wasm-bindgen in this repository. It's unfortunately not easy to make sure those are in-sync when you're doing in-repo development.

@billhannah can you go merge main into this? It seems like CI is the only blocker for this PR, which seems to be the only blocker. The other examples can be done in subsequent PRs

Replaced by #3503.


[BUG] FULL_DEMO of CORTEX_M3_MPS2_QEMU_GCC doesn't work sometimes

Describe the bug
FULL_DEMO of CORTEX_M3_MPS2_QEMU_GCC doesn't work sometimes
Target

CORTEX_M3_MPS2_QEMU_GCC
QEMU

Host

QEMU on Ubuntu on x86_64
QEMU on WSL

To Reproduce
$ cd Demo/CORTEX_M3_MPS2_QEMU_GCC/
$ make FULL_DEMO=1
$ qemu-system-arm  -machine mps2-an385 -monitor null -semihosting --semihosting-config enable=on,target=native -kernel ./build/RTOSDemo.axf -serial stdio -nographic
and wait for 10 seconds.
Expected behavior
FULL_DEMO app should print "OK: No errors", but it sometimes stop with the error message ""Error: Death "
CORTEX_M3_MPS2_QEMU_GCC/main_full.c has a "TimerMode" task which runs about 950ms and vTaskDelete itself. uxCurrentNumberOfTasks is decremented in idle task.
vCreateTasks in Common/Minimal/death.c sleeps for 1000ms in order to wait for other tasks to be created and set uxTasksRunningAtStart.
When uxCurrentNumberOfTasks is decremented after uxTasksRunningAtStart is set,
FULL_DEMO app stop with the message "Error: Death - tick count 10000"

Hi @anolivetree
Thank you for reporting the issue. We are looking to reproduce the issue and will start working on the fix.

Hi @anolivetree
We were able to reproduce the issue, and have created a patch for solving the same.
Can you please confirm, if the demo works for you?

@kar-rahul-aws
It works on my PC without any problems. Thank you for the fix!

@anolivetree
Thank you for the confirmation. Closing this issue.


Add platform compatability for darwin-21

What
Add platform compatability for darwin-21
Link to story
came out of me running a bundle install locally and don not think
it can do any harm?!
Checklist
Before you ask people to review this PR:

Tests and rubocop should be passing: bundle exec rake
Github should not be reporting conflicts; you should have recently run git rebase main.
There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
The PR description should say what you changed and why, with a link to the JIRA story.
You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
You should have checked that the commit messages say why the change was made.
You should have run NOCOVERAGE=true rake rswag to ensure the swagger docs are up-to-date

I think compatibility is already being address in this P: https://github.com/ministryofjustice/laa-hmrc-interface-service-api/pull/905/files#diff-89cade48462044ee1b672dc5f4c3ec250fbd29effcd8932096a23c1283c6731fR403

closed as superceded by https://github.com/ministryofjustice/laa-hmrc-interface-service-api/pull/905/files#diff-89cade48462044ee1b672dc5f4c3ec250fbd29effcd8932096a23c1283c6731fR403


⚠ ERROR - ENOENT: no such file or directory

Please see screenshot.

@johnrlive I'm sorry. I think I did a mistake. I will change the README file and Getting Started content.
Thank you for your review.


Migrate typed_message_listener.h to Value

Change the typed_message_listener.h and all child classes to use the
Value class in the interface, rather than using the Native Client
specific pp::Var.
As an additional outcome, the implementation of the
typed_message_router.cc file becomes completely free of pp::Var usages
as well.
This commit contributes to the goal of making most of the //common/cpp
library be toolchain-agnostic and support WebAssembly (as tracked
by #185).

Thanks.


Server CSS Errors

@jedihacks could you update the description and provide more information on this issue?

Sure thing!
To reproduce on /origin/develop branch; use 'npm start' from terminal.   Then go to your localhost copy, and you should get the following error.
If you refresh/go to other pages; you'll see a couple other errors all relating to CSS & the Hydrator.

@luiskcs89

I've found that there are some issues in jsdom related to this CSS parsing. The specific case of this screenshoot is due to last-child , but there are also issues when the font-family styles have spaces and so on. Some of the issues seem to be closed for newer versions of jsdom but stencil/core requires 11.5.1 which doesn't have those fixes.

Is there anything we can do to override the errors for now, or are the errors having any adverse effects?

From what I read, the errors don't have an adverse effect on the app, they just come from jsdom's css parser which doesn't support some legitimate CSS features (https://github.com/jsdom/jsdom/issues/2177#issuecomment-376139329). Looks like there is nothing we can do about this from our side.

Need to update rules for JSdom to silence CSS errors

Actually I am not seeing these error logs anymore on the current develop branch and this issue could probably be closed.

@daftclaud Can you confirm this is resolved on Thursday and If so close the defect.

Confirmed with Claudio that this can be closed. So Closing ticket

Just a comment: make sure you run npm run start as opposed to just npm start


Doesn't work for xml layout including

Seems that it cannot retrieve the content of included layout using <include>.

This functionality is not implemented but I think would be very useful.
Thanks, I will put this feature as a priority.

Created separate story for this issue.

if I add<EMAIL_ADDRESS>result will be abnormal too.


Evaluation Error Ran out of memory

Hi XiaoYee, thanks for your sharing. When I ran your code, VGG_GRU, I encounter a error when doing evaluation, Ran out of memory. I try many approaches, but it doesn't work. I even load test data by using train load function, but it still occurs. However, when training, it work fine. Would you like to give me some advices? thanks.

I found the solution. It is the output_feature that take up too much space.  when I add with "torch.no_grad():" before "for batch_idx, data,label in enumerate(test_loader): '' , it works


Change csi-vsphere-config Secret Name To Be Cluster-Specific

What would you like to be added:
We should make csi-vsphere-config vSphere secret names cluster-specific.
Why is this needed:
Right now, all workload cluster CSI drivers use the same set of vSphere credentials because eksa-system:csi-vsphere-config secret in the CRS is not scoped to a particular cluster.
In order to support using different sets of vSphere credentials for different workload clusters, we should explore creating cluster-specific eksa-system:csi-vsphere-config secrets.
We should also audit our other vSphere secrets to verify that they are not being used globally in an inappropriate fashion.

we dropped vsphere csi driver as a default-installed component, closing.


Notebooks: Remove unused prompts code

We were only using ConfirmPrompt here (which is based on some code from another OSS repo, and is just a simple wrapper around the showQuickPick() API).
Don't see much reason to keep a bunch of code around that we don't need, so cleaning up for sanity purposes (and it helps code coverage #s too, which is a nice bonus 😄)

Coverage decreased (-0.03%) to 35.044% when pulling 52989f39df7db2a2aa419934c29ca79d17453e29 on test/removeUnusednbPromptCode into 95107f1f611df05f85e1cc7122f088f4d9cc6aec on main.


Data model

In this Pull Request

[X] Create a new app called my blog and Connect the project with Postgres database set up.
[X] Initialize project with Git.
[X] Build your project schema.
[X] Create and run the necessary migration files.
[X] All columns that are foreign keys have a corresponding index.
[X]  Set up all necessary Linters.

Thank you very much @Mihndim2020 I really appreciate for your constructive feedback on call. just I'm sorry there was heavy rain and everything has been stopped.


fix(scene composer): refactoring video player to work with react 18 u…

…pdates
Overview
Refactor of the videoPlayer component to work with the React 18 updates & unblock users on main branch.
Some things to note...

video.js no longer exports their models. This creates issues when trying to use their built in features & accessing things such as controlBar. Due to this we had to introduce multiple anys with the use of // eslint-disable-next-line @typescript-eslint/no-explicit-any. This is not ideal, but is the scenario where any is necessary.
OnDemand works & the example app will now load without issue, however, LIVE mode is not fully functional. Updates to address that will come in a later update.
Casting for viewport will be addressed in the follow-up PR to resolve issues with LIVE mode.

https://github.com/awslabs/iot-app-kit/assets/6610619/59e89574-20da-4510-b838-d9d8a4428328
Verifying Changes
Scene Composer
For scene-composer package changes specifically, you can preview the component in the published storybook artifact. To do this, wait for the Publish Storybook action to complete below.

Click on the workflow details
Select the Summary item on the left
Download the zip file

To run the storybook build locally, you need a local static web server:
npm install -g httpserver
cd <Extracted Zip Directory>
httpserver

Then open the website http://localhost:8080 to run the doc site.
Legal
This project is available under the Apache 2.0 License.

@mumanity would you like for me to wait until the unit tests are passing to review? :)


Could not find zendesk.messaging:messaging-android:2.13.0 for building APK file.

Describe the bug
We have a expo dev-client application, I have installed the package and it works, but recently for android it is failing with the following issue:
Could not find zendesk.messaging:messaging-android:2.13.0
To Reproduce
Steps to reproduce the behavior:

try to build app with the installed react-native-zendesk-messaging

Expected behavior
execute build successfully
Screenshots

Environment (please complete the following information):

Platform: [Android]
React Native Version : "0.71.14"
Zendesk SDK Version : 0.2.1

Additional context
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:processDebugResources'.

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not find zendesk.messaging:messaging-android:2.13.0.
Searched in the following locations:
- http://<IP_ADDRESS>:8081/artifactory/libs-release/zendesk/messaging/messaging-android/2.13.0/messaging-android-2.13.0.pom
- file:/home/expo/workingdir/build/node_modules/react-native/android/zendesk/messaging/messaging-android/2.13.0/messaging-android-2.13.0.pom
- file:/home/expo/workingdir/build/node_modules/jsc-android/dist/zendesk/messaging/messaging-android/2.13.0/messaging-android-2.13.0.pom
- https://dl.google.com/dl/android/maven2/zendesk/messaging/messaging-android/2.13.0/messaging-android-2.13.0.pom
- https://repo.maven.apache.org/maven2/zendesk/messaging/messaging-android/2.13.0/messaging-android-2.13.0.pom
- https://www.jitpack.io/zendesk/messaging/messaging-android/2.13.0/messaging-android-2.13.0.pom
- https://oss.sonatype.org/content/repositories/snapshots/zendesk/messaging/messaging-android/2.13.0/messaging-android-2.13.0.pom
Required by:
project :app > project :react-native-zendesk-messaging

Did you add repository configuration to your build.gradle?
https://github.com/leegeunhyeok/react-native-zendesk-messaging/blob/master/docs/getting-started.md#android

Yes, I did that.

Also the repo has been changed from, 'https://zendesk.jfrog.io/artifactory/repo' changed to "https://zendesk.jfrog.io/ui/native/repo".
is there any special java version configuration fir parsing POM file?

I have tested all possible things but its so weird for me that event i used patch-package and changed the repo URL but another issue showing related to Parsing POM file is not well-formed! even i have updated to latest version.
Could not resolve zendesk.messaging:messaging-android:2.8.0.
Required by:
project :react-native-messaging-zendesk
> Could not resolve zendesk.messaging:messaging-android:2.8.0.
> Could not parse POM https://zendesk.jfrog.io/ui/native/repo/zendesk/messaging/messaging-android/2.8.0/messaging-android-2.8.0.pom
> The markup in the document preceding the root element must be well-formed.

It looks like  "build:ios:dev": "eas build -p ios -e development --local", ignore android/build.gradle, because any changes in this file not reflected on build

I have the same error. It looks like  "build:android:dev": "eas build -p android -e development --local", ignore android/build.gradle, because any changes in this file not reflected on build If run expo run:android - ok

our app is built on eas servers, so what can i do to resolve the build issue?

I have the same error. It looks like  "build:android:dev": "eas build -p android -e development --local", ignore android/build.gradle, because any changes in this file not reflected on build If run expo run:android - ok

our app is built on eas servers, so what can i do to resolve the build issue?

I added plugin to my app.config.json.
Now this plugin run for each build and check if /android/build.gradle has this repositories
withAndroidGradlePlugin.js
`const { withProjectBuildGradle } = require('@expo/config-plugins')
const {
createGeneratedHeaderComment,
removeGeneratedContents,
} = require('@expo/config-plugins/build/utils/generateCode')
// Because we need the package to be added AFTER the React and Google maven packages, we create a new allprojects.
// It's ok to have multiple allprojects.repositories, so we create a new one since it's cheaper than tokenizing
// the existing block to find the correct place to insert our camera maven.
const gradleMaven = allprojects { repositories { maven { url 'https://zendesk.jfrog.io/artifactory/repo' } } }
const withAndroidGradle = _config => {
return withProjectBuildGradle(_config, config => {
if (config.modResults.language === 'groovy') {
config.modResults.contents = addZendeskImport(config.modResults.contents).contents
} else {
throw new Error('Cannot add camera maven gradle because the build.gradle is not groovy')
}
return config
})
}
function addZendeskImport(src) {
return appendContents({
tag: 'zendesk-messaging',
src,
newSrc: gradleMaven,
comment: '//',
})
}
// Fork of config-plugins mergeContents, but appends the contents to the end of the file.
function appendContents({ src, newSrc, tag, comment }) {
const header = createGeneratedHeaderComment(newSrc, tag, comment)
if (!src.includes(header)) {
// Ensure the old generated contents are removed.
const sanitizedTarget = removeGeneratedContents(src, tag)
const contentsToAdd = [
// @something
header,
// contents
newSrc,
// @end
${comment} @generated end ${tag} \n,
].join('\n')
return {
  contents: sanitizedTarget ?? src + contentsToAdd,
  didMerge: true,
  didClear: !!sanitizedTarget,
}

}
return { contents: src, didClear: false, didMerge: false }
}
// TODO: add params like maven array and make this plugin reuseable for others maven
const withAndroidGradlePlugin = config => {
return withAndroidGradle(config)
}
module.exports = withAndroidGradlePlugin
`


Issue installing marketplace-eqp on Mac os sierra

The "https://repo.magento.com/packages.json" file could not be downloaded: SSL: Connection reset by peer
Failed to enable crypto
failed to open stream: operation failed

Getting this error after attempting to install. I never get prompted for any auth. I've tried setting up an auth.json file, according to the Composer docs, and added the public/secret keys that I set up with my Magento account, but get the same error as without having an auth.json.
Any tips?

I was able to resolve this by following this Issue
https://github.com/magento/marketplace-eqp/issues/2
I was under the impression this would be able to be installed "globally", but this works for me.

Actually, this does not seem to have worked. At first, I was getting the error
ERROR: the "MEQP1" coding standard is not installed. The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz and Zend

and then set the install path using...
vendor/bin/phpcs --config-set installed_paths /path/to/marketplace-eqp

and now the error is gone, but i get no output when actually trying to test an extension?

I've done the same, but I'm actually getting a fatal error:
Fatal error: Trait 'Utils\Helper' not found in .../vendor/magento/marketplace-eqp/MEQP2/Sniffs/Classes/CollectionDependencySniff.php on line 21

@Banjerr is this issue still actual? If yes, please provide steps to reproduce it.

@lenaorobei indeed it is. I believe the main problem is not being able to install with Composer; i'd get that SSL issue every time. Adding as a dependency on a project seemed to work, but that doesn't seem to work at all, similar experience to @erfanimani
Failed to enable crypto
failed to open stream: operation failed```

@Banjerr it seems like this problem is related to Magento packages repository. Please, find more about similar issues in the article and in the GitHub-thread.

@Banjerr was this answer helpful for you? Can I close this issue?

This is still an issue for me. I have installed phpcs from either composer or brew and it results in the same issue:
PHP Fatal error:  Interface 'PHP_CodeSniffer_Sniff' not found in /usr/local/etc/php-code-sniffer/Standards/MEQP1/Sniffs/Classes/Mysql4Sniff.php on line 15
PHP Stack trace:
PHP   1. {main}() /usr/local/Cellar/php-code-sniffer/3.0.2/bin/phpcs:0
PHP   2. PHP_CodeSniffer\Runner->runPHPCS() /usr/local/Cellar/php-code-sniffer/3.0.2/bin/phpcs:18
PHP   3. PHP_CodeSniffer\Runner->init() /usr/local/Cellar/php-code-sniffer/3.0.2/src/Runner.php:70
PHP   4. PHP_CodeSniffer\Ruleset->__construct() /usr/local/Cellar/php-code-sniffer/3.0.2/src/Runner.php:294
PHP   5. PHP_CodeSniffer\Ruleset->registerSniffs() /usr/local/Cellar/php-code-sniffer/3.0.2/src/Ruleset.php:206
PHP   6. PHP_CodeSniffer\Autoload::loadFile() /usr/local/Cellar/php-code-sniffer/3.0.2/src/Ruleset.php:1094
PHP   7. include() /usr/local/Cellar/php-code-sniffer/3.0.2/autoload.php:167

Fatal error: Interface 'PHP_CodeSniffer_Sniff' not found in /usr/local/etc/php-code-sniffer/Standards/MEQP1/Sniffs/Classes/Mysql4Sniff.php on line 15

Call Stack:
    0.0020     352832   1. {main}() /usr/local/Cellar/php-code-sniffer/3.0.2/bin/phpcs:0
    0.0037     507080   2. PHP_CodeSniffer\Runner->runPHPCS() /usr/local/Cellar/php-code-sniffer/3.0.2/bin/phpcs:18
    0.0140     860728   3. PHP_CodeSniffer\Runner->init() /usr/local/Cellar/php-code-sniffer/3.0.2/src/Runner.php:70
    0.0194    1082160   4. PHP_CodeSniffer\Ruleset->__construct() /usr/local/Cellar/php-code-sniffer/3.0.2/src/Runner.php:294
    0.0449    1179984   5. PHP_CodeSniffer\Ruleset->registerSniffs() /usr/local/Cellar/php-code-sniffer/3.0.2/src/Ruleset.php:206
    0.0450    1180040   6. PHP_CodeSniffer\Autoload::loadFile() /usr/local/Cellar/php-code-sniffer/3.0.2/src/Ruleset.php:1094
    0.0452    1203400   7. include('/usr/local/etc/php-code-sniffer/Standards/MEQP1/Sniffs/Classes/Mysql4Sniff.php') /usr/local/Cellar/php-code-sniffer/3.0.2/autoload.php:167

Any idea on how to resolve this, that would be very helpful. If I find a way to resolve it I will include it here below.

ok, I was able to make this work now. The only way it worked is with the older version of Code Sniffer 2.9.
I used brew to install it brew install<EMAIL_ADDRESS>and once it was installed properly everything worked as it should.
Seems like some work needs to be done to make this package play nice with the newer version.

@ronpeled did you installed via Composer by running $ composer create-project --repository=https://repo.magento.com magento/marketplace-eqp magento-coding-standard  command?
In composer.json we require version 2.6.2 of PHP_CodeSniffer.

@lenaorobei Yes.

@ronpeled what errors did you get in case of installing via Composer? In the provided stack trace I see version 3.0.2.

I'm not sure, but when I had php code sniffer 3.0.2 installed via composer that's when all the issues came up. It seems this version of code sniffer includes some additional config settings that take over the local setup with php code sniffer 2.6.2. Once removed, it all worked as expected.

@ronpeled I don't think problem related to code sniffer in any way, I bet it's purely Composer / system $PATH issue.
So, /usr/local/Cellar/php-code-sniffer/3.0.2/bin/phpcs:0 seems like globally installed phpcs (latest stable version) while this project requires version 2.6.2.
To make them play well with each other you need either to composer require this project globally (so that 2.6.2 version of phpcs is installed globally as well) or put it to some directory but then you should use not phpcs command but <YOUR DIRECTORY>/vendor/bin/phpcs.

@orlangur Yes I think you are correct. The issue was with the global phpcs I had setup on my environment. Once removed the local version worked as expected. All good now.
in my other comment I mentioned it would be ideal that it worked with any version of phpcs but I'm sure it's a bit more complicated. This package as is now works and is very helpful.
Side note: it would be ideal when Magento's core files will actually 'pass' these tests... :)

I don't think it makes sense due to

This is the first stable release of the 3.0 branch, and is a large refactoring of the code base. It breaks backwards compatibility for all custom sniffs and custom reports. An upgrade guide for sniff and report developers is available here: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Version-3.0-Upgrade-Guide

Everything is fine until proper constraints specified in composer.json.
Magento 2 main repo is currently using ancient 1.x version, after both repositories migrate to 3.x combined set of rules can be enforced for core. It will lead to improving both Magento code base and this coding standard I believe.

If there are any additional questions please refer to the Magento Stack Exchange for further discussion.

@ronpeled, Hello.
I am trying to understand what was de definitive solution to this issue. Could you please tell me if it is with composer or not?


When building miri from source, all executions fail with could not create LLVM TargetMachine

When building Miri from source, we've encountered the following error:
error: could not create LLVM TargetMachine for triple: x86_64-unknown-linux-gnu:
Unable to find target for this triple (no targets are registered)', src/setup.rs:36:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This occurs when running the test suite with ./miri test or running cargo miri <subcommand> in any context after ./miri install.
We've been able to reproduce this error after fully uninstalling the entirety of Rust, deleting and recloning the repository, and following the steps listed in CONTRIBUTING.md.
Only the stable toolchain (stable-x86_64-unknown-linux-gnu) is installed aside from miri. The machine we're using is running Arch (6/1 release). The native C/C++ compiler is clang 15.0.7. We're building a fork of miri, which is up to date with commit 1a80d1 on May 13th. We've seen the same error appear when running cargo miri setup in latest release of miri in nightly, but this error does not occur in that configuration when running cargo miri run or cargo miri test.
Are there any configuration options we should try and modify to fix this? Thanks!

You seem to be pretty deep into this, if you'd like to have more of a conversation than GitHub accommodates we have a #miri stream in the Rust Zulip: https://rust-lang.zulipchat.com/
I can't figure out how to build your fork of Miri, the normal process complains:
error: No suitable version of LLVM was found system-wide or pointed
              to by LLVM_SYS_160_PREFIX.

I suspect the problem you're running into is related to the fact that the miri executable is always linked to librustc_driver which is always linked to libLLVM. I guess you're coordinating LLVM versions between your rustc_driver and inkwell? How?

And just to get this out of the way, I'm an Arch user, Miri development works great on Arch.

Thanks for your response!
The purpose of the fork is to explore executing foreign functions in Miri using the LLI interpreter. That's why we have the llvm-project submodule; we needed to add a few C API functions to LLVM's ExecutionEngine to be able to use Miri's memory operations in place of LLI's.
We set the LLVM_SYS_160_PREFIX variable to llvm-project/build. This build is only used for Miri, and shouldn't be installed anywhere else.
I'm pretty new to using the llvm toolchain, so I'm entirely unsure if our build of LLVM could be conflicting with what librustc_driver expects. I'm attempting to recreate this issue on a different machine, and I'll follow up on the Zulip channel!

So to be clear, if you are trying to build unpatched Miri, that works or doesn't work? Note that Miri needs a nightly version of Rust. The recommendation is to use ./miri toolchain to set up the right version.
If you want to change LLVM, you'll have to build a custom rustc and then build Miri against that. Otherwise you'll likely end up with 2 copies of LLVM, one in rustc and one in Miri, and I can't imagine that going well.

https://github.com/icmccorm/miri/ does not exist any more, and I don't think there's anything actionable for us here.


Add meteor wallet to migration

Hi @roshaans - appreciate you taking the time to review our changes!
I've finished the relevant refactoring as requested.

One thing I noticed was that the chrome extension was not in sync with the website where I imported my accounts.

The sync between web wallet and extension is incoming. Our next step is to redirect to the extension for adding the accounts when our web wallet detects it. For the time being, web wallet users can still migrate their accounts so long (and soon, migrate from Meteor web wallet to extension as well).


connector 4.2.1 not working with encryption (regression)

After an upgrade to connector 4.2.1 it does not work any longer with oc encryption. I already filed this for an earlier version last year and @LinneyS made a quick fix then, but probably this code change was not included in later versions of the connector?
See https://github.com/ONLYOFFICE/DocumentServer/issues/899 and
https://central.owncloud.org/t/onlyoffice-integration-possible-regression-in-connector-for-master-encrypted-oc/23810 for reference
Tested on latest docserver with oc 10.4 and 10.5 RC2. Error msg on OC side:

"reqId":"Vnk6KEN7np69YX87IEzy","level":0,"time":"June 10, 2020 18:29:21","remoteAddr":"<IP_ADDRESS>","user":"admin","app":"OC\\User\\Session::validateToken","method":"PUT","url":"\/owncloud\/index.php\/apps\/onlyoffice\/ajax\/settings\/address","message":"token e1380aed2429d25e616a219ff3f1603a1b3326ab91bd04a816c2bda1a97c67ffa049d60eb90865dbab331ddcc66c80bc2c3d2434ffbf925bba31469d73e937bc with token id 106650 found, validating"}
{"reqId":"Vnk6KEN7np69YX87IEzy","level":0,"time":"June 10, 2020 18:29:21","remoteAddr":"<IP_ADDRESS>","user":"admin","app":"OC\\User\\Session::validateToken","method":"PUT","url":"\/owncloud\/index.php\/apps\/onlyoffice\/ajax\/settings\/address","message":"token e1380aed2429d25e616a219ff3f1603a1b3326ab91bd04a816c2bda1a97c67ffa049d60eb90865dbab331ddcc66c80bc2c3d2434ffbf925bba31469d73e937bc with token id 106650 found, validating"}
{"reqId":"Vnk6KEN7np69YX87IEzy","level":1,"time":"June 10, 2020 18:29:21","remoteAddr":"<IP_ADDRESS>","user":"admin","app":"onlyoffice","method":"PUT","url":"\/owncloud\/index.php\/apps\/onlyoffice\/ajax\/settings\/address","message":"Select demo: false"}
{"reqId":"Vnk6KEN7np69YX87IEzy","level":1,"time":"June 10, 2020 18:29:21","remoteAddr":"<IP_ADDRESS>","user":"admin","app":"onlyoffice","method":"PUT","url":"\/owncloud\/index.php\/apps\/onlyoffice\/ajax\/settings\/address","message":"SetDocumentServerUrl: https:\/\/docs.netzwissen.de\/"}
{"reqId":"Vnk6KEN7np69YX87IEzy","level":1,"time":"June 10, 2020 18:29:21","remoteAddr":"<IP_ADDRESS>","user":"admin","app":"onlyoffice","method":"PUT","url":"\/owncloud\/index.php\/apps\/onlyoffice\/ajax\/settings\/address","message":"SetDocumentServerInternalUrl: "}
{"reqId":"Vnk6KEN7np69YX87IEzy","level":1,"time":"June 10, 2020 18:29:21","remoteAddr":"<IP_ADDRESS>","user":"admin","app":"onlyoffice","method":"PUT","url":"\/owncloud\/index.php\/apps\/onlyoffice\/ajax\/settings\/address","message":"Set secret key"}
{"reqId":"Vnk6KEN7np69YX87IEzy","level":1,"time":"June 10, 2020 18:29:21","remoteAddr":"<IP_ADDRESS>","user":"admin","app":"onlyoffice","method":"PUT","url":"\/owncloud\/index.php\/apps\/onlyoffice\/ajax\/settings\/address","message":"SetStorageUrl: "}
{"reqId":"Vnk6KEN7np69YX87IEzy","level":3,"time":"June 10, 2020 18:29:21","remoteAddr":"<IP_ADDRESS>","user":"admin","app":"onlyoffice","method":"PUT","url":"\/owncloud\/index.php\/apps\/onlyoffice\/ajax\/settings\/address","message":"CommandRequest on check error: {\"Exception\":\"Exception\",\"Message\":\"Error occurred in the document service: Invalid token\",\"Code\":0,\"Trace\":\"#0 \\\/var\\\/www\\\/owncloud\\\/apps\\\/onlyoffice\\\/lib\\\/documentservice.php(305): OCA\\\\Onlyoffice\\\\DocumentService->ProcessCommandServResponceError(6)\\n#1 \\\/var\\\/www\\\/owncloud\\\/apps\\\/onlyoffice\\\/controller\\\/settingscontroller.php(283): OCA\\\\Onlyoffice\\\\DocumentService->CommandRequest('version')\\n#2 \\\/var\\\/www\\\/owncloud\\\/apps\\\/onlyoffice\\\/controller\\\/settingscontroller.php(168): OCA\\\\Onlyoffice\\\\Controller\\\\SettingsController->checkDocServiceUrl()\\n#3 \\\/var\\\/www\\\/owncloud\\\/lib\\\/private\\\/AppFramework\\\/Http\\\/Dispatcher.php(153): OCA\\\\Onlyoffice\\\\Controller\\\\SettingsController->SaveAddress('https:\\\/\\\/docs.ne...', '', '', 'WCXb2byYtBf8', false)\\n#4 \\\/var\\\/www\\\/owncloud\\\/lib\\\/private\\\/AppFramework\\\/Http\\\/Dispatcher.php(85): OC\\\\AppFramework\\\\Http\\\\Dispatcher->executeController(Object(OCA\\\\Onlyoffice\\\\Controller\\\\SettingsController), 'saveAddress')\\n#5 \\\/var\\\/www\\\/owncloud\\\/lib\\\/private\\\/AppFramework\\\/App.php(100): OC\\\\AppFramework\\\\Http\\\\Dispatcher->dispatch(Object(OCA\\\\Onlyoffice\\\\Controller\\\\SettingsController), 'saveAddress')\\n#6 \\\/var\\\/www\\\/owncloud\\\/lib\\\/private\\\/AppFramework\\\/Routing\\\/RouteActionHandler.php(47): OC\\\\AppFramework\\\\App::main('SettingsControl...', 'saveAddress', Object(OC\\\\AppFramework\\\\DependencyInjection\\\\DIContainer), Array)\\n#7 \\\/var\\\/www\\\/owncloud\\\/lib\\\/private\\\/Route\\\/Router.php(342): OC\\\\AppFramework\\\\Routing\\\\RouteActionHandler->__invoke(Array)\\n#8 \\\/var\\\/www\\\/owncloud\\\/lib\\\/base.php(916): OC\\\\Route\\\\Router->match('\\\/apps\\\/onlyoffic...')\\n#9 \\\/var\\\/www\\\/owncloud\\\/index.php(54): OC::handleRequest()\\n#10 {main}\",\"File\":\"\\\/var\\\/www\\\/owncloud\\\/apps\\\/onlyoffice\\\/lib\\\/documentservice.php\",\"Line\":338}"}

Hi @thommierother
I have installed ownCloud 10.4.0 (stable), ownCloud ONLYOFFICE integration app 4.2.1, ONLYOFFICE Document Server <IP_ADDRESS>
Created several files
Enabled encryption https://doc.owncloud.com/server/admin_manual/configuration/files/encryption/encryption_configuration.html#enabling-master-key-based-encryption-from-the-command-line
I can edit old encrypted files and create new files well.
And I have reviewed the changes between 4.2.1 and 4.1.3 and there are no open / save edits that could affect encryption.

Error occurred in the document service: Invalid token in your log says the JWT secret is wrong

ok, I'll have a look again, thanks for the re-check


chore: remove unused sync_wrapper

sync_wrapper crate seems not to be used.

Oh it's not used? It probably should be, so that reqwest::Body can allow !Sync streams.

I've tried reintroducing it doesn't look possible because of the functions taking shared references https://github.com/paolobarbolini/reqwest/tree/unsync-body

If you do end up reintroducing it, please update the dependency to 1.0.0 or later. This doesn’t involve any incompatible changes: the only change from 0.1.2 to 1.0.0 was replacing ’ with ' in the description in Cargo.toml.

This was used again.


unordered list is not rendering bullet points in description_html on database page

Thanks for this tremendous package, @simonw!
In the description_html for a database, I have an unordered list.
However, on the database page on the deployed site, it is not rendering this as a bulleted list.

Page here: https://labordata-warehouse.herokuapp.com/nlrb-9da4ae5
The documentation gives an example of using an unordered list in a description_html, so I expected this will work.

ordered lists didn't work either, btw


slickGoTo with infinite variableWidth images

I would like the slickGoTo image to appear to the left or the centre of the users' screen when multiple images of different widths are displayed. Is this at all possible? My current settings are:
        infinite: true,
        speed: 500,
        arrows: true,
        adaptiveHeight: true,
        draggable: true,
        variableWidth: true,
        slickGoTo: this.props.index

`

slickGoTo is now change to method instead of prop.
Check this example https://github.com/akiran/react-slick/blob/master/examples/SlickGoTo.js
open a new issue if you are still facing issues with slickGoTo


Caught error missing code and meta properties (they are undefined)

Bug description
I write a query like:
try {
  await [deleted, created] =  this.prisma.$transaction([
  this.prisma.users.deleteMany({ where: { username: "someUsername" } }),
  this.prisma.users.create({ where: { username: "notUniqueUsername" } })
])
} catch (error) {
  if (error.code === "P2002") throw new BadRequestException("Username isn't unique. Derp")
}

My expectation is for this to work and I know the error is a P2002 error because when I console.log(error) I see information akin to:
Error: Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: Some(KnownError { message: "Unique constraint failed on the fields: (`socialId`,`platform`)", meta: Object({"target": Array([String("socialId"), String("platform")])}), error_code: "P2002" }), kind: UniqueConstraintViolation { constraint: Fields(["socialId", "platform"]) } })
    at /Users/david/Code/project/packages/server2/node_modules/@prisma/client/runtime/index.js:27103:19
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  clientVersion: '2.17.0'
}

Ignore minor differences (socialId/platform versus username) as I was just giving an example earlier...
https://www.prisma.io/docs/reference/api-reference/error-reference
The documentation tells me to expect a error.meta and error.code and both are undefined when I console.log them.

How to reproduce
View above
Expected behavior
error.code and error.meta should behave as documented
Environment & setup

OS: Mac OS
Database: PostgreSQL
Node.js version: v12.10.0
Prisma version:

prisma               : 2.17.0
@prisma/client       : 2.17.0
Current platform     : darwin
Query Engine         : query-engine 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Studio               : 0.353.0

I updated the above to show that my issue actually happens when doing things with transactions.

For what it is worth, error.message exists and is
"ConnectorError(ConnectorError { user_facing_error: Some(KnownError { message: "Unique constraint failed on the fields: (`socialId`,`platform`)", meta: Object({"target": Array([String("socialId"), String("platform")])}), error_code: "P2002" }), kind: UniqueConstraintViolation { constraint: Fields(["socialId", "platform"]) } })"... but this is still broken and hella janky because I don't think it is realistic for me to have to do REGEX on this message to find the P2002 error.

Ryan on Slack confirmed it.

I think this is similar to https://github.com/prisma/prisma/issues/6156

@janpio I can confirm the 3 retry attempts on my end.

I can reproduce this, looks like only {"clientVersion":"2.20.0-dev.18"} is available in the error.
Ready to use reproduction:
import { PrismaClient } from "@prisma/client";

async function main() {
  const prisma = new PrismaClient();
  await prisma.user.create({
    data: {
      email: "nonunique",
    },
  });
  try {
    const [deleted, created] = await prisma.$transaction([
      prisma.user.deleteMany({
        where: {
          email: "test",
        },
      }),
      prisma.user.create({
        data: {
          email: "nonunique",
        },
      }),
    ]);
    console.log(deleted, created);
  } catch (error) {
    console.log(JSON.stringify(error));
    console.log(error.code);
    console.log(error.meta);
  }
  prisma.$disconnect();
}

main();

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Post {
  id        Int      @default(autoincrement()) @id
  createdAt DateTime @default(now())
  title     String
  content   String?
  published Boolean  @default(false)
  author    User     @relation(fields: [authorId], references: [id])
  authorId  Int
}

model Profile {
  id     Int     @default(autoincrement()) @id
  bio    String?
  user   User    @relation(fields: [userId], references: [id])
  userId Int     @unique
}

model User {
  id      Int      @default(autoincrement()) @id
  email   String   @unique
  name    String?
  posts   Post[]
  profile Profile?
}


Refs #26601 -- Used new-style middlewares in documentation.

Grrr, this CI server is definitely dumb!

@claudep Thanks :+1:


Compile error Hooked service

I'm getting a startup error as the attached error message:
/C:/Users/massi/AppData/Roaming/Pub/Cache/hosted/pub.dartlang.org/angel_framework-2.0.4+1/lib/src/core/hooked_service.dart:102:27: Error: The argument type 'List<FutureOr Function(HookedServiceEvent<dynamic, dynamic, Service<Null, Null>>)>' can't be assigned to the parameter type 'Iterable<FutureOr Function(HookedServiceEvent<Id, Data, T>)>'.

'List' is from 'dart:core'.
'FutureOr' is from 'dart:async'.
'HookedServiceEvent' is from 'package:angel_framework/src/core/hooked_service.dart' ('/C:/Users/massi/AppData/Roaming/Pub/Cache/hosted/pub.dartlang.org/angel_framework-2.0.4+1/lib/src/core/hooked_service.dart').
'Service' is from 'package:angel_framework/src/core/service.dart' ('/C:/Users/massi/AppData/Roaming/Pub/Cache/hosted/pub.dartlang.org/angel_framework-2.0.4+1/lib/src/core/service.dart').
'Iterable' is from 'dart:core'.
before.addAll(hooks.before);

/C:/Users/massi/AppData/Roaming/Pub/Cache/hosted/pub.dartlang.org/angel_framework-2.0.4+1/lib/src/core/hooked_service.dart:103:26: Error: The argument type 'List<FutureOr Function(HookedServiceEvent<dynamic, dynamic, Service<Null, Null>>)>' can't be assigned to the parameter type 'Iterable<FutureOr Function(HookedServiceEvent<Id, Data, T>)>'.

'List' is from 'dart:core'.
'FutureOr' is from 'dart:async'.
'HookedServiceEvent' is from 'package:angel_framework/src/core/hooked_service.dart' ('/C:/Users/massi/AppData/Roaming/Pub/Cache/hosted/pub.dartlang.org/angel_framework-2.0.4+1/lib/src/core/hooked_service.dart').
'Service' is from 'package:angel_framework/src/core/service.dart' ('/C:/Users/massi/AppData/Roaming/Pub/Cache/hosted/pub.dartlang.org/angel_framework-2.0.4+1/lib/src/core/service.dart').
'Iterable' is from 'dart:core'.
after.addAll(hooks.after);
^
/C:/Users/massi/AppData/Roaming/Pub/Cache/hosted/pub.dartlang.org/angel_framework-2.0.4+1/lib/src/core/hooked_service.dart:114:42: Error: The argument type 'List<FutureOr Function(HookedServiceEvent<dynamic, dynamic, Service<Null, Null>>)>' can't be assigned to the parameter type 'Iterable<FutureOr Function(HookedServiceEvent<Id, Data, T>)>'.
'List' is from 'dart:core'.
'FutureOr' is from 'dart:async'.
'HookedServiceEvent' is from 'package:angel_framework/src/core/hooked_service.dart' ('/C:/Users/massi/AppData/Roaming/Pub/Cache/hosted/pub.dartlang.org/angel_framework-2.0.4+1/lib/src/core/hooked_service.dart').
'Service' is from 'package:angel_framework/src/core/service.dart' ('/C:/Users/massi/AppData/Roaming/Pub/Cache/hosted/pub.dartlang.org/angel_framework-2.0.4+1/lib/src/core/service.dart').
'Iterable' is from 'dart:core'.
listeners.addAll(isAfter == true ? hooks.after : hooks.before);

I just repair cache and do an upgrade of flutter package and pub upgrade.
The application is a backend web server running in a VM.
The problem happen with DART SDK 2.7.0, 2.5.0 and 2.3.0 not happen.
I fould the flutter masterchannel introduce this error.
If you want to reproduce the error use flutter master channel and upgrade.
I switch back to dev channel and everything is working.

Not work with flutter channel master

What VM version?
On Tue, Nov 12, 2019 at 12:28 AM fleugzeug<EMAIL_ADDRESS>wrote:

Not work with flutter channel master
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/angel-dart/framework/issues/249?email_source=notifications&email_token=ACMIUPFJBF4POJWT5V7RQDTQTI5JTA5CNFSM4JJBTQZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDZCNPI#issuecomment-552740541,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMIUPC6U6ZZFOUTUECXTOLQTI5JTANCNFSM4JJBTQZQ
.

--
Tobe Osakwe
Student, B.S. Comp. Sci, Florida State University
https://thosakwe.com

I start with dart downloading flutter web framework, but never used flutter only dart.
On last update of master channel the DART version was 2.7.0 and I have the problem.
On current version (as flutter doctor):
[√] Flutter (Channel dev, v1.10.14, on Microsoft Windows [Versione 10.0.18362.449], locale it-IT)
• Flutter version 1.10.14 at k:\tools\flutter
• Framework revision 1946fc4da0 (5 weeks ago), 2019-10-07 15:23:31 -0700
• Engine revision 1d62160fdb
• Dart version 2.6.0 (build 2.6.0-dev.5.0 d6c6d12ebf)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at K:\tools\androidsdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = K:\tools\androidsdk
• Java binary at: K:\tools\android\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 3.5)
• Android Studio at K:\tools\android
• Flutter plugin version 40.2.2
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
[√] Connected device (2 available)
• Chrome          • chrome          • web-javascript • Google Chrome 78.0.3904.97
• Headless Server • headless-server • web-javascript • Flutter Tools
! Doctor found issues in 1 category.
Channel dev.
The VM version is: Dart VM version: 2.6.0-dev.5.0.flutter-d6c6d12ebf (Fri Oct 4 10:11:30 2019 +0000) on "windows_x64"
The not working version is (as flutter doctor):
[√] Flutter (Channel master, v1.10.17-pre.59, on Microsoft Windows [Versione 10.0.18362.449], locale it-IT)
• Flutter version 1.10.17-pre.59 at k:\tools\flutter
• Framework revision 9e0df259df (10 hours ago), 2019-11-11 15:56:43 -0800
• Engine revision 31cd2dfca2
• Dart version 2.7.0
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at K:\tools\androidsdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = K:\tools\androidsdk
• Java binary at: K:\tools\android\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[X] Visual Studio - develop for Windows
X Visual Studio not installed; this is necessary for Windows development.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including following components:
MSBuild
MSVC v142 - VS 2019 C++ x64/x86 build tools
- If there are multiple versions, install the latest one
Windows 10 SDK (10.0.17763.0)
[√] Android Studio (version 3.5)
• Android Studio at K:\tools\android
• Flutter plugin version 40.2.2
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
[√] Connected device (3 available)
• Windows    • Windows    • windows-x64    • Microsoft Windows [Versione 10.0.18362.449]
• Chrome     • chrome     • web-javascript • Google Chrome 78.0.3904.97
• Web Server • web-server • web-javascript • Flutter Tools
! Doctor found issues in 2 categories.
Dart VM version: Dart VM version: 2.7.0 (Fri Nov 8 21:32:48 2019 +0000) on "windows_x64"
On channel master of flutter.

I'm having the same issue once I upgrade to Dart 2.7. Anyone find a workaround for this?

I’m guessing it’s a type error that was ignored by the Dart VM prior to
2.6. I’ll be sure to put out a patch ASAP. The new version will be 2.0.4+1.
On Tue, Nov 19, 2019 at 6:59 AM Venkat Dinavahi<EMAIL_ADDRESS>wrote:

I'm having the same issue once I upgrade to Dart 2.7. Anyone find a
workaround for this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angel-dart/framework/issues/249?email_source=notifications&email_token=ACMIUPAMJJ7KJCQIBEPVV6DQUP5LVA5CNFSM4JJBTQZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEOPK7A#issuecomment-555545980,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMIUPBG27LPYK6PWW3DQA3QUP5LVANCNFSM4JJBTQZQ
.

--
Tobe Osakwe
Student, B.S. Comp. Sci, Florida State University
https://thosakwe.com

This is resolved in<EMAIL_ADDRESS>which I'm going to ship in a few minutes.

https://pub.dev/packages/angel_framework/versions/2.1.0

thanks a lot


Lexing individual lines incorrectly identifies keywords and ends inside of heredocs and comments

We cannot lex individual lines to know if they've got keywords because they may be in a heredoc:
irb(main):003:0> pp Ripper.lex("-f  --input_file           Use this file instead of stdin for preprocessed input;")
[[[1, 0], :on_op, "-", BEG],
 [[1, 1], :on_ident, "f", ARG],
 [[1, 2], :on_sp, "  ", ARG],
 [[1, 4], :on_op, "-", BEG],
 [[1, 5], :on_op, "-", BEG],
 [[1, 6], :on_ident, "input_file", ARG],
 [[1, 16], :on_sp, "           ", ARG],
 [[1, 27], :on_const, "Use", ARG],
 [[1, 30], :on_sp, " ", ARG],
 [[1, 31], :on_ident, "this", ARG],
 [[1, 35], :on_sp, " ", ARG],
 [[1, 36], :on_ident, "file", ARG],
 [[1, 40], :on_sp, " ", ARG],
 [[1, 41], :on_ident, "instead", ARG],
 [[1, 48], :on_sp, " ", ARG],
 [[1, 49], :on_ident, "of", ARG],
 [[1, 51], :on_sp, " ", ARG],
 [[1, 52], :on_ident, "stdin", ARG],
 [[1, 57], :on_sp, " ", ARG],
 [[1, 58], :on_kw, "for", BEG],
 [[1, 61], :on_sp, " ", BEG],
 [[1, 62], :on_ident, "preprocessed", CMDARG],
 [[1, 74], :on_sp, " ", CMDARG],
 [[1, 75], :on_ident, "input", ARG],
 [[1, 80], :on_semicolon, ";", BEG]]

But if you lex it with full context:
source = %Q{<<~EOM
  -f  --input_file           Use this file instead of stdin for preprocessed input;
EOM}

irb(main):008:0> pp Ripper.lex(source)
[[[1, 0], :on_heredoc_beg, "<<~EOM", BEG],
 [[1, 6], :on_nl, "\n", BEG],
 [[2, 0],
  :on_tstring_content,
  "-f  --input_file           Use this file instead of stdin for preprocessed input;\n",
  BEG],
 [[3, 0], :on_heredoc_end, "EOM", BEG]]

A better solution than lexing individual lines is to lex the whole document, and then "push" state back into the lines based on what is in the lex

This is only an issue if we're ever depending on this information. Currently, we're not.


Store transformed values in duckdb index file

Add the following columns:

{column_name}__hf_length - for lists and strings (all strings, both string-strings and class-strings)
{column_name}__hf_duration - for audios
{column_name}__hf_width and {column_name}__hf_height - for images

If we're going to recompute the duckdb files, I wonder if we could look again at the following possibility:

storing the indexes and additional columns into the .duckdb file,
while using the original parquet files to store the data

I don't know if it could work. If so, it could also make the requests slower or more complex. But it might reduce the cold-start latency of /filter and /search, as well as the local storage needs.

storing the indexes and additional columns into the .duckdb file,

I think that could be possible if we create the data table and then the index and finally remove the data table.
But should reduce disk usage in theory, but I have seen that duckdb has an interesting way ot managing "drops" actions.
See Limitations on Reclaiming Disk Space:

Running DROP TABLE should free the memory used by the table, but not always disk space. Even if disk space does not decrease, the free blocks will be marked as “free”. For example, if we have a 2 GB file and we drop a 1 GB table, the file might still be 2 GB, but it should have 1 GB of free blocks in it. To check this, use the following PRAGMA and check the number of free_blocks in the output:
PRAGMA database_size;

For that, I run a simple experiment and looks weird for me but expected by duckdb:
andrea@asoria:~/Documents/tools$ ./duckdb010/duckdb test.duckdb
v0.10.0 20b1486d11
Enter ".help" for usage hints.
D CREATE TABLE data AS FROM 'https://huggingface.co/datasets/allenai/c4/resolve/refs%2Fconvert%2Fparquet/en/partial-validation/0001.parquet';
 99% ▕███████████████████████████████████████████████████████████▍▏
100% ▕████████████████████████████████████████████████████████████▏
D
D select count(*) from data;
┌──────────────┐
│ count_star() │
│    int64     │
├──────────────┤
│       141509 │
└──────────────┘
D PRAGMA database_size;
┌───────────────┬───────────────┬────────────┬──────────────┬─────────────┬─────────────┬──────────┬──────────────┬──────────────┐
│ database_name │ database_size │ block_size │ total_blocks │ used_blocks │ free_blocks │ wal_size │ memory_usage │ memory_limit │
│    varchar    │    varchar    │   int64    │    int64     │    int64    │    int64    │ varchar  │   varchar    │   varchar    │
├───────────────┼───────────────┼────────────┼──────────────┼─────────────┼─────────────┼──────────┼──────────────┼──────────────┤
│ test          │ 363.2 MiB     │     262144 │         1453 │        1453 │           0 │ 0 bytes  │ 363.2 MiB    │ 12.3 GiB     │
└───────────────┴───────────────┴────────────┴──────────────┴─────────────┴─────────────┴──────────┴──────────────┴──────────────┘
D .exit
andrea@asoria:~/Documents/tools$ ls -la
total 744052
...
-rw-rw-r--  1 andrea andrea 380907520 abr 19 11:23 test.duckdb
andrea@asoria:~/Documents/tools$ ./duckdb010/duckdb test.duckdb
v0.10.0 20b1486d11
Enter ".help" for usage hints.
D drop table data;
D PRAGMA database_size;
┌───────────────┬───────────────┬────────────┬──────────────┬─────────────┬─────────────┬──────────┬──────────────┬──────────────┐
│ database_name │ database_size │ block_size │ total_blocks │ used_blocks │ free_blocks │ wal_size │ memory_usage │ memory_limit │
│    varchar    │    varchar    │   int64    │    int64     │    int64    │    int64    │ varchar  │   varchar    │   varchar    │
├───────────────┼───────────────┼────────────┼──────────────┼─────────────┼─────────────┼──────────┼──────────────┼──────────────┤
│ test          │ 363.2 MiB     │     262144 │         1453 │        1453 │           0 │ 64 bytes │ 256.0 KiB    │ 12.3 GiB     │
└───────────────┴───────────────┴────────────┴──────────────┴─────────────┴─────────────┴──────────┴──────────────┴──────────────┘
D .exit
andrea@asoria:~/Documents/tools$ ls -la
total 744052
...
-rw-rw-r--  1 andrea andrea 380907520 abr 19 11:24 test.duckdb
andrea@asoria:~/Documents/tools$ ./duckdb010/duckdb test.duckdb
v0.10.0 20b1486d11
Enter ".help" for usage hints.
D PRAGMA database_size;
┌───────────────┬───────────────┬────────────┬──────────────┬─────────────┬─────────────┬──────────┬──────────────┬──────────────┐
│ database_name │ database_size │ block_size │ total_blocks │ used_blocks │ free_blocks │ wal_size │ memory_usage │ memory_limit │
│    varchar    │    varchar    │   int64    │    int64     │    int64    │    int64    │ varchar  │   varchar    │   varchar    │
├───────────────┼───────────────┼────────────┼──────────────┼─────────────┼─────────────┼──────────┼──────────────┼──────────────┤
│ test          │ 363.2 MiB     │     262144 │         1453 │           1 │        1452 │ 0 bytes  │ 256.0 KiB    │ 12.3 GiB     │
└───────────────┴───────────────┴────────────┴──────────────┴─────────────┴─────────────┴──────────┴──────────────┴──────────────┘
D .exit
andrea@asoria:~/Documents/tools$ la -la
total 744052
...
-rw-rw-r--  1 andrea andrea 380907520 abr 19 11:24 test.duckdb

See that:

First, file size was 363Mib (After table creation)
After the drop, the size remains the same (I would have expected it to reduce)
What changed in duckdb was the free_blocks, as mentioned in the docs.

So, I am not sure if this can help us :/

Should be ready for review now @huggingface/dataset-viewer
@severo regarding storing index+transformed values and data separately - it probably would be possible to avoid problem that @AndreaFrancis described above by creating new connection  and new database and copy only what's needed there (I'm not sure, haven't tested yet). But anyway I don't completely understand how it would make search/filter more efficient since we will have to download parquet files with data too anyway, no? I only see that download could be performed in parallel in this case.

Should we name the columns like {column_name}.length ? It would feel more natural later when running queries in duckdb sql on the hub.
And in case of collision we can ignore I guess

while using the original parquet files to store the data

it would make things too slow or complicated imo, especially in downstream usage of the duckdb files from users

especially in downstream usage of the duckdb files from users

I agree, if we ever want to advertise using duckdb.index file, it wouldn't be useful without data

Yes, it was an open question. The benefit would have been to reduce the size of the file we have to download. But no worry if it's not feasible or too complex.

@AndreaFrancis thank you for pointing out to this issue with loading all columns, hopefully it's fixed now

And in case of collision we can ignore I guess

@lhoestq I realized it might cause problems at the stage of filtering. Let's say a dataset itself contains string column text and text.length but text.length is not an integer column corresponding to lengths of texts but something different, it might be even of different dtype. For example, string or class label with values "long" and "short". But when we filter, we assume that {column_name}.length contains integers corresponding to lengths.
I don't know if examples like this exist though lol

okay i checked text, audio and image datasets and found one example with column names collision. i didn't check lists but i guess we are fine anyway :D

I haven't thought before - maybe we should also update duckdb version since we are recomputing everything? But I don't know if it's needed.

Not needed for now IMO

sorry, one more thing i forgot :see_no_evil: shouldn't i update the job runner's version?

it would recompute all the stats. I think it's what we want, right?


Python API and REST API - Delete Experiment - no test for validate: is user owner

On delete experiment, REST API, there is a validation to check that the use is the owner of the experiment: only the owner of a experiment can delete that experiment. This has been coded up. However, it has not been tested. A test need to be written:

User A creates a project with an experiment and
gives user B access to that project; then
user B tries to delete the experiment (and fails); then
user A deletes the experiment (with success).
It is easiest to write this test in Python (assuming that user A and user B exist).

This can easily be written as extension of the delete project test (see issue #1028)

Fixed while fixing issue #1028


ModuleNotFoundError: No module named 'utils.transforms'

When I enter this command :
python demo/vis.py --video sample_video.mp4
I will get the error like this :
Traceback (most recent call last):
File "demo/vis.py", line 5, in
from lib.hrnet.gen_kpts import gen_video_kpts as hrnet_pose
File "/home/dvlab/PoseFormerV2-main/demo/lib/hrnet/gen_kpts.py", line 21, in
from lib.hrnet.lib.utils.inference import get_final_preds
File "/home/dvlab/PoseFormerV2-main/demo/lib/hrnet/lib/utils/inference.py", line 17, in
from utils.transforms import transform_preds
ModuleNotFoundError: No module named 'utils.transforms'
however, i download the whole file on the github. Also, I check if my document is missed, but everything is good
please tell me how to solve this problem
thanks

Can you try the latest code? I did not encounter this issue.

it works, thanks a lot


less CRLF error

if i change to LF, error not found
/usr/local/bin/csscomb /Users/DragorWW/projects/us/csscomb/styles/elements.less
stack:  /Users/DragorWW/projects/us/csscomb/styles/elements.less
Please check the validity of the block starting from line #39

38 | .hide {
39*|     display: none !important;
40 | }
41 | .block {

Gonzales PE version: 3.0.0-28
Syntax: less
CSScomb Core version: 3.0.0-3.1

Process finished with exit code 1

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

This no longer seems to be a problem with the latest csscomb release :tada:


module: "system" and outFile generates wrong module names

TypeScript Version: 2.4.0-dev.20170519
Code
this Typescript code (on the main project)
'use strict'

import { createStore, applyMiddleware, combineReducers } from 'redux'
import { routerReducer, LOCATION_CHANGE } from 'react-router-redux'
import { handleActions, Action } from 'redux-actions'
import { Login, Data, Groups } from 'cim-typings'
import { Initials } from 'cim-shared-ui/helpers'
import * as RActions from './actions'

generates
System.register("reducers", ["redux", "react-router-redux", "redux-actions", "../../cim-shared-ui/helpers", "actions"], function (exports_2, context_2) {
/* ... */
})

which is wrong. "../../cim-shared-ui" should be "cim-shared-ui", because it's a npm linked package. not sure if the problem is the link itself, because I have this, and works correctly, which is also from the main project:
'use strict'

import React from 'react'
import { Data } from 'cim-typings'

System.register("components/status", ["react", "cim-typings"], function (exports_5, context_5) {
/* ... */
})

tsconfig.json as follows:
{
  "exclude": [
    "./node_modules",
    "./jspm_packages",
    "./dist"
  ],
  "include": [
    "./generic.d.ts",
    "src/*.ts",
    "src/*.tsx",
    "src/**/*.tsx",
    "src/**/*.ts"
  ],
  "compilerOptions": {
    "module": "system",
    "jsx": "react",
    "target": "es5",
    "moduleResolution": "node",
    "allowSyntheticDefaultImports": true,
    "rootDir": "src",
    "newLine": "LF",
    "allowJs": false,
    "noImplicitAny": true,
    "baseUrl": "./",
    "noEmitOnError": true,
    "sourceMap": true,
    "alwaysStrict": true,
    "inlineSourceMap": false,
    "paths": {
      "*": [
        "node_modules/@types/*",
        "*"
      ]
    },
    "lib": [
      "dom",
      "es2015",
      "es5"
    ],
    "outFile": "dist/app.js"
  }
}

Expected behavior:
module: "system" should output dependencies as authored
Actual behavior:
TS is trying to do something funny with the paths, and it's inconsistent with other npm linked packages. The only difference between the two is that cim-typings is a commonjs module, and cim-shared-ui is a system module

I first thought it was a problem with JSPM jspm/jspm-cli#2275 but it's really a mix of outFile and module "system" from Typescript

Does cim-typings declare the typings for the module cim-shared-ui?

no, it's unrelated from each other

The reason I ask is that the name cim-typings implies that the package contains nothing but types. If that is the case, then it doesn't serve as reference for the expected behavior of cim-shared-ui because all imports will be elided from the output code anyway.

it has .js files, like I said, it has exported consts objects like such:
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.MaritalStatusTypes = {
    casado: 'Casado',
    divorciado: 'Divorciado',
    separado: 'Separado',
    solteiro: 'Solteiro',
    viuvo: 'Viúvo'
};
exports.PhoneTypes = {
    fixo: 'Fixo',
    celular: 'Celular'
};

I see, I was just put off by the name the package.
Also, I tried to reproduce but I couldn't.

looks somewhat like #15876
I'll try to make a minimal repro

I just looked over this again and I think it is a bug in TypeScript because module specifiers are never supposed to be rewritten. Having said that, I couldn't reproduce the bug.

is there at least any workaround for this? the side-by-side .d.ts generation really mess this up

still happening in 2.5.0-dev


Error message is not translated to Spanish on sign in page, but it is translated to spanish on the contact methods page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Change language preference to 'Spanish'
Click on 'Profile' avatar > click on 'Profile' > click on 'contact methods'
Click on 'New contact method' > enter email address  & click on 'Add' button
Open the newly added contact method
Enter a wrong magic code & and observe that the error message is in Spanish
Sign out
Scroll to the bottom & and change the language preference to Spanish
Enter email & click on 'Continue' button
Enter a wrong magic code

Expected Result:
Error message is not translated to Spanish as contact methods section
Actual Result:
Error message should be consistently translated to Spanish on Sign in page too.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.63-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/38435837/3fb21a57-899f-4afe-8fe5-014bc9b57db2
https://github.com/Expensify/App/assets/38435837/925bae12-707e-4949-bfb5-246ad952b453
Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693292456452099
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
Error message is not translated to Spanish on sign in page, but it is translated to spanish on the contact methods page
What is the root cause of that problem?
https://github.com/Expensify/App/blob/cbda2b03824d9b125ec6ab19e87ff533bea1b22f/src/pages/signin/ValidateCodeForm/BaseValidateCodeForm.js#L206C31-L206C48
As you can see the code, error message isn't translated. This is the root cause of the problem.
What changes do you think we should make in order to solve the problem?
We should translate the error message.
const {translate} = useLocalize();

// other code

setFormError({validateCode: translate('validateCodeForm.error.pleaseFillMagicCode')});

This is Backend issue, backend should return a translation key for error, not ful error message.

Thanks @ishpaul777 !
Closing.


Organization invitations system

UPDATE: See comments below

The data model root is namespaced (soft multi-tenancy) by an organization entity. Users are connected to different organizations through memberships.

At user registration time, an organization and its membership will be created.
That's the extent of our current membership handling. It has the following limitations:

No other users can be added to the same organization (unless a DB entry is manually added)
memberships can not be deleted, meaning a user can't leave an organization.

This task is about to be able to add users, existing or not, to be added to an existing organization.
Invitation system context
This could be performed via an invitation system, and it should contain

[user 1] being able to create an invitation to org1 for<EMAIL_ADDRESS>
this invitation should be time-limited and exclusive to the given org and user

[user 2] should be able to accept/decline the invitation
[user 1] should be able to revoke the invite

Invitation system implementation first cut
User 1
Create invitation
chainloop org invite create --org deadbeef --user<EMAIL_ADDRESS>=> invitation created with code "XC-A0-12-BT" valid for 1 week

You can list the invitations
chainloop org invite ls

or revoke it
chainloop org invite revoke --code XC-A0-12-BT

chainloop org invite create --org deadbeef --user<EMAIL_ADDRESS>user 2
Join an org
chainloop org invite accept --code XC-A0-12-BT

or reject the invite
chainloop org invite reject --code XC-A0-12-BT

Refs https://github.com/chainloop-dev/chainloop/issues/350

The implementation shown in the task has changed in the end #404

We do not generate invitation codes
Explicit Acceptance/Decline of invites are not required. For now users invited will automatically join an org on login.

So, long story short

Senders can create, revoke, and list sent invitations.
Receivers, on login, will get added to their invited organization automatically.


Grpc from proto

Description
Grpc client create directly protos files. Reference here: https://docs.microsoft.com/tr-tr/aspnet/core/grpc/basics?view=aspnetcore-3.0
And maybe create Protos files repo reference all projects single protos repo.
https://github.com/dapr/dotnet-sdk/issues/92#issuecomment-541764993
Issue reference
#92
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

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

@mehmetuken I have reopened this PR. Are you still working on it, Can we prepare this for merging?

@amanbha i can't see reopening. I change assets to private and bump Google.Protobuf, and i think is done.

Thanks for the contribution @mehmetuken .


feat: determine rssi of messages from node

Hi @Johboh.
This PR is not for merging, its for provoking a discussion about determining the RSSI of messages received from a node.  Knowing the RSSI makes it easier to tell if the signal is weak, or if it has changed (e.g. maybe because of bad weather, a new obstruction, etc).  So it would be great if this value could be derived and made available to the host application.
The ESP-NOW API doesn't make the RSSI available, but it can be obtained by enabling promiscuous mode so that the host receives all WiFi frames regardless of the destination MAC.  When a WiFi frame is received and passed to the promiscuous mode callback, the RSSI is available there.  This callback is called before the normal ESP-NOW handling, so it means that the RSSI can be cached along with the MAC address its associated with, so that when the normal ESP-NOW handling of the message executes the RSSI can be retrieved from the cache.
Its not very elegant, but it works.
The caching implementation in this PR is not very elegant either, but it also works.  The intention was to use something that was simple, with static allocation, so a ring buffer came to mind (copied from https://github.com/Locoduino/RingBuffer with the Arduino.h dependency removed).  But don't focus on that (there will be better approaches for the caching) - have a look at how the RSSI is obtained.  Do you think this is worth it to get the RSSI?

As a "reverse" solution, what do you think if instead the nodes reported their RSSI as part of the challenge request? In the same way they include their firmware version in the challenge request: https://github.com/Johboh/EspNowNetwork/blob/main/src/impl/EspNowNode.cpp#L226

Given that RSSI means "received signal strength indicator", if the node reported an RSSI value to the host, it would be reporting how well the node can "hear" the host.  That's worth knowing too, since the communication between the host and node is bidirectional.
So the node could report an RSSI value, but I think the host should also determine the RSSI for messages received from the node.

Oops, fumbled phone and hit the close button by mistake.

Given that RSSI means "received signal strength indicator", if the node reported an RSSI value to the host, it would be reporting how well the node can "hear" the host. That's worth knowing too, since the communication between the host and node is bidirectional.
So the node could report an RSSI value, but I think the host should also determine the RSSI for messages received from the node.

Right, OK, measuring RSSI on host side is probably preferable then. I think its valuable to have this information host side, but I think it could be in a separate (optional) class, e.g. something like EspNowRssi, that one can use if one wants to know RSSI for the nodes. As in, the EspNowRssi will collect and store the RSSI for mac addresses, and then users can call getRssiForMac() when needed. That is, no changes to the EspNowHost API or implementation. So in the host.ino example, it will be somthing like: Serial.println("Got message from 0x" + String(metadata.mac_address) + " with ID " + id + " rssi=" + esp_now_rssi.getRssiForMac(metadata.mac_address));
And instead of a ringbuffer, I think you could use a std::deque instead: https://en.cppreference.com/w/cpp/container/deque


Repalced the IIS with the Apache server in the Windows AdminRouter im…

…plementation

The changes in this PR are clean after rebasing my commit on top of the newly merged in https://github.com/dcos/dcos-windows/pull/36
Note: to avoid deployment failure, this PR cannot be merged before the following one was merged into mesos-jenkins repro
https://github.com/Microsoft/mesos-jenkins/pull/57


Convert to a "Halite style" cookbook.

@coderanger has recently pushed out the poise-service library cookbook which is a Halite style cookbook. I wanted to reach out to you first to figure out if you'd accept a patch to do so with the Chef Sugar cookbook instead of maintaining an internal fork of the cookbook.
My main motivation here is we would no longer need to distribute Chef Sugar as a gem. This proves problematic for those of us that are in an enterprise setting. Even though cookbook updates can happen out of band we're still using the chef_gem LWRP to include it.
My proposed changes are quite straightforward and simple:

Add the Halite extension to Berksfile.
Modify the default recipe to simply require 'chef/sugar'.
Modify the Gem specification to add Halite as a dependency

You can see examples:

Poise cookbook
Poise Service cookbook

Hi @johnbellone
Until Halite gets more traction and adoption in the Chef community, I will not be merging support for it. Chef sugar is dep-minimal and I prefer to keep it that way. Sorry! :smile:


Bump rand

Upgrade rand to 0.6, changing only the use of some APIs in tests.
Pin lazy_static to <1.2, as newer versions break compilation with rustc 1.22.1.

If you like, you can update the note about the minimum Rust version in the README as well. The use_arc_str (actually due to be removed in 0.16, we'll just use Arc<str> everywhere) and nickel features are only tested on stable.


Basic privacy dialog

[x] Password-protected only supported for maps
[x] Visually to look like in the screenshot for a normal user
[x] Possibility to change Visualization privacy (dataset/map).
[x] Possible to set password if selected password option (see #1873 for details)
[x] Show upgrade banner for users that have any disabled options
[x] Possibility to change permissions (organization environment)
[x] Show privacy options depending of the account (take into account upgrade links and open source)

solved in #1909


[Screen Readers - Power Toys - Color Picker]: An element's IsOffScreen property must be false when its clickable point is on screen.

Microsoft PowerToys version
0.41.3
Running as admin

[ ] Yes

Area(s) with issue?
ColorPicker
Steps to reproduce
Test Environment:
OS: Windows 10 Version Dev
App version: 0.41.3
App name: PowerToys
Screen Reader: Narrator
Tool: Accessibility Insight for Windows
Repro Steps:

Launch Accessibility Insights for Windows tool.
Open Power Toys Settings App.
Navigate to "Color picker" list item and activate it.
Now Press shortcut key which appears on "Activate Color Picker" edit field and Choose any color.
Run Accessibility Insights for Windows tool.
Observe the issue.

User Impact -> Priority 2
If the object role, state(s), properties, boundary, name, and description are not programmatically determinable, it would be difficult for the platforms that provide Accessibility APIs, and would in turn affect the screen reader dependent users to determine the object properties.
WCAG Reference:
https://www.w3.org/TR/WCAG21/#name-role-value

✔ Expected Behavior
An element's IsOffScreen property must be false when its clickable point is on screen.
❌ Actual Behavior
An element's IsOffScreen property must not be True when its clickable point is on screen.
Other Software
No response

@v-amanpra The ListViewItem is actually off screen.. (the first time that can only be seen when scrolling the listview). So it this considered a bug?
Related: https://github.com/microsoft/axe-windows/issues/387

Closing this issue as no longer repro.


SAK-29182 new account tool should respect invalidEmailInIdAccountString sakai.property

https://jira.sakaiproject.org/browse/SAK-29182
The existing sakai.property invalidEmailInIdAccountString defines a list of domain names that are not allowed in guest accounts, which is useful for preventing accidental creation of guest accounts for users (based on email address) that already have an external account (based on user name).
When the New Account tool has the tool property force-eid-equals-email set to true (introduced in SAK-28184), the tool is essentially doing exactly what the sakai.property descibes, and as such it should respect the property if it's set.
This introduces a new sakai.property (user.email.invalid.domain.message) to provide a customizable, paramaterized error message which is presented to the user when in the event that they attempt to use an email address with one of the offending domains. This sakai.property can utilize the following two parameters as often as necessary, and in any order. "{0}" will be replaced with the contents of the sakai.property "ui.institution". "{1}" will be replaced with the offending email domain string.

Forgot to update default.sakai.properties... updating.


Please provide Japanese documentation for the official wiki

I work with a number of Japanese customers. It is difficult to introduce the high level concepts or the details technical aspects without some of this documentation being written in Japanese.  For example, this page would be a prime candidate for a translation by a human:
http://docs.ens.domains/en/latest/
so that this:
http://docs.ens.domains/jp/latest/
doesn't show this:
        \          SORRY            /
         \                         /
          \    This page does     /
           ]   not exist yet.    [    ,'|
           ]                     [   /  |
           ]___               ___[ ,'   |
           ]  ]\             /[  [ |:   |
           ]  ] \           / [  [ |:   |
           ]  ]  ]         [  [  [ |:   |
           ]  ]  ]__     __[  [  [ |:   |
           ]  ]  ] ]\ _ /[ [  [  [ |:   |
           ]  ]  ] ] (#) [ [  [  [ :===='
           ]  ]  ]_].nHn.[_[  [  [
           ]  ]  ]  HHHHH. [  [  [
           ]  ] /   `HH("N  \ [  [
           ]__]/     HHH  "  \[__[
           ]         NNN         [
           ]         N/"         [
           ]         N H         [
          /          N            \
         /           q,            \
        /                           \

You should point them to https://ethereum-japan.net/wiki/ens
I can read and write Japanese but not sure it's worth translating only for the Japanese audience.


Use env["PATH_INFO"] instead of env["REQUEST_PATH"]

env["REQUEST_PATH"] isn't covered by the rack spec, and thus not necessarily passed to the application by some web servers. This fixes issue #1.

Awesome! Sorry about that. I tested with Rails and Sinatra only and they both set REQUEST_PATH :/ Let me update the gem too.

Fetching: rack-superfeedr-0.0.3.gem (100%)
Successfully installed rack-superfeedr-0.0.3
1 gem installed
Installing ri documentation for rack-superfeedr-0.0.3...
Installing RDoc documentation for rack-superfeedr-0.0.3...```