[TEST] deploy changes/additions to existing config to 1-n BUs

request by Christine.
this is us testing our #2 pipeline:

create multiple changes
commit these into separate user stories (sometimes 2 changes, sometimes just 1 per US)
promote & deploy to "pre-target"
confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
try to selectively back-promote 1 user story to 1 prod BU
confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
try to selectively back-promote 2 user stories at once to 1 prod BU
confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
try to use mass-backpromote feature to deploy all remaining user stories to both prod BUs
confirm deployment worked

Tested and working:

[ ] create multiple changes
[ ] commit these into separate user stories (sometimes 2 changes, sometimes just 1 per US)
[ ] promote & deploy to "pre-target"
[ ] confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
[ ] try to selectively back-promote 1 user story to 1 prod BU
[ ] confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
[ ] try to selectively back-promote 2 user stories at once to 1 prod BU
[ ] confirm deployment worked (in SFMC); confirm target BU's folder in git master branch (github)
[ ] try to use mass-backpromote feature to deploy all remaining user stories to both prod BUs
[ ] confirm deployment worked

Content on source:

Automation in source:

Asset in source:

DataExtension in source:

Ran deploy into pre-target bu with 2 user storys, one with the dataExtension change, and the other with the automation and asset changes:

Automation in pre-target:

Asset in pre-target:

DataExtension in pre-target:

Ran back-promote into target_1 bu with 2 user storys, one with the dataExtension change, and the other with the automation and asset changes:

Automation in target_1:

Asset in target_1:

DataExtensions in target_1:

The mass-backpromote all in the same time bug is fixed by this PR: #195 , for this issue #171

assuming this test is done successfully now


Lack of Notification for Removed Ship Nodes via Avahi mDNS Integration

Description
When a ship node is added, the Avahi mDNS picks it up and notifies the application through the api.ServiceReaderInterface about all currently visible services. However, when a ship node is removed, no update is sent. This poses a challenge for the implementer of the interface as there's no indication that the node is no longer available.
Version
Tested with CEMd (577b756) and eebus-go (45c4e2d)
Expected Behavior
The implementer of the api.ServiceReaderInterface gets also updated when a ship node gets removed.

Thanks for the bug report and the PR for that. It is great to see the first contribution for this repo :)


[Question] WorkerHandler doesn't extend Handler

I have cloned this repository and, when I try to compile it, I have an error telling me that WorkerHandler doesn't extend Handler.
I have looked into it a little bit and I found out my problem comes from the keyword "final" before the argument "message" in the "handleMessage" method.
One of the errors I have in Android Studio is :

Error:(113, 5) error: method does not override or implement a method from a supertype

If I remove the final keyword, it compiles just fine.
I thought this might have something to do with Java 8 so I install Java 7 and update my alternative to use Java 7 but I have the same error.
Here is a link to a pastebin with the result of my gradle assemble command from a freshly cloned copy : http://pastebin.com/Bss5XuwR
I have asked around me for other people to try to compile and they manage to do it just fine.

It seems to me this is the root cause:
./agera/agera/src/main/java/com/google/android/agera/Common.java:104: error: cannot find symbol
  static final class WorkerHandler extends Handler {
                                           ^
  symbol:   class Handler
  location: class Common

Some setup went wrong or you accidentally removed the import of android.os.Handler?
The final keyword on a parameter does not change the signature of a method; it only affects whether the body of that method can change the value of that parameter.
Also, Android Studio should fully support Java 8 by now.

I understand the confusion but as you can see in the pastebin, I haven't changed anything, it comes from the repository directly. The error telling me that the problem is from the handleMessage method is not shown in the pastebin because it doesn't print in the command line but in Android Studio.
I know that the final keyword doesn't change the signature of the method that why I don't understand.

I think I figured out the problem. What was solving the problem was not the removal of final but my Android Studio plugin which was optimizing the import. While optimizing the import, it would reorganize them and put import android.os.Handler at the top of the list.
After some more testing, it seems that import android.os.Handler needs to be above import com.google.android.agera.BaseObservable.Worker because Worker has a reference to WorkerHandler and I guess that it is treated before the import android.os.Handler and that's why it cannot find the symbol.
Sorry for wasting your time on this.

Import statement ordering should not matter either, at least per Java specification..... If your issue is fixed by reordering imports, I think something deeper down is broken...

I had the exact same problem mentioned above and strangely enough changing the order the import statements did the trick.


[GITHUB] Setup GitHub CI (#1)

Why is the change needed?
As mentioned in Issue #1, the CI is only implemented in the (internal) GitLab repository and not on the (public) Github one.
What changes does the patch introduce?
Implements a CI pipeline as a GitHub workflow.
How was this patch tested?
Manual review.

the change itself LGTM, however the CI failures seem valid errors due to different precisions. We have to fix the tests before merging this...

Can you open a MR on our gitlab to fix the issue with python versions > 3.8? @apierg @dennisfcc

Can you open a MR on our gitlab to fix the issue with python versions > 3.8? @apierg @dennisfcc

I opened the MR.

Closes #1


fix: upgrade axios

Upgrade axios to >= 1.6.0

:tada: This issue has been resolved in version 2.5.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Fixed in issue 1.6.2.
Closing.


Feature/essifi 133

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

PR can be approved
@maikel-maas
Given the simplicity of the questions and the updates by Hafeez, I can answer the resolution for you Maikel


Update Jetty to 12.0.8 + other dependencies

https://github.com/jetty/jetty.project/issues/11592

@martint @electrum PTAL


Setup website cicd

What

When we make edits to the website, have it be deployed automatically

How

Use GitHub CI/D, fallback to CircleCI

Related

#210

References

https://github.com/marketplace?type=actions
https://help.github.com/en/actions/automating-your-workflow-with-github-actions
@steebchen is a resident expert gh ci now

Merges to master trigger new deploys of gh-pages 🎉


Pin Icon BitmapDescriptorFactory.FromView does not work all time

I am using this custom icon in all my calls, but sometime the icon does not show and not throw any exception.
PIN
pinPosicao = new Pin
{
  Type = PinType.Place,
  Position = position,
  Label = item.StringDataEvento,
  Icon = BitmapDescriptorFactory.FromView(new BindingPinView("", "pin_red.png"))
};
_mapa.Pins.Add(pinPosicao);

VIEW
XAML
<?xml version="1.0" encoding="UTF-8"?>
<StackLayout xmlns="http://xamarin.com/schemas/2014/forms"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             WidthRequest="37"
             HeightRequest="48"
             AnchorX="0.5"
             AnchorY="0.8"
             x:Class="Views.Component.BindingPinView">
    <AbsoluteLayout VerticalOptions="FillAndExpand" HorizontalOptions="FillAndExpand">

        <Image Source="{Binding ImageSource}"
            AbsoluteLayout.LayoutBounds="0, 0, 37, 48"
            AbsoluteLayout.LayoutFlags="None" />

    </AbsoluteLayout>
</StackLayout>

CS
using Xamarin.Forms;
using Xamarin.Forms.Xaml;

namespace Views.Component
{
	public partial class BindingPinView : StackLayout
	{
		private string _display;
		private string _imageSource;

		public BindingPinView(string display, string image)
		{
			InitializeComponent();
			_display = display;
			_imageSource = image;
			BindingContext = this;
		}

		public string Display
		{
			get { return _display; }
		}

		public string ImageSource
		{
			get { return _imageSource; }
		}

	}
}

I tried to copy the example, but something does not work.

I can confirm this annoying behavior, it happens only on Android (no problem on iOS):
With FromView(...), some subviews (images) are loaded, others not. The text always works.
It is not related to the images itself, it happens randomly:
load page: markers 3 & 4 of 10 have no image, rest work
reload page: now markers 1, 4, 7 have no image
reload again: now only marker 9 has no image
etc.
It is exactly like in this closed issue (see screenshot): https://github.com/amay077/Xamarin.Forms.GoogleMaps/issues/114
This was NOT fixed. The user closed it because he found a workaround with "fromSource", but for my map I need markers with custom images and dynamic text, so that is not an option.
I tried putting every section of the related code to the main/ui-thread and also to create the markers with delay (after InitializeComponent(), even after OnAppearing() - nothing works.
Note: it may be related to some Android-specific internal change to how the image is loaded to the marker and then there is no callback to redraw the marker if it takes too long or something, at least that is a theory I read here:
https://github.com/airbnb/react-native-maps/issues/100
Those people seem to have the same problem and they posted many "hacks" to fix it, but I am not experienced enough to do it in xamarin forms, I believe amay007 has to implement a fix in the android-specific code of the nuget.
I would literally pay money to get this fixed reliably :)

_pin.Icon = BitmapDescriptorFactory.FromView(
	new ContentView {
		WidthRequest=100,
		HeightRequest=100,
		Content = new Image {
			Source = ImageSource.FromUri(someHttpUri))
		}
	 }
);

I want to change PinView (include image fromUri)
But this does not work at first.
But it works from the second. (because cached image)
(in iOS)

can confirm this. It happens sometimes on map initialization, when new View with map created, or - more rare - when switching between apps or pages, and map reinitializes.

BitmapDescriptorFactory.FromView
Where I tried
ImageSource.FromResource dose not worked(both Android and iOS).
ImageSource.FromFile worked(Android). iOS not confirmed.
BitmapDescriptorFactory.FromStream worked on both Android and iOS.
There was a problem of #40(Why custom pin icon in iOS bigger than Android?) on iOS, but a modified version (2.3.0) was released on 2018/1/23, and confirmed that it works.

I found that when using the FFImageLoading plugin, using ImageService.Instance.LoadCompiledResource("your_image_here.png").Preload(); before you load the pins, fixes this issue that sometimes images are not loaded. I hope this helps others with this issue.

@amay077 I am still seeing BitmapDescriptorFactory.FromView only work sometimes.

Can anybody tell me what I need to do, in order to shrink my pin? Now is too large.
I am using Icon = BitmapDescriptorFactory.FromBundle("locations_pin.png")

Can anybody tell me what I need to do, in order to shrink my pin? Now is too large.
I am using Icon = BitmapDescriptorFactory.FromBundle("locations_pin.png")
And my loications.pin image is under Assets folder

have you got it beacuse im also facing same issue

Can anybody tell me what I need to do, in order to shrink my pin? Now is too large.
I am using Icon = BitmapDescriptorFactory.FromBundle("locations_pin.png")
And my loications.pin image is under Assets folder

Also facing the same issue in iOS. Seems to be related to #40 that was closed claiming it was fixed, but the custom pin in iOS is still around 5x bigger than in Android (created using BitmapDescriptorFactory.FromBundle()), and also the same size bigger than the pins created with BitmapDescriptorFactory.DefaultMarker().

Same here, years after they closed it with latest stable version., icon too large on iOS, has to do w/ map api v3 which has a size setting, but i don't see how to specify in this code

Can anybody tell me what I need to do, in order to shrink my pin? Now is too large.
I am using Icon = BitmapDescriptorFactory.FromBundle("locations_pin.png")
And my loications.pin image is under Assets folder

I have the same issue

IDK if everybody is suffering the same issue but this could be the reason?
"Wait for a GoogleMap to become available from a MapFragment or MapView that you have added to your application. You can obtain the GoogleMap instance by calling getMapAsync() and waiting for the onMapReady(GoogleMap map) callback."
ref: https://developers.google.com/android/reference/com/google/android/gms/maps/model/BitmapDescriptorFactory

I have the same issue.

I have the same issue.


[CLEANUP] rector: Add strict return type based on returned strict expr type

This applies the rule ReturnTypeFromStrictBoolReturnExprRector. For Details see:
https://github.com/rectorphp/rector/blob/main/docs/rector_rules_overview.md#returntypefromstrictboolreturnexprrector

Rebased it.

Should those PHPDoc @return statements also be deleted?

Should those PHPDoc @return statements also be deleted?

I think so, if they don't provide anything more than the type hint.

Rebased and removed the PHPDoc annotations.


How to get an artifact's parent directory?

Up until now, I have been following the documentation's suggestion of using cmd_args(my_artifact).parent() for this, but it doesn't work anymore as of the 2024-07-01 release. What is the suggested alternative?

Note that this doesn't really give you the artifact's parent directory.  It gives you a cmd_args() that contains the artifact's parent directory as something that you can pass into an actions.run().  In particular, it does not give you the artifact's parent directory as an Artifact, so you can't use it (for example) to ctx.actions.symlinked_dir(...) or various other methods.  And AFAICT, there is no way to do that.


ERROR: unable to listen on any of the requested ports: [{3306 3306}]

maria db port not aceessing.
Forwarding: gateway-mysql:3306 to pod gateway-mysql-6c7bb4bf4c-w9bnn:3306
ERROR: unable to listen on any of the requested ports: [{3306 3306}]
Actually this port not required to access remote side, but kubfwd is stopping here. Not accessing

Does kubectl port-forward work for your service?

Not working  i reinstalled  again and using kind cluster following error came
INFO[20:40:20]  _          _           __             _
INFO[20:40:20] | | ___   | |_   ___ / | | |
INFO[20:40:20] | |/ / | | | ' \ / _ \ |\ \ /\ / / _  |
INFO[20:40:20] |   <| || | |) |  /  |\ V  V / (| |
INFO[20:40:20] |_|_\,|./ _||   _/_/ _,_|
INFO[20:40:20]
INFO[20:40:20] Version 1.13.0
INFO[20:40:20] https://github.com/txn2/kubefwd
INFO[20:40:20]
INFO[20:40:20] Press [Ctrl-C] to stop forwarding.
INFO[20:40:20] 'cat /etc/hosts' to see all host entries.
INFO[20:40:20] Loaded hosts file /etc/hosts
INFO[20:40:20] Hostfile management: Original hosts backup already exists at /root/hosts.original
INFO[20:40:20] Forwarding: ahyushhra:8081 to pod ahyushhra-684c7fd97c-zqckj:8081
INFO[20:40:20] Forwarding: ahyushhra-elasticsearch:9200 to pod ahyushhra-elasticsearch-7d78fbccf-djqtr:9200
INFO[20:40:20] Forwarding: ahyushhra-elasticsearch:9300 to pod ahyushhra-elasticsearch-7d78fbccf-djqtr:9300
INFO[20:40:20] Forwarding: gateway:8080 to pod gateway-848ff8f467-z9l4v:8080
INFO[20:40:21] Forwarding: gateway-elasticsearch:9200 to pod gateway-elasticsearch-67db675bc9-w576t:9200
INFO[20:40:21] Forwarding: gateway-elasticsearch:9300 to pod gateway-elasticsearch-67db675bc9-w576t:9300
INFO[20:40:22] Forwarding: jhipster-grafana:3000 to pod jhipster-grafana-66c5c55bbf-8v4f7:3000
panic: interface conversion: runtime.Object is *v1.Status, not *v1.Pod
goroutine 181 [running]:
github.com/txn2/kubefwd/pkg/fwdport.(*PortForwardOpts).WaitForPodRunning(0xc000020690, 0xc000089200, 0x0, 0x0, 0x0)
/Users/cjimti/workspace/txn2/kubefwd/pkg/fwdport/fwdport.go:306 +0x617
github.com/txn2/kubefwd/pkg/fwdport.(*PortForwardOpts).PortForward(0xc000020690, 0x0, 0x0)
/Users/cjimti/workspace/txn2/kubefwd/pkg/fwdport/fwdport.go:130 +0x7ca
github.com/txn2/kubefwd/cmd/kubefwd/services.(*FwdServiceOpts).LoopPodToForward.func1(0xc000020690, 0xc000020870)
/Users/cjimti/workspace/txn2/kubefwd/cmd/kubefwd/services/services.go:474 +0x32
created by github.com/txn2/kubefwd/cmd/kubefwd/services.(*FwdServiceOpts).LoopPodToForward
/Users/cjimti/workspace/txn2/kubefwd/cmd/kubefwd/services/services.go:473 +0x91c
[root@mainnode ~]# panic: interface conversion: runtime.Object is *v1.Status, not *v1.Podpanic: interface conversion: runtime.Object is *v1.Status, not *v1.Podpanic: interface conversion: runtime.Object is *v1.Status, not *v1.Pod
-bash: panic:: command not found

These are two separate issues.
First Issue: Are you able to kubectl port-forward your gateway-mysql?
The second Issue is #114


Implement native plugin that will provide a list all apps installed on phone and watch

We need native plugin that will provide a list of apps that are installed both on phone and watch and can show notifications. This plugin is needed for Settings -> Notifications and muting -> Choose which apps can alert your watch screen. UI and filtering logic for the screen was done as part of #82 but list of apps was stubbed.

@crc-32 I think you completed that as part of the notifications update?


Loading status always displayed

Hello,
Thank you for this module.
All works great since a long time.
But, there'is a strange problem that always display a loading status "Chargement..."
See screen here
Here is the config.js
        {
                module: "MMM-PIR-Sensor-Lite",
                position: "top_right",
                config: {
                        title: "",
                        showDetection: false,
                        showCountDown: false,
                        sensorPin: 21, // GPIO pin
                        deactivateDelay: 30000,
                        commandType: 'vcgencmd',
                }
        },

Do you know why ?
Thank you.

You still have this issue? I had it too.
Turned out this module wanted to read the /dev/gpiomem with the pi user, but after upgrading my RPi to Bullseye (from Buster), this folder has the wrong permissions for use with the mirror.
Have a look here:
https://raspberrypi.stackexchange.com/questions/124402/user-getting-removed-from-group-after-reboot
When you run the provided pir.py script from the commandline as user pi it will give an error:
"RuntimeError: Not running on a RPi!"
I fixed it by adding below 2 commands to the crontab so it will 'stick' on reboots, as /dev/gpio is recreated (in memory) every reboot (note: it breaks some of the security on your pi, use with caution):
sudo crontab -e
@reboot sudo chown root.gpio /dev/gpiomem
@reboot sudo chmod g+rw /dev/gpiomem
After this the MMM-PIR-Lite worked again for me. (I forked the repo and made some other changes too).


Bug: Changes made on every key press in state in profile url change

Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for certain conditions.

Operating System: Windows
Browser: Chrome

Expected Behavior
Only perform change state when user clicks on submit or wait for certain seconds (1sec)
Current Behavior
The state is getting updated on every key press
Steps to Reproduce
Please provide detailed steps for reproducing the issue.

Just go to the profile page
Click on a profile pic
Start typing in the input field and keep the console open
You can see the error.

Screenshot

Solution:
Create debounce method or just submit string on button click
@agamjotsingh18 Can I work on this?

Can I Work on this??

@ShubhamPatil0723 are you working on this or should i assign to @Sohamkayal4103 ?

@ShubhamPatil0723 are you working on this or should i assign to @Sohamkayal4103 ?

This issue was not assigned to me, but sure let @Sohamkayal4103 work on it

Cool @ShubhamPatil0723

Sure @Sohamkayal4103, you can work upon it

can I work on it in gssoc23.

can i work on it ?

sure

sir I want to work on this issue under gssoc'23

hello, error mentioned here is different when I am clicking on change logo url.

can you tell me where can I just discuss this.


Unable to scrape NYT articles

Everything else seems to work reasonably well, though...

Not an issue anymore because the source for the news site has changed.


View suppressed vulnerability in Component view in 3.1

I suppressed vulnerability on Component view but after refresh I don't view this suppressed vulnerability in order to correct or comment.
Can you add possibility to view suppressed vulnerability in Component view like in Project View

Audit Mode: Disabled

Audit Mode: Enabled


[Update Request]: Schniz.fnm 1.35.1

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
Schniz.fnm
Package Version
1.35.1
Please describe the changes you would like to see
There is a new release(1.35.1) available

117458

Close with reason: Resolved by above PR;


Rework Dockerfile and Makefile to OCP standard ones

And rename the operator to alibaba-disk-csi-driver-operator, when at it.

cc @openshift/storage


Real Bug found on OpenUI5.org?

I think I found a real bug on OpenUI5.org. It appeared on Chrome 55 only and only on my MacBook this afternoon.
See attached video which shows some quick bug tracing that I did.
Not sure what caused it to appear right now. Maybe it has something to do with German Umlauts.
I think I'll try to open and close the window, hopefully this makes it disappear...

Have you tried f12?
Any console error?
On 22 Dec 2016 16:01, "Frank Weigel"<EMAIL_ADDRESS>wrote:

I think I found a real bug on OpenUI5.org. It appeared on Chrome 55 only
and only on my MacBook this afternoon.
See attached video
https://cloud.githubusercontent.com/assets/9580095/21431162/84770524-c866-11e6-8ee8-d140804956ec.gif
which shows some quick bug tracing that I did.
Not sure what caused it to appear right now. Maybe it has something to do
with German Umlauts
https://cloud.githubusercontent.com/assets/9580095/21431197/a7aaaf78-c866-11e6-8c67-56344a501448.jpg
.
I think I'll try to open and close the window, hopefully this makes it
disappear...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SAP/openui5/issues/1278, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAimjkAmyxn0Sdy2fiK-PvMAvYaSOK1jks5rKp7kgaJpZM4LUHiR
.

The bug was too close to F12, so I didn't dare to press it...

Looks serious and after watching the screencam I have to confirm it was a bug.
Any way to reproduce?

Definitely hit F12 and use the Ins[p]ector tool.

This is too hard to fix... Carry the issue over to the next service pack.

That's definitely a bug

On stack overflow, I was told to try and catch the bug.
But to do so, I first would need to know the bug's current location and second I don't know exactly what to do afterwards?
@akudev: according to some younger experts around here, the bug is self-reproducing - but only if there is yet another one. Sounds too risky to me to follow that path.
@qmacro: thanks for the tip. I tried but couldn't find the Ins(p)ector tool. I remember that in earlier versions of Firefox there was an icon that reminds me a bit of the current bug. But the latest Firefox no longer has that button. Or do I have to install some bugin?

Did you find the root cause?
Is it attracted to fiery birds maybe?

Bug didn't show up for 2 1/2 weeks now, so I'm closing this.


Could not acquire write lock for… errors

I just upgraded mvnd to 1.0-m6-m39 via Snap from 0.9.0 (using Java 11) and ran a build of my reactor with 27 modules as usual (max parallelism 11). It spat out some errors such as
Could not acquire write lock for '~/.m2/repository/.locks/com.github.spotbugs~spotbugs-annotations~4.7.3.lock'
Could not acquire write lock for '~/.m2/repository/.locks/commons-collections~commons-collections~3.2.2.lock'

and the build failed partway through
Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-bytecode-version) on project …: Execution enforce-bytecode-version of goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce failed: Could not acquire write lock for '~/.m2/repository/.locks/groupId~artifactId~1.234.lock' -> [Help 1]
Failed to execute goal some:plugin:1.2:some-mojo (default-some-mojo) on project …: Execution default-some-mojo of goal some:plugin:1.2:some-mojo failed: Could not acquire write lock for '~/.m2/repository/.locks/groupId2~artifactId2~5.678.lock' -> [Help 1]
Could not acquire write lock for '~/.m2/repository/.locks/groupId3~artifactId3~9.012.lock'

When I ran the build again, it passes, so I presume this was some sort of race condition, possibly involving artifact downloads (I had pulled in various POM updates since the last local build of the project).
No further details were provided, and I was not using -e so there was no stack trace giving context. I checked ~/.m2/mvnd/registry/1.0-m6/daemon-*.log which did not really add any more information:
Dispatch message: ExecutionFailure{projectId='…', halted=true, exception='java.lang.IllegalStateException: Could not acquire write lock for '~/.m2/repository/.locks/com.github.spotbugs~spotbugs-annotations~4.7.3.lock''}

If nothing else, the Throwable.toString of the cause ought to be included in the top-level error message I think.

Faced the same issue on 1.0-m7 windows version.
Apache Maven Daemon (mvnd) 1.0-m7 windows-amd64 native client (b2ef5d81997adbcdb72dc8c5603722538fa641fe) Terminal: org.jline.terminal.impl.jansi.win.JansiWinSysTerminal Apache Maven 4.0.0-alpha-7 (bf699a388cc04b8e4088226ba09a403b68de6b7b) Maven home: C:\work\tools\mvnd-0.7.1-windows-amd64\mvn Java version: 11.0.15, vendor: Eclipse Adoptium, runtime: C:\work\tools\java\jdk-<IP_ADDRESS>-hotspot Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
I was able to get a full stack trace
 Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire write lock for 'C:\work\repository\.locks\artifact~antlr~antlr~2.7.6.lock' in 30 SECONDS         at org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire (NamedLockFactoryAdapter.java:202)         at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:271)         at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:259)         at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:352)         at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:187)         at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:242)         at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectArtifacts (LifecycleDependencyResolver.java:193)         at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:131)         at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:361)         at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:318)         at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:217)         at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:178)         at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:77)         at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:166)         at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)         at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:114)         at io.takari.maven.builder.smart.SmartBuilderImpl.buildProject (SmartBuilderImpl.java:209)         at io.takari.maven.builder.smart.SmartBuilderImpl$ProjectBuildTask.run (SmartBuilderImpl.java:81)         at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:515)         at java.util.concurrent.FutureTask.run (FutureTask.java:264)         at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)         at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)         at java.lang.Thread.run (Thread.java:829)

@cstamas any idea ?

FYI.
I have discovered that there is probably some problem with the Maven resolver implementation.
I initially used apache-maven-3.8.8-resolver-1.9.7 but neither Redisson nor Hazelcast worked.
Now I am using apache-maven-3.8.8-resolver-1.8.2 and Redisson works but Hazelcast still doesn't work.
I am guessing this will be all eventually fixed in Maven 3.9 as soon as it matures first.

$ mvnd -v
Apache Maven Daemon (mvnd) 1.0-m7 windows-amd64 native client (b2ef5d81997adbcdb72dc8c5603722538fa641fe)
Terminal: org.jline.terminal.impl.jansi.win.JansiWinSysTerminal
Apache Maven 3.9.3<PHONE_NUMBER>9f1ead511c958d89bd2f672198ae9f)
Maven home: D:\projects\salog\software\mvnd\mvn
Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: D:\projects\salog\software\java
Default locale: en_US, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

But I also get this:
Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire write lock for 'C:\Users\hohwille\.m2\repository\.locks\artifact~com.caucho~com.springsource.com.caucho~3.2.1.lock' in 30 SECONDS
        at org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire (NamedLockFactoryAdapter.java:202)
        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:271)
        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:259)
        at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:352)

Windows Filesystem and file-locking is a disaster. However, with regular mvn the error does not occur even not when I run parallel builds (e.g. -T 2C). Please also note that also with mvnd the error goes away if I do not specify concurrent build (no -T option).

Windows Filesystem and file-locking is a disaster

I couldn't agree more.

the error does not occur even not when I run parallel builds

Trust me, it is purely non-deterministic, I thought the same at first.
Even Named Locks don't seem to be working perfectly yet.
"-Daether.connector.basic.threads=1 -Daether.connector.resumeDownloads=false" hasn't worked perfectly either.
From where I stand, this is a dead end at the moment.
My hopes lie with Maven 3.9

I was now able to reproduce the lock errors also with pure maven and without mvnd.
Therefore I created MNG-7868.
IMHO this issue here is kind of invalid as it is a bug in maven itself and not in mvnd.

Locking in Mavem aims to solve two things:

parallel build coordination (within one Maven parallel building process)
shared local repository across several Maven (ST or MT, parallel) processes

For brevity we call them

ST,  single threaded, the "usual" way of Maven working,
MT, multi threaded, or "parallel", either using -T with or without "smart builder"/mvnd and
MP, multi process case, when local repository is shared across multiple Maven ST/MT processes (on single or multiple hosts).

HOW locking is set up (especially for which scenario, MT/MP) is left to user, some examples:

the default locking (since 3.9.0) the rwlock-local as name says is (JVM) local, so handles only MT builds
the file-lock can handle MP cases (on single host, or on properly set up NFS volume)
for larger scale, usually CI use case with shared local repositories, we recommend the Hazelcast/Redisson solutions

By the way, for non-mvnd users I'd personally recommend to NOT use the "vanilla" -T builder (that comes with Maven), but rather use the superior Takari Smart Builder (see README). This will make Maven parallel builds behave similarly as mvnd (also uses Smart builder) sans the persistent daemon and logging feature.
I would really like to see a reproducer project that produces this kind of error, but let me explain what happens here...
By default, the parameter aether.syncContext.named.time (30 seconds) is the amount of time a synchronization context shall wait to obtain a needed lock. In latest Maven/mvnd releases the message is actually improved to clearly show that (as can be seen above in comments, but not in original issue description: "Could not acquire write lock for $lockName in 30 SECONDS"). So, there is no cause per se, the cause IS the timeout.
Sadly, way before NamedLocks (that are actually used as "low level fine grained locking implementation") the SyncContext was defined way earlier and I "inherited" it. Major problem with this API is "coarseness" of it.
My current assumption/focus is "hot artifacts": artifacts that are highly referenced (for example like slf4j-api might be in a project, or some "api" module that has zillion downstream plugin modules building against given api module, etc -- usually "star shaped" projects at least when dependencies observed) due SyncContext above could cause that parallel resolved module dependencies became serially resolved, and -- especially on larger projects -- the "looser" threads end up congested, waiting more then 30 seconds, that will cause the timeout.
Current (bad) workaround for this is raising the time limit using -Daether.syncContext.named.time=40 (default time unit is seconds) and "experiment", as this value theoretically depends on project layout and size. But is bad, as you want fast builds, but this actually slows it down even more.

An example of perf test against Apache Camel is here: https://cstamas.github.io/camel-perftest/
Sadly, I could not make it perform these errors.

So any (hopefully OSS) "reproducer project" is welcome, to sort out last bits of Maven locking. TIA!

This is a very good direction.
I have witnessed locking failures on larger projects even with Redisson and Hazelcast (as mentioned in the past).
These are probably timeouts in which case the plain error message I am getting Could not acquire write lock for ... is badly worded.
However, it seems I missed the error detail .
Could not acquire write lock for 'C:\work\repository\.locks\artifact~antlr~antlr~2.7.6.lock' in 30 SECONDS
which explains the problem.
I will increase the time limit using -Daether.syncContext.named.time and get back to you.

IMHO this issue here is kind of invalid as it is a bug in maven itself and not in mvnd.

I agree with this assesment, and is perfectly clear: mvnd only suffers from this bug (as it pressures the locking most), that is actually deep in resolver.

And one more note: with latest Maven 3.9.4 you have option to collect "diagnostic data" for locking as well, and in case of those timeouts, it will spit out the diag data, see here https://maven.apache.org/resolver/maven-resolver-named-locks/index.html#diagnostic-collection-in-case-of-failures
Note: collecting diag data has impact on heap usage, so you may need to tweak it, if you hit OOM.

Noted, the disgnostics work only with Maven 3.9.4 and resolver 1.9.14+
However, the timeout change didn't work:
using -Daether.syncContext.named.factory=semaphore-hazelcast -Daether.syncContext.named.nameMapper=gav -Daether.syncContext.named.time=60
SmartBuilder and Maven 3.8.8-resolver-1.8.2
I am still getting the same errors:
12:53:38.601 E Internal error: java.lang.IllegalStateException: Could not acquire write lock for 'artifact:XXX' -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.IllegalStateException: Could not acquire write lock for 'artifact:XXX'
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:121)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:963)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:296)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
Caused by: java.lang.IllegalStateException: Could not acquire write lock for 'artifact:XXX'
    at org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire(NamedLockFactoryAdapter.java:165)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:233)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:212)
    at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:272)
    at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:192)
    at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:242)
    at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:1150)
    at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:916)
    at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:361)
    at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:267)
    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:448)
    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:414)
    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:377)
    at org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:414)
    at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:405)
    at org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:82)
    at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:535)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:220)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    ... 11 common frames omitted

Should I wait for opportunity to run with Maven 3.9.x ? or am I missing something?

Sorry, all this above is true for Maven 3.9.4 and latest 1.9.14+ resolver...
Am really unsure what Maven 3.8.8-resolver-1.8.2 is.... Is it @michael-o product? https://maven.apache.org/resolver/maven-3.8.x.html
What stops you to move to Maven 3.9.4?

Nothing stops us, besides workload, commitments and priorities.
I have planned for this to happen later this year.

@cstamas @eliasbalasis Re: Maven 3.8.x with Resolver 1.9.x: Yes, I do produce and sign those deliverables. Cherry-picked commits allowing people access new Resolver if thy can't/want/whatever upgrade. I will upgade those to 1.9.15 shortly.

@cstamas We are using Apache Resolver 1.9.13 in a different project and started to see the locking issues as well. Can it be related to a slow file system? When was this locking introduced? Given that this is outside of mvnd should the issue be moved to the Maven Resolver project?
java.lang.IllegalStateException: Could not acquire lock(s)
        at org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire(NamedLockFactoryAdapter.java:219)
        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:271)
        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:259)
        at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:242)
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:231)
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:172)
        at org.eclipse.aether.internal.impl.collect.df.DfDependencyCollector.resolveCachedArtifactDescriptor(DfDependencyCollector.java:382)
        at org.eclipse.aether.internal.impl.collect.df.DfDependencyCollector.getArtifactDescriptorResult(DfDependencyCollector.java:368)
        at org.eclipse.aether.internal.impl.collect.df.DfDependencyCollector.processDependency(DfDependencyCollector.java:218)
        at org.eclipse.aether.internal.impl.collect.df.DfDependencyCollector.processDependency(DfDependencyCollector.java:156)
        at org.eclipse.aether.internal.impl.collect.df.DfDependencyCollector.process(DfDependencyCollector.java:138)
        at org.eclipse.aether.internal.impl.collect.df.DfDependencyCollector.doCollectDependencies(DfDependencyCollector.java:108)
        at org.eclipse.aether.internal.impl.collect.DependencyCollectorDelegate.collectDependencies(DependencyCollectorDelegate.java:222)
        at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:87)
        at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:327)
        at ...
        Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire write lock for 'artifact:junit:junit:4.13.2' in 30 SECONDS
                at org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire(NamedLockFactoryAdapter.java:202)
                ... 30 more
        Suppressed: java.lang.IllegalStateException: Attempt 2: Could not acquire write lock for 'artifact:junit:junit:4.13.2' in 30 SECONDS
                at org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire(NamedLockFactoryAdapter.java:202)
                ... 30 more

@guw this is definitely maven-resolver issue, but cannot say more without knowing more. Please try to enable "lock diag" (set system property --not Maven property!) aether.named.diagnostic.enabled=true.

@cstamas @eliasbalasis Re: Maven 3.8.x with Resolver 1.9.x: Yes, I do produce and sign those deliverables. Cherry-picked commits allowing people access new Resolver if thy can't/want/whatever upgrade. I will upgade those to 1.9.15 shortly.

@michael-o
Did you have any opportunity to publish the latest version of "Resolver" ?

@guw this is definitely maven-resolver issue, but cannot say more without knowing more. Please try to enable "lock diag" (set Java system property --not Maven property!) aether.named.diagnostic.enabled=true.
Edit: locking was introduced in Resolver 1.8.x but reworked/generalized in 1.9.x lineage.

It is with Java system property that I experimented but I never got any detailed output.
Also as @cstamas mentioned further up:

And one more note: with latest Maven 3.9.4 you have option to collect "diagnostic data" for locking as well, and in case of those timeouts, it will spit out the diag data, see here https://maven.apache.org/resolver/maven-resolver-named-locks/index.html#diagnostic-collection-in-case-of-failures
...
...
 This means mvnd is out of scope, as latest m7 uses older resolver....

It seems Maven 3.9.x is the only effective way.
However, I do vaguely recall having tried Maven 3.9.x at some point discovering some incompatibilities that I didn't have the time to explore, which may be implying that we are at a dead end.
I have planned for an upgrade to Maven 3.9.x before the ned of this year, at which point I am expecting to stumble upon any incompatibilities and I will let you know.

@cstamas @eliasbalasis Re: Maven 3.8.x with Resolver 1.9.x: Yes, I do produce and sign those deliverables. Cherry-picked commits allowing people access new Resolver if thy can't/want/whatever upgrade. I will upgade those to 1.9.15 shortly.

@michael-o Did you have any opportunity to publish the latest version of "Resolver" ?

@guw this is definitely maven-resolver issue, but cannot say more without knowing more. Please try to enable "lock diag" (set Java system property --not Maven property!) aether.named.diagnostic.enabled=true.
Edit: locking was introduced in Resolver 1.8.x but reworked/generalized in 1.9.x lineage.

@guw It is with Java system property that I experimented but I never got any detailed output (using https://maven.apache.org/resolver/maven-3.8.x.html)
Also as @cstamas mentioned further up:

And one more note: with latest Maven 3.9.4 you have option to collect "diagnostic data" for locking as well, and in case of those timeouts, it will spit out the diag data, see here https://maven.apache.org/resolver/maven-resolver-named-locks/index.html#diagnostic-collection-in-case-of-failures
...
...
 This means mvnd is out of scope, as latest m7 uses older resolver....

It seems Maven 3.9.x is the only effective way. However, I do vaguely recall having tried Maven 3.9.x at some point discovering some incompatibilities that I didn't have the time to explore, which may be implying that we are at a dead end. I have planned for an upgrade to Maven 3.9.x before the ned of this year, at which point I am expecting to stumble upon any incompatibilities and I will let you know.
This is not "mvnd" related though, without a shadow of a doubt. Should we post this somewhere else?

Planning to package today.

@eliasbalasis Distros delivered. Please check them out from the dist dev space.

@michael-o
many thanks for making the effort, it helps a lot.
I will try it and see how it goes.

@eliasbalasis could you please provide us feedback why did official 3.9.x release not work for you? I think the real path should be forward, instead to stick to one-man && non-asf maven customized distribution (that as example shows above, just makes things worse, as both users and devs are confused why things does not work while they should [IF it would be official distro])...

@cstamas
I agree with moving forward but I hope you understand that such transformations often have a cost that has to be prioritized, particularly when the relevant systems are used by multiple teams on multiple projects to eliminate disruption of any operations.
That said, I do recall having tried running some of our builds on Mavel 3.9.x as an experiment in the past but I cannot remember off the top of my head the exact errors.
However, like I said, I have planned for this transformation to happen before the end of this year, as part of our yearly technical debt handling effort, at which point I will know the exact problem and I will report it, if it is still effective.

As promised, I am now transforming our build systems to make use of Maven 3.9.6 and named locks for our parallel builds.
The first indications are promising, using a remote Redisson cache.
However, it will take a while to observe the system under heavy load.
I will be reporting findings here.

Unfortunately, after a little while the problem is still present.
Could not acquire lock(s)
I am switching back to -Daether.syncContext.named.factory=file-lock -Daether.syncContext.named.nameMapper=file-gav
This is not perfect but at least it hasn't reproduced the problem for a considerably long period of time.

-Daether.named.diagnostic.enabled=true did not reveal much, except detailed list of the active locks.
However, I was using the rwlock-redisson named locks factory.
I will try with other named lock factories.

semaphore-redisson named locks factory did not work either.
I will try with Hazelcast name locks factory.

The point of "diagnostic" is exactly that, please paste it into gist and put it here....

@cstamas,
I cannot share the build output because it contains references to private components.
Specifically for "redisson" named lock implementation, trust me when I say that the build output did not reveal much except detailed list of the active locks.
It contains only the list of locks at the time of failure and no stack trace or any detailed analysis of the errors.
Therefore it is pointless for me trying to cleanup the build output by removing the references to private references.
I observed this repeatedly using "gav" , "discriminating" name mappers.
(see https://maven.apache.org/resolver/maven-resolver-named-locks/index.html)
However, the "static" name mapper seems to be the only one working without producing any locking errors.
This is great progress from where I stand.
I am now trying to experiment with "hazelcast" named lock implementation and I intend to share the outcome.

At least you can do following as written here:
https://github.com/apache/maven-mvnd/issues/836#issuecomment-1706549388
You should be able to identity your "hot artifact", if you have one.

@cstamas,
I am using "aether.named.diagnostic.enabled=true"
which now seems to be working after upgrading to Maven 3.9.x
Also, identifying the hot artifact is easy.
It is included in the build output and it is different on every build.
However, this is not the problem I am trying to resolve.
The problem I have been trying to resolve for a long time,
is the Maven distributed locks malfunction,
which didn't seem to be working before Maven 3.9.x but seems to be working now,
with "static" name mapper and "redisson" named lock implementation.

I spoke too soon.
It is still not working.

Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
...
...
...
Java version: 17.0.10, vendor: Oracle Corporation, runtime: /usr/lib/jvm/jdk-17-oracle-x64
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "4.18.0-5<IP_ADDRESS>.el8_9.x86_64", arch: "amd64", family: "unix"
...
...
...
Redisson 3.23.4
1 connections initialized for <host>/<ip>:<port>
24 connections initialized for <host>/<ip>:<port>
...
...
...
Using the SmartBuilder implementation with a thread count of 12
...
...
...
Diagnostic dump of lock factory
===============================
Implementation: org.eclipse.aether.named.redisson.RedissonReadWriteLockNamedLockFactory
Active locks: 1

Name: static-artifact
RefCount: 7
  Thread[BuilderThread 5,5,] -> []
  Thread[BuilderThread 8,5,] -> []
  Thread[BuilderThread 7,5,] -> []
  Thread[BuilderThread 2,5,] -> []
  Thread[BuilderThread 1,5,] -> []
  Thread[resolver-1,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> []
  Thread[BuilderThread 11,5,] -> []
  Thread[resolver-3,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> []
  Thread[BuilderThread 0,5,] -> []
  Thread[BuilderThread 9,5,] -> []
  Thread[BuilderThread 10,5,] -> []
  Thread[BuilderThread 6,5,] -> []
  Thread[resolver-5,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> []
  Thread[BuilderThread 4,5,] -> []
  Thread[resolver-2,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> []
  Thread[resolver-4,5,org.apache.maven.artifact.resolver.DefaultArtifactResolver] -> []
  Thread[BuilderThread 3,5,] -> []

------------------------------------------------------------------------
Reactor Summary for <top level artifactId>:
...
...
...
Could not acquire lock(s)
<the hot artifactId>: Could not acquire lock(s)
...
...
...
To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.
Redisson 3.23.4
1 connections initialized for <host>/<ip>:<port>
24 connections initialized for <host>/<ip>:<port>
...
...
...

As pointed out, no error details


Version bump

Changes since release 0.43.0:

Move action_collector into fastlane_core for more comprehensive collection

👍  🚗


[FEATURE] Send search request query DSL json directly to search request

Is your feature request related to a problem?
Data Prepper is going to support configurable queries that will utilize the opensearch java client for search requests.
The query DSL is being taken is as a json string, and the opensearch java client does not support passing a Map or json string to pass this query DSL directly.
However, the opensearch java client requires queries to be modeled using the opensearch java client classes
What solution would you like?
An option to pass the search request directly to the SearchRequest class instead of having to model it piece by piece
What alternatives have you considered?
modeling the entirety of a search request in Java in Data Prepper. This does not scale well
Do you have any additional context?
Add any other context or screenshots about the feature request here.

Thanks @wbeckler.
yes that would do the job. Closing this issue

Reopening as the real need is a similar feature supported by the Elasticsearch Java Client here (https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/7.17/loading-json.html)

I really like the description used in the es docs, i agree that my teams normal workflow is using kibana to make some custom query, then directly using that json in the high level rest client. I would like for that to still be possible in the future,
as the high level rest client gets deprecated there still needs to be a way to go from json request to any endpoint in kibana to being able to send that as a request in my java app.

For bookkeeping, in what way is https://github.com/opensearch-project/opensearch-java/issues/377 different? Also would love to see a PR ;)

I wholeheartedly agree that we need this feature should be prioritized.
Our team has encountered a significant challenge that is nudging us towards considering alternative clients. The issue arises when the internal builders of SearchRequest have a bug (referenced in Issue #780), leading to the generation of an incorrect request with invalid JSON.
In that case there is nothing we can do and the api is useless for us, since the deserialiser will produce the wrong query...
We are constructing the request body using a library and would like to be able to pass the Json body directly to the "search" endpoint.
Maybe we could have something like this
SearchRequest.Builder().index("someIndex").fromJson(theJson).build()
Please, correct me if I am wrong but that does seem like a tall task, wouldn't we need to just modify the code that serialises the json prior to create a request and use the raw json passed?

Please, correct me if I am wrong but that does seem like a tall task, wouldn't we need to just modify the code that serialises the json prior to create a request and use the raw json passed?

I think so, I am not sure why the previous attempts haven't worked. Take it up @brentam!


Signature Error

I am Getting This Error with the Following VIdeo :
https://www.youtube.com/watch?v=5lLclBfKj48
[youtube] 5lLclBfKj48: Downloading webpage
[youtube] 5lLclBfKj48: Downloading video info webpage
[youtube] 5lLclBfKj48: Extracting video information
[youtube] 5lLclBfKj48: Downloading js player en_US-vflPRjCOu
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 744, in _extract_signature_function
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 796, in
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 254, in resf
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 55, in interpret_statement
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 135, in interpret_expression
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 220, in extract_object
AttributeError: 'NoneType' object has no attribute 'group'
(caused by AttributeError("'NoneType' object has no attribute 'group'",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

You are using an outdated version of youtube-dl. Read our FAQ if you have troubles updating.


Which is right font size 14 px or 16 px ?

Hi, I'm maintainer of feathericon-rails and  feathericon-sass . :octocat:
I'm trying upgrade to feathericon 0.7.0. :muscle:
I had checked the issue Change font design size from 16px to 14px , but it looks difference between
https://github.com/feathericon/feathericon/blob/v0.7.0/build/css/feathericon.css#L27
and
https://github.com/feathericon/feathericon/blob/v0.7.0/build/scss/_feathericon.scss#L31 .
The font size of _feathericon.scss is 14px, but feathericon.css is 16px.
Could you tell me which is right? :seedling:

@syokenz
Hi! thank you the report !
14px is correct, so https://github.com/feathericon/feathericon/blob/v0.7.0/build/css/feathericon.css#L27 is wrong font-size.
Bugfixed on https://github.com/feathericon/feathericon/pull/58 💪💪

@featherplain Thanks !  🚀

@featherplain  feathericon-rails and feathericon-sass v0.7.0 released ! 🎉   Thanks !


hey when i tried to uninstall my vm using winget but couldnt it says couldnt find package and i tried to get the id of it but it said "couldnt find package "

Brief description of your issue
when i try to uninstall my vm doesnt work when i do list doesnt work
Steps to reproduce
install oracle vm virtualbox and go to terminal and type
winget uninstall []Oracle VM VirtualBox
and when i do
winget list Oracle VM VirtualBox
Expected behavior
expected to uninstall the app or show me the id
Actual behavior
it says "package not found"
Environment
winget uninstall Oracle VM VirtualBox
"package not found"
winget list Oracle VM VirtualBox
"package not found"

What happens when you try winget uninstall virtualbox

lemme try

it works!!!! tysm man how about installing roblox i tried installing roblox i said
winget install roblox-player
but didnt work

it works!!!! tysm man how about installing roblox i tried installing roblox i said
winget install roblox-player
but didnt work

Try winget search roblox to see what packages are available for install, and then use the package ID to install the one you want

thank you so much man really appreciate it

also i tried doing winget search roblox but it only got the fake roblox


Restore map position and zoom level on configuration change.

Fixes #605.
The map position and zoom level are now stored in the MapContainerViewModel and are used to restore the map state after configuration changes.
@gino-m thanks very much for your help with this. LMK what you think. I'm not entirely convinced by the class name GroundCameraPosition but couldn't think of anything better.

Note that I filed #650 and #651 to fix the architectural issues which led to this issues.


[BUG] logout Cancel button is invisible

Description
The dialog box's cancel button is not visible in light mode.
Screenshots
showing in darkmode

not showing in lightmode

Additional information
No response
🥦 Browser
Microsoft Edge
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

please assign it to me.

hello Mr. @Dun-sin
can you assign me this issue, or else should i start working on it?

hello Mr. @Dun-sin
can you assign me this issue, or else should i start working on it?

That's rude I'm not a Mr, before you give someone a gender search first it's annoying or use gender neutral wordings

hello Mr. @Dun-sin
can you assign me this issue, or else should i start working on it?

That's rude I'm not a Mr, before you give someone a gender search first it's annoying or use gender neutral wordings

sorry 😣
i am not good at English.
can i call only @Dun-sin ?

please assign it to me.

Sure, thanks for wanting to contribute, Make sure you follow the rules 👉🏽here👈🏽, else your PR will not be accepted and will be closed. Good Luck


showInputBox - initial value is not returned, if user presses enter without making a change

vscode.window.showInputBox({ value: 'test' }).then(text => {
    console.log('result: ' + text);
});

If the user presses enter without typing, '' is returned. If they type anything, the correct value is returned.
OSX, 1.5.0-insider but not 1.4.

7ba701b?

Running into same issue. Version 1.5 on OS X 10.10.3. Default value is not returned if user does not type in the input box. Thank you.

Also noticed this as well when working on my extension.
Version 1.5.2
OS: Windows 10 v1607

Is this issue fixed? Does "closed" mean it's fixed? I still am experiencing the same issue, where I have to modify the default value before the input is accepted. Any thoughts?

@riteshatsencha fixed for 1.6.0 which will be released end of week.

Not sure if this needs a new bug report, or reopen this one.   When pressing enter with no input, if there is a validateInput function, if the default value is invalid, then the default value is still passed as an accepted return value.
ie:
const descStr = await vscode.window.showInputBox({
  validateInput: (value: string) => {
    if(!value || value.trim().length === 0) {
      return 'Cannot set empty description';
    }
    return null;
  }
});
if (descStr === undefined || descStr.trim().length == 0) {
  // pressing enter with no other input will still submit the empty string
  Display.showError('Cannot set empty description');
  return;
}

expected behavior would be to run the validator first and respond as per usual valid state (prevent acceptance)  (alternately, react as if cancelled)
editing the input box then deleting it again to become invalid works as expected


[e2e]: nodejs release main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5595640948
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Wed Jul 19 06:10:53 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v40.0.43
Run: https://github.com/slsa-framework/example-package/actions/runs/5605173785
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: release
Branch: v40.0.43
Date: Wed Jul 19 23:49:40 UTC 2023
Tests are passing now. Closing this issue.


Can't set my collateral and enlist my NFTs

Hello, I need your help. I want to connect my wallet to http://cnft.io after I reset it because it keep loading, whenever I try to listing my NFT it always says I need to set collateral first. I can't enlist my NFTs there too. So I tried to set collateral but it's always failed. Can you help me? And I also can't see 1 of my NFT on asset, before I reset the wallet I'm sure it still there, I already check on pool.pm too and I can see the NFT.
Here's my wallet address:
addr1q96yu5z0ngnx6mvtwg0pyr6zh7hwejjc64djp5qsre53zyw49ltkk35yaetv2a4s4lj8gm290eugx48e2ud7gl8vjrwq4pe3mk
Thankyou!

Update:
I finally success to set my collateral, now the other problem. whenever I tried to enlist my smart contract listing in cnft.io, it said "invalid collateral". I should ask help from nami or cnft.io? thanks

How did your collateral issue got resolved


[Cloudflare pages] Allow to use the same repository in multiple projects

Expected Behavior
Cloudflare pages could allow using the same repository across multiple projects
Actual Behavior
Currently the option is disabled, "in use" appears
Section that requires update
https://dash.cloudflare.com/.../pages/new
Additional information
I have in a single repository, several projects in subdirectories, each corresponding to a different site, this option would be important for me not to need to create several different repositories, each containing a single site

👋 @MarlonLuan  I'm sorry, we only take care of developers.cloudflare.com documentation requests in this repo! Please reach out to community.cloudflare.com for support.


kubevirt tests delete with cascade=orphan behaviour that it doesn't perform

What happened:
Sometimes this test fails: [test_id:838]deleting VM with cascade=false should orphan DataVolumes and VMI owned by VM..
What you expected to happen:
The assumption is that if you delete the VM with cascade=orphan, the VMI, PVC, and virt-launcher pod will remain alive, without the VM ownerref.
How to reproduce it (as minimally and precisely as possible):
Run the same steps as the test manually.
Additional context:
It looks like the code of kubevirt will attempt to re-adopt orphaned VMIs and if that wasn't enough to cause the VMI to vanish - as an orphaned object with an ownerref will be deleted - it will also explicitly delete VMIs if the VM is being deleted.
I'm not sure how this test ever works, but maybe if things happen fast enough, it may succeed. This seems to happen often enough.
Environment:

KubeVirt version (use virtctl version): main as of 12/Feb/2023
Kubernetes version (use kubectl version): v1.26.0
VM or VMI specifications: Used example/vm-alpine-datavolume.yaml after changing http: to registry: (as it was wrong)
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): Same as kubevirtci
Kernel (e.g. uname -a): Same as kubevirtci
Install tools: N/A
Others: N/A

/assign


az devops project create --name throws a false error after creating the project

When running az devops project create --name via an Azure DevOps CLI, it creates the project, but returns the following error, even though the account used for creating the project is added as a project administrator on creation:
https://dev.azure.com/ai-factory-azure/ai-factory-bootstrap/_build/results?buildId=35&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=96d51190-c773-5e24-6d77-f5dbb8477180&l=14
This is making the pipeline step fail, even though it has not actually failed.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ce3c1e46-6a16-19f1-ee37-0ac9e783e64a
Version Independent ID: 0172eade-f91a-d284-51b0-804cf9d4c327
Content: az devops project
Content Source: latest/docs-ref-autogen/devops/project.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

route to service team

Please reopen if you still need assistance, also please add details of the error, others will not have access to your project


Demos of the component does not actually use component?

The Demos page does not appear to actually use <nutrition-facts> anywhere?

I may have misunderstood the assignment, but I thought we had to create the demos before we actually implement the component so I created the demos how I normally would before I package it into a component. The demos are nearly identical to my final component and function the same way so I kept it as is.
I hope that is not a huge issue.

The demos are your component in action, so that people viewing them can get a sense of how they can use your component and what it does.

I will update the demos to use the nutrition-facts component instead (should still look and work exactly as it does right now). Sorry about that.

It wouldn't be too hard of a fix since I do actually have the component.
Should I resubmit it?
On Fri, May 6, 2022, 2:26 PM Lea Verou @.***> wrote:

The demos are your component in action, so that people viewing them can
get a sense of how they can use your component and what it does.
—
Reply to this email directly, view it on GitHub
https://github.com/yaroluchko/nutrition-facts/issues/1#issuecomment-1119877778,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUM4FX3VECJAA5ZDM65ZZLTVIVP6ZANCNFSM5VIV26MQ
.
You are receiving this because you commented.Message ID:
@.***>


(C++) Bare open braces generating incorrect HTML

Describe the issue

When there's a bare open brace on a line by itself, it gets some invalid HTML.
Which language seems to have the issue?

C++
Are you using highlight or highlightAuto?
highlight
...
Sample Code to Reproduce

hljs = require('highlight.js');
content = `
#include <iostream>
#include <conio.h>
#include <stdlib.h>
using namespace std;

int main()
{
	char name[50];
	cout << "What is your name, warrior?" << endl;
	cin.getline(name, 50);
	cout << "You better move fast, " << name << ". The goblins are attacking the city." << endl;
	cout << "\\n----------------------Press any key to continue----------------------" << endl;
	_getch();
	return 0;
}
`;
console.log(hljs.highlight('c++', content).value);

Resulting output, on highlight.js 10.1.2:
#include <iostream>
#include <conio.h>
#include <stdlib.h>
using namespace std;

int main()
{
	char name[50];
	cout << "What is your name, warrior?" << endl;
	cin.getline(name, 50);
	cout << "You better move fast, " << name << ". The goblins are attacking the city." << endl;
	cout << "\n----------------------Press any key to continue----------------------" << endl;
	_getch();
	return 0;
}

Expected behavior

Note the line which is { -- it should be just {.
Additional context

Never mind, I see what's going on - there's an extra layer of nesting on the , which is what's getting closed at the start of the new line. Where this was causing problems is I am splitting the output string into an array based on newlines, so that I can add some per-line markup for formatting purposes. I'll look for an alternate approach to this.

In this case it actually is affecting my visual output, since I'm using CSS counters to number lines and in a context where I don't have complete control over the input, and the only way I could figure out to do that consistently was with some annoying hacks that involve display:table and the like. It was working great until I ran into this spot where highlight.js was splitting a token across multiple lines. :)

What's the rationale for having a multi-level nesting on some token types? For example, in the above, having function wrapping the keyword, title, and params tokens. This seems unnecessary, and I can't think of any context in which I'd want to have different highlight rules for a keyword when it's inside a function declaration vs. inside a code statement, for example.
I very much want to be able to split the highlight.js output line-by-line, and having tokens nest when some can span multiple lines makes this quite difficult without doing an extra layer of HTML parsing and manipulation.
Thanks!

In this case it actually is affecting my visual output

Your output, not ours. ;-)  The easiest way to add lines (if you don't need to wrap) is just with a second block you position right next to the first and put the line numbers there.
What's the rationale for having a multi-level nesting on some token types? For example, in the above, having function wrapping the keyword, title, and params tokens. This seems unnecessary, and I can't think of any context in which I'd want to have different highlight rules for a keyword when it's inside a function declaration vs. inside a code statement, for example.
It's just the way our parser works.  Some themes might want to highlight the whole function header differently, etc.

I very much want to be able to split the highlight.js output line-by-line, and having tokens nest when some can span multiple lines makes this quite difficult without doing an extra layer of HTML parsing and manipulation.

Lots of things can span multiple lines (comments, strings, etc) so this is a problem you have to deal with in any case.  You may want to look at the tree representation of the data and use that instead to render your own HTML.

Ah, multi-line comments are a fair point that I hadn't considered. That makes sense.

The easiest way to add lines (if you don't need to wrap) is just with a second block you position right next to the first and put the line numbers there.

Yeah, this is probably what I'll do, although it would be nice to have wrapping work correctly. I was hoping to make my solution as pure-CSS as possible but that's something for another day.


Improve ServiceAccount Signing Key Rotation Procedure

How to categorize this PR?

/area security usability
/kind enhancement
What this PR does / why we need it:
The ServiceAccount signing key rotation procedure is not working well for clusters with lots of ServiceAccounts when the user intervenes during the rotation procedure by creating/deleting new/old ServiceAccount  secrets. Today, the code implicitly assumes that the first secret in the .secrets[] list in ServiceAccounts is the one that was created by gardenlet in the Preparing phase, however, this assumption is not always correct.
This PR does the following:

Introduce new lastInitiationFinishedTime and lastCompletionTriggeredTime fields in the credentials status APIs so that we can better track when the Preparing phase was finished and when the Completing phase was triggered.
The fields are only present when a credentials rotation is ongoing (i.e., when the phase is Prepared or Completing).
The fields can also be used to present more accurate warnings to the end-user.
With the information of these fields, the deletion of old ServiceAccount secrets can check when a related Secret was created and only clean it up when it was created before the first phase finished. All secrets created after this time were already signed with the new key and do not need to be cleaned up. This way, gardenlet no longer interferes with the custom operations of end-users.

Release note:

The `ServiceAccount` signing key rotation procedure has been improved and should work better for clusters with lots of `ServiceAccount`s or intermittent creations/deletions of new/old `ServiceAccount` secrets.

/test pull-gardener-integration

/assign

/assign

/lgtm needs second opinion

/test pull-gardener-e2e-kind-operator

/approve


Bad param meta data: VT_AIRSPD_RULE is UINT but min is set with float value

Latest QGC complaining about bad metadata:
PX4ParameterMetaDataLog: Invalid min value, name: "VT_AIRSPD_RULE"  type: 5  min: "0.0"  error: "Invalid number"

Thanks for reporting Don, fixed in https://github.com/PX4/Firmware/pull/10897.

FYI @RomanBapst


Added Kindergarten Garden

See: https://github.com/exercism/x-common/blob/master/kindergarten-garden.md

Looks good


What is the limit on HCS message length?

Description
At this page we see a highlighted note that specifies "HCS message size: 1024 bytes".  Where at this page - the actual API reference - we see "Max size of the Transaction (including signatures) is 6kB".
And we don't know what size the signatures are, but unless the signatures add up to 5kB that makes it sound like you can have bigger messages.
The true limit, whatever it is, should be specified in both places.  Additional, in the API reference page (the second one) it would be nice to have a note mentioning what the typical size of the transaction with signature is.
Steps to reproduce
Visual inspection of above two linked pages will suffice.
Additional context
No response
Hedera network
other
Version
N/A
Operating system
None

Confirmed max HCS  message size is 1024 bytes (1 kb). In comparison, the max size of a transaction (including messages and signatures) is 6 kb.
There isn't a fixed signature size, as it varies by transaction.
Updated docs and resolved in b19b85a


Proposal: Support better query for pools

Background
We currently only have a single query for querying all Pools, namely osmosis/gamm/v1beta1/pools.
But with different pools existing under different circumstances, and with over 500+ pools existing in state as of right now, there are situations where a person would like to query pools with a certain filter, or a whitelist.
I would like to propose two different ways of supporting better queries for pools.
Suggested Design

The first way of doing this can be done via creating a pool query that accepts different filter as its request, something like this

message QueryPoolWithFilterRequest {
       int64 minLiquidity = 1;
       string poolType = 2;
      int64 minPoolAssetNum = 3;
      ...
}

and then whoever's requesting can use the field that they want to use as a filter, leaving other fields with null value.  The response would be returned via iterating over pool state, only returning the pools that goes under the filtered request.

The second way of doing this is a quite untraditional way of supporting queries, which is done via using app.toml. We create a field in app.toml where the node operator can have their own list of whitelist pool ids. Then we have a query, say QueryPoolsUnsafe, which would non-deterministically only return the state of the pools that are whitelisted in app.toml. Using the QueryPoolsUnsafe query, who ever's querying does not have to go through the process of having to query all states of pools first, and the filtering them within the client side.

Open for discussions on the pros and cons of these ways, and also if we even do need these queries!

Hello @mattverse! This issue seems interesting, I would like to work on it. May I? (I am more of a fan of the first suggested design)

Yes please!


Model attribute updatedAt not updating with autoUpdatedAt: 'updated_at'

Sails version: 0.12.3
Node version: 5.7.0
NPM version: 3.6.0
Operating system: OSX 10.11.5

Expected Behavior:
After successfully updating a record using .update(), the record's updated_at field should auto-update to the current time.
Note: I changed the autoUpdatedAt setting (also mentioned here) using autoUpdatedAt: 'updated_at' in config.models so the field is titled updated_at instead of updatedAt. It should still have the same functionality.
Actual Behavior:
The model successfully updates, but it does not update the updated_at field.
Steps to Reproduce:

sails new
Remove grunt file
Add the following lines to sails.config.models:

    autoUpdatedAt: 'updated_at',
    migrate: 'alter'

sails generate model test
sails generate controller test
Add the following lines to TestController.js:

module.exports = {
	test: function(req, res){
		Test.create()
		.then(function(created){
			sails.log('created');
			sails.log(created);

			//update
			Test.update(created, {})
			.then(function(updated){
				sails.log('updated');
				sails.log(updated[0]);

				Test.findOne(updated)
				.then(function(found){
					sails.log('found');
					sails.log(found);

					res.end();
				});
			});
		});
	}
};

sails lift
Request http://localhost:1337/test/test
Sails Log:

debug: created
debug: { createdAt: '2016-08-25T21:35:46.679Z',
  updated_at: '2016-08-25T21:35:46.679Z',
  id: 1 }
debug: updated
debug: { createdAt: '2016-08-25T21:35:46.679Z',
  updated_at: '2016-08-25T21:35:46.679Z',
  id: 1,
  updatedAt: '2016-08-25T21:35:46.698Z' }
debug: found
debug: { createdAt: '2016-08-25T21:35:46.679Z',
  updated_at: '2016-08-25T21:35:46.679Z',
  id: 1,
  updatedAt: '2016-08-25T21:35:46.698Z' }

So it looks like Sails is still setting the updatedAt field of the model on update instead of looking at the field name from sails.config.models. This will then not save to a SQL database because the updatedAt column does not exist.
Link to StackOverflow Question

This also happens on sails 0.12.4, node 6.5.0, npm 3.10.3, Operating system centos 7, kernel: 3.10.0-327.28.3.el7.x86_64

Confirmed.  Looks like a bug to me.  @particlebanana?

I did some research, this bug is in waterline v0.11.0 and was fixed in v0.11.3. So just updating the version to 0.11.3 will fix this.
Note: waterline is already on version v0.12.2, so maybe look into that?

So to clarify, the bug fix is in package.json to update and make the line "waterline": "~0.12.2"? Or at least 0.11.3?
On a personal level, I can fix this now by manually adding "waterline": "~0.12.2" to my package because npm uses flat structure, correct?

I would not tempt a major version upgrade without testing everything. Leave a change like that to the core team. But you coould infact manually change that line to 0.11.3.
Node js does use flat structure nowadays but if you add it in your package.json my guess is it would just install both versions or you get an error. It has to change in sails' package.json

Right, understood. It would definitely need to be tested, so until then I wanted to make sure an individual change would work. I'll update it in sails' package.json to 0.11.3 then. Thank you for researching it and for your helpful comments! :)

After updating the sails package to include the updated waterline, I ran the same code as above, and it still doesn't work.
I got the following code output and error:
debug: created
debug: { createdAt: '2016-09-19T03:05:58.554Z',
  updated_at: '2016-09-19T03:05:58.554Z',
  id: 19 }
Warning: a promise was created in a handler but was not returned from it
    at Deferred.toPromise (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/deferred.js:494:61)
    at Deferred.then (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/deferred.js:505:15)
    at TestProject/api/controllers/TestController.js:17:5
    at wrapper (TestProject/node_modules/sails-hook-orm/node_modules/lodash/index.js:3592:19)
    at applyInOriginalCtx (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/normalize.js:421:80)
    at wrappedCallback (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/normalize.js:324:18)
    at callback.success (TestProject/node_modules/sails-hook-orm/node_modules/switchback/lib/normalize.js:33:31)
    at _switch (TestProject/node_modules/sails-hook-orm/node_modules/switchback/lib/factory.js:58:28)
    at TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/dql/create.js:248:9
    at TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:52:16
    at TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:269:32
    at TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:44:16
    at null.<anonymous> (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/schema.js:152:44)
    at fn (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/callbacksRunner.js:60:10)
    at TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:181:20
    at iterate (TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:262:13)
    at Object.async.forEachOfSeries.async.eachOfSeries (TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:281:9)
    at Object.async.forEachSeries.async.eachSeries (TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:214:22)
    at Object.runner.afterCreate (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/callbacksRunner.js:63:9)
    at after (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/dql/create.js:243:17)
    at TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/dql/create.js:230:68
    at wrapper (TestProject/node_modules/sails-hook-orm/node_modules/lodash/index.js:3592:19)
    at applyInOriginalCtx (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/normalize.js:421:80)
    at wrappedCallback (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/normalize.js:324:18)
    at callback.success (TestProject/node_modules/sails-hook-orm/node_modules/switchback/lib/normalize.js:33:31)
From previous event:
    at Deferred.then (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/deferred.js:505:27)
    at Object.module.exports.test (TestProject/api/controllers/TestController.js:11:4)
    at wrapper (TestProject/node_modules/sails/node_modules/lodash/index.js:3095:19)
    at routeTargetFnWrapper (TestProject/node_modules/sails/lib/router/bind.js:181:5)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:164:37)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:138:11)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:135:11)
    at pass (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:145:5)
    at nextRoute (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:100:7)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:167:11)
    at alwaysAllow (TestProject/node_modules/sails/lib/hooks/policies/index.js:224:11)
    at routeTargetFnWrapper (TestProject/node_modules/sails/lib/router/bind.js:181:5)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:164:37)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:138:11)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:135:11)
    at pass (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:145:5)
    at nextRoute (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:100:7)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:167:11)
    at module.exports (TestProject/node_modules/sails/lib/hooks/cors/clear-headers.js:14:3)
    at routeTargetFnWrapper (TestProject/node_modules/sails/lib/router/bind.js:181:5)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:164:37)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:138:11)
    at pass (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:145:5)
    at nextRoute (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:100:7)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:167:11)
    at sails.router.bind._middlewareType (TestProject/node_modules/sails/lib/hooks/csrf/index.js:148:11)
    at routeTargetFnWrapper (TestProject/node_modules/sails/lib/router/bind.js:181:5)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:164:37)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:138:11)
    at pass (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:145:5)
    at nextRoute (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:100:7)

debug: updated
debug: { createdAt: '2016-09-19T03:05:58.554Z',
  updated_at: '2016-09-19T03:05:58.554Z',
  id: 19,
  updatedAt: '2016-09-19T03:05:58.577Z' }
Warning: a promise was created in a handler but was not returned from it
    at Deferred.toPromise (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/deferred.js:494:61)
    at Deferred.then (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/deferred.js:505:15)
    at TestProject/api/controllers/TestController.js:22:6
    at wrapper (TestProject/node_modules/sails-hook-orm/node_modules/lodash/index.js:3592:19)
    at applyInOriginalCtx (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/normalize.js:421:80)
    at wrappedCallback (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/normalize.js:324:18)
    at callback.success (TestProject/node_modules/sails-hook-orm/node_modules/switchback/lib/normalize.js:33:31)
    at _switch (TestProject/node_modules/sails-hook-orm/node_modules/switchback/lib/factory.js:58:28)
    at TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/dql/update.js:234:9
    at TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:52:16
    at Object.async.forEachOf.async.eachOf (TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:236:30)
    at Object.async.forEach.async.each (TestProject/node_modules/sails-hook-orm/node_modules/async/lib/async.js:209:22)
    at TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/dql/update.js:225:13
    at updatedNestedAssociations (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/dql/update.js:262:12)
    at TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/dql/update.js:222:31
    at wrapper (TestProject/node_modules/sails-hook-orm/node_modules/lodash/index.js:3592:19)
    at applyInOriginalCtx (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/normalize.js:421:80)
    at wrappedCallback (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/utils/normalize.js:324:18)
    at callback.success (TestProject/node_modules/sails-hook-orm/node_modules/switchback/lib/normalize.js:33:31)
    at _switch (TestProject/node_modules/sails-hook-orm/node_modules/switchback/lib/factory.js:58:28)
    at afterwards (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/adapter/dql.js:244:14)
From previous event:
    at Deferred.then (TestProject/node_modules/sails-hook-orm/node_modules/waterline/lib/waterline/query/deferred.js:505:27)
    at Object.module.exports.test (TestProject/api/controllers/TestController.js:11:4)
    at wrapper (TestProject/node_modules/sails/node_modules/lodash/index.js:3095:19)
    at routeTargetFnWrapper (TestProject/node_modules/sails/lib/router/bind.js:181:5)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:164:37)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:138:11)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:135:11)
    at pass (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:145:5)
    at nextRoute (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:100:7)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:167:11)
    at alwaysAllow (TestProject/node_modules/sails/lib/hooks/policies/index.js:224:11)
    at routeTargetFnWrapper (TestProject/node_modules/sails/lib/router/bind.js:181:5)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:164:37)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:138:11)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:135:11)
    at pass (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:145:5)
    at nextRoute (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:100:7)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:167:11)
    at module.exports (TestProject/node_modules/sails/lib/hooks/cors/clear-headers.js:14:3)
    at routeTargetFnWrapper (TestProject/node_modules/sails/lib/router/bind.js:181:5)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:164:37)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:138:11)
    at pass (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:145:5)
    at nextRoute (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:100:7)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:167:11)
    at sails.router.bind._middlewareType (TestProject/node_modules/sails/lib/hooks/csrf/index.js:148:11)
    at routeTargetFnWrapper (TestProject/node_modules/sails/lib/router/bind.js:181:5)
    at callbacks (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:164:37)
    at param (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:138:11)
    at pass (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:145:5)
    at nextRoute (TestProject/node_modules/sails/node_modules/express/lib/router/index.js:100:7)

debug: found
debug: { createdAt: '2016-09-19T03:05:58.554Z',
  updated_at: '2016-09-19T03:05:58.554Z',
  id: 19,
  updatedAt: '2016-09-19T03:05:58.577Z' }

@shanemileham Apologies for the slow reply.  (@particlebanana and I have been mainly focused on the adapters/drivers on the Waterline front as we get ready for Sails v1.0)  Looks like we just need to npm publish, but I want to run through the commits and make sure everything is solid first.  We'll look at that this afternoon.

@shanemileham Published<EMAIL_ADDRESS>which should have this patched.

Just tested it (and fixed my promise antipatterns), and it works! Thank you @mikermcneil and @particlebanana for your help. Looking forward to Sails v1.0! 😄

@shanemileham you're welcome!  Us too :)

I noticed that the current version of Sails still depends on the buggy waterline version. Will this be updated soon? Or do I need to manually change the dependency on Heroku after it builds?


Build failure: firefox-unwrapped-111.0.1

Steps To Reproduce
Steps to reproduce the behavior:

Build firefox-unwrapped from master branch

nix build 'github:NixOS/nixpkgs#firefox-unwrapped'

Build log
error: hash mismatch in fixed-output derivation '/nix/store/2yljlnmgw23cxlbiqs9g7vahxl1iaqs3-firefox-111.0.1.source.tar.xz.drv':
         specified: sha512-59JIuEXLUk78KIGOCgytBrpaysMCGYhhkbcCthMUOI0QoWkMbXBLCnDSvCxLHwTtAjUNy53OnFZQPSrzuu/k0w==
            got:    sha512-sWyTmaGcsd4thloCPVT75xwjo2PqTTbNWPQfZPetBLwbnYqESJQ0F1FuFzN+DuKv03DCmnK1GwlHFh9P+raTXw==
error: 1 dependencies of derivation '/nix/store/fa311n83vy5h9chsnv6x43j2691l1wqx-firefox-unwrapped-111.0.1.drv' failed to build

Notify maintainers
@lovesegfault
@mweinelt
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.97, NixOS, 22.11 (Raccoon), 22.11.20230307.b511e78`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

The hash listed in https://archive.mozilla.org/pub/firefox/releases/111.0.1/SHA512SUMS has apparently changed at 16:36 UTC today. The tarball was already available earlier than that, so the release apparently changed later that day.
b16c9399a19cb1de2d865a023d54fbe71c23a363ea4d36cd58f41f64f7ad04bc1b9d8a8448943417516e17337e0ee2afd370c29a72b51b0947161f4ffab6935f  source/firefox-111.0.1.source.tar.xz

That would also line up with the hash you are seeing.
❯ nix hash to-sri --type sha512 b16c9399a19cb1de2d865a023d54fbe71c23a363ea4d36cd58f41f64f7ad04bc1b9d8a8448943417516e17337e0ee2afd370c29a72b51b0947161f4ffab6935f
sha512-sWyTmaGcsd4thloCPVT75xwjo2PqTTbNWPQfZPetBLwbnYqESJQ0F1FuFzN+DuKv03DCmnK1GwlHFh9P+raTXw==

In fact, we have the same hash as e.g. Alpine.
Will investigate the change shortly, then update the hash.


Unittest enhanced html config: Failing test messages aren't very readable

This issue was originally filed by<EMAIL_ADDRESS>
I made a small change to increase the readability of the failing test messages in the html_enhanced_configuration. I've attached a couple of screenshots so you can get a quick idea of what this change does :)
Here's my submitted code review url (hopefully I did it properly).
https://codereview.chromium.org/710813002

Attachments:
before.png (39.16 KB)
after.png (40.34 KB)

This issue has been moved to dart-lang/test#262.


Use [Property] Attribute

Use [Property] Attribute (PropertyAttribute.cs) for overriding a property's getter and setter methods instead of having backing fields and using the ObservableObject::Set<T>(ref T t, T value) function.
Before:
private string _username;
public string Username
{
    get => _username;
    set => Set(ref _username, value);
}

After:
[Property]
public string Username { get; set; }

Pro:

Much cleaner code
More maintainable code (less backing field or get & set pollution)

Con:

Difficult to implement
Probably having to use Fody (PropertyChanged Implementation)

Does not really work in .NET, because this approach requires either an assembly weaver (like Fody) or a macro (which has limited functionality in .NET)