workaround Issue 14718 - float parsing depends on platform strtold

comment out the affected unittests for now

Issue 14718 – float parsing depends on libc strtold precision

Auto-merge toggled on

Thx!

No no no, the test should be elided ONLY for the platform it fails on, not all platforms!

the test should be elided ONLY for the platform it fails on, not all platforms!

Of course it would be the best way, but how distinguish debian-7.4 system from other linux systems? I couldn't find an easy way.

At least it should be versioned out for Linux systems, not all.

It's a problem during lexing so we can't version it out.


typo in "name servers"

Huge critical important pull request!!! for a game changing break haha

Thank you for the Pull Request, @003random. Your bounty will be awarded shortly. :P


PERF-4097 Use higher precision output for queries/sec to avoid reporting zeroes

@gregorynoma 10 might be overkill, but I was having some trouble deciding how much might be "enough". If you have a query that runs for several hours, you might need 5-7 digits to capture the value and still leave enough precision to detect a 5-10% change in performance. I just went with 10 to give a bit of extra padding.


Tweaked for server, sub, and pub on Ubuntu.

It didn't build for me out of the box, I had to add -lrt to the binaries. Whether or not that also works on Mac OS is another question. I'd be happy to adjust the PR as needed.
I also added copy-pastable build and run commands. I hadn't used bazel in a while and figure it might help others to have them handy.

Hey @dallison thanks for all this! I had to try it out right away and had to tweak some things for Ubuntu 20.04. I'm not sure how to best specify those -lrt that I needed, any suggestions?

Thanks Roland.  I tried it on macos and it doesn't have an librt.so.  I'm modifying the BUILD files to add a select for the binaries.
I don't have Ubuntu 20.04 but I'll make sure it works on the version I have

Superseded by the better solution in #11


[quick_actions] Optimised UI test to prevent flaky CI failures

This PR will hopefully fixes the flaky testQuickActionWithFreshStart iOS UI test (see flutter/flutter#83483).
Since I wasn't able to reproduce the issue on my local environment it is difficult to determine if this really resolves the problem. However the test was launching and terminating the app under test and I think this was interfering to the point where the app is terminated right before the test to check for the "action-two" screen shows up.
I have restructured the test script to ensure the app under test is terminated after each test so the environment should start in a fresh state for each of the tests.
Added benefit is that is makes the UI Test logic easier to read and understand and less prone to mistakes when additional tests are added.

flutter/flutter#83483

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides. (Note that unlike the flutter/flutter repo, the flutter/plugins repo does use dart format. See plugin_tool format)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.

The version number is not updated since this PR only restructured an existing UI Test so it would run more stable. In my opinion this change didn't warrant a new release to be published.

[ ] I updated CHANGELOG.md to add a description of the change.

The version number is not updated since this PR only restructured an existing UI Test so it would run more stable.

[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Looks good other than one question. It's not really clear to me why this would fix it since it was waiting for the springboard, so the termination should have been complete, but it's worth a try.

The old test starten with the following code block:
XCUIApplication app = [[XCUIApplication alloc] init];
[app launch];
[app terminate];

I suspect that the terminate command takes a while to complete and terminates the process to late. So when the test is already progressing the quick action button is tapped the app is launched but then the terminate from earlier kicks in basically cancelling the launch causing the test to timeout because the action_two screen is never displayed.

Looking at the failing step it seems this actually made it worse :(. As now both UI tests seem to fail. I will look into it.

@mvanbeusekom since this is intended to fix a flake, can we re-trigger the failing check several times while in PR, to see if this actually fixes the flakiness?

This is the flaky test:
build-ipas+drive-examples CHANNEL:stable PLUGIN_SHARDING:--shardIndex 2 --shardCount 4

@mvanbeusekom since this is intended to fix a flake, can we re-trigger the failing check several times while in PR, to see if this actually fixes the flakiness?
(I can re-run the test several times today, I just need to know what's the task that usually failed)

@ditman that would be much appreciated. The questionable step in question would be build-ipas+drive-examples CHANNEL:stable PLUGIN_SHARDING:--shardIndex 2 --shardCount 4.
I have just triggered it to run for a second time.

Thanks @mvanbeusekom, I'll leave it in a window and retrigger it a bunch of times today. Thanks for the info!

Thanks for the info @mvanbeusekom, I'll leave it in a window and retrigger it a bunch of times today. Link.

@ditman and @stuartmorgan I have just run the flaky job 10 times in a row and all green. So it looks good so far. Maybe @ditman you can run it a view times on some other times during the day (maybe it is some caching issue and all builds succeed now because I run them quickly after each other)?

@ditman you can run it a view times on some other times during the day (maybe it is some caching issue and all builds succeed now because I run them quickly after each other)?

@mvanbeusekom yes, I definitely can run this a few more times later in the PM. The main difference between this and master is that in the PR, this is running pretty much by itself, and when it runs in master this runs with other tasks.
In any case, promising! :D

I've retried this in master a few times, and it seems solid: https://cirrus-ci.com/task/5610373752553472


Improve khmer segmenter performance by using fst segmenter

Pull Request
Related issue
Fixes #250
What does this PR do?

[x] add khmer words fst converted from khmerdict.txt using fst crate
[x] change to use fst segmenter instead of icu_segmenter
[x] remove icu deps

PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Hello @xshadowlegendx,
thank you for your PR,
did you run the benchmarks?


file uploads > 65536 characters, binary blobs/mp4s etc.

Hello there,
First, I have to say that I am really impressed by what you guys are doing here. Also, your docs are outstanding and easy to follow. I spotted your project on my recommendations page and immediately fell in love, losing most of my Friday night tinkering around.
When I got to your file upload section in the docs, I hit a snag when trying to upload an mp4 file.
{   "detail": [     {       "loc": [         "body",         "file"       ],       "msg": "ensure this value has at most 65536 characters",       "type": "value_error.any_str.max_length",       "ctx": {         "limit_value": 65536       }     }   ] }

It seems like the File type expects bytes as strings, which aren't allowed to go past 65536 characters in length. I expect others might run into this too, or be confused like I am when hitting this part.
-Russell

First, I have to say that I am really impressed by what you guys are doing here. Also, your docs are outstanding and easy to follow. I spotted your project on my recommendations page and immediately fell in love, losing most of my Friday night tinkering around.

Awesome! It's great to hear that. Thanks for writing it :smile:

When I got to your file upload section in the docs, I hit a snag when trying to upload an mp4 file.

Thanks for the very detailed bug report.
The bug was because of a default constraint in Pydantic. I just created a custom internal class for this that fixes the problem. I also added a test for this specific use case.
Please try with the latest version 0.1.17.

I also plan on supporting Starlette's (undocumented) file uploads, to get a file-like object. But this will come afterwards.

Great, thanks! 0.1.17 works without a hitch :tada:. I'll close this issue and keep an eye out for changes in the future.

I also plan on supporting Starlette's (undocumented) file uploads, to get a file-like object. But this will come afterwards.

That looks like a good idea. Do you have any plans to reuse pathlib's file interface?


Error while updating 'transform' of a view managed by: RCTView

I get this error:
Error while updating 'transform' of a view managed by: RCTView
React Native 0.32 works good.

React Native version: 0.33
Platform(s) (iOS, Android, or both?): Android
Operating System (macOS, Linux, or Windows?): Linux

+1

+1
React Native 0.32 works good, after upgrade to 0.33 change router cannot work on Android.

@ruskid Can you post your sample code to reproduce it?

I rolled back to 0.32 for the moment and I am using react native router flux library for routing, so I don't think my sample example will help you. you can check the library and try to reproduce the error by the examples there.

experiencing the same issue after upgrading from .31 -> .33

+1
this.props.navigator.push(this.getRoute(component, props));

+1 update to rn33

+1
Having the same issue and I'm not on even some advanced stuff. I just started doing some simple tutorials and this showed up.
React Native version: 0.33
Platform(s) (iOS, Android, or both?): Android
Operating System (macOS, Linux, or Windows?): Windows

+1
No solution?
React Native version: 0.34
Platform(s) (iOS, Android, or both?): Android
Operating System (macOS, Linux, or Windows?): Windows

This is happening to me only when I try to put the navigator into a <Modal/>.
React Native version: 0.34.1
Platform(s) (iOS, Android, or both?): Android
Operating System (macOS, Linux, or Windows?): macOS

This just started happening on my project and I'm not sure I even changed anything. We've been using 0.33 for a while here and have had successful builds so I'm not sure what changed.. haven't upgraded to 0.34 yet.
Note We are using [react-native-router-flux(https://github.com/aksonov/react-native-router-flux) (3.35.0). Not sure if this is truly related but saw it mentioned above so sharing. This definitely has me stuck at this point.

@dwilt
Just upgraded to RN 0.34.0 and the error disappeared.

Just upgraded to RN 0.33.1 and got same error

RN 34 seems to solve the issue for me as well

Agreed, sorry for not replying. Upgrading to 0.34.0 did fix it for me

I can confirm that 0.34.1 and 0.34.0 both still cause the issue. Even the 35 and 36 release candidates also cause the issue. the problem appears to be related to the newly introduced TransformHelper calling the TransformMatrix that was introduced here: https://github.com/facebook/react-native/commit/df053117778d8ebcc1943f20127e49078f79da0b
We are investigating the problem because we need to be able to use transform properties:
The root cause appears to have a relationship to type conversion from string to double in Java
see Crash log:
com.facebook.react.bridge.JSApplicationIllegalArgumentException: Error while updating property 'transform' of a view managed by: RCTView
	at com.facebook.react.uimanager.ViewManagersPropertyCache$PropSetter.updateViewProp(ViewManagersPropertyCache.java:88)
	at com.facebook.react.uimanager.ViewManagerPropertyUpdater$FallbackViewManagerSetter.setProperty(ViewManagerPropertyUpdater.java:123)
	at com.facebook.react.uimanager.ViewManagerPropertyUpdater.updateProps(ViewManagerPropertyUpdater.java:42)
	at com.facebook.react.uimanager.ViewManager.updateProperties(ViewManager.java:34)
	at com.facebook.react.uimanager.NativeViewHierarchyManager.createView(NativeViewHierarchyManager.java:220)
	at com.facebook.react.uimanager.UIViewOperationQueue$CreateViewOperation.execute(UIViewOperationQueue.java:148)
	at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.dispatchPendingNonBatchedOperations(UIViewOperationQueue.java:890)
	at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.doFrameGuarded(UIViewOperationQueue.java:863)
	at com.facebook.react.uimanager.GuardedChoreographerFrameCallback.doFrame(GuardedChoreographerFrameCallback.java:32)
	at com.facebook.react.uimanager.ReactChoreographer$ReactChoreographerDispatcher.doFrame(ReactChoreographer.java:131)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:771)
	at android.view.Choreographer.doCallbacks(Choreographer.java:586)
	at android.view.Choreographer.doFrame(Choreographer.java:555)
	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:759)
	at android.os.Handler.handleCallback(Handler.java:739)
	at android.os.Handler.dispatchMessage(Handler.java:95)
	at android.os.Looper.loop(Looper.java:135)
	at android.app.ActivityThread.main(ActivityThread.java:5422)
	at java.lang.reflect.Method.invoke(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:372)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:914)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:707)
Caused by: java.lang.reflect.InvocationTargetException
	at java.lang.reflect.Method.invoke(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:372)
	at com.facebook.react.uimanager.ViewManagersPropertyCache$PropSetter.updateViewProp(ViewManagersPropertyCache.java:77)
	... 21 more
Caused by: com.facebook.react.bridge.UnexpectedNativeTypeException: TypeError: expected dynamic type `double', but had type `string'
	at com.facebook.react.bridge.ReadableNativeArray.getDouble(Native Method)
	at com.facebook.react.uimanager.TransformHelper.processTransform(TransformHelper.java:77)
	at com.facebook.react.uimanager.BaseViewManager.setTransformProperty(BaseViewManager.java:157)
	at com.facebook.react.uimanager.BaseViewManager.setTransform(BaseViewManager.java:57)
	... 24 more

I found that the translate property of the transform was causing this error for me.
On line 77-79 of the TransformHelper it assumes the property is a double where I had been giving string values like "50%". I suspect any translation with a percentage or unit will break.
https://github.com/facebook/react-native/blob/v0.34.1/ReactAndroid/src/main/java/com/facebook/react/uimanager/TransformHelper.java#L77

@facebook-github-bot label android

yesterday, my version is 31,
today,i'm update rn to 35, it's report ====>  call argument isn't a string
so i'm reback to 33,
it's report property 'transform' of a view managed by :RCTView
should i update to 34.....

Yep to confirm we had to 'safety wrap' our translate
  if (Platform.OS == 'ios') {
        transform.translate = ['0', '-100%'];
      }

That fixes android, but of course - no translate. Thankfully this was only cosmetic in our case, but That new MatrixHelper/TransformMAtrix stuff file seems to have issues atm.

For me this issue was resolved by changing the rotation string suffix from 'degrees' to 'deg'.  e.g. from:
'rotateZ': '30degrees'
to:
'rotateZ': '30deg'

I just upgraded to RN0.35, but it did not work. As mentioned before, the error appears when changing navigator's routes. Besides, I tried all the solutions above, but still can't find anyone works. :(

Seeing this error as well, RN 0.35 only when I build for release on Android. This is a really bad bug can't find any work around. Also it only seems to be happening when I build for release, not happening on debug builds

I'm getting a very similar error to this in RN 0.35 when I build for release on Android but rather than  the cause that @the-simian was seeing, I'm getting Caused by com.facebook.react.bridge.UnexpectedNativeTypeException: expected Map, got a int64.
When the exception is thrown, the props ReactStylesDiffMap in ViewManagersPropertyCache contains an unusual transform value - something like transform: [1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1]. It looks like it's coming from NavigationCard component in NavigationExperimental.
My half-baked theory is that the usual transform Map (i.e.transform: { scale: 1 }) is expected but for some reason it has already been converted into a matrix.
The only solution I could find was to downgrade to RN 0.34. Hopefully someone else can shed some light on this weird issue.

Any update on this one?

I am not sure if it is related but I have faced the same error. The problem was that I've created animated value without arguments new Animated.Value(). It works when I change it to new Animated.Value(0).

In mi case I had react-native-parallax-scroll-view": "0.19.0 and that was creating a problem,  I ended up not using it in order to avoid that issue.

For future reference: I was having this issue with React Native 0.44. It turns out I was passing NaN (Not a Number) to an Animated.Value, kinda like this: <Animated.View style={{transform: [{translateX: this.animatedValueThatWasNaN}]}}/>.
In my case, the NaN came from a calculation in a video player, where Android reported progress on a video that had undefined duration, which resulted in currentVideoPosition/totalDuration was an invalid calculation, causing NaN. While probably not directly relevant to your situation, it may help you understand that the error lies in your own application, although I would say RN could be a bit more helpful with the error message (ie. saying the value is not a number).

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

For future reference: check your dependencies. I had this issue because I was using react-native-material-switch with RN 47. I removed it and used the native Switch component and everything worked fine.

I have the same issue dose any one have progress with this issue?
RN version : 0.49.3
OS:windows
platform:android

Seeing this on RN 0.53.3, Windows, Android (physical device) as well.

having this issue on android device using RN 53.0 :(

Be careful to give an array to the transform property. I was giving an object and I had this exact error.
<Image source={...} transform={{rotateZ: '90deg'}} /> // Bad

<Image source={...} transform={[{rotateZ: '90deg'}]} /> // Good

Also running in this issue. Seems to be caused also by translation transformations. Other types of transformations work of for me. I am resorting to showing a degraded experience on Android vs. iOS.


serverless monitoring

hi
i have servelress framework called openfaas and with lot of functions and i started installing the Dyantrace as we use dynatrace for all monitoring. .
i am getting errors installing on our serveless. do you have any proper documentation steps for installing the agent . My current setup is kubernetes and serverlss runs on top of it as containers ?

Hi,
thanks for your inquiry. May I refer you to https://www.dynatrace.com/support/help/cloud-platforms/kubernetes. If this does not contain the requested information, please re-post your question at https://answers.dynatrace.com.


google-chrome not found

hello,
I've issue when generate pdf, grafana running on docker together with image-render, I put screenshot on the attachment and following is version detail

Grafana docker version                                                      = grafana:10.4.2-ubuntu
Grafana docker Image Render version                               = grafana-image-renderer:3.10.3
Grafana Plugin grafana-dashboard-reporter-app version = v1.2.0
Grafana Plugin Image Render version                               = grafana-image-renderer:3.10.3
Grafana Plugin

I run docker with following this docker-compose https://github.com/mahendrapaipuri/grafana-dashboard-reporter-app.

I guess you are not using the same Grafana docker image as provided in the repo. If you are using your own Grafana image, you will need to install chromium in the image. For example, we do it for the image provided in the repo here


add sleeping and spinning benchmark

This PR add 2 new benchmarks sleeping (to simulate I/O bounded task) and spinning (to simulate CPU bounded task) such that i can investigate how dynamically configure cpu frequency affects latency of such tasks

I also added a CI workflow and tested it in #852.
Can you copy the spin-sleep.yaml in your code.
Also as you see here https://github.com/vhive-serverless/vSwarm/actions/runs/7856433672/job/21439224624#step:9:1 it fails to deploy in knative

Hi @dhschall, I have fixed the end-to-end test, thank you! I would like to request review from you again if possible.


Fixed #34981 -- Added pair and bisect options to DiscoverRunner.

ticket 34981

@sulabhkatila I'm not sure if you saw the latest comment in the ticket about this PR. Let us know if you have time to keep working on this! Thanks.

Hi @nessita I read the comment and will send send a revised PR soon


Setting the Difficulty Level of the Game

Hi,
Thanks for your nice code and documentation.
I saw the report from Kevin Chen where he experimented with three difficulty levels (easy, medium, hard) of the game.  Can you please tell me which difficulty level the game is set in your code ? and How to change the difficulty level if I want to?
I guess, it's related to value of PIPEGAPSIZE in wrapped_flappy_bird.py.. currently it's set to 100. Is that hard mode? By Increasing or decreasing the PIPEGAPSIZE, can I change the difficulty level? If so, are there any specific value for those modes?
Thanks!

I have the same question. Does anybody have an idea of this?

set PIPEGAPSIZE... I think the default is- PIPEGAPSIZE = 100 as hard mode, 150 as medium and 200 as easy. However, you can set any value based on your preference...setting PIPEGAPSIZE < 100 would make it more harder.


Vue warn after click dialog accept and cancel

OS: windows 10
Node.js version : v12.13.1
Vuesax version: v3.12.3
Browser version: Chrome Version 87.0.4280.88
Which package manager did you use for the install? NPM

add .native to @click in your component
default it is like @click='function'
make it @click.native='function'

Following this method did not solve the problem

This method worked almost 3 years ago. maybe some changes have been in luasax(

Following this method did not solve the problem

This method worked almost 3 years ago. maybe some changes have been in luasax(

got it, thanks


Unable to Migrate to Azure SQL

Type: Bug
After right-clicking Manage from our on-prem server connection, the Azure SQL Migration just spins and is unavailable.  I also receive the message, "Failed to start SQL Tools Service" when first launching Azure Data Studio - Insiders edition and am unable to load Linked accounts (it also just spins).
Azure Data Studio version: azuredatastudio-insiders 1.48.0-insider (471a0e369411ae1b7f03b549a1133a48e5c99aed, 2024-02-13T06:39:04.970Z)
OS version: Windows_NT x64 10.0.17763
Restricted Mode: No
Preview Features: Enabled
Modes:

System Info

Item
Value

CPUs
Intel(R) Xeon(R) Gold 6342 CPU @ 2.80GHz (8 x 2793)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: unavailable_software

Load (avg)
undefined

Memory (System)
12.00GB (7.24GB free)

Process Argv

Screen Reader
no

VM
100%

Extensions (1)

Extension
Author (truncated)
Version

sql-migration
Mic
1.5.3

Hi @dmccoygh
Please gather and upload logs for investigation.

Please provide process on how to gather logs and where they are located and I will upload.
Thanks,

David McCoy | Fluor Federal Petroleum Operations, LLC  | Lead Programmer Analyst | Contractor to the U. S. Department of Energy SPR |<EMAIL_ADDRESS>504.734.4558|F<PHONE_NUMBER>
From: Cheena Malhotra @.>
Sent: Thursday, February 15, 2024 5:54 AM
To: microsoft/azuredatastudio @.>
Cc: McCoy, David (CONTR) @.>; Mention @.>
Subject: [External] Re: [microsoft/azuredatastudio] Unable to Migrate to Azure SQL (Issue #25322)
Hi @dmccoyghhttps://github.com/dmccoygh
Please gather and upload logs for investigation.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azuredatastudio/issues/25322#issuecomment-1945948138, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQPWD6UPYBRPUTMNKAFMNDDYTXZNXAVCNFSM6AAAAABDHERCKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBVHE2DQMJTHA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Oops.. Actions didn't trigger comment.. you can find instructions here:
We need more info to debug your particular issue. If you could attach your logs to the issue (ensure no private data is in them), it would help us fix the issue much faster.

First open the Settings page, find the Mssql: Tracing Level setting and change that to All then restart Azure Data Studio.
Open command palette (Click View -> Command Palette) and run the command Developer: Set Log Level... and set the level to Trace.
Run the repro scenarios.
Collect the following logs:

Console Logs

Open Developer Tools (Help -> Toggle Developer Tools)
Click the Console tab
Click in the log area and select all text (CTRL+A)
Save this text into a file named console.log and attach it to this issue.
Developer Tools can be closed via Help -> Toggle Developer Tools

Application Logs

Open command palette (Click View -> Command Palette)
Run the command: Developer: Open Logs Folder
This will open the log folder locally. Please zip up this folder and attach it to the issue.

Now you can revert the Log/Tracing levels changes made in step 1 and step 2.

console.log
Console.log file attached

ads logs.zip
Additional logs file attached

Is there any update on this?


feat(core): allow configuring aliasing naming strategy

Implements different table aliasing for select-in loading strategy and for QueryBuilder
and makes it configurable.
BREAKING CHANGE:
Previously with select-in strategy as well as with QueryBuilder, table aliases
were always the letter e followed by unique index. In v5, we use the same
method as with joined strategy - the letter is inferred from the entity name.
This can be breaking if you used the aliases somewhere, e.g. in custom SQL
fragments. We can restore to the old behaviour by implementing custom naming
strategy, overriding the aliasName method:
import { AbstractNamingStrategy } from '@mikro-orm/core';

class CustomNamingStrategy extends AbstractNamingStrategy {
  aliasName(entityName: string, index: number) {
    return 'e' + index;
  }
}

Note that in v5 it is possible to use expr() helper to access the alias name
dynamically, e.g. expr(alias => `lower('${alias}.name')`), which should be
now preferred way instead of hardcoding the aliases.

Codecov Report

Merging #2419 (06c8963) into master (706935e) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master     #2419   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          188       188
  Lines        10419     10423    +4
  Branches      2285      2288    +3
=========================================
+ Hits         10419     10423    +4

Impacted Files
Coverage Δ

packages/core/src/drivers/DatabaseDriver.ts
100.00% <100.00%> (ø)

...core/src/naming-strategy/AbstractNamingStrategy.ts
100.00% <100.00%> (ø)

packages/knex/src/query/ObjectCriteriaNode.ts
100.00% <100.00%> (ø)

packages/knex/src/query/QueryBuilder.ts
100.00% <100.00%> (ø)

packages/knex/src/query/ScalarCriteriaNode.ts
100.00% <100.00%> (ø)

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 706935e...06c8963. Read the comment docs.


multiple server node start will failed

according to this https://github.com/rancher/rke2/issues/869 issue, multiple server node start at the same time will failed, need to run in sequence.

should be addressed in #54


Ask for optional arguments when interactively collecting arguments

For example the rankBack argument in /suspend and the specialNotes argument in /host. If these commands are ran using the interactive way, the argument collector will not ask for the optional arguments and thus will be their default values. This is not always desirable.

Both rankBack and specialNotes are not optional anymore. A value for both will be prompted:

Argument rankBack must be either true or false.
Argument specialNotes should be "none" to not provide no notes and anything else to do so.


Comfyui-ollama Node Name Display Error

After installing comfyui-ollama, part of the node name is displayed as another node comfyui-ollama-YN, but I did not install this node.

what nodes? the YN i think its a fork from this repo


Message not sent to a large number of users "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"

Hi Team, Need help here. We are facing issues relating to communicator where some users are not getting messages and need to understand what the issue is. The error message we are getting for this set of users is "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond". This happens to almost 1,000 users out of 12,000 users sent to.

Thanks in advance.

Hi  @bchamnarnkit ,
These errors shared will required some analysis from our side. If required, we can get over call to troubleshoot it. We will keep you posted with update.

Thanks for your. Do you happen to know what could potentially be causing this? I can also schedule a call  but if we have some assumptions or initial thoughts on why this is failing do let me know? Thanks

Thanks @v-royavinash , I will work with my customer to try it and provide revert back if there are any issues


WithParameter in QueryDefinition Throws error using json nested dotted notation.

We are using automation to build queries from existing data and there are nested json objects. The automation resolves nested json objects as dotted notation nested parameters. It generates the replaceable @parameter part from the field parameter resolved. With this very limited parameter replacement method we have to write a considerable amount of code to manage this issue.
Our current workaround is to filter the dots and ensure the fields remain unique matches.
Example:
In a cosmos document there could be a nested object
},
"Updated":{ "unixtime":15336895,"status":true},
The failing query pattern:
SELECT TOP 10 * from PLsystem c where c.opstatus=@opstatus and c.ApplicationId=@ApplicationId and<EMAIL_ADDRESS>Describe the bug
<EMAIL_ADDRESS>1565705133)
Microsoft.Azure.Cosmos.Query.Core.Exceptions.ExpectedQueryPartitionProviderException: {"Errors":["Invalid query. Specified parameter name<EMAIL_ADDRESS>is invalid. Parameter names should be in the format of symbol '@' followed by a valid identifier. E.g. @param1"]}
To Reproduce
Use the sample project
Start at line 194. In line 200, Modify the query definition to use nested parameters using the full path.
QueryDefinition query = new QueryDefinition("SELECT * FROM Families f WHERE f.id = @id AND f.Address.City = @Address.City")
Change line 202 to<EMAIL_ADDRESS>"Seattle");
Expected behavior
I would expect that the parameter would not care about dotted notation and accept the input.
Actual behavior
Microsoft.Azure.Cosmos.Query.Core.Exceptions.ExpectedQueryPartitionProviderException: {"Errors":["Invalid query. Specified parameter name<EMAIL_ADDRESS>is invalid. Parameter names should be in the format of symbol '@' followed by a valid identifier. E.g. @param1"]}
Environment summary
SDK Version: v3
OS Version (e.g. Windows, Linux, MacOSX) Window 10 current version.
Additional context
Add any other context about the problem here (for example, complete stack traces or logs).

The grammar for parameter does not accept dots, since it would conflict with PropertyReferences.


Release 51

Coverage decreased (-0.01%) to 13.24% when pulling c1761da9df56915f1888486321e49ba1e4b4766d on current into 0c20087b72ea144b01c8771fc963eaba66a92475 on master.


tests: shorten utils function names

All the functions we use to create Virtual Machines and DataVolumes mention very prominently that they are "random". This makes the function names redundantly longer and confuses a causal reader to think that there is anything random in the make or behavior of the created object, while only its name is random.
This PR suggests to drop the Random term from all of these functions.
NONE

/lgtm

/lgtm

/retest

this looks nice, but I am afraid that this kind of change will probably make most of the automatic bugfix cherry picks that touch any functional test to fail (a need for rebase). Such renames of common utilities are always a pain to merge.

Closing due to failure to garner consensus and too many modified files.


M3-5338: Notification Drawer refinements

Description
This PR updates the UI for the notification drawer and it's empty state. The notification drawer is less of a drawer and is more consistent with the user menu.
Tasks that will be addressed in a future PR:

[ ] Refactor NotificationDrawer to implement MUI's Drawer component instead of adding conditional logic inside of our Drawer component
[ ] Bold the username, action and entity name in the event messages inside the notification drawer

How to test
Test the notification drawer for the following scenarios:

No notifications and no events (turn on mocks)
Notifications but a few events (< 5 events)
Notifications but a lot of events (uncomment the code inside of serverHandlers.ts

@bnussman I had the same thought. I'm actually looking into that rn


Capitalized Patterns in the title

I capitalized Patterns in the title "Behavioral Patterns"

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.


Doesn't work with nextjs@12 compiler

next.config.js
  experimental: {
    swcPlugins: [
      ['@lingui/swc-plugin', {}],
    ],
  },

Receive error when build:
thread 'thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: LayoutError', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/rkyv-0.7.37/src/impls/core/mod.rs:265:67
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: LayoutError', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/rkyv-0.7.37/src/impls/core/mod.rs:265:67
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'thread '<unnamed><unnamed>thread '' panicked at '' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("/Users/tim/projects/timescenery/node_modules/next/dist/client/router.js")'

Caused by:
    0: failed to invoke<EMAIL_ADDRESS>as js transform plugin at<EMAIL_ADDRESS>    1: RuntimeError: out of bounds memory access
    2: heap_get_oob', <unnamed>/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/swc-0.226.26/src/plugin.rs' panicked at ':failed to invoke plugin: failed to invoke plugin on 'Some("/Users/tim/projects/timescenery/node_modules/next/dist/client/dev/amp-dev.js")'

Caused by:
    0: failed to invoke<EMAIL_ADDRESS>as js transform plugin at<EMAIL_ADDRESS>    1: RuntimeError: unreachable
    2: unreachable', 216/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/swc-0.226.26/src/plugin.rs:failed to invoke plugin: failed to invoke plugin on 'Some("/Users/tim/projects/timescenery/node_modules/next/dist/client/next-dev.js")'

Caused by:
    0: failed to invoke<EMAIL_ADDRESS>as js transform plugin at<EMAIL_ADDRESS>    1: RuntimeError: unreachable
    2: unreachable14', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/swc-0.226.26/src/plugin.rs::216216::1414

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'thread '<unnamed><unnamed>' panicked at '' panicked at 'failed to invoke plugin: failed to invoke plugin on 'Some("/Users/tim/projects/timescenery/projects/client-react/pages/_app.page.tsx")'

Next.js v12.3.1
Plugin: 0.1.0

so we have to upgrade to nextjs13?
if yes, then we'll need to upgrade react->18 as well, but our project isn't ready for this :)

I'm trying to find a solution, but looks like swc plugins is so bleeding edge and api is very unstable


Pluging/portal updates for wordpress

Hi,
as a wordpress user, will the portal plugin updates appear in the standard updates area and if they do and I update the plugin, will my style edits to css files be replaced so I need to do the edits again?
Thanks for your time

Hi
This plugin is in the main repo so the updates are automatic as per normal.
If you change any CSS or code in the plugin it will replace when it is updated
You will need to re-apply each time it updates
This is because it loading in an Iframe
Paul


ipp-usb: cannot print on HP m28a on ArchLinux

from /var/log/ipp-usb/device.log
10-07-2022 21:04:57:   USB[0]: connection allocated, 1 in use: a-- --- ---
10-07-2022 21:04:57:   HTTP[074]: connection 0 allocated
10-07-2022 21:04:57: > USB[0]: write: wanted 976 sent 976 total 976
10-07-2022 21:04:57: < USB[0]: read: wanted 4096 got 0 total 0
10-07-2022 21:04:57: !  USB[0]: zero-size read
10-07-2022 21:04:57: < USB[0]: read: wanted 4096 got 0 total 1024
10-07-2022 21:04:57: ! USB[0]: zero-size read
10-07-2022 21:04:57: < USB[0]: read: wanted 4096 got 0 total 1024
10-07-2022 21:04:57: ! USB[0]: zero-size read
10-07-2022 21:04:57: < USB[0]: read: wanted 4096 got 28 total 1052
10-07-2022 21:04:57: < HTTP[074]: response body: got 981 bytes; EOF
10-07-2022 21:04:57:   USB[0]: connection released, 0 in use: --- --- ---

keep-alive quirk is set for M28a.

Hi,
the log fragment that you've published doesn't contain any problem by itself. zero-size reads are not problems, but sometimes correlates with real problems, though there are a lot of devices that have zero-size reads though works absolutely reliable.
First thing to do, is to isolate the problem to the particular component (it may be on CUPS side, for example).

Btw, I see you are from Moscow, like me. Where are you located here?

@alexpevzner in Butovo

Very near to me. I'm in Yasenevo.

Scanning works. Web-browser page too. But printing is not - KDE reports than "job is cancelled by printer" for any page, even test one. HPLIP works.

ipp-usb is only a transport. Job can be cancelled due to many reasons. If after failed printing job all IPP-USB interfaces are idle:
10-07-2022 21:04:57:   USB[0]: connection released, 0 in use: --- --- ---

this is very unlikely that the problem is in the ipp-usb.
My Kyocera also doesn't work out of box with the open source stack. For me, it helps to extract the .PPD file from the proprietary driver bundle and to manually install it on CUPS.
@tillkamppeter, can you help us, please? How to solve problems like these?

@rilian-la-te here we would need some more information:

If there is a way to connect the printer by Ethernet or Wi-Fi instead of USB, it should also do driverless printing and scanning. Is it working completely and correctly this way or do you get the same printing problem?
To investigate the printing problem itself you should put CUPS into debug logging mode (cupsctl --debug-logging) and print another (failing) job. After that get the /var/log/cups/error_log file and attach it here. Note that GitHub only accepts it if you rename it to have the extension .txt.
Also attach the PPD file of your CUPS queue (in /etc/cups/ppd/, also rename it to have a .txt extension for attaching it).
Get further info from your printer with the command ipptool -tv ipp://localhost:60000/ipp/print get-printer-attributes.txt > attrs.txt Attach the file attrs.txt to this bug report.

Please attach the files one by one, do not compress them and do not package them together. Thanks.

@tillkamppeter will do.
Printer do not support ethernet.
I will do attaching PPD and other files.

@tillkamppeter
Logs:
error_log.txt
attrs.txt
printer.ppd.txt

@rilian-la-te please also do the following:
sudo systemctl stop cups

Then edit the PPD file of your printer in /etc/cups/ppd/. It has the name of your print queue. Remove the line
*cupsFilter2: "image/pwg-raster image/pwg-raster 10 -". Save the file.
The start CUPS again:
sudo systemctl start cups

Try to print again. Does this work now?

@tillkamppeter nope, same symptoms. Removing cups-filte is not working.

@debiantriage everywhere mode is also does not work.

New log:
error_log.txt

Jobs 35, 36 and 38 are printed on testq. For nsswitch.conf we see

I [21/Jul/2022:22:38:22 +0300] [Job 35] File of type text/plain queued by "rilian".
D [21/Jul/2022:22:38:22 +0300] [Job 35] Sending job to queue tagged as raw...

Sending as raw should not happen with a correctly set up  everywhere queue. No filtering takes place; nsswitch.conf is sent without any filtering and the M28a cannot possibly print it.
@rilian-la-te
Thanks for the input but, unfortunately, it does not seem to provide any definite useful information about the operation of ipp-usb. The lpadmin command should produce a PPD in /etv/cups/ppd after querying the printer. Does it?

@debiantriage
testq.ppd.txt
With second attempt, nsswitch.conf is printed using Everywhere generator.

New log:
error_log.txt
Driverless also was able to print nsswitch.conf..
But KDE test page is still cannot be printed.

nsswitch.conf prints on testq and hp-home with everywhere and driverless. I would expect that printing from (say) Firefox would work for either queue.
The test page does not print on testq and hp-home with either everywhere or driverless. We see Job canceled at printer. I do not knw the reason for that. Maybe a cups-filter issue?

@debiantriage printing from Firefox works.
As nsswitch.conf too. But I want to print some other files.

@debiantriage @tillkamppeter from Okular pdf printing works too, so, only printing non-pdf files is not working.
Is there any way to force jobs as pdf?

Printing from firefox using GTK dialog does not work, which is strange.

PNG files is also printed using lp -d

@tillkamppeter @debiantriage looked to /var/spool/cups and see than all jobs with format
document-format-detectedapplication/vnd.cups-pdf-bannerIdocument-formatapplication/vnd.cups-pdf-banner
is not printed, but with
ocument-format-detectedapplication/pdfIdocument-formatapplication/pdf
is printed. Is I missed some conversions from banner to pdf?

Even lp -d hp-home /usr/share/cups/data/testprint works from command line.
But printing test page does not work from Qt and Gtk print dialogs. It is same file, I do not know who it should not work
error_log.txt
Look to jobs 61 and 62. It is effectively same file, one from KDE print dialog, and one from lp -d. First succeed, but second failed.

Here is /var/spool/cups output
[5x5linux-manjaro cups]# cat d00061-001
#PDF-BANNER
Template default-testpage.pdf
Show printer-name printer-info printer-location printer-make-and-model printer-driver-name printer-driver-version paper-size imageable-area job-id options time-at-creation time-at-processing

[5x5linux-manjaro cups]# cat d00062-001
#PDF-BANNER
Template default-testpage.pdf
Show printer-name printer-info printer-location printer-make-and-model printer-driver-name printer-driver-version paper-size imageable-area job-id options time-at-creation time-at-processing

[5x5linux-manjaro cups]# cat c00061
Gattributes-charsetutf-8Httributes-natural-languageru-ruE
                                                         printer-uri ipp://localhost/printers/hp-homeBjob-originating-user-namerilianjob-name   testprint!copies#
finishings!job-cancel-after*0Djob-hold-untilno-hold!
                                                    job-priority2B
job-sheetsnoneBnone!    number-upDprint-color-mode
monochromejob-uuid-urn:uuid:65751982-1235-3d1d-78ae-29d4af8fa746Bjob-originating-host-name      localhost1date-time-at-completed
                                                                                �▒▒%+1date-time-at-creation
                                                                                �▒▒+1date-time-at-processing
                                                                                �▒▒+!time-at-completedb�j!time-at-creationb�j!time-at-processingb�j!job-id=# job-state       Djob-state-reasons▒processing-to-stop-point!job-impressions-completed!▒job-media-sheets-completedEjob-printer-uri+ipp://5x5linux-manjaro:631/printers/hp-home!
                                                                                job-k-octetsI▒document-format-supplied▒application/octet-streamI▒document-format-detectedapplication/vnd.cups-pdf-bannerIdocument-formatapplication/vnd.cups-pdf-bannerBdocument-name-supplied        testprintAjob-printer-state-messageDjob-printer-state-reasonsmedia-empty-warning

[5x5linux-manjaro cups]# cat c00062

Gattributes-charsetutf-8Httributes-natural-languageru-ruBjob-originating-user-namerilianE
                                                                                printer-uri+ipp://rilian@localhost:631/printers/hp-homejob-nameПробная страницаI▒document-format-detectedapplication/vnd.cups-pdf-bannerIdocument-formatapplication/vnd.cups-pdf-banner!
                                     job-priority2job-uuid-urn:uuid:b612bc0b-d334-3686-76b2-42f442792db8Bjob-originating-host-name      localhost1date-time-at-completed
                                                                                �▒+1date-time-at-creation
                                                                                �▒
                                                                                +1date-time-at-processing
                                                                                �▒
                                                                                +!time-at-completedb�j�!time-at-creationb�j�!time-at-processingb�j�!job-id>#  job-stateDjob-state-reasons▒processing-to-stop-point!job-impressions-completed!▒job-media-sheets-completedEjob-printer-uri+ipp://5x5linux-manjaro:631/printers/hp-home!
                                                                                job-k-octetsDjob-hold-untilno-holdB
job-sheetsnoneBnoneAjob-printer-state-message6Задание отменено на принтере.Djob-printer-state-reasonsmedia-empty-warning

error_log.txt
Did 63 and 64 with debug logging (also same file, 63 is sucessful, 64 is failed)

Tried to print both methods into file devices, and see this:
jobs.tar.gz
Maybe this bug caused by a wrong colorspace?
[rilian@5x5linux-manjaro ~]$ file failed-job
failed-job: Cups Raster version 2, Big Endian, 300x300 dpi, 2480x3508 pixels 1 bits/color 1 bits/pixel ColorOrder=Chunky ColorSpace=black
[rilian@5x5linux-manjaro ~]$ file success-job
success-job: Cups Raster version 2, Big Endian, 300x300 dpi, 2480x3508 pixels 8 bits/color 8 bits/pixel ColorOrder=Chunky ColorSpace=sGray
[rilian@5x5linux-manjaro ~]$

@tillkamppeter fixed the issue by editing PPD (reference earlier).
Correct PPD:
printer.ppd.txt
There was an issue than PPD was set on RGB color model, and RGB color model was not defined in PPD. So, if printer supports only monochrome, we should not define RGB in PPD, or allow saving default settings (see https://github.com/OpenPrinting/cups/issues/415). So, when creating a driverless, we should check printer attributes and set default colormodel only to supported values.
And printing from lp works, I guess, because we have https://github.com/OpenPrinting/cups/issues/421

@alexpevzner is the bug fixed?

@tillkamppeter?


Spanish translation

Hello, I can translate for free the scripts for beginners since at first we need to get used to English but it's hard when we don't understand it. Let me know if you're interested.

I understand spanish and portuguese. if you need, I am available


Updated docker file for controller and clusterctl.

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes https://github.com/multicloudlab/cluster-api-provider-ibmcloud/issues/44
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

NONE

/lgtm


more marathon-lb fixes

@alberts  Shouldn't we release a new package version (->10) ? Not sure if users will be able to catch it.


[question] Support for SonarQube 5.6

SonarQube 5.6 LTS is released some days ago. Are there any plans / timeline to support the new version?

+1

Sonar has made big changes on plugin APIs and some APIs are no longer available or working as before. For example, code duplication API is no more available. Now, if you want to support a language you have to provide a lexer based on SSLR. If you don't do that, you can't set information about the file metrics (number of lines, number of line of comments, number of line of code...).
I think that our plugin could be adapted quickly (code is quite simple and just simplifies calls to Sonar APIs) but the most difficult part is to understand and find a way to make features still working correctly with Sonar 5.6+.
For now, I tried to find solutions to make it work with Sonar 5.5. I didn't try for Sonar 5.6. We will try it but I don't know when  and I can't ensure that it will be possible.
But it is an open source project so you could also try yourself and I will be pleased to have external contributors.

Hi @aurelien-baudet  I'm very excited to see this plug in and also a little disappointed it won't work with 5.6.  We are also looking to move to Sonar 5.6 LTS. On reviewing 5.5 did you find some of the standard rule violations will work correctly e.g. for eslint?  I wonder if we can at least support a subset of the analysis and allow the others to be disabled whilst we work on getting the other report types imported.
Thoughts?

I noticed most of the reports are configurable so perhaps it does work in 5.6 for importing some linters such as eslint reports if others are turned off which don't work.

Hello,
thank you for the great plugin!
After upgrading to Sonar version 5.6 we have experienced some problems so I wanted to check whether it is still the case that 5.6 version is not supported?
Also, we are now having a multi-module project: is this supported by the plugin?
Thanks in advance!

Try to use https://github.com/Pablissimo/SonarTsPlugin

Hi @aurelien-baudet! Thanks for explanation about Sonar 5.6.
I'm running Sonar 5.5 with SonarScanner 2.8 (by gulp-sonar) and generating reports with sonar-web-frontend-reporters and JSCPD with gulp-jscpd.
However the duplication reports aren't reaching Sonar.
Do you know if this can be related to code duplication API deprecation?
Thanks in advance!

@fsmaia  @aurelien-baudet  already answered this question in a previous post (see above)
It seems that he is pretty muched occupied this days.
About the problem of duplications, we have the same problem, we generate the js-duplication.xml with the sii reporter, the file is read and added to sonar api measures but the measures do not displays in the sonar interface (btw, we use the 5.6 release). I tried to debug quickly but i didn't notice something strange.
Btw, @aurelien-baudet, i did a pull request to correct a problem of regexp we encountered with the java plugin and Sonar 5.6 (the code resolved our problem).
We also did corrections in the reporters, i'll try to do a pull request for it this week.

We also did corrections in the reporters, i'll try to do a pull request for it this week.
I have a bit more spare time than Aurelien has, so this one should be merged quickly. One day i'll dig in the plugin code enough to review and merge PR but i neither do have enough time for that ATM, so you'll have to wait for Aurelien to do it.

Hey Guys,

Native eslint rules should be included. You have to configure your Sonar Rules to activate or deactivate ruleset. If the defaultruleset exclude them you can tune them in sonar.
The sure thing is the reporters report them. The main issue with upgrading the plugin for more recent sonar version is the pure removal by sonar of some API we used and don't have alternative anymore to display this informations.


Checkpoint/backup in case of crash

This is a great package! I was just wondering if there is any way in the package that supports checkpoints. Sometimes, there could be a crash/error running at a certain parameter set. It would be nice if there is a checkpoint file so that re-running the parameter sweeping would not re-run the already-run sweep.

Hi, thanks for your interest in the project.
I'd see this as a 2-step post-processing task. You could use a bool field named "crashed" to mark crashed runs. There are two ways to generate that.

Add a "crashed" check to func after the workload has exited and add the "crashed" field to the dict returned by func
Have a post-processing script add the field to the database, iterate over all psets, parse the run's output (disk) and update the pset's "crashed" value (database record)

I'd use the latter since here you have full control over post-processing you data (i.e. the criterion for what counts as crashed or how to detect a crashed state might change). You can re-run post-processing and setting the "crashed" flag as often as is needed.
Then have a second driver script (see this part of the README), that filters only crashed=True runs from the old database and re-runs those. Repeat that until no crashed runs remain.
See also this run script and this data analysis script for worked out examples (adding a column, parse output, update field values).
In your final database, you will have all crashed runs and the final good run for a specific pset (different _run_ids). In a final data evaluation script, simply use all crashed=False runs only.


Validate -i value for ssh command is an existing app instance

What Need Does It Address?
Without this change, passing a -i value that is equal to or greater than
the total number of instances the application has results in a cryptic
error message about the ssl handshake, which can lead users down a false
trail.
Possible Drawbacks
To keep the validation checks for the -i flag together, I moved the not-negative validation check after the creation of cmd.opts and cmd.appReq. No tests were upset by this, but it could be the case that due to factors I didn't catch--if populating cmd.appReq is expensive, for instance--this could result in slower feedback when you enter a negative value for -i.
Also, I didn't add any i18n translations for the new message. Note: When trying to run bin/i18n-checkup, I observed that the schema of the translation .json files was completely changed. On Slack, @anand indicated that this was probably due to the fact that the team is using a particular version of i18n4go that is different than the one I got with go get, and that I should not make any changes to the translation files and submit anyway.
Why Should This Be In Core?
It improves the messaging of a core feature, as opposed to adding new functionality.
Description of the Change
In addition to checking that the -i value is non-negative, fetch the InstanceCount of the specified application and ensure the -i value is less than that. If not, fail with a descriptive message.
Applicable Issues
https://github.com/cloudfoundry/cli/issues/1130

@davwards When I have one running instance of the app "my-app", the following no longer works:
$ cf ssh my-app -i 0
FAILED
Incorrect Usage: The specified application instance does not exist

NAME:
   ssh - SSH to an application container instance
...

The Requirements method is meant for setup so that the Execute method can perform the core logic of the ssh command. What you have could work, if you did a cmd.appReq.Execute() before performing the check. This will make the API call to get the application object. Without it, calling cmd.appReq.GetApplication() returns an empty application model with instance count defaulting to 0, thus the scenario above.
However, the calling function that runs Requirements and Execute is already responsible for running cmd.appReq.Execute(). It would be much cleaner to move this check in the Execute method.

I see! That suggests that the way I simulated the situation in ssh_test wasn't true to life; how would I do that properly?

@davwards At the layer that was being unit-ish tested, you were doing the right thing. The correct way to expose this bug would be through integration tests. You can add a test for this here, and you can use this as an example.

Hi all; I'm getting pulled off the Labs beach, so my available time to work on this is diminishing. Getting the bosh-light integration test environment set up is proving pretty difficult. All this to say, I don't expect to be able to deliver an integration-test-driven fix soon.
@nickwei84, I also feel like my understanding of the test setup is incomplete; it seems odd to me that the unit test I wrote could be correct, given that the implementation was completely broken. Is there not a way to simulate the life-like behavior of cmd.appReq.Execute() and cmd.appReq.GetApplication()? (In particular, the fact that GetApplication() returns an empty model until Execute() has been called.)

@davwards I'd recommend getting a PWS account and test against that.
The unit tests for the Requirements() and Execute() methods intrinsically have different assumptions. The calling function in cf/cmd/cmd.go should tell you what these assumptions are link to code chunk. Following the order that things are called, stubbing out GetApplications() in the Execute() method would have been the right thing to do.

@davwards Please let us know if you think you won't be able to get to this any time soon and would like us to finish the job.

@dkoper Indeed, feel free to wrap this up; I don't want it to get stuck in limbo waiting on me.

resolved the issues which arose in an initial review


update: snapshot_indexer_evm - for U256

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
3855

Relevant Lines:
6402

💛  - Coveralls


Improve binding element type inference using CheckMode

Fixes #49989
Alternative to PR #50241.
Here, to prevent false circular-relationship on binding elements initialized with their siblings (like the code segment below), we've utilized CheckMode values other than Normal as an indicator of suppressing type-checking errors.
const [a, b = a] = [0];
// or
const [a, b = a + 1] = [0];

~One gotcha in this PR was to revert the updated links (i.e., links.type) of a symbol. Because once a circular relationship error was encountered the type of the symbol is inferred to be any and then somewhere in the call stack, the symbol's associated links.type would be assigned to that returned any type. So, in cases other than CheckMode.Normal we'd replace back the links.type old value.~ (Sorry, that was not up-to-date)
The gotcha is that I had to suppress updating the symbol's links.type (to any type) for other than CheckMode.Normal cases, because that would block further efforts to find the correct type for the symbol. Now, I'm thinking maybe it's better to also check if the returned type is any and then do the suppression. I didn't find any better approach than this, so let me know if there's one:
function getTypeOfVariableOrParameterOrProperty(symbol: Symbol, checkMode?: CheckMode): Type {
    const links = getSymbolLinks(symbol);
    let result = links.type;
    if (!result) {
        result = getTypeOfVariableOrParameterOrPropertyWorker(symbol, checkMode);
        // For a contextually typed parameter it is possible that a type has already
        // been assigned (in assignTypeToParameterAndFixTypeParameters), and we want
        // to preserve this type.
        if (!links.type && !(checkMode && checkMode !== CheckMode.Normal)) {
            links.type = result;
        }
    }
    return result;
}

Further issues
Although this PR resolves common cases like the one above, but in cases like below false errors still occur. I didn't dig more to fix such issues because handling them would, in my opinion, clutter the type-checker without significant value in return due to the rarity of such usages. Please correct me if I'm wrong.
const [a, b = (() => 1 + a)()] = [0];

@babakks Do you want to keep working on this? I'd like to close it otherwise to avoid stale PRs.

@sandersn I'll try to address @weswigham's comment soon (before the weekend). Is that okay?

Sure, no big rush, it's been months since I looked at this =)

@sandersn Since this PR was based on an old commit of the main branch, I re-applied the changes here (with a slight modification to restrict the side-effects) on another PR, #56753. Please close this one and review the other when you deem fit.


Validate codables

Most of my usages of codable forms are as follows:
guard let form = try? request.read(as: SomeForm.self), form.isValid else {
    response.status(.badRequest)
    return next()
}

I was wondering if it makes sense to formalise/generalise this:

Add a Validatable protocol with an isValid property.
When decoding a type that also conforms to Validatable, throw an error if the validation fails.

request.read already checks if the form's fields are of the correct type, so it makes sense to check the values as well. If conforming to a protocol could get Kitura to do the validation automatically, that would increase safety, as it's easy to forget to add form.isValid to every read operation.
Note that I only use this for simple validation checks (that the type can do itself). If validation has dependencies (such as a database connection), I do it separately. I don't think this can be generalised without a proper dependency injection system.

Thanks for your idea, it sounds interesting.  I'm wondering why you couldn't implement this solution in your app without it being part of Kitura?  You could define Validatable yourself and write a helper that you use inside your route handlers?

I could and I probably will :) I was just wondering if this is general purpose enough to add to Kitura.

OK, let us know how the pattern works in practice. If it's generally useful we could certainly consider adding it to Kitura.

I gave this a try, and while it does work, I feel it's a bit too cumbersome to do on my end.
I used the following protocol and extension:
protocol Validatable {
    var isValid: Bool { get }
}

extension RouterRequest {
    func readAndValidate<T: Decodable & Validatable>(as type: T.Type) throws -> T {
        let result = try read(as: T.self)
        guard result.isValid else {
            throw ServerError.invalidForm
        }
        return result
    }
}

I have two issues here:

I had to create a new error type here, which doesn't really fit my application. In my application, errors are only used for internal server errors (things that should not happen). User errors are reported with a 400 Bad Request. While I can still do that, it feels silly to have to create and throw an error, just to catch it and return a 400.
Ideally, I'd want the new readAndValidate method to be an overload of the existing read method, where one takes a Decodable & Validatable and the other a Decodable. This way, I don't have to remember to call the right method, which defeats the purpose of not having to remember to call isValid. Unfortunately, this is not something I can do on my end, as I cannot delegate from the former to the latter (the method will just call itself). I could ofcourse copy/paste the implementation of read into my read, but that's not a clean solution.

Thanks for looking into this. I had another thought - as your SomeForm is Decodable, why not implement the validating logic in a init(from:) method instead of letting the compiler synthesise it?

I was hoping to build a simple validation protocol/framework that could be used to validate anything that needs validation.
It would be nice if there was some declarative way to express validation constraints. Java, for example, has a Bean Validation API that lets you add validation annotations to domain types. Instances of these types can then be validated whenever validation is needed, such as when parsing a form of before persisting to a database.
Have you look at Vapor's validation framework (https://docs.vapor.codes/3.0/validation/overview/)? Kitura could benefit from something like this. It would be even better if, in the future, Kitura and Vapor could share a common framework :D

@djones6 @Andrew-Lees11 please give your thoughts :-)

So this sounds like a good idea. The point of read as and Codable routes is that you get the object you expect and if you have constraints beyond the type it makes sense for you to add that when you define your object. Normally you could add this to the init but because it is codable the init from decoder would be fairly complicated.
I assume in your implementation isValid would be a computed property where you check the fields of your object. Would this make more sense as a function?
lastly, I like the idea of overloading read and making a validation framework to make it easier for the user.

I assume in your implementation isValid would be a computed property where you check the fields of your object. Would this make more sense as a function?

Yes it was a computed property. I don't think it makes more sense as a function, as that would indicate the implementation can be quite complex (whereas computed properties should be simple in implementation).
Vapor's implementation is interesting too. It's definitely more powerful, but for simple use cases, it feels over engineered, making it hard to use.

Ok I'm happy with it as a computed property. I think in most cases you are just going to be checking the value of your fields so having a computed property seems sufficient for this case. Would you like to raise a PR with your suggested change?

@ianpartridge A reason to avoid validation during init(from:): the TypeDecoder (used during Swagger generation) works by creating an instance using dummy values.  Validation during init would cause this to fail, or require a mechanism to provide your own (valid) dummy values.
@svanimpe Apologies being late to the party...
I think it makes a lot of sense for this to be a general purpose mechanism, and to have Kitura's Codable routing recognize when types are Validatable, and only pass instances to the user's route handler that pass validation.
My preference would be for a mechanism that can communicate back the nature of a validation failure.  A simple (synchronous) implementation using Error might be something like:
public protocol Validatable {
    func validate() throws
}

struct SomeForm: Codable, Validatable {
  let name: String
  func validate() throws {
    guard !name.isEmpty else {
      throw ValidationError("Name field cannot be empty")
    }
  }
}

do {
  let form = try request.read(as: SomeForm.self)
  try form.validate()
  // continue processing
} catch let error as ValidationError {
  Log.error("Invalid form received: \(error)")
} catch {
  Log.error("Unable to decode form: \(error)")
}

I wonder however if it's worth making it asynchronous - what if validation required you to consult some third party? For example, for a registration form, checking an e-mail blacklist service or validating an address against a property or postcode database.  Here's an async version:
public protocol Validatable {
    func validate(completion: @escaping (ValidationError?) -> Void)
}

struct SomeForm: Codable, Validatable {
    let name: String
    func validate(completion: @escaping (ValidationError?) -> Void) {
        guard !name.isEmpty else {
            return completion(ValidationError("Name cannot be empty"))
        }
        completion(nil)
    }
}

let form = try? request.read(as: SomeForm.self)
form.validate { (error) in
    if let error = error {
        Log.error("Invalid form received: \(error)")
        return next()
    }
    // continue processing
}

Personally, I'd prefer to stick to simple, synchronous, O(1) validations that can be done using only the properties of the form. From a design standpoint, I really wouldn't want a simple form type to require access to the database or some other service. If more complex validation is required, I do it in the route handler that uses the form. That handler already has access to these services.

@ianpartridge and I discussed this.  Something we'd like to be able to do is to represent validations in the OpenAPI (swagger) specification that Kitura can generate for a REST API.
When your Codable route handler is registered with the router, the types declared in your handler are inspected by the TypeDecoder and expressed as definitions (models) within the swagger document.  We'd want to also be able to express the constraints on the values for those definitions by deriving those from the code that is used to validate them.
To do this, we'd need an API where the constraints are registered on the Validatable type, and then executed against an instance of that type.  Although I haven't looked closely at Vapor's API, it seems similar in many respects.  However I'd want to keep it simple and accessible.  I'm not sure yet whether those two goals are compatible.


random@ issues

Hi there,
I am trying to use random@, and I've found that it is malfunctioning for me. It is not sending out the desired result to other acts (it doesn't seem to be sending anything at all), and it will also erase all data for each randomizer if either another randomizer is selected (alt-clicking on another number) or the number slider is changed on the far left. This is new behavior as of the last couple of days (I'm not sure what has changed, but I just now deleted all ppooll data and reinstalled Max, so it's all the freshest stuff). Thanks!

its working here.
pls give me steps to reproduce.
what is "alt-clicking on another number" ?
why do you alt-click on which number?
...
i open random@, edit the second line after 1: with ho_st1 vol 0 0. 1.
then click on 1 in the 3rd line and see the volume in ho_st1 being randomized between 0. and 1.
...
it might very well be, that random@ is hard to understand, how to get wanted results.
pls give me instructions on what is unclear in the patch or info.

... i did a few cosmetic updates on random@ lately because i used it in the factiory-environment "ducks".
but this should not have changed its behaviour.

Still not working for me (I have used it a bunch before this). Alt-clicking as per the info ("alt click on a number to select it without switching"). If I do anything to change the active randomizer, it erases everything I've entered, and is not sending out anything to host@ when I copy what you've done. Thanks!

do you see any errors or duplicate objects in the max-console?
if the problem persists, we only can do an online meeting to solve that.

@Pogslammer  i did some facelifting on<EMAIL_ADDRESS>maybe it works for you now. if not lets look at it...

Fixed! It may have been the facelift (looks great!), though I haven't used ppooll since the II.sub bug fix, so it may be that. Thanks so much for all your efforts.


using dark theme instead of light

I've added margin and padding, made the loading a little bit prominent.
Update: input box bg is darker and the text is white.

You'll probably look at the vercel deployment but here are images.