Request for adding one dataset paper

Dear Repo Owner,
Thank you for maintaining this nice repo of LLM for Recommendation. We have recently released a session-recommendation dataset named Amazon-M2 for evaluating LLMs in recommendation scenarios. It provides both a dataset, a benchmark, and three text-related tasks. Would you mind adding this work to your repo?
Thank you for your attention.

Hi,
Big thanks for your request to remind us about this awesome dataset and benchmark. We have added it to our repo.
Please feel free to send us more information or other related resources if needed.
Best Regards.

Thank you!


RN 0.64 FBReactNativeSpec - Syntax Error: Invalid regular expression

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
I'm upgrading to RN 0.64.0 (by following the upgrade helper). When building my iOS app via Xcode, I get the following error from FBReactNativeSpec:
>>>>> Generating schema from flow types

/Users/<user>/<project>/node_modules/react-native-codegen/lib/parsers/flow/index.js:220
    const regex = new RegExp(TURBO_MODULE_REGISTRY_REQUIRE_REGEX_STRING, 'g');
                  ^

SyntaxError: Invalid regular expression: /TurboModuleRegistry\s*\.\s*get(Enforcing)?\s*<\s*Spec\s*>\s*\(\s*['"](?<nativeModuleName>[A-Za-z$_0-9]+)['"]\s*,?\s*\)/: Invalid group
    at new RegExp (<anonymous>)
    at buildSchema (/Users/<user>/<project>/node_modules/react-native-codegen/lib/parsers/flow/index.js:220:19)
    at Object.parseFile (/Users/<user>/<project>/node_modules/react-native-codegen/lib/parsers/flow/index.js:276:10)
    at files.reduce (/Users/<user>/<project>/node_modules/react-native-codegen/lib/cli/combine/combine-js-to-schema.js:75:35)
    at Array.reduce (<anonymous>)
    at combineSchemas (/Users/<user>/<project>/node_modules/react-native-codegen/lib/cli/combine/combine-js-to-schema.js:66:16)
    at Object.<anonymous> (/Users/<user>/<project>/node_modules/react-native-codegen/lib/cli/combine/combine-js-to-schema-cli.js:90:40)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
Command PhaseScriptExecution failed with a nonzero exit code

React Native version:
System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 460.01 MB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.20.1 - ~/.nvm/versions/node/v12.20.1/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v12.20.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK:
      API Levels: 28, 29, 30
      Build Tools: 28.0.3, 29.0.2, 30.0.3
      System Images: android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>42882
    Xcode: 12.4/12D4e - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_281 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found (installed globally)
    react: ^17.0.1 => 17.0.1
    react-native: 0.64.0 => 0.64.0
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Follow upgrade helper tool for RN 0.64.0
yarn install
pod install
Build iOS (Xcode and react-native run-ios give the same error)

Expected Results
Build to succeed
Snack, code example, screenshot, or link to a repository:
Error described above.
Another user created a similar issue in the rn-cli repo: https://github.com/react-native-community/cli/issues/1378

I got the same error here.
This is an dependency error on<EMAIL_ADDRESS> I've updated react-native-codegen to version 0.0.7 and the error goes away.
I use yarn so I put it on resolver attribute inside package.json.

@igormontella Thank you! This fixed it!

from my side, the problem was a space in the project path. Interesting that previous version wasn't be under this issue

I'm also running into this issue. I'm using npm not yarn. Any recommendations for updating<EMAIL_ADDRESS>dependency of react-native-codegen to version 0.0.7 with npm?

@igormontella How can I change the react-native-codegen version?

Run: "yarn add --dev react-native-codegen" and rebuild IOS project

Thanks for the react-native-codegen tip, saved my sanity


Define a solution for organization members to push new version(s) of projects

Currently
As per indication at the moment all the RxSwiftCommunity repositories  doesn't have a shared access where contributors could easy make updates and deploy the approved updates when ready.
Required
Discuss and find a solution to this problem where contributors could update and deploy on all fronts without contacting the original creator of the repository.

 I'm pretty busy this week but will try to chime in when I can. If there're specifics I can answer, please @ me.

I will be handling  RxCoreDatauntil we find a solution in here. for the whole community.

I came up with a great solution for the deployment issue we've been battling. Closing this issue in favor of a new one where I'll describe the solution and gather some feedback before starting with a pilot (on RxAlamofire, probably)


AMBARI-23895 Configuration Validation is throwing errors on correct configuration

How was this patch tested?
21537 passing (33s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2362/
Test PASSed.


use countAPI instead

Use countAPI as counter persistance plan instead of postgreSQL database to make it more independent and also avoid heroku's free plan limitation of database, only allows 10000 lines.

failed, because the domain https://api.countapi.xyz is not in the whitelist of pythonanywhere

see https://www.pythonanywhere.com/whitelist/


The global variable looks gray, as if it is not being used(but it is)

Issue Type: Bug
The global variable currentSlide looks gray, as if it is not being used. If I move it to the global scope, the variable declaration stops being gray.  And if I move it back again, everything is still ok.

When I delete this variable from local scope - the global variable looks like it's still been used.

I have autosave option being swiched on
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:34:46.910Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3 CPU       M 330  @ 2.13GHz (4 x 2128)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: unavailable_offskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: unavailable_off

Load (avg)
undefined

Memory (System)
3.86GB (1.34GB free)

Process Argv
D:\Курс JavaScriptDOMИнтерфейсы для новичков\jsbasic-20201022_ellan --crash-reporter-id 3271867f-5249-444b-84ff-f4d63580ccb5

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.14

vscode-firefox-debug
fir
2.9.1

auto-close-tag
for
0.5.10

debugger-for-chrome
msj
4.12.12

elmmet
nec
1.0.1

LiveServer
rit
5.6.1

markdown-preview-enhanced
shd
0.5.16

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
openlogontheside:30221877
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30211402
wsl2promptcf:30224613
pythonvsdeb440:30248342
unusedpromptcf:30224611
folderexplorercf:30224615
openfilemenu:30224647
pythonvsded773:30248341
vstes627:30244334
pythonvspyt600cf:30251589

The value is faded out because it is never read. In the first example you only declare and increment it. In the second, totalShift is also never used for anything after its declaration

@mjbvz Thank you very much for the reply.


Fix for screen readers (NVDA in particular) which do not detect webview "soft" refresh / new DOM in iframe (must be "hard" webview load-from-scratch, including inner links / intra document navigation)

Related r2-navigator-js code change: readium/r2-navigator-js@32e8361

Successfully tested on Windows 10 Pro (latest):

hardware device (laptop) with touch screen (this is important, as this has been known to trigger the accessibility tree in Electron/Chromium)
software emulation (VirtualBox) => NVDA is very choppy in this configuration, lots of silent pauses

Note that hyperlinking from the TOC (right-hand-side vertical slide-out menu) and with the keyboard shortcuts for spine-level navigation (CTRL+SHIFT LEFT/RIGHT (also ALT if not MacOS)) automatically brings focus to the "main" content area which wraps the EPUB HTML document webview. This means that screen readers can directly dive into the publication content when hyperlinking, with one step ahead (arrow keys, depending on VoiceOver vs. NVDA, etc.)

Hi Daniel, three minor, additional notes from our testers. Happy to file more accurately if this Issue isn't the right thread:
Text does not advance. The program says it has two settings for content, scrollable and paging.  I’d expect with scrollable, the text would automatically advance as I read but it doesn’t with any of the three screen reader’s I tried (JAWS, NVDA and Narrator). What I assume are buttons for paging, named left and right, didn’t change the text with any of the screen readers. [My interpretation of this is that the screen reader is reading text below of the visible text in the window, however the text displayed on the screen does not advance with the screen reader - Matt]
Narrator – When you load a book and turn on Narrator’s scan mode, it starts reading fine.  But if you hit ctrl+end to jump to the bottom of the text and start pressing up arrow, you get no speech from Narrator and the app behaves like it is hung. (only tested Narrator)
Announcements that a new book is imported by eKitabu are not announced in JAWS (only tested JAWS)

Thanks Matt!
Let's break this down into distinct actionable issues.
(I'll report back here in a few minutes)

First issue: https://github.com/readium/readium-desktop/issues/761

Second issue: https://github.com/readium/readium-desktop/issues/762

Third and final issue: https://github.com/readium/readium-desktop/issues/763


Make sure finished projects render on certs / timeline?

Nice to have:

[ ] A user can open previews in full-screen in a new tab.

For this, did we decide on:

When the preview is open, the code is visible?
The preview lives in a unique URL to be linked to directly?

We've not got that far on the ui design, but options are:

separate buttons to show preview and source
separate tabs for preview and source

I'm leaning towards separate buttons, as I think that'll be less cluttered.
As for the Nice To Have, there would need to be a URL that fetches the preview. It could just be handled via query params, rather than unique paths, though.

I think I would go with two buttons, one for the code and another for the preview. Both open a modal on the page, and they would probably need to work anywhere else we show solutions - the cert itself, the timeline, and the settings page.
I guess if you can make a URL that opens the preview in a new tab, that would be preferable. I assume that would be more difficult, but I'm not sure.

I would prefer:

A Camper can link to a unique URL (url with query params. e.g. freecodecamp.org/certification/sky020/responsive-web-design?view=full)
The full view opens in a new tab (always?)
The editor view opens in the current editor? Or, a completely new view showing uneditable code and preview?

Since this just intended to showcase work, I think there should just be a code view, not an editor view.  Prism highlighted text should do the job.
Putting in a real editor, even a read-only one, seems like overkill.


chore(deps): update all non-major dependencies

This PR contains the following updates:

Package
Type
Update
Change

@hywax/tools-eslint
devDependencies
patch
^1.0.0 -> ^1.1.0

@nuxtjs/i18n (source)
dependencies
minor
9.0.0-rc.2 -> 9.1.0

pnpm (source)
packageManager
patch
9.14.2 -> 9.14.4

unimport
pnpm.overrides
minor
3.13.4 -> 3.14.3

Release Notes

nuxt-modules/i18n (@nuxtjs/i18n)
v9.1.0
Compare Source
This changelog is generated by GitHub Releases
🚀 Features

Configurable generated file and directory paths  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3235 (abc3d)

🐞 Bug Fixes

Sync route parsing utilities  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3211 (5363e)
Support special characters in generated messages type keys  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3223 (543e4)
Messages type generation not watching locale files  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3224 (c0532)
types:

Add missing shared types  -  by @userquin in https://github.com/nuxt-modules/i18n/issues/3212 (ff957)
Expose types to runtime with alias  -  by @BobbieGoede and @userquin in https://github.com/nuxt-modules/i18n/issues/3231 (bc8a2)

View changes on GitHub
v9.0.0
Compare Source
This changelog is generated by GitHub Releases
🚨 Breaking Changes

Upgrade vue-i18n v10  -  by @kazupon in https://github.com/nuxt-modules/i18n/issues/3001 (c3b1f)
Rename public runtime config properties  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3096 (34b7b)
Configurable lang attribute for useLocaleHead  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3097 (a3fb8)
Nuxt context injected function types  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3098 (97528)
Remove deprecated legacy dynamic route params  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/2801 (a00c2)
Change useLocaleHead options shape and defaults  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3100 (85550)
restructureDir defaults  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3106 (3e336)
Move to ESM only  -  by @userquin in https://github.com/nuxt-modules/i18n/issues/3118 (eb31e)
Remove deprecated locale iso property  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3146 (039f2)

🚀 Features

V-t directive SSR fully  -  by @kazupon in https://github.com/nuxt-modules/i18n/issues/3014 (0ef6d)
Generate Locale type based on configuration  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3025 (9aa71)
Configurable directory restructure  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3054 (08638)
Configurable directory restructure  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3054 (c906a)
Add support for multi domain locales  -  by @DotwoodMedia, Vincent de Vreede and DarthGigi in https://github.com/nuxt-modules/i18n/issues/3065 (88916)
Add support for multi domain locales  -  by @DotwoodMedia, Vincent de Vreede and DarthGigi in https://github.com/nuxt-modules/i18n/issues/3065 (93d62)
Runtime logger formatting and debug verbose option  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3067 (80d9e)
Support Nuxt 4  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3105 (73f6b)
Support Nuxt 4  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3105 (5ba98)
Experimental typed routes  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3142 (c103d)
Experimental vue-i18n and messages type generation  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3151 (4f734)

🐞 Bug Fixes

Unpin and update dependencies  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3015 (3c327)
Unable to configure server integration using inline options  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3020 (6c51e)
Generated module augmentation should use @intlify/core-base  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3034 (e2c58)
Unable to configure server integration using inline options  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3020 (856ba)
Encode switchLocalePath during SSR replacement  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3043 (be59c)
Encode switchLocalePath during SSR replacement  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3043 (28d22)
Rename locale iso property to language  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3055 (6a29a)
Rename locale iso property to language  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3055 (df938)
strategy: 'no_prefix' when using differentDomains  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3061 (8536b)
strategy: 'no_prefix' when using differentDomains  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3061 (53f16)
Cookie being reset on reload in ssg build  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3087 (ec74f)
Set default values for locales and restructureDir  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3088 (88a7b)
Cookie being reset on reload in ssg build  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3087 (7ccaf)
Empty i18n options not loading vue-i18n config file  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3093 (c720b)
Empty i18n options not loading vue-i18n config file  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3093 (a8463)
Fallback generated locale type to string  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3107 (b2d49)
Use generated tsconfig and virtual file augmentations  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3112 (62963)
Remove jiti version override  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3115 (2678e)
Don't use nuxt aliases  -  by @userquin in https://github.com/nuxt-modules/i18n/issues/3120 (98897)
Move shared types to runtime  -  by @userquin in https://github.com/nuxt-modules/i18n/issues/3121 (00638)
Custom routes not analyzed in layer with custom srcDir  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3133 (b9e52)
Custom routes not analyzed in layer with custom srcDir  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3133 (10c02)
Update intlify dependencies  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3137 (3bcda)
Use next tag for v9 edge release  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3138 (f61b5)
Warn when using SEO features without baseUrl  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3145 (35b45)
vueI18n resolution not using restructureDir defaults  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3159 (a0164)
Update @intlify/h3 dependency  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3165 (893f9)
Use experimental pages:resolved hook if enabled  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3196 (11b3e)
Use NuxtLink config in components  -  by @yeganemehr in https://github.com/nuxt-modules/i18n/issues/3183 (507a0)
Set publish tag to latest  -  by @BobbieGoede in https://github.com/nuxt-modules/i18n/issues/3198 (a9fb9)

View changes on GitHub

pnpm/pnpm (pnpm)
v9.14.4
Compare Source
Patch Changes

Don't ever save mutated metadata to the metadata cache.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v9.14.3
Compare Source
Patch Changes

Some commands should ignore the packageManager field check of package.json #7959.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

unjs/unimport (unimport)
v3.14.3
Compare Source
Bug Fixes

scan-dirs: correctly add the file pattern to the dirs glob. (#400) (3db6721)

v3.14.2
Compare Source
Bug Fixes

scan-dirs: add tsx and jsx into default file extensions (#397) (1c0aaeb)

v3.14.1
Compare Source
Bug Fixes

build: publish script (e59424c)

v3.14.0
Compare Source
Features

scan-dirs: support exclude glob and set dirs exclude types (#395) (5978277)

Performance Improvements

move fast-glob to tinyglobby (#396) (97bfaa0)

3.13.4 (2024-11-27)
Bug Fixes

upgrade string-literal to fix injecting import for the code with /a[/]bcd/ (#393) (8c03bf6)

3.13.3 (2024-11-23)
Bug Fixes

distinguish class by declarationType (#391) (250b001)

3.13.2 (2024-11-14)
Bug Fixes

Remove non-existing 'locale' from date-fns preset (#388) (f67b88d)

3.13.1 (2024-09-27)
Bug Fixes

addon: wrong vue directives transform filter (#380) (cf374a5)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Hywax Assistant.

👋 @hywax-assistant
💖 Thanks for opening this pull request!
We use semantic commit messages to streamline the release process.
Examples of commit messages with semantic prefixes:

fix: interval for sending a request in the base service
feat: add new NAME service
docs: example of using the NAME service

👋 @hywax-assistant Congrats on merging your first pull request! 🎉


Retry logic in clients

Right now the Cassandra Thrift clients (0.7, 0.8, and 1.0) and the Aerospike client (#324) implement client-side operation retries within YCSB code. I find that a little counterintuitive: I'd expect the operation failure rates reported by YCSB to be based on pretty simplistic client usage. Anyone have any thoughts?

I can see the merit in both arguments, but having differences across stores is yet more for our users to grok while comparing. So I think this is something we need to set a guideline for and document (sort of like the issue of making sure clients flush to remote after a transaction).
If we take the position of no-retries, what do we do with a datastore binding that does the retry below us? I guess at that point it can be seen as a feature of using that datastore?
If we want retries in general, it seems better to pull that functionality up into the wrapper. then we can report on the error rate still.

If we take the position of no-retries, what do we do with a datastore binding that does the retry below us? I guess at that point it can be seen as a feature of using that datastore?

I think so. If the client itself implements retries, fine - you'd see the same behavior in the wild.

yeah, I agree. We should start labeling these issues that have datastore binding guidelines. Eventually once we make a doc we can then do a sweep of bringing bindings in line. Not much use enforcing it until then.

Agreed, valid point.
I added the retry logic to take care of the occasional Amazon EBS hiccup. Thinking about this again, though, that logic should actually go into the Aerospike client and not into the YCSB binding, so that everyone benefits from it.
I'll change that.


Use pachyderm/pgbouncer:1.16.2 in unit tests

The fact that you changed environment variables is good; I think that's what prevented this from being a drop-in replacement. If the tests pass, merge this!

Haha yea, I was wondering why "it didn't work" before, and I realized I was just too lazy to go through each env variable name 😅.


The result out of domain

Hello !  thanks for sharing your great job!
I noticed your model also achieved a promising result in an out-of-domain case. Have you tested your model's performance in other domains, e.g. infrared images? And how about the robustness of your model in the out-of-domain case?
Thank you !

I don't think it would work on infrared images. That example is just an interesting case. I have not extensively tested its robustness in different domains.

I don't think it would work on infrared images. That example is just an interesting case. I have not extensively tested its robustness in different domains.

Thanks for your kind reply !


Upgrade terraform-provider-azuredevops to v0.5.0

This PR was generated via $ upgrade-provider pulumi/pulumi-azuredevops --upstream-provider-name=terraform-provider-azuredevops.

Upgrading terraform-provider-azuredevops from 0.4.0  to 0.5.0.
Fixes #151
Upgrading pulumi-terraform-bridge from v3.42.1 to v3.46.1.

Changes look like they align with upstream release notes


Fix create-botbuilder-parity-issues.yml workflow

Fixes #minor
Description
In response to the label "Automation: Parity all", this workflow tries to create a parity issue in the dotnet repo. Since this workflow action originates in the dotnet repo, it would be an error to create a parity issue in the dotnet repo.
Specific Changes
Remove dotnet from the matrix repo array.

Pull Request Test Coverage Report for Build 303074

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 78.793%

Totals

Change from base Build 303002:
0.006%

Covered Lines:
25320

Relevant Lines:
32135

💛  - Coveralls


Refactor remote attestation code

Description
Introduce teaclave_attestation, a new create for attestation related code.
This PR refactor RA related code and move them into the teaclave_attestation crate.
For the teaclave_attestation, we start to try thiserror and anyhow for error management.
Type of change (select applied and DELETE the others)

[x] Code polishing

How Has This Been Tested?
CI: https://ci.mesalock-linux.org/mssun/incubator-mesatee/275
Checklist (check ALL before submitting PR, even not applicable)

[x] Fork the repo and create your branch from master.
[x] If you've added code that should be tested, add tests.
[x] If you've changed APIs, update the documentation.
[x] Ensure the tests pass (see CI results).
[x] Make sure your code lints/format.

I also add a verifier.rs file (https://github.com/apache/incubator-teaclave/pull/198/files#diff-dd6dee8420bdab6e40cf4171574f1aec) for TLS verifier for RA. Basically, I create a new struct called SgxQuoteVerifier to wrap around EnclaveAttr and rewrite the original EnclaveAttr struct.


Keyboard Manager remove "keys" section to simplify interface

Description of the new feature / enhancement
After making https://github.com/microsoft/PowerToys/issues/13762 "keys" section will not be needed.
To simplify ui remove "keys" section.
Scenario when this would be used?
In games, apps.
Supporting information
No response

if memory serves, there is actually a reason why we do this, I believe key to key remapping can influence shortcut remapping.  @arjunbalgovind am i correct here?

Yes, that's correct. As per the initial design choice, key to key remappings are applied before shortcut remappings are applied and hence combining the two windows would not work unless they are divided into two sections and a clear ordering is enforced.
Example if a user remaps A->B, then when they hit "Ctrl+A" on their keyboard in the Remap Shortcut window, it would appear as Ctrl+B since the key level remapping is already reflected at that stage.

Ultimately, this may be part of #2027 so lets dup it against that.


Known Interface Bugs (kraken)

[ ] Status icon next to server name remains a spinner
[ ] Start/Stop/Install buttons unable to be used after pressing one of them unless page is refreshed

[ ] The version number is currently 0.8.7

[ ] UI does not properly indicate if daemon is unavailable on Add Server

https://github.com/PufferPanel/PufferPanel/blob/master/app/views/admin/server/view.html#L229
Code missed which uses the socket, this is no longer used
[ ]


Work around odd Rubinius problem involing variable arguments and super

This works around an apparent Rubinius bug having to do with methods taking variable arguments, and **options then using super. With this workaround, Rubinius no finally passes all tests.
The offending code was in RDF::Vocabulary::Term#initialize.

Coverage decreased (-0.04%) to 90.955% when pulling 310937b8f3e07bcabb80e4543740c8cb1d7ed2ee on feature/rbx-term-uri into e57000dcfca07ac4ae7e7328f0d459e7833a80fd on develop.

The following code illustrates the bug:
class Outer
  def initialize(*args, **options)
    raise ArgumentError, "args should be an array of a String, was #{args.inspect}" if args.first.is_a?(Array)
  end
end

class Inner < Outer
  def initialize(*args, **options)
    super
  end
end

Inner.new("foo", bar: :baz)

See https://github.com/rubinius/rubinius/issues/3643.


Creating sim-link to raw1394 file

Description of the bug: https://github.com/jsk-ros-pkg/jsk_travis/issues/187
There are a lot of build failures with this problem:
https://builds.apache.org/view/Incubator Projects/job/incubator-mxnet/job/master/482/
https://builds.apache.org/view/Incubator Projects/job/incubator-mxnet/job/master/475/

LGTM Thanks for doing this.

The failure is not related to this PR. Please put a  rebuild .

the 1394 error is not really an error

To really find the error, please print the error instead of sh "echo caught error"

@szha I agree that this, in majority (all?) of the failures, not the root cause. But can we still eliminate it so whoever is looking on the build would not be distracted by the red herring.

Find a single one that's failed due to this first.

On the other hand, it would be really helpful to print the actual error in the Jenkinsfile by fixing the line sh "echo caught error"

I want to remove red herring so no one else will spend time investigating something that is not relevant to build problems(even if 0 builds are failing due to this reason). And yep, I completely agree that fixing sh "echo caught error" would be a bigger win, I will try to allocate some time later to fix it.

The place to edit is at https://github.com/apache/incubator-mxnet/blob/master/Jenkinsfile#L526
The reference on how to edit is at https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#code-catcherror-code-catch-error-and-set-build-result
Hopefully you won't have to allocate too much time.

Doing it here https://github.com/apache/incubator-mxnet/pull/8199


Add CameraHelper

CameraHelper help you to visualize your camera in 3D space.

Thanks! I'm not sure whether the naming CameraHelper is descriptive enough for a class that helps you visualize the camera's frustum though. I can't think of a much better name, perhaps CameraModel or something. Who knows a better name?

I took the same name as in three.js but indeed it's not so explicit.

Ok @xoppa I updated everything.
Still the name...

Ok I just added thue update() after initialization.

thanks


Possibly too slow learning in simplemaze

It is suspicious that we need about 250K episodes to learn that the best choice from (3,1) is Left, and the score for Right remains pretty high.  There could be a bug in the simple maze, or in the learning algo (perhaps randomness has been lost somehow?).
Regardless where the bug is, we may consider taking this case, and trying to devise some problem-specific tests.  Perhaps tests that white-box check interaction of the Sarsa class and the Maze class.

fixed in PR #69


EnvisalinkAlarmPanel class overrides logging config

Thanks for all the  hard work.  Using this in a Samsung Smartthings environment and love it.
The EnvisalinkAlarmPanel class in alarm_panel.py currently overrides the logging configuration in the logging hierarchy when it is initialized.  This results in log messages being sent to syslog rather than the log file defined in the users root logger.  It also sets the logging level to DEBUG, which results in a lot of unnecessary logging if you are not in fact debugging.  If this is somehow necessary, allow the user to reset the logging config on the instance.

I inherited this code and so am not sure why it was setup like that but I can't think why this would be necessary so I should be able to change it.
Are you using the 4.x or 5.x version?

Using 4.6.  Was unaware there is a 5.x version so will check into that.

Sorry for the delay.  I've posted a new 4.8 release the the logging.basicConfig call removed.
I'll propagate that to the 5.x line in the future but have some other changes I need to sort out there first.


kube-proxy of rp nodes connecting to tp masters

What type of PR is this?
/kind bug
What this PR does / why we need it:
It sets --tenant-server-kubeconfig arg pointing to TP masters for kube-proxy at RP nodes.
Which issue(s) this PR fixes:

Fixes #1346
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

/lgtm


Unhelpful/misleading Parse error Unexpected '{' when source has bad indents

This was originally filed as Issue #2141, but it actually has nothing to do with tabs, and that issue was closed amid argument about tabs vs. spaces.  Moving on...
The actual issue is that in the presence of invalid indents (e.g. see example below), the parser error Unexpected '{' is confusing, misleading, and incorrect.  In this trivial example, it's easy to see what's wrong, but in a larger file with actual "{" chars, and especially for users new to CoffeeScript syntax, the error is very misleading.
Surely there is a more friendly error message such as "Unexpected Indent" or something similar that would be more appropriate than blaming the user for typing a character that doesn't even exist.
foo:
  spaces: 2
    spaces: 4

Error: In test.coffee, Parse error on line 3: Unexpected '{'
    at Object.parseError (/opt/local/lib/node_modules/coffee-script/lib/coffee-script/parser.js:470:11)
    at Object.parse (/opt/local/lib/node_modules/coffee-script/lib/coffee-script/parser.js:546:22)
    at Object.compile (/opt/local/lib/node_modules/coffee-script/lib/coffee-script/coffee-script.js:40:22)
    at /opt/local/lib/node_modules/coffee-script/lib/coffee-script/command.js:140:33
    at /opt/local/lib/node_modules/coffee-script/lib/coffee-script/command.js:110:18
    at [object Object].<anonymous> (fs.js:115:5)
    at [object Object].emit (events.js:64:17)
    at afterRead (fs.js:1112:12)
    at Object.wrapper [as oncomplete] (fs.js:254:17)

Yeah, that's not valid coffeescript. What did you expect the compilation to look like? {foo: {spaces: ?? }}


[NoQA] Memoize: Fix debugging stats issues

Details

[x] Add monitoringName to memoized functions

Some of the memoized functions lack identifiers while each function should have an id to be distinguishable.

[x] Update avgFnTime calculation

Memoized functions with a 100% cache hit ratio have avgFnTime equal to zero, while it should be equal to at least the first function call time.

[x] Analyze memoization for getEmojiUnicode

Cache retrieval tends to be slower than the actual function call, while it should be the other way around.

[x] Analyze getLocaleDigits usage

This function seems not to be used at all, possibly due to a specific flow Jason performed; consider adding memoize stats data to analytics.

[x] Investigate getUnreadReportsForUnreadIndicator performance

Retrieval/execution times are way above expected (8ms/22ms), while it should be faster.

[x] Optimize caching for freezeScreenWithLazyLoading

It creates many unnamed empty cache entries; check how to cache effectively and add monitoringName.

Fixed Issues

$ https://github.com/Expensify/App/issues/48319
PROPOSAL: https://github.com/Expensify/App/issues/48319#issue-2496723831
Tests

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@ishpaul777 This PR is not yet ready for review, sorry for the miss-click! :D

We might also adjust (or add another) timing for cacheRetrievalTime.
Currently it measure the time for cache itself but not for the entire memoize overhead, which might be insightful.
We either can add memoizeFnTime as a new mark or change cacheRetrievalTime to be measured from function start
https://github.com/Expensify/App/blob/b912e17c094c9e3fb4a374c66428a159ab59331a/src/libs/memoize/index.ts#L67

Update avgFnTime calculation
Memoized functions with a 100% cache hit ratio have avgFnTime equal to zero, while it should be equal to at least the first function call time.

After investigating, the first call is registered properly.
What is happening is that monitoring was enabled after initial function call was made, so the function call timing could not be registered and all subsequent calls were intercepted by the cache, so we ended up with zero value for fnTime.

Status update: https://github.com/Expensify/App/issues/48319#issuecomment-2324077191

Cache retrieval time stat was changed as follows:
Retrieval time adjustments
In the memoize module, we now track retrieval from the direct start of the function. Before, we started tracking the time after the initial setup (args, key calculations etc.). Setup can also contribute to retrieval time, so it should be measured as well.
This should contribute to more precise timings.
Before
        const statsEntry = stats.createEntry();

        // Detect if memoized function was called with `new` keyword. If so we need to call the original function as constructor.
        const constructable = !!new.target;

        const truncatedArgs = truncateArgs(args, options.maxArgs);

        const key = options.transformKey ? options.transformKey(truncatedArgs) : (truncatedArgs as Key);

        const retrievalTimeStart = performance.now();

After

        const statsEntry = stats.createEntry();

        const retrievalTimeStart = performance.now();

        // Detect if memoized function was called with `new` keyword. If so we need to call the original function as constructor.
        const constructable = !!new.target;

        const truncatedArgs = truncateArgs(args, options.maxArgs);

        const key = options.transformKey ? options.transformKey(truncatedArgs) : (truncatedArgs as Key);

fnTime and retrievalTime unification at stat entry level
In order to remove some complexity, the fnTime and cacheRetrievalTime marks were merge together into one processingTime and its separation was moved to the Stats module (based on didHit prop). It does not change anything in runtime, just simplifying code a bit.

@ishpaul777 The PR is ready to be reviewed now :)
CC @mountiny

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Thanks for the investigation, looks good to me

Hmm checklists are filled in, not an emergency

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/mountiny in version: 9.0.28-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 9.0.28-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Tests do not work properly.

The following tests have been fixed.

io.personium.jersey.engine.test.ScriptTest


Scoped Stores get duplicate modules when inheriting modules from parent

Scoped stores get duplicate modules when inheriting from Store. Need to make sure duplicates do not happen and native modules take precedence over inherited.

This is resolved. Inherited modules will be checked against store modules and the store modules will take precedent


Desktop- Split - Unable to select members for split expense in the group DM

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

Version Number: 9.0.55-6
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5142441&group_by=cases:section_id&group_id=306203&group_order=asc
Issue reported by: Applause - Internal Team
Action Performed:

Navigate to a group conversation with at least 2 users
Select Split expense
Select the Scan tab if it is not already active
Upload a digital receipt
Click on the radio button and select two members

Expected Result:
The user can select not all participants from the group DM for the split expense by clicking the radio buttons next to members' names/email addresses
Actual Result:
Unable to select members for split expense in the group DM. All group DM participants are selected by default
Workaround:
Unknown
Platforms:

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

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/cb6d3d04-6039-424c-9c58-50f46b098d72
View all open jobs on GitHub

@bfitzexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

@bfitzexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

This is p2p focused, which isn't a priority right now. Let's close this out for the moment.


Error when starting HTTP server: Address already in use

When attempting to start the HTTP server using the python -m http.server command, an OSError with the message "Address already in use" is encountered.

Setup and configuration
Current version:

Mac OS 14.4.1 Sonoma
My model and agent (you can see these settings in the UI):

Model: GPT 3.5 Turbo
Agent: Planner

Commands I ran to install and run OpenDevin:
pipenv install
Steps to Reproduce:

Create a simple web server that says "Hello World!"

Logs, error messages, and screenshots:
$ python3 -m http.server
Background command started. To stop it, send a kill action with id 27
$ Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/usr/lib/python3.10/http/server.py", line 1307, in
J    test(
File "/usr/lib/python3.10/http/server.py", line 1258, in test
w    with ServerClass(addr, HandlerClass) as httpd:
File "/usr/lib/python3.10/socketserver.py", line 452, in init
^    self.server_bind()
File "/usr/lib/python3.10/http/server.py", line 1301, in server_bind
g    return super().server_bind()
File "/usr/lib/python3.10/http/server.py", line 137, in server_bind
t    socketserver.TCPServer.server_bind(self)
File "/usr/lib/python3.10/socketserver.py", line 466, in server_bind
U    self.socket.bind(self.server_address)
OSError: [Errno 98] Address already in use
$ Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
`    exec(code, run_globals)
File "/usr/lib/python3.10/http/server.py", line 1307, in
J    test(
File "/usr/lib/python3.10/http/server.py", line 1258, in test
w    with ServerClass(addr, HandlerClass) as httpd:
File "/usr/lib/python3.10/socketserver.py", line 452, in init
^    self.server_bind()
File "/usr/lib/python3.10/http/server.py", line 1301, in server_bind
�    return super().server_bind()
File "/usr/lib/python3.10/http/server.py", line 137, in server_bind
socketserver.TCPServer.server_bind(self)
File "/usr/lib/python3.10/socketserver.py", line 466, in server_bind
U    self.socket.bind(self.server_address)
OSError: [Errno 98] Address already in use
$ python -m http.server
Background command started.  BTW @nickmoore444 you should be using uvicorn to start the server

I am using uvicorn to start the backend if I run this @stratte89 it will kill the backend server that's running on 3000, the problem is the http server isn't starting because it's trying to use an existing port, I noticed a few other people on youtube that ran into this.  Maybe starting the server on 8080?
python -m http.server 8080

Sorry I think I misunderstood--it's the agent running python -m http.server 8080?

The agent is not running on 8080 it's trying to use a port that's already being used I suggested the fix is to have it run on another port.

I'm going to close this in favor of https://github.com/OpenDevin/OpenDevin/issues/954


Command not found

In last step when i run vncstart command then displaying command not found

it should be found...try to reinstall it...or you can run the vncserver using ...
vncserver

Install VNC use this very interactive.


[RFC] Adopting black Python formatter.

The black Python formatter supports automated code formatting.  It's widely used on various Python projects like dask and optuna and I really like its output.  It allows me to write code without wrangling with formats, which is becoming more and more difficult with Python typing.
However currently xgboost's formatting style is quite different from the default in black so black will generate a huge diff.  It's "uncompromising" so we can't avoid it.

Another good alternative is yapf, which is mush lesser intrusive.

Closing for now.  Tried both formatter, I think this has to be an incremental effort, otherwise the diff is just too huge.


CH14 Implementing a ResNet-34 CNN Using Keras

Hi Aurélien, it seems that this line model.add(ResidualUnit(filters, strides=strides)) does not work.

It should be model.add(ResidualUnit(filters, strides)) instead.

Great tx a lot! I'm currently traveling, but when I get back (couple of weeks), I'll fix this.

Thanks for your reply Aurélien. Your code was right. It was my fault, I define strides as stride in the definition of ResidualUnit. For those who also encounter the same issue, please check your spelling of strides in this line, def __init__(self, filters, strides=1, activation="relu", **kwargs):


get nil while create verifier using public key

code:
let publicKey = SecKeyCreateWithData(data! as CFData, attributes as CFDictionary, &error)
let jws = try JWS(compactSerialization: serialization)
let verifier = Verifier(verifyingAlgorithm: .RS256, publicKey: publicKey) // get nil while create verifier
let payload = try jws.validate(using: verifier!).payload
let message = String(data: payload.data(), encoding: .utf8)!

Interesting, I'll take a look. Can you confirm, that publicKey is not nil in your example?

I could not reproduce your problem with the latest version of JOSESwift (1.4.0) on Xcode 10.1.
The following code
let publicKey = /* Generate public key */

// Get public key data
guard let publicKeyData = SecKeyCopyExternalRepresentation(publicKey, nil) else {
  print("Could not get data of public key.")
  return
}

let attributes: [String: Any] = [
  kSecAttrKeyType as String: kSecAttrKeyTypeRSA,
  kSecAttrKeyClass as String: kSecAttrKeyClassPublic,
  kSecAttrKeySizeInBits as String: 2048
]

// Create public key from data
guard let publicKeyFromData = SecKeyCreateWithData(publicKeyData, attributes as CFDictionary, nil) else {
  print("Could not create public key from data.")
  return
}

// Construct verifier from imported public key
let verifier = Verifier(verifyingAlgorithm: .RS256, publicKey: publicKeyFromData)

if verifier == nil {
  print("Verifier is nil.")
} else {
  print("Verifier is ok.")
}

prints "Verifier is ok.".
I suspect, that your public key was nil. Please double check your code. Feel free to open another issue if you still have the problem despite having a fully initialized public key.


Configure volumes for Grafana deployment

Is your feature request related to a problem? Please describe.
We are users of secrets-store-csi-driver-provider-azure to load secrets from Azure Key Vault to a Pod. My intent was to generate parts of the auth configuration in Terraform and store the content in a Key Vault secret. Then load the secret into the Grafana deployment. The issue is that secrets-store-csi-driver-provider-azure works by adding a volume to the Pod which refers to a specific storage class that is linked to the Key Vault. You can refer to this deployment for an example. Currently the Grafana resource only allows users to either set secrets and configmaps or add Deployment overrides. The issue is that GrafanaDeployment does not currently allow setting of volumes.
Describe the solution you'd like
An additional parameter Volumes in GrafanaDeployment would solve this use case allowing people to load configuration files with secrets-store-csi-driver-provider-azure. The Volumes configured would be appended to any other existing Volumes in the Grafana Deployment.
Describe alternatives you've considered
There are no other real options currently as it is not enough to only configure containers in the deployment.
Additional context
I can implement if you are willing to accept the PR.
Existing solutions
None.

Looks like this could be solved by #367 , @pb82 ?

Yes adding the ability to set volumes and volumemounts in the Grafana resource would solve this issue and probably #367.


support the custom img url

Issue: #140
support the custom img url.
Add new prop: customAvatar
Usage:
<Gravatar customAvavar="/local/avatar/url" className="your-classname"/>

BTW, add the prop-types into the package.json.
If it has any question, happy to discuss

I think this is addressed by the new domain prop.


How to compute Recall@100

Hi, one of the evaluation metric for zero shot object detection is Recall@100, but how to compute it is not very clear.
My understanding is following.
First, select top 100 detections from an image.
Second, mark a predicted bounding box as positive if it has an IoU greater than a threshold (0.5 for example) and no other higher confidence bounding box has been assigned to the same GT box.
Third, compute recall@100 for this image number_of_positive_prediction / 100.
Forth, compute recall@100 for all images sum(recall@100 for each image) / number_of_image.
Is it correct ? Thanks a lot!

In the third step, it should be : number_of_positive_prediction / number_of_all_gt_box * 100, for example: 50 / 100 * 100 = 50%
The other steps are correct.

Yes. Thanks!
By the way, how to generate word embedding vectors seems very confusing.
From here, I know that gensim is used to generate embeddings. But results are different between mine and the author's.
Do you know to generate the embeddings? Thanks very much.
Here is the script I used.
import numpy as np
import gensim.downloader
print(list(gensim.downloader.info()['models'].keys()))
# ['fasttext-wiki-news-subwords-300', 'conceptnet-numberbatch-17-06-300', 'word2vec-ruscorpora-300', 'word2vec-google-news-300', 'glove-wiki-gigaword-50', 'glove-wiki-gigaword-100', 'glove-wiki-gigaword-200', 'glove-wiki-gigaword-300', 'glove-twitter-25', 'glove-twitter-50', 'glove-twitter-100', 'glove-twitter-200', '__testing_word2vec-matrix-synopsis']
word_vectors = gensim.downloader.load('word2vec-google-news-300')
person_embedding = word_vectors['person']
person_embedding  = person_embedding / np.linalg.norm(person_embedding)
print(person_embedding)

Hi, I directly used the word embedding vectors from https://github.com/salman-h-khan/PL-ZSD_Release/blob/master/MSCOCO/word_w2v.txt.
I think your normalization operation is correct and I suspect the pre-trained w2v model could be different. (I also do not know which pre-trained w2v model used in https://github.com/salman-h-khan/PL-ZSD_Release,  and I just use the same embedding vectors for fair comparison)

OK, thanks very much for your kind answers.


deps: update cel-cpp to 0.5.0

Signed-off-by: Kuat Yessenov<EMAIL_ADDRESS>Commit Message: update CEL evaluator to 0.5.0 (https://github.com/google/cel-cpp/releases/tag/v0.5.0).
Risk Level: low
Testing: unit / regression
Docs Changes: none
Release Notes: none

/retest

/retest

/retest

Windows compiler does not like initializing int64_t constexpr with long values, sending a patch upstream.

This might require some serious patching of cel-cpp since it assumes aliased string_views when using protobuf. Sigh.

@kyessenov is there any way to avoid Envoy-side patches? We're really trying to avoid these going forward.

@htuch Yes, it can be fixed upstream. It's difficult to enforce in g3, so it just needs regular maintenance to ensure abseil-protobuf use is valid with non-aliased absl and std string_views.

Thank you for identifying the ambiguous long vs int64 issue. Awaiting cleaning up format check

The coverage dropped by 0.1% because of dependency upgrade? That is unexpected.

/retest

/retest

/lgtm deps

/retest

Yay, took 2 months on-off but finally ready!


No reconnection attempt on ECONNRESET error.

It seems to be that when a "ECONNRESET" error is encountered there is no attempt to reconnect until the socket times out (producing the "Timed out while trying to establish connection" error). Is this correct?

yes,  i have seen that issue too.


3 new topographical map images w/ fixed pine valley lake

*fixed the lake size and added back a few lines i forgot to move from another layer
All new topographical map images for all maps for a consistent look. With 5 meter step and labels to indicate the height, can't do SVGs or the labels will not export, the matrix transform settings were exported from QGIS with the PNG and when i tested Pine valley in a local version of Studio the settings worked perfect
matrix transform settings
Pine valley
-94.9
0
0
-94.9
199952
199952
Lake valley
-92.74
0
0
-92.74
197453
197453
Aurora falls (seems to be 6x6km map)
-141.86
0
0
-141.86
300459
300899

Looks good to me now if used with QGIS export settings

Could you please update renderBackground() in RailroadMap.ts to make use of these files?
I'm not a big fan of the green background on the labels. Could that be white instead?

"Could you please update renderBackground()" will do

"> I'm not a big fan of the green background on the labels. Could that be white instead?" me neither but its to understand what height goes to what line maybe antoher day il deal with the labels i got an idea but its getting late today

well shit i need to do the labels now cause i forgot the matrix stuff changes a bit when i changes stuff in the map image so dont merge il change the labels

it's good in my eyes now

🚀


Multiprocessing crashes when using start_method='fork' on M1 Macbook

Hello!
I would like to kindly ask for your assistance.
Multiprocessing crashes when I run tests on my Macbook Air 2020 M1, start_method of WorkerPool is 'fork'.
However, when I change the strart_method to 'spawn' it works just fine.
Please have a look at the attachments
I would appreciate a lot your help!
Best,
Tomer

Multiprocessing crashed .txt

I'm not a Mac expert, but from what I can gather 'fork' is not really stable on Mac. See also: https://bugs.python.org/issue37677 and https://bugs.python.org/issue33725. People recommend using 'spawn' (or 'forkserver') as start method as a workaround.
Now, I realize that spawn can have its downsides (slower, no shared objects), but would that be sufficient for your use case?
I don't have a Mac (w/ or w/out M1) at my disposal to test mpire, which is unfortunate.

Closing due to inactivity


BTC withdraw doesn't work

Hi,
My account has 0.1155 btc which I would like to withdraw.
Even if I try to withdraw only 0.11 btc (leaving$50 worth of BTC i.e. 0.0055btc to cover the transfer fee) monyx still says I don't have enough funds in my account.
Please fix it and actually enable withdraws

Nevermind.  Still same error as before. Withdraw does not get processed.

@monyxcoin , can you look into this?

I have the same issue

sounds like they disabled it again.

 Just let us withdraw our money! @monyxcoin

Looks like it's happening to all us right now I tried to withdrawal several times and keep getting same error
"Error or the hot wallet is empty and soon will be funded" after few minutes the pending amount disappears.

Calm down! Our hot wallet is now funded.

Read the error description! "Hot wallet is empty and soon will be funded"

Monyx I was little confused by that that's all. I never used word scam at all.

thank u monyx! Yes please read the errors guys

Monyx do you plan to find hot wallet? The constant disabling of deposits causes fear that you may exit. This causes price to go down. Just let people get out who want to get ou.

Do you plan to fund the hot wallet?


some confuse about the api getTextContent

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Chrome 84
Operating system and its version: macOS 10.15.5
PDF.js version: 2.5.207
Is a browser extension:

Steps to reproduce the problem:
1.
2.
What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)

when i parse a pdf, it parse the content to so many single letters, i am confuse that why not merge them into a word?
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

i want to know the function getTextContent's logic so that i can avoid it

i want to know the function getTextContent's logic so that i can avoid it

Attach (recommended) or Link to PDF file here:

Without this information, the issue is not actionable/valid.

i am confuse that why not merge them into a word?

In general that's actually done, however this is a very complex topic with a lot of heuristics and sometimes things aren't perfect.

As-is, this issue contains no actionable information and furthermore it's more-or-less guaranteed to be a duplicate of existing issues in https://github.com/mozilla/pdf.js/labels/4-text-selection

Attach (recommended) or Link to PDF file here:

Without this information, the issue is not actionable/valid.

i am confuse that why not merge them into a word?

In general that's actually done, however this is a very complex topic with a lot of heuristics and sometimes things aren't perfect.

As-is, this issue contains no actionable information and furthermore it's more-or-less guaranteed to be a duplicate of existing issues in https://github.com/mozilla/pdf.js/labels/4-text-selection


Add sponsorship details to home page.

This PR adds sponsorship details to the homepage, with a hyperlink to the sponsors website.
Changes:

index.html: A new h3 has been added along with a hyperlink attached image.
assetts/images/rev_outline.png: The sponsor's logo has been added to the assetts folder.

Gonna have to be a no chief


Time travel back from future

Hopefully one day Apple will make all our lives more easy: http://www.openradar.me/radar?id=4949404398125056

cc @terhechte 😂

Hahaha, These mistakes keep on happening until Apple finally resolves my bug report :)
@tomquist when are you coming back to Hamburg? ;)

@terhechte when your radar is fixed ;-)

@timcook you readin‘ this?

Hahaha! I love Apple developer humor!

Ha. Thanks @tomquist ! 😄
lol @TimCook


Added tests for src\test\common\installer\poetryInstaller.ts

For #9231

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[ ] Has a news entry file (remember to thank yourself!)
[ ] Appropriate comments and documentation strings in the code
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[x] Unit tests & system/integration tests are added/updated
[ ] Test plan is updated as appropriate
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #9278 into master will increase coverage by 0.87%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9278      +/-   ##
==========================================
+ Coverage   57.78%   58.65%   +0.87%
==========================================
  Files         557      537      -20
  Lines       29590    28391    -1199
  Branches     4474     4303     -171
==========================================
- Hits        17098    16653     -445
+ Misses      11548    10799     -749
+ Partials      944      939       -5

Impacted Files
Coverage Δ

src/datascience-ui/native-editor/redux/store.ts
0% <0%> (-100%)
:arrow_down:

...tascience-ui/native-editor/redux/reducers/index.ts
0% <0%> (-100%)
:arrow_down:

src/datascience-ui/history-react/redux/store.ts
0% <0%> (-100%)
:arrow_down:

...rc/datascience-ui/interactive-common/transforms.ts
0% <0%> (-100%)
:arrow_down:

...tascience-ui/history-react/redux/reducers/index.ts
0% <0%> (-100%)
:arrow_down:

src/datascience-ui/interactive-common/tokenizer.ts
0% <0%> (-65%)
:arrow_down:

src/datascience-ui/react-common/arePathsSame.ts
0% <0%> (-62.5%)
:arrow_down:

src/datascience-ui/react-common/locReactSide.ts
0% <0%> (-50%)
:arrow_down:

src/client/testing/serviceRegistry.ts
49.09% <0%> (-47.28%)
:arrow_down:

src/datascience-ui/react-common/logger.ts
0% <0%> (-40%)
:arrow_down:

... and 42 more

Continue to review full report at Codecov.

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


Fix positive test rate y-axis in trends chart

 Vertical axis for "Positive Test Rate" under Trends is broken (0, 1%, 1%, 2%, 2%, ...)


Allow using a specific instance of the bus with the hosted service

Motivation
The new AddMassTransitHostedService assumes that everyone uses containers and there's no more than one bus instance exists in the application. That's not always the case. We don't use containers for everything and we sometimes host two bus instances in one service.
There's also a bit of confusion about older extensions that have conflicting method names with the Microsoft DI integration library.
Implementation
Marked old extensions obsolete, along with the SimplifiedBusHealthCheck to encourage people to use new extensions and also add UseBusHealthCheck to the bus configuration code.
Added an overload for AddMassTransitHostedService that accepts an instance of IBusControl.

REbased/merged.


Proxy kwargs independently from positional args. Closes #571.

Thank you for the fix.
Could you please exclude all the not relevant formatting changes (e.g. changing '' to "")?
Also I think this change deserves a separate test case, not modifying the existing
it "behaves like the object it is trying to be" do

Done @andrykonchin; I also added support for proxied-method blocks and respond_to_missing? (following best practice). (The blocks were already working, but I added test coverage & made it explicit in the method-missing.)

Looks good. Thank you. But there is a failed spec on old Rubies.

I fixed the spec. Not a pretty fix, but an efficient one.

Closed in favor of #573


Translate model pagination documentation to English

refer https://github.com/hyperf/hyperf/pull/6515


无法自动更新

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

前面一堆叫你如何清晰的报错误的别管，反正就是无法更新

请现在再试一次，问题是否解决？如果未解决，看到什么错误提示？

已经调查到是windows7兼容性问题。最新内测版本已经添加了提示，bug即将关闭


Does this work with macOS / Apple Silicon?

I clone the repo, generate the bindings, build the demo...which all seems to work, but when I run the demo I get:
Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'Demo, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
Similarly when I create a new project and add the Libsql.Client nuget package...the app builds fine but when run I get:
Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'Libsql.Client, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Any ideas?

I have opened #18 to address "issue 2" outlined above and will keep this issue open for "issue 1".

Nice, I'm glad that did it. I will consider updating the configuration to unrestrict the platform target and close this issue once I decide whether or not to make the change.

I will remove the platform target to for the implied AnyCPU default.


Facial emotion using deep learning

Related Issuse or bug

Face emotion recognition can be done with various algorithms and here it is presented using tensorflow and opencv,

Fixes: #188
Additional Info

Readme contains everything. Datasets are also added in the repo.

Can you assign this to me as a part of CrossWoC

great @smriti1313

Hi, I guess since I was not assigned this issue, the points regarding this issue is not reflected on the DWoC leaderboard.


Fix false passing report on compile time failures

Test: perl6 -e 'use Test; my $fake_test_dir = "/tmp/t".IO andthen *.mkdir; my $fake_test_file = $fake_test_dir.child("should-fail.t") andthen *.spurt(q|use Test; use Not::Found; ok 0;|); nok( run($_, $fake_test_file), "Failing test should fail: $_" ) for <prove prove6>;'

Instead of $aggregator.failed, it should probably call $aggregator.has-errors

Fixed in master


Add 3D version of UpSampling

Seems like the build failed because of PRNG stuff. Should I close this PR and create a new one?

I believe all you need is to pull the latest master.

I deleted this repository though. I'll just close/re-open.


SIFT install on Ubuntu 18.04.1 LTS Incomplete due to Failures

I'm trying to install SIFT on Ubuntu 18.04.1 LTS and getting the following results.

Incomplete due to Failures -- Success: 199, Failure: 82

List of Failures (first 10 only)

 NOTE: First failure is generally the root cause.

 IMPORTANT: If opening a ticket, please include this information.

  - ID: python-software-properties
    SLS: sift.packages.python-software-properties
    Run#: 0
    Comment: Problem encountered installing package(s). Additional info follows:

It appears the failure is due to python-software-properties so I tried to find and install this package manually and found...
$ apt-get install python-software-properties
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package python-software-properties is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
software-properties-common
E: Package 'python-software-properties' has no installation candidate
When I tried to install the replacement (software-properties-common), I got...
$ apt-get install software-properties-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
software-properties-common is already the newest version (<IP_ADDRESS>.5).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Is there something I can do to work around these errors and package changes or is this something that needs to be fixed on the SIFT package end of things?

18.04 is not yet supported.
Sent from my iPhone

On Sep 27, 2018, at 08:57, qiMakur<EMAIL_ADDRESS>wrote:
I'm trying to install SIFT on Ubuntu 18.04.1 LTS and getting the following results.
Incomplete due to Failures -- Success: 199, Failure: 82
List of Failures (first 10 only)
NOTE: First failure is generally the root cause.
IMPORTANT: If opening a ticket, please include this information.

ID: python-software-properties
SLS: sift.packages.python-software-properties
Run#: 0
Comment: Problem encountered installing package(s). Additional info follows:
It appears the failure is due to python-software-properties so I tried to find and install this package manually and found...

$ apt-get install python-software-properties
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package python-software-properties is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
software-properties-common
E: Package 'python-software-properties' has no installation candidate
When I tried to install the replacement (software-properties-common), I got...
$ apt-get install software-properties-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
software-properties-common is already the newest version (<IP_ADDRESS>.5).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Is there something I can do to work around these errors and package changes or is this something that needs to be fixed on the SIFT package end of things?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

any idea when it will be?

I'm having the same issues with 18.04. I am going to try to use an earlier version of ubuntu. I did re read the instructions and it does state to download ubuntu 16.04

18.04 is still not supported 100%.

When can we expect 18.04 to be supported?

Beta is up. Instructions are at https://github.com/teamdfir/sift-saltstack
Sent from my iPhone

On Jun 16, 2019, at 13:14, JustinDuaneNewman<EMAIL_ADDRESS>wrote:
When can we expect 18.04 to be supported?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Colab GPU limits exceeded

I can't run this notebook in colab. As soon as I try downloading CARLA ("! sudo -u colab wget -O /home/colab/CARLA.tar.gz https://carla-releases.s3.eu-west-3.amazonaws.com/Linux/CARLA_0.9.10.tar.gz"), Colab stops by saying that COlab GPU limits have exceeded. I haven't used Colab in a few days, so its not because I've been running the GPU for a long time. Is it possible that Colab bans me because of downloading a lot of files very fast?

No, Colab users are not banned for downloading files. The error is actually the one reported i.e., GPU limits exceeded.
It is a coincidence that it stops during the download (you can try run other code if you want)
I have personal experience on this: Colab keeps shutting down my instances even with the pro subscription as I used Colab too much in a short time, apparently (BTW, I didn't use Carla at the time as it was a different project). Even after several months, I cannot use Colab with my primary account. I found confirmation in this Reddit.

Oh wow, this is a surprise. Thanks a lot for your help. I'll probably have
to shift to some other platform.


improve findSimilarClasses with awareness of class channel name format

Improve findSimilarClasses to support narrowing down class channels based on prefix (e.g. cop), code (e.g. 3223), professor name, the entire name, or a prefix of the entire name (e.g. cop3223). Keeps Levenshtein similarity as a fallback.
Closes #835

this lgtm
it would be fantastic if you could add a few unit tests that have an input and list of classes, or if you otherwise show how you tested this

Added some unit tests.
To support ClassService I stubbed GuildService including guild.channels.cache. I'm not that experienced in writing tests, so I would appreciate any feedback on my approach or suggestions for improvement.
Here are also a few screenshots from my local testing using the server's template at https://discord.com/template/y79RbsjxvZfN :

screenshots


Index for all channels not refreshing on mambabuild

The index repodata cache is not being refreshed for all the conda channels because of the big ttl set on:
https://github.com/mamba-org/boa/blob/fc9050d1f392382b09571e72cffc8554d3003802/boa/cli/mambabuild.py#L71
I think this need to be configurable or, at least, much, much smaller.
@wolfv @marcelotrevisani - what do you think?
I searched at mamba's codebase and the ttl of the cache doesn't seem to be set to a high number there, so it's a problem only for mambabuild.

I believe that would be nice to have it at least configurable in a certain way
maybe something like
mamba --config local_repodata_ttl=1000

Is it possible to use conda config for that?
For example:
conda config --set boa.local_repodata_ttl 600
Or conda would not allow it because:
CondaValueError: Key 'boa' is not a known primitive parameter.

Does this mean we would have something like a .mambarc or .boarc ?
Can this be passed as a command-line argument to mambabuild for now?
I guess we need your input here @wolfv  :-)

Yeah I'd be happy to have a boarc file! Will need it soon for other stuff. PRs welcome :)

@wolfv - I'm happy to contribute with the .boarc :-)
Do you think we should leverage the Config machinery available from conda (since conda is already a dependency) or implement a new one?

Good question. Might be better to start a new one, I'm not sure how conda handles unknown keys


fix: deep and universal links

Summary:

Fixes #138
Deep and Universal Links currently do not work on RN visionOS. Since iOS 13, if the project has opted into Scenes, lifecycle events are now controlled by SceneDelegate instead of AppDelegate.
After this PR is merged, we also need docs showing how to implement them, since the React Native docs only apply to non-Scene apps.
This PR is intended to be worked on. Currently, this solution works for Deep and Universal links when the app is already running or in background. When launching the app (previously killed) via Deep or Universal Links, Linking.getInitialUrl() will  always return null, due to launchOptions being initialized as an empty object in RCTReactViewController.
The Apple Documentation indicates scene(_ :continue:) for handling Universal Links when app is already running, but that only applies to UIKit-based apps. For SwiftUI, the onOpenURL(_:perform:) view modifier must be used.
Final usage example for apps:
SceneDelegate.swift
class SceneDelegate: NSObject, UIWindowSceneDelegate {
  ...

  func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) {
    // Other logic already present here
    ...

    // Deep Links and Universal Links - called when the app was previously NOT running
    RCTLinkingManager.scene(scene, willConnectTo: session, options: connectionOptions)
  }

  func scene(_ scene: UIScene, openURLContexts URLContexts: Set<UIOpenURLContext>) {
      // Deep Links - called when the app was previously running or suspended
      RCTLinkingManager.scene(scene, openURLContexts: URLContexts)
  }
}

App.swift
struct visionaryApp: App {
  @UIApplicationDelegateAdaptor var delegate: AppDelegate

  var body: some Scene {
    WindowGroup {
      TabView {
        RCTRootViewRepresentable(moduleName: "myApp")
          .tabItem {
            Label("Home", systemImage: "house.fill")
          }
        RCTRootViewRepresentable(moduleName: "SettingsScreen")
          .tabItem {
            Label("Settings", systemImage: "gear")
          }
      }
      // Add the onOpenURL view modifier
      // Calling AppDelegate directly here but this should be improved to call SceneDelegate, probably
      .onOpenURL(perform: { (universalLink: URL) in
        delegate.onOpenURL(url: universalLink)
      })
    }

  }
}

AppDelegate.swift
class AppDelegate: RCTAppDelegate {
  ...

  // Universal Links - called when the app was previously running or suspended
  func onOpenURL(url: URL) {
    RCTLinkingManager.onOpen(url)
  }
}

Changelog:

[IOS] [ADDED] - Added equivalent scene method scene:willConnectTo:options: to handle Deep and Universal Links when app was previously NOT running
[IOS] [ADDED] - Added equivalent scene method scene:openURLContexts: to handle Deep Links when app was previously in background or suspended
[IOS] [ADDED] - Added equivalent scene method onOpenURL to handle Universal Links when app was previously in background or suspended
Test Plan:

Deep Link (rntester://) with app previously killed, fetch initial URL via Linking.getInitialURL()
Deep Link (rntester://) with app previously running or suspended, fetch incoming url via Linking.addEventListener('url', callback)
Universal Link with app previously killed, fetch initial URL via Linking.getInitialURL()
Universal Link with app previously running or suspended, fetch incoming url via Linking.addEventListener('url', callback)

Closed in favour of #140


Fixes #14 Mac M1 build issue

Sorry for the long pause. The PR aims to address a Mac M1 build issue by adding libgeos-dev and upgrading pyproj. utm zone is updated to integer per underlying lib requirement.
Closes #14

Thanks for updating the commits -- it looks like EasyCLA picked those changes up and now we just need the CLA itself signed.  You should be able to do that by clicking "Please click here to be authorized." in the EasyCLA message, but please let me know if you have any problems.  The CLA process and agreement is intended to be quick and lightweight to just provide the protection InterUSS needs to keep functioning, but we sometimes run into problems.  Fortunately, the Linux Foundation is usually pretty quick to help resolve them.

Hi @BenjaminPelletier, apologies for not getting back quickly. I understand the purpose of the CLA process. In fact I am waiting for my team to furnish me the appropriate details to apply for the license. It is just some administrative matters that I hope to clear by the end of this week.

As a follow up, the recent change to python slim results in some packages failing to build on Mac M1.  As these packages have no arm 64 built distribution yet,  they require gcc to build.
 × Building wheel for psutil (pyproject.toml) did not run successfully.
#9 15.62   │ exit code: 1
#9 15.62   ╰─> [43 lines of output]
#9 15.62       running bdist_wheel
#9 15.62       running build
#9 15.62       running build_py
#9 15.62       creating build
#9 15.62       creating build/lib.linux-aarch64-cpython-38
#9 15.62       creating build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/_pssunos.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/_psposix.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/_psaix.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/_compat.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/_pslinux.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/_common.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/_psbsd.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/__init__.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/_psosx.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       copying psutil/_pswindows.py -> build/lib.linux-aarch64-cpython-38/psutil
#9 15.62       creating build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_unicode.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_misc.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_linux.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_sunos.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_osx.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_aix.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/runner.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_testutils.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_system.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_connections.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/__init__.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_bsd.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_windows.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_memleaks.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_contracts.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_posix.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/test_process.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       copying psutil/tests/__main__.py -> build/lib.linux-aarch64-cpython-38/psutil/tests
#9 15.62       running build_ext
#9 15.62       building 'psutil._psutil_linux' extension
#9 15.62       creating build/temp.linux-aarch64-cpython-38
#9 15.62       creating build/temp.linux-aarch64-cpython-38/psutil
#9 15.62       gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPSUTIL_POSIX=1 -DPSUTIL_SIZEOF_PID_T=4 -DPSUTIL_VERSION=594 -DPy_LIMITED_API=0x03060000 -DPSUTIL_LINUX=1 -DPSUTIL_ETHTOOL_MISSING_TYPES=1 -I/usr/local/include/python3.8 -c psutil/_psutil_common.c -o build/temp.linux-aarch64-cpython-38/psutil/_psutil_common.o
#9 15.62       C compiler or Python headers are not installed on this system. Try to run:
#9 15.62       sudo apt-get install gcc python3-dev
#9 15.62       error: command 'gcc' failed: No such file or directory
#9 15.62       [end of output]

Just added gcc and it will build fine.  Let me know if I can add it.
To slim the image size, maybe we can add a stage for compiling the packages and then use them in next stage. Need to find out exact steps.

Awesome, sounds great.  Yes, we want to have as broad of support as practical, so adding gcc sounds fine.  Ideally/eventually, it would probably be good to have a multi-stage build so that gcc is available to perform the necessary package installation, but then not included in the final built image.  Until we have developer time to do that, leaving gcc in the build to enable compatibility on arm64 platforms seems fine.

After a little hiccup setting up, looks like the CLA is now covered!

Thanks for working through everything for this contribution; much appreciated!


[BUG] Centaur Warrunner's Horsepower facet movement speed irregularities

Bug type

[ ] Ability
[ ] Item
[ X ] Hero
[ ] Bot
[ ] UI
[ ] Other

Describe the bug
Centaur Warrunner's Horsepower Facet does not stack with points based movement speed increases (boots, battle level bonuses). The interaction is finicky.
Expected behavior
Centaur Warrunner should receive 30% of his strength as bonus movement speed
To Reproduce
Use Horsepower facet, purchase Wings of haste, allocate Battle pass points in to movement speed. Level up and/or increase Centaur's strength and observe his movement speed as you do.
Screenshots
Screenshot 1: +275 movement speed (should be +323)
161 Strength * .3 = 48.3 + 100 (boots) + 175 (battle points) = 323 bonus movement speed

Screenshot 2: +275 movement speed (should be +295)
66 Strength * .3 = 19.8 + 100 (boots) + 175 (battle points) = 295 bonus movement speed

Screenshot 3: +275 movement speed (should be +348)
244 Strength * .3 = 73.2 + 100 (boots) + 175 (battle points) = 348 bonus movement speed

Screenshot showing +175 MS from battle pass

https://www.dota2.com/hero/centaurwarrunner
It is same as Dota2 described

@windybirth What about the +175 movement speed bonus from the battle points?