Increase validation problems test coverage

Context
With a recent PR TODOs have been left.
This addresses some of those.
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test this

unintentin

The merge queue build has failed. Click here to see all failures.

The merge queue build has failed. Click here to see all failures.


[BUG]  Footer email and phone no  aren't clickable and hence not launching gmail on clicking

Description

Footer email links isn't launching Gmail when clicked as it is not clickable.
I will make both email & phone no. clickable
@swaraj-das

Screenshots

Any additional information?
No response
What browser are you seeing the problem on?
Chrome
Checklist

[X] I have checked the existing issues.
[X] I have read the Code Of Conduct
[X] The changes don't break the code
[X] Please attach the screenshots and video of the development work once it is done

@swaraj-das please assign me the task

I would like to contribute on this. please assign me that issue.


DB Problem upgrading from <IP_ADDRESS>7 to <IP_ADDRESS>9

Gogs version (or commit ref): <IP_ADDRESS>9
Git version: 2.7.4
Operating system: Ubuntu Xenial
Database (use [x]):

[ X] PostgreSQL
[ ] MySQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ X] No
[ ] Not relevant

Log gist:

Description
I'm getting following when trying to start <IP_ADDRESS>9 instance on  <IP_ADDRESS>7 populated Postgres database:
2016/08/04 17:26:47 [...s/routers/install.go:71 GlobalInit()] [E] Fail to initialize ORM engine: sync database struct error: pq: syntax error at or near ""enable_prune""

Try upgrade to latest version.
Please dump full xorm.log here.

cc @lunny

Latest fails to compile with:
lessc public/less/gogs.less public/css/gogs.css
go install "-v" -ldflags '-X "github.com/gogits/gogs/modules/setting.BuildTime=2016-08-04 06:31:30 UTC" -X "github.com/gogits/gogs/modules/setting.BuildGitHash=ee28fd92551961070cff4fe1b37ab94268c2f111"' -tags '""'
github.com/gogits/gogs/models
# github.com/gogits/gogs/models
models/login.go:299: undefined: binding.AlphaDashDotPattern in binding.AlphaDashDotPattern.MatchString
models/mail.go:47: undefined: macaron.NewTemplateSet
models/mail.go:48: undefined: macaron.DEFAULT_TPL_SET_NAME
models/mail.go:51: unknown macaron.TplRender field 'TemplateSet' in struct literal
Makefile:20: recipe for target 'build' failed
make: *** [build] Error 2

How can I get xorm.log?

Looks like you have very outdated dependencies.
https://gogs.io/docs/upgrade/upgrade_from_source

Ok my fault, I didn't do glide install, it compiles fine.
So it seems like Gogs version <IP_ADDRESS>3 works fine, thanks


Swap order of Ether to Bitcoin got cancelled but my ether were not returned to my wallet

What happened with my transaction!!! How much i need to wait and where my ether?
My ether gone
REF ID#: BITYTQMXAV
Amount to send: 8.97323732 ETH
Amount to receive: 0.80000000 BTC
Payment Address: 0x76b7b147427bf0b83f35b9347e3c392045c4dda7
Rate: 0.08982 ETH/BTC

Please EMAIL<EMAIL_ADDRESS>and<EMAIL_ADDRESS>so that we may determine what happened and resolve this in a timely manner for you. Thank you.


ci(actions): fix no space left on device error

Currently the builds on main are failing with the error
System.IO.IOException: No space left on device.
See for example the runs

https://github.com/MediaMarktSaturn/technolinator/actions/runs/8566012762
https://github.com/MediaMarktSaturn/technolinator/actions/runs/8566139722

Therefore, follow the suggestion in this comment

https://github.com/orgs/community/discussions/26351#discussioncomment-3251595

to free up space on GitHub runner, before running the CI.

Why do we need more than the guaranteed 10gb disk space though?

Why do we need more than the guaranteed 10gb disk space though?

not sure whether this will help, as it only free up ~3Gi.
but let's see.


Add a retry strategy for the subgraphs tests

Proposed changes
Adds a retry strategy for the subgraphs tests which depend on the network and may fail occasionally.
Fixes
Closes #1128.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
n/a

This should really be generalized and put into a class with generic helper functions, as I've seen this same logic implemented several places (and yes, I am also a "contributor" to that).
However we can do better than what we have so far done and use built-in libraries entirely. Please open a ticket if you agree with my suggestion, link this PR so we can replace and discard this implementation and others (like my own) after
import requests
from requests.adapters import HTTPAdapter, Retry

def requests_retry_session(...):
    s = requests.Session()
    retries = Retry(total=5, backoff_factor=0.1, status_forcelist=[404, ... ])
    s.mount('http://', HTTPAdapter(max_retries=retries))
    s.get(api_specs["url"])

https://urllib3.readthedocs.io/en/latest/reference/urllib3.util.html#module-urllib3.util.retry https://www.peterbe.com/plog/best-practice-with-retries-with-requests

I think we cannot because if you notice the implementation, we get status 200 and a specific error message in the returned dictionary which we need to handle.

This should really be generalized and put into a class with generic helper functions, as I've seen this same logic implemented several places (and yes, I am also a "contributor" to that).
However we can do better than what we have so far done and use built-in libraries entirely. Please open a ticket if you agree with my suggestion, link this PR so we can replace and discard this implementation and others (like my own) after
import requests
from requests.adapters import HTTPAdapter, Retry

def requests_retry_session(...):
    s = requests.Session()
    retries = Retry(total=5, backoff_factor=0.1, status_forcelist=[404, ... ])
    s.mount('http://', HTTPAdapter(max_retries=retries))
    s.get(api_specs["url"])

https://urllib3.readthedocs.io/en/latest/reference/urllib3.util.html#module-urllib3.util.retry https://www.peterbe.com/plog/best-practice-with-retries-with-requests

I think we cannot because if you notice the implementation, we get status 200 and a specific error message in the returned dictionary which we need to handle.

yes so we generalize it one step further and wrap this basic requests retry with back off method such that it is itself retried when specific message is returned.


torch version error

When i tired to train a model using dist-train.sh, an error occurs:
ImportError: .../mmdetection/mmdet/ops/dcn/deform_conv_cuda.cpython-36m-x86_64-linux-gnu.so: undefined symbol: _ZN3c105ErrorC1ENS_14SourceLocationERKSs
And this is solved from downgrading torch 1.0.1 to 1.0.0. Anyone knows why this is the case?

This codebase should be compatible with both pytorch 1.0.0 and 1.0.1. When you installed a new version pytorch, did you recompile the ops?


Add GCMR thermal properties

Now that I'm running a multiphysics simulation for the GCMR, I noticed some properties are missing from the doc description page.
I've added most everything I can from the current simulation files in the GCMR simulation directory, but I'm missing a few values. (see: NEED VALUE)
I'm also wondering about the various BISON material objects: GraphiteMatrixThermal, ChromiumThermal, FeCrAlThermal, and BeOThermal. Are these available if you are using the Moose Heat Transfer module and not BISON? Since BISON is not Open-Source, I'd like these values to be available for people to use if they do not have access.
Tagging @nstauff.
Closes #354.

Got it, I'll just link all the BISON docs for the materials they apply to!

@lewisgross1296  BISON has a different material object for this (https://mooseframework.inl.gov/bison/source/materials/GraphiteMatrixThermal.html).

Job VTB Documentation on 201c85c wanted to post the following:
View the site here
This comment will be updated on new commits.

Looks good thank you for the contribution!


flet build apk --include-packages flet_video

When issuing that command on windows everything breaks as follows:
PS C:\Users\dan\flet\crystaltunes> flet build apk --include-packages flet_video
Creating Flutter bootstrap project...OK
Customizing app icons and splash images...OK
Generating app icons...OK
Generating splash screens...OK
Packaging Python app...OK
Building .apk for Android...Resolving dependencies...
  file_picker 6.2.1 (8.0.0+1 available)
  fl_chart 0.65.0 (0.67.0 available)
  flutter_lints 2.0.3 (3.0.2 available)
  flutter_native_splash 2.3.7 (2.4.0 available)
  intl 0.18.1 (0.19.0 available)
  js 0.6.7 (0.7.1 available)
  leak_tracker 10.0.0 (10.0.5 available)
  leak_tracker_flutter_testing 2.0.1 (3.0.5 available)
  leak_tracker_testing 2.0.1 (3.0.1 available)
  lints 2.1.1 (3.0.0 available)
  material_color_utilities 0.8.0 (0.11.1 available)
  meta 1.11.0 (1.14.0 available)
  package_info_plus 4.2.0 (7.0.0 available)
  package_info_plus_platform_interface 2.0.1 (3.0.0 available)
  petitparser 5.4.0 (6.0.2 available)
  screen_brightness 0.2.2+1 (1.0.0 available)
  screen_brightness_android 0.1.0+2 (1.0.0 available)
  screen_brightness_ios 0.1.0 (1.0.0+1 available)
  screen_brightness_macos 0.1.0+1 (1.0.0 available)
  screen_brightness_platform_interface 0.1.0 (1.0.0 available)
  screen_brightness_windows 0.1.3 (1.0.0 available)
  sensors_plus 4.0.2 (5.0.1 available)
  test_api 0.6.1 (0.7.1 available)
  toml 0.14.0 (0.15.0 available)
  vm_service 13.0.0 (14.2.0 available)
  wakelock_plus 1.2.1 (1.2.4 available)
  xml 6.3.0 (6.5.0 available)
Got dependencies!
27 packages have newer versions incompatible with dependency constraints.
Try `flutter pub outdated` for more information.

Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'...                            9.0s

┌─ Flutter Fix ──────────────────────────────────────────────────────────────────────────────┐
│ [!] Your project requires a newer version of the Kotlin Gradle plugin.                     │
│ Find the latest version on https://kotlinlang.org/docs/releases.html#release-details, then │
│ update C:\Users\dan\AppData\Local\Temp\flet_flutter_build_ckkOHZHJV1\android\build.gradle: │
│ ext.kotlin_version = '<latest-version>'                                                    │
└────────────────────────────────────────────────────────────────────────────────────────────┘

e: Incompatible classes were found in dependencies. Remove them from the classpath or use '-Xskip-metadata-version-check' to suppress errors
e: C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with
an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
e: C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/META-INF/kotlin-stdlib-jdk8.kotlin_module: Module was compiled with
an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
e: C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an
incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (14, 10): Unresolved reference: listOf
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (19, 12): Unresolved reference: listOf
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (25, 12): Unresolved reference: listOf
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (26, 17): Unresolved reference: javaClass
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (55, 6): Class 'kotlin.Suppress' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Suppress.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (62, 12): Unresolved reference: listOf
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (78, 6): Class 'kotlin.Suppress' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Suppress.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (85, 12): Unresolved reference: listOf
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (90, 2): Class 'kotlin.Suppress' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Suppress.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (95, 52): Unresolved reference: let
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (96, 37): Unresolved reference: it
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (100, 52): Unresolved reference: let
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (101, 34): Unresolved reference: it
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (108, 5): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (110, 16): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (111, 9): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (114, 16): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (115, 9): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (117, 21): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (129, 38): Unresolved reference: lazy
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (133, 6): Class 'kotlin.Suppress' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Suppress.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (135, 7): Unresolved reference: run
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (137, 9): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (138, 19): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (142, 13): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (143, 19): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (144, 25): Unresolved reference: listOf
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (148, 19): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (151, 19): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (154, 7): Unresolved reference: run
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (156, 9): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (157, 19): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (159, 13): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (160, 25): Unresolved reference: listOf
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (164, 19): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Messages.g.kt: (167, 19): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Wakelock.kt: (23, 5): Class 'kotlin.Unit' was compiled with
an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Wakelock.kt: (24, 37): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\Wakelock.kt: (26, 23): Class 'kotlin.Unit' was compiled
with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\WakelockPlusPlugin.kt: (16, 21): Class 'kotlin.Unit' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\WakelockPlusPlugin.kt: (17, 5): Class 'kotlin.Unit' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\WakelockPlusPlugin.kt: (21, 21): Class 'kotlin.Unit' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\WakelockPlusPlugin.kt: (22, 5): Class 'kotlin.Unit' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\WakelockPlusPlugin.kt: (26, 15): Class 'kotlin.Unit' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\WakelockPlusPlugin.kt: (30, 15): Class 'kotlin.Unit' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\WakelockPlusPlugin.kt: (34, 5): Class 'kotlin.Unit' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\WakelockPlusPlugin.kt: (38, 5): Class 'kotlin.Unit' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
e: C:\Users\dan\AppData\Local\Pub\Cache\hosted\pub.dev\wakelock_plus-1.2.1\android\src\main\kotlin\dev\fluttercommunity\plus\wakelock\WakelockPlusPlugin.kt: (42, 16): Class 'kotlin.Unit' was
compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from C:/Users/dan/.gradle/caches/transforms-3/6498ee1438a7a83cb4725beb055db98c/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':wakelock_plus:compileReleaseKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
   > Compilation error. See log for more 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 8s
Gradle task assembleRelease failed with exit code 1

Error building Flet app - see the log of failed command above.
PS C:\Users\dan\flet\crystaltunes>

So far I have been able to get it to compile an apk with following modifications to plugins:
#WSL:
cd /mnt/c/Users/dan/AppData/Local/Pub/Cache/hosted/pub.dev
nano media_kit_video-1.2.4/pubspec.yaml
(change version to: wakelock_plus: ^1.2.4)
nano serious_python_platform_interface-0.7.0/pubspec.yaml
(change version to: package_info_plus: ">=4.0.2 <7.0.0")
Currently getting a blank screen, but may be due to something else, I'll look more into it. but these changes get video to compile to apk again.

ok tested it on android phone, I had port set which android does not like lol. But yeah above fixes work perfectly, working on android just fine now...


OPNsense 19.7.2-amd64 in Xenserer 7.1 hangs on command sysctl -A

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[-] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[-] I have searched the existing issues and I'm convinced that mine is new.
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.
Relevant log files
If applicable, information from log files supporting your claim.
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant.
e.g.:
OPNsense 19.1.1 (amd64, OpenSSL).
Intel® Xeon™ E3-1225V5 3.3Ghz Quad Core
Network Intel® I210-AT

Hello!

OPNsense 19.7.2-amd64 VM in Xenserer 7.1 (all updates and xentools are installed).
Type sysctl -A in Xencenter VM console or in ssh console.
VM hangs with 100% CPU load. Only Force Reboot from Xencenter helps.
Thank you!
Best Regards,
Oleg.

Hi Oleg,
It is worth testing the behaviour on FreeBSD or HardenedBSD and report the issue there if it persists. It's not something that is in the scope of our project.
We can, however, take patches if they exist in said projects. :)
Cheers,
Franco

Hi, Franco!

The same Xenserer 7.1 and VM with FreeBSD 10.2-RELEASE on it (xentools are installed).
sysctl -A in Xencenter VM console or in ssh console.
Everything works fine.

Sysctl command is very usefull when diagnosting or tuning the system. For example https://forum.opnsense.org/index.php?topic=6590.0
sysctl -A # Shows system variables
Unfortunately, i haven't any hardware server to test OPNsense 19.7.2-amd64 and sysctl -A command.
Thank you!
Best Regards,
Oleg.

OPNsense 19.1/19.7 uses HardenedBSD 11.2. You can also try FreeBSD 11.2, but 10.2 won't give us a good data point.


TEM-29: test ipfs functionality

:construction_worker: Purpose
Enable tests that cover IPFS functionality, which is possible now following #185
:rocket: Changes
Minor refactor of IPFSManager to use given connectionURL properly
Minor adjustments to makefile and test/docker-compose.yml
Enable pubsub in ipfs nodes
Enable some tests
:warning: Breaking Changes
none

I triggered a branch merge. Also noticed this error running make clean
solidity@mastermind:~/go/src/github.com/RTradeLtd/Temporal$ make clean
=================== cleaning up temp assets ===================
Stopping ipfs.cluster.1  ... done
Stopping test_minio_1    ... done
Stopping ipfs.node.1     ... done
Stopping test_rabbitmq_1 ... done
Stopping test_postgres_1 ... done
Stopping ipfs.node.2     ... done
Removing ipfs.cluster.2  ... done
Removing ipfs.cluster.1  ... done
Removing test_minio_1    ... done
Removing ipfs.node.1     ... done
Removing test_rabbitmq_1 ... done
Removing test_postgres_1 ... done
Removing ipfs.node.2     ... done
Removing network test_default
Removing image ipfs/go-ipfs:v0.4.17
Removing image ipfs/go-ipfs:v0.4.17
ERROR: Failed to remove image for service ipfs.node.2: 404 Client Error: Not Found ("No such image: ipfs/go-ipfs:v0.4.17")
Removing image postgres
Removing image rabbitmq
Removing image ipfs/ipfs-cluster:v0.5.0
Removing image ipfs/ipfs-cluster:v0.5.0
ERROR: Failed to remove image for service ipfs.cluster.2: 404 Client Error: Not Found ("No such image: ipfs/ipfs-cluster:v0.5.0")
Removing image minio/minio
No stopped containers
===================          done           ===================

actually @postables i think i changed the behaviour in another commit to avoid that:
❯ make clean
===================  shutting down test env ===================
Stopping ipfs.cluster.2  ... done
Stopping ipfs.cluster.1  ... done
Stopping ipfs.node.1     ... done
Stopping test_postgres_1 ... done
Stopping test_minio_1    ... done
Stopping test_rabbitmq_1 ... done
Stopping ipfs.node.2     ... done
Removing ipfs.cluster.2  ... done
Removing ipfs.cluster.1  ... done
Removing ipfs.node.1     ... done
Removing test_postgres_1 ... done
Removing test_minio_1    ... done
Removing test_rabbitmq_1 ... done
Removing ipfs.node.2     ... done
Removing network test_default
===================          done           ===================
=================== cleaning up temp assets ===================
No stopped containers
===================          done           ===================


chore: add networkPolicy enabled for vault dependency

Enable networkPolicy for vault dependency for the umbrella chart.

Marco Lecheler<EMAIL_ADDRESS>Mercedes-Benz Tech Innovation GmbH (ProviderInformation)

LGTM. The failing kyverno policy check is related to DAPS and not caused by this change


Authentification failure for Settings Sync

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.60.0
OS Version: Mac 11.4

Steps to Reproduce:

Command P
Settings Sync: Turn on
Click Sign in and turn on
Select xxxx github (Microsoft account is marked as signed in)

Resulting Error message :
[2021-11-10 21:53:26.342] [settingssync] [info] Request failed {"url":"https://vscode-sync.trafficmanager.net/v1/manifest","status":401,"execution-id":"xxxxxx"}
The issue Reporter under the Help menu doesn't send the for either.
I've also tried to sync setting using the Microsoft account I am signed into but it doesn't work either and I would rather use my Github account. Incidentally, I can't find where to sign out of the Microsolft account.
when I got to output Github Authentification I get
[Info  - 21:03:09.820] Getting sessions for all scopes...
[Info  - 21:03:09.820] Got 1 sessions for all scopes...

I managed to sign out of both accounts and sign back in which fixed the problem. I'm going to close the issue. Thanks.


Fix incorrect AOT Memory Planning

This change introduces a second memory planning phase in the AOT code
generator once the storage rewrite pass has been completed, fixing
incorrectly sized workspaces for a variety of models.
It comes with accompanying tests so we can safely refactor this later.
Also corrected a typo in the TE compiler regards the memory alignment
argument :smile_cat:
Co-authored-by: Manupa Karunaratne<EMAIL_ADDRESS>

CC @manupa-arm

Also CC @mbs-octoml @electriclilies for reviews :smile_cat:


Added two solutions to 'flow' in CSX/Recursion - Code Review Requested

Please review code if you have time...
Any advantages or disadvantages to one solution over the other?

On attempt 1, I did use arrray.shift() but I had no idea that I could use the shift method to return the array element's functionality as well , as in funcArray.shift()(input).  I guess I didn't realize that it returned the definition of the first function.  So I added the extra step of assigning it to variable name callback.
But, yes, I can see how return flow(funcArray.shift()(input), funcArray) is not only much cleaner, but also doesn't store an additional variable in memory.  Its super cool.  When I first read that line I was like, "what...you can do that?!" :-)


IMS responds with octet-stream when image/jpeg is available

I'm currently working with a Slim deployment which is retrieving JPEG encoded SM instances. The request's accept header is as follows:
multipart/related; type="image/jls"; transfer-syntax=1.2.840.10<IP_ADDRESS>.80, multipart/related; type="image/jls"; transfer-syntax=1.2.840.10<IP_ADDRESS>.81, multipart/related; type="image/jp2"; transfer-syntax=1.2.840.10<IP_ADDRESS>.90, multipart/related; type="image/jp2"; transfer-syntax=1.2.840.10<IP_ADDRESS>.91, multipart/related; type="image/jpx"; transfer-syntax=1.2.840.10<IP_ADDRESS>.92, multipart/related; type="image/jpx"; transfer-syntax=1.2.840.10<IP_ADDRESS>.93, multipart/related; type="application/octet-stream"; transfer-syntax=*, multipart/related; type="image/jpeg"; transfer-syntax=1.2.840.10<IP_ADDRESS>.50
and the response's content type is:
multipart/related;start="<***@resteasy-multipart>";type="application/octet-stream"; boundary***
The source image is JPEG encoded, so I think that since JPEG appears after octet-stream, it chooses octet-stream instead. I assume the issue is introduced here:
https://github.com/ImagingDataCommons/dicom-microscopy-viewer/blob/097282b5690886735f3fe6521d0774ee33b7f418/src/pyramid.js#L461-L472
Would it be sufficient to just put push the octet stream mediatype after the jpeg mediatype if statement?

What archive backend are you using @cgorman? From an HTTP perspective, the order shouldn't be significant. I would consider this a bug in the archive and/or a lack of clarity of the DICOM standard regarding the expected behaviour.
Intuitively, I would expect the archive to return the image as it is stored if the corresponding media type is in the list of acceptable media types provided by the client. Unfortunately, that behaviour is not explicitly defined by the standard.
Some archives return the pixel data as stored when they are requested with type="application/octet-stream"; transfer-syntax=*. That behaviour appears to be standard conformant. The standard states that a request with such an accept header should result in the data being returned in the default media type for the resource category (see PS3.18 8.7.7 Accept Header Field and PS3.18 8.7.5 Acceptable Media Types). For Frame Pixel Data resources (a subset of Bulkdata resources) the default media type for JPEG compressed pixel data should be image/jpeg (see PS3.28 <IP_ADDRESS>.2 Compressed Bulkdata Media Types). cc @dclunie

Unfortunately, archives have not done a great job in implementing this part of the standard and the behaviour varies between implementations.
Some archives include the "Available Transfer Syntax UID" attribute in the search results (see PS3.18 <IP_ADDRESS>.3 Instance Resources). If provided, the value may help us in selecting a single acceptable media type without having to provide a long list of acceptable media types, which many archives apparently struggle to handle correctly.
cc @gunterze @jasonklotzer @stevenborg for awareness

dcm4chee-arc 5.29.3 will prioritize Media Types in "accept" Header or "accept" Query Parameter for compressed formats over Media Types for uncompressed formats with equal q value
https://github.com/dcm4che/dcm4chee-arc-light/issues/3981
Recommend to specify a q value < 1.0 for multipart/related; type="application/octet-stream", to do not rely on how an archive prioritize Media Types with equal q values.

I am not sure how may servers implement and return it, but in CP 1901 we did add as an instance-level query parameter the Available Transfer Syntax UID (0008,3002) to describe the Transfer Syntaxes that the origin server will assure will be supported for retrieval of the SOP Instance.
The idea is that you can find out (per instance) what the appropriate Transfer Syntax is, if you want it the way it is stored (or can losslessly be converted to), and then you can craft your Accept header very narrowly accordingly.
See PS3.18 <IP_ADDRESS>.3 Instance Resources and PS3.4 C.<IP_ADDRESS>.2 Available SOP Transfer Syntax UID.
I haven't checked to see whether the Google DicomStore used by IDC actually implements this or not (but it isn't mention in their documentation), and if not, we should probably put in a feature request, particularly (but not only) if any of our viewers (Slim or OHIF) would find this useful. (@fedorov)
@gunterze, does dcm4chee-arc 5? I haven't tried it, but I think it does, based on this closed as implemented tracker item.

Yes it does. E.g.:
$ curl http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/rs/studies/2.16.840.1.1139<IP_ADDRESS>.0.10118.6000009.497166.721604/instances | jq '.[]["00083002"]'
{
  "vr": "UI",
  "Value": [
    "1.2.840.10<IP_ADDRESS>.50"
  ]
}

Created issue and PR in dcmjs dicomweb-client.


SDK should be ready for payment right after connect

Right now we have some cases where trying to send payment right after connect (on existing node) returns with no route.
It seems that when the connect returns we are not making sure the node is connected to the lsp which is for sure one case that causes this issue.
We can start with this fix.

@JssDWt from what you've seen, were they outgoing payments or incoming payments those that failed with no_route right after connect?

@ok300 the issue is for sending and I was able to reproduce it.
I added connect to lsp peer as part of the connect method and it didn't solve the issue.
In addition Talking to @cdecker my understanding is that greenlight already holds the pay request until the lsp peer is connected. It turns out that there is an issue there and the pay is released before the channel is really active.
I will leave this open until is fixed in gl.

@roeierez It was not about sending. It happened on node_info, receive_payment and lnurl_withdraw. Several types of issues:

service not available error
transport error
a weird case where the client got completely stuck. This got resolved after the node on greenlight
2 channel force closes directly after receiving the payment. The users had an output with a local balance of exactly the received amount.

I don't think I specifically had issues with connect regarding sent payments. no_route was not an issue specifically. (there were cases of no_route, bit they were in the other direction, where the sdk was the recipient)

@JssDWt the list above I believe is not one issue but different use cases where each use case is a potential issue :)
I suggest to open issue for every use case but this specific issue is about getting no route when attempting to send immediately after connect.  It is reproducible.
The transport error I believe was reproduced after recover right? I will open an issue.
Please open an issue for service not available if you can as I am not aware of the exact details.


Update sleepers and anomalies data

Really needed before public release

Drifter battleship: http://playground.schildwall.info/basics/types/types.php?typeID=37473
Wormhole PVE sheet: https://docs.google.com/spreadsheets/d/17cNu8hxqJKqkkPnhDlIuJY-IT6ps7kTNCd3BEz0Bvqs/pubhtml

Updated sleepers data from http://playground.schildwall.info/basics/npcattributes/
TODO: drifter shield resists? maybe add neut range/amount, web strength/range, dis strength/range?

Split into 2 issues #11 #12


Improvements to Answer Parsing

Make the bot accept answers after (ACCEPT: tags

Note: Tried to fix with #12 and #22, but couldn't due to changes in code

I think the best way to do this would be to use .split(' (ACCEPT: ') as this will create a single element array if it doesn't have the "accept" thing at the end, which is what was manually being done earlier anyways. Once you split it, you can check the size to see whether you need to remove the trailing bracket or not.


A feature of hint while coding .....

The legit request of mine is to do add a feature of hint while coding either its a function names ,words like that and that also gives us idea and application of that certain lines as a popup hint for ease of coding ...

closing due inactivity


Authentication using API Keys

The instructions did not include how to authenticate using the newer API keys. I was only able to find this information in your PHP library and thought that other people may be stuck like I was.

This is great! It was on my list to specifically add this to this page. Thanks for doing this, I'll get it merged in shortly.


Shardstore Unittest Fix

High Level Overview of Change
This fixes some recent failures in the shard database unit tests.

Context of Change
The unit test functions testDeterministicShard and testImportWithOnlineDelete were modified to fix test case failures. Please limit the review to 7778710 as this fix is stacked onto several unmerged PRs.

Type of Change

[x ] Bug fix (non-breaking change which fixes an issue)

:tada:


Add MapPathToHandle API to handle path string

--Add new MapPathToHandle API to handle path string, currently it does
not support dictionary.
--This API would be used in data management support for mobile client
side.
--In details, given a string positioned at the root tag of a WDM path,
the delimiter is /, read out the relevant tags and provide
the equivalent path handle.

All comments addressed, please help review again! @jaylogue @robszewczyk  thanks!

Codecov Report

Merging #403 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #403      +/-   ##
==========================================
- Coverage   54.48%   54.45%   -0.03%
==========================================
  Files         344      344
  Lines       58492    58522      +30
==========================================
  Hits        31869    31869
- Misses      26623    26653      +30

Impacted Files
Coverage Δ

...c/lib/profiles/data-management/Current/TraitData.h
45% <ø> (ø)
:arrow_up:

...lib/profiles/data-management/Current/TraitData.cpp
81.05% <0%> (-4.51%)
: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 56bcb34...de8c468. Read the comment docs.


Error with routes.

hi,
i need solve this problem in the sessions#new:
Routing Error
No route matches {:action=>"show", :controller=>"sessions"}
I followed the tutorial step by step but does not work.
thanks

Need some more info. Paste your sessions#new page and your routes file in here.


drivers: gpio_pca95xx: add missing gpio_utils.h include

Include gpio_utils.h to fix a build failure:
gpio_pca95xx.c:490:20: warning: implicit declaration of
function 'GPIO_PORT_PIN_MASK_FROM_NGPIOS'
[-Wimplicit-function-declaration]
gpio_pca95xx.c:490:20: error: initializer element is not constant
.port_pin_mask = GPIO_PORT_PIN_MASK_FROM_NGPIOS(
DT_INST_##inst##_NXP_PCA95XX_NGPIOS), \
Signed-off-by: Göran Weinholt<EMAIL_ADDRESS>

@dcpleung is there any platform that can be used to test this? It should have been caught in sanitycheck long ago.

IIRC, mec15xxevb_assy6853 has this as an GPIO expander. However, this is not enabled by default.
@franciscomunoz Could we enable this option as default for the MEC1501 dev board?


Complete Account Link Transaction description

AccountLinkTransaction section misses information about which accounts can be used for delegated harvesting:
Delegated Harvesting allows an account Ah to harvest on behalf of an account A. When the account Ah is chosen as delegated account for A, it is not allowed to:

- own any mosaics
- to be a cosignatory of any other account
- to be a multisig account
- to be already a delegated account for another account
- to have a delegated account itself

For the time the account Ah is used as delegated account, the account is not allowed:

- to initiate any transactions
- to receive any transactions where the account is involved, e.g. recipient of mosaics, use as cosignatory,...

@matthewkim93 is working on this task.


Live

test PR

Docs Build status updates of commit 1743bb9:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


add libqt5-serialport-dev key to provide build headers

Please add the following dependency to the rosdep database.
Package name:
libqt5-serialport-dev
Package Upstream Source:
https://www.qt.io/
https://github.com/qt/qtserialport
Purpose of using this:
This package provides header and Qt5SerialPortConfig.cmake files to build an application using the Qt5::SerialPort module.
Distro packaging links:
Links to Distribution Packages

Debian: https://packages.debian.org/

REQUIRED
https://packages.debian.org/sid/libdevel/libqt5serialport5-dev

Ubuntu: https://packages.ubuntu.com/

REQUIRED
https://packages.ubuntu.com/hirsute/i386/libqt5serialport5-dev/filelist

Fedora: https://src.fedoraproject.org/browse/projects/

IF AVAILABLE

Arch: https://www.archlinux.org/packages/

IF AVAILABLE
https://archlinux.org/packages/extra/x86_64/qt5-serialport/files/

Gentoo: https://packages.gentoo.org/

IF AVAILABLE

macOS: https://formulae.brew.sh/

IF AVAILABLE

Alpine: https://pkgs.alpinelinux.org/packages

IF AVAILABLE

NixOS/nixpkgs: https://search.nixos.org/packages

OPTIONAL

Checks

[ ] All packages have a declared license in the package.xml
[ ] This repository has a LICENSE file
[ ] This package is expected to build on the submitted rosdistro

Could you add?
https://src.fedoraproject.org/rpms/qt5-qtserialport
https://packages.gentoo.org/packages/dev-qt/qtserialport
https://pkgs.alpinelinux.org/package/edge/community/x86/qt5-qtserialport

Hi @ivanpauno thanks for the feedback. Note that there already is a rosdep key for libqt5-serialport and what I want to add is a key for packages that contain the development header and CMake files.

https://src.fedoraproject.org/rpms/qt5-qtserialport

It looks like the fedora package does include this RPM with development files https://koji.fedoraproject.org/koji/rpminfo?rpmID=27106679 so I will specify qt5-qtserialport.

https://packages.gentoo.org/packages/dev-qt/qtserialport

I am having trouble finding the list of files included in that package. Do you have any tips on where that information can be found?

https://pkgs.alpinelinux.org/package/edge/community/x86/qt5-qtserialport

It looks like the alpinelinux package that I want to add is https://pkgs.alpinelinux.org/package/edge/community/armhf/qt5-qtserialport-dev which does include the development headers and CMake Qt5SerialPortConfig.cmake files. I will specify that package.

Hi @ivanpauno thanks for the feedback. Note that there already is a rosdep key for libqt5-serialport and what I want to add is a key for packages that contain the development header and CMake files.

Thanks for clarifying, I didn't notice that.

https://packages.gentoo.org/packages/dev-qt/qtserialport
I am having trouble finding the list of files included in that package. Do you have any tips on where that information can be found?

I couldn't find that, but I think they do include header files there.
e.g.: https://github.com/ros/rosdistro/blob/50786bb7164fdd424a78ced35efa87f4fe33b0e0/rosdep/base.yaml#L4630

@ivandariojr I found a way to list the package contents on this site https://www.portagefilelist.de/site/query/listPackageFiles/?category=dev-qt&package=qtserialport&version=5.9.4&do#result
I confirmed that the gentoo package has the development files so I will add it to the rosdep entry.


Using custom embeddings and embeddingfunction with sentence transformers

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I would like to use custom embeddings function as I need specific sentence transformer for multilingual support:
This is howe I create embeddings function:
class MyEmbeddingFunction(EmbeddingFunction[Documents]):
def call(self, input: Documents) -> Embeddings:
#sentence_transformer_ef = embedding_functions.SentenceTransformerEmbeddingFunction(model_name="bert-base-multilingual-uncased")
sentence_transformer_ef = embedding_functions.SentenceTransformerEmbeddingFunction(model_name="intfloat/multilingual-e5-large")
embeddings = sentence_transformer_ef(input)
return embeddings
custom = MyEmbeddingFunction()
and I can pass it to cromadb without any problems:
chroma_collection  = chroma_client.get_or_create_collection(name=f"MLRag", embedding_function=custom)
But in order to use it in query_engine I need to pass embed model to service context
set service context
service_context = ServiceContext.from_defaults(
chunk_size=768,
llm=llm,
embed_model=embed_model
)
how can I construct custom embed model that will use my custom transformers?

You'll probably find this helpful. Just need to extend the base class
https://docs.llamaindex.ai/en/stable/examples/embeddings/custom_embeddings.html

I tried using:
embed_model = SentenceTransformerEmbeddings(model_name="intfloat/multilingual-e5-large")
set service context
service_context = ServiceContext.from_defaults(
chunk_size=768,
llm=llm,
embed_model=embed_model
)
but no luck

I also tried:
from llama_index.embeddings import HuggingFaceEmbedding
embed_model = HuggingFaceEmbedding(model_name="intfloat/multilingual-e5-large")
model is downloaded, but query_engine dies on search

You can also use the langchain model if you want, but it needs a wrapper
https://docs.llamaindex.ai/en/stable/examples/embeddings/Langchain.html
Going to close out this issue then


Impartial or empty trusted list for multiplexing app

We observe an unwanted behavior for multiplexing apps during cross apps validation.
This is due to the current nature of the web service call result when an app is requesting for the trusted list: the successful returned list contains only the currently installed apps that are trusted.
For example:

App A with package name com.sdl.appa and is the only installed multiplexing app
App A requests the list, sending com.sdl.appa, it gets the empty list

The Livio app with package name com.livio.sdl and is the only installed multiplexing app
Livio app requests the list, sending com.livio.sdl, it gets com.livio.sdl

Subsequently, if a none trusted app is the only installed multiplexing app on the device, upon a successful request and download, its trusted list is empty and it cannot correctly validate other trusted apps that may be installed later.
Here is the flow:
1. App A is the only installed multiplexing app and is not on the trusted list:

App A makes a request for the trusted list
Successful returned result is an empty list
App A saves this empty list to its private shared preference
Install FordPass (trusted)
App A cannot correctly validate FordPass because its trusted list is empty

In any case, an empty trusted list received from RouterServiceValidator.getTrustedList() at any time during a run of a multiplexing app does not make sense because there are trusted apps by default.

For test 1 above, we can work out the logic so App A gets the default trusted list in case the request result returns an empty list. However, for test 2 below, there is not a way for App A to correctly validate Spotify as Spotify is not on the default trusted list but was made trusted later, unless we either update the default trusted list or modify the behavior of the woprjr request result. @joeygrover do you have any comment on this?
2. App A is the only installed multiplexing app and is not on the trusted list:

App A makes a request for the trusted list
Successful returned result is an empty list
App A correctly works out the logic so it can get the default trusted list
Install Spotify (trusted)
App A cannot correctly validate Spotify because its trusted list is default list and does not contain Spotify

The issue reported isn't correctly stated and the case explained is already handled, for that I am closing the issue.
When the router service connects and sends the SDL start intent, the SdlBroadcastReceiver calls the RouterServiceValidator to perform a trusted router service list query.  Within this call, the RouterServiceValidator searches the device for all SDL enabled apps and creates a JSON object. Next, the RouterServiceValidator checks to make sure it wasn't flagged to force a redownload of a list or that the timeout hasn't been reached. If neither of those are true, it then makes sure that the previously generated list of SDL enabled apps on the device matches the one used in the previous query. If it does match, the callback will return and the cached list will be used. If the list of SDL enabled apps does not match the one cached from the earlier trusted router service query, it will trigger a redownload event that will then use a new, updated list. If the list is retrieved successfully, the new list of SDL apps installed will be cached as well.  This covers the case of apps being installed/deleted between connected sessions. If you find an error with this process not working as designed please raise a new issue.
Finally, an empty list does make sense. While the library includes default trusted apps, those are only known to be trusted at the time of library release. There can come a time when those packages are no longer trusted and must not be used. Therefore, if they are not trusted they will not be in the list, and if no other app is trusted an empty list will be returned.

I agree this issue should not be flagged as bug but rather enhance.
And the case explained is not handled please read the above steps carefully, more detailed steps below.
The current code ensures that, in this flow, the app that is installed later has the most updated list of SDL enabled apps (thus itself in the trusted list if it's trusted) while the firstly installed app, without any forced download, will only have an empty trusted list.
Preconditions:
No SDL enabled multiplexing app installed in device
Steps:

Install app A, multiplexing and not trusted, with package name com.sdl.appa
App A gets the list of SDL enabled apps from device, it gets com.sdl.appa
App A makes the request for the trusted list, sending com.sdl.appa
App A gets the empty list back, it saves it to shared preference
Install app B, multiplexing and trusted, with package name com.livio.sdl
App B gets the list of SDL enabled apps from device, it gets com.sdl.appa, com.livio.sdl
App B makes the request for the trusted list, sending  com.sdl.appa, com.livio.sdl
App B gets the response from woprjr server that contains com.livio.sdl and saves it to shared preference
At this point if app A attempts to validate app B, it will not get a correct result as its trusted list is still empty.

This is not correct.
All apps perform the logic stated previously for every connection made. Every app for every connection checks to see if any SDL enabled apps were installed, deleted, or updated. If true for any of those, it will redownload an updated trusted app list. Each app contains their own list of trusted apps and previously scanned apps that were used to request the trusted app list.
Locking this conversation as the logic is misunderstood and should be cleared up before continuing to discuss here.

At step 9. please state what the trusted list is for App A and App B.
Base on what I see:
App A gets an empty list
App B gets com.livio.sdl

Every app for every connection checks to see if any SDL enabled apps were installed, deleted, or updated

Correct, but app A is not making a connection at this point and does not redownload.  It's only for app B that gets the latest SDL enabled app installed as in step 6.

App A will have an empty list at the exact time of App B's installed, however, the list itself is only needed when there is a connection. Therefore, there is never a time when the list isn't updated and it needs to be and there is no issue. Creating a network call each time an app is installed, deleted, or updated would be incredibly irresponsible on the our part, especially if the user doesn't connect to a module.


Update public pool names

This change is required for builds to continue working in the new org, dev.azure.com/dnceng-public.

Forcing merge so we can at least have public CI trigger, even though it can't report back to GitHub yet.


Update tslint config.

This is blocked until eslint-plugin-react releases a version above 7.18.3.

I think this is superseded by #301


Examine current site's log for load and make sure new site can handle that plus project increases

Include the API services, upload, list and searching

I was thinking we might instead just blitz the site and see how it does. We could also blitz a clone of the old site for comparison.

Please see me.

Here’s some data:

-p 1-30:60 -T 10000 http://nugetgallery.jeffhandley.com/Packages : 538 hits - no errors/timeouts, and the site was fine
o	This is a dedicated Windows Server, with SQL Server local
-p 1-30:60 -T 10000 http://preview.nuget.org/Packages : 527 hits - no errors/timeouts, and the site was fine
-p 1-30:60 -T 10000 http://nugetgallery.apphb.com/packages : 315 hits - 12 errors, and the site was fine (albeit a little pokey)
This is an AppHarbor deployment, with SQL Server over the internet to my dedicated server
-p 1-30:60 -T 10000 http://nuget.org/List/Packages : 5 hits - 59 timeouts – 10 errors, and the site was down for about a minute after the blitz finished

This proves that the preview site holds up about as well as a dedicated server with a local SQL Server instance, better than an AppHarbor instance connected to a remote database, and a helluva lot better than the current nuget.org website.
I think this is evidence enough that the new site should do just fine.  To be safe, we are going to spin up a 2nd web role instance and deploy the site with 2 instances, with the ability to scale up to 4 if needed.


[exporter/awsxray] Add aws sdk http error events to x-ray subsegment and strip prefix AWS.SDK. from aws remote service name

Description:

Convert individual HTTP error events into exceptions within subsegments for AWS SDK spans.

Normalize the service name from awsxray.AWSServiceAttribute attribute by removing the AWS.SDK. prefix (in some aws sdk instrumentation, we have added the prefix to produce metrics with the prefix to clearly indicate the resource). This change ensures that X-Ray backend recognizes standard service names like "DynamoDb", "S3", etc., enabling correct identification of AWS service types.

Link to tracking Issue: NA
Testing: Unit tests are added.
Documentation: NA
This is a copy of a open PR to open-telemetry/opentelemetry-collector-contrib https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/27232, we may want to directly merge this change instead of waiting for upstream to review + approve

Cancelling - I realized that I opened this PR against the wrong base branch, I actually want to merge into aws-cwa-dev. The head branch includes lots of commits that aren't in the aws-cwa-dev, so I'm creating a new PR which is rebased correctly


[installer e2e] Fix tests failing on deploy pipeline

What does this PR do?
Fix installer e2e tests:

Don't assert that the current version is devel because that's not true in build pipelines

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge

/merge

/merge


[Explain error with Copilot] Flag not showing up on macOS

Any thoughts on why the flag wouldn't show up on macOS? I haven't been able to find it in any of the release channels. It's definitely there (and very cool!) on a Windows 11 VM running Edge mainline.

Originally posted by @phyllisstein in https://github.com/MicrosoftEdge/DevTools/issues/203#issuecomment-1936949386
AB#48952537

This is now enabled by default on all platforms including macOS.

Closing this issue.


crash on non existant or empty README.md

Describe the bug
when the manifest declared readme file does not exist, cargo-spellcheck errors out rather than warning and moving on.

To Reproduce
# Cargo.toml

readme = "doesnotexist.md"

Expected behavior

Screenshots
Error:
   0: Common mark / markdown file does not exist
   1: failed to open file `/media/supersonic1t/projects/parity/polkadot-bernhard-testing-doc/node/malus/README.md`
   2: No such file or directory (os error 2)

Location:
   /home/bernhard/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-spellcheck-0.8.5/src/traverse/mod.rs:498

Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Please complete the following information:

System:  Fedora
Obtained:  cargo
Version: <!-- run $(cargo spellcheck --version) --> cargo-spellcheck 0.8.5

Additional context

Hello,
I tried to reproduce this issue and I think it has been already resolved (no panic!, and log contains a warning) in the commit dc08b026f9ee01071f70a13e0a7d77dbb44c4a6f .
More specifically in this else: https://github.com/drahnr/cargo-spellcheck/commit/dc08b026f9ee01071f70a13e0a7d77dbb44c4a6f#diff-4b3ee144b2b16d3477dd51cf4b17c9d58e30414a2da0f970e199c7b6410db3faR185-R190 .
Here is the log:
$ cargo spellcheck -vvvv check
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::config::args] Attempting to load configuration by priority.
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::config::args] No cfg flag present
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::config::args] Using /home/anon/tools/rust/cargo-spellcheck/tests/missing_readme/Cargo.toml manifest as anchor file
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::config::args] No user config present /home/anon/.config/cargo_spellcheck/config.toml
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::config::args] Using configuration default, builtin configuration (5)
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck] Executing: Check with Config { dev_comments: false, skip_readme: false, hunspell: Some(HunspellConfig { lang: Lang5 { lang: eng, country: US }, search_dirs: SearchDirs([]), skip_os_lookups: false, use_builtin: true, extra_dictionaries: [], quirks: Quirks { transform_regex: [], allow_concatenation: false, allow_dashes: false, allow_emojis: true }, tokenization_splitchars: "\",;:.!?#(){}[]|/_-‒'`&@§¶…" }), nlprules: Some(NlpRulesConfig { override_rules: None, override_tokenizer: None }), reflow: Some(ReflowConfig { max_line_length: 80 }) } from None
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::traverse] Running on inputs ["/home/anon/tools/rust/cargo-spellcheck/tests/missing_readme"] / recursive=true
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::traverse] Processing /home/anon/tools/rust/cargo-spellcheck/tests/missing_readme -> /home/anon/tools/rust/cargo-spellcheck/tests/missing_readme
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::traverse] Running on absolute dirs ["/home/anon/tools/rust/cargo-spellcheck/tests/missing_readme"]
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::traverse] Found a total of 1 files to check
[2021-10-15T22:00:23Z WARN  cargo_spellcheck::traverse] 📜 read-me file declared in Cargo.toml invalid.md is not a file
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::traverse] 🥞 Recursed into 0 modules from /home/anon/tools/rust/cargo-spellcheck/tests/missing_readme/src/main.rs
[2021-10-15T22:00:23Z DEBUG cargo_spellcheck::checker] Running NlpRules checks.
[2021-10-15T22:00:23Z INFO  cargo_spellcheck::checker::tokenize] 🧮 Loading tokenizer...
[2021-10-15T22:00:28Z INFO  cargo_spellcheck::checker::tokenize] 🧮 Loaded tokenizer.
[2021-10-15T22:00:28Z INFO  cargo_spellcheck::checker::tokenize] 🧮 Loading rules...
[2021-10-15T22:00:29Z INFO  cargo_spellcheck::checker::tokenize] 🧮 Loaded rules.
[2021-10-15T22:00:29Z DEBUG cargo_spellcheck::checker::nlprules] Processing /home/anon/tools/rust/cargo-spellcheck/tests/missing_readme/src/main.rs
[2021-10-15T22:00:29Z DEBUG cargo_spellcheck::checker] Running Hunspell checks.
[2021-10-15T22:00:29Z DEBUG cargo_spellcheck::checker::hunspell] Dictionary search path is not a directory /usr/share/myspell/
[2021-10-15T22:00:29Z DEBUG cargo_spellcheck::checker::hunspell] Dictionary search path is not a directory /usr/share/hunspell/
[2021-10-15T22:00:29Z DEBUG cargo_spellcheck::checker::hunspell] Dictionary search path is not a directory /usr/share/myspell/dicts/
[2021-10-15T22:00:29Z INFO  cargo_spellcheck::checker::hunspell] Using builtin en_US hunspell dictionary and affix files
[2021-10-15T22:00:29Z DEBUG cargo_spellcheck::checker::hunspell] Dictionary setup completed successfully.
[2021-10-15T22:00:29Z DEBUG cargo_spellcheck::checker::hunspell] Processing /home/anon/tools/rust/cargo-spellcheck/tests/missing_readme/src/main.rs

Interesting part:
[2021-10-15T22:00:23Z WARN  cargo_spellcheck::traverse] 📜 read-me file declared in Cargo.toml invalid.md is not a file

Maybe this issue can be closed?


feat(docs): add live-preview, props, return values to useTable

antd useTable doc
antd useEditableTable doc
react table useTable doc
mui useDataGrid doc

I think, you can delete Pagination, Sorters and Filtering sections because the doc repeat it. You already write about it in Properties section. It is a radical decision, I know so who supports this? :d @aliemir @omeraplak @yildirayunlu

https://63d7618129f7517513fdf7f0--refine-doc-preview.netlify.app/docs/api-reference/mui/hooks/useDataGrid/#realtime-updates
https://63d7618129f7517513fdf7f0--refine-doc-preview.netlify.app/docs/api-reference/antd/hooks/table/useTable/#realtime-updates
https://63d7618129f7517513fdf7f0--refine-doc-preview.netlify.app/docs/packages/documentation/react-table/#realtime-updates
Quotes in Realtime Updates are breaking the lines after. Also In react-table docs, realtime updates and properties has extra empty line in between.
useEditableTable has extra empty line in between basic usage and description.
for all table hooks, live provider required and notification provider required texts are need to change according to data hooks (check useList hook in core) and type definitions in Properties section can be removed since we don't do that in other hooks + we have that in API section.
@alicanerdurmaz


Millisecond dates not parsed

Example, the modified date on https://www.gbif.org/occurrence/1705512979 is 2017-12-04T13:16:35.907+12:00 but is not parsed, and no issue is added either.  Dates without the milliseconds parse correctly.

Check for other date inconsistencies too, e.g. compare a download with the published source.


Add samples for new AppConfig features

Added in https://github.com/Azure/azure-sdk-for-net/pull/18487

Can this be closed now?


VM Create: if no ssh key is present, we should surface a friendly message to the user

Currently the following error message is displayed:
An RSA key file or key value must be supplied to SSH Key Value
Do we need something more friendly than that? I assume not...


Please assist with TLS config

@oderwat ,
May I request guidance and/or advice getting the secure websocket (wss://) connection to work with the embedded nats server. Below is my attempt. I tried numerous attempts but to no avail. I am missing something major in my understanding in my very limited knowledge of TLS certs. I do know they certs work - tested with an other go app (gorilla websockets). My ISP enabled 80/433/3000/4000 ports.
Thank you in advance.
package back
import (
"bytes"
"compress/flate"
"context"
"crypto/tls"
"encoding/base64"
"fmt"
"image"
"image/jpeg"
"log"
"net"
"net/http"
"net/url"
"os"
"os/signal"
"time"
"github.com/go-chi/chi/v5"
"github.com/go-chi/chi/v5/middleware"
"github.com/maxence-charriere/go-app/v9/pkg/app"
"github.com/nats-io/nats-server/v2/server"
"github.com/nats-io/nats.go"
"github.com/o1egl/govatar"
"golang.org/x/net/netutil"

)
// AppServer implements the Backend service
type AppServer struct {
mux *chi.Mux
}
func (srv *AppServer) Mux() *chi.Mux {
return srv.mux
}
type Muxer interface {
Mux() *chi.Mux
}
func Create(ah *app.Handler) {
var srv AppServer
cert, err := tls.LoadX509KeyPair(
"mysite.com/combined_certificate.pem",
"mysite.com/certificate-key.pem",
)
if err != nil {
log.Fatal(err)
}
tlsConfig := &tls.Config{
Certificates:       []tls.Certificate{cert},
ServerName:         "mysite.com",
InsecureSkipVerify: true,
}
opts := &server.Options{
	ServerName:     "Your friendly backend",
	Host:           "<IP_ADDRESS>",
	Port:           8501,
	NoLog:          true,
	NoSigs:         true,
	MaxControlLine: 4096,
	Accounts: []*server.Account{
		{
			Name: "cluster",
		},
	},
	Websocket: server.WebsocketOpts{
		Host:       "<IP_ADDRESS>",
		Port:       3000,
		NoTLS:      false,
		TLSConfig:  tlsConfig,
		SameOrigin: true,
		AllowedOrigins: []string{
			"wss://mysite.com",
			"wss://mysite.com:3000",
			"wss://www.mysite.com",
			"wss://www.mysite.com:3000",
			"https://mysite.com",
			"https://mysite.com:3000",
			"https://www.mysite.com",
			"https://www.mysite.com:3000",
		},
		Compression:      false,
		HandshakeTimeout: 5 * time.Second,
	},
	DisableShortFirstPing: true,
}
// Initialize new server with options
ns, err := server.NewServer(opts)
if err != nil {
	panic(err)
}

// Start the server via goroutine
go ns.Start()

// Wait for server to be ready for connections
if !ns.ReadyForConnections(2 * time.Second) {
	panic("could not start the server (is another instance running on the same port?)")
}

fmt.Printf("Nats AppServer Name: %q\n", ns.Name())
fmt.Printf("Nats AppServer Addr: %q\n", ns.Addr())

// Connect to server
nc, err := nats.Connect(ns.ClientURL())
if err != nil {
	panic(err)
}

// This is the chat broker
_, err = nc.Subscribe("chat.say", func(msg *nats.Msg) {
	fmt.Printf("Got: %q\n", msg.Data)
	err = nc.Publish("chat.room", msg.Data)
	if err != nil {
		panic(err)
	}
})
if err != nil {
	panic(err)
}

_, err = nc.Subscribe("govatar.female", func(msg *nats.Msg) {
	if err != nil {
		panic(err)
	}
	var img image.Image
	// always female and random
	img, err = govatar.Generate(govatar.FEMALE)
	if err != nil {
		panic(err)
	}
	var buf bytes.Buffer
	err = jpeg.Encode(&buf, img, &jpeg.Options{Quality: 80})
	if err != nil {
		panic(err)
	}
	err = msg.Respond([]byte("data:image/jpeg;base64," + base64.StdEncoding.EncodeToString(buf.Bytes())))
	if err != nil {
		log.Printf("Respond error: %s", err)
	}
	// noErr(err)
})
if err != nil {
	panic(err)
}

r := chi.NewRouter()
srv.mux = r

r.Use(middleware.CleanPath)
r.Use(middleware.Logger)
compressor := middleware.NewCompressor(flate.DefaultCompression,
	"application/wasm", "text/css", "image/svg+xml" /*, "application/javascript"*/)
r.Use(compressor.Handler)
r.Use(middleware.Recoverer)

listener, err := net.Listen("tcp", ":443")
if err != nil {
	panic(err)
}

mainServer := &http.Server{
	Addr:      listener.Addr().String(),
	TLSConfig: tlsConfig,
}

// try to build the final browser location
hostURL := url.URL{
	Scheme: "https",
	Host:   mainServer.Addr,
}

log.Printf("Serving at %s\n", hostURL.String())

// This is the frontend handler (go-app) and will "pick up" any route
// which is not handled by the backend. It then will load the frontend
// and navigate it to this router.
srv.mux.Handle("/*", ah)

// registering our stack as the handler for the http server
mainServer.Handler = srv.Mux()

// Creating some graceful shutdown system
shutdown := make(chan struct{})
go func() {
	listener = netutil.LimitListener(listener, 100)
	defer func() { _ = listener.Close() }()

	err := mainServer.ServeTLS(listener, "", "")
	if err != nil {
		if err == http.ErrServerClosed {
			fmt.Println("AppServer was stopped!")
		} else {
			log.Fatal(err)
		}
	}
	// when run by "mage watch/run" it will break mage
	// before actually exiting the server, which just looks
	// strange but is okay after all
	// time.Sleep(2 * time.Second) // just for testing
	close(shutdown)
}()

// Setting up signal capturing
stop := make(chan os.Signal, 1)
signal.Notify(stop, os.Interrupt)
// Waiting for SIGINT (kill -SIGINT <pid> or Ctrl+c )
<-stop
shutdownServer(mainServer, shutdown)
fmt.Println("Program ended")

}
// shutdownServer stops the server gracefully
func shutdownServer(server http.Server, shutdown chan struct{}) {
fmt.Println("\nStopping AppServer gracefully")
ctx, cancel := context.WithTimeout(context.Background(), 5time.Second)
defer cancel()
fmt.Println("Send shutdown!")
if err := server.Shutdown(ctx); err != nil {
log.Fatal(err)
}
fmt.Println("Waiting for server to shutdown!")
<-shutdown
fmt.Println("AppServer is shutdown!")
}

Well, if your backend uses TLS and you could verify that it works, the question remains if you use the correct setup for the client, which means that you need to use a custom dialer and add the SkipTLS option when connecting. We had the NATS guys add this option to the go-client library. We also published some code that can be used with and without TLS websockets: natswasm.go.
If you still have problems, you may need show more of your code, so we could actually compile it and try to get it to work.

Thank you for your assistance. Much appreciated!!!!
I checked and do believe I am using the custom dialer correctly. But heck
something is surely wrong with my understanding. And I would like it to
work - core design pattern
I am not confident with pull-requests etc. So I did it my way. I checked
out a clone of the original master branch (yours) and created a new "
*test" *branch.
A folder contains the certs I know I should not do this. But the domain is
my test domain.
You can find the code here:
https://github.com/brucebotes/go-nats-app.git
Please browse and see if I missed something. You are very familiar with the
code ...
Many thanks.
On Mon, 24 Jul 2023 at 21:32, Hans Raaf @.***> wrote:

Well, if your backend uses TLS and you could verify that it works, the
question remains if you use the correct setup for the client, which means
that you need to use a custom dialer and add the SkipTLS option when
connecting. We had the NATS guys add this option to the go-client library.
We also published some code that can be used with and without TLS
websockets: natswasm.go
https://github.com/metatexx/mxx/blob/main/natswasm/natswasm.go.
If you still have problems, you may need show more of your code, so we
could actually compile it and try to get it to work.
—
Reply to this email directly, view it on GitHub
https://github.com/oderwat/go-nats-app/issues/6#issuecomment-1648492542,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABN6M5X7C3HAU6S7YRKUBJLXR3ETDANCNFSM6AAAAAA2V4JS7I
.
You are receiving this because you authored the thread.Message ID:
@.***>

I got your version to run. But I had to replace the domain and certificates and such. We usually use a domain that resolves to a local address, like "local3.somedomain.com" that resolves to <IP_ADDRESS> (in this case) because <IP_ADDRESS> usually is taken by stuff on our machines. But anyway.
You should first check if you can use nats --server wss://<IP_ADDRESS>:3000 sub test and see if that connects and works. It did for me. However, the website still did not work. I was struggling and did not understand what was going wrong until added "Proxyman" in the middle just to see that the request actually ends up with a 403 (which is not displayed anywhere when debugging, afais). As the nats-cli client is connecting, it was clear that it has to do with the browser (as usual).
I made the following modification which made it work:
SameOrigin: false,
AllowedOrigins: []string{},

So it has to do with the same origin policy. I was too tired to figure out what the origin should be. Anything "sane" did not work. I have to confess that I do not need where it fails and that I had to debug all the code. We use an external NATS cluster, and it uses the distributed access model (JTW+NKey) to make sure that only allowed clients can connect.

Hans, I am SO GRATEFUL for your assistance. I really have limited knowledge
working with TLS/SSL. Nats is also relatively new to me - although I have
used it in the past with a micro service training course - Stephen Grider
on Udemy. Wonderful stuff.
I agree, when I commented the embedded part out and used an external
instance of nats.io, it worked. But it is important for me to have it
embedded, even the web assets into a single file. I want to enhance my
chances for hosting - maybe fly.io.
Thus there is interaction between the net/http code when embedding. I will
look into the local3.samedomain.com concept. I now know the issue is not
the code ( or a bug in nats) but the topology of the domains etc which I
have no idea off....
Nevertheless, THANK you for the great example and support in the open
source space. We really appreciate  your contribution to enhance and expand
our competency in the real world.
On Tue, 25 Jul 2023 at 01:21, Hans Raaf @.***> wrote:

I got your version to run. But I had to replace the domain and
certificates and such. We usually use a domain that resolves to a local
address, like "local3.somedomain.com" that resolves to <IP_ADDRESS> (in this
case) because <IP_ADDRESS> usually is taken by stuff on our machines. But
anyway.
You should first check if you can use nats --server wss://<IP_ADDRESS>:3000
sub test and see if that connects and works. It did for me. However, the
website still did not work. I was struggling and did not understand what
was going wrong until added "Proxyman" in the middle just to see that the
request actually ends up with a 403 (which is not displayed anywhere when
debugging, afais). As the nats-cli client is connecting, it was clear that
it has to do with the browser (as usual).
I made the following modification which made it work:
SameOrigin: false,
AllowedOrigins: []string{},
So it has to do with the same origin policy. I was too tired to figure out
what the origin should be. Anything "sane" did not work. I have to confess
that I do not need where it fails and that I had to debug all the code. We
use an external NATS cluster, and it uses the distributed access model
(JTW+NKey) to make sure that only allowed clients can connect.
—
Reply to this email directly, view it on GitHub
https://github.com/oderwat/go-nats-app/issues/6#issuecomment-1648750859,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABN6M5WEVPBQN6AQZYEJSH3XR37OPANCNFSM6AAAAAA2V4JS7I
.
You are receiving this because you authored the thread.Message ID:
@.***>

Did it not work, when you remove the same origin check? I think it should.
You may want to check out: https://github.com/mlctrez/go-nats-app, he added a proxy into the formula to have the same origin for the HTTP and web server, like it is in a traditional setup.
But I also would not recommend having the internal NATS server. You can create a cluster on fly.io (see: https://github.com/fly-apps/nats-cluster/) or just use NGS (https://docs.synadia.com/ngs/guides).
Running a single NATS server on a cheap VPS can also be an option. Having three of them can serve a fairly significant number of users, too. I believe you can create that for less than $20 a month, and it may host some DB and other stuff too if needed. It is never too early to learn a bit about hosting.
For the client, there is not really a difference where the NATS server is running. It would be more important to have the backend data (DBs, for example) on the same machine as the services and the Nats-Server. So you do not end up with a lot of RTT between them.
The reason to work with an integrated NATS server that we have is running a leaf-node with the whole server deployed on a client computer. For example, by using WebView to create an executable that runs the app on Windows or OSX. The integrated NATS server will then contact the cluster and is used to store data locally without the need to go over the network, but still be able to use NATS for the processing of all data. One could also use the internal NATS server to simplify conversation between the frontend and the backend in an isolated app.

Thank you so much. No, unfortunately I could not get it to work :(.
I will be exploring/testing the mlctrex reverse proxy approach ( based on
gin - I am a chi fan) simply for learning and better understanding. Just
maybe, I can get the TLS to work...
But I have come to a similar conclusion. I will opt for the decentralised
approach. Yea, I will have to manage TLS certs at more than one location,
not too much of a risk these days. Sharing TLS and addressing network
configs is hard.
There is very little effort and less complexity going for the external
approach. The Nats strengths are simplicity and robustness (QoS) and
embedding the server may compromise its strengths which I am experiencing.
Not a good idea. It is very difficult to ring fence when there are issues.
I get the reasoning for the embedded approach and leaf-nodes, makes a lot
of sense for "off-line" modes  and recovery etc. Let Nats figure that out.
Having a Nats client in the WASM service of a PWA is also a fantastic idea.
It fascinated me,
Again thank for valuable time and assistance. Most appreciated.
Ps the fly.io nats-cluster looks very promising, co hosting. Thank you for
info,
On Tue, 25 Jul 2023 at 13:23, Hans Raaf @.***> wrote:

Did it not work, when you remove the same origin check? I think it should.
You may want to check out: https://github.com/mlctrez/go-nats-app, he
added a proxy into the formula to have the same origin for the HTTP and web
server, like it is in a traditional setup.
But I also would not recommend having the internal NATS server. You can
create a cluster on fly.io (see: https://github.com/fly-apps/nats-cluster/)
or just use NGS (https://docs.synadia.com/ngs/guides).
Running a single NATS server on a cheap VPS can also be an option. Having
three of them can serve a fairly significant number of users, too. I
believe you can create that for less than $20 a month, and it may host some
DB and other stuff too if needed. It is never too early to learn a bit
about hosting.
For the client, there is not really a difference where the NATS server is
running. It would be more important to have the backend data (DBs, for
example) on the same machine as the services and the Nats-Server. So you do
not end up with a lot of RTT between them.
The reason to work with an integrated NATS server that we have is running
a leaf-node with the whole server deployed on a client computer. For
example, by using WebView to create an executable that runs the app on
Windows or OSX. The integrated NATS server will then contact the cluster
and is used to store data locally without the need to go over the network,
but still be able to use NATS for the processing of all data. One could
also use the internal NATS server to simplify conversation between the
frontend and the backend in an isolated app.
—
Reply to this email directly, view it on GitHub
https://github.com/oderwat/go-nats-app/issues/6#issuecomment-1649645309,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABN6M5WOBE7XKCGCUTR3UT3XR6UC3ANCNFSM6AAAAAA2V4JS7I
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi Mr Oderwat.
Well done and thank you for your advice and support. (This includes
https://github.com/mlctrez/go-nats-app, from  mlctrez
https://github.com/mlctrez) and there is the go-app from *maxence-charriere
(*https://github.com/maxence-charriere/go-app).
The TLS works really well with the proxy and the embedded Nats Server. It
like  having 4+ components in one,

Web server - backend
Embedded frontend
Embedded Nats server
Embedded Caddy. (reverse proxy)
"and the bonus - a PWA with WASM - thank you Maxence and Hans for
go-app

A huge learning curve for me! Awesome stuff!. I cannot thank all of you
enough.
I do agree that it is not ideal, but this does give me an edge for a very
powerful and manageable proposition. Easy devops etc.
Thank you Hans for your guidance, I am lost for words.
On Tue, 25 Jul 2023 at 14:14, Bruce Botes @.***> wrote:

Thank you so much. No, unfortunately I could not get it to work :(.
I will be exploring/testing the mlctrex reverse proxy approach ( based on
gin - I am a chi fan) simply for learning and better understanding. Just
maybe, I can get the TLS to work...
But I have come to a similar conclusion. I will opt for the decentralised
approach. Yea, I will have to manage TLS certs at more than one location,
not too much of a risk these days. Sharing TLS and addressing network
configs is hard.
There is very little effort and less complexity going for the external
approach. The Nats strengths are simplicity and robustness (QoS) and
embedding the server may compromise its strengths which I am experiencing.
Not a good idea. It is very difficult to ring fence when there are issues.
I get the reasoning for the embedded approach and leaf-nodes, makes a lot
of sense for "off-line" modes  and recovery etc. Let Nats figure that out.
Having a Nats client in the WASM service of a PWA is also a fantastic idea.
It fascinated me,
Again thank for valuable time and assistance. Most appreciated.
Ps the fly.io nats-cluster looks very promising, co hosting. Thank you
for info,
On Tue, 25 Jul 2023 at 13:23, Hans Raaf @.***> wrote:

Did it not work, when you remove the same origin check? I think it should.
You may want to check out: https://github.com/mlctrez/go-nats-app, he
added a proxy into the formula to have the same origin for the HTTP and web
server, like it is in a traditional setup.
But I also would not recommend having the internal NATS server. You can
create a cluster on fly.io (see:
https://github.com/fly-apps/nats-cluster/) or just use NGS (
https://docs.synadia.com/ngs/guides).
Running a single NATS server on a cheap VPS can also be an option. Having
three of them can serve a fairly significant number of users, too. I
believe you can create that for less than $20 a month, and it may host some
DB and other stuff too if needed. It is never too early to learn a bit
about hosting.
For the client, there is not really a difference where the NATS server is
running. It would be more important to have the backend data (DBs, for
example) on the same machine as the services and the Nats-Server. So you do
not end up with a lot of RTT between them.
The reason to work with an integrated NATS server that we have is running
a leaf-node with the whole server deployed on a client computer. For
example, by using WebView to create an executable that runs the app on
Windows or OSX. The integrated NATS server will then contact the cluster
and is used to store data locally without the need to go over the network,
but still be able to use NATS for the processing of all data. One could
also use the internal NATS server to simplify conversation between the
frontend and the backend in an isolated app.
—
Reply to this email directly, view it on GitHub
https://github.com/oderwat/go-nats-app/issues/6#issuecomment-1649645309,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABN6M5WOBE7XKCGCUTR3UT3XR6UC3ANCNFSM6AAAAAA2V4JS7I
.
You are receiving this because you authored the thread.Message ID:
@.***>


Charts are not shown on Openhab Android APP

Hi,
I'm using your code in my openhab installation. Works like a charm from the browser but not on Android app.
I tried to include in sitemap direct grafana link, and it work, so I think there is someting in your code that avoid charts to be shown on android app.
Can you helpme about this?
Kindly regarda
Marco

@marcolino7 I've added a comment in issue #2 with some details on how to get the code with charts working in the openHAB Android App. Hopefully that works out well for you too!

HI,
I make it work.
Thanks

That's great!


[Bug]: Line Authoring not working.

Describe the bug
Line authoring does not display author's name, date, nor is the colour working.

Relevant errors (if available) from notifications or console (CTRL+SHIFT+I)
No response
Steps to reproduce
Install plugin, sync github, activate line authoring.
Expected Behavior
No response
Addition context
No response
Operating system
Windows
Installation Method
None
Plugin version
2.24.2.

Do you still experience this issue on the latest version 2.24.3 ?
Are there any errors in the console (CTRL+SHIFT+I)? And make sure you open a file, that's already committed.