Periodic update sensor remaining_requests

I have an automation running for charging depending on solar power, which consumps quite a lot of requests at some days. Sometimes 15 requests gone to 0.
In that cases I „reset“ the request by turning ignition on and off. But the integration seems not to update that sensor periodically and my automations are stuck, as I use the remaining request as a condition. For now I have to force an update via switch, which consumps one request for „nothing“.
Is the limitation to 15 request by your integration or is this by skodas service?
Could you either update that sensor as all the others?
Maybe you could force an update without consumping a request?

I have an automation running for charging depending on solar power, which consumps quite a lot of requests at some days. Sometimes 15 requests gone to 0.
In that cases I „reset“ the request by turning ignition on and off. But the integration seems not to update that sensor periodically and my automations are stuck, as I use the remaining request as a condition. For now I have to force an update via switch, which consumps one request for „nothing“.
Is the limitation to 15 request by your integration or is this by skodas service?
Could you either update that sensor as all the others?
Maybe you could force an update without consumping a request?

The limit is set by VW Group om server level, nothing I can get around in the integration I'm afraid.
I only know of one way to get the number of requests and that is by performing a request. The native app does some trickery to know this but I have not been able to regerar engineer it.
Since the number gets reset every time the car has been driven the integration cheats by resetting the number to 15 when it detects the car is moving. This is somewhat of a hack since it's a bit of hit and miss as you have noticed. If the car starts and stops between two polling cycles then the integration won't pick up in it and won't reset the number of requests.

Thanks for explaination.
How do you detect that the car is moving? Turning ignition on and off seems to reset the requests on server side and last time I would bet the integration shows 15 requests remaining. Today I switches ignition on and offvery fast (within 20 seconds) which was maybe between two polling cycles.
Do you say that ignition on and off over two polling cycles will reset the requests due to the hack you‘ve mentioned? That would be a workaround for me.

If the app triggers in the same way, only faster. Then keeping the ignition on for at least 1 polling cycle (what you defined in configuration.yaml).
I will see if there's another way to implement this as well. It probably involves keeping track of timestamp of last counter reset. Have you noticed of parking time timestamp is updated when you switch ignition on and off?

Parkingtime seems to be not supported by my Superb iV.
Whatever it is not in the entity list.

Parkingtime seems to be not supported by my Superb iV.
Whatever it is not in the entity list.

Strange, it should show up for all cars with device tracker

Does this depend on privacy settings in the car.
I remember that i switched off some services.

After changing privacy settings in the car the missing entities like „parking_time“ appeared.
And yes parking_time has changes on ignition on and off.
How do you detect movement for now?
Yesterday (after change of privacy settings) the reqests raise to 15 immediately with the next poll after ignition. Maybe your hack didn‘t work for me due to my privacy settings. And it does now?

Yes most probably the privacy settings were hindering the reset.
The car still needs to be on over a polling cycle for the current implementation to detect it.
I might rewrite it to reset the number on parking time updated, that should be more reliable.

Sounds fine.
Maybe the privacy setting are worth a hint in the readme, as „parking position“ has to be enabled for reliable reset of request.
I will get the updates version on hacs.
Thanks.

Information regarding privacy settings has been added to README


ERROR: Plugin with id 'com.android.library' not found.

Current behavior
I'm not able to build android-exoplayer project
Reproduction steps
Clone react-native-video project, then open android-exoplayer folder in Android Studio, sync project with gradle
Expected behavior
Project should be synced
My problem is that I would like to use this library, but I need to add some additional code to android exoplayer. I wan't to change view etc. In this case I wanted to open android-exoplayer and change it a little, but at the begining I got error from issue title.
I searched for solution and I found that adding this:
buildscript {
    repositories {
        jcenter()
        google()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.3'
    }
}

May solve problem.
I also had to update gradle distribution to:
distributionUrl=https://services.gradle.org/distributions/gradle-5.4.1-all.zip
Right now I'm getting those errors:
ERROR: Unable to resolve dependency for ':@debug/compileClasspath': Cannot resolve external dependency com.facebook.react:react-native:+ because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debug/compileClasspath': Cannot resolve external dependency com.google.android.exoplayer:exoplayer:2.10.5 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debug/compileClasspath': Cannot resolve external dependency androidx.annotation:annotation:1.1.0 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debug/compileClasspath': Cannot resolve external dependency androidx.core:core:1.1.0 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debug/compileClasspath': Cannot resolve external dependency androidx.media:media:1.1.0 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debug/compileClasspath': Cannot resolve external dependency com.google.android.exoplayer:extension-okhttp:2.10.5 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debug/compileClasspath': Cannot resolve external dependency com.squareup.okhttp3:okhttp:3.14.3 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugAndroidTest/compileClasspath': Cannot resolve external dependency com.facebook.react:react-native:+ because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugAndroidTest/compileClasspath': Cannot resolve external dependency com.google.android.exoplayer:exoplayer:2.10.5 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugAndroidTest/compileClasspath': Cannot resolve external dependency androidx.annotation:annotation:1.1.0 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugAndroidTest/compileClasspath': Cannot resolve external dependency androidx.core:core:1.1.0 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugAndroidTest/compileClasspath': Cannot resolve external dependency androidx.media:media:1.1.0 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugAndroidTest/compileClasspath': Cannot resolve external dependency com.google.android.exoplayer:extension-okhttp:2.10.5 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugAndroidTest/compileClasspath': Cannot resolve external dependency com.squareup.okhttp3:okhttp:3.14.3 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugUnitTest/compileClasspath': Cannot resolve external dependency com.facebook.react:react-native:+ because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugUnitTest/compileClasspath': Cannot resolve external dependency com.google.android.exoplayer:exoplayer:2.10.5 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugUnitTest/compileClasspath': Cannot resolve external dependency androidx.annotation:annotation:1.1.0 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugUnitTest/compileClasspath': Cannot resolve external dependency androidx.core:core:1.1.0 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugUnitTest/compileClasspath': Cannot resolve external dependency androidx.media:media:1.1.0 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugUnitTest/compileClasspath': Cannot resolve external dependency com.google.android.exoplayer:extension-okhttp:2.10.5 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

ERROR: Unable to resolve dependency for ':@debugUnitTest/compileClasspath': Cannot resolve external dependency com.squareup.okhttp3:okhttp:3.14.3 because no repositories are defined.
Show Details
Affected Modules: android-exoplayer

My whole build.gradle file looks like this:
apply plugin: 'com.android.library'

def safeExtGet(prop, fallback) {
    rootProject.ext.has(prop) ? rootProject.ext.get(prop) : fallback
}

android {
    compileSdkVersion safeExtGet('compileSdkVersion', 28)
    buildToolsVersion safeExtGet('buildToolsVersion', '28.0.3')

    compileOptions {
        targetCompatibility JavaVersion.VERSION_1_8
        sourceCompatibility JavaVersion.VERSION_1_8
    }

    defaultConfig {
        minSdkVersion safeExtGet('minSdkVersion', 16)
        targetSdkVersion safeExtGet('targetSdkVersion', 28)
        versionCode 1
        versionName "1.0"
    }
}

dependencies {
    implementation "com.facebook.react:react-native:${safeExtGet('reactNativeVersion', '+')}"
    implementation('com.google.android.exoplayer:exoplayer:2.10.5') {
        exclude group: 'com.android.support'
    }

    // All support libs must use the same version
    implementation "androidx.annotation:annotation:1.1.0"
    implementation "androidx.core:core:1.1.0"
    implementation "androidx.media:media:1.1.0"

    implementation('com.google.android.exoplayer:extension-okhttp:2.10.5') {
        exclude group: 'com.squareup.okhttp3', module: 'okhttp'
    }
    implementation 'com.squareup.okhttp3:okhttp:3.14.3'

}

buildscript {
    repositories {
        jcenter()
        google()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.3'
    }
}

Does anyone know how can I fix it? Thanks!

hi @kosmateus, in your root build.gradle file, you may want to confirm the right maven repositories have been added. For example:
allprojects {
    repositories {
        google()
        jcenter()
    }
}


Update to 1.21.3?

Any Prevision to update mod for the 1.21.3 version, since it says its incompatible ?

@enjarai

Mojang has massively rewritten both entity and armor rendering in 1.21.3. This means that updating this mod will require essentially a full rewrite of the rendering internals. This will most likely take a while.

Thank you so much for the update. I can't begin to imagine how long that will take or the scope of the changes.


DISCSUBTITLE fields interpreted as Latin1 when UTF-8?

I labled a disc within a collection as "Debussy: Images, Prélude à l'après-midi d'un faune".  It's stored in the LMS database in UTF-8 characters.
When displayed on the album listing, it comes out as "Debussy: Images, PrÃ©lude Ã  l'aprÃ¨s-midi d'un faune" which is what you would  get if you interpreted the bytes as Latin-1 (iec 8859-1).

Thanks, I figured since it was correct in the DB, was probably a skin issue.
Any thoughts on how it might be getting sent wrong?
Will file an issue on LMS, referencing this issue.

Fixed as LMS: https://github.com/LMS-Community/slimserver/pull/1221
Thanks....


[BUG] Wuxiaworld.site

Describe the bug
 When someone attempts to download novels on the bot from
wuxiaworld.site   they would get this error
java.net.SocketTimeoutException: Read timed out
This is the full log:
java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(Unknown Source)
        at java.net.SocketInputStream.read(Unknown Source)
        at java.net.SocketInputStream.read(Unknown Source)
        at sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
        at sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
        at sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(Unknown Source)
        at sun.security.ssl.SSLSocketImpl.readApplicationRecord(Unknown Source)
        at sun.security.ssl.SSLSocketImpl.access$300(Unknown Source)
        at sun.security.ssl.SSLSocketImpl$AppInputStream.read(Unknown Source)
        at okio.Okio$2.read(Okio.java:140)
        at okio.AsyncTimeout$2.read(AsyncTimeout.java:237)
        at okio.RealBufferedSource.indexOf(RealBufferedSource.java:355)
        at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:227)
        at okhttp3.internal.http1.Http1Codec.readHeaderLine(Http1Codec.java:215)
        at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189)
        at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:88)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
        at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
        at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
        at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
        at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:126)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
        at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
        at okhttp3.RealCall$AsyncCall.execute(RealCall.java:147)
        at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Steps to reproduce

Expected behavior

Screenshots

Platform

Logs

Additional context

Does this happen right at the start when the grabber is "checking" or midway during the download (eg. chapter 50). It works fine for me, I only tried 10 chapters through, so I would suggest trying again later or use a longer wait time since Read time out means that the server was too slow to provide an answer.

somtimes it happens right away somtimes midway, what if the person is a VIP?

It's a server (wuxiaworld.site) issue. Being a vip won't matter at all. Their server is too slow and can't keep up. I'll take a look why it stop grabbing through, normally it should skip those and retry them at the end.

thank you very much!

what happens if a person download a manga using a telegram bot?

Try it out. It might work, if you have images download enabled. I'm just not sure which host also have manga with matching page selectors.

It is working now so I will close this issue and thank you!


Memory leak on EventEmitter ?

Im getting sometimes lot of this errors. I don't usually get them but when i do i get like 10 in the same request. Any idea why this happens?
I'm using nunjucks library which depends on chokidar.
(node) warning: possible EventEmitter memory leak detected. 11 change listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at StatWatcher.addListener (events.js:236:17)
    at Object.fs.watchFile (fs.js:1339:8)
    at EventEmitter.FSWatcher._watch (/home/developer/node1.local/node_modules/koajs-nunjucks/node_modules/nunjucks/node_modules/chokidar/index.js:251:8)
    at EventEmitter.FSWatcher._handleDir (/home/developer/node1.local/node_modules/koajs-nunjucks/node_modules/nunjucks/node_modules/chokidar/index.js:351:8)
    at /home/developer/node1.local/node_modules/koajs-nunjucks/node_modules/nunjucks/node_modules/chokidar/index.js:385:38
    at FSReqWrap.oncomplete (fs.js:78:15)

Seems like invalid usage inside nunjucks. I'll comment there.

I get same errors with gulp-watch which depends on chokidar too

set usePolling and persistent options is fixed to me
chokidar.watch(path, {
    usePolling: true,
    persistent: true
});


Installed extensions filter for the extension center

fix #414
Added a filter icon and filter logic

@saai-syvendra thanks for the PR! happy hacktoberfest
Changes are made to fetch the extensions again when applying filter, because otherwise filter will be applied on outdated data.
Test case: Install an extension, and then apply filter. In the previous implementation, newly extension won't show up.


Update zksync-env.sh

Changes made:
1.Improved formatting and indentation for better readability.
2. Enclosed variable expansions in double quotes to prevent word splitting and globbing issues.
3. Replaced some subshell executions ($(...)) with command substitution (cmd || true) for better error handling.
4. Reorganized the script structure for clarity and easier maintenance.
5. Added missing double quotes around file paths to handle paths with spaces or special characters properly.
6. Simplified some conditional statements and error handling.
7. Improved comments for clarity.

Nice


SyntaxError: f-string: unmatched '('

D:\Github\Merge-image>python cli.py merge -folder "Merged\CH (1)" -fit
Traceback (most recent call last):
File "D:\Github\Merge-image\cli.py", line 86, in
from utils.image_merger import merge_folder
File "D:\Github\Merge-image\utils\image_merger.py", line 42
copy2(list_to_merge[0].filename, f'{path_to_destination}/{index+1:03d}.{list_to_merge[0].filename.split('.')[-1]}')
^
SyntaxError: f-string: unmatched '('

Regarding this, as of python 3.12.0, f-strings support nested apostrophe characters. so please update your python to 3.12.x or higher


Menu not showing when added programatically

Yesterday I implemented the PagingMenuController by copying the storyboard and working from your example, this worked perfectly fine. I'd rather do it programatically though, but the menu is not showing up now. Is there something I am missing?
my didFinishLaunchingWithOptions looks somethings like this
self.window = UIWindow(frame: UIScreen.mainScreen().bounds)
let containerViewController = ContainerViewController()
let navigationContoller = UINavigationController(rootViewController: containerViewController)
self.window!.rootViewController = navigationContoller
self.window!.makeKeyAndVisible()

Then later I configure the menu the same way as in the readMe
let viewController = UIViewController()
viewController.title = "First title"

let viewController2 = UIViewController()
viewController2.title = "Second title"

let viewControllers = [viewController, viewController2]

let options = PagingMenuOptions()
options.menuItemMargin = 5
options.menuHeight = 60
options.menuDisplayMode = PagingMenuOptions.MenuDisplayMode.SegmentedControl
let pagingMenuController = PagingMenuController(viewControllers: viewControllers, options: options)

self.addChildViewController(pagingMenuController)
self.view.addSubview(pagingMenuController.view)
pagingMenuController.didMoveToParentViewController(self)

The menu bar doesn't show but I can transition between VC's. What am I doing wrong?

Well, I created a new project and copied the codes shown above. However it works fine for me.
Could you send me some screenshots?

I guess I got your point. I've just fixed it and updated to 0.4.2 version.
So please use 0.4.2 and if there is still a bug, comment here again.
For your information, I added PagingMenuControllerDemo2 target implemented programmatically. Hope it would be helpful for you.

Sorry for the late response, and thanks a lot will have a look right now.

:+1:
Don't forget run pod install in terminal if you want to run example project.

Thank works. Thanks 💪🏼

Awesome :smile:


Deprecate fromEventWhere

I haven't thought of a reason not to deprecate it.  We could release this deprecation in 0.13 and remove for either 0.14, or 1.0.  If we think of a reason to keep it between now and then, we can reinstate it.
See #86

The docs need some attention too.  Seems like the two sections, fromEvent and fromEventWhere could be combined easily.  I might be able to tackle that tonight.

Good call.  That'd be awesome if you combine them!

Docs updated, and added a unit test to ensure synchronous propagation, which was the premise of deprecating fromEventWhere in the first place :)

Looks like a perf test snick in there.  The rest is :+1:! :)

Oh man, good catch! Thanks!

Removed the accidentally added perf test and squashed commits.


Weird URL added to unc file path

Hello,
We are using this library to download a file from a web API and save a file in a network location
It works fine when we test, using postman, on a development machine, but when we run the code in Azure PaaS Application Service Environment it adds a weird path in front of legitimate path "D:\ere\erre \[server name]\folder\file.pdf"
Any idea why it is doing it ?
Thank you

No idea.  Sorry.   That's a bit out of scope for this library.

why out of scope, because i am running it from Azure PaaS?

This library doesn't do any file I/O operations itself.  The only thing it does is provide a managed wrapper for the LogonUser Win32 API to get a token handle for a specific username and password and then passes that handle to the WindowsIdentity.Impoeronate or WindowsIdentity.RunImpersonated  .NET methods.
How file I/O works within any given environment, whether single PC, local workgroup, homegroup, domain, cloud PaaS, VM, etc. is not part of this library, but part of other code your application might be calling.
Even if for some reason file I/O operations are manipulating the path when running under impersonation within some environment, that's an issue with that environment - not this library.

That makes sense. Thank you for the explanation
On Wed, Apr 28, 2021 at 7:56 PM Matt Johnson-Pint @.***>
wrote:

This library doesn't do any file I/O operations itself. The only thing it
does is provide a managed wrapper for the LogonUser Win32 API to get a
token handle for a specific username and password and then passes that
handle to the WindowsIdentity.Impoeronate or
WindowsIdentity.RunImpersonated .NET methods.
How file I/O works within any given environment, whether single PC, local
workgroup, homegroup, domain, cloud PaaS, VM, etc. is not part of this
library, but part of other code your application might be calling.
Even if for some reason file I/O operations are manipulating the path when
running under impersonation within some environment, that's an issue with
that environment - not this library.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mattjohnsonpint/SimpleImpersonation/issues/59#issuecomment-828875441,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADB75IXKKJXVCYRQBJJBE2TTLCVD7ANCNFSM43YCLEEA
.

No problem, and Good luck!


Cross-compilation is broken

libbpf-sys cannot be cross-compiled.
default-features
There's no way to specify include path for cross-compilation. I opened #93 to fix it.
cargo build --target aarch64-unknown-linux-gnu
  In file included from bpf_prog_linfo.c:9:
  libbpf_internal.h:19:10: fatal error: libelf.h: No such file or directory
     19 | #include <libelf.h>
        |          ^~~~~~~~~~
  compilation terminated.
  In file included from nlattr.c:14:
  libbpf_internal.h:19:10: fatal error: libelf.h: No such file or directory
     19 | #include <libelf.h>
        |          ^~~~~~~~~~
  compilation terminated.
  In file included from libbpf_errno.c:15:
  libbpf_internal.h:19:10: fatal error: libelf.h: No such file or directory
     19 | #include <libelf.h>
        |          ^~~~~~~~~~
  compilation terminated.
  make: *** [Makefile:134: /home/kxxt/repos/libbpf-sys/target/aarch64-unknown-linux-gnu/debug/build/libbpf-sys-099efd81f8db105f/out/obj/staticobjs/nlattr.o] Error 1
  make: *** Waiting for unfinished jobs....
  make: *** [Makefile:134: /home/kxxt/repos/libbpf-sys/target/aarch64-unknown-linux-gnu/debug/build/libbpf-sys-099efd81f8db105f/out/obj/staticobjs/bpf_prog_linfo.o] Error 1
  make: *** [Makefile:134: /home/kxxt/repos/libbpf-sys/target/aarch64-unknown-linux-gnu/debug/build/libbpf-sys-099efd81f8db105f/out/obj/staticobjs/libbpf_errno.o] Error 1
  btf.c:18:10: fatal error: gelf.h: No such file or directory
     18 | #include <gelf.h>
        |          ^~~~~~~~
  compilation terminated.

static, vendored
cargo build --target aarch64-unknown-linux-gnu -F static,vendored

  Makefile.am: installing './INSTALL'
  backends/Makefile.am: installing 'config/depcomp'
  configure.ac: installing 'config/ylwrap'
  parallel-tests: installing 'config/test-driver'
  configure: error: in '/home/kxxt/repos/libbpf-sys/elfutils':
  configure: error: cannot run C compiled programs.
  If you meant to cross compile, use '--host'.
  See 'config.log' for more details
  thread 'main' panicked at build.rs:305:5:
  make failed
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

After I modify build.rs to pass --host aarch64-linux-gnu to configure, another error:
  --- stderr
  configure: WARNING: not running biarch tests,  does not work
  /home/kxxt/repos/libbpf-sys/elfutils/libcpu/i386_parse.y:243.1-8: warning: POSIX Yacc does not support %defines [-Wyacc]
    243 | %defines
        | ^~~~~~~~
  /bin/sh: line 1: ./i386_gendis: cannot execute binary file: Exec format error
  /bin/sh: line 1: ./i386_gendis: cannot execute binary file: Exec format error
  make[1]: *** [Makefile:814: i386_dis.h] Error 126
  make[1]: *** Waiting for unfinished jobs....
  make[1]: *** [Makefile:814: x86_64_dis.h] Error 126
  make: *** [Makefile:542: install-recursive] Error 1
  thread 'main' panicked at build.rs:318:5:
  make failed
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This is an upstream bug(https://sourceware.org/bugzilla/show_bug.cgi?id=28891). Unfortunately, to fix it, we need to import  upstream provided release tarballs into this repo instead of using git submodule. Is that acceptable?

Unfortunately, to fix it, we need to import upstream provided release tarballs into this repo instead of using git submodule. Is that acceptable?

I see that libbpf-sys is already using a mirrored repo of elfutils: https://github.com/libbpf/elfutils-mirror.git
I think the best way to solve the cross-compilation failure is

Convert elfutils-mirror to a fork of elfutils
Disable maintainer mode in build.rs
When updating elfutils, generate the missing header files and commit them:

autoreconf --install --force
./configure --disable-debuginfod --enable-maintainer-mode --without-zstd --disable-libdebuginfod
make -C lib libeu.a
make dist
git add -f libdw/known-dwarf.h libcpu/x86_64_dis.h libcpu/i386_dis.h
git commit -m "generate headers"
git push

This way we have all the required generated headers and cross-compilation is working.

I see that libbpf-sys is already using a mirrored repo of elfutils: https://github.com/libbpf/elfutils-mirror.git
I think the best way to solve the cross-compilation failure is
1. Convert elfutils-mirror to a fork of elfutils

2. Disable `maintainer mode` in `build.rs`

3. When updating elfutils, generate the missing header files and commit them:

autoreconf --install --force
./configure --disable-debuginfod --enable-maintainer-mode --without-zstd --disable-libdebuginfod
make -C lib libeu.a
make dist
git add -f libdw/known-dwarf.h libcpu/x86_64_dis.h libcpu/i386_dis.h
git commit -m "generate headers"
git push

This way we have all the required generated headers and cross-compilation is working.

I have created a cross-compilation friendly fork: https://github.com/kxxt/libbpf-sys-cross/tree/libbpf-sys-cross using the above workflow. But unfortunately I cannot really use it in my application because of https://github.com/rust-lang/cargo/issues/9227
If this workflow can be accepted, please let me know and I will create a pull request.

until upstream gets their act together (which admittedly may not happen at all...)

I don't think elfutils will fix their bug. This bug has been there for 14 years<EMAIL_ADDRESS>
My suggestion would be to create a GitHub Action that generates the headers and commits and force-pushes them to a different branch, from which they can be consumed. In my opinion, we should strive for this happening without human input. If you agree, feel free to open a pull request against the mirror and we can work to get it in.

I totally agree with you. I will try to set up GitHub Actions to do that. But I probably won't be able to open a PR to against the mirror. The GitHub actions should be placed on a new orphan branch to avoid conflicts with upstream. And GitHub PR cannot do that.

the libbpf-sys changes seem sensible to me and I don't see any conceptual roadblocks to merging

Thanks!

Why do we need libstdc++? Did you update elfutils? I recall newer versions requiring it, but that was not the case with the version we currently mirror.

Yes, the security report in my CI warns me about CVE-2024-25260 found in libbpf-sys so I updated elfutils to 0.191

I have get the GitHub Actions solution working.
So here's how it works:
The CI is updated to test cross-compilation for x86_64, aarch64 and riscv64 gnu targets.

We add a workflow to libbpf-sys (not elfutils-mirror)
When elfutils need to be updated, trigger the workflow manually with a tag  from elfutils-mirror repo(for example: elfutils-0.190) .
Then the workflow will generate the missing headers and commit them to elfutils-0.190-cross branch. This branch is then published to elfutils-mirror repo.
After that, the workflow will open a pull request to libbpf-sys repo to bump the elfutils submodule.

One unfortunately thing is that the CI won't run for this PR because it is opened by a bot. A workaround is manually close and reopen the PR.
When the CI is green(hopefully), we can merge that into libbpf-sys repo.
Otherwise, we can continue to fix things in that PR to make the CI green and then merge it. (example: https://github.com/kxxt/libbpf-sys-cross/pull/3)

I will open a PR to libbpf-sys after my previous PR is done: #93

Why do we need libstdc++?

libstdc++ is actually not required if we only build libelf. The build script build all the tool binaries() which not only wastes time and also pulls in C++ dependencies. I fixed it in https://github.com/kxxt/libbpf-sys-cross/pull/3

We add a workflow to libbpf-sys (not elfutils-mirror)

Why not elfutils-mirror, though? I'd rather not have cross-repo dependencies like this. Particularly given that they are not maintained by the same folks.
We can just move the code of elfutils-mirror into a different branch and land the action code on main, assuming that was the issue. Then we should be able to use a cronjob action or a branch pattern to run on all other or specifically patterned branches and create new <...>-cross branches in response.
It possible I am missing something else, of course.

Why do we need libstdc++?

libstdc++ is actually not required if we only build libelf. The build script build all the tool binaries() which not only wastes time and also pulls in C++ dependencies. I fixed it in kxxt#3

This is great. Feel free to open a pull request.

Why not elfutils-mirror, though? I'd rather not have cross-repo dependencies like this. Particularly given that they are not maintained by the same folks.
We can just move the code of elfutils-mirror into a different branch and land the action code on main, assuming that was the issue.

Yes, I wanted to do it that way in the first place as well.

Then we should be able to use a cronjob action

That might be possible. But I am not sure how you want to do it in a cronjob.

or a branch pattern to run on all other or specifically patterned branches and create new <...>-cross branches in response.

That's not how GitHub Actions works.  Initially I tried to create a workflow that runs on new tags.  GitHub Actions uses the workflow file from whatever branch/tag it is running on instead of using the yml file from the default branch. If the branch/tag doesn't have the workflow yml file, the workflow won't run at all.

It is possible I am missing something else, of course.

The workflow yaml file I am using now is a workflow_dispatch one that needs to be triggered manually.
So it is not impossible to place it at the elfutils-mirror repo.  But I feel it is not the right place if the workflow isn't fully automatic. By placing it in libbpf-sys repo, we only manually trigger the workflow when we want to update the elfutils submodule and the workflow opens a pull request for it.

This is great. Feel free to open a pull request.

@danielocfb https://github.com/libbpf/libbpf-sys/pull/95 for optimizing  the build time.

Well, now I think we no longer need to touch elfutils-mirror repo at all.
The needed generated headers are only necessary when building libcpu, which is a library we actually don't need. I am changing #95 into a PR for fixing cross-compilation with static,vendored features.


added windows 11

after reading this article, i confirmed windows 11 is supported

Learn Build status updates of commit 7c01db5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/security-policy-settings/accounts-guest-account-status.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


最近一直403 求解

最近除了这个问题 新手 不知道怎么解决 有没有大佬看下
{
"error": {
"errors": [
{
"domain": "global",
"reason": "downloadQuotaExceeded",
"message": "The download quota for this file has been exceeded."
}
],
"code": 403,
"message": "The download quota for this file has been exceeded."
}
}

google drive 下载限额超了

google drive 下载限额超了

这个有没有 解决办法呢


IntelliJ debugger not converting paths correctly

The IntelliJ debugger appears to not be converting paths correctly. It cannot step into a getter whereas the devtools debugger, attached to the same instance of the VM, was able to step into the getter.
To reproduce the situation:

Clone the sdk repo (any commit should work, but I was using f7bf890ff77046576c1c3ca5f5414ca17a0590f7).
Open the analyzer package as a module.
Add the file analyzer/test/src/diagnostics/assignment_to_final_test.dart with the following content:

// Copyright (c) 2019, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

import 'package:analyzer/dart/analysis/features.dart';
import 'package:analyzer/src/generated/engine.dart';
import 'package:test_reflective_loader/test_reflective_loader.dart';

import '../dart/resolution/driver_resolution.dart';

main() {
  defineReflectiveSuite(() {
//    defineReflectiveTests(AssignmentToFinalTest);
    defineReflectiveTests(AssignmentToFinalWithNnbdTest);
  });
}

@reflectiveTest
class AssignmentToFinalTest extends DriverResolutionTest {}

@reflectiveTest
class AssignmentToFinalWithNnbdTest extends AssignmentToFinalTest {
  @override
  AnalysisOptionsImpl get analysisOptions => AnalysisOptionsImpl()
    ..contextFeatures = new FeatureSet.forTesting(
        sdkVersion: '2.3.0', additionalFeatures: [Feature.non_nullable]);

  test_field_late() async {
    await assertNoErrorsInCode('''
class A {
  final a;
  void m() {
    a = 1;
  }
}
''');
  }

  test_localVariable_late() async {
    await assertNoErrorsInCode('''
void f() {
  final a;
  a = 1;
}
''');
  }
}

Add a breakpoint in analyzer/lib/src/dart/element/element.dart on line 9158. (In case the source changes, that's here in PropertyInducingElementImpl.isLate:

  @override
  bool get isLate {
    if (linkedNode != null) {
      return enclosingUnit.linkedContext.isLate(linkedNode);
    }
    if (_unlinkedVariable != null) {
      return _unlinkedVariable.isLate; // <-- Breakpoint here
    }
    return hasModifier(Modifier.LATE);
  }

Debug the file added in step 3. When the breakpoint is hit, attempt to step into the getter isLate.

When I did this, the newly added frame was highlighted in yellow (what does that mean?) and the file containing the method was not opened. My current hypothesis is that the path of the file that should have been opened (analyzer/lib/src/summary/format.dart) could not be correctly converted to the URI sent by the VM (or vice versa).

This was running
IntelliJ IDEA 2019.1.2 (Community Edition)
Build #IC-191.7141.44, built on May 7, 2019
JRE: 1.8.0_202-release-1483-b49 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.4
using version 2.3.0-edge.f61a96c9297df400271b035558c8f972bb827779 of the SDK.


Dev

Included beforeModalShow method

Why for ? Please provide explanation and use case where this could be helpful

@LouisJS  In my case i'm using beforeModalShow() method to apply custom sound while opening modal.

IMO, it doesn't belong to the react-native-modal repository.
You should do your action the same time you're setting Modal to visible=true

I agree with @LouisJS , you should do that kind of logic when you show the modal. No need for another trigger :)
Thanks anyway!


YARN-9906. Fix Docker container multi volume mounts bug

NOTICE
YARN-9906. Fix Docker container multi volume mounts bug

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
83
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
1237
trunk passed

+1
compile
65
trunk passed

+1
checkstyle
28
trunk passed

+1
mvnsite
38
trunk passed

+1
shadedclient
882
branch has no errors when building and testing our client artifacts.

+1
javadoc
27
trunk passed

0
spotbugs
77
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
75
trunk passed

_ Patch Compile Tests _

+1
mvninstall
35
the patch passed

+1
compile
56
the patch passed

+1
javac
56
the patch passed

+1
checkstyle
22
the patch passed

+1
mvnsite
33
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
877
patch has no errors when building and testing our client artifacts.

+1
javadoc
25
the patch passed

+1
findbugs
80
the patch passed

_ Other Tests _

+1
unit
1288
hadoop-yarn-server-nodemanager in the patch passed.

+1
asflicense
29
The patch does not generate ASF License warnings.

4971

Subsystem
Report/Notes

Docker
Client=19.03.3 Server=19.03.3 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1659/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1659

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux ea8c587da3bf 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / bbcf0b9

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1659/1/testReport/

Max. process+thread count
306 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1659/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
20m  2s
trunk passed

+1 :green_heart:
compile
1m 20s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
1m  9s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
checkstyle
0m 28s
trunk passed

+1 :green_heart:
mvnsite
0m 42s
trunk passed

+1 :green_heart:
shadedclient
15m 27s
branch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 27s
hadoop-yarn-server-nodemanager in trunk failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
0m 30s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+0 :ok:
spotbugs
1m 25s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
1m 21s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 41s
the patch passed

+1 :green_heart:
compile
1m  9s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javac
1m  9s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
javac
1m  1s
the patch passed

+1 :green_heart:
checkstyle
0m 22s
the patch passed

+1 :green_heart:
mvnsite
0m 34s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 38s
patch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 26s
hadoop-yarn-server-nodemanager in the patch failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
0m 24s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
findbugs
1m 29s
the patch passed

_ Other Tests _

-1 :x:
unit
22m  7s
hadoop-yarn-server-nodemanager in the patch passed.

-1 :x:
asflicense
0m 32s
The patch generated 1 ASF License warnings.

86m  4s

Reason
Tests

Failed junit tests
hadoop.yarn.server.nodemanager.containermanager.linux.runtime.TestRuncContainerRuntime

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1659

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 4ed8f6d9bdfb 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e756fe35909

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/3/artifact/out/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/3/artifact/out/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

unit
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/3/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/3/testReport/

asflicense
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/3/artifact/out/patch-asflicense-problems.txt

Max. process+thread count
422 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/3/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 11s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
42m 43s

trunk passed

+1 :green_heart:
compile
1m 47s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
1m 41s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
0m 39s

trunk passed

+1 :green_heart:
mvnsite
0m 55s

trunk passed

+1 :green_heart:
javadoc
0m 43s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 38s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
spotbugs
1m 51s

trunk passed

+1 :green_heart:
shadedclient
19m 54s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 45s

the patch passed

+1 :green_heart:
compile
1m 45s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
1m 45s

the patch passed

+1 :green_heart:
compile
1m 39s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
1m 39s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 24s

the patch passed

+1 :green_heart:
mvnsite
0m 40s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
spotbugs
2m  0s

the patch passed

+1 :green_heart:
shadedclient
19m 42s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
24m 36s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
0m 35s

The patch does not generate ASF License warnings.

124m 45s

Reason
Tests

Failed junit tests
hadoop.yarn.server.nodemanager.containermanager.linux.runtime.TestRuncContainerRuntime

hadoop.yarn.server.nodemanager.amrmproxy.TestFederationInterceptor

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1659

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux dd1307714c1f 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9bb25cd28fe2262d4dc9f84aa82a7263d006a66c

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/1/testReport/

Max. process+thread count
513 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1659/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


fix(engine/simplify_question_marks): fix type arguments on from

This PR makes the utility function call in ast_utils takes extra parameter, so that we can generate a proper call to from. We were missing the two generic type arguments on this method call when simplifying question marks.
Fixes #1083.

Can you ocamlformat this?


Is there any information about the analysis of the code of this project ?

I am looking for some articles or information about the design of this project just like what in the documentation of petsc.

Maybe this is a good start:
https://dl.acm.org/doi/10.1145/3480935

Thanks very much. I am trying.


Consider narrower classes for static matcher methods

Consider adding a Matchers or ValueMatchers class with static helper methods for creating ValueMatcher instances. There is currently the Ddjt class, but that name is hard to remember or discover, and it contains not only helper methods for creating matchers but also other kinds of methods. For example, it contains a method aMapOf, which could be confused for a matcher helper method. Also since the CodeMatcher instances work differently than ValueMatchers, perhaps they should be in a CodeMatchers class rather than being a part of the same class of helper methods as the ValueMatcher helper methods.

Further, in the new matcher class(es), I would consider not including the 'be' aliases for the methods currently in the Ddjt class. For example, greaterThan and beGreaterThan - only provide greaterThan. Since DataNode contains the shouldBe alias for should and shouldNotBe alias for shouldNot, it seems that users will still be able to write their assertions in ways that will sound correct when spoken. I think having fewer options will make it easier for users to find the matchers they are looking for more quickly.

Webtau allows to write mixed tests, i.e. cli test that plays nicely with browser and http. In this case it would not be as convenient to have them separated. Right now, assuming a single static star DSL import, one can simply start writing http.put and cli.run without fiddling with imports.
Discovery is a tricky business. If you split into separate classes then you will have to somehow discover those.

https://github.com/twosigma/webtau/pull/449


Remove duplicate marker

Remove the second definition of marker, which incorrectly overwrites the first one. The new marker should automatically start replacing the old one, since they have the same name.
Note that other repos depend/used to depend directly on the github for this repo, so I can't remove the marker font file, which is depended on by some builds out there.

Thanks for all the reviews!!


[BUG] font-normal is not a tailwind css class

Describe the bug
I'm getting the following error when using the font-normal tailwindcss class: Classname 'font-normal' is not a Tailwind CSS class
You can see the exact error right here:
https://github.com/Axedyson/syncbase/runs/8176476144?check_suite_focus=true
To Reproduce

Clone this repo
Run yarn install in the root directory
Run yarn eslint . --max-warnings 0 in the root directory

Expected behavior
It shouldn't complain about the css class
Environment (please complete the following information):

OS: WSL2 (Ubuntu 20.04.5 LTS)
eslint-plugin-tailwindcss version: 3.6.1
tailwindcss version: 3.1.8
eslint version: 8.23.0

eslint config file or live demo
Here is the eslint config that was in use:
https://github.com/Axedyson/syncbase/blob/main/.eslintrc.js

Okay I'm stupid, I didn't specify a font-normal in the tailwindcss config


Issue building version 0.1.2 with Carthage

I am using swift-hoedown using Carthage. In my Cartfile I specified this as:
github "njdehoog/swift-hoedown" ~> 0.1

When I run the initial
carthage bootstrap

I get the following error:
*** Fetching swift-hoedown
*** Fetching hoedown
*** Checking out hoedown at "3.0.2"
*** Checking out swift-hoedown at "0.1.2"
Parse error: expected submodule commit SHA in output of task (ls-tree -z 0.1.2 Carthage/Checkouts/hoedown) but encountered:

This used to work just fine. By hard coding 0.1.1 as the version for swift-hoedown the problem is gone.
Any advise is appreciated.

Same problem,wish can be fix soon.


[Bug] - CRITICAL: Deadlock AgentHealthManager and failing instrumentation

Describe the bug
Under unknown circumstances an inspectIT Thread as well as an application thread run into a deadlock.
The inspectIT Thread tries to log a message in AgentHealthManager and the application thread wants to log an error from a failing instrumentation (ContextPropagationUtil.readPropagatedSpanContextFromHeaderMap). Afterwards each thread that also runs into an failing instrumentation is also blocked as the log cannot be written. Finally, the application crashes or is not capable to respond if too many threads are blocked.
How I interpret the thread dump (section Additional information):

inspectIT Thread: AgentHealthManager.triggerEventAndMetricIfHealthChanged detects a AgentHealtStatus Change (maybe because the instrumentation failed). Within this method, a lock is created 0x000000030a72ce78 and the thread wants to write a log. Unfortunately, the application thread already acquired the lock
Application Thread: The failing instrumentation triggers writing of an error lock. Logback creates a Lock (the lock that the inspectIT Agent cannot get). Afterwards Logback calls rocks.inspectit.ocelot.core.logging.logback.InternalProcessingAppender.append that calls AgentHealthManager.triggerEventAndMetricIfHealthChanged. As the inspectIT Thread holds the lock to the synchronize block, the application thread is blocked

AgentHealthManager.triggerEventAndMetricIfHealthChanged
To Reproduce
Don't know how to reproduce
Expected behavior
No deadlock ;-) Both threads can write the log.
I think best would be that the application thread is decoupled from "Agent Status Health", meaning detection, signaling should not happen within the application thread. It should not happen that managing the Agent Health Status can decrease application performance until application outage
Additional information (screenshots, stack traces, etc.)
`Found one Java-level deadlock:
"inspectit-thread-0":
waiting to lock monitor 0x00007f1a5bbee480 (object 0x000000030dc40a88, a rocks.inspectit.ocelot.core.logging.logback.InternalProcessingAppender),
which is held by "http-nio-8080-exec-1447"
"http-nio-8080-exec-1447":
waiting to lock monitor 0x00007f1a16c53b80 (object 0x000000030a72ce78, a rocks.inspectit.ocelot.core.selfmonitoring.AgentHealthManager),
which is held by "inspectit-thread-0"
Java stack information for the threads listed above:
"inspectit-thread-0":
at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:63)
- waiting to lock <0x000000030dc40a88> (a rocks.inspectit.ocelot.core.logging.logback.InternalProcessingAppender)
at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51)
at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:270)
at ch.qos.logback.classic.Logger.callAppenders(Logger.java:257)
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:421)
at ch.qos.logback.classic.Logger.filterAndLog_2(Logger.java:414)
at ch.qos.logback.classic.Logger.warn(Logger.java:700)
at rocks.inspectit.ocelot.core.selfmonitoring.AgentHealthManager.triggerEventAndMetricIfHealthChanged(AgentHealthManager.java:168)
- locked <0x000000030a72ce78> (a rocks.inspectit.ocelot.core.selfmonitoring.AgentHealthManager)
at rocks.inspectit.ocelot.core.selfmonitoring.AgentHealthManager.checkHealthAndSchedule(AgentHealthManager.java:147)
at rocks.inspectit.ocelot.core.selfmonitoring.AgentHealthManager$$Lambda$2107/0x0000000800c1ec40.run(Unknown Source)
at rocks.inspectit.ocelot.core.instrumentation.context.ContextManager.lambda$wrap$1(ContextManager.java:76)
at rocks.inspectit.ocelot.core.instrumentation.context.ContextManager$$Lambda$3174/0x0000000800dcec40.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(java.base@11.0.18/Executors.java:515)
at java.util.concurrent.FutureTask.run(java.base@11.0.18/FutureTask.java:264)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(java.base@11.0.18/ScheduledThreadPoolExecutor.java:304)
at<EMAIL_ADDRESS>Source)
at<EMAIL_ADDRESS>Source)
at<EMAIL_ADDRESS>Source)
"http-nio-8080-exec-1447":
at rocks.inspectit.ocelot.core.selfmonitoring.AgentHealthManager.triggerEventAndMetricIfHealthChanged(AgentHealthManager.java:163)
- waiting to lock <0x000000030a72ce78> (a rocks.inspectit.ocelot.core.selfmonitoring.AgentHealthManager)
at rocks.inspectit.ocelot.core.selfmonitoring.AgentHealthManager.onLoggingEvent(AgentHealthManager.java:72)
at rocks.inspectit.ocelot.core.logging.logback.InternalProcessingAppender.append(InternalProcessingAppender.java:76)
at rocks.inspectit.ocelot.core.logging.logback.InternalProcessingAppender.append(InternalProcessingAppender.java:27)
at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:82)
- locked <0x000000030dc40a88> (a rocks.inspectit.ocelot.core.logging.logback.InternalProcessingAppender)
at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51)
at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:270)
at ch.qos.logback.classic.Logger.callAppenders(Logger.java:257)
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:421)
at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:383)
at ch.qos.logback.classic.Logger.error(Logger.java:538)
at rocks.inspectit.ocelot.core.instrumentation.context.ContextPropagationUtil.readPropagatedSpanContextFromHeaderMap(ContextPropagationUtil.java:231)
at rocks.inspectit.ocelot.core.instrumentation.context.InspectitContextImpl.readDownPropagationHeaders(InspectitContextImpl.java:468)
at org.apache.tomcat.websocket.server.inspectitGen$$$5549193644763076326.executeImpl(VoidGenericActionTemplate.java)
at org.apache.tomcat.websocket.server.inspectitGen$$$5549193644763076326.execute(VoidGenericActionTemplate.java:23)
at rocks.inspectit.ocelot.core.instrumentation.actions.bound.BoundGenericAction.executeImpl(BoundGenericAction.java:113)
at rocks.inspectit.ocelot.core.instrumentation.actions.bound.BoundGenericAction.execute(BoundGenericAction.java:100)
at rocks.inspectit.ocelot.core.instrumentation.hook.actions.ConditionalHookAction.execute(ConditionalHookAction.java:24)
at rocks.inspectit.ocelot.core.instrumentation.hook.MethodHook.onEnter(MethodHook.java:118)
at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilter.doFilter(InvokerFilter.java:68)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:177)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:360)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:891)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1784)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
- locked <0x00000006490479a8> (a org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(java.base@11.0.18/Thread.java:829)
`
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Agent Version 2.3.0. Looking at Code Changes of AgentHealthManager and InternalProcessingAppender, I think it can happen since Version 1.16

I can reproduce the issue locally. Thanks for the bug report. That helped a lot by spotting the source of the bug. I should be able to have a fix at the end of the week.
But I am not so sure, when a release containing this fix will happen.


unmounting / remounting in StackNavigator

hi I asked on discord but no real luck there.
react-navigation question/ignorance/confusion: it seems the StackNavigator keeps components around even as they get buried on the stack. They don't seem to be unmounted for example. This means when things pop off and the app is returning to an 'old' page, it has 'old' state afaict like if a textinput had gained focus, when we return it will still have focus - whereas it was defined to start off unfocused. iiuc this is a problem i have in my use case. does react-navigation give me something, sort of like "viewWillReappar" where i could know that a given component/page is live again because it was returned to / popped to?

"react-navigation": "^1.0.0-beta.9",
"react-native": "0.44.0",
"react-redux": "^5.0.5",
"redux": "^3.6.0",
"redux-logger": "^3.0.6",
"redux-thunk": "^2.2.0",

yeah I need this, so my code in componentDidMount(); is working

@buncismamen et. al. I do not think that #51 is what I want, personally. What I think I want is a navigator that remembers the stack but

does not pre-create any components.
only creates the component when they are being navigated to, either going to them or returning to them from the stack.
releases/frees/destroys the component when navigating away from it. (in the case of navigating to the same screen then i am going to hazard to guess it is better to not release it, as the exception that proves the rule.)
thus calls the full RN component lifecycle appropriately when going to or leaving a component.

What I want is basically a "StacklessNavigator" that keeps the history so that back navigation works right automatically, however, does not cache any components at all. (Somebody should think of a better name, of course, like "NonCachingStackNavigator" or something.)

Hi Guys!  I'm new here and have been asked to help out with this.  Based on the last post by @jslz it seems this would be a custom router where every route acted like a reset() but the route history is stored in an array somewhere, so when you go "back" it will create a new nav to the previous route via the array.
Are you sure you want to destroy and create the view each time?  this can cause render delays especially if data is involved.

@leejms having the option to experiment with cached vs. non-cached would be great. While caching might make things faster, it has various effects that don't fit our use case so well.

cool!  i'm getting the code now and will look into it.
can you give me a newbie version of the unwanted effect and how to create it?
(very noob! :) )
@jslz & @buncismamen

same issue

@leejms, @yash2code  wouldn't this replace here - https://github.com/react-community/react-navigation/issues/2122 - solve this issue?

I have following dependencies:
"react-navigation": "^1.0.0-beta.11",
"react": "16.0.0-alpha.12",
"react-native": "0.45.1"
How can I use navigator.pop() function? I need to unmount older screen and navigate to new screen.

NavigationActions.reset saved me.
I spent time to re-understand NavigationActions.reset's usage.
the correct usage is that you should reset all navigation state stack.
it means we should give a basic stack navigation list to actions , and point out your current index.

   const resetAction = NavigationActions.reset({
        index: 2,         // it means current state is C, and can goBack to A
        actions: [
          NavigationActions.navigate({ routeName: 'A'}),
          NavigationActions.navigate({ routeName: 'B', params: {id: "***"}}),
          NavigationActions.navigate({ routeName: 'C', params: {id: "***"}}),
          NavigationActions.navigate({ routeName: 'D', params: {id: "***"}})
        ]
   })
   this.props.navigation.dispatch(resetAction);

Oh wow thanks for sharing that @ArvoGuo - your example really helps to makes sense of it!

Pinging OP @jslz since this issue has not been active for a while, and it's related to an old version of the lib. Moreover, the snippet @ArvoGuo seems to help out in clarifying the question and the actual FR is on #51.
Please let me know if you want this to remain open; if I get no answer in the next 7 days I will close it.

Hi there @jslz ,
In an effort to cleanup this project and prioritize a bit, since this issue had no follow up since my last comment I'm going to close it.
If you are still having the issue with the latest version (especially if it's a bug report) please check the current open issues, and if you can't find a duplicate, open a new one that uses the new Issue Template to provide some more details to help us solve it.

Navigations.reset is now replaced with StackActions.reset


Add "coil" entity for coil-level data

While most MRI data with multi-channel coils is saved and converted to images only in its combined state, one can reconstruct both magnitude and phase data from each coil separately.
My understanding is that coil-level data is necessary for quantitative susceptibility mapping with SWI data, which is why BEP-004 proposes the addition of a "coil" entity. However, coil-level data can also be used in other modalities, including fMRI, where phase-based denoising can be improved by incorporating coil-level phase data (which @CesarCaballeroGaudes and @ostanley most likely know more about than me).

Hi @tsalo could you be a bit more concrete what you are proposing, preferably also with an example? that will make your issue easier to parse for @bids-standard/raw-mri

Ah, yes, sorry about that. The idea is that you can save the signal (both magnitude and phase) from individual channels in the head coil. Typically, the scanner combines the data across coils before reconstruction, but it's something you can switch in most sequences. Unfortunately, I don't know exactly which datatypes the entity should apply to, except SWI and func.
In BEP004, the proposed format is _coil-<index>, with the convention that, if coil is not defined, it is assumed that the image is the total/combined data. So, we might have:

func/sub-X_task-Y_coil-1_bold.nii.gz
func/sub-X_task-Y_coil-1_bold.json
func/sub-X_task-Y_coil-2_bold.nii.gz
func/sub-X_task-Y_coil-2_bold.json
func/sub-X_task-Y_coil-3_bold.nii.gz
func/sub-X_task-Y_coil-3_bold.json
func/sub-X_task-Y_bold.nii.gz  # coils 1-3 combined, probably with sum of squares
func/sub-X_task-Y_bold.json

I don't have any data collected yet, but I was hoping to get some phantom data I could share as an example at some point in the near future. In the meantime, is the example I provided helpful?

Just chiming in here. I have two thoughts on this but I am not as familiar with BIDS specs. I will read up.

Storing coil specific functional data will drastically increase storage requirements. I don't think this matters to BIDS but it is something to think about for sharing data. A 32 channel Rx means 32 times the data if it is stored at this level. This turns a 200MB functional file to 6.4GBof data for example and that is just uncombined magnitude.

I think that if you are storing combined and uncombined runs in the same folder you need a required field, probably in the json, with a combination method. For example, as sos combined image has a phase of 0 but a complex sum combined image results in poor combinations for magnitude and phase. Therefore you may have a _bold.nii.gz file with one method and a _phase.nii.gz with another method. This is why I believe if you are looking into this stuff the combination method should be required. I don't know the scope of that requirement though. I will think about it.

Hope this helps. Happy to chat more. Excited other people want to try phase denoising :)
Olivia

@ostanley thank you for weighing in. I hadn't thought about the metadata that should be associated with the entity.
It looks like CoilCombinationMethod is a recommended metadata field (see the last row here), so there's no need to edit the metadata requirements, but we will need more documentation related to coil-level data. I believe that coil-level files should just have "None" or maybe "n/a" for the CoilCombinationMethod field, while the combined files can have some value there if the method used was not root-sum-of-squares (rSOS). Perhaps it would be necessary to add a check when the entity coil is used that CoilCombinationMethod be set to "None" in the validator.

Would it perhaps be better to use "channel" instead of "coil"? I know that "coil" tends to refer to the whole unit, while "channel" refers to the individual subunits, although in at least one case in the MR BIDS specification, they seem to be used interchangeably:

For the fields described above and in the following section, the term "Volume" refers to a reconstruction of the object being imaged (e.g., brain or part of a brain). In case of multiple channels in a coil, the term "Volume" refers to a combined image rather than an image from each coil.


CAD Disconnecting Randomly

What version of Node.js are you using?
17.3.0
What version of npm are you using?
7.10.0
What operating system are you using?
Windows Server 2019
What version of SnailyCAD are you currently using?
1.26.5
Describe the Bug
[1] }
[1] { PROCESS_CWD: 'C:\\nginx\\html\\snaily-cadv4\\apps\\api' }
[1] { PROCESS_CWD: 'C:\\nginx\\html\\snaily-cadv4\\apps\\api' }
[1] { PROCESS_CWD: 'C:\\nginx\\html\\snaily-cadv4\\apps\\api' }
[1] { PROCESS_CWD: 'C:\\nginx\\html\\snaily-cadv4\\apps\\api' }
[1] { PROCESS_CWD: 'C:\\nginx\\html\\snaily-cadv4\\apps\\api' }
[1] { PROCESS_CWD: 'C:\\nginx\\html\\snaily-cadv4\\apps\\api' }
[1] { PROCESS_CWD: 'C:\\nginx\\html\\snaily-cadv4\\apps\\api' }
[1] Error:
[1] Invalid `prisma.officer.updateMany()` invocation:
[1]
[1]
[1] Error occurred during query execution:
[1] ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Error { kind: Db, cause: Some(DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState(E40P01), message: "deadlock detected", detail: Some("Process 12896 waits for ShareLock on transaction 608681; blocked by process 8208.\nProcess 8208 waits for ShareLock on transaction 608682; blocked by process 12896."), hint: Some("See server log for query details."), position: None, where_: Some("while updating tuple (7,3) in relation \"Officer\""), schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("deadlock.c"), line: Some(1153), routine: Some("DeadLockReport") }) }) })
[1]     at RequestHandler.handleRequestError (C:\nginx\html\snaily-cadv4\node_modules\@prisma\client\runtime\index.js:30855:13)
[1]     at RequestHandler.request (C:\nginx\html\snaily-cadv4\node_modules\@prisma\client\runtime\index.js:30834:12)
[1]     at async PrismaClient._request (C:\nginx\html\snaily-cadv4\node_modules\@prisma\client\runtime\index.js:31812:16)
[1]     at async Promise.all (index 0)
[1]     at async setInactiveUnitsOffDuty (C:\nginx\html\snaily-cadv4\apps\api\src\lib\leo\setInactiveUnitsOffDuty.ts:6:3)
[1] yarn workspace @snailycad/api generate && yarn workspace @snailycad/api start exited with code 1

Expected Behavior
CAD has disconnected and there is the information from the console. Not sure why its doing it.
To Reproduce
No response

[     script:sna-alpr] Error: SyntaxError: Unexpected token < in JSON at position 0
[     script:sna-alpr]     at JSON.parse (<anonymous>)
[     script:sna-alpr]     at consumeEnd (@sna-alpr/server/server.js:5208:24)
[     script:sna-alpr]     at BodyReadable.<anonymous> (@sna-alpr/server/server.js:5195:11)
[     script:sna-alpr]     at BodyReadable.emit (node:events:394:28)
[     script:sna-alpr]     at BodyReadable.emit (@sna-alpr/server/server.js:5084:22)
[     script:sna-alpr]     at endReadableNT (node:internal/streams/readable:1343:12)
[     script:sna-alpr]     at processTicksAndRejections (node:internal/process/task_queues:83:21)

Also I see this in the server console errors


Enabling bedrock service in Frankfurt.

https://github.com/ministryofjustice/modernisation-platform/issues/5677
Updating Modernisation Platform top-level SCP to allow access to Bedrock in eu-central-1.
Note: This is not added to the regional SCP because it would block bootstrapping activities in non-MP accounts in Germany.

Hi @julialawrence, I don't think this is needed specifically to allow Bedrock access. We allow unrestricted use of Frankfurt (eu-central-1) as part of the regional service control policy.
The Modernisation Platform-specific SCP doesn't lock down further use of Frankfurt, so this change appears to be wider ranging than possibly appropriate, unless I'm misunderstanding it?
@davidkelliott could you advise?


Question about the colors

I found this repo cause I am currently also trying to create RGB dem tiles and they also have some strange spikes in them.
I followed an other tutorial first where i created the RGB dem using rio rgbify but here I've seen that you simply use gdal and the color-mapping.
I wonder how that works though?!?
3590 68 1 84
8890 253 231 37

where as the formula should be
height = -10000 + ((R * 256 * 256 + G * 256 + B) * 0.1)

but if I enter your values, this does not add up? So I am wondering how your color-mapping works?
Would be awesome if you could explain that.

You just need to determine a range of elevations that encompasses your DEM data. In this case, all of the raster values fall between 3590 meters and 8890 meters. The color range is expressed as RGB values from rgb (68, 1, 84) at 3590 meters to rgb (253, 231, 37) at 8890 meters. Each included meter is assigned a color within this RGB range. This is simply a two-entry version of the techniques for hypsometric tinting presented on websites like Bjørn Sandvik's "Creating color relief and slope shading with gdaldem" and Robert Simmon's "A Gentle Introduction to GDAL Part 5: Shaded Relief."


Add NavigationItem child items

Hey @pomianowski
Do you think it is possible to add something like child nav-item?

+1


Error compiling

How did you get this to work with java 10? I get the following error:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project XXX: Fatal error compiling: invalid target release: 10 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project XXX: Fatal error compiling

I have the same error:

@axpira I can see your maven running on jdk 1.8.0_151

I created a PR that fixes it:
https://github.com/joshlong/spring-boot-and-java-10/pull/3

@anandshah123 So the solution is to run maven on jdk 10? How do I do that?
@mballoni Your PR doesn't fix the problem for me, possibly because I need to change the JAVA_HOME or maven java version to java 10?


call v:lua.cmp.utils.feedkeys.call.run(2) is inserted if the plugin is lazy-loaded with other plugins by dein.vim

FAQ

[X] I have checked the FAQ and it didn't resolve my problem.

Announcement

[X] I have checked Breaking change announcement.

Minimal reproducible full config
local dein_dir = vim.fn.expand('~/.cache/dein')
local dein_core = vim.fs.joinpath(dein_dir, 'repos/github.com/Shougo/dein.vim')

if vim.fn.isdirectory(dein_core) == 0 then
  vim.system({ 'git', 'clone', 'https://github.com/Shougo/dein.vim', dein_core }):wait()
end

vim.opt.runtimepath:append(dein_core)

local dein = require('dein')

dein.begin(dein_dir)

dein.add('hrsh7th/nvim-cmp', {
  on_event = {
    'InsertEnter',
  },
  hook_post_source = function ()
    require('cmp').setup({})
  end,
})
dein.add('tversteeg/registers.nvim', {
  on_map = {
    nv = '"',
    i = '<C-r>'
  },
  hook_post_source = function ()
    require('registers').setup({})
  end
})
dein.add('hrsh7th/cmp-buffer', {
  on_source = {
    'nvim-cmp',
  },
})
-- dein.add('hrsh7th/cmp-path', {
--   on_source = {
--     'nvim-cmp',
--   },
-- })

if dein.check_install() then
  dein.install()
end

dein.end_()

Description
I make registers.nvim load (and then its window opens) when pressing <C-r> in insert mode. When pressing <C-r>,  call v:lua.cmp.utils.feedkeys.call.run(2) is inserted into a current buffer but the window isn't open. The plugin is loaded.
This issue doesn't appear using registers.nvim and nvim-cmp only. I checked to see which plugins affect this issue, it seems to be caused by using cmp-buffer or cmp-path together. In addition according to git bisect, it seems that this issue has appeared since e55033f`.
Plugins:
Shougo/dein.vim
tversteeg/registers.nvim
Steps to reproduce

Open nvim with minimal config
Start insert mode
Press <C-r>

Expected behavior
Theregisteres.nvim window opens.
Actual behavior
all v:lua.cmp.utils.feedkeys.call.run(2) is inserted into a current buffer and theregisteres.nvim window doesn't open (I don't know why it is call in the config I usually use but all in the minimal config).
Additional context
Lazy-loading when entering insert mode (InsertEnter) instead of pressing <C-r> stops this issue from appearing.

I have a similar issue I get mp.utils.feedkeys.call.run(...) inserted when scrolling the mouse wheel in insert mode on an empty buffer. With vim.o.mouse = 'nv'
Going back to a9c701fa7e12e9257b3162000e5288a75d280c28 fixes the issue, going to  e55033f makes it reappear.

I have similar issue with nvim-cmp while jumping through loclist in insert mode:
inoremap <m-up>     <c-o>:lprev<cr>
inoremap <m-down>   <c-o>:lnext<cr>

sometimes appears garbage like
(358)
(360)
.feedkeys.call.run(287)
.utils.feedkeys.call.run(289)
u.feedkeys.call.run(194)
deys.call.run(196)
ddys.call.run(199)
kdll.run(124)
deys.call.run(126)
d v:lua.cmp.utils.feedkeys.call.run(129)
lua.cmp.utils.feedkeys.call.run(61)
kddkeys.call.run(63)

More offten this happends at ends of loclist when lprev/lnext prints 'No more items'.

I found the solution here:
https://github.com/hrsh7th/nvim-cmp/issues/2033#issuecomment-2448135783


Alex build failing with missing filepath at preprocessing step

I'm not sure if it is relevant but this is on Nixos.
➜ cabal build
Build profile: -w ghc-8.10.7 -O1
In order, the following will be built (use -v for more details):
 - alex-3.2.7 (exe:alex) (first run)
Preprocessing executable 'alex' for alex-3.2.7..
alex: /home/solomon/Development/haskell/alex/./data//AlexTemplate-ghc: openFile: does not exist (No such file or directory)

That filepath looks odd. Any ideas what might be going wrong?

I can reproduce this with cabal build, however, stack build seems to work

I can confirm this problem on macOS Mojave.

Yes this is a very weird error. I think there is some logic in prior versions of alex to try to use newer templates? But those don't exist because we simplified the templating system.

BTW if you manually run alex on the file and delete the original Scan.hs, it will work. It is just when cabal invokes Alex that weird things happen!

Ah, this is because the autogenerated Paths_alex module allows alex_ env vars to override the data dirs. During the build those env vars are defined (at least with the latest Cabal), and thus we try to bootstrap feeding the old alex the new alex's templates! :facepalm:
More reason to finish https://github.com/simonmar/alex/pull/174, I suppose.

Is this still a problem? I ran cabal build and cabal test successfully on master (3.5.1).
At any rate, I happy suffered from a similar error which can be traced back to Cabal; see https://github.com/haskell/happy/issues/274#issuecomment-2152649291.

Let's close this optimistically.


⚠ Bofrost.com has degraded performance

In dc42870, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1426 ms

Resolved: Bofrost.com performance has improved in a65e4c5 after 6 minutes.


[newrelic-pixie] [newrelic-k8s-metrics-adapter] Add image pull secrets (#597)

Is this a new chart
No.
What this PR does / why we need it:
Add imagePullSecrets on deployments/jobs where it is missing.
Which issue this PR fixes

fixes #597

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [mychartname])

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Vinicius Figueiredo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Added to the Roberto's comments I would add like a .global.pullSecrets or something like that so we don't have to do it in all the charts individually.

I definitely agree but I'd suggest to leave that for a follow-up PR when we add it to all of our charts rather than just one :)

@roobre done! :)

Added a default empty list as suggested. Sorry about delay, I was sick for few days.

No prob, there are conflict because the other charts have been upgraded. Rebase or bump the version again and I will merge it as soon as possible to not stale this PR.
I don't want to abuse your patience anymore :)

Hey @viniciusfs, this is looking good from our side, if you can rebase the changes we're ready to get it merged


fixes PollEvent() hung after Fini() on windows

It seems too many unused codes are left in console_win.go, which makes this obvious problem hard to be aware of while coding.

I wonder if this is what is causing the following problem?
https://github.com/rivo/tview/issues/573

@joegrasse of course, that's why I found this problem

Thanks for finding this!


Module path and Getting Started instructions

[Related to issues #867 and #120.]
The instructions (and the Sharepoint Migration Tool) assume that the users module folder is always at $env:UserProfile\Documents\WindowsPowerShell\Modules, but this may not be the case if folder redirection is implemented (either redirected manually or through OneDrive's Backup Your Folders feature).  Ideally, the SPMT installer should respect the user's Documents user shell folder location, wherever it is located.
In the meantime, the documentation should at least note that the path in the instructions may differ if it has been redirected, or to use the full path to the module directory.

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

ID: 83229fe4-a0fc-5d45-1e32-2cf9bee9374b
Version Independent ID: ea237f69-8d65-e3c6-1c77-5f3fdfb73d34
Content: Using PowerShell cmdlets to migrate to SharePoint Online
Content Source: migration/overview-SPMT-PS-cmdlets.md
Product: sharepoint-server-itpro
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

@bryhall Thank you for pointing this out and helping improve MS Docs.  Are you suggesting having a note added to the article?

@bryhall We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

@scanum / @lindspea - Apologies, did not see the notifications for replies.  I'm not sure how to re-open this issue without creating a new one.
My recommendation is primarily that the installer respect the user's actual modules path.  However for the documentation, I think it would be helpful for others (especially if they use OneDrive's feature) to be aware of the path mismatch.


feat(auth): rework auth:login to work with coveo://

Still rough around the edges, but working ™

Will require more work to support other usage for the custom scheme


Update NodeId n event-bus subscribers

Motivation:
Hazelcast is sometimes resetting the UUID of a member.
(https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/internal/cluster/impl/ClusterServiceImpl.java#L342)
This is almost happening everytime in a container environment like Kubernetes where multiple pods with several verticles are all started and deployed at the same time.
Even after the UUID is reset, the ClusterManager (Vert.x HazelcastClusterManager) is still republishing the event-bus subscribers with the stale UUID of the member.
The problem does not immediately manifest , as the IP address of the member POD still remains the same and eventhough the Vert.x NodeSelector does a  lookup with stale UUID, the correct IP address is still returned.
Issue creeps up the moment, a member POD is restarted either due to a delete or a crash and a new member POD comes up with a new IP address and UUID.
Hazelcast is now broadcasting a member removed event with the latest member UUID(of the deleted POD) to other members but since the subs-map and node-map is not updated during the reset (earlier) , it is not getting evicted which is resulting in a huge problem with eventBus timing out mostly during a  reply as it keeps trying to reply to a member that is already gone.
Sample logs:
Service 1 (First POD)
=======
Line 144-155
jvm 1    | Members {size:1, ver:1} [
jvm 1    | 	Member [<IP_ADDRESS>]:5701 - 202d7784-d695-4d46-83ba-24541b6a2943 this
jvm 1    | ]
jvm 1    |
jvm 1    | 2022-12-16 12:12:18.265+0000 [] [vert.x-worker-thread-0] INFO  com.hazelcast.core.LifecycleService - [<IP_ADDRESS>]:5701 [nimbus-v3] [4.2.4] [<IP_ADDRESS>]:5701 is STARTED
jvm 1    | 2022-12-16 12:12:18.265+0000 [] [vert.x-worker-thread-0] INFO  i.v.s.c.h.HazelcastClusterManager - Local Member : <IP_ADDRESS>
jvm 1    | 2022-12-16 12:12:18.265+0000 [] [vert.x-worker-thread-0] INFO  i.v.s.c.h.HazelcastClusterManager - Local Member Node Id: 202d7784-d695-4d46-83ba-24541b6a2943
jvm 1    | 2022-12-16 12:12:18.295+0000 [] [vert.x-worker-thread-0] INFO  i.v.s.c.h.HazelcastClusterManager - Join complete
jvm 1    | 2022-12-16 12:12:18.296+0000 [] [vert.x-worker-thread-0] INFO  i.v.s.c.h.HazelcastClusterManager - [
jvm 1    | 2022-12-16 12:12:18.296+0000 [] [vert.x-worker-thread-0] INFO  i.v.s.c.h.HazelcastClusterManager - ]
jvm 1    | 2022-12-16 12:12:18.296+0000 [] [vert.x-worker-thread-0] INFO  i.v.s.c.h.HazelcastClusterManager - []
jvm 1    | 2022-12-16 12:12:18.356+0000 [] [vert.x-eventloop-thread-0] INFO  i.v.c.e.i.c.ClusteredEventBus - Starting EventBus with Cluster Address : <IP_ADDRESS> and nodeId :202d7784-d695-4d46-83ba-24541b6a2943
Line 374:
jvm 1    | 2022-12-16 12:17:13.071+0000 [] [hz.happy_borg.cached.thread-8] WARN  c.h.internal.cluster.ClusterService - [<IP_ADDRESS>]:5701 [nimbus-v3] [4.2.4] Resetting local member UUID. Previous: 202d7784-d695-4d46-83ba-24541b6a2943, new: e0a23b31-e32c-4ad1-9acc-d43d76c0dd01
Line 1077:
jvm 1    | 2022-12-16 12:17:20.227+0000 [] [vert.x-worker-thread-2] INFO  i.v.s.c.hazelcast.impl.SubsMapHelper - republishOwnSubs::
jvm 1    | 2022-12-16 12:17:20.227+0000 [] [vert.x-worker-thread-2] INFO  i.v.s.c.hazelcast.impl.SubsMapHelper - republish for adress: 202d7784-d695-4d46-83ba-24541b6a2943
After this POD is deleted:
Service 2 (2nd POD)
=====================
Line 5206 - 5216:
jvm 1    | 2022-12-16 12:26:54.853+0000 [] [hz.sharp_wilson.priority-generic-operation.thread-0] DEBUG c.h.i.p.InternalPartitionService - [<IP_ADDRESS>]:5701 [nimbus-v3] [4.2.4] Removing Member [<IP_ADDRESS>]:5701 - e0a23b31-e32c-4ad1-9acc-d43d76c0dd01
jvm 1    | 2022-12-16 12:26:54.854+0000 [] [hz.sharp_wilson.priority-generic-operation.thread-0] INFO  c.h.internal.cluster.ClusterService - [<IP_ADDRESS>]:5701 [nimbus-v3] [4.2.4]
jvm 1    |
jvm 1    | Members {size:3, ver:5} [
jvm 1    | 	Member [<IP_ADDRESS>]:5701 - b12a46d5-1572-4bd3-afff-1e9915b27662
jvm 1    | 	Member [<IP_ADDRESS>]:5701 - d99db539-c9be-4aaf-a813-5e303c63fc5c this
jvm 1    | 	Member [<IP_ADDRESS>]:5701 - 9b4a6841-ceff-494c-a358-dcca647938de
jvm 1    | ]
jvm 1    |
jvm 1    | 2022-12-16 12:26:54.854+0000 [] [hz.sharp_wilson.event-3] INFO  i.v.s.c.h.HazelcastClusterManager - New HZ Members removed event: [e0a23b31-e32c-4ad1-9acc-d43d76c0dd01]
jvm 1    | 2022-12-16 12:26:54.856+0000 [] [hz.sharp_wilson.cached.thread-5] INFO  c.h.i.server.tcp.TcpServerConnector - [<IP_ADDRESS>]:5701 [nimbus-v3] [4.2.4] Could not connect to: /<IP_ADDRESS>:5701. Reason: IOException[Connect timed out to address /<IP_ADDRESS>:5701]
Conformance:
Your commits should be signed and you should have signed the Eclipse Contributor Agreement as explained in https://github.com/eclipse/vert.x/blob/master/CONTRIBUTING.md
Please also make sure you adhere to the code style guidelines: https://github.com/vert-x3/wiki/wiki/Vert.x-code-style-guidelines

Thank you for the PR. We actually had a similar issue reported against 3.9, and we lost the fix when rebuilding the CM for Vert.x 4.
I am going to reintegrate the fix in master and close this one. Thank you

Thank you so much. I can confirm that this issue did not occur in 3.9


Model Updaging Event Closure is not triggering when ->save() is called.

Laravel Version: 8.13.0
PHP Version: 7.4.11
Database Driver & Version: PHP PDO & MySQL 5.7.32

Description:
When doing an update on a model you'll use ->save() method to update it.
so I have this code on my UserController@update method
$user = $this->user->findOrFail($id);
$user->fill($request->all());
$user->save();

I have this on my User Model
/**
 * The "booted" method of the model.
 *
 * @return void
 */
protected static function booted()
{
    static::updating(function ($user) {
        # Some code here setting default values when updating
        $user->name = 'Test Name';
    });
}

Steps To Reproduce:

Create new fresh laravel app using laravel new project-name command
Create a UserController by running php artisan make:controller UserController --resource and then register it on your router
Then add the booted code to your User Model.
Try setting your default name value on the static::updating method.
Then try updating a single model and checked on the value if it reflected.

Other Details
static::creating is being triggered fine, but static::updating is not

@skeeith I've tried your code and it is working fine without any problem.
After calling the save() method for update, the user->name is Test Name.
Also the issue's title and description aren't same! (title says deleting not working and in the description you're talking about updating).

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

@khalilst thanks for verifying this man, it looks just specific to my project, also the model is not actually User but a different one. I created a new v8 project and it does work fine, maybe there's just something wrong with my project. good to know you verified it.
Thanks!

@driesvints I found the issue when updating a certain Model and it didn't have any changes (which is expected behavior for me) on the fields, the Model::updating event isn't being triggered. it's being triggered ONLY WHEN there's really a change on a single field.
The problem here is when you're dealing with  or probably radio types (I haven't tried it on radio) when you tick off/turn off/unchecked an input checkbox it doesn't send a key: value pair on the request BUT this should be considered as off behavior.
This is ON
checkbox_field_name: 'on',
...other fields

This is OFF
...other fields

Now, whether there aren't any changes, the Model::updating event SHOULD TRIGGER but the problem is it doesn't.


Piglin eating weirdly if they have a weapon in their left hand

I don't even know if this is fixable, it's funny anyway

will look into this lol

@leyxcx Is this issue still present in later versions, and/or the version you play on?


Export excel missing one column

I am trying to export but one column is missing. That column is of type List. I tried to handle it like this
columns.Insert(6, new SlickColumn
{
Field = TokenRow.Fields.ChallanList.Length.ToString(),
Title = "Challans",
            Format = ctx =>
            {
                var item = (TokenRow)ctx.Item;
                if (item.ChallanList != null)
                    return "" + item.ChallanList.Count + "";
                return "N/A";
            },
            Width = 70,
        });

But still function getColumns in serenity is not considering it and for some reason still getting null.
Please advice

Excel export uses column list you define at server side. So it is not possible to use dynamic columns.


Request: Options to build without minification & sourcemap generation

Title says it all. dist-it makes debugging shipped libs damn near impossibru without options to skip minification, and/or without sourcemaps.

I'm for it! There could be an option like --no-minify or so. Contributions are welcome! :four_leaf_clover:

In the latest version this is possible.
See the help output: https://github.com/IonicaBizau/dist-it#cloud-installation


Linting

Hi guys, I am confused on :
If we are using both pylint and flake8?
any details on this will be appreciated.

I think we are supposed to use any one of it.

Yeah, we used pylint. You can check out work in hw4g1


Ability to ssh to github actions runnner.

ssh via tmate will close the VM, if UT's fail. so put a sleep instead and build manually.

makes sense; how is it used?
In actions, there is a tab for Setup tmate session which gives details about the ssh connection.


migrate python tools in the codebase

nilearn now has all the core methods to automatically generate a small brainsprite viewer from python in one line. But this is not suitable for more advanced use case, e.g. build dashboards featuring multiple viewers. There needs to be tools to:

generate sprites
generate brainsprite snipets, with support for all brainsprite options.

Because the python part of the project is going to remain very simple, there is no need for a separate project, and the python code should simply be merged in the codebase.

Update: would be better to improve the API in nilearn, and leave brainsprite as pure js. Brainsprite documentation would explain how to use private nilearn method for sprite generation & advanced use case, but there would be no python code in brainsprite per say.


[NOD-555] Added linters and tests to Dockerfiles

Rebuild after update in master

Rebuild after update in master

Rebuild after update in master

Rebuild after update in master


Error when calling browserSupportsWebAuthnAutofill() if navigator.credentials is not defined

I suggest changing the code to be more defensive
    if (navigator?.credentials?.conditionalMediationSupported) {

Good callout, thanks @sameh-amwal. That line is actually supporting old conditional UI logic in Chrome Canary. As of Chrome Canary 109 the isConditionalMediationAvailable() flag is the correct one, so I can probably finally remove the lines that're causing the issue here:
https://github.com/MasterKale/SimpleWebAuthn/blob/master/packages/browser/src/helpers/browserSupportsWebAuthnAutofill.ts#L11-L13

Good callout, thanks @sameh-amwal. That line is actually supporting old conditional UI logic in Chrome Canary. As of Chrome Canary 109 the isConditionalMediationAvailable() flag is the correct one, so I can probably finally remove the lines that're causing the issue here:
https://github.com/MasterKale/SimpleWebAuthn/blob/master/packages/browser/src/helpers/browserSupportsWebAuthnAutofill.ts#L11-L13

Nice. I like easy fixes 😊

Another issue worth mentioning. isConditionalMediationAvailable() returns true for chrome and firefox on the iPhone which both don't support however resulting in unexpected behavior for code that depends on it.

Another issue worth mentioning. isConditionalMediationAvailable() returns true for chrome and firefox on the iPhone which both don't support however resulting in unexpected behavior for code that depends on it.

Hmm, there's not much I can do at the library level to account for a browser lying about its support of WebAuthn. Something like this, per-browser quirks for a given OS, would be worth documenting on a site like passkeys.dev, but as for this project, I'd rather not try to expand this to try to do OS and browser detection to guess when the API is actually available...

makes sense. thanks for the info about passkeys.dev. Cool resource!

@sameh-amwal This should be fixed in<EMAIL_ADDRESS>