Change Logical Name for new DB EXport

Is your feature request related to a problem? Please describe.
I am trying Export and DB backup to a new DB with a new name on the same server using the Export-RubrikDatabase. This is for a new test environment refresh where we need to make a copy of a bunch of DBs at a certain point in time.
Describe the solution you'd like
Getting error
WARNING: user_error
WARNING: Logical name 'DB_PS' does not map to any of the backup files in the snapshot.
Describe alternatives you've considered
ForEach ($DB in $DBs){
    Write-Host "Getting Snapshots for:" $DB.Name -ForegroundColor Cyan
    $SnapShot = Get-RubrikSnapshot -id $DB.ID -Latest
    $Dest = Get-RubrikSQLInstance -Hostname $ServerName -Name $InstanceName
    $DestDBName = $DB.Name + "_PS"
    $DestDBLog = $DestDBName +"_LOG"
    $targetfiles = @()
    $targetfiles += @{logicalName=$DestDBName ;exportPath='G:\Data\'}
    $targetfiles += @{logicalName=$DestDBLog;exportPath='G:\Data\'}

    Write-Host "Exporting Snapshot:" $SnapShot.date "To:" $Dest.ID -ForegroundColor Cyan
    Export-RubrikDatabase -Id $DB.ID -RecoveryDateTime $SnapShot.date -TargetInstanceId $Dest.ID -TargetDatabaseName $DestDBName -TargetFilePaths $targetfiles -FinishRecovery

}

Additional context
No response

This is not something we can fix as logical names of a database cannot be changed during a recovery operation. You are able to change the path and physical name though.

Thanks… we will look into changing how we organize our DBs then.
Nick Thoman
Senior Systems Engineer | Information Services
Brethren Mutual Insurance Company
w:<PHONE_NUMBER>
m:<PHONE_NUMBER>
e<EMAIL_ADDRESS>For support requests please email<EMAIL_ADDRESS>On Jan 29, 2024, at 1:47 PM, Chris Lumnah @.***> wrote:

This is not something we can fix as logical names of a database cannot be changed during a recovery operation. You are able to change the path and physical name though. — Reply to this email directly, view it on GitHub, or unsubscribe. You
This is not something we can fix as logical names of a database cannot be changed during a recovery operation. You are able to change the path and physical name though.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/rubrikinc/rubrik-sdk-for-powershell/issues/847*issuecomment-1915351331__;Iw!!E3q_Ug!2LyZbKFdFT_RZe7e5KdDfzVa2pgBhy5axTDN8CUyenVSLSACSdUZJ6oiMuPnq0k6LF4V3y_M19lPAR-CvB3D0A$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ALQNAZ3DWSUCVEBDQWT6FV3YQ7VETAVCNFSM6AAAAABCHFEPHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVGM2TCMZTGE__;!!E3q_Ug!2LyZbKFdFT_RZe7e5KdDfzVa2pgBhy5axTDN8CUyenVSLSACSdUZJ6oiMuPnq0k6LF4V3y_M19lPAR8hNuMCDw$.
You are receiving this because you authored the thread.Message ID: @.***>

Thanks @clumnah - closing at it appears there is nothing we can do here...


RestTemplate call "I/O error on GET request for" - PCFDEV - Eureka

I'm getting below error when I make resttemplate call as below.
To me it looks like random generated hostname is not accessible.
I use pcfdev-v0.30.2+PCF1.11.0-windows ,  pcfdev-v1.2.0-windows. spring-boot.2.1.3.
// Get movie details
MovieDetails movieDetails =
restTemplate.getForObject("http://movie-details-service/jpamovies/" + movieId, MovieDetails.class);
"message": "I/O error on GET request for "http://movie-details-service/jpamovies/2\": 7c6b7bdc-36ca-4b0f-77d9-f2f2; nested exception is java.net.UnknownHostException: 7c6b7bdc-36ca-4b0f-77d9-f2f2",
I'm having Eureka server registration as below.

Application
AMIs
Availability Zones
Status

MOVIE-CATALOG-SERVICE
n/a (1)
(1)
UP (1) - bdd136c3-c3e6-4333-4840-fcd0

MOVIE-DETAILS-SERVICE
n/a (1)
(1)
UP (1) - 7c6b7bdc-36ca-4b0f-77d9-f2f2

Please help to resolve the issue.

This does not seem to be related to Eureka (as shown above the registration data seems fine), consider checking the docs for the client used (Spring).


Update pyiron_atomistics optional dependency

And get it as an extras require in setup.py so dependabot sees it

from maggma.utils import get_flat_models_from_model
    ImportError: cannot import name 'get_flat_models_from_model' from 'maggma.utils' (/usr/share/miniconda3/envs/my-env/lib/python3.11/site-packages/maggma/utils.py)

Because mpi-api is 0.37.2, not 0.39.5, because pyiron_atomistics allows a lower bound of 0.37.0. I've actually run into exactly this before, I just forgot that conda is allowing that broken lower bound.


--daemon-start-if-needed needs ability to set custom command for starting the daemon

Hi,
I'm using gevent and I start pytest with:
 python -m gevent.monkey --module pytest

Using --daemon-start-if-needed breaks because it starts pytest normally. Thus need a config to set how to auto start the daemon.

Are you able to solve this using PYTEST_DAEMON_PYTEST_NAME (see the readme on usage)?
I believe with this:
https://pypi.org/project/pytest-gevent/
You can change the value from pytest to pytest-gevent
Its almost midnight for me so I'll check back on this tomorrow morning or afternoon. Thanks!

Actually looking at the implementation that might not work because it's expecting a module name
args = [
                sys.executable,
                "-m",
                pytest_name,
                "--daemon",
                "--daemon-port",
                str(port),
            ]

But maybe writing a wrapper module would work.

I believe with this:
https://pypi.org/project/pytest-gevent/

That library is deprecated and it says to use my way in their readme https://github.com/asottile-archive/pytest-gevent

Actually looking at the implementation that might not work because it's expecting a module name

Yep it won't work, just tried some different variations.

But maybe writing a wrapper module would work.

That could be it.

Did the wrapper end up resolving your issue? I'm also curious about your use case because the library doesn't support running tests concurrently (it will turn off xdist via the workaround feature, for example), but maybe you need it for other reasons.

I wasn't able to work on the wrapper. Use case for this library is just faster test execution locally while working on the codebase.
xdist isn't related to this case, though I'm blocked there too on gevent https://github.com/pytest-dev/pytest-xdist/issues/1069. I'll probably use pytest-split for multi-core running of test suite.

I don't recommend rerunning your whole test suite. The intended use case is the same as you see in the gif in the readme; you execute single tests or test files from the IDE. You would use the CI to automatically run a test suite for your project and in that case you wouldn't see a benefit from using the hot reloader.

I agree, I never mentioned xdist, you did here:

I'm also curious about your use case because the library doesn't support running tests concurrently

Maybe you thought (gevent => concurrent-tests)?

Another thing is that sys.executible in that arg list means it reuses the same application that ran it. You could change your executable to something like this (ChatGPT threw this together):
#!/bin/bash

# Store the first argument, which is assumed to be '-m'
module_flag=$1

# Store the second argument, which is the name of the module, e.g., 'pytest'
module_name=$2

# Remove the first two arguments from the list of all arguments
shift 2

# Run the python command with the modified module and the remaining arguments
python -m gevent --module $module_name "$@"

You would then invoke it like this:
my_script -m pytest --daemon-start-if-needed <path to test>

That script doesn't work. I'll just use a runfile from the IDE for now, thank you.


Allow users to configure or ignore checks

Users may want to ignore certain checks, like #1, or configure other checks, like #8. What do you think about adding a configuration file that lets users enable/disable or pass options to checks? My team would be happy to work on this if you'd be willing to accept the feature.

Fixed via your PR. Thanks.


Implement compiler-rt's 128-bit integer conversions to/from floats

This PR provides Crystal ports for these compiler-rt functions:

__floattidf (Int128#to_f64!)
__floattisf (Int128#to_f32!)
__floatuntidf (UInt128#to_f64!)
__floatuntisf (UInt128#to_f32!)
__fixdfti (Float64#to_i128!)
__fixsfti (Float32#to_i128!)
__fixunsdfti (Float64#to_u128!)
__fixunssfti (Float32#to_u128!)

This allows those conversions to be done on Windows.

https://github.com/crystal-lang/crystal/blob/b06c7b25241add5bd30de6a94f90ef1d25aa945d/spec/compiler/codegen/arithmetics_spec.cr#L3-L16
Does this still apply with the PR?

The functions themselves work as intended but the ABI issue probably remains (same as __divti3).

Regarding @BlobCodes' comment: The float to uint conversions in arithmetics_specs should be expected to work with this spec. See  https://github.com/straight-shoota/crystal/runs/4356998682?check_suite_focus=true:
--- c/spec/compiler/codegen/arithmetics_spec.cr
+++ w/spec/compiler/codegen/arithmetics_spec.cr
@@ -3,18 +3,15 @@ require "../../spec_helper"
 # Int128 and UInt128 specs do not pass on win32 because of missing compiler-rt symbols
 {% unless flag?(:win32) %}
   SupportedInts            = [UInt8, UInt16, UInt32, UInt64, UInt128, Int8, Int16, Int32, Int64, Int128]
-  SupportedIntsConversions = {
-    to_i8: Int8, to_i16: Int16, to_i32: Int32, to_i64: Int64, to_i128: Int128,
-    to_u8: UInt8, to_u16: UInt16, to_u32: UInt32, to_u64: UInt64, to_u128: UInt128,
-  }
 {% else %}
   SupportedInts            = [UInt8, UInt16, UInt32, UInt64, Int8, Int16, Int32, Int64]
-  SupportedIntsConversions = {
-    to_i8: Int8, to_i16: Int16, to_i32: Int32, to_i64: Int64,
-    to_u8: UInt8, to_u16: UInt16, to_u32: UInt32, to_u64: UInt64,
-  }
 {% end %}

+SupportedIntsConversions = {
+  to_i8: Int8, to_i16: Int16, to_i32: Int32, to_i64: Int64, to_i128: Int128,
+  to_u8: UInt8, to_u16: UInt16, to_u32: UInt32, to_u64: UInt64, to_u128: UInt128,
+}
+
 describe "Code gen: arithmetic primitives" do
   describe "&+ addition" do
     {% for type in SupportedInts %}

@HertzDevil can you make the proposed changes? 🙇


[pgadmin] envFrom is not supported in variables

https://github.com/rowanruseler/helm-charts/pull/147


Replace Bungee Components with Kyori

Bungee code has been removed completely, some legacy Bukkit stuff too. The only ChatColor stuff remaining is stuff that's immediately used for messages, display names, and lore.

Closed for GPLv3 licensing issues.


Stock History

How could a stock history be implemented to keep track of how many sales or additions were made to a given product?

That is exactly how the package works :) Ik keeps track of stock mutations, with ->stock([date]) you can check the stock on a given date. With ->stockMutations you can get alle mutations for a stockable (eg product) model.


Add missing prototype for FIPS callback

Fixes #2533
The call to FIPS_crypto_set_id_callback() was added in revision a43cfd7bb1fc681d563e, but there is no prototype for it in <openssl/fips.h>.

Travis failure is unrelated (see #4866)

FWIW: this solved my issue in https://github.com/openssl/openssl/issues/4864

I have tested this patch for all combinations of VC-WIN32/VC-WIN64A, vc9/vc11/vc14/vc15 and dll's/static libs with OpenSSL-Fips-2.0.16. 'passed all tests' in all 16 instances.

Thanks for your effort, @Jan-E!

Rebased without changes to fix the fatalerrtest and get some green lights from the build bots.

Pushed. Thanks.

Thanks for your effort, @Jan-E!

My pleasure. I gave all of you due credit:
https://www.apachelounge.com/viewtopic.php?p=36237#36237


generate coverage report with //tools:coverage

Use genhtml to generate the coverage report locally. This may differ
from the one generated by codecov.
Update check workflow to use the coverage data produced
//tools:coverage.
Change-Id: I1c76edf442167dd978aa8568a607033c8f4f65d3

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.87%. Comparing base (bb1d986) to head (a517e99).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #64   +/-   ##
=======================================
  Coverage   76.87%   76.87%
=======================================
  Files          25       25
  Lines         307      307
  Branches        8        8
=======================================
  Hits          236      236
  Misses         71       71

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


ENH: Add python wrapping for CudaCommon

This wrapping differs from the one that used to be in RTX by the fact that it only wraps the interface for floating type data and only for image dimensions included in ${ITK_WRAP_IMAGE_DIMS} and vector components included in ${ITK_WRAP_VECTOR_COMPONENTS}.
RTX will have to wrap by itself everything else it needs.

@LucasGandel

I think the best strategy would be to mimick the wrapping of GPUCommon, there is no reason to limit the wrapping to float. See here.

I think the best strategy would be to mimick the wrapping of GPUCommon, there is no reason to limit the wrapping to float. See here.

Sounds good, we will add the following types (from itkGPUImage.wrap) :
UNIQUE(types "UC;UL;${ITKM_IT};${WRAP_ITK_SCALAR}")
UNIQUE(vector_types "${WRAP_ITK_VECTOR_REAL};${WRAP_ITK_COV_VECTOR_REAL}")

I applied the modifications related to the previous comments. Let me know if you think something should be changed again :)


AWS Pack not returning results in array.

The behavior was recently changed to no long put the results in to an array.  This most likely is fine but it is not backwards compatible.  We need to either reimplement this or add a giant disclaimer.

Lots of changes to AWS pack over last 18 months, don't think this is relevant any more.


Example: cmdlet swapped with summary

Hello team, Kindly correct the Examples of cmdlet "Get-ADSyncObjectsWithInheritanceDisabled" as summary swapped with cmdlet.

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

ID: 82a4128e-9afe-01b8-1b90-9a5fa101a361
Version Independent ID: 097caa74-01be-edbf-cdfd-40541387d2d4
Content: Azure AD Connect: ADSyncConfig PowerShell Reference
Content Source: articles/active-directory/hybrid/reference-connect-adsyncconfig.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@valkyriei Thank you for pointing this out . We will have this reviewed and updated.

@valkyriei Thank you for pointing that out. We have updated the document . It will be live with the next release cycle in the next 24-48 hours.
Thank you.


Release build of perf example is broken

Running ./gradlew assembleRelease against the performance example fails, seemingly due to proguard obfuscation or GMScore version drift.
My hunch is that something is wrong with the drop of GMScore from google3/integ into the SDK.
> Task :app:compileReleaseJavaWithJavac FAILED
~/quickstart-android/perf/app/src/main/java/com/google/firebase/quickstart/perfmon/MainActivity.java:64: error: cannot access zze
        mTrace.start();
              ^
  class file for com.google.android.gms.internal.firebase-perf.zze not found

None of these proguard rules fix it:
-keep com.google.firebase.perf.metrics.**
-keepnames com.google.firebase.perf.metrics.**
-keepnames com.google.android.gms.internal.firebase-perf.**
-keep com.google.android.gms.internal.firebase-perf.**

I am running ./gradlew assembleRelease

@kurtisnelson I am able to run ./gradlew assembleRelease on the master branch from both the root directory of this repo and the perf directory.
Maybe you've got something bad in your build cache?  This also is the kind of thing that Travis would catch in this repo, so I am a bit skeptical that there's a real problem here and it's more likely that one of us has a bad setup.

I think this was a machine config issue, haven't heard any other reports.  Closing for now, happy to re-open if anyone else can repro.

I have a similar issue. It caused by using Java 9 instead of 8.


Prune requirements

[ ] Additional function parameters, change functionality or change defaults?
[ ] New estimator in cr.tl.estimators?
[ ] New kernel in cr.tl.kernels?
[ ] New gene trend model in cr.ul.models?
[ ] New plotting function in cr.pl?
[x] Other?

I think 2 can be removed:

ipywidgets (not necessary)
tzlocal (not sure why this is present, think @Marius1311 you've had some problem when it was missing)
wrapt? (use simple decorators)
h5py (was due to some error in 3.0.0 [strings as bytearrays], should be fine now)
future_fstrings (needed only for <3.6, which we no longer support)
anndata (done through scanpy)

Also numba>=0.53.0 should be checked to see what the problem (if any) is.

Sound good to me!

closed via #571


error: core mapping not found for darwin:arm64

when execute make dev.run cannot run on Mac M1

There is no mapping for the core auto-downloder on ARM Macs, so needed cores can be downloaded and placed into the cores folders manually from here: https://buildbot.libretro.com/nightly/apple/osx/arm64/latest/. Default cores are described here: https://github.com/giongto35/cloud-game/blob/master/configs/config.yaml#L157.

Feel free to test it with the latest commit. Mupen64 is not present in the official repository (RetroArch) so you could try to build it yourself (https://github.com/libretro/mupen64plus-libretro-nx) on your system and put it in the cores folder.


Query HealthScore as part as Health Service checks

In addition to the direct service pings to Event Hub, Cosmos DB and Storage, this adds a query to the Log Analytics workspace to also take the HealthScore into account.
Challenge is yet that the score seems to be not always super reliable and thus the health service might report unhealthy for a few queries.

@nielsams

@nielsams what do you think, should we merge this in its current state already or rather wait?

Looks very good! My only suggestion would be to also parameterize the Kusto query. That may change a few times as we evolve the model.

Ok, so now you can disable individual health checks by adding an app setting to the health service like:

Then that service is not getting checked:

will be migrated to Connected


Ctrl+K not captured while on JupyterLab

Describe the bug
Ctrl+K is not captured while on JupyterLab.
Expected behavior
Ctrl+K works consistently everywhere in Orchest.
To Reproduce
Steps to reproduce the behavior:

Go to the pipeline editor
Hit Ctrl+K, see command palette open
Enter JupyterLab
Hit Ctrl+K, nothing happens or the browser captures the event (on Firefox, address bar gains focus)

Environment

OS: Linux Mint
Browser: Firefox
Orchest's version (in the settings page): v2022.03.6

@ricklamers @iannbing Anything we can do here given that JupyterLab lives in an iframe? I guess we can simply catch certain commands (in this case Ctrl+K) before sending it to the iframe?


Documentation on uploading files is incorrect - Must open in binary form

Description
Describe your issue here.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[ ] question
[X] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[X] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[X] I've read and agree to the Code of Conduct.
[X] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
slackclient version: 1.3.1
python version: 3.7.3
OS version(s): Windows 10 Pro Version 1809
Steps to reproduce:

Install slackclient & Python
Start a working client
Open a photo without specifying any modes (as shown on [https://slack.dev/python-slackclient/basic_usage.html#uploading-files])
Use api_call 'files.upload' to upload the photo to a given slack channel.

Example code:
if os.path.isfile(path):
with open(path) as photo:
client.api_call(
'files.upload',
channels=channel_id,
file=photo,
title=filename
)
Solution: Have the documentation specify opening the file in read and binary modes.
Sample function for uploading a photo, which could be genericized to any file:
def upload_photo(client, channel, path, filename):
""" Takes the slackclient, path to file, and desired name of the file to upload, and uploads it.
"""
if os.path.isfile(path):
with open(path, 'rb') as photo:
client.api_call(
'files.upload',
channels=channel,
file=photo,
filename=filename,
title=filename
)
Expected result:
Given file (in my case, a photo) to be uploaded to the given channel.
Actual result:
Without the read binary modes, I get this error.
UnicodeDecodeError: 'charmap' codec can't decode byte 0x8f in position 57: character maps to <undefined>
Attachments:
None

I appear to be having a number of issues with demonstrating the code in my issue. I apologize, as I am newer to GitHub.

Hi @coopervk, Thanks for opening an issue about this. Our documentation can definitely use an update. I'm working on this now with @splinterific and we'll be changing this in v2.

Thanks for reporting this. The latest document and samples in the repository are surely correct. Allow me to close this issue now.

https://slack.dev/python-slackclient/basic_usage.html#uploading-files
https://github.com/slackapi/python-slackclient/blob/master/integration_tests/samples/readme/uploading_files.py


Creating Android export template fails

Godot version:
2a4c528d067826dd1af865c93c3dc945c9a0e196
OS/device including version:
Windows 10 64x
Issue description:
`C:\Build Godot\godot\platform\android\java>.\gradlew build --info
Initialized native services in: C:\Users\GoCrayons.gradle\native
Found daemon DaemonInfo{pid=10468, address=[20075fda-61ef-43c3-8408-486eba4c81b1 port:61000, addresses:[/<IP_ADDRESS>, /0:0:0:0:0:0:0:1]], state=Idle, lastBusy=1576818897201, context=DefaultDaemonContext[uid=ca3c7cf4-07cc-4585-a9e4-495d5d3a7a6c,javaHome=C:\Program Files (x86)\Java\jdk1.8.0_181,daemonRegistryDir=C:\Users\GoCrayons.gradle\daemon,pid=10468,idleTimeout=10800000,priority=NORMAL,daemonOpts=-XX:MaxMetaspaceSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx512m,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]} however its context does not match the desired criteria.
At least one daemon option is different.
Wanted: DefaultDaemonContext[uid=null,javaHome=C:\Program Files (x86)\Java\jdk1.8.0_181,daemonRegistryDir=C:\Users\GoCrayons.gradle\daemon,pid=7812,idleTimeout=null,priority=NORMAL,daemonOpts=-Xmx1536m,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]
Actual: DefaultDaemonContext[uid=ca3c7cf4-07cc-4585-a9e4-495d5d3a7a6c,javaHome=C:\Program Files (x86)\Java\jdk1.8.0_181,daemonRegistryDir=C:\Users\GoCrayons.gradle\daemon,pid=10468,idleTimeout=10800000,priority=NORMAL,daemonOpts=-XX:MaxMetaspaceSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx512m,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]
Looking for a different daemon...
The client will now receive all logging from the daemon (pid: 14344). The daemon log file: C:\Users\GoCrayons.gradle\daemon\5.1.1\daemon-14344.out.log
Starting 19th build in daemon [uptime: 2 hrs 17 mins 7.941 secs, performance: 93%, no major garbage collections]
Using 4 worker leases.
Starting Build
Settings evaluated using settings file 'C:\Build Godot\godot\platform\android\java\settings.gradle'.
Projects loaded. Root project using build file 'C:\Build Godot\godot\platform\android\java\build.gradle'.
Included projects: [root project 'godot', project ':app', project ':lib']

Configure project :
Evaluating root project 'godot' using build file 'C:\Build Godot\godot\platform\android\java\build.gradle'.

Configure project :app
Evaluating project ':app' using build file 'C:\Build Godot\godot\platform\android\java\app\build.gradle'.
Creating configuration androidTestUtil
Creating configuration compile
Creating configuration apk
Creating configuration provided
Creating configuration api
Creating configuration implementation
Creating configuration runtimeOnly
Creating configuration compileOnly
Creating configuration wearApp
Creating configuration annotationProcessor
Creating configuration androidTestCompile
Creating configuration androidTestApk
Creating configuration androidTestProvided
Creating configuration androidTestApi
Creating configuration androidTestImplementation
Creating configuration androidTestRuntimeOnly
Creating configuration androidTestCompileOnly
Creating configuration androidTestWearApp
Creating configuration androidTestAnnotationProcessor
Creating configuration testCompile
Creating configuration testApk
Creating configuration testProvided
Creating configuration testApi
Creating configuration testImplementation
Creating configuration testRuntimeOnly
Creating configuration testCompileOnly
Creating configuration testWearApp
Creating configuration testAnnotationProcessor
Creating configuration debugCompile
Creating configuration debugApk
Creating configuration debugProvided
Creating configuration debugApi
Creating configuration debugImplementation
Creating configuration debugRuntimeOnly
Creating configuration debugCompileOnly
Creating configuration debugWearApp
Creating configuration debugAnnotationProcessor
Creating configuration androidTestDebugCompile
Creating configuration androidTestDebugApk
Creating configuration androidTestDebugProvided
Creating configuration androidTestDebugApi
Creating configuration androidTestDebugImplementation
Creating configuration androidTestDebugRuntimeOnly
Creating configuration androidTestDebugCompileOnly
Creating configuration androidTestDebugWearApp
Creating configuration androidTestDebugAnnotationProcessor
Creating configuration testDebugCompile
Creating configuration testDebugApk
Creating configuration testDebugProvided
Creating configuration testDebugApi
Creating configuration testDebugImplementation
Creating configuration testDebugRuntimeOnly
Creating configuration testDebugCompileOnly
Creating configuration testDebugWearApp
Creating configuration testDebugAnnotationProcessor
Creating configuration releaseCompile
Creating configuration releaseApk
Creating configuration releaseProvided
Creating configuration releaseApi
Creating configuration releaseImplementation
Creating configuration releaseRuntimeOnly
Creating configuration releaseCompileOnly
Creating configuration releaseWearApp
Creating configuration releaseAnnotationProcessor
Creating configuration testReleaseCompile
Creating configuration testReleaseApk
Creating configuration testReleaseProvided
Creating configuration testReleaseApi
Creating configuration testReleaseImplementation
Creating configuration testReleaseRuntimeOnly
Creating configuration testReleaseCompileOnly
Creating configuration testReleaseWearApp
Creating configuration testReleaseAnnotationProcessor
Parsing the SDK, no caching allowed
SDK initialized in 813 ms

Configure project :lib
Evaluating project ':lib' using build file 'C:\Build Godot\godot\platform\android\java\lib\build.gradle'.
Creating configuration androidTestUtil
Creating configuration compile
Creating configuration publish
Creating configuration provided
Creating configuration api
Creating configuration implementation
Creating configuration runtimeOnly
Creating configuration compileOnly
Creating configuration wearApp
Creating configuration annotationProcessor
Creating configuration androidTestCompile
Creating configuration androidTestPublish
Creating configuration androidTestProvided
Creating configuration androidTestApi
Creating configuration androidTestImplementation
Creating configuration androidTestRuntimeOnly
Creating configuration androidTestCompileOnly
Creating configuration androidTestWearApp
Creating configuration androidTestAnnotationProcessor
Creating configuration testCompile
Creating configuration testPublish
Creating configuration testProvided
Creating configuration testApi
Creating configuration testImplementation
Creating configuration testRuntimeOnly
Creating configuration testCompileOnly
Creating configuration testWearApp
Creating configuration testAnnotationProcessor
Creating configuration debugCompile
Creating configuration debugPublish
Creating configuration debugProvided
Creating configuration debugApi
Creating configuration debugImplementation
Creating configuration debugRuntimeOnly
Creating configuration debugCompileOnly
Creating configuration debugWearApp
Creating configuration debugAnnotationProcessor
Creating configuration androidTestDebugCompile
Creating configuration androidTestDebugPublish
Creating configuration androidTestDebugProvided
Creating configuration androidTestDebugApi
Creating configuration androidTestDebugImplementation
Creating configuration androidTestDebugRuntimeOnly
Creating configuration androidTestDebugCompileOnly
Creating configuration androidTestDebugWearApp
Creating configuration androidTestDebugAnnotationProcessor
Creating configuration testDebugCompile
Creating configuration testDebugPublish
Creating configuration testDebugProvided
Creating configuration testDebugApi
Creating configuration testDebugImplementation
Creating configuration testDebugRuntimeOnly
Creating configuration testDebugCompileOnly
Creating configuration testDebugWearApp
Creating configuration testDebugAnnotationProcessor
Creating configuration releaseCompile
Creating configuration releasePublish
Creating configuration releaseProvided
Creating configuration releaseApi
Creating configuration releaseImplementation
Creating configuration releaseRuntimeOnly
Creating configuration releaseCompileOnly
Creating configuration releaseWearApp
Creating configuration releaseAnnotationProcessor
Creating configuration testReleaseCompile
Creating configuration testReleasePublish
Creating configuration testReleaseProvided
Creating configuration testReleaseApi
Creating configuration testReleaseImplementation
Creating configuration testReleaseRuntimeOnly
Creating configuration testReleaseCompileOnly
Creating configuration testReleaseWearApp
Creating configuration testReleaseAnnotationProcessor
Parsing the SDK, no caching allowed
SDK initialized in 0 ms
debug|native Gradle local properties file not found at C:\Build Godot\godot\platform\android\java\local.properties
debug|native No CMake version was specified in build.gradle. Choosing a suitable version.
debug|native Trying to locate CMake in local SDK repository.
debug|native - Downloading '3.6.4111459'.
debug|native Trying to locate CMake in PATH.

FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring project ':lib'.

Invalid revision: 3.15.19101501-MSVC_2

Try:
Run with --stacktrace option to get the stack trace. Run with --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 17s`
Steps to reproduce:
Minimal reproduction project:
N/A

for 3.2, it was changed a bit.
https://docs.godotengine.org/en/latest/development/compiling/compiling_for_android.html#building-the-export-templates

for 3.2, it was changed a bit.
https://docs.godotengine.org/en/latest/development/compiling/compiling_for_android.html#building-the-export-templates

Still getting the same problem :(
`SDK initialized in 0 ms
debug|native Gradle local properties file not found at C:\Build Godot\godot\platform\android\java\local.properties
debug|native No CMake version was specified in build.gradle. Choosing a suitable version.
debug|native Trying to locate CMake in local SDK repository.
debug|native - Downloading '3.6.4111459'.
debug|native Trying to locate CMake in PATH.
FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring project ':lib'.

Invalid revision: 3.15.19101501-MSVC_2

Try:
Run with --stacktrace option to get the stack trace. Run with --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 1s`

I've fixed it :)
I'm not sure what the problem is exactly to be honest, but this is what I did:
I've downloaded this: https://cmake.org/files/v3.15/
Then I just updated the build.grade file with the appropriate cmake version: https://prnt.sc/qeibc1.


Does not return a non-zero exit status when sync function generation fails

The make-sync-function script returns an exit status of zero in all cases, even if the script failed (e.g. because the document definitions file does not exist). It should return a non-zero exit status in failure cases.
To reproduce the issue, execute the following commands:
$ ./make-sync-function /path/to/file-that-does-not-exist.js /path/to/generated-sync-function.js
$ echo $?

The second command displays the exit status from the previous command. It should be non-zero when the document definitions file does not exist, but currently it is always zero.

Resolved by https://github.com/Kashoo/synctos/pull/37.


"Maximum call stack size exceeded" when populating lexical relationships

Link to reproduction
No response
Describe the Bug
There appears to be an intermittent infinte recursion when populating relationships within the lexical plugin. This following error will be repeated several times in the logs,
RangeError: Maximum call stack size exceeded
    at /home/node/app/node_modules/.pnpm/payload@2.11.0_typescript@5.3.3_webpack@5.90.1/node_modules/payload/dist/fields/hooks/afterRead/promise.js:240:60
    at traverseFields (/home/node/app/node_modules/.pnpm/payload@2.11.0_typescript@5.3.3_webpack@5.90.1/node_modules/payload/dist/fields/hooks/afterRead/traverseFields.js:13:12)
    at Array.forEach (<anonymous>)
    at /home/node/app/node_modules/.pnpm/payload@2.11.0_typescript@5.3.3_webpack@5.90.1/node_modules/payload/dist/fields/hooks/afterRead/traverseFields.js:14:49
    at promise (/home/node/app/node_modules/.pnpm/payload@2.11.0_typescript@5.3.3_webpack@5.90.1/node_modules/payload/dist/fields/hooks/afterRead/promise.js:82:54)
    at Object.populationPromise (/home/node/app/node_modules/.pnpm/@payloadcms+richtext-lexical@0.6.1_@lexical+clipboard@0.12.6_payload@2.11.0_typescript@5.3.3_yjs@13.6.12/node_modules/@payloadcms/richtext-lexical/dist/index.js:607:85)
    at richTextRelationshipPromise (/home/node/app/node_modules/.pnpm/@payloadcms+richtext-lexical@0.6.1_@lexical+clipboard@0.12.6_payload@2.11.0_typescript@5.3.3_yjs@13.6.12/node_modules/@payloadcms/richtext-lexical/dist/populate/richTextRelationshipPromise.js:67:5)
    at recurseRichText (/home/node/app/node_modules/.pnpm/@payloadcms+richtext-lexical@0.6.1_@lexical+clipboard@0.12.6_payload@2.11.0_typescript@5.3.3_yjs@13.6.12/node_modules/@payloadcms/richtext-lexical/dist/populate/richTextRelationshipPromise.js:24:18)
    at Array.forEach (<anonymous>)
    at /home/node/app/node_modules/.pnpm/@payloadcms+richtext-lexical@0.6.1_@lexical+clipboard@0.12.6_payload@2.11.0_typescript@5.3.3_yjs@13.6.12/node_modules/@payloadcms/richtext-lexical/dist/populate/richTextRelationshipPromise.js:27:30

This will then usually be followed by the following MongoDB error and an app crash

  [Symbol(errorLabels)]: Set(0) {}
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
    at /home/node/app/node_modules/.pnpm/mongodb@4.17.1/node_modules/mongodb/lib/utils.js:348:66
    at /home/node/app/node_modules/.pnpm/mongodb@4.17.1/node_modules/mongodb/lib/sessions.js:530:9
    at commandHandler (/home/node/app/node_modules/.pnpm/mongodb@4.17.1/node_modules/mongodb/lib/sessions.js:478:33)
    at Transaction.transition (/home/node/app/node_modules/.pnpm/mongodb@4.17.1/node_modules/mongodb/lib/transactions.js:120:15)
MongoRuntimeError: Attempted illegal state transition from [TRANSACTION_ABORTED] to [TRANSACTION_ABORTED]
        throw new error_1.MongoRuntimeError(`Attempted illegal state transition from [${this.state}] to [${nextState}]`);

/home/node/app/node_modules/.pnpm/mongodb@4.17.1/node_modules/mongodb/lib/transactions.js:120
    at /home/node/app/node_modules/.pnpm/payload@2.11.0_typescript@5.3.3_webpack@5.90.1/node_modules/payload/dist/fields/hooks/afterRead/promise.js:240:60
    at traverseFields (/home/node/app/node_modules/.pnpm/payload@2.11.0_typescript@5.3.3_webpack@5.90.1/node_modules/payload/dist/fields/hooks/afterRead/traverseFields.js:13:12)
    at Array.forEach (<anonymous>)
    at /home/node/app/node_modules/.pnpm/payload@2.11.0_typescript@5.3.3_webpack@5.90.1/node_modules/payload/dist/fields/hooks/afterRead/traverseFields.js:14:49
    at promise (/home/node/app/node_modules/.pnpm/payload@2.11.0_typescript@5.3.3_webpack@5.90.1/node_modules/payload/dist/fields/hooks/afterRead/promise.js:82:54)
    at Object.populationPromise (/home/node/app/node_modules/.pnpm/@payloadcms+richtext-lexical@0.6.1_@lexical+clipboard@0.12.6_payload@2.11.0_typescript@5.3.3_yjs@13.6.12/node_modules/@payloadcms/richtext-lexical/dist/index.js:607:85)
    at richTextRelationshipPromise (/home/node/app/node_modules/.pnpm/@payloadcms+richtext-lexical@0.6.1_@lexical+clipboard@0.12.6_payload@2.11.0_typescript@5.3.3_yjs@13.6.12/node_modules/@payloadcms/richtext-lexical/dist/populate/richTextRelationshipPromise.js:67:5)
    at recurseRichText (/home/node/app/node_modules/.pnpm/@payloadcms+richtext-lexical@0.6.1_@lexical+clipboard@0.12.6_payload@2.11.0_typescript@5.3.3_yjs@13.6.12/node_modules/@payloadcms/richtext-lexical/dist/populate/richTextRelationshipPromise.js:24:18)
    at Array.forEach (<anonymous>)
    at /home/node/app/node_modules/.pnpm/@payloadcms+richtext-lexical@0.6.1_@lexical+clipboard@0.12.6_payload@2.11.0_typescript@5.3.3_yjs@13.6.12/node_modules/@payloadcms/richtext-lexical/dist/populate/richTextRelationshipPromise.js:27:30

To Reproduce
I haven't been able to put together a consistent method of reproducing this error. It seems to happen somewhat randomly. The error also stops happening as soon as the app crashes and restarts.
It might be related to a block containing an array field being used within a richtext field.
Payload Version
2.11.0
Adapters and Plugins
richtext-lexical, db-mongodb, bundler-webpack, plugin-cloud-storage (s3)

I have been trying to track down this issue with my production admin for over a month now and still no luck.
My feeling is that its related to a block that can be added to the lexical content, which in turn has a lexical field in it.  This second level lexical editor doesn't have any way to embed a third level lexical editor, or have the relationship feature, but it does allow links to pages.   The page link can reference the page that is currently being edited, as this is the only way to add # anchor links within the page as far as I can see.   I am wondering if this is what caused it in my case but I cannot verify this easily as it only crashes from time to time.
@AlessioGr Is there any guidance you can give here?  Or is there a way to add a stop condition to the lexical recursion?
This is quite a problematic issue as it fails sporadically, and causes pages of our site to not be found.

I think it likely is being caused by a lexical editor containing a block with another lexical editor. We have a similar configuration. We do not have any recursive references within these blocks though.
It doesn't happen reliably so my feeling is that it could be some sort of race condition.

So I have been debugging this again today as I managed to run into the issue pretty regularly and my suspicion was confirmed about the cause in https://github.com/payloadcms/payload/issues/5101#issuecomment-1956358339 .
When I fetch my page I want to be able to have a depth of 2 so that I can grab all the associated data in a single request, but there is no way to specify how deep the link feature should recurse. This seems to lead to situations where the link resolved the linked page, but that page could be itself (or another page that references this one).  This causes the rich text recursion to never halt, or at least exhaust the maximum stack depth.  It feels like the link field would only ever need to fetch the associated doc with a depth of 0, as I assume that most use cases for this feature, devs just want to be able to get a handle on the url of the doc being linked to?
@AlessioGr I know you know way more about the inner workings here, does this make sense or ring true at all?
So far the only way I see to definitely prevent this issue is to always fetch data with a depth of 0, and thats going to be quite a rewrite from my side, so would love to hear your thinking before I go down that path.

I noticed this error in the report:
MongoRuntimeError: Attempted illegal state transition from [TRANSACTION_ABORTED] to [TRANSACTION_ABORTED]
Possibly related to #4350

I think that is the route I will take, I am just concerned about some underlying issue here as changing the max depth on a call from 1 -> 2 causes this issue, and the same document occurs in the output in various nest depths 10 times (if I manage to get it to work without the service hitting the max call stack.
The most complicated part of this page is this structure:
PAGE: {
    content: LexicalEditor with FAQ block
}

FAQBlock: {
   faqs: Array<question, answers>
   where answer = LexicalEditor
}

In this relatively simple setup, if the page happens to link to itself to jump to content in the page, why would 10 instances of the page be returned in the json structure when the max depth is 2?
https://github.com/payloadcms/payload/discussions/5141 would help this situation as there seems no other way to do in-page jump links with out rewriting the LinkFeature or linking to the same page, which seems to be very problematic.
I feel though that the LinkFeature or content field as a whole should have some way to customise the required depth.  Otherwise, any time you want to fetch Page A which links to Page B, and Page B links to Page A, and also have a depth of 2 to collect related data to the page (Author and AuthorImage for ex), there will be a much larger response than needed from the rest api.  Is there a way to do this that I am missing?

This started happening to me quite recently in prod environment, I'm using payload ^2.11.1 and richtext-lexical of ^0.7.0. The error seems to start happening in 4 hours after deploy. Here's a log of my deployment:
[13:09:16] INFO (payload): Connected to MongoDB server successfully!
[13:09:16] INFO (payload): Starting Payload...
[13:09:16] INFO (payload): Payload Admin URL: /admin
    CORS_ALLOWED_ORIGINS: [redacted]
    CSRF_DOMAIN_WHITELIST: [redacted]
(node:1) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
[13:09:17] ERROR (payload): There is an error with the email configuration you have provided. Error: Invalid login: [redacted] Error: authentication failed: authentication failure
[16:57:42] ERROR (payload): RangeError: Maximum call stack size exceeded
    at /home/node/app/node_modules/@payloadcms/richtext-lexical/dist/populate/richTextRelationshipPromise.js:27:30
    at Array.forEach (<anonymous>)
    at recurseRichText (/home/node/app/node_modules/@payloadcms/richtext-lexical/dist/populate/richTextRelationshipPromise.js:24:18)
    at richTextRelationshipPromise (/home/node/app/node_modules/@payloadcms/richtext-lexical/dist/populate/richTextRelationshipPromise.js:67:5)
    at Object.populationPromise (/home/node/app/node_modules/@payloadcms/richtext-lexical/dist/index.js:609:85)
    at promise (/home/node/app/node_modules/payload/dist/fields/hooks/afterRead/promise.js:82:54)
    at /home/node/app/node_modules/payload/dist/fields/hooks/afterRead/traverseFields.js:14:49
    at Array.forEach (<anonymous>)
    at traverseFields (/home/node/app/node_modules/payload/dist/fields/hooks/afterRead/traverseFields.js:13:12)
    at afterRead (/home/node/app/node_modules/payload/dist/fields/hooks/afterRead/index.js:21:40)
... repeatedly until the CMS shutdowns itself

The thing with this error is that, when it starts appearing, no richtext containing resource can be accessed. And after a while the CMS shutdowns maybe because of how much error that has been happening over a period of time.
Weirdly, this error happened in my codebase where I disable any relationship linking to the LinkFeature in richtext-lexical by specifying the code below in all of my collection config:
admin: {
  enableRichTextLink: false,
  enableRichTextRelationship: false
}

In the meantime I'll implement a live patch using patch-package to disable richTextRelationship population all together.

Yikes! Just stumbled on this and it's making me wonder if it is the cause of our performance issues across large swaths of our site. cc @jmikrut and @AlessioGr for visibility because this seems like potentially a really big problem. We're seeing API payloads of 2MB+ and response times upwards of 5s on pages with lots of links in a rich text and this seems like it must be the cause.

Oh man... I just removed a Rich Text with a bunch of links from our homepage and the response went from nearly 7s to a few milliseconds. And just to be clear, this is running on some hefty heft infra (like $3k/month aws stuff).

Unclear to me where this is coming from, but potentially could pass depth through from props or something?
https://github.com/payloadcms/payload/blob/916923071a2c28077326bfd2059d1665ef47e94f/packages/richtext-lexical/src/field/features/Link/populationPromise.ts#L56C9-L56C14

When I fetch my page I want to be able to have a depth of 2 so that I can grab all the associated data in a single request, but there is no way to specify how deep the link feature should recurse.

This seems to lead to situations where the link resolved the linked page, but that page could be itself (or another page that references this one). This causes the rich text recursion to never halt, or at least exhaust the maximum stack depth.

When I fetch my page I want to be able to have a depth of 2 so that I can grab all the associated data in a single request, but there is no way to specify how deep the link feature should recurse.

So I would say it's definitely expected for the link feature to behave that way. It should resolve relations the same way a relationship field outside of lexical would resolve them.
That said, especially since you currently cannot have different depths for different fields, I'm thinking of adding a maxDepth property to the lexical Relationship / Link / Upload features.

This seems to lead to situations where the link resolved the linked page, but that page could be itself (or another page that references this one). This causes the rich text recursion to never halt, or at least exhaust the maximum stack depth.

This is strange indeed. The depth always gets passed through, so recursion should eventually halt when the max depth is reached. I have tested this with different types of field configurations and was not able to reproduce this - it always works as expected. Would be great if you're able to provide a reproduction, even if the issue only occurs 20% of times.
I'll work on a maxDepth property for certain nodes in the meantime, as that's a genuinely useful feature and would fix this issue for you

Sorry just one more thought - because we have 20+ collection types available in a LinkFeature relationship, I think in order to stop the "recursion" we'd have to go through and edit maxDepth on every single relationship field across all the collection right?

The more I think about this, the more I'm convinced this is actually a bug in LinkFeature but could be expected behavior in RelationshipFeature? I would expect LinkFeature to really be nothing but a "link", which is to say a label and a URL and really nothing more. The docs seem to hint at this when describing the behavior of RelationshipFeature (I think implying that LinkFeature is just an "inline" link):

RelationshipFeature: Allows you to create block-level (not inline) relationships to other documents

I know this is tricky because payload doesn't have a intrinsic concept of a URL, I'd expect to maybe have to specify a generateURL callback or something?

@ssyberg maxDepth has made it into both 2.x and 3.x for Link, Relationship and Upload fields now!
Additionally, in 3.x, I have revamped any handling of population within lexical to match exactly how population works in Slate or core relationships - and I believe that would fix that maximum call stack size exceeded issue, given that it only happened within lexical.

I would expect LinkFeature to really be nothing but a "link", which is to say a label and a URL and really nothing more. The docs seem to hint at this when describing the behavior of RelationshipFeature (I think implying that LinkFeature is just an "inline" link

Yep! You're exactly right. LinkFeatures could be used as inline relationships. Also, in 3.x, it should be much easier to customize the link fields in a way where you can completely remove the internal doc relationship, and only have a URL and label field.

I think in order to stop the "recursion" we'd have to go through and edit maxDepth on every single relationship field across all the collection right?

Only the ones within the link fields. LinkFeature.maxDepth automatically sets the one of the internal link doc. For other custom relationships you added to the link fields, you'll have to add the maxDepth there.
You do not have to add maxDepth to any populated fields, as the maxDepth of the parent relationship field "trickles down" to all future relationships. Pretty much all it does is override depth from that point on.

I think I brought this up in another feature request long ago, but I've long felt maxDepth should be discarded or renamed and it should be defaultDepth which is the depth that gets returned by default, but that you always can override it in a given API call by specifying depth directly.

It does behave a bit differently. maxDepth only sets / overrides the depth for sub-field population if it's smaller than the depth which was provided. That said, defaultDepth, or maybe even minDepth, could be an interesting feature request.

Amazing!


[APIM 3.0.0][UX] The Store application is named as "WSO2 developer portal", but the react application has the "store" context

The store application is renamed from API Store to API Developer portal. However, the context of the application is still store/. Should we rename it to developer?

fixed.


新增 keystone vars 文件以便编译 rpm; wording

这个 PR 实现什么功能/修复什么问题:
新增 keystone vars 文件以便编译 rpm
是否需要 backport 到之前的 release 分支:

release/2.10.0

Codecov Report

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

@@            Coverage Diff            @@
##           master   #1018      +/-   ##
=========================================
+ Coverage    7.91%   7.94%   +0.02%
=========================================
  Files         355     355
  Lines       56236   56236
=========================================
+ Hits         4450    4466      +16
+ Misses      51391   51378      -13
+ Partials      395     392       -3

Flag
Coverage Δ

#aFlag
7.94% <ø> (+0.02%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/util/seclib2/seclib.go
95.74% <0%> (+4.25%)
:arrow_up:

pkg/util/rbacutils/rabc.go
77.52% <0%> (+4.56%)
:arrow_up:

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 b799835...67718be. Read the comment docs.

/cherrypick release/2.10.0

/lgtm
/approve


Need to recover files on VirtFS disk that crashed and won't boot

Describe the issue
I installed an Ubuntu 22.04 UTM VM on an M1 MacBook Air to do some software development and the VM crashed and now won't boot. Using grub I am able to see my software using the ls and cat commands and the files seem to be ok. I would like to know if there is some way to recover the directory containing my software using grub or some other method.
Configuration

UTM Version: 4.1.5 (74)
macOS Version: 13.2 (22D49)
Mac Chip: M1

Crash log
Using the Console.App I am unable to find the crash report, but there is an error message printed when trying to restart the VM: QEMU exited from an error: qemu-aarch64-softmmu: -drive if=pflash,unit=1,file=/Volumes/OS X Snow Leopard 10.6.8/UTM/SongBook.utm/Data/efi_vars.fd: Could not read image for determining its format: Input/output error.
Debug log
I am unable to find the debug log after clicking the debug option, however I found a report under Diagnostic Reports I can attach if it would be useful.
Upload VM
I have attached the compressed config.plist.
If I can provide more information please let me know. Any help would;d be much appreciated.
Regards,
Daryl

You can create or use another Linux VM to do this.
Install qemu (through brew), and you'll get the qemu-nbd binary, which you can use to serve the file like this:
qemu-nbd -f qcow2 <path-to-disk-image>
Then in the VM install nbd-client if it isn't already installed, then run

sudo modprobe nbd
sudo nbd-client <ip_of_host> /dev/nbd0 -nofork
sudo mount /dev/nbd0 /mnt/

After that, you can access the files inside /mnt/ and can copy them to your host.

Hi @ktprograms,
Thanks for your response. I tried to follow your instructions but when I ran the nbd-client command I got the following message:
E: option eaten by 42 mice
Here are the steps I too:

Installed new UTM Ubuntu VM

On the host (my MacBook Air) I ran the command:
$ qemu-nbd -f qcow2 /Volumes/OS\ X\ Snow\ Leopard\ 10.6.8/UTM/SongBook.utm/Data/80F9E8D8-80F8-4E91-AD77-24A6BA8E8998.qcow2
The command did not produce any errors. The command did not return to command line and ps shows that it is running.

Booted the new Linux VM and ran the following commands:
a. # modprobe nbd
b. # nbd-client <IP_ADDRESS>  /dev/nbd0 -nofork  // The ip <IP_ADDRESS> is the MacBook Air
This command yielded the error:
nbd-client invalid option — ‘o’
E: option eaten by 42 mice
I then tried the same command using two dashes with the —no-fork option and this time it produced the:
E: option eaten by 42 mice
c. I then proceeded to try the mount anyway and got the following error:
# mount /dev/nbd0 /mnt/
This command returned: mount: /mnt: can’t read superblock on /dev/nbd0.

@ktprograms, I appreciate your response and your help. Can you tell if I messed up any of the instructions or if there is anything else I can try?
Thanks again and Best Regards,
Daryl Williams

On Feb 3, 2023, at 01:50, ktprograms @.***> wrote:
You can create or use another Linux VM to do this.
Install qemu (through brew), and you'll get the qemu-nbd binary, which you can use to serve the file like this:
qemu-nbd -f qcow2
Then in the VM install nbd-client if it isn't already installed, then run
sudo modprobe nbd
sudo nbd-client <ip_of_host> /dev/nbd0 -nofork
sudo mount /dev/nbd0 /mnt/
After that, you can access the files inside /mnt/ and can copy them to your host.
—
Reply to this email directly, view it on GitHub https://github.com/utmapp/UTM/issues/4987#issuecomment-1415515019, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH7A5I2CIYFOKYEQCUOLCLWVTIGBANCNFSM6AAAAAAUPQBREU.
You are receiving this because you authored the thread.

I'm not sure what I did wrong before but I was able to successfully run the nbd-client <IP_ADDRESS>  /dev/nbd0 -nofork command and it reported the following:
Warning: the oldstyle protocol is no longer supported.
This method now uses the new style protocol with a default export
Negotiation: ..size = 65536MB
Connected /dev/nbd0
and when I try the mount: sudo mount /dev/nbd0 /mnt/
I get the following error:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program or other error.
Using grub I am still able to ls and cat the files I need to recover  and they still appear to be ok. Any help would be greatly appreciated.
Daryl

The nofork flag isn't important, so you can just remove it.
I didn't realise it wasn't a Linux VM that you needed to recover the files from. What filesystem is on the disk?
As for the mount error, it's probably because the disk has multiple partitions. Run partprobe /dev/nbd0 and then fdisk /dev/nbd0 (both as root/sudo), and then try to mount the correct partition.

Thanks for following up, but I guess I didn’t explain very well. The VM that crashed is indeed using Linux Ubuntu 22.04, the host system is my MacBook laptop. I created a second Linux VM to follow your instructions.I did after a few tries get the nbd-client command to work but thart’s when I got the error:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nbd0, missing codepage or helper program or other error.
I’m pretty sure the VM that crashed was using an ext4 filesystem. I ran part probe (as root) and the ran disk but got an error:
fdisk: cannot open /dev/nbd0: Inappropriate ioctl for device
I’m still hoping there’s a way to. Get at those files.
Thanks again for your help.
Daryl

On Feb 3, 2023, at 16:46, ktprograms @.***> wrote:
The nofork flag isn't important, so you can just remove it.
I didn't realise it wasn't a Linux VM that you needed to recover the files from. What filesystem is on the disk?
As for the mount error, it's probably because the disk has multiple partitions. Run partprobe /dev/nbd0 and then fdisk /dev/nbd0 (both as root/sudo), and then try to mount the correct partition.
—
Reply to this email directly, view it on GitHub https://github.com/utmapp/UTM/issues/4987#issuecomment-1416564518, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH7A5O26DKFMLLZI7443GTWVWRF7ANCNFSM6AAAAAAUPQBREU.
You are receiving this because you authored the thread.

The VM that crashed is indeed using Linux Ubuntu 22.04,
Oh, sorry. No worries, these instructions should still work.

After partprobe, what nbd devices do you see in /dev/?

Hi @ktprograms,
I forgot to run the qemu-nbd command the first time I tried your suggestion and I think that’s why it failed. I am now running the qemu-nbd command on my laptop and re-tried your suggestion a with somewhat better outcome. There three partitions on the virtual disk:
/dev/nbd0p1 2048    2203647   2201600   1G EDI System
/dev/nbd0p2 2203648 6397951   4194304   2G Linux filesystem
/dev/nbd0p3 6397952 134215679 127817728 60.9G Linux filesystem
I was able to mount /dev/nbdp01 and see the root filesystem but when I tried to mount /dev/nbd0p3 I got the following error:
mount: /mnt unknow filesystem type ‘LVM2_member’'
I don’t know yjat much about LVM so I guess I’ll start reading up on how to mount an LVM2_member volume…
Thanks again, I appreciate your help.
Daryl

On Feb 3, 2023, at 16:46, ktprograms @.***> wrote:
The nofork flag isn't important, so you can just remove it.
I didn't realise it wasn't a Linux VM that you needed to recover the files from. What filesystem is on the disk?
As for the mount error, it's probably because the disk has multiple partitions. Run partprobe /dev/nbd0 and then fdisk /dev/nbd0 (both as root/sudo), and then try to mount the correct partition.
—
Reply to this email directly, view it on GitHub https://github.com/utmapp/UTM/issues/4987#issuecomment-1416564518, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH7A5O26DKFMLLZI7443GTWVWRF7ANCNFSM6AAAAAAUPQBREU.
You are receiving this because you authored the thread.

Hi @ktprograms,
Just wanted to let you know I was finally able to recover my files using the instructions you provided. Two of the LVM volumes had the same vg-group name so I had to rename one of them and then I was able to mount the volume using the following commands:
vgdisplay  // Showed me both volume groups with the same name.
vgrename  newgrp-vg  // Rename the volume group
modprobe dm-mod
vgchange -ay
$ lvscan
mount /dev/newgrp-vg/ubuntu-lv  /mnt
Thanks again for all your help.
Daryl


GDExtension iOS export minimum OS version is hard coded 10.0

Godot version
Godot v4.1.1.stable
System information
macOS 13.6.1 - Vulkan (Compatibility) - AMD Radeon Pro 560X OpenGL Engine - Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 Threads)
Issue description
GDExtension code could use new c apis available in newer iOS. This hard coded minimum os version in Info.plist will cause rejection when submitting binary to App Store.
Steps to reproduce
Create a gdextension using fmemopen(), which is a new api since iOS 11. And submit the app to App Store, the submission will fail with error:

Minimal reproduction project
N/A

4.1.1 is outdated, 4.1.3 and 4.2 defaults to 12.0, for GDExtension you can use ios_min_version=VERSION command line argument. Also, you can use @available around your code. But it's probably enough to change min. version in the exported project (will be configurable on export in 4.3 - https://github.com/godotengine/godot/pull/84162).

Closing as per above comment, this seems resolved in 4.1.3 and 4.2.


🐛 [Bug] Problem with duplicate calls and GT Server

🐛 Bugreport

There was a problem reported twice of events be calculated twice for users if two calls happen simultaniously.
Is this permanently resolved?

Yes it is.
On GDT-Server I make sure that this change will be done only once.
I have tried locking db with lock table but that didn't work.
Now I write a lock file to hard disk while changing and remove it once done.


tour: wrong type in example

Context: https://tour.golang.org/basics/4
In description: "In this example, add takes two parameters of type int." but the strings type in code example in function "add"

I see func add(x int, y int) int {, click the Reset button on the right, someone probably changed the code (the tour saves local changes).


Entry Edit - Entry Type is not pre-populated

As the title States, is visible on the entry edit page

Fixed via: 38a2bc20fa613e9a7e33fe3f65d404684ec0b84e
The Framework should now be "useable"


(NSArray *)arrayOfColorsWithColorScheme:(ColorScheme)colorScheme for:(UIColor *)color flatScheme:(BOOL)isFlatScheme;

It seems to me that the compiler is looking for the method:
+ (NSArray *)arrayOfColorsWithColorScheme:(ColorScheme)colorScheme for:(UIColor *)color flatScheme:(BOOL)isFlatScheme;

but the method, found in NSArray+Chameleon.h/m is the following:
+ (NSArray *)arrayOfColorsWithColorScheme:(ColorScheme)colorScheme with:(UIColor *)color flatScheme:(BOOL)isFlatScheme;

(with should be for)

Whoops! I just realized this was apparently fixed 3 days ago! But when I pulled master today, I still had the same issue.
(https://github.com/VAlexander/Chameleon/commit/21230b0357f456d1c9a29deb4cd4aa11c2eb3999)

Hi @Mackarous! Thanks for looking into this. Just to make sure I understand correctly, you're using the latest version of Chameleon in your swift project, but it won't compile because it is still using the old + (NSArray *)arrayOfColorsWithColorScheme:(ColorScheme)colorScheme for:(UIColor *)color flatScheme:(BOOL)isFlatScheme; method?
I'm updating the example project now to properly call the updated method. Are you using cocoa pods?

Just updated the example project to reflect the recent changes. I also went back in and rather than completely obliterate the old method, I simply deprecated it, in favor of:
+ (NSArray *)arrayOfColorsWithColorScheme:(ColorScheme)colorScheme with:(UIColor *)color flatScheme:(BOOL)isFlatScheme;

Just updated cocoapods as well to 1.1.2. Everything should be working now. If you have any problems, feel free to open up a new issue.

Hey I totally didn't get any notifications over this. Just wanted to say thanks a lot! Looks great. I am not using cocoa pods right now as my project is in swift.


store/sqlite: quote column names

To make reserved keywords such as 'from' available in schemas.

111db0365ab8a9b545720c41332cfe7bc8e55594


'TorchOn' does not work on some Android devices.

.I'm using the latest pre release of BarcodeScanner.XF which is <IP_ADDRESS> - Pre. I'm trying to turn on the Torch while the camera is previewing and scanning by adding a button in the camera view and setting the property 'TorchOn' to True/False. But it only works on my Samsung SM-G390F device which has Android  9 / API Level 28. I tried using several other devices such as a Samsung Galaxy Note 9 with Android 10 / API Level 29 and a Samsung Galaxy Tab A (SM-T385) which also has Android 9 but it doesn't work.
This is the output when I tried to turn on the Torch in Samsung Galaxy Tab A. The torch doesn't turn on.
[LegacyRequestMapper] convertRequestMetadata - control.awbRegions setting is not supported, ignoring value
[LegacyRequestMapper] Only received metering rectangles with weight 0.
[ViewRootImpl@1932dc4[MainActivity]] ViewPostIme pointer 0
[ViewRootImpl@1932dc4[MainActivity]] ViewPostIme pointer 1
[UseCaseAttachState] Active and attached use case: [androidx.camera.core.ImageAnalysis-9122cabe-f4c6-4407-8406-b0141db4f7cd190324984, androidx.camera.core.Preview-7e2eacbd-77cd-453c-853f-47def64a4116237397620] for camera: 0
[CaptureSession] Attempting to submit CaptureRequest after setting
[CaptureSession] Issuing request for session.
[RequestQueue] Repeating capture request cancelled.
[RequestQueue] Repeating capture request set.
[LegacyRequestMapper] convertRequestMetadata - control.awbRegions setting is not supported, ignoring value
[LegacyRequestMapper] Only received metering rectangles with weight 0.

This is the output when I tried to turn on the Torch in Samsung SM-G390F. The torch turns on.
[ViewRootImpl@3a508a0[MainActivity]] ViewPostIme pointer 0
[ViewRootImpl@3a508a0[MainActivity]] ViewPostIme pointer 1
[UseCaseAttachState] Active and attached use case: [androidx.camera.core.Preview-b60ea37b-3d6c-462e-8114-bd53b70450b962989428, androidx.camera.core.ImageAnalysis-c397c380-7865-410a-8bfa-f087533a9dc4194412280] for camera: 0
[CaptureSession] Attempting to submit CaptureRequest after setting
[CaptureSession] Issuing request for session.

@JimmyPun610  Appreciate if you can look into this issue.

Hi @Ruvi1996 ,
Unfortunately, I do not have those devices to reproduce the bug, I would suggest you add the source directly for reference to see if you could get more information. This library is using AndroidX, my guess is hasFlashUnit returning false.
The source code would be in CameraViewRenderer.cs in ./Android/Renderer

Hey there,
These methods were there on v5.0.9 and worked without any issue. since I had a building issue on iOS with this version, I upgraded it to <IP_ADDRESS>-pre. Am I missing anything?

Thanks in advance
Amin


SQL server memory usage / performance

Hi,
I am seeing high memory usage when reading strings from SQL server:
sql_query = """select top 1 cast(name as char(1)) from mytable"""
dsn = ODBC.DSN(connection_string, prompt=false)
@time df1 = ODBC.query(dsn, sql_query)
@time df2 = ODBC.query(dsn, sql_query)
@time df3 = ODBC.query(dsn, sql_query)
@time df4 = ODBC.query(dsn, sql_query)
@time df5 = ODBC.query(dsn, sql_query)
@time df6 = ODBC.query(dsn, sql_query)
ODBC.disconnect!(dsn)
0.001646 seconds (249 allocations: 657.516 KB)
0.002606 seconds (257 allocations: 18.219 KB)
0.001265 seconds (249 allocations: 657.516 KB)
0.002547 seconds (257 allocations: 18.219 KB)
0.001312 seconds (249 allocations: 657.516 KB)
0.002832 seconds (257 allocations: 18.219 KB)
If i now change the query to return 2 chars instead of 1 and run the same code:
sql_query = """select top 1 cast(name as char(2)) from mytable"""
0.001709 seconds (249 allocations: 721.516 KB)
0.002964 seconds (257 allocations: 18.219 KB)
0.001308 seconds (249 allocations: 721.516 KB)
0.002769 seconds (257 allocations: 18.219 KB)
0.001378 seconds (249 allocations: 721.516 KB)
0.002496 seconds (257 allocations: 18.219 KB)
It looks like it uses 64 KB of memory for a single extra character. And in my code i run into performance issues with larger queries.
Also it seems like every other run has much lower memory usage. I am obviously running the query only once in my real code.
I am using ODBC 0.5.1 on julia 0.5.0 on windows.
I previously used ODBC 0.3.x with much lower memory usage (of the order of bytes per extra char) / better performance
Thanks, Gus

Hi,
I made this change: #149 and it runs (apparently) without ill effects. Thanks, Gus

Closed via #149


Migrate build from Grunt/Browserify to Webpack

I could be persuaded to work on this, but I can't get to it until Mid June probably.

I stumbled upon this as I am working on integrating leaflet-measure to the ipyleaflet jupyter widget. Is there any workaround?

This has been needed for a while. I haven't had much opportunity to look into it, but I will make an effort to make some progress this week.

This is done as of release 3.0.0

Great thanks @brandoncopeland


loan estimate explainer link swap

Changes
Fix newly reappeared links in loan estimate explainer that were swapped with each other.
Review

@amymok @virginiacc

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Looks good! :+1:


Update to code for Esoil in sparse vegetation.

I had intended to add this update to the original 4.2 release, but forgot about it until now.  This addresses issue #306.

@tbohn - can you address the comments in #309?

@bartnijssen - ready for you.

@tbohn: Can you show what the results of this change is?
@jhamman: Go ahead and merge after comments are addressed.

How should I show the results - should I attach a plot of ET before/after?

@tbohn - a plot of ET separate plots of E and T would be great.

First, some performance statistics at eddy covariance towers - mostly Ameriflux but also 5 other towers in Mexico:

Class
N
Old Median NSE
New Median NSE
Change

ENF
8
0.53
0.51
-0.02

DBF
2
0.61
0.57
-0.04

CSH
4
0.23
0.25
+0.02

OSH
8
0.61
0.62
+0.01

WSA
2
0.40
0.49
+0.09

SAV
1
0.50
0.53
+0.03

GRA
21
0.38
0.55
+0.17

(ENF = Evergreen Needleleaf Forest; DBF = Deciduous Broadleaf Forest; CSH = Closed Shrubland; OSH = Open Shrubland; WSA = Woody Savanna; SAV = Savanna; GRA = Grassland)
So, you can see that changes are minimal in forest biomes, but a big improvement in more sparsely-vegetated biomes such as savannas and grasslands.

(I fixed you table - nice try though :wink: )

Ah, so I just needed to insert a blank line between the non-table text and table text?

Here's an example of before and after the change, at the Santa Rita Mesquite Ameriflux Tower (Open Shrubland).
Old Model (NSE = 0.64):

New Model (NSE = 0.73):

As you can see, the main effect is to reduce Esoil a bit (primarily due to the RARC_SOIL of 100 s/m).
Here's another example, from Diablo (Grassland).
Old Model (NSE = 0.32):

New Model (NSE = 0.53):

I can include plots of other sites if you'd like to see more...

@jhamman and @bartnijssen - do you need me to provide any more test results for this?

This looks good to me.  Thanks for showing some results @tbohn.  @bartnijssen?

@tbohn: Thanks for the plots and explanations


When looking at the affiliated contacts for an account in SF1 the name is not shown

Only Role, Status and Start Date are shown. However, the affiliation Compact Layout does show Affiliation Name, Organization Name, and Contact Name. It seems like the Compact Layout shown is not defining the fields shown in the Record Preview Card.
Reported at https://powerofus.force.com/_ui/core/chatter/groups/GroupProfilePage?g=0F980000000CmVX&fId=0D58000001NRRcj

Or npe5__Contact__r.Name,  which would include the new standard Middle & Suffix fields if being used.

You can go one step further and make the name clickable by wrapping a hyperlink function around the name:
HYPERLINK("/"+ npe5__Contact__r.Id ,npe5__Contact__r.FirstName + ' ' + npe5__Contact__r.LastName)
Looks like you need to create a custom compact layout too cuz you can't edit the packaged one. Also if you need to access Affiliations from the parent you'll be viewing the related list, not the compact layout. As such your new formula field needs to be one of the first four columns in your related list. Don't like it? Vote this up: https://success.salesforce.com/ideaView?id=08730000000l5EpAAI


Update README.md

@liamkillion Can you elaborate on this version compatibility issue? Our omniauth-oauth2 dependency currently resolves to 1.6.0 and we're unsure if pinning omniauth-oauth2 to ~> 1.3 is going to break other OmniAuth strategies we use.

@aguynamedben  a version update to omniauth-oauth2, at version 1.6.0, introduced a change that breaks this gem - hope that helps!

@liamkillion Do you know what that change was?  We must get this gem fixed for multiple reasons.

Other gems have already set omniauth-oauth2 version to a minimum of 1.6, e.g. omniauth-google-oauth2.  Sites with multiple authentication sources are now stuck between a rock and a hard place.
There is an open CVE security vulnerability, currently unpatched, in omniauth, and when it gets fixed we must be able to update to the patched version.

Name: omniauth
Version: 1.9.1
Advisory: CVE-2015-9284
Criticality: High
URL: https://github.com/omniauth/omniauth/pull/809
Title: CSRF vulnerability in OmniAuth's request phase
Solution: remove or disable this gem until a patch is available!

We can't have a web of fixed dependencies preventing the upgrade.
    omniauth-oauth2 (1.6.0)
      oauth2 (~> 1.1)
      omniauth (~> 1.9)

CC @grnhse Please pay attention!

All of these patches are to lock the version dependency, and that is a terrible precedent to set.

Discovered the issue.  Version 1.4.0 of omniauth-oauth2 only had one tiny change, removing the callback_url override, and it broke a ton of oauth integration gems.  Those gems fixed the issue by redefining an explicit callback_url override in the same form as what had been removed.
      def callback_url
        full_host + script_name + callback_path
      end

PR coming soon.

PR with fix is here: https://github.com/grnhse/omniauth-greenhouse/pull/8

@NickMeves @jcmuller @tfrey7 @dianaliu @mtoneil @bouffy @tdphillipsjr @acaloiaro @hugomarcotte @evan-duncan @Adam262 @kbruccoleri @jooshbzm @Ataraxic
This is not a good look for Greenhouse.
This needs to be addressed.  It is a security issue.
Please also see #8
Please also note that this gem is dead as of now.  It is incompatible with the current major version of omniauth, and is a potentially a security risk.  There are frequently CVEs filed against the  omniauth family of gems, which in turn forces upgrades.  As this gem is incompatible with latest version is forces use of older, CVE-vulnerable, versions of the omniauth suite.  This is unacceptable.
Bundler could not find compatible versions for gem "omniauth":
  In Gemfile:
    omniauth (~> 2.0.0)

    omniauth-greenhouse was resolved to 1.3.1, which depends on
      omniauth (>= 1.3.1, < 2)

I am removing our Greenhouse integration.  I hope to see this situation improve.

This PR should be closed.


[CT-3504] [Bug] Invalid message when the connection to a PostgreSQL database fails

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
An invalid message is displayed when the connection to a PostgreSQL database fails.

Database Error
'utf-8' codec can't decode byte 0xe9 in position 103: invalid continuation byte

It seems that this message is new in 1.6.6.
Dbt debug 1.6.5 does not display it.
Expected Behavior
A more explicit message, for example :
FATAL:  password authentication failed for user "*****"
Steps To Reproduce
run dbt init
when prompting for the password set an invalid one
dtb debug
Relevant log output
pip install dbt-postgres==1.6.5
[...]
dbt debug
23:28:07  Running with dbt=1.6.5
23:28:07  dbt version: 1.6.5
23:28:07  python version: 3.11.6
23:28:07  python path: C:\Users\***\venv_python\dbt\Scripts\python.exe
23:28:07  os info: Windows-10-10.0.19045-SP0
23:28:07  Using profiles dir at C:\Users\***\.dbt
23:28:07  Using profiles.yml file at C:\Users\***\.dbt\profiles.yml
23:28:07  Using dbt_project.yml file at C:\Users\(***)\dbt_project.yml
23:28:07  adapter type: postgres
23:28:07  adapter version: 1.6.5
23:28:07  Configuration:
23:28:07    profiles.yml file [OK found and valid]
23:28:07    dbt_project.yml file [OK found and valid]
23:28:07  Required dependencies:
23:28:07   - git [OK found]

23:28:07  Connection:
23:28:07    host: ***
23:28:07    port: 5430
23:28:07    user: ***
23:28:07    database: ***
23:28:07    schema: public
23:28:07    connect_timeout: 10
23:28:07    role: None
23:28:07    search_path: None
23:28:07    keepalives_idle: 0
23:28:07    sslmode: None
23:28:07    sslcert: None
23:28:07    sslkey: None
23:28:07    sslrootcert: None
23:28:07    application_name: dbt
23:28:07    retries: 1
23:28:07  Registered adapter: postgres=1.6.5
23:28:07    Connection test: [ERROR]

23:28:07  All checks passed!

----------------------------------------------

pip install dbt-postgres==1.6.6
[...]
dbt debug
23:29:48  Running with dbt=1.6.6
23:29:48  dbt version: 1.6.6
23:29:48  python version: 3.11.6
23:29:48  python path: C:\Users\***\venv_python\dbt\Scripts\python.exe
23:29:48  os info: Windows-10-10.0.19045-SP0
23:29:48  Using profiles dir at C:\Users\***\.dbt
23:29:48  Using profiles.yml file at C:\Users\***\.dbt\profiles.yml
23:29:48  Using dbt_project.yml file at C:\Users\(***)\dbt_project.yml
23:29:48  adapter type: postgres
23:29:48  adapter version: 1.6.6
23:29:48  Configuration:
23:29:48    profiles.yml file [OK found and valid]
23:29:48    dbt_project.yml file [OK found and valid]
23:29:48  Required dependencies:
23:29:48   - git [OK found]

23:29:48  Connection:
23:29:48    host: ***
23:29:48    port: 5430
23:29:48    user: ***
23:29:48    database: ***
23:29:48    schema: public
23:29:48    connect_timeout: 10
23:29:48    role: None
23:29:48    search_path: None
23:29:48    keepalives_idle: 0
23:29:48    sslmode: None
23:29:48    sslcert: None
23:29:48    sslkey: None
23:29:48    sslrootcert: None
23:29:48    application_name: dbt
23:29:48    retries: 1
23:29:48  Registered adapter: postgres=1.6.6
23:29:48    Connection test: [ERROR]

23:29:48  1 check failed:
23:29:48  dbt was unable to connect to the specified database.
The database returned the following error:

  >Database Error
  'utf-8' codec can't decode byte 0xe9 in position 103: invalid continuation byte

Check your database credentials and try again. For more information, visit:
https://docs.getdbt.com/docs/configure-your-profile

Environment
- OS: Windows 10
- Python:3.11
- dbt-postgres:1.6.6 or later

Which database adapter are you using with dbt?
postgres
Additional Context
No response

Thanks for reporting this @Michael-cd30 !
I've added your expected log output to https://github.com/dbt-labs/dbt-core/issues/8386.
For clarity, is dbt-postgres==1.6.6 working for you when you have the correct password? And the problem you are reporting is only affecting you when the password is incorrect and you are using v1.6.5?
What kind of error message (if any) to you get with 1.6.5 when you do dbt run within an incorrect password?
Using macOS, it is working as expected for dbt-postgres==1.6.6, so I'm guessing that the issue that you are reporting is specific to Windows (see below for my log output).

1.6.5 vs. 1.6.6 on macOS

(postgres_1.6) $ python -m pip install dbt-postgres==1.6.5
Collecting dbt-postgres==1.6.5
...
Downloading dbt_core-1.6.5-py3-none-any.whl (994 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 994.4/994.4 kB 10.4 MB/s eta 0:00:00
Installing collected packages: dbt-core, dbt-postgres
...
Successfully installed dbt-core-1.6.5 dbt-postgres-1.6.5

(postgres_1.6) $ dbt debug
17:33:39  Running with dbt=1.6.5
17:33:39  dbt version: 1.6.5
...
17:33:39  adapter type: postgres
17:33:39  adapter version: 1.6.5
17:33:39  Configuration:
17:33:39    profiles.yml file [OK found and valid]
17:33:39    dbt_project.yml file [OK found and valid]
17:33:39  Required dependencies:
17:33:39   - git [OK found]

17:33:39  Connection:
17:33:39    host: localhost
17:33:39    port: 5432
...
17:33:39  Registered adapter: postgres=1.6.5
17:33:39    Connection test: [ERROR]

17:33:39  All checks passed!

(postgres_1.6) $ python -m pip install dbt-postgres==1.6.6
Collecting dbt-postgres==1.6.6
...
Downloading dbt_core-1.6.6-py3-none-any.whl (995 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 995.1/995.1 kB 9.4 MB/s eta 0:00:00
Installing collected packages: dbt-core, dbt-postgres
...
Successfully installed dbt-core-1.6.6 dbt-postgres-1.6.6

(postgres_1.6) $ dbt debug
17:34:06  Running with dbt=1.6.6
17:34:06  dbt version: 1.6.6
...
17:34:06  adapter type: postgres
17:34:06  adapter version: 1.6.6
17:34:06  Configuration:
17:34:06    profiles.yml file [OK found and valid]
17:34:06    dbt_project.yml file [OK found and valid]
17:34:06  Required dependencies:
17:34:06   - git [OK found]

17:34:06  Connection:
17:34:06    host: localhost
17:34:06    port: 5432
...
17:34:06  Registered adapter: postgres=1.6.6
17:34:06    Connection test: [ERROR]

17:34:06  1 check failed:
17:34:06  dbt was unable to connect to the specified database.
The database returned the following error:

  >Database Error
  connection to server at "localhost" (::1), port 5432 failed: FATAL:  password authentication failed for user "root"

Check your database credentials and try again. For more information, visit:
https://docs.getdbt.com/docs/configure-your-profile

Hello @dbeatty10 ,
I'm currently working with 1.7.4 and I've tried to install older versions to find when the problem appears.
I thought it was between 1.6.5 and 1.6.6 but it's seems older.
In fact, dbt debug only display [ERROR] without explanation on 1.6.5 and previous.
1.6.5
15:56:52  Registered adapter: postgres=1.6.5
15:56:58    Connection test: [ERROR]

1.6.6
15:59:47    Connection test: [ERROR]

15:59:47  1 check failed:
15:59:47  dbt was unable to connect to the specified database.
The database returned the following error:

  >Database Error
  'utf-8' codec can't decode byte 0xe9 in position 127: invalid continuation byte

If the profiles.yml is correct then dbt works fine.
But If on my profiles.yml, before running a dbt run, I write :

an invalid host, the error message is : 'utf-8' codec can't decode byte 0xe9 in position 127: invalid continuation byte
an invalid port, the error message is : connection to server at "localhost" (::1), port 5431 failed: Connection refused (0x0000274D/10061)
an invalid dbname the error message is : 'utf-8' codec can't decode byte 0xe9 in position 84: invalid continuation byte
an invalid user the error message is : 'utf-8' codec can't decode byte 0xe9 in position 103: invalid continuation byte
an invalid pass the error message is : 'utf-8' codec can't decode byte 0xe9 in position 103: invalid continuation byte

As a result, it's quite difficult to find what's the real problem.

Thanks for gathering this info @Michael-cd30 🏆
I'm going to close this issue in favor of https://github.com/dbt-labs/dbt-core/issues/8386. I've added references to this issue there and included the key learnings within the acceptance criteria.


Acrolinx quality improvements: Introduction -to-Active-Directory-Domain-Services-AD-DS-Virtualization-Level-100.md

#assign: @robinharwood, @Xelu86, @iainfoulds
@robinharwood @Xelu86 @iainfoulds
Can you review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Closing due to duplication, apologies.


[dv, chip] Add UNR generated excl for the chip

Signed-off-by: Srikrishna Iyer<EMAIL_ADDRESS>

I'm apparently unable to leave comments on the exclusion file itself due to its size, so here is a list of initial comments/questions after a quick scan-through:

nit: need to add license header
are we going to have to re-generate this UNR file later? Seems like many instances of toggle coverage being marked UNR here that will be hit when chip level tests are developed fully

Same here as Udi's question. I saw some unreachables like this:
Toggle 0to1 hmac_key_o.key_share1 [0] "logic hmac_key_o.key_share1[255:0]"
It happened both in AES and HMAC.This is because the AES and HMAC keys have not been connected to Keymgr in top-level. If that the case, should we re-generate the UNR once they are connected?


Add benchmark for Kefir (RxJS/Bacon competitor)

(FYI, the Travis build failure appears spurious, caused by a connection failure to Sauce Labs and a build timeout long before it could actually run any tests.  The non-Sauce builds worked fine.)


0728 test run

part of 730 tests
gaol: test 1M record load (each record value is 10KB)
test env
export NUM_OF_SI=5
export SI_INSTANCE_TYPE=t2.large
export RKV_INSTANCE_TYPE=t2.xlarge
export JAEGER_INSTANCE_TYPE=t2.xlarge
export JAEGER_ROOT_DISK_VOLUME=200
export YCSB_INSTANCE_TYPE=t2.large

test procedure (load only)
after the test lab has been set up, login to ycsb vm, cd work/go-ycsb, make change to workloads/workloada file, with following changes:
threadcount=2
fieldlength=1000
recordcount=1000000
operationcount=1000000
workload=core

then run ./bin/go-ycsb load rkv -P workloads/workloada
test result
Run finished, takes 1h9m37.403247648s
INSERT - Takes(s): 4177.4, Count: 999990, OPS: 239.4, Avg(us): 8113, Min(us): 4344, Max(us): 217343, 99th(us): 25071, 99.9th(us): 43391, 99.99th(us): 62943

other observations

rkv service host took memory used 547MB;
redis si each took memory ~4.3GB

closed; already passed the milestone


Update the Readme file

in your readme file there is very less information about the project and also about the pre required dependencies and also there is many missing information about the project policy , security like community link etc i want to improve this also improve the Readme file more interactive by adding some beautiful CSS.

would you like to take this issue?

@mendacium-a11y  yes


feat: label line support custom path. close#3000

[中文版模板 / Chinese template]
🤔 This is a ...

[ ] New feature
[ ] Bug fix
[ ] TypeScript definition update
[ ] Bundle size optimization
[ ] Performance optimization
[x] Enhancement feature
[ ] Refactoring
[ ] Update dependency
[ ] Code style optimization
[ ] Test Case
[ ] Branch merge
[ ] Release
[ ] Site / documentation update
[ ] Demo update
[ ] Workflow
[ ] Other (about what?)

🔗 Related issue link

🔗 Related PR link
close #3000

🐞 Bugserver case id
66abcc3c27f96000ad549eef

💡 Background and solution

📝 Changelog

Language
Changelog

🇺🇸 English

🇨🇳 Chinese

☑ Self-Check before Merge
⚠ Please check all items below before requesting a reviewing. ⚠

[ ] Doc is updated/provided or not needed
[ ] Demo is updated/provided or not needed
[ ] TypeScript definition is updated/provided or not needed
[ ] Changelog is provided or not needed

🚀 Summary
copilot:summary
🔍 Walkthrough
copilot:walkthrough

这个感觉可以在站点上补充个 demo


Fix compresskv with lookahead issue

Description
Fix attn_mask in compresskv w/ lookahead.
Note: chatglm is partially fixed and will print abnormal output.
1. Why the change?

2. User API changes

3. Summary of the change

4. How to test?

[ ] N/A
[ ] Unit test: Please manually trigger the PR Validation here by inputting the PR number (e.g., 1234). And paste your action link here once it has been successfully finished.
[ ] Application test
[ ] Document test
[ ] ...

5. New dependencies

[ ] New Python dependencies
- Dependency1
- Dependency2
- ...
[ ] New Java/Scala dependencies and their license
- Dependency1 and license1
- Dependency2 and license2
- ...

PR Validation: https://github.com/intel-analytics/ipex-llm-workflow/actions/runs/10349724071


Sourcery for codable

To reduce writing repetitive code was implementing autogenerated code for Codable by using sourcery. protocol AutoCodable was implemented to mark enums which have to be extended  by protocol Codable (same why we have in Prism for generating enumPrism)
Codable.stensil have been added to replace Codable.swift and make project looks cleaner.

@AndriiDoroshko
Merge branch 'master' into SourceryForCodable
Why you are making merge instead of rebase?

@AndriiMoskvin In the fork where i'm working, the master is not updated with aol/master, so i have no choice. Rebase did not work in case like this(

@AndriiDoroshko So you can't sync your master with remote master from base repo? I don't believe that it is impossible :)

@AndriiMoskvin The fork is not under my account))) Roman already sync fork with aol master) So, i'm going to squash commits)

@AndriiMoskvin Let me update it with the master and make the last check of this PR)
Unfortunately, i'm busy at the moment, so hopefully, you don't mind if i make it done today after 7 pm)

@BogdanBilonog Couldn't you take a look on a PR? I believe it's almost ready)

@AndriiDoroshko What about protocols that we discussed ☝?

BogdanBilonog There are a new file Autogeneratable. In this file, protocols are decelerated as well as extensions) Is this what we've discussed and agreed?

@AndriiDoroshko rebase please.

@AndriiDoroshko could you please look at this PR?


[6.4.x] BZ1310208: When converting .XLS to GDT, Globals defined with short Class Names are converted to invalid Globals file

See https://bugzilla.redhat.com/show_bug.cgi?id=1310208
This is the corollary of https://github.com/droolsjbpm/drools-wb/pull/130 for 6.4.x.
(cherry picked from commit 5e335d848d72f2d2fe1a4c84dcb89eb1a8742687)

I cloned my fork into a new folder, checked out BZ1310208-6.4.x branch and built locally with tests without problem. This is also just a cherry-pick of the master commit which builds fine.

Jenkins please retest.

@psiroky This is really strange.. tests pass locally for me with a fresh clone into an empty folder. The logs suggest tests are being ran in parallel. Could this be the cause on our CI slaves?

@manstis yes, that could be the case. Those CI slaves are also considerably slower than average development machine. My guts are telling that disabling the SSH/Git daemons will fix this... (assuming they can be disabled for these tests).

Jenkins please retest this.

+1 once the tests pass.

INVESTIGATING TEST FAILURES - PLEASE DO NOT MERGE

Jenkins please retest this.

Jenkins please retest.

Jenkins please retest.

@psiroky Please merge at your leisure!


Feat:removed redundancy for keyboard users

Please describe the changes this PR makes and why it should be merged:
Modified the tabindex to enhance keyboard user experience by reducing redundancy. #432
Status

[yes ] Code changes have been tested against prettier, or there are no code changes
[ yes] I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

[ ] This PR changes the codebase

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
[ ] This PR changes the internal workings with no modifications to the external API (bug fixes, performance improvements)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

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

lgtm


Feature Request: Only populate empty translations with Google or OpenAI

I really like the ability to use Google Translate or OpenAI to update your translation strings. After testing it, it looks like it will update every string for the language you select.
This is ok as an option, but I have projects that get regularly updated, so I'll often have a bunch of translations that are checked and approved, and also a set of new strings to translate (or, rather, all languages are identical). I want to be able to ask for auto-translations for the new entries without changing any of the approved / finalised ones.

hi @dave-mills it's a good idea i will try to add it on the next version.

Thanks! I was tinkering with ideas last week. If I get something working for my project, should I share a PR?

yes i will be great

check the last version.


Update stats once a day

I believe it's okay to update stats once a day instead of every 15 minutes.

ping @JohnPhamous

Thanks for the ping! This works for me, thanks for the PR!


add basic association support for ABAP CDS views

Associations for ABAP CDS are not materialized in the db, but old versions of AS ABAP had an ADT service to get the corresponding JOIN clause (to be used from the SQL console). This commit maps a single association path into its corresponding JOIN behind the scenes to be able to use associations to a limited degree.
Path expression attributes, CTEs, and set operators are currently not supported but a query like the following should work without any problems:

Nice, thank you 👍


Add ability to dismiss toast notifications (#4058)

FRONTEND PULL REQUEST
Related Issue
Resolves #4058
Changes Proposed

add an "X" button to the toast notifications so a user can close them without having to wait for them to auto close
update the designs to match the figma
create a <SRToastContainer> component that has all the defaults for <ToastContainer>
create a showSuccess and use showError to display toast notifications to avoid having to passing <Alert>s

Additional Information

Noticed some patterns in the support admin pages where we were showing toast notifications but a user would never actually see this because they are immediately redirected (e.g. https://github.com/CDCgov/prime-simplereport/pull/4451#discussion_r995092415) If we want to fix this up in a separate story, please let me know and I can create an issue for it.
Kenny noticed while archiving a test, that the toaster message appears right before the screen reloads. the toaster should appear after the screen reloads to give the user time to view the message.
Considering the two bullet points above, we may want a story to check/clean up the toast message display experience throughout the app.
As seen in the comments for the original issue linked above, Kenny decided and asked that the toast notification be moved to the bottom left hand corner and to keep the auto close at 5 seconds.

Testing

Go to all different parts of the app that generate a success or error message (e.g. Results tab, /sign-up, Manage organization form, patient bulk upload with errors etc...)
Ensure the change has not introduced any new accessibility concerns

Screenshots / Demos

added a ticket for some of the work that could be done: https://app.zenhub.com/workspaces/simplereport-growth--engagement-605b43a6ceb92c000f86279a/issues/cdcgov/prime-simplereport/4510


WIP: prometheus exporter

Signed-off-by: Issif<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area config

/area outputs

/area tests

/area helm

What this PR does / why we need it:
This PR adds a prometheus exporter for both metrics of events from falco and falcosidekick itself
Which issue(s) this PR fixes:

Fixes #60
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign issif
You can assign the PR to them by writing /assign @issif in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

LGTM label has been added.  Git tree hash: 72c6249bf03efd5884185194321fa13ebb4f180e

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nibalizer
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [nibalizer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nibalizer
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [nibalizer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, nibalizer
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [nibalizer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


chore(sidecar): Sidecar 3000

This bumps Sidecar to v3000 and introduces dark mode.
Todos

[x] Use correct icons in tabs (need help with this - very simple)

Activity

Profile

Feature flags

It also works in light mode:

Will run through that next separately, thx!


Port terrain example

Added viewed boolean to chunks, which is used to efficiently track chunks that can be removed from an instance because nobody is looking at it.
Added to_unloaded function to loaded chunks. Used to make an unloaded clone of a loaded chunk.
Ported terrain example to valence_new.
Terrain generation is now fully asynchronous and will no longer block the main tick loop.

Unloaded chunks closer to players are prioritized over chunks that are further away.

Test Plan
cargo r -p valence_new --example terrain

Testing this effectively seems a bit difficult. I'll have to think about this.


AWS import firehose resources hangs with no output

When I try to import a kinesis firehose resources with the last version of terraformer command execution hangs with no output:
I use this command: terraformer import aws --resources=firehose --filter="Name=<resource-name>" --regions=<region>
2021/07/02 11:44:15 aws importing region eu-west-1
2021/07/02 11:44:17 aws importing... firehose

No additional output is provided to undestand the issue.
Furthermore, importing other resources like EKS, KINESIS ecc, produces the expected output.
Anyone else has the same problem?

I have kind of the same problem since I cannot import firehose resources but I get an error.
% terraformer import aws -r firehose --regions=eu-west-1
2021/07/02 11:45:18 aws importing region eu-west-1
2021/07/02 11:45:20 aws importing... firehose
2021/07/02 11:45:59 aws error initializing resources in service firehose, err: operation error Firehose: ListDeliveryStreams, exceeded maximum number of attempts, 3, https response error StatusCode: 400, RequestID: d1b7f777-915a-8b41-88ef-15e0abd007f1, api error ThrottlingException: Rate exceeded
2021/07/02 11:45:59 aws Connecting....

I am using darwin arm64

@sap-nocops I use linux-amd64 machine.