Issues with the logger cast

Environment
MacOSX
Liquibase Version:
4.1.0
Liquibase Integration & Version: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.>
org.liquibase:liquibase-core:4.1.0
org.liquibase.ext:liquibase-hibernate5:4.1.0
Liquibase Extension(s) & Version:
Database Vendor & Version:
Operating System Type & Version:
MacOSX Catalina
10.15.6
Description
Trying to implement a gradle task for the diffChangeLog liquibase's command line command.
My dependencies:
    implementation("org.liquibase:liquibase-core:4.1.0")
    implementation("org.liquibase.ext:liquibase-hibernate5:4.1.0")
    runtimeOnly("com.mattbertolini:liquibase-slf4j:4.0.0")

The task
tasks.register<JavaExec>("liquibaseDiffChangelog") {
    description = "Runs Liquidbase diff between schema and current changeSet"
    group = "liquibase"
    classpath = sourceSets["main"].runtimeClasspath + configurations["liquidbase"]
    main = "liquibase.integration.commandline.Main"

    args("--changeLogFile=" + project.projectDir.toString() + "/src/main/resources/changelog-changesets.xml")
    args("--referenceUrl=hibernate:spring:**redacted**?dialect=org.hibernate.dialect.MySQL57Dialect")
    args("--username=sa")
    args("--password=sa")
    args("--url=jdbc:mysql://localhost:3306/**redacted**?useSSL=false&nullNamePatternMatchesAll=true")
    args("--driver=com.mysql.cj.jdbc.Driver")
    args("diffChangeLog")
}

it gives me
▶ ./gradlew liquibaseDiffChangelog

> Task :liquibaseDiffChangelog FAILED
16:38:12,437 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
16:38:12,438 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
16:38:12,439 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/**redacted**/build/resources/main/logback.xml]
16:38:12,553 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding LoggerContextListener of type [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack
16:38:12,554 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@7c7b252e - Propagating DEBUG level on Logger[ROOT] onto the JUL framework
16:38:12,554 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting LoggerContextListener
16:38:12,556 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
16:38:12,558 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
16:38:12,563 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
16:38:12,817 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.AsyncAppender]
16:38:12,819 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ASYNC]
16:38:12,819 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to ch.qos.logback.classic.AsyncAppender[ASYNC]
16:38:12,819 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNC] - Attaching appender named [STDOUT] to AsyncAppender.
16:38:12,819 |-INFO in ch.qos.logback.classic.AsyncAppender[ASYNC] - Setting discardingThreshold to 51
16:38:12,820 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [liquibase] to INFO
16:38:12,821 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@7c7b252e - Propagating INFO level on Logger[liquibase] onto the JUL framework
16:38:12,821 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.fieldlens] to DEBUG
16:38:12,821 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@7c7b252e - Propagating DEBUG level on Logger[com.fieldlens] onto the JUL framework
16:38:12,821 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.wework.costmanagement] to INFO
16:38:12,821 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@7c7b252e - Propagating INFO level on Logger[com.wework.costmanagement] onto the JUL framework
16:38:12,821 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
16:38:12,821 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@7c7b252e - Propagating INFO level on Logger[ROOT] onto the JUL framework
16:38:12,821 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ASYNC] to Logger[ROOT]
16:38:12,821 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
16:38:12,822 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@64e7619d - Registering current configuration as safe fallback point
Unexpected error running Liquibase: class com.mattbertolini.liquibase.logging.slf4j.Slf4jLogService cannot be cast to class liquibase.logging.core.JavaLogService (com.mattbertolini.liquibase.logging.slf4j.Slf4jLogService and liquibase.logging.core.JavaLogService are in unnamed module of loader 'app')
For more information, please use the --logLevel flag
2020-10-13 16:38:12.850 [main   ] ERROR l.integration.commandline.Main$1 - Unexpected error running Liquibase: class com.mattbertolini.liquibase.logging.slf4j.Slf4jLogService cannot be cast to class liquibase.logging.core.JavaLogService (com.mattbertolini.liquibase.logging.slf4j.Slf4jLogService and liquibase.logging.core.JavaLogService are in unnamed module of loader 'app')
java.lang.ClassCastException: class com.mattbertolini.liquibase.logging.slf4j.Slf4jLogService cannot be cast to class liquibase.logging.core.JavaLogService (com.mattbertolini.liquibase.logging.slf4j.Slf4jLogService and liquibase.logging.core.JavaLogService are in unnamed module of loader 'app')
        at liquibase.integration.commandline.Main$1.run(Main.java:276)
        at liquibase.integration.commandline.Main$1.run(Main.java:193)
        at liquibase.Scope.child(Scope.java:169)
        at liquibase.Scope.child(Scope.java:145)
        at liquibase.integration.commandline.Main.run(Main.java:193)
        at liquibase.integration.commandline.Main.main(Main.java:156)

Any recommendations?
Steps To Reproduce
List the steps to reproduce the behavior.

Please be precise and ensure private information is redacted
Include things like

Files used - sql scripts, changelog file(s), property file(s), config files, POM Files
Exact commands used - CLI, maven, gradle, spring boot, servlet, etc.

Actual Behavior
A clear and concise description of what happens in the software before this pull request.

Include console output if relevant
Include log files if available.

Expected/Desired Behavior
A clear and concise description of what happens in the software after this pull request.
Screenshots (if appropriate)
If applicable, add screenshots to help explain your problem.
Additional Context
I've submitted the issue here - https://github.com/mattbertolini/liquibase-slf4j/issues/11
Reply from @mattbertolini -
Thanks for the info! Sadly I did encounter this in my testing. It seems the the Liquibase CLI is expecting the default LogService implementation (the default being JavaLogService) to be returned in all cases. Here's the area of the code where that happens:
https://github.com/liquibase/liquibase/blob/ef986f4f7cef26c2c9e22c6265d5f1f014302e20/liquibase-core/src/main/java/liquibase/integration/commandline/Main.java#L272-L277
I'm not sure if that is a bug on their part or a deliberate design decision. Based on the code around it, it looks deliberate. I guess they are expecting people to use standard out and the default Java logger does that just fine.
I would suggest opening an issue with Liquibase on this. There's no workaround I can do from my side. They will need to stop casting to a concrete type. If Liquibase doesn't or won't fix this, another way of avoiding the problem is to not use this library but rather bridge java.util.logging to SLF4J. I hope this information helps. Let me know if you have any other questions.
┆Issue is synchronized with this Jira Bug by Unito

Hi @PavelSusloparov Thanks for bringing this issue to our attention.  We will add it to the list of issues that we are processing.

@molivasdat hello, I'm looking at the code, and seems It'll be ok to use an interface instead of casting to implementation and seems setting parent to the logService from the current scope is not required at this part of the code.
Could you assign me to this task, I'm in the testing stage now and I believe I would make a PR today?

Hi @EEM86 Thanks for helping.  I have assigned you this issue.

This was changed at some point. In 4.15.0, the code is correctly handling different Logger implementation.
Closing this as "stale"


Allow joins on regions that are within a threshold (instead of requiring overlap)

In order to comply with BedTools requirements, we need an option to join on data that fits some threshold.

+1! We used to have something like this, actually. There are myriad ways to do this, but IMO the simplest way is to increase the width of the reference region keys on one side of the join. Not sure if you had an alternative approach in mind; this is but one approach out of many...

I've given this some thought and I believe that using the ReferenceRegion.distance() is the best way to go about it. In my cleanup of ReferenceRegion.scala I am adding an isNearby() method that takes a threshold. This can completely replace the overlaps calls in all cases.


Impossible to import the library in Xcode using CocoaPods

For more information, please consult the screenshots below:
In Xcode imported pods list:

In Xcode source code:

Podfile:

Thank you in advance for keeping me updated on the fixing of this bug.

It's FontAwesome_swift, not FontAwesome.swift. CocoaPods changes dot to underscore in framework name.

Thank you for the answer, problem fixed.


upgrade sonatype from 2.x to 3.x before April 1st

Our Sonatype nexus repository license will expire on April 1st. We need to upgrade our instance before then by following this guide
https://help.sonatype.com/repomanager3/installation-and-upgrades/upgrading-from-nexus-repository-manager-2?utm_term=&utm_campaign=NA+|+SouthEast+|+ABM+|+Generic+|+Repository&utm_source=google&utm_medium=cpc&hsa_tgt=dsa-1834004784646&hsa_grp=146043118952&hsa_src=g&hsa_net=adwords&hsa_mt=&hsa_ver=3&hsa_ad=646018512623&hsa_acc=2665806879&hsa_kw=&hsa_cam=18328993905&gclid=CjwKCAiAuOieBhAIEiwAgjCvciXM3Ri1_EE1pVdhjiGMkLekF4m8VFGXjiD-g02NXV-dWodIhrQ7eBoCGDwQAvD_BwE

It looks like we don't have to any upgrading with the OSS version of sonatype as per this Jira ticket
https://issues.sonatype.org/browse/OSSRH-65300


Support reading of device profiles.

Now it is possible to support other modbus devices by adding a device profile in profiles folder and include the profile name in the config file.

@nagydavid will you please review the changes and eventually test if possible. Thanks.


Pagination machination

Ticket: []
Feature flag: n/a

Purpose

Fix issues with pagination

Summary of Changes

Prevent the "First" button from showing up when we are already on the first page
Reset page param when we change sort or add/remove filters

Screenshot(s)
Side Effects

QA Notes

Funniest PR name since Draft Nodes were Daft Nodes.


【𝕏𝚆𝙰𝚃𝙲𝙷:⊱ᐯIᗪEO𝚂】Oviya Helen Breaks Silence on MMS Video Controversy ʟᴇᴀᴋᴇᴅ 𝙻𝚒𝚗𝚔 On Social Media 𝕏𝘛𝘸𝘪𝘵𝘵𝘦𝘳 【ＸＸＸ HKJ7B8】 #25 #2260

24 sec ago
🟢 ➤🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
🟢 ➤🌐 Click Here To link (Full Viral Video Link)
Social media has been buzzing with rumors surrounding a private video allegedly featuring actress Oviyaa. Several users are circulating screenshots they claim are from the video, igniting widespread speculation and discussion across platforms.
However, many believe that the video might be a deepfake—a digitally manipulated video designed to deceive. Oviyaa has not yet commented or issued any statement regarding the rumors. Some netizens have also shared intimate scenes from her Tamil movie “90 ML,” further adding to the confusion. Fans of the actress are urging others not to spread or share the video.
This incident mirrors a similar situation involving Bollywood actress Urvashi Rautela a few months ago. A video, purported to be a private clip, turned out to be a scene from her film Ghuspaithiye. Responding to the misunderstanding, Rautela expressed her initial distress but clarified that it was not a personal video, emphasizing that no woman should have to go through such an ordeal.
Oviyaa, known for her work in Tamil and Malayalam cinema, gained recognition with the romantic comedy Kalavani (2010) and followed it with notable roles in films like Marina (2012) and Moodar Koodam (2013). She also appeared in the hit horror-comedy Yaamirukka Bayamey (2014). Oviyaa became widely popular after participating in the first season of Bigg Boss Tamil in 2017, where she earned a large fanbase despite leaving the show early.
As the controversy unfolds, her supporters continue to appeal for caution and empathy, asking people to avoid sharing unverified or sensitive content.
Oviya reacts to the private video leak; Says, 'Next time bro'
Oviya Leaked Trends On Social Media Amid Her Private Video Goes Viral
Oviya Video Oviya Leaked Video Oviya priva...
Oviya Video Oviya Leaked Video Oviya private video Oviya MMS Bigg Boss Tamil fame Oviya · devafcee. Astronaut · 3m ago in. Galaxy S24.
Private Videos Leaked? Actress Says 'Enjoy'
This social media user commented “A 17-second video of you has leaked madam” and Oviya replied “Enjoy”. She even reacted to a couple of ...
Oviya's Shocking Reply To Private Video Leaked Issue ...
oviya''s latest video has taken social media by storm, captivating viewers and sparking widespread discussions. This young digital creator has garnered ...
+SEX MMS clip Oviya private video leaked ? Social media ...
SEX MMS clip Oviya private video leaked ? Social media abuzz with rumours actress, Posts: 0, Last Post: Oct 12, 2024 - 6:40 PM ...
ZWATCH.VIDEOS Oviya Leaked Video On Social Media X ...
VIDEOS Oviya Leaked Video On Social Media X Twitter

bvbv

cvbcv


reload option in transitionTo reloads all states in a hierarchy. Unable to reload just the current nested state.

When using the reload option in state.transitionTo on a nested state, all of its parents are also reloaded. You should be able to reload only the current state.
My use case is a nested state with params. In some cases I have the same state and params and I simply wish to reload it (to refresh data from the server), however using the reload option also reloads it's parents, which resets templates and directives in parent states.
One workaround I found is to have some kind of random param in the nested state which is changed every time you wish to reload/refresh the current state. UI-Router seems to handle the case fine when a state has unique params every time, it just cannot reload a state with the exact same params since it believes there is no work to do.
Here is what happens:

Nested state, no changes to params =  UI router does nothing, since it assumes it is already on the correct state
Nested state, with an additional unique param assigned to a random value to uniquely identify every transitionTo call = works correctly, able to "refresh" nested states without reloading parents
using the reload option, refreshes the nested state correctly but also reloads all parents

I can setup a plunk, I just wanted to see if this is worthwhile first.

I have a similar problem with the reload. I use resolves to update data in my state's controller.(when it's an active state)
I use the params work-around above, it does reload the resolves, but doesn't reinitialize the controller, the injected resolve is not updated. I also tried transition with options
{ reload: true, inherit: false, notify: true } which didn't work neither.

The ability to set the descendant depth of the reload is an excellent idea.

We implemented this feature for a private project.
PR was created: https://github.com/angular-ui/ui-router/pull/1795
Welcome to try it..

I think this makes sense from a high level.  I'd to omit the second reloadState parameter, and overload the existing reload parameter.

{ reload: true }// reloads all,
`{ reload: 'foo.bar' } // reloads top.bar, and any children
`{ reload: stateObj } // reloads state found in stateObj, and any children

Squash your commits and set your commit message to match the contributor guidelines.  If @nateabele concurs, I think we'll merge this in.

Created a new PR according to your comments: https://github.com/angular-ui/ui-router/pull/1809

Fixed in #1809.

+1 Was looking this since long back. Thank you.

Can reload accept a list of states to reload?
Or it is too much to ask?
{ reload: ['foo.bar','foo.bar.car.jar'] }

@dumbojet that doesn't make any sense since reloading a parent state reloads the descendents


[AutoPR resources/resource-manager] Renaming CreateGroupRequest to CreateManagementGroupRequest

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2456

Codecov Report

Merging #1943 into restapi_auto_resources/resource-manager will not change coverage.
The diff coverage is 28.57%.

@@                           Coverage Diff                            @@
##           restapi_auto_resources/resource-manager    #1943   +/-   ##
========================================================================
  Coverage                                    53.16%   53.16%
========================================================================
  Files                                         4724     4724
  Lines                                       117205   117205
========================================================================
  Hits                                         62316    62316
  Misses                                       54889    54889

Impacted Files
Coverage Δ

...tgroups/operations/management_groups_operations.py
9.32% <0%> (ø)
:arrow_up:

.../mgmt/resource/managementgroups/models/__init__.py
100% <100%> (ø)
:arrow_up:

...ntgroups/models/create_management_group_request.py
57.14% <50%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d4cb715...01250dd. Read the comment docs.

Will not been merged in resouces finally.


Fix check mode issue #20 (https://github.com/trondhindenes/Ansible-wi…

…n_dsc/issues/20)

Based check mode evaluation on results of Get-AnsibleParams rather than a property of $params
Slightly re-ordered opening block so that updated code is preceded by comment about params being a hashtable
Removed conditional check that set the $CheckFlag variable

This has been manually tested against an Ansible 2.3 stable instance. Please let me know if there are specific tests you would like carried out ahead of any potential merge?

Thanks for this! I'm away from my computer atm, but I'll get this verified/merged as soon as I can.


skipProperties - what is the proper usage?

Hi, skipProperties says it takes a list but there is no example and I couldn't find this anywhere in the cli code. How do we use this option on the CLI? Thanks!

The way is:
cleancss -O2 skipProperties:list-style,transition path/to/input.css

All properties come as comma separated list.


Confusion about the Training Process.

Thank you for your outstanding work.
I am truly inspired by reading your papers. However I have some confusion about the training process.
The paper says that the tasks are trained sequentially, but combining the code, I found that the training of the model aiming at loss of $L_{Baseline}$ is separate from the training of the model aiming at loss of $L_{past}$ and $L_{current}$.
Simply put, if I want to run a 5-step experiment on the dataset CIDAR-10. I need to execute the ./MSc-iNCD/scripts_our_direct_concat/cifar10_s5/01234_cifar10_s5_direct_concat.sh file first to get the five model .pth files, and then only after that I can execute the ./MSc-iNCD/scripts_our_teacher_student/cifar10_s5/s1234_cifar10_s5_teacher_student.sh to get the final result. In other words, five incremental discovery steps need to run the model training process nine times to get the results in the paper, is that correct?
Looking forward to your answer.

I see, , though the code is written so strangely.


Feature - Make jmeter.exit.check.pause configurable

jmeter.exit.check.pause is currently set to a static 2 second wait.  This should be configurable, options are:

Read the value from jmeter.properties
Set it in the POM

I've done a basic implementation of this, but after thinking about it a bit more I think we should probably use the value set in jmeter.properties.
If we go the POM route the code is going to be a lot messier.
We can already set it in the POM by overriding it using the existing properties override mechanism, adding another field to the POM would mean we have three places to check and synchronise up and I don't think it's worth the hassle.  This is going to require some rewrite to the properties code anyway.

This is now automatically set based upon the value in the final jmeter.properties file used by the plugin.
We always set to the value in the properties file + 500ms to ensure JMeter has had a chance to process thread cleanup.


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
The current version <IP_ADDRESS> installs <IP_ADDRESS>.  If you look at the manifest that was approved in #116943
It is the same as <IP_ADDRESS> with the old url, release date, and I assume product code, hash.
Steps to reproduce
Install <IP_ADDRESS>
winget install --exact --id RicoSuter.NSwagStudio --version <IP_ADDRESS>
Notice the download url, it's downloading 13.19.0
Also check the installed version via:
winget list --exact --id RicoSuter.NSwagStudio
Actual behavior
Installs 13.19.0
Expected behavior
Install 13.20.0
Environment
Windows Package Manager v1.5.2201
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.3324
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.20.2201.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Enabled
LocalArchiveMalwareScanOverride           Disabled

Screenshots and Logs

Thanks for reporting, I have tried again #118172

This appears to be complete.


refactor(state): reuse method proposalIsTimely

Small refactor to simplify the calls to "is timely"

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments
[x] Title follows the Conventional Commits spec

Shouldn't this go to v1 too?

Shouldn't this go to v1 too?

It's just a small refactor. I don't think it's worth the hassle


WIP. ResourcePoolImpl Propbe implementation

@e0ne any plan to rebase this PR?

@zshi-redhat I'm going to rebase and finish the implementation soon

closing this one for now. @e0ne  please reopen if you intend to resume working on it


React Native example in README

React Gateway works just fine in React Native. There is just one catch: component prop of <GatewayDest> must have React Native component like View.
It would be nice to have this mentioned in README so others don't have to wonder whether it will work or not.
Thanks for creating and maintaining react-gateway, works like a charm!

LGTM.

thank you @vlki


Check for default exposes

For things from the prelude (https://package.elm-lang.org/packages/elm/core/latest/), it's not useful to specify things like List.List, Maybe.Maybe or String.String in type annotations.

See #12 for resolution.


(FACT-1623) Implement load average resolver for AIX

This uses the getkerninfo system call to get the current load
averages. AIX's uptime command also uses the same system call
to obtain this information.

On an AIX 7.1 VM:
[0] [AIX] root@aix71-4:~ # /opt/puppetlabs/puppet/bin/facter --query load_averages && uptime
{
  15m => 0.907669,
  1m => 1.0027,
  5m => 0.916275
}
  11:12PM   up 2 days,  13:52,  3 users,  load average: 1.00, 0.92, 0.91

You can see that the values match the uptime command.
Should I have an acceptance test here? We can use uptime to compare the values. I didn't add one here b/c I couldn't see one for the glib resolver that the other platforms use.

CLA signed by all contributors.

@caseywilliams Agreed. I spent a while sifting through their docs trying to figure that out and I couldn't find anything. @branan Do you happen to know?

I have no idea what the last arg is. Everything I know about getkerninfo is captured in the comment in the network resolver


Add expanded links caching

This adds caching for the expanded links endpoint. It is unfortunately needed since the /world taxon is huge and takes about 20s to build. A more permanent solution is hopefully forthcoming via https://trello.com/c/mOdpAGVj.

Wrote up why this is a bad solution on the Trello: https://trello.com/c/mOdpAGVj/961-improve-performance-of-the-expanded-link-set-endpoint-3#comment-59523f83cd2c7225e9fc9e62


vkCreateImage valid usage checks / tests

Adds 18 valid usage checks to vkCreateImage(), with about 2/3 of those in core validation and the rest in parameter validation.  Includes a pretty much full-body refactoring of PreCallValidateCreateImage() in buffer_validation.cpp.
Fixed some existing tests that tripped the new VUs, and modified them to use VUID-based error matching instead of string matching.
Added a new test to exercise all the new VUs that weren't otherwise being tested.

Appveyor is stuck, but PR is passing on Travis and local CI.  Pushing.


[Documentation] Add unit testing section

Changing a native ChoiceType to an autocomplete field, using Symfony-UX/autocomplete, might cause unit tests for forms to fail.
It needs to register the right TypeExtensions to make it work correctly.

Q
A

Bug fix?
no

New feature?
no

License
MIT

Thanks Alexandre!


Using the Github API instead of a local git repository

If you want to use this tool you either specify a local git repository at compile time or it will always clone a bare repository on every cargo-bisect-rustc run.
This is somewhat inconvenient and using the Github API is something one could do instead.
What are your thoughts about it? I'd like to implement it, maybe as a flag (--no-local-git-repo-is-available-so-use-github-instead-plz)

If we can reliably use the GitHub API (without, e.g., hitting rate limits) then I would love to do that by default (with perhaps a flag to fallback to local git repo). Happy to accept a PR!

:+1: to this idea too.

I have a prototype of this that I need to rebase.


No notifications from RocketChat

no notifications via app or mail
independent of mail provider

In General, the E-Mail sending & push notifications settings are correct. So might need to check the (default?) notification settings of rooms etc.

-Weird, because there are also no notifications for private messages. Is this something RocketChat admins can/should check?

Possibly (don't know the Rocket.Chat Admin panel too well). Either some problem with our notification configuration or some bug in Rocket.Chat (didn't see one in the Rocket.Chat repo though)

Notifications seems to work again. I got notifications by email and app today for a message where I was pinged and also in sparkpost I see notification emails send again. Thus I close this issue.
@yolo-bird Reopen it, if it is necessary or write us in #meta-dev


error: debug failure. false expression

Current behavior
Gets error: debug failure. false expression and the type errors are not caught in runtime
Expected behavior
No error and type errors should be caught
Steps to reproduce the issue
npm run dev
Issue reproduction repository
https://stackblitz.com/edit/webpack-webpack-js-org-sdj2xg?file=package.json
Environment

fork-ts-checker-webpack-plugin: 8.0.0
typescript: 5.0.2
eslint: 8.36.0
webpack: 5.76.2
os: windows 10

works fine until typescript 4.9.5

Is it possible this error is in ts-loader and not fork-ts-checker in your case? I'm seeing the same thing over there: https://github.com/TypeStrong/ts-loader/issues/1604

I don't think so. I am not using ts-loader in my project.


Allow filtering workers by hostname, name or even by configuration/queues

Right now we don't have any filters for workers. With a few hundreds of workers, finding the ones you want becomes a bit tricky, and more so if we add #28. It'd be nice to filter them just like we filter jobs.

I'd like to work on this issue.

hi, is anyone currently working on this? if not, I would like to give it a try :)

Still me! I was waiting for https://github.com/basecamp/mission_control-jobs/issues/28 and then got busy. Hoping to have a PR done this weekend.

sure no problem

hey! anyone currently working on this issue? Looks like a good one to get started on this project and I would love to give it a try

I've unassigned myself, life got in the way of this unfortunately.

🙁 sorry to hear that. I can take a look at it throughout this week, I should get something ready to review by the weekend

hi @matiassalles99, I took de liberty to open a PR draft since I did some work with jobs filters and this was pretty similar

ohh sorry @matiassalles99, you can go ahead if submit yours

@Xeitor nah it's fine don't worry, I can take a look at another issue 💪


Error messages

@FinnStutzenstein I think the service is ready now. There is nothing else I plan to do. I am sure you find a lot of bugs and that you have suggestions for changes. I wait for you issues.


@EqualsAndHashCode sub-property

Is it possible to supply @EqualsAndHashCode with subproperty?
e.g.
@EqualsAndHashCode(of = "currentProperty.subProperty")

AFAIK no, and I can't remember such a request. I guess, my proposal would help: #1393.
@EqualsAndHashCode.Exclude
private Whatever currentProperty;

@EqualsAndHashCode.Include
private Whatever2 subprop() {
    return currentProperty.subProperty;
}

It's rather verbose, but pretty general. If you like it, please vote for it (by using the smiley icon, not by posting +1!).

Via annotate-inclusion-on-methods you can add this behaviour. We're working on that: Working on it: https://github.com/rzwitserloot/lombok/wiki/FEATURE-IDEA:-Annotation-based-Include-Exclude-for-ToString,-EqualsAHC,-etc


UBIKA WAF detection

Is it possible to add  UBIKA to the coverage of this tool?

I believe Ubika is the renovated version of DenyAll (for which we already have detection for). Not sure if much has changed in terms of fingerprints. If you have an instance of such a WAF running you can provide it to us to speed up the addition of the WAF. Feel free to DM me on twitter if the instance cannot be shared publicly. :)

closing this as no updates, feel free to reopen!


multiarch startup error: ${ftbInstallMarker}: ambiguous redirect

Relevant portion of the logs:
=================  FORGE INSTALL ENDS  =================

Pack install Finished.

/start-deployFTBA: line 53: ${ftbInstallMarker}: ambiguous redirect

Seems to have been introduced in f97b3bf82e2b116910c3f3e1d25d05bb8130d1ad as I encountered this error immediately after docker recreated the container with the updated image pushed ~30 min ago.

I reverted that commit locally, but since the last run had ftbInstallMarker undefined, the startup script deleted the server and attempted to reinstall it.
So then with the commit reverted, the server failed to come up with: ERROR unable to locate the installed forge server jar. I had to also delete the marker file and let the server be reinstalled.

oof unfortunately the script had also wiped out a bunch of metadata (namely the config directory). I would suggest pulling that image since it's going to cause data loss for some folks.
I would highly recommend the unofficial bash strict mode as a way to catch these sort of errors. A reference to an undefined variable would've been a hard error.

I have reverted the commit and new images are building.

Strange I already had set -e, but maybe this issue still happened since curl downloaded a partial file. I'm just going to leave the scripts alone for now since the original motivation got resolved externallly.

Thanks Geoff!
For completeness: set -e causes bash to abort after the first non-zero return code. set -u would have been helpful here since the variable ftbInstallMarker was undeclared. I think it was a mistake in your commit that the variable was deleted.


Filesize limitations

Hello,
I am trying to use alphafold for my predictions and I would like to understand the difference between the full-size and reduced databases "reduced_dbs" and if the accuracy of the structural prediction is influenced by this choice? This is relevant for the next questions.
If using the reduced database leads to potentially less accurate predictions for some proteins, it would make sense to use the full database. However, in such case I cannot copy files larger than 1TB to my scratch partition, which means I cannot use bfd_metaclust_clu_complete_id30_c90_final_seq.sorted_opt_a3m.ffdata. Is there a way to split this file (and associated bfd_metaclust_clu_complete_id30_c90_final_seq.sorted_opt_a3m.ffindex) in two parts? If yes, is there a way to have alphafold read the two parts in order to circumvent the filesize limitation?
Thank you for your support,
Fabio

Hi, I'm not sure that it is possible to split HHblits database files - this would be a question for the hh-suite authors.
The structural predictions achieved using the reduced_dbs setting were found to be less accurate when tried on large datasets, but they are still very high accuracy - I would recommend using this.


TraceControl: Add module name to trace

Forward-port of https://github.com/rdkcentral/rdkservices/pull/3555. See PR for details
Current implementation of the TraceControl plugin won't output the origin of the trace.
With this commit, the resulting log message will have the for: []:[]:[file-name:line-number] :
This would allow for easier handling of log messages in a scenario where multiple plugins have their tracing flag enabled at the same time.
To capture syslog messages for a given plugin, use journalctl |grep <module-name>.

Need to update changelog and versioning - https://github.com/rdkcentral/RDKServices#versioning

Merged as part of https://github.com/rdkcentral/rdkservices/pull/3831


Add removal date for sample registration

As discused on Slack, this page had the initial warning added in July/August
2019, and no one has contacted us to say they use it. This commit establishes
a removal date of 01/02/2021, at which point the form will automatically
disappear. I am preparing another branch that removes the associated code,
which can be merged in after this date.

Actual removal ready to roll here: https://github.com/sanger/sequencescape/pull/2972
1730 deletions!


Is this project actively maintained ?

Hello @ftxqxd,
At first, sorry for the ping, I'm assuming you're quite busy so I'll make it short :
It's been a while since your last update on this repository, do you consider it still active ? If not, I'd suggest you to add another maintainer so this crate doesn't stay abandoned.
You can for example add the Bus Factor +1 team to your crate that'll eventually find another maintainer for this project. If you want, you can also add me, so I'll take care of this for you.
I don't want to see this great project being abandoned, that's why I'm contacting you today.
Again, sorry for the inconvenience.
Sincerely,

I haven't really had the time to maintain the project, so I'm happy to hand control over to someone else, as I don't really intend to work on it any more. I've added you as an owner on the crates.io repo; feel free to add anyone else who wants to contribute, too.
Thanks for your interest in the project – it's nice to know people are still using it, even if I did abandon it a while ago :)

Thank you ! 🙇♂


recreate: fixed formatting of CQL output

Table fields where misaligned with table options.
MV fields where used different indentations, now it's aligned with rest.
Removed first empty line and added it at the end.
Fixes #46

Can you point me were the empty lines are fixed.

Can you point me were the empty lines are fixed.

Turns out they were there, github just cuts them. Check out golden files on your computer. I'll fix commit msg


Cannot use observable array for generating the map markers

For instance, in an app with a markers defined via a service, this code shows 0 markers despite there being 3 markers in the array.
<agm-map [latitude]="lat" [longitude]="lng">
<agm-marker *ngFor="let marker of markers$ | async"
[latitude]="marker.latitude"
[longitude]="marker.longitude">

In the TS file, markers$ is defined as
markers$: Observable<Marker[]>;
and initialized as this.markers$ = markerService.markers$;
with Marker model:
export interface Marker {
ip: string;
rate: number;
city: string;
state: string;
latitude: number;
longitude: number;
}

sorry never mind :) i was zoomed too far in. didn't notice the markers appearing :)

I am sorry for this comment but i almost fell from my chair laughing,
Funny as hell.


filezilla: 3.57.0 -> 3.58.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/filezilla/versions.
meta.description for filezilla is: "Graphical FTP, FTPS and SFTP client"
meta.homepage for filezilla is: "https://filezilla-project.org/"
meta.changelog for filezilla is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0/bin/.fzsftp-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0/bin/fzsftp had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0/bin/.fzputtygen-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0/bin/filezilla had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0/bin/fzputtygen had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0/bin/.filezilla-wrapped had a zero exit code or showed the expected version
0 of 6 passed binary check by having a zero exit code.
0 of 6 passed binary check by having the new version present in output.
found 3.58.0 with grep in /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0
found 3.58.0 in filename of file in /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
filezilla

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A filezilla https://github.com/r-ryantm/nixpkgs/archive/7ab41a2fd673abe1bbadf991be5b06bd3661fb29.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0
ls -la /nix/store/q2a1qfr5y4lsp6pdx3syn28gdc5dgbxh-filezilla-3.58.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

filezilla

Maintainer pings
cc @pSub for testing.

@ofborg eval


Prometheus won't deploy if the ECK Operator has not been installed (workaround is install it)

We need ECK API[1] to trigger creation of TLS materials[2] including the default-session-secret[3] used by Prometheus [4]. Otherwise the prometheus-default-0 container will stay stuck on ContainerCreating unable to mount the session secret.
Workaround is to install ECK[5] as per our docs (even if you don't intend to use Elasticsearch). It can likely be removed after STF installation.
[1] https://github.com/infrawatch/service-telemetry-operator/blob/569bfd6c726f430f65ef4837b81742ab155ea643/roles/servicetelemetry/tasks/main.yml#L54
[2] https://github.com/infrawatch/service-telemetry-operator/blob/569bfd6c726f430f65ef4837b81742ab155ea643/roles/servicetelemetry/tasks/main.yml#L49
[3] https://github.com/infrawatch/service-telemetry-operator/blob/569bfd6c726f430f65ef4837b81742ab155ea643/roles/servicetelemetry/tasks/component_certificates.yml#L30
[4] https://github.com/infrawatch/service-telemetry-operator/blob/569bfd6c726f430f65ef4837b81742ab155ea643/roles/servicetelemetry/templates/manifest_prometheus.j2#L62
[5] https://github.com/infrawatch/documentation/blob/7330ea1e3012a22375cfb4104b1f48122ddadefc/doc-Service-Telemetry-Framework/modules/proc_deploying-stf-to-the-openshift-environment.adoc#L190

Testing
I installed STF from master branch in use_redhat mode with no ECK
$ ansible-playbook --extra-vars __local_build_enabled=true --extra-vars __service_telemetry_snmptraps_enabled=true --extra-vars __service_telemetry_storage_ephemeral_enabled=true --extra-vars __service_telemetry_observability_strategy=use_redhat --extra-vars __deploy_stf=false ./build/run-ci.yaml

$ oc apply -f build/mystf1.yaml
servicetelemetry.infra.watch/default created

$ oc get csv --selector=operators.coreos.com/elasticsearch-eck-operator-certified.service-telemetry
No resources found in service-telemetry namespace.

$ oc get apiservers | grep elast | wc
      0       0       0

Everything seems to be working okay; prometheus deployed just fine.
$ oc get secret default-session-secret
NAME                     TYPE     DATA   AGE
default-session-secret   Opaque   1      7m25s

$ oc get po
NAME                                                      READY   STATUS      RESTARTS   AGE
alertmanager-default-0                                    3/3     Running     0          44m
default-cloud1-ceil-meter-smartgateway-7d54b48686-2k9kg   3/3     Running     0          45m
default-cloud1-coll-meter-smartgateway-59bb9fc985-sdgkh   3/3     Running     0          45m
default-cloud1-sens-meter-smartgateway-6d56f55bf4-2qwg7   3/3     Running     0          45m
default-interconnect-8b44c4485-2vj2w                      1/1     Running     0          53m
interconnect-operator-848759d9fb-n6zq5                    1/1     Running     0          59m
prometheus-default-0                                      3/3     Running     0          44m
prometheus-webhook-snmp-2-build                           0/1     Completed   0          53m
service-telemetry-operator-2-build                        0/1     Completed   0          59m
service-telemetry-operator-7dcf6b58c9-m4tfn               1/1     Running     0          50m
sg-bridge-2-build                                         0/1     Completed   0          54m
sg-core-2-build                                           0/1     Completed   0          56m
smart-gateway-operator-2-build                            0/1     Completed   0          57m
smart-gateway-operator-867545f986-vztbg                   1/1     Running     0          50m


Applying 64 dust to 64 extractors is the same as applying 1 dust to 1 extractors

https://github.com/user-attachments/assets/be733a2d-745b-4910-b705-5f058051263e

Dust will now automatically fix its percentage depending on the dust item amount.


feat: glob schema endpoint for generate

Using multiple gql files and combining them is a fairly common use case I believe.

@LiamMartens Sorry I was not being clear enough. Some existing codebase, which I am planning to remove, is still using lodash. So further depending lodash itself, or adding lodash.*, is discouraged.
I think we should add lodash back to package.json to keep tests green before the above refactoring happens.

@PabloSzx I updated it now to just allow gql or graphql, maybe it makes sense to just support it like that as there is really no proper use case for a JSON glob


[BUG]fix batch matmul not set attrs_type_key, when using tvm.parse.parse_expr will raise error.

df_parsed = tvm.parser.parse_expr(
    '''
    fn (%p0527: Tensor[(16, 256, 256), float16], %p1361: Tensor[(16, 64, 256), float16]) -> Tensor[(16, 256, 64), float16] {
        nn.batch_matmul(%p0527, %p1361, transpose_b=True) /* ty=Tensor[(16, 256, 64), float32] */
    }
    '''
)

the code above may fail, cause not set nn.batch_matmul attrs_type_key.
test_code:
def test_nn_batch_matmul():
    df_parsed = tvm.parser.parse_expr(
        '''
        fn (%p0527: Tensor[(16, 256, 256), float16], %p1361: Tensor[(16, 64, 256), float16]) -> Tensor[(16, 256, 64), float16] {
        nn.batch_matmul(%p0527, %p1361, transpose_b=True) /* ty=Tensor[(16, 256, 64), float32] */
      }
        ''')

now the attr has been properly set.

@yzhliu

Seems you have hit an flaky error, please run another job (rebase and push, or empty commit)

Sorry another flaky errors. You can relax the tolerance in https://github.com/apache/tvm/blob/d35b858ceb5c7157c3faa78c88eb8f8971ba5e96/tests/python/contrib/test_cudnn.py#L308

@MeJerry215 please fix the CI problem


Live server is not responding

Type: Feature Request
The live server is installed in the VScode very easly and have a go live option in stats bar but when i click on in it does not respond and nothing happen. Please try to solve my problem.
Extension version: 5.7.9
VS Code version: Code 1.83.0 (e7e037083ff4455cf320e344325dacb480062c3c, 2023-10-03T16:12:16.321Z)
OS version: Windows_NT x64 10.0.19045
Modes:

I have same problem earlier, if you have open two window vscode, and one of them have already start live-server, and you are trying to open live-server in another window, it will not be responding. and I solved it by close another window of live-server. i guess it's because the default port 5500 was occupied by one of vscode live-server, hope this will help you!

Go to “Edit system environment variables”
Click on “Environment Variables”
In the System tab, look for “PATH” or “Path”
Click on “Edit”
Add C:\Windows\System32
Click Ok and close everything.
If it doesn't work:
Uninstall the extension
Restart your computer.
Reinstall the extension
Go to the live server extension's settings
Click in "Edit in settings.json"
Remove the line “liveServer.settings.NoBrowser”: true,"
And manually add your preferred browser. Example:
“liveServer.settings.CustomBrowser”:“chrome:PrivateMode”
IF this help you, please follow me!


Updating BuildTools version

Updating BuildTools version to enable WindowsAppSDK updates. This was already made in main. Needs to be made in release/1.1-stable to support WinAppSDK 1.1.5 servicing.
main fix: https://github.com/microsoft/WindowsAppSDK/pull/2902/files

/azp run


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

This change is

Sorry, it has been already fixed.
Thank you


Added WindCORES to the list

I added WindCORES to the list, from my point of view a quite interesting project. They place small datacenters inside the tower of wind turbines, bringing the consumers of electricity closer to the producers while making the entire IT infrastructure more decentralized at the same time.

Updated branch to make it mergable into master.

Thabo you for your contribution @DonHege :sparkles:


workflows/tests: test API generation.

This should avoid making changes here that break API generation.
See also https://github.com/Homebrew/homebrew-test-bot/pull/920

There is a part of me that wonders if we could speed up the check by not writing the results to files if all we're testing is the actual JSON generation but that's not really that important.

@apainintheneck Yeh, this is a good idea worth investigate. A --dry-run or --no-write or something would be worth having if it sped things up a bit.


Support callout at 2D positions in addition to MD

See #241

Might be relevant for instance for having callouts on faults
Can be used also for user annotations/bookmarks, but that would require a backend that store this locations


nvidia-smi: only one process named hyprland

OS : Arch Linux
I successfully installed the Nvidia drivers in Hyprland, but nvidia-smi is only showing one process named Hyprland with GPU memory usage of 1MB.
I am using the hyprland-nvidia-git package from AUR. I have also set the grub nvidia_drm.modeset=1 option, enabled the mkinitcpio modules, and set all the ENV variables mentioned in the wiki.

I have one integrated Intel GPU and one dedicated Nvidia GPU.

please help me to fix this

great, nvidia is not supported.


New feature: Unioning source data

Are you a current Fivetran customer?
Yes, Pawel Ngei, Pattern Brands
What change(s) does this PR introduce?

Introduce the ability to union data from multiple schemas databases, as per https://github.com/fivetran/dbt_klaviyo_source/pull/9 (for Klaviyo)

Does this PR introduce a breaking change?

[ ] Yes (please provide breaking change details below.)
[x] No  (please provide explanation how the change is non breaking below.)

Is this PR in response to a previously created Issue

[ ] Yes, Issue [link issue number here]
[x] No

How did you test the PR changes?

[ ] CircleCi
[x] Other (please provide additional testing details below)

Pattern Brands data, two datasets from Facebook Ads connector
Select which warehouse(s) were used to test the PR

[ ] BigQuery
[ ] Redshift
[x] Snowflake
[ ] Postgres
[ ] Databricks
[ ] Other (provide details below)

:building_construction:
Feedback
Will need to remember to add a Readme note about the basic_ad table to the other two plugins, it's not advertised enough

Thanks again so much for putting the effort into this PR @pawelngei! There are a few minor changes (tests and formatting updates) that I am going to apply before we include this in a live version of the package. Therefore I am changing the base branch to be a working branch that I will apply these updates to.
Thanks so much!


WIP: bump snapshot version

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/retest

/retest

/retest


3dSkullStrip error

2017-04-12 02:37:48,469 workflow:ERROR ['Node skullstrip.a0 failed to run on host sh-0-31.local.']
2017-04-12 02:37:48,469 workflow:INFO Saving crash info to /scratch/PI/russpold/data/psychosis/05_mriqc/out/logs/crash-20170412-023748-jdurnez-skullstrip.a0-115bb300-17cc-4a78-9dfa-c0b20f0cc88e.pklz
2017-04-12 02:37:48,470 workflow:INFO Traceback (most recent call last):
  File "/root/src/nipype/nipype/pipeline/plugins/multiproc.py", line 52, in run_node
    result['result'] = node.run(updatehash=updatehash)
  File "/root/src/nipype/nipype/pipeline/engine/nodes.py", line 366, in run
    self._run_interface()
  File "/root/src/nipype/nipype/pipeline/engine/nodes.py", line 476, in _run_interface
    self._result = self._run_command(execute)
  File "/root/src/nipype/nipype/pipeline/engine/nodes.py", line 607, in _run_command
    result = self._interface.run()
  File "/root/src/nipype/nipype/interfaces/base.py", line 1085, in run
    runtime = self._run_wrapper(runtime)
  File "/root/src/nipype/nipype/interfaces/base.py", line 1728, in _run_wrapper
    runtime = self._run_interface(runtime)
  File "/root/src/nipype/nipype/interfaces/afni/base.py", line 130, in _run_interface
    return super(AFNICommandBase, self)._run_interface(runtime)
  File "/root/src/nipype/nipype/interfaces/base.py", line 1762, in _run_interface
    self.raise_exception(runtime)
  File "/root/src/nipype/nipype/interfaces/base.py", line 1686, in raise_exception
    **runtime.dictcopy()))
RuntimeError: Command:
3dSkullStrip -input /scratch/PI/russpold/data/psychosis/05_mriqc/work/workflow_enumerator/anatMRIQCT1w/AFNISkullStripWorkflow/_in_file_..scratch..PI..russpold..data..psychosis..03_bids..sub-S5139LGO..anat..sub-S5139LGO_run-1_T1w.nii.gz/skullstrip/sub-S5139LGO_run-1_T1w_conformed_corrected.nii.gz -prefix sub-S5139LGO_run-1_T1w_conformed_corrected_skullstrip.nii.gz
Standard output:

Standard error:
/usr/bin/xvfb-run: line 183: 35821 Segmentation fault      DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE "$@" 2>&1

Return code: 139
Interface SkullStrip failed to run.

Crashfile and logs attached.

In version 0.9.1, using the latest docker image (poldracklab/mriqc).

This is going to be tough, but thanks for reporting!

This happened with AFNI-16.2.07~dfsg.1-1~nd80+1. Currently we use 16.2.07~dfsg.1-2~nd16.04+1, so this is probably fixed. Please reopen if this happens again, and we will consider upgrading AFNI to v 17.


Create a node app to validate URLs

Create a node app to validate URLs

A sample node app - https://codesandbox.io/s/check-if-url-exists-vbg6q
Written in TypeScript, but use a vanilla JS for the actual implementation, as GitHub would need "node" to run the app


Escape all forward slashes to allow sub-directories

The Problem
If the baseUrl in cypress.json contains a subdirectory, the test run fails.
This issue can be recreated using the aldefouw/redcap-docker-compose repository by amending app volumes setting in the docker-compose.yml file to '../www/:/var/www/app/public_html/sub' and changing the baseUrl in cypress.json to "http://localhost:8080/sub".
The Fix
I have amended the escaping of the baseUrl parameter in support/index.js to escape all forward slashes, not just those at the start of the URL.

@rabramley - Good call!  This makes good sense to me.
This is safer escape behavior in general for URLs than what we had before so I'll merge this in.
Thanks for your contribution.


Recommend to add overflow css in Card Component

Card Title has a problem with overflow issue.
Example

const CardTitle = React.forwardRef<
  HTMLParagraphElement,
  React.HTMLAttributes<HTMLHeadingElement>
>(({ className, ...props }, ref) => (
  <h3
    ref={ref}
    className={cn(
      "text-2xl font-semibold leading-none tracking-tight",
      className
    )}
    {...props}
  />
))
CardTitle.displayName = "CardTitle"

So I recommend to add overflow and text-overflow like this
const CardTitle = React.forwardRef<
  HTMLParagraphElement,
  React.HTMLAttributes<HTMLHeadingElement>
>(({ className, ...props }, ref) => (
  <h3
    ref={ref}
    className={cn(
      "text-2xl font-semibold leading-none tracking-tight overflow-hidden text-ellipsis",
      className
    )}
    {...props}
  />
));
CardTitle.displayName = "CardTitle"

PR
https://github.com/shadcn-ui/ui/pull/2593

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


correcting bugs

AbstractBasicRequest.java- allow 'minWordLength' to be null to avoid rewriting the internal default value;
ModelMetadata.java - correcting bug (default stopWords is a Set).

I could not test because your branch is 18 commits behind master.
Also I think a null value on a integer field could be avoided if the default value is negative to flag that the user did not changed anything during request or am I missing something?

Just one commit behind and not conflicting. Wasting of time, but updated.
New PR created.
On Thu, May 18, 2017 at 7:08 PM, Leonardo Souza<EMAIL_ADDRESS>wrote:

I could not test because your branch is 18 commits behind master.
Also I think a null value on a integer field could be avoided if the
default value is negative to flag that the user did not changed anything
during request or am I missing something?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Lambda-3/Indra/pull/36#issuecomment-302475596, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJAYJgMW2JjmTanu99DwnzIXTfebCtQ8ks5r7Hr2gaJpZM4NffvL
.

In relation to the null value, it is an equivalent solution, there is no error on it. Changing is, again, only another waste of time.


Adding a warning to the README about the need to use a recent version of the provider for private endpoints

Adding a warning to the README about the need to use a recent version of the provider for private endpoints to avoid a recently discovered bug in older versions.
Commit checklist

[ ] Changelog
[ ] Doc gen (make generate)
[ ] Integration test(s)
[ ] Acceptance test(s)
[ ] Example(s)

Warnings about using latest provider for private endpoints


Add support for temporary session tokens

Resolves #2141
Tested with credentials generated with aws sts get-session-token. It also provides an expiration field but that is not necessary to use the temporary token.

Manual testing
We decided to do manual testing for the first pass and worry about automating the test later.
1. Temporary credential generation
Here is the generation of the temporary credentials. I looked and there really is no way to do this via the AWS console. By default they only last 1 hour!

2. New Optional Session Token Field
I couldn't think of any visual way to indicate that the session token is optional, so I labeled it "(Optional)".

And here you can see that it doesn't block the Next button once the first two credential fields are provided.

Still a bit worried that this feature will confuse newbies, but not sure what else to do here.
3. Session Token is defined in the DB
Self explanatory

4. Can still install modules and get the expected results out of it
Everything is working just fine with these temporary credentials :)

it might be good to mention it in the /docs/aws part of the documentation


Blog Section - Building RESTful CRUD API in Spring Boot Image Not Visible

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
In the blog section titled "Building RESTful CRUD API in Spring Boot," the image intended to illustrate the content is not visible. The request is to fix the issue so that the image displays correctly within the blog post.
Use Case
I want the image associated with the blog post to be visible. This involves checking and correcting the image URL or path, ensuring proper formatting, and verifying that the image loads correctly across different devices.
Benefits
Fixing the image visibility will enhance the blog post's visual appeal and effectiveness, improve user engagement by aiding understanding and retention, and ensure a professional appearance by making sure all blog elements are functioning correctly.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

I want to work on this issue. Also, please add the label GSSOC and the level that you find appropriate for this issue. thank you!


intrauterine fetal demise

Mondo term (ID and Label):
pregnancy disorder with abortive outcome (ID # 0041526)
Synonym to be added:
intrauterine fetal demise (IUFD); intrauterine fetal death; stillbirth
Synonym subtype: ie, broad/exact/narrow/related:
exact
Database cross reference for the synonym: Such as PubMed ID (in the format PMID:XXXXXX) or a cross-reference to another ontology, like OMIM or Orphanet.
32491465
Your nano-attribution (ORCID):
0000-0001-7151-1615

@cmungall @hrshdhgd
I think you could use this issue for your demo ontobot.

related to: https://github.com/monarch-initiative/mondo/issues/6254


Block Exporter #5: Disable Selected Blocks on Tab Switch

fixed bug where switching tabs would update the toolbox with all enabled blocks--despite selected blocks still being on the workspace.
edited exporter controller's updateToolbox() function (which is called upon tab switch to account for any changes to the block library) to disable all selected blocks.

This change is

@evd2014 @picklesrus @vicng

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Vega mining performance on Linux with ROCm lower than Windows 10

Running teamredminer (https://github.com/todxx/teamredminer) on Linux with ROCm 4.5, hashrates are noticeably lower than on Windows 10 on the same hardware. The cards are a reference Vega 56 with Samsung memory and an Asus ROG Strix Vega 64.
With undervolting, memory overclocking and tweaked memory timings (same settings on both OSs), I can get over 48MH/s on DaggerHashimoto (Ethereum) from each GPU on Windows, whereas Linux only manages 33-36MH/s. The lower performance is accompanied by reduced power usage and temperatures.
The differences are similar using stock clocks and voltages, can't remember the exact figures, though.
Linux system is Linux Mint 20 with kernel 5.13, using upstream amdgpu driver. Windows is running the 21.12.1 driver.
I have run clpeak (https://github.com/krrishnarraj/clpeak) on both OSs - results pasted below.
The discrepancies in the transfer bandwidth test results are particularly interesting.
I have tried changing several amdgpu module parameters, such as vm_fragment_size, vm_update_mode and aspm - none of these changes resulted in improvements. Any ideas as to what to look into next would be much appreciated.

Anything above that i tested resulted in performance regression.
No idea where the regression comes from, kernel or rocm.

Thanks, Nostromo-KM. Can't remember if I ever tried it with 5.4, but will give it a go.

Update: performance is indeed higher with 5.4 kernel. ROCm libraries/packages are still 4.5, firmware is the same as before (latest version in repos).
My guess would be that the amdgpu module is responsible for the regression - this could be checked by installing the DKMS module, providing it actually builds with 5.4.

Hi @falcon35180
Thanks for reaching out.
I certainly understood the situation.
I do not think its an ideal comparison as we are comparing between Linux/ROCm and Windows10/non-ROCm.
So I can not comment more on this as the comparison is not good.
I recommend to try with older kernels like 5.4 as suggested above.
This way you might find perf drops by comparing 2 different linux kernels, I recommend to file the issues in those cases.
Thank you.

@falcon35180 FYI you can run the AMDGPU-pro stack in a docker container. You can get a Docker image with AMDGPU-pro and teamredminer here: https://hub.docker.com/r/wesparish/teamredminer.
Works just fine without any special kernel modules or similar and you can keep using your regular desktop with Mesa at the same time.

@Atemu I'm now running the two Vegas on a Tiny Core Linux setup with kernel 5.4, upstream driver and amdgpu-pro OpenCL libraries. As mentioned earlier, 5.4 performs well - amdgpu-pro (version 20.40) and ROCm give the same results in this regard.


[WIP] Revert Ubuntu 21building

@TheTrunk This branch 17492a6 builds on mac locally. Not sure about travis.
I am building on
Mac mini Intel Core i7
macOS Ventura 13.1
I am building only using ./zcutil/build.sh


Adds Pre and Post Tradier Order Duration

Expected Behavior
Be able to place limit order outside market hours with Tradier:
https://blog.tradier.com/blog/2018/05/trading-in-the-pre-and-post-market-sessions-tradier-brokerage.html
Actual Behavior
It's not possible.
Additionally, if there is one of these orders in the account, Lean throws an exception:
Error converting value "pre" to type 'QuantConnect.Brokerages.Tradier.TradierOrderDuration'

Potential Solution
N/A
Reproducing the Problem
Please a limit order with the pre duration:

and deploy LEAN before it is filled.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

How far back does the synchronization go? The error is pulling trade data back to "create_date":"2022-03-31T20:00:26.865Z"
The error is not reliant on the trade being unfilled when LEAN is deployed. The Pre-market trade was placed and filled prior to starting LEAN.

Hey @bryan78305! Sorry about that, issue should be solved now by PR https://github.com/QuantConnect/Lean/pull/6281. Leaving this issue open as feature to add support for Pre and Post order duration for tradier.


Help compiling for Android

Hello, I am new to nativescript but not new to programming.  I run the android app and was hoping to make some enhancements to the scanning process but I'm unable to get the android app to run from code.  First, I was getting compilation errors, but was able to fix that by changing the sass-loader version down to ~10.1.1 (looks to be a known issue) and having to set the environment variable --openssl-legacy-provider.  After doing that, I was able to get it to compile but when trying to run it I got a black screen with red text:
record.factory is not a function

TypeError: record.factory is not a function
    at R3Injector.hydrate (file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:55044:35)
    at R3Injector.get (file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:54865:33)
    at file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:54902:55
    at Set.forEach (<anonymous>)
    at R3Injector._resolveInjectorDefTypes (file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:54902:31)
    at new NgModuleRef$1 (file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:68932:26)
    at NgModuleFactory$1.create (file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:68986:16)
    at file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:72779:45
    at<EMAIL_ADDRESS>(file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:145611:26)
    at Object.onInvoke (file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:72187:33)
    at<EMAIL_ADDRESS>(file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:145610:32)
    at<EMAIL_ADDRESS>(file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:145361:43)
    at NgZone.run (file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:72070:28)
    at PlatformRef.bootstrapModuleFactory (file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:72777:23)
    at file:///data/user/0/org.nativescript.PantryParty/files/app/vendor.js:72829:41

Seems as if there's a version conflict that I can't seem to track down.  Hoping for some help getting it running so I can start to contribute.  Thank you!

I was able to get it running by modifying the following versions:
    "sass-loader": "~10.1.1",

    "@nativescript-community/ui-material-bottomsheet": "~5.1.16",
    "@nativescript-community/ui-material-button": "~5.1.16",
    "@nativescript-community/ui-material-ripple": "~5.1.16",

I will put in a pull request shortly for this fix.


Language adapter training

Is there an example showing training language adapters?
In my opinion the language-modeling section of the examples is misleading because it provides scripts which can be used for language modeling but there is none showing adapters usage.

Hey,
The script we have been using in the past has been pushed to legacy.
We will add adapters to the new scripts ASAP.
Meanwhile the legacy code should still work:
https://github.com/Adapter-Hub/adapter-transformers/blob/master/examples/contrib/legacy/run_language_modeling.py

Hi, thanks a lot for the quick reply :)
This legacy code does not support the HuggingFace Datasets library, right ?
So, I guess I have to change how the data is loaded to be able to train language adapter by providing a dataset name (from HF hub) ?

Hi @sstojanoska,
we now have modified versions of HuggingFace's new language modeling scripts with adapter support: run_clm.py & run_mlm.py. These support loading data from HuggingFace datasets.

Thanks for the updates :)


Found a vulnerability. How do I report it securely and privately?

Hey Staff,
I'm an ethical hacker and noticed that while looking through the app on my free time that I found a critical vulnerability for the desktop app of this wallet. Is there a way to report this more securely instead of on a public issue on GitHub like this current one??? I don't want to say anything involving the vulnerability on here because people might be able to easily find it and cause problems for you guys.
Thanks & Regards,
WYV3RN

You can send it on to<EMAIL_ADDRESS>

Thanks!


npm run update to automate pulling down the latest code from git

People who don't know how to manage git should be able to receive updates to Postmarks. I've been talking to some other folks at Glitch and it sounds like the best way to support Glitch installs (and one that should be plenty useful to non-Glitch installs as well) is to provide some npm scripts that manage this.
Proposal outline:

npm run update, given that a git upstream has been set, should take the current git HEAD, move it into a backup branch, then (force-?)pull  from the main branch (if we eventually change release strategies, we can change this script to do something more nuanced to find the current installed version & grab the latest version that we believe we can safely update the user to)
A companion npm run git-setup should exist to prompt the user for a URL to a git remote, defaulting to the main postmarks repo, giving someone an opportunity to specify their own fork if they're choosing to manage the project that way.
Because we have the backup branch, we can provide manual instructions for restoring the branch if need be.

In general everything relevant data-wise should be safe given that .gitignore includes the directory, but maybe we should also make backups of .db files?
It seems like there might be previous work here in other projects–curious if anyone knows of any other relatively small projects that have already handled something like this (less interested in something as heavyweight, or as Docker-oriented, as Mastodon)

Instructions I've given to a few people which have yielded mixed success:
git remote add upstream https://github.com/ckolderup/postmarks
rm .data/.keep
git pull upstream main

I just did a remix on Glitch to test this out and it looks like there's a problem with the gitignore strategy I have right now of keeping the .data directory in the git repo by using an empty .keep file, then trying to .gitignore everything except that file. This blog post has an interesting alternative approach, replacing the .keep with a subdirectory .gitignore that ignores everything except itself. We should probably switch to using that, and see if that makes the existing three-line process above work smoothly as a default scenario?


NOFIELDS does not seem to work over RESP

Set up a key with a single object with field foo:
./tile38-cli
<IP_ADDRESS>:9851> set test 1 field foo 100 object '{"type":"Point","coordinates":[-96.4146030229,28.444531979]}'
{"ok":true,"elapsed":"31.863µs"}

NOFIELDS works correctly within tile38-cli:
<IP_ADDRESS>:9851> intersects test limit 3 nofields bounds 28.444531979 -97 29 -96.4146030229
{"ok":true,"objects":[{"id":"1","object":{"type":"Point","coordinates":[-96.4146030229,28.444531979]}}],"count":1,"cursor":0,"elapsed":"31.934µs"}

but does not work with redis-cli (or python redis client):
redis-cli -p 9851 --raw
<IP_ADDRESS>:9851> intersects test limit 3 nofields bounds 28.444531979 -97 29 -96.4146030229
0
1
{"type":"Point","coordinates":[-96.4146030229,28.444531979]}
foo
100

Note that foo and its value are both returned, despite the NOFIELDS argument.
Same thing happens in SCAN, SEARCH, WITHIN and NEARBY.

Thanks for reporting. I just pushed a fix to the master branch.


Upgrade JWT middleware from 0.2.1 to 0.2.2

The JWT middleware is no longer a django middleware, thus, upgrading to this new "minor" version is breaking the middlewares. More details here https://github.com/flavors/django-graphql-jwt/pull/125.
For reference about why those changes have happened: https://docs.djangoproject.com/en/2.2/topics/http/middleware/

Might I suggest changing the pyproject.toml field for the django-graphql-jwt package? I spent quite a bit of time debugging an issue when the root cause was simply updating the poetry lock dependencies from the project. I can confirm that 0.3.1 does not work with the mainline codebase.

@adithyabsk what do you mean? I is already pinned to 0.3.0.

@NyanKiyoshi When you run poetry lock the dependency will resolve to 0.3.1 because of semantic versioning:
https://github.com/mirumee/saleor/blob/2e94e8df80f305889434f549a4da6abc1257b598/pyproject.toml#L25

Ah I see 👍 I will try to see if there are updates about #5149 as it is supposed to fix that issue.
Feel free to open a pull request to fix the pyproject.toml!


I'm getting "Unknown command: 'inspectdb_refactor'. Did you mean inspectdb?

Using latest Django and psycopg2.
Any tips?

I'm sorry! This was my fault...
default database wasn't coming through in settings.py.
We all good.


Remove hard-coded 82 zone limit

Describe the bug
New LIFX multizone devices can have over 82 zones, so remove the hard-coded limit and work with the zone count reported by the device.
Additional context
Upstream issue: https://github.com/home-assistant/core/issues/125149

Fixed via #379


fix: no dup on file descriptor

As a note:
There wasn't any issue before, there isn't any issue after this. I'm removing it regardless.


Removes shelljs

TODO:

[ ] test code in the test/webbrowser.js

Nice idea! Removing shelljs may help a bit with the web browser performance.

How are you planning to test this? I think we can just run the bots and see what it does, or are changes on the bots required for this as well?

test code in the test/webbrowser.js

I'm not sure what sort of testing you had in mind here, however:
I've tested this patch locally on Windows, using commands such as e.g. gulp unittest/fonttest/browsertest, and everything appear to work exactly the same as with the current master.

I'm not sure what sort of testing you had in mind her

Mostly aborting hanging browser process.

Mostly aborting hanging browser process.

I've just tested this (on Windows), by reverting a patch (on top of this PR) that fixed an infinite loop, and once the timeout[1] was reached the browser was closed/cleaned-up properly.
There were no problems running e.g. back-to-back gulp browsertest commands.[2]

[1] https://github.com/mozilla/pdf.js/blob/658fb03db1e3ccc2f140daa46ef961f877aa0615/test/test.js#L100
[2] I'm assuming that issues with aborting a hanging browser process would have prevented a new test from being successfully triggered run.

/botio test


Resolve #821

Please see code analysis at https://github.com/maputnik/editor/issues/821#issuecomment-1772360990

Please see code analysis at https://github.com/maputnik/editor/issues/821#issuecomment-1772360990

thanks!


CVE-2021-46828

Installed Resource libtirpc 1.3.2-r0 in python:3.10.5-alpine3.16
https://github.com/docker-library/python/blob/master/3.10/alpine3.16/Dockerfile#L43
can it be removed?

I don't think so. We check all build dependencies for whether they were linked to by something built and if it is still in the final image, then something is linking to it (or an apk dependency of it). This bit is making sure anything that provides an  .so that is linked to is kept after we remove the temporary .build-deps defined/installed earlier:
https://github.com/docker-library/python/blob/6ca54f5e8a180fad4b525c2dfecd23c76ff04894/3.10/alpine3.16/Dockerfile#L101-L107
libnsl-dev depends on libtirpc-dev, so to get rid of libtirpc-dev, we also have to remove libnsl-dev. It looks like these are both linked to by the nis module:
/ # find /usr/local -type f -executable -not \( -name '*tkinter*' \) -exec scanelf --needed --nobanner --format '%p%n#p' '{}' ';' | grep rpc
/usr/local/lib/python3.10/lib-dynload/nis.cpython-310-x86_64-linux-gnu.solibnsl.so.3,libtirpc.so.3,libc.musl-x86_64.so.1

Which is only just now being deprecated with a warning starting in Python 3.11 (https://peps.python.org/pep-0594/) and won't be removed until Python 3.13.

Will this be fixed in the next image refresh? If yes, when is it planned?

Looks like you can bypass that by installing latest versions in your Dockerfile:
RUN apt-get install libtirpc3=1.3.1-1+deb11u1 libtirpc3=1.3.1-1+deb11u1 -yqq

Will this be fixed in the next image refresh? If yes, when is it planned?

For the Alpine-based images, today. Since the base images were just updated in https://github.com/docker-library/official-images/pull/12929, the dependent images will be rebuilt in the coming hours.
For the Debian-based images, probably in 3 weeks or so since the last rebuild was only 8 days ago (https://github.com/docker-library/official-images/pull/12889).

@yosifkit isn't the base image update for a different CVE, not CVE-2021-46828?

@yosifkit the base image update is for a different CVE, i confirmed CVE-2021-46828 is still in python:3.10.6-alpine3.16 from couple hours ago

Yes, the base was updated for a specific different CVE, but since we rebuild all dependent official images when a parent image changes, the Alpine-based python images will naturally get any security fixes of packages installed in their layers. https://security.alpinelinux.org/vuln/CVE-2021-46828 shows that for Alpine 3.16, the 1.3.2-r1 contains the fix, which is the version in the most recent image:
$ docker run -it --rm python:3.10.6-alpine3.16 sh
Unable to find image 'python:3.10.6-alpine3.16' locally
3.10.6-alpine3.16: Pulling from library/python
213ec9aee27d: Pull complete
6b2a141cd227: Pull complete
a292fad6b52e: Pull complete
4593e4e33a59: Pull complete
95765f0918ef: Pull complete
Digest: sha256:db0f3888d0ef4293a6387462b87a75bcdd0c4bc4cfc798ec617a5923be780cf6
Status: Downloaded newer image for python:3.10.6-alpine3.16
/ # apk list | grep tirpc
WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/main: No such file or directory
WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/community: No such file or directory
libtirpc-conf-1.3.2-r1 x86_64 {libtirpc} (BSD-3-Clause) [installed]
libtirpc-1.3.2-r1 x86_64 {libtirpc} (BSD-3-Clause) [installed]


Kil kill

@andreistefanescu @cos @bmmoore @radumereuta @daejunpark @grosu please review
things I deleted

sdf parser
old krun, kompile, kast frontends
old compiler
old debugger, executor, model checker, prover frontends
old unparser
unparser and unflatten backend
--kore flag (now the default)
dead code arising from deletion of the above

things I did not delete

html, latex, pdf, doc, coq backends
checks that need to be rewritten for kore
kil hierarchy

things I moved

various static things that were part of a class I deleted but used by the new pipeline
various packages with kore in their name to a better package name

things I commented out

most of ktest. unfortunately we're still not in a good shape to pass any of the tests in ktest, even imp, mostly because the unparser isn't done yet. Once we implement a collection normalization filter and the format attribute it should pass though.

The diff looks pretty intimidating but it's actually much less bad than it seems. Most of it is just deleted files and small renames to packages. The remainder is all grouped in a single commit that you should be able to easily review separately, and is also mostly deletions, but at the less-than-file level. That said, you may wish to review the first commit on the command line just because github truncated the diff and it's actually moderately distracting to see the full body of every file that is deleted in the diff.
If we need to bring anything back, we can always do that; I tested the code which remains against IMP, the KORE tests in ktest, and the C semantics and they all passed; I don't think anything got deleted that was part of the KORE pipeline.

Wow, this is big!  Many will be affected, but it had to happen, otherwise we would continue to drag our feet.  This way we know that no time is being wasted on KIL, and developers who want functionality not present in KORE have motivation to make that functionality work.  I rely on @andreistefanescu , @cos, @bmmoore , and @daejunpark for checking the technical details of the pull request.
@bmmoore , I see that the tutorial tests have been deactivated.  I understand why, but you had one or two tests that worked in your branch.  Can you please add those back?
@dwightguth , was it necessary to remove most of ktest?  I think its functionality should be orthogonal to KIL vs. KORE.  Yes, we do not have a pretty-printer yet, I know, but we could use the labeled form until we get one.  Actually, we should get a pretty-printer asap.
Otherwise it all LGTM.

I have no particular objection to us modifying temporarily the outputs of krun for the tutorial to give us better test coverage. Given that the test coverage is severely limited by this diff, I think that's probably a good idea. But I think that that is better done by Brandon in a followup pull request than as part of this giant monster.

lgtm. I see you also renamed several packages. I'm ok with the changes.

With #1575 still open, removing SDF parsing may be premature. My only other concern is being able to run old definitions, which is probably handled well enough by keeping independent K installations.

Closing since we agreed to do this later.


WIP: new monitor package

Still very much a WIP
PR Checklist

[ ] Added Tests
[ ] Updated Documentation
[ ] Updated CHANGELOG.md for the appropriate package

Closing as this was moved out into its own repo.


tensorrt > 8.5 will throw error: ‘class nvinfer1::ICudaEngine’ has no member named ‘getNbBindings’

https://forums.developer.nvidia.com/t/tensorrt-8-5-depecated-functions/278907

https://forums.developer.nvidia.com/t/tensorrt-8-5-depecated-functions/278907

Do you have multiple version of TensorRT?
getNbBindings just in tensorrt8


make more efficient use of condor bulk submission

Ok, it seems the only reason we needed to pre-sort for bulk submission was that some parameters were only selectively set and instead of using preset defaults, it would default to the value from a previous job within the same bulk submit. So bulk submits with some jobs setting the parameters and some jobs without setting the parameters lead to weird behavior.
This patch fixed that for the highIOjob flag (always set for either 0 or 1) and numberOfCores (always set, even for singlecore jobs which now specifically request 1 cpu). That in turn allows us to get rid of the pre-sorting by numberOfCores and highIOjob.
I tested this change for numberOfCores with a bulk submit of 26 jobs all requesting between 4 and 8 cpus and it worked fine, the jobs running in Condor showed up the correct number of cpus it requested.
There are still some parameters that are selectively set, but since we don't pre-sort by them, nothing is changed to how things work now. There is a chance we might even be able to get rid sorting by sandbox and just bulk submit everything without caring about sandbox, but that needs more work and also will need us to address these last outstanding parameters that are selectively set.
Example for how to deal with such a parameter would be what I did for MaxWallTime. Old code set it selectively, new code defaults to 12h if it is not set. Of course, if we say that the expected wall time should always be set for a job, we can also simplify this.
I'll follow up in HN with the list of parameters. We need to make sure that they are always set, either by always having the information available to set it or by providing some sensible default.
@amaltaro @ticoann , would appreciate feedback and comments on this patch (as it exists now).

This patch will have to be reworked once the "jdl magic" patches are merged, but that's ok. It's good enough for code review and discussions as-is.

Dirk, for wallTime and requestDisk, I suggest you set the default value to the minimum in these settings. So, 1h and 1GB.

I have a problem with that because that is the optimal way to make sure the jobs get run on a pilot with not much wall time left and will end up being rescheduled.

And the disk could be a problem too. If you ask for 1GB and use 20GB, you can cause problems for other payloads running in the same pilot.

My take here is that only a very small fraction of jobs won't have the performance estimates set inside the job (correct ?). As such, asking for a bit more resources won't affect the big picture much, but will make sure these jobs have a chance to run correctly.
If my initial assumption is wrong, maybe we should make sure that most jobs actual have these estimates set ?

The impact of guessing too high is small, mainly not quite as efficient job scheduling as could be possible. The impact of guessing too low can be lots of job retries and internal Condor rescheduling and/or using up all the disk space in the pilot.

Valid comments, Dirk. From my experience, only utilitarian jobs (cleanup, logcollect, possibly harvest) don't have job estimates.That's why I was shooting at lower default values to ease job scheduling.
That's why 12h estimated for these job types may not be optimal... but I agree that if it's too low, we have much more problems on the agent side.
So it would be 12h walltime and 20gb for disk, right?

Yeah, 12h wall time (still only a quarter of pilot lifetime, so should be easy to schedule), 20GB disk per core (which is what each site should provide anyways) and the 1000MB for memory.

test this please

test this please

test this please

Ok, this seems to work. Also just tested in a Tier0 replay. Jobs with different cpu requests and different highIOjon flags were bulk submitted together and it worked fine.
Now looking at the outstanding jdl parameters
     if job.get('taskName'):
         jdl.append('+WMAgent_SubTaskName = "%s"\n' % job['taskName'])

     if job.get('taskType'):
         jdl.append('+CMS_JobType = "%s"\n' % job['taskType'])

How about I just add an "Unknown" as default ? I still think this should actually always be set, but I don't want to dig through the code base to confirm this...
     if job.get('inputDataset'):
         jdl.append('+DESIRED_CMSDataset = "%s"\n' %

job['inputDataset'])
if job.get('inputDatasetLocations'):
jdl.append('+DESIRED_CMSDataLocations = "%s"\n' %
','.join(job['inputDatasetLocations']))
How about and empty string "" as default ?
     if self.useGSite:
         jdl.append('+GLIDEIN_CMSSite = \"%s\"\n' % (jobCE))

No idea. Is this guaranteed to be always set or do we need a default ?
     if job.get('proxyPath'):
         jdl.append('x509userproxy = %s\n' % job['proxyPath'])

Do we even still use this ? If potentially yes, how about an empty string "" again as default ?
     if job.get('requestName'):
         jdl.append('+WMAgent_RequestName = "%s"\n' %

job['requestName'])
m = GROUP_NAME_RE.match(job['requestName'])
if m:
jdl.append('+CMSGroups = %s\n' %
classad.quote(m.groups()[0]))
Default "Unknown" again ?

@bbockelm any comments on how some of these parameters are used in the HTCondor side and what sensible defaults are ?

"Unknown" is a fine default, I suppose.
We in fact do use x509userproxy in the global pool from WMAgent: perhaps we don't use it for the T0 pool?
I have no clue what GLIDEIN_CMSSite is for or why we would set it.
Everything else looks familiar.

We do use x509userproxy , but it is set by the schedd based on the X509 environment, not because the agent puts it there. We have never set this variable from the agent.

Ok, so proposal:
Default "Unknown" for +WMAgent_SubTaskName, +CMS_JobType, +WMAgent_RequestName and +CMSGroups.
Remove setting x509userproxy (btw, CRAB3 doesn't use the agent submission plugins, does it ?).
What about +DESIRED_CMSDataset and +DESIRED_CMSDataLocations ? Empty string as suggested ok ? What is this used for ? Just monitoring or something functional ?
About +GLIDEIN_CMSSite, I am going to ask in HN about it what this is for...

Don't remove x509userproxy please. We do set it in the agent environment and AFAIK we need this setting in both the agent code (to add the path/DN to the classAd) and to the condor schedd config.
I think we should not give Unknown as default value for:
WMAgent_SubTaskName, +CMS_JobType, +WMAgent_RequestName
instead let it break the component. It should always be present. If it's not, we need someone investigating it.
About +CMSGroups, when @bbockelm put it in WMCore code it was meant to be temporary until gWMS was able to handle it itself. Otherwise, Unknown should work be sufficient here.

@amaltaro , you are not correct on this. No agent sets this. I checked.

And how the schedd knows which file has to be shipped with these jobs?
I thought we needed to have X509 var in the system before starting the agent, such that the plugin would inherit this env var, e.g.:
cmst1@vocms0230:/data/srv/wmagent/current $ cat /data/admin/wmagent/env.sh | grep X509_USER
export X509_USER_CERT=/data/certs/servicecert.pem
export X509_USER_KEY=/data/certs/servicekey.pem
export X509_USER_PROXY=/data/certs/myproxy.pem

but I failed to find it in the code.  I'm not.

I am 100% certain. The schedd picks it out of the environment the condor_submit is run in and you need a special schedd config parameter to do this (which is set for production agent machines schedd).
The agent itself has never cared what the X509 environment is set to.

The x509userproxy code remnants are code leftovers from when CRAB was developed to run inside an agent. It would have been a request level parameter, passing the user proxy for the user submitting the request.

Ok, following the discussion in HN and here, these are the next changes:
+WMAgent_SubTaskName, +CMS_JobType, +WMAgent_RequestName are always set using the information in the job. If the job doesn't have the info the component crashes (and we should check if this is a valid use case or not).
In the case +CMSGroups wasn't set, set it to undefined now. This is not a string value, but a literal with special meaning.
Same thing for +DESIRED_CMSDataset and +DESIRED_CMSDataLocations, instead of not setting them they will be set to undefined now.
I left x509userproxy alone for now (since frankly it doesn't matter one way or the other). If we ever clean this up we will have to remove a whole bunch of dead code, not just that two lines.

test this please

Next set of changes:
Had to change how request_memoy and request_disk are set. Some jobs have it set to None, which is not a valid value. For consistency reasons I also changed how +MaxWallTimeMins is set.
This version also gets rid of the sorting by sandbox. Tested that first and it seems to work.

test this please

@amaltaro , this is ready for some more testing on the agent side

I'm gonna test it now. Please make a new commit if you make any changes besides the default values I suggested, for the moment.

Hi Dirk, Alan,
I have been reading the discussion here about default parameter values. I would like to have a better understanding of what kind of jobs would carry those default values, and as this would affect payload to pilot scheduling performance, I'd prefer this be discussed together with the SI team. What do you think, should we try next Thu?
Antonio.

There is not going to be an effect since almost all jobs will have non-default values configured. We are only talking about utility jobs here... Anyways, I won't be available Thursday.

Ok, it does not have to be this Thu. of course, and even we can discuss this by email or here… just to keep SI people aware of the potential impact of this.
So don't we have some properly defined values for utility jobs? Even more, have we been monitoring what the typical actual used values are?
Another question out of curiosity, I saw some defaults depending on number of cores, are we running any utility jobs using more than one?

Merges can be multi-core. AlcaHarvesting and repack too, but they aren't strictly utility jobs.

And I agree, all job types should declare how long they'll take. This is insurance. If we are sure that all utility jobs do declare their wall time and disk needs we could just remove the defaults and extract these from the job without fallback.

Anyways, this will blow up the scope of this ticket. At the moment if a job doesn't declare wall time or disk, we don't put it into the job and HTCondor picks whatever default it wants (no idea what these are, do you Antonio ?). I think we can make a better job than HTCondor, so we should put something halfway sensible now and maybe open another issue to track down all jobs that don't declare it.

Dirk, my point was precisely that this discussion should happen outside the context of this ticket, with broader audience, given its potential impact. I think we'd need to
-identify the key scheduling parameters (cores, disk, memory, walltime, anything else?)
-know what type of jobs (and how many) do not request them explicitly (why?)
-find out what HTCondor is doing in that case
-propose hopefully better values for the defaults than those currently in use by HTCondor. We could even define different sets of defaults depending on the type of jobs.

That discussion should not hold up this ticket. We pick sensible, maybe a bit too large defaults and we can discuss to our hearts content what the perfect values should be. Once we have them we can update the defaults in the code. I am not going to willing to wait for it. Anyways, feel free to discuss it in the SI meeting, you don't really need me for it at this stage.
I put my sensible (bit likely a bit on the high side) defaults in the code, I think they'll work just fine.

Ok, I agree, ideal values should not prevent us from setting reasonable values now.

Changes look good to me. I also ran a bunch of workflows (including a large enough multicore request) together and didn't spot any issues.
@ticoann it's good to be merged from my side

test this please


ETS integration tests need updating

Elastic Transcoder got out of sync with a refactor of Rusoto feature flags.  The flag needs to be changed from ets to elastictranscoder here: https://github.com/rusoto/rusoto/blob/master/tests/ets.rs#L1 .
There's more work to be done since our clients have also changed.  Examples: imports referring to rusoto::ets need to be switched to rusoto::elastictranscoder.  There's a bit more than that to do but that will help someone get started.

I'll take care of this.


bug introduced in .set

The latest release has a bug. Wasn't there in 2.2.4
n1: {
  type: N1
}

N1 = Class.create({
  ...
 fields: {
    n2: {
      type: N2
    }
  }
});

doc.set({n1: {n2: {...}}}) makes n2 an object of N1 class instead of N2 class.

You have a bug in your example. You're setting the n1 field which does not exist in the N1 class. So it's not possible that such a code could work. I've tested and nested classes are casted properly. So it's probably bug in your code.

Reprod: https://github.com/settlin/astro-bug
I did not explain the entire structure. It's like this.
N2 = Class.create({
	name: "N2",
	fields: {
		a: {
			type: Number,
			optional: true
		},
	}
});

N1 = Class.create({
	name: "N1",
	fields: {
		n2: {
			type: N2,
			optional: true
		},
	}
});

export const Post = Class.create({
	name: "Post",
	collection: Posts,
	secured: false,
	fields: {
		n1: {
			type: N1,
			default() { return {}; },
		},
	}
});

What fails is post.set("n1.n2", {a: 1}), that too only when post.n1 is undefined initially.

So it's a correct behavior. You can't set value on a document that does not exist. Astronomy can't figure out how to create such a nested document.

It worked till 2.2.4. I have not made any code changes. (It also works in mongo/minimongo).
Even if you plan to phase out this functionality (though I would beg you not to, as it removes all the flexibility that v2.3 provides with its cast and merge features), it should show proper error. What it does instead is that it sets n1.n2 to be of N1 class, instead of N2 class.
Please checkout the repo, run, click on the button and see the field and error.

Ok I will investigate it later today, but for me it should not work at all. It shouldn't set any value and if it did in previous version then it was a bug.

Sorry that it took me so long to investigate, but at first I had problems with running this reproduction because of the bug in Meteor and I've postponed it a little bit. Today I've took a look at it and in deed there is a bug that I've introduced... Sorry for that. I have to create more tests, to find such a bugs on earlier stages of development.
Previously I've been casting default values to its classes and with the new set() options I've changed some things and accidentally I've removed casting default values. So I've prepared a fix and I will release a new version today or tomorrow.

Fixed in 2.3.6

Thank you.