Android cannot build

Description
Cannot build project for android on MacBook Apple M1. IOS works fine.
React Native Version: 0.67.2
Android NDK: 25.1.8937393
I tried to create a new project and everything ran fine there. This project also compiled successfully on windows.
Version
0.1.172
Steps to reproduce
.
Snack, code example, screenshot, or link to a repository
Unfortunately, I can not pass the code of my project
Error: Command failed: ./gradlew app:installGooglePlayDebug -PreactNativeDevServerPort=8081
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
Note: /Users/alex/Documents/code/react-native/discify_app/node_modules/lottie-react-native/src/android/src/main/java/com/airbnb/android/react/lottie/LottieAnimationViewManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/alex/Documents/code/react-native/discify_app/node_modules/lottie-react-native/src/android/src/main/java/com/airbnb/android/react/lottie/LottieAnimationViewManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note<EMAIL_ADDRESS>uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /Users/alex/Documents/code/react-native/discify_app/node_modules/react-native-background-timer/android/src/main/java/com/ocetnik/timer/BackgroundTimerModule.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/alex/Documents/code/react-native/discify_app/node_modules/react-native-share/android/src/main/java/cl/json/RNSharePathUtil.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/alex/Documents/code/react-native/discify_app/node_modules/react-native-sound/android/src/main/java/com/zmxv/RNSound/RNSoundModule.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/alex/Documents/code/react-native/discify_app/node_modules/react-native-svg/android/src/main/java/com/horcrux/svg/VirtualView.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/alex/Documents/code/react-native/discify_app/node_modules/react-native-video/android/src/main/java/com/brentvatne/react/ReactVideoViewManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/alex/Documents/code/react-native/discify_app/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
/Users/alex/Documents/code/react-native/discify_app/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:33: error: package com.shopify.reactnative.skia does not exist
import com.shopify.reactnative.skia.RNSkiaPackage;
^
/Users/alex/Documents/code/react-native/discify_app/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:128: error: cannot find symbol
new RNSkiaPackage(),
^
symbol:   class RNSkiaPackage
location: class PackageList
Note: /Users/alex/Documents/code/react-native/discify_app/android/app/src/debug/java/com/discify_app/ReactNativeFlipper.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
2 errors
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileGooglePlayDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 51s

We need more information to reproduce the issue here.
What are the steps we need to execute to reproduce the build error? It looks like the RN Skia module is not found somehow?

For some reason it does not work in my project. in the new project everything works.
I just installed the module and ran npm run android
It is also very strange that it does not work on mac os, on windows everything works.
I have tried everything, uninstalling modules, reinstalling android ndk, trying different versions of react native skia, but still nothing works

i also found that people faced with this issue before there https://github.com/Shopify/react-native-skia/issues/144

@wcandillon Hi, I'm experiencing something similar.
react-native-skia builds fine on our iOS build, but does not build on our Android build.
We are on RN 0.69.7
Here's the initial error:

We then tried a fresh RN project using RN version 0.71.7. by:
npx react-native init testSkia
yarn add @shopify/react-native-skia
This worked on Android. We then tried another fresh RN project but this time using RN version 0.69.7. We couldn't get this to work on Android. The build kept failing with errors like:
Make Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: FBJNI_LIBRARY linked by target "rnskia" in directory /XXXXX/Documents/testSkia/testSkia69/node_modules/@shopify/react-native-skia/android JSI_LIB linked by target "rnskia" in directory /XXXXXX/Documents/testSkia/testSkia69/node_modules/@shopify/react-native-skia/android REACT_LIB
We tried all the recommended fixes but none of them worked.
We then thought, we should try to upgrade our project from 0.69.7 to 0.71.7 since react-native-skia built fine on the fresh RN 0.71.7. We spent all day getting the project to upgrade to 0.71.7 and building successfully on iOS. BUT again skia gave us cmake errors on even this version!
I'm at wits end trying to figure this out.
To summarize, we got react-native-skia:
Fresh RN 0.69.7 project -> FAILS on Android
Fresh RN 0.71.7 project -> SUCCESSFUL on Android
On our own project with rn 0.69.7 build SUCCESSFULLY on iOS but FAILS on ANDROID
On our own project with rn 0.71.7 builds SUCCESSFULLY on iOS but FAILS on ANDROID
Any help would be much appreciated. I will try to provide more error logs tomorrow... been a long day.


certmanager: solve CannotRegenerateKey

CertManager throws a warning with the current Helm chart because the .spec.privateKey.rotationPolicy is unset.
This will set the field to Always which allows rotation in case there is a need for, which can resolve potential issues of an invalid cert.
  Type     Reason               Age   From                                   Message
  ----     ------               ----  ----                                   -------
  Warning  CannotRegenerateKey  12m   cert-manager-certificates-key-manager  User intervention required: existing private key in Secret "hubble-relay-client-certs" does not match requirements on Certificate resource, mismatching fields: [spec.privateKey.algorithm[], but cert-manager cannot create new private key as the Certificate's .spec.privateKey.rotationPolicy is unset or set to Never. To allow cert-manager to create a new private key you can set .spec.privateKey.rotationPolicy to 'Always' (this will result in the private key being regenerated every time a cert is renewed)

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Are you a user of Cilium? Please add yourself to the Users doc
[x] Thanks for contributing!

/test

@universam1 It seems the failed CI test in Gateway API is due your branch lagging behind main a bit. Could you rebase on origin/main? Thanks!

Thanks for the heads up @gandro - rebased on current main

/test


inbound parse webhook incorrectly parses e-mail addresses including encoded words

Scenario: we receive an e-mail from a user that felt really lucky that he could use an address like: From: =?UTF-8?B?PG15LW5hbWUtYWdhaW5AaG9zdC5sb2NhbD4=?=<EMAIL_ADDRESS>The inbound parse webhook will send us this in the “from” field as the value<EMAIL_ADDRESS><user@TEST> which is not a legal e-mail address anymore.
The original one may be really strange and close to a bad idea, although it is legal as it conforms to RFCs.
I think the relevant RFCs are 5322 and 2047.  RFC-2047 mentions: “IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's”.
The address syntax is specified in 5322, in this case it can be applied like this:
address         =   mailbox / group dropping group, which in our case expands to:
address         =   (name-addr / addr-spec) dropping add-spec, expands to:
address         =   [display-name] angle-addr expanding display-name, leads to:
address         =   phrase angle-addr expanding phrase leads to
address         =   (1*word / obs-phrase) angle-addr In our case it ends as
address         =   atom angle-addr which is equal to:
address         = =?UTF-8?B?PG15LW5hbWUtYWdhaW5AaG9zdC5sb2NhbD4=?=<EMAIL_ADDRESS>This proves that the address is sound, you can have <foo@bar> <foo@bar> without putting it with quotes as ”<foo@bar>” <foo@bar> when using word-encoding.
From what I understand of the RFC there is no legal way to represent decoded UTF-8 in an address. It would certainly be more correct if under these circumstances the “Name” would be at least put in quotes. At least the golang mail parser would parse that correctly then.
If this can’t be done then at least the documentation should be updated because it’s currently very misleading (for from and to) :

Email sender, as taken from the message headers.

Should be rephrased to something like:

Email sender name and address. Both decoded into charset and separated by space. May not conform to a RFC 5322 e-mail address.

tl;dr summary: The addresses in from from inbound parse can't be used to do something like send email reply to the sender. As alternative I can use the raw headers and parse the From:  in there.
The documentation is not helpful as it lacks the point that the email in from is useless except for displaying purposes.


[Enhancement] task worker pool name should be distinguished in top -H

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
When a be is running, we can distinguish the thread name of taskworkerpool. The default name is too long.
be/src/agent/task_worker_pool.cpp
Solution
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

i'd like to try

i'm willing to try

@dataroaring  Hi, I want to try this issue. I read the source file and did not understand clearly the problem. Could you please make a detailed example? (Like, from what to what?) Thanks! :)

@dataroaring Hi, I want to try this issue. I read the source file and did not understand clearly the problem. Could you please make a detailed example? (Like, from what to what?) Thanks! :)

TaskWorkerPool::TaskWorkerPool(std::string_view name, int worker_count,
std::function<void(const TAgentTaskRequest& task)> callback)
: _callback(std::move(callback)) {
auto st = ThreadPoolBuilder(fmt::format("TaskWorkerPool.{}", name))
.set_min_threads(worker_count)
.set_max_threads(worker_count)
.build(&_thread_pool);
CHECK(st.ok()) << name << ": " << st;
}
Here TaskWorkerPool.xxx is name of the worker thread. However, when we use top -H in linux, thread num is cut, so we just see TaskWor. We can name it TWP{name}, names also should be short.

i have no experience, can i try?


Rename and rework build tests

Damon has inspired me with our newfound test coverage.
Closes #1034
We should definitely expand on this - builds is very much not tested. But figured it'd be nice to get our existing tests running

@sf-dcp - codecov edits the existing comment as you push commits

Oops sorry @sf-dcp , I kept working on this not thinking that I had already requested review. Just added one more test - I'll get this merged after tests pass and leave at current coverage for now


Just upgraded to the latest version today and the integration stopped working. Please look into it.

This error originated from a custom integration.
Logger: homeassistant.config_entries
Source: custom_components/lektrico_custom/init.py:44
Integration: Lektrico Charging Station (documentation, issues)
First occurred: 9:33:14 PM (2 occurrences)
Last logged: 9:39:02 PM
Error setting up entry Wallbox Charger for lektrico_custom
Error setting up entry Wallbox Lektrico for lektrico_custom
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/lektrico_custom/init.py", line 44, in async_setup_entry
await charger.charger_info()
File "/usr/local/lib/python3.9/site-packages/lektricowifi/lektricowifi.py", line 103, in charger_info
return Info.from_dict(data)
File "/usr/local/lib/python3.9/site-packages/lektricowifi/models.py", line 62, in from_dict
user_current = data["user_current"]
KeyError: 'user_current'

Hello masoudemad,
Thank you very much for reporting this issue.
I talked with our development team and the error is because 'user_current' exists in the firmware 1.41 which has no official release yet. The official release will appear soon and only then the chargers will auto update to this firmware.
Can you please confirm that your charger has a lower version than 1.41 ?
If you tell us the serial number of your charger, we can update it now (the serial number is that 5XXXXX number).
Or you can contact the support and ask for 1.41 firmware.
Thank you for your patience and understanding,
Mihaela G.P.

Thank you Mihaela for getting back to me so quickly. Just looked and "Automatic updates" option is enabled in the app.I confirm that the charger has 1.40 firmware. S/N: 500262
Regards,Emad
On Friday, May 13, 2022, 10:06:41 AM GMT+3, mtarjoianu @.***> wrote:
Hello masoudemad,
Thank you very much for reporting this issue.
I talked with our development team and the error is because 'user_current' exists in the firmware 1.41 which has no official release yet. The official release will appear soon and only then the chargers will auto update to this firmware.
Can you please confirm that your charger has a lower version than 1.41 ?
If you tell us the serial number of your charger, we can update it now (the serial number is that 5XXXXX number).
Or you can contact the support and ask for 1.41 firmware.
Thank you for your patience and understanding,
Mihaela G.P.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hello Emad,
Your charger was updated to version 1.41.
The above error with "user current" should no longer appear.
Best Regards,
Mihaela


Fix naming of cubes from abf/abl files

The abf/abl file loader was setting the name of the cubes incorrectly.
On this page explaining the LAI3g & FPAR3g datasets it states that:
abl <- LAI3g
abf <- FPAR3g
as opposed to what we currently have

@pp-mo, do you mind having a look at this?


v0.2.0

Pull Request Test Coverage Report for Build 77

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 69:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


Sqldbawithabeard verbose shouldprocess

I have removed Write-Host and added Write-Verbose enabling .\install.ps1 ...... -Verbose to show all the steps
I have moved the output to the end block and used write-output for that
I have added SupportsShould process enabling .\install.ps1 -WhatIf to show what would happen if you ran the install

What If on Suitable Instance

Verbose install

None Verbose Install

I could easily prove a log file if you would like ?

Also added check for the smo connection - that should have been in the comments as well


AutoComplete - Faster tab completion

I've made some changes that allows for faster tab completion by backspacing all the needed characters at once, as opposed to one at a time.
Prior to this change, I've noticed some issues with very slow tab completion, especially when using a readline project over an ssh connection. I think this addresses those issues.
This PR is similar to the goal of #45, but makes much smaller changes, and passes all unit tests.
Thanks so much for this project, hope this change is useful!

I see what you did.   I approve this change.  Nice job!

@Latency Yep, all tests seem to be passing!

Can you take a look at Ctrl+W .. It looks like you could do your magic there too.
Thoughts?

@Latency Oh sweet, I'll check out your fork. I can look into Ctrl+W too

What I do is configure Remote Repositories to include whomever and that way you can track their changes to be merged into your branch.
It is showing that mine is the latest branch.  I am working on getting PR admin access... so we can merge it to master.
I updated target framework versions today to latest as well.  I believe I have a .nupkg port ready for download on my repo.
You can configure your Tools -> NuGet Package Manager -> Package Manager Settings to include the location of the newly downloaded file so it can find it in NuGet to be added rather than NuGet,org for now.


apt-get (not pip) install SciPy

Hopefully this will prevent timeouts on Travis.

I'm now using this setup to install numpy&scipy for Python 2.x and 3.x on Travis: https://github.com/TeamHG-Memex/Formasaurus/blob/master/.travis.yml. scipy is still installed by pip (it is in install_requires); apt-get install scipy ensures dependencies are satisfied. It is kind of slow the first time (and with no output because of travis_wait), but subsequent runs are fast.

Thanks, I stole some of that for my second version. I'm now trying Travis's Trusty beta to get a new enough SciPy.

wow, they finally made Trusty beta, didn't know that - thanks!

Not that it matters, it doesn't seem to pick up the right NumPy for some reason...

Ok, got it right, pushed to master.

:+1:


Automated cherry pick of #8258: feat: add a retry mechanism to AutoSyncExtDiskSnapshot

Cherry pick of #8258 on release/3.4.
#8258: feat: add a retry mechanism to AutoSyncExtDiskSnapshot

Codecov Report

Merging #8263 into release/3.4 will decrease coverage by 2.68%.
The diff coverage is 0.36%.

@@              Coverage Diff               @@
##           release/3.4   #8263      +/-   ##
==============================================
- Coverage         6.22%   3.53%   -2.69%
==============================================
  Files              759     303     -456
  Lines           117145   62169   -54976
==============================================
- Hits              7289    2198    -5091
+ Misses          109197   59819   -49378
+ Partials           659     152     -507

Flag
Coverage Δ

#aFlag
3.53% <0.36%> (-2.69%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/compute/models/buckets.go
1.10% <0.00%> (+0.03%)
:arrow_up:

pkg/compute/models/cachedimages.go
1.75% <0.00%> (-0.06%)
:arrow_down:

pkg/compute/models/cloudaccounts.go
0.48% <0.00%> (-4.66%)
:arrow_down:

pkg/compute/models/dns_recordsets.go
1.82% <0.00%> (-0.24%)
:arrow_down:

pkg/compute/models/dns_zones.go
1.62% <0.00%> (-0.06%)
:arrow_down:

pkg/compute/models/initdb.go
0.00% <0.00%> (ø)

pkg/compute/models/loadbalancerawscachedlbb.go
5.71% <0.00%> (+0.08%)
:arrow_up:

pkg/compute/models/loadbalancerawscachedlbbg.go
3.31% <0.00%> (-0.21%)
:arrow_down:

pkg/compute/models/loadbalancerhuaweicachedlbb.go
4.16% <0.00%> (+0.04%)
:arrow_up:

pkg/compute/models/loadbalancerhuaweicachedlbbg.go
3.90% <ø> (+0.03%)
:arrow_up:

... and 469 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 09e37de...02264fb. Read the comment docs.

/lgtm
/approve


Feature Request: Mobile port

I notice that the app is made with Web tchnologies, is possible to port it to an android app to read files from the sd card?

It’s certainly possible.  It’s basically just node.js with an embedded Chrome browser, so anything that can provide node.js + a browser + local file access would work...

https://blog.usejournal.com/how-to-build-android-apps-with-node-js-using-android-js-2aa4643be87b may be a good starting point if anyone wants to do a PR for this.  Keep in mind you could host on a remote box and then access remotely if you are simply looking to review from your phone.


Fixed upgrade issue (1.8->1.9) with overlay-modules.

High level description including:

Allows overlay upgrades from 1.8 -> 1.9
Allows any agent configuration change (disabling mesos or docker network) to be allowed during upgrades
*Earlier the test cases were assuming that the configuration applied by the Master will always be the configuration given to the network configuration of the agent. This is obviously not true during upgrades since the overlay configuration for a specific agent is retrieved from the replicated log.
We are therefore changing the test to learn the overlay configuration being applied by the Master, and ensure that the configuration is reflected on the agent end-point.

Issues
DCOS-557
...
Checklist

[*] Included a test which will fail if code is reverted but test is not
[ ] Followed relevant code rules Rules for Packages and Systemd

If this is a component/package update, include

[ ] Change Log from last:
[ ] Test Results:
[ ] Code Coverage:

@jieyu @kaysoky @cmaloney this is ready for review.
Ran the upgrade integration tests on this PR to verify that it passes.

@mellenburg can you take a look at this?

🚢
LGTM.

Hi @asridharan what is the issue you were intending to link to? https://dcosjira.atlassian.net/browse/557 is giving me a broken link...

@lingmann sorry typo in link. Just updated the link.


Skip rarely needed maintainer tools when not available

This is a third alternative (after #17227/#17278 (CI provisioning) and #17317 (lightweight feature)) to solve the problem of missing maintainer tools autopoint, gtkdocize.
This is the fastest solution for vcpkg ports which don't really need to update to these parts of the build systems. It solves the issue both for CI and for vcpkg users.
The tools are still used when provided by environment variables (set by the portfile or toolchain file), found in the host system, or of found in matching vcpkg tools directories.

What does your PR fix?
Fixes #17057, #17098.

Which triplets are supported/not supported?
-/-

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
-/-

cc @Neumann-A for review this PR.

atk:x64-windows: Download error, unrelated

libmicrohttpd:x64-osx: Linker error, unrelated, except that both this PR and the error are related to the gettext port.
Undefined symbols for architecture x86_64:
 "_CFArrayGetCount", referenced from:
     _add_system_trust in libgnutls.a(certs.o)
     __nl_language_preferences_default in libintl.a(langprefs.o)

I assume that the missing symbol is in some CoreF... library, and a dependency is not properly carried. From config.log, the dependency exists in /Users/vagrant/Data/installed/x64-osx/lib/libintl.a, i.e. in the library created from vcpkg's gettext port.

fontconfig: Hard dependency on autopoint. This indicates an issue in this PR, because it worked before, so the new code should have found an existing autopoint program.

Maybe this PR is too invasive or too naive because it effectively pretends that these tools are available. It might be safer to touch those environment variables only in the ports which actually do not need to run these tools. OTOH, it seems to uncover hard dependencies.

fontconfig: Hard dependency on autopoint. This indicates an issue in this PR, because it worked before, so the new code should have found an existing autopoint program.

Actually, this was broken before. However, it is clear now that autopoint is a hard requirement for building fontconfig.

It might be safer to touch those environment variables only in the ports which actually do not need to run these tools.

This was picked up in #17419 (libidn2, waiting for merge) and #17420 (libtasn1, merged).
I'm closing this draft PR now. (But it gave useful insight.)


fix: verify rootDir and all roots are directories

Summary
See #9549 for background.
This could be considered a breaking change and I can print a warning instead?. Also, as mentioned in #9549, should we verify that roots exist in jest-haste-map as well? Not sure how that affects Metro, but jest-haste-map is super inconsistent in how it handles missing roots depending on whether Watchman is used and if the OS is Windows.
Closes #9549.

Test plan
Integration tests added

Codecov Report

Merging #9569 into master will decrease coverage by 0.02%.
The diff coverage is 41.66%.

@@            Coverage Diff             @@
##           master    #9569      +/-   ##
==========================================
- Coverage   65.05%   65.03%   -0.03%
==========================================
  Files         286      286
  Lines       12127    12139      +12
  Branches     3005     3008       +3
==========================================
+ Hits         7889     7894       +5
- Misses       3600     3606       +6
- Partials      638      639       +1

Impacted Files
Coverage Δ

packages/jest-config/src/normalize.ts
76.66% <41.66%> (-1.21%)
:arrow_down:

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 00e9e09...6d9e3d4. Read the comment docs.

bah, here we go https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/

Codecov Report

Merging #9569 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9569      +/-   ##
==========================================
- Coverage   65.05%   65.03%   -0.03%
==========================================
  Files         286      286
  Lines       12127    12139      +12
  Branches     3005     3008       +3
==========================================
+ Hits         7889     7894       +5
- Misses       3600     3606       +6
- Partials      638      639       +1

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 00e9e09...eb69703. Read the comment docs.


Use style.textContent

style.type = 'text/css'; is the default value
style.textContent is supported in IE9 as the standard way to set its content

https://developer.mozilla.org/en/docs/Web/API/Node/textContent#Browser_compatibility

I sometimes forget how much simpler life is when minimum support gets bumped. :)


Animations on modals

Why are there no animations on modal components? When implementing modals, it pops up so suddenly. Is the documentation on the website outdated or is this already implemented?

@coolpopo Looking at https://react.semantic-ui.com/modules/modal shows that there aren't any animations currently. Maybe you were looking at https://semantic-ui.com/modules/modal.html ?

wrap TransitionablePortal outside Modal and modal will have animations.

@thhoang99 would you have a snippet or codepen demonstration this ? I could not make it work

@hubertguillemain Ok, here you go https://codepen.io/thhoang99/pen/XYxMOX?editors=0010.

Thanks @thhoang99 I see that you actually have to force set the inner Modal's open prop to true. Perfect !

@thhoang99 @hubertguillemain have you guys found maybe a clean solution for the background of the modal not being animated?

Ok guys, just put together the fix for animating the dimmer color here https://codepen.io/jpincheira/pen/rKoYNW
Thank you @thhoang99 for your solution.

@pincheira your solution for dimmer animation very well, for my solution, i still continue use TransitionablePortal wrap outside Dimmer, but this time same your, i must interfere with css to remove background dimmer of modal.

Thank you! @pincheira

No worries @Martinnord, super glad you found it useful 👍

Both Transition and TransitionablePortal support modals as far as I have seen. I use both in my production app.

@annjawn Would you mind sharing the code? You got me super curious!

@Martinnord  here you go - https://codesandbox.io/s/zx93o93w3x

@annjawn Sorry for the late reply. It looks great! Although it would be nice to see it animating out as well. Is that possible with TransitionablePortal?

@Martinnord Yes unfortunately, transition out effect can only be achieved by TransitionablePortal. I have created a fully functional Material UI style App SnackBar using TransitionablePortal in SUIR and it works quite well.

Try Transition.Group. Here's your CodeSandbox code modified, and fully working.
<Transition.Group
          open={open}
          transition={"fade down"}
          duration={1500}
        >
        {open && (
            <Modal open={'true'}>
              <Modal.Header>Select a Photo</Modal.Header>
              <Modal.Content image>
                <Modal.Description>

                    We've found the following gravatar image associated with
                    your e-mail address.

Is it okay to use this photo?

                </Modal.Description>
                <Button onClick={this.openModal}>Click me!</Button>
              </Modal.Content>
            </Modal>
  )}
  </Transition.Group>

Code Sandbox - https://codesandbox.io/s/14nk96xx3j

Thanks for the quick answer. I looked at the code and tried to apply it to my. Unfortunately I still have no luck with this. The transition just wont do its job. I understand it's hard for you to pinpoint out what I'm doing wrong, but this is my current code:
<Transition.Group
    open={openStartMenuModal}
    transition={"fade down"}
    duration={400}
>
    {openStartMenuModal && (
        <StartMenuModal
            open={openStartMenuModal}
            closeModal={this.closeModal}
            shopMenu={shopMenu}
            handleSelectedBundleProduct={this.handleSelectedBundleProduct}
            handleTabChange={this.handleTabChange}
            handleProductToCart={this.handleProductToCart}
        />
    )}
</Transition.Group>

Really weird!

@annjawn When having the "actual" modal inside of the Transition.Group it works fine. But when I tried to break it out to its own component the transition no longer worked. You can try by uncommenting some code. https://codesandbox.io/s/zqzv2y4923

Okay.. So after some investigating in Semantics own source code I've come across this. At this line in TransitionGroup, https://github.com/Semantic-Org/Semantic-UI-React/blob/master/src/modules/Transition/TransitionGroup.js#L111. They essentially just wrap the child in a Transition. So I went into Transition.js. And noticed at this line here, https://github.com/Semantic-Org/Semantic-UI-React/blob/master/src/modules/Transition/Transition.js#L289. They cloneElement(this.props.children, ...) and tac on some computed classNames and computed styles. So their built in Modal component probably already knows how to accept this. But my wrapper didn't have that. So I just had to add className and style to my StartMenuModal props and put them on the Modal.
As shown here, https://codesandbox.io/s/zqzv2y4923

Yes, I was actually thinking that there must be something with the wrapped component that you are using. But glad that you were able to resolve this.

I'd love to be able to add fade in/out animation to my modal which currently isn't possible yet, please keep this thread open. The workaround with the TransitionablePortal is extra work and visual glitches occur.

AnimatedModal.jsx
import React from 'react'
import { TransitionablePortal, Modal } from 'semantic-ui-react'

export default function AnimatedModal(props) {

    function handleClose(e) {
        setTimeout(() => document.body.classList.remove('modal-fade-in'), 0)
        if ('onClose' in props) {
            return props.onClose(e)
        }
    }

    const { open, onClose, ...innerProps } = props

    return (
        <TransitionablePortal
            open={props.open}
            transition={{ animation: 'scale', duration: 400 }}
            onOpen={() => setTimeout(() => document.body.classList.add('modal-fade-in'), 0)}
            onClose={handleClose}>

            <Modal open={true} onClose={handleClose} {...innerProps}>
                {props.children}
            </Modal>
        </TransitionablePortal>
    )
}

AnimatedModal.css
.ui.dimmer {
  transition: background-color 0.5s ease;
  background-color: transparent;
  opacity: 1 !important;
}

.modal-fade-in .ui.dimmer {
  background-color: rgba(0,0,0,.75);
}

AnimatedModal.jsx
import React from 'react'
import { TransitionablePortal, Modal } from 'semantic-ui-react'

export default function AnimatedModal(props) {

    function handleClose(e) {
        setTimeout(() => document.body.classList.remove('modal-fade-in'), 0)
        if ('onClose' in props) {
            return props.onClose(e)
        }
    }

    const { open, onClose, ...innerProps } = props

    return (
        <TransitionablePortal
            open={props.open}
            transition={{ animation: 'scale', duration: 400 }}
            onOpen={() => setTimeout(() => document.body.classList.add('modal-fade-in'), 0)}
            onClose={handleClose}>

            <Modal open={true} onClose={handleClose} {...innerProps}>
                {props.children}
            </Modal>
        </TransitionablePortal>
    )
}

AnimatedModal.css
.ui.dimmer {
  transition: background-color 0.5s ease;
  background-color: transparent;
  opacity: 1 !important;
}

.modal-fade-in .ui.dimmer {
  background-color: rgba(0,0,0,.75);
}

 <AnimatedModal open={myOpenFalseVariable} size='tiny' onClose={props.handleClose} closeIcon>
    <Modal.Header>My Title</Modal.Header>
   <Modal.Content>
   ....
</AnimatedModal>

hello?

Would be nice to be able to add transition to Popup's. The examples for non-React Semantic UI are much nicer: https://semantic-ui.com/modules/popup.html

any examples for modal transition for fade left animation. please help me with this


pip install can't find 'requirements.txt'

Using python 3.5.x from anaconda. I get the following:
(mkdocs-environment) BusterBoy:wellzesta-docs jmr$ pip install mkdocs-rtd-dropdown
Collecting mkdocs-rtd-dropdown
  Using cached mkdocs-rtd-dropdown-0.0.9.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/g_/xb36_7gn2zg21qz3_rlt6k9w0000gp/T/pip-build-mviy3t01/mkdocs-rtd-dropdown/setup.py", line 5, in <module>
        with open("requirements.txt") as data:
    FileNotFoundError: [Errno 2] No such file or directory: 'requirements.txt'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/g_/xb36_7gn2zg21qz3_rlt6k9w0000gp/T/pip-build-mviy3t01/mkdocs-rtd-dropdown/

I git clone the repo and did: sudo python3 setup.py install
then it worked fine.

Not even a setup.py install works for me on Python 3.6 with Anaconda.

Thanks for the report. It looks like I left requirements.txt out of the Manifest.
I fixed it and pushed out an updated version.


Where To Post Sample Code

Hi @mpost (sorry I mentioning you), where can we post sample code to? For example, I have JS code to create card view (using composite), where do I post it so other may use it? I Think using issue will not be appropriate.
Thanks.

@jokorivai You could create a gist and link it here so google will pick it up when people search for "card" and "tabris".
In addition you could "pin" your snippet on the scratchpad and make it publicly available so that other people can find it: https://tabrisjs.com//scratchpad/

ok thankyou @mpost

For anyone keeping score at home, the link to publicly available scripts is at https://tabrisjs.com/public/scripts


Couple things...

In the installation section, please go into detail on how to install this and where it will show up. For instance, being a linux and webmin noob, I would do something like this:
From the Webmin Interface, click through Webmin -> Webmin Configuration -> Webmin Modules
Select the "From ftp or http URL" option and enter this URL: https://github.com/Real-Gecko/filemin/raw/master/distrib/filemin-0.9.6.linux.wbm.gz
After it successfully installs, you will see the "Filemin File Manager" module under the "Others" menu.
The other thing is ... after you upload a compressed file (.tar), how do you uncompress it through Filemin?

I'll add usage tips in next release. Filemin will be in next Webmin release, so it'll be installed by default, no more need to provide installation procedure :)

Oh nice! Looking forward to it!
Also, I figured out how to uncompress .tar files ... rename it to .tar.gz


Blended Pairwise

Based on https://arxiv.org/abs/2110.12650

this is ready to merge now if the CI passes.


[Proposal] With all class names, find a balance between consistency, ease of use for newcomers, and ease of customization

I've seen this discussion pop up in a bunch of other threads both here and on Twitter. Just wanted to open a dedicated issue so we can give it proper consideration as we approach Tailwind 2.0.
General idea: people have proposed moving to linearly incrementing, number-based class names (text-1, text-2, etc.) instead of word-based class names (text-xs, text-sm, etc.) and non-linearly incrementing number-based class names (m-10, m-12, m-16, m-20, etc.).
I've experimented a lot with this and have given some thought to the trade-offs. From what I've seen, we all agree that these things are important:

Class names should be reasonably consistent across all of Tailwind
Tailwind should be easy for newcomers to use
Tailwind should be easy to customize

And here's how the class naming systems stack up in terms of those priorities:
Word-based
Pros:

Arguably the easiest naming system for Tailwind newcomers. T-shirt size classes like text-xs in particular feel super intuitive.
Easy to be semantic, e.g. tracking-wide and leading-relaxed.

Cons:

Hard/impossible to find names for custom, in-between values (xs.5? small-and-a-half?). Right now, this is why spacing utilities completely ditch the words altogether and go with a scaled number-based approach.
Easy to fall into the trap of making words inconsistent across different properties. Case in point: text-lg, tracking-wide, and leading-relaxed are all next size up from the default size.

Numbers that always increment by 1 (or 100)
Pros:

Arguably the easiest naming system once you get past the initial Tailwind learning curve and get acclimated to the Tailwind way of designing things.
You can use -0 to "unset" all properties, instead of trying to remember which should be -none and which should be -0.
Very easy to name your custom values.
Extremely easy to guess the "next" class when you're designing and just need to bump the size up or down for any given property. mt-10, mt-12, and mt-16 become mt-8, mt-9, and mt-10.

Cons:

Not always easy to remember where the "default" value is. When you apply this naming scheme to all properties, the default font-size becomes text-3, the default border radius becomes rounded-2, and the default shadow becomes shadow-1.
Not easy to guess how much your design will be affected by incrementing the class name. With mt-10, mt-12, and mt-16, you have a sense that you're adding progressively larger amounts of spacing, but with mt-8, mt-9, and mt-10, you'd expect linear increments in the underlying spacing values, and you might be confused when that doesn't happen.
Sucks for opacity. Don't ever make me use something other than opacity-25 for opacity: 0.25.

Numbers that always increment based on the change in the underlying values
Pros:

Keeps you grounded in how much size you're adding to a design. mt-10, mt-12, and mt-16 make it clear that you're adding progressively larger amounts of spacing.
Very easy to name your custom values
You can use -0 to "unset" all properties, instead of trying to remember which should be -none and which should be -0.

Cons:

Sometimes difficult to remember, even for Tailwind veterans.
Big learning curve for Tailwind newcomers, who need to spend a lot of time in the docs until they start to remember that mt-32 exists, but mt-36 does not.
Keeps you grounded in how much size you're adding to a design. This is both a pro and a con—the downside is that it forces you give some thought to the underlying values in Tailwind's design system, which are implementation details for Tailwind users who aren't customizing the system.

I've been thinking about this a lot the past few months. There's a certain amount of granularity that string-based class names don't provide. In theory, it's pretty easy to move toward number-based class names, but it comes with a catch: the scale (i.e., multiplier) is going to be different for each property (e.g., margin versus letter-spacing). Furthermore, some value ranges are bounded (e.g., opacity), so they'd likely need to be handled differently.
That being said, I've been incrementally adopting number-based based classes on my new projects out of necessity and it's been working great, but only once you get familiar with the different scales. I can't imagine the new developer experience is too great using this approach, but I could be wrong. Let's just take line-height, letter-spacing, and opacity as an example:
{
  letterSpacing: {
    // Formula: 200 * letterSpacing (e.g., 200 * 0.015em -> 3)
    '0': '0',
    '1': '0.005em',
    '2': '0.01em',
    '3': '0.015em',
    '4': '0.02em',
    '5': '0.025em',
    '6': '0.03em',
    '8': '0.04em',
    '10': '0.05em',
    '12': '0.06em',
    // and so on
  },
  lineHeight: {
    // Formula: 20 * (lineHeight - 1) (e.g., 20 * (1.2 - 1) -> 4)
    // Question: what do we do for line-height < 1?
    '1': '1',
    '2': '1.1',
    '3': '1.15',
    '4': '1.2',
    '5': '1.25',
    '6': '1.3',
    '8': '1.4',
    '10': '1.5',
    '12': '1.6',
    // and so on
  },
  opacity: {
    '0': '0',
    '20': '0.2',
    '40': '0.4',
    '60': '0.6',
    '80': '0.8',
    '100': '1',
  },
}

In this case, the numbers are consistent with theme(spacing) (with the exception of opacity, which makes sense to keep it that way), but the scales are defined completely differently. There's definitely some mental math gymnastics going on here when you're using them, but if you've got well-defined components (e.g., .type-h1) that inherit these properties and you're using them globally, you only need to think about it once and then simply apply it everywhere.
On a more philosophical note, I find that the front-end development process happens in this order:

Develop the supplied design using pixels as your guide
Fill in the blanks with what looks good using feelings as your guide

So once the pixel-perfect design has been coded, the developer needs to go with their gut. That's where having a consistent yet granular scale comes in super handy. This is especially true for properties like transition-duration, where a small change can make or break an experience.
Overall, I really like the idea of making Tailwind class names number-based as I find it incredibly useful, but I do worry about the initial developer onboarding experience a bit.

Hey folks! Really appreciate the level of thought put into this.
If I've learned anything working in and with open-source though it's that end-users value stability/backwards compatibility extremely highly, and breaking changes need to correct some really fundamental problem that frustrates/limits a large portion of the user base to be worth it.
Put another way, just because a breaking change is an improvement, it doesn't mean it's automatically worth doing — in fact in my experience working on Tailwind itself a breaking change has to be a really significant improvement to even be worth considering, because even if a class name isn't perfect people will still learn it and get used to it and it becomes a really superficial "problem". I went down this road trying to improve the leading and tracking utilities from 0.x to 1.0 and ultimately after weeks of hashing it out with the community it made the most sense to just stick with what we had and live with it because it just wouldn't have improved anyone's lives enough to be worth adding the extra friction in upgrading to 1.0.
So for that reason I'm not planning to make any drastic changes like this to the current naming conventions until it feels like it's a really huge problem that's causing people lots of pain, because I believe the silent majority care more about things being stable than being perfect.
On the same note I decided recently that I'm actually not going to push forward with a v2.0 any time soon, and will instead just include the transforms, transitions, and grid features into v1.2 so folks can upgrade without having to worry about anything breaking. Ideally I'd like to get the new {color}-50 values and the small color palette adjustments into a minor release as well, but since that will affect how people's projects look I'm going to eventually open another discussion about that and find out if people are actually worried about that from a "breaking change" perspective, especially since it won't actually "break" anything since no class names are changing.

Sounds good to me—glad to have this issue to refer back to, since this topic seems to pop up every time a new core plugin is introduced.
For anyone stumbling across this who's really gung-ho about linear numeric naming, I had some fun exploring what kind of NPM package would make it really easy for users to configure this kind of stuff on their own—here's what I came up with.
And here's the source code for anyone who wants to use a similar approach to create their own custom naming conventions 🤖


Uploaded cloud support

Added cloud support
Added ER integration with IC
Updated Better error handling
Removed delete observable functionality

stale


Add "in" operator

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

Files
Coverage Δ

os.go
91.66% <100.00%> (ø)

compare/compare.go
71.42% <3.57%> (-28.58%)
:arrow_down:

... and 2 files with indirect coverage changes
:loudspeaker: Thoughts on this report? Let us know!.


Sidebar Collection: Search and Sort

Discussed in https://github.com/tinacms/tinacms/discussions/4258

Originally posted by amankumarrr October 15, 2023
As we continue to add collections, it can become challenging for users to search through them. To improve the user experience, we recommend implementing the following features for easier navigation.

Search option on the top of the panel
Sort option to sort it by its label

Figure: Tina's sidebar n number of collections

See screenshot from Forestry.io.  We allowed users to include horizontal dividers (not show in screenshot) or headings in the sidebar.


wide FM (standard radio service) cannot be received by communication receiver

wide FM (standard radio service) cannot be received by communication receiver.
This issue is known since the beginning of QS.
For instance when we set to 104,90MHz (local stereo wide FM radio service in my area) then we are not able to hear it clearly.
Demodulation is awfull.
The question is why. Wide band, signal strenght and FM demodulation should be enough to hear it but it is not.
In the same place I am able to hear that station perfectly by means of RTL-SDR or build in QS separate radio service receiver.

Not sure what you're asking ?
FM broadcast deviation is like 50kHz, narrow band comms deviation is 5kHz or less.

Aaa... ok. If standard radio service has 50kHz of deviation then it makes sense on 25kHz wide band of communication chanel

If you want to listen to FM broadcast station, you need to use the wide band FM radio.

ok, issue cleared

Some countries have already stopped using the VHF FM broadcast band for broadcast radio, it's now used for others things.


PlaceholderText not showing

Describe the bug
It seems that beyond 3.0.4 the PlaceholderText no longer shows for me.
To Reproduce
default behavior.
Expected behavior
the place holder text should be visible when the textbox is empty
Screenshots
No response
OS version
OS: Windows 11 Enterprise N
Version: 23H2
.NET version
4.8.1
WPF-UI NuGet version
3.0.5 or later.
Additional context
No response

Please provide more information.

Odd... I just tried updating the Version to 3.0.5 again and it seems to be working now.
I am not sure what was going on, but when I submitted the bug 2 weeks ago, I switched back and forth between versions 3.0.5 and 3.0.4 several times to verify the bug. Whenever I went to version 3.0.5 the 'PlaceholderText' wouldn't display. It was just showing an empty Textbox. I used just the default Textbox shown below to test it.
<ui:TextBox PlaceholderText="This is a Test" Text=""/>
If it starts happening again I will update this with any new information.


Duplicate RefGenome uploads - more event listeners issues

This happens after doing delete some reference genomes and then trying to upload without refresh. Again, the fix is similar to before with making sure to properly remove event listeners.

Fixed in 302ac7b5c52e57a7171a322087009ca10c01b6e1. (Note typo in commit message).


Error rendering tiles containing CJK text at z6+

As soon as you view China, Hong Kong, Taiwan, North or South Korea, or Japan at zoom level 6 or above, MapLibre GL JS throws the following error and stops rendering tiles until you reload the page:
Uncaught RangeError: mismatched image size
    xa image.js:11
    wa image.js:61
    clone image.js:67
    getGlyphs glyph_manager.js:101
    asyncAll mat4.js:44
    getGlyphs glyph_manager.js:48
    asyncAll tile_request_cache.js:136
    asyncAll tile_request_cache.js:136
    getGlyphs glyph_manager.js:39
    getGlyphs pos_attributes.js:2
    processTask actor.js:182
    receive actor.js:132
    EventListener.handleEvent* actor.js:49
    E2 dispatcher.js:45
    Yt style.js:68
    _updateStyle map.js:967
    setStyle map.js:945
    Map map.js:256
    ibaUJ americana.js:284
    newRequire index.fe42b686.js:71
    <anonymous> index.fe42b686.js:122
    <anonymous> index.fe42b686.js:145
image.js:11:14

This issue was fixed in maplibre/maplibre-gl-js#917, which made it into v2.1.2. However, Americana is on a fork of MapLibre GL JS for maplibre/maplibre-gl-js#716. We need to update GL JS in order to unblock enhancements related to East Asian countries.
Reproduces in Firefox 96 on macOS.

Fixed in #194.


[USRGeneration] For clang macro USRs, use the more general API that doesn't require a PreprocessingRecord.

@swift-ci smoke test and merge


feat: add identifier casting

Hello 🙂!
Following https://github.com/unjs/magicast/issues/37, I added Identifier casting.
(I'll add other after)

I made the builders.raw tests inside a folder to make smaller files
I added a vitest-ui (because that's awesome to work with!)
I added \u0020 in errors.test.ts to stop my IDE from removing the trailing space
I didn't add a builders.identifier function, as you can create an identifier with builders.raw directly

Nice, thank you!


crashes

Describe your bug here.
crashes midway the song. idk why. even in zanta taiko, it crashes when its at tom's turn
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
yes but it also crashes when i put it without edited

This is to look at the creator, not here

Can you actually describe how and when this "bug" is happening because just saying "it crashes" doesn't help at all

https://user-images.githubusercontent.com/54176781/149769208-33adf223-d729-4b38-9b58-8482754237f3.mp4
btw didnt edit anything

Can you actually describe how and when this "bug" is happening because just saying "it crashes" doesn't help at all

Isn't that a problem with the mod
Why are you reporting it here

Isn't that a problem with the mod Why are you reporting it here

then how does people play with the mod?
i dont understand
its on all the mods i play

Yes but it is the creator problem, not the engine.

Isn't that a problem with the mod Why are you reporting it here

then how does people play with the mod? i dont understand its on all the mods i play on psych engine 0.5.1

the taiko script is by me and it's buggy. only ask questions pertaining to BASE psych engine itself on here.


Admin work queue

View a list of items that need admin attention. Including (but not limited to):

New scores
New records
New badges
Incomplete badges

Use DI tags + approval repositories


tests: remove xfail

https://github.com/fsspec/adlfs/pull/333 has been merged and released.

Closing, as we will likely need to change the test framework to remove xfail.


Exceptions

Please flesh out the Exceptions section: what exceptions might be thrown, and what do they mean?   In my case, I can select a file fine using PickSingleFileAsync, but when I use GetFileFromPathAsync I get System.UnauthorizedAccessException, and I have no idea why.

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

ID: f1a0b142-3819-3929-bc93-c4d8e0598978
Version Independent ID: 932a8fe2-dc4e-ade9-e67d-45897840c037
Content: StorageFile.GetFileFromPathAsync(String) Method (Windows.Storage) - UWP app developer
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.storage.storagefile.yml&version=GBlive&_a=contents
Product: windows
Git Login: wdg-dev-content
Microsoft Alias: wdg-dev-content

@ginami
Please assign someone to this issue who can actually address it. It is a) unacceptable that a public API method can throw undocumented exceptions and that b) even after it was reported months ago, ZERO progress has been made.
I don't want to criticize your system here (and I really can't since I'm not seeing the big picture), but I do wonder whether you guys actually have a system in place which checks if the assigned authors actually do comment/work on "their" issues? Too often, once someone has been assigned to an issue, it is left behind to rot in the grave while seemingly no one at Microsoft seems to care.
Appreciate your comment!

Hi @Felix-Dev. Thanks for filing the issue. I am very sorry that we did not respond to it in a timely manner. We are working out our processes for ownership of issues, particularly when ownership of the associated content changes, as was the case here. Please accept my sincere apology for letting some things slip through the cracks. We do our best to address issues that come in, but we need to do better.
To you specific question about an Exceptions section in this document, generally speaking, Windows Runtime APIs are designed not to throw exceptions of the kind that we expect deployed code to handle at runtime. That's why the docs are not in the habit of mentioning them. However, there are some cases where that rule is not followed. We have sent your findings to the product team and will respond back with their guidance, and then we’ll work with them on whether/what to document here regarding exceptions.

@jillre,
thank you for your fast response! Seeing the number of issues filed all the time and that you guys also have your own priorities (writing new API documentation,...) I can see that sometimes it might be a bit overwhelming for the team and some issues, especially in the cases you mentioned, end up being forgotten.
It's nice to see that you are aware of some of the causes for the issue-backlog! And just to clarify, I don't demand every issue to be fixed/worked on immediately after it was filed (which would be a huge demanding task coupled with all your other work). Just, a timely comment by a Docs team member if the issue is being looked at (or not being worked on for whatever reason) would be appreciated a lot 🙂
As for the specific question: The issue for me here stemmed from the fact that a rather similar method has its exceptions detailed whereas it is missing for this specific method. See StorageFolder.GetFolderFromPathAsync(). So for the sake of consistency I was advocating to include thrown exceptions for this particular method too. (I suspect, given the close proximity of these two methods, that they are (nearly) identical.)
Thank you again for your timely response!
Felix

@Felix-Dev thanks for the link to StorageFolder.GetFolderFromPathAsync(). That's helpful.


Configure DefaultMaxRetryAttempts

Hello,
this line https://github.com/vulcand/oxy/blob/a0e9f7ff10402f5912abd9851659dec0988aa2c2/buffer/buffer.go#L204 effectively limits the number of attempts to 10, irrespective of the retry predicate specified. Am I missing something or is there a way to configure the max number of attempts?
Thanks! 😃

It seems to be a "prehistorical" mistake :smile:, I fixed the problem with the predicate in #234.

@ldez hello again, I saw the PR with the fix was reverted - what was the reason behind it?

Hello, because it was a misunderstanding, the code is right.

@ldez does it mean that the number of retries should be limited to 10 by design?

@ldez hello, could you maybe elaborate on the misunderstanding? Is it indeed intended cap the number of retries at 10? Or can the number of retriews be higher as well (and I simply didn't see how to configure this)?


removed create_at and updated_at colums as per Doc issue 333

@iriberri , part one Docs issue#333- https://github.com/CartoDB/docs/issues/333.  Please sign-off if correct.

@iriberri , removed comma as instructed.  Good?

Awesome! Thanks :)

@rochoa , Carla and I made a small doc update (related to Docs issue#333).  Since you are the owner of this repo, please merge this branch.

Thanks for keeping docs clean & tidy! :smile:


Evaluation criteria

Hi Jeremy,
Thank you so much for sharing the boltz1 with us!
Currently we are trying to predict some protein-ligand complex cases, we got the results and successfully downloaded it, but when we tried to find the Evaluation criteria/ scores, we got nothing.
So how to evaluate our results?
Thank you so much!

We will be releasing out confidence model very soon!

Has now been released in v0.3.0!

Excited! May I ask a question that how to evaluate the score, like, is it very confident, confident or very low? or how to visualize it ? Thank you so much!
confidence_score0.8144504427909851
ptm0.6312305927276611
iptm0.5645926594734192
ligand_iptm0.4999026358127594
protein_iptm0.5855854749679565
complex_plddt0.876914918422699
complex_iplddt0.7071197628974915
complex_pde1.8762571811676025
complex_ipde11.478374481201172


[BEAM-5706] Revert 324f0b3e3c (pull request #6564 from udim/pubsub-0-35-4)

Please add a meaningful description for your change here

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

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


Grav 1.4.6/1.5.0-beta.1 causes preview error in admin editor

After Grav update to 1.4.6:
Go to pages in admin plugin, try to edit and click on preview tab:
Error message:

Preview looking for ...json.twig  and not for ...html.twig template!
This is definitely a grav error and not an admin issue.
I did all updates first (grav, admin, form, login). --> preview error
Then installed backup and did only the grav update...--> preview error
Seems related to:
https://github.com/getgrav/grav/pull/2044

Could be this? https://github.com/getgrav/grav/pull/2044

Oh you said that already. :)

Ok, fixed... one liner.. see above...

While that fixed the preview, it reverted the original issue.. better fix is:
Grav: https://github.com/getgrav/grav/commit/dfed333e1b1c36afa6e74b7a62c332057bbdb7ac
and
Admin: https://github.com/getgrav/grav-plugin-admin/commit/dc9b6daaa34bb0bca5e7883c8873d21aba850e3c


MNT: Re-render the feedstock [ci skip]

Hi! This is the friendly conda-forge-admin automated user.
I've re-rendered this feedstock with the latest version of conda-smithy (1.6.0) and noticed some changes.
If the changes look good, then please go ahead and merge this PR.
If you have any questions about the changes though, please feel free to ping the 'conda-forge/core' team (using the @ notation in a comment).
Remember, for any changes to the recipe you would normally need to increment the version or the build number of the package.
Since this is an infrastructural change, we don't actually need/want a new version to be uploaded to anaconda.org/conda-forge, so the version and build/number are left unchanged and the CI has been skipped.
Thanks!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

CircleCI isn't building because pull/1 is a blacklisted branch??? What is going on? @conda-forge/Core

conda & conda-build upgrade, see https://github.com/conda-forge/conda-forge-build-setup-feedstock/issues/40

Not sure how this relates to upgrading conda-build version 2. Could you please elaborate @scopatz ?

I guess this is a very old feedstock that hasn't been re-rendered previously. In the 1.0.0 release of conda-smithy, we disabled any CI from building that was unused. We did this by using skip to determine which CIs would be skipped and some cleverness with the CIs to convince them not to build. This feedstock skips non-OS X builds as such only Travis CI is enabled.
Though very strangely we are seeing a CircleCI status here, but it does appear to have skipped correctly. Not sure why the status is present. Could be a bug with CircleCI webhooks. Could have come about by trying to restart CircleCI. Not sure which if any of these caused it. While I have seen this maybe once or twice since conda-smithy version 1.0.0 came out, it has been exceedingly rare. If you keep seeing it with new PRs let us know, otherwise would just recommend ignoring it.

Oh, that was just my guess for why it would be broken.

Oh ok. Just wanted to make sure our upgrade process wasn't getting totally out of hand. 😄

Sorry for shooting from the hip.  Clearly I am bad at multitasking :)

Oh right I forgot Circle shouldn't even be running on this feedstock.  I'll merge this then. I don't anticipate any PRs on this repo for a while, except for rerenders.

Hmm, just got an email that I was subscribed to conda-forge/iterm2-tools-feedstock notifications on CircleCI. @jakirkham

Yeah, I have gotten a bunch of those of late. Didn't use to. Figure they changed some (default) settings somewhere. Think it also happened after I merged PRs. Haven't looked into unsubscribing yet. Hopefully shouldn't matter when CircleCI is not used.
Would also add that we still enable all CIs on all feedstocks. We merely disable them using file level changes. This is done mainly for cases where maintainers may want to later enable the other CIs. Also it is just easier to maintain.


Add TLS support

Add TLS support to the canary. Currently the canary config contains an environment variable to enable TLS. However it is disabled by default and not implemented even if enabled.

To be precise, this issue is about:

enabling TLS connection to a Kafka cluster (providing a CA certificate to the canary)
enabling TLS mutual authentication (providing client cert and key to the canary for authentication)


Update cats-effect, cats-effect-testkit to 3.4.9

About this PR
📦 Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-testkit

from 3.4.1 to 3.4.9
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #45.


chore: remove betamax and upgrade deps

We've been waiting for this. Thank you so much!

This is great work!


feat: compute() function

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

87 of 103 (84.47%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.4%) to 95.584%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/rx-effects/src/compute.ts
87
103
84.47%

Totals

Change from base Build<PHONE_NUMBER>:
-4.4%

Covered Lines:
449

Relevant Lines:
465

💛  - Coveralls


Update Tip Calculator.py

Not valid!!

I also want to know about the math followed for the calculation of tip. I couldn't get it!


[ADDITION] Guess The Color game

Description
GUESS THE COLOR when the RGB value is given
We will be having easy and hard level
Blocks of different colors are given
The RGB value is given and we need to guess the color and select the correct box
Screenshots
No response
Additional information
Assign me this @raj03kumar @cleveranu @Shreyaar12

@Shreyaar12 @raj03kumar Assign me this issue

Hi @linga66 , i am assigning this task to you. Kindly complete within a week. Good luck for your work!


Improvements in table in neetoEditor

Ref: https://github.com/bigbinary/neeto-kb-web/issues/5677
@gaagul _a
//cc @AbhayVAshokan

This issue needs to have certain priority as a customer has reported a ticket. https://neetokbhelp.neetodesk.com/desk/tickets/63
priority _t


New Version of UBUNTU 18.04 needs over 5GB RAM

I have been running the new version of 18.04 using Quick Create in Hyper-V and even in idle state it required over 5-6 GB of  RAM.  This is odd - even Windows 10 Pro idles at around 3GB or less.  Can anybody explain why?

Presuming you are looking at the Assigned Memory, and presuming by "Idle" you mean that you have a gnome session running (ie logged in) but have no applications going and no extra services loaded. With the memory buffer, and its infrequent allocation times... without modifications, this can be expected.
Ubuntu desktop minimal install + vm tools + minimal services (ssh,rdp,vnc,...) + ui extensions + a windows 10 theme, it doesn't break my minimum 2000mb startup memory before login.
Logged in, it uses around 4gb, then comes down to 2.4gb after logging out. Due to the Memory Buffer, the Assigned Memory (when having only just logged in) does seem to be a bit high, but is not a bug with Microsoft's vm tools, or even the dynamic memory. (check top for your gnome session) Its a being a piggy. I don't like it either. But I still use it for stuff, and expect it. There are some tweaks that can be done to help, but not anywhere near as much as you might need.
Here's what I say,

If you want a full desktop experience, and not have leaner windows-side usage, buy more ram, or just setup another physical or externally hosted host. This could cost, I get it, it is what it is.
If you want a low ram gui, consider a different shell. You don't need to reinstall the OS either, just select installed ones from the login screen. Xfce anyone? Some people can be fooled by small distros' default shell-themes, but there's lots of eye candy no matter how small you go. opendesktop.org , deviantart.com ...
If you want the base OS's memory usage to be lower, use a lighter linux distro.
If you just need to run some applications on the ubuntu system - like if you were testing an application or using it like an OS on-demand - you have more options, like making your own X session, openbox, or X over the network or even X forwarding over ssh. (running without a shell)

A warning though, if Enhanced session is what you need, in ubuntu or an os with a compatible xrdp compilation, you are going to need to customize the xrdp startup scripts for your shell, and potentially have to deal with any issues with session management (dealt with by sesman in the current Microsoft scripts). I'm stumbling down this path right now.

This repo is being archived, so closing this issue.

This repo is being archived, so closing this issue.


MTU size difference between global virtual network peering and peering in the same region

We discovered by accident that there is a difference in MTU size for global virtual network peering. I didn't find this anywhere in the documentation.
We have two regions connected and when I do a ping test with -s (size of packet) parameter the global virtual network peerings works up until a MTU of 1472 bytes, whereas a ping to a machine via peering in the same region is more or less unlimited (tried up to 9000 bytes).
Please update the documents to indicate this limitation for global virtual network peering.

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

ID: 457b3ba7-7ac5-93be-981c-677553ad39dd
Version Independent ID: 18182311-9919-ac93-0d13-de8b05a986a7
Content: Troubleshoot virtual network peering issues
Content Source: articles/virtual-network/virtual-network-troubleshoot-peering-issues.md
Service: virtual-network
GitHub Login: @v-miegge
Microsoft Alias: kaushika

Or for clarification: Not only is the MTU size lower in global virtual network peering, it also seems that the connection does not support fragmentation.
We see this for UDP traffic only, TCP is not affected.

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

@ffloimair Thanks for the feedback! I moved this Issue to the Peering Overview Doc. I have assigned the issue to the content author to evaluate and update as appropriate.

@altambaw who owns this now

#assign:@altambaw

fyi, the maximum "ping size" is 1472 (1500-20 IP header - 8 ICMP) when the mtu is 1500. this is expected as azure supports 1500 mtu. the fact that you might see more mtu in places doesn't mean it's supported. @altambaw fyi

I'll work with @atambawala to review this

Peering does not restrict or impact MTU, and there is no difference between Global Peering and In-region Peering in the context of MTU size support. Higher MTUs may work based on the type and settings of the VM NIC (eg: setting jumbo frames enables MTU of 4K without fragmentation). In the end, supporting larger MTU size would depend on the VM NIC settings and network infrastructure, but by default Azure guarantees support for 1500 MTU.

#please-close


Changed .vsixmanifest to support Visual Studio 2019.

I really love this extension, so I am trying to contribute with #188 , following this article: https://blogs.msdn.microsoft.com/visualstudio/2018/09/26/how-to-upgrade-extensions-to-support-visual-studio-2019/
As said there, only changing the .vsixmanifest may work things out. I couldn't test the extension locally because I failed to setup the environment to debug, so if someone could run it prior to accepting, would be greatly appreciated!
Sorry if I did something wrong in regards of the pull request, I'm unexperienced with GitHub.

Yeah if someone can solve this before April when VS2019 goes live I know it'd help my team. We are all about the OpenCover and we all like what this extension brings to Visual Studio!

Gave you tested this with the released 2019? It complains about missing CoreEditor for me

Even with this manifest, it does not seem to identify VS 2019. Something more is needed for this extension to work. I have tried to do some investigation, but can't seem to find out what is preventing the extension to identify VS 2019 as a valid installation target.

VsixUpdater(https://github.com/axodox/VsixUpdater) works to override these tags when make .vsix file.
when I remove this nuget package and build, I could install and run in VS2019.
...perhaps this is true way that fix VsixUpdator to support VS2019.

r-matsunaga you are right :-) I also managed to make it install on VS 2019 after removing the VsixUpdater. It looks like that module is overriding what is entered in the manifest file, and forcing the module to not identify VS 2019 as a valid target. Thank  you very much for the tip.

Is there a released VSIX somewhere? I can't build AxoCover locally :/

I have uploaded my compiled vsix to dropbox: https://www.dropbox.com/s/1s8oodc4rm3f8fc/AxoCover.vsix?dl=0
It seems to be working fine. Only issue is the yellow bar on the top upon startup, saying that it will not be compatible with future versions of VS.

I will look into this over the weekend

I have created VSIX updater to maintain VS2012 compatibility (still used at my company by some people pn legacy projects) and to decrease VSIX size. I have updated the VS version there. Nuget is still doing validation, so I will have to wait some time to rebuild AxoCover.

Made this build: https://github.com/axodox/AxoCover/releases/tag/master-1.1.399
I am abroad right now, so I do not have a full dev env for this, can you check it with VS2019?

I checked again it seems that the original reason for VSIX updater - that it was not possible to build packages which are compatible from VS2012 to VS2017 is not a problem anymore, but I would still keep it for its compression ability. I have updated it, and the VSIX manifest, so now new builds should work on VS2019. For the async loading further work is required.

Please check this build on VS 2019 and 2012 (and between :D): https://github.com/axodox/AxoCover/releases/tag/master-1.1.400

The build works fine on VS 2019, I even don't get the yellow warning about deprecated plugin stuff that came up with the other vsix :-)

I will wait a bit for more confirmations, and possible error reports. Until that you may use the above build. If everything is fine I will push this out to VS marketplace in a few weeks.

Hi,
Tested the previously mentionned build on VS 19 (Version 16.1.16) and it works fine, except warning from VS saying : "Visual Studio did not load one or more extensions that were using deprecated APIs" since i added the extension ...
Great work none the less, really appreciated !

Hi all, whats the latest with this PR?

Bump

Can it be done again for VS2022 Would be nice


[BEAM-7526] Fix toBeamValue logic in BigQueryUtils

BigQuery arrays are represented as lists of maps where each map contains the element value under a key named 'v'. During the work to add schema support to BigQuery reads (BEAM-6673), this logic was changed assuming it was a mistake.
This PR reverts the above change.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @tvalentyn
I think this PR should fix the post commit tests in the SQL module. I couldn't run the tests myself to make sure because they require GCP credentials. Is there a way to run them without actually committing to master?
cc: @reuvenlax

@charithe it is run sql postcommit command to the bot

run sql postcommit

This breaks my code.  BigQuery returns an array whose elements are not organized this way.  The elements are simple maps, if array of records, or array of base types.  Should I file a ticket?

Yeah, file a ticket here with details, if you have access, and reach out to<EMAIL_ADDRESS>


Add a flag to force a restage after bind/unbind service instance

Solution to Story [82140190]
As of now user has to restage an app with 'cf restage SOME_APP' command after
binding or unbinding to ensure bind/unbind env variable changes take effect.
With --force-restage flag , User has option to restage an app with bind/unbind itself.
Note: Currently we have not handled this flag for if its already bind. If you want to handle that situation we are ready to change.

Thank you for your continuous contributions to the CLI.
I'm not clear on what problem this feature tries to solve. I assume it's not so the user needs to type less.
cf bind-service myapp mydb -c ~/workspace/tmp/instance_config.json && cf rg myapp
cf bind-service myapp mydb -c ~/workspace/tmp/instance_config.json --force-restage
I also understand that with most buildpacks a restart is sufficient, which is quicker than a restage.
It is the CLI's design philosophy for each command to do just one thing, which adds to my reluctance to accept this feature.
Cheers,
Dies Koper,
CF CLI PM